Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 14 hrs, 8 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 2 hrs ago - more...
| The Following User Says Thank You to llelectronics For This Useful Post: | ||
|
2015-08-26
, 05:16
|
|
Posts: 1,298 |
Thanked: 2,277 times |
Joined on May 2011
|
#172
|
I have nothing against Debian based distros (I use Debian testing + KDE on the desktop). In some aspects it's even better than Mer, because Mer is still stuck with some antiquated packages because of that GPLv3 avoidance.
|
|
2015-08-26
, 13:27
|
|
Posts: 108 |
Thanked: 417 times |
Joined on Oct 2013
|
#173
|
Originally Posted by Ken-Young
I don't think there are big advantages, other than your personal preferences. I recently tested both systems on my Nexus 4 and they both work very well at this point (no GPS yet on N4 with SFOS, but N5 should be fine according to https://wiki.merproject.org/wiki/Adaptations/libhybris).
I have Ubuntu Touch running on a Nexus 5, and it works pretty well. What would be the advantage to moving to SailfishOS? Has anyone tried both?
In my opinion there are more apps and customization options (3rd party) available for Sailfish OS (no Android support of course), the system offers more choices (accounts, settings) and generally feels more mature. There can be some UI scaling "unbeauties" on SFOS due to the high display resolution, but upcoming v2.0 should fix all that.
OTA system upgrades are not supported yet on Sailfish OS and might break stuff (like certain camera features), so a reinstall is recommended and can be annoying. Otherwise Sailfish OS is best supported on the Nexus 5 and was also used to show upgrade 2.0 at the MWC.
Sailfish OS runs very fast on my Nexus 4, while Ubuntu phone had some lags here and there (probably not the case on Nexus 5).
| The Following 3 Users Say Thank You to caprico For This Useful Post: | ||
 |
|
2015-08-26
, 21:25
|
|
Posts: 411 |
Thanked: 1,105 times |
Joined on Jan 2010
@ Europe
|
#174
|
Originally Posted by caprico
We are beta testing OTA methodology, see bug 852 , stay tuned!
OTA system upgrades are not supported yet on Sailfish OS and might break stuff (like certain camera features), so a reinstall is recommended and can be annoying. Otherwise Sailfish OS is best supported on the Nexus 5 and was also used to show upgrade 2.0 at the MWC.
|
|
2015-09-02
, 06:14
|
|
Posts: 411 |
Thanked: 1,105 times |
Joined on Jan 2010
@ Europe
|
#175
|
We need your help guys
1. Are you using Multirom? If so, what's your underlying primary rom (cm12 or cm11 or ..) and what kind of cm11 snapshot (M9 etc) are you using for flashing with which version of sailfishos
2. Do you encounter the above bug? Open fingerterm, type 'top' and watch out for sensor* processes. Rotate your N5 and back, lock and unlock the screen and check again.
Last edited by BluesLee; 2015-09-02 at 08:07.
Originally Posted by sledges on XDA
Can you post following information
We have investigated the dreaded battery drain: looks like those with MultiROM and Lollipop as primary (CM12/AOSP5) are experiencing sensorfwd and sensors.qcom consuming 10-12% of CPU and thus draining battery
Installations without MultiROM seem to be fine and actually increasing battery life each update since ~alpha11.
We need more confirmations of the above suspect, would be great if you could share your battery drain experience. Bug ref: https://bugs.nemomobile.org/show_bug.cgi?id=837
1. Are you using Multirom? If so, what's your underlying primary rom (cm12 or cm11 or ..) and what kind of cm11 snapshot (M9 etc) are you using for flashing with which version of sailfishos
2. Do you encounter the above bug? Open fingerterm, type 'top' and watch out for sensor* processes. Rotate your N5 and back, lock and unlock the screen and check again.
Last edited by BluesLee; 2015-09-02 at 08:07.
|
|
2015-09-02
, 06:57
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#176
|
Yes. But didn't know it works with CM12, last try I did (2 weeks ago), SFOS never starts with CM12. But didn't even know we can install SFOS without Android. How? Is there any tutorial somewhere?
1. Yes. CM11. Took a build from XDA.
2. Yes, sensors.qcom takes around 14% of the CPU and sensorfwd 12%.
1. Yes. CM11. Took a build from XDA.
2. Yes, sensors.qcom takes around 14% of the CPU and sensorfwd 12%.
| The Following User Says Thank You to romu For This Useful Post: | ||
|
|
2015-09-02
, 07:19
|
|
Posts: 411 |
Thanked: 1,105 times |
Joined on Jan 2010
@ Europe
|
#177
|
Originally Posted by romu
SFOS does not work if you flash it with CM12 (not yet) but you can use CM12 etc as a primary rom using Multirom and SFOS (with CM11 as a basis) as a secondary. Follow the instructions at the beginning of the installation instructions, see my initial post, for SFOS usage without Multirom.
Yes. But didn't know it works with CM12, last try I did (2 weeks ago), SFOS never starts with CM12. But didn't even know we can install SFOS without Android. How? Is there any tutorial somewhere?
1. Yes. CM11. Took a build from XDA.
2. Yes, sensors.qcom takes around 14% of the CPU and sensorfwd 12%.
|
|
2015-09-02
, 07:42
|
|
Posts: 602 |
Thanked: 735 times |
Joined on Mar 2011
@ Nantes, France
|
#178
|
Thanks. I remember I tried it and no luck, SFOS never started, so I switched to the MultiROM procedure and it works. Sorry, I just forgot.
| The Following User Says Thank You to romu For This Useful Post: | ||
|
|
2015-09-02
, 09:29
|
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#180
|
Originally Posted by shmerl
It is apparently because people from KDAB, that have more experience with Ubuntu Touch than with Mer, are helping with the effort.
By the way, do you know why Plasma Mobile isn't based on Mer anymore and instead is using Kubuntu as a base? Or it's just the prototype example? In the past Plasma Active was based on Mer.
This is in itself kinda funny, as even though they are basing they work on top of Ubuntu Touch, they are still kinda turning it back to Mer in places, like for example by using Wayland rather than Mir, which is used by the "normal" Ubuntu Touch images.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
I know that it is running on Arch also already though no image is available.
I guess Ubuntu as base was choosen as it seems easier for the developers. Also the automatic packaging infrastructure for arm builds is already there. And finally that prototype on which the current Image is based on was primary developed by people employed by Blue Systems which is also sponsoring Kubuntu amongst other Free Software and Open Source projects.
Also keep in mind way much software is available in armhf repos for Debian and Ubuntu which might be also a big reason why this will remain the main development base for most devs.
Donation for my sailfish apps via PayPal
Donate using Liberapay