yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] iCalculate:
Perfect, works perfectly. Many thanks :good:
[Nexus 4 Android Development] meangreenie:
Very awesome; the reports of a lackluster touch response was worrying

I finally got mine ordered today and this will probably be the first thing that goes on it, after root and busybox.
[Nexus 4 Android Development] rmkilc:
You should incorporate addon.d support. ;)
[Nexus 4 Android Development] AlwaysDroid:
Settings > developer options > pointer location
[Nexus 4 Android Development] Net.silb:
Touch sensitivity improved drastically, pinch zoom not so much.
[Nexus 4 Android Development] whittikins:
The "pinch to zoom" delay/bug/issue/whatever is NOT specific to the Nexus 4. It is the app! My Galaxy Nexus behaves the SAME way (not zooming immediately) in certain apps (Browser, Chrome, Gmail, Gallery, Google+, Reddit Sync, and probably many others). However, the following apps zoom correctly (immediately upon pinching) on both devices: Quickpic, Facebook, Firefox, Tapatalk, Tweet Lanes, and many others.

Google apps and some others must be using Google code for zooming, and I hope it gets fixed!
[Nexus 4 Android Development] whittikins:
The revert isn't working for me. It's still changing the driver at every boot. I definitely want to keep using this, but I decided to try the revert just in case. It even continues after flashing another kernel. Any ideas?
[Nexus 4 Android Development] noobdeagle:
Yep, Revert does not work and still hangs at boot please fix cause this is not ideal.

looking in the package all it does is install recovery ?, hmmm
[Nexus 4 Android Development] Net.silb:
I'm running CM, I wanted to see if revert works and it didn't. I wiped /system and reflashed CM + Gapps and that did the trick. Now I'm back on the on the touch responsiveness fix driver.
[Nexus 4 Android Development] housry23:
Does anyone know if the touch sensitivity problems have been reported to Google and/or LG? hopefully they'll release a fix soon. I don't notice it in every day use, but when playing Temple Run I notice it a lot. I want to try this driver, but with people saying the revert zip isn't working, makes me a little hesitant.
[Nexus 4 Android Development] DerKiLLa:
The patch doesnt work for me ...

I'm using CWM 6.0.2.0 and Superroot.

If i flash the DD.zip, there is no lag at start and no Driver.log.
[Nexus 4 Android Development] Deciare:
If the revert zip isn't working, you ought to be able to revert the change manually by mounting /system as read-write (using ES File Explorer or your file manager of choice) and deleting:

/system/etc/init.d/09driver

/system/SynaImage.E015.bin

---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------

Are you instructing CWM to disable the recovery flasher when rebooting after flashing DD.zip? If you're using the stock ROM, the recovery flasher must be enabled (i.e. you will lose CWM) in order for the startup script to run.
[Nexus 4 Android Development] DerKiLLa:
So i have to use either Stock ROM + Stock Recovery or a Custom ROM and CWM?
[Nexus 4 Android Development] robollama:
Have we gotten any official response from Google yet? Are they even aware of the issue?
[Nexus 4 Android Development] XupModz:
This is NOT an issue it is a downside to the way the digitizer is integrated Into the LCD panel in combination with the driver they may be able to send out a patch that would help the driver but there's not much they can do
[Nexus 4 Android Development] irishrally:
DD.zip borked touch for me in CWM. I prefer the kernel version so I don't have to wait 15-20 seconds every boot on the Google flash screen waiting for the magic to happen.
[Nexus 4 Android Development] noobdeagle:
i did that and it still hung at start up in the end i just reflashed the stock google images.
[Nexus 4 Android Development] osi13:
This fix does work, to an extent. I've been using this driver since it was posted on Google Code. Everything was going fine until today. The issues I'm experiencing are a lot worse than the updated driver. I'm experiencing ghosting, and occasionally my screen will stop functioning for up to 10 seconds. This is absolutely not a fix. It really makes me mad that both drivers are garbage
[Nexus 4 Android Development] DarkRyoushii:
Getting the same issue as you.. I've also run the revert but the same things are happening, the touch is unresponsive at the start and for about a minute in TWRP. Really hope OP can release an ACTUAL revert soon enough :S
[Nexus 4 Android Development] dannejanne:
Could this be made to work on a Galaxy Nexus too? Since the sensitivity issue is present on them too occasionally for a lot of people. Only way to fix it is to turn screen off & on when it happens.
[Nexus 4 Android Development] neer2005:
No the galaxy nexus has different drivers which are phone specific
[Nexus 4 Android Development] bossman137:
marked difference, thanks for the script. I hope i dont run into those issues. Love it so far (been 2 minutes lol)
[Nexus 4 Android Development] brom25:
haven't really noticed any differences, but if you people say it works then it should be better :p it's as perfect as the original nexus 4
[Nexus 4 Android Development] akbisw:
ONLY difference is that it recognizes "light touches" better. Other than that the screen response time is EXACTLY the same, which was Great to begin with on stock. So in the end Im not complaining! I guess this is better if you use a capacitive pen
[Nexus 4 Android Development] Richieboy67:
I'm so not seeing any problems.. Kind of funny though that someone posts they are not seeing an issue with every day use but when playing TEMPLE Run they notice.. And Google should be worried about it why?

