Develop Bugs

4th nexus same issue

As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
I have called about this issue. First time around Verizon said take it back get a new one. So I did that and so on happened 2 more times same issue same results. Now on my 4th one its starting again. So verizon said it was Samsung and Samsung said Verizon.
So I was hoping for some input on what direction I should go now.
Sent from my Galaxy Nexus using XDA

After so many replacements, I can only imagine that this is happening because of your location?
Sent from my GT-P7510 using xda premium

My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA

srh21 said:
My wife has the same phone and she has not had any of these issues. On the other had she doesn't use her phone as much as I do! I'm pretty much on mine all day and she maybe looks at it once a day.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.

srh21 said:
As of now I'm on my 4th Gnexus and once again I'm being plagued with the same issue I have since my first one back on launch day. Loss of voice during a call, high pitch noises, (think scratching on a chalk board) loss of sound on all key press as well as numbers when dialing.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
when you said high pitch noises, do you mean that during a call you can hear a buzzing sort of noise when people speak? I get that on my nexus too, it's slightly irritating but I'll live with it, better than spending time to unroot it, go back to stock and then waste a whole week in the service centre.

akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App

Powell730 said:
It's obviously not user error.. If you read a bit you'd see there is a very lengthy thread about this very issue.. It's called microphone cutting out during call or something like that.. You can replace your phone as much as you want, it's not going to change it. the cause is unknown but I believe they have at least determined it not to be hardware..
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
That is correct. Audio outbound gets garbled and then lost completely. This is the worst bug of this phone. I can't count how many phone calls where I'd have to hang up and redial because the other person couldn't hear me anymore.
Sent from my Galaxy Nexus using Tapatalk

I'd blame the carrier, as i'm on Orange UK, and I use T-Mobile UK as well, and call quality both ends, is excellent

Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.

akira02rex said:
This is an obvious case of user-error. The odds of getting a defunct phone that many times in a row is about like winning the lottery, literally.
Click to expand...
Click to collapse
Not sure how it could be user error as well. This isn't my first phone.

srh21 said:
Not sure how it could be user error as well. This isn't my first phone.
Click to expand...
Click to collapse
KWKSLVR said:
Your wife may not have the issue but are y'all talking on the same tower when the issue arises? I'm on Verizon as well and never had this problem. That said, I don't talk a lot, maybe 400 minutes a month - mostly to my boss that has an iPhone so half the time I can't hear crap anyway due to that fact.
I will say, as a recent T-Mobile transplant that has used Verizon off and on for several years with work phones, Verizon doesn't seem to have the same call quality in general terms. Maybe it's just my ear, but even back in the day I owned some Motorola claim shells that sounded pretty muddy.
Have you tried to replicate the problem on a completely stock phone with no 3rd party apps? I wonder if there's a conflict somewhere.
Click to expand...
Click to collapse
I pretty much tried everything. New sim cards, using it with nothing installed (stock) I'm super bummed I been waiting on a nexus device to hit Verizon for a while now. I'm not sure how much longer I'm going to put up with this.

What about rolling back onto 3G? Are you on the fringe of LTE connectivity at all?
I know a lot of people talk about call quality. Frankly, I haven't experienced any issues and no one has told me that it sounds like crap (and believe me, I have friends that would mention it, we're a HARSH bunch). I don't doubt they exist, and you certainly don't sound like 3/4ths of XDA that are overly dramatic whiners. Out of curiosity, roughly how many minutes a month do you talk? Any chance that it's just an issue where, well you know, the more you do something the more opportunity to experience something that goes wrong? I used to talk a ton for work, like 3000+ minutes a month. I had a lot more dropped calls then than now, know what I mean?
You know what I'd do, which Verizon would HATE but, hey, you are the customer. I'd take you and your wife's phone into Verizon, and have them flip the numbers around. Keep EVERYTHING else about the phones the same. Her apps stay, your apps stay, just swap the numbers around and try her phone with your regular use for maybe 3 or 4 days. If you can replicate the problem while she doesn't experience the issue at all on your phone, then you can probably narrow it down to either the tower your on, or maybe the phone really is just buggy after you've been on it for a while.
Every so often I'll have a long conversation and a call gets dropped, but I've never not been able to hear someone or them not be able to hear me. Like, they're the typical issues that you could assign to either being a tower pass off problem or the nature of LTE long before the phone (on either my end or the other person's end). But, like I said, that's a rare occurrence for me.

