Develop Bugs

Uber Kingdom rEVOlution 3D Flashing over...

Probably a stupid question but:
Since this ROM keeps on updating so frequently and the instructions to install take a bit of time, is it alright just to flash over without deleting all the data and cache and whatnot? Or if you don't will it bring many problems?

Post a link to it and I will test it a few times and get back to you. I have a 10 hour flight, I can burn some time with it lol
Sent from my ADR6300 using XDA App

Well basically if he has changed or updated the base of the ROM between the two you will have probs. Basically things won't run correctly, get lots of force closes, rosie loops, that sort of thing. Really the amount of time it takes to wipe n flash isn't that bad so I do clean wipes every time its kind of force of habit so really I would suggest doing unless howls says otherwise or any dev for that matter. Happy flashing!
Sent from my Hybrid using XDA Premium App

yeah, definitely wipe every time... it's really not that tedious of a process. I still have all my texts and bookmarks for some reason, TB restores my MARKET apps and data, HTC restores my contacts, etc.
I know its a pain, but I just figure I'm already paying nothing for basically having a brand spanking new phone, the least I can do for the developer and myself is take my time and do it right.

http://forum.xda-developers.com/showthread.php?t=1088013
Here's the link to the ROM
And to everyoen else, thank you for your responses! They are all helpful and I guess I'll take the 5-10 min to wipe everything and do clean installs

Im using his latest version RSL0.6 and I can tell you that all those updates are worth it... about flashing over none of the devs recommend it because if you start to have issues they wont help you if you didnt follow theirs instructions... when I flash Uber Rom I usually only clean one time not tree like it says on the thread..... and I havent had any issues at all...
Hope this helps...

[Q] Constant freezes on multiple roms

I have been having some persistent freezes where I have had to pull the battery to get the phone to do anything at all. Here is what is happening:
1 - factory reset, wipe cache partition, wipe DALVIK cache
2 - install either CyanogenMod 7 or TSM PoolParty rom
3 - restore apps only or apps+data via Titanium or download the apps new from the android market and amazon app store
At this point the phone works great and will remain running fine for any period of time. However when I install a new app (after my first batch install), the phone starts to freeze. The freezing requires me to pull the battery in order to regain any activity on my phone. But after the first freeze, the phone freezes after about 30-45 seconds regardless of what I am doing on the phone.
I'll admit to being a big noob when it comes to rooting roms so I don't know if there is any logs I can look at or what the proper troubleshooting actions should be. I want to keep root and the ASOP roms so any help would be most appreciated.

This used to happen to me. People blamed it on the Incredible 2 HD ROM. I blame it on the processor mixed with scripts that were found on sense. Try increasing your min frequency to the like 368000 one. I used aerovan's kernels with CPU Master/Set CPU with:
gov-smartass v2
max-111300
min-36800
---------- Post added at 09:04 PM ---------- Previous post was at 09:01 PM ----------
You are also wiping wrong. You should wipe data/factory reset, format system, wipe dalvik.

