Related
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Do you leave bluetooth, gps, anything on? Trip turning your mobile days off añd let.the phone go through the däy then check your usage.
Android 17 said:
I've been getting over 40, sometimes over 60% android system use, which I find kind of crazy, considering I have downgraded my PRI from 1.90 to the 1.77, I've updated profile. I've ran 2 different sense roms based on the latest OTA, as well as Cyanogen Mod 6.1.1 final.....I'm running out of clues as to what would be causing this.
I doubt it's an app, as I tried flashing a sense rom and installed a very minimal amount of apps and I am still experiencing this issue.
I'm not quite sure what to try next here, is anyone suffering from a similar issue or have any other suggestions??
Thanks!
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Not really I'm getting between 20-30% usually .
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
With WiFi on
Sent From My Fully Rooted HTC Evo 4G Via XDA App.
When did it start doing that?
Android 17 said:
Nope, I turn off everything when I'm not using it, gps, bluetooth, even 3G are all turned off when not in use.
Click to expand...
Click to collapse
Swyped From Eva Running Myn's RLS4.95 On The Now Network!
For the most part I only get really high android system usage if I'm on my phone a lot. For the most part its less than 20%. But it can approach 50 if I'm using my phone a ton.
Sent from my ADR6300 using XDA App
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
drmacinyasha said:
Get the Spare Parts app (it comes in CyanogenMod) and check the Partial Wake usage in Battery History. If it's showing Android System as using a lot of the partial wake, then continue on:
This was a known bug that was found and solved in CyanogenMod. What's solved it for people still having it is to use a FORMAT_ALL.zip in recovery, which formats and completely wipes the system, data, cache, and kernel (boot) partitions. I used it, and it got rid of my wake-lock.
So to review:
1) Backup via Titanium Backup or something similar.
2) Nandroid backup.
3) Flash FORMAT_ALL.zip
4) Flash ROM (and gapps, if applicable)
5) Boot up, check partial wake usage after a while.
6) If all good, add your accounts, but do not add any apps. Check partial wake after an hour or two.
7) Restore apps in groups (5-10 apps), rebooting then waiting 30 minutes or so between each group, checking on partial-wake usage each time.
EDIT: Here's the FORMAT_ALL.zip
Click to expand...
Click to collapse
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Android 17 said:
Does this format the SD card as well? I thought i read it did, which would be a hassle. Also, you mentioned doing a nandroid back up, yet then flashing a rom, does this mean I would not want to simply restore my nandroid?
Click to expand...
Click to collapse
1) It will not format or wipe the SD card.
2) Nandroid backup is always done as a precautionary measure. You do not restore from it afterwards, in this case.
Yea i've been reading a lot of people with that ota has been having that problem
Android 17 said:
I think it may have to do with the newest OTA, or baseband update, I know that normally, most users can experience about 20% or so system usage with moderate use, but it seems I reach above 50% or so with moderate/a bit heavy use, it just seems like a bit much, and I don't remember having such an issue before.
I know some users mentioned the latest PRI messing with their phones, but I put the older one back on and it doesn't seem to have fixed it.
y
Edit: Like, for example, I just checked my android system after taking my phone off the charger, and it immediately shows as 70%, though this number will go down a bit, but even with light use, it seems to linger around 40-60% usage.
Click to expand...
Click to collapse
I just got my EVO last week so I have 3.70 and have not rooted yet. My phone has been off the charger for 7 hours and Android System is currently at 94% with Cell Standby, WiFi and Phone idle all at 2%. I had a Hero before the EVO and the Screen was what always seemed to use the most battery and its not even on the list for my EVO which I thought was very strange. I guess I need to look into the manual Root method since the others are not HBoot 2.10 and 3.7 compatible at this time.
I'm running stock 3.70 unrooted and right now Android System battery use is at 59%.
All of you with issues:
1) Download the FORMAT_ALL.zip from above.
2) Backup with Titanium Backup and Nandroid.
3) Flash FORMAT_ALL.zip
4) Flash your ROM
5) Via Titanium Backup, restore only user apps and their data, no system apps, system app data, or system settings! Do not restore from Nandroid.
I'm having the same issue. I'm stock UNROOTED 3.70. Is there a way to fix this for us non-rooted folks? I have been having significant battery drain and I did a factory reset and wiped everything except the SD card before the update. I do plan on roofing soon but I have the new 2.10 HBoot an hardware version 0003 and i want to make sure there is a well tested method and instructions before I attempt it. I'm no noob i've read this site daily since I got my Evo in June and I'm also an electrical engineering aka NERD but i just want to be certain before I root as this only phone I use and can't be longer than a day without it due to work. Any input here as well as on a fix for the high system use would be greatly appreciated! Thanks in advance!
Hi everyone!
first, happy new year!
I have a problem with my desire...it freezes in a way that the pulling the battery out is the only thing that helps...it doesn't respond to any button, the screen os off and I can't wake it up
it's rooted with unrevoked, clockwork recovery
tried different roms, the best for me is baadnwz dhd port...
been on that for a while and didn't have the freezing problem, then I flashed the miui..
went back to baadnwz and it started to freeze...a few times a day
then I reflashed it, uninstalled the font changer and that helped...for two days(thought that was the problem) but tonight(~36h from the clean install of the rom) it froze again...
so, I don't think it's the rom, obviously it is not the font changer...
why is this happening, has anyone encounter this before, is there a solution?
please advise, what should I do?
thank you
For what it's worth...
If you can get it back to stock ROM, then do so. Then take it back to the place you bought it and demand a brand new replacement. I would even go so far as to note/print a few pages of some the forums as evidence of the widespread problem.
If my (and many other people's experiences) on here are anything to go by, then your problem will only get worse...and let's face it, whoever has heard of a electronic non-software related problem getting better on it's own? Having read just about every available post on the subject I've concluded that no amount of flashing/reflashing/fiddling is going to fix it.
Sorry to be negative about it, but them is just the facts as I see them.
hmm...so it's like that huh?
what do you mean "if" I can go to the stock rom?
can't I flash the original rom, or ruu or something?(I don't know, never tried something like that)
but then again, I'm not sure that it isn't a software problem...I'm just lurking around to see if anyone has encountered this before and solved it....
if all else fails, I'll flash a clean rom without restorin my apps and see how it goes from there...
just my experience
trikpa said:
hmm...so it's like that huh?
what do you mean "if" I can go to the stock rom?
can't I flash the original rom, or ruu or something?(I don't know, never tried something like that)
but then again, I'm not sure that it isn't a software problem...I'm just lurking around to see if anyone has encountered this before and solved it....
if all else fails, I'll flash a clean rom without restorin my apps and see how it goes from there...
Click to expand...
Click to collapse
In all honesty, you may be able to reflash back to stock ROM. It may well depend on what firmware you have on your phone and whether your phone is branded (mine is T-Mobile UK). I know when I originally got mine and rooted it, it was hboot 0.83. It went wrong (external speaker stopped working). I was able to flash it back to stock ROM and I sent it back to HTC. When I finally got it back after 8 weeks (long story involving HTC incompetence and bad luck/incompetence with UPS), it was on hboot 0.93.0001. I rooted it with Unrevoked and installed LeeDroid 2.2f ROM. Shortly afterwards, it started to freeze/reboot. However, everything I've read so far leads me to believe LeeDroid wasn't the cause of the freeze/reboot fault. The problem is far too widespread (just Google 'HTC Desire reboot freeze problem') for it to be caused by a particular custom ROM.
Anyway, the upshot for me is that no matter what I've tried, I haven't been able to get it back to stock ROM and therefore, can't send it back for repair/replacement.
I sincerely hope you have better luck than me.
well, I'll see how it goes..
thank you for your answers
is there a way that I can make a log or something to see whether an application is doing this or something else?
well, I think I solved my problem, and for further reference here's a post that I did in another thread where this was disccused..
trikpa said:
just to let you guys know, I don't have any more freezes
some say it's because of the sense rom, some it's the dhd rom, others told me it's the radio or the ril files....
tried all of that plus few more things and nothing...
well, it turned out to be my backup(or an app in it..)
I always backed my apps and data with my backup pro, very nice app that restores everything....but the last rom flash I did, I didn't restored my apps&data and started fresh installs...and no freezing
I don't know what exactly caused problems, but one more thing that may be responsible...I flashed "font changer" and changed system fonts on my phone...and then backed my apps...maybe that's he deal...dunno...
anyways, I'm back with a killer phone with the best rom out there - baadnewz's
Click to expand...
Click to collapse
hope that will help someone
cheers
Do you still have any issues with the phone freezing sometimes when charging from A/C?
Mine doesn't freeze as much as it used to since updating the RIL files but being left charging seems to upset it
w0mbat said:
Do you still have any issues with the phone freezing sometimes when charging from A/C?
Mine doesn't freeze as much as it used to since updating the RIL files but being left charging seems to upset it
Click to expand...
Click to collapse
no freezes whatsoever
trikpa said:
no freezes whatsoever
Click to expand...
Click to collapse
OK, that sounds good. I only usually recover a few items using Titanium backup but next time that I flash a ROM update. I'll start it all from scratch and hope to get the same result as you.
I don't know, maybe it was a specific app but I don't have the time nor the will to test each one of them
I've got the same problem. Now that I read your post it makes sense.
Restored my apps trough titanium backup and 5 hours later my phones freezes.
Can u make list off apps that you have ?
mine (those that I restored)
vandaag 24
teamviewer
circel widget battery
dropspace
handcent
sdwatch
adfree
advanced task killer
fotmob
gridcalendar
applanet
astro
barcode scanner
cardio trainer
compass 2.1
gouden gids
gowalla
shazam
flitz said:
I've got the same problem. Now that I read your post it makes sense.
Restored my apps trough titanium backup and 5 hours later my phones freezes.
Can u make list off apps that you have ?
mine (those that I restored)
vandaag 24
teamviewer
circel widget battery
dropspace
handcent
sdwatch
adfree
advanced task killer
fotmob
gridcalendar
applanet
astro
barcode scanner
cardio trainer
compass 2.1
gouden gids
gowalla
shazam
Click to expand...
Click to collapse
well, it's been a while since then and I don't know what apps I used back then...but I can tell you what apps I used that you use
from your list I used
handcent
adfree
applanet
astro
barcode scanner
and maybe the compass
hope it helps, but my advice, do a fresh install
tnx, Ill keep ya posted
flitz said:
tnx, Ill keep ya posted
Click to expand...
Click to collapse
any news?
my phone started to freeze again
and I didn't restore backup, did a full fresh install...
don't know what to do
Yes, I've solved my problem by buying a new SD card.
This time from Kinsgstond instead of Sandisk.
Hope it solves your problem too.
My phone freeze after charfing while its off. I noticed that it freezes when it says "preparing SD card". This happened twice so far
Sent from my HTC Desire using XDA App
flitz said:
Yes, I've solved my problem by buying a new SD card.
This time from Kinsgstond instead of Sandisk.
Hope it solves your problem too.
Click to expand...
Click to collapse
well, I did buy a new 8GB card, but it never occured to me that it could be the problem....I think it didn't freeze right after I switched cards...
for now I flashed a newer version of the rom I'm using and will see how it goes...if not, I'll switch cards again
thanks for your answer
Yann2011 said:
My phone freeze after charfing while its off. I noticed that it freezes when it says "preparing SD card". This happened twice so far
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
well, sd card could be the problem in your case too, try another one...and post here with results
I'm curious
Well so far I have reflash the phone after a factory reset + wipe with no app restored via backup. It is performing ok so far. Last freeze was 2 days ago. I will wear down the battery to get a chance to charge it up this afternoon. I will see if it freezes again.
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.
When I have everything turned off, WIFI, GPS, 4G, it dies a few percent a minute
I don't have a signal in my room, and I read that it takes a lot of battery searching for one,
but even when I'm at a restaurant or someone else s house it goes down that fast
It's rooted, I was thinking of trying to unroot it, and take it to sprint
Would they be able to tell?
is there anything I can try to stop the battery from dying that quick, without another battery.
I have two battery's, but its annoying to keep switching them.
Go to settings /applications/running services. And check from there ...after that go to manage applications and see what's in the running tab
Sent from my Dell Streak using XDA App
not a lot
calendar
connect to pc service
dmservice app
google services framework
google messages service
htc dm
htc iq service
agent service
network locations service
messages
tranaction service
pvmservice start
pvwmdrmservice
voicemail
i dont know what most of that is
It must not have always been like this. What changed?
Check spare parts for partial wake lock.
I dont know what changed, Its always been a short battery, but not an hour.
I switched roms, but I switched last night again, and that didn't fix it
Whats a partial wake lock?
I looked in spare parts. I didn't see anything like that.
In spare parts, click battery history, you'll also see a running versus awake time, where it says other usage, click it, then select partial wake lock, and on the second tab, you can click since last boot.
android system
calendar
UID 10022
music
voice mail
dialer
media
internet
none of them are very full
shoofly said:
android system
calendar
UID 10022
music
voice mail
dialer
media
internet
none of them are very full
Click to expand...
Click to collapse
Calibrate your batter, do a complete wipe + stock rom. If it still lasts less then an hour or even less then 5 hours then you have a bad battery or bad phone
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
If i have a bad phone, and I unroot it, can sprint tell?
shoofly said:
If i have a bad phone, and I unroot it, can sprint tell?
Click to expand...
Click to collapse
As long as your bootloader is s-on and you deleted all your "rooting" files off the phone/sdcard, they won't know.
i would install process manager from market, it tells you apps running in real time, and how much cpu its being used, it might help you pinpoint if its an app doing this, also could use catlog, this app lets you see the log on your phone you might be able to see the problem there too
It could possibly be the PRI and NV on your phone. Several people have voiced concerns about horrible battery life, and one of the problems that's been pointed out is the PRI and NV versions (1.90 is the culprit). A way to fix this is to flash the 1.77 versions.
Do this to see what you are on:
Go to settings, then to about phone, then to software information.
Here's a link to download different versions. Thank Calkulin for this, he is the man. http://forum.xda-developers.com/showthread.php?t=715485
Put the .zip folders on the root of your sd card, go into recovery mode (factory reset and clear the dalvik cache and such I think, if I remember correctly, you might want to check with someone more knowledgeable than me) and flash those .zip folders and hopefully that'll help.
tropicalbrit said:
It could possibly be the PRI and NV on your phone. Several people have voiced concerns about horrible battery life, and one of the problems that's been pointed out is the PRI and NV versions (1.90 is the culprit). A way to fix this is to flash the 1.77 versions.
Do this to see what you are on:
Go to settings, then to about phone, then to software information.
Here's a link to download different versions. Thank Calkulin for this, he is the man. http://forum.xda-developers.com/showthread.php?t=715485
Put the .zip folders on the root of your sd card, go into recovery mode (factory reset and clear the dalvik cache and such I think, if I remember correctly, you might want to check with someone more knowledgeable than me) and flash those .zip folders and hopefully that'll help.
Click to expand...
Click to collapse
You got it right, except when flashing, he would just need to wipe cache and dalvik, no need to wipe factory/data, flash the pri or nv, reboot, wipe cache and dalvik, flash nv, then reboot again.
And that's why I'm a junior member, just rooted a couple weeks ago, and now addicted to flashing ROMs and scouring over the XDA forums... Thanks man
Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?
If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time
Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!
I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048
Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.
MIUI, for the win, man!
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.
prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?
same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.