Android Help What should I buy Thursday (Dec 28 2017) - Your weekly device inquiry thread! |
- What should I buy Thursday (Dec 28 2017) - Your weekly device inquiry thread!
- HTC and Motorola say they don’t slow old phones like Apple does
- The Pixel C has been dropped from the Google Store
- Pixel 2 XL XDA Display Analysis: A Well-Calibrated Package with Some Critical Mistakes
- No, The Pixel Did Not "Outsell" the iPhone X this Holiday Weekend
- Smartphone Display Technologies & Terminology Explained (OLED, LCD)
- LastPass updates Authenticator App and responds to article that exposed security flaw
- Next Samsung Exynos to be revealed on January 4, 2018
- [Discussion] Which Android device aged poorly throughout its lifecycle of 2 years?
- $300 off on Pixel 2 and 2XL at Verizon ends in 2 days
- Magisk v15.1[Stable] Released!
- Face unlock is probably coming to OPO 3/T
- CMV: Greenify is still required in Oreo. Doze, App Standby & limiting Background Activity cannot substitute hibernation
- The Nokia 1 may launch as part of the Android Go program
- Galaxy S9 and Galaxy S9+ swing by the FCC
- Multiple Verizon Google Pixel 2 Owners are Reporting their Bootloaders can be Unlocked
- iOS Mail Client Spark will be coming to Android in 2018!
- Has anyone bought a cheap Android and had their socks blown off?
- Rant: Android OEMs don't slow down their phones like Apple does because they CAN'T.
- Next-year Snapdragon 670, 640 and 460 specs leak
- Apple's approach to the iPhone battery concerns is exactly what Google should have done with the Nexus 6P.
- arcore-patch: Attempt to get ARCore Preview 2 running on unsupported devices
- Our Favorite Android Phone of 2017!
- Which Android phones have lasted you 3 years (or more?)
- [Discussion] Which Android device aged well throughout its lifecycle of 2 years?
- Android Parallel Tasks Incoming With Chrome OS 64 [VIDEO]
| What should I buy Thursday (Dec 28 2017) - Your weekly device inquiry thread! Posted: 28 Dec 2017 03:10 AM PST Credits to the team at /r/PickAnAndroidForMe for compiling this information:
Note 1. Join us at /r/MoronicMondayAndroid, a sub serving as a repository for our retired weekly threads. Just pick any thread and Ctrl-F your way to wisdom! Note 2. Join our Discord, IRC, and Telegram chat-rooms! Please see our wiki for instructions. [link] [comments]  | ||
| HTC and Motorola say they don’t slow old phones like Apple does Posted: 28 Dec 2017 06:46 AM PST
 | ||
| The Pixel C has been dropped from the Google Store Posted: 28 Dec 2017 11:04 AM PST
 | ||
| Pixel 2 XL XDA Display Analysis: A Well-Calibrated Package with Some Critical Mistakes Posted: 28 Dec 2017 02:07 PM PST
 | ||
| No, The Pixel Did Not "Outsell" the iPhone X this Holiday Weekend Posted: 28 Dec 2017 01:00 PM PST
 | ||
| Smartphone Display Technologies & Terminology Explained (OLED, LCD) Posted: 28 Dec 2017 02:19 PM PST
 | ||
| LastPass updates Authenticator App and responds to article that exposed security flaw Posted: 28 Dec 2017 10:06 AM PST | ||
| Next Samsung Exynos to be revealed on January 4, 2018 Posted: 28 Dec 2017 06:34 AM PST
 | ||
| [Discussion] Which Android device aged poorly throughout its lifecycle of 2 years? Posted: 28 Dec 2017 04:48 AM PST Was thinking back to my old HTC One X and that thing aged so poorly by the time it was 2014. It had a lot of specs that were shortsighted to say the least (Tegra 3 with only 1800mAh battery) that only served to cripple it faster. The processor was also so locked down that many devs left after less than a year, leaving development scarce. Which devices do you feel aged poorly during its 2 year life cycle, because of its specs, software, or trouble in the OEM itself? [link] [comments]  | ||
| $300 off on Pixel 2 and 2XL at Verizon ends in 2 days Posted: 28 Dec 2017 07:07 PM PST | ||
| Magisk v15.1[Stable] Released! Posted: 28 Dec 2017 02:05 PM PST | ||
| Face unlock is probably coming to OPO 3/T Posted: 28 Dec 2017 10:56 AM PST
 | ||
