maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   Sailfish 3.0.2 Oulanka (https://talk.maemo.org/showthread.php?t=100698)

pichlo 2019-03-18 20:12

Re: EA: Sailfih 3.0.2 Oulanka
 
Did they finally fix Exchange? (I guess I'll find out soon.)

OK, answering myself. No, they did not. I expected it to take a few days to find out, but it only took a few minutes. SFOS is getting worse more and more lagging behind with each update.

r0kk3rz 2019-03-19 08:47

Re: EA: Sailfih 3.0.2 Oulanka
 
For anyone wondering what this part is about

Quote:

Camera - Supported values of each device's camera parameters are now passed through to Qt, enabling more camera controls in apps. Thanks to Adam Pigg (piggz) for this contribution.
You can try it out with this application:
https://github.com/piggz/harbour-advanced-camera
https://build.merproject.org/package...dvanced-camera
https://openrepos.net/content/piggz/advanced-camera

Which exposes a lot of different scene modes and controls that the camera hardware may support but haven't been exposed by the middleware until now.

All you developers feel free to join in the fun and send a Pull Request

stickymick 2019-03-19 09:14

Re: EA: Sailfih 3.0.2 Oulanka
 
If you have WiFiKiller installed disable it before updating. Just to be on the safe side..

Updated Xperia X this morning. First attempt to update failed :eek:
On trying again I disabled WiFiKiller and it only downloaded a few bytes then went to update OK after that.

Just updating my J1 now. Getting "Not enough memory to apply update" errors on that. Haven't got many apps, images or videos on the device either. If it fails again I may try via terminal.
This has now got me thinking and asking myself 'Is Sailfish now getting a bit too big for the original Jolla 1 device or is it just a case of too much left over junk from previous installs, apps and temporary files clogging the system?" :confused:

DrYak 2019-03-19 10:18

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

Originally Posted by deutch1976 (Post 1555324)
Their main focus now is XA. Xperia X was left back and i don't see a bright future for this device :(

Sailfish X continue to be support for Xperia X (and even all the way back to Jolla 1).

Android compatibility layer currently will not get any love on the Xperia X in the near future for precise technical reasons that were explained.

But unlike Jolla one where it will never be possible, if they manage to get some spare resource and pay developers, they could technically develop a brand new abstraction layer for Sailfish X running above the Sony kernels and blobs for AOSP 8.1 (porting some of the work from XA2), and the Android abstraction layer could run inside that.

The problem is that developing that would cost some significant money to Jolla, so currently, they are concentrating efforts on what can earn them money back (developing for the device that sells SFX licenses nowadays).

So although no technical blocker, it's not going to happen soon.

Quote:

Originally Posted by stickymick (Post 1555356)
Just updating my J1 now. Getting "Not enough memory to apply update" errors on that. Haven't got many apps, images or videos on the device either. If it fails again I may try via terminal.
This has now got me thinking and asking myself 'Is Sailfish now getting a bit too big for the original Jolla 1 device or is it just a case of too much left over junk from previous installs, apps and temporary files clogging the system?" :confused:

Two advices :

- switch the profile for meta-data blocks from "dup" to "single" on flash media (as opposed to harddisk) it's useless anyway.
That's going to free some extra space on the tiny flash of the Jolla

- Due to bugs in syncing with Google, over time the contact SQLite data base can get absolutely ginormous (gigabytes range). You can purge the file from the partition (it will resync anyway) it will free room on the flash, and your RAM will be happy too.

Then do the balance (use "btrfs-balancer" to do it for you), some significant space will have been freed.
(Well, until contacts go bonkers again in a couple of months).

meloferz 2019-03-19 10:31

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

[vendor] fix sensors when fresh flashing with v17B binaries
So, I understand that with the new binaries sensors as proximity sensor will work right?

Enviado desde mi H3123 mediante Tapatalk

max_power 2019-03-19 11:28

Re: EA: Sailfih 3.0.2 Oulanka
 
Are there any information what the new Battery Savings Mode actually does when it kicks in?

PamNor 2019-03-19 14:15

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

Originally Posted by stickymick (Post 1555356)
If you have WiFiKiller installed disable it before updating. Just to be on the safe side..

Updated Xperia X this morning. First attempt to update failed :eek:
On trying again I disabled WiFiKiller and it only downloaded a few bytes then went to update OK after that.

Just updating my J1 now. Getting "Not enough memory to apply update" errors on that. Haven't got many apps, images or videos on the device either. If it fails again I may try via terminal.
This has now got me thinking and asking myself 'Is Sailfish now getting a bit too big for the original Jolla 1 device or is it just a case of too much left over junk from previous installs, apps and temporary files clogging the system?" :confused:

if You have RPNCALC or KODI installed? Uninstall them. They use a lot of space.

peterleinchen 2019-03-19 15:33

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

Originally Posted by stickymick (Post 1555356)
...
Just updating my J1 now. Getting "Not enough memory to apply update" errors on that. Haven't got many apps, images or videos on the device either. If it fails again I may try via terminal.
...

Do not do that.
It will likely end in a corrupt system state if the update does not find any more free space.
It is due to the bad approach of Jolla to give a small rootfs in favour of BIG user data. Just deinstall some huge applications and reinstall them after update.

These commands may help you to find data suckers:
Code:

#devel-su
rpm -qa --queryformat '%{SIZE}\t %{NAME}-%{version}\n' > /home/nemo/Documents/pkgs.txt

ssu lr > /home/nemo/Documents/repo-setup.txt

 
devel-su du -x -a / > /home/nemo/Documents/filelist.txt


wrm 2019-03-19 16:39

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

Originally Posted by gaelic (Post 1555339)
So the Xperia X is +- dead, either switch to a XA or leavw the ecosystem for good now :(

I vote for leaving. Xperia X wont get not just Android support update, but rest hardware related bugs also wont be fixed: camera, bluetooth, nfc and so on.

taixzo 2019-03-19 17:27

Re: EA: Sailfih 3.0.2 Oulanka
 
Quote:

Originally Posted by MartinK (Post 1555334)
From the detailed changelog:

Code:

python3-base

Updated : 3.4.3-1.1.4.jolla -- 3.7.2+git1-1.3.2.jolla

Now that's interesting! If I'm reading the changelog correctly it looks like Python 3 in Sailfish OS was just upgraded from 3.4.3 to 3.7.2 - that's quite a jump & very welcome. :)

This also makes Sailfish OS pretty cutting edge Python wise, as even latest Fedora 29 also has Python 3.7.2 at the moment.

Lets hope library and runtime updates like this become the norm rather than an exception in the future. :)

This is a bit worrying to me, as I'm currently developing an app that has a Python module that's compiled binary code - do I need to create multiple packages with dependencies on different Python versions? (The compiled code is version-specific.)


All times are GMT. The time now is 18:32.

vBulletin® Version 3.8.8