intermittently stuck booting phone "Sensor Manager"

joelphilippage

Senior Member
Apr 18, 2015
166
76
0
Phoenix
Since about DP4 of Android P I have had an issue where my Pixel 2 gets stuck booting. Occasionally when rebooting the phone gets to the Google logo, then starts showing the loading bar beneath it. I have taken a logcat while this is happening and am getting these logs repeated:

Code:
08-14 07:45:31.490 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:31.680 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:32.491 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:32.681 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:32.950 881-881/? I/ServiceManager: Waiting for service sensorservice...
08-14 07:45:33.491 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:33.681 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:33.955 881-881/? I/ServiceManager: Waiting for service sensorservice...
08-14 07:45:34.492 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:34.681 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:34.960 881-881/? I/ServiceManager: Waiting for service sensorservice...
08-14 07:45:35.492 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:35.682 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:35.966 881-881/? I/ServiceManager: Waiting for service sensorservice...
08-14 07:45:36.492 769-1469/? W/ServiceManagement: Waited one second for [email protected]::ISensorManager/default. Waiting another...
08-14 07:45:36.682 1172-1172/? W/ServiceManagement: Waited one second for [email protected]::IMemtrack/default. Waiting another...
08-14 07:45:36.972 881-881/? I/ServiceManager: Waiting for service sensorservice...
08-14 07:45:37.073 881-881/? W/ServiceManager: Service sensorservice didn't start. Returning NULL
The easiest reliable fix I have found is booting to fastboot first then selecting start. It has always booted up using this method.

The first couple of times this happened I reset the phone by flashing a factory image with wiping user data. This allowed it to boot up but I saw that problem again later.

This has also only happened while the phone is rooted using Magisk and has happened without any modules installed. I'm not sure if this would happen without root but I have never seen it happen.

This is a Verizon Pixel 2 I got refurbished with the bootloader unlocked using the exploit with a certain version.

I have not gotten permanently stuck but I would like to know if there is a fix or if it is a hardware problem so I could ask for a replacement.

Thanks!

-Joel
 

hoban_eris

Senior Member
Jan 15, 2010
238
6
0
This worked for me

Hey Joel, I doubt you still care about this issue, given how long you've gone without a response, but since I found your question as a top google result for this issue, and because I just encountered it and worked around it myself, here's this for future posterity: https://github.com/topjohnwu/Magisk/issues/543
Specifically, I had to boot to recovery mode, then delete some files (be careful with the command as you're deleting data):
Code:
# rm -rf /data/adb/*
Best of luck.
 

maszeta

Member
Feb 24, 2016
25
7
3
This worked for me

Hey Joel, I doubt you still care about this issue, given how long you've gone without a response, but since I found your question as a top google result for this issue, and because I just encountered it and worked around it myself, here's this for future posterity: https://github.com/topjohnwu/Magisk/issues/543
Specifically, I had to boot to recovery mode, then delete some files (be careful with the command as you're deleting data):
Code:
# rm -rf /data/adb/*
Best of luck.
Dude, thank you so much! It worked

To improve your answer, I would say it's a good thing to backup the folder before deleting its contents by executing this in your pc:
Bash:
adb pull /data/adb/