-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixel Pro 6 Android 12 no longer connects to Dash #1069
Comments
did you try to activate dash with 2.8.2.17 or only continue session? |
Continue a session only. I will be changing pods today so can try to activate a new one? |
Yes you can like i say on discord chanel, update doesn't work but clean install and activate new pod work |
yes, permission is asked during pod activation |
Is this something you are going to try and fix for in session update? I can try to test it today before starting a new pod?? |
i don't have android 12 phone. Unable to test it |
Ok, I will switch pods today on .17 and activate and go from there. I wonder if subsequent dev updates will behave the same? Or is this something we think dev 17 only requires a new pod activation to grant permission then it will behave like before (in session dev updates will be ok??) |
Just a note, I remember when I start testing Android S (12 beta version) and xDrip didn't work at all with Dexcom but was able to work with MiaoMiao and Bubble, first try to fix was adding the permission request on xDrip NightscoutFoundation/xDrip#1734 but didn't work. The only solution that worked was this one NightscoutFoundation/xDrip#1723. This cannot be related at all to this issue but just to leave my experience with Android 12 at the beginning. |
Adding to this, Dev 18 is unable to be tested as it crashes on Pixel Pro 6. Both in place and fresh install crashes and must go back to Dev 14 and MUST reinstall fresh Dev 14 to get BT connection back. |
parapenT1sta i use xDrip with G6 on my Zenfone 8 to Android 12 and it work fine but i use last Nightly . |
Please let us know if Dev 18 works. It crashes for me on both in place and fresh install. I do not have a copy of Dev 17 so must stay on Dev 14 for everything to work. I hope @MilosKozak can either delay Dev 14 expiry (tomorrow) or help test new Dev 19 that works |
It seems most recent commits for Dev 18 has fixed this. not sure if each new version will prompt a new BT permission but it forced me to request that permission and then connected to Dash pod. Good to close this? |
FYI - I updated to dev 18 yesterday and it asked for additional permissions but the connections were totally fine to dash and I had no issues. Pixel 6 Pro - Android 12 - Dash - Dexcom BOYDA |
Update to dev 18 today built 35ded... work fine no additional request for me but I update 17 c21... Yes I think issue can be closed |
Starts at 16:53:48.880
BT connection permission issue.
AndroidAPS_LOG_1639432456805.log.zip
AndroidAPS 2.8.2.17-dev
Build: c21b4be-2021.12.13-13:54
Remote: https://github.com/nightscout/AndroidAPS.git
Flavor: fullrelease
Nightscout version: UNKNOWN
Engineering mode enabled
The text was updated successfully, but these errors were encountered: