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
Related
kernel, platform, dev-tools, and "extra" source code!
here
to answer the most obvious question:
Jean-Baptiste Queru said:
Here are the GPL source files that match the 4.0 / r14 SDK.
Like we did for all Honeycomb release, this is NOT the full source tree for IceCreamSandwich, these are only the GPL parts that are in the SDK (along with a few associated files), and they're not enough to build the whole IceCreamSandwich for a device.
Click to expand...
Click to collapse
thanks for the link, but the code is useless - no UI libraries, no dalvik to boot JAR's,
no applications... still waiting until google releases the full sources in november
I agree it's mostly useless, but the kernel source at least provides the basic patches needed for the newer version.
the basic patches are for the emulator only.
we need drivers from LG for our hardware, at least a kernel dev like franco can port the drivers to the 3.0
tree, but its a lot of work ... and currently he didnt have a lot of time.
Hello all,
Is there a way to build the native android kernel for your device, to include other linux applications?
I would like to build X11 inside of android and use the existing GUI of android.
I'd also like to be able to compile other linux apps isde android as well.
all the searching I have is about linux inside of a chroot, and that's not what i'm looking for.
since android is build upon linux, then really it should only be a matter of runing a few scripts to call init files and other libraries?
I did see this "Build native GNU/Linux applications: the easy way"
But nothings been done since early 2012.
If I'm going to be compiling an android and its kernel for a device from scratch, then it makes sense to extend the linux to include the functionality to build native linux apps as well, right?
Hello,
I have a question about the best way to manage an Android software project that will involve modifying core Android code.
My question is not a normal "how to do this in Android", but rather, concerns the code management process and the build procedure. Has anyone any experience with this, or can point me somewhere?
We are starting a project to implement an audio application on Android phones, the various ARM architectural flavours. This will involve modifying and extending the C/C++ code in the Media Framework library, plus some supporting Java code. In other words, relative to the complete Android codebase, the amount of code that will be affected is quite small. We will need to support various Android versions and various phone manufacturers and models per manufacturer. Our development process concerns using the pure AOSP as a basis, and initially targeting the Google Nexus as a reference platform. After that, customisations needed for real-world phones will be done in cooperation with the phone manufacturers.
From a code management viewpoint, my idea was to maintain a git repository for our Media Framework files, that will be branched for each maintained version of Android. Separately, we will check out from the Google AOSP repository the code for each supported version of Android, and overlay/merge our Media Framework code onto this codebase. The resulting codebase for each version of Android will be built targeted to the range of Android phones that we support, initially the reference Google Nexus.
Some development approaches that come to mind:
- For each Android version, we could patch Android's Media Framework with our code, and then maintain the entire merged AOSP in a local git repository. This would be a huge undertaking, when branches are included, but would at least guarantee that the codebase is always up to date. Howoever, merging our code changes across difference Android versions would be difficult.
- Another option is to only maintain our Media Framework files in a local git repository, branched for each Android version. Before building a specific Android version,we could checkout the Android version from the Google repository (or keep it cached locally on our build system or on developers' machines) and then patch Android's Media Framework files with our files.
Many thanks,
polomora
WiFi direct has a shell tool for doing configuration changes called "p2p_cli". I can't find a newer version compiled to run on Android 5.0 with the new PIE security requirement.
It seems to be part of the Android platform source code, here: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master/src/p2p
Reference on PIE compile:
http://stackoverflow.com/questions/...id-l-error-only-position-independent-executab
Some ROM developer can maybe compile it for me and provide a download of the binary? Thank you.
Z5C is originally deployed with bluetooth 4.1, however it seems that his chip is capable of an upgrade to 4.2 and maybe even to 5.0.
( idk if it is 5.0 upgradable, here are referring to it as it is:
https://community.infineon.com/t5/W...x/Bluetooth-BCM43455-security-mode/m-p/266305 )
Here I found infos on the BT chip type:
GitHub - seemoo-lab/nexmon: The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more
The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more - GitHub - seemoo-lab/nexmon: The C-based Firmware Patching Framewor...
github.com
Here it is broadcom related infos, with an upgrade in 2019:
https://device.report/broadcom/bcm43455
BT 4.2 introduces some security features and a 10x capacity and 2.5x speed increase for data packets, bt 5.0 increases also the range.Here a quick reference:
Bluetooth - Wikipedia
en.wikipedia.org
Are current mod roms upgraded or there are been tries to do do that?
tagging @Berni-0815 as he the main developer of this handset
For that we need the hardware drivers. Without them it's nearly impossible to upgrade this stuff.
Ok.
Has the hardware driver to be device specific ( ie written for z5c, which I think is impossible to find ) or could be taken from another device's blobs, or even from sources like this one?
Cypress Android 10 Release [2021-01-14]
Framework Version cy-imx-android-10.0.0_2.0.0-6 Kernel Verison Linux localhost 5.4.3-00002-ga85b5953f05b #1 SMP PREEMPT Wed Dec 23 07:58:53 CST 2020 aarch64 FMAC Version v5.4.18-gamera-android-2-0-gde98449dbb46 Release Date 2021.01.22 Description Cypress Android release for the broad market...
community.infineon.com
tagging also @TRKARTAL as searching on github I've seen that in the past has worked to patch this firmware
I for myself have given up to fiddle around with hardware related drivers or patching them.