The smartphone landscape is drastically changing its focus. What was once a North-America-centric monopoly of high-specification phones is now merely an afterimage of the past. The meat of the game is elsewhere now; emerging markets looking for good bang-for-buck are what OEMs are increasingly aiming towards, and in this new game the old players must adapt-or-die. Xiaomi has grown at one of the most notable rates in the industry, leading it to become the world's most valuable start-up; and its...
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 email@example.com: Upgrade screen should
respect screen orientation
The following change refers to this bug:
Comment #2 on issue 382592 by firstname.lastname@example.org: 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!
There are so many Power Banks out there. However, they are not all the same. Some sacrifice weight for capacity. Others do the opposite. Some come with two ports and some come with more, while others come with less. Some are just batteries with a case around it, but others have some unique features. In this episode of XDA TV, Producer TK reviews the RAVPower RP-WD02 Wireless Filehub & Portable Travel Router. This device is the successor to the RP-WD01...
Most of this article doesn't only apply to Telegram+ -- it just happens to be an example that got a lot of coverage elsewhere, with many authors or commentators putting the full blame on Google, Telegram, the Telegram+ developer or even WhatsApp Inc (eh?). In this article, we'll try to look at the different aspects to provide a clear view of what actually happened, and what can (and hopefully will) improve with regards to developers in general and the Play...