>
New Topic
>
Topic Locked
Esato Forum Index
>
General discussions >
Rumours
> SONY XPERIA Rumors 2014
Bookmark topic
Is the current android even 64bit ready? I would think the next version will have 64bit built in?
--
Posted: 2014-02-11 14:17:56
Edit :
Quote
On 2014-02-11 04:51:46, vivftp wrote:
Well this news about the quality of the front facing speakers certainly is nice. I've long since wondered when Sony would up their game for external audio quality on their phones. The E1 was a nice step, but of course that's not a waterproof flagship phone.
Gonna hold on to my Z Ultra for now. Keeping a close eye out for news on the new Ultra, or the 2H flagship that's been rumored with the Arc back. Can't wait for more info on that front.
Think arc design rumor has been shut down by other source, it was made up BS. This point on from Sony Mobile its omni balance from their Japanese designer, not from EU Erricson anymore.
--
Posted: 2014-02-11 15:26:48
Edit :
Quote
So, S5 is rumored to come out with a QHD screen and the latest, a 20 MP camera. Now I know QHD on a 5-5.2" screen is absurd, but it would be a big selling point for the S5 that could boost its sale way more than its competitors, Z2 included.
--
Posted: 2014-02-11 15:37:10
Edit :
Quote
aaaand on a more relaxed note....
MARKETING DONE RIGHT!
http://thenextweb.com/shareab[....]er-inside-bottle-water/#!vej3f
--
Posted: 2014-02-11 15:37:33
Edit :
Quote
@ ascariss
Android is based on Linux Kernel, which is 32bit and 64bit compatible...
but it's only the kernel, the rest is mainly 32bit binaries including the runtime libraries, drivers, Dalvik Machine, ART, UI, Apps...
The use of Dalvik and ART means that transition to 64bit is easier as Java it self has very small differences between 32bit and 64bit... the main problem will be with C & C++ Code used with Android NDK as these will need to have a lot of changes compared to Pure Java solutions...
If you switched to the 64bit Kernel, then the next step will be 64bit drivers, in fact you can't use 32bit drivers in 64bit environment... so both must be ready...
The only thing that I'm not aware of it is :
Android uses a heavily modified Linux Kernel, I don't know if these modifications are both 32bit and 64bit or just 32bit to speed everything up and keep it clean from unwanted source... if it was just 32bit, then the Kernel will need more time to work with it for 64bit...
The latest Android kernel is based on Linux Kernel 3.4, there's newer versions up to 3.13 but Google uses special versions called the long-term stable releases... the latest one of these releases is 3.10 which was released in June last year..
--
Posted: 2014-02-11 15:39:49
Edit :
Quote
In other news, what happened to razec? Is he doing a se-love? (Reference to 2010 thread)
--
Posted: 2014-02-11 15:44:35
Edit :
Quote
On 2014-02-11 15:39:49, Xajel wrote:
@ ascariss
Android is based on Linux Kernel, which is 32bit and 64bit compatible...
but it's only the kernel, the rest is mainly 32bit binaries including the runtime libraries, drivers, Dalvik Machine, ART, UI, Apps...
The use of Dalvik and ART means that transition to 64bit is easier as Java it self has very small differences between 32bit and 64bit... the main problem will be with C & C++ Code used with Android NDK as these will need to have a lot of changes compared to Pure Java solutions...
If you switched to the 64bit Kernel, then the next step will be 64bit drivers, in fact you can't use 32bit drivers in 64bit environment... so both must be ready...
The only thing that I'm not aware of it is :
Android uses a heavily modified Linux Kernel, I don't know if these modifications are both 32bit and 64bit or just 32bit to speed everything up and keep it clean from unwanted source... if it was just 32bit, then the Kernel will need more time to work with it for 64bit...
The latest Android kernel is based on Linux Kernel 3.4, there's newer versions up to 3.13 but Google uses special versions called the long-term stable releases... the latest one of these releases is 3.10 which was released in June last year..
As to your first post, Q was def sleeping... hard. The reason we know this is that that S805 exists (as a flagship no less), and that its not scheduled to be in products till 2/3Q14 pushing more advanced flagship SoC's out to 4Q and most likely CES/MWC '15. Meanwhile K1.Denver is expected in the same timeframe late summer early fall most likely tablets. So that would mean MediaTek/nVidia/'Apple' will all definitively have 64bit solutions out against the S805. (excluded Samsung for a reason)
As for Android, the current Kernel is 3.4 right? Still Linux includes 64bit support. So I agree, I would also like to add that ARMv8-A includes 32bit user space, where you can use 32bit drivers in an 64bit environment which mitigates a lot of that re-write and developers can move forward. the thing is however lower end devices probably wont get 64bit for a fair bit of time meaning that development will probably lag slightly, but we see that now, so there may be a clear dilineation later for higher end games and such, still thats on the devs to chose. But at this point, there isnt much holding the move back, the expectation would be a meaningful jump in utility, unlike iOS whose architecture is completely different (doesnt have Davlik/ART middleware that needs to be mitigated through HW).
[ This Message was edited by: my ninja on 2014-02-11 15:59 ]
--
Posted: 2014-02-11 16:51:18
Edit :
Quote
Thanks for the replies. I am curious who will bring the first 64bit device for android.
--
Posted: 2014-02-11 17:42:15
Edit :
Quote
@my ninja,
Your point might be correct if we're talking about 64bit, but Qualcomm already have a 64bit SoC.. thought all current 64bit SoC's are low-end/mid-range for now.. even the one's announced by MediaTek.. the A57 core will need more time to see it in market so Qualcomm still has the time.. thought I don't know till when. while they said that first Snapdragon 805 will show in May: this mean that they might not have any higher-end model till later this year with devices targeted for early 2015...
Currently Only Samsung and nV announced high-end 64bit, but they're still not mid year hit, Tegra K1 quad-core is 32bit ( Again A15 core ), the Denver one which is 64bit won't see the light till second half this year... and no body knows anything about power consumption.. which was very bad in Tegra 3 and Tegra 4...
Samsung latest SoC is 5420 which is 4+4 A15+A7 big.LITTLE ( used in Note 3 3G edition ), we still don't know what Galaxy S5 will pack, but I feel it too early for a 64bit even if Samsung went for the shortcut way ( using plain A57 cores rather than a modified one )...
@ascariss
The SoC could be Intel as it's already almost ready, but they're working on the software side and coz Android isn't ready yet for 64bit, Intel is working harder for this...
About who will make it ? might be ASUS as these guys have good relation with Intel and recently they announced 3 devices with Intel Atom SoC's...
By the way, to add to my previous reply, Linux Kernel 3.4 ( the current one ) doesn't have support for ARM 64bit ( ARMv8-A ), it has been added in Kernel 3.7... but that doesn't mean Google can't port it but it's illogical to update old Kernel while they're targeting something major.. I guess they will move up to 3.10...
--
Posted: 2014-02-11 19:56:20
Edit :
Quote
I did read that Intel was pushing for the 64bit android since they already have the 64bit baytrail chips so all they need is the OS.
--
Posted: 2014-02-11 21:05:40
Edit :
Quote
New Topic
Topic Locked