Thank you for your reply AgalychnisCallidryas. Since I am using AOSP roms and not a Sense rom, would this fix still help (I still plan on trying what you said anyways)?
Also you mention that I am wiping wrong. Following your rom flashing guide, I am not sure what I format. I am not doing the back up steps (#1-6), and I don't see what to format before I get to step 12 where you install the rom.
Once again, thanks for your help and quick responses.

The steps I am talking about the CPU settings are FOR AOSP. Sorry for making it unclear. I was saying that the scripts in Sense fixed the problem, but there are no such ones in AOSP.
And I left the Format System out of my guide. Oops. Check it again, should be fixed now.

Well, I adjusted the cpu (I don't have gov-smartass v2 installed...and I honestly wasn't sure where to even get it from) using the settings in CM7 with no improvement. Is there anything else that you can think of?

Just a few questions?
Are you restoring with data on Titanium?
Are you undervolting?
I am willing to bet the problem is simple. What rom did you make your backup on? I have quit using titanium for all my backups unless there is game progress I am saving. I take the additional minutes to just install from market.
Sent from my Incredible 2 using xda premium

Also try flashing Areovan's kernal for AOSP.
Sent from my Incredible 2 using xda premium

Zax10,
I am using Titanium to restore my apps without system data, but the problem happens even when I download the apps new from the market (I'm approaching 9 GB of data because I have frozen so many times).
The problem has happened when restoring apps created on CM7 and TSM.
I do not mess with the voltage, other than the one attempt to fix my problem based upon what AgalychnisCallidryas said above.
I am currently trying Condemned CM7.2 rom and should it freeze again, then I will try adding in Arovan's Kernel....then I'll try Magnolia 2.0 rom

I would definitely flash Evans. 8 bfs kernel. I think changing cpu settings in cyanogenmod settings> cpu settings> I would change governor to either ondemand or interactive. Then I would check set on boot
Sent from my Incredible 2 using XDA App

Arovan's Kernel didn't help and in CM7 the governor is set to ondemand by default. I think I'm going to load a sense rom and see what happens. Also are there any log files that I can look at that will tell me why the freeze is happening?

what version of aero's are you using? bfs or cfs?

aeroevan_aosp_0.8_bfs
I have also now ran into the problem of not being able to download any apps to my phone, regardless of the rom, when selecting the app directly on my phone (I can still push apps to it from the web). I'm not so worried about that as I did find some potential solutions to it that I have yet to spend much time on, but if you happen to have a solution for that too then I'm willing to listen.

Sleep of death [answered]

I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2

Have you tried doing a super wipe between flashes?

Should fix Shutdown Freeze
rfail1988 said:
I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Hhhhmmmm, have you flashed any ROMs or was that a stock flash?
Even with stock flashes you can have issues just asking [for instance when I got a phone from Tmobile nothing would fix the shutdown menu not appearing for me then once I re-flashed a new ROM low and behold it worked].
Or if you are using the SmartAss V2 governor [or anyothers dependant on it like I believe lionheart is] in your CPU speed tweaking app you may want to use on demand or conservative instead. If you flashed any kernel, CPU tweak scripts you may need to check the values that applied [usually in init.rc folder somewhere as a script [just open in any text editor to read them]. Also definitely could be any UnderVolt settings [where you set voltage used by CPU under certain speed conditions and if set lower than the cpu can tolerate then when it switches to speed that is set too low is when it shuts off] . Undervolting can be done in either System Tuner or Faux Clock [swipe screen to left on open and viola global under/over volt setting ]. If you have not done any of these things or are unsure read below and see if that helps.
What I would try [in order]
First run backups in titanium backup and nandroid [titanium is so you can restore apps back without having to re-install and reset your settings and nandroid just to be safe if you are newer to working with Android Devices in this way]
Then Reboot in to recovery [on boot [right after you feel the very first vibrate] hold BOTH vopl keys in [press in center] and release when you see Samsung Logo, just be sure you release before it goes off screen]
Tap Clear Cache [in Main Menu]
Tap Clear Dalvick Cache [in advanced]
Flash Fix Permissions script [found in QA and in Dev threads for this phone] you want the Fix Permissions v2 by Minotauri zip [look at my past posts I have linked my mirror page to many posts]
You just save it to either internal or external sd and flash it just like you would when installing a ROM in cwm Recovery Menu
and reboot and see what happens [this should nail it really after clearing both caches and fix perms I bet]
if that does nothing reboot clear caches [if you had to wait to see] and go to mounts and storage and format /data [only]
Restart and see what happens...
If that really does nothing be sure to re-download your ROM via WiFi ONLY [or copy from computer]
be sure to flash darkside super wipe [google it, my mirror page, the forums, its everywhere] and Kernel Cleanser Script BEFORE YOU FLASH THE ROM
[Like So]
Boot in to recovery Flash Darkside Super Wipe
Flash Kernel Cleanser [another script [google, my mirror page, forums again]]
Then Flash ROM [and NOTHING else]
Boot phone [skip account setup we'll be back] wait 3 min after initial lockscreen if unsure] and don't do anything [no app installs setting adjusts nothing]
Restart in to Recovery again
Wipe Cache and Dalvick Cache
Install aany helper zips [like super user, toggles zip whatever with any custom radio being the last thing]
Restart Phone
You should not have shutdown freeze after reboot and clearing cache you should prolly still have it on initial boot, pull battery if needed and manually boot in to recovery as above.

RealPariah said:
Hhhhmmmm, have you flashed any ROMs or was that a stock flash?
Even with stock flashes you can have issues just asking [for instance when I got a phone from Tmobile nothing would fix the shutdown menu not appearing for me then once I re-flashed a new ROM low and behold it worked].
Or if you are using the SmartAss V2 governor [or anyothers dependant on it like I believe lionheart is] in your CPU speed tweaking app you may want to use on demand or conservative instead. If you flashed any kernel, CPU tweak scripts you may need to check the values that applied [usually in init.rc folder somewhere as a script [just open in any text editor to read them]. Also definitely could be any UnderVolt settings [where you set voltage used by CPU under certain speed conditions and if set lower than the cpu can tolerate then when it switches to speed that is set too low is when it shuts off] . Undervolting can be done in either System Tuner or Faux Clock [swipe screen to left on open and viola global under/over volt setting ]. If you have not done any of these things or are unsure read below and see if that helps.
What I would try [in order]
First run backups in titanium backup and nandroid [titanium is so you can restore apps back without having to re-install and reset your settings and nandroid just to be safe if you are newer to working with Android Devices in this way]
Then Reboot in to recovery [on boot [right after you feel the very first vibrate] hold BOTH vopl keys in [press in center] and release when you see Samsung Logo, just be sure you release before it goes off screen]
Tap Clear Cache [in Main Menu]
Tap Clear Dalvick Cache [in advanced]
Flash Fix Permissions script [found in QA and in Dev threads for this phone] you want the Fix Permissions v2 by Minotauri zip [look at my past posts I have linked my mirror page to many posts]
You just save it to either internal or external sd and flash it just like you would when installing a ROM in cwm Recovery Menu
and reboot and see what happens [this should nail it really after clearing both caches and fix perms I bet]
if that does nothing reboot clear caches [if you had to wait to see] and go to mounts and storage and format /data [only]
Restart and see what happens...
If that really does nothing be sure to re-download your ROM via WiFi ONLY [or copy from computer]
be sure to flash darkside super wipe [google it, my mirror page, the forums, its everywhere] and Kernel Cleanser Script BEFORE YOU FLASH THE ROM
[Like So]
Boot in to recovery Flash Darkside Super Wipe
Flash Kernel Cleanser [another script [google, my mirror page, forums again]]
Then Flash ROM [and NOTHING else]
Boot phone [skip account setup we'll be back] wait 3 min after initial lockscreen if unsure] and don't do anything [no app installs setting adjusts nothing]
Restart in to Recovery again
Wipe Cache and Dalvick Cache
Install aany helper zips [like super user, toggles zip whatever with any custom radio being the last thing]
Restart Phone
You should not have shutdown freeze after reboot and clearing cache you should prolly still have it on initial boot, pull battery if needed and manually boot in to recovery as above.
Click to expand...
Click to collapse
Lionheart works fine. Smartass v2 is a mess.
OP, what is your min clockspeed?
Sent from my SGH-T989 using xda premium

Thanks, ill try that after work today i didnt superwipe althoigh i have the file so ill try that and reflash my rom.
Sent from my SGH-T989 using Tapatalk 2

rfail1988 said:
I have flashed multiple gb roms with this same issue. My phine will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate :-(
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I have this same issue but no solution. It happens about 2 times a month, not enough to bother me but I have to pull the battery to get working again. I am using Juggs 5.0 with CPU tuner and the sophisticated profile minimum clock is 192 Max is 1512. I did do a super wipe before flashing and cleared caches and so forth. I was using gingersnap rom before and I wanna say it was happenening then too but I could be wrong. I always assumed it was something to do with the cpu settings, usually happens when I start an app shortly after waking the device.
Sent from my SGH-T989 using XDA

mr1ncred1ble said:
I have this same issue but no solution. It happens about 2 times a month, not enough to bother me but I have to pull the battery to get working again. I am using Juggs 5.0 with CPU tuner and the sophisticated profile minimum clock is 192 Max is 1512. I did do a super wipe before flashing and cleared caches and so forth. I was using gingersnap rom before and I wanna say it was happenening then too but I could be wrong. I always assumed it was something to do with the cpu settings, usually happens when I start an app shortly after waking the device.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Dont clock to 192. 384 is the min

G1ForFun said:
Lionheart works fine. Smartass v2 is a mess.
OP, what is your min clockspeed?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
My min clock speed is 192, and i am on jugg 5.0, but have had the same issue with foxstar and another rom that i cant remember. I havent messed with oc/uv settings, and have even eliminated my setcpu screen off profile so it wont happen in theory while not in use. Usuly it happens while being used in non-cpu-intensive apps like dolphin of tapatalk.
I have since cleared dalvik and cache (again) and it hasnt happened yet after a few hours. Only time will tell!
Sent from my SGH-T989 using Tapatalk 2

rfail1988 said:
My min clock speed is 192, and i am on jugg 5.0, but have had the same issue with foxstar and another rom that i cant remember. I havent messed with oc/uv settings, and have even eliminated my setcpu screen off profile so it wont happen in theory while not in use. Usuly it happens while being used in non-cpu-intensive apps like dolphin of tapatalk.
I have since cleared dalvik and cache (again) and it hasnt happened yet after a few hours. Only time will tell!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Like I said, don't clock that low

Looks like the cpu values arent the problem. I also fixed permissions and it died soon after i turned up my min values. A superwipe, kernel cleanse and reflash seem to be in order!
Sent from my SGH-T989 using Tapatalk 2

Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2

xcrazydx said:
Dont clock to 192. 384 is the min
Click to expand...
Click to collapse
For the record I raised my min to 384 but didn't solve the problem. Happened this morning surfing the web using Dolphin HD. Like I said tho, doesn't happen often enough to make me mad, and I don't think I'll be running this rom too much longer
Sent from my SGH-T989 using XDA

mr1ncred1ble said:
For the record I raised my min to 384 but didn't solve the problem. Happened this morning surfing the web using Dolphin HD. Like I said tho, doesn't happen often enough to make me mad, and I don't think I'll be running this rom too much longer
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
What kernel?

wow! U da man!
rfail1988 said:
Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I'm having the same problem with my SGS2? can you tell me the exact sequence? maybe we should make it a sticky, as I have seen many threads with the same problem but no definite solution!

Possible fix for the T-Mobile Samsung Galaxy S2 Sleep of Death.
Hey I had to work on a couple of phones just like your phone. After a couple of weeks with the phone, I found this out by accident and maybe it can help. Instead of just writing down the steps I made a video let me know if it works. I was able to reproduce on a couple of phones but don't know for sure if it is just a luck.
Here is my video.
http://youtu.be/SV3oDycVSb4
rfail1988 said:
I have flashed multiple gb roms with this same issue. My phone will power down at the least opportune times (at night and its my alarm clock). It can only be fixed by a battery pull and nothing else. Anyone know a solution to this, or even why it happens? Im desperate
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
---------- Post added at 08:41 AM ---------- Previous post was at 08:05 AM ----------
Hey I had to work on a couple of T-Mobile Sleep of Death Galaxy S2. After a couple of weeks dealing with the phone, I found this out by accident and maybe it can help. Instead of just writing down the steps I made a video let me know if it works. I was able to reproduce on a couple of phones but don't know for sure if it is just a luck.
Here is my video.
http://youtu.be/SV3oDycVSb4
rfail1988 said:
Its been a full day since a sleep of death (if that is whatever you call it)... After extensive searching i found the fix permissions script and it seems to have worked. Thanks again for you help. Question answered!
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse

JB roms suddenly not working?

I'm just going to throw this out there for anyone who may know the answer, after searching for the last 3 days, I'm not finding anyone else having the same problem, so I'm thinking it may be something I did. Here's the issue.
I'm a confirmed flash-a-holic, and flash new roms or backups probably 2-3 times per week. I haven't tried any of the JB roms until recently, but dove in just before Nit's Viper Rom became available for ICS. I had installed the JB "global" rom, and had it working(ish), and then changed to the viper mod, then installed Aeroevan's "unofficial JB" when the 10/25 update on Goo.im came available. The install went smoothly and it worked great for about a day, then tanked big time when I tried to change the launcher from Trebuchet to Nova (I can't even guess why THAT had anything to do with it). It started lagging big time and then boot looping. Now, upon trying to wipe everything (factory reset/cache/dalvik/all partitions but sd), I get nothing but boot loops and NONE of the JB roms will install. From my reading, I know others get boot loops, but after a sequence, finally get into setup. Mine will too after 5-6 boot loops minimum, but the screen freezes on the initial setup screen and it's completely unusable (touch screen unresponsive). I don't get why that is when I HAD it installed the other day and it was very responsive (using Aeroevan's JB mod). I WAS using the 4EXT recovery when I started doing all of this, then switched recoveries to the most recent TWRP, and it allowed me to install Aeroevan's JB mod, and even start the setup, but very soon started lagging and then the boot loops again. At this point, I'm sortof at a loss, and the only thing I can think of is that maybe I should NOT have been wiping the sd partitions and SHOULD have only been wiping cache/dalvik/factory reset. At the moment, anyway all ICS mods are flashing/running just fine (currently on Nit's Vipermod and really liking it btw), but if anyone knows where I went astray, I'd appreciate any pointers. Thanks all, this is by far the best forum I have been a part of!

http://forum.xda-developers.com/showthread.php?t=1805773&page=117

Oh boy..... Be sure and post back if you find a solution, glad I'm not the only one! I thought I did this to myself... which I guess I sortof did if you get technical.
Sent from my Dinc2 using Tapatalk

I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....

auberry05 said:
I had the same problem but was told to flash new radio and it stopped bootlooping and everything went back to normal....
Click to expand...
Click to collapse
Which radio did you flash?

Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.

bwpoersch said:
Ok, I made headway by reverting TWRP recovery back to 4ext's newest recovery, restored my oldest original stock GB backup with ext3 partitions which was originally a CWM recovery. I let it run after install for about 10 minutes without updating anything, then 4Ext wiped data, cache/dalvik, system. I then reformatted all partitions back to 4ext and then wiped everything again even fixing permissions. Then I tried a fresh install to Aeroevan's unofficial CM10 from 10/25 and gapps from 10/11. Install went smoothly and booted first time with no boot loops. I'm using it right now and I'm back in the butter again..... for now at least. If I take a turn for the worst, I'll post back.
Ok, well, scratch that, I am having the same problems a couple of other guys are having in the cm10 dev thread. I'm only able to run sense roms, original stock, UKBII, etc, no ICS or JB roms work, incredibly laggy and bootlooping endlessly. I have never had this much trouble flashing roms, I do it all the time. Sadly, it started when I flashed the viper rom, and I don't even have a copy of it to re-flash now since I wiped my card and it wasn't backed up on my computer (I think I must've downloaded it from my phone). I have spent WAY too much time on this, so am now relegated to only lurking here until someone can find a solution that's not just "firing down the well" like I've been doing since this started.
Click to expand...
Click to collapse
On follow-up, I read mixed opinions about the wisdom of using TiBu on restores, assuming I'm able to ever recover this my thinking is that one could use TiBu to restore apps ONLY and NO data and that would/should not cause a problem (assuming you're restoring a backup from within your installed ROM's file structure .i.e., JB/ICS/GB)? Also, I use My Backup Pro to restore call/MMS/texts only, that oughta be safe too shouldn't it?

I had a similar issue last night. never had problems flashing from viper to cm10 till yesterday. I've flashed back and forth about 3 times until I flashed the leaked 4.2 camera with sphere camera on aero cm10 Halloween build. I was playing around with the sphere camera and attempted to get it to actually finish loading the pics together by overclocking to 1.4mhz and I ended up pulling the battery. it boot looped very slow and laggy after. I did a full wipe, fresh install of aeros cm10 from twrp and got the same thing. So I recovered viper Rom from twrp , booted, then did a full wipe and install of cm10 and still boot loops laggy. I did not have the overclock settings "set at boot" ticked when I put it to 1.4mhz. odd indeed
sent by the viper

So... I was having no issues until today's huge headache. I was on cm10 10-25 and it worked great. Dirty flashed to 31 and it all went to hell. Slowed to a crawl so restarted to recovery to fix permission. Restarted and it kept restarting. I got some failure message when it would boot. Don't recall what it was.
I then tried 3 different recoveries and also full wipes and fresh flashes of 3 different roms. Same loop result basically. Finally an old recovery worked and I'm on a month old mrom version now. Soo... any thoughts on what the heck happened? I did nothing out of the ordinary. I was worried I somehow bricked but obviously not since I'm sending this on my phone. Kinda freaked to do anything right now... any thoughts or help/ideas?
PS... I just use the basic cwm and only cwm for my recoveries.
Sent from my Incredible 2 using xda app-developers app

Ukb wont boot here.
Sent from my HTC_Amaze_4G

so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper

fen0m said:
so I got aeros 10/31 build to boot after taking 10 min to finish the start up set-up. it was extremely laggy, it would random restart a few times. I played around with over clocking then under clocking but the cpu was maxed out 24/7. I'm assuming this is what is causing the extreme lag. I changed the governor to on demand and it started to act normal and not lag out. so I used it for awhile then I decided to change the cpu governor back to smartassv2 and then I was back to lag and the cpu was maxxed again... can't recreate the scenario cuz it doesn't boot now...
my conclusion is it has to due with the kernel and cpu governors on JB. I've tried aeros jb 12, 13,14,and 15 kernel and also Evans kernel with no luck on getting the cpu not to b maxed out... hope this helps solve the issue
Sent by the viper
Click to expand...
Click to collapse
Someone just threw down on the info. Sounds like I will be flashing the latest mrom. Not gonna repeat the horror of my recent cm10 fiasco. Thanks for this.
Sent from my Incredible 2 using xda app-developers app

Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium

jtsrtr13 said:
Unfortunately I too am finding it near impossible to flash any ICS/JB ROM. The closest I've gotten is the Google sign-in on Andromadus Mimicry, but that practically slows to a halt when signing in. As of now I'm on Condemned CM7 and I must say I REALLY miss Google Music.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Sent from my Incredible 2 using xda app-developers app

Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Sent from my MB865 using xda premium

A2Trip said:
Baby mamas INC 2 has been having same issues. I have to believe it had something to do with her being on the ICS leak from back in September with the 320 radio. I went as far as to getting back to compete stock with s-off. Got back to 2.3.3, got CWM and root. Hopefully I can try getting her phone back on CM9-10 cuz she really misses it and we were having EXACT problems stated above. Boot loops, touch screen not responsive, wallpaper would change out of nowhere, lock screen would be black with nothing but hardware buttons lighting up. Thank GOD for these devs and their work to get back to stock or I would have thrown this POS out the window lol.
Click to expand...
Click to collapse
I did the revert a while back for some other issues and didn't have any trouble getting aeroevan's CM10 up and running. I haven't had any issues with it other than the persistent bugs which are no problem for me. I don't think these issues have anything to do with the radio, but with the way the stuff is getting flashed. You might try a different recovery. I have had success with TWRP and CWM (as installed from ROM Manager, not touch) restored from a backup for me, but I didn't install using CWM.

ericsdeadinside said:
Try installing 4ext recovery. Format system, data, cache to ext3 like 3 times. Flash tunnas global cm10 rom
Click to expand...
Click to collapse
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium

Don't know what to tell you. I switched to 4ext ran CDMA miui for a week and I was able to flash cm10 with no issues.
Sent from my Incredible 2 using xda app-developers app

jtsrtr13 said:
Did these things ....even Stunna's CM10 was laggy beyond belief. Back to gb.....again.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
+1... seems like only Sence ROMs have been working on my girls Inc. 2. Viper seems fine for now... But her phone must literately hate CM9 and 10...7 works fine too. Not quite sure why these issues have been going on to few of us but I'm almost certain it will not be solved... On the move...
Sent from my MB865 using xda premium

hey guys I fixed my Inc 2 with jb ics lag/ boot looping issues.
check it out
http://forum.xda-developers.com/showthread.php?t=1987051
Sent from an incredibly running JB inc2

Galaxy S3 T-Mobile Problems. AOKP the reason?

My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks

Probably.

I'm running AOKP without any issue. What have you installed recently? Did you flash custom kernel, overclock cpu, change cpu voltages, etc...? Download OS Monitor app and see which processes are eating cpu and your battery. Maybe it's time to wipe everything clean: factory reset, wipe external sdcard, and reflash the ROM. An sdcard full of stuffs can cause the media scanner process to run long and eat up battery.
S-beamed from my GSIII via xda premium

I wouldnt go as fsr as blaming the rom right away, especially if its a milestone. More kernel related and or user error. Give us more info to help you solve this so you can use your the way you want to.
Sent from my SGH-T999 using xda premium

There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.

vx117 said:
There have been problems with the new kernel versions that have been merged into the ROMs. Take CM10.1 for example, each nightly is iffy. You never know when it's gonna be buggy or not. So far, my phone has been constantly rebooting.
Click to expand...
Click to collapse
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.

More like kernel related but yes aokp and cm10.1 can mess up your phone at times

Aerowinder said:
That's why people use custom kernels. Not just for overclocking, but also for picking up the slack on the CM kernel.
Click to expand...
Click to collapse
Yes, but even with custom kernels it can get buggy. No kernel is one-size fits all since each chip is unique. You gotta pick and choose which kernel works best for your phone.

Kyle Chen said:
My galaxy s3 on tmobile has been overheating, dying fast, charging slow, and randomly rebooting the past week. I'm running AOKP MR1 milestone. I'm thinking maybe AOKP is the issue, but not too sure.
What are some other stable good vanilla 4.2.2 roms I can try? thanks
Click to expand...
Click to collapse
I was having that issu as well but it was with touch wiz roms and kernels it actually ended up being a dud phone and battery. .. I have done a warranty exchange and it fixed it I also got an anker battery too and its been doing good only gets hot when I have it on charge and use it.. so it would ight not be just the rom. Try a different kernel see if its the battery getting hot and go from there. Isolation is key bud:thumbup:
Sent from my SGH-T999 using Tapatalk 2

This morning my phone was stuck on the AOKP boot logo and it was overheated like crazy. I did a battery pull and waited for the phone to cool down. After that I booted it back up, but the battery drained pretty fast and the phone still heated up.
I did not flash any custom kernals or anything. Just AOKP milestone 1.
Maybe I will wipe the entire phone and reflash aokp.
OR
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.

+1
I've been running AOKP since 2 hours after I got my d2tmo, initially KAsp3rd's unofficial builds, and now the official "nightly" builds... I have been using a very stable build since January, but recent official developments have me flashing regularly again.
Every single build since JB 4.2.2 MR1 has been very unstable on my device, somewhat randomly rebooting quite regularly... I say "somewhat" randomly because there are a certain few actions I can perform which will cause reproducible immediate reboots on demand, including but not limited to trying to DISABLE* USB Debugging. I've noticed that the device is far more likely to reboot itself when attempting to run apps as superuser. I noticed that Koush's Superuser app/infrastructure is embedded/integrated in the ROM and when I installed the latest version from the Google Play Store, it said that my su binary was out of date, so I updated it... It didn't resolve the random reboots, but when the device did reboot next, it performed some additional setup steps, including prompting me for my first & last name which was really odd because the initial setup had, I thought, been completed, and the device had been rebooted (by itself mostly) at least a dozen times prior to this.
I suspect these issues might have something to do with the superuser integration in the ROM and I ask that you who are experiencing similar random reboots take note of any patterns such as whether it occurs more often when attempting to perform superuser privilege escalation.
Currently I'm testing whether setting "Superuser Access" to "Disabled" helps at all. I'll report my findings once a conclusion is established.
*I'm trying to disable it to troubleshoot why the device doesn't show up when I issue `./adb devices` on my PC running Ubuntu 12.10 Linux; it doesn't even show up in the list of connected USB devices when I issue a `lsusb` command which is weird. I've rolled back to my backup of the January AOKP 4.1.2 build and confirmed that the device is visible to adb, so it doesn't seem to be an issue with my hardware...
P.S. I've posted about it in the new official d2tmo AOKP Nightly thread on the RootzWiki Forum (linked above).
---------- Post added at 11:29 AM ---------- Previous post was at 10:50 AM ----------
Disabling Superuser didn't seem to help at all. It has still rebooted itself twice since then.

[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13

PM me for a modified SlimBean build I use if interested. No random reboots and I have had the same issue in the past. Also, you could try wiping 3 times (cache,dalvik, factory reset and system) and then install KT747. Its the most up to date kernel as far as the patches and drivers go.
Sent from my SGH-T999 running Chihuahua v1 ROM

re: acceptable
Ch4m3l30n said:
I installed the following kernel I found here on XDA and I've had 2 crashes in the last 2 days which is acceptable to me.
dkp-3.4-d2att-d2tmo-20130424.zip
[KERNEL][4.2.x] dkp - d2tmo - 4/24/13
Click to expand...
Click to collapse
Why should any amount of crashes or random reboots be "acceptable" to anyone when there are so many
other roms in these xda forums to choose from which do not crash at all and are full of excellent features? LOL

Make a backup. Wipe cache and data. Then try another rom
Sent from my SGH-T999 using xda premium

My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.

Kyle Chen said:
My phone is actually not overclocked
This morning it was so hot that it literally burned my hands.
I am looking for a rom with similar features as AOKP like virtual buttons etc, no issues.
Click to expand...
Click to collapse
did you try reformatting your sdcard(s), factory reset, format /system partition (via recovery), and reflash the ROM? maybe just reformat the sdcards first, and see if that helps.
S-beamed from my GSIII via xda premium

Kyle Chen said:
<snip>
Are there any roms that are better than AOKP and what is the best kernal to flash?
Thanks.
Click to expand...
Click to collapse
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.

bwb8771 said:
Kyle, what ROM did you finally settle on? I ask because I'm looking for one, am contemplating AOKP, but came across your complaints/observations here, and am reconsidering.
Click to expand...
Click to collapse
I ended up flashing like a touchwiz galaxy s5 themed kitkat rom, which I have been using since September. Before that I used cyanogenmod 11. Haven't tried AOKP in a long time. When I get time I plan to flash some lolipop rom I guess.

Is there any activity on AOKP any longer, loved rom but it looks like 10/18/14 is the last build i can find.....