4 replies to this topic

[Imhotepp]

Hi

I have a problem with my OSF II (tried both fibblesan and fish & chips roms) where the sound is all garbled when I use headset profile, but the strange thing is A2DP (high quality stereo) profile works fine. Has anyone else experienced this issue? Or is it a hardware problem for my handset?


Cheers

[nre]

I had a similar issue with my Vivacity, where my bluetooth car kit would not work properly (garbled sound like you), but A2DP works fine.

I tried the other custom ROM from Seb404 and this fixed the problem (F&C rom is based on fibblesan so no surprise that it didn't help matters). Interested to hear if it works for you too...

I posted up in the FLB thread about this, but never got a response, see HERE

Edited by nre, 05 January 2012 - 02:31 PM.

[Imhotepp]

Yup, I tried Seb404's rom and it works fine, strange that all people that use FLB's rom and its derivatives don't find this problem an issue.

Thanks for the tip

[not a footballer]

Imhotepp, on 09 January 2012 - 08:07 PM, said:

Yup, I tried Seb404's rom and it works fine, strange that all people that use FLB's rom and its derivatives don't find this problem an issue.

Thanks for the tip

Identical problem here too, with a Vivacity and both a TomTom720 and a Wharfedale car radio.

I've tried the r1 version of seb404's rom (from the podtwo blog), but it doesn't fix the problem. Is this the version you used or was it the r0?

Also, when installing this rom, is it necessary to also install the stock kernel (seb404 says something about the kernel being automagically selected but it wasn't clear what this meant for the actual install - does it essentially mean you don't have to explicitly install the kernel after the rom image?).

Edited by not a footballer, 17 January 2012 - 05:53 PM.

[not a footballer]

I discovered that doing a factory reset then installing the seb404 r1 rom (I've got it now - it already contain the TMV kernel, so no need to separately install it) it was fine, but when I did a CWM restore (of a backup done under the FLB rom), the problem returned.

I realise now I just did a 'restore', not thinking - I presume that will that have just restored everything, kernel, rom (the FLB one) and the data (apps)..

I'm now back to clean ses404 rom state, I'll try restoring just the data later...