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.
Related
I was noticing 100% awake time and poor battery life after updating to 2.2 and installing all my usual apps so I uninstalled them one at a time and after uninstalling LED light it went back to normal.
LED light widget works fine for me.
It worked fine for me too but it was causing the phone to always be running. Install the phone info app and check the battery history, it will always be at 100% running.
Why would you want it anyways? It has the flashlight app now which actually has 3 settings, low,medium and high.
aaron130 said:
Why would you want it anyways? It has the flashlight app now which actually has 3 settings, low,medium and high.
Click to expand...
Click to collapse
The led light app has a widget so when you hit and the light instantly turns on or off. The htc flashlight loads a picture of a flashlight which is pretty lame.
I like the new flashlight they put in, but it definitely needs a widget..
I use switchpro widgets right now
my flashlight/torch stopped working. i've rebooted and it worked for a while, but now it isn't working anymore... any help?
Are you using a particular app for this ? I have heard of some apps breaking these feature. LED's have a kinda high failure rate, relative to other lighting sources.. it is possible you burnt out or had a defective LED
If you use your LED flashlight as a torch (with a widget for example), it automatically stops after a while (perhaps a minute, I haven't checked that), that's meant to keep the LEDs healthy...
So no need to reboot your phone, just manually stop the torch (even if it has already been automatically stopped) and relaunch it.
I know this has probably been mentioned 1000 times but why doesn't anyone make an app that will let you manually turn the soft key lights on or off on a non-rooted dinc.
So many clock apps, etc have the option of forcing the softkey lights off, prove that it could be easily done since those apps are available for non-rooted dincs.
If anyone has a solution (other than the black e-tape one) please let me know. You can't see the buttons worth a crap unless the room is very well lit. in other words useless at night in the house with normal lighting. Yes I know I could cover the sensor with my thumb but there has to be a solution lurking out there somewhere.
thanks in advance.... johncal
There is. It's called Screen Filter. You can use it to do really low brightness (like when you use your phone in bed, not what she said ) and also manually turn softkey lights on or off. Actually, I'm not sure about forcing on, but it does turn off softkey lights for as long as you want.
Seriously, why do you want to turn them off? I sorta memorized the position of the softkeys.
I find the softkeys way too bright, so I've always used apps to turn them off in the past, never on.
In addition to trying Screen Filter as recommended above, give LEDs Hack a try. It's primarily designed to turn them off, but maybe the "ON" button will work... I'm really not sure.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
With CM7, I no longer have to use Screen Filter for turning off the softkeys, but I do still use it to dim the screen very low.
I really want to keep the softkeys on not off. I'm also running a stock non-rooted rom. Phone's fine for me the way it is except that I just want the ability to keep the softkey lights on. I guess I'm just surprised that no one has come up with a solution for that.
Screen filter is for turning them off and unfortunately, LED hack is for rooted phones. Thanks for the suggestions though.
byrong said:
I find the softkeys way too bright, so I've always used apps to turn them off in the past, never on.
In addition to trying Screen Filter as recommended above, give LEDs Hack a try. It's primarily designed to turn them off, but maybe the "ON" button will work... I'm really not sure.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
With CM7, I no longer have to use Screen Filter for turning off the softkeys, but I do still use it to dim the screen very low.
Click to expand...
Click to collapse
Where are the softkey settings in CM7? I looked under the autobrightness settings place but couldn't find anything.
Nightly 37 btw.
-CM7 ADR6300
dpwhitty11 said:
Where are the softkey settings in CM7? I looked under the autobrightness settings place but couldn't find anything.
Click to expand...
Click to collapse
Menu > Settings > CM Settings > Display > Automatic Backlight > Edit other levels
Lower / Upper = readings from the light sensor
Screen = the screen brightness you want based on the lower/upper light sensor values
Buttons = whether or not you want the softkeys on. Unfortunately, they cannot be dimmed (hardware limitations, from what I've read), so 255=on and 0=off
In the default configuration, for example, if the sensor value is 0-199, the screen will be set to brightness 25 and the softkeys will be turned on. If the sensor value is >399, notice that the softkeys turn off (button value changes to 0). If you want the buttons on all the time, set all button values as 255. If you're like me, and you hate the softkey lights, set all button values to 0.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
Click to expand...
Click to collapse
Byrong, youre the man. Did not know about this. Bye bye softkey lights. Thanks!
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...
The "new" flashlight application in the marshmallow update is rubbish. The old one had the ability to regulate brightness using the volume rocker and turn the ligh on and off using the power button.
The new one is
- laggy (it takes a while after you turn on the light on screen and it turns actually one)
- doesn't turn on light when the app starts
- power button turns off screen but not the light
- exiting the app doesn't turn off the light
While some of those feature might be useful it really is a major change to the original one. That one was very simple to use and swift in it's response.
Is there any way to get the apk for the original one? Been trying some other flashlight apps in the store but most of it is ad ridden crap.
any tips are greatly appreciated
Could not agree more, tried to download the old one and it just crash. Whoever's idea is this, should get fired.