yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Notor1ouS-:
when using android auto, connected to a car, the phone itself is very laggy/slow when using it.

that wasn't the case on los16.
[OnePlus 3 & 3T Cross Device Development] DLH007:
Hello together,

can someone tell me why LOS 17 doesnt have a real DarkMode for OLED?

Its a dark grey instead of black, why?

LOS 16 was black.

Thanks
[OnePlus 3 & 3T Cross Device Development] slipstreamer88:
Having this weird issue where files storage in setting is being shown negative. Tried to restart and clear cache, and dalvik cache from recovery.

Any help in how to debug this further?

My setup:

OP3

TWRP SAR, 9.0.6 firmware without soter alipay files, f2fs data and cache, clean installed 0404 >> dirty flash 0412 build, opengapp pico 0404, unlocked bootloader, encrypted, magisk installed (using app systemizer, systemless host module only)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I thought the same as you but, surprisingly, it DOES work on unrooted Los 17.1. See my updated post https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post82169973
[OnePlus 3 & 3T Cross Device Development] knpk13:
Adb root is still included by default on LOS (and most custom roms I'd guess, probably intended primarily for devs and scripts) from what I know. You don't need to flash anything extra to use that. Addonsu has been their "easier" root solution for users (since you can use it with apps and it has a GUI), but since they dropped it, only magisk is left. I'm actually not sure if you can use adb root with apps that need root though since I haven't tried that before.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
On an unrooted device, apps don't have access to root, only ADB (if enabled and supported). In fact there's no su binary so root access is something special to ADB.
[OnePlus 3 & 3T Cross Device Development] :
I messed it up myself with my modified build.prop settings:

By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command the ro.debuggable=1 line must be in build.prop, which I have set to 0 for CTS reasons.

Unfortunately it seems my banking app is looking for this parm because when set to 1 the app is giving an error message on startup.

So no adb root for me as long as I want to use the banking app.

Have added this to my post somewhere on page 71 also.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=2911853]BillGoss[/MENTION];

This is probably a 'do not try this at home' but may be nice to know what I managed to do without loosing data...

Setup:

TWRP SAR,

LOS17.1

Locked Bootloader

Encryption and password set

This is what I did (taking some risk, I agree on that one....)

- enabled OEM unlocking again in dev options

- Rebooted in fastboot

- fastboot oem unlock

- Rebooted in system >> worked!

- Flashed another recovery (did not work.....)

- Rebooted in fastboot again

- Flashed TWRP SAR again

- fastboot oem lock

- Rebooted in TWRP (asked for password and worked nicely)

- Rebooted in system (asked for password and working nicely)

- disabled OEM unlocking again in dev options

- Rebooted in system (asked for password and still working nicely)

So it seems it is possible to lock/ unlock, even with encrypted data and password without issues as loosing data.

Edit:

Tried it again to be 200% sure but now I got the message 'decryption failed' already after just the fastboot oem unlock and rebooting in system... Unfortunately seems to have had luck the first time but not the second time...
[OnePlus 3 & 3T Cross Device Development] :
Great information! Thanx for sharing.

Which firmware did you use? Which fw was in use when the initial encryption has been done?
[OnePlus 3 & 3T Cross Device Development] :
That's the only thing I forgot to mention indeed...

I am using your non-deblobbed 9.06 firmware.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That was my experience also: unlocking the bootloader with TWRP doesn't affect the data partition.

But, as I said in the post you quoted, LOCKING the bootloader with an encrypted data partition screwed up the encryption password for me.

Are you planning to lock your bootloader again? If so, I'd be interested to see if you have the same issue.
[OnePlus 3 & 3T Cross Device Development] :
Read again... ;)

Typing from that phone now with locked bootloader.:good:

Edit:

Tried it again to be 200% sure but now I got the message 'decryption failed' already after just the fastboot oem unlock and rebooting in system... Unfortunately seems to have had luck the first time but not the second time...
[OnePlus 3 & 3T Cross Device Development] thesplitter:
My German banking app works perfectly with magisk and magisk hide, why don't you just flash magisk and hide?

If it works you will have both root (ADB and apps) and the banking app
[OnePlus 3 & 3T Cross Device Development] :
Hi [MENTION=5008553]thesplitter[/MENTION];

