yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mike.sanders:
Hi Eric,

yes, I know about OpenGapps not yet being available for Android 11. But there's a discussion over at Github indicating that it might be ready quite soon now, so that's why I explicitly said in my first post I'd wait for it.

And I didn't intend to criticize you - I had hoped I'd done my research properly and figured it all out correctly (that's why I painstakingly described things in so much detail) so that someone in the know could get away answering with no more than a simple "yes".

So when instead you described another approach I wondered if and what I might have overlooked and simply tried to verify my understanding of the differences of what I had described and what you came back with in your response...

- Mike
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No sweat.

For upgrading to LOS 18: if you’re currently on an official build, you DO NOT need to wipe your device ... Just wipe system (and cache - recommended) then flash LOS 18 & gapps ... via TWRP or LOS recovery (adb).

Note that Magisk can sometimes be a problem.

Eric
[OnePlus 3 & 3T Cross Device Development] $anket:
Hey guys, Sorry if this is wrong thread but I need help.

I upgraded from official los 17.1 to 18.1 using official wiki guides but i was having some issue after upgrading (I am not using GAPPS). So I decided to clean flash los 18.1. My BL was locked and with LOS recovery.

But before clean flashing I made a stupid mistake. One app was not working without gapps, so i decided to check whether it will work with microg or not. So I wiped cache/system and flashed this rom. During installation there was a confirmation of "Signature Verification failed, proceed to Install: Yes/No". I clicked Yes. When I rebooted System it did prompt me for a secure boot password. But after that booting did not complete and threw me back in recovery telling me to Factory reset.

Then I wiped system/cache and tried adb sideload LOS 18.1 but it falied at 28%. So I performed a factory reset and tried again. But still it did not install.

And now there is an error displayed in los recovery: "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory"

I also tried adb sideload stock oos los recovery but it did not work as well.

tl/dr, I soft bricked my device. BL is locked, LOS recovery with failed to bind mount error.

So what should I do? Any help will be appreciated.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
All this with a locked BL ... !

You could try this:

- Power off your device

- Boot to LOS recovery

- Factory reset > Format data/factory reset.

- Boot to recovery

- Factory reset > Format system and cache partitions

- Apply update > Apply from adb

- Sideload LOS 18.1 then MindTheGapp

- Reboot system now

If unsuccessful ... unlock your BL, flash via fastboot TWRP recovery ... Format Data (not wipe) then perform a clean flash of LOS 18.

Good luck
[OnePlus 3 & 3T Cross Device Development] $anket:
I did format data/system/cache multiple times in los recovery but still not able to side load anything. I think when I formatted data in recovery, it messed up my data partition. This error "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory" appeared only when I formatted data initially. There was no such error before performing format data.

And also I was on latest los 18.1 recovery. But now it says 17.1-20210307. How it got downgraded, I dont know.

Unlocking BL is out of scope since OEM unlock was disabled and since I've got no os to boot into, can't enable it.

Edit: found this reddit post about los recovery having the same issue as mine
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Wow !

Did you try via fastboot ?

fastboot erase userdata
[OnePlus 3 & 3T Cross Device Development] $anket:
Yeah I tried that. But since BL is locked, it throws "format failed" error. I guess my only option is to try unbrick tool.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
As expected ...

I never tried with a locked BL but via adb root (if USB debugging and Rooted debugging were enabled in dev options) ... ?

https://xdaforums.com/t/rom-official-nightly-lineageos-17-1-for-oneplus-3-3t.3990061/post-82169973

However I guess your only option is to try unbrick tool.
[OnePlus 3 & 3T Cross Device Development] $anket:
Sadly I enabled USB debugging only. I think it won't matter now as I have no os installed.

Yeah i hope it works.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Maybe your adblock lists are blocking amazon?
[OnePlus 3 & 3T Cross Device Development] $anket:
My conclusion is, formatting system + format data/factory reset in LOS Recovery makes the device unbootable. Even adb sideload won't work. I might be wrong.

Similar issue is discussed here.

Can anyone with a spare device confirm this? (Only do this if u have Unlocked BL)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Of course the phone can't boot if you wipe the system partition!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About your adb issue:

- Did you enable ADB in Advanced options of LOS recovery before applying from ADB ?

- Did you check your USB cable ?

- Does adb devices find your device ?
[OnePlus 3 & 3T Cross Device Development] $anket:
Yes I know. But it should allow me adb sideload a rom. But it didn't. During adb sideload, it get stucks around 12% and throws me that bind error. And everytime I boot into recovery, this bind error is displayed permanently at the bottom of the screen.
[OnePlus 3 & 3T Cross Device Development] $anket:
Yeah device was getting detected in adb as well as fastboot.

By the way I solved the issue using Unbrick tool.
[OnePlus 3 & 3T Cross Device Development] johngare:
Anyone experiencing an issue when your screen turns off snd then upon turning it back on either by fingerprint or powerbutton, the screen just keeps on flickering and won't open unless you restart it which is pretty annoying.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there! Happy to see the OP3 getting LOS 18.1!

Just a few questions before I update from 17.1:

- how is the GPS working? On 16.1 it worked very well, fast and accurate but on 17.1, not so good on my device, even after the GPS patch from months ago (I am not using GApps)

- is it possible to choose the 4G network manually and not only automatically? This option works on LOS 17.1 for the OP3 but I know it doesn't work on the OP2 and OP5 on LOS 17.1 (you can not select manually the network, it's automatic only)

