Pages

Subscribe:

Ads 468x60px

Labels

Monday, 22 October 2012

ROEHSOFT RAM-EXPANDER (SWAP) v1.73 Apk



 RAM_EXPANDER Virt. Memory expansion up to 4.0 GB. Swapfile manager with Top Speed!
Please check your Device with ‘MemoryInfo & Swapfile Check’
before you buy!
Up to 4.0 GB of memory per click! Android 1.6 – 4.1 with root access and external SD CARD! More memory means, the background service can not be stopped, and many programs will work correctly in the first place!
Languages: German and English
- use free external SD card as RAM memory (RAM SWAP / SWAP MEMORY)
- RAM expansion up to 4 GB swapfile
- The usual performance losses occur when swap sd cards not from class-8
- Widget for PNP swap (swap on / swap off)
- Detailed information storage and analysis
- Autostart function
- Swappiness kernel parameter set
- Use simple child’s play
(1 click optimization and automatic calculation)
- Support of all Android devices with Tung (root access and support Kernelswap)
Note: please try before you buy with our app “https://play.google.com/store/apps/details?id=com.roehsoft.meminfo” whether their device ROEHSOFT RAM Expander is compatible, thank you!
Should there still be problems, please contact me before they write such requests to the Review forum!
too little memory? equal no more! More games to play and run more applications at once! Moreover, you need only increase your memory. Lasting up to 4.0 GB! Memory increase, rather than using Task Killer or memory optimizer.
ROEHSOFT Ram Expander is more effective than any other tool of its kind Why? The First find out!
ROEHSOFT RAM expander widget support via the lightning-quick on and off of extended memory.
Dadruch can remove the SD card despite swapfile or provide via USB.
Also, you can raise important that control basic kernel parameters for the swapping itself to the effectiveness of extended memory.
In order to obtain root access you may continue to help this Linkk http://shortfuse.org/.
Particularly favorable entry phones often have little RAM, either here TaskKiller programs help further or you use a swapfile, which is sufficient memory available. ROEHSOFT Expander makes your device more easily. Many applications can now run simultaneously, and do not have to worry about your RAM.
Extended every Android device up to 4 GB of RAM, where it creates a swapfile on the SDCARD.
Maximum size of the swap file is architecture requires 4GB!
By setting the value of swappiness you can control the behavior of the kernel, the greater the value the more is being outsourced.
Please note! For damages that may result from the use of this software does not accept liability!

C Compiler For Android



Programmers this is an wonder full app who are using android, this Gives you a clean environment of C and 







c++   C4droid is a simple C/C++ IDE + C/C++ compiler for Android with Makefile support.
C4droid already has almost full C language support, so you don’t need to wait when it will be added.
You can to write your own applications on Android phone, and run them. This app uses TCC and uClibc, so it has full support of ANSI C and some support of ISO C99. C4droid can be used for educational purposes or to practice in C language.
Some components of C4droid are LGPL-licensed. You can download used source code of TCC and uClibc on their websites (But TCC had been modified by me, so I recommend to email me to get modified source).
C4droid includes Android Terminal Emulator so you can to run your application comfortably.
To get C++ support you need:
1) Install GCC plugin (C4droid will ask you to install it).
2) Select G++ compiler in C4droid preferences.
3*) Use iostream, not iostream.h
4*) Add “using namespace std;” to your program (before int main)
To compile Makefile projects, open any file in the same folder with Makefile and long-click “Compile” to configure current directory (C4droid will create .c4droid configuration file when you’ll press Ok). After configuring folder, you can press compile button and C4droid will build your project.
Don’t forget to enter executable name and select compilation mode (and press ok also, else changes will be discarded)
C4droid supports SDL, NativeActivity and Qt for GUI now, install SDL plugin for C4droid to use it (only GCC/G++ compiler is supported, so you need GCC plugin).
(SDL is detected with #include “SDL.h”, NativeActivity is detected with #include “android_native_app_glue.h”, Qt is detected with #include “QtGui”).
There is an experimental support for Qt using necessitas, but note that it’s in alpha stage.
Qt support limitations:
1) Path to Ministro libraries is hardcoded (/data/data/org.kde.necessitas.ministro/files/qt/lib), so email me if it will change.
2) Only QtCore and QtGui libraries are supported by C4droid for now.
3) If you’re compiling a single-file Qt app, you must add #include “yoursourcefilenamewithcpp.moc” to the end of file. If you’re using .pro file for compilation, you don’t need to do that.
Quick manual:
If you have found a bug or app is not working, email me.
If app crashes on start, reboot your device, it’s a Google Play/Android bug.
Long click save button to “save as”, long click run to run with arguments.
Result of compilation (binary) is placed in “/data/data/com.n0n3m4.droidc/files/temp”, because sdcard doesn’t have permission for execution by default.
If you have “Illegal instruction” error, using internal compiler (TCC), install GCC plugin, GCC supports softfloat (by default).

