Hello I have a problem and so searched all over the internet , not the solution have a motorola xt890 with intel chipset , it happens that the appliance after an automatic update made by him to be turned off and on again , it does not start Android and not even in fastboot mode, have sought various solutions and came to the conclusion that not a way to rewrite the abarelho boot sector that would allow entry into fastboot mode and thus make the device recovery! I wonder is there any way to save the Xt890 motorola that only displays the message "code corrupt system required" Forgive me for my English google translate! I'm from Brazil .
I have a Asus Memopad 7 ME176CX with 64 bit Architecture and i want to develop but the driver on the Asus suppport page doesn't work and the driver on the Intel doesn't work either.
If someone have an idea or the solution, thanks!
This is an already solved problem, but I thought I leave my story here so others won't have to spend as much time debugging as I did.
HAXM 1.1.0 is not loading x86 atom image on fresh Yosemite install (core 2 duo): it goes straight to a black screen.
I can run ARM images, but when I try to run an Atom x86 image (android 4.4.2, nexus 5 clone), it goes to a black screen and sits there doing nothing. The emulator output reports "HAX is working and emulator runs in fast virt mode" before going to the black screen emulator window.
Never had an older version of HAXM installed, so don't think its the "old haxm verison doesn't work on mavericks/yosemite" problem.
Why i cannot install usb to my win 8.1? a message "This OS is not supported: Windows"
My computer is DELL.
Hi Does anyone have information on how to get access to the Android smartphone hardware development program and reference material information?
We are a startup in the process of evaluating chipsets and wanted to have the intel reference design as an option.
Online, there only developer reference is software related.
I am successfully using vaapi on Intel linux machines (haswell i5) to decode h.264 video and display in an x window. I have ported this code to a native application on android 4.4.2 r1 ia1.
The decoding works as I can convert a frame to rgb and copy the bytes onto the native window, when I use vaPutSurface it returns 0 but nothing appears on the window. I do however get the 2 following lines of log output
11-18 16:52:45.396: D/MOS(9725): mm:Mos_InitInterface_Linux called
11-18 16:52:45.396: E/MOS(9725): Mos_InitInterface_Linux: Unable to initialize context