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

Build 20190831

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: 31 Aug 2019, 11:37:59 CEST / 31 Aug 2019, 09:37:59 UTC):

no changes to device tree, kernel, blobs and/or nlos specifics - just synced with upstreams.

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] Jigneshg:
My sister also had a US model of OP3 and Jio doesn't work coz there is no Volte on US model enabled. And US model only has one 4G band for Jio.

So as you said you have to use Jiocall app for calls provided your Data is always on. Even if your mobile data is off you won't be receiving the call as well.. And its the same on OOS or any ROM u use.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Huh. Weird. Is there any way to enable volte then?

My data is always on. The annoying part is if I connect to WiFi, it switches off data and calls don't work lol.
[OnePlus 3 & 3T Cross Device Development] :
Have you tried enabling "Mobile data always active" in devopts?
[OnePlus 3 & 3T Cross Device Development] knpk13:
I just checked, it was already active. Rip.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (September Security Patch)

Build 20190906

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: 6 Sep 2019, 10:13:47 CEST / 6 Sep 2019, 08:13:47 UTC):

Revert "current.pick.sh: RIP libhealthd.lineage." — Nvertigo (HEAD -> nlos-16.0, nvertigo/nlos-16.0

Revert "current.pick.sh: reenable lineage off-mode charging pics." — Nvertigo

Patch up: P_asb_2019-09. — 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] djplus:
Thanks for the build. In last build dated 31 aug 2019, somehow dash charging wasn't working but issue seems solved on todays build. :) thanks [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
I'm happy to see your issue solved.

Though it's not build related: dash charging has worked for me on 0831. Most probably: dirt. The rest is timely coincidence...
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION]

Can you add support to view battery usage when clicked on battery icon. Currently we have to tap three dots to see battery usage.

Edit
[OnePlus 3 & 3T Cross Device Development] :
Reconsider your quoting and edit your posting accordingly, please. Only quote those parts of a previous posting, which you are referimg to. This helps to keep the thread a fun to read for everybody! Thanx in advance.

Fpr your featute request: I don't think the requested behaviour is usefull.

If you short tap the tile, you can switch bat saver mode on and off, If you long press, you are on tje bat main settings page and can go to profiles, manager, restricted apps and three dots. If this is changed to battery usage, you always need to go to the settings main page to access the battery settings main page to access profiles, manager or restricted apps. This change wouldn't make the ux better, but more uncomfortable, less straight forward and - most important ;) - I don't like it... ;)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I believe the requestor meant the big battery icon already in the battery main settings page. As far as I remember it worked like that in the OxygenOS.
[OnePlus 3 & 3T Cross Device Development] djplus:
Exactly. I was asking for this, Sorry if i represented in a wrong way. [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
Got that wrong.

If you can point me to patches, I'll check them.
[OnePlus 3 & 3T Cross Device Development] djplus:
Sorry I don't have any links or source to patches , maybe someone from the community can suggest ?.
[OnePlus 3 & 3T Cross Device Development] undrwater:
Just a quick WARNING to not install Oxi-fy from Magisk. It resulted in a bootloop on my device.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Pls post your problem HERE

If you can get a log it would be very helpful for the dev
[OnePlus 3 & 3T Cross Device Development] undrwater:
Thanks for the reply. I will report in both places, but I could use some guidance on what makes a good log for this problem. I can perform logcat on my linux box, and I can get into adb shell.

Should I just grab logcat as the device is looping?

I can do this after I backup tonight.
[OnePlus 3 & 3T Cross Device Development] :
If you search on google for "xda adb logcat how to", the first hit is: https://xdaforums.com/showthread.php?t=1726238 (important in your situation is the second part beginning with "On the other hand".

I would appriciate not being used as search engine assistant. My name is nvertigo67 - it's not "ok google".

If I consider your statement "I will report in both places", I would like to ask you to read and respect OP.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION]

if you're bored about how stable your current build is:

https://github.com/mcdachpappe/andr...mmit/5bce34003ab56fa3cd197ddbbabee412d6de6e3c

https://github.com/nitrogen-project...mmit/39525988e7b13f265b199b1dc755505061e29a02

https://github.com/nitrogen-project...mmit/39cb731184383e094fe722163991951c8b090ac5

if you're really, really bored:

porting Q system wide dark mode into P

Thanks :silly::laugh::silly:
[OnePlus 3 & 3T Cross Device Development] :
How do we use this after merging - I don't like the idea of enabling 900mAh by default? (apart from userinit.sh)

