[Bug] No such field runtime

[Archanial]

Describe the issue

There's the runtime that happens every 2 to 3 hours.

Steps to reproduce

No idea. My best guess it's related to double tap screen wake, since it's not always working when double tapping quickly.

Expected bahavior

No response

Your device setup (Please take some time to give correct information here)

Pixel 7 pro, stock, rooted with magisk 25.2, security update September 5th.
Lsposed 1.8.5, aosp 2.4.0, no other modules

Logs

I'll attach them in a minute

[Archanial]

trace_05.txt

[siavash79]

Nice catch

[EleoXDA]

One question though, why September sec patch with pixel 7 pro? Do we still continue to support pre-Dec sec patch devices?

[Archanial]

No reason in particular, just never updated.

[EleoXDA]

No reason in particular, just never updated.

Well, November sec patch and below is no longer updated. That is why I am asking. If you can reproduce it on Dec+ security patch we can discuss it

[Archanial]

I'll update in a bit and try to reproduce the bug.

[EleoXDA]

Ok. Please do and create an issue

[siavash79]

It MAY be still present in new versions. Let's keep it around to check it

[EleoXDA]

It MAY be still present in new versions. Let's keep it around to check it

that is what I said to him. to open an issue after updating to Dec. But I no longer see it on Dec. It was present in Nov though

[Archanial]

Updated to 2.5.0, December 5th security update and the runtime is still there.

[EleoXDA]

Updated to 2.5.0, December 5th security update and the runtime is still there.

Please share LSposed logs zip here

[Archanial]

LSPosed_2022-12-30T17_55_41.198597.zip
Here are full lsposed logs.

[EleoXDA]

trace_05.txt

I cannot find the logs you shared in this traces file you attached 🤔

LSPosed_2022-12-30T17_55_41.198597.zip
Here are full lsposed logs.

Could you also share your AOSPMods settings?

To get AOSPMods settings, go to 3dot menu->import/export->export settings to a file and save it to a file. If you cannot upload the file to GitHub, try to add it in a zipped folder before uploading.

I checked but I cannot see the same error you have. It has to do something with your settings so we will need to reproduce with your options as this is probably not something that happens while installing AOSPMods but rather happens when some option is enabled. On our device there is no such error in full.log:

[Archanial]

aospsettings.zip
here are my settings

here's the screenshot from runtime happening on version 2.5.0

Reading the runtime and considering the screen doesn't always wake up when double tapped I can only assume the runtime happens when this setting is enabled:

Also the runtime always gets logged when I double tap the screen quickly two times in order to wake the phone up.

[EleoXDA]

aospsettings.zip
here are my settings

here's the screenshot from runtime happening on version 2.5.0

Reading the runtime and considering the screen doesn't always wake up when double tapped I can only assume the runtime happens when this setting is enabled:

Also the runtime always gets logged when I double tap the screen quickly two times in order to wake the phone up.

Now it is reproducible. It doesn't react when you tap too fast or tap too slow. That is expected behavior.

But the error may need more attention:

E LSPosed-Bridge: java.lang.NoSuchFieldError: com.android.keyguard.KeyguardUpdateMonitor#mBouncer
E LSPosed-Bridge: 	at de.robv.android.xposed.XposedHelpers.lambda$findField$1(Unknown Source:6)
E LSPosed-Bridge: 	at de.robv.android.xposed.XposedHelpers.j(Unknown Source:0)
E LSPosed-Bridge: 	at de.robv.android.xposed.c.get(Unknown Source:28)
E LSPosed-Bridge: 	at java.util.Optional.orElseThrow(Optional.java:404)
E LSPosed-Bridge: 	at de.robv.android.xposed.XposedHelpers.findField(Unknown Source:25)
E LSPosed-Bridge: 	at de.robv.android.xposed.XposedHelpers.getBooleanField(Unknown Source:4)
E LSPosed-Bridge: 	at sh.siava.AOSPMods.systemui.FingerprintWhileDozing$1.afterHookedMethod(FingerprintWhileDozing.java:54)
E LSPosed-Bridge: 	at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(Unknown Source:147)
E LSPosed-Bridge: 	at LSPHooker_.shouldListenForFingerprint(Unknown Source:15)
E LSPosed-Bridge: 	at com.android.keyguard.KeyguardUpdateMonitor.updateFingerprintListeningState(KeyguardUpdateMonitor.java:22)
E LSPosed-Bridge: 	at com.android.keyguard.KeyguardUpdateMonitor.updateBiometricListeningState(KeyguardUpdateMonitor.java:0)
E LSPosed-Bridge: 	at com.android.keyguard.KeyguardUpdateMonitor$14.handleMessage(KeyguardUpdateMonitor.java:156)
E LSPosed-Bridge: 	at android.os.Handler.dispatchMessage(Handler.java:106)
E LSPosed-Bridge: 	at android.os.Looper.loopOnce(Looper.java:201)
E LSPosed-Bridge: 	at android.os.Looper.loop(Looper.java:288)
E LSPosed-Bridge: 	at android.app.ActivityThread.main(ActivityThread.java:7872)
E LSPosed-Bridge: 	at java.lang.reflect.Method.invoke(Native Method)
E LSPosed-Bridge: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
E LSPosed-Bridge: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
E KeyguardUpdateMonitorLog: Ignoring startListeningForFingerprint()]

[Archanial]

I have upgraded to 2.6.0, the exact runtime is gone, but a similar stack trace now keeps popping up. Lsposed 1.8.6, Jan sec update.