Just got my Evo replaced. I had an early 002 version that OC'd to 1228 24/7, ran great, only 3 point touch. I could run each and every kernel released without problems. My USB Charging jack busted and phone wouldn't charge so sprint replaced it. Rev 003 of course. My problem is that every custom kernel i try , i get re-boots, even at stock clocks. Well not full reboots, like a sense reboot. I can use set CPU with all my same profiles, set at 998 max with the stock kernels, and have absolutely no problems. Same CPU settings, or even removing set cpu all together i get the reboots with Kings and Netarchies kernels. I haven't tried them all, but a lot of them. No pattern to the reboots, just randomly happens. Any ideas? Has anybody heard of others with this problem? I can OC to 1192 and it doesn't increase the frequency of the reboots. It doesn't feel like the same stability issues i've experienced with previous high Overclocks. My 002 felt bulletproof when it came to tweaking. i hate that i broke it. This 003 feels fragile
I don't care.
Flash cm6 with snap and never need overclock.
beastmods said:
Flash cm6 with snap and never need overclock.
Click to expand...
Click to collapse
It happens when not overclocked. at stock settings with custom kernel. I know its a lot of rambling, but i think it is all pertinent information. But i have not tried CM6 with the new EVO. Didnt really care for it, but willing to try it for diagnostic purposes. Maybe it'll win me over this time.
[email protected] said:
I don't care.
Click to expand...
Click to collapse
Awesome, I dont care that you dont care.
Bump. Bump.
Anybody? This is why i originally posted in dev section. Kernel pros are not hanging around in Q&A.....
Bumpity 10char
i don't use sense based roms or kernels, but i assume this may hold true for them as well.
I've had a couple times where i flashed a kernel that afterwards prevented flashing other kernels. i was unable to successfully flash any kernel (even known good versions...ie: the same .zip i had used in the past).
once i did a full wipe and that fixed it.
the other time i restored a nandroid and after that i could flash as expected.
good luck.
DraginMagik said:
i don't use sense based roms or kernels, but i assume this may hold true for them as well.
I've had a couple times where i flashed a kernel that afterwards prevented flashing other kernels. i was unable to successfully flash any kernel (even known good versions...ie: the same .zip i had used in the past).
once i did a full wipe and that fixed it.
the other time i restored a nandroid and after that i could flash as expected.
good luck.
Click to expand...
Click to collapse
Thanks for input. I've actually done all of that multiple times Even complete un root re-root. Since i couldnt use any custom kernel at all, my 2 week old evo suddenly had a bad usb port so sad. I got my new one today and i've been at 1267 for the past 2 hours.. Awesome!
Ya i have frequent and random reboots running Ava v9 with kings 10 cfs. Plz help. Any fix?
Related
i have a sclc dinc that i cant get to clock past 998mhz. i have tried alot of diff kernals and roms to c if that would help. on my old dinc i never had a problem finding one that would work.. im currently running the new gingerbread rom and i went to c if i could go over the 998 and it bootlooped on me.. so couldnt get it on this rom either.. ive tried KK, Hydra, and a few others and nothing will get over 998. anyone else had this issue or have a solution? thanks
All cpus behave differently and the only guarantee is that it should be stable at 998. As there's no defect, there is unfortunately no solution. As crappy as it sounds, your phone is operating within its design parameters.
It is also possible that the ROM you're using isn't compatible with those kernals enough to allow it to overclock without bootlooping. Try it with Skyraider, Myn's, or Virtuous (just to name 3 I've used and overclocked) to see if you get the same results.
I have tried different roms with different kernals. Cm6, SR, etc... and still have same results with trying different kernals. I never had a prob with my old dinc but seems to b every thing I try on this one
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
TheManCalledX said:
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
Click to expand...
Click to collapse
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
That's the min for gingertiny right? If so, then yes. But I've literally never run into this problem since going from CM back to Sense. Never once had it happen during all my different Sense ROM flashes. Could it be something to do with the way CM does it's storage tree vs sense? I'm at a loss right now and just want some ideas on what to look into.
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
TheManCalledX said:
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
Click to expand...
Click to collapse
Flash amon ra recovery from rommanager. Then go into the recovery and select other anf fix apk uid mismatches, and fix permissions. You can flash back to clockwork when your done. I would also raise your min freq to 245000, and try that for awile.
Okay, I flashed a Nandroid backup from the very first day I rooted my phone. Then a couple others from other sense ROMs I have run. Every once in a while I'm still dealing with a little lag loading something, and I'm trying to let things settle in for a couple days before I flash a new kernel.
But, a friend at work also has an Inc, and after going from Sense to CM back to Sense, he's experienced similar problems. So I have a vague idea of what the problem is, but literally no idea how to fix it.
cmlusco said:
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
Click to expand...
Click to collapse
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
EDIT: I thought i would also mention that this happens on all governers except performance, not just on sa or sa2.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
cmlusco said:
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
Click to expand...
Click to collapse
I never had the problem using 128 before I switched to CM and back to Sense.
TheManCalledX said:
I never had the problem using 128 before I switched to CM and back to Sense.
Click to expand...
Click to collapse
Well i have never used CM, i have always used sense roms.
Try smartass governor (not smartass v2) and see if it helps. I don't know about reboots but there is no wake lag or virtually none.
Sent from my ADR6300 using Tapatalk
Ok, I posted a test release in the kernel thread. Please test it if you're having lag issues.
to themancalledx
I had the exact same problem going from aosp to sense. For me it was a pretty simple fix. I hope it works for you. Go into recovery select advanced and then fix permissions. Good luck.
New kernel released. Try that one.
Sent from my ADR6300 using Tapatalk
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
I've only experienced this after trying different roms and kernels. I flashed the stock kernel and the deodex rooted stock rom back at the same time and have had no such things happen again.
Imo, stock always runs better than any other rom. I always get better battery too.
My sensation was/is the same way, reboots, dropped signals and all until I put it back to stock rooted. Now it's fine.
——————————
Deebo took your bike too?
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
I've run roms and kernels since we got root. Never had a random reboot or any other problem for that matter.
Sent from my SGH-T989 using Tapatalk
no6969el said:
Yes I have had it more often on this phone though but it has been fixed by wiping the proper things first then flashing. If not then you might need to redownload the file.
If that doesnt work then you need to make sure that the kernel you are using is compatible with the rom
Also make sure that you are using the proper cpu software for the kernel.. Setcpu seems to work good for most but on Juggernauts new kernel they highly recommend Fauxclock .
Click to expand...
Click to collapse
The only thing I'm worried about is if I continue to wipe and reinstall these customs ROM's that this issue could worsen, but you said that Fauxclock was highly recommended for Jug's Rom? I should try that out myself.
I've always done exactly what was written on the Instructions themselves.
But as for now. . I did a full wipe.. including my SD and the USB data and did a practice call for roughly an hour with me playing games and surfing. So far, there has been any problems. I hope this is perm!
I'd hate to waste another $500 phone D:
As far as the problem kernel with rom etc..
I am running Jug's rom straight. No different kernel's nothing.
I just had it happen to me last night. First time on this phone it has happened. It its stock, rooted. Happened while I was paying music in the car. My other phones with custom roms used to do it all the time.
I wonder if this has happened to anyone without ANY mods on their phone? =X
Fix Permissions
What exactly does that do?
jangst123 said:
Fix Permissions
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Sighx said:
I'm not sure if this has happened to anyone else..
However, this seems to be an ongoing issue with me and Android.
I've had the X10a and Nexus One .. both after only rooting it and using a different rom. While making phone calls and charging.. my phone would reboot..
Or playing a game on the phone.. it would reboot. I basically couldn't do anything without the phone rebooting. Which was sad.
Now with the Galaxy S2X.. This very same issue just happened to me moments ago.
Should I have never rooted it or changed the rom in the first place?
It was running very well before I decided to do so.. even while charging and talking on the phone.
Its funny because it just happened while charging.... I'm not even on the phone myself.
Does anyone seem to have any problem with this when using custom ROMs?
Because if this is true.. then I guess I'll flash the stock kernel and stuff back on the phone just to HOPE it doesn't occur then. :/
Click to expand...
Click to collapse
Are you overclocking?
I am running jugs rom. Before I cleaned everything I did move a lot of apps to SD. Maybe that cause it but as for now I have no.problem. definitely report in the future should there be anymore.
AllGamer said:
none, with Juggernaut, they did an excellent job
yes, with stock ROM
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
jabela said:
Reviving old thread... I have a completely stock S2X running 4.0.3 and it randomly reboots or shuts itself off.
I'm trying to figure out if it's a wayward app or a hardware problem. Thinking of rooting and removing the bloatware.
I also saw that it could be a faulty power button, but it also happens by itself, sitting on a desk.
Click to expand...
Click to collapse
Root try new rom and kernel see if that fixes it.
Did anyone find any solution? everything in this thread failed for me ..
Have you tried updating to jellybean? Mu phone used to randomly reboot on 4.0.4 probably once a day, and hasn't done it since I did. I am on stock rom.
Sent from my SGH-T989D using Tapatalk 4 Beta
I have a problem that I can't seem to figure out. It started when I first tried the SOS rom with Lionfish. At first everything on my evo was running amazingly smooth. Then out of nowhere My phone started lagging like crazy. Sometimes my screen would take forever to wake up after I pressed the power button. The capacative buttons would light up but the screen would take a few seconds to come on. Sometimes it wouldn't come on at all. I decided to just wipe and try Synergy rom (my current rom) which is supposedly very reliable. After a few days the same exact problems started occuring again. I'm wondering if Lionfish is the issue? Has anyone had a similiar experience? Any help would be much appreciated.
Lionfish is undervolted. Just flash a stock kernel and troubleshoot yourself. Not all phones handle undervolting the same.
fitz420 said:
Lionfish is undervolted. Just flash a stock kernel and troubleshoot yourself. Not all phones handle undervolting the same.
Click to expand...
Click to collapse
Ok, I'll try and see if that works.
Hey all good morning, what a messed up way to start the morning. So I was on my phone paying some bills, reading some manga when it powered off on me, I thought this was the known random reboot you get when flashing CM10 sometimes so I paid it no mind, however the phone has still not turned back on. I've done battery pulls, tried to boot into recovery or download and nothing is working it's just dead. I definitely didn't do anything this morning, flashed no roms nada and it had full charge shoot it was plugged in to my work computer when it happened. Someone, anyone please help me, I have the toolkit on this computer and can download anything all I need is instruction. Please help and also I've wanted the CM10 rom because I like it but it doesn't seem ready to be my daily driver as I'm having issues and have flashed different versions with it seeming to get worst while getting better. What does anyone recommend for a safe daily driver, stable, no reboots, crashes and still can be played with like CM10 for features somewhat?
Shels said:
Hey all good morning, what a messed up way to start the morning. So I was on my phone paying some bills, reading some manga when it powered off on me, I thought this was the known random reboot you get when flashing CM10 sometimes so I paid it no mind, however the phone has still not turned back on. I've done battery pulls, tried to boot into recovery or download and nothing is working it's just dead. I definitely didn't do anything this morning, flashed no roms nada and it had full charge shoot it was plugged in to my work computer when it happened. Someone, anyone please help me, I have the toolkit on this computer and can download anything all I need is instruction. Please help and also I've wanted the CM10 rom because I like it but it doesn't seem ready to be my daily driver as I'm having issues and have flashed different versions with it seeming to get worst while getting better. What does anyone recommend for a safe daily driver, stable, no reboots, crashes and still can be played with like CM10 for features somewhat?
Click to expand...
Click to collapse
I've been using ths 08/14 CM10 rom on a full wipe without much issues, but have come accross your issue on an old CM9 build last month.
For me to get the phone to boot, I removed the battery and powered it on by AC only, and then poped in the battery, and haven't had issues since.
Do you do any overclocking or undervolting? You say CM10, what release? What kernel?
Hopefully we can get your phone working once more
jeb101 said:
I've been using ths 08/14 CM10 rom on a full wipe without much issues, but have come accross your issue on an old CM9 build last month.
For me to get the phone to boot, I removed the battery and powered it on by AC only, and then poped in the battery, and haven't had issues since.
Do you do any overclocking or undervolting? You say CM10, what release? What kernel?
Hopefully we can get your phone working once more
Click to expand...
Click to collapse
Thanks for the support, I'm not sure what happened but I just saw the samsung logo and it's booted up, so now it's up and running but that kinda scared me lol. I know what you mean jellybro hasn't given me much problem before which is why I've picked it over others but this now scares me lol especially since I actually formatted my phone last friday and had to start from scratch, so was worried it was a repeat without me doing anything lol. I'm using the 20120813 release and the kernel that comes with it, I haven't played with kernels at all, is there a kernel I should look at? And I don't overclock per say I may switch the cpu performance to "performance" from time to time but that's it and no undervolting I try not to play with things I don't understand too much lol
I'd recommend you to hop on the new 08-14 official CM10, now that cm9 is released, i would imagine seeing many more frequent updates from Cyanogen himself.
I was using Jellybro and got random crashes, but so far no issues with 0814 cm10. Just do a full wipe, dalvik wipes and dirty flash cause more issues than its worth, especially with Titanium Backup you do a one click restore, and get a sms backup tool. Simple clean switch. Just make sure not to copy system data with TI, which would give you the same results as a dirty flash.
Sent from my SAMSUNG-SGH-I747 using xda premium