![]() |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
My problem is no sound from earpiece , but have sound from speaker or earplug
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
This is very annoying when I receive calling but no voice heard. I need plug in my earphone to talk that moment. The bugs occur randomly
|
Re: Sailfish OS (officially) on Sony Xperia devices
A headset needs to hijack the mic as well as the speaker so it's not the same as standard headphones.
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
I will disable it and see if the problem re-occurs. |
Re: Sailfish OS (officially) on Sony Xperia devices
Now just happened again...this time no sound from earpiece, speaker and earplug......I need reboot again. I have reboot many times in 1 day, very annoying
|
Re: Sailfish OS (officially) on Sony Xperia devices
Hi Guys!
Got my new nano-sim today. It doesn't work on my xperia. It ask for PIN, give it but i dont get any bars/network on it. The new nano-sim works fine with my N9 (with an adapter). Have used another nano-sim (different provider) for a day with no problems. But with my new nano-sim from my main provider it won't work. Any ideas? Cheers! |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
https://drive.google.com/open?id=1ZT...8Vdog16kKFFkIB https://drive.google.com/open?id=1Nn...zeMZMyimhQphi8 https://drive.google.com/open?id=19H...yZqMgNw4lhO4Tn |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Now I use my old SIM and haven't made any further testing with the new one. I activated the old SIM in Telia Finland web pages by myself. EDIT: Maybe you can find some help here: http://talk.maemo.org/showpost.php?p...postcount=1777 |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
EDIT: Looks like my phone is carrier locked. Tried many different SIMs. The seller of the phone lied to me about being carrier unlocked. Looks like i have to change carrier now... EDIT: You can unlock the carrier by going into service menu and enter a code you can buy online. But how do i access the service menu with SFOSX? Android is the *#*#7378432#*#* |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Can then either use prompted one or change to one of your own and save. |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Air plane mode? |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
But still locked to the carrier.... |
Re: Sailfish OS (officially) on Sony Xperia devices
Hi,
while eagerly waiting for a build for the X Compact, I wonder if I can update the phone the all new updates proposed by Sony without compromising a future SFOS flashing? Currently, I run Android 7.1.1 / Firmware: 34.3.A.0.238. Thanks. |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
got today the same issue. No network. Solution: Airplan Mode on/off.
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Code:
devel-su systemctl restart ofono.service |
Re: Sailfish OS (officially) on Sony Xperia devices
2.1.3.7 update overwrites /etc/ofono/ril_subscription.conf on F5122.
So you need to edit it again to have the phone functions working. |
Re: Sailfish OS (officially) on Sony Xperia devices
Some extra notes about reclaiming a few gigabytes disk space to add to root and/or home logical volumes:
Quote:
- only partitions 51 and 52 need to be touched for reclaiming some gigabytes for root and home logical volumes; - partition 51 (user partition) is managed by lvm (as a volume of 5298 blocks of 4Mb each, as of the devel-su vgdisplay command) as a volume labeled "sailfish" containing two ext4 partitions (/dev/sailfish/root and /dev/sailfish/home) that lvm can resize when not mounted (that is: early boot time) - partition 52 (factory reset image partition) is formatted as ext4 (even if not marked as such in the partition table) and contains ~600 Mb of data (actually only two compressed image files and md5sum files) - fdisk doesn't save changes until you explicitly command it. My assumptions: - future upgrades won't need to alter partition 52 contents (just verified the 2.1.3.7 doesn't touch the partition 52, see below); - thus that factory reset image only needs less than ~700 Mb, it shouldn't ever grow; - then we can delete/create/fill partition 52 at some higher startsector address (the last ~700 Mb of mmc storage) and make it again an ext4 containing the same factory reset image files - fdisk can delete/create partitions without altering disk contents (when you "delete partition 51", as long as you create again a partition 51 starting from the same startsector and at least as big as the former partition 51 before rebooting, you don't lose its data) - logical volume manager can resize its logical volumes without losing data (i.e., no need for a "partition resizer"). Risks: - until the unlikely event of getting a serial port console or a method to boot off microSD, messing with the boot sequence (kernel, boot partitions, etc) may brick the phone, because everything -including the factory reset option- depends on a bootable kernel accessing the right partitions containing the right data. If anything goes wrong while messing with fdisk and partition 51 and volume manager, the Xperia is probably bricked. I tried this before upgrading to 2.1.3.7: Code:
[nemo@Sailfish ~]$ devel-su |
Re: Sailfish OS (officially) on Sony Xperia devices
alfmar
I posted a manual to resize parts 51 and 52 somewhere here. Upgraded to 2.1.3.7 today - all good. Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
This is a huge benefit of this recovery implementation (easy to update files on a separate partitions) compared to the old one (basically unupdatable/hard to update BTRFS snapshots). Still even if they for example kept the last two recovery file versions around it's unlikely it would every use the full 7 GB available. |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
http://talk.maemo.org/showpost.php?p...postcount=2092 |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
It doesn't rely on data nor recovery partitions. You could nuke them and the recovery will still boot. (But you won't be able to use the "factory reset" entry from the telnet menu. You'll have to drop into a shell a fix by hand). So you could OFF ; Volume-key Down ; USB cable : Code:
fastboot flash recovery hybris-recovery.imgOr more directly : Code:
fastboot boot hybris-recovery.imgI haven't had time to investigate yet, but I strongly suspect that the bootloader itself isn't stored on the eMMC flash. So fastboot mode should work even without it, and fastboot boot should be entirely be doable in-RAM. Thus this last option should still work even if you completely **** up the whole GPT partition and need to re-partition manually. (But this isn't a guarantee. Maybe the bootloader needs to do something silly, like checking a checksum or a signature in order to decide if it needs to display a warning, and crashes in case of corrupt partitions) |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Telenor in Norway has that as routine to protect SIM cards sent by post. Regards, Frode |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
EDIT: But this i wonder: You can unlock the carrier by going into service menu and enter a code you can buy online. But how do i access the service menu with SFOSX? Android is the *#*#7378432#*#* |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
However, the biggest issue here are probably all those other partitions which contain crucial data for some hardware components. As I understood it when this topic was discussed in the second-to-last community meeting, some of those partitions can't be restored and you hard-brick the device when they are removed / damaged. So f***ing up the whole partition table (or at least making the slightest mistake during its restoration) could FUBAR (f*** up beyond all repair) your phone. We also need to keep in mind that "moderately safe" or even "unlikely events" are not safe enough for Jolla to deploy an automated process with the possibility to completely brick the device. |
Re: Sailfish OS (officially) on Sony Xperia devices
Does any one know if the browser and email client will be improved in regards to general UI speed within the next year?
|
Re: Sailfish OS (officially) on Sony Xperia devices
Is there a way to get rid of the warning screen on the start up?
|
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
Joke aside no, there is no known way of removing that warning. |
Re: Sailfish OS (officially) on Sony Xperia devices
The non-joke way to remove the warning screen would require Jolla to get their boot image (the hybris-boot.img file with the kernel+initrd that gets flashed on the boot partition) signed by Sony's key.
Or alternatively, to get their own certificate admitted into the Xperia X's bootloader. And then, re-locking the bootloader. |
Re: Sailfish OS (officially) on Sony Xperia devices
Seems like with the new string being translated for 2.1.4 we might have another update before Christmas which would be a nice :)
|
Re: Sailfish OS (officially) on Sony Xperia devices
Been unusually busy lately, but I haven't fallen off the face of the Earth (or blasted off to test the spherical vs. flat argument).
<long story alert> In fact, I've gotten an Xperia X to try the official Sailfish X on. I'd been using a Oneplus X with a community SFOS build, and really liked it. Unfortunately, its support for US frequency bands is incomplete, so it's voice and data QOS is a problem in some places -- one of which is my house. So on the Experia bandwagon I hop! Backing up the Digital Restrictions Management stuff turned out to be a bigger PITA than I'd expected, and began to look like it was gonna take more time than the device sells for at the hourly rate I bill my free time to myself. So it's SFOS all the way for me! (If I ever need to part with the phone, I'm sure someone here would like it at a very reasonable price with Sailfish installed.) I miss the double-tap to wake. Hopefully that gap will be filled soon. Also miss the display-off gestures, particularly to start the camera and the flashlight. But the biggest regression from the OnePlus community build is the SD card support. On the OnePlus X, I was able to use any SD card I tried, including a 64GB card with the exfat support from OpenRepos, but with Sailfish X I found that all my cards 32GB and bigger -- fat32 or exfat -- fail with dmesg errors about "tuning". I see that's apparently a kernel issue with the build and certain SD cards related to timing and transfer speed, etc. </long story> But now, something I hope someone has some insight on. I was able to use a 16GB fat32 card -- for a while. I installed a few apps, including SSHFS support to copy my backup off the other device -- so far so good. Then I tried the exfat tools, including bleeding edge SD card tools. Once I installed the bleeding edge sd-utils, the 16GB card wouldn't mount, automagically or manually. I removed bleeding edge sd-utils and replaced it with stock, and 16GB SD card was back. Again -- so far, so good. So I restored the backup from SD card and went on to install a bunch of my favorite apps. Somewhere along the way, the 16GB SD card disappeared again. It's okay in other devices and on the Ubuntu PC, so I don't think it's a hardware failure. Instead, I suspect that something I installed in the meantime has caused the issue. I've tried uninstalling a few things and retrying the SD card, but I haven't found a culprit. I've searched here and on TJC, but haven't found another report of this behavior. As of now, I can't seem to use any SD I have of any size or format. If anyone's got any ideas on this, I love to hear them . . . |
Re: Sailfish OS (officially) on Sony Xperia devices
robthebold,
I don't have the answer, but suspect microsd support is behind this issue on X https://together.jolla.com/question/...g-grey-photos/ I have noticed ext4 errors in dmesg. Repairing ext4 on a desktop and using the card in J1 and the card works fine. Back in the X it works initially, then the ext4 errors appear again. Presumably need a newer kernel or to try a different card. Rich |
Re: Sailfish OS (officially) on Sony Xperia devices
Quote:
|
| All times are GMT. The time now is 03:53. |
vBulletin® Version 3.8.8