64-bit Intel Bay Trail chips to be in Windows tablets next year, maybe Android
1. Droid_X_Doug (Posts: 5620; Member since: 22 Dec 2010)
Hopefully there will be 4+ Gb of RAM along with the 64-bit chips.
4. mturby (Posts: 232; Member since: 09 Jan 2013)
4? thats not enough! what abut 6 or 8 or 10. will that be enough for ur device? or u just want to buy something new?
7. Droid_X_Doug (Posts: 5620; Member since: 22 Dec 2010)
You need a minimum of 4 Gb for the addressing advantage of 64-bit to kick in. Notice my reference to 4+.
The real requirement is for the O/S to support 64-bit hardware and application developers to write 64-bit apps. Until 64-bit O/S and apps are available, 64-bit really isn't a benefit.
11. Shatter (Posts: 1997; Member since: 29 May 2013)
To update an app to 64bit all the developer has to do is recompile it.
13. Droid_X_Doug (Posts: 5620; Member since: 22 Dec 2010)
What about adding functionality that takes advantage of additional memory addressing available?
14. joey_sfb (Posts: 2782; Member since: 29 Mar 2012)
64 bits are just bigger buckets so if your data element is more than 32 bits the benefit is immediate but in most real world example they hardly reach 32 bits most just around 8 bits and 16 bits.
Therefore, most 64 bits app are actually slower than their 32 bits counter part with a bigger memory foot print and more resources is require to move data around the system.
17. nmentley (Posts: 2; Member since: 26 Dec 2013)
For iOS that's true.
android and wp8 are java and .NET.
Those a bytecode languages... and will run 64bit without recompiling.
For example, If you write a java program on a pc. Compile it on 32bit windows... and execute the JAR file on 64bit linux it'll run fine and in 64bit.
The same is true for android. Jars run 32bit with a 32bit java runtime. The same jars will run 64bit on a 64bit runtime.
16. nmentley (Posts: 2; Member since: 26 Dec 2013)
The vast majority of android apps are java and, I believe, every windows phone 8 app is .NET.
Java and .NET binaries are compiled to bytecode instead of machine code and as a result are architecturally independent.
If the OS is 64bit and the bytecode runtime. The apps will fully support 64bit.
The reason Apple had to jump to 64bit first is because their apps are machine code.. and will need to be updates or at the vary least recompiled to be 64bit.
3. mturby (Posts: 232; Member since: 09 Jan 2013)
so? this is boring...is it going to make the phone faster? will it be faster than a 1.2 dual or quad or octacore processor? is it gonna make android faster than what it is already? will the apps open faster that what we already have? stupid manufacturers trying to play with our mind to get our money. screw u.
5. brrunopt (Posts: 477; Member since: 15 Aug 2013)
But baytrail chips are already 64bits, just running windows 32bit because of Connected standby support..
10. jove39 (Posts: 1265; Member since: 18 Oct 2011)
you are right...but I am not sure many people are aware of it :)
6. ArtSim98 (Posts: 2529; Member since: 21 Dec 2012)
I would love to see more Intel processors in smartphones one day!
8. Droid_X_Doug (Posts: 5620; Member since: 22 Dec 2010)
Patience. Intel knows their future is the low power mobile market.
12. Shatter (Posts: 1997; Member since: 29 May 2013)
Baytrail is better performance/per watt than a15 its just a matter of making them appealing to smart phone makers. They cost about 2x as much as a snapdragon 800.
9. jove39 (Posts: 1265; Member since: 18 Oct 2011)
"64-bit Intel Bay Trail chips to be in Windows tablets next year..."
64bit baytrail is already running windows...just that windows version is 32 bit...64bit windows doesn't have connected stand by...just yet.
A7 is first arm based 64bit chip...not first mobile chip with 64bit architectire.
15. aryanfr1 (Posts: 40; Member since: 24 Jan 2013)
Apple though bought the 64 bit on mobile device but m it won't be disappointed to see Android phones will capitalise on that and breed much more advanced processors as like they have lost the ridiculous display war.