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
Related
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
It might have been a bad flash. Try redownloading the rom and flash again. Also, make sure that you do not have too many apps installed. How much free space do you have on system?
The only apps that I had were the ones that came with the ROM itself, didn't download anything before or after flashing it.
may i know does this rom support audience cancelling noise?
thx
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
scrypt said:
I wanted to know which kernel is the best to flash with thi ROM other than glitch kernel that comes with the Rom.
The glitch kernel has a problem that you can't make a NANDROID backup with it. What other kernels does this ROM support can anybody post a link to one. I tried searching but couldn't find one
Click to expand...
Click to collapse
ICS ones, but the Dev thread tells that & more.
I don't miss Nandroid when I'm backing up with Super Manager, Super Backup for data, apks, call logs and SMS.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
When my screen first appears after a reboot it does that, too, shows half the screen, then the other half, but only for a couple of seconds, I figured it's because it's still reading media, loading widgets, screen, etc. Doesn't last more than 2 seconds, fortunately.
cOld1 said:
I looked at the posts in the dev section to see if anyone else had this problem, also noticed there is no Q&A for this ROM otherwise I'd post it there, I'd also post this there but I have less than 10 posts ;(. But around 2 days ago I flashed this ROM and all of a sudden the screen itself started to glitch, like half of the screen would split and disappear completely for a few seconds then reappear, then it would do it again but to the other half of the screen. Also restarted my phone to see if this would continue but it got stuck in a boot loop so I just flashed another ROM on the phone and it's been working fine so far, any ideas on how this happened? Would be appreciated..
Click to expand...
Click to collapse
Were you still running the Glitch kernel that installs with the ROM?
It's odd that it went from working to not working. It sounds like something changed something which caused a conflict or corruption... it wouldn't have boot looped otherwise.
If not had any issues like this...
It was a fresh install of the ROM itself, was running for ~ 5 minutes. I didn't install anything via the Market or anything like that....
Un-invert Calendar?
I like Doc's V5 ROM a lot. Best I've used so far. However, I don't care for the inverted apps and am using the "Revert Inverted Apps to Stock" tweak mentioned here. It works just as expected except for the Calendar app - it remains inverted.
Can anyone else confirm so I'll know it's not just me?
Does anyone have a solution?
Thanks!
Bob
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Anyone have vibration issues when receiving texts?
battery life
Battery saving settings - LiveOC 126%, MaxCPU=800*1.26=1008MHz. Nexus KB3 Modem. No deep idle sleep, no screen state settings, no internal voltage settings, ARM voltages are OC/UV. Power saver in ROMSettings enabled.
Boraltis said:
Only quirk I had with V5 was Gmail force closed constantly, even though I never use it. It would just notify me repeatedly that Gmail, an app I never touched, was force closing. Wiped caches and fixed permissions. It's been money ever since. Could use stronger battery life, but hey. Beggars can't be choosers.
Sent from parts unknown.
Click to expand...
Click to collapse
has any one experienced having a feedback loop in either your end or their end when using either the speaker phone or a headset?
Sent from my SGH-I897 using XDA
I am having an issue with the system time. It won't update automatically. Just gets stuck at a particular instance like 3:45 and won't update until I manually change the clock from 24 hours to 12 or vice versa. The happens after long sleep periods like two hours. After this the problem is persistent until I flash a new kernel.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
xThe Enforcer said:
Anyone have vibration issues when receiving texts?
Click to expand...
Click to collapse
Yes I am having this same problem no vibration with texts
no vibration with texts
Yeah. Same here. No separate vibration for SMS. But if you turn "Vibration only" system wide - it works for SMS.
Awkward.
scrypt said:
Yes I am having this same problem no vibration with texts
Click to expand...
Click to collapse
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Well anybody having an issue with time???please read my previous post^^ and tell me if it's sounds familiar , thanks
It happens when you switch a kernel as well? Try switching ROMs and see if it does it then go back to this, I haven't used this ROM since this incident ( OP ), using DK3 atm =p
b-eock said:
For guys having SMS problems with vibration. Go to SMS app, press the menu soft key, then settings, and scroll all the way down and enable vibration
Click to expand...
Click to collapse
I love you.
Sent from my SGH-I897 using xda premium
This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?
Sepharite said:
This is a common problem since the very beginning. The only way to stop it from occuring is if I leave it on Browser and put it to sleep.
I just installed the latest CM9 and the problem still occurs.
Is there anyway to fix it?
Click to expand...
Click to collapse
After the first time you get it to sleep without rebooting, you can turn off the screen at any point without a problem, right?
Try raising up the minimum clock speed to 384 and see what happens.
Minimum cpu was already raised. I changed the schedule to deadline,let's see if this works.
Sent from my GT-I9100 using Tapatalk 2
Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.
I have the same, or similar problem
allstar319 said:
Caches were cleaed upon installing the latest nightly? Used to have that problem with some of the very first nightlies, TP would reboot upon turning off the screen, clearing caches fixed that.
Click to expand...
Click to collapse
I have the same, or similar problem but unfortunately have not found a fix after trying every possible remedy from clearing the cache and upping the min frequency to a complete uninstall with acmeuninstaller . Clearing the cache may fix it for a small amount of time but it always seems to come back. I tried upgrading with both goo and with CWM thinking one may be missing something but both have the same results.
I managed to trace the problem to wifi turning off when sleeping for me. If i set wifi to stay on during sleep it does not happen, if I use a widget to go into airplane mode on sleep it does not happen but if i set wifi to turn off during sleep it happens. It may take a day or two to manifest but it always seems to come back.
I finally ended up using the 7/7 nightly because it doesn't do it and i dont feel like finding the exact nightly that the bug manifested in. I know it was after 7/7 and prior to 8/9. It is a pain as the 7/7 has some lag not found in the later nightly but if the choice is lag or greater battery drain, I choose lag.
Anyway..... Sorry to jack your thread. I feel for you, the reboot on sleep make the TP unusable. If you do manage to find a fix because i still search the forums hoping to see something i haven't tried yet.
Making the cpu scheduler to Deadline fixed the problem so far.
Sent from my GT-I9100 using Tapatalk 2
same problem
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?
esemudeo said:
hello guys,
I have the same reboot-problem. I tried almost anything...
@Sepharite
Is it still fixed with cpu scheduler to Deadline?
If yes, how did you do that?
I just installed the app "No-frills CPU Control" und turned the cpu scheduler to Deadline, but it still reboots.
I have only no reboots, when I'm using the touchpad after booting for a while.
Anyone has an idea?
Click to expand...
Click to collapse
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2
Infinite Jest said:
I've had the same problem for months. At this point, we may have to live with it. I find that if you let the device time out of its own, about 80% of the time it won't reboot again. It definitely serves as a reminder that we aren't in stable build territory yet (though, some people apparently don't experience this).
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer. I have to ask, you don`t have this problem anymore?
esemudeo said:
Thanks for the answer. I have to ask, you don`t have this problem anymore?
Click to expand...
Click to collapse
No, I still have this issue. I just live with it and try to minimize rebooting (which in have to do every couple of days anyway, thanks to match some point all of my apps crashing a couple of times when I try to open them unless I reboot.)
hey guys, good news.
User Sohip wrote in another thread, he also had reboots, but after he disabled the lock screen it stopped rebooting.
So I disabled the lock screen, and it seems to work. You should try it.
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
oh, now I get reboots again
---------- Post added at 11:00 AM ---------- Previous post was at 10:27 AM ----------
By the way, just in case, somenone tries ot fix this reboot-problem.
When the touchpad goes to sleep, it makes a „click“-sound, and then it reboots.
At least my touchpad makes a „click“-sound.
I haven't had a lock screen for months and the problem has persisted.
Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.
Post a log. Which ROM where you on before flashing CM.
sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2
CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!
I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.
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.