Database Info

GPSD Process Overutilization

Problem Description:
The gpsd process is using 100% of my cpu for (at time of this post) 8 hours straight. The gps is locked on, and I can get sub 50 meter accuracy indoors instantly. (Which is abnormal)
I turn off gps, and the problem continues. (GPS does not shut down despite the UI telling me it is shut down.)
Problem remediation:
I can reboot. This fixes the problem for a little while.
Question:
Is there a way to see what app is locking up the gpsd process?
I have all of the usual (adb, terminal, root) methods of investigation.
I don't want to reset the gps yet until I figure out what is doing this.

ps
system 85 1 5388 360 ffffffff afd0c0cc S /system/vendor/bin/gpsd
kill -9 85
system 10455 1 1288 548 00000000 afd0c0cc S /system/vendor/bin/gpsd
kill -9 10455
system 10468 1 1288 548 00000000 afd0c0cc S /system/vendor/bin/gpsd
Each kill only resets the PID, and the process continues to eat the battery/cpu.

I actually have a suspect app that I would like to point a finger at, but I need some sort of evidence to present the app maker.
Any help, or direction to start looking would be appreciated.

I know there is a way to tell what is using what, I just don't remember exactly whether its a system thing or an app. That isn't very helpful, I know. However, what I can offer is this: if you know which app is the offender, take a screenshot of your battery usage right now, uninstall the app, then after a full day of use see if the battery usage is better. If so, you will at least confirm.your suspicion.
Brought to you by tapatalk on my HTC Flyer.

It is much more immediate than battery usage over a day. If I leave it this way, the battery is dead in an hour or less.
Here are the tell tale signs:
CPU is pegged at 100%
Phone is very warm to the touch
Battery is getting sucked down like a slurpee
Here are my mitigating steps:
Watchdog Lite alerts on gpsd going too high
I have uninstalled the offending app
I have not gotten this specific issue since I have uninstalled.
I am 99% sure that the app I uninstalled is the offending app.
I need a log or way to prove conclusively that this app is causing the issue so that I can present my findings to the developer.

You could try looking through logcat to see if you find anything suspicious.

[Q] Significant battery drain in my new OPO

I have recently received the OPO. After charging it to 30% and just keeping WiFi on I found the battery to b zero in 12 hrs. I did not even wake up the screen in the whole time. I am really worried now. Its running on the latest 38R version. I am attaching the screenshots and also the kernel wake locks reported by GSam battery monitor for battery drain. In OPO forum a guy suggested to do a manual update of 38R. Will that work as I am already running 38R on it. Please help.
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Oct 21, 2014 1:56:19 AM
Usage Details
CPU Usage:44m 15s
App UID:0
Wakelock Detail
Included Packages
Included Processes
init
kthreadd
ksoftirqd/0
kworker/0:0H
kworker/u:0
kworker/u:0H
ksoftirqd/1
kworker/1:0
kworker/1:0H
kworker/0:1
kworker/1:1
kworker/0:1H
kworker/u:1H
sync_supers
system
kworker/1:1H
kworker/1:2
irq/344-synapti
dbs_sync/1
cfinteractive
ngd_rx_thread1
boost_sync/1
kworker/0:2
mmcqd/0
ueventd
flush-179:0
jbd2/mmcblk0p28
healthd
vold
netd
zygote
thermal-engine
boost_sync/2
dbs_sync/2
ksoftirqd/2
kworker/2:0
kworker/2:0H
kworker/2:1H
ksoftirqd/3
kworker/3:0
kworker/3:0H
kworker/3:1H
kworker/2:1
msm_slim_qmi_cl
irq/288-wcd9xxx
mdss_fb0
irq/33-cpubw_hw
mpdecision
kworker/u:6
kworker/2:2H
kworker/u:9
kworker/u:10
kworker/u:14
kworker/u:16
kworker/u:17
kworker/u:18
kworker/1:2H
kworker/2:2
kworker/3:2
kworker/u:1
MC_Thread
TX_Thread
RX_Thread
kworker/u:3
kworker/0:0
kworker/u:5
kworker/u:2
bdi-default
kswapd0
file-storage
irq/170-msm_sdc
irq/253-msm_sdc
mmcqd/0rpmb
jbd2/mmcblk0p14
jbd2/mmcblk0p16
jbd2/mmcblk0p15
debuggerd
kauditd
flush-0:19
kworker/3:2H
kworker/u:4
kworker/3:1
kworker/3:3
kworker/u:7

You need several full to zero charge cycles for your battery percentage meter to be accurate. The first couple times, let your phone die COMPLETELY until it shuts itself down. Then charge to 100% UNINTERRUPTED. Your stats aren't going to be accurate after only charging once to 30%.

