yashsingh1/xdaforums huggingface dataset:
[OnePlus 9] Guidosaur:
Yeah now that you mention it my double tap to wake isn't working anymore. I just did an update with the built in LOS updater. Double tap to sleep still works on the lock screen and the status bar though. Thankfully I haven't had to force close apps 15 times today though lol
[OnePlus 9] hankster112:
Would also like to know the answer to this.
[OnePlus 9] imbasador:
yes, double tap is not working.

and game experience get worse then in past.
[OnePlus 9] mattie_49:
Long press on Fp sensor to unlock phone is perfectly fine for me until issue with double tap is resolved. Nice build so far. I've even tried tripping the tap to wake switch to on with gravity box & lsposed. It was already on . :(

And the battery drain from before with binder issues is resolved. Everything smooth like silk. I like
[OnePlus 9] Eric_Lev:
FYI ... Single tap to wake :

Settings > System > Gestures > Touchscreen gestures > Single tap ... and enable Show ambiant display
[OnePlus 9] mattie_49:
Very nice
[OnePlus 9] shadabkiani:
On the downloads page, I see super_empty.img. What does it do? Wipe the super partition and delete all logical partitions inside?
[OnePlus 9] mattie_49:
Dunno. But don't anyone try to flash bluspark onto 3/5 build. Must be a13 actual framework because it tried bootlooping then booted with zero touch response on screen. Dirty flash got it back. He's rebasing kernel currently. !! Righteous. Love op9 again

Anyone got a g-cam they can't live without on this device they could share. ?
[OnePlus 9] mattie_49:
And btw aosp mods lsposed was updated 8 hrs ago. Shows volte In status bar and switched to 4g versus LTE. And to answer earlier question yes Volte is here. Only way Verizon connect to data. Volte in status bar.
[OnePlus 9] hibert:
Same here, no Touch after flashing blue Spark Kernel over the latest build from 03/05
[OnePlus 9] dimoochka:
Bug Report (Trebuchet Search Tapping Partially Unresponsive With a Work Profile Setup)

Model: LE2115 (NA)

What is your--

LineageOS Version: 20.0-20230305-NIGHTLY-lemonade

LineageOS Download URL: https://mirrorbits.lineageos.org/fu...age-20.0-20230305-nightly-lemonade-signed.zip

Gapps version: MindTheGapps-13.0.0-arm64-20221025_100653

Did you--

wipe: yes

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

other modifications: Magisk, ih8sn

Bug info: This is a minor issue that's been present since I initially installed Lineage 1-2 months ago. I believe that this is a UI bug that pertains to Trebuchet's search behavior when a work profile is set up. Easy to reproduce; when searching for an app in Trebuchet, touching an app icon will fail to launch it. Additionally, the Personal | Work profile buttons are hidden while searching, but touching in the area where those buttons would be results in activation of those buttons' behavior. In other words, the UI visually hides the buttons but behaves as if they're still there.

Screen capture video of the issue attached (watch it through to the end - I demonstrated the weird Work Profile button behavior). Please let me know if you'd like a logcat capture as well!
[OnePlus 9] mattie_49:
Working on my end.
[OnePlus 9] dimoochka:
I should probably change the title; not totally unresponsive - check out the screen grab vid that I took.
[OnePlus 9] Eric_Lev:
About GCam, I use this one :

Hasli: LMC8.4_R15

Download LMC8.4_R15 by Hasli.

www.celsoazevedo.com

or

https://sourceforge.net/projects/eric-lev/files/GCam/OP9/

Or one of my previous post

