Related
My rooted nook screen keeps turning off while charging, and I can't find the setting to disable it. I have it configured so wi-fi turns on and off with the screen, and sometimes I'd like wifi on in the background to download or do other things. The only way I can do that now is to remember to keep touching the screen every few minutes.
Any help?
I use a widget from the market called Screen ON widget. Just have to tap it to keep screen on. Works great.
Sent from my hacked nook color.
There's an app called 'Setting Profiles' which works well for this situation. The free version allows just one rule which should be fine if this is all you need it for.
Thanks for the response guys. I actually do use Setting profiles, which is what I use to turn the wifi on and off with the screen. I just haven't figured out how to configure it to keep the screen on.
I searched for 'Screen on widget', but I got 3000 hits, and couldn't find it.
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Hey, I'm only posting because I had a very similar issue. What I did was go into display settings (while connected via USB) and changed the timeout to one minute (or whatever you want). For me, when I went to change the timeout, no item was selected by default. This happened to me after I installed WidgetLocker for some reason. I doubt I will help but I had a very similar issue...
xd_sjo said:
Hi all,
I've had a search around but couldn't find this particular issue discussed.
I have a N1 running CM7. When the phone is plugged in (either on my desk, or in the car) the screen will auto dim to a very low level after approx. 20 seconds after last touch.
This happens if the brightness is set to auto or a manual level. I've gone through all the settings I can find but couldn't find anything regarding this. I have got developer > stay awake enabled, which I guess stops the screen from actually sleeping, but it still goes dim.
The CM7 auto dim settings are disabled.
Any advice folks? I want the screen to not auto-dim after 20 seconds. Out of interest, the 'Car Widget Pro' widget seems to be able to force the brightness if you choose something other than 'auto' in the widget settings. So perhaps I am missing something somewhere else?
It's a real PITA when trying to navigate in the car with google maps as whenever I touch the screen to get the brightness back it disables gps tracking and I have to re-hit the icon, which is distracting whilst driving..
Here's hoping..
Click to expand...
Click to collapse
There's an app for that. Search Google Play for screenwake or something. I dunno I'll search up the name for you tommorow
Sent from my Nexus One using XDA
I just installed JellyBam ROM which is based on AOKP/CM10. The only issue I am having is when the phone is docked in the official desk dock. This is my first Jellybean ROM, so it could be an issue with JB as a whole. Here is the problem.
When on ICS, this is how the phone behaves when desk docked:
If the phone was locked (with screen off), it turns the screen on, unlocks itself, starts the Clock app and continues likes that for a few minutes. Then it activates the Night mode on the clock and stays like that until the phone is undocked.
If the phone was NOT locked (that is the screen is on, with either on the launcher screen or some other app screen), the phone starts the Clock app and continues likes that for a few minutes. Then it activates the Night mode on the clock and stays like that until the phone is undocked.
Now on Jellybean, this is what I am facing:
If the phone was locked (with screen off), the screen turns on for 1 minute (which is the screen turn off time I set in the Settings) and then the screen turns off. When I undock the phone, the screen turns on at the lockscreen. And then when I unlock it, the Clock app shows up, implying that the Clock app was indeed launched when I docked, but some lockscreen setting overrode it.
If the phone was NOT locked (that is the screen is on, with either on the launcher screen or some other app screen), the phone starts the Clock app and continues likes that for 1 minute (which is the screen turn off time I set in the Settings). Then it turns the screen off. When I undock the phone, the screen turns on at the lockscreen. And then when I unlock it, the Clock app shows up, implying that the Clock app was indeed launched when I docked, but some lockscreen setting overrode it.
Is it possible to revert this desk dock behavior back to ICS style?
Just to let you know that I fixed this issue by creating a Tasker profile for a third party desk clock app
Yeah, Tasker is awsome.
Invisman said:
Now on Jellybean, this is what I am facing:
If the phone was locked (with screen off), the screen turns on for 1 minute (which is the screen turn off time I set in the Settings) and then the screen turns off. When I undock the phone, the screen turns on at the lockscreen. And then when I unlock it, the Clock app shows up, implying that the Clock app was indeed launched when I docked, but some lockscreen setting overrode it.
If the phone was NOT locked (that is the screen is on, with either on the launcher screen or some other app screen), the phone starts the Clock app and continues likes that for 1 minute (which is the screen turn off time I set in the Settings). Then it turns the screen off. When I undock the phone, the screen turns on at the lockscreen. And then when I unlock it, the Clock app shows up, implying that the Clock app was indeed launched when I docked, but some lockscreen setting overrode it.
Is it possible to revert this desk dock behavior back to ICS style?
Click to expand...
Click to collapse
Just for the record I'm getting this behaviour with a JB 4.2 based custom rom (rasbeanjelly) on a gsm Galaxy Nexus. Desk dock worked properly with JB 4.1.2
Dunno if it's all JB - Google has few hits on the subject.
eta: I found the fix.
settings > display >daydream
make sure daydream is on, select clock. > clock settings, select 'when docked'
The clock is now white instead of blue, with no options to change it that I can see (may be a rom issue), otherwise desktop mode works much the same as in JB 4.1.x
Screen dimming - requires single tap to "wake" - looking for a way to disable
So I am running a stock Sprint HTC One (Android 4.4.2, software version 5.03.651.3) and for months now (for some reason, I thought I first noticed this behavior right after 4.3 got pushed out), there is a single behavior that has perplexed me, and despite trying various configuration changes, I cannot seem to get it to resolve.
I currently have all power-saving features disabled, screen timeout set to 1 minute, automatic brightness enabled (slider, which shouldn't make any difference, is set to the middle), daydream is disabled, and developer options are on with no screen timeout while charging enabled.
What seems to happen is that after about 1 minute (also the duration set for screen timeout, which initially made me wonder), the screen (while plugged in and charging) will dim slightly, maybe about 50% of the standard brightness when the phone is actively being used, and I have to tap the screen (not the double-tap I have been reading about, which supposedly isn't even implemented yet) just once to dismiss the dimming in order to register touch input.
At first, I checked Daydream a bunch of times, enabled it, disabled it, changed settings, and it seemed to have nothing to do with it, because when I did enable Daydream, I got the real screensaver or colored screensaver that I had chosen in the options.
I then disabled auto-brightness, set the manual brightness level to minimum, maximum, and a dozen levels in between, and I still got the dimming that required a single tap to restore use of the screen and brought the brightness back up to its normal level.
I made a bunch of power saving changes, enabled, disabled, to no avail.
Three factory resets later, (tested with no installed apps) I still have the same behavior. It seems like there is a setting that is enabling some sort of screen saver (that only dims the screen to about 50% of the set brightness level, but disables interaction from the user until the screen is tapped a single time) that is dismissed with that single tap.
I've gotten used to it, but it's really infuriating, especially in the car when I have it mounted on the dash for things like GPS, streaming audio (I just want to be able to see what song is playing if it's a new album), and other things that require a glance over to the phone. Sadly, in the car is probably the worst time for the dimming, since the ambient light outside makes the screen appear off when this "feature" kicks in.
I've spent a great deal of time searching/reading threads not only here, but on other mobile forums as well, and I cannot even find a reference to this issue that behaves the same way mine does.
This is my Hail Mary in the hopes that I really have missed something simple.
Thanks in advance for any ideas!
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
1. if you dont have a lockscreen then it cant show you notifications on it. duh, lol.
2. we all have known about this since before lollipop came out.
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
budorat said:
1. I see no reason why a notification could not be shown on the screen using ambient display even if I don't have a lock screen. It is not like I have actually turned the screen on yet.
2. And yet, when I tried searching for an answer to why my ambient display wasn't working, I found no mention of it at all, not in XDA or the web in general.
Thanks for clearing it up for me, it is clearly a feature of the phone.
Click to expand...
Click to collapse
if you dont have a lockscreen, then it has nothing to show the incoming message on. if no lockscreen, then it would just show in the status bar.
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
budorat said:
I understand your point simms22, but I think you may be missing mine. Does it have to be the lock screen that the notification is shown on when it arrives.
For example, msg arrive, screen turns on to show msg. If I do nothing then the screen turns off. If I haven't interacted with the screen, does the notification really need the lock screen to be displayed? I guess that I'm just not convinced that the lock screen is needed to display notifications when I pick my phone up, ie before I touch the screen. If I then interact with a notification then perform the interaction, but if I touch a part of the screen where is no notification, open the device.
The above would be mute if I pick the device up and press the power button to open the home screen.
I guess I look at things a little different, I design systems and interfaces for a living for the Dept of Defence.
I have found that the ambient display does not always activate when I pick the phone up, I'd say its about 90% reliable, have u found the same ?
Click to expand...
Click to collapse
yea, the way the code is written, there needs to be a lock screen to be displayed. i dont really use it anymore, but i found it to be around 90% as well.
Just to re-iterate, Ambient display is displaying the Lockscreen notifications, not SystemUI notifications, so to show the lockscreen notifications, Lockscreen must be on.
budorat said:
It appears that ambient display does not work when your screen lock setting is set to None.
I was showing a mate my Nexus 6 yesterday and started playing with a few settings. I noticed that all of a sudden my ambient display stopped working. I did some testing this morning and finally worked it out that when the screen lock setting is set to None, ambient display does not activate. Any notifications that come through stop appearing on the screen. Setting the screen lock setting to anything other than None ensures ambient display works once again.
1. Is this a known feature / situation for the N6 ?
2. Is anyone else experiencing the same behavior or is it just me ?
Click to expand...
Click to collapse
I totally agree. I upgraded from my 2013 Moto X, with Moto DIsplay, to the N6. I NEVER used a lock screen on the Motox, and enjoyed being able to just glance at the phone to know what was incoming.. its quite annoying that I can no longer get my notifications to show up on my screen without turning the phone on, and pulling the shade down. I'm on the computer all day, and have my phone setup next to me and use it to get a quick view of incoming work emails, with out taking my hands off the keyboard, or even stop typing for that matter.
If I would have known that the N6 was unable to work in this matter I would not have gotten it. I would have gone with the Moto X 2 instead.
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
tr3mm0r said:
Hi guys. Do you know any, preferably minimalistic, screen lock app that is compatible with ambient display? Have tried my fav Zui Locker with no luck.
Click to expand...
Click to collapse
I dont think it works with any.
That's what I was afraid of. Sticking with stock locker then since I love the new feature.
Sent from my Nexus 6 using XDA Free mobile app