Nexus 4 Lollipop update coming ‘soon’

While Nexus 7 (2012,2013 WiFi models), Nexus 10 and Nexus 5 owners have seen both OTA and factory images of Android 5.0 Lollipop arrive, the Nexus 4 has so far been left out in the dark. The good news is that the latest sweet treat is coming soon for owners of the LG Nexus 4, at least that’s the word from Google’s Sascha Prüter.

On Google+, Prüter first teased that the Lollipop LRX21T was “Locked and loaded!” After a bit of poking and prodding by various G+ users (including Artem Russakovskii), it was revealed that he was referring to the Nexus 4’s upcoming Lollipop update.

No exact timeframe has is given, with Prüter only saying it will come soon, “not sure when exactly but shouldn’t be too long. Staging the factory images always takes some time.” So don’t be sad, Nexus 4, your time to shine again is almost here! We’ll be sure to update our readers as soon as we learn more.

Android Lollipop leaks appear for the LG G3 F400S and D855

By "Kunal Vohra", Director@H2K

LG has surprised everyone with the pace of its upcoming Android Lollipop update for the LG G3, which is scheduled to arrive sometime in the coming week. If you can’t wait just a few more days you may be interested in a couple of Lollipop builds that have recently leaked for the D855 and F400S models of the G3.

Controversially, these leaked KDZ files have gradually been made available via a pay walled teaser over at LGBBS. With some update versions brandishing a price tag apparently worth $200, the motives behind the leaks are a little questionable. Fortunately for intrigues sake, the good folks over at XDA have grouped together to grab and share the leaked files openly.

A Lollipop test build for the F400S version of the G3 appeared first. However, this software was built from the unfinished LRX16E version of Lollipop, resulting in the odd bug and hiccup for users to contend with. According to those who have tried out the ROM the UI feels considerably slicker than before. The video below gives us a little look at what’s in store for LG G3 owners.

The D855 version of the LG G3 has also received a leaked version of Android Lollipop, but this time it comes from the finalized LRX21M code base under LG’s D85519C version number. The result is fewer bugs and an experience that is likely to be very close to the update that LG will roll out to its handsets in the coming weeks. That being said, there appear to be a couple of new LRX21M based versions too, albeit still locked behind a paywall. This ROM appears to work on either the 16GB or 32GB models of LG G3 D855.

If you are eager to boot up Lollipop on your G3, you can grab the free F400 S file here, and the D855 file from here. Remember, ROMs designed for specific handsets won’t work on phones with different model numbers.

If messing around with manual installations isn’t your thing, you fortunately don’t have long to wait before LG pushes the update out officially.

Still Having Problem..!!! Connect with Admin

 Kunal Vohra

BBM: 7F72A48D

Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates 

Google posts Android 5.0 “LRX21L” factory image for the Nexus 9

The Nexus 9 Volantis factory image has now been officially put up, and while this doesn’t mean much for current Nexus owners, brand new Nexus 9 owners can immediately start playing around without worrying about messing up their devices — since factory images are well within reach if they need them.

So what about the rest of us? While the rumor mill claims that the images may have been delayed due to bugs and other issues, we really can’t say for sure. It could be sometime tonight, tomorrow or even in the days or weeks to come. We don’t blame you if you’re anxious for Lollipop on your existing Nexus — I know I am (my Nexus 5 wants to leave developer preview behind for good!).

Stay tuned, as we’ll be sure to provide more details as soon as we learn more about when the Nexus Lollipop images will hit.

By "Kunal Vohra", Director@H2K

Still Having Problem..!!! Connect with Admin
BBM: 7F72A48D


 Kunal Vohra Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates 

Lollipop opens up app access to microSD storage

r

Google is easing restrictions on access to the microSD card that were first introduced on KitKat. With the arrival of new Lollipop APIs, apps will again be able to write data to any folder on the microSD card, provided the user allows it.

On KitKat, apps can only write data to their own folders on the microSD card. This was intended as a security measure, as well as a way to prevent the “folder creep” that made a mess out of folders trees. But the limitation effectively crippled many apps that required “write access” across the folder tree, such as file explorers, music apps, or gallery apps. One of the best-known examples is ES File Explorer, whose developer Tod Liebeck went as far as to create an app (for rooted devices) that removed the limitation, so ES File Explorer could work as intended.

Now Google is backtracking on the limitation – in Lollipop, a new intent lets apps request access to folders from the microSD card, including folders belonging to different applications. The user can grant the app access to specific folders (say, just the Music folder for a media player app) or to the parent folder, which gives the app free access to everything on the card. This permission only needs to be granted once.

Here’s how Google engineer Jeff Sharkey describes this “richer access” in a Google Plus post:

We heard loud and clear that developers wanted richer access beyond these directories, so in Lollipop we added the new ACTION_OPEN_DOCUMENT_TREE intent.  Apps can launch this intent to pick and return a directory from any supported DocumentProvider, including any of the shared storage supported by the device.  Apps can then create, update, and delete files and directories anywhere under the picked tree without any additional user interaction.  Just like the other document intents, apps can persist this access across reboots.

This gives apps broad, powerful access to manage files while still involving the user in the initial selection process.  Users may choose to give your app access to a narrow directory like “My Vacation Photos,” or they could pick the top-level of an entire SD card; the choice is theirs.

It looks like Google has taken the – mostly negative – feedback to heart and made microSD folder access more flexible, while keeping the security measure in place for apps that have no business in modifying data across the microSD card. The responsibility of deciding what level of access an app is granted falls to the user, which isn’t ideal because it could lead to confusion, or at worst, exploitative behavior by shadier apps. But this compromise is still preferable to the lockdown from KitKat, which prevented many legitimate apps from working as intended.

Now we only need manufacturers to roll out Lollipop to their devices – check out our update roundup for what we know so far.

By "Kunal Vohra", Director@H2K

Still Having Problem..!!! Connect with Admin
BBM: 7F72A48D


 Kunal Vohra Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates 

Chainfire successfully roots the Nexus 9

Well that certainly didn’t take long. Rooters and modders that have expressed interest in the extremely new Nexus 9 will be pleased to know that superuser guru Chainfire has already successfully managed to root Android Lollipop running on the Nexus 9.

Considering that the factory images for Android 5.0 were only just released a few hours ago, it’s pretty fair to say that Chainfire works pretty darn efficiently. After all, in that amount of time he not only managed to root Lollipop on the Nexus 9, but he also managed to create a 64bit version of the superuser binary as well.

Now for those who can’t wait to get this device rooted (that would be me), there are a couple of things to keep in mind. Right now there is no custom recovery for the Nexus 9. Also, as this is a brand new device running a brand new version of Android, the typical CF Auto-root method is also not yet possible, as the CF Auto-Root framework hasn’t been updated to patch live kernels (which is an Android 5.0 requirement) or to work with 64 bit devices. That means that if you don’t have experience with ADB and Fastboot commands, you might want to hold off just a bit.

That being said, anyone familiar with ADB will be able to root the device in most likely under 5 minutes, as the process really is pretty simple. Chainfire has provided the 3 files you will need to complete the process, which basically consists of:

1. Enabling fastboot oem unlock via developer options and executing it
2. Performing fastboot boot inject.img
3. Performing fastboot flash boot patched.img.

As mentioned before, anyone with a bit of ADB/Fastboot time under their belt will find this process extremely easy to do. Chainfire went on to say that he will get started updating Auto-root with all of the new 5.0 components, but that it would require a bit of time.

Android L brought forward an insane amount of changes, and considering that 64 bit support came with it, it’s no wonder that it took Chainfire “a few hours more than I had hoped for” to get everything working. Rooters should also keep in mind that lots of root apps will probably be very buggy, or may not work at all on Android L until they are updated.

For those looking for the CFAR method to root their device, simply check out the Chainfire thread regularly to see when the update arrives.

With all the great things we’ve seen and heard about the Nexus 9, will you be rooting yours? Let us know why or why not in the comments below.

By "Kunal Vohra", Director@H2K

Still Having Problem..!!! Connect with Admin
BBM: 7F72A48D


 Kunal Vohra Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates 

Google Android 5.0 Lollipop Source Code being pushed to AOSP!

Well what do we have here, Android Lollipop being uploaded to AOSP as we speak! As you can imagine, a code dump like this takes a great deal of time, and it could be hours before everything is completed. At the moment, the branch is being referred to as “lollipop-release” and it carries a build number of LRX21M, though its official release tag should be android-5.0_r1 when it ‘fully hits’.

Even more exciting, it’s also only a matter of time before device-specific repositories for all Nexus hardware shows up, and at least a few have already surfaced including theNexus 7 (2013) LTE ‘deb’ and Nexus 7 (2013) Wifi ‘flo’. It is worth noting that a new repository for Android TV is also available now, though it is hard to say whether or not the full code will be uploaded.

Once everything is uploaded, it’ll only be a matter of time before developers and many others begin playing around, bringing us hidden goodies and so much more. And before you ask, no the Nexus factory images are not up yet. Patience my friends, all in good time.

By "Kunal Vohra", Director@H2K

Still Having Problem..!!! Connect with Admin
BBM: 7F72A48D


 Kunal Vohra Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates 

HTC’s countdown begins, Lollipop in 90 days for One M8 and M7 owners

Back in June, HTC first announced that it would bring the next version of Android (then known simply as Android L) over to the One M7 and One M8 within 90 days of receiving the final code from Google. Now we can all start our timers, as HTC’s Mo Versi has taken to Twitter with the good news that HTC has the code in hand.

As before, the update is promised for the One M8 and M7 within 90 days worldwide as part of their “HTC Advantage” program. As is typical, unlocked handsets will be among the first to receive the update, and US carriers will likely be among the very last.

Although HTC’s tweet doesn’t mention any other HTC devices, just two weeks back we received (unofficial) word that HTC planned to bring the update to a variety of devices including handsets like the Desire Eye, One E8, One Max and many others. Of course these devices won’t actually receive the update until sometime after HTC’s main flagships (M7/M8). So mark your calendars folks, if all goes well, you should have Lollipop on your HTC One no later than three months from now.

What do you think of HTC’s commitment (and transparency) to fast updates? Tell us in the comments below.

By "Kunal Vohra", Director@H2K

Still Having Problem..!!! Connect with Admin
BBM: 7F72A48D


 Kunal Vohra Download Our Official Android App & Get Free Internet

"The Hackers Street"

For Daily Updates