search

OpenSeizureDetector / Android_Pebble_SD

The main OpenSeizureDetector Android App, that is published on the Android Play Store.
http://openseizuredetector.org.uk
GNU General Public License v3.0
9 stars 11 forks source link

V4.2.4 - Problems with Android 13 Go Edition (Moto E13) #166

Closed jones139 closed 2 months ago

jones139 commented 3 months ago

The OSD notifications do not display, and when you go into the system apps settings for OSD, it says "at your request, Android is blocking this app's notifications from appearing on this device". This is not useful.... I think it is because I have updated the target SDK to keep Play Store happy, so new Android 13 issues come to light that we were not seeing previously (https://source.android.com/docs/core/display/notification-perm) I have also had trouble with getting OSD to run on this new phone too - some permissions were not granted, but I'll do a clean install once this issue is fixed to see if it was just me pressing the wrong button.

jones139 commented 3 months ago

Confirmed that if we set the target sdk down to 32 (Android 12) then notifications appear ok.

There is another issue that permission BLUETOOTH_CONNECT is not granted, causing a crash.

jones139 commented 3 months ago

We had to explicitly request permission to display notifications, and ask for more bluetooth permissions.

I have put all of this in StartUpActivity to keep it in one place, and changed the workflow for switching to BLE data source so that StartUpActivity is called to get permissions before we try to scan to find the device. V4.2.6a built and uploaded into the #166 branch for testing on a few devices before I merge this.

jones139 commented 3 months ago

V4.2.6 needs a bit more work - it got into a complete tizz when I went out of range for 5 minutes and will not reconnect. The strange thing is that re-booting the watch and force stopping the OSD phone app have not got it working again either. I'll try V4.2.6 tonight with the Garmin VenuSQ and go back to PineTime tomorrow.

jones139 commented 2 months ago

Although getting the revised version started was tricky for some reason (I think I may have had an interference problem because I'm working on both Garmin and Pinetime watches at the same time, so had 3 watches, 2 phones and a laptop all very close together), once it go going it has worked without trouble for about 16 hours with the phone and watch about 3m apart. Will leave it over night and have a go at the start-up sequence tomorrow.

jones139 commented 2 months ago

It seems that the problems I was having were interference - it has worked very well since I stopped having too many watches next to each other. There is an issue with BLE Data Source not shutting down cleanly - will treat that as a separate issue.