i mean, it would be wonderful if gym equipment manufacturers released native sailfish apps, but in the meantime, SFOS users can save their workouts, setup their air conditioners, and control their home water heaters without purchasing an additional android phone.
i currently have my old XA2 flashed with android again, just so i can add new devices to apps, and then control them with reverse engineered scripts. (rheem water heater, whisker litter robot, midea air conditioner, GE air conditioner, basically every smart appliance requires android or ios to initially add the device, even if you can reverse engineer the web client to control them after).
bluetooth support in android is necessary basically ONLY for closed source, walled garden device setup, like home automation, and there is no possibility for native SFOS apps for those anyway.
=> be of good cheer, this is a nail in the coffin of full android devices being required in addition to SFOS.
That’s actually an extremely important thing to keep in mind.
I would probably never have made my Roomba work with Sailfish if there was no way to initially set it up using an Android app which I haven’t opened ever since
Ditto! And ungainly. And the community efforts to make bluetooth available in the AAS lxc context have other valuable lessons involved and those will no doubt be even more useful techniques coming with the OS itself. In all, solving ‘odd’ problems can lead to insights in more mundane (ie. bluetooth in SFS without AAS) context.
Clearly, yet another time there’s not even a word regarding the 10 IV / V port. Which is really sad, considering that in 4 months we’ll be celebrating the 2nd anniversary of Jolla announcing it (at the Jolla Love Day 2 in May 2024) as coming in August 2024. This utter lack of communication is more than just disrespectful.
Dampffisch is another new app. It allows you to read the news from your Steam games. You can add steam games by their game id or from your recently played games if your Steam profile is public.
In the last community news there have been some progress noticed about the development for the 10iv and 10v - will them be included in this update or do we have to wait for a later update?
If them are included in this update it would be great if this devices get the update as an middle between cbeta- and ea-release. It would bring a few more early-testers for the development for the AAS-Update and we can see the progress about this adaption.
If you mean the person I was replying to, I don’t really blame them for wanting to raise this issue again. Communication hasn’t been great on Jolla’s part
I’m also interested in learning more about the development of the Xperia 10 IV / V port.
Just recently went with a used 10 V to try SFOS on, albeit it’s not a recommended platform compared to ageing 10 III.
My goal was to use this platform to make my mind up about SFOS as a main platform, and I’m open to spend on a J2 in the mid-term but not now.
Edit: Purchased Xperia license in hopes to make our voices heard, although it’s a small sum compared to full-blown HW purchase.
assuming you only have an Xperia 10V, the license you have purchased will not work on your device as they aren’t currently for sale until there is a mature adaptation. You could contact the helpdesk either now to request a refund, or later to request a transfer to an Xperia 10 V license should they complete an adaptation
Ah, so that’s why the trial mode is included as of 5.0.0.71 so AAS and other stuff is working there indefinitely while they work on mature adaptation.
I’ve checked the compatibility table during order process and assumed they’ll extend it once adaptation is completed.
I won’t ask for a refund as of now and just wait whether the transaction is carried over for XQ-DC54 / Xperia 10 V.
Even would get another license and support development of it, the only thing I hope for they either push forward or communicate it won’t happen (for any reason).
I have some Garmin devices and use IQ Store and Garmin Connect. I also have Bluetooth speakers that are not from Sonos. However, the main reason are my hearing aids. I cannot base my decision on who develops a native app. Every hearing aid is adapted differently to hearing problems. I already use the Community AAS solution and have had success with it. Garmin and hearing aids.
