Ask / Submit

[hotfix] Opt-in hotfix for connectivity in upcoming update 7 [not relevant]

asked 2014-06-09 16:06:07 +0300

Aard gravatar image

updated 2015-07-25 21:31:16 +0300

eric gravatar image

Update: we just released this to subscribers. (12.6., 14:20 EEST)

We've been working for a while on updating connman to a newer version (from 1.15 to 1.23). It will fix connectivity issues in some environments - but comes at a regression risk in some networks where the old one worked fine.

We used all the different networks available to us to identify and fix issues - but there's a lot more interesting network hardware out there, so we decided not to include it in update7, but make it available for community members as opt-in hotfix, which will be published the same week as the update, hoping that the new stack gets the toughest and widest audience for testing.

If you want to test the new connectivity stack please send an email with arbitrary content to, making sure the From-Address used is the one matching your Jolla account. After processing your email (which may take a while) you should get an update notification and be able to install the hotfix like any regular update.

Please add new issues as answers to this post or for already known issues add a comment to the answer describing your issue. If you want to go back to the old connectivity stack just send an email to, after a while you'll get an update notification which will bring you back to the main update.

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by chemist
close date 2014-09-21 17:48:02.092477


This is cool, but wouldn't it be cooler by following/unfollowing here or via store?

harry ( 2014-06-09 16:21:12 +0300 )edit

I think this is the appropriate way - if it was too easy to opt-in, inexperienced users might try it and break something.

nodevel ( 2014-06-09 16:24:13 +0300 )edit

would be better if one could hotswap between the versions, so i could test both in places that i dont visit all too often and have baf reception like my summer home in the middle of nowhere.

Whippler ( 2014-06-09 16:27:44 +0300 )edit

Does this version support WPA2-PSK/AES (and others) networks or do we need to install the patched wpa_supplicant again?

Alex ( 2014-06-09 16:34:29 +0300 )edit

To be clear, this only affects wifi and bluetooth? Not the normal GSM/LTE reception?

BonoNL ( 2014-06-09 16:37:44 +0300 )edit

@Alex WPA2-PSK/AES has always been supported.

tigeli ( 2014-06-09 16:43:36 +0300 )edit

@harry the update system is mostly disconnected from the store, so technically not possible

@Whippler logically it's two different releases, so not really possible. We've been thinking about offering as separate repository, but this way is easier for users, and does not add a liability for us for future updates

@BonoNL this covers connman + support packages, so enabling/tearing down cellular data connections are covered as well. It's not related to voice.

Aard ( 2014-06-09 16:55:14 +0300 )edit

Connman 1.24 (bugfix release) was released a couple of days ago, will you first let users test 1.23 for a while before updating to 1.24, or will you update to 1.24 asap?

nthn ( 2014-06-09 17:01:01 +0300 )edit

any chance seeing EAP-SIM activated ? it seems to be available within connman / wpa_supplicant but not enabled in Sailfish. see

pedro ( 2014-06-09 17:09:10 +0300 )edit

Does the hotfix corrects this? ->

ApB ( 2014-06-09 20:59:39 +0300 )edit

@nthn No plans as of yet to update to 1.24. I'd like to get this update out before integrating the next set of connman changes.

@ApB There are quite a few crash, memory and wifi plugin fixes in our 1.23 connman update.

llornkcor ( 2014-06-09 23:37:02 +0300 )edit

Would It be possible to downgrade after this hotfix? Or will it evolve upwards after "comments/feedback?"

JoneK ( 2014-06-10 02:19:58 +0300 )edit

You can downgrade by opting out as described above. And technically, you can then send another mail to opt-in again, and hence switch between the two releases.

sdjayna ( 2014-06-10 10:46:10 +0300 )edit

Does this support 802.11g with 802.1X authentication? Hopefully, this update will fix issues with pure-IPv6 networks (with NAT64 a few jumps away). Should we just leave feedback as "answers"?

WhyNotHugo ( 2014-06-10 10:50:33 +0300 )edit

I'd be interested if it supports WPA2/Enterprise by PEAP, which i also the only a little bit exotic setup i have available. If this is not covered by testing, yet.

