[Q] mtp problems + time issue - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

OK, i've had my sgh-i747m since the first day of release, and this problem has never gone away. I have installed mtp drivers of every kind on 3 different windows7 installations, and my gs3 has NEVER been able to be connected, I always get a code 10 (unable to start device) even tho the drivers install fine, and it sees the galaxy s2 and atrix just fine. Does anyone else have this problem? I've tried many different methods to try to convince it to work, but it never has worked.
Also, since i got the device, whenever I reboot, the time resets to the beginning of the epoch (some day in 1970) and stays there untill i connect to a wireless network. So, for example, it's 7:30 pm on my phone, I am out of network range, and can't get any bars. I reboot, and when my phone boots up, the date and time are for 1970 something, and it stays that way until i get a phone connection (or wifi). The worst part is that when I do finally get the time from the telco or ntp, all my scheduled activities (like titanium back or other apps settings backup, or my alarms) all go off, even if they were scheduled for 2 am.
To test for this issue, go to date/time settings, unclick automatic date & time, then shutdown or reboot and see if your date/time are correct.
Are these issues just me, do I have a defective phone, or do others have this same problem?

Are you rooted? Running any custom software? What have you tried to fix the problem other than install drivers on different PC's?

dntesinfrno said:
Are you rooted? Running any custom software? What have you tried to fix the problem other than install drivers on different PC's?
Click to expand...
Click to collapse
i had the problem on touchwiz-stock, touchwiz with rooted kernel, touchwiz with kt747 kernel, cm9, cm9 nightlies, cm10 nightlies, AOKP unofficials, leankernel, and kt747 kernels on all the above. I've tried the windows update drivers, i tried installing kies, i've tried in mtp mode, ptp mode, with/without debugging enabled, downloading drivers from samsung, everything suggested in forums, and stuff found from search. Everything short of calling up tech support, who wouldn't touch me with custom roms installed.

gomisensei said:
i had the problem on touchwiz-stock, touchwiz with rooted kernel, touchwiz with kt747 kernel, cm9, cm9 nightlies, cm10 nightlies, AOKP unofficials, leankernel, and kt747 kernels on all the above. I've tried the windows update drivers, i tried installing kies, i've tried in mtp mode, ptp mode, with/without debugging enabled, downloading drivers from samsung, everything suggested in forums, and stuff found from search. Everything short of calling up tech support, who wouldn't touch me with custom roms installed.
Click to expand...
Click to collapse
Sounds to me you have a hardware problem. If a standard feature of the phone doesn't work in a fully stock environment there is reason (and proof) enough to make a warranty case with your carrier or Samsung.

dntesinfrno said:
Sounds to me you have a hardware problem. If a standard feature of the phone doesn't work in a fully stock environment there is reason (and proof) enough to make a warranty case with your carrier or Samsung.
Click to expand...
Click to collapse
Yeah, but it takes 4-6 weeks for that replacement and in the mean time I have no phone. but if it isn't a problem that EVERYONE has with the phone, I may be able to get a replacement or loaner. I just need to figure out if this is really just my phone, or everyones d2can handsets. I've found at least 4 other people with the time problem.

I'm running AOKP and experiencing the same problem with the time whenever I reboot and don't have an internet connection enabled. Also had this problem with Serenity ROM.
MTP runs with no problems tough.
Sent from my SGH-I747 using xda premium

The time issue i think is a known issue with the GS3. I know the recoveries rarely, if ever show the right time and date which i though was isolated to the recovery. This evening during a reboot i happened to notice my clock was way off as soon as it showed and then within half a second it picked up the time from either my wifi or the cell network and corrected itself. I am running AOKP as well but i don't think it has anything to do with the ROM. As for the OP the MTP issue alone would have me at my local shop getting a warranty replacement.

I talked to you in the IRC? Yeah? I think so.. the phone is really funky and airplane mode and then going into a reboot will screw your time and date up.

Randomacts said:
I talked to you in the IRC? Yeah? I think so.. the phone is really funky and airplane mode and then going into a reboot will screw your time and date up.
Click to expand...
Click to collapse
Wasn't me if thats who you were talking to...but come to think of it i did turn on airplane mode breifely and i'm not sure if i rebooted since, maybe that had something to do with my clock freaking out last night.

Same issue...
I have the exact same issue with the MTP device drivers... win 7 64 bit issue... some people say a factory reset, then connect before re-installing all the apps will fix it... havent tried yet.

Date changes to 1970 on reboot
I had the same issue and after hours of surfing, only solution found was to install an app like "ClockSync"
Worked for me 100%

Related

[Q] Random Reboots

I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.

