yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Needles_one:
OP, is there any way you could add an alternative option for the alert slider - alarms only. This one is presented on stock OOS and some AOSP Pie's.
[OnePlus 3 & 3T Cross Device Development] :
Alarms only is a dnd setting on oreo (i.e. in OOS), which is removed in pie. Pie only has only one dnd setting, which can be configured to behave like alarms only.

Would you please show me the commits in "some AOSP Pie's"? If they don't break anything else, I'll add them.

(It would be helpfull for getting the complete relation chain, if you can point me to a gerrit instance instead of a git repo. Also: if an additional switch setting is added.

If you look at this commit https://review.lineageos.org/c/LineageOS/android_device_oppo_common/+/236894 you'll find we've replaced the (oreo only, removed in pie) with vibration, because there is no alarms only in oreo. Before this change, you've had alarms only in the settings, but - of course - it hasn't worked. We've needed this commit to get the slider to work properly, because alarms only tried to trigger something, not present in poe any longer.

If you mean the to restore the broken behavior like before this commit: no!
[OnePlus 3 & 3T Cross Device Development] Zaphod_B_1:
Hi [MENTION=4405529]nvertigo67[/MENTION],

question from my side regarding this: Is it regular behaviour of Pie, too that in "Total silence" mode the media volume is set to zero and it isn't possible to set it?

I'm asking because in Oreo that was different as I remember... Only the notifications were totally silent and it was possible to play media (and set its volume) in that mode.

Is there any possibility to have a similar mode as I described?

Cheers

Zap
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=6986703]Zaphod_B_1[/MENTION]:

Total silence utilizes the silent mode from volume settings (in deed it's the very same status you enable by hitting the mute icon in on screen volume dialog twice until the striked bell appears), which implies silence for media. This is the same on 15.1 and 16.0. Perhaps you mix that with the additional dnd setting we had on 15.1 (removed in oreo).

You can configure dnd ("Priority" switch setting) settings to silence everything but media.
[OnePlus 3 & 3T Cross Device Development] Zaphod_B_1:
Thanks for clarification. You're right, maybe I've mixed that up. I'll try configure the settings accordingly.
[OnePlus 3 & 3T Cross Device Development] kbr0:
Is it known that there is ab issue with the oneplus c-type bullets and calling? The other Party can hear me finde, but I can't hear a thing. Does anyone else have that issue? Or maybe a workaround?
[OnePlus 3 & 3T Cross Device Development] :
I don't have hands on a usb c-type headset. With the above information I can answer all three questions with "I don't know".
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.135-rc1; maintainance)

Build 20190219

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: 19 Feb 2019, 19:32:47 CET / 19 Feb 2019, 18:32:47 UTC):

current.pick.sh: "lineage-sepolicy-fix & op3: Rewrite livedisplay HAL sepolicy". — Nvertigo

NLOS: add for reference /vendor/xiaomi. — Nvertigo

Revert "current.pick.sh: "settings: Allow accessing LineageSettings via settings command"." — Nvertigo

Revert "current.pick.sh: libril: Fix manual network selection with old modem & op3: Enable workaround for old MCC/MNC format." — Nvertigo

Revert "current.pick.sh: "op3: Migrate to livedisplay 2.0"." — Nvertigo

Revert "current.pick.sh: "op3: livedisplay: Support sysfs backend display modes"." — Nvertigo

current.pick.sh: add "parts: don't allow clock and network traffic to be enabled at the same time\* to pie-network-traffic. — Nvertigo

Revert "current.pick.sh: "op3: Convert TouchscreenGestures to touch HAL"." — Nvertigo

Revert "current.pick.sh: "op3: Convert KeyDisabler to touch HAL"." — Nvertigo

op3: Fix neverallows — dianlujitao

op3: Update tftp_server blobs to P from daisy — DennySPB

op3: livedisplay: Support HBM — dianlujitao

[DNM][WIP]op3/t: allow a bunch of denials after merge of pie_neverallows and lineage-sepolicy-fix. — Nvertigo

[DNM][WIP]op3/t: fix some more neverallows. — NvertigoMerge v3.18.135-rc1 of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc into nlos-16.0 — 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] cukierkas:
NLOS: add for reference /vendor/xiaomi.

Amateur question : what is this about? Do oneplus and xiaomi shares same libs?

Ot, I do remember we had a talk about need to go to 4.x kernel.