I have posted this before. You have a zero gap display meaning the display you see is in front of the touch pad or touch screen, whatever you want to call it. This makes the display look much closer and better but makes the screen a bit less sensitive to light touches.

This is not a defect at all and most people should not even notice this as an issue.

The pinch zooming is not hardware either and works well in Firefox and other apps.
[Nexus 4 Android Development] MrPhilo:
After flashing this my phone is just stuck on a black screen, think I bricked it... trying to find a way to fix it, any ideas?
[Nexus 4 Android Development] irishrally:
Did you flash the zip or the kernel? Hard to tell when you posted the same thing in both threads.
[Nexus 4 Android Development] MrPhilo:
I accidently posted that in that thread, I meant this thread, my bad.

I tried holding volume down and power button, no go.
[Nexus 4 Android Development] trter10:
Hold both volume buttons and power for 15+ seconds and it should hard reboot
[Nexus 4 Android Development] jameslfc5:
Definitely worked! Thank you so much!
[Nexus 4 Android Development] reddv1:
You can't hold both volume buttons simultaneously, it's a rocker. Trying that could damage your volume buttons.

To hard reboot just hold the power button until it reboots or until the led flashes red..
[Nexus 4 Android Development] trter10:
I hold mine at the same time all the time....
[Nexus 4 Android Development] reddv1:
That's weird, on my galaxy nexus I could but on the N4 I can't. Holding one volume button then trying to press the other one causes the first one to lift.
[Nexus 4 Android Development] robto:
Perfectly clarified ...or not ;)

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Android Development] MrPhilo:
It's okay I just got it exchanged haha, just that I lost my perfect no bubble screen protector I put on :(
[Nexus 4 Android Development] apat183:
Works good but anyone found a solution to the 30-45 sec unresponsiveness after a reset? Happens in recovery and after reboot. Not a deal breaker but would be great to know if there was a work around?

Cheers
[Nexus 4 Android Development] trter10:
I think the reason for the touch lag on boot is because it takes awhile to install the file for some reason and the way it does it the boot process is not halted while the script is running. If anyone has a way around this please let me know!

