Database Info

Android NDK r3 and OpenGL ES 2.0!

Android Games WILL be improved thanks to NDK r3 and OpenGL ES 2.0
Developers on the Android platform have already been pushing the boundaries of Android gaming. Even Quake 3 has been seen running on the Android platform. Things can only get better with today’s announcement.
The Android Developers Blog today announced the availability of the NDK r3 that will let android developers directly access OpenGL ES 2.0 features.
Applications targeting Android 2.0 (API level 5) or higher can now directly access OpenGL ES 2.0 features. This brings the ability to control graphics rendering through vertex and fragment shader programs, using the GLSL shading language.
A new trivial sample, named “hello-gl2″, demonstrates how to render a simple triangle using both shader types.
With access to these enhanced OpenGL ES features game graphics should be greatly improved and we should start to see an awesome future for Android gaming. Obviously, we still need developers to take advantage of the new API and have the hardware powerful enough to use it, but everything is getting real close to serious gaming on Android.
Source: Android Developers Blog
Source: AndroidSPIN
-----
What is the Android NDK?
The Android NDK is a toolset that lets you embed components that make use of native code in your Android applications.
Android applications run in the Dalvik virtual machine. The NDK allows you to implement parts of your applications using native-code languages such as C and C++. This can provide benefits to certain classes of applications, in the form of reuse of existing code and in some cases increased speed.
The NDK provides:
* A set of tools and build files used to generate native code libraries from C and C++ sources
* A way to embed the corresponding native libraries into application package files (.apks) that can be deployed on Android devices
* A set of native system headers and libraries that will be supported in all future versions of the Android platform, starting from Android 1.5
* Documentation, samples, and tutorials
This release of the NDK supports the ARMv5TE machine instruction set and provides stable headers for libc (the C library), libm (the Math library), OpenGL ES (3D graphics library), the JNI interface, and other libraries, as listed in the section below.
The NDK will not benefit most applications. As a developer, you will need to balance its benefits against its drawbacks; notably, using native code does not result in an automatic performance increase, but does always increase application complexity. Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't allocate much memory, such as signal processing, physics simulation, and so on. Simply re-coding a method to run in C usually does not result in a large performance increase. The NDK can, however, can be an effective way to reuse a large corpus of existing C/C++ code.
Please note that the NDK does not enable you to develop native-only applications. Android's primary runtime remains the Dalvik virtual machine.
Contents of the NDK
Development tools
The NDK includes a set of cross-toolchains (compilers, linkers, etc..) that can generate native ARM binaries on Linux, OS X, and Windows (with Cygwin) platforms.
It provides a set of system headers for stable native APIs that are guaranteed to be supported in all later releases of the platform:
* libc (C library) headers
* libm (math library) headers
* JNI interface headers
* libz (Zlib compression) headers
* liblog (Android logging) header
* OpenGL ES 1.1 and OpenGL ES 2.0 (3D graphics libraries) headers
* A Minimal set of headers for C++ support
The NDK also provides a build system that lets you work efficiently with your sources, without having to handle the toolchain/platform/CPU/ABI details. You create very short build files to describe which sources to compile and which Android application will use them — the build system compiles the sources and places the shared libraries directly in your application project.
Important: With the exception of the libraries listed above, native system libraries in the Android platform are not stable and may change in future platform versions. Your applications should only make use of the stable native system libraries provided in this NDK.
Documentation
The NDK package includes a set of documentation that describes the capabilities of the NDK and how to use it to create shared libraries for your Android applications. In this release, the documentation is provided only in the downloadable NDK package. You can find the documentation in the <ndk>/docs/ directory. Included are these files:
* INSTALL.TXT — describes how to install the NDK and configure it for your host system
* OVERVIEW.TXT — provides an overview of the NDK capabilities and usage
* ANDROID-MK.TXT — describes the use of the Android.mk file, which defines the native sources you want to compile
* APPLICATION-MK.TXT — describes the use of the Application.mk file, which describes the native sources required by your Android application
* HOWTO.TXT — information about common tasks associated with NDK development.
* SYSTEM-ISSUES.TXT — known issues in the Android system images that you should be aware of, if you are developing using the NDK.
* STABLE-APIS.TXT — a complete list of the stable APIs exposed by headers in the NDK.
* CPU-ARCH-ABIS.TXT — a description of supported CPU architectures and how to target them.
* CHANGES.TXT — a complete list of changes to the NDK across all releases.
Additionally, the package includes detailed information about the "bionic" C library provided with the Android platform that you should be aware of, if you are developing using the NDK. You can find the documentation in the <ndk>/docs/system/libc/ directory:
* OVERVIEW.TXT — provides an overview of the "bionic" C library and the features it offers.
Sample applications
The NDK includes sample Android applications that illustrate how to use native code in your Android applications. For more information, see Using the Sample Applications.
Click to expand...
Click to collapse
You can download the Android NDK: here

