Ask / Submit
80

[Announcement] Community Sony Xperia X Compact release

asked 2018-02-27 00:38:26 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2018-03-09 13:52:26 +0300

steph gravatar image

[notice] to work around the sensors issue I have release a different image with working gyro/light/proximity. The link has been amended, and the new image has the tag 'sg01'

Ahoy!

I'm happy to announce the first community build of SailfishOS 2.1.3 built upon community infrastructure for the Sony Xperia X Compact (f5321/kugo).

Many, many thanks to the porting community, sailors, private testers, the Sony Open Devices team but most of all to Manizuca upon whose device adaptation work this is based.

Requirements:

  • Sony Xperia X Compact (f5321) upgraded to the latest Android 6 or 7 before unlocking the bootloader. This is a critical step. Attempting to flash without upgraded firmware may brick your device
  • Download and unzip the archive here, and follow the instructions therein. They are the same as per the Xperia X Community build. For specific instructions on installing under Windows, see this XDA post

What works:

  • everything that works in the community port of the Xperia X

What isn't working:

  • everything that doesn't work on the community port of the Xperia X
  • OTA updates. If you flash this image to your device you will need to manually upgrade via the command line, and currently even that may not work. Although feature complete, this is a work-in-progress.
edit retag flag offensive close delete

Comments

4

Thanks a lot @steph! It's much appreciated! My X Compact still lies unboxed, waiting to be liberated from Android. :)

luen ( 2018-02-27 00:48:52 +0300 )edit
1

upgrade it first!

steph ( 2018-02-27 01:02:36 +0300 )edit
2

Yep, will start right away!

luen ( 2018-02-27 01:06:36 +0300 )edit
3

@steph this is really great, that you make this "officially" available now. I'm still running your build from November. Will this version here fix the gps issue? Is it save to install this version over the current one (2.1.3.5) I use?

naytsyrhc ( 2018-02-27 01:09:36 +0300 )edit
3

Sir, you are absolutely awesome, many thanks for your hard work

figgis-diggis ( 2018-02-27 09:57:46 +0300 )edit

11 Answers

Sort by » oldest newest most voted
11

answered 2018-02-28 10:12:40 +0300

steph gravatar image

updated 2018-02-28 10:17:21 +0300

Hi all,

I have updated the download link on the post to a new link with working sensors. Please all use that, I suggest you reflash completely as I do not know how many of the packages are broken for sensors. Sailfish can be flashed over itself without needed to restore stock android first. If you have already started to use your X Compact with this image you can back up settings either with the backup app in settings or from the shell with cp/rsync/tar etc.

In the mean time I am going to start work making sure that the same thing does not happen with the 2.1.4 build.

Apologies all for the inconvenience!

edit flag offensive delete publish link more

Comments

2

@steph Thank you very much for the port, the Compact would be the perfect successor for my Jolla1! I have a few questions about the port: Does the X Compact with sailfish have similar problems with partitioning as they are reported about the Xperia X ? (Big hidden partition for recovery, too small partition for the system which makes updates difficult). Can you estimate if and when OTA updates will be possible? If Jolla creates a graphical interface for installing SailfishX, can it be used to flash your image on the compact?

pvcn ( 2018-02-28 10:45:55 +0300 )edit
2

1) hadn't heard of any problems with the X (and have had an X since launch and have no issues with it) but I haven't made any other changes so I expect it behaves exactly as the X. If you want to alter partition sizes you can build yourself of course, this is the community build ;) 2) for OTA should hopefully be days/weeks (if all goes well) but probably weeks/a month or two 3) I don't know, I don't know how that will work.

steph ( 2018-02-28 11:49:46 +0300 )edit
2

@steph Thanks for your instant answers! My question about partitioning refers to this post: https://together.jolla.com/question/171437/what-bugs-does-sailfish-x-have/?answer=173292#post-id-173292 Can't confirm it myself since i still use jolla1. Hope i will be able to use your build soon, as an non-technie i will wait and hope for an easy way to install it with ota-updates . best regards and again thanks for bringing sailfish to a compact device!

