简体   繁体   English

Appgyver类固醇启动画面的持续时间

[英]Appgyver Steroids splashscreen linger duration

Before I knew the existence of AppGyver Steroids, I was building an app with PhoneGap, everything was going on smoothly. 在我知道AppGyver类固醇的存在之前,我正在用PhoneGap构建应用程序,一切都进行得很顺利。 Recently, I tried to use AppGyver Steroids to build my app, so I ported the project from PhoneGap to Steroids following the official guide found on the web. 最近,我尝试使用AppGyver Steroids来构建我的应用程序,因此我按照网络上的官方指南将项目从PhoneGap移植到了Steroids。 I could successfully debug my app on my MacBook afterwards, no problems at all. 之后,我可以在MacBook上成功调试应用程序,完全没有问题。

I have created an app with AppGyver Steroids that shows a Microsoft Bing Map with several hundred pushpins attached. 我创建了一个带有AppGyver类固醇的应用程序,该应用程序显示了带有数百个图钉的Microsoft Bing Map。 When I wanted to test it on my Samsung Galaxy S2, I deployed it to the cloud and built the apk file with the Ad Hoc version. 当我想在三星Galaxy S2上对其进行测试时,我将其部署到云中并使用Ad Hoc版本构建了apk文件。 Most of the build settings are left as default. 大多数构建设置保留为默认设置。

Later, when I install it on my device and run it, the default "AppGyver" splashscreen lingered for around 15 seconds or longer before the Bing Map showed up. 稍后,当我在设备上安装并运行它时,默认的“ AppGyver”启动屏幕会停留约15秒钟或更长时间,然后显示Bing Map。

I would like to know: 我想知道:

  • if there are any ways to adjust the duration of showing the splashscreen 是否有任何方法可以调整显示初始屏幕的持续时间
  • the reason of such a long loading time if this is not a "setting-related" issue 如果不是与“设置有关”的问题,那么加载时间如此之长的原因

I have found the same problem on a Samsung Galaxy Ace 2, running Android 4.1. 我在运行Android 4.1的Samsung Galaxy Ace 2上发现了相同的问题。 However, on a Samsung Galaxy S4 Mini, the splashscreen disappears much quicker, after around 5 seconds. 但是,在三星Galaxy S4 Mini上,启动屏幕在大约5秒钟后消失得更快。 The steroids native code is not public so it is difficult/impossible to find the source of this problem without asking Appgyver staff, but in any case they are working on a new Android client which will almost certainly fix this kind of thing. 类固醇的本机代码不是公开的,因此很难/不可能在不询问Appgyver员工的情况下找到此问题的根源,但是无论如何,他们正在开发一个新的Android客户端 ,几乎可以肯定会解决这种问题。 I think unfortunately it's a case of hang tight... if you want to try asking the Appgyver staff they are usually very responsive: http://forums.appgyver.com/ 不幸的是,我认为这是一种束手无策的情况...如果您想尝试询问Appgyver员工,他们通常反应迅速: http ://forums.appgyver.com/

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM