cesisco's Forum Posts

  • Thank you guys.

    I think It's important that we can collect a bigger list of devices that can run the HTML versions smoothly but can't run the APK properly, so their engineers can test on the actual device.

    This was stated by a chromium project member, and probably not everyone is aware of:

    "WebView's rendering pipeline is not the same as Chrome's and is likely to be slightly slower in general on any device. Because the way it renders is different, it may provoke different behaviours/optimisations/bugs/etc from GPU drivers as well, which may also affect performance. If we have a reproducible case where there's a large difference we can investigate further."

    So, that could be the final explanation for the bad APKs performance, but like he said( and Artpunk too) their Pixel devices can run the APKs smoothly, so I think it's still relevant to collect the information about the devices that can't run the APK well so they figure out the performance difference.

    And for me it's not that obvious why a Pixel device performance would be so much better than a medium-range Samsung Galaxy

  • Hey tarek2 thanks

    The bad performance was there before I included the texts, so I included them to give me clues on the bad performance ;)

    But  you are right I can replace for Spritefonts

    Just to clarify, I need the info about the devices that run the APK poorly, but can run the HTML version smoothly, to figure out why is he difference so big. In your case it runs poorly on both.

  • On my test Runs really really bad instead of just stutters it does big jumps lugging:

    Galaxy S8

    SM-G950F

    Android 9

    Render: webgl2

    Not sure if this is normal but why does it print info like:

    AppleWebkit/537.36

    Safari/537.36

    etc...

    When the phone is a Samsung Android

    Aslo, the Web version runs quite badly on the same phone so I'm not sure if this is just a problem with the APK or the whole Android, as both run the same (APK & Web)

    Thanks for the feedback.

    That info is the user agent.About the Web version running poorly, do you have the Chrome browser updated?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I just discovered a new thing

    I have a game made in Construct 3 which is quite big in size. It requires many processing in the background. But amazingly it runs super smooth in my android mobile.It was made long way back (around last year in September)

    And yeah, when Construct 3 was free for the jam,I made few android games and it was lagging a lot on mobile. I simply ignored it.

    Currently we are attributing the lagging issue to Android Webview. But why it is discriminating the apps made earlier and now in terms of performance? I believe that issue is in Construct 3 or something related to Cordova implementation because if Webview was at fault then my old game should had also lagged. But only new ones are lagging

    For confirmation, download any game made in Construct 3 few months before and compare the lagging in it

    I'm trying to collect the device list where the problem is reproducible, to post on the chromium issue, but what you say should be checked indeed.

  • Hello, good work you guys have put in.

    The projects that been tested do they all run fine on pixel devices?

    Also if it lagged on all the device except pixel it still a problem.

    I think the list of tested devices and OS versions should be compiled into a list and posted on the issue. This sounds like a significant issue as the mobile market is an important one. I don't own a android devices myself, but it would be nice to get the problem fixed.

    Could be helpful for the chromium devs to know so they have an easier time finding the issue if it is on their side.

    How are you guys generating the apk-files?

    I don't remember the workflow, if it is possible, try export a Cordova project and do the android wrapping manually.

    Hey Vikingvikingviking , that could be helpfull.I'm building the APK with the C3 build service.

    Can you build my example manually so we can compare? I don't have all set up to do it right now.

    Edit:Sorry, forget about it, I missed the part you said "I don't own a android devices myself"

  • cesisco Hey man you got a response on crbugs. They are asking for an example apk that shows janking on Pixel devices.

    https://bugs.chromium.org/p/chromium/issues/detail?id=1127307#c46

    I was going to suggest uploading your test APK to the chromium forum, but heres the thing. I just tested your APK on my Pixel 4a and it runs smoothly!

    I dont see any janking in your test project actually.

    Yep, and they said that the original issue on that page was working fine on their Pixel devices too...but I think it's worth posting my example anyway.

  • Artpunk CascadeGames klabundee Vikingvikingviking and any user who tested, can you list the devices where you seeing the problem, so I can list them all and post on the issue, so they can test, please?

    In this format

    Device: Samsung Galaxy A20 

    OS:10.0

    Edit:Or just "Samsung Galaxy A20 (OS 10.0)"

  • Sorry klabundee I missed your post, thanks for the feedback.

    Let's start starring this issue and hope for the best

    bugs.chromium.org/p/chromium/issues/detail

  • Hi Artpunk, thanks for the feedback.

    Yep, I think it's not a good move trying to build for Android at this stage.It's mesmerizing the difference of what we can do on a computer browser with C3, and what we can do on mobile.

    I don't know if I should fill a bug report, since there are similar ones in place, or probably C3 users just should start starring those issues to draw more attention to the problem.(just 9 users starred this one)

    bugs.chromium.org/p/chromium/issues/detail

  • Hey friend,can you test this c3p file (actually I don't have active account)

    https://drive.google.com/file/d/1uAu975guxFsdfZt7zknQbdZCyKJzcbC7/view?usp=sharing

    Also share the resultant APK

    Hi, sorry dude, didn't test.The main reason of the example I made is having a very small and reproducible project to test.If the problem is present on this, it will be on any other example.

  • > > Instead of every tick,do "every 1 second"

    >

    > Hi, this is just a generic example, you can even remove the every tick and it will jank.

    Are you sure that you tested without "every tick" in APK? If yes then I would like to go in past and say something important to myself regarding game engine

    Yes off course I tested that.This particular file example is not the problem, I did this example because of the problem.

    Thanks for the feedback anyway

  • Instead of every tick,do "every 1 second"

    Hi, this is just a generic example, you can even remove the every tick and it will jank.

  • Edit:Any user who tested this, can you list the devices where you seeing the problem, so I can list them all and post on the chromium issue, so they can test, please?

    Like this:

    Samsung Galaxy A20 (OS 10.0)

    -----------------------------------------------------------------------------------

    Edit:HTML link added

    -----------------------------------------------------------------------------------

    I'm seeing a "Jank" problem when I compare the same project using Chrome mobile with the C3 remote preview feature VS an APK built with the C3 build service.

    This is not a bug report, and I'm aware of all the other threads about APKs and Webview problems, but I didn't see a simple example showing that this is not a problem derived from bad optimization or bad practices from the user, but an issue that's out of developer's control and affects all users equally.

    I took a day to test APKs on several devices, with several export options on Android 7, 8, 9 and 10, and the Jank problem still persists on the APKs no matter which render it uses, Android version or any other variable.

    I made a simple project with just a circle rotating around a pivot point, and some Debug info about FPS, device, render and user agent.

    What I'm seeing is a smooth movement on Chrome mobile, and a Janky movement on the APK even if it's 60FPS on both.

    If someone is interested in testing the Chrome mobile VS APK, and get back here sharing their experiences I'll appreciate it.

    C3 project

    https://www.dropbox.com/s/978o9vzkttl0cdm/ChromeVsApk.c3p?dl=1

    APK

    https://www.dropbox.com/s/4xlfvhdritadux2/ChromeVsApk.android.debug.apk?dl=1

    HTML

    punchytaps.xyz/bugs/janktest/index.html

    Export options on this APK:

    C3 241(latest stable)

    The project settings are all on default

    Minify mode: Simple

    Min.Version : 5.1(but I'm seeing the same problem with higher versions)

    Tested on:

    Alacatel A30 XL

    Redmi 5

    Samsung A20e

    Samsung Galaxy J5

    Tagged:

  • You do not have permission to view this post

  • faulknermano thanks for the tip, I had to do that a couple a years ago and I completely forgot about that ” hack”.

    I’ll keep you posted if I find some other clue on this.Please keep us posted as well if you have any update on this.Thanks