search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.32k stars 654 forks source link

Poco M3 GSI 11 feedback #1765

Open KaMyKaSii opened 3 years ago

KaMyKaSii commented 3 years ago

AOSP 11.0 v302 - system-roar-arm64-ab-gapps - VNDK 29 Before each logcat I executed the command "logcat -c" so that the result is as dry as possible. I also leave a boot log to check for possible problems. liveboot.log

  1. Fingerprint causing gestures on the interface

As if it were the result of pressing TAB/enter on a keyboard. Using the keylayout file of this thread fixes the problem. Attached is the result of "getevent" anyway. getevent.txt

  1. Activating the "Securize" option causes the device to be stuck in the boot logo (not bootanimation)

I think it's because the option requires /system read-write while the filesystem doesn't allow it and ends up leading to corruption. I'm using my own Magisk module to disable the native root.

  1. The scroll is considerably slow, dragged

Turning on "Disable HW overlays" seems to improve a bit, but maybe it's placebo. Attached is a logcat while scrolling, do not know if it helps in something. scrolling.txt

  1. The system does not go into deepsleep

After leaving the device locked for about 7 hours (in airplane mode), the device loses about 3-4% (6Ah battery) and Franco Kernel Manager and Naptime report zero deep sleep time. Attached is a logcat with Naptime active (deep sleep starts faster) and the device locked for 20 minutes. locked.txt

  1. Random audio crackling

In a few moments (i don't know what the trigger is) WhatsApp audios start popping a lot. Attached is a logcat with this happening. And not exactly connected to the same problem, but with the volume close to the maximum I realize that the ear speaker begins to burst, I believe that GSI is forcing it higher than in the stock ROM (in the Poco M3 the three speakers work together all the time). cracklingaudio.txt

  1. Screen recording leaves the device and the interface extremely slow

As if the device did not have hardware encoding, although the codec is h264 screenrecording.txt

Thank you for your time and great work!

phhusson commented 3 years ago

  1. Add your device to https://github.com/phhusson/device_phh_treble/blob/android-11.0/rw-system.sh#L139

  2. If system wasn't mountable r/w, "securize" wouldn't have any effect, so you wouldn't be stuck. The most likely issue is that your vendor has an older SPL (Security Patch Level) than system, so doing "securize" does a rollback of SPL, which makes data inaccessible and can be fixed only with factory data reset (or un-rollbacking SPL). That's a global issue of Securize that I need to work on. You can edit rw-system.sh and remove the part where it sets security patch level, but then you won't pass SafetyNet.

  3. Open a different ticket and generate a trace while scrolling with systrace.py (I use the one from https://android.googlesource.com/platform/external/chromium-trace/, the one in Android SDK no longer works in modern browsers)

  4. Try a night with vanilla or floss variant, without installing any app, starting at somewhere between 20% and 80% (going from 100% to 96% overnight is to be expected, even with the battery physically disconnected from the smartphone)

  5. Open two different tickets. Start by disabling audio efects in treble settings.

Le ven. 19 mars 2021 à 00:26, KaMyKaSii @.***> a écrit :

AOSP 11.0 v302 - system-roar-arm64-ab-gapps Before each logcat I executed the command "logcat -c" so that the result is as dry as possible. I also leave a boot log to check for possible problems.

  1. Fingerprint causing gestures on the interface

As if it were the result of pressing TAB/enter on a keyboard. Using the keylayout file of this thread https://forum.xda-developers.com/t/disabling-fingerprint-gestures.3875779/post-78712491 fixes the problem. Attached is the result of "getevent" anyway. getevent.txt https://github.com/phhusson/treble_experimentations/files/6167688/getevent.txt

  1. Activating the "Securize" option causes the device to be stuck in the logo

I think it's because the option requires /system read-write while the filesystem doesn't allow it and ends up leading to corruption. I'm using my own Magisk module to disable the native root.

  1. The scroll is considerably slow, dragged

Turning on "Disable HW overlays" seems to improve a bit, but maybe it's placebo. Attached is a logcat while scrolling, do not know if it helps in something. scrolling.txt https://github.com/phhusson/treble_experimentations/files/6167690/scrolling.txt

  1. The system does not go into deepsleep

After leaving the device locked for about 7 hours (in airplane mode), the device loses about 3-4% (6Ah battery) and Franco Kernel Manager and Naptime report zero deep sleep time. Attached is a logcat with Naptime active (deep sleep starts faster) and the device locked for 20 minutes. locked.txt https://github.com/phhusson/treble_experimentations/files/6167692/locked.txt

  1. Random audio crackling

In a few moments (i don't know what the trigger is) WhatsApp audios start popping a lot. Attached is a logcat with this happening. And not exactly connected to the same problem, but with the volume close to the maximum I realize that the ear speaker begins to burst, I believe that GSI is forcing it higher than in the stock ROM (in the Poco M3 the three speakers work together all the time). cracklingaudio.txt https://github.com/phhusson/treble_experimentations/files/6167696/cracklingaudio.txt

Thank you for your time and great work!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1765, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OWHJHQ3SQSTVVEE6TDTEKD33ANCNFSM4ZNVAGYA .

KaMyKaSii commented 3 years ago
  1. Try a night with vanilla or floss variant, without installing any app, starting at somewhere between 20% and 80% (going from 100% to 96% overnight is to be expected, even with the battery physically disconnected from the smartphone)

At the moment I am using the GSI in my daily use, I know it is not recommended but could not stand the RAM management of stock MIUI. This is my first device that uses FBE encryption and still don't quite understand how can I wipe data without formatting (and lose /data/media) or is this impossible now? I tried to make a TWRP "wipe data" before leaving the stock ROM for GSI and it turned out to be in bootloop, TWRP could no longer decrypt my internal storage and I had to format. Is installing the vanilla variant using DSU also valid or do I really need to install as the main system?

  1. Open two different tickets. Start by disabling audio efects in treble settings.

I will test with the audio effects disabled and then open the new tickets if necessary