nieldk | # 221 | 2017-05-30, 06:43 | Report

I suppose You 'could' try 2.1.1.12

Merienth | # 222 | 2017-05-30, 07:05 | Report

Besides the obvious choice of crying () on together.jolla, could anyone point out how to debug this?

velox | # 223 | 2017-05-30, 07:45 | Report

As I inherited an old mako (Nexus 4) this week:
Does anyone of you guys know how to upgrade it to Iijoki?
There's http://repo.merproject.org/obs/nemo:...shos_2.1.0.11/ – but when I simply change the release to 2.1.0.11 and urls to "devel" in the OTA-directions, it doesn't find jolla-hw-adaptation-hybris when doing version --dup.
I've used CM11-base as described in the wiki.
Pointers in the right direction would be very much appreciated.

rinigus | # 224 | 2017-05-30, 08:32 | Report

@velox, there is no 2.1.x release for mako yet, as far as I know. Without proper release, I wouldn't recommend updating via version --dup - many things can break.

You should probably ask for status on IRC and see if ballock can give you an update. I used to assist him with the port earlier, but don't have much time for it anymore due to other commitments. Haven't seen ballock active on IRC either, as much as I followed it from the logs.

mako port would probably need some new active porter(s) that could test/develop on it. So, if you have time and a wish to work on it, I would recommend to ask on corresponding IRC channel for help. The porters are amazing in helping out with the ports and would help you regardless of your level.

nieldk | # 225 | 2017-05-30, 08:42 | Report

If you look on https://wiki.merproject.org/wiki/Ada...ishOS_for_mako it should be possible to OTA to 2.1.0.11.

But I think the issue @velox is having, is due to trying to use 'devel' repository.

Try to OTA by simply doing this:

rinigus | # 226 | 2017-05-30, 09:48 | Report

Not really, the last release is gamma8, 2.0.5.6. The fact that you can run these commands and get something resembling 2.1.x is surely not encouraged. With each SFOS release, each ported device has to get itself properly ported. As far as I understand, some packages are provided only via device-specific repos. These packages will not be updated (since they don't exist yet, we have to compile them as a part of porting) if you run update before port is ready.

I would suggest to stick to 2.0.5.6 and ask on IRC about the status of the port.

velox | # 227 | 2017-05-30, 10:04 | Report

Thanks guys!

@nieldk I think my first try (resulting in not booting anything) was only changing the $RELEASE. Didn't mention that because I'm actually not really sure that's what I did – That was just playing around for a few minutes on a work break.

@rinigus I'm a bit pressed for time as well, lately, but it may be a good opportunity to learn something new. I'll at least look into the HADK stuff a bit and then see If I can get myself to use IRC again for the first time in 15 years

nieldk | # 228 | 2017-05-30, 10:54 | Report

Totally true, it is not recommended

kuba77 | # 229 | 2017-05-30, 10:59 | Report

I have unpublic test version of 2.1 for Nexus 4 from the porter but many things does not work (camera, telephone module etc.). But it is build 1,5 months old.

explit | # 230 | 2017-05-30, 11:24 | Report

Cool, thanks!