Database Develop

Backlight problem

My screen will be darker after 10 sec.
I can set this again to 5 min. and after a few on and offs it will be back at 10 sec.
This is very annoying!
I thought i had found the problem, but it wasn't.
HKCU/ControlPanel/Backlight/BatteryTimeout setting up to 300. This is 5 minutes. It counts in seconds. But this isn't working.
Please can anyone help me?? A lot more have this problem.

I have the same problem, anyone the solution?

same problem here. I have call the helpdesk of htc they told me to do a hard reset. But it doesn't work for me. They also told me to return the phone when the problem stays afther a hard reset

vipinholland said:
same problem here. I have call the helpdesk of htc they told me to do a hard reset. But it doesn't work for me. They also told me to return the phone when the problem stays after a hard reset
Click to expand...
Click to collapse
i had the same "problem" and indeed, after a hard reset the backlight stays on 2 minutes as my heart wishes. i also use the the option to "auto adjust backlight. i have to admit it is strange...i don't see the connection.

KukurikU said:
i had the same "problem" and indeed, after a hard reset the backlight stays on 2 minutes as my heart wishes. i also use the the option to "auto adjust backlight. i have to admit it is strange...i don't see the connection.
Click to expand...
Click to collapse
yes, my backlight stay's also on for 1 minute(my setting)...hope the sound problem is also gone..

It is a bug in keypad locking
I think the backlight problem only occurs if you are using the keylock feature by pressing the end call button for a couple of seconds.
You can try it out yourself:
1) set your backlight settings to whatever you want and verify it works as intended.
2) Now just normally switch of your phone (not locking the keypad) by pressing the power button, switch back on and verify that the setting is still correct.
3) Then do a soft reset and again verify that the setting is correct.
4) Now lock the keypad by using the end call button (press a couple of seconds until locked).
5) Now unlock the phone and check the backlight settings: they are put back on the default values!! I guess it is a bug in the keypad lock functionality.
Btw, step 2) and 3) are just for verification, you may skip these to reproduce the bug.

Actually, if you use the lock feature of the device (for instance by enabling AutoDeviceLock in the registry, see tweak 18 in the stickied Diamond tweaks thread) the settings are also reset to the default values.
Is this the case for everybody? Or is it just me that it seems the locking feature contains bugs.

FYI...I had this issue from the start when I was running the Asia HK 1.34 ROM image. I flashed it using HardSPL and put the Europe 1.35 image on the device and have not had the problem since. All backlight values work normally as of now....I recommend this if your device is the HK ROM and you're having the issue. Not sure if it'll work for you, but it worked for me....

The solution is simply
You have to change DWORD LockLevel present in HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel\ to 0 (zero)
And now your time of standby don't change anymore

[Q] Volume control delay when the screen is off

When I try to change the volume for music while the screen is off a lot of the times the phone would not reflect this change until much later or when I turn the screen on, it's very annoying when it happens.
This is not a problem when the screen is on. I use ARHD for the most of the times and I went through (70.0-71.1-81.0-82.0) and the problem is still there, I don't think it's ROM related.
Anyone knows what's causing this? It's a weird problem that only affects the volume change while the screen is off.

Sackboy11 said:
When I try to change the volume for music while the screen is off a lot of the times the phone would not reflect this change until much later or when I turn the screen on, it's very annoying when it happens.
This is not a problem when the screen is on. I use ARHD for the most of the times and I went through (70.0-71.1-81.0-82.0) and the problem is still there, I don't think it's ROM related.
Anyone knows what's causing this? It's a weird problem that only affects the volume change while the screen is off.
Click to expand...
Click to collapse
Have you tried it with the stock rom?
Have you updated your firmware?
Do you have screen lock or saver installed?

Nexus 6 Screen Response Issue

Whenever I disconnect/reject a call on my Nexus 6 the phone screen doesn't respond!
I can lock the phone and use the screen swipe up to unlock it, but after unlocking it screen doesn't respond.
If I hold the power button and touch on power off or power on, it works, the phone powers off/restarts!
When unlocked, the nav buttons work. But the part above the nav bar buttons doesn't work. It however, works for the above mentioned cases
It's very irritating yet funny how it isn't responding.
Is the system frozen?
No, lock and unlock works, on screen nav buttons work, restart and power off menu works!
Is the touch screen not responding?
Nope! Consider the same answer as above
Can anyone help me with this issue please?
PS: Only started facing the issue after updating to Android 7.1.1 (Yes, I did manual OTA install)

Rajakodumuri said:
Whenever I disconnect/reject a call on my Nexus 6 the phone screen doesn't respond!
I can lock the phone and use the screen swipe up to unlock it, but after unlocking it screen doesn't respond.
If I hold the power button and touch on power off or power on, it works, the phone powers off/restarts!
When unlocked, the nav buttons work. But the part above the nav bar buttons doesn't work. It however, works for the above mentioned cases
It's very irritating yet funny how it isn't responding.
Is the system frozen?
No, lock and unlock works, on screen nav buttons work, restart and power off menu works!
Is the touch screen not responding?
Nope! Consider the same answer as above
Can anyone help me with this issue please?
PS: Only started facing the issue after updating to Android 7.1.1 (Yes, I did manual OTA install)
Click to expand...
Click to collapse
Without the basic logcat there is nothing that anyone will be able to help you with. Logcats are trouble shooting 101

zelendel said:
Without the basic logcat there is nothing that anyone will be able to help you with. Logcats are trouble shooting 101
Click to expand...
Click to collapse
Reinstalled the same image and rooted the phone! Issue resolved

Back, home, task button stop working. Why?

Hi,
I have a fresh new Motorola G5S and suddenly the three android buttons stop working (back, home, task).
If I tap them nothing happen every other parts of the screen works without problems.
This happen randomly and when it happen there is no way to restore the situation if not by repeatedly change the orientation of the screen and reboot the phone.
Is there someone else with this problem?
How can I solve it?

Bumping question

Samsung Galaxy A30( SM-A305G ) does not wake up. Any suggentions?

Hello friends,
My situation:
Out of the blue my phone stopped responding to the wake-up action. Every time I lock it, I have to restart for the screen to turn on again. The power button is working just fine, since I can go to recovery mode and use it to select options there. I even installed a somewhat wrong version of the TWRP recovery that would not boot to the main OS, but the power/lock button would work just fine in recovery, putting the phone to sleep and waking it up. I reverted the instalation after so I could boot to the main OS ( Android 10). I tried reinstalling(from an official image of the rom) the full rom, incluing everything from OS to Bootloader, and could not make the wakeup action work again. Once my phone is on, if I lock it, I have to force a restart to turn the screen on again. I even tried sending a direct command to the OS using adb shell input keyevent KEYCODE_POWER and KEYCODE_WAKEUP to no success. Even tough I made sure other common events like opening the camera (KEYCODE_CAMERA) were working when the screen was on, and I bet it was working when the screen was off too, but it would not wakeup the screen and I would not be able to see the camera view finder.
My phone is a Samsung galaxy A30, model SM-A305G, currently in Android 10.
I think I described the problem good enough, but If anyone have a problem understanding it, just let me know and I try to explain it better.
Can anyone help me out here? I tried a lot of things to not success.
Thanks!

I have the exact problem you described, did you find any solution ?

Shalesh said:
I have the exact problem you described, did you find any solution ?
Click to expand...
Click to collapse
flash official ROM with Odin or with twrp

I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?

Shalesh said:
I tried several different official roms by odin but nothing changed.
Power button and volume rockers works perfectly in recovery or download mode but in the OS volume rockers do not do anything (nor volume button commands from adb shell) and if I press the power button phone sleeps and never wakes up.
Very very strange at this stage I disabled sleep and with a amoled black bacground using the phone but I really wonder wtf is going on ?
Click to expand...
Click to collapse
very strange

I made furher research about the issue and here is what i've found.
Some videos mentioned same problem in similar samsung models and they stated that changing the daughterboard that connected to motherboard via screen flex resolved the issue. Other videos reflowed the connector in the motherboard side of the flex.
Also phone not responding the adb power commands while in sleep but responding fine when awake got me thinking there is a problem with a some kind of awake pin of screen. Probably there is a short or a missconnection in that pin. That's why solutions in the videos work I think.
It is definitelty not a software issue because it happens in every official or custom rom except in twrp (which does not put screen into sleep mode according "mScreenState" info)
It is not a hardware issue related to power button. Power button works perfectly fine in recovery, download mode and when awake.
Its a hardware issue that probably about the connection that sends wake up signal which maybe from motherboard side of the connection or maybe daughterboard side.
Not a real solution but I found a app called touch protector which has an option that you can disable the touch and set screen brightness to 0%, basically means normal off state for the amoled screens.
I set double click of volume down to sleep mode for touch protector. Maybe with some keymap editing someone can set powerbuttons function to not real sleep but touch protector's sleep. This will be best software solution.
In the hardware side if the problem is daughterboard it can be swapped easily but reflowing smd connecters in motherboard could be risky for me and I don't want to open the never opened device for not solving the problem.