I just installed the cm10 11-25 nightly and wanted to report a bug. I tried posting it in the developer's thread, but I don't seem to have the right permission.
I've had a couple auto-restarts and a couple sleep of death issues. Also, every now and then, it will boot directly into the NOOK OS.
I upgraded from CM10 b3 is that helps.
Is this a known issue or something specific to me?
Thanks
It's a known issue to me. I have had a similar experience. I went from the nightly 24th to 25th and immediately had SOD. I power cycled it and tried again, same results. When it went sleep it SOD'ed. I have kept WiFi on Always from the beginning and through the 24th never had a SOD. My region is set to Europe (default I guess) but I live in South America. I reverted back to the nightly from the 24th and am back to full time WiFi and no SOD on wake.
EDIT-I waited until the 12/01 nightly reflashed and all is well. No more SOD.
Motherboard-QI08M910ZJ3
Man. Date 11/08/2010
OMAP3630 ES1.2
Touchscreen-cyttsp
Nightly 24th on the emmc
Sent from my NookColor
I am using 20121228-NIGHTLY-encore nightly release and the sleep of death (SOD) bug happens on my Nook Color too. I had left my Nook on a table and later it had booted up to the Nook OS.
Related
Hey guys,
I'm running CM 10.1 RC5 with franco M2, and I started experiencing massive suspend_backoff wakelock a week or so ago. It only happens on my home wifi and nowhere else.
I did some googling and most people say this is caused by Chrome, but I don't even have that installed. I tried a different kernel with no success (faux still gave me suspend_backoff wakelock). But the thing is, I never got this wakelock when I was running stock, so could it be a CM issue?
Any tips would be appreciated.
I am facing the exact problem.... Chrome is not installed on my phone either...
Last weekend for the second time flashed Quarx's CM 10.2 Nightly from CM 10-2ndboot. Here's my report:
1) Experienced the "unfortunately android keyboard has stopped" problem after updating. Didn't know how to solve it, so I had to flash SBF and still had this issue. After numerous times of reflashing finally got this problem gone. So I guess it's my flashing problem (?).
2) 720P Recording isn't working, although this is th default present for the camera app.
3) I wonder if anyone else noticed it: texts in the SMS app is thincker yet blur tha the previous roms (CM10 or earlier). Actually it's hard to read.
4) Also, the touch buttons' lightness is no longer auto-adjusted - either 100% light or off. Don't know if this is a univeral Jelly Bean issue or only occurs for Defy.
5) Last but not least: how can I disable the animation effects while switching the home screens?
Except from the above, all other functions worked fine. But in the end I flashed back to my previous choice - the stable CM10-2nd boot builds due to all those small but iritating issues.
Maybe they will all be solved in KitKat?
ymyzhifeng said:
Last weekend for the second time flashed Quarx's CM 10.2 Nightly from CM 10-2ndboot. Here's my report:
1) Experienced the "unfortunately android keyboard has stopped" problem after updating. Didn't know how to solve it, so I had to flash SBF and still had this issue. After numerous times of reflashing finally got this problem gone. So I guess it's my flashing problem (?).
2) 720P Recording isn't working, although this is th default present for the camera app.
3) I wonder if anyone else noticed it: texts in the SMS app is thincker yet blur tha the previous roms (CM10 or earlier). Actually it's hard to read.
4) Also, the touch buttons' lightness is no longer auto-adjusted - either 100% light or off. Don't know if this is a univeral Jelly Bean issue or only occurs for Defy.
5) Last but not least: how can I disable the animation effects while switching the home screens?
Except from the above, all other functions worked fine. But in the end I flashed back to my previous choice - the stable CM10-2nd boot builds due to all those small but iritating issues.
Maybe they will all be solved in KitKat?
Click to expand...
Click to collapse
1. Usually this is a wrong gapps issue.
2. 720p rec might not be working due to green lens Defy.
3. No, it looks the same.
4. Yes, i've noticed this too, but it's not a major issue.
5. I think there is an option in Trebuchet settings/use a different launcher.
ymyzhifeng said:
Last weekend for the second time flashed Quarx's CM 10.2 Nightly from CM 10-2ndboot. Here's my report:
1) Experienced the "unfortunately android keyboard has stopped" problem after updating. Didn't know how to solve it, so I had to flash SBF and still had this issue. After numerous times of reflashing finally got this problem gone. So I guess it's my flashing problem (?).
2) 720P Recording isn't working, although this is th default present for the camera app.
3) I wonder if anyone else noticed it: texts in the SMS app is thincker yet blur tha the previous roms (CM10 or earlier). Actually it's hard to read.
4) Also, the touch buttons' lightness is no longer auto-adjusted - either 100% light or off. Don't know if this is a univeral Jelly Bean issue or only occurs for Defy.
5) Last but not least: how can I disable the animation effects while switching the home screens?
Except from the above, all other functions worked fine. But in the end I flashed back to my previous choice - the stable CM10-2nd boot builds due to all those small but iritating issues.
Maybe they will all be solved in KitKat?
Click to expand...
Click to collapse
1) You need to install the correct gapps from TJKV (unfortunately i can't post links)
2) It's working for me (Defy+).
3) It's perfect in my Defy+, not blurry.
4) It's true, nothing to say.
5) Go to Settings>Developers option>Drawing and turn Animation off in this itens: Window animation scale, Transition animation scale and Animator duration sacel.
so for the past few weeks i've been trying to find a stable ROM for my G2 (D-801) and i've been plagued with graphical glitches (static across screen) and lockups that will either cause the screen to freeze for a random amount of time (20+ seconds) or just lock up for a few seconds and then reboot.
This issue persisted across CM11, Karbon, PA, and everything else that has a recent build date in the development forums. So i was beginning to suspect I might have a hardware fault with my phone that was causing the problem.
The last thing I did was flash the oldest ROM i have for the phone. Paranoid Alpha from 12-03-13.
And graphically it has been PERFECT. So i'm not sure what the deal is with my phone.
currently running:
Baseband:
M8974A-AAAANAZM-1.0.190084
TWRP:
2.6.3.4
not sure what the deal is, or if I've forgotten to update something outside of the ROM that could be causing these issues.
Thanks for the help.
For the past few weeks, I've been having multiple sleep of death events. Sometimes more than one per hour. I've tried upgrading nightlies, but they keep happening. I'm running CM12.1 with encrypted storage and an Android for work profile. Anyone experience anything similar?
I downloaded app to see why my gyro is weird and there i can se that gyro or orientation does not work and it did before joining beta.
Is this a known issue?
Can i solve it somehow?
I got ota yesterday so a pretty new build i guess
I am not rotted i havet it all original
I've had a similar if not the exact same issue as of obtaining this device. I enrolled in the beta around the third Dev preview (immediately after I purchased the phone, it's still fairly new as of writing this), at the end of the fourth preview I started having the same issue, gyroscope just spontaneously stopped working. At first I thought it was a hardware issue after doing some research (apparently some Nexus 6P users gyroscopes are just getting stuck or something along the lines of that?? And they'll report it working again after a few good smacks to the thigh.) I would have assumed this to be the issue but I found that rebooting the device actually fixed it temporarily, but after a few hours it stops working again. I'm now using the fifth and final dev preview and it's still an issue. The fact that rebooting fixes the issue (temporarily) and not smacking the phone around in my scenario leads me to believe this is a dev preview bug.
Yeah it looks like it. Never har trouble before but after updating ro beta it started.
Anyone know if this is a known bug?
its a known bug just restart your phone if gyro isnt working.