What version of ICS are you running? I had this same problem, specifically and most frequently the one where the audio cuts out of a call, sometimes it'd do it and force me to re-call my girlfriend as many as 3 or 4 times in an hour.
What fixed it was flashing ICS 4.0.4 released from Google themselves (if I waited for Verizon to do it I'd probably be single by now). This fixed it for me immediately right out of the gate. I've had the other issues you spoke of every so often but the audio cut out was constant. This fixed everything. Been running for a while without problems (month or so maybe?).

Eh...you didn't flash it straight from Google. At best, you flashed it straight from the Verizon/Google ota server the test ota is on

I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.

lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
From here?
http://android.clients.google.com/p....signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip

try a different SIM/Network. you'd be suprised

IINexusII said:
try a different SIM/Network. you'd be suprised
Click to expand...
Click to collapse
What network do you suppose he would try?

Sounds like the phone is doing you a favor. If I had to talk to my girlfriend for an hour a day I'd want my phone to kill itself.

lblacklol said:
I stand corrected, this is what I get when trying to post while on hold at work. Not straight from Google, leaked 4.0.4. Originally found it elsewhere linked to a google domain site, but it's best served up here.
http://forum.xda-developers.com/showthread.php?t=1481044
Give that a shot for now, fixed my woes anyway.
Click to expand...
Click to collapse
Did not fix the microphone going out issue for me :-( I just flashed the 4.0.4 leak on Tuesday hoping it would alleviate this problem, but I had the mic go out about 15 mins into a call last night. Same story as with stock, had to hang up and re-dial to continue the conversation.

Galaxy Nexus - flawed by bad NAND!!! \data partition corruption issue

Issue: \data partititon become corrupt for no obvious reason.
Manifests itself through: Freezes followed eventually by (endless) reboots
When: Randomly when you install new apps (may be every day as it can happen only every other week/month), or setting up apps (like Twitter, mail, etc)
Temporary solution: Re-flash Samsung FW but lose ALL YOUR DATA. Attention: CWM restore will not fix the problem!
---- Here goes a link to the fabulous mskip's tutorial, you will find here everything you need to get it back up temporarily
I experienced this in 401, 402, 403 and 404, some were expecting better data integrity in 404... I confirm this is not the case
I would not go as far as saying that this is 100% the reason, but it looks like the NAND quality is craaaaaap! There is no external SD card, Android should be able to do a perfect job now at handling info and preserving quality of data.
I will contact Samsung and ask for a refund (if at all possible)... Disgusting thing to put such a piece of s''t on the market without proper testing and call it "flagship/pure Google experience". This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Any advice, I am inetersted, have tried pretty much everything so far and did not solve the problem...
DO YOU HAVE THE SAME ISSUE? Let your voice heard...

DO YOU HAVE THE SAME ISSUE?
Click to expand...
Click to collapse
No. Could it be possible you're overreacting?

David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Agree as well ..seems more like rubbish
Sent from my Galaxy Nexus using xda premium

David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...

Umm, sounds like you need a replacement phone.
Deep breath....deep breath.

KWKSLVR said:
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
Click to expand...
Click to collapse
Right While i'm catching my breath, found another thread pointing to the same issue IMHO (didn't not see it initially):
http://forum.xda-developers.com/showthread.php?t=1490815
Attempting to contact Samsung already...

vulpy said:
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Click to expand...
Click to collapse
Your first post came across as a hysterical rant - this is the first I've heard of the problem so it's not affecting many phones, and ultimately Samsung are going to have the occasional dodgy NAND chip. Sounds like you got one.
If you'd had several phones and they'd all exhibited this problem you'd be right to be peeved, but it simply sounds like you've been unlucky and are pissed off about it. Have you even discussed it with Samsung's tech support or taken it back to the shop you bought it from?
And accusing an XDA recognised developer of trolling is not a great start to your time here.

I've not heard of other people having this problem with the Gnex? Who are these other people having this same problem? Maybe speak with them and see if a replacement phone might solve the problem. I really hope you can get this fixed and not give up on such a great platform.
Sent from my Galaxy Nexus using Tapatalk

vulpy said:
This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Click to expand...
Click to collapse
The burden of evidence is on you bro. That is a pretty bold claim.

David Horn said:
...And accusing an XDA recognized developer of trolling is not a great start to your time here.
Click to expand...
Click to collapse
Respect for your dev background (haven't used any of your ROMs yet), in all fairness I'm far less impressed with your communication skills... I must agree though, my message may have come across as too abrupt and you're right again, I am going to sort it out with Samsung...
Did not mean to get people horrified, rather to blow the whistle on a worrying and annoying bug and smth people may consider if they come across or consider a purchase.
For having worked in the mobile comm semiconductors space for years, I know just what sets apart a serious company from a me-too profile. Surprised to see Samsung having this king of issues. Normally they are ironed out easily though SW regression tests and HW stress processes (at least at serious OEMs).
I will let one of the moderators judge if my crime is so serious, your ego will survive, I'm sure I will come back when/if issue solved (or in good progress).

yeah, mine is fine. If it was a widespread problem I would back your corner, but I seems rather isolated. Rather then cause mass hysteria I would say you need to return your handset
Sent from my Galaxy Nexus using XDA

This happened to mine. But only once.
Quite frustrating, as my phone is my alarm clock and it was bootlooping when I needed to go to sleep!
However, a reflash of the 4.0.2 stock images sorted it out, and no problems since. I'm pretty sure I caused it by pulling out the battery at some sensitive point in a reboot or something.
If this happens to you frequently, then you need to exchange your phone.
Also, I think this could be a pretty good resource as opposed to a rant if you put your mind to it. I'm not a developer, but I'm also not a total n00b, and it took me a little while to figure out how to fix the problem, when I had it. I'm sure there are people out there who would appreciate a guide.

In this thread, op is going through that time of the month, when was his own modification back fires in his face, his explosive emotions reek havoc on an online forum.
If you want to see a device with bad nand memory, see the HTC Desire S forum .
Also the reboots and freezes I used to experience on my device were application related. Device hasn't frozen, nor rebooted in about *looks at up time* .. 27 days .

adrynalyne said:
The burden of evidence is on you bro. That is a pretty bold claim.
Click to expand...
Click to collapse
... I was actually referring to a poll in another thread (link in this thread) concluding that half of the people who answered have experienced freezes and reboots... it may be biased somewhat by the fact that people who experienced the issue are more likely to vote than those who didn't... maybe an overstatement from me.

Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk

First I heard about this too. I've flashed tons of roms and mods and constantly installing uninstalling apps.
The GNex has been anything but non-stable. I think I've had to pull the battery once or twice since ownership. Never heard anyone complain about randomly losing all their data... especially not daily. Perhaps on a bad flash in CWM.
Maybe you should look into a super wipe that completely erases everything, deletes the partition tables and recreates everything from scratch. Maybe it'll help but it honestly sounds defective.
Sent from my Galaxy Nexus using xda premium

Thanks Player911... Interesting idea, was thinking as well to do a total wipe and sort of a sector-by-sector reformat, but could not find a way of doing it. Is there any tool that would allow me to do it? Maybe this will isolate bad sectors...

Will check shortly with Samsung folks, thanks mate! (what slows me down is the fact that I'm currently travelling to the US and the guarantee is only European and it's Sunday= hotline is closed in Europe).
daern said:
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse

Uhh, I don't believe my reboots are due to this. Just saying. That whole thread does not point to your theory as the issue. I'm gonna go ahead and call this myth busted and suggest you go get a replacement because this is just another extremist "my phone is busted but I refuse to get a new one" thread.
Sent from my Galaxy Nexus using xda premium

You've been Samsunged
Sent from my Galaxy Nexus using xda premium

[Q] Nexus 7 owners...... problems, fixed or not?

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.

Touch "gets stuck" on letters while typing

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.

Common Issues with M8?

Hi I own a LG G2 and planning to upgrade. So I am researching into worthy upgrades and their common issues faced by people regularly.
So please mention the common and uncommon issues you faced while using this device or heard about.
Any other suggestions regarding my upgrade is also welcome.
Thanks

in_core said:
Hi I own a LG G2 and planning to upgrade. So I am researching into worthy upgrades and their common issues faced by people regularly.
So please mention the common and uncommon issues you faced while using this device or heard about.
Any other suggestions regarding my upgrade is also welcome.
Thanks
Click to expand...
Click to collapse
Common issue:
People that don't know what they're doing and are to lazy to read up messing up and soft bricking their devices.
Not so common issues but has been reported:
Lettering falling out on the back of the device
Camera showing some purple tint in low light
SIM cards not being picked up / read. Possibly not making proper contact
Some reports of camera lenses cracking
Have seen some people say that they have some dropped calls and/or SMSs not sending
Any other issues might possibly have been discussed in the Build Quality Concerns thread, might want to drop there and have a look at it.

BerndM14 said:
Common issue:
People that don't know what they're doing and are to lazy to read up messing up and soft bricking their devices.
Not so common issues but has been reported:
Lettering falling out on the back of the device
Camera showing some purple tint in low light
SIM cards not being picked up / read. Possibly not making proper contact
Some reports of camera lenses cracking
Have seen some people say that they have some dropped calls and/or SMSs not sending
Any other issues might possibly have been discussed in the Build Quality Concerns thread, might want to drop there and have a look at it.
Click to expand...
Click to collapse
Pink Tint again? Like the M7? Oh Boy :/
Why can't giant manufacturers like HTC and Sony get things perfect even for once :/

in_core said:
Pink Tint again? Like the M7? Oh Boy :/
Why can't giant manufacturers like HTC and Sony get things perfect even for once :/
Click to expand...
Click to collapse
Yeah like the M7 though I haven't seen a lot of reports of it and I haven't noticed a problem like that on my device either.
And yes, it would be nice to have things perfect if you take into consideration the price we pay for these devices. :good:

BerndM14 said:
Yeah like the M7 though I haven't seen a lot of reports of it and I haven't noticed a problem like that on my device either.
And yes, it would be nice to have things perfect if you take into consideration the price we pay for these devices. :good:
Click to expand...
Click to collapse
Exactly. Just about 10 months back I bought this G2 wi the same price the HTC One M8 is offered now in my country and after 7-8 months of usage suddenly i get this weird touch sensor issue and then after weeks it come to a point i cant even operate the phone properly and end up spending around $130 to change the whole display for it.
Thats the main reason I am changin this phone to get something which is reliable for a long period. Orelse i really loved my G2 and intended to keep it for atleast a Whole year more.

one common problem is the camera lens... even if you keep the phone in a case all the time, u are likely to get scratches on the lens, causing blur/soft pictures. but fret not! turns out its just some coating on it and can easily be removed with car polish or toothpaste.