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)
Related
I just launched my game on Google Play, it works fine on Android devices, but if I try to boot it though Bluestacks emulator the Unity splash (sometimes) shows and after that only a dark grey screen and nothing happens
This is how it looks after the Unity Splash intro
I have tried to install the game though Google Play and by installing the Apk file itself, both ways dont work.
I'm using v2021.1.18f1 to build the game
The game itself is here https://play.google.com/store/apps/details?id=com.BrokenGlass.TapNinja
Thank you.
UPDATE
I fixed it by changing a lot of settings in the Player Settings, not sure which is the one that actually made it work. Raguels answers was partially correct, but changing only the Graphics API did not work.
This is how my Player Settings look
It is happening because you didn't include some of the supported graphics API in your android build. Bluestacks might not work if you omit OpenGLES2. Make sure you have OpenGLES 2 in your supported graphic APIs. You can find it in Project Settings/Player/Other Settings
To make it available, you will have to change the Color space from Linear to Gamma.
For me worked changing "Optimized Frame Pacing" to disabled, in Proyect Settings/Player/Resolution and Presentation
Background
I have a live wallpaper that uses the relatively new API (from Android 8.1 - API 26) to request the OS to use customized colors:
https://developer.android.com/reference/android/service/wallpaper/WallpaperService.Engine.html#notifyColorsChanged()
https://developer.android.com/reference/android/service/wallpaper/WallpaperService.Engine#onComputeColors()
The problem
On Android 8.1 and even on Android P DP1, all worked fine with these functions, as they did what normal wallpaper do with the colors, affecting the notification drawer if the color that was chosen is dark enough. Here's a comparison between choosing a non-dark color and choosing a dark color background:
Thing is, on Android P beta (DP2), even though this function get called, it doesn't do anything, ever.
To test it on your own, you can try the full project I've published here.
What I've found
I thought that maybe the API has changed, so I've tried to find which functions are available, but I couldn't see anything that's new.
I've tried to use various ways to return the customized colors:
a. WallpaperColors(Color.valueOf(0xff000000.toInt()), Color.valueOf(0xff000000.toInt()), Color.valueOf(0xff000000.toInt()))
b. WallpaperColors.fromDrawable(ColorDrawable(0xff000000.toInt()))
c. WallpaperColors.fromDrawable(BitmapDrawable(completelyBlackBitmap))
d. WallpaperColors.fromBitmap(completelyBlackBitmap)
Sadly none worked (fromBitmap is the one that works well on Android 8.1).
Seeing this, I've re-checked that my code is ok, and noticed that the built in live wallpaper works fine, and that selecting a solid black wallpaper (instead of live wallpaper) also affected the UI of the OS.
Seeing that it works with built in apps, I've reported to Google about this issue, only to find out that they don't understand what I'm talking about, and each time I've tried to tell them they've misunderstood it differently:
https://issuetracker.google.com/issues/79404938
https://issuetracker.google.com/issues/79665215
https://issuetracker.google.com/issues/80029770
I wanted to make sure it's not an issue with just my app, but with others too, so I've tested Muzei live wallpaper app, which is actually made by one of Google's own developers. The issue indeed occurs there too, while working fine on Android 8.1.
I was just curious, and wanted to check if the issue could occur if I've moved Muzei to be a system app, but after doing so, I've seen the issue still exists.
The questions
How come it doesn't work anymore?
Is there a workaround/fix for this?
Why does it work fine for built in apps and for normal wallpapers, but not for third party apps? I don't think their code is any difference.
OK, Google confirmed it's a bug, which will be fixed on later version:
The development team has fixed the issue that you have reported and it
will be available in a future build.
And, it works fine now on DP4 (beta 3) of Android P.
I've built an html5-video webpage that uses video-js and its chromecast-plugin. When I use the resulting cast button on video-js player's control-bar, when running on Chrome-browser on Android, it fails to completely transfer over to the TV's screen. The failing symptom is that only a large blue cast-icon is visible in the center of the TV screen. It fails on Android, each and every time I try it. (My Android is version 7.1.1, on a Google Nexus-9 tablet.)
And when it fails to completely cast over to the TV, the cast-icon-button on the video-js control-bar turns red, which I assume means that the chromecast-plugin 'knows' that it failed. (The videojs-chromecast-plugin is version 2.0.8)
My chromecast device is a 2nd-generation chromecast-dongle from Google.
[ From a PC-platform, the video-js chromecast-plugin's cast-button works perfectly every time. That PC-platform is Windows-10, using the newest version of Chrome browser (Version 63.0.3239.132 (Official Build) (64-bit)) ]
So, could someone with Android and a chromecast device please test my
webpage and report whether it works or whether they too fail with a large
blue cast-icon image in center of their TV-screen.
(Note: I've googled for symptom of the blue cast-icon in center of TV, and
find various reports of this exact symptom, on various platforms. But
none of those problem posts ever end with a solution, so I've concluded
that this is a known open issue.)
My webpage that is failing is located here:
https://weasel.firmfriends.us/HTMLVideoFromCloud/
[ You can see the page's html and javascript via "view page source"
in the browser (right-click anywhere on the page, outside of the
video-js viewer) ]
(EDIT#1) Ok, some extra clarification: The problem casting from Android happens ONLY when I use the cast-button at right-end of videojs-viewer's control bar.
But, I have found an alternative cast-button on Android, that CAN successfully cast my page to the TV. I don't recall exactly what I did to get this extra button to start appearing, but it will appear for a few seconds in the upper-left client-area of the video-js player window rendering my webpage. This 'workaround' doesn't completely solve my issue, because the goal is to get videojs-chromecast-plugin's cast-button to work. Also, other people viewing the page from Android may not know how to get that alternate cast-button.
(EDIT#2) I've tested now from two different tablets...both fail.
(1) Android version 7.1.1, on a Google Nexus-9 tablet
(2) Android version 5.1.1, on a Google Nexus-10 tablet
TIA...
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
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.