Related
Can anyone who has done i9000 teardown confirm if this analysis is correct?
512MB SLC Nand, and (384MB LPDDR [2 piece 166Mhz Mobile DDR] + 128 MB Nand) OneNand, all packaged on a MPC with the PowerVr+Hummingbird core.
Then a 16GB piece MoviNand (samsung's version of MLC based eMMC), all manufactured by samsung.
If it's right, then all the galaxy s phones (i9000(m), vibrant, captivate.. etc) only have 512MB of true fast Nand rom, could be the cause of the lag issues.
Although I don't have a teardown of the Fascinate and Epic, I'd assume they are the same as the GSM versions, with the exception of a 1GB/2GB MLC nand replacing the 16GB MoviNand (ie. they have only 512MB SLC Nand too).
Samsung is very smart when it comes to lowering the BoM and ip costs in building this high spec android phone.
By comparison, SE Xperia X10 has a 2x512MB (1GB total) fast Micron SLC Nand rom, 3 piece 384MB of LPDDR (166Mhz, x16*2+x32) higher bandwidth than i9000's. Nand + Ram made by Micron (which makes superior ic's compared to samsung).
HD2, and Sprint Evo 4G all have the same MCP made by Hynix; Google Nexus One and Htc desire share a MCP made by samsung, even though they have different specified Ram amounts (512MB vs 576MB), could be caused by the different allocations of available OneNand?
It is very likely, that the minimum requirement for Android 3.o is not 512MB ram, but 512MB rom, (Android, like Maemo, is very good at memory management). I'd say that the Sony Ericsson Xperia X10 is actually more "future proof" than the i9000, and the HTC phones released so far.
I'm curious too. I thought this phone had 512MB of RAM...
Sent from my SAMSUNG-SGH-I897 using XDA App
As described in the lag fix topics! is that they are not using slow nand but the filesystem is causing the lag!
Out of curiosity, what does your nickname stand for.. Sony Ericsson MC? There is a blog I noticed called SEMC.. I only ask because it clearly creates a conflict of interest for you to decide between both devices fairly.
NAND imho is considered to be flash, not RAM. Samsung officially said that they had 512MB RAM, and they seem to consider NAND to be flash too. In the case this unit didn't have 512MB LPDDR, it would mean they lied during the announcement: http://www.samsung.com/ph/news/newsRead.do?news_seq=19925&gltype=globalnews , as the OneNAND/MoviNand site differentiates between flash and RAM too. I have emailed them though to ask specifically.
In regards to Micron vs Samsung RAM quality, to be honest, when working at an apple reseller, we didn't really have trouble with either. Both are fine, and Apple themselves went through various types of RAM (including Hynix and Samsung). We didn't notice any serious issues with either. Perhaps there is a difference when overclocking, but I hardly imagine anyone will use the phones after overclocking them much (although, someone already overclocked theirs to 1.6GHZ). Overclocking eats up battery life...
You forget that the i9000 has a MUCH faster GPU (90million triangles vs the X10 one), 802.11n, BT3 and REAL multitouch (if the SE gets multitouch, it will be a shonky hack with serious flaws that make it unusable for anything but pinching gestures). Where did you get your teardown specs from? Anyway, the truth of the matter, is that it depends what you need to do. But in almost any synthetic benchmark at the moment (not that they matter), Galaxy S is ahead.
It doesn't matter how great the X10 is anyway, because by the time it gets 2.1, Android 3 will probably be out. In fact, knowing Sony Ericson, you'll be lucky to get 2.2 (used to own a K750i, which was a W800 with crippled software, thanks Sony Ericcson). Honestly, Android 1.6 is close-to-ancient, and no developer is going to seriously buy a phone which runs such an old version of Android still (2.0, possibly, 2.1 yeah ok, 2.2... YAAAAAA).
So theoretically, maybe (I haven't seen the proof myself though). But, in reality, I'd expect the Galaxy S to have a longer useful timespan.. The X10 was announced 9 months ago. Google coded at least 2 major versions of Android within that time (and performed full QA too). So, the X10 is certainly NOT a phone I'd recommend. Whether or not it supports it, it is unlikely Sony ericsson will port Android 3 to it. They still haven't even ported Android 2.x to it yet, and it is their flagship Android mobile phone. And the X10 likely never attracted the kind of people who will port Android 3 by themselves, because they are also the kind of people who were unimpressed with the version of Android it shipped with.
Oh, and by the way, the lag likely isn't because of the RAM. There seems to be other factors at play (bad scheduling for instance would explain why GPS also goes funky sometimes, music skips at the beginning using doubletwist and the lag).
I think the OP was just using the Xperia for illustrative purposes. No one who has used both units will make a qualitative comparison between the X10 and the Galaxy S, which is in a different league.
Ultimately, it was not just Android 1.6 that made me sell my X10, but its horrible call quality, low 384Mb RAM (not so good for Gingerbread, which SE might never release anyway), and mediocre touch sensors that did it. It's a shame because with some tweaks, the X10 could have been spectacular. I do love its external design, 854x480 res., and excellent camera.
andrewluecke said:
(although, someone already overclocked theirs to 1.6GHZ). Overclocking eats up battery life...
Click to expand...
Click to collapse
Source? I read that the cpu is capable of going to 1.6ghz, but I haven't read anyone actually OC to 1.6ghz.
In Canada, the retail prices between the Galaxy S ($500) and the Xperia 10 ($550) are actually laughable. Rogers and SE will have to do a BIG price drop ASAP.
INeedYourHelp said:
Source? I read that the cpu is capable of going to 1.6ghz, but I haven't read anyone actually OC to 1.6ghz.
Click to expand...
Click to collapse
You are correct.. Must have read the headline from Reddit or something dodgy.
Also, I don't think the poster is using the Xperia X10 as an example, because he posted the same message, but also on the Xperia X10 board.. By the sounds of things, he could be working on an article (in which case he should probably pull the phones apart himself), or it sounds a tad like marketing. Or possibly neither...
Here is interesting reading: http://forum.xda-developers.com/showthread.php?t=752617
Saying that the X10 is ahead of the SGS is plain wrong, that device it self has NO support for multi-touch and wont be getting one anytime soon.
SEMC said:
Can anyone who has done i9000 teardown confirm if this analysis is correct?
512MB SLC Nand, and (384MB LPDDR [2 piece 166Mhz Mobile DDR] + 128 MB Nand) OneNand, all packaged on a MPC with the PowerVr+Hummingbird core.
Then a 16GB piece MoviNand (samsung's version of MLC based eMMC), all manufactured by samsung.
If it's right, then all the galaxy s phones (i9000(m), vibrant, captivate.. etc) only have 512MB of true fast Nand rom, could be the cause of the lag issues.
Although I don't have a teardown of the Fascinate and Epic, I'd assume they are the same as the GSM versions, with the exception of a 1GB/2GB MLC nand replacing the 16GB MoviNand (ie. they have only 512MB SLC Nand too).
Samsung is very smart when it comes to lowering the BoM and ip costs in building this high spec android phone.
By comparison, SE Xperia X10 has a 2x512MB (1GB total) fast Micron SLC Nand rom, 3 piece 384MB of LPDDR (166Mhz, x16*2+x32) higher bandwidth than i9000's. Nand + Ram made by Micron (which makes superior ic's compared to samsung).
HD2, and Sprint Evo 4G all have the same MCP made by Hynix; Google Nexus One and Htc desire share a MCP made by samsung, even though they have different specified Ram amounts (512MB vs 576MB), could be caused by the different allocations of available OneNand?
It is very likely, that the minimum requirement for Android 3.o is not 512MB ram, but 512MB rom, (Android, like Maemo, is very good at memory management). I'd say that the Sony Ericsson Xperia X10 is actually more "future proof" than the i9000, and the HTC phones released so far.
Click to expand...
Click to collapse
Sorry to thread necro, but I'm from the Samsung Epic 4G forums and just ran across your thread because it was linked in an RFS vs EXT4 debate that's been raging for the last week or so.
I believe that you're close in your hardware analysis, the Galaxy S phones have 384 MB of LPDDR (I theorized DDR-400) but I believe instead of 128 MB of NAND, it's actually 128 MB of OneDRAM, which is a Samsung high-speed hybrid memory solution. I've seen teardowns that described a mystery NAND module and I'm pretty sure the OneDRAM is it.
Anyhow, here's my thread about it: I think it's likely that the I9000 uses more or less the same RAM configuration.
http://forum.xda-developers.com/showthread.php?t=886793
Sorry for bringing this up but it is the only revelant thread to my question..Along with the SGS I also have a Desire HD.I noticed in quadrant (I know it doesn't count but I'm just being curious) that in memory benchmark the SGS scores about 1800 points while the DHD 1000-1100..Assuming they're both equipped with LPDDR1 memory modules, what favours the SGS to have better performance?
From teardown of i9000, it has:
512MB SLC Nand, and (384MB LPDDR + 128 MB [2 piece 166Mhz Mobile DDR] ) OneNand, all packaged on a MPC with the PowerVr+Hummingbird core.
Then a 16GB piece MoviNand (samsung's version of MLC based eMMC), all manufactured by samsung.
If it's right, then all the galaxy s phones (i9000(m), vibrant, captivate.. etc) only have 512MB of true fast Nand rom, could be the cause of the lag issues.
Although I don't have a teardown of the Fascinate and Epic, I'd assume they are the same as the GSM versions, with the exception of a 1GB/2GB MLC nand replacing the 16GB MoviNand (ie. they have only 512MB SLC Nand too).
Samsung is very smart when it comes to lowering the BoM and ip costs in building this high spec android phone.
By comparison, SE Xperia X10 has a 2x512MB (1GB total) fast Micron SLC Nand rom, 3 piece 384MB of LPDDR (166Mhz, x16*2+x32) higher bandwidth than i9000's. Nand + Ram made by Micron (which makes superior ic's compared to samsung).
HD2, and Sprint Evo 4G all have the same MCP made by Hynix; Google Nexus One and Htc desire share a MCP made by samsung, even though they have different specified Ram amounts (512MB vs 576MB), could be caused by the different allocations of available OneNand?
It is very likely, that the minimum requirement for Android 3.o is not 512MB ram, but 512MB rom, (Android, like Maemo, is very good at memory management). I'd say that the Sony Ericsson Xperia X10 is actually more "future proof" than the i9000, and the HTC phones released so far.
hopefully what you analyzed is true! I really don't want 2.1 to be the last software update on my X10.
SEMC said:
It is very likely, that the minimum requirement for Android 3.o is not 512MB ram, but 512MB rom, (Android, like Maemo, is very good at memory management). I'd say that the Sony Ericsson Xperia X10 is actually more "future proof" than the i9000, and the HTC phones released so far.
Click to expand...
Click to collapse
You had me until here. There is no "minimum requirement" listed for Android 3.0, since it hasn't been announced yet.
iead1 said:
You had me until here. There is no "minimum requirement" listed for Android 3.0, since it hasn't been announced yet.
Click to expand...
Click to collapse
No, the next version of android hasn't been officially announced, but I think you'll find that future android devices running high end branch of android from SE (and other manufactures) will at least 1GB of nand rom.
SE Xperia X10 has a 2x512MB (1GB total) fast Micron SLC Nand rom
Click to expand...
Click to collapse
can anyone explain me this part .....
For example, an OMAP4440 based 864*480 (Sharp panel for SE, a first i think ) device that's in the works ...
This may be pulling the strings bit too far but are U max from esato?
If yes, is there any truth in the psp phone rumor? Also, what are the next devices, the X10 successors lined up for in terms of Processor and GPU?
Also the galaxy S has a better CPU and GFX card, so the better RAm in the X10 wont do to make it more future proof.
Yes, SE will release Gingerbread for X10 in 2013 - after the machines take over.
More than any device specs holding back updates for existing phones is that SE & others don't want to give you a free update. Why would they want to provide you with a update to prolong the life of your phone, when they could sell you or your provider a new one for actual money . Future proof is a myth built in obsolescence is the reality.
Am I correct in assuming you are associated with Sony Ericcson somehow (SE-MC as your nick)? I only ask because it clearly creates a conflict of interest for you to decide between both devices fairly.
NAND imho is considered to be flash, not RAM. Samsung officially said that they had 512MB RAM. In the case this unit didn't have 512MB LPDDR, it would mean they lied during the announcement: http://www.samsung.com/ph/news/newsR...ype=globalnews , as the OneNAND/MoviNand site differentiates between flash and RAM too. I have emailed them though to ask specifically.
We never really had issues with Micron or Samsung RAM at the Apple reseller I worked at. Micron might possibly be better, but you probably wont notice any differences unless you start over-clocking.
You forget that the i9000 has a MUCH faster GPU (90million triangles vs the X10 one), 802.11n, BT3 and REAL multitouch. Also, if you are writing an article, shouldn't you perform your own teardown so you can be 100% sure of what you are writing about? Anyway, in almost any synthetic benchmark at the moment (not that they matter), Galaxy S is ahead. The X10 however is probably ahead in photo quality.
Both phones are suited towards different audiences really, and both have their own benefits. I'd expect the Galaxy S to have a longer useful timespan though.. Sony Ericsson 9 months after announcement have announced plenty of new phones, but haven't even updated Android to 2.0. They clearly have the resources, but their priorities seem to be capturing more of the market, rather than helping their existing customers. If anything, SE's attitude suggests A3 wont be ported to the X10. The X10 likely never attracted the kind of people who will port Android 3 by themselves either (1.6 is too old for developers). Sony Ericsson also have a strong history of using software to upsell customers.
Anyway, it depends on what your requirements are. Neither Sony Ericsson nor Samsung are known for great long term software support, ROM's for Froyo have already been leaked by Samsung for the Galaxy S, whereas, there is very little evidence that SE are actively working on upgrading theirs (seriously, by now they should have at least gotten 2.0).
Despite my uses for a camera Flash, I ended up settling on the Galaxy S though. It's up to people to make their own choice, but I personally believe that the SE is the better long term choice.
Yes, SE will release Gingerbread for X10 in 2013 - after the machines take over.
Click to expand...
Click to collapse
Impossible cause the worlds gonna end in 2012. No Gingerbread for us x10 users.
Sent from my X10a using Tapatalk
se_dude said:
is there any truth in the psp phone rumor? Also, what are the next devices, the X10 successors lined up for in terms of Processor and GPU?
Click to expand...
Click to collapse
Not very likely is it, with psp neXt gen coming . The 2 divisions operates quite independently. However, an android device (running a 'high end' branch of android ) is currently in internal testing, based on TI's OMAP4400 series, and paired with LPDDR2 I believe, since the performance put that of samsung's i9000 to shame. I don't know if this is the *supposed* psp phone, but it does have an unusually wide aspect ratio screen (864*480) which could suggest a gaming 'portal' is coming to select future se devices.
andrewluecke said:
NAND imho is considered to be flash, not RAM. Samsung officially said that they had 512MB RAM. In the case this unit didn't have 512MB LPDDR, it would mean they lied during the announcement: http://www.samsung.com/ph/news/newsR...ype=globalnews , as the OneNAND/MoviNand site differentiates between flash and RAM too. I have emailed them though to ask specifically.
Click to expand...
Click to collapse
Nand is not 'considered' to be flash, it is flash. OneNand is just a mcp with 'flash' + ram. The problem is, on samsung mobile's own devices, i9000 in particular, are some custom mcp's that are not publicly available. There are some mcp's used here which have comparable public offerings (from samsung semi), the application processor for example; but even they are slightly different. Making analysis a bit painful, some purely based on experience.
I have a X10a but let's face it.
Galaxy S is the better smartphone now and will be in Q4 too.
While X10 will run 2.1, Galaxy S will run 2.2 which will give better performance.
Who cares about long distant future?
Next year, this time, probably only 20% of the current X10 'geek' owners will still have the X10.
The rest will move to better smartphones 1.2Ghz, 1.5Ghz, dual core, etc.
The usual, non geek, owner won't care anyway if he has 1.6, 2.1, 2.2, 3.0, etc as hong as he can make calls, listen a few mp3s and take some nice snapshots.
Even the galaxy s has a life span so don't think that it will get 3.0 since Samsung support stinks
Sent from my X10a
If Android 3.0 will be "standalone" (only rumour yet) you dont need SE to install it in the X10.
Yes, the i9000 have better specifications, better graphic card, but and the construction? next year, half will had problems... they are having problems now.
I have changed HTC to SE because of all the problems i had with HTC, GPS no working, vibrate not working, etc etc... i'm tired of these problems.
consolation said:
Yes, SE will release Gingerbread for X10 in 2013 - after the machines take over.
Click to expand...
Click to collapse
At 8:30 am, SE became self aware.
anjo2 said:
If Android 3.0 will be "standalone" (only rumour yet) you dont need SE to install it.
Click to expand...
Click to collapse
Not with with a locked bootloader you won't!
andrewluecke said:
You forget that the i9000 has a MUCH faster GPU (90million triangles vs the X10 one)
Click to expand...
Click to collapse
Bah... you should consider stopping repeating other people's **** when it makes no sense.
According to those numbers, that phone is like 2 times faster than a GameCube
Now if you look at GLBenchmark, it's not quite 90 millions per second, but more like 7 millions textured triangles per second while the snapdragon seems to cap at around 2 millions in all tests, and the older power VR in the droid does 2.5 millions.
The Galaxy S is thus quite faster in those benchmark.
Now that's a benchmark, in actual games/apps, you don't care about that, what you want is your framerate to stay higher than 30fps, and in this case what you get is more like 30.000 textured and lit tris per frame max on a snapdragon (X10), 37.000 tris on a PowerVR (moto droid) and around 65.000 on a Galaxy S.
So it's certainly faster like a bit more than 2 times faster than the older snapdragon, but those "90 millions triangles per second" are totally made up.
SEMC said:
Nand is not 'considered' to be flash, it is flash. OneNand is just a mcp with 'flash' + ram. The problem is, on samsung mobile's own devices, i9000 in particular, are some custom mcp's that are not publicly available. There are some mcp's used here which have comparable public offerings (from samsung semi), the application processor for example; but even they are slightly different. Making analysis a bit painful, some purely based on experience.
Click to expand...
Click to collapse
Or assumptions/guessing, as it seems to be in this case..
According to Microsoft QSD8250 is the chipset. Now how bad is it? I see people are saying it'd be better than HD2 since it'll have the perfect drivers from MS, but still wonder how this compare with the phone I am planning to get, Captivate, or an iPhone 4.
What prompted MS to choose this over so many newer (and possibly better) options?
rexian said:
What prompted MS to choose this over so many newer (and possibly better) options?
Click to expand...
Click to collapse
My guess: WP7 has been in development for quite some time, so at the start of development they choose the top processor that was available. But I think that this forum focuses to much on the processor and specifications, because in the end, the whole package must be convincing and that includes the operating system that has been optimized for this processor.
Furthermore, the current specifications will be the lowest common denominator for quiet some time (perhaps until WP8) and all apps will be optimized to run satisfactory on this specification (AFAIK the 20 second start-up rule for apps will be measured with the current specification). Newer processors may speed some things up, but the current hardware will be the target platform...
The development must have started before this chipset was launched, but you are right - this was most likely the target platform.
There are not many 3D games available though, the basic working will be fluid I know when I check at the store in few days. My worries are about the 3D games that will be launched later. If the experience with those is not as good as other platforms, MS will be in trouble. Better hardware will fix the issue in future but the reputation will be ruined and be stuck for a while.
Captivate is more powerful, mainly due to its GPU being about 4 times more powerful than the qsd8250s adreno200 gpu. Though, all WP7 devices will have better looking games since Captivate runs android... And everyone knows android games look crap, no matter how how powerful the hardware is (due to devs having to make their devices run on low end hardware to get more sales)
The IP4 is a better comparison because it's hardware and software have been fully engineered to run along each other, very much like WP7 devices. While it does have a more powerful GPU compared with the QSD, there wouldn't be much difference; the adreno 200 pushes about 22million triangles per sec, where as the sgx535 pushes about 28million triangles per sec. Whether developers even use all those polygons, I'm not sure I've seen.
Though epic citadel on iOS as well as this upcoming game called Aralon sure looks good.
Aralon link: http://www.gizmodo.com.au/2010/10/oh-man-aralon-for-ios-is-gonna-be-good/
Thanks Cruzer. Now it makes sense. 22 mil vs 28 mil is not a big difference. Were they running at the same clock-speed? I hear A4 processor in iPhone 4 runs at ~800MHz, so may be they both perform in a similar manner.
Not sure how much the GPU is affected by the CPU. I think it's more to do about the speed of the actual GPU, but don't take me on that quote lol.
I have a Captivate and an iPhone 4. Im getting rid of both of them to get a HD7 or Focus. The iphone works flawlessly and isnt buggy in the slightest bit, the captivate is very choppy and i couldnt take it after a while with the lagging even after i upgraded to froyo. I would go with wp7 to be different and because it looks fun even if it uses an older processor. The hummingbird and A4 are both top of the line and its going to be hard to compete especially with each having a different os.
Writing this from my iphone 4
So many froyo roms in development section, but still Vibrant showing 324 (more or less) of ram available? Isn't froyo suppose to fee that part of ram up that is not being used in eclair?
I think some of it is reserved for the GPU
Sent from my SGH-T959 using XDA App
There's a thread in the i9000 section about this. The short version is that all that RAM you can't see is reserved for various parts of the device to use. The radio uses some, the camera uses some, the GPU, etc.. It sucks that that memory is reserved even if you aren't using the GPU, for example, but that's how it is. They have a kernel patch over there that attempts to free up some of it by reducing the allocations. It seems to work without causing problems, but time will tell.
So the answer to the question is NEVER. There is 512MB of RAM in the device, but you won't be able to use all 512MB for user progams ever. This is no different than most off the shelf computers, they advertise 4GB of RAM, but the internal graphics takes 512MB, and other devices in the machine often do the same thing. Would it be nice if manufacturers wern't allowed to advertise this way? Maybe. However, Samsung isn't doing anything that isn't "industry standard". IMO they should all be advertising user-available RAM rather than installed RAM, but then people would ***** that the OS takes up some RAM, so you will never make everyone happy.
I would be unhappy if I thought we needed more RAM, but honestly I've never seen my Vibrant even get close to low.
I don't mind the RAM issue as I'm not having issues (yet), what I don't like is the internal storage.
On the Vibrant it's not too bad since we have 16GB, but for something like the G2 where they advertise it as 4GB, but you only have access to ~1.5, that's just not cool!
Eventually there'll probably be some kernel tweaks or something that'll free up some of that internal RAM, but I don't forsee anyone coding for it until they actually need it themselves (nothing speeds up development more than personal interest....why do you think the dev ROMs are so much better than the Samsung ones).
Jolla will be announcing a new phone, you may have heard of this, will be announced tomorrow (20/05/13 at 4:30pm GMT), here is a live stream to the event I found from the Jolla official twitter account. #IAmTheOtherHalf
From what I have heard the screen will be no larger than 5" in size, and will likely get a physical slide out qwerty keyboard, don't quote me on this, just from research, that is all I found
It's 5/20 not 5/13. The only thing we know is Engadget guessed it was 5 inches from when Marc partially took it out of his pocket.
aironeous said:
It's 5/20 not 5/13. The only thing we know is Engadget guessed it was 5 inches from when Marc partially took it out of his pocket.
Click to expand...
Click to collapse
some people in different countries represent the date in different ways, I did day/month/year as I am from UK.
UPDATE:
4.5" screen (unknown resolution at this time, known to be HD so either 720p or 1080p
dual core processor (unknown clock speed)
unknown RAM
unknown GPU
8mp AF camera
seems to have a front facing camera of unknown mp count.
replaceable battery
4G (LTE)
16GB + microsd card expandability
unknown battery size/life
(All specs quoted from jolla website)
disappointed that it is not quad core but as the OS is based on C++, efficiency will be much better than Android, providing the RAM is of decent size and the GPU is good, it shouldn't make that much difference speed wise, also doesn't seem to have a qwerty keyboard (only reason why I thought it would is that, one of the guys at Jolla in an interview, stated that more phones should have a physical qwerty keyboard.)
i am waiting for jolla :laugh:
nh1402 said:
some people in different countries represent the date in different ways, I did day/month/year as I am from UK.
UPDATE:
4.5" screen (unknown resolution at this time, known to be HD so either 720p or 1080p
dual core processor (unknown clock speed)
unknown RAM
unknown GPU
8mp AF camera
seems to have a front facing camera of unknown mp count.
replaceable battery
4G (LTE)
16GB + microsd card expandability
unknown battery size/life
(All specs quoted from jolla website)
disappointed that it is not quad core but as the OS is based on C++, efficiency will be much better than Android, providing the RAM is of decent size and the GPU is good, it shouldn't make that much difference speed wise, also doesn't seem to have a qwerty keyboard (only reason why I thought it would is that, one of the guys at Jolla in an interview, stated that more phones should have a physical qwerty keyboard.)
Click to expand...
Click to collapse
Quad core doesn't really matter in Android as the OS itself currently only supports 2, apps have to specifically use the extra cores, and only a few games do. I believe KLP is supposed to change that to "N" cores (along with full Intel support). Because Android used a VM, it is RAM that makes the biggest difference. That is why iOS and WP7/8 are so smooth with much lower RAM than Android.
I have read, and anyone can correct me on this, that KLP is the start of moving away from Dalvik and will support ARM and x86 natively with fat binaries. This is the rumour why KLP was not released at I/O, because they are re-writing the OS as native.
As you mentioned, Sailfish is a native OS, it won't need as high of specs as Android, which also means cheaper phones (in theory).
I was just saying future proof wise, if their OS supports Quad-Core, and they provide one in their first phone, they could just stick with this phone for a while, as it wouldn't need to be updated yearly, to keep with the competition. The phone as of the last time I checked had the equivalent price of £350, which is more than a Nexus 4, and yet that has a quad core processor, I have mentioned that to Jolla via their support page, and will be releasing more details as the release date gets closer, the main thing that was a huge turn off for me was not the Quad Core processor as much but the MASSIVE Bezel around the 4.5" screen, but then found out that the final design of the phone will have a smaller bezel, as mentioned by the lead designer at Jolla.
If they want anyone to buy their phone, it just has to be cheaper. Nokia made pretty good inroads with their Lumia devices by making them very inexpensive (and often free) on contract. Windows Phone is now at 5% market share, and it is almost entirely Lumia devices. With Jolla being former Nokia people, hopefully they will understand this instead of making the mistake Palm did with the Prē
Sent from my Nexus 4 using xda premium