Database Develop

Noob seeks help..bluetooth kaput?

So I've got g1 with latest cyan rom, one small problem I've been with out bluetooth for over a month a can't figure it out, I wiped 3-4 times and it worked brieflt, however once everything is reinstalled the problem persist. I seached all over, I'm sure it has something to do with init.trout.rc, but being complete noob that's as far as I can go without help, with that said please help me
Tia
Attached below log:
Generated with SendLog 0.0.3 http://l6n.org/android/
T-Mobile G1 dream 1.6 DRC83
User 2%, System 3%, IOW 0%, IRQ 0%
User 9 + Nice 0 + Sys 11 + Idle 292 + IOW 0 + IRQ 0 + SIRQ 0 = 312
PID CPU% S #THR VSS RSS UID Name
4481 3% R 1 896K 352K app_56 top
4364 1% S 15 123676K 23052K app_2 com.android.vending
95 0% S 49 190520K 32896K system system_server
129 0% S 2 2928K 416K wifi /system/bin/wpa_supplicant
5 0% S 1 0K 0K root events/0
6 0% S 1 0K 0K root khelper
7 0% S 1 0K 0K root suspend
8 0% S 1 0K 0K root kblockd/0
9 0% S 1 0K 0K root kmmcd
10 0% S 1 0K 0K root bluetooth
11 0% S 1 0K 0K root kondemand/0
12 0% S 1 0K 0K root qmi
13 0% D 1 0K 0K root rpcrouter
14 0% S 1 0K 0K root detect

hmmmmm try using dwang 1.13 and see if it works with that rom...

Thank you kind sir, that worked wonders not only BT works, but it runs so much smoother no hiccups Biggest kudos to Dwang and his wonderful rom

[Q] Device freezes up for ~20s on application crash

