How can I make a BlackBerry app have an icon but when a user does something within the app the app will disappear from the app switcher but be running in the background? I'm thinking of a timer app that will do that. Then when the timer is up it will reappear.
You have to have your application run in two contexts, one a UiApplication context with an icon, one with an Application context without an icon. The Applicatin may be autostarting, or may be started by your UiApplication. This can be done by specifying an alternate entry point into your application.
You have to be very careful with your coding though. Applications that don't exit and are badly written can have a huge impact on performance, battery life and data usage.
Related
I am developing a windows based java application, One of the requirements for this application is, when this application is installed on other machines, it should open automatically at specified time and user has to select some option on the application, If the user didn't choose the options and close/minimize the application, the application should pop-up again after some time.
Please let me know how do I achieve the above functionality.
First of all, because of security reasons windows services are prevented from interaction with users via Gui - one should make significant efforts to show window from service process. You described process that unlikely may be called windows service, rather it should be scheduled. Some kind of Windows port of cron will help you. For instance, nnCron. It can in particular display, hide, close, kill, minimize, maximize and hide specified windows to system tray. Just in case, to fully answer your question - turning process (that has no GUI and was not created as service) into windows service is easy with help of srvany. Srvany.exe allows any Windows application to run as a service.
I have an application that comes baked onto about 10 unrooted device OS's. Located in /system/priv-app. We're trying to update the application and prevent the users from uninstalling a critical update or clear the data.
I've come across a way to prevent the user from clearing data (here), but I'm looking for a way to disable the "Disable" button from the app menu. Anyone know how this works? Is this something in the app configuration or is it only applicable through the OS code?
We had to write a Java application which runs on a windows 8 tablet (not RT).
I would much rather have written it using C#, but we really didn't have a choice.
Basically, we use launch4j to wrap our installer executable JAR in an EXE which then installs the appropriate application files and creates shortcuts on the desktop and in the start menu programs folder to ensure that the user sees the icons on the metro start screen.
The Problem
When the application starts up, it checks if any updates are available via a server, if they are available they are downloaded.
The issue that we've seen is that if the application is downloading the updates, and then we turn off the screen and leave it off for at least 30 seconds, once we turn the screen back on, the application is frozen and does not progress.
We then have to kill the app and start it again.
Providing the screen is not turned off again, the downloads finish and the application works fine.
Is there a way to either keep the screen on, keep our process running or detect when the screen comes back on and execute some code when that occurs?
Any help would be greatly appreciated.
I have an android application which main view consists of a tab-bar with three tabs in it.
When developing and running the application on the device through adb I get the following behavior:
When clicking the phone button "Home screen" and relaunching the application it seems as the application continues where I was before pressing the button (remembers selected tab etc...) (apparently its still running in the background).
However when I export and sign the application (using Eclipse) it suddenly always seem to start a new instance of the application when returning from home screen.
Why does it behave so different in those cases? And what do I need to do in my application in order to always have the "running in background" behavior.
If you always want your application to have "running in background behavior", then set android:alwaysRetainTaskState="true" in your main activity manifest. This prevents Android from periodically resetting your application back to the root activity.
android:alwaysRetainTaskState
It sounds as though your application is being destroyed between the point that you go to the home screen and start the app back up again. This can be due to not having enough memory available on the device. If you have a lot of background apps running on your device this may be the reason it is happening.
I would recommend debugging and checking out which path is being hit, that is, whether or not your app is going through just the onResume lifecycle method, or if it is also going through the onCreate lifecycle method.
I want to write a Java BlackBerry application that runs on startup and stays running in the background, but gives the user an indication that it is running with an icon in the corner of the homescreen. What techniques can I use?
For showing content on the home screen / status bar, see this thread. You can either have different states on your own application icon or add a notification in the BB status bar. All is explained there.
right click on blackberry project ->properties->applicaiton tab
keeps in background: create Appliation type project.
blackberry application that runs on startup:check option "autorun on startup".
but gives an indication that it is running with an icon in corner:
which corner you are talking about?
The blackberry button sits to the left of the trackball/trackpad, or to the left of the return button on the storm. If you press and hold the blackberry button, the OS will show all running apps in a popup. Do you need a more significant notification that the app is running?
The notification ribbon and the app 'splat' are generally used to show message counts and other activity of interest to the user, not just that your app is running.