yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
It's 9.0.1 with 5.0.8 bootloader and keymaster

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] pedritopl:
OP3T (A3010), 128Gb variant. Flashed the 9.0.2 firmware with 5.0.8 bootloader and keymaster and the build. Booted just fine :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Oof I just switched back to 5.0.8 firmware for the previous build. Flashed 9.0.2 firmware WITHOUT 5.0.8 bl and km, but while flashing the file, it said that 5.0.8 bl and km was getting flashed. Did you forget to change the text for the zip or is it the wrong file?

Since I'm reformatting anyway, do you currently recommend f2fs or ext4? I have to reformat both /data and /cache right? Also is journalling disabled on LOS and NLOS for ext4? I'm thinking of switching to f2fs after reading this post, and whatever other information I could find via Google, and considering that the Pixel 3 has switched to f2fs as well.

Update: Clean flash ext4, everything works. I used the original OOS 9.0.2 zip to get the firmware update just to be sure. Didn't like OOS so switched back to NLOS. But um.. the volume panel is back on the right side for some reason? I see they added new code for the expanded volume panel though, so that's nice. I've noticed this for a while now, not sure if it's normal; Every time the volume panel appears the bell icon on top flashes once.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Do you notice any differences in NLOS behaviour between 5.0.8 fw and 9.0.2 fw?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Not really. For a moment I thought my WiFi connection was smoother/more stable, but it was probably just a placebo effect :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Well, switching firmware without formatting data consistently resulted in the fingerprint scanner not working anymore lol. Other than that, didn't notice any difference.
[OnePlus 3 & 3T Cross Device Development] :
I've forgotten to delete the ui_print line from updater-script. I've just checked the containing files: the unmodded fw is the unmodded fw. You can trust the file names. I'll remove the wrong output line later today. Thanx for the heads up.

It's easy for cache: ext4 (even OOS is using ext4 on cache). A reboot after dalvik/cache wipe with f2fs on cache is about 10% longer then with ext4 on cache.

For userdata: I'm using f2fs with 15.1 and 16.0 without any issues. On the other hand, nlos uses los sources. If you look at something simple as the additional sepolicy rules for los ota on encrypted f2fs, you see that f2fs is not the most important priority for the los devs... In the end my recommendation hasn't changed: ext4, though f2fs should work as well.

We can have either the new expandable volume panel (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/244295 ) or the volume panel on the left side (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/236982 ) but not both at the same time.

The left side patch gets really ugly and complecated with the expanded panel (animation and order needs to be mirrored, which blew up the code in a way I don't like).

[MENTION=9350973]All[/MENTION]:

One or another. Just play with the expandable panel and let me know which one is prefered.

From a users point of view: no drawback (at least for most users, last native OnePlus pie blobs build hasn't worked for some people); no benefit. Vendor security patch level is 1st of May instead of 1st of November.

From a developers point of view: it's easier to keep track of the blobs, if they mostly come from one source then kanging pie blobs from (different) other msm8996 devices.

Conclusion: it's nice to use native OnePlus pie blobs, but not a mandatory big step.

Independently from the used blobs, I'm observing differences in throughput up to 20% with 5GHz ac (ap the only one on 5GHz)... So maybe more then placebo, but really observed - but not related to the blobs.

[MENTION=9350973]All[/MENTION]:

It would be great to have some feedback by users, suffering from broken ril, freezes and reboots on the last native OnePlus pie blobs build. Please mention if it hasn't worked - I don't keep track of names, configs and issues... ;) Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
Can someone check this issue reported here?

Please and thanks!

https://gitlab.com/LineageOS/issues/android/issues/764
[OnePlus 3 & 3T Cross Device Development] :
Crosspostings are bad manner!

BT works flawlessly for me with soundlink 2 and move bt pro.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
i would like to report that i am facing the same problem of ril not mounting with pie blob builds that i had with the previous pie builds with a dirty and clean flash.

i didn't have the command by heart and without any access to nearby wifi i was unable to look it up.

i need to by heart it or else i miss the window and it reboots. this is the exact same behavior like last time.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I saw in another thread that You're getting incredibly good SOT times because You use some heavy mods... Are you having those problems also on a clean flash without mods?
[OnePlus 3 & 3T Cross Device Development] :
Thanx fpr taking the time to test this build!

I've hoped this one https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/249157 would fix the ril issue. On the other hand: if that commit would fix something, the issue would have shown on all setups.

I'm still seeing no pattern for working/non-working devices/setups.

Out of desperation: I'm on A3003. Maybe it's working on A3003, but not for A3000 and A3010???
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm on a A3010 (3T 128Gb). All works fine.

No heavy mods. Just Magisk 19.2 with one module (YouTube vanced).

---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------

It's 1st of April on my setup.

I flashed the oxygenos-9.0.2-bl-km-5.0.8-firmware-3T.zip that You linked.

Did I miss something or You meant April instead of May?
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
For me it's working fine again, so it seems we have atleast a reproducible situation.

But that's not helpful in any way [emoji2369]

L

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] knpk13:
I can confirm its 1st April 2019. I flashed the official OOS zip.
[OnePlus 3 & 3T Cross Device Development] :
Ok. Desperation isn't as good for debugging as logic...

