search

Jasper-1024 / NoWakeLock

An application that controls Android wakelocks can run on Android N and later.
GNU General Public License v3.0
97 stars 8 forks source link

[BUG] Doesn't work on Android 14 #17

Closed HarriBuh closed 5 months ago

HarriBuh commented 9 months ago

I don't understand why Instagram is involved in this issue, though...

[Device Model]: Pixel 7

[Stack Trace]: java.lang.IllegalArgumentException: Unknown package: com.instagram.lite at android.os.Parcel.createExceptionOrNull(Parcel.java:3061) at android.os.Parcel.createException(Parcel.java:3041) at android.os.Parcel.readException(Parcel.java:3024) at android.os.Parcel.readException(Parcel.java:2966) at android.content.pm.IPackageManager$Stub$Proxy.getApplicationEnabledSetting(IPackageManager.java:6125) at android.app.ApplicationPackageManager.getApplicationEnabledSetting(ApplicationPackageManager.java:3117) at com.js.nowakelock.data.repository.appdas.AppDasAR.getSysAppInfo(AppDasAR.kt:138) at com.js.nowakelock.data.repository.appdas.AppDasAR.access$getSysAppInfo(AppDasAR.kt:28) at com.js.nowakelock.data.repository.appdas.AppDasAR$getSysAppInfos$2.invokeSuspend(AppDasAR.kt:118) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664) Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@1afebc4, Dispatchers.Main.immediate]

Jasper-1024 commented 9 months ago

Ok, after receiving the feedback, I will flash the device I have to Android 14 in the near future to reproduce the problem.

According to the log content, the problem is caused by changes in the system API and has nothing to do with Instagram. It may just happen that Instagram applies for a wake lock, and then accesses the changed system API when recording nowakelock.

HarriBuh commented 5 months ago

Any news on this issue? It's already June

Jasper-1024 commented 5 months ago

yes...😢😢😢