Related
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.
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
Update 2012-10-02:
OK, I have eliminated my firewall from the equation: obviously I can't necessarily just whack the work's firewall without consequences. Nothing's blocked, and all services on the phone seem to work.
As for other devices: I dug up my old Nexus One (Gingerbread, stock), and upgraded my Transformer Prime to Jelly Bean. Both do not show the error in logcat, and neither have the battery drain issue. Just for kicks, I checked the version of the Google Services Framework on all three:
Samsung Galaxy Nexus: 4.1.1-398337
ASUS Transformer Prime: 4.1.1-438695
HTC Nexus One: 2.3.6
Wanna bet there's a bug in 4.1.1-398337 that got fixed in 4.1.1-438695?
Further update:
I also tried the following with no success:
Delete app data for Google Services Framework (NOT RECOMMENDED!)
Remove Google accounts from the phone.
Re-add Google accounts to the phone.
Update: 2012-10-04
I think I found a workaround. It looks like it's a domino effect thingy that happens here:
1) I've got a Netgear N600 ADSL/Wifi router at home. On my 2.4GHz radio, I set up two access points: one for my stuff and one for guests. I made sure to delete the guest account from all my Wifi equipment to make sure there's no "fighting" or "flapping".
2) It appears that the phone ignores the Wifi-'stay connected while sleeping' setting, or the radio is broken. When the phone goes to sleep, it disconnects from Wifi.
3) When the phone disconnects from wifi, the Google Services Framework lose connection: this causes the phone to wake up.
4) When the phone wakes up, Wifi gets re-established. This makes Google re-connect.
5) The phone goes back to sleep and we return to step #2.
This causes a LOT of wakeups, lost connections and other crap. Since the phone doesn't lose connection when it's awake, it's fricken difficult to debug. Also, it's NOT a signal quality issue. My phone can be right next to the access point and it wouldn't help.
So, could you guys try different access point settings at home? I've heard WMM, QoS and some of the protocols could cause the Galaxy Nexus's radio in Jelly Bean to go a bit wonky.
-- Jan Gutter
jangutter said:
Interested in solving a real puzzler? Then read on!
The patient: a rooted, otherwise stock Jelly Bean (JRO03C 4.1.1) Galaxy Nexus. Being used as an everyday phone (and a bit of development).
The symptoms: Excessive battery drain by "Google Services", but ONLY on my home Wifi network!
This is where things get weird: on 3G, on my company's work Wifi, and without network, the battery drain is absent. I can *reliably* cause Google Services to start hammering the wakelocks, and stop them, just by moving to a different Wifi hotspot. There's NO change in functionality: Google Talk, Play Store, and network access work exactly the same. Push messages seem to come in normally too, but I haven't tested that very well. There's no configuration change whatsoever.
More details: After installing BetterBatteryStats, I've gotten a better look at the wakelock draining the battery. After gathering stats for 25-30 minutes, the following wakelock is the top user:
Code:
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 7 m 47 s (467 s) Count:786 30.3%
So, I decided to check logcat for "GTalkService" messages, and see if there's a major difference between work (good) and home (bad).
Turns out I get a lot of the following at home, but not at work:
Code:
[ 08-15 17:36:02.719 709: 709 I/GTalkService/c ]
[[email protected]] connect: acct=1000000, state=CONNECTING
[ 08-15 17:36:34.461 709: 1177 E/GTalkService ]
connectionClosed: no XMPPConnection - That's strange!
This is repeated a LOT and looks like it correlates quite well with the wakelock.
I use the phone, and I would hate to wipe it completely: I would really like to get to the bottom of this.
First of all, I'm not 100% sure this is a Galaxy Nexus only problem. It might be Jelly Bean, or ICS, or whatever. Would you suggest I post on the Google Android bug list, where the crickets chirp, and major bugs disappear into a big Python black hole?
Thanks guys! If only for reading this far!
-- Jan Gutter
Click to expand...
Click to collapse
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Petrovski80 said:
Could it be that your home router's firewill is somehow blocking parts of GTalk traffic, causing it to continuously retry connecting?
Click to expand...
Click to collapse
Nope, I checked that: there's no firewall. At work there is, but it doesn't affect my phone (services are not affected visibly). Google Talk works fine in both situations.
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Exactly the same
cricka15 said:
any developments in this? have an s3 which is behaving similarly. my WiFi is always on as I'm usually near a hotspot at work home /gfs.gtalk_async wake lock showing up in better bat stats. been having battery drain issues for a while now and decided it was time to do some research.turned off pretty much every synch/auto backup app on the phone but still draining, not quite as bad, but still seems to struggle to stay asleep for very long!
Click to expand...
Click to collapse
Does anyone have solved this.. i have got exactly the same situation as Jan. No trouble at work but only at home.
Not affecting ASUS Transformer Prime
Nothing new here, except I also cross-checked with my ASUS Transformer Prime. There's no drain on it, and also no errors in logcat about GTalkService.
I'll post an update once I've checked my trusty old Nexus One out of storage, that'll happen next week, though.
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
sgtlange said:
Interesting note about the wifi. I only seem to get this problem during the week at work, on the weekends it doesn't happen that often. I get poor data connection at work and rely on the wifi instead. I'll try to not use the wifi for a day or so and see if the wakelock is reduced. Thanks for the tip, this has been a problem for a while now.
Galaxy s2 on Sprint
Click to expand...
Click to collapse
Just take note: in general Wifi uses a LOT less battery than 3G. A better test might be to disable Wifi AND sync.
Jan
some decent insightful ideas here. My S3 on official stock based custom has bad drain over wifi. My google services framework version is the 4.1.1-438695 which isn't affected in your case so it's not that.
Better battery stats at first put google maps as the wakelock so I realised it's location service was left on so I turned that off. Then BBS varies and shows different apps and what not causing wakelocks but the drain remains the same.
My router is an Asus with custom linux firmware Tomato with a robust plethora of functions. I updated it yesterday and put the settings back closer to default. I'll have to try disabling WMM and QoS settings as their both already on at the moment. Also the kernel developer i'm on to quote: "Made a change in wifi offload filtering to deny muticast packets but allow multicast DNS packets."
After leaving wifi on last night the drain still remains at about 10% per 3 hours. Compared to before it used to be almost 15% per 3 hours. BBS doesn't show wlan_rx_wake as the top wakelock as most common before as that's down to running for 8 minutes in 9 hours rather than the top around 45 minutes. Instead battery-monitor is the top at a little over half an hour in the 9 hours. Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Infy_AsiX said:
Googling battery-monitor shows little useful information but I assume it's like before where Wifi is waking the device and something OS related that turns on with it gets given the wakelock status although its not the trigger.
Click to expand...
Click to collapse
Have you tried disabling the WiFi Power Save Mode on the S3? From this article:
http://www.s3forums.com/forum/galaxy-s3-general-discussion/1329-wifi-tip.html
1. Open up the Galaxy S3 phone dialer
2. Dial *#0011#
3. Look for the “ServiceMode” screen and press the left menu button
4. Select “WiFi”
5. You should see that the “WiFi Power Save Mode” button is “ON” – turn it “OFF”'
My colleagues with the same phone has serious battery drain until they use that.
Infy_AsiX said:
I'll have to try disabling WMM, QoS, auto-sync and gtalk and see how I go. Hopefully you're right about it being wifi disconnect related and can be fixed.
Click to expand...
Click to collapse
I seem to recall that the Google framework sends/receives a keep-alive packet once every hour or so. LOTS of stuff in the Android framework keep TCP connections open from the server side because otherwise the service provider just kills them. Blame stateful firewalls.
What could be happening here is that the WiFi chip offloads a number of these functions from the main CPU: i.e. it's got a simple TCP offload stack that just queues data for the main CPU to wake up. If the WiFi chip receives a keep-alive TCP packet with no payload, it doesn't bother to wake up the CPU and just absorbs it. If the WiFi chip goes to sleep, rather, it never receives these, the connection dies and the CPU needs to wake up on timeout and re-establish everything (eating battery in the process). It's paradoxically cheaper to keep the WiFi chip running on full power, than to let it go to sleep. This is pure speculation, and only one of many scenarios that might fit the facts.
The S3 has the *option* to change the WiFi sleep-mode from aggressive (default) to a value that lets the entire system use less battery. The Galaxy Nexus doesn't: which means that it may, or may not have the sleep-mode built in. In any case, it seems my router can remotely trigger disconnects when the main CPU is off, and by switching settings on it, I managed to perform a workaround. Unfortunately the Galaxy Nexus (on Jelly Bean, at least) seems to have a serious bug in this respect, and other people are not so lucky: http://code.google.com/p/android/issues/detail?id=35352
It seems that the core issue (WiFi disconnect), causes a knock-on effect, raising Google Services Framework, Android OS and potentially anything that syncs's battery profile.
Jan
Getting good drain now 1% an hour compared to 3%. Seems setting WMM to auto rather than enabled in tomato fixed it. The night before I had it disabled as well as QoS and it was bad as well. I will test further to be certain what's the scenario.
I've got a second S3 that's been suffering as well. Having two to test makes testing much faster. The service menu power save mode off didn't help. It caused strange disconnects with WMM in all states. S3 wifi menu would state poor connection and wouldn't reconnect. Note the S3 already has strange disconnects to begin with I find but in this case it sometimes wouldn't reconnect. Also restarting the phone resets the power save mode to enabled.
Can't find any information on a difference between enabled and auto in tomato WMM. I'll be sure to keep testing.
Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
New Google Services Framework
Hey guys,
looks like Google Services Framework got a version bump on the latest Galaxy Nexus update: it's now listed as version 4.1.2-485486
This is for JZO54K (4.1.2).
It could be that they've fixed the knock-on effect (but the core issue is likely the same, since the radio code is apparently exactly the same).
Jan
I have this same wakelock on my evo 4g lte. Same log error exactly. Only on my works wifi. Problem is eliminated when running a Vpn on the phone. Only caveat Is all the free vpn services seem to disconnect after a period of inactivity.
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Rawi666 said:
I know this is an old topic but I had the same drain (30% overnight) on my Galaxy S2.
After weeks of searching and trying different things I found the solution.
Change DTIM value in your router configuration from 1 (default) to 255.
This value is usually in Advanced->Wireless tab on most routers.
Now my phone uses 2% battery overnight with wifi on, sync on instead of 30%.
Click to expand...
Click to collapse
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
SpinTX said:
I tried this and got weird results. My phone couldn't connect to my network, but my tablet could (GT 7510) which also experiences the drain issue. How did you come up with the value 255? Any other value I can try? Thanks
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Try lowering this value to 10 or 8 and see if it helps.
Rawi666 said:
Try lowering this value to 10 or 8 and see if it helps.
Click to expand...
Click to collapse
Thanks, will give it a shot. Also, because of your post, I discovered that toggling wifi on and off stops Google Services from draining. It will still drain, if your wifi is set to turn off, when the device sleeps. I really think you hit the nail on the head, discovering the source of the problem. It's an issue I have been trying to fix for a long time and your post at least got me to toggling the drain. So thanks again!
Sent from my SGH-T999 using xda premium
Would love to he root cause of this... I had the same problem on my s3 and now on the s4.with and without custom roms etc. The problem only is work, and I'm putting it down to some service that the work firewall or something blocks... Only solution I've come up with is turning off the wifi when I'm at work.. Else I get in excess of 15min /hour of wakelock.
All apps etc. Up to date, sync on/off, no difference, all "location" settings turned off.
I give up.
Wifi signal strength!
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
keltickal said:
Whatever Google did to cause a variety of wakelock problems, having a strong wifi signal seems to solve them. Apparently, wakelocks occur when there are unreliable connections to Google's servers.
Kal
Click to expand...
Click to collapse
A friend with the nexus 4 and same problem told me to try disabling Google hangouts (formally talk).. Apparently it keeps refreshing itself once ur signed in (and it signs in automatically)... Will experiment tomorrow at work where I get the problem.
Sent from my GT-I9500 using xda premium
Both my data and WiFi have been acting very strange the past week. Both services will show me as connected but I will only get the upload arrow showing on each indicator and then sometimes the icons just go gray. It has been happening very often and I have changed both my ROM and kernel on clean installs and I still have the same issue. Any help would be appreciated.
Bump. Still have the problem.
Flashing back to stock should work
Posting your basics usually gets you better answers
Sent from my Galaxy Nexus using Tapatalk 2
czonin said:
Both my data and WiFi have been acting very strange the past week. Both services will show me as connected but I will only get the upload arrow showing on each indicator and then sometimes the icons just go gray. It has been happening very often and I have changed both my ROM and kernel on clean installs and I still have the same issue. Any help would be appreciated.
Click to expand...
Click to collapse
I started a thread here on a topic where my wifi and signal bars turn gray and the phone doesn't have data connectivity any more. sometimes this happens a dozen or more times a day and sometimes once or twice.
one response in that thread indicated that 4.2.2 made a positive impact on the problem.
I've been searching for a definite fix for this data/WiFi issue to no avail. I'm not entirely sure of when this issue began to occur but my phone (Toroplus) constantly loses WiFi signal. By losing signal I mean WiFi will turn off and on all by itself. And yes, WiFi sleep policy is set to stay on always. This issue alone made me go back to stock only to find the WiFi issue is present there too. I've also ruled out my router as the culprit. Im suspecting this is a Google issue. By the way, I talked to a sprint store employee who owned a galaxy nexus and after a few minutes of playing with his phone, which was completely stock and never rooted, I noticed his WiFi connection would turn off and on all by itself too. Any insight from anyone with knowledge to this would be appreciated.
Wi-Fi optimization off. If that does not fix it, I dunno.
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Wi-Fi optimization off. If that does not fix it, I dunno.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion but that doesn't fix it. Are you not having this issue? What's your setup? What ROM do you use? I've basically used all of them and it never goes away. I'm thinking of going to the HTC One when it's released just in case it's a Samsung issue.
I have also experienced this problem, especially at work where the network uses some WPA Enterprise variant. I've digged through logcats and can't find the problem either. A few Google Code forum posts talk about a possible bug introduced by network adapter manufacturers, or wpa_supplicant configuration issues. Haven't found a workaround yet, so I had to go back to 4.1.2, which seems to be stable.
More info here:
http://code.google.com/p/android/issues/detail?id=34212
http://code.google.com/p/android/issues/detail?id=40023
The more I read on this subject the more I come to realize this is not specific to a certain device. The only common denominator that jumps out at me is jellybean. Seems like the issue is with Google, not hardware. Sucks that such a basic feature is not reliable out of the box. At least now I can understand why my buddy calls Android "buggy". Hopefully this is fixed sometime in the near future.
I was just wondering if anybody has been having this issue. After successfully locking onto satellites for GPS for navigation, if I turn off maps when I reach my destination, it requires a reboot until I can use GPS again, it only updates once every few minutes. Haven't done much testing on it since I was on a highway going 80 when I noticed
Sent from my Nexus 7 using Tapatalk HD
Flippy125 said:
I was just wondering if anybody has been having this issue. After successfully locking onto satellites for GPS for navigation, if I turn off maps when I reach my destination, it requires a reboot until I can use GPS again, it only updates once every few minutes. Haven't done much testing on it since I was on a highway going 80 when I noticed
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Same issue here. I think its wide spread but only a few of us use the GPS function
Sent from my Nexus 7 using xda app-developers app
yup
Happened when i pushed the second update (twice). I'm hoping for a fix soon.
Same here!
Same here... even exchanged for a new device from 16 to 32gb model and still the same issue. Works for about 10-30mins then locks me in the location completely.
Moderator should merge threads.... issue is duped on XDA
Happened to me while playing ingress, I had to reboot
Sent from my Nexus 7 using Tapatalk 4 Beta
This seems to be a legitimate issue. Has anyone reported the bug to Google?
Vanhoud said:
Happened to me while playing ingress, I had to reboot
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
HERES THE FIX!!
I had this very same issue, and found a resolution for it (can't remember the source now)
After taking both system updates and rebooting, it is necessary to hard reset the device. Upon the initial boot, you must leave all options checked but the following -
Backup and Restore options (you can turn on after the initial setup is finished from options)
there are three location options, one being new to 4.3 and what I believe to cause this - it mentions the ability for location to be grabbed when the screen is off. You must diable this option.
Finish installation, and then you will have properly working GPS.
Here's how I'm quantifying that - before when I was in the exact same boat as those in this thread, I would open GPS test, and I could see 7 or 8 sats in view, but it wouldn't lock. Or if it did, it would work for a short period of time, and then bomb out. I drove around the city for a few hours yesterday using the GPS so we're near and dear now to each other.
After doing all this - you will IMMEDIATELY see 20 sats available upon launching gps test and then almost immediately get full lock and keep it that way.
Was a pain that I had to clear everything, but now GPS is working as I would expect it, and I've not had any issues getting full lock, even in my basement.
Hope this helps!!
I tried to duplicate the problem you describe, but was not able to.
Here is what I did:
- Launch Maps application for the first time.
- Accepted the terms of service and enabled location services access, including Wi-Fi.
- Got location via Wi-Fi, then pinpointed the location via GPS.
- Back to home screen -> Settings -> Apps.
- Maps was not running, but I went into Maps under the all apps view and force closed it.
- Back to home screen.
- Launch the Maps application again and I had an accurate location via GPS in less than 10 seconds.
I repeated this procedure again with the same results. I then disabled Wi-Fi location assistance so that only GPS was available. Repeating the tests twice again and I still see the same results. I have no problems getting a good location lock quickly.
I am running the stock firmware, build JSS15J, and Maps v7.0.1.
I am happy to test again if somebody having this problem can provide specific information regarding their test procedures and results.
mrc13an said:
I tried to duplicate the problem you describe, but was not able to.
Here is what I did:
- Launch Maps application for the first time.
- Accepted the terms of service and enabled location services access, including Wi-Fi.
- Got location via Wi-Fi, then pinpointed the location via GPS.
- Back to home screen -> Settings -> Apps.
- Maps was not running, but I went into Maps under the all apps view and force closed it.
- Back to home screen.
- Launch the Maps application again and I had an accurate location via GPS in less than 10 seconds.
I repeated this procedure again with the same results. I then disabled Wi-Fi location assistance so that only GPS was available. Repeating the tests twice again and I still see the same results. I have no problems getting a good location lock quickly.
I am running the stock firmware, build JSS15J, and Maps v7.0.1.
I am happy to test again if somebody having this problem can provide specific information regarding their test procedures and results.
Click to expand...
Click to collapse
It was showing an accurate location in Maps until I started to drive. Once I sped up, it showed me where I was ~15 miles back
Sent from my Nexus 4 using Tapatalk 2
kmartburrito said:
HERES THE FIX!!
I had this very same issue, and found a resolution for it (can't remember the source now)
After taking both system updates and rebooting, it is necessary to hard reset the device. Upon the initial boot, you must leave all options checked but the following -
Backup and Restore options (you can turn on after the initial setup is finished from options)
there are three location options, one being new to 4.3 and what I believe to cause this - it mentions the ability for location to be grabbed when the screen is off. You must diable this option.
Finish installation, and then you will have properly working GPS.
Here's how I'm quantifying that - before when I was in the exact same boat as those in this thread, I would open GPS test, and I could see 7 or 8 sats in view, but it wouldn't lock. Or if it did, it would work for a short period of time, and then bomb out. I drove around the city for a few hours yesterday using the GPS so we're near and dear now to each other.
After doing all this - you will IMMEDIATELY see 20 sats available upon launching gps test and then almost immediately get full lock and keep it that way.
Was a pain that I had to clear everything, but now GPS is working as I would expect it, and I've not had any issues getting full lock, even in my basement.
Hope this helps!!
Click to expand...
Click to collapse
Thanks, I'll try this when I get back to a decent data connection
Sent from my Nexus 4 using Tapatalk 2
I was the source #1, AND #2 although I thought this fixed it, the issue came back! Its like a memory error with the gps driver and or buffer with a overstack flow of data and it either crashes it so you loose gps functions, or locks it up so its searching but never locks. Seems as if its software and android 4.3 or google system service or framework issues. Same problem with older S4 chipsets and jellybean. Google fixed that by updating system files for jelly bean 4.1.2 and 4.2.x. Also the new maps could be the culprit as well since it was updated to a completely new version.
kmartburrito said:
HERES THE FIX!!
I had this very same issue, and found a resolution for it (can't remember the source now)
After taking both system updates and rebooting, it is necessary to hard reset the device. Upon the initial boot, you must leave all options checked but the following -
Backup and Restore options (you can turn on after the initial setup is finished from options)
there are three location options, one being new to 4.3 and what I believe to cause this - it mentions the ability for location to be grabbed when the screen is off. You must diable this option.
Finish installation, and then you will have properly working GPS.
Here's how I'm quantifying that - before when I was in the exact same boat as those in this thread, I would open GPS test, and I could see 7 or 8 sats in view, but it wouldn't lock. Or if it did, it would work for a short period of time, and then bomb out. I drove around the city for a few hours yesterday using the GPS so we're near and dear now to each other.
After doing all this - you will IMMEDIATELY see 20 sats available upon launching gps test and then almost immediately get full lock and keep it that way.
Was a pain that I had to clear everything, but now GPS is working as I would expect it, and I've not had any issues getting full lock, even in my basement.
Hope this helps!!
Click to expand...
Click to collapse
kmartburrito said:
I had this very same issue, and found a resolution for it (can't remember the source now)
After taking both system updates and rebooting, it is necessary to hard reset the device. Upon the initial boot, you must leave all options checked but the following -
Backup and Restore options (you can turn on after the initial setup is finished from options)
there are three location options, one being new to 4.3 and what I believe to cause this - it mentions the ability for location to be grabbed when the screen is off. You must diable this option.
Click to expand...
Click to collapse
I had done a hard reset as well after applying the initial updates. I left backup enabled but disabled restore during the setup process and disabled all three location features as well.
skyhawk21 said:
I was the source #1, AND #2 although I thought this fixed it, the issue came back! Its like a memory error with the gps driver and or buffer with a overstack flow of data and it either crashes it so you loose gps functions, or locks it up so its searching but never locks. Seems as if its software and android 4.3 or google system service or framework issues. Same problem with older S4 chipsets and jellybean. Google fixed that by updating system files for jelly bean 4.1.2 and 4.2.x. Also the new maps could be the culprit as well since it was updated to a completely new version.
Click to expand...
Click to collapse
Yes you were, I remember your username now. Thanks skyhawk21! You resolved this for me. I used my N7 for a few hours in the car yesterday, and it was spotty and crappy in clear weather for a while, I did a reset in the car like you mentioned, and everything now has been working solidly since. Thanks again.
The last part is sad to hear. I however have used it for several hours straight with no issues, so I'm hoping it stays strong.
I am confused, so should I reset mm y tablet? Will that actually fix GPS?
Sent from my Nexus 7 using xda app-developers app
It will fix it for awhile but the issues creeps back up.... good luck this new nexus 7 is turning to be into a nightmare, flaky gps and flaky touch screen issues on two fo them now!
As long as you only use google maps it seems to work ok.
Once you start using other GPS apps (GPS Test, Gas Buddy, Google Earth) the problem shows up eventually.
It might have to do with multiple apps accessing GPS, but that is just a guess.
I wouldn't bother factory resetting (for the N7 2013 GPS issue). Reboot has always allowed the unit to get locks again (for me) It feels like an OS or driver problem.
I found a posting on AndroidCentral about the same issue. According to one of the posters, the issue is known by Google and an OTA should be pushed out soon for it. I just hope its true because I'm pretty dependant on my N7 for finding my way around town
http://forums.androidcentral.com/google-nexus-7-tablet-2013/300566-gps-problems-nexus-7-2013-a.html
Sent from my Nexus 4 using Tapatalk 2
I must be lucky, I've used it for several more hours, and still rock solid GPS at all times.
hmmmmm gps wasn't locking earlier then decided to do a soft reset, now it's working. I just have to try it later when i drive home and see what's up.
Hello everyone,
I hope all the pixel 6 pro owners are not suffering from high blood pressure lol
I've bought the pixel 6 pro few months ago and kept hoping it'd be better by updates. and indeed it improved a lot with time except one annoying issue: The insane mobile network's battery usage.
As you can see in the screenshot, it takes more than 30% of my battery to just be idle on LTE with data off. not even a game uses that much of power.
I contacted Google, they asked me to return it but since I live in Morocco it's impossible due to the insane customs' taxes, so I just have to live hoping they'd fix it with an update.
what I noticed is that this issue isn't present in custom roms. I also noticed that many people are still facing this issue to this day.
I reported the bug many times using the feedback app in the QPR beta yet got no replies.
Take out the trash, Facebook.
Try a network reset.
Find the apps sucking the bandwidth. All cloud apps are prime suspects. A logging firewall would be helpful for this. Firewall block all apps that don't need internet access.
Disable all Google, app and carrier feedback.
Malware is also a possibility.
Finally factory reset if you suspect malware and/or can't track down the cause(s). Be aware it may reoccur so it's always better to find the root cause when possible.
blackhawk said:
Take out the trash, Facebook.
Try a network reset.
Find the apps sucking the bandwidth. All cloud apps are prime suspects. A logging firewall would be helpful for this. Firewall block all apps that don't need internet access.
Disable all Google, app and carrier feedback.
Malware is also a possibility.
Finally factory reset if you suspect malware and/or can't track down the cause(s). Be aware it may reoccur so it's always better to find the root cause when possible.
Click to expand...
Click to collapse
I tried literally everything. Tried a clean install with no apps installed, still the same. Tried disabling adaptive connectivity and "mobile data always on", still the same problem. LTE always drains battery.
I even tried deleting modem partitions then reinstalling the stock rom yet the issue persists. Can't seem to get rid of this issue.
mohamed.sakhiri said:
I tried literally everything. Tried a clean install with no apps installed, still the same. Tried disabling adaptive connectivity and "mobile data always on", still the same problem. LTE always drains battery.
I even tried deleting modem partitions then reinstalling the stock rom yet the issue persists. Can't seem to get rid of this issue.
Click to expand...
Click to collapse
That sucks. Maybe a hardware issue... I know that's the last thing you want to hear. It may be an antenna problem rather than the mobo.
Does it get better with the data on? Have your carrier do a network reset on their side.
Double check all configurations for the mobile data. Try clearing the data in the SIM toolkit app if it has that. Not sure how the SIM is managed on that maybe it's misconfigured. Try temporarily disabling Google play Services and see if that helps.
If you have a good local shop sometimes a second pair of eyes can spot the issue.
blackhawk said:
That sucks. Maybe a hardware issue... I know that's the last thing you want to hear. It may be an antenna problem rather than the mobo.
Does it get better with the data on? Have your carrier do a network reset on their side.
Double check all configurations for the mobile data. Try clearing the data in the SIM toolkit app if it has that. Not sure how the SIM is managed on that maybe it's misconfigured. Try temporarily disabling Google play Services and see if that helps.
If you have a good local shop sometimes a second pair of eyes can spot the issue.
Click to expand...
Click to collapse
I don't think it could be a hardware issue since I tried some custom roms from xda and there was no drain. Network usage was limited to 2%.
I really don't know what's going on with this phone lol. I'm not the only one, there are some people online complaining about the same issue.
mohamed.sakhiri said:
I don't think it could be a hardware issue since I tried some custom roms from xda and there was no drain. Network usage was limited to 2%.
I really don't know what's going on with this phone lol. I'm not the only one, there are some people online complaining about the same issue.
Click to expand...
Click to collapse
You need to find what's causing it then. Perhaps a system apk is endlessly polling another service or the internet. Make sure it's not a rootkit... Android 12 had a huge hole that Google plugged earlier this year. It doesn't apply to me so I'm not up to speed on it. Try flashing with the latest stable stock rom or simply go with what works.
It maybe they had to substitute a smaller chipset or component during a production run due to supply issues and the current firmware inadvertently wasn't configured properly for it. If so eventually they will correct the firmware more than likely. Samsung is notorious for doing that, Google probably does it too.
Fun times...
mohamed.sakhiri said:
Hello everyone,
I hope all the pixel 6 pro owners are not suffering from high blood pressure lol
I've bought the pixel 6 pro few months ago and kept hoping it'd be better by updates. and indeed it improved a lot with time except one annoying issue: The insane mobile network's battery usage.
As you can see in the screenshot, it takes more than 30% of my battery to just be idle on LTE with data off. not even a game uses that much of power.
I contacted Google, they asked me to return it but since I live in Morocco it's impossible due to the insane customs' taxes, so I just have to live hoping they'd fix it with an update.
what I noticed is that this issue isn't present in custom roms. I also noticed that many people are still facing this issue to this day.
I reported the bug many times using the feedback app in the QPR beta yet got no replies.
Click to expand...
Click to collapse
Unless you "have" to use the facebook app, which is a battery hog,
just go to m.facebook.com, the mobile site. Less battery drain and when you close
your browser, there isn't any app running that you don't know of.
Forget that percentage number, over the various updates I have had it be anywhere from 5% to 50% and it has made absolutely zero difference to how long the phone lasts during the day.
Are you actually not getting through a day on the battery? If you are then forget about that number as its not really telling you anything.
The mobile network drain is due to the Samsung radio chip they chose, it was known to be a battery hog even 4 years ago. They use a different, more efficient over in the Pixel 7 and 7 Pro