[CM13] No WiFi after reboot - Galaxy S III Q&A, Help & Troubleshooting

Hi,
a have a very strange problem with my Wifi. I cant switch it on.
When I install a new nightly build of CM via TWRP wifi is working like a charm. But after a reboot the toggle WLAN doesnt work. Hotspot creation isnt working either.
I already tried:
- setting wifi_display_on on settings.db to 1 --> no effect at all
I tried to get more info from logcat with "adb logcat". When I type "su \ svc wifi enable" the log is showing:
08-23 08:59:46.177 8067 8067 D AndroidRuntime: Calling main entry com.android.commands.svc.Svc
08-23 08:59:46.177 1982 1982 E SELinux : avc: denied { find } for service=wifi scontext=u:r:sudaemon:s0 tcontext=ubject_r:wifi_service:s0 tclass=service_manager
08-23 08:59:46.182 2374 2686 D WifiService: setWifiEnabled: true pid=8067, uid=0
08-23 08:59:46.182 2374 2686 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
08-23 08:59:46.182 2374 2513 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
08-23 08:59:46.182 8067 8067 D AndroidRuntime: Shutting down VM
08-23 08:59:46.232 2374 2513 E WifiStateMachine: Failed to load driver
08-23 08:59:46.232 2374 2374 E WifiService: Wi-Fi state is failed
08-23 08:59:46.232 2374 2374 D WifiService: setWifiEnabled: false pid=2374, uid=1000
08-23 08:59:46.232 2374 2374 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
08-23 08:59:46.237 2374 2513 E WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
08-23 08:59:46.282 2374 2513 E WifiStateMachine: Failed to load driver
08-23 08:59:46.287 2374 2374 E WifiService: Wi-Fi state is failed
08-23 08:59:46.287 2374 2374 D WifiService: setWifiEnabled: false pid=2374, uid=1000
08-23 08:59:46.287 2374 2374 E WifiService: Invoking mWifiStateMachine.setWifiEnabled
Click to expand...
Click to collapse
MOD: 13.0-20160821-NIGHTLY-i9300
Kernel: 3.0.101-CM-g6112c4d
I am pretty stuck here. Please help me getting my Wifi working again. Thx in adavance.

factory reset ?

exe98123q said:
factory reset ?
Click to expand...
Click to collapse
I would like to avoid that.

from snapshot work for you ? nightly are not stabile
backup system and test imo

Facing the same issue though in all cm based ROMs.
However it gets fixed in s6 experience ROM. It did for me at least. But after flashing cm it again gets back to the same error. Let me know if you get a solution.
Sent from my GT-I9300 using XDA-Developers mobile app

magically fixed
Hi,
2 Days ago I installed the latest Nightly on my S3 and Wifi keeps working even after Repoot. I have no idea why but I am happy.
KR
HaVonTe

I encountered the problem some months back but it was fixed automatically when I flashed a tw ROM. But it occurred again,finally changed the modem to the latest version and it works now. After changing the modem tried cm13,cm14.1,miui8,two,aosp.
In all of em it works. Though I was in cm13 only for like a day. Mostly use AOSP and wifi, hotspot,bt all works fine now.
Sent from my GT-I9300 using XDA-Developers mobile app

Related

[Q] APN issue with CM based ROMs

