yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can only use fastboot commands when your phone is in fastboot mode and you can only use ADB commands when your phone is booted or in recovery.

To check that your PC can see your phone in fastboot mode type:

fastboot devices
[OnePlus 3 & 3T Cross Device Development] Solifuge:
Hi guys,

sorry for the n00b question.

Is the LOS 16 supporting the Adaptive Battery ? I can't find this setting in my OP 3T.

Thanks in advance !
[OnePlus 3 & 3T Cross Device Development] :
Answered here: https://xdaforums.com/showpost.php?p=79043072&postcount=934
[OnePlus 3 & 3T Cross Device Development] Chol:
I have the same issue. If I connect my phone to the PC after a phone reboot, USB debugging is enabled. I then have to enable developer settings, disable USB debugging, disable developer settings. After the next reboot, the same procedure again... :(
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I installed 0319 build according to two procedures:

- from a clean installation of LOS 16 (0304 build) + successive updates (automatic or manual) ... until 0319,

- a clean installation (from scratch).

Surprisingly, some Settings menus (e.g. Show nofications menu of Messaging) depend on procedure used.

Strange or expected ?
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
Is there any possible way to increase the notification icon size for always on display?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I don't think so.

A possible way to increase the notification ligth (not icon) on display:

==> enable "Lights with screen on" and "Use custom values" in "Notification ligth" menu.
[OnePlus 3 & 3T Cross Device Development] gon250:
Thanks for your time. I have solved the problem by installing the drivers of the phone from an installer. I'm not at home but in case someone is interested I could share it.

I have had the problem on a windows 10 machine and the adb command was working properly(Also the devices manager was showing my device) the problem was on the fastboot command. After install the drivers the problem was fixed. Sorry for the noob question here and I guess I was missing details.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About a customization issue of SIM card:

A color change of SIM card disables the PIN code input screen at restart and the mobile network is not working!

Tested from:

- a clean installation of LOS 16 (0304 build) + successive updates (automatic or manual) until the last one,

- a clean installation (full wipe + install build/gapp/official SU ) from scratch (i.e. without restoring devices settings via a Google Drive backup).

- a clean installation (full wipe + install build only ).

==> My solution for removing this issue: a NANDroid Restore.

Has anyone else experienced the problem? Or check it out?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I tested on NLOS, so there might be some differences to official LOS...

No problem here. Changed colors for both SIMs, rebooted. Everything worked fine. PINs asked and network working.

My setup: Clean flashed last NLOS build from December and dirty flashing every build since then.
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Changes included in lineage-16.0-20190320-nightly-oneplus3-signed.zip

increase timeout for waiting on block device

android_system_vold

Does this correct OTA update issue for anyone?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I also tested on NLOS 16.0... a great build, ... :) but failed on LOS... :(

---------- Post added at 19:09 ---------- Previous post was at 18:25 ----------

On Linux, no need to install drivers ... only adb and fastboot via Terminal... it's fast and efficient.

For Debian-based Linux users (ubuntu, linux mint ...): sudo apt-get install android-tools-adb android-tools-fastboot

==> https://www.xda-developers.com/install-adb-windows-macos-linux/
[OnePlus 3 & 3T Cross Device Development] :
If you look at [MENTION=9708417]Eric_Lev[/MENTION]'s logs, my analysis, the suggested workaround and [MENTION=5091734]dianlujitao[/MENTION]s and my open questions, you'll find that the issue is not really accepted as issue du to open questions (basically: why is it working for some setups, but not for others). This means it is highly unlikely to find a fix in gerrit (why fix somethimg that is not an accepted issue). You'll also find, that the mentiomed commit doesn't relate in any way to the blocked file creation on the cache fs.

I may be wrong, but perhaps a logcat of the issue and details on the setup could be helpful to track this.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION]:

Of course, I was waiting for confirmation of this issue before posting a logcat.

From a clean install (full wipe caches/data/system + install 0319/nano gapp/official los su) ...

OnePlus 3T / FW 5.0.8 / TWRP 3.2.3-10 / f2fs cache & data / official LOS 16.1 / encrypted data

Please, find enclosed the logcat... Thanx for tracking this issue.

