Hello all!
I wasn't sure if I could post this in the dev forum or not, so it went into q&a:
My question concerns the "high brightness" mode that is available on the 'Torch' app in CyanogenMod 7 ('nexus torch').
I have tried the app on a LeeDroid ROM and the phone starts acting weird whenever I tried to use the 'high brightness' functionality. I am currently using Android Revolution 5.1.7 and I am experiencing the same problem.
Define "weird"?
- the screen goes black
- the hardware buttons at the bottom stay illuminated and no longer respond (no vibration - and yes haptic feedback setting is on)
- the leds start flashing at the "high brightness" instead of burning without interruption
- both leds flash at the same time as if the "strobe" option was selected, but it was not
- the flashing is erratic (no fixed intervals)
- the power button and volume rockers no longer work
- you have to remove the battery in order to 'unblock' the phone
From extensive googling and searching the xda forums, I have learned it might be a problem with the driver controlling the leds (e.g. the module that CM7 uses to light them with the torch app is not the same as the module that ARHD5.1.7 or LeeDroid uses - or maybe it's not a module at all and it's just a different driver compiled into the kernel?). In any case the problem, and my question, remains:
[!] "high brightness" is not working on Android Revolution HD 5.1.7
[?] How could it be made to work? Using another kernel? Compiling the CM7 led-driver for the kernel used by ARHD5.1.7?
This question could be interpreted dev-wise (kernel modules, compiling, /proc something something modification, etc.) or "basic"-wise (use another app, use CM7 , "ask in the dev forums", etc.)... The choice is yours!
Thanks in advance!
sstm
Well,for me high brightness causes overheating problems.On CM7 and on LeeDroid's Froyo rom with power notification widget(yes,it supports high brightness) I had reboots when using it for about half a minute.So I think there is no point in using it as it will damage your hardware sooner or later.These LEDs overheat too easily!
Hmm, with CM7 I have never experienced issues with the high brightness function. Sure it gets hot, but only after a couple of minutes - which is already way more than I'm looking to use it for.
For me, on other roms than CM7, the phone just immediately stops working, not after half a minute or so, just 'click the button' and viola - remove battery required...
Related
I tried to find a solution with the Board Search, but I had no result (just something for WinMobile).
When I slide my Kaiser, the backlight of the keyboard is just on for a short moment. I tried it several times, If I slide it not complete, the illumination will stay. The illumination just stops, when the device slides completely.
If I slide the device several times directly one after the other, the backlight stays each time for a different time after the device is slides completely.
I Tried it now with several Android builts. Does anybody has an idea how I can fix this issue or is this a normal issue and I have to live with it?
The keyboard backlight kicks on the moment the switch orientation "button" is hit by the keyboard slider. The backlight then stays lit for a pre-determined time (about 1-2seconds)
Thanks for the fast answer, but I couldn't agree. The orientation of the screen changes directly when I start to slide the phone (after approx 3mm). The Backlight starts at the same time. When I didn't slide compleate (as mentioned above) the backlight will stay until I finished the slide.
Is there a possibility to change the pre-determined time (the light is on)?
Some time ago, I thought it would be clever to make the backlight sensitive to the ambient light sensor, so that the backlight wouldn't be turned on if the room is bright. Unfortunately, the light sensor is too sensitive, so it keeps the keypad backlight off except when the room is very dark.
I have fixed this only one or two days ago. When l1q1d builds the next 2.6.32 kernel, it will have the corrected backlight.
If you are talking about a different kernel than 2.6.32, I don't know the status of the driver. I'm solely using 2.6.32 myself.
Thank you very much for the helpful feedback, n2rjt!
I use another kernel from this source:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
I found it over the forum search. Will the bug be also fixed in the kernel I can download over the link in your signature or do I have to wait until the kernel is updated? I will try using this kernel!
n2rjt said:
Some time ago, I thought it would be clever to make the backlight sensitive to the ambient light sensor, so that the backlight wouldn't be turned on if the room is bright. Unfortunately, the light sensor is too sensitive, so it keeps the keypad backlight off except when the room is very dark.
I have fixed this only one or two days ago. When l1q1d builds the next 2.6.32 kernel, it will have the corrected backlight.
If you are talking about a different kernel than 2.6.32, I don't know the status of the driver. I'm solely using 2.6.32 myself.
Click to expand...
Click to collapse
Hum, learn something new every day, I did not know that our phones 'had' an ambient light sensor?
Is this a known bug?
When I use the power management widget and toggle the screen brightness to the lowest. Then when I go to stand-by (by clicking powerbutton or automaticly) and try to activate the phone again the screen stays black (touch buttons light up but I can't use them).
I have to take out the batterie and reboot to get the screen back...
I'm so happy to see this.
I have exactly the same problem. My Wildfire S arrived this afternoon. I used it without any problems until about 22.30, then all of a sudden it wouldn't get out of standby anymore. The only way to get it working again is indeed by removing the battery for a second.
I did a factory reset (through the general phone menu) and now the problem has disappeared, but it could come back any second.
Other people experiencing the same problem?
This is a phone bought in the Netherlands where I live by the way, the black Wildfire S.
I had the same problem.
I had my wildfire s mount to usb... and using the navigon software while driving... then suddenly went to black screen with the keys activated.
I tried to enable the screen but with no luck.
When I unplugged the usb...I push the power button... and suddenly it came back to normal.
!!
very strange.
well... I found a sort solution for this.
If you do what you said.... the only way to enable it again is to plug a usb...and unplugged it.
!!!!!
The bug starting when we enable the lowest brightness!!!!!!!
I'm having the same problem. If you don't set the brightness to the lowest, it won't happen. So, this will be consideration between stability and use duration
Just the Backlight is turned off.
I have the same problem. Use an external light source and bring light to your wildfire S and you'see it is still alive. If you are able to find your brightness settings using the flashlight, increase it and you will have your old display again... It is definetly a bug.
Hi,
so any news on this bug or whether htc is doing something about it?
Just got my WF S with the most recent software and still has this bug which is very annoying. Would be great to be able to use lower backlight for nights/less battery!!
UPDATE: using continuous lightness, I found that whenever I choose light lower than 12% it stays dark and has the bug, please HTC do something about it!!!
Has this been fixed in a custom rom or does it presist in all roms?
I had it on original and custom (CM7.2) ROMS.
Think this is general bug, too bad. or someone does NOT have this bug??
I have this bug too. But u can Try to Pull the ring in the middel, Then the Screen shoudl appear again.
I do not have this bug.
Stock European ROM 2.3.5, jikantarus OC Kernel, BL unlocked and rooted
Hi,
Cyanogen comes with a flashlight app called "torch" that has a "high brightness" function - and it's *ridiculously* bright - brighter by miles than the htc one even on highest settings. But the APK crashes on ARHD (and from what I can see, all sense roms), and the app it's based on from the market, the "Nexus One Torch" does turn it on, but it flashes every 2s or so and turns the screen off, so you can only turn it off by taking the battery out (or as I was at the computer, adb reboot)
So is there a working high power torch app for sense roms?
Nexus torch works for me, you just have to press where the on button was. Exactly the same place. Although mine flashes too.
I'm currently on cm72-111128.2017-NIGHTLY-Defy.
Everything works fine except that recently I notice sometimes after I turn off the screen with power button the four function buttons are still bright (technically it's three b/c the search button seemed to be broken a week ago). And that might be the reason that occasionally the battery drains too fast.
My ways to solve the issue: 1) reboot; 2) go to Device settings - Button brightness and adjust the brightness level to whatever level and then back to the previous level you've set.
I know this might be a bug. Anyone has some idea to fix it? Our hero Epsylon3 has been devoted him to porting ICS and I'm afraid he won't have much time to care CM7.
This weekend I unlocked the bootloader and installed LineageOS 14.1 (rooted) on my LG G4 / UK h815. I have a flipcover case and I want to stop the screen turning on/off when I open/close the cover. There doesn't seem to be an option within Nougat/LOS 14.1 to disable this feature. I've found a few apps that claim to disable the proximity sensor but none fixed this issue so I presume it must depend on the magnet sensor instead? Has anyone else been successful in disabling this? How did you do it?
I flashed TWRP to my recovery partition following the instructions here:
https://wiki.lineageos.org/devices/h815/install
fastboot said it flashed OK but I have not been able to enter into TWRP by doing the VOLUME DOWN + POWER BUTTON dance. All I get when doing that is the stock factory reset menus so I have only been able to boot into TWRP by using fastboot. Is there something missing from that guide or is there a better guide thats guaranteed to enable me to boot into TWRP by using the boot button trick?
I knew the LOS camera wasn't going to be as good as the stock one so I used ES File Manger to dump the camera apk from the stock rom but the apk failed to install, claiming it was corrupt. Maybe it would've worked if I dumped it using a different app or maybe its not compatible with Nougat? Can I download a working apk of the stock camera from somewhere?
Finally, does Quick Charge work under LOS? Under the stock rom it would say 'Fast charging' when I use my quick charge charger and cable but it always says 'Charging slowly' under LOS whether I use quickcharge gear or not.
Thanks
The first showstopping (really annoying) bug I've come across with LOS 14.1 is that the screen randomly goes very dim, even when the battery is fully charged, and adjusting the screen brightness slider (if you can make it out) has no effect. The only fix when this happens seems to be rebooting.
I won't be putting up with that happening multiple times a day so unless someone has a fix I'll be looking for another ROM.
pfmdan said:
The first showstopping (really annoying) bug I've come across with LOS 14.1 is that the screen randomly goes very dim, even when the battery is fully charged, and adjusting the screen brightness slider (if you can make it out) has no effect. The only fix when this happens seems to be rebooting.
I won't be putting up with that happening multiple times a day so unless someone has a fix I'll be looking for another ROM.
Click to expand...
Click to collapse
Thats Live Display. Sensor is Reading Brightness and Adjust Screen brightness. Sometimes that takes 2-3 Sec.
With case You should disable it in Options otherwise you will deal with it most everytime.
Next:
Did you know what you are doing? Stock camera on custom rom? really?!! With LOS 14 u installed a custom kernel, so stock camera isnt supported anymore. NO driver / different Driver for camera as cause. Use Google Camera or other. use Search.
next:
Quick Charge work, but it is only a flaw of los that it shows slow charging.
other suggestions would be it is a kernel setting.
Hi uweork
Sounds like I need to disable live display to avoid the dim screen problem then. The screen brightness slider shouldn't stop working though, surely?
You say I should be able fix my flipcase screen problem by disabling it in options (do you mean Settings?) but where exactly? I have tried disabling 'Flip cover' under settings but that doesn't stop the cover turning the screen on/off when I open/close the flip cover. The only solution I can think of is working out which devices (under /dev/input probably) are used for the magnet and proximity sensors then writing a script that will delete them at boot but that seems like an awful hack to me - I'm hoping there is a nicer fix.
Thanks!
pfmdan said:
Hi uweork
Sounds like I need to disable live display to avoid the dim screen problem then. The screen brightness slider shouldn't stop working though, surely?
You say I should be able fix my flipcase screen problem by disabling it in options (do you mean Settings?) but where exactly? I have tried disabling 'Flip cover' under settings but that doesn't stop the cover turning the screen on/off when I open/close the flip cover. The only solution I can think of is working out which devices (under /dev/input probably) are used for the magnet and proximity sensors then writing a script that will delete them at boot but that seems like an awful hack to me - I'm hoping there is a nicer fix.
Thanks!
Click to expand...
Click to collapse
About your Problem with Flipcase is didn´t mention a thing. so ich dont know what to do.
But live display you find in Settings-> Display (i didn´t use Los 14 so maybe someone other can be of more help here)
pfmdan said:
Hi uweork
Sounds like I need to disable live display to avoid the dim screen problem then. The screen brightness slider shouldn't stop working though, surely?
You say I should be able fix my flipcase screen problem by disabling it in options (do you mean Settings?) but where exactly? I have tried disabling 'Flip cover' under settings but that doesn't stop the cover turning the screen on/off when I open/close the flip cover. The only solution I can think of is working out which devices (under /dev/input probably) are used for the magnet and proximity sensors then writing a script that will delete them at boot but that seems like an awful hack to me - I'm hoping there is a nicer fix.
Thanks!
Click to expand...
Click to collapse
Live display is a colour temp change (basically a night mode). Sounds more like a bug that you can't change brightness manually.
As for the flip cover, why do you want to disable it fully? I don't think you can even on stock LG can you?
I've fixed my screen woes with xposed and the Magnet Sensor Control module 1.1. It only claims to support Nexus devices but it seems to work fine with the G4 too.