Hi all,
i cannot connect to my business company using "non-standard" APN connection, with any CM based ROMs; default MMS and internet APNs work fine. I need to setup an APN that requires user and password with CHAP authentication type.
I've tried almost all CM (7,9,10) with the same results, the connection fails. No errors popup on my device. I've searched a lot for a solution without success. All works fine with the stock ROM (GB 2.3.4)
Here is the logcat with CM7 based (Neutrino)
Code:
I/RIL:chat( 9834): send (ATZ^M)
I/RIL:chat( 9834): expect (OK)
I/RIL:chat( 9834): ATZ^M^M
I/RIL:chat( 9834): OK
I/RIL:chat( 9834): -- got it
I/RIL:pppd( 9828): Serial port initialized.
I/RIL:chat( 9836): send (AT+CGDCONT=1,\"IP\",\"myprovider.tim.it\"^M)
I/RIL-MX ( 1361): Read Ch0 << 0716~+RSSI=0,11,99,99,0,0,0
I/RIL:chat( 9836): expect (OK)
I/RIL:chat( 9836): ^M
I/RIL:chat( 9836): AT+CGDCONT=1,"IP","myprovider.tim.it"^M^M
I/RIL:chat( 9836): OK
I/RIL:chat( 9836): -- got it
I/RIL:chat( 9836): send (^M)
I/RIL:chat( 9836): send (ATD*99#^M)
I/RIL:chat( 9836): expect (CONNECT)
I/RIL:chat( 9836): ^M
I/RIL:chat( 9836): ATD*99#^M^M
I/RIL:chat( 9836): CONNECT
I/RIL:chat( 9836): -- got it
I/RIL:chat( 9836): send (^M)
I/RIL:pppd( 9828): Serial connection established.
and this one from the stock ROM (GB 2.3.4 IT):
Code:
08-23 15:17:59.561 17853 17853 I RIL:chat: send (ATZ^M)
08-23 15:17:59.603 17853 17853 I RIL:chat: expect (OK)
08-23 15:17:59.633 17853 17853 I RIL:chat: ATZ^M^M
08-23 15:17:59.633 17853 17853 I RIL:chat: OK
08-23 15:17:59.633 17853 17853 I RIL:chat: -- got it
08-23 15:17:59.633 17845 17845 I RIL:pppd: Serial port initialized.
08-23 15:17:59.653 17855 17855 I RIL:chat: send (AT+CGDCONT=1,\"IP\",\"myprovider.tim.it\"^M)
08-23 15:18:00.023 17855 17855 I RIL:chat: expect (OK)
08-23 15:18:00.023 17855 17855 I RIL:chat: ^M
08-23 15:18:00.051 17855 17855 I RIL:chat: AT+CGDCONT=1,"IP","myprovider.tim.it"^M^M
08-23 15:18:00.051 17855 17855 I RIL:chat: OK
08-23 15:18:00.051 17855 17855 I RIL:chat: -- got it
[COLOR="Red"]08-23 15:18:00.051 17855 17855 I RIL:chat: send (AT$QCPDPP=1,2,\"password\",\"user\"^M)
08-23 15:18:00.411 17855 17855 I RIL:chat: expect (OK)
08-23 15:18:00.411 17855 17855 I RIL:chat: ^M
08-23 15:18:00.431 17855 17855 I RIL:chat: AT$QCPDPP=1,2,"password","user"^M^M
08-23 15:18:00.431 17855 17855 I RIL:chat: OK[/COLOR]
08-23 15:18:00.431 17855 17855 I RIL:chat: -- got it
08-23 15:18:00.431 17855 17855 I RIL:chat: send (^M)
08-23 15:18:00.441 17855 17855 I RIL:chat: send (ATD*99#^M)
08-23 15:18:00.511 14594 14594 D GSM : receive msg EVENT_INFORM_DISCONNECT_AFTER_DELAY to call onDataDisconnectDone().
08-23 15:18:00.511 14594 14594 D GSM : onDataDisconnectDone: scan cancelled, return mNetworkScanResponseMsg = null mIsNetworkQueryPending = false
08-23 15:18:00.521 17855 17855 I RIL:chat: expect (CONNECT)
08-23 15:18:00.521 17855 17855 I RIL:chat: ^M
08-23 15:18:00.551 17855 17855 I RIL:chat: ATD*99#^M
08-23 15:18:00.551 17855 17855 I RIL:chat: CONNECT
08-23 15:18:00.551 17855 17855 I RIL:chat: -- got it
08-23 15:18:00.551 17855 17855 I RIL:chat: send (^M)
as you can see there are some missing commands in CM7 (red text) that specify user and passowrd.
Already done:
wiped all
format system before flash
flashed new radio
various update from stock rom (ril and ppp)
Now i ran out of shots
Any idea?
Also problem here
The first custom ROM i used, was CM 10.1 and the APN worked fine.
I made a backup, and tried another ROM, the paranoid, and now any custom ROM i try, even CM7 doesn't connect to APN.
What can i possibly have made to screw completly my custom ROMs APN connection?
please help.

Help with nfc.apk

I can toggle nfc on and off but when rom first installs I get nfc service has stopped.
Here is log.
---- Aug 1, 2016 6:07:24 PM ----
08-01 18:06:02.964 628 628 I ServiceManager: service 'nfc' died
08-01 18:06:12.924 651 651 I drsd : relabeling: /data/data/com.android.nfc,com.android.nfc,platform,1027
08-01 18:06:15.864 27494 27494 I ActivityManager: Start proc com.android.nfc for added application com.android.nfc: pid=28260 uid=1027 gids={41027, 9997, 3002, 3001, 1028, 1015, 1023} abi=armeabi-v7a
08-01 18:06:15.884 2148 2148 E audit : type=1400 msg=audit(1470089175.884:5689): avc: denied { dyntransition } for pid=28260 comm="main" scontext=u:r:init:s0 tcontext=u:r:s_nfc:s0 tclass=process
08-01 18:06:15.884 2148 2148 E audit : type=1300 msg=audit(1470089175.884:5689): arch=40000028 syscall=4 per=800000 success=yes exit=13 a0=1a a1=ab69cab0 a2=d a3=b6f4225c items=0 ppid=27286 ppcomm=main pid=28260 auid=4294967295 uid=1027 gid=1027 euid=1027 suid=1027 fsuid=1027 egid=1027 sgid=1027 fsgid=1027 tty=(none) ses=4294967295 comm="main" exe="/system/bin/app_process32_xposed" subj=u:r:s_nfc:s0 key=(null)
08-01 18:06:16.134 28260 28260 W ResourcesManager: Asset path '/system/framework/com.broadcom.nfc.jar' does not exist or contains no resources.
08-01 18:06:28.030 27925 27925 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1686 android.content.ContextWrapper.sendBroadcast:391 android.content.ContextWrapper.sendBroadcast:391 com.android.settings.nfc.SBeamEnabler.updateState:-1 com.android.settings.nfc.SBeamEnabler.saveSbeamOn:-1
08-01 18:06:41.810 28260 30428 E SnepServer: at com.android.nfc.dhimpl.NativeLlcpServiceSocket.accept(NativeLlcpServiceSocket.java)
08-01 18:06:41.810 28260 30428 E SnepServer: at com.android.nfc.snep.SnepServer$ServerThread.run(SnepServer.java)
08-01 18:06:41.810 28260 30429 E NdefPushServer: at com.android.nfc.dhimpl.NativeLlcpServiceSocket.accept(NativeLlcpServiceSocket.java)
08-01 18:06:41.810 28260 30429 E NdefPushServer: at com.android.nfc.ndefpush.NdefPushServer$ServerThread.run(NdefPushServer.java)
08-01 18:06:41.810 28260 30431 E HandoverServer: at com.android.nfc.dhimpl.NativeLlcpServiceSocket.accept(NativeLlcpServiceSocket.java)
08-01 18:06:41.810 28260 30431 E HandoverServer: at com.android.nfc.handover.HandoverServer$ServerThread.run(HandoverServer.java)
08-01 18:06:45.180 31418 31495 I AMMetaDataParserService: Resource data:Loop for running activitycom.android.settings.nfc.NfcAdvancedRoutingSetting
08-01 18:06:45.240 31418 31495 I AMMetaDataParserService: Resource data:Loop for running activitycom.android.settings.nfc.PaymentDefaultDialog
08-01 18:06:46.070 27925 27925 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1686 android.content.ContextWrapper.sendBroadcast:391 android.content.ContextWrapper.sendBroadcast:391 com.android.settings.nfc.SBeamEnabler.updateState:-1 com.android.settings.nfc.SBeamStateReceiver.onReceive:-1
08-01 18:06:49.790 27925 27925 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1686 android.content.ContextWrapper.sendBroadcast:391 android.content.ContextWrapper.sendBroadcast:391 com.android.settings.nfc.SBeamEnabler.updateState:-1 com.android.settings.nfc.SBeamEnabler.saveSbeamOn:-1
---- Aug 1, 2016 6:07:24 PM ----

Need help interpreting dump file for system rebooting itself.

My phone just keep rebooting itself. It's been sent out for "repair" a couple times now and they aren't able to fix it. They did replace the mainboard, but it's still rebooting. I was able to capture the dumpstate and see where it crashed, but I just don't know how to interpret the info. Can anyone help?
Code:
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #1: 2 when =46076699 package=com.google.android.gmsoperation =*walarm*:com.google.android.gms.gcm.ACTION_CHECK_QUEUE
12-06 07:05:44.965 1392 2067 V AlarmManager: Triggering alarm #2: 2 when =46093358 package=androidoperation = null listenTag =*job.delay*
12-06 07:05:56.722 1392 1392 I DeviceIdleController: updateChargingLocked: charging=false
12-06 07:05:59.999 1392 2067 V AlarmManager: Triggering alarm #0: 3 when =46108403 package=androidoperation =*alarm*:android.intent.action.TIME_TICK
12-06 07:06:16.323 5536 5536 E AndroidRuntime: FATAL EXCEPTION: main
12-06 07:06:16.323 5536 5536 E AndroidRuntime: Process: com.android.bluetooth, PID: 5536
12-06 07:06:16.323 5536 5536 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-06 07:06:18.183 12055 12055 I chatty : uid=1000 system_server expire 15 lines
12-06 07:06:18.446 12055 12145 I chatty : uid=1000(system) CpuTracker expire 1 line
12-06 07:06:18.450 12055 12090 I chatty : uid=1000(system) batterystats-sy expire 1 line
12-06 07:06:18.452 12055 12055 I chatty : uid=1000 system_server expire 1 line
What is the full name of your device ?
Teddy Lo said:
What is the full name of your device ?
Click to expand...
Click to collapse
It's the OnePlus 5.
Did you tried to restore your phone back to stock ?
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
or try with this steps
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Teddy Lo said:
Did you tried to restore your phone back to stock ?
https://www.thecustomdroid.com/restore-oneplus-5-stock-firmware/
or try with this steps
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Click to expand...
Click to collapse
Yep, multiple times. However, they approved to just replace it so it's been shipped out to get replaced. But I would still be curious to know why it kept happening in the off chance an app or something else I was doing was causing it.

camera issues

I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use.
I got the logcats and i see this error -
02-12 10:46:44.252 760 760 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
I ran the nm command on the libguy.so and I find an undefined symbol there. I searched and found a shim that has this very symbol - libshim_camera_hal.so, I also found source files for this and found the function in device/motorola/sanders/libshims/camera_hal.cpp
I checked the shim file on the device, the shim file is present in /system/lib64 and /system/lib folders. libguy.so is in /system/vendor/lib and is 32bit.
Is this an LD_LIBRARY_PATH issue?
What can i do to fix this issue.
doors666 said:
I am having issues with custom rom that i built using lineage-15.1. My device is sanders. The camera is not working. The camera 2 app disappears soon after booting after installation. I installed open camera and it says camera is in use...
Click to expand...
Click to collapse
I don't have this device but, the following threads, that's device specific, may be helpful for what you are looking for and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3722844
https://forum.xda-developers.com/showthread.php?t=3708082
https://forum.xda-developers.com/showthread.php?t=3708997
If all else fails, try posting your question within the following thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3593531
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
are you building that lib shims?
in libshims/Android.mk
and in device.mk
Refer to this tree: https://github.com/Keertesh19/device_motorola_sanders
yes I am building that. the files do have slight differences though as I took the device,vendor,kernel from validus links. I also downloaded the validus tree using the manifest and built it and i get the same issue there also. but its not there in the latest published rom.
I still have this issue, tried a lot of things, but still no fix.
I downloaded the latest validus published ROM build and that works fine, no issues with the camera.
I synced the validus repo using the manifest file and made a build, camera does not work.
Steps -
repo sync with validus manifest.
lunch validus_sanders-userdebug
brunch sanders
clean install.
Am I missing some step here? One thing that bothered me is that brunch works fine, but make fails. The error (I think it was about java doc, it asks me to run make update-api, that also fails.
I extracted both the ROMs and did a compare on both ramdisk and /system, no significant difference that could cause this.
I extracted the shims from good rom and copied it onto the phone which had my built rom and it still did not work.
I tried fedora (26 and 27) and ubuntu (17.10 and 16.04 LTS) to make build, no difference.
I modified the initrc and modified the LD_SHIM_LIBS to include the full path for the shims, still does not work.
This is the error that I get in the logs -
03-02 09:32:31.853 2558 2558 I init : type=1400 audit(0.0:520): avc: denied { execute_no_trans } for uid=1006 path="/system/vendor/bin/mm-qcamera-daemon" dev="mmcblk0p53" ino=2817 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=1
03-02 09:32:31.924 2558 2558 F libc : CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...
03-02 09:32:31.924 2558 2558 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2558 (mm-qcamera-daem), pid 2558 (mm-qcamera-daem)
03-02 09:32:31.939 2561 2561 E cutils-trace: Error opening trace file: No such file or directory (2)
03-02 09:32:31.936 2562 2562 I crash_dump32: type=1400 audit(0.0:521): avc: denied { ptrace } for uid=1006 scontext=u:r:crash_dump:s0 tcontext=u:r:init:s0 tclass=process permissive=1
03-02 09:32:31.945 2562 2562 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
03-02 09:32:31.946 691 691 I /system/bin/tombstoned: received crash request for pid 2558
03-02 09:32:31.947 2562 2562 I crash_dump32: performing dump of process 2558 (target tid = 2558)
03-02 09:32:31.947 2562 2562 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-02 09:32:31.947 2562 2562 F DEBUG : Build fingerprint: 'google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys'
03-02 09:32:31.947 2562 2562 F DEBUG : Revision: '0'
03-02 09:32:31.947 2562 2562 F DEBUG : ABI: 'arm'
03-02 09:32:31.947 2562 2562 F DEBUG : pid: 2558, tid: 2558, name: mm-qcamera-daem >>> /system/vendor/bin/mm-qcamera-daemon <<<
03-02 09:32:31.947 2562 2562 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-02 09:32:31.948 2562 2562 F DEBUG : Abort message: 'CANNOT LINK EXECUTABLE "/system/vendor/bin/mm-qcamera-daemon": cannot locate symbol "_Z35eglQueryStringImplementationANDROIDPvi" referenced by "/system/vendor/lib/libguy.so"...'
03-02 09:32:31.948 2562 2562 F DEBUG : r0 00000000 r1 000009fe r2 00000006 r3 00000008
03-02 09:32:31.948 2562 2562 F DEBUG : r4 000009fe r5 000009fe r6 ff8a460c r7 0000010c
03-02 09:32:31.949 2562 2562 F DEBUG : r8 00000000 r9 ed86e010 sl 00000000 fp ff8a58a4
03-02 09:32:31.949 2562 2562 F DEBUG : ip ff8a4630 sp ff8a45f8 lr ed907309 pc ed905808 cpsr 200f0030
03-02 09:32:31.950 2562 2562 F DEBUG :
03-02 09:32:31.950 2562 2562 F DEBUG : backtrace:
03-02 09:32:31.950 2562 2562 F DEBUG : #00 pc 0005f808 /system/bin/linker (__dl_abort+63)
03-02 09:32:31.950 2562 2562 F DEBUG : #01 pc 00010931 /system/bin/linker (__dl___linker_init+2820)
03-02 09:32:31.950 2562 2562 F DEBUG : #02 pc 000156a4 /system/bin/linker (_start+4)
the latest changes to the device tree seems to have fixed this issue. thanx guys. though would love to know what was causing this issue.

s905x tv boxes problems with different launchers

I have a tv box with s905x running android 7.1.2. When i try to use different launcher than default (droidlogic mbox launcher), it force close it.
I searce the android log and i found that the error is probably with wallpaper manager. I have found that many people with tv boxes have the same problem.
Also if i try to put a wallpaper with an wallpaper app it crashes too.
The error is that WallpaperService not running.
How can i solve that?
Code:
9-05 20:22:06.328 4371 5498 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x13200000 cmp=net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard (has extras)} from uid 1000 on display 0
09-05 20:22:06.400 4371 4526 I ActivityManager: Start proc 11428:net.pierrox.lightning_launcher_extreme/u0a50 for activity net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard
09-05 20:22:06.512 4371 8711 W Binder : Binder call failed.
09-05 20:22:06.512 4371 8711 W Binder : java.lang.SecurityException: Neither user 1041 nor current process has android.permission.WAKE_LOCK.
09-05 20:22:06.512 4371 8711 W Binder : at android.app.ContextImpl.enforce(ContextImpl.java:1585)
09-05 20:22:06.512 4371 8711 W Binder : at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1617)
09-05 20:22:06.512 4371 8711 W Binder : at com.android.server.power.PowerManagerService$BinderService.updateWakeLockWorkSource(PowerManagerService.java:3453)
09-05 20:22:06.512 4371 8711 W Binder : at com.android.server.power.PowerManagerService$BinderService.updateWakeLockUids(PowerManagerService.java:3444)
09-05 20:22:06.512 4371 8711 W Binder : at android.os.IPowerManager$Stub.onTransact(IPowerManager.java:105)
09-05 20:22:06.512 4371 8711 W Binder : at android.os.Binder.execTransact(Binder.java:565)
09-05 20:22:06.514 4371 4642 I WindowManager: mLongPressOnHomeBehavior = 0
09-05 20:22:06.585 11428 11428 I art : Starting a blocking GC AddRemoveAppImageSpace
09-05 20:22:06.586 4371 4380 I art : Background partial concurrent mark sweep GC freed 13995(815KB) AllocSpace objects, 0(0B) LOS objects, 33% free, 8MB/13MB, paused 2.095ms total 126.137ms
09-05 20:22:06.586 11428 11428 W System : ClassLoader referenced unknown path: /system/lib/LightningLauncher
09-05 20:22:06.742 11428 11444 E ActivityThread: Failed to find provider info for net.pierrox.lightning_launcher.lwp_key
09-05 20:22:06.880 11428 11428 I auncher_extreme: type=1400 audit(0.0:297): avc: denied { read write } for name="gsm" dev="tmpfs" ino=10303 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:gsm_device:s0 tclass=chr_file permissive=1
09-05 20:22:06.880 11428 11428 I auncher_extreme: type=1400 audit(0.0:298): avc: denied { open } for path="/dev/gsm" dev="tmpfs" ino=10303 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:gsm_device:s0 tclass=chr_file permissive=1
09-05 20:22:07.368 11428 11428 W WallpaperManager: WallpaperService not running
09-05 20:22:07.369 11428 11428 E AndroidRuntime: FATAL EXCEPTION: main
09-05 20:22:07.369 11428 11428 E AndroidRuntime: Process: net.pierrox.lightning_launcher_extreme, PID: 11428
09-05 20:22:07.369 11428 11428 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
09-05 20:22:07.373 4371 4920 W ActivityManager: Force finishing activity net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard
I started android 8.1 treble and l also have a problem with droidlogic .

Categories

Resources