pvcn ( 2018-02-28 21:26:46 +0300 )edit
4

answered 2018-03-21 01:42:03 +0300

Xeno_PL gravatar image

Is it me, or dynamic brightness has very little effect on Xperia X Compact? I've made sure light sensor works (confirmed with csd tool), but screen brightness is about the same regardelss of light sensor being covered or exposed to direct light.

Can any owners of regular Xperia X confirm screen brightess adjusts according to output from light sensor?

edit flag offensive delete publish link more

Comments

1

Automatic adjusting don't work for me.

Oleg ( 2018-03-21 07:28:31 +0300 )edit
1

Yes, auto brightness works on regular Xperia X but not on Compact.

Manatus ( 2018-03-21 08:27:28 +0300 )edit
1

I've tried to take a look at this issue, with Elros help (many thanks again) i found out that mce doesn't receive proper values from ALS. Logs of brightness_filter_als module are floded with lines:

modules/filter-brightness-als.c: fba_status_sensor_value_change_cb(): sensor: 0

when phone is in direct light It seems it should get some values from /dev/input/event0 (Name: "AMS TCS3490 Sensor") I've tried to cat this device but no output was shown regardless of changes in ambiet light.

If someone more skilled with Sailfish ports have any ideas how to debug it further, any help would be welcome.

Xeno_PL ( 2018-03-22 00:10:57 +0300 )edit
5

Adaptive brighness quick fix: in terminal

 devel-su
printf > /etc/mce/99-blacklist-tcs3490.ini "[evdev]\nblack=AMS TCS3490 Sensor;\n"
systemctl restart mce

It blacklist false als from mce so mce uses the one that works. Many thanks to spiirion, without his help i'd never found it out.

Xeno_PL ( 2018-03-22 15:03:28 +0300 )edit

@Xeno_PL Respect. Works! :)

Manatus ( 2018-03-22 18:15:22 +0300 )edit
3

answered 2018-06-09 14:53:23 +0300

notthebee gravatar image

updated 2018-06-09 18:59:24 +0300

First of all, massive thanks to the developers for making it possible!

I've been using the build for a few days, so in case anyone is interested, here's my little review of it (installation, patches, Android apps, etc.):

https://www.youtube.com/watch?v=sIO36VRB-dw

edit flag offensive delete publish link more

Comments

@vattuvarg thanks! corrected the link

notthebee ( 2018-06-09 19:00:09 +0300 )edit

@notthebee - Pretty good video. Thanks.

vattuvarg ( 2018-06-09 19:03:11 +0300 )edit
2

answered 2018-02-28 09:39:41 +0300

Cavalier gravatar image

Steph, Gyro/accelerometer and proximity sensors do not work. Do you know how to repair them?

edit flag offensive delete publish link more

Comments

2

I will be looking at that today. They work in the local build so shouldn't be too long.

steph ( 2018-02-28 09:45:54 +0300 )edit
2

answered 2018-03-01 10:43:52 +0300

romu70 gravatar image

Thanks a lot Steph.

I've listed some tweaks here : https://talk.maemo.org/showthread.php?t=100227

I've also tried the OTA update procedure described in the X Community Build thread. It works...almost. Everything seems ok during the update. But at reboot, the phone stays lock on the Sony screen.

The good news is it remains reachable through SSH, so maybe things are not so difficult to get OTA but I'm far from being an expert.

edit flag offensive delete publish link more
1

answered 2018-02-27 12:27:28 +0300

Cavalier gravatar image

Thank you, Steph! My phone already has been upgraded to Android 8. Is it possible to install sailfish os on it? Or I have to downgrade to 7 version?

edit flag offensive delete publish link more

Comments

It is not known yet. I asked basically the same question for Xperia X, please see https://together.jolla.com/question/180135/sony-xperia-x-and-android-8/

Direc ( 2018-02-27 12:30:22 +0300 )edit

