I first started using CM at 6.1.2. I'm now on CM7 RC2 and the same problem still occurs. I have no idea why this happens but I'll provide as much info as possible in the hope that someone will be able to figure it out.
My phone will work completely normally for several days after I initially flash CM6.1.2 or CM7. After a few days, a crash will occur where the screen stays on but the phone is completely unresponsive to all input -- touch, softkeys, or hardware keys. The power button stops functioning. After a while, the screen dims and the phone reboots. After the reboot the phone chugs along for a few hours and then the same thing happens. This crash almost always occurs in the Browser, in the middle of loading a page. I don't think it's a memory issue because I consistently have ~100MB free for RAM.
Also, I don't know if this is at all related, but I often notice just before the crash, the haptic feedback from the phone for keyboard presses and the softkeys becomes very erratic and inconsistent.
I can never get a logcat because the phone restarts after the crash. Has anyone else seen this or know what might be the problem? Again, this has been happening all the way since CM6.1.2 (and possibly earlier, I haven't tried anything earlier than 6.1.2 though). This is driving me pretty crazy, and I really love CM and would like to continue using it, but this is kind of a dealbreaker.
Did you wipe between flashing CM6 and CM7?
Yes, I always wipe data/cache/dalvik between flashing.
3 days ago I found that pressing the home button didn't take me to my home screen, but just briefly flashed black, but stayed on the home screen. It vibrates so the button is recognised as being pressed.
Rebooting fixes this issue, but it does come back (seemingly randomly).
CM 7-11162011-NIGHTLY-DesireHD, LordMod kernel.
Has been totally stable for months (haven't flashed anything for about about 2 or 3 months, now that I've found I'm totally happy with CM7 and that there are no new nightlies)
http://androidforums.com/droid-x-su...92-home-button-just-flashes-black-screen.html
This thread describes my exact issue, but ADW-Launcher can't be cleared as default, presumably as it's my only launcher. Restarting adwlaucher doesn't fix the issue, but a reboot does.
Please help me fix this!
Have you tried clearing the app data? Maybe wipe cache.
There is actually new nightlies just not from the buildbot. A few people are syncing to the repo and uploading new builds everyday
I don't have a real need to get new nightlies tbh, CM is doing a fab job at the moment, though I can't say I'm aware of what's changed so maybe I'm missing out!
After going crazy, literally trying everything, it seems Tasker is to blame. I've got a rule that says lock the screen if the proximity sensor is set off. If I experience the problem, disabling and re-enabling that rule solves the issue.
I really can't think why that'd be though?! Especially as the proximity sensor is not being set off at the time the issue starts.
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
gaveup said:
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
Click to expand...
Click to collapse
It's quite possible that your phone isn't handling the 3.4 kernel very well. Although, did you try Task's last update (4/9)? I haven't had lockups on the last couple builds.
But if you keep getting them, revert back to a 3.0 kernel/ROM build until 3.4 is more stable.
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Ksenios said:
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Click to expand...
Click to collapse
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Azhery said:
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Ksenios said:
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Click to expand...
Click to collapse
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Azhery said:
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Some time ago I had OmniRom and after few OTAs I actually started noticing similar issue if I recall correctly (that was the reason for me to switch back to CM).
mybe u try..full wipe..wipe data..wipe cache..wipe system..wipe internal storage..
Sent from my GT-N7100 using Tapatalk
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Ksenios said:
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Click to expand...
Click to collapse
mybe u can try other rom like cyanogenmodx..bcause i nver had this issue..
Sent from my GT-N7100 using Tapatalk
I was actually thinking about it, but as I said, when I used OmniRom few months ago, I recall that I had similar issues. Nevertheless thank you for your insight. Anyone have any slightest idea what might be causing such behavior?
I seem to have fixed the issue. Turns out the culprit was Business Calendar - Business Tasks to be more precise. I unistalled both and so far didn't experience those wake up lags.
Hello all
I installed cm12 nightly and I'm stuck with a setup screen where I have to choose language and WiFi, I select them and then I have a 2nd select WiFi screen
How can I solve this ?
Thanks
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Well I can't skip through it because it gets stuck at the 2nd network detection, probably provider selection but I never get there.
It's the Cm account app, why they need an app for that is beyond me but if it is not solved soon I'll move along to another rom....
In the meantime i'm still looking for a fix
Thanks
apuntigam said:
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Click to expand...
Click to collapse