[ROM][11.0][OFFICIAL][instantnoodle] Pixel Experience [AOSP][2020-12-10]

SUPERUSER

Senior Member
Jan 23, 2013
1,574
535
0
did you enter fastboot to make it fastbootd to write system?
Thank you. No, I did not, I learned something new.
I was sitting past midnight trying to read up on what the heck was going on.
Google could have made it a little more simplified to indicate which mode is which and the command to enter and switch between them.

Like "fastboot reboot fastboot" for most people look like a 1x1=1 i.e. rebooting the phone to the same mode you are currently in.
Later I also discovered that you can enter fastbootd via gui; Boot to fastboot>Use volume buttons to scroll to Recovery mode>User power button to select>Advanced>Enter fastboot> and the blue pill above will now say "Fastbootd mode".

Both ways are very discrete and the recovery is too 100% made to trick me the button does a normal reboot to fastboot/bootloader.

https://source.android.com/devices/bootloader/fastbootd


The rom is stable and way more responsive and handle ram better than oxygen rom, its one thing I got very irritated by.
I have 12GB ram but the ram management in stock rom decides to discard apps and redraw them, that's why I modified the ram management.
I got Magisk Canary working, patched the boot.img from the payload and flashed it in fastboot, sadly Fingerprint sensor is disabled after flashing Magisk. It was working when I set up the rom on first boot.
I can probably live with this a while, its the first rom we have and its such an improvement over oxygen os.




Edit: (forgot to mention some additional things)

Gesture navigation
is working perfectly, this is another thing that bugged me on stock rom, enabling gesture navigation and having all animations at 0 is very glitchy swiping up to either go home, or open recent apps.
It just won't register the gesture 90% of times, so I went back with the normal navigation bar.
In this app, its excellent. Nothing to complain about, it registers the gesture right the way even if I do just more my fingers starting the gesture ever so slightly.


OSD layout is exactly as it should be.
I am used to having small size on letters and dpi, currently using "Smallest width" = 528.
Volume button OSD are just the right size, Power menu is about the size I want too.
On Oxygen os these overlays even though I set my font size and dpi low the size never changes on these, they are always the same size which is the most annoying this about stock rom.
Changing volume watching a video puts an overlay that covers almost half of the screen...

And on top of that, the famous input delay when holding down the volume buttons.
Yay, its gone in this rom, its just on stock rom this is present...my god driving me nuts.
https://forum.xda-developers.com/oneplus-7-pro/help/volume-kyes-delay-t3938887

Edit 2:

I successfully passed Safetynet
, basicIntegrity and ctsProfile by following this guide here installing MagiskHide Props Config module.
https://forum.xda-developers.com/apps/magisk/fix-magisk-manager-20-3-ctsprofile-t4080921

Lowest volume step is way to high in some apps, and some not..I am not sure if I am going crazy but it feels like volume is increasing by its own.
In Tiktok volume is so loud I have to mute the speaker in panic late at night and put my finger over the speaker grill.
In youtube its almost like its very quiet.
To explain, Mute = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10.
Volume level 0 is muted and level 1 is the lowest volume you can get.
But volume level 1 is way to loud to be the lowest volume level step.

I tried to deactivate MusicFX apk but did nothing.
Current workaround is to having Viper4Android and changing master power with -10.5db output gain and -3db threshold limit.

I will upload logs later. Perhaps I will try to get a decibel meter reading too so we have some scientific data to correlate with.
Not sure if I'm gonna keep the rom or not, volume is a big issue, cant have a boombox in the middle of the night.
Its an issue on stock rom too but not this bad.
https://forums.oneplus.com/threads/lowest-volume-for-is-still-way-too-loud.1052706/
 
Last edited:

SUPERUSER

Senior Member
Jan 23, 2013
1,574
535
0
Here are some cherry picked line of errors from different logs about biometric/fingerprint errors.
I uploaded an attachment with all logs needed. I will also send logs via the link in op post/header of this thread.
I will now reflash and go back to stock rom.
Code:
[B]dmesg.log[/B]
[B]Line 1162-1163[/B]
[    0.652667] [    0.652666]@4 fingerprint_detect soc:fingerprint_detect: fingerprint_detect_probe: success
[    0.652681] [    0.652681]@4 create_panic_flush_control
[B] Line 3566-3584[/B]
[    5.020314] [    5.020313]@5 dashd: dashd_main enterd
[    5.020318] [    5.020318]@5 dashd: run /system/bin/dashd ENGINE START!
[    5.020371] [    5.020370]@4 init: processing action (boot) from (/vendor/etc/init/hw/init.qcom.rc:116)
[    5.020411] [    5.020410]@5 FASTCHG: dash_dev_write: fw_ver_count=6256
[    5.020453] [    5.020453]@5 dashd: THREAD is created!
[    5.021111] [    5.021109]@7 type=1400 audit(1601536742.399:39): avc: denied { read } for comm="vendor.qti.hard" name="u:object_r:boottime_prop:s0" dev="tmpfs" ino=20837 scontext=u:r:hal_sensorscalibrate_qti_default:s0 tcontext=u:object_r:boottime_prop:s0 tclass=file permissive=0
[    5.021118] [    5.021117]@7 type=1400 audit(1601536742.435:40): avc: denied { read } for comm="dashd" name="cmdline" dev="proc" ino=4026532237 scontext=u:r:dashd:s0 tcontext=u:object_r:proc_cmdline:s0 tclass=file permissive=0
[    5.022722] [    5.022720]@4 init: Received control message 'interface_start' for '[email protected]::IVendorFingerprintExtensions/default' from pid: 593 (/system/bin/hwservicemanager)
[    5.022740] [    5.022739]@4 init: Could not find '[email protected]::IVendorFingerprintExtensions/default' for ctl.interface_start
[    5.023812] [    5.023810]@4 init: Created socket '/dev/socket/lmkd', mode 660, user 1000, group 1000
[    5.025333] [    5.025331]@4 init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory
[    5.025559] [    5.025558]@4 init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory
[    5.025761] [    5.025760]@4 init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory
[    5.030546] [    5.030544]@7 type=1400 audit(1601536742.435:40): avc: denied { read } for comm="dashd" name="cmdline" dev="proc" ino=4026532237 scontext=u:r:dashd:s0 tcontext=u:object_r:proc_cmdline:s0 tclass=file permissive=0
[    5.030554] [    5.030553]@7 type=1400 audit(1601536742.443:41): avc: denied { read } for comm="pm-service" name="u:object_r:boottime_prop:s0" dev="tmpfs" ino=20837 scontext=u:r:vendor_per_mgr:s0 tcontext=u:object_r:boottime_prop:s0 tclass=file permissive=0
[    5.030714] [    5.030713]@5 dashd: THREAD running
[    5.030752] [    5.030751]@5 dashd: dash read
[    5.032095] [    5.032093]@4 init: Received control message 'interface_start' for '[email protected]::IVendorFingerprintExtensions/default' from pid: 593 (/system/bin/hwservicemanager)
[    5.032113] [    5.032112]@4 init: Could not find '[email protected]::IVendorFingerprintExtensions/default' for ctl.interface_start

