Did you know: 5 interesting facts about Android L
0. phoneArena 20 Jul 2014, 10:02 posted on
Google unveiled its brand new version of Android at Google I/O nearly a month ago, and that makes for more than enough time for us to get acquainted…
This is a discussion for a news. To read the whole news, click here
1. AfterShock (Posts: 2812; Member since: 02 Nov 2012)
Well before Jake comes and craps on it.
I got to say, L rocks.
Grats Google for a Dev preview, this is slick.
8. NokiaFTW (Posts: 2043; Member since: 24 Oct 2012)
I'm a WP fan and user, and I've said it before, I'll say it again. I really like Android L. It looks sleek and sexy. Kudos to Google on this one.
17. AfterShock (Posts: 2812; Member since: 02 Nov 2012)
Not sure if serious....
Serious in liking L or speculative similarity with tiles conspiracy that has a lot in common with a supposed lake monster?
To be %100 clear, this looks nothing at all or like WP!
If serious, hope you try it out honestly when it's a full release later.
18. PapaSmurf (Posts: 8614; Member since: 14 May 2012)
Nowhere did he say L looks like 8.1. Nowhere.
2. DEATHSTROKE9 (Posts: 399; Member since: 09 Nov 2013)
Now this is interesting. Thanks phonearena. Those iPhone 6 parts were very boring.
38. lolatfailphones (Posts: 153; Member since: 08 Apr 2013)
Yes give us top 5 android L features we might already know about!
3. DEATHSTROKE9 (Posts: 399; Member since: 09 Nov 2013)
And how will the nexus 6 get a 64-bit CPU? I thought snapdragon 810 was coming next year.
33. Berzerk000 (Posts: 4069; Member since: 26 Jun 2011)
No way. Dual core Cortex A57 + quad core A53 would be less powerful than quad core Krait 400, even after the added performance of 64 bit.
35. sgodsell (Posts: 1289; Member since: 16 Mar 2013)
Qualcomm is not the only CPU vendor out there. In fact a number of of chip OEMs make 64 bit CPUs as well. For instance Intel already has 64 bit CPUs that already run Android now on Intel. Samsung, Motorola, and a few others already have 64bit CPUs in some of their phones and tablets. Mediatek, Nivida, Rockchip, LG, Samsung all are releasing 64bit Arm CPUs. In fact Qualcomms first 64bit chip should be the Snapdragon 410 CPU this fall.
6. tech2 (Posts: 2183; Member since: 26 Oct 2012)
Although that sounds a bit ambitious but if Google partners with Samsung on Nexus 6 then there is a high chance of it releasing with 64-bit Exynos processor.
We heard quite a bit about Google forming strong relations with Samsung and I sincerely hope the new Nexus is not based on LG G3 coz of its awful display and size.
7. Scott93274 (Posts: 1182; Member since: 06 Aug 2013)
Well my last phone was a Samsung Galaxy Nexus... and that phone was nothing to brag about....
11. tech2 (Posts: 2183; Member since: 26 Oct 2012)
LOL....are you serious ?! It was the first phone to debut the most successful android version yet, Ice Cream Sandwich !
It was also the first android phone with a 720p display !
Nexus phones phones were never known for their ground breaking specs but Galaxy Nexus was.
19. Scott93274 (Posts: 1182; Member since: 06 Aug 2013)
I'm pretty sure you're wrong about it being the first phone with 720p display... And yes it was the first phone with ICS, I guess you could say that the stuff that irritated me the most about it was Verizon forcing their crap on the phone, and TI for lack of support. Even though it was a Nexus device, I saw other phones get OS updates before my own.
Aside from that, I guess you could say that my frustration with the phone just so happens to be with the fact that it aged poorly, it slowed down really bad towards the end of its lifecycle, and the battery would drop 20% on the 30 minute commute to work (Even after removing a majority of the software and removing background programs regularly). If I wanted to hug walls, I would have gone with an iPhone.
27. PapaSmurf (Posts: 8614; Member since: 14 May 2012)
It was the very first phone with a 720p screen. It was a bigger deal than the iPhone's Retina screen. Blame Verizon for all your problems because the unlocked version of the phone worked flawlessly.
28. CanYouSeeTheLight (Posts: 860; Member since: 05 Jul 2012)
The 720p display wasn't that great tbh it had troubles with low brightness, the GPU barely could handle the 720p resolution, a 5MP camera that was awful, and pityful battery life.
With that being said it still set the standard regarding smoothness(on 4.1) and camera speed on Android when it came out.
9. Busyboy (Posts: 344; Member since: 19 Jun 2014)
I doubt they would go to Samsung yet again. Nexus usually changes after 2 models with a company, so I'm hoping Sony gets it next. Since their allowing you to unlock the bootloader something must be up.
12. AfterShock (Posts: 2812; Member since: 02 Nov 2012)
No offense, but I hope you're wrong about soc platform, not bit width.
Somehow I feel Nexus will be higher end then G3 if made by LG again, which I feel will happen.
We all know G2 and N5 are sister models basically, but I think Google may have little more influence on the over all package this time around. Just my hunch.
Oh, I also have felt all along, but honestly questioning it, that it'll be 64 bit, the part where I was way off was the G3 which I thought was going to be too.
( LG released the G3 half baked IMO)
15. AfterShock (Posts: 2812; Member since: 02 Nov 2012)
Sorry, I wandered, I meant the G3 coming with higher end soc like 805, not the lack of being 64.
As if the N5(14, model) is 64, it'll be head an shoulders shove their own flagship the G3.
36. Berzerk000 (Posts: 4069; Member since: 26 Jun 2011)
I would be happy with a Tegra K1 that's underclocked to save battery. The dual core 64 bit version is apparently as powerful as the 32 bit quad core, which has A15 cores at 2.3 GHz. That's impressive considering most other A15 based SoCs run under 2 GHz, and work with their A7 cores in big.Little for their benchmark scores. And the GPU is 3 times as powerful as the GPU in the A7 chip in the iPhone 5S and new iPads, that definitely leaves some room for underclocking while still being a good upgrade from the S800 in the Nexus 5.
66. pulkit1 (Posts: 306; Member since: 03 Jul 2014)
I really think nexus 6 will get a 64bit soc because nexus is supposed to showcase latest android in its full glory and since android L supports 64bit nexus must have it else its pointless for developers to buy nexus to optimise their apps. Nexus is meant for developers to optimise their apps for the latest android release and 32bit android nexus will nit allow them to do so .
13. james.blunt.1973 (Posts: 36; Member since: 15 Dec 2013)
What comes after Nexus 6? Nexus 7?
44. xche78x (Posts: 101; Member since: 11 Mar 2014)
Google will probably add a suffix to the nexus names and revert the numbering to zero or 1. Ex google nexus one. They can even call the nexus 6 the "Nexus L." So the next model could be named Nexus L2 or Nexus M.
Nexus 7 is already used in the 2012 nexus tablet made by asus with tegra 3 and the nexus 7 2013 with s4pro soc. nexus 7 name might still be used on the 3rd iteration if they ever made such product, could use 64but soc from any manufacturer and QHD display. Or just release nexus 8 rumored to be made by htc.
16. Trolloftheyear (banned) (Posts: 66; Member since: 16 Jul 2014)
Best smartphone OS will be even better.
20. XperiaFanZone (Posts: 1396; Member since: 21 Sep 2012)
Are the users able to stay on Dalvik? Some apps may not work on ART.
45. xche78x (Posts: 101; Member since: 11 Mar 2014)
Just like 64bit windows, android L still has dalvik to run legacy apps. Its transparent, users dont need to switch anything. If apps are not upgraded to art version, android will select dalvik as its runtime for only such app. Thats how i understand it, correct me if im wrong...
46. sachouba (Posts: 29; Member since: 08 Jun 2014)
When I am using ART Runtime on the Galaxy S5, I cannot run some apps whereas they work with Dalvik. Android doesn't select Dalvik automatically, and it's impossible to do it manually. Maybe it changed on Android L.
52. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
ART is the same crap as Dalvik besides it compiles upon installing rather than while executing.
55. yowanvista (Posts: 306; Member since: 20 Sep 2011)
Educate yourself before posting crap.
56. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
Oh, my bad. They are also named differently.
But beside that, I repeat, the same crap.
Google is trying to make you believe ART is something advanced,
but in reality, it's all about dealing with the overheads in a different way.
The joke is however, these overheads aren't existent on native platforms to start with.
Educate yourself before posting crap.
58. Arte-8800 (banned) (Posts: 4562; Member since: 13 Mar 2014)
There are lots of weird things in both APIs. I personally find it hard to think up the same names for methods that the NextStep team did (the core of iOS and the reason everything starts with NS). When I want to stop a timer in Android I call stop() when I want to stop one in iOS I call invalidate. Which one makes more sense to you? I can find examples where iOS is better than Android just as easily.
Google needs to improve the framework. Animations could be cleaner and easier, the UI framework needs work too. I want more controls baked in. I hate the original calendar picker. Not a huge fan of the slot machine spinner on iOS as it was so huge. Newer Android versions are much improved.
Apple needs a lot of improvements too. Look how long it took them to support something like regular expressions they should have had from the start. They have no support for modal UIAlertViews which can really suck. The whole delegate methodology for UIAlertViews makes things a big mess when you have multiple of them in a single piece of code. Who the heck wants to deal with button indexes? You reorder or change the visible buttons and it is all out of whack.
Xcode needs some more features or maybe plug-in support so people can add things they need. It is an OK IDE but is missing a lot of features I have really gotten used to in Eclipse. AppCode is a huge help in this area and I use that for balls to the wall code editing and use Xcode when I need Interface Builder, Story Boards and Core Data manipulation.
Coming from PC development I like the layout managers of Android for the most part. You can come up with a couple of layouts that work nicely on a number of devices. I see a number of iOS apps that are locked into portrait as no one wants to even do a second layout for landscape.
iOS is locked into a few sizes. Sure, that makes is easier on the designer but for Apple to do a new screen size things are going to break since there is so much hard coded to the current sizes. They lost out on future flexibility. That will generally come and bite you. A bit of the pain was felt on the larger iPhone 5.
Developers and designers can do a better job on Android. Excuses need to stop being made. Google does back port new APIs which is nice. Apple pushes you into the future via OS upgrades and does not back port anything. ARC sure as hell makes life a lot easier. I am excited to try out the new Auto Layout.
We need them both around to push each other.
59. tedkord (Posts: 4937; Member since: 17 Jun 2009)
Ahead of time compiling removes the overhead of JIT.
21. dexter_jdr (Posts: 1145; Member since: 28 Jun 2012)
i did not know that 5 facts = 7 pictures.
37. Berzerk000 (Posts: 4069; Member since: 26 Jun 2011)
The last 2 are labelled as assumptions.
23. hurrycanger (Posts: 1190; Member since: 01 Dec 2013)
I just feel like Google is taking their time working with another company to use their product's name for the next Android. Just like Kit Kat.
24. ChooseGoose (Posts: 1; Member since: 09 Jul 2014)
The second image has Key Lime Pie instead of Kitkat...
25. hurrycanger (Posts: 1190; Member since: 01 Dec 2013)
yea.. it's an old image. Google did make it Android Key Lime Pie though, and later changed it to Kit Kat.
26. guest (Posts: 97; Member since: 13 Jun 2012)
All of Intel's processors are 64 bit and I am sure they would give Google a sweet price just to break into the Android platform. Oh and they are already shipping.
30. ayephoner (Posts: 837; Member since: 09 Jun 2009)
kit kat is made by herhsey's. herhsey's only L candy is the caramels named Lancaster. if you weren't paying attention to candy over the last year, herhsey announced this brand last fall and it came out in the winter. this wasn't too long after hershey and google released kit kat.
i'm not sure if anyone else has thought about this, or put it out there, but i'm thinking android 5.0 will be "android lancaster." you (maybe) heard it here first.
31. ayephoner (Posts: 837; Member since: 09 Jun 2009)
i could totally see the android robot stamped out in that vanilla caramel pattern for the new statue.
40. chromoid (Posts: 8; Member since: 03 Oct 2013)
Kit Kat is made by nestle. Hersheys has a license to make it in the us.
43. ayephoner (Posts: 837; Member since: 09 Jun 2009)
the deal with google was with hershey's as well as nestle. i'm just making a guess anyways, but it makes sense to me.
53. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
Cause all the Androtakus gathered here for a preemptive strike on me and the truth.
60. lolatfailphones (Posts: 153; Member since: 08 Apr 2013)
Lol I was like..WTF slow news arena?
39. mas11 (Posts: 1030; Member since: 30 Mar 2012)
As someone that builds PCs as a hobby, I don't understand what the big deal is when it comes to 64-bit. All 64-bit really does is allow the system to use 4+ GB RAM.
41. chromoid (Posts: 8; Member since: 03 Oct 2013)
That is not the only thing 64 bit cups offer
One of many is a larger instruction bus that allows longer instruction sets to be passed through the cpu.
71. ArmDeveloper (Posts: 2; Member since: 20 Jul 2014)
There's no such thing as "instruction bus".
Both 32-bit (recent ARMv7, like Cortex A7/A15, etc.) and 64-bit ARM CPUs (like Cortex 53/57) can process 128 bits per single NEON instruction.
A common misconception is that AArch64 could intrinsically process more data per clock cycle than before. It's still limited to processing *128 bits* per single NEON instruction, for example 4x 32 bit packed floats "at a time", just like earlier 32-bit ARM chips. Of course, it's a different matter how many instructions are actually issued and processed per clock cycle. At least some ARMv7 CPU implementations actually take 2 cycles to process a single simple 128-bit NEON instruction, such as vector addition. Such previous generation "half issue" 32-bit CPUs could only really process 64-bits per clock cycle. Of course nothing prevents from implementing a similar "half issue" 64-bit ARMv8 CPU...
Amount of processing done per clock cycle does not depend on architecture, rather on particular chip implementation.
62. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
True, the benefit of 64bit computing is quite significant, but rather situational.
While what you are saying might be valid on x86, it's different on ARM.
It absolutely needed a new instruction set in order to raise the IPC beoynd that of the CA15's.
And there was no reason for this to remain a 32bit one. Et voilà, aarch64 is born.
64. ArmDeveloper (Posts: 2; Member since: 20 Jul 2014)
As someone who builds PCs as a hobby, you should know that 32-bit systems do not limit amount of addressable RAM to 4 GB. Operating systems do.
32-bit can address just as much physical RAM as 64-bit. There's of course a well known consumer operating system vendor that has limited their OS to just 4 GB on 32-bit platforms. But that's not a technical limitation, just a marketing one (or something similar).
This applies to x86 CPUs as well as to newer 32-bit ARM CPUs.
48. antmiu2 (Posts: 214; Member since: 19 Jun 2011)
Android L is the first ground-up redesign since Android 4.0 ... no its much like kit kat with a theme on it
61. tedkord (Posts: 4937; Member since: 17 Jun 2009)
No, it isn't. It changes a large part of the way Android works, with a change from JIT to AOT compiling.
63. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
And what Google doesn't want you to know : the Dalvik vs ART graph is only valid for Nexus. Qualcomm's 32bit Dalvik JIT beats the hell out of Google's 64bit ART.
65. joey_sfb (Posts: 3003; Member since: 29 Mar 2012)
Why bother? Opinion are like ass holes. Everyone has one.
Android is still preferred mobile OS after switching over from iOS and I will use it till another better choice appear. More than ever I preferring Xiao Mi Redmi Note over my Samsung Note 3. I like MIUI interface over Touchwiz.
For Xiao Mi Ex-Samsung user, try out Smart stay EX works as well as my Samsung Note.
Still I will buy Note 4 when its available.
70. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
It's not my opinion but a fact.
Google's JIT sucks. That's the only reason that they got much gain through a less lousy job.
And here is my opinion :
They should be ashamed instead of presenting this graph proudly.
67. tedkord (Posts: 4937; Member since: 17 Jun 2009)
You're talking about the QC optimized DALVIK (which is very good) vs. the KitKat version of ART, which is a beta feature (and isn't 64bit). Also, the QC DALVIK isn't useful for non-QC chipsets.
The newer Android L dev preview ART is showing very solid performance and battery gains, up to 2-3X speed improvements.
It doesn't matter how much you cry and fuss, Android is here to stay.
69. JakeLee (banned) (Posts: 1021; Member since: 02 Nov 2013)
You forgot to mention "according to Google", "allegedly"
And you also forgot that I have access to the 64bit PDK plus developer board.
Optimization is a rather ungrateful job :
If you can achieve very much through optimizations, it just means the orignial was a lousy job to start with.
And that's Google's JIT that massively sucks while the new ART is a halfway decent one, nothing else here.
And again, vendors like Qualcomm will optimize ART, but the performance gain over their Dalvik JIT will be marginal at best.
All these bells and whistles around ART aren't justified.
Java sucks 31 balls to start with.