Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted.
They in fact check if SE Linux is in enforcement mode. Here is the log snippet:
Code:
11-23 18:44:54.894 2259 2521 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity bnds=[350,815][506,994] (has extras)} from uid 10036
11-23 18:44:54.935 2084 2084 I display : [DYNAMIC_RECOMP] HWC_2_GLES by low FPS(0)
11-23 18:44:54.969 2259 4027 I ActivityManager: Start proc 20526:com.fidor.fsw/u0a119 for activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
11-23 18:44:55.190 2084 2084 I display : [DYNAMIC_RECOMP] GLES_2_HWC by high FPS(39)
11-23 18:44:55.229 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libEGL_mali.so from the current namespace instead.
11-23 18:44:55.326 20526 20540 D libEGL : loaded /system/lib/egl/libEGL_mali.so
11-23 18:44:55.339 2084 2133 W GrallocMapperPassthrough: buffer descriptor with invalid usage bits 0x400
11-23 18:44:55.356 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv1_CM_mali.so from the current namespace instead.
11-23 18:44:55.362 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv1_CM_mali.so
11-23 18:44:55.586 20526 20540 I vndksupport: sphal namespace is not configured for this process. Loading /system/lib/egl/libGLESv2_mali.so from the current namespace instead.
11-23 18:44:55.588 20526 20540 D libEGL : loaded /system/lib/egl/libGLESv2_mali.so
11-23 18:44:56.455 20526 20526 I putmethod.latin: type=1400 audit(0.0:774): avc: denied { read } for name="/" dev="tmpfs" ino=3689 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:rootfs:s0 tclass=dir permissive=1
11-23 18:44:56.455 20526 20526 W putmethod.latin: type=1300 audit(0.0:774): arch=40000028 syscall=334 per=800008 success=yes exit=0 a0=ffffff9c a1=898ca354 a2=4 a3=0 items=1 ppid=2066 auid=4294967295 uid=10119 gid=10119 euid=10119 suid=10119 fsuid=10119 egid=10119 sgid=10119 fsgid=10119 tty=(none) ses=4294967295 exe="/system/bin/app_process32" subj=u:r:untrusted_app_25:s0:c512,c768 key=(null)
11-23 18:44:56.455 1978 1978 W auditd : type=1307 audit(0.0:774): cwd="/"
11-23 18:44:56.455 1978 1978 W auditd : type=1302 audit(0.0:774): item=0 name="/sbin" inode=3689 dev=00:12 mode=040755 ouid=0 ogid=0 rdev=00:00 obj=u:object_r:rootfs:s0
11-23 18:44:56.455 1978 1978 W auditd : type=1327 audit(0.0:774): proctitle="com.google.android.inputmethod.latin"
11-23 18:44:56.455 1978 1978 W auditd : type=1320 audit(0.0:774):
11-23 18:44:56.527 2259 3192 W ActivityManager: Force finishing activity com.fidor.fsw/com.gft.fidor.views.splash.SplashScreenActivity
Since LineageOS sets SELinux by default into permissive, this check fails and the app crashes. I'm able to set it to enforced with "SE Linux mode changer" or any other app of that kind, but immediately after the change the phone starts eating 100% cpu and modem (neither internet, nor SMS/phone calls) aren't working, which makes me think LineageOS doesn't work really well in enforcement mode of SE Linux. But the app itself launches just fine with SELinux in enforced.
I'm not an expert in Android and SELinux, but would like to know if there is a way:
to workaround the check we see in the logs and work with the app in permissive mode
to make LineageOS work correctly under enforced
PS. It doesn't matter which way to set the SELinux mode. Whatever is done - through kernel, in init.d or in adb shell, the symptoms are exactly the same after the change.
Thanks
bytes85 said:
Hi,
I'm running LineageOS 15 (Android 8) on S5 mini. Everything is fine except one banking app that I really need. They validate on startup, whether the phone is rooted...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Unofficial LineageOS (since there's no Official LineageOS Oreo released yet) thread for your device.
https://forum.xda-developers.com/showthread.php?t=3678205
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
Hey guys,
i have a problem when building 4.0.3 from source. When i flash the fresh compiled
OTA package to my device, the device ends in a bootloop stuck at the google logo.
Logcat says:
Code:
I/SystemServer( 238): Power Manager
I/SystemServer( 238): Activity Manager
I/ActivityManager( 238): Memory class: 64
I/SurfaceFlinger( 251): SurfaceFlinger is starting
I/SurfaceFlinger( 251): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/IMGSRV ( 251): :0: PVRSRVBridgeCall: Failed to access device. Function ID:3223086860 (Bad address).
E/IMGSRV ( 251): :0: OpenServices: PVRSRVBridgeCall failed.
E/IMGSRV ( 251): :0: PVRSRVConnect: Unable to open connection.
E/IMGSRV ( 251): :0: OpenPVRServices: Failed to open services connection
E/IMGSRV ( 251): :0: hal_init: Failed to open services (err=-14)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open framebuffer HAL (Not a typewriter)
E/IMGSRV ( 251): :0: hal_open: Graphics HAL not initialized
E/FramebufferNativeWindow( 251): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 251): Display subsystem failed to initialize. check logs. exiting...
I/ServiceManager( 109): service 'sensorservice' died
I/ServiceManager( 109): service 'power' died
I/ServiceManager( 109): service 'entropy' died
D/AndroidRuntime( 259):
D/AndroidRuntime( 259): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 259): CheckJNI is OFF
I don't know whats going wrong. Can it be a kernel problem? I have tried different 4.0.3 kernels from the dev section, but the result is the same.
The device is a GSM device with PRIMEKK15 unlocked bootloader and I9250XXKK6 baseband.
After pulling the latest 4.0.3 sources with repo and setting up the proprietary files i'have compiled the system without errors:
Code:
~/android/4.0.3$ . build/envsetup.sh
~/android/4.0.3$ lunch full_maguro-userdebug
~/android/4.0.3$ make -j4 otapackage
I really don't understand what i am doing wrong ...
Thanks for any suggestions or answers.
my camera on Desier HD stop working. Each time I tried to open Camera aplication, I received message - unable to connect to camera
I tried use also different apps, I also tried to install my ROM again with all wipes and factory reset without success.
All was working fine before with this ROM, camera stoped working about 3 days ago. Only thing I know about is that it afll down on carpet from my hands. Tha t day I tried later to make phone and camera was not working.
Is there any apps how to test if there is HW problem with camera?
I'm using this ROM: JellyTime for DHD 4.2.2 R11
/devlog/system_log:
Code:
11-23 23:54:47.978 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.028 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Sun Jun 23 14:18:49 PDT 2013
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build description: yakju-user 4.2.2 JDQ39 573038 release-keys
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
11-23 23:54:48.208 E/QualcommCameraHardware( 1484): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
11-23 23:54:48.218 E/QualcommCameraHardware( 1484): createInstance: startCamera failed!
11-23 23:54:48.218 E/CameraClient( 1484): Could not open camera 0: -1
11-23 23:54:48.218 E/CameraClient( 1484): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
11-23 23:54:48.218 E/CameraHolder( 4195): fail to connect Camera
11-23 23:54:48.218 E/CameraHolder( 4195): java.lang.RuntimeException: Fail to connect to camera service
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.native_setup(Native Method)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.<init>(Camera.java:340)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.open(Camera.java:302)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:291)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.Util.openCamera(Util.java:478)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:344)
11-23 23:54:48.228 W/SensorService( 1809): sensor 00000000 already enabled in connection 0x51df4d58 (ignoring)
11-23 23:54:50.430 W/InputMethodManagerService( 1809): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000c in package table 0 because it is not complex!
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000d in package table 0 because it is not complex!
Thank You for help
jordibravo said:
my camera on Desier HD stop working. Each time I tried to open Camera aplication, I received message - unable to connect to camera
I tried use also different apps, I also tried to install my ROM again with all wipes and factory reset without success.
All was working fine before with this ROM, camera stoped working about 3 days ago. Only thing I know about is that it afll down on carpet from my hands. Tha t day I tried later to make phone and camera was not working.
Is there any apps how to test if there is HW problem with camera?
I'm using this ROM: JellyTime for DHD 4.2.2 R11
/devlog/system_log:
Code:
11-23 23:54:47.978 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.028 E/WVMExtractor( 1484): Failed to open libwvm.so
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build changelist:
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build date: Sun Jun 23 14:18:49 PDT 2013
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): build description: yakju-user 4.2.2 JDQ39 573038 release-keys
11-23 23:54:48.168 E/QualcommCameraHardware( 1484): android::QualcommCameraHardware::QualcommCameraHardware(): sense version:
11-23 23:54:48.208 E/QualcommCameraHardware( 1484): startCamera X: /dev/msm_camera/control0 open failed: No such file or directory!
11-23 23:54:48.218 E/QualcommCameraHardware( 1484): createInstance: startCamera failed!
11-23 23:54:48.218 E/CameraClient( 1484): Could not open camera 0: -1
11-23 23:54:48.218 E/CameraClient( 1484): initialize: Camera 0: unable to initialize device: Operation not permitted (-1)
11-23 23:54:48.218 E/CameraHolder( 4195): fail to connect Camera
11-23 23:54:48.218 E/CameraHolder( 4195): java.lang.RuntimeException: Fail to connect to camera service
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.native_setup(Native Method)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.<init>(Camera.java:340)
11-23 23:54:48.218 E/CameraHolder( 4195): at android.hardware.Camera.open(Camera.java:302)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:291)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.Util.openCamera(Util.java:478)
11-23 23:54:48.218 E/CameraHolder( 4195): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:344)
11-23 23:54:48.228 W/SensorService( 1809): sensor 00000000 already enabled in connection 0x51df4d58 (ignoring)
11-23 23:54:50.430 W/InputMethodManagerService( 1809): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000c in package table 0 because it is not complex!
11-23 23:54:50.490 W/ResourceType( 1809): Skipping entry 0x7f04000d in package table 0 because it is not complex!
Thank You for help
Click to expand...
Click to collapse
I suppose there is a loose connection between camera module and circuit board
sent from my Nokia Lumia 820
the easiest way to make sure is flashing stock rom. if it doesnt work, it is most likely hw
Same problem here
I'm not well versed in this type of work but I'm using a Samsung S4mini and Windows 10. From this debugging report, can someone help me figure out what is wrong ?
11-23 19:07:00:793 W/I Tool version : 3.19
11-23 19:07:00:793 W/I adb.exe
11-23 19:07:00:793 W/I aapt.exe
11-23 19:07:00:923 W/I Android Debug Bridge version 1.0.31
11-23 19:07:01.84 A/W process (30772) : Implicit intents with startService are not safe: Intent { act=service.tracetool.SocketService.ACTION (has extras) } android.content.ContextWrapper.startService:506 android.content.ContextWrapper.startService:506 service.tracetool.TTBroadcastReceiver.onReceive:41
11-23 19:07:01.85 A/I UsbThread : thread main : wait current UsbThread to terminate 0
11-23 19:07:01.85 A/I UsbThread2.run() needToBeClosed is true
11-23 19:07:02:510 W/I Wait java service
11-23 19:07:02:617 W/I waiting android server connection ... 1
11-23 19:07:02.25 A/I UsbThread2 : thread stopped
11-23 19:07:02.35 A/I TunnelController : thread stopped
11-23 19:07:02:875 W/I Waiting for connection
11-23 19:07:02.76 A/I TunnelController : thread stopped
11-23 19:07:02.86 A/I UsbThread3 : usbServerSocket : Waiting for the host to connect
11-23 19:07:05:108 W/I Sending busybox21
11-23 19:07:04.94 A/E UsbThread3.run() loop error. firstByte : 39 : WTOA_copyFile
11-23 19:07:04.94 A/E UsbThread3.run() loop error. lastCommand : 32 : WTOA_setGlobalVar
11-23 19:07:04.94 A/E UsbThread3.run() loop error. Exception type : class java.io.FileNotFoundException
11-23 19:07:04.94 A/E UsbThread3.run() loop error. Exception message : /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E UsbThread3.run() loop error. Exception cause : libcore.io.ErrnoException: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E UsbThread3.run() loop error. Exception string : java.io.FileNotFoundException: /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
11-23 19:07:04.95 A/E libcore.io.IoBridge.open(IoBridge.java:409)
11-23 19:07:04.95 A/E java.io.FileInputStream.<init>(FileInputStream.java:78)
11-23 19:07:04.95 A/E service.tracetool.Api.copy(Api.java:1471)
11-23 19:07:04.95 A/E service.tracetool.UsbThread.copyFile(UsbThread.java:1944)
11-23 19:07:04.95 A/E service.tracetool.UsbThread.run(UsbThread.java:316)
11-23 19:07:04.96 A/E UsbThread3.run() -> unexpected disconnection
11-23 19:07:04.96 A/I UsbThread3 : usbServerSocket : Waiting for the host to connect
11-23 19:07:15:538 W/D UsbThread : ReadBytes : Connection Closed Gracefully.
Server List at 11-23 19:08:05:322
DNS List
24.200.241.37
24.202.72.13
24.200.0.1
192.168.42.129
Did you use supersu?
Which version android?
Use busybox?
erkin98 said:
Did you use supersu?
Which version android?
Use busybox?
Click to expand...
Click to collapse
Sorry for not updating my posting but by reading other postings I tried to install Busybox on its own and it worked for me. Thanks for looking into it for me
GANBRO said:
Sorry for not updating my posting but by reading other postings I tried to install Busybox on its own and it worked for me. Thanks for looking into it for me
Click to expand...
Click to collapse
Your welcome
D/PermissionCache( 351): checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (114 us)
I/AudioMixer( 374): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
D/AMZ-audio_hw_primary( 374): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/AMZ-hardware_info( 374): hw_info_append_hw_type : device_name = speaker
D/AMZ-ACDB-LOADER( 374): ACDB -> send_audio_cal, acdb_id = 53, path = 0
D/AMZ-metrics.platform_audio( 374): audio_hw:device_enabled:speaker=1;CT;1:NR
I/FA ( 1460): Tag Manager is not found and thus will not be used
V/PanelView( 1279): animationTick called with dtms=0; nothing to do (h=1184.0 v=-4000.0)
D/AMZ-ExternalSpeakerAmpControl( 374): Loading /etc/audio/speakers/dsp_software.patch for channel 0
I/QCOM PowerHAL( 374): Processing audio hint. Metadata: state=0
D/AMZ-ExternalSpeakerAmpControl( 374): Completed initializing speaker for channel 0. Result = 0
D/Mms:app ( 1937): cancelNotification
D/AMZ-ExternalSpeakerAmpControl( 374): Loading /etc/audio/speakers/dsp_software.patch for channel 1
I/Adreno-EGL( 1937): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: ()
I/Adreno-EGL( 1937): OpenGL ES Shader Compiler Version: E031.24.00.15
I/Adreno-EGL( 1937): Build Date: 11/12/14 Wed
I/Adreno-EGL( 1937): Local Branch:
I/Adreno-EGL( 1937): Remote Branch:
I/Adreno-EGL( 1937): Local Patches:
I/Adreno-EGL( 1937): Reconstruct Branch:
D/OpenGLRenderer( 1937): Enabling debug mode 0
D/AMZ-ExternalSpeakerAmpControl( 374): Completed initializing speaker for channel 1. Result = 0
D/AMZ-ExternalSpeakerAmpControl( 374): EnableAmps complete. Result = 0
D/AMZ-audio_speaker_platform( 374): Loading speaker use case "music"
D/Mms:app ( 1937): new threadId: -2
D/Mms:app ( 1937): cancelNotification
V/RenderScript( 1937): Application requested CPU execution
V/RenderScript( 1937): 0x7639bc08 Launching thread(s), CPUs 4
I/ActivityManager( 1153): Displayed com.android.mms/.ui.ConversationList: +418ms
I/Timeline( 1153): Timeline: Activity_windows_visible id: ActivityRecord{41c209d0 u0 com.android.mms/.ui.ConversationList t2} time:57099
D/Mms ( 1937): [1] mDeleteObsoleteThreadsRunnable calling asyncDeleteObsoleteThreads
I/ServiceManager( 434): Waiting for service AtCmdFwd...
D/Mms:app ( 1937): cancelNotification
D/Mms ( 1937): [1] onQueryComplete finished DELETE_OBSOLETE_THREADS_TOKEN
I/Timeline( 1937): Timeline: Activity_idle id: [email protected] time:57124
D/PackageManager( 1153): Ignoring attempt to set enabled state of disabled component com.google.android.gsf/com.google.android.gsf.update.SystemUpdateActivity
D/PackageManager( 1153): Ignoring attempt to set enabled state of disabled component com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$ SecretCodeReceiver
D/PackageManager( 1153): Ignoring attempt to set enabled state of disabled component com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService$ Receiver
D/AMZ-Atfwd_Sendcmd( 434): AtCmdFwd service not published, waiting... retryCnt : 4
someone knows how to see logcat?
Hi,
on latest nightly LineageOS 15.1 Android Auto crashes with "Google Play Services not working" on startup.
Log:
Code:
11-14 13:02:26.748 1107 2869 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[440,288][640,561]} from uid 10033
11-14 13:02:26.868 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +90ms
11-14 13:02:27.083 8728 8728 I GH.LifetimeManager: connectToCarService
11-14 13:02:27.084 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.125 1107 5646 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.car.service.START pkg=com.google.android.gms } U=0: not found
11-14 13:02:27.129 8728 8979 E GmsClient: unable to connect to service: com.google.android.gms.car.service.START on com.google.android.gms
11-14 13:02:27.130 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#1
11-14 13:02:27.145 8728 8728 W GH.CarApiClientManager: connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-14 13:02:27.145 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.183 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#2
API_UNAVAILABLE sounds like I missed something to install? I'm using Open GApps Mini. Android auto menu item is also missing in settings - google - services menu.
Same setup on other devices for example HTC M8s works without problem.
Anyone seen this issue before and may help?
Edit:
Got it somehow working for now. I was in settings - google - show debug items (in top menu) - google play services modules (at the bottom) - car / car_setup. There I did check for updates nothing happened went back to GCM Diagnostics pressed disconnect, then connect, and ping nothing really happened again. Then I went back did hide debug items now Android auto menu was present and I was able to startup Android Auto without the error.
Log seems fine now:
Code:
11-17 23:26:19.848 1107 2924 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[241,612][440,885]} from uid 10033
11-17 23:26:19.970 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +77ms
11-17 23:26:20.187 15152 15152 I GH.LifetimeManager: connectToCarService
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: start
11-17 23:26:20.195 15152 15178 D CAR.CLIENT: connect [email protected]
11-17 23:26:20.212 14973 14987 D CAR.SERVICE: Package validated: com.google.android.projection.gearhead
11-17 23:26:20.215 14973 14987 D CAR.SERVICE: Android Auto has car home but both aliases are disabled. Nothing to do
11-17 23:26:20.235 15152 15152 D CAR.CLIENT: onICarAvailable [email protected]
11-17 23:26:20.236 14973 14987 D CAR.SERVICE: Registering [email protected]
11-17 23:26:20.236 15152 15152 I GH.CarApiClientManager: connected
11-17 23:26:20.236 15152 15152 D GH.CarApiClientManager: calling onConnected on [email protected]
11-17 23:26:20.247 11394 11394 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.248 11394 11394 D GH.CarApiClientManager: start
Still I do not know what was causing the issue. I was always able to use Android Auto until it was broken for no reason. Maybe some strange issue while disconnecting from the car caused the car play service to crash. Nevertheless, reboot alone did not fix it. I'll report back if it breaks again in the future and maybe dump logs directly after the incident.