It’s not 100% perfect yet, for example today my wife came home with the car and my phone wouldn’t connect - but at this point I don’t know if the issue is with the app or SFOS bluetooth in general.
Works good for me, I can see it connects to the car from the app preview (sorry if I’m not using the correct name).
What I also noticed is a spike in battery consumption, I haven’t installed anything else, but I would like to find a way to measure it, if possible
Look here for a monitoring guide:
BTW, the name you were looking for is ‘cover’ 
1 Like
Yeah, I noticed it too. It doesn’t absolutely slaughter the battery, but something needs to be done about it anyway… According to Grok it’s caused by keeping the radio open. I think we need some “preliminary” check whether the car is even remotely in range before turning the system on to prevent polling when it’s far away - the online api comes to mind first, we could ask it for the car’s coordinates and see if it’s within a kilometer or something and only then do the bluetooth stuff. Or save the location when the car was in range and compare to that. And then maybe do some lower frequency checks every now and then. The official app probably gets notifications about the car location and triggers stuff when it’s in vicinity…
I guess the problem with the api is that everyone needs their own api key for it and it has pretty tight limits on how much it can be used for free.
Anyway, now it’s reliable enough that I haven’t had to carry my backup phone at all anymore. Sometimes there’s some delay in detection, but that’s acceptable IMO, and maybe we can get rid of that as well while improving the battery consumption.
Oh yeah and regarding the cover - the buttons on there are completely useless at the moment. The cover only supports two native buttons, so those custom things I put there can’t take any touches etc. The way it needs to be done is that there’s one button to cycle through locks/trunk/frunk/ac/charging/whatever and the second one performs the command. That’s probably better anyway, since it allows many actions without making it cluttered. Also there could be a setting to select what’s shown there.
I’m testing using BlueZ signals instead of polling. It should be much more battery friendly, but let’s see if it works. I’ll post the rpm here once build completes.
Kia app (Kia EV3) works perfectly 
No widget tho
2 Likes
Just a quick test today with Peugeot.
- 2020 peugeot 508 SW with new Jolla phone
- The phone can be connected via bluetooth to the car. The phone did not reconnect automatically after restarting the car but did find/connect manually very easily (faster than the initial pairing)
- Calls could be made and received and the contacts from the phone could be used to make the calls.
- Using android Tidal I could play music to the car speakers but artist/track information was not seen and was named unknown. Tracks could not be changed via the scroll on the steering wheel.
- Connecting the phone with a USB cable to the car the infotainment system recognized possibility for Android auto but it did not actually work.
- Verified that ABC mobiili version 4.41.25 can be used for charging the hybrid car battery.
1 Like
Android Auto with MicroG worked for me in LineageOS with GitHub - sn-00-x/aa4mg: Android Auto 4 microG · GitHub. But I don’t see how it would work with AppSupport in Sailfish.
1 Like
@nappa85 and others who might be interested, check this out: Release v0.2.16 · Pauligrinder/ElectricEel · GitHub
It now listens for signals from Bluez instead of polling, which not only should be more efficient but also seems to work better. In particular, if you measure the battery consumption, please compare this and the polling version.
Oh and I also changed the cover as I described before.
2 Likes
But you tried just the app with status and remote commands, right? Not the smartphone key (if available in your KIA)?
@pauligrinder I really appreciate the work you put into dev of a native app. For the sake of overview, do you think it might be the right time to move your app into a dedicated topic and just link it from here?
1 Like
I’ve thought about it, yes. But let’s see how development will even proceed from here.
1 Like
The key only works with apple, some samsungs, pixels, some oppo, some oneplus and some motorola (They have a list of compatible phones). I knew it would not work. But the Kia has a good physical key. I don’t really want it.
2 Likes
Has any finn tried virta charging app with jolla phone? Has it worked at all? Just tried it for the 1st time and it crashes when selecting the charger for usage.
Does anyone use the Electroverse network?
I’ve created an app for personal use but wondered if someone may find it useful.
11 Likes
looks awsome! How did you make it?
Claude was kind enough to reverse-engineer their API
3 Likes
My take on EVs I tested with Jolla Phone:
(heads up: I only really use a bluetooth connection for playing audiobooks and music)
On Smart for Two:
- Connection works mostly flawlessly - sometimes it cant connect automatically. A reconnect (removing the device, adding a new one) is then nessesary
On Honda e:
- Bluetooth connection autoconnects flawlessly every time, covers update immidiatly and it feels more snappy than on other phones
- There is supposed to be android auto, but i dont see the need to enable it (doesnt it need google stuff? bah)
One thing that is annoying in general though is that audio gets choppy when turning off the rolling computer (the EV) in general. But that could also be a thing with music streamed via Angelfish browser as I dont remember it with UnPlayer. weird that it only happens with Angelfish and cars though xD
xD
ah I see. what services API did you use?
The one used by Electroverse map page: Electroverse Map | EV Charging Stations | Europe’s Largest Network
1 Like