I wont moderate this thread, but since some where already messing up other topics, I thought it would be smarter to open a thread for this problem.
Here is what it's all about:
The softkeys in V20n stop being light after about 5 seconds. If you use them again, they stay light for about 5 seconds again, and so on.
But since in the dark, they are hard to locate, some ppl here feel disturbed by this problem very much.
This build.prop tweak didn't fix the problem, as I was told.
Code:
# Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
Maybe any dev here has an idea, of how to fix it.
N00BY0815 said:
I wont moderate this thread, but since some where already messing up other topics, I thought it would be smarter to open a thread for this problem.
Here is what it's all about:
The softkeys in V20n stop being light after about 5 seconds. If you use them again, they stay light for about 5 seconds again, and so on.
But since in the dark, they are hard to locate, some ppl here feel disturbed by this problem very much.
This build.prop tweak didn't fix the problem, as I was told.
Code:
# Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
Maybe any dev here has an idea, of how to fix it.
Click to expand...
Click to collapse
ro.mot. stands for Motorola Devices.
But changing to ro.lge. has still no effect
Mick2K said:
ro.mot. stands for Motorola Devices.
But changing to ro.lge. has still no effect
Click to expand...
Click to collapse
Well if so, they have a bug inside of the Tweaks that can be applied to stock rom thread...
But anyway, anyone who got a solution already?
Here is an explanation of the Build.prop tweaks but it's in German.
Not everyone can read (understand) it.
It's just a bug in the Firmware and i don't think we can fix it that way.
As i wrote in another Thread this is a Bug in the V20N firmware and the LG support acknowlegded the Bug in the German LG support forum.
I doesnt mean that the Bug will be fixed soon coming from LG but at least it will be fixed (maybe---sometimes---in the future---on the Enterprise---opps, too far )
Here is the Link to the German forum where you can read that I, pythoner, started the fight, won some people over, and slayed the incompetent LG Support (without taking an Arrow to the Knee). Im sorry to write that they're Incompetent, but read it for yourself, they really are (sry, only in German)
Lg-Supportforum
EDIT: Support Ullrich on the second page makes the most disturbing/Incompetent comment. Something like "Its not a Bug, its a feature, live with it"
Related
hey guys i have upgrade some thing to do sharpness picture on my tilt and now
i just see black screen.
after i take the picture i can see the pic but when i turn on the camera its show blank black screen
i have been searching for alot of msg on the forum and i didnt found any solution
please guys there is a solution?
I don't know about everyone else, but every time I've installed anything and gave undesired results, had bugs, etc. I just uninstall it. Try that. If it fixes the problem, then there ya go.
Radio
Every time this has happened to me or someone I know the radio you are using isn't compatible with the Rom. Flash to a differant radio and see if that fixes you problem
Are you really going to start a new thread " every " time you have a problem ? You have 25 posts and you have already started 7 new threads. I don't think I have started 7 new threads in 1600 posts.
To answer yesterday's new thread , http://forum.xda-developers.com/showthread.php?t=524573 The camera sucks, deal with it. You can do thinks to quicken the shutter delay. Search !
To answer today's new thread, try a different radio, or one of the many camera updates that you would have found in the many...many...many threads already started on this subject, that a simple search would have led you to. Otherwise, the camera sucks , deal with it.
To improve your picture taking, go here
Hey!
If you guys really really want the MOD, let's do something about it. AND I NEED ALL SUPPORT FROM EVERYONE.
Read Carefully.
I'm not sure if you've heard of PSX emulator or not. The author, zodttd, has started the project because he saw
there was a petition ( Here ) to have me bring PSX, N64, and the VLC media player to the Android platform. With over 1800 signatures I started work on PSX a few days ago.
Click to expand...
Click to collapse
So what I am thinking is, we should do the same thing too!
I have begun a petition. Now all I need is you guys to sign it. It's a really simple process.
Once we have enough signatures, we can show it to mods from other communities.
Petition
Thanks,
Clay
have you sent any emails to app developers or anything like that before you post a petition? I think you may be jumping the ball a little bit here... go ask a few developers first.. Im pretty sure someone might have the time (or knowledge to help you learn how to implement your idea...
doesnt seem like it should be that hard to link the led notification and a button backlight... they have done it with trackballs...
As soon as I get my vibrant I shall start work on this.. Someone will probably get it working before me but I shall give it a shot..
Petition is a nice idea, but no need for it. Im pretty sure once the vibrant (galaxy s) gains more popularity, the programs an mods will start to come.
wow making the button backlight as notifications is actually a really good idea.
Lieu10ant said:
wow making the button backlight as notifications is actually a really good idea.
Click to expand...
Click to collapse
Second that! Actually seems like a pretty simple mod as well.
MINUS Stl said:
Second that! Actually seems like a pretty simple mod as well.
Click to expand...
Click to collapse
Thirded. Great idea.
This would be fantastic. Good idea.
can't wait to see progress.. also, is there a charging light? if not can there be a mod to have one of the buttons (i rather see the search icon as a charging LED)
Thinking about getting a Vibrant, and this mod would make the purchase that much easier.
All for it!!!
Make it happen
Im still on the fence if i should buy this phone because im so used to my g1's hardware keyboard and the lack of an led notification is kind of turning me away from this awesome beast. i spent maybe half an hour playing with one today at t-mobile...if this gets done maybe ill get a vibrant and overcome my attachment to hardware keyboards lol.
a cool idea would be to have someone make the backlight for the buttons light up sequentially left to right!
speedysilwady said:
Im still on the fence if i should buy this phone because im so used to my g1's hardware keyboard and the lack of an led notification is kind of turning me away from this awesome beast. i spent maybe half an hour playing with one today at t-mobile...if this gets done maybe ill get a vibrant and overcome my attachment to hardware keyboards lol.
a cool idea would be to have someone make the backlight for the buttons light up sequentially left to right!
Click to expand...
Click to collapse
Even in stock form you will not regret the purchase of this device I love this device
Agreed. This thing is amazing. Came from a G1 and the lack of hw keyboard isn't a big deal for me (and I used the hw kb constantly!). No led notification is odd, but if we can do this button backlight mod....
What about AMOLED?
I don't get it-
Why are we looking for workarounds like lighting the menu buttons when there's a Super AMOLED screen to play with? Since there's no backlight to lose precious mWh's from the battery every time you want to show a light pixel, shouldn't a simple white text/pattern/indicator drawn on the screen with the rest of it black/off work as needed? Make it flash, make it off most of the time like a normal indicator, make sure that notification is bright, perhaps make it customizable, and bingo!
It might even be more efficient than some silly LED somewhere...
gthmcty1 said:
Even in stock form you will not regret the purchase of this device I love this device
Click to expand...
Click to collapse
thanks i think ima go for it!
and whoever mentioned the screen idea, its deff not bad either imo but idk how thatd compare to the backlight idea battery-wise...i mean maybe youre right it might take less battery to flash the screen rather than the menu buttons
iPhace said:
I don't get it-
Why are we looking for workarounds like lighting the menu buttons when there's a Super AMOLED screen to play with? Since there's no backlight to lose precious mWh's from the battery every time you want to show a light pixel, shouldn't a simple white text/pattern/indicator drawn on the screen with the rest of it black/off work as needed? Make it flash, make it off most of the time like a normal indicator, make sure that notification is bright, perhaps make it customizable, and bingo!
It might even be more efficient than some silly LED somewhere...
Click to expand...
Click to collapse
that doesn't sound bad at all, something like the battery icon that the screen shows when the phone is powered off but is charging. have a notification icon show on the screen and have it blink at certain values
yes sir. i'm all for it as well!
That sounds like a great idea. And different buttons could be set for different notifications. Like say the Menu button could light up if you have a new text, the Home button if you have a new E-mail, and so on.
I used to do a lot of Java coding, but am pretty rusty. Tomorrow I'm going to start looking into implementing any of the ideas mentioned here. Already installed the android sdk, just need to learn how to write android applications
I have made a previous thread long time ago.http://forum.xda-developers.com/showthread.php?t=1038598
Finally i have found what makes my screen blank during calls on any gingerbread custom or stock.
Its my faulty proximity sensor.
I used many device tests and they say naturally that my sensor is dead.
Strangely in froyo it works.
I dont care if it is software of hardware,i want you to tell me a way to turn that DAMN thing off as it is driving me crazy.
I have used ALL the apps on market,proximity off,sanity etc,i have bought all but no luck.
Can the app Tasker help me?
PLEASE!!! help me!!! i beg you people.
EDIT
and as i have suspected,if i use my handsfree (they say they turn off the proximity sensor),well everything works super fine....
come on guys...many people have the same issues,you are the gurus.help!
no one???? wtf
karapoutsoglou said:
no one???? wtf
Click to expand...
Click to collapse
I guess you will have to downgrade to FROYO and stay there
Nitro_123 said:
I guess you will have to downgrade to FROYO and stay there
Click to expand...
Click to collapse
that is ridiculous! with hands free the phone works perfectly.
in htc with the same problem they have found a way to disable it through hex editor.
it must not be that hard for a programmer
with root explorer and a hex editor.
wtf??? im in xda
edit
look how many people have this problem
http://code.google.com/p/android/issues/detail?id=15291
there must be a solution for us too.
I have the same problem. All stock and custom roms gives me this error. I was finally able to turn off the proximity sensor with the latest MIUI Rom.
A fix would be great thou.
If it works fine in Froyo I would say it is software. Have you tried CM7? you might be luckier.
It should be easy for a kernel dev (not me sorry) to disable it. It would be a matter of not compiling the sensor's driver in the kernel so it will never get loaded.
Maybe if you ask one of the kernel devs how to compile a working Kernel and disabled the driver they might do it for you.
If you are using a stock firmware then probably cf-root with proximity sensor hack would be the best option.
K.
EDIT: I had a look at the kernel menu and indeed the GP2A sensor is there and seems easy to not include. The bad news is that it looks like the light and proximity are the same hardware (or at least driver) so if you disable one I am sure you will loose the other one.
This is the name as it appears in the kernel menuconfig "GP2A ambient light and proximity input device". Please note that I never compiled an Android kernel (but will soon for fun) and my knowledge is quite limited.
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
jeremy89632 said:
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
Click to expand...
Click to collapse
i sent him a mail. here are the responses:
it seems unlikely:
- I don't have the device
- it uses different touch controller than 10.1
- kernel doesn't support configurable parameters for 8.9
Click to expand...
Click to collapse
I'm speaking about driver provided for controller used in 8.9, it has
no possibility to change configuration. And the firmware of the
controller is a binary blob with no documentation.
Click to expand...
Click to collapse
looks like we are unlucky
being very upset with this problem i started poking around the build.prop
it might be placebo but i feel that when this is added:
Code:
windowsmgr.max_events_per_sec=300
it gets a little more responsive. still not what i want it to be but better than before.
Try Touchscreen booster
It seems to have helped mine.
thanks. seems a little more responsive.
here is the apk if anybody else was wondering:
http://forum.xda-developers.com/showthread.php?t=1261237
My 8.9 LTE is super sensative, probbly the most I have seen on any android tab.
I can just barely graze my screen with rhe back of my fingernail and it even picks that up.
Compared to my roomates ASUS Transformer Prime, wo cant even use his fingernail unless he really jams it down.
iinteresting but im on the tegra version which aparently has completely different hardware
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
MatteAce said:
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
Click to expand...
Click to collapse
Try TouchScreen Booster?
the_hatrix said:
Try TouchScreen Booster?
Click to expand...
Click to collapse
that's been the first thing I did, but the improvements it brings are very light.
Does the tablet really have different hardware between the wifi and the LTE version? (at least regarding the screen digitizer)
Loccy said:
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Click to expand...
Click to collapse
Hmm, is it really a sensitivity issue? If I swipe first then wiggle like you mention, the screen will wiggle slightly. It sounds like there is a threshold to switch from holding the finger down motionless, to scrolling from left to right.
Perhaps a threshold setting (if available) is sufficient to overcome this?
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Kasracer said:
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Click to expand...
Click to collapse
I have Samsung 3.2 OTA update and it really changes nothing.
Btw no answer yet from Samsung, and yes, the problem is just about some sort of accidental touch filter
Hello, and please, if there is another thread about this problem that i didn't fine, excuse me!
my question is simple:
is there any ROM (2.3.x - gingerbread) in that the led of soft keys is working well and it does not shut down after a few seconds? if yes...please tell me wich one.
as i can remember, in Froyo the light from the 4 soft keys stayed on all time the screen was unlocked ... correct?
i would really like that someone give me a sulution. i have seen a MIUI video in wich, unfortunately the lights are killed as well after a few secs....
thanks in advance.
dookoo said:
Hello, and please, if there is another thread about this problem that i didn't fine, excuse me!
my question is simple:
is there any ROM (2.3.x - gingerbread) in that the led of soft keys is working well and it does not shut down after a few seconds? if yes...please tell me wich one.
as i can remember, in Froyo the light from the 4 soft keys stayed on all time the screen was unlocked ... correct?
i would really like that someone give me a sulution. i have seen a MIUI video in wich, unfortunately the lights are killed as well after a few secs....
thanks in advance.
Click to expand...
Click to collapse
I prefer not to, if you want better battery life.
You can ask the developers in this thread about the leds.
Sent from the Sun.
@Zakys
Thats Bogus. These LEDs (more like SMDs) need close to nothing. Maybe your Phone will last 1 minute longer with the lights out.
@dookoo
its a Bug. LG already acknowlegded it in the german support forum. They are working on a fix to get them working again (like under 2.2). Knowing LG that can take quite some time.
pythoner said:
@Zakys
Thats Bogus. These LEDs (more like SMDs) need close to nothing. Maybe your Phone will last 1 minute longer with the lights out.
@dookoo
its a Bug. LG already acknowlegded it in the german support forum. They are working on a fix to get them working again (like under 2.2). Knowing LG that can take quite some time.
Click to expand...
Click to collapse
But the latest LG phones does the same. Perhaps it's not a bug. Anyway, what's bogus??
Sent from the Sun.
there is core modification solving this problem
@juqe
Care to share your knowledge?
@ Zakyz
Then all the other Phones are defect . I contacted the LG support myself and they said it is a Bug to be solved.
Try to google Bogus. Its english.
pythoner said:
@juqe
Care to share your knowledge?
check this out
Click to expand...
Click to collapse