yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4626346]t0pg3ar[/MENTION]:

First of all: thanx for the first logcat on this spotify issue.

Sadly both logs stops, when it gets interesting: a segmentation fault is generated (finally) in libc, I need to know the reason. This is in the next 20 or 30 (or even 100, if the backtrace is long) lines after the libc line.

The errors before are due to connection errora when trying to connect:

30002 30162 E COMSCORE: Caused by: java.net.ConnectException: failed to connect to /::1 (port 80) from /:: (port 49032): connect failed: ECONNREFUSED (Connection refused)

This is either an error of the remote site or some issue with your ip connection. I would bet for the first. Anyway: no matter whats the reason for the refused connection, the app shouldn't crash.

I think the real culprit is the segmentation fault.
[OnePlus 3 & 3T Cross Device Development] t0pg3ar:
No problem, I know how annoying it is to solve tech issues without any background information. Your IP suggestion made me think maybe AdAway could be in the way. Disabled it, rebooted, issue persists. So here I am with a longer logcat. This contains everything I could grab in that timespan. There surely is some more information than necessary in there, but maybe it contains what you need. It's from start of Spotify till crash, copied when the terminal went 'quiet'.
[OnePlus 3 & 3T Cross Device Development] :
Thanx again!

The segfault comes from skia and hwui. I'm pretty sure it's this: https://review.lineageos.org/q/topic:"unclipped_layers"+(status:open OR status:merged)

I'll make a new build tomorrow.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (fix spotify; mainainance)

Build 20190315

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: 15 Mär 2019, 10:06:24 CET / 15 Mär 2019, 09:06:24 UTC):

Revert "current.pick.sh: fix-aapt-warnings." — Nvertigo (HEAD -> nlos-16.0, nvertigo/nlos-16.0

Revert "current.pick.sh: unclipped_layers." — Nvertigo

Revert "current.pick.sh: p_webview_72.0.3626.121." — 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] t0pg3ar:
You are fast. Thank you very much, I can confirm I heard the splat of a bug being squashed while flashing. Spotify's working nicely again :)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (small fixes; maintainance)

Build 20190319

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 Mär 2019, 10:20:25 CET / 19 Mär 2019, 09:20:25 UTC):

current.pick.sh: disable "op3: Rewrite livedisplay HAL sepolicy" - commit has vanished. — Nvertigo

Revert "current.pick.sh: "Allow Gallery to access system_app_data_file"." — Nvertigo

op3: Rewrite livedisplay HAL sepolicy — dianlujitao

op3: wifi: Enhance move_wifi_data.sh to copy required files — Hu Wang

op3: wifi: Add move_wifi_data.sh — Abhishek Srivastava

Revert "op3: Allow appdomain to get vendor_camera_prop" — dianlujitao

op3: List additional native libraries to expose to apps — Bruno Martins

op3: Remove audio policy copy — dianlujitao

op3: audio: config: Remove 2 instance support for "primary input" — Samyak Jain

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] 64ashg:
Anyone getting generic mac 02:00:00:00:00 for wifi and no imei and bluetooth, basically all radios not working after dirty flashing the latest build? I had clean flashed the 15/03 build and dirty flashed 19/03 build over it. Dirty flashing 15/03 build turned things back to normal

15/03 build with pico gapps and magisk 18.1.

This has happened the first time on nlos (15.1 and 16). Maybe first time in general. Anyone has experienced this before?
[OnePlus 3 & 3T Cross Device Development] :
In the los thread somebody reported smething similar (crashing bt and wifi). If I remember correctly that was related to magisk modules.
[OnePlus 3 & 3T Cross Device Development] knpk13:
That's not what exactly happened with me. I dirty flashed the 19/3 from last build and it wouldn't boot. Uninstalling and reinstalling magisk fixed it and it booted. It seems that the cause was the substratum themes, since when I tried reenabling it, the system crashed and refused to boot again. So I'm uninstalling and reinstalling substratum to see if that fixes the issue. All my radios work though.

Edit: reinstalling substratum themes fixed the issue
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Removing and reinstalling magisk did the trick. Thanks :good:
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Hey, anybody know why does the

CHARGE_FULL L_DESIGN=2999

even after i have installed a new battery to my 3t? The 3 is supposed to have 2999~3000mAh but the 3t is rated at 3400mAh. I have installed an original battery from oneplus btw.

Should i clean flash again and try this? I have clean flashed 19/03 build but a few days before installing the new battery.

Thanks in advance.

Ps, i am posting this as i have seen somebody have the same problem in the forums before.
[OnePlus 3 & 3T Cross Device Development] :
Where did you get CHARGE_FULL L_DESIGN from? Kernel Adiutor and aida are reporting 3400 mAh.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
/sys/class/power_supply/battery/charge_full_design

My aida and kernel auditor also says 3400mAh but the above file is an in kernel sort of relatively accurate tool, which was added by my repeated requests in the nlos 15.1 thread for us to know how bad is the battery degradation. I was happy to see it got carried over to nlos 16 :)

It was a feature working in sultan's los 14.1 builds and then on nos oreo builds, thats where i came from to nlos. I think it should be there, the comment with sultans commit and link to nos thread in nlos 15.1 thread.

Thanks for the immediate reply :)
[OnePlus 3 & 3T Cross Device Development] :
Ah, ok. sysfs doesn't came to my mind due to the capital letters.

I've just picked it from 15.1 - but I have to admit I've never checked it.

If you look at https://xdaforums.com/showpost.php?p=77892221&postcount=1044 , my value is something with 28xx mAh on a used battery. Compared to that 2999 mAh seems ok for a new battery. Did you ever see 3400 mAh on 15.1?
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Nope, i started off with 2750ish with nlos 15.1. But that was a one and a half year old battery.

It was at 2550ish when i replaced it.
[OnePlus 3 & 3T Cross Device Development] :
Then I consider it's working like on 15.1. For me I was 2809 last October and now it's 2562. Looks plausible to me.

What do you think: just take it as is (and was) or remove it again?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Have you cleaned USB port, headset mesh as well? I remember you were saying to do that when battery replacement will be carried out.

3400mAh - that's a theoreticaly designed max capacity, which can be reached only in labaratory and under only in some circumstances. And not allowed by battery controller to preserve longlivines. Its not healthy to charge battery till bottle neck.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I'll take it as it was, and today morning i saw it had reached 3081 with normal use. I am still in the first cycle of the battery. It shows that correct. My cycles counter is zero.

I think with more cycles it should get more accurate.

Yes i got that cleaned, only the headset mesh. And it was dirty. The call quality is as good as new.

Ps the box of my battery said 3300mAh. So 3400 mAh is actually a theoretical number i guess.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.137; lockscreen shortcuts)

Build 20190324

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: 24 Mär 2019, 14:53:20 CET / 24 Mär 2019, 13:53:20 UTC):

current.pick.sh: pie-lockscreen-shortcuts. — Nvertigo

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

Revert "current.pick.sh: lineagehw-hidl." — Nvertigo

Merge tag 'v3.18.137' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-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] AndreiVolk:
Hi everyone, I'm on this rom from a few weeks and I'm happy with it. No problems untill now but I'm coming from oos and i feel that the in call volume is lower on this rom.

I found this on los thread:

https://xdaforums.com/oneplus-3t/help/low-call-volume-t3575675

but in system/vendor/etc/mixer_paths_tasha.xml i have the 2 rows to edit under <mixer> and not under <path name="speaker">(see screenshots).

Can someone tell if is the same thing before i do something stupid ? ???

Also, before flashing this rom i formated to ext4 as advised in op and i would like to encrypt my phone again. Did someone already tried to encrypt using this rom ? I searched the thread but didn't find any answer.

Thank you :D