You are right: https://github.com/nvertigo/android_device_oneplus_oneplus3t/blob/pie-blobs/lineage_oneplus3.mk#L27

This matches OOS 9.0.2:

ingo@adler /usr/local/src/oxygenos $ grep ro.build.version.security_patch system/build.prop
ro.build.version.security_patch=2019-04-01
ingo@adler /usr/local/src/oxygenos $
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Having the panel on the left was nice and I got used to it, but the expandable panel gives more functionality, by sacrificing not-that-much IMHO.

Fine for me the way it is right now. I don't see reasons for You to invest long hours on this.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
yes i had done a clean flash test too. and the mods weren't heavy, just little tweaks that haven't conflicted with anything or each other as i have tested them extensively.

---------- Post added at 04:20 AM ---------- Previous post was at 04:16 AM ----------

i am on a a3003, 3t 128gb. i wished the same too when i was having this problem the last time around. but then i searched the thread and people with a3003 had it working..

edit: i am using a 4g volte isp, reliance jio to be exact. can anyone using that provider's sim or a volte protocol based isp in general tell if they are having an issue?

i do not have a regular 2g/3g provider's sim to test it..

edit2: i am running unencrypted since i had to reformat my entire data partion after the 16th may builds. i havent let oos encrypt my partions as i haven't flashed it in a long long time. [MENTION=7134312]knpk13[/MENTION] did you flash oos since we last faced the problem? if yes, then did it resolve the issue? can you highlight what steps need to be taken? i am asking as you didn't report problems this time around
[OnePlus 3 & 3T Cross Device Development] knpk13:
Resolve what issue? I didn't have any problems on either of the pie blobs based builds. Also I ran unencrypted for a long time for various irrelevant reasons. Decided to encrypt with NLOS yesterday though. Went fine.

Edit: Oh I see what you're asking. After flashing OOS I reformatted data again and flashed NLOS and encrypted on it. I reformatted data several times this week for testing, ext4, f2fs, Oreo firmware, pie firmware, encrypted, unencrypted, OOS, glassrom, NLOS. Finally settled on one setup lol. But yeah I didn't have any issues with RIL/sim cards with either of the pie blobs NLOS builds.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
sorry i misquoted you on the issue

i should've quoted, after a proper search, [MENTION=6789884]devilsworkshop[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Sytis:
Reporting on a A3003 3T 64GB with F2FS on both data and cache with encrypted userdata. Also using microg and Magisk 19.2. No issues whatsoever with the 9.0.1+5.0.8 build and also no issues with the 9.0.2+5.0.8 build. Thanks :good:
[OnePlus 3 & 3T Cross Device Development] :
Thought the same on added functionality first.

After some days of usage, I've come to the conclision, I'm not using the panel anymore: most of the time I'm only using the hardware keys. With panel on the left side, I use it to enable vibrate, silience, a larger volume step or starting the audio settings with my left thumb (as a right handeder I hold the device mostly with my left hand).

Since the expandable panel is back to the right side I've just not used it again.

