I dont need nor have i used one, but here's some help.
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
It appears that Android 2.0 will have RFCOMM support. Please see the following like for details.
Hello, has this problem ever been fixed?
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X'
Am now in exactly the same situation.
I did try having a play with the hardware acceleration options in LinuxMCE Admin, but it didn't seem to make any difference.
May I also say thanks for all of the help so far. Am trying to add relevant information to the wiki as we go.
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X' I searched the forum for this problem and found a lot of threads about this problem. I've tried a number of possible solutions like manually installing the latest Nvidia driver on the MD but I get stuck with the same message again. Maybe I should mention that my Core has no Nvidia graphics card (it's an Intel MB with onboard graphics) because I'm not using my Core for video playback. I tried this thread http://forum.linuxmce.org/index.php?topic=8460.msg56517#msg56517 and it worked fine but when I tried the 'dpkg-reconfigure -phigh xorg-server' it says: /usr/sbin/dpkg-reconfigure: xorg-server is not installed. Again I searched the forum for this but can't seem to find a solution.
I've got so far so i really would like to get to the AV Wizard. Any suggestions?
Thanks for the help so far
it seems the Android stack has its own unique problems, particularly that the phone itself cannot be an RFCOMM server, which is required by our bluetooth code.
I don't believe the next round of updates have been built yet.
tschak: if this is really a regression, it has to be fixed asap. We can't trash existing stuff with new patches. And just as a note, that hid stuff should not really be handled in orbiter.