Slatedroid info

Everything about android tablet pc [slatedroid]

OnePlus One gets its own Stock Android ROM

Posted by wicked July - 24 - 2014 - Thursday Comments Off

OnePlus promised to be different and, to some extent, they are. That desire to be unique and to never settle shows up once again today as OnePlus revealed a gift for lovers of a 100 percent, pure, vanilla Android experience: A stock Android ROM just for the OnePlus One, complete with a gapps download, and instructions for flashing, all without voiding your warranty.

This stock Android image is somewhat amusing. OnePlus One already has the distinction of being the only commercial product that actually runs a custom ROM, although modified, out of the box. Sure, the OPPO N1 could have had that honor, except for the fact that the CM-toting N1 was only a limited edition and the regular versions only allowed dual booting at the very least. Given how CyanogenMod is itself already quite close to an AOSP-based vanilla Android setup, it might seem that this stock Android ROM is a bit redundant.

CyanogenMod, however, does add quite a bit on top of plain Android, which is evident when you compare it to the version running on a Nexus, which itself is also modified by Google. Most of the CM bits are there mostly for convenience primarily and, in the case of very specific CM features like CM Account, to add value. What this stock ROM provides, then, is a jumping board for other OnePlus One compatible ROMs, features, and development that could come out in the near future. One interesting note that OnePlus makes is that flashing this stock ROM does not void your device warranty, definitely an unconventional arrangement. Bricked devices, however, are not covered by that warranty.

A smartphone with flagship specs at half the price, CyanogenMod 11 out of the box, stylized back covers starting with bamboo, support of two of the largest custom ROM communities, and, now, its very own stock ROM. OnePlus One is turning out to be quite a dream come true, except that it is slowly becoming a nightmare for some. With yet another wave of invites raffled off, there doesn’t seem to be any sign that OnePlus will be making this One available to the general public, which makes trying to get a OnePlus One feel like trying to win a lottery. Considering how they are handing out invites anyway, it technically is.


Kernel source files for LG G Watch and Samsung Gear Live released by Google

Posted by wicked July - 22 - 2014 - Tuesday Comments Off


Google, via the Android Open Source Project (AOSP), has made the official kernel files for the Samsung Gear Live and LG G Watch available for download. This is good news for developers who want to work on developing custom ROMs for the devices or fine tune apps to take full advantage of the platform. Being smartwatch devices, this should also help those developers who want to create unique watch faces for the devices.

In releasing the code, Bill Yi on the Android Building Google Group indicated the development team is planning a “full platform push” for the next version of Android, currently dubbed Android L.

If you want to grab the source, hit the source link below.


Come comment on this article: Kernel source files for LG G Watch and Samsung Gear Live released by Google

Google uploads part of the Android Wear source code to AOSP

Posted by wicked July - 22 - 2014 - Tuesday Comments Off

Eager wearable developers can now get their hands on the source code for Android Wear devices, or at least part of it, as Google has uploaded version 4.4w_r1 of the wearable code to the AOSP repository. However, this is only a partial release related to GPL projects for devices which are currently shipping, much like what we have seen with the Android L developer preview.

Files for this new release can be found under the android-4.4w_r1 tag in the repository. Active development branches of the wearable code can be found under the kitkat-wear directory, hence 4.4w, which is where future patches and minor updates will be placed. Speaking of which, we can probably expect a number of changes to the wearable code as Google works out the bugs and kinks of its new platform.

Android Wear AOSP screenshot

In addition, Kernel sources for the LG G Watch (Dory) and Samsung Gear Live (Sprat) have also appeared in the directly for download, which might help out developers looking to work with these particular smartwatches.

Although this is only a partial release of the full code, Bill Yi has explained that Google will be making a full platform push for Android’s next milestone release, Android L, which will offer developers much more to work with.

The release of the full Android Wear source code, expected around the launch of Android L later this year, will open up the platform to developers wishing delve into the finer details. It’s going to be interesting to see what developers can find to tweak and what new ideas they can pull from the code.


If you haven’t heard already, XDA is putting on its second annual xda:devcon. This year, we’re doing it international style and holding the even in Manchester, UK on the weekend of September 26-28. We have great sponsors from Sony and Oppo who joined us last year, to newcomer OnePlus. However, it takes more than great sponsors to make an event like the successful, it takes great speakers.

Returning to xda:devcon is a speaker from last year. Founding member of the “Free Xperia Project” and now a Community Manager with Sony Developer Relations, Alin Jerpelea has a core technical background and has been active on XDA since 2006 on multiple platforms.

