Just to tease this out some more … Fused location is a thing in itself Fused Location Provider API | Google for Developers and I am keen to see just what sort of understatement (or irony) underlies the use of the word “Fused”.
Here is some Location info collected from my nicely working /e/OS a15 (heavily redacted in order to show my phone’s Location input sources)
adb shell dumpsys location
adb shell dumpsys location
Location Manager State:
User Info:
current users: u[0]
Location Settings:
Location Setting: true
Location Allow/Deny Packages:
Location Providers:
passive provider:
service: registered
listeners:
identity=1000/android[LocationService]
properties=ProviderProperties[powerUsage=Low, accuracy=Fine]
network provider:
identity=10103/com.google.android.gms
properties=ProviderProperties[powerUsage=Low, accuracy=Coarse]
target service=10103/com.google.android.gms/org.microg.gms.location.provider.NetworkLocationProviderService@2
fused provider:
service: ProviderRequest[@+1h0m0s0ms, WorkSource{1000 android}]
listeners:
1000/android[TwilightService]/01763C28 Request[@+1h0m0s0ms BALANCED, WorkSource{1000 android}]
identity=10103/com.google.android.gms
properties=ProviderProperties[powerUsage=Low, accuracy=Coarse]
target service=10103/com.google.android.gms/org.microg.gms.location.provider.FusedLocationProviderService@2
connected=true
gps provider:
properties=ProviderProperties[powerUsage=High, accuracy=Fine, requires=satellite, supports=[bearing,speed,altitude]]
Used-in-fix constellation types: GPS GLONASS GALILEO
Historical Aggregate Location Provider Data:
passive:
gps:
fused:
network:
What I aim to illustrate “Fused location is a thing in itself” (and may be used for instance in an app or system to the exclusion of other sources) shows in brief the final lines
Historical Aggregate Location Provider Data:
passive:
gps:
fused:
network: