Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:One benchmark (Score 4, Informative) 164

Yeah... no.

vr-zone

As it stands right now, the prototype version is consuming 2.6W in idle with the target being 2W, while the worst case scenarios are video playback: watching the video at 720p in Adobe Flash format will consume 3.6W, while the target for shipping parts should be 1W less (2.6W)

extremeTech

The final chips, which ship early next year, aim to cut this down to 2W and 2.6W respectively. This is in-line with the latest ARM chips, though again, we’ll need to get our hands on some production silicon to see how Medfield really performs.

Comment Re:One benchmark (Score 1, Redundant) 164

Sure, it's great, and compares well to this gen of processors (which are all at the 45/40nm fab (the exynos 4210 is 45nm, not 32nm as vr-zone incorrectly states)).
But what about the next gen chips that will have 32/28nm fab?

And how will it compare to the Quad-Core A9 processors (Tegra 3), higher clocked dual core A9 processors (Exynos 4212) or A15/A15 based designs? (Exynos 5250 and Krait/Snapdragon S4)

Comment Re:No *official* port. (Score 1) 333

You should theoretically be able to flash w/e modem file you want to it, IIRC.

Oh, and you're lucky with the GPS performance. I had one of the very first Galaxy S phones, and the GPS would always drop, and never get a proper lock. It was utterly useless for navigation, because it always assumed I was somewhere else.

Comment Re:No *official* port. (Score 1) 333

hah, I've had many people and a few ROM/CM developers say Galaxy S was a paid beta for Galaxy S II ;-). When I got it, my friend even said the next one will be 10x better. Given my relative naivety at the time, I didn't think it'd be possible...

The shocking thing is that even though it was a beta, Galaxy S was arguably the best android phone on the market for at least 6 months. It did many things right: Decent internal memory size, Best in class GPU, proper multi-touch touchscreen (no bs dual-touch like Nexus One/Desire/Incredible/Droid), ~1.8GB for app installs (150ish MB was the norm back then). Brilliant video playback and codec support.

But 1GB RAM, dual core 1.2ghz A9, 8MP camera with 1080p and flash, flawless high profile 1080p playback and even 1080p flash playback (youtube). Like anandtech said: The Best, Redefined.. and that review was 5 months after the phone launched!

Comment Re:No *official* port. (Score 1) 333

There were 3 problems with Galaxy S, imho. 1) Shitty rfs file system. 2) Shitty GPS. 3) Relatively low RAM

rfs isn't a shitty file system. It actually performs rather well. Samsung's original implementation of it sucked in a truly mind-boggling way. The file system drivers these days work very well and that can be seen clearly as there's no longer a performance improvement gained when converting later Gingerbread based roms to ext4. I don't know what they were thinking originally though. I think the rfs issue made up 90% of the performance problems on Eclair and Froyo.

GPS sucks. This isn't your opinion. It's everyone's opinion. It's not just the software, but also the hardware. The software does help though. Later modems like JVS actually perform very well despite the shitty antenna design.

The RAM issue on the other hand isn't so much as the system has low RAM, but rather that Samsung have made such a bloated piece of crap implementation of Android. Switching to Cyanogenmod showed how little Android is supposed to use when running, and also freed up some 80mb on the /system partition.

Sigh. From the top: I don't know of how they've changed RFS over the last few months, but it was shitty when I used it. Does it still lock up where there is I/O going on, like media scanner running? That's what I always noticed with it.

GPS sucks: It is my opinion, and it just happens to coincide with what majority of the problems other people have. There are people that are perfectly happy with the way their GPS works too...

The RAM issue is real. I could feel the pinch, but others might think it's okay and perfectly normal. Had the same problem on Samsung based ROMs, and CM7/AOSP ROMs. I've never felt like that for Galaxy S II

Slashdot Top Deals

This restaurant was advertising breakfast any time. So I ordered french toast in the renaissance. - Steven Wright, comedian

Working...