You are absolutely right and this have been my setup for more then a year I think. Though, I have learned a lot the last years by reading, tweaking and just trying to find what the reason is for some issues I had with my de-Googled phone. The bad part is that I have done a fresh install more then once.... the good part is that I for example do not just install Magisk because everyone is doing that, but try to understand what is the reason why an app is not working.

For most users your setup will be absolute the easiest and probably the best. Magisk Hide is doing it's work for banking apps, Magisk is providing root access, everything is working out of the box. Though, a more secure setup would be no root access and still working banking apps, locked bootloader and encrypted storage; this is what I managed in the last weeks. Out of curiosity and just because I had the feeling it would be possible... ;)

I hope my tweaking, crashing my phone, the fresh installs and the (stupid) questions and/or posts are helping other people to make the right decisions and to let them know there are more roads that lead to Rome....

What I have learned the last days:

- locking, encrypting and changing build.prop settings is possible for a secure setup of my phone;

- unlocking and locking again may lead to a fresh install so do not do this at home...

- I know now what settings in build.prop are screwing up my banking app, so without Magisk I can get it to work

- I know the relation adb root and ro.debuggable

- I have made a nice setup to get a locked bootloader for myself and hopefully for some other people.
[OnePlus 3 & 3T Cross Device Development] :
Snap's buildin qr- and barcode reader

Is quickreader (part of Snap''s source code) acesseble in 17.1?
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Sorry if oot, [MENTION=4405529]nvertigo67[/MENTION] can we just wipe all ifaa & soter things including ifaa manager if we flash your fw oxygenos_9.0.6_noalipay.zip ?
[OnePlus 3 & 3T Cross Device Development] Hate_Breeder:
Currently in latest nightly, mic not working in all apps except calls. After restart it is normal again....
[OnePlus 3 & 3T Cross Device Development] :
No.

Read my fw thread.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
found answers on this thread what i was looking for, deleted the questions
[OnePlus 3 & 3T Cross Device Development] punio4:
Any ideas on what might be causing the microphone to stop working?

Oh, and another thing - Bluetooth seems to take forever to connect to my car radio on 17.1.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
which variant (Full/mini/Micro/Nano/Pico)of Opengapps is recommended?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
On my side:

- no sweat with BT (headset, car ... etc),

- no sweat with microphone ... [MENTION=7858776]punio4[/MENTION]

- no sweat with android auto (i just tested ... but i don't use it) ... [MENTION=2867000]Notor1ouS-[/MENTION]

- no QR/barcode reader with stock snapshot (see screenshot) ... [MENTION=4405529]nvertigo67[/MENTION]

Recommended : pico or nano open gapps ... [MENTION=6966373]Muralidharc22[/MENTION]
[OnePlus 3 & 3T Cross Device Development] punio4:
Would love to find a way to reliably reproduce the issue. It has been mentioned multiple times in the thread.
[OnePlus 3 & 3T Cross Device Development] RKS96:
Does anyone else noticed worst signal strength? In my home signal is weak as is but sinc 17.1 I regularly lose signal all together. On los 16 signal was low but l almost never got disconnected.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Same here and no VOLTE as well

---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------

Do you have Volte? Network is on LTE
[OnePlus 3 & 3T Cross Device Development] RKS96:
Is there FIRMWARE/MODEM changes between 9.x.x versions of OOS. I migrated from OOS 9.x.x stable - cant remember --> LOS16-->LOS17.1. I read that LOS doesn't include FIRMWARE/MODEM so I might be on something old. If that is the case how can i update FIRMWARE/MODEM without losing data?
[OnePlus 3 & 3T Cross Device Development] :
9.0.5 and 9.0.6 has the same modem - All other version steps (.1->.2->.3->.4->.5) have each another modem.
[OnePlus 3 & 3T Cross Device Development] RKS96:
Ok TNX. Can i flash 9.0.6 on LOS 17.1 and then TWRP SAR without reboot + LOS 17.1+Magisk without losing data? TNX again.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I like the way you think :)

Btw, there was a merge recently with a flag in the dev options that if enables will flash also lineage recovery, so far I haven't managed to make that happen, with both OTA and manual flash. The log does not even mention a recovery flash.

Has anyone tried it?

