yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Phid13:
This ROM with magisk 20.4, pico gapps and madys MCD q kernel using the darknesssched CPU governor gave me the most battery life I've ever seen on my phone, consistently 5 hours screen on with Max brightness, wifi and heavy gaming, while also being the smoothest android 10 experience I've had yet. However, since using thus ROM the phone has frozen three times in 3 days when I couldn't do anything and had to restart the phone. Not sure why this is.
[OnePlus 3 & 3T Cross Device Development] pijas82:
Gallery 0 images, lags, can't set a ringtone. Back to pie again, and I can't download anything

Edit: remove sar twrp, flash official and everthing works
[OnePlus 3 & 3T Cross Device Development] thesplitter:
The ringtone issue is a gapp issue, I've ended up noticing that the "retro" ringtones apply perfectly but the pixel lineup doesn't.

I had lags only when I dirty flashed, but after getting the SAR TWRP and wiping data, everything runs smoothly.
[OnePlus 3 & 3T Cross Device Development] pijas82:
Clean flash with sar twrp, problems, ringtones, gallery, downloads, lags , clean flash , change twrp , no problems here

Same gapps pico 03/04 same build, different twrp
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Twrp ( no sar) + ROM + pico opengapps

Perfect, no problems
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can flash Los 17.1 with official TWRP, and you can back up 17.1 with official TWRP, but if you restore a Los 17.1 backup your phone won't boot unless:

- you restore a system image, or

- flash the rom again.

That's why you're best off with SAR TWRP when using Los 17.1

See https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post81410383
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
Tried dirty flashing/updating from LOS 16, wouldn't boot (hey, can't blame a guy for trying); clean flashed with micro Gapps and Magisk 20.4, been running fine all day. WiFi, BT, camera, GPS working, all my apps working. Thanks to OP and the Lineage team for squeezing more life out of the OP3!
[OnePlus 3 & 3T Cross Device Development] sobhan06:
what is the purpose of installing magisk? only to gain superaccess in the sense to just root the device? Because some apps are showing that it can not be accessed when a device rooted error? any solution for this?

Also one thing I noticed is the internet speed showing the bar in the status seems to bit bigger occupying more space.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Magisk is good for two things:

1. Providing root access. Applications such as Titanium Backup, file explorers, and so on have more functionality using root.

2. Allowing a phone with an unlocked bootloader to pass SafetyNet. It also allows protected apps like Pokemon Go, Netflix, and many banking apps to work on an unlocked or rooted phone.

So, if you don't need root access and your bootloader is locked, then you don't need Magisk.
[OnePlus 3 & 3T Cross Device Development] npeersab:
working fine for me. I am using pixel launcher
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Error while flashing Magisk

I tried flashing Magisk through twrp, but it showed an error. also, I didn't gain root access do not know why(checked it through root checker). installed magisk manager to check the safety status: cts profile: false is appearing. Googled around but no direct solution can be found.

Also when an incoming call is accepted the screen goes black and does not light back unless the calls get over/disconnected, anyone experiencing the same?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Make sure you unmount the system partition before flashing Magisk.
[OnePlus 3 & 3T Cross Device Development] moso11:
Are you using any modded Pixel Launcher or the original one?

Can you share a link?

EDIT: Which nightly are you on? Are you using TWRP-SAR?
[OnePlus 3 & 3T Cross Device Development] Darkje:
We only have 2g and 4g. Volte is mandatory for a proper dialog. Buy no dice. It simply dont work. Back to oxygen. And time for a new phone.
[OnePlus 3 & 3T Cross Device Development] fbngrt:
Thanks for the clarification. This is what I expected. I am sticking with TWRP for now.

Apart from that I upgraded my device (Oneplus 3 / locked bootloader / FW 9.0.6 / encrypted) yesterday. I installed the TWRP sar version and dirty flashed 17.1 and opengapps. Worked like a charm. :)

The only small issue I noticed is the night mode not being enabled/disabled on sunset/sunrise. I can live with that.
[OnePlus 3 & 3T Cross Device Development] :
Please read - at least - the OP, better read the complete thread:

