I am running Sailfish OS on my Nexus 7 and when I use Android there is some lag. But when I use Sailfish there isn't. I know with ios they have rendering performance over apps and on Android its vice versa. Is sailfish doing the same?
DavidLattimerii said:
I am running Sailfish OS on my Nexus 7 and when I use Android there is some lag. But when I use Sailfish there isn't. I know with ios they have rendering performance over apps and on Android its vice versa. Is sailfish doing the same?
Click to expand...
Click to collapse
I can't answer you're question technically. But if you compare the specs of an android device and the jolla phone you'll see there is a huge difference. The sailfishos work on much lower hardware quite flawlessy and is not so ressource hungry than android.
It runs very smooth until it's memory is free... if you use a bit much of memory it start sometimes to lag a lot. It's a low memory problem around that the Jolla crew it's working, the next update (january 2015) hopefully will fix it.
DavidLattimerii said:
I am running Sailfish OS on my Nexus 7 and when I use Android there is some lag. But when I use Sailfish there isn't. I know with ios they have rendering performance over apps and on Android its vice versa. Is sailfish doing the same?
Click to expand...
Click to collapse
It clearly depends on your device(not exactly, the GPU drivers)
Some shaders can be more or less efficient depending on HW and the driver(not much for Sailfish as it uses LibHYBRIS)
You should note, that Sailfish OS does not run Java Virtual Machine. All apps are compiled to machine code. This makes Sailfish bleeding fast.
enedil said:
You should note, that Sailfish OS does not run Java Virtual Machine. All apps are compiled to machine code. This makes Sailfish bleeding fast.
Click to expand...
Click to collapse
It runs the Dalvik or ART JVM for Android compatibility.
Only if you run Android apps!
Sent from my iPhone using Tapatalk
enedil said:
Only if you run Android apps!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
You have to explicitly run it without Android support...
(if it ran it on demand, launch times would be terrible)
Related
Last night Google announced the Google Chrome open source OS.
This OS will be available for small ARM based devices up to full scale desktop/laptop x86 based devices. Google aims to create a nearly instant on OS with a high reliabilty and the ability to use the applications for Chrome in any (HTML5 Compatible?) browser on any other platform.
ANY WAY... ARM compatibility is nice
http://googleblog.blogspot.com/2009/07/introducing-google-chrome-os.html
Possible for it to run on the xperia?
dadeadman said:
Possible for it to run on the xperia?
Click to expand...
Click to collapse
Nobody knows. For now, it's just an initial announcement with no further details. We'll have to wait for them to release before we see, but it's basically just another window shell on top of a Linux kernel.
Which is fine with me. If google can release an OS that can be flexible enough for ARM to x86, and it WORKS, I'll be happy. I'd love to see a proper Linux ROM on our HTC devices.. it's a shame to be limited to a haret 'side boot' instead of a native ROM
l3it3r said:
Which is fine with me. If google can release an OS that can be flexible enough for ARM to x86, and it WORKS, I'll be happy. I'd love to see a proper Linux ROM on our HTC devices.. it's a shame to be limited to a haret 'side boot' instead of a native ROM
Click to expand...
Click to collapse
Considering WM devices have a REALLY bad habit of booting quite differently from maker to maker, I wouldn't be holding your breath for anything other than a haret based solution for quite some time...
Dear All,
Since Firefox OS will be HTML5 based, is this likely a failure? Take a look at Facebook failure when they create their android app using HTML5 and they decided will abandon this and goes native.
They just said HTML5 isn't fast yet although Android use Webkit (which faster than Gecko anyway).
I wonder how Firefox OS can handled complicated and bulky app like we already seen in playstore today.
Thanks
HTML5 can be faster
dels07 said:
Dear All,
Since Firefox OS will be HTML5 based, is this likely a failure? Take a look at Facebook failure when they create their android app using HTML5 and they decided will abandon this and goes native.
They just said HTML5 isn't fast yet although Android use Webkit (which faster than Gecko anyway).
I wonder how Firefox OS can handled complicated and bulky app like we already seen in playstore today.
Thanks
Click to expand...
Click to collapse
Regarding that, you should check out sencha's response to facebook. They built a HTML5 app, fastbook [ google it please, not allowed to post outside links .... yet ] that they say is faster and more feature rich than the native ones Facebook built after ditching HTML5.
HTML5 is not necessarily slower than native an especially since FirefoxOS will be doing away with the Dalvik Virtual Machine needed for android, it should have faster perfomance and fewer requirements.
The only way we can tell for sure is by running them and comparing so let FirefoxOS come out then do the comparison and pick whatever suits you
Faster than light
The point for FirefoxOS and Mozilla, it's that it implements WebApis that works with the Hardware of the devices that has installed FirefoxOS. All the WebApis are approved by the W3C, so don't worry about what it's better between native o web, the thing is how you develop your Apps, and how you implement the power of Gecko. Do you know how much frameworks and ways to make Web apps there are?
Ichigo said:
So, as you all know Android kitkat 4.4 came out recently. Along with it was ART, a replacement for Dalvik that promises faster and more efficient execution, better battery life, and a more fluid experience. ART stands for Android Runtime, and executes apps different than Dalvik. ART uses AOT to execute apps, which is pre-compiling bytecode into machine language when apps are first installed, turning them into truly native apps. ART still is still experimental currently, but let's discuss our opinions.
I know that when programming games for android, if it uses heavy 3D translations, you'll to use the NDK, coding in C or C++, allowing the app to run natively, and helps maintain frame rate and speed. Because the ART has apps running natively now, will it possibly help maintain framerate and speed better on lower-end devices? I know java is much slower slower than c++, but will running the java coded app natively help at all?
Anyways, share your opinions, ideas, or questions.
Click to expand...
Click to collapse
I don't know much about ART, but from what I heard this sounds awesome . I think that it is just crazy not to precompile the code into machine language, sure there is longer install times, but hey, the apps should run much faster.
The thing is that currently it is quite hard to try it out, even on KitKat (which I don't have yet). Would love to make a comparison between the two
Here are some benchmarks by Android Police: http://www.androidpolice.com/2013/1...ormance-wont-blow-away-today-will-get-better/
I hope that they will improve that method. If they do, it will be amazing.
Apps could much faster.
I do, however, like Java. One of the reasons why I prefer Android to Ubuntu Touch (which uses C++).
nikwen said:
Here are some benchmarks by Android Police: http://www.androidpolice.com/2013/1...ormance-wont-blow-away-today-will-get-better/
I hope that they will improve that method. If they do, it will be amazing.
Apps could much faster.
I do, however, like Java. One of the reasons why I prefer Android to Ubuntu Touch (which uses C++).
Click to expand...
Click to collapse
When KitKat comes to Nexus 4 I'll do some before/after benchmarking on MagicKeyboard (since it is fairly predictable and CPU intensive) - sounds quite promising.
PicomatStudios said:
When KitKat comes to Nexus 4 I'll do some before/after benchmarking on MagicKeyboard (since it is fairly predictable and CPU intensive) - sounds quite promising.
Click to expand...
Click to collapse
Kitkat is here on our Nexus 4s.
nikwen said:
Kitkat is here on our Nexus 4s.
Click to expand...
Click to collapse
Aw, yeah... I try to make a rule that wherever possible I use 'standard' build on our test devices, that way I can be sure I'm seeing what our users see
Depending how long it takes I might have a look !
PicomatStudios said:
Aw, yeah... I try to make a rule that wherever possible I use 'standard' build on our test devices, that way I can be sure I'm seeing what our users see
Depending how long it takes I might have a look !
Click to expand...
Click to collapse
Now the official ones are finally here.
nikwen said:
Now the official ones are finally here.
Click to expand...
Click to collapse
OK got it finally.
In a not particularly scientific test I tried typing the sentence
'The quick brown fox jumped over the lazy dog.'
into Magic Keyboard 2 (as many other apps as possible stopped, internet off, etc)
After each key press the app runs quite a large number of comparisons/calculations/bitshifts in a loop, in order to score the most likely word (CPU intensive work)
I only ran the test 3 times but there does seem to be an improvement with ART
Average prediction time for each configuration is:
Android 4.3:
20ms
Android 4.4 / Davlik:
19ms
Android 4.4 / ART:
15ms
From previous tests I know that the prediction times are fairly consistent.
Obviously the above is some way short of proof but early signs are good.
i am on android 4.4.4 with art runtime i haven't noticed any performance enactment and also not a single app cashing
Sent from my XT1022 using XDA Free mobile app
I found HTC Desire Z could run this new OS. How about our phone?
c786764052 said:
I found HTC Desire Z could run this new OS. How about our phone?
Click to expand...
Click to collapse
I think it is possible, but someone have to do it. Have you tried the Ubuntu on your DesireZ? I was exited when it came out but there was so much hassling to get it up and running so I settled down and begin to wait easier set up. Back then I used my DZ as daily driver so the requirement of ADB connection to run Ubuntu on the phone made it, well, non-portable which was no go for me. And in the mean time Flinny was making great Jelly Bean ROMs in form of CM11, which I was using. Around the Flinny's builds 14-18 I was switching back and fort with DesireZ and u8800pro, until I found that u8800pro could run the latest versions of the Android more smoothly.
But about the Ubuntu Touch, it was found laggy in DesireZ. Maybe because the Ubuntu suggest (or requires) the phone to have at least dual-core CPU. Our U8800Pro shares almost identical specs to DesireZ, little difference with CPU clock speed. At u8800pro runs at 1Ghz while DesireZ at 800Mhz. But with overclocking I have seen the u8800pro running at 1901Mhz and also DesireZ got around 1800/1900Mhz too. After all I still found the u8800pro run more smoothly at latest version of the Android (JB and KitKat). So maybe the Ubuntu will perform a little better in Huawei than in the HTC. But I consider porting the Ubuntu Touch for the u8800(pro) unnecessary, there is definitely a lot of things to fix which takes time and I'm sure it is going to be laggy anyway. We have to admit that this device is old, it can't run latest ROMs smoothly.
Lihis said:
I think it is possible, but someone have to do it. Have you tried the Ubuntu on your DesireZ? I was exited when it came out but there was so much hassling to get it up and running so I settled down and begin to wait easier set up. Back then I used my DZ as daily driver so the requirement of ADB connection to run Ubuntu on the phone made it, well, non-portable which was no go for me. And in the mean time Flinny was making great Jelly Bean ROMs in form of CM11, which I was using. Around the Flinny's builds 14-18 I was switching back and fort with DesireZ and u8800pro, until I found that u8800pro could run the latest versions of the Android more smoothly.
But about the Ubuntu Touch, it was found laggy in DesireZ. Maybe because the Ubuntu suggest (or requires) the phone to have at least dual-core CPU. Our U8800Pro shares almost identical specs to DesireZ, little difference with CPU clock speed. At u8800pro runs at 1Mhz while DesireZ at 800Mhz. But with overclocking I have seen the u8800pro running at 1901Mhz and also DesireZ got around 1800/1900Mhz too. After all I still found the u8800pro run more smoothly at latest version of the Android (JB and KitKat). So maybe the Ubuntu will perform a little better in Huawei than in the HTC. But I consider porting the Ubuntu Touch for the u8800(pro) unnecessary, there is definitely a lot of things to fix which takes time and I'm sure it is going to be laggy anyway. We have to admit that this device is old, it can't run latest ROMs smoothly.
Click to expand...
Click to collapse
I don't have a Desire Z,so I never tried.
I think you are right,Ubuntu will not be as smooth as Android on our old devices.
I have a Xperia Z1 now.Hope I can experience this new OS someday,I'm quite interested in the Ubuntu.
Sent from my IDEOS X5 using XDA Free mobile app
c786764052 said:
I don't have a Desire Z,so I never tried.
I think you are right,Ubuntu will not be as smooth as Android on our old devices.
I have a Xperia Z1 now.Hope I can experience this new OS someday,I'm quite interested in the Ubuntu.
Sent from my IDEOS X5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm interested about Ubuntu phone too. Shame that Indiegogo campaign didn't raised the amount of funds what Canonical was requesting. Have you read of this: Meizu MX4 with Ubuntu Touch makes an appearance ? Looks pretty neat. So in that manner it would be nice to have some kind of Ubuntu Touch port to test the user interface and make some kind of opinion is it good to use etc. before going to buy eg. that phone. As I think I have to wait very long time before that or other Ubuntu phones hits to stores here where I live.
So I know the Nexus Player has an atom processor, so its running some form of Android x86. I have an Asus Chromebox, which I have previously loaded up with Android x86 in the past. Does anyone know if there is a way to get the Android TV interface on generic Android x86, or is Google doing something different here (and not entirely open sourced)? I am pretty interesting in trying to get the Android TV experience on the Chromebox to see how well that works.
-If this should be in one of the dev areas please feel free to point me in that direction.
It is (kinda) possible.
You need to be running Android 5.0+ already and then the Leanback Launcher can be installed (it's working on my Nexus 5 and on my oDroid C1 running 5.1)
Be aware that it's not a perfect solution
koperniczx3 said:
It is (kinda) possible.
You need to be running Android 5.0+ already and then the Leanback Launcher can be installed (it's working on my Nexus 5 and on my oDroid C1 running 5.1)
Be aware that it's not a perfect solution
Click to expand...
Click to collapse
Thanks for the tip.
In your case, on an oDroid, you'll still be running an arm variant of android. When you say its not perfect, what exactly isn't working?
I've read on the android x86 project's forum that video playback is an issue on Android 5.0 and up, as recently as May of this year. Need to find some more recent threads regarding that, and determine how well supported Intel's graphic drivers are in Android. I know the Nexus Player is using a 3rd party gpu.
Separately, just so I understand, is Android TV just essentially stock Android with the leanback UI and Launcher?