2.1.1/Jämsänjoki EA
 

New Early Access release has been made available!

release notes

changelog

Jämsänjoki update fixes dozens of bugs reported by our community, adds many improvements and new corporate features, like mobile device management (MDM), new Camera user interface with quick access from Lock Screen, smarter Calendar on Events, WPA2 Enterprise PEAP support, new VPN options (PPTP, L2TP), Bluez version 5 for Jolla C and much more.

Re: 2.1.1/Jämsänjoki EA
 

hm, they swapped to bluez5 on JollaC without audio support for bluetooth. Therefor this device is useless for me. Swapped to Jolla1 again.

Re: 2.1.1/Jämsänjoki EA
 

You have to remember this is Early Access release not final one.

You can try do downgrade your Jolla C

Re: 2.1.1/Jämsänjoki EA
 

I know but at all EAs this stuff was nearly implemented as in the consumer release - just heavy bugs were corrected by now. So I guess all aqua fish users (or at least EAs on JollaC) will not have audio via bluetooth with the release.

Re: 2.1.1/Jämsänjoki EA
 

Hahaha, now after several years they lower themselves to impletment wpa enterprise. rofl.

Re: 2.1.1/Jämsänjoki EA
 

As for all Early Access Release i would only update or even recomend it to someone who as a second Jolla phone. According to https://together.jolla.com/questions/ members there are a lot of complaints. Have to wait and see

Re: 2.1.1/Jämsänjoki EA
 

"Now vendors can drop more easily things like Developer Mode, Sideloading, Store and Sailfish OS updates."

...

Re: 2.1.1/Jämsänjoki EA
 

I'm still rolling on the floor:

https://together.jolla.com/question/...ed-workaround/

"Bug" opened Dec 2013, so amazing three and a half years to implement a basic feature which already was working on my N9 with Meego.

Re: 2.1.1/Jämsänjoki EA
 

Cool, for the first time in a long time, I didn't get the "update failed to install" message. I wonder if I've finally gotten rid of all the packages causing conflicts.

Some thoughts: the camera shortcut is very useful, but it looks like it doesn't load the camera in the background, so every time after rebooting your phone or restarting the home screen, you'll have to wait several seconds before the camera will start. Not ideal for the intended use, namely taking quick snaps. And yes, finally we don't need to enter the command line anymore just to connect to enterprise Wi-Fi. The Notes cover is still awful, so I don't know what they could possibly mean by 'polished'.

Re: 2.1.1/Jämsänjoki EA
 

Unfortunately I think Sailfish will not succeed. Not, because it is a bad OS, but because the guys here are so negative. Instead of being happy, that there is a a long awaited feature finally available, there is just sarcasm and mockery.

If all the thousand other platforms have all the features you think that are standard nowadays, well than you can tell me, if there is native caldav support in Android meanwhile. The last time I've seen it, it wasn't there. Just available over third party apps. But of course that's not a standard.

If you want to have something other than Sailfish just choose the OS you like there are so many out there, and all are really great and have no downsides...

Don't get me wrong. I'm also often struggle on some Sailfish things. But for me there are no alternatives out there at the moment. Still hope that plasma mobile will develop, but i fear that will still take a while.

So I'm happy that there is a new update, bringing new features an hopefully also bugfixes.

Re: 2.1.1/Jämsänjoki EA
 

I know what you mean, instead of complaining I made that post as a how-to to show a manual way for people get the wifi access, which I believe is the main strength of a good community. Jolla won't be able to deliver everything we want but as a community we can work together to help each other to fill the gaps :)

Re: 2.1.1/Jämsänjoki EA
 

I updated my first Jolla which I got from Narinkkatori. Update failed until I finally removed browser history and some other stuff. Update installation took long time and when it booted, it did not request for locking code nor pin code. Double tap and swype to bring up lock screen. I can open the device with locking code, but none of the simple methods will make this to ask sim cards pin-code, hence no 2G/3G/4G connections. Also WLAN does not work either. So this Jolla is completely without normal networking. I will not update my other J1's before I get this resolved. Will report back.

Re: 2.1.1/Jämsänjoki EA
 

Few other observations: there is no such thing as landscape-mode except on applications which seem to turn the screen on their own initiative, not based on sensor. E.g. terminal is in portrait mode and anything I do does not bring out landscape mode. Many applications do not even start. E.g. camera tries to start but dies without error message,

I guess the update failed catastrophically for some reason. I guess I have to flash this device.

Re: 2.1.1/Jämsänjoki EA
 

