Develop Bugs

Serious WIFI & 4G issues PLEASE HELP GIVE INSIGHT

I really need some user commentary here as I have tried vigorously looking into my connectivity 'flimsy-ness' lately.
I have a GNex LTE version
this is fast...when it is fast.
However, wifi drops at times. and 4g if the reception is lost and reverts to 3g...it never goes back to 4g even in zones where it obviously exists, needing to be corrected manually.
It is very nerve wrecking. such an expensive phone to have such issues.
My question is, does anyone else have this? (im on 4.0.3)
should i return this and ask for a replacement? maybe this is defected.
Please help out as time is running out for a replacement at verizon
THANK YOU AND HAPPY NEW YEAR

I got hit by the Verizon outages and outside of that, I had some cell data connectivity issues twice. However, I have not had them since the last outage. (Also after changing ROMs both which are 4.0.2)
My father was visiting and got hit by what you describe and fixed it with a power cycle and hasn't said it occurred since.
How often does it occur for you?
To be on the safe side and so you don't miss your window, you may want to exchange.

A lot. The wifi is absolutely terrible. It does not stick. And turning the phone off with having put on the always on thru advance wifi settings it still turns off. I can not and will not risk it. Talked to Verizon made them express mail another gnex. I'd rather take my time and compare then go to the store and chuck this and receive another. One this is for sure. If the other one has the same problem. I will be very very sad. I love this phone (plus I have the unlimited plan..switched with my gf...and MAN Is it nice going over 10gb already)
I hope no one else has this problem. Really curious to know.
Sent from my Galaxy Nexus using xda premium

Seriously, no one offers any opinions??
Sent from my Galaxy Nexus using xda premium

Mine is solid. Holds wifi, holds 4G. The problem you are talking about has been brought up by others. Look around on this forum and you'll see it has talked about. People have had luck swapping out for another and others haven't. Looks like there are simply some out there with issues and you got one. They do not all have this issue. There is an OTA update coming with 4.0.3 soon that MAY help. You might just want to swap it out. If you do, don't leave the store until you know it's working.
Sent from my Galaxy Nexus using xda premium

Same thing happening with my wifi dropping connection all the. Gmail and whatsapp messages are always late, bloody frustrating:-[

Update: just received a new gnex. In the mail. Can confirm within the first three minutes of using it......same problem. Unbelievable
Sent from my Galaxy Nexus using xda premium

I have had the same router for the last 2 years, my nexus S never has had any sort of drops on wifi like this.
This is without a doubt a serious problem. I will be now doing more thorough testings with the 4g reception followed by the 4g dropping to 3g and seeing if it ever reverts.
I pray to god this is a software issue. but to be honest...having had all nexus's (nexii?) i have never had a reception issue or had an update that improved it...so im sort of freaking out now

I'm having this issue as well. It will help if you change the wifi policy to stay on always. Hit menu inside the wifi options.

I had the same issues and returned mine. I hope it gets fixed, because I loved everything else about the phone and want it back, but not at the expense of poor data reception.

on a NEW one that was sent...SAME PROBLEM.
ALREADY HAVE THE ALWAYS ON POLICY.
....this is some scary S*$T!!!!

I have had wifi issues with specific routers. I have 2 Linksys wrt 54g with latest firmware which frequently do not connect despite having a strong signal. I have a router in the micasavrde home automation controller that connects fine, all with wpa2 security. The wifi at work at 2 different sites works fine, but I am not sure what routers are being used. I think this is mainly a software issue with certain routers and may be fixable. Maybe we need a thread documenting people's experience with routers with no issues and routers that have problems .
Sent from my Galaxy Nexus using Tapatalk

[Q] Looking for SGH-T989 hardware knowledge

I have a very strange wifi/bluetooth problem that seemed to come out of nowhere and I think it may be hardware but I'm not too sure. When I format the system and install a new ROM everything works as it should for a little while but then within a few hours the software toggle switch grays out and wifi and or bluetooth don't respond. Bluetooth always seems to go out first but wifi follows soon after. I thought originally I had a corrupted driver or something but no matter how many different ROMS I try, going from gingerbread all the way to jelleybean and the phone always acts the same after a seemingly random amount of time. I don't know too much about how bluetooth/wifi drivers work so this may still be the issue.
Sometimes by toggling the various switches off/on a bunch wifi will go back on, and even more rarely bluetooth will work without a system format but it never stays working. If anyone knows what the problem may be I would appreciate some help or if you can point me to a component level diagram that would be helpful too. I have been looking around for a few weeks now with no luck. I never dropped the phone and it looks like I just pulled it out of the box. I did take it apart and look for loose connections and cold solder joints (I have quite a bit of experience at component level repair) but found nothing.
I did try to go back to stock GB with Odin and that was about the same, it worked for about a day and then the problems crept back up.

I thought for sure someone would have an answer.
Sent from my SGH-T989 using Tapatalk 2

I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app

jmpsatx said:
I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
I switched to twrp and the problem isn't gone but it is better. I'm not sure if it's a coincidence or not but this seems like a positive step.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

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.

weak wifi transmission

I recently reverted to stock on my at&t note 2. I am having wifi issues. The phone gets a strong signal from my router (-50) but I get authentication errors connecting if I am not very close. Standing 5 feet from the router I get terrible throughput. I am running dd-wrt and can see that the router is only getting -90 signal from my phone. Every other device is much stronger.
I have tried disabling wifi power save mode and have tried the OTA update to ucamh3 baseband.
Any suggestions greatly appreciated.

With a weak or malfunctioning wifi setup over multiple roms ....I might suspect a bad antenna ??
Not a for sure thing...but it should be considered...
Several of these devices were returned early on with antenna issues...
With a pure stock UCAMH3 rom running...wifi has been excellent...
I would try a clean slate data reset in recovery...and a router reset as well...
Then set up the wifi again on the device...
It's a long shot...but is certainly a good first step in diagnosing the device and the antenna...
Does the device suffer the same in other wifi areas ??
If not...look back to your home system....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.

kevingt01 said:
Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.
Click to expand...
Click to collapse
I'm on CyanogenMod now with no improvement. Router sees strength of -85 and SNR of 9 when I'm 5 feet away from it.

exact same issues here with i317. wifi worked great for about a year while rooted, and running multiple roms. i loaded SkyNote4.3 and it's been down hill ever since. I'm currently on DN3 4.3 and it works fine if i am close to my router as well. have S4, and Nexus 7 on same router, and they work fine with great signal, so it's not the router. I even removed security from my wifi as a test, and same results.
I have tried reverting to 4.1.2 and still no change. Appears to be SNR related at the moment, as my other wifi devices have 38-50 SNR values on DD-WRT, but my i317 has 10-12. No microwaves or any of that jazz going on, all 3 of these devices sitting next to each other when pulling values.
still investigating, but if anyone has any suggestions i'm open to ideas at this point.
what has been tried: reverting to 4.1.2 stock firmware from sammy, 4.2 bootloaders, 4.3 bootloaders, different modems, different kernels, different roms.

I got a replacement Note 2 from AT&T for this reason. I Googled the problem and found many mentions of it, so I called AT&T and had the CSR Google the problem while I was on the phone..
Of course I hadn't opened it up or anything...

I sent my phone to Samsung twice. The first time they just tried to update the software and claim it was fixed. That obviously did nothing to resolve the problem. I just got it back from a second visit to the service center where they replaced the mainboard. I haven't tried it yet, but expect that solved the problem. I'll confirm later tonight.

yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.

white8785 said:
yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.
Click to expand...
Click to collapse
I thought mine was antenna related so I bought a new housing. That didn't fix it. I read where one person bent up the contacts a little so I tried that and it didn't fix it. I never used to believe software would screw up the hardware, but I really believe some firmware has a bug that's pushes too much power to the wifi transmitter and damages it. That's just a hunch from a few posts I've read. It sounds like this may have happened to people with a Samsung OTA update.
If I were you, I'd log onto Samsung's site and just double check that you don't have any warranty left with them. If not, I'd even try chatting with them expressing disappointment in the device. let them know that apple geniuses would take care of you anyways. Maybe they'll be generous.. worth a shot.

So good and bad news. After getting my phone back from Samsung the second time, wifi authentication issues and drops are gone. The strength is good enough to keep me connected around the house, and speed is fairly consistent throughout the house, and is good enough for browser, etc. However, the speed still isn't up to par with other devices. I'm now experiencing 4-5mbps on speedtest.net (vs. ~20mbps on my other wireless devices). :/

[Q] Can this G2 be saved?

I obtained a used T-Mobile G2 pretty cheap (but I do have the ability to return it). Seems I've learned why it was so cheap.
I've never been able to get WiFi to work on it, and Bluetooth is extremely shaky. A check in the Phone status seems to indicate the phone cant detect either of their MAC addresses.
Just to be sure, I rooted the phone and reflashed known-good firmware. No change. I flashed an updated radio. No change.
At this point, I'm beginning to think a hardware fault (the phone's a bit beat up) has killed the WiFi chip, which is a deal-breaker for me since one thing I wanted to do was set this up to use T-Mobile's WiFi Calling.
My question is if there is anything else I can try? Or should I declare it busted and return the phone for a refund?

I would return it, but MAC address is stored in efs partition, you can always take a look at that to but I don't any change you make to that would help your issue, I bet its hardware
For more info and faster help check here
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 4 using XDA Premium 4 mobile app