Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

I would just prefer regular Mer on a NOTE.
But to go all-out would be to put Mer with a UX that I have in mind (best combo of WebOS, Android, WP) with specs such as:
- 4GB RAM
- 2GHz Dual Cortex A15 (28nm)
- LITTLE.big 1.2GHz Dual Cortex A7
- 5.2in 1080p SLCD-IPS+ Display
- 10 finger Capacitive screen with Digitizer
- S Pen with Silo
- 128GB NAND and microSD expandable
- 5V charged microUSB with HOST (better than OTG)
- Notification light, Kickstand, Bezelless and Front Stereo Loudspeakers
- 4MP Ultrapixel with OIS but one that doesnt suck like One's
- Noise cancelling mics, aGPS-GLONASS, BT, Dualband WiFi
- Miracast functionality
- HDMI-Miracast Dongle accessory
- "Other half" concept with symmetrical USB contacts at back
- qwerty/azerty accessory, gamepad, etc etc

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

That would be a truly amazing device. Please DO IT ASAP! I would PreOrder at Once.

Ok. Anything else you want to add? :D

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

what do you mean by "regular mer"?

Mer is just a core. Not even middleware, don't even think about GUI.

The two most known OS's that use mer as core (apart from Sailfish) are Plasma Active and Nemo.

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

You'll note that he separated out the UX.

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

Yes, make sure it's a 1080p screen. Not that lame 720 crap.

And while you are at it. Make sure the device is military green!

Thx

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

Also, make sure it comes with a projector and a coffee machine, but proper espresso one, not that filtered stuff.

On a more serious note, I doubt that 1080p makes sense on anything as small as a 4-5" screen. Then again, and depending on the technology behind the interface for the other half, we may have a bigger folding screen - the technology for that is out there, not commercialised [as far as I know] but it is there.

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

To be honest you can probably get a 1024 x 600 screen on a 4-5" screen, and in most (90%) instances it would be just as good as a 1920 x 1080 (which is x3 times less dense).

And having a "low-end" 1.5GHz Dualcore S4 Snapdragon-2GB RAM would be as quick as a 2.0GHz Quadcore A15-3GB, in most instances.

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

That, and I'm sure you don't need dual core anyway. You don't need a Ferrari to go to buy groceries either, but some people have it, and in the same way I'd happily use a single core 2GHz CPU that can go as low as -say- 500MHz, as opposed to two 1.5GHz ones that can go as low as 500MHz. The former will use less energy, and get single tasks done quicker, and I'm pretty sure that I don't use applications that require multi cores, hence the OS doesn't need to worry about multiple processors, and so on.

I reckon Jolla will do well with "low" or "mid" end hardware - the idea is that the OS is smooth, that's all. The only tricky bit I expect is the browser, especially in those pages that don't have a mobile version, as Javascript can be quite heavy; _but_ there is no phone, high end or not, that handle those well enough. In fact, some laptops/desktops also struggle if they are a little bit behind on the spec end.

Also, if you use the phone to compile, transcode, run genetic algorithms, well, it's going to be as fast as it is, isn't it?

We're kind of joking in this thread anyway, we ain't know anything, and we won't until the _actual_ phone is *actually* announced.

Re: JollaMobile : Jolla continues Nokia's excellent work on #MeeGo based smartphones
 

You don't get it about Dualcore devices.

When in standby they shut one of the cores down, and clock the remaining one to the lowest frequency and voltage. This is usually 150MHz @650mV.

When in "low power" state, they will clock that single core a little higher; eg to 300MHz @800mV.

After that, it will stay on the same frequency (300MHz) and turn the other core on and alter the voltage slightly (850mV). This point, it will be using a little more power but will double all tasks (well, almost all).

Depending on the Application, most wont require more than 800MHz @900mV to run. But having that second core is useful in almost all instances and will increase responsiveness without a big hit on power. This is one area where iOS thrives, and where Android lags behind (Apps aren't made specifically for target device, target device not tailored for specific app, efficiency is compromised).

However, newly arriving Modern Apps, are no longer light software... they're more powerful and more demanding (some even desktop grade). I think a 1.2GHz Dualcore can handle most of these well (leaving enough overhead for the OS, multitasking for other Apps).

So clocking higher than needed, especially when the overhead is already large enough... its just extra performance not utilized, but still dampening the battery life. This is why having a 2GHz processor can be a battery hog, and is not quite useful (yet).

Going quadcore does increase performance... but by a small margin. However, the power hit is just as high. So its an inefficient choice. Or at least for the time being, the OS's still need to mature and dev's need to convert their Apps to take advantage of such things.

Hence, 1.5GHz Dual > 2GHz Quad ... it offers the necessary power at better voltages, but it isn't future proof.