At xda:devcon ’13, Jerpelea gave a presentation entitled “Android on Legacy Devices – Use It or Lose It.” In that presentation, he holds a dialog with the audience and talks about how Android support on legacy devices from developers is demanded by a lot of people because manufacturers rarely release Android updates. Developers and members at XDA work hard to support devices on new Android versions. Jerpelea pondered how much we should push those devices. Is it enough to have the latest Android version booted, or do we want more? Check out the video to see what they have to say on this video from last year.

This year, Jerpelea returns and offers up another excellent presentation. This time, he will be giving a talk entitled “AOSP For Sony Devices: Past, Present and Future.” Have you ever wonders what Sony is doing to open up for more collaboration and more innovation in the Open Source community? In this session Alin will share with you where Sony is taking AOSP for Xperia in the short term. Sony wants to support external community innovation, so Alin will discuss how Sony will improve their work on openness around AOSP.

Join us September 26 to 28 in Manchester for XDA:DevCon 2014. Register to attend using this link for exclusive savings. Hurry as the Early Bird registration ends August 1st.

The post Sony Developer Relations Community Manager Alin Jerpelea to Talk About Sony AOSP at XDA:DevCon 2014 appeared first on xda-developers.

Browse the New AOSP Code Commits in Android L Developer Preview

Posted by Will Verduzco July - 3 - 2014 - Thursday Comments Off

android l aosp changelog

It’s been just one week since Google introduced Android L to the world at the Google I/O 2014 opening keynote. In the time since, we’ve gotten our hands on the developer preview release and even managed to root it. Then in a surprising move, Google decided to open source part of the Android L codebase in limited capacity.

We don’t yet have the complete L source code, and likely won’t until its official release in the Fall. However, the fine folks over at FunkyAndroid have done what they do best by listing out every code commit available in the recently open sourced component of the Android L developer preview.

The FunkyAndroid team has already given us developer changelogs for Android,4.4.2_r2, 4.4.3, and 4.4.4. Now, they’ve gone ahead and given us yet another developer changelog for the open source components of the Android L developer preview. As always, this service is made possible thanks to an open source script released by none other than former AOSP lead JBQ.

In a change from usual operating procedures, today’s changelog comes in two forms: a version with chromium-related changes and a version without. The former racks in about 60k commits, while the latter roughly halves that. However, it’s important to keep in mind that this list only looks at the partial source code that was made available two days ago. As such, not every change has made it into this list, and there are even potentially changes in this list that aren’t in the developer preview images.

[Thanks to everyone who sent this in!]

The post Browse the New AOSP Code Commits in Android L Developer Preview appeared first on xda-developers.

Android L Preview Hits AOSP for Nexus 4, 5, 7 and 10 (Updated)

Posted by Kellex July - 2 - 2014 - Wednesday Comments Off

When Google released the Android L Developer Preview last week to the Nexus 5 and Nexus 7 (2013), I can imagine that a number of you were disappointed – namely those with a Nexus 4, Nexus 7 (2012) or Nexus 10. While Google still hasn’t released flashable images for any of those devices today, they have pushed Android L code for each to the Android Open Source Project (AOSP), which means that your favorite developer will likely having something for you shortly in the form of a ROM

Once that happens and you get to flashing, you may want to cruise through the substantial list of Android L features we have already covered in a number of posts. You will find overviews of goodies like the new Quick Settings Panel, multi-tasking,  managing notifications, Heads-Up notifications, an improved Android Beam, Do Not Disturb mode, and more. To catch the full list, you will want to start here.

AOSP Links:  Nexus 5 | Nexus 4 | Nexus 10 | Nexus 7 (2013) | Nexus 7 (2013) LTE | Nexus 7 (2012) | Nexus 7 (2012) 3G

Update:  As has been noted in the comments, this is not full source, so no ROMs just yet. Meh.

Android L Preview Hits AOSP for Nexus 4, 5, 7 and 10 (Updated) is a post from: Droid Life

Google posts Android L preview source code for various Nexus devices

Posted by wicked July - 2 - 2014 - Wednesday Comments Off


The preview of Android L can now be tried on additional Nexus devices. Last week at Google I/O, the source code was made available for the Nexus 5 and Nexus 7 (2013) while others were left out. Google has added the Nexus 7 (2012), Nexus 10, and Nexus 4 to the Android L preview. Older Nexus devices like the Galaxy Nexus and Nexus S are obviously being left behind due to age.

Hit the break for individual links to each device.

Source: AOSP

Come comment on this article: Google posts Android L preview source code for various Nexus devices

Limited Android L Developer Preview Source Code Now Available, Support for Current Nexus Devices

Posted by Will Verduzco July - 2 - 2014 - Wednesday Comments Off

Android L Developer Preview Source Code in the AOSP

Update: As pointed out by XDA Forum Member a3361035 in the comments below, this isn’t a complete release just yet. Rather, these are just a few GPL projects for the L-Preview release, and not a full platform update.


As we mentioned earlier today, the Android L Developer Preview is exactly that–a developer preview. However, many users understandably want to taste the future of Android today. As such, quite a few Nexus 5 and 7 owners have ventured to install the Android L Developer Preview firmware images on their daily driver devices.

Unfortunately, not every one happens to own a hammerhead or flo. But now, as a surprise to many, Google has pushed the Android L Developer Preview source code to the AOSP under the “android-l” branch. Device-specific support is available for the Nexus 4 (lge/mako), Nexus 5 (lge/hammerhead), Nexus 7 2012 WiFi (asus/grouper), Nexus 7 2012 Mobile Data (asus/tilapia), Nexus 7 2013 WiFi (asus/deb), Nexus 7 2013 Mobile Data (asus/flo), and Nexus 10 (samsung/manta).

While these files were most likely released in order to help OEMs and third party developers begin preparing for L’s release, they will also enable custom ROM developers to build Android L releases for their devices of choice. But naturally, building for unsupported devices will be more difficult due to the lack of L-enabled proprietary binaries and device trees. As these source files are only for a few GPL projects and not the entire L-Preview AOSP source, this isn’t of benefit to ROM developers just yet. However, those wishing to learn more about the L preview may find use in the code.

Developers, head over to the AOSP to peer into the code. From there, all the relevant code will be available in the relevant subfolders with the “android-l” branch. ROM developers looking for device-specific files can find the goods in the appropriate links below:

[Many thanks to XDA Recognized Contributor ryukiri and everyone else who sent this in!]

The post Limited Android L Developer Preview Source Code Now Available, Support for Current Nexus Devices appeared first on xda-developers.

AOSP Commits Reveal Change to API Level Naming Convention

Posted by Will Verduzco June - 22 - 2014 - Sunday Comments Off

AOSP Commit 99021

Google I/O 2014 is just a few short days away, and many of us waiting on the edges of our seats in hopes of a new Android release. There’s naturally much speculation to be had as to what this upcoming version will bring when it eventually reaches consumers. However, we’ve also been able to glean relevant information about the future of Android by looking at recent AOSP merges.

Recently, we talked about how the next major Android release is poised to remove Dalvik runtime compiler altogether and set ART as default. That, however, is not the only piece of information that can be had about the future of Android. New merges to the AOSP master branch by Googler Andrew Hsieh indicate that the next major version of Android will revise API level naming convention.

Up until now, Android API level naming convention has dictated that all versions receive numerical API levels. This started with Android 1.0, which was API level 1, and has continued onward to KitKat, which is API level 19.

Now according to two recent merges to the AOSP master branch, it seems like 64-bit API levels will be renamed to non-numeric characters, with the 64-bit iteration of the Android-L release receiving the letter “L” for its API level. The merges themselves mention that this new naming convention is tentative, though this will potentially make things easier for developers creating native apps with the NDK.

Change 99021 - Merged
64-bit in android-L
Tentatively rename 64-bit API level to non-numeric: ‘L’
Change-Id: I676099e467d5426da6cd1d96d63fc201f78ce533

Change 99016 - Merged
64-bit in android-L
Change-Id: I10daf2da97aa9d3c99661b5d79080b96a0ae9f22

What do you make of all of this? If nothing else, it further goes to show the heavy emphasis Google is placing on 64-bit computing in Android-L (perhaps Lollipop?). Share your thoughts and conspiracy theories in the comments below.

[Many thanks to XDA Recognized Developer helicopter88 for the heads up!]

The post AOSP Commits Reveal Change to API Level Naming Convention appeared first on xda-developers.

Dalvik Virtual Machine to be Replaced By ART in Next Version of Android

Posted by wicked June - 20 - 2014 - Friday Comments Off

It’s (almost) official: Google will eschew the Dalvik virtual machine for ART in the next release of Android. Commits in the AOSP master branch point to the removal of Dalvik entirely.

What does that mean, exactly? Dalvik was a useful stop-gap for Google in the early days of Android, when the team had to formulate a solution for running apps on a myriad of hardware. The virtual machine essentially acted as a translator of sorts, interpreting code to run on different architectures.

ART, or Android Runtime, is a much more efficient solution. Instead of “translating” code, it compiles it natively for each device. That comes with the disadvantages of slower install times and larger install files, but the benefits of slightly increased battery life and more responsive apps.

ART was integrated into Android last year with the release of Android 4.4 “Kit Kat.” It can be enabled on devices running that firmware and above, but many apps aren’t completely compatible with it yet. Hopefully developers will update their apps by the time ART becomes the new standard.

Via: XDA Developers

Dalvik Virtual Machine to be Replaced By ART in Next Version of Android is a post from: Droid Life