Perhaps someone with more electrical engineering know-how can answer.
It's almost certainly a hardware issue. I don't know if it's the cable I'm using, some grounding issue, or what, but the problem is really annoying.
Full disclosure, I have a tmobile/at&t motherboard inside a N7105. I swapped it over last fall-ish because the N7105 motherboard developed a sleep of death problem that persisted through every rom I put on there, and even occurred when I was in recovery. Whatever, I can't get LTE on tmobile with this phone anyway, which is why I acquired a tmobile motherboard to swap in.
Perhaps it was always a problem, since I rarely use the headphone port. I got an unpleasant surprise a couple months ago when I tried- nothing but static through headphones. Long story short, it's apparently some grounding issue? I followed the recommendations in that post. I still needed to smack it a little before it would work. But it more or less solved the issue.
I've been having wifi problems recently, and it may or may not be a consequence of the above issue. My wifi would simply stop detecting wifi signals. It would stop connecting, and then the wifi settings would eventually realize that it couldn't see any networks at all. Turning the wifi on/off or rebooting wouldn't bring it back. I keep solving this by disassembling my phone (poor thing, it's been disassembled so many times in the past month), letting it sit for a bit, and reassembling it. I'm slowly working out that putting screws in any slot other than right by the wifi antenna would eventually result in the lost wifi. It does work to bring the wifi back, and anything less doesn't. I don't know why. It might be a contact issue, but I can't see any difference between this and the N7105 motherboard.
In any case, this means that whatever grounding connection needed to make the headphone port work just isn't happening. That's fine, I still have my trusty rockboxed ipod.
But the wifi problem persists, and it's completely absent in the N7105 motherboard (but sleep of deeeeaaaaath). It could be that the Anker 10ft cable I recently got is no good or allowing too much electrical noise through or something. Maybe it doesn't like being charged too quickly. The wifi problems do occur more frequently when I use the Anker cable to charge.
To be honest, I'm not holding out much hope for a solution. The phone is three years old, and even if I could have happily continued using it for another year or so, it is starting to show its age. I've been browsing Note 4s on ebay. It might be time for a change.
The motherboard in the ATT (i317) and Tmobile (t889) are not identical to the n7105 which may be part of the issue.
I have also read posts where XDA members had replaced their USB charging port and flex cable and would up with no cell signal and wifi.
Maybe the USB port/cable in the needs to be changed too?
I'm not sure if the motherboard is an issue, since I've used it in this configuration for months with no problems.
In any case, I've stopped using my 10ft Anker cable to charge, and as long as I leave most of the screws out, the wifi behaves. I don't know if it's electrical noise, more grounding issues, static electricity, or what. It's not ideal, but it's better than no wifi.
Related
A few weeks ago I decided to take the plunge and root/unlock my Gnex. Installed Team Kang AOKP Release and then recently updated to Milestone 4. I am running the GSM Version on Tmobile. Originally as yakjuxw and flashed to yakju before rooting, etc.
Has anyone else run into problems with the Galaxy Nexus charging? It seems to have been progressive. About a week ago my phone randomly started turning the screen on and showing the 'charging' icons and animations as if the phone was plugged in. Then A few days ago I had to play with the plug for it to begin charging. Earlier yesterday, I've reached a point where my gnex would only charge if its off. If i plug the Samsung charger into the phone, the battery screen displays "Not Charging" as opposed to the "Discharging/Charging", so its my guess it knows the charger is plugged in but cannot charge the battery for some strange reason.
It seems im not the only one.
http://groups.google.com/a/googleproductforums.com/forum/#!topic/mobile/RahZtFg39DU
I've contacted Samsung and they are aware that this is happening and have offered to take my phone into repair under warranty but that would require sending my phone off for 2 weeks, so i'd like to try something else.
As pointed out by the last poster in the google thread, squeezing the charger seems to fix the issue but just for a couple minutes. Does this have to do with the contacts/usb charge board/plug?
I have the same problem, but I have root on mobile and I did not cover the guarantee in Samsung
supumaster, the galaxy nexus is a phone that is very easily re-locked and un-rooted. do some searching online. you can 'get your warranty back'
I had the exact same problem, tried everything and nothing worked, finally sent phone to UK here's more info
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=23789
It sounds like liquid damage to me.
Look really closely inside your charging port for anything green/white, especially toward the very base of the pins. Also, look at the charger itself for any green/corrosion on the pins. If you find any, dip a toothbrush in some denatured alcohol and scrub your charging port.
Works like a charm.
Normally. I'd agree with you, but if you check out that google thread chanchan posted above, hundreds of galaxy nexus users are experiencing the same thing. So either this phone is EXTREMELY prone to moisture damage, or there's something very very wrong.
I had this issue for a day or two at the beginning of February. It disappeared by itself and hasn't returned since.
I had the same problems, specifically it wouldn't charge on some chargers (my car charger), and it would think it was plugged into USB when it wasn't, the lightning bolt would light up, and the screen would never go into full sleep.
I went through a whole lot of that thread, and lots of other people having the same problems, one sugestion was to get a toothpick and stick it in the phone's USB plug and lightly bend the 'tab' up towards the screen. so, i did that, and it fixed all my problems.
likely the tolerance between that 'tab' and the bottom of the plug are so tight, having a USB cord pull on the 'tab' makes some of the data pins short out on the metal surround of the plug. bending it back makes it 'unshort', and work like it's supposed to.
i would highly reccomend being VERY careful with this if you attempt it, i'm guessing its VERY easy to snap off that 'tab' in the plug and ruin your phone.
if this happens again on my phone, i'm sending it back to samsung or verizon to fix.
So I seem to have temporarily corrected the problem with the toothpick trick. I can't advise anyone to do the same as the chance of breaking is probably pretty good. Will let you know if the problem returns.
In other news, I'm on hold with Samsung. I've just been informed that the New York based company that I purchased my Gnex device, is actually not a US device and they will not provide any sort of support for it. If i want support I have to contact UK division of Samsung and all repairs would have to go through them.
I am just f***** livid right now.
I had this problem for a couple months. Now even the toothpick thingy no longer works.
Can no longer get USB data connection. Computer keeps saying "Drivers fail to install" or somesuch. Sometimes it manages to charge via USB, no luck via the wall charger...
Time to send it in. Been a Nokia user for 10+ years, no issues that required it to be sent off for repaired. Super disappointed. Google should get someone else to build their Nexii series...
I have this issue every now and then. It goes away after a reboot.
Sent from my Galaxy Nexus using xda premium
I've this problem too. My nexus always gets stuck on 97-98%, and the battery screen says "Not Charging". So, somewhere on some forum I've found this trick and works fine for me.
Just unplug the charger and then plug it in again after waiting for 10sec, it will gradually go to 100% in 5-10mins and the status will change to "Charging" from "Not Charging".
YuryAC said:
Normally. I'd agree with you, but if you check out that google thread chanchan posted above, hundreds of galaxy nexus users are experiencing the same thing. So either this phone is EXTREMELY prone to moisture damage, or there's something very very wrong.
Click to expand...
Click to collapse
This issue has nothing to go with watter i believe. It was only an excuse for Samsung support guys as this happening way too often and they decided to blame us instead of Samsung.
First time this happened to my Galaxy S II when there was no rain oustside and watter damage was near to impossible. Now this happened to my GNex while i had a flu and were in bed for last two days. Watter? Nah, i felt poor but never pissed on my self nor on my phone :-D BTW, GNex started to charge again when i plugged in an HTC charger. So i'd rather blame charger/charging port quality and not the watter.
Don't take this as a fix but I managed to make the problem on mine go away by gently bending the connector inside the USB port with a pair of tweezers.
So it kinda hints at a contact issue with the connector. Could have stemmed from using non-Samsung provided USB cables and chargers...
Before you all jump down my throat for not searching the forum, I did, and did not find anyone with a similar enough problem to warrant not posting.
I have a HTC incredible 2, I've had it for around a year, and it currently has the Aeroevan CM9 with his custom kernel installed. I pulled it apart and cleaned out the usb-micro port, and reflowed the solder on all connections. All of the pins in the micro-usb port have continuity to the flex cable pads as well, so it does not appear to be a hardware problem with the charging port assembly. It still refuses to charge right now. Sometimes it will charge for 10 or so minutes, but the percentage will not really go anywhere, and it will drain it back to zero and shut itself off. edit: I've tried 4 different usb-micro cables, and none work.
This seems to be somewhat of a common problem for this device, and I'm wondering if any of you have had the same problem, and if you fixed if, how. Most of the posts I've seen on the verizon question board were with people who still had phones under warranty, so they were just given replacements. My warranty expired around a week or two ago. I might pick up a new battery to see if that works. Otherwise, the upgrade (which is only available because one of the other people on my plan has one available) costs $130. I'm in college, and can only afford that if it is an absolute necessity i.e. there is no easy or feasible solution.
Thanks guys.
Dude its a known issue with the phone. You will need to replace the micro-usb port. Sorry to be blunt, but its happened to quite a few. It happened to my nephew and he needed to get a new phone.
here you go
http://www.ebay.com/itm/USB-Power-C...onnector-HTC-Incredible-2-S710e-/170734676910
I guess what I don't understand is that, electronically, the assembly is fine. Oh well, I was going to do that anyway.
Hi,
I have had my HOX for 3 weeks now and since yesterday (so, not a new thing), I keep losing the signal in my appartment, in some places outside. Oddly enough, signal is OK (tho just 3-4 bars) in my office.
1. Could this be related to the WIFI antenna issue even tho it's not WIFI issue? In other words, is there a chance that by fixing the WIFI antenna issue, I can get solve this?
2. If not, what are my other options? The garanty is already voided so I cannot send it to HTC for repair (voided by an "unofficial repair center" after the screen got smashed by dropping it from like 1m... - it's very possible that the fall or their repair broke something else, but the repair was already 2 weeks ago)
Thanks for your help!
First thing I'd ask is are you rooted? Have you been playing with radios recently?
If not, the next thing I'd look at is trying to find someone else with a micro-sim, and asking to borrow it. If they still get a good signal on their network on your phone, it might be your sim card. I had a faulty one once which just started dropping network like you describe. It can happen.
If their sim card also shows poor reception, you might have an aerial issue caused by the unofficial repair centre opening the phone up. (Although from the feedback on the WiFi issue thread HTC have worrying repair standards too).
If you can't find another micro-sim, just try finding someone on the same network. This phone (when working) has excellent network reception (better than my previous Desire S) so if a side-by-side comparison shows a big difference in signal strength, again I'd think about getting the sim replaced.
https://play.google.com/store/apps/details?id=de.android.telnet&feature=search_result#?t=W251bGwsMSwyLDEsImRlLmFuZHJvaWQudGVsbmV0Il0.
If your replacement sim still has the same problem, then I'd consider opening the phone up as per the video guide in the WiFi Issue thread in the general section. Seems to be quite easy if you are careful. It is unlikely that the same aerial for the WiFi is also the 3G one, but I've looked at the tear down pictures, and can't read chinese! If i find out which one it is, I'll update this post. If not, just check all the connections.
Hi,
I have also been having this network drop issue but only near my office. The reason I think is that my office is between two towers and every now and then it tries to balance the traffic on the networks and hence keeps disconnecting devices from one to connect to the other one... However, I have cut out my normal sim into a micro sim and that was done by the guys at the shop from where I bought the device and they had said that if there are any issues, then please order a proper micro sim and use it....
I think that might also be the problem.....
levtrp savans
All,
After checking that my SIM card wasn't in cause (used a friend's HTC One X to test my SIM card and test with his), I broke open the case and saw the problem.
The problem is the damn design of those antenna contact! I saw probably around 10 of those small metal piece that are supposed to be a bit "up" and somehow touch the contact area on the back cover.
I found that 2 of them (in two different pairs, they all seem to be in pair to create a closed circuit I suppose) were a little bit lower than their counterpart, so with a flat screwdriver, put them upright, closed the case and voila, I am enjoying network with full bars since yesterday.
If the issue comes back (and it probabl will, if they got bent the first time it probably means that the metal already was bent beyond its elastic deformation area), I'll probably end up buying a soldering iron a add some patch of silver to increase the height of the contact zones. That's .... just lame I am sure they had a good reason to do that, but seriously!?
Guillaume
Glad you got to the bottom of it. Yeah I think the design choice is forced from having the main body of the phone slide in at an angle into the outer case. If the two parts just clamped together like a more traditional phone build, then they perhaps could have used a different approach.
I'm putting off opening mine up (I have the dreaded WiFi drop issue) as my current case puts just enough pressure on the screen to act like a permanent squeeze, halting my problem.
Would be interested to know if the problem reoccurs like you said it might. Keep us posted.
Hey all,
A friend and I both got SGS3's within the last couple of weeks - mine's VZW, theirs is Sprint, both 100% unrooted, bone-dry-stock (for now). I noticed some really strange behavior, and I'm wondering if anyone else has any experience or thoughts on what might be going on.
Anyway, when the MHL cable is plugged into my phone, everything works as expected, however, plug it into my friend's Sprint device, and the video output works, but within moments the data connection drops and then the signal is lost altogether.
I'm not sure what the deal is, at all, and probably wouldn't have believed it if I didn't see it, and test it several times myself. My best guess is that because the 3G signal wasn't super strong in the first place, induction in the MHL cable caused enough interference to drop the signal all together (though going from 3 or 4 bars to X, may suggest otherwise). I may try wrapping the cable through a ferrite core or something to see if that helps out... but that's kinda a shot in the dark.
I spent a few minutes searching around, but I'm wondering if anyone has any additional thoughts or experience with this kinda thing.
Happens on 2x Sprint GSIII's that I've owned. Now Im not sure if it's a hardware issue or not.
I did a search and most of the Wifi problems seem to describe knox security and bootloader issues.
Here, I wish to describe/discuss what seems to be a hardware problem in my n7100 note 2.
This occurs with stock and dr. ketan rom on 4.4.2 even with wifipatch applied (technically not needed).
OS 4.4.2
boot loader: n7100ZSUFNL1 (I believe this bootloader should be ok - correct me if I'm wrong).
model GT-n7100
ISSUE
- the wifi icon doesn't turn on or wifi drops out when the system is running hot. This happened the first time after I flashed a ROM/upgraded and I thought it was a ROM issue.
- however, more recently, I have managed to keep the wifi signal absolutely stable when i open up the back cover and run a fan blowing on the back/cpu area at the top back of the phone around the camera area.
- with fan cooling => completely stable
- without fan cooling => drops out when system under load or randomly.
for some reason, omega rom had a problem for me where it kept disconnecting irrespective of the heat
I have seen discussions of our phone overheating but this seems to be a hardware problem with the wifi module.
I presume that there may be micro fractures with the wifi chip solder (seems to be a theme in electronics) that may be causing wifi problems with overheating.
This happened with an iphone 4 voice audio processing chip once for me and the "online community" had figured out a fix by taping in a "pressure mount" for the chip.
//blog.lovefone.co.uk/iphone-4-faulty-microphone-audio-chip-problem
Any suggestions on taping in a heatsink or pressure against the wifi module?
Help would be appreciated. Just adding to the knowledgebase in the community.
When Samsung adopted RoHS some range of devices plagued with badly soldered BroadCom chips. I personally know one S3 and two Note 2 (one is mine own) with all the same problem: no WiFi from time to time and likely no BT too.
I paid ~100 euros to change the main board with BC chip guaranteed working about half a year ago.
Thanks for the quick reply and confirmation.
After ordering a new midframe; playing around with screws and disassembling it a few times; it does feel like a solder joint/connection issue.
I haven't heard much feedback from the net on this problem which is why i raised it.
Others on the net have mentioned loosening the screws securing the motherboard down. I will try that as well but I presume that with a loose solder joint; overtightened screws may warp the motherboard just enough for the connection to flake out.
THanks again.
PS - if anyone else has the same problem/suspicion; please chime in.
So, in follow up.
Adding aluminum tape to the wifi chip didn't seem to work. I took it off and reseated the midframe where the antenna is located.
Still was getting dropped wifi.
Disassembled; took a small screwdriver and gently lifted the wifi contacts from the motherboard up so that it makes better contact with the midframe.
Seemed to help.
It's definitely hardware. Whether it's a problem with the WIFI chip or with the antenna; i don't know but it's somewhere along that line.
Crazy hardware gremlins