just waiting for it ! Good job!

Kind of makes sense now why the binary 3D driver broke from 1.6->2.0

and i most care about whether our G1 are supported ?!

huhaifan1 said:
and i most care about whether our G1 are supported ?!
Click to expand...
Click to collapse
well if the rumors about every single android device being upgraded to 2.1 in the US are true then id think so. we already have partial 3D working, so i think with this release the devs will be able to make it work

Except the chip in the G1 is not built for 2.0.
IMHO, if you'll see 2.0 drivers on the G1 (or Hero) it'll be software. But I'd love to be proven wrong, so please do.

Chainfire said:
Except the chip in the G1 is not built for 2.0.
IMHO, if you'll see 2.0 drivers on the G1 (or Hero) it'll be software. But I'd love to be proven wrong, so please do.
Click to expand...
Click to collapse
from what ive read on androidspin and phandroid, some phones will receive a slimmer 2.1 that doesnt support lwp OTA. some devs have found ways to use software libs and kernel edits to use partial 3D acceleration in some 2.1 roms. Firerat and Case_ managed to get 3D and Youtube HD working on Canon's Roms. The next OpenEclair should have fully working 3D, lwps, and video according to wesgarner, so i think that this upcoming release mentioned in the article will provide more tools for our devs to use on the G1.

but when EXACTLY - like DATE - are they coming!?

chim4ira312 said:
but when EXACTLY - like DATE - are they coming!?
Click to expand...
Click to collapse
The NDK is available now, maybe the devs should look into it:
http://developer.android.com/intl/de/sdk/ndk/index.html
What is the Android NDK?
The Android NDK is a toolset that lets you embed components that make use of native code in your Android applications.
Android applications run in the Dalvik virtual machine. The NDK allows you to implement parts of your applications using native-code languages such as C and C++. This can provide benefits to certain classes of applications, in the form of reuse of existing code and in some cases increased speed.
The NDK provides:
* A set of tools and build files used to generate native code libraries from C and C++ sources
* A way to embed the corresponding native libraries into application package files (.apks) that can be deployed on Android devices
* A set of native system headers and libraries that will be supported in all future versions of the Android platform, starting from Android 1.5
* Documentation, samples, and tutorials
This release of the NDK supports the ARMv5TE machine instruction set and provides stable headers for libc (the C library), libm (the Math library), OpenGL ES (3D graphics library), the JNI interface, and other libraries, as listed in the section below.
The NDK will not benefit most applications. As a developer, you will need to balance its benefits against its drawbacks; notably, using native code does not result in an automatic performance increase, but does always increase application complexity. Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't allocate much memory, such as signal processing, physics simulation, and so on. Simply re-coding a method to run in C usually does not result in a large performance increase. The NDK can, however, can be an effective way to reuse a large corpus of existing C/C++ code.
Please note that the NDK does not enable you to develop native-only applications. Android's primary runtime remains the Dalvik virtual machine.
Contents of the NDK
Development tools
The NDK includes a set of cross-toolchains (compilers, linkers, etc..) that can generate native ARM binaries on Linux, OS X, and Windows (with Cygwin) platforms.
It provides a set of system headers for stable native APIs that are guaranteed to be supported in all later releases of the platform:
* libc (C library) headers
* libm (math library) headers
* JNI interface headers
* libz (Zlib compression) headers
* liblog (Android logging) header
* OpenGL ES 1.1 and OpenGL ES 2.0 (3D graphics libraries) headers
* A Minimal set of headers for C++ support
The NDK also provides a build system that lets you work efficiently with your sources, without having to handle the toolchain/platform/CPU/ABI details. You create very short build files to describe which sources to compile and which Android application will use them — the build system compiles the sources and places the shared libraries directly in your application project.
Important: With the exception of the libraries listed above, native system libraries in the Android platform are not stable and may change in future platform versions. Your applications should only make use of the stable native system libraries provided in this NDK.
Documentation
The NDK package includes a set of documentation that describes the capabilities of the NDK and how to use it to create shared libraries for your Android applications. In this release, the documentation is provided only in the downloadable NDK package. You can find the documentation in the <ndk>/docs/ directory. Included are these files:
* INSTALL.TXT — describes how to install the NDK and configure it for your host system
* OVERVIEW.TXT — provides an overview of the NDK capabilities and usage
* ANDROID-MK.TXT — describes the use of the Android.mk file, which defines the native sources you want to compile
* APPLICATION-MK.TXT — describes the use of the Application.mk file, which describes the native sources required by your Android application
* HOWTO.TXT — information about common tasks associated with NDK development.
* SYSTEM-ISSUES.TXT — known issues in the Android system images that you should be aware of, if you are developing using the NDK.
* STABLE-APIS.TXT — a complete list of the stable APIs exposed by headers in the NDK.
* CPU-ARCH-ABIS.TXT — a description of supported CPU architectures and how to target them.
* CHANGES.TXT — a complete list of changes to the NDK across all releases.
Additionally, the package includes detailed information about the "bionic" C library provided with the Android platform that you should be aware of, if you are developing using the NDK. You can find the documentation in the <ndk>/docs/system/libc/ directory:
* OVERVIEW.TXT — provides an overview of the "bionic" C library and the features it offers.
Sample applications
The NDK includes sample Android applications that illustrate how to use native code in your Android applications. For more information, see Using the Sample Applications.
Click to expand...
Click to collapse

