Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 3 days, 4 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 4 days, 4 hrs ago - more...
| The Following 3 Users Say Thank You to pichlo For This Useful Post: | ||
 |
|
2017-10-10
, 08:02
|
|
Posts: 943 |
Thanked: 3,228 times |
Joined on Jun 2010
@ Zagreb
|
#142
|
Originally Posted by olf
this.....
But while I wonder why many people are getting so excited about the Librems's hardware, the real conundrum to me is the software stack:
Showing out a GNU/Linux desktop on an ARM developer board is nothing new, but without a large set of "touch"-capable applications for miniature screens, this will presumably be in 2019, where Openmoko's software distributions ended (or where a "naked" Mer/Nemo is): Not really what one expects as a Smartphone, today (or in 2019).
Has anybody heard or read about specific plans for the basic software stack and addressing the lack of "mobile" apps?
What's the point of a smartpone that is as useful as some candy bar crap. If you can't do things in browser than you can't do them at all in most cases.
My jolla screen was busted so I'm using AOSP ATM and while I do miss sailfish as OS and gestures, but from pure app POV it is way better even just for the basic stuff. Bunch of free navigation apps that just work, file managers with simple but full network acces, working telegram, VIA browser that is 721478 light years ahed of the one in sailfish....
| The Following 2 Users Say Thank You to kinggo For This Useful Post: | ||
|
|
2017-10-10
, 08:31
|
|
Posts: 951 |
Thanked: 2,344 times |
Joined on Jan 2012
@ UK
|
#143
|
I do like my sailfish phone, and librem phone seems interesting but I am worried that it might be a linux desktop distro placed on a phone compared to a proper thought out OS made to run on a mobile device. BUT time will tell and we shall see what happens.
Some people do want their favourite distro on a phone
Some people do want their favourite distro on a phone
| The Following 4 Users Say Thank You to mariusmssj For This Useful Post: | ||
|
|
2017-10-10
, 09:23
|
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#144
|
Originally Posted by mariusmssj
Well, there is not really anything preventing "regular" distros from carrying mobile optimized apps. They already usually support at least two pretty disparate use cases - big headless server/server clusters and single user workstations/desktop computers. So supporting another use case/form factor should not be *that* hard.
I do like my sailfish phone, and librem phone seems interesting but I am worried that it might be a linux desktop distro placed on a phone compared to a proper thought out OS made to run on a mobile device. BUT time will tell and we shall see what happens.
Some people do want their favourite distro on a phone
Even Sailfish OS isn't (thankfully!) that different from a "normal" Linux distro under the hood - just some additional mobile middleware and little optimizations/hacks here and there.
So I think running normal Linux distros on mobile devices should be genrally fine and could help Sailfish OS by more people working on mobile Linux distros (not embedded hacks).
But that doesn't mean it won't take time to actually get to regular distro (say Fedora/Debian/Arch/etc.) work on a mobile device in a usable form - you need to package and stabilize all the middleware, create touch interfaces for applications, etc.
Doable ? Certainly!
Fast ? Likely not.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader
Universal Components - a solution for native looking yet component set independent QML appliactions (QtQuick Controls 2 & Silica supported as backends)
| The Following 8 Users Say Thank You to MartinK For This Useful Post: | ||
|
|
2017-10-10
, 16:56
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#145
|
Reaching the $1.5 million milestone weeks ahead of schedule enables Purism to accelerate the production of the physical product. The company plans to move into hardware production as soon as possible to assemble a developer kit as well as initiate building the base software platform, which will be publicly available and open to the developer community.
https://puri.sm/posts/librem-5-phone...0percent-mark/
Also found this "new" video:
https://www.youtube.com/watch?v=emb3ImTFyIY
Last edited by mikecomputing; 2017-10-10 at 17:27.
https://puri.sm/posts/librem-5-phone...0percent-mark/
Also found this "new" video:
https://www.youtube.com/watch?v=emb3ImTFyIY
__________________
Keep safe and healthy
Keep safe and healthy
Last edited by mikecomputing; 2017-10-10 at 17:27.
| The Following 8 Users Say Thank You to mikecomputing For This Useful Post: | ||
|
|
2017-10-10
, 17:06
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#146
|
Originally Posted by olf
AFAIK PureOS itself is GTK :/ So I guess n900/neo fans would like it.
Has anybody heard or read about specific plans for the basic software stack and addressing the lack of "mobile" apps?
But personally think they should use Qt/QML instead of GTK.
Why? It simple:
Porting SFOS apps would be easier if they used Qt/QML. We also have Plasma mobile and Nemo mobile which also uses Qt/QML.
So I don't get why on earth use GTK nowdays on a mobile OS. It is easier write apps in QML/C++ than using C and some bindings(gtkmm/pygtk) since no one want to use lowlevel C this days when write apps. Also coders are lazy and want an IDE and QtCreator already in place. GTK has no "pro" IDE AFAIK. Many still prefer Vim(me also) but still if you want top make mobile apps fast you need an IDE with possibility to debug and so on.
I personally prefer QtCreator over bloatead Android studio. Jolla/Qt team has done a great job with QtCreator + mer tooolchain. So why invent the wheel and use GTK and some unknown IDE? I really don't get it.
Well let's see what happens...
Edit: it seems from the video above that they will provide some kind of framework for both GTK and Qt. Nice
__________________
Keep safe and healthy
Keep safe and healthy
Last edited by mikecomputing; 2017-10-10 at 17:40.
 |
|
2017-10-10
, 17:30
|
|
Posts: 141 |
Thanked: 1,530 times |
Joined on May 2011
@ Finland
|
#147
|
Originally Posted by olf
There was a post about a month ago on GNOME's desktop-devel-list looking for people interested in writing the mobile UI and asking if GNOME as a project was interested in participating. So, my guess is that they currently have nothing, not even the stack chosen. And that makes their funding campaign look really odd, because it implies they have a mobile OS. I get the impression what they actually have is a distro running stock GNOME 3 on ARM.
But while I wonder why many people are getting so excited about the Librems's hardware, the real conundrum to me is the software stack:
https://mail.gnome.org/archives/desk.../msg00011.html
| The Following 7 Users Say Thank You to otsaloma For This Useful Post: | ||
|
|
2017-10-10
, 17:41
|
|
Posts: 3,464 |
Thanked: 5,107 times |
Joined on Feb 2010
@ Gothenburg in Sweden
|
#148
|
Originally Posted by otsaloma
Check the video above it may give some more info. It seems they want to work near both Gnome and KDE community and make some "framework" for both...
There was a post about a month ago on GNOME's desktop-devel-list looking for people interested in writing the mobile UI and asking if GNOME as a project was interested in participating. So, my guess is that they currently have nothing, not even the stack chosen. And that makes their funding campaign look really odd, because it implies they have a mobile OS. I get the impression what they actually have is a distro running stock GNOME 3 on ARM.
https://mail.gnome.org/archives/desk.../msg00011.html
__________________
Keep safe and healthy
Keep safe and healthy
|
|
2017-10-10
, 20:06
|
|
Posts: 339 |
Thanked: 1,623 times |
Joined on Oct 2013
@ France
|
#149
|
Originally Posted by olf
Indeed, but there are not only architecture changes :
One should not expect too much performance gain by going from a ARM's low-end 32bit core (A9) to their low-end 64bit cores (A53 & A55): This is mostly 32 vs. 64bits, e.g. allowing for 4+ GBytes of RAM.
Even though ARM also designed a class of cores below that (i.e. the very-low-end 32bit A7 and 64bit A35), their midrange cores (32bit: A12 = A17, 64bit: A57 & A73) and especially their high-end cores (32bit: A15, 64bit: A72 & A75) are way faster.
only the higher range of iMx6 features the 4 cores, most only have one or two, whereas this mid range iMx8M have 4 cores. I can't find where I read that the iMx6 they where targeting had only 2 cores, I may have dreamed that one...
imx6 are limited to 1.2GHz whereas imx8 go to 1.5GHz.
And the A53 should be more power efficient.
But yeah, as said before, even the iMx8 is weaker than the octo-cores and the like found in Android flagships.
By the way, the higher range of iMx8 exist with 4xA53+2xA72, but is not targeted here. It probably costs a lot more.
 |
|
2017-10-10
, 23:36
|
|
Posts: 304 |
Thanked: 1,246 times |
Joined on Aug 2015
|
#150
|
Originally Posted by Zeta
They are considering to use the i.MX 8M Quad instead of the i.MX 6 Quad, i.e. this is just going from four low-end 32bit cores to four-low end 64bit cores, see Wikipedia.
[...] I can't find where I read that the iMx6 they where targeting had only 2 cores, [...]
Furthermore the Vivante GC7000 GPU used in all i.MX 8 versions currently has no FOSS driver support at all; I believe that is withholding them to do this change, as that work can hardly be achieved within the given timeframe of 15 to 24 months.
BTW, in contrast to that the FOSS driver and MESA support for the recent generation Qualcomm Adreno 5xx GPUs is mostly done, and done for Adreno 3xx and 4xx (what cannot be said for the older Vivante GPU generations either: still a lot of work to do for them).
Originally Posted by Zeta
The perceived performance for interactive uses comes primarily from single-thread performance, so that core-craze is hardly worth much beyond two cores and largely irrelevant beyond four cores.
[...] But yeah, as said before, even the iMx8 is weaker than the octo-cores and the like found in Android flagships. [...]
It is the effective average IPC (instructions per clock) and clock frequency of a core what matters (multiplied with each other): Thus modern high-end ARM cores have more than a threefold performance advantage compared to low-end ones, for each core.
Multiplying that with the number of cores effectively being used for your workload gives a rough estimate of the perceived performance difference!
Last edited by olf; 2017-10-11 at 07:20.
| The Following 4 Users Say Thank You to olf For This Useful Post: | ||
There is indeed a 4GB limit on 32-bit systems but it is per process. There is nothing stopping you designing a 32-bit machine with more that 4GB of RAM and a clever memory management system that can handle it. Each process would still be limited to 4GB but not the whole system.
Not that any of that matters (yet) to mobile systems. It's not like we have phones with more than 4GB sold in six-packs.
Русский военный корабль, иди нахуй!