[BetterBatteryStats] tweakradje:
vbus wake lock

Been searching this thread for the vbus wake lock trouble. No definitive answers, apart from a little dusting the connector :)

Now I have two Samsung cores with both the same vbus problem drain. Both on Android 4.1 with kernel 3.4.0-1594964-user

Here is a kmsg dump (grep -C 10 -i vbus /proc/kmsg)

You will see usb cable was connected during some time during the logging.

Anyone? Thanks

See attachement for complete log

<6>[71896.090929] c0 early_suspend: calling mdp_early_suspend
<6>[71896.090991] c0 early_suspend: calling msmsdcc_early_suspend
<6>[71896.091032] c0 early_suspend: calling msmsdcc_early_suspend
<6>[71896.091072] c0 early_suspend: calling msmsdcc_early_suspend
<6>[71896.091137] c0 PM: Syncing filesystems...
<6>[71896.094421] c1 active wake lock usb_bus_active
<6>[71896.094469] c1 active wake lock vbus_wake_lock
<6>[71896.094506] c1 wake lock ath6kl_suspend_wl, expired
<6>[71896.103977] c0 sync done.
<6>[71898.726551] c0 fsa_microusb 3-0025: fsa9480_work_cb: intr: 0x2 intr2: 0x0
<4>[71898.726601] c0 KBJ TEST : fsa9480_write_reg , register = 5 , values = 3
<6>[71898.726902] c0 fsa_microusb 3-0025: fsa9480_work_cb: start unmasking attach/detach irq
<6>[71898.728331] c0 fsa_microusb 3-0025: intr: 0x2, dev1: 0x0, dev2: 0x0, adc: 0x1f
<4>[71898.728379] c0 fsa9480_detect_dev : REG_CTRL = 1e , usbsw->mansw : 0
<6>[71898.728424] c0 [BATT] [jena_usb_cb] Board file [fsa9480]: USB Callback
<6>[71898.728467] c0 msm_set_acc_type : [BATT] acc_status = 0
<6>[71898.728509] c0 msm_set_cable : [BATT] cable_status(0)
--
<6>[71959.613864] c1 bma2x2_set_mode: 2
<6>[71959.613891] c1 reactive_enable = 0, reactive_state =0
<6>[71959.616689] c1 bma2x2_set_mode: 2 Success
<6>[71959.616724] c1 reactive_enable = 0, reactive_state =0
<6>[71959.917099] c1 early_suspend: calling mdp_early_suspend
<6>[71959.917161] c1 early_suspend: calling msmsdcc_early_suspend
<6>[71959.917202] c1 early_suspend: calling msmsdcc_early_suspend
<6>[71959.917242] c1 early_suspend: calling msmsdcc_early_suspend
<6>[71959.917301] c1 expired wake lock ath6kl_suspend_wl
<6>[71959.917336] c0 PM: Syncing filesystems...
<6>[71959.917369] c1 expired wake lock vbus_wake_lock
<6>[71959.917481] c1 suspend: enter suspend
<6>[71959.917549] c1 PM: suspend entry 2016-12-19 20:53:05.175756592 UTC
<4>[71959.917652] c1 Freezing user space processes ... (elapsed 0.02 seconds) done.
<6>[71959.951119] c1 sync done.
<6>[71959.951152] c1 PM: Syncing filesystems...
<6>[71959.956686] c1 sync done.
<4>[71960.188037] c1 Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
<4>[71960.208611] c1 Suspending console(s) (use no_console_suspend to debug)
<6>[71960.208734] c1 [BATT] msm_batt_suspend
<6>[71960.208761] c1 msm_batt_set_alarm[BATT] set alarm
...

Please see attachement

EDIT: Think I already found the cause. It's Google Play Services. I removed it, rebooted, switched of Wifi and Data. After one hour only 1% wake time and very little vbus wake lock. Next is to let it install again (switching on internet) and then test again.

EDIT2: stooped Android, removed Google services framework and Goole Play Services data, rebooted. Then adjusted gtalk_%heartbeat_ping_interval_ms to 5 minutes. All looks fine now.

More info here: http://xdaforums.com/showpost.php?p=36926738&postcount=83

Check connection status: am start com.google.android.gms/.gcm.GcmDiagnostics