https://developer.android...cs/connectivity/wifi-scanYou can use the Wi-Fi scanning capabilities provided by the WifiManager API to get a list of Wi-Fi access points that are visible from the device.
Dat kan met een korte omweg zonder user permission.
https://developer.android...cs/connectivity/wifi-scanA successful call to WifiManager.getScanResults() requires any one of the following permissions:
ACCESS_FINE_LOCATION
ACCESS_COARSE_LOCATION
CHANGE_WIFI_STATE
If the calling app does not have any of these permissions, the call fails with a SecurityException.
Alternatively, on devices running Android 8.0 (API level 26) and higher, you can use the CompanionDeviceManager to perform a scan of nearby companion devices on behalf of your app without requiring the location permission. For more on this option, see Companion device pairing.
En CompanionDeviceManager draait in de achtergrond zonder dat de gebruik een app gebruikt
Apps can passively listen to all scan completions on device by using the broadcast without issuing a scan of their own.
Wanneer je zo bijvoorbeeld om de X Aantal minuten de omringende B/Essid’s en signaal sterkte van al je gebruikers verzameld kan je bij een andere Google dienst buiten de telefoon van de gebruiker om constant de exacte locaties van gebruiker /mensen via een web api volgen/uitlezen/kopen
https://developers.google...tion/geolocation/overviewThe Geolocation API returns a location and accuracy radius based on information about cell towers and WiFi nodes that the mobile client can detect. This document describes the protocol used to send this data to the server and to return a response to the client.
Communication is done over HTTPS using POST. Both request and response are formatted as JSON,
@
k995 ja, de te kopen gebruikers locaties zijn wel degelijk op basis van 5G masten beschikbaar.
https://developers.google...rview#calculating_cell_idRadio types prior to NR
(5G) use the 32-bit cellId field for passing the network cell ID to Geolocation API.
GSM (2G) networks use the 16-bit Cell ID (CID) as is. Valid range: 0–65535.
CDMA (2G) networks use the 16-bit Base Station ID (BID) as is. Valid range: 0–65535.
WCDMA (3G) networks use the UTRAN/GERAN Cell Identity (UC-ID), which is a 28-bit integer value concatenating the 12-bit Radio Network Controller Identifier (RNC-ID) and 16-bit Cell ID (CID).
Formula: rnc_id << 16 | cid.
Valid range: 0–268435455.
Note: Specifying only the 16-bit Cell ID value in WCDMA networks will result in incorrect or zero results.
LTE (4G) networks use the E-UTRAN Cell Identity (ECI), which is a 28-bit integer value concatenating the 20-bit E-UTRAN Node B Identifier (eNBId) and the 8-bit Cell ID (CID).
Formula: enb_id << 8 | cid.
Valid range: 0–268435455.
Note: Specifying only the 8-bit Cell ID value in LTE networks will result in incorrect or zero results.
Hier leggen ze uit hoe locatie vestreking zit ingebakken in Android in combinatie met de play store
https://youtu.be/4LPDsPvCbCo &
https://www.journaldev.co...tion-google-play-servicesNeed for introducing Google Play Location Services
The Google Location Services API, part of Google Play Services, provides a more powerful, high-level framework that automates tasks such as location provider choice and power management. Furthermore, it provides new features such as user’s activity detection that wasn’t available in the Android Framework’s Location API. Currently, Google provides 5 user states which are In Vehicle, On Bicycle, On Foot, Still, and Tilting, which are good enough to detect user’s activity, and to provide right content according to user’s status.
Another feature it provides is Geofencing API that is used to notify a user entering or exiting a particular area.
The above advantages clearly indicate why Google Location Services API is Google’s recommended way of getting a user’s location. It provides the best accuracy based on our needs
Google verkoopt/verhandeld (ook in België) op deze manier wel degelijk exacte (5G)locatie gegevens van Android bezitters. Inclusief gedrag via de play-store api
https://developers.google...ocation/usage-and-billing
How the Geolocation API is billedSKU: Geolocation
A Geolocation SKU is charged for requests to the Geolocation API.
MONTHLY VOLUME RANGE
(Price per REQUEST)
0–100,000 100,001–500,000 500,000+
0.005 USD per each
(5.00 USD per 1000) 0.004 USD per each
(4.00 USD per 1000) Contact Sales for volume pricing
[Reactie gewijzigd door xbeam op 24 juli 2024 01:01]