"Probably the best wish for a dreamer: Be underestimated", 잫읻 젤지옥루
Posted on April 17th, 2015 No comments
Huge fragmentation in Android world requires new devices to be added to local test devices who do not prefer remote device testing services. Not only there are still Android 2.x and 3.x users (for who cares about those users too), there are also variety of modified Android systems (not talking about rooting devices); almost every Android device manufacturer customizes Android for their own use and unfortunately the same Android SDK usage differs on every device (even on every model of some manufacturers).
As a result, testing RADYO on multiple devices and OS versions is a must.
Therefore here is the latest (but not the newly released) device added to test devices which are used to test RADYO.
Posted on May 10th, 2013 No comments
If you have purchased your computer with Windows 8 already installed on it and if it is a really new computer (not just a batch with operating system replaced), you may never ask a question like this.
Problem: Applications those supposed to show video/audio, can’t show video/audio ; It may stay at “buffering” state forever, either internally or exposing this status to user visually too.
Discovery: I have found this problem, it’s visible reason and it’s visible solution while my application was being released as one of the first Windows 8 applications. I have received numerous messages through the contact form of my application and Windows Store reviews related to this problem. After some investigation i saw similar messages on other media-related applications too and when i tried those applications i saw the same problem really do exist on them too. So it was not a problem caused by my application.
Reason: You (or manufacturer) have probably installed non-Microsoft made display driver. Eventhough the relation between a display card driver and an audio application may not make sense, relation really goes down to Display driver-Microsoft Media infrastructure level.
Affected products: Any Windows 8 device with an old display adapter (WDDM 1.x) operating with NON-Microsoft display driver. (certified or not)
Official solutions: None yet. That may be possible, though it has still not been fixed since the beta versions. I have informed both Microsoft (face-to-face, MSDN forums and email) and display card manufacturers (email, forums): They couldn’t solve this issue or they don’t solve this issue and/or they won’t solve this issue. This issue MAY never be solved as i started to think that this is a low-level decision made by Microsoft. I never received information related to this situation, it may be being kept as a secret because of technical or marketing reasons.
Solution: Telling you to buy a new computer is not a solution but an alternative. You can fix this problem with only uninstalling your custom display driver. If you have installed many custom-display drivers (certified or not) uninstalling once may not fix the issue as you have to revert your display driver to Microsoft’s default display driver (Windows Display Driver Model 1.x)