Greeting.
I'm currently working on a crossplatform test project that involves adobe cirrus for video chat and such. The application is written in Flash builder 4.6 standard (no profiler option) in flex and A3 and the target platform is Windows and Android.
Both use the same code and strangly the windows version works well without any freeze/unespected termination, but the android one somtimes just quit out of the application back to the android homescreen after using the video chat. And when i reselect the application window, it seems like it has restarted.
I tried to run the application in "debug" mode on the device, but there's no error poping up when the application crash/exit just a "terminated, exit value: 0" message.
I'm using resource monitor app to monitor memory and cpu to check if it's a out of memory issue, but the app seems to use a stable 60-70mb of the memory leaving about 280-300mb left and the cpu is at the highest on 80%.
I also tried to alter needed phone "right" to everything, even if I really only need phone wifi state, internett and camp&mic.
I'm not running any other apps beside the resource monitor and the test app when testing.
So any clues?
Related
I use my mobile device to run my flutter applications. I know all about the hot reload but I'm so tired of having to wait every time I connect back to my phone again maybe the next day and then the app has to be re installed and the gradle task assembler has to be built again. Please I want to ask if there is a way to reconnect easily and a way for the apps to run easily again any time I want to work on a project again after a while.
There are a couple of alternatives to building the APK and installing it on a physical device:
Use an emulated android device
You can use an android emulator. The easiest way to set that up is probably the graphical interface in Android Studio (see https://developer.android.com/studio/run/managing-avds), but you can also use flutter emulators --create [--name <Name>] to create a new virtual device. Then use the button in the bottom right of VS Code to select that device, before launching the debugger.
Build for desktop
Depending on the dependencies of your app, you could try building the app for the platform you're developing on (Windows, Linux, or macOS). This has the same visual result as an Android app, but does not need an emulator or physical device. The rendering engine is the same (Skia) on all platforms. The obvious downside is that some plugins may not be available for desktop.
See https://docs.flutter.dev/development/platform-integration/desktop on how to set that up.
I'm testing phone resource usage using Android Profiler from Android Studio, however I am unable to load session other than the project's own application.
I wanted to see usages of the most popular mobile application, but something is blocking me from loading the sessions of installed application.
I think profiler other application is possible since it's mentioned in the developer.android documentation. https://developer.android.com/studio/profile/android-profiler?hl=el#advanced-profiling
Picture of list of other process in the standalone Profiler app can be visible here: Android profiler session options
Here we can see numerous session being shown in the dropdown menu. How can I enable it thought a mobile device or a emulator?
Other than that, if there's a way to profile your whole mobile device resource usage than I would be also interested in this.
Android Studio Profilers are working with debuggable apps only because it reads some sensitive data, such as the memory content in a heap dump. Therefore, non-debuggable apps don't typically show up in the dropdown menu. This is true for standalone profiler as well.
I believe the screenshot showing a list of other processes probably come from an emulator image of userdebug or eng build. You can check by running command "adb shell getprop | grep ro.build.fingerprint". On those devices, every app was considered debuggable by the system. However, Android Studio would be working in the best-effort mode and some functionality may not work unless the app is inherently debuggable (which means, its APK is built as debuggable).
Regarding the question on whole mobile device resource usage: Sorry, it's currently beyond the scope of Android Studio Profilers as the profilers are designed for the app your are developing. However, please feel free to open a feature request at https://b.corp.google.com/issues/new?component=192708&template=840533.
I created a simple Xamarin ANDROID App. I set up my phone to development mode and deployed my app to the phone via USB.
The app continues to work on the phone as a regular app.
I then created a Xamarin MOBILE App which was more complex. I deployed it to my android phone via Visual Studio debug mode as with my previous app and it ran perfectly. But when I attempt to run the app directly from my phone, it won’t run. The first screen partially loads without anything on it and then disappears. My phone puts a message up saying that my app keeps stopping and would I like to close the app. I make use of a file placed in Assets. Might this be an issue when not debugging from the computer?
Might there be a difference between deploying a xamarin android app and a xamarin mobile app.
A minor thing is that it has added the name ‘.droid’ to the name of my app which I would like to get rid of.
I am new to deploying apps to a phone
I have solved it thanks to your helpful prompts.
I looked at the error logs and the error was ‘FATAL’ in a mono dll. This was indirectly helpful in that I knew it wasn’t the logic in my code.
I also made the discovery that running my app directly in the emulator also failed in the same manner as on my phone. I also ruled out that it might be an issue with transferring an asset -a file the my app uses- as I bypassed using the asset.
(Running my app via visual studio in both the emulator and my phone worked perfectly.)
I then decided to re-house my forms and classes in a new template as I suspected it was corruption in some xml configuration setting that didn’t bother Visual Studio. This worked great and the app now runs stand alone on the phone (and emulator).
I have written a simple login page using xamarin forms. When I try to deploy it on emulator, the emulator opens but my app is not visible.
1) Does it take time for the app to be deployed? Or would it appear on start up?
2) Should warnings be considered? I have no errors though.
Most Android emulated devices are slow. I have found that some of them simply won't render an app. This is not an indication that the physical device, which you are trying to emulate, won't work however. Try testing what works in an emulator and then creating a copy of what works in the device manager. Then make slight changes that are closer to the target device in the copy. Deploy every time to ensure that it is working. This process takes patience. If you are fortunate enough to have the physical device, debug through the USB connection.
I am currently developing an Android app without an Android device.
Therefore, unwillingly, I am using Android Studio's emulator as my only source of testing.
However, half the time I use the emulator, the program glitches and the app either stops or does not trigger the functionalities that I put in.
However, the other half of the time (I did not change any line of code when doing this), I'll simply run the emulator again and the app will function normally.
But now I am concerned about this because I am not certain if this is only a bug in the emulator or if the same thing will happen in a real device. Since I do not have an android device, there's no way for me to text this in a real setting.
Can I just ignore this glitch? or is this actually an issue?