E.
[OnePlus 3 & 3T Cross Device Development] Reeb_Lam:
Anyone one knows if there is screen burn in protection in always on mode. I didn't notice the text move in always on mode even after 2 minutes.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I'm new to this rom, I just finally updated from Sultans Lineage for the 3t. Great rom! Thanks for building it.

I'm having an issue in that the brightness slider seems to work on an exponential scale. Full bright is as bright as I'd like it be, but what was half brightness with any other rom I'd used previously, now with this rom I need to set it at ~80% to get the same brightness level. Adaptive brightness is turned off, I'm just setting it manually, so that's not effecting it. Is this normal with this rom?

I clean flashed the latest updated so everything should be good there. I had dirty flashed it over Sultan's Lineage 14 originally and that actually worked really well, but this issue was present so I figured I'd clean flash it to see if that changed anything. I'm not running any other modification either.
[OnePlus 3 & 3T Cross Device Development] Dirk:
You're correct about how the Brightness slider works. It's intentional though. A Pie 'feature'

I find 70 is the new 30.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Yikes, this is a feature?! I'm really curious what the advantage of it is?
[OnePlus 3 & 3T Cross Device Development] camdadeye291:
I asked a couple of days ago but no-one answered my post. What is the difference between the official and unofficial builds (aside from the obvious)? Is the unofficial more stable or something?
[OnePlus 3 & 3T Cross Device Development] Dirk:
In physics we talk about the arrow of time, as incremental time as we know it is illusory and subjective. It is better to think of time in the context of Entropy. Cause comes before effect. Things move from order to disorder. Custom ROMs move from unofficial to official.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Lmao
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Yes I'm aware of those 2 questions, suggested workaround, & that gerrit may not see it as anything to fix for 3/3T. Is it possible a TWRP update may help?

Manual flash is not a deal breaker as OTA auto updates are really just a convenience.
[OnePlus 3 & 3T Cross Device Development] Reeb_Lam:
Can anyone please confirm if there is burn in protection from always on display feature. I didn't saw text in aod mode even after 2 minutes.
[OnePlus 3 & 3T Cross Device Development] :
If you are really aware of [MENTION=9708417]Eric_Lev[/MENTION]'s logs, the analysis and suggested workaround, how can you conclude that a twrp update will help????

The issue is in tje rom, when the files needed for autoflashing are generated - this is not related to twrp: twrp can't find the necessary files, because they arn't generated by the rom. TWRP CAN'T FLASH INEXISTENT FILES.

I would suggest you read the logs again to understand, what's going wrong inside the rom.
[OnePlus 3 & 3T Cross Device Development] gon250:
I have disabled one of the two sims cards and for some reason.. randomly appears on the top menu the icon of both sim cards. Not always only some times. Any idea why this happends? someone having the same "issue".

Also I have seen when I change the style from default to dark or the accent color, some views still in black or white and with different acent colors.. a kind of mix between both.
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the log!

May I asked someone else to have a look at this log, please?

After inspecting this for hours, I think I'm overseeing something elementary.

What I read from the log, the settings fragmemt for com.android.settings/com.android.settings.sim.SimPreferenceDialog is restarted successfully, but I don't see or miss, why the sim card settings are vanished.

It's not sepolicy. And I have no changes on nlos compared to los in the simPreferenceDialog. The only changes regarding sim in general are: https://review.lineageos.org/q/topic:"pie-msim-ringtones"+(status:open OR status:merged) , but I can't see how these should relate to the symbol color...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION]

First, thanx.

Is there anything else I can do to help you?

[MENTION=9350973]All[/MENTION]

If relevant or useful: may I ask someone to change the symbol color of one of their SIM cards and restart to confirm this issue?... on LOS 16 of course.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
That's constructive: read carefully and follow directions from the maintainer.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
To be contructive: could you change the symbol color of one of their SIM cards and restart to confirm this issue (i.e. https://xdaforums.com/showpost.php?p=79159967&postcount=1342) ?

Thank you in advance for your help.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I don't like sarcasm. Anyway, please state precisely the steps you want me to perform and I will do the test.

The linked post seems unclear to me, likely due to me not being natively English speaking.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I didn't mean to be sarcastic and I am not natively English speaking (I am French... nobody is perfect ... :) ).

First, many thanks for your help.

Second... About the issue:

Go to Settings … Networks & Internet … SIM cards

Select SIM slot 1 or 2

Change the colour of SIM card … Confirm by OK

Go back to home page of Settings

Restart

Question: is the PIN code input screen enabled at restart?
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9708417]Eric_Lev[/MENTION]: I guess the log is from before the reboot, isn't it? If so, would you provide a log from the reboot, please?
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I have 2 Sims, both with PIN, both with custom color.

