Samsung Galaxy S5 Watch Thread

Let the rumor mill begin!

I have a hard time swallowing the "Non-removable batteries". It has always been a staple for the S-series phones, along with memory card support. Although I heard a while back that Samsung was going to take a new direction starting with the S5 series phones, and go in a much more unconventional route.
 
Let the rumor mill begin!

I have a hard time swallowing the "Non-removable batteries". It has always been a staple for the S-series phones, along with memory card support. Although I heard a while back that Samsung was going to take a new direction starting with the S5 series phones, and go in a much more unconventional route.
Well, maybe it's just one of the many models of the S5. Quite frankly, Samsung probably wants to get on the metal gold bandwagon, not that plastic gold...
 
I thought I was famous for starting rumor threads early, but dang man, you started this 7 months before it's released :eek:

I need to start my Nexus-Six thread next :p
 
Reminds me time to go start the galaxy note 4 thread.
 
But who will start the HTC Mega Ultra Maximus Two thread ?!! (because Two > One) :)
 
I think I may as well jump on the nVidia GTX-880 thread now, and also get rolling on the HTC Two thread.
 
just had my G2 for a week now, and already told the wife if the s5 was up to snuff I'm using my Jump plan for it on release.
 
I thought this was a new article, but it's from June, lol. I guess this thread could have been started a few months back. :D
 

I've been reading rumors of a 4,000mAh battery in the S5 for a few weeks now. At first I thought, yeah right, that's a nerds wet dream, not gonna happen, would love it, but just seems so far fetched.

But now, if the rumor is a true, a solid Metal uni-body design, like the HTC One, and iPhone, with a fixed battery, then I could see Samsung putting in massive MAXX style battery, and could market it, by saying hey no more removable batteries, but we have a 4,000mAh battery, so no need to ever change your battery, this beast will go 48+ hours long.

But being on ATT, only Samsung phone I will buy again, is a 'Developers Edition' or 'Google Play Edition', don't want to be stuck on a locked bootloader again.
 
Yes, the rumors are constantly swirling regarding the S5.
I am waiting for it and will be up for an upgrade next Q1. The S4 is a great phone and I think Samsung is going for Apples throat in a big way with the next phone.

I thought the all metal uni-body was dispelled as a possibility, but here it is again...still waiting for leaks...
 
Fingerprint tech. 64 bit CPU.

Not quite sure what 64bit CPU would do anything for Android OS unless they somehow rewrite the entire kernel, which is very unlikely.
Which is completely pointless in this regard.... Maybe for some marketing....:confused:

Fingerprint would be lovely. I really enjoy using that on 5S and HTC One MAX.
 
2014 is shaping up to be a major year for smartphones. I think the biggest updates to the popular phones are due;

- Galaxy S5 = Feb / March release - all new metal body, new design, and whole new architecture.

- iPhone 6 = Aug / Sept release - all new design, larger screen.

- Asus Nexus 6 = Oct / Nov release - Android 5.0 Liquorice.
 
2014 is shaping up to be a major year for smartphones. I think the biggest updates to the popular phones are due;

- Galaxy S5 = Feb / March release - all new metal body, new design, and whole new architecture.

- iPhone 6 = Aug / Sept release - all new design, larger screen.

- Asus Nexus 6 = Oct / Nov release - Android 5.0 Liquorice.

Pretty much the same as last few years then :) Except that Galaxy is now rumored to be metal.
 
Aluminum could be a deal-breaker for me.

Aluminum is for soda cans.

Fortunately there are so many good Android phones out there, you don't have to buy Samsung these days.
 
Not quite sure what 64bit CPU would do anything for Android OS unless they somehow rewrite the entire kernel, which is very unlikely.

Rewrite what? The Linux kernel has had support for 64-bit ARM CPUs for over a year now.
 
Aluminum could be a deal-breaker for me.

Aluminum is for soda cans.

Fortunately there are so many good Android phones out there, you don't have to buy Samsung these days.

M8 HTC '1' should be a sweet phone too, due out in March.
 
Rewrite what? The Linux kernel has had support for 64-bit ARM CPUs for over a year now.

The reason why iOS sees quite a bit of performance improvement from 64bit is due to inline reference count, it's heavily used under Obj-C (If you are iOS developer you should know what I am talking about). This gives a huge boost for it's speed. Android's VM on the other hand is not up for the same logic. Unless something is changed in the new ART that I don't know about, there will be very little improvement over the 64bit architecture on Android.
 
The reason why iOS sees quite a bit of performance improvement from 64bit is due to inline reference count, it's heavily used under Obj-C (If you are iOS developer you should know what I am talking about). This gives a huge boost for it's speed. Android's VM on the other hand is not up for the same logic. Unless something is changed in the new ART that I don't know about, there will be very little improvement over the 64bit architecture on Android.

Why not?
 
  • 16MP ISOCELL camera
  • 64 bit Exynos 14nm CPU (the jump to 14nm is surprising since even Intel hasn't done that yet... we'll have to wait and see though)
  • 3GB LPDDR3 RAM
  • New improved 500PPI Super AMOLED display
  • 4000mAh battery based on nanotech... which means smaller battery with better dispersion characteristics
  • Android 4.4 KitKat

I'm excited!
 
A friendly reminder: if the GS5 rumor cycle is anything like that for the GS3 and GS4, you'll have to be extremely skeptical. Even moreso than in the Apple rumor mill, people are prone to just making stuff up about Samsung's future product line -- fake product renders, fake screenshots and (of course) fake specs.

The only things that have much credence are components that Samsung has already announced and should make their debut in 2014. A 64-bit CPU and an ISOCELL camera are natural fits, but there's a lot of stuff up in the air.
 
But that has nothing to do with 64-bit.

There have been 64-bit JVMs since before anyone in the x86 world even knew what 64-bit was.

It's the way the assembler / architecture works. It's not that simple as "supports 64bits".

Apple took advantage of message passing and reference count structure and specially modify for 64 bit address. Android can not simply takes the same approach since this is not how the current VM works.
On the other hand, using VM will always be slower than native, and it's A LOT slower on Dalvik VM than JVM.
 
Is this a joke? 64 bit has no performance benefits, it has some benefits in unifying code built for a desktop OS and using it for mobile. In fact 64 bit code uses a lot more memory, and iOS devices are already memory constrained.

It's just a bandwagon, nothing more.
 
Is this a joke? 64 bit has no performance benefits, it has some benefits in unifying code built for a desktop OS and using it for mobile. In fact 64 bit code uses a lot more memory, and iOS devices are already memory constrained.

It's just a bandwagon, nothing more.

The way it works on iOS is quite different than the typical 64bit support like I mention earlier.
 
Is this a joke? 64 bit has no performance benefits, it has some benefits in unifying code built for a desktop OS and using it for mobile. In fact 64 bit code uses a lot more memory, and iOS devices are already memory constrained.

It's just a bandwagon, nothing more.
Hater! :mad:
 
It's the way the assembler / architecture works. It's not that simple as "supports 64bits".

Apple took advantage of message passing and reference count structure and specially modify for 64 bit address. Android can not simply takes the same approach since this is not how the current VM works.
On the other hand, using VM will always be slower than native, and it's A LOT slower on Dalvik VM than JVM.

Sure a VM will always be slower than native, but most performance-important pieces of code are native anyway. You said the entire kernel had to be re-written to take advantage of 64-bit. Why? The kernel has nothing to do with Dalvik or VMs or anything you're talking about.

I don't think 64-bit is that important on a mobile chip (for performance), but this idea that there's some kind of magic in iOS and Android is at an inherent disadvantage, I'm just not following that.
 
He means Objective-C (used by most Apple apps) has a specific optimization on ARM64 which allows certain operations to be faster, like the reference count updating.

This is very specific though, and in general 64-bit computing doesn't mean it'll be faster, like most people tend to think.

Android has been slow because Google's choice of JVM, Dalvik, is an ancient pig and has none of the typical JVM optimizations. Which is why they are finally moving to ART.
 
He means Objective-C (used by most Apple apps) has a specific optimization on ARM64 which allows certain operations to be faster, like the reference count updating.

I'm sure in practice that adds up to about nothing.
 
Back
Top