I don't know but I expect it should be ok to flash SFOS over Android 8. If in doubt, backup, backup again and ideally have a Windows machine with a copy of EMMA about.

steph ( 2018-02-27 12:34:56 +0300 )edit

I think you can pretty easily downgrade using the flashtool and xperifirm. And then run sailfish.... http://www.flashtool.net/downloads.php

bertjefred ( 2018-02-27 13:05:17 +0300 )edit
1

At least one user (can't remember where I saw it) said that installing Sailfish X on top of Android 8 went just fine, and it runs well, too.

Direc ( 2018-03-03 11:53:34 +0300 )edit
1

Here, SFX flashed over 8.0.0, worked as advertised.

Xeno_PL ( 2018-03-21 12:40:31 +0300 )edit
1

answered 2018-04-09 21:39:06 +0300

KingofBrixton gravatar image

First of all, thank you very much for the build and your effort, steph.

On my compactX I have a minor problem though, there is no sound and pulseaudio fails to start:

systemd[2591]: pulseaudio.service: Service hold-off time over, scheduling restart. pulseaudio[5942]: Default and alternate sample rates are the same. pulseaudio[5942]: Default and alternate sample rates are the same. pulseaudio[5942]: Default and alternate sample rates are the same. pulseaudio[5942]: Default and alternate sample rates are the same. pulseaudio[5942]: Failed to open module /usr/lib/pulse-8.0/modules/module-policy-enforcement.so: /usr/lib/pulse-8.0/modules/module-policy-enforcement.so: undefined symbol: pa_shared_data_inc_integer pulseaudio[5942]: Failed to open module "module-policy-enforcement". pulseaudio[5942]: Module load failed. pulseaudio[5942]: Konnte Daemon nicht initialisieren. pulseaudio[5942]: Assertion 'pa_atomic_load(&(c)->_ref) > 0' failed at pulsecore/dbus-shared.c:76, function pa_dbus_connection_get(). Aborting. pulseaudio[5938]: E: [pulseaudio] main.c: Start des Daemons fehlgeschlagen. systemd[2591]: pulseaudio.service: Control process exited, code=exited status=1

If I comment out the following line

load-module module-policy-enforcement

from

/etc/pulse/arm_droid_default.pa

pulseaudio will start and I got sound in browser and system but not during a phonecall (neither microphone).

I tried to reinstall pulseaudio via pkcon and delete the config files (/home/nemo/.config/pulse) but it won't help. Any ideas are appreciated.

edit flag offensive delete publish link more
1

answered 2018-06-05 08:55:33 +0300

Matty gravatar image

Hello, Thank you very much for that build. I have installed Sailfish on my Xperia Compact and it was quite easy :)

Unfortunately i cannot install any APK files and i do not see android service in the jolla store. Could you guide me through how to enable the Android app support. Also the Killdroid, which seems to be the only app i can install that does have to do with android, says "error starting android service"

Kind Regards Matthias

edit flag offensive delete publish link more

Comments

Community ports like this one have no support for running Android apps via AlienDalvik. This is one of the features of offcial ports made by Jolla. Some users reported that aliendalvik installed from sailfish X rpms works fine.

Xeno_PL ( 2018-06-05 09:56:46 +0300 )edit

Hello Xeno_PL

Thanks for your answer. So the Jolla Store apps are all apps i can use with the community port? I would have also taken the official port, but as far as i know there is none for the xperia x compact, right? Is there a way to get the official one to the compact?

Kind Regards Matthias

Matty ( 2018-06-05 10:12:56 +0300 )edit

@Matty there is no way to get official port for X Compact. On Community port you can install apps from Jolla store and from https://openrepos.net/ (you can install apps from openrepos throught https://openrepos.net/content/osetr/storeman

atlochowski ( 2018-06-05 11:24:43 +0300 )edit
1

You can install Android support on Xperia X Compact if you have an officially purchased image for Xperia X and if you copy the RPMs from the installation. See my comment to my answer here. I have not tested it though and please note that it is most probably not legally allowed. If we are lucky, the Xperia X Compact will be the next in row of officially supported by Jolla now that the Dual Sim got its support.

