yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Regarding TWRP, POB, And changing FS:

TWRP/LOS keep asking earlier POB even when no POB set up in the os after it boots if you only change FS (without format data) with earlier FS on POB (my case was EXT4 to F2FS).

I haven't tried to set a new POB, does it overwrite the old or just become conflicted? Is it a bug or a feature?

Well it would be better if it remove the earlier POB when changing FS since changing FS removes all data including internal storage.

With the current way, my time is wasted because of encrypting /data back...

Step to reproduce:

You're on EXT4 with POB, then you reboot into TWRP and change your FS by selecting Wipe>Advanced wipe>Tick data>Change fs>Pick f2fs>Confirm

Flash your rom and reboot. You should now greeted with your old POB.

Things to try after booting into the OS:

Set up with no security - reboot and see if it still ask your old POB

Set up with a new security POB - reboot and see if it ask your new POB instead the old one (The POB should be different between the new and the old)

If something funny happen, you just have to use format data option in TWRP.

Also 1 more i have in mind, if you backup your current ROM with POB activated, reboot back to system and remove your POB, reboot back to TWRP and wipe everything, and then restore your backup,

Does it succeed along with your POB restored?

I'll leave this issue (feature?) to you guys posted at TWRP thread..........
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The reason your POB (which I take to be password on boot) remains after changing fs format is because the menu options (see screenshot):

- Advanced Wipe will reformat /data to the desired format without losing encryption

- Format Data will reformat /data to ext4 and removes encryption

See the discussion/testing in https://xdaforums.com/oneplus-3/one...ial-twrp-touch-recovery-t3742894/post78334783
[OnePlus 3 & 3T Cross Device Development] :
Yes. i already knew it based on your earlier post.

I'm just wondering now why can't we have a POB removed while still retraining an encryption with advanced format option.

If it's for security measure, then there is no risk at all since changing FS via advanced format also wiped internal storage.

It also raise an interesting questions for me about this POB (which i've not tested yet);

1. What if i add a new POB after that situation?

2. Does POB included in the TWRP backup?

There is 1 more interesting problem in my case, in my latest TWRP backup which it succesfully restored/booted after the testing, it doesn't accept my previous lockscreen password which i'm sure it's correct (luckly i don't use POB). I have to delete lockscreen.db things to finally unlock my phone..

That situation is really scared me when testing things, what if i happen to backup a system with POB enable? Will it carries the POB and accept my password? Since we know with POB, we can't access our data if the password is not accepted.

That is the concern i tried to raise here. If the backup/restore/format etc around POB is still broken, we shouldn't recommend it to anyone for enabling it yet.

It carries a greater data losses rather than a security risk since we are in the

Custom Rom zone

which carried a risk that tomorrow something might be broken.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
TWRP backups do not include the data partition encryption info - they do a file-based backup of /data. So, you'll never clear or set the POB using TWRP backups.

My experience is that of you can only restore a data backup without deleting the lock screen password if you've not wiped /data nor set the lock screen password (including setting it to the same password) since the backup was taken.
[OnePlus 3 & 3T Cross Device Development] :
In my latest restored backup, i'm sure i wiped everything first.. even checking the FS is the same as my backup.

So yeah, this is a lesson for me later when i want to do a TWRP backup, bettter clear any security things first :laugh:
[OnePlus 3 & 3T Cross Device Development] :
Definetly NO!

If you use TWRP-Home->Wipe->format data it will be formated to ext4, no matter which fs is currently on userdata.

It's explained in the twrp thread. Also: read the console output of the actions you take in twrp. If you are formatting with TWRP-Home->Wipe->format data the output clearly states that userdata is formated with ext4. Reading helps!
[OnePlus 3 & 3T Cross Device Development] :
Yeah, so it's instead EXT4 with /data decrypted....

We all can agreed to blame F2FS for the OTA failed
[OnePlus 3 & 3T Cross Device Development] :
Definetly not! It's not the fault of f2fs or the f2fs implementation, but just missing sepolicy rules.

Since file operations (like create, getattr or xattr) and encryption are implememted differently in ext4 and f2fs, it's not surprising, that the fses needs differnt sepolicy rules. (See system/sepolicy: there are many differnt rules for ext4 and f2fs)