Thanks :)
[Nexus 4 Android Development] noneabove:
I ran the revert but still get a ton of delay before our accepts input, what gives, how do I fix it? :(
[Nexus 4 Android Development] meangreenie:
^^try just manually deleteing the init.d script

and/or restore your boot.img
[Nexus 4 Android Development] irishrally:
Apat183: If you don't mind flashing a kernel to downgrade the touch driver then use this method because there is no lag on boot.

http://xdaforums.com/showthread.php?t=2027476
[Nexus 4 Android Development] apat183:
Thanks Irishrally, I already flash franco.Kernel. Flashing the custom kernel linked above would overwrite franco.kernel correct?

Maybe i can ask franco to implement the above script in the kernel? or is there a way I can merge manually into franco.kernel after i download it? I have limited technical skills so could be a problem lol

Edit: ok looks like franco is not keen to implement old drivers in kernal, just found this
[Nexus 4 Android Development] pmcqueen:
as stated, the only real issue here is the lack of touch for the first minute or so after boot. not really a big deal, and the responsiveness is indeed way better with this older driver (the combo of a matte/anti-glare screen protector and this driver allows me to have full touch functionality even with a pair of double-layered gloves on - pretty sweet) but if someone could whip up a fix for the delay upon boot, it would be awesome.

I suppose I could just flash the driver manually each boot? it would probably be quicker than waiting for the script to run.. or would that not work?
[Nexus 4 Android Development] dwang:
whast the point? You'll still get a delay because when the phone is flashing the touchscreen fw, the touchscreen becomes unresponsive.

The only way to fix the delay is to not downgrade the ts fw, which means modifying the kernel to not check for the ts fw version.
[Nexus 4 Android Development] kashsih93:
im facing the same issue! any fix yet?
[Nexus 4 Android Development] kashsih93:
revert?

i would like to revert back to the original touch driver. is it working and is it safe t do so? im using parandroid 2.99 beta 8.
[Nexus 4 Android Development] hicks12:
I really dont understand why they have changed this, there must have been something wrong with this driver originally? I have noticed the difference now I was expecting the same as my optimus 2x however its drastically different, the sensitivity requires a proper tap to register so I sometimes miss things like pressing the onscreen display (seems to require the most pressure), however sliding/swiping the menus are fine.

Im hoping someone encorporates this or simply changes the sensitivity of the current driver soon!
[Nexus 4 Android Development] meangreenie:
k, i know how to get rid of this without reinstalling rom.

delete 09driver from /etc/init.d

delete SynaImage.E015.bin from /system

boot recovery, wait if you get the long pause and then install motleys reset stock boot.img or via fastboot the boot.img that goes with your rom

wipe cache and davlik via recovery menu

power off via recovery menu

start phone and let it boot, i will take longer to rebuild davlik

after reboot go back to recovery/fastboot and install what kernel/boot.img you want

edit, the newer driver sux lol, off to reinstall the older driver from the op again
[Nexus 4 Android Development] leventccc:
Thanks for the mod, works great on my 1 day old nexus 4 :)
[Nexus 4 Android Development] pac213:
Does this work with CM 10.1?
[Nexus 4 Android Development] yokken:
Well this worked for me, except my touchscreen was unresponsive for over a minute. Looks to be that way upon every reboot too. I guess I can deal with that. It's way more sensitive now, like my SGS3. So nice. Except my phone seems to be getting quite a bit warmer.
[Nexus 4 Android Development] sarni84:
Lolz...it won't make your phone warmer. The reason why takes about a minute at boot and recov is because it is rewriting the touch driver.
[Nexus 4 Android Development] yokken:
Yeah, I figured the warm temps were because of a kernel issue. I tried to revert but no dice. Flashed new AOKP and Motley kernel, hoping it's back to the (worse but more functional) newer driver.
[Nexus 4 Android Development] ElectricAndi:
One question: does this downgrade method mean, that the flash of the touchscreen will physically flashed to get the e015 firmware?

Or will it just be written to a folder on the eMMC where the kernel expects to be the firmware?

