Develop Bugs

Anyone getting very high android system use?

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!

How to Stop IQD process?

I finally found what's been keeping my phone up and causing my cpu usage to be at 100%. In the spare parts and system panel apps, it's something called IQD. How in the world can I stop this because this phone is almost useless now because the battery drains constantly when not on the hook. It will just die overnight.

barats said:
I finally found what's been keeping my phone up and causing my cpu usage to be at 100%. In the spare parts and system panel apps, it's something called IQD. How in the world can I stop this because this phone is almost useless now because the battery drains constantly when not on the hook. It will just die overnight.
Click to expand...
Click to collapse
its kinda like on a pc in the task manager seeing "system idle process at 99%"
there is a runaway app causing your drain, its not the iqd process thats the problem......at least thats my interpretation of what 30 seconds of google can do....

Well even after doing a complete data wipe, it's still happening. I find it hard to believe it's a native app causing this.
And I found nothing out there at that places this process with a given app. I've had the same sets of apps and settings for a long time now and this just started happening.

barats said:
Well even after doing a complete data wipe, it's still happening. I find it hard to believe it's a native app causing this.
And I found nothing out there at that places this process with a given app. I've had the same sets of apps and settings for a long time now and this just started happening.
Click to expand...
Click to collapse
its unlikely a native app causing this , did you use TB to restore you apps?
with data? or app only?
if so TB has a freeze function if u have the paid version, might help rule it out,
just freeze one by one and the check cpu usage.
or maybe your battery is going bad?
or try a fresh flash without using TB to restore apps for a few
just trying to throw some ideas your way.........

I have TB but have never used it to restore apps. I always download them back one by one for some reason.
And I do want to do a fresh flash but with the newly updated Clockwork, it can not flash any roms at all. I want to switch to RA but need to figure out how.
And how can I know if the battery is going bad?

barats said:
I finally found what's been keeping my phone up and causing my cpu usage to be at 100%. In the spare parts and system panel apps, it's something called IQD. How in the world can I stop this because this phone is almost useless now because the battery drains constantly when not on the hook. It will just die overnight.
Click to expand...
Click to collapse
This process appeared when I upgraded from 1.77 PRI to 1.90 PRI. It was very frustrating to deal with. The only way get rid of the process is to downgrade Your PRI. FYI Nand restoring to a previous backup will not downgrade your pri. Hope that helps!

I had the same problem. What I did was use calk's formatt all zip then wiped cache and dalvik then flashed my rom again. But I,think I found the problem. Its the PRI. I bet you have a 3.30 rom on a 1.90 PRI. 3.30 roms need 1.77 PRIs, the 1.90 causes the wake issue. Put it this was, do what I said and it will be gone. I guarantee it.

barats said:
I have TB but have never used it to restore apps. I always download them back one by one for some reason.
And I do want to do a fresh flash but with the newly updated Clockwork, it can not flash any roms at all. I want to switch to RA but need to figure out how.
And how can I know if the battery is going bad?
Click to expand...
Click to collapse
inside rom manager it has an option to flash Amon_Ra revovery, if its greyed out then you need to dl it to your sd card, reboot and go back into rom manager, choose flash alt recovery (Amon_Ra v1.8)

mroneeyedboh said:
I had the same problem. What I did was use calk's formatt all zip then wiped cache and dalvik then flashed my rom again. But I,think I found the problem. Its the PRI. I bet you have a 3.30 rom on a 1.90 PRI. 3.30 roms need 1.77 PRIs, the 1.90 causes the wake issue. Put it this was, do what I said and it will be gone. I guarantee it.
Click to expand...
Click to collapse
Yes I do and I downloaded some all in one zip with wimax, pri, radio, etc and it was 1.9!
How do I go down to 1.7???

Thanks dude!! You are a lifesaver! It worked perfect.
If you were here, I'd buy you a drink.
My phone is finally normal and not sluggish and a battery draining nightmare. Whooo

barats said:
Thanks dude!! You are a lifesaver! It worked perfect.
If you were here, I'd buy you a drink.
My phone is finally normal and not sluggish and a battery draining nightmare. Whooo
Click to expand...
Click to collapse
haha no problem dude. Just hit the thanks button for me in my post

[Q] irc, myn's rls5, toastmod kernal.....wth is wrong

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.

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!

1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.

Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!

grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.

No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...

dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol

Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.

HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.

dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.

Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?

Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.

jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!

*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.

The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.

dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!

Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67

[Q] "Seaching for GPS..." loop?!?! HELP!!!