The expanded panael looks absolutly great - but regarding real life usage I don't use the added functionality...

Let's wait for more comments.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I don't have a strong preference for either, but I'm slightly leaning towards expandable more than left as I remember using the feature heavily in Oreo. But I've gotten used to a non expandable panel on the left, so I don't really care, I'll get used to whatever is used. The things I really care about are already there in NLOS. One big example is a black substratum theme. I cannot live with this blinding white crap from Google. I could keep listing more reasons, but I'll cut it short and just say the that NLOS matches my philosophy of the perfect ROM. The only thing I would try to change right now is to get the normal LOS bootanimation again since it's more minimal and suits my taste, since after I encrypted, I noticed LiveBoot doesn't work before I enter the encryption password, it starts working after. I'm trying to find a magisk module to do that. Maybe I'll learn to build my own for it soon if I don't find one.
[OnePlus 3 & 3T Cross Device Development] :
If this refers to the bt icon: I absolutly disagree: since bt (if the sevice is visible, which you can't disable since 14.1) is quite prune to data stealing attacks, I alwaya want the bt icon visible if active - not only on swipe QS down.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I agree as well. If a hardware feature like wifi or Bluetooth or NFC is on, I want to be able to see it. This behavior seems to affect the NFC icon too. I didn't use NFC much on Oreo so idk if it was visible then though, like how Bluetooth was.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
There are things we agree, some things not. I would prefer shady icon, like rr roms has, when no connections available. But . Take or leave it. In case you know how to change that- you can always try ;)
[OnePlus 3 & 3T Cross Device Development] knpk13:
I see. I believe parts of Telegram are open source. But it seems to be happening on every messaging app I use. Whatsapp, SMS, Telegram, Discord, etc. That's why I thought it was an Android system error. I'll ask the developers of the apps why this is happening then. Thanks for pointing out the error in the log.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is the style for black and dark themes in display settings a LOS feature or an AOSP Pie feature? I can't tell since I don't have any device that runs AOSP Pie.
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Is firmware 5.0.8 also for op3? or just for op3T?
[OnePlus 3 & 3T Cross Device Development] knpk13:
OOS 5.0.8 is the latest for both models. But the firmware differs, so make sure to flash the one for your model, depending on whether it's an OP3 or OP3T. OP only has a link to 3T firmware last I checked, but you can find a link to 3 firmware on the forums.
[OnePlus 3 & 3T Cross Device Development] :
Couldn't have explained better.

The download for 3 fw I've linked in earlier builds (NLOS-15.1 thread), seems to be out of the game. If anybody has a oos 5.0.8 fw thread/download, please drop me a note, and I'll add it to OP.

It's los specific: https://review.lineageos.org/q/topic:"pie-styles"+(status:open OR status:merged)

Introduced in 15.1: https://review.lineageos.org/q/topic:"berry"+(status:open OR status:merged) .
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Well, guys, must admit, this rom is fantastic. Upgraded today from nlos15 to 16 simply clearing the system, dalvic and cache. Installed on top with opengapps nano and magisk afterwards. Zero glitches, fc's or other noncences. Playing already maybe for last 2 hours - no issues at all. Yes, those nfc and bt icons are hidden while not in use - but I'm not complaining. Developers from Google are working hard, [MENTION=4405529]nvertigo67[/MENTION] even harder to make rom safe as possible. Plus those services on background doesn't take too much battery, we won't safe the planet while turning off bt for rest of the day.

Happy to say, that decided to walk with 3t until it reaches slowly death or fast crash. 5t will wait in drawer for better days, like [MENTION=1763460]Dirk[/MENTION] was talking about. To say the truth, native oos on 5t makes me feel like a fool with strange decisions. But gestures are fantastic, reminds me good old days with blackberry z10, later z30. Happy days :) Another thing, to busy right now looking for another less annoying custom rom, plus, after last update, 5t become treble friendly. That makes even funnier story while playing with custom features. Maybe some day will play with it.

Regards, happy user.

---------- Post added at 12:41 PM ---------- Previous post was at 12:24 PM ----------

