We have moved to a new Sailfish OS Forum. Please start new discussions there.
10

Yotaphone 3 & Sailfish OS?

asked 2017-04-05 16:03:49 +0300

Cryx gravatar image

updated 2017-04-05 16:31:08 +0300

jiit gravatar image

Yotaphone shows a new photo on their Website (yotaphone.com), maybe the Yotaphone 3. Any thoughts about a possible Sailfish OS Version since Jolla has this deal for a Russian mobile OS?

edit retag flag offensive close delete

Comments

1

Mind that every smartphone maker willing to reach masses will use Android, and they will not drop that idea easily.

Macilaci457 ( 2017-04-05 17:18:44 +0300 )edit
4

They do not have to drop it, do they? They can just provide SFOS as an alternative.

tortoisedoc ( 2017-04-05 22:19:47 +0300 )edit

just provide... and just provide some resources to build drivers kernel and test all functions for quality...
they must earn something with this. then just provide an other os, is a little bit lightly told i think...

cemoi71 ( 2017-04-06 23:01:55 +0300 )edit
1

nice phone indeed

cemoi71 ( 2017-04-06 23:04:20 +0300 )edit

2 Answers

Sort by » oldest newest most voted
8

answered 2017-04-06 18:05:27 +0300

_ _ _ _ T A _ _ _ _ gravatar image

updated 2017-04-06 20:23:16 +0300

Yotaphone with Sailfish OS was a news about 2 years ago, and that was in fact the first Russian company interested in SFOS device - according to my limited knowledge based on internet observations. Yotaphone are unique due to 2nd screen which is e-ink touchable reader. It can play role of main screen, but e-ink use about 5 times less energy, so smarphone can work much longer, and excluding playing video or shooting photos 2nd (e-ink) screen can be even better as it is much more healthy and less tiring for eyes, as this is first of all a comfortable e-book reader. That would be fantastic if they would sell that 2nd screen as TOHalf for current Jollas - I would buy it, really.

If they haven't launch YP3 with Sailfish so far, then I suppose that was rather about waiting for "green light" from their RU gvt. On the other hand, it is much wiser to use OS that is certified and hence allowed then to fight against RU administration. I am quite sure that if they were "kindly asked by sad men in suits from RU gvt" - you need to wait until we let you - they just obeyed and have been waited IMHO. Who knows. The question is what changes were enforced by RU gvt in Yotaphone with Sailfish, as I think it will be a RU version.

Anyway: I recognise Sailfish YotaPhone as valuable sailfish device for a replacement and for everyday use. And I would have much comfortable for eyes e-ink screen for daily operations and use. (Do you remember N9 off screen-saver displaying time using only some pixels?) Of course with possibility to switch to classic screen and vice versa in the fly. YotaPhone use 5"Amoled screen with GorillaGlass and 4,7" EPD E-ink display with refresh rate of 0.12 sec 16 greyscales. As they say "Android screens can be almost impossible to read in bright sunlight. YOTAPHONE’s EPD screen is perfectly readable even in the brightest sunshine: fiction, Facebook, Twitter, news, RSS-feeds, blogs, mail, messaging and absolutely everything else. Reading on EPD 100 h, Using maps on EPD Up to 18 hours." See their video in English here: https://yotaphone.com/us-en/ They have with Yota about 150 patents and patent applications, so I think their technical solutions are and will be quite unique for a time. I think that would also be very interesting company for possibly Jolla partnership, IMHO. Smaller then INOI or OMP, having origins like a start-up, so finally it could realise they are quite easy for Jolla "to finds a common language" and cooperative. Also I suppose that if they were accepted in a RU landscape there so far they would be accepted still also when would join to Sailfish. So, Jolla please: cooperate with them - we would have first serious Sailfish OS e-book reader with e-ink screen, and really good mobile for replacement. I would buy it as next device. Additionally, as I know,they have own distribution in many countries also via their site. For me YotaPhone "mobile of 2 fronts" is second the most innovative device, just after Sailfish OS device as first the most innovative one.

YotaPhone 3 is to be much cheaper, as manufactured by ZTE in China - price was a problem with Y2, unrealistic for me. It is expected to be in sell in summer 2017, we will see. I will buy it.

Additionally for YotaPhone company: there will be a demand, seems to me quite significant, at Russian market due to Jolla cooperation and Sailfish RU propagation in institutions and hence among common people, and that will be an opportunity for YotaPhone. Would be irrational not to use that opportunity and not to launch the Sailfish YotaPhone 3, IMHO. But to let it happen the support and cooperation with Jolla is necessary IMHO. I put it here as I haven't seen YotaPhone anywhere in the context of recent cooperation between Jolla and Russian side. Perhaps I am wrong or unaware, I don't have any precise info. I just think in best Jolla, Sailfish, sailors, users, RusFed, free coders etc.etc. is Jolla to pay some attention towards cooperation with YotaPhone company, to verify if it is included (if is interested in) and not omitted (despite is interested in) or needed additional support can be provided. It also can happen they ought to be considered as company partly operating in China, considering their cooperation with ZTE so Chinese manufacturer.

