Phone (C2) vs Xperia 10 V

General
#61

Let’s put it this way.
The 10 V is much faster than the C2. But the C2 will crush the 10 V if the application uses more than 6 GB of RAM, because the 10 V does have less memory.
My phones sometimes feel like single task devices, because to copy 2 lines of text from 1 app to another (bitwarden login info to browser), I encounter 4 OOM kills and have to reopen these 2 apps multiple times, as stated in my original post.

There has been a lot of mentioning (from complaining to raising awareness) of the C2’s low specs. Your table did show it is not too slow. And it has more RAM. So it might be the better choice for me. Your table did help me. Not in the comparison with the 10 V, but in knowing the raw speed of the low specced C2 are more than enough for me.

#62

Bitwarden as in BitSailor? Might it be nodejs eating RAM?

#63

Some things to clarify first

There is a version of 10 V that have 8GB RAM (XQ-DC72).
What do you mean by “Application uses more than 6GB of RAM”? Also RAM of 10 V is faster. Sorry, there is no simple way to compare C2 as in fact lower specs overall.

Mentioning my table, which shows only up to Xperia V/VI really, there are much more powerfull phones than sony 10’s. C2 is deem slow, as it is slower compared to our last community device. Which is old generation of sony lowest xperia line phone

And man, if there

There is something seriously wrong with your device

#64

if there is something eating RAM with 6GB, will not stop OOM happening with 2GB more RAM

#65

But you gain more time until it happens, ducks and running away

2 Likes
#66

True, but my xa2 with 4gb ram had less oom app kills than xiii with 6gb ram.

#67

I am using xa2 plus (4gb) right now and oom is very rare, where on 10 mk2 (4gb) it was sometimes happening just after minimizing the app - it was hard to use two apps simultanously. Xa2 is 32bit which has smaller memory consumption, so I have some hopes that 8gb for 64 bit is enough and will be on par with 4gb on 32bit.

1 Like
#68

I had the XA2 and the X Compact, both of which were running on 32-bit SFOS. My first 64-bit SFOS device is my current daily driver, the Sony XZ2 Compact, and I experience these OOM issues here more often than on 32-bit.

#69

But isn’t it 4gb ram?
Previously said seem too simple but I can understand reasoning behind this statment
32bit - 4gb
64gb - 8gb

#70

@Ride92

Thanks for the comparison chart, but which version of AnTuTu scores was used? I’m asking because there are significant differences between the scores for each model depending on which AnTuTu version was used. My daily driver, the XZ2 Compact, with its great community SFOS port, has a speed comparable to the C2 with older Antutu-Version (7 and smaller), which is a good value.

#71

All comparable scores were taken from one website. https://www.kimovil.com/pl/
Most of the time there is no information about which antutu was used. So to make my chart more relaiable I’ve taken scores from different sites as well, sometimes taking average of few scores. As I said in my post there is nothing technical about this.

I’ve also checked XZ2 score and was amazed how this old device would perform. Always this make me wonder why jolla focuses only on low end devices when few years back you could have a device with similar abilities to this year all new community phone :stuck_out_tongue:

#72

Small little comparision which goes into the same direction:

1 Like
#73

If the phone purely working aliendalvik system 8gigs help quite a lot, but if native browser working together with AD apps, indeed I found 8g sometimes still yields OOM killing, for 12g and 16g I rarely see any OOM anymore even with waydroid run together with AD.
For gaming I found AD is less preferable in compared due to its HW acceleration, waydroid are running directly of on HW, but AD is using hybris’s rendering, in some case it is less smooth, so when choosing GPU probably the more capable the better, it helps both in saving energy and smooth gaming experience.

P.S. waydroid will have a lot of problems on debugging,a lot of stuff treat it as a simulator but AD have done a ton of works trying to make it functional to apps more likely to be a phone, so if gaming is a must don’t bet on waydroid unless you have a lot of time on debugging this issues.

#74

What is DA in your post?

1 Like
#75

Ah sorry, that’s a typo, should be AD, all DA refers to aliendalvik, AppSupport in sailfish system.

#76

Thanks, maybe edit the post too:)

About AD rendering, on the last official device I have (Xperia 10) I found that AD did not do many frames for app animations, until 4.5.0.x I think, when it started doing that too. Waydroid was always as snappy as booting Android. However, not the same can be told when using nested compositor (i.e. a window per app).

Maybe this is what’s holding AD back? Multi-window? (basically they both use the native HWC service, but one goes through lipstick first?) And we need a full screen mode for games only…:)? DirectX vibes from the 90’s…

1 Like
#77

Yeah, i saw some update notes on 4.6 for a smoothier firefox on AD as well, maybe they have changed some settings on that, currently im on 4.5.0.24 as well, lxc config for AD looks like there is a refresh rate setting as well, which is 59.99 alike so i guess the problem might have something to do with likstick setting for power saving.

for windows mode waydroid works partly pretty well on sailfish as well, it doesnt have the same lag on texts like on AD, but since android is a single window system it doesnt run in parallel overall so it just doesnt worth make it working like so i felt.

also If you open a HW acceleration required app in AD you will find it works nearly identical to waydroid, but you can feel the lag happens sporadically, likely couple few seconds a time, im quite sure it runs with HW accelerated, but the difference is noticeable, or maybe scheduling settings for cgroups? I kind feeling they tradeoff quite a lot trying to manage run the android system in a more controllable manner, it works really really good as a collaborative system when main app ecosystem is just not good coverage enough.

#78

There is a version of 10 V that have 8GB RAM (XQ-DC72)

where to get that one from?

#79

Be careful and check the list of supported devices first (exact model). More RAM devices often are for the asian market and not supported by sailfish

1 Like
#80

ebay.

jolla have said they will support the 8gb variant.