Bluetooth and Android?

[arrrghhh]

Originally Posted by neilson

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.

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

Honestly, these posts that say 'I won't use Android full-time until X works' are pretty dumb. No offense, but it's not like we're getting a commission on how many people run Android full-time. We don't really care if everyone runs it full time, or just uses it for fun/part time. You could use it 24hrs/day, or 1hr/day - makes no difference to us.

Originally Posted by ndno

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

My co-worker said the same thing. I just told him... his loss .

[neilson]

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.

[arrrghhh]

Originally Posted by neilson

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.

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 .

[neilson]

Originally Posted by arrrghhh

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 .

Time, Love, and Tenderness indeed. #michaelbolton'd

[JustusIV]

Originally Posted by arrrghhh

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

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

[arrrghhh]

Originally Posted by JustusIV

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

I will update this thread if I get any additional information.

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

Plus, the kernel code he committed seems to cause issues with sleep... So definitely some kinks to iron out.

[JustusIV]

Originally Posted by arrrghhh

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

what is userland fix?

[arrrghhh]

Originally Posted by JustusIV

what is userland fix?

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 ).

[JustusIV]

Originally Posted by arrrghhh

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 ).

Yeah i meant the more general sense. Thank you for giving me a little insight.

[drewcam888]

anyone heard of an update on userland bluetooth fix