https://xdaforums.com/t/rom-official-lemonade-13-lineageos-20.4536697/post-88022355
[OnePlus 9] RobertDMR:
I have a few different OnePlus phones running Lineage, so I may be misremembering, but didn't the original 20 instructions for OP9 say to be on Android 12 firmware? If so, then I'm guessing it's not okay for me to go from the old build to the new re-released version because it says to be on Android 13 firmware now?
[OnePlus 9] mattie_49:
Do you think that androidfreak knows about the Dt2w being broken on lemonade 3/5 build? I tried switching on through lsposed to no luck. ?
[OnePlus 9] dimoochka:
I know that this isn't exactly reassuring, but 1-2 months ago, before I installed LOS20, I fully upgraded OxygenOS. My guess is I'm running A13 firmware. Happy to check my device if given proper instructions.

I also remember reading on this forum that someone mentioned proper firmware is included with LOS20; don't quote me on that. My memory is totally unreliable.
[OnePlus 9] Eric_Lev:
Fw is embedded so no sweat ...
[OnePlus 9] Eric_Lev:
Dt2w works on 9 pro and fails on 9 ... Be patient and wait for a fix.
[OnePlus 9] shadabkiani:
Can you please tell me how I can load config? I tried but I can't. Screenshot below. When I click on 'Import ready-made configs', it just loads the default. There is no option where I can load the config 'Arcide-LMC8.4-OP9P-v7.1.xml' that you shared on sourceforge.
[OnePlus 9] Eric_Lev:
How to Load & Save XML Configs in Google Camera Ports

How to import and export settings/configs on Google Camera versions that support this feature.

www.celsoazevedo.com
[OnePlus 9] shadabkiani:
Thanks. Actually I read that before too, but now I realized that I missed the part "Double click the dark area around the shutter button." That allowed me to load the desired config.
[OnePlus 9] mattie_49:
3/05 lemonade build with latest blu_spark is damn near perfect. Flashed late last night again. I'll wait for to Dt2w to be fixed.Literally zero issues other than tap to wake not working.
[OnePlus 9] mattie_49:
Had to return to stock for small trip. Can anyone confirm if Dt2w is fixed in 3/12 build.?
[OnePlus 9] Eric_Lev:
Double-Tap to wake (Dt2w) is not fixed in 3/12 build.

My setup : LE2115 - Clean flash to install LOS 20 - latest build - MindTheGapps - ih8sn

Edit (13/03) : https://gitlab.com/LineageOS/issues/android/-/issues/5648
[OnePlus 9] mattie_49:
Ty for quick reply my friend.
[OnePlus 9] Josh McGrath:
Upgrading from 19.1 to 20 the DTW, double tap to wake, works for me if it helps diagnose the issue.
[OnePlus 9] Eric_Lev:
FYI: https://gitlab.com/LineageOS/issues/android/-/issues/5648
[OnePlus 9] mattie_49:
Is this an official bug report to lineage? Because I really don't think Androifrk looks at thread. Or he started thread unofficial way back when and it went official. Not sure . Really wanna daily drive this though. Thought maybe would be fixed in 3/12 . I also though it was kernel side issue ,flashing latest blu_spark does not fix issue . Just really used to feature from running stock.
[OnePlus 9] TimmyP:
The Tmobile US 2117 model of the OP9 is not listed in official compatibility. Does anyone know if there are any issues?
[OnePlus 9] Guidosaur:
My OP7Pro wasn't listed on the LineageOS compatibility list either but I got it to work. I used some program to flash it to a non-tmobile version of the phone and then did the LOS install. There's probably a process like that you can do. It's kinda at your own risk though
[OnePlus 9] TimmyP:
^Thanks. Im already converted and rooted on A11 OOS11 trying to decide if I should stay here for awhile.
[OnePlus 9] Guidosaur:
Well I think per the LOS instructions you need a12 firmware. I updated all the way to a13 and then did the LOS install and it worked fine.
[OnePlus 9] BeardedGears:
Are things fixed to run this as a daily driver
[OnePlus 9] Guidosaur:
What are your prerequisites for that to be the case?
[OnePlus 9] hibert:
I updated to the latest build yesterday. now the google play services are crashing. I keep getting random fc messages. also the google settings in the settings app no longer works. it closes without an error message. Wondering if I'm alone with this or I've ****ed something. I only use the bluspark kernel and magisk, nothing more.
[OnePlus 9] dimoochka:
A few of us have been using the latest build without any major issues like this (with Magisk). Maybe related to bluspark? I'm fine but don't have that installed.
[OnePlus 9] hibert:
I had no problems with last week's build. with the same bluespark version. so I don't think it's a kernel related problem. but i am not a developer :P From experience with custom roms, i assume that somehow a play service update is to blame for the misery. it's hard to say now. I will try now a dirty gaaps flash. but I think I have to reinstall, too bad.
[OnePlus 9] dimoochka:
You can try clearing the data for Google Play Services, but yeah you might have to just clean flash. I had a similar problem during my initial LineageOS install a few months ago but I think I made a mistake while flashing (like installing to slot A/booting, then flashing again to slot B and switching to it but forgetting to flash gapps). Anyway, haven't touched it since I got it working. My update process is using the OTA lineage updater and installing Magisk to the inactive OTA slot prior to reboot - and that's worked perfectly.
[OnePlus 9] andr01dfr3ak:
I am aware of this issue and am looking into it. I've just been busy with other things.

For now, just use single tap, since the kernel currently reports double tap as two single taps instead.
[OnePlus 9] shadabkiani:
This thread is more active so I'm asking here. I sideloaded crDroid, and then reboot recovery, then sideloaded NikGapps basic version, and then some addons (8 to be precise). But when flashing Google Search add-on (which is around 150MB), it gave error like no more space. Anyway, the phone booted and I checked from Root Explorer that /system, /system_ext, /product, they have less than 30MBs left. Is there any way I can resize/expand /system or /product within /super partition?
[OnePlus 9] mattie_49:
Can anyone confirm or deny if today's build has d2tw working properly?
[OnePlus 9] dimoochka:
Sad to report that the bug persists in today's build.
[OnePlus 9] BeardedGears:
Double tap to wake ?
[OnePlus 9] mattie_49:
Yes sir
[OnePlus 9] andr01dfr3ak:
Once dt2w is fixed, I will let you know.
[OnePlus 9] mattie_49:
Much appreciated. !
[OnePlus 9] mattie_49:
I see the fix coming next build sir. Very cool. Gonna flash and get everything set-up
[OnePlus 9] mattie_49:
Really enjoying lineage since setting up last night. Blu_spark kernel pairs nicely with build. And you know I like android keyboard hands down compared to g-board. So much easier to type it seems.
[OnePlus 9] mattie_49:
After messing around using pixelify and changing launchers recents. I found that like I thought trebuchet wasn't allowed notification access. I granted it permissions and dt2w works perfectly. Not a bug. By default this setting is wrong. What I'm really asking are these merges coming gonna break things intended to fix. Because Dt2w works fine after allowing notification access to trebuchet. ?? R139 blu_spark might of fixed also. But it is indeed working properly. @andr01dfr3ak
[OnePlus 9] mattie_49:
This is fix,device and app notifications.
[OnePlus 9] dimoochka:
Tried it, didn't work for me. Trebuchet already had access. I run stock kernel.
[OnePlus 9] mattie_49:
This must be why. R139 fixes somehow. He just posted this am new. Flashed and its working properly.
[OnePlus 9] Arakmar:
For those who can't wait next sunday build (it drived me crazy), I built the kernel with the DT2W fix :

boot_lemonade_20230323_dt2w_fixed.img

drive.google.com

