Related
Well......
I got bored and built liquidsmooth for the o2x with the cm10.1 device repos. the boot.img was salvaged from cm10.1 because GCC was being stupid and not building the kernel. This is for the old bootloader.
What Works:
-User interface
-telephony
-settings
-SMS
-most things
What doesn't work:
-Home button
-lockscreen (somehow the logcat is complaining about no lockscreen)
-probably a hell of a lot of other stuff (please tell me what doesn't work)
If anyone can help me with the problems, that would be much appreciated.
Here's a logcat if you think you can fix the issue with the lockscreen: http://pastebin.com/4DBADere
Download: http://d-h.st/Qvz
Device Source and Build Instructions:
Same as CM build except edit local manifest to use JordanRulz/android_device_lge_p990 instead of the CM source,
and do
Code:
repo init -u https://github.com/LiquidSmooth/android -b jb2
instead of repo init with the CM repo.
PM Me. i can teamview you to help in fixing
Sent from my LG-P990 using Tapatalk 2
MinoochX said:
PM Me. i can teamview you to help in fixing
Sent from my LG-P990 using Tapatalk 2
Click to expand...
Click to collapse
ill upload the logcat tomorrow
Please don't use my experimental kernels in this rom. If you want to use kowalski, use a stable one. If there are problems with the exp kernels i need to track them all in the kernel thread. Can't look in all threads to see if there are reports.
About gcc being stupid... you need a compiler with graphite support. If you don't know how to compile it for yourself then use precompiled kernels from my folder...
Also would have been nice of you to pm me before using my kernel in your rom...
pengus77 said:
Please don't use my experimental kernels in this rom. If you want to use kowalski, use a stable one. If there are problems with the exp kernels i need to track them all in the kernel thread. Can't look in all threads to see if there are reports.
About gcc being stupid... you need a compiler with graphite support. If you don't know how to compile it for yourself then use precompiled kernels from my folder...
Also would have been nice of you to pm me before using my kernel in your rom...
Click to expand...
Click to collapse
The version in the flashable zip uses the CyanogenMod kernel.
JordanRulz said:
The version in the flashable zip uses the CyanogenMod kernel.
Click to expand...
Click to collapse
Oh lol sorry... i misread and thought the exp 112 in your signature was part of the op. My bad
If you want to embed the 100p5 you're welcome to do so. The CM one is buggy as hell
anyways, this is what happens with the lockscreen:
Code:
I/PowerManagerService( 823): Going to sleep by user request...
D/SurfaceFlinger( 95): Screen released, type=0 flinger=0x411d0318
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
D/dalvikvm( 823): GC_FOR_ALLOC freed 455K, 29% free 5576K/7816K, paused 29ms, total 29ms
V/NvAudioALSADevice( 98): [NVALSA] setParameters[screen_state=off]
V/NvAudioALSADevice( 98): LowPower = true
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
D/dalvikvm( 1171): GC_FOR_ALLOC freed 1539K, 37% free 5945K/9412K, paused 18ms, total 20ms
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/PowerManagerService( 823): Waking up from sleep...
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/WindowManager( 823): No lock screen!
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
V/NvAudioALSADevice( 98): [NVALSA] setParameters[screen_state=on]
V/NvAudioALSADevice( 98): LowPower = false
JordanRulz said:
anyways, this is what happens with the lockscreen:
Code:
I/PowerManagerService( 823): Going to sleep by user request...
D/SurfaceFlinger( 95): Screen released, type=0 flinger=0x411d0318
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
D/dalvikvm( 823): GC_FOR_ALLOC freed 455K, 29% free 5576K/7816K, paused 29ms, total 29ms
V/NvAudioALSADevice( 98): [NVALSA] setParameters[screen_state=off]
V/NvAudioALSADevice( 98): LowPower = true
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
D/dalvikvm( 1171): GC_FOR_ALLOC freed 1539K, 37% free 5945K/9412K, paused 18ms, total 20ms
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/PowerManagerService( 823): Waking up from sleep...
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/ ( 823): mpu3050_suspend: suspending sensors to 0000
I/ ( 823): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 823): Actual ODR: 50 Hz
I/ ( 823): mpu3050_resume: Resuming to 0070
I/WindowManager( 823): No lock screen!
E/gralloc ( 95): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
V/NvAudioALSADevice( 98): [NVALSA] setParameters[screen_state=on]
V/NvAudioALSADevice( 98): LowPower = false
Click to expand...
Click to collapse
Re obtain blobs
Sent from my GT-I8160 using xda premium
AW: [ROM] [WIP] [HELP] [4.2.2] LiquidSmooth JB for Optimus 2X
Is it possible to get this rom for new bootloader?
best regards
Craxx
Send from my Nexus 4 with Tapatalk 2
Craxx said:
Is it possible to get this rom for new bootloader?
best regards
Craxx
Send from my Nexus 4 with Tapatalk 2
Click to expand...
Click to collapse
I do not know how to port it to the new bootloader, but i will post my slightly modified device source so that anyone who knows how can do it.
AW: [ROM] [WIP] [HELP] [4.2.2] LiquidSmooth JB for Optimus 2X
That would be great when somebody could compile a rom for new bootloader because i use liquid smooth on my nexus4 and it is really great
best regards
Craxx
Send from my Nexus 4 with Tapatalk 2
Hello everyone,
I'm currently running a GE 4.4.2 ROM without problems.
I would love to switch back to a Sense ROM, however, no matter which ROM I try (I even went back to stock with an original RUU), my dialer FC's
'com.android.phone ' stopped.
I also tried several firmwares,
I tried CWM iso TWRP...
Currently S-off, SuperCID,
Any ideas??
Sent from my HTC One using XDA Premium 4 mobile app
Post logcat
CYNiCAL2KX said:
Post logcat
Click to expand...
Click to collapse
0f4f00, arg=0x6cbf84a8
D/libc ( 902): pt_debug : __thread_entry->func=0x6b313ebd
D/libc ( 902): , tls=0x6c0f4f00, arg=0x6cbf84a8
D/memalloc( 185): ion: Allocated buffer base:0x4a921000 size:8355840 fd:51
D/memalloc( 185): ion: Allocated buffer base:0x400a0000 size:4096 fd:55
D/memalloc( 902): ion: Mapped buffer base:0x6c0f5000 size:8355840 offset:0 fd
1
D/memalloc( 902): ion: Mapped buffer base:0x69ad5000 size:4096 offset:0 fd:73
D/memalloc( 185): ion: Allocated buffer base:0x4b68b000 size:8355840 fd:62
D/memalloc( 185): ion: Allocated buffer base:0x40087000 size:4096 fd:77
D/memalloc( 902): ion: Mapped buffer base:0x6e116000 size:8355840 offset:0 fd
6
D/memalloc( 902): ion: Mapped buffer base:0x69af7000 size:4096 offset:0 fd:78
D/PowerManagerService( 473): releaseWakeLock(412fb430): PARTIAL_WAKE_LOCK , t
=ActivityManager-Launch, flags=0x1
D/memalloc( 185): ion: Allocated buffer base:0x4a3e9000 size:3014656 fd:104
D/memalloc( 185): ion: Allocated buffer base:0x400c9000 size:4096 fd:105
D/memalloc( 473): ion: Mapped buffer base:0x71917000 size:3014656 offset:0 fd
19
D/memalloc( 473): ion: Mapped buffer base:0x65a78000 size:4096 offset:0 fd:32
D/SensorManager( 473): onSensorChangedLockedCalledCount = 9000, size = 3, lis
ner = [email protected]
E/ALSAModule( 193): s_standby handle h 0x412eeb70
E/ALSAModule( 193): Number of modifiers 0
E/ALSAModule( 193): usecase_type is 0
D/PowerManagerService( 473): releaseWakeLock(419b7668): PARTIAL_WAKE_LOCK , t
=AudioOut_4, flags=0x1
D/UDove ( 473): DeviceStatus Before dumpsys battery
D/UDove ( 473): DeviceStatus After dumpsys battery
D/ErrorReport( 473): HtcErrorReportManager End---add error logs to dropbox
D/BatteryService( 473): updateBatteryStats: auto update.
I/BatteryService( 473): read native_update done
D/PowerManagerService( 473): acquireWakeLock(41ed4930): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1, pid=473, uid=1000, mUserState=0x3
D/PowerManagerService( 473): releaseWakeLock(41ed4930): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1
D/BatteryService( 473): updateBatteryStats: update triggered by UEvent.
I/BatteryService( 473): read native_update done
D/PowerManagerService( 473): acquireWakeLock(41e5aad8): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1, pid=473, uid=1000, mUserState=0x3
D/HtcPowerSaver( 473): Received battery changed intent.
D/UsbnetService( 473): BroadcastReceiver:nReceive+
D/UsbnetService( 473): onReceive BATTERY_CHANGED
D/UsbnetService( 473): --> pluggedType = 2, mPluggedType = 0, mScreenOff = f
se
D/UsbnetService( 473): BroadcastReceiver:nReceive-
D/HtcPowerSaver( 473): Checking...
I/HtcPowerSaver( 473): >> updateStatus
D/NotificationService( 473): mIntentReceiver() Intent.ACTION_BATTERY_CHANGED
D/PowerManagerService( 473): runHtcPowerSaverCheck ==========================
==========
D/PowerUI ( 798): closing low battery warning: level=95
D/PowerUI ( 798): plugged = true, health = 2, mBatteryLevel = 95, mPluggedBat
ryLevel = 95, mLowBatteryWarningLevel2 = 25, mshowLowChargingWarning2 = true
I/HtcPowerSaver( 473): currentStatus=8000, currentLevel=95, enableLevel=-1, e
ble=false, mAutoModeOn=false, popDialog=false, statusChangeTo=-1
I/HtcPowerSaver( 473): << updateStatus
D/PowerManagerService( 473): releaseWakeLock(41e5aad8): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1
D/PowerManagerService( 473): TPE algorithm. remove timeout.
D/PowerManagerService( 473): ALG=2, lsvalue=320(5th)->160(3th), last_level=3,
Value=142->90, bValue=255, kValue=0, mPowerState=0x3, mSkippedScreenOn=false,
nitialAnimation=false, immediate=false
V/LightsService( 473): setLight #2: color=#ffffffff
D/lights ( 473): set_light_buttons_func: on=16777215 brightness=255
V/LightsService( 473): setLight #0: color=#ff8d8d8d
W/ActivityManager( 473): Activity destroy timeout for ActivityRecord{412b1230
om.android.htccontacts/.DialerTabActivity}
V/LightsService( 473): setLight #0: color=#ff8c8c8c
V/LightsService( 473): setLight #0: color=#ff8b8b8b
V/LightsService( 473): setLight #0: color=#ff8a8a8a
V/LightsService( 473): setLight #0: color=#ff898989
V/LightsService( 473): setLight #0: color=#ff888888
V/LightsService( 473): setLight #0: color=#ff878787
V/LightsService( 473): setLight #0: color=#ff868686
V/LightsService( 473): setLight #0: color=#ff858585
V/LightsService( 473): setLight #0: color=#ff848484
V/LightsService( 473): setLight #0: color=#ff838383
V/LightsService( 473): setLight #0: color=#ff828282
V/LightsService( 473): setLight #0: color=#ff818181
D/libc ( 184): pt_debug : pthread_create->start_routine=0x405fa2c5, tls=0x
1c7f00, arg=0x4051dd98
D/PowerManagerService( 473): acquireWakeLock(41e5d388): PARTIAL_WAKE_LOCK , t
=RILJ, flags=0x1, pid=969, uid=1001, mUserState=0x3
D/libc ( 184): pt_debug : __thread_entry->func=0x405fa2c5
D/libc ( 184): , tls=0x411c7f00, arg=0x4051dd98
D/PowerManagerService( 473): releaseWakeLock(41e5d388): PARTIAL_WAKE_LOCK , t
=RILJ, flags=0x1
V/LightsService( 473): setLight #0: color=#ff808080
V/LightsService( 473): setLight #0: color=#ff7f7f7f
V/LightsService( 473): setLight #0: color=#ff7e7e7e
D/PowerManagerService( 473): acquireWakeLock(41b83388): PARTIAL_WAKE_LOCK , t
=AlarmManager, flags=0x1, pid=473, uid=1000, mUserState=0x3
V/AlarmManager( 473): sending alarm PendingIntent{4145b520: PendingIntentReco
{4156c770 android broadcastIntent}}, intent=android.intent.action.TIME_TICK, t
e=RTC, count=1, when=1395665040000, repeateInterval=0
D/PowerManagerService( 473): releaseWakeLock(41b83388): PARTIAL_WAKE_LOCK , t
=AlarmManager, flags=0x1
V/LightsService( 473): setLight #0: color=#ff7d7d7d
V/LightsService( 473): setLight #0: color=#ff7c7c7c
V/LightsService( 473): setLight #0: color=#ff7b7b7b
V/LightsService( 473): setLight #2: color=#ff000000
V/LightsService( 473): setLight #0: color=#ff141414
D/lights ( 473): set_light_buttons_func: on=0 brightness=0
V/LightsService( 473): setLight #2: color=#ffffffff
D/lights ( 473): set_light_buttons_func: on=16777215 brightness=255
D/SensorManager( 473): onSensorChangedLockedCalledCount = 9500, size = 3, lis
ner = [email protected]
D/PowerManagerService( 473): TPE algorithm. remove timeout.
D/PowerManagerService( 473): nativeSetScreenState: on=false
D/PowerManagerService( 473): nativeSetScreenState: err=0
D/BatteryService( 473): updateBatteryStats: update triggered by UEvent.
D/PowerManagerService( 473): setScreenStateLocked, turn off the button light
V/LightsService( 473): setLight #2: color=#0
D/lights ( 473): set_light_buttons_func: on=0 brightness=0
V/LightsService( 473): setLight #1: color=#0
D/PowerManagerService( 473): acquireWakeLock(41b6e6a8): PARTIAL_WAKE_LOCK , t
=sleep_broadcast, flags=0x1, pid=473, uid=1000, mUserState=0x0
V/LightsService( 473): setLight #0: color=#ff000000
D/PowerManagerService( 473): acquireWakeLock(41b6ef50): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1, pid=473, uid=1000, mUserState=0x0
I/BatteryService( 473): read native_update done
D/HtcPowerSaver( 473): Received battery changed intent.
D/UsbnetService( 473): BroadcastReceiver:nReceive+
D/UsbnetService( 473): onReceive BATTERY_CHANGED
D/UsbnetService( 473): --> pluggedType = 2, mPluggedType = 0, mScreenOff = f
se
D/UsbnetService( 473): BroadcastReceiver:nReceive-
D/NotificationService( 473): mIntentReceiver() Intent.ACTION_BATTERY_CHANGED
D/PowerUI ( 798): closing low battery warning: level=95
D/PowerManagerService( 473): runHtcPowerSaverCheck ==========================
==========
D/HtcPowerSaver( 473): Checking...
I/HtcPowerSaver( 473): >> updateStatus
D/PowerUI ( 798): plugged = true, health = 2, mBatteryLevel = 95, mPluggedBat
ryLevel = 95, mLowBatteryWarningLevel2 = 25, mshowLowChargingWarning2 = true
I/HtcPowerSaver( 473): currentStatus=8000, currentLevel=95, enableLevel=-1, e
ble=false, mAutoModeOn=false, popDialog=false, statusChangeTo=-1
I/HtcPowerSaver( 473): << updateStatus
D/PowerManagerService( 473): releaseWakeLock(41b6ef50): PARTIAL_WAKE_LOCK , t
=BatteryServiceUpdateStats, flags=0x1
D/KeyguardViewMediator( 473): password timeout now
D/StatusBarManager( 473): disable:0 pkgName=android threadName=PowerManagerSe
ice [email protected]
W/MessageQueue( 1368): Handler (android.view.ViewRootImpl$ViewRootHandler) {41
7fc0} sending message to a Handler on a dead thread
W/MessageQueue( 1368): java.lang.RuntimeException: Handler (android.view.ViewR
tImpl$ViewRootHandler) {412b7fc0} sending message to a Handler on a dead threa
W/MessageQueue( 1368): at android.os.MessageQueue.enqueueMessage(MessageQueue
ava:300)
W/MessageQueue( 1368): at android.os.Handler.sendMessageAtTime(Handler.java:4
)
W/MessageQueue( 1368): at android.os.Handler.sendMessageDelayed(Handler.java:
6)
W/MessageQueue( 1368): at android.os.Handler.sendMessage(Handler.java:383)
W/MessageQueue( 1368): at android.view.ViewRootImpl.dispatchScreenStateChange
iewRootImpl.java:4938)
W/MessageQueue( 1368): at android.view.ViewRootImpl$W.dispatchScreenState(Vie
ootImpl.java:5308)
W/MessageQueue( 1368): at android.view.IWindow$Stub.onTransact(IWindow.java:1
)
W/MessageQueue( 1368): at android.os.Binder.execTransact(Binder.java:367)
W/MessageQueue( 1368): at dalvik.system.NativeStart.run(Native Method)
D/PowerManagerService( 473): acquireWakeLock(41b6c380): PARTIAL_WAKE_LOCK , t
=show keyguard, flags=0x1, pid=473, uid=1000, mUserState=0x0
D/PowerManagerService( 473): ActivityManagerNative.getDefault().goingToSleep(
D/PowerManagerService( 473): acquireWakeLock(41a5b678): PARTIAL_WAKE_LOCK , t
=ActivityManager-Sleep, flags=0x1, pid=473, uid=1000, mUserState=0x0
E/ThermalDaemon( 1220): notify PnPMgr CPU3 frequency recover to 1728000
I/FeedHostManager( 902): onPause
I/FeedProviderManager( 902): onPause
D/HtcDeviceInfoManager( 473): SET_TOP null fg=com.htc.launcher
I/SocialFeedProvider( 902): +onPause
I/SocialFeedProvider( 902): -onPause
E/ThermalDaemon( 1220): notify PnPMgr CPU1 frequency recover to 1728000
V/UPolicy ( 473): [Eng]canLogUserProfiling, TellHtc Ui Mode is: normal
D/libc ( 998): pt_debug : pthread_create->start_routine=0x40cbb065, tls=0x
cbdf00, arg=0x664b2008
D/libc ( 998): pt_debug : __thread_entry->func=0x40cbb065
D/libc ( 998): , tls=0x6bcbdf00, arg=0x664b2008
D/NfcService( 998): ScreenObserver: OFF
D/libc ( 998): pt_debug : pthread_create->start_routine=0x40cbb065, tls=0x
0bdf00, arg=0x664b2668
D/libc ( 998): pt_debug : __thread_entry->func=0x40cbb065
D/libc ( 998): , tls=0x6c0bdf00, arg=0x664b2668
D/NfcService( 998): NFC-C OFF, disconnect
I/InputMethodManagerService( 473): screenObserver: isScreenOn=false
I/InputMethodManagerService( 473): Disable input method client.
D/PowerManagerService( 473): releaseWakeLock(41a5b678): PARTIAL_WAKE_LOCK , t
=ActivityManager-Sleep, flags=0x1
D/PowerManagerService( 473): acquireWakeLock(41b7e458): PARTIAL_WAKE_LOCK , t
=NfcService:mRoutingWakeLock, flags=0x1, pid=998, uid=1027, mUserState=0x0
D/AlarmManager( 473): ACTION_SCREEN_OFF
D/FlexNetS( 866): CampNetworkInWhiteBlackList had check current PLMN =
D/UsbnetService( 473): BroadcastReceiver:nReceive+
D/UsbnetService( 473): onReceive SCREEN_OFF
D/UsbnetService( 473): BroadcastReceiver:nReceive-
D/PowerManagerService( 473): releaseWakeLock(41b7e458): PARTIAL_WAKE_LOCK , t
=NfcService:mRoutingWakeLock, flags=0x1
D/WirelessDisplayService( 473): ScreenReceiver;android.intent.action.SCREEN_O
,callOnGoing: false, Screen On: false
D/WirelessDisplayService( 473): ScreenReceiver: ACTION_SCREEN_OFF && Not in D
gleWait nor MirrorEnabling State: REQ_JOIN_GROUP - FALSE
D/SessionManagerService( 473): Received intent: #Intent;action=android.intent
ction.SCREEN_OFF;launchFlags=0x50000010;end
D/ContactMessageStore( 969): start background delete task...
D/CursorWindowStats( 969): Allocate Cursor Window larger than default value,
ze: 4194304, default:2097152
D/CursorWindowStats( 969): Allocate Cursor Window larger than default value,
ze: 4194304, default:2097152
D/ContactMessageStore( 969): size: 0 , 0
D/ContactMessageStore( 969): Background delete complete
D/HtcFooter( 473): layerDrawableIndex = 0
D/CursorWindowStats( 949): Allocate Cursor Window larger than default value,
ze: 4194304, default:2097152
D/libc ( 184): pt_debug : pthread_create->start_routine=0x405fa2c5, tls=0x
1bbf00, arg=0x4051dda8
D/libc ( 184): pt_debug : __thread_entry->func=0x405fa2c5
D/libc ( 184): , tls=0x411bbf00, arg=0x4051dda8
D/PowerManagerService( 473): acquireWakeLock(41d18340): PARTIAL_WAKE_LOCK , t
=RILJ, flags=0x1, pid=969, uid=1001, mUserState=0x0
D/HtcFooter( 473): layerDrawableIndex = 0
D/HtcDeviceInfoManager( 473): SCREEN_OFF pre=off lastOn=1395664650981
D/HtcLockScreen( 473): UnlockScreen: setVisibility :4
V/KeyguardViewManager( 473): KGVM: Set visibility on com.android.internal.pol
[email protected] to 6291456
D/PowerManager( 473): customizeScreenDelay(411089, false, 0x2, -1, -1, -1)
D/PowerManagerService( 473): acquireWakeLock(4186ae88): PARTIAL_WAKE_LOCK , t
=HtcLockScreen:event_15, flags=0x1, pid=473, uid=1000, mUserState=0x0
D/StatusBarManager( 473): disable:16777216 pkgName=android threadName=WindowM
agerPolicy [email protected]
I/Launcher( 902): CloseSystemDialogsIntentReceiver, reason: lock
D/PhoneStatusBar( 798): disable: < expand icons alerts ticker system_info bac
home RECENT* clock >
D/PowerManagerService( 473): releaseWakeLock(41b6c380): PARTIAL_WAKE_LOCK , t
=show keyguard, flags=0x1
D/PowerManagerService( 473): acquireWakeLock(41302680): PARTIAL_WAKE_LOCK , t
=IdleScreen:command_15, flags=0x1, pid=854, uid=10199, mUserState=0x0
D/HtcLockScreen( 473): UnlockScreen: onPause
D/PowerManagerService( 473): releaseWakeLock(41302680): PARTIAL_WAKE_LOCK , t
=IdleScreen:command_15, flags=0x1
D/HtcLockScreen( 473): UnlockScreen: onPause
I/EASAppSvc( 2361): [ NA ]forceResume()
D/Socket_Alarm( 2361): registerHTCSocketMonitorCallBack
D/Socket_Alarm( 2361): set mSocketMonitor
D/Socket_Alarm( 2361): HTCSocketMonitorImpl::HTCSocketMonitorImpl
D/PowerManagerService( 473): releaseWakeLock(41b6e6a8): PARTIAL_WAKE_LOCK , t
=sleep_broadcast, flags=0x1
D/HtcFooter( 473): layerDrawableIndex = 0
D/HtcFooter( 473): layerDrawableIndex = 0
D/HtcLockScreen( 473): UnlockScreen: setVisibility :4
D/LockPatternKeyguardView( 473): **** UPDATE SCREEN: mode=LockScreen last mod
LockScreen, force = false
D/HtcLockScreen( 473): UnlockScreen: setVisibility :8
D/PowerManagerService( 473): acquireWakeLock(41910e30): PARTIAL_WAKE_LOCK , t
=IdleScreen:command_15, flags=0x1, pid=854, uid=10199, mUserState=0x0
D/PowerManagerService( 473): releaseWakeLock(41910e30): PARTIAL_WAKE_LOCK , t
=IdleScreen:command_15, flags=0x1
D/PowerManagerService( 473): acquireWakeLock(41837658): PARTIAL_WAKE_LOCK , t
=IdleScreen:event_15, flags=0x1, pid=854, uid=10199, mUserState=0x0
D/LockPatternKeyguardView( 473): **** UPDATE SCREEN: mode=LockScreen last mod
LockScreen, force = false
D/HtcLockScreen( 473): UnlockScreen: setVisibility :8
D/PowerManagerService( 473): releaseWakeLock(4186ae88): PARTIAL_WAKE_LOCK , t
=HtcLockScreen:event_15, flags=0x1
D/HtcFooter( 473): layerDrawableIndex = 0
D/PowerManagerService( 473): releaseWakeLock(41d18340): PARTIAL_WAKE_LOCK , t
=RILJ, flags=0x1
D/memalloc( 185): ion: Allocated buffer base:0x4c1c8000 size:8077312 fd:50
D/memalloc( 185): ion: Allocated buffer base:0x401e1000 size:4096 fd:108
D/memalloc( 473): ion: Mapped buffer base:0x74b09000 size:8077312 offset:0 fd
84
D/memalloc( 473): ion: Mapped buffer base:0x40000000 size:4096 offset:0 fd:31
I/dalvikvm-heap( 854): Grow heap (frag case) to 14.114MB for 2073616-byte all
ation
D/PowerManagerService( 473): releaseWakeLock(41837658): PARTIAL_WAKE_LOCK , t
=IdleScreen:event_15, flags=0x1
D/libc ( 854): pt_debug : pthread_create->start_routine=0x6b1f3ebd, tls=0x
8fcf00, arg=0x6cd76a48
D/libc ( 854): pt_debug : __thread_entry->func=0x6b1f3ebd
D/libc ( 854): , tls=0x6b8fcf00, arg=0x6cd76a48
D/memalloc( 185): ion: Allocated buffer base:0x4cced000 size:8355840 fd:116
D/memalloc( 185): ion: Allocated buffer base:0x400ca000 size:4096 fd:117
D/memalloc( 854): ion: Mapped buffer base:0x6b8fd000 size:8355840 offset:0 fd
2
D/memalloc( 854): ion: Mapped buffer base:0x669cc000 size:4096 offset:0 fd:56
W/IdleScreen_base( 854): MainContain: enableAnimators Failed.
D/libc ( 854): pt_debug : pthread_create->start_routine=0x40cbb065, tls=0x
3d5f00, arg=0x6c4791f0
D/libc ( 854): pt_debug : __thread_entry->func=0x40cbb065
D/libc ( 854): , tls=0x6c3d5f00, arg=0x6c4791f0
W/WSPPUtility( 854): request cur loc, but there is no sys cur
W/WeatherTimeKeeper( 854): [refreshWeatherData] no weather data
D/memalloc( 185): ion: Allocated buffer base:0x4d4e5000 size:8355840 fd:120
D/memalloc( 185): ion: Allocated buffer base:0x40088000 size:4096 fd:121
D/memalloc( 854): ion: Mapped buffer base:0x6c52b000 size:8355840 offset:0 fd
1
D/memalloc( 854): ion: Mapped buffer base:0x669df000 size:4096 offset:0 fd:83
Will this do??
With logcat...any ideas?
Sent from my HTC One using XDA Premium 4 mobile app
Have you tried a custom dialer, if so does that FC too
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Have you tried a custom dialer, if so does that FC too
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Hi there,
Thanks for the reply.
Just installed IC with sense 6.0
Problem solved!!!!!!!
Google photos worked fine until the new google photos (that one announced on Google I/O)
It crashes on start with the following LogCat Output
Code:
06-08 17:22:34.304: A/libc(6280): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 6338 (network)
06-08 17:22:34.994: E/InputDispatcher(556): channel '222e0488 com.google.android.apps.photos/com.google.android.apps.photos.home.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.004: E/InputDispatcher(556): channel '2227a0d8 com.google.android.apps.photos/com.google.android.apps.photos.onboarding.IntroActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.054: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 44
06-08 17:22:35.064: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 45
06-08 17:22:35.074: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 58
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.564: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 33
Anyone experiencing the same problems?
leuofiridia said:
Google photos worked fine until the new google photos (that one announced on Google I/O)
It crashes on start with the following LogCat Output
Code:
06-08 17:22:34.304: A/libc(6280): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 6338 (network)
06-08 17:22:34.994: E/InputDispatcher(556): channel '222e0488 com.google.android.apps.photos/com.google.android.apps.photos.home.HomeActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.004: E/InputDispatcher(556): channel '2227a0d8 com.google.android.apps.photos/com.google.android.apps.photos.onboarding.IntroActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
06-08 17:22:35.054: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 44
06-08 17:22:35.064: E/IMGSRV(797): :0: PVRDRMOpen: TP3, ret = 45
06-08 17:22:35.074: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 58
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.154: E/JavaBinder(556): !!! FAILED BINDER TRANSACTION !!!
06-08 17:22:35.564: E/IMGSRV(144): :0: PVRDRMOpen: TP3, ret = 33
Anyone experiencing the same problems?
Click to expand...
Click to collapse
Problem solved with a update launched this week
I gave up and called T-Mobile. They're sending me a replacement next-day air. Should I try to re-lock this one?
So a bit of background. I was running unlocked the latest stock 6.0.1 without root or custom kernels etc.
Last night I noticed my battery indicator was orange but my phone never entered battery saver. Went into battery saver to turn it back on; the toggle didn't work. I figure that's weird, but a reboot should fix it. I attempt reboot my device. It has been stuck in a bootloop since (at the dots animation). After giving up on it, I left it to charge overnight off (just incase it was some weird low battery thing). Try again this morning and still no luck.
Troubleshooting
Booted into stock recovery; wiped cache. No luck.
I snagged the latest images from Google and flashed boot and system. No luck.
I booted into stock recovery; wiped cache. No luck.
Downloaded TWRP and used the 'boot' command to boot into it without flashing. Used that to backup the contents of my internal storage.
Booted back into stock recovery. Did a factory rest and wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery). No Luck.
Booted into stock recovery; wiped cache. No luck.
Booted into stock recovery. Did a factory rest and wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery)(thinking maybe I missed an image last time). No Luck.
edit2:
Fastboot erased userdata and cache. No luck.
edit3:
Fastboot formatted userdata and cache. No luck.
Booted into stock recovery. Did a factory rest and wiped cache. (figured that might initialize the partitions if they were left blank)No luck.
Used the 'boot' command to boot into TWRP without flashing. Wiped /data, /cache, and dalvik cache in TWRP No luck.
I always gave it at least 5 minutes (once as long as 40 minutes) of booting before moving on to the next step. As you can see, I'm long past trying to preserve anything, I just want a useable phone again.
Edit: also weird. I can only turn the phone off via bootloader > power off. Holding the power button always causes a reboot instead of a power off.
Wait a minute... nobody's answered this?? I'm stuck in the EXACT SAME situation. The N6 was running a ROM AOK forever and once I tried powering it on after allowing it to completely drain its battery... NO LUCK
Were you able to get your unit working again? Does anyone have any idea outside what's in the OP?
skielbasa said:
I gave up and called T-Mobile. They're sending me a replacement next-day air. Should I try to re-lock this one?
So a bit of background. I was running unlocked the latest stock 6.0.1 without root or custom kernels etc.
Last night I noticed my battery indicator was orange but my phone never entered battery saver. Went into battery saver to turn it back on; the toggle didn't work. I figure that's weird, but a reboot should fix it. I attempt reboot my device. It has been stuck in a bootloop since (at the dots animation). After giving up on it, I left it to charge overnight off (just incase it was some weird low battery thing). Try again this morning and still no luck.
Troubleshooting
Booted into stock recovery; wiped cache. No luck.
I booted into stock recovery; wiped cache. No luck.
I flashed the full image (radio, bootloader, boot, system, userdata, cache, recovery). No Luck.
Booted into stock recovery. Did a factory rest and wiped cache. No luck.
Fastboot erased userdata and cache. No luck.
edit3:
Booted into stock recovery. Did a factory rest and wiped cache. (figured that might initialize the partitions if they were left blank)No luck.
Used the 'boot' command to boot into TWRP without flashing. Wiped /data, /cache, and dalvik cache in TWRP No luck.
I always gave it at least 5 minutes (once as long as 40 minutes) of booting before moving on to the next step. As you can see, I'm long past trying to preserve anything, I just want a useable phone again.
Edit: also weird. I can only turn the phone off via bootloader > power off. Holding the power button always causes a reboot instead of a power off.
Click to expand...
Click to collapse
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?
biggiesmalls657 said:
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?
Click to expand...
Click to collapse
lol, thats a question from 3 moths ago.. i highly doubt that they are waiting on an answer :angel:
simms22 said:
lol, thats a question from 3 moths ago.. i highly doubt that they are waiting on an answer :angel:
Click to expand...
Click to collapse
I didn't read the timestamp but maybe its lying around somewhere.
From SELinux Denials to Sensor Failure
biggiesmalls657 said:
Did you flash all partitions separately and erase command and then format? Are you using an official Nexus 6 cable?
Click to expand...
Click to collapse
I've flash each partition individually with 71.18 BL Stock & 71.21 BL N Preview Stock to no avail.
Mixing 71.18 & 71.21 Roms brought about a SeLinux issue but that was solved by getting the BLs and their appropriate Roms right.
Now I'm running into an odd sensor failure in my LogCat that I can't get around:
Code:
--------- beginning of main
02-09 20:45:15.323 245 245 W auditd : type=2000 audit(0.0:1): initialized
02-09 20:45:17.385 252 252 I /system/bin/tzdatacheck: tzdata file /data/misc/zoneinfo/current/tzdata does not exist. No action required.
--------- beginning of system
02-09 20:45:17.396 246 246 I vold : Vold 3.0 (the awakening) firing up
02-09 20:45:17.396 246 246 V vold : Detected support for: exfat ext4 f2fs ntfs vfat
02-09 20:45:18.099 279 279 D QSEECOMD: : qseecom listener services process entry PPID = 1
02-09 20:45:18.099 279 279 E QSEECOMD: : Listener: index = 0, hierarchy = 0
02-09 20:45:18.099 277 277 I mdm_helper: 1 supported modem(s) found
02-09 20:45:18.099 277 277 I mdm_helper: Setting up mdm helper device structure
02-09 20:45:18.099 277 277 I mdm_helper: Found private data for MDM9x25
02-09 20:45:18.099 277 277 I mdm_helper: ESOC Details:
02-09 20:45:18.099 277 277 I mdm_helper: Name:MDM9x25
02-09 20:45:18.099 277 277 I mdm_helper: Port:/dev/esoc-0
02-09 20:45:18.099 277 277 I mdm_helper: Link:HSIC
02-09 20:45:18.099 277 277 I mdm_helper: Device configuration loaded
02-09 20:45:18.099 277 277 I mdm_helper: Starting MDM helper
02-09 20:45:18.099 277 277 I mdm_helper: Creating thread for MDM9x25
02-09 20:45:18.099 277 280 I mdm_helper: Starting MDM9x25
02-09 20:45:18.099 277 280 I mdm_helper: MDM9x25 : switching state to POWERUP
02-09 20:45:18.100 277 280 I mdm_helper: MDM9x25: Initializing environment
02-09 20:45:18.100 279 279 D QSEECOMD: : Init dlopen(librpmb.so, RTLD_NOW) succeeds
02-09 20:45:18.100 279 279 D QSEECOMD: : Init::Init dlsym(g_FSHandle rpmb_init_service) succeeds
02-09 20:45:18.100 279 279 I rpmb : RPMB Mult = 16384, Rel_sec_cnt = 1
02-09 20:45:18.100 279 279 E DrmLibRpmb: rpmb_init succeeded! with ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : Init rpmb_init_service ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : RPMB system services: init (Listener ID = 8192)
02-09 20:45:18.101 279 279 E QSEECOMD: : Listener: index = 1, hierarchy = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : Init dlopen(libssd.so, RTLD_NOW) succeeds
02-09 20:45:18.101 279 279 D QSEECOMD: : Init::Init dlsym(g_FSHandle ssd_init_service) succeeds
02-09 20:45:18.101 279 279 E SSD : ssd_init_service succeeded!
02-09 20:45:18.101 279 279 D QSEECOMD: : Init ssd_init_service ret = 0
02-09 20:45:18.101 279 279 D QSEECOMD: : SSD system services: init (Listener ID = 12288)
02-09 20:45:18.102 279 279 D QSEECOMAPI: : QSEECom_get_handle sb_length = 0x400
02-09 20:45:18.102 279 279 D QSEECOMAPI: : App is not loaded in QSEE
02-09 20:45:18.107 274 274 I lowmemorykiller: Using in-kernel low memory killer interface
02-09 20:45:18.122 278 291 E Sensors : sns_fsa_la.c(78):realpath failed for directory name2
02-09 20:45:18.123 278 291 E Sensors : sns_reg_la.c(289):Error creating registry file
02-09 20:45:18.123 278 291 W Sensors : sns_reg_mr.c(370):File init failed 5
02-09 20:45:18.136 276 276 I SurfaceFlinger: SurfaceFlinger is starting
02-09 20:45:18.136 276 276 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
02-09 20:45:18.143 276 276 D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
02-09 20:45:18.176 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:18.176 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:18.252 276 276 D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
02-09 20:45:18.260 276 276 D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
02-09 20:45:18.277 276 276 I Adreno : QUALCOMM build : 52af4d2, I8366cd0437
02-09 20:45:18.277 276 276 I Adreno : Build Date : 10/20/15
02-09 20:45:18.277 276 276 I Adreno : OpenGL ES Shader Compiler Version: XE031.05.13.02
02-09 20:45:18.277 276 276 I Adreno : Local Branch : M14
02-09 20:45:18.277 276 276 I Adreno : Remote Branch :
02-09 20:45:18.277 276 276 I Adreno : Remote Branch :
02-09 20:45:18.277 276 276 I Adreno : Reconstruct Branch :
02-09 20:45:18.584 279 279 D QSEECOMAPI: : Loaded image: APP id = 2
02-09 20:45:18.586 279 279 D QSEECOMD: : Parent qseecom daemon process paused!!
02-09 20:45:18.587 331 331 D QSEECOMD: : qseecom listener service threads starting!!!
02-09 20:45:18.587 331 331 D QSEECOMD: : Total listener services to start = 5
02-09 20:45:18.587 331 331 E QSEECOMD: : Listener: index = 0, hierarchy = 1
02-09 20:45:18.587 331 331 D QSEECOMD: : Init dlopen(librpmb.so, RTLD_NOW) succeeds
02-09 20:45:18.587 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle rpmb_start) succeeds
02-09 20:45:18.587 331 331 D QSEECOMAPI: : QSEECom_register_listener 8192 sb_length = 0x5000
02-09 20:45:18.591 331 331 D QSEECOMD: : Init rpmb_start ret = 0
02-09 20:45:18.591 331 331 D QSEECOMD: : RPMB system services: Started (Listener ID = 8192)
02-09 20:45:18.591 331 331 E QSEECOMD: : Listener: index = 1, hierarchy = 1
02-09 20:45:18.591 331 331 D QSEECOMD: : Init dlopen(libssd.so, RTLD_NOW) succeeds
02-09 20:45:18.591 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle ssd_start) succeeds
02-09 20:45:18.591 331 331 D QSEECOMAPI: : QSEECom_register_listener 12288 sb_length = 0x5000
02-09 20:45:18.592 331 331 D QSEECOMD: : Init ssd_start ret = 0
02-09 20:45:18.592 331 331 D QSEECOMD: : SSD system services: Started (Listener ID = 12288)
02-09 20:45:18.592 331 331 E QSEECOMD: : Listener: index = 2, hierarchy = 1
02-09 20:45:18.593 331 331 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed....
02-09 20:45:18.593 331 331 E QSEECOMD: : Listener: index = 3, hierarchy = 1
02-09 20:45:18.599 331 331 D QSEECOMD: : Init dlopen(libdrmtime.so, RTLD_NOW) succeeds
02-09 20:45:18.599 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle atime_start) succeeds
02-09 20:45:18.599 331 331 D DrmLibTime: QSEE Time Listener: atime_start
02-09 20:45:18.599 331 331 D QSEECOMAPI: : QSEECom_register_listener 11 sb_length = 0x5000
02-09 20:45:18.600 331 331 D DrmLibTime: registering fs service to QSEECom is done!
02-09 20:45:18.600 331 331 D DrmLibTime: begin to create a thread!
02-09 20:45:18.600 331 331 D DrmLibTime: Creating a pthread in atime_start is done! return 0
02-09 20:45:18.600 331 331 D QSEECOMD: : Init atime_start ret = 0
02-09 20:45:18.600 331 338 D DrmLibTime: QSEE Time Listener: dispatch
02-09 20:45:18.600 331 331 D QSEECOMD: : time services: Started (Listener ID = 11)
02-09 20:45:18.600 331 338 D DrmLibTime: before calling ioctl to read the next time_cmd
02-09 20:45:18.600 331 331 E QSEECOMD: : Listener: index = 4, hierarchy = 1
02-09 20:45:18.600 331 331 D QSEECOMD: : Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
02-09 20:45:18.600 331 331 D QSEECOMD: : Init::Init dlsym(g_FSHandle fs_start) succeeds
02-09 20:45:18.600 331 331 D QSEECOMAPI: : QSEECom_register_listener 10 sb_length = 0x5000
02-09 20:45:18.601 331 331 D QSEECOMD: : Init fs_start ret = 0
02-09 20:45:18.601 331 331 D QSEECOMD: : file system services: Started (Listener ID = 10)
02-09 20:45:18.601 331 331 D QSEECOMD: : QSEECOM DAEMON RUNNING
02-09 20:45:18.711 276 276 I qdutils : PartialUpdate status: Enabled
02-09 20:45:18.711 276 276 I qdutils : Left Align: 8
02-09 20:45:18.712 276 276 I qdutils : Width Align: 8
02-09 20:45:18.712 276 276 I qdutils : Top Align: 1
02-09 20:45:18.712 276 276 I qdutils : Height Align: 1
02-09 20:45:18.712 276 276 I qdutils : Min ROI Width: 8
02-09 20:45:18.712 276 276 I qdutils : Min ROI Height: 1
02-09 20:45:18.712 276 276 I qdutils : Needs ROI Merge: 1
02-09 20:45:18.712 276 276 I qdutils : Left Split=720
02-09 20:45:18.712 276 276 I qdutils : Right Split=720
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing Qualcomm Hardware Composer
02-09 20:45:18.715 276 276 I qdhwcomposer: MDP version: 500
02-09 20:45:18.715 276 276 I SurfaceFlinger: Using composer version 1.5
02-09 20:45:18.715 276 276 I qdhwcomposer: hwc_registerProcs
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing UEVENT Thread
02-09 20:45:18.715 276 276 I qdhwcomposer: Initializing VSYNC Thread
02-09 20:45:18.716 276 342 I qdhwcomposer: vsync_loop: Reading event 0 for dpy 0 from /sys/class/graphics/fb0/vsync_event
02-09 20:45:18.716 276 276 D qdhwcomposer: hwc_getDisplayAttributes disp = 0, width = 1440
02-09 20:45:18.716 276 276 D qdhwcomposer: hwc_getDisplayAttributes disp = 0, height = 2560
02-09 20:45:18.717 276 276 I SurfaceFlinger: EGL information:
02-09 20:45:18.717 276 276 I SurfaceFlinger: vendor : Android
02-09 20:45:18.717 276 276 I SurfaceFlinger: version : 1.4 Android META-EGL
02-09 20:45:18.717 276 276 I SurfaceFlinger: extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_swap_buffers_with_damage EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_create_context EGL_KHR_surfaceless_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable EGL_KHR_create_context_no_error
02-09 20:45:18.717 276 276 I SurfaceFlinger: Client API: OpenGL_ES
02-09 20:45:18.717 276 276 I SurfaceFlinger: EGLSurface: 8-8-8-8, config=0xb6a86978
02-09 20:45:18.718 276 342 I qdhwcomposer: vsync_loop: Reading event 1 for dpy 0 from /sys/class/graphics/fb0/show_blank_event
02-09 20:45:18.719 276 342 I qdhwcomposer: vsync_loop: Reading event 2 for dpy 0 from /sys/class/graphics/fb0/cec/rd_msg
02-09 20:45:18.721 276 342 E qdhwcomposer: vsync_loop:unable to open event node for dpy=0 event=2, No such file or directory
02-09 20:45:18.722 276 342 I qdhwcomposer: vsync_loop: Reading event 0 for dpy 1 from /sys/class/graphics/fb-1/vsync_event
02-09 20:45:18.722 276 342 I qdhwcomposer: vsync_loop: Reading event 1 for dpy 1 from /sys/class/graphics/fb-1/show_blank_event
02-09 20:45:18.723 276 342 I qdhwcomposer: vsync_loop: Reading event 2 for dpy 1 from /sys/class/graphics/fb-1/cec/rd_msg
02-09 20:45:18.726 276 276 I SurfaceFlinger: OpenGL ES informations:
02-09 20:45:18.726 276 276 I SurfaceFlinger: vendor : Qualcomm
02-09 20:45:18.726 276 276 I SurfaceFlinger: renderer : Adreno (TM) 420
02-09 20:45:18.726 276 276 I SurfaceFlinger: version : OpenGL ES 3.1 [email protected] ([email protected])
02-09 20:45:18.726 276 276 I SurfaceFlinger: extensions: GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_half_float GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_compressed_ETC1_RGB8_texture GL_AMD_compressed_ATC_texture GL_KHR_texture_compression_astc_ldr GL_OES_texture_npot GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_OES_texture_3D GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_QCOM_alpha_test GL_OES_depth24 GL_OES_packed_depth_stencil GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_EXT_sRGB GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_EXT_texture_type_2_10_10_10_REV GL_EXT_texture_sRGB_decode GL_OES_element_index_uint GL_EXT_copy_image GL_EXT_geometry_shader GL_EXT_tessellation_shader GL_OES_texture_stencil8 GL_EXT_shader_io_blocks GL_OES_shader_image_atomic GL_OES_sample_variables GL_EXT_texture_border_clamp GL_EXT_multisampled_render_to_texture GL_OES_shader_multisample_interpolation GL_EXT_texture_cube_map_arr
02-09 20:45:18.726 276 276 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 16384
02-09 20:45:18.726 276 276 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 16384
02-09 20:45:18.730 276 276 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb6aa4000
02-09 20:45:18.730 276 276 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
02-09 20:45:18.730 276 276 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
02-09 20:45:18.730 276 342 I qdhwcomposer: handle_blank_event: dpy:0 panel power state: 1
02-09 20:45:18.841 344 346 D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
02-09 20:45:18.888 344 346 D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
02-09 20:45:18.896 344 346 D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
02-09 20:45:18.907 344 346 I Adreno : QUALCOMM build : 52af4d2, I8366cd0437
02-09 20:45:18.907 344 346 I Adreno : Build Date : 10/20/15
02-09 20:45:18.907 344 346 I Adreno : OpenGL ES Shader Compiler Version: XE031.05.13.02
02-09 20:45:18.907 344 346 I Adreno : Local Branch : M14
02-09 20:45:18.907 344 346 I Adreno : Remote Branch :
02-09 20:45:18.907 344 346 I Adreno : Remote Branch :
02-09 20:45:18.907 344 346 I Adreno : Reconstruct Branch :
02-09 20:45:18.923 344 346 E BootAnimation: couldn't find audio_conf.txt
02-09 20:45:19.617 276 276 D SurfaceFlinger: shader cache generated - 24 shaders in 267.772125 ms
02-09 20:45:19.637 276 276 D qdutils : DEBUG_CALC_FPS: 0
02-09 20:45:19.637 276 276 D qdutils : period: 10
02-09 20:45:19.637 276 276 D qdutils : ignorethresh_us: 500000
03-21 17:30:31.580 245 245 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
03-21 17:30:31.580 245 245 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
02-09 20:45:28.065 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.066 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.069 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.069 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.071 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.071 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.074 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.074 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.076 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.077 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.078 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.078 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.079 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.080 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.081 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.081 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.082 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.082 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.083 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.083 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.085 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.085 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.087 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.087 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.089 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.089 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.090 278 291 E Sensors : sns_reg.c(255):Invalid ID: 3040
02-09 20:45:28.091 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.091 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.093 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.093 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.094 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.094 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.096 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.096 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.097 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.097 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.098 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.098 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:28.099 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:28.099 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.108 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.108 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.109 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.109 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
02-09 20:45:38.111 278 291 E Sensors : sns_reg_la.c(91):reg_read: reg file not open
02-09 20:45:38.111 278 291 E Sensors : sns_reg.c(291):Received error from sns_reg_read/write 5
KLBrey said:
I've flash each partition individually with 71.18 BL Stock & 71.21 BL N Preview Stock to no avail.
Mixing 71.18 & 71.21 Roms brought about a SeLinux issue but that was solved by getting the BLs and their appropriate Roms right.
Now I'm running into an odd sensor failure in my LogCat that I can't get around:
Click to expand...
Click to collapse
Hardware. Are you using an official fastboot cable? Did you flash the binaries of the sensor drivers?
Can My Poor N6 Bounce-Back from Seeming Complete Sensor Failure??
biggiesmalls657 said:
Hardware. Are you using an official fastboot cable? Did you flash the binaries of the sensor drivers?
Click to expand...
Click to collapse
Since you're the 2nd to mention USB cable quality, I'll address that:
I have my OEM Turbo Charger and I'm sure I still have the OEM Cable that came with it, but I'm currently using an Amazon Basic Branded 5ft replacement to one my cat devoured. Since it seems that Cable Matters, I'll wrangle the one's I have with me when the Sun's is up.
The Immediate Worse Case S:
I'll have to wait until I return home Monday if none of the cables with me are The One*.
Flash Binaries of Sensor Drivers:
whaaa
[* thanks Moto, one more Must Match in my life]
[SOLVED] Bootloop with Major Sensor Failure
After looking into physical things like cable quality and low-level drivers provided to ROM bakers (neither were my particulate issue), I pieced together a diagnosis and resolution that worked for me:
Validating my /persist partition OR Creating a new ext4 one if it's curruptI dropped to TWRP v3 recovery, opened an ADB Shell and checked which partitions were automatically mounted. Alas, /persist wasn't there... it was gone, baby, gone! So I tried to recover it using
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
Which resulted in a Bad Superblock with no backups. Using an alternate Superblock (ie. e2fsck -b 8197) also failed. So I crossed fingers that my N6 retained specs about how /persist should be and created a fresh ext4 version
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
That solved (nearly) everything. I was able to watch live logcat as my N6 successfully booted into 6.0.1 MM again. Everything seems AOK so far, but it's late and I'm about to crash. When the Sun's up again, I'll test it and post once more.
Dear all,
I usually use bluetooth everyday to listen to spotify on the car audio everyday. Today I noticed that the bluetooth activation option was off, so I proceeded to activate it in Settings->Bluetooth->On. However, the button/slider moved right, but stayed greyed out. No scan is done, and pressing the ". . ." on the top right corner only shows "Show received files", with the other options greyed out.
I spent the whole day trying several simple things that one could find online. Eventually, I did a factory reset but it did not help.
I went into engineer mode (through *#808#) and tested the "search bluetooth device" with no result... it just stays there forever scanning.
I connected the phone to adb and checked the console while greping for "Bluetooth" and this is what I got while running the engineer mode test:
Code:
05-28 17:38:57.181* 1521* 3679 I ActivityManager: START u0 {act=com.android.engineeringmode.bluetoothtest.BluetoothSearch cmp=com.android.engineeringmode/.bluetoothtest.BluetoothSearch} from uid 1000 pid 9391 on display 0
05-28 17:38:57.278* 1521* 1587 D BluetoothManagerService: Message: 20
05-28 17:38:57.279* 1521* 1587 D BluetoothManagerService: Added callback: [email protected]:true
05-28 17:38:57.296* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.298* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.310* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.351* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.357* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.360* 1521* 1588 I ActivityManager: Displayed com.android.engineeringmode/.bluetoothtest.BluetoothSearch: +133ms
05-28 17:38:57.363* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.380* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.485* 9391* 9391 W BluetoothSearch: openDevice
05-28 17:38:57.489* 9391* 9391 W BluetoothSearch: Bluetooth is not opened
05-28 17:38:57.564* 1521* 2419 D BluetoothManagerService: enable():* mBluetooth [email protected] mBinding = false mState = 14
05-28 17:38:57.564* 1521* 2419 D BluetoothManagerService: enable returning
05-28 17:38:57.564* 1521* 1587 D BluetoothManagerService: Message: 1
05-28 17:38:57.564* 9391* 9391 D BluetoothSearch: open Bluetooth device sucessful
[B]05-28 17:38:57.564* 1521* 1587 D BluetoothManagerService: MESSAGE_ENABLE: mBluetooth = [email protected]
05-28 17:39:00.600* 1521* 1587 E BluetoothManagerService: waitForOnOff time out
05-28 17:39:01.001* 1521* 1587 D BluetoothManagerService: Message: 42
05-28 17:39:01.002* 1521* 1587 D BluetoothManagerService: MESSAGE_RESTART_BLUETOOTH_SERVICE: Restart IBluetooth service
05-28 17:39:01.007* 7563* 8635 D BluetoothAdapterService: enable() - Enable called with quiet mode status =* false[/B]
For comparison, here is the log output when I activated and deactivated the Bluetooth toggle in the Settings:
Code:
05-28 18:05:38.421 1521 1539 I ActivityManager: START u0 {act=android.settings.BLUETOOTH_SETTINGS flg=0x14000000 cmp=com.android.settings/.Settings$BluetoothSettingsActivity} from uid 10025 pid 2372 on display 0
05-28 18:05:38.482 2540 2540 D LocalBluetoothManager: setting foreground activity to non-null context
05-28 18:05:38.493 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.493 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.497 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.517 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.520 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.521 1521 1588 I ActivityManager: Displayed com.android.settings/.Settings$BluetoothSettingsActivity: +80ms
05-28 18:05:38.531 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.532 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.538 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.882 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.899 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.958 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.255 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.262 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.289 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:50.927 1521 3098 D BluetoothManagerService: enable(): mBluetooth [email protected] mBinding = false mState = 14
05-28 18:05:50.927 1521 3098 D BluetoothManagerService: enable returning
05-28 18:05:50.928 1521 1587 D BluetoothManagerService: Message: 1
05-28 18:05:50.929 1521 1587 D BluetoothManagerService: MESSAGE_ENABLE: mBluetooth = [email protected]
05-28 18:05:53.978 1521 1587 E BluetoothManagerService: waitForOnOff time out
05-28 18:05:54.379 1521 1587 D BluetoothManagerService: Message: 42
05-28 18:05:54.379 1521 1587 D BluetoothManagerService: MESSAGE_RESTART_BLUETOOTH_SERVICE: Restart IBluetooth service
05-28 18:05:54.383 7563 7574 D BluetoothAdapterService: enable() - Enable called with quiet mode status = false
Seems to be similar, with both logs showing the same thing at the end, which look like it timed out something. The only difference I see with the engineer mode test was that it had successfully activated the BT device, which somehow is a relief because I was starting to consider that this could be a bluetooth module waving goodbye.
Has anyone got any idea on this?
Coincidently, I have been trying to find for over three weeks the cause for a major battery drainage on my OP3T. Since my device is not rooted, I am not able to get much info, and was narrowing it down to app consume. I even left the device on but will only gsm signal (no wifi, bluetooth or cellular data), and it only lasted for the same 16 hours as it does with everything on. Maybe it has something to do with the bluetooth device slowly getting to this state of malfunctioning?
On another note, when the battery issue started, I also noticed that I had a weird issue with bluetooth: i could pair with car audio, play media through the car audio, answer calls through it as well, everyone could listen me through the car audio mic, but I wasn't able to listen to anyone. I tried several factory resets, even resetting the car audio, but no avail. Then it all just kind of culminated on a (hope not) dead bluetooth on my 3-month old OP3T.
Any suggestions?
Best regards,
oldiamond
oldiamond said:
Dear all,
I usually use bluetooth everyday to listen to spotify on the car audio everyday. Today I noticed that the bluetooth activation option was off, so I proceeded to activate it in Settings->Bluetooth->On. However, the button/slider moved right, but stayed greyed out. No scan is done, and pressing the ". . ." on the top right corner only shows "Show received files", with the other options greyed out.
I spent the whole day trying several simple things that one could find online. Eventually, I did a factory reset but it did not help.
I went into engineer mode (through *#808#) and tested the "search bluetooth device" with no result... it just stays there forever scanning.
I connected the phone to adb and checked the console while greping for "Bluetooth" and this is what I got while running the engineer mode test:
Code:
05-28 17:38:57.181* 1521* 3679 I ActivityManager: START u0 {act=com.android.engineeringmode.bluetoothtest.BluetoothSearch cmp=com.android.engineeringmode/.bluetoothtest.BluetoothSearch} from uid 1000 pid 9391 on display 0
05-28 17:38:57.278* 1521* 1587 D BluetoothManagerService: Message: 20
05-28 17:38:57.279* 1521* 1587 D BluetoothManagerService: Added callback: [email protected]:true
05-28 17:38:57.296* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.298* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.310* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.351* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.357* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.360* 1521* 1588 I ActivityManager: Displayed com.android.engineeringmode/.bluetoothtest.BluetoothSearch: +133ms
05-28 17:38:57.363* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.380* 1521* 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{c31ba04 u0 com.android.engineeringmode/com.android.engineeringmode.bluetoothtest.BluetoothSearch} [email protected] which=1
05-28 17:38:57.485* 9391* 9391 W BluetoothSearch: openDevice
05-28 17:38:57.489* 9391* 9391 W BluetoothSearch: Bluetooth is not opened
05-28 17:38:57.564* 1521* 2419 D BluetoothManagerService: enable():* mBluetooth [email protected] mBinding = false mState = 14
05-28 17:38:57.564* 1521* 2419 D BluetoothManagerService: enable returning
05-28 17:38:57.564* 1521* 1587 D BluetoothManagerService: Message: 1
05-28 17:38:57.564* 9391* 9391 D BluetoothSearch: open Bluetooth device sucessful
[B]05-28 17:38:57.564* 1521* 1587 D BluetoothManagerService: MESSAGE_ENABLE: mBluetooth = [email protected]
05-28 17:39:00.600* 1521* 1587 E BluetoothManagerService: waitForOnOff time out
05-28 17:39:01.001* 1521* 1587 D BluetoothManagerService: Message: 42
05-28 17:39:01.002* 1521* 1587 D BluetoothManagerService: MESSAGE_RESTART_BLUETOOTH_SERVICE: Restart IBluetooth service
05-28 17:39:01.007* 7563* 8635 D BluetoothAdapterService: enable() - Enable called with quiet mode status =* false[/B]
For comparison, here is the log output when I activated and deactivated the Bluetooth toggle in the Settings:
Code:
05-28 18:05:38.421 1521 1539 I ActivityManager: START u0 {act=android.settings.BLUETOOTH_SETTINGS flg=0x14000000 cmp=com.android.settings/.Settings$BluetoothSettingsActivity} from uid 10025 pid 2372 on display 0
05-28 18:05:38.482 2540 2540 D LocalBluetoothManager: setting foreground activity to non-null context
05-28 18:05:38.493 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.493 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.497 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.517 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.520 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.521 1521 1588 I ActivityManager: Displayed com.android.settings/.Settings$BluetoothSettingsActivity: +80ms
05-28 18:05:38.531 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.532 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.538 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.882 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.899 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:38.958 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.255 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.262 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:39.289 1521 1561 D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{b01d111 u0 com.android.settings/com.android.settings.Settings$BluetoothSettingsActivity} [email protected] which=1
05-28 18:05:50.927 1521 3098 D BluetoothManagerService: enable(): mBluetooth [email protected] mBinding = false mState = 14
05-28 18:05:50.927 1521 3098 D BluetoothManagerService: enable returning
05-28 18:05:50.928 1521 1587 D BluetoothManagerService: Message: 1
05-28 18:05:50.929 1521 1587 D BluetoothManagerService: MESSAGE_ENABLE: mBluetooth = [email protected]
05-28 18:05:53.978 1521 1587 E BluetoothManagerService: waitForOnOff time out
05-28 18:05:54.379 1521 1587 D BluetoothManagerService: Message: 42
05-28 18:05:54.379 1521 1587 D BluetoothManagerService: MESSAGE_RESTART_BLUETOOTH_SERVICE: Restart IBluetooth service
05-28 18:05:54.383 7563 7574 D BluetoothAdapterService: enable() - Enable called with quiet mode status = false
Seems to be similar, with both logs showing the same thing at the end, which look like it timed out something. The only difference I see with the engineer mode test was that it had successfully activated the BT device, which somehow is a relief because I was starting to consider that this could be a bluetooth module waving goodbye.
Has anyone got any idea on this?
Coincidently, I have been trying to find for over three weeks the cause for a major battery drainage on my OP3T. Since my device is not rooted, I am not able to get much info, and was narrowing it down to app consume. I even left the device on but will only gsm signal (no wifi, bluetooth or cellular data), and it only lasted for the same 16 hours as it does with everything on. Maybe it has something to do with the bluetooth device slowly getting to this state of malfunctioning?
On another note, when the battery issue started, I also noticed that I had a weird issue with bluetooth: i could pair with car audio, play media through the car audio, answer calls through it as well, everyone could listen me through the car audio mic, but I wasn't able to listen to anyone. I tried several factory resets, even resetting the car audio, but no avail. Then it all just kind of culminated on a (hope not) dead bluetooth on my 3-month old OP3T.
Any suggestions?
Best regards,
oldiamond
Click to expand...
Click to collapse
Send it back. Sounds like a lemon.
zelendel said:
Send it back. Sounds like a lemon.
Click to expand...
Click to collapse
Thanks, I am actually thinking of that, but would like to give some struggle first.
Could a kind soul at least provide a copy+paste of adb logcat connecting to bluetooth for comparison? Thanks in advance!
Wouldn't have a logcat sample, but I had same issue when firmware version did't match OS version.
Is there any chance you did the same?
maddler said:
Wouldn't have a logcat sample, but I had same issue when firmware version did't match OS version.
Is there any chance you did the same?
Click to expand...
Click to collapse
Hi, thanks for the reply. No, I haven't (yet) fiddled with the phone, in that aspect. Still unrooted and only did two OTA updates as soon as they became available. This behaviour sort of only started to manifest after the last OTA, but not immediately... seemed to be gradually reaching this status since then.
Maybe the Bluetooth firmware upgrade somehow failed during one of the OTA. If you're lucky, manually flashing the firmware zip with 4.1.3 firmwares found in this forum could solve your problems. Seems like OTAs are a bit finicky on Oneplus phones as many others have experienced different problems when installing OTAs.
If that was an OTA flashing issue I'd say that would've just stopped working. Anyway, I'd say that trying to flash it again is no arm. Give it a try and see if there's any improvement.
Hi all,
I downloaded OnePlus 3T OxygenOS 4.1.3 Ver 4.1.3 (2017-04-17) from the official website, and checked md5 after download. Then I sideloaded it via adb. No errors reported while doing this. Maybe trying to update a new version of the modem firmware only (currently Baseband version MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.88834.1.89286.1) ?
EDIT: Forgot to mention that the issues maintained.
Status update: flashed OOS beta 7. Still no Bluetooth, battery drain still happens. But a very nice UI now
Will try to open a ticket with their support.