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.
Related
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.
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.
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.
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
My wife's pixel 3xl recently started having this problem. It is completely unmodified stock, locked bootloader, reports it is on the latest update.
Wifi and bluetooth won't stay on. A reboot fixes it, but eventually they shut off again. Sometimes it lasts a few days after a reboot, sometimes less. Once they shut off, they can't be turned back on again. You can try and toggle them on with quick settings, but it doesn't actually work. Only a reboot fixes it.
I tried a factory reset a couple of weeks ago. That seemed like a cured it for about a week, but it's back.
It's a pretty aggravating problem. If I can't fix it soon, she's probably going to end up with a new phone. Anyone else seen this, or better yet, know a fix? I've done some searching in the forum and on the web in general, but I didn't find anything informative other than one webpage that talked about some pixels, especially the 4a, having problems like this after updating to android 11.
Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Edit: I have no idea why this would make a difference, but I switched unlocking method from swipe to none this morning and that eliminated that long wake-up delay. It's back to fast and responsive like it should be.
Now to see if wifi and bluetooth are going to behave better on android 10.
jason2678 said:
Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Click to expand...
Click to collapse
You can try wakelock V3 and select 'CPU' and set as autostart on boot in the app settings to see if it wakes faster.
I can't believe that it worked for me. I was facing the same issue and I got frustrated. I was just serching and came across a reel showing fix regarding it. In that video person switched off his pixal tapped it on his leg (backside of phone) and then started it and keep tapping it on his leg while starting. It's really weird but I gave it a try. And can't believe it worked. Wife and Bluetooth both fixed now. Getting "on" now.