Android and openness is something we talk about all the time, but the recent developments in the industry point towards inherent flaws with this very premise. Be it from bloggers, political institutions or corporations, Android is seemingly not open enough. The “War on Openness” is ironically becoming an open war, where many players are increasing their stakes and scope to try and land a bigger hold - or at the very least, restrict Google’s - on what is the world’s...
Snapshots of Android “L” Found in Chromium Issue Tracker
Google I/O 2014 is a mere 35 hours away, and many of us are hoping for the release of the next major version of Android, thus far only known as “L.” Whether or not Android “L” makes its appearance at I/O, we already know quite a bit about it.
At this point, we have a few relatively concrete details about the upcoming Android “L” release. We know that Dalvik will soon be shown the door in favor of ART, and we know that quite a bit of emphasis has been placed in the 64-bit codebase. And through rumors detailing the new Quantum Paper UI paradigm, we also have a good idea of what the next major version of Android will look like.
Now thanks to an issue posted to the Chromium issue tracker that was discovered earlier today by redditor Doopl, we have an even clearer picture of what L may look like. The issue itself (now-removed issue tracker entry 382592) is of little consequence itself, but it deals with Chrome’s layout not observing screen orientation changes. Although the issue tracker entry itself has been made private or deleted, information on the now-fixed bug can still be found on Google Groups:
Comment #1 on issue 382592 by firstname.lastname@example.org: Upgrade screen should
respect screen orientation
The following change refers to this bug:
Comment #2 on issue 382592 by email@example.com: Upgrade screen shouldrespect screen orientation
Note that due to the necessity to fit the header and the buttons, the
scrolled area has been expanded to contain the text in the bottom.
3u-tablet-portrait.png 347 KB
3u-tablet-landscape.png 154 KB
3u-phone-portrait.png 160 KB
3u-phone-landscape.png 168 KB
In addition to the portrait layout shown above, the issue tracker also showed a screenshot displaying the issue above when in landscape mode:
Both screenshots come in at 1280×768 resolution and feature software navigation keys, which means that this is likely a Nexus 4. In the screenshots, Chrome Browser isn’t shown to be running full screen, which jives with earlier rumors of a redesigned cards-based multitasking system, and the app itself also features Quantum Paper-like design elements.
Also of note in these screenshots is a big L icon, which is likely the tentative USB debugging symbol for the upcoming L release. In addition, there is a silenced alarm icon, whcih likely indicates some kind of built-in quiet hours functionality. Finally, it appears as if Android L will do away with KitKat’s status bar gradient in favor of a flatter look.
What are your thoughts on these unintentionally discovered screenshots? Are you a fan of this potential new look, or do you think that the move towards this cards UX metaphor is less than ideal? Let us know your thoughts in the comments below!
[Many thanks to everyone who sent in the reddit link!]
Want something on the XDA Portal? Send us a tip!
Smartphone cameras have advanced so tremendously over the past few years that they have almost completely replaced point and shoot digital cameras for the most of us. Furthermore, since our smartphones are always with us, the majority of us end up taking tons of photos throughout the lifespan of our devices. But what happens to all the old photos you take? Do you store them on an external hard-drive or keep them backed up to an online cloud service like Flickr? Let us know what your favorite way of storing old photos is and why.
Before the release of Android 5.0 Lollipop, the Holo Design guidelines served as the official reference for Android design, right from IceCream Sandwich to KitKat. However, updates to the guidelines were few and far between, leading to a lack of synchronization between Android design and current UI/UX trends. Google seems to have learned from their mistake the last time around, and earlier this week, a significant update was released for the Material Design guidelines, marking the second revision in less...