My profighter runs fine on my current phone(a bit slow).for older phone,it display”application error,the connection to the server was unsuccessful.(Https://localhost/index.html)”behind is the EULA agreement.is there any remedy?android apk.
What does the Android remote debugger show?
First thing first.i would like to trim my project and see if it works properly.best rdgs,tst
My intuition tells me that,if the nsb HTML engine waits for 10 more sec,my app would load fine.first ,the splash screen display,then after 24 sec,err msg display(server connection..)(my point of view,app still not loaded yet).after that,around 8 sec,the EULA agreement appears behind the err msg(server connection).could the nsb HTML engine waits for 10 sec more,that is,a total of 34 sec waiting time ,until my app loads,better still,display the splash screen for 34 seconds.thanks in advance,tst
My tab ,23 sec ,before error msg (server connection..),29 sec ,after which EULA display.hopes my feedback helps..my html files runs fine.my own issue is speed,old or new phone,apk or html runs slow.the real issue comes when my plane starts firing(slow).
The best advice is still to hook up the Chrome Remote Debugger. You will see the full error messages.
These are the official docs for remote debugging.
In my case I had to install the Samsung ADB Drivers from Samsungs website. The phone would show up in Chrome Debugger without those drivers but my NSB app would never appear with its little ‘Inspect’ button otherwise just like your screen shot above.
From the official source if you like:
https://developer.samsung.com/android-usb-driver
-FRC
Take note:this is exe file
#frc ,sorry for my stupid mistake,forgive me being too careful.in george sub link ,I found that it is downloading the same exe file.hopefully,it hasn’t dampen your enthusiastic in helping others in this forum.once again ,sorry,tst
Finally,success.figgle with adb.found that I have to load web app on device .running apk on device won’t work.but my original concerns was error starting the apk.below are 2 errs on my web app
Let’s address the first one: It seems like your app starting playing sound as soon as it starts. Google requires apps to have some interaction with the user before that is done. You can imagine how annoying it could be for an app to start playing sound before the user has done anything on it.