I have used Web Audio API followed the tutorial on HTML5 Rock. I have added one audio context with 11 tracks of mp3 files, each file plays about 5 min.
This app works perfectly fine before I accidentally update my chrome to 26.0.1410.64m (PC version). In this new version of chrome, this app crash everytime with no exception.
However,the app can work fine in the latest MAC version of chrome. And if I load smaller mp3 files (5 track that each play for 1min) to latest version of PC chrome, nothing goes wrong. I have tried to fully uninstall the latest version in my win8 PC and install early version of chrome, the problem still exists.
Anyone has any idea about this problem? It really freaks me out.
Related
I created a new empty project, switched platform to Android and started Build and Run. But when it comes to "Copying APK File to device" it just freezes and I have to restart Unity.
I installed Android SDK & NDK tools just before that (through Unity Hub). Android Build Support was installed by me manually a while ago so it was visible as installed in Add Modules window. I did not do any changes to the project. The most interesting thing is that the apk is built in my Builds folder. Not sure if it works though.
I am using Unity 2019.1.0f2. The device Android version is 9.0 (API level 28) and the minimum API set in Player is 16, so the problem should not be with API.
Does anyone know possible reasons for it?
Try to turn off the following setting on your android device.
Settings -> Developer options -> Monitor apps installed by ADB
This setting(if turned on) will ask a verrification if you want to install the app. It feels like this cuts off the connection with unity which causes it to get stuck.
Unplugging and replugging the device seems to work aswell. In case of big projects this is anoying tho since if you are to quick it will just say it lost connection and it will ask if you want to reconnect, which in turn causes the same problem.
This is the only answer that worked for me:
https://answers.unity.com/questions/1248123/build-run-apk-freezes-on-pushing-content-only-one.html
In short, Player settings -> Publishing settings -> Split application binary
First of I would ask you on what computer did you run this on? (performance wise)
Second you can just copy the .apk file to the phone and install it there. If you got to where it prompts for copying to android your apk file is fine and built.
I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.
I am trying to support my webapp on the Nexus 7 using Chrome.
I tried installing the android SDK, and creating a avd like the Nexus 7 with the Google Tools, and after waiting 10 minutes for it to boot up, I found no Chrome, and an emulator that is so slow that it is completely useless. (I am testing a video app, and this thing cant decode a video in real time)
I have done all my iOS testing with the device simulator, and it works well.
Do I have some setting wrong that is causing problems, or am I just wasting my time?
The emulator might be okay for Android applications, but for web applications, you're probably going to need the real thing.
Even the recent Emulation options in Chrome 32.0.1700.76 m, do not match the same rendering on an actual Nexus 7.
I was debugging blackberry apps from Eclipse. It works fine at the beginning but since some days ago, I could no longer get the app onto any emulator or device.
The packaging and signing shows NO error. After it displays the "debugger attaching..." screen, I could not find the app anywhere on the emulator or device. I have tried to reinstall the eclipse and JDEs a few times. One observation is that it had about 280 files to sign. Without any changes in the code now it has 540 files to sign.
I want an android and iphone emulator to run on windows to test my gwt application on windows. can someone point me to a proper emulator because i've been trying some with no success
The official iPhone simulator does not run on Windows. Seems you have to get a Mac ;-)
However the Android emulator can be installed pretty much anywhere:
http://developer.android.com/guide/developing/tools/emulator.html
If you point the Andorid browser in the emulator to your GWT application you should be able to test it. You can find messages from the browser in LogCat, watch out for the logging tag WebCore. You can even log from within your code and get the output in LogCat, see:
http://developer.android.com/guide/webapps/debugging.html