Either use the shipped kernel reproduce the freezing and help fixing it by providing pstore, or use the mcd thread to help fixing the custom kernel.

Using a quite early stage rom with a custom kernel and reporting freezes in the rom thread shows a massive lack of understanding technical contexts as well as a lack of resepect for the OP: Recommending custom kernels for better whatever is ok, but for reporting issues, always return to stock los17 and reproduce the issue before reporting it in the rom's thread; for issues with a custom kernel, use the custom kernel's thread. Obviously, no one can fix a custom kernel issue in the rom...

Sidenote: the technical knowledge needed and the dare for max customized setup often correlate indirectly... :(
[OnePlus 3 & 3T Cross Device Development] sobhan06:
CTS profile false issue

CTS profile status is false for me. Trying to figure this out but whatever I do it is not changing. on Lineage OS 17.1, Magisk 20.4, tried Hide props, Busybox modules with a terminal emulator for editing the fingerprint props. This simply didn't change anything.

Then through TWRP flashed Magisk hide props, safety patch, and Petnoire's modules but that also didn't change anything.

So, what are the other options available. any guidance will be appreciated.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
I flash ROM with simple wip
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Did you enable Magisk hide in Magisk Manager? It's off by default.
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
VoLTE and VoWiFi work fine, but the settings for your provider may be missing in the EFS ?! :cool:
[OnePlus 3 & 3T Cross Device Development] DavidXanatos:
How does rooting work on system-as-root devices anything to worry about or do i just install Magisk and that's it?
[OnePlus 3 & 3T Cross Device Development] npeersab:
I am using this pixel launcher https://www.apkmirror.com/apk/googl...ase/pixel-launcher-10-4-android-apk-download/

[only this variant is working others were crashing]

currently on lineage-17.1-20200402-nightly

TWRP: https://androidfilehost.com/?fid=4349826312261695823
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Ho thank god, that worked for me. Cheers mate.
[OnePlus 3 & 3T Cross Device Development] Eggstones:
How did you activate that? Before going on to lineage 17.1 I was able to get volte but not vowifi/WiFi calling by using *#800# (or *#800#*) but that isn't working. Have hardly any reception at home (UK, three) so need to sort this as I'm in lockdown (or get a new phone)
[OnePlus 3 & 3T Cross Device Development] punio4:
If you only installed pixel launcher you don't need it. Try doing an OTA update and see if pixel launcher continues working.
[OnePlus 3 & 3T Cross Device Development] sephk:
voice recording apps only work once after rebooting, after that they cant seem to access any mic, main or rear. I have tried it with Google Voice Recorder also, same result. After that Google Assistant is also not able to access the mic until the next reboot. Phone calls are able to access the mic ok even without reboot. Anyone else can try this out please? Thanks
[OnePlus 3 & 3T Cross Device Development] Dirk:
That's for OOS. Field Test number is *#*#4636#*#* As i said before, i think we're out of luck on Three Network (See screenshot) When you're on the main screen use the menu on the top right to check IMS.

Edit: Once you've checked let me know if your result is any different from mine.
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Odd. I get the same as you but this screen looked different on both OOS 9.0.6 and lineage 16 (last version) install. Neither of the toggles were greyed out on those installs. I also got volte working fine on OOS 9.0.6 too so I know that works on stock with three.

The IMS info is almost the same bar the first entry. Should that be registered or is it down to me being on WiFi?
[OnePlus 3 & 3T Cross Device Development] kallest1100:
Hello everyone!

a question, can you update from the last lineage 16 directly to the current lineage 17.1?

If so, how should you do that?

Or do you have to set everything up again?
[OnePlus 3 & 3T Cross Device Development] :
*#*#4636#*#* is an official supplemental service code supported on all current phones. For a starting point: https://en.wikipedia.org/wiki/Supplementary_service_codes

*#80[0-3]#* are proprietary oneplus/oppo codes.

Since the latter is closed source, proprietary stuff no one has source code for, they are execlusive to vendor's stock rom. (NOTE: I'm not sure, but I think it's partly in logkit with some hooks and callbacks in fw/b - if you want to reverse engineere these codes.)

To do the same as enabling volte/wifi you can do this on custom roms:

https://xdaforums.com/oneplus-3t/how-to/guide-enable-volte-root-devices-t3593652 (edit from twrp if you arn't rooted)

Maybe you need additionally:

https://xdaforums.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542

https://xdaforums.com/oneplus-3t/how-to/guide-enable-volte-custom-rom-android-t4073355

...and maybe it's not working at all... :(

---------- Post added at 16:19 ---------- Previous post was at 16:13 ----------

If you wonddr if time for a clean flash, the answer is always yes.

Though some users have reported it seems to work - if you don't know exactly what you are doing and what the technically differences between 9 and 10 are, I'd strongly recommend a clean flash. It will save your time and save you from disappointments.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
I'm also using classic TWRP (no SAR) for now, how do I change to TWRP SAR ?

Thanks! :)
[OnePlus 3 & 3T Cross Device Development] Eggstones:
The lineage website told me to reinstall and I think the updater recommends you to do that too
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
- Using fastboot as always

- Through TWRP > INSTALL > Select .img as file type > Select TWRP.img > Flash it as Recovery partition

- [MENTION=2911853]BillGoss[/MENTION] described how to flash it with dd command via Terminal Emulator some posts before yours
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Last year, when I was using LOS 16, I edited the EFS partition as described in this guide: https://xdaforums.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542 (but unfortunately the link in this thread no longer works).

Since then VoIP and VoWiFi have worked perfectly.

Even after installing LOS 17.1, both worked immediately, because the EFS partition was not changed by the update.

This EFS changes affects the system more deeply and it takes about 1 hour to overwrite a lot of files in EFS, but it's permanent and ROM independent.

There is also the possibility to delete or change profiles, but with an update these changes are overwritten again, so it's not permanent. AFAIK these changes "only" activate VoLTE but not VOWiFi.
[OnePlus 3 & 3T Cross Device Development] snyperius:
Is it safe to relock the bootloader with the LOS recovery and LOS 17.1 installed? What if I have already installed my apps as well? Will it make a full "factory" reset or just wipe /data? Will OTA updates still work? (There is one app I would like to have which won't start because it says my device is rooted, which AFAIK is not. At least I didn't root it. And it's not even a banking app...)

I'm a bit confused because I've only found several years old contradictory information about this on google.

Thanks in advance!
[OnePlus 3 & 3T Cross Device Development] votz11:
maybe bug : conected bluetooth work well but when someone call you phone does not ring , its like to be in silent mode

anybody else face same?
[OnePlus 3 & 3T Cross Device Development] Eggstones:
I have to say the battery life is amazing! I wish I had done this ages ago
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
FYI... you need to search a bit more :o .
[OnePlus 3 & 3T Cross Device Development] Notor1ouS-:
i directly upgraded from LOS16 to 17. I did the same a year ago from 15 to 16. NO wipe since then.

everything works. i did remove all my magisk modules before, just to avoid problems.

first boot takes 10-15mins. after boot the system needs another 5mins for "starting system".

then, the "system process" and google services are busy with rebuilding stuff it seems. that took 30mins, during that time the system can be laggy & slow.

its also helpful to restart the phone and wipe caches + dalvik again.

no problems now, the phone is very snappy and works without problems.
[OnePlus 3 & 3T Cross Device Development] spandy992:
Rom is awesome with great battery life.

Just two problems.

1. Airtel Volte doesn't work.

2. Slow motion doesn't work on gcam and stock lineage camera.

Any solution?
[OnePlus 3 & 3T Cross Device Development] snyperius:
I did read all of these before posting.

Most of them are about TWRP thus they're irrelevant for me.

"Since los recobery doesn't support encryption, it can't solve the ota issue on encrypted data partitions."

This is part of why I wrote the contradictory information part of my post, since I did encrypt my data partition and had a successful OTA update, moreover, the phone does ask for the pin before booting.

And none of these answer my question if relocking the bootloader will wipe everything or only the data partition. (Or do apps store their data on the data partition,too? I'm sorry, I'm a noob)

So thank you for your time and effort but you didn't really help at all...

Somebody who actually knows the answer to my questions?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Locking (and unlocking) the bootloader automatically reformats the data partition - it's not the same as a factory reset. That means all your apps and settings and all files will be wiped. It will be like a brand new phone. But the operating system is untouched so it will boot Los 17.1 if that's what your flashed. UNLESS you are running the latest versions of TWRP which are signed with the right keys, then locking/unlocking the bootloader doesn't reformat the data partition.

Also, if your phone isn't rooted (you didn't flash Magisk before locking the bootloader) or your rom doesn't supports rooted debugging (which Los 17.1 does) you won't be able to change the recovery you use on the phone, UNLESS you're using TWRP. TWRP is both signed (can be used on a locked phone) and can flash recovery images.

Edited. And again.
[OnePlus 3 & 3T Cross Device Development] berturion:
Hello, did anyone try to install microg with nanodroid on this rom ? Does the nanodroid spoofing signature patch work ?
[OnePlus 3 & 3T Cross Device Development] :
Is this true [MENTION=2911853]BillGoss[/MENTION], as I read something different here: https://xdaforums.com/showpost.php?p=79354383&postcount=569 (second part)
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I'm sorry but I assume that if you ask, "it's safe to relock the bootloader...?", you know what that operation does. Those are the first questions you should ask yourself, what do you know about relocking the bootloader? what happens if I lock or unlock the bootloader?

If the information you read doesn't answer your questions... Yes, you've to search a little more definetly.

Don't take this as an offense, I just want to prevent users from having future problems. To be at this point it's necessary that you understand basic concepts.

Remember this "To build a house you've to start at the foundation".

Thank you [MENTION=2911853]BillGoss[/MENTION]

?

I guess, he meaned TWRP keeps installed and works even if you lock or unlock the bl, because this version was "signed to work with locked bootloader"
[OnePlus 3 & 3T Cross Device Development] snyperius:
Again, as most of the time, I did my research before posting. Some people wrote locking the bootloader on a custom ROM could cause bootlooping or even bricking. Some wrote it's safe. Most of them wrote about TWRP, not surprisingly, since the LOS recovery has been publicly available only for a few days so I think it was fair to ask. Thus I asked my questions here, so that someone with experience or knowledge regarding my question could help. You've proven you have none of those. Why you still have to try to prove me wrong is beyond me. You're just making searching less efficient with posts that have nothing to do with this topic, and trying to make me do just that, too. This is my last reply in this topic for now, it went too far already.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Correct, if you're using TWRP you can update your recovery. But that's not possible if using the Los recovery on an encrypted phone (context of the original question).

I'll edit my post to make that clear.
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Is los Camera that good?

Are images taken from Los camera is good? I have installed gcam for usage, it produces images better than Los camera but not as the stock camera. what do you think?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Calendar stock app:

In contrast to LOS 16, Planning option and Parameter menu (three dots in the upper right-hand corner) have disappeared on LOS 17.1 (see the three attached screenshots). Hence, add a new event is impossible. In addition, the display is language-dependent.

Is anyone facing this issue? ... It is not an issue ... https://android-developers.googleblog.com/2019/03/aosp-application-updates.html

AOSP Application Updates (28 March 2019)

To date, the following 3 apps have been cleaned up: Music, Calendar, and Calculator.

Calendar Application

AOSP's Calendar app now exposes itself as an intent handler for the calendar events. New events cannot be created and existing events cannot be edited or deleted. The following features have been deleted: support for multiple accounts, reminders and settings. In addition, some features remain that are not needed for providing a part of the platform functionality: views for day, week, and month. This app may be further simplified in the future.
[OnePlus 3 & 3T Cross Device Development] :
I know it is the locked bootloader issue again, but little help would be appreciated.

Out of curiousity I just:

- flashed SAR TWRP

- Formatted /data and wiped the rest

- Did an OEM LOCK by fastboot

