Is there a way to launch one Java ME Midlet from another? Both of them would be running on CLDC Phones. What we are planning is that there's one main midlet that will do maximum of the work and there's a smaller midlet which will be launched based on certain condition in the main midlet.
Automatically launching MIDlets is typically done using the MIDP2.x PushRegistry API (with a loopback network trigger) or using the Content-Handling API on the phones that support it (recent Samsung, Sony-Ericsson, Nokia...)
Related
I am working on open-source programs to control Amateur radio via serial ports. However, since serial ports are an exclusive resource only one application can use it at a time, but there is many applications that want to talk to the radio. I am writing an application that pretends to be a radio so the client can talk to it. Under the covers via SignalR sends and receives radio information via HamBus which the repo is on GitHub if you are interested.
So what I need is for the ham app that wants to talk to a radio via rs-232 to talk to my app via ptys instead.
On Windows, I use virtual COM ports and it seems like I can use PTY for the same purpose.
Is this possible? Can I do it with C# and .NET Core?
I am trying to find a clever way to keep a BLE app active in the background on iOS 6, without breaking any of Apple's rules. I plan to use the phone as a peripheral device and another BLE circuit as the central. My app will automatically be opened when a user arrives to a building using geofencing. After that the iPhone will connect to the first BLE central device it sees (the device will be in its white list). The user will then be able to move throughout the building switching to different BLE "nodes".
My question is: What do I need to do in the background when a user is stationary at their desk so that the app does not get suspended due to memory resources?
My idea is based on this solution for a separate problem: There could potentially (not regularly) be 10-50 users in an area with only a few BLE "nodes" and I read at bluetooth.org that I could setup a dynamic connection system, basically rotating connections through all the users.
My idea is to setup a similar dynamic system where the central device (not the iPhone) disconnects the device on regular intervals (30-40 minutes) and then the iPhone will reconnect.
Is this something that some feasible? Is this against the iOS development guidelines? I was unable to find anything explicit about this. I have also asked on the iOS developer forum, but unfortunately it is not as popular as this site.
Thanks in advance!
Xcode -> Project target -> Capabilities -> Enable background mode
Check Uses Bluetooth LE Accessories
Capabilities
Also enable the following key in .plist file
Required background modes
App communicates using CoreBluetooth
Plist
Is it possible to run an application in background and user can use the mobile simply and can do the common task in j2me ?
As far as I know...
It depends on the mobile for which you are developing the app. If you are developing for a mobile OS like Symbian S60 which supports multitasking then it is auto-handled by it.
Edit
To know how to minimize a J2ME app to run in the background see the following threads:
How to make a J2ME application run in Background?
How Do I Minimize a J2ME App?
I want to write an application that sends text from one device to another. How can I test it with an emulator on a PC? Is it possible with the Sun Java Wireless Toolkit?
Yes, it is possible, at least with version 2.5.2_01
Just launch the emulator 2 or more times, and the phones "find" each other
I need some way to communicate between J2SE app and j2me midlet running in emulator in netbeans. How can I achieve this?
Well, technically, Netbeans is a J2SE application so you are already doing this everytime you launch the J2ME emulator.
I expect that when Netbeans launches the emulator, it does it in a way that sends the emulator standard output and standard error back to Netbeans. Presumably using the emulator executable command line parameters. That is one-way communication though.
The debugger inside Netbeans uses a standard protocol to retrieve information and manipulate the emulator:
http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jpda.html
Of course, using this still restricts what you can do.
Since the emulator is meant to represent a phone, the only pure-Java to pure-Java communication channel is networking. That means opening a tcp, udp or http connection between the two environments. Of course, getting this to work once you put your J2Me application on an actual phone will require quite a bit of setup on the J2SE side of things.