100% wake time issues - Hero CDMA Q&A, Help & Troubleshooting

I've tried several past version of DC and Freshhh and more often than not have encountered 100% wake times. A reboot never takes care of the issue and nothing looks out of the ordinary in spare parts, so a complete wipe and flash takes place. After reflashing Fresh 2.3.3, I realized a possible cause for the wake issues. I was able to recreate 100% wake times when using Titanium Backup (donated version) and running a batch restore.
My question is Titanium the real problem or is it just coincidence? Has anyone else had wake issues after using Titanium?
BTW, just want to thank the dev's and members of the xda community for all your help and hard work.
Sent from my HERO200 using XDA App

Related

[Q] Phone Unresponsiveness

Hello Community!!
I am seeing a problem with my Revo, and I'm putting it out here because you guys are good at finding answers.
I am running Gingervolt 1.3 with the blitzkreig kernel installed. I have previously tried Hicks' little ICS responsiveness script.
Here is my problem. Most days after little to moderate use, Phone/text, I have to reboot my phone by either soft reboot (power button) or a hard reboot (battery pull) because nothing at all is responding. By nothing I mean, touch the screen..nothing, open a program...nothing...etc.
It is a slow degrade sometimes where (and my wife has mentioned it using my phone) that the touch screen is really really laggy and non responsive, especially when using a keyboard or even trying to play angry birds.
I have done a full wipe including data, cache, dalvik. I have formatted my internal and removable SD card, I have not used previous backups, instead resorted to downloading programs and installing from scratch.
This is a very frustrating issue. If it was a computer I'd say either the processor was overworking, or the ram was used up. But since we don't use program killers in GB I'm kind of at a loss. And I'm tired of having to wipe my phone every few days just so I have meh performance (and no, I'm not hating on the phone, or the rom or any of the developers, nor do I have any interest in changing phones,etc)
I'm just looking for suggestions/solutions etc. I'm sure I missed something in my troubleshooting steps.
Thanks in advance for those who read through this and try to give a hand. I appreciate it.
Wow. Since you've already gone to extreme measures, I'm at a loss. My suggestion would be to freeze the apps you do install to look for a culprit there. Or, don't install any and see how the phone performs.
I restored a nandroid prior to Google's 10¢ apps promo and my phone is back in fine form. It was lagging badly before that. I was rebooting daily. Now I go for days and the phone's solid.
Sent from my VS910 4G using Tapatalk
I was experiencing similar issues about a week after updating to blitzkrieg 1.0. I restored from backup and it's been stable since. I just installed 2.0 today, so I'm curious to see if it'll have the same effect.
Sent from my VS910 4G using xda premium
I can't say yet whether or not 2.0 has added to or taken away from the response type issues. I did have to do a couple of battery pulls yesterday just to get firefox to do anything. I'm going to uninstall that one. I may, just for S&G's do one more factory wipe and put all the tweaks and mods in place before downloading anything but the most essential programs. I did this phone, but the unresponsiveness sometimes can be a real pain.
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
revo_65 said:
What do you have it clocked at? I have issues at 1.9 so maybe back it down a bit. I get lots of screen freezes and have had some rebooting issues at 1.9
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Currently I have it at 1.7, before when it was really bad, the oc wasn't sticking and I was at 1024, so not overclocked much. I am sure its an app that is causing the problem, but I'm not sure what.
I've never had this type of issue using Blietzkreig or any of the other tweaks so I'd guess you're right in thinking it's an app. Since you've pretty much tried everything else I would say maybe try going back to complete stock then rooting again? That just seems like what I would try if I had tried everything else and nothing worked.
And yeah you definitely don't want to overclock too much because it could definitely damage the hardware of your phone since it's not meant to run at that level. But you said you had it at 1.0ghz so it doesn't seem like that is the problem unless the damage was cause when running at 1.7ghz. I had mine at 1.9 and didn't see any issues except my phone randomly started to vibrate for a while then just restart. It did that twice when i first flashed everything but it seems fine now. I brought it down to 1.0ghz just cuz i'm not really using it now and I don't want it causing any problems with the hardware.
Thanks for the Feedback everyone. I am not sure what the issue is/was/going to be. I think Firefox was a big part of it and I have since removed it. But I am still getting random freezes, almost like the deep sleep while the screen is on. Oh well, maybe I do need to go back to complete stock.

[Q] Tried Everything - Touchpad Screen Unresponsive (CM9)

Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6
flash the latest nightly.
screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.
Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system
Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...
Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.
Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )
i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA
Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed
This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?
I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2
Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app
I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?
I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2
I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.
Bump - still no fix identified for this by anyone with this issue please?
To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android

