Anybody else having problems with the haptic feedback turning off when the phone reboots?
I'm running stock UCLG1 (was on CM9 for a bit, back to unrooted stock due to the Good app & a possible upcoming RMA) & every time my phone reboots, the hepatic feedback turns off. I've tried fiddling with the Auto haptic on or off, still happens. I don't recall the problem when I got the phone or with CM9, but have noticed it since I went back to stock (admittedly a newer version than pre CM9).
It's really annoying in combination with the random reboots I get once a day or so. I may be RMAing the phone soon due to the reboots, will see if that fixes this issue too.
Related
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Do you have setCPU ?
i know sometimes when people set screen off properties to low it freezes and needs a batt pull
Funny enough, I guess the problem started after I installed that. I cleared its settings and cache and uninstalled the program hoping it would fix it, but no dice. I figured that would fix the issue if it was related
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
I tried that once, didn't seem to help but I will give it another shot.
I am running stock DK28 ROM, maybe a fresh install will help?
o and you wouldn't happen to be on viper rom would you ?
iSaint said:
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
Click to expand...
Click to collapse
Set it at 200 min.
not running viper ROM. I am running stock froyo with root access.
DiGi: Is that what you have it set on? I thought I read somewhere not to set it that low.
I was running on 200 min just fine. I haven't had setcpu on my phone for a little while though. I think 100 is too low and causing the problem. 200 didn't cause crashes for me.
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
djbacon06 said:
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
Click to expand...
Click to collapse
Odin
reflash your rom
probably something went wrong when flashing
this happens to me when my battery is low (stock dk28)
it's working for me
djbacon06 said:
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Click to expand...
Click to collapse
Recently changed my phone to android and my phone wouldn't wake up every time it goes to sleep more. (Radio 2.10.50.2)
looked and tried a lot of suggestions (format SD, flash ROM, update setup.txt file and etc) but nothing worked until I flashed the new radio 2.14.50.
And it's been working fine for a day now (finger crossed).
Do you have adjbrightness? Theres a problem with it on galaxy s phone where it won't wake up that they haven't been able to fix and that may be your problem.
Did you ever figure out how to fix this "no wake up" issue? I had this problem out of the box with my mini. So does my friend.
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.
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.
So.. i have had a weird problem for quite awhile now but have been putting up with it..
When on a voice call when the screen goes off it will mute the mic, leaving the other person asking if i am there.. i have to shake the phone or hit the power button a bunch. It also doesn't wake up instantly when that happens, almost like its in a deep sleep. I don't have any battery saver apps or anything installed....
I am using CM11 right now with FL24 modem, i have tried other modems.. same issue.. This issue also happened on other roms incluing vanir and others...
I did a search and found one other person with the same exact issue.. but no fix posted, was hoping someone might have an idea on how to figure this out.. thanks..
Experiencing Similar Problem
I've been experiencing a similar issue for a bit over a month, too. I'm not quite sure if it was when the screen went off, but certainly within 15 seconds of making or receiving a call my mic cuts off. It sometimes comes back after -- I don't know if that's because I shake the phone around or otherwise get the screen to come on, although the mic turning back on and the screen turning back on do not happen at the same time.
I'm also on CM11 with FL24 modem on a Samsung Epic 4G Touch, which makes me suspect it's the same problem. Do you have a link to the other forum post?
I suspect it's a relatively recent regression with CM, because I installed CM11 on the phone at the end of October and everything was fine. I first started experiencing the issue a few weeks thereafter. I can't recall if it happened after upgrading CM, or if It was after I installed Google Voice (since removed,) or if there was no particular prompt.
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.