Saturday, 20 October 2012

Android Solar Charger



An app on Google Play is proving to the world that the vast majority of Android users fail to read the description of an app before downloading it.
The Solar Charger app for Android claims that it can charge your phone just by leaving its screen out in the sun. If that sounds too good to be true, that's because it is! However, the app has already been downloaded between 1 and 5 million times (!), so clearly some people are falling for the joke. According to the app developer, that's the whole point: people need to read the description of their apps. If they don't, it's their loss.
The description of the Solar Charger app begins innocently enough: "Go green! Charge your phone with the power of the sun! Start this application, put your phone in a well lit place and watch your battery charge using the solar panel."
Sounds promising enough, right? But as the description continues, it should become even more obvious to the common person that this app is an epic joke:





Tuesday, 18 September 2012

Android Button Example


1. Add Button

Open “res/layout/main.xml” file, add a button.
File : res/layout/main.xml
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    android:orientation="vertical" >
 
    <Button
        android:id="@+id/button1"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Button - Go to mkyong.com" />
 
</LinearLayout>

2. Code Code
Attach a click listener to the button.
When user click on it, open mobile browser and display URL : http://www.mkyong.com.
File : MyAndroidAppActivity.java
package com.mkyong.android;
 
import android.app.Activity;
import android.content.Intent;
import android.net.Uri;
import android.os.Bundle;
import android.widget.Button;
import android.view.View;
import android.view.View.OnClickListener;
 
public class MyAndroidAppActivity extends Activity {
 
 Button button;
 
 @Override
 public void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  setContentView(R.layout.main);
 
  addListenerOnButton();
 
 }
 
 public void addListenerOnButton() {
 
  button = (Button) findViewById(R.id.button1);
 
  button.setOnClickListener(new OnClickListener() {
 
   @Override
   public void onClick(View arg0) {
 
     Intent browserIntent = 
                            new Intent(Intent.ACTION_VIEW, Uri.parse("http://elektroidapps.blogspot.in"));
       startActivity(browserIntent);
 
   }
 
  });
 
 }
 
}

3. Demo

Run the application.

Source Code Download Here 


Saturday, 11 August 2012

Install Android SDK, Eclipse, and Emulator (AVDs) (Tutorial -1)


Android is a large and fast-growing segment of the mobile phone market. With potentially 350,000 users activating a new Android phone every day and multiple Android App Stores popping up (Google’s Android Market was recently revamped, and now other markets are coming online, like Amazon’s Android App Store), now is a great time to jump into Android development.
This walk-through will get you started installing the Android Software Development Kit (Android SDK), installing and configuring the Eclipse IDE for Android development, and choosing and installing Android Virtual Devices (AVDs) to emulate the Android environment right on your local computer. After following these steps, you will be ready to create your first Android application!
1. Download the Android Software Development Kit (SDK)
The very first step is to download the Android Software Development Kit (SDK) that will let you emulate Android on your local computer. It is not too large (only ~30MB, compared to the monolithic XCode/iPhone SDK, which is almost 4GB!).
From the Android SDK Download Page, make sure to choose the version that is correct for your operating system.
After your Android SDK download is complete, unzip and move the new folder to a permanent location (*not* your downloads directory). I use a folder in my home directory (~/Android/android-sdk-mac_x86/) but you can move it anywhere you would like. There is no wrong location. Wherever you choose will hereby known as $ANDROID for future reference.
2. Download Eclipse IDE for Java Developers
When I develop for Android, I choose to use Eclipse as my Integrated Development Environment (IDE). Eclipse can be suitably adapted for Android development since you can get plugins to help with creating your Android project, launching your Android emulator, and preparing your Android application for the Android Market. It is not an ideal IDE, but the pros outweigh the cons for Android Development.
From the Eclipse Downloads Page, choose the “Eclipse IDE for Java Developers. Make sure you are getting the correct version for your operating system. Eclipse is fairly large (~100MB) but still a lot smaller than the 4GB XCode for the iPhone!
After your Eclipse IDE download is complete, unzip and move to a permanent folder. I use the applications directory in my home folder (~/Applications/).
For OSX users: we will want to have access to Eclipse.app from within our Applications folder. To do this:
·         Make an alias of the Eclipse.app file (CTRL-Click then “Make Alias”)
·         Move the alias into root applications folder (/Applications/) so that it shows up next to your other applications
Now you can use Eclipse just like any other application, including adding it to your dock. I do this with all of programs that I download that do not have installers (i.e., they are just .app files). This may not be a necessary step (I am fairly new to OSX), so please let me know if there is a better way!
3. Install the Android Development Tools (ADT) plugin for Eclipse
Next, we will use Eclipse to install the Android Development Tools (ADT) using Eclipse’s built-in plug-in system. From within Eclipse:
1.       Choose “Help” > “Install New Software….”
2.       Click the “Add…” button and create a new entry:
o    Name: “Android ADT” (this space is for your own personal use, so name it whatever you want)
o    Location: “https://dl-ssl.google.com/android/eclipse/” (try just http:// if the https:// does not work for you)
3.       Check all the boxes to install all the tools
4.       Just keep clicking “I agree”, “Next”, “Yes”, etc. until it asks you to restart
5.       Go ahead and restart Eclipse when prompted to




4. Connect Android SDK with Eclipse IDE
This next step connects the Android SDK from Step #1 to the Eclipse IDE from Step #2. In Step #3, you should have restarted Eclipse. If you have not done so, do that now. From within Eclipse:
1.       Click on the “Eclipse” menu (next to the apple logo for OSX) and choose “Preferences”
2.       Click on “Android” heading in the menu-tree to open our Android Eclipse preferences
3.       Click the “Browse…” button to the right of the ”SDK Location” box
4.       Enter the location of your Android SDK (the $ANDROID path from Step #1)
5. (Optional) Additional Android/Eclipse Config
While we are in the Android section of our Eclipse preferences, let’s change a few more things. These steps are entirely optional. For these additional preferences, we need to expand the menu-tree under the “Android” heading:
1.       Click on the triangle next to the “Android” heading in the preferences tree to expand our options
2.       Click on the “DDMS” sub-heading and change the “Logging Level” settings to “Verbose” so that we see everything that goes on while developing
3.       In the “Usage Stats” sub-heading, click the checkbox to allow Google to know how we are using the SDK (seems fair enough, right?)
6. Decide Which Android Platforms You Will Support
This graph will help you decide which ones are relevant and worth your time. I recommend checking theAndroid Platform Versions Graph every month or so to see how rapidly it changes! When I first found this graph less than a year ago, Android 1.5 and Android 1.6 together represented ~50% of the graph. Today, they are only ~8%. For me, this dramatic change in Android 1.5/1.6 deployment means that my efforts will be better spent focusing on Android 2.1+. For you, it may be worth it to support 1.5/1.6 for those 8% of users. Only you can make that decision.
When deciding, consider that you will need to test, debug, and provide customer support for every version of Android that you support, and for each individual device that runs those versions! For example, deciding to support 2.1 means that there are a whole host of different hardware devices that you may receive feedback regarding; whereas supporting 2.3.3 (for right now) only means the Nexus One and the Nexus S. Just keep that in mind while deciding.
From a resources standpoint, not only do you need to test and support each version that you plan to release for, but you also need to have those Android SDKs and Android Emulators on your machine (which takes up space; which, on my smaller SSD, is a finite resource). It may not be an issue for your, but it is just yet another thing to keep in mind.
Finally, no matter which versions you choose to support right now, make sure to check the Android Platform Versions Graph every month or so to see how it is changing, and to adjust accordingly. This will let you know when you can stop supporting older versions of Android and, most importantly, will let you know when you need to start supporting newer versions of Android as they grow and gain traction.
7. Install Android SDK Components
Android is packaged in such a way that the base Android SDK (downloaded in Step #1) is distinct and separate from each API version of the Android SDK. This means that for each version we want to support (from Step #6), we need to download a separate Android SDK for that version. This can be very annoying when installing (notice how many steps we have done by now), but in the long-run is a very beneficial design for us Android Developers. As new API versions are added and old API versions are phased out, we can install/uninstall the APIs as compnents, rather than a single huge download like XCode is for iPhone (4GB! I just can’t get over that! Who has a 4GB download for a minor version change?!)
We need to download the Software Development Kits (SDKs) for the Android versions that we want to support. To do this, we can use the Eclipse IDE + Android ADT that we installed in Step #3. From within Eclipse:
·         Click on “Window” then “Android SDK and AVD Manager”
·         In “Available packages”, select the platforms you want to support. You can either choose all, or pick-and-choose what you want to develop for. For example, 2.1, 2.2, and 2.3.3 are all I care about, so I am using API 7, 8, and 10. In the “Android Repository” package, I checked the boxes next to:
o    Android SDK Platform-tools, revision 3
o    SDK Platform Android 2.3.3, API 10, revision 1
o    SDK Platform Android 2.2, API 8, revision 1
o    SDK Platform Android 2.1, API 7, revision 1
o    Samples for SDK API 10, revision 1
o    Samples for SDK API 8, revision 1
o    Samples for SDK API 7, revision 1
o    Android Compatibility package, revision 1
·         In the “Third party Add-ons”, decide what you are interested in. If you are going to be using Google Maps (or anything Google beyond Android), you want to install their APIs. If you want their licensing / billing packages, get those too. I checked the boxes next to:
o    Google APIs by Google Inc., Android API 10, revision 1
o    Google APIs by Google Inc., Android API 8, revision 1
o    Google APIs by Google Inc., Android API 9, revision 1
o    Google Market Licensing package, revision 1
o    Google Market Billing package, revision 1
·         Choose “Install Selected”, then the “Accept All” radio button, then “Install”. This may take a while. If it seems like your download has paused, check for any confirmation dialogs that you need to click “Accept” to. These can sometimes be hiding in the background.
8. Create Your Android Virtual Devices (AVDs)
Last but not least, we need to create Android Virtual Devices (AVDs) that will be our Android Emulators for running and testing our Android applications on our local computer. In the same “Android SDK and AVD Manager” from Step #7, choose “Virtual Devices” on the left and create “New…” ones. I like to create AVDs to represent different Android versions that I want to test, as well as different hardware specs and screen densities my users are likely to be using.
The main idea is to test different versions of the Android API, as well as different screen resolutions and densities. I tend to pair older versions of Android (most likely running on older hardware) with lower screen densities, and new versions of Android (most likely running on newer hardware) with better screen resolutions.