yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Sorry, I'm out here. It seems to be something related to power management: just before PhotonicModulat (I have no clue how this relates to car usage; do you use android auto?), the systems tries to freeze all apps and send the device to sleep.
[OnePlus 3 & 3T Cross Device Development] deejaycarras:
No my car hasn't have Android Auto, media system has bluetooth only. I will wait to another freeze and i send you those logs again!
[OnePlus 3 & 3T Cross Device Development] :
Why? I gave all my knowledge in my last posting. I have no clie whats going on. I'm out here, because I don't know how to fix. I understand, you don't like my answer, but that's the way it is: I can't help you, you are on your own.
[OnePlus 3 & 3T Cross Device Development] deejaycarras:
Sorry [MENTION=4405529]nvertigo67[/MENTION] i was understand that in attached logs you can't find anything (because in there are no clues about the issue) sorry my mistake and thanks for your work!

All of your answers allways are welcome!!
[OnePlus 3 & 3T Cross Device Development] 64ashg:
With an offset for you too. Thanks for the reply, i thought it was probably my fault running a dirty flash :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Lol I don't have the balls to dirty flash a new Android version.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Is anyone else having audio issues? After playing music for a while through the phone speaker (after a few songs), all audio suddenly stops working. This has happened multiple times now and I even missed a call. I have viper4android installed (and audiofx disabled), so I'll see if it happens without it and grab a log if it does.

Edit: Happened again so testing without viper now.

Also [MENTION=4405529]nvertigo67[/MENTION] , one nice thing about the current substratum implementation is that since it has a magisk module, the overlays don't show up as apps to be backed up in titanium backup. Systemless makes dealing with that easier yay.
[OnePlus 3 & 3T Cross Device Development] :
You've just managed to hit both rules with your question. ;)

The problem with your way of updating is, that you'll never know if it's the rom or the dirty rom change... At the end of the day, you'll spend more additional time on digging in issues then saving time from dirty rom changing.

BTW: everything not yet merged to los src base (meaning: everything in current-pick.sh) is highly suspect to issues - if every issue would have been eliminated, it would have been merged already.

The spacing in the statusbar is not ready, but at least it's working. The current beta los build can't have this spacing issie, because the traff8c isn't shown at all... ;) I prefer a working traffic indicator... ;)
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9350973]All[/MENTION]

Hey, this is an alpha build! A construction site! It doesn't make any sense to put an arab carpet in before the screed is ready. If you want to play with mods, dirty rom changing etc. grab a stable rom. Issue reports tainted with mods and other experimental stuff doesn't help to get the rom better and will end in frustration for you.

[MENTION=7134312]knpk13[/MENTION]: in the 15.1 thread you clearly claimed you remove always all mods before reporting... Please stick to this in the alpha 16.0 thread, too.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It's happening without mods as well. After some testing, I suspect the problem is with my music player, Poweramp. Doesn't happen on other players. Not a ROM issue, something wrong on my end. False alarm, sorry.
[OnePlus 3 & 3T Cross Device Development] :
I'm not so sure. Of course, many apps arn't really p ready(*) and there is quite a probability that this is also true for Poweramp. On the other hand: the rom is alpha, pa is going deep in the audio stack - perhaps it triggers something... Really not sure in this stage.

(*)Last night I've merged the substratum system service, sadly it doesn't work and crashes the SystemUI. When investigating the crash I found some hints, that andromeda has similar issues... (ps clearly states "not compatible"). We will see...

It's like always: three months before we get a version smoothly working, g pushd a new version... *lol*
[OnePlus 3 & 3T Cross Device Development] knpk13:
It's only that app (clean install) that suddenly stops playing any audio (with and without mods). Pausing and replaying, nothing works after that point. The default music app works without any issues. Should I send a log? I'm not sure when to start capturing it though. I'll try to work it out on my own to before bothering you though.

IDK about Poweramp not being P ready though, it just had a new major version release to v3.

Edit: [MENTION=4405529]nvertigo67[/MENTION]

Here is the log. Viper is disabled is magisk, so no audio mods. The inbuilt AudioFX app is disabled as well. Poweramp was playing a song. And after the song ended, suddenly no audio. Next song wouldn't play. I started a logcat and tried playing and pausing and switching songs and adjusting the volume. Then I stopped the logcat. Closing the app in recents and restarting it doesn't fix the problem. Only force stopping Poweramp from settings and then starting it again fixes the issue. Hope the log helps.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Upload didn't work sorry. Here. I feel kinda silly that I don't understand what the stuff in the logs mean.
[OnePlus 3 & 3T Cross Device Development] :
traffic indicator

Has anybody tried to turn the device landscape? Or has anyone tried to center the clock? The traffic indicator is not misaligned, but always centered... *lol*
[OnePlus 3 & 3T Cross Device Development] cukierkas:
While reading all of you guys I've decided to use a hand brake and sit silently with nlos15. :)

By the way, does call recording feature works on stock Los16 dialer?

Regards.
[OnePlus 3 & 3T Cross Device Development] :
Like in the 15.1 thread I don't talk of candy.

This looks worse then it is. There are NO dublicate notifications sounds. PA clearly states on their official forum that thwr is NO single poe device PA is validated on. The traffic indicator is centered, yes an issue, but a showstopper???

If very rare cases with bundeling unsurported mods with unsupported software (here: PA doesn't fully support pie) on an alpha build, takes the first three pages of a thread, the rom is just f0cking stable... *lol*

On the other hand: yeah, builds I have spended 10 months on are more sophistecated then something I've put together in 6 days (even without sleeping... ;) ) ;)
[OnePlus 3 & 3T Cross Device Development] :
I've just read in the official PA forums, that everybody has issues with pie. I've read that after spending 45 m with your logfile (logfile reading IS a pain in the ass - not only for you), assuming you tried to find a solution by reading (here on xda as well as on the official PA forums)....

If you want PowerAmp, use a rom validated for PA.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I only checked the xda forums rip. I assume it's not a ROM error and an app error then as I suspected. Thanks for looking into it. I'll use another music app for now in that case.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Sorry, uploading via labs seems to be buggy for me right now. The screenshot should be visible now.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Not on nlos16, but try vlc player. It has it own libs and his on decoders. Pie friendly.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Try simple gallery from market. Something wonderful I was looking for ages.

https://play.google.com/store/apps/details?id=com.simplemobiletools.gallery
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I have rolled back to nlos 15.1 but will keep a close eye on this thread nonetheless, especially for the eventual addition of sdclang, the refinement it brought was almost oos marshmallow-nougat like, heck even los 14.1 by sultan.

That said, i also observed a notification not being updated or dismissed with a file being downloaded by firefox and mega app. The download progress bar was stuck at a midway value, even though the files are downloaded. Smaller downloads behaved well but 500+mb file sizes showed this.

It could be my dirty flashing setup, probably, but worth looking into whoever decide to stick to it.

For anyone trying it out, the animations are great and so was the battery life, no show stopper bugs, just nuisances(far and apart) imo. I am just too particular about my phone's behavior now that i can't give more time to search for workarounds or just simply learn to live with it ;)

Thanks in advance :) to dev and testers
[OnePlus 3 & 3T Cross Device Development] :
Forgot to mention:

PA is no debug build - of course - so we can't really know from the logs what's going on. In the dmesg you can see, that the dsp is released (I guees it's when you force close PA). The only activity of PA in the logcat, is volume adjustment passed to PA.

Since PA comes with it's complete own audio processing, I guess the dsp is not released when it should - what happens exactly will always stay inside PA.

Ups, I was always thinking we talk of notification sounds. Platinum and cesium have two list entries each. I have no idea why:

ingo@adler /usr/local/src/los16 $ adb shell su -c "find /system /data/media -iname \*platinum\* -o -iname \*cesium\*"
/system/media/audio/alarms/Cesium.ogg
/system/media/audio/alarms/Platinum.ogg
ingo@adler /usr/local/src/los16 $

:confused::confused::confused:

The rom shipped libs arn't the problem - they are working including audiofx audio processing. Neither are the build in codecs. The problem seems to be the audio processing itself: our dsp/dac hardware seems to be much more potent then what oos and los/nlos is getting out of them.

Mods like viper or atmos are getting more out of our hardware, by directly communicating with dsp/dac. I guess PA is doing the same with it's audio processing (hd modules, equilizer).

Though vlc is surely a great player, it doesn't offer the audio processing enhancements [MENTION=7134312]knpk13[/MENTION] (and others) want to use.

The benefit and the issue here (audio mods, PA) are the same: the execlusive lock on the dsp. If something goes wrong inside of PA it stops playing sounds, but doesn't release the hardware...

EDIT:

Double alarm sounds

ogg files do not only have a filename, but also a tags called Track Name and Title:

ingo@adler /usr/local/src/los16 $ mediainfo -f out/target/product/oneplus3/system/media/audio/alarms/Promethium.ogg|grep -e "Track name" -e Title
Title : Platinum
Track name : Platinum
ingo@adler /usr/local/src/los16 $ mediainfo -f out/target/product/oneplus3/system/media/audio/alarms/Platinum.ogg|grep -e "Track name" -e Title
Title : Platinum
Track name : Platinum
ingo@adler /usr/local/src/los16 $ mediainfo -f out/target/product/oneplus3/system/media/audio/alarms/Alarm_Classic.ogg|grep -e "Track name" -e Title
Title : Cesium
Track name : Cesium
ingo@adler /usr/local/src/los16 $ mediainfo -f out/target/product/oneplus3/system/media/audio/alarms/Cesium.ogg|grep -e "Track name" -e Title
Title : Cesium
Track name : Cesium

Will be fixed in the next build.

EDIT2:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/236765
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello Op! Out of curioisity, why do our device needs zRAM enabled when it has 6gb physical RAM already? Is there any advantage or purpose to it? I am asking based on these 2 lines I saw in the chaneglog:

Please ignore if my question is wrong or invalid. I am not an expert about android and how it handles memory but i am aware that physical memory will always be better and faster than zRAM swap partition from internal memory.
[OnePlus 3 & 3T Cross Device Development] kbr0:
Just wanted to pop in and say Thank you for the ROM. Everything I need works smoothly.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
[MENTION=4405529]nvertigo67[/MENTION] is it possible that you add quick launch/ shortcut for camera on lock screen in your rom?
[OnePlus 3 & 3T Cross Device Development] :
It's extremly low on my priority list. It's one of these "if everything is fixed (i.e. 5GHz hotspot) and I'm bored to tears..."
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
I see no need for this feature.

You can still access camera faster with 2x press of the power button.
[OnePlus 3 & 3T Cross Device Development] Itachi_Uchiha:
is there any way to hide the carrier label on the lockscreen?

The lockscreen just looks so cool without the label
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Alright, thanks for your reply!

Unfortunately not working for me.
[OnePlus 3 & 3T Cross Device Development] :
Is it enabled? Settings->System->Gestures->Jump to Camera
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Yep. I even tried switching from nova to trebuchet as default launcher and uninstalled gcam mod.

Is it working for you?
[OnePlus 3 & 3T Cross Device Development] :
Works perfectly fine for me. In deed I'm using nova as standard launcher and have set pixel2mod V8 as default cam. Do you use off screen gestures? Can you start a cam with?
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
:eek: I'm a complete idiot...

I mixed up power with home button.

So it's also working for me.

Sorry for bothering you.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
BTW you can also set it to lunch at Home Button double tap. I have it for both - power and home button :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
All the talk about the home button reminds me, long tap on the home button doesn't pull up Google assistant. This was the behavior since the very first build when I clean flashed, but I didn't really care about it since I don't use assistant that much. Is assistant working for other people? If yes, I'll try a clean flash on the latest build to see if it works for me then.

Edit: Using opengapps nano, and button settings are fine.
[OnePlus 3 & 3T Cross Device Development] Creed_ok:
Search for "Assist & voice input" in Settings. Choose "none" for assist app and then "Google". After this assistant on long tap will work.
[OnePlus 3 & 3T Cross Device Development] aikattx:
My phone is oneplus 3t before. Then after flashing this rom my phone change to oneplus 3 with 3000 mah battery. Is it correct or I'm going crazy forgetting my phone model? ?
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
I have not even checked this once cuz it's so irrelevant what it's displaying it. It's purely optical, and has zero influence on youre hardware.
[OnePlus 3 & 3T Cross Device Development] :
May I ask what you are talking about? I have a 3t with 3400mAh:

oneplus3 / # getprop |grep -e "ro.product.device" -e "ro.vendor.product.device" -e "ro.product.model" -e "ro.vendor.product.model"[ro.product.device]: [OnePlus3T]
[ro.product.model]: [ONEPLUS A3003]
[ro.vendor.product.device]: [OnePlus3T]
[ro.vendor.product.model]: [ONEPLUS A3003]
oneplus3 / # cat /sys/devices/soc/qpnp-fg-17/power_supply/bms/battery_type
OP_3400mAH
oneplus3 / #
[OnePlus 3 & 3T Cross Device Development] kryzeK:
[MENTION=4405529]nvertigo67[/MENTION] since I installed NLOS 16 (about two weeks ago, clean flash) I have some "LED of death". My phone freezes with a black screen and white LED.

This only works again if I force the reboot longpressing power button, this happened I think 4 times.

Is this a known problem already?
[OnePlus 3 & 3T Cross Device Development] :
"Known" in the meaning of "others expirienced that, too": yes.

"Known" in the meaning of "I know where to look" or "I know how to reproduce" or "I know the reason": no.

To fix this, we need to find the trigger (to come to the cause and fix it).

Some useres expirience this regulary (like you) - some has never expirienced this (like me). So, we can be pretty sure the trigger is setup specific. To find the trigger I relay on the useres expiriencing this, because I can't find a trigger for something that doesn't happen on my side.

Currently I have no idea how to start to debug this.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
What a pity :( but I completely understand. For anything you need that I can help, please let me know.
[OnePlus 3 & 3T Cross Device Development] :
On a first glance it's quite simple: just ask three or four users expirience this to describe their setup en detail, compare it and find the intersecting set.

On a second glance this becomes complecated because of the users... ;) Perhaps "complecated" is not the right term and "time consuming" would be the better phrase... (I.e. A user complains about the extended slider settings in oreo pie and after a couple of days after finding out that he uses a custom kernel without the needed patches for extended slider settings, he stated that it doesn't seem important for him to mention the custom kernel earlier. This is an extrem example, but shows very clearly, why it's complecated/time comsuming.

If you'd like to step in here, Imwould suggest to compare the setups by this list as a starting point:

recovery used to format data the last time data was formated.

fs used on the last format

rom used to encrypt data

exact version of twrp used to flash

exact version of the gapps-/microg-package used

all steps taken to flash the rom in exact order

Rooted? If so: exact version of the package (just comes to my mind, though I doubt it's related, but who knows: I still use Magisk 17 for root, because 18 has all noaudit sepolicy rules disabled, which spams the log much too much for my use - it's really annoying.)

Any mods used (though I clearly state I don't support mods in this thread, it's important to know to track down issues of this kind! As someone taking care of a support thread of any kind, one will know, why Dr. House belives all people are lying... ;) )

suspected actions that may trigger the WLOD (Withe Led Of Death)

exact list of installed apks

Settings (that's a tough one...)

There are usefull additions to this I havn't thought of, for sure!!!

General thought: there are no random issues. Not seeing the pattern make us percept some randomness - but not seeing a pattern, doesn't mean there is no pattern - it just means we havn't found it.

Keep in mind this seems to be an issue on all los based roms: I've read reports of WLOD in the los thread, the rr thread and - of course - in our thread. If you find two nlossers, one losser and one remixer, this should be ok for comparission for this very issue.
[OnePlus 3 & 3T Cross Device Development] t0pg3ar:
I wish I could give you such an advanced report, but I can't anymore. As a few others, I also suffered from those hard locks - and I managed to fix them. In my case, the culprit was Google Opinion Rewards and, possibly, the Privacy Guard. Every morning I take my phone off of the charger and turn on wifi. Generally it'd lock up then. One time it locked up only after pressing the GOR notification. After the reboot I pressed GOR again - lockup. Naturally I removed GOR., as it was crashing anyway. No lockups in those days. I reinstalled GOR after a few days later and I have had no single issue since.

Like I said, I cannot replicate the issue anymore, so a LogCat is not gonna work. What I do know is that I have Magisk running without addons, AdAway and use the adviced, stable TWRP. Whether or not I had denied GOR any rights via the Privacy Guard, I do not know.
[OnePlus 3 & 3T Cross Device Development] simthadim:
Does USB OTG work fort anyone? I am trying to perform WALT latency tests but can't seem tot connect with the device trough USB OTG.
[OnePlus 3 & 3T Cross Device Development] rezaluchu:
I can use my SanDisk drive without any problem. So OTG works fine.
[OnePlus 3 & 3T Cross Device Development] simthadim:
Merci. Unfortunately my phone does not reckognize any USB OTG device ( used a computer Mouse/keyboard before, neither gets sufficient power to show any sign of life). The WALT device is not recognized as well. Will check it some time later.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.134-rc1 & some fixes; secure all tiles on lockscreen)

Build 20190204

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: 4 Feb 2019, 12:23:56 CET / 4 Feb 2019, 11:23:56 UTC):

squash: require unlocking to use tiles — Daniel Micay

apns-conf.xml: fix APN for tre.dk.

op3/t: sepolicy: adjust for hal_livedisplay_default.te.

op3/t: remove redudant system props.

Merge branch 'linux-3.18.y' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc into 134-rc1 — Nvertigo

ARM: dts: msm: FIxup GPU 0mhz clock — Nvertigo

drivers: video: mdss: Fix direct references to HZ — celtare21

drivers: ipa: Fix direct references to HZ — Humberto Borba

drivers: platform: gsi: Fix direct references to HZ — Humberto Borba

drivers: hwmon: Fix direct references to HZ — Humberto Borba

drivers: i2c: Fix direct references to HZ — Humberto Borba

Convert few critical drivers to use msecs_to_jiffies insted of HZ — Dorimanx

msm: kgsl: Remove POPP — Sultan Alsawaf

Optimize copy_page for modern ARM platforms — Harm Hanemaaijer

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:
[MENTION=4405529]nvertigo67[/MENTION] - something's wrong with the uploaded files.

I downloaded three times and all three tries resulted in the same md5sum, but different from the one You provided.

Either You provided a wrong checksum, or had a faulty upload or my operator cached a faulty download a provided me the file from it's cache (three times).

~/_flash$ md5sum -c nlos-16.0-20190204_125049-beta-oneplus3t.zip.md5sum

