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

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

Aard

13973 ●68 ●61 ●55

http://bwachter.lart.info...

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

eric

12967 ●88 ●133 ●123

https://twitter.com/erkki...

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 connman-hotfix@jolla.com, 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 connman-hotfix-opt-out@jolla.com, 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

Comments

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

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

8

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 +0200 )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 +0200 )edit

11

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 +0200 )edit

8

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

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

0

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

Manankanchu

9022 ●42 ●54 ●50

http://www.manankanchu.co...

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 1.0.7.18 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

Comments

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

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

0

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

miska

1028 ●20 ●28 ●28

http://michal.hrusecky.ne...

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

Comments

1

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 +0200 )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 +0200 )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 +0200 )edit

0

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

Maddis

176 ●7 ●11 ●19

Still current: SMS-receiving-issue

edit flag offensive delete publish link

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

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

Comments

23 Answers

Comments

Comments

Question tools

Stats

Related questions

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

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

Comments

23 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions

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