My Note freezes up whenever an application crashes, for about 20s. Here's some logcat output for when this happens:
Code:
<app crashes here>
E/AndroidRuntime(24971): ... 11 more
W/ActivityManager( 1864): Force finishing activity r.intent.getComponent().flattenToShortString()
D/OpenGLRenderer(22653): Flushing caches (mode 2)
I/ClipboardServiceEx( 1864): mCBPickerDialog enter case. MSG_DISMISS_DIALOG
D/OpenGLRenderer(22653): Flushing caches (mode 0)
E/android.os.Debug( 1864): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate(24985): Check if stand-alone
I/dumpstate(24985): begin
I/SurfaceFlinger( 1699): id=6398 Removed idx=0 Map Size=4
I/SurfaceFlinger( 1699): id=6398 Removed idx=-2 Map Size=4
W/ActivityManager( 1864): Activity pause timeout for r
E/lights ( 1864): write_int: path /sys/devices/virtual/sec/sec_touchkey/brightness, value 2
W/PowerManagerService( 1864): Timer 0x7->0x3|0x0
I/PowerManagerService( 1864): Ulight 7->3|0
D/PowerManagerService( 1864): setLightBrightness : mButtonLight : 0
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
V/ThermistorObserver( 1864): mThermistorState =0, Thermistor temperature: 330
E/AlarmManagerService( 1864): android_server_AlarmManagerService_set to type=1, 1339768800.000000000
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
I/InputReader( 1864): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.9138 ]
E/lights ( 1864): write_int: path /sys/devices/virtual/sec/sec_touchkey/brightness, value 1
I/PowerManagerService( 1864): Ulight 3->7|0
D/PowerManagerService( 1864): setLightBrightness : mButtonLight : 130
D/PowerManagerService( 1864): lightSensorChangedLocked 260
D/PowerManagerService( 1864): lcdValue 130
D/PowerManagerService( 1864): buttonValue 0
D/PowerManagerService( 1864): keyboardValue 0
D/PowerManagerService( 1864): lightSensorChangedLocked : mKeyboardLight : 0
I/InputReader( 1864): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
I/InputReader( 1864): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.9139 ]
I/InputReader( 1864): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/DEFERED_APP_VISIBILITY( 1864): tweaking closing app
W/PowerManagerService( 1864): Timer 0x7->0x3|0x0
E/lights ( 1864): write_int: path /sys/devices/virtual/sec/sec_touchkey/brightness, value 2
I/PowerManagerService( 1864): Ulight 7->3|0
D/PowerManagerService( 1864): setLightBrightness : mButtonLight : 0
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
D/VoldCmdListener( 1692): asec list
D/VoldCmdListener( 1692): CommandListener::AsecCmd::runCommand -> --
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
W/WifiStateTracker( 1864): getNetworkInfo : NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
D/PowerManagerService( 1864): lightSensorChangedLocked 263
D/PowerManagerService( 1864): lcdValue 130
D/PowerManagerService( 1864): buttonValue 0
D/PowerManagerService( 1864): keyboardValue 0
D/PowerManagerService( 1864): lightSensorChangedLocked : mKeyboardLight : 0
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/Watchdog( 1864): [email protected] 10815
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
I/InputDispatcher( 1864): Application is not responding: AppWindowToken{42893f90 token=Token{425f35c0 ActivityRecord{41998280 com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher}}}. 20019.5ms since event, 20018.6ms since wait started
I/InputDispatcher( 1864): [JUST INFO] cannot print log on outbound queue because current's inputChannel is null
I/WindowManager( 1864): Input event dispatching timed out sending to application AppWindowToken{42893f90 token=Token{425f35c0 ActivityRecord{41998280 com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher}}}
D/PowerManagerService( 1864): lightSensorChangedLocked 264
D/PowerManagerService( 1864): lcdValue 130
D/PowerManagerService( 1864): buttonValue 0
D/PowerManagerService( 1864): keyboardValue 0
D/PowerManagerService( 1864): lightSensorChangedLocked : mKeyboardLight : 0
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
I/dumpstate(24985): done
I/SurfaceFlinger( 1699): id=6401(10) createSurface 0x409d4 (800x1280),1 flag=400
V/WindowManager( 1864): rotationForOrientationLw(orient=1, last=0); user=0 mLidOpen=-1 mDockMode=0 mHdmiPlugged=false mAccelerometerDefault=1 sensorRotation=-1
D/BatteryService( 1864): update start
D/BatteryService( 1864): level:100 scale:100 status:2 health:2 present:true voltage: 4200 temperature: 330 technology: Li-ion AC powered:false USB powered:true icon:17302836 invalid charger:0
I/power ( 1864): *** release_dvfs_lock : lockType : 1
D/PowerManagerService( 1864): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 1864): mDVFSLock.release()
I/Process ( 1864): Sending signal. PID: 22653 SIG: 3
I/dalvikvm(22653): threadid=3: reacting to signal 3
I/SurfaceFlinger( 1699): id=6402(1001) createSurface 0x4992c (1x1),1 flag=0
I/dalvikvm(22653): Wrote stack traces to '/data/anr/traces.txt'
W/ActivityManager( 1864): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 1864): Activity idle timeout for r
I/Process ( 1864): Sending signal. PID: 1864 SIG: 3
I/dalvikvm( 1864): threadid=3: reacting to signal 3
D/STATUSBAR-BatteryController( 1995): onReceive() - ACTION_BATTERY_CHANGED
D/STATUSBAR-BatteryController( 1995): onReceive() - level:100
D/STATUSBAR-BatteryController( 1995): onReceive() - plugged:2
D/STATUSBAR-BatteryController( 1995): onReceive() - BATTERY_STATUS_CHARGING:
D/KeyguardUpdateMonitor( 1864): received broadcast android.intent.action.BATTERY_CHANGED
D/KeyguardUpdateMonitor( 1864): handleBatteryUpdate
D/WifiService( 1864): ACTION_BATTERY_CHANGED pluggedType: 2
D/UiModeManager( 1864): mLastBroadcastState = 0mCarModeEnabled = falseisDeskDockState(mDockState) = false
V/UiModeManager( 1864): updateLocked: null action, mDockState=0, firing homeIntent: null
D/UiModeManager( 1864): updateConfigurationLocked: mDockState=0; mCarMode=false; mNightMode=0; uiMode=17
I/dalvikvm( 1864): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1864): Sending signal. PID: 1995 SIG: 3
I/dalvikvm( 1995): threadid=3: reacting to signal 3
I/dalvikvm( 1995): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1864): Sending signal. PID: 2144 SIG: 3
I/dalvikvm( 2144): threadid=3: reacting to signal 3
I/dalvikvm( 2144): Wrote stack traces to '/data/anr/traces.txt'
D/dalvikvm( 1864): GC_CONCURRENT freed 903K, 37% free 28953K/45767K, paused 3ms+10ms
D/dalvikvm( 1864): JIT code cache reset in 4 ms (1048452 bytes 179/0)
D/dalvikvm( 1864): GC_EXPLICIT freed 1138K, 36% free 29363K/45767K, paused 3ms+11ms
E/AlarmManagerService( 1864): android_server_AlarmManagerService_set to type=1, 1339719586.394000000
W/ResourceType( 1864): Skipping entry 0x7f040021 in package table 0 because it is not complex!
E/DataRouter( 1697): usb connection is true
E/DataRouter( 1697): DSR is ON. Don't send DTR ON.
I/InputDispatcher( 1864): Delivering touch to current input target: action: 0
E/ActivityManager( 1864): ANR in android.process.acore (com.gau.go.launcherex/com.jiubang.ggheart.apps.desks.diy.GoLauncher)
E/ActivityManager( 1864): Reason: keyDispatchingTimedOut
E/ActivityManager( 1864): Load: 0.53 / 0.51 / 0.4
E/ActivityManager( 1864): CPU usage from 31698ms to 0ms ago:
E/ActivityManager( 1864): 2.3% 1864/system_server: 1.7% user + 0.5% kernel / faults: 1778 minor 3 major
E/ActivityManager( 1864): 1.8% 22653/android.process.acore: 1.7% user + 0.1% kernel / faults: 145 minor 1 major
E/ActivityManager( 1864): 1.3% 24959/logcat: 0.6% user + 0.6% kernel
E/ActivityManager( 1864): 0.6% 1711/adbd: 0.1% user + 0.5% kernel / faults: 4 minor
E/ActivityManager( 1864): 0.4% 1699/surfaceflinger: 0.2% user + 0.1% kernel / faults: 186 minor
E/ActivityManager( 1864): 0.4% 23081/kworker/0:3: 0% user + 0.4% kernel
E/ActivityManager( 1864): 0.2% 3645/com.vlingo.client.samsung: 0.1% user + 0% kernel / faults: 10 minor
E/ActivityManager( 1864): 0.2% 910/mmcqd/0: 0% user + 0.2% kernel
E/ActivityManager( 1864): 0% 1692/vold: 0% user + 0% kernel / faults: 21 minor
E/ActivityManager( 1864): 0% 23943/logcat: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 1703/gpsd: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 1995/com.android.systemui: 0% user + 0% kernel / faults: 9 minor
E/ActivityManager( 1864): 0% 17118/kworker/u:3: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 22271/kworker/u:1: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 2/kthreadd: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 816/irq/356-mxt540e: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 1686/jbd2/mmcblk0p10: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 1697/drexe: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 1700/zygote: 0% user + 0% kernel / faults: 51 minor
E/ActivityManager( 1864): 0% 1991/dhd_dpc: 0% user + 0% kernel
E/ActivityManager( 1864): 0% 2041/wpa_supplicant: 0% user + 0% kernel / faults: 3 minor
E/ActivityManager( 1864): 0% 2121/com.swype.android.inputmethod: 0% user + 0% kernel / faults: 113 minor
E/ActivityManager( 1864): 0% 2144/com.android.phone: 0% user + 0% kernel
E/ActivityManager( 1864): +0% 24971/net.whatsbeef.animationtest: 0% user + 0% kernel
E/ActivityManager( 1864): 14% TOTAL: 7.7% user + 6.2% kernel + 0.3% iowait + 0% softirq
E/ActivityManager( 1864): CPU usage from 669ms to 1192ms later:
E/ActivityManager( 1864): 37% 1864/system_server: 26% user + 10% kernel / faults: 525 minor
E/ActivityManager( 1864): 10% 1920/WindowManager: 10% user + 0% kernel
E/ActivityManager( 1864): 10% 1925/InputDispatcher: 1.7% user + 8.9% kernel
E/ActivityManager( 1864): 8.9% 1869/Compiler: 8.9% user + 0% kernel
E/ActivityManager( 1864): 3.5% 1902/ActivityManager: 3.5% user + 0% kernel
E/ActivityManager( 1864): 1.7% 1874/Binder Thread #: 0% user + 1.7% kernel
E/ActivityManager( 1864): 1.7% 2133/Binder Thread #: 1.7% user + 0% kernel
E/ActivityManager( 1864): 1.7% 2697/Binder Thread #: 1.7% user + 0% kernel
E/ActivityManager( 1864): 1.7% 5150/er$SensorThread: 1.7% user + 0% kernel
E/ActivityManager( 1864): 18% 22653/android.process.acore: 18% user + 0% kernel / faults: 121 minor
E/ActivityManager( 1864): 10% 22653/d.process.acore: 10% user + 0% kernel
E/ActivityManager( 1864): 6.6% 22768/XAEngine_ticker: 6.6% user + 0% kernel
E/ActivityManager( 1864): 1.6% 22677/d.process.acore: 1.6% user + 0% kernel
E/ActivityManager( 1864): 10% 1699/surfaceflinger: 4% user + 6.1% kernel
E/ActivityManager( 1864): 5.1% 1809/SurfaceFlinger: 4% user + 1% kernel
E/ActivityManager( 1864): 2% 7474/Binder Thread #: 0% user + 2% kernel
E/ActivityManager( 1864): 1% 1820/SurfaceFlinger: 0% user + 1% kernel
E/ActivityManager( 1864): 1% 1835/Binder Thread #: 0% user + 1% kernel
E/ActivityManager( 1864): 1% 7661/Binder Thread #: 0% user + 1% kernel
E/ActivityManager( 1864): 1.1% 17118/kworker/u:3: 0% user + 1.1% kernel
E/ActivityManager( 1864): +0% 25233/kworker/1:1: 0% user + 0% kernel
E/ActivityManager( 1864): 41% TOTAL: 31% user + 10% kernel
I/InputDispatcher( 1864): Delivering touch to current input target: action: 0
I/InputDispatcher( 1864): Delivering touch to current input target: action: 0
W/SIP ( 2121): IInputMethodWrapper. mCaller.executeOrSendMessage(MSG_UPDATE_WACOM_STATE)
W/SIP ( 2121): IInputMethodWrapper. inputMethod.updateWacomState(msg.arg1). arg1 =0
E/android.os.Debug( 1864): [email protected] > dumpstate -k -t -z -d -o /data/log/dumpstate_app_anr
I/dumpstate(25235): Check if stand-alone
I/dumpstate(25235): begin
D/PowerManagerService( 1864): lightSensorChangedLocked 284
D/PowerManagerService( 1864): lcdValue 130
D/PowerManagerService( 1864): buttonValue 0
D/PowerManagerService( 1864): keyboardValue 0
D/PowerManagerService( 1864): lightSensorChangedLocked : mKeyboardLight : 0
I've got GO Launcher as the launcher here, which apparently did the ANR, but exactly the same thing happens with the stock twlauncher. I don't think the launcher is at fault here, but I don't really know. This is extremely frustrating when developing apps, obviously. Does anyone else get this behaviour? I'm on XXLPY, no root, never rooted, only stock roms. Any help?

