Android default services are not running on hikey960


#1

Hi,

There were some services running, because of which dmesg logs were continuously scrolling.
But now suddenly no logs are seen, completely stopped even I tried flashing the earlier working images.
Please suggest should I need to run some commands??

Thanks


#2

Could you please clarify your issue, is it a problem with ‘logging’ or a board booting issue ?
Do you have a serial console? if yes please attach the output.


#3

With the same images flashed, earlier below logs are continuously coming on the console, so I use to give stop command to access the command prompt.

[ 91.192230] (stk) : waiting for ver info- timed out or received signal
[ 91.198808] (stk) :kim: failed to read local ver
[ 91.201964] (stk) :download firmware failed
[ 91.206401] (stk) :ldisc_install = 0
[ 91.208805] (stc): st_tty_close
[ 91.214064] (hci_tty): st_register failed -22
[ 91.494516] logd: logdr: UID=1002 GID=1002 PID=3773 n tail=5 logMask=8 pid=3692 start=0ns timeout=0ns
[ 91.506850] logd: logdr: UID=1002 GID=1002 PID=3773 n tail=5 logMask=1 pid=3692 start=0ns timeout=0ns
[ 92.548535] logd: logdr: UID=1002 GID=1002 PID=3773 n tail=0 logMask=8 pid=3692 start=0ns timeout=0ns
[ 92.560092] logd: logdr: UID=1002 GID=1002 PID=3773 n tail=0 logMask=1 pid=3692 start=0ns timeout=0ns
[ 92.590607] init: Untracked pid 3773 exited with status 0
[ 92.624673] binder: release 3692:3725 transaction 15842 in, still active
[ 92.631423] binder: release 3692:3725 transaction 15839 out, still active
[ 92.656244] binder: send failed reply for transaction 15842 to 3690:3690
[ 92.738192] logd: logdr: UID=1002 GID=1002 PID=3793 n tail=5 logMask=8 pid=3690 start=0ns timeout=0ns
[ 92.750450] logd: logdr: UID=1002 GID=1002 PID=3793 n tail=5 logMask=1 pid=3690 start=0ns timeout=0ns
[ 92.764108] logd: logdr: UID=1002 GID=1002 PID=3793 n tail=0 logMask=8 pid=3690 start=0ns timeout=0ns
[ 92.775782] logd: logdr: UID=1002 GID=1002 PID=3793 n tail=0 logMask=1 pid=3690 start=0ns timeout=0ns
[ 92.793930] init: Service ‘bluetooth-1-0’ (pid 3690) killed by signal 6
[ 92.801574] init: Sending signal 9 to service ‘bluetooth-1-0’ (pid 3690) process group…
[ 92.810204] binder: release 3690:3690 transaction 15839 in, still active
[ 92.817353] init: Successfully killed process cgroup uid 1002 pid 3690 in 0ms
[ 92.824715] binder: send failed reply for transaction 15839, target dead
[ 92.841064] init: Untracked pid 3793 exited with status 0
[ 92.858458] init: starting service ‘bluetooth-1-0’…

But now no logs are coming it is stopping at below logs:

u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0
[ 38.705894] type=1400 audit(36.535:140): avc: denied { write } for pid=2088 comm=“Thread-7” name=“timerslack_ns” dev=“proc” ino=19176 scontext=u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0
[ 38.726266] type=1400 audit(36.535:140): avc: denied { write } for pid=2088 comm=“Thread-7” name=“timerslack_ns” dev=“proc” ino=19176 scontext=u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0
[ 38.746528] type=1400 audit(36.535:141): avc: denied { write } for pid=2088 comm=“Thread-7” name=“timerslack_ns” dev=“proc” ino=20572 scontext=u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0
[ 38.768565] type=1400 audit(36.535:141): avc: denied { write } for pid=2088 comm=“Thread-7” name=“timerslack_ns” dev=“proc” ino=20572 scontext=u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0

please suggest.

Thanks


#4

Don’t use stop for this, you stop pretty all your android services.
You already have the prompt if you enter the stop command.
If you are annoyed by the log in the console, use dmesg -n 1 to reduce log level, or use adb.


#5

Yes you are right.
But my concern is those logs are not coming now, stops at:

[ 38.768565] type=1400 audit(36.535:141): avc: denied { write } for pid=2088 comm=“Thread-7” name=“timerslack_ns” dev=“proc” ino=20572 scontext=u:r:system_server:s0 tcontext=u:r:mediaprovider:s0:c512,c768 tclass=file permissive=0


#6

Can you let me why logs are stopped.


#7

Does your device remain functional ? Are you able to retrieve log from logcat command ?

The avc:denied (SeLinux) issue is does not seem to be a critical one, you can try to set SeLinux to permissive with:
$ adb root && adb shell setenforce 0
And see if this makes any difference.


#8

Yes my device is functioning properly. I have built system.img and flashed, worried that is it causing any issues.

$ adb root && adb shell setenforce 0

No difference seen.


#9

Once the device has booted you should not see much more log in the console except some kernel message, by default warning and errors, so when something is going wrong.

You can dump Android system messages with the logcat command.