yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
I havn't known there's a trial version. The attached screenshots show my tests with an old S3 3.5mm jack headset an a flac file (FLAC audio bitstream data, 16 bit, stereo, 44.1 kHz).

Have you tried deleting cache, or - if that alone doesn't help - deleting data from poweramp.

BTW: with this lowend headset opensl output sounds much richer (more treble, much more bass) then Hi-Res Audio for me. With bt (Teufel Move BT, aptx) I can hear no difgerence between opensl and Hi-Res. But this is only my perception and taste, of course.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
yes, cleared data as well. And you are right, sound output is much great with opensl than hi-res which is just the opposite in stock. Nevermind, I'm ok with it. :good:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (bring back AudioFX; remove wakelock blocker)

Build 20190928

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

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

Oneplus 3: OxygenOS 9.0.5 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 Sep 2019, 10:38:30 CEST / 28 Sep 2019, 08:38:30 UTC):

Revert "Remove AudioFX." — Nvertigo

op3/t: sepolicy: fix some more denials. — Nvertigo

op3/t: sepolicy: fix order and comments (cosmetics) — Nvertigo

Revert "boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0" — Nvertigo (*)

Revert "boeffla_wl_blocker: update to wakelock blocker driver v1.0.1" — Nvertigo (*)

Revert "boeffla_wl_blocker: update to wakelock blocker driver v1.1.0" — Nvertigo (*)

Revert "wl_blocker: add more wakelocks to the default block list" — Nvertigo (*)

Revert "boeffla_wl_blocker: fix LENGTH_LIST_WL_DEFAULT size." — Nvertigo (*)

Revert "op3/t: defconfig: enable CONFIG_BOEFFLA_WL_BLOCKER." — Nvertigo (*)

WG: squash WireGuard-0.0.20190913. — Nvertigo (Note: has been in 0920 already - forgotten in 0920 changelog)

(*) I've tested myself without wakelock blocker after the los kernel rebase. I don't think it's needed anymore.

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] Private_goose:
Haven`t been in a custom rom game for a while, so i have some dumb questions. I followed the first install instruction and ended up with unencrypted data. Is it supposed to be like that, or is it because i flashed magisk before booting into system for the first time?

And how do i encrypt data? Option in settings>security>encryption?
[OnePlus 3 & 3T Cross Device Development] knpk13:
This ROM does not force encryption. Neither does Magisk. And yes, that's where encryption is in the settings. Make a backup and charge your battery before you start the process.
[OnePlus 3 & 3T Cross Device Development] :
Yes, of course it's intended! The OP reads:

"Optional (mandatory, if you have issues with encryption): Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4"

As stated this step is optional and only mandatory if you expirence issues with encrypted data (like passphrase accepted, but data corupted, or passphrase is not exepted at all). If you decode to format data, encryption is removed, as stated in OP.

No.It's because you've formated data - see OP.

Yes. As [MENTION=7134312]knpk13[/MENTION] said: get a backup before encrypting, though I don't expect any trouble with encrypting.
[OnePlus 3 & 3T Cross Device Development] :
Passing safetynet api

A new build (with basically just the build fingerprint updated to the one from OOS 9.0.5) is up in the usual location. Announcement follows later.

I've added a guide and zips for passing safetynet in posting #3.

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (build fingerprint from 9.0.5; maintainance)

Build 20191004

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

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

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

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

Changelog (Last repo sync: 4 Okt 2019, 10:25:01 CEST / 4 Okt 2019, 08:25:01 UTC):

op3: Move libnfc-nxp_RF.conf to /vendor — dianlujitao

op3/t: update build fingerprint to OOS 9.0.5.

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] knpk13:
[MENTION=4405529]nvertigo67[/MENTION] What do you think about this? I was curious about this app. https://opensource.srlabs.de/projec...-on-custom-ROMs-like-CyanogenMod-or-LineageOS

I tried using SnoopSnitch a long time ago on NLOS and it complained about a missing DIAG driver (whatever that means). I tried it again and it still does.
[OnePlus 3 & 3T Cross Device Development] Zaphod_B_1:
I recently opened a seperate thread about it and [MENTION=4405529]nvertigo67[/MENTION] already tried to include the CHAR_DIAG driver into NLOS. Umfortunately it did not work. Would love to see Snoop Snitch working on NLOS.

Here is my thread: https://xdaforums.com/oneplus-3t/help/kernel-rom-available-diagnostic-t3953246

Edit: I even tried it with other ROMs (one OOS-based) and other Kernels, still no luck. Seems that Oneplus removed the Diagnostic part for the Qualcomm modem somewhere after OOS based on Android 7.1.1.

And as I was able to find out recently it seems that Cyanogenmod/LineageOS never had support for the driver built in.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Oct. Security Patch & mainainance)

Build 20191010

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

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

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

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

Changelog (Last repo sync: 10 Okt 2019, 10:53:12 CEST / 10 Okt 2019, 08:53:12 UTC):

Patch up: P_asb_2019-10. — 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] hellcat50:
Really love your rom, superb performance and you even fixed the slow 5 ghz bug (I mean, even the oneplus 7 pro on stock rom has this bug)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (long screenshot; screenshot qs tile; WireGuard: 20191012)

Build 20191013

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

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

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

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

Changelog (Last repo sync: 13 Okt 2019, 09:51:56 CEST / 13 Okt 2019, 07:51:56 UTC):

All credits for Long screenshot (aka scrolling screenshot or longshot) belongs to TeamMOKEE:

current.pick.sh: "Long screenshot". — Nvertigo

NLOS: track our own device/lineage/sepolicy. — Nvertigo

Add Longshot.apk — Nvertigo

SystemUI: tiles: Migrate to new screenshot method with Longshot support — XiNGRZ

SystemUI: tiles: Add screenshot tile — Martincz Gao

fwb: Port extended screenshot function from OOS (cleaned) — jhenrique09

NLOS: add TILE_SCREENSHOT logging const. — Nvertigo

Add rules for Long screenshot service — jhenrique09

WG: squash WireGuard-0.0.20191012. — 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:
Perfect! Thanks a lot for this addition :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
One question though - why jpg instead of png? I noticed now all screenshots (long or short) are saved as jpg instead of png as before.
[OnePlus 3 & 3T Cross Device Development] :
As you can see in this commit https://mokeedev.review/c/MoKee/android_frameworks_base/+/42050 we use the changed service for screenshots provided by the prebuilt Longshot app. The app seems to be kanged from pixelexpirience (perhaps modded from pixel gactory images). I don't know who and why it was decided to ise jpg, perhaps size and/or processing time, but in the end I've no clue at all. Since longshot app is closed source (for me), I'm not spending time on getting to the ground of this.
[OnePlus 3 & 3T Cross Device Development] knpk13:
What made you add this feature? It's extremely useful imo, so thanks to you and Mokee. I think OOS has a pretty polished version of it too but I haven't used it in so long so I don't remember. I wonder why it's not in stock LOS. Also, nice, it works pretty well. Don't think I can see any reduction in image quality in JPG compared to PNG for screenshots. There was one issue I noticed though, I can't delete (short) screenshots from the notification anymore, it doesn't work. Is it working for anyone else?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Works here.
[OnePlus 3 & 3T Cross Device Development] :
Really? As you know from my previous answers to feature requests, I'll add a feature if it doesn't break something else and if I can find all necessary patches...

Maybe it's not clear enough:

It's a basic difference, if you ask to add scrolling screen shot, or if you ask to add https://github.com/MoKee/android_frameworks_base/commit/971c799d8eb57f8873f15bddf0d1810ffc75abdd (which can't work, of course), from porting https://mokeedev.review/q/topic:%22longshot%22+branch:%5E.*mkp.*

I've no chance to find all needed commits on the first two requests, but when I found the topic in mokee's gerrit...

Absolutely.

Really? https://mokeedev.review/c/MoKee/android_frameworks_base/+/41960 changes the aosp default behaviour. See i.e. https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/239182 vs. https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/239179

Take a "normal" screenshot and a long screenshot and take a look at the logs: Longshot app fires a notification on "normal" (and "cutted") screenshots, but for long scteenshots there is no notification, but Longshot app starts gallery (or the dialog if no default app for pics is selected - btw: opgallery prefered by Longshot, but you can make any gallery the default).

Really? You get a notification for long screenshots?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
He asked for "(short)" screenshots... I even quoted the sentence where it's clearly visible the question refers to short screenshots.
[OnePlus 3 & 3T Cross Device Development] :
Of course. You're right. Brainlocked: I've taken "...delete (short)..." as notification shurtcut to delete... *lol*
[OnePlus 3 & 3T Cross Device Development] sinkoo1979:
Smooth Rom
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks for adding this great feature. I missed not having it after using OOS.
[OnePlus 3 & 3T Cross Device Development] pijen:
would you push/merge it to stock LOS? is it possible in the first place? i really missed that

thanks
[OnePlus 3 & 3T Cross Device Development] :
Stick to xda rule #1 and search/read before posting, please:

The 4th posting before your request explains why especially this commit https://github.com/nvertigo/android_frameworks_base/commit/33d447462cc5a5de60835efbfb116892ae106eee won't be accepted by los.
[OnePlus 3 & 3T Cross Device Development] pijen:
i did read your post, since i didn't really understand what it means, i just asked it whether it can be added to stock LOS or not

thanks :D
[OnePlus 3 & 3T Cross Device Development] Dirk:
[MENTION=4405529]nvertigo67[/MENTION]

Have you noticed that Android 10 ROMs all have an extra level of /system folder? So /system/build.prop has become /system/system/build.prop. /media, /app, /priv-app are all moved too. That's a lot of flashable zips, (including my own), that are not going to work as designed.

I've checked:

LOS & crDroid - OP5

crDroid - Poco

NitrogenOS - OP3/T

All the same new directory structure. Seems like it might be the new AOSP standard for Android 10.

Just a heads up in case you weren't aware, but it's a bit of a PITA, right?
[OnePlus 3 & 3T Cross Device Development] :
Thanx. The system as root **** is introduced with Android 10. I've assumed everybody using 10 roms is aware of this - but after reconsidering, I belive you are right. I've added

"For all system as root roms (Android 10 based roms) you need to adjust PROPFILE in META-INF/com/google/android/update-binary."

to #3.
[OnePlus 3 & 3T Cross Device Development] meiser:
Hi nvertigo67,

may I ask you to integrate the StopSwitch Delay patch to remove a delay mentioned in the XDA Navigation Gestures app thread?

The patch is for frameworks_base and is quite trivial:

diff --git a/services/core/java/com/android/server/am/ActivityManagerService.java b/services/core/java/com/android/server/am/ActivityManagerService.java
index eb9e84e27ca..60ed3a01fcb 100644
--- a/services/core/java/com/android/server/am/ActivityManagerService.java
+++ b/services/core/java/com/android/server/am/ActivityManagerService.java
@@ -574,7 +574,7 @@ public final class ActivityManagerService extends ActivityManagerNative

// Amount of time after a call to stopAppSwitches() during which we will
// prevent further untrusted switches from happening.
- static final long APP_SWITCH_DELAY_TIME = 5*1000;
+ static final long APP_SWITCH_DELAY_TIME = 0;

// How long we wait for a launched process to attach to the activity manager
// before we decide it's never going to come up for real.

Thanks in advance,

meiser
[OnePlus 3 & 3T Cross Device Development] :
I don't think it's a good idea. "static final long APP_SWITCH_DELAY_TIME = 5*1000;" is part of https://github.com/nvertigo/android_frameworks_base/commit/95fc68f24a2a.

If somebody thinks the 5s delay isn't necessary and regressing the fixed issue is less important then fixing a third party app on rom basis (which is systematically a bad idea!), the complete commit should be reverted.

In my oppinion, the fix is more important, then a workaround which reintroduces this issue in favour for a third party app.

If I find a timeslice for reading a thread of over 2600 posts, I'll look into. Sadly the thread search for APP_SWITCH_DELAY_TIME returns 2 postings (incl. the OP), but in both postings APP_SWITCH_DELAY_TIME can't be found.
[OnePlus 3 & 3T Cross Device Development] xuser_:
[MENTION=4405529]nvertigo67[/MENTION]

I have successfully upgraded to stock oos 9.0.5(without losing my oos oreo data and internal storage)

thanks to your post,

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Now, I am unrooted, unlocked bootloader and encrypted with latest official twrp

1- Flashing latest NLOS build will wipe my internal storage?

2. Is the latest fully rebased kernel any better than the previous one?

Optional,

Any Idea if franco's r50 kernel is rebased for oos pie?

Thanks!

---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------

[/COLOR [MENTION=4405529]nvertigo67[/MENTION]

I have successfully upgraded to stock oos 9.0.5(without losing my oos oreo data and internal storage)

thanks to your post,

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164

Now, I am unrooted, unlocked bootloader and encrypted with latest official twrp

1- Flashing latest NLOS build will wipe my internal storage?

2. Is the latest fully rebased kernel any better than the previous one?

Optional,

Any Idea if franco's r50 kernel is rebased for oos pie?

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
Just stick to the installation instructions in the OP: as long as you don't expirience any issues with encryption, no need to format data, just wiping data is sufficient.

Both worked flawlessly for me, I've noticed no difference in stability, performance and bat life. The same goes for the removal of boeffla's wake lock blocker. As you already know, no other user has reported any issues neither with the old kernel, nor with the rebased one.

Why do you ask? What is your problem with one of them?

Please respect OP.

What is your issue with the shipped kernels?
[OnePlus 3 & 3T Cross Device Development] xuser_:
>> No problem just wanted to know if

1. FK rebased kernel(if exists) for stock oos pie

2. there is any significant advantage of upgrading to stock oos kernel vs latest r50 FK kernel vs your fully rebased kernel

3. Is your rebased kernel compatible with the latest stock oos? if yes, could you please share the kernel as zip?

---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------

BTW OP does not talk about the 'internal storage' ( flashing from stock oos pie to NLOS pie)

6. Optional (mandatory, if you have issues with encryption): Format data: in twrp tap on wipe and then tap on format data. This will delete all data, remove encryption and leave you with ext4, which is highly recommended. If you are insisting to use f2fs see: https://xdaforums.com/one...9#post75688089 - NOT recommended!

so, if we have issues with encryption will format data format the internal storage as well?
[OnePlus 3 & 3T Cross Device Development] :
If you don't start respecting OP, I'll stop answering you!

OOS kernels and source build rom lernels aren't compatible to each other, never has been and (to my understanding) never will be.

If you don't understand, that my answer as well as the directions in OP answers your question for "internal storage" bijectively and sufficiently, that means that you don't know, that wiping data in twrp doesn't touch media and formatting data cleans the complete data partition. If that is the case, I strongly recommend to learn about twrp, before using it.

I've answered that already.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
You really have no clue that OOS Pie and NLOS are two completely different ROMs and their respective kernels are NOT built to just flash & work on each other.

1. You shouldn't ask FK kernel queries in this thread. There is a separate thread for that and you should go there and ask any queries related to FK you have

2. You can not use NLOS's kernel on OOS Pie and vice versa.

3. Yes, formatting data will delete everything from internal memory. This ROM requires OOS Pie firmware and OP already has provided 2 ways to switch to OOS Pie firmware if you are coming from OOS Oreo. NLOS will NOT format your internal memory by itself.

Please only ask relevant questions to NLOS here and don't discuss custom kernels.
[OnePlus 3 & 3T Cross Device Development] Itachi_Uchiha:
Is there any specific build that is the most stable or are we to assume the latest build is the most stable build?
[OnePlus 3 & 3T Cross Device Development] :
No and yes.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
For my usage pattern (apps, mobile data, way i use my phone),I've not seen a single issue or bug in the last 2 months. With NLOS, you can always go with the latest release. However, everyone has a unique way of using their phone so there could be something broken for you. It's better to report with logs and the developer will help fix it.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION]

I think the automatic switch for LTE/GSM/WCDMA (in mobile networks settings) doesn't work correctly, what could possibly the cause of it? Blocked wakelocks?

Few times in a month, let's say i moved to a bad signal 4g location and the signal is lost usually for the first time. In order to get the signal back, i should force it to GSM only via settings, boom it's full, and then switched back to LTE/GSM/WCDMA to get 4g signal (in the same location, even it's bad). If i don't do that, i can't use internet nor phone calls.

I'll do the proper way with logs and clean installation next time i travel again. Just a friendly conversation this time :D