[Q] Misterious wakelock TIME_TICK and AudioOut_3, not even Google can save me

Here's the "dumpsys alarm":
Code:
Current Alarm Manager state:
Realtime wakeup (now=2013-09-02 18:09:01):
RTC_WAKEUP #4: Alarm{414e7b30 type 0 com.google.android.gsf}
type=0 originalType=0 when=+6d0h56m41s99ms repeatInterval=583916000 count=0
operation=PendingIntent{4267f4c8: PendingIntentRecord{425d9de8 com.google.android.gsf broadcastIntent}}
RTC_WAKEUP #3: Alarm{413be8c0 type 0 com.google.android.gms}
type=0 originalType=0 when=+3d16h58m7s206ms repeatInterval=0 count=0
operation=PendingIntent{42681458: PendingIntentRecord{413260e8 com.google.android.gms broadcastIntent}}
RTC_WAKEUP #2: Alarm{414d0f30 type 0 com.android.providers.calendar}
type=0 originalType=0 when=+15h51m34s514ms repeatInterval=0 count=0
operation=PendingIntent{413c4af8: PendingIntentRecord{415a2dc8 com.android.providers.calendar broadcastIntent}}
RTC_WAKEUP #1: Alarm{43046b68 type 0 com.google.android.gms}
type=0 originalType=0 when=+8h18m32s487ms repeatInterval=86400000 count=0
operation=PendingIntent{4179b6a8: PendingIntentRecord{4302bd38 com.google.android.gms startService}}
RTC_WAKEUP #0: Alarm{426f0c38 type 0 com.google.android.gsf}
type=0 originalType=0 when=+9m41s963ms repeatInterval=1800000 count=0
operation=PendingIntent{414d35e8: PendingIntentRecord{41472648 com.google.android.gsf broadcastIntent}}
RTC #15: Alarm{42f69828 type 1 com.sonyericsson.updatecenter}
type=1 originalType=1 when=+6d18h0m29s607ms repeatInterval=0 count=0
operation=PendingIntent{4304e200: PendingIntentRecord{42ec1cf8 com.sonyericsson.updatecenter broadcastIntent}}
RTC #14: Alarm{42861128 type 1 com.google.android.partnersetup}
type=1 originalType=0 when=+6d17h50m19s341ms repeatInterval=0 count=0
operation=PendingIntent{41632128: PendingIntentRecord{42641a00 com.google.android.partnersetup startService}}
RTC #13: Alarm{4264c900 type 1 com.facebook.katana}
type=1 originalType=1 when=+23h47m35s708ms repeatInterval=0 count=0
operation=PendingIntent{41408f00: PendingIntentRecord{42656ca0 com.facebook.katana broadcastIntent}}
RTC #12: Alarm{414358d0 type 1 com.android.vending}
type=1 originalType=0 when=+17h50m57s858ms repeatInterval=0 count=0
operation=PendingIntent{41470688: PendingIntentRecord{4143fe20 com.android.vending startService}}
RTC #11: Alarm{426bdd78 type 1 com.sonymobile.mx.android}
type=1 originalType=0 when=+17h50m33s728ms repeatInterval=86400000 count=0
operation=PendingIntent{42629e20: PendingIntentRecord{426d47b8 com.sonymobile.mx.android broadcastIntent}}
RTC #10: Alarm{414afbc0 type 1 android}
type=1 originalType=1 when=+5h50m58s849ms repeatInterval=0 count=0
operation=PendingIntent{414f4b68: PendingIntentRecord{41501178 android broadcastIntent}}
RTC #9: Alarm{412ec378 type 1 com.android.calendar}
type=1 originalType=1 when=+5h50m58s849ms repeatInterval=0 count=0
operation=PendingIntent{42bad3d8: PendingIntentRecord{4272d518 com.android.calendar broadcastIntent}}
RTC #8: Alarm{42b87198 type 1 com.sonyericsson.extras.liveware}
type=1 originalType=0 when=+3h50m58s849ms repeatInterval=0 count=0
operation=PendingIntent{4245f7d0: PendingIntentRecord{43020e68 com.sonyericsson.extras.liveware startService}}
RTC #7: Alarm{42c70e30 type 1 com.android.chrome}
type=1 originalType=1 when=+3h41m25s509ms repeatInterval=18000000 count=0
operation=PendingIntent{431ae5a0: PendingIntentRecord{42ec9568 com.android.chrome startService}}
RTC #6: Alarm{42ce2718 type 1 com.facebook.katana}
type=1 originalType=1 when=+2h49m36s494ms repeatInterval=10800000 count=0
operation=PendingIntent{42bcf5c0: PendingIntentRecord{42c10710 com.facebook.katana startService}}
RTC #5: Alarm{42b88d38 type 1 com.google.android.googlequicksearchbox}
type=1 originalType=0 when=+1h53m21s49ms repeatInterval=0 count=0
operation=PendingIntent{426aa9e0: PendingIntentRecord{426d9490 com.google.android.googlequicksearchbox startService}}
RTC #4: Alarm{426ac148 type 1 com.android.chrome}
type=1 originalType=1 when=+13m27s864ms repeatInterval=0 count=0
operation=PendingIntent{42689d88: PendingIntentRecord{426b0d58 com.android.chrome broadcastIntent}}
RTC #3: Alarm{426a9d58 type 1 com.android.chrome}
type=1 originalType=1 when=+10m33s813ms repeatInterval=0 count=0
operation=PendingIntent{426b2ff8: PendingIntentRecord{426b2fc0 com.android.chrome broadcastIntent}}
RTC #2: Alarm{42656e40 type 1 com.facebook.katana}
type=1 originalType=0 when=+7m7s975ms repeatInterval=0 count=0
operation=PendingIntent{42eb42e0: PendingIntentRecord{4196baf0 com.facebook.katana broadcastIntent}}
RTC #1: Alarm{42656d88 type 1 com.facebook.katana}
type=1 originalType=0 when=+4m36s494ms repeatInterval=900000 count=0
operation=PendingIntent{42b32690: PendingIntentRecord{42460050 com.facebook.katana broadcastIntent}}
RTC #0: Alarm{42fa5b80 type 1 com.facebook.katana}
type=1 originalType=0 when=+8s324ms repeatInterval=0 count=0
operation=PendingIntent{42fdd4e0: PendingIntentRecord{415893b8 com.facebook.katana broadcastIntent}}
Elapsed realtime wakeup (now=+6h10m23s538ms):
ELAPSED_WAKEUP #6: Alarm{41947850 type 2 com.google.android.gms}
type=2 originalType=2 when=+20d21h26m51s185ms repeatInterval=0 count=0
operation=PendingIntent{4182d170: PendingIntentRecord{4194af60 com.google.android.gms startService}}
ELAPSED_WAKEUP #5: Alarm{42ec5c78 type 2 com.google.android.gms}
type=2 originalType=2 when=+20d21h26m51s3ms repeatInterval=0 count=0
operation=PendingIntent{42821328: PendingIntentRecord{42ec7b70 com.google.android.gms startService}}
ELAPSED_WAKEUP #4: Alarm{43075990 type 2 com.google.android.gms}
type=2 originalType=2 when=+20d21h26m50s487ms repeatInterval=0 count=0
operation=PendingIntent{41622628: PendingIntentRecord{430758f0 com.google.android.gms startService}}
ELAPSED_WAKEUP #3: Alarm{428133b0 type 2 android}
type=2 originalType=2 when=+18h4m36s462ms repeatInterval=86400000 count=0
operation=PendingIntent{4152a988: PendingIntentRecord{41320c20 android broadcastIntent}}
ELAPSED_WAKEUP #2: Alarm{432c4800 type 2 android}
type=2 originalType=2 when=+1h51m57s782ms repeatInterval=0 count=0
operation=PendingIntent{412501c0: PendingIntentRecord{4123fa48 android broadcastIntent}}
ELAPSED_WAKEUP #1: Alarm{42573300 type 2 android}
type=2 originalType=2 when=+10m49s404ms repeatInterval=0 count=0
operation=PendingIntent{418c2b70: PendingIntentRecord{4263a680 android broadcastIntent}}
ELAPSED_WAKEUP #0: Alarm{42571b40 type 2 com.google.android.gsf}
type=2 originalType=2 when=+9m43s832ms repeatInterval=0 count=0
operation=PendingIntent{4126fa70: PendingIntentRecord{42b31e58 com.google.android.gsf broadcastIntent}}
ELAPSED #20: Alarm{426271e8 type 3 com.ea.games.r3_na}
type=3 originalType=3 when=+29d4h43m10s41ms repeatInterval=0 count=0
operation=PendingIntent{42638ed0: PendingIntentRecord{4262e120 com.ea.games.r3_na startService}}
ELAPSED #19: Alarm{42ecea90 type 3 com.google.android.talk}
type=3 originalType=2 when=+21h34m36s462ms repeatInterval=86400000 count=1
operation=PendingIntent{42fa5c10: PendingIntentRecord{42ecea18 com.google.android.talk broadcastIntent}}
ELAPSED #18: Alarm{4146afb8 type 3 com.google.android.talk}
type=3 originalType=2 when=+20h19m36s462ms repeatInterval=86400000 count=1
operation=PendingIntent{412af170: PendingIntentRecord{414724b8 com.google.android.talk broadcastIntent}}
ELAPSED #17: Alarm{42ee62d8 type 3 com.google.android.talk}
type=3 originalType=2 when=+19h4m36s462ms repeatInterval=86400000 count=1
operation=PendingIntent{427280f8: PendingIntentRecord{42ee61e8 com.google.android.talk broadcastIntent}}
ELAPSED #16: Alarm{42bd7288 type 3 com.facebook.katana}
type=3 originalType=3 when=+11h49m36s462ms repeatInterval=43200000 count=1
operation=PendingIntent{42c162c8: PendingIntentRecord{42c16250 com.facebook.katana startService}}
ELAPSED #15: Alarm{415a3cb0 type 3 com.android.phone}
type=3 originalType=3 when=+2h4m36s462ms repeatInterval=28800000 count=0
operation=PendingIntent{41540918: PendingIntentRecord{417df750 com.android.phone broadcastIntent}}
ELAPSED #14: Alarm{43154268 type 3 com.facebook.katana}
type=3 originalType=3 when=+48m55s380ms repeatInterval=0 count=0
operation=PendingIntent{42bed658: PendingIntentRecord{431541c8 com.facebook.katana startService}}
ELAPSED #13: Alarm{42feb0e0 type 3 com.google.android.googlequicksearchbox}
type=3 originalType=2 when=+22m46s358ms repeatInterval=1811284 count=1
operation=PendingIntent{430630d8: PendingIntentRecord{4167ae98 com.google.android.googlequicksearchbox startService}}
ELAPSED #12: Alarm{418658f8 type 3 android}
type=3 originalType=3 when=+7m52s635ms repeatInterval=0 count=0
operation=PendingIntent{41828670: PendingIntentRecord{4137afe0 android broadcastIntent}}
ELAPSED #11: Alarm{430dd1f8 type 3 com.google.android.googlequicksearchbox}
type=3 originalType=2 when=+4m37s505ms repeatInterval=0 count=0
operation=PendingIntent{43098160: PendingIntentRecord{430e30c0 com.google.android.googlequicksearchbox startService}}
ELAPSED #10: Alarm{432bd3f8 type 3 com.google.android.talk}
type=3 originalType=2 when=+4m36s462ms repeatInterval=86400000 count=0
operation=PendingIntent{431f7838: PendingIntentRecord{432bdd88 com.google.android.talk broadcastIntent}}
ELAPSED #9: Alarm{431f1180 type 3 com.sonymobile.androidapp.diagnostics}
type=3 originalType=3 when=+4m36s462ms repeatInterval=3600000 count=1
operation=PendingIntent{416f8760: PendingIntentRecord{427c4940 com.sonymobile.androidapp.diagnostics broadcastIntent}}
ELAPSED #8: Alarm{42fe1940 type 3 com.sonyericsson.devicemonitor}
type=3 originalType=3 when=+4m36s462ms repeatInterval=3600000 count=1
operation=PendingIntent{42ff9600: PendingIntentRecord{42fed038 com.sonyericsson.devicemonitor startService}}
ELAPSED #7: Alarm{412e3c18 type 3 android}
type=3 originalType=3 when=+4m36s462ms repeatInterval=1800000 count=1
operation=PendingIntent{4177fab8: PendingIntentRecord{412e2a18 android broadcastIntent}}
ELAPSED #6: Alarm{43238d08 type 3 com.google.android.talk}
type=3 originalType=2 when=+4m36s462ms repeatInterval=86400000 count=0
operation=PendingIntent{431dee38: PendingIntentRecord{4323abc0 com.google.android.talk broadcastIntent}}
ELAPSED #5: Alarm{430e3fb8 type 3 com.facebook.katana}
type=3 originalType=3 when=+4m36s462ms repeatInterval=43200000 count=0
operation=PendingIntent{430bd8f0: PendingIntentRecord{425cdc10 com.facebook.katana startService}}
ELAPSED #4: Alarm{43121960 type 3 com.facebook.katana}
type=3 originalType=3 when=+4m36s462ms repeatInterval=86400000 count=0
operation=PendingIntent{431434b0: PendingIntentRecord{425f5a50 com.facebook.katana startService}}
ELAPSED #3: Alarm{414abfe8 type 3 com.google.android.googlequicksearchbox}
type=3 originalType=2 when=+4m34s643ms repeatInterval=896985 count=1
operation=PendingIntent{415059b0: PendingIntentRecord{414abf78 com.google.android.googlequicksearchbox broadcastIntent}}
ELAPSED #2: Alarm{413c5928 type 3 com.android.phone}
type=3 originalType=3 when=+3m17s313ms repeatInterval=0 count=0
operation=PendingIntent{413d9e50: PendingIntentRecord{41494ba0 com.android.phone broadcastIntent}}
ELAPSED #1: Alarm{41361720 type 3 com.sonymobile.storagechecker}
type=3 originalType=3 when=+2m13s84ms repeatInterval=300000 count=1
operation=PendingIntent{41361710: PendingIntentRecord{4282fa30 com.sonymobile.storagechecker startService}}
ELAPSED #0: Alarm{431d7748 type 3 android}
type=3 originalType=3 when=+58s817ms repeatInterval=0 count=0
operation=PendingIntent{414f4e70: PendingIntentRecord{41500f88 android broadcastIntent}}
Broadcast ref count: 0
Top Alarms:
+33s924ms running, 0 wakeups, 272 alarms: android
act=android.intent.action.TIME_TICK
+10s762ms running, 1 wakeups, 1 alarms: com.android.providers.calendar
act=com.android.providers.calendar.intent.CalendarProvider2
+8s380ms running, 0 wakeups, 371 alarms: com.android.chrome
cmp={com.android.chrome/com.google.ipc.invalidation.ticl.android2.AndroidInternalScheduler$AlarmReceiver}
+6s64ms running, 0 wakeups, 197 alarms: com.android.phone
act=com.android.internal.telephony.gprs-data-stall
+4s494ms running, 0 wakeups, 32 alarms: android
act=com.android.server.ThrottleManager.action.POLL
+3s77ms running, 0 wakeups, 12 alarms: android
act=com.android.server.action.NETWORK_STATS_POLL
+2s443ms running, 0 wakeups, 554 alarms: com.android.chrome
cmp={com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver}
+2s357ms running, 0 wakeups, 24 alarms: com.google.android.googlequicksearchbox
act=com.google.android.apps.sidekick.calendar.CalendarIntentService.UPDATE_CALENDAR_ACTION cmp={com.google.android.googlequicksearchbox/com.google.android.apps.sidekick.calendar.CalendarIntentService$CalendarReceiver}
+1s684ms running, 0 wakeups, 6 alarms: com.sonymobile.androidapp.diagnostics
cmp={com.sonymobile.androidapp.diagnostics/com.sonymobile.androidapp.diagnostics.service.Alarm}
+1s584ms running, 0 wakeups, 66 alarms: com.sonymobile.storagechecker
act=com.sonymobile.storagechecker.intent.action.ALARM_EXPIRED cmp={com.sonymobile.storagechecker/com.sonymobile.storagechecker.controller.DeviceStorageService}
Alarm Stats:
com.sonymobile.androidapp.diagnostics +1s684ms running, 0 wakeups:
+1s684ms 0 wakes 6 alarms: cmp={com.sonymobile.androidapp.diagnostics/com.sonymobile.androidapp.diagnostics.service.Alarm}
com.google.android.talk +455ms running, 0 wakeups:
+450ms 0 wakes 3 alarms: act=com.google.android.apps.babel.CLEANUP_DB
+5ms 0 wakes 1 alarms: act=com.google.android.apps.babel.UPDATE_NOTIFICATION
android +37s882ms running, 98 wakeups:
+33s924ms 0 wakes 272 alarms: act=android.intent.action.TIME_TICK
+4s494ms 0 wakes 32 alarms: act=com.android.server.ThrottleManager.action.POLL
+3s77ms 0 wakes 12 alarms: act=com.android.server.action.NETWORK_STATS_POLL
+1s448ms 91 wakes 91 alarms: act=android.content.syncmanager.SYNC_ALARM
+710ms 0 wakes 6 alarms: act=com.android.server.WifiManager.action.START_SCAN
+184ms 3 wakes 3 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
+147ms 4 wakes 4 alarms: act=android.net.wifi.DHCP_RENEW
com.sonymobile.superstamina +699ms running, 16 wakeups:
+699ms 16 wakes 16 alarms: act=com.sonymobile.SUPER_STAMINA_POWER_STATE_TIMEOUT
com.oasisfeng.greenify +394ms running, 7 wakeups:
+394ms 7 wakes 7 alarms: act=com.oasisfeng.greenify.CLEAN_NOW
com.android.phone +6s64ms running, 0 wakeups:
+6s64ms 0 wakes 197 alarms: act=com.android.internal.telephony.gprs-data-stall
com.sonyericsson.updatecenter +162ms running, 0 wakeups:
+149ms 0 wakes 1 alarms: act=com.sonyericsson.updatecenter.action.SYNCHRONIZE_ALL
+13ms 0 wakes 1 alarms: act=com.sonyericsson.updatecenter.action.BOOT_COMPLETE
com.google.android.gsf +3s734ms running, 44 wakeups:
+1s425ms 17 wakes 17 alarms: act=com.google.android.intent.action.SEND_IDLE
+1s76ms 9 wakes 9 alarms: act=com.google.android.intent.action.MCS_HEARTBEAT
+1s71ms 12 wakes 12 alarms: cmp={com.google.android.gsf/com.google.android.gsf.checkin.EventLogService$Receiver}
+162ms 6 wakes 6 alarms: act=com.google.android.intent.action.GTALK_RECONNECT
com.facebook.katana +1s58ms running, 0 wakeups:
+934ms 0 wakes 11 alarms: act=com.facebook.common.executors.WakingExecutorService.ACTION_ALARM
+78ms 0 wakes 2 alarms: act=com.facebook.orca.database.ACTION_ALARM cmp={com.facebook.katana/com.facebook.contacts.database.AddressBookPeriodicRunner$LocalBroadcastReceiver}
+31ms 0 wakes 3 alarms: cmp={com.facebook.katana/com.facebook.katana.service.BackgroundDetectionService}
+16ms 0 wakes 1 alarms: cmp={com.facebook.katana/com.facebook.katana.service.PhotoCleanupService}
+3ms 0 wakes 1 alarms: act=com.facebook.katana.service.5 cmp={com.facebook.katana/com.facebook.katana.service.FacebookService}
0 0 wakes 1 alarms: act=com.facebook.katana.service.4 cmp={com.facebook.katana/com.facebook.katana.service.FacebookService}
com.google.android.googlequicksearchbox +2s915ms running, 0 wakeups:
+2s357ms 0 wakes 24 alarms: act=com.google.android.apps.sidekick.calendar.CalendarIntentService.UPDATE_CALENDAR_ACTION cmp={com.google.android.googlequicksearchbox/com.google.android.apps.sidekick.calendar.CalendarIntentService$CalendarReceiver}
+799ms 0 wakes 23 alarms: cmp={com.google.android.googlequicksearchbox/com.google.android.apps.sidekick.TrafficIntentService}
+498ms 0 wakes 12 alarms: act=com.google.android.apps.sidekick.REFRESH cmp={com.google.android.googlequicksearchbox/com.google.android.apps.sidekick.EntriesRefreshIntentService}
+293ms 0 wakes 3 alarms: cmp={com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service}
com.android.chrome +10s754ms running, 0 wakeups:
+8s380ms 0 wakes 371 alarms: cmp={com.android.chrome/com.google.ipc.invalidation.ticl.android2.AndroidInternalScheduler$AlarmReceiver}
+2s443ms 0 wakes 554 alarms: cmp={com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver}
+6ms 0 wakes 1 alarms: act=com.google.android.apps.chrome.omaha.ACTION_REGISTER_REQUEST cmp={com.android.chrome/com.google.android.apps.chrome.omaha.OmahaClient}
com.android.vending +130ms running, 0 wakeups:
+123ms 0 wakes 7 alarms: cmp={com.android.vending/com.google.android.finsky.services.ContentSyncService}
+7ms 0 wakes 1 alarms: cmp={com.android.vending/com.google.android.finsky.services.DailyHygiene}
com.sonymobile.storagechecker +1s584ms running, 0 wakeups:
+1s584ms 0 wakes 66 alarms: act=com.sonymobile.storagechecker.intent.action.ALARM_EXPIRED cmp={com.sonymobile.storagechecker/com.sonymobile.storagechecker.controller.DeviceStorageService}
com.android.providers.calendar +10s762ms running, 1 wakeups:
+10s762ms 1 wakes 1 alarms: act=com.android.providers.calendar.intent.CalendarProvider2
com.sonyericsson.devicemonitor +164ms running, 0 wakeups:
+164ms 0 wakes 5 alarms: act=com.sonyericsson.devicemonitor.TICK cmp={com.sonyericsson.devicemonitor/com.sonyericsson.devicemonitor.DeviceMonitorService}
com.google.android.gms +1s367ms running, 18 wakeups:
+1s367ms 18 wakes 18 alarms: act=com.google.android.intent.action.SEND_IDLE
Super Stamina debug info:
SuperStaminaEnabled=true
SuperStaminaIsPowerState0=true
WakelockIsTakenInStaminaMode=false
Internal Whitelist (11 items):
com.sonyericsson.organizer
android
com.sonymobile.superstamina
com.sonymobile.smallapps.timer
com.sonyericsson.secureclockservice
com.sonyericsson.android.mbt.power
com.sonymobile.provider.tasks
jp.co.fsi.fs1seg
com.android.providers.calendar
com.sonyericsson.android.mbt.powerinstrumentation
com.sonyericsson.android.wakeup
User Whitelist (4 items):
10083
10218
10049
10050
1. TIME_TICK is killing my battery, Wakelock Detector shows that AlarmManager-Launch under Android System has some thousands wakelocks.
2. AudioOut_3 is still going off even though I turn off all the touch screen sound/pad sound and after screen off.
STAMINA whitelisted Gmail, Greenify, and Shadowsocks.