I resorted to system reset. Went through the firmware updates starting from 1.0.0.5. Phone worked in 2.1. but installing Jämsänjoki resulted with same problems. No mobile (apparently does not recognize sim card present) nor is there Wlan. So next I do the same but leave Jämsänjoki out.

Re: 2.1.1/Jämsänjoki EA
 

I can confirm, that the device lock is gone, it's only there after a reboot for once. But I have no problems with mobile connections. Also Terminal is switching to landscape just like it should (Have you set UI-Orientation inside Terminal-app).

Re: 2.1.1/Jämsänjoki EA
 

Of course. It is the fault of the user and their sarcarsm that Jolla is not successful.
Surly it is not the missing features like connecting to a wifi withouth having to activate developermode and edit some files in the terminal. That's what the vast majority of users want and do.

Re: 2.1.1/Jämsänjoki EA
 

Hm, ok, just need to calm down and explain myself.

Of course I know what I do (EA since the flag exists). Swapping to the J1 means: back to stable - yes this is my stable backup every EA user should have. You might see, that my post at tjc is not as negative as it might be interpreted here on tmo - and - I was too fast yesterday.

The developers kicked out the bluetooth 8bit mono audio profile. Quote "Routing low quality audio (8 kHz mono) to Bluetooth headsets not meaningful". What I did not know was that some of my bt headset devices just use this ugly codec (ugly because it is not meaningful - the devs say, ugly because of it's sound quality). But with these devices (Jabra suite) I have my special use cases - and they do not work anymore.

It may be a basis of discussion if "not as meaningful" functionalities really need to be deleted or not. And this might or might not be a thread on tmo to discuss. And if the developers have arguments for kicking it out then I would accept it - and dump my devices...

I only saw (or better heard): no audio anymore via bluetooth. Bummer. And I did this ooold mistake: just type it into the next thread compared to the update. And therefore I want to apologise especially if just this post has this negative connotation nobody really needs for this OS.

And hey - nice camera UI now.

Re: 2.1.1/Jämsänjoki EA
 

I have to correct this. After the update my lock time was set to 60 min. After setting it back all is fine ...:o

Re: 2.1.1/Jämsänjoki EA
 

Well you want a hackable device don't you ;)

And yes, I also want a lot of things. Anyway I have to use what I get. The choices are

• Android which is packed with add- and spyware.
• IOS, a walled garden
• Sailfish OS, a nice but unfortunately not yet finished alternative.

I have chosen Sailfish and live with the downsides. If I would have chosen one of the others, I would have to live with their downsides.

And of course I have the choice every day anew. I'm not forced to use Sailfish.

By the way, i have already written, that Android doesn't offer anything which i think is standard (guess why), but there are third party apps which help them out.
...Oh and on IOS please open the Terminal (isn't that standard?).

And of course you could have written an application which build up the network instead of using terminal. Being active is always better than complaining.

Re: 2.1.1/Jämsänjoki EA
 

You were talking about why Jolla is not successful. Now you're talking about some different things and fingerpoint on other platforms. That's always the lamest excuse off all: "but they are not perfect either".

Re: 2.1.1/Jämsänjoki EA
 

Guys, stop acting like Windows Phone community. :/

Re: 2.1.1/Jämsänjoki EA
 

I have the same problem with mobile connections and wifi. Seems relaterd to the other half. I have a The Other Half Keyboard. If i boot with TOHKBD attached the system comes up without mobile connections and wifi. If I boot without the other half attached to the backside of the phone everything boots as expected. Attaching the TOHKBD later on is no problem and it's working fine. Have to test the behviour with the original (white) other half later, as i don't have it with me now.

I had no time for more debuging but my speculation is that it may be a problem with the order of the kernel module loading.

Re: 2.1.1/Jämsänjoki EA
 

No fun, no jokes, no sarcasm allowed?

Re: 2.1.1/Jämsänjoki EA
 

J1 here, upgraded without any problem.
No patchmanager and no TOHKBD though.

Re: 2.1.1/Jämsänjoki EA
 

Doing it in one post is joking doing the same joke just 2 posts below is bitterness.
And doing so is probably doing more damage than it is helping in any way.

Edit: A lot of doings in this post :D

Re: 2.1.1/Jämsänjoki EA
 

Hello all. Got tip from tjc to try reboot without TOH installed. I have had TOHOLED on this device on most of the updates so far without notable problems.

In any case, I removed the TOH, rebooted the phone and it seems to be in working order now. Attached TOH and still works.

After this, reboot with TOHOLED installed again takes a looong time and after it finally starts, no mobile connection, no SIM pin-code request, no WLAN, no bluetooth. I say this is a bug. Somebody forgot that there can be devices on J1.

Re: 2.1.1/Jämsänjoki EA
 

Bitter is that WPA Enterprise is still not working through GUI. Tried with 2 different eduroam Account at 3 different University locations. Anyone else successful?

Re: 2.1.1/Jämsänjoki EA
 

I can't get my Jolla C into recovery mode. Do this guide not apply anymore?

Re: 2.1.1/Jämsänjoki EA
 

I think it's just the (third party, mind!) TOH software packages that need an update. I'm surprised something so minor could cause such trouble, but this is why EA exists.

Re: 2.1.1/Jämsänjoki EA
 

I will try as soon as I can find a way to free enough space on my Jolla C to do the update. But well, it may take weeks (usually I finally force myself to uninstall half my applications to free space when the next early update is around the corner :o).

Re: 2.1.1/Jämsänjoki EA
 

For eduroam at my university is working perfect. I can log in using username and password.
Are you share is possible to log in without certificates at your university?

Re: 2.1.1/Jämsänjoki EA
 

Good to hear. I just get a meaningless error: "connection failed". And I'm sure I do not need certificates as a manual configuration is working ....

Re: 2.1.1/Jämsänjoki EA
 

I thought the 2.1.1.23 was a minor update so there should not have been any breaking changes. That's my assumption. Naturally Jolla decides on update policies and should any breaking changes be reflected by updating also second version number. Hmm, I just checked my other Jolla and it is running Iijoki (2.1.0.11). I think the one I updated to Jämsänjoki was running the same. Maybe updating the third version number reflects e.g. kernel module load order change which might mean that 3rd party TOHs need an software update.

This was the first time I tried backup and restore, worked fine. There are some settings that were not recovered, like how often e-mail client should check for new posts, but otherwise seems to be ok. All the more important settings, accounts, calendar, contacts etc are fine.

Re: 2.1.1/Jämsänjoki EA
 

Hi from Italy :) here eduroam gui works properly. Note: first update failed, then i've reset my jolla1 and I've upgraded it up to 2.1.1 and then I've connected it to eduroam without problems (no certificates required by my university)

Re: 2.1.1/Jämsänjoki EA
 

Try using dedicated resource for Jolla C (using Volume-up button instead)https://jolla.zendesk.com/hc/en-us/a...-Recovery-Mode

Re: 2.1.1/Jämsänjoki EA
 

Thanks a lot! That's what I was looking for, but couldn't find.

Re: 2.1.1/Jämsänjoki EA
 

Made another attempt today. Working now :)
I'm not sure where the error was yesterday (i made sure the password was right), maybe the auth servers had a hickup.

So: slow but steady progress on Sailfish.

Re: 2.1.1/Jämsänjoki EA
 

Hi! Yesterday I tried to update my aquafish/Jolla C mode.
And it failed. And I bricked my phone. then I recovered it (volume up+power for recovery mode instead). I menaged to recover it. But no bt, no Wlan. then I updated manually mh phonr via data connection. Ig redtored everything. Then I updated to the latest release. it works,now!
Not so easy,guys.

Re: 2.1.1/Jämsänjoki EA
 

The update didn't go well for me. At the end of the process, I got a screen telling me that there was an error and the phone was not updated, and asking me to reboot. Now the Jolla C won't boot, it's stuck on the white Jolla and Sailfish logos on black screen and will stay there for hours.

Please note that the issue is probably related to my device and not to the update, I had been fiddling with the logical volumes sizes in recovery mode due to some problems before trying the update (but I thought I finally completely solved them when I decided to go forward with the update, everything seemed to be OK again). I don't mean to discourage people from updating as I have no clue whether this is just bad luck or a pre-existing problem on my end that did not go well with the update (and I suspect this).

I'll probably have to do a factory reset, unless someone has another idea?

Requiem_76, would you mind describing the steps you went through in recovery mode to solve your boot issue?

Re: 2.1.1/Jämsänjoki EA
 

Guys, if you have problems after the update (boot loops, black screens, etc.), please check in recovery mode, if the correct bluez packages are installed.

This update ships and enables bluez5, which caused the above mentioned problems on my Jolla C after the update. One part was updated to version 5, and one part was still on version 4.

After I fixed the installed packages to the correct version in recovery mode, my device booted correctly again.
I forgot to disable openrepos-repositories which may have messed up my update process...