Repackaged Android App drawing issues on Blackberry Playbook simulator - android

I am trying to repackage a small game I made for Android to be used on the Blackberry Playbook.
I was able to repackage it and deploy to the Blackberry Simulator on vmware just fine, except the redrawing on the simulator just behaves very strangely. For example I get a lot of flickering when things redraw. And sometimes half the screen draws and the other half doesn't. Sometimes the bottom portion of the screen disappears and all the images get shifted up.
This mostly seems to happen when I'm swapping button images, or using ImageView to do little animations and such.
Has anyone else experienced this? Is it a simulator issue, or will it occur on the Playbook as well? Any idea how to fix?

I can confirm I have experienced the same flickering problems on the Simulator, but I published my repackaged Android app on the BlackBerry AppWorld, got the promotional PlayBook, and the app works fine on the real device. It is definitely the Simulator problem.

Related

Icons randomly replacing one another on compiled Cordova app, Android 7.0 WebView

I'm working on a Cordova mobile app that uses jQuery Mobile. On this app, we've created buttons using icons from the Font Awesome library. In Chrome, everything works great -- the icons appear as they should. However, if we compile the app and run it on our Android test devices then the icons will start to randomly replace other icons on the same page.
If we use Chrome DevTools to inspect the page while the mobile app is running on the phone, the icons display correctly on the desktop inspector, but not on the mobile device.
Here's a screenshot of the icons displaying correctly. This is from Chrome DevTools inspecting the mobile app while it's running live on the mobile device.
Here's a capture of the same screen taken from the device. I've indicated in red where the differences in icons are.
More pertinent observations and facts:
Our primary test devices are Samsung S7s running Android 7.0 -- all of these devices have this same problem.
The icons do not start to replace one another until we've changed pages a couple times.
It's not consistent which icons get replaced. It will vary each time we fire up the app. One icon that gets replaced one time might be left untouched the next time.
This problem does not occur on our older Android test device (Droid Razr Maxx HD running Android 4.4.2).
I've tried re-compiling the app with the android-targetSdkVersion removed, set to 22 and set to 25. In all instances, the icons continue to swap randomly on the newer Androids.
We've upgraded cordova-android to the latest version (6.2.3 as of writing) and the issue remains.
If I use Chrome DevTools to manually remove the Font Awesome icon CSS class (e.g., fa-user-plus) and then re-add it again, the icon will then display correctly on the device.
We've noticed that sometimes (as you can see in the screenshot below) a small white line might appear underneath an icon that has been replaced.
Does anyone know what might be causing this? Any theories on how it's possible for Chrome DevTools to show one thing while the device shows another would also be helpful.
I stumbled across a solution for this problem while debugging a separate issue on the same app where position:relative elements would disappear while I was scrolling on a mobile device.
While I haven't been testing on an iPad, the solution provided in this question iPad Safari scrolling causes HTML elements to disappear and reappear with a delay fixed both issues.
What I did was apply -webkit-transform: translate3d(0,0,0) to the class .ui-btn (the jQuery Mobile class for buttons). After a re-compile, the icons would no longer randomly swap with one another.
I have little insight as to why -webkit-transform: translate3d(0,0,0) fixes this apparent WebView rendering bug. If anyone has a deeper understanding of what's going on, please leave a comment!

Html5 Canvas game - black screen on Android devices after browser is run on the background

as per title, I've made this html5 canvas game by using the toolkit for Createjs with Flash.
It works fine on iPad and iPhone, but my QA tester found a very strange bug on Android: if you hide the browser (not close it, but simply send it on background), when you reopen it the game will either freeze or show a black screen, depending if it's in landscape/portrait mode.
I've uploaded a short version of the game - there is only the main menu, but that should be enough to test the bug - at the following link:
http://upload.id.net/view/zip/52d5d18c9f0a188b
Can anybody please help me with this, as I'm totally oblivious to why this is happening..?
I don't have an android device to test it myself, so there's that, too :(
Try to upload the game first (not running from phone memory card) and see if the problem persist. I'm not sure about this but i strongly believe that it has something to do with security in chrome. Good luck

Ionic side scroll bar not working with Samsung S6

I am facing very weird issue. Working on mobile application using Ionic and Angularjs. Things are pretty good but all of a sudden side menu scrollbar become sluggish. It will be easy to pin point things but issue is only coming with Samsung S6 (Android 5.x). S4 it is good. Any other mobile with Android 5.X version it is good. iOS working great. Just specific mobile it is not good.
I am creating dynamic menu based on response, I tried to do it hard code way but nothing helps. Also cross check digest timing that is also in ms. So, I doubt that can be issue.
I can't even pin point the issue to solve it. As things are very much specific to this mobile.
Any idea to debug it or way I can get and/or provide more info.
Let me know if any further information is required.
PS: I tried fresh ionic application with side menu, there it is working good on S6.

AS3 Air 3.3 app on Android always crashes after 4 seconds

I'm testing on an HTC Sensation, running android 4.0.3.
I'm publishing using FlashDevelop 4.0.3 and using the Air Mobile AS3 App template.
All the application does is display a Rectangle using:
this.graphics.beginFill(0x00FF00);
this.graphics.drawRect(0, 0, 100, 100);
Just so I can see that its actually publishing something.
The app runs correctly if I publish to the desktop, however when I switch to publishing it to the phone, the problem I'm facing is that the application publishes and runs on the phone, but only for a few seconds.. usually about 4 seconds and then it crashes out.
The really weird thing is that it was working fine about a week ago.. I'm not sure what's changed since then, but yeah it started happening this morning, I tried everything I could think of... including stripping everything out of the app and also doing a factory reset of my phone... nothing seems to have helped...
has anyone else had this problem? or have any ideas on what might be causing it or how to fix it? any help would be greatly appreciated.
Cheers
Update:
it seems changing the render mode to "auto" instead of "direct" stops the crashing, which is great, however if you need to use direct for stage3d content this doesn't really help. anyone else having this issue?
Can you post the source code of your application? I do too have HTC Sensation but my firmware version is 2.3.6. It would be interesting to test it.
I just updated my XPERIA ARC to ICS and now I'm having problems with AIR apps as well. Seems the app is not getting the Click/Touch interactions. Some InteractiveObjects like TextInput gets the click and focus as it should, but Buttons are not working. And I'm using latest Flex/AIR sdks...
But I'm pretty sure we are in Adobe/Apache hands until they update the AIR with a fix.

Phonegap application not scaling images properly on Android 2.1

We have developed an application using Sencha Touch and PhoneGap which works flawlessly on iOS devices. It's now time to port the app to the Android OS, which in most cases works great, except when the app is run on a device running Android 2.1.
Images are not scaled properly in this case (they are much larger than they should be). It is likely that I am seeing an example of this bug:
http://code.google.com/p/android/issues/detail?id=5141
There is a work-around posted in the linked forum, but it does not seem to have any effect in my case.
If anybody has further suggestions they would be welcomed!

Categories

Resources