Thanks a lot for your answers!
[OnePlus 3 & 3T Cross Device Development] snyperius:
With a little gps.conf file tweaking, the GPS on my OP3T is at least as good as it is with OOS (sub-half a minute GPS position fix indoors.) I've written down what I did in a comment above somewhere, read back or search for it.
[OnePlus 3 & 3T Cross Device Development] defi231:
that reminds me of the beginning of LOS 16 there where similar problems with magisk topjohnwu and LOS from dianlujitao, nvertigo created a workaround / bootsigner

boot image is not correctly resigned by addon.d · Issue #2013 · topjohnwu/Magisk

due to investigation of some members(see posting), the issue was found that addond is not correctly resigning the bootimage

github.com

would this help in this case too?
[OnePlus 3 & 3T Cross Device Development] an0ndr0id:
Preferences > Root based ad blocker > Deselect Enable web server
[OnePlus 3 & 3T Cross Device Development] an0ndr0id:
I ran the 04.12 ota update and received the same Magisk error (the 04.05 update did not have this this error) resulting in a bootloop. Are you patching each update?
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
Hello,

Cannot access TTS. When I try to configure it, it crashes the settings app.

Is this a known issue? Any fix?

Thanks
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm back on an unlocked bootloader so I no longer have problems dirty flashing updates. In fact, I'm on 0412 after dirty flashing it over 0405. Magisk add-on survived nicely.

But if you have a locked bootloader then you'll need to create a patched boot image of 0412 using the Magisk app when the system is running and then in TWRP install that patched image in the boot partition after you've dirty flashed 0412.
[OnePlus 3 & 3T Cross Device Development] an0ndr0id:
My bootloader is unlocked as well. But I keep getting that same Magisk error followed by bootloop.
[OnePlus 3 & 3T Cross Device Development] votz11:
install magisk.apk like normal app , work for me at least
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Hmm.

I went back to have a look at my logs from my dirty flashing of 0412, which booted without issues, and saw this:

! Unable to detect Magisk app APK for BootSigner
Error preloading public library libandroid.so: dlopen failed: library "libstatssocket.so" not found: needed by /system/lib64/libandroid_runtime.so in namespace system
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1989 (main), pid 1989 (main)
Aborted

Very weird. So it's works for me even with the error but it doesn't work for you.

Do you need help getting out of the boot loop?

Restoring backup of boot and system partitions only of last backup (effectively rolls back the update) is simplest way to get things going again.
[OnePlus 3 & 3T Cross Device Development] vettayyan:
Thanks It worked like CHarm
[OnePlus 3 & 3T Cross Device Development] vettayyan:
Thanks It worked
[OnePlus 3 & 3T Cross Device Development] vettayyan:
Same Question again, for Screenshots,, Is it possible to add the 3 Fingers swipe to take screenshot,, With the current way to take screenshot ( Running App (Bottom) ) to take screenshot ,, I dont have the Volume Keys working .. So need that gesture to take screenshot even on LOCKSCREEN or WALLPAPER of HOME SCREEN which is currently not possible for people like me!!

Also, Where the Downloaded Updates gets stored... I cant find the data/lineageosupdate folder
[OnePlus 3 & 3T Cross Device Development] :
GPS is working fine, though I found one app which is not updating it's location during usage, only on startup of the app.

Not using GApps either, a fix normally in 2-3 seconds using OsmAnd, FitoTrack etc...

You can set preferred network type to LTE only, though without VoLTE working, phone calls will not work. Do not know if this is what you mean, but as long as I remember the option is there and working...

Overall; 18.1 is very stable here without any issues, though it seems that copying and/or deleting files in Total Commander is noticably slower then in 17.1.
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
Commits are on gerrit since Lineage 16.0. I don't think it's going to get forward ported and included on 18.1. It's probably because code was reverse engineered from a device or core lineage team doesn't prefer this feature in general
[OnePlus 3 & 3T Cross Device Development] vettayyan:
Thanks , By the way where the Updates are usually stored!!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
/data/lineageos_updates
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
Hi all,

I have a few questions to this ROM, before installing:

- What GApps should I use? In the past, I used 'nano' but GApps don't seem to be supported on Android 11 (yet?). Probably related: how can I install Google camera (which might be better than LOS stock camera app?)?

- Are VoLTE and WiFi Calls working?

- What about the Hotspot, working?

- Can anyone compare whether this ROM is running better (smoother) than OOS 9.0.6? Any FCs? (Back in CyanogenMod times, I had such problems repetitively which was very annoying.)

- Has anyone tested Bluetooth (Audio streaming), and Android Auto and can confirm both are working?

- I will need a few financial related apps: so I assume (from what I've read so far) a locked BL w/o root would be the best solution?

- If the latter is true, I assume the way to go for me would be (coming from stock OOS 9.0.6): backup files, unlock BL, install TWRP, full system backup via TWRP, install LOS 18.1 nighly, flash gapps, lock BL (via TWRP?) - correct?

- How can I apply the GPS fix (gps.conf) w/o root?

- What are the latest security updates included in this ROM?

- Is Dash Charge working?

- Finally and very important for me, is double tap to wake and sleep supported?

Thank you so much! 😊
[OnePlus 3 & 3T Cross Device Development] BillGoss:
- Gapps: see the LineageOS installation instructions or use OpenGapps pico (which I'm using) from https://sourceforge.net/projects/opengapps/files/arm64/test/

- GPS fix: I don't see the need for it, but you can use TWRP to edit GPS config

- April 5 security patches

- fast charging works

- double-tap to wake/sleep works
[OnePlus 3 & 3T Cross Device Development] snyperius:
- locking the bootloader is done via fastboot (just like unlocking), otherwise the process you wrote down seems to be the correct way (I used MindTheGApps)

- Bluetooth audio streaming is working with all my devices (still doesn't mean that it will work with everything, but whatever worked in OOS will most likely work in LOS, too)
[OnePlus 3 & 3T Cross Device Development] beta_serpico:
This is something due only on LOS 18.1 because of SafetyNet or these steps must be followed in every ROM based on Android 11?

LOS 18.1 is going to solve this issue or it can't be fixed?

Thanks!
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
If you are using root, you can setup this gesture using the app "GMD Gesture Control" (and many more). Not sure if this helps.
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
AFAIK, just due to SafetyNet. ;-)
[OnePlus 3 & 3T Cross Device Development] beta_serpico:
What I really don't understand is if safetynet is active starting from Android 11 and not from 10.

I'm on an unofficial Pixel experience ROM with bootloader unlocked, twrp 3.5 and no magisk.

I use 2 bank apps and Google Pay to store loyalty cards.

My fiancée has a phone with LOS 17.1 with LOS recovery and no magisk.

She uses 2 bank apps.

We have no issues with these apps in both our phones... So it is an issue only on Android 11 ROMs?

Thanks!
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
I think it's just related to the specific financial apps you are using. Some of them perform a check and some of them don't.

SafetyNet is already available since Android 2.3 (although with restrictions for Android 6.0 and below, not being able to read the boot state) if you have the updated Play Store services installed/updated, see here.
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
Hello,

Is your phone ringing correctly when paired with the car?

In my case, the first call I receive the phone rings and I can ear the car stereo ringing as well. If I reject the call, the following ones I receive, the phone rings too low and the car stereo does not ring at all, but mutes the music. If I answer the call then hang up, it works correctly.

I think it has something to do with in-band ringtone.

:-/
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
Thanks for the insights. Have you been using 2021/4/2 or newer? Cannot answer your question (and would be interested in an answer as well) but the latest changelog says "Fixed ringtone when bluetooth headset connected". So maybe that issue has already been resolved? 🙈
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
I have the latest nightly (20210412). It gives me the same problem since android 10 on every rom. I remember reading somewhere that turning off in-band ringtone fixed this issue but we do not have that option anymore under Developer Settings. If there is a way to turn it off, I would love to try, as it bothers me a lot. Not a complete deal breaker as I can notice the phone is ringing by the muting of the audio and the car display shows the caller ID, but realy anoying.
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
Hm not cool because I am using my phone a lot in my car via Bluetooth...

@dianlujitao do you have an idea about this issue? Or can you re-enable that setting so that @JoniKatita can try with it turned off? 🙂
[OnePlus 3 & 3T Cross Device Development] malerocks:
Depends on the banking app. I have HSBC banking apps from 2 different countries on my phone. One has an issue with the ROM, one doesn't (go figure!)
[OnePlus 3 & 3T Cross Device Development] S4turno:
Upgraded from official 17.1 to official 18.1 (remove pin + dirty flash 18.1 + new GApps).

No major issues so far, but:

- Regular charging seems to be slower than before (it's not "charging rapidly" with the same cable/charger).

- The settings shortcut from the tiles area (sometimes) crashes the UI, sending me to the lock/pin screen.

Might try a clean install, just in case.

Edit: Both issues still there after a clear install.
[OnePlus 3 & 3T Cross Device Development] johngare:
Question, if my phone's screen is no longer the original oneplus display. Will it affect my device in flashing this rom like the flicker issue upon turning on the screen after it goes off? Thanks!
[OnePlus 3 & 3T Cross Device Development] snyperius:
I've just tried it with 2 different cars. The first one, an aftermarket head unit (JVC KD-R784BT) did not replicate the issue. Even after declining an incoming call several times, it always ringed normally (although with about half a second off from the phone, resulting in an interesting canon between the phone and the car), and resumed playing music afterwards.

The original audio system of a 2015 Toyota Yaris, however, produced the same phenomenon you were describing.

In conclusion, it's probably not just LOS to blame here but the audio system you're using, too.
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
Yes, it must be a conjunction of the two. When I try with some bluetooth headset it works correctly but on my car, a 2018 VW Golf it does not (when I was on the original firmware it worked flawlessly). It never worked with any other rom from android 10 on. I have tried with a Samsung phone with android 11 and it works. On the Samsung it has an option in Bluetooth settings to sync (or not) the phone ringtone with paired device. It would be great to have this on our device as I think this is somehow the culprit... maybe I'm wrong.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Why don't you add screenshot option to power menu? That's selectable from settings.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Here's a graph showing the charging rates of OOS 9.0.6 (OOS 4/20), Los 17.1 (Los 4/20), and Los 18.1 (Los 4/21).
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Which setting? It used to be there in 17.1, but I can't see it in 18.1.
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
I am not completely sure but I don't think this will be a problem (assuming your replacement screen has the same resolution which could have an impact if not).
[OnePlus 3 & 3T Cross Device Development] CodeFinder:
Really cool, thanks for sharing! :-) Have these plots been generated with 'dash charge' active? I mean did the phone show 'fast charging' or the like? About ~10min increase for OOS vs LOS 18.1 is somewhat noticeable. 🙈
[OnePlus 3 & 3T Cross Device Development] BillGoss:
On Los it says "Charging rapidly". Also, the difference in times is mainly due to the slower charge rate towards the end, not the early fast rate.
[OnePlus 3 & 3T Cross Device Development] johngare:
Whenever I install A11 roms, the screen will not turn back on after it goes to sleep. Fingerprint will vibrate, power button does the same but screen never goes on. Restarting will help but once the screen goes off, the issue goes again. This doesn't happen in A10 roms.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
This has never happened to me (all original hardware) so it may well be related to your screen replacement.
[OnePlus 3 & 3T Cross Device Development] johngare:
I really don't know if the screen in my device has been replaced or not. I just asked that question because someone mentioned that the screen in my op3 might have been replaced before. If that is true then how come, it doesn't have any issue installing A10 roms?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
There's a screenshot button when you tap the Recents button
[OnePlus 3 & 3T Cross Device Development] johngare:
I am able to use the latest PixelPlus UI rom right now without any issue. I don't know what the dev did but this is the first A11 rom that I can use without any problem.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
I have the exact same issue (clean flash).
[OnePlus 3 & 3T Cross Device Development] [GER]Roxxor:
Hi!

Somebody else got issues with GPS? It very often just does not show ANY satellites.

I already searched for "GPS" in this thread, and saw the suggestion to select the proper NTP server according to continent in the GPS.conf. This worked at first, but now after some time I again see no satellites at all. Does somebody know how to properly debug GPS? Unfortunately it seems like Logcat doesn't show any details regarding GPS.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've found that it will automatically encrypt the phone when I install it after doing a Wipe>Format Data in TWRP.

But if you use Magisk, you should be able to patch the boot image to NOT preserve force encrypt - but I've never done this because an unencrypted phone is a security risk.
[OnePlus 3 & 3T Cross Device Development] anttaz:
Thanks but too late to use app if already encrypted during first boot. Shame I will have to go for a decrypted ROM

Thanks for the suggestion. But by time got to Magisk app too late as phone already booted and forced encryption, therefore Magisk app would be unable to decrypt an encrypted device. I shall find a ROM that does not force me to be encrypted. Thanks.
[OnePlus 3 & 3T Cross Device Development] anttaz:
But why not? I prefer the choice myself if I want to encrypt and I prefer not to encrypt.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You could install the Magisk apk (which doesn't root your phone, simply installs the app) on your current setup and then use it to patch the Los 18.1 boot.img. Then when you flash Los 18.1 also flash the patched boot.img. That should keep the phone unencrypted. But, like I've said, I've not tried this.
[OnePlus 3 & 3T Cross Device Development] :
I am using LOS for some years now, but can choose myself if I want to encrypt or not.

On 18.1 I am not encrypted at the moment.

Don't know if this is what you mean, but my phone is not forcing encryption.

When this is not the default behaviour, I don't know anymore what I have done for that in the past unfortunately, but you are right; I want to choose myself ;-)
[OnePlus 3 & 3T Cross Device Development] :
For what it is worth.... I did not take any logs or whatever...

I am using a gps config where I am using pool.ntp.org and let the auto selection decide.

Normally this is only taking 3-5 seconds (no Google stuff on my phone and wifi and bluetooth scanning disabled).

Though.... sometimes it is not. The work around for me then (take note of the order!) is starting the app using gps and then disabling gps >>> wait till icon in taskbar is gone, and enable gps again.

This way in 3-5 seconds I have my gps back, not the other way around though....

One of my apps is not working correctly with 18.1 gps, where it was with 17.1 gps. So it seems something is changed in between, but did not check already in the changelogs. For those who want to try: the route.nl app will take the right gps location on startup, after that gps is not refreshed anymore, where other apps are working correctly.
[OnePlus 3 & 3T Cross Device Development] votz11:
how you update your vendor ?
[OnePlus 3 & 3T Cross Device Development] :
I didn't ;-)

Just changed dates in build.prop, see https://xdaforums.com/t/rom-official-nightly-lineageos-18-1-for-oneplus-3-3t.4230665/post-84793213
[OnePlus 3 & 3T Cross Device Development] [GER]Roxxor:
Ah. That workaround helps. Worked for me. Yeah, but somethings not right.

@dianlujitao

Could you maybe have a look? I would be happy to provide more data if needed.