zondag 29 maart 2015

Android 5.1 Lollipop

The Android 5.1 Lollipop update has been rolling out beyond those early-release Android One devices for a few weeks now, and while not every Nexus has 5.1 yet, a new security feature has just been rolled out to both Android 5.1 and 5.0: ''on-body detection.'' Head to the updated section below to see how it works and for more info on the Android 5.1 Android update.

Android L lollipop interface pink lol
Android 5.1 release date and features revealed. / © ANDROIDPIT
Update: Smart Lock is a security feature in Android 5.0+ that allows you to set certain objects (like smartwatches), locations (like your home or office) or your face as ''trusted'' - this means that when your watch is near your phone, you're at home or work or your front-facing camera can see you that your lock screen security will be switched off and pressing the power button on your phone will take you straight to the home screen.
''On-body detection'' has now been added to devices running Android 5.0 and above. The way on-body detection works is that once you've unlocked your device with a pattern or PIN it won't re-lock until it is set down. If you continue to hold your phone or put it in your pocket or bag it will remain unlocked. The process works with your device's accelerometer, so if you're laying in bed and hold your phone particularly still you will be prompted to re-renter your lock screen security.

AndroidPIT Nexus 5 Android 5 1 Lollipop security on body detection
This is ''on-body''detection in Android 5.1 Lollipop.  / © ANDROIDPIT

Android 5.1 Android update

The Android team has officially announced the Android 5.1 update on its official Android blog. The announcement comes complete with a few update details, including support for multiple SIM cards, Device Protection and high definition (HD) voice. You'll also get Wi-Fi and Bluetooth shortcuts in Quick Settings.
There's no details on scheduling for which devices and when, but you can start the good old button mash cycle right now. Head to Settings > About Phone > Software Update and get busy. If you're rocking a Motorola phone, Nexus device or Google Play Edition you're likely to be first in line for the update.
We'll do some button mashing ourselves and bring you more on the Android 5.1 update as soon as we have it, as well as a install tutorial as soon as the factory images are available.

test du motorola moto e 2015 android 00
Moto, Nexus, Android One, GPe: the quick updates list just gets bigger. / © ANDROIDPIT

Android 5.1 Lollipop update: when will I get it?

The first devices to get the Android 5.1 update will be the T-Mobile Nexus 6 and Verizon Nexus 6, with the T-Mobile Nexus 5, Nexus 7 and Nexus 4 also on the rapid fire update list - possibly by the end of the day if you're lucky.
The Nexus 9 will also be high on that list, along with the Moto X (2014), Moto G (2014) and possibly even the brand spanking new Moto E (2015). Google Play edition devices will also be quick to get the update action.
Previous coverage: HTC's ever-vocal, always-lovable Product Management Vice President Mo Versi was responding to a twitter question about the HTC One (M7) GPE update  a while back when the next version of Google's mobile OS was hinted at:

woensdag 25 maart 2015

HTC One M9+ to be launched on April 8

HTC will introduce a larger version of its M9 flagship on April 8 in China.

The company’s Chinese unit just published the image below on Weibo, along the #MoreThanOne hashtag, all but confirming the existence of the long rumored One M9+.

The image matches the numerous leaks from the past weeks showing a circular camera module and a secondary depth sensor mounted above it, just like on the One M8. Other than that, the device teased in the image features the same two-tone design and brushed metal texture of the One M9.

So, what do we know about this One M9+? Various leaks point to a 5.5-inch display, though at least one claims it will be just 5.2-inch, and there’s a solid chance the M9+ will feature a Quad HD screen, as opposed to Full HD on the M9. According to @upleaks, HTC is going to swap the Qualcomm Snapdragon 810 chip from the M9 (which caused it quite a bit of trouble) with a high-end chip from MediaTek. Other specs are likely to stay the same, save for the necessary changes in the camera and battery capacity departments.

One big feature that will differentiate the M9+ will be a fingerprint sensor mounted, somehow awkwardly, on the front of the device. HTC has used a rear-mounted fingerprint sensor on the One Max, but moving it to the front should bring better usability. We don’t know if this is a swipe-based sensor or touch-based, like the new Galaxy S6 and the iPhones.


maandag 23 maart 2015

Rumor: LG G4 5.6-inch Screen

A tweet from a  tipster with the handle @OnLeaks says that the LG G4 is going to feature a 5.6-inch screen. That would represent a slim .1 inch increase from the size of the screen on the LG G3. We expect the resolution to remain at 1440 x 2560. We don't expect to see the LG G4 introduced until May. The current flagship model was unveiled on May 27th, 2014.

The LG G4 will feature a 64-bit octa-core Snapdragon 810 under the hood. We could see a 16MP-20MP rear camera on the handset with OIS still included. Most likely LG will stick with 3GB of RAM and 32GB of native storage.

This year, LG will apparently have something even bigger up its sleeves with the LG G4 Note. Early speculation has the device earmarked for the second half of the year, carrying a 5.8-inch display. This model is apparently being considered as a challenger to the Samsung Galaxy Note 4, and will be offered with a stylus that might be

zondag 15 maart 2015

Google: Android 5.1 Memory Leak Has Been Fixed Internally, No Timeline For Release Yet

In the Android community, Lollipop 5.0 is known for a lot of things. Unfortunately, among those things is a pretty severe memory leak that has plagued users with app crashes and launcher redraws, as device memory filled and failed to clear.
When Android 5.1 was announced, many hoped the issue would finally be resolved. After all, Google did mark the memory leak (which climbed to the 34th highest position in the issue tracker's history) as "future release" back in December.
As it turns out though, Lollipop 5.1 is not without its own memory leak, at least for some users over at the issue tracker. But Google has some good news and some bad news. The good news is that the 5.1 memory leak has been "fixed internally." The bad news? "We do not currently have a timeline for public release."
Project Member #35 al...@android.com
This has been fixed internally. We do not currently have a timeline for public release.
Status: FutureRelease
Labels: Restrict-AddIssueComment-Commit 
The status change appeared 39 hours ago (at the time of writing) on an issue created March 12th, which you can check out for yourself below. Here's hoping the fix doesn't take too long to appear publicly, whatever the version number.

A memory leak that was originally discovered in Android 5.0.1, is still annoying and befuddling Nexus device users with Android 5.1. According to the Issue Tracker page on the AOSP website, Google has internally fixed the issue and plans to include it in an upcoming release. That most likely would be Android 5.1.1.  

The complaints are beginning to read the same. Apps, especially Google+, restart on their own. Some active apps disappear in the middle of using them, and free RAM drops in hours to about 750MB-800MB from 1.1GB-1.3GB. Most of the people who sent in a complaint appear to be using the Nexus 5, although other Nexus devices have been cited. Some complaints said that opening apps would increase the amount of RAM in use, but closing apps would not reduce that figure.

Issue 159738, "Memory leak still present on Android 5.1," was closed by Google on Friday. Now, it is just a matter of waiting for Android 5.1.1. Google will no doubt stamp this as "Rush" because no one wants to live with the craziness of a handset running with a memory leak.
Reported by jlmcr...@gmail.comMar 12 (3 days ago)
Memory leak not fixed. I've had system RAM bloated over 1GB, processes restarting and launcher redraws.

Android 5.1 running on a Nexus 5.