Michael,
Yes, /dev/socket directory exists when I boot from qi, but there is no
dbus entry under it.
I'll be able to do the log thing later or tomorrow, I don't have my FR
with me today.
And yes, Andy, I can say there's something wrong with something, not be
specific, only that using that rootfs, kernel and qi causes me problems. I
do actually like qi a lot, the boot time is so much faster.
I'll report on the actual bluetooth/headset thing at some point too. I was
able to answer a call with the button on it, which was pretty cool, but
music still came out of the phone speaker.
Thanks,
D.
On Thu, 12 Feb 2009, Michael Trimarchi wrote:
Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcelo wrote:
On Wed, Feb 11, 2009 at 5:48 PM, dave <[email protected]> wrote:
Qi sucks?
Actually, Qi rocks.
I have Qi:
$ adb shell ls -l /dev/socket/dbus
srw-rw---- bluetooth bluetooth 2000-01-31 18:00 dbus
Ah good... Dave I think you can say "Something is wrong with something"
but Qi shouldn't be able to impact the kernel bringing up bluetooth or
the rootfs creating dbus things.
It can be a problem in the kernel or rootfs that is exposed by Qi, it's
what happened with other rootfs recently with this read-only mount thing.
- -Andy
Can you increase android loglevel to 8 and send
a complete dmesg after that. The level 8 show if I remember the device
creation and the
directory creation. Do you have the socket directory under dev. That is
created by the init
process.
Michael
_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