Thanks a lot for @LuK1337 and everyone involved with this fix !
[OnePlus 9] Guidosaur:
Can someone please tell me what setting I need to change or what app/service I have to install to keep the brightness from changing by itself? I've turned off auto brightness, and used one-shot auto brightness, and the phone will still dim itself randomly. Super noticable when I was using the phone as my gps on a road trip last week. I just have a lineage install with mindthegapps (linked from the wiki) flashed and that's it. Is it just Digital Well-being I need to install or am I missing a setting?
[OnePlus 9] mattie_49:
I noticed this as well. Especially outdoors. And my auto brightness was off.
[OnePlus 9] Guidosaur:
It's way more annoying to me than double tap to wake not working lol. LineageOS on my OP7pro with the same kind of install did the same thing
[OnePlus 9] mattie_49:
That change to fix dt2w was merged. Is dt2w fixed in today's build?. And maybe it's mindthegapps. That's what I used also. Someone that knows more will have to chime in.
[OnePlus 9] mattie_49:
I went back to stock to see what F-21 was about. I jump around. But the screen dimming randomly is hard to get used to.
[OnePlus 9] shadabkiani:
Try this: Developer Options > Force Peak Refresh Rate (Enable). Let us know if it fixes your issue.
[OnePlus 9] dimoochka:
Fixed!
[OnePlus 9] Guidosaur:
Tried it but no dice. Still brightness all over the place when I'm in direct sunlight. Looking around Reddit it looks like it lots of OnePlus (maybe other manufacturers too) have this issue on LOS. It looks like it's either a bug with High Brightness Mode (Live Display), or Device Health Services from Google being absent.
[OnePlus 9] TimmyP:
This fixed the color flickering. Wtf is that? Sorry new to this ROM.

PS its very mild bit almost like is changing color temperature setting instantly.
[OnePlus 9] mattie_49:
Digital wellbeing nikgapps addon. Sideload through recovery.
[OnePlus 9] TimmyP:
Is there an partition backup method? Lineage Recovery doesn't have backup, and twrp doesn't seem to want to fastboot (gets stuck on fastboot logo).
[OnePlus 9] mattie_49:
Partitions Backup & Restore - Apps on Google Play

Backup your important partitions to avoid any data or IMEI corruption

play.google.com

Works perfectly. Dumps to sd card. Go into settings prior and use raw image.
[OnePlus 9] TimmyP:
Thank you! You have been a massive help!
[OnePlus 9] shadabkiani:
In LineageOS (and other ROMs based on it) the default setting is that if there is no motion on screen for a few seconds, the refresh rate changes from 120Hz to 60Hz, hence there is a flicker momentarily every time it does that. By enabling Force Peak Refresh Rate, it is locked at 120Hz.
[OnePlus 9] TimmyP:
I see thank you. Im gonna guess, since I was at a webpage not moving when I saw it, that it can be triggered on and off by simple moving graphics.

Flashing Device Health also fixed it, and you dont need that setting enabled.
[OnePlus 9] mattie_49:
Locked at 120hz will eat the batt alive. I do believe on stock it fluctuates automatically also.
[OnePlus 9] Guidosaur:
Alright, I figured out the random brightness changes everyone lol. Installed Device Health Services from the play store and it didn't work. It turns out if you go to Display>Live Display either turn the setting to off or outdoors. The automatic setting is selected by default, and can put the brightness into overdrive if the sensor detects a bunch of sunlight. It doesn't work well on the auto setting at all though. Just pick off or on (outdoors) and it'll be set.
[OnePlus 9] TimmyP:
Xposed edge top brightness slider solves all brightness issues imo (but that last one lol). Phones never have good AB. Even tweaked AB sensor values they have always sucked.
[OnePlus 9] Guidosaur:
That's crazy Xposed still exists lol. I remember messing with that one my HTC M8 😭. But this brightness issue was that even with AB off completely, it would still keep changing the brightness.
[OnePlus 9] javi2246:
No one has had any problems with the latest update (03/26)? It downloads, installs and stays in bootloop until it reboots 3 or 4 times and boots to the previous version. I have tried two or three times without success.
[OnePlus 9] TimmyP:
Its usually Lsposed now, but the module is called xposed edge and I cant live without it. It gives you full button control, even shortcuts for volume buttons when phone is off. Power for torch, double up for tv volume, double down for smart device control.
[OnePlus 9] Guidosaur:
That's awesome. I've been wanting to change my volume down from rewind to play/pause but I haven't been able to find a way to do so
[OnePlus 9] TimmyP:
Its definitely your answer. Its really well developed, stable and maintained. I wouldn't recommend straight up xposed modules usually, but this one is really nice and all I use. There is a lot to it too, like per app disable control, gestures, schedules...