The problem is that f2fs is shipped but not completely tested and supported by the rom.

Blaming f2fs for missing sepolicy rules is not really hitting the cause of the issue.

EDIT: if you read this thread, you'll find my modified bootimage (the two rules added), which proofes that these two rules definetly fix the autoflashing issue on encrypted f2fs.
[OnePlus 3 & 3T Cross Device Development] :
I'm not really good on this, so i can't really back and forth ideas with you on this. But have you considered another reasons?

I believe that's why it hasnt been merged. Because there is no problem on the other device.

The analogy is like - If your roof is leaked out, doesn't mean holding it with a tape fixed the problem. It just mean you temporarily fixed the leaked.

But if you kept it like that, the leaked may become a flood.
[OnePlus 3 & 3T Cross Device Development] :
Please read the thread. Your statememt is proofed to be false: there are other devices suffering from this.

Pointing out over and over the same and circling again and again back to allready known information by claiming proofed to be false statements made me not dealing with this issue anymore.
[OnePlus 3 & 3T Cross Device Development] :
All right chief, good luck then :p
[OnePlus 3 & 3T Cross Device Development] RoggaRolla:
Working very good so far, OP3.

Sound => Do Not Disturb => On (Slider on Middle DND Positon) => Notifications => No Sound from Notifications

Still getting sounds. Any ideas? Any unseen checkbox?
[OnePlus 3 & 3T Cross Device Development] Adept_Cain:
Hi, I'm unable to receive SMS on a clean install of LOS 16 from OOS. Australia, Vodafone, OP3T. Able to send SMS, send and receive calls and use data and wifi, just no SMS receiving. I've done some Googling and can't seem to find any solutions, any ideas?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
New official TWRP is out with several bug fixes merged so it became recommended again, for details check https://xdaforums.com/showpost.php?p=79351842&postcount=565

You can relock bootloader after flashing the new TWRP 3.3-1 as it's signed now, any ROMs(including latest lineage) with signed boot.img can boot with locked bootloader.

Btw, you can lock/unlock bootloader without losing data as long as TWRP is installed!
[OnePlus 3 & 3T Cross Device Development] Oyorf:
I have little problem with call volume with LOS16 and op3. So call volume is pretty low and hard to hear what other person is saying. I think this is software related as previously with oos volume was ok. Anybody knows any fix for this?
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Same here, on all three Oneplus 3:s. You can change this by changing some values in the mixer XML file, just wish this was default or that there was a Magisk module with better mixer values.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Have a look at https://xdaforums.com/oneplus-3t/help/low-call-volume-t3575675/post71499375
[OnePlus 3 & 3T Cross Device Development] NelMax:
Now blocked the bootloader, but after that the system did not accept the encryption password. Again unlocked the bootloader and the password was accepted. What could be the problem?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Clear password before locking
[OnePlus 3 & 3T Cross Device Development] Dirk:
Well, locking the Bootloader should at least solve the Safetynet issue!
[OnePlus 3 & 3T Cross Device Development] Naudiz:
I assume you cannot lock the bootloader, as long as you want to use root with Magisk, correct?
[OnePlus 3 & 3T Cross Device Development] :
Not quite sure: if the magisk installation routine resigns the reassembled boot image with the the aosp key, it should work. Probably worth a feature request for magisk.
[OnePlus 3 & 3T Cross Device Development] NelMax:
This did not help, after locking the bootloader, the system again asked for a password. :(
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
If you've not set up Password on Boot, you can simply delete the "gatekeeper.pattern.key" & "gatekeeper.password.key" files in /data/system.

It would remove the screen lock. ;)
[OnePlus 3 & 3T Cross Device Development] NelMax:
The screen lock is disabled, the phone start lock too. But after locking the bootloader, at startup, the phone asks for a password.
[OnePlus 3 & 3T Cross Device Development] :
The original question was about the encryption passwd:

https://xdaforums.com/showpost.php?p=79352546&postcount=1768
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Can I lock the Bootloader without formatting /data?

