Related
Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.
I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.
guidocioni said:
Hi there,
first of all i apologize for my poor english. Got my Galaxy Nexus for a week and i'm not very excited about ICS. I expected great battery life and a few bugs but i've seen a lot. There's an annoying one : sometime my phone seem to live without my touch. If i'm with keyboard on it starts to type messages like "dajhfhakjerehk" then it go on the home and start open apps randomly without my touch. Seems like the volume bug but different; anyone experiencing this issue ?
I hope that's only software, otherwise i had to bring the phone back to the seller very soon.. I wish that 4.0.3 will be released soon so i can decide if it's software or hardware problem.
Thank you all in advance.
Click to expand...
Click to collapse
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Snoemannen said:
I have the same problem with mine, it doesn't happen often though and I can't reproduce it on queue but I have had my phone for 3 weeks now and it has happened happened several times so it's not just a one time thing.
Click to expand...
Click to collapse
So i'm not the only one.. I can't reproduce me as well : sometime not happen for 2 days , sometine twice a day..
djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
If it was the digitiser i think that it would stop always, not randomly every 2 o 3 day.. That's my opinion
djmcnz said:
If you're running stock software and this happens frequently I think you should return your device for a new one - sounds like a faulty digitiser to me...
Click to expand...
Click to collapse
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.
Snoemannen said:
It only happens every other day or even more rarely and it just for a short period so I'm not sure what is doing it.
I also have the more common multi-touch bug after using some 3D games like Heavy Gunner so I'm more inclined to believe that it is something that triggers it similar to that than for the digitizer to be faulty, but that might just be me trying to convince myself that it will be fixed since I don't want to go through the hassle to replace the phone.
Hopefully google will release the next update again soon, be it 4.0.2 again or .3 or whatever, I'm still on ad yakjuxw with 4.0.1 so I was going to wait untill I get the update before I take any action.
Click to expand...
Click to collapse
me too , let's wait
It's all about the 4.0.1. I had that issue before, now it works fine with 4.0.2. Just update and that problem will disappear.
Sent from my Galaxy Nexus using xda premium
I have the exact same problem, and I must say I am so relieved to see it's just a software bug! Thanks, Rilazi
sorry for bumping this thread but the issue it's very annoying.. I can't even use my phone, it start doing things himself!! How can i do ?
Hi all,
I got my One X a few weeks ago, very soon after launch (O2). Initially I was very happy with my purchase but now I'm left extremely frustrated with this handset and regretting buying it - screen flicker, dropped calls, lots of little bugs, and now... The camera won't work!
I've been using it quite a bit since I bought it, but yesterday I was using it (no settings changed) and each time I took a picture there was either corruption in the image or a blank image with an exclamation mark icon instead of the picture. This now seems to happen almost every time I try to take a shot - I've done the following in an attempt to rectify:
1. Reboot handset
2. Ensured no other apps are running prior to using camera
3. Reset camera settings to default
4. Ensured phone was fully charged
5. Ensured I have enough free storage space (~22GB free)
I'm not going to perform a factory reset because I'm not convinced it's going to help anything AND I shouldn't really have to do that! I haven't got time to completely reconfigure my phone.
Still, I'm unable to take a photo and this is *really* annoying me! A premium handset with issues all over the place... Unacceptable!
Now I'm left thinking I'm going to go back to O2 and demand replacement with a SGS3, because by the looks of things HTC haven't actually fixed most of the bugs we're all experiencing.
Such a shame - had so much potential and a genuinely amazing device to pick up and use in many ways, but it's quite frankly not fit for purpose if I can't make reliable calls, take pictures or use the screen without serious flickering.
Has anyone else experienced these camera issues I described above?
Apologies for the tl;dr, just a very frustrated HOX owner.
So because you got a faulty phone all the others out there are not fit for purpose?
OK got ya that seems fair
There's something wrong with your particular phone, just get it replaced. The vast majority of people have no flaws whatsoever.
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
nikorette said:
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
adamsharif said:
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
Click to expand...
Click to collapse
Yes really. It'd be incredibly foolish to assume that XDA users are representative of the majority of phone users and even more foolish to assume that people who have flawless phones will be just as vociferous as those with flawed phones.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
Why don't you try and reflash your phone with a RUU or return it for replacement?
Well that's what I've done - just booked it in with O2 so will see what happens.
Still interested to know whether anyone has had this camera issue though?
adamsharif said:
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
nikorette said:
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Lol you still don't get it. Some people just do not know about forums. Unless you get a number from HTC that states how many returns per device made. Nobody, not you or me will know. Not reading anything other than what's on my screen. I'm defensive, by logic you're aggressive.
I guess you won't. Everyone else just ran a factory reset instead of crying about it.
Anyway like most of the threads on here its no longer about the op's post and more about the ego of the people posting. I'll admit I am at fault sorry if I derailed your thread..
Sent from my HTC One X using Tapatalk 2
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Adamsharif;
You do seem to have a phone that, under UK law does not appear to be fit for the purpose for which it is intended, regardless of the warranty obligations of HTC.
In reality, you should back everything up and factory reset the phone, if only to rule out any problems which could be solved, by doing this. If then, the phone does not work, you are well within your rights to demand a refund or a replacement.
If you're not willing to do a simple reset to fix potential issue, HTC and the users here are definitely not going to be willing to help you out. We can't reset the phone for you, but you still want to fix it by using and looking at the phone until it behaves itself.
adamsharif said:
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Click to expand...
Click to collapse
Here you go, proof that the majority of XDA members have no issues whatsoever with their device.
http://forum.xda-developers.com/showthread.php?t=1585082
Of course, people with no problems don't post much on forums, so the actual, real-world results of such a poll would be MUCH more one-sided.
As for your camera problem, many people have suggested fixes; Factory Reset, re-flashing RUU and, if all else fails, return the device and get a refund/replacement.
People seem to think their £500 device is going to be perfect. Don't get me wrong, It SHOULD be perfect, but no device is ever going to be. The HTC One X issues are also relatively minor compared to some devices that came before it.
kannanX10 said:
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Exactly. There's an old thread about this issue. Fixed with 1.28
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok, I guess I shouldn't have been so stubborn - currently backing up the device and will do a factory reset.
The backlight issue, however, is the one I'm returning for - the thing I find strange about both that and the camera issue is that they suddenly appear which really makes me feel that there are hardware issues in the first batch.
Lesson learned - don't buy a handset as soon as it comes out!
Personally I feel that mobile manufacturers need to undertake better testing and not rush their products to market - if you look at many of the recent handsets from Apple, Samsung, HTC there have been a lot of silly issues which have damaged reputations.
If I can have a HOX with working camera, backlight and calling it will be the perfect device!
You don't want to change your phone and yet you can't live with the problems. What do you want? Just ranting? Got it.
Sent from my HTC One X using XDA
ALL THE CORRUPTION ISSUES EXCEPT FLICKER are solved by firmware 1.29
My new hox was updated to 1.29 two days after I bought it, I never encountered the said issues, also flicker is related to overheat on 1.29 the phone temperature is a lot better
you regret buying the most praised and critically acclaimed android phone lol
I think we're being a little harsh on adamsharif, I love my HOX but its not without it's flaws and some of the 1.26 bugs were just messy...the phone shouldn't have been released with this firmware...it was rushed but I can understand why with the SG3 looming!
Unfortunately the average user turns to a forum when he / she has issues, the average user doesn't sign up to XDA to just say how happy they are, some do, just not your average joe, so it all looks like doom & gloom!
£500 is a lot of money, should we have to factory reset it after a few days / weeks? Should we not expect a near perfect product considering the money spent....I don't know....android isnt a perfect OS so I think the arsehole answer is get an iPhone!? I think in 3 months time we'll all be happier and mostly problem free!
Sent from my HTC One X using XDA
Guys please stop the pointless comments.
Back on topic. I suggest you try a third party camera app from market and see if that works. If it works, i too believe that hard reset will solve the problem. Also, don't underestimate hard reset. It usually solves most unknown issues
Guys, I was all set to get a new 32gb Nexus 7....the reviews are great, and then I start reading about the issues.
After a bit more reading, I'm left wondering if its such a good idea? I read that Google released an update, then I also read that it didn't always fix things for people?
So the questions I guess are, Do you own one? Have you had a problem? Is it now fixed by the update? Maybe you've never had any problems?
Would you recommend getting one? I don't wanna spend out on something that I'll regret.
Thanks guys.
I've had mine since the first weekend of availability and it's lived up to all my expectations and then some, you're just buying the usual support vocal minority, sume have legit issue, noisy are just being nitpicky
Sent from my HTC One using Tapatalk 4
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Thanks for your reply.
Mine worked 100% out of the box, no light bleed, no multi-touch issues, no GPS issues. Updates have installed perfectly. I am running stock deodexed + root + TWRP + Elemental X 1.1 Kernel. Couldn't be happier with my purchase. :good:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
madpete said:
Thanks, this is what I'm trying to determine...if its just a few people shouting loud, or a big issue affecting a lot.
Click to expand...
Click to collapse
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
I bought the 32gb. Works flawlessly, I got it a week and half ago.
Sent from my Nexus 7 using xda app-developers app
GET ONE
I would say go for it, you are always going to have issues with most anything. Just buy from a retailer with a good return policy, I own the nexus 7 2012 and the nexus 7 2013 , no issues here, awesome devices.
Thanks guys. Sfhub, you make some good points....think I will buy from a large high street store, rather than online.
Sent from my GT-N7100 using XDA Premium 4 mobile app
sfhub said:
My suggestion is you buy from a place with a reasonable return policy.
We have no idea whether this is a 1%, 5%, 10% or more problem. Even if it were a 20% problem you would still have a huge number of people without issues, but from a product standpoint it would be very bad.
In my personal experience GPS is completely fixed on multiple units with the JSS15Q firmware.
Multi-touch is hit or miss, many units either got multi-touch fixed or saw no improvement. Some saw things get worse. You can see from the changelog history of the touchscreen firmware that they have been making various changes to address the issues, so the issues are real and acknowledged in some part.
Changelog for touchscreen firmware is available here:
http://forum.xda-developers.com/showthread.php?p=44954563#post44954563
As to the random reboots, IMO there are 2 issues, one is a hardware issue and the other is one or more software issues. The hardware issue is more rare, but if you have it, it will be difficult to avoid the reboots, unless Google/Asus can find a software workaround for the problem.
With respect to the software reboot issues, you can usually avoid them by avoiding a "trigger" app. Some folks usage just never triggers the problem. Some people trigger it when using chrome. For others it is some other app. Usually when you stop using the trigger app the software reboots go away.
You need to make the decision for yourself. There will be lots of people saying no problem and lots of people saying they got multiple units all with issues.
Click to expand...
Click to collapse
i think mine is definitely, hardware, maybe , cuz of user error, ie, bad dirty flashing of zips, i dont' want to start all over fresh again, too many apps/settings to revert back (yes call me lazy sob)
most of the reboots happen when im clicking on an app with wifi on , but one of my last reboots, it just just rebooted out of the blue, i didn't even touch the tablet, but i seen it reboot!
Not sure, really, whether I have/had problems or not. Got mine over the weekend. During my initial playing, I did not notice any touch issues. The GPS would lock, but I didn't have time to take it anywhere for long enough to be sure if it would stay locked for a long period of time. Almost immediately (1 day) I got the JSS15Q OTA update. The GPS DOES seem to lock a bit faster, and I seem to be seeing more satellites than before -- it could be my imagination, though. Still no touch issues that I can see.
New Nexus 7 (then) past issues, (now), Cool TAB!
phab3k said:
I know a lot of people have reported the GPS issues and the touch issues, but I've never experienced them myself. I bought mine the day it was released, 32gb model.
Click to expand...
Click to collapse
I HAD issues out of the box. Waited for the first update from Google, rebooted once after. Took forever to get the screen to respond to any kind of tap. Rebooted a couple of times and was able to get somewhat R E A S O N A B L E response out of the screen. GPS would work for all of 2 minutes and then shut down. No problems with Wi-Fi.
That was then, along came update: JSS15Q! All is happy in Nexus land. GPS is strong and works flawlessly even in the darkest center of my house! Screen is responsive my fingers are happy.
APPS? That is another matter, remember, even with a stock Nexus 7 fhd you are on the bleeding edge meaning that many apps found on Google Play may fail. Live with it until either the app is updated, ***** at the (no don't *****, contact the developer and kindly tell him/her your problem; or find another app that works for now.
Games? Heh, that is a real crapshoot. If it won't function, move on.
This is one hell of a tablet with excellent video, good sound, fast processing. Short of it not being the size of my 60" monitor (TV) I can read everything with these 78 year old eyes!
[email protected]@dog!
Google Nexus 7FHD
Kindle Fire Rooted Android 4.3
Kindle Fire HD 8.9 Rooted 2nd boot loader Android 4.2.2
Droid Bionic stock Android 4.1.2
Guys, just wanted to say thanks for all the posts. You help me make up my mind, and gave some sound advice.
I've took the plunge and brought the 32gb model (from a big high street retailer), and I have to say....what a cracking little tablet this thing is, I am really impressed with it. I have not had any issues with it, so I seem to be one of the lucky ones....either that or they have fixed the issues by the time we got them in the UK.
I do feel for all the people who had problems though, its a nightmare when these thing happen. Theres no doubt there has been or are some issues out there, one thing with a Nexus device I guess is it is patched fast if its sw...obviously hw is a different issue.
Looking forward to enjoying this device now, if I can get on it....have to wrestle it off the wife and kids first!
......thanks again guys.
Pete.
Just got my 32gb Nexus today in the UK. Only thing I have noticed is that tap and hold on screen is slow to react. Can take a couple of trys before it works. Sometimes taping an app is slow to open. Running stock and latest update. Only change made is to use Nova as the launcher.
Sent from my HTC One S using Tapatalk 4
To Wugfresh Re: Toolkit
This is a followup to my 2 confusing Twitter's I made it worse by referencing Nexus 4 and 7 so I will stick to 7 (mostly). I now realize that lurking has its penalties since I need 9 posts after this before I can post this in the relevant thread (with a nostalgic tear for the days we welcomed all comers and left our doors unlocked).
I bought an N7 FHD (2nd gen) and rooted it after the 4.3 auto update soft bricked (right term of art?) it. I used the other toolkit to restore it to JDQ39 factory unrooted. Then it installed JSS15J. Today it tried to do an update and (presumably) it failed because of rooting. That build is no longer on the developer's website and has been replaced by JSS15Q. I would never presume to call myself a developer but my first modem was a 300 baud acoustic coupler and I have a 5 1/2" floppy disks older then most of you and it's actually floppy. ROFL.
Back to reality, on the Nexus 4, I could not discern how to upgrade to the latest Y build but I did manage to restore it to factory settings and Google handled the rest, You were kind enough to add JSS15J to your toolkit for the Nexus 4 but it is not available (in your drop-down) for the Nexus 7. I figured that if you made JSS15J available for the N7 I could restore the N7 to a factory fresh un-rooted one and Google could update it to JSS15Q. In the alternative you might guide me to how I could go from JSS15J to JSS15Q. I am certainly not in your league but this is not my first rodeo and I cannot tell you how grateful I am for your efforts. Your toolkit saved my Nexus 4 from the 2 week wait during which Google might have told me rooting voids the warranty or just have left me phone-less till they returned it.
Again thank you especially, and to all the others here who light candles in the darkness for each other and the rest of us pilgrims. A tip of my fedora to ya. Never forget one definition of a pioneer is someone with an arrow in their back.
Much of the time I am as confused as a baby in a topless bar who said, "What do you mean this is not a lunchroom, what else could it be?"
My suggestion is to keep root, grab the latest carbon ROM, the elemental 1.1 kernel and you should be all set. They already have the updates From G in them and they work superb.
Sent from my Nexus 7 using Tapatalk 4
Do you own one?
Yes, from day one.
Have you had a problem?
Yes, GPS and the touchscreen grounding issue.
Is it now fixed by the update?
Yes, GPS seems fixed.
No, grounding issue may be worse. Works fins as long as I'm holding it. Placing it causes touches to become sporadic.
Maybe you've never had any problems?
I wish...
Would you recommend getting one?
Yes, it still a FANTASTIC device and many have no issues. If you do return it right away until you get one without issues.
I spoke too soon....at first I thought everything was ok....then I began to notice when I was typing that sometimes it would come out as gibberish. I thought nothing of it as we all make typos now and then, then I noticed that press and hold didn't always register (sometimes takes a few goes). I downloaded the multi-touch test from play and to my horror it's all over the place (compared it against my note 2), this is with the latest update. After reading around a bit more, I'm beginning to think these touch screen issues are hardware....and that it's more widespread than people think. Will be exchanging it for another one, hopefully fair better second time.
Sent from my GT-N7100 using XDA Premium 4 mobile app
madpete said:
Will be exchanging it for another one, hopefully fair better second time.
Click to expand...
Click to collapse
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
sfhub said:
Before you return, perhaps you could try this thread:
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Hey man, thanks for the reply.
I opted for the swap out because I don't want to loose the warranty, which I believe you would if you unlocked it?
I bought from PC World / Currys so the swap was no hassle.
Using the new one now, its testing better and typing and "hold and drag" is working much better (although hold and drag still isn't 100%, it's now acceptable to me).
I tested before and after the update, the observation I made is that the update seems to dull down the touch screen a little. It became slightly less responsive after the update than before, but hasn't really affected the usability on this one....although I think I prefered it pre update.
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.
Hi all,
I have recently been noticing ghost scrolls, where I would be slowly scrolling downwards, say, in the XDA app or reddit app, and randomly it would scroll quickly upwards when I lift my fingers. I was thinking this was a hardware issue so I got a replacement device on the way. However, I saw this https://www.reddit.com/r/GooglePixel/comments/7rczu2/scrolling_up_when_scrolling_down/.
Has anyone else been experiencing the same thing? I posted a vid and pic https://imgur.com/a/ny8fT. The second pic is touch input trace enabled in developer options, you can see there was a ghost long fast drag down to the bottom below the navbar.
Have been away from XDA for a while, please let me know if I am going against any rules about posting images hosted on other sites.
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
I wonder if something like this is what causes Twitter to randomly show me a different tweet when I tap on one. (maybe it's doing a phantom scroll briefly).
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
yep, thats happened to me a few times before as well. Not twitter specifically, but in reddit I would click on a post, and somehow I would end up on some random other post like 2 post below it, and if I hit back once, I get to the post I originally intended to click on instead of the subreddit list.
So there must be some sort of ghost touches/scrolls on finger release, causing the unintended post to be queued up just before the intended one.
I'm surprised there hasn't been more people bringing up this issue (assuming this is indeed a software 8.1 issue and not an isolated issue in the touch panel).
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Devhux said:
Reddit has done that to me too, come to think of it.
Agreed that it's surprising we aren't hearing more of this. Makes me wonder if I should do a warranty swap.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
elliwigy said:
definitely doesnt sound like a hardware issue.. ive experienced this on more devices than the p2xl and more so on stock.. u also might get it when ur data lags..
on the available custom roms i cant say i remember the last time it occurred.. either way, it cant be that bad to even remotely consider replacing it
Click to expand...
Click to collapse
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
ethantarheels123 said:
Oh really? Have you only experienced this on 8.1 only, or also 8.0? I had the pixel 2 xl back in October/November on 8.0 and didn't experience any of this. I just repurchased the 2 xl several days ago and immediately noticed it within the first few hours of playing around with it.
I think it definitely is a software bug, if not a hardware issue. The touch input trace shows a ghost drag of a perfectly straight line to the bottom of the touch panel with an incredibly high Yv, I got one as high as 179. Normal hard flick scrolling would top out at around 30 or 40, so definitely something fishy going on here, whether it's software or hardware.
It happens for me like between 5 and 10 times within half an hour to an hour, and they are usually annoying enough where I lose my place where I was scrolling.
Click to expand...
Click to collapse
prolly 8.1.. i got mine around december late nov. pretty sure its software related.. they had an issue with touch on the lockscreen right?
It seems like so many touch issues with 8.1 release. For this reason, I am still using 8.0.
https://productforums.google.com/forum/#!msg/phone-by-google/FfzV1578L8Q/1HcWw3CCAQAJ
https://issuetracker.google.com/issues/70344455
ethantarheels123 said:
Yea, I have a replacement device on the way, but after hearing a few others experiencing the same issue, I'm starting to think it might not be a hardware issue after all.
Click to expand...
Click to collapse
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
ayoraider07 said:
Any update with the replacement device? I am having the same sporadic ghost scroll: I'll be scrolling down a page on reddit or slickdeals app (happens with other apps as well), and randomly it'll perform a strong up-scroll... I notice it more often when I lay in bed on my side, and have the screen orientation locked to portrait, resting the phone on the bed horizontally...
Click to expand...
Click to collapse
Replacement device has the same issue, so this is definitely a software bug. Hopefully Google fixes it soon in the next patch update.
Nexus 6P here. I started getting these ghost touches with the last security update. 8.1 is the problem, not a solution.
My mom has the same issue of touch on places she doesn't touch, on Pixel XL.
Could it be the same?
Here is a video about it that I took, just by scrolling in the settings screen:
https://drive.google.com/file/d/1JCsTuMDvMNHh0CO7sF7yoLFT26uNIhUp/
It's a bit hard to reproduce, but it occurs eventually.
Has anyone tried to use Android P, and see if it helps?
Anyway, I've reported about this here too:
https://forum.xda-developers.com/pi...h-pixel-xl-t3807188/post76879468#post76879468
Any fixes yet?
I know this is old, but I wanted to know if anyone found a fix for this. I eventually found an Oreo 8.1 Rom that I like and this is the only issue that's bothering me.