Is it possible to get an Android Air app to startup at Boot time.
Doing it in Java seems quite possible (see Android 2.2: How to make an app to run automaticly on startup & how to make an app start another app) but I am not sure how you
do the same thing in AS3.
James
Related
Reproduction:
File -> New -> Other -> Multi-Device Application.
Tabbed with Navigation (or other non 3D, non blank app)
Build and start the app as android 64-bit and launch is in the connected device.
This works.
Now, as soon as you go to:
project options -> Application -> Entitlement List
turn on "Receive push notifications"
Then try to start the app.
The app will no longer be able to start.
The question here is, what exactly is the android API expecting to find in the APP, which causes this crash? I'm not getting into the debugger - the app closes before Delphi Rad studio 10.4.2 (using the v30 Android SDK) is even able to "hook" into anything. With as much as Rad studio is doing automatically, I'd expect it to create the required frame or app hook automatically, but there's just "nothing" that resembles useful information regarding this.
Main article on adding push notifications here:
https://docwiki.embarcadero.com/RADStudio/Sydney/en/Firebase_Android_Support
And yes, I did follow that part as well, with the same crashing result. The google app emulator doesn't give me anything worthwhile either,. I'm a bit at a loss here.
Proglem:
Create custom Android App which will never be killed by the platform.
Given a Dialer app (or a phone-app), for making calls on Android Phone, is there a way to similarly create custom app and make it a system app, so that Android always keep it running?
In other words, the problem we have is to deploy an app which will never be killed by AOSP due to lack of resources or anything similar, which is what I think android does for Dialer and some other system apps/services.
Possible helpful hint: The device will always have power supply, as it is not a phone/tablet but rather a custom device running custom AOSP.
At the beginning I built an desktop application (WPF in .NET Framework) and Engine (Class Library in .NET Framework). Later I tried to built frontend for the Engine project in Xamarin.Forms/Xamarin.Android. I was suprised when I just added a reference to Xamarin project and everything worked fine.
The problem appears when I run my android application and block device using power button - application start to work 2-3 times slower. Even Task.Delay(1000) takes 1500-3000 ms to be executed.
I have internal timer in the Engine project and this problem causes time divergence between real-time and time inside Engine.
The Engine project is multi-thread project. It creates and destroys many threads during work.
What I have tried:
using WakeLock.Partial.
using Android.App.Service
disabled battery power optimization
all permissions for application
add application to "whitelist" in device settings(work in background, ignore battery
optimization options)
Application works fine on blocked device when the device is connected to power source.
Android Version: 10
Is it possible to keep CPU of android device running all time with full power? How to keep code exeuction at normal speed when device is blocked?
I have found the solution - WakeLock inside Foreground service.
Foreground service alone was not enough.
With this combination the Engine works with normal speed when device is locked without connection to any source of power.
I am a bit of an android noob and I am not sure how can I run my app as long as the phone is on.
Well I don't sure how can I open my app on startup and make it so it will run in the background.
By the way, my app is notifing me when I have a certain amount of battery power left.
You should learn Android Service and then implement battery application.
First read android life cycle and its basics then you should try application developent
use this Link
I want to launch the stopwatch application that comes with android from my app but have no idea how to do this.
I do not want to create a stopwatch on my own since it needs to keep running when I close my app.
Up until Android 4.1 (or maybe 4.2) AOSP Android did not have a stop watch in it, and there is no official SDK support for launching that part of the app. Stopwatches are likely installed by the user or the OEM on the majority of devices.