Wow, just had a strange falling down from the chair! Decided to listen Spotify in background and bang - huge earpiece "stereo" effect blown me away! Really happy to find out, that 2€ cents size earpiece is capable to have such output! On nlos15 it was way lower.

That made me feel more "in love" with this rom. Thank you.
[OnePlus 3 & 3T Cross Device Development] knpk13:
https://xdaforums.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628/post77384418

There's a new thread and a mirror linked in the post. (For both 3 and 3T)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
How about this one? [MENTION=4405529]nvertigo67[/MENTION]

I'm using the firmwares provided in that thread since a few months without any problems.

Edit: oh, but those are 3T only...

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166
[OnePlus 3 & 3T Cross Device Development] Mata99:
[MENTION=4405529]nvertigo67[/MENTION] what do you think about this commit?

"github.com/nitrogen-project/android_device_oneplus_oneplus3/commit/3c19eb345c4055af42771ee865abf6ed92b6a5e4"

(sorry for how I wrote url but otherwise xda blocks post)
[OnePlus 3 & 3T Cross Device Development] :
Makes sense to me to have the volume panel at the volume keys.

The overlay commit relays on this SystemUI patch: https://github.com/nitrogen-project...mmit/e69193f2b375d4cc8d434157d3ceea26f54f0ac3

It was pure luck I was able to find that easily. Since NOS doesn't have gerrit it's normally much harder to find ALL needed commits there. Please always try to list all patches necessary, when suggesting something from a gerrit-less rom.

Volume panel on the left side will be in the next build. Nice idea!
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Some fresh user questions about Status bar icons, but from other side. How to ditch that lame LTE icon and return back to tiny and lovely 4g?

How to ditch that dot? I have no notch and want all my available icons back!

Dnd switch. Where only vibration gone? No haptic feedback at my side. Again dirty flash.

Edit: yes, notch we hate made that dot appear. And I'm forced to move clock to the left, just because of it. In this case we will save some pixels to have more icons. And the same notch is the answer of missing Bluetooth and nfc icons - it takes golden place, so why not to hide some icons, while those services are not used!

Sadly, at developer section, notch - we have no option to have NO NOTCH STATUS BAR :(

Regards.
[OnePlus 3 & 3T Cross Device Development] karkiankit:
love this rom, i have a question

1. Is there any way to make quick setting stretch from edge to edge ? like it was in oreo ? so that no space is wasted in both sides of my phone?

2. Any substratum them i can use to achieve that ? Personally i think QS in nougat was best till now in terms of looks.

3. Can i remove round corner elements from notification and from entore system ? like rectangular noticificatio like in oreo ?

Please share what you know.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I am positive substratum themes can be used to achieve all the effects you're looking for. However I'm personally happy with the design and I just use the swift black theme to make everything black, so I am not familiar with the themes you would want to use. You'll have to search for them on your own or wait for someone else to recommend specific themes, but I'm sure you'll find it easily, as I've seen those themes in the play store before.
[OnePlus 3 & 3T Cross Device Development] :
Tiny lte and lte+ are not very high on my priority list. In the 15.1 pr 14.1 thread I've explained, why I won't use 4g.

Standard means "device standard" which is in case of op3/t no notch.

I can't see any notch: center the clock, and you will see there is no notch.

The bt and nfc icon thingy is about the changed functionality - not about space consuming. The icons show up if something is connected.

[MENTION=9350973]All[/MENTION]:

I would like to ask everybody to stick to op before reporting issues. If you like to dirty flash on version bumb, use mods doing somthing not recommended, please do so. Before complaining about anything ot repprting an issue: clean flash with the absolute minimum of apps needed to reproduce the issue.
[OnePlus 3 & 3T Cross Device Development] Syssx:
In which case they show up? For example, I'm having my wear os watch connected to my phone,and the icon for BT isn't visible (I guess this is due to it using BT LE). And NFC icon should be visible all the time in my opinion, because you just don't "connect" it, it's ready to be used.

I've reported those (BT and NFC not visible in status bar) in LOS16 beta thread, but if they're not bugs and it's just Google being dumb, I'll take my response back.

Thanks.
[OnePlus 3 & 3T Cross Device Development] :
That's why I've asked a few üages back. It turns out, that the new icon behavior is intended by google and no bug in los or nlos but a pie "feature"... :(
[OnePlus 3 & 3T Cross Device Development] Master_TC:
[MENTION=4405529]nvertigo67[/MENTION]

The new icon behavior is a pie "feature". The behavior is on all pie roms i have tested...

Stupid question: what is the difference of your rom and LOS 16 beta? is your rom linux permissive too?
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7134312]knpk13[/MENTION]:

For the bootanimation: the "normal" user should see the bootanimation only once after update. I think I can claim I'm seeing the bootanimation most often - and I like it the way it is... ;) Copying an other is really easy.

I've stoped using liveboot quite some time ago (back then it doesn't work with addonsu or Magisk). So take the following with a grind of salt: since liveboot is installed as userapp (in userdata, not in system), userdata needs to be mounted for liveboot to work. This can only happen, if the secured boot passphrase is given. Perhaps you can move it to /system/app (or /system/priv-app, though I don't think it's needed to make it an previleged app) and it will (hopefully) start working earlier.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Just wanted to remind about this old post related to the current "Phone is starting" discussion.

