I'm using systrace to find and solve my frozen frame issues.
and I see this methood, It seem like it called by android framework while initialising.
Related
So I'm staring at this image trying to figure out how to actually look at my app...
I just updated my IDE to 1.5 and now none of my projects render a visual representation of their layouts.
I've tried restarting the application, checking for updates, restarting my computer, making sure my SDKs are all in order, but without fail upon startup I am treated to a pleasant view of nothing.
I've tried the solutions listed here and here but nothing has really worked. I don't see a sort of rendering log or even alerts of bugs.
Any ideas?
I had to re-install pretty much all of my SDKs, but I was finally able to get the layout to render again.
All was well until very recently when I noticed that debugging has become very slow. I do not recall any drastic changes that would cause this.
UI Navigation has a noticeable lag and network operations take forever. This is somewhat remedied if I reboot the phone and restart Android Studio/ADB.
App behaves fine when running in normal mode.
I'm using Dalvik runtime, on Android 4.4.2. I have not used ART.
Any advice on how to address this?
Check your breakpoints in Debug bookmark (button "View Breakpoints"), if there are many breakpoints which you forgot delete in the past this may slow you debugger. In my case deleting all breakpoints fix the problem.
I had such an experience before and it was due to a custom library that I had attached to my project, I still don't know how these two were related but after removing the library it worked like a charm.
See what has been added to your project recently, maybe it help you too.
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)
Recently upgraded to the AIR 3.1 SDK and have run into a show stopping issue regarding InvokeEvent on mobile devices. The application is dispatching a new InvokeEvent each and every time you change orientation on the device. And it isn't clearing the "queuedEvents" array. Worst of all, the new event it dispatches each time is a clone of the last one recieved. In the case of our application, this would be parameters that tell the application to load certain data. So each time you change orientation, the application re-triggers that load sequence, causing lots of undersirable behavior.
The code is pretty simple to test out:
protected function preinitializeHandler(event:FlexEvent):void
{
NativeApplication.nativeApplication.addEventListener(InvokeEvent.INVOKE, onInvoke);
}
protected function onInvoke(event:InvokeEvent):void
{
trace(event.toString());
}
Now each time you change orientation you will see the trace statement and the event.target.queuedEvents collection continues to grow while never clearing any of the previously caught events out.
Rolling back to AIR 3.0 fixes this behavior. And I've been able to demonstrate that in two separate projects.
I'd love to hear of a fix or work around so we can release using 3.1, but either way, I thought I'd make others aware of this issue as I haven't been able to find anything about it through my searching.
For additional details on hardware: This doesn't occur in emulator or my LG Slate, but it does happen every time on both of our Xooms and our Samsung Galaxy Tab. It doesn't appear to be an issue with iOS.
UPDATE: Just updated to the 3.2 release candidate (3.2.0.2060) and the problem remains. Our software wont be able to update past 3.0 for the foreseeable future, which means we can't upgrade to Flex 4.6 SDK either, not without removing a significant feature of our application. This doesn't inspire us to the future of AIR in our company.
There are a few solutions and work around we might be able to employ to fix our specific feature, but there is still a concern over the effects of having an ever ballooning invoke queue that never clears. That could have additional issues over extended use of the application.
UPDATE 2: I put more details in the Adobe forum post. http://forums.adobe.com/message/4278518
Eric Jensen
As the titles state, I can't drag widgets onto the screen. Attempting to do so simply produces a dashed outline, but the widget isn't added. Different widgets cause differently-sized outlines to be created, so the application (Eclipse) is recognizing my input to some degree. No errors are produced either.
I've found no documentation on the drag-and-drop UI approach, probably because it's supposed to be self-explanatory (I had no problems doing the same thing on Qt, for example). Also note that I've gotten a basic "hello world" program working, both on an emulated device and on a smartphone.
I tried uploading a picture illustrating the problem but as I am a new user I don't have the permissions to do so.
EDIT: Well restarting Eclipse fixed the issue, though I still don't know what caused it.
Well restarting Eclipse fixed the issue, though I still don't know what caused it.