Google Talk issue - after a few minutes Contacts are all offline when not

I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?
i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?
Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.
Same problem here.
Although I have not tried it with stock non rooted phone...
I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.
Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)
I updated my software which included an updated gtalk with video..so far so good.
crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.
DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.
Exact same problem with my I9100, Gtalk with video. Very annoying.
I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).
Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?
Are there any news about this issue? I'm having the same problem.

[Q] Anyone else having severe (wifi) tethering issues. Link to GoogleCode Bug

edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
luck02 said:
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
Click to expand...
Click to collapse
http://code.google.com/p/android/issues/detail?id=38563
I, like many others have had this problem since 4.1.2, rolled back to 4.1.1 and WiFi tethering worked again. Back to 4.1.2, stopped working again. Installed 4.2 on Gnex yesterday hoping for fix but still no good.
As 4.1.2 is "old hat" now I have started new issue at Google for 4.2 here
code.google.com/p/android/issues/detail?id=39618
Please anybody with same problem go there and add to report.
DO NOT turn it into a *****ing thread like so many here on xda.!!! The item to which luck02 referred for 4.1.2 at code.google.com is just full of twats ranting about their phone suppliers charges for data and crap like that.
code.google.com is to report faults and bugs and by everybody contributing pertinent information maybe Google will look for a fix. Trolling and whinging does nothing but obscure the facts...... please respect this. Just tell them model number, build and describe fault - thanks
Well there is definitely some ranting and twats involved but to my mind that's just part and parcel of being on the internet. Ignore and contribute as you can. Has anyone tried the CM build on the GNEX? Also, has anyone confirmed / denied whether third party wifi tether applications resolve the issue (requires root)?
Actually even more importantly, has anyone isolated where the breakage is actually occurring? I'm assuming it's something in the drivers / networking layer that is screwing up the routing between incoming data and the wifi layer...
I will probably downgrade if nothing else works.
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
luck02 said:
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
Click to expand...
Click to collapse
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
Even made my own Odin package using radio from 4.1.1 (even tho supposedly same as 4.1.2) system and other files from 4.2 - same result, nothing worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Tried two WiFi tethering apps with exact same result... shows tether as working, greyed out WiFi icon on tab and no go on laptop or desktop....I have spent hours on this to no avail
Have you tried any network diagnostics while not tethered?
I may be getting carrier and 4.1.2 issues. I was running some ping tests while not tethered yesterday. Full 5 bars of 'H+' running CM10 and I was getting horrible signal. More than 50% dropped packets and long ping times.
I'll roll back to an older CM sometime soon and see if there's a difference over the next couple of days.
Thank you,
stinky73 said:
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Click to expand...
Click to collapse
I'm Noob, I got problem same error on 4.2 and 4.2.1, this issue over half a month.
I have google some website, found have several people like us have this issue and still no idea to fix it...
Mostly couldn't connect to laptop or Mac Book. For me is PlayStation Vita (firmware 2.0 Wifi only)
My PS Vita could deal with my galaxy Nexus on 4.1.2 , but 4.2 is could reach Internet correctly.
I have tried several Wi-Fi Device to connect my Galaxy Nexus,
My PC , My PS3, My PSP, My Uncle Galaxy Nexus 4.1.1 (Samsung image) are working fine.
Only my PS Vita couldn't...
But base on others, have same issue on other device, so I did think this issue may cause by 4.2.
Base on this issue, I have try "wifi-tether" , whatever this download on Google play! or "3.3 pre-2" on their website.
I have it running on Factory 4.2 , 4.2.1 Rooted + Super user, this couldn't work correctly.
Running on KALO 2.0 ROM, this have error on "Clamping MMS"....
No Luck for me.
My GNexus is only one device at the moment, which could let my PS Vita online... I have some PS Vita game need running online.
This force me stay on 4.1.2 and try disable System update notification next minute, for several weeks or month until the solution come...
Or... Anyone could build a patch which could let 4.2 using 4.1.2 Wi-Fi tethering engine?

[Q] losing wifi connectivity- full bars but all gray

