EarthnFire78
YAY!!! ME :)
I have updated the the IHO binary, my build comes with a newly compiled kernel that I believe has the fixes for the zv9 radio. This kernel like mrg666 is going to be only for OM-IHO.
Media fire is not working for me today. Anyone have an alternate link to download it?
Lastly, how can I confirm the v4 kernel flashed over? I see my kernel version under settings / about phone, but what should current version read? I didnt take note before I flashed.
If you've flashed the new kernel, it should read:
Kernel version
2.6.32.9-v4
bobzhome@ubuntu #1
[B]su[/B]
[B]bdaddr [new bluetooth address][/B]
[B]hciconfig hci0 reset[/B]
Media fire is not working for me today. Anyone have an alternate link to download it?
Lastly, how can I confirm the v4 kernel flashed over? I see my kernel version under settings / about phone, but what should current version read? I didnt take note before I flashed.
Set your browsers user agent to desktop and try downloading from media fire again, it works
I am going to bring up a bug that was first raised a few months ago: The hardcoded Bluetooth address: Instead of using the phone's unique MAC address, all IHO ROMs use the same fixed address of 43:25: D1:00:00:00.
@Schlidel: Since this problem exists in multiple ROMs for different phones, I would speculate there is a module in CM that needs to be adapted for each phone in order to properly pick up the Bluetooth MAC address. In that case it would be a common CM issue, but one that can only be fixed in a hardware specific implementation. Since CM doesn't officially support our phones, they may not consider it their problem.
That bdaddr_read module I mention in the IHO repository, gets the address from a Broadcom service (which I think is generic). Maybe that service returns the wrong address - or maybe bdaddr_read doesn't save the address properly for the Bluetooth daemon to pick up.
I honestly shouldn't post these speculations here. I am sure the devs are laughing or rolling their eyes over my ignorance
I am definitely not rolling my eyes. I will look into this bluetooth address issue. Let me see what can I do.
Oh heaven's yes.
Sent from my VM670 using Android Central Forums
@mrg666: You're awesome, thanks a lot. Both for your work and for being so nice about it. Seriously!
One question: Were you able to determine that it actually is the Broadcom service returning the wrong address - and not just bdaddr_read (which I believe WAS localized for IHO) that saves it incorrectly (or in a way so that dependent processes never pick it up right)?
Is there a way to call that Broadcom service straight and display (or log) the address it returns?
Just a thought, so you don't spend time replacing or fixing the Broadcom driver, only to find that it was a simple mistake in bdaddr_read.
Again, sorry if I am confusing things...