Re: 2.1.4 EA / Lapuanjoki
 

Upgraded to 2.1.4.13 after the second attempt

Patchmanager not working. can somebody else confirm?

Thanks

Re: 2.1.4 EA / Lapuanjoki
 

upgraded also to 2.1.4.13 and patchmanager launched normaly

Re: 2.1.4 EA / Lapuanjoki
 

Removed all patches, removed ausmt and patchmanager, removed /var/lib/patchmanager...

As soon i install patchmanager and tap the icons in settings - patchmanager is closing just a second after opening....

Re: 2.1.4 EA / Lapuanjoki
 

what is your SFOS version described in "about" page in settings apps ?

Re: 2.1.4 EA / Lapuanjoki
 

2.1.4.13

Device Adaptation 0.0.1.8

Re: 2.1.4 EA / Lapuanjoki
 

Successfully updated from 2.1.3.7 to 2.1.4.13 on my XperiaX. Everything seems to work fine (including Patchmanager). Only warehouse which was removed during the update, but that was to be expected.

Edit: Successfully replaced it with storeman, v0.0.16-3 works like a charm.

Haven't found any issues yet, but the system somehow feels more responsive and fluent.

Re: 2.1.4 EA / Lapuanjoki
 

I cant seem to update , getting problem with store error, i had already updated to 2.1.4.12 last week but wishing not have done that, i think i need to reflash, anybody other suggestions?:o

Re: 2.1.4 EA / Lapuanjoki
 

Successfully updated from 2.1.3.7 to 2.1.4.13 on Oneplus 3T. So far: Jolla Together app is crashing on a regular basis when one starts scrolling.

Patchmanager works, new version of storeman too.

Re: 2.1.4 EA / Lapuanjoki
 

Do you still have the releases-internal.jolla.com repositories if you do a ssu lr (after devel-su)? I had the same problem, and finally solved it by replacing all occurances of "releases-internal.jolla.com" with "releases.jolla.com" in the file /usr/share/ssu/repos.ini (also as root).
After this the update worked as expected.

DISCLAIMER: You do this at your own risk, make a backup of the file before editing!

Re: 2.1.4 EA / Lapuanjoki
 

How to upgrade from 2.1.4.12 to 2.1.4.13? After 2.1.4.12 I changed the repos a suggested before. Now, system settings show "update" to 2.1.3, manual updateto 2.1.4.13 "works" somehow after deleting the manually added reps (jolla, hotfixes and apps), at least some packages were updated. But system settings still mentions, that update to 2.1.3 is available. Adding the previously added repos with 2.1.4.13 does not work. Any ideas?

Re: 2.1.4 EA / Lapuanjoki
 

Do not worry. It will automatically be fixed when hit the EA. ;)

Re: 2.1.4 EA / Lapuanjoki
 

I got back to 2.1.3 first after replacing the internals that seiichiro0185 suggested, then i manual update with terminal to the latest.

Re: 2.1.4 EA / Lapuanjoki
 

No problems after manually updating to 2.1.4.13. I think CPU managment is still not working as expected. The big cores get barely used. Minimum scaling frequency is still set to 691200 and core 3 seems to e exclusively used for the camera daemon. E-Mail is still slow for me.

Re: 2.1.4 EA / Lapuanjoki
 

memory killer is too often happen, so i made a swap memory, the problem is solved

Re: 2.1.4 EA / Lapuanjoki
 

No sure, if this is caused by the available RAM, as there are around 800 MB free on my device:
Nevertheless, adding swap is no big deal, and if it prevents unwanted closing of apps, let's do it. Below, I create a swapfile in /home which is the biggest partition available. Placing it directly in /home is somewhat unaesthetic, but we have to work with what's available. Putting it on the sdcard is a dumb idea because a) access speeds are way slower and b) it would wear the sdcard quite badly.

As always: DISCLAIMER: You're doing this on your own risk, I'm not responsible if something goes wrong. This reduces the available space for the user data by the amount of swap you are adding.

Please use the method provided by TMavica here as it does not requires parts of the user data partition: https://talk.maemo.org/showpost.php?...&postcount=111

below only for reference:
You can choose the size of the swap in the first comand (fallocate), either use M (for MB) or G (for GB). In my example, I create a 2 GB swap file.

Code:

---

# Create the swapfile
fallocate -l 2G /home/swapfile
# Set permissions
chmod 600 /home/swapfile
# Prepare file as swap
mkswap /home/swapfile
# Enable swap
swapon /home/swapfile

# Now, you can check that swap memory is available:
free -m

# Finally, add an entry to /etc/fstab so the swap gets enabled on boot
echo "/home/swapfile none swap defaults 0 0" >> /etc/fstab

---

If you want to remove the swap file any time (e.g. you need the space), delete the entry in /etc/fstab, disable it with

Code:

---

swapoff /home/swapfile

---

and delete the file.


Same for me. I'd suspect this is not a memory issue but maybe rather some incompatibility with the browser API!? It always crashes when you are in the middle of the loaded page (according to the scrollbar), so I'd suspect it tries to load more entries and fails.

Re: 2.1.4 EA / Lapuanjoki
 

BTW: 2.1.4 was official (re-)released. Release notes: https://together.jolla.com/question/...14-lapuanjoki/

Re: 2.1.4 EA / Lapuanjoki
 

Can anyone upload or post /usr/share/ssu/repos.ini for 2.1.4.13? I think, I broke it somehow while trying to solve the update 2.1.4.12-> 2.1.4.13...
Thank you!

Re: 2.1.4 EA / Lapuanjoki
 

Here you go: https://pastebin.com/ij7EEbe5

Re: 2.1.4 EA / Lapuanjoki
 

Thank you: hm. looks the same: I get an error:
Critical error: unable to determine update size
pkcon refresh gives
file '/repodate/repomd.xml' on medium 'https://releases.jolla.com/releases/2.1.4.13/jolla-apps/arm7hl

Re: 2.1.4 EA / Lapuanjoki
 

what is the output of your ssu lr command ?
here is mine :

Re: 2.1.4 EA / Lapuanjoki
 

It looks the same but in the global repositories I have:

Re: 2.1.4 EA / Lapuanjoki
 

Updated. It took bloody ages but that was kind of expected. So were some no-longer-working patches. Those should be just a matter of time.

What was not expected is that the phone still does not boot with TOHOLED on. I still have to take it off, boot up, and only put it back on once the UI has started.

Pity.

Re: 2.1.4 EA / Lapuanjoki
 

After reboot the additions sailfish-ca.pem and ssu-defaults.ini after the repo are gone, but still having same problem: repodata/repomd.xml not found / cannot determine size of the upgrade

Re: 2.1.4 EA / Lapuanjoki
 

Could you post the full line of the jolla repo output from ssu lr? Have you refreshed the repos?

Re: 2.1.4 EA / Lapuanjoki
 

How to fix 2.1.4.12 to 2.1.4.13

that is what it should look like:

Re: 2.1.4 EA / Lapuanjoki
 

Here is the complete output:
I used pkcon refresh but got

Re: 2.1.4 EA / Lapuanjoki
 

look at my answer about you. But you have to do something more.

first, clean your ssu:

ssu rr adaptation0
ssu rr adaptation1
ssu rr aliendalvik
ssu rr apps
ssu rr customer-jolla
ssu rr hotfixes
ssu rr jolla
ssu rr sailfish-eas
ssu rr xt9
ssu ur

and give your output again

Re: 2.1.4 EA / Lapuanjoki
 

Thank you CVP: this worked out: finally on 2.1.4.13...

Re: 2.1.4 EA / Lapuanjoki
 

For updating from 2.1.4.12 to 2.1.4.13 / fixing the repositories, the release notes state:

Re: 2.1.4 EA / Lapuanjoki
 

Another update installed, no issues here

Re: 2.1.4 EA / Lapuanjoki
 

I use that method

zramctl -s 1048576000 /dev/zram0
mkswap /dev/zram0
swapon /dev/zram0
swapon -s

Re: 2.1.4 EA / Lapuanjoki
 

Upgrading both Jolla 1 and X. So far nothing to report, camera on X still seems not precise, front one doesn't auto focus.
Still prefer Jolla 1 for small things.

Sent from my SM-N950F using Tapatalk

Re: 2.1.4 EA / Lapuanjoki
 

tested with swap memory enabled, if i open many app include android app, no OOM happened, if I disabled it, OOM happened and phone is slowed down。 With swap memory enabled, when open many apps, the phone still very smooth

Re: 2.1.4 EA / Lapuanjoki
 

Thanks for pointing out another option. I never used zram before, the way I understand it is that it extends the available memory by compressing all tables in /dev/zram0 and storing them in the RAM itself. This clearly has the advantage that it does not require any actual disk space (thus leaving the already small user space untouched). Regarding the performance, I can't say which is better (reading/writing to the slower disk or doing compression in RAM).

However, I actually noticed that my swap is rarely used. I had to run a lot of apps for it to actually start running out of memory and using the swap file (and even then it only used like 1 MB from the swap). This probably has to do with the swapiness settings (vm.swappiness is set to 30). I'd mostly suspect that there is actually enough memory available on the XperiaX, but the memory management seems to be slightly off, causing the OOM handling (= killing of apps) to be executed rather fast. Extending the memory with swap of course fixes this (as there is enough free memory available), even though the swap is rarely used. If this is the case, using zram would be the better option since it's mostly about providing additional memory to prevent OOM, even though it is rarely used.

Re: 2.1.4 EA / Lapuanjoki
 

At least my phone can run many apps without OOM occured, and smoothly

Re: 2.1.4 EA / Lapuanjoki
 

Copy in Sailfish-browser not work on sailfish x , sailors to confirm this?

Re: 2.1.4 EA / Lapuanjoki
 

works for me...

Re: 2.1.4 EA / Lapuanjoki
 

Thanks , seems not reliable.

Re: 2.1.4 EA / Lapuanjoki
 

On JP1 I used to set memory killer module at: adj 9999 and min free 1 (or vice versa), also wrote these values somewhere in init.rc, to save them in case of reboot. But now cant find these original values in init.rc file to modify them. Any ideas where they are hidden? Or gone?

Re: 2.1.4 EA / Lapuanjoki
 

wifi tethering is still disabled?