Hm, a current TWRP should also support fastbootd-mode. If not directly, it should be possible with this command sequence (from PC):Yes lots of people have. I flashed OOS firmware to my phone and am running fine. I'm pretty noob at android stuff, but not at linux. My only advice is that all the people failing seem to be trying to cling to TWRP. I say embrace the LOS recovery that they now bundle. Recognize that fastbootD mode in LOS recovery is not the same thing as booting to fastboot via adb. These are two different modes and only fastbootD mode via LOS recovery gives you the permissions you need to make things work.
No issue hereFirst of all, thanks for the ROM, so far so good. Good battery performance, pretty fluid, Safetynet passed easily with magiskHide + propConf, ...
The only bug I've found is that USB file transfer is not working. I've tried it on 2 windows computers and the device is not recognized as USB mass storage, I've tried on a Linux computer and it's working though. It's not drivers related cause using stock ROM or other custom roms makes file transfer works on windows.
Anyone with this issue?
You can use substratum lite + nonavbar.apk (for ANdroid 11, which hides the navigation bar, floating here around on XDA) + FluidNG from play store to archive this. My wife is using this because she also wanted the OOS styled gestures back. Sometimes FluidNG doesnt work (when you get a call and phone is locked, also some situations i cant remember). but she is pretty satisfied.
Hmmm... I see the FluidNG app. The fact it's no longer mantained doesn't inspire confidence but I could try it, sure (and thanks!).You can use substratum lite + nonavbar.apk (for ANdroid 11, which hides the navigation bar, floating here around on XDA) + FluidNG from play store to archive this. My wife is using this because she also wanted the OOS styled gestures back. Sometimes FluidNG doesnt work (when you get a call and phone is locked, also some situations i cant remember). but she is pretty satisfied.
-> for i just use the new gestures and love them now.
If you need more informations, just ping me here.
Yes, it's EOL, but working in it's state.Yes. I solved it that way. Changed the notification sound to something else and notifications sounds are working now. The previous sound was fine, when selected it played back with no problem. And it used to work. Don't know what messed it up.
Thanks for chiming in, I appreciate it even if I had solved it (and I should have written sooner the solution, as it might help others experiencing the same).
Hmmm... I see the FluidNG app. The fact it's no longer mantained doesn't inspire confidence but I could try it, sure (and thanks!).
I understand the nonavbark.apk thing, in order not to have conflicts with FluidNG (I suppose).
What is substratum lite for, though, in this scenario? I have zero experience with substratum. Zero, nada, zilch.
I already had twrp 3.5.2 installed...
PixelExperience 12 GSI already available. I am using it right now. ArrowOS Unofficial maintainer fixed some bugs and when it will fully stable, I will build PE.Nice you got it working. We also use Swiftkey (forgot to mention ;-) )
Yeah it's sad that it's EOL :-(
Without LOS and derivates most people throw devices away and buy new ones.
I also will use it as long CFW/LOS is supported and security updates are comming.
All the manufactures have dollar/euro signs in there eyes.
The Planned Obsolescence is so wierd these days i can't describe.
But yeah that's another story.
I am so happy that our device is still supported from PE on Android 11.
Does anyone know if our device will support A12/PE?
(Dont get me wrong, not asking for ETA).
Just want to know if @SevralT or another maintainer will bring PE12 for our device.
I think you need to download the latest O+ build. When I first went through this process I used the "...34..._OTA_052...zip" and the issues persisted. It turns out that the website hadn't updated to the latest image file yet. I think I used the recommended O+ app and was able to download the "..34..OTA_0610...zip" (October build) and after I went through the extract/flash process everything worked fine.Thanks for posting this issue. I have noticed this issue as well lately and was wondering how to fix it.
Just to make sure, if I used OnePlus6TOxygen_34_OTA_046 zip file to install originally, i should use Payload-Dumper against it to extract the files, correct?
I have gone ahead and was able to extract the files but wanted to make sure before heading into fastboot to flash the files over.
So it was a multi-step process, but it's actually pretty simple. LOS has a good guide here: https://wiki.lineageos.org/devices/fajita/fw_update
Damn @Eric_Lev the fingerprint sensor is still showing up randomly. If I press it, it doesn't go away.I have to turn the screen on and off. Attached is a photo of the issue in Facebook Messenger and my nightlight option turned off.
Try this fix :Hi all! I've searched the forums but couldn't find an answer to my issue:
Since I got Lineage, the fingerprint sensor randomly pops up unwanted after the phone is unlocked. I have to turn the screen on and off to get it to go away. Is anyone else experiencing this issue or know of a fix?
I'm currently on lineage_fajita-userdebug 11 RQ3A.211001.001 10036875
Thanks in advance!
What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
/data/user_de/0/com.android.phone/filesand edit the carrierconfig file there. It should be something like
carrierconfig-com.android.carrierconfig-89148000001882338238-1839.xml. Note that the first number is the SIM ID, so it will be different for each phone. Change the following line:
<boolean name="rtt_supported_bool" value="true"/>
<boolean name="rtt_supported_bool" value="false"/>