yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5616867]150208[/MENTION]: my room is in the basement. Moving my op3t from the rear of the room (2/3g sometimes only edge; differs with weather conditions - really!) to the window (lte or lte+, the latter only if the weather plays in... ;) ) let it always jump back from 2/3g or edge to lte or lte+.

EDIT: Prefered network type is configured to LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA, though I don't think it's the problem. After https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/244335/8/system.prop I've changed manually to 22 (aka: LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA).
[OnePlus 3 & 3T Cross Device Development] :
All right, thanks for the heads up

I'll do clean next time i travel then :good:
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Installed Rom in the morning... smooth one i would say.. Network switching between lte to all the way edge & then switching back to lte automatically was the issue.. No indication of signal bars in the status most of the times. Airtel volte doesn't work.. modified build.prop still volte doesn't work.. Help pls !??

Thanks :highfive:
[OnePlus 3 & 3T Cross Device Development] :
The build prop edits just enable the switch in the phone menu - it does not enable volte.

Does volte work for your mcc/mnc on oos? If so, have you tried the apn settings from oos fpr your mcc/mnc?

EDIT:

on signal strength indicators in the status bar and on how to compare real signal strength:

https://xdaforums.com/showpost.php?p=80289043&postcount=1079
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Airtel volte works on oxygen os starting from 5.0.8 to 9.0.5.. Bricked the phone in the morning & then flashed oxygenos from 3.1.2 to 9.0.5 :D

Will try to edit apn settings as suggested. Didn't know abt this trick.

Thanks...
[OnePlus 3 & 3T Cross Device Development] shivangswain:
1) I can't seem to change the Bootsplash logo by flashing regular Bootsplash zips. Any idea what to do?

2) What kernel does this ROM use? A modification of the official LineageOS kernel or FrancoKernel (because I see you in the FrancoKernel thread often). Asking just out of curiosity, already using your ROM and loving it (except for the Bootsplash & Bootanimation, sorry).
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Mcc/mnc for my state 404/40. If i change mnc to different state & save apn then it's picking default mnc 40. It doesn't work with suggested method :crying:
[OnePlus 3 & 3T Cross Device Development] :
The bootlogo zips provided in this thread are still working.

For other packages ask the dev of those packages.

Anything in the recovery log from flashing bootlogo?

https://github.com/nvertigo/android_kernel_oneplus_msm8996

It's based on los sources, but has additions from [MENTION=4800121]Sultanxda[/MENTION], [MENTION=3292224]franciscofranco[/MENTION], [MENTION=7030109]mcdachpappe[/MENTION], [MENTION=947981]Lord Boeffla[/MENTION] and all I've forgotten. Best you check the commits: all nlos specific changes are always rebased on top of los, for ease of checking.
[OnePlus 3 & 3T Cross Device Development] shivangswain:
Thanks for the quick and concise reply. Big fan, would like to express my gratitude once again - Thanks!
[OnePlus 3 & 3T Cross Device Development] :
You've got me wrong. You can't change mcc/mnc (this double is defined by the sim/carrier you are using), compare the apn settings for 404/40 of oos with ours. (/system/etc/apns-conf.xml). This is a boot time config, no new build is needed for testing, just edit the file and check permissions and selinux context after editing in twrp, reboot and reset network settings. To revert, just dirty flash the installed rom zip again.

Since I can't test this (I'm on 262/02), you may want to ask otjer nlos users or los users for their expirience with 404/40. Maybe something like this is needed: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/247676 But that's just guessing, since I can't test... ;) I can put this in for the next build. This is a buld time configuration - rebuild of tje rom is required to change. Don't forget to reset network settings, after flashing the next build.
[OnePlus 3 & 3T Cross Device Development] lautarex:
Hi, I've been using this ROM and it's been amazing. It's very fast, smooth and feels super stable. I would like to ask if there is any possibility to add face unlock, as in stock OOS?

Another feature that I would love to see is automatic screen unlocking when you write the right PIN.

I would like as well to thank the devs for maintaining this project and our beloved op3t as great as a new flagship and full of features.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
While we're at this... Could You also add 260/01? It's strange but it seems to be completely missing from the list while all other 260/xx networks are present. The parameters should be the same as for all other 260/xx networks (they're all the same, volte+ims enabled).
[OnePlus 3 & 3T Cross Device Development] :
Face unlock: oos face unlock is closed source - but you can use google's face unlock with opengapps nano (instead of pico), if smartlock is enabled. For the record: regarding security, fp is much superior to smartlock's face unlock!

Automatic screen unlocking: no, because of security. (You can easily gues the pin/paysword length with that "featute", which decreases the relative security level.)
[OnePlus 3 & 3T Cross Device Development] :
It doesn't make sense to add all carriers indiviually to the device tree, because if not defined otherwise (in fwb or CarrierConfig), the default is: https://github.com/nvertigo/android...base/core/res/res/values/config.xml#L176-L184

If it's disabled by config, I belive in the devs, who have tested that. As explained previously, I can test only for 262/02, which doesn't support volte on oos...
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Oh... So it's "true" by default!

Thanks!

Then I don't understand why it's implicitly set to true for the other carriers :)
[OnePlus 3 & 3T Cross Device Development] :
I hate fp, when i need it to be fast, either the fp or my hand has some bird poop on it :crying:
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
404/40 Airtel location: chennai

404/49 Airtel location: Hyderabad

Sorry for previous post.. My location setting: 404/49 Hyderabad

apns-config.xml does contains 404/49 of airtel.

This is a boot time config, no new build is needed for testing, just edit the file and check permissions and selinux context after editing in twrp - could you please explain things i need to check/do in a detail !?? Editing in twrp !!??

Thanks for your time & knowledge sharing. You are awesome man :highfive:
[OnePlus 3 & 3T Cross Device Development] :
You've cutted a very important part of my original posting: "regarding security".

As a matter of fact, faceunlock is the most insecure method.

Regarding comfortability your milage may vary.

You've got me wrong. You need to compare each and every setting, not only presence: in nlos' apns-conf.xml find all lines containing mcc="404" and mnc="49". In oos' apns-conf.xml find all blocks (it's the same syntax like the lines in nlos' apns-conf.xml, it just contains line breaks) containing mcc="404" and mnc="49". Then compare each and every setting inside the line/block. Watch out: carrier="some_string" is just some string, it doesn't need to have the very same string in los/nlos and oos! "Type" is a good field to find the corresponding lines/blocks.

Sidenote: though airtel may use different mnc for different location, the double mcc/mnc defines a carrier, not a location. Mixing up the concept of carrier and location can be very confusing (mcc: mobile country code; mnc: mobile network code).

In twrp you can use vim for editing apns-conf.xml. After mounting system, start the terminal:

/system/xbin/vim /system/etc/apns-conf.xml

For vim usage: http://vimdoc.sourceforge.net/htmldoc/usr_02.html

Alternately you can use /system/xbin/nano. Usage: https://www.nano-editor.org/dist/v2.1/nano.html#Editor-Basics

You can check permissions (-l) and selinux contexts (-Z) with ls in the twrp terminal:

ls -lZ /system/etc/apns-conf.xml
-rw-r--r-- 1 root root u:object_r:system_file:s0 580139 2009-01-01 00:00 /system/etc/apns-conf.xml

To restore the above (if neccessary!):

chmod 0644 /system/etc/apns-conf.xml
restorecon /system/etc/apns-conf.xml

Never forget to reset network settings, after changing /system/etc/apns-conf.xml!

In deed. That's why I'm extremely carefull to add/change something: If an additional setting is neccessary and proofed to work, I'll ad it, but I can't support you on finding which settings are needed. If you look i.e. at 204/04 (https://review.lineageos.org/c/Line...ges/apps/CarrierConfig/res/xml/vendor.xml#124 ) and i.e. 404/92 (https://review.lineageos.org/c/Line...es/apps/CarrierConfig/res/xml/vendor.xml#1858 ), you'll see that the configured settings are veryvery different. Since I can only test for 262/02, you are on your own here.
[OnePlus 3 & 3T Cross Device Development] :
That what's a good journalist do ;)

I carried a super secret propaganda to make you looks bad :highfive:
[OnePlus 3 & 3T Cross Device Development] :
CarrierConfig

I've decompiled OOS 9.0.5 CarrierConfig.apk (for this matter: CarrierConfig.odex) and pulled res/xml/vendor.xml.

I've found:

ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep -A4 -r -e "mcc=\"404\" mnc=\"40\"" -e "mcc=\"404\" mnc=\"49\"" /mnt/export/data/Downloads/incoming/Android/vendor.xml
<carrier_config mcc="404" mnc="40">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_volte_default_enabled_bool" value="true" />
<boolean name="carrier_vt_available_bool" value="false" />
</carrier_config>
--
<carrier_config mcc="404" mnc="49">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_volte_default_enabled_bool" value="true" />
<boolean name="carrier_vt_available_bool" value="false" />
</carrier_config>
ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $

According to these findings, the next build (hopefully, if time permits: tomorrow) will have:

https://github.com/nvertigo/android...mmit/94e3436cf0c1404a02c401eb09109cc3c4902c03

https://github.com/nvertigo/android...mmit/b36b476fc947ae70a83a7eb4163778745d0c5a11

[MENTION=6561751]pedritopl[/MENTION]:

You've asked for 260/01. It's not in OOS, either:

ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep -A3 -r "mcc=\"260\" mnc=\"01\"" /mnt/export/data/Downloads/incoming/Android/vendor.xml
ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep -A3 -r "mcc=\"260\" mnc=\".*\"" /mnt/export/data/Downloads/incoming/Android/vendor.xml
<carrier_config mcc="260" mnc="02">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
</carrier_config>
<carrier_config mcc="260" mnc="03">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
</carrier_config>
<carrier_config mcc="260" mnc="05">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
</carrier_config>
<carrier_config mcc="260" mnc="34">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
</carrier_config>

For testing, I'm going to include

https://github.com/nvertigo/android...mmit/0a522918aa71901b80f280dd5481bb8c87ff890e

Let me know, if this changes anything at all...
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Awesome man... I'm breaking my head with build.prop & apn-conf.xml files

Hopefully it fixes for 404/49. Thank you again. :highfive:
[OnePlus 3 & 3T Cross Device Development] :
Forget build.prop:

ingo@adler /usr/local/src/oxygenos $ grep -i -e ims -e volte system/build.prop default.prop system/build.prop:persist.volte_enalbed_by_hw=1
ingo@adler /usr/local/src/oxygenos $

Focus on apns-comf.xml (the above commits, are no substitute for a correctly configured apn).
[OnePlus 3 & 3T Cross Device Development] :
CarrierConfig

New build up in the usual location. Use https://xdaforums.com/showpost.php?p=80617193&postcount=1151 as changelog, announcement posting and OP update follow later today.

[MENTION=5304504]vijay.ev[/MENTION] and [MENTION=6561751]pedritopl[/MENTION]: test regarding volte and report back, please.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I see no change related to VoLTE for 260/01 :-/

You were probably right about the default settings. Seems that adding those explicit values for 260/01 doesn't make any difference.

Thanks anyway for trying!
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20191022

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.5 firmware

Oneplus 3: OxygenOS 9.0.5 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.5. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

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

Changelog (Last repo sync: 22 Okt 2019, 09:16:15 CEST / 22 Okt 2019, 07:16:15 UTC):

op3/t: overlay: CarrierConfig: add 260/01. — Nvertigo

op3/t: overlay: CarrierConfig: add 404/49 from OOS. — Nvertigo

op3/t: overlay: CarrierConfig: add 404/40 from OOS. — Nvertigo

Note: if you want to test the new CarrierConfig for 260/01, 404/40 or 404/49 after a dirty flash (aka update), reset network setting and reboot to system!

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] vijay.ev:
Volte doesn't work. Unlocked bootloader & installed clean nlos rom from usb otg by formatting everything from twrp once again on my friend Oneplus 3T.

Reset network setting. Rebooted couple of times. When i call - LTE switches from LTE to H+/E i.e VOLTE doesn't work.

:( :crying:

---------- Post added at 06:06 PM ---------- Previous post was at 05:50 PM ----------

Please check... build.prop doesn't contain code: persist.volte_enabled_by_hw=1

:confused:

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

Please check build.prop doesn't contain code: persist.volte_enabled_by_hw=1

:confused:
[OnePlus 3 & 3T Cross Device Development] :
Please help keeping this thread readable. Only quote, what you are relating to. After an unintented double posting, use the edit button.

Why do you think it's needed? I can't find anything using this prop:

ingo@adler /usr/local/src/los16 $ grep -r -i persist.volte_enabled_by_hw system/ hardware/ external/ frameworks/ packages/ vendor/oneplus/oneplus3/ ../oxygenos/firmware-update/ ../oxygenos/RADIO/ kernel/oneplus/msm8996/
ingo@adler /usr/local/src/los16 $

Have you tried setting the persist prop manually and reboot?

Note: I dislike setting persistent props just for testing. It gets automatically set, if i.e. in build.prop, but when removed from build.prop it persists (that's why it's called persist). I doubt that the vast majority of users is able to get rid of a persistant prop without clean flashing...

BTW: Is 404/49 set to the same values in apns-conf.xml of nlos/los and oos?
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Sorry for the double post. Manually added persist.volte_enabled_by_hw=1 and rebooted - No luck

404/49 set to different values in apns-conf.xml of nlos & oos.

Additional value in apns_conf.xml for 404/49 apn type in oos: protocol="IPV4V6" roaming_protocol="IPV4V6"
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
Is there any solution for Mobile network standby issue on Pie firmware?
[OnePlus 3 & 3T Cross Device Development] :
Copy oos version to /system/etc/apns-conf.xml, check/fix permissions and selinux contexts, reset network settings and reboot.

I've never expirienced that. I can't fix, what's not an issue on nlos.
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
Every custom ROM based on LineageOS has that sincer dianlujitao merged Pie blobs. Even LineageOS has that. And I am not the only one who has that. See detailed battery after some time you used the phone with mobile data.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I'm not sure if you've noticed before but thet Mobile Network Standby you see in battery details has been there since Lollipop (Android 5), IIRC. I had a OnePlus one then and this was the most discussed topic, how to fix mobile standby battery drain.

I use mobile data 80-90% during the weekdays and i can tell you that it barely affects my battery if phone is in standby. Ofcourse if you have sync running in background and too many apps sending you push notifications while phone is not in use, it will affect your battery and your phone will be temporarily out of deep sleep.

I am not sure how you use your phone or what apps you use, but I have really no drastic battery drain with mobile data ON and phone on standby mode.
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
Selinux contexts !?

Sorry i was complete noob on that. What needs to do/check or any terminal commands needs to perform !??

Once again. Thanks very much for your patience & knowledge to fix the issue on volte topic.

---------- Post added at 03:39 AM ---------- Previous post was at 03:26 AM ----------

@nvertigo67 please look into below thread where [MENTION=8829870]SuperDroidBond[/MENTION] confirmed airtel volte working on their rom. It might be very much helpful to replicate same in our Nlos.

https://xdaforums.com/oneplus-3/one...nal-aosp-5-0-android-8-0-pre-t3693585/page274

Thanks :highfive:
[OnePlus 3 & 3T Cross Device Development] :
I havn't expirienced the mobile data drain myself, but I've noticed quite some reports of moile data drain since 5. What I've never seen is a logcat for mobile data drain after a clean flash with only nano or pice opengapps and no other apps installed nor apps or data or settings restored.

We had some wifi related wake locks in 14, 15 and 16 from the kernel, which resulted in idle drain. I've addressed them by [MENTION=947981]Lord Boeffla[/MENTION]'s wake lock blocker, but after the last kernel rebase it's not needed anymore.

For now I'm still pretty sure it's a setup triggered issue (or maybe carrier specific - but I doubt that), but no rom issue.

I've explained all steps in detail two pages back, when you've asked the very same question: https://xdaforums.com/showpost.php?p=80611769&postcount=1149

I've read the complete page, but did not find any hint on how to fix.... No change, no gerrit commit not even a change log. I have no idea, why this link should help fixing this.

Considering the above, I would like to stop the airtel conversation with you at this point.
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
I will make a clean flash with no apps to see if that can be fixed.
[OnePlus 3 & 3T Cross Device Development] :
After running through the first time setup, enable dev opts, set the log buffer size to 4 Mio and reboot. :good::good::good:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Did you remove longshot in this build? I'm only able to take regular screenshots now.
[OnePlus 3 & 3T Cross Device Development] :
I've forgotten to run current.pick.sh... my bad, sorry. Thanx for heads up!

Doesn't matter that much, use 1013. It's nearly the same as 1022, but apns.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20191024

Note: 20191022 removed because of incomplete patching (curtent.pick.sh wasn't run). If you use 20191022 update as soon as possible to 20191024.

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.5 firmware

Oneplus 3: OxygenOS 9.0.5 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.5. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.5 blobs, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

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

Changelog (Last repo sync: 24 Okt 2019, 10:31:52 CEST / 24 Okt 2019, 08:31:52 UTC):

op3/t: overlay: CarrierConfig: add 260/01. — Nvertigo

op3/t: overlay: CarrierConfig: add 404/49 from OOS. — Nvertigo

op3/t: overlay: CarrierConfig: add 404/40 from OOS. — Nvertigo

Note: if you want to test the new CarrierConfig for 260/01, 404/40 or 404/49 after a dirty flash (aka update), reset network setting and reboot to system!

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] Tiggy_Drum:
First LineageOs 17 ROM for op3/3t available ! Can't wait to see yours !
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi,

I'm getting the dialer app crashes from time to time since some time already, but only today I was able to check and confirm that the crashes only appear if I have the "Record all calls" option on (which is how I want it). It seems to be crashing mostly (or only) if I try to call someone and then I hangup before the call is answered.

I last clean flashed around January and dirty flashed all builds since then, so I'll understand if this report is ignored.

I attach the logcat from a quick problem reproduction.

The line which seems to be the most interesting is:

java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String com.android.incallui.call.DialerCall.getNumber()' on a null object reference

My setup: OP3T A3010, build 20191024, opengapps-pico

I'd appreciate if anyone looks at this and lets me know if the problem is somewhere in my setup or is it a bug introduced by the record-all-calls option.
[OnePlus 3 & 3T Cross Device Development] :
Since the log is filtered, I can only guess: Is the crash happening, when you pick an incoming call, or if you make a call? I guess the first. Does the call comes with callerid suspressed? I havn't expirienced this myself, but I ignore all calls without caller-id.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi, I used "logcat -v long" - does that filter the output by default? :-o

The "test procedure" is:

- make sure "record all calls" is on

- start a call

- hangup before the other part answers

App crash.

Reproduction rate with this scenario is about 60-70%.