Slashdot Mirror
Android Pie Breaks Pixel XL's Ability To Fast Charge (theverge.com)
Google's recent launch of Android 9.0 Pie hasn't gone off without some early bugs and issues. According to The Verge, users are reporting that Android Pie prevents their phone from fast charging when plugged into many chargers. Google's own charger doesn't even appear to be working. From the report: Other Pixel XL owners say the bundled charger still functions properly and displays "charging rapidly," but third-party USB-PD (power delivery) chargers no longer juice up the XL as quickly as they did pre-update. Google has oddly marked a bug report on the problem as "won't fix (infeasible)," which is likely alarming to see for those experiencing it, especially since it can very clearly be attributed to the Android 9.0 update. Things were working normally, then Pie came, and then something broke. A second thread has been posted with more users chiming in to confirm they're affected.
Noted how quickly that bug got reopened after this hit /.
Instead of closed by some half-assed lackey, then what hope do we have of getting other bugs fixed (skia segfaults with bitmap (free'ing) handling whilst drawing in another thread, argb8888 segfaults (with register corruption), etc)
I mean, seriously, take a look at some of the bugs on there. Some devs are f*cking SCREAMING to get some bugs fixed and the dev team (which need to be bigger) are most of the time, oh hum, obsolete now I guess (then it continues in the next several fucking versions of the OS so the devs give up bothering to report)
Sort it out.
Privacy: Apps get internet access by default, granting an app access to any data on the phone lets it slurp all the data over to the company. FFS the calculator app on my phone phones home.... as if that's any of their business! Unacceptable, unfixed.
Confused 'Back' button, a do-all back button that steps backwards, cancels, switches app, exits app, does everything confused as fook. Broken design unfixed.
No way to tell the OS you're done with an app. Does the app need to continue in the background, yet get killed by the OS? Does it run in the background but *should* be killed by the OS? No amount of AI can fixup this shit, whatever UI man is blocking this, sack him.
Running multiple apps should not require the app be resizable, yet it does.
The app is portrait or landscape, the screen is portrait or landscape, when the phone ran one app at a time one the screen, this was one-to-one relationship. That's not true anymore and it needs to be addressed. Unfixed.
Fook is the memory a joke. At what point will I ever be able to run a 5GB app on a phone with 6GB??? At what point will I be able to switch away from an app, and not switch back only to find it needs to reload again.
Is the purpose of a smartphone to run apps the user wants run, or to save battery and second guess what the user wants to run? If you actually knew what the user wanted, you wouldn't be second guessing it to save battery.
Now its swipe up for the list of used app. Use to be click, now its swipe, a more complex action.... I hope this is a prelude to a better design, because you've just deprecated the MRU, hiding its functionality behind the home button. Great if you're actually going to fix up the mess of "apps run by their screen shot that may or may not be running' (= the MRU) and "apps run by their icon that may or may not also be running' ( = the app tray). On the other hand, I suspect you're just copying Apple blindly and badly.
ahhh,