In a rather surprising move, HTC is the first OEM to promise an update to Android L. HTC has stated that this policy is part of their HTC Advantage program and that this will apply to the One (M7) and One (M8). There’s also the caveat their 90 day delivery promise applies to when HTC first receives the code, not when the developer previews go live.
Today at Google I/O many of Google’s designers and engineers took to the stage to give the world a few previews of the new design and features that will be included in the yet to be named upcoming Android L release. The most visible of all the changes comes with Google’s new design language and so that’s something to talk about first before focusing on the changes under the hood.
Google’s new design language is something they call Material Design. Material design is something Android users are already familiar with from the design of Google Now and some of the recently updated Android applications like Google I/O 2014. Material design takes inspiration from physical materials like paper and ink, but implements these concepts in a modern way that is very different from other designs like the skeuomorphic interface of old versions of operating systems like iOS. In the upcoming Android L release the entire interface will be redesigned using this new type of design language. To demonstrate it, Google’s Director of Android User Experience Matias Duarte demonstrated the upcoming changes to the Gmail application after being redesigned using these new principles of Material Design.
As you can see, the app adopts a much cleaner and more colorful appearance while still being completely familiar to users acquainted with the older application. The use of lines in the application has been reduced with the lines that separate emails being thinner and extending only across a portion of the screen, and the border from the star on favorited emails being removed entirely. The contact icons adopt a circular design similar to what Apple has done with iOS 7, and a circular bubble for starting a new email is ever-present at the bottom of the display. One final thing to note is the retirement of the three dot overflow menu in favor of moving settings and navigation into the pane that slides in from the left side of the display.
Another significant part of the new design language which is hard to describe in photos and words is the use of depth, shadows, and animations. Google has really worked hard on creating an interface that feels responsive and resonates with how humans interact with devices. In Android L every interface element can have a Z-axis level specified and this will change how the application looks by altering 3D views and adding lighting and shadows that will be different in size and scale based on what position an element is on the 3D plane.
Google’s new Material Design principles are something they hope developers will use to create unified applications across all of their platforms, extending far beyond Android. Some more info about the fundemental principles of Material Design can be found in this guidebook.
In Android L Google is making significant improvements to how notifications are handled on Android. A feature that is often requested is lockscreen notifications and in Android L Google is displaying notifications right on the lockscreen of a device.
As you can see, each application can display a card on the lockscreen to notify the user of anything they missed. Multiple notifications from the same app are consolidated into one card to make effective use of space. By swiping down the user reveals other cards that are further down in the list of notifications. Touching a card brings the user to the application the notification was for, and swiping cards to the right removes them in the same fashion as swiping away banners in the normal notification center.
Google has also improved how notifications work within applications. In a similar fashion to the new notifications shown in the iOS 8 preview. Android notifications can now present the user with banners that appear at the top of the display with relevant options for responding to them. During the keynote Google demonstrated how a user can recieve a video call while playing a game and they can choose to either decline and continue playing or answer and be taken to the application the notification was sent from.
Android L will also bring along big changes to the recent apps list. Currently the recent apps list consists of a single card for each application that the user has recently opened. In Android L applications will now be able to display multiple cards in the recent apps list to make it easier for the user to navigate and to create a more complete history of where the user has recently been on their device.
As you can see above, the recent apps list uses the new principles of Material Design. Each application is presented as a card in a scrolling list with realistic lighting and shadows that reacts to the position of the cards in the list. One very important thing to mention about the new functionality about the recent apps list is that it includes cards for each browser tab that the user has open, rather than just consolidating them all to a single card for whatever web browser the user uses. With this Google is making a statement about how they feel about web applications and how they should be treated similarly to native apps on the device. It is a very different approach from what Apple and Microsoft are doing but with Google’s far reaching web services it makes sense to handle web applications this way. It may also reduce the number of apps created that are simply mobile websites wrapped in an application which is good for all users.
Android L brings along some major improvements to the underlying OS along with all the changes on the surface. One of the most significant for developers and users alike is the retirement of Google’s Dalvik virtual machine. Dalvik has been the software that runs Android applications since the beginnings of Android itself and with Android L Google is removing it entirely in favor of their new ART runtime. While Dalvik uses mainly Just-in-Time code compilation to compile Java bytecode into machine code at the time it is run, ART opts for Ahead-of-Time compilation which compiles Java bytecode into machine code at the time of install. Because of this, applications do take up slightly more space and take longer to install, but there should be significant performance improvements with this new Android runtime. During the keynote Google noted that benchmarks running on ART can see up to 4x the performance over the same benchmark being run in Dalvik. Google also made a point of noting that ART is very cross platform with support for x86, ARM, and MIPS instruction sets.
The next big announcement is 64-bit Android support. Apple launched the first 64bit mobile devices with iOS 7 and the Apple A7 CPU in late 2013 and a 64-bit version of Android has been long awaited ever since then. Android L includes complete support for 64-bit with all instruction sets that Android supports including ARMv8, x86-64, and MIPS64. With this comes support for larger numbers of registers, and an increase in the addressable amount of memory which will come in handy in the near future if the amount of RAM in Android devices continues to increase at the rate it currently is.
Battery life is always a concern with mobile devices that are running increasingly more powerful hardware and complicated software. In Android L Google has been working on what they call Project Volta. Project Volta is an effort to improve the battery life on Android smartphones through software optimization. Volta has a part aimed at developers and a part aimed at users. The part aimed at developers starts with a new tool that Google has created called Battery Historian.
Battery Historian is a tool that allows the user to see how the battery is being used on their device and at what times certain hardware features or processes are using the battery. This is mainly aimed at developers to help them improve when their application performs things like network requests which involves waking up the device’s radio and using lots of power. In the image above you can see a sample scenario where an application is causing a device’s radio to wake up roughly every twenty seconds. Developers can use this information to better schedule when their application should perform updates and grab information from the internet.
Google is also including a JobScheduler API for developers which allows them to perform specific tasks in their application during certain circumstances. An example would be only checking for updates when the device is connected to WiFi rather than doing it over cellular. The JobScheduler API can also have an application check for updates and new information at the same time as other applications to reduce the number of times a device has to wake up the radio and perform network tasks.
For users Google is including a feature that we’ve seen many OEMs implement on recent smartphones. Battery Saver is a feature that can reduce the performance of a device and limit the functionality of it to extend the battery life of a device when its battery has dropped below 20%. When the user’s battery is low the system will send a notification that allows the user to quickly enable the feature. It is not entirely clear to what extent the new battery saver feature limits the performance and capabilities of the device.
All these features are just a preview of what Google is doing in the upcoming Android L release. Google has not given a timeframe on when Android L will begin to ship but it’s clear that Google is very serious about creating a unified experience across all devices for all users and that Android has become their vessel to do so.
Today Microsoft announced a second iteration of the Nokia X family of low end smartphones they first announced at Mobile World Congress earlier this year. The new device is the Nokia X2 Dual SIM, and is a slightly higher specification device than the original Nokia X device announced in February.
First, the display is slightly improved with the addition of Nokia’s ClearBlack polarization technology which Brian Klug covered in his review of the Lumia 900. ClearBlack helps with blacks as well as outdoor viewing by using polarization and several layers to reduce reflections on the display. It can make an mediocre display look OK, and a good display look great, at least in my experience. This ClearBlack technology is outfitted onto the 4.3” 800×480 resolution display of the new X2.
Also improved is the SoC. The original Nokia X was based on a Qualcomm Snapdragon S4, and the new device bumps it up to a current generation dual-core Snapdragon 200. In addition, the X2 trumps both the original X and the larger XL devices with 1 GB of RAM, however it keeps the same amount of storage as the other devices in the line with a small 4 GB but does support expansion with up to 32 GB of microSD.
The camera is also bumped up from the X which had a 3 MP fixed focus camera. The X2 has a 5 MP autofocus model with f/2.7 and a LED flash. Camera size is 1/4 inch so it’s unlikely this camera will be very effective in dim scenarios, but with the flash it should at least take some sort of picture. There is also a Front Facing Camera – a bonus over the original X, but it is only VGA resolution.
On the software side, the Nokia platform has been revved to “Nokia X software platform 2.0” with this release which offers enhancements to the user interface such as a Windows Phone-esque alphabetical app list, a new home key, and a pull-down notification screen. While an update is scheduled for existing devices, the software platform 2.0 will not be available on the older X and XL models due to hardware limitations of those devices.
| Nokia X Series | ||||||
| Nokia X | Nokia X2 | Nokia XL | ||||
| Display | 4″ 800×480 | 4.3″ 800×480 with ClearBlack | 5″ 800×480 | |||
| SoC | Snapdragon S4 (dual-core 1 GHz) | Snapdragon 200 (dual-core 1.2 GHz) | Snapdragon S4 (dual-core 1 GHz) | |||
| Memory | 512 MB | 1 GB | 768 MB | |||
| Storage | 4 GB | 4 GB | 4 GB | |||
| Camera |
3 MP Fixed Focus 1/5 inch No FFC, No FLash |
5 MP Auto Focus 1/4 inch VGA FFC, LED FLash |
5 MP Auto Focus 1/4 inch UXGA FFC, LED FLash |
|||
| Weight | 129 g | 150 g | 190 g | |||
| Battery | 1500 mAh 3.7 V (5.55 Wh) | 1800 mAh 3.8 V (6.84 Wh) | 2000 mAh 3.7 V (7.4 Wh) | |||
As for the actual device, it’s going to be available in Black, White, Yellow, Green, Orange, and Grey with an “Inner Glow” outer clear coat. The device goes on sale in July with an expected MSRP of €99 (around $135 USD).
We weren’t really sure what was going to happen to the X Line with the Microsoft acquisition, but at least one more device has now launched so obviously there is some internal support for AOSP with Microsoft services. It’s likely this device was already in the pipeline prior to the acquisition, so we’ll have to wait and see if any other Android based devices find their way out of Microsoft. It will be interesting to see if we ever get any sales numbers on the X line vs the low end Windows Phone line (Lumia 520, 630, etc) because all of the X line phones have come in at or around the same price as the Lumias. We’ll have to wait and see at the next financial call if any of the numbers are broken out, but I wouldn’t count on it.
While this launch is Korea-only, Samsung recently announced a new version of their Galaxy S5 smartphone, dubbed the Galaxy S5 Broadband LTE-A. Naming aside, this makes this phone the first to launch with APQ8084 and MDM9x35. For those unfamiliar with Snapdragon 805 and MDM9x35, this means that the CPUs are now Krait 450 instead of Krait 400, and the GPU is now Adreno 420 instead of Adreno 330. While the CPU revisions are minor, the GPU is fast enough to have the same level of performance at 1440p as an Adreno 330 at 1080p. The MDM9x35 modem also means that category 6 LTE is supported for speeds of up to 300 Mbps. The MDM9x35 is also the first 20nm SOC part shipping from TSMC, which bodes well for 20nm SoCs in the near future.
Qualcomm also notes that this phone integrates the WTR3925 transceiver, so carrier aggregation is done on a single chip instead of the WTR1625L/WFR1620 dual-chip solution that was previously needed. Samsung also integrated a QHD (2560×1440) OLED display into this model at the same 5.1″ display size. The only other difference is that the phone now has 3GB RAM instead of the 2GB present in the international model. Otherwise, the rest of the phone is identical to the international Galaxy S5. It’s curious to note that Samsung has chosen to use the 2.5 GHz bin of the APQ8084 line rather than the highest 2.7 GHz bin, although the reasons behind this decision aren’t quite clear yet.
While this launch is Korea-only, Samsung recently announced a new version of their Galaxy S5 smartphone, dubbed the Galaxy S5 Broadband LTE-A. Naming aside, this makes this phone the first to launch with APQ8084 and MDM9x35. For those unfamiliar with Snapdragon 805 and MDM9x35, this means that the CPUs are now Krait 450 instead of Krait 400, and the GPU is now Adreno 420 instead of Adreno 330. While the CPU revisions are minor, the GPU is fast enough to have the same level of performance at 1440p as an Adreno 330 at 1080p. The MDM9x35 modem also means that category 6 LTE is supported for speeds of up to 300 Mbps. The MDM9x35 is also the first 20nm SOC part shipping from TSMC, which bodes well for 20nm SoCs in the near future.
Qualcomm also notes that this phone integrates the WTR3925 transceiver, so carrier aggregation is done on a single chip instead of the WTR1625L/WFR1620 dual-chip solution that was previously needed. Samsung also integrated a QHD (2560×1440) OLED display into this model at the same 5.1″ display size. The only other difference is that the phone now has 3GB RAM instead of the 2GB present in the international model. Otherwise, the rest of the phone is identical to the international Galaxy S5. It’s curious to note that Samsung has chosen to use the 2.5 GHz bin of the APQ8084 line rather than the highest 2.7 GHz bin, although the reasons behind this decision aren’t quite clear yet.