Here are the first few lines of the log... "0.002: Starting Subsurface-mobile:2.0(4.6.4.961):Android Marshmallow (6.0):arm:en-US" "0.002: build with Qt Version 5.9.1, runtime from Qt Version 5.9.1" localBtDevice isn't valid
Clearly we don't get access to the local Bluetooth device. Typical reasons for that are a) BT turned off b) the host is not connectable (I have never seen this) or c) the app has no access to Bluetooth. On standard Android, apps do not need to request special permission to access BT (we ask for location and storage access). I wonder if this is different in your flavor of Android? You mention "giving permission", so that makes me wonder if there's something different from what we normally see on Android and if we need to do something on the Subsurface-mobile side to set that up. Which phone do you have? /D > On Oct 10, 2017, at 8:50 AM, Florian Dworkowski, DM ASVZ <[email protected]> > wrote: > > Hi Dirk > > > Thanks for the fast reply. I attached the logfile. > > best, > > Florian > > ****************** > > Florian Dworkowski > PADI DM > [email protected] > ****************** > Am 10.10.2017 16:33, schrieb Dirk Hohndel: > >> >>> On Oct 10, 2017, at 4:43 AM, Florian Dworkowski, DM ASVZ >>> <[email protected] <mailto:[email protected]>> wrote: >>> >>> Hi >>> >>> I am not and never have been to use Bluetooth in the beta of SSmobile. I >>> always get the message that BlueTooth is not enabled, despite giving >>> permission and switching BT to on. >>> >>> Android 6.0.1 >>> >> >> Can you send us the subsurface.log file (it's in the root of your local >> storage device on Android)? This will hopefully shed some light on the >> problem... >> /D > <subsurface[1].log>
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
