Thread Tools
Posts: 70 | Thanked: 90 times | Joined on Feb 2015
Originally Posted by alfmar View Post
My home wifi AP uses channel #13 and SailfishX has no problems connecting. The command iw phy phy0 info on SailfishX says that only 2484 MHz (channel 14) is actually "disabled" (because of the "global" and "Italy" regulatory domains; AFAIK channel 14 is only available in "Japan" regulations), and 5 GHz channels 36 to 140 (5.18 to 5.7 GHz) are also available.

In the "valid interfaces combinations" it clearly shows that "AP" and "Managed" are separate features, thus the hardware does not support being both an access point and a client at the same time.

Using the command iw dev wlan0 link on SailfishX I can see it is now using the channel 13 (frequency 2472 MHz) at 72 MBit/s speed.
Thank you for the information.

Running iw phy phy0 info gives:

	Band 1: 
[. . .]
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
Is there any way to enable channel 12 and 13? The firmware flashed to bring the device up to 34.3 version was the Central Europe 1 version, so channel 12 and 13 should not be restricted in those regions, and yet it is. Or does Sailfish restrict it based on the timezone or IMSI?

iw reg set [2 letter country code, eg BE, DK, RU, AU, etc] works but does not survive reboot and it changes back to the original settings.

Further testing seems to show that dead SIMs from a variety of countries do not change the regulation setting, while live SIMs do, and the reg setting is changed to the country of the connected network. One wonders what happens on the Xperia dual-SIM version if one is using two different SIMs in a border area, eg, Uzbekistan (1 - 11) and Kazakhstan (1 - 13).

Last edited by oenone; Today at 16:25.

The Following User Says Thank You to oenone For This Useful Post:
Posts: 155 | Thanked: 517 times | Joined on Sep 2009 @ Hampshire, UK
I just realised my X has been quiet all day despite emails arriving...

A quick check shows no sound output at all. Checked volume in settings, ambiences and from the volume key.

I saw this previously on the community build, but this is the first time it's happened since the official build arrived.

I use sailcron to switch to a silent ambience overnight and back to a noisy one in the morning. It certainly switched back to 'noisy', and the 'muted' icon wasn't shown.

Back to normal after a reboot.

Next time I will check the phone audio, and anything else I can think of. Anyone had anything similar?

The Following 3 Users Say Thank You to epninety For This Useful Post:
Posts: 76 | Thanked: 322 times | Joined on Mar 2010 @ southern Italy
Hmm... this is too funny to not to mention it here.

After exporting contacts using vcardconverter, I also exported the entire database of calls and SMS messages from old Jolla phone (now without SIM) to Xperia X.

First, export message groups and phone calls lists to a binary file: log in via ssh on Jolla and execute:
commhistory-tool export -groups -calls mystuff
then move that binary file to Xperia X and execute:
commhistory-tool import ./mystuff
(you can safely ignore the bunch of warnings).

and everything gets in place and sorted by date, no UTF8 characters lost, added to the already existing recent calls and SMS text messages in its database.

The Following 4 Users Say Thank You to alfmar For This Useful Post:
Posts: 138 | Thanked: 603 times | Joined on Dec 2014 @ Earth
Originally Posted by rfa View Post
Turning this off hasn't worked. I'm going to try again on a different computer on the weekend.
Do you get to fastmode ?
(Turn off, hold volume up, insert USB cable, the phone turns on, the screen stays black and the LED eventually shine blue. The blue color is important).

I'll try without using the Sony software, as I think this is causing the problem
Normally you shouldn't need to use Emma - the sony software.
It's only used to flash official Sony firmware (e.g.: upgrading to "Central Europe 34.3.a.0.238").

And even if you need to downgrade/upgrade firmware, I would definitely recommend using instead.

Originally Posted by pexi View Post
Linux went without a glitch for me. Just had to install the android tools with a single command, turn off phone, plug it in while pressing volume up (or was it down for fastboot mode?), checking fastboot devices and proceeding from there with flashtool... if i recall correctly.
For the record :

- Volume Up : is for (Android standard) fastboot mode, and gives you a blue LED with a black screen.
That also allows you to unlock the bootloader to accept non-Sony-signed firmware (e.g.: SFOX or custom Android ROMs).

If you still run the stock Sony :

- Volume Down : is for the proprietary Sony flash mode, and gives you a green LED with a black screen.
You can use Sony's official Emma tool for Windows, or the cross-platform Flashtool to upgrade or downgrade firmwares.

If you've unlocked the bootloader and installer an Android recovery firmware (e.g.: TWRP, ClockWorkMod, etc.)

- Volume Down : is for recovery mod, and gives you a green LED with a menu on the screen (either touch screen, or using only the volume buttons for up/down, depending on the exact firmware installed).
It enables you to install firmware using ZIP files on the SDCard.

If you've unlocked the bootloader and installed the optionnal Jolla recovery firmware :
- Volume Down : is for recovery firmware, and gives you a green LED with a screen showing instruction to use telnet to connect to the Phone.
The actual recovery menu is visible on telnet.
(Pro tip : If you're on a Jolla 1 phone - DO NOT use the btrfs recovery)
Using the shell you can do pretty much anything.

Originally Posted by gaelic View Post
For me the lowest volume setting is to loud, and high volume way too high an massively cracking, I guess on the long run it would destroy the speakers.
I would suspect a bug in pulseaudio having an abronally high volume level. (In that situation, the cracking is software audio clipping, not destruction of the speakers)
(The speakers of nearly all smartphones are piezo anyway. They are solid-state).

Originally Posted by mosen View Post
Is the display brightness range the same on sfos as it is in android?
Booted the thing in android for the updates and found it is nicely dark on lowest setting. Unprecedented in sfos device i would say.
In Android, you usually set a brightness setting, and that's it.
In Sailfish OS, you generally set a desired brightness and the phone will play with it's actual brightness settings, based on the light sensors.
(The end result might end up being brighter or darker depending on ambient light).

Originally Posted by rogger888 View Post
I just want to say thank you to all those who helped me
Happy that as a community we managed to help eachother.

Last edited by DrYak; Today at 22:18.

The Following 2 Users Say Thank You to DrYak For This Useful Post:
Posts: 139 | Thanked: 81 times | Joined on May 2010 @ Sunny Woollahra
My issues are all related to unlocking the bootloader... (I think) - I can't upload pictures @ work, so I'll type away below:


Rooting status: Bootloader unlock allowed: Yes

I'm running 34.3.A.0.238

Developer options: ON
OEM unlocking: ON
USB Debugging: ON
Verify apps over USB: ON

Select USB Configuration: MTP (Media Transfer Protocol)

Everything else (in developer options) is OFF

Location: OFF

Lock screen & security:
Protection by my Xperia: OFF (this was on previously)

Device administration:
Unknown sources: ON


From the Sony website (where the instructions don't match either the video or the links provided) I have searched elsewhere & downloaded (as shown on the Sony video) installer_r24.4.1-windows.exe

I've downloaded the fastboot driver

I've (eventually) got it running in Windows 8.1 (rebooted into Testmode & run unsigned driver, again these steps don't match the Sony steps in the video

I've got the CLI running

I've typed in fastboot devices

a code has returned (I don't have it in front of me)

I've then (from step 4/4 on the unlock your bootloader Sony website) entered (Copy pasted) the code

and FAILED is al that happens...
I think there should be another word for mondegreen
Posts: 216 | Thanked: 555 times | Joined on Jun 2010 @ USA
Originally Posted by rfa View Post

I've then (from step 4/4 on the unlock your bootloader Sony website) entered (Copy pasted) the code

and FAILED is al that happens...
Did you enter your IMEI at the Sony site, and are you certain that the code they gave you is pasted exactly in the fastboot command?
Sony Xperia X SFOS, Nokia N810

sailfish os, sony xperia x

Thread Tools

Forum Jump

All times are GMT. The time now is 23:43.