yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Me too, I'm sorry I meant "ratify", messed with other conversations :s I wanted to say that it is another member that verifies encryption is working, as you already did.

Edited
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
flash last update and didn´t detect the sim card...

any one with this problem?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Same here, no sim detected.

Dirty flashed using pico gapps
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
I tried to change the drawer of the sim and nothing changes..
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
did anyone get flash without error on sim card?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Do a clean install
[OnePlus 3 & 3T Cross Device Development] ab123321:
Haven't got a sim working too. There are endless attempts to start radio service in android:

I ServiceManagement: getService: Trying again for android.hardware.radio@1.1::IRadio/slot1...
W ServiceManagement: Waited one second for android.hardware.radio@1.1::IRadio/slot1

P.S. ofc I did a clean install
[OnePlus 3 & 3T Cross Device Development] rexit1979:
Same here.No sim detected after flashing clean.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I can confirm, no Sim detected after clean flashing the latest build.

As a sidenote, has anyone gotten restoring apps with Titanium Backup to work on this ROM? It doesn't work for me, but other functions like freezing and backing up work. I've sent a report and a log to the Titanium Dev team but I haven't gotten a response in weeks so I thought I'd ask if anyone else has had that issue.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
TB works just fine provided the app you're restoring isn't split. If it is, then you have to install it from Play Store and then you can restore the data. I've attached a list of the split apps on my phone, just as an example. And here's a screenshot of what a split app like like.

Edit: you could also try using Migrate v3.0 alpha 2 to install your apps (it worked for me): https://xdaforums.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763/post78060823
[OnePlus 3 & 3T Cross Device Development] rexit1979:
Migrate works for me perfectly. But what about sim detection?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've not had a problem with the Sim.
[OnePlus 3 & 3T Cross Device Development] rexit1979:
Quite strange. Faced similar situation with AEX 7.0 latest by Ajithrez and the rom is removed now from download site.All other roms I tried are working good.

​
[OnePlus 3 & 3T Cross Device Development] Dirk:
That got a good belly laugh from me. Well done! :laugh:

I guess 'Should' leaves a tiny bit of wriggle room. Not, 'we insist that...', but rather, 'we would pefer it if...'.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9708417]Eric_Lev[/MENTION] & [MENTION=1763460]Dirk[/MENTION]:

Since this is the op3/t thread I havn't talked about what SHOULD be or what other devices offer, but about what IS. op3/t doesn't use forced encryption. A new user reading this thread and follow the link in question thinks op3/t use encrypted data by default - taking statememts like this with a gain of salt is just usefull. Every avoided misunderstanding saves our all time.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Just a bit more testing following on from https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post82871515

This time I did the following:

1. Clean install of Los 17.1 200608 (rom only, no Gapps, no Magisk). Result: GPS Status doesn't get a fix and no locks on satellites. Other than getting no fix, this looks just like my previous post.

2. Clean install of Nlos 16.0 200607 (only rom). Result: good lock on satellites. So Los 16 clearly does something that Los 17.1 doesn't.

3. Restore Los 17.1 backup. Result: good lock on satellites.

Conclusion: Los 16 is doing something that is good for GPS, which Los 17.1 doesn't do, and it survives clean flashing and restores so I'm guessing it's writing something in /persist or EFS. And Los 17.1 over time loses whatever it is that makes GPS work.
[OnePlus 3 & 3T Cross Device Development] Rootax:
Hello there.

Just switched from oos 906 to latest los 17.1 nightly+magisk 20.4, and everything I use is working great.

Thx a lot to everyone working on it :)
[OnePlus 3 & 3T Cross Device Development] :
gps and location service

Just a thought on location services:

If you want to debug/test gps it's necessary to exclude other location services. This is done by setting the location service to "device only" disabling bt and wifi scan as well as all google location services. At this point only the qcom location stack (from miui_DAISYGlobal_V11.0.2.0.QDLMIXM_d59f395371_10.0) is used.

If gapps (and therefore the location services from gms) arn't installed they doesn't need to be disabled (in deed the settings are missing), of course.

The qcom gps stack itself uses additional information (like nlp) which is handled inside the gps stack and reported as gps position outside the stack to apps. If you look at https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-17.1/gps/etc/izat.conf#L52 you'll see the qcom gps stack uses the network location provider from gms. If no gms (gapps or microg) is installed izat can't work as intended.

Especially the systematically tests from [MENTION=2911853]BillGoss[/MENTION] (no gps if no gapps are installed) suggest that gps refuses to lock if izat can't find a nlp. This shouldn't ( ;) ) be the case (and surely wasn't in 16.0), "pure" gps should ( ;) ) work as well, but the mentioned test is quite clear.

For further testing I'd suggest to increase the log level for gps and izat:

https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-17.1/gps/etc/gps.conf#L27

https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-17.1/gps/etc/izat.conf#L5

Another note:

Don't use maps (or similar user apps) for trying to tell if gps is working (maps uses location not only gps). Always use apps showing the actual sat locks. Keep in mind that some apps (like https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 ) uses an own agps data implementation, which may effect the result. The simpler, the better. (You can identify such apps by trying to inject agps data: if that works, the app has an own agps implementation, since the qcom gps stack doesn't allow external apgs data injection (because services like izat handle agps data stack internally). I like https://play.google.com/store/apps/details?id=com.android.gpstest but there are surely other "simple" apps, too.
[OnePlus 3 & 3T Cross Device Development] minoccio:
He says : "Oxygen OS required"
[OnePlus 3 & 3T Cross Device Development] :
Galileo

Does anybpdy know of a msn8996(pro) soc equipped device with a stock rom supporting galileo?

Since both (msm8996 amd msm8996pro) socs support galileo on hardware level, there's the chance of enabling galileo for op3/t with kanged blobs from such a rom.
[OnePlus 3 & 3T Cross Device Development] sanchaz:
Works with Custom Rom as well.

https://xdaforums.com/showpost.php?p=82059625&postcount=1190

---------- Post added at 12:35 PM ---------- Previous post was at 12:33 PM ----------

Indeed, I think that's it thanks.
[OnePlus 3 & 3T Cross Device Development] :
This one?:

https://www.deviceranks.com/en/phone/6235/zuk-z2 (and the z2pro)

This is what the spec's are saying:

Navigation . . . . . . . . . . . . . . . . . . . . . . . . . .GPS, A-GPS, GLONASS, BeiDou, Galileo

Edit 1:

Additional, here you can find a list of all smartphones which are currently able to use Galileo, which are about 30 phones.

Though, I have no idea which one is using 'our' chipset and it seems the Zuk Z2 (Pro) is not one of them...

https://www.usegalileo.eu/EN/inner.html#data=smartphone

Edit 2:

I have compared some lists:

https://www.usegalileo.eu/EN/inner.html#data=smartphone

https://galileognss.eu/is-your-phone-using-galileo/

and

https://www.gizmotimes.com/lists/list-of-phones-powered-by-qualcomm-snapdragon-821/16889

https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-821-msm8996-pro

https://www.akshatblog.com/snapdragon-821/

etc....

Unfortunately this is not giving a match.

So I think we are stuck on the old GPS, GLONASS and BeiDou networks, it seems Galileo is not there for us....

.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I'm not sure if 3. is true - it also could be that it coincidentally worked..

I'm thinking of this, because for me it sometimes works..

So you should observe if aber 3) the gps and lock on satellites are ALWAYS as good as in LOS 16.

And I was on LOS 16. I installed clean LOS 17 on a second OP3 (and configured it on this second device). I created a nandroid backup of this. Then I cleared data and system on my main device, installed los 17.1 and moved the Nandroid backup to my main device and restored it there (sounds complicated, I know)

The result of this is that I have gps issues - also after a kind of your point 3) "restoring a nandroid 17.1 backup over los 16..)

--

One thing about the sorting issue in the gallery app:

since the mediaprovider fix in 0615, the camera photos, and also instagram, panorama photos, download photos etc are sorted right again. That's a huge improvement!

But screenshots that were new taken aren't sorted right - they don't appear in the timeline, and in its folder, they are below the oldest screens (for me, before 2016)..

So it seems it isn't fixed 100%

Anybody else did see this?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I agree that I don't have enough data points to prove definitively what I said, but my results indicate that this is likely. In summary the tests were:

1. Los 17 - no satellite locks (backup taken)

2. Clean install 16 - good satellite locks

3. Clean install 17 - good satellite locks

4. Restore 17 (from 1.) - good satellite locks

5. ... Time (days) passes (no system changes)

6. Los 17 - no satellite locks (backup taken)

7. Restore 17 (from 6) - no satellite locks

8. Clean install 17 - no satellite locks

9. Clean install 16 - good satellite locks

10. Restore 17 (from 6) - good satellite locks

Clearly from 4-5-6 having good GPS in 17 doesn't mean it stays that way.

And, always, 17 GPS will work if installed/restored after 16.
[OnePlus 3 & 3T Cross Device Development] rohan164:
does this work with any carries other than german? like for in india? (Jio/Airtel)
[OnePlus 3 & 3T Cross Device Development] :
Does your mcc/mnc (mandatory carroer info!) work on stock oos? If so you don't need to edit efs, anyway.

If your mcc/mnc works on oos but not on los you need to compare the carrier config. Forst step is comparing apns-conf.xml. If the apn config for your mcc/mnc is the samd, you need to decompile (baksmali) carrierconfig and phone apks and compare the setiings for your mcc/mnc in the resources.

If your mcc/mnc isn't working in oos the efs edit may work.
[OnePlus 3 & 3T Cross Device Development] gaizkaxda:
Seems a-gps problem. Don't know if a-gps info can persist from Los 16 to Los 17 upgrade inside GPS chip?
[OnePlus 3 & 3T Cross Device Development] sanchaz:
So I hit into a problem attempting this yesterday.

When using PDC got "QMI connection not ready, please use USB drvier version 1.00.32" (...)

There seems to be this https://xdaforums.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073

But I haven't attempted it yet, so can't say it will work, and won't brick your phone.

Another alternative might be to temporarily revert back to Oxygen OS or some rom based on OOS, run the changes and then restore your LineageOS and just edit the props to force VoLTE. (Haven't attempted it either)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
More on the GPS issue... [MENTION=3345663]gaizkaxda[/MENTION]'s comment made me wonder about AGPS so I did some more testing.

As I've mentioned before, restoring a Los 17 rom over a clean [N]Los 16 rom results in a working GPS setup.

However, doing an AGPS reset kills GPS on Los 17 - I end up with very few satellites and no locks.

I tested this using GPS Status (https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2) and GPS Test (https://play.google.com/store/apps/details?id=com.chartcross.gpstest) and I took a logcat during the AGPS reset. I've attached the logs below. I noticed there are a number of errors related to sensors and location.

I also wondered if my ad blocker (DNS66) might have anything to do with this so I disabled it, but this made no difference.

Then I switched back to [N]Los 16 and tested resetting the AGPS, but this has no impact - the phone very quickly found all the satellites (31) and locked on to half of them (16).

But then I disabled mobile data on the phone so there was no external data access and this time resetting the AGPS produced the same result on Los 16 as I was getting on Los 17: a very long time to find any satellites and no locking onto any of them!

Conclusions:

1. poor GPS performance is caused by missing AGPS data.

2. Los 17 has a problem in that it can't renew the AGPS data once it's been cleared, even though it has external data access. On Los 16, the AGPS data is quickly renewed if there's an external data connection.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Changes in 20200622 were just about default app; calendar, clock & recorder.
[OnePlus 3 & 3T Cross Device Development] :
Great finding! Great logs (xtra data download is completely missing)!

I think I found the reason: from 15.1 to 16.0 the location for configuring xtra data (and some more gps related settings) have moved from gps.conf to frameworks/base (via overlay): https://github.com/LineageOS/androi...base/core/res/res/values/config.xml#L393-L395

But now in 17.1 there are no xtra data configurations neither in https://github.com/LineageOS/androi...rameworks/base/core/res/res/values/config.xml nor in gps.conf.

The quickest way to check if this is really the cause is adding these three lines https://github.com/LineageOS/androi...us3/blob/lineage-16.0/gps/etc/gps.conf#L9-L11 to gps.conf.

It would be great, if you would like to check this.
[OnePlus 3 & 3T Cross Device Development] najmalfirosh:
Been using for past few days, everything works fine except that the wifi keeps disconnecting and reconnecting back immediately quite often, does anyone have a fix for this. This is happening on other custom roms as well, i've tried a few. I'm on 9.0.6 kernal, could this be a kernal issue?
[OnePlus 3 & 3T Cross Device Development] generalprobe:
I found two devices that could help us.

The first less promising device is the LG G6, where users were unable to use Galileo, but the second one seems quite promising. It is the Samsung Galaxy Tab S3.

https://www.gsmarena.com/samsung_galaxy_tab_s3_9_7-8554.php

Also I found some forum entries where a samsung community moderator confirmed Galileo functionality on the Galaxy Tab S3.
[OnePlus 3 & 3T Cross Device Development] najmalfirosh:
I'm also facing a similar issue, not just on 5ghz,even on 2.4. I've tried flashing different Roms, but the problem still persists. Let me know if you have found a fix for this issue.

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
So I added the XTRA_SERVER lines to /vendor/etc/gps.conf, but that made no difference. I also tried using the Nlos gps.conf file, also to no avail. So the solution isn't as simple as that, which is a shame.
[OnePlus 3 & 3T Cross Device Development] :
Worth a try. :(

For 17 the bt stack blobs from daisy are used:

https://github.com/LineageOS/androi.../lineage-17.1/proprietary-files.txt#L533-L570

I don't know if reverting some (last seven) commits here: https://github.com/LineageOS/android_device_oneplus_oneplus3/commits/lineage-17.1/gps allows to use the pie oos 9.0.6 blobs (which allow setting of XTRA servers) - maybe one of the homebuilders can check, or if something else in the q stack is failing/missing when using blobs for a msm8953. Maybe [MENTION=5091734]dianlujitao[/MENTION] can fix it with an increased log level for gps and izat. Thanx to [MENTION=2911853]BillGoss[/MENTION]' testing the issue is easy to reproduce.

EDIT:

one of the homebuilders can also try to use this los-16.0 commit:

https://github.com/LineageOS/androi...mmit/468741a1b05ac904e9c6434916bd0eb7a3fdc920
[OnePlus 3 & 3T Cross Device Development] :
Some things I see/ noticed:

No https is used for the XTRA_SERVER;

I see xtra3grc.bin is used in the LOS16 commit, though in the last test xtra3grcej.bin is used; does this make any difference?

XTRA_TEST_ENABLED=1 and XTRA_THROTTLE_ENABLED=0 are missing in the default gps.conf, are they needed for the XTRA_SERVER data?

Edit:

I have changed my gps.conf and added some stuff as XTRA_SERVER's (https) and some extra lines from pie/10 based gps.conf I found in other roms.

Seems to work for me at the moment, but am wondering if it really solves the issue.

Have enclosed it as attachment, would you like to test, feel free.... ;)

Ofcourse you have to rename from gps.conf.txt to gps.conf and move it to /system/vendor/etc.
[OnePlus 3 & 3T Cross Device Development] :
I don't remember the reason, but in 13 or 14 I've suggested https - it wasn't accepted.

Good question, I havn't even realised that "j".

Maybe, but without increased gps/izat logging I'm not sure - surely worth a try.
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
Where can we find the apns-conf.xml ? I couldn't find it in /etc or in any other location on my phone.

I checked the file in github, it has an entry for my MCC/MNC (404/49) which is same as what worked in OOS.

<apn carrier="Airtel GPRS" mcc="404" mnc="49" apn="airtelgprs.com" type="default,supl" />
[OnePlus 3 & 3T Cross Device Development] :
It should be in $sys_root/system/etc or in $sys_root/system/vendor/etc. In doubt mount system in twrp and on the terminal "find / -name apns-conf.xml".

There must be more 404/49. If I grep through oos:

ingo@adler /usr/local/src/oxygenos $ grep -A1 'mcc="404"' system/etc/apns-conf.xml|grep 'mnc="49"'|wc -l
3
ingo@adler /usr/local/src/oxygenos $

On a quick view I'd guess the difference is the ims apn present in oos but missing in los and the other apns differ, too. So your statement it's the same in oos (worked) and los (not working) is not true.

EDIT:

Try attached apns-conf.xml (replace, check permissions and selinux contexts; wipe network settings and reboot). If this fixes volte for you, this commit is needed: https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/242686 (cherry pick to lineage-17.1 branch).
[OnePlus 3 & 3T Cross Device Development] :
Just had to take my car for shopping; good opportunity to test. Lock within seconds, also after switching off, driving some km's and switching gps and nav on again...

WIll try some more, but results are better I have the idea..
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Some differences about los16 and los17 gps.conf (in /system/vendor/etc)

1) LOS 16

XTRA_CA_PATH=/system/etc/security/cacerts

LOS 17

XTRA_CA_PATH=/usr/lib/ssl-1.1/certs

--> /usr doesn't exist on the device. The path from LOS16 does also exist in LOS17, I'll change this setting to the LOS16 setting and watch if gps gets better. In fact I have no clue if this setting can impact gps setting in any way, or is just for the downloading thing of xtra.bin file..

2) LOS 16

CAPABILITIES=0x37 # GPS Capabilities bit mask

LOS 17

CAPABILITIES=0x17

I googled a bit, https://review.lineageos.org/c/LineageOS/android_device_samsung_jf-common/+/232702

Changing the Capabilities bit coukd improve the lock time - I'll also set this option to its los16 value and watch gps ..

3) There are a few new settings in los17 config file that arent in the los16 version, but most of them are set to 0, so I think to the default value..

for example

4) and of course the missing XTRA_SERVER_1 to 3, as [MENTION=2911853]BillGoss[/MENTION] already found out

How to update a-gps (According to this site https://www.itechify.com/2016/08/04/how-to-fix-gps-oneplus-3-guide/)

You can download this app, there are the options Clear AGPS and Update AGPS within the app..

https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en

Edit: I attached both gps.conf files from los17 as well as from los16. So feel free to compare it yourself, maybe you can find other differences and/or strange settings :)
[OnePlus 3 & 3T Cross Device Development] :
As explained previously: injecting agps data from userspace is not possible by design with the qcom gps stack. If an app allows injecting agps data it has implemented an own additional layer in the stack. This is not good or bad, but you don't debug what you want to debug with such apps: you want to debug the qcom gps stack, but what you really see is the result from app specific additional layer... This is (for me) more confusing then helpfull.

I would also disable intermodiate position, because until the "real" sat fix happens this is just a faked lock, which makes it even harder to comüare times.

To avoid misunderstandings: with the altered gps.conf you get a (real) sat lock in a few secomds after deleting agps data and not manually injecting it, arn't you?

EDIT:

For the article you've linked:

Setting gps to high accuracy enables the location stack to use gservives for location. With this setting it's even harder to tell if and how good gps (and glonass and beidou) is (are) working.

The agps data is renewed internally by the qcom bt stack itself, it CAN'T!!! ne updated externally from an userspace app. The app mentiomed in the posting should report "AGPS rrquest failed" as long as the qcom location stack is used. It does that on oos 9.0.6 and los 16, I'm surprised if it's not reporting "AGPS request failed" on your device.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I was just comparing the files, but haven't tested it yet.

But I'll test these settings and will report my results here, but it needs some testing of course.

The fact that some times the gps works fine on our los17.1 bit no modified settings makes it really very very hard to say if changing this and that will have an impact... :mad:
[OnePlus 3 & 3T Cross Device Development] :
you can test my GPS.conf as all points you mentioned are in it...;)

Edit:

Did not solve the issue.

Just disabled internet, cleared agps data with the app GPS status, closed the app, enabled data, after that enabled GPS and opened Osmand.

Took almost 30 sec before lock.

Did the same again but then with gpstest instead of osmand; TTFF 46 secs.
[OnePlus 3 & 3T Cross Device Development] :
30 - 60 sec is normal for first fix after deleting agps data. If you get a sat lock at all after deleting agps data, the issue [MENTION=2911853]BillGoss[/MENTION] has described (no lock at all after deleting apgs data) IS fixed. All following locks should happen as fast as on los-16.0 (outdoors with blue skies ~3 - 5 sec).
[OnePlus 3 & 3T Cross Device Development] Darkestnoir:
My GPS not working at all now, finds only few sats and got no fix after 5 minutes. Flashed 0602 fresh and also tried the mentioned gps.conf from Johan2020.

Anybody tested this [Magisk Module] Step By Step Definitive GPS Solution (Global)?
[OnePlus 3 & 3T Cross Device Development] :
That's strange. Just cleared agps data again, went outside and after about 40-50 sec I had my lock.

Next time lock in only a few secs... :good:

Edit:

A sorry is at is place; I see two changes were not included, I made later. In the first lines make http instead of https, also changed ACCURACY_THRES=10 (70 as default).
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
It was in $sys_root/system/product/etc. Tried the file you sent but it didn't fix Volte.