Reply
Thread Tools
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#1
I use bluetooth sparingly, maybe once or twice a month, so I am not 100% certain about when it stopped working.

Anyway, I had overclocked the cpu to 900 mhz using kernel-power in extras-testing and was fine-tuning voltages, reading the overclocking thread, I decided to check in terminal "dmesg | grep error" to find any cpu related errors and the output was "[ 124.260314] hci_h4p hci_h4p: FW error", 3 minutes and some googling later, I found it to be related to bluetooth. So I decided to activate it to pair the N900 with some bluetooth headphones and it just didn't work, no icon, no nothing.

Right now, I've reflashed the device and the error is presistent. No bluetooth for me.

output from "dmesg | grep hci_h4p":

Code:
[       5.895874] hci_h4p hci_h4p: Registering HCI H4P device
[      15.893157] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[      16.269866] hci_h4p hci_h4p: Valid bluetooth address not found.
[      16.269927] hci_h4p hci_h4p: FW error
[      16.269958] hci_h4p hci_h4p: Sending firmware failed.
output from "dmesg | grep Bluetooth":
Code:
[      15.793151] Bluetooth: L2CAP ver 2.13
[      15.793182] Bluetooth: L2CAP socket layer initialized
[      15.887634] Bluetooth: SCO (Voice Link) ver 0.6
[      15.887664] Bluetooth: SCO socket layer initialized
[      43.842132] Bluetooth: RFCOMM socket layer initialized
[      43.842193] Bluetooth: RFCOMM TTY layer initialized
[      43.842224] Bluetooth: RFCOMM ver 1.11
Any help would be appreciated.
 

The Following User Says Thank You to azstunt For This Useful Post:
Posts: 3,664 | Thanked: 1,530 times | Joined on Sep 2009 @ Hamilton, New Zealand
#2
fw =firmware error?
 
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#3
Originally Posted by maxximuscool View Post
fw =firmware error?
That's my guess. It's what it says.
 
Posts: 3,664 | Thanked: 1,530 times | Joined on Sep 2009 @ Hamilton, New Zealand
#4
Originally Posted by azstunt View Post
That's my guess. It's what it says.
try reflashing it. it might help. if it doesn't then it must be hardware failure.
 
Posts: 20 | Thanked: 4 times | Joined on Nov 2009
#5
What was the outcome of your bluetooth chip? have you solved the problem or it was an hardware fault? I have the exact same problem and I am still investigating if it is or not an harware fault (but the more time I spend investigating, the more I think so...)
 
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#6
Originally Posted by yupa View Post
What was the outcome of your bluetooth chip? have you solved the problem or it was an hardware fault? I have the exact same problem and I am still investigating if it is or not an harware fault (but the more time I spend investigating, the more I think so...)
I believe I may have fried the bluetooth chip and so it is a hardware problem.
 
Posts: 9 | Thanked: 4 times | Joined on Aug 2010
#7
Originally Posted by azstunt View Post
I believe I may have fried the bluetooth chip and so it is a hardware problem.
Hi did you find out if this was a hardwared failure. im also getting the same error. I have tried all flashing types but no luck. I think it had something to do with the fact that after one of my previous flashes my phone version showed as 0000.
 
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#8
Originally Posted by rwnoob View Post
Hi did you find out if this was a hardwared failure. im also getting the same error. I have tried all flashing types but no luck. I think it had something to do with the fact that after one of my previous flashes my phone version showed as 0000.
I have found no solution so far. I still think that it is a hardware failure. I also had that phone version in one of my previous flashes, it didn't allow me to reflash... I had to manually change the version in order to do so. I guess you had to do the same.
 
Posts: 9 | Thanked: 4 times | Joined on Aug 2010
#9
Yes i had to do the same. I ran some tests with xterm after lots of googling. It seems though that the hardware is there but there is no firm/software in the blutooth folder. But i guess i will send it in as i dnt think I will get a fix for this.

Thanks Bud
 
atilla's Avatar
Posts: 1,210 | Thanked: 597 times | Joined on Apr 2010 @ hamburg,germany
#10
if you guys really fried your bluetooth chip with overclocking you shold post this in the overclocking thread.
maybe you are one of the first who fried your phones
__________________


Nobody likes us but we dont care....
 
Reply


 
Forum Jump


All times are GMT. The time now is 09:36.