I've been waiting for the stable version of CM7.1 forever so I could finally use it. I didn't bother with the nightlies, since I was enjoying MIUI, so this is my first experience with CM, and I'm having some issues.
Firstly, I got caught in multiple bootloops, even though I wiped the cache and Dalvik, and even did a factory reset. When that didn't work I wiped everything, yanked the battery, then re-flashed everything, which (finally) got it booted.
At which point I realized the home button does absolutely nothing. I went into both the CM settings and the ADW Launcher settings and set actions for the home button - still nothing. No short press or long press. The home button on my phone at the moment is completely for show. I know it works because it's never given me any trouble, and key test from recovery works just fine.
I'm also not getting a lockscreen. I've toggled my way through pretty much every possible lockscreen setting and combination of settings, and there simply is no lockscreen on my phone.
Those are just the biggest issues I've discovered thus far. I'll be playing with it for another couple hours, but if no one can find a fix for these issues, than the hell with CM7, I'm back to MIUI. It's a shame, because CM7 has some amazing features, but without a lockscreen or home button it's just not worth much.
Edit #1: Just made a test phone call with it. Although sound works fine, after hitting the end button it took a solid 20 seconds to actually end the call.
Once you got it booting, did you restore any system apps or data? I've had this exact thing happen to me before, and it was because of system data.
Didn't restore anything. Wiped everything, flashed CM, got problems. I finally just went ahead and restored my MIUI off a nandroid backup. I'll stay with MIUI until someone finds a solution to the CM issues....
Hmm, that's weird...not sure what it is then. Maybe a bad download or something? Not sure. I guess probably try it again some other time
I'll wait a week or two to see if these issues pop up on any other threads or the CM forums, and if they don't then I'll try downloading it through ROMManager instead of from the CM site and reflashing.
Related
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
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.
I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.
Hey all, my phone keeps freezing. It's anytime I interact with it, it has a chance to lock up hard. I just went to unlock the phone and it froze as soon as I touched the 'lock' to unlock the phone. I recently tried doing a full wipe but it didn't make any difference. This has been happening since Christmas, I'd been hoping new nightlies would fix it, but so far nothing has changed.
Last night I was playing Pandora and went to hit 'next', the screen froze when I unlocked and hit the button, but music kept playing like nothing was wrong. Previously, I thought it was Swype causing it, but it's not just the keyboard popping up anymore that's giving me this behavior.
Is there a log or something I can view to see what is happening and causing this? It's extremely irritating and I just want to fix it.
CM10.1 Nightly
KT747 (1-10-2012) Edit: I'm going to flash today's nightly without the kernel to see if that helps.
Try doing a fresh installing, clear everything several times, dont restore any data
Sent from my PG06100 using xda premium
That's my next step. Without the KT kernel my issues are significantly reduced, I think I'll wipe and not restore my apps/settings/texts.