LexusBrian400 said:
You need several full to zero charge cycles for your battery percentage meter to be accurate. The first couple times, let your phone die COMPLETELY until it shuts itself down. Then charge to 100% UNINTERRUPTED. Your stats aren't going to be accurate after only charging once to 30%.
Click to expand...
Click to collapse
It did not happen for the first time. This stats is from the 5th or 6th time of this kind of drain. I seriously doubt about the kernel wake ups now

Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2832525
Transmitted via Bacon

timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2832525
Transmitted via Bacon
Click to expand...
Click to collapse
No, I did not.... Will try that and update here. Thanks.

timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2832525
Transmitted via Bacon
Click to expand...
Click to collapse
Hi, I have tried it and it really worked, thank you. But still I find that Cpu wakes are draining my battery to a bit unlike my MOTO G. One doubt I had was that, Y only google play services? why cant we apply the same process of denying the wakeup and keep wake options for other apps too like play store? Will it improve or effect the performance of the device?

kandalamv said:
Hi, I have tried it and it really worked, thank you. But still I find that Cpu wakes are draining my battery to a bit unlike my MOTO G. One doubt I had was that, Y only google play services? why cant we apply the same process of denying the wakeup and keep wake options for other apps too like play store? Will it improve or effect the performance of the device?
Click to expand...
Click to collapse
You can experiment as much as you like with the features of Privacy Guard, keeping in mind that some apps will misbehave if you disallow the wrong permissions. Use an app like BetterBatteryStats to track down exactly what's causing your wakelocks in the meantime though.
Transmitted via Bacon

timmaaa said:
You can experiment as much as you like with the features of Privacy Guard, keeping in mind that some apps will misbehave if you disallow the wrong permissions. Use an app like BetterBatteryStats to track down exactly what's causing your wakelocks in the meantime though.
Transmitted via Bacon
Click to expand...
Click to collapse
Hi,
I have tried denying the google play services from privacy guard, still the phone does not go to deep sleep. 95% of the time the phone is awake even when the screen id off. While using the phone and when on idle state, the drain rate is being the same. Am helpless. Unable to use the phone because of this issue.

HTC One S Android 5.1 Lags and Random Reboots

Hello everyone, most of you should know me by now.
I've been talking to @fatboyslimerr and it seems he and a lot of people are having random reboots.
I've created this thread as a discussion place to make it easy to coordinate the issues.
Known So Far about Random Reboots:
-Not Kernel Related apparently
-Issues appear when it goes into sleep mode
-Issues are appearing with wcnss_wlan.0, power.0, and alarm failing to suspend
-Issues are only (supposedly) appearing on CM-Based ROMS
Please post as many logs as possible and report the combinations where it's appearing
Thanks, javelinanddart

@Tamlins @waver1967 @letsurock @kudykam @amh.online @Auross are some of the people I believe that also had this reboot issue running various CM-based ROMs.

