Works fine for me(in Signal). You should probably check if Signal has the correct Android permissions(camera and mic).
Sometimes these permissions get denied automatically i’ve noticed .
Permissions are ok. I checked it twice.
Not strictly Xperia 10 III related question, but … I will be switching from Jolla C and would like to take opportunity to transfer SMS history.
Catch – I would like to combine SMS history from 2 phones – from Jolla (1) and Jolla C to Xperia.
Also, backup function to SD card on Jolla (1) produces unusable archive, cant’ be imported.
I guess I have to do that “manually” and I don’t know how 
Anyone gone through this before?
Thanks,
b.
1 Like
So I used backup from 10 to 10 III, and some things got moved, but some not, like notes, mentioned in other bug reports already.
Fortunately SMS history worked just fine, apart from the fact that they now show up with just the phone numbers and not contact names, which might be a problem for you.
Not sure though if backup will work from an older SFOS version, you might want to update your Jolla C to SFOS 4.4, and then try to merge records to that backup from Jolla 1. How? I have no idea. Also, maybe you want to create a separate topic for that, it might be useful for a lot of people!
Edit: Yeah, really sorry but I don’t think you can merge message history in the backup, it is a dump, that isn’t text based. I don’t think it is possible.
1 Like
backup messages from command-line on both phones
commhistory-tool export -groups messages-phone-1.exp
then try to import both files on your Xperia, use “import” instead of “export”
maybe it’ll work
2 Likes
ok so it would be great to monitor this as it can be a blocker for X10III similar to this one:
TBH, echo during calls hasn’t been an issue to me, as long as I keep the volume low. At least nobody has ever mentioned it during a call…
1 Like
it’s not a problem for you but for the other side and they maybe do not complain because they think it’s like that and it’s also very personal as some people may find it problematic while others won’t bother.
That’s why I personally do not use BT headphones because the voice quality is much lower compared to when I’m using wired headset so the caller hears me better.
Right now it’s a plague and with the remote work it’s even bigger problem that people thinks that wireless headset is ok while it’s not and it’s difficult to hear the other side very often, even when they’re in the room.
True indeed. I also prefer wired headaets because of the poor quality calls via Bluetooth (which is a known problem and some proposals to fix it exist).
Actually, I don’t know why I wrote what I wrote, I shouldn’t have posted it at all. Sorry about that. I’ve had a few notes on that in a few calls, and lowering volume fixed it. Lowering volume is not possible on noisy environments, so echoing is an actual issue. (It seems to be AOSP specific, Android isn’t affected.)
Actually, I don’t know why I wrote what I wrote, I shouldn’t have posted it at all. Sorry about that.
Nah, no worries at all 
This may have been mentioned, but you can apply multiple backups. At this time, SFOS has zero redundancy checks. I know this from experience trying to apply backups with the current Notes bug. Whatever parts of the backup get restored are done. If you opt to run the backup again, nothing stops it from doing so.
My XA2 has THREE duplicate sets of messages from the course of a year, and three attempts to restore my backup. Very tedious and annoying.
So nothing dramatic should occur so long as you are selective with the backup procedure from both phones. Try to backup and restore individual parts instead of making a single massive tarball (the Notes bug will break your restore as stated already).
I cannot wait! I couldn’t gave up on jolla…
Today! It comes today! I was using 10 mk2 for a while but finally decided that XA2 suits me better. So I come here from XA2, and, from what I read I can expect quite performance boost, right? I really hope it will meet my demand
Anyway I know I’ll see it for myself today but is it really that powerfull that jolla market it that way?
Camera works in Signal. However, trying to link a device, the (rear) camera does not focus (to scan a QR). The face-facing camera did work (maybe because the focus was already good enough to read the QR).
As well, auto-focus of the camera does not work with PrivacyIDEA.
To link a device with Signal Desktop, point the camera (which doesn’t focus) at the QR-code and just wait a little bit. After a short time, it will recognize the QR code
I had similar problems, scan after restart could work better.
I just checked the camera in signal again: after a fresh start of restart of android app support I am able to take exaclty one photo.
If i try to change camera or take a second one signal tells me “camera not available”/“no ccamera” All permissions for signal ar given.
Hello guys, I have tried to find some info about it, but no Luck. It is not an huge issue (even though it seems to eat the battery bit faster), but I have issues with notifications LED. I have only modified the colors (in /etc/mce/20hybris-led.ini), but the LED does not blink, but stays ON all the time. Weirdly enough, LED does blink, if the phone is on charger (not charged yet). Anybody has same issues? Did you correct it ? Any link or manual what to do ?
Thank you
EDIT: Obviously I forgot to mention, Sony Xperia 10 III
18mo later, I dusted the X10III off the shelf and finally put it in production.
It’s definitely a noticeably snappier daily driver compared to X10II. I was hoping to skip it for some next more powerful upcoming devices, but Jolla’s reorg is just too much of an unknown, so I bit the bullet. At least SFOS current release seems to be stable enough by now.
I tested my Android app/data backup/restore theories, unfortunately it’s a no-go fail 
.
-
Biggest obstacle seems to be that devices will have different UID/GID values for each installed app. I copied some
/home/.android/data/data/directories over, such asorg.kman.AquaMail, and the app was only able to access this data after Ichown-d old device UID/GID to matching the new device’s app installation’s. This would definitely need scripted assistance to complete successfully, otherwise only a few apps are worth the trouble to migrate by hand. -
Some apps may have other types of device switch protections “anti-tampering” built-in, too. Even if you get data directory ownership correct, app might still refuse to load old data for their own whatever security reasons. This reduces efficiency of the whole exercise into a completely unknown territory. For example, I couldn’t get Slack to just continue working, had to repeat sign-in to all workspaces.
-
I did make a significant change on X10III: I installed GApps into Alien image vs MicroG + Aurora store on X10II. Maybe this also made a difference to whether it’s possible to continue with old app data, or not.
tl;dr You mostly need to re-do your Android apps installation from zero.
Is there anyone else in this thread running their X10III App Support on Google Play from Google play services on xperia 10 III Sailfish 4.4.0.64
Everything is working great in general, but I’m seeing a small set of Android apps being denied with “Not available for device”, for example (a non-security concious) Fender Play a guitar study app.
It installed and worked fine on previous X10II with Aurora Store, so there must be some parameter Play Store is checking for, but there’s no info visible anywhere for why the app is being denied.
Downloaded + installed APK via APKPure, and of course everything works fine. Would be nice to have everything centrally updated.
Is your X10III Play Store also blocking “Fender Play” app, or some other app you care about? Lmk!
I’m curious if you also get sound disappearing issues