Permission Denial: Enable bluetooth requires com.mediatek.permission.CTA_ENABLE_BT
Also happens on the jelly-pro:
All permissions are given.
08-31 23:39:16.615 9242-9318/org.briarproject.briar.beta.debug E/ACRA: ACRA caught a SecurityException for org.briarproject.briar.beta.debug java.lang.SecurityException: Permission Denial: Enable bluetooth requires com.mediatek.permission.CTA_ENABLE_BT at android.os.Parcel.readException(Parcel.java:1683) at android.os.Parcel.readException(Parcel.java:1636) at android.bluetooth.IBluetoothManager$Stub$Proxy.enable(IBluetoothManager.java:302) at android.bluetooth.BluetoothAdapter.enable(BluetoothAdapter.java:930) at org.briarproject.briar.android.keyagreement.ShowQrCodeFragment$1.run(ShowQrCodeFragment.java:166) at android.os.Handler.handleCallback(Handler.java:836) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.loop(Looper.java:203) at org.briarproject.bramble.system.AndroidExecutorImpl$1.run(AndroidExecutorImpl.java:36) at java.lang.Thread.run(Thread.java:761)
You can prevent the crash by switching on Bluetooth.
changed the descriptionToggle commit list
Interestingly, @ligi's app didn't crash but got a permission request dialog.
Sorry, I don't understand - do you mean @ligi has another app that enables Bluetooth and doesn't crash, or Briar doesn't crash when it gets the above exception?
Could we fix this by asking for Bluetooth to be enabled rather than enabling it manually (#790)?
To clarify: when getting this issue the idea came up it might be a general problem with Bluetooth enabling/permissions on this device. The permission handling on this device looked a bit custom. So I installed one of my apps that also enables Bluetooth if it is disabled(https://github.com/ligi/VaporizerControl) - Interestingly this worked - more interestingly we kinda use the same code (that said it was already late in the meetup when this device showed up - so this should have a deeper look) Also the device was from moritz from https://www.torservers.net - if you need to verify if the bug is fixed it might be worth dropping him a mail.