After many weeks of hesitation I finally took the plunge, unlocked my bootloader (using DrakenFX's guide) and installed LineageOS. The process went smoothly except for the part where my battery is now hosed.
Basically, regardless of how much charge the battery has, the phone doesn't seem to read the level accurately. It doesn't matter whether the phone is turned off (while showing the battery symbol/charging indicator), in recovery mode, or booted to the OS. It might at one moment read 63%, then 1% the next. The interesting thing is that when I boot the phone to TWRP with a fully charged battery, disable the screen timeout and crank the brightness to 100%, it will take 3 days for the battery to discharge even if TWRP is reporting 1% battery, as if TWRP reads the battery as being full regardless of the level it's reporting.
However, if I boot to the OS with a fully charged battery, the OS will read 63% at first (it's always 63%), then within a few seconds will drop to 1% and the phone will shut down (every time). So far I've tried battery calibration apps, draining the battery in TWRP until it shuts off, then leaving it on the charger for 6+ hours (read somewhere that's supposed to reset the battery counter) and, of course, wiping cache/dalvik cache/system/data/internal storage and re-flashing not only LOS, but several other ROMs/kernels as well. I also tried different chargers/cables/power sources, etc. Still FUBAR.
Can anyone offer any insight as to what I may have done to cause this? Is my only option at this point to re-lock the bootloader, go back to stock and send it in for warranty service? I've been dealing with this for 2 weeks now, and the phone is basically a paperweight unless plugged in. Any suggestions here would be greatly appreciated.
That really sucks. it sounds like the battery is toast. try flashing the stock rom to see what happens? Perhaps a hardware issue was happening before you did that but it didn't show until after you took the plunge. Happened to me with the HTC One m8. Had speaker issues a day or two after I unlocked the BL and I know unlocking the bl didn't cause it, so i was mad.
twilighttony said:
That really sucks. it sounds like the battery is toast. try flashing the stock rom to see what happens? Perhaps a hardware issue was happening before you did that but it didn't show until after you took the plunge. Happened to me with the HTC One m8. Had speaker issues a day or two after I unlocked the BL and I know unlocking the bl didn't cause it, so i was mad.
Click to expand...
Click to collapse
The battery was great right up to the point where I wiped/flashed LOS the first time. I'm wondering if it was caused by a combination of A) the battery not being fully charged during the initial unlock/wipe/flash process (it might actually have been at 63%, but it was plugged in) and B) having wiped cache/dalvik cache/system/data/internal storage before the first install.
Going back to stock is my next step. I've been avoiding it because, for one, I don't think it's gonna fix the problem, and two, even if it does fix the problem I'm back to dealing with ZTE's maddening software, which is what drove me to LOS in the first place. Sigh...
n00bsville0123 said:
The battery was great right up to the point where I wiped/flashed LOS the first time. I'm wondering if it was caused by a combination of A) the battery not being fully charged during the initial unlock/wipe/flash process (it might actually have been at 63%, but it was plugged in) and B) having wiped cache/dalvik cache/system/data/internal storage before the first install.
Going back to stock is my next step. I've been avoiding it because, for one, I don't think it's gonna fix the problem, and two, even if it does fix the problem I'm back to dealing with ZTE's maddening software, which is what drove me to LOS in the first place. Sigh...
Click to expand...
Click to collapse
I personally don't think installing Los caused the problem for the simple fact that battery functions are controlled by the kernel which is Linux based (doesn't seem like it correlates but hear me out) just like the los kernel, and that part wouldn't have changed too much, if at all. I think it is a hardware issue. I have seen weirder coincidences happen when doing things like this.
I'd try clean flashing LOs or RR again (a fresh download) and see if that fixes it? Maybe even a complete format to make sure all traces of the last install are gone.
Something may have gotten corrupt the first time, possibly?
tele_jas said:
I'd try clean flashing LOs or RR again (a fresh download) and see if that fixes it? Maybe even a complete format to make sure all traces of the last install are gone.
Something may have gotten corrupt the first time, possibly?
Click to expand...
Click to collapse
So far I've tried 4 different ROMs and 3 different kernels, and each time I'm wiping cache/dalvik cache/system/storage/internal storage before flashing. I'm actually on RR now. I'm re-locking the bootloader and going back to stock today. I guess we'll see how good ZTE's warranty service is.
Related
Because I flashed quite a number of custom roms I have at some point broken the battery indicator. My phone works completely fine except that the battery status is displayed entirely wrong. It charges up to 100% and 4200 mV just fine but quickly goes down to 1%. The phone runs just as long at 1% as it took to go down to 1%, though.
I have tried many different roms and also went back to stock. I also know that deleting batterystats.bin is just a myth and Android itself should be able to figure it out over time. As nothing I have tried so far improved the situation I would like to completely wipe the internal storage, leaving only the recovery behind to flash a clean version of Android.
Is there any way to do this or is this highly unrecommended altogether?
Thanks in advance.
acxy said:
Because I flashed quite a number of custom roms I have at some point broken the battery indicator. My phone works completely fine except that the battery status is displayed entirely wrong. It charges up to 100% and 4200 mV just fine but quickly goes down to 1%. The phone runs just as long at 1% as it took to go down to 1%, though.
I have tried many different roms and also went back to stock. I also know that deleting batterystats.bin is just a myth and Android itself should be able to figure it out over time. As nothing I have tried so far improved the situation I would like to completely wipe the internal storage, leaving only the recovery behind to flash a clean version of Android.
Is there any way to do this or is this highly unrecommended altogether?
Thanks in advance.
Click to expand...
Click to collapse
Besides wiping data and doing a factory reset, there's nothing.
Maybe it's the battery itself... the circuitry inside it that measures capacity may have broken.
Do you have any friends or relatives that can borrow you a battery, just to check this?
Hope it helps.
Lean946 said:
Besides wiping data and doing a factory reset, there's nothing.
Maybe it's the battery itself... the circuitry inside it that measures capacity may have broken.
Do you have any friends or relatives that can borrow you a battery, just to check this?
Hope it helps.
Click to expand...
Click to collapse
I already bought another battery and the problem persists with both.
I found a thread that does the exact thing for a different device.
acxy said:
I already bought another battery and the problem persists with both.
I found a thread that does the exact thing for a different device.
Click to expand...
Click to collapse
Hmm, i'm not quite sure about formatting system, it seems to trigger the bootloader's security for some reason: http://forum.xda-developers.com/showpost.php?p=15862526&postcount=68 (very old post, from when development on the MS2 was just starting).
Besides that, looking at that zip's script:
Code:
format("ext4", "MMC", "/dev/block/mmcblk0p1");
format("ext4", "MMC", "/dev/block/mmcblk0p2");
format("ext4", "MMC", "/dev/block/mmcblk0p8");
I don't know whether mmcblk0p1 is /system, also I don't have a milestone anymore to check.
If you try it and you get stuck, you're gonna have to flash an sbf i think.
I'm still believing is something hardware related, the battery controller on the phone?
Good luck on this one.
Lean946 said:
If you try it and you get stuck, you're gonna have to flash an sbf i think.
I'm still believing is something hardware related, the battery controller on the phone?
Click to expand...
Click to collapse
As long as I am sure that I can still flash a clean sbf after deleting part of /system/ and not brick the phone instead I would give it a go.
I still have a week of warranty left and I am waiting for an answer from the repair service right now but I doubt that they fix this problem without charging me.
acxy said:
Because I flashed quite a number of custom roms I have at some point broken the battery indicator. My phone works completely fine except that the battery status is displayed entirely wrong. It charges up to 100% and 4200 mV just fine but quickly goes down to 1%. The phone runs just as long at 1% as it took to go down to 1%, though.
I have tried many different roms and also went back to stock. I also know that deleting batterystats.bin is just a myth and Android itself should be able to figure it out over time. As nothing I have tried so far improved the situation I would like to completely wipe the internal storage, leaving only the recovery behind to flash a clean version of Android.
Is there any way to do this or is this highly unrecommended altogether?
Thanks in advance.
Click to expand...
Click to collapse
I think you use the SBF package to resolve your problem. You can use google to find milestone2 sbf.
So I've had this issue for a while now, probably since spring where my phone will consistently die at around 15% Everytime instead of 1%, it will just skip from 15% to 1% then power off immediately. This happened today when I had battery saver auto enable at 25% and used it a bit more till it got around 15% and while in standby it just powered off and when I tried hitting it back on it actually did and showed 1%. During this time I made a phone call and opened hangouts for about 2 minutes and locked my phone again and about another minute later it randomly powered off again and would no longer get past the boot animation without shutting off. I don't believe this is a ROM issue since I've changed my ROM multiple times from stock to many custom ones (Marshmallow/Nougat) and the issue is present on all of them. I am currently on the latest PureNexus ROM with Franco kernel.
Only thing that would make sense is that my battery is degraded pretty badly and I just need a new battery installed. I bought my phone from Huawei and have no insurance plan so I don't know how much battery replacement would come out to be.
I've had the same issue since 7 hit. beyond frustrating.
i had that issue before too. i did a clean factory reset and the issue went away
Well I've done full wipes (system,cache,internal,everything) and have gone through multiple roms stock, purenexus, weta, etc and it's been present in each. It does feel like it started happening once i switched to Nougat but I couldn't remember exactly. Might try a marshmallow rom and see if it's any different since I haven't ran marshmallow since Android N came out for beta.
Installed 7.1.1 still happens.
https://imgur.com/a/I6vbZ
I've also had this happen multiple times. Not since I wiped to get the Google Assistant.
Hi, did you find out any solution?
I have this issue also but it happens randomly. It started when I installed Nougat.
I have that too, even after I've flashed a full system image of 7.1.1 DP (used the flash all script, so including everything). Very annoying...
same here. did marshmallow help at all? i'm about to go that route, lock boot loader, etc.
frodriguez96 said:
Well I've done full wipes (system,cache,internal,everything) and have gone through multiple roms stock, purenexus, weta, etc and it's been present in each. It does feel like it started happening once i switched to Nougat but I couldn't remember exactly. Might try a marshmallow rom and see if it's any different since I haven't ran marshmallow since Android N came out for beta.
Click to expand...
Click to collapse
Root if you didn't, then do a battery calibration
Hopefully this solves the issue
I have this issue too. Battery unpredictable drops to 0% at 10%-20% and phone switches off.
I've had this issue before. I did a couple of things so not so sure what fixed it. I installed ex kernel. And tried the different Cpu settings on the Interactive Governor. Ghostpepper is the one I'm currently on. No idea what fixed it. But my phone did that same thing twice before I swapped to a different kernel.
---------- Post added at 05:01 AM ---------- Previous post was at 04:52 AM ----------
I think its more or less your cpu not liking any of the settings. Maybe making it scale down to low to fast or not letting it scale up. I'm not so sure but I think thats what it is. I also doubt any battery calibration apps do much. If I remember right all they do is erase your battery history. If anything it might be bad to use those apps. To each his own tho. I guess you guys can try those apps.
This apparently happens if you have auto battery saver enabled. Disable it and you should've have the issue.
Fun fact: if you select whatever percentage in the auto-mode, it will die at that percentage.
I got the same issue but randomly after upgrade to 7.
Koragg618 said:
This apparently happens if you have auto battery saver enabled. Disable it and you should've have the issue.
Fun fact: if you select whatever percentage in the auto-mode, it will die at that percentage.
Click to expand...
Click to collapse
That makes sense. My was battery saver was set to 10% which is when my phone would shut down. What fixed it for me was dirty flashing the rom. But I bet it only fixed it because it turned off battery saver.
On the other hand, I guess it does a great job saving battery this way. Best battery saver ever.
Mine and my wife's are hardware related. RMA'd both of them. Her's is a 5X though and would turn back on after about 20-30 seconds by itself after it turned off. Factory reset and all that, still on MM. Spoke to Project Fi and guy had me update it to N, it did it again right after we got done doing setup and it was still in the 90s%
Jammol said:
Mine and my wife's are hardware related. RMA'd both of them. Her's is a 5X though and would turn back on after about 20-30 seconds by itself after it turned off. Factory reset and all that, still on MM. Spoke to Project Fi and guy had me update it to N, it did it again right after we got done doing setup and it was still in the 90s%
Click to expand...
Click to collapse
Sounds haunted! Happy Halloween
galaxys said:
Sounds haunted! Happy Halloween
Click to expand...
Click to collapse
Yeah I know right. What made me even more mad was when she told me, "oh that....that's been happening for the past 3 months!" :crying:
Update: Got the new replacement. They sent me a brand new one!!!
I was on oreo
I have backup so data not an issue thankfully.
Was using Nitrogen rom with its stock kernel but rom is not the issue since literally no one else is affected, im positive its my phone. Possibly hardware related.
Short version: As you can tell from the title. My phone is freezing randomly while flashing, or sometimes on booting it just stays at google logo. After freezing for 20 seconds and the phone getting hot, the screen goes off. It does not however bootloop.
It does not power off when the screen goes off in the normal sense either since if i attach a charger nothing shows, no battery icon, but i know it charges because then if i go into bootloader and then twrp back again, battery is increased. but if no charger, the screen stays off and battery is not decreased, like a power off :/ what is wrong?!
Full disclosure: i had my cpu(motherboard) repaired 2 weeks ago when it just dropped dead after freezing and me trying to reboot it, which it never did.(that was aquarius rom)
After repair i flashed nitrogen and all went fine until it happened yesterday too but thankfully i could access bootloader and occasionaly twrp. i somehow (after the 100th time of it finally not freezing in flashing or splash screen) managed to clean flash my rom again and it booted.
All went good for a day then suddenly it froze today and when i hard rebooted it, it never went past the google logo again, and screen turns off, which is where i am now. But now i can access twrp most of the time without it freezing now.
What ive done so far: Since this time it actually opens twrp 90% of the time unlike yesterday and freezes only few times, ive managed to flash a few different rom versions and even tried going back to nougat. ALL leading to -> Google logo 20 seconds, screen off.
I'm in the process of downloading factory images and OTAs, which will take 6 hours since i have a slow connection. but i dont know which i should flash (ill be using Heisenbergs guide). Which is a better option at succeding?
what i think is wrong: probably the flashing takes a toll on the cpu and it just freezes n gets hot n shuts off. NO bootloop. Ive attached logs from ''copy log'' option in twrp, i dont know if that will help.
Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores?
I'd highly appreciate some technical expertise and advice as to how i should procees from now.
Thank u for taking the time to read it!
Lord. Tech said:
.... Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores? I'd highly appreciate some technical expertise and advice as to how i should procees from now. Thank u for taking the time to read it!
Click to expand...
Click to collapse
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
v12xke said:
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
Click to expand...
Click to collapse
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images?
i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Lord. Tech said:
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Click to expand...
Click to collapse
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
v12xke said:
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
Click to expand...
Click to collapse
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon.
Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Lord. Tech said:
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon. Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Click to expand...
Click to collapse
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
v12xke said:
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
Click to expand...
Click to collapse
LOL i agree, cant even get a decent internet connection out here let alone battery spare parts to a back-closed phone 95% people haven't even heard of, including the 3 repair shops i took it to the first time!! i had to google it and show them pics and videos on how to open it imagine. But since it was dead weight at the time, that botched joke surgery of my phone was still my best hope haha.
well, in other news, nothing worked i guess the phone is toast now. it just keeps freezing no matter what, stock images, 4 cores off, modified boot.img, everything. I got it in Pheonix Arizona from best buy 2 years ago when they had the 50$ off on the gold version. so cant even freaking RMA it to google! Gonna send it in for repair as a last resort, though i dont know what they can do at this point, repair cpu?
Maybe i should start looking into replacements perhaps the OP3T.... damn this is depressing.
Thanks for the help, i guess u win some, u lose some...
Hi, I am a proud owner of a Essential PH-1. I bought it in november 2017 from amazon.com.
I used it for several days with the stock Android Nougat ROM, then I decided to try out the beta of Oreo. It worked well for me, I managed to use it as my daily driver with beta 2. Then, I don't know why, I decided to go back to the stock Nougat ROM. First I tried NMJ51B as described on the Essential page. But the phone audio stopped working (no tone dials, no call-voice.) Then I flashed NMJ32F and audio worked again. I made the OTAs and everything seemed to work just fine.
But then I realised, the PH-1 keeps staying warm and the battery discharged rapidly.
Now, even when tuned completely off, it still stays warm and the battery drains completely.
I can get into recovery and fastboot. I tried Oreo beta 3, but the problem doesn't go away.
Any ideas, what I can try to stop that? Is my device bricked?
It's possible you could have mismatched firmware between partitions. I recommend flashing the latest stable dump, 88C, from this guide: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
It's set up to flash to both slots. Obviously, you will need adb up & running if you haven't already.
You will need an unlocked bootloader (fastboot flashing unlock) AND unlocked critical partitions (fastboot flashing unlock_critical). These will both wipe all your data, so backup anything u don't wanna lose. Download the dump, unzip it, and place all files in fastboot directory (usually platform-tools in the android-sdk folder). If u run Windows, make sure u have the driver's from Essentials site. Then run the flash-all.bat (drag & drop into terminal). If the flash-all doesn't work, open it in a text editor and copy/paste the commands into terminal one at a time.
Thank you for the suggestions. I really missed the "critical" part of unlocking the bootloader. I was wondering, why I got so many errors while flashing.
(Essential should update their instructions on flashing stock ROMs)
Now I worked my way up from NMJ20D to NMJ51B (flashed both manually... without errors ) and then did the OTA to NMJ88C. My battery just reached 100% and I will let ist rest for some time to see, if the draining stopped. I will report back in about 2h.
Well that's a bummer -.-
I disabled everything, but the PH-1 still keeps warm and drains the battery.
(no additional application installed)
dzendeh said:
Well that's a bummer -.-
I disabled everything, but the PH-1 still keeps warm and drains the battery.
(no additional application installed)
Click to expand...
Click to collapse
Sounds like it could be a bad battery. Contact Essential.
I've been having the same issue since Monday. I've been running the Oreo Beta 3 and haven't done any system updates since... well, since the Beta 3 a while back.
At first I thought it was some app that may have updated since Sunday / Monday so I uninstall them all. Seeing that "Phone Idle" was keeping the phone awake, I thought it may have something to do with my network configuration (Rogers in Canada). After doing some research and trying different networking settings, it was still not making any difference. Then someone mentioned that perhaps it has something to do with a bad SIM card so I removed the SIM and let the phone sit for a while and still was doing that.
Now I've had my phone powered off for about 1.5 hr and the phone is still warm and draining battery.
Reading your post, I'm thinking it could be a defective battery as well. On Sunday night, I did drop my phone onto a carpet from my seat, note that I do have a case on and it was really a minor fall and didn't think anything of it. Perhaps it has damaged the battery? From a fall from 2' onto a carpet with my case on?
dataslayer said:
Reading your post, I'm thinking it could be a defective battery as well. On Sunday night, I did drop my phone onto a carpet from my seat, note that I do have a case on and it was really a minor fall and didn't think anything of it. Perhaps it has damaged the battery? From a fall from 2' onto a carpet with my case on?
Click to expand...
Click to collapse
I'd say it's Oreo beta (they're warning people on beta builds about significant battery drain), software is not optimal and consuming a lot of resources. One constantly restarting faulty resource could cause that too. Location services maybe? You haven't turned your phone off if it's running hot 1.5 hours in or you're having some shady agency paying a visit. Ceramics are good at heat dissipation
I held onto my Nexus 10 with my original battery for what seemed like forever until about a month ago where I finally decided to get a new battery to give it a bit more juice. One thing I did notice was after swapping the battery I was short exactly one screw from when I started on the battery. Those are tiny!
At first, it looked like the new battery worked wonders and lasted longer than the original although I noticed something. Every time it got to around 23% it would abruptly shut down. After researching a bit I tried the battery calibration app AND wiping the cache partition. Didn't matter.
I backed up my data then I attempted a factory reset. Didn't matter.
Up to last night I had been using a generic fast charger cable with brick and then tried a fast charger cable connected to the original nexus 10 wall brick as the original usb cable sort of disintegrated over the years. I tried using a different usb cable from my old Samsung S3 phone but I used it with the original power brick that came with the nexus 10. Didn't matter BUT I did notice that using it that time it took forever to charge to 50% and as of now is still stuck there. I"m going to keep waiting to see if this fixes itself.
Since I had wiped my data I figured it might be a good idea to install a custom recovery like TWRP unlock the bootloader and root the phone. Went for it although I ran into issues with Busybox and not having enough storage to install. After finagling it I put it on xbin and got it working.
I'm still using the latest version of stock lollipop. I was thinking of flashing the marshmallow romon Lineage 13 to retain use of the camera for scanning things but had heard of issues with youtube and bluetooth as well as random restarts so might not. I'm going to lose the use of the camera there are probably better versions to use than Lineage 14 which was my other choice.
Right after this in addition to having the battery shut down every time I started it back up it ALWAYS optimized apps. Every time and with about 172 apps or so boot times seemed close to 45 minutes. Horrible.
I tried running the calibration app again AND manually deleting batterystats.bin as I wasn't sure if the app was actually doing it. Again nothing.
I then went into TWRP and wiped the cache and dalvik thinking that might fix the optimizing issue. I noticed after doing so it I got an unable to mount storage message constantly. A quick repair file system command stopped that but it might be indicative of something.
Then I thought well maybe the battery issue might resolve itself if I let it drain from 100% to 0 or 5 inside TWRP. It didn't shut off right at 23% but like 5 minutes from that it went to 0% then 3 minutes later it auto shut off. I feel like that's indicative of something I just don't know what.
I'm beginning to think I got a bad replacement battery. Or that the missing battery screw is rolling around somewhere inside the Nexus 10 and shorting something out maybe? That's probably not possible but I'm at a loss.
I took photos of the cables connecting to the battery and made SURE they matched exactly as they did before with the lines on the ribbons so I'm inclined to think it wasn't that.
I'm not thrilled about having to pay for another battery and take off the back of the Nexus 10 again (that was the worst part hands down) but if that's all it is I'm willing to do it.
Kind of out of ideas except trying a second new battery.
Anyone have an idea of what else to try?
Random but I'll mention the first time I booted after the root SU asked to update new binaries. As I did a second factory reset after rooting the next time it asked me I declined. Not sure if that made a difference one way or another.
I did attempt to use the optimizing apps fix app but that stuck it in a boot loop. Leading to the 2nd factory reset.
While the battery hasn't resolved itself yet I'm trying it out again tonight. I got it to about 18 percent two days ago before it turned off. This time I'm going to charge it for 20 hours instead of 10. See if that makes a difference.
As for the optimization issue. I tried flashing a stock factory image and when the device became unrooted until I used the Nexus Root Toolkit to do autoroot with Super SU and Busybox I WAS able to reboot the device multiple times without the optimizing app issue. Then I rooted with autoroot and the issue came back,
Safe to say that my issue with optimization be due to something I'm not doing correctly during or after rooting the device.
Since then I've formatted wiped dalvik and cache and factory reset and left Busybox uninstalled though SuperSU is still a system app. Might be something wrong with the version of SU or the binaries maybe?
Version on my device is 2.79-SR3
Edit: After Uninstalling via the clean root option in Super SU I can verify that removing it removes the optimizing apps issue. Reinstalling it re-introduces it.
Should I be using a different version of Super SU for the Nexus 10? Should I use Magisk instead?
Update:
After installing Magisk in TWRP after one reboot there was one instance of optimizing apps it appears to not do this anymore after the one time. Magisk appears to be the way to go.
That's one issue solved! Nandroid backup time at last.
As for the other the battery appears to be getting slightly better life before.