Jump to content

Sven Killig

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sven Killig

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Location
  • Your Current Device(s)
  1. Oh! Reading the syslog, I had the impression you got ID pin detection based OTG working with the stock kernel driver.
  2. This only works for Texas Instruments OMAP based phones with the musb host driver.
  3. I had the impression that it still charged, but am not 100% sure either. I think it switched between booting boot.img/recovery.img
  4. I can't discover what source code files I need to modify/exclude to build a kernel without memory bus overclocking at stock speed.
  5. Thanks :) How do I disable this memory bus overclocking at stock speed?
  6. I wanted to do a fork on github like I did on the Nexus One, but I'm confused what kernel tree the definite one would be.
  7. I think it should work. But keep the notes on my Nexus One page about missing power in mind. I use this cable.
  8. In principle all devices that Linux supports can be connected. But depending on the device, one may have to either use a Debian overlay or write a bridge to the Android framework.
  9. "XCD 35 open source code for Android Eclair" → Android 2.1 → kernel 2.6.29
  10. The Blade is charged by the hub. I updated the modules archive to include USB audio drivers.
  11. I just wrote down the differences to my page for the Nexus One. There you can find more details.
  12. I made it :) Details for USB host mode on my website.
  13. I come from the Nexus One and am used to try out a kernel with fastboot boot Z:\ZTE_Kernel_Eclair_General\arch\arm\boot\zImage but that doesn't seem to work on the Blade (black screen). Is it supposed to work or how is it done on the Blade?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.