Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Hi everyone. I wanna tell you about something weird happening to my HD2 lately that’s really pissing me off. Every once in a while, when I wake up my device from standby or for instance after receiving a text, I’m not able to unlock my phone!! I try to move the slider all the way to the left or right, but the screen is totally unresponsive. It’s like my fingers aren’t touching the display at all.
I therefore turn the screen off and on again several times and eventually I happen to “resume” the screen sensitivity and reach the homepage. The phone is not frozen since it works fine when unlocked, just the screen.
Even more weird is the fact that if I remove the battery and restart the device, when I get to the PIN Code screen I’m still not able to enter any digit since the screen is still unresponsive and I have to do the whole display off/on routine several other times till it gets sensitive again. This problem is starting to happen more and more frequently and with several ROMs.
At first I thought it was rom related so I switched from “Miri v17.4” to “Energy June,11” and then to “HyperROM Ultimate v12”. Nothing, nada, zip. The problem still remains. Then I tried running Miri v17.5 with no extra apps installed, like BSB or CHT or whatever because I know sometimes programs can have incompatibilities with roms so I tried to keep it as stock as possible, but that didn’t solve the situation either.
I performed a “task 29 by doloop” between each flashing and tried many radios as well (2.10.50.28_2, 2.10.50.26, 2.11.50.20 and now I’m on 2.12.50.02_2).
I’m really desperate because I don’t know what’s causing this. Any help/advice is greatly appreciated!
Sorry for the long post, I tried to describe this issue as accurately as possible.
Thanks.
Many people are having this problem. Many topics about it too, but no final solution.
In my case two things seemed to help: adjusting light settings (turn off automatic adjustment) and taking out SD card and putting it back in, and/or change the SD card to a faster one.
I even reflashed my phone and the problem persisted until I was finally able to put back a stable backup.
First off thanks for your reply. I just checked and automatic backlight adjustment is on. Are you saying this problem might however be ROM related? Some time ago when I was using MIRI v16 this problem occurred just a couple of times and I didn't give it too much attention. I was wondering if the touchscreen might be faulty and therefore in need of assistance..
I don't think it's ROM related, well at least not in my case. I didn't have any problems using stock ROM and an 8 GB card, until I bought a 16 GB card (the exact same day the problem occured for the first time, I just didn't realize it could have something to do with the card, until I read this forum and found my own post about the screen not being responsive dated May 3rd, the day I started using the card ).
I installed Cookie's Home Tab 1.8.5 (on my card) and the screen became unresponsive again and I had a lot of problems uninstalling it, because of that screen problem. So I did a hard reset and the problem still persisted, couldn't even use the wizard because the screen wouldn't respond.
I think it's a combination of hardware and software problems. Hardware meaning SD card and software meaning power settings (automatic light adjustment), maybe the way the software is written to the SD card, I don't know.
I've got it working now, but I'm a little afraid to do any more tweaks and I would very much like to use the light adjustment settings.
So I'm still testing and maybe some day I'll buy a new SD card class > 4. The 4GB card, class 6 seemed to help the last time I hard reset my phone.
Yeah I get your point but still I wonder why has this issue just happened to show recently. With the older ROMs everything was working fine and none of the above ever occurred.
That leads me to 2 conclusions:
1. Newer ROMs (mixed updated packages from different sources) are less compatible with the phone and thus create a new series of problems, mine included (just take a look at some of the latest rom changelogs to see for yourself what I mean). All of this not to mention the extra complications that programs such as CHT have caused..
2. The screen has became faulty. Maybe in the earlier phases the problem just happens occasionally and becomes more and more existent as the touchscreen module “degrades” (or something like that..)
Just yesterday I turned my phone on and the screen was unresponsive (I’m running miri v17.5). I tried removing the SD Card and disabling the auto backlight adjustment but none of these helped.
Anyway, here’s what I’m gonna do in the next days:
I’ll flash MIRI v16 which is a ROM I don’t remember having this particular problem with and I’ll see how it goes. Should the unresponsiveness occur again, I’ll go with a stock ROM (the one the phone came with).
If both of these tests fail then I’ll send it in for repair.
It goes without saying that I’m all ears for any advice/help you guys can give.
Thanks.
http://www.youtube.com/watch?v=VHy_t-DHqq8&feature=related
I did... It's working now...
Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.
Hi depakjan, This is great, thanks for tracking these issues.
can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.
i think the bsod is fixed with 2.12 radio and above..
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem
Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..
Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Led Notification is not functioning, especially on Sense build.
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!
Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.
Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy
Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
gitm said:
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
Click to expand...
Click to collapse
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
I've had the exact same issue when using RC2 with faux's kernel. I've tried the LV and SV versions and still had the same problem.
Finally I gave up and just reinstalled RC2 without faux's kernel and I have not had any issues.
Sent from my HTC Glacier using XDA App
Tazzaras said:
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
Click to expand...
Click to collapse
Yea I have wiped and formated everything. The install I am now on I actually waited a full 30 mins instead of recommended 5 min.Nothing against teamroyal as I have mad respect for what they do, but RoyalGinger has made me a pro at installing it
So far no kernal crashes, which has given me a perma-grin. I'm gonna flash back to the latest LV version of faux kernel (the one that came with it). I'm sure it will be fine as I think the whole problem has to do with the screen off animation. I'll report back with my results.
Update:
It is the screen off animation that is causing my issue. I have flashed the latest kernel and everytime I have the off animation on, it locks. On screen animation works when on by itself, but turn the off animation on, power on and off a couple of times, and it will crash. I'll try to grab the logs and submit them.
Well seems everytime usb debugging is on it simply won't crash, and I can't get emulator to record when the phone crashes. Sorry I can't get a logcat
Same here on my wife's phone. Had to restore a 2.3.2 nandroid because both (CM7 rc2 and RG 1.3) were freezing on wake. Dunno what the cause is because on my mytouch RG 1.3 runs fine since it dropped......
If u read thru the post for Royalginger 1.3 it says that the best kernel for the rom is the kernel that it comes with... it also says u will get best/smoothest response with it set at smartass... I'm not sure if its changed since I've read but give it a try...
Sent from my HTC Glacier using XDA Premium App
So the good news is I was able to get a logcat. I didn't realize that when the phone completely freezes (power on/off does nothing) you can still dump the logcat, hooooray for me. So here is my logcat file, and for the record this ONLY happens when I have the off and on screen animations enabled in the "CyanogenMod settings", with them off I can power on and off without the phone crashing.
[ROM] - RoyalGinger 1.3
[Kernel] - version 2.1.0 Low Voltage
[CPU Frequency] 245~1113
[Governor] Smartass
[Theme] - Honeybread (CM7 honeycomb theme)
[Live Wallpaper] - None
Update:
I did what was instructed in the dev section for flashing the latest Faux Kernel (2.1.2.1). I wiped the cache and delvikcache. I then fixed permissions and installed the kernel. Once the phone got to the lock screen, I waited 15 minutes for the kernel to "settle", immediately rebooted and let it sit for another 15 minutes.
Once that was I done, I enabled both the on and off screen animations, and after power on and off about 20 times, it crashed the phone again. So I am still having the same issue. Also as a heads up, I tried different themes just incase it was the theme, but that made no difference. So I reverted back to screen on/off animations as all off, and still no lockups. I have attached another logcat file, just incase there is some new data in it.
On another note, there simply isn't any last_kmsg file, so I'm sorry I can get you folks the file. It isn't on the phone when it crashes or even when the phone works correctly.
Have you done anything with spare parts?
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
gitm said:
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
Click to expand...
Click to collapse
gitm - 1.3.1 should be out by tonight, barring anything weird coming up last minute in testing
and this has the new 2.1.2.1 faux kernel built in but if you want to try in the mean time - go to his thread and flash that kernel (wipe both caches and fix permissions, then flash kernel, then settle for 5 mins on initial boot, reboot, settle another 5 min, then go)
can't remember, are you using stock launcher or a 3rd party?
Using launcher pro.
As for the new kernel, it is still causing the same issue. In my logcats, it says "cpu pegged", and that is pretty odd. Hopefully 1.3.1 will fix it, but I will keep testing and keep you posted
For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.