Keep up the good work ?
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Try to clean headset's mesh from inside first.
[OnePlus 3 & 3T Cross Device Development] AndreiVolk:
I can do that but still doesn't change the fact that the in call volume is lower than on oos, at least on my device :(
[OnePlus 3 & 3T Cross Device Development] phoberus:
I did this and it helped not that much. After 1-2 days it was already low again

on line I changed now the value to 94:

<ctl name="RX0 Digital Volume" value="94" />

seems louder now
[OnePlus 3 & 3T Cross Device Development] :
I'm not at home the next three weeks. I had configured remote access to my developmemt host, but for some reason I can't access the host since a couple of hours. As a result I can't update the rom till I'm home again.
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/oneplus-3/one...1-20180223-t3754855/post78334059#post78334059

If you really run out of mem, search the mentioend thread for "sdf5"... ;)
[OnePlus 3 & 3T Cross Device Development] abhibnl:
wow! This was one of the most knowledgeable content i've read recently on XDA. Thanks for this and thanks for explaining why ZRAM could actually help even when there is high physical RAM available.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Deleted, sorry
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
some years ago, there was an awesome lightweight gallery called QuickPic, but it was ruined after it was bought by Cheetah Mobile

this is a modified version without the Cheetah Mobile crap

https://xdaforums.com/android/apps-games/mod-gallery-quickpic-based-4-7-4-t3790425

you can clearly feel how fast it is. even oneplus gallery app has now over 50mb apk size :eek:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Lol that's why I was asking xD

I couldn't find a replacement for quickpic after it was bought. I kept using it while trying out alternatives but finally decided to switch when I upgraded to Pie as it hasn't been updated in over a year. And that pink text finally put me over the edge. Thanks, I'll check out the link. The inbuilt gallery with the swift black theme suffices for now though.

Edit: I'm not sure how the mod is being updated when the original app was last updated last year. Interesting. I love the mod though. Seems like it's a missing a couple options from before cheetah took over though. We should probably continue this in the mod thread though.
[OnePlus 3 & 3T Cross Device Development] :
Did you consider reading the commit you've just quoted? The Helium-Hassium issue is explicitly addressed - as well as some more...

Really? Use the rom shipped soundpicker: it's not crashing, but working like charme. For me ps is not even offering com.google.android.soundpicker.

If you arn't sure, what you have done to your setup ("I'm not sure if it's part of the ROM or part of gapps."), clean flash according to OP: if you think you have found an issue clean flash with only gapps pico or nano and reproduce.

Dude, please don't create bugs to report if you can't find any.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.130; SDCLANG-6; busybox; fix alarm sounds; fix ogg playback)

Build 20181218

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: N/A currently.

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

Changelog (Last repo sync: 18 Dez 2018, 17:26:15 CET / 18 Dez 2018, 16:26:15 UTC):

Revert "libcameraservice: force specific cam id for google face unlock". — Nvertigo

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

NLOS: bring back NLOSWallpaperPicker. — Nvertigo

NLOS: bring back busybox. BB rulez... — Nvertigo

current.pick.sh: fix typo. — Nvertigo

NLOS: track our own hardware/qcom/power. — Nvertigo

current.pick.sh: system/nfc: SDCLANG-6: fix declaration. — Nvertigo

NLOS: qcom native Snapdragon llvm 6.0.9 toolchain. — Nvertigo

NLOS: op3/t: use upstreamed kernel. — Nvertigo

current.pick.sh: "Sounds: Squashed cleanup of sound files". — Nvertigo

binary: Append cc/cxx wrapper to sdclang — Luca Stefani

build: Require devices to opt-in for SDCLANG — Steve Kondik

Turn off sdclang for cfi sanitizer — Pengxuan Zheng

Add support for using the secondary SDLLVM toolchain — Pengxuan Zheng

Control building shared libs, static libs and executables with SDLLVM LTO — Pengxuan Zheng

