yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20190627

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.3 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.3 firmware

Oneplus 3: OxygenOS 9.0.3 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.3. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.3 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.3 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.3 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 27 Jun 2019, 12:08:45 CEST / 27 Jun 2019, 10:08:45 UTC):

op3: Kill camera shim library — dianlujitao

op3: Address IFAA denial — dianlujitao

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Hi [MENTION=4405529]nvertigo67[/MENTION], yes, this was a brain-damaged, late-night decision with not enough reading / thinking. Fortunately within an hour or so, I had the phone running with the main stuff I needed today again (no music in the car is a no-go :D).
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Strange. My Bluetooth quick settings tile is gone after installing this build over the previous one (dirty flash).

Have not tried (yet) flashing the previous build to see if it would be back. Bluetooth is working, just the quick settings tile is gone (and not on the list of tiles that can be added).

Anyone else with the same issue?

Edit: phone reboot fixed it. Had to add the button to quick actions, but at least it was on the list of possible buttons. Strange.

Edit2: "quick action button" -> "quick settings tile" correction. Thanks Ingo.
[OnePlus 3 & 3T Cross Device Development] :
What are you talking about, dude? I have no "quick action button" for bt.

As far as I remember "quick action button" was replaced/enhanced/reworked by "floating button" back in kitkat times (or earlier?). It's something an app dev can make use of. An example would be the moveable button that appears on screen recording.

If you talk of "quick settings tile", I would suggest you call it "quick settings tile".

If we talk of the "quick settings tile", I would guess you havn't wiped dalvik and cache or you have one or more magisk modules installed and activated.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Will not write on XDA in a hurry during breakfast... x100 times ;)

I meant "quick setting tile".

I did wipe dalvik & cache.

I do have one Magisk module ("OnePlus 3/3T Front Camera Fix" for GoogleCam). I haven't thought it might have any relation to Bluetooth "quick setting tile".

Sorry and thanks.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (blobs & firmware: 9.0.4; maintainance)

Build 20190630

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.4 firmware

Oneplus 3: OxygenOS 9.0.4 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 30 Jun 2019, 13:28:14 CEST / 30 Jun 2019, 11:28:14 UTC):

NLOS: bring up OOS 9.0.4 blobs. — Nvertigo

op3/t: regenerate blobs from OxygenOS 9.0.4 (op3t zip). — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] Sbodezzi:
hi folks, i'm tryng to use this rom with microG but the "MicroG.zip" that i found gave me error 7 when i tried to install it.

i can't found any guide to install it. someone can help me please?
[OnePlus 3 & 3T Cross Device Development] bertino:
Maybe your file is corrupted. Try to redownload it. What microg zip are you using? There is no "official" microg installer zip. Also please ask in the appropiate thread for that installer.
[OnePlus 3 & 3T Cross Device Development] :
What's the message in thentwo or three lines before "Error 7"? Please post the recovery log from the "Error 7" flash. Can you give a link to the zip you are referimg to, please?

"Error 7" means asertation failed, you need to find out which asertation has failed and why.
[OnePlus 3 & 3T Cross Device Development] Sbodezzi:
Something like

Failed to start /system/build.prop file not found

If this is not enought i send you some picture of the error.

https://mega.nz/#!kBUzHYbB that is the microG.zip

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
Just the recovery log is sufficient.

/system/build.prop is only available, if system is mounted. I really need to see the zip (see below) amd the recovery log.

Guessing (and I hate to guess!!!) from this information: the zip is relying on busybox. twrp-3.3.x.x has removed busybox completely and only offers toybox. If the zip is using busybox to mount system, the mount will fail, system is not mounted, so build.prop can't be there. But let's look at the l9g and the zip before taking my guessing for a fact.

I can't open that link, it asks for "Entschlüsselungs-Code". Can you give me the source of the zip package (site, thread or whatever), please?
[OnePlus 3 & 3T Cross Device Development] Sbodezzi:
Your guess was right!

I flash twrp 3.2 and the flash goes perfect!

Try this link https://mega.nz/#!kBUzHYbB!vOn0Sw_ZUaRND3Yp5ZGtwRgRQAK7HfvDh3pLMJNKuFg

Sorry but I found this zip on telegram so I had to upload on mega.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] knpk13:
You mentioned you found the zip on telegram, no other details so I don't know how reliable your source was.

Try NanoDroid or the MicroGInstaller zips. They both have threads on XDA and I think the latter has a module on the magisk repo too. They're more reliable sources.

Btw try to provide logs and more details instead of letting people guess if you can, so they can help you better.
[OnePlus 3 & 3T Cross Device Development] :
I'm happy to hear it's working now.

Let me add some thoughts, though:

When guessing, I've meant fixing the zip (unpack, replace "busybox" with "toybox" [only occurs once] in updater-script, repack). Using an older twrp version will work, of course and obviously, but the risk to forget to reflash 3.3.1-0 before next update/backup/restore would be to high for me. Never forget: the highest risk for messing up a setup is between the ears of the user. Anyway, I've left this comment: https://github.com/NoGooLag/MicroG_Packs/issues/2

If issues with flashable zips show up it's important to read all output in the twrp console and save and check tne recovery log!!! (it's on the advanced page of twrp) The log would have clearly state something like "/sbin/busybox: command not found".

It's imporant to give sufficient information to identify the used package. "found this zip on telegram" is not sufficoent to identify the package. I've taken the information to find the git from updater script. Identifying the package is also important to tell if the package is trustworthy or not (see also the posting from [MENTION=7134312]knpk13[/MENTION]; he has some points).

Though I check every flashable zip before using it no matter of the source of the package, I completely agree that a xda thread, activly maintained and supported is a valid point in telling the qualoty of a package. If you read such a thread you also get valuable information on installing, setup, potential traps and hazards.

nandroid and logs: the two most important features of twrp.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (July security patch & maintainance)

Build 20190702

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.4 firmware

Oneplus 3: OxygenOS 9.0.4 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 2 Jul 2019, 15:38:06 CEST / 2 Jul 2019, 13:38:06 UTC):

Patch up to android-9.0.0_r44. — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] :
Recommended Setup

As you know I'm recommending locked bootloader and unmodded fw in the releasenotes, thoughmI'm using my device with an unlocked bl and the modded fw (https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

After two and a half weeks of following (and trying to fix) issues resulting from unmodded 9.0.x fw and/or locked bootloaders in the official los thread, I'm thinking of changing the recomendation, because I've exactly zero issues with the unlocked bootloader with modded fw. Magisk is working like charme, too.

Which setup are you using? Any issues? Does it make sense to change the recommendation? I really want to give the users the least annoying expirience...
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm on an unlocked BL and modded FW. Magisk 19.3. OP3T A3010. Encrypted data. TWRP-3.3.1-0.

No problems at all.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
The least annoying experience is indeed the modded firmware as you need quite some time to go locked. That too coming from someone who had the most issues with it until recently.

That said, i am unencrypted now and unlocked, so that makes life a little easier..
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I've been using your modded fw zip with official oos zip and I've zero issues. I really don't have time to wipe my entire device just to flash a ROM and your fw mod zip is a lifesaver.
[OnePlus 3 & 3T Cross Device Development] frov:
I upgraded to the new firmware yesterday and shortly thereafter also to the July 2nd NLOS.

Coming from an older NLOS of a month or so old, magisk 19.3, unlocked BL and not encrypted (I now see).

I used the modded FW, dirty flashed NLOS. Had to wait and reboot twice in between, because it gave some message and no launcher.

For rest, no issues at all. Happy user.

EDIT: oh, and upped to TWRP 3.3.1.0 (from DL.TWRP) before I did firmware and NLOS.
[OnePlus 3 & 3T Cross Device Development] xdam57733:
I cannot find advice of how to handle this very history of updates and after shooting myself in the foot when going from 5.0.8 to 9.0.3 firmware, I am going to ask:

My phone now has the unmodded 9.0.3, can I just flash the unmodded 9.0.4 firmware and ROM of 20190702 now? Or will that badly affect the encrypted data again?

I somehow do not expect the modded 9.0.4 to work properly now that the unmodded 9.0.3 is installed.

Thanks for your help.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yes. That's what I did. And I have encrypted data ext4, and an unlocked bootloader.
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Thanks, will do on the weekend then.
[OnePlus 3 & 3T Cross Device Development] 13THWARRI0R:
Well I m in unlocked BL and unmodded FW ... Will go locked... In future maybe ...
[OnePlus 3 & 3T Cross Device Development] itraceyou:
Is it normal to have "Mobile Network Standby" always on the number 1 of battery usage (show full device usage)?
[OnePlus 3 & 3T Cross Device Development] :
Depends on configuration, uage, signal strength and signal-noise ratio. Your screen shot doesn't look unlikely. I have wifi nearly always on, even when not connected to an ap:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (WireGuard: 20190702; maintainance)

Build 20190709

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.4 firmware

Oneplus 3: OxygenOS 9.0.4 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 9 Jul 2019, 09:48:53 CEST / 9 Jul 2019, 07:48:53 UTC):

WG: squash WireGuard-0.0.20190702. — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] undrwater:
Can someone please test a Tasker wifi tether task for me?

It's failing with a report that the device is blocking me from using this function and advising moving Tasker to /system/priv-app.

I'm not seeing that this is a typical problem, which is why I'm asking here.

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] :
Since tasker is a payed app, I'm out of testing.

Most people - like me - don't understand what to test: setup wifi tethering in tasker, activate wifi tethering by tasker or making tasker previleged and test one of the former... A detailed testing plan would be mandatoty here.

BTW: why is moving tasker to previleged apps for previleged access a problem as long as it works?
[OnePlus 3 & 3T Cross Device Development] skymera:
App-systemizer in Magisk can do this.
[OnePlus 3 & 3T Cross Device Development] undrwater:
Thanks... Those who use tasker will understand the request, it's a common and simple task for this app. I appreciate your input.

