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?

[SCRIPT][NDK] agcc wrapper mod for latest Android NDK

Here is an update to 'agcc' wrapper originally written by Andrew Ross. You can find his original version here.
Modded/Updated agcc
Helps you to quickly compile native C code for ARM, MIPS or x86 targets. I updated 'agcc' to try out a few existing exploits on Android, in hope of finding a few more to open up root for my new phone.
I thought some of you may find this updated script useful for compiling native code. I have tested these changes only on a Windows machine using Android NDK r8b.

Reserved
[RESERVED]

guidance needed on compiling an existing android code

Hi,
Sorry for the basic question here. I just want to compile and build an apk from an android open source project; but i don't know how to !!
I'm on ubuntu 13.10. I have downloaded the Android ADT bundle from developer android com /sdk/ index.html
I've run eclipse (from ADT bundle) and have imported a downloaded version of the open source project.
The open source project is Prey github com / prey / prey-android-client
The project is setup in eclipse but i see red flags and doesn't run (because it doesn't know how to run).
Can you guys point me to a guide or tell me how to compile & build an apk out of this.
Unfortunately the README file in the repository is useless (i.e. blank!)
Thanks.

shanehelms said:
Hi,
Sorry for the basic question here. I just want to compile and build an apk from an android open source project; but i don't know how to !!
I'm on ubuntu 13.10. I have downloaded the Android ADT bundle from developer android com /sdk/ index.html
I've run eclipse (from ADT bundle) and have imported a downloaded version of the open source project.
The open source project is Prey github com / prey / prey-android-client
The project is setup in eclipse but i see red flags and doesn't run (because it doesn't know how to run).
Can you guys point me to a guide or tell me how to compile & build an apk out of this.
Unfortunately the README file in the repository is useless (i.e. blank!)
Thanks.
Click to expand...
Click to collapse
I would say you should go though the getting started guides on d.android.com and things will become a little more clear

[ROM][Flo][4.4.2] Tablet UI Building Kit

Introduction
SlateKit project (slatekit.org) is a drop-in replacement of Android UI stack,
to help makers building custom tablet UI by using Qt/QML, JavaScript and Chromium.
This means you don't need to flash your device, just drop the file, execute the script, then it's done.
Today we announce the first technical preview of SlateKit Base for Nexus 7 (2013),
the platform-specific port, alone with other UI components like Browser, LockScreen and Keyboard.
Prerequisite
Nexus 7 “razor” [2013] (WiFi)
Android 4.4.2 (KOT49H)
rooted and adb shell access
Installation
Download the image: goo.gl/ybYVO1 (146.7 MB)
Unzip files to /data, make sure busybox has executable permission
Start the UI by:
Code:
./chroot.sh
Technical details
a minimal Ubuntu root filesystem (Trusty/armhf)
Qt 5.2.1 and Oxide 1.0 (Chromium content API wrapper)
libhybris for hardware acceleration
hwcomposer QPA from Mer project
What's next?
Theoretically this rootfs works for all Android 4.4 system with HW composer 1.1/1.2,
so I'll try to enable it on other SoCs and make an installer.
If you find this interesting or useful, welcome to join the project:
blog: penkia.blogspot.com
source: github.com/penk/SlateKit
twitter: penk
email: [email protected]
Happy Hacking!
penk

How about deb version?
Sent from my Nexus 7 using Tapatalk

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.