I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.
Related
I've been rooted for about a month now, playing with various roms and loving it.
However, today, I decided to try FrEak's newest rom using netarchy/toasts latest kernel. Things were going pretty well for a while, then all of a sudden, everything either quit responding or is taking at least a minute to respond, i.e. notification bar, menus opening/closing, touchscreen, etc.
So I did a complete wipe, cache, etc. and flashed the latest BakedSnack rom, again, with netarchy kernel, and same issue.
Does anyone have any suggestions? I'm wondering if going back and re-rooting would help....but if I do, should I use SimpleRoot or the newest unrevoked?
This is killing me!!!!
Last good responding rom I had was Fresh 3.1.0.1, but haven't tried reflashing that to see if it's the roms I'm using or something wrong with my phone.
Thanks in advance.
try a different kernel.
I'm currently running Cyanogenmod 6.1.1 stable and every time I try to flash it the rom will at some point within the first 30 minutes of using it reboot. After that point it will start sporadicly rebooting. I've tried everything from flashing the stock rom and flashing back to even unrooting it and rerooting it but nothing has worked. It doesn't seem to be a problem with the rom itself though as I had these same problems running myn's twopointtwo rls4. The odd thing is though that when I run the most recent rooted stock rom I haven't seemed to have these problems. I could be mistaken about the stock one though because I haven't run it for very long. I'm going to try a few things with cyanogen and if I keep having problems I'll probably flash the stock one and see if they go away. But has anybody else had this problem and if so do they know how to fix it?
edit: turns out my battery has some sort of short in it because I replaced it with my spare and haven't had any problems.
**** Note, this thread is not pointing fingers at ROM Devs *****
So starting back when porting of ICS from skyrocket was done I never had any random reboots or crashes fast forward to about 2 weeks ago when sudden and many freezes, lock ups and random reboots started. I first started seeing it on darkside v3 and it continued to darkside v6 during which time I decided to bounce to AOKP which gave me the same results.
Things I have tested are:
[1] Different ROMs (all based on 4.0.3)
[2] 3 different SDCards, all brand new
[3] Running different radios
[4] No apps installed, basic default setup after ROM flashed with and without add-on launchers. Tested using TW, Nova and Apex.
[5] Formatted sdcard and internal storage
[6] New battery - pending results, ordered 2 days ago will be here Wednesday
[7] New bluetooth - pending results, ordered 2 days ago will be here Tuesday (Not sure if it would help but it was a good excuse to tell the wife)
[8] Flashed multiple times using CWM (non-touch) and TWRP
Anytime a ROM is flashed I always superwipe and on a few occasions I have manually select clear/format section via CWM. My flashing steps are perfect and followed to a T per AOKP and Darkside. Ive always flashed 100% battery charge and anytime I try to logcat I'm unable to get a log due to the random reboot because it won't save the log.
Once the new battery gets here and that doesn't work I'm completely lost with what else I can try. Does anyone who has experience and knows the file system of 4.0.3 > 4.0.4 know if something has been changed that may help or does anyone have any other method for me to find the issue at hand? Also keep in mind running darkside GB based on 2.3.6 is stable as hell.
Your assistance is much appreciated.
I had freezes and reboot when I went from 4.0.3 to 4.0.4
then I just started from fresh. I Odin 'd to stock, and I started fresh with apparently and data. Didn't use titanium backup.. have not had a freeze or reboot since. I really think most users issues are because they are restoring old data.
Edit. After re-reading your thread I see that you never flashed a 4.0.4 rom. I really don't know why u are having issues.. your method of flashing looks really sound
Sent from my SGH-T989 using xda premium
Oh to add to that I have never restored apps with data or apps. I always go to the play store and reinstall fresh.
How old is your phone? I've only had mine since Mar and I've flashed plenty, restored apps with data, and no reboots or freezes.
Sent from AOKP Goodness :-D
LoopDoGG79 said:
How old is your phone? I've only had mine since Mar and I've flashed plenty, restored apps with data, and no reboots or freezes.
Sent from AOKP Goodness :-D
Click to expand...
Click to collapse
Maybe 4-5 months old.
well if you wiped all that and you still getting random lags and you re flashed your CWM
just make sure you download count hasnt moved you know when your in download mode
cause it might be hardware and try
darkside v7
and AOKP B40
if its not the software then its the hardware
you could always try odin and start fresh that always seems to work on mine
Odin or cwm 5.0.2.7
Sent from my SGH-T989 using xda premium
Cookiem0sta said:
you could always try odin and start fresh that always seems to work on mine
Click to expand...
Click to collapse
I odin and started fresh and ran ICS stock for 3 days with no crashes or issues. I then rooted and flashed new ICS Rom and have not had any issues for the past 48 hours. Everything doing great. Something must have been stuck between all the upgrade/flashes that were causing the crashes.
Eugene fixed the reboots on AOKP, as far as AOKP, it was ROM related.
http://forum.xda-developers.com/showthread.php?p=28087997
Sent from AOKP Goodness :-D
LoopDoGG79 said:
Eugene fixed the reboots on AOKP, as far as AOKP, it was ROM related.
http://forum.xda-developers.com/showthread.php?p=28087997
Sent from AOKP Goodness :-D
Click to expand...
Click to collapse
Yeah I read that earlier on twitter and although there was reboot issues my phone was just tripping. After odin to stock and starting fresh I have no issues with darkside however I might grab the latest AOKP with Eugene kernel. I hear good things.
ScreamingSkulls said:
Yeah I read that earlier on twitter and although there was reboot issues my phone was just tripping. After odin to stock and starting fresh I have no issues with darkside however I might grab the latest AOKP with Eugene kernel. I hear good things.
Click to expand...
Click to collapse
The battery life is awesome, though probably not as good as Darkside.
Just be sure to flash the one from the link I provided. That one has the fixed kernel and ROM
Sent from AOKP Goodness :-D
My stock phone was just fine and then.. Crashing, freezing, random rebooting, call echo, missed calls and missed text. My phone was possessed by some android demon after upgrading to 4.0 from Samsung via Kies. A google search took me to XDA. I'm a noob and all but I read every post and I watched all your YouTube videos (thank you ScreamingSkulls, that helped a lot). TDJ posted the DARKSIDE v4 rom while i was reading his thread so I flashed my first custom rom. No major problems, the camera froze when I first opened it but I killed it and it worked fine after that (I later read that others had that happen too). I flashed the v5 rom then v7.. I did have an issue when I flashed the VENOM 03 #3 kernel. After I flashed it stuck for a long time on the S logo (animating). I got it to reboot successfully so I flashed it again just be sure and it worked. I also flashed the VENOM 03 #5 kernel yesterday and everything is running smooth.
My phone was running for about 52 hours before my doubletwist app started changing songs by itself and freezing lol, this isn't the first time it's happened, I've even done a clean install from odin, funny thing is, with GB could run my phone for almost 5 days or more straight if I let it with no issues, but ICS seems a bit more laggy, I think I'll wait for the dev's to whip up some extra mean stuff until there is an official repair for it.
Nice thread. Id been reading about that reboots. I can tell you im on jaminson' s rom and no problem here about that or apps fcs. Smooth and stable. Is nice to read that you fix it
Vibrant- Kankwich Kang CM9
Galaxy S2 T989 - An amazing machine on any rom.
Only issue I get sometimes is when I'm trying to text someone and the keyboard doesn't pop up
Sent from my SGH-T989 using Tapatalk 2
I had hellish problems with ics, echo randomly in speaker, headset, even bluetooth, on wifi and not. App crashes, camera hosing, reboots, major scroll lag, touch lag, i ended going back to ginger a few times.
What i found out is to NOT RESTORE OR TOUCH ANYTHING! I have always run tdj's roms since he started putting them out but used titanium back to restore nonsystem apps, used rom tool box to tweak a few minor things.
I am running darkside evolution with v5 of ds kernel, i did not restore anything with tb didnt tweak any thing os just settings wise. Only loaded bare min apps i need. I do highly recommend nova launcher, its nice and fast and better on battery.
Just loading the ROM fresh and nova only issues are a few echo calls but very minimal. Performance and battery life are insane, I'm currently 15hr at 65% battery on light to moderate use, incredible. Otherwise runs perfectly great. Probably apps are just not totally ics compatible not sure.
Sent from the Darkside
constantly crashes... aokp. reboots not yey
Sent from my SGH-T989
Hi, I've been suffering some random reboots (about 3 per battery cycle) and after every reboot battery goes down drastically. I've changed the ROM and kernel and it still happens. I attach a photo of the battery life (you can see when the 3 reboots happened in the interruptions of the graphic) and a catlog (it's my first catlog so I'm not sure what to do). If you need any more info or the previous part of the log just tell me and I'll provide it.
Mine is a GSM gNEx and now I'm on Rootbox ROM (31/01/13 version) with ak 670.42 dummy kernel but as I said, it also happened in CM 10.1, AOKP, PA and with ak purity, leankernel and franco kernel.
Thanks in advance and sorry for my english.
it could very well be the phone itself. i had something similar happen on my toroplus and havent had the problem since i replaced it.
It could be your chip, but let's look at a couple of things first.
1) Are you dirty flashing by any chance?
2) Have you gone 100% stock and see if it happens there?
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
binlalo said:
Nope, I haven't tried 100% stock, will try tomorrow (after doing my last exam of my degree). Also I've just had a reboot at 82% battery and the first one yesterday was at 82-81%. Is it a coincidence or can it be a hint? Maybe it's the battery...
Also I've been doing a full wipe between ROMS, no dirty flashing except for upgrades on the same ROM (just upgraded rootbox to latest JOP40G)
Click to expand...
Click to collapse
Well I would do 100% stock boot, recovery, ROM etc... and see what it does.
I doubt it's your battery.
My random reboots stopped after I stopped flashing custom kernels. Try a clean install and keep the kernel that came with the ROM and see if you still get them.
Thanks, then tomorrow I'll try going back to stock ROM + kernel and see if it gets solved, if not I'll try with full stock.
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.