My droid incredible has been having some major problems with any GPS-related functions when flashing to custom ROMs. I've tried CM7, OMGB, OMFGB, and MIUI so far. The GPS worked great in OMGB and OMFGB after updating the radio, but when I tried this on CM7 and MIUI (both of which seemed much smoother and refined), no dice. I've also tried completely reflashing the rom (yes, I did wipe data, cache, and dalvik cache), uninstalling WeatherBug, flashing 4 different radios (4.08, 11.19, 5.02 and 5.06) as well as reflashing the original stock 7.28 radio, and even tried that fix through a sense rom where you dial some ## number and then enter some MSL number. That didn't seem to work for me, the call didn't even go through. No matter what I try, I can't seem to get GPS to work on either of the custom ROMs that I love. Major bummer, because I used GPS daily on stock 2.2 Froyo before rooting my phone. I'd appreciate any help at all on this issue and I really would like to get my phone's GPS functionality working again.
P.S. - I've already spent countless hours searching XDA as well as other forums about this issue, and the above list of troubleshooting steps is what I've come up with so far. Please don't lecture me with a useless response such as "Use the search function" as I have already done so. Thanks

Seems like you've done your research. Have you tried an app titled "GPS Status & Toolbox" in the market?

Just tried that app but no luck. I tried clearing the current GPS settings and then downloading new ones. Anything I'm missing?

I only saw mention of AOSP roms, did you try using *228 on a Sense rom? I'm not sure if there's a difference performing this on an AOSP rom but I recall folks saying to do that on a Sense rom. As you stated, GPS worked on two roms just not MIUI or CM7, which is weird. Have you returned to or are you currently using OMGB and OMFGB and retained your ability to use gps? I'm trying to rule out this being a hardware issue since you noted GPS failed on two of four roms.

SlimSnoopOS said:
I only saw mention of AOSP roms, did you try using *228 on a Sense rom? I'm not sure if there's a difference performing this on an AOSP rom but I recall folks saying to do that on a Sense rom. As you stated, GPS worked on two roms just not MIUI or CM7, which is weird. Have you returned to or are you currently using OMGB and OMFGB and retained your ability to use gps? I'm trying to rule out this being a hardware issue since you noted GPS failed on two of four roms.
Click to expand...
Click to collapse
Just reflashed OMFGB, and now GPS DOESN'T work?!?!?!?!? I've tried everything all over again, format SD card, reflash radio, I'm clueless.

Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.

SlimSnoopOS said:
Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.
Click to expand...
Click to collapse
I do use Titanium to restore system data. I flashed from CM7 to MIUI and did a batch restore of EVERYTHING, and got a FC on android.process.acore. I reflashed MIUI and the FC problem was fixed, but GPS still did not work. After this I flashed back to OMFGB and even complete stock 2.2 with sense, still no GPS. I will try your suggestion above, however I'm doubting this is a hardware problem as my GPS worked fine before rooting my phone. I'm guessing I screwed up something to do with the software, I just don't know enough about the subject to make an educated guess about what I screwed up. Anyway, I'll try flashing that gingerbread leak and let you know. Thanks for all the help so far guys.

SlimSnoopOS said:
Do you recall performing anything on your phone that may have messed with the gps? Do you restore system data at all with something like Titanium? My only other suggestion is to flash rmk40's gingerbread leak found here:
http://forum.xda-developers.com/showthread.php?t=1087077
The reason I'm suggesting is due to the 3G drop issue that people have fixed by flashing this. I'm doubtful, but maybe this could resolve the gps issue as well? Aside from this, I'm hoping another XDA member has suggestions/solution as it looks like hardware failure if you do not recall anything odd that caused the gps issues.
Click to expand...
Click to collapse
No luck. GPS still is not working.

Aight, well one thing is you are not supposed to backup/restore system data. Idk how deep it affects rom flashes but that is very likely the source of your gps issues. Have you flashed a rom without restoring anything and checking gps? With titanium you are supposed to backup user data. If you ask many dev's, they strongly discourage backing up system data.
1) flash a rom (step 2 is an option within Settings in gingerbread roms, idk about froyo roms)
2) if you want to completely start from scratch Cancel google restore by NOT signing into your google account upon initial setup. Go into Settings>Privacy and uncheck "Back up my settings" as well as "Automatic Restore."
3) sign into your google account and let it sync
4) test your gps
If you always restore system data through Titanium each time you flashed a rom PRIOR TO testing gps, this may have resulted in your problems.

I'd have to agree with slimsnoop, my first flash I made the mistake of restoring system data and everything went crazy wifi freaked, gps, repeated fc's. I'd try flashing then try gps, if its working then i'd restore apps one by one and see if any interfere with the gps. If that doesn't work then i'd go stock, master clear/factory reset and see how that goes make sure EVERYTHING important is backed up to your pc cause it will wipe it clean, if none of that works then i'd leave it stock and take it in for replacement or repair if possible.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

