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.
Related
New sprint rom?? http://forum.ppcgeeks.com/showthread.php?t=10293&page=3
http://download.america.htc.com/RUU_...PL106_Ship.exe
It's been confirmed. That is the new official ROM for Sprint. It fixes the Bluetooth issues among others. No Rev. A or GPS of course, but that was expected.
question is, is this really "better" than the alltel rom that has been available for a long time already over at PPCgeeks...
The alltel rom fixed the BT and alarm problem as well. I'm excited to see that Sprint finally caught up, but I'm wondering if this is better than the setup I currently have.
Well I for one am happy and upset.. I would like to see REV A , as I need the faster upload speeds for sending big files from my 4gb micro sd.
I havent tried the Alltel rom, but the new sprint rom fixes the keyboard lag + wm6 responsiveness problems.
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
kmartburrito said:
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
Click to expand...
Click to collapse
i took the plunge yesterday, i skipped out on all the sprint customization and everything turned out ok....haven't tested bluetooth yet but everything you said seems to be on point...
kmartburrito said:
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
Click to expand...
Click to collapse
Just to clarify this is part. A hard reset will completely erase any carrier customizations there is absolutely no reason for installing extrom, hard resetting then skipping. Just start out with the hard reset, skip customizations and you'll be good to go.
Although there are still the other bugs with the update =)
Just installed it a while ago, skipped the sprint customizations, everything seems to be running good and actually noticeably quicker than before. New startup screen is cool too, no problems thus far =)
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Seems to only happen to some people though. I have had my phone on pretty much straight since the rom update.
there seems to be a major bluetooth issue where the BT just shuts off periodically.. Not sure how,but they found a way to make bluetooth even worse!
I can't carry on a conversation without BT shutting off on me.. (or use the gps without it shutting off/etc..)
-mark
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
GoodThings2Life said:
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
Click to expand...
Click to collapse
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
wsparvis said:
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
Click to expand...
Click to collapse
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
No, "most" users are not experiencing better results. I've been using this ROM with poor results, as have many others. Read this thread for many sad tales of woe:
http://forum.ppcgeeks.com/showthread.php?t=10302
Basically, the new ROM does fix a bunch of things, but breaks others, so I would not recommend installing this ROM.
1) Locks up when changing from Sprint to roaming. You can test this by manually switching from Sprint to roaming and back a few times, you WILL get a phone lockup.
2) BT turns off randomly for many users.
3) Turn on BT, let unit sit for a few minutes until it goes to sleep, turn unit back on, dpad no longer works. I have seen this myself many times.
Don't install this update --- use the Alltel ROM or wait for another update.
GoodThings2Life said:
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
Click to expand...
Click to collapse
1) You're incorrect in stating that most users have no problems, etc. Some do, some don't. Read the posts at ppcgeeks, pdaphonehome, BAW, hofo. I am not at all alone in having problems.
2) I downgraded 2 days ago, and my Mogul runs fine again - just exactly like it did for the 1st 3 months I had it. It's not my hardware! It's a bad ROM release.
Not everyone uses the phone in the same way at all. So of course some people will not see the same problems that others do.
If you never use Bluetooth and never roam, then this ROM will work for you. Otherwise, it will cause problems. For me, Bluetooth works much better in 2.09, and I rarely if ever see lockups as I have with 2.16. So, I'm going with 2.09 for now. The alarm problem IS fixed in 2.16 but I never use alarms on my phone so it's not an issue for me. Freezes when roaming ARE a problem.
cbunting said:
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Click to expand...
Click to collapse
is colonels rom built on the alltel core rom? if so it may be our best bet as of now.
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...
So I have the known freezing problem, where it freezes and have to reboot.
Well started having WiFi issues as well, ****ty connection, to having to turn off and turn back on the connection because it wouldn't work at all. This is related to the freezing problem correct? Also, how does it seem to be getting worse? Shouldn't it just be the same until they send an update?
Yes, I have tried all suggestions options.
From what I've read here on the forums along with a few other sites is that the WiFi freeze is an issue with GNex and 4.2.1. Just hold tight for an update and the issue should be fixed.
But with random reboots, are you using a stock ROM and Kernel?
TheGrayHatter said:
From what I've read here on the forums along with a few other sites is that the WiFi freeze is an issue with GNex and 4.2.1. Just hold tight for an update and the issue should be fixed.
But with random reboots, are you using a stock ROM and Kernel?
Click to expand...
Click to collapse
Yes it's stock everything.
Started noticing other things, think it's related to WiFi somehow, for example this site will not let me log in, I type my credentials it says thanks, and then loads the page again without my logged in. Also, another site does not let me type, i hit the first letter and the keyboard goes away.
Some weird things. Hoping it will all be fixed with an update.
I think I also noticed a very small light bleed (only noticeable on the nexus loading screen), should I try to exchange it or is that pretty much the same on all devices?
bmancell said:
Yes it's stock everything.
Started noticing other things, think it's related to WiFi somehow, for example this site will not let me log in, I type my credentials it says thanks, and then loads the page again without my logged in. Also, another site does not let me type, i hit the first letter and the keyboard goes away.
Some weird things. Hoping it will all be fixed with an update.
I think I also noticed a very small light bleed (only noticeable on the nexus loading screen), should I try to exchange it or is that pretty much the same on all devices?
Click to expand...
Click to collapse
Hmm, if your device does suffer from light bleed, then it should be reproducible (In my opinion).
To try and reproduce it I would do this:
Turn brightness all the way up and disable the AUTO setting
Download the app, Display Tester, from the Play store (There is a myriad of similar apps, find one for you)
Optional: Check for dead pixels by cycling through the colors
Get to the black preset and see if you notice any shades of white coming through. If the black is consistent with the remainder of the screen, then no bleed. If not, they you may have some
Truth be told, I've read many posts in-which people complain how this is their Nth unit. If you feel that the minor bleed ruins your experience with the device, then return it. If not, then enjoy it! My personal opinion is to keep the device and not risk receiving a device with greater issues. And with the wifi lag, are you using Chrome as your browser? If so, I would try boat Browser (Flash Support) or Dolphin Browser with Jetpack. If that solves the WiFi issue (credentials) then there you go! If it doesn't then you can always try flashing a ROM or Factory Resetting. Good luck! :good:
I will try that out.
And with the browser, it's not just the browser with issues, other internet apps do have issues as well.
*update
I tried the test, and it seems there are two small areas at the top right side of the screen. I can only see it on black, so it does not wreck my experience.
Something like this, does it get worse? The year warranty that it has, is this something they will fix/replace?
I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11
ThomasBags said:
I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11
Click to expand...
Click to collapse
You talking about the tablet itself, or in my router settings? How would I do that on the tablet?
I checked my router, it's on Channel 6, so not going to help me.
You should be able to change the channel, but I don't see a correlation between the two.
ThomasBags said:
I found you can fix wifi issues temporarily by switching the channel to 8 or anything other than 11
Click to expand...
Click to collapse
Changing the wifi channel may help, it would depend on your network and the networks around you though.
I've had the same issues with wifi it's an absolute nightmare. I thought my first tablet was genuinely faulty since I couldn't find too many complaints here about the wifi. However the replacement I have been sent is the same. I'm not sure if it's an issue with 4.2 and certain routers but I had the wifi drops, and more annoyingly I had poor wifi signal that would frequently drop to no bars and cut the video I was watching at the time. Very frustrating.
I have not had a chance to test my nexus 4 however the wifi reception on that is pretty poor too while my old desire hd is fine so I'm sure it's android. Not sure how long it's going to take for a fix of any kind, there are a few reports on the Google submission page with a lot of replies.
Best thing to do is to submit a bug report to Google. At the very least it may get them to actually acknowledge that there is a problem with jelly bean.
Yeah it's starting to pass me off, it's getting worse by the day. Almost unusable.
Not sure if I should send back or wait for update.
I've been running on 5.0 for about a week (stock, rooted). I rather suddenly had the tablet fail to auto-rotate, but rebooting sorted it out at the time. Now it completely refuses to rotate. Not only that, but every app I've tried that reports sensor data doesn't even acknowledge the existence of any input other than the touchscreen and the microphone. I've tried reflashing 5.0 to no avail, and I'm in the process of going back to 4.4 to see if that does anything but I'm not feeling hopeful about it.
Does anyone have any ideas of what else I could try? I'm pretty sure it's well out of warranty (rooting aside), so I'm not sure how feasible it would be to get support on it from Asus. I'm considering popping it apart and seeing if anything obvious is wrong but I'm not sure what I'd be looking for.
Klades said:
I've been running on 5.0 for about a week (stock, rooted). I rather suddenly had the tablet fail to auto-rotate, but rebooting sorted it out at the time. Now it completely refuses to rotate. Not only that, but every app I've tried that reports sensor data doesn't even acknowledge the existence of any input other than the touchscreen and the microphone. I've tried reflashing 5.0 to no avail, and I'm in the process of going back to 4.4 to see if that does anything but I'm not feeling hopeful about it.
Does anyone have any ideas of what else I could try? I'm pretty sure it's well out of warranty (rooting aside), so I'm not sure how feasible it would be to get support on it from Asus. I'm considering popping it apart and seeing if anything obvious is wrong but I'm not sure what I'd be looking for.
Click to expand...
Click to collapse
I had same problem with my N7 2013. First: I opened the back and secured a lousy cable, closed, worked almost 1 full day till everything stops. I also used my book case with magnets. Then: I reopened, secured the other side too of the lousy cable and closed. No case till this, 5 days are passed and no error. So, due to my flaw in the modus operandi, now I don't know if it was for the cables of for the case with magets. I hope the second, I won't use that case either anymore :laugh:
Hope this can help (even if I have the 2013 version)
I have exactly the same issue. My Nexus 7 2013 is on 5.0.1 and rooted. I nnoticed the issue yesterday. First alerted by screen rotation not working, I used CPU Z to see if the compass was detected and I found the sensors page completely blank.
Any help would be greatly appreciated.
I'm on the 5.4.0.1 build, and I'm having an odd reoccurring issue that's driving me crazy.
I'll install the Google stuff in the proper order using the APKs (instructions from a post on this site; I've tried other kits/instructions, same results), reboot at the proper times, and it'll work fine for a brief time. All of a sudden the touchscreen will start to glitch out badly-- a touch on a given spot will register countless presses on the same X axis, but going up or down the screen (looping at the edge) wildly, causing a lot of stuff I don't want to press to get pressed.
If I do a factory reset, it doesn't fix the issue. I have to rewrite the firmware by doing a ADB sideload after clearing cache and factory resetting to get the touchscreen to work normally again.
Any ideas? I really kinda need access to Google Play if at all possible.
Firehawke said:
I'm on the 5.4.0.1 build, and I'm having an odd reoccurring issue that's driving me crazy.
I'll install the Google stuff in the proper order using the APKs (instructions from a post on this site; I've tried other kits/instructions, same results), reboot at the proper times, and it'll work fine for a brief time. All of a sudden the touchscreen will start to glitch out badly-- a touch on a given spot will register countless presses on the same X axis, but going up or down the screen (looping at the edge) wildly, causing a lot of stuff I don't want to press to get pressed.
If I do a factory reset, it doesn't fix the issue. I have to rewrite the firmware by doing a ADB sideload after clearing cache and factory resetting to get the touchscreen to work normally again.
Any ideas? I really kinda need access to Google Play if at all possible.
Click to expand...
Click to collapse
Could be a bad screen. You can download touch screen repair apps and try a few of those. Could be dust stuck in between the casing and screen. A safety pin does good to clean that, just be careful. If a new device, you have 30 days to return it for a replacement. First I heard of this issue so that's about all I got right now.
DragonFire1024 said:
Could be a bad screen. You can download touch screen repair apps and try a few of those. Could be dust stuck in between the casing and screen. A safety pin does good to clean that, just be careful. If a new device, you have 30 days to return it for a replacement. First I heard of this issue so that's about all I got right now.
Click to expand...
Click to collapse
This is my second unit. I expected it might be a hardware issue, and indeed it did act like it, but doing a adb sideload, etc does fix it.
I've also just confirmed the problem starts as soon as I install the Google Framework. Time to do another ADB sideload since I broke it again...
Okay,, no fault of anyone here, I've just hit my patience limit with the irritating Amazon-side stuff-- I've been fighting this for nearly a month and I'm almost out of return time.
Anyone got any suggestions on a relatively cheap Android tablet with at least comparable specs, actual Google Play support, and hopefully OS updates? Bonus if it doesn't have the Bluetooth controller lag issue my Nexus 5X suffers from.
Touch screen is prefect, no glitches discovered. @Firehawke, Fire HD 8 is a best possible cheap Android-based tablet of all the time, you can't find better option even with the cheap Chinese junk-droid from Aliexpress.
Firehawke said:
Okay,, no fault of anyone here, I've just hit my patience limit with the irritating Amazon-side stuff-- I've been fighting this for nearly a month and I'm almost out of return time.
Anyone got any suggestions on a relatively cheap Android tablet with at least comparable specs, actual Google Play support, and hopefully OS updates? Bonus if it doesn't have the Bluetooth controller lag issue my Nexus 5X suffers from.
Click to expand...
Click to collapse
If I had a choice, I'd return it and get a Fire 7 (not one from 2017) and hope for one that has a rootable OS. I love my HD 8, but I've pretty much gutted it of Amazon. The only thing not making it 110% is not having root.