Bluetooth Low Energy / Google Mesh

machinehead

I have read locked posts about this on here that imply Google Mesh is an opt in/out service linked to Google Play services. However, I am currently running a flavour of AOSP (Volla OS) on a Vollaphone which does not have Play Services enabled. The behaviour of the Bluetooth app on my device suggests that it does not require Play Service and that it is connecting to Google's mesh even when I have user-operated Bluetooth turned off. I'm attaching some screenshots (or at least I would attach them ... is there a way to upload images here?) that show the app has accessed contacts and nearby devices in the last 24 hours even though I think I have BT disabled. The BT app is a system app (com.android.bluetooth) and it cannot be disabled nor permissions edited. Obviously this is a huge concern for me, because even though I have location disabled, my location is easily retrieved by Google based on the proximity of other users' BLE beacons. I am a hair's breadth away from switching to Graphene OS but I need to know - is this standard AOSP behaviour that will therefore be identical in Graphene?!

machinehead

machinehead Linked to this issue is the issue of the Emergency Alerts app (com.android.cellbroadcastreciever.module) which comes bundled with AOSP. This app cannot be removed, deactivated nor its permissions altered or denied. The app also has permission to make use of nearby devices BLE beacons and the app overrides any Emergency Alert settings. Even if you turn them off in settings the app will just ignore it or turn them back on. Presumably it can or will also use Google's mesh to deliver the alerts to devices not connected to cellular or WiFi networks. Again, I assume this is stock AOSP behaviour and will be identical in Graphene OS?

monogram

machinehead Linked to this issue is the issue of the Emergency Alerts app (com.android.cellbroadcastreciever.module) which comes bundled with AOSP. This app cannot be removed, deactivated nor its permissions altered or denied.

This can be achieved via ADB, it's one of the first things I do when I set up new systems on my phones. I force-close and disable all three system packages related to Cell Broadcast. I know Developer Options and ADB and tinkering with preinstalled apps are all advised against over here, but I've been doing that for years and had no problems whatsoever. Plus, I just love being left alone by annoying and disruptive useless alerts.

machinehead

Other apps on the Volla O/S flavour of AOSP that grant themselves irrevocable permissions including access to location AND BLE beacons, include the settings app itself, talkback and FM radio. None of these can be removed. Is it possible to get a list of all the non-removable, unstoppable system apps that come with Graphene O/S and all the permissions required by those apps? Is "nearby devices" permissions anywhere on the dev team roadmap as a potential (probable?) privacy breach that needs to be overcome?

de0u

machinehead So far this thread seems to have a fairly high ratio of assumptions to data. For example, I am unaware of any evidence that the cellular Wireless Emergency Alerts system use Bluetooth mesh technology in any way. Is it possible to share evidence supporting this suspicion?

My understanding (albeit not verified by reading the source) is that the AOSP WEA app has some Bluetooth access so that it can present alerts differently depending on whether or not a Bluetooth headset is in use. Regardless, if you are interested in knowing what the GrapheneOS WEA app does, the source code is available. Also, the GrapheneOS project publishes build instructions for any individuals who might wish to experiment with removing standard apps.

This forum is not particularly well situated to comment/advise on Volla OS or the Vollaphone. I think there is a Volla user forum here: https://forum.volla.online

gta3

monogram could you list The full names of those 3 packages.

In the past when I disabled too much, the phone wouldn't start.

Thanks ahead

monogram

gta3
WARNING: please be careful (don't try this at home), things can break.
Their names can vary across devices, on my 6a they are:

· Wireless Emergency Alerts (com.android.cellbroadcastreceiver.module)
· com.android.cellbroadcastreceiver
· com.android.cellbroadcastreceiver.overlay.pixel
· com. android.cellbroadcastservice

When you disable-user them via ADB, you need to go back to Settings - Apps - Show all - Three dots/Show system - Search for "cell" and force-close all the listed packages.
But again, please be careful.

Note: if you use more than one user/profile, you have to repeat the process for each user/profile.