Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
loswr86 said:
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
Click to expand...
Click to collapse
Answers to your first two questions:
1) After (although it S-ON it technically shouldn't matter)
2) No
Here are some tips, this could be as simple as a battery going bad, i consider a replacement one, either original HTC or Laza would be my recommendation. Also, I would consider going S-OFF, then going through @REV3NT3CH's full downgrade/upgrade guide from start to finish, this seems to be fix for many "odd" issues in the Rezound, I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
acejavelin said:
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
Click to expand...
Click to collapse
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
loswr86 said:
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
Click to expand...
Click to collapse
Always use the kernel that comes with a ROM, until you know it's stable and unless you have a good reason to switch... it is the best match to the ROM and the benefits you get from another kernel are generally marginal at best unless you need a specific feature that is not included in the ROM's kernel.
Proper sequence when installing a ROM when S-ON would be to wipe everything but external SD, then flash ROM, immediately reboot into bootloader and start fastboot, flash the boot.img with "fastboot flash boot boot.img" then reboot. Any other sequence could give questionable results.
Using Titanium backup to restore information in between JB and KitKat (either way) is not recommended, even with root access TiBu has issues restoring into /system in KitKat. It is highly recommended to reinstall all apps from the Play Store and use something like SMS Backup & Restore to handle text message migration.
I would again recommend a new battery, and going S-OFF especially now that the "wire trick" is no longer required using Rumrunner or Firewater S-OFF, then going through the downgrade/upgrade process I mentioned earlier.
So I have been unsuccessful at getting Windows drivers working for my rez. HTC sync and Windows used to identify it, but after I originally rooted it back in Dec, I wiped my laptop clean and set up a dual boot. Since then I haven't been able to get HTC sync to identify the phone, and ADB only works if I am in the TWRP or bootloader. Same with mounting and moving files, recovery only. Since the rumrunner S-OFF exploit needs me to be in Android, I'm in a pickle.
Things I have tried:
Current HTC sync software (Doesn't recognize the phone)
Downloaded and installed the driver from the Rav3nt3ch guide mentioned earlier
Also tried the old version of HTC sync that is mentioned in the same article
acejavelin said:
I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
Click to expand...
Click to collapse
to make sense of it. the reason it works is through some flashings or wrong deleteion of files the files that are integrated in system that a ROM does not have these RUU.exe files and OTA (ph98img.zip) files do have and repairs the phone to its neccesary needed state again. a good example to prove it is a typical rom is about 160mb in size and only contains bare necessities really..where as the ruu or ota is usually around 600mb in size and also full flashes the phone to proper partitions and such...as stated in my guide be sure to let phone fully boot and go through first setup of those particular roms....some people skip this step thus not activating their verizon service
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
loswr86 said:
So I have been unsuccessful at getting Windows drivers working for my rez.
Click to expand...
Click to collapse
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
REV3NT3CH said:
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
Click to expand...
Click to collapse
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
loswr86 said:
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
Click to expand...
Click to collapse
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
REV3NT3CH said:
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
Click to expand...
Click to collapse
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
loswr86 said:
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
Click to expand...
Click to collapse
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
The battery power can not be recognised by the phone?
REV3NT3CH said:
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
Click to expand...
Click to collapse
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
loswr86 said:
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
Click to expand...
Click to collapse
eh...always search the threads bud...all of what you need and updated is here
---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------
Hermosa said:
The battery power can not be recognised by the phone?
Click to expand...
Click to collapse
on older twrp or miscompiled recoveries it will simply just read as 66% and stay there....a good example...phils touch needs this battery reading part fixed as well as it shows 66% for battery currently
6.0.3.6 installed. Hopefully this oversight is what it takes to improve my experience with android modding. Thanks for your help fellas.
I don't remember having this much trouble modding my old HTC tilt back in the day.
Flashing clockworkmod 6.0.3.6, reinstalling CM 11 via CWM and then flashing the boot.img seems to have fixed my battery issues. After a few days of use, battery is holding charge much better. A note on what I think I was doing wrong, for others:
-I had originally flashed TWRP 5.X
-Then I followed this article explaining how to install custom roms whlie s-on
-I then loaded the various custom roms via the above method with the CWM 6.0.3.1 (Listed on their website)
-Chaos insued
Don't do this.
Hello,
I am totally new to android hacking, so thanks in advance for replying with as much details as possible.
I have an HTC One and wanted to root and install ARHD 70.0.
I rooted unlocked the bootloader, then rooted the phone. All went well.
Default install of ARHD 70.0 (with all checkboxes by default: sense6 tool box, google packages). I also checked the first 2 checkboxes for performances: ext4 setting and nosql setting. Before installing i did a wipe as recommended.
Then i installed ARHD 70.0. Installation went well too.
Upon reboot im in Sense 6 and i'm loving it.
As soon as I reboot, after about 1min, my battery level jumps to a fixed value (77% on that case) and goes down really slowly. Im 100% sure there is not tat much left because the indicator was at 50% just before i rebooted and also right after the phone restarted. After about 1min, it gets to 77% and sticks there.
I reinstalled multiple times (always with wiping first). I tried without Xposed framework and Sense 6 tool box... The issue reappeared after the first restart (from Sense, not from installation of ARHD).
I am pretty sure it's not hardware related because when i was on my unmodified HTC Once with Sense 5.5, it never happened.
I have not (afaik) modified/installed a kernel.
Do you guys know what could be the problem ?
Is there a way to see whats happening once i reboot into a log file so i can see which process affects this ? It always happens after reboot when i'm about 1min in.
Thanks for your help. Tried searching the forums, but i couldnt find anything helpful
EDIT1: AFAIK i must be S-ON since i havent changed anything regarding that
EDIT2: I also tried to update Xposed framework (because it was reporting that it was runnign an old version) through recovery (because im S-On) and then i updated Sense 6 toolbox (cause it needed an update) and it didnt fix my issue.
I
Long time listener, first time caller. Here's my sob story:
Love my DNA, and kept it stock, unrooted until November. Latest OTA did something terrible to my battery life (seemed to happen to many folks). Decided it was time to root, as I had enjoyed CM on my previous phone. My steps taken:
- Rooted via SunShine, achieved S-off, unlocked bootloader, all the goodies
- Installed TWRP
- Flashed CM 11 stable and set up
- started having SMS issues right away. First one would send, but subsequent messages would fail. Data was fine and received SMS okay. Got fed up.
- Tried flashing a couple of different radios, but couldn't with TWRP
- Wiped and flashed LiquidSmooth
- Enjoyed this ROM, but still had SMS issue. Got fed up.
- Wiped and flashed a superstock ROM
- SMS worked finally! But battery life was TERRIBLE, as Android OS, mediaserver and wakelock killed it in a manner of a few hours. Got fed up.
- Wiped and flashed ViperROM
- Love the ROM, but still having SMS issue. Got fed up.
- Flashed a couple of different radios via fastboot (currently on Baseband version 1.01.04.0308), and no resolution to SMS issue. Getting fed up.
So I either need to figure out how to fix the SMS issue OR solve the wakelock/mediaserver issue to be happy. I love this phone, but the problems are driving me crazy and I don't want to have to upgrade just yet.
Help!
PS- I'm on a Mac, so that complicates things a little.
Well, I wiped and flashed NuSenseSix and the associated firmware and FINALLY have a fully-functioning phone with great battery life and no SMS issues. Highly recommend! Hopefully that will be the end of the saga!
djun1t said:
Well, I wiped and flashed NuSenseSix and the associated firmware and FINALLY have a fully-functioning phone with great battery life and no SMS issues. Highly recommend! Hopefully that will be the end of the saga!
Click to expand...
Click to collapse
'
But you haven't gone past 4.4.2? Correct.
I recently upgraded my phone from 4.4.2 to 5.0.2. I upgraded it via the RUU method. My bootloader is unlocked, my phone is s-off and I rooted my phone after by flashing the supersu.zip file. I also wiped the cache and davlik cache after upgrading it. However, since then, the battery life seems worse. I have been using GSam battery monitor for a while now and it says that for App Usage, the Kernal (Android OS) is using about 25 percent, and Android System is using about 19 percent. Is this normal? My apps use a total of 75% of my battery while the screen only uses 20 percent. Any suggestions or tips and tricks? Thanks!
Just did the same thing with the exact same results. I may down grade back to the January global WWE RUU. How can it be so much worse!?
I'm on a rather older rom: http://forum.xda-developers.com/showthread.php?t=2544790 Omnirom 4.4.4 with TWRP
I have been having issues with the phone Endlessly rebooting while charging and this causes it to drain the battery instead of charging it (Started happening a few months ago). Now even with different batteries they get nuked from this same reboot while charging process. The phone would work as long as I didn't fully drain a battery, but once I did I couldn't get power back in them because of this rebooting/charge issue.
I bought an external battery charger today (I have three batteries already) so hopefully the phone will boot on a fully charged battery. I'm using the OEM Samsung wall charger and Samsung USB cable that came with the phone.
I would like to upgrade my rom but I know there was an issue with extending the internal partition and my chip being "possible to brick" when extending the partition.
My phone doesn't have the stagefright bug fixed so that was another reason I wanted to upgrade. Anyone who's had my phone and upgraded from kitkat to the newer rom's I'd appreciate some advice. I've been through many rom's before but the last couple (upgrading from cwm to twrp and now needing to extend the partition to actually be able to use it) are more advanced than what I've done so far.
Sorry for my vague post, it's been a long night/morning and I'd appreciate any guidance.
Lastly, I forgot to add- Over all these years of switching rom's and upgrading I have dozens of folders, paths and directories and God knows what that I'm fairly certain are redundant and taking up space, any way to clean that out (without bricking my phone- no I won't randomly delete stuff) safely when moving to a more recent rom?
Dang, no updates? I know it's holiday's and all. I just don't wanna brick my phone trying to upgrade from kitkat because of the emmc brick bug. Ebay said my external battery charger should arrive between today (Jan 5th, and January 25th) ... So I have some time lol. Been without a phone for two months.
Update, got the external charger, it worked and the battery is charged. Phone's power button still not working, looking for an assist to wipe and upgrade to newest rom >.>
Edgarhighman said:
Update, got the external charger, it worked and the battery is charged. Phone's power button still not working, looking for an assist to wipe and upgrade to newest rom >.>
Click to expand...
Click to collapse
The latest stock ROM for the i777 is jelly bean 4.1.2 and the latest unofficial ROM is CM 13 I think. I suggest using cook's rom wipe files (just search the galaxy s2 section here for them) and jeeboo kernel to boot wiz cat ROM which is kit kat based. It's a stock based ROM. Or just ODIN the jelly bean stock ROM and start from scratch to boot whatever ROM you want.