I thought it would always perform a factory reset if you un/lock the BL...
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Hmm I get it now... Didn't understand the issue earlier.

Oops sorry, my bad.
[OnePlus 3 & 3T Cross Device Development] :
Maybe that's the reason, why oos recovery always wipes (formats in this case) userdata on unlock/relock operations.

I think this conversation should be continued in the twrp thread - I'm pretty sure this is not rom specific and interesting for all users trying to relock the bootloader.
[OnePlus 3 & 3T Cross Device Development] hutsaniffo:
I'm on the most recent build. All of a sudden casting (to a Sonos device and to Google Home) via Spotify stopped working properly. Sometimes the streaming devices appear and sometimes they do not, when I try to connect sometimes it works and sometimes it does not. My device passes the safetynet test according to Magisk. I see the devices in the list, but I can not connect.
[OnePlus 3 & 3T Cross Device Development] 666biker:
has someone from you also an issue, that display has strange (grey) color after reboot?

I had this issue with latest unofficial release and still remains after clean install (official release 16042019).

It is possible to fix it somehow? thanks
[OnePlus 3 & 3T Cross Device Development] ufokomar:
yes support :)
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Today's build is up!
[OnePlus 3 & 3T Cross Device Development] legendavey:
SELINUX IS ENFORCING, YAY! Thank you [MENTION=5091734]dianlujitao[/MENTION], you legend! ❤
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
I'm afraid you can't just disable VoLTE on a Jio SIM. Jio is a 4G only network & calls are possible only via VoLTE or using their app to make calls. I myself use Jio 4G... However, I'm on OOS so don't know about fixing VoLTE on Pie actually.

Woah! Those screenshots are really making me jealous!

I also own a 3T & my SoT never really crosses 3 hrs 30 mins mark (atmost, 3 hrs 45 mins).

Can I ask how many apps you've installed on your 3T? And, what apps basically you use during your day? I used to get better battery with OOS N (around 4 hrs 30 mins to 5 hrs).

Even if I don't game, my usage won't go up the 3 hrs 45 mins mark :/
[OnePlus 3 & 3T Cross Device Development] legendavey:
VoLTE is now working on the LOS beta builds, so no worries there. :)
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Alrighty! :cowboy:

I'm actually still waiting for Xposed before moving to Pie :silly:

Till then, it's Oreo time for me ;)
[OnePlus 3 & 3T Cross Device Development] caryle:
It needs to install magisk manager app manually.

---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------

Amazing update!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've attached a file listing all my installed apps. The version numbers are out of date in the list as I keep them all up to date.

My most used apps are (in no particular order):

XDA Labs for the forums

Moon+ Reader Pro for reading books (my most used app)

