SFOS support for new xperia devices

Probably not: there are four licence groups. A licence from one group cannot be used on a device from another group. 10 and 10 II are in different licence groups (information from: https://jolla.zendesk.com/hc/en-us/articles/115003837053?mobile_site=true)

3 Likes

Yeah, shame as I wanted to get it via the discount :slight_smile:

1 Like

Not 100%. Jolla transfered an unused X (group 4) to XA2 (group 3). So, as of my understanding, they did it, but they didn’t have to…

Existing customers have (so far) always received a hefty discount on a license for the latest supported device during the first couple of weeks, even if you only ever bought a Jolla phone you’ll probably get a nice price cut on the license when it’s out.

2 Likes

Ended up buying a licence for Xperia 10 (which I own), then we’ll get one for the Xperia 10 III (or II) when I get one of those devices. Need to support Jolla :slight_smile:

1 Like

btw, then I’ll go search again, but haven’t find anything yet, what was the Jolla rationale to support only Xperia 10 devices? I understand they use it as ‘reference’ device, fair enough, but I’m sure people would love Sailfish on more powerful devices (for example Xperia 5 or even the 1) as they too get added to the Open Device program by Sony.

And with the big news that Android system is now signed, that might be quite a push for people to get serious about Sailfish as an even better alternative to Android or iOS.

They’ve never explained their rationale, but I suspect it’s because a cheaper device will appeal to a larger base.

There is a community port of the last gen Tama devices (XZ2, XZ2c, XZ2 Premium, XZ3), and they’ve asked Jolla to license Android Support for it, but nothing has come forth yet, and with Waydroid making leaps and bounds into that space, you wonder if Jolla have lost a potential source of income.

3 Likes

In better response to yours and everyone else, I would suggest… running tests. And the first test I would do is on the web engine with Octane 2.0.

Octane primarily tests JS functions, but they can make direct calls to the CPU and GPU.
A few tables under the spoilers here, containing the scores of both my Thinkpad T440s and my AMD Ryzen PC, both on Firefox.

Thinkpad T440s, Intel i5-4300U, Manjaro Linux, Firefox

Octane Score: 3519

[Richards]
1347
Core language features

[Deltablue]
1732
Core language features

[Crypto]
2316
Bit & Math operations

[Raytrace]
3984
Core language features

[EarleyBoyer]
4277
Memory & GC

[Regexp]
1151
Strings & arrays

[Splay]
2331
Memory & GC

[SplayLatency]
6172
GC latency

[NavierStokes]
4628
Strings & arrays

[pdf.js]
3412
Strings & arrays

[Mandreel]
1974
Virtual machine

[MandreelLatency]
4557
Compiler latency

[GB Emulator]
8004
Virtual machine

[CodeLoad]
5262
Loading & Parsing

[Box2DWeb]
3950
Bit & Math operations

[zlib]
9084
asm.js

[Typescript]
5950
Virtual machine & GC

AMD Ryzen 2600, RX480, Windows 10, Firefox

Octane Score: 21702

Richards
7413
Core language features

Deltablue
10890
Core language features

Crypto
16820
Bit & Math operations

Raytrace
21143
Core language features

EarleyBoyer
23030
Memory & GC

Regexp
5524
Strings & arrays

Splay
14922
Memory & GC

SplayLatency
22409
GC latency

NavierStokes
23035
Strings & arrays

pdf.js
23546
Strings & arrays

Mandreel
15485
Virtual machine

MandreelLatency
36125
Compiler latency

GB Emulator
63437
Virtual machine

CodeLoad
29145
Loading & Parsing

Box2DWeb
30509
Bit & Math operations

zlib
71947
asm.js

Typescript
34943
Virtual machine & GC

And then finally, the Octane bench on my Sony Xperia XA2 H3123, Sailfish OS 4.1, Aliendalvik disabled.

Xperia XA2, SFOS 4.1, no Aliendalvik loaded

Octane Score: 4479

Richards
5740
Core language features

Deltablue
8820
Core language features

Crypto
4839
Bit & Math operations

Raytrace
13468
Core language features

EarleyBoyer
6092
Memory & GC

Regexp
590
Strings & arrays

Splay
2143
Memory & GC

SplayLatency
1472
GC latency

NavierStokes
5342
Strings & arrays

pdf.js
3306
Strings & arrays

Mandreel
2778
Virtual machine

MandreelLatency
3811
Compiler latency

GB Emulator
8877
Virtual machine

CodeLoad
4545
Loading & Parsing

Box2DWeb
5749
Bit & Math operations

zlib
14903
asm.js

Typescript
4866
Virtual machine & GC

I would like someone to post the bench on their X10ii if possible, so we can see the difference it makes just between a couple of years in hardware innovation.

PS. I had to tediously copypaste the results text over to Notes to get it all, so have fun with that.

2 Likes

Hello everyone!

I’m sorry for not having been around for a while … life happens or however the saying goes …

since I’ve read about the “10 III Dual-SIM” to be supported now too; When would you suggest to buy that? It has been announced but it’s not working yet and you cannot buy it yet from what I can see.

also: Can anyone tell me more about the camera in the “10 II Dual-SIM” and how well it works under Sailfish? I shall try and get a “10 II Dual-SIM” or “10 III Dual-SIM” next; and @olf ? you’re right, it’s now more difficult to get one … why is it that all the nice things have to be sold out so fast?

1 Like

Xperia 5 III is now listed in Sony’s open devices here: https://developer.sony.com/develop/open-devices/get-started/supported-devices-and-functionality/

Any plans to support SailfishOS on it in the future?

interesting kernel/device support graph at the bottom of that page.

seems like the xperia 5 II might be a more realistic option, in sharing the kernel 4.19 kernel with the xperia 10 III, where the xperia 5 III jumps up all the way to kernel 5.4:

1 Like

It most probably that mark IIIs are AOSP12, not currently supported by hybris patches (even if launched with 11)

1 Like

Linux 4.4→4.9→4.14→4.19→5.4 are always increments in +5 releases steps: There is no “jump”, because Linus Torvalds rolls over after x.19 or x.20 (so there is at most 1 release variance): No real “major” release of Linux exists since v3!

BTW, these are simply kernel.org’s official “longterm release” versions, which most Linux vendor use (except for Canonical, they prefer to have NIH).

3 Likes

sure, but until Jolla support an Experia AOSP device that uses Android 12 / Kernel 5.4 i imagine that any community device support will have an easier time if that devices’ AOSP uses the same building blocks as a pre-existing Jolla SFOS device, i.e. the 5 II because of its similarity to the hardware adaptation already accomodated for in the 10 III.