I'll do what you ask on my 1st sim as soon as you confirm the setup is ok.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION]:

Yes, it is the locat before reboot.

I will do my best to provide a logcat from the reboot... after a nandroid backup of my OP3.

---------- Post added at 15:03 ---------- Previous post was at 14:57 ----------

[MENTION=1966251]Uqbar[/MENTION]

Thanx. Your build is an official LOS16 ... Right?

Setup OK .... First, perform a Nandroid backup before testing.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Only official builds here and no root and no custom kernel.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
This 16.0 is the best thing that could happen to my op3t. Thanks to OP.

ATM I cannot see bluetooth status in the status bar, no icon. I have it enabled to be shown in the stettings for the status bar. Is there more buried in the depths of the settings, which I have not found yet? Or is it an issue of the 16.0 waiting to be fixed later?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION]:

Please find enclosed the today's logcats (before and from reboot).
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Done.

It worked.

My 3T rebooted properly, asking (as usual) for a PIN for both SIMs and showing the expected SIM color.

With v15.1, instead, I had random issues with the PIN of my second SIM not being asked for or with the request being "overdrawn" by my phone password request.

But that's long gone since my very first v16 working build.

---------- Post added at 03:20 PM ---------- Previous post was at 03:19 PM ----------

I disagree. LOS v16 is the best thing that could happen to any 3T after CM. :D
[OnePlus 3 & 3T Cross Device Development] :
So called feature of pie: icon shows up, only if an device is connected. It's not showing up as soon as activated.

[MENTION=9350973]All[/MENTION]: if anybody has a link to changes restoring pre-pie behaviour, I'd highly appriciate!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Many thanks [MENTION=1966251]Uqbar[/MENTION] !

My config is: OnePlus 3T / FW 5.0.8 / TWRP 3.2.3-10 / f2fs cache & data / official LOS 16.1 / encrypted data

and yours, please?

Another question: does OTA updater work for you?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
BT icon works fine (i.e. device connected, icon displayed) on my side.
[OnePlus 3 & 3T Cross Device Development] sfoslino:
Thank you. If I connect to my Amazfit Bip, that results in NO icon if connected (connection is driven thru gadgetbridge). Made a test and connected right after your answer to a soundbox and had an icon. As far as I can remember, there was no icon too with a connection to another device that was driven thru a 3rd party app. But I cannot test it atm, but will do it later.

There is always some kind of mystery in every software, some infidels may call it bugs. ;)
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Pretty the same. I am not sure I am on f2fs, though.

I don't use ota: I manually download packages, reboot to recovery and flash manually.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Many thanks.

Please, could you check the cache/data format via Disk Info (https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=fr)?
[OnePlus 3 & 3T Cross Device Development] Syssx:
[MENTION=5091734]dianlujitao[/MENTION]

A lot of people are complaining about the OTA nott working also on Reddit - https://old.reddit.com/r/LineageOS/...pdates_on_oneplus_3t/?st=jtizzdc1&sh=8b24e651

Should someone of us just go, and create an issue on github issue tracker? Maybe [MENTION=9708417]Eric_Lev[/MENTION] you could try and create it, since you have logs. Link to LOS issue tracker: https://gitlab.com/LineageOS/issues/android/issues
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=4405529]nvertigo67[/MENTION] and [MENTION=9350973]All[/MENTION]:

About OTA updater:

I performed a clean install (full wipe and cache & data on f2s) from scratch with 0319 build.

Today, I made a Nandroid backup to give you the two logs about symbol color issue of SIM card.

In order to check again the issue of OTA updater, I performed a full wipe (but now cache & data on ext4) and then restored my Nandroid backup.

Miracle: OTA updater now works very well.