For what I stated above though, you (or at least I) needed tasker, as you need it to turn on the display, then open whatever app... Then you make the shortcut to the task.

There is also back up settings, which you will want to do after you find out that setting up app state is no joke, and you can set it up for both focus and opened states to turn off\restore key control. Its a pain, but it does not fail. (like for emulators, you can relenquish control to system and back for volume or to program a volume button in the emulator).

PS: Check out the top edge\status bar slider for brightness (or whatever). It destroys what gravitybox had on 11 with "status bar brightness slider." So much better!
[OnePlus 9] shadabkiani:
I haven't tested on stock. But on LineageOS, I haven't noticed any high battery drain. It's the same as that setting disabled. Also, it doesn't stay at 60Hz for long. As soon as you tap the screen, or if there is even as slightest a motion as network speed activity, it will shoot back upto 120Hz. This would only help if you do reading on your phone for long periods without touching screen. You can test this by also enabling Show Refresh Rate setting in Developers Options. Also, enabling Force Peak Refresh Rate doesn't mean the display is locked at 120Hz permanently. Some apps and games I play don't support 120Hz, so as soon as I open them, display locks at 60Hz despite the peak refresh rate setting.
[OnePlus 9] dimoochka:
I had a boot loop issue after upgrading. It was related to an incompatible Magisk module that I had to update. Try to boot into safe mode.
[OnePlus 9] TimmyP:
Thats what was causing it for me. The network counter. Was not doing it on stock rom. I could be sitting in a menu not moving, and it would slightly flicker to *slightly new colors.
[OnePlus 9] javi2246:
Well, it was indeed that, thank you very much because it would have cost me to find it.
[OnePlus 9] mattie_49:
Enjoying the nightly builds for sure sturdy

And stable . Has anyone found a 3rd party launcher that works without breaking recents or home button? Lawnchair still stuck on alpha 4 they have had for months.
[OnePlus 9] mattie_49:
Always disable modules before you update.
[OnePlus 9] TimmyP:
The home button seems to work in Nova, but there is no timing to it. I noticed this as soon as I upgrade from A11.

You can use Xposed edge pro to set a bottom center edge press that makes it work like it did in A11. Just give it a shot, its actually slightly better imo. Much easier to use.

*and i swear im not trying to simp or anything for this module. I will state, however, that it seems to be far beyond any other module Ive ever used in every aspect. Its almost unbelievable that it works so well.
[OnePlus 9] mattie_49:
I've tried many today. Just gonna use lawnchair latest dev build. Recents won't change through quick switch yet. But everything works. I love my device again. I'll post some battery stats soon. Using blu_spark kernel.
[OnePlus 9] TimmyP:
Nice! I might give that kernel a shot soon. I love this device too. Just remember if you ever want to try a new launcher, try that module. I actually just tried this because your comment made me wonder if home is working right, since it was kinda strange behaving.
[OnePlus 9] mattie_49:
Which module?
[OnePlus 9] TimmyP:
Xposed edge - Apps on Google Play

This module provides you Gesture control and Key control.

play.google.com

They have a pro one too for 1.99. I just got it right away so Im not sure what it adds.

PS: Works fine with riru and lsposed in case.
[OnePlus 9] mizarddo:
Is it alright to flash the twrp on this using magisk instead of fastboot?