I'm not talking about downloading the recovery IMG and flashing it, I'm talking about the automatic recovery update with the nightly build zip
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Micro G magisk module if only this rom has signature spoofing, the best minimum google intrusion.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
which means we have to live with poor signal strength and without VOLTE(Airtel)? or shall we expect fix in coming days?
[OnePlus 3 & 3T Cross Device Development] matulko:
I tested this flag last week and with enabled this flag in Dev options, previously installed TWRP was replaced with lineageos recovery during lineageos OTA update.

No separate recovery download was done, just installed latest lineageos build via OTA

My setup:

- f2fs, encrypted, locked bootloader and it's is working without any problems
[OnePlus 3 & 3T Cross Device Development] :
No. On rom changes clean flash is mandatory, on major version changes clean flash is strongly recommended. Since gong from oos 9.0.6 to los-17.1 is both... Read this thread for detailed instalation instructions - it has been discussed more then once.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Weird, then it's obviously my setup, I just checked again and the log does not mention anything recovery related during the zip flash.
[OnePlus 3 & 3T Cross Device Development] :
The recovery is NOT flashed, if you consider only the part done in recovery. It's flashed during first rom boot (

https://github.com/LineageOS/androi...6ffaf6baeb0230fa164/rootdir/init.rc#L848-L855 ) if persist.sys.recovery_update=true.

If it's not changed, I'd start checking the presence of /system/bin/install-recovery.sh (rom's path, not twrp patch) and if the property is set afzer rom boot.

EDIT: Magisk removes the service definition as well as the service start.
[OnePlus 3 & 3T Cross Device Development] RKS96:
SRY if I was unclear. I know clean flash is recommended between OS upgrades. I always have done that. What I meant is I already am on LOS 17.1 but i don't remember what OOS version I was on before LOS 16 and now 17.1. I think I was on OOS 9.0.2 so MYB my bad cell signal is from old FIRMWARE/MODEM. By my last question I wanted to find out if I can upgrade FIRMWARE/MODEM by dirty flashing OOS 9.0.6 on LOS 17.1 witch will upgrade FIRMWARE/MODEM, SYSTEM, RECOVERY ect. Then without reboot flash TWRP SAR, LOS 17.1, Magisk ect back without losing data/banking apps ect.

OR MYB I can use FIRMWARE/MODEM only zip like... https://xdaforums.com/showpost.php?p=80979561&postcount=720

TNX for support.
[OnePlus 3 & 3T Cross Device Development] :
Yes, just keep an eye on the model - fw packages arn't unified.
[OnePlus 3 & 3T Cross Device Development] vizdak:
I dirty flash April 02 17.1 from 16.1 and all goes well. I'm on April 12 version now.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Could you clarify 'Yes' for first Question or 2n Question? i am also having exactly the same issue
[OnePlus 3 & 3T Cross Device Development] :
Don't flash oos but only the fw package.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Flashing 9.0.6 firmware may not be needed as we still have MPSS.TH.2.0.c1.9-00102-M8996FAAAANAZM-1.197095.1.198697.1 which is from oos 9.0.6
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Thanks for the clarification.

So it's magisk that does not allow the recovery update to happen with LOS update
[OnePlus 3 & 3T Cross Device Development] :
Anyone having issues getting a GPS fix/lock?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Nope, I use it with Android auto (app) almost every day, not a single issue so far.

GPS lock is easy and no lags.
[OnePlus 3 & 3T Cross Device Development] :
Desperate last attempt to catch my white whale: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post82333975#post82333975 (it's the same on 16 and 17)
[OnePlus 3 & 3T Cross Device Development] Eggstones:
How do you stop lineage from creating shortcuts for all newly installed apps? I can't see s setting for it on the playstore or find where you do it in settings.
[OnePlus 3 & 3T Cross Device Development] :
It's a launcher setting. If you use trebuchet: longpress empty backhround, tap settings and disable shortcut creation.
[OnePlus 3 & 3T Cross Device Development] fadern:
Hi,

Im running the 18/4 build and i'm experiencing very low volume when im in a call. Is this a known issue and are there any fix?
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
I know one way if you have root.

Go to:

/System/etc/mixer_paths_tasha.xml

(You need a root Explorer vor similar)

Increase following values to:

<ctl name="RX0 Digital Volume" value="90" />

<ctl name="RX1 Digital Volume" value="90" />

Whithout root no idea.
[OnePlus 3 & 3T Cross Device Development] :
Boot to twrp, mount system and edit or replace the file (if teplacing check permissions and sepolicy context).

Disclaimer: I'm not responsible if increasing these values physically breaks the speaker.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
i am on LOS 18.04 nightly ,SAR TWRP, no root. can i flash 19.04 Nightly as OTA or through TWRP?( i would like to retain SAR TWRP recovery after flash)
[OnePlus 3 & 3T Cross Device Development] :
A dirty flash in TWRP will do the job ;)