naytsyrhc ( 2018-06-05 11:33:57 +0300 )edit

The next device will be the XA2.

I dont think Xperia X compact will be supported by Jolla.

makarch ( 2018-06-06 13:49:05 +0300 )edit
0

answered 2018-02-27 21:09:05 +0300

meinlieberjolli gravatar image

Already gotta unlocked device with Paranoid Android (twrp) on it. Android version is 7.1.2. Safe to switch to Sailfish OS?

edit flag offensive delete publish link more

Comments

1

Provided the bootloader had been upgraded to greater than 34.3 before you flashed twrp it should just work. I would flash stock android back to it first to be safe however.

steph ( 2018-02-28 09:11:58 +0300 )edit

Thanks.

Is there a way to backup my current system? I'd like to have my Android system as a save haven.. When I install Sailfish OS twrp gets lost?

meinlieberjolli ( 2018-02-28 10:02:35 +0300 )edit
1

You should install one of the backup apps to get things backed up before you attempt the upgrade. I suggest flashing back to stock (ideally using the official tools) as I do not know how twrp will behave with SFOS.

steph ( 2018-02-28 10:06:10 +0300 )edit
0

answered 2018-02-28 10:05:44 +0300

ming1 gravatar image

Hello, i cant Flash the Image. Can anybody help? I get this Message.

This is a Windows flashing script for Sony Xperia X Compact device.

Power on the device in fastboot mode, by doing the following: 1. Turn off your Xperia. 2. Connect one end of a USB cable to your PC. 3. While holding the volume up button pressed, connect the other end of the USB cable to your Xperia. 4. After this you should see the blue LED lit on Xperia, and it will be ready for flashing

Drücken Sie eine beliebige Taste . . . MD5SUM 'ed5a809dc0024d83cbab4fb9933d598d' match for file 'AdbWinApi.dll'. MD5SUM '0e24119daf1909e398fa1850b6112077' match for file 'AdbWinUsbApi.dll'. MD5SUM 'c980ea6caa9140ee3f30cdc0e98844c4' match for file 'fastboot.exe'. MD5SUM '15bb5806375af0b7f031cbcbea84cf12' match for file 'flash-on-windows.bat'.

Searching a device with vendor id '0x0fce'..

The device is unlocked for the flashing process. Continuing..

'34.3' is new enough to support vendor partition. Continuing.. "." kann syntaktisch an dieser Stelle nicht verarbeitet werden.

edit flag offensive delete publish link more

Comments

Hi

it appears that the hashes for the windows fastboot executable and library are out of date. I need to find more up-to-date versions for windows.

(also please download the working image here: https://futr.io/ipfs/QmTpoKtixjD7xMtVESh96ZzFHhSJLG3DtM5NRrnezSa85a/)

steph ( 2018-02-28 10:12:17 +0300 )edit

Hi,

downloaded the Image from: https://futr.io/ipfs/QmTpoKtixjD7xMtVESh96ZzFHhSJLG3DtM5NRrnezSa85a/. Thats not the problem,maybe the Fastboot it is.

ming1 ( 2018-02-28 10:18:36 +0300 )edit

Hi ming1, yes the issue is with the fastboot.exe and DLL that are bundled with the zip file, and that they changed versions somewhere along the line. I need to do some research but you should be able to download both as per for the Xperia X and comment out the md5sum line in the batch file and you should be able to flash.

steph ( 2018-02-28 10:38:51 +0300 )edit

Thanks for the help. I will try it ;-)

ming1 ( 2018-02-28 10:45:55 +0300 )edit
1

Flashing Completed under Virtual Box (Ubuntu). with windows doest´n work. So i´m happy

ming1 ( 2018-02-28 15:58:58 +0300 )edit
Login/Signup to Answer

Question tools

Follow
26 followers

Stats

Asked: 2018-02-27 00:38:26 +0300

Seen: 8,721 times

Last updated: Jun 09