Related
Ok, I'm finally reporting this Uber annoying problem.
My phone will just lock up for anywhere between 2 and 15 seconds. I thought this was maybe a bad backup from titanium, so I stopped using it. I cleared my SD card, I've tried multiple roms, I'm formatted everything including SYSTEM during each different ROM install.
It seems the issue happens after I use SMSBACKUP+ to restore my txt messages. *EDIT But I've had it happen without installing SMSBACKUP+ EDIT* Handcent has been force closing on me for weeks as well. I just removed Handcent, and installed ChompSMS. The problem is still happening.
It happens very randomly, and without any cause that I can tell. I'll hit the power button, and unlock the screen, and then the touchscreen is completely unresponsive for seconds at a time. The touch buttons (home,back,etc) are also unresponsive. Then all the sudden, the phone will try to catch up to every one of my touchs.
Also, whatever it is is killing my battery. Yesterday I installed MikFroyo, and the phone was good for over 12-15 hours. Then I charged it, and something in the past 2 hours caused the issue and completely drained my battery in those 2 hours.
I've had this problem with
FreshEVO (multiple versions)
SprintLovers
Burnt Droid (multiple versions)
Ava-Froyo
OMJ's EVO
BakedSnack
I've also tried ASOP mods like MIUI and Cyanongen Mod, and as far as I can remember, the problem didn't happen with them, but I really would like to have my 4g work.
I just want my phone back!!!!
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
First backup your apps and data. Then flash calkulins format all, then flash your rom and start from there it should work
Sent from my PC36100 using XDA App
I've been using calkulins format all for the past 2 weeks (7 flashs)
teh roxxorz said:
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
Click to expand...
Click to collapse
I've used every kernel I could get my hands on, thinking it was the problem. I've been using stock kernels for the past 2 months now with the same problems.
I just haven't heard anything else bad about SMSBACKUP+, but I have read some issues with locking up, freezing etc regarding SMS in general.
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
davidc23 said:
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Been there, done that about 50 times too. I'm just gonna go without HandCent for a few days and a new ROM install and see what happens.
Have you had any other complaints about this?
None, what's your hardware version
Sent from my PC36100 using XDA App
davidc23 said:
None, what's your hardware version
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Current
HW: 0003
MikFroYo 4.5
2.6.32-17-gee557fd [email protected] #15
3.70.651.1
Are u using setcpu
Sent from my PC36100 using XDA App
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
EDIT: Also, what PRI version and Radio/baseband version do you currently have? The latest? 1.90 PRI and 2.15.00.11.19? If you are on the 1.90 PRI, try downgrading it to the 1.77. The 1.90 PRI is definitely known to cause issues that you speak of on some phones. Just anothing thing to double check. Here is an attatchment of the 1.77 PRI. It sounds like you don't have anything to lose by trying. Everyone's phone acts differently with different software and what not.
davidc23 said:
Are u using setcpu
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nope... Complete stock roms, with little to no apps. I can only think to point at bad hardware, the base sms operation, smsbackup+, handcent, or titanium backup. All of which I'd had issues without one or the other installed.
k2buckley said:
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
Click to expand...
Click to collapse
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
4g still scans
Sent from my PC36100 using XDA App
mintee said:
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
Click to expand...
Click to collapse
Check the Edit in my previous post as well
k2buckley said:
Check the Edit in my previous post as well
Click to expand...
Click to collapse
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
mintee said:
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
Click to expand...
Click to collapse
Dang!! That's an old radio / pri combo! I've never rolled back that far, so can't say much about it, but are you sure that's not contributing to the issue? Maybe it doesn't like the 3.70 build.
Sent from my PC36100 using XDA App
Does anybody have any idea what would cause my Epic to shutdown several times a day and won't power back on without pulling the battery. I have tried doing data factory resets, Odin back to stock, different Roms and it keeps doing it. I've purchased a new battery and it still happens with the new battery. Anybody have any ideas or words of advice to help me fix this problem? Thanks in advance.
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
downyours said:
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
Click to expand...
Click to collapse
Yes its rooted. I have never messed with clock speeds, so it shouldnt be an issue with that I hope. Ive also tried wiping the battery stats as well in CWM. It first started when I flashed Syndicate Rom Frozen a few weeks ago. So I have tried several other roms since then and I still have the same problem. I even purchased a new battery and still have the same issue. Im lost in this one. Im not blaming the problem on Syndicate either, I was just letting you know when I first noticed the problem.
Sent from my SPH-D700 using Tapatalk
What happens when you open the keyboard? Does anything light up? Or does it just continue to stay off?
It stays completely off and blacked out when I open the keyboard. I have to pull the battery in and out to get anything.
Sent from my SPH-D700 using Tapatalk
And youve gone completely back to stock without root. No difference?
Also, the kernels that you have run, are they overclock kernels? What about the one your running now? If so, I think they are overclocked from the get go and possibly set for 100mhz on the low end. You might want to try and find SetCPU on the website here, (there is a free one) and set it to raise the speed on the low end. Also add a profile for screen off that changes to 200-400. It would be free and relatively easy to try.
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
dazednconfused1144 said:
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I might be wrong, but I think the newest ViperRom is set by default at 200-1000. To reach the 1200 mark, you have to use SetCPU. Same for going under 200 (which is known to cause problems for some folks when the screen turns off).
I just wanted to say thanks for the help. I wanted to update you and let you know I finally found the problem. For some reason it had something to do with restoring my apps and data through Mybackup Pro and Titanium. I finally just started taking out different steps of what I was doing and finally just downloaded all of my apparently directly from the market and the problem went away. No more blackouts. I don't know why that would cause that problem, but it did. Thanks again for all of your replies and help.
Sent from my SPH-D700 using XDA Premium App
I think ever since I started flashing EB13 or EC05 based roms and kernals, I been experiencing thi stuttering lag and when I check setcpu, it stuck on 1200mhz clock no matter what governor its on. while this is happening, if i hit the home button, it wont go back to the home screen, just pop up the recent app window. this is an on and off issue and I dont know the root of the problem. When everything is smooth and no stuttering lag, the cpu clock is adjusting fine when I access setcpu. Any solutions or idea why this is happening? If their is a app to record the screen as a video, I will definitely upload the video or record the phone with my other working epic.
Mine used to do that back on frankenstein
Now on the acs rom (forgot which one lol) works fine
Sent from my SPH-D700 using XDA Premium App
Well I never experienced this on any of my past ROMs,but with EC05 SRF base ROM I've been working on,this happens to me aswell. I'm already trying to narrow this down,I think its kernel based also (EC05 code).I have a problem with popping and static when scrolling,but I can also be listening to music with phone in pocket,and hear it lag every so often,and not at certain intervals (1 hour,2 hour) so its nothing syncing with FB or whatever that's causing the problem. So I'm pretty sure its a kernel based problem. I'm working on a DK28 kernel ROM,stay tuned... What I can't believe is that no other devs admit or see this problem,only users. But I'm sure the wheels are turning,but since I can't code yet,I'm gonna do it my way,hack up a ROM Frankenstein style
Sent from my SPH-D700 using XDA Premium App
U can try "no-frills cpu control" works for me
Its in the market
Sent from my SPH-D700 using XDA App
glad im not the only one with this issues. happens i think the most when i make any changes with the system.
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