Add support for building with proprietary compiler — Pengxuan Zheng

NLOS: move from alpha to beta. — Nvertigo

Revert "Revert "op3: Build with SDCLANG"" — Nvertigo

op3/t: Convert lights HAL into a native binderized HAL — Bruno Martins

op3/t: display: adjust s6e3fa5's config to color profile name mappings. — Nvertigo

op3/t: audio: fix ogg/vorbis playback. — Nvertigo

treewide: fix alignment warnings for gcc-8.x. — Nvertigo

fs: Workaround the compiler's bad optimization — Nikhilesh Reddy

[WIP] treewide: various fixes for gcc 7.x warnings. — Nvertigo

Merge remote-tracking branch 'stable-upstream/linux-3.18.y' into linux-stable/merge-16.0 — Nvertigo

Merge remote-tracking branch 'nc/lineage-16.0' into linux-stable/merge-16.0 — Nvertigo

Merge branch 'kernel.lnx.3.18.r34-rel' of https://github.com/android-linux-stable/msm-3.18 into lineage-16.0 — Nathan Chancellor

Merge 3.18.129 into kernel.lnx.3.18.r34-rel — Nathan Chancellor

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:
Well, a huge job done, nice movement is going on! Even jump to beta!

Regards.
[OnePlus 3 & 3T Cross Device Development] Oswald Boelcke:
beautify your pie

The dark mode is not in Settings->Display (like in 15.1) any more, but in Settings->devops->Night mode.

I wouldn't have looked there, if I wouldn't have seen it in the commits... Hope it helps one or another from getting blinded by a massive amout of white... ;)

EDIT:

Just finished a clean flash (too much testing the last days) and - know what? - Settings->Display->Design is back... ;)
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Well, good news. Got 5t 8/128gb version today for cry cheap, 240€. Hope you're going to support this model someday as well. Will pass my beloved 3t to son.

Regards.
[OnePlus 3 & 3T Cross Device Development] :
Highly unlikely. I'm planing to use my 3t for another year. Since I'm nly developing for devices I've my hands on...
[OnePlus 3 & 3T Cross Device Development] :
Will be fixed in the next build: https://review.lineageos.org/c/LineageOS/android_device_oppo_common/+/236894
[OnePlus 3 & 3T Cross Device Development] abhibnl:
This actually gives me hope to switch to NLOS once there is no more support from OOS team after Pie release. As of now, i am really happy with the Oreo OOS and the stability is just too good to ditch but i think i'll need to eventually upgrade to latest android version. This is definitely a ROM to keep an eye on
[OnePlus 3 & 3T Cross Device Development] :
To all users having tried other pie roms:

On 15.1 the bt status icon was there as soon as bt was enabled, and gets "brackets" if a device was conmected. But even unconnected the icon signaled "bt is on - danger!" to me.

On 16.0 the icon only shows up if something is connected. Is this changed intendedly for pie, or is this a b7g worth spemding time on? (I'm afraid it's no bug...)
[OnePlus 3 & 3T Cross Device Development] mk_1996:
That's not a bug i can confirm. That's how bluetooth works on pie
[OnePlus 3 & 3T Cross Device Development] knpk13:
None of my notifications from messaging apps or SMS go away when I click on reply or mark as read. They still stay in the notification drawer until I swipe them away, but the icon from the status bar disappears. Clicking on reply or mark as read in Oreo caused the notification to go away. I'm not sure if what I'm experiencing is the intended behavior in Pie. This the log from clicking on mark as read multiple times on a notification from the Telegram app.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Unfortunate. At least it still shows as turned on when you swipe down from the status bar (the quick settings toggles I think is what you call them?)
[OnePlus 3 & 3T Cross Device Development] :
Can anybody comfirm this for the shipped SMS/MMS app? For me the the notification vanishes as soon as I tap on "mark read".
[OnePlus 3 & 3T Cross Device Development] :
I don't use telegram, and I don't know what to look for. I can't see any errors in the androisd system.

EDIT:

This seems to be a telegram problem - but I don't know if related (for closed source apps, it's better to ask the dev, he knows his code), this just states, that there is no notification with the key telwgram refers to:

12-19 14:56:02.163 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:04.078 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:05.376 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:05.797 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:06.048 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:06.293 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:06.493 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:06.698 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:06.930 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:15.117 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|10112
12-19 14:56:16.067 W/NotificationService(806): No notification with key: 0|org.telegram.messenger|-152977827|null|1011
[OnePlus 3 & 3T Cross Device Development] cukierkas:
No bug at all. Really handy. It tries to follow iOS lead and that's not too bad.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Enjoy the enforced "holiday" :laugh:
[OnePlus 3 & 3T Cross Device Development] stevenkyk:
Recently I finally found the time to update from 15.1 to 16 via a clean flash. After setting everything up then I realised something wrong with location settings. I understand that pie made location a binary setting, however, network based location fails to work without turning on WiFi scanning. Back on 15.1, I always stuck to battery saving mode with WiFi & BT scanning off and network based location works without a hitch. Now on 16.0, whenever I'm indoors or when the app doesn't request a high accuracy location, location is broken with WiFi scanning disabled.

I was running opengapps nano from 20190406 initially, even made a switch to mindthegapps 20190216 and let it automatically update to latest play services before testing. All results are the same.

TL;DR does network based location work for anyone without WiFi scanning?
[OnePlus 3 & 3T Cross Device Development] :
What you describe is perfectly matching the explenation here: https://developer.android.com/guide/topics/connectivity/wifi-scan

(BTW: I've always thought that allowing wifi state change to apps requestimg coarse location - no matter if wifi scanning is allowed by user settings - is a serve security risk in 15.1.)
[OnePlus 3 & 3T Cross Device Development] stevenkyk:
So I assume wifi scanning also covers cell tower scanning? My main concern is that wifi is active as long as wifi scanning is allowed, not sure how much of an impact will it be on battery.
[OnePlus 3 & 3T Cross Device Development] :
I don't know.

If wifi is switched off and wifi scanning is enabled, the wifi hardware is only switched on if wfi is actually scanned. That's why apps need to request wifistate change in addition to coarse location to use wfi based location service.

BTW: Since the gps modules are better optimized for bat life compared to 5 or ten years back, the saved bat life in power saving mode (aka wifi-, bt- and cell tower scanning) is marginal. I some situations (i.e. navigation app in car) wifi location service eats much more battery then gps only mode. I would highly recommend using just gps, because you don't know what g is doing with your location data, like selling them to to antidemocratic companies like oxford analytica or alike... :( :( :( ...and only use wifi based location services, if an app you really need is relaying on. I would not use an app relaying on network services that enables g to collect your location data.
[OnePlus 3 & 3T Cross Device Development] :
My neighbour offered a backup connection to my development host. That's great and I'm thankfull for that!

Sadly that's only a 2Mbit/500KBit link. resulting in

rsync.exe -P -e "ssh -p xxxx" some_ip:/mnt/export/data/src/los16/out/target/product/oneplus3/nlos-16.0-2019040
8_120235-beta-oneplus3t.zip /c/Users/ingo/Downloads/
The authenticity of host '[some_ip]:xxxx ([some_ip]:xxxx)' can't be established.
RSA key fingerprint is foobar.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[some_ip]:xxxx' (RSA) to the list of known hosts.
Password:
nlos-16.0-20190408_120235-beta-oneplus3t.zip
12681216 1% 44.90kB/s 4:01:23

At least -P allows to keep the allready downloaded part, if the connection breaks...

So perhaps this night or tommorow we will have an update with Aprils security patches...
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Gutten tag, hope you haven't forgotten naggy user :D How your holidays?

Still thinking not to make a 5t port of your lovely rom? :) Missing it's rock solid performance :D