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. :-(
Related
With some effort I finally managed to install Qt for Android and wrote my first testing app. Everything went ok when debugging(usb debugging on galaxy s5) but after deploying the app via "Bundle Qt libraries in APK" and installing+running it on the phone I encountered a problem.
The design of the app changes after the first time run. The left screenshot is how the app looks after installing and tapping 'Open'; the right one is made after closing the app via the back button and opening it again from the app drawer:
(The add button in the first image is blue because it was in focus)
As you can see, the slider(QSlider) theme changes, and the 'Add' button also gets smaller.
I've also built and deployed the app with the x86 kit(instead of armeabi-v7a) and installed it on Genymotion Nexus 5 emulator, getting the same strange behaviour.
I am running my web application built in using HTML5 on the android browser.
I have one search box on my home screen.
Whenever I tap inside the search input box the virtual keyboard appears and the application is shrinks and resizing with whatever available place above the keyboard.
This behavior I have seen on samsung galaxy tab (3.1), samsung galaxy note (2.3.6) and samsung S3(4.0)
But, if I run the same web application on the HTC desire(2.3.5) or even HTC evo 3D, the keyboard appears above the app and the application does not shrinks.
I am looking if there are any setting for web browser on android.
I know there are manifest file settings like resize pan and other for android hybrid as well as native application but I want to know if there are any settings for normal web application running on android browsers.
Try
android:windowSoftInputMode="adjustResize"
in your manifest file.
You might need to use android:windowSoftInputMode="adjustResize|adjustPan".
Place this code in the activity under application , where u want such setting
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.
I have this browser launching application which didn't have any problem till now: when it is being tested on Samsung Galaxy 10.1 (Model Number: GT-P7510) with Android 3.1 Honeycomb.
The issue is this: whenever I tap on a text box, the whole screen will flash across a black screen for a moment and revert back to normal. It starts flickering/blinking the black screen when I leave a focus on any text box as well.
Currently, I've no idea what is causing this issue as I've tested this application on several devices e.g. Samsung Galaxy S, Samsung Galaxy Tab 7-inch with previous version of OS from 2.1 to 2.3.
Anyone who has any clue as to what is going on whether be it a compatibility issue with the app or a change in function in honeycomb 3.1 or the device itself, please share your information and enlighten me on this matter please. Any kind of help is greatly appreciated!
Thanks
I'm sorry that this is not a solution, but I think I can shed some light on the problem.
We have recently been testing a functional jQuery Mobile HTML5 app wrapped with PhoneGap Android 2.x phones to the Galaxy tab 10.1. We have seen something very similar, with the exception that we have defined a splash screen for our app. What we see is that when an input field is given focus, the screen flashes up the splash screen momentarily. Very annoying! To verify if this is the same problem, define a splash screen for your PhoneGap app and see if the screen flahes your image instead of a black background. Knowing something about what's going on with PhoneGap and the Android WebView, this is my best estimation of what is happening: PhoneGap loads the main App activity with a black background and displays the splash screen (if defined) in that initial window. PhoneGap then starts the WebView and opens it on top of the main Window. When a field is selected, the Android invalidates the component wach time it updates it based on a focus event or keypress, or whatever, and Android redraws everything. So it redraws the main window behind the WebView and then redraws the WebView with the HTML page content on top of it. Since the device is not properly double-buffered, you see all of this redrawing in all its ugly glory right in front of your eyes.
We have seen serious glitches with Android web forms on some Android 2.x phones we have tested, and this looks like yet another glitch, but this time on the Galaxy Tab running Honeycomb (3.0).
We have attempted to use CSS -webkit-backface-visibility to resolve issues on some phones when experiencing flicker in the past - but this has caused serious rendering issues in HTML forms. Be warned! In theory this should be a viable fix to introduce some double-buffering into the mix, but in our experience it causes more problems than it solves.
I am not confident that this can be resolved, except by an Android software update from Google/Samsung.
So I've searched for an answer but found nothing. Basically, whenever I run a simple little menu app for android tablets using the eclipse android emulator 3.0, only about 1/6th of the app is shown (the top center piece, if the tablet is held landscape.) I've done tutorials using the 2.2 emulator and they work just fine, but whenever I launch the 3.0, the app (and only the app - the android home runs fine) just doesn't appear. When I look at it in the main.xml layout folder, the graphical layout shows it exactly the way I want it to appear.
Is this a problem with the emulator? This can't be a common problem, otherwise I'm sure I would have found a solution by now, but there must be some switch or something that I'm not seeing that's making the app appear as if it were running on a phone and not a tablet.
Do you have a low resolution set for your 3.0 AVD? If you run the AVD Manager, what resolution does it show?