- flashed the whole stuff (latest firmware, Lineage 17.1 04/04

- rebooted into system, set a password, encrypted the device, disabled OEM unlock and enabled ADB in developer settings

- rebooted into system and configured the rest

Though....

The warning screen is gone ofcourse, everything is working fine (Lineage is great btw), but the banking app I had issues with and needed Magisk for, is still complaining.

Am I missing something here?
[OnePlus 3 & 3T Cross Device Development] DavidXanatos:
So the LOS 17.1 does not longer have the privacy guard, that's a pity.

So its no longer possible to deny an application a particular permission while making it think it got it?

Or is there a way?

Also I don't understand why, if the new permissions hub and old privacy guard was an eider or decision, why drop the IMHO superior privacy guard?
[OnePlus 3 & 3T Cross Device Development] Doc Sniper:
Look at that: https://www.xda-developers.com/line...-addonsu-implementation-favor-magisk-manager/

See last paragraph:
[OnePlus 3 & 3T Cross Device Development] BRDigung:
I really miss the three finger screenshot in some lineageos 17.1 buils the screenshot method is included, is it also coming to the oneplus3?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Did you try disabling USB/ADB Debugging?
[OnePlus 3 & 3T Cross Device Development] DavidXanatos:
[MENTION=3288532]sniperle[/MENTION] thanks but that is still not really much saying.

The internet says: "The application permission settings is based on the runtime permission system introduced in Android 6.0 (API 23), while Privacy Guard is based on AppOpsManager API, a lower level permission management mechanism introduced in Android 4.4 (API 19). If you allow or deny a permission from the APP's application permission options, the APP will know that. But if you deny a permission with Privacy guard, the APP will not get any feedback, i.e. it will not know you have denied the permission with Privacy Guard. Privacy Guard also has higher priority weight than application permissions. For example, if you allow read contacts permission in the APP's permission settings and deny the very permission in Privacy guard, the APP will think it has got the permission while acctually it will just get empty result."

So it does not seam like there would be a direct conflict between these two features. But more like for whatever change to Android 10 the AppOpsManager API was no longer suitable and as a last desperate resort it was decided to enable a much less powerful permissions hub.

Really a pity.

Anyhow I would appreciate some more info's what was the issue with that API that made it no longer possible to implement the privacy guard feature.
[OnePlus 3 & 3T Cross Device Development] knpk13:
More info on the technical side of that has been sparse from the LOS devs from what I've read (other than saying that they were unable to port it). I'm not able to find the exact link, but this discussion was on the LOS subreddit a lot. You may want to look/ask there or on IRC.
[OnePlus 3 & 3T Cross Device Development] :
I did now; in developer options OEM unlock disabled, ADB disabled, USB file transfer disabled, fresh install of banking app, though still the same issue. Can this be because I have no Gapps installed then... default setup of almost every phone is with Gapps installed. Should not know any other reason... :confused:
[OnePlus 3 & 3T Cross Device Development] :
No gapps -> no g services -> no safetynet api -> no apps, which utilize saftynet api will work.

If that is the issue with ypur app: nobody can know with that amount of information.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
hello, I need a little help. I want to clean the OP3 and then put the Lineage 17.1

For that I need to block the bootloader and install the source to later do the whole process. Someone help me with Recovery from oneplus to put and then the whole process? I already tried and I can't block bootloader ...

Thanks
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
LOL! I though you have it installed, without google services installed it's not possible a verification from the API protocol.

https://developer.android.com/images/training/safetynet/attestation-protocol_2x.png
[OnePlus 3 & 3T Cross Device Development] :
Ok [MENTION=4405529]nvertigo67[/MENTION], I understand. Though, with Magisk in the past (also without Gapps) it worked without any issues so never thought about Gapps.... I guess I am lost in this one but don't bother, it is not the biggest deal; further working fine.

Thanks for the help [MENTION=4405529]nvertigo67[/MENTION] and [MENTION=4938641]Viper The Ripper[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
If you think "a banking app" and "is still complaining" is sufficient information to dig into your issue, I'm out.