yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
It's already in. I just hate the "compile time download script". I want a defined state of source code, when starting the build. Therefor I've changed the script to update manually... What I've forgotten... Thanx for the heads up.

I'm on the nlos shipped kernel ("stock" let me think of OOS... ;) ), with pin. After a wrong pin the input field and the keyboard is fired up again, but this time the focus is not in the input field. If I type my pin now, no astericses (correct plural???) are shown in the input field - if I press ok now, the pin is wrong (aka empty) again. Can you check if manually setting the focus to the input field (just tap in) before typing the password a second time works? It does for pin.

Neither the patches nor my oppinion has changed since I've answered this the last time: https://xdaforums.com/showpost.php?p=79584247&postcount=724

Let me add: when I've tried to backport, the changed error handling generates kernel panics. Since stability is my first priority (before batt life, before features), I've stoped working on dts.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks! I never noticed that the focus had been lost. Tapping in the entry field and entering the password again works.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (WireGuard: update to 20191206; Fix ArrayOutOfBounds error; maintainance)

Build 20191210

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.6 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.6 firmware

Oneplus 3: OxygenOS 9.0.6 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.6. 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.6 firmware, 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.6 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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

Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.

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

Changelog (Last repo sync: 10 Dez 2019, 14:02:26 CET / 10 Dez 2019, 13:02:26 UTC):

Use patchset #2 of https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/265144 , which fixes ArrayOutOfBounds error

op3/t: remove redudant dalvik.vm.heapsize. — Nvertigo

WG: squash WireGuard-0.0.20191206. — 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] Ysfzone:
This is the best ROM for OP3/T with less features but is stable and strong and battery friendly..

But i can't use it.. i want at least tile for disable HW keys.. because i play a lot of games and without game mode or tile for disable HW key (Home-recents-back) i press accidently this key a lot and it's impossible to me to play games..

Please add at least (Tile for disable HW key) not game mode..
[OnePlus 3 & 3T Cross Device Development] knpk13:
You could try making a tasker or some other automation script to turn off hw keys in the settings. Or maybe just turn off hw keys completely and use on screen navigation?
[OnePlus 3 & 3T Cross Device Development] Ysfzone:
It's useless for me to use navigation screen on keys phone..

I believe nvertigo can add this.. i hope that.. for me it's a Christmas Gift ?
[OnePlus 3 & 3T Cross Device Development] :
We don't have a "disable hw buttons mode". So I can't make a tile for it before implementing "disable hw buttons mode". The same goes for tasker: as long as ther is no "disable hw buttons mode" you can't use tasker to enable what we doesn't have.

If on screen navbar and extended display (which is controleable by tasker) isn't an option, nlos is just not the best rom for your usecase.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can do it if you're rooted with:

echo 1 > /proc/s1302/virtual_key

To re-enable them send a 0.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is anyone having issues recording video, or sending videos in WhatsApp? Some of my videos get corrupted while recording, and videos in WhatsApp don't get sent unless I reboot. I barely use WhatsApp or record videos so hadn't noticed till now.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
i haven't noticed such issues. but i have definitely seen some delay in the video. like the audio and video are not at sync. After i finish the recording and play,it plays normally. when i send it to someone via whatsapp after trimming the original video,it starts to lag. The audio and video aren't synced. And then the original video behaves the same way too. not sure if its rom related,or a lineage thing in general.
[OnePlus 3 & 3T Cross Device Development] :
I'll check the first one. The latter is already in work upstream.
[OnePlus 3 & 3T Cross Device Development] Tiggy_Drum:
Do we get adaptive battery function ? Or this is a feature to install by an other way or a setting to enable ?
[OnePlus 3 & 3T Cross Device Development] :
That's a good question and - honestly - I don't know. Obviously the ai part of the code is closed source and is not contained in aosp. aosp has battery manager and Standb apps. I guess(!) that's the open source part of the game. I have no idea how the battery manager mechanism differs from the adaptive battery mechanism. Anyway, you can check in Standby apps to which bucket each app is assigned.

We will see what oos 9 has on board. If they ship blobs with deepmind ai sofware isn't known currently. At least not me.

BTW: I'm beliving in the laws of thermodynamics. Therefore I highly doubt g's promise of bat saving up to 30%... (g will argue that 0.2% is inside the range of "up to 30%"... ...but in real life we will not see those 30%)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (The Return of The Snap; qcom WiFiDisplay)

Build 20181227

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later 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: 27 Dez 2018, 10:28:49 CET / 27 Dez 2018, 09:28:49 UTC):

current.pick.sh: pie-qcom-wfd. — Nvertigo

current.pick.sh: common: Label and allow access over LiveDisplay sysfs nodes. — Nvertigo

current.pick.sh: common: Expand labeling of sysfs_vibrator nodes using genfscon. — Nvertigo