Feedly for my news on Android (recently replaced Google+ as it's closing down next year)

Frost for Facebook

Chrome for web surfing

I have not enabled Google Assistant and I don't have any attached devices.

I'm nearly always in WiFi and have mobile data turned off.

I have my screen brightness set to adaptive and not very bright (I mostly use my phone indoors).

I have WiFi and BT scanning turned off.

I use Delta gapps because they are quite minimal. http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Just hit 4 SoT with 30% left. I am using latest Caesium kernel and some interactive governor tweaks.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
And here's mine :eek: :(

Installed apps list also attached.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Two things:

- I've found that games always drain the battery quite fast.

- The Facebook app also drains the battery, even when not in use. Which is why I use Frost https://xdaforums.com/android/apps-games/app-frost-facebook-t3685896
[OnePlus 3 & 3T Cross Device Development] Flounderist:
I have 59 apps installed, no gaming.

My average day is calls, text, web browsing and social. 2 sim running and device is most of the time using wi-fi.

Apart individual way of using the same device that may affect hugely the battery life, I was wondering if you clean flashed ROM on top of the previous builds and if device is encrypted. Also xposed could be the culprit.

I would avoid dirt flash or TiBu backups, when moving SDK version the best option is a fresh start.

Are you on latest (5.0.7) stable firmware?

If rooted, install any kernel manager app to find of CPU is going deep sleep on idle.

Give a try to some custom kernel as well. I would recommend Caesium.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Yeah, thinking to get rid of Facebook app for sure.

I don't even use Facebook now :eek:

I'm actually on OOS 5.0.7 ;)

Clean flashed it 2 days back. Tried BBS also but couldn't find which app was the culprit.

Today morning also I lost around 6% battery overnight.
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
Hopped into the beta builds ( BL 5.0.7 + LOS 16 5/12/18 + Open Gapps 6/12/18 + Magisk 17.3 + stock kernel)

So far stabe, no frills

Jio VoLTE is working now.

I have this permanent notification on the status bar that "SIM 1 is HD capable". Can't seem to get rid of it. VoLTE symbol on the status bar would be a good addition instead.

A bit of FCs during initial setup, but was able to complete it.

Default display size is a bit tiny. Not sure if its the proper default settings for oneplus 3.

No option to quick unlock immediately after entering PIN, without pressing OK button.

Everything works great! Thanks for your time & effort OP
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
Same. This was also an issue in the early-Pie ROMs but have already been fixed. [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Flounderist:
You are probably mining a lot of bitcoins for someone else

:D
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Lol... Uninstalled the FB app & also some other apps that I rarely used. Let's see if I see any improvement. ;)
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I uninstalled FB and i saw huge improvements in battery. That's definitely a step i would recommend for a better battery life.
[OnePlus 3 & 3T Cross Device Development] Flounderist:
I use a modded FB app with some debloating works on it. Search for Facebook LC in XDA. Same for messenger.
[OnePlus 3 & 3T Cross Device Development] legendavey:
All stock
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Can you check if "Reduce Power Consumption" is enabled in Settings > Display > Live Display? (Only if I remember the correct path).

Please turn it off if it's turned on.
[OnePlus 3 & 3T Cross Device Development] 666biker:
It was turned on, but after restart again same "strange" colors after turning it off.

I am using DCI-P3 color profile.

Can be also because of I am using Substratum with Root?

Exist also some different way how to have black theme (I maean also for notification panel, dialer, ..and so on..) for AMOLED display?
[OnePlus 3 & 3T Cross Device Development] realtos:
i thought so too in the beginning until i used the notifiction popup from "take screenshot" and use SHARE and choose massage, then the pic is fine, but if i send inside the stock app its fussy

see attached pick, if I use the SHARE ( Del on pic ) and send the picture mms through that option the mms pic is perfect but not if i use the attach icon in the app.

can anyone test this on their phone to see if its like that?
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Confirmed - almost.

If I use the share function of a screenshot, everything is great. The screenshot i send is 222KB and the photo I receive is 222KB.

But if I manually attach the screenshot from inside the messaging app the result is a fussy pic of 40 KB.

But if I send myself a photo of 1.54 MB - the result is a 40KB fussy photo no matter how I send it.
[OnePlus 3 & 3T Cross Device Development] GTRanushka:
Interesting. Do you know what does this feature does? How does it reduce power consumption?
[OnePlus 3 & 3T Cross Device Development] himsin:
Btw oneplus has released official open beta for pie. No idea if firmware bug is fixed or not.

Edit: official post has a precondition written "Boot loader should be locked", so I guess firmware bug is still present and we won't be able to use the pie firmware for custom roms.
[OnePlus 3 & 3T Cross Device Development] cgirerd:
Account sync disabled and battery drain

Deleted, not relevant
[OnePlus 3 & 3T Cross Device Development] ireaper4592:
screen randomly goes off and comes back on ?
[OnePlus 3 & 3T Cross Device Development] soubhikmullick:
Wanted a quick update on current issues with the latest nightly. I am planning on upgrading to it, also would like to know how Pubg performs on this OS compared to OOS.
[OnePlus 3 & 3T Cross Device Development] sighunter:
no
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Has someone already tried the new pie firmware with LOS?
[OnePlus 3 & 3T Cross Device Development] :
Yes. See posting #2 or use thread search: https://xdaforums.com/search/thread/3866517?query=pie firmware
[OnePlus 3 & 3T Cross Device Development] Blamz:
tried to find a flashable zip of it but could not find.
[OnePlus 3 & 3T Cross Device Development] raphael.e:
Still exploring.. But seems to be working after flashing the firmware zip and the fingerprint removal script

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post79363202
[OnePlus 3 & 3T Cross Device Development] 19Gonzo82:
Could somebody please hint me the download folder for the OTA updates? I'll have to manually flash them as OTA doesn't work for me either.
[OnePlus 3 & 3T Cross Device Development] 19Gonzo82:
That's what I was looking for. But I don't have such a folder.

Edit: nvm. Found it. Had to use #root explorer though.
[OnePlus 3 & 3T Cross Device Development] S4turno:
You can also bookmark the download page, this way you don't have to navigate through folders on your phone:

https://download.lineageos.org/oneplus3
[OnePlus 3 & 3T Cross Device Development] immi803:
I clean flashed oos pie beta and after that clean flashed a custom rom and firmware is absolutely fine and working in peace, though i didn't tried LOS with pie firmware, for community sake (apology) ,I'm taking name of custom rom here, DU 13.1 works fine with pie firmware, unencrypted

Caution: backup your data before going to oos pie as it'll encrypt if you're unencrypted, luckily i didn't loose my data ,got encrypted on long first boot to oos, may be you're not that lucky ;)
[OnePlus 3 & 3T Cross Device Development] legendavey:
By waiting for Oneplus to fix a flaw in their firmware, we could be looking at a few weeks, or months. Or it's possible Oneplus doesn't care about it altogether and leaves it unfixed in the final release. So waiting for a fix may not result in anything after all.

Considering half the users on this forum including me regularly switch between ROMs and clean flash most of the time, I'd say taking a backup and flashing this firmware wouldn't be the end of the world. For those that are encrypted anyway.

I'd suggest going with the newer community beta firmware - a backup and a clean flash never hurt anyone, but that's just my 2¢. :)
[OnePlus 3 & 3T Cross Device Development] :
On pie firmware