| Posted: 28 Dec 2017 04:02 AM PST I have read several times that "Greenify is no longer required after Marshmallow because of Doze". I disagree. Disclaimer: I've no app-writing knowledge, just a long-time Android user with 300+ apps on a rooted Nexus 6P. I did some research to form the opinion below. Feel free to point out my misconceptions! Doze can only save battery during screen-off time, by disabling network access, denying wakelock and JobScheduler until predefined "maintenance window". ForceDoze merely shorten the time between screen-off and Doze. It doesn't help when my screen is on. All apps become "active" when I exit Doze, and the phone may become slow when I switch on the screen. App Standby can "doze" apps during screen-on time, but it only applies to apps that are inactive for some time. (I cannot find how long it takes to become inactive) All apps become "active" when charging, and phone may slow down the moment I start charging. The Background Activity switch in Oreo can help enforce older apps to conform with Oreo Background limitation - by blocking implicit broadcasts, force the use of JobScheduler, etc. There will be less wakeups by the apps. I'm not sure, but I think it just make outdated apps to be more controllable by Doze. The problem is, I need to use some poorly-written but irreplacbale apps (e.g. local govt apps, local news, transportation, food delivery or heavy-ad apps) These apps may have a background service to receive notifications (which I don't need), or may update content by itself, etc. Only Greenify can help me keep these bad apps in check, by making sure the app won't restart regardless of screen on/off and broadcasts. It's important because I use my phone all the time when I'm travelling or working outside. If you only use a selected few and well-written apps, Greenify probably has no use. If you use many apps like me, without Greenify, I have a feeling that those bad apps will eat battery and slow my phone down badly. Let me know if I'm wrong! [link] [comments]  | ||
| The Nokia 1 may launch as part of the Android Go program Posted: 28 Dec 2017 09:08 AM PST
 | ||
| Galaxy S9 and Galaxy S9+ swing by the FCC Posted: 28 Dec 2017 05:22 AM PST
 | ||
| Multiple Verizon Google Pixel 2 Owners are Reporting their Bootloaders can be Unlocked Posted: 28 Dec 2017 09:40 PM PST
 | ||
| iOS Mail Client Spark will be coming to Android in 2018! Posted: 28 Dec 2017 08:37 AM PST
 | ||
| Has anyone bought a cheap Android and had their socks blown off? Posted: 28 Dec 2017 08:29 AM PST Just asking because I just bought a Xiaomi Mi A1, reviewers were pretty meh about it, but I got it to replace my iPhone 6s and I'm absolutely stunned by it. It's fast, never a stutter, multitasks amazingly well, the camera has already given me some of the best photos I've ever taken on a phone camera. I can't rave enough about the thing! If this is meh as an android device how amazing must others be? Anyone else amazed by their budget device (under $200)? [link] [comments]  | ||
| Rant: Android OEMs don't slow down their phones like Apple does because they CAN'T. Posted: 28 Dec 2017 06:06 PM PST Preface: I've done smartphone repairs/sold replacement batteries for ~6 years. iPhones are able to sacrifice performance in favor of not unexpectedly shutting down because iOS is able to check for battery wear in the first place. The OS knows how many charge cycles and wear percentage that the device's battery has sustained, and this information is accessible via Apple's diagnostics or even the end user. CoconutBattery is the go-to Mac OS app for many iPhone users, but for those who don't have an Apple computer there are a plethora of apps on the App Store that can do more or less the same thing (although their accuracy is questionable after iOS 10 closed off the API used to read battery data IIRC). Battery health information is also accessible via hardware as well, by using a battery tester such as this one. As you can see the battery stores a lot of useful information in addition to cycle count/wear level, such as serial number, manufacture date, temperature etc. Note how the battery doesn't only have two pins like a "dumb" battery does (one for V+ and another for V-); it has four pins - two additional ones for reading sensor info and battery data off the fuel gauge chip in the battery. Now, as far as I'm aware, Android has no idea how healthy a battery is based on cycle count or wear percentage. You could say that this is an argument from ignorance, but trust me; if there was a way to test an Android phone's battery wear percentage and cycle count at the software level, I'd be all over it. I have looked high and low, and apps like AccuBattery just don't cut it. Any app on the Play Store that claims to be able to provide battery health information are estimating it at best and completely fake at worst. In my six years of smartphone repair (and selling replacement batteries) this frustrates me to no end. Customers come in and ask for a new battery, and usually I don't question them and do as they say. Surprise surprise! It was Google Play Services all along! The battery replacement didn't help much, and I got the short end of the stick. "The customer is always right", after all! /s I'll give Android OEMs the benefit of the doubt when it comes to being able to test for battery health at the hardware level. But this is by no means user accessible, and the tools needed to access such data aren't openly available. You have to send it into a service center for x number of days/weeks and then be told something that can't be corroborated. You might even be charged a diagnostic fee if you decide not to go ahead with a repair! Most Android phone batteries have extra pins that suggest they have a fuel gauge chip or something of the sort that can be accessed using the right tools. Ironically, Motorola makes phone batteries that only have a positive and negative terminal - nothing more (including but not limited to Moto G4 Plus). Meaning not even Motorola can test for battery health! TL;DR: refer to title [link] [comments]  | ||
| Next-year Snapdragon 670, 640 and 460 specs leak Posted: 28 Dec 2017 09:09 AM PST
 | ||
