Related
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?
Using the unlock button doesn't always make my screen show up. Yet, the lights for the four buttons at the bottom of the screen. Sometimes, the screen even comes up but it keeps flickering.
Is this a known issue?
LGS1231 said:
Using the unlock button doesn't always make my screen show up. Yet, the lights for the four buttons at the bottom of the screen. Sometimes, the screen even comes up but it keeps flickering.
Is this a known issue?
Click to expand...
Click to collapse
Please read the posts in the Gingervillain thread. Are you OCing?
Going through what I can of the 50something pages of the thread. And yes, I am overclocked.
Props for trying man, everybody appreciates that.
Um okay, that actually might be the problem... What are you OC at? Are you using the screen on/off animations? Are you using SetCPU?
Try to take your OC down a notch, one step at a time, and try switching the screen on and off each time to see how much you can OC and still have the screen functioning normally.
So flashing the CM7 Gingervillain ROM, there was already a kernal built in but I only maxed it out at 1401mhz. Yes, I am using SetCPU and I'm also using the custom profiles.
I'm pretty sure that 1401mhz is at a stable level because 1497mhz was even tested to be pretty stable.
I see that you are running the same ROM, but since you haven't mentioned having a similar issue, I assume you don't have this issue? I'm just scared that one day the screen won't be turning on at all.
I am currently not OC'd, since I personally don't feel the need to be. But as you can read in the other thread, overclocking has provided screen problems for tons of people. There is no border that says "Okay now your screen's gonna start acting freaky", it differs for almost everyone.
I tested it myself a while ago: I had no problems up to about 1,2 GHz, but when I mine to 1,4 or higher I had the same issues.
But like I said, it all depends, there are people who are OCing at 1,5 and have no complaints..
Overclock to 1.2 area and let us know what's up
Sent from my HTC Vision using XDA App
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
If you're using setcpu, raise the screen off clock speed.
Texted while driving
Thanks for the suggestion. I am using set CPU. I looked and can't find that setting. How do I get there?
I am getting the same thing on different ROMS. Specifically the latest Midnight and Syndicate ROMS, which are the only two ROMS I have ever ran. It just started this out of no where as well. I was running Midnight for over a week with no issues, and then yesterday it started shutting off multiple times. So, I wiped everything three times, and flashed Syndicate last night, and then this morning it started doing it again. I just Odin'd back to stock, and am going to see how it runs before rooting and flashing again. I would love to hear what could be causing this issue.
I've been having the same issue. I've had it with the latest Syndicate ROMs, Bonsai ROMs, and Midnight ROMs. It's been very frustrating as I've only been able to reproduce the issue after using the phone for a day our two. It only happens when on battery power and when the screen has been off for several minutes. I've always ensured Set CPU is set to minimum 200 mhz and I've also had the issue without set cpu installed, so I don't think that's it.
I've been doing lots of testing to determine what might be causing it and so far I've eliminated the kernel and ext4 as the culprit. I think it must be some relatively new tweak that all the custom ROMs are implementing. My latest theory is perhaps the NCIQ tweaks.
Thanks so much for the input. Hopefully someone can figure this thing out
Sent from my SPH-D700 using XDA Premium App
mpscmedic said:
I have been having an issue with my phone shutting down on me. When I put it in sleep mode, and after a while try to turn it back on, the phone is completely shut off. The only way to turn it back on is to pull the battery. When it is plugged in, it never does this-even in sleep mode. This is also not ROM specific, it has happened on several different ROMS. Does anyone know how to fix this issue? Thank you for your help!!!!!!!
Click to expand...
Click to collapse
I experienced the same issue, and reported it in the Bonsai 4.0.1 thread, as that's the ROM I'm using. I would defnitely like to know about the solution, as it is quite frustrating when this occurs and it does not allow using the phone without the battery power cycle.
Sent from my SPH-D700 using XDA App
Data corruption
I, have found it is best to fully wipe everything.
I installed srf and got freezes and random reboots.
Then i installed cm7, and re-flashed srf from that not a problem since.
This issue has been discussed before,and i suggested this remedy to fix the ailments.
It is tedious but it works just fine.
Not sure what the problem is, but you probably came from an EC05 stock rooted ROM.
I think that is the underlying cause of these problems.
fully wipe your phone 3 times wipe everything flash cm7 ,you dont need to flash the gapps then flash srf or bonsai and watch them run.
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 just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?
Using it the last few days w zero issues. Which one are you using and how did you flash?
Sent from my SPH-D710 using xda app-developers app
I just installed it myself yesterday, but all has been good. I haven't had any of those problems. You probably should download it again and flash it again.
kdubhotsauce said:
I just recently installed CM9 alpha 6 on my Epic 4g Touch but ever since my phone restarts so much! Its just super buggy and it acts as if im holding down the power button showing the options for Reboot, Airplane mode, etc. After that it restarts. It will does this almost constantly to the point where the phone is barely usable. Anyone experience similar issues? Any suggestions?
Click to expand...
Click to collapse
Really stupid question, but did you use "Calkulin's_FORMAT_ALL_for_E4GT" zip file before flashing CM9? I only ask because I have had issues in the past with other roms by forgetting to wipe everything beforehand. Even the savvy tech could forget something sometimes :silly:
I'm running the exact same ROM. I underclocked mine down to 800Mhz to save battery and it was causing constant restarts. I moved it up to 1000Mhz and they stopped. If you tried messing with the clock speeds that might have caused it
OP, did you fix your problem or did it just go away? I recently flashed mine to cm9 alpha 6 and am having the exact same problem. Never has this phone had problems before.