AFAIK, the power consumption of typical LCD screen is about 75% for back-light. As for pixels, it's not that much about the number of pixels but the area of screen they have to cover. One big pixel can use roughly same amount of juice as several smaller pixels covering the same area. There is some power "wasted" on circuitry needed for handling extra pixels but AFAIK it shouldn't be significant compared to other things consuming power.

Bigger resolutions do need more capable SoC/GPU, which may or may not lead to increased power consumption. It depends on how much newer SoC/GPU has improved on performance AND how that has affected power efficiency on those chips. Moving to smaller manufacturing process helps on this regard, as well as possibility to cram more transistors to smaller die (of course the design/architecture has to be good). So, I do question the idea that older, low powered chip coupled with low resolution screen automatically results in more power efficient device compared to newer chip with relatively high resolution screen if the devices are similar in size.

Sorry guys, do you really think this discussion has still anything to do with the initial thread? Wouldn't it make sense to open a new thread for this screen discussion?

The screen is already chosen it is 5.5" IPS and 1080p.

y'know....
I have been pondering this same question for a while now...long while...

I think as a serious topic as it is...there should be a separate thread for it...

Also I think there should be a thread in off topic...
Called the "Waaaayyyy Off Topic Hijack Thread" ..
whose sole purpose is to deviate as much as humanly possible,
from the pertinent topic being discussed at the time in it.

I am sure I will enjoy spending some time there...

Yeah, I have been quiet lately due to off topic discussion. But I'm sure I'm some how blamed anyway. As always

On the other ...side/hand/frontier? What else is there to discuss in this thread? We simply have to wait for Chen to announce the sailingChen campaign.

Ahhhhhh Dave is involved, that explains anything.
It couldn't have ended differently, than running off topic...

hahahahaaha...
ah..
well to commemorate

I will indeed make the said thread as a homage to the master ...
Mr. Dave.

once I get home ...

I have a fitting topic start too.

Back to topic:
@chenliangchen if you consider to offer this device also with android. Wouldn't it make sense to offer the device with a dual boot system right from the start? Maybe that would save some people from the dark side by just playing with SFOS.

And something different, how long do you think will it take to port SFOS to the livermorium device. To be honest I'm a little bit concerned about that, because Jolla is releasing Sailfish X unfinished.

Hehe. It always works better to move Off topic here as off topic is the only true way to be on topic for threads over 2-3 pages. Becouse of the fact that all valid discussions has already be been discussed from the info we got. But to keep a thread/project alive over time, Off topic most be allowed. Why not continue here until Chen ship the Moto mod and start building a qwerty slider. We can have a lot of fun in this Thread over the years to come until something might be ready.

Like having a contest when we think it is ready for customers:
Chen thought/hoped before end of this year.
My bet was in about 2 to 3 years.
Anyone else?

TL;DR: The fact that Sailfish X isn't 100% finished has no impact on SFOS on livermorium. In fact, when you look at it, the remaining work to get Sailfish X being perfect on Sony Experia X is about all the work that would be needed to get it on Livermorium too.

-----

When you look into the detail, Jolla has just finised the long and exhausting part of porting the whole of Sailfish OS from 32 bits to 64 bits.

Up until now we had 32bits ARMv8 used by nearly every smartphone port (and 32bits 486-like Atom used by the tablets). Sony Experia X is the first ever 64 bits CPU (an ARM64 one).

In theory that requires "just" recompiling everything for the new architecture. In practice, the devil is in the detail and it's a long process of chasing all the minute small unexpected bugs.

So, now with Sailfish X all the hard work (or at least tedious work) has been done.

The things that are missing on the Sony Experia X are very specific to *that* platform (getting the drivers to work and plugging them into the users space to work - they "just" need to get BlueZ5 working).


So for a potential Sailfish OS port on this upcoming livermorium, it shouldn't take as much time :
Sailfish X is already working on 64bits architecture.

The main problem is going to be drivers :
- getting the binary Android linux kernel fork provided(*) by Qualcomm to run
- using libhybris to have all the binary proprietary drivers (eg: EGL drivers) to run on GNU/Linux instead of Android.
- plugging all the other userspace component.

Should be work within the "months" range.
Somewhere between 1 month (we're terribly lucking and everything works on the first attemps) and 6 months at worst.

(Again, that's incredibly fast, because the tedious work is already been done)

----

(*) : Or if we're extremely lucky, maybe that the PCB that chen has decided to use as a base happens to be useable with the vanilla upstream linux kernel and freedreno drivers.

Another option to get faster, would be to leverage the community porting (in progress) for the Motorola Z Play, using the same MSM8953 chip as seen here :
https://talk.maemo.org/showthread.php?t=99669

Seeing as Chen said in the linked thread he had sent a private message to the porter, and that he is working closely with Motorola for the keyboard Moto Mod, I wouldn't be suprised if there is some truth behind this.