Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 23 hrs, 15 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 18 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 3 hrs ago - more...
| The Following 4 Users Say Thank You to Fellfrosch For This Useful Post: | ||
 |
|
2018-09-05
, 09:32
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#2742
|
Originally Posted by Fellfrosch
Maybe you knew what they were on about. I had no problems with the Linuxy stuff, but the Androidy stuff was like Chinese to me.
It's been a while, that I installed Sailfish X.
But beeing just a average Linux user, I had no problems Installing Sailfish X following exactly the instructions.
Originally Posted by Fellfrosch
No patches. I only just installed Patchmanager but have not set it up yet. Uninstalling it made no difference.
All patches disabled?
How much space left on internal memory?
Just to be curious:
What happens if you touch the reboot text?
The "Reboot" text starts off white but once I tap on it, it turns cyan and the whole thing freezes.
Never mind, I restarted again - about the fifth time already, each time unistalling something to see if it makes a difference - and now I have reset the device and am setting it up again. No big loss, there was nothing on it.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
Last edited by pichlo; 2018-09-05 at 09:43.
| The Following 6 Users Say Thank You to pichlo For This Useful Post: | ||
 |
|
2018-09-05
, 09:42
|
|
Posts: 1,092 |
Thanked: 4,995 times |
Joined on Dec 2009
@ beautiful cave
|
#2743
|
Never owned an Android phone. But of course used sometimes the phones of my friends. Maybe i just had luck to read instructions in the right way...
For your update problems: If you have had all patches disabled and enough space on internal memory, and it still doesn't work, try update manually:
For your update problems: If you have had all patches disabled and enough space on internal memory, and it still doesn't work, try update manually:
Code:
# ssu release 2.2.1.18 # version --dup
| The Following 5 Users Say Thank You to Fellfrosch For This Useful Post: | ||
|
|
2018-09-05
, 10:45
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#2744
|
Originally Posted by pichlo
Yaay, success!
...and now I have reset the device and am setting it up again.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
| The Following 5 Users Say Thank You to pichlo For This Useful Post: | ||
|
|
2018-09-05
, 10:55
|
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#2745
|
The difficulty of Sailfish X installation really depends on if you want to backup the TA partition (so that you can return the device to original state, for example for easier warranty repair) or not. Without the backup step (which entail at least one firmware flashing and then 3 hours of updates or two firmware flashings) the installation process is easy, you just:
0. pay for license, download the image, download the kernel binaries
1. make sure the Android firmware is new enough
2. unlock the bootloader (this is kinda annoying, but I understand the security implications of why it is it done that way)
3. run the Jolla provided flashing script
And that's it, isn't it ?
As for additional optional but useful steps:
a) resize rootfs so your updates will not fail in the future due to the by-default laughably small rootfs overfilling
b) install Google play services in case some of the Android apps you use require them
c) install warehouse to get access to OpenRepos apps
d) install modRana & OSM Scout server from OpenRepos ;-)
0. pay for license, download the image, download the kernel binaries
1. make sure the Android firmware is new enough
2. unlock the bootloader (this is kinda annoying, but I understand the security implications of why it is it done that way)
3. run the Jolla provided flashing script
And that's it, isn't it ?
As for additional optional but useful steps:
a) resize rootfs so your updates will not fail in the future due to the by-default laughably small rootfs overfilling
b) install Google play services in case some of the Android apps you use require them
c) install warehouse to get access to OpenRepos apps
d) install modRana & OSM Scout server from OpenRepos ;-)
__________________
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)
| The Following 8 Users Say Thank You to MartinK For This Useful Post: | ||
|
|
2018-09-05
, 11:53
|
|
Posts: 1,092 |
Thanked: 4,995 times |
Joined on Dec 2009
@ beautiful cave
|
#2746
|
Originally Posted by MartinK
Martin is right. Probably that was the problem. I didn't make a backup of the TA partition. Because I definitely wanted the phone to run Sailfish and not Android.
The difficulty of Sailfish X installation really depends on if you want to backup the TA partition (so that you can return the device to original state, for example for easier warranty repair) or not. Without the backup step (which entail at least one firmware flashing and then 3 hours of updates or two firmware flashings) the installation process is easy, you just:
0. pay for license, download the image, download the kernel binaries
1. make sure the Android firmware is new enough
2. unlock the bootloader (this is kinda annoying, but I understand the security implications of why it is it done that way)
3. run the Jolla provided flashing script
And that's it, isn't it ?
As for additional optional but useful steps:
a) resize rootfs so your updates will not fail in the future due to the by-default laughably small rootfs overfilling
b) install Google play services in case some of the Android apps you use require them
c) install warehouse to get access to OpenRepos apps
d) install modRana & OSM Scout server from OpenRepos ;-)
for the optional additional steps:
a) I solved this problem working with some symlinks from usr/share to home
b) I prefer a Google free system
c) a must have
d) look at c)
| The Following 7 Users Say Thank You to Fellfrosch For This Useful Post: | ||
|
|
2018-09-05
, 12:20
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#2747
|
I did not make a backup of anything. I don't even know what a "TA partition" is. Never heard that term in my life. Just like about 80% of the things mentioned in the installation instructions.
Look, I also went though this a while ago and don't remember all the details, but I do remember it took me a good part of a whole day to complete it. There were many outdated links and other things I had to look up for myself, because they were not sufficiently explained.
Some examples: the instructions mention you have to download Emma, whereas in reality no such thing was necessary since the flashing tool was included in the downloaded zip. it was never explained what a "fastboot driver" is and why do I need one. As it turned out, following the instructions and installing it was a grave mistake as the process worked much better without it. The instructions for getting the unlock keys mentioned I had to give Sony my details but none of that happened, making me waste time trying again because I was assuming I did it wrong. It was never explained what "vendor binary images" are and why do I need them. The fact that you will get an outdated version was mentioned only at the end and only as a "by the way".
But first and foremost of all, the instructions are badly structured. I would have written them as a list of steps with a short explanation what it is and why is it needed. Then, and only then, would I go into details of each step. The way the instructions are written makes even reading them a pain. It looks like it was written by someone who wanted to jot them down quickly before he forgets, rather than by someone who knows how to write user manuals.
Anyway. You say it was easy for you. That either makes you a genius or me an idiot. I can live with both
Look, I also went though this a while ago and don't remember all the details, but I do remember it took me a good part of a whole day to complete it. There were many outdated links and other things I had to look up for myself, because they were not sufficiently explained.
Some examples: the instructions mention you have to download Emma, whereas in reality no such thing was necessary since the flashing tool was included in the downloaded zip. it was never explained what a "fastboot driver" is and why do I need one. As it turned out, following the instructions and installing it was a grave mistake as the process worked much better without it. The instructions for getting the unlock keys mentioned I had to give Sony my details but none of that happened, making me waste time trying again because I was assuming I did it wrong. It was never explained what "vendor binary images" are and why do I need them. The fact that you will get an outdated version was mentioned only at the end and only as a "by the way".
But first and foremost of all, the instructions are badly structured. I would have written them as a list of steps with a short explanation what it is and why is it needed. Then, and only then, would I go into details of each step. The way the instructions are written makes even reading them a pain. It looks like it was written by someone who wanted to jot them down quickly before he forgets, rather than by someone who knows how to write user manuals.
Anyway. You say it was easy for you. That either makes you a genius or me an idiot. I can live with both
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
| The Following 5 Users Say Thank You to pichlo For This Useful Post: | ||
|
|
2018-09-05
, 13:07
|
|
Posts: 1,092 |
Thanked: 4,995 times |
Joined on Dec 2009
@ beautiful cave
|
#2748
|
Originally Posted by pichlo
I am quite far away from a genius and you (as far as I know you from this forum) from an idiot.
Anyway. You say it was easy for you. That either makes you a genius or me an idiot. I can live with both
Which installation guide did you use? I used that one:
https://jolla.com/sailfishx-linux-instructions/
and I presume that you used a different one.
All links work in that guide and emma was marked as Option2:
If your device has its bootloader unlocked BEFORE updating to the latest version of Android, you need to follow OPTION 2 of section 1 in Windows instructions first to update your device using Sony’s flashing tool Emma.
Last edited by Fellfrosch; 2018-09-05 at 13:22.
|
|
2018-09-05
, 14:34
|
|
Posts: 6,447 |
Thanked: 20,981 times |
Joined on Sep 2012
@ UK
|
#2749
|
Thanks, Fellfrosch, that's very nice of you
I followed the Windows instructions here: https://jolla.com/sailfishx-windows-instructions/
In retrospect, I think my biggest problem was that I prefer to know what I am doing, which was not always the case here. The instructions are not written in a consistent style, they are a weird mix of "expert" and "trained monkey" level. A trained monkey does not need to understand, just follow steps. An expert does not need explanations because (s)he knows it all. I was lost somewhere in between
For example, I still do not know "vendor binary images" are and why do I need them. I mean, I am replacing a vendor's binary image (Android) with my own (Sailfish), am I not? So why on earth do I need this? But I guess I do not really need to know that. It's just a black box that I need for some reason. I could do the whole thing again in no time at all if I had to.
I followed the Windows instructions here: https://jolla.com/sailfishx-windows-instructions/
In retrospect, I think my biggest problem was that I prefer to know what I am doing, which was not always the case here. The instructions are not written in a consistent style, they are a weird mix of "expert" and "trained monkey" level. A trained monkey does not need to understand, just follow steps. An expert does not need explanations because (s)he knows it all. I was lost somewhere in between
For example, I still do not know "vendor binary images" are and why do I need them. I mean, I am replacing a vendor's binary image (Android) with my own (Sailfish), am I not? So why on earth do I need this? But I guess I do not really need to know that. It's just a black box that I need for some reason. I could do the whole thing again in no time at all if I had to.
__________________
Русский военный корабль, иди нахуй!
Русский военный корабль, иди нахуй!
|
|
2018-09-05
, 15:55
|
|
Posts: 1,092 |
Thanked: 4,995 times |
Joined on Dec 2009
@ beautiful cave
|
#2750
|
Originally Posted by pichlo
Well at that point I can just guess that flashing the image you still need the image of sony because there are parts in it, which are needed to flash a third party image. But that should explain someone else, I can just guess there.
For example, I still do not know "vendor binary images" are and why do I need them. I mean, I am replacing a vendor's binary image (Android) with my own (Sailfish), am I not? So why on earth do I need this? But I guess I do not really need to know that. It's just a black box that I need for some reason. I could do the whole thing again in no time at all if I had to.
To be honest at that part I just behaved the trained monkey way
. As I told you I'm just an average Linux user and maybe more the idiot than you because at some points I don't even try to understand, because I'm to lazy. So maybe that helped me with the instructions.Which saved me at least a lot of time.
 |
| Tags |
| sailfish os, sony xperia x |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 23:55.
How much space left on internal memory?
Just to be curious:
What happens if you touch the reboot text?