Blizzz ( 2014-06-10 10:54:58 +0300 )edit

This does not include wpa2/enterprise support.

llornkcor ( 2014-06-10 10:57:15 +0300 )edit

This is AWESOME! Looking forward to seeing more opt-in opportunities to help you guys betatest new features!!

faenil ( 2014-06-10 11:35:28 +0300 )edit

@llornkcor So is it WPA2 Enterprise support removed from this hotfix or do you mean UI? I am currently running Saapunki update with WPA2 Enterprise network I configured via developer mode? I could otherwise opt-in in testing a new ConnMan version, but if it removes even the current weak WPA2 Enterprise support I really do not see the point.

Karri Huhtanen ( 2014-06-10 13:28:16 +0300 )edit

@nodevel Do you think that sending an email will stop anyone from testing the hotfix? Do you think it is wanted? @Aard Let's see whether you get enough testers. Maybe it is not worth spending additional effort. It just feels wrong to reply via a different channel

harry ( 2014-06-10 15:04:33 +0300 )edit

@harry the number of people who signed up so far looks encouraging. Additional reason why it makes sense to do it like this: We're interested in test results. So it makes sense to limit it to people who are active here on together anyway.

Aard ( 2014-06-10 17:57:40 +0300 )edit

I still havent get any notification

TMavica ( 2014-06-10 18:12:08 +0300 )edit

@TMavica You'll get the update notification once we release the hotfix, which will happen during this week.

Aard ( 2014-06-10 19:11:13 +0300 )edit

@Karri Huhtanen Same level of WPA2/Enterprise "support".

llornkcor ( 2014-06-11 06:02:12 +0300 )edit

@ApB We've patched quite a few connman crash fixes, which is one reason it hasn't been released in normal update channels yet.

llornkcor ( 2014-06-11 06:05:11 +0300 )edit

Any chance this will also bring bluetooth support for android apps? (to be exact, support for HeartRateMonitors for sports apps like runtastic) Or maybe some kind of API for BT that the MeeRun makers could use?

Ozymandias ( 2014-06-11 09:58:38 +0300 )edit

sshd don't start automatically after Maaninka update, does this help with that?

lasse ( 2014-06-11 21:48:37 +0300 )edit

installed this new update- all connections are up and running, so far all good

skrokhmal ( 2014-06-12 14:54:12 +0300 )edit

So I subscribed and installed the hot-fix thinking I will be able to connect to the wifi at work. Unfortunately it does not work. When I try to connect to this network my phone says that it is not able to connect to this network. The only information I got from our IT support is that it needs PEAP using MSCHAPV2 protocol. As far as I understand for now the only fix will be following this guideline? Can someone please verify this? I don't want to "patch" my system if it does not work either.

Eische ( 2014-06-12 15:05:25 +0300 )edit

That workaround works for me! Make sure you create the file with your login details as mentioned in the first post, and install the patched wpa_supplicant which is one of the answers. After that, reboot and it should work.

nthn ( 2014-06-12 15:15:42 +0300 )edit

i installed the update, also assuming that it would work for me (running WPA2 Enterprise network, that needs PEAP and MSCHAPV2)....after applying the old workaround it works again... Will try again after a factory reset after a phone (will use the downgrade phone temporary as second phone for testing purposes....)

BoertjE ( 2014-06-12 15:49:11 +0300 )edit

After installing, everything seems fine. @Neo I tryed and was successful in adding an event (to my Yahoo calendar, not local).

magullo ( 2014-06-12 16:49:51 +0300 )edit

Since installing the update I experience some connectivity problems.
When I came home today the Jolla does not connect to my home WLAN network. It seems it tried but was not successful (icon switched between WLAN and GSM).
After rebooting the Jolla it connects to the WLAN. However it also connects to GSM. I now have two IPs assigned. wlan0: 192.168.x.x, rmnet0: 10.176.x.x. I think this was not the case before the update. Actually the WLAN IP address is used for Internet connections.
I will further test in the following days and report back.

alex25 ( 2014-06-12 19:19:53 +0300 )edit

Trying the hotfix... So far, only a little trouble deciding whether to use wifi or 2G. Will post any issue.

dmelamet ( 2014-06-12 19:22:32 +0300 )edit

@BoertjE did you downgrade wpa_supplicant? As there is a newer version installed I was wondering if it has the revertpatch...

chemist ( 2014-06-12 20:16:38 +0300 )edit

It seems I haven't received a notification with the update yet, manually checking also doesn't help. Should I resend the mail?

nthn ( 2014-06-12 20:56:42 +0300 )edit

In fact, when I use the warehouse app to check for updates, it shows the hotfix, but for some reason I didn't get a notification. Should I wait until I get one?

nthn ( 2014-06-12 21:38:42 +0300 )edit

Ok. Now I have installed both this hot-fix and the patched wpa_supplicant. My phone still connects to my home wifi. switching from home wifi to GSM never worked flawless. When I leave home I have to unlock the phone to get connected to mobile data network (otherwise mitakuuluu keeps saying "waiting for connection") I asked a colleague to pull out the wifi setting (content of wpa_supplicant.conf) on his android phone for our wifi at work. I will then put it into my config file and hope to get connected to it.

Eische ( 2014-06-12 21:50:49 +0300 )edit

Just got my update - everything works as it was in WPA2 environment, still not working with WPA2 enterprise

TopStreamsNet ( 2014-06-12 22:32:53 +0300 )edit

