I have been suffering from some massive battery drain the last few days and after some investigation I found out that the app "Bump" now uses GPS, and does so constantly. It was using up almost as much battery as the screen.
Anyhow just thought I would post a heads up for anyone else who might have it installed.
Hi, this is Dave from Bump. We had a bug in version 2.0.0 of Bump that would cause location services to be accessed at the wrong time on certain phones. This has been corrected in the latest version of Bump (2.0.2).
If you are still seeing problems, please let us know!
-dave
Still a problem
I just uninstalled Bump because I couldn't figure out what was keeping my GPS on, and noticed Bump was using 33% of my battery.
I only keep it installed in case I ever run into anyone else who uses Bump. hasn't happened in three years, guess it's not a big problem _for me_.
Might be for Bump.
Related
Hi All,
I am putting this here in the Q&A section because I don't have any posts yet and I can't put it in the dev section. I'm running CM10 nightlies on the Samsung Galaxy S2 Skyrocket and I'm currently on 10/18. What I've noticed today, and I haven't found any information on it yet.
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
From what I've read so far, this has been an issue in other CM10 nightlies for other devices but I'm not sure if it has been reported yet for this one. I know to fix it, I can do a reboot but just curious if it is being looked at.
Thanks and apologies if it is listed elsewhere - i did search and couldn't find it.
andygens said:
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
Click to expand...
Click to collapse
I have the same thing, although it doesn't seem to be burning through the battery like actually having GPS on. If it helps, I do have tasker automatically shut off GPS when the screen is off so I'm not sure why it would be running in the background.
andygens said:
Hi All,
I am putting this here in the Q&A section because I don't have any posts yet and I can't put it in the dev section. I'm running CM10 nightlies on the Samsung Galaxy S2 Skyrocket and I'm currently on 10/18. What I've noticed today, and I haven't found any information on it yet.
This morning I used my maps and GPS to get around town a bit and then came to work. When I looked at BBS a few hours later I noticed a kernel wakelock on PowerManagement. After some investigation, I learned I needed to look into partial wakelocks and found a corresponding wakelock on the GPSLocationprovider which I imagine is from my use this morning.
From what I've read so far, this has been an issue in other CM10 nightlies for other devices but I'm not sure if it has been reported yet for this one. I know to fix it, I can do a reboot but just curious if it is being looked at.
Thanks and apologies if it is listed elsewhere - i did search and couldn't find it.
Click to expand...
Click to collapse
Check the better battery stats thread there is a way to fix that and this has already been answered please use search
Sent from my SGH-I727 using xda premium
crashpsycho said:
Check the better battery stats thread there is a way to fix that and this has already been answered please use search
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
I have read most of that thread and have been unable to find a solution which works for me.
Based upon my reading in other device threads, some people get this wakelock if they use GPS for anything and then attempt to turn it off. For example, if you turn on GPS, use a maps application for a short while, close the maps application and turn off GPS, the wakelock is born. Even if you kill any active maps services, it will still be there.
I am under the impression that a flavor of this issue can be caused by location aware apps such as Google Maps and Facebook, but the issue where it is constantly active for hours on end, is perhaps an inherent issue in the 4.0.x and 4.1.x, kernels. I have found many people complaining of this issue on many different flavors of roms (ICS / JB) and hardware (HTC, Samsung, LG).
One user's solution was to never turn GPS off, but will continue to look for a better solution.
Its Google now, turn it off and see if it Persists in bbs
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
First there is a thread in general section devoted to wakelocks. Please search.
Second never post in dev section unless you are dropping a ROM kernel or mod.
Sent from my SGH-I727 using Tapatalk 2
Even without Google Now enabled I can recreate this wakelock without fail. GPS on, use GPS, GPS off, wakelock materializes.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
Unfortunately there does not seem to be any info about this particular phenomena in the threads that I have found.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Sorry to resurrect an old thread. Has anyone who has had this issue resolved it?
Like promiseoc, I can get the wakelock every time I use the gps, and shut it off later. So far, I've tried the fix in bbs using Gemini Manager and disabling latitude and all location services. I'm also not signed into google now. I use Latitude occasionally, but make sure to shut it off when not in use.
So far, I've had this problem on each of the AOSP-based roms I've tried (CM10, Liquid, and Slim). Great roms, all of them, but any other suggestions on what else I can try?
jedah said:
Sorry to resurrect an old thread. Has anyone who has had this issue resolved it?
Like promiseoc, I can get the wakelock every time I use the gps, and shut it off later. So far, I've tried the fix in bbs using Gemini Manager and disabling latitude and all location services. I'm also not signed into google now. I use Latitude occasionally, but make sure to shut it off when not in use.
So far, I've had this problem on each of the AOSP-based roms I've tried (CM10, Liquid, and Slim). Great roms, all of them, but any other suggestions on what else I can try?
Click to expand...
Click to collapse
I guess we are just supposed to keep GPS on and forget about it. I don't like to because of paranoia but it seems like that's the fix. Happens across a library of devices.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
promiseofcake said:
I guess we are just supposed to keep GPS on and forget about it. I don't like to because of paranoia but it seems like that's the fix. Happens across a library of devices.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Oh well. If that's the only solution, so be it. I was always under the belief that drained battery, but then again I've never tested how much it does. May not be a big deal. Thanks.
The wakelock goes away if you reboot and I think it also does if you plug your phone into a charger even briefly. Of course, ensure it is not a charger that causes the vbus_wakelock.
phoneturf said:
The wakelock goes away if you reboot and I think it also does if you plug your phone into a charger even briefly. Of course, ensure it is not a charger that causes the vbus_wakelock.
Click to expand...
Click to collapse
Goes away with reboot but then you lose battery whilst media scanner runs. I now leave GPS on and forget about it. That is interesting about the charger, I will have to check it out.
promiseofcake said:
Goes away with reboot but then you lose battery whilst media scanner runs. I now leave GPS on and forget about it. That is interesting about the charger, I will have to check it out.
Click to expand...
Click to collapse
Any word if this will be worked on in the new update?
If you leave GPS enabled it's a non-issue.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Sorry to revive, but I have this even with GPS always disabled.
Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S
Starting today, my phone has been giving me notifications about a sign in error to my Google account. It's happened about 5 times so far, all just today. My phone is completely stock. Is anyone else experiencing this issue? Are Google servers having some issues?
I think Google was having problems this morning. Maybe they still are.
Sent from my ADR6300 using xda app-developers app
Okay thank you
Same here. I just flashed the latest Cyanogen mod nightly so I thought it was the ROM.
Sent from my SCH-I535 using xda app-developers app
Been getting that error like crazy today. I'm guessing it's cleared up though? Haven't seen it in a minute..
Just started getting it a few hours ago, completely stock.
I wonder if they're just making system wide changes in waves, you guys are getting the errors much later than me, I haven't gotten one in hours now
I am getting as well yesterday and today with 2 different ROMs so I believe its a Google issue
Confirming as well, just got one to be exact
I've been getting the log in error periodically for over a day now
It's been happening to me since last night, and I'm on a completely different phone. In searching for a solution that DIDN'T involve starting from scratch by reflashing a ROM (literally hours of work to retweak and restore everything, titanium backup and all) I found another thread regarding this issue on a totally different phone forum of xda.
I myself am running Now for ICS on my One S running Viper Rom. From this thread, with no details given I can only assume most of you are using Verizon galaxy S 3s?
But anyways. In the other thread it seemed the consensus that the issues were related to Google now. Some users reported some success from logging out of their Google plus then logging back in again. That resolution has provided me no dice so far.
Most users reporting the issue said that their google now was even not working at all. Have any of you tried google now while encountering these issues? Does it work or does it seem to be malfunctioning? Mine (along with the rest of my google apps) all seem to be working fine still. =L
Is anyone on here using a phone other than the Verizon GS3? what roms are involved? Anyone encountering this issue NOT have google now installed to their phone?
Hoping to narrow the details down in the interest of gaining a little more knowledge about this specific occurrence.
This happened to me a couple months ago, and I was running GNow for ICS back then too. Can't remember but I'm fairly certain the issue worked itself out. But its obnoxious ass all hell. Been getting the notification once every 5 minutes whenever I dismiss it, and its been prevalent since last night! It's starting to severely irritate me lol.
Sent from my HTC One S using xda premium
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
FIXED!!! (for me at least)
boojay said:
I'm on an HTC Amaze running a custom Speed Rom. My battery ran out during the error message and my phone wouldn't turn on again. Luckily I had a nandroid from earlier in the month, but I still lost 3 weeks of data on my phone, not the end of the world, but certainly a nuisance. I also recall having this happen a few months ago and the issue resolved itself so my guess is that it's an issue on Google's side. I am, however, disappointed that it's taking so long. A few hours is fine, but over a day and counting?
Click to expand...
Click to collapse
Tell me about it. Im seriously starting to lose my sanity over this.
A couple users said to disable Google Account manager (via settings > apps) as a temporary solution, but for me doing so disabled all of my g apps entirely so that's definitely not a good work around.
I spotted a thread in the amaze forum involving a speedrom issue (http://forum.xda-developers.com/showthread.php?t=1968141) and he seemed to think it was related to his Rom. Seemed that doing what he did resolved it, but given the prevalence of this issue accross as many devices as it has and as many roms as it has, I'm inclined to think that the issue coincidentally resolved itself while he was busy flashing lol
Regardless... I'm so desperate to stop being pestered by this issue that imma bout to wipe cache and dalvik cache and see I'd that doesn't fix the issue for me as well. I'll report back when I know one way or the other.
Edit - cache and dalvik cache wiped. Crossing my fingers. Only time will tell... Or not. Got the error whilst I was writing this paragraph lol. No dice
Edit 2 - interesting. I've had the sports card running for a couple days now. It kinda updated but didnt seem to be working 100%. Whether its related or not, im not sure but simultaneous to this behavior I noticed that the search function didn't work. Didn't open chrome up at all so I'd simply have to type my search into chrome directly. I just disabled the sports card and my search function is working again all of a sudden. Haven't gotten the error yet, if this pans out that might have been the source of my problem. Keeping my fingers crossed.
Edit 3 FIXED!!!!! (for me at least). It's now been an hour and 35 minutes since I disabled the sports card. My now search has been working for the first time in days since the instant I disabled it and the error free hour and 35 minutes is by far the longest span of time I've achieved in the last 24 hours (was getting the error within 5-10 minutes of each time I dismissed it previously). Anyone else encountering this issue have the Sports card enabled? Try it, see if it solves the issue for you as well and share with the class =)
Edit 4 - I guess it was a passing moment nonetheless. Got more errors.in the last 15 minutes after about 2 and 1/2 hours of not seeing it at all. Damn this is effing ridiculous
Sent from my HTC One S using xda premium
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
boojay said:
Yeah AndroidAutobot, still issues here. It's really starting to get on my nerves. Kinda wish there was a way to disable specific notifications because it's not really hindering my usage. My only concern right now is draining my battery.
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
I just went into the phone settings then account. Removed my gmail account then resign in and I have got the error all night
Sent from my SCH-I535 using xda premium
AndroidAutobot said:
Yeah. I gave up on it last night and figure with it being as prevalent as it is, it absolutely has to be server related and can't be anything Rom/system related by any means. On a positive note Im pretty sure I havent seen it in 3-4 hours so maybe they've finally fixed it. This is day 3 for me so I sure hope they did
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
boojay said:
Ditto, it's been a couple of hours since I've received the error. I think we have it beat!
Swyped from my Android/iPhone Killer
Click to expand...
Click to collapse
Yep. It's been gone all day for me. At least it was persistently annoying enough this time around to actually remember that it.resolved.itself.I'd.there's ever a next time this comes up. Knocking on wood that It won't ever again of course =)
Sent from my HTC One S using xda premium
I recently switched to VZW and got the SGS3 (100% stock so far)...great phone except for one issue. Twice now the battery has completely crashed....going from fully charged before bed to full draining and turning off the phone while I slept.
I assumed it was an app causing the problem. At first I thought it was the game X-Plane. However, last night it happened again and I had not played any game. The one app I used immediately before both battery crashed was RadarScope. I'm surprised it would somehow cause the battery to crash after using it though because before going to bed I always use the ICS task killer to close all unnecessary apps.
Please help me diagnose these extreme crashes. I don't see how it could be RadarScope because I close it before going to bed, but that's the best explanation I have so far.
No one has any idea? I thought it may have been a quirk with the stock kernel interacting with certain apps, but maybe it's simply a bug in RadarScope or one of my other apps.
TeeJay3800 said:
No one has any idea? I thought it may have been a quirk with the stock kernel interacting with certain apps, but maybe it's simply a bug in RadarScope or one of my other apps.
Click to expand...
Click to collapse
Download https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats and it'll tell you what you need to know.
Sent from my SCH-I535 using xda app-developers app
My wife got a moto g a few weeks ago on boost mobile - such a nice fast fluid and stable phone, almost the same as the nexus 4.
The problem is that last week it's begun shutting itself off randomly for no reason.
It is fully updated, stock, not rooted, it has no unusual apps installed and still it randomly turns itself off - I'm not sure if just at random while it's sleeping or also during calls, I will double check, but a Google search told me that it isn't a common problem and therefore there was no common solution.
We are not developers and don't know how to do anything crazy with bootloaders or the kernel or anything, so please bare that in mind - is there any simple solution that anyone could suggest that we try?
Thanks so much in advance!
It powers off cause of a safety mechanism to prevent it from damaging phone. Idk what causes it this happened to me once
Sent from my XT1034 using xda app-developers app
Thanks... Any suggestions for a fix?
--------------------------------------------
My right hand took a break long enough to write you this message, and you should be grateful for that.
Hey all, I searched the forums and didn't find a similar issue so I'd like to pose this question to everyone:
Does anyone have issues with the device waking up from deep sleep?
If I leave my phone alone without using it for about two hours, it takes a good 15 seconds between when my fingerprint is registered to actually getting to the homescreen and being usable.
I find this to be a very strange occurrence and am not sure what is causing the issue.
I am running Nova Launcher on top but I don't have any apps installed that are egregious. Its mostly all Google Apps and Uber/Lyft so I'm not sure what the issue is.
Does anyone even know how to troubleshoot the issue at all? Since there isn't root, I wish I knew which app my phone was "choking" on to figure out how to best handle the situation.
Thanks for the replies folks!
Run gsam for a day and track the rouge apo
ticklemepinks said:
Run gsam for a day and track the rouge apo
Click to expand...
Click to collapse
Agreed. That definitely doesn't happen to me when I pick up my phone in the morning.
tecz0r said:
Hey all, I searched the forums and didn't find a similar issue so I'd like to pose this question to everyone:
Does anyone have issues with the device waking up from deep sleep?
If I leave my phone alone without using it for about two hours, it takes a good 15 seconds between when my fingerprint is registered to actually getting to the homescreen and being usable.
I find this to be a very strange occurrence and am not sure what is causing the issue.
I am running Nova Launcher on top but I don't have any apps installed that are egregious. Its mostly all Google Apps and Uber/Lyft so I'm not sure what the issue is.
Does anyone even know how to troubleshoot the issue at all? Since there isn't root, I wish I knew which app my phone was "choking" on to figure out how to best handle the situation.
Thanks for the replies folks!
Click to expand...
Click to collapse
What u mean there isn't root?