It sounds like less headache but I've had twrp trust issues on this phone
[OnePlus 9] shadabkiani:
TWRP isn't recommended/needed for this phone. If you still feel the need to use TWRP for whatever reason, it's recommened to temporarily boot it by fastboot boot your_TWRP.img instead of having it permenently flashed.
[OnePlus 9] Not-Aus:
New Magisk is there:

Klick
[OnePlus 9] BeardedGears:
Finally did update to 20.

On startup on 1+ screen in orange letters it says orange state, device is unlocked and cannot be trusted... Haven't seen this before
[OnePlus 9] sodnwsdho:
Because of upgrading to OnePlus9's Android 13 firmware
[OnePlus 9] shadabkiani:
That's not true. It's because of unlocked bootloader, and I beleive F.17 and before did not have the Orange State warning, and they were on A13. It's the newer abl.img that shows that warning. You can flash previous build's abl.img (20230212) and the Orange State will be gone. I have attached that in this message. You have to flash from fastbootd mode:

fastboot flash abl abl.img
[OnePlus 9] mattie_49:
This is stock A13 OnePlus warning that bl is unlocked and device isn't safe. I get orange banner on op9 global na after unlock on A13
[OnePlus 9] TimmyP:
Does it get rid of the 5 second pause at boot?
[OnePlus 9] shadabkiani:
I think so, but I haven't compared times. Even if it doesn't, you would get rid of that stupid message at least.
[OnePlus 9] mattie_49:
Flashing older abl.img partition on newer firmware won't render msm tool useless will it? Param preload errors. Super partition error ,sha 256 does not match error. Just curious as I do hate annoying orange banner. But flash builds weekly and wanna be able to get back 😞

And what about Google internal ota. That does a partition checksum prior to installation of new build. Will it effect being able to update without returning to new abl.img?
[OnePlus 9] shadabkiani:
I am currently on crDroid 9.2 and it had the Orage State warning too, so I used the same abl.img that I shared above (that is from LOS older build). I have not faced such errors.

What do you mean by Google OTA? You mean OTA on OxygenOS? I haven't used this abl.img on OOS though.
[OnePlus 9] mattie_49:
Yes Google Ota is what delivers our builds internally after OnePlus releases. So yes on Oos. Have you tried to msm back after using said able.img . From say cr-droid back to stock?
[OnePlus 9] shadabkiani:
I just used MSM tool right now to extract boot.img as a test, and it successfully did that.

By MSM back, you mean reverting all the way back to OOS11 as we do in unbricking? No I haven't done that after this abl.img workaround, but it wouldn't matter. MSM firmware includes abl.img that came with that specific firmware version, and it would flash that. We don't need to worry about that.
[OnePlus 9] mattie_49:
Makes sense. I just know on the carrier branded Verizon op8 I had to modify many partitions just to unlock bl. Made device unstable and bricked very easy. In the end. Msm would start as normal. After downloading super partition it would just start dl'ing super partition again, only this time with a sha _256 does not match error. This was the end of that device.
[OnePlus 9] shadabkiani:
Hmmm... Well, on OnePlus 9, I did a long range of experiments when I got this device a couple of months ago to understand it's partitioning and backing up/restoring. Long story short, it has about 128 partitions, and there are only a handful of partitions (25 to be exact) that are very critical and probably device specific (like modesmst1 modemst2 param and others), because they are not updated/flashed when applying OTA/MSM. Apart from that, other partitions do get updated/flashed with OTAs, and abl.img is one of them. So you can just go ahead and mess with it all you want. When you revert through MSM, it would flash abl.img that came with that particular version of OOS11. In every LOS build, the payload.bin contains abl.img too. On newer builds, the abl.img contained that Orange State warning (just like recent OOS13 builds). The last build without that warning was 20230212, and it's abl.img I shared above, and I myself have been using on crDroid too. (Maybe the latest LOS build's abl.img got rid of it again, I don't know, I left LOS)
[OnePlus 9] thethirdmurph:
anybody have problems with tts? I can't use gps