off topic BTW: This could be an opportunity for eventual further cooperation with ZTE. Note so far confirmed are Sailfish ports on following devices from "ZTE Open C and following variants of this mobile phone by ZTE: ZTE Kis III (Kis 3), ZTE V811, ZTE V811W, ZTE Blade M, Beeline Smart2, Moche Smart A16 (MEO), Optus Hop Smart, Skinny V811." I assume I don't need to say about oncoming potential demand in China.

edit flag offensive delete publish link more
2

answered 2017-04-08 13:54:16 +0300

velox gravatar image

updated 2017-04-08 13:55:44 +0300

As both an e-ink and a SailfishOS user, I actually have some thoughts on this, which I might as well share:

While the Idea might seem like a good one at first glance, IMO the SailfishOS UI isn't really feasible on e-ink, since all swipe interactions rely on large portions of the screen animating, which is not what e-ink is made for: In the best case it'll end up looking a bit ugly and make portions of the screen unreadable, in the worst case it leads to heavily reduced life time of the screen compared to just having "static full screen updates" once in a while. I'd be not surprised if those ideas weren't followed for this reason alone.

Also, one of the unique things about SFOS is having ambiances, which are made for looking pretty on full-colour-displays but almost always lack the required contrast to really shine on e-ink – if you only have a few steps between white and black, it's best if you use all of them.

Source:

I have a modded/rooted Tolino reader and run some light weight android apps on it which are not optimized for this kind of screen. Even animated scrolling in lists can be painful to look at. As a nerd, I adore the added value of the device and can live with sometimes manually starting a "screen flash update" app to reduce artifacts from previously displayed content when it becomes too much, but most consumers would be really appaled.

edit flag offensive delete publish link more

Comments

4

I don't think that's a problem because the e-Ink display is on the backside of the device, it's not the main interactice screen.

juiceme ( 2017-04-08 15:25:35 +0300 )edit
2

+1 to juiceme. The point is that YottaPhone has 2 screens, but not 1, and 1 is Amoled and 2 is e-ink. Hence if you use a device "staticly" so e.g. lock screen or notices or just a clock or calling/answering calls - then I think in fact animations with swipes are not needed. Could be either omitted or extended with a something like a symbol of swipe (e.g. >>>>) instead of animation. But anyway, you can switch from e-ink to amoled (and vice versa) in the fly and have fully animated swipes, gestures etc.. Frankly, I would sacrifice animated elements and ambiences for much longer battery life and simplified display at e-ink, very easy and without regrets. Simply because when a device "awaits" my action or a phone call then b/w clock with or without notifications are OK for me. Also note YP has 16 greyscales and colours with that e-ink AFAIK. I agree animations at e-ink can look ugly or hopeless indeed but I doubt that would cause e-ink screen damages - I would be for adaptation to e-ink as I have mentioned above. Also agree with "artefacts" you have mentioned, but this can be solved by adding a button/swipe/procedure/something else to clean them. This can be conditional, as OS recognises to which of 2 screens "a display" is directed. Agree about issues, but they are not unbeatable, also I think Yotta can have some ideas how to solve them.

_ _ _ _ T A _ _ _ _ ( 2017-04-11 14:10:11 +0300 )edit
1

Yes, I agree on almost everything there, but my point wasn't that it's not possible, only that almost no parts of the user interface could be (nicely) used unmodified – I don't expect a timely rewrite of Silica for this soon. The alternative would be just sending "static images with touch area definitions for callbacks" to the second screen, which wouldn't be as useful and would require software additions, as well. I don't even expect SFOS/lipstick to handle multiple screens at all at this point, but feel free to correct me if I'm wrong.

Also, it's not so much about really "damaging" the screen but about limited amount of changes per pixel in the lifespan of the screen – which is not really noticeable when only switching every few minuted or even seconds, but might be when doing "60fps animations" for extended periods which SFOS is trying to have. Note that this might have improved in recent e-ink generations, but should be considered, still.

Don't get me wrong, I'd absolutely adore having this and, same as @_ _ _ _ T A _ _ _ _, would gladly accept almost any limitation that comes with it. I just don't see it coming in the (near) future due to huge changes in software this implies and the limited (yes, you and me want it – perhaps another 1000 people of which some may even buy it, but that's still limited) expected revenue.

TL;DR Cool: Hell, yes. Feasible: Well, still no.

velox ( 2017-04-11 15:37:30 +0300 )edit

My guess based on observations is that when YP3 will be launched with SFOS then user will make requests for needed adaptations. Anyway even with Android the same problems described above, seems to me, are present. So I think they have find a solution for at last some of them - and those experiences could be adopted and used. If nothing else helps - then one can just use main Amoled screen, that will work always I suppose ;-)

_ _ _ _ T A _ _ _ _ ( 2017-04-13 21:22:47 +0300 )edit
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2017-04-05 16:03:49 +0300

Seen: 2,167 times

Last updated: Apr 08 '17