Develop Bugs

[Q] How To Prevent Display from Dimming when plugged into Power

When I'm in my car, I have my GN mounted on a vent, and plugged into power. I'll often use this to check traffic with Google Maps, or for whatever reason, would like to keep the display on (preferrably full power since it's not running off the battery), and not dim after the preset time. I have yet to find a way to do this.
I have gone into Developer Settings, and enabled the "Stay Awake" when plugged into power, but this does not prevent the screen from dimming after the preset time. So this doesn't accomplish what I want.
On my prior Touch Pro 2, there was a simple setting - keep display on, full brightness, when plugged into power. Seems like a no-brainer to have this feature, but I'll be darned if I can find it.
Any ideas? Or Apps that will provide this functionality?
Thanks.
(Verizon Galaxy Nexus, Stock 4.0.2 ROM)

I think screebl might help. Not 100% sure that it will though
Sent from my Galaxy Nexus using XDA App

Thanks. As you said, it doesn't seem Screebl will do what I'm wanting.
There are a few other Apps, such as "Stay Awake" where you can configure it to keep the display on whenever a specified app or apps are running. I guess this might be an option.
But seriously, this seems to be a major omission in Android. I understand why one might want the display to auto-dim (although I can just turn it off when I want, so even this is questionable). But if it's plugged into power, surely the user should have a readily available option to keep the display on. For example, a "Never" option in the screen that has the various timeout options.
I'm new to Android - is there really no straightforward way of doing this??

Bump..
Still hoping for a straightforward way to keep the display at full power when connected to my car charger.
Thanks.

Widgetsoid has as one of its display switches to keep the display always on, and it does work. So I made a 1x1 widget that has that one switch, and use it when I want the screen to stay on. Not elegant, but functional.

Thanks for the suggestion; I'll check it out.
I'm still somewhat surprised that this pretty basic functionality isn't built into the OS itself, or that there aren't ready-made Apps to implement this.

DLCPhoto said:
Thanks for the suggestion; I'll check it out.
I'm still somewhat surprised that this pretty basic functionality isn't built into the OS itself, or that there aren't ready-made Apps to implement this.
Click to expand...
Click to collapse
I dont think google had car mode ready for release. Couple that with the fact the car dock with pogo pins hasnt been released either. Yes google f'ed up but im sure we will see it in future update. Or a dev will probably be nice enough to do something.
Sent from my Galaxy Nexus using xda premium

Settings, Developer Options, put a check mark on stay Awake.
Sent from my Galaxy Nexus

nxt said:
Settings, Developer Options, put a check mark on stay Awake.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What he said.... I am assuming the OP is a first timer on Android. This has been the way to do it since the stock G1 software

momentarylapseofreason said:
What he said.... I am assuming the OP is a first timer on Android. This has been the way to do it since the stock G1 software
Click to expand...
Click to collapse
Yes, I'm a first timer with Android, but I still do my research before posting. Did you actually read my initial post or the Subject title?
I have already enabled this setting. Yes, it does keep the screen 'awake' but it still dims after the timeout in Display Settings.
My post is how to keep the screen at normal brightness when plugged into power

I read your post. I agree, it is annoying. I have not found a solution to it and it has bugged me for years while in the car. I have had 4 android phones and it has been the same on all of them so it is not an individual phone thing, it is an android thing. My best suggestion is while in the car to have navigation turned on, that keeps the screen fully lit. I would think that some enterprising developer could delve into how the navigation mode keeps the phone at full power and come up with an app to do the same.

bmolloy said:
I read your post. I agree, it is annoying. I have not found a solution to it and it has bugged me for years while in the car. I have had 4 android phones and it has been the same on all of them so it is not an individual phone thing, it is an android thing. My best suggestion is while in the car to have navigation turned on, that keeps the screen fully lit. I would think that some enterprising developer could delve into how the navigation mode keeps the phone at full power and come up with an app to do the same.
Click to expand...
Click to collapse
Thanks.
I've been looking at a few Apps (Screen On, Screen Timeout Widget, KeepScreen), but there are questions about each of them, uncertain compatibility with ICS, etc.
I did discover that when I had a Video playing (podcast through BeyondPod), the display did stay undimmed while I was plugged into Power. Navigation also works this way. Really crazy that this isn't an available option in the OS.

This worked on my old Droid, haven't tested on my Galaxy Nexus yet -- but hopefully the app is ICS compatible: https://market.android.com/details?id=com.probeez.liteprofiles&hl=en
Setting Profiles Lite is limited to one rule -- so make your one rule this: When charging, screen timeout=never (since this actually changes the screen timeout on the basic level, instead of the workaround that the Dev Settings option triggers).
(The full version of Setting Profiles will of course also do this, and I'm sure you can also do this with Tasker.)

rjax said:
This worked on my old Droid, haven't tested on my Galaxy Nexus yet -- but hopefully the app is ICS compatible: https://market.android.com/details?id=com.probeez.liteprofiles&hl=en
Setting Profiles Lite is limited to one rule -- so make your one rule this: When charging, screen timeout=never (since this actually changes the screen timeout on the basic level, instead of the workaround that the Dev Settings option triggers).
(The full version of Setting Profiles will of course also do this, and I'm sure you can also do this with Tasker.)
Click to expand...
Click to collapse
Thanks - will check it out!

[Q] Why is my phone auto answering calls?

I'm running JB on a rooted but otherwise stock GS3 phone and for some reason it auto answers after the second or third ring. Doesn't matter if the phone is in my pocket or just sitting on my desk. I've dug through all the settings and cannot find any indication of being able to turn this "feature" off. Help please.....It wasn't doing this on ICS, it just started after the JB update.

SiriusDoggy said:
I'm running JB on a rooted but otherwise stock GS3 phone and for some reason it auto answers after the second or third ring. Doesn't matter if the phone is in my pocket or just sitting on my desk. I've dug through all the settings and cannot find any indication of being able to turn this "feature" off. Help please.....It wasn't doing this on ICS, it just started after the JB update.
Click to expand...
Click to collapse
I'm on cm10 but go into your phone dialer and hit the menu button pick settings and go from there.... sorry I can't help any further but its in there somewhere

neno2323 said:
I'm on cm10 but go into your phone dialer and hit the menu button pick settings and go from there.... sorry I can't help any further but its in there somewhere
Click to expand...
Click to collapse
Well, that got me closer then I was. I found the setting in that menu (Can't believe I didn't go there before) but the strange thing is the check box to "auto-answer" was unchecked. So I checked it then called my phone from my landline and it once again auto-answered as you would expect with the check box checked. I then un-checked the box and tried it once again and it now seems to be working properly.
Thanks for the assistance!

SiriusDoggy said:
Well, that got me closer then I was. I found the setting in that menu (Can't believe I didn't go there before) but the strange thing is the check box to "auto-answer" was unchecked. So I checked it then called my phone from my landline and it once again auto-answered as you would expect with the check box checked. I then un-checked the box and tried it once again and it now seems to be working properly.
Thanks for the assistance!
Click to expand...
Click to collapse
Glad it worked out...

If you not setall answering[/URL], it must be your mobile phone is broken, please go to repair it.

[Q] Touch Key duration bug - lights stay on when set to stay off

I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
I often use it to read in the dark, so I turn the brightness down and set the touch keys to never light up. However, after a while the lights come on and stay on until the setting is altered again.
Anyone else getting a similar issue?

Hi! I think it's a common bug. I have the same problem and read that many people have it.
I'm not aware of any permanent solution, so for now i keep mine at 1.5 seconds (I'd prefer them off, but thats the best I could find!)
PS: Sorry for my English!

No need to apologize. Your English is perfect.
Sent from my SM-N900V using XDA Free mobile app

If the problem's widespread, what devices/ROMs has it been seen on? Is it Galaxy-specific, I wonder.

Same issue here
rosyatrandom said:
I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
[....]
Anyone else getting a similar issue?
Click to expand...
Click to collapse
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.

I have the same problem, regardless of what I set the duration to. It never did this under Kitkat.

Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.

nismofreak said:
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.
Click to expand...
Click to collapse
Hi! I have same problem with Brazil version also.
Might it be related to that version only?

pantezuma said:
Hi! I have same problem with Brazil version also.
Might it be related to that version only?
Click to expand...
Click to collapse
could possibly be... anyone with this issue not on the Brazil version?

Yes, same problem here with my new Samsung Tab S 8.4 SM-T700, stock 5.0.2
Putting it to 1.5 secs is the best I can do for now. I'm looking around on the app store to see if there's a different app to control this that might work (aside, the Galaxy S6 came with no way to turn these off and you have to use a separate app to do this).

nismofreak said:
could possibly be... anyone with this issue not on the Brazil version?
Click to expand...
Click to collapse
Mine is stock US (or whatever the official region is).

Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.

levon9 said:
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.
Click to expand...
Click to collapse
I tried that with mine... won't work: no matter what I change the setting to they just stay on until I restart the device. I created a ticket with Samsung support last week, but no response from them so far.

Ah .. ok, that's interesting, thanks for sharing. Hopefully Samsung will issue a fix in the next update. Nice tablet otherwise.

I'm sure most, if not all, knew this, but it is definitely a software issue. I flashed CM 12.1 the other day and the touch keys stay off. Perhaps someone can look into the stock firmware and see if there's a way we can fix it ourselves?

Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!

giancian said:
Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!
Click to expand...
Click to collapse
I never use power saving mode, because I'm almost always near a charger, and I also had this issue. I don't think power saving mode has much to do with it. Not directly, at least.

Hi, I'm not using power savings mode, but have the same problem, so I'm not sure this mode is a factor (at least a sole factor).

Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.

pantezuma said:
Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.
Click to expand...
Click to collapse
Hi,
I suggested this app earlier upstream, however, it ended up not working for me. Not sure how it's working for you, but happy it is. (FWIW, I never use power savings)

Unknown wakelock keeps pixel awake 100% of the time

Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock

Purchase Ex Kernel manager and turn that wakeloke off threw kernel using that app

Right here!

petiolarissean said:
Purchase Ex Kernel manager and turn that wakeloke off threw kernel using that app
Click to expand...
Click to collapse
I did so, but the wakelock wasn't there.

Try service disabler its free
---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------
Have you tried customs roms and is it still doing it?

petiolarissean said:
Try service disabler its free
---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------
Have you tried customs roms and is it still doing it?
Click to expand...
Click to collapse
Yes I did and it persists.:crying:

thetrangdam said:
Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock
Click to expand...
Click to collapse
You flash stock firmware, roms etc and reset, and problem persists? Have you considered that there's no feasible way to remedy this? As in, your phone has defective hardware?
Otherwise, it would have to be a phone hacked by CIA with custom hardware that is impervious to resets and firmware flashes.
Think about it...

Contact google and there pretty easy going and will go out of there way replace phone.Ive went threw 5 pixel and every time they have jump threw hoops to make me happy.Phone returned 3-5 days every time.

Maybe it's malware!?
Read this: https://www.google.de/amp/s/amp.reddit.com/r/Moto_Z/comments/5ox4ab/constant_wakelock/
Sent from my Pixel XL using XDA Labs

nabbed said:
You flash stock firmware, roms etc and reset, and problem persists? Have you considered that there's no feasible way to remedy this? As in, your phone has defective hardware?
Otherwise, it would have to be a phone hacked by CIA with custom hardware that is impervious to resets and firmware flashes.
Think about it...
Click to expand...
Click to collapse
That could probably right.
At first, my device kept showing a persistent notification "USB Supplying Power to attached device",
And I could not charge my device unless I reboot (then it will appear again later).
I googled & figured some people had the same problem and got it solved by cleaning the charging port
on the phone so I did the same.
It stills show up time after time, but now I can choose to "charge this device" from the popup & charge fine.
But the kernel wakelock, which I believe belongs to usb otg or something like that, still keeps my device awake 100% of the time, and drain the battery.
petiolarissean said:
Contact google and there pretty easy going and will go out of there way replace phone.Ive went threw 5 pixel and every time they have jump threw hoops to make me happy.Phone returned 3-5 days every time.
Click to expand...
Click to collapse
Appreciate your help.
Unfortunately, I live in a country where Google isn't available, and purchased this device from private vendor,
so there's no way I can RMA this now.
spezi77 said:
Maybe it's malware!?
Read this: https://www.google.de/amp/s/amp.reddit.com/r/Moto_Z/comments/5ox4ab/constant_wakelock/
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Maybe not.
It happens no matter what rom, kernel I'm on.
Since I had the persistent "USB Supplying Power to attached device" time after time,
it's likely that wakelock thinks I'm plugging something into the usb port all the time,
and keeps my devices awake.
I've cleaned the port with tooth pick, some alcohol & air duster but the wakelock hasn't gone away.

Caused by USB I've seen before in BBS thread, I think it's due to a poor USB port on the device contact Google to see your options

I agree @liam_davenport. I did a little digging through some xda threads and people claimed they had that wakelock if they plugged their phone in wrong, do to the USB port being sloppy. There is also something in our device tree called "tcpm logging" that is related to that number, doing a little research now to see what it is/does.

let me talk to my cousin,he works at google.Let me throw problem at him

thetrangdam said:
Hello guys,
I have encountered this 9-0022 kernel wakelock ever since I purchased this Pixel XL, and it keeps my device awake all the time.
It persists no matter how many times I factory reset or flashed a different factory image.
Google shows no answer of what it is and how to block it.
Has anyone faced this problem?
Android version: 8.1.0 April, Stock
Click to expand...
Click to collapse
I've only heard of this problem with people running Android P preview2. It seems using the finger unlock on back of phone, some people tap it when the screen begings to dim and taping fingerprint brightens screen. But what I was thinking, that doing that even without preview2 might cause similar effect.
So you could try disabling that feature might help. It seems that their connected somehow.

fiverings said:
I've only heard of this problem with people running Android P preview2. It seems using the finger unlock on back of phone, some people tap it when the screen begings to dim and taping fingerprint brightens screen. But what I was thinking, that doing that even without preview2 might cause similar effect.
So you could try disabling that feature might help. It seems that their connected somehow.
Click to expand...
Click to collapse
Didn't he say Android 8.1, stock? He flashed it many times?

SOLVED: Stay connected when device sleeps (EVR-AL00)

PROBLEM SOLVED
Mate 20X (EVR-AL00; Build no. 9.0.0.136). I left my phone at home while downloading the new games via our Wi-Fi. But when I got back, I noticed that it has not downloaded any more data since I left it.
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
------------------------------
TRY THIS:
AngelDeath said:
@the_passerby5981 I figured it out, and boy your going to hate sending yours back, I was right, it is tied to something. I kept thkinking and kept coming back to this thread knowing you and I were missing something, and I found it from your screenshot and others, then tested it on mine and bingo. The reason its disabled is because it is tied to the SIM card. So that setting is tied to a sim card, and it didnt work on yours or mine because we were both testing it out without a SIM, and as soon as I put mine in to see if I was right, it enabled to turn on or off.
Click to expand...
Click to collapse
the_passerby5981 said:
BUG FOUND! (Problem solved).
Android 8 had the option under WLAN and option to disable staying connected to WLAN and MOBILE as separate.
In Android 9, they are baked together under Battery. Thus, Stay awake when device sleeps gets DISABLED WHEN NO SIM IS INSERTED.
Click to expand...
Click to collapse
Moderators, please close the thread. I seem to not have enough privileges to do it myself.

Mine was checked on but a good one to know. Need a good week to really go thru the settings and get them set how you like. Like a maze with secret passages.

the_passerby5981 said:
Mate 20X (EVR-AL00; Build no. 9.0.0.136). I left my phone at home while downloading the new games via our Wi-Fi. But when I got back, I noticed that it has not downloaded any more data since I left it.
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
Click to expand...
Click to collapse
Thanks for the info that's been pissing me off for awhile now

Cccmachins said:
Mine was checked on but a good one to know. Need a good week to really go thru the settings and get them set how you like. Like a maze with secret passages.
Click to expand...
Click to collapse
Did you do it yourself? Or did it come that way?

the_passerby5981 said:
Did you do it yourself? Or did it come that way?
Click to expand...
Click to collapse
Strange I have the same phone as you with the same update and I have the option to turn it on and off.

On EVR-L29 it was off, so i turn it on myself now Thanks.

the_passerby5981 said:
Did you do it yourself? Or did it come that way?
Click to expand...
Click to collapse
I think I had to turn it on. Been over a week since I got it. Changed so much stuff can't remember. Old-timers setting in.

hughey2k2 said:
Strange I have the same phone as you with the same update and I have the option to turn it on and off.
Click to expand...
Click to collapse
Look!

the_passerby5981 said:
Look!
Click to expand...
Click to collapse
That's a beach. AL00 here 136 and I still have the option to turn on or off. Ain't playing with or I'll lose mine. Or go blind
---------- Post added at 08:53 PM ---------- Previous post was at 08:30 PM ----------
Goofy ass Hicare iPhone wanna be says I feel your pain and rest your phone. I wanted to tell her to go where the sun doesn't shine but just doing her job. But she maybe right. May have to reset

the_passerby5981 said:
Look!
Click to expand...
Click to collapse
That's really strange have you ever restarted the phone since the new update. If that doesn't work you can try to reset all settings and see if that works there's no reason why yours is blocked and other people's aren't unless you have some kind of aggressive battery manager or something.

hughey2k2 said:
That's really strange have you ever restarted the phone since the new update. If that doesn't work you can try to reset all settings and see if that works there's no reason why yours is blocked and other people's aren't unless you have some kind of aggressive battery manager or something.
Click to expand...
Click to collapse
Resetting the settings did nothing. Gonna give a shot at resetting the phone. I didn't tinker with any other settings coz I wanted the phone to be up and running at once. It only happened that I hit a snag with this issue.
TAKE NOTE: My unit is running on a "China ROM".

hughey2k2 said:
Thanks for the info that's been pissing me off for awhile now
Click to expand...
Click to collapse
Do you also have an EVR-AL00 running on 9.0.0.136?

the_passerby5981 said:
Do you also have an EVR-AL00 running on 9.0.0.136?
Click to expand...
Click to collapse
Yeah I have the same phone.

same, able to change no problem

I tried last night to toggle thinks on and off to try to get mine to gray out. I couldn't. I tried again with HiCare but he needs some info for your phone. Give them a try. You need that option.

the_passerby5981 said:
Mate 20X (EVR-AL00; Build no. 9.0.0.136).
The culprit? The option Stay connected when device sleeps under the battery settings is DISABLED (neither ON nor OFF). Anyone else has this experience? What can be done about it?
Click to expand...
Click to collapse
I also have the EVR-AL00 with Build Number 9.0.0.136. I have no problem to enable/disable the option. See the pictures.

hughey2k2 said:
Yeah I have the same phone.
Click to expand...
Click to collapse
Just to clarify, you have the same phone and build number as mine, AND the same experience? Cannot toggle "Stay connected when device is asleep" ON/OFF?

the_passerby5981 said:
Just to clarify, you have the same phone and build number as mine, AND the same experience? Cannot toggle "Stay connected when device is asleep" ON/OFF?
Click to expand...
Click to collapse
Yes I have the same Phone and build number but I can toggle the "stay connected when device is asleep"tab on and off

1. So, there are about 5 users here with the same model number (EVR-AL00) and build number (9.0.0.136). Some can toggle "Stay connected while device sleeps", while--like me--hughey2k2 cannot. I cannot.
2. If it were a software problem, then all of us should have the same experience.
3. Does this point to, possibly, a hardware-related problem peculiar to the specific production batch? (Just to spell it out I mean, hughey2k2's phone were produced in the batch and there was a problem in production--possibly hardware--that could be the cause).
Comments?
EDIT: hughey2k2's unit does not have the same problem.

hughey2k2 said:
Thanks for the info that's been pissing me off for awhile now
Click to expand...
Click to collapse
If you can toggle ON/OFF, then what is pissing you off about it?