I like the design, But the phone is even bigger than Sony Xperia 10 VII.
88% of the people voted for Display size ~5" to ~6" and this closer to 6.5" So no check.
At 6.36 inches Motorola Edge 60 Neo is significantly smaller and Xiaomi 17 and vivo X300 are sized ~151 x 72mm. Galaxy S25 with 6.2 inch display is sized 146.9 x 70.5mm.
One hand use - no check.
Whats with the big bottom bezel if no front facing bottom speaker, or the huge notch
Also, Support for Android apps with Jolla AppSupport. Is it included with the purchase?
Cellular: 4G + 5G. No mention of GSM / HSPA for those who still have 2G, 3G in case VoLTE is not well implemented in the beginning.
Ordered a voucher of this new Jolla phone without any hesitation. The final price for the pre-orders is ok for that spec.
Thank you for choosing an AMOLED screen and RGB indication LED.
What is the lead time until the pre-orders are shipped? 1 year?
Anyway, I’m happy the Jolla finally did this. Now they have the full power of their own device (with decent specs), all the specs, documentation, SW stack is theirs and they don’t rely on some third party company with an opaque SW blob.
Jolla must work hard on the SW in order to make voice over 4G/5G work on day one. They cannot mess this up because this phone is almost their final chance.
If the amount of pre-orders hits 2000, then I gather the actual full technical specification will be finalised and you will be able to make the final payment of €499* (not to be confused with the regular price which will be higher for people who didn’t pre-order) when that happens.
As mentioned the shipping time is expected to be mid-2026 so don’t expect a delivery by Christmas
If you pre-order and we don’t hit 2000 by the 6th of January, your voucher will be refunded to you. And we’ll all be quite disappointed. But hopefully that doesn’t happen.
*the website says the €99 voucher will be “deducted” from the final payment “later” so it may be €400, unsure. either way you are paying a minimum of €499 for voucher + phone
So the story continues. Instead of ever finishing any of the existing unfinished devices, let’s make people shell out money yet another time on yet another one, that’ll end up unfinished as all the remaining ones.
I will NOT buy this or any other future device or licence until they prove that they’re a serious and trustworthy company rather than a bunch of careless and unserious kids. The communication about the 10 IV and V has been so CARELESS that it’s been actually almost OFFENDING to all those who shelled out hundreds of euros misled by their hollow statements and promises from May 2024, then completely forgotten and never again properly addressed, except for completely meaningless chit-chats like @rainemak’s “Xperia 10 IV / 10 V could well be the first officially supported community port which would have commercial components available including AppSupport – but that community port does not exists yet” which, as all their statements, actually carries ZERO reliable information and means completely nothing other than that something “could well be” something but it isn’t and no one knows if it’ll ever be.
I agree about the bugs just migrating from one device to the next, however, a large part of those bugs started when they started relying on other companies’ hardware and forcing Sailfish to run on something that normally runs Android. Looking back at the original Jolla phone, it certainly had bugs, but those were ‘simply’ bugs in Sailfish, not bugs in the hardware adaptation (at least I can’t think of any). I’m sceptically hopeful that this new phone, because it wasn’t originally designed for Android, won’t suffer from a bunch of the adaptation bugs present in Sailfish X or the C2. This time they’ve picked out the parts themselves, so I assume they’ve picked those that are most likely to “just work”.
Are you suggesting that ANY part of this phone will not consist of commonly available, mainstream elements, commonly found in Android devices?
Yeah, but probably only out of those supported by the given Chinese manufacturer that will then glue it all together for them and put it in that nice casing, quite possibly the only unique thing.
Of course it’s made in China, the point is that the original Jolla Phone was also made in China and still, to this day, is perfectly functional (of course, if you don’t need Android applications and don’t browse too much). It runs smoother than all of the Xperias despite having a fifteen-year old processor and 1GB of RAM. I assume that back then, Jolla didn’t just have an extremely lucky day after throwing random parts together.
I don’t mean to say some scepticism and frustration based on past experiences isn’t warranted, but the fact that they’re still in business after all these years (instead of just pulling the plug after e.g. the tablet troubles) and probably doing the best they’ve been doing in a very long time, and actually finally freeing their proprietary parts (not a money-making move), suggests that some optimism is equally warranted.
SFOS runs with kind of usable speed on the J1 only because it is SFOS 3.something, i.e. long before Sailjail, encryption, etc., which is what (and definitely not Xperia hardware itself) made newer devices appear kind of sluggish (especially visible on e.g. the XA2). If the same SFOS version as on the J1 was installed on e.g. the XA2 or the 10 III, it would literally fly.
But it’s nothing new. Actually, it’s been their modus operandi since 2012.
Finish what’s unfinished first, and only then move forward (rather than COMPLETELY VICE VERSA, as it’s been the case for years). Not just the infamous 10 IV/V but also the C2 that also has a lot of problems. Note that I won’t even mention the 10 III.
Oh, and start communicating more respectfully with people. One meaningless statement every 3 months that “they might think about something” (and then nothing) definitely isn’t such.
A given SoC supports given peripherals. It’s not that you can mix anything with anything. And also a given factory (e.g. a PCB farm) supports (or at least makes financially feasible) certain options (e.g. litography level depending on SoC “micronage”, how many PCB layers it needs, etc.). Lastly, with quantities that a small company like Jolla buys, you are restricted by prices, because such small quantities are costly per unit, so you end up buying older components and not the latest and greatest ones, because older components are relatively much cheaper at such low quantities.
Which, in reality, shrinks the choice to quite a limited number of possible combinations, at least if you want to end up with a tolerable per unit cost. Which, in turn, means that what you’ll probably end up with will be (almost?) the same choice as many existing cheap Android devices from cheap “brands”, whose small “manufacturers” (all those MyPhones, MaxComms, etc.) also had an identical choice to make.
Thanks for your detailed answer. If the world as you described then there is only this one way. And “cheap” was also on the requirements at least of some people. So thanks to the Sailors for finding a good solution when bound to this restrictions.
Make no mistake, even the J1 was a designed-for-Android platform (delayed 6 months to make libhybris, remember?). Jolla was going to use the ST-Ericsson Snowball(?) platform which was basically the last platform that sipped a Linux adaptation and not only an Android one, but it was cancelled. This J2 is more than likely going to be on a platform targeted at Android. I think maaaybe Qualcomm has one with official non-Android Linux support (which might be just as buggy), but never heard of it for MediaTek.
With that said, there are of course worse and better choices of hardware still. Jolla will of course have made sensible choices as far as they could. And honestly a lot of what big G is doing for driver interfaces and mainlining is actually for the better - just challenging to keep up with at times.
Well, unless Jolla have started designing and manufacturing hardware themselves then this new phone too will use ‘other companies hardware’. And that hardware will still need low level hardware drivers, won’t it? As far as I know this software layer is not part of SFOS at the moment. So unless Jolla are going to write all these themselves in the next six months, perhaps as native linux drivers, then they are still going to be relying on blobs or drivers written and supported by other companies (just like it is for the Sony models) - or have I got this wrong?
My guess is that the new Jolla phone is based on either an existing manufacturer’s model or parts bin, and it won’t take long for the community to work out where it came from. Totally new phones take years to design, test and get to market using a cast of thousands. For such a small company as Jolla to design one from scratch would be both impossible and cost prohibitive.
So, at the moment, I can’t aee how this new phone can be any different to, say, the C2 based on a Reeder model with all of the attendant bugs and issues that this port came with.
The manufacturer is likely to also sell development boards based on a reference design. It is possible that Jolla already have these right now. With this reference design, many Linux drivers have already been made. Of course adaptations might be necessary on driver and higher level. What is also provided is full documentation of the reference design and possible alterations requested by Jolla. I don’t know how much Sony provided Jolla in terms of documentation, but since you pay for a HW phone you also get the full documentation associated with it.
The drivers are a mix from different sources but that’s the case for almost any manufacturer these days unless you are Apple that does everything in house.