nlos-16.0-20190204_125049-beta-oneplus3t.zip: FAILED

~/_flash$ cat nlos-16.0-20190204_125049-beta-oneplus3t.zip.md5sum

7dd59f3d2c8e393835e9a95c7831f4d6 nlos-16.0-20190204_125049-beta-oneplus3t.zip

~/_flash$ md5sum nlos-16.0-20190204_125049-beta-oneplus3t.zip

fcd9a5f42f0f88b94f344eed69c9db99 nlos-16.0-20190204_125049-beta-oneplus3t.zip
[OnePlus 3 & 3T Cross Device Development] :
The build system has an ugly change: it always touches all zip in the out dir (also the already build ones). I've tested something that hasn't worked and shipped the previous one (which had a changed checksum besause of the toiching). For this time ignore the md5sum (since I'm testing afain, md5sum has changed again...). Sorry.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
All right! Thanks for the explanation.

Proceeding to flash then :)
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
What is "md5sum"?

What is its use in ROM flashing?

I have never used it.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's the md5 checksum of the file. By comparing the md5 checksum of the downloaded zip file with what is listed, you can verify that your downloaded file isn't corrupted or truncated.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Dirty flashed the latest build and sRGB/ DCI-P3 as colour profiles in LiveDisplay are not available anymore.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Whoa, can someone else confirm the same? I use that profile and i am thinking of flashing it over nlos15.1

Thanks in advance :)