[B] Event.log[/B]
10-01 09:22:39.115 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.117 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.129 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.132 I/chatty  ( 1369): uid=1000(system) Binder:1369_2 identical 1 line
10-01 09:22:39.142 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.144 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.151 I/am_uid_active( 1369): 10186
10-01 09:22:39.159 I/sysui_multi_action( 1369): [324,1,757,1090,758,12,806,com.android.settings,871,com.android.settings.SubSettings,1091,113]
10-01 09:22:39.160 I/am_on_create_called( 7704): [0,com.android.settings.SubSettings,performCreate]
10-01 09:22:39.170 I/am_on_start_called( 7704): [0,com.android.settings.SubSettings,handleStartActivity]
10-01 09:22:39.170 I/snet_event_log( 7704): [120484087,-1,]
10-01 09:22:39.171 I/am_on_resume_called( 7704): [0,com.android.settings.SubSettings,RESUME_ACTIVITY]
10-01 09:22:39.176 I/sysui_multi_action( 7704): [757,87,758,1,833,35]
10-01 09:22:39.180 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.189 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.193 I/sysui_multi_action( 1369): [757,803,799,fingerprintd_openhal_error,802,1]
10-01 09:22:39.197 I/am_on_top_resumed_gained_called( 7704): [0,com.android.settings.SubSettings

[B] logcat.log[/B]
[B] Line 115-119[/B]
10-01 09:19:06.606 I/SystemServiceManager( 1369): Starting com.android.server.biometrics.BiometricService
10-01 09:19:06.606 V/FingerprintService( 1369): mDaemon was null, reconnect to fingerprint
10-01 09:19:06.606 I/SystemServer( 1369): StartBackgroundDexOptService
10-01 09:19:06.607 V/FingerprintService( 1369): Fingerprint HAL id: 0
10-01 09:19:06.607 W/FingerprintService( 1369): Failed to open Fingerprint HAL!
[B] 2458-2459[/B]
10-01 09:19:15.950 I/ActivityManager( 1369): Start proc 6346:com.qualcomm.qti.biometrics.fingerprint.service/u0a168 for broadcast {com.qualcomm.qti.biometrics.fingerprint.service/com.qualcomm.qti.biometrics.fingerprint.service.ShutdownReceiver}
10-01 09:19:15.955 D/ConnectivityService( 1369): Returning BLOCKED NetworkInfo to uid=10195
[B] 2495-2501[/B]
10-01 09:19:16.962 V/FingerprintService( 1369): mDaemon was null, reconnect to fingerprint
10-01 09:19:16.966 V/FingerprintService( 1369): Fingerprint HAL id: 0
10-01 09:19:16.966 W/FingerprintService( 1369): Failed to open Fingerprint HAL!
10-01 09:19:16.967 D/BiometricService( 1369): checkAndGetBiometricModality: user=0 isHardwareDetected=true hasTemplatesEnrolled=false enabledForApps=false
10-01 09:19:16.968 V/FingerprintService( 1369): mDaemon was null, reconnect to fingerprint
10-01 09:19:16.972 V/FingerprintService( 1369): Fingerprint HAL id: 0
10-01 09:19:16.972 W/FingerprintService( 1369): Failed to open Fingerprint HAL!
[B] 3338[/B]
 10-01 09:19:21.096 W/JHwRemoteBinder( 1369): BinderProxy is being destroyed but the application did not call unlinkToDeath to unlink all of its death recipients beforehand.  Releasing leaked death recipient: com.android.server.biometrics.fingerprint.FingerprintService
There is also a bunch of selinux errors regarding audio, aptx, bluetooth and more.
 

Lucejester

Member
Nov 15, 2013
13
5
0
Any recent feedback on thoughts on battery life? I'm sure the general smoothness/speed of the rom is good, and I've always enjoyed AOSP/Pixel roms in the past, was thinking of swapping over from Oxygen this weekend just to see if a few small nags I have with the phone may go away. (No major complaints with Oxygen, but it just doesn't really blow me away either.) Thank you guys!
 

shaneg79

Senior Member
Sep 10, 2009
541
93
48
Any recent feedback on thoughts on battery life? I'm sure the general smoothness/speed of the rom is good, and I've always enjoyed AOSP/Pixel roms in the past, was thinking of swapping over from Oxygen this weekend just to see if a few small nags I have with the phone may go away. (No major complaints with Oxygen, but it just doesn't really blow me away either.) Thank you guys!
Battery life is great for me on the T-Mobile OnePlus 8