Related
Hi there!
I bought a damaged G1 from ebay to hack on.
There is some strange behaviour, that seems to be related to the trackball.
Everytime i scroll some pages for a while, the trackball is going really mad.
It toggles between applications, e.g. starts phone app or contacts and enters weird numbers.
If i leave it completely untouched the system behaves normal.
Just to give it a try, i disassembled the device and removed the trackball mechanic. Result: Everything behaves normal.
Due to these problems, i started a little research on the trackball parts.
So here's what i found (see attachment).
I will do some further investgation and check out if i'm able to fix this issue.
My suspicion is, that one of the magnetic sensors got damaged and toggles between high and low all the time, even without the trackball beeing moved.
Did anyone realized such a behaviour on a G1?
Any comments are welcome!!
Regards,
scholbert
Note that the trackball on HTC DREAM is identical to the trackball used in RIM cripplephones, so you can find a replacement easily... you can probably get a broken RIMjunk for $5 with good trackball hardware, or you can try at something like blackberrytrackball.com.
Hey lbcoder,
i knew that the touchball is identical to those used in the blackberries.
Thanks anyway to add this info and for pointing me at the web link!
Got a spare part with broken flat cable from another G1 device.
I'll have to do some further testing and then start the soldering job
BTW the trackball itself is not the damaged part. It's one of the magnetic sensor parts, i suppose.
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Regards,
scholbert
It *is* magnetic though, so theoretically it *could* be an issue with the mechanical components rather than with the sensor itself... i.e. something stuck in the wrong place getting picked up by the sensor as continuous. Unless you've tried swapping them out already.
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
...
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
Click to expand...
Click to collapse
Sure, just did some test with the other mainboard (connector for touchscreen is damaged on this part).
The trackball behaves normal with this combination.
So the sub-PCB must be O.K.
I'll try searching for something weird on the original mainboard.
Damn, this would be much harder to fix i suppose
I'll keep you informed!
Anyway, maybe the datasheet would be of any use for the curious geeks
Best regards,
scholbert
experts welcome
Hi again,
after some more testing and examination of the hardware stuff, i'm in doubt that this problem is hardware related.
So i started to think of some software related issues.
I know that bootcode and Android filesystem should be aware of bad blocks in NAND memory.
But anyway here's the history of the device (so far i know it):
- It came to me with stock bootloader and firmware 1.5
- A stock update was made to firmware 1.6
- I did a downgrade to RC7 using a goldcard
- Rooted the device using telnet
- Installed cm-recovery-1.4
- Followed the steps from cyanogen's wiki to move to v4.2.12.2
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
- Also did a radio update to 2.22.19.26i
- Installed Hard-SPL as well
Everthing went fine, also no problems during registering to a google account.
I am able to boot into HSPL and the cm recobery is also intact.
It's very strange that the trackball weirdness did not change during all these up/downgrades.
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Apart from that the device behaves quite normal...
What the hell is wrong with this device?
Could there still be some corrupt areas in NAND caused by bad blocks even after reflashing the system?
Any advice would be welcome!
Regards,
scholbert
scholbert said:
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Click to expand...
Click to collapse
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Hi jalsing,
thanks for your reply
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
Sounds like hardware related damage, because this occurs in recovery mode as well. Maybe the pushbutton underneath the trackball causes this issue, while pressed.
Could be some corrosion or similar causing this...
Is there anyone who made some experience with file corruption or bad blocks?
Regards,
scholbert
scholbert said:
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Click to expand...
Click to collapse
I have noticed some weirdness in the power button, but I am thoroughly convinced that, at least in my case, it must be hardware related.... if I just shove down on the power button with the pad of my finger, it goes off and then right back to the lock screen. If I press the power button on the 9-clock point with a finger nail, it behaves as expected.
Although I must admit that this appeared coincidentally with a radio firmware upgrade.
Hey there,
I have been having an odd issue too although one that has not been mentioned. About a week ago when i scrolled "left" or while landscape "down" the trackball got jammed every 3 rotations. When you continue scrolling it repairs itself temporarily and then returns. This issue is still present but is not quite so bad.
I'm guessing that this would also be a hardware issue. Its not at a stage where its overbearingly annoying yet, just wondering if anyone else has similar issues.
Hi vonapets,
have you tried to check your hardware with HTC Dream diagnostic programm on sdcard? You'll have to create a "goldcard" and with the file DREADIAG.nbh.
Insert the card and enter bootloader mode, the test software will load automatically. Please search the forum, if you don't know what i'm talking about.
Anyway i did these tests on my device sometime ago and all hardware test were successful.
That's why it's all so strange
Especially i run the button test several times, and the test software did pass with no errors.
Regards,
scholbert
???
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
jalsing said:
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
+1
i have trouble using recovery too. I have to press it very lightly to get it to select only once otherwise it clicks several times ><
Not a huge issue for me really, i don't use it that often, but it is pretty irritating.
But, no. I've never had it enter any numbers or anything, that is strange.
However, i do have a strange problem where when the phone receives a slight knock, like if it's in my pocket and it bangs against something, or i drop it a couple of inches onto my desk or something, a random app will launch. I have no idea why this happens and it's not anything coming in contact with the screen because it happens even when it's locked. It's usually the market which opens too for some strange reason. Oh, it also reboots sometimes too
Yeah, i think i need a new phone
scholbert said:
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
Click to expand...
Click to collapse
Virtual keyboard? Or touchscreen? Is the virtual keyboard actually listed as a separate input from the touchscreen? If it is, then how could it even be triggered when the vk isn't even opened? Or is the vk open when this weirdness happens? Could it simply be the digitizer that's borked?
Here's a REAL SIMPLE IDEA: clean the digitizer with rubbing alcohol. Can't hurt, and now that you bring touch events into the picture, there is a little bit of a dejavu feeling starting to come over me -- not from personal experience mind you, but I do recall someone mentioning something about a greasy digitizer causing some weird problems.... that went away when it was properly cleaned.
And if nothing else, if it happens to be a digitizer problem and the digitizer is totally borked, try disconnecting it. You should still be able to navigate by trackball and hack on it without a functioning touchscreen.
I know it sounds confusing, but it's true...
Thanks for the replies!
Is the virtual keyboard actually listed as a separate input from the touchscreen?
Click to expand...
Click to collapse
Yepp!
If it is, then how could it even be triggered when the vk isn't even opened?
Or is the vk open when this weirdness happens?
Click to expand...
Click to collapse
Yepp!
BTW, you may type characters on the vk simultanously, while there are numerous 3's fired from somewhere inside the system.
The ascii changes if i also scroll the trackpad....
If you are able to close vk it opens up again randomly
Could it simply be the digitizer that's borked?
Click to expand...
Click to collapse
Nope!
Already did test with disconnecting the digitizer, same behaviour.
Very wicked and confusing
I really think there must be something destroyed inside the MCU.
Short circuit or ESD damage on a GPIO bank of the chip.
I will do further debugging.....
scholbert
...not givin' up
Hey there,
i don't know if this is still of interest for someone, but anyway here's updated information about this confusing behaviour:
- booting into recovery console (different kernel, only initrd running from RAM)
- scrolling up with the trackball causes ASCII char "u" in this console
- after scrolling the hardware keyboard is blocked
Using SHR kernel:
- used sd boot image from leviathan and flashed it to the boot partition
- sdcard is used as rootfs
- system boots up after login i enter the console
- scrolling up with the trackball causes strange ASCII string "u542i3" in this console
- after scrolling the hardware keyboard is not blocked
Pretty sure that some parts of hardware are causing this "ghost" input.
I decided to put the mainboard into pure alcohol for some hours.
Though the humidity stickers on my mainboard never turned to red, i just want to make sure that there's no dirt causing this strange effect.
Anyway it's my last hope....
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Would be very helpful to find the needle in the stack
EDIT: In the meantime i found out a lot, about the internal components of the HTC dream.
If there's some interest, i may open up a new thread post some information about it.
Cheers,
scholbert
O.K. no ideas anymore.
Quoting myself:
scholbert said:
...
I decided to put the mainboard into pure alcohol for some hours.
...
Anyway it's my last hope....
Click to expand...
Click to collapse
Last hope has gone!
Some hardware part has also gone, i suppose.
Battery life was always very worse using this mainboard, which is another indicator, that something hardware related had gone mad.
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Click to expand...
Click to collapse
Anyone??
Whatever, i think i'll use that mainboard for some awesome experiments
Bye bye,
scholbert
Hey, new to this forum, and just stumbled across your post searching for a resolve to my problem, which seems to be very similar to yours.
Phone seems to work fine except:
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Seems to flatten the battery pretty quick.
I stripped the phone checked everything clean and dry etc, tried turning the trackball upside down on the offchance, but no change. I have done nothing software related as I'm not too clued up on that side of things. It has the std 1.6 operating system as far as I know.
I have no clue where to go from here with it though, think my best bet might just be to get another one that needs a screen or something and use mine for parts?
Good to see I'm not alone with this issue though so there's a chance someone may figure it out.
....at least i'm not alone
Hi ram5ay,
thanks a lot for your reply!
ram5ay said:
...
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Click to expand...
Click to collapse
That's exactly the behaviour of my device.
Seems to flatten the battery pretty quick.
Click to expand...
Click to collapse
True, i also observed this issue.
Seems that parts of the hardware are damaged or not set up correctly due to some other error.
As a result some of the GPIO's may act as an output and are shortened to Vio or GND. This could be a reason why the battery got drained so fast
Anyway, as i already wrote down, got no clue how to fix this.....
Best regards,
scholbert
scholbert said:
got no clue how to fix this.....
Click to expand...
Click to collapse
Cool man, no worries. Maybe futile, but I'll prob pull mine apart again and have another look, if I have any success I'll keep you posted.
Good Morning Guys,
I have a strange experience to tell to me fellow users. After using my Samsung Focus, I placed it next to me, momentarily, on the sofa. With the device still on, no lock screen, I turned to it and tried to flick the start screen up to get to the marketplace (which is on the bottom of my start screen). There was no response.
I picked up the device and the start screen scrolled to the bottom when I flicked to the bottom, as I normally experience.
I placed the phone back on the sofa and tried to perform the same task, but the screen was unresponsive. I propped the phone up against the back of the sofa and tried to the flick the screen up, no response. I placed the phone on a wooden end table - the screen responded to my touch.
Has anyone else experienced anything similar?
Thanks for your time,
M
Sometimes this happens to me. It seems my thumb gets better response than my finger, but maybe it's because I hold it up. Doesn't happen often, but it is a little annoying. Hopefully it will be addressed in an update.
THanks for your input. Maybe we need to have a greater electrical field
Shocking eh?
Same thing sometimes my phone thinks I'm clicking on something when scrolling. It just stops and opens w/e I was over. Also noticed it only happens when I use a finger that isn't my thumb
Sent from my SGH-i917 using Board Express
This happens to me when the phone is on its back flat...It's like it doesn't recognize that it is being touched. It is annoying but I think i will deal with it for now.
Biggzz said:
This happens to me when the phone is on its back flat...It's like it doesn't recognize that it is being touched. It is annoying but I think i will deal with it for now.
Click to expand...
Click to collapse
This is exactly what happens to me; however, for me it has to be surrounded by either fabric or placed on paper (although there is some slight touch responsiveness on paper).
However, if the device is flat on it's back and I hold the edges with my other hand, the screen responsiveness returns.
I was wondering whether electrical grounding and/or static electrical buildup is an issue.
Thanks for everyone's responses so far. Once I get a few more peoples responses (and maybe some suggestions !!) I may forward the issue to Samsung.
M
I have noticed this same issue with my Focus as well. At first I thought it was just in my head but it happens all the time when I lay the phone flat on my bed.
All of your situations have happened to me.
It has to do with whatever happens when you're holding it. Touch responsiveness and accuracy go way, way, way up when holding it. But if it's lying on something non-conductive or even in a dock of some sort, it gets funky.
I mention some experiences of my own in the Multi-touch Issues thread.
I"ve submitted the question to Samsung via their Community Q&A webpage. The question will show up in approximately 72 hours.
The question was submitted at 7:45pm 11/22/10 Eastern Standard Time (EST). Hopefully those details will help you find the question when it's posted. It's posted under the name Molal
I included a link to this thread, so please continue to post your experiences, even if you have experienced nothing of the sort described here. I want it to be as objective as possible
Thank you all.
M
Molal said:
I"ve submitted the question to Samsung via their Community Q&A webpage. The question will show up in approximately 72 hours.
The question was submitted at 7:45pm 11/22/10 Eastern Standard Time (EST). Hopefully those details will help you find the question when it's posted. It's posted under the name Molal
I included a link to this thread, so please continue to post your experiences, even if you have experienced nothing of the sort described here. I want it to be as objective as possible
Thank you all.
M
Click to expand...
Click to collapse
It is annoying as i like to lay my phone on a table or desk and still use it.
Could it be related to this?
http://www.youtube.com/watch?v=vL6sLW7Ll0E&feature=player_embedded
Def. Not as bad as that but it is annoying. Hopefully someone can find a simple mod to fix this. I wonder if using a case would get rid of the issue
Sent from my SGH-i917 using Board Express
MikeyMike01 said:
Could it be related to this?
http://www.youtube.com/watch?v=vL6sLW7Ll0E&feature=player_embedded
Click to expand...
Click to collapse
Excellent find, thank you MikeyMike. This is exactly what I experience.
M
MikeyMike01 said:
Could it be related to this?
Click to expand...
Click to collapse
Interestingly enough, my experience on my Focus is the opposite of that..
i.e. when I place it on the table - the phone is *less* responsive compared to placing it on my desk mat (leather) - which is is more responsive.
Overall - it's not as bad as the video. The phone is just less accurate (i.e. I swipe the phone to move the tiles and it opens the program at the start of my swipe instead of moving the tiles). In the hand, the phone is very responsive - and - if I touch the top/bottom of the phone with another finger on the same hand as my "swiping" finger - it's responsive no matter what.
I too find the focus touch sometimes screws up, it happens randomly, also the browser seems to scroll not as smoothly as at first.
I'm really looking forward to some Microsoft updates, but overall the phone has been really good, I've even got adjusted to the onscreen keyboard.
Using focus now.
Its also the first phone that works well enough I have used where I don't mind browsing my morning sites on and not miss my laptop
The touch buttons really piss me off though, I always press them accidentally.
I just discovered this issue recently and its very annoying to me. Seems to be a problem to the ground of the device so I feel it is a hardware problem. Just watched that video of the HTC Incredible doing the same thing and it seems to be what the case is. Girlfriend had to brag about saying "oh iPhone doesn't have that problem blah blah blah" and started using it on the same table.
Wow its like you guys read my mind. I was showing off the phone to my brother and it was laying on the kitchen table when it started having the same exact issues. Could it be a hardware problem? Im about 2 second away from returning this phone tomorrow. Too many little annoyances.
This guy has the same problem on his Samsung omnia 7 http://www.youtube.com/watch?v=o52nzpzg8Aw
Haven't forgotten about this thread. I have been checking the Samsung website everyday for my question; however, it has failed to show up. In the next 2 days I'll be contacting Samsung directly via telephone to discuss this issue.
M
olieebur said:
Girlfriend had to brag about saying "oh iPhone doesn't have that problem blah blah blah" and started using it on the same table.
Click to expand...
Click to collapse
It's got the opposite problem. It only works when you don't touch it.
My brothers Focus either A) just started doing this, or B) he just noticed it.
Hi all,
My trusty blackstone has begin letting me down and I don't know if flashing a new rom will help, or if it is something physical that is breaking / broken. I'm using the Stonehenge ROM with CHT and everything has been fine for months.
Recently the touch screen allignment just seems to 'wander' sometimes just a little, other times quite a lot (so much that using the fake hardware buttons at the bottom of the phone, brings up the start menu). This means that intermittently I cannot answer calls, and typing a message on the SIP is an absolute nightmare!
The start menu icons do not seem to be as affected as the home screen and CHT, and I can quite easily get to the phone settings and recalibrate the screen - this will help for a short while but the alignment drifts again.
Restarting the phone has a temporary positive effect but it doesn't last.
Anyone else experienced this?
I have exactly the same problem.
Dissembled the whole device, blown some hot air but didn't help. Seems it's a HW fault. But I have a doubt whether the problem is in digitizer or in control board.
It's definitely one of the more frustrating problems that I've ever had with the phone.
I might try flash a new ROM then give up if that doesn't work. At least I won't be tempted to disassemble as it has already been tried, tbh I'd have just tried the tin of compressed air too, I don't trust my soldering skills for tiny electronics.
It is getting progressively worse, the touch area of the screen has slipped so low now that I can't use half the screen.
Screen Alignment Fix
Have a look on this one, maybe this will help you...http://forum.xda-developers.com/showthread.php?t=538113
Hi guys, just bought a Galaxy Note - love the device except has anyone else noticed the touchscreen sensitivity is pretty bad?
I come from mostly HTC devices - the most recent being the Sensation and I could type much faster because the sensitivity of the screen seemed to register touches better.
I have downloaded SGS Touch which when the settings are adjusted are much better but, the settings always revert and I prefer a better or more permanent solution. Is it just my unit? Haven't flashed any custom rom yet so I can still return for warranty.
Would love to know everyone's thoughts and if it is a widespread problem, what did you guys do to fix it?
Are you referring to something like this?
http://forum.xda-developers.com/showthread.php?t=1330163
Please update if that fixed your problem.
Hi,
Thanks for the response. It is not related to the movement issue but more toward typing... if I type the same as I used to with HTC sensation, I find that I will miss characters out. I have to be more deliberate in the touching of the screen and that makes my typing about 30-40% slower than before.
It can be resolved with the sensitivity program but I find that it keeps reverting. I was wondeing if there was a more permanent solution..
Thanks
Same Problem Here
I'm having the same touch screen sensitivity issue. The touch screen on my new SGNote is much less sensitive than that of my Motorola Atrix 4G. I'm finding that I have to press MUCH harder in order to register making typing slower and typo's common and causing usability problems with some apps. Any help in a permanent fix would be greatly appreciated. I'll continue to research this issue and post any of my own findings.
Hey All-
I searched for this with the assumption that with all the N7 screen issues there would be others experiencing this but I was not able to find much of any help.
----
My N7 is registering touches without me making contact with the screen. It is always in the same location. When the keyboard is up, it is where the letter 'D' is located. If I pass my finger directly overhead, or often times, even near to, the 'D' button, the tablet registers it as a touch. I can make the tablet register a touch with my finger as far as 1/4'' away from the screen surface. As you may imagine, this makes typing near impossible. As I pass over the letter 'D' to access other letters, it registers 'D' everytime.
I have tried other keyboards and the problem persists. It isn't necessarily over the same letter (due to differing keyboard layouts) but it is always in the same location on the screen.
I popped the back cover off and tightened/loosened screws to no avail. Turning the screen off and then back on does not help as it seems to do with some of the other screen issues that others are experiencing. The one thing I have found to strangely help is pushing on the screen in the affected location with extremely firm pressure; in essence squishing the s*** out of it. When I do this, the screen will behave better (it will still ghost touch in the area but my finger must be very close to the screen) for a period of time before reverting to misbehavior.
--
Has anyone else experienced something of this sort? I am currently running stock/rooted/unlocked; It seems to be a hardware issue so I don't think another ROM will help though I will try the CM10 nightlies when they boot properly. I'm ready to just bring it back for a new one but I know the Wal-Mart I bought it at is out of stock.
Any help would be very much appreciated, thank you.
Im having the same issue mine is in random places, usually top left corner but when im texting it starts typing random letters, I've been looking
for a solution or someone with the same issue you are the first and only that i have found. I am also having the dead spot issues, they tend to alternate.
thunderinacircle said:
Hey All-
I searched for this with the assumption that with all the N7 screen issues there would be others experiencing this but I was not able to find much of any help.
----
My N7 is registering touches without me making contact with the screen. It is always in the same location. When the keyboard is up, it is where the letter 'D' is located. If I pass my finger directly overhead, or often times, even near to, the 'D' button, the tablet registers it as a touch. I can make the tablet register a touch with my finger as far as 1/4'' away from the screen surface. As you may imagine, this makes typing near impossible. As I pass over the letter 'D' to access other letters, it registers 'D' everytime.
I have tried other keyboards and the problem persists. It isn't necessarily over the same letter (due to differing keyboard layouts) but it is always in the same location on the screen.
I popped the back cover off and tightened/loosened screws to no avail. Turning the screen off and then back on does not help as it seems to do with some of the other screen issues that others are experiencing. The one thing I have found to strangely help is pushing on the screen in the affected location with extremely firm pressure; in essence squishing the s*** out of it. When I do this, the screen will behave better (it will still ghost touch in the area but my finger must be very close to the screen) for a period of time before reverting to misbehavior.
--
Has anyone else experienced something of this sort? I am currently running stock/rooted/unlocked; It seems to be a hardware issue so I don't think another ROM will help though I will try the CM10 nightlies when they boot properly. I'm ready to just bring it back for a new one but I know the Wal-Mart I bought it at is out of stock.
Any help would be very much appreciated, thank you.
Click to expand...
Click to collapse
Nexus 7 phantom taps
I'm having similar problems with my Nexus 7 bought in November. Worked fine for a while, now I'm getting phantom taps making typing a real pain and page scrolling can be frustrating when it suddenly scrolls to the top of the page! Anyone know if this is a warranty fix?
I had this happen one time. It freaked me out.
Sent from my LG-P999 using xda premium
OP and others - have you look at the video here - post #1254 - look familiar to you at all - http://forum.xda-developers.com/showthread.php?t=1770919&page=126
A # of us had been freaked out, wondering if our secured WPA2 network has been breached and remotely controlled ...
If your device is brand new, return it & get it exchanged, or get it fixed under warranty - it's hardware related. The 16GB WiFi only model that I got from local Staples store had that problem that got worst - the replacement & upgraded 32GB unit has been flawless thus far - running stock but rooted 4.1.2 rom. I was within the 14 days/holiday time frame for exchange/return w/o stocking fees, luckily & did not have to wait for it to be repaired under warranty.
Upgrading to 4.2 firmware and/or custom Rom & kernel do not help, YMMV - of course ...
BTW, local Staples tech support counter manager said up to 20% of the N7 are getting returned/exchanged for various issues. Wow !!
After 4.2.2 my nexus7 makes phanton clicks too
Similar with this video www.youtube.com/watch?v=Tkh3W_ITwEw
I turn off screen and turn on and stop... The times in times i get it
Have solution?
I had to take my screen protector off after the update it was pressing places on the screen didn't happen until 4.2.2 update
Sent from my Nexus 7 using xda premium