In my case, that was the one and only occurrence of this bug. Right after flashing the modified 9.0.1 firmware (with 5.0.8 elements) and the 20190516 build.

As the possible Launcher workaround and/or influence was mentioned - for the sake of completeness, I use Nova.

Regarding the workaround of switching the screen off for 10s - I'm sure I waited much more (several minutes), but not 100% sure if with screen off. Kind of 80% sure the screen was off for a few seconds at least (and it didn't help).

This problem never ever appeared on my phone before or after. Even after flashing the 9.0.2 (+5.0.8 elements) firmware.
[OnePlus 3 & 3T Cross Device Development] :
Let's discuss the PIS isuue in the los thread - the SNR on this topic is bad enough without discussing it in two places. Thanx anyway.
[OnePlus 3 & 3T Cross Device Development] Ormad:
Hello, is anyone experiencing issues with assistant? I tried both 26 and 30 may build and can't activate voice Match. It can be toggled and asks and register voice for 4 times but it gets again toggled to off just after ?

Am I missing something? Thanks!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (June Security Patch; Kernel: WireGuard-20190601; New Backgrounds app)

Build 20190604

Releasenotes:

NLOS-16.0 relies on OxygenOS firmware. OxygenOS 5.0.8 firmware is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

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

Changelog (Last repo sync: 4 Jun 2019, 17:31:15 CEST / 4 Jun 2019, 15:31:15 UTC):

Revert "Revert "current.pick.sh: remove pie-battery-styles."" — Nvertigo

Revert "current.pick.sh: rewrite pie-battery-styles picking." — Nvertigo

Patch up to android-9.0.0_r40. — Nvertigo

NLOS: track our own packages/apps/Backgrounds. — Nvertigo

Revert "NLOS: bring back NLOSWallpaperPicker." — Nvertigo

current.pick.sh: remove picking webview. — Nvertigo

Revert "current.pick.sh: "SystemUI: Enable and fix QS detail view, adapt layout to Pie"." — Nvertigo

Revert "current.pick.sh: "SystemUI: Advanced location tile"." — Nvertigo

Revert "current.pick.sh: "SystemUI: Add Profiles tile"." — Nvertigo

Revert "current.pick.sh: "SystemUI: Fix several layout bugs"." — Nvertigo

Revert "current.pick.sh: "SystemUI: allow devices override audio panel location"." — Nvertigo

Revert "op3/t: overlay: Relocate volume dialog to the left side." — Nvertigo

WG: squash WireGuard-0.0.20190601. — 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] pedritopl:
Is it safe to dirty flash this over the "Native Pie Blobs build 20190530" (after downgrading the firmware to 5.0.8) or should I rather wait for another 9.0.2 Blobs based alpha build (if there will be another one)? :)
[OnePlus 3 & 3T Cross Device Development] :
It's what I did. Downgrade fw (from modded 9.0.2 to 5.0.8); reboot to recovery before flashing the rom.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Thanks. Proceeding to flash then :)