Since it seems Cyan has halted release of cyan 11 nightlies for the Atrix HD (indicative of what, I'm not sure), I figure it's worth solving this personal issue now; since it will most likely require another factory reset and I'd rather do it now.
Since day one of using custom ROMs, I've had the issue of my phone randomly crashing. Despite previously using only stable cyan releases, making sure to do clean resets (factory, dalvik, formatting system partitions,etc), letting the phone "stabilize" after installing (no clue what this means, but people seem to suggest just letting the phone sit about 10 min after flashing a new ROM, claiming a more stable experience), and even flashing a new kernel, I still see the same issue.
At this point, I've pretty much accepted that more likely than not, I'll have my phone randomly freeze and reset in my hands during basic use, calls, texting, internet use, listening to music, etc. Though clearing the Dalvik cache seems to quell the problem, it soon returns to the familiar behavior a day or two later. Any other basic solutions I might be overlooking? Suggestions, even obvious, very welcome.
CM11 switched to unified builds for the Moto 8960 family . http://www.cmxlog.com/11/moto_msm8960/
You can safely download a zip and dirty flash it over your current CM11 installation. At least that's what I did and I'm having possibly the smoothest experience so far on this phone/CM combo running Sat March 01 nightly.
About your crashes, do you get a phone freeze with signal loss before restarts? Do you always get a restart when the phone crashes?
Did you try enabling 2G only for a while? Do you crash while on WiFi?
You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.
Thank you for the link to the new unified build. I've been busy with approaching midterm that I'd only heard of the new builds but didn't look into it personally.
As for the freezing. It's always been the same behavior: screen and all function buttons suddenly becoming unresponsive with no warning or change in signal (regardless of wifi or data use) remaining frozen for 10 to 30 sec, before returning to the unlocked bootload warning screen and the normal cyan reboot animation and normal lock screen after.
Everytime is has froze it will restart (i suspected a memory issue at one point, but after watching the memory usage long enough to see it randomly freeze but no change in mem, I doubt that it's directly the issue). I have not tried switching to 2g, so it would be worth a try. It will freeze regardless of whether wifi is off or on.
The only real "pattern" I could argue seeing is that it freezes most often during skype calls, while playing music (pandora and play music), and internet using browser; though it might only be because I'm actually paying attention to the phone while it is doing these tasks, I'm sure that it's probably freezing and resetting in my pocket thoughout the day. It will also randomly reset while looking through settings or non-data dependent tasks. Ironically, I've never had it reset on me while I was watching a youtube video. Go figure.
audit13 said:
You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.
Click to expand...
Click to collapse
Any ROM, stable, nightly, cyan or other, with still see it start randomly freezing and rebooting an hour to a day after flashing.
-update*
After having switched to 2g signal instead of LTE, I haven't seen anymore randomly rebooting. I'm not sure if this was the issue but it's already been a day which is longest I've seen it remain stable.
1 Week later, back to the same behavior as before. Seems I might just screwed for having a stable modded phone.
Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
[Q]
Out of the blue my Bionic just started rebooting. 8-10 time per day, who knows how may time at night. I am using the stock ROM. I am looking for a stable ROM that I can use to fix the problem. I also have the problem of disapearing apps that I move to the ext card.
Feedback on possible cures will be welcomed.
I just experienced my first unexpected reboot. It was after plugging in my USB to my computer.
This seems like the sort of thing that would have a 50% chance of being related to your hardware, and a 50% chance of an unstable app screwing something up. The stock software is at least stable enough that it's not very likely to be the cause of your issues, and flashing another ROM (which will have the same kernel) won't help if it is a hardware issue.
A factory reset followed by staggered reinstallation of apps (one or two at a time, to see if one in particular might be causing issues) would be my first step for a problem as extreme as random reboots. The next step is through warranty channels. I might even do that first- I don't think I could put up with a phone that rebooted on me.
And the cure for disappearing apps is to not use media area for storage. The phone dedicates 4gb for apps, that should be more than enough until they patch a fix.
i may have to add that my phone was completely stable until i purchased and installed the extended battery then i started to experience reboots and a few locks here and there.
i did a few factory reset on the stock but the phone was still acting up with the new battery.
i then decided to root and run roms and to be frank no locks and or reboots running the same battery that seemed to be causing the problems based on that being the only change to my phone before the reboot and locks.
i am not saying that there is something there with the stock as there would be more reports on this but rooting and going back to stock is a single click now making it a fast process to trouble shoot the software.
i am experiencing a bad or short life with the extended so in my case it could have been the battery screwing up the reads on the software (guess) but the first 3 charge from full to dead just about 3 days after that same extended only last one day.
in general it seemed that my issue could have been a bad battery and wiping data and playing with roms may had help but in the end i will be calling verizon for a battery replacement as i doubt that in two weeks the battery charge for an extended could only last 1 day of medium use.
sorry long response and by no means i'm i encouraging to root and rom just speaking out of my experience.
Hi - first post here. After 4 Thunderbolts - Verizon sent me a Bionic. Much better however, after rooting with 43v3r and de-bloating with The Black Hat App - I'm having random reboots. Initially, the reboots were several times per day increasing in frequency to several times an hour. Y u c k - My Thunderbolt could do that too.
So in troubleshooting:
1 - I've reverted to stock build - no add'l apps: No reboots in 48 hours. So - I doubt it's hardware.
2- After reverting - I then rooted w/43v3R, then debloated - just using stock apps - no reboots in 24 hours. So, I really doubt it's debloating or rooting
3 - After adding a few apps - Stitcher, Enhanced email, SVOX w/voice, Beautiful Widgets (w/clock selected) - I get a reboot.
4 - Remove everything but stitcher. No reboots - 24 hours.
5 - Add Enhanced Email yesterday
Today, I had a reboot.
6 - So culprit 'looks' like Enhanced Email OR perhaps a switching problem between 3/4g (The Thunderbolt - Stitcher used to drop connection in this particular location so, there IS an issue w/3G-4G.
Questions:
1 - If it's not a 3g/4g issue; could it be related to where Enhanced email or Stitcher chooses to install itself?
2 - Is there a log somewhere where I could find 'boot' times and any issues relating to reboots? Like a 'minidump' in Windows...
thanks
I, too, have started having unexpected reboots. I can't pinpoint it exactly, but I have also recently isntalled Enhanced Email (trial version).
Reboot Logger
Hey Google is our friend - don't know why I didn't look before but I found this in Android Market.
"Reboot Logger" by Watanabe,Masayuki.
Just installed it - will report back after Thanksgiving (in the U.S. - Thursday)...
(I would post a link but I'm a noob here - and, now I know why I hate myself.)
Looks like promising -
Have yall installed any themes or different battery icons, or anything like that to yours? Mine is 43v3R rooted with the liberty romv2. I was changing a cpl of the icons and experienced a reboot just out of the blue. I got rid of the icons I changed and stayed with the icons that came with the liberty rom and have no issues at all. I do not have enhanced mail on mine.
most bionics will turn off and wont turn back on till you do a battery pull. Its a known issue, all you have to do is google it and it turns up. From what ive read putting the battery on performance mode and putting on detect in pocket will help. Personally it doesnt help, i had the issue with the stock battery so purchased a extended thinking it was the battery, but after doing research i found out it isnt. They say the new OTA should fix it
icons - reboot logger
Thanks - haven't changed any icons BUT I am using HTC Thunderbolt wallpaper. I had a Thunderbolt that had a reboot problem until the OTA before Gingerbread - Verizon offered me the Bionic when I called about my Thunderbolt issues (I had three replacements - all with the same issues).
I will try different wallpaper -
Reboot logger works well but doesn't offer a clue as to what is causing the reboots. Mine has rebooted 2-3 times per day since I installed Reboot Logger(RL).
3 times a day is tolerable but, I would like to get to the bottom of what's causing it.
What IS helpful with RL is that it does show that the reboots are not occuring in any obvious time sequence.
They may be related to push emails coming in from my Exchange server. Not sure - I'll post more as I learn more. Hopefully the upcoming OTA will fix - though my experience with HTC's OTAs does not give me a lot of hope.
Update - Last night, I uninstalled Stitcher - Stitcher frequently throws errors requiring a FORCE CLOSE. I also have kept Blueooth off.
No reboots in 24 hours -
Will reinstall Stitcher in the morning (I need it at the gym)...
Update tomorrow/Monday
Turned Bluetooth ON - no reboots in 36 hours so, It looks like Stitcher may be the culprit - I wonder if Stitcher has issue with the internal/external SD storage scheme.
As I noted previously, Stitcher reports 'force closes' frequently - especially when it's not even active (when I have not loaded it or used it).
(No sooner than I posted this - my phone rebooted. And again, and again will switch off BT - I'm in my office so, there's could be an issue with 3g/4g switching or other interference...)
Have you tried setting the phone to run strictly 3g? I have had no issues at all with mine jumping back and forth between 3g/4g.. I leave mine on 3g to keep it from trying to search for a 4g signal. I never turn bluetooth on, nor do I ever really use the compass. hmmmm... Can you tell me everything you have done to the phone. Apps you have installed, what ROM you using, if you have .886/.893 etc? I'm willing to see how close we are as for as how our phone's are setup and help as much as I can. I have not had a single issue with mine other then that one reboot after changing the battery icon.
After nearly two weeks of monitoring restarts - it appears that the problem is more related to where I am. At my home, restarts are rare and related to Stitcher.
At work in Beverly Hills, CA; restarts occur frequently. I assume it has something to do with 3g/4G switchover/crossover or interference.
I had lots of problems with the Thunderbolt dropping data connections in 90210. I could not use the hotspot. On the Bionic, the hotspot functions really well. I've used it up north near Fresno in 3G only land, here in BH and at home where I have decent 4G coverage.
When I remove Stitcher, the reboot problem disappears. Sometimes when I 'wake' the phone, there is a dialog apologizing for Stitcher having 'force closed' even if I haven't used it for days. Market reviews indicate anecdotally that Stitcher has a problem with force closes. This behavior must also be at the root of some of the reboots.
I've also set all programs not to update automatically - this may have reduced the reboots as well. On average, I'm getting 2-3 reboots per day. More than I would like but, tolerable.
This is a common problem between FroyoMod, CM6 and Chronos.
Whenever i make a call, i hear 2 secs, then the audio stops for 2 secs, then it comes back, and so.
Sometimes it's like when there is poor signal, it makes that bizarre breaking-overlapping sound, but the signal is very good, it's not the problem.
In FroyoMod if i re-flash the phone mod (modified phone apk) it works for the first boot, but if i reboot it wont work again.
In Stock Rom it works fine.
It's like a problem with crystalTalk, but the moded phone does not have crystal talk, so i don't know what to do to keep the phone working as a phone.
Once it fixed applying another overclock settings, lower values and normal voltage, but now it doesn't helps to any better even with stock clocks.
It's annoying because i have to decrypt what i'm hearing when talking to other people.
I really need help with this, can't post it on the roms threads because i don't have privileges.
Happening with CM7 too =(
don't you have data enabled?
I think it happen to me when I have a data transfer and recieve/initiate a call ... like having a non properly cleaned buffer ...
No, data not enabled, i don't even have a data plan, so i live wi-fi based, at work, school and home i have wi fi so i don't really need a data plan.
I did the same as before, wiped data caches before flashing, flashed chronos 1.9.0, it seemed to work, wiped data and caches, and then flashed froyomod, and it seems to work now.
It may habe something to do with the temperature of the phone? Today i did everything placing the phone over a frozen gel so it was cool and it worked at the first time, last time with the flashing, rebooting, etc, the phone was warm like after playing a heavy game.
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
I have this VERY frustrating issue, hoping someone can help. I just got a replacement Note 4 because my first one had faulty GPS hardware. The new N4 I have has this weird stutter, every couple of seconds it will stutter for half a second or so. You can see animations actually frozen in place for that half a second. Every once in a while the stutter will be several seconds and everything just locks up, but this is only occasionally, the other stutter is pretty constant.
I've flashed Dynamic Kat, I've also flashed it back to completely stock NK4. I've ensured I do a factory wipe, wipe Dalvik cache, complete format, etc etc in between flashes. I still get the stutter no matter what, and it's BEFORE I even install any apps, accounts or settings.
Just to add to the weirdness I installed CM12 nightly build last night and there was no stutters at all, none, not even a hint. BTW CM12 is a LOT faster than any N4 rom I've flashed, it's an amazing ROM but missing too many features to be usable at this time.
So is this maybe an issue with NK4? That's the only thing in common that I can think of. Anyone else?
I have the same issue. It impacts the keyboard as well
Flash AEL Kernel make sure it's the 6.1 version the 6.2 doesn't work for some reason.
I had the same problem, with the kernel flash it went away.
I'm sure you have done this but just in case, check the animation setting in dev options and set all three to .5 . In your kernel settings app get frequency logs and see what's up. I use the 6.2 with no problems with dk4. Try odin then back to stock then repeat. All else fails return device if you verify it's faulty.