I think you are referring to some posts about recovery automatically updated by using OTA, though you have to enable this in developer settings.

OTA in combi with TWRP is not working when encrypted, so instead just download the latest ROM package, reboot into TWRP and dirty flash the package.

This way you also see what is happening (error messages etc...)
[OnePlus 3 & 3T Cross Device Development] fadern:
Do you have a guide for rooting oneplus3? Im looking at magisk but ive never tried it.

I dont know if our device is system-as-root?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Fairly easy, download magisk zip, flash it and all done :)
[OnePlus 3 & 3T Cross Device Development] fadern:
I have now rooted my phone and I dont seem to have that file.
[OnePlus 3 & 3T Cross Device Development] :
/system/vendor/etc/mixer_paths_tasha.xml
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Just tried to use Instagram to upload a picture but the app just crashed. It worked fine last night. (Uses lineage 2020_04_20)

Clean cache or reinstal?
[OnePlus 3 & 3T Cross Device Development] fadern:
Im using Signal as my default mess app and when im calling but get no answer the "send message" link/notification isnt doing any thing. I suppose it should open the message app and send a message?!
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Just realised that either last night's or today's version of lineage has wiped all my audio and photos!

This has not happened to me before. Why has it done this? Luckily I backed all up yesterday. Could this have anything to do with the migrate app restoring it in such a way that it got wiped.

Of I hadn't made a backup yesterday I would be devastated.

Is this a massive bug or have I done something wrong when updating lineage?
[OnePlus 3 & 3T Cross Device Development] stalkerski:
Help

Guys please help I have problems with microphone it stops work randomly and helps only reboot. How to solve it?
[OnePlus 3 & 3T Cross Device Development] dbsoundz:
Does someone know how to do this with new LineageOS Recovery? I updated from 16.1 to 17.1 and also installed the LineageOS Recovery. In TWRP just boot into recovery, enter your Password for encrypted data and flash... But in LineageOS Recovery I can't see any options to decrypt data?!
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
Deleted
[OnePlus 3 & 3T Cross Device Development] FrailtyXYZ:
coming from OOS 4.5.1 with ext4, latest twrp from twrp website as well. what steps can i do to clean flash latest nightly? can i just flash latest firmware then do the steps in OP? TIA.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Anyone noticed that WhatsApp font is not changeable since 18-04 Nightly(not sure about previous builds though)?

---------- Post added at 09:07 PM ---------- Previous post was at 09:01 PM ----------

I would have done this

1.Flash 9.0.6, enable OEM unlock,unlock bootloader,enable USB debugging,enable advanced restart option ..etc,check LOS wiki)

2.Flash TWRP/SAR TWRP ( do not boot into OOS as TWRP will be replaced by OOS recovery), boot into recovery

3.Wipe/format

4.Flash LOS nightly followed OpenGapps(Pico version)

( you need to have the above 2 files in your PC and move to mobile after formatting)

5.Boot into System
[OnePlus 3 & 3T Cross Device Development] :
Theoretically yes, but that way you'll need to format the userdata partition after upgrading the fw. Either you need to relock the bootloader before upgrading, or you may want to consider: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

EDIT: if you decode to relock the bootloader, please report if userdata is wiped - to my knowledge no one has tested with 4.x.x bootloader...

Happy flashing!

---------- Post added at 18:07 ---------- Previous post was at 18:00 ----------

Why? Firmware package is absolutly sufficient (Download size 1.6 GB vs. 50 MB)
[OnePlus 3 & 3T Cross Device Development] :
Are you sure it was LOS related? Did not notice anything in changelog related to photo or audio storage. Did you also update Gapps and may be some Gapps related stuff which could be the culprit?