In sum up: OTA updater fails on f2fs and works on ext4 … but I do not know why !

Reminder the post of Bill Goss:

==> https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79070328#post79070328

[MENTION=5396529]Syssx[/MENTION]:

About creating an issue on github issue tracker, [MENTION=4405529]nvertigo67[/MENTION] is more competent than I am to do this.

PS1: the symbol color issue of SIM card also occurs on ext4.

PS2: enclosed the previous log of OTA updater on f2s (dated March 11 - see line 585).
[OnePlus 3 & 3T Cross Device Development] Calum 2:
My system is ext4 and my data partition is f2fs. (I have no idea why they're different, I don't remember ever formating the system partition, I thought these shipped with f2fs from 1+...?)

I'm running 5.0.8 version of firmware, yesterday's build of LOS, and TWRP 3.2.3.1.

OTA isn't working here either.

Question the second: formating data will wipe all media on the phone, correct?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The system partition is shipped as ext4. It would never befit from f2fs as it's read only.
[OnePlus 3 & 3T Cross Device Development] skythian:
Download link won't work anymore?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I also get a 404 for the link I in the OP.

Use this: https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
[OnePlus 3 & 3T Cross Device Development] hauckk@sfreserves.org:
I used latest gcam mod by skulshady and it worked
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Fixed, copypasta error
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, pasta will really make a mess of things! :laugh:
[OnePlus 3 & 3T Cross Device Development] pharandeamit:
Any Random Freezes or System UI Crash on this ROM? and how's battery/ SOT on this ROM? Will try today... Thanks
[OnePlus 3 & 3T Cross Device Development] Playa82:
Another "dumb" question. Can i install it over official 15.1 when i only wipe System ? Same steps as from 14.1 to 15.1
[OnePlus 3 & 3T Cross Device Development] legendavey:
Instructions from the OP text:

Installation:

First time flashing LineageOS 16.0 on your device, or coming from another ROM?

Download the zip(s)

Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)

Perform a nandroid backup of your current ROM (Optional)

Wipe data/factory reset

Flash LineageOS

Optional: Install the Google Apps addon package

Reboot

You can try anything else and it *might* work, but these are the recommended steps to get a functioning system without any bugs. I wiped system, data and caches. No issues for about a week now. :)
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Since it will be a Oreo > Pie jump, i would suggest a clean flash. You can later restore apps using your preferred backup app but i would suggest a clean system for this OS jump. Also, this LOS 16 is still in alpha so one more reason to start fresh.
[OnePlus 3 & 3T Cross Device Development] Dirk:
It seems like the 'latest' TWRP (3.2.3-1) will have problems with Encryption is Data is Formatted using it:

So to avoid problems 3.2.3-0 would be better.

---------- Post added at 14:57 ---------- Previous post was at 14:53 ----------

Beta officially, but i agree, any jump to a new version should get a clean install. :good:
[OnePlus 3 & 3T Cross Device Development] :
TWRP (3.2.3-1): Decryption data (ext4) is working fine for me
[OnePlus 3 & 3T Cross Device Development] Dirk:
It already says that in the post i quoted:

The problem, it seems, is Encryption won't work. Perhaps you should read the post again?
[OnePlus 3 & 3T Cross Device Development] :
Yep, you're right: I've overseen it
[OnePlus 3 & 3T Cross Device Development] Dirk:
For anyone flashing a ROM for the first time this must all seem really confusing. They're told "use the latest TWRP" but then it won't Encrypt if they Format Data? I think 3.2.3-1 should be pulled until this is fixed. Especially as in all the other Pie Threads people are repeatedly told to Format Data to install.

Bottom line i guess is to stick to to 3.2.3-0?
[OnePlus 3 & 3T Cross Device Development] Playa82:
Ok. But i want to save the data wipe. Every new start is a pain...
[OnePlus 3 & 3T Cross Device Development] :
It's not about decrypting. It's about formating data and reencrypting from the rom. This is not possible with 3.2.3-1, as [MENTION=5091734]dianlujitao[/MENTION] explains here: https://xdaforums.com/oneplus-3/one...h-recovery-t3742894/post78324758#post78324758 and all followups.

---------- Post added at 19:49 ---------- Previous post was at 19:46 ----------

