Related
Hi Guys,
I did some research here and on google but couldn't find any good results.
I really have a serious lag in my keyboard, more likely at the repeating characters like, hello or whoohoo ... wil be like helo whoho, ...
Is there a fix or something else. When typing emails this result in a lot of frustation. I don't know how you guys think or experience this problem!
Thnx for you comments.
it's been brought up before but might be hard to search on...
Others have reported that turning off Word Completion and Auto Correct have helped.
Settings --> Input ... Word Completion tab
Give that a shot.
I have the same problem. I've turned off input completion under settings -> input -> word completion and in programs -> xT9 Settings. But when I type the letter A, Q, O, and L it tries to auto complete. Also Z is displayed as X. I installed the AT&T Keyboard fix from TaurusBullba and nothing changed. I am using Dutty_s_hybrid_Rom_Build_18533 Final on an AT&T tilt. Thanks for the help.
I've got the same issue. I've turned off Word Completion, etc. but it didn't seem to make a difference. Guess I need to slow my thumbs down...
Yes, the lag is quite annoying at times. It seems to be less of an issue when less programs are running. But I noticed the problem is not as bad since I stopped using Windows Media Player (which I would run all the time) and started using Audio Manager.
L8
With me the lag was even bigger after I had installed the HTC Touch Keyboard cab, which also xt9. After removing it got a little better (but still there's lag)...
So i guess there is no 1 solution for this keyboard lag? I'm also faced with the same problem I can finish typing my sms about 4 to 5 words faster then it can appear on the screen.
Anybody found a solution?
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Even though I think this should help you guys as well, I'm kind of pissed off that one has to use workarounds for such an expensive device to work properly. Especially when it comes to the keyboard which is among the top 5 reasons for buying it in the first place. I'm aware of the argument that this kind of thing happens with all WM devices, but still this seems close to unacceptable for me.
All the best
dsyro said:
Even though I think this should help you guys as well, I'm kind of pissed off that one has to use workarounds for such an expensive device to work properly. Especially when it comes to the keyboard which is among the top 5 reasons for buying it in the first place. I'm aware of the argument that this kind of thing happens with all WM devices, but still this seems close to unacceptable for me.
Click to expand...
Click to collapse
I totally agree, especially for a product that costs €600 or more! Nevertheless it's with all WM and HTC devices, and... has your pc never crashed or do you use a WindowsXP pc which has no tools or addons?
dsyro said:
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Click to expand...
Click to collapse
This appears to have fixed it for me, thank you!
This seems to have fixed it about 90% of the time. Sometimes when typing "www." it will end up ww. but that is only part of the time.
Thanks!
Mine sped up somewhat when I did the repeat rate change, but I REALLY noticed a difference when I removed the 3G dial pad and rebooted, seems everything is running faster now, but knowing my luck its a tease and it'll just go back to normal
dsyro said:
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Click to expand...
Click to collapse
Very odd, but it works for me. Thanks for the tip!
Up/Down control setting change worked for me too. Now the only problem is I actually get 3 letters sometimes!
Axman said:
Up/Down control setting change worked for me too. Now the only problem is I actually get 3 letters sometimes!
Click to expand...
Click to collapse
Maybe decrease the key repeat rate?
SWEET
the up down to a minimum seems t work for me. any suggestions as to which screen keyboard is better to use then the one in the rom my thumbs are to fat and its hard to use the keyboard when im driving. I knwo tis not safe but everyone does it. i guess it would be safer If my kaiser had bigger screen buttons for ppl with chubby fingers. LOL
thanks in advance.
juanitto
Hi Juanito,
Don't think it's your chubby fingers - we all suffer from it. I've heard people talk about the PCMKeyboard. On the last Roms i've tried, it didn't work, not sure why. I am currently running a ROM that has the Diamond keyboard, which I like too. The only thing I have to get used to is that it has two keys on each button (similar to for instance Nokia) but it is QWERTY (see here http://forum.xda-developers.com/showpost.php?p=2199341&postcount=15)...
Regards,
Nika.
I do also have the same problems with the whole touchscrenn input.
after some time working around, somehow all inputs have a delay. so for example when I am trying to close a program, the X (to close Prg) animates to be pushed half a second after I clicked on it...
or when I am trying to switch between tabs, it seems as the cpu is hanging somewhere around 100% and you have to repeat your input more times or try to push harder on the screen etc... until the inputs has been accepted.
is that a known issue? its very annoying...
only thing that helps is to softreset the device... but after some minutes the effect starts again...
to dr-house: your problem might be related to the 'htc task manager', especially versions 2 and higher. Disable it's auto start-up and see if you see any improvements.
how do u disable the taskmanger on startup and do the 3G txt thing??
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
Click to expand...
Click to collapse
Mine locks up when Gyrator2 tries to rotate the screen on incoming calls. Really annoying. I want to be able to rotate my screen in most programs, but it always seems to screw up my incoming calls and creates more lag...I'm gonna try to go back to sensorlock instead of pocketshield...
I will try to post it to the official forum as well.
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
Click to expand...
Click to collapse
I had to same problem. I had Gyrator2 running which rotated the screen and screwed up Pocketshield screen.
I put an Event in Gyrator2 to disable rotation when in PShield screen.
The Event should be the same as Manila's except application/window title is "PShield"
That fix the problem.
i get odd issues as well
I agree, I get odd issues as well. I get the occassional hang, crash, missing bar etc. I uninstall pocketshield and I don't get issues. I'm using NATF 2.3 rom. I paid for it and it worked ok for a while until I noticed these intermittent problems...
wmserver said:
I had to same problem. I had Gyrator2 running which rotated the screen and screwed up Pocketshield screen.
I put an Event in Gyrator2 to disable rotation when in PShield screen.
The Event should be the same as Manila's except application/window title is "PShield"
That fix the problem.
Click to expand...
Click to collapse
I created a rule in Gyrator almost immediately after installing PS - I didn't want it to rotate the PS screen.
I left it up to Gyrator to get the window name and now my rule is set for the window #NETCF_AGL_BASE_.
But my problem is not in rotating, my problem is in unlocking (at least I think so). Anyway, will try to change the window name to PShield and see if it makes any difference.
EDIT
Nope it didn't. The top bar disappeared again during the first seconds of my testing :-(
ferus said:
Hi,
does anybody here use PocketShield?
I experience a strange problem - time to time when I unlock my phone the whole top bar disappears. The Start button, the Close button...everything.
I can't do anything with the phone - the only solution seems to be to navigate to the programs tab (via TF3D), select All programs and run the Lock - this locks the phone again and when I unlock it then suddenly my top bar is back. It seems to be completely random.
I know that there is a forum on the developers site but I was wondering if any of the bright minds here could help me ;-)
I am running the 2.0.6.2 free version.
I will try to post it to the official forum as well.
Cheers.
Click to expand...
Click to collapse
An updated version has now been released (9th Dec) to fix this problem...
rmjjjt said:
An updated version has now been released (9th Dec) to fix this problem...
Click to expand...
Click to collapse
Thank you my friend for letting me know. If this is indeed fixed I don't mind paying the $13. Will check it right now.
New version available today - but it's not working correctly. after I use the slide bars one time to ignore a call, every call after that is missing the slide bar (answer and ignore soft buttons are there though) and when caller hangs up before I take any action PS just sits there, like it's stuck. Sounds like the same problems you describe earlier.
Im using PocketShield, but I was wondering - the phone always locks after I insert the stylus (I have Touch HD), after a while PocketShield kicks in and after that if I want to unlock the device, I first have to unlock the "normal" lock and then the PocketShield. Really annying.
Is there a way to disable the lock after stylus insertion?
chetlet said:
New version available today - but it's not working correctly. after I use the slide bars one time to ignore a call, every call after that is missing the slide bar (answer and ignore soft buttons are there though) and when caller hangs up before I take any action PS just sits there, like it's stuck. Sounds like the same problems you describe earlier.
Click to expand...
Click to collapse
actually i just experience this an hour ago.. also every time I slide the keyboard to unlock my Fuze the screen freezes on the landscape mode. all keys on the keyboard besides the windows key. I hope they fix these bugs right away..
I have the same problem with the top bar disappearing. I'm not running Gyrator or anything like that. I'll try a new version when the bugs mentioned have been ironed out. It is a great product though. I do like it.
Are any of these being posted in the PocketSheild forum? They need to know the bugs.
cheez said:
Are any of these being posted in the PocketSheild forum? They need to know the bugs.
Click to expand...
Click to collapse
yes many people posted on the pocketshield forums with same issues...
i dont know if anyone else is having this issue... but
i seems that when slide to answer is activated PSPP some calls get answered automatically... and it takes me to the "talking" screen immediately.
any help on this issue would be super!
I'm having other issues with PocketShield. I didn't have this same problem with version 2.0.6.3, but with version 2.1 I started to have problems with my alarm notification. When the alarm goes off, it just quickly vibrates once and just stops if it's in a locked state. Also, I noticed a heavy battery drain issue--the battery charge would drop about 10% each hour. Once I uninstalled it, the problems with the alarm and battery drain stopped.
Even with the new version (2.1.0.1) I still have problems answering phone calls. I'll slide to answer and the phone just keeps ringing. I hit the "Send" key and nothing happens. I hit the "Answer" soft key and still nothing....
Anyone else still see these problems?
I have a different issue, when phone is not locked and I have an incoming phone call, pocket shield kicks in and shows me "lock screen" where I have to slide to unlock the device and only then I get the standard "Incoming call" screen...
v2.1.0.1
Major Problems
Well I was gonna pay for it but their payment server seems to be phishing site. Also it crashed SQB and when I uninstalled it, the program removed my outlook email account. Sorry but looks like malicious program so going back to an old sensor lock. I did like the software interface but Paypal confirmed me, so I shouldn't need to give you my personal information to pay for the software. No shipping means I am not giving you my phone number and address, etc. Sorry too many questionable things going on for a screen lock... rule is KISS and since this programmer isn't doing that then dump it off my device is my rule.
Neo_ said:
I have a different issue, when phone is not locked and I have an incoming phone call, pocket shield kicks in and shows me "lock screen" where I have to slide to unlock the device and only then I get the standard "Incoming call" screen...
v2.1.0.1
Click to expand...
Click to collapse
version 2.1.0.4 is out and is supposed to fix that problem..
I ran the site and its fine why do you say its a phishing site?
My screen rotation has stopped. It remains on portrait.
I'm guessing I need to exchange the phone.
Any other thoughts or suggestions?
Oh, I'm on the Froyo Beta 2.8.1 of Design Gears'. Been on it for a few days, so I doubt that has anything to do with it.
i hope you have tried pulling down the notifications, and enable auto rotation, or checked it out in the settings....! ! !
neo_31591 said:
i hope you have tried pulling down the notifications, and enable auto rotation, or checked it out in the settings....! ! !
Click to expand...
Click to collapse
Thanks for the suggestiong, but yes, of course Including power off, pull battery reboot; look in several other programs that may fiddle wiht it.
Later, I did one-click back to orig ROM, and it still did it. Went to a 4 hour meeting and after that it works
What I'm afraid will happen now is it will work until my 30 days are up and quit again.
youre lucky that you were able to flash back! my phone did the same thing only when it was stuck in portrait mode I lost all ability to interface via usb... so I was stuck until android magicaly fixed itself today. My phone was stuck like that for 4 days.
Well, I'm back to no rotation, and Screeble is showing as Phone Idle.
I am beginning to think that the sensors on the phone are going out.
ewingr said:
Well, I'm back to no rotation, and Screeble is showing as Phone Idle.
I am beginning to think that the sensors on the phone are going out.
Click to expand...
Click to collapse
I went through the same thing with Assonance. Fixed by installing launcher pro, then recalibrate in display settings, then uninstall launcher pro. I used launcher pro because it has its own screen rotate setting that reset the phones. Give it a try.
Pretty much immediately after posting, I decided to reload my ROM. That fixed it. This happened immediately after doing some software upgrades from the market. Apparently software can screw it up. Or a botched upgrade.
Well, my rotation is broken once again. This is becoming a bit frustrating.
There were 6 apps that updated last night. I'm not sure why/how an app could break rotation. I can toggle it on and off, but the sensor is not working.
I guess I will once again restore to stock, rflash, etc, and see if it comes back. If its the hardware, I wish it would just quite once and for all, and I'd hvae the phone replaced.
This is gonna help so much but that sux
Sent from my GT-I9000 using XDA App
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.
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