Well as you googled you probably found this thread *click me* for TIME_TICK and this one *click me* for AudioOut_3...
in there they tell multiple ways to avoid those wakelocks or at least discribe why they're happening.
If you didn't find those, I hope those two links will help you

FSN said:
Well as you googled you probably found this thread *click me* for TIME_TICK and this one *click me* for AudioOut_3...
in there they tell multiple ways to avoid those wakelocks or at least discribe why they're happening.
If you didn't find those, I hope those two links will help you
Click to expand...
Click to collapse
I DID look over those posts, however:
1. The TIME_TICK wakelock is still there. I tried freezing any app that will/might wake up when the screen is off, even stock alarm/clock, but it does not make it stop ticking.
2. The AudioOut_3 is a dead loop. I turned off every sound that my phone can possibly make, and deleted every app in "dumpsys audio", but no, it's still ticking.

i should point out that you also have chrome wakes :
+8s380ms 0 wakes 371 alarms: cmp={com.android.chrome/com.google.ipc.invalidation.ticl.android2.AndroidInternalScheduler$AlarmReceiver}
+2s443ms 0 wakes 554 alarms: cmp={com.android.chrome/com.google.ipc.invalidation.external.client.contrib.AndroidListener$AlarmReceiver}
any weird widgets for clocks or alarms ?
maybe one of your whitelisted apps are doing this

