View Full Version : Sailfish OS on Sony Xperia X Compact (community build)
Steph Gosling's SailfishOS image for Xperia X Compact is out now (https://together.jolla.com/question/180109/announcement-community-sony-xperia-x-compact-release/).
Also g7 has created a patcher that transforms XperiaX image to be compatible with Xperia X Compact. OTA updates work with the patched image.
Patcher at Github:
https://github.com/g7/sailfishx-patcher-f5321
About the patcher on TJC:
https://together.jolla.com/question/185922/sailfish-os-on-sony-xperia-x-compact/
Cavalier
2018-02-27, 15:26
Gonna try image soon. Thanks!
Cavalier
2018-02-27, 21:36
Gyro/accelerometer and proximity sensors do not work too
Volume to low in the Flow ambience
Original link has now a new image and the sensors work. :)
I guess it would be nice to keep the important informations in the first message to avoid the mess the Official thread is now.
For example, how to update, what works, what doesn't, etc.
And for the story, I tried "version --dup" to update...and no luck, I had to reflash the phone.
EDIT: Some questions I have for the moment (take this message as post-it note):
why no twitter / facebook feeds & accounts Answered
how to keep SFOS updatedAnswered...almost
how to install mce-tools (double tap to wake the phone, etc) Answered
How to install mce-tools
devel-su
pkcon install mce-tools
mcetool --set-low-power-mode=enabled
mcetool -–set-doubletap-mode=show-unlock-screen
mcetool -i disabled
mcetool -z always
Notice you can also set:
mcetool -–set-doubletap-mode=unlock
...to unlock the phone with a double tap.
Works fine on my XC.
why no google / twitter / facebook feeds & accounts
devel-su
pkcon install jolla-settings-accounts jolla-settings-accounts-extensions jolla-settings-accounts-extensions-google jolla-settings-accounts-extensions-jolla jolla-settings-accounts-extensions-twitter jolla-settings-accounts-extensions-facebook
Thanks Romu. :)
Sorry I'm not too keen on keeping track of things in the first message. Most of the stuff in any other community thread usually applies to this port too, as well as actual SailfishX tricks, and reading and adding everything just leads to the first message becoming a badly formed wiki page. Plus probably running out of space eventually...
The threads will be always a mess, and I think that proper wiki would be better for this purpose. :)
No problem.
How to keep SFOS updated
This is where things get more complicated. This version of SFOS is specific to the X Compact, so every try of OTA update will corrupt the some phone in some way.
So, for updates, we've to wait for new images.
Alien Dalvik works on the XC. I've just bought Sailfish X to avoid problem, not sure if this will be enough though :rolleyes:
Cavalier
2018-03-01, 15:30
how to make font size in sailfish browser more bigger?
bertjefred
2018-03-01, 15:51
Alien Dalvik works on the XC. I've just bought Sailfish X to avoid problem, not sure if this will be enough though :rolleyes:
So what are the steps to achieve this Romu?
Thanks!
First you need to get the RPMs. And then install it.
Check TJC ;)
EDIT: But be fair OK. Buy a Sailfish X license.
You cannot blink an eye... 8|
pisarz1958
2018-03-01, 21:15
how to make font size in sailfish browser more bigger?
Go to about:config and change layout.css.devPixelsPerPx to a desired value. This setting is overwritten every time you open Sailfish Browser with defaults though.
bertjefred
2018-03-02, 05:38
First you need to get the RPMs. And then install it.
Check TJC ;)
EDIT: But be fair OK. Buy a Sailfish X license.
Yeah that was kinda the question. Can you obtain them by buying the license.?
in the past I've bought the Jolla1 and the tablet, which were both not good enough hardware-wise. So yeah I will always look for the fairest way to get the rpm's to get Sailfish and Alien running on decent hardware. After Jolla i switched to x compact, so I'm super stoked about the community build!
Yeah that was kinda the question. Can you obtain them by buying the license.?
At least the somewhat legal method I used requires that you have a physical Sailfish X phone, as that device is the only one that is accepted at Jolla Store.
There may be other methods I'm not sure of. For instance I don't know whether version in Jolla1 phone is compatible with Sailfish X Compact or not. (If it is you wouldn't have to buy X.)
Can you obtain them by buying the license.?
No.
I bought a license and thanks to some guys here, I've got the RPMs. But right now, I don't know how to manage updates for example.
Other problem is Sailfish X has OTA updates delivered by Jolla. The XC image doesn't.
Just the beginning of a long journey I guess.
bertjefred
2018-03-02, 09:35
Thanks guys,
That clears up a lot. I will start by just installing Sailfish on my x compact to check out the current Sailfish (X) status. It has been a while since I've been sailing.
And then decide if I 'll go for the semi offical route (get an official license and kindly ask for rpm's) and take the long journey with you.
Thanks for now!
Cavalier
2018-03-02, 09:41
Thanks guys,
That clears up a lot. I will start by just installing Sailfish on my x compact to check out the current Sailfish (X) status. It has been a while since I've been sailing.
And then decide if I 'll go for the semi offical route (get an official license and kindly ask for rpm's) and take the long journey with you.
Thanks for now!
dont forget to save Drm keys before unlocking bootloader
dont forget to save Drm keys before unlocking bootloader
Too late for me. Totally forgot that before unlocking.
bertjefred
2018-03-02, 10:14
dont forget to save Drm keys before unlocking bootloader
Thanks for the heads up, and yeah already downgraded this morning, so that is in progress.
The double tap to wake up the XC doesn't work so well. Maybe half of the time, once the phone is awake, the swipe to unlock doesn't work.
Still valid doubletap hint, since doubletap is bit slow both on X and X Compact:
mcetool --set-lockscreen-animation=disabled
makes it feel faster when you don't subconsciously wait for animation to finish until you can swipe.
Bluetooth is just not usable at all on the XC, at least for music. So much scratches that it hurts my ears. Same for others ?
For me music through bluetooth to Nokia wireless receiver with XC works as it did with X. Maybe one hiccup in five songs. Might to be related either to sleep modes or plain coverage. Also got one hiccup during writing this.
Automatic brightness does not seem to do much. When you enable it, it approximately halves the brightness, but it does not seem to react to changes in ambient lightning.
Brightness sensor is working according to csd test. I tried different settings with mcetool to no avail.
Anyone with different experiences?
Cavalier
2018-03-03, 16:19
I switched it off. Seems it doesn't work
Help me please.
I can't flash. I run "flash-on-windows" and I see after "Searching a device with vendor id '0x0fce'.." message "it was unexpected".
XC has after update droid_8 v.34.4.A.2.19 on board.
Since you are running Windows you should be able to download Sony's Emma firmware flasher tool and downgrade your X Compact to 34.3.A.0.252.
There was also one mention in original TJC announcement about Windows flashing script using old dll, and that caused problems too.
Cavalier
2018-03-03, 22:42
Sorry, I can't help you. I'm using Linux.
Извини, но помочь тебе не смогу. Я использую Линукс. Есть отличный гайд, правда на немецком. http://sailfishmods.de/2017/10/howto-sony-xperia-x-teil-2-sailfish-os-community-installieren/
Можно использовать google.translate
Почему выбирая такую систему Sailfish еще пользуешься виндовс?
@Manatus, @Cavalier. Many thanks for help! No problem with Linux. I flashed.
@Cavalier. Пользовался виндой в прошлом году для отката на дроид_6, бэкапа TA и прошивки Xperia_X. Проблем не было, я и решил проторенным путем...
P.S. Other problem. I see "Command failed: This tool coold not find any available package: could not find mce-tools." after attempt "pkcon install mce-tools"
Try to run 'pkcon refresh' or 'zyp ref' as root, and try installing mce-tools again.
Try to run 'pkcon refresh' or 'zyp ref' as root, and try installing mce-tools again.
@Manatus, thanks :-) It's OK after "pkcon refresh"
I've been able to play some music over BT without so many problems. Good, even if I don't know what changed.
But, the metadata about the track being played are not sent, and the battery status sent over BT seems all wrong. Same for you ?
bertjefred
2018-03-04, 10:34
I've got Sailfish installed on my X Compact now. And it's running fine. Have not checked all the options and connections yet. But big thanks or all the help do far guys!
Cavalier
2018-03-20, 06:48
Any news about new update?
Regarding bluetooth stutter, it seems to happen when wifi and bluetooth signals overlap. I use 2,4 GHz frequency for wifi and BT uses the same. Hiccups started immediately when I started using laptop today, after an hour without problems.
So one should try switching wifi to 5 GHz range if possible.
Xeno_PL at original together.jolla.com thread (https://together.jolla.com/question/180109/announcement-community-sony-xperia-x-compact-release/) found out how to get autobrightness working:
devel-su
printf > /etc/mce/99-blacklist-tcs3490.ini "[evdev]\nblack=AMS TCS3490 Sensor;\n"
systemctl restart mce
nemishkor
2018-03-22, 16:27
devel-su
printf > /etc/mce/99-blacklist-tcs3490.ini "[evdev]\nblack=AMS TCS3490 Sensor;\n"
systemctl restart mce
Adaptive brighness quick fix in terminal from Xeno_PL (https://together.jolla.com/users/2678/xeno_pl/)
I felt that the default haptic feedback volume is bit low, especially some keypresses. You can raise the volume through
/usr/lib/qt5/plugins/feedback/droid-vibrator-device.ini
Up all values by 10 for a mild increase, or 20 for really strong, and reboot the phone.
All keyboards (lockscreen, virtual keyboard and fingerterm) seem to be tied to values PressWeak and ReleaseWeak, so you cannot tune them separately of each other. At least not from this file.
I'm not sure which service could be restarted instead of reboot. Mce did not seem to affect it and ngfd.service seems to be inactive.
citronalco
2018-07-30, 10:17
Has anyone re-build Steph Gosling's image and is willing to write a howto like https://codedream.me/2018/02/02/how-to-build-sailfish-os-for-samsung-galaxy-s7/ or even a script like https://github.com/CancroSailors/sailfish-build-environment?
I tried for several days now, but it seems like I don't have the required knowledge to figure out how things should fit together :(
I'm going to try to install using these instructions https://together.jolla.com/question/180109/announcement-community-sony-xperia-x-compact-release/?sort=latest#sort-top
Unless someone knows better?
Has anyone re-build Steph Gosling's image and is willing to write a howto like https://codedream.me/2018/02/02/how-to-build-sailfish-os-for-samsung-galaxy-s7/ or even a script like https://github.com/CancroSailors/sailfish-build-environment?
I tried for several days now, but it seems like I don't have the required knowledge to figure out how things should fit together :(
i just flashed sailfishos on the xperia x compact. if you could be more specific about the issues you encountered, i might be able to help you.
on a sidenote, would be nice to update to latest version of sailfishos...
Cavalier
2018-07-30, 18:50
What version of Saifish os on your device?
@citronalco - Just curious - what is the value of rebuilding, rather than flashing the available image? Do you think you maybe could update?
@Cavalier - current and only (community) build for XC is 2.1.3.7.
what is the value of rebuilding, rather than flashing the available image?
well, for one, mouhijoki right now instead of kymijoki ;)
for another, if someone posts enough information for someone with reasonable technical skills but limited specific sfos-building-knowledge can build from src, then we wont have to wait for steph to rebuild it in future, either
well, for one, mouhijoki right now instead of kymijoki ;)
for another, if someone posts enough information for someone with reasonable technical skills but limited specific sfos-building-knowledge can build from src, then we wont have to wait for steph to rebuild it in future, either
yeah, mouhijoki would make a huge difference. as for now, myself, it's unusable as daily driver because
1) caldav (not to mention carddav) doesn't work (edit 1/8/18: does now since receiving updated rpm:s)
2) no internet sharing (pro-tip below is good for a one-time solution, but does not provide the one-button approach, i assume)
internet sharing works!
if you have perl (i forget if its by default avail), run this as devel-su in a terminal
#!/usr/bin/perl
use strict;
use warnings;
sub main(@){
system "echo 2 > /sys/module/bcmdhd/parameters/op_mode";
print "turn off tethering, turn off wifi, turn on tethering\n";
print "ready?";
<STDIN>;
system "ip link set dev wlan0 master tether";
print "tethering should now work\n";
print "disable tethering? [Y/n] ";
my $ok = <STDIN>;
if($ok !~ /n/i){
system "echo 1 > /sys/module/bcmdhd/parameters/op_mode";
print "turn off tethering, turn off wifi, turn on wifi\n";
print "also, have fun entering the wifi password\n";
}else{
print "ok, leaving tethering on. wifi wont work. rerun this to fix\n";
}
print "exiting, ok? (you might want to just close the terminal) ";
<STDIN>;
}
&main(@ARGV);
EDIT:
anyway, this is what you need to do as devel-su:
echo 2 > /sys/module/bcmdhd/parameters/op_mode
#turn off tethering, turn off wifi, turn on tethering
ip link set dev wlan0 master tether
#to turn it off, turn off tethering button and then run:
echo 1 > /sys/module/bcmdhd/parameters/op_mode
citronalco
2018-08-02, 21:24
@citronalco - Just curious - what is the value of rebuilding, rather than flashing the available image? Do you think you maybe could update?
Yes, I'd like to try to build an updated image. And I'd like to learn how to set up such things. Plus: I feel rather uncomfortable putting all the burden on a single person, in this case steph.
i have accidentally upgraded sensorfw-qt5 twice now, thus breaking gyro/accel and prox sensors (and by extension, auto-rotation), and each time not noticing until much later that all my photos are portrait..
in case someone else has done so:
zypper install --force sensorfw-qt5=0.9.4-1.32.1 sensorfw-qt5-configs=0.9.4-1.32.1
zypper addlock sensorfw-qt5
i have accidentally upgraded sensorfw-qt5 twice now, thus breaking gyro/accel/compass (and by extension, auto-rotation), and each time not noticing until much later that all my photos are portrait..
You have the compass working on the XC? Per the Xperia X bugs list at together.jolla.com, the compass isn't supposed to work:
Missing Xperia-X hardware functionality:
Fingerprint sensor does not currently function. (fixed with SFOS 2.2.0.x)
Compass does not currently function.
https://together.jolla.com/question/171437/what-bugs-does-sailfish-x-have/
or do I misunderstand?
nope, i mispoke, compass has never worked. i meant proximity sensor
You have the compass working on the XC? Per the Xperia X bugs list at together.jolla.com, the compass isn't supposed to work:
https://together.jolla.com/question/171437/what-bugs-does-sailfish-x-have/
or do I misunderstand?
With the latest release compass is supposed to work on the Xperia X and X Compact.
Or maybe its the next release, we're already using some newer stuff in ported devices I think
afaik, compass only works in google maps, period, and only in mouhijoki
With the latest release compass is supposed to work on the Xperia X and X Compact.
Or maybe its the next release, we're already using some newer stuff in ported devices I think
I'll keep my fingers crossed. :) If you see any FM radio functionality, please let us know! It's the one feature I will miss and can't work around.
Isthere any work being done with updating an image for the x compact or is everybody holding their breath for sfos3?
//Happy user of kyminjoki on x compact.
Hello,
Lurker here (from the Internet Tablet Talk days!) and an occasional contributor to the Sailfish OS community.
I'm chiming in to say that I've been working on a compatibility layer to run official Sailfish X images on the Xperia X Compact.
I've been running it as my daily driver for months (before I was running a custom-built port) and things work nicely (at least, I haven't found more bugs than the ones reported on the officiak Xperia X port).
OTAs work (tested on my own device 2.1.3 -> 2.1.4 -> 2.2.0).
OTG doesn't work and likely won't, as the Xperia X kernel does not ship drivers for the Type-C controller in the X Compact.
The main repo is available here: https://github.com/g7/droid-compat-f5321
Unfortunately another piece required (the image patcher) is not yet public because I'm not that satisfied with the code. Due to time constraints I haven't been able to prettify it, nonetheless I hope to release it sometime this or next week.
So, do not give up!
Eugenio
in case anyone cares, id pay someone 100$USD to port mouhijoki (or later) to x compact, as long as it was approximately as good a port as the kymijoki, and it comes out in the next coupla months and is publicly available like steph's kymijoki port. (deliverable by paypal or credit card)
just throwing that out there, on the off chance that incentivization would be helpful
internet sharing works!
if you have perl (i forget if its by default avail), run this as devel-su in a terminal
#!/usr/bin/perl
use strict;
use warnings;
sub main(@){
system "echo 2 > /sys/module/bcmdhd/parameters/op_mode";
print "turn off tethering, turn off wifi, turn on tethering\n";
print "ready?";
<STDIN>;
system "ip link set dev wlan0 master tether";
print "tethering should now work\n";
print "disable tethering? [Y/n] ";
my $ok = <STDIN>;
if($ok !~ /n/i){
system "echo 1 > /sys/module/bcmdhd/parameters/op_mode";
print "turn off tethering, turn off wifi, turn on wifi\n";
print "also, have fun entering the wifi password\n";
}else{
print "ok, leaving tethering on. wifi wont work. rerun this to fix\n";
}
print "exiting, ok? (you might want to just close the terminal) ";
<STDIN>;
}
&main(@ARGV);
EDIT:
anyway, this is what you need to do as devel-su:
echo 2 > /sys/module/bcmdhd/parameters/op_mode
#turn off tethering, turn off wifi, turn on tethering
ip link set dev wlan0 master tether
#to turn it off, turn off tethering button and then run:
echo 1 > /sys/module/bcmdhd/parameters/op_mode
First script working for me. Second script returns '...device 'tether' not found'
Thanks
$150 for Nurmonjoki before december.
(anyone else want to throw down, and then maybe ask steph?)
Unreasonable Behaviour
2018-09-05, 06:00
$150 for Nurmonjoki before december.
(anyone else want to throw down, and then maybe ask steph?)
Please check this theard on TJC.
https://together.jolla.com/question/185922/sailfish-os-on-sony-xperia-x-compact/
It sound like its possible to convert X image into compact one.
https://github.com/g7/sailfishx-patcher-f5321
This would also be the solution for my wife. :D
WHOA! gonna try this out when i get home. if it works and the dev will take it, theyre gonna get my money
thanks for finding this!!
Nice, I have some friends who have an X compact, one of them even running the community image at the moment. :)
just flashed mine and updating to 2.2.1.18 nurmonjoki.
edit: working beautifully.
(just a quick sidenote, doesnt work anymore on 2.1.3.7 official image, as primary.xml.gz doesnt exist for it)
Sailfish_OS-Jolla-2.2.0.29-f5121-0.2.1.20 zipped image directly from Jolla was fine as a base for patching.
same, but i havent flashed it yet. i spent a few hours trying to get the kymjoki image patched, but i just couldnt download all the right packages that patch.sh needed and couldnt find because the package list for that release is missing on releases.jolla
hey uh, before i flash this thing, does this filesize look right to you @Manatus? (40MB smaller patched)
> du -b Sailfish_OS-*
1132148505 Sailfish_OS-Jolla-2.2.0.29-f5121-0.2.1.20.zip
1094298344 Sailfish_OS-patched-for-f5321-2.2.0.29-f5321-0.2.1.20.zip
hey uh, before i flash this thing, does this filesize look right to you @Manatus? (40MB smaller patched)
> du -b Sailfish_OS-*
1132148505 Sailfish_OS-Jolla-2.2.0.29-f5121-0.2.1.20.zip
1094298344 Sailfish_OS-patched-for-f5321-2.2.0.29-f5321-0.2.1.20.zip
my equivalents:
Sailfish_OS-Jolla-2.2.0.29-f5121-0.2.1.20.zip
1 132 148 505 bytes
Sailfish_OS-patched-for-f5321-2.2.0.29-f5321-0.2.1.20.zip
1 094 433 413 bytes
YAAAY!
works beautifully, with gyro/screen-rot, etc.
donated 130EUR (156USD) to g7 via the paypal donate button on the github repo
(i didnt test out nurmonjoki yet, just mouhijoki, but still)
mousse04
2018-09-10, 18:01
Hey guys ,
how do you make it work with your xperia x image ? I mean, the image is linked to your jolla account name and imei of the device .
So, to get android and exchange you need to provide a valid imei ... Sorry, I'm confused
the g7 process actually uses your official jolla image, which is linked to your jolla account.
it makes small but important changes to that image, leaving imei/etc.
(if you havent bought an official jolla image, then you cant use this process)
ramirowski
2018-09-11, 16:34
Hi all, already patched the official sailfishx zip image, my thoughts about the procedure after 4 attemps:
1.- don't do this in windows due the script is for linux
2.- in ubuntu 18 doesn't work the procedure (I used ubuntu 14)
3.- if you want to use a virtual machine, use vmware player (latest version)
4.- always use the virtualbox and vagrant latest versions!
regards to all from CHILE!
yea, i had to download latest vagrant as well. the one in debian sid was too old, some dependency couldnt be installed for vbguest
aspergerguy
2018-09-12, 11:57
On Mac OSX 10.13.6 using VirtualBox 5.1.38 with latest Vagrant created box debian/stretch64 (v9.5.0) and patched .zip created.
Hadn't appreciated that processor using Ubuntu 16.04 LTS now too old to support virtualisation which wasted a bit of time.
Having now installed to F5321 a couple of points which may save others some time. Firstly I found only satisfactory method of TA Backup was using backupTA_v2 under Windows and also had to install legacy Xperia X Compact driver from:https://developer.sony.com/file/download/xperia-x-compact/ to get Androxyde Flash Tool to recognise device.
mousse04
2018-09-13, 12:23
Guys,
do you know where aliendalvik rpm package is located in the Xperia X ?
Also, I've just flashed my XC with the patched image from my X, but I cannot enable developer mode.
Thanks
I suppose there is no harm telling it, as one has to have the license to download it in the first place...
When the download of the Android support (or Predictive Text) from Jolla store has just ended, they can be found momentarily in the directories
/var/cache/zypp/packages/aliendalvik/armv7hl/
and
/var/cache/zypp/packages/xt9/armv7hl/
If you keep the terminal open and keep tapping at
cp /var/cache/zypp/packages/aliendalvik/armv7hl/* .
you can copy the rpm to your current directory _just_ before the installation is over and it vanishes again.
Note that the directories do not exist until they have been installed at least once.
you can copy the rpm to your current directory _just_ before the installation is over and it vanishes again.
or you can just do `pkcon download . aliendalvik`
or you can just do `pkcon download . aliendalvik`
Last time I tested that it didn't work for me, but if it does, even better. :)
mousse04
2018-09-13, 17:51
or you can just do `pkcon download . aliendalvik`
thanks a lot. just tried anf it works.
but ... the same with sailfish-eas didn't work :(
Edit : ok, finally make everything to work :) !!! Thanks guys
Hmm, I wonder if it is possible to use this method to turn some community ports into a full ones?
Hi all, already patched the official sailfishx zip image, my thoughts about the procedure after 4 attemps:
1.- don't do this in windows due the script is for linux
2.- in ubuntu 18 doesn't work the procedure (I used ubuntu 14)
3.- if you want to use a virtual machine, use vmware player (latest version)
4.- always use the virtualbox and vagrant latest versions!
regards to all from CHILE!
I did it on Win10 with no problems using Vagrant for Windows and VB for Windows...
Hmm, I wonder if it is possible to use this method to turn some community ports into a full ones?
Theoretically, but the reason it works on XC is that it is so close to the same as X. If there are other phones as close to some phone that has official fw, then you could do the same thing.
I was wondering if there might be any way to mount ta backup to the boot img to get Sony camera features. This has been done for Android, with a dev tool and with manual dumping ta to sd card, but not sure if adaptable to our os. I have posted what I tried so far at the end of comments in g7's post here - https://together.jolla.com/question/185922/sailfish-os-on-sony-xperia-x-compact/
Anyone here know about that stuff?
The OBS repo for xperia x compact has been fixed, so hopefully anyone still running the community version should be able to zypper dup to the latest release.
I don't have an xperia x compact, so I cant test it myself and usual warnings apply
Somehow I had completely missed that OTA was working from the command line for community version!
I _was_ wondering what those messages about sensors package were all about in this thread, but I hadn't noticed OTA update mentioned in the Steph's original message. :(
Maybe a reflash time again...
I flashed (twice) to community version and both
devel-su
ssu release 2.2.1.18
pkcon refresh
version --dup
sync
reboot
and
ssu release 2.2.1.18
devel-su zypper clean -a
devel-su zypper ref -f
devel-su zypper dup
sync
power button
caused infinite Sony logo after the reboot.
I flashed (twice) to community version and both
devel-su
ssu release 2.2.1.18
pkcon refresh
version --dup
sync
reboot
and
ssu release 2.2.1.18
devel-su zypper clean -a
devel-su zypper ref -f
devel-su zypper dup
sync
power button
caused infinite Sony logo after the reboot.
Hmm, i guess further investigation is required.
Thanks for playing!
Two be honest I don't know how infinite the Sony logo was, but I waited for several minutes on both occasions... ;)
So not much have changed, first let's make sure if F5321 port has all the repos right
Heres zypper lr output for X Compact:
[root@Sailfish nemo]# zypper lr -d | grep -v openrepos
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
---+-----------------------------+-----------------------------+---------+---------+----------+--------+---------------------------------------------+--------
1 | adaptation-community-common | adaptation-community-common | Yes | No | 99 | rpm-md | plugin:ssu?repo=adaptation-community-common |
2 | apps | apps | Yes | No | 99 | rpm-md | plugin:ssu?repo=apps |
3 | hotfixes | hotfixes | Yes | No | 99 | rpm-md | plugin:ssu?repo=hotfixes |
4 | jolla | jolla | Yes | No | 99 | rpm-md | plugin:ssu?repo=jolla |
14 | store | store | Yes | No | 99 | rpm-md | plugin:ssu?repo=store |
[root@Sailfish nemo]#
and for JP1 for comparision:
[root@Sailfish nemo]# zypper lr -d | grep -v openrepos
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
---+--------------------+--------------------+---------+---------+----------+--------+------------------------------------+--------
1 | adaptation0 | adaptation0 | Yes | No | 99 | rpm-md | plugin:ssu?repo=adaptation0 |
2 | aliendalvik | aliendalvik | Yes | No | 99 | rpm-md | plugin:ssu?repo=aliendalvik |
3 | apps | apps | Yes | No | 99 | rpm-md | plugin:ssu?repo=apps |
4 | customer-jolla | customer-jolla | Yes | No | 99 | rpm-md | plugin:ssu?repo=customer-jolla |
5 | eas | eas | Yes | No | 99 | rpm-md | plugin:ssu?repo=eas |
6 | hotfixes | hotfixes | Yes | No | 99 | rpm-md | plugin:ssu?repo=hotfixes |
7 | jolla | jolla | Yes | No | 99 | rpm-md | plugin:ssu?repo=jolla |
11 | store | store | Yes | No | 99 | rpm-md | plugin:ssu?repo=store |
12 | xt9 | xt9 | Yes | No | 99 | rpm-md | plugin:ssu?repo=xt9 |
is there a way (except tcpdump) to find out full repo url?Can anyone post list of the repos for port with working OTA?
BTW F5321 image buikd job has failed (go link from irc log)
Error <repo>[09/23 10:36:07] : Could not run transaction.
umount: /var/tmp/mic/imgcreate-*/: no mount point specified.
ERROR: Job failed: exit code 1
Maybe that's why update didn't work.
BTW F5321 image buikd job has failed (go link from irc log)
Error <repo>[09/23 10:36:07] : Could not run transaction.
umount: /var/tmp/mic/imgcreate-*/: no mount point specified.
ERROR: Job failed: exit code 1
Maybe that's why update didn't work.
No, that's just an image builder, i think i know whats going on there.
Evidently some packages need updating on OBS, but it helps to have a device to debug.
I f there's an image to try maybe we can set up a irc session, you'll tell me what I have to do and I'll post the results.
Folks, beware of this Fuj:tech USB-C adapter with Xperia X Compact:
https://www.verkkokauppa.com/fi/product/68862/jqkgr/Fuj-tech-microUSB-USB-C-adapteri
I had charging and connection problems with it after couple of months use. It may wear out the connector in the phone.
More:
https://together.jolla.com/question/190313/xperia-x-compact-charging-problem/
X Compact with g7's hacked Xperia X image updated to SFOS 3.0.0.5 without problems.
SFOS 3.0.0.8 updated without problems on g7's image.
Can someone confirm whether the patcher for Sailfish X works for Sailfish 3 as well? The github repository only mentions latest SF2 versions.
I'm on the verge of buying an X Compact, but unfortunately I need Alien Dalvik, so the community port is not enough for me.
[Edit] Oh wait. I thought g7's image was the community build, while it actually is the patched image. Sorry. Great to hear that it works then!
FlyingAntero
2018-11-15, 09:08
I run the patcher provided by G7 (many thanks) using Sailfish X Trial for F5121. The patching process was successful but I got few errors during the process:
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation0' because of the above error.
Error building the cache:
[adaptation1|plugin:/ssu?repo=adaptation1] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation1' because of the above error.
Error building the cache:
[aliendalvik|plugin:/ssu?repo=aliendalvik] Valid metadata not found at specified URL
Warning: Skipping repository 'aliendalvik' because of the above error.
Are these errors related to the commercial features? I have not flashed patched image yet. I am planning to purchase license later and install commercial features then from the Jolla app store.
FlyingAntero
2018-11-18, 18:54
I installed the patched version of Xperia X Sailfish X package (Sailfish OS 3.0.0.8 Trial) to X Compact and everything went well. Once again, thanks to g7 for tool.
[Edit] Oh wait. I thought g7's image was the community build, while it actually is the patched image. Sorry. Great to hear that it works then!
I can confirm that it works on 3.0.0.8. Thanks a lot g7, this is awesome.
I got the same errors FlyingAero, with paid Sailfish X. But I haven't tried all paid features yet (I have close to no use for MS for exchange), however Dalvik and text prediction work well.
FlyingAntero
2018-11-20, 09:23
I ran some benchmarks with my X Compact running on Sailfish 3 and got very strange results in Sysbench. I used these settings:
Single: sysbench --test=cpu --cpu-max-prime=10000 --num-threads=1 run
Multi: sysbench --test=cpu --cpu-max-prime=10000 --num-threads=6 run
I got constant results in multi core test (about 19s) but in single core test there is huge variation. Usually the results is 155s but sometimes 80s. I know that benchmarks are not very realible but this time it is very strange since I got either 155s or 80s, nothing else. Is this related to the issue of using the big cores? I remember that Jolla said during the launch of Xperia X Sailfish X package that foreground apps do not always run on the big cores. Is that fixed yet?
Unreasonable Behaviour
2018-12-12, 16:05
I'm not sure if i should poste here, but a new thread is may be too much.
I have bought a X Compact for my wife and now i want to install salifish on it.
What was done:
- TA partition saved
- Licence bought
- Image downloaded "Sailfish_OS-Jolla-3.0.0.8-f5121-0.2.1.11.zip"
Now I want to use the G7's sailfishx-patcher-f5321 and stuck on the end with:
cat: /vagrant/droid-config-f5121/kickstart/pack/f5121/hybris: No such file or directory
mv: cannot stat 'patcher-tmp/work/Sailfish*.zip': No such file or directory
On the begin there were some more errors:
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation0' because of the above error.
Error building the cache:
[adaptation1|plugin:/ssu?repo=adaptation1] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation1' because of the above error.
Error building the cache:
[aliendalvik|plugin:/ssu?repo=aliendalvik] Valid metadata not found at specified URL
Warning: Skipping repository 'aliendalvik' because of the above error.
Building repository 'apps' cache .................................................. .................................................. .................................................. .......[done]
Building repository 'customer-jolla' cache .................................................. .................................................. ...............................................[done]
Building repository 'hotfixes' cache .................................................. .................................................. .................................................. ...[done]
Building repository 'jolla' cache .................................................. .................................................. .................................................. ......[done]
Error building the cache:
[sailfish-eas|plugin:/ssu?repo=sailfish-eas] Valid metadata not found at specified URL
Warning: Skipping repository 'sailfish-eas' because of the above error.
Building repository 'tmp-compat-f5321' cache .................................................. .................................................. .............................................[done]
Error building the cache:
[xt9|plugin:/ssu?repo=xt9] Valid metadata not found at specified URL
Warning: Skipping repository 'xt9' because of the above error.
Some of the repositories have not been refreshed because of an error.
Did somebody had same error with 3.0?
I can't download an older image anymore.
I have used Win10, as i had troubles to flash my X with Linux before (Oct 2017).
EDIT: may be i found something, i have manually dowloaded the zip for git, by using the cliet there are some more files now
I will try again and let you know
EDIT2: no luck today
I: Syncing back the patched tree
I: Repacking
patcher-tmp/work/repack.sh: line 5: pushd: $'/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.0.0.8-f5121-0.2.1.11/patcher-tmp/work\r': No such file or directory
patcher-tmp/work/repack.sh: line 6: $'\r': command not found
patcher-tmp/work/repack.sh: line 8: $'\r': command not found
patcher-tmp/work/repack.sh: line 10: $'\r': command not found
patcher-tmp/work/repack.sh: line 128: syntax error: unexpected end of file
I: Cleaning up...
Connection to 127.0.0.1 closed.
I'm not sure if i should poste here, but a new thread is may be too much.
I have bought a X Compact for my wife and now i want to install salifish on it.
What was done:
- TA partition saved
- Licence bought
- Image downloaded "Sailfish_OS-Jolla-3.0.0.8-f5121-0.2.1.11.zip"
Now I want to use the G7's sailfishx-patcher-f5321 and stuck on the end with:
cat: /vagrant/droid-config-f5121/kickstart/pack/f5121/hybris: No such file or directory
mv: cannot stat 'patcher-tmp/work/Sailfish*.zip': No such file or directory
On the begin there were some more errors:
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation0' because of the above error.
Error building the cache:
[adaptation1|plugin:/ssu?repo=adaptation1] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation1' because of the above error.
Error building the cache:
[aliendalvik|plugin:/ssu?repo=aliendalvik] Valid metadata not found at specified URL
Warning: Skipping repository 'aliendalvik' because of the above error.
Building repository 'apps' cache .................................................. .................................................. .................................................. .......[done]
Building repository 'customer-jolla' cache .................................................. .................................................. ...............................................[done]
Building repository 'hotfixes' cache .................................................. .................................................. .................................................. ...[done]
Building repository 'jolla' cache .................................................. .................................................. .................................................. ......[done]
Error building the cache:
[sailfish-eas|plugin:/ssu?repo=sailfish-eas] Valid metadata not found at specified URL
Warning: Skipping repository 'sailfish-eas' because of the above error.
Building repository 'tmp-compat-f5321' cache .................................................. .................................................. .............................................[done]
Error building the cache:
[xt9|plugin:/ssu?repo=xt9] Valid metadata not found at specified URL
Warning: Skipping repository 'xt9' because of the above error.
Some of the repositories have not been refreshed because of an error.
Did somebody had same error with 3.0?
I can't download an older image anymore.
I have used Win10, as i had troubles to flash my X with Linux before (Oct 2017).
EDIT: may be i found something, i have manually dowloaded the zip for git, by using the cliet there are some more files now
I will try again and let you know
EDIT2: no luck today
I: Syncing back the patched tree
I: Repacking
patcher-tmp/work/repack.sh: line 5: pushd: $'/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.0.0.8-f5121-0.2.1.11/patcher-tmp/work\r': No such file or directory
patcher-tmp/work/repack.sh: line 6: $'\r': command not found
patcher-tmp/work/repack.sh: line 8: $'\r': command not found
patcher-tmp/work/repack.sh: line 10: $'\r': command not found
patcher-tmp/work/repack.sh: line 128: syntax error: unexpected end of file
I: Cleaning up...
Connection to 127.0.0.1 closed.
Your tool is either not tested well enough since it seems to use your native filesystem and not expect it to be vfat ntfs or the like and barfs on the lineendings or symbolic links. Or you did something wrong with any git repo checkout like using native lineendings or unpacking things by hand instead of letting the script/tool do it. Did you move part of the stuff from your other computer to this one?
Unreasonable Behaviour
2018-12-13, 11:19
Your tool is either not tested well enough since it seems to use your native filesystem and not expect it to be vfat ntfs or the like and barfs on the lineendings or symbolic links. Or you did something wrong with any git repo checkout like using native lineendings or unpacking things by hand instead of letting the script/tool do it. Did you move part of the stuff from your other computer to this one?
@ljo thanks for your replay
Instructions for the patcher are contained in git:
https://github.com/g7/sailfishx-patcher-f5321
You have to use vagrant which is creating an Vitual Box VM.
So every thing is running on the created VM.
I have tried it now on my Linux VM but there the limitation is Virtual Box (runnung VM in a VM) you will got: “VT-x is not available”
BUT, i copied the the files from git repo (VM Linux) to Win
and have now a patched image. :D
I: Done! Enjoy!
I: Cleaning up...
EDIT: Device is now up and running Sailfish 3.0.0.8 :D
I ran some benchmarks with my X Compact running on Sailfish 3 and got very strange results in Sysbench. I used these settings:
Single: sysbench --test=cpu --cpu-max-prime=10000 --num-threads=1 run
Multi: sysbench --test=cpu --cpu-max-prime=10000 --num-threads=6 run
I got constant results in multi core test (about 19s) but in single core test there is huge variation. Usually the results is 155s but sometimes 80s. I know that benchmarks are not very realible but this time it is very strange since I got either 155s or 80s, nothing else. Is this related to the issue of using the big cores? I remember that Jolla said during the launch of Xperia X Sailfish X package that foreground apps do not always run on the big cores. Is that fixed yet?
Have you seen this - https://together.jolla.com/question/187833/howto-enable-a72-cores-to-make-xperia-17x-faster/
FlyingAntero
2018-12-31, 10:09
Have you seen this - https://together.jolla.com/question/187833/howto-enable-a72-cores-to-make-xperia-17x-faster/
Yes, I did see that earlier. If I have understand correct those A72 cores are in use in some usage scenarios but not always. That might reason for the strange results in sysbench.
Updated g7's version to SFOS 3.0.1.11 without problems.
aspergerguy
2019-01-07, 20:12
Updated g7's version to SFOS 3.0.1.11 without problems.
Concur with this although as only supposed to be bug fixes just a cautionary note that updating to Sailfish 3.0.1.11 destroys something and you will get "Waiting for network" message if Play Store previously installed. Updated both F5321(g7) and F5122 with this result, whilst downgrading both to 3.0.0.5 restored Play Store function again.
Unreasonable Behaviour
2019-01-16, 16:27
Updated g7's version to SFOS 3.0.1.11 without problems.
I can confirm :)
Hello
I just switch from my old & destroy oneplusx with port sailfishos to Xcompact with sailfishX and the g7 patch (Thanks to him)
Everything seems OK except (for my first tests) that I don't have sound in my record video
Do you have the same issue ?
Unreasonable Behaviour
2019-01-22, 17:47
Hello
I just switch from my old & destroy oneplusx with port sailfishos to Xcompact with sailfishX and the g7 patch (Thanks to him)
Everything seems OK except (for my first tests) that I don't have sound in my record video
Do you have the same issue ?
Works fine on my wife's device.
May be the media volume is set to a lower level?
Is the mic correctly working?
You could check with CSD Tool.
Go to settings -> product information and click 5 times on the buildnumber, then it should start.
Audio for recorded video works for me too.
Audio for recorded video works for me too.
after more tests it s ok
Volume seems be at low level when I did my first test
sorry for off-topic; I just wanted to quickly reach out to X Compact users... LuneOS, (open continuation of HP WebOS - now dead, but still probably the best OS to date), has had a recent update - https://pivotce.com/2018/11/28/luneos-november-stable-release-doppio/ . X Compact is a perfect candidate for LuneOS, in my opinion - small, good specs, affordable, available, and with plenty of framework in place, (Lineage, AOSP, and Halium). I don't have the experience or ability or computer set up neded to build. Anybody else?
who needs this dead stuff with no apps?
PS I had hp touchpad
who needs this dead stuff with no apps?
PS I had hp touchpad
Who needs 'apps' is the proper question...
who needs this dead stuff with no apps?
PS I had hp touchpad
Nobody - let's join the cause to resurrect it, and fill it to heaven with apps...
oh yeah. like Sailfish/ubuntu touch/etc wasn't enough to see that niche OSes are in dire need of apps.
So let's create another OS, it won't be the same this time.
oh yeah. like Sailfish/ubuntu touch/etc wasn't enough to see that niche OSes are in dire need of apps.
So let's create another OS, it won't be the same this time.
Whaddyamean SFOS is a niche OS because no apps?
It's my daily driver with pretty much all the features I need.
And here 'features' != 'apps'
oh yeah. like Sailfish/ubuntu touch/etc wasn't enough to see that niche OSes are in dire need of apps.
So let's create another OS, it won't be the same this time.
WebOS goes back to 2011, and further back to PalmOS, so it's not really a new one. It has to be re-created by devs bc of proprietary stuff, but if you look at what has been done and the effort being put into it staying alive, (not only LuneOS, but even legacy WebOS, software and hardware as-is), it speaks of the fact of it being "not just another alternative OS". LG, who currently owns WebOS, and still uses it for tvs, even met with LuneOS team recently to talk about their plans for an official open WebOS. fact is: WebOS is awesome, and if the attention could miraculously be given to it, it jas a real chance to succeed ...
it doesn't have a chance to succeed
even tizen is dead, while samsung has way more resources to do something with it than lg has
PS not only did I have hp touchpad, I've had palm m505 and sony nx73v, so I know a lil bit of history
PPS from all those OSes besides ios/android, only Sailfish looks live enough to be a real alternative someday, so all the resources ideally should be put into it, not spread all over dead OSes and forks.
it doesn't have a chance to succeed
even tizen is dead, while samsung has way more resources to do something with it than lg has
PS not only did I have hp touchpad, I've had palm m505 and sony nx73v, so I know a lil bit of history
PPS from all those OSes besides ios/android, only Sailfish looks live enough to be a real alternative someday, so all the resources ideally should be put into it, not spread all over dead OSes and forks.
Probably true... I had to try. I'm actually pretty happy w/ Sailfish also. You have to admit, though, being an old-time WebOSer - it would be pretty neat to have it on an XC.
I updated my X Compact to SFOS 3.0.2.8. No other problems except that settings did not offer the update for me directly (I'm in EA) so I had to do
devel-su
ssu release 3.0.2.8
pkcon refresh
version --dup
sync
reboot
aspergerguy
2019-03-19, 14:24
I updated my X Compact to SFOS 3.0.2.8. No other problems except that settings did not offer the update for me directly (I'm in EA)
Surprised as prompted upon my Xperia X Compact:
has anyone run the g7 patcher successfully on 3.0.1 or 3.0.2? I got it to go fine right up to the last line, then the script closes when it can't find it's own temp file, and ends with "... I: Repacking cat: /vagrant/droid-config-f5121/kickstart/pack/f5121/hybris: No such file or directory mv: cannot stat 'patcher-tmp/work/Sailfish*.zip': No such file or directory" Any ideas?
Full log is here - https://pastebin.com/nKh8QAqk
I was able to get patched root.img by changing the last line of the script from "patcher-tmp/work/Sailfish*.zip" to "patcher-tmp/work/root.img", but I think it contains all partitions, so not sure how to divied it, and fashing it to system doesn't work.
Unreasonable Behaviour
2019-03-26, 20:29
has anyone run the g7 patcher successfully on 3.0.1 or 3.0.2? I got it to go fine right up to the last line, then the script closes when it can't find it's own temp file, and ends with "... I: Repacking cat: /vagrant/droid-config-f5121/kickstart/pack/f5121/hybris: No such file or directory mv: cannot stat 'patcher-tmp/work/Sailfish*.zip': No such file or directory" Any ideas?
Full log is here - https://pastebin.com/nKh8QAqk
I was able to get patched root.img by changing the last line of the script from "patcher-tmp/work/Sailfish*.zip" to "patcher-tmp/work/root.img", but I think it contains all partitions, so not sure how to divied it, and fashing it to system doesn't work.
I think i had the same problem on a earlier release too. Please check post 106 and 108.
The trick is to clone the repository correct, i have done this on linux vm and moved the files to windows.
Then you can clone the repository (form g7 readme):
git clone https://github.com/g7/sailfishx-patcher-f5321.git
cd sailfishx-patcher-f5321
git submodule init
git submodule update
I think i had the same problem on a earlier release too. Please check post 106 and 108.
The trick is to clone the repository correct, i have done this on linux vm and moved the files to windows.
Then you can clone the repository (form g7 readme):
git clone https://github.com/g7/sailfishx-patcher-f5321.git
cd sailfishx-patcher-f5321
git submodule init
git submodule update
Thanks, but I'm using Windows 10. Vagrant and Vbox worked fine to patch 2.2, but getting this error on 3.0...
I think i had the same problem on a earlier release too. Please check post 106 and 108.
The trick is to clone the repository correct, i have done this on linux vm and moved the files to windows.
Then you can clone the repository (form g7 readme):
git clone https://github.com/g7/sailfishx-patcher-f5321.git
cd sailfishx-patcher-f5321
git submodule init
git submodule update
Do you know soecifically which files are different depending on whoch address you cloned? Maybe I can manually download appropriately through Windows...
aspergerguy
2019-03-27, 20:31
has anyone run the g7 patcher successfully on 3.0.1 or 3.0.2? I got it to go fine right up to the last line, then the script closes when it can't find it's own temp file, and ends with "... I: Repacking cat: /vagrant/droid-config-f5121/kickstart/pack/f5121/hybris: No such file or directory mv: cannot stat 'patcher-tmp/work/Sailfish*.zip': No such file or directory" Any ideas?
Have now managed to create both Sailfish_OS-patched-for-f5321-3.0.1.11-f5321-0.2.1.6.zip and Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15.zip using Mac OSX with Vagrant 2.2.4 & VirtualBox 5.2.28 as g7 modified patch.sh a matter of only 11 hours ago to use grep without -P (Perl) flag.
Resizing the filesystem on fimage.img to 194702 (4k) blocks.
The filesystem on fimage.img is now 194702 (4k) blocks long.
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/ (stored 0%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flashing-README.txt (deflated 59%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/md5.lst (deflated 36%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.exe (deflated 67%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/sailfish.img001 (deflated 54%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-boot.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-recovery.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinUsbApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash.sh (deflated 57%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/Jolla-3.0.2.8-f5121-armv7hl.urls (deflated 92%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash-on-windows.bat (deflated 63%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.img (deflated 3%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fimage.img001 (deflated 2%)
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.0.2.8-f5121-0.2.1.15
I: Done! Enjoy!
I: Cleaning up...
Have now managed to create both Sailfish_OS-patched-for-f5321-3.0.1.11-f5321-0.2.1.6.zip and Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15.zip using Mac OSX with Vagrant 2.2.4 & VirtualBox 5.2.28 as g7 modified patch.sh a matter of only 11 hours ago to use grep without -P (Perl) flag.
Resizing the filesystem on fimage.img to 194702 (4k) blocks.
The filesystem on fimage.img is now 194702 (4k) blocks long.
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/ (stored 0%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flashing-README.txt (deflated 59%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/md5.lst (deflated 36%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.exe (deflated 67%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/sailfish.img001 (deflated 54%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-boot.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-recovery.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinUsbApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash.sh (deflated 57%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/Jolla-3.0.2.8-f5121-armv7hl.urls (deflated 92%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash-on-windows.bat (deflated 63%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.img (deflated 3%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fimage.img001 (deflated 2%)
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.0.2.8-f5121-0.2.1.15
I: Done! Enjoy!
I: Cleaning up...
Nice - I'll try again with new files...
Have now managed to create both Sailfish_OS-patched-for-f5321-3.0.1.11-f5321-0.2.1.6.zip and Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15.zip using Mac OSX with Vagrant 2.2.4 & VirtualBox 5.2.28 as g7 modified patch.sh a matter of only 11 hours ago to use grep without -P (Perl) flag.
Resizing the filesystem on fimage.img to 194702 (4k) blocks.
The filesystem on fimage.img is now 194702 (4k) blocks long.
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/ (stored 0%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flashing-README.txt (deflated 59%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/md5.lst (deflated 36%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.exe (deflated 67%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/sailfish.img001 (deflated 54%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-boot.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/hybris-recovery.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinUsbApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash.sh (deflated 57%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/Jolla-3.0.2.8-f5121-armv7hl.urls (deflated 92%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/AdbWinApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/flash-on-windows.bat (deflated 63%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fastboot.img (deflated 3%)
adding: Sailfish_OS-patched-for-f5321-3.0.2.8-f5321-0.2.1.15/fimage.img001 (deflated 2%)
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.0.2.8-f5121-0.2.1.15
I: Done! Enjoy!
I: Cleaning up...
Same result for me on Windows... Full log here - https://pastebin.com/JdE01qte
aspergerguy
2019-03-28, 16:57
Same result for me on Windows... Full log here - https://pastebin.com/JdE01qte
Have now patched 3.0.2.8 using Mac OSX, Windows 10 and Ubuntu 18.04 LTS satisfactorily. I am not a Windows user by choice but you do seem to be running it in quite a buried folder structure, whereas using GIT it is right after ~ if makes any sense. Did you just add new patch.sh to existing or recreate from scratch?
Have now patched 3.0.2.8 using Mac OSX, Windows 10 and Ubuntu 18.04 LTS satisfactorily. I am not a Windows user by choice but you do seem to be running it in quite a buried folder structure, whereas using GIT it is right after ~ if makes any sense. Did you just add new patch.sh to existing or recreate from scratch?
Deleted the whole old folder and started from scratch... I'll try moving the directory and see what happens. Thanks for confirming that it worked for you. At least now I know I'm not messing with it for nothing...
aspergerguy
2019-03-28, 20:09
Thanks for confirming that it worked for you. At least now I know I'm not messing with it for nothing...
Here is Windows 10 log file in case of any help to you: https://pastebin.com/N2Xjg7RU
I would try getting a new F5121 3.0.2.8 image as yours doesn't have libpython3_7m1_0 but the old libpython3_4m1_0 and on my output retrieves 17 new packages instead of your 16 new packages.
Here is Windows 10 log file in case of any help to you: https://pastebin.com/N2Xjg7RU
I would try getting a new F5121 3.0.2.8 image as yours doesn't have libpython3_7m1_0 but the old libpython3_4m1_0 and on my output retrieves 17 new packages instead of your 16 new packages.
Thanks. I also got some help on TJC, so I'll work on it...
Here is Windows 10 log file in case of any help to you: https://pastebin.com/N2Xjg7RU
I would try getting a new F5121 3.0.2.8 image as yours doesn't have libpython3_7m1_0 but the old libpython3_4m1_0 and on my output retrieves 17 new packages instead of your 16 new packages.
Problem solved - I guess the droid-compat folder is empty when downloading the zip from Github, (since it's expected that you would update submodules, but I only downloaded the zip and extracted it). I simply downloaded the droid-compat files as a separate zip, and copied them to the folder. Success. Thanks again
Unreasonable Behaviour
2019-04-25, 15:58
Update to Sailfish 3.0.3 Hossa worked well on Sony Xperia X Compact :p
Same (actually one issue, but unrelated to the device model).
Flash-A-Holic
2019-07-10, 03:53
I updated my X Compact to SFOS 3.0.2.8. No other problems except that settings did not offer the update for me directly (I'm in EA) so I had to do
I had same issue. I was on SFOS 3.0.1 but the updater via settings said that software was up to date. I used terminal to update to 3.0.2.8. Again, updater did not offer update to 3.0.3. Once again I updated via terminal to latest 3.0.3.10. Any ideas how to fix the updater (via settings).
meet.vino
2019-07-10, 06:24
Update to Sailfish 3.0.3 Hossa worked well on Sony Xperia X Compact :p
Does it have Android Support? I require it only for one app called Hike Messenger. Btw, is there a native App for Hike Messenger?
Flash-A-Holic
2019-07-10, 07:22
Does it have Android Support? I require it only for one app called Hike Messenger. Btw, is there a native App for Hike Messenger?
You can buy the license for Android App support. For Xperia X ja X Compact it is up to Android KitKat 4.4. For XA2 serie it is up to Android Oreo 8.1.
meet.vino
2019-07-11, 05:16
You can buy the license for Android App support. For Xperia X ja X Compact it is up to Android KitKat 4.4. For XA2 serie it is up to Android Oreo 8.1.
I bought a Xperia X license but I haven't used it. Can I use it for the X Compact?
aspergerguy
2019-07-11, 05:38
I bought a Xperia X license but I haven't used it. Can I use it for the X Compact?
Yes you can, although Jolla will register device as F5121.
Flash-A-Holic
2019-07-19, 03:32
I had same issue. I was on SFOS 3.0.1 but the updater via settings said that software was up to date. I used terminal to update to 3.0.2.8. Again, updater did not offer update to 3.0.3. Once again I updated via terminal to latest 3.0.3.10. Any ideas how to fix the updater (via settings).
Still same issue. My XA2 can find the new 3.1.0.11 update but X Compact cannot. How to solve this issue? Tried to change to different account but it did not fix the issue.
aspergerguy
2019-07-19, 05:16
Still same issue. My XA2 can find the new 3.1.0.11 update but X Compact cannot. How to solve this issue?
No problem updating XperiaCompact last night.
Flash-A-Holic
2019-07-19, 05:24
No problem updating XperiaCompact last night.
Any idea what might be wrong with my X Compact. I can update via terminal just fine but via settings I cannot find any update. It just says device is up to date.
I too had to update via command line. The same with the three previous updates, so it does not seem to get fixed by itself.
Flash-A-Holic
2019-07-24, 09:33
Could it be related to this:
- https://together.jolla.com/question/202496/one-jolla-account-to-rule-them-all-not-working/
I have also two devices with same account. Other phone can get updates but X Compact doesn't. Do you have several devices with same account?
aspergerguy
2019-07-24, 09:51
Could it be related to this:
- https://together.jolla.com/question/202496/one-jolla-account-to-rule-them-all-not-working/
I have also two devices with same account. Other phone can get updates but X Compact doesn't. Do you have several devices with same account?
Whilst Jolla's advice now is for separate accounts for each device, historically I have had a number of devices upon account updating without issue provided the appropriate licenses have been purchased for those requiring them ( a mix of Jolla 1, AquaFish, Xperia X, Xperia X Compact and XA2); with proviso that redemption of Jolla Tablet refund vouchers against Sailfish license may have necessitated some intervention upon my account by Jolla.
FlyingAntero
2019-08-15, 06:44
Has anyone tried to run Anbox on X Compact? I installed Anbox to my X Compact but it does not work without patched kernel. Any tutorial how to apply those patches?
https://github.com/anbox/anbox/tree/0f80db195e50a5ba048fef9c28881b85efc2cefd/kernel/patches
https://github.com/adilinden-oss/overlayfs-patches
https://github.com/mlehtima/android_kernel_sony_msm/commit/947b4eb5c26c0eb22c708d73ca712b04f1a1d960
nikos523
2019-08-31, 13:08
How to install mce-tools
Notice you can also set:
mcetool -–set-doubletap-mode=unlock
...to unlock the phone with a double tap.
Works fine on my XC.
hi
how can i disable this option now and remove double tap to unlock?
thanks
mcetool --help
...
--set-doubletap-mode=<disabled|show-unlock-screen|unlock>
...
nikos523
2019-08-31, 15:08
mcetool --help
...
--set-doubletap-mode=<disabled|show-unlock-screen|unlock>
...
That gives me syntax error 'newLine' for some reason.
I checked help documentation, checked for typos, nothing wrong but it doesnt work.
to be clear, the command to remove double-tap unlocking is:
mcetool --set-doubletap-mode=disabled
nikos523
2019-08-31, 16:05
to be clear, the command to remove double-tap unlocking is:
mcetool --set-doubletap-mode=disabled
Thanks, that worked.
Yet the "side effects" are still there. That means I can see the proximity sensor blinking when I use my camera (didn't before) and lockscreen swipe is still unresponsive some times.
Edit
Nevermind, I refreshed the device and it seems to work again now.
Warning :
I just updated to 3.2.0 my X compact and i lost camera feature
app camera stay black, no flashlight feature
same issue with the advanced camera apps
Warning :
I just updated to 3.2.0 my X compact and i lost camera feature
app camera stay black, no flashlight feature
same issue with the advanced camera apps
in fact after pkcon refresh ans pkcon update some package are missing
droid-compat-f5321-hybris-libsensorfw-qt5-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:38 CET
droid-compat-f5321-feature-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:38 CET
droid-compat-f5321-droid-system-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-hal-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-config-sailfish-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-config-flashing-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:32 CET
droid-compat-f5321-droid-config-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:32 CET
But after update i always have the problem =/
No issues after update to 3.2.0.12 for me. Except that I had to do it from the command line, as usual for some time on my device.
in fact after pkcon refresh ans pkcon update some package are missing
droid-compat-f5321-hybris-libsensorfw-qt5-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:38 CET
droid-compat-f5321-feature-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:38 CET
droid-compat-f5321-droid-system-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-hal-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-config-sailfish-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:34 CET
droid-compat-f5321-droid-config-flashing-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:32 CET
droid-compat-f5321-droid-config-0.0.9-1.27.1.jolla.armv7hl Wed 30 Oct 2019 22:02:32 CET
But after update i always have the problem =/
Hi all,
Anyone have an idea ?
it's like missing some driver.
No big information when I launch the camera APP and CSD test fail to.
Hello, patch creator here. I hope this post doesn't get to moderation like the other one did last time :)
If you updated before 30/10 00:00 UTC+1 you might get the camera black (and aliendalvik not starting) issue.
Everyone who updated afterwards is (should be) fine, X Compact compatibility layer updates are picked automatically during Sailfish OS upgrades.
For those who experience the issue(s), these commands should be enough:
devel-su
zypper ref -r compat-f5321
zypper dup -r compat-f5321
add-preinit-oneshot /var/lib/platform-updates/flash-bootimg.sh
reboot
=================================================
For those wondering what the issue was, SELinux got enabled in Jolla's Xperia X kernel and then subsequently disabled via kernel cmdline (https://github.com/mer-hybris/droid-hal-img-boot-f5121/commit/e75706e57e2117675c7313d8f31084091c180e27) (I think to easily test SELinux without having to re-build the kernel).
This broke both the camera and aliendalvik.
The patcher patches on-the-fly Jolla's kernel replacing the devicetree and the cmdline to match X Compact's.
So in the end we got SELinux enabled and a cmdline which doesn't explicitly disable it.
The cmdline has been synced (https://github.com/g7/droid-compat-f5321/pull/2/files).
We got pretty unlucky as Jolla touched one of the few HA parts that the patch touches too :) Fortunately the fix is simple enough.
Eugenio
meet.vino
2019-11-01, 04:17
Hi.. Can anyone please confirm if there is Android support for X Compact? And, is the camera quality that bad?
Hi.. Can anyone please confirm if there is Android support for X Compact? And, is the camera quality that bad?
camera quality is same as X, android support is same as X.
X Compact is my only phone, and ive been using it for 16 months without any significant issues (with g7-patched official rom). before that, i used X for a year.
(note that in order to get android support, you must pay for a sailfish X license. you can then download and patch the img with g7's patcher, and install it just like the X, and have android support, etc)
aspergerguy
2019-11-01, 05:38
(note that in order to get android support, you must pay for a sailfish X license. you can then download and patch the img with g7's patcher, and install it just like the X, and have android support, etc)
Haven't tried recently but ran into problems trying to patch Sailfish 3.xx.img so have to flash older 2.xx one and then update via terminal.
i flashed Sailfish_OS-patched-for-f5321-3.1.0.11-f5321-0.2.1.17.zip
worked fine for me.
when jolla posts my official 3.2 download in the jolla shop, ill try to patch+flash it, and report what happens here
(although, despite having flashed 3 SXC's at least 10 times total, im still not too clear on who picks up the changes to droid-compat-f5321, and where, when i run the patcher in vagrant)
aspergerguy
2019-11-02, 10:56
i flashed Sailfish_OS-patched-for-f5321-3.1.0.11-f5321-0.2.1.17.zip
worked fine for me.
Revisited this and after updating Vagrant happy to concur no issues in creating "Sailfish_OS-patched-for-f5321-3.1.0.11-f5321-0.2.1.17" on Mac
Revisited this and after updating Vagrant happy to concur no issues in creating "Sailfish_OS-patched-for-f5321-3.1.0.11-f5321-0.2.1.17" on Mac
Glad to hear that :)
(although, despite having flashed 3 SXC's at least 10 times total, im still not too clear on who picks up the changes to droid-compat-f5321, and where, when i run the patcher in vagrant)
The compatibility layer is on an OBS repository (https://build.merproject.org/project/show/home:eugenio:compat-f5321), the patcher script simply unpacks the stock Sailfish X images, adds the repository and installs the pattern specifying the packages to install.
Then the target kernel gets patched too and everything gets repacked and zipped.
The patching process also installs an SSU feature referencing the compatibility layer repository, so that updates to the compatibility layer gets picked up during Sailfish OS OTA upgrades.
Has anyone else expierienced crashes on android browser with embedded youtube links after 3.2 upgrade
aspergerguy
2019-11-06, 14:46
Revisited this and after updating Vagrant happy to concur no issues in creating "Sailfish_OS-patched-for-f5321-3.1.0.11-f5321-0.2.1.17" on Mac
Similarly no problems creating "Sailfish_OS-patched-for-f5321-3.2.0.12-f5321-0.2.1.15.zip" today.
:( for the first time using eugenio patcher, i AM having trouble creating Sailfish_OS-patched-for-f5321-3.2.0.12-f5321-0.2.1.15.zip
rather, having trouble flashing it once i create it. i get this:
wolke:~/Code/sx/flashing/Sailfish_OS-patched-for-f5321-3.2.0.12-f5321-0.2.1.15$ ./flash.sh
Detected Linux
Searching device to flash..
Found 1 devices: QV701QB10B
Fastboot command: fastboot -s QV701QB10B
Flashing boot partition..
target reported max download size of 536870912 bytes
sending 'boot' (12228 KB)...
OKAY [ 0.440s]
writing 'boot'...
OKAY [ 0.098s]
finished. total time: 0.538s
Flashing userdata partition..
target reported max download size of 536870912 bytes
error: write_sparse_skip_chunk: don't care size 518443984 is not a multiple of the block size 4096
erasing 'userdata'...
OKAY [ 0.434s]
sending sparse 'userdata' 1/2 (511248 KB)...
error: write_sparse_skip_chunk: don't care size 518443984 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 518443984 is not a multiple of the block size 4096
OKAY [ 16.074s]
writing 'userdata' 1/2...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 20.307s
just to check, i rebuilt 3.1 (in eugenio's ./patch.sh -a f5321 in vagrant) and reflashed it and it worked fine. no idea whats up
could NOT get it to work btw. have no idea why sailfish.img has wrong sparse size, and comparing the logs between the two builds (3.1 and 3.2) was not enlightening
aspergerguy
2019-11-09, 15:15
Just a thought, you are using the latest "platform-tools" for fastboot?
im on debian sid, which is usually fairly up-to-date with these things
wolke:~$ fastboot --version
fastboot version 1:8.1.0+r23-5
Installed as /usr/lib/android-sdk/platform-tools/fastboot
ok, now, im on the actual current version of platform-tools, and its still failing. (fastboot version 29.0.5-5949299)
wolke:~/Code/sx/flashing/Sailfish_OS-patched-for-f5321-3.2.0.12-f5321-0.2.1.15$ fastboot --version
fastboot version 29.0.5-5949299
Installed as /usr/lib/android-sdk/platform-tools/fastboot
wolke:~/Code/sx/flashing/Sailfish_OS-patched-for-f5321-3.2.0.12-f5321-0.2.1.15$ fastboot flash userdata sailfish.img001
error: write_sparse_skip_chunk: don't care size 511927192 is not a multiple of the block size 4096
Sending sparse 'userdata' 1/2 (519476 KB) error: write_sparse_skip_chunk: don't care size 511927192 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 511927192 is not a multiple of the block size 4096
OKAY [ 16.373s]
Writing 'userdata' FAILED (remote: 'buffer overreads occured due to invalid sparse header')
fastboot: error: Command failed
android app support is broken for me!
in 3.1 with a fresh flash of g7 (also continues to be broken after ssu-ing to 3.2)
i can install android support (during initial setup or in jolla store, i have a paid license).
it works fine, AndroidSupport is in the config, /opt/alien looks good, i can logcat and see services starting and such.
BUT i cant install any APKs, and when i install Andriod Store (aptoide) from the jolla store, the icon disappears before i can click it (no desktop file is generated, and afaict, nothing is actually installed).
when i use apkd-install, the DBUS service returns 'ok' and does nothing.....
android-support worked perfectly fine the FIRST time i flashed 3.1. the RPM has been updated to aliendalvik-1.0.90-1.armv7hl.rpm, but installing the previous aliendalvik-1.0.89-1.armv7hl.rpm doesnt help either...
again, this is on a fresh 3.1 install, with working jolla login and a paid license...
:(
apkd-install aptoide_cm.aptoide.pt_9.0.0.3.apk
devel-su chroot /opt/alien /system/bin/logcat
D/AlienPackageManagerClient( 5729): installPackage size = 37
D/AlienNativePackageManager( 5729): installPackage=/data/app//incoming/cm.aptoide.pt.apk, silent = false
W/ContextImpl( 5729): Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1028 com.android.server.AlienNativePackageManager.insta llPackage:179 dalvik.system.NativeStart.run:-2 <bottom of call stack> <bottom of call stack>
W/ContextImpl( 5729): Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1040 android.app.ContextImpl.startActivity:1029 com.android.server.AlienNativePackageManager.insta llPackage:179 dalvik.system.NativeStart.run:-2 <bottom of call stack>
I/ActivityManager( 5729): START u0 {act=android.intent.action.VIEW dat=file:///data/app/incoming/cm.aptoide.pt.apk typ=application/vnd.android.package-archive flg=0x10000000 cmp=com.android.packageinstaller/.PackageInstallerActivity} from pid 5729
W/ResourceType( 5869): Failure getting entry for 0x7f070004 (t=6 e=4) in package 0 (error -75)
D/dalvikvm( 5869): GC_CONCURRENT freed 1617K, 15% free 16231K/18880K, paused 2ms+27ms, total 58ms
D/dalvikvm( 5869): WAIT_FOR_CONCURRENT_GC blocked 48ms
D/dalvikvm( 5869): GC_FOR_ALLOC freed 5770K, 34% free 12559K/18880K, paused 25ms, total 25ms
D/dalvikvm( 5869): GC_FOR_ALLOC freed 751K, 33% free 12676K/18880K, paused 17ms, total 17ms
D/dalvikvm( 5869): GC_FOR_ALLOC freed 254K, 32% free 12930K/18880K, paused 14ms, total 14ms
I/dalvikvm-heap( 5869): Grow heap (frag case) to 13.015MB for 380813-byte allocation
D/dalvikvm( 5869): GC_FOR_ALLOC freed 509K, 34% free 12792K/19252K, paused 16ms, total 16ms
D/dalvikvm( 5869): GC_FOR_ALLOC freed 240K, 33% free 13048K/19252K, paused 14ms, total 14ms
I/dalvikvm-heap( 5869): Grow heap (frag case) to 13.263MB for 520988-byte allocation
D/dalvikvm( 5869): GC_FOR_ALLOC freed 254K, 33% free 13303K/19764K, paused 14ms, total 14ms
D/dalvikvm( 5869): GC_CONCURRENT freed 829K, 30% free 13910K/19764K, paused 1ms+4ms, total 32ms
D/dalvikvm( 5869): WAIT_FOR_CONCURRENT_GC blocked 22ms
D/dalvikvm( 5869): GC_CONCURRENT freed 496K, 24% free 15053K/19764K, paused 1ms+5ms, total 59ms
D/dalvikvm( 5869): WAIT_FOR_CONCURRENT_GC blocked 53ms
D/dalvikvm( 5869): GC_CONCURRENT freed 1278K, 21% free 15795K/19764K, paused 1ms+4ms, total 62ms
D/dalvikvm( 5869): WAIT_FOR_CONCURRENT_GC blocked 56ms
I/ActivityManager( 5729): Displayed com.android.packageinstaller/.PackageInstallerActivity: +829ms
g7 fixed the 3.2.0.12 patching/flashing issue. it is now possible to patch it and install it using the git branch `block-size-alignment` of `sailfishx-patcher-f5321`
...aaaand merged to master :)
Thanks to @wolke for testing!
p.s.: newly built zip fixed the aliendalvik issue as well
EDIT: i never did figure this one out. it was suddenly completely broken on freshly built 3.1 installs (despite working on 3.1 before), and stayed broken after updating to 3.2 with ssu. flashing 3 different times with slightly different procedures didnt fix it. also, once logged into jolla account in 3.1, it offered me the official upgrade to 3.2 (which it never did before....), and then THAT didnt fix it.
installing zip of 3.2 fixed it, no problem.
monkeyisland
2019-11-12, 16:48
Hello Question:
Is it now safe to upgrade the compact with the gui?
:)
aspergerguy
2019-11-12, 18:03
[QUOTE=monkeyisland;1561883]Is it now safe to upgrade the compact with the gui?
:)[/QUOTE
Did two examples via terminal without issue but not brave enough to rely upon gui.
Is it now safe to upgrade the compact with the gui?
Yes, it is!
maximilian1st
2019-11-15, 09:48
Hi all,
first of all thank you Eugenio for your work creating the patch, as soon as I have a working 5321 I'll head to PayPal.
I just wanted to mention this request I made to Jolla Care about a transfer of my broken Xperia X licence to my Xperia X Compact phone and got this answer:
HI,
Thank you for your message!
Since we don't support your device, we cannot transfer your licence as it won't give you any Android support or other licensed benefits.
Sincerely,
Jolla Customer Care
It's a bit of a shame the device is not supported officially as it seems to work for all of you, but coming from a small company I can understand they don't have the resources for it.
maximilian1st
2019-11-15, 10:40
And now the patcher complains about Virtual Box Guest addtions
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/communicators/ssh/communicator.rb:257:in `execute': Vagrant was unable to mount VirtualBox shared folders. This is usually (Vagrant::Errors::VirtualBoxMountFailed)
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
Did this happen to all of you? If not it might well and here is the solution to it.
https://github.com/dotless-de/vagrant-vbguest/issues/292
Thank you DuckDuckGo ;-p
maximilian1st
2019-11-15, 10:56
Next issue I found while the script is patching:
$ vagrant ssh -c "/vagrant/patch.sh -a f5321 -i /vagrant/Sailfish*.zip"
W: You must be root to use this script! Trying with sudo...
I: Unzipping the Sailfish X archive
Archive: /vagrant/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15.zip
creating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/Jolla-3.2.0.12-f5121-armv7hl.urls
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/AdbWinUsbApi.dll
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flash-on-windows.bat
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fastboot.exe
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flash.sh
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/md5.lst
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hw-release
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fastboot.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hybris-boot.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/hybris-recovery.img
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/flashing-README.txt
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/AdbWinApi.dll
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/fimage.img001
inflating: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/os-release
I: Converting the fimage sparse image to a raw image...
I: Copying the fimage contents
'/tmp/sailfish-image-patcher/tmp.BwT0WHatci/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/home.img.gz' -> 'patcher-tmp/work/fimage/home.img.gz'
'/tmp/sailfish-image-patcher/tmp.BwT0WHatci/Sailfish_OS-Jolla-3.2.0.12-f5121-0.2.1.15/root.img.gz' -> 'patcher-tmp/work/fimage/root.img.gz'
I: Uncompressing the contents
I: Copying the Sailfish root contents...
I: Preparing for the patch...
I: Patching the image...
DBus unavailable, falling back to libssu
DBus unavailable, falling back to libssu
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 490 0 --:--:-- --:--:-- --:--:-- 503
100 858k 100 858k 0 0 1291k 0 --:--:-- --:--:-- --:--:-- 6452k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 511 0 --:--:-- --:--:-- --:--:-- 525
100 449k 100 449k 0 0 727k 0 --:--:-- --:--:-- --:--:-- 727k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 154 100 154 0 0 508 0 --:--:-- --:--:-- --:--:-- 522
100 1121k 100 1121k 0 0 1581k 0 --:--:-- --:--:-- --:--:-- 1581k
warning: ./augeas-libs.rpm: Header V3 DSA/SHA1 Signature, key ID f2633ee0: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:augeas-libs-1.6.0+git1-1.2.8.joll################################# [ 50%]
2:zypper-1.14.6+git3-1.3.8.jolla ################################# [100%]
Retrieving repository 'tmp-compat-f5321' metadata .................................................. .................................................. ............................................[done]
Building repository 'tmp-compat-f5321' cache .................................................. .................................................. .................................................[done]
Specified repositories have been refreshed.
Retrieving repository 'jolla' metadata .................................................. .................................................. .................................................. .....[done]
Building repository 'jolla' cache .................................................. .................................................. .................................................. ..........[done]
Specified repositories have been refreshed.
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation0' because of the above error.
Error building the cache:
[adaptation1|plugin:/ssu?repo=adaptation1] Valid metadata not found at specified URL
Warning: Skipping repository 'adaptation1' because of the above error.
Error building the cache:
[aliendalvik|plugin:/ssu?repo=aliendalvik] Valid metadata not found at specified URL
Warning: Skipping repository 'aliendalvik' because of the above error.
Building repository 'apps' cache .................................................. .................................................. .................................................. ...........[done]
Building repository 'customer-jolla' cache .................................................. .................................................. .................................................. .[done]
Building repository 'hotfixes' cache .................................................. .................................................. .................................................. .......[done]
Building repository 'jolla' cache .................................................. .................................................. .................................................. ..........[done]
Error building the cache:
[sailfish-eas|plugin:/ssu?repo=sailfish-eas] Valid metadata not found at specified URL
Warning: Skipping repository 'sailfish-eas' because of the above error.
Building repository 'tmp-compat-f5321' cache .................................................. .................................................. .................................................[done]
Error building the cache:
[xt9|plugin:/ssu?repo=xt9] Valid metadata not found at specified URL
Warning: Skipping repository 'xt9' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 18 NEW packages are going to be installed:
droid-compat-f5321-droid-config droid-compat-f5321-droid-config-flashing droid-compat-f5321-droid-config-sailfish droid-compat-f5321-droid-hal droid-compat-f5321-droid-system
droid-compat-f5321-feature droid-compat-f5321-hybris-libsensorfw-qt5 droid-devicetree-f5321 libpython3_7m1_0 python3-base rpm-divert sailfish-content-graphics-closed-z1.25
sailfish-content-graphics-default-z1.25-base sailfish-device-encryption-unlock-ui-resources-z1.25 sailfish-minui-resources-z1.25 sailfish-upgrade-ui-resources-logo-z1.25
sailfish-upgrade-ui-resources-z1.25 yabit
The following NEW pattern is going to be installed:
droid-compat-f5321
18 new packages to install.
The script does finish and there is a slightly smaller patched image created. Not sure if it will work as the errors seem to be about the proprietary parts of Sailfish.
"Since we don't support your device, we cannot transfer your licence as it won't give you any Android support or other licensed benefits."
ughhhhhh. if you had just given them the IMEI without telling them the model they likely would have done it and it would have worked.
i assure you that i have a working llicense on two xperia x compacts, with official android support downloaded directly the jolla store, and predictive text, etc, AND official OTA updates (which do NOT work anymore if you dont have the license)
ooh, try this: "can you remove the IMEI from my account? im going to switch to a new xperia x, but i dont have the IMEI yet and i want it to work right away"
and then install it on an x compact and it might work!
(also, if you buy a second license, it will work as soon as you flash)
BARRING THAT, you can just download the aliendalvik RPM on your xperia X with pkcon, copy it to your xc, and use it.
maximilian1st
2019-11-17, 11:56
Hey Wolke, thank you for your answer. I had a mail back from Jolla confirming the licence is freed from my broken Xperia X as I asked them to do. Either way, I might as well sell this X Compact for 30€ and buy another X Compact as the microphone is rubbish and people on the other end complain they don't hear me. Tried myself with the *#*#service#*#* microphone test and can confirm it is malfunctioning. Could have been mentioned in the eBay listing.
SFOS 3.2.1.19 updated with OTA, no issues. :)
aspergerguy
2019-12-26, 18:55
Just to mention no problems using g7 patcher with latest Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27.zip
I: Creating an empty root image
1821+0 records in
1821+0 records out
1909456896 bytes (1.9 GB, 1.8 GiB) copied, 1.26998 s, 1.5 GB/s
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: done
Creating filesystem with 466176 4k blocks and 116640 inodes
Filesystem UUID: 8a9da342-263a-40ee-9483-daae54cc36df
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
I: Syncing back the patched tree
I: Repacking
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27
0+0 records in
0+0 records out
0 bytes copied, 0.000848465 s, 0.0 kB/s
Physical volume "/dev/loop0" successfully created.
Volume group "sailfish" successfully created
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/loop1: 24286/116640 files (0.1% non-contiguous), 264455/466176 blocks
We got ourselves root blocks _ 398302 _
after maths size _ 1631444992 _
Rounding up size to full physical extent 1.52 GiB
Logical volume "root" created.
1 logical volume(s) in volume group "sailfish" now active
398302+0 records in
398302+0 records out
1631444992 bytes (1.6 GB, 1.5 GiB) copied, 12.8736 s, 127 MB/s
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
home: 83/7328 files (7.2% non-contiguous), 13309/16222 blocks
We got ourselves home size _ 13314 _
Rounding up size to full physical extent 56.00 MiB
Logical volume "home" created.
2 logical volume(s) in volume group "sailfish" now active
13314+0 records in
13314+0 records out
54534144 bytes (55 MB, 52 MiB) copied, 0.320027 s, 170 MB/s
0 logical volume(s) in volume group "sailfish" now active
1+0 records in
1+0 records out
1 byte copied, 0.000580506 s, 1.7 kB/s
mke2fs 1.43.4 (31-Jan-2017)
Discarding device blocks: done
Creating filesystem with 341796 4k blocks and 85536 inodes
Filesystem UUID: 00435d11-5b24-4102-b290-ab612c05807c
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
fimage.img: 11/85536 files (0.0% non-contiguous), 14574/341796 blocks
resize2fs 1.43.4 (31-Jan-2017)
The filesystem is already 341796 (4k) blocks long. Nothing to do!
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
fimage.img: 16/85536 files (6.3% non-contiguous), 130960/341796 blocks
resize2fs 1.43.4 (31-Jan-2017)
Resizing the filesystem on fimage.img to 197441 (4k) blocks.
The filesystem on fimage.img is now 197441 (4k) blocks long.
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/ (stored 0%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/sailfish.img001 (deflated 55%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/hybris-recovery.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fastboot.img (deflated 3%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/AdbWinUsbApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fastboot.exe (deflated 67%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/fimage.img001 (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/Jolla-3.2.1.20-f5121-armv7hl.urls (deflated 92%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flash-on-windows.bat (deflated 63%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/hybris-boot.img (deflated 2%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/md5.lst (deflated 35%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flashing-README.txt (deflated 59%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/AdbWinApi.dll (deflated 49%)
adding: Sailfish_OS-patched-for-f5321-3.2.1.20-f5321-0.2.1.27/flash.sh (deflated 57%)
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.2.1.20-f5121-0.2.1.27
I: Done! Enjoy!
I: Cleaning up...
Connection to 127.0.0.1 closed.
iMac:sailfishx-patcher-f5321 adrian$
willi.liebig
2020-02-04, 15:36
hi, I have the same trouble as post 106 ... after cloning of the git repository (git clone https://github.com/g7/sailfishx-patcher-f5321.git) the folder "droid-config-f5121" is still empty, even when I manually download the patcher. Is this a bug or how can I manage to get all files downloaded?
Will
its a submodule. from the readme:
git clone https://github.com/g7/sailfishx-patcher-f5321.git
cd sailfishx-patcher-f5321
git submodule init
git submodule update
willi.liebig
2020-02-04, 19:17
hi, mh, there are still some errors. Is there a possiblity to download the patched zip-file anywhere?
SFOS 3.3.0.14 updated without issues on g7's hack image.
Also enabling the encryption worked. I had all kinds of issues in restoring existing data from the GUI based backup after the encryption, so prepare well with external backups if you do this.
Scratch that what I said above. Either after the upgrade _or_ after doing the encryption, leds and sound stopped working. So upgrade only if you dare.
Scratch that what I said above. Either after the upgrade _or_ after doing the encryption, leds and sound stopped working. So upgrade only if you dare.
What's the output of
systemctl --user status pulseaudio
Have you tried running the upgrade again via command line?
devel-su
ssu re 3.3.0.14
version --dup
FWIW my X Compact works fine, even though the upgrade failed mid-way (but it doesn't seem related to the patch).
I also have encryption enabled, but since 3.2.0.
========================
EDIT: Now that I remember, I had to mask pulseaudio's system wide service after enabling encryption back then. Pulseaudio is normally started in the user session, but after encryption is enabled is started system-wide so that it's possible to route audio when taking emergency calls from the encryption unlock screen (I guess).
Not sure what is wrong, I thought it was due to encryption being a work in progress on 3.2.0 so I haven't complained :) But it seems to be an issue on 3.3.0 too, then.
You can mask pulseaudio using this command:
systemctl mask pulseaudio
Thanks Eugenio! I was bit too fast...
I got the issue fixed by doing a factory reset, and upgrading from there back to latest. After enabling encryption again I didn't have issues anymore.
I tried 'version --dup' just before resulting to factory reset, but all packages were up to date.
In addition to sound I also had issues with the LED. Csd tests showed that the led still worked, just it did not get triggered in the events with text messages, calls etc.
I also noticed also that any pull menus that normally would have sound to them didn't trigger haptic feedback (haptic was fine with virtual keyboards). Both of these issues may be connected to pulseaudio and order in which SFOS expects things to happen.
So I think your suggestion would have worked.
Well, at least the factory reset has now been tested and working! :)
hmm, cant create a g7 image for rokua
keep getting:
error: Failed dependencies: libreadline.so.8 is needed by zypper-1.14.6+git4-1.5.1.jolla.armv7hl
trying to messing with the inner chroot patch file and not having much luck
previous problem had an easy solution (just install readline rpm).
now ive got another problem. inner patch seems to apply correctly in chroot, but repacking the image files fails.
(note that the zip file is built, but is only half the size of the source zip file)
I: Syncing back the patched tree
I: Repacking
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25
0+0 records in
0+0 records out
0 bytes copied, 0.000164125 s, 0.0 kB/s
Physical volume "/dev/loop0" successfully created.
Volume group "sailfish" successfully created
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/loop1: 25063/116640 files (0.1% non-contiguous), 264442/466176 blocks
We got ourselves root blocks _ 398289 _
after maths size _ 1631391744 _
Rounding up size to full physical extent 1.52 GiB
Logical volume "root" created.
1 logical volume(s) in volume group "sailfish" now active
398289+0 records in
398289+0 records out
1631391744 bytes (1.6 GB, 1.5 GiB) copied, 7.78859 s, 209 MB/s
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
home: 83/7328 files (3.6% non-contiguous), 13285/16198 blocks
We got ourselves home size _ 13290 _
Rounding up size to full physical extent 52.00 MiB
Logical volume "home" created.
2 logical volume(s) in volume group "sailfish" now active
13290+0 records in
13290+0 records out
54435840 bytes (54 MB, 52 MiB) copied, 0.163591 s, 333 MB/s
0 logical volume(s) in volume group "sailfish" now active
1+0 records in
1+0 records out
1 byte copied, 0.00015447 s, 6.5 kB/s
Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G flex-group-size] [-N number-of-inodes] [-d root-directory]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file]
[-jnqvDFSV] device [blocks-count]
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
umount: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX: not mounted
rmdir: failed to remove '/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX': Directory not empty
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
ok fixed it, see https://github.com/g7/sailfishx-patcher-f5321/pull/14
Hey guys I need some help if possible.
I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.
Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2020-05-02.log.html
respectively:
https://build.merproject.org/project/show/home:vknecht:hw:qualcomm:f5121
also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project/show/home:vknecht:hw:sony:loire
because of:
https://github.com/sonyxperiadev/device-sony-loire/commit/75811b2c2d85cc8147e1b4d6b29d22bfb5ac2c84#diff-bfe4388236c79fe44d6c494ecad6875e
I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.
Sheigorath
2020-09-21, 20:02
Hey guys I need some help if possible.
I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.
Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2020-05-02.log.html
respectively:
https://build.merproject.org/project/show/home:vknecht:hw:qualcomm:f5121
also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project/show/home:vknecht:hw:sony:loire
because of:
https://github.com/sonyxperiadev/device-sony-loire/commit/75811b2c2d85cc8147e1b4d6b29d22bfb5ac2c84#diff-bfe4388236c79fe44d6c494ecad6875e
I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.
Is there any news about new ports for Compact?
I updated Eugenio's (g7) port to 3.4.0.22 on X Compact. No issues spotted.
smatkovi
2020-10-21, 19:50
this should be the solution, at least it helped on my mothers xperia x compact https://together.jolla.com/question/197811/35mm-audio-connector-not-working-on-xa2/?answer=199698#post-id-199698
What's the output of
systemctl --user status pulseaudio
Have you tried running the upgrade again via command line?
devel-su
ssu re 3.3.0.14
version --dup
FWIW my X Compact works fine, even though the upgrade failed mid-way (but it doesn't seem related to the patch).
I also have encryption enabled, but since 3.2.0.
========================
EDIT: Now that I remember, I had to mask pulseaudio's system wide service after enabling encryption back then. Pulseaudio is normally started in the user session, but after encryption is enabled is started system-wide so that it's possible to route audio when taking emergency calls from the encryption unlock screen (I guess).
Not sure what is wrong, I thought it was due to encryption being a work in progress on 3.2.0 so I haven't complained :) But it seems to be an issue on 3.3.0 too, then.
You can mask pulseaudio using this command:
systemctl mask pulseaudio
aspergerguy
2021-05-31, 13:21
I updated Eugenio's (g7) port to 4.1.0.24 on Xperia X Compact. Have not encrypted as a backup device and yet to check notification LED and audio.
maximilian1st
2021-05-31, 18:36
I have the Xperia X Compact as a daily driver since quite some time and did the patch thing before version 3.4. Since then, I just update OTA and it still works the same as it did with the first flashed patched version.
I don't care about the android layer anymore, not really using it. Only for Ankidroid ;-p But I would miss the text prediction as presage has no French version or Dutch. And honestly I read the howto make it yourself and I still don't know where to start
Funny thing is the Xperia 10 II is about the same width as the X Compact but way too tall. Small phones are not trendy these days.
https://www.phonearena.com/phones/size/Sony-Xperia-X-Compact,Sony-Xperia-10-II/phones/10217,11367
I remember Casio or Panasonic had a 2G credit card size phone at some point. thought that was a very cool device at the time.
Smartwatches will probably be the future of phones with a mini tablet as second device.
That was way off topic, sorry ;-p
aspergerguy
2021-06-01, 06:30
Funny thing is the Xperia 10 II is about the same width as the X Compact but way too tall. Small phones are not trendy these days.
Although running community port by rinigus the XZ2 Compact is very similar in size to Xperia X Compact.
aspergerguy
2022-03-17, 19:24
I have the Xperia X Compact as a daily driver since quite some time and did the patch thing before version 3.4. Since then, I just update OTA and it still works the same as it did with the first flashed patched version.
And honestly I read the howto make it yourself and I still don't know where to start
Just to say that with g7 patch still updates to 4.2.0.21 (using terminal and sfos-upgrade) and can still build latest Sailfish_OS-patched-for-f5321-4.3.0.15-f5321-0.2.3.9 with one caveat. Whilst I am essentially a Mac user OSX Monterey doesn't sit happy with VirtualBox without a bit of tinkering, but got there eventually.:)
aspergerguy
2024-09-22, 14:07
Just a final word of thanks to g7 whom has now moved on to other projects, but has ensured that patch still works to compile the final version of Sailfish 4.6.0.15 for F5321 Xperia X Compact. :)
monkeyisland
2024-09-25, 09:32
can you evtl load it up somewhere ?
aspergerguy
2024-09-26, 18:28
can you evtl load it up somewhere ?
Have sent you a link via PM, but can't leave it there more than a few days due to space constraints.
vBulletin® v3.8.8, Copyright ©2000-2025, vBulletin Solutions, Inc.