Google's location
-
On one of my devices I get the repeated message asking to turn on Google's location service. I have the device's location service (gps) turned on which should be enough.
Blackview7000 Pro Android v 7.0
See video.......https://mega.nz/file/4TYWGZ5T#Ips-BmUGy9mBhoALACVGnqlZbg7XwWioIRrDSZMUadk
-
@Whinging-Biker Android 7? In that case I'm not surprised something like this happens and a more sophisticated service is requested
-
@Whinging-Biker said in Google's location:
Blackview7000 Pro
Oeh... that's an oldie I guess...
If you are not afraid of some tinkering, you could try to revive your blackview with LineageOS: https://tweakdroid.com/lineage/blackview-bv7000-pro/
(guarantee to the doorstep...but it beats throwing it away immediatly ) -
There's nothing wrong with my Blackview 'satnav'. It's only MRA that causes this.
-
@Whinging-Biker That can be but as this app is created in 2023 it might require never services than other apps
-
Is this being treated as a bug?
-
@Whinging-Biker, I think it is a difficult case. I looked up your device's specs and they seem to meet the minimal system requirements of the platform the App is built on. But there can potentially be a lot of other problems on a phone that old. It would be good to know if others experience the same problem on the same device. If your phone is not being used for other purposes, you can try to refresh the OS by a factory reset, or by flashing an original ROM. Bugs are only bugs when all other things are being deducted out
But personally I suspect having such a modern and sophisticated app running on your device is ultimately not going to make you happy.
-
I'm happy to try and refresh the OS by a factory reset. I only bought and use this phone as a satnav and it has no other problems so replacement is not imminent.
I'll get back to you. -
@Con-Hennekens I have the same, if I try to turn off Google location services I get repeated messages to turn it on and the app won't work without it.
Samsung S22+ latest version of Android. -
I'd suggest it's an 'oversight' rather than a bug, since many users may not want to run Google Services - mainly for privacy reasons, so the app shouldn't lock them out.
The app can easily work without 'Google Location Accuracy' (which is basically using WiFi and movement sensor input to aid in locating you), so it's wrong to block users.
The only downsides using GPS only would be:
- slow to locate the user initially
- potential problems locating in cities with tall buildings when satellites may not be in direct view
Those limitations can be shown in a popup warning the user of the consequences.
If it's useful to MRA, this is what you see as a user repeatedly, so you can't use the app. If you select 'No, thanks' the popup re-appears:
And this is the option that blocks the app, if you disable it (that's how it looks in Android 12, not Android 6). It's one of the Google-specific options within the location settings menu:
-
@richtea999 , I usually have these options OFF and it doesn't keep me from using the app or throw any errors. Google location services also incorporates the normal use of the GPS. You cannot shut that off, but you can shut off the "improvements" by wifi or Bluetooth.
There might be another problem. The app is android Auto compatible. I think there is no Android Auto compatibility in Android 7 yet. Therefore the minimum system requirements will most likely be set at Android 8.
-
@Con-Hennekens said in Google's location:
@richtea999 , I usually have these options OFF and it doesn't keep me from using the app or throw any errors. Google location services also incorporates the normal use of the GPS. You cannot shut that off, but you can shut off the "improvements" by wifi or Bluetooth.
There might be another problem. The app is android Auto compatible. I think there is no Android Auto compatibility in Android 7 yet. Therefore the minimum system requirements will most likely be set at Android 8.
https://developer.android.com/training/cars
"Note: Android Auto is only compatible with phones running Android 6.0 (API level 23) or higher."So MRA have got the minimum version correct at 6, which is below the 7.0 that Whinging Biker is running.
It blocks me on Android 12 too so something is not quite right, but it's not the Android / API level.
-
@richtea999, I don't understand what's blocking you. You can continue without the "better experience", you just can't stop location services. But location services runs just fine without the "improved location accuracy" (which does not improve anything if you ask me).
MRA has set nothing yet concerning the minimum system requirements, and I don't think it is up to us what they will support. Good find about AA though. That was just me guessing indeed.
-
I'll make sure this is investigated a bit more by us
-
@Con-Hennekens said in Google's location:
@richtea999, I don't understand what's blocking you. You can continue without the "better experience", you just can't stop location services.
For Corjan, whenever you come back round to investigating:
Video of the app being locked out by having 'Google Location Accuracy' off which shows:- repeated tapping of 'No, thanks' and it pops up again
- location is enabled when I pull down the Settings
But location services runs just fine without the "improved location accuracy" (which does not improve anything if you ask me).
It improves accuracy at the expense of privacy. That's why the option is there. Personally, Google knows far too much about me already , but others may want that option.
MRA has set nothing yet concerning the minimum system requirements, and I don't think it is up to us what they will support. Good find about AA though. That was just me guessing indeed.
They have to set a minimum supported OS level, quite generously at Android 6. That minimum determines which APIs (i.e. code libraries) are available when coding. In general the higher the minimum, the easier it is to code (better libraries, less chances for apps to crash, better support from Google & StackOverflow, improved security, etc), but with a small loss of potential users - around 2% of users in the case of Android 6.
-
@richtea999 said in Google's location:
Video of the app being locked out by having 'Google Location Accuracy' off
Ah, I see ...
@richtea999 said in Google's location:
It improves accuracy at the expense of privacy.
Actually I think it disturbs accuracy at the expense of privacy. What it does is help get a quicker fix if you move your phone over great distances being shut down (or location being shut off). Another thing that does the same is the IP of your internet connection, or the location of the cell-tower with which you connect. And if all is turned off, your privacy simply gets violated first chance of a working connection in retrospect. Honestly, if I wanted to avoid google knowing where I am I would surrender to the other big brother... (or by a garmin). All which does not make the bug okay of course...
@richtea999 said in Google's location:
They have to set a minimum supported OS level, quite generously at Android 6.
Why would they "Have to" do that?
-
@Con-Hennekens said in Google's location:
@richtea999 said in Google's location:
They have to set a minimum supported OS level, quite generously at Android 6.
Why would they "Have to" do that?
At risk of going waaayyyy off-thread if you want to make use any of Google's services (like the 'enhanced' location discussed) then you have to have at least Android 4.4.
For Android 6 there was a major change in the OS where permissions became opt-in. Before that, apps could just suck information about the device and user with aplomb. That's the usual reason why 6 might be a sensible minimum to build for.
Moving further up the OS versions, Google is well known for forcing app developers to support higher versions of OS. Note those are 'target' API levels not minimum, but as a developer you have to jump the hoops. They've been doing it since 2017, and it's a royal pain. However, I can also see why they do it. The main reasons are:
- to force apps to meet the best security. Older libraries will have holes.
- performance is generally better in the newer libraries
- to avoid Google's library authors from having to support ancient devices ('ancient' being say 5 years old)
-
@richtea999, That is great information and I can see you are knowledgeable about it. But I still think it is up to the developer what they write in their minimum system requirements, and what they want to actively support. People seem eager to use old unused phones to mount on their bikes, but that can hardly deliver a good first impression that way. It might be better to aim a bit higher.
-
@Corjan-Meijerink said in Google's location:
I'll make sure this is investigated a bit more by us
I see the app has now gone live with this issue. It doesn't work on any of my devices with Google Location Accuracy turned off. I cannot test or use the app.
video -
Is anyone working on this? I still cannot use the app and another release has gone by.