I'm running official CM10.1 20130522 nightly on my 862 and I am not able to adjust volume with volume buttons with the screen turned off.
Works fine if screen is turned on, even at lockscreen.
Now, I am using this with Spirit FM radio app, so perhaps there's a weird conflict. If so, maybe I'm not doing the settings there right, if so, I'll go to the respective thread for that app.
Off topic, I need more 10.1 nightlies since 20130522!! Lol.
Sent from my DROID RAZR MAXX HD
Related
Is anyone else having this issue as well I can get rid of it I've tried everything to what happens is sometimes when my phone is asleep tonight wake it up it's completely unresponsive, the screen turns on but I can't do anything other than hit the power button on and off and volume other than that I am stuck on the same screen. Also when I wake up in the morning after charging my phone overnight it is always frozen like this but even worse when it has been more than a few hours. Could this be related to using an alternative home? I have used both launcher pro and adw with the same results. I have never had this with any of my other android phones. Any ideas?
Sent from my DROID BIONIC using Tapatalk
Take it to Verizon and get a switchout.
Before I do that I would like to make sure that it isn't software based otherwise I will just run into the same issue.
Sent from my DROID BIONIC using Tapatalk
I haven't experienced that issue, but something similar. About once every 2 days my phone won't wake at all. The notification light seems to be working, but pressing the power/lock button doesn't wake the phone, screen stays black and I have to pull the battery. If I call the phone while it's in this state, nothing happens on the Bionic's side, but the phone I calling from hears 4 rings before going to voicemail. I've uninstalled Widget Locker and Home Switcher to see if either of them are the culprit.
awesome, thanks
I would do a factory rest and see if it was a software problem first.
Sent from my DROID BIONIC using xda premium
Do you have in pocket detection on under settings? Try turning that off. I was having major issues like that when I was using that setting.
quentin0 said:
Do you have in pocket detection on under settings? Try turning that off. I was having major issues like that when I was using that setting.
Click to expand...
Click to collapse
Good advice, the pocket sensor on this phone is borked.
--
On stock there's an option in display settings for keeping the front key lights on for as long as the screen is on, which I'd really like to have on offical CM 10.1 but there's obviously no such option. On Dexter_nlb's CustoNexus Soft Buttons Light worked a charm but it doesn't seem to work on CM now. Has anyone had any luck with similar apps? I can't be the only one who wants it, since it's an option in stock.
This ROM has it in the options.
/plug
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Probably software issue.
If your using a magnetic case (problem)
You could try disabling the lockscreen if its enabled.
Daydream could in my theory affect that time frame.
The backlight should last years longer. The gpu should as well. I can't think of any other hardware issue.
If you have an sdcard try cm11 [or the bn rom] and see what happens. OR full backup of current rom in cwm and flash cm11 to internal. Clean and restore 10.1.3 and be back to right where you left off.
lmacmil said:
My HD (running 10.1.3 stable) has just started behaving strangely when I wake it up from sleep. The screen will flash then go black. Whether I push the Nook button or the power button, the same thing happens. It may do it 2 or 3 times before it comes on. Started doing this yesterday. Just now, it would not come on at all. I see the screen for a half second, then it goes black. Just wondering if it's already toast or if this is a known problem with a remedy.
Click to expand...
Click to collapse
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case but it happens without it. Before this happen, my slide to unlock screen would act up by not unlocking when I slide to unlock; it would just go back to the initial lock screen. Slide to unlock would not work so I turn off the lockscreen, now experiencing blackout screens when I try to wake it up by pressing either buttons. This problem happens infrequently but it is annoying.
kinvid said:
Yes I have the same flickering issues when trying to wake it up from sleep. I would have to press either button numerous times to get it to stay on and not black out. I'm on the same 10.1.3 stable. I am using a magnetic case...
Click to expand...
Click to collapse
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
lmacmil said:
I learned from another post that if it does not awaken when the magnetic case is opened the first time, close and open it again. This works for me 95% of the time. Sometimes there's 2 or 3 second lag but it almost always comes on.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Works like this on my HD+, too. Sometimes requires opening case cover twice, but the screen always comes on.
In daydream showing the clock on my tylt charger on my night stand its annoying that the capacitive buttons are lit up the entire time...figured google would have fixed this by now...guess not.
I just discovered that Lux, the autobrightness program, can turn them off entirely without root. Awesome, but i would like them on (normal) when not charging and off when charging.
Anyone know of an app that would do this that doesnt require root? I thought for any app to do it root was required, but lux proved me wrong on that, so now im on the hunt for a program that will.
Oh, and is there an easy root method out there yet on this?
sdgmcdon said:
In daydream showing the clock on my tylt charger on my night stand its annoying that the capacitive buttons are lit up the entire time...figured google would have fixed this by now...guess not.
I just discovered that Lux, the autobrightness program, can turn them off entirely without root. Awesome, but i would like them on (normal) when not charging and off when charging.
Anyone know of an app that would do this that doesnt require root? I thought for any app to do it root was required, but lux proved me wrong on that, so now im on the hunt for a program that will.
Oh, and is there an easy root method out there yet on this?
Click to expand...
Click to collapse
If I had to guess I would say Tasker can probably do this. I don't have any experience with the app, but I know that it is capable of just about anything that can be done without root.
neyes said:
If I had to guess I would say Tasker can probably do this. I don't have any experience with the app, but I know that it is capable of just about anything that can be done without root.
Click to expand...
Click to collapse
I used Tasker to do this with my Droid Razr Maxx. I don't recall if it required root or not...
Alert > Set Light is where you do it, find the one you want and set a value. My Moto X 2013 lists several options, but sure what the Turbo would list. Play around with it.
I had the same problem and figured out a solution that doesn't require root or an additional app...
Set a screen lock such as key code or pattern and the option where the power button locks it. With the screen off, hit the power button once to go to the lock screen but don't unlock. Daydream should start shortly without the keys lit.
I tried it and it works perfectly. A couple additional suggestions. For Daydream to start, you have to have it setup properly (i.e. on charge/dock/both). In addition, if you want it to operate in landscape mode, you'll need to run Daydream first in landscape. Turn the screen off with the power button and then turn it back on with the power button while leaving it in landscape mode. Don't unlock it and Daydream will start and the capacitive buttons will remain off no matter how dark the room is.
Hope this helps...
Revisiting this subject because the new lollipop update for the Droid Turbo has broken the solution I mentioned above. Anyone have suggestions on how to turn off the capacitive buttons while the phone is being charged and running a clock app?
Dabrador said:
Revisiting this subject because the new lollipop update for the Droid Turbo has broken the solution I mentioned above. Anyone have suggestions on how to turn off the capacitive buttons while the phone is being charged and running a clock app?
Click to expand...
Click to collapse
Try an app like Darker. Just set it to turn capacitive keys off and 100% transparency. Then turn off the apps notifications.
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Byrkoet said:
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Click to expand...
Click to collapse
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
alray said:
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
Click to expand...
Click to collapse
Thanks for the info. I figured as much, I will try Exodus.
EDIT: I have tried Exodus, XenonHD and Dirty Unicorns. Though no success: none of them were able to turn on the display after it dimmed.