I have an android application that i successfully ported to the blackberry playbook. I updated my playbook to OS 2.1 and all of a sudden, when the ported android app switches/launches a new activity, the BB OSs' "multitasking" window comes up showing all the other android applications "running" on the playbook. So i have to tap my app's window again to make it fullscreen. This happens for every activity that my app launches, and my app has about 8 activities all in all... is there anything i need to change in my app to stop this from happening on the playbook? Thanks
Related
I'm creating an Android application and it's nearing completion. Unfortunately, it currently breaks the System UI when I click the square for showing all the applications running when the app I'm creating is open. Any ideas as to why this is happening? Is it using too much memory?
I'm developing a "small" application which creates alarms/reminders using the TNotificationCenter.
The app shows the current time on the main screen, two buttons and a label.
One button is to add new alarms, the other button is for settings.
Outside of the "viewable screen" there are two rectangles containing the components for purpose according adding alarms and the menue.
Both rectangles use a floatanimationn to be shown and hide.
When I compile the app with Delphi XE7 the application works fine on different mobiles (Galaxy S2 Android 4.2, Galaxy S3 Android 4.3, Galaxy S3 Android 4.4).
When I compile the app with Delphi XE8 the application starts fine. I also can press the menue button to show the menue. But when I press one of the menue buttons (show alarms, set sound file, quit application) it freezes.
Especially for this app it would be great if I could use Delphi XE8, because with it I can use a certain sound for the notification (TNotification.SoundName), a feature which has been introduced with XE8.
I have read a similiar problem here:
Black screen with Delphi XE8 Firemonkey + Android 4.4
I followed that instructions, but it didn't help for me. I checked this way, because sometimes the app also started and just showed a black screen. But most of the time it freezes when I press one of the menue items.
You can download the project here:
http://mschlereth.de/stuff/dl/QuickAlarm.zip
Solved
I have built the application from scratch under XE8 and now it works.
Of course, I copied and pasted most of the code, but the interface is built from scratch.
That's a bit frustrating, because it probably means that I would have to do this will all of my applications if I would like to use XE8 as the preferred IDE. :-(
I've faced the different behavior of my app while clicking its icon if it was already launched before.
If I install the app via Eclipse or apk manager, launch it, press home button and then launch the app again clicking the application icon - it will bring the first activity from stack to front.
If I install the same version from the Play Market and follow the same steps - the application is relaunched completely from the very beginning (splash screen activity).
Is there a difference between intents which are used to start the app in this two cases?
How can I simulate the Play Market behavior to ensure that everything is fine before the release?
Thanks in advance.
This sounds like its to do with the android lifecycle. Read more here:
http://developer.android.com/training/basics/activity-lifecycle/index.html
Your activity will go through different stages when it starts back up depending on if it has been completely destroyed or if it has just been stopped. Pressing the home button will only stop your app rather than completely destroying it. If you're phone is running out of resources android might destroy your app in order to free up the resources its using.
Running from eclipse will start your app from a brand new start up (The same as people will get when they install from the market). So if it works when you run it from eclipse. It should work when other people install it too.
I have developed an android application whose first version is already available on Google play.
Now my problem is, when I installed first version of my app on any android device (Samsung galaxy SII, LG Optimus), it works fine for me.
I have created shortcut of my app on home screen and have moved my app from phone memory to SDCard.
Then I have install new version of the same app on my phone and tried to open it from the shortcut that I have created on home screen.
But app is not opening from that shortcut and giving me an error message that "application is not installed on your device".
Does anybody have any idea why this happening?
Haven't you declared one of your activities or permissions twice by accident? You might have declared you launcher activity again somewhere in the Manifest.
i am new to android development and had question regarding custom screen saver.
The requirement is for a tablet which will always be plugged in so battery life wouldn't be
an issue. The required app should behave as a screensaver in that during inactivity, the tablet should launch this app which contains a flash file that displays a series of images and video. When activity is resumed then the tablet takes the user back to the program they were using.
Can this be done via an app without requiring any hacks?
cheers,
abhi
There is no concept of a "screensaver" in Android.
There is the lock screen, which can be modified via custom firmware, though AFAIK it is implemented in Java as part of the OS and therefore could not be replaced via a Flash APK.