Originally Posted by neilson (Post 2031709)

Ok, so now that the camera is working and everything else seems to be working(as in, tweaks are what're needed), Bluetooth seems to be the last "not working period" function.

Can we use this as a thread to monitor and track any Bluetooth-related developments?

Originally Posted by JustusIV (Post 2032025)

Well that is alot more information then i have ever seen. So thank you.
If the OP doesn't want to turn this into a bounty thread i will.

Originally Posted by pts69666 (Post 2031752)

Bluetooth is by far not the only "not working period" function. There are quite a few actually. A short list includes:

Proximity sensor
TV Out
3.5mm Headset jack (well, it works if you don't want speaker working)
MMS
Internal Memory

Originally Posted by arrrghhh (Post 2032059)

Not to take any wind out of your sails, but a lot of devs aren't doing this for monetary benefit.

Now that doesn't mean they don't appreciate a donation, you just can't expect that giving someone $20 will guarantee that BT will work.

I guess the point of 'bounty' threads is the dev gets the money once it starts working? Now what stops people from just not donating once it is working?

IMHO, bounty threads are just not a good idea. I encourage people to donate, but don't expect any dev to feel obligated to you because you threw them $20. Perhaps this post is unnecessary, I just remember someone said they donated $100 to a dev, and 8 months later they got a new phone. So long as you don't have that attitude with donations, feel free to do your bounty thread :p

Originally Posted by JustusIV (Post 2032080)

Not to sound to selfish here but it was my attempt to steer a project the way i wanted it when i clearly lack the skills to do it any other way :P

Originally Posted by Grafton (Post 2045082)

I believe the bump app works via bluetooth, when I was booting my rodum400 as "touch pro" incorrectly the bump app worked with my brother-in-laws samsung android

Originally Posted by docnas (Post 2054001)

I had checked the irc logs repeatedly today and was feeling preety gidddy hearing cotulla say that he actually was porting it over according to the last thign i read from him he was able to get tetris working :P
On top of that we have viruscrazy saying he had gottten bluetooth working and to top it off it seems ACL Natemcnutty and Lmiller seem to be on the cusp of getting nand to work so it was preety exciting today ...

Originally Posted by JustusIV (Post 2066864)

This is a shameless bump. Anyone have any more information on Bluetooth?

Originally Posted by arrrghhh (Post 2066865)

It doesn't work yet, and it's one of the hundreds of things devs are trying to fix.

Originally Posted by JustusIV (Post 2066999)

Yeah i am aware it doesn't work yet :( I am also aware the devs are working on a lot of stuff and am grateful for everything they do. Was just hoping for any information. I have seen mention of BT a few times reading through other post but was just wondering how it was coming along.

Originally Posted by arrrghhh (Post 2067093)

jb is working on it semi-privately... Seems like he might have the interface up and it pairs, but it doesn't route audio correctly, which we knew would be an issue because the sound code is a hacked-mess. They're completely rewriting it for .35, so it should be a lot cleaner - BT may have to wait until then anyways, as it'll be much, much easier to troubleshoot/resolve issues on sound routing.

If jb does start a public thread like he did with cam, I will certainly repost it here if someone doesn't beat me to it :p.

Originally Posted by JustusIV (Post 2067109)

You da man! and JB the man! :)

what is .35? the jack?

Originally Posted by JustusIV (Post 2067109)

You da man! and JB the man! :)

what is .35? the jack?

Originally Posted by JustusIV (Post 2067222)

Thanks for the info. Learn something new every time i come here. :P

Originally Posted by Jerome

Hi,

Some of you already know that I was working on Bluetooth for the rhodium these days. It's now working at full speed (4Mbps) and I've been able to make a call using a BT headset (need to make a last test to check that both uplink and downlink works, right now, I made test by calling voicemail).

In the mean time, I've made my diamond to work at full speed and make a call to my voicemail through the BT headset (also need to test in both ways).

Please find attached the 3 patches required for bluetooth on rhodium (well, these patches are only the kernel side patches, I will do the patches for the userland side).

* For the brf6350 bluetooth modules (diamond, raph, ...), there only a small change to do in the rootfs :

in /init.cfg/init.froyo.rc (or init.gingerbread.rc, but haven't tested because not yet switched to gingerbread), change the following lines:

service hciattach /system/bin/hciattach \
-n -s 115200 /dev/ttyHS1 texas 115200 flow

with :

service hciattach /system/bin/hciattach \
-n -s 115200 /dev/ttyHS1 texasalt 4000000 flow

(need to use texasalt to load the firmware file bcm6350.bin already present in the image).

Regards, Jerome

Originally Posted by arrrghhh (Post 2067356)

Alright, one of our amazing devs (the same that brought us the camera, viruscrazy aka Jerome) has sent an update via the mailing list. I am reposting it here, verbatim.

Originally Posted by fishingmedic (Post 2067370)

Sweet!! thanks for the update. Now is this something we're going to need to wait for a commit on or will he release a test kernel like he did with the camera kernel?

Originally Posted by arrrghhh (Post 2067416)

Kernel code is done, just needs to be committed. Userland changes need to be made, then it'll be good to go ;).

Originally Posted by proxhack (Post 2067384)

Holly Crap...I am going to be rich, no more tickets for driving and talking on the phone!

Originally Posted by neilson (Post 2067920)

Any chance that we with Rhodiums can help test this BT fix from Viruscrazy? I have a new Jawbone Era and if I had working BT on Android, I'd be using that permanently instead of Windows Mobile.

Originally Posted by ndno (Post 2067587)

Very good news there! Maybe my picky co-worker will try out android now; all he cares is having BT work under android.

Originally Posted by neilson (Post 2067929)

Very true, and well said. I willingly made the choice to spend $130 on a headset and that was my decision. The fact that BT is on its way to working is a bonus, but it's not like my buying a headset had any impact on the BT working on Android either. I'm a patient man, and in fact will hold off on upgrading to an HTC Arrive since Windows Mobile(and Android) suit me just fine right now.

Originally Posted by arrrghhh (Post 2067939)

Patience it is then.

Hopefully jb has something more public soon - it's not working yet for him, so there's no point in releasing it for testing.

Also, as I understand it... this fix is going to apply to both types of chipsets, so there's really no reason to test it for every device like cam - it should "just work". Time will tell ;).

Originally Posted by JustusIV (Post 2068111)

This is the greatest news i have heard in a long time.
I would like to buy someone a beer/coffee.
Jerome
Arrrghhh

Anyone else need one?

Originally Posted by arrrghhh (Post 2068120)

I'll just pass your donation right on to the XDAndroid project... I don't really do much for the project other than try to help test and support end-users ;).

You can certainly donate to Jerome as well, I'm sure he won't mind :D. I can dig up his PayPal details if you wish, I can't readily find them.

If you do donate to the XDAndroid project, that money does get spread amongst devs. I know that a good chunk is going to be offered to Jerome, assuming we can get a hold of him :p.

Originally Posted by arrrghhh (Post 2067927)

The fix has already been sent for commit. Need to fix userland, because without it the kernel fix is useless. Please, be patient.

Originally Posted by JustusIV (Post 2072063)

I don't really know where else to check but this thread. I am being patient just curious about any status changes?

Originally Posted by arrrghhh (Post 2072105)

Progress happens in short little bursts - still waiting on the userland fix, I haven't heard anything from jb on it.

Originally Posted by JustusIV (Post 2072223)

what is userland fix?

Originally Posted by arrrghhh (Post 2072225)

As in what's the fix? I don't know what it is yet - if I did, I'd be wrapping it up and having people test it!

If you mean what it is in the more general sense, it just means that the fix needs to take place in the Android system - system.ext2 aka 'userland' instead of the Linux kernel - zImage - kerneland (no one calls it that :p).