Is anyone have a problem with their contacts sync to their Google account. Everytime mine tries to sync, I get a force close and states Google Services framework has unexpectedly stop. I've reflashed Gapps, and different roms. This is getting frustrating.
[Official] CyanogenMod 7 discussion
- Thread starter enzofall
- Start date
Link to possible new radio?
Try fixing the permissions for that. That may help.
I cannot get the radio to flash, What do I name the file again? Clockwork keeps giving me a long error message. UGH
A lot of people were having trouble flashing the new radios on clockworkmod. Not sure what was going on with it but when switched to Amon_RA the radios flashed with no problem. Once flash just reflash clockworkmod.
Clockwork Recovery version does not support the Amend scripting language Amon_RA does.
Here is a great theard that might help to explain it. [NOTICE] ClockworkMod Recovery 3.0+ and update-script - xda-developers
candroid90
Well-known member
- Jun 11, 2011
- 55
- 1
- 0
Does anyone else have problems with the lock screen becoming unresponsive? This has happened to me 3 times in the last 2 weeks. The phone isn't locked-up or anything, but I cannot unlock the screen at all. I have seen other UI flakiness which may or may not be related, but this one is frustrating because it forces me to reboot the phone.
If anyone has any tips or ideas that would be great, thnx!
If anyone has any tips or ideas that would be great, thnx!
happens to me sometimes too i usually just hold down the unlock button for about 3-5 seconds usually flickers on. i've also read somewhere about disabling the screen off and on animation
Cool, thanks - I just disabled the on/off animations as well as the "wallpaper hack" setting in ADW. (trying random things mainly)
So you mean just holding your finger on the unlock icon for a few seconds? (rather than trying to swipe it?)
Well I after running CM7 stable for about 3 weeks now I have to say that while there's a lot of things I like about it, it's certainly nowhere near as stable as the stock ROM that comes on the EVO.
I consistently have weird, flaky UI problems such as the following:
- Screen won't turn on after pressing power button. Needs to be held down for a couple of seconds for screen to come on.
- Unlock widget gets "stuck" and won't move no matter how many times I try to swipe it.
- Any widgets or icon's on the Android home screens won't appear - only the wallpaper is visible. Pressing the home button seems to trigger the screen to redraw itself. (this is only a temporary fix)
- Many of the settings menus won't be visible unless I drag my finger across the screen, forcing it to redraw.
All of these things are intermittent, and eventually force me to reboot. Then everything's great for a couple of days until they start happening again.
I have yet to reach a week of uptime, whereas with the stock ROM I would typically get a good 4 or 5 weeks of uptime before I needed to reboot.
I can't be the only one experiencing this stuff? Trying to decide if the benefits of cyanogen is worth this hassle.
I consistently have weird, flaky UI problems such as the following:
- Screen won't turn on after pressing power button. Needs to be held down for a couple of seconds for screen to come on.
- Unlock widget gets "stuck" and won't move no matter how many times I try to swipe it.
- Any widgets or icon's on the Android home screens won't appear - only the wallpaper is visible. Pressing the home button seems to trigger the screen to redraw itself. (this is only a temporary fix)
- Many of the settings menus won't be visible unless I drag my finger across the screen, forcing it to redraw.
All of these things are intermittent, and eventually force me to reboot. Then everything's great for a couple of days until they start happening again.
I have yet to reach a week of uptime, whereas with the stock ROM I would typically get a good 4 or 5 weeks of uptime before I needed to reboot.
I can't be the only one experiencing this stuff? Trying to decide if the benefits of cyanogen is worth this hassle.
I don't have any of those issues on 7.1 RC. Wipe all and flash again? If you back up your apps it shouldn't take more than 30 minutes.
Well I after running CM7 stable for about 3 weeks now I have to say that while there's a lot of things I like about it, it's certainly nowhere near as stable as the stock ROM that comes on the EVO.
I consistently have weird, flaky UI problems such as the following:
- Screen won't turn on after pressing power button. Needs to be held down for a couple of seconds for screen to come on.
- Unlock widget gets "stuck" and won't move no matter how many times I try to swipe it.
- Any widgets or icon's on the Android home screens won't appear - only the wallpaper is visible. Pressing the home button seems to trigger the screen to redraw itself. (this is only a temporary fix)
- Many of the settings menus won't be visible unless I drag my finger across the screen, forcing it to redraw.
All of these things are intermittent, and eventually force me to reboot. Then everything's great for a couple of days until they start happening again.
I have yet to reach a week of uptime, whereas with the stock ROM I would typically get a good 4 or 5 weeks of uptime before I needed to reboot.
I can't be the only one experiencing this stuff? Trying to decide if the benefits of cyanogen is worth this hassle.
I never experienced any of those things when I ran CM7 which was up to about 3 weeks ago when I switched to MikG 2.15 and now 2.3. You might want to try installing it from scratch and making sure to wipe everything multiple times. I once ran into random issues while testing out ROMs that no one else reported and it was apparently due to CWM not wiping one of the caches properly.
Thanks guys, maybe I'll try going to 7.1 RC1. Looking at this thread in the cyanogenmod forums, it looks like others are seeing the screen not turning on problem that I'm seeing: Screen doesn't show in 7.1.0 RC1 sometimes - CyanogenMod Forum
It's a common problem, I think the popularly accepted term for it is "wake lock" issues. I saw it on a previous build of CM7 but I haven't had the problem at all running CM7 and Tiamat 3.3.7 kernel.
Before flashing a new CM7, try downloading the Tiamat kernel and flashing that first. Most people say 3.3.7 gives the best battery of any of the versions and keeps HDMI functionality. Wipe cache, dalvik-cache, and battery stats in recovery before flashing the kernel (leave data intact).
Before flashing a new CM7, try downloading the Tiamat kernel and flashing that first. Most people say 3.3.7 gives the best battery of any of the versions and keeps HDMI functionality. Wipe cache, dalvik-cache, and battery stats in recovery before flashing the kernel (leave data intact).
Just rooted my Evo again and running CM7! But one issue:
Is anyone getting "insuffcient storage available?" I have over 150MB of space available, and some apps, such as Angry Birds, just won't install.
I've tried force stopping Market, even clearing cache. Still won't work. Any suggestions?
Is anyone getting "insuffcient storage available?" I have over 150MB of space available, and some apps, such as Angry Birds, just won't install.
I've tried force stopping Market, even clearing cache. Still won't work. Any suggestions?
Similar threads
Trending Posts
-
-
Question Android 14: Is there a Do Not Disturb Feature?
- Started by tinker1234
- Replies: 1
-
-
-
Facebook
Twitter
Instagram