Database Users

Google JellyBean SDK

Thursday, July 19, 2012
Google Jelly Bean SDK Updated, Full Version Open To Downloads
2:01 AM Sophia
The version of Google’s Jelly Bean SDK is officially released and available for download! Being obtainable since Google I/O in a preview state, the new version is fairly improved and brings number of patches and bug fixes.
So the latest SDK tools revision 20.0.1 is now open and moreover, it is ready for developers to download! Before you rush to get it, learn what’s new first:
SDK tools revision 20.0.1 Dependencies include the following : the SDK Tools r20.0.1 is designed for use with ADT 20.0.1 and later, so those developing in Eclipse with ADT will need to , update the ADT Plugin to 20.0.1 first. Apache Ant 1.8 or later is required for those developing outside the Eclipse. And one more thing requited is the Android SDK Platform-tools revision 12 or later.
The improvements and bug fixes brought by the SDK tools revision 20.0.1 include the following:
• Fixed wrong check on build state that forced repetitive Java code recompilation;
• Fixed problems with running more than one emulator and running multiple emulators with GPU acceleration;
• Improved resize algorithm for better rendering on scaled emulator windows;
• Fixed a bug in the lint check for unprotected broadcast receivers to ignore unprotected receivers for default Android actions;
• Fixed build issue for projects using Renderscript;
• Fixed memory leak in the emulator.
DOWNLOAD
The SDK tools revision 20.0.1 can be obtained from HERE
original thread here

....... wrong post

...wrong section :laugh:

So you just copy and paste something and post it in Development section instead of General?

[Q] Flashing custom kernel only on my Nexus 7 (2013)

Hi,
my only goal is to use my Nexus 7 (2013 version, running kitkat) to view digital television (dvb-t).
Therefore, have I unlocked it (with complete erase grrr), then rooted it.
And finally, read about one hundred message threads on xda to know how to compile dvb modules for my kernel (3.4.0-gac9222c).
My problem, after all this work, is that it seems that Google did not compile its kernel with modules support.
After doing
# lsmod, I got the following error:
/proc/modules: No such file or directory.
This means apparently that there is no modules support for this kernel.
http://stackoverflow.com/questions/18818442/loading-kernel-modules-in-android-4-3
My 2 questions is the following:
(1) is it possible to flash a kernel image on my nexus 7 to get module support
(2) is it possible to do that without reflashing my ROM (my stock ROM is enough for my needs)
Cheers,
Louis

I am now in the process of recompiling my own kernel for my Nexus 7 2013, incorporating the DVB-T drivers that I need.
I found a very good tutorial for doing this: http://pete.akeo.ie/2013/10/compiling-and-running-your-own-android.html
The only problem is that the sources of dvb usb drivers in the Android kernel are not up-to-date.
I am searching an easy way to inject the last sources from git://linuxtv.org/media_build.git into the Android kernel?
The directory structure is different. I think i will be forced to update the Makefiles and the Kconfig files by hand, and add & replace .c and .h files manually. I someone has a better (more lazy) solution, I am interrested :victory:
Meanwhile, I play with an old Freecom usb DVB-T stick that is supported by old media sources in the Android kernel.

Wrong forum, here is the 2013 model's one: http://forum.xda-developers.com/nexus-7-2013

Upgrading the ZTE Open 1.1 to 1.2 keeping official rom

ZTE officially updated the ZTE Open to 1.1 and abandoned it.
To manually update it to the latest and greatest, follow these simple steps:
Grab a copy of Ubuntu 12.04, and install basic pre-requisites:
https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites
You can follow this for a basic build environment http://forum.xda-developers.com/showthread.php?t=2634107
clone the b2g repository:
Code:
git clone git://github.com/mozilla-b2g/B2G.git
now if you want to build 1.2 run
Code:
cd B2G
BRANCH=v1.2 VARIANT=user ./config.sh inari
Wait for it to build.
when it finishes run
Code:
./build.sh gecko
This will build only gecko at the 1.2 version
to flash run
Code:
./flash.sh gecko
this will update gecko to the version you chose, we now need to update gaia to the same version
run
Code:
cd gaia
MOZILLA_OFFICIAL=1 make production
This will leave you with the ZTE 1.1 stock rom, with a gonk 1.1 HAL base, but with the final version 1.2 Gecko and the final version of 1.2 Gaia.
1.3 upwards need a Jellybean base and we do not even have the true kernel source for the zte open, so this is the furthest stable rom you can get with the ICS based stock rom ZTE have given us.
You can build 1.3, 1.4, 2.0, 2.1 and 2.2 gecko using the above method, but I find it very unstable and broken, due to the Gonk HAL being so out of date.

When flashing the Gaia layer to the ZTE Open use "MOZILLA_OFFICIAL=1 make production" instead of "make reset-gaia"
Doing this updates the Gaia layer as normal but with the official Firefox OS branding (thanks to the MOZILLA_OFFICIAL=1). This means the browser will have the Firefox logo and so will the logon and log off boot screens. More importantly, the "make production" command will make the build you create be optimised as if it was official. This means offline caching of applications. "make production" also does not add any testing apps to your phone, so it is as if the build you are using is official.
The code again is "MOZILLA_OFFICIAL=1 make production" and it should be used where "make reset-gaia" is in this post :good:

What's the difference between "VARIANT=user" and "VARIANT=userdebug"?

LinuxHolic said:
What's the difference between "VARIANT=user" and "VARIANT=userdebug"?
Click to expand...
Click to collapse
The valid build types are:
eng – this variant will have some development tools and predefined settings that developers need (e.g. USB debugging enabled).
user – this is the variant for a product that suppose to go out to the users. Will use only modules that the end-user will need and more restricted settings.
userdebug – A combination of the user and eng variants. It’s intended for users testing your environment, but not developing it.

Noob question about compiling AOSP from source

Hi,
I want to learn more about Android kernel development so I'm trying to compile AOSP (Android 7) from source for my Nexus 7. I have prior experience doing Linux kernel development but the real hurdle for me is the Android build environment.
I have checked out android-7.1.2_r39 with the proprietary blobs for Nexus 7 and I've made it to the point where I need to choose a target.
However because I'm trying to compile Android 7, `full_grouper-userdebug` does not show up on the build target list when running `lunch`.
Is it enough to grab the /device/asus/grouper directory from a tree where it is included and add that to my AOSP tree or is there something else I need to do to compile Android 7 for this device?

Raspberry Pi 4 can run both Android and Linux apps.

Hi,
We make a Debian based Linux distribution that runs as an application on top of Android.
For Raspberry Pi 4 we use KonstaKang's latest 64bit LineageOS 19 (Android 12).
Installation is as simple as installing Android APK's. You can download a free evaluation
version from volkspc.dot.org.
Regards
Vasant

This can also be done with apps like AnLinux, Andronix, Debian noroot, or with proot-distro in termux.

It has been a while since I updated thread - . We just made a new release yesterday. This is based on KonstaKang's LineageOS 20 (Android 13). We also provide a SDK so that developers can build their own Debian Bullseye based distribution.

Our Linux desktop is now based on Debian Bookworm XFCE 4.18. The SDK has also been updated to Bookworm. More details at volkspc.org.

Our latest release works well with both of KonstaKang's LineageOS 20 (Android 13) and AOSP 13.