SoDs and other reboot bugs.

Could some of you, who use CM7 please tell me, which apps you are using? Cause then I would do a fresh installation on my OB, make a backup and then you can try to restore it and see if you still have SoDs... Cause either those are due to faulty installations, buggy apps, you are using, or other things. Cause I never had any before (except in Zeus, where everyone had them). I really wanna try to figure out, if it is a CM7 error or if you guys make things wrong somehow... Tell me, if you wanna give it a shot
I don't remember very well, but i think i was using either twitter or foursquare, then i pushed the power button, phone did not respond after that. Also while charging.
Coulf anyone gimme a full list of the apps you are using? Cause the i could set it up and you could simply restore the backup and see, if it gets better.
Sent from my LG-P970 using xda app-developers app
After Byope's last kernel update no more SoDs or wakelocks

[Q] ROM's progressively get slower after each use

Quick one here, I hope. I flash a new ROM everyone few weeks or so and when I do it seems very fast at first then just starts to chug like no other. Happens with CM9, CM10, AOKP, Slimbean, helly bean, etc. I know it's not the ROM then. I do the standard wipe/reset and then flash the ROM, then flash the Gapps, then let it boot up and go from there. Not sure if I really need to wipe the cache partition, or cache, or davlik cache...but usually do. Why do they always seem to slow down so easily ?
I use a wiki widget, sound search, and the clock... nothing more and close apps out often. It just seems to chug when just navigating, or going through pictures, or just typing. Any ideas or good habits I should have ? Thanks !
Bad question? Anyone I can ask ? Thanks
Sent from my SGH-I897 using xda app-developers app
One thing that I found to help was to reboot the phone every night. I flashed often, so I set schedule in titanium backup premium to redo my backup every night, and then reboot the phone. This dramatically helped the rom slowdown.
Sent from my AT100 using Tapatalk 2
cheddleson said:
One thing that I found to help was to reboot the phone every night. I flashed often, so I set schedule in titanium backup premium to redo my backup every night, and then reboot the phone. This dramatically helped the rom slowdown.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
I agree with this. Also, all roms naturally tend to get slower after use. One reason they get slower is due to human psychology. We become used to the rom's speed, so it seems slower after a period of time. Another reason is all the data that is created after you start using a rom. During day to day usage of your phone, a lot of caches and personal data is stored, so they clunk up your system and ultimately slow down your phone. Rebooting deletes a lot of temporary caches and restarts services that may have started leaking memory, so it speeds up your phone.

FM Radio Issues

I mam using the latest Criskelo rom (11.2, iirc) and when I go to turn on the FM Radio via pressing the power button in the application, the light turns green and I can hear sound coming from the headphones for a few seconds then the 'green' light goes out and the sound stops. Rebooting the phone does not seem to resolve the issue. Any ideas?
You may want to try posting in that ROMs thread if you don't get an answer here
Sent from my GT-N7000 using Tapatalk 2
I flashed the RR JB release and this still seems to be an issue. I am wondering what to do now, since I am now reasonably sure it is not related to the actual ROM itself. I guess I could wipe and try setting up the device from scratch and see if the issue remains or returns, but I don't really want to go that route if possible. Thanks for your response.
You can make a full nandroid backup first and then if you do a full wipe and it doesn't fix it you can restore it...because honestly that is probably your first step to trouble shoot
You can also try a third party FM app like spirit fm
Sent from my GT-N7000 using Tapatalk 2
Wiping.
Yeah, I didn't want to wipe, but I think I might have to. I did a full nandroid backup. Spirit Radio did not help. I did a nandroid and then wiped and now the FM Radio works like a charm.
Yeah sounds like something with your old setup was causing some sort of conflict.
Try the radio after you reinstall each app so you can see if a particular app was causing the issue or if it was just some sort of corruption or other issue that occurred with the system
Sent from my GT-N7000 using Tapatalk 2

Categories

Resources