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
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?
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
That doesn't sound like a common issue, and it's possible you might have a hardware defect with your phone.
I'd flash it back to stock, or as close as you can find, and take it back to wherever it was purchased for a replacement or repair.
raulttro said:
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
Click to expand...
Click to collapse
mine does the same with stock, but its not that common it happens like once a week for like 2-3 secs, and you dont need to have apps running, i just took it as it is
I m having no such issues in my DHD and i have used ARHD since very early versions.
Are you using any programs like setcpu or cpuspeed? Which kernel are you using?
If you have your htcsense account on, it would be a better idea to turn it off as well. And finally you can recalibrate your G-sensor (settings ---display)
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Ah! ok...it is really a strange problem though, i would say. I never had this issue being touch unresponsive.
Yes of all the ARHD builds 2.0.15 is the best one, IMO. Well, the GB build is still in beta and it lags. The battery life is claimed to be slightly better though. But i could not live without search function (which FC all the time), the tweaks we have for Froyo builds and the overall user experience with froyo is just awesome...and Mike has done great job. At the moment the version i m using is priceless...
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
MattOsprey said:
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
Click to expand...
Click to collapse
You have a similar problem as mine, but not so often.
What do you mean by a serious problem? It depends if it is disturbing you or if you can live with it. It won't get worse as I've seen it is not a hardware problem.
You can do the test by installing CM7 ROM and check if it does again. For me that solved the problem, but as I like to use HTC Sense, it is not an option to stay on the CM7 ROM.
raulttro said:
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Click to expand...
Click to collapse
Just a really wild guess, which launcher are you using? As I'm using launcher pro plus and it has a tendency to freeze after restart and the screen has no response for a while, usually it force closes automatically and restarts instantly after and works perfect. I'm on CM7 latest nightly and haven't tried other roms for a while so it might not be comparable. So if you are using launcher pro then try to manually restart it if it doesn't force close itself and start again. And if you're not, well just ignore this
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.
After originally sending Tillus a PM as he had a similar issue with another ROM I thought I had better post here.
I have tried Oxygen, CM7 and Redux but I get this problem with all of them. Everything runs fine for a few days and then I go to unlock my phone and the screen stays blank. The keys light up but the screen stays just blank. Tried Back-Trackball-Vol down (as suggested in post linked to in PM below) but it didn't work. I then have to take out the battery and restart.
Once it starts happening the gaps between it happening get smaller and smaller. It has happened 4 or 5 times today alone.
First time, on Oxygen, my phone eventually wouldn't turn on any more and I had to get HTC to fix it under warranty.
Then I tried Redux where it happened after a few days. Someone on here suggested I look at the CPU settings. I did and saw that Redux had a power save mode, so I tried that and it seemed to work but after a few more days the same thing happened. Although this was after a reboot so perhaps the phone didn't retain power save mode afterwards.
On Sunday I loaded CM7. Worked for about 24 hours before the blank screens started.
Running ONDEMAND governor, Min 245 Mhz, Max 998 Mhz.
Any ideas?
Here is the PM I sent to Tillus for info:
Tillus said:
d10brp said:
Tillus,
Hope you don't mind me sending you a PM. I noticed you had the same issue as me (screen not turning on from lock screen http://forum.xda-developers.com/showthread.php?p=9652281#post9652281). Did you ever find a permanent solution? I'm getting this issue with Oxygen, Redux and CM7.
Thanks
Alan
Click to expand...
Click to collapse
Hi,
uhm, I think this was a specific Auraxtsense issue which was resolved eventually. I never experienced this fault again - neither in a later auraxtsense version nor in oxygen (2.0.3) which I am using now.
Are you overclocking your cpu? Maybe you set the screen-off frequency too low? Or are you using a undervolt-kernel with very low settings, especially in low cpu frequencies?
As I said, I haven't experienced this issue for a while now.
Click to expand...
Click to collapse
Did you try keeping the power button pressed for a few seconds? I know, it sounds silly
Are you sure you don't have this problem on a 2.2 rom? I don't see you mentioning it in your post. Only that you have this issue with 2.3 roms.
What kernel do you use? Try a SVS kernel, don't use a HAVS kernels for now.
Also are you sure you tried the latest version for let's say Oxygen? From the oxygen changelog:
v2.0.3
Fixed font bug introduced in previous version
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
Click to expand...
Click to collapse
I'm fairly new to this so I have only tried 2.3 ROMs since rooting. Obviously phone has been running official sense just fine on both 2.1 and 2.2 for about a year.
Also, apologies for this, but I don't know what the kernal is. Just followed the noob video tutorial. Is it Alpharev?
Haven't tried Oxygen since RC7 so I might try it out.
Seems to be memory related as just after I posted, something slightly different happened, I pressed the lock button and the lock screen appeared but then froze. After a couple of minutes the screen eventually locked again with a very slow jerky animation. So I have just removed a couple of apps that seem to be running all of the time, App protector pro and StumbleUpon. No crashes since then (2 hours).
Sent from my HTC Desire using XDA App
So that worked for about 2 days. Now thinking maybe it is the SD card. Ordered a new one.
I've been having issues lately with my Inc. Seems like its on sense ROMs, even stock. My phone will just freeze then reboot. Timing varies. What app I'm using varies. Flashed several ROMs, with full wipes. Even formated everything and started over fresh with a stock ROM. Still having freezes and reboots. It's getting very frustrating. Does anyone have any ideas? Please.
Sent from my ADR6300 using Tapatalk
freeze/reboot
Same here. Usually freezes and reboots at least once a day. Started probably about a week ago. Worked fine with the ROM/Kernel below for a good month prior. Only thing I can think of is I downloaded a bad update at some point.
Original Incredible
ROM - Wildstang 2.3.4
Kernel - 2.6.35.13 gingertiny-v2
Well,i has the same sort of problem...I took it back to the store to show the customer service reps and it never rebooted. About halfway home, it started rebooting again. Now I have to go back to the store.
countryfolk07 said:
I've been having issues lately with my Inc. Seems like its on sense ROMs, even stock. My phone will just freeze then reboot. Timing varies. What app I'm using varies. Flashed several ROMs, with full wipes. Even formated everything and started over fresh with a stock ROM. Still having freezes and reboots. It's getting very frustrating. Does anyone have any ideas? Please.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Try installing incredicontrol and over-bolting a little bit. The chips in these phones like a little extra push in their "old age".
Sent from SkyNet's Matrix in a galaxy far, far away, where no one has gone before...
chris7os said:
Try installing incredicontrol and over-bolting a little bit. The chips in these phones like a little extra push in their "old age".
Sent from SkyNet's Matrix in a galaxy far, far away, where no one has gone before...
Click to expand...
Click to collapse
Yeah, I've been tinkering, and I'm seeing that my phone doesn't like the lower voltages in Tiny's kernels. I am running Jermaine's stock+ right know and things have stabilized. So yeah, must be voltages. Just threw me off because I've been running Tiny's since he started. I haven't had a reboot yet on stock+ kernel. Thank you everyone for your input.
Sent from my ADR6300 using Tapatalk