I will try this. I was hoping for some insight as well, since this is new behavior on tasker's part, and I've not seen other reports of the issue.

Thanks again!
[OnePlus 3 & 3T Cross Device Development] :
If you want my input, I need a detailed description and a log. That "Those who use tasker will understand the request", doesn't help to get my input - I guess it's either sepolicy, wrong android permission requesting/handling or the additional tile security on nlos.

What does the tasker devs say? Since it's a payed app, they have payed people doing professional support. I'm just a hobbiest with limited knowledge and limiled resources.
[OnePlus 3 & 3T Cross Device Development] undrwater:
I apologize [MENTION=4405529]nvertigo67[/MENTION], I wasn't attempting to be annoying, just asking if someone using tasker and this ROM was having a similar experience to mine.

Anyway, app systemizer worked and now tasker can start tethering.

Thanks for your attention!
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Hi [MENTION=4405529]nvertigo67[/MENTION]

I've been using your ROM for a while and I am impressed with the battery life.

Can you test this https://review.lineageos.org/q/topic:%22pie-onehandmode-tile%22 in the next build? I prefer to use hw keys over sw navbar (Burnin is a real prob on my phone) and the commits in the above topic may help us to use OneHandMode without activating the sw navbar.

I have tested this on my Moto E LTE and it works fine.
[OnePlus 3 & 3T Cross Device Development] :
I'll try to push a build today. I'm quite busy today, may be it's tommorow. Thanx for the heads up.
[OnePlus 3 & 3T Cross Device Development] :
New build with one-hand-mode-tile is up in the usual location. Announcement and Changelog (which is basically https://review.lineageos.org/q/topic:"pie-onehandmode-tile"+(status:open OR status:merged) ) follows later.
[OnePlus 3 & 3T Cross Device Development] Mr.LOVER:
does this rom have gcam with slowmo working?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Gcam is not included in the ROM. You can install any version of Gcam that works best for You.

---------- Post added at 03:50 PM ---------- Previous post was at 03:45 PM ----------

One Hand mode works great. Better than I expected (didn't expect that level of customization).

Note: to make it work, you first need to activate it in Settings->Display->Advanced :)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (one-hand-mode-tile & maintainance)

Build 20190715

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.4 firmware

Oneplus 3: OxygenOS 9.0.4 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 15 Jul 2019, 10:15:54 CEST / 15 Jul 2019, 08:15:54 UTC):

current.pick.sh: "pie-onehandmode-tile".

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE pending

FYI:

The room, my building host lives in, is that hot, that it's decides to crash after about 85% of building. Though I can wait for 15 min, power on the building host and finish the build, I don't like pushing such a "hot build"... Temperatures should drop the next days according to the weather forecast - hopefully I can supply a "cold build" on Sunday or Monday.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20190728

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.4 firmware

Oneplus 3: OxygenOS 9.0.4 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.4. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.4 blobs, but you don't need to reformat the userdata partition.

Oneplus 3T: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 28 Jul 2019, 09:48:44 CEST / 28 Jul 2019, 07:48:44 UTC):

Revert "NLOS: track our own packages/apps/Messaging." — Nvertigo

op3: Enable QC combo NLP — dianlujitao

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] djplus:
hey [MENTION=3456089]nvertigo[/MENTION] -

just wanted to let you know that the os is extremely smooth,

Trust says root access disabled inspite being rooted via magisk. can you suggest something ?
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79826596#post79826596
[OnePlus 3 & 3T Cross Device Development] djplus:
Thanks. Will Try.
[OnePlus 3 & 3T Cross Device Development] Tiggy_Drum:
Hi,

Just a question, did someone have the RCS working with this ROM ?

Thanks
[OnePlus 3 & 3T Cross Device Development] :
Ambiguous:

https://en.wikipedia.org/wiki/RCS

Just a thought: Why should anybody spend time to answer, if you don't spend the time to ask an understandable question?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
https://www.****************/2018/1...s-messaging-chat-feature-in-android-messages/

I'll help you with it. But no, no need to have those bels and whistles.
[OnePlus 3 & 3T Cross Device Development] Tiggy_Drum:
Sorry I thought that was simple to understand. I am talking about the Rich Communication Service, the new ''sms''.
[OnePlus 3 & 3T Cross Device Development] :
To my knowledge pie doesn't support the rcs api. It will be supported in q: https://android-review.googlesource.com/c/platform/frameworks/base/+/838794
[OnePlus 3 & 3T Cross Device Development] Tiggy_Drum:
Thanks for the answer, hope you will port Q on our devices, you made such a great ROM. Thanks for your time and your work ?
[OnePlus 3 & 3T Cross Device Development] :
Can you add this? Last time i tried the rom doesn't has it.

Want to try for another shot. If you don't mind ofc :p

And yes sorry for the lack of searching first in this thread if it exist, just rushing things as usual lol
[OnePlus 3 & 3T Cross Device Development] :
Good idea! Will be in the next build: https://github.com/nvertigo/android_frameworks_base/commit/48c64d12eff9c058e5c9325d224187889c622b96