| Posted: 28 Dec 2017 03:45 PM PST You may or may not have seen the recent article Apple posted about the iPhones battery performance, and how they are offering battery repairs for $29 and updating iOS to include information about battery performance that will be visible to the user. This is exactly what Google should have done with the Nexus 6P where there are loads of people (including myself) who experienced random shutdowns where the device wouldn't reboot until it was plugged in (SOL if you are in an emergency and don't have a charger). To be honest, this really puts Google to shame. With all the talk of how Google is an "AI" first company, they sure don't like to provide consumers with actually beneficial features, like reporting when the battery is under-performing physically. What's the use of Doze, background throttling, app standby and all these optimisations if the physical cell itself is the issue? These changes don't magically fix the chemistry, and don't give consumers the knowledge if their battery is no longer performing as it should. Hopefully we can use this to encourage Google this is a step in the right direction. Alternatively, they could just remove the battery status indicator, because that seems the direction they're headed... [link] [comments]  | ||
| arcore-patch: Attempt to get ARCore Preview 2 running on unsupported devices Posted: 28 Dec 2017 06:38 AM PST
 | ||
| Our Favorite Android Phone of 2017! Posted: 28 Dec 2017 12:03 PM PST
 | ||
| Which Android phones have lasted you 3 years (or more?) Posted: 28 Dec 2017 10:53 AM PST I read that first discussion about which phones lasted less than 2 years, and it seems like there are a LOT of flagship phones that died well within 2 years. I have always wanted to have the flagship phone so it would last me 3 years/be a little future proof, but it hasn't worked out. But if flagships are not lasting very long, Im starting to think paying a $400/year subscription to have a great smartphone is a little too much. Tell me which worked out for you, and what manufacturer(s) you really think make the longest lasting phones? As for me, I've constantly had to switch phones within 2 years since I got my first smartphone (droid Bionic) due to performance issues. My HTC m8 was doing fine just after 2 years, but couldn't keep up running Uber (Driver), Google Maps, and Spotify without very sluggish performance so I needed to upgrade. I chose the S7E the day it came out (IIRC March 2016?), and so far it's my favorite phone. So far the S7 Edge is doing pretty well. It's starting to chug or lock up on certain tasks that it didn't use to, and randomly die during calls, but overall I am still happy enough with the performance that I didn't take advantage of a $400 trade-in to get an S8. I plan on keeping this phone, hopefully, for another year or at bare minimum until halfway through next year. If my phone starts to really shut down shortly after the S9 comes out and I don't feel confident that any flagship will last me more than 2 years I think I will start to get the cheaper, mid-range phones (when they are new) so I can lower my smartphone "subscription" fees [link] [comments]  | ||
| [Discussion] Which Android device aged well throughout its lifecycle of 2 years? Posted: 28 Dec 2017 09:53 AM PST | ||
| Android Parallel Tasks Incoming With Chrome OS 64 [VIDEO] Posted: 28 Dec 2017 04:43 AM PST
 |
![Android Parallel Tasks Incoming With Chrome OS 64 [VIDEO]](https://b.thumbs.redditmedia.com/soc3pgrIjL2n8b_MZ8_s_V9MC68dwiEbMJQyG56zIzA.jpg "Android Parallel Tasks Incoming With Chrome OS 64 [VIDEO]")
| 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