Related
Background
This is by no means definitive, so don't everyone go get your panties in a wad and pitch fits like 12 year olds.
So several days ago I noticed that my GNex was starting to have issues with dropping calls and data connections. Basically, I was dropping data and voice despite having a connection to the network about every 2-5 hours, requiring a reboot. This happened over a 3 day period in a stationary position, in radically different places (like 80-150 miles apart). It was happening on 3G and on 4G so I was pretty confident that it wasn't just a localized outage or the local tower acting up. I'm no expert and certainly no /dev, but I've been around some Android devices a time or two.
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else. As an example, shortly after getting my GNex I installed TweetDeck. I had used Navigation several times to test GPS (first thing I did being a SGS owner) so I knew it worked and worked well. Anyway, immediately after installing and setting up TweetDeck, my GPS crapped. It would see satellites but not connect... even after 30 minutes....even after rebooting, clearing AGPS data, blah blah. Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Solution (For me at least)
With that event in mind, and a crapped out radio, I went looking through my app drawer for apps that access the radio. I picked out Network Info II 0.6.0, Real Signal 3.5 and Network Signal Info 1.51. I rebooted and waited. Here it is three days later, and I have yet to have a single voice or data drop. If I've had one on the data side, I haven't noticed and it certainly wasn't for long.
I don't know how or why. All I know is that I've never had any form of radio trouble and those apps were recently installed, and that without them, the radio issues are gone. Take it for what it's worth, which probably isn't much. But if you're on 4.0.4, with 4.0.4 radios and you're suffering from radio problems, flip through your app drawer and remove or freeze applications that have the sole purpose of polling data from your radios. Who knows, maybe having 3 was 1 or 2 to many.
Thanks for the write up. And I really think the issue with certain apps interfering with OS-level stuff is a big issue, and one that nobody seems to want to notice.
There are a ton of posts, not only on this forum but on others, where people are saying they have so many issues with the Nexus and this and that. What a lot of people don't realize is that, yes, certain apps that are either poorly coded in general or not coded for ICS can potentially interfere with the normal operations of your phone.
A lot of people tend to use/stick with apps that they are used to, right? I came from the G1, the very first Android phone, so I've been using Android for awhile, and I bet that other people are too. Some apps are a staple of people's usage, meaning as soon as they get a new device, those same apps are the first to be downloaded and installed. However a lot of times those apps are abandoned by their developers, never to be touched again.
So of course an app that was coded on Froyo or even Eclair that calls the GPS or the radio or bluetooth stack or something else hardware related can potentially cause issues, especially with ICS being such a radical change from Gingerbread.
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
[email protected] said:
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
Click to expand...
Click to collapse
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Food for thought: Apps have not been updated to work 100% with ICS?
KWKSLVR said:
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Click to expand...
Click to collapse
Alright, so will that app tell me what is accessing that feature or do I need to go through every app to find out and what exactly shoould t say in the access?
Help me out here please because this is starting to annoy me!
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
bk201doesntexist said:
Food for thought: Apps have not been updated to work 100% with ICS?
Click to expand...
Click to collapse
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
I've thankfully been free of radio issues thus far on my GNex, but I want to thank you for this thread.
KWKSLVR said:
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else.
...
Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Click to expand...
Click to collapse
KWKSLVR said:
I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation.
Click to expand...
Click to collapse
Not to jump up on too high of a soapbox, but I couldn't agree with you more.
It's very satisfying to read about people methodically, empirically testing. It's something that seems rare these days.
So thank you!
KWKSLVR said:
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
Click to expand...
Click to collapse
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
[email protected] said:
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
Click to expand...
Click to collapse
When I froze those apps, I picked them because I knew they had access to:
Network communication > view network state > Allows an application to view the state of all networks. The part in bold is the description of what the permission "View Network State" means. That permission is under the "Network Communication" Category. Some apps will have more than that single permission under Network communication, some with have none at all. "Real Signal" has the fewest permissions out of the three I froze, and maybe all three don't HAVE to be frozen, but I haven't tested that yet.
Another random thought. During that time period, I also had a BUNCH of random reboots.
Maybe on other devices 95% user error might be closer.
But, not on my Gnex! What if you bought a completely new phone and have not installed any apps. The first time you open up the stock browser and use it for 5 mins or so on 4G LTE next to the cell tower -75 db stationary and still lose connection of both data and voice with "the triangle of death" on 2 separate GNex with 2 new SIM cards? Is this a bad batch? To me, "bad batch" is when we say 1/100 is a faulty device but this is almost reversed with GNex. We should exchange devices until we find a "good batch"
All I am saying is we all should be a little more compassionate for people like me. A lot of problems are made by users, sure. But it sure isn't 95%....It's more like samsung/google/vzw 60% in this case..
I hope I shed a little light on all the users that did not create user errors yet still have radio problems and VZW keep telling us to wait because issues are going to be addressed with the supposed firmware update that should have come in Feb, now March. Now...I don't know when.
Thank you for your post though, you rock
With anything, even product reviews, the people that have issues always make up the vocal majority. No one talks about how things work the way they should.
If my phone truly dropped 4G as often as it did when I had this application conflict, I'd be in the Verizon store every day until I either had a replacement or got banished from the store. If Verizon told me that it was "normal" and to live with it, I'd pay a visit to management at a different Verizon store and pay an online visit to the BBB. If that didn't do any good and I was really REALLY bored and had nothing better to do, I'd probably draw up a letter to Verizon's legal department about the liability Verizon could have when a consumer can't call 911 in the middle of the night because the radio crashed.
I still think it's an incompatibility hiccup with ICS more than necessarily an issue with Verizon's LTE network. I see GSM owners complaining too. And, as I said in the OP, I can only speak for a "stock" 4.0.4 bootloader/modem/radio experience. I've seen posts from people talking about how their problems have disappeared since making the move from 4.0.2 to 4.0.4. All I can speak of from my own experiences is that I've never had a problem from any version of ICS other than what I experience.
Come to think of it, I think I'll defrost all three of those apps and see what happens, especially since the phone in my hotel seems to be in working order.
OK, in the couple of hours since I've defrosted my cocktail of apps I've:
Opened the Facebook app, watched it poll for GPS and lock, then closed the Facebook app only to have GPS stuck on. Once I went into Settings > Apps > Location Services and tried to uncheck "GPS satellites" it rebooted. After rebooting, the phone showed 4G and a connection to Google's servers but I couldn't browse or use any app that is web based (like speed test, gmail, etc). After about 30 minutes of trying, I rebooted again and everything was fine. I have a feeling it's related to Real Signal looking at the plethora of stuff it monitors and that it's starting up on boot.
That's all I personally care to see. Needless to say, they're all frozen again.
I don't think there is a problem with real signal, I only installed it after having these problems to start with.
Since I got my nexus it works randomly drop voice and data. People would call me and get a fast busy signal. I tried many different radios and they all behaved the same. I switch my network to CDMA only and haven't dropped data or voice in two days.
Sent from my Galaxy Nexus using xda premium
On 4.0.4?
I don't think it's necessarily just Real Signal. I think it's multiple apps polling data from your radios. After a few more days, I'll go through them one by one. So far in my experiences on my setup, there is something up with the combination of those apps.
Again, there's a solid chance that a combination of other apps could give other people similar issues.
I will say this, even if I had problems before installing those apps, this particular cocktail would only make them worse.
It's not ICM
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Woodk1 said:
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Click to expand...
Click to collapse
Yes, indeed.
I am very surprised to not see one yet!
It means all of us with this issue is actually being very patient at the moment.
Again, for anyone who does not have this issue at all, and curious to find out what issue we all are actually describing here by LTE Connection Drop + Voice Drop is:
http://code.google.com/p/android/issues/detail?id=24345
Man, why does everyone always pull the "class action lawsuit" line?
Firstly, you're not going to do diddly squat legally about it, so stop kidding yourselves (and us) when you say that you are.
Secondly, no service you pay for is "guaranteed" to have 100 percent uptime. My Comcast internet connection goes out every 3 months or so anywhere from 5 hours to one day. Do you think I have legal grounds to sue them? Nope. When a thunderstorm rolls in and you lose power for 12 hours, can you sue your electric company? Nope. In fact, I'm pretty sure in most ToS contracts or forms that you sign, it states that they do not guarantee you anything.
LTE is a relatively new technology, and Verizon is the first one to offer it. There's going to be hiccups and growing pains. It's been a year and it's A LOT better now than it was back when it started. 4 years ago we were all happy to get something faster than EDGE speeds, and now we get connections capable of 40/50 Mbps down at times and people are still unhappy.
I understand people's frustrations with the network/switching issues that are occurring between CDMA and LTE. But we live in an age where everyone feels entitled and important enough to immediately sue another company at the drop of a hat.
Here's an idea: If you are faced with severe LTE switching issues and it's a continuing problem, call up customer support. Tell them what is going on and let them help you. Yes, you are past your 14 day return policy, but you have one year of a device warranty, they will ship you out a replacement device. Since your Nexus works fine and your wife's does not, it leads me to believe that it's not a network issue in your area, and either: A. Your wife got two dud Nexus' in a row, which sucks but is not unheard of. or B. Your wife is using some sort of app or service that interferes with the radios. If you still have the issue after the 3rd replacement, call them up again and explain, and they just might be able to give her a different device altogether if the Nexus isn't working out for her.
Dear MMcCraryNJ,
hear my long plea if you have the time. If you don't that is okay.
Firstly, I am so glad you seem to be not affected by this issue on your GNex.
Every single day, I wish I was in your shoes.
On the brighter side though, with LTE Data/voice drop & severe vertical banded screen & one-way-microphone outbound issues, I have come to join in XDA forum. I've also gotten to know countless VZW / Samsung customer service representatives at all levels as well as local store customer service agents.
Secondly, I, and I am sure most of all the other GNex users with above issues, know that no product & service is guaranteed to work perfectly with 100% uptime. Personally, it takes a significant defect of any product for me to call customer service at all. I am one of those, who actually try to live with products that have minor flaws everyday. If GNex did drop my LTE 3-4 times daily, I'll live with out much complaint let alone 3 months that you've mentioned. 3 months of uptime would be heavenly, but I'll actually be perfectly fine with 3 hours uptime. Sadly, my uptime has been 5-10 minutes with LTE. If my one-way-outbound microphone cut off issue happened 1 out of 10 calls, I'll live happily. Sadly, nearly every other call makes my voice into a robot and I have to call back again.
I am personally coming from Droid Eris long long time ago when Android first came out with newest 3G technology back then. Eris wasn't issue free but my satisfaction with what I got was pretty much 95%. You see, as long as a product performs what it claimed to perform 60-80% of the time, I am happy. Claim and advertisement that Verizon made with CDMA Galaxy Nexus in the US as "The latest 4G LTE Pure Google ICS Smartphone meeting the most reliable 4G LTE network in the world" caught my attention, as many others, to actually decide to choose this new phone with my 2 year contract over countless androids that came out in the past 3 years.
Again, our frustration that is described on these post is described in detail here (http://code.google.com/p/android/issues/detail?id=24345) it is not a LTE / 3G switch issue only. Switching issue is very small part of this problem. I will not go into any detail of one-way-microphone cut off issue at all, due to its unrelated nature on this particular post.
Just as you've suggested naively, your suggestions in order that you wrote them in were exactly the steps I thought and took from very first day I purchased GNex back 4 months ago from a local verizon store. I have stopped in at the verizon store to get exchanges of the actual device, SIM card. None of these replacements solved the data/voice drop issue. I am all talking about stock 4.0.2 without any apps installed on any of these GNex. It can't possibly be the bad batch as I received batches that were produced in completely different months. I loved whatever was promised with GNex so much that I was determined to find the one for me as no other devices Verizon offer at the time appeal to me at all. As 14 days has passed, the local verizon literally told me to 1) wait for the update 2) root your device to all different kind of ROMs and Radios 3) call VZW customer service. Which all of the advice I followed, I am still waiting, none of the ROMs and radios solved the issue.
Ever since then, I've been calling VZW and Samsung (when VZW transferred me), and talked to numerous customer service representatives at all different levels. (Level 2 & 3 and at some points I've been transferred and escalated twice to a person really higher up) With my efforts, I was actually able to tag all my calls, and send them screenshots (via e-mail), and follow through to actually make above mentioned issues officially put on VZW technical bulletin. It is a huge improvement, because when I first called about these issues, they told me "They've never heard of these issues.". Now, after all of our efforts, they admit there's over "120 technical bulletin reportings on these issues."
You do think that it is so easy to get a refurbished factory replacement phones with all my history right?
The answer is sadly No. They've been literally telling me to wait a little longer no matter how much I requested them to get me a replacement device. They are indeed very hesitant to keep replacing devices for all of us especially now days where the supposed update is going to resolve these issues. And on my end, I want to see first if the software fixes it, because I am literally burned out to get another screen protector install everything again, etc. Now the official answer is wait....for the update. If they don't keep their last promise of March update to resolve this issue, that is when my patience will run out and I'll jump to a different device. Although, I love this phone....
This is the longest online posting of any sort in my life ever. I hope this somewhat gives you a new perspective on what unlucky GNex user like myself had to go through in the past 4 months due to getting "bad batches"
Trust me, I hate to live in a society where anybody can talk about law suits against anybody. But, this was one of my first moments that I literally felt like I was hopeless & got betrayed by VZW / Samsung / Google. I started to fantasy about way to make them responsible for this poor product and service. All I wanted was at least 60 percent working "4G LTE Smartphone". (4G LTE is turned off due to connection drop, Phone is unusable as business purposes due to frequent one-way-cut off). After $299 and 2 year contract with $75 monthly service bill of 4 months with all the time I spent to help VZW/Samsung with this issue as a customer, my wildest dreams of thinking of participating in a class law suit, which will never happen, actually make me feel a little bit less helpless towards these major corporations as a customer.
Thank you for hearing my plea. I sincerely apologize for the length of this post.
Hope more of us can enjoy this great GNex in the near future.
After all, I love this device, I love this XDA forum and GNex community. I wouldn't want to switch to a different device just yet
OK, I'll admit it: I'm a huge fan of Defender 2 game. Downloaded because it was so heavily advertized that my phone suggested it in notification - and played ever since.
Initially, the game played lie a charm, no problems whatsoever. 4.0.2
However, I had some issues with the phone and took it to service a couple of times. After the second time at service, my phone upgraded to 4.0.4 and my troubles with the hame began. I should mention that I'm grateful I had a protective foil because the idiots there managed to seriously scratch it Anyway, the problem:
Every once in a while (2 - 3 games taking 2 - 3 minutes each), the screen just stops responding. My weapon no longer shoots arrows, I can't cast spells, etc, etc. This happens regardless of game time: it can happen during the second game as surely as during the twentieth. Edit: Lasts up to 5 seconds.
However, the non-responsiveness is limited: touch usually stops working on the right (bottom) part of the screen, but still works on the other side (where speaker + front camera are). I have managed to actually observe an instance where the border between working and non-working section was extremely clear at about 1/3 - 2/3 split. Moving my finger in and out of this zone would make the game start shooting arrows again or stop doing it, depending on the zone I moved my finger into.
Perhaps I should also mention that the phone heats up quite a bit during gameplay. However I'm not so sure it should be a factor since the unresponsiveness can happen even right after I start playing. But perhaps that's also a factor to consider?
Anyway - anyone else having these issues or someone that can explain what I'm experiencing?
I started having the same issue yesterday morning as well - except it seems to be ALL the time. The bottom 1/3 of the screen doesn't respond to touch about 50% of the time. Typing is virtually impossible and every touch must be made deliberately and repeatedly. I downloaded a multitouch test and it was quite obvious where the division was between responsive and un-responsive.
I'm rooted on 4.1.1 with stock everything. I restored to my previous nandroid backup from a week ago but still had the problem. Definitely seems like hardware now.
I really don't want to have to buy a third Nexus...
Funny: I just flashed minco ROM which has Francisco's kernel and this doesn't happen any more. Played some 20 rounds so far so I can't say for sure yet, but it seems this rom solves the issue where stock and some others didn't
Latest update: the minco ROM does help, but it does not solve the issue.
I will try to escalate this to Francisco, perhaps (look, I'm an optimist, OK? ) he'll be inclined to look into the issue. Seems to be something few people are aware of. I imagine there aren't many games where one has a fingen onscreen all the time...
A lot of people are experiencing this problem (including me). I'm pretty sure its a software issue. Mine started after I updated my phone from ICS 4.0.2 to 4.0.4...and with jelly bean. I would love for some one to find and correct this issue.
Sent from my Galaxy Nexus using xda app-developers app
Yes, me too - moving from 4.0.2 to .4 seems to be when they introduced the problem. Don't know about lot of people though: searching yielded almost nothing.
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.
So, I got my Note3 last week as soon as I heard CM11 nightlies were officially available. I spent zero time with the stock ROM.
Everything installed perfectly the first time. CM11 ran nearly perfectly, especially considering it's a nightly and there are no stable releases or RCs, yet, etc.
On Thursday I spent a full day at my desk at work. I noticed that my phone rebooted in my pocket. I figured "hey, it's a nightly...I've seen far worse"....then I noticed almost every 2 hours it seemed to reboot again, sometimes more frequently. It never rebooted in the middle of me using it...only while in my pocket.
So, I figured "hey, no big deal. Another nightly or two and this should be ironed out." So I restored my stock backup on Friday after work. All weekend long, no problems whatsoever. I figured it must have been something wonky in the nightly CM11.
Then on Monday, while sitting at my desk, it happened again...and again....and again. Same exact circumstances. I figured maybe I borked something so I got a restore-to-stock and flashed it via Odin.
Well, long story short this continues to be a problem whenever I spend any significant time at my desk at work. It doesn't happen anywhere else so far. It happens with any ROM I throw at it. I've Googled around and it appears that I'm far from the only person experiencing this problem however I don't experience froot-loops like a lot of people. Just semi-random reboots.
Now, I'm pretty convinced that a different (or new) modem would take care of this. I had the GS2 on Sprint and we had a problem we referred to as "LOS" (Loss Of Service) which typically required a reboot...even on my bone-stock phone...it seems to happen with the same randomness. One thing I do know about sitting at my desk, my phone is constantly switching back and forth between H, H+, LTE, DC and occasionally E...Edge being the only thing that gets solid service about 1 wobbly bar.
That's my own theory. This isn't a deal breaker for me. It only happens at work and if I wait a few seconds my phone is back in commission without any intervention.
Anyone else have a similar experience, tips, ideas, theories...? I'm more curious than anything.
Perhaps a Wi-Fi issue?
krelvinaz said:
Perhaps a Wi-Fi issue?
Click to expand...
Click to collapse
I keep wifi off at all times, wifi scanning set to off. I have unlimited data and my 4G speeds outclass my (relatively very good) cable modem speeds at home and at work (I live and work a stones throw from the NOC...I mean...literally, across the street from both places). I would prefer wifi if it wasn't sketchier than my cell connection.
So, it's not that.
How many files on your microSD card? Notice I asked how many, not how much space taken up. Android's media-scanner service seems to have huge stability issues once you cross the 10,000 files threshold. If that's your case, delete some files and see if it still reboots. I had about 10k files, deleted down to 6.5k and no more random reboots for me.
I have the same issue, and I don't have a micro SD card in the slot. The phone will randomly restart, usually after unlocking the phone. I have disabled wifi-scanning, auto app updates, and factory reset device, but nothing helps. It didn't do this before the kit kat update. It only happens maybe once a day or every other day. It's not terrible, just annoying at times. I'm thinking its a software bug.
Also, i'm running everything stock at the moment.
I have been on Cyanogenmod nightlies since I got the phone...and in the past week or two it does not reboot randomly with either Cyanogen or AOKP. At all. Still does with TW, I haven't taken the KK update so I don't know if that will help or hurt....and unless I absolutely am required to I won't be taking that update ever.
Maybe some kind of interference, that's kinda odd that it's happening only at your desk. And on stock.....
Sent from my SM-N900T using XDA Premium 4 mobile app
Couple of weeks back I wrote about Netflix stuttering/ dropping frames a few times per minute. Someone gave me some feedback that my internet connection might be too good for Netflix. This actually seems plausible given fast lanes and the fact that others with MUCH slower speeds are able to stream high quality without a hiccup.
I don't watch much Netflix but today I wanted to watch house of cards so I unplugged the Ethernet and switched to WiFi. The same issue persists...
Just wanting to watch the show, I switched the input to apple TV which is hardwired. Not only does it not have problems but the quality is NOTICEABLY better!
I have 2 aftvs. My other box doesn't have the stutter issue. The only differences are its running 51.1.4.1 and the box with the issue is 51.1.4.0.
Btw--i contacted amazon not just about this but also the recurring tiny screen problem, and the "unable to play this title" problem. They seemed to know disturbingly little. First, they told me if I had the old red icon Netflix to go to the appstore and uninstall the old one then install the new white one.
Of course I already have the new one. There is no standalone appstore to go to, and the update just over writes the old one. Are they even using fire TV over there?
Needless to say that didn't help, as I think tech support anticipated. Which is why they ended with "contact Netflix"
So anyone here have an idea? Thanks.
KLit75 said:
Couple of weeks back I wrote about Netflix stuttering/ dropping frames a few times per minute. Someone gave me some feedback that my internet connection might be too good for Netflix. This actually seems plausible given fast lanes and the fact that others with MUCH slower speeds are able to stream high quality without a hiccup.
I don't watch much Netflix but today I wanted to watch house of cards so I unplugged the Ethernet and switched to WiFi. The same issue persists...
Just wanting to watch the show, I switched the input to apple TV which is hardwired. Not only does it not have problems but the quality is NOTICEABLY better!
I have 2 aftvs. My other box doesn't have the stutter issue. The only differences are its running 51.1.4.1 and the box with the issue is 51.1.4.0.
Btw--i contacted amazon not just about this but also the recurring tiny screen problem, and the "unable to play this title" problem. They seemed to know disturbingly little. First, they told me if I had the old red icon Netflix to go to the appstore and uninstall the old one then install the new white one.
Of course I already have the new one. There is no standalone appstore to go to, and the update just over writes the old one. Are they even using fire TV over there?
Needless to say that didn't help, as I think tech support anticipated. Which is why they ended with "contact Netflix"
So anyone here have an idea? Thanks.
Click to expand...
Click to collapse
I've recently been having the same jitter/lag on Netflix. It's not all the time though. It seems to happen in episodes (no pun intended). With several back to back jitters over the course of a few minutes, then it's fine. I only occasionally get buffering pauses, so I don't think it's that. A clean reinstall and clearing of Dalvik/cache doesn't help either.
Were you able to find resolution?
xm41907 said:
I've recently been having the same jitter/lag on Netflix. It's not all the time though. It seems to happen in episodes (no pun intended). With several back to back jitters over the course of a few minutes, then it's fine. I only occasionally get buffering pauses, so I don't think it's that. A clean reinstall and clearing of Dalvik/cache doesn't help either.
Were you able to find resolution?
Click to expand...
Click to collapse
I did report in another thread (with the hope others would chime in but no one did) that 51.1.5.0 seemed to have fixed Netflix. Several weeks later I can confirm it did for me. Prior to that nothing I did could fix the multiple issues I was experiencing. If you're already on the latest firmware I'm not sure what it could be.
While it has improved, I find it strange that Netflix on my atv3 still displays a much better resolution than aftv. My conspiracy aka wild & crazy theory is the 2 streaming giants are fighting a passive aggressive war. Its not that outrageous. But I don't think amazon is intentionally throwing the monkey wrench. Its more like if there is an issue they could address they willingly choose to ignore it. Just a thought--sorry its not helpful. Hope you find a fix.
KLit75 said:
Couple of weeks back I wrote about Netflix stuttering/ dropping frames a few times per minute. Someone gave me some feedback that my internet connection might be too good for Netflix. This actually seems plausible given fast lanes and the fact that others with MUCH slower speeds are able to stream high quality without a hiccup.
I don't watch much Netflix but today I wanted to watch house of cards so I unplugged the Ethernet and switched to WiFi. The same issue persists...
Just wanting to watch the show, I switched the input to apple TV which is hardwired. Not only does it not have problems but the quality is NOTICEABLY better!
I have 2 aftvs. My other box doesn't have the stutter issue. The only differences are its running 51.1.4.1 and the box with the issue is 51.1.4.0.
Btw--i contacted amazon not just about this but also the recurring tiny screen problem, and the "unable to play this title" problem. They seemed to know disturbingly little. First, they told me if I had the old red icon Netflix to go to the appstore and uninstall the old one then install the new white one.
Of course I already have the new one. There is no standalone appstore to go to, and the update just over writes the old one. Are they even using fire TV over there?
Needless to say that didn't help, as I think tech support anticipated. Which is why they ended with "contact Netflix"
So anyone here have an idea? Thanks.
Click to expand...
Click to collapse
KLit75 said:
I did report in another thread (with the hope others would chime in but no one did) that 51.1.5.0 seemed to have fixed Netflix. Several weeks later I can confirm it did for me. Prior to that nothing I did could fix the multiple issues I was experiencing. If you're already on the latest firmware I'm not sure what it could be.
While it has improved, I find it strange that Netflix on my atv3 still displays a much better resolution than aftv. My conspiracy aka wild & crazy theory is the 2 streaming giants are fighting a passive aggressive war. Its not that outrageous. But I don't think amazon is intentionally throwing the monkey wrench. Its more like if there is an issue they could address they willingly choose to ignore it. Just a thought--sorry its not helpful. Hope you find a fix.
Click to expand...
Click to collapse
Thanks for the reply. I didn't take the latest update because I have mine with the system/data mounted to an external HD and the updates ability to use a USB seemed less robust than the hacked version. Maybe I should relook at updating now.
xm41907 said:
Thanks for the reply. I didn't take the latest update because I have mine with the system/data mounted to an external HD and the updates ability to use a USB seemed less robust than the hacked version. Maybe I should relook at updating now.
Click to expand...
Click to collapse
Well let me say the loss of mouse functionality might've made me hesitate but unfortunately I didn't know. I don't regret it because unlike others I don't use the BT keyboard for everything but had just bought the k400 like 2 weeks earlier so that probably wasn't money well spent...other than that I'm VERY happy with the new firmware.
KLit75 said:
Well let me say the loss of mouse functionality might've made me hesitate but unfortunately I didn't know. I don't regret it because unlike others I don't use the BT keyboard for everything but had just bought the k400 like 2 weeks earlier so that probably wasn't money well spent...other than that I'm VERY happy with the new firmware.
Click to expand...
Click to collapse
Oh. I thought the latest firmware brought native BT capabilities.
xm41907 said:
Oh. I thought the latest firmware brought native BT capabilities.
Click to expand...
Click to collapse
Oh yea it does...I was referring a specific functionality ( it was reported here) basically the mouse cursor is invisible on the home screen and on many apps I've tried. It makes the web browser tougher to use, I think. But yes BT capabilities improved, its just losing that cursor really messed things up for me and many others. I haven't explorered any Possible workarounds. I've only owned the keyboard for a short time but some use it for a lot of things. Might depend upon how often you use it.