Is there any way to ditch Sense without losing BT audio?

[Guest milko9000]

If I use LauncherPro as default Home on the latest Modaco pre-release 2.1 build, I can't get my BT car doohickey to work. It pairs OK but it won't actually connect at all. If go back to Sense and reboot, presto BT audio again! But it's not as pretty* :)

If I don't set LauncherPro as default Home but then switch into it (ie Sense gets loaded too) then the BT audio connects fine so I guess there's something important in there. Can anyone think of a way to get around this?

(*and it really irks me that it wastes a whole button to add widgets and shortcuts to the page! Honestly, so dumb)

[Guest stevenz]

If I use LauncherPro as default Home on the latest Modaco pre-release 2.1 build, I can't get my BT car doohickey to work. It pairs OK but it won't actually connect at all. If go back to Sense and reboot, presto BT audio again! But it's not as pretty* :)

If I don't set LauncherPro as default Home but then switch into it (ie Sense gets loaded too) then the BT audio connects fine so I guess there's something important in there. Can anyone think of a way to get around this?

(*and it really irks me that it wastes a whole button to add widgets and shortcuts to the page! Honestly, so dumb)

The launcher has nothing to do with Bluetooth, it's coincidental.

[Guest milko9000]

Then it's an amazing coincidence don't you think? I rather suspect it comes with some files/settings/inits/whatever that are required. Turn off Sense and reboot - BT fail. Turn it back on and reboot, BT back again. Try it!

[Guest masterpfa]

If I use LauncherPro as default Home on the latest Modaco pre-release 2.1 build, I can't get my BT car doohickey to work. It pairs OK but it won't actually connect at all. If go back to Sense and reboot, presto BT audio again! But it's not as pretty* :)

If I don't set LauncherPro as default Home but then switch into it (ie Sense gets loaded too) then the BT audio connects fine so I guess there's something important in there. Can anyone think of a way to get around this?

Success!!!! ;)

Radu, over at XDA-Developers, has an AWESOME Vanilla based ROM that now has working A2DP, the one thing that many people had been complaining about with AOSP/Vanilla ROMS.

I have been using his ROMS from since he first started developing ROMS and Radu, along with the community, has developed 2 great Custom Roms

VanillaEclair 4.0 for all flavours as long as it's Vanilla and

ChocolateEclair 1.0.1 for those who prefer sense.

Have a look, both workable and fully useable as daily ROMS :(

He has also posted a FIX for developers, if you know your way around a ROM this may work for you.

Edited June 18, 2010 by masterpfa

[Guest milko9000]

Thanks masterpfa, I read that too this morning! I'll have to give one of his ROMs a go... or wait for Feeyo to release 1.7.1... or wait for the next Modaco build. Too many roms!

[Guest mrliam]

If you go into Applications > HTC Sense > Clear Defaults

When you press the home button, it will give you the choice to go to "Home" or "HTC Sense".

If you select "Home" and choose that as your default, you will get to discard HTC Sense and still use Paul's new ROM.

A decent option?

[Guest klutsh]

A2DP is now fixable in AOSP rom's: http://forum.xda-developers.com/showthread.php?t=704976

[Guest milko9000]

If you go into Applications > HTC Sense > Clear Defaults

When you press the home button, it will give you the choice to go to "Home" or "HTC Sense".

If you select "Home" and choose that as your default, you will get to discard HTC Sense and still use Paul's new ROM.

A decent option?

Yeah, that's what I was doing (well, with LauncherPro not vanilla Home) but it was killing A2DP for me - could no longer connect to the headset despite happily pairing. Looks like it'll be fixed now though, since all the roms on XDA are catching up with RaduG's fix.