The question behind is: Can there be any negative effects in sort of "wear" of the touchscreen flash if we flash it e.g. two times a day? As far as I understand the other method (modded kernel) only needs to flash one time as the automatic upgrade to e027 is disabled, correct?
[Nexus 4 Android Development] paratox:
use Matr1x kernel, it won`t reflash new firmware. but you have to flash the E015 firmware one time this way:
[Nexus 4 Android Development] Bakedbread:
Hey there,

I tried your method and it worked, but is there any other more permanent way of downgrading to E015? Only reason I ask is cause I like to use different kernels like Franco, so the touch fw always reverts back to e027 after reboot. The init.d script isn't the greatest because of the major stall after reboots.

Any help would be appreciated! The E027 driver is just awful. I don't know what lg was thinking
[Nexus 4 Android Development] ElectricAndi:
Thank you paratox, but I installed the modded stock kernel from the other touch sensitivity thread. I only asked because I am interested if the method described here results in a lot flash writes.

As a cwm user I don't care about touch in recovery, so the kernel method has no disadvantages. ;)
[Nexus 4 Android Development] oddfuturejoey:
Folks I need help: I flashed this over Bricked kernel (the latest one) and my phone is COMPLETELY unresponsive to any touch. It has been 5 minutes since my last reboot and the only thing that works is my power button, but since I can't select "Reboot Recovery" I can't even get into TWRP to try and nandroid back to my previous state.

Please help?
[Nexus 4 Android Development] benjamin.j.goodwin:
Hold power button down until the phone shuts down, then once the phones off hold power button with volume down button . That will get you to boot loader. Use the volume key and go up twice, should say recovery. Use power to select and welcome to recovery.

Sent from boozing beery N4...
[Nexus 4 Android Development] oddfuturejoey:
Thanks, Benjamin, that's what I did and I reflashed the zip, cleared cache, cleared dalvik, and rebooted and everything APPEARS to be right again :D :D

Jus haven't reboted to try again, cause I'm scared lol

But thanks!!
[Nexus 4 Android Development] rickytenzer:
I can't seem to get this to work. I am rooted and Busybox is installed, but for some reason the install hangs on setting up the init.d. It eventually completes, but I don't get any unresponsive screen on boot and I checked my touch values and nothing close to .2

Can anyone help?

EDIT: Never mind. Busybox wasn't installed correctly. Fixed!
[Nexus 4 Android Development] nokkenas:
Thanks for this! Like any others who have installed this mod, my screen becomes unresponsive for 1 minute. Also, Power Toggle keeps crashing on boot.
[Nexus 4 Android Development] masterg0g0:
I had a lot of instability with this, screen was not responding even in recovery. Scared me, plugin into the PC USB kind of recovered it. Then reverted it. Please consider this is a feedback
[Nexus 4 Android Development] nokkenas:
I'm going back to revert this mod. Too bad, this mod is great but it will be greater if the initializing phase is faster. Personally I'd prefer it stays longer on boot animation but the touch screen works as soon as the phone is booted to OS rather than booting faster but there's more wait until the screen is available.
[Nexus 4 Android Development] meangreenie:
It's a shame that only the mart1x kernel gives you a choice on which touch driver to use (meaning touch driver only needs to be installed once and not at every boot)
[Nexus 4 Android Development] mohitrocks:
While this seemed to work very well, it would render the screen unusable for a couple of seconds upon boot. (I believe the ROM I was using was Xylon) Nevertheless, thank you very much for this mod.
[Nexus 4 Android Development] nokkenas:
OP, please add this to first post. The revert zip forgets to delete the 09driver file. Also don't forget to clear cache and dalvik to remove the mod completely. Even after deleting all of the files doesn't stop my phone from being unresponsive during boot.
[Nexus 4 Android Development] masterg0g0:
Yes I too have noticed this. Will clear the cache
[Nexus 4 Android Development] Onismurai:
Do I have to re-flash the mod after update my ROM or kernel? I am using Franco and update almost weekly. Also CodefireX is not usually get update fast but I am still worry about this
[Nexus 4 Android Development] Scoutamis:
I have tried the revert zip, and clearing cache/dalvik but i still cant use my touch screen for the first 5 minutes after my phone boots.
[Nexus 4 Android Development] bjg020683:
Revert zip does not work.
[Nexus 4 Android Development] Scoutamis:
So how do we undo it?
[Nexus 4 Android Development] rickytenzer:
That's not true. Worked for me. Touchscreen works right on boot.
[Nexus 4 Android Development] bjg020683:
Look at post #93. Delete files using root explorer or es file explorer, after that go to your recovery and clear cache and dalvik cache.
[Nexus 4 Android Development] marquel1:
not bashing this mod but using this mod not only did my touch response go out on the ROM when I kicked it into recovery mode my touch response still did not work for me it didn't respond... The sensitivity did increase but at a high cost and I don't think it's worth ruining a 300 dollar phone for the touch to be increased... Great mod but comes with high risk
[Nexus 4 Android Development] masterg0g0:
This happened to me too, somehow the drivers were stuck even after going to recovery. Some more tweaking required. How was decided that e15 driver was best for our nexus 4
[Nexus 4 Android Development] no6969el:
After flashing the DD.zip I cleared the cache and dalvik. It booted and I was able to use the touch screen instantly. So I rebooted to test again and it still worked as soon as it booted. So I recommend that.
[Nexus 4 Android Development] masterg0g0:
Try nook screen re calibrator from Google market. My touch screen is better
[Nexus 4 Android Development] kingwaffle:
Yeah, that doesn't do anything.

I have a feeling this could be a manufacturing defect. I had to RMA my Nexus and I could have SWORE it was better than the replacement I received.

Could be in my head, though. I am hoping it [/I]is[/I] a driver issue.
[Nexus 4 Android Development] kingwaffle:
Does anyone have a respectable PRS? Mine is in the 0.55-60 range.

Should I RMA it? This is already my second device (first one had a hairline crack in the back)
[Nexus 4 Android Development] masterg0g0:
Don't be paranoid, take a step back relax and think is it really needed. Is the phone really unusable? Sorry I know it does not help
[Nexus 4 Android Development] kingwaffle:
Unusable? No, but it is sometimes cumbersome to type on SwiftKey and feel the keyboard lagging behind my fingers. I also invoke Google Now accidently from time to time.
[Nexus 4 Android Development] no6969el:
Anybody else noticed that when you plug it in the screen brightness can no longer be adjusted. Until reboot. ALSO lost recovery.

EDIT: So the brightness issue is caused by having animations off in DEV settings... the recovery issue never existed. I just had to reboot.
[Nexus 4 Android Development] thanostsimo:
everything is so far super good ! I am seeing the difference a lot :)
[Nexus 4 Android Development] ElectricAndi:
People like you never learned to ask yourself "Did I something wrong?" - you always shout around that others are doin' wrong. Bravo!
[Nexus 4 Android Development] no6969el:
Hey bro while it was my stupid mistake about the recovery there was nothing I could have done wrong as installation is pretty damn straight forward. I had a legitimate question if anyone else had the brightness issue.
[Nexus 4 Android Development] Perilla_:
After a reboot, to recovery or system, it stay at least 30sec unresponsible.
[Nexus 4 Android Development] trter10:
That is untrue. This mod does not cause that. You didnt install recovery correctly
[Nexus 4 Android Development] Hallucinogen775:
everybody using this mod should really educate themselves before using it.

what you are describing is perfectly normal. whenever a non-modified kernel is started/loaded, it overrides the downgraded touch firmware e015 back to e027 again. the flash process takes about 10-20 seconds during which the touchscreen is non-responsive, this is normal!

matrix kernel does not show this behavior (it doesn't check touchFW upon startup hence not upgrades it back again after a reboot), that is why i am running it. it still reverts when i enter recovery, which i do on a regular basis.

therefore i created (= cut + pasted) two scripts which i run via widget(s) on my homescreen:

1) checkTouchFirmware

2) installE015Firmware

This way checking the current version as well downgrading it to e015 again only takes a single touch (and a few seconds waiting).

i am not using this mod anymore but do the flashing manually. also uninstalling this mod was not a problem at all. as i said before, some education would be good before flashing stuff.

i simply looked at the updater-script and followed through and just looked what it did and removed the involved and all related files.

best regards,

hallu
[Nexus 4 Android Development] Perilla_:
I just said what happen. I have upgraded fhe firm manually and it worked almost instantly, but with the mod it take loonger.

What widget you use to run a command?

Thanks ;)
[Nexus 4 Android Development] Hallucinogen775:
i use smanager and its widget. it takes 5-10 minutes to get used to smanager, but it's well worth it... very handy and useful app.

basically you import the script to smanager, set properties (as root, on boot, etc.). then you can select it as for the widget. the widget lets you choose from your pre-configured scripts.

best ergards,

hallu
[Nexus 4 Android Development] Perilla_:
Thank you very much, I will see what I can do.

Enviado desde mi Nexus 4 usando Tapatalk 2

Edit. Any way to not show the console each time you run a command from widget? I enabled notifications and dont need to see the shell.

Thanks again!

Edit 2. I see its a feature of no ads version.
[Nexus 4 Android Development] NMarco:
this mod works with CM 10.1?
[Nexus 4 Android Development] tanoxxx:
Hi trter10

Thanks for thsi mod, i love it :)

i see in OP "Last edited by trter10; 25th January 2013 at 08:46 PM" there is some change?

i use the old version of the mod..

Thanks
[Nexus 4 Android Development] ugotproblemz:
Flashed this MOD with PA Feb 3 Build and Franco kernel...lag was unbearable...about 1 minute of unresponsiveness. But afterwards it works like MAGIC.

would love to use to, but super unresponsive for me and gets pretty hot.

Tried the revert.zip file but didnt work. so i simply reflashed the kernel again

Also for some reason after flashing this and rebooting from CWM it tells me that the rom might flash stock recovery or something....my options were to say No or say yes and disable recovery? (something along those line) even if i choose go back it just simply reboots. Please look into this OP
[Nexus 4 Android Development] Remcotjuuh:
I flashed this .zip and as said above the lag took way too long; about 2 minute here. So I used the undo script and flashed the franco kernel again but still my touch screen doesn't work :(. Any tips please?

Edit: After typing this the touch screen came back to life after some time, but I guess the mod is still active. What can I do to be sure it's deleted, since the undo does not seem to work.
[Nexus 4 Android Development] meangreenie:
Delete init.d entry and the.bin file, reboot to recovery... note it will probably get stuck for a minute there, just wait it out..... then delete dalvik and cache.. Reboot, should be gone.