Screen blinks every 10 seconds for 1/2 second, WTF?

Here is the Logcat. I flashed a factory image, totally redone everything from scratch, still it persists...
01-19 22:00:11.415 280: 280 W/qdhwcomposer ]
hwc_prepare: panel is in bad state. reset the panel
[ 01-19 22:00:11.416 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode off
[ 01-19 22:00:11.416 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 0 on display: 0
[ 01-19 22:00:11.699 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 0
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 0 on display 0
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode normal and enabling vsync
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 2 on display: 0
[ 01-19 22:00:11.968 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 1
[ 01-19 22:00:11.970 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 2 on display 0
[ 01-19 22:00:20.011 280: 339 I/qdhwcomposer ]
getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0
[ 01-19 22:00:20.021 280: 280 W/qdhwcomposer ]
hwc_prepare: panel is in bad state. reset the panel
[ 01-19 22:00:20.021 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode off
[ 01-19 22:00:20.021 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 0 on display: 0
[ 01-19 22:00:20.333 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 0
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 0 on display 0
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode normal and enabling vsync
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 2 on display: 0
[ 01-19 22:00:20.592 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 1
[ 01-19 22:00:20.594 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 2 on display 0
[ 01-19 22:00:28.605 280: 339 I/qdhwcomposer ]
getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0

Have you found any solution to this problem ?
Kevinyaheard said:
Here is the Logcat. I flashed a factory image, totally redone everything from scratch, still it persists...
01-19 22:00:11.415 280: 280 W/qdhwcomposer ]
hwc_prepare: panel is in bad state. reset the panel
[ 01-19 22:00:11.416 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode off
[ 01-19 22:00:11.416 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 0 on display: 0
[ 01-19 22:00:11.699 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 0
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 0 on display 0
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode normal and enabling vsync
[ 01-19 22:00:11.702 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 2 on display: 0
[ 01-19 22:00:11.968 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 1
[ 01-19 22:00:11.970 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 2 on display 0
[ 01-19 22:00:20.011 280: 339 I/qdhwcomposer ]
getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0
[ 01-19 22:00:20.021 280: 280 W/qdhwcomposer ]
hwc_prepare: panel is in bad state. reset the panel
[ 01-19 22:00:20.021 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode off
[ 01-19 22:00:20.021 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 0 on display: 0
[ 01-19 22:00:20.333 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 0
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 0 on display 0
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
reset_panel: setting power mode normal and enabling vsync
[ 01-19 22:00:20.336 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Setting mode 2 on display: 0
[ 01-19 22:00:20.592 280: 340 I/qdhwcomposer ]
handle_blank_event: dpy:0 panel power state: 1
[ 01-19 22:00:20.594 280: 280 D/qdhwcomposer ]
hwc_setPowerMode: Done setting mode 2 on display 0
[ 01-19 22:00:28.605 280: 339 I/qdhwcomposer ]
getPanelResetStatus: got change event in fb0 with PANEL_ALIVE=0
Click to expand...
Click to collapse
I'm also facing the same issue

[DEV] Z5 Kernel messages & related stuff + fix(es)

The following is all on stock (out of the box), unrooted kernel + ROM
(from adb shell)
What are all those warnings, cluttering messages ... ?
Seriously Sony, You can do better than that ! :silly:
----------------------------
what is wrong with the other half of this octa-core CPU ?
Code:
dmesg | grep -i error
<3>[ 5.226418] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 5.226714] bcl_handle_hotplug: Error -1 onlining core 5
<6>[ 6.471743] subsys-pil-tz fe200000.qcom,lpass: Subsystem error monitoring/handling services are up
<6>[ 6.720171] CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0xffffffc0bb348c10
<3>[ 7.359383] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 7.359854] bcl_handle_hotplug: Error -1 onlining core 5
<6>[ 9.994728] pil-q6v5-mss fc880000.qcom,mss: Subsystem error monitoring/handling services are up
<3>[ 12.646433] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 12.646764] bcl_handle_hotplug: Error -1 onlining core 5
<3>[ 51.139961] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 51.140351] bcl_handle_hotplug: Error -1 onlining core 5
<3>[ 56.007422] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 59.416963] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 59.417713] bcl_handle_hotplug: Error -1 onlining core 6
<3>[ 59.418682] bcl_handle_hotplug: Error -1 onlining core 7
<3>[ 59.938214] bcl_handle_hotplug: Error -1 onlining core 4
<3>[ 59.938477] bcl_handle_hotplug: Error -1 onlining core 6
<3>[ 59.939182] bcl_handle_hotplug: Error -1 onlining core 7
Code:
<3>[ 113.634913] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 113.635003] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 113.635077] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 113.635167] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 113.635239] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 114.126510] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 114.127990] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 114.128127] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 114.128235] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 114.128328] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 114.128833] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 114.130425] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 114.130555] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 114.130651] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 114.130736] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 114.130825] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 114.131253] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 118.627004] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 118.627547] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 118.629118] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 118.630696] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 118.632506] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 118.635036] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 120.434214] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 120.435633] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 120.438024] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 120.439507] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 120.441429] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 120.442626] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 120.727274] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 120.729267] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 120.730679] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 120.732006] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 120.733579] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 120.736131] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 121.427916] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 121.428139] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 121.429569] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 121.429693] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 121.429801] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 121.429894] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 122.427181] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 122.427633] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 122.428097] _cpu_up: attempt to bring up CPU 6 failed
<3>[ 122.429589] bcl_handle_hotplug: Error -1 onlining core 6
<4>[ 122.430073] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 122.431584] bcl_handle_hotplug: Error -1 onlining core 7
<4>[ 130.270372] _cpu_up: attempt to bring up CPU 5 failed
<3>[ 130.270447] bcl_handle_hotplug: Error -1 onlining core 5
<4>[ 130.270528] _cpu_up: attempt to bring up CPU 7 failed
<3>[ 130.270596] bcl_handle_hotplug: Error -1 onlining core 7
[upstream, RFC, old] http://marc.info/?l=linux-arm-kernel&m=129245682806207&w=2
----------------------------
And the following looks like some usb gadget or usb f_fs related issue:
http://www.serverphorums.com/read.php?12,1379459
[FIX] ? https://lkml.org/lkml/2014/2/27/38 [PATCH] usb: gadget: return the right length in ffs_epfile_io()
Code:
<3>[16729.608668] ffs_epfile_io(): Error: returning -512 value
<3>[16729.882382] ffs_epfile_io(): Error: returning -512 value
<3>[16732.738660] ffs_epfile_io(): Error: returning -512 value
<3>[16732.969768] ffs_epfile_io(): Error: returning -512 value
<3>[16737.264389] ffs_epfile_io(): Error: returning -512 value
<3>[16737.600648] ffs_epfile_io(): Error: returning -512 value
<3>[16738.981945] ffs_epfile_io(): Error: returning -512 value
<3>[16740.424212] ffs_epfile_io(): Error: returning -512 value
<3>[16740.777312] ffs_epfile_io(): Error: returning -512 value
<3>[16741.298607] ffs_epfile_io(): Error: returning -512 value
<3>[16741.582891] ffs_epfile_io(): Error: returning -512 value
<3>[16741.929018] ffs_epfile_io(): Error: returning -512 value
----------------------------
Code:
<4>[ 5.102064] IRQ32 no longer affine to CPU5
<4>[ 5.102067] IRQ33 no longer affine to CPU5
<4>[ 5.102071] IRQ34 no longer affine to CPU5
<4>[ 5.102073] IRQ35 no longer affine to CPU5
<4>[ 5.102076] IRQ36 no longer affine to CPU5
<4>[ 5.102079] IRQ37 no longer affine to CPU5
<4>[ 5.102082] IRQ38 no longer affine to CPU5
<4>[ 5.102084] IRQ39 no longer affine to CPU5
<4>[ 5.102087] IRQ41 no longer affine to CPU5
<4>[ 5.102090] IRQ42 no longer affine to CPU5
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/303395.html
[upstream, RFC] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-September/368189.html
----------------------------
The following could point at issues in image processing (Camera)
https://android.googlesource.com/kernel/msm/+/ce7b14b30bded11fc66b80f926d5bb8be626715d^!/ (mm-camera: Implement scratch buffer support)
Code:
<3>[ 171.146938] msm_isp_get_buf: No Buffer session_id: 1 stream_id: 2
<3>[ 171.180304] msm_isp_get_buf: No Buffer session_id: 1 stream_id: 2
----------------------------
The following hints at some issues with Bluetooth headphones. Call or sound output related issues could happen (?)
Anyone had issues with stability at the end of calling ? ( https://talk.sonymobile.com/t5/Kernel/Phone-reboots-as-soon-as-call-ends/td-p/1022774 )
what phone model is this ?
Code:
<3>[ 6.683139] msm-pcm-routing qcom,msm-pcm-routing.41: ASoC: Failed to add route VOICE2_STUB_DL -> Voice2 Stub -> INTERNAL_BT_SCO_RX_Voice Mixer
<3>[ 6.840240] msm-dai-q6-dev qcom,msm-dai-q6-sb-2-rx.191: ASoC: Failed to add route SLIMBUS_2_RX -> direct -> Slimbus2 Playback
<3>[ 6.840269] msm-dai-q6-dev qcom,msm-dai-q6-sb-2-tx.192: ASoC: Failed to add route Slimbus2 Capture -> direct -> SLIMBUS_2_TX
Luckily we don't have
Code:
Unbalanced enable for IRQ
----------------------------
The following could lead to some sluggishness and/or instability:
CMA (memory fragmentation ?, exhaustion ?) issues, could in some part be related to zram & zsmalloc
( https://lkml.org/lkml/2014/11/3/559 )
Code:
<4>[ 7.398189] alloc_contig_range test_pages_isolated(c7818, c781d) failed
<4>[ 7.398626] alloc_contig_range test_pages_isolated(c7820, c7825) failed
<4>[ 7.399363] alloc_contig_range test_pages_isolated(c7828, c782d) failed
----------------------------
Code:
<4>[ 74.405171] HTB: quantum of class 10001 is big. Consider r2q change.
<4>[ 74.417974] HTB: quantum of class 10010 is big. Consider r2q change.
http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm
----------------------------
Code:
texfat: fail_safe is enabled
https://en.wikipedia.org/wiki/Transaction-Safe_FAT_File_System
Code:
<6>[ 5.829983] zram0: detected capacity change from 0 to 536870912
uh - nice ?!
----------------------------
Lol
Code:
<4>[16728.136727] _cpu_up: attempt to bring up CPU 5 failed
<4>[16728.136922] _cpu_up: attempt to bring up CPU 7 failed
<3>[16729.674537] PM: Some devices failed to suspend
<4>[16743.410363] _cpu_up: attempt to bring up CPU 4 failed
<4>[16743.410617] _cpu_up: attempt to bring up CPU 5 failed
<4>[16743.410868] _cpu_up: attempt to bring up CPU 6 failed
----------------------------
Code:
<4>[ 13.266151] ------------[ cut here ]------------
<4>[ 13.266167] WARNING: at /home/hudsonslave/root/workspace/offbuild_kitakami2-2.0.2_android_matrix/HUDSON_PRODUCT/sumire/HUDSON_VARIANT/user/label/CM_OFFBLD/kernel/include/linux/of.h:555 somc_chg_set_step_charge_params+0x108/0x11c()
<6>[ 13.266173] Modules linked in: texfat(PO) wlan(O) mhl_sii8620_8061_drv(O) ecryptfs(O) kscl(O) qdrbg_module(O) qcrypto_module(O)
<6>[ 13.266195] CPU: 0 PID: 275 Comm: kworker/0:2 Tainted: P W O 3.10.49-perf-g75e6207 #1
<6>[ 13.266205] Workqueue: events power_supply_changed_work
<6>[ 13.266209] Call trace:
<6>[ 13.266217] [<ffffffc0002069f8>] dump_backtrace+0x0/0x270
<6>[ 13.266222] [<ffffffc000206c78>] show_stack+0x10/0x1c
<6>[ 13.266230] [<ffffffc000cb2468>] dump_stack+0x1c/0x28
<6>[ 13.266238] [<ffffffc00021cc78>] warn_slowpath_common+0x74/0x9c
<6>[ 13.266243] [<ffffffc00021ce9c>] warn_slowpath_null+0x14/0x20
<6>[ 13.266249] [<ffffffc0008c8b4c>] somc_chg_set_step_charge_params+0x104/0x11c
<6>[ 13.266256] [<ffffffc0008cf994>] smbchg_external_power_changed+0x204/0x49c
<6>[ 13.266261] [<ffffffc0008b4480>] __power_supply_changed_work+0x3c/0x50
<6>[ 13.266270] [<ffffffc0005fac68>] class_for_each_device+0x80/0xa8
<6>[ 13.266275] [<ffffffc0008b4178>] power_supply_changed_work+0x84/0xdc
<6>[ 13.266282] [<ffffffc00023843c>] process_one_work+0x260/0x3c4
<6>[ 13.266287] [<ffffffc000239458>] worker_thread+0x1f8/0x348
<6>[ 13.266295] [<ffffffc00023e95c>] kthread+0xac/0xb8
<4>[ 13.266299] ---[ end trace 8fab15b750bb072b ]---
if it's similar to https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.14.19 ( bq2415x_charger: Fix Atomic Sleep Bug ) it's an Atomic Sleep Bug in the
charger handling (qpnp-smbcharger_extension* , qpnp-smbcharger ) ;
kernel/include/linux/of.h is responsible for "Definitions for talking to the Open Firmware PROM"
----------------------------

@zacharias.maladroit
There are even more warnings in the kmesg:
- Permission issues related to Super-Stamina-mode
- Kernelspace tries to copy Xloud effects but fails, as Xloud is long deprecated
Plus various bugs caused by Sony:
- sched small cluster boost issue
- broken function retval checks in the touch driver

@Tommy-Geenexus
what bothers me is that the 4 other cores don't appear to work - I doubt that it's different for the Z5c or Z5P
Comparing the battery consumption with the Note 3, the battery percentage drops at an frightening rate,
might be due to the fact that this is only the 2nd or 3rd full battery charging cycle but still:
Sony has lots of work to do,
this remembers me of the good 'ol days with the Galaxy S 1 - kernel source messy, but stuff worked pretty well,
not sure how to refer to this:
is it a software issue, hardware issue, works as intended ™ (Sony's way of utilizing the CPU differently, but why the errors) or just some WIP-state ?
Considering that this device costs ~ 700 € - this is underwhelming (well, at least for now);
I know for a fact that this will improve - but seriously: do I really have to root the device (and unlock the bootloader - since there's currently no other option !),
to get some decent battery saving performance (via e.g. XPosed & Greenify, Titanium Backup freezing) ?
I've already disabled and kicked a lot of battery consumers from the device (facebook, the other social stuff, maps, etc. etc.) - which helps significantly - but I'm still not satisfied (well, always striving for perfection )
edit:
seems like I need to check out the Z5c and Z5P kernel development, there's more kernel-related action happening there,
I'm still undecided whether to unlock the bootloader at this early stage ...

zacharias.maladroit said:
@Tommy-Geenexus
what bothers me is that the 4 other cores don't appear to work - I doubt that it's different for the Z5c or Z5P
Comparing the battery consumption with the Note 3, the battery percentage drops at an frightening rate,
might be due to the fact that this is only the 2nd or 3rd full battery charging cycle but still:
Sony has lots of work to do,
this remembers me of the good 'ol days with the Galaxy S 1 - kernel source messy, but stuff worked pretty well,
not sure how to refer to this:
is it a software issue, hardware issue, works as intended ™ (Sony's way of utilizing the CPU differently, but why the errors) or just some WIP-state ?
Considering that this device costs ~ 700 € - this is underwhelming (well, at least for now);
I know for a fact that this will improve - but seriously: do I really have to root the device (and unlock the bootloader - since there's currently no other option !),
to get some decent battery saving performance (via e.g. XPosed & Greenify, Titanium Backup freezing) ?
I've already disabled and kicked a lot of battery consumers from the device (facebook, the other social stuff, maps, etc. etc.) - which helps significantly - but I'm still not satisfied (well, always striving for perfection )
edit:
seems like I need to check out the Z5c and Z5P kernel development, there's more kernel-related action happening there,
I'm still undecided whether to unlock the bootloader at this early stage ...
Click to expand...
Click to collapse
What do you mean with "4 other Cores don't work"?
The most effective way of increasing battery life is underclocking.
The SD810 suffers from too high clocks (anything > 1.5 GHz will further increase leakage of the transistors and the power consumption roughly raises exponentially),
The cause is the manufacturing process (MOS) in 20 nm, which decreases high clocks efficiency exponentially.
You can take a look here:
https://github.com/Tommy-Geenexus/android_kernel_sony_msm8994_suzuran_5.x/commit/5ba0df5b785d17393c383041b3de88a9167d372e
Downclocking greatly helps with battery life and heat emission. After downclocking my Z5C it barely gets warm, and i can play games for 20 min without throttling.

I see the same kernel log entries related to CPU hotplug failing for cores 4-7.
It appears to be a software (kernel) issue, did anyone already bring it to Sony?
Sent from my E6653 using Tapatalk

millicent said:
I see the same kernel log entries related to CPU hotplug failing for cores 4-7.
It appears to be a software (kernel) issue, did anyone already bring it to Sony?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
I've written to Sony support, they referred to Sony Developers - not sure who to contact there (they write to post at Stack Overflow & create an account - yeah, great way, NOT )
also contacted Sony XPERIA at G+ , no response so far
Plugging appears to work (?) - that's at least what the CPU-Z app shows
CPU 7 once was enabled at 384 MHz, now the same is shown for CPU 4 - wasn't shown higher than 384 MHz
Those error messages are debug messages, even if it works with those messages, they should have been disabled in production to avoid spamming the logs and reducing load.
It's interesting that the kernel & ROM appears to use zram with 512 MB, swapping is always good - even if it's only im RAM
there are some issues with memory fragmentation when using it but upstream (Linux Kernel Devs) are working on it
Still battery consumption is weird & significantly higher than on the Note 3: watching a 720p video (3-4 minutes): 1-2% battery drop,
not sure if this is due to un-optimized kernel, software (non-efficient usage of hardware codecs) or the LCD display being more hungry than SuperAMOLED

It might be that the higher cores are severely throttled and the kernel log lines represent Sony fix for sd810..hehe
I just performed an antutu benchmark on my E6653 and on older HTC one m7, rooted but not overclocked. Only 4 cores but unlocked to 1.7 ghz.
The CPU results, especially for multicore are amazingly similar.
Here are the numbers
My z5
CPU maths 4668
CPU multicore 7272
My m7
CPU maths 4681
CPU multicore 7253
I repeated the test 3 times the numbers are consistent and the numbers above are the best I got thus far.
Sent from my E6653 using Tapatalk

Well, the thing was:
with stock kernel the Quad-core 2.0 GHz Cortex-A57 cores were seemingly not working optimally,
there only was one active at the minimal frequency of 384 MHz,
and the Quad-core 1.5 GHz Cortex-A53 was doing all the work,
the functionality is surely not optimal.
Now with the AndroPlus kernel the cores of the Quad-core 2.0 GHz Cortex-A57 part are more active,
Only 4 cores but unlocked to 1.7 ghz.
Click to expand...
Click to collapse
this refers to the 6653 ?
yes, you're clearly not getting the most out of the hardware,
the greatest part is to blame on Qualcomm, but if the hardware is limited like that (overheating issues, performance decline),
Sony needs to do more about it (they did: two heatpipes),
perhaps they can optimize it some more (same magic perhaps ? - massive underclocking during less screen activity and using the Quad-core 1.5 GHz Cortex-A53;
when doing multimedia utilizing the Quad-core 2.0 GHz Cortex-A57 but also applying some clever governors & other energy tricks beside STAMINA ?).
Hopefully they have some tricks in store with Android 6.0 ...

zacharias.maladroit said:
Well, the thing was:
with stock kernel the Quad-core 2.0 GHz Cortex-A57 cores were seemingly not working optimally,
there only was one active at the minimal frequency of 384 MHz,
and the Quad-core 1.5 GHz Cortex-A53 was doing all the work,
the functionality is surely not optimal.
Now with the AndroPlus kernel the cores of the Quad-core 2.0 GHz Cortex-A57 part are more active,
Only 4 cores but unlocked to 1.7 ghz.
this refers to the 6653 ?
yes, you're clearly not getting the most out of the hardware,
the greatest part is to blame on Qualcomm, but if the hardware is limited like that (overheating issues, performance decline),
Sony needs to do more about it (they did: two heatpipes),
perhaps they can optimize it some more (same magic perhaps ? - massive underclocking during less screen activity and using the Quad-core 1.5 GHz Cortex-A53;
when doing multimedia utilizing the Quad-core 2.0 GHz Cortex-A57 but also applying some clever governors & other energy tricks beside STAMINA ?).
Hopefully they have some tricks in store with Android 6.0 ...
Click to expand...
Click to collapse
The A57s consume roughly 4x as much power as the A53. You definitly do not want all A57s running.
Qcom made a mistake at clocking both Clusters that high. But the competition forced them to do so. As the competition uses superior manufacturing processes / targets devices with more thermal headroom SD SoCs are left behind with issues not present in comparable SoCs.

The HTC one m7 can achieve 1.7 Ghz on all cores
Sent from my E6653 using Tapatalk