yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] abhibnl:
He has indeed switched full-time to Pixel 2 as per his last update. I beliebe he is only developing Kernels now since Pixels already have good and clean stock ROMs. I haven't seen a single developer who praises OnePlus' kernel code. Everyone says it's pure garbage and they don't know how to even release a source code properly. I am planning to leave OP phones for good. I just hope to keep on using this device til I see an affordable S855 flagship in my country. (maybe 6 more months)
[OnePlus 3 & 3T Cross Device Development] :
kernel sources

[MENTION=5091734]dianlujitao[/MENTION]:

Would you explain the latest forced update on the kernel sources, please?

From your comment on this commit (https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8996/+/239775 ) I can guess you rebased the kernel sources, but neither in gerrit, nor in the pushed sources I can find a hint what the actual base is, you rebased on top of.

Thanx for all your effort and time you spend on our outdated ex-flagship!!! op3/t rulez (with los)!!!
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
The base is um7.5-04000, and the only difference is that commit.
[OnePlus 3 & 3T Cross Device Development] :
Out of curiousity (and hoping to learn): why did you rebase instead of merge?

I don't want to rush you, I just want to make sure you havn't missed: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post78598792#post78598792 .
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
In case I missed it again when next time rebase the kernel

My carrier doesn't use manual network selection so cannot fix, it seems to be a problem with qti telephony extension.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
What do You mean by that? No carrier support is needed. Just try switching from automatic network selection to manual and select any carrier (your own for example). It doesn't matter which You choose because it doesn't work and exits to the Settings app, one level up.

Anyone has any idea when exactly was this bug introduced? I noticed it on January 5th. Maybe we could find the commit that causes this.
[OnePlus 3 & 3T Cross Device Development] Andrea224:
[MENTION=5091734]dianlujitao[/MENTION] why on update 24/01 did you revert the battery styles setting?
[OnePlus 3 & 3T Cross Device Development] :
Are you sure it was working in December's builds? I'm asking, because I havn't tried in December, and have always thought it was an issue since 16.0...
[OnePlus 3 & 3T Cross Device Development] ele95:
very very buggy
[OnePlus 3 & 3T Cross Device Development] Andrea224:
Fine, I was thinking about the fact of it being WIP yet. Well, let's wait again.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hmm... Now that you're asking - no, I'm not sure. I checked my history of installed builds and it turns out that I switched from 15.1 to 16.0 with the NLOS 20181230 build - and the problem was already there :-/ Sorry.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Ok, successfully reproduced, will dig later
[OnePlus 3 & 3T Cross Device Development] karmo82:
Actions Services

Any idea how to make smart predictions work? I use Pixel 3 launcher from

https://xdaforums.com/android/apps-games/app-unmodified-pixel-3-launcher-t3852857

I've granted all pixel 3 and actions services permissions & notifications including in Privacy Guard. I also tried updating the apps to the latest build but still no luck.
[OnePlus 3 & 3T Cross Device Development] :
Please honor OP: mods are not supported in this thread. I'd suggest you ask in the mod's thread.
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
Any way to get back battery percentage on status bar on last build?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] legendavey:
I combed through the entire system settings but no luck. Battery styles appears to be WIP, so I'd wait for a couple of builds for it to get fixed. Or else, it'll be ready when LOS goes official.
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
I managed to find it by searching "percentage" on system settings and it takes you under battery setting and there you can try to enable it, but unfortunately nothing happens [emoji25]

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
First, thank you Dianlujitao for this ROM and for your hard work ... :good:

The previous release (15th january) was a very smooth ROM but I confirm that the above issues occur with the new update (24/01).

Note that I have installed the last release from a dirty install.

Perhaps a clean install will remove all problems and everything will be working really fine ... Right ?
[OnePlus 3 & 3T Cross Device Development] jianwen03:
I built this rom according to this instruction and now my phone reboots to fastboot whenever I try to reboot to system. (Reboot to system>Splash screen before bootanimation>Phone suddenly reboots>Now at fastboot)

Tried to use "adb logcat" during boot but it stays at "waiting for device" until the phone reboots to fastboot...

Any method I can use to help myself?
[OnePlus 3 & 3T Cross Device Development] qasimtb:
Hi [MENTION=5091734]dianlujitao[/MENTION] I am not able to use Volte on my Airtel connection. Tried everything like Volte hacks but in vain. Do you know how I can enable it. Or do you need any type of logs or something to check for it. The same happens in 15.1 too.

I know some ROMs in which it is working flawlessly.

Thanks in Advance
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
If it's not supported on oxygenos, it's not supported here.
[OnePlus 3 & 3T Cross Device Development] legendavey:
It works on OOS, but for some reason the MCC MNC list for Airtel India seems to be incomplete. I would put up a commit for those missing entries but I can only test for Mumbai.
[OnePlus 3 & 3T Cross Device Development] realtos:
did the commands but still dont work. attached logcat from boot to after fail.
[OnePlus 3 & 3T Cross Device Development] :
Whatever you attached here, no logcat contained.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I think it was a bug report
[OnePlus 3 & 3T Cross Device Development] realtos:
hmm used alogcat now and outputted this, hope they are real logs
[OnePlus 3 & 3T Cross Device Development] :
The logs are crippeled: timestamp and ppid column are missing pid is moved. The first one has some kind of format tags included... None of them is done with my modified apns-conf.xml, only the los shiped one comtains 172.16.1.25 as mms proxy address:

I/MmsService( 2120): [SendRequest@2ec2993] Using APN [type=mms mmsc=http://mms mmsproxy=172.016.001.025 mmsport=8799 name=3MMS apn=data.tre.dk bearer_bitmask=0

172.16.1.25 is part of 172.16/16 which means it is reserved for private networks. Therefor it's droped on every router on the internet. In other words: that can't work at all.

Before continuing testing, make sure you use my apns-conf.xml and check in the apn settings that mmsproxy is "mmsproxy.3.dk".

As long as mmsproxy is 172.16.1.25 it will never work - even not with three crippeled logcats... ;)

(For reference: https://tools.ietf.org/html/rfc1918 )
[OnePlus 3 & 3T Cross Device Development] realtos:
okay thanks.

i did cp the file there after i made sure it wasnt there aswell but then it must be the 2 cmds i did afterwards that had no effect? the chmod/restorecon, didnt see or get an OK or done, just 4 new warning lines

in APNs i have 3 ( data.tre.dk ) which is highlighted and 2 below ones called 3MMS and Oister MMS ( oister is a lowbudget subcompany and i use 3 ) in 3MMS under MMS proxy it say 192.016.001.025

but the enabled one called 3 ( data.tre.dk ) also have MMS proxy which is "Not set", Proxy isn't set either nor port, Username, Password, Server MMSC and MMS port but should focus be here? or the apn called 3MMS

one is not set and other is that funky IP adresse.

im thinkin the phone uses the top apn to send mms and thats not set and the ROM is forced to use 3MMS which use that IP ? or im way off?
[OnePlus 3 & 3T Cross Device Development] :
??? You should overwrite the existing /system/etc/apns-conf.xml. If this file doesn't exists, your setup is broken! If you use "cp -iv /patch/to/my/apns-conf.xml /system/etc/apns-conf.xml" you should be ask to confirm the overwriting.

Then you have failed to replace the shipped /system/etc/apns-conf.xml with my version.

Again: with my version of apns-conf.xml you wouldn't have mmsproxy=172.16.1.25

I can't understand, why replacing /system/etc/apns-conf.xml failed for you.

Anyway: as long as you can see the apn with mmsproxy=172.16.1.25 you don't use my apns-conf.xml.

You are. You havn't replaced /system/etc/apns-conf.xml.

From my verison:

grep 'mcc="238" mnc="06"' /mnt/export/data/Downloads/incoming/apns-conf.xml
<apn carrier="3" mcc="238" mnc="06" apn="data.tre.dk" mmsc="http://mms.3.dk/" mmsproxy="mmsproxy.3.dk" mmsport="8799" type="default,supl,mms" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="IMS" mcc="238" mnc="06" apn="ims" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="H3G DK MMS" mcc="238" mnc="06" apn="services" mmsc="http://mms.3.dk/" mmsproxy="mmsproxy.3.dk" mmsport="8799" type="mms" protocol="IPV4V6" roaming_protocol="IPV4V6" />

From the shipped version:

grep 'mcc="238" mnc="06"' out/target/product/oneplus3/system/etc/apns-conf.xml
<apn carrier="3" mcc="238" mnc="06" apn="data.tre.dk" user="" password="" authtype="3" type="default,supl" />
<apn carrier="3MMS" mcc="238" mnc="06" apn="data.tre.dk" proxy="" port="" mmsproxy="172.016.001.025" mmsport="8799" mmsc="http://mms" user="" password="" authtype="3" type="mms" />
<apn carrier="3 DK" mcc="238" mnc="06" apn="data.tre.dk" mmsc="http://mms.3.dk" mmsproxy="mmsproxy.3.dk" mmsport="8799" type="default,supl,mms" />
<apn carrier="Oister" mcc="238" mnc="06" apn="data.dk" proxy="" port="" user="" password="" mmsc="" type="default,supl" />
<apn carrier="Oister MMS" mcc="238" mnc="06" apn="data.dk" proxy="" port="" user="" password="" mmsc="http://mms.oister.dk" mmsproxy="mmsproxy.oister.dk" mmsport="8799" type="mms" />

As you can see from the above, if using the fixed apns-conf.xml you shouldn't see any "oister" nor "3MMS" apns any more.

Flash attached apns-conf-xml.zip in twrp and check the apn settings again. I you still see "oister" reset Wifi, mobile and bluetooth data in Settings->System->Reset options from within running los and reboot.
[OnePlus 3 & 3T Cross Device Development] realtos:
hallo i just restored everything to stock and reinstalled everything and it worksssss!! :D now i only see 3 apns. thanks alot man for helpin me with this. hope this can help others aswell.
[OnePlus 3 & 3T Cross Device Development] :
Hopefully this gets merged soon:

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/240162
[OnePlus 3 & 3T Cross Device Development] Sebaxakerhtc:
It's work normally.

Just have a little to perfect.

What i find:

Change volume on main screen make change of media volume, not ringtone.

And battery percentage not shown.

But thank's for the ROM!

You are the best!
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Sadly, google has this change "forced" on all users of Pie and it's the default behavior in Android 9. You can not change ringtone volume by default when pressing volume button on home screen. Unless a developer adds a way to change the behaviour, we are stuck with this change. Just 1 more "change for the sake of change" from google when they run out of ideas for new Android version changes.
[OnePlus 3 & 3T Cross Device Development] vivian&ondine:
Very welcomed change from google.
[OnePlus 3 & 3T Cross Device Development] syd4asif:
Not able to receive messages

I am not able to receive messages. In both builds LOS 16-20190112 and LOS-1620190124 please help asap
[OnePlus 3 & 3T Cross Device Development] realtos:
works fine here, so it never worked or just those 2 builds?
[OnePlus 3 & 3T Cross Device Development] syd4asif:
Only With this ROM.
[OnePlus 3 & 3T Cross Device Development] morteza-25:
So far so good, everything works perfect for me on 20190124. Great experience since last time I installed a custom rom was on moto defy :fingers-crossed:.

I am not sure if the things that I am going to mention is Android 9.0's features, LOS' features or bugs, but there are few minor things here and there which I noticed. Apart from battery percentage which everyone mentioned here, I had a weird scrolling experience. I cannot reproduce it every time but mainly when I am in the Settings->Apps->All apps and I go to an app detail and press back and start scrolling (up) I can see a shadow of previous screen for a few millisecond or it doesn't scroll at all. Has anyone else experienced it? I think I captured it in the screen recorder as well, but you know while it's recording everything is a bit slow and laggy...

Other than that I thin adaptive brightness is a bit slow and harsh it's either 0 or the brightness you set for the max.
[OnePlus 3 & 3T Cross Device Development] bjo81:
My OP3 vibrates randomly, the first time while finishing the LOS logo on boot. It also vibrates randomly while all other apps use the notification sound. Any clue what this can be?
[OnePlus 3 & 3T Cross Device Development] realtos:
a bug most likely
[OnePlus 3 & 3T Cross Device Development] realtos:
but my op3 automaticly use vibrate as default when booting up even my rocker is down. so need to turn it a notch up and down to get it normal, but that feature is WIP so its gonna get worked out when devs have time. maybe it can relate to your issue, so we just have to enjoy the rom and wait for updates, devs are working hard on this rom :) without them we are lost hehe
[OnePlus 3 & 3T Cross Device Development] abhibnl:
[MENTION=4898097]arter97[/MENTION] [MENTION=4800121]Sultanxda[/MENTION]

Guys, I know you don't develop for this device anymore but you are two extremely talented devs I know and just wanted to disturb you to see if you have any inputs to help nvertigo with this 5Ghz issue. I hope this tagging hasn't bothered you.
[OnePlus 3 & 3T Cross Device Development] galaxykeks:
Really?

For me it's the only thing which bugs me on Pie.

I mean, right now, for the sake of not annoying everyone, i just put it on vibrate. This makes me miss calls. I can't turn the volume low without annoying everyone.

Also when i turn to vibrate my music often won't play on my headphones. I need to go back to ring mode to hear my music.

It's completely ****ed up. I mean they can have it as default, no issues, but i wish that long press on the profile chooser (ring, vibrate, mute) would bring up the extended sliders.

It wouldn't disturb any UI or user flow or whatsoever.

In working life, the ringer volume is far more important than media volume.

I agree that this changes once u are out of office, then i don't care so much.

-----

Apart from this, the build is also running smoothly for me.

The only thing i noticed, that after flashing/ updating it, the system settings are lost. (ringer, clock setup and so on)

Also, but already present before, if u have the clock in the middle and enable the traffic-meter it will be displayed below the clock (clock overwrites it). It would be nice to have an option to see it besides the signal bar
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Same here. I don't like the current setting. I prefer the previous behaviour.
[OnePlus 3 & 3T Cross Device Development] :
Code cleanup, here: properties

[MENTION=5091734]dianlujitao[/MENTION]:

The configuration of op3/t's properties is somehow inconsistent: some build props are set via PRODUCT_PROPERTY_OVERRIDES in device.mk, some via system.prop file. This make it harder to avoid errors like this:

ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep -r persist.vendor.radio.rat_on
device.mk: persist.vendor.radio.rat_on=combine \
system.prop:persist.vendor.radio.rat_on=combine
ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $

I would suggest to put all op3/t properties in one place. I see three optinos to do so:

put all props to system.prop

put all props to device.mk

put all props to (new) system_prop.mk (like https://github.com/LineageOS/android_device_oneplus_sdm845-common )

I can do the cleanup, after you've made a deccission which way to go.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Just remove duplicated ones in device.mk, I meant to keep system.prop in sync with CAF.
[OnePlus 3 & 3T Cross Device Development] Fangh:
Hello. I have the 12/01 update and I can see there is a new 24/01 version

1) How can I easily upgrade ? Can I flash the new zip without wipe anything ?

2) How can I be easily notified when there is an update ? My system did not warn me and I it says that there is no new version.

Thank you !
[OnePlus 3 & 3T Cross Device Development] simthadim:
1) Yes, you can flash the new build without a wipe. Some refer to this as 'Dirty flash'. As always, be sure to back up because your milage may vary: no guarantees.

Though I have never experienced errors. Sometimes people do notice a difference between a 'clean flash' and a 'dirty flash' because of some leftover binaries and apps. Nothing to be scared of, though.

2) Can't check as I am on NLOS (due to my MicroG requirements).
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
[MENTION=5091734]dianlujitao[/MENTION] I need to replicate a bug to you. I have a pair of BT headphones: Sony WH-CH500. When I am making a call with the headphones, I can hear the other person with cracklings. This bug is present in LineageOS 15.1 and up to 16. On OxygenOS and AOSP based ROMs, I don't have this problem. I find it a big problem for me because I can't hear the other part so well. Do you need me to provide logs for you when I'm making a call with BT headphones connected to solve the problem? I would appreciate if after that you will find and solve it. And I guess I am not the only one here with this problem.

Thank you sincerely.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
1) If you look in /system/addon.d you will see the list of things that will survive a dirty flash. In my case it's Magisk and Gapps. As a rule you normally never need to wipe data or system unless you're changing ROMs (eg, OOS to Los) or a major version change (eg, Oreo to Pie).

2) There's no update notification yet (this is not a stable, official version yet). You can check here for updates: https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC

There's a bug in 0124 so the battery level doesn't display the percentage value, which is why I'm sticking with 0115 for the time being.

Sent from my OnePlus 3T
[OnePlus 3 & 3T Cross Device Development] Dirk:
Magisk.
[OnePlus 3 & 3T Cross Device Development] dingsaller:
[MENTION=4793933]uttam.ace[/MENTION]

OP: "Installation:

First time flashing LineageOS 16.0 on your device, or coming from another ROM?

Download the zip(s)

Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)

Perform a nandroid backup of your current ROM (Optional)

Wipe data/factory reset

Flash LineageOS

Optional: Install the Google Apps addon package

Reboot"
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've only found one issue so far: the gallery app is missing (see screenshot of apps on a totally clean install with no gapps).

Otherwise everything is working just fine. I'm using Open Gapps Pico and Magisk 17.1.

GPS lock is quite fast (20 s to lock after resetting the A-GPS data inside the house)

I won't know about battery life for another 24 hours.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Another issue is the settings app FC's when you try to change the dark style to black in display settings.

Lots of random reboots and freezes too.

GPS doesn't work either, but I don't think that's the ROM's fault as GPS isn't working for me on other ROM's as well for some reason :/
[OnePlus 3 & 3T Cross Device Development] mk_1996:
i wasn't discussing stuff. i was just helping out. My device is already decrypted because unlike others i actually care to read the OP first before jumping in to ask for installation procedures. All i was saying was encryption wasn't even a bug on pie at all. its just the mechanism was different
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I don't get FC''s when changing the style to dark. And I've not yet experienced reboots or freezes.

Did you do a clean install and are you using the 5.0.6 firmware?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
So I've been running this for nearly a day. Battery life has been good. Given my setup I expect to use 10% per hour of SOT and that's exactly what I got on this rom.

I've had no FC's, reboots, or lagging.

My setup:

- stock rom and kernel; stock settings

- mobile data turned off (rarely need it when I'm not at home and it doesn't affect voice and SMS)

- mostly on WiFi and indoors

- WiFi and BT scanning turned off

- screen on auto-brightness

- no apps such as Greenify or Naptime
[OnePlus 3 & 3T Cross Device Development] knpk13:
I did do a clean install and I'm on the 5.0.6 firmware; still have those issues every time. Only mods I installed later were Magisk 17.3 and a substratum theme, but these issues were present on a clean install with no gapps, Magisk, or themes. This was on the Nov 13 build though. I see there's an update now, so might try that soon. Edit: OP mentions that there can be random kernel panics on the current build.

I can't get my GPS to work no matter what ROM I use so I guess it's a hardware problem. Surprising considering there's no physical damage, sigh. I switched back to Oreo (NLOS) for now.

Edit: I'm on ext4, unencrypted.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Have you tried tugapower?
[OnePlus 3 & 3T Cross Device Development] legendavey:
Man, don't discuss other ROMs on a development thread. Incredibly disrespectful. You have private messages and a Oreo/Pie discussion thread for that.
[OnePlus 3 & 3T Cross Device Development] muubase:
Hi. Anyone facing FC for apps like Spotify and LinkedIn?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
These're known bugs, FCs are due to many features are still WIP, not a big deal.

Random reboots and freezes is really a serious problem, so it's really not suitable for dd tbh and the main reason I call it an "alpha build". It's probably a bug in Qualcomm's kernel baseline, since Xiaomi msm8996 devices suffer from the same issue, and we're using the same baseline for kernel. It seems that msm8996 is not actively developed in qcom, since there're only 3 public Pie baseline for msm8996, and all of them are unstable, while msm8998/sdm660 have 7 and most of them are stable.

It's hard to address the random kernel panic, because it's hard to reproduce, and our kernel debugging methods are limited since I don't have access to UART console and the panics are not even logged in pstore ¯\_(ツ)_/¯. I'd keep waiting for new kernel baselines from qcom and try if they fixed the issue, on the other hand, if they don't fix it for a extremely long time, I may consider using O kernel as base for P.
[OnePlus 3 & 3T Cross Device Development] uttam.ace:
Yesterday installed, fluid smooth feeling. sometimes got fc, like changing theme, or finger unlock. sometimes home button not working. After reboot everything starts working again, considering it is in alpha stage it works pretty good and enough stable for my daily driver. I am rooted with latest stable magisk (17.1).

Again thanks .....cheers....
[OnePlus 3 & 3T Cross Device Development] pdsuthar:
I am having a strange problem. When I wake up my device it shows black screen but system is working fine as reboot it blindly. I have to reboot it to fix this. Any help?
[OnePlus 3 & 3T Cross Device Development] helderfp:
No problems so far, clean install and format data. Everything working great. Idle drain not so great.
[OnePlus 3 & 3T Cross Device Development] helderfp:
Snap camera vs gcam in low ligth
[OnePlus 3 & 3T Cross Device Development] uttam.ace:
Which gcam version r u using?
[OnePlus 3 & 3T Cross Device Development] realtos:
read other posts, its alpha build.