What's the porpose of this? I've always thought oled doesn't have backlight.

How do we control the seperate volumes? Don't we need to add the additional interfaces to - at least - audio_output_policy.conf, audio_policy_configuration.xml and/or mixer_paths_tasha.xml? Do we need additional android and/or selinux permissions to use it from userspace? Do we need to add code to fw/b and fw/av to get the controls to settings?

This will not happen on nlos-16.0: changing the api without increasing the api level and making a sdk backport (not sure if possible at all) is far beyond my abilities and my knowledge. Or in other words: I like the stability of nlos... ;)
[OnePlus 3 & 3T Cross Device Development] :
Should be disable by default, and user configurable in kernel adiutor-like apps. Same with all the other.

It reduces the minimal brightness with an assumption that it will save some % of the battery. Useful for adaptive brigthness in indoor usage. It hurts your eyes if back into standard mode with adaptive brightness on while indoor (if your eyes already getting used to the dimmer mode)

This.. I don't understand it either about how that's work. I tried manualy edit the mixer_paths_tasha.xml and other with no luck previously- but it's another subject and might be my fault. Yesterday, I ended up flashing franco and those options are back in kernel adiutor.... it's just my guess about headphone gain control options in KA since i have a really, really bad (low sound) headphone.

I'm just teasing you here :laugh:
[OnePlus 3 & 3T Cross Device Development] abhibnl:
After finally deciding to leave OOS Oreo behind, and having terrible experience with OOS Pie, it feels good to be back on NLOS again. ROM is super stable so far, and I always welcome [MENTION=4405529]nvertigo67[/MENTION] no BS commits approach. Thanks for providing a stable ROM. It just works :)
[OnePlus 3 & 3T Cross Device Development] :
If you enable adaptive brightness and set Brightness level to 0% it's much to dark for me. I use 33%. Is 0% really too bright for you?

I'm not asking to annoy you, but to umderstand, what's the purpose of this patch.

EDIT: With the backlight dimmer patch applied, I see the switch in kernel adiutor - but switching on and off doesn't make a difference?!?

For the system wide dark mode: I know you were kidding - I just wanted to avoid misunderstandings for people reading that.
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION] ,

Backlight Dimmer helps a lot at night when the screen is the only source of light, and yes it bright even at 0.

I vote for backlight dimmer if you are going to add that option to the kernel !!.:good:
[OnePlus 3 & 3T Cross Device Development] :
Where in kernel-adiutor is the soumd control when the patch is added?
[OnePlus 3 & 3T Cross Device Development] :
It's for adaptive brightness - as i said earlier

Standard setting at 0% isn't bright nor dark for me

Dimmer settings at 0% is almost black :silly:

It helps adaptive brightness at reasonable level in indoor usage (for me)

I believe you need to wait a couple of seconds or reboot after switching it on/off

In sound tab,

There should be 4 new line, headphone gain-headphone poweramp gain-speaker gain-michrophone gain

Though only Headphone Gain is working
[OnePlus 3 & 3T Cross Device Development] undrwater:
Thank you. I must not have communicated my intent very well. My initial post regarding this was just a WARNING to the users of this ROM that one of the Magisk modules I had tried ended up in a bootloop. 'Twas not a support request (I have read, and was attempting to respect the intent the OP). Following that, [MENTION=7452106]SenseSei[/MENTION] suggested you (and the module developer) might find it valuable to get a log of the bootloop.

I would never intentionally put you in that position. I have read the document "how to ask intelligent questions" (http://www.catb.org/~esr/faqs/smart-questions.html), and attempt to follow its recommendations.

I did a search here at XDA and elsewhere to determine when to take and what to look for in a log (I am quite familiar with HOW to take the log, just less so with what bears interest, and when that might occur).

I think you are saying here that you are NOT interested in a log of the bootloop (likely) caused by the Magisk module; but that is an assumption. Clarify, or not, as you wish. I see that it is more appropriate to submit a log on the thread that [MENTION=7452106]SenseSei[/MENTION] posted.

Thank you so much for your work. I TRULY appreciate it. I want to be helpful.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=2799078]undrwater[/MENTION]:

I've taken your first posting on the Magisk module as what it is: a word of warning. I appriciate that.

I've decided to jump in on the phrase "I will report in both places", because I don't support/debug/fix mods in this thread. Also: reporting issues in more then one place leads to doing the same work ny many people (aka waste of other peoples lifetime ;) ).

Everything is ok.

[MENTION=5616867]150208[/MENTION] & [MENTION=10055765]djplus[/MENTION]:

The dimmer patch is working well (I was too impatient when testing - it takes 2s or so to be applied). I need to fix sepolicy and do some more testing for the other two. I try to push a test build tomorrow.
[OnePlus 3 & 3T Cross Device Development] knpk13:
There's always NLOS 17

...

Hopefully :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION] Just out of curiousity, is it possible to add a switch to display settings for the backlight dimmer option ? Just as you did with the one handed mode ?

Also one more request kindly sync lineage changes till date if possible.
[OnePlus 3 & 3T Cross Device Development] knpk13:
You don't really need to ask for that, it happens with every build. Did lineage merge something interesting that you're waiting for?
[OnePlus 3 & 3T Cross Device Development] djplus:
Nope.
[OnePlus 3 & 3T Cross Device Development] :
If I take your questions literally: yes and no.

Of course it's possible, but it's not that easy as with the one handed mode tile: fw/b already knew one handed mode, so it was possible to just add the tile. fw/b doesn't know about backlight dimming.

To answer your implicit qurstion: no, I won't spend time on it. It's your chance to jump in! I'd really appriciate any help!
[OnePlus 3 & 3T Cross Device Development] djplus:
Just a short history,

I was introduced to custom ROMs when I was stuck with my moto g , and due to some curiosity i stumbled upon XDA so I started following threads related to rooting flashing and other stuff. I am no developer. The love for aosp and lineage is immense. I love using custom ROMs as I don't like stock ROM esp in terms of battery life and other stuff.

So when I see developers like you giving exceptional service to the community I feel grateful.

(One such person was developer of xenonhd ( for cancro).

In short I don't have any expertise in developing ROMs.

Anyways Thanks for your hardwork and time.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Can anyone please guide me as to where to find the option to enable "clear all recent apps"? I'm using Nova launcher and i dont have a clear all recent button when I go into recents.
[OnePlus 3 & 3T Cross Device Development] :
Depnding on the recents provider you are using, eitjer swipe all recently used apps to the right or all the way down.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
If you're rooted there's a great little app that adds a "delete all" button: on the recent apps screen: https://play.google.com/store/apps/details?id=eu.chainfire.recently
[OnePlus 3 & 3T Cross Device Development] :
Test build

Last repo sync: 11 Sep 2019, 12:44:38 CEST / 11 Sep 2019, 10:44:38 UTC

Patches to test:

mdss_fb: add backlight dimmer option — flar2

Seems to work: adjustment (if just enabled) happens on first adaptive backlight change.

ASoC: wcd9335: Sound control — flar2

Not working for my stereo bt headset, nor on my bt soundbar. I do not have hands on a 3.5mm jack stereo headset. I still belive that this needs implementation in fw/av and fw/base to make use of it, but I may be wrong. Tell me if it's useable/usefull, please.

drivers: misc: implement usb fast charge mode — engstk

IMHO not needed at all. I've done tests with the usb slot of my tab (low power, of course) and the usb3 slot of my build host (2000 mAh capable according to mb docu). I've always used the same - original op3t - cable. I've checked the max charging current with Ampere.

Unpatched: tab 500 mA (chown as "charging slowly" on lockscreen; host 1500 mA (chown as "charging" on lockscreen)

Patched with fast charge disabled: tab 500 mA (chown as "charging slowly" on lockscreen; host 1500 mA (chown as "charging" on lockscreen)

Patched with fast charge enabled: tab 500 mA (chown as "charging slowly" on lockscreen; host 1500 mA (chown as "charging" on lockscreen)

According to this tests, the patch is useless - the automatic adjustment is even better then the patch (1500 mA compared to 900 mA). Perhaps I miss the usecase for this patch. If so, tell me, please.

It's save to dirty flash on top of 0906. It's safe to return from the test build to 0906 by dirty flashing. Always wipe caches and dalvik.

ROM: https://drive.google.com/open?id=11NrWN_S-LV86arhdfUn0c2x_h_mc9myD

MD5: https://drive.google.com/open?id=1HwDHe3kxKutQls4zjqG_EIyr9hIiS9Dx

Happy flashing, testing and reporting!
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION]

Setup -

Clean flash , No Gapps, Magisk 19.3.

1. Backlight dimmer works as intended. ( enabled via HolyDragon Kernel Adiutor)

2. Headset gain works on 3.5 mm headset and not on bt headset. ( enabled via HolyDragon Kernel Adiutor)

3. Usb charge current is as you said - 500ma max.(mine hover aroud 300 whie connected to laptop) (Checked via ampere)

better drop the usb fast charge patch,

while rest two may be helpful.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4405529]nvertigo67[/MENTION]

All is good. About fast charge, it supposed to increase USB mode up to 900mA while MTP is on. Supposedly useful when you used the phone on Auto, used the phone for road navigation, etc.

xda messed link posts, you can try to quote my post to see the img if it's doesn't load..
[OnePlus 3 & 3T Cross Device Development] knpk13:
From what I remember when I used custom kernels, USB 3.0 provides up to 900ma to devices, and USB 2.0 provides up to 500ma.

Edit:

And these are for standard USB ports, not dedicated charging ports. The patch likely exists for that use case. [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
I have my device's usb config on "File Transfer" (in formerly android versions - I think in nougat - it was mtp) as default (in deed I have no "Auto" mode at all). So my testing results (patch has no effect at all, no matter if enabled or not) were all done with mtp enabled.

May I ask you to check the test build, if force fast charge makes a difference? Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] :
Please read my posting. I get 1500 mA max with "File Transfer" enabled on my build hosts usb3 slot, no matter of fastcharge setting or patch applied.
[OnePlus 3 & 3T Cross Device Development] :
Sorry, what i mean with Auto is Android Auto (car) :laugh:

Yes it's working for me while connecting it to usb 3 port on my PC. Without the patch it will only draw 500ma max. If your port is designed to only give 500ma max, of course it will only draw those number.

However, it's not really mandatory either for me. If you don't like it i can live with it :)

You seems have a high amp usb 3 port so the phone detect it as wall charger.. i don't know why it happen. But yes i know there exist a high amp usb port.

Oh yeah, what matter most it's not the software readings about the max current, rather the actual min/max readings at the top. I tried to connect my phone to my old 1 amp samsung charger, it detects as max 1500ma while it wobbles at 700-900ma min/max.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
That's what I am doing right now. Swiping individual apps in "up" direction as there is no single button to clear them all. And I have the default Pie recent style.

Thank you. I'll check it out.
[OnePlus 3 & 3T Cross Device Development] Dirk:
No. Try reading the post you quoted again. Nobody said swipe Up. Swipe Right and the Clear All button appears on the far Left.
[OnePlus 3 & 3T Cross Device Development] :
No, that's not what I've written.

If you swipe ALL THE WAY TO THE RIGHT (for p recents provider [aka trebuchet]; see pic 1) or ALL THE WAY TO THE BOTTOM (for o recents provider [aka SystemUI]; see pic 2), there is your clear all button...
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I feel so stupid right now. All this time I was looking for a button and didn't even notice that it actually appears as a text. I thought nvertigo was suggesting to clear all apps individually as there is no clear all button.

Thanks again :)
[OnePlus 3 & 3T Cross Device Development] :
Arghh, it's the third time I've been traped by this... ;)

