Hi. I recently upgraded my pixel 6a from A14 /e/ to A16 /e/
the in-between i re-flashed google factory BP2A.250605.031.A2, which is early android 16. This was working well and charged to 100%. Holds a charge, charges, all the things it is supposed to do (besides A16 is horrible “googled”)
Then a few days later flashed /e/ os e-4.1.1-a16-20260718651044-community-bluejay
Things were OK except, I can not charge, at all….
with the battery way down to 40% ish, I re-flashed factory BP2A.250605.031.A2. This allowed me to charge the phone again. This time i installed a few items, used it and… the 6a worked fine. So I re-flashed /e/ os e-4.1.1-a16-20260718651044-community-bluejay again with the 100% charge.
Now the 6A is not charging again - I can connect the charger - says charging then flips off to not charging… When I look at the battery status… it is reported as “dead” (see screenshot from /e/ OS)…. I am not sure if there is something funky with the firmware (from google obviously) - or something else is going on but… i have to be back in stock firmware to charge my pixel 6a.
Any ideas? screen shots are in /e/ 4.1.1, right after i charged my Pixel 6a to full while on factory - then flashed /e/ 4.1.1 - so screen shots are from fresh install tonight (9 August 2026).
FYI. no issues and no “dead” battery when on A14 /e/ OS before I started this update. I am expecting something weird, possibly more nefarious (by google) in the google firmware for A16 at the moment.
Same Phone on Android 15. battery is good health (see image)…. it is only A16 which shows and reports dead with a functional battery that still lasts me about 2.5 days…(I am not a heavy cell user, and turn off while driving due to flock and axom cameras)
Issue with 4.1.1 /e/ is on A16. Have to revert back to A15. Stock A16 does charge - I believe this is the trip over 400 cycles - I could be wrong - hopefully a dev can point me in the correct direction. I did extract the kernel - unsure if there can be a kernel mod for A16. used Android Boot Image Editor to extract boot.img from A15, A16 and the /e/ 4.1.1 A16 - however I am not so sure of myself moving forward on the kernel as this is not debian.
I have the factory flash which was removed from googles web site. ask me for the removed file for other Pixel 6a owners having issues with a known good battery. i imagine some units have a failing battery. Mine is flagged due to charge cycles. no overheating, no swealling, and lasts for days.
Reverting back to e-4.1.1-a15
Flashed stock bluejay-bp1a.250505.005, radio file radio-bluejay-g5123b-145971-250103-b-12866815
flashed A15 /e/ OS e-4.1.1-a15-20260719651411-community-bluejay
now charged to 100% on my mini devuan linux desktop and unplugged
Pixel 6a /e/ A15 4.1.1 not a fluke - battery is good. 1 day after posts above - same pixel 6a. battery strong, minor charge cycles only on usb from laptop (~ 5v 1.6A). Screen shot from this evening. /e/ A15 4.1.1 is also properly stopping charging at 90% as I have enabled. Verifying my battery did not “die” post flashing from /e/ A14 to A16 to /e/ A16 - and back to Google A15 to /e/ A15 4.1.1. There is something off with /e/ A16 4.1.1 and the charging.
as for /e/ A16 4.1.1…
I do believe a path to look at (? not sure though) - higher charge cycles from a 2022 phone in 2026… however this phone has been taken care of and not abused charging since I got it (swappa purchase “mint condition” but has been a great phone)
is the setup/kernel in boot and dtbo for A16 possibly triggering to not charge and false labeling the battery as “dead” in A16 but not in A14 or A15 /e/? Just a theory
