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

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

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

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.

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

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

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

@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.

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?

any chance seeing EAP-SIM activated ? it seems to be available within connman / wpa_supplicant but not enabled in Sailfish. see https://together.jolla.com/question/1008/jolla-support-or-will-support-the-eap-sim-wlanwifi-authentification/

Does the hotfix corrects this? -> https://together.jolla.com/question/36927/bug-wifi-search-sometimes-does-nothing/

@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.

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

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.

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"?

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.

This does not include wpa2/enterprise support.

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

@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.

@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 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.

I still havent get any notification

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

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

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

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?

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

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

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.

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.

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....)

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

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.

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

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

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

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?

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.

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

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!)

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 :/

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?

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 7.6.120.0), AProaming seems to work too.