so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
jrmacarthur said:
I'm not trying to threadjack here, but I just wanted to share my experiences.
I've been have the exact same thing happen to my phone (Nexus maguro). I've tried every JB rom I could find, several different kernels and my wifi eventually always goes grey on me. All network activities stop. I'm back on stock everything right now and it still happens.
It happens on my home wifi as well as work wifi.
I'm about to puttstock ICS on my phone and try that out for a couple days.
Anyway, good luck with your problems, i'm going to follow this thread in hopes you'll get a solution that may help me.
If I do figure anything out i'll post back.
Click to expand...
Click to collapse
seems that this is a topic that has been posted on a bit over time with no real single culprit or fix. I'll post back if I figure anything out... I know in the Cyanogen thread, I saw info that stated that the MAC address of the phone was changing and I'm going to try and determine if that is happening to mine.
I have the same issue. Sometimes even when i pick up the phone, if i look fast enough i see that the Wi-Fi bars weren't even there! Thats only 1 out of 5 times though. The other time its usually just grey bars. Sometimes it actually will click back and they'll flash to blue and grey 2-3 times and then go solid blue. Then sometimes like you, they'll stay grey. I've tried everything too...reverting to stock, Different kernels, ROMs, routers, static IP, 2.4 or 5ghz, full auto mode. The only fix that makes it a little more reliable, is using Wi-Fi PM Fast. But even that, is not reliable. I'd say its about 50% reliable then, for a huge sacrfice in battery life. For me i've noticed this started to happen with 4.2. Before that i never had a problem. All other devices though no problem. My Nexus 7 is just fine. But the galaxy nexus, no matter what router or where i am, the Wi-Fi is totally unreliable. For me, it happens within 2 minutes that it will disconnect most times. Then 1 in 10 times it'll be fine for 10 hours.
In all honesty, i've given up. Just come to deal with it. Use mobile networks when i'm not needing to download. I can download files and stream music just fine too. If there is traffic going through, it never disconnects. But when its just sitting there without traffic, it disconnects, or, loses connection to google servers i should say.
well that's not good to hear...
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
jrmacarthur said:
I installed stock 4.0.4 a couple days ago and have not had my wifi go grey on me yet.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah, I love Cyanogen so not willing to go back to stock... waiting for them to finish 10.1 and I guess I'll see how it behaves then.
Hi all,
Just to say that I have the same problem. I have been upgraded from ICS to 4.2 and nothing had happened but I had to downgrade to 4.1.1 (AOKP Build 4) due to other issues and after that I started notice the WiFi problem.
At first I thought it was when the screen went off, but I has happened with screen on too. I have to turn WiFi off and the back on to connect properly again, very annoying.
As I said I started noticing this after I downgraded, but then again, I had used AOKP 4.1.1 before without this issue. I think that it is time to change my phone :/
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
I'm on Muzzy 4.2.2 and I'm currently having the same problem. It's not a new problem since I remember having it months ago (disabled my phone's WiFi because I kept missing emails and other notifications - grew tired of dealing with it). I thought it was my router, so I swapped it with a newer one recently, but it carried forward (old router was TRENDnet Draft N and the new one is ASUS RT-N66U).
I would like to know how to properly troubleshoot this problem.
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
subhramani said:
I'm glad I didnt have to create a thread for this. I have been facing this problem quite a lot. I can confirm that WiFi works absolutely fine until 4.1.2, whether it is stock or CM10 (I havent tried the other ROMs yet). I have faced this problem only from 4.2. It still exists on 4.2.2. Happens on all the ROMs I have tried till now including CM10.1 nightly as well as the stock factory image.
When the phone is sleeping, it seems to lose WiFi connectivity and when woken up, the WiFi bars is grey though it is full. If I am very lucky, it will turn blue automatically. Most of the times, I have to switch WiFi off and back on for it to connect properly.
Anyone knows the root cause for this? In case this has been discussed in any other thread?
Click to expand...
Click to collapse
have you posted this information over in any of the threads where the developers are working such as Cyanogen in an effort to bring this issue to the forefront for more visibility?
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Fabur87 said:
I have had those wifi problems with every android version and rom I had on my GNex as far as I can remember.
Sometimes it will be able to reconnect but sometimes I have to disable and re-enable wifi to get it back.
I too thought that it might have been my crappy router as I have had multiple problems with it over the years (some Linksys router).
This is really annoying because it won't receive any e-mails until I randomly decide to have a look at my phone. :/
Click to expand...
Click to collapse
trust me, I understand your frustration... some days, I can go almost all day without loosing wifi data throughput and other days it won't last 10 minutes without going to gray bars.
unfortunately, no one is sharing any fixes which tells me that no one has a good handle on the problem.
Same issue for me on stock Android 4.2.2. Leave WiFi on overnight and when I wake up its connected to WiFi but gray bars...
Sent from my Galaxy Nexus using xda premium
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
tgeery said:
so, I've read around here on the XDA forum about problems with wifi connectivity where we have full bars for wifi but they are gray and you are not getting out. many describe my situation but I've not seen any real solutions...
my problem is that I can connect to my wifi router without issue but then a random amount of time later, sometimes fairly quickly and sometimes it's hours later, I will pick up the phone and see full bars but they are gray and I'm not getting out. I can try opening a terminal window and pinging the gateway/dns servers and can't even reach the gateway.
things I have tried:
- turned off MAC filtering on the wifi AP
- switched from a 5 GHZ wifi on the AP to 2.4 GHZ net on the AP and vice versa
- manually set the phone wifi preference to one or the other (5 or 2.4)
- battery pull on the phone
- delete network settings for my AP and reconfigure
I have not yet tried a static IP config on the phone but I can easily try that... {edited to add} well, I tried static config and that didn't help at all...
one other tidbit of info, I have a work Blackberry with wifi and it never loses wifi connectivity so this is a problem unique to my Nexus.
I'm running Cyanogen 10.0.0-toro and no, I haven't tried a full wipe and reload yet.
thoughts or suggestions?
Click to expand...
Click to collapse
same thing happened to me on toroplus sourcery 5.1, after trying everything i could think of and talking to one of the devs, i finally did a fresh download of rom and gapps. wiped cache,wiped dalvik, factory reset, wipe system, deleted android folder off of storage then installed the fresh download of rom and gapps and its been working great for me since. hope this helps.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
aqcon said:
Can you elaborate on this? I've flashed 5 different modems and still get this problem... it happens to my cell service bars, as well. Would love to know what the cause is.
Click to expand...
Click to collapse
i just know ever since moving to a 4.2.2 kernel that has the 4.2.2 drivers my wifi has been stable. I know there was a post in the anarkia thread with the ak kernel that had the drivers. but i believe most any 4.2.2 kernel would have them implemented. i do have the newest bootloader and radio too. but i know as soon add i got the 4.2.2 drivers all issues were resolved wifi wise. of course i think if you have a 4.2.2 kennel you'll have them.
M3drvr said:
The update to 4.2.2 drivers have fixed all WiFi issues for me. For the first time since 4.1 I can now use WiFi optimization now. And WiFi is fully reliable.
Click to expand...
Click to collapse
I'm looking forward to that update - I've been watching the Cyanogen threads for when I think the 10.1 has matured enough to become my daily driver... good to know you've had positive results!
Temporary solution
me facing same issues , Solution would be to use an app called wifi fixer by zanish-g1 from the play store ...
it worked for me !! :good:

[Q] Another wifi bug thread, I've tried everything possible.

Hi!
I know there are plenty of threads about the wifi on this phone, I've read every one of them, posted in many places and have had no good outcome.
Here is my (lengthy) story.
Had annoying wifi bugs on stock 4.1.2, seemingly general lack of interest from the phone in connecting to wifi, but would generally connect after a reboot of both modem+phone+ disabling PSM (even then, not always )
6 months on stock go by, thought flashing a custom rom would fix everything and all would be well again, so I flashed PA.
An even more annoying bug showed up,
Turn wifi on > doesn't automatically connect, so I manually go to the wifi settings page and try connecting.
Before trying to connect - Full signal.
While trying to connect - Goes down to one bar while connecting > fails > then goes back to full signal.
Does occasionally connect, but it's rare. Rebooting both phone and the modem does nothing at all, seems to have a mood of it's own.
It's not just my wifi, but wifi at college too, other devices connect to the same access point just fine.
What would fix this? Will pretty much try most things now,I tried flashing NEAK too.
I don't have a data plan either, so my phone is basically useless without wifi, I've resigned to using my laptop all the time.
Thank you for reading this so far, I'd be thankful for ANY advice.
TL;DR :- Annoying wfi bug, tried every 'solution' I've heard of, nothing worked, never buying a Samsung again :crying:
(Attached images of the phenomenon)
UPDATE:- Just like stock, it will only connect if I am a foot away from the router, irrespective of how much signal I have. Even if I have a full signal elsewhere, it won't connect
dude u r running AOSP :silly::silly:
try TW Rom and see if the problem exists
yahyoh said:
dude u r running AOSP :silly::silly: try TW Rom and see if the problem exists
Click to expand...
Click to collapse
We meet again!
Like mentioned in the post, the only reason I flashed an aosp based ROM was in the desperate hope it'd rid the phone of its WiFi problem.
Thought a custom ROM would do what Samsung refuses to do.
Hope someone has a valid solution for this.
Sent from my Galaxy Note II using Tapatalk 2
Anyone?
I forgot I already had the range issue for quite a while, even on stock.
I had tried everything, including static IP, wps, and whatever else was stated to work.
Does anyone know of a working solution to this? Is this a hardware/software issue?
Sent from my Galaxy Note II using Tapatalk 2

Categories

Resources