Yes, I know. There are some plans now after one user found the way how to use BT in AAS.
Isn’t it good thing that Jolla is implementing the long waited function? Isn’t it great that community findings will improve the life of the users?
Sorry for the delay @unmaintained , I followed rdomschk steps with shell-exec and it simply .. worked. I suppose if you run the commands from command line or do two shell scripts it will also work. Some other steps I did also, disable bluetooth on the sailfish, stop android support (I think the script does that anyway) . One more step I did, I downloaded “Pulsar” app from f-droid and I run it. I found out that Gadget-bridge doesn’t start automatically android bluetooth, - doesn’t even ask. Pulsar has this option, don’t remember if it brings a popup or has a menu / button for that. After I enabled the bluetooth from that app, it worked for Gadget-Bridge too! Also I tried Hrm app from f-droid, I was intrested for apps to read the hrm strap. There might be other apps too, or maybe somewhere some android settings that you can activate the android bluetooth AFTER the commands of rdomschk . I hope I helped a liitle bit, let me know if something still doesn’t work for you.
Some additional info about the upcoming Bluetooth support in AAS, straight from Jolla’s mouth:
- It’ll work simultaneously with native Bluetooth support, so no need to pick and choose.
- It’ll (initially) probably be available as a standalone package in the Jolla Store, so people who want to test can test, and if they experience severe issues they can just uninstall the package.
- It looks like Jolla will be able to use a very similar approach to support NFC in Android apps, but realistic use cases are very limited: NFC payment in Android apps is basically locked behind Google and banks’ proprietary code, and most other use cases can ‘simply’ get a native app.
Well that sounds really good!
How does this depend on Google, especially when a Bank has its own app and doesn’t use Google Pay?
(Sorry if this might be a dumb question… Or does this references to probably existing security features tied to Google Play Service?)
I don’t think Curve (NFC payments) has any dependency on Google, except for its notifications (handled fine by microG).
That is a good question. My bank has its own app, with rudimentary Wero support (no merchant payments yet) so it’d be great to be able to pay for things with my SFOS device without using US payment handlers when that gets added. I wouldn’t mind scanning a barcode for that though.
I think realistically we’d need to have some sort of integration with the hardware secure element for NFC payments of any kind to be supported (same as with most of the Android apps that ask you to ‘set a lock code’ - from what I’ve seen they want to store some credentials securely behind that). That’s a big job, but we are thinking about how we might be able to do that. Not Soon™ though.
I need to look into Curve!
Depends on the bank/application in question, but yes, they may require Google’s security features (ie. a locked device).
My bank has its own app, with rudimentary Wero support (no merchant payments yet)
Wero for merchants just started this year as far as I know (at least it was reported that way in Germany). Don’t know if Wero is capable to use NFC at all right now - my bank offers it, but I had no need and chance to try it out.
3 posts were merged into an existing topic: Fingerprint support in Android
I wrote a script to switch bluetooth back and forth, and now i got TapKey (needed to lock/unlock the office doors) working with bluetooth
I may have celebrated too early: even though i’m 100% sure it worked before, it doesn’t anymore, TapKey complains bluetooth isn’t on, and turning it on in the android settings “succeeds”, but if you go back, it’s still turned off. no idea why this stopped working, i got it once, maybe i forgot a step somewhere?
I have this problem, how did you solve it? even after a reboot, it doesn’t work anymore.
trying to enable bt in the android settings, appears to succeed, but going out and back in, it’s not enabled.
I didn’t solve it, and haven’t needed it enough to continue tinkering.
Will just wait for the upcoming official AAS BT app for now.
thanks for the reply… it’s so weird, i had it working and now it doesn’t work anymore ;_; . i hope i don’t need the tapkey app for work, i’ll have to make sure i’m not the first, nor the last
Hey, where can i find this Tesla app? how can i download it?
Android Tesla-app from aurora store.
is aurora store where to get the android apps trustworthy then? is this aurora in the harbour?
Yes, you can find the Aurora store from the Jolla store.