I don't have a Galaxy S, but I wonder:
Samsung released their Samsung Moment 2.1 ROM with the Lib's NOT optimized for the ARM-11 architecture. Can someone find out if the 2.1 AND the 2.2 ROMs for the SGS are optimized for the Cortex-A8 instruction set WITH Neon?
(I planned to compile them from scratch once I got my SGS, but I figured someone might know.)
EDIT: After further research, I've come to the conclusion that the Moment's lib's were optimized for ARM-11 but not for VFP. I wonder if NEON is enabled on the Galaxy S?
Related
http://images.anandtech.com/graphs/graph4177/35412.png
Some of you might know, the Galaxy S uses the PowerVR SGX-540 GPU, which will be in the upcoming Omap 4 SoC. And Samsung decided to switch from PowerVR to ARM for the GPU in the SoC, the Mali-400. The image you see is the early benchmarks of that new SoC, the Samsung Exynos SoC (formally Orion). My friend shared the image and right now he's not here for me to link the original site, but i'll edit that in later. Also as a note that mali chip is currently at 65nm in the benchmarks, the final chip will be in 40nm? But still, as someone who has been excited to see "5x the performance of the galaxy s" idc if it's an early build, I'm still
How about you guys?
information like this is suspect and rife with no base standard so it little or no meaning. The other phones are upgrades and most likely have tweaks of varying degrees. So this provides really nothing........ Beside the TMO Vibrant is at the top of most of the bench tests t to see the fascinate so much above...... mames one question the test results
kanwal236 said:
http://images.anandtech.com/graphs/graph4177/35412.png
Some of you might know, the Galaxy S uses the PowerVR SGX-540 GPU, which will be in the upcoming Omap 4 SoC. And Samsung decided to switch from PowerVR to ARM for the GPU in the SoC, the Mali-400. The image you see is the early benchmarks of that new SoC, the Samsung Exynos SoC (formally Orion). My friend shared the image and right now he's not here for me to link the original site, but i'll edit that in later. Also as a note that mali chip is currently at 65nm in the benchmarks, the final chip will be in 40nm? But still, as someone who has been excited to see "5x the performance of the galaxy s" idc if it's an early build, I'm still
How about you guys?
Click to expand...
Click to collapse
Wow the Tegra 2 doesn't beat the SGX-540 by much talking about making a powerful phone,wow the Galaxy S is a damn powerful phone,now if game companies tarted to actually use its powerful GPU,it would be great.
Extremely interesting, this.
Well, I hope it gets better as Samsung updates the software, drivers and other parts of the UI. (lolz)
Take a closer look at the benchmark, this is a graphics benchmark. The cpu itself has great performance, but what made the S so great was that it had the best gpu, no game lagged. Samsung is changing up the gpu provider and the new one benchmarks lower than the S, by final release at most they could hope for is getting the same performance in graphics. But the point is, samsung promised 5x the graphics performance, we're currently at half.
Sent from my SXY-T959
Are you surprised?
Is all the 2.2 roms for vibrant JIT Optimization enabled?
I heard that JIT would make our Vibrant more fast....
seems not, jit in 2.2 only optimized for some cpus, the cpu vibrant used is been optimized in android 2.3, same as nexus s
2.2 has jit. jit typically improves performance on all phones running it, but jit's improvements are dependent on what app you are running.
the reason jit isn't apparent on our phones is due to pretty much 2 reasons.
1) is due to how samsung built the CPU in our phones.
While it is arm a8 based, there are other things companies add to it to make it more targeted. Samsung designed part of this different than qalcom did.
2) Google's coding
Google implemented jit with a "spcific" generalization for it (i.e, they kinda based it around qalcom cpu's). Since the vibrant had a different implementation of a specific feature that benifited from jit, the jit optimization was rendered "unoptimised" and therefore we have a "slower" jit effect.
In real world practice, jit doesn't help our phones that much, it's more synthetic.
geoffcorey said:
the reason jit isn't apparent on our phones is due to pretty much 2 reasons.
1) is due to how samsung built the CPU in our phones.
While it is arm a8 based, there are other things companies add to it to make it more targeted. Samsung designed part of this different than qalcom did.
2) Google's coding
Google implemented jit with a "spcific" generalization for it (i.e, they kinda based it around qalcom cpu's). Since the vibrant had a different implementation of a specific feature that benifited from jit, the jit optimization was rendered "unoptimised" and therefore we have a "slower" jit effect.
In real world practice, jit doesn't help our phones that much, it's more synthetic.
Click to expand...
Click to collapse
i'm curious where you are getting this info... cause i can't find anything from google saying they optimized jit for the snapdragon.
snapdragon and hummingbird use the same isa, so while the hw implementation is different that shouldn't realistically have much impact on performance.
but that isn't as relevant as the fact that jit is reducing the necessity to interpret (and reinterpret) code which is where a lot of the performance benefits of jit are.
funeralthirst said:
i'm curious where you are getting this info... cause i can't find anything from google saying they optimized jit for the snapdragon.
snapdragon and hummingbird use the same isa, so while the hw implementation is different that shouldn't realistically have much impact on performance.
but that isn't as relevant as the fact that jit is reducing the necessity to interpret (and reinterpret) code which is where a lot of the performance benefits of jit are.
Click to expand...
Click to collapse
iirc humming bird and snapdragon (well qalcom chips for the most part) implement SIMD is different bit sizes.
qalcom uses 128bit while hummingbird uses 64bit. Since google worked with a lot of qalcom chips, i'm assuming the 2.2 jit was optimized more for the higher bit length SIMD than what samsung used. With 2.3, google optimized for larger and smaller SIMD bit lengths.
geoffcorey said:
iirc humming bird and snapdragon (well qalcom chips for the most part) implement SIMD is different bit sizes.
qalcom uses 128bit while hummingbird uses 64bit. Since google worked with a lot of qalcom chips, i'm assuming the 2.2 jit was optimized more for the higher bit length SIMD than what samsung used. With 2.3, google optimized for larger and smaller SIMD bit lengths.
Click to expand...
Click to collapse
yeah, i remember seeing that somewhere with the SIMD bit length. so now, is it something that can be optimized or is it simply a hw limitation/difference?
Yes, Google optimized hit to work with both the Samsung simd and the Qualcomm simd in 2.3. But it 2.2, the Samsung simd optimization isn't there and there really isn't a way to work around it.
Sent from my SGH-T959 using XDA App
geoffcorey said:
Yes, Google optimized hit to work with both the Samsung simd and the Qualcomm simd in 2.3. But it 2.2, the Samsung simd optimization isn't there and there really isn't a way to work around it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
seems like it would manifest somewhere, but so far running cm7 i'm getting maybe a little better performance than 2.2 roms. same linpack and quadrant. granted cm7 is far from perfect. more what i'd expect just from progress on the os than an optimization. and what about moto? are the omaps just screwed until google decides that moto is their next nexus manufacturer?
funeralthirst said:
seems like it would manifest somewhere, but so far running cm7 i'm getting maybe a little better performance than 2.2 roms. same linpack and quadrant. granted cm7 is far from perfect. more what i'd expect just from progress on the os than an optimization. and what about moto? are the omaps just screwed until google decides that moto is their next nexus manufacturer?
Click to expand...
Click to collapse
i think the omaps have a wider SIMD bit length than samsung chose, so they saw improvements in the 2.2 jit.
I think the reason CM7 hasn't show much optimization is jit is because it still has a lot of debugging enabled in the kernel level.
funeralthirst said:
seems like it would manifest somewhere, but so far running cm7 i'm getting maybe a little better performance than 2.2 roms. same linpack and quadrant. granted cm7 is far from perfect. more what i'd expect just from progress on the os than an optimization. and what about moto? are the omaps just screwed until google decides that moto is their next nexus manufacturer?
Click to expand...
Click to collapse
CM7 Quadrant CPU score:5800
2.2 Roms Quadrant CPU score:1500
But i think it just skip the H.264 decoding test to achieve the high score(like the HTC devices which have qualcomm cpu)
plane501 said:
CM7 Quadrant CPU score:5800
2.2 Roms Quadrant CPU score:1500
But i think it just skip the H.264 decoding test to achieve the high score(like the HTC devices which have qualcomm cpu)
Click to expand...
Click to collapse
really? my quadrant is about 1500 on cm7 and an average of about 14mflops on linpack. and mflops should directly relate to simd/neon implementation.
plane501 said:
CM7 Quadrant CPU score:5800
2.2 Roms Quadrant CPU score:1500
But i think it just skip the H.264 decoding test to achieve the high score(like the HTC devices which have qualcomm cpu)
Click to expand...
Click to collapse
the number is not important, it's the breakdown of numbers (i.e. what's the number in the i/o portion of that score?).
just saw on this website http://www.popherald.com/samsung-galaxy-s-ii-plus-iphone-5-release-date/7595 and i was supprise that samsung have made Samsung Galaxy S II Plus,more faster and powerful procesor,but then they might change the name of it before they release it
I thought the galaxy sii mini was going to be like this but only a single core 1.4ghz cpu which seems more likely. Why would they release a phone with a slightly faster processor, its not like the current phone is slow and surely the current phone will get 2.3.4 soon anyway.
Just about everyone using Tegrak's OC tool has been able to hit 1.4 GHz. Heck, even some kernels are being released at 1.504 GHz stock. So, the CPUs in our devices are perfectly capable of the 1.2 -> 1.4 jump, just not sure what the point to all that is given everything runs smooth already at 1.0GHz even.
Seems overly pointless to me, when a firmware & kernel upgrade could easily handle the 1.4GHz upgrade and provide 2.3.4 at the same time.
There will no doubt be other 'new' features(NFC hardware etc) but if that's the main selling point of the phone then I'll kinda lose a little respect for my beloved Samsung. The least they could do is develop their chip to run at 2GHz stably and develop a battery that can keep it running for a whole weekend without needing to be charged. That'd be an upgrade worth paying for.
hey samsung come on guys how about selling in the us first before making newer models
Hi,
I think this place is where I can get most answers to my queries since I believe Galaxy phone share many same specs...
I'm looking for the following information : what processor is inside the phone? It's a Samsung S5570 and I understand the processor is ARMV6. Is V6 only or + VFP.
I guess I can get the answer if I install Firefox as it only works on V7 processors but I think I have read it could work with V6+VFP.
Can anyone tell if the phone has VFP in it?
I don't know a lot about computer hardware but I understand VFP is Very Floating Point and it enhances the capacities of the processor...
Thanks,
Pascal
The Nexus 7 should be very "powerful" as promised by Google!
Quad-core 1.3 GHz Tegra 3 processor vs Dual-core 1.2 GHz Cortex-A9... the Nexus is a Giant in CPU performance, but the UI isn't smoother than Galaxy S2, indeed it seems that the UI hardship to drag from one screen to another, is not at all fluid! in some case this is irritating!
At this point the Mali GPU of the Galaxy S2 it's a big point over the perfmance!
Anyone have the same observation about the UI smoothness of the S2 vs the Nexus 7?
Naamah said:
The Nexus 7 should be very "powerful" as promised by Google!
Quad-core 1.3 GHz Tegra 3 processor vs Dual-core 1.2 GHz Cortex-A9... the Nexus is a Giant in CPU performance, but the UI isn't smoother than Galaxy S2, indeed it seems that the UI hardship to drag from one screen to another, is not at all fluid! in some case this is irritating!
At this point the Mali GPU of the Galaxy S2 it's a big point over the perfmance!
Anyone have the same observation about the UI smoothness of the S2 vs the Nexus 7?
Click to expand...
Click to collapse
Are you comparing stock with stock? Personally, I find both stock and most roms very smooth. I don't have a GS2 but its definitely a lot smoother than the phones I have played on, including the GS2 on ICS stock.
What did you do to it? I use a SGS3 at work (I'm a software engineer currently developing a proprietary android app for my company) and the Nexus 7 is just as "smooth" if not smoother. You realize as soon as you install apps or modify it in any way the comparison to another device is not fair because it's not on even footing, right? Take it and the S2 back to stock with a factory reset and then compare them. It's entirely possible that apps that you choose to install will affect the performance of the device, even when they are not running.
CHollman82 said:
What did you do to it? I use a SGS3 at work (I'm a software engineer currently developing a proprietary android app for my company) and the Nexus 7 is just as "smooth" if not smoother. You realize as soon as you install apps or modify it in any way the comparison to another device is not fair because it's not on even footing, right? Take it and the S2 back to stock with a factory reset and then compare them. It's entirely possible that apps that you choose to install will affect the performance of the device, even when they are not running.
Click to expand...
Click to collapse
The Nexus7 and the S2 have the same Apex Launcher, the same LWP, and around the same software installed, the kernel is about to stock (excepted for the rooting) on both device, and the software installed is pretty the same (maybe the S2 have some apps plus rather the N7).
The Stock S2 is not AOSP (is Samsung full of bloatware) as in N7, so compairing the stock isn't to right... so I've installed in my S2 the SuperNexus (AOSP JB) to compare with N7 (AOSP JB).
Exist a benchmark to test the smoothness of the UI? instead of the CPU benchmark?
The difference of smoothness I've found maybe can be imputed to the different screen resolution? (1280x800 vs 480x800)
I don't know what you've done to your N7 but that just sounds ridiculous. I have a Galaxy S2 and have used that many ROMs & Kernels on it I care not to mention.
But still it has never even come close to the N7's stock experience, in fact the only thing I use my S2 for now is phone calls. This bad boy goes everywhere with me now tethered to my phone when I'm not at home.
Sent from my........
RockNrolling said:
Magnetised banana
Click to expand...
Click to collapse
After a lot of trying I've found that my LWP scrool smooth on S2 but not on N7... maybe it's a code related question (about Mali driver?).
Comparing the speed of the excution of the various apps the N7 is greater, but regarding the smoothness of the UI the S2 is equal to N7 (maybe a little bit greater).
At this point I must say thanks to the developer of the S2 ROM and the "optimized Mali driver for project butter"?
Naamah said:
After a lot of trying I've found that my LWP scrool smooth on S2 but not on N7... maybe it's a code related question (about Mali driver?).
Comparing the speed of the excution of the various apps the N7 is greater, but regarding the smoothness of the UI the S2 is equal to N7 (maybe a little bit greater).
At this point I must say thanks to the developer of the S2 ROM and the "optimized Mali driver for project butter"?
Click to expand...
Click to collapse
Is this an AOSP or touchwiz rom?
Because I remember codeworkx himself saying that the exynos S2 will never have full project butter and JB stuff because of all the closed source drivers and stuff samsung uses. He said that the OMAP version had a smoother UI, so I doubt it comes close to the N7. Unless you're using the omap version
markj338 said:
Is this an AOSP or touchwiz rom?
Because I remember codeworkx himself saying that the exynos S2 will never have full project butter and JB stuff because of all the closed source drivers and stuff samsung uses. He said that the OMAP version had a smoother UI, so I doubt it comes close to the N7. Unless you're using the omap version
Click to expand...
Click to collapse
Mine is an AOSP ROM (based on CM10) so... I've been heard about OMAP, but I don't know what is on details...