Using now 5t with 4.4.153 - į really don't see the difference with the 3t nlos16 I was using maybe 2months ago on 3.x kernel version. Only cpu, battery backup, camera and display are biggest differences. Other are the same - rock solid and fast. Sometimes I'm catching myself to buy a spare device, 3t, of maybe 120€ for learning purposes. Still rocks ;)

In other hand, 4 hours of sot - doesn't worth it. I'm spoiled with 8hrs :eek: :)

https://ibb.co/gTFkzkp
[OnePlus 3 & 3T Cross Device Development] Mata99:
[MENTION=4405529]nvertigo67[/MENTION] using last update Spotify doesn't work: music starts but after a few seconds it stops
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Dirty flashed latest build. No problems with Spotify.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Clear Spotify's cache. Even better to clear art cache + cache in recovery.

If that step won't help - reinstall Spotify from gplay store.
[OnePlus 3 & 3T Cross Device Development] :
git lg1 -- proprietary-files.txt |grep -i daisy
* 7f322fb - (vor 9 Wochen) op3: Update tftp_server blobs to P from daisy — DennySPB
* 1ed8c8c - (vor 3 Monaten) op3: Kang ims.apk from daisy — dianlujitao
* 970acf1 - (vor 3 Monaten) op3: Massive blob update from daisy — dianlujitao

Largest one: https://github.com/nvertigo/android...38da69f#diff-e18a190ec9e1d301d38ff968dea34a59

The suggested fix makes sense to me (btw: caches should be wiped from within twrp on each update/dirty flash. Force closing and wiping data of spotify in rom's app settings should be the same as reinstalling). It would explain the different expirience reported here in this thread, as well as here:

https://review.lineageos.org/q/7abefe9e881c4bbc219d9b89bb5862e0966daa46
[OnePlus 3 & 3T Cross Device Development] Mata99:
I have done some tests, without earphones sound works fine. I have the same Spotify issues in YouTube.

I have also try a clean flash but the problem persist.
[OnePlus 3 & 3T Cross Device Development] :
I don't use spotify. Youtube works great with earpiece, Teufel Move BT and Bose Mini II Soundlink. I've no access to a 3.5 mm jack headset, nor to a usb-c headset. This makes it imppssible for me to fix anything with the current status of information.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Also tried headphones (3.5mm jack) and still no problems.

edit: No problem when a song is already playing and i plug in the earphones. But no sound when i first plug in the headphones and press play or one song is finished and the next begins. Same for yt.

edit2: bug persists after clearing app data & cache.
[OnePlus 3 & 3T Cross Device Development] simthadim:
I finally updated the (pre) jan 22 2019 build to the latest build (20190219). However, I get the same thing when I first installed NLOS (see my comment on the 22nd of Jan)

THE NLOS bootscreen shows (blue LED is on for a short amount of time), it takes VEEEEERRRY long and eventually reboots to TWRP. When I updated (dirty flash) I downloaded the .zip, transferred it tomy phone, rebooted in TWRP and ' installed it from a local zip package' . Cleaned the cache afterwards (was that my mistake? Shouldn' t be it, right?). After installation I read on the screen that the installation was successful, Magisk installed itself automatically as well (as it would normally do once a new image is flashed).

Are there any logs (TWRP?) that would be of help in development before I try a clean flash?

My set-up:

Oneplus 3 A3003

Firmware 5.0.0.8 (see OP)

TWRP version (3.2.0-fix3, as mentioned in OP).

Upgraded from 20190122 (the latest build that was available on that day) --> 20190219

On the previous build I ran:

- Magisk (V18)

- and MicroG (which I flashed using Shadow53' s zip. Micro G needs to be a system app, therefore I flashed it in TWRP, rather then install it via F-droid)

I gave fakestore (for MicroG) additional signature spoofing permission ( as this was not introduced in the build I installed, I mentioned this to you back then.).
[OnePlus 3 & 3T Cross Device Development] :
Back then (https://xdaforums.com/showpost.php?p=78734956&postcount=348 ; btw: it would have been just nice to reference the old conversation to save me from the need of searching), you ended with:

You havn't lost a single word on the status of your data partition. Did you format it with 3.2.3-1? Did you reformat with 3.2.1.0-fix3? Did you really follow OP? I gave quite some directions in the convesation before the posting I've quoted, but you didn't give any feedback.

I'd recommend a clean flash as if coming from an other rom (including format data with twrp-3.2.1.0-fix3) after fixing your data partition from formating with twrp-3.2.3-1.

It's added:

https://github.com/nvertigo/android_vendor_nlos/commit/9a7cd0443630d0be0e21eb3c54f86767d528a25e

Sadly I didn't receive any feedback if it's working.
[OnePlus 3 & 3T Cross Device Development] :
Would you check if audiofx is the culprit with your 3.5mm jack connected headset, please?

In twrp (either terminal or filemanager) delete /system/priv-app/AuioFX directory, wipe caches, reboot to system and test again.

(Of course everybody with access to a 3.5mm jack headset is invited to test the above. For obvious reason I ask people known to give feedback first.)
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Solved the problem for me. Thanks! :)
[OnePlus 3 & 3T Cross Device Development] Mata99:
When I open /system folder, it is empty.
[OnePlus 3 & 3T Cross Device Development] :
Mount system in twrp.
[OnePlus 3 & 3T Cross Device Development] Mata99:
Thanks, now it works.
[OnePlus 3 & 3T Cross Device Development] :
I've just made a build without AudioFX. To my surprise I've the impression that the sound is clearer (or more treble-rich). Since perception is very prune to placebo effects and self fullfilling prophecies, I wonder if it's just me, or if it's for real?

I've tried to use AOSP MusicFX after removing LOS AudioFX, sadly this disables audio alltogether as soon as MusicFX is enabled - so this is no option. But I'm seriously considering to drop AudioFX completely with no replacement. What do you (@all: it's really easy to remove AudioFX from the current setup - just delete it from within twrp) think?
[OnePlus 3 & 3T Cross Device Development] Mata99:
In my opinion you can remove AudioFX and not replace it with MusicFx, I never use them.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I use a magisk module to remove AudioFX systemlessly and I use Viper4Android instead, so no comments on audio with AudioFX. Even when I has AudioFX installed I always kept it disabled; was never of any use to me. Just give me pure proper stock sound, OnePlus. Kinda sucks I need to use root and viper to get sound that doesn't seem like the audio was put through a blender. This seems to be unfortunately true of most consumer electronics rip.
[OnePlus 3 & 3T Cross Device Development] phoberus:
Same for me, no problem to remove AudioFx. I'm using it at the moment but I can also switch to Viper4Android
[OnePlus 3 & 3T Cross Device Development] kbr0:
Removed AudioFX. No problems So far. Have never used it and would not miss it if were gone.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
I also never used it and therefore wouldn't mind not having AudioFx.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.136; remove AudioFX for now)

Build 20190223

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: 23 Feb 2019, 10:54:06 CET / 23 Feb 2019, 09:54:06 UTC):

current.pick.sh: pie-caf-imports. — Nvertigo

Rename permissions-nlos.xml to privapp-permissions-nlos.xml. — Nvertigo

Remove AudioFX. — Nvertigo

Merge tag 'v3.18.136' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-16.0 — Nvertigo

cfq-iosched: fix the setting of IOPS mode on SSDs — Jens Axboe (los/lineage-16.0

block: Make CFQ default to IOPS mode on SSDs — Tahsin Erdogan

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:
Damn... My slow boot problem is back. Around 26 seconds at the "Starting Android..." screen :-/

It's interesting that the problem wasn't there after formatting, encrypting & restoring backup (suggesting that it's not my data partition content problem), but it was right back after one or two dirty flashes of next builds.

I'm not sure, but it might be that it's getting worse with every next build flash, that's why I didn't pay attention earlier, but with today's build it reached those 26 seconds and was impossible not to notice...

Seriously, no one else facing it? If so, I will continue searching for the problem specific to my setup.

OP3T, A3010, 128Gb version. Data formatted with "fix3" TWRP.

Edit: oh, and nvertigo67 - it's not a clean flash and I have Magisk (systemless hosts + YT Vanced), so I understand You won't waste time on it. That completely fine with me. Just trying to make sure no one else is facing the same issue.
[OnePlus 3 & 3T Cross Device Development] :
I can't find anything specific I can pin down to cause your issue in the logs, but two things caught my eye:

data wasn't cleanly umounted:

[ 33.934150] e2fsck: e2fsck 1.43.3 (04-Sep-2016)\x0a
[ 33.934314] e2fsck: Pass 1: Checking inodes, blocks, and sizes\x0a
[ 33.934374] e2fsck: Inode 5111973 extent tree (at level 1) could be shorter. Fix? yes\x0a
[ 33.934428] e2fsck: \x0a
[ 33.934481] e2fsck: Inode 5185544 extent tree (at level 1) could be shorter. Fix? yes\x0a
[ 33.934533] e2fsck: \x0a
[ 33.934585] e2fsck: Pass 1E: Optimizing extent trees\x0a
[ 33.934637] e2fsck: Pass 2: Checking directory structure\x0a
[ 33.934688] e2fsck: Pass 3: Checking directory connectivity\x0a
[ 33.934740] e2fsck: Pass 4: Checking reference counts\x0a
[ 33.934791] e2fsck: Pass 5: Checking group summary information\x0a
[ 33.934844] e2fsck: [QUOTA WARNING] Usage inconsistent for ID 10036:actual (774144, 39) != expected (778240, 39)\x0a
[ 33.934897] e2fsck: [QUOTA WARNING] Usage inconsistent for ID 10173:actual (12926976, 186) != expected (12931072, 186)\x0a
[ 33.934949] e2fsck: Update quota info for quota type 0? yes\x0a
[ 33.934999] e2fsck: \x0a
[ 33.935052] e2fsck: [QUOTA WARNING] Usage inconsistent for ID 10036:actual (757760, 35) != expected (761856, 35)\x0a
[ 33.935105] e2fsck: [QUOTA WARNING] Usage inconsistent for ID 10173:actual (11972608, 129) != expected (11976704, 129)\x0a
[ 33.935157] e2fsck: Update quota info for quota type 1? yes\x0a
[ 33.935207] e2fsck: \x0a
[ 33.935256] e2fsck: \x0a
[ 33.935307] e2fsck: /dev/block/dm-0: ***** FILE SYSTEM WAS MODIFIED *****\x0a
[ 33.935360] e2fsck: /dev/block/dm-0: 180839/7421952 files (2.5% non-contiguous), 23185330/29679735 blocks\x0a
[ 33.935428] e2fsck: e2fsck terminated by exit(1)\x0a
[ 33.967414] EXT4-fs (dm-0): mounting with "discard" option, but the device does not support discard
[ 33.967488] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: barrier=1,noauto_da_alloc,discard
[ 33.967576] SELinux: initialized (dev dm-0, type ext4), uses xattr

restorecon takes over 28 seconds - quiet near the delay you expirience:

[ 63.094398] init: Command 'restorecon --recursive --skip-ce /data' action=post-fs-data (/init.rc:548) took 28846ms and succeeded

From the last_kmesg I can see no reason for 1. - anyway: your data fs wasn't cleanly umounted.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
It's strange the FS wasn't unmounted clearly. I just did a software reboot from the power menu right after the first boot to new build...

Anyway, I have no experience whatsoever with restorecon. Should I run something like "restorecon -R -v /data" on a running system? Is it safe? Can it break anything?
[OnePlus 3 & 3T Cross Device Development] :
I'm not sure, if related to your issue at all - it just caught my eye.

Running restorecon is safe, but it doesn't makemtoo much sense to do so, if files are opened already. Better to do it from recovery. But I don't think it's necessary, because the restorecon exits successfully (after 28 seconds, which cought my eye).
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Fixed it!

After countless reboots and tries it seems I'm back to decent 7-8s at "Starting Android..." screen. Not bad, considering 101Gb of data on the (ext4) data storage.

What I did:

- e2fsck in TWRP (fix3) - didn't help

- restorecon in TWRP - took ages (over 0.5h in verbose mode) - didn't help, actually made it worse for one boot

- disabled both modules (YT Vanced & systemless hosts) + denied root permission to all apps by default - IT WORKED!

- restored root permission to all apps except AdAway (it needs systemless hosts) - no change, still OK

- restored YT Vanced module - no change, still OK

- restored systemless hosts module - no change, still OK

- restored root permission for AdAway and updated hosts file - to my surprise - no change, still OK!

In other words - temporarily disabling all Magisk modules seems to be doing the trick. Even though I restored everything to as it was before, the boot time is normal again... Will have to monitor the situation, but at least now I know where to look next time it happens :)

Sorry for the off-topic. My problem had nothing to do with the ROM and was/is related to the Magisk mods...
[OnePlus 3 & 3T Cross Device Development] knpk13:
Actually I have to agree. Past week I've been noticing the color looks different after a reboot (I think it resets to standard). I ran cat on the dci-p3 node and it returned 1, and dci-p3 is the selected option in display settings as well. However, changing the display setting to something else like and then back to dci-p3 brings the color back. Can someone confirm it's not just my imagination?

I'm on ext4 unencrypted.

While we're at it, ant recommendations for a terminal emulator for Android? I can't paste commands in the inbuilt one (enabled from devops) and I've been trying out termux.
[OnePlus 3 & 3T Cross Device Development] :
As I've explained more then one time:

My visual perception's memory is not good enough to tell the difference between standard, dci_p3 and srgb after a reboot! I can see the differencies, when switching: i.e. from dci_p3 to standard. But I can't see the differnce without direct compare: i.e. when rebooting with dci_p3 and the device comes up with standard, I can't tell the difference.

If I set dci_p3 and reboot, I can't see any difference (see abvove). So I go to settings (which still shows dci_p3) and switch back to standard. When switching I see a difference: especially white gets colder.

If I check the nodes and settings file directly after reboot, it's ok (as you've stated).

If I switch after reboot from dci_p3 to standard and back to dci_p3 I see both switchings. For me the dci_p3 before standard and after standard look the same. Though I belive that you can percept a difference, I can't: for me it's the same.

Since I don't trust my visual perseption's memory, and all "measurable" facts (sysfs nodes, settings files and logcat) clearly show NO errors, I can't help you. Due to my lack of an accurate visual memory, it's possible that it's working for me, but not for you - and I'm just not able to tell because of my distrust of my own visual memory...

The only thing I'm 100% sure: if I set dci_p3 and reboot, it's not resetted to standard, because I see a difference when switching to standard!

DON'T!

Using an android device with an unlocked bootloader, a custom recovery AND NO secured boot is one of the worst ideas currently around! Like the Darwin Award (honoring people, who have died from a really stupid idea), there should be something like a "stupid data exposure award" for this setup!

Running an interactive shell directly on the device (no matter which terminal app or if rooted or not) yields strange results since 15.1. I'm using "adb shell" with adb over network - which works much better then any local shell. Before 15.1 I've used juicyssh with hackerskeyboard (for cursor keys, ESC- and ctrl-key).
[OnePlus 3 & 3T Cross Device Development] Andrea224:
[MENTION=4405529]nvertigo67[/MENTION] I know that it's not recommended, but can I dirty-flash your rom over the dianlujitao's build?
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
Try. But not recommended. Take backup first or use migrate app. That apps makes clean flash much easier if you want to save time and effort
[OnePlus 3 & 3T Cross Device Development] :
You can do what ever you want with your device, of course!

Your device, your time, your rules.

If you want to share your expirience or search for help in THIS THREAD stick to THIS THREAD'S OP. THIS THREAD is for supporting nlos while still staying readable. THIS THREAD is not for wasting time and postings (see readablility...) on hunting down phantom issues and/or side effects of using other roms settings database or other stuff resulting from not sticking to OP.

My thread, my time, my rules (as published in OP).

Rule of thumb: whenever you wonder if it's time for a clean flash, the answer is yes. This is also true for car tires and underwear.

The time (often enough not only your own) you spend on debugging strange issues and trying to fix them without clean flash is always longer, then the time it takes to clean flash and setup...
[OnePlus 3 & 3T Cross Device Development] stryker09:
Hi guys anyone have issues with charging? i.e. charges for a few mins then it just stops on it's own? It didn't happen in the previous build. Only the 23rd build. I'll get logs when I get home, just thought I'd post this first.

I'll probably clean flash just to be sure before grabbing some logs.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I haven't noticed any problems related to charging. Works fine.
[OnePlus 3 & 3T Cross Device Development] stryker09:
Thanks! probably a bad flash then, I'll clean flash and report back in a few hours
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
Hey [MENTION=4405529]nvertigo67[/MENTION]

Im running your build from 19th Feb with Caesium Kernel. (If you won't invest your time because of the custom kernel, I'm totally fine with it, too :) )

No GApps installed, no microG installed.

Filesystem is f2fs, encrypted.

I have issues with the app "DB Navigator", that it randomly crashes.

I have attached a logcat, in the hope there's something obvious that goes wrong on my device.

L
[OnePlus 3 & 3T Cross Device Development] :
I'm low on time for the next week. I can look into not before next week. Just a thought: is db navigator relaying on coarse location and cloud messaging (for real time notifications)? So you need gapps or microg for gms, arn't you?