What's the benefit of using the open beta pie firmware, currently? Everybody is talking of weather the fw bug is acceptable - but what's the actual benefit of flashing it? To make an educated decision weather to take the current fw drawback, one needs to know, which benefits the new fw has to offer.

Of course, nobody knows if and when OnePlus will fix the fw bug, but what benefit do we loose, if waiting for the non-beta release? Perhaps it's fixed by then...
[OnePlus 3 & 3T Cross Device Development] ZVNexus:
Also a funny bug I found. The bootloader unlock screen on pie firmware is wrong. Yes is no and no is yes.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Indeed! I also think we should wait until OnePlus 'disables' that bug. It's not a 'bug' from their side. It's intentional as they want people to test their Community Build as stock as possible. That's why they're forcing people to lock the bootloaders so that people give their feedback without any custom kernels or mods or even root. So, they should be 'fixing' this thing when the Stable build rolls out. And, maybe when the final Stable rolls out, it can happen that OnePlus again makes some changes to the FW & then the developers would again need to incorporate those new changes into the ROMs. So IMO, LOS should still be based on the OOS 5.0.8 firmware & not the Community Build Pie firmware.

But that's my opinion, ;) the devs surely know better than me...

But as an encrypted user, yes it takes a decent amount of time to backup & get your device running back up if internal storage is also to be wiped (atleast in my case as I have just 5 GB remaining out of my 64 GB 3T :p)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Because rainbows and unicorns my friend. Rainbows and unicorns. Also a button that when pressed, pours forth an unlimited stream of single malt Scotch from the Headphone Jack.
[OnePlus 3 & 3T Cross Device Development] bumbum.droid:
Wanted to report that a couple of days ago I migrated to official from unofficial without having to wipe (just changed keys and dirtyflashed) Thank you to ivanich for your post about the lineagos guide! I executed the script from my phone's terminal as my ADB connection wasn't working.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About pie firmware:

In French, we say: Il est urgent d'attendre... Perhaps in English, it is urgent to wait... :cool:
[OnePlus 3 & 3T Cross Device Development] theduke7:
May I ask which screen you mean?

The option on devolopers settings?
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
I suppose he means the one that pops on the screen when you type in the fastboot command. The volume buttons are used to select 'Yes' or 'No' if the user wants to lock/unlock the device.