decrep
Prominent Member
- Joined
- May 5, 2024
- Messages
- 977
- Solutions
- 1
- Reaction score
- 981
- Points
- 319
- Location
- Mandurah Western Australia
- Driving
- MG4
Good idea Ian
For Android, the method to get to the Digital key pages is different depending on the theme in use:It's odd that they wouldn't have removed the button entirely, if they disabled it.
If it was the circuit board in my opinion it would either work or it wouldn't. (I'm sure @Everest will correct me)
In the app info my permissions are location, nearby devices, notifications and phone.There doesn't seem to be anything useful I can do with that
In the app info my permissions are location, nearby devices, notifications and phone.
Nearby devices sound like a good one to try. I suppose phone may be also be required to provide some sort of device ID, but may only be necessary if you want to use the phone MG assistance feature in the app.
I've not done any android programming, but have a vague memory that there are hundreds of permissions the programmer can request. To make it manageable for the user to enable and disable, they are put in to just a few groups such as phone, location, contacts etc. The BT permissions are lumped in with location permissions I guess.For some nefarious reasons, Google require location to be enabled for BT to pair.
With regard to the boot button, I don't know if you realised it @Rolfe but it is an 'unlock and open' button. If you hold the button down the boot will unlock and open a little bit - you still have to heave the boot lid up. Just saves you pressing the boot handle button to open.
EDIT: The keyfob button works at a distance whereas the boot handle button needs the keyfob to be near as with the other door handle buttons.