So, I did a video-game in UE 4.8 and compiled it for Android.
It’s a game for training mathematical abilities in first and second
graders, using Android tablets. However, the game won’t run in the
tablets we are using for the training program. After installing the
APK, when I try to run the game, it immediately closes and a sign
appears saying: “The application has stopped”. I installed the
application in other several android devices and it works fine (e.g.
LG F60, Samsung Galaxy S5). However, I need to make it work for this
particular tablet, because those are the ones we are using for the
training program and we have like 80 of them. The tablet is a
ProntoTec X1, these are the specs:
CPU: All winner A31s Quad Core-Cortex A7, 1.2GHZ;
OS: 4.4 KitKat;
RAM: 1G DDR3;
10.1-inch screen, 1024 x 600 Pixels
I’ve tried different things, like compiling an empty project, but is the same: it works on other devices, but not on these tablets. I also compiled the game using different API versions of the SDK and NDK, but that didn’t help either. These are the versions that I’m currently using: ndk-r10e, ant-1.9.6, jdk-1.7.0, sdk platform-19 (android studio 1.2.2).
Please, any suggestion is welcome. Thanks!
Take a look at the droid versions supported, also have a look at the droid permissions, I had this issue some time ago and the permissions is what did it for me.
Related
Can we based on Android Studio Emulators for different display screens create the App? Can we trust Android Studio Emulators ?
I mean for example whatever that's displayed on the Nexus 7 Emulator, would be exactly the same as it is really displayed on the real Tablet itself.
Yes, we can.
I've compared lots of emulators vs real devices - they are almost identical
Android Emulators give you a basic idea of different layout. Padding and pixel adjustment may be different in real device due to difference between system screen resolution and real device screen resolution.
The Android Emulator is built hand-in-hand with the Android platform for the Android SDK. Moreover, the latest Android Emulator system images (API 24+) 100% pass the Android Compatibility Definition, so that you can have even more assurance that app behavior will be exactly the same between the Android Emulator and a physical Android device.
May be my question seems to be dumb as i'm new baby to this...
I'm trying to run an android application in 7 inch Samsung Galaxy tab(7 inch)...everything work fine but when i move on to Samsung Galaxy Tab S2(10 inch) i faced an alignment issue in my application...Getting crashed sometimes too.
Can anyone suggest what should i do to resolve it...Have to create separate layout files for 10 inch tablet????
Please also tell me how can i test my application in an Samsung Galaxy Tab S2 10 inch emulator.
I can really recommend using Genymotion as an Emulator. It' very fast, and only has some minor limitations as free version, like you might not be able to use Google APIs.
It also provides predefined settings for different Devices.
If you don't want to use a third Party Emu, you could of course use the Android Studio Emulator too.
For the crashes: get used to use the Debugger and to using Unit Tests.
I would also recommend switching from Eclipse to Android Studio, since Eclipse is no longer the supported IDE by Google. Migrating your project shouldn't be a hassle.
Without your Layout code people won't be able to help you on that part.
I have developed an application which uses Cordova/Phonegap on Android to display Open Layers 3 maps.
It is quite similar to this project:
https://github.com/netgis/ol3
I have found that the application runs smoothly on the Samsung Note 4 running Kitkat V4.4.4, and runs fine on an old S2 running Jellybean (almost equally well in fact), but it runs terribly slowly on a bran new Galaxy Tab Pro 12.2 running KitKat V4.4.2.
I was wondering if there is any Cordova/Phonegap expert out there who might know why.
The only difference between them that I can see is the version of android! V4.4.4 and V4.4.2.
I have discovered threads on SO which generically say that WebView can be a problem and cause slow performance, but I'm getting great performance on my Note 4, and the S2 runs better than the tablet does using Jellybean.
I'm not sure code would be useful to show here, essentially I have a Cordova Android application with a single HTML document with Open Layers 3 map embedded, that's it.
The problem turns out to lie with WebView, which uses the default Android browser. For some reason this browser restricts CPU support if you're trying to use GPU acceleration (enabled by default), but doesn't provide GPU acceleration itself (it's really strange but true).
Apparently KitKat has this problem prior to Android V4.4.3. So if you're running V4.4.4 you won't encounter this performance problem as it has been fixed (as it uses Chromium instead of the default browser).
Here's one of many references I've found which corroborate this:
https://code.google.com/p/chromium/issues/detail?id=315111
Some devices haven't yet been updated to this level, here are my completely up to date devices:
The tablet uses Android V4.4.2
The S2 uses Android V4.0.2
The Note 4 uses Android V4.4.4
The S2 uses Jelly Bean and is therefore fine, the Note 4 uses the updated KitKat and also runs fine, but the tablet struggles with the application to such an extent it is unusable owing to it being below V4.4.3.
For me, the majority of suggested solutions on SO are to disable hardware acceleration, but these suggestions are unsuitable as my application really does require hardware acceleration to render maps efficiently.
The solution is to take this problem away completely by forcing the use of Chromium irrespective of the OS Version through the use of Crosswalk.
There are plenty of resources I've found to use Cordova in synergy with crosswalk:
https://crosswalk-project.org/documentation/cordova.html
https://blog.nraboy.com/2014/10/use-crosswalk-ionic-framework-android-apps/
We are evaluating Delphi XE5 specifically to see how easy it is to develop mobile apps. We have developed a simple Android app that scrolls through a TClientDataset using a DBNavigator. The application comprises a few input fields, labels and slider controls (TSwitch).
Everything works ok and sliders (animations) are responsive, except on a Google Nexus 10 (Android 4.3) where everything happens in slow motion. It is like the app is still running in emulator mode. (A sliding button takes over 2 seconds to move from left to right!)
We have successfully tested the app on a Samsung Galaxy S3 (Android 4.1.2) and a HTC One (4.2.2) and the UI is as responsive as one would expect.
Update.
We asked the question at Code Rage 8 and they are referring it to the R&D Department. Will update when or if we get an answer.
I see mention of the screen resolution in comments. Has it actually been determined that it is the screen resolution that is the issue here?
Can you go into the developer options on the Nexus and try anything there that forces GPU usage or whatever might potentially help things along graphics-wise?
And is there anything clue-like in logcat? Run monitor.bat in the Android SDK tools directory or, if the path to it has spaces in, then that won't work so run ddms.bat instead from the same location (DDMS doesn't abort due to spaces in the path).
It would be good to get more evidence on the problem, rather than (educated) guesswork.
If it turns out to be screen size, well that will be interesting for Embo.
I just put an app on the market and it is showing on all phones I have except for my Acer Liquid Mini. This one:
http://www.gsmarena.com/acer_liquid_mini_e310-3711.php
I have phones with the same res screens, Android 2.2, and close enough to the same hardware specs yet this is the only phone that it doesn't show for. It is running on factory defaults. When I try to install by the browser Google just says that the app isn't compatible and no more information.
I have the minSDK set to 4, maxSDK set to 10, I'm not specifying any screen resolutions in the Manifest (as recommended by the Android Doc post Android 1.6) and install location is set to "auto".
Does anyone have any ideas?
Apparently Google has problems with knowing the hardware constraints on some devices, such as this one, my Desire with the 2.3 upgrade and my Irish Galaxy 10.1" tab. They are working to sort it out
You could try deploying you app on appslib, they got a list of devices supported. You can choose a set of features required by your app and see the devices that will be able to run it.
I can't promise that both Android Market and appslib will give you the same results, i.e. will associate a device to the same requirements but that's a track to follow.