Eventually I could only use the phone when plugged in, and then it just totally wouldn't turn on anymore dead as a doornail. Oh one more important word of caution for people just letting this "can't read battery meter error" problem lie, and not addressing it immediately: last time I went like a month or so, nursing the problem because of the location that I was in with my phone. Don't know if this is somehow related to this mess with people's batteries swelling: but just putting it out there!! Seems like it shouldn't be getting so hot and probably not good for the battery when it does. The phone software is not supposed to allow a charge two ways at the same time, but don't know if there's a glitch in that and it's being over charged. The point of all this is: a ribbon cable connector is popping out allegedly, so pressure pushes it back in.Īs a sidebar I noticed when using Android auto I have the phone plugged in via a cable and then I also was leaving it in my wireless charger in my Audi Q5 the phone would get really hot. Now I read: pressure to the right of the logo on the back trying this now, and will see what happens. Error message is back this morning again. I didn't get the message for the rest of yesterday, and happy Skippy that I fixed it, however. Meanwhile back at the ranch: I can researching a fix: yesterday I applied pressure to the lower right corner of the back of the phone "after powering it down" 1 inch up, and 3/4 of an inch in from the bottom right corner. Don't know if there's a backlog but they haven't sent the packaging out yet. I'm having the same problem on my pixel 4 XL, with "system UI can't read your battery meter" error: I started a repair with Google ( not U break I fix: the first time I had this problem U break I fix wasn't going to cover under the warranty however I used Google directly and they did cover it for free) via tapping on a message error and they started a work order to send me the packaging. I've only ever owned Nexus or Pixel smartphones, but I'm planning to switch to Samsung for my next device. I called them up to confirm, and they emphasized that it was a REPAIR program not a warranty program, and recommended that I just buy a new device with a new warranty.Īt this point, I'm a little disgusted with both the quality of the hardware and the customer support for Google. About a week after sending it in, I received an email that it would cost more to repair the phone than it would be to replace it, so they offered to sell me a refurbished 4 XL (now over two years old, with known issues) for $519. I contacted Google, and they requested that I send the phone in for their own engineers to repair. They tried replacing the battery among other things, but the issue persisted and now the phone wasn't turning at all even after charging wirelessly they speculated it was a motherboard issue, but claimed that worst-case scenario Google would replace my device free of cost. On their recommendation I took the phone in to a local uBreakiFix/Asurion location. When I got back from my trip, I noticed that the phone would charge wirelessly and could briefly turn back on.My 2-year warranty expired in October but I read about Google's 1-year extended repair program, and their covered issues fit my phone's issues to a T. Even when holding down the power button and volume down for 7+ seconds, the menu disappeared almost as soon as it appeared. I presumed the battery had died, but no matter how long I charged it, from any cable, it wouldn't turn back on. Eventually, the inevitable happened and my phone shut down. I had already been running Android 12 for a couple months by that time so I'm not sure that was the direct cause, though I was on vacation in a warm climate at the time. Some of my research indicates a hard reset might work (I doubt it though) and it's possible that my battery died the same time I upgraded Android, but I'm not sure about that either.īack in December my Pixel 4 XL got that question mark in the battery, and a notification that the battery indicator had failed. I tried entering fastboot and when it came back into normal mode it actually displayed properly for a bit but quickly errored out again.ĭoes anyone have any ideas how I could potentially diagnose this? I have booted into safe mode and observed that it was having the same behavior. I tried an application called easy battery calibration, but it states that the battery is constantly 50% charged regardless of how long it's been plugged in. A consequence of this is that I've had my phone completely run out of charge and generally seems to be unstable. My phone seems to not know how much charge it has anymore and the percentage amount now displays a ?. I'm reaching out to see if anyone has been experiencing battery issues following the latest update to Android 12.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |