9 replies to this topic

[theCyborg]

I just flashed CM7 a day or so ago, and have largely been impressed by everything. I can live with WiMax being broken, as well as the few other minor bugs, but there has been one major bug that has cropped up.

Whenever a call ends, whether incoming or outgoing, the screen won't come back on. This has happened whether or not I use the power button to end the call, and also when the other person has ended the call. When I hold the phone to my ear, the display turns off accordingly, but will never turn on.

If I use the speakerphone, it doesn't happen nearly as often, but it's not really a viable solution. I know there's a setting to keep the screen on longer, but it will eventually turn itself off. Is a wipe-reflash necessary to help fix this, or is there a way to reset the proximity and/or light sensor values?

This is the first flash I've ever done, so I'm still new to everything.

[AmericanJedi001]

One other person reported a similar--maybe identical--bug.  Unfortunately, I don't think he found an easy fix.  I would reflash, and be sure to wipe your Cache and Dalvik partitions.  If that doesn't fix it, maybe try again and wipe Data as well?  That's just a guess.  Good luck!

[theCyborg]

Well, seeing as how I've gotten all the apps/settings/etc. already set up, would doing a Nandroid backup via ClockworkMod Recovery, reflashing CM7, then reverting to the backup work, or would that be missing the point of the flash?  Thanks to Titanium Backup, I can backup/recover my apps/data, but I don't want to have to set up everything again if I don't have to.

[AmericanJedi001]

Quote

Well, seeing as how I've gotten all the apps/settings/etc. already set up, would doing a Nandroid backup via ClockworkMod Recovery, reflashing CM7, then reverting to the backup work, or would that be missing the point of the flash?  Thanks to Titanium Backup, I can backup/recover my apps/data, but I don't want to have to set up everything again if I don't have to.

To restore a Nandroid backup would be missing the point: it would revert you to whatever state your phone was in at the time you made the Nandroid backup, including any issues you're having.

Go ahead and make the Nandroid backup, but save it in case things go horribly wrong. You could also do a Titanium backup.

Unless you wipe the Data partition, all your settings should remain as they are.

Be sure your Homescreen Launcher saves its settings to the SD card.  I use Launcher Pro Plus, which has a manual Backup-to-SD function.  Then perform the flash from ClockworkMod (CWM) Recovery and wipe Cache and Dalvik.

If that doesn't work and you repeat it, while also wiping the Data partition, then yes, you'll have to re-do most of your settings.  I say "most" because a few apps, such as Launcher Pro, will restore settings from the SD card automatically (if the settings were saved beforehand!) once they've been reinstalled after a fresh ROM flash.

So in summary, make sure you have a Nandroid to restore the entire phone back to the state it was in.  Use Titanium Backup (TB) to restore individual apps and their settings/ data, and use any save-to-SD (or External) feature your apps may have.  Occasionally a TB app restore will misbehave, necessitating a Data and/or Cache wipe for the offending app.  So use different types of saves and backups for different circumstances.

Edited by American Jedi, 31 December 2011 - 08:18 PM.

[theCyborg]

Well, I've got good news and bad news. After wiping the various settings and reflashing CM7, the problem doesn't seem to happen as often. It still happens just the same, though. However, upon sliding out the keyboard in order to take my case off (to yank the battery), the screen popped back on just fine. Unfortunately, this wasn't something I'd tried before the wipe/reflash, but at least my phone is still usable despite the bug.

Granted, I really hope this gets fixed soon, but as long as I can simply slide the keyboard out and back to turn the screen back on, I can live with it. Anyone else running into this kind of issue?

[AmericanJedi001]

theCyborg, on 02 January 2012 - 10:45 PM, said:

Well, I've got good news and bad news. After wiping the various settings and reflashing CM7, the problem doesn't seem to happen as often. It still happens just the same, though. However, upon sliding out the keyboard in order to take my case off (to yank the battery), the screen popped back on just fine. Unfortunately, this wasn't something I'd tried before the wipe/reflash, but at least my phone is still usable despite the bug.

Granted, I really hope this gets fixed soon, but as long as I can simply slide the keyboard out and back to turn the screen back on, I can live with it. Anyone else running into this kind of issue?

I'm glad to hear it's not happening as often, but it sucks it still happens at all.  I'm thinking that this issue may have come up a couple months ago with CM, but I can't recall if it was one or two individuals, or a particular "nightly" / "kang" release, which would have been quickly replaced or reverted to the previous release.  Either way, try the latest Epic MTD CM nightly, found here.  Here's the quick-and-dirty start-from-fresh that I recommend, since you're having what I would call a major issue:

• Save the latest version of Epic CyanogenMod to your SD card
  
• Use your favorite backup app to back up any and all apps that you hold dear, besides those built into CM7.2 and the Google Apps *
  
• If you use Titanium Backup, click the [Menu] button >> [More (\/)] >> [Create "update.zip"...] to create a flashable copy of TB **
  
• Power down, boot into Recovery
  
  • Wipe the Cache, Dalvik, and Data partitions
    
  • Flash the latest CM release
    
  • I almost always wipe again after I flash, in this case all three partitions ***
    
  • Flash the Google Apps ("Gapps" / "GApps" / etc.)
    
  • Flash the TB .zip you created in step 3.  (You do use TB and therefore followed step 3., right? )
    
  • Reboot

• After booting into Android, allow your phone at least a couple minutes to finish rebuilding the Dalvik cache, etc.
  
• Log back into Google services
  
• Set up your favorite launcher and system settings
  
• Using TB and the Market where necessary, restore all your apps
  
• Experience the awesomeness of a fully working CyanogenMod nightly!  (Besides the usual bugs, but at least no showstoppers!)
  Notes

• * You'll be flashing these shortly.
  
• ** And you'll be flashing this soon too.
  
• *** Probably unnecessary, but it seems reasonable to think that fresh partitions before a ROM flash, and after, before bootup, would make sense.

Good luck!  I hope I didn't leave anything out...

[Pvt.JoKeR]

not exactly the same issue, but i had my phone on my desk the other night (playing bf3) and a friend called, i didn't touch my phone (as I had just talked to him less than 10 min ago) and then watched it reboot itself as soon as it went back to the lock screen.  wasn't a big deal, but was rather annoyed as i'm pretty sure this is the first time i've ever had my phone reboot randomly while running ANY CM7 rom..

[exdaxtcy]

Pvt.JoKeR, on 06 January 2012 - 07:33 PM, said:

not exactly the same issue, but i had my phone on my desk the other night (playing bf3) and a friend called, i didn't touch my phone (as I had just talked to him less than 10 min ago) and then watched it reboot itself as soon as it went back to the lock screen.  wasn't a big deal, but was rather annoyed as i'm pretty sure this is the first time i've ever had my phone reboot randomly while running ANY CM7 rom..

I've heard of this from other users and seen it myself on earlier TW based ROM's, but never CM.  Guess it's not reproducable, eh?   If it is grab logs and kmsg dump.

[Pvt.JoKeR]

codest3r, on 06 January 2012 - 10:24 PM, said:

I've heard of this from other users and seen it myself on earlier TW based ROM's, but never CM.  Guess it's not reproducable, eh?   If it is grab logs and kmsg dump.

So far I've only seen it happen that 1 time, and I've moved through several different nightlies since..

[sonarchist]

Have been experiencing smooth sailing on my other device, EPIC on nightly 10........however, this one (cm6) has tended to ring when a call comes in, tho the screen remains *black*.......yes I slide along the screen + guess where the slider would be often w/ good results, lol.........................all to say, we're blessed that cm7 is at the stage that it is in.....+ it's only gonna get better!

.............incremental goodness in the making.

sent via m920.::CM6::.Pandroid