As said: try, if it works without any issues you are good to go, if you encounter issues, clean flash and reproduce beforegetting logs for an issue report.
[OnePlus 3 & 3T Cross Device Development] helderfp:
Hows the rom in terms of performance and battery life?
[OnePlus 3 & 3T Cross Device Development] MrKartupelis:
I'm experiencing Android Setup crashes on first boot with Magisk + latest OpenGApps. Anyone had this issue before?:confused:

I also get same connectivity setup screens over and over before crash happens.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Same here, but this works after a few tries later
[OnePlus 3 & 3T Cross Device Development] MrKartupelis:
I installed ROM and Gapps in seperate boots and that did work.

Unfortunately now i'm trying to make ambient display work :confused:
[OnePlus 3 & 3T Cross Device Development] :
op3/t is shipped with system as ext4 and data as f2fs. You don't remember, because you havn't done that.

For the second question: absolutly yes.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About OTA updater fails:

Reminder: op3/t is shipped with system as ext4 and data as f2fs.

See this post: https://xdaforums.com/showpost.php?p=79170200&postcount=1382

Based on several tests, it seems OTA updater fails on f2fs and works on ext4:

See this post: https://xdaforums.com/showpost.php?p=79169667&postcount=1379

If OTA updater fails, 3 alternatives:

1- Manual update in recovery

2- Automatic update via Lineage Downloader (app Play Store)

3- Automatic updater via OTA updater but before starting Updater switch to permissive selinux (adb shell su -c "setenforce 0" or "su 0 setenforce 0" via a terminal app).

See this post: https://xdaforums.com/showpost.php?p=79098332&postcount=1171

Credits: [MENTION=4405529]nvertigo67[/MENTION] and [MENTION=2911853]BillGoss[/MENTION] ... Many thanks!!!

To switch from f2fs to ext4 (if wished):

First:

Perform a Nandroid backup (via recovery of course)

Optional: perform a backup of your app (e.g. via Migrate – app Play Store) but root is required.

Copy the entire External storage to your computer

Boot in recovery

Format all partitions in ext4 format (via Wipe … Advanced Wipe)

Reboot recovery

Alternative A: "dirty install"

Copy "/TWRP" directory of your PC backup to External Storage

Restore your Nandroid backup

Reboot System

Reboot Recovery

Copy the entire PC backup to External Storage

Reboot System

Alternative B: "clean install"

Download the zip(s) and copy to External storage

Install the last build + gapp + SU (if needed – official LOS SU or Magisk).

Reboot System

Optional: restore your app backup

Enjoy … Hope so!

[MENTION=5396529]Syssx[/MENTION]:

About creating an issue on github issue tracker, [MENTION=4405529]nvertigo67[/MENTION] is more competent than I am to do this.
[OnePlus 3 & 3T Cross Device Development] Syssx:
I'll just tag [MENTION=5091734]dianlujitao[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION], it finally looks like the culprit of OTA updater failing is indeed F2FS. Logs of it are attached to this post: https://xdaforums.com/showpost.php?p=79169667&postcount=1379

Personally I don't know a lot about fixing stuff like 90% of people here on XDA so we rely on you guys. Kudos for this.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Thank you for the great write up.

The thread for Migrate, here on XDA, states that it has issues with LOS SU. Would you still recommend it?

I think I'll check out the LOS play store app, that sounds like the easiest way to go.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No issue with official LOS su. I use it... but it's off topic, isn't it?

Reminder: All of us really need to follow the XDA rules and keep this thread development related only. There are specific sections dedicated to help and support for discussions and questions like these.
[OnePlus 3 & 3T Cross Device Development] :
I think his question is related and not off topic. The problem is you are talking of different topics:

[MENTION=6911010]Calum 2[/MENTION] is talking of migration (aka migrating from 15.1 -> 16.0), your awesome writeup (and since [MENTION=6911010]Calum 2[/MENTION] quoted this your answer) is about updating and automatic flashing.

Question for LOS Downloader: if you automaically flashing an update when on f2fs encrypted with secured boot, is twrp asking for a passphrase?
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Maybe it's just very slow, as detailed here https://xdaforums.com/showpost.php?p=77220579&postcount=3361j for LOS15.1