Database Develop

Is there any app\hack that will leave the keyboard backlight on?

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...

[Q] Touch Buttons lightening

Hey all,
hope this is the right Thread for my post.
I've found out that the touch buttons of my device(Galaxy i9000) are lightening as long as the display is on.
On the device of my girlfriend the buttons are lightening only for 3 seconds then they turn off again even the display is still on.
We both have Froyo 2.2.1 XXJQ3 flashed over Odin. Nothing else is modded.
No rooting, no lagfix.
I know thats it's normal that the buttons are only lightening for 3 seconds, but my girlfriend wants me to set her mobile so it's like mine.
And I have the question why my buttons are lightening as long as the display's on and other phones of the users here not?
Hope u pros can help me again.
Greetz and thx

That's really strange...mine only go in in some apps, when I click them, our when I an typing but generally they are off...will look into it. Are you sure you both running exactly the same firmware?
Sent from my GT-I9000 using XDA App

I'm on the same firmware flached wit Kies (official) and mine is fine. If keep touching the screen, the buttons keep lightening but if after two seconds they are off.
flash the official version it's in kies

Hey guys,
Yeah I'm sure that we both have the same firmware, because I flashed them together. First mine then her's.
Today I flashed both to 2.3.3 and again my buttons stay on and her's not.
In my opinion it looks much better when they stay on as long as the display is on especially when it's dark, but im still curious whats the reason for this.
Still hope u can help me.
Thx and greetz

keep the lights on
Hi there,
I had exactly the same problem with my phone - especially annoying if you are
using phone in darkness.. App "keep the lights on" is a smooth solution..
Give it a try, step out of the dark
cheers

saving battry

I know that it saves battery but why the heck it doesn't do that on my phone?
Never changed something and I have to say that I really like that they stay on, but is there a chance that we can set up if lights stay on or not?

Landlord_t said:
Hi there,
I had exactly the same problem with my phone - especially annoying if you are
using phone in darkness.. App "keep the lights on" is a smooth solution..
Give it a try, step out of the dark
cheers
Click to expand...
Click to collapse
For me on XXJPK, while the app works, after I lock and unlock the buttons light up again so you would have to double tap the widget to turn the lights off every time... :-(

@markdj57
On JP3 and JPO works just fine - after turning the widget (and lights) on, I simply
throw the widget in trash and the buttons and display become one

MasterJam882 said:
Hey guys,
Yeah I'm sure that we both have the same firmware, because I flashed them together. First mine then her's.
Today I flashed both to 2.3.3 and again my buttons stay on and her's not.
In my opinion it looks much better when they stay on as long as the display is on especially when it's dark, but im still curious whats the reason for this.
Still hope u can help me.
Thx and greetz
Click to expand...
Click to collapse
XXJVK known issue/feature: Button lights are always on when screen is on.
However, this phenomenon should not occur on older firmwares.

Is there a simple fix yet?

Look at this post, worked for me and others.
http://forum.xda-developers.com/showpost.php?p=12529554&postcount=478
Enviado desde mi GT-I9000 usando Tapatalk

I found that the app "screen filter" makes the soft key lights turn off after a couple of seconds when it's running, other than that I've never experienced it :/
Sent from my GT-I9000 using Tapatalk

[APP] LG Touch LED Notifications

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.

[Q] Faulty mute toggle?

Hi everyone
Re-posting this from the general section (posted on there by mistake, was still half asleep lol, sorry)
Just got the xperia z yesterday (after my previous lg 4x was stolen... grrr... may the thief get permanent bursting hemorroids...) and I noticed a weird thing.
The mute/vibrate/sound toggle in the notification bar does not seem to work, and the same goes for the one in the popup shown by pressing the power button for a couple seconds.
Details: the mute or vibrate icon appears on the notification bar, but if I check the volumes in settings, they're still all on, and if I receive a call or get a notification or whatever, the phone actually rings despite the supposedly muted state.
All this doesn't happen if I "manually" turn the volume off with the volume buttons or via settings: in that case the vibrate icon appears and the phone actually does not ring.
Has anyone experienced anything similar?

All good here dude. Hope you get it fixed. Have you tried turning phone off and on again? That usualy fixes small.glitches.
Sent from my C6603 using xda app-developers app

steve17harris said:
All good here dude. Hope you get it fixed. Have you tried turning phone off and on again? That usualy fixes small.glitches.
Click to expand...
Click to collapse
Yep, already tried that of course, as well as uninstalling the one widget I have that interacts with volumes, just to be sure it was not some weird conflict (and of course it wasn't)
Not a biggie actually, as I can turn it down manually or by said widget, but I hope I'll figure it out anyway if only for the sake of understanding the source of the issue

Yep I understand that. Annoys me when I cant get something working lile its ment to.
Sent from my C6603 using xda app-developers app

I have a problem with the toggle in the notification bar and the power off menu. System settings show me notifications and ringtones are off, but the phone still has audible, unmuted notification sounds. Really annoying.

robogo1982 said:
I have a problem with the toggle in the notification bar and the power off menu. System settings show me notifications and ringtones are off, but the phone still has audible, unmuted notification sounds. Really annoying.
Click to expand...
Click to collapse
Yep, that's the same exact issue I'm having

I guess we have to wait for a software update.

robogo1982 said:
I guess we have to wait for a software update.
Click to expand...
Click to collapse
I guess as much...
Actually, I could try a factory reset just to be sure, but I admit I'm kind of too lazy to set my stuff up again from scratch only to try and fix that small glitch

Vostradamus said:
I guess as much...
Actually, I could try a factory reset just to be sure, but I admit I'm kind of too lazy to set my stuff up again from scratch only to try and fix that small glitch
Click to expand...
Click to collapse
Well, I was thinking the same, but now that we got root... :laugh:

robogo1982 said:
Well, I was thinking the same, but now that we got root... :laugh:
Click to expand...
Click to collapse
Heard about it, but haven't read the whole thing yet (yep, still being lazy)
Jokes apart, I was planning to leave it 100% stock for at least a little while to see how the battery behaves without even the slightest piece of modding (got the phone only last friday, today has been the first real "field test" for the battery and so far I'm pretty positively impressed)

Well I have already removes/frozen a bucketload of apps happy bunny, I am. Now I only need to figure out which app does what so I don't kill something and make my phone less usable.

robogo1982 said:
Well I have already removes/frozen a bucketload of apps happy bunny, I am. Now I only need to figure out which app does what so I don't kill something and make my phone less usable.
Click to expand...
Click to collapse
lol I removed a few apps too, but luckily for me they were uninstallable without root or anything.
I also disabled a few more through the stock apps management, for the time being it's sufficient for my taste

Same irritating automatic toggling action going on
Vostradamus said:
Hi everyone
Re-posting this from the general section (posted on there by mistake, was still half asleep lol, sorry)
Just got the xperia z yesterday (after my previous lg 4x was stolen... grrr... may the thief get permanent bursting hemorroids...) and I noticed a weird thing.
The mute/vibrate/sound toggle in the notification bar does not seem to work, and the same goes for the one in the popup shown by pressing the power button for a couple seconds.
Details: the mute or vibrate icon appears on the notification bar, but if I check the volumes in settings, they're still all on, and if I receive a call or get a notification or whatever, the phone actually rings despite the supposedly muted state.
All this doesn't happen if I "manually" turn the volume off with the volume buttons or via settings: in that case the vibrate icon appears and the phone actually does not ring.
Has anyone experienced anything similar?
Click to expand...
Click to collapse
Yes, having the same problem as well with mine. But it has been the same problem since I had ICS on my Xperia Arc S, then Xperia V and now this when I use the toggle in the notification bar or any other toggle aside from toggling it manually via setting. Very irritating since it has never and probably will never be fixed due to the fact that it's a cross-model issue. Chances are, those who say they don't have this problem already has it but don't know it yet or will get it eventually. Sony needs to iron this out once and for all

Touchscreen Fix, Testers Please

Go to System\usr\idc and open file clear_ped.idc with a text editor
look for the line
#Pressure
touch.pressure.scale=0.2
I changed to 0.1, save and close,
Secondly go to System\usr\idc and open file clearpad.idc
look for the line touch.filter.level = 2
I changed the level = 2 to level = 4
Reboot and enjoy.
My touchscreen now works flawlessly and I hope this fix works for others please test and report back your findings.
Remember to hit thanks if I helped you in any way.
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.

I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk

How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers

Dark-Skript said:
How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers
Click to expand...
Click to collapse
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.

TagEHeuer said:
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.
Click to expand...
Click to collapse
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?

What Rom and Kernel are you on
Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
What Rom and Kernel are you on, I think some 4.3 ROMs still have an issue with the system being read only, I'm by no means a dev and you would need to read about this on whatever ROM you have thread, once you gain access to system being read, write you will have no issue saving.

Try other settings
ArashMiniStar said:
I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.

Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further

TagEHeuer said:
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further
Click to expand...
Click to collapse
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.

Dark-Skript said:
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.
Click to expand...
Click to collapse
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376

TagEHeuer said:
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376
Click to expand...
Click to collapse
Thank you soo much, for all the help. This fixed the issue!!

Dark-Skript said:
Thank you soo much, for all the help. This fixed the issue!!
Click to expand...
Click to collapse
It's a pleasure, always happy to help.

Hello guys! I came here to show you this video:
[Search Youtube for XPERIA Z1 タッチ切れ再現法 The method of reproduce] Sorry, new users can't post links it seems. But please check the video out.
I wanted to ask if any of you could give a reasonable explanation of it. If this is a software issue - how could it be reproduced in such a manner, by touching the metal frame of the phone? The video shows it pretty well. I also managed to reproduce the bug like this on my Z1. It has been in service for about 20 days now. I am worried that they might just 'mask' a hardware issue with software filtering. My initial assumption is that this is due to bad grounding? Why else would human contact trigger it? You can see it can be reproduced on-demand like this.
Thanks for reading! I hope someone can explain it.

Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !

水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Agree.

eclyptos said:
Agree.
Click to expand...
Click to collapse
video demonstrates that a touch is being registered when touching the frame. It's kinda weird since why did the screen reacted to the touched frame. I have done that also and it's the same with me. But even after touching the frame and screen registered the touch, still screen fails to produce a continuous touch.
Sometimes it produces phantom touches which can be the cause of the random zooming and highlighting when browsing
Also tried changing the touch filter and failed to save. I think it needs root access

Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app

RISHI RAJ said:
Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is really a widespread problem across the globe. even Z1s owners are plagued by this problem and most likely even the z1 compact.

@Banwell13 I've not tried this as my touchscreen problem seems to have fixed itself? Strange.
But i'll definitely be keeping this thread in mind if it re-occurs.
Thanks for your efforts m8, appreciate it.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Think what he ment was if you hold the frame then the issue doesn't occur, well that's what happens on mine at least, putting it down on a desk usually makes the bug show it's face. Holding the frame fixes it.

@dladz, @brapicoco, Guys, we said this 20 times, the issue don't show on our devices in the same mode.