OnePlus 6 and PocoPhone F1 Main requirements
The OnePlus 6 and PocoPhone F1 are both getting pretty well supported now, so I'm opening this issue to track what's left before potentially moving them to main (And so anyone interested can maybe chip in :D)!
Outstanding issues
OnePlus 6
Call audio
Needs Alsa UCM configs to fix the earpiece speaker, I haven't been able to get it working for quite a few kernel versions. There might be a kernel bug here but I'm not sure. The earpiece seems to be wired up differently to the Poco F1.
Charging
The OnePlus 6 has some quirk where it refuses to charge at more than 250ma, this seems to be due to some weird changes OnePlus did to support their custom Dash charging. I've done some research into it but haven't been able to resolve the issue.
OnePlus 6T
Panel
We currently have to skip the reset sequence for the 6T panel, as the init sequence in the driver doesn't work properly.
Speaker
The TFA speaker codec requires a huge downstream driver mess, and its own firmware, we currently don't carry this in our tree, but we could.
PocoPhone F1
WiFi: Although 2.4Ghz works perfectly, 5Ghz reception is poor. Not able to find the cause yet.
Mobile Data: On the surface it works, but if pmOS is dual/alternatively boot with android, somehow some modem internal config/something gets corrupted and mobile data stops working for that particular sim in pmOS (calls,sms will still work. also, in android mobile data will work. only when using pmOS/ModemManager it wouldnt). Temporary suggestion is to not boot android and pmOS with the same sim and try a different sim if mobile data doesnt work. :( Yet to find the root cause. I have a hunch that it could be related to: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/660
Poco F1 (EBBG) variant's display has some issues when display off and on, its not consistent and has issues with suspend/resume. Poco F1 (Tianma) variant's display works great and already in mainline.
Thanks Joel
Both devices
Sensors
The sensors are connected to a co-processor - the SLPI (Sensor Low Power Island), the Application Processor is prevented from communicating directly with the I2C/SPI controllers that the sensors are connected to, so the only way to communicate with them is via the SLPI. We communicate with it using ProtoBuf over QMI, so the protobuf format needs to be reversed, as well as the initialisation sequence and whatever device specific configuration is needed.
Some preliminary stuff was documented here: https://github.com/calebccff/sensordaemon-re
Wake up on phone calls/SMS
The devices don't currently wake up for calls or SMS, I asked around and it seems like the interrupt responsible for this is handled by one of the Glink drivers, these currently don't configure the interrupt as a wakeirq. This would need to be fixed. This interrupt may also be the one that fires for things like remoteproc crashes, we'd need to detect this and put the device back into suspend if this is the case, as some devices (e.g. laptops) might not automatically suspend again after waking up.
GPS
It could be talked to using ModemManager if I am right. But havent experimented with it much yet. These could improve the situation:
Activity
added help wanted label
added category::device + 1 deleted label
@calebccff the GPS works perfectly on my new Oneplus 6? Down to the meter I'm correctly positioned on Gnome Maps out of the box, and I don't think it's Wifi triangulation (it's not cellular triangulation as I have no SIM card in it).
I just posted a video of this here, and there's some confusion as to what works so I thought I'd try to bring the wiki up to date. A few more things seem to work on the phone than on the wiki, so I took the liberty of updating the wiki as you mentioned once sometimes the documentation lags behind? Feel free to update any of my edits to what works/doesn't please, and hope I didn't cause confusion.
Same for battery - why is this partial? I get 3 full days on idle w/ suspend, and charging is no longer an issue as I believe @calebccff removed that caveat from the wiki, and it works great for me now (no more fastboot mode only charging).
So I moved battery and GPS to yes, and calls to partial. Hope that's ok. https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada)
Love what you do and thank you!
By Niko on 2022-11-06T18:17:24
Edited by Administrator-
Will check GPS now! And just to provide some data for my battery/charging change this is the wiki edit where caleb removed the battery caveat, and my real-world experience is that the battery is far from "partial". Suspend loses around 20% a day when in suspend for me and charges normally. https://wiki.postmarketos.org/index.php?title=OnePlus_6_%28oneplus-enchilada%29&type=revision&diff=32137&oldid=32030
By Niko on 2022-11-06T21:37:14
-
Yep I see a bright blue dot at the correct location in Google Maps and have location enabled in Settings, but when I run
mmcli --location-monitorin Console I get:error: no modem was specifiedEDIT:
mmcli -Lreturns:error: couldn't find the ModemManager process in the busBy Niko on 2022-11-06T21:45:27
Edited by Administrator -
How do I find a list of my modem
mmcli -m any?error: couldn't find the ModemManager process in the bus
In case you're running this in ssh shell, then you should run this in the user's session terminal, or at least import DBUS_SESSION_BUS_ADDRESS (I think) env var from your logged in user on the phone. In any case make sure modemmanager service is running
By Alexey Min on 2022-11-06T21:51:44
-
Try
rc-service modemmanager statusFor me mmcli returns some info, GPS section has only nmea field, 3GPP is there too. I am not able to test GPS properly indoors, will try to do that outdoors later. Right now, my location looks like it's WiFi-based.
But I'd bet that GPS is still broken, and the way GNOME Maps does not show range marker when zoomed in further, was the reason you thought otherwise. (Looks like a bug in Maps to me...) To test GPS properly, make sure to zoom out, and test in outdoors conditions when you change your position.
By Grzegorz Sadowski on 2022-11-06T23:15:00
Edited by Administrator -
Aha! Maybe I mistook the WiFi based location for a GPS location then!
When I run
rc-service modemmanager statusI getstatus: stoppedBy Niko on 2022-11-07T21:36:32
Edited by Administrator -
@tpikonen Is it maybe triangulating your position over Cellular and/or WiFi though? That was my misunderstanding too. Although I too am perfectly positioned, tis' not actual GPS being used, even if you I am positioned precisely on a map.
The fact that it only works for you if there's an unlocked SIM on the device seems to hint at the fact that it's cellular triangulation positioning going on? Maybe I'm missing something though!
By Niko on 2022-12-16T23:57:32
-
No. You can use Satellite (the flatpak works fine) to check the GNSS reception. If the receiver in your device has not been on recently, it may take 15 min or so to get a lock, but you should see at least some signals in about a minute (or right away with a 'warm' receiver).
As said, the location interface in ModemManager does not work with locked modems, so you need an unlocked SIM.
By Teemu Ikonen on 2022-12-20T17:27:04
Edited by Ghost User -
Hello, just for sharing my experience, I have an output when I use the following command with
-m 0which is very important because if I understood well, it designates the modem "number" in the command :mmcli -m 0 --location-enable-gps-nmea.Anyway : what to do with this output ? When I open Puremaps/Gnome Maps, I still have a location fix every ~10mn which is incompatible with navigation. I can't use my Oneplus in my car and I can't advise anybody asking me a location in the street (in case of emergency for instance).
So, is there any possibility to make the GPS work ? I am even okay to install proprietary packages if necessary, because this feature (and camera) is essential in modern phone. Thank you.
By prog-amateur on 2023-02-03T13:42:51
Edited by Administrator -
Anyway : what to do with this output ? When I open Puremaps/Gnome Maps, I still have a location fix every ~10mn which is incompatible with navigation. I can use my Oneplus in my car and I can advise anybody asking me a location in the street (in case of emergency for instance).
You mean that the fix takes 10 minutes to complete? You can inject A-GPS data to reduce the time to get a fix by:
mmcli -m any --location-statusThis will print 3 URLs normally where you can get the data, download it with
wgetorcurland inject it:mmcli -m any --location-inject-assistance-data=/path/to/downloaded/fileThis procedure will be automatically in the future.
By Dylan Van Assche on 2023-06-13T10:21:53
Edited by Ghost User -
So, is there any possibility to make the GPS work ?
I'm starting to worry what's wrong with my Oneplus 6, since its GPS works more or less perfectly.
If you insist on testing with
mmcli, then you can get NMEAs by enabling the GPS receiver and AGPS MSB.mmcli -m any --location-enable-gps-nmea mmcli -m any --location-enable-agps-msb mmcli -m any --location-status mmcli -m any --location-getThis is all done automatically by correct client software, like geoclue and satellite.
It's also useful load the assistance data for AGPS as Dylan said. Without AGPS it takes at least 10 min to get a fix on a cold device.
By Teemu Ikonen on 2023-02-03T10:41:10
Edited by Ghost User -
Dear @dylanvanassche , dear @tpikonen , thank you very much for your kind help. I would like to correct my previous comment : in Puremaps or Gnome maps, the fix happen every 10mn (first fix = 10mn, then it cannot track me, then 10mn after it fix again, etc.).
After testing based on your comments, there was some progress but I still struggle to get the GPS working. Please find the outputs of your instructions :
0. Conditions :
- Wifi : ON
- Data (4G) : ON
- Position (privacy settings) : ON (I can also see the icon on the notification bar)
- Bluetooth : OFF
1. GPS/A-GPS enabling inputs :
mmcli -m any --location-enable-gps-nmea mmcli -m any --location-enable-agps-msb-> this gives me the following output :
successfully setup location gathering2. Location status :
mmcli -m any --location-status-> this gives me the following output :
----------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea, agps-msb | signals: no ----------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275Sometimes I have the same result but with
signals: yesandrefresh rate: 1 seconds.What is very intesresting is that there is no 3 URLs, only 1 URL and when I try
wget supl.google.com:7275it gives me the following output :Connecting to supl.google.com:7275 wget: error getting response: Connection reset by peerThe same input but without the port (
wget supl.google.com) gives me a server error 404 Not Fount.3. Positioning :
mmcli -m any --location-get-> this gives me the following output (this was tested in a city area in my job location where the network is good) :
----------- GPS | nmea: | $PQWP1,095551.25,03,0.820304751,0.069813170,0.00,326716.03,6000.00,3*324. Satellite flatpak app :
The app does not show any satellite around me. Please find the log :
[11:15:00] Satellite version 0.3.1 started [11:15:00] Trying to initialize source "quectel" [11:15:08] Source is QUALCOMM INCORPORATED, model 0, revision MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] Lock lost [12:18:27] NMEA info not received with locationPlease, based on these outputs and tests, what do you think ? Thank you very much !
By prog-amateur on 2023-02-03T13:42:15
Edited by Administrator -
@tpikonen There's nothing wrong with your Oneplus 6 ;) I have seen this working on some SDM845 devices and some not.
@prog-amateur It seems you are 'unfortunate' with your device. Some devices report these 3 URLs (with Qualcomm XTRA support), some only report the SUPL server. We still don't know why though. I only got it working with XTRA, not when only the SUPL server was reported. You cannot use
wgetfor SUPL as it pure IP based, not HTTP. SUPL requires either MSA or MSB enabled and goes through your carrier and stuff, reporting your phone number to the SUPL server as Google so I don't investigate that option and rather avoid and disable it completely.However, you get some NMEA responses, but is that really all?
By Dylan Van Assche on 2023-02-03T17:44:02
-
@prog-amateur indeed you seem to be unlucky with your device. Your firmware version is exactly the same as here, but I get this from
mmcli -m any --location-status:-------------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, cdma-bs, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea, cdma-bs, agps-msb | signals: no -------------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275 | supported assistance: xtra | assistance servers: https://xtrapath1.izatcloud.net/xtra3grcej.bin | https://xtrapath2.izatcloud.net/xtra3grcej.bin | https://xtrapath3.izatcloud.net/xtra3grcej.binI suggest you try to download and inject the file from one of the assistance servers (
mmcli -m any --location-inject-assistance-data=<file>) and then letwatch mmcli -m any --location-getrun for some time to see if you get any $GPGGA or $GPGSV sentences.Injecting the assistance data may not work though, since ModemManager does not report it being supported (
supported assistance: xtra) on your device.By Teemu Ikonen on 2023-02-03T20:41:26
-
@dylanvanassche
However, you get some NMEA responses, but is that really all?
Thank you. Yes, I see only NMEA this is really strange, I think it could be related to my dual SIM version. I have 2 slots with 1 SIM card inserted only. By the way, what version do you have (single or dual SIM) ?
@tpikonen
I suggest you try to download and inject the file from one of the assistance servers
Thank you, I have an error message with this method unfortunately. Same question : what version do you have (single or dual SIM) ?
I have done further investigations with
mmcli -m anydue to my dual SIM version (I have edited withXXXXXXXXXXto hide some elements), please see the output :----------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: XXXXXXXXXX ----------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | carrier config: Bouygues_France_Commercial | carrier config revision: 08013B08 | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: XXXXXXXXXX ----------------------------------- System | device: qcom-soc | drivers: ipa, rpmsg_ctrl, qrtr | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ----------------------------------- Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: [32mconnected[0m | power state: on | access tech: lte | signal quality: 80% (recent) ----------------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ----------------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ----------------------------------- IP | supported: ipv4, ipv6, ipv4v6 ----------------------------------- 3GPP | imei: XXXXXXXXXX | enabled locks: sim, fixed-dialing | operator id: 20820 | operator name: Bouygues Telecom | registration: home | packet service state: attached ----------------------------------- 3GPP EPS | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: mmsbouygtel.com | initial bearer ip type: ipv6 ----------------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 | slot 2: none (active) ----------------------------------- Bearer | paths: /org/freedesktop/ModemManager1/Bearer/1As you can see, the
slot 1contains the SIM card, but it is not mentioned(active), whileslot 2is empty and is mentioned as(active).Switching SIM card from slot 1 to slot 2 properly (no "hot swap") makes the phone crash (error window :
Oh no! Something has gone wrong. A problem occured and the system can't recover. Please log out and try again). As I still could have access to the terminal, I have triedmmcli -m anywith the following output :----------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: XXXXXXXXXX ----------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: XXXXXXXXXX ----------------------------- System | device: qcom-soc | drivers: ipa, rpmsg_ctrl, qrtr | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ----------------------------- Status | lock: sim-pin | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: locked ----------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ----------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ----------------------------- IP | supported: ipv4, ipv6, ipv4v6 ----------------------------- 3GPP | enabled locks: sim, fixed-dialing ----------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: none | slot 2: /org/freedesktop/ModemManager1/SIM/0 (active)As you can see here,
slot 1is empty, andslot 2has the right freedesktop path and is state as(active).So my idea was to put back the SIM card in
slot 1and trying to switch "activate" the slot 1 and deactivateslot 2, but I am begineer in mmcli and I could succeed to do so. What do you think ?Thank you so much !
By prog-amateur on 2023-02-04T11:17:41
-
Aha! I see what happens ;)
----------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: XXXXXXXXXX ----------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | carrier config: Bouygues_France_Commercial | carrier config revision: 08013B08 | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: XXXXXXXXXXLook at that carrier config entry! It is different than on mine:
ROW_Commercial. This means that the SoC found a matching carrier config for your SIM. These configs contains various low level stuff like VoLTE support, but also GPS configuration. This way, carriers can request to use a different SUPL server for example. You played already with the slots and saw that it crashes then, there's no carrier config available in the 2nd dump, so that is already not really good. Not sure what is active then on the modem in that case.Can you try a SIM from a different carrier?
By Dylan Van Assche on 2023-02-05T13:24:32
Edited by Administrator -
Thank you very much @dylanvanassche ! I think you are right, please see the results with a Free SIM card (as a reminder: my SIM card is Bouygues) :
1.
sudo mmcli -m any:----------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: XXXXXXXXXX ----------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | carrier config: Oversea-Commercial_DS | carrier config revision: 0801F13A | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: XXXXXXXXXX ----------------------------------- System | device: qcom-soc | drivers: qrtr, ipa, rpmsg_ctrl | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ----------------------------------- Numbers | own: XXXXXXXXXX ----------------------------------- Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: registered | power state: on | access tech: lte | signal quality: 59% (recent) ----------------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ----------------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ----------------------------------- IP | supported: ipv4, ipv6, ipv4v6 ----------------------------------- 3GPP | imei: XXXXXXXXXX | enabled locks: sim, fixed-dialing | operator id: 20815 | operator name: Free | registration: home | packet service state: attached ----------------------------------- 3GPP EPS | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer ip type: ipv4v6 ----------------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 | slot 2: none (active)-> interesting thing : the SIM card is in slot 1 and like for Bouygues, slot 2 is still empty but stated as
(active).2.
sudo mmcli -m any --location status:-------------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: gps-nmea, agps-msb | signals: yes -------------------------------- GPS | refresh rate: 1 seconds | a-gps supl server: supl.google.com:7275 | supported assistance: xtra | assistance servers: https://xtrapath3.izatcloud.net/xtra3grcej.bin | https://xtrapath1.izatcloud.net/xtra3grcej.bin | https://xtrapath2.izatcloud.net/xtra3grcej.bin-> here, unlike
Bouygues, localization is enabled, and I can see the 3 URLs.3. Satellite flatpak app :
The app find the signals quickly !
4. Questions :
Now, I would like to understand :
-
the Free operator is recent in France, Bouygues has a lot of history
-
with Android (before installing PostmarketOS), A-GPS was working with Bouygues without any problem
-
-> therefore : why my Bouygues SIM card can't have A-GPS in PostmarketOS ? is there anything I can tweak (config file, etc.) to make the GPS working with my SIM card ?
Once again, thank you very much for your kind help, I hope we are close to solve this issue !
By prog-amateur on 2023-02-05T13:24:15
-
-
ooooooh this super great! Finally my hypothesis about this black box thing pays off ;)
with Android (before installing PostmarketOS), A-GPS was working with Bouygues without any problem why my Bouygues SIM card can't have A-GPS in PostmarketOS ?
You can have A-GPS via SUPL servers (agps-msa/agps-msb in ModemManager) or XTRA (inject assistance data in ModemManager). Carriers can configure all of this if they want in these modem profiles. They get activated by the operator ID on the SIM card normally.
Currently, we don't have everything in place like on Android to handle all these options as everything is proprietary so we have to reverse engineer here what happens and what we are missing.
is there anything I can tweak (config file, etc.) to make the GPS working with my SIM card ?
I think we can load a different modem config file in your case, but I'm not sure as I have mixed results with that in the past on my SHIFT6mq so I'm a bit hesitant (I don't want to break anyones phone ;) ). I got it working like that on the SHIFT6mq for a while but then never ever again. Currently loading these modem config files is also volatile, it does not persist across reboots. ModemManager has support for 1 modem already to load config files that are available inside the modem, but a lot of them are just stored in the modem partition on Android which require to be loaded first onto the modem. We don't have the infrastructure for this yet, but we should have it in the future as it brings also VoLTE support for example.
By Dylan Van Assche on 2023-02-05T13:31:59
-
Thank you for all those details ! Well somebody has to test it... Do you think we can save the modem config file ? I ask this because I would like to test with a tweaked modem config, but in case it doesn't work (and persist after reboot unexpectedly), I would be happy to restore the old one. thank you
By prog-amateur on 2023-02-06T11:38:37
-
Hi, I'm having similar GPS problems with my OnePlus 6.
Similar to @prog-amateur, I do only get a
$PQWP1line. I ranmmcli -m any --location-getfor quite some time but didn't get any$GPGGAor$GPGSVsentences.The steps I did
- SIM: https://www.netzclub.net
- Wifi: ON
- Data (4G): ON
- Position (privacy settings): ON
sudo mmcli -m 0 --location-enable-gps-nmea #=> successfully setup location gatheringsudo mmcli -m 0 --location-get-------------------------- 3GPP | operator mcc: 262 | operator mnc: 03 | location area code: 0000 | tracking area code: 00E4FF | cell id: 0138DD19 -------------------------- GPS | nmea: | $PQWP1,095049.47,03,0.900415361,0.181339711,0.00,256705.44,6000.00,3*3Bmmcli -m any --location-status----------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea | signals: no ----------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275sudo mmcli -m 0 --location-enable-gps-raw #=> successfully setup location gatheringsudo mmcli -m 0 --location-status----------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-raw, gps-nmea | signals: yes ----------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275sudo mmcli -m 0 --location-enable-agps-msa #=> error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Aborted: Couldn't enable location 'agps-msa' gathering: Failed to receive operation mode indication'sudo mmcli -m 0 --location-enable-agps-msb #=> error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Aborted: Couldn't enable location 'agps-msb' gathering: Failed to receive operation mode indication'sudo mmcli -m 0---------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: cc3fd9464eaa9dd3bd9b769a603d10bc75da751e ---------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: 861949041755659 ---------------------------------- System | device: qcom-soc | drivers: ipa, rpmsg_ctrl, qrtr | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ---------------------------------- Numbers | own: 49159**REDACTED** ---------------------------------- Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: connected | power state: on | access tech: lte | signal quality: 80% (recent) ---------------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 3g, 4g; preferred: 4g ---------------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ---------------------------------- IP | supported: ipv4, ipv6, ipv4v6 ---------------------------------- 3GPP | imei: **REDACTED** | enabled locks: sim, fixed-dialing | operator id: 26203 | operator name: o2 - de | registration: home | packet service state: attached ---------------------------------- 3GPP EPS | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4 ---------------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 | slot 2: none (active) ---------------------------------- Bearer | paths: /org/freedesktop/ModemManager1/Bearer/1Notes
Not sure, why
agps-msa/agps-msbcan't be activated.I hope some of this information is helpful. If I can provide more, please let me know.
By langfingaz on 2023-06-14T13:25:08
Edited by Administrator -
Can you test with a SIM from a different operator? The GNSS problems in OP6 have been traced to the operator dependent modem configuration previously in this thread.
Not sure, why agps-msa/agps-msb can't be activated.
This is a known but recent bug, see #2030. The lack of MSA or MSB does not seem to affect the GNSS performance in OP6 that much though, I get reasonably fast fixes also without them.
By Teemu Ikonen on 2023-06-14T08:37:19
-
Thanks for the information about AGPS MSA/MSB bug.
I tried the same/similar steps with another SIM card. But the results are very similar. Maybe it is because both operators use the same physical cell network?
One difference is that I had to restart my modem (after booting) in order to unlock the SIM card. And after that, slot 2 is still marked as "active" in the output of
sudo mmcli -m any.Here are my notes:
- SIM: https://www.alditalk.de/
- Wifi : ON
- Position (privacy settings) : ON
After boot, no SIM unlock entry came up. The SIM is in the first slot, but the second one is active:
sudo mmcli -m any----------------------------- General | path: /org/freedesktop/ModemManager1/Modem/1 | device id: cc3fd9464eaa9dd3bd9b769a603d10bc75da751e ----------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: 861949041755659 ----------------------------- System | device: qcom-soc | drivers: ipa, rpmsg_ctrl, qrtr | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ----------------------------- Status | state: failed | failed reason: sim-missing ----------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ----------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ----------------------------- IP | supported: ipv4, ipv6, ipv4v6 ----------------------------- SIM | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/1 | slot 2: none (active)After restarting the modem, the SIM unlock entry came up:
sudo service modemmanager stop sudo service msm-modem-uim-selection restart sudo ModemManager --debug 2>&1 | tee mm.logMobile Internet (with disabled WIFI) is working.
sudo mmcli -m 0 --location-enable-gps-nmea #=> successfully setup location gatheringsudo mmcli -m 0 --location-get-------------------------- 3GPP | operator mcc: 262 | operator mnc: 03 | location area code: 0000 | tracking area code: 00E4FF | cell id: 013B5B16 -------------------------- GPS | nmea: | $PQWP1,132626.47,03,0.900415361,0.181339711,0.00,256705.44,6000.00,3*38mmcli -m 0 --location-status------------------------ Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea | signals: no ------------------------ GPS | refresh rate: 0 secondssudo mmcli -m 0 --location-enable-gps-raw #=> successfully setup location gatheringsudo mmcli -m 0 --location-enable-agps-msa #=> error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Aborted: Couldn't enable location 'agps-msa' gathering: Failed to receive operation mode indication'sudo mmcli -m 0 --location-enable-agps-msb #=> error: couldn't setup location gathering: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Aborted: Couldn't enable location 'agps-msb' gathering: Failed to receive operation mode indication'sudo mmcli -m 0---------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: cc3fd9464eaa9dd3bd9b769a603d10bc75da751e ---------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: 861949041755659 ---------------------------------- System | device: qcom-soc | drivers: qrtr, ipa, rpmsg_ctrl | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ---------------------------------- Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: connected | power state: on | access tech: lte | signal quality: 75% (recent) ---------------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ---------------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ---------------------------------- IP | supported: ipv4, ipv6, ipv4v6 ---------------------------------- 3GPP | imei: ***** | enabled locks: sim, fixed-dialing | operator id: 26203 | operator name: MEDIONmobile | registration: home | packet service state: attached ---------------------------------- 3GPP EPS | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4 ---------------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 | slot 2: none (active) ---------------------------------- Bearer | paths: /org/freedesktop/ModemManager1/Bearer/1I ran the following command for 30 minutes with the smartphone in direct sunlight but didn't get any $GPGGA or $GPGSV sentences:
sudo watch mmcli -m any --location-getNeither did I get a fix or a location here:
flatpak run page.codeberg.tpikonen.satelliteBy langfingaz on 2023-06-14T14:21:06
-
I tried the same/similar steps with another SIM card. But the results are very similar. Maybe it is because both operators use the same physical cell network?
They have the same operator id, which seems to be the thing that determines the configuration, so yes.
By Teemu Ikonen on 2023-06-14T19:37:49
-
Thanks again! I ordered a SIM card from another provider (Vodafone this time) which has no monthly basic fee. When it arrived, I'll test locationing again.
Should this work with mobile data disabled if connected to WIFI? Including A-GPS? (Otherwise I would add a data package to the SIM)
By langfingaz on 2023-06-16T08:04:05
-
There needs to be a an unlocked SIM card in the phone for the GNSS to work. This is (AFAIK) a ModemManager limitation.
AGPS-MSA needs a data connection when acquiring a fix, MSB needs a data package download every few days. I'm not sure if either of them work ATM, but the GNSS performance is acceptable anyway.
By Teemu Ikonen on 2023-06-17T07:35:01
-
So, I tried it again if I can get accurate location with my OnePlus 6. This time with a Vodafone (Germany) SIM card. I still didn't get any
$GPGGAor$GPGSVsentences with--location-get.And when running
sudo mmcli -m anyI still don't see anycarrier config...
- SIM: https://vodafone.de/CallYa
- Wifi: ON
- Position (privacy settings): ON
SIM pin entry came up on boot. Automatically configured APN named "Mobile Broadband" is web.vodafone.de
sudo mmcli -m 0 --location-enable-gps-nmea #=> successfully setup location gatheringsudo mmcli -m 0 --location-get-------------------------- 3GPP | operator mcc: 262 | operator mnc: 02 | location area code: 0352 | tracking area code: 000000 | cell id: 0000D9E7 -------------------------- GPS | nmea: | $PQWP1,142830.47,03,0.900415361,0.181339711,0.00,256705.44,6000.00,3*36mmcli -m 0 --location-status----------------------------- Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea | signals: no ----------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275sudo mmcli -m 0 --location-enable-gps-raw #=> successfully setup location gatheringsudo mmcli -m 0---------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: cc3fd9464eaa9dd3bd9b769a603d10bc75da751e ---------------------------------- Hardware | manufacturer: QUALCOMM INCORPORATED | model: 0 | firmware revision: MPSS.AT.4.0.c2.15-00007-SDM845_GEN_PACK-1.358880.1.399256.2 1 [May 09 2021 22:00:00] | h/w revision: 20001 | supported: gsm-umts, lte, tds | cdma-evdo, lte, tds | lte, tds | cdma-evdo, gsm-umts, lte, tds | current: gsm-umts, lte, tds | equipment id: 861949041755659 ---------------------------------- System | device: qcom-soc | drivers: qrtr, ipa, rpmsg_ctrl | plugin: qcom-soc | primary port: qrtr0 | ports: qrtr0 (qmi), rmnet_ipa0 (net), rpmsg_ctrl2 (ignored) ---------------------------------- Numbers | own: **redacted** ---------------------------------- Status | lock: sim-pin2 | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10) | state: registered | power state: on | access tech: gsm | signal quality: 68% (recent) ---------------------------------- Modes | supported: allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: 3g | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 4g; preferred: 4g | allowed: 2g, 4g; preferred: 2g | allowed: 3g, 4g; preferred: 4g | allowed: 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 4g | allowed: 2g, 3g, 4g; preferred: 3g | allowed: 2g, 3g, 4g; preferred: 2g | current: allowed: 2g, 3g, 4g; preferred: 4g ---------------------------------- Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-3, utran-4, utran-6, | utran-5, utran-8, utran-9, utran-2, eutran-1, eutran-2, eutran-3, | eutran-4, eutran-5, eutran-7, eutran-8, eutran-12, eutran-17, | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, | eutran-40, eutran-41, eutran-66, eutran-71, cdma-bc0, cdma-bc1, | utran-19 | current: egsm, dcs, pcs, g850, utran-1, utran-4, utran-5, utran-8, | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, | eutran-7, eutran-8, eutran-12, eutran-17, eutran-18, eutran-19, | eutran-20, eutran-25, eutran-26, eutran-28, eutran-29, eutran-30, | eutran-32, eutran-34, eutran-38, eutran-39, eutran-40, eutran-41, | eutran-66, eutran-71, cdma-bc0, cdma-bc1, utran-19 ---------------------------------- IP | supported: ipv4, ipv6, ipv4v6 ---------------------------------- 3GPP | imei: **redacted** | enabled locks: sim, fixed-dialing | operator id: 26202 | operator name: Vodafone.de | registration: home | packet service state: attached ---------------------------------- 3GPP EPS | initial bearer apn: internet | initial bearer ip type: ipv4 ---------------------------------- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/1 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 | slot 2: none (active)By langfingaz on 2023-06-24T12:03:41
-
location works via antenna triangulation, but not via gps! i am testing this since weeks while cycling through portugal, spain, france, england, ireland... as soon as i leave crowded places with lots of antennas or supermarkets with public wifi, it looses the position. tested on op6, pmos & mobian, mainline, no android partition nor recovery, disabled suspend, plugged to powersource. willing to test alpha firmware!
By magdesign on 2023-07-08T09:54:24
-
What @sado1sado meant it that if GPS works on your OP6 depends on the SIM card you are using.
I have, for example, tried a Vodafone (Germany) SIM card and could not get working GPS (see here: #1505 (comment 1444436251)). Instead, I had only an approximate location (the same as you described).
@magdesign What provider are you using? Can you provide the output of
sudo mmcli -m any?By langfingaz on 2023-07-08T10:51:28
Edited by Administrator -
Did you try with other sim cards, like the other people in this thread?
The consensus so far, is that due to different SIM provider settings (mainly related to assistance servers), with some simcards it is impossible to use AGPS (unless you inject AGPS data manually, there was a proof-of-concept script to do that). This was the reason for long fix times. If you want to change the general consensus, more proof is needed.
Obviously, antenna triangulation does work, and it also depends on user's provider, which may make troubleshooting GPS issues a bit more complicated.
By Grzegorz Sadowski on 2023-07-08T10:53:36
Edited by Administrator -
@magdesign For some mysterious reason, the GPS works when some SIM cards are used, but not with others. This is something with the firmware.
If
mmcli -m any --location-statusshows 3 URLs of assistance servers, GPS should work. If it doesn't, it will not provide NMEA sentences, even when GPS was enabled by GeoClue. The latter certainly happens as I have a SIM here where it works on the POCO F1, but as soon as you put the same SIM in a SHIFT6mq which has slightly different firmware, GPS is broken there.Until today, it remains unclear what causes the firmware to behave differently regarding GPS depending on the SIM card.
By Dylan Van Assche on 2023-08-29T20:05:20
Edited by Ghost User -
@sado1sado tried with: Salt (Swiss), Orange (Morocco), Mauritel (Mauretania), Orange (Guinea), SFR (France), Lebara (UK), Lebara (DE) (should start to keep all the sim cards and bring them to a dev) However, mobile data seems not to work under sxmo, after adding apn.
edit: just figured out that under mobian my wifi is not working and this seems to be because the drivers are not packed into the os as with pmos. this could also cause that gps on some devices is working (as users say...)
By magdesign on 2023-09-25T12:49:35
Edited by Administrator -
@langfingaz @magdesign Of course, this is just a theory, but from which version of android did you switch to PmOs? I had an interesting dependency on Poco F1, if you install pmos with different versions of android before, the mobile Internet could simply not work for me. Now I have a problem similar to yours on op6t, I could not get a working gps from any of the sim cards, I put pmos with oos11
By Jaymz 665 on 2023-08-19T08:03:27
-
I bought a new sim card, and another used OP6, and GPS worked flawlessly for me there. This new card does not heal GPS on my old model, though.
What's weird: I flashed PMOS after having android 9 then ubports on the old model, and apart from the GPS issue, I get crashdump on every boot, unless I push volume down while booting. I am pretty sure I need to reflash latest Android on both slots and GPS might work with the new sim card, along with hopefully fixing crashdump issue as well. Will report back, as this would confirm that some of you may suffer from wrong firmware being flashed apart from having a SIM that is not friendly to GPS on Linux.
By Grzegorz Sadowski on 2023-08-22T20:53:51
-
Sounds like something to be worth trying
By langfingaz on 2023-09-12T20:06:03
-
Please disregard my previous report for now; I am not sure if my testing methodology was correct (and if AGPS worked at all). Reflashing OOS did not help for the other model, either (although crashdumps are gone). I need to gather more data about it.
To flash on both slots, the easiest way is to first flash OOS, then flash copy-partitions ZIP through custom recovery. Basically a few first steps of https://wiki.lineageos.org/devices/enchilada/install (make sure to read installation guide for your own model! this link is for OP6 only)
By Grzegorz Sadowski on 2023-10-08T12:45:46
Edited by Ghost User -
@Jaymz665 there was lineageos on it. but i managed to delete the recovery partition and so its not possible to install any android again (no option to flash twrp) for testing. still in hope that someone will solve this gps quest. will test with all sim cards on my travels, but i am sure its a driver/firmware issue..
By magdesign on 2023-09-25T12:50:09
Edited by Administrator -
@magdesign I don't believe any SDM845 devices have a recovery partition if there's A/B slots, it's simply unneeded: https://source.android.com/docs/core/ota/ab
By Jami Kettunen on 2023-09-18T17:49:38
-
@magdesign @langfingaz @sado1sado I've done a couple of experiments. I will not torment, immediately to the results, after installing OOS version 9.0.16, GPS started working for me (when installing version 9.0.6, the mobile Internet did not work!). So yes, it's about the firmware. I don't know if it affects, but just in case, after the OOS firmware, I checked the mobile Internet and gps, then I flashed pmos
By Jaymz 665 on 2023-10-30T08:41:54
Edited by Ghost User -
I think this will help, OOS11 did not give gps, a similar problem exists on pocof1 (when installing android above version 11, mobile Internet disappears), so I assume something similar is happening here.
Everything should work out of the box. The only thing I did to make sure the gps was working:
mmcli -m any --location-status-------------------------------- Location | capabilities: 3gpp-laci, gps-raw, gps-nmea, agps-msa, agps-msb | enabled: 3gpp-lac-ci, gps-nmea | signals: yes -------------------------------- GPS | refresh rate: 0 seconds | a-gps supl server: supl.google.com:7275 | supported assistance: xtra | assistance servers: https://path2.xtracloud.net/xtra3grcej.bin | https://path3.xtracloud.net/xtra3grcej.bin | https://path1.xtracloud.net/xtra3grcej.binBy Jaymz 665 on 2023-10-18T08:40:17
-
I am happy to confirm that flashing 9.0.8 on both slots, then flashing PMOS Edge, results in working GPS on my OP6.
By Grzegorz Sadowski on 2024-01-15T10:52:09
Edited by Ghost User -
pmOS and other mobile Linux distros in general do not use Halium (except for UBPorts aka Ubuntu mobile, Droidian and Sailfish OS). But our experience suggests that something happens after flashing a "wrong" Android version, which breaks GPS on pmOS installed on such phone later. It would need to be debugged by somebody why and where the problem happens - but at least we have a solid workaround now.
By Grzegorz Sadowski on 2023-10-27T12:49:14
-
As for a guide, I'll try to add this to device page at some point, but here's a few quick notes about how I do it:
- make sure to download OxygenOS in the right version (9.0.8 OP6, 9.0.16 OP6T), if you want GPS to work
- dtbo is erased during installation procedure of pmOS, which blocks booting custom recovery image from pmOS' slot. So, to boot/flash a recovery, you need to switch to the other slot first. Then, you can use fastboot-flashable ZIPs with OxygenOS (I think it was easily available on OnePlus forums)
- Finally, flash copy-partitions ZIP through a custom recovery - it copies the freshly installed OS to the other slot. Basically a few first steps of https://wiki.lineageos.org/devices/enchilada/install (make sure to read installation guide for your own model! this link is for OP6 only)
Alternate options for above, would be to use OnePlus' official software to recover (Windows needed), or use one of the EDL tools; but I did that months ago and I do not remember the details. For sure the EDL way on Linux was weird and I spent some time before I finally understood what I want to do.
By Grzegorz Sadowski on 2023-10-27T13:04:17
-
Thanks @Jaymz665 for figuring out that it is the previously installed Android version, which breaks GPS (or mobile data)! And thanks @sado1sado for your guide! I can confirm, that GPS is working on my OnePlus 6 on gnome-mobile out of the box after first installing OOS 9.0.8 on both slots.
When I previously reinstalled Android, I had used android-ota-payload-extractor to get the partition images and flashed those with
fastboot. This did, however, not work with the Android 9 image (OOS 9.0.8). The reason was, that I had previously Android 11 (OOS 11) installed.My solution was to first reinstall Android 11 and then do a rollback/downgrade to Android 9 following this guide for the OnePlus6/6T. After this I upgraded to OOS 9.0.8.
Not sure if these steps are more complicated than necessary. Maybe a fastboot-flashable ZIP of OOS 9.0.8 would have worked directly?
By langfingaz on 2023-10-30T09:04:33
-
yup, you can restore with either fastboot-flashable ZIP (which is basically a convenient ZIP with all the .img files), or recovery-flashable ZIP, (as I described above, it's assuming you have a working recovery on either slot). I think I simply didn't have a package with fastboot files for 9.0.8 when I was restoring my phone, I'll check that once I restore my other model soon.
By Grzegorz Sadowski on 2023-10-31T10:19:05
-
people who flashed pmOS on both slots do not have a recovery and are somehow not allowed to flash via fastboot (even after enable write_critical). the only solution is edl mode, see my profile on pmos wiki for the exact commands. gps is working fine with the oos 9.0.8 workaround! thanks to point out.
By magdesign on 2023-11-05T18:35:24
-
Do you really have to flash an old OOS again to "fix" this, or is there some firmware partition thing from that OOS release that could be flashed on its own to achieve the same result?
By clayton craft on 2024-02-17T17:41:28
Edited by Ghost User -
i still dont get why we need data to get precise location with modemmanger. while in waydroid i get my exact position but not under linux (in the same time on the same device without data!) ??? (maybe its geoclue or 3G..)
@craftyguy so you need someone to test different scenarios or is it just a question to think about? i spent several hours to bring android back onto the op6 to finally flash pmos or droidian. its a frustrating process 🤪
By magdesign on 2024-01-16T15:54:00
Edited by Administrator -
Just to add a minor simplification to the GPS fix steps (the rollback version 9.0.4 works fine for this, tested on 6T):
- Rollback to oos 9.0.4 using this guide already linked by @langfingaz (works on oos 11 too, and no need to update afterwards to 9.0.16)
- Ensure both A/B partitions have this same version using the guide mentioned by @sado1sado (apply that zip using TWRP)
I just did this last week and GPS works fine now in pmos.
By biemster on 2024-02-16T12:37:35
-
Call audio fix for OP6 was merged in time for 22.12. Can be tracked here: #1338 (closed)
By Grzegorz Sadowski on 2022-12-06T08:52:24
Edited by Administrator -
Call audio confirmed working for me on OP6 on 22.12!
By Niko on 2023-02-03T21:59:01
Edited by Administrator -
I can also confirm call audio works somewhat reliably on OP6 with the latest pmos edge. No workarounds are needed for the UCM configs to be applied. So no need to manually install
alsa-utils(as per #1801 (closed)) or manually adjust the system sounds slider on fresh install (I left it in the default lowest volume). @joelselvaraj do you know why this might be the case? Also, at times after a successful call I won't get any audio in successive calls, which I can fix by going into the sound settings. I presume this might be the case when the Pulse module does not get unloaded properly.By Ghost User on 2022-12-06T18:03:11
-
I see you can have audio calls since a week.
- Can you confirm that you can receive calls after the phone has been suspended in RAM (I mean, can the call wake up the phone from standby/deep sleep mode)? This bug is what prevent me to use a Purism Librem 5 as a daily driver.
- Also did you find any bug related to call audio since last week ?
If the answers to these questions are OK, I'd like to buy a OnePlus 6 and try PostmarketOS as I consider this phone ready to be used as a daily driver, for my needs at least (thanks to @nikodunk 's review and setup video on YouTube).
Thank you very much for your kind feedback !
By prog-amateur on 2022-12-16T10:59:39
-
Confirmed both on 22.12. Calls from sleep have been working for me repeatedly on Phosh (won’t work on Gnome Mobile yet AFAIK), and haven’t found any new bugs. Have been daily driving it for a few days. No guarantees though :)
By Niko on 2022-12-17T13:00:18
Edited by Administrator -
I am with a "dying" Nexus 5 on Ubuntu Touch, its battery is draining fast and the screen is broken. I think this is the moment to jump into this OnePlus 6 experience.
I hope that it will be conclusive, if not, it's not dramatic, I would have tried to recycle an "old" mobile ^^
I hope also Gnome mobile will become as functional as Phosh because it has a great UI.
In any case, thanks a lot for the feedback and thanks for your very informative video and all the efforts from you and the community.
By prog-amateur on 2022-12-17T13:08:48
-
@fleetime
Also, at times after a successful call I won't get any audio in successive calls, which I can fix by going into the sound settings. I presume this might be the case when the Pulse module does not get unloaded properly.
I have some stability problems too, regarding audio routing on 22.12 (Plasma Mobile). I added an issue to track this: #1866 (closed)
By Grzegorz Sadowski on 2022-12-20T22:21:09
mentioned in issue #1866 (closed)
By Grzegorz Sadowski on 2022-12-20T22:18:41
-
After a few days of daily driver, I found using Phosh on OP6 globally positive. Please fin my feedback about what's would need to be improved :
- Wake up on Calls/SMS: disabling suspend on RAM solve the issue but affect (not so much) the battery consumption.
- GPS: it can find a fix (via Mobile ?) once per 10mn, meaning GPS cannot be used for navigation (I drove from point A to point B and the location was updated only every 10mn). I have tried to understand the links shared above about Geoclue, ModemManager, etc. but without success (my knowledge is limited), and the flatpak app Satellite gives no Signal even after several minutes so I don't understand what's wrong here.
- Loud speakers/headphones: I can't use the loud speakers/headphones during calls. Pushing the Loudspeakers button does nothing. To use headphones, I have to switch the audio device in the settings but it is not done automatically after plugging the headphones.
- Tri-state key switch (full/quiet/silent): this button is not supported. I have tried to install the apk as said in the wiki but without any success even after restart.
-
Ring phone: it does not work. Even if I put an
.ogamusic in the Tweaks app, it doesn't work (while.ogamusic works for Alarm). - The vibration motor : it vibrates continuously during a call, and in a very unpleasant way (until it makes a "clacking" sound). How to change this (vibrate / stop / vibrate / stop, etc., and / or reduce vibration force)?
-
Gnome Online Account : it works well for emails/calendar
but it does not automount any remote dav server location. If I try to add manually a remote dav (or ssh/smb/etc.) folder in nautilus, it doesn't work (the link becomes red after I put a. To get remote server, open a terminal and type:like indavs://)sudo apk add gvfs-goa && sudo apk add gvfs-dav.
Thank you very much for your kind help.
By prog-amateur on 2023-06-13T11:19:43
Edited by Administrator -
I fixed the missing ringtone in this feedbackd-device-themes MR. I think the issue will be fixed once the alpine package is updated. P.S. you can workaround the issue for the moment by copying an updated feedbackd theme to
~/.config/feedbackdBy Federico Amedeo Izzo on 2023-01-11T15:51:02
-
- There's some Nautilus related package I think you have to install. Not sure why its not in there by default. Seemingly same on Manjaro and Fedora Phosh builds I tried on Pinephone, and same on this as well.
By Gary Foster on 2023-01-06T16:35:48
Edited by Ghost User
-
- This works for me, I took three phone calls today, and the phone rang every time with the default ring tone. Maybe you meant you'd tried to set your own tone.
I would add ...
- Mobile data issues for me, can't get it to work and get the orange triangle whether I try 2G/3G/4G.
By Gary Foster on 2023-01-06T16:33:54
Edited by Administrator -
Maybe you meant you'd tried to set your own tone.
Yes it is. And since then, I can't set any ringtone, even the default one.
- Mobile data issues for me, can't get it to work and get the orange triangle whether I try 2G/3G/4G.
I had the same issue but succeed to solve it by going to "Settings > Mobile Network > Access Points Names > and add a custom access point name based on my SIM operator (you can usually find it by googling)".
By prog-amateur on 2023-01-06T16:33:54
-
Hello, I am on Mobile GNOME v23.06 stable and I have 2 problems :
- I see that many windows don't fit the screen. Please, as I can't use the "Mobile settings" app (because it is related to Phosh) : do you know a way/script to adjust the scaling so I can use the phone comfortably ?
- The rotate screen button is missing : please, do you know how to make it appear ?
Thank you very much for your kind help.
By prog-amateur on 2023-07-31T19:51:41
Edited by Ghost User -
The discussions in this issue should ideally be about the overall status of the device ports and issues around moving these devices from
communitytomaincategory. Like what we are lacking and debugging some of the core issues.For general issues related to Gnome Mobile or any interface, it would be better to ask in the related place than here. For example you can ask in the Gnome Mobile matrix chat group (https://matrix.to/#/#mobile:gnome.org) or the postmarketOS matrix chat group(https://matrix.to/#/#main:postmarketos.org) or the gnome mobile fork's gitlab issue tracker (https://gitlab.gnome.org/verdre/mobile-shell) as mentioned in their README.
Also remember gnome mobile is just a prototype at this stage and still lacks a lot features and mostly being worked on by few people. It is slowly being merged into upstream gnome and probably might only get better support after that.
By Joel Selvaraj on 2023-07-31T19:51:41
-
A summary of the current state, from my perspective as an OP6 user... Feel free to correct me and add further information.
TL;DR: Wake up and (if still an issue) earpiece fixes are left to fix; plus sensors which already have a draft MR in good shape.
Call audio with earpiece was implemented: #1338 (closed) Although last time I checked, pmOS stable had a problem with switching between earpiece/speaker after a call - earpiece would no longer work in subsequent calls. I think there was an issue tracking that, I will try to test it and report back. I remember fast charging was fixed.
Sensors draft MR: !4050 (merged) OP6 and OP6T are supported, F1 isn't yet.
Wake up on phone calls/SMS - I don't know if anybody is working on this. My OP6 (on edge) does not wake up on call - modem seems to be alive though, as I only need to push the power button, and it suddenly notices the incoming call.
GPS just works.
A few people (like me) had to flash OnePlus' Android 9 on both slots (9.0.8 for OP6, 9.0.16 for OP6T), before installing pmOS, to get it to work. You also may have less luck about AGPS with specific carriers (I think it can still be injected in such case). For more details, see the long GPS thread in this issue's comments.
Additionally, some support for replacement screens was merged some time ago as well.
Other conclusions:
- GPS bound to Android version installed before pmOS is something minor, but maybe worth investigating later
- in my opinion, GPS status should be 'green' despite what I mention above
- I'll try to update the OP6 wiki to include information from this thread (ie. about GPS)
- I think a generic GPS guide in wiki for troubleshooting, might be a good idea - information in this thread and in OP6 article is generic enough and should be put in a separate place.
By Grzegorz Sadowski on 2024-03-20T13:58:12
Edited by Ghost User -
Here's the GPS guide based on the thread comments and information from OP6 article https://wiki.postmarketos.org/wiki/Troubleshooting:GPS It would be nice if somebody, who knows the status of GPS on other devices, takes a look and corrects any mistakes. I'm in particular unsure if I described state of SUPL well, based on the comments in the long thread above.
I also changed GPS in wiki article to green again.
By Grzegorz Sadowski on 2023-10-31T10:31:18
-
From my point of view, a requirement to flash Android 9 before flashing pmOS is not unreasonable as a workaround. The question is, do we want somebody to take time to debug this further, assuming such requirement has no downsides for the other system components.
In my opinion it's not a high priority, so I did not create an issue for it - but surely it is a bug.
By Grzegorz Sadowski on 2023-11-01T20:39:01
-
I know only what OP6's wiki article states:
The bootloader is the only firmware that postmarketOS doesn't install itself, all other firmware (devicetree, gpu, modem etc) is supplied by postmarketOS. In contrast to custom Android ROMs, it is incredibly unlikely that any bugs or issues you encounter are caused by whatever OS you previously had installed on the device.Of course, the GPS case proves this is not always true.
By Grzegorz Sadowski on 2023-11-02T09:52:39
-
all firmware is provided by the distro (e.g postmarketOS). however the modem has a bunch of configuration data which it can write to from Android but which we make read only in pmOS.
It could be that some weird data here results in issues for Linux
By Caleb Connolly on 2024-02-17T17:45:48
Edited by Ghost User
-
Mobile Data: On the surface it works, but if pmOS is dual/alternatively boot with android, somehow some modem internal config/something gets corrupted and mobile data stops working for that particular sim in pmOS (calls,sms will still work. also, in android mobile data will work. only when using pmOS/ModemManager it wouldnt). Temporary suggestion is to not boot android and pmOS with the same sim and try a different sim if mobile data doesnt work. :( Yet to find the root cause. I have a hunch that it could be related to: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/660
Yes, the same thing on sm7150. But I accidentally discovered that it is also possible to use different versions of firmware on android and pmos. This fixes bug in my case. I hope this will somehow help in fixing this issue
By Danila Tikhonov on 2023-11-13T20:16:58
-
Regarding Poco F1 mobile data, this comment is from one of the users in the matrix channel
If you install UT, stock, any android 9 and 10, as well as ppui 11 before PMOS, the Internet works. If you install other versions 11,12,13 android or Los - there is no Internet
I bought a Poco F1 for the purpose of installing PostmarketOS. Before installing PostmarketOS, Android versions were updated to the latest version with latest firmware would be there. TWRP was finally used to fully install PostmarketOS with no Android system.
Despite following directions in the wiki, mobile data have never worked using this PostmarketOS Poco F1 setup. The sim card does provide mobile data when paired with a pinephone and did provide mobile data to the Android system used by the phone before PostmarketOS was installed over it.
By chris on 2024-01-24T22:16:32
Edited by Ghost User -
By chris on 2024-01-24T23:31:06
