gpsd keeping phone awake all the time

I have a Samsung S4 I9500 and since the 4.4.2 upgrade my battery started draining around 10% per hour. I checked the battery settings and it says that the draining apps are: Android OS, Android System and gpsd. I also installed BetterBatteryStats and I found out that the phone is awake 100% of the time. Then I checked the Kernel Wakelocks and gpsd is the process keeping my phone awake most of the time. I have searched forums and google exhaustively and tried all solutions but none have worked. I even rooted my phone and started uninstalling all apps that could be using the gpsd process and it didn't work. Then I installed CyanogenMod hoping this would work, but no, I still have the same problem. Right now I have CyanogenMod CM11 (cm-11-20140811-NIGHTLY-i9500), gapps (MICRO MODULAR PACKAGE http://forum.xda-developers.com/show....php?t=2397942) and only a few extra apps installed: App Master, BetterBatteryStats, ColorNote, Slider Widget, Waze, Whatsapp and Xperia keyboard (I installed this one because the Android Keyboard (AOSP) kept crashing, so I disabled it). I have no idea of what to do next, if someone with extensive Android and gpsd knowledge can help me please do so, I have run out of ideas on what to do to fix this...

Quick Reply Reply

14th August 2014, 02:06 AM |#2

OP Junior Member

Thanks Meter: 0

renaming gpsd

So I can rename the gpsd bin in /system/bin/gpsd to something else and it won't drain my battery anymore, but I can't use my gps... I need to rename it to gpsd and restart my phone... ANNOYING!

Quick Reply Reply

16th August 2014, 03:09 AM |#3

OP Junior Member

Thanks Meter: 0

solution (partially)

So I partially solved my problem:
I created two shell scripts to stop and start the gpsd process. So if I want to use an app like Waze that uses gpsd I launch my start script and then when I finish using the app I launch my stop script. I use the SManager app to launch the scripts (with the Widget addon to have quick buttons in the start screen.

start_gpsd:
#!/system/bin/sh
mount -o rw,remount /system
chmod 755 /system/bin/gpsd
mount -o ro,remount /system
pkill scriptmanager

stop_gpsd:
#!/system/bin/sh
mount -o rw,remount /system
chmod 644 /system/bin/gpsd
pkill gpsd
mount -o ro,remount /system
pkill scriptmanager

Quick Reply Reply

18th August 2014, 12:03 PM |#4

Member

Thanks Meter: 2

having the same problem

i'm having the same problem. gpsd is eating up my battery. the phone can't get into deep sleep.

for a few days i was able to experiene normal battery and then it comes up again after 2 days.

i'm starting to think that this might be a google search or google now problem. before updates, everything was working fine. i initially thought foursquare was the culprit but the problem is still there.

this is so irritating, no one seems to have a solution.

Quick Reply Reply

31st August 2014, 08:35 PM |#5

Junior Member

Thanks Meter: 0

solution (partially) script

Hi tomatus270389

Could you please tell me, how can I make that shell script step by step.

Thanks.

Quick Reply Reply

17th September 2014, 10:11 PM |#6

Member

Johannesburg

Thanks Meter: 24

Quote:

Originally Posted by chinov13

Hi tomatus270389

Could you please tell me, how can I make that shell script step by step.

Thanks.

Hi Chinov

I've been struggling with the GPSD process chomping away at my battery for 2 weeks now. Finally I found a work-around that works for me, although it doesn't solve the root cause.

I solved the issue on my Galaxy S4 (rooted with Omega 24) by installing Tasker (purchased from the play store). It's actually quite simple once installed. You create a new shell script task that runs as su and in the command type "pkill gpsd" (without the quotes). Then you can set an IF condition (at the bottom) to only execute it when %GPS not equal "on" (also without the quotes). That will ensure that Tasker doesn't kill the gpsd process when you switched GPS on manually to use it for navigation etc. Once that's done, you can create a schedule to execute that task every 2 minutes or whatever works for you.

Easy!

Hope this helps you or someone else.

Koeties

Last edited by Koeties; 18th September 2014 at 06:24 AM.

Quick Reply Reply

3rd December 2014, 03:30 AM |#7

Senior Member

Thanks Meter: 111

Quote:

Originally Posted by Koeties

I am 99,99% sure it is not a local hardware/software issue, but a carrier issue due to any incorrect parameters on their net/cells, maybe Fast Dormancy... not sure.

All with this issue, see this thread: http://forum.xda-developers.com/show...php?p=51989209
[Q] What is l2_hsic kernel wakelock and I9500 not entering deep sleep

Quick Reply Reply

3rd February 2015, 12:30 PM |#8

Member

Johannesburg

Thanks Meter: 24

Quote:

Originally Posted by jaswinky

Feedback on this from my side: Turned out you're correct jaswinky, it was something the carrier did. They very quietly disabled whatever they did and my problems went away. I only found out about what they did in other local forums. At least the work-around sorted my battery drain problems out while the carrier mucked around.

Quick Reply Reply

Guest Quick Reply (no urls or BBcode)
The following errors occurred with your submission

Okay
Message: Posting Quick Reply - Please Wait

Analysis & Opinion

Sony Open Device Program Interview: Opening Much More Than Just Software

Through the Viewfinder: Droidcon UK 2015

Editorial Edge Plus Premium: OEM Naming Conventions & How They Dilute Flagships

What is the Most Underrated Feature on Android, and Why?

King of Best Phones Under $100 (Part 5)

gpsd keeping phone awake all the time

Top Threads in Questions and Answers by ThreadRank

vBulletin Message