SlimSnoopOS said:
Aight, well one thing is you are not supposed to backup/restore system data. Idk how deep it affects rom flashes but that is very likely the source of your gps issues. Have you flashed a rom without restoring anything and checking gps? With titanium you are supposed to backup user data. If you ask many dev's, they strongly discourage backing up system data.
1) flash a rom (step 2 is an option within Settings in gingerbread roms, idk about froyo roms)
2) if you want to completely start from scratch Cancel google restore by NOT signing into your google account upon initial setup. Go into Settings>Privacy and uncheck "Back up my settings" as well as "Automatic Restore."
3) sign into your google account and let it sync
4) test your gps
If you always restore system data through Titanium each time you flashed a rom PRIOR TO testing gps, this may have resulted in your problems.
Click to expand...
Click to collapse
Tried that on Cyanogenmod just now, and I unchecked "backup my settings", however "automatic restore" was checked and greyed out, I couldn't do anything about that one. Also, I had to sign into my google account in order to download maps so I could test it. So if google sync is interfering with the GPS I'm not able to stop it from syncing on a custom rom. Thanks for the suggestion, though.
Jsmokey said:
I'd have to agree with slimsnoop, my first flash I made the mistake of restoring system data and everything went crazy wifi freaked, gps, repeated fc's. I'd try flashing then try gps, if its working then i'd restore apps one by one and see if any interfere with the gps. If that doesn't work then i'd go stock, master clear/factory reset and see how that goes make sure EVERYTHING important is backed up to your pc cause it will wipe it clean, if none of that works then i'd leave it stock and take it in for replacement or repair if possible.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Click to expand...
Click to collapse
I've actually already tried a complete restore back to 2.2, as well as a factory reset once I"m already at stock configuration. I'll try that again tonight if I get a chance. Is there anything you can recommend when retsoring back to factory configuration? any hidden settings I'm missing that have something to do with the radio or GPS or wireless settings?

No the only settings I've found for gps is location for pics and stuff, besides a factory reset should of changed it all back anyways, i'd say its a hardware issue but seeing as two roms were working at one point and not now it kind of seems that maybe something isn't getting erased with factory reset thats catching you up, I'm not sure what the code is for yours but i'd try the actual master clear code. I read somewhere theres a difference between factory reset and master clear not sure if there really is though, and if you can find a secret code list there might be something where you can change the gps sat pool. When I get home tonight I'll do some digging and see if I can't find something to get this working for you
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

When you install cyanogen, to test maps without signing in, download the gapps package from the cyanogen thread on this forum or on cyanogenmod forums
Sorry, can't provide links. On cell
Sent from my ADR6300 using XDA App

Cryous said:
When you install cyanogen, to test maps without signing in, download the gapps package from the cyanogen thread on this forum or on cyanogenmod forums
Sorry, can't provide links. On cell
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I do use the gapps package. It's also available on rom manager, however when you flash the gapps package it's basically multiple market links that take you to the apps of your choice so you can download the latest version. This requires you to sign into the market, which requires you to sign in to your google account =/
The only other solution I could think of is finding an .apk of the maps app, and doing that manually. I can't imagine that the google sign in is what is interfering with the GPS though. I'll try Jsmokey's suggestion and search for a master reset code, maybe that'll do the trick for me. If i'm flashing to the stock config the maps app is already included anyway. Thanks for the idea though.

Jsmokey said:
No the only settings I've found for gps is location for pics and stuff, besides a factory reset should of changed it all back anyways, i'd say its a hardware issue but seeing as two roms were working at one point and not now it kind of seems that maybe something isn't getting erased with factory reset thats catching you up, I'm not sure what the code is for yours but i'd try the actual master clear code. I read somewhere theres a difference between factory reset and master clear not sure if there really is though, and if you can find a secret code list there might be something where you can change the gps sat pool. When I get home tonight I'll do some digging and see if I can't find something to get this working for you
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Click to expand...
Click to collapse
No luck finding a "master clear code" on Google, but I did find that there is an option for factory reset in the hboot menu. Is this what you're referring to possibly? Also, is this different from the factory reset option in settings>storage while the phone is on?

UPDATE: Just called verizon, apparently they are out of stock of dinc's and are sending me a dinc 2! =D
Anyway, what steps can I take in the future to make sure I DON'T screw up my phone the next time in the first place (besides NOT restoring system data in Titanium)?

snoshreddax21 said:
No luck finding a "master clear code" on Google, but I did find that there is an option for factory reset in the hboot menu. Is this what you're referring to possibly? Also, is this different from the factory reset option in settings>storage while the phone is on?
Click to expand...
Click to collapse
Yeah I wasn't sure if it had a master clear or not some phones do some don't, I can't remember if what you're talking about is different from regular factory reset or not its been a while since I played around with a droid inc. Glad to hear you're getting a replacement and an upgrade at that. Basically do searches for what you can back up and back up everything system related you possibly can, you can't be too prepared when disaster strikes.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.

Sounds great. I'll probably do a nandroid backup at absolute stock and make sure it's working correctly. Thanks to everybody for all the help.
-snoshreddax21

Do you mean if you call them for a warranty replacement they will send you a dinc2?
Sent from my ADR6300 using XDA App

Glad to be of service! Hopefully things work out on the DInc2 for you.
As far as warranty replacements go, the availability of DInc vs. DInc 2 depends on what they have in stock in your area. At this point, I wouldn't be surprised if more folks received DInc 2's as replacements.