fatboyslimerr said:
@Tamlins @waver1967 @letsurock @kudykam @amh.online @Auross are some of the people I believe that also had this reboot issue running various CM-based ROMs.
Click to expand...
Click to collapse
Hi,
Yes I have it.
(sorry for my poor english)
I had it @ the begening of CM12 but the problems seemed to be corrected in some of last versions of CM12 (but I also changed 2-3 times Gapps)
The problem came back with 12.1. (with Gapps 5.1)
I'm not a dev, It's juste a feeling but are we sure that the problem not coming from Gapps ? Someone tryed to test with no Gapps installed at all ? (I can't do it for the moment)
Hboot 2.16
S-OFF
Cache/Dalvik cache wipe only
Regards,
Tamlin

Tamlins said:
Hi,
Yes I have it.
(sorry for my poor english)
I had it @ the begening of CM12 but the problems seemed to be corrected in some of last versions of CM12 (but I also changed 2-3 times Gapps)
The problem came back with 12.1. (with Gapps 5.1)
I'm not a dev, It's juste a feeling but are we sure that the problem not coming from Gapps ? Someone tryed to test with no Gapps installed at all ? (I can't do it for the moment)
Hboot 2.16
S-OFF
Cache/Dalvik cache wipe only
Regards,
Tamlin
Click to expand...
Click to collapse
It's a ROM issue, not gapps or kernel

For me, it used to reboot when charging the phone. Now I am on Euphoria 5.1.1 24-05-15 build. I didn't have any reboot in this build.

letsurock said:
For me, it used to reboot when charging the phone. Now I am on Euphoria 5.1.1 24-05-15 build. I didn't any reboot in this build.
Click to expand...
Click to collapse
Exactly the same problem : reboot when fully battery charged ! I'm on cyanid L 5.1.1 ROM.
I will do some tests with the setting tomorrow and i tell you if i find something interesting.

letsurock said:
For me, it used to reboot when charging the phone. Now I am on Euphoria 5.1.1 24-05-15 build. I didn't any reboot in this build.
Click to expand...
Click to collapse
Auross said:
Exactly the same problem : reboot when fully battery charged ! I'm on cyanid L 5.1.1 ROM.
I will do some tests with the setting tomorrow and i tell you if i find something interesting.
Click to expand...
Click to collapse
As far as I know Euphoria is not CM based, so maybe that's it. I know Cyanide for sure is.
Thanks for the feedback and please do run tests!
BTW, I have emailed @intervigil about this

I've been using CM from version 11 to 12.1.
I've alway seen random reboots and I still see some (1 to 3 times a day). Each time, it' GPS/gyro related. I use location services a lot: Ingress, Ware, Google Maps, Google location tracking, apps needing GPS for other usages. Each time I could diagnose it, the last lines of the last_kmg were about the Panasonic gyro kernel driver. It both happen while the screen is off and on, but it occurs more often while unlocking and turning on the phone/screen.
Since 12.1, I have random reboots while the phone is charging. This is new, and I did not take the time to diagnose this one, it always happened while I'm in bed trying to sleep, I don't want to get up I think it can be reproduced easily, just make it charge, in less than 2 hours it should occur.

I got a reboot whilst device was sleeping, not charging on Euphoria from 1st May.
The last_kmsg is here https://drive.google.com/open?id=0B7gvN7Z3xFy2V05zQ2VuYkwzMUU&authuser=0

Do you know if we can find any logs on the system which could explain some reboots or another troubles ?
Thanks

I just had a reboot while the phone was screen off in my pocket. I had been using Ingress so it might have tried to access GPS data. It was a full reboot with vibration and white HTC statup screen. That's why I guess it's a kernel bug.
Several info:
HBOOT 2.16
CM 12.1 2015-05-06 unofficial nightly built by F-L-Y-E-R
Radio 1.20
ext4 FS
Here are the last lines of /proc/kmesg:
Code:
[18001.475382] wakeup wake lock: bam_dmux_wakelock
[18001.480113] PM: early resume of devices complete after 4.120 msecs
[18001.482310] [BATT][BMS] cc_uah = 72241uAh, raw->cc = 102858d, cc = 16942477 after subtracting 0
[18001.482341] [BATT][BMS] pm8921_bms_resume: BMS_TOLERANCES=0x2f
[18001.484722] [USB] OTG PM resume
[18001.485179] [GSNR] Gsensor enable
[18001.485179] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[18001.488659] [COMP][AKM8975] akm8975_resume: (m, a, t, mv) = (0x0, 0x0, 0x0, 0x0)
[18001.488689] [GYRO][PANASONIC] Gyro sys on on:g_status=0 off_status=0
[18001.488720] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=0
[18001.488750] [FLT]TPS tps61310_resume:
[18001.493054] msm_fb_ext_resume: Turning on HPD circuitry
[18001.493298] PM: resume of devices complete after 13.123 msecs
[18001.496106] [BATT] htc_battery_complete: sr_time_period=32959 ms; total passing time=168592 ms.htc_batt_info.state=0x2, batt_temp=374, sensor0_temp=0 at 18000998147051 (2015-05-11 12:06:23.003784523 UTC)
[18001.712709] Restarting tasks ... done.
[18001.742527] PM: suspend exit 2015-05-11 12:06:23.250197422 UTC
[18001.747746] suspend: exit suspend, ret = 0 (2015-05-11 12:06:23.255412362 UTC)
[18001.957024] [COMP][AKM8975] AKECS_GetOpenStatus:
[18002.228381] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:
[18003.479350] PM: suspend entry 2015-05-11 12:06:24.986408282 UTC
[18003.516188] Freezing user space processes ...
[18003.526138] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:wait OK
[18003.534165] (elapsed 0.009 seconds) done.
[18003.537278] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[18003.545823] Suspending console(s) (use no_console_suspend to debug)
[18003.553972] [BATT] htc_battery_prepare: passing time:170652 ms, alarm will be triggered after 3430 sec.(suspend_highfreq_check_reason=0x0, htc_batt_info.state=0x6), batt_temp=374, sensor0_temp=0 at 18003055387229 (2015-05-11 12:06:25.060994183 UTC)
[18003.555620] msm_fb_ext_suspend: Turning off HPD circuitry
[18003.559130] [FLT]TPS tps61310_suspend:
[18003.559130] [FLT]TPS flashlight_turn_off
[18003.559741] [GYRO][PANASONIC] Gyro sys off on:g_status=0 off_status=1
[18003.559771] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=1
[18003.559771] [GSNR] Gsensor disable
[18003.559771] [GSNR][BMA250] BMA_set_mode: mode = 0x01
[18003.576344] [USB] OTG PM suspend
[18003.609367] [BATT][BMS] cc_uah = 72410uAh, raw->cc = 1030269, cc = 16974441 after subtracting 0
[18003.609367] [BATT][BMS] pm8921_bms_suspend: BMS_TOLERANCES=0x2f
[18003.610740] PM: suspend of devices complete after 55.360 msecs
[18003.611564] PM: late suspend of devices complete after 0.823 msecs
[18003.612999] PM: noirq suspend of devices complete after 1.403 msecs
[18003.612999] Disabling non-boot CPUs ...
[18003.613457] msm_pm_enter
[18003.613457] msm_pm_enter: power collapse
[18003.613457] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000000,00020000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[18003.613457] msm_pm_enter: return
[18003.614891] PM: noirq resume of devices complete after 1.312 msecs
[18003.615715] wakeup wake lock: bam_dmux_wakelock
[18003.616753] PM: early resume of devices complete after 0.762 msecs
[18003.618706] [BATT][BMS] cc_uah = 72855uAh, raw->cc = 10499d7, cc = 17078743 after subtracting 0
[18003.618706] [BATT][BMS] pm8921_bms_resume: BMS_TOLERANCES=0x2f
[18003.620079] [USB] OTG PM resume
[18003.620202] [GSNR] Gsensor enable
[18003.620202] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[18003.623864] [COMP][AKM8975] akm8975_resume: (m, a, t, mv) = (0x0, 0x0, 0x0, 0x0)
[18003.623864] [GYRO][PANASONIC] Gyro sys on on:g_status=0 off_status=0
[18003.623864] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=0
[18003.623894] [FLT]TPS tps61310_resume:
[18003.625848] msm_fb_ext_resume: Turning on HPD circuitry
[18003.626092] PM: resume of devices complete after 9.308 msecs
[18003.628900] [BATT] htc_battery_complete: sr_time_period=121949 ms; total passing time=292601 ms.htc_batt_info.state=0x2, batt_temp=355, sensor0_temp=0 at 18003130309446 (2015-05-11 12:08:27.003479085 UTC)
[18003.845656] Restarting tasks ... done.
[18003.866684] PM: suspend exit 2015-05-11 12:08:27.241231020 UTC
[18003.880388] suspend: exit suspend, ret = 0 (2015-05-11 12:08:27.254953790 UTC)
[18004.062350] [COMP][AKM8975] AKECS_GetOpenStatus:
[18004.352935] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:
COMP is for compass and GYRO for the gyroscope.
Would it be possible for someone to build a kernel without the gyro driver so that I can use it during a few days for testing? And maybe also another one without the compass driver ?

kdd998 said:
I just had a reboot while the phone was screen off in my pocket. I had been using Ingress so it might have tried to access GPS data. It was a full reboot with vibration and white HTC statup screen. That's why I guess it's a kernel bug.
Several info:
HBOOT 2.16
CM 12.1 2015-05-06 unofficial nightly built by F-L-Y-E-R
Radio 1.20
ext4 FS
Here are the last lines of /proc/kmesg:
Code:
[18001.475382] wakeup wake lock: bam_dmux_wakelock
[18001.480113] PM: early resume of devices complete after 4.120 msecs
[18001.482310] [BATT][BMS] cc_uah = 72241uAh, raw->cc = 102858d, cc = 16942477 after subtracting 0
[18001.482341] [BATT][BMS] pm8921_bms_resume: BMS_TOLERANCES=0x2f
[18001.484722] [USB] OTG PM resume
[18001.485179] [GSNR] Gsensor enable
[18001.485179] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[18001.488659] [COMP][AKM8975] akm8975_resume: (m, a, t, mv) = (0x0, 0x0, 0x0, 0x0)
[18001.488689] [GYRO][PANASONIC] Gyro sys on on:g_status=0 off_status=0
[18001.488720] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=0
[18001.488750] [FLT]TPS tps61310_resume:
[18001.493054] msm_fb_ext_resume: Turning on HPD circuitry
[18001.493298] PM: resume of devices complete after 13.123 msecs
[18001.496106] [BATT] htc_battery_complete: sr_time_period=32959 ms; total passing time=168592 ms.htc_batt_info.state=0x2, batt_temp=374, sensor0_temp=0 at 18000998147051 (2015-05-11 12:06:23.003784523 UTC)
[18001.712709] Restarting tasks ... done.
[18001.742527] PM: suspend exit 2015-05-11 12:06:23.250197422 UTC
[18001.747746] suspend: exit suspend, ret = 0 (2015-05-11 12:06:23.255412362 UTC)
[18001.957024] [COMP][AKM8975] AKECS_GetOpenStatus:
[18002.228381] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:
[18003.479350] PM: suspend entry 2015-05-11 12:06:24.986408282 UTC
[18003.516188] Freezing user space processes ...
[18003.526138] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:wait OK
[18003.534165] (elapsed 0.009 seconds) done.
[18003.537278] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
[18003.545823] Suspending console(s) (use no_console_suspend to debug)
[18003.553972] [BATT] htc_battery_prepare: passing time:170652 ms, alarm will be triggered after 3430 sec.(suspend_highfreq_check_reason=0x0, htc_batt_info.state=0x6), batt_temp=374, sensor0_temp=0 at 18003055387229 (2015-05-11 12:06:25.060994183 UTC)
[18003.555620] msm_fb_ext_suspend: Turning off HPD circuitry
[18003.559130] [FLT]TPS tps61310_suspend:
[18003.559130] [FLT]TPS flashlight_turn_off
[18003.559741] [GYRO][PANASONIC] Gyro sys off on:g_status=0 off_status=1
[18003.559771] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=1
[18003.559771] [GSNR] Gsensor disable
[18003.559771] [GSNR][BMA250] BMA_set_mode: mode = 0x01
[18003.576344] [USB] OTG PM suspend
[18003.609367] [BATT][BMS] cc_uah = 72410uAh, raw->cc = 1030269, cc = 16974441 after subtracting 0
[18003.609367] [BATT][BMS] pm8921_bms_suspend: BMS_TOLERANCES=0x2f
[18003.610740] PM: suspend of devices complete after 55.360 msecs
[18003.611564] PM: late suspend of devices complete after 0.823 msecs
[18003.612999] PM: noirq suspend of devices complete after 1.403 msecs
[18003.612999] Disabling non-boot CPUs ...
[18003.613457] msm_pm_enter
[18003.613457] msm_pm_enter: power collapse
[18003.613457] msm_mpm_irqs_detectable: cannot monitor 000000,00000000,00000000,00000000,00000000,00000000,00020000,00000000,00000000,00000000,00000000,00000000,00000000,00000000
[18003.613457] msm_pm_enter: return
[18003.614891] PM: noirq resume of devices complete after 1.312 msecs
[18003.615715] wakeup wake lock: bam_dmux_wakelock
[18003.616753] PM: early resume of devices complete after 0.762 msecs
[18003.618706] [BATT][BMS] cc_uah = 72855uAh, raw->cc = 10499d7, cc = 17078743 after subtracting 0
[18003.618706] [BATT][BMS] pm8921_bms_resume: BMS_TOLERANCES=0x2f
[18003.620079] [USB] OTG PM resume
[18003.620202] [GSNR] Gsensor enable
[18003.620202] [GSNR][BMA250] BMA_set_mode: mode = 0x00
[18003.623864] [COMP][AKM8975] akm8975_resume: (m, a, t, mv) = (0x0, 0x0, 0x0, 0x0)
[18003.623864] [GYRO][PANASONIC] Gyro sys on on:g_status=0 off_status=0
[18003.623864] [GYRO][PANASONIC] GyroB sys off on:g_status=0 off_status=0
[18003.623894] [FLT]TPS tps61310_resume:
[18003.625848] msm_fb_ext_resume: Turning on HPD circuitry
[18003.626092] PM: resume of devices complete after 9.308 msecs
[18003.628900] [BATT] htc_battery_complete: sr_time_period=121949 ms; total passing time=292601 ms.htc_batt_info.state=0x2, batt_temp=355, sensor0_temp=0 at 18003130309446 (2015-05-11 12:08:27.003479085 UTC)
[18003.845656] Restarting tasks ... done.
[18003.866684] PM: suspend exit 2015-05-11 12:08:27.241231020 UTC
[18003.880388] suspend: exit suspend, ret = 0 (2015-05-11 12:08:27.254953790 UTC)
[18004.062350] [COMP][AKM8975] AKECS_GetOpenStatus:
[18004.352935] [GYRO][PANASONIC] EWTZMU2_GetOpenStatus:
COMP is for compass and GYRO for the gyroscope.
Would it be possible for someone to build a kernel without the gyro driver so that I can use it during a few days for testing? And maybe also another one without the compass driver ?
Click to expand...
Click to collapse
@intervigil confirmed this is a known CM bug that the Compass/Gyro causes reboots on Ville
This is a separate issue from the ROM side stuff @fatboyslimerr
I'll add this issue to the OP though thanks for reminding me
I'm waiting for @fatboyslimerr to confirm is a minor modification I made might've fixed Compass

javelinanddart said:
@intervigil confirmed this is a known CM bug that the Compass/Gyro causes reboots on Ville
This is a separate issue from the ROM side stuff @fatboyslimerr
I'll add this issue to the OP though thanks for reminding me
I'm waiting for @fatboyslimerr to confirm is a minor modification I made might've fixed Compass
Click to expand...
Click to collapse
Good news then

kdd998 said:
Good news then
Click to expand...
Click to collapse
Not fixed unfortunetely

javelinanddart said:
@intervigil confirmed this is a known CM bug that the Compass/Gyro causes reboots on Ville
This is a separate issue from the ROM side stuff @fatboyslimerr
I'll add this issue to the OP though thanks for reminding me
I'm waiting for @fatboyslimerr to confirm is a minor modification I made might've fixed Compass
Click to expand...
Click to collapse
That is a bug haunting Ville for ages...since long time ago users are reporting reboots while using maps or similar apps (I had it too several times in the past but now I'm not using maps/nav so often)
Sent from nowhere over the air...

Rapier said:
That is a bug haunting Ville for ages...since long time ago users are reporting reboots while using maps or similar apps (I had it too several times in the past but now I'm not using maps/nav so often)
Sent from nowhere over the air...
Click to expand...
Click to collapse
Yeah I heard from @intervigil
It's mostly compass apps
I've used Google Maps with no issues.
Unfortunately that's not the only issue
Phone seems to be rebooting when in deep sleep mode

Yep, still having reboots during sleep. Google maps does work fine, device gets seriously hot but it works fine. 3rd party compass apps cause reboots after awhile.

fatboyslimerr said:
Yep, still having reboots during sleep. Google maps does work fine, device gets seriously hot but it works fine. 3rd party compass apps cause reboots after awhile.
Click to expand...
Click to collapse
Device getting seriously hot is thermald issue
Why I used showp's thermal in a nutshell: Never had my ville not feel cold to the touch
Not that I have ville anymore ofc....

Since 2 days, I've been using cm12.1 nightly from the 15th. Now back on hboot 2.15 and last officially pushed (for international region) radio by HTC: 1.11.
I discovered the quick toggle for the compass and disabled its usage (it must be relatively recent). So far: not one reboot related to GPS
I had 2 reboots while setting up all my apps but didn't take the opportunity to get a logcat or kmesg. It did not occur since.

kdd998 said:
Since 2 days, I've been using cm12.1 nightly from the 15th. Now back on hboot 2.15 and last officially pushed (for international region) radio by HTC: 1.11.
I discovered the quick toggle for the compass and disabled its usage (it must be relatively recent). So far: not one reboot related to GPS
I had 2 reboots while setting up all my apps but didn't take the opportunity to get a logcat or kmesg. It did not occur since.
Click to expand...
Click to collapse
Sweet!
IDK about the apps thing

1705 wakelocks running enhdroix 14.10.14

I need some help, having lot's of wakelocks recently. Strange kinda came out of no where lol. below are my GSM stats showing the lock, let's fix this! thanks!
GSam Labs - Battery Monitor - Export Data
Android System
May 6, 2015 6:53:03 PM
Usage Details
CPU Usage:16m 20s
CPU Usage (Background Only):16m 20s
Keep Awake:2m 7s
Number of Wake Locks:1705
Number of times waking device:114
Bytes Sent:10.07 KB
Bytes Received:11.72 KB
Accelerometer:1h 23m 32s
Proximity:1m 4s
App UID:1000
Wakelock Detail
ActivityManager-Launch1.1m(161)
AlarmManager35.5s(653)
SCREEN_FROZEN5.8s(11)
NetworkStats3.8s(86)
SyncLoopWakeLock3.3s(494)
WifiSuspend2.2s(92)
*backup*1.8s(20)
DHCP1.7s(4)
ActivityManager-Sleep1.4s(44)
GpsLocationProvider1.2s(29)
SyncManagerHandleSyncAlarm1.1s(100)
handleAudioEvent0.5s(2)
AudioMix0.4s(5)
handleMediaEvent0.1s(1)
PhoneWindowManager.mBroadcastWakeLock0.0s(1)
WiredAccessoryManager0.0s(2)
Included Packages
Android System
Settings
Service Programu
Key Chain
Input Devices
Fused Location
Settings Storage
Dev Tools
Included Processes
system:ui
qseecomd
time_daemon
surfaceflinger
android
com.android.settings
com.android.keychain
system_server
servicemanager
qrngd
Click to expand...
Click to collapse

wakelocks are how your phone works, they need to be there. its an occasional wakelock with a "stuck" process thatll drain battery.

simms22 said:
wakelocks are how your phone works, they need to be there. its an occasional wakelock with a "stuck" process thatll drain battery.
Click to expand...
Click to collapse
yes I understand that lol but my phone drained pretty fast that day and this is the only clue. I went from averaging 5 hr's SoT to 3 that day. Big difference so I would like some help please.

Battery drain on a brand new K1

So I picked up a Nvidia Shield K1 this weekend and this night I thought to see how effrctive DOSE was.
I went to bed with 96% battery and woke up to a 70% battery.
I havent tweaked anything in my tablet its completly stock.
I'm going to upload a screenshot to prove it. The tablet wws in sleep mode trough this screenshot and not being used as it wpuld sugest.
My question is, is there a way to solve this?
Sorry if my english is bad, and thanks to anyone whom can help me!
Sent from my SHIELD Tablet K1 using XDA Free mobile app

Filz0r said:
So I picked up a Nvidia Shield K1 this weekend and this night I thought to see how effrctive DOSE was.
I went to bed with 96% battery and woke up to a 70% battery.
I havent tweaked anything in my tablet its completly stock.
I'm going to upload a screenshot to prove it. The tablet wws in sleep mode trough this screenshot and not being used as it wpuld sugest.
My question is, is there a way to solve this?
Sorry if my english is bad, and thanks to anyone whom can help me!
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Have you the Marshmallow update?

Yes I updated it as soon as turned it on
Sent from my XT1524 using XDA Free mobile app

I had the same problem but i think a factory reset solved it.

Strange, I haven't this issue. I have upgraded to Marshmallow once opened from its box, and unlock bootloader/root just after.
Maybe an application which blocks the doze mode?

Have you tried a wakelock detector? You should be able to track down what exactly is eating up your battery.
Check out GSam Battery Monitor, works for me!

Yes, GSam or BetterBatteryStats (link of the XDA post)

There's a thread on the NVidia forum about a similar drain, and in many cases the tablet also runs quite hot when it should be doing next to nothing.
forums.geforce.com/default/topic/904962/shield-tablet/android-6-0-update-battery-drain-by-miscellaneous-app-new-shield-k1-model-/
It appears to be a bug after the 6.0 update, it triggers the /system/bin/logd process.
You can check if you have the same bug by running adb shell with
Code:
top -m 5
(for 5 highes using processes) when it drains quickly, and look for the /system/bin/logd process.
It doesn't necessarily mean that it's the same bug, but considering the fact that quite a lot of people experience the same issue..
On the forum many users reported improvements when turning app optimization off, occasionally turning wifi off and on again and setting 'Keep Wi-Fi on during sleep' to 'Only when plugged in' or 'never'.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.

Same issue since marshmallow, runs hot with light use and huge battery drain. Been busy so haven't tried to debug or even reset yet but good to know its not just me.... Will unlock and root (will be a factory reset) soon, hope all will be fixed with this

Downgraded to 5.1.1 for the bad battery drain on marshmallow so I'm waiting to see if nvidia issues a update

I sufferring too the issue about abnormal battery drain, and I can't find a way to disable the touchboost (that clock at max cpu&gpu at same time)
so I searched for a kernel manager app compatible since 27th December when I installed my K1 with ota 6.0 , the only one that was updated is Ex Kernel Manager app (latest version 2.41 because 2.38 etc doesn't work) setting it on eco power mode or underclocking cpu to max 1224Mhz (if tablet is turned off or restarted must be set again), lcd set at 60% brightness but auto on, gave to me 26hrs. of active use on internet websurfing, movies and some light gaming at fallout shelter (2%) with wifi on all time and bluetooth for some.
Now I'm happy again ^_^
Regards

aaronne said:
I sufferring too the issue about abnormal battery drain, and I can't find a way to disable the touchboost (that clock at max cpu&gpu at same time)
so I searched for a kernel manager app compatible since 27th December when I installed my K1 with ota 6.0 , the only one that was updated is Ex Kernel Manager app (latest version 2.41 because 2.38 etc doesn't work) setting it on eco power mode or underclocking cpu to max 1224Mhz (if tablet is turned off or restarted must be set again), lcd set at 60% brightness but auto on, gave to me 26hrs. of active use on internet websurfing, movies and some light gaming at fallout shelter (2%) with wifi on all time and bluetooth for some.
Now I'm happy again ^_^
Regards
Click to expand...
Click to collapse
Hmm, I was actually hoping on keeping one of my devices completely stock/unrooted for a change, makes it easier for OTA's and takes less of my time on tinkering with it
That being said, when looking at CPU Spy it seems the CPU govenor isn't really flexible, most of the CPU states are sleep, 204MHz, 312MHz, 1044MHz, 1530MHz and 2218MHz, and little to no time on the other states.
I'm no kernel expert, but it seems to me that battery life could be extended without performance issues if it wouldn't immediately switch to high CPU states but the states in between...
Anyway, haven't had these abnormal drains since I changed the settings I mentioned earlier. Misc drain snuck a couple of percent yesterday, but lightyears away from what it used to.

I've done those changes and so far the battery life has improved a lot, one more thing my WiFi sometimes drops out of the blue does anyone else have this issue?
Sent from my SHIELD Tablet K1 using XDA Free mobile app

Filz0r said:
I've done those changes and so far the battery life has improved a lot, one more thing my WiFi sometimes drops out of the blue does anyone else have this issue?
Sent from my SHIELD Tablet K1 using XDA Free mobile app
Click to expand...
Click to collapse
Haven't had a dropout as far as I know, but I did notice a WiFi performance drop once or twice. I was still connected, but webpages wouldn't load untill I'd reset the WiFi adapter. Those were also the times that a slight misc drain appeared.

I received NVidia shield v2 K1 with lollipop out of the box.
it updated via OTA to Marshmallow 6.0 and I had to revert back and block it from updating cos it was way to buggy for me, main problem was Wi-Fi/No internet issue. The tablet was a paper weight without internet.
N.B it did connect to the Wi-Fi. Rebooted my router, rebooted tablet, turned airport mode on/off , Changed frequencies and still nothing. My other devices could connect and have internet without issue.
N.B. It could connect to Wi-Fi, just no internet icon !

frentrop said:
There's a thread on the NVidia forum about a similar drain, and in many cases the tablet also runs quite hot when it should be doing next to nothing.
forums.geforce.com/default/topic/904962/shield-tablet/android-6-0-update-battery-drain-by-miscellaneous-app-new-shield-k1-model-/
It appears to be a bug after the 6.0 update, it triggers the /system/bin/logd process.
You can check if you have the same bug by running adb shell with
Code:
top -m 5
(for 5 highes using processes) when it drains quickly, and look for the /system/bin/logd process.
It doesn't necessarily mean that it's the same bug, but considering the fact that quite a lot of people experience the same issue..
On the forum many users reported improvements when turning app optimization off, occasionally turning wifi off and on again and setting 'Keep Wi-Fi on during sleep' to 'Only when plugged in' or 'never'.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.
Click to expand...
Click to collapse
+1,
I had to set WiFi to Never on during sleep, I also use the debloater app to pretty much disable all Nvidia apps. My standby time has increased dramatically. But I hope nvidia releases an official fix.
Sent from my ONE E1005 using Tapatalk

Hi guys, I recently updated to 6.0 and have issues with battery drain during sleep. I see that I have a lot of wake locks by GOOGLE_C2DM. Attached is the export from GSAM.
First I thought it was Facebook and Instagram which had the C2DM services, I uninstalled the apps but still have the wake locks.
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Jan 28, 2016 9:18:27 AM
Usage Details
CPU Usage:14h 13m 2s
CPU Usage (Background Only):14h 13m 2s
Keep Awake:4h 18m 5s
Number of Wake Locks:35
Bytes Sent:26.08 KB
Bytes Received:54.92 KB
App UID:0
Wakelock Detail
GOOGLE_C2DM0.4s(35)
Included Packages
Included Processes
file-storage
mmcqd/0rpmb
wifi_scan_polic
cfinteractive
wl_event_handle
nvmap-bz
kauditd
sdcard
zygote
irq/80-soctherm
ueventd
kswapd0
surfaceflinger
watchdogd
debuggerd
watchdog/0
watchdog/1
watchdog/2
watchdog/3
tlk_daemon
jbd2/mmcblk0p13
jbd2/mmcblk0p14
jbd2/mmcblk0p18
jbd2/mmcblk0p23
jbd2/mmcblk0p8-
icfb-kthread
su
adbd
lmkd
logd
netd
spi0
spi3
vold
/init
rcu_preempt
khubd
rcu_sched
irq/105-tegradc
irq/118-4-0058
kthreadd
installd
kworker/0:0
kworker/0:1
kworker/0:2
kworker/0:3
kworker/0:4
kworker/0:5
kworker/0:6
kworker/0:7
kworker/0:8
kworker/0:9
kworker/1:0
kworker/1:1
kworker/1:2
kworker/1:3
kworker/1:4
kworker/1:5
kworker/2:0
kworker/2:1
kworker/2:2
kworker/2:3
kworker/3:0
kworker/3:1
kworker/3:2
kworker/3:3
healthd
dhd_watchdog_th
irq/259-spi0.0
mmcqd/0
irq/77-tegra_ac
irq/77-tegra_mo
ksoftirqd/0
ksoftirqd/1
ksoftirqd/2
ksoftirqd/3
wpa_supplicant
migration/0
migration/1
migration/2
migration/3
irq/189-gk20a_s
dhd_dpc
dhd_rxf
kworker/0:0H
kworker/0:10
kworker/0:1H
kworker/0:2H
kworker/1:0H
kworker/1:1H
kworker/1:2H
kworker/2:0H
kworker/2:1H
kworker/3:0H
kworker/3:1H
kworker/u8:0
kworker/u8:1
kworker/u8:2
kworker/u8:3
kworker/u8:4
kworker/u8:5
kworker/u8:6
kworker/u8:7
kworker/u8:8
kworker/u8:9
kworker/u9:1
irq/321-mpu6xxx
kworker/u8:10
kworker/u8:11
kworker/u8:12
tegradc.0/a
tegradc.0/b
tegradc.0/c
tegradc.0/d
tegradc.0/e
tegradc.1/a
tegradc.1/b
tegradc.1/c
tegradc.1/d
tegradc.1/e

no, it is : /system/bin/logd -> this process gets stuck due to a third party error.
Just install OS Monitor and reset this Process if it runs into a high load.
nVidia will Release a Patch within the next days or a week, there is a announcment for that and a beta update for tester.

I install Deep Sleep app and set it to SLUMBERER MODE, now my battery only goes down 2% overnight. I'm happy with the results. Don't mind having notifications appear after I wake up device.

frentrop said:
.
.
.
I have had some good results by selecting 'Only when plugged in' and by turning off 'Help NVIDIA improve SHIELD' in 'About tablet', but we'll have to wait on NVidia to fix this.
Click to expand...
Click to collapse
Hi,
Did this fix your problem permanently?
I bought mine 3 days ago, updated to mm 2 days ago and yesterday, voila, drain occurred while browsing pages I think, or some YouTube or streaming video...
I will try this today when I come back.