yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Dirk:
Oof, that's some difference!
[OnePlus 3 & 3T Cross Device Development] helderfp:
Latest from tolyan

https://www.celsoazevedo.com/files/android/google-camera/dev-tolyan009/

First picture is from Gcam second from snap
[OnePlus 3 & 3T Cross Device Development] Badd_blood:
I'm currently on 15.1 nightly. Is this planned to be an official nightly build later on or is this a separate project?
[OnePlus 3 & 3T Cross Device Development] legendavey:
Thanks to all the hours spent and the awesome work by [MENTION=5091734]dianlujitao[/MENTION], this should (hopefully) eventually make it to official nightly status once the LOS team releases 16.0 officially. :)
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
The latest repo failed to build with the following error:

[ 30% 29515/97012] build /LineageOS/16.0/target/...uct/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolic
FAILED: /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy
/bin/bash -c "(ASAN_OPTIONS=detect_leaks=0 /LineageOS/16.0/host/linux-x86/bin/checkpolicy -M -c 30 -o /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf ) && (/LineageOS/16.0/host/linux-x86/bin/sepolicy-analyze /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp permissive > /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains ]; then echo \"==========\" 1>&2; echo \"ERROR: permissive domains not allowed in user builds\" 1>&2; echo \"List of invalid domains:\" 1>&2; cat /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.permissivedomains 1>&2; exit 1; fi ) && (mv /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy )"
device/oneplus/oneplus3/sepolicy/hal_livedisplay_default.te:2:ERROR 'unknown type hal_livedisplay_default' at token ';' on line 79953:
allow hal_livedisplay_default sysfs_livedisplay:file { { getattr open read ioctl lock map } { open append write lock map } };
#line 1 "device/oneplus/oneplus3/sepolicy/hal_livedisplay_default.te"
checkpolicy: error(s) encountered while parsing configuration
/LineageOS/16.0/host/linux-x86/bin/checkpolicy: loading policy configuration from /LineageOS/16.0/target/product/oneplus3/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf
[ 30% 29520/97012] //frameworks/base/libs/services:libservice.../core/java/com/android/internal/os/IDropBoxManagerService.cp
ninja: build stopped: subcommand failed.
09:32:14 ninja failed with: exit status 1

It's not ready for nighty yet
[OnePlus 3 & 3T Cross Device Development] legendavey:
You do know that LineageOS is in the middle of migrating LineageHW to treble-friendly HALs, right? If you check our device on gerrit, you'll see our maintainer working overtime to get LiveDisplay 2.0 working properly on our device after LOS deprecated 1.0 - your logs seem to indicate that you should hold off on personal builds until that work is done. :)
[OnePlus 3 & 3T Cross Device Development] ivanich:
Actually you need to apply a few commits from Gerrit
[OnePlus 3 & 3T Cross Device Development] :
You are right. [MENTION=4329165]ivanich[/MENTION] and [MENTION=7403273]legendavey[/MENTION] are right, too. I belive that's why we havn't nightlies, yet... ;)

to fix the above you need to pick these (at least, and even if these fix this error you maymrun in other errors):

# op3: Convert TouchscreenGestures to touch HAL
safer-repopick 241212 -P device/oneplus/oneplus3/

# op3: Convert KeyDisabler to touch HAL
safer-repopick 241213 -P device/oneplus/oneplus3/

# op3: Migrate to livedisplay 2.0
safer-repopick 240885 -P device/oneplus/oneplus3/

# op3: livedisplay: Support sysfs backend display modes
safer-repopick 241174 -P device/oneplus/oneplus3/

# lineagehw-hidl
safer-repopick 241116
safer-repopick -t lineagehw-hidl -e 241116,241004
safer-repopick 241004 -P lineage-sdk/

From: https://github.com/nvertigo/local_manifest/blob/nlos-16.0/current.pick.sh

Since the com0lete hidl stuff is still wip, you may need to resolve a confict and follow gerrit regulary to know what to pick. Also watch out: for the hidl topic i.e. you need to pick the revert before picking the rest: the commit id's order is not the order of the relation chain.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Hey [MENTION=4405529]nvertigo67[/MENTION], just wanted to add that your regularly updated repopick list on github was a LOT of help some time ago when I did my own early builds of LOS 16! :good: :)
[OnePlus 3 & 3T Cross Device Development] :
hidling lights

[MENTION=5091734]dianlujitao[/MENTION]:

I remember you havn't liked this one for 15.1. Would you like to see this in gerrit for 16.0, when everything is "hidled" anyway?

https://github.com/nvertigo/android...mmit/1469ddee766aa237c89726ae8b76bda12dc3f40f
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
No, there's no noticeable benefit from the conversion, the "legacy" hal is still used even on pixel3
[OnePlus 3 & 3T Cross Device Development] Chol:
We are getting closer ... wiki: Promote remaining 16.0 day-one ship devices :)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Successful dirty update (only wipe caches) with the last build (lineage-16.0-20190210-UNOFFICIAL-oneplus3.zip) ... :good:

Very stable ROM and no bug for the moment .... Many thanks dianlujitao !
[OnePlus 3 & 3T Cross Device Development] laupuy:
Yep, thanks sir dianlujitao and happy Chinese new year ?

Changelog

2019.2.10:

Sync latest source

Update kernel to LA.UM.7.5.r1-04100-8x96.0

Livedisplay & touchscreen gestures internal API migration

Allow disabling new USB gadgets when the device is locked

Minor bug fixes
[OnePlus 3 & 3T Cross Device Development] laupuy:
It's ok in last build ;)
[OnePlus 3 & 3T Cross Device Development] Phaech4x:
why "show CPU info" is not available in developer options? that option supposed to be under "WebView implementation". is this a bug? on 20190210, same on 2019.1.24 build.

update: nvm, seems this option was removed from AOSP years ago. some of other ROM have patch to implement this feature, but lineageos not.
[OnePlus 3 & 3T Cross Device Development] legendavey:
[MENTION=5091734]dianlujitao[/MENTION] not sure if this is reproducible on your end, but I found that USB debugging won't stay disabled if I turn it off, it is re-enabled every time I reboot the device.
[OnePlus 3 & 3T Cross Device Development] 666biker:
Hello did someone dirty flash 12.Jan. -> 10.Febr.? I made it, and circle battery percentage option is gone. Or enabling this feature was moved somewhere? thanks
[OnePlus 3 & 3T Cross Device Development] laupuy:
It's gone, the option is no longer available.
[OnePlus 3 & 3T Cross Device Development] 666biker:
temporary or not planned anymore for LOS 16? (circle battery with percentage). Also landscape battery indicator with percentage inside will be sufficient :)
[OnePlus 3 & 3T Cross Device Development] Andrea224:
Battery style setting is still WIP, so we have to wait. Maybe once LOS 16.0 will be official there it will be or maybe even before, nobody knows it exactly.
[OnePlus 3 & 3T Cross Device Development] :
"Maybe" is the keyword here. Maybe pie-battery-styles never gets merged like for oreo-battery-styles... It's much easier for [MENTION=5091734]dianlujitao[/MENTION] to pick something to this beta builds, then getting something merged to the official version. Official is not always better then beta...
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hmm, wait and see https://ausdroid.net/2019/02/12/lineageos-starts-rolling-android-9-0-pie-nightlies-v16-0/amp/

;)
[OnePlus 3 & 3T Cross Device Development] legendavey:
I think the guy who wrote the article got a little carried away. The wiki, download site and blog haven't been updated yet. So maybe it's best to wait, like you said. :highfive:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
In version 190210, there's a small bug in the Messaging app: irrespective of what sound I've selected for the notification in Messaging>Settings>Notification it always plays the default sound set in Settings>Sounds>Default notification sound.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
[MENTION=7403273]legendavey[/MENTION] [MENTION=6561751]pedritopl[/MENTION] [MENTION=4405529]nvertigo67[/MENTION] Can you guys check if there's WhatsApp/CamScanner bug in the latest build? The hal1 package list implementation changed a bit and we'd like to know if the new impl works
[OnePlus 3 & 3T Cross Device Development] :
I'm on the road, I can do a build tomorrow evening (hopefully) or on Saturday.

The simplification looks good on a first glance.

Just a thought: I don't understand, when original caf/aosp patches are prefered, and when simplefications are aproppriate...
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
original caf patches are never preferred, we always clean up before merging
[OnePlus 3 & 3T Cross Device Development] legendavey:
I tested both WhatsApp video calls and CamScanner image quality just now and there is no video lag/quality loss on my end. Same as the previous builds. [MENTION=6561751]pedritopl[/MENTION] please confirm if you have the same results for these apps on your end.
[OnePlus 3 & 3T Cross Device Development] :
Sadly it's not that straight forward. I.e. here it's just the other around: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/218486
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm on latest NLOS build. No problem in CamScanner at least, but NLOS uses other approach to this than pure LOS, so I'm not sure if this helps.
[OnePlus 3 & 3T Cross Device Development] legendavey:
You're right. NLOS uses a different approach and while it works (a friend has tested the fix it employs) it isn't the same as the workaround used by LOS.

Although I think (personal opinion) that the package specific approach used on LOS is better.
[OnePlus 3 & 3T Cross Device Development] :
That's not the question.

The question is, if the simplified code (which not only looks good, but should also be less expensive) is working as the original caf commit is. Which is already comfirmed by [MENTION=7403273]legendavey[/MENTION].

We can't use the fw/a (NLOS) solution for LOS, because it changes android's default behavior. Which is ok for builds only for op3/t, but shouldn't be in a device tree for auto building for ALL devices.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
On device side I personally prefer keeping the original CAF **** if they're harmless just for easier upgrading, there're indeed other maintainers cleaning up those stuff.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
With the last build (lineage-16.0-20190210-UNOFFICIAL-oneplus3.zip), a color SIM label change seems lead to a SIM issue.

To be confirmed.

A backup re-install removes this one.

Many thanks dianlujitao for this very stable ROM !
[OnePlus 3 & 3T Cross Device Development] Antwar:
I cannot charge with phone off on this version ( -16.0-20190206) just charge loops (vibrates show battery symbol with tiny red band) charges fine when switched on.

Tried dirty and clean install got the same charge issue with both.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No problem with the charge (phone off and on) with the last build (2019/02/10).

---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------

No problem with the charge (phone on and off) with the last build (20190210).
[OnePlus 3 & 3T Cross Device Development] kkwete:
Hi.

Just fresh installed last LOS 15.1 on my OP3.

But not easy to have a "vibrate only" option with slider...!

I 'll try LOS 16 but I'm not sure...I have to flash latest stable firmware before flashing LOS. I found stable 5.0.8. Good?

I don't find post with all flashable firmwares....sorry!
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
5.0.8 is the newest one.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] laupuy:
OP3?

here you go: https://www.celsoazevedo.com/files/android/oneplus3-modem-firmware/
[OnePlus 3 & 3T Cross Device Development] kenboyles72:
I'm guessing that live display is going to get optimized for less power consumption? I like live display, but drains way to much battery compared to other phones with native support.
[OnePlus 3 & 3T Cross Device Development] kkwete:
Great!

Better to flash latest stable version or latest openbeta?

And is it possible to root this version? To install AdAway...

;)
[OnePlus 3 & 3T Cross Device Development] :
Since ob has ended before 5.0.8 was released, 5.0.8 is the most current fw. 5.0.8 is also the image most of the blobs for the current 16.0 build are taken from (also true for 15.1. - not sure weather 15.1's OP is updated accordingly, or still recommends latest ob). Follow [MENTION=4756384]Der-Knuffi[/MENTION]'s advice and use 5.0.8 from [MENTION=6849132]laupuy[/MENTION]'s link.
[OnePlus 3 & 3T Cross Device Development] laupuy:
1. stable and latest 5.0.8 as nvertigo67 said (Open beta is over)

2. Yes, I'm not root but the dev released addon su:

2019.1.1:

Working unofficial SU addon: https://androidfilehost.com/?fid=11410963190603887268

or use magisk...

PS.

Blokada is very good as alternative to root+adaway: https://blokada.org/
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Use latest stable Magisk (18.1) for root. It works fine.

Edit: DNS66 is also a great ad blocker (no root needed) https://xdaforums.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497/post69303673
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION], here's another bug (which has been around for a while). When connecting to a public wifi that pops up a page to action (agree, etc) before giving you access to the internet, then I don't get the notification that I need to action the login and the input page isn't displayed. This means I cannot connect to the internet using this public wifi.

I've attached logs. I'll try to attach a screen shot of what the notification looks like on OOS, but it may take me a while to do that.
[OnePlus 3 & 3T Cross Device Development] kkwete:
I just fresh flashed LOS 16 on my OP3, and all works fine with 5.0.8 OOS fw and modem.

No problem at all.

I'll compare root with adaway, or DNS66 without root.

Really thx!
[OnePlus 3 & 3T Cross Device Development] legendavey:
Ah you're talking about the captive portal that pops up to let you sign in with a user/pass or your phone number, right? I dunno why, but it has worked for me since the first LOS 16 beta builds.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Same here, at least with Unifi hotspot portals which is the most common where I live.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] kkwete:
I've no led notification.

Is it normal or a bug?

Thx!
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

a bug, it works on my side ;)
[OnePlus 3 & 3T Cross Device Development] :
Lucky you! ;)

led notification has some "hickups" since 15.1:

Apps coming with there own led setting (like k9 and whatsapp) work most of the time (one out of five notifications doesn't trigger the led - occurs randomly.

Some pps without own led settings never ever triger the led. I.e. google notes. Neither with auto select color, nor with explicitly setting color and freq in the per app settings makes the led shine. The last time I saw a notification light for google notes was in 14.1.

I'm hunting this ****er since the first 15.1 builds to no advance. :( There's something horribly wrong with led notifications. LightFlow works, but increases bat usage while screen off by about ~0.3%/h.
[OnePlus 3 & 3T Cross Device Development] laupuy:
arf, sorry I'm not power (app) user so led works for my apps (phone, sms, telegram...) :D
[OnePlus 3 & 3T Cross Device Development] :
I was kidding, no reason for a sorry.

For completeness (I always hope somebody knows what's going wrong, if the description is detailed enogh) for inbuild apps (like you mentioned: phone, sms, mms etc.) you can set a custom color and freq and it's working.

Honestly: I give a **** if notes is working or not, I just like it for testing, because I think if any third party app is properly migrated to o, it's one of googles app. It's also easy to trigger a notification with notes... So I guess notes is perfect for testing.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I've no idea, according to the logcat your portal DOES return http204, you should've been redirected to login page

02-18 07:18:51.176 D/ConnectivityService( 2499): reportNetworkConnectivity(102, false) by 10019
02-18 07:18:51.176 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 102]( 2499): Forcing reevaluation for UID 10019
02-18 07:18:51.178 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 102]( 2499): PROBE_DNS connectivitycheck.gstatic.com 1ms OK 172.217.25.131
02-18 07:18:51.179 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 102]( 2499): PROBE_DNS www.google.com 2ms OK 172.217.167.68
02-18 07:18:51.187 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 102]( 2499): PROBE_HTTP http://connectivitycheck.gstatic.com/generate_204 time=6ms ret=204 request={User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36]} headers={null=[HTTP/1.1 204 No Content], Content-Length=[0], Date=[Sun, 17 Feb 2019 20:18:51 GMT], X-Android-Received-Millis=[1550434731186], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1550434731180]}
02-18 07:18:51.188 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 102]( 2499): PROBE_HTTPS https://www.google.com/generate_204 time=7ms ret=204 request={User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.32 Safari/537.36]} headers={null=[HTTP/1.1 204 No Content], Alt-Svc=[quic=":443"; ma=2592000; v="44,43,39"], Content-Length=[0], Date=[Sun, 17 Feb 2019 20:18:51 GMT], X-Android-Received-Millis=[1550434731187], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1550434731180]}
02-18 07:18:51.189 W/BroadcastQueue( 2499): Background execution not allowed: receiving Intent { act=android.net.conn.NETWORK_CONDITIONS_MEASURED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
02-18 07:18:51.190 D/ConnectivityService( 2499): NetworkAgentInfo [WIFI () - 102] validation passe
[OnePlus 3 & 3T Cross Device Development] ToKnight:
Are there any news on wireless charging?
[OnePlus 3 & 3T Cross Device Development] :
This is a thread in op3/t's development forum. op3/t does not have hardware support for wireless charging. Most probably you posted in the wrong forum/thread.
[OnePlus 3 & 3T Cross Device Development] simthadim:
The phone does not have the hardware for wireless (i.e. magnetic) charging. There are kits available, though I'd presume this to be such a rare case... ;)
[OnePlus 3 & 3T Cross Device Development] :
Those kits will work out of the box. The available kits (i.e. https://qi-wireless-charging.net/oneplus-3t-wireless-charging/ ) are connected to the usb jack. For the device (and therefor for the OS) it looks like charging via usb - no reason to implement wireless charging on the OS side, because 7sb charging is already implemented.

And to be "that one" again: since the additional hardware is wired to the usb jack, the term "wireless charging" isn't really correct. It's a "wireless charging receiver for usb-c".

This is a nice writeup on oneplus' philosphie: https://www.xda-developers.com/oneplus-explains-wireless-charging/
[OnePlus 3 & 3T Cross Device Development] 666biker:
should be this camera viewfinder issue / damage or LOS issiue?

I dont know what should happened, no crash, no scratch on camera lens just noticed during taking photo.

left up corner on image

https://ibb.co/b7ByTSL
[OnePlus 3 & 3T Cross Device Development] BillGoss:
To me, that looks like dust on the camera sensor. I've had that on my DSLR camera. But I have no idea how you'd go about removing the dust on the phone. And I can't imaging how dust world get on to the sensor in a sealed phone.
[OnePlus 3 & 3T Cross Device Development] Chol:
oneplus3 is not in the initial 16.0 list :( hudson: The real lineage-16.0 ship commit
[OnePlus 3 & 3T Cross Device Development] legendavey:
Relax. It will be, when it is ready. If it isn't, it'll be in the next batch. Either way, we already have a *perfectly* functional beta build so sit tight and keep your fingers crossed! ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thank you both for your responses. I've been doing dirty installs since November 2018. I now did a clean install of 190210 and captive portal is working fine. The new install also fixed up some other odd problems I was having.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Yeah sometimes a clean flash is all you need. It *should* be a prerequisite to reporting bugs, IMO. Only bug reports on clean flashed devices should be accepted. :cowboy:
[OnePlus 3 & 3T Cross Device Development] morteza-25:
I think it is now ?
[OnePlus 3 & 3T Cross Device Development] Flounderist:
Op3 is in the list :cowboy:
[OnePlus 3 & 3T Cross Device Development] Roman91:
what does it mean? nightlys are near?
[OnePlus 3 & 3T Cross Device Development] realtos:
means bringup
[OnePlus 3 & 3T Cross Device Development] Mcenzie:
Can anyone please post the roomlist for selfbuilds? Thx
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/nvertigo/local_manifest/blob/nlos-16.0/oneplus3t.xml

sed -e 's/nlos/LineageOS/g' and remove revision
[OnePlus 3 & 3T Cross Device Development] unimke:
Does lineage OS support Japanese language?
[OnePlus 3 & 3T Cross Device Development] caryle:
Yes
[OnePlus 3 & 3T Cross Device Development] unimke:
Guys anyway to install pixel luncher on this rom? I installed the APK from APK mirror but it force closes.
[OnePlus 3 & 3T Cross Device Development] skythian:
Rootless Pixel Launcher and Pixel Bridge Companion (sideload)
[OnePlus 3 & 3T Cross Device Development] philstar:
In my opinion the call volume is very, very low, even if it set to max.

Is there any possiblity to increase i further?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Have you looked at this thread? https://xdaforums.com/oneplus-3t/help/low-call-volume-t3575675/post71499375
[OnePlus 3 & 3T Cross Device Development] philstar:
Thansks for your fast reply, worked perfectly. I followed the instructions on the reddit post, which was linked in this thread, if somebody else has the same issue (https://www.reddit.com/r/OnePlus3T/comments/aa7lk3/earpiece_low_volume/ecpp2mp/). I just had to increase the one mentioned value.
[OnePlus 3 & 3T Cross Device Development] unimke:
Anyway to make the Google feed page on the home screen turn dark when the system theme is set to dark?
[OnePlus 3 & 3T Cross Device Development] realtos:
see google settings or right place to ask, maybe google sections? this rom dont have any google built in so its not op3related
[OnePlus 3 & 3T Cross Device Development] Playa82:
it's gettin Close :)

https://review.lineageos.org/c/LineageOS/hudson/+/242408
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Not yet LineageOS 16.0 Official for OnePlus 3/3T

==> https://www.lineageoslog.com/
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=5091734]dianlujitao[/MENTION], when I try to set an image for myself in settings>system>multiple users I get an error (see attached screenshot) when using the stock gallery app, but it works ok if I use Google Photos.

Logs attached.

I'm on 190210.