installed and yes, now sshd works like it should. So does everything else. Thank you. (I don't know what hit me, everybody knows Maaninka is not a lake!)

lasse ( 2014-06-12 23:10:03 +0300 )edit

trying now... how odd tough, all your issues seems like the issues i had with 1 true 3.... And the gms to wlan switch has never worket proper with my phone... <- switched from answer to comment :/

JoneK ( 2014-06-12 23:41:04 +0300 )edit

Same happens again. The device did not switch to office wifi. I had to temporally disable gsm connectivity first. Now the device is again connected to wifi and gsm network. Am I the only one with problems? Should I try to go back to the latest stable version to verify everything works ok then?

alex25 ( 2014-06-13 09:55:03 +0300 )edit

wpa_supplicant needs to be downpatched for eduroam (it got updated but seriously, why update if you do not apply patches that are actually there for month...) for networks, I have IPv4+IPv6 on a Cisco AP (AIR-LAP1131AG-E-K9 on a NetworkWlanController with FW, AProaming seems to work too.

chemist ( 2014-06-13 11:28:19 +0300 )edit

I just (manually) updated to this update and eduroam works fine for me, without having to downgrade wpa_supplicant.

nthn ( 2014-06-13 13:15:09 +0300 )edit

@nthn no RADIUS? Just did some more testing before I sent it to care@... IPv6 is working unreliable, first I had v6 on eduroam, switching to company internal network no v6 anymore (university network, eduroam and company network share everything but the SSID...) swapping back to eduroam no v6, tried that for a while and had the admins at the uni look from the other side but nothing to see there, turning off wlan at all and turning it on again and tada v6 on company network - now my device is on its way to finland, if you want me to test anything in specific, end of next week I guess

chemist ( 2014-06-13 14:53:09 +0300 )edit

@chemist Yes, IPv6 connectivity is faulty, which is a real pain for me, since I only have access to either WPA-802.1X or pure-IPv6 networks. I've shared my finding (for Jolla mora than for other users) as an answer below, feel free to contribute anything else you may have to add - I don't think these comments let us follow up feedback on eath subject well enough :)

WhyNotHugo ( 2014-06-14 00:27:26 +0300 )edit

I think wpa_supplicant used with jolla misses this commit:

It doesn't work with Ziggo's Wifispots: wpa_supplicant log

My first impression of is that WiFi is more reliable, for know i keep it.

richhanz ( 2014-06-14 12:57:37 +0300 )edit

How long does it take to procede the mail? I'm waiting for over one and a half day :D

drummer12 ( 2014-06-14 15:42:37 +0300 )edit

@drummer12: not that long, are you sure you sent an email from the email account that is associated with your jolla account? Double check at

@drummer12 - just saw a mail come in for you this minute, you should be offered the update very soon, sooner if you restart your phone.

sdjayna ( 2014-06-14 15:44:55 +0300 )edit

thanks a lot, got the notification! I resend the mail, added some content and don't leaving all blank ;)

drummer12 ( 2014-06-14 15:51:54 +0300 )edit

@richhanz We have that patch included in our git now (

tigeli ( 2014-06-14 17:38:58 +0300 )edit

@tigeli Great! Is it going to be used in ;-)

richhanz ( 2014-06-14 21:35:21 +0300 )edit

I just sent a mail to opt-out from the update. I want to check if the problems I mentioned earlier also happens with the stock 1.0.7 firmware.

alex25 ( 2014-06-15 17:28:56 +0300 )edit

I have still not received the update to get back the old connectivity stack. What else (expect writing a mail to can I do to force it? The new stack works totally unreliable on my device.

alex25 ( 2014-06-16 17:11:50 +0300 )edit

@alex25 Thanks for pointing that out, if you check for updates now you should have more success, failing that restart the phone and open store: you'll be offered the downgrade!

sdjayna ( 2014-06-16 17:31:48 +0300 )edit

23 Answers

Sort by » oldest newest most voted

answered 2014-06-14 07:11:49 +0300

My main issue so far was missing usability in Public WiFi Hotspots (unencrypted WiFi, DHCP, captive portal) as in most cases Jolla just simply did not connect on layer 1 (WiFi)

Now having installed hotfix I at least managed to associate, received an IP, got the landing page and could log in.

After several hours I got this weird behaviour:

  • working in an App suddenly the "select Internet connection" UI popped up showing list of available WiFi networks (never had this before that being within an App suddenly the WiFi UI popped up)
  • closing this UI and going into my list of known WiFi networks it showed the Hotspot WiFi in status "being disconnected" (a status I've never seen before)
  • sliding down to the "select Internet connection" UI I found the Hotspot WiFi and clicked to connect
  • for some 10 minutes I had this UI in status "connecting" and in the list of known WiFi networks I had the same SSID in status "being disconnected"
  • then out of a sudden the whole config UI's seemed to restart as if some reset routine had stepped in and Jolla connected to the Hotspot WiFi just fine
edit flag offensive delete publish link more


known issues with hotspot usage. We'll get to these when we can.

llornkcor ( 2014-06-16 22:44:27 +0300 )edit

answered 2014-06-15 10:45:20 +0300

miska gravatar image

Have some troubles - while connected to wifi, mobile internet is not disabled and actually I have default route set through mobile data and no default route for wifi. And the idnicator icon keeps switching between wifi and data. But can't reproduce it reliably although happend on multiple networks (home, McDonalds). Sometimes I end up with the correct state, sometimes with this error.

edit flag offensive delete publish link more



This happens because the mobile data connection does not get forcible disconnected when connecting to WLAN. Applications that keep open sockets and do not disconnect and reconnect when the default route changes will still use the old interface. The icon will alternate between WLAN and mobile data only when data is being transmitted over the mobile data link.

Toggle the mobile data enabled switch off then on again to force the mobile data connection to disconnect.

Aaron McCarthy ( 2014-06-16 04:58:01 +0300 )edit

good point about the socket. It might be a good idea to requestDisconnect at that point. Although I might be worried we miss some use cases where user would want mobile data connection as well (gps/location?), but I cannot think of any. connman currently has no way to migrate the sockets as in IEEE 802.21 MiH and would probably be too big for us to implement.

llornkcor ( 2014-06-16 22:36:54 +0300 )edit

Just tested this. Sometimes connman does the correct thing changing the default route, even with an open socket on mobile data. It can even keep playing/streaming!

llornkcor ( 2014-06-17 00:00:55 +0300 )edit

answered 2014-06-17 11:27:45 +0300

Maddis gravatar image

Still current: SMS-receiving-issue

edit flag offensive delete publish link more

Question tools



Asked: 2014-06-09 16:06:07 +0300

Seen: 9,520 times

Last updated: Sep 21 '14