Open mar-v-in opened 8 months ago
At https://positon.xyz/docs/getting-started/ the URL is
https://api.positon.xyz/v1/geolocate?key=[API-key]
Has it changed or do both URLs work?
The first URL there is just the documentation. The second URL is the one you actually add to the microG settings. (In location settings, at the upper right tap the 3 dots)
Tap "Configure service URL" and paste the URL in there.
Just keep in mind that these services are in very early days and their database is not comprehensive yet.
If it gives you bad results, just disable it and use GPS until it improves.
You can also submit data to the beacondb service, eg for your neighborhood and other places you travel.
Don't forget to enable the "Remember from GPS" feature - this will automatically create a local location db in places where you get a good GPS signal.
At https://positon.xyz/docs/getting-started/ the URL is
https://api.positon.xyz/v1/geolocate?key=[API-key]
Has it changed or do both URLs work?The first URL there is just the documentation. The second URL is the one you actually add to the microG settings. (In location settings, at the upper right tap the 3 dots)
If you look at my post you see that the URL mentioned at positon.xyz is different from the one that mar-v-in posted. My question war about that difference.
At https://positon.xyz/docs/getting-started/ the URL is
https://api.positon.xyz/v1/geolocate?key=[API-key]
Has it changed or do both URLs work?The first URL there is just the documentation. The second URL is the one you actually add to the microG settings. (In location settings, at the upper right tap the 3 dots)
If you look at my post you see that the URL mentioned at positon.xyz is different from the one that mar-v-in posted. My question war about that difference.
I made a mistake and updated my post, sorry about that.
@EchedelleLR note that data submission is already possible for BeaconDB using NeoStumbler or Tower Collector. Not sure whether it would fit within microG's scope to feature submission itself.
The problem is battery. If microG is already getting data in local, could be better to use that having already microG.
NeoStumbler cannot be put in automatic mode with microG devices, or at least I did not see possibility to enable because the API related to detect the movement seems not supported.
A few hours in background takes 25% of battery.
At https://positon.xyz/docs/getting-started/ the URL is
https://api.positon.xyz/v1/geolocate?key=[API-key]
Has it changed or do both URLs work?The first URL there is just the documentation. The second URL is the one you actually add to the microG settings. (In location settings, at the upper right tap the 3 dots)
If you look at my post you see that the URL mentioned at positon.xyz is different from the one that mar-v-in posted. My question war about that difference.
I don't know what is up with this platform but it seems to keep dropping my comment edits.
What I was trying to say is that the original URL Marvin posted is correct. The one you posted that ends in "[API Key]" is just a generic template example. Without the full expanded key added (as in Marvin's posted URL), it won't work.
At https://positon.xyz/docs/getting-started/ the URL is
https://api.positon.xyz/v1/geolocate?key=[API-key]
Has it changed or do both URLs work?The first URL there is just the documentation. The second URL is the one you actually add to the microG settings. (In location settings, at the upper right tap the 3 dots)
If you look at my post you see that the URL mentioned at positon.xyz is different from the one that mar-v-in posted. My question war about that difference.
Just by trying, either in microg or your browser, you would have had your answer already. It appear the API url has changed, with v1/geolocate
added, and the one to use at the moment is https://api.positon.xyz/v1/geolocate?key=74600654-2aec-11ef-aa95-3b7218da6865
@EchedelleLR note that data submission is already possible for BeaconDB using NeoStumbler or Tower Collector. Not sure whether it would fit within microG's scope to feature submission itself.
Instructions to submit data: https://beacondb.net/
Just by trying, either in microg or your browser, you would have had your answer already. It appear the API url has changed, with
v1/geolocate
added, and the one to use at the moment is https://api.positon.xyz/v1/geolocate?key=74600654-2aec-11ef-aa95-3b7218da6865
This is a reminder (after it was also brought up in #2478) that, what I originally wrote remains correct, the URL you have to configure in microG to use Positon is https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865
. This is because microG already adds the /v1/geolocate
automatically during the request. If you configure to https://example.com/v1/geolocate?[...]
, microG will send the actual request to https://example.com/v1/geolocate/v1/geolocate?[...]
, which is not what you want here.
And for those that want to use BeaconDB, the URL you need to configure is https://beacondb.net/
.
As mentioned in #2478, in the next version of microG I'll add the feature to automatically remove /v1/geolocate
if it was wrongly added by the user.
Can anything be done for huawei users?
Can anything be done for huawei users?
Huawei users with -hw build don't need to do anything as they never used Mozilla. microG does not act as network location provider on -hw build because Huawei devices with original OS already have their own network location provider.
Can anything be done for huawei users?
Huawei users with -hw build don't need to do anything as they never used Mozilla. microG does not act as network location provider on -hw build because Huawei devices with original OS already have their own network location provider.
Ah so there is nothing us -hw users can do for issues like #2490 ? :( Will the non -hw version work on HarmonyOS ?
That issue (and this issue for that matter) are not in any way relevant to you. You are not using the location provider feature from µG.
Maybe add Mylnikov GEO and radiocells.org to the wifi location service and make microg automatically contribute to it should slowly solve this? The important thing is that the location service should be free, on both software and database, I don't know why grapheneos claim that a e/OS implementation would be proprietary, I doubt it, but if it's true we should avoid it.
As was announced at https://github.com/mozilla/ichnaea/issues/2065, Mozilla will retire MLS soon. The final deadline for third parties seems to be set to June 12.