Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Android Bug Cellphones Google Operating Systems Software Technology

Android Pie Breaks Pixel XL's Ability To Fast Charge (theverge.com) 79

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.
This discussion has been archived. No new comments can be posted.

Android Pie Breaks Pixel XL's Ability To Fast Charge

Comments Filter:
  • by Anonymous Coward on Tuesday August 14, 2018 @05:14AM (#57121382)

    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.

    • Re: (Score:3, Insightful)

      by AmiMoJo ( 196126 )

      I've got a Pixel XL and didn't notice this issue because I charge overnight from a slower charger anyway. In general though I'm very happy with the Pie update. It's fixed the small performance issues I was seeing, just slight lag here and there. Feels like a brand new phone again.

      The only down side so far is that the new app switcher screen is swipe left/right instead of up/down, and I find the latter easier.

    • by msauve ( 701917 ) on Tuesday August 14, 2018 @07:26AM (#57121852)
      "Noted how quickly that bug got reopened after this hit /."

      Yeah, it's like Google has a time machine and can go back from the 6:00AM time it was posted here in order to re-open the ticket at 01:59AM.

      This was reported on XDA weeks ago, Android Police a couple of days ago, and on Reddit shortly after.

      Yeah, /. had lots to do with it.
    • Noted how quickly that bug got reopened after this hit /.

      You actually think anyone involved with this gives a shit about a slashdot posting? Slashdot hasn't had any meaningful influence in well over a decade and it's usually several days behind the curve on anything newsworthy. A few thousand people are regulars here and most of the well known people who used to hang out left quite some time ago. I have a hard time recalling the last time I read a posting here that I hadn't read elsewhere at least 24+ hours previous. The only reason most of us are still here

      • by dgatwood ( 11270 )

        Slashdot posted the bug this morning. If I'm reading it right, the bug was reopened at 10:59 last night. So unless there's time travel involved or something.... :-D

        • by morcego ( 260031 )

          So unless there's time travel involved or something.... :-D

          I wouldn't put it past them. Sneaky bastards. :D lol

    • ...if not to prevent bugs like this. Isn't all the stuff that makes your hardware work supposed to be contained in the /vendor partition and not updated with new OS versions. Surely the ability to fast charge would be part of that, no? Or does Google put out a whole new /vendor setup when they upgrade you anyway. If so, what's the point?

  • by palemantle ( 1007299 ) on Tuesday August 14, 2018 @05:21AM (#57121396)
    I don't think it's quite panic time yet. While it's true that this was marked 'Won't fix' at one point, the issue has now officially been reopened.
  • It's going on my nerves.

    I have a tablet running Android 5. Runs perfect. Why does the Airbnb app have to fail running correctly? What does the app have that it requires the Avantgarde of software to run on?

    This is bullshit. I wish vendors would focus more on stability and long-term support than this nonsense. Same goes for operating systems.

    My 2 cents.

    • by Anonymous Coward

      "updaterits"?

      Did you mean "updater-itis", perhaps?

      Maybe you don't know that "itis" means "inflammation of"

      So, you're tired of updaters being inflamed? Interesting

      I don't even know what that means.

    • I have an old tablet with some old version of Android on it- probably 5. I daren't connect it to Wifi. I don't trust the security of the operating system. I still occasionally play some old games on it I installed long ago when bored but never anything that requires internet.

    • Android tablet ... running perfect...

      Is this a post from an alternate universe where Google doesn't half-ass the tablet version of Android? Has slashdot proven quantum entanglement with parallel realities?

    • What does the app have that it requires the Avantgarde of software to run on?

      If it required 9 I'd agree with you. 5, on the other hand, seems a little ... dated.

  • AHhhhh (Score:1, Interesting)

    by Anonymous Coward

    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

  • by sad_ ( 7868 )

    that is the AI taking over optimizing your battery.
    obviously it's better for your battery not to be charged.
    the AI knows best, just comply.

    • That is what I was thinking too. AI is right around the corner: it will come right after we fix stuff like charging phones, root exploits, etc. Any day now.
  • by Lorens ( 597774 ) on Tuesday August 14, 2018 @08:06AM (#57122044) Journal

    I have noticed that when I use a certain (shady) cable to charge my iPhone, it charges much faster, but then it doesn't hold the charge. When I use the normal cable, getting to 100% takes much longer, but the device lasts twice as long. Is that known/expected behavior?

    • by AmiMoJo ( 196126 ) on Tuesday August 14, 2018 @09:11AM (#57122512) Homepage Journal

      Sounds like your battery is worn out. When batteries start to near their end of life their behaviour during charge and discharge starts to change.

      Apple had trouble with this before, you may recall, with phones going from 50% to 2% instantly. They eventually did a free battery replacement scheme to cover it; maybe yours is covered.

      The technical reason is that battery state of charge is estimated by measuring voltage and load. The voltage falls off as the battery discharges. More load also makes the battery voltage sag. So to estimate state of charge you need to know the voltage and load, and then fudge it a bit so for example it never goes up even if your estimate was a bit low.

      Fast charging creates more heat. Older batteries get hotter. It's likely that the charging system is ending charge prematurely with a worn out, hot battery. A slow charge mitigates that and actually puts more energy into the battery before the system thinks it is full.

      • Fast charging creates more heat. Older batteries get hotter. It's likely that the charging system is ending charge prematurely with a worn out, hot battery. A slow charge mitigates that and actually puts more energy into the battery before the system thinks it is full.

        The "reduced" battery capacity with an old battery isn't actually really reduced (at least not as dramatically as your % charge indicates). When you charge an old battery (normally, dunno about fast charge), it's still taking nearly the same

  • Well that's annoying as shit. Guess I'll hold off on updating my phone to 9.0 until this gets fixed.
  • And should only be enabled when you actually need your phone to charge quickly. This will prevent premature wear on the battery.

  • My fast charge on my Gen1 non-XL is fine, and my battery use while the phone is off is much improved... but while using it, I can almost feel it draining.

As you will see, I told them, in no uncertain terms, to see Figure one. -- Dave "First Strike" Pare

Working...