Fist off, huge thanks to these people:
-Ryuinferno - His init.d on any device method
-Matt on code.google.com - Old touch driver and temp install method
Disclaimer:
-I am not responsible for any damage this may cause.... (You've seen this a billion times so I'll leave it at that)
NOTE: This mod causes touch to be unresponsive for about 30 seconds on boot up!
What this does:
-Enables init.d by adding a command into install-recovery.sh to run anything in /system/etc/init.d (method by Ryuinferno)
-Extracts the E015 driver to /system for safe keeping and script usage (E015 is a downgrade of the touch driver that senses touch better)
-Adds an init.d script that changes the touchscreen driver to E015 on every boot (driver supplied by Matt and so was the temp-replace method. It runs his method on every boot essentially.)
-Sends log to /data/Driver.log so user can check proper installation if desired
The advantage of using this over using a kernel with E015 in it is that it does not mess with custom recovery touch sensing.
Instructions:
-THIS WILL NOT WORK UNLESS BUSYBOX IS INSTALLED! You can install it with this app.
-Download the zip from here
-Flash it in a custom recovery. If you don't know how to flash a recovery / root / flash a zip, there are plenty of tutorials floating around.
If you want to undo this:
-Flash this zip through recovery.
Enjoy!
thanks.. works well but the disadvantage of this is that everytime you reboot your phone is not responsive for 5 - 10 seconds.
Touch is far more sensitive. I can no longer rest my finger on the home button without it triggering although PSR values are still the same with lowest I got being 0.36
also can you please provide a revert .zip to remove all changes? I don't want to have to reflash my ROM if I no longer want the mod. Thanks.
DarkRyoushii said:
thanks.. works well but the disadvantage of this is that everytime you reboot your phone is not responsive for 5 - 10 seconds.
Touch is far more sensitive. I can no longer rest my finger on the home button without it triggering although PSR values are still the same with lowest I got being 0.36
also can you please provide a revert .zip to remove all changes? I don't want to have to reflash my ROM if I no longer want the mod. Thanks.
Click to expand...
Click to collapse
My touch is responsive instantly... Weird
Yep I can get a revert out soon
Sent from my Nexus 4 using Tapatalk 2
Thanks for this. I'll wait for a revert as this hasn't been much of a concern for me since I got used to it, but it's great to see this development today. I'm sure a number of folks are thrilled.
Just to confirm, this would qualify as an add-on to any kernel, correct? I noticed you mentioned the advantage of this over kernels with the new sensitivity but reading on your description it appears this will not replace your kernel?
lnfound said:
Thanks for this. I'll wait for a revert as this hasn't been much of a concern for me since I got used to it, but it's great to see this development today. I'm sure a number of folks are thrilled.
Just to confirm, this would qualify as an add-on to any kernel, correct? I noticed you mentioned the advantage of this over kernels with the new sensitivity but reading on your description it appears this will not replace your kernel?
Click to expand...
Click to collapse
It's not a kernel, it's essentially a script that runs on boot.
Revert going up in the next hour
Not only does e015 fix the touchscreen responsiveness, it also fixes the issue where if the phone is connected to an a/c powered usb port, the touchscreen responsiveness is even more degraded.
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
DarkRyoushii said:
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
Click to expand...
Click to collapse
Reverter http://goo.im/devs/trter10/RevertE015.zip
DarkRyoushii said:
yea but I've noticed a few bugs with it already (touch being registered as pressed for about 4 seconds longer than my finger) as well as it is making my swiftkey lag behind so I'll probably revert until an official fix is in the works/made.
Click to expand...
Click to collapse
Not seeing these issues myself. The stock keyboard is super smooth. I don't use swift key however.
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
KidCarter93 said:
I've just added this to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 4 using Tapatalk 2
Tested out and as someone who hasn't had much of an issue with the reduced sensitivity, this is awesome. No issues with SwiftKey or anything either.
I am however unresponsive for about 10s after boot, not a big deal though.
Sent from my Nexus 4 using Tapatalk 2
lnfound said:
Tested out and as someone who hasn't had much of an issue with the reduced sensitivity, this is awesome. No issues with SwiftKey or anything either.
I am however unresponsive for about 10s after boot, not a big deal though.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This made mine unresponsive for around 30 seconds, it's random also, and makes the touchscreen unresponsive in recovery for around a minute.
Doesn't really seem to make any difference to the sensitivity on my phone either so I guess different phones have different sensitivity? Or I don;t notice the difference.
Using the revert zip didnt do anything so I had to revert to a nandroid backup.
Definitely feels like its improved! Hopefully its not just placebo
Sent from my Nexus 4
Checked the PRS readings and got 0.3-0.5 instead of the usual 0.5-0.6. I'm also using a screen protector that's real thick. All is well!
biffsmash said:
This made mine unresponsive for around 30 seconds, it's random also, and makes the touchscreen unresponsive in recovery for around a minute.
Doesn't really seem to make any difference to the sensitivity on my phone either so I guess different phones have different sensitivity? Or I don;t notice the difference.
Using the revert zip didnt do anything so I had to revert to a nandroid backup.
Click to expand...
Click to collapse
Same here
qwahchees said:
Checked the PRS readings and got 0.3-0.5 instead of the usual 0.5-0.6. I'm also using a screen protector that's real thick. All is well!
Click to expand...
Click to collapse
I checked mine as well, still mostly in 5s but a few in the 3s. Even the 5 presses would've never registered in the past, huge difference.
Sent from my Nexus 4 using Tapatalk 2
This is awesome! It's absolutely more sensitive than stock. Taps are still in the .50's a lot, but I can get them in the .20's. However, ignoring the numbers, the absolute lightest taps are now registering so I'm thrilled with this
Thanks OP!
EDIT: Also, it's so sensitive that I can use my fingernail to tap and swipe (I'm a guy with short nails, so this wouldn't work for someone with longer nails). Even still, such a big difference because this wasn't possible with the original driver.
A few questions...
1) Does the "undo" zip work?
2) Okay to use with any ROM, correct (running stock 4.2.1 odexed)
3) OP: Any idea on the temporary freeze at each initial boot?
If im not reading this wrong, the "fix" uses an OLDER driver ? (i find it funny each time something is fixed by going back in time)
Related
We finally got our hands on a Inc device (a big thank you to Ruggar for loaning us the device to dev on) and lo and behold, we are unable to touch the green droid in setup wizard (this is a recently reported issue among quite a few users).
We were unable to replicate this issue before, but have finally found the problem with our loaned test device.
The kernel we use puts us in a bootloop right after installing the Rom. This issue is still being tested and a solution will be in the works.
Using other kernels (like King's) let us boot up the device, but sadly we were unable to get feedback when touching the screen. Turns out the loaned device is an SLCD screen, not AMOLED. These kernels do not contain SLCD drivers, thus you cannot touch the screen.
So, if you have an Inc with an SLCD screen, you cannot currently run ShadowRom. All Inc's with the AMOLED screen can run it perfectly fine.
Rest assured this is a major issue, and we are working on a fix asap. We'll keep you posted.
I had no idea the dincs were so different just because of the screen
thy require a whole new set of touchscreen drivers. we ran into this issue on the eris with the MELFAS and SYN touchpanel. its a huge pain in the ass
I'm using an incredible and i was having the same problem until I installed it without a theme in rom manager
Sent from my ADR6300 using XDA App
That explains all my issues...thanks shadow rom!
Sent from my Incredible using XDA App
haha people can actually use shadowrom to test if they got a slcd or amoled.
Ianxcom said:
I had no idea the dincs were so different just because of the screen
Click to expand...
Click to collapse
The software and hardware need to communicate properly so a different screen without drivers is useless.
i used shadow rom v1 wout problems, when trying v2 is when the touchscreen issues occured.
I have an AMOLED screen, ShadowROM works fine, until I try to flash ShadowROM with a theme...
If you flash the theme after shadowrom has its first boot then it will work
Sent from my ADR6300 using XDA App
Thanks facepunch!
Is this the main shadowrom thread? I thought there would be more, I love shadowrom with the Luna theme, been using for several weeks, will Luna work on other aosp roms too?
Sent from my ADR6300 using XDA App
hfulbri1 said:
Is this the main shadowrom thread? I thought there would be more, I love shadowrom with the Luna theme, been using for several weeks, will Luna work on other aosp roms too?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
This isnt the main thread. I'll post up a main thread as soon as our next revision is released tho
Will the next revision have the fix for slcd screens?
Is there an easy way to find out what type of screen you have?
The easiest way is to look at the SKU on your box. If it ends with W2 then you have an AMOLED screen, if it ends with W3 then you have an SLCD screen.
Other ways I've heard (but cannot verify) if the SLCD screen has little "dots" 1/4 inch apart on it that you can see when the screen is off, at a certain angle in certain lighting.
Another for sure way is to make a nandroid backup, and try to flash ShadowRom.
I have a slcd screen and used koush test 2 kernal...which got shadowrom to work. Just flashed in recovery after rom install.
SamuraiXDroid
samuraixzodus said:
I have a slcd screen and used koush test 2 kernal...which got shadowrom to work. Just flashed in recovery after rom install.
SamuraiXDroid
Click to expand...
Click to collapse
We've been playing with that kernel for a week now, and we're pretty sure we will be including it into our next release.
What do you think the issue was?
SamuraiXDroid
samuraixzodus said:
What do you think the issue was?
SamuraiXDroid
Click to expand...
Click to collapse
Drivers.
Sent from my ADR6300 using XDA App
Hey guys,
Just to let you know there is an application out there now to take care of force recalibration of the screen.
When I first got my nook I know it didn't register touch properly, so I ran some commands and it started working fine.
Decided I should make my first app something that helps people, so here you go. Checkout "nook screen recalibrate". It's a simple minimalistic application the re calibrates then reboots
Updated Version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Here's the market link.
Helpful since you don't have enough posts to post links yet. But thanks for this app!
Ironically when I go to the link and try to push it to my NC, it says it's not compatible. :X
Fine print mentions that is only works with GB (android 2.3 and above).
yep.. i dont think any rom uses anything lower than that
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
assid2 said:
yep.. i dont think any rom uses anything lower than that
Click to expand...
Click to collapse
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Not sure what exactly that application does.so can't comment.
Sent from my Nexus One
byronczimmer said:
The nookie froyo is based on 2.2.
If your software doesn't require 2.3 functionality, can you lower the required API to '7', which is the stock Android API level (2.2/Froyo)?
Click to expand...
Click to collapse
I think it should work. I shall reduce the requirements.
However there is no way to check cause my touch is working perfect now
However I find it performs better slightly if I do this once a week
Sent from my Nexus One
Updated release v2.0
Updated to version 2.0
* Better GUI
* Button to start process
* Lowered MinSDK to support froyo (untested)
Force closes on nookie 2.2
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Strange, I had reduced the minimum requirements
I have no other froyo device to test on, let me check once again against an emulator
Sent from my Nexus One
Ok maybe this is in my head, but if I run this every couple nightlies, touch feels slightly better and responsive.
Maybe it's the nightly, maybe the way it interacts, maybe the screen de sensitises over time, maybe it's all in my head
If anyone cares to do some testing, that would be great
Sent from my Nexus One
cowballz69 said:
Force closes on nookie 2.2
Click to expand...
Click to collapse
Let me know if you wanna try this so I can publish to the market
Sent from my NookColor using Tapatalk
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Try cleaning your screen prior to running the application, make sure you don't touch the screen prior to restarting
Sent from my Nexus One using Tapatalk
kruuth said:
This may sound crazy but after running this I think that the screen is actually leases responsive and now shows the "ghost" touches so badly that the on screen keyboard isn't usable. Is there something to do to fix this?
Click to expand...
Click to collapse
same thing on my end. I ended up reflashing the latest cm7 nightly and its back to the way it was
Sent from my NookColor using Tapatalk
That's extremely strange. First time I've heard issues like this crop up. Do you have a screen guard or something
Sent from my NookColor using Tapatalk
For those who would want to try, scews the S2.
But the link from nolook actually fixes it.
nolook said:
is it different from this app:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
edit: only fixed it for a short time. i'm back with some bad touch.
can you attach the .apk i cant go to market to download!! plsss
Touch Patch For Atrix V1
-Increasing touch performance
-Soft scrolling
-5 Multitouch
-Other many things...
Versions
-Fast:Extreme Performance,But little unstable
-Stable:Stable,Recommend version
-How to Apply
Download fast or stable,and flash in cwm.
And If you want discard this patch,flash original.zip
-Work
Cm9,Cm7,Blur based Roms,others...
-Not work yet
Neutrino Rom,MIUI,others...
Try this!
This patch tested on Korean Atrix Community
I will release update in several days;
Enjoy!
Will test it now - Thanks!
Edit: Works fine on Nottatrix 1.3.1. Will test it further over the next few days, but it seems to improve sensitivity of the touch recognition (especially when the screen is a little grimy).
Gonna test this and see how it works I'm on jokers CM9
EDIT: seems to be working in some areas and others not, but it helps with the keyboard on jokers a little
Sent from my MB860 using XDA
schwarzlichtkind said:
Will test it now - Thanks!
Edit: Works fine on Nottatrix 1.3.1. Will test it further over the next few days, but it seems to improve sensitivity of the touch recognition (especially when the screen is a little grimy).
Click to expand...
Click to collapse
What version is you tested?
Not working on Neutrino? Why?
Formhault said:
Not working on Neutrino? Why?
Click to expand...
Click to collapse
Sorry, I don't know
I will find it...
Sent from my MB860 using XDA
Nvm sometimes on CM9 it doesn't take the touch the first time
Sent from my MB860 using XDA
woorim98 said:
What version is you tested?
Click to expand...
Click to collapse
Like I already wrote: 1.3.1
With the touch patch stable v1.
It makes the screen really snappy, but sometimes that's limiting. Without a very steady finger it's next to impossible to produce an absolute precise touch
Sent from my MB860 using Tapatalk
Seems to works fine on CM7 05-08 build (latest)
Hmm, original version is a rollback?
In case we want the stock thing again?
If it is, i ll try this mod!
Sent from my MB860 using XDA
Does this mod genuinely make a difference or is it placebo effect?
And how does the fast one differ from the normal one in terms of touch sensitivity?
Lastly, does this mod work with CM9 and improve the dodgy touch sensitivity?
Sorry if this post sounds negative, I don't intend it that way. I've said it before, but AndroidON always makes really cool mods and this isn't an exception. So big props once again
Who said this didn't work with Neutrino? Mines working perfectly... but could it be because I installed the patch via ADB?
Anyways, my first impression is that scrolling certainly feels smoother and more 'iphone-y' - which is a good thing
It seems to act more sensitive also and swipes seem to register faster and more accurately. This really shows when you play 'Temple Run,' I actually died the first few rounds being so used to the original 'non-sensitive' touchscreen but after that, it certainly felt more snappy.
However, I did find a few niggles which are kinda hard to explain tbh. But strangely, after a reboot, it seemed to have fixed itself, which is odd but great nonetheless. I'm not fully convinced that these issues are fixed but I'll report back, but I'm sure it will be fixed in V2.
I also tried the fast version, but it was kinda weird. Especially the notification tray, it pulls down and pulls up really fast and it looks a bit weird. Also, touch responses also seemed slightly fishy. So I also recommend the stable one.
Look's like this mod may be cooked it V2.8 Neutrino - if the OP doesn't mind?
Notorious544d said:
Who said this didn't work with Neutrino? Mines working perfectly... but could it be because I installed the patch via ADB?
Anyways, my first impression is that scrolling certainly feels smoother and more 'iphone-y' - which is a good thing
It seems to act more sensitive also and swipes seem to register faster and more accurately. This really shows when you play 'Temple Run,' I actually died the first few rounds being so used to the original 'non-sensitive' touchscreen but after that, it certainly felt more snappy.
However, I did find a few niggles which are kinda hard to explain tbh. But strangely, after a reboot, it seemed to have fixed itself, which is odd but great nonetheless. I'm not fully convinced that these issues are fixed but I'll report back, but I'm sure it will be fixed in V2.
I also tried the fast version, but it was kinda weird. Especially the notification tray, it pulls down and pulls up really fast and it looks a bit weird. Also, touch responses also seemed slightly fishy. So I also recommend the stable one.
Look's like this mod may be cooked it V2.8 Neutrino - if the OP doesn't mind?
Click to expand...
Click to collapse
Scrolling is definetly faster... but see my video on this. Tried it on your V2.8 EE beta... wiped cache/dalvik after flashing the stable version. I am NOT gonna try the fast one, lol.
There are some faults, especially when you hold your finger on something (also noticeable in the video I made).
Formhault said:
There are some faults, especially when you hold your finger on something (also noticeable in the video I made).
Click to expand...
Click to collapse
Yep, that was the problem I also experienced but couldn't really explain. When you hold anything down, it spazzes up. Like try to select a a letter in a word and 'hold' your finger there, the arrow thingy will just keep 'shaking.'
If that makes sense...
That seems to be the only main issue really. I just tried the messaging app and WOW, typing is MUCH faster than before.
Formhault said:
Scrolling is definetly faster... but see my video on this. Tried it on your V2.8 EE beta... wiped cache/dalvik after flashing the stable version. I am NOT gonna try the fast one, lol.
There are some faults, especially when you hold your finger on something (also noticeable in the video I made).
Click to expand...
Click to collapse
Same problem with cm9
Sent from my MB860 using xda premium
Notorious544d said:
That seems to be the only main issue really. I just tried the messaging app and WOW, typing is MUCH faster than before.
Click to expand...
Click to collapse
You've got to be kidding. I tried to send a simple message, 4 words long... It took me 20 seconds...
It sure is faster, yeah... faster and full of mistakes...
So, I have CM7 latest nightly and I'm typing. Nothing wrong here. Didn't saw the video yet. Just reporting typing its good with this mod and SwiftKey....
Sent from my MB860 using Tapatalk 2
balintmaci said:
try multitouchvizualizer and hold down multiple fingers
Sent from my Atrix 4G
Click to expand...
Click to collapse
I just tried and worked perfectly... Didn't had that issues. Really. Maybe I can make a video to show...
I used 2 multitouch apps, btw...
Sent from my MB860 using Tapatalk 2
Any way to flash this on Neutrino ROM without ADB push?
~Sent from my Unlocked, Rooted, Faux 1.45gHz Motorola Atrix 4G~
balintmaci said:
was that some nice drumstep you were listening to during the video?
Click to expand...
Click to collapse
Emalkay - Flesh & Bone
balintmaci said:
i found that CTRL, BLEN, TCHTHR, TCHDI, MRGTIMEOUT, MOVFILTER(greatly), NOISETHR, GESTEN, PRESSPROC, DRAGTHR, NUMGEST, GESTEN, and VOLTAGE, had been changed.
anyone know what these are? and is voltage increase dangerous/why is it important?
Click to expand...
Click to collapse
Perhaps the OP could shed some light on what those values are...
The point of increasing voltage... I guess that's how sensitivity works, right? More voltage = more sensitivity...?
---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------
I made three more reboots. Plus, I played Dark Legends for about 20 minutes. Now, I made another reboot.
In Multitouch Visualiser, I don't see glitches anymore. Having two touch points on the same axis works very well. When a third/fourth/fifth touch point comes into play, things remain the same though - problematic.
Edit : NOPE. Nevermind that. It still is glitchy, even with two touch points... Just like in the video... So, nothing has improved.
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
Obartuckc said:
Any way to flash this on Neutrino ROM without ADB push?
~Sent from my Unlocked, Rooted, Faux 1.45gHz Motorola Atrix 4G~
Click to expand...
Click to collapse
I did it the old fashioned way : flash .zip via recovery (TWRP, in my case).
As many people have noticed, the home/back capacitive/virtual buttons often do not work.
http://www.pocketables.com/2013/04/...-issues-with-capacitive-hardware-buttons.html
http://www.androidauthority.com/htc-one-capacitive-button-problems-198220/
http://forum.xda-developers.com/showthread.php?p=40538985
http://forum.xda-developers.com/showthread.php?t=2231832
http://forum.xda-developers.com/showthread.php?t=2243961
http://forum.xda-developers.com/showthread.php?p=40574171#post40574171
http://forum.xda-developers.com/showthread.php?t=2248951
http://www.youtube.com/watch?v=uvxi6KUR-WA
http://www.youtube.com/watch?v=V7zKpBSluKU
http://www.youtube.com/watch?v=7v5Oc5-7rbA
http://www.youtube.com/watch?v=wxkwyyvOkZ8
http://forums.androidcentral.com/htc-one/270508-home-button-shorting-out.html
http://forums.overclockers.co.uk/showthread.php?p=24147320
http://forums.androidcentral.com/htc-one/270811-back-button.html
http://forums.androidcentral.com/htc-one/271243-button-issue-htc-one.html
http://community.sprint.com/baw/message/569148
Personally, I find it to be *incredibly* annoying and pretty much ruins the experience of using this otherwise good phone. I have already been to the Sprint store to possibly exchange it, but their demo unit had the exact same problem (and the employee I was talking to had also noticed the problem). I have also ran "getevent -lt /dev/input/event6" from adb shell (/dev/input/event6 seems to be the raw output of the touchscreen, some people said it is event5 on theirs rather than event6). This shows you raw data every time you touch the screen. However I noticed that when my touches of the home button go undetected, nothing is read from /dev/input/event6...so I am afraid it may be a hardware problem. I have 11 more days before my 14 day Sprint satisfaction period ends, so I'm on the fence on whether or not I should return it and wait for a better phone, or exchange it and probably get another with the same problem, or...wait for HTC to try to fix it with software.
Some have said a recent update to the Taiwan version of the One solved the problem...:
patato2 said:
doing a bit translation from Taiwan version if you guys can't wait. not sure if I used the correct words though, hope you don't mind.
1.29.709.12(214.04MB)
1. virtual button sensitivity adjusted
2. slow motion video quality improved under low lit
3. better Beats Audio experience
4. better background noise when using headphone
5. better bluetooth device matching
some said back button issue fixed after upgrading.
Click to expand...
Click to collapse
Further evidence that a software patch fixed the home button:
http://translate.google.com/transla...a=X&ei=fy91Ua_5HYaQqgHi_ICwCA&ved=0CGgQ7gEwAw
Poor Google Translate translation:
Did not receive update notifications
Through Settings> About> Software Update> Check Now
We can immediately receive an update notification
After the update the virtual keys become normal
There is a need to go faster
PS: Please note that this is the official update, Brush, may not be updated automatically through the official update to brush back the official
Click to expand...
Click to collapse
Here is the response I got from HTC:
Thank you for retrieving the information for me, [xxxxxx]. I did some research and there will be an MR update to fix this issue with the virtual keys. We do not have any information as to the date the update will be released since it will be released via Sprint your network provider, and it is currently being worked on.
I realize that not having the specific details such as the date is annoying, but we do appreciate your patience. I want to thank you again for sending me that information because that really helps us out a lot. Let me know if you have any other questions I may be able to address with you at this time.
Sincerely,
Casey
HTC
Click to expand...
Click to collapse
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Most likely what you are actually noticing is that not all presses are registered and you are rationalizing it by assuming that you just missed the target. In reality, there is a problem with the home/back buttons that HTC needs to fix, soon.
chogardjr said:
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
I have this issue as well. Seems like you have to hit the button in almost the perfect spot to get it to register.
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
treIII said:
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
~Sent in beast mode using my HTC One~
chogardjr said:
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Hey chogard. Waaazz up? Where's your Rom if you have the one. Wheres that odexed beauty?
Sent from my HTCONE using Xparent Blue Tapatalk 2
Lots more confirmations that OTA 1.29.709.12 solved the problem for the Taiwan variant HTC One. WHEN WILL SPRINT/HTC GIVE US AMERICANS THIS FIX?
patato2 said:
Here's some information about 1.29.709.12 upgrade (Taiwan version), and some responses I read from other forum.
And... sorry guys, I really don't know when will your updates come. and i don't have the phone yet . I envy you!
.
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Lots confirmed the home/back key issue fixed, looks solid.
2. slow motion video quality recording improved under low lit
Didn't see anyone post about it
3. better Beats Audio experience
Some said the left / right sound are better balanced.
4. reduce background noise when using headphone
a few guys said noise is "significantly" reduced.
5. better bluetooth device matching
a few guys confirmed bluetooth device matched faster.
Click to expand...
Click to collapse
For anyone interested, the Taiwan OTA firmware is available here:
http://www.androidrevolution.nl/downloader/download.php?file=1.29.709.12.zip
http://forum.xda-developers.com/showthread.php?t=2182823
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
jaybombz said:
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
Click to expand...
Click to collapse
I prefer to tap with my fingertip and this is rarely detected by the home/back buttons, which is SOOOO annoying. I'm debating trying to swap it out for a new one. From what I can tell the problem seems to affect EVRYONE, although many people might not notice or be annoyed by it. So the question is, is it truly a pure software fault, or is it a hardware fault that software (ie, an OTA) can mask or at least partially correct.
That's my preference as well - it has been an adjustment and one that I'm not terribly pleased with. I'm surprised the issue didn't show up in pre-release testing but I have to imagine it's something that software can fix with a remap of the area the system recognizes as buttons.
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Where's the Rom Fernando?
Sent from my HTCONE using Xparent Blue Tapatalk 2
It's really not an issue with the "area", as I can touch the dead center of the home button and it still won't work. Seems to me that it is either not sensitive enough, or some other problem.
Regardless, word is that an OTA fixed this problem on the Taiwan HTC One 2 days ago, so now I guess we just need to complain loud enough that HTC/Sprint pump out the fix to us ASAP before we all return our phones.
Mines like this as well, you can hit the back button dead on and no response. Hopefully they issue a fix somewhat quickly.
Sent from my HTCONE using Tapatalk 2
Having this problem as well. My device was built April 9th 2013. I can sit there and tap on the home button for 30 seconds or more in every way possible and have no registration of the contact.
This might just be wishful thinking but for some reason clicking the app drawer icon seems to fix the issue right away making me think this is software.
Other than this the build quality and everything else seems perfect.
Sent from my HTCONE using xda app-developers app
HTC needs to admit they have a problem here and advise us whether we should be returning these or waiting for an OTA patch which will be coming VERY soon.
I saw some people talking about this and didn't know what they were referring to.. I got my phone on launch day and have no issues with it, that looks super annoying
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
mang0 said:
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Calibration does not resolve the issue.
Just wanted to share an unofficial build of AOKP for our TF701T's I did for myself.
Special thanks to Team AOKP for their wonderful rom!
Disclaimer: You flash it, you break it, you fix it. I will be update the builds weekly or so as new features are added into AOKP regularly.
Flash the same as any other rom. Use current Banks Gapps.
Known issue: I have enabled the glcomposer in the build.prop because the overall smoothness and battery life is greatly improved. However, because ASUS hasn't updated past 4.3, there may be occasional graphical glitches. You can disable the glcomposer by removing the one line in build.prop containing glcomposer in it BUT do try as it is first and see the difference for yourself. I have been using it for a couple weeks now and the graphical glitches are very small and barely noticeable.
Examples of where to see smoothness include: Scrolling homescreens. Swiping pages in App Drawer. Swiping pages in the widget drawer. Swiping away notifications while on homescreen. Swiping down notifications and quicktiles while on homescreen. Swiping to Google Now page in GEL launcher.
Latest Rom here:
ROM Download
Sources used:
Device: tf701t device tree
Kernel: Kernel tree
Vendor: Vendor tree
Anyone tried it yet?
Reports are welcome and help to get some traction going.!
Sent from my K00C using XDA Free mobile app
Paulicat said:
Anyone tried it yet?
Reports are welcome and help to get some traction going.!
Sent from my K00C using XDA Free mobile app
Click to expand...
Click to collapse
Excellent work. Very fast. No graphical glitches so far that i can see. Lets of options.:good:
It's great to see another ROM option for the tf701t! I just tried this out. The graphics really are quite smooth, and I love all of the customization options. Alas, as with cyanogenmod and cromi, Bluetooth functionality is severely diminished -- a mouse barely moves the cursor at all and a keyboard has severe typelag making it unusable. Any idea what's going on thereand how to fix it? I'm happy to be a guinea pig.
Awesome, glad to see other people trying this out!
I will post weekly build updates as often as possible.
Sent from my K00C using XDA Free mobile app
Im amazed how smooth it is. I guess this shows with this tegra4 theres still room for improvement which is a good thing.
It's very nice. The camera doesn't crash, and I the current version of Netflix doesn't crash. With some roms I've had to use 3.0.
lexelby said:
It's great to see another ROM option for the tf701t! I just tried this out. The graphics really are quite smooth, and I love all of the customization options. Alas, as with cyanogenmod and cromi, Bluetooth functionality is severely diminished -- a mouse barely moves the cursor at all and a keyboard has severe typelag making it unusable. Any idea what's going on thereand how to fix it? I'm happy to be a guinea pig.
Click to expand...
Click to collapse
I'll try and take a look, busy weekend/holiday up here. New build will be up in a couple days though.
Sent from my K00C using XDA Free mobile app
Absolutely no rush -- any work you do is appreciated and I'm perfectly happy to wait patiently I'll keep an eye here and try new versions as you post them.
lexelby said:
Absolutely no rush -- any work you do is appreciated and I'm perfectly happy to wait patiently I'll keep an eye here and try new versions as you post them.
Click to expand...
Click to collapse
So I just remembered I had an old Microsoft Notebook mouse 5000. I connected it and it works perfectly normal.
No lag or delay whatsoever...any chance you have another mouse to try?
Sent from my K00C using XDA Free mobile app
Paulicat said:
So I just remembered I had an old Microsoft Notebook mouse 5000. I connected it and it works perfectly normal.
No lag or delay whatsoever...any chance you have another mouse to try?
Sent from my K00C using XDA Free mobile app
Click to expand...
Click to collapse
Not a mouse, but I had another bluetooth keyboard, so I paired it up and gave it a try. Worked perfectly fine with no typelag :/ The one that doesn't work is a combo keyboard/touchpad. I don't think xda will let me link to a product on amazon, but it's a "tp cromeer" branded case with builtin bluetooth keyboard/touuchpad. Made for the N8000, but it fits the tf701t quite nicely.
Any idea why just this one device wouldn't work?
lexelby said:
Not a mouse, but I had another bluetooth keyboard, so I paired it up and gave it a try. Worked perfectly fine with no typelag :/ The one that doesn't work is a combo keyboard/touchpad. I don't think xda will let me link to a product on amazon, but it's a "tp cromeer" branded case with builtin bluetooth keyboard/touuchpad. Made for the N8000, but it fits the tf701t quite nicely.
Any idea why just this one device wouldn't work?
Click to expand...
Click to collapse
I actually have a mini combo keyboard touchpad I can try tonight.
My guess is going to be some sort of silly device incompatibility though...
I dont have any problems with this inexpensive bluetooth keyboard.
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED
YayYouFixedIt said:
I dont have any problems with this inexpensive bluetooth keyboard.
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED
Click to expand...
Click to collapse
I have not had any responsiveness issues with this device on any rom to be honest...
For clarity, are you seeing this problem on this rom or no?
Thank you for this ROM, it feels good to know that the TF701 has not been forgotten...:good:
myeepad said:
Thank you for this ROM, it feels good to know that the TF701 has not been forgotten...:good:
Click to expand...
Click to collapse
Cheers! I'll do what I can while I have this tablet!
Paulicat said:
I have not had any responsiveness issues with this device on any rom to be honest...
For clarity, are you seeing this problem on this rom or no?
Click to expand...
Click to collapse
It happens on all roms, but it would be a very subtle thing. I dont see it really as a problem. Just something that requires a reboot.
YayYouFixedIt said:
I do find though. I dont know if its possibly the kernel or android itself or if too many apps are running in the background. Input in general and reponsiveness is lost completely until reboot. It starts to lag all input I think. Like touch sensitivity etc. I wonder if anyone else has found this on to be the case on this device. Not sure if there is some app thatll restore it by killing processes possibly. Another thing I notice is that Android is running tonnes of threads. Compared to the few that run on linux. 600+ on android. Less then 100 threads on Linux usually depending on the distro. This rom right now has 900+ threads showing in htop. But it is still smooth as butter. Maybe thats not a big deal then.
EDITED
Click to expand...
Click to collapse
Yes -- I know exactly what you're talking about I think.
On any ROM I've tried, it happens. A fresh reboot always clears things up, but after running a few apps (and / or putting the tablet to sleep overnight perhaps?) the whole system lags a bit. General stuff, like switching programs and running apps like Tapatalk and Engadget (for example). I'm forced to kill apps manually, and that sometimes does the trick.
One thing I tried out yesterday that seems to be helping -- give this a shot too: in your developer settings, you'll see that you can restrict how many background processes are running. Currently, I have background processes limited to just 2 at a time (and also "strict mode" enabled)... and I have to say, I'm noticing a difference! Might take some more testing to see what the pros and cons of this are, but if it just means that I don't have background processes piling up on me, this might be a workaround?
Aside from that, has anyone tried Greenify with good results?
Sent from my K00C using Tapatalk
Trevor_g said:
Yes -- I know exactly what you're talking about I think.
On any ROM I've tried, it happens. A fresh reboot always clears things up, but after running a few apps (and / or putting the tablet to sleep overnight perhaps?) the whole system lags a bit. General stuff, like switching programs and running apps like Tapatalk and Engadget (for example). I'm forced to kill apps manually, and that sometimes does the trick.
One thing I tried out yesterday that seems to be helping -- give this a shot too: in your developer settings, you'll see that you can restrict how many background processes are running. Currently, I have background processes limited to just 2 at a time (and also "strict mode" enabled)... and I have to say, I'm noticing a difference! Might take some more testing to see what the pros and cons of this are, but if it just means that I don't have background processes piling up on me, this might be a workaround?
Aside from that, has anyone tried Greenify with good results?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Honestly guys, I don't see this issue using this AOKP rom...I've left it for a few days no reboot, and I don't see any slowdowns/lag.
On a brighter note, I have a new build ready to be uploaded tonight.
I messed up some merges for battery/charging and was struggling to sort it out the last couple days.
All good now.
New build will be up later tonight.
Paulicat said:
Honestly guys, I don't see this issue using this AOKP rom...I've left it for a few days no reboot, and I don't see any slowdowns/lag.
On a brighter note, I have a new build ready to be uploaded tonight.
I messed up some merges for battery/charging and was struggling to sort it out the last couple days.
All good now.
New build will be up later tonight.
Click to expand...
Click to collapse
Got it. In that case, I'll have to give this a shot! ☺
Sent from my Nexus 5 using Tapatalk