Hello !
SUMMARY: How to run pocketsphinx_continuous on mobile phone with Android, and how to do it with simulator of mobile phone with Android. PocketSphinx can be downloaded for free here, for both Linux and Windows: http://cmusphinx.sourceforge.net/html/download.php .
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------
SHORT EXPLANATION
I'd like to create application for mobile phone and server such that:
1. User runs application on mobile phone with Android, this application uses PocketSphinx. It is Automatic Speech Recognition software for devices like mobile phones, written in C. Somebody told me that "Pocketsphinx is used successfully on Symbian with minimal effort". (However I think Android may be better choice). My knowledge about Android is limited but I know something about CMU Sphinx. Can you help me, please, to run this PocketSphinx on Android? I also need to find simulator of mobile phone with Android. I have already found Wireless Toolkit and I tried to use this emulator, however I think it doesn't allow to run simulation of mobile phones with Android. (By the way I am limited in my project to mobile phone of the price up to about 160 euro; which Android version would be best for my application?).
2. This application communicates with the user. The users speaks digits and some other words (dictionary is about fifteen words, I can create language and acoustic models, as well as formal grammar in CMU Sphinx, with the use of SphinxTrain). The application recognizes those digits.
3. Based on this talk, mobile phone sends information about results of recognition to the server. I can do it in Java for CLDC/MIDP with httpconnection, POST method on the mobile phone side and with Tomcat on server. I think this httpconnection must be possible not only in Java ME, but also in Android C. But this is thing which will bother me later, now I'd like to run pocketsphinx_continuous on Android and try to modify it according to my needs.
Summing up, what I'd like to know is how to run demo pocketsphinx_continuous on mobile phone with Android, and how to do it with simulator of mobile phone with Android. (I've got Wireless Toolkit but I think it is not capable of running Android). PocketSphinx can be downloaded for free here, for both Linux and Windows: http://cmusphinx.sourceforge.net/html/download.php . There are two ways of installing it in Ubuntu. First is to unpack it (it is tar.gz), enter its directory and type "./configure", "make", "sudo make install". The other, different, is written in README file, i.e. run autogen.sh, "./configure", "make clean all", "make test", "make install". The result should be, among many other files, javadoc in doc directory.
------------------------------------------------------------------------------------------------------------
LONG EXPLANATION
What is required to give me some advices is written above. So if you don't want / don't have time to read the whole text, just above explanation is enough. But let me say about other possible approaches which I try to do. Those are worse than what I explained above, but I also tried them.
CMU Sphinx contains SphinxTrain to create acoustic model. It has got some different recognizers (also called decoders), those are PocketSphinx, Sphinx4 and some other. PocketSphinx is written in C and is for devices like mobile phones. Sphinx4 is Java application for PCs because it requires better hardware. There is good tutorial about using SphinxTrain with Sphinx4. It is here: http://www.speech.cs.cmu.edu/sphinx/tutorial.html . There is no similar tutorial for PocketSphinx. However with some knowledge about Android and C it is possible to run it on Android. The other approach than PocketSphinx, is using this Sphinx4. However it requires connection between mobile phone and server, sending audio data from cellular phone to server. It can be done with Skype, but there is still problem on server side with redirecting sound from Skype to Sphinx4. So you see there are two different approaches. One is to run speech recognition on mobile phone with PocketSphinx and Android. The other is speech recognition on server with Sphinx4. There are some ways to follow this second option. One is Skype on both server and mobile phone. (But there is problem with redirecting speech from Skype to Sphinx4). The other is too expensive Digium card. The third one is IVR, but I still look for good open-source IVR software. All of those three ways of second option involve Sphinx4. It was much easier to create application with Sphinx4. It is for PCs, not embedded devices, because it requires better device, extensive floating point math and some other things. But it has much better documentation than PocketSphinx. But I want to use PocketSphinx because I don't need to pay to anybody for access to mobile internet in order to send data through internet for application like Skype. The access to internet is required only for short time to send little text data with httpconnection, POST method. This is why I'd like you to help me, please, with running pocketsphinx_continuous on simulator of PocketSphinx on mobile phone with Android. (By the way, I see I've got installed S60 Developer Tools -> 3rd Edition FP1 SDK -> MIDP -> Emulator).
Summing up in a list, those are in CMU Sphinx:
I. SphinxTrain, which I can use to create files needed for speech recognition
II. decoders which use speech input and some files which I create with SphinxTrain, to follow speech recognition (input speech + files from SphinxTrain = are used by decoder)
II-1. PocketSphinx, written in C, for devices like mobile phones
II-2. Sphinx3, written in C, for PCs, actually the best developed
II-3. Sphinx4, written in Java, for PCs, with the best documentation
II-4. Some other, older versions
Those are possible approaches of solving my task:
I. Speech recognition on mobile phone with PocketSphinx. This is much better way than [II].
Problems: 1. running PocketSphinx on mobile phone with Android. 2. simulating mobile phone with Android on PC. I also thought that maybe I should consider Meamo, what do you think about it? Or use things different than CMU Sphinx, e.g. Simon, HTK, Julius. I looked at those other ASR engines and I think PocketSphinx may be best choice.
II. Speech recognition on server with Sphinx4. There are some different ways of establishing voice connection between mobile phone and server.
II-1. ordinary call from mobile phone to server; server has got Digium card. Disadvantage: Digium card is expensive.
II-2. to use Skype on both mobile phone and server. Problem: redirecting of sound from Skype to Sphinx4 and vice versa.
II-3. can you think about any other ways? I found that Asterisk may be useful.
Greetings !
Summing up, what I'd like to know is how to run demo pocketsphinx_continuous on mobile phone with Android
Click to expand...
Click to collapse
First step would be to setup a toolchain and compile the prog for android
or statically linked with uClibc.
Then push it onto your device and test if it works as expected.
You can also push it onto the android emulator that comes with the sdk.
Just my 2 cents...
Thank you very much!
Can you give me any links to tutorials which can be useful for me?
By the way I know how to create my own application in Sphinx4 and I know how to run demo in PocketSphinx, but I've got some difficulties with creating my own application for PocketSphinx. So if you can have a look at PocketSphinx http://cmusphinx.sourceforge.net/html/download.php and tell me which files I need to have to create new project for PocketSphinx, I would be greatful. I mean that for Sphinx4 the only what I need to do is to enter S:\tutorial\sphinx4-1.0beta3-src\src\apps\edu\cmu\sphinx\demo\helloworld and create my own ...\demo\my_application, and inside it analogically to what is here ...\demo\helloworld. In the case of PocketSphinx, to run the application, I need to enter S:\tutorial\pocketsphinx\doc and run pocketsphinx_continuous. So I check what I've got in this file and I cannot see what files and where I need to have in order to create new project. I uploaded directory doc with pocketsphinx_continuous here: http://www.speedyshare.com/files/19429494/doc.7z
Greetings and thanks once more !
Rough outline: You'll need the Android SDK and NDK, both of which are available from http://developer.android.com/. The NDK will allow you to compile C code. You'll need to wrap the C core in a Java layer to make it accessible to the rest of the Android system. The SDK also includes an emulator, which I believe you've asked for if I understand you right.
I haven't actually attempted this, so that's about all the help I can be, but there is sample code included with the NDK that should get you started.
Thanks for your answer !
I check the google and see that NDK is term of Android, because I knew only SDK abbreviation. I assume NDK is especially for porting (like porting PocketSphinx for Android). So am I right that with this NDK I don't need to change code of PocketSphinx? I think it would be too easy .
There also other question which I've got. It is not strictly connected with Symbian but there wouldn't be any need for porting if I won't solve this problem. I've got my application in Sphinx4. There are also examplary appications for Sphinx4 and PocketSphinx. I can run demos from PocketSphinx (as explained in first post), as well as demos from Sphinx4. I can change source code of demos from Sphinx4 to perform my task. I'd like to do similar thing with PocketSphinx, but even if it should be easy task, I cannot do it. In Sphinx4 it is much simpler because all source files are in one directory. In PocketSphinx it is done in somehow different way. (http://cmusphinx.sourceforge.net/html/download.php). Without ability to move my application from Sphinx4 there is no need for me to port this PocketSphinx to Symbian.
Greetings !
johnyjj2 said:
I assume NDK is especially for porting (like porting PocketSphinx for Android). So am I right that with this NDK I don't need to change code of PocketSphinx? I think it would be too easy .
Click to expand...
Click to collapse
NDK is used to write software for Android devices that are compiled natively to the platform -- for now, this usually means ARM. Java as you probably realize is a bytecode intermediate language that the java virtual machine converts to native calls at runtime. This means that Java is generally platform independent whereas your C code is not.
JNI as used with the NDK is the Java Native Interface (or something to that effect). It allows you to call code that has been compiled for a specific processor from Java. This means that you could put heavily optimized super fast calculations in a native library and call them from your Java app.
It could also mean, that you've more or less written your entire application in some native code, and then you have written a java shim that has enough code to initiate and start your native software. Beware, there be dragons here.
The fact that you CAN do this, doesn't mean you SHOULD. There are a lot of benefits to using the android platform and specifically using the android way of writing applications. Concepts like views, activities, intents, etc., greatly simplify how an Android device interacts with other Android devices and provides a consistent and powerful framework.
For something like SCUMMVM, it is a game (platform) that is very linear in design; you are either actively playing it, or it is on pause. How other applications are running while using SCUMMVM is inconsequential. It sounds like you have very different requirements.
Thanks for answer!
Isn't that link (http://cmusphinx.svn.sourceforge.net/viewvc/cmusphinx?view=rev&revision=9470) simply trying to copy engine library to Symbian, without effect? Only enginge won't help, there is also need to write from zero code which will use this library. So it looks like there is still long way to have it working. Do I understand it properly?
Greetings!
Introduction
Hello guys and welcome to my first guide (be indulgent please haha)
In this guide I will show you how to build your first Android app, knowing java langage will be very helpful to follow up but it's not required.
In addition, we will not see a lot of Java in this introductory tutorial.
That said, if you want to go further in the development of Android applications, you will need to know Java.
In this guide we will create a very simple Android application ("Hello World!) The goal is to see basis of development.
What to expect from this guide
Setting up the development environment
A very simple example
I’ll be using Windows for this tutorial. However, there will be not much difference on another system (GNU/Linux or Mac OS X). You just need to adapt the instructions to your particular situation.
The toolbox : JDK
The toolbox : JDK
As I said quickly in the introduction, Android applications are developed in Java. You may already have some of the tools that I will present here if you ever developed in Java. Well, so much better! It is much less work for you.
A word about Java
One characteristic of Java is portability, which means that computer programs written in the Java language must run similarly on any hardware/operating-system platform. This is achieved by compiling the Java language code to an intermediate representation called Java bytecode, instead of directly to platform-specific machine code. Java bytecode instructions are analogous to machine code, but they are intended to be interpreted by a virtual machine (VM) written specifically for the host hardware. End-users commonly use some special tools installed on their own machines.
These tools are included in the JDK. In addition, the JDK contains the JRE (so also the virtual machine), which is handy.
To summarize, there has two cases:
You are a simple user of Java : you must have JRE.
You are a developer : you need the JDK tools
Frequently asked question :
Since I tried to put myself in Java, I may already have JDK installed ... How do I know if this is the case ?
We will make a very simple little test (or rather 2 ).
Start by opening a command prompt in Windows (Start -> Programs -> Accessories -> Command Prompt) or a terminal if you're on a Mac or GNU / Linux.
To know if JRE is installed, type the following command:
Code:
java -version
To know if JDK is installed, type the following command:
Code:
javac
In both cases, if the command is not recognized, is that you do not have the tool in question (JRE or JDK).
If you have only the JRE, install the JDK.
If you have nothing ... Install the JDK: p (the JRE is included anyway).
In short, now that you know where you stand with your Java environment, you can do (or not btw) the installation.
While all of these explanations were not necessarily required, it is still better to know what is installed, right ?
Installing the JDK
The installation of the JDK will be faster than his explanations, I promise
downloading
To start, go to this address.
Click the "Download JDK" button.
On the next page, accept the license agreement and click on the executable to download : jdk-7u51-windows-x64.exe in my case
installation
To start the installation, double-click the executable previously downloaded and let it guide you (or run it from a terminal).
And voilà ! Here is the first brick laid.
Next steps are installing android sdk, eclipse and ADT plugin or you can just download and install adt bundle wich provide you with :
Eclipse + ADT plugin
Android SDK Tools
Android Platform-tools
The latest Android platform
The latest Android system image for the emulator
Thanks to @FreakOde and @Chain Hacker
Specific tools for Android : Android SDK
Specific tools for Android : Android SDK
We have just installed the JDK. So now you have the tools to develop a Java program. That said, an Android application is a particular Java program. You have the basic tools but not the specific tools to Android.
The tool you are missing is the SDKAndroid. It contains what you need, not to develop a standard Java program, but to develop an Android application.
Download the Android SDK and decompression
To download the Android SDK, go here and choose the file depending on your system.
As you can see, this file is compressed (zip for Windows and Mac or tgz for GNU / Linux). Unzip it where you want on your hard drive.
Remember exactly where you put the decompressed content. His path will be needed for the future. I recommend a safe place that will not move.
Personally, I put the contents of the zip in : C:\Android\android-sdk-windows
Add the SDK to PATH
Frequently asked question :
Ok I do not mind ... but what's the point?
No worries, before the manipulation, let me explain what it is.
What is the PATH?
When Windows (and this is the same principle on Mac or GNU / Linux) executes a command, it will search for it in specific directories...if it is not found in these directories, it considers that it does not know it and returns an error.
These specific directories are defined in what is called an environment variable: a variable (which, by definition, contains a value) accessible by Windows, everywhere, all the time.
The environment variable in question is PATH. To see its value, type the following in the command prompt in Windows:
Code:
echo %PATH%
You get a series of directories separated by ";".
It is in each of these directories that Windows searches for commands that you ask.
For example, the java command that we used earlier, is located in the C:\Windows\System32. Well I'm sure that this directory is in your PATH.
So now, we'll need that Windows knows where the new commands of the Android SDK are.
To add it to your path, execute this command :
Code:
set PATH=%PATH%;"path to android sdk"
So in my case I should execute
Code:
set PATH=%PATH%;C:\Android\android-sdk-windows
One last step is required to install the Android SDK. Do not worry, this is the easiest.
Installing Android platforms
The last step is to install at least one version of Android platform. According to the version of Android, APIs differ a little. At the time of this writing, the latest version of Android is version 4.4.2 (KitKat).
In the SDK directory, an executable is present: SDK Manager.exe. It's a small interface to manage versions of Android.
Run it to start the installation.
Among the available packages, choose the one you want:
{
"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"
}
Personally, I took everything! To be sure not to return.
On Mac and GNU/Linux, run from a terminal the "android" command in the directory / tools /.
The installation will take a few minutes (to me it was quite long since I took everything ...).
Once installation is complete, we can move to: Installing Eclipse.
Development environment : Eclipse
Development environment : EclipseAs for the JDK, it may be that you already have Eclipse installed. If this is the case, great. You can now move on to the next section.
Otherwise, we will install it together.
Frequently asked question :
But in fact, what is Eclipse?
Eclipse is what we call an IDE or "Integrated Development Environment". This is a software that allows you to write programs more easily than simple Notepad in Windows (although it is possible). Besides the color code, it will bring you useful tools to compile your programs, debugging, etc.. It can be used to develop with any type of language, but we use it to make Java.
In addition, Eclipse is designed to be augmented with plug-ins. Thus, there is a plugin to develop Android applications ...! We'll see this in the next section.
Do you like it? Well let's go for the download and installation!
Download
First of all, go here and download Eclipse.
Choose 32 Bit or 64 Bit depending on your configuration (if you do not know , take 32 Bit ) .
On the next page , click on the big green arrow and ... wait for it to finish!
Installing Eclipse
Installing Eclipse really comes down to ... unzip the downloaded file!
You can place it anywhere on your hard drive. Personally ( on Windows ), the story that things are organized , I placed the folder " eclipse" in C:\Program Files ( or C :\Program depending on your version of Windows).
To start Eclipse, run the executable found in the directory "eclipse" (really , you guessed ? haha ) .
At startup, Eclipse will ask you the location of your Workspace. This is the directory that contains all the data related to your Java programs ( and thus your Android applications). Your source code will be stored there. This is the time , if you have a hard drive dedicated to your data, choose a directory therein. Otherwise, you can leave the default directory.
Well. Now , to develop our Android apps more easily , we need a small plugin.
A small plugin for Eclipse ADT
A small plugin for Eclipse ADT
As I briefly mentioned in the previous section, Eclipse has been designed to be able to receive plugins. Depending on whether you are Java, PHP, Javascript developer, (...) you have at your disposal a whole bunch of plugins that make your life easier.
The plugin for the Android application development is called ADT (Android development tools).
This time we will not download the plugin on the website of his publisher but directly from Eclipse.
ADT installation:
So first start Eclipse. In the "Help" menu, select "Install New Software ...".
In the window that opens, click on "Add ..."
Enter the following values:
Name: Android Plugin (for example)
Location: https://dl-ssl.google.com/android/eclipse/
Click OK, and wait a few seconds. Then you get this window:
http://img15.hostingpics.net/pics/156355window.jpg
Check the "Developer Tools" (which also tick the underlying tools) and click "Next". In the next window, click again on "Next"
In the next window, accept the terms of the license agreements and click "Finish"
During installation, you may get a security warning.
It tells you that Eclipse does not know what you are installing. But we, we know. So you can safely confirm by clicking "Ok".
At the end of the installation, you are prompted to restart Eclipse.
We have one small thing to do before moving on to the next part: Configure the ADT plugin. We will tell the plugin where the Android SDK.
In the "Window" menu, select "Preferences".
In the left pane, choose "Android"
Click "Browse ..." and choose the location of the SDK installed earlier in this tutorial.
Click "Apply" then "Ok". And voila!
Setting a virtual device (for testing)
To test our application, we use a virtual phone! Very convenient because it's cheap (well it's free )
Our virtual phone (yes you can have more than one if you want) are called "AVD", which leans "Android Virtual Device". It fits with what you want to do.
To begin, click on the little button as shown in the screenshot
This opens the AVD Manager. You should have no AVD yet. To create one, click "New ...". The following window is very important because it will define your "phone":
Configuring AVD could be a complete tutorial ... We therefore remain there for the moment.
Click the "Create AVD" button to complete the creation of your virtual mobile. You then end up with a beautiful AVD in your list. You can then close the "AVD Manager" to finally move to developing your first Android app
New Android project
Finally! We reach the goal! Now it's good, our environment is in place. If you have not had any problems so far, you are ready to create a new Android project.
Create a new project
To begin, select from the menu "File" -> "New" -> "Project". With the ADT plugin, you now have the option to create a "Android Application Project". Select this option and click "Next". Then you come to the window, which allows you to initialize your Android project:
Here are the important information to fill :
Application name: This time it is the name of your application. That will appear in the very eyes of the user. You can put special characters if you wish.
Project Name : This is the name that will define your Eclipse project. You can put whatever you want but avoid spaces and other special characters.
Package name: By convention, the name of a package is in the form of a "url upside down ." You can put your personal domain name or whatever you want. As long as you do not post your application on a large scale , it is not very important.
Minimum required SDK: This is the minimum number required API to run your application. You can not install the application on a mobile with an older API.
Build Target : Select the version of Android on which you want to work .
Click "Finish" to create your project.
Application code
Code créé par défaut
Here is the code created by default:
Code:
package com.test.helloxda_university;
import android.os.Bundle;
import android.app.Activity;
import android.view.Menu;
public class MainActivity extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
}
This code contains various elements:
Package Name
some "import" android.*** : Required libraries to the script
The class MainActivity that inherits from Activity.
I will not detail what constitutes the onCreate() method because we will now change it.
Code of our "Hello XDA-University!"
The purpose of our application is to say "Hello XDA-university". For this, we need a field "text". On Android, a field of this type is a TextView (Android, all the elements are based on the View class).
We create our TextView with the following line:
Code:
TextView tv = new TextView(this);
This requires to import the corresponding library:
Code:
import android.widget.TextView;
we apply a text to our TextView:
Code:
tv.setText("Hello XDA-university !");
Finally, we apply the TextView to the current view:
Code:
setContentView(tv);
You will notice the following line:
Code:
super.onCreate(savedInstanceState);
It can tell Android how to start the application (we call the onCreate method of the parent class by passing the savedInstanceState, which is the previous state of the application).
Complete code (what a code!) of our application:
Code:
package com.test.helloxda_university;
import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;
public class MainActivity extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
TextView tv = new TextView(this);
tv.setText("Hello XDA-university !");
setContentView(tv);
}
}
With this, our text should be able to be displayed without issues.
Launch the application in the AVD
To launch the application, choose "Run" from the menu ... "Run"
The AVD will then take a few moments to start: you will see the letters "ANDROID" in gray on black background. This might take some time depending on your configuration.
Once the AVD is fully started, your application will launch automatically:
Ta daaaa!
Well I told you: nothing transcendent ... But we must start somewhere.
We arrive at the end of this tutorial dedicated to the establishment of an environment of Android development. This is not the only way.
There are many steps to finally not much except a little "Hello!" ... But you are now armed to get started with Android. I leave it to you to learn the art of developing Android applications: Sights, Activities, Intents, etc. ....
I hope you learned something with me and if you have any questions do not hesitate to ask me.
this is a great writeup. Thank you!
wfarid said:
this is a great writeup. Thank you!
Click to expand...
Click to collapse
You are welcome mate
subscribed for now. I might need this later. TQ
This is something great you have done dear..:good::good: Great tut BTW..:angel:
Probably u could have just told them to download "android bundle" from developer site..that could have saved a lot of their work
Cool..!
Sent from my Nexus 5 using XDA Premium 4 mobile app
great guide!
Just a suggestion: I think You can also avoid the virtual device's setup for testing because eclipse let You also to test the apps directly on the smartphone if You have usb debugging enabled ... it's quicker for me because a virtual device requires memory to run ..
Awesome TUT
Subscribing it might need it in future!!
Yhank You !
Dude a suggestion don't get angry you can just link to the ADT bundle instead of downloading SDK and Eclipse separately... By the way nice guide for starters.. :good: But you could have also included using XML stuff and not just the coding.. Just a suggestion.. After all they also need XML to master developing...
Amazing!!! I just start learning Java for a couple week now but now I can learn Android dev at the same time too. :good:
Hi...! Congratulations! Its an excelent guide. Im not a developer but reading the lines makes me want to learn more. If you ever want it to be translated just let me know. Salutes from Argentina!
Enviado desde mi Moto X mediante Tapatalk
Finally someone makes a guide using proper english!
Google has all this explained on the android website but it is as if they dont know english and wrote it all from a translator without the grammer!
So thank you! But a tad bit to late, i did all this a year ago (took me a few weeks)
I recommend using version without demo apps, its smaller. But if you want to try demo apps to test if is JRE working, use version with demo apps.
This app provides a complete Java Runtime Environment (JRE) for Android devices. This JRE include a Java Virtual Machine (JVM) and Java SE 7 class library APIs. This enables running standard Java SE 7 desktop applications on Android devices. This includes Java applications that use Swing and/or AWT graphical user interfaces.
You need to be logged in google account to run this app.
The JRE is capable of running any "pure Java" applications. If the Java application includes/requires application JNI libraries then these native libraries will need to be rebuilt (compiled/linked) with the Android Native Development Kit (NDK).
Using this App to successfully run a specific Java application, will require some basic knowledge of using a JRE. For example you will need to copy the application JAR files to the device's file system and then configure a command line to launch the Java Virtual Machine (JVM).
The following is a list of limitations in the current release.
- Java Applets embedded inside Android web browser are not supported. (There is an Applet viewer included that can be used to run Java Applets standalone)
- JavaFX is not supported.
- Only supported on Android devices with an ARMv7 processor.
The following is a subset of Java applications that currently will NOT run on this app due to missing JNI libraries.
- Minecraft for PC
** Java is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Click to expand...
Click to collapse
Java JRE without demo apps
Java JRE with demo apps
Update: links removed. Moderators not allowed this app, because it is moded JRE4A with crack. I will upload it somewhere else, and here will be Tutorials what write to google, to find it.
Sony Xperia Z3 Stock 6.0.1 - Not working :crying:
gouster3 said:
I recommend using version without demo apps, its smaller. But if you want to try demo apps to test if is JRE working, use version with demo apps.
Click to expand...
Click to collapse
While this sounds great, could you give a few more details:
Did you write this yourself?
Why is a Google account required?
How do AWT/Swing work? Don't they usually use native widgets? What does your JRE use instead?
FD_ said:
While this sounds great, could you give a few more details:
Did you write this yourself?
Why is a Google account required?
How do AWT/Swing work? Don't they usually use native widgets? What does your JRE use instead?
Click to expand...
Click to collapse
It is JRE4A with removed trial limit, and moded popups to be more user friendly. For example popup with buy, reedem, tral is modded to: Welcome to JRE, OK button have trial button function, other buttons removed. Then dialog this is trial version and will work only one minute... is changed to press ok to start java app. Title changed from jre4a to java, and icon changed to java icon.
Google account is required because of jre4a licencie checking. You dont need to have buyed jre4a, but without account app crashes. It is a bug.
And please removed links from quotes.
Soon i will post guide how to find this files on google
No you will not. Cracked apps and warez are not allowed in anyway on xda. Nor are you allowed to tell people how to find it.
Thread closed