We have a simple app deployed using PhoneGap targeting Android version 2.2 API 8 and up. On the various android emulator's I've setup it works and on all the devices in the office it works....except one and go figure it's the squeaky wheel in the office. So enough noise has been made that I am now tasked with spending time on only one device. I've setup an emulator as close to it as possible. The device is a Motorolla Droid2 Global running 2.3.4. Know right off the bat I can't setup the emulator to 2.3.4 only 2.3.3. I understand 2.3.4 is only a service patch but I'm trying to mimic it as best as possible.
The behavior that it exhibits is that upon opening on this one device it hangs indefinately with a white modal screen and the spinning animation. Of course I can't get the behavior to happen in development. Further everything is self contained so there are no web services etc. involved. So I need advice on how to debug.
My current thought...may not be a good one is to fall back to the 80's and put a message box display after every significant line of code and push the .apk onto her device.
Also since this happens at the very load of the application here is the code...one line.
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
//setContentView(R.layout.main);
//super.load( "file:///android_asset/www/index.html");
super.loadUrl("file:///android_asset/www/index.html");
}
Any thoughts greatly appreciated.
JB
This is more a path towards a solution than an actual solution, but anyway:
Get some logging in your javascript and get it connected through to the logcat log; also get logging in any java functions you call or have added to the phonegap base. Run logcat and see what you get in the way of messages from all levels. Develop suspicions and set logging traps for them.
Related
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
I'm using the ImpactJS framework for work and I've tried what most of people did to get their games to work but with no luck, most recently I tried following the instructions from this thread: http://impactjs.com/forums/help/cocoonjs/page/1.
It seems whatever I do CocoonJS refuses to launch the Impact framework (I've tried with both a game and with just the framework alone but nothing happens), whenever I launch the game I get a black screen running at about 60 fps.
Again I'm just trying to get the framework itself working but even that seems impossible. Does anyone have any suggestions?
I'm pretty sure you have a javascript error (see console log), or maybe you have debug enabled on ImpactJS (debug requires DOM, not supported by CocoonJS)
I'm trying to show one public twitter profile in one WebView of my app, is not necessary to login twitter, in the MotoDev Simulator this works fine, but in the physical device don't work, this: "403 fobiden limite exceed rate" error appears, this is the simple code line that I'm using:
webView.loadUrl("https://mobile.twitter.com/#!/asambleaecuador");
and works fine into de MotoDev simulator AVD
....can somebody helpme please!!!
Thanks
Did you figure this out?
I was just wondering why you're trying to use "https://mobile.twitter.com/#!/asambleaecuador" instead of simply using "https://mobile.twitter.com/asambleaecuador".
Anyway, I just wanted to say that there's no "MOTODEV simulator AVD", MOTODEV Studio uses the regular Android SDK emulator, nothing special to it. And the problem you're facing is probably due to differences between the underlying implementation of the AVD browser and the one you have on your physical device - Android devices have a great amount of different browser implementations.
I have created an application in Qt Necessitas. When I start it on my Android device I have a GUI which is very different from what I see in Qt Creator.
For example: I have created spacing between a label and textbox and when I start it as a desktop app everything is okay. But when I port it to Android it seems it's not working. And then my textbox is smaller than in the normal GUI in Creator, as are the buttons and so on.
What might cause this and what can I do about it?
And one more thing: I have a problem with resizing the app size to the max of device window. But I get error about loading fullscreen FALSE.
I have started Qt Mobile application. Everything is done in mainwindow. So I have put all commands on my mainwindow. I don't know what to do. If you need a specific file please tell me, so I can post it here.
Try making your Mainwindow smaller and play with sizes. maybe the resolution you are using is not supported by the device.
I'm very new to android development and to get started I've started modifying the android ask sample 'shape wallpaper'. I've added a touch ripple, change resources etc and removed the more basic example. If I have my se xperia x10 plugged in and run the app it downloads to the phone and once started works great. I then unplug the phone and the wallpaper keeps working for approximately 24 hours. It then slows redrawing dramatically then displays nothing - I can't even load the settings page!
Anyone have any ideas why? Do I need to do a compilation outside eclipse? I've got the source on Google code which i'll add a link to once I can get on pc (typing this on phone).
Thanks.
Source is here: http://code.google.com/p/shapelivewallpaper/
Okay I think I know why..yes you need to modify some code, see:
Richard Green's GLSurfaceView adapted for LiveWallpapers
That should fix the problem, I use the code myself with no problems.