Thanx for testing, explaining and the screenshot!

It hasn't come to my mind, that the purpose of this patch is not increasing the usb max charging current, but to completely ignore the limits from usb max chraging current.

usb max charging current should be a hard limit to my understanding.

From a systematically view this is bad practise and I don't lile it.

For the "ASoC: wcd9335: Sound control Add left and right headphone gain control"-commit:

Controling the two stereo channels for headphones (and headsets - for that matter) seems usefull to me. With no rom intergration and adiutor not allowing to raise the gains seperatly it's completely useless. Further more: I've tested this with my old s3 cabled headset and found the issue with randomly paused output from Music app (which can only be resumed again after force closing Music app) when playing with the gain setting in adiutor. That's one of the issues that made me removing AudioFX from nlos.

Bottom line: The next build will have the backlight dimmer patch. I'll add the audio patch, when it's possible to integrate it in the rom's audio settings. I'll look at the force fast charge patch if it's possible to raise the hard limit imstead of ignoring it the next nights - I can't promise anything.
[OnePlus 3 & 3T Cross Device Development] :
Yep, no problem.

The commits about audio patch it's not done yet and need another tweaks. It will be even better if you can integrate it with this changes, or even more into bottom speaker/mic gain :D

Again, no pressure, do it if you like it and you've got some times to kill :laugh:

I'm lost at words, the only words i can think of without writing an essay is; Thank You for everything!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (backlight dimmer & maintainance)

Build 20190913

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: 13 Sep 2019, 11:03:02 CEST / 13 Sep 2019, 09:03:02 UTC):

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

ASoC: wcd9335: Sound control — flar2

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

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

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

Happy flashing!