This doesn't at all in any way say that we're getting 2.0 drivers for the G1. All it's saying is that phones with 2.0 will be able to directly access ES2.0 functions.
Which, really, has absolutely nothing to do with the driver issue we face. Unless you can point out something I missed.

Gary13579 said:
This doesn't at all in any way say that we're getting 2.0 drivers for the G1. All it's saying is that phones with 2.0 will be able to directly access ES2.0 functions.
Which, really, has absolutely nothing to do with the driver issue we face. Unless you can point out something I missed.
Click to expand...
Click to collapse
sorry i probably misunderstood the article =/
im still not very experienced with android development, i thought this would help the devs a little bit with getting 3d working (since theyre already doing that without official drivers)

I did indeed get a humongous boner on reading this earlier. It was enhanced by 3D.
My favorite part about this is the new ability to use openGL in apps! That means the entire face of our OS is going to change.
...and speaking of OS... Qualcom/htc just released a new radio for the G1. The G1 To this day holds over 50% of the android installed user base. There is no doubt the G1 will live beyond 1.X

bleah writing games in opengl es 1.0 was hard enough...

Gary13579 said:
This doesn't at all in any way say that we're getting 2.0 drivers for the G1. All it's saying is that phones with 2.0 will be able to directly access ES2.0 functions.
Which, really, has absolutely nothing to do with the driver issue we face. Unless you can point out something I missed.
Click to expand...
Click to collapse
agreed
the binary still needs to be available
as far as I can see with have two
the open source one
/system/lib/egl/libGLES_android.so
and the proprietary
/system/lib/egl/libGLES_qcom.so
the quoted text in the OP is basically stating that an Android developer will now be able to mix in a little c/c++ to get direct native access to opengl es
functions

Firerat said:
agreed
the binary still needs to be available
as far as I can see with have two
the open source one
/system/lib/egl/libGLES_android.so
and the proprietary
/system/lib/egl/libGLES_qcom.so
the quoted text in the OP is basically stating that an Android developer will now be able to mix in a little c/c++ to get direct native access to opengl es
functions
Click to expand...
Click to collapse
sorry guys like i said i misunderstood =/ i was hoping the NDK would provide some help but i now see its pretty much for apps, facepalm >_<;
edited the title to avoid further confusion lol

speedysilwady said:
edited the title to avoid further confusion lol
Click to expand...
Click to collapse
Was just about to do that, thanks .
I'm sure we'll get drivers eventually, either hacked or official. Just a matter of time.

Gary13579 said:
Was just about to do that, thanks .
I'm sure we'll get drivers eventually, either hacked or official. Just a matter of time.
Click to expand...
Click to collapse
haha no problem, glad to see i have a moderator type mentality. lol
yeah im sure we will, theyre already partially working, so its only a matter of time hopefully

What Chainfire said is that there is no hardware support for OpenGl ES 2.0 in msm720x chips. (refs here, sorry couldn't find official spec datasheet).
So even if 2.0 is supported, it will only be through software drivers implementation, which means really slow rendering.

spocky12 said:
What Chainfire said is that there is no hardware support for OpenGl ES 2.0 in msm720x chips. (refs here, sorry couldn't find official spec datasheet).
So even if 2.0 is supported, it will only be through software drivers implementation, which means really slow rendering.
Click to expand...
Click to collapse
Thats right.
But most Games will probably/hopefully still be written for OpenGL1.1. (Because of the userbase whatsoever)

For a start, but to focus at the future, too bad, the G1 will get old sooner

On board android development

Im a fairly knowledgeable computer user without a computer!
I love to write programs!
It really is a shame that there is not an onboard development kit for this platform.
I have tried several implementations available in the market. None of them seem to satisfy my thirst.
Before I gave up on sl 4 a, I learned a little about android virtual machine. When coupled with the right tools, and knowledge, full access to the android java api are possible.
Being that I don't have a computer, I cannot compile any wrappers to handle superclassing the api. As you may know a simple hello world gui will not run on android without a superclass.
It is not my aim to go for full fledged on board development. The overhead is way too high. Ie battery power, syntactical semantics storage space for libraries yada yada yada...
Mozilla has the rhino javascript engine which can execute code within the android virtual machine. However as I said before super classing presents a very serious problem.
I aim to write a bridge in java and javascript. However I have no tools to do the java side work.
I do have access to a shell account with a working j d k, but the j d k is not fully compatible with the android sdk. On top of that I'm faced with the 50 megabytes quota offered with my free shell account. The android sdk is 2.5 gigabytes in size approximately.
To sum it all up there are a few files that I need from the android sdk that will allow me to compile java programs using my free shell, and then convert them for usage on the android virtual machine.
The files in question are as follows:
aapt - weird android packaging mechanism
dx - android virtual machine byte code converter.
From my research I have learned that dx is actually a java program that runs in the standard java implementation.
Well whatever the case is I need these programs running on an Ix86 Unix bsd architecture if anyone out there can supply them pre assembled.
This is not an official request for comments but all comments are appreciated.
Sent from my HTC Magic using Tapatalk

This is how I run my scripts from the shell.
Rhino came to me from sl4a. Sl4a project is unsuccessful @ functional implementation of rhino JavaScript for android at time of this writing.
For whatever purpose sl4a does not execute the dalvik command properly ($BOOTCLASSPATH is being pushed out of context via Rhino or the dalvikvm onLoad) so even though you can install the JavaScript interpreter from sl4a you can't use it without some fancy footwork.
I had to change permissions on my dalvik cache folders as well to get it working on my droid. For some reason the system did not want to accept the rhino library into its dex cache (using cyanogen mod. 6). Just do rwx permissions for everyone on
/data/cache
and
/system/cache
Note that the above file systems are usually mounted read only.
Note also that this is a single line shell command. put it in an sl4a shell script or run it from the terminal.
/system/bin/dalvikvm -Xbootclasspath:/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/mnt/sdcard/com.googlecode.rhinoforandroid/extras/rhino/rhino1_7R2-dex.jar -Xss128k org.mozilla.javascript.tools.shell.Main -O -1
Running this command in the terminal will activate a javascript interpreter shell that has full access to the android java framework.
If you would like to run a script instead of an interactive shell please append the following to the preceding command
-f /path/to/your/script/yourscriptName.js
That line would make an interesting argument to your new shell script!
For more information about Rhino see my next post for suggestions and resources.
if you are interested in this project now is a very good time to learn java programming! I just started yesterday and I haven't been to sleep yet! lol. it is also considered a requirement to learn the android java api if you plan to capitalize on its functionality.
Aye.. time for more coffee ..
- Posted via mobile

SL4A - http://code.google.com/p/android-scripting/
Android API - http://developer.android.com/reference/packages.html
Rhino API - http://www.mozilla.org/rhino/apidocs/index-all.html
Rhino Documentation - http://www.mozilla.org/rhino/doc.html
Suggested Reading
JavaScript The Definitive Guide: 5th
Edition
some books on Java ... classes,
interfaces, overrides, packages,
sub classing, super classing,
inheritance, extends, import
// its pretty much like jascript without
// all that stuff
some books on Android Programming
- Posted via mobile

Avid Droidery said:
To sum it all up there are a few files that I need from the android sdk that will allow me to compile java programs using my free shell, and then convert them for usage on the android virtual machine.
The files in question are as follows:
aapt - weird android packaging mechanism
dx - android virtual machine byte code converter.
Click to expand...
Click to collapse
So no one out there develops for android under linux?
I downloaded the source tree for the davlik virtual machine but there is no make file to compile the project! Tell me that is not aggravating!
The web quotes a file "envsetup.sh" and a command called "lunch" to be run in a 'build' directory. None of these files were supplied with the download. Practices in idiocy should be banned from the web! Lol.
So let's say I used 'git' to grab the source tree of a single project in the android sdk. How am I supposed to build a project with no make file???
The normal way to do this... is to run the gui setup called 'android.' that does me no good. I only have ssh access to my build server!
Is there no 1 out there who can build these files for linux and supply them to me? From what I understand all you need to do is successfully install and configure the sdk and these files will b available to you in the tools directory.
I would like to file an issue about having no text based setup for the android sdk. In the real world we may not always be able to use a graphical user interface. especially under linux/unix/posix! But what good would that do me? I needed these files 3 days ago
*update issue filed under general build questions google groups (PC WIZ)
So let's recap.. if you are using the android sdk under linux or if you have physical access to a unix machine and some spare time I could really use your help!!!!
I would like to make this topic become a reality soon.
- Posted via mobile (as always)

Ok I got dx up and running.
I found where to get the files prebuilt.
http://android.git.kernel.org/?p=pl...11c17b4f5507f00905ec73f2fb90eaa387f72;hb=HEAD
Yes in platform/prebuilt .. @ the android source code repository.
I also downloaded aapt but the library files are not available on my system for this build. I don't have the rights to upgrade my development server. Stay tuned.
Here is stderr output from './aapt':
./aapt: /usr/lib/libz.so.1: no version information available (required by ./aapt)
./aapt: /lib/tls/i686/cmov/libc.so.6: version `GLIBC_2.4' not found (required by ./aapt)
If you are thinking of downloading any files from the source code repository using your android device you will be very disappointed! wget fails to download the raw views of the files and reports them as garbage. The built in download manager just keeps tellin me download unsuccessful. In short it took me the better part of 3 hours to get 3 files using 3 different downloaders.
I was unable to download the shell script 'dx' nor was I able to cut copy paste the full source because android would not let me everything it did let me copy had line terminators removed. Somebody needs to fix that clipboard!! Tell me that's not aggravating!
In retrospect the browser should not say 'select text' as a menu option. It should say 'select some of this text, mangle it and then send it to the clipboard' lol.
Anonymous ftp access should be an open source requirement! I blame today's shortcomings on all open source licenses! Lmfao.
- Posted via mobile

Anyone out there care to donate a 19th/Early 20th century laptop?
I am starting to think like a rhino. I can tell because I'm ready to run my head through the wall! @ aggravating factors.
I am beginning to believe that the android platform is cursed! Lol.
The android devices are awesome! I don't really mean to offend anyone but the software is ****. The source code tree doesn't even resemble a tree.
No offense to Linus Torvalds But you shoulda stuck to hardware programming. I would like to show you a picture of what a git managed project looks like to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know anything technical about it but I think you missed a paper or two on derivative theory. I dont know calculus but everyone knows that a seed from a tree makes a new tree. In retrospect, common sense is pure logic dressed up by the mind as a perception of reality.
My perception of your project and the issue of fault may be wrong but this monstrosity is hosted on your site (android.git.kernel.org)
Please don't get me wrong sir linux is the best damn thing running and everyone involved in its development owes that to you.
I really wish the android platform would have stuck with the tried and true GNU development system. Where source code (seeds) can be downloaded as a seperate package and module dependencies (earth, water, sun, etc..) are easily solved.
I predict this platform will fail within the next 10 years because of this build system. It is quite simply too complicated for new programmers to get on board with fresh ideas. Not to mention the amount of prior knowledge and lofty resources it requires to do so. This is a systemic issue. The flow of integration and information is invaluable to software development. I'm here to tell you the **** doesn't flow.
If anyone dares to challenge these points of authority, might you consider telling me why an open source platform with open source software does not have a bona fide linux distribution like Gentoo, damn small linux, or micro linux? I assure you it is not because no one would use it.
- Posted via mobile

Here is a great program if your'e interested in this script business.
http://code.google.com/p/android-scripting/downloads/detail?name=textedit-sl4a.apk&can=2&q=
Let's face it when it comes to the android appearing to multitask things properly it's all about the app! The dialogs are weak but the functionality is perfect. Happy scripting!
- Posted via mobile

Avid Droidery said:
Here is a great program if your'e interested in this script business.
http://code.google.com/p/android-scripting/downloads/detail?name=textedit-sl4a.apk&can=2&q=
Let's face it when it comes to the android appearing to multitask things properly it's all about the app! The dialogs are weak but the functionality is perfect. Happy scripting!
- Posted via mobile
Click to expand...
Click to collapse
Thx ill check it out
Sent from my HTC Knight using telepathy

JKILO said:
Sent from my HTC Knight using telepathy
Click to expand...
Click to collapse
That is even funnier than the guy I saw run into a car on his bicycle today! Luckily for everyone involved he wasn't hurt. Not so sure about his phone though.
You are welcome.
- Posted via mobile

Update. This project is on pause until further notice. I have been thwarted at every attempt to succeed in this endeavor therefore is my understanding that I must retool and upgrade my resources before I am able to provide a definite solution.
Feel free to ask any questions regarding my current research.
Standing by ...
- Posted via mobile

I managed to wrestle my old workstation out of storage.
Some stats
Pentium D 975 Dual Core 3.0 GHz. EM64T
4GB Ram
175 GB HITACHI SATA Gen II HD on Intel RAID Controller
FOXCONN 975X7AB MOBO
I built it back in '07 but she still runs like a champ!
Anyway just wanted to gloat a little... If you were stuck working on an android you might be as happy about your situation! Heck, I'd be happier with a knock off Chinese netbook running Windows CE 5.0. @ 255 MHz.
I predict this platform will fail within the next 10 years because of this build system. It is quite simply too complicated for new programmers to get on board with fresh ideas. Not to mention the amount of prior knowledge and lofty resources it requires to do so. This is a systemic issue. The flow of integration and information is invaluable to software development. I'm here to tell you the **** doesn't flow.
Click to expand...
Click to collapse
So what does flow? It isn't the Android API! Let's compare some code on the topic of User Interface Design and Implementation.
An application with a single button the android way:
Code:
public class MyActivity extends Activity {
protected void onCreate(Bundle icicle) {
super.onCreate(icicle);
setContentView(R.layout.content_layout_id);
final Button button = (Button) findViewById(R.id.button_id);
button.setOnClickListener(new View.OnClickListener() {
public void onClick(View v) {
// Perform action on click
}
});
}
}
Oh wait a second were not done yet! The following code belongs in a separate file:
Code:
// .... some of this document was removed to improve clarity.
<Button
android:id="button_id"
android:layout_height="wrap_content"
android:layout_width="wrap_content"
android:text="@string/self_destruct"
android:onClick="selfDestruct" />
Seriously all that for one f*%#&n button? It doesn't even do anything when you push it..
Ok that's uh... hmm interesting to say the least. :barf:
Let's look at the same thing in HTML+JS:
Code:
<FORM>
<INPUT TYPE="button" NAME="button" Value="Push Me" onClick="alert('I am not a killer, but don't push me!');">
</FORM>
Simpleton you say? Try this on for size:
Code:
;---------- [Create the Button Control] ----------
INVOKE CreateWindowEx, 0, addr ButtonClass, addr szButText,\
WS_CHILD or WS_VISIBLE or BS_PUSHBUTTON or BS_ICON or \
BS_LEFT or BS_VCENTER or BS_TEXT,\
100, 50, 100, 40, hWnd, 702, hInstance, 0
mov hButCtrl, eax
;---------- [Load the Image] ----------
invoke LoadIcon, hInstance, 901
mov hImage, eax
invoke SendMessage, hButCtrl, BM_SETIMAGE, IMAGE_ICON, hImage
The code above is actually just a snippet from a source file for a 32-Bit Program for Windows written in assembler. But the concept is the same. There is no code here for a click action. To make the example more interesting, this button has an icon drawn onto it.
Sure, I could provide more examples in different languages, but I believe my point is clear here.
Am I the only person here who realizes somebody screwed up when they thought of the API for this platform? I don't understand the reasoning behind this. The programmer spends more time implementing than creating under this platform. When I look at the more complicated apps that are available in the market I have to say well done! But I also have to say "I am sorry about your losses."
Honestly I don't know what to say other than "I wish I was head of R&D for Google over in Mountain View Ca." These guys obviously have no idea what they are doing.
Point and case made by example.
Who wants to collab. with me on an all HTML based GUI framework for the android? Honestly I would love to. Google says this platform is all about code reuse... Hmm... how come there is no /usr/lib directory? You can use their platform to make libraries! but they are for private use only unless you write a 12 chapter book (in code) explaining to the android what people can do with it. Of course then you have to write a real 12 chapter book for the developers on how to use the API you exposed. :barf: :barf: :barf:
Anyway to make matters worse... It is actually easier to program their platform using javascript, but in my honest opinion... It isn't worth the [bad language] trouble... Here's another code excerpt for android in JavaScript:
Code:
// a plethora of code removed to improve clarity....
var buttonRun = new Button(Activity);
buttonRun.setLayoutParams(new LayoutParams(
LayoutParams.FILL_PARENT, LayoutParams.FILL_PARENT, 1));
buttonRun.setText(Droid.translate("RUN"));
buttonRun.setOnClickListener(function () {
// code to do some stuff here
});
// even more code removed to improve clarity...
If you are used to reading my posts you will have to excuse my malformed paragraphing. I am used to composing all my posts by voice recognition
So what does all this mean? In regard to the thread topic, this means that you have your work cut out for you. Just look at the JavaScript code above and see how ridiculously close it is to writing a program that must be compiled. Mind you that is only the code to create ONE button. Looking back even further, it was easier in ASSEMBLER.
Ok, Android Scripting. Its more than a great Idea... It's the best Idea anyone ever created for this platform. Its too bad that an entire platform API has to be written nearly from scratch before we can take full use of it. Well, I am working on an implementation of rhino. Everything compiles smoothly from eclipse but I can't really test anything or come up with any ideas because I know I'm headed down the wrong path.
Well I brought you here for your interest so let me boost your interest.
You want GUI programming in script? Visit the following link and click on:
http://droidscript.blogspot.com/2010/03/droidscript-getting-started.html
I wonder why that project 'died' in its infancy He certainly accomplished quite a bit!
LOL I was right about this platform before I ever opened the IDE! LOL

One more point of interest...
Assembler is the fastest (and most powerful) programming language on the planet. I never thought I would live to see the day that I would find another language (other than C++) that was harder to program with. I was wrong. And I will be wrong about this platform coming to a failure if google pulls its head out of its ass (and gives me or my ideas a job.) LOL.
Note to google devs: Keep It Simple Stupid. HTML5 Based Interface is the only way to go. Especially for a device with limited capabilities. The code is already out there and implemented. It only needs to be adapted. Seriously, throw backwards compatibility out the window and work with something that has the roots, credibility, and global support to be worthy of said term.
Anybody who wants to run that bull**** will have to settle for an 'OnBoard Legacy Code Emulator.' Personally I don't have the time to be bothered with your crypto-pseudo-bloatware and neither does my microprocessor. And just in case you are wondering, I am usually the person who has to say: "I told you so."

I have always thought of it to be like you have revealed it to us... Snap, this just means the end of my Android programmer life... so long Androooiid, so long Google !

Re: onboard android programming
I use JavaIDEdroid program with DroidDevelop for compile my android programs on my android device.
I can't paste links here, but you can find its on the market.
They use eclipse Java compiler and some another utilities to provide ability to create correctly working apk files at output.

wow. this is the only posting mentioning DroidDevelop.

[SOURCECODE] Galaxy Fit S5670 GB SOUCECODE

HEllo people,
For people who have been looking for the source code of this phone recently,but are unable to download it due to the registration process at opensource.samsung.com, I am mirroring the source code! Download and Enjoy!
Source Code (127.18 MB)

PLEASE NOTE->
I will not be responsible for any bricking of the device while modification and/or addition of values to the Source Code or the Kernel.

What is Source Code?
In computer science, source code is text written using the format and syntax of the programming language that it is being written in. Such a language is specially designed to facilitate the work of computer programmers, who specify the actions to be performed by a computer mostly by writing source code, which can then be automatically translated to binary machine code that the computer can directly read and execute. An interpreter translates to machine code and executes it on the fly, while a compiler only translates to machine code that it stores as executable files; these can then be executed as a separate step.
Most computer applications are distributed in a form that includes executable files, but not their source code, which is useful to a user, programmer, or system administrator who wishes to modify the program or understand how it works.
The source code which constitutes a program is usually held in one or more text files stored on a computer's hard disk; usually these files are carefully arranged into a directory tree, known as a source tree. Source code can also be stored in a database (as is common for stored procedures) or elsewhere.
Source code also appears in books and other media; often in the form of small code snippets, but occasionally complete code bases; a well-known case is the source code of PGP.
The notion of source code may also be taken more broadly, to include machine code and notations in graphical languages, neither of which are textual in nature. An example from an article presented on the annual IEEE conference on Source Code Analysis and Manipulation:[1]
For the purpose of clarity ‘source code’ is taken to mean any fully executable description of a software system. It is therefore so construed as to include machine code, very high level languages and executable graphical representations of systems.[2]
The code base of a programming project is the larger collection of all the source code of all the computer programs which make up the project.
It has become common practice to maintain code bases in version control systems.

-> The Kernel and Source code is as seen on Samsung's website
-> Uploaded here in order to avoid regestration process on the website
-> Do NOT download this if you are not sure of what it is or how to edit these
-> Also, Do download if:
-You are planning to develop a kernel
-For Stable CM7 or Future releases
-You are studying the Code
- Bug fixing
- You are learning Kernel dev.
- You belong to the Kernel DEV. TEam of Fit!
------------------------------
CLICK ON TEH THANKS BUTTON, IT DOES NOT EXPLODE!!!

Can I change kernel is Windows or what?

No kernel developing is not supported in windows you need linux you need linux or mac os

omarhasan76 said:
No kernel developing is not supported in windows you need linux you need linux or mac os
Click to expand...
Click to collapse
VMWare or Virtual PC does the job.

Yes, Yes it does! You dont need to install Linux!

ya but its the same thing installing linux or using virtual machine

omarhasan76 said:
ya but its the same thing installing linux or using virtual machine
Click to expand...
Click to collapse
I meant the same.....

Which version/baseband ?

hey this source code is for galaxy ace gt s5830
i guess and not for fit ??

[TOOL][ALL] Assimilation 1.0

Description
Assimilation is a multi-call shell script, designed to manage Arch Linux chroots.
Open Source
Assimilation is open source and licensed under the Apache License 2.0. You can check out the source code at GitHub.
A More Descriptive Description
Assimilation is a shell script I wrote back in the summer of 2013. Since then I've turned it from an overnight project into an open source project on GitHub.
I've always hated using chroots on my Android device, until I wrote Assimilation that is.
Assimilation will automatically detect your CPU architecture (currently it supports ARMv5 - ARMv8, i686, and x86_64), download the corresponding Arch Linux image and extract it. From there it can automatically mount necessary resources and enter a chroot for you. Once you exit the chroot, it can automatically clean up all mounts for you.
Assimilation runs nicely on my Android smartphone and tablet, as well as my HP Chromebook 11.
What Can I Use Assimilation For?
Glad you asked!
Firstly, Assimilation is not for the faint of heart! You must have access to a Terminal and have root access.
I use Assimilation for a number of things...
- I've turned an old Galaxy S into a personal file server that runs surprisingly fast (will write a guide for this soon).
- I also use Assimilation to use programs like Git on my Chromebook.
If you encounter any problems using Assimilation, please use GitHub's Issue tool to bring it to my attention.
If you like Assimilation (or my other app, Epoch Launcher), please follow me on twitter @mirasmithy

Reserved!

AutoSploit

This could be very good. I didn't read too much though.
AutoSploit is slightly more sophisticated but only because it leverages two popular, well-supported security tools. "As the name might suggest," its author wrote on the tool's GitHub page, "AutoSploit attempts to automate the exploitation of remote hosts." To do that, the Python script uses command line interfaces and text files to extract data from the Shodan database, which is a search engine that taps into scan data on millions of Internet-connected systems. AutoSploit then runs shell commands to execute the Metasploit penetration testing framework.

The link didn't work.
This one did:
https://arstechnica.com/information...ool-sparks-fears-of-empowered-script-kiddies/
Not useful for tablet exploitation.
Sent from my iPhone using Tapatalk