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 was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
sniperwitagun said:
i was running Froyo on my epic for the longest time and i used odin to go back to 2.1 just recently because i missed how smooth it was. i noticed that no matter what i do, my notification light won't work anymore. even when the screens off. im running stock DI18 right now (unrooted) and i have no idea why it hasnt worked. any ideas? they would be greatly appreciated.
Click to expand...
Click to collapse
Weird, why not run Bonsai, midNIGHT or Viper 2.2 ROMs?
I have been using midNight for about 3 months (since I got my epic for xmas) and it is VERY fast with no lagginess what so ever
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
does it work if you odin back to dk28?
try it first and see what happens
musclehead84 said:
Mine didn't work on 2.1 either.
Sent from my Evo Killer!!!
Click to expand...
Click to collapse
Mine has worked on 2.1 stock, 2.1 epic experience, 2.1 noobnls rom and other 2.1 roms ive tried as well as now running bonsai..
i was running bonsai. i switch roms every day until i find one i like. ive run almost all of the dk28 roms at this point. i was running viper with the gingerbread theme with ext4 and i really liked that setup. but the notification led let me stealthily text at work or school so really miss it. i re-rooted my epic and put the latest epic experience for eclair back on my phone and ran phoenix kernel but for some reason the newer builds of that for me make my touchscreen unresponsive whenever it feels like it, so i went back to fluff kernel. however, the notification light still doesnt work. ive tried wiping the phone, using odin to go back to stock, ive tried third party notification led programs, tried playing with the stock settings, installing handcent again and playing with those led settings, and just about everything else i can think of. im thinking there must be something i can run in the terminal emu to make it reset or something. im a pretty avid linux user, but im no expert when it comes to android so this is something slightly out of my expertize. but from googling and browsing xda somewhat, its a growing problem. most people dont care enough to fix it though and like 75% of xda members with epics moved to froyo anyway.
Im currently running calkulins evio 2 rom v1.8
(however this is not a rom specific issue for me)
2.2
2.15.00.11.19
htc kernel #15
3.70.651.1
1.90_003
While using the phone sometimes in texting, when swyping words, in the browser, in apps, or otherwise.. the screen just.. with lack of better words, "WIGS OUT"
it twitches as if there were 5 other fingers or someone else tapping the screen near the top and the screen twitches and halfway slides, then will just become unresponsive.
To fix it I have to just turn off the screen, then turn it right back on and unlock the phone and its back to normal.
it happens, probably 1 out of every 5 times I unlock the screen and start sending a text. its really starting to rack up though since I use my phone all the time.
I can provide a lot of information,, but,. any ideas so far?
thanks for your consideration.
That happens rarely to me on CM7. Are you overclocking at all? Perhaps re-flash the rom?
since im on calkulins rom im actually underclocking right now.
im not using any governors including setcpu or battery savers, because the script and profiles are built into the rom.
That being said,
Today alone, I have ran EviO 1.8, MIUI 1.24, and warm TwoPointTwo
and this problem has transcended each change of rom...
...
that means its a hardware issue.. right?
:/
How long have you been on the roms? They can be laggy the first 2 days or so. Are you using the pre-installed kernel?
when it first started happening i was on warmtwopoint two and had been on it for probably 2 weeks. the other roms it happens the whole time, from the beginning.
its been going on for almost 3 weeks now.
when on warmtwopoint two i think i was using the preinstalled kernel.
on miui i was using netarchy #11
and the preinstalled htc #15 kernel included in calkulins.
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
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.