I am not using any Gapps or Google apps, updating almost every day at the moment but did not loose any of my data...

When you still have your backups you may be could do a restore of /system, /data and your sdcard, update again and share the logs when it is happening again ;)

---------- Post added at 18:48 ---------- Previous post was at 18:41 ----------

Somewhere on these forums I read about people flashing latest OOS 9.06 and then flashing a custom ROM because otherwise they do not manage to get VoLTE working. Though I do not know what, is there something else not firmware related which is flashed en could be the difference between just flashing firmware package or OOS complete?

As said, no idea what, but do not know if there are some "hidden" partitions I have missed??? :confused:

As I see it there is indeed no reason for flashing complete OOS and for myself latest OOS was more then two years ago....

---------- Post added at 18:53 ---------- Previous post was at 18:48 ----------

Because it is not there... ;) You would better have read before switching to LOS recovery... lots of info around here in the last 5-10 pages... and in other topics ;)

---------- Post added at 18:58 ---------- Previous post was at 18:53 ----------

No, just tested with latest build from the 20th. Though, there are some changes in GPS part as mentioned in change log, so you could try to update and clear all caches. Do not know if it helps but it is worth a try...
[OnePlus 3 & 3T Cross Device Development] Eggstones:
No. Last night I reinstalled my backup using the migrate app and all my audio was there. This morning I installed the 19th April update and then later this morning the latest. Not sure when the data went as I didn't try to play any audio files until this afternoon when I noticed my photos in gallery, videos and audio was gone.

The installs was done via the system.

I'm afraid I haven't a clue how to get the logs, but if I get some assistance I'll do that.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
I have	lineage-17.1-20200419-nightly-oneplus3 installed. It does freeze the whole system if i lock the screen or put the phone on charge. Also if i restart the system it does sometimes as well especially if i restart from TWRP after wiping chache/dalvik. All these system freeze are random. Sometimes does not do this for long time...Anybody got similar experience with this nightly??

Also SIM card switch not available and can not turn on/off mobile data from statusbar...

Also was trying the 20200420 nightly but i have the following issues: network does not shown properly at status bar, messing up with SIM card slots, the "do not disturb" always switching ON, mobile data not available
[OnePlus 3 & 3T Cross Device Development] :
Maybe corrupted download, maybe an error while flashing, maybe something else. I've read that, too. When I saw it the first time, I've asked for a recovery log and the exact version of the fw-only package, which breaks volte- sadly I never got an answer.

If you compare my fw packages (the unmodded ones) with the original full oos zips, you'll find it's exacty the same for the flashing directives as well as for the conten of /firmware-update and /RADIO. I've also checked the oos 9.0.6 first boot sequence, if any changes e.g. to the efs partions are done or if anything is changed on the fw partions - it's not.

Since then this theory it's necessary to flash full oos is repeated here and there, sometimes I ask why, because I'd like to sort it out (maybe there's a broken or incomplete package around), but if I get an answer at all (mostly not - thanx for your answer!) it's basically "I've read it's necessary"...

I'm doing fw packages for the op3t since 4.0.3 and for the op3 since 9.0.1 and never had a single report of this for los-14, los-15 and los-16 - I'm really interested in this simple "why?", because if there's a broken fw package around, it should be sorted out - if there's another reason it should be announced. At the moment it seems to me like a shadow on the wall from Plato's cave allegory is just repeated without any reality check.
[OnePlus 3 & 3T Cross Device Development] Muralidharc22:
Thanks for 'Why' ?:) i was not sure of Firmware flashing how it works, will give a try as described below from https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

and let you know if i get VOLTE working or at least if i get a good 4G reception as on OOS 9.0.6

---

Custom roms

(not containing firmware - to my knowledge: all custom roms)

flash official twrp-3.3.1-0 and reboot to recovery (you can skip this, if you already use twtp-3.3.1-0, of course)

take a nandroid

flash

for Oneplus 3T: oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip

for Oneplus 3: oxygenos-9.0.6-bl-km-5.0.8-firmware-3.zip

reboot to recovery

(dirty) flash your preferred, 9.0.x firmware needing custom rom (if your rom doesn't need 9.0.x firmware, stay with 5.0.8)

wipe cache and dalvik

reboot to system and enjoy your custom rom

---