current.pick.sh: op3: Add QCOM's WFD implementation. — Nvertigo

current.pick.sh: op3: Add priv-app permissions whitelist from LA.UM.7.6.r1-03900-89xx.0. — Nvertigo

current.pick.sh: force picking abandoned audio panel commit. — Nvertigo

Revert "current.pick.sh: pie-hide-night-display." — Nvertigo

Revert "current.pick.sh: "configpanel: replace "Alarms only" with "Vibration""." — Nvertigo

Revert "current.pick.sh: Performance: Memory Optimizations." — Nvertigo

hotfix.xml: remove Snap; readded upstream. — Nvertigo

op3: Address perf hal denial with boost enabled — dianlujitao

[DNM] op3/t: Snap: allow plattform_apps to execute it's cached data files. — Nvertigo

op3/t: overlay-lineage: increase maximal visible icons in status bar. — 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] phoberus:
I noticed that the Ram management is not optimal. Although only a few apps are executed and I only switch to another one for a short time, the app is closed in the background and has to be restarted.

For example I'm in "App 1", just switch to "App 2" for a few seconds and then back to "App 1" -> "App 1" restarts.

I hope you understand what I mean. After a device-restart it is OK again for some time.

RAM is mostly 80% full. No tweaks or custom settings, kernel etc.. Clean flash

edit: i'm on the 22.12 build. Is this changelog maybe a fix to this problem?
[OnePlus 3 & 3T Cross Device Development] :
I have reverted the repopick from current-pick.sh, because it was merged upstream. I doubt it's the cache trimming from this commit, perhaps battery manager: you can try moving App1 from the RARE bucket to WORKING_SET. I'll check the code for new (pie introduced) bg limits.

BTW: I've never understood, what the memory page in devops is showing or how it's calculated. For accurate numbers I use free, top or htop.

EDIT: Would you please check your logs, if App1 is killed by lmk or what ever stops App1?
[OnePlus 3 & 3T Cross Device Development] dyc3:
is it possible to implement the feature where an app's version info is displayed in package installer while installing or updating an app package? I saw this feature in the nitrogen rom..
[OnePlus 3 & 3T Cross Device Development] :
I'm not sure if it's worth the effort, because 95% of the users use gapps, which replaces package installer, no matter which package size is choosen.
[OnePlus 3 & 3T Cross Device Development] dyc3:
Yep.. google slaves... why dont you stop the gapps support in your future builds XD
[OnePlus 3 & 3T Cross Device Development] :
Slaves... ha, you know how to get me... *lol* Will be in the next update for the freedom fighters and unchained ones.

https://github.com/nvertigo/android...mmit/ba8cce0bf0a31f12badf200f9a194503cdeca596

https://github.com/nvertigo/local_manifest/commit/8e1a42c3069f9a20b19e276b3256ce50a96bba95
[OnePlus 3 & 3T Cross Device Development] dyc3:
Thanks..
[OnePlus 3 & 3T Cross Device Development] netmm:
This ROM is the best thing that's ever happened to the OP3.

You should put up a donation link in the OP, I'd certainly not be the only one to show some appreciation.

Kudos to you my man!
[OnePlus 3 & 3T Cross Device Development] :
I don't like begging for donations. But since this has been ask the second time now: if you look on the left side of each of my postings, in the column with my user name, just below "Thanx Meter" there is a large yellow button reading "Donate to me".

Away from that: thanx for your kind words.
[OnePlus 3 & 3T Cross Device Development] karkiankit:
Hi, i am planning on switching to this rom but i want to ask does this rom has QS rows/colums setting???
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello [MENTION=4405529]nvertigo67[/MENTION]

Would you consider adding a "gaming mode" toggle in QS tiles which when enabled would disable the soft touch buttons? I will try to ask around about a commit from Skydragon ROM dev so that I can help you. I know it's not a popular request but i use my phone to watch youtube and netflix and often hold from the front area including the FP sensor. So i just enable gaming mode so that the buttons will stay disabled.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'm pretty sure you can add custom QS tiles from apps like Tasker (and others) to perform whatever action you need it to.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
This particular tile actually does more than that. It also enables a DND mode where Heads-up and other notification popups will be disabled and only notification that will come through is an actual phone call. I have no clue how to do that with Tasker. I tried it once and wasn't fully able to understand or utilize it so got a refund.
[OnePlus 3 & 3T Cross Device Development] :
No, it hasn't.

Honestly, I don't like to add it. One of the most used phrase is "make it configurable". If I would have added all config options this phrase was used for, we would have dozens of gui switches. If the majority of users opts for i.e. 4 columns and 4 rows, we can have it changed, but I don't want to start to add gui customizing switches, because it is only one option for you, but we all know, where this ends once started.

I've tried adding this on NLOS-15.1 and failed legendary even finding the related patches. If anybody can provide a list of all needed patches, I would be able to tell if I want these in NLOS (i.e. I don't like api changes). Any help on finding all needed commits is highly appreciated!

You can switch all zen modes via settings cli. I've already explained how to get a comprehensive list of all settings acessible via the settings cli: https://xdaforums.com/showpost.php?p=78386477&postcount=1411
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I will make sure I get in touch with the dev and try to get all patches for you to review. In the meantime, my first impressions as i flashed it yesterday after work. Stable, fluid, VoLTE working, all basic phone functions working properly. The only thing in not able to figure out is Night mode or night light. Is it called something different in this Rom? I use it daily in bed for watching some YouTube and Netflix to use warm screen color temperature
[OnePlus 3 & 3T Cross Device Development] :
Settings->Display->Nigh light should be removed in the last builds. Settings->System->Devopts->Night mode is basically the same as Settings->Display->Style->Style (the latter has an additional automatic mode for wallpaper). I'm looking for a possibility to remove Night mode from dev-opts, because the Display Styles is superior.

For your purpose go to Settings->Display->LiveDisplay->Display mode and select Automatic. In Settings->Display->LiveDisplay->Color temperature you can adjust how warm you want it. For some video players (mx and vly come to my mind) you need to disable full brightness settings in the player itself for watching in an dark environment.
[OnePlus 3 & 3T Cross Device Development] :
Dude, you should know better. This is ambigouos and lacks information...

From the last sentence I guess, you talk only about whatsapp recorded and trimmed videos. From the first and second sentence I guess it's for some recorded videos (which cam app?), and only the sending is whatsapp related...

I've no idea, what's the sending issue is. Settings? i.e. Data restriction?

The same as above. Let me be the devils advocate: So you say, if you take a video with Snap on the back cam, switch to wa, trim it and sent it, the original video played with shipped video player is out of sync... ;)

Wild guessing based on curtent information:

The trim in wa is broken, demuxing/remuxing breaks video's sync. (If you ask google, this is around since 2013)

Questions:

Does the out of sync appear on each wa demuxed/remuxed (this is always done to reduce the resolition, even if you don't trim), or only if it's trimmed?

Does the out of sync appear only on wa recorded and muxed/trimed (depemd on previous amswer) videos or on all recorded videos (i.e. Snap) handeled later with wa?

Are video calls working in sync?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Sorry I didn't really know what information to provide exactly since this issue is really weird so I thought I'd ask if anyone was having issues with these apps in general (if they weren't, I was going to try a clean flash). Here's a better description. The issues with corrupted video happened with all 3 camera apps I used, stock snap app, gcam, and open camera. I have never tried to use the WhatsApp camera to record video. Sometimes it just says, "failed to record", try again and FC's. Sometimes it records and then when you try to play the file, it doesn't work.

WhatsApp on the other hand, if I try to send any video file, just says it failed, even if I hit retry, and asks me to reboot. The message is "Failed to process video. If you keep getting this error, please reboot and try again". I reboot and it works. I looked at the log, and it's full of errors, most of them unrelated to the camera or Whatsapp or video player. Is that normal? I tried saving the logs, but the phone hanged and was very laggy when dealing with these video files while trying to play or send them in WhatsApp, and just stopped in between, so I went to recovery and cleared the cache/dalvik and reflashed the ROM and performance seems better now.

Edit: I tried sending a video again, and the screen became non responsive, and I eventually got the failed to process video error message again. I think the log worked this time though.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Attached
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7134312]knpk13[/MENTION]

I've no problems at all to send a backside 11 s (5.5 Mb) video. Works immidiatly and without lagging the phone.

I suggest you do a clean flash to get a sane setup again. The log is full of omx codec errors. Did you mess with media xml files, or did you flash stuf that messes with codecs incl. audio codecs? Anything special about your setup you've forgotten to mention?

What's definetly sick and can lead to any strange effects: dex2oat is broken on your setup. From your log:

12-15 08:08:39.231 F/linker (2481): CANNOT LINK EXECUTABLE "/system/bin/dex2oat": "/system/lib64/libart-compiler.so" is 64-bit instead of 32-bit

The linker should know to link dex2oat with /system/lib/libart-compiler.so instead of /system/lib64/libart-compiler.so. I suggest clean flashing with only gapps and magisk (without modules) and without restoring anything, install wa from scratch and only restore the messages (no wa backup from backup apps or google).
[OnePlus 3 & 3T Cross Device Development] knpk13:
Huh? I don't even know what omx or media xml is. Audio.. hm I have viper4android installed and it works perfectly. Other than that I have the op3t magisk modules for front Cam and slow motion installed since it was recommended in the gcam thread. Ok I'll clean flash. Do you have any idea how dex2oat can get broken? Is that normal? I attached a magisk log if it's of any use, but I'm still going to clean flash like you recommended.
[OnePlus 3 & 3T Cross Device Development] :
I'm pretty sure the slow motion fix messes with the media xml files. Don't you check what a zip is doing to your system before flashing and judging it works?

omx (openmax) is the way android utilizes hardware-based codecs. See: https://source.android.com/devices/media

It's always strange, when people with a messed up setup claim at first: it's working perfectly... ;)

dex2oat: no, it's not normal - it's sick. That's why I've written in my last posting, that this is sick and will lead up to strange effects!
[OnePlus 3 & 3T Cross Device Development] mk_1996:
i am so very sorry for providing incomplete information. I was talking about the screen recorder that ships with the ROM. I will further investigate the app for issues. Again,i apologise
[OnePlus 3 & 3T Cross Device Development] knpk13:
[MENTION=4405529]nvertigo67[/MENTION]

You were right, the slo-mo module deals with some XML files and I don't know how they work, so examining zips like those is hard for me.

I disabled all magisk modules and the issue didn't go away.

So I clean flashed. Latest NLOS, opengapps nano, magisk and security patch zip. No modules or or any other mods. Logged into my Google account. Clean installed WhatsApp from play store and restored local backup of messages through the app. Tried to send a video, and same error. "Failed to process video, please try again and reboot if the issue is persistent." I attached logs from normal system running after a clean flash (still had a lot of errors, idk if its normal), first boot. And a log when trying to send a video on WhatsApp.

Edit: Hm, I think I figured it out. Any videos I record with non stock camera apps don't get sent on WhatsApp without a reboot. Weird part is they get sent on other apps like telegram and discord. I tried sending video files I downloaded from the internet, and videos I recorded with the stock cam and they worked like a charm. I guess its not an NLOS issue but this is still very confusing. I'll try a different ROM to check. A convenient excuse to try out LOS 17 again.
[OnePlus 3 & 3T Cross Device Development] :
Then you are lost. If you flash system changing stuff you don't understand, you can't expect other people to do this for you in order to fix your setup. Especially don't expect me, to spend hours on investigating your logfiles (which are still missing ppids).

I have no idea how to help you. I've recorded a video with Arnova8G2-V8 and it gets reduced from 1080p 30fps to 640x352 with variable framerate - but it gets send. Propably the encoding of the videos with the changes for slow motion arn't liked by wa, I don't know. It's sutely no rom issue. And honestly: after investigating your first log for accumulated 50 minutes and spending an other 30 minutes on testing, I'm not willing to spent more of my time on this.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=4405529]nvertigo67[/MENTION]

Yesterday I discovered that my password manager (RoboForm; com.siber.roboform) died (sort of like a force close) entry time I accessed the user identity information (bank account, drivers licence).

After a lot of messing around I finally discovered that the problem happens on only nlos but not on los or oos.

So I did a pristine (wipe data and system; install rom and Magisk only) install of nlos, installed only RoboForm (I have a copy of the APK) and verified that the problem happens. At that point I took a logcat (this was my reason for installing Magisk).

I then did the same but using los. I've attached the logs for both roms. I hope the logs show what the issue is.
[OnePlus 3 & 3T Cross Device Development] :
Great issue report!

Though one question left: which builds are you using?

--------- beginning of crash
12-22 07:33:05.721 5949 5949 E AndroidRuntime: FATAL EXCEPTION: main
12-22 07:33:05.721 5949 5949 E AndroidRuntime: Process: com.siber.roboform, PID: 5949
12-22 07:33:05.721 5949 5949 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=22; index=22
12-22 07:33:05.721 5949 5949 E AndroidRuntime: at android.text.TextLine.draw(TextLine.java:267)
[...]

This looks like you are using nlos 20191205. This should be fixed in 20191207 (hotfix build; not in history, only in thread: https://xdaforums.com/showpost.php?p=81132381&postcount=1338 ) and 20191210.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The logcat file names tell you:

Nlos 191205

Los 191215

Edit: now I see that it's the out off bounds error. I'll update nlos. Thanks for pointing out the problem and solution!

Edit 2: dirty flashed nlos 191210 and the problem is fixed.
[OnePlus 3 & 3T Cross Device Development] :
*lol* I was so focused on the content of the logs, that I've not seen what they've wraped in...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I have a similar problem with reading emails. I only see what I expect to see.

Thanks for finding the problem and fixing it and for your continued work on this rom.
[OnePlus 3 & 3T Cross Device Development] :
[SWAGGER]

One of the key technologies of the least annoying rom: "Ultra Mega Hyper Fast Fixing" (UMHFF) [patent pending]

it's fixed before you ask...

[/SWAGGER]

*lol*
[OnePlus 3 & 3T Cross Device Development] ememeh:
Quick question: is the latest build updated to December '19 security patch?
[OnePlus 3 & 3T Cross Device Development] :
According to history in OP: yes. (see build 20191205)