Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
this work with zeus?
Yep, I've 6.31n and work good.
lean7 said:
Yep, I've 6.31n and work good.
Click to expand...
Click to collapse
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Used it once, in february...its not this good
But does the job
Sent from my LG-P970 using Tapatalk
This app is known here. There already was a discussion with it.
From the app in Google play:
"We are aware of the issues with Optimus Black since the 2.3.4-update"
ciplukzz said:
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Click to expand...
Click to collapse
You were right! It's not working now :S
Thankyou for sharing this app!
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
If you want the source my build directory is hosted here: http://www.mediafire.com/?hmx5wpbwx00c47l
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out (sorry for the format, can't post links yet - please remove the spaces):
Code:
www . mediafire . com / ?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Good aproach! Take into account that is normal that the kernel switch off leds on battery... think in the leds allways on... I have had some kernel-related atempts to correct this... but atm no luck.
Regards!
When the screen is off and the device is on battery it is doing some sort of polling every few seconds to check and reset the LEDs rather than just a trigger when the screen turns off and that is what makes the app not work.
I tried a few different ways to reset the LEDs but the only way that would work is to force them off by writing a 0 into led_onoff followed immediately by a 1 into led_onoff. It wasn't enough to just echo 1 > led_onoff, I had to do a 0 first. However, with power connected, just the echo 1 > led_onoff was all I needed.
As far as I could tell, the led_onoff seems to only part of the 970 device code. I'm guessing that the other devices don't have an issue because they don't have to activate the LEDs in that way.
One other thing I tried was removing all write privileges to those files after turning on the LEDs to see if the system was writing a value into them to turn them off. They were still turned off so I kind of figured it's something in the kernel itself manually resetting things.
this should be good if work in customs ROM...to notify us for new message and etc
have a problem
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
lean7 said:
You were right! It's not working now :S
Click to expand...
Click to collapse
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
read the first page pls. it isnt working with 2.3.4 we know that.
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
Did you try the one I posted in post 9? http://forum.xda-developers.com/showpost.php?p=28571222&postcount=9
It sort of works in blink mode (best with repeating non-fading pulse with a lit time of 2000ms).
I'm using it in Zeus v6.35 at the moment.
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
My only wish is that it was all 4 lights instead of just search, but who cares, in a month Ill probably prefer just search and be happy
Thanks for this find, I was desperate for it
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Still not working on 2.3.4
working on ics?
New version of LG Notifications
jn83 said:
Still not working on 2.3.4
Click to expand...
Click to collapse
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS: of course all credits go to the original creator of Lg Notification application. I only try to fix this to work on Lg Optimus Black on Gingerbread.
Dan
danfizesan said:
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS:
Dan
Click to expand...
Click to collapse
There is a problem with repeat fading pulse. It eats too much battery. Constant light it is much battery friendly.
Related
Or at the very least extend it? It is definitely a top 10 pet peeve of mine with my G1. The few seconds that the keyboard is on is just too damn short.
Thanks.
PS- Yes I did search. Found nothing useful in the results.
hrm
Most people want it off
Power Manager used to do this, but it doesn't anymore. I'm with you, it's almost impossible to use the keyboard in dim/no light with the short illumination it gives.
Well here is the source to the DarkKeys hack
Im sure you could easily reverse the code to make them stay on instead of off
Or you could ask the dev to add it as an option they might be willing to
http://code.google.com/p/darkkeys/source/browse/
pentace said:
hrm
Most people want it off
Click to expand...
Click to collapse
I'm not most people. And I doubt most people are touch typists, because that is what you have to be if you want to use the G1 in the dark after the backlight has gone out. Sure I could roll the trackball. Which moves the focus on the field and then I need to change that focus again which highlights everything so then I need to deselect everything and I can get back to typing.
Thanks but no. 5 seconds before the backlight is out is too damn short. And I can guarantee you that the light they are using is LED based. You might get 5 minutes of extra battery life by turning it off. Maybe.
Someone made an app to turn it off... Backlight off I think. If you contact them and get the source code for it from them, then it wouldn't be very hard to find someone to modify it to do what you want...
Ohsaka said:
Someone made an app to turn it off... Backlight off I think. If you contact them and get the source code for it from them, then it wouldn't be very hard to find someone to modify it to do what you want...
Click to expand...
Click to collapse
I posted the source to the code 2 posts up
Dark Keys 2.0 aparently let you turn backlight on or off, haven't tried it yet gonna find it now...
BrightLight Off
BrightLight Off will do the job for you.But if want the light to stay on just don't stop typing
jacsonmoore3 said:
BrightLight Off will do the job for you.But if want the light to stay on just don't stop typing
Click to expand...
Click to collapse
Obviously, you don't get the point.... Or, were you just making a smart remark?
I tried Dark Keys - but, with 1.6 it just force closes every few seconds. I would try to mess with the code... But, I'm not experienced enough for serious dev work and I dang sure wouldn't know how to alter the compatibility from an earlier, say 1.1 release, to work on the newer 1.6 release.
If anyone could help with this I'm sure some users would appreciate it. I know I would. I would like the option for to turn the kb light on when it was opened and off when it was closed.
it would probably require a service to run, which would slow down the phone. i just move thr trackball to turn the lights back on...
Freedomcaller said:
it would probably require a service to run, which would slow down the phone. i just move thr trackball to turn the lights back on...
Click to expand...
Click to collapse
I don't think (although, I am probably wrong) that Android uses services like Windows. It seems to me that opening the kb would start prompt an intent to turn on the backlight and closing it would turn it off. I don't know that it would cause any more memory/resources in Android to run.
Has anyone found a solution to this problem yet? I don't have many complaints about the G1, but the keyboard backlight issue is definitely one of them...
Look what I just received on my RSS feed:
Translated from Italian
I'm studying it to see how it works, can someone help me?
Why don't you just link to the official thread? http://www.swedroid.se/forum/showthread.php?t=38703
I can tell you it's working!
/edit
Works like this:
When screen is off the app checks every 30 sec to see if there is any new incoming email, sms/mms, calls. If it's returned as true the lights of your touch buttons light up. It lights up every 10 sec for 3 hours. If the phone is not wakened withing that time, it stops.
The first time you have to press "start" to start the process. If you tick the "start service on boot", it's not necessarily to press start.
Test it with the "test" key.
You can also set the default value of the brightness of the buttons with this app
Think that's about what is important from that post.
Very nice, thanks for the hint.
I was watching the fact that is fulfilled by Log messages, is it normal?
Perfect Thnx a lot for the link.
Missed this feature since my change from Desire
Novek said:
Why don't you just link to the official thread? http://www.swedroid.se/forum/showthread.php?t=38703
I can tell you it's working!
/edit
Works like this:
When screen is off the app checks every 30 sec to see if there is any new incoming email, sms/mms, calls. If it's returned as true the lights of your touch buttons light up. It lights up every 10 sec for 3 hours. If the phone is not wakened withing that time, it stops.
The first time you have to press "start" to start the process. If you tick the "start service on boot", it's not necessarily to press start.
Test it with the "test" key.
You can also set the default value of the brightness of the buttons with this app
Think that's about what is important from that post.
Click to expand...
Click to collapse
checks every 30 sec? is it possible a battery drain issue or let the phone never sleep?
that was my thoughts too... Will check it out for a day and see.
Sent from my LG-P990 using XDA App
Wow, looks&works nice.. What about battery life impact?
I'm afraid it will drain terribly the battery... if someone can help me understand where is the code that controls the leds, I can try to set it up so that it's activated by notifications, instead of checking for them... we might need Paul's help here!!!
OK that's very nice and handy indeed, but i also wanna know about the battery drainage, on the otherhand using the app (or hidding menu) to reduce the output power of the leds you can conserve lot's of energy tho .
Yeah I'm not sure that's the way it's supposed to be done. While I am grateful for the dev of this app, I think the goal is to have these LEDS tied in to the Android Notification system itself, because any other way will be a drain on the battery.
Tegra2 is awesome because it takes up so little power in idle. If we have an app checking every 30s, the SoC is no longer idle, per say. If we increase the timer to let it idle, it's no longer a real notification system. Hence, this is probably not the way to go.
No I'm not sure where this is handled in Android though. If i'm not mistaken, a setting activated or not on the ROM, to tell the OS wether the phone has or not a LED for notifications. If so, we just need to rerout those acceses to the button LEDs. Then again, wtf do I know lol.
If anyone wants to point me in the right direction I'd love to look into that more closely (I dev C++, Java so should be able to work something out) Pm me.
There could be some push notification that goes to the notification bar, that may be used to also trig this software?
I guess it doesn‘t wake up the machine but runs as a background process.
Sent from my LG-P990 using XDA App
I've used it for a day now, fr6, 1200mhz overclock. After a lot of texting, and intense music playing I still have 30% battery. At the bottomline, I haven't noticed any impact on the battery life.
Sent from my LG-P990 using XDA App
I'm having a go at writing my own version that can do both brightness settings and notifications. So far I've caught up to Paul's app feature-wise, and will tackle notifications in a bit (hopefully in a more battery friendly way).
If I'm first done then I might put it on the market, but otherwise it's a great learning exercise for me!
Sent from my LG-P990
My fix is a 80$ liveview but I'm sure that's a little out of context.. still wish this phone came with an led notification. :/
Sent from my HTC Magic/Dream using XDA Premium App
thank you for the app,but there some problems with the app.the phone will reboot when you got some calls and messages.
Sent from my LG-P990 using XDA App
tiwiz said:
I'm afraid it will drain terribly the battery... if someone can help me understand where is the code that controls the leds, I can try to set it up so that it's activated by notifications, instead of checking for them... we might need Paul's help here!!!
Click to expand...
Click to collapse
Code:
echo 20 > /sys/devices/platform/star_touch_led/wled
20 is the brightness value i think.
I've used mine for 7 hours now, 50% left.
I've used wimp for music, wifi hotspot and xda/web. That's prof it's good enough for me...
Nice app! Just what I was looking for!
Hi people, I got my phone today, and as you do, you set it up how you like it, I set it to keep the home, back and settings keys to light all the time, and it did. I did a OTA up software update, and now, even though ive put it to keep keys lit at all time, it still goes off after a few seconds?any one else had this problem?
OrionCarl said:
Hi people, I got my phone today, and as you do, you set it up how you like it, I set it to keep the home, back and settings keys to light all the time, and it did. I did a OTA up software update, and now, even though ive put it to keep keys lit at all time, it still goes off after a few seconds?any one else had this problem?
Click to expand...
Click to collapse
Got my phone today with 10d on it. Almost immediately got an update to 10f and exactly the same - the front key lights always turn off after what I believe to be 1.5 seconds, no matter how I set it
Hm...same here. Lights turn off after 2-3 sec.
Sent from my LG-P880 using xda app-developers app
mali_veseljak said:
Hm...same here. Lights turn off after 2-3 sec.
Click to expand...
Click to collapse
Going to raise this with LG Tech Support once their e-mail contact page is back up and running
lol >> it is fun to say that the light for front keys turn off after 1.5 or 2 seconds
You can make it long from the setting and HERE THE PROCEDURE ..
PLEASE GO TO ( Settings > Power saver > Front key light ) there is Gear button beside it >> press it and change the period of time ..
Don't forget to press on Thanks button if I help you Guys
Best regards,
ozeer said:
lol >> it is fun to say that the light for front keys turn off after 1.5 or 2 seconds
You can make it long from the setting and HERE THE PROCEDURE ..
PLEASE GO TO ( Settings > Power saver > Front key light ) there is Gear button beside it >> press it and change the period of time ..
Don't forget to press on Thanks button if I help you Guys
Best regards,
Click to expand...
Click to collapse
Not exactly, no. That setting gives you the option of '1.5 seconds' or 'Always off' and only applies to how the lights work during Power-Save mode, not normally.
Nice try to make us look stupid though :banghead:
SimonTS said:
Not exactly, no. That setting gives you the option of '1.5 seconds' or 'Always off' and only applies to how the lights work during Power-Save mode, not normally.
Nice try to make us look stupid though :banghead:
Click to expand...
Click to collapse
lol >> I am sorry , but I like kidding with anyone ..
Yes , you're right with that the option for the light of front keys is 1.5 or off
_______________________________________________________________________
I found the solution for that now
Please GO TO ( Settings > Display > Front Key Light ) >> there is option is that " Always On "
Please try that and replay .. I am waiting
Best regards,
ozeer said:
lol >> I am sorry , but I like kidding with anyone ..
Yes , you're right with that the option for the light of front keys is 1.5 or off
_______________________________________________________________________
I found the solution for that now
Please GO TO ( Settings > Display > Front Key Light ) >> there is option is that " Always On "
Please try that and replay .. I am waiting
Best regards,
Click to expand...
Click to collapse
I'm not sure if you are intentionally trolling or just stupid.
It is quite clearly stated that setting to 'Always On' makes no difference at all.
Do you have v10f on your phone? Do you even have this type of phone?
Calling all owners. Is there anyone out there?
OK, so I have raised this with LG Tech Support and they are telling me that it is an "Isolated Issue". Here is the copy of my emails with them;-
ME: I purchased this phone yesterday in the UK. I immediately got an OTA update to v10f. With this version there appears to be a bug. The "Front key light" setting doesn't change anything. I want to set it to "Always On" so that the lights are on whenever the screen is, but the button lights still go out after about 2 seconds.
This appears to be a software problem as other people on the forums have reported the same issue.
Click to expand...
Click to collapse
THEM: Based on the information you have provided me with, and after reading through your query, I would recommend that this is a standard setting on the handset unfortunatly unless in use the LED lights will power down, if you touch the LED lights they should illuminate again but unfortunatly there isnt a setting that you can change. Unfortunatly we are unable to do anything here at LG currently but we will raise this as a issue and you will have to wait for another update or bug fix if this is a software issue.
Click to expand...
Click to collapse
ME: This is definitely NOT a standard setting. Under software v10d this worked perfectly - as long as the screen was on, the buttons were lit up. The setting has the option of "Always On" and the fact that it doesn't work means that something is broken in the code. I have looked on XDA-Developers.com and found that I am far from the only person with this problem. There is also a partial solution which may point to the problem;-
"EDIT: OMG, changing the content of this file to 1 did fix it instantly! I'm not sure, if this app caused this behavior to happen but if anyone has the same issue, the exact location of the file is:
/sys/devices/platform/button-backlight/leds/button-backlight/br_maintain_on
EDIT 2: the file will be set to Ɔ' on each reboot, even with read-only permissions and when this app is not installed. It looks like this could be a firmware bug?
Maybe this will help - but at the moment I am seriously considering returning my phone and getting something by a different manufacturer as this is more than just annoying. Having those buttons flick off so quickly is a real nightmare when you are actually using the phone.
Click to expand...
Click to collapse
THEM: Based on the information you have provided me with, and after reading through your query, I would recommend that this appears to be a islolated issue, as said before i will raise a Voice Of Customer which means that i will be raising this issue to head office and they will read this and look into the case. Unfortunalty i must inform you that your handset is covered by LG for 12 months under warrenty but you will fully void this by changing the codeing or altering the data inside the handset in anyway, this will also mean that the LG engineers will not repair this as it will be deemed as rooted.
Click to expand...
Click to collapse
Can anyone out there confirm that they are running v10f and that the screen buttons work correctly for them. It would be interesting to tie this down and see if it is a problem with all v10f versions, if it is location specific, or if it maybe only effects certain batches of the phones.
---------- EDIT -----------
Thanks to this post by k1337Ultra, it appears that this can be fixed by disabling and then re-enabling the Automatic Brightness. Hope this helps others - very annoying though to find the solution buried in a totally irrelevant thread
---------- EDIT 2 -----------
And it works after a reboot as well. Yippee!!!!!
Good news for that you have fixed your problem .. Don't blame me with that because I am using V10C firmware and it is superb with no problem on LED buttons
Best regards,
ozeer said:
Good news for that you have fixed your problem .. Don't blame me with that because I am using V10C firmware and it is superb with no problem on LED buttons
Best regards,
Click to expand...
Click to collapse
Thanks - it would also have been helpful if you had either;-
1) mentioned that you were using an old version of software
2) actually read the OP and my post, realised that we were talking about a problem only in the latest version, and realised that posting would be fairly pointless.
its nice to see im not the only one that has the issue!! similar to you, if I enable the auto brightness the buttons stay lit fine, soon as I put it back, it goes back to going off after a few seconds!very annoying given they are not real buttons so can be a pain to find, grrrrr!
OrionCarl said:
its nice to see im not the only one that has the issue!! similar to you, if I enable the auto brightness the buttons stay lit fine, soon as I put it back, it goes back to going off after a few seconds!very annoying given they are not real buttons so can be a pain to find, grrrrr!
Click to expand...
Click to collapse
I am following it up with LG Tech Support and will post back here if they actually tell me anything useful.
ok simon, doubt you will you get any sense out of them, their backup isnt up to much sadly! good luck
It's just to inform that the keys light are working like they should in V10G
Sent from my LG-P880 using xda app-developers app
RuedasLocas said:
It's just to inform that the keys light are working like they should in V10G
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
cool, cheers for that!! have to wait untill it comes here by the looks of it!:good:
The new official V10H Firmware solves this bug also
I like to keep the battery in my Note as charged up possible which means I plug it into the charger most times I come home and so I have to unplug it whenever I leave ... and so both coming and going the phone display turns on when I plug/unplug it and 99.9% of the time I don't want this. If the display is off it should just stay that way! For some reason I find this unwanted behavior so obnoxious I was going to get rid of the phone ... until I realized that getting a new phone might likely have the same problem since it seems to be quite common. I'm not so sensitive to other things not quite working the way I would like, but that one is so obviously crazy and happens so many times per day that it bugs me more and more each day. I've never seen this discussed, so my main confusion on this issue is why this doesn't seem to bother anybody else.
Anyway I noticed in the Revolt Rom there is a feature in the list called "Wake up on charging".
Does having this feature imply that one can disable it ... i.e. not have it wake up when the charger is plugged in?
Also does this mean that you can also disable Wake up when charging is terminated by unplugging the charger?
Please say yes and I will just die now and go to heaven.
If my interpretation of this feature is correct ... can most modern roms do this or is this unique to the Revolt rom?
Thanks
~Paul
~Paul
wrong section to post q
I have found option in developer menu but that states to keep device awake.
Usually screen dims and sleeps after a while.
I press powerbutton to put screen into sleep.
Another workaround could be to use tasker and program it to set screen off upon adding charger.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Usually screen dims and sleeps after a while.
I press powerbutton to put screen into sleep.
Click to expand...
Click to collapse
Yes it dims after 10 minutes (in my case since that is my sleep delay setting), but why should I waste 10 minutes of power or why should I have to press the power button to avoid this? My point is that this makes no sense. It would make way more sense for the screen to turn off when I tell it to and not otherwise.
> Another workaround could be to use tasker and program it to set screen off upon adding charger.
Now you're talking. A suggestion that actually worked. I had never heard of tasker. I paid the 3 bucks, then spent an hour learning how it works and figuring out the right combination of profile contexts and tasks ... and then it didn't work. I was using button number 26 which was supposed to be the power button but I never figured out why this didn't turn off the screen on the N7000. (Surprisingly tasker does not have a task identified as turning off the display!). Eventually however I stumbled across the fact that the task item called "system lock" turned off the display, and that did the trick for me. It was a minor expense and a lot of work to get my phone to behave the way I believe it should have to begin with ... but I'm happy that I prevailed in the end. Thanks very much for your suggestion.
~Paul
Haven't seen that option in stock-based ROMs but CM ROMs can do this.
I'm currently using CM10.2 and the screen stays off while connecting/disconnecting the charger
good one
jakuburban said:
Haven't seen that option in stock-based ROMs but CM ROMs can do this.
I'm currently using CM10.2 and the screen stays off while connecting/disconnecting the charger
Click to expand...
Click to collapse
Do you know if that is true with CM10.1 based roms as well?
I don't flash often, and I don't want to flash a CM10.2 based rom since it looked to me that this was still too much of a work in progress.
~Paul
pmennen said:
Do you know if that is true with CM10.1 based roms as well?
I don't flash often, and I don't want to flash a CM10.2 based rom since it looked to me that this was still too much of a work in progress.
~Paul
Click to expand...
Click to collapse
I think jellybam had this option and surely some other ROMs have it too, but I can't help You with 10.1 ROMs as I don't use them myself.
However You might wanna give a chance to 10.2. I think it's pretty good for daily usage as I'm using it like 3 weeks now. All the major bugs have been fixed. The only unsupported apps are the navigation ones like tom tom and automapa. However forevermaps still works.
That's what worked for me in Tasker
Profile: State/Power/Power any
Entry --> Power - On
Exit <-- Power - Off
Task: Power - On
Variable/Variable set/%PWR =1
Task: Power - Off
Variable/Variable set/%PWR =0
Profile: State/Display/Display State Off
Entry --> Power - Old
Exit <-- Screen - Off
Task: Power - Old
Variable/Variable set/%PWR_OLD = %PWR
Task: Screen - Off
Display/System Lock
If %PWR_OLD =/= (not =) %PWR
Variable/Variable set/%PWR_OLD = %PWR
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Strange bug indeed and i have no idea why. The vibration on boot is always there to tell that bootloader boots. Its easier to troubleshoot a black phone that way, according to the service manual.
Sent through time and space from my s3mini/CM11
Jucarez said:
Hi there, guys.
I did a wide search in Google/XDA/whatever and didn't manage to find anything related to my problem, so I'm posting it here :good:
My S3 Mini (I8190N) runs flawless and quite smooth on NovaFusion/Maclaw 20140524. Using Gravity Box for enabling navbar (since the I8190N loses its capacitive buttons when changes the kernel) did the trick and fully usable...
Except for one little BIG bug: everytime I receive a notification (Whatsapp, Gmail, FB, SMS, calls, doesn't matter which app) while the screen is off, it reboots. Every. Single. Notification. Cause of this, my battery lasts just a couple of hours, since is rebooting non stop, and I lose a lot of important things (calls, alarms, SMS, you name it)
I tried some things:
- Installing today's NovaFusion release (didn't solved);
- Clean installing 20140524 again (nope) and clean installing today's release (nope again);
- Removing Xposed and Gravity Box (I thought it could be some incompatibility, but nope);
- Disabling lockscreen (to test if the problem was with lockscreen itself, but no).
Following the logic, it appears to be something related to notifications waking up the screen (the phone even vibrates a little before restarting again), but I didn't find any configuration related to this.
So please, anyone? Any advices? Any solutions? This issue is getting me heads off
Click to expand...
Click to collapse
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Meticulus said:
Since there seem to be issues with the capacitive button lights on your device, I would assume that the problem is with BLN (Back light notification) which activate the capacitive button backlights when you receive a notification and the screen is off.
I would suggest that you check to see if BLN is enabled and disable it. There is a BLN Control App in the Play store :good:
Click to expand...
Click to collapse
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
i have the i8190 and have the same problems
So I'm using Carbon and Slimkat, works perfectly fine
Jucarez said:
This makes a HUGE sense! :victory:
(still weird, tho, that only the I8190N loses its capacitive buttons on new kernel, but not entering this discussion haha)
Will try this, @Meticulus. Thanks in advance
Click to expand...
Click to collapse
Did you try it ?
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Hi guys,
I tried it. It's working perfectly. Hallelujah!
Now I'm discovering the Xposed to do a lot of other things (autohide the navbar, disable the "3-dot" button on apps, etc)
Thank you very much!
down
tys0n said:
Download Disable_BLN.zip and flash in recovery. See if it works. My backlight are always off with this flashed.
https://app.box.com/s/ybzhlojc807u8srw8lep
Click to expand...
Click to collapse
LMH1998 said:
Thank you! Now it works perfectly fine Finally found the solution after few months, thank you!
Click to expand...
Click to collapse
Jucarez said:
I tried it. It's working perfectly. Hallelujah!
Click to expand...
Click to collapse
Unfortunately, the workaround "patch" is not available anymore :crying:
would it be possible to upload it again anywhere, maybe here?
or is there another possibility to fix that problem yet?