Android Help LastPass' Android Authenticator App Is Not Secure |
- LastPass' Android Authenticator App Is Not Secure
- Pocky official Twitter joins the game to get Android P's name
- Instagram will now add ‘Recommended’ posts to your feed
- Some Samsung Galaxy Note8 units died after battery drained out - PiunikaWeb
- The Android 7.0 update for Sony TVs bundles in software that captures viewing information for targeted ads and content, Disabling this service results in a permanently reoccurring overlay.
- Spotify to Google Play Music - My observances on switching for a week
- Flurry: Apple led holiday device activations, but Samsung gained ground
- HTC to limit number of new smartphones for 2018
- ARCore Atom Visualizer is now available for Samsung S6, S7, S8+, Note 8 and more. • /r/ARCore
- [Opinion] After answering any question, Google Assistant should wait a few second for follow-up question.
- Nokia 7 rumored to launch globally alongside the Nokia 9
- January 2018 Security Patch Reportedly Rolling out to Mi A1 Oreo Beta Testers
- As good as it gets: has the smartphone peaked?
- LG G6 Oreo update spotted on Chinese forum
- Snapchat Developing "Stories Everywhere” to Push Content Outside the App and Grow Users
- An In-Depth Review on the Google Pixel Buds
- Is there an old phone that you never got but still really want?
- MIUI brings Display Gestures for Full Screen Phones.
- TechTablets Xiaomi Redmi 5 Plus Video Review
| LastPass' Android Authenticator App Is Not Secure Posted: 27 Dec 2017 05:09 AM PST
 | ||
| Pocky official Twitter joins the game to get Android P's name Posted: 27 Dec 2017 09:29 AM PST
 | ||
| Instagram will now add ‘Recommended’ posts to your feed Posted: 27 Dec 2017 12:13 PM PST
 | ||
| Some Samsung Galaxy Note8 units died after battery drained out - PiunikaWeb Posted: 27 Dec 2017 05:28 PM PST
 | ||
| Posted: 27 Dec 2017 07:42 AM PST Edit: The app is called Samba, not to be confused with Samba/SMB, a common networking protocol for file sharing in Windows and other systems. [link] [comments]  | ||
| Spotify to Google Play Music - My observances on switching for a week Posted: 27 Dec 2017 02:33 PM PST I've used Spotify for well over a year and as my first music streaming service, it's amazing, and Spotify is amazing. The idea of being able to keep all of my music on one cohesive server under one app at the convenience of $9.99 a month was astonishing, and it kept me entertained for such a long time. I listened to music nearly everyday, and on my device (LG G3 - Verizon), it was horribly slow. This was my one big drawback with the app, and through multiple re-installs of the app it would only temporarily solve my problem before popping back up again. Again, I don't know if this was an issue with my poor wifi signal or with my phone, but I do have good enough internet to stream 4k Netflix over wifi, and the G3 is still a flagship albeit a bit old now, so this left me scratching my head. GPM never really caught my eye, but over the last week I've been using it under the free 4 month trial offered with the Play Stores 12 day special, and its been an entirely different experience even with a library of the same size. GPM loaded as snappily as it should be expected to, which Spotify failed to do 90% of the time in just loading my albums. I was able to completely replicate my rather extensive, obscure library in GPM and keep all of my regular music player music within the same app. This was selling me at this point, along with the fact Google bundles a Youtube Red subscription for free with the ALREADY free 4 months subscription, Google had SOLD me on GPM. In terms of the performance and better integration with casting from my Google Home to my Chromecast, integrating into Googles ecosystem was small, but still felt ever so slightly more streamlined once everything was set up and it truly does feel faster and like less of a hassle running on my phone than Spotify would even refuse to do. The main gripes i do have with GPM is when you try to actually navigate the App, while it is much faster and doesn't take minutes to load at a time like Spotify did, having to rely on the left side of the phone and the top menus so much felt worse than spotify who landed you right in your library like a music app should. However in the end, Google wins my hand with everything you get with GPM compared to Spotify. I DO think Spotify has a more streamlined and professional experience by itself on phones and devices that run it smoothly, but with 4 free months of Google Play Music, the same library and selections I was able to have on Spotify, better Chromecast integration, AND especially a free addition of Youtube Red with the subscription trumps an unsupported, buggy experience I had all over the place with Spotify. Perhaps if I had actually gotten my issue solved beyond telling me to "delete and redownload" (I have a 10gb Library on a 5mpbs network, really?), then Spotify could've kept my loyalty. The only thing I'll miss is the better looking layout, but ii definitely won't miss the horrible function of it on my phone. I seriously have no idea why my phone was specifically so slow on Spotify, maybe it's its age? Maybe, but since support never bothered to help me get it fixed? Goodbye Spotify, don't let the door hit your ass on the way out. [link] [comments]  | ||
| Flurry: Apple led holiday device activations, but Samsung gained ground Posted: 27 Dec 2017 06:39 PM PST
 | ||
| HTC to limit number of new smartphones for 2018 Posted: 27 Dec 2017 06:13 AM PST | ||
| ARCore Atom Visualizer is now available for Samsung S6, S7, S8+, Note 8 and more. • /r/ARCore Posted: 27 Dec 2017 11:29 AM PST
 | ||
| Posted: 27 Dec 2017 07:56 AM PST Google's aim is to make assistant more conversational and make it feel natural, right? But having to say "Hey Google" for every question breaks that "I'm having a natural conversation" illusion. For example -
That's how it typically goes for most users. Granted, you don't necessarily need to wait for the bloop. You can ask your question immediately after without waiting. Two problem with that - 1) Most users don't know it. 2) Even if you know it, the bloop still happens and now it will happen while you are asking your question and that throws me off every time. For example, "Hey Google, what's the tem.. [bloop] ..uhh.. temperature outside? Even if you disable the bloop in settings, you still have to say "Hey Google" before everything you say. That's not conversational. We don't say "Hey Sam" before everything we say to Sam while talking to him. Instead, if GA waiting 2-4 seconds after answering any question, this would be so much more natural -
I know you can combine two questions with "and". For example, "Hey Google, what's the temperature outside and is it going to rain today"? But that's more of a planned question. You have to plan ahead what questions you are going to ask and then form a syntax. That makes you overtly conscious that you are interacting with a machine and not having a natural conversation. Thoughts? [link] [comments]  | ||
| Nokia 7 rumored to launch globally alongside the Nokia 9 Posted: 27 Dec 2017 08:14 PM PST
 | ||
| January 2018 Security Patch Reportedly Rolling out to Mi A1 Oreo Beta Testers Posted: 27 Dec 2017 08:52 AM PST
 | ||
| As good as it gets: has the smartphone peaked? Posted: 27 Dec 2017 12:06 PM PST
 | ||
| LG G6 Oreo update spotted on Chinese forum Posted: 27 Dec 2017 03:30 AM PST
 | ||
| Snapchat Developing "Stories Everywhere” to Push Content Outside the App and Grow Users Posted: 27 Dec 2017 03:04 PM PST
 | ||
| An In-Depth Review on the Google Pixel Buds Posted: 27 Dec 2017 02:00 PM PST When Google removed the headphone jack from the Google Pixel 2, they had to provide an alternative. The Google Pixel buds are in my opinion a fantastic alternative which make me wonder why I didn't switch to wireless earlier. I'm sure you've seen all the negative reviews for these cute little headphones however the experiences shared by the Verge, the Guardian, engadget and more don't seem to reflect my time with the Pixel Buds over the last couple days. Maybe I'm biased since I received these £160 earphones as a Christmas present, or I'm simply more tolerant of its shortcomings. In my view, the most important feature of wireless earphones is, well, the audio. It's not hi-fi quality and probably won't be the best audio experience you can get for the high price tag however (again in my opinion) it provides the perfect balance between treble and bass, making sure that the highs and vocals aren't overwhelmed by bass. That being said, the Pixel Buds deliver a surprisingly large amount of bass for earphones of this size. The device has an open ear design which means that it does a very poor job at isolating your surroundings. I don't mind this since I'll be primarily using them while walking and therefore being able to hear cars is good. You can turn them up with a simple gesture to immerse yourself. The buds stay inside your ear with the fabric hoops that are formed using the cord. Once settled the earphones sometimes feel like they're about to fall out. It takes some time to get used to this & trust the little hoops. My first impression as I unboxed the Pixel Buds was just how small and soft the case felt. The fabric used feels premium though the hinge keeping the case together is quite the opposite. Since the case is essential for the function of Pixel Buds I checked with Google Support to make sure that the hinge doesn't contain any electronics - apparently not, so if the top of the case ever falls off it won't be the end of the world. Inside the small container is three leds. As you're charging the case these go white indicating whether you either have over 75%, 50% or 25% battery in the case with the individual dots. If an amber light is showing then the case's or Pixel Buds battery is critically low. Charging the case is performed through USB C and should provide 20 hours of extra charge (not including the buds). Pressing the small little button while the buds are in the case as well as toggling manual pairing mode switches the leds between the device's battery and the bud's battery - a pulsing green light means that the bud's are connected and charging. I found that the battery lasts for as long as Google claims - 5 hours if I don't use the assistant. I found that with a bit of practice, inserting and removing the pixel buds from the case was easy to do with two hands, though sometimes as you can see in the video the connection wasn't working and I had to take them out and try again until the green led appeared. The cord wraps around the case and tucks in nice and tidy. Pairing was a simple process (once you remove the plastic covering the pins) and within minutes I had setup the Google Assistant. The assistant is called by holding and speaking to the right earbud. There's no wait between touching the bud and speaking & if the phone's internet connection is sufficient, the pixel buds respond immediately performing tasks such as searching the weather, sending messages or skipping songs. [pause, change song] The whole right side of the earbud is touch sensitive and whilst many reviews say that it is too sensitive, I've sometimes noticed that it isn't sensitive enough. The assistant works 90% of the time however during a conversation (such as sending a message) my buds often failed to hear my response when it asked who I wanted to message. It's not clear whether you're meant to hold down on the right earbud every time you want to speak or not and the voice in your ear switches between a high quality human sounding voice and a not so accurate robotic voice. On receiving notifications, the Pixel Buds will play a chime as long as your phone isn't in do not disturb mode. For the first two messages it will play the chime and say "Message from Thomas Pepall" (or whoever) and if you ignore both these messages it will simply just play the notification sound until you double tap the right earbud. This behaviour got quite annoying as my friends had conversations on a whatsapp group sending messages that Google struggles to pronounce. On the plus side, you can turn this feature off in the Google Assistant settings. I'd like a way to choose which apps I want to receive spoken notifications from. Replying to messages is performed by just holding the right earbud. The microphone in the buds is very clear and messages can be dictated clearly. After having made a couple phone calls, the people on the other end said that they wouldn't have guessed I was wearing earbuds. That's all I really want to say about the Google Pixel Buds, I tested out the translation feature and seems like a bit of a gimmick - adding latency by sending the audio from the buds to the phone and then to the cloud and therefore I'll just simply say that it worked but wasn't particularly impressive. Putting aside the small little issues and glitches with the assistant that will hopefully be solved in software updates, I think that the first generation of Pixel Buds definitely a very good offering from Google however for £159 I think that they appeal more to the early adopter & tech savvy than the general target market that Google is aiming for the Pixel 2. Overall, I'm extremely pleased with my pair and would recommend them to anyone who's willing to spend the money on a good pair of wireless earbuds. [link] [comments]  | ||
| Is there an old phone that you never got but still really want? Posted: 27 Dec 2017 01:39 AM PST Sometimes you just want something that at the time you either could not afford or simply did not buy, but you still want to own. For me, it's LG G4 - I just liked how this phone looked, it's design and its camera. Never bought it when it was in its prime but always wanted it. So I got one in late 2017. Pretty decent phone with a spectacular camera but of course has LG's well known quality issues. Nexus 5X - Don't own this, but this phone really makes me hate LG. Right now, this would've been the go to phone for all budget minded. Costs around $200, great design, camera that shoots way above its price point, stock Android. If only LG hadn't messed it up. I may still take a risk on it later on. Galaxy S6 - One of the best daylight cameras ever made. Beats both the S7 and the S8 in daylight. I like its design too. Want to own one, but it's still a bit expensive. [link] [comments]  | ||
| MIUI brings Display Gestures for Full Screen Phones. Posted: 27 Dec 2017 02:54 AM PST
 | ||
| TechTablets Xiaomi Redmi 5 Plus Video Review Posted: 27 Dec 2017 04:02 AM PST
 |
| You are subscribed to email updates from Android. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment