Help please! Kindle fire behaves differently to other android devices
Hi, We've have an app that works fine on typical Android devices but behaves differently on our two kindle fire 7" HD devices. This is the scenario - app is running fine 60 FPS - user clicks button to launch web view e.g. login to Facebook - activity is started - Facebook dialog is showing - user presses BACK button to return to OUR app - now the FPS is 30 FPS - it's dropped by 50% If the user presses the HOME button and relaunches then we are back to 60FPS (app hasn't been quit) On the Android devices we've tested on (quite a few), the frame rate drop doesn't happen when the back button is pressed. This is driving us crazy as we really would like to launch our app on the Amazon app store before the holidays :( Any help or suggestions is much appreciated. Thanks Scott
Hi Meyumeapps, Thank you for writing to us. Without looking at the code its difficult to find the root cause of the issue. Is that possible to isolate the issue in a sample app and provide the source code of it through ContactUs (
Is the Amazon SDK for Kindle 7 HD much different to the Android variant? I've got the simplest of test apps built using the MOAI game engine (
http://getmoai.com) The app performs flawlessly on my Android devices but has 50% frame rate slow down when returning to the app on the Kindle Fire using the back button. All I'm doing is starting an activity to open the silk web browser and show the Google Home page. Any tool that might help me isolate the problem? I'm using a GLSurfaceView Renderer and the ononDrawFrame is called at a solid 60 FPS. After back button pressed this rapidly drops to 30FPS. I've timed the render and update code in my app and it takes no more than 2ms, even after the slow down. It's almost as if something else is dragging the frame rate down, like a spinning thread or something. I'm happy to post an APK if it help? Thanks Scott
Some more information: The slow down also occurs if I DON'T launch the activity from my app but instead press the quick menu and then go through app search. Returning to my app from search is an immediate 50% slow down. It is almost as if the quick start menu continues to consume resource after it has been closed?