[sirius]

I too am having this problem with the upgraded firmware. I can't even get my USB cable working under 10.5.2 so have no way of iSyncing my calendar & contacts. Everything was fine until I upgraded the Nokia firmware - so I point the finger at them & not Apple.

I can't believe so many people are having this problem & Nokia have not fixed it.

[sirius]

I got a response from Nokia:

"In response to your enquiry, firmware updates on any Nokia mobile phones enhances its existing features. It neither adds nor removes any features on the respective mobile phones. In this instance, I would recommend that you contact MAC or visit the following website for information on the softwares developed by MAC:

http://www.nokia.co.uk/A4626029

With regard to the downgrade, kindly note that there aren't any options to revert to the previous firmware version.

Kind regards,

Bhanu
Nokia Care"

This is like being told, "actually, you are wrong & what you are describing is untrue." This is a total cop-out & utter refusal to accept any responsibility by Nokia.

My point is that it worked before the "upgrade" & now it doesn't...

[pinhead2008]

Wow, it's amazing how ignorant Nokia is by ignoring the possibly thousands of Mac users having problems.

iPhone here I come!

[erlewine]

Me too
time to sold my n73 and buy an iPhone.

thnks for all nokia!

[sirius]

Another response from Nokia -

"In response to your email, the Bluetooth specifications in your Nokia N73 may differ from the Bluetooth specifications in MAC's operating system. We have not tested our Nokia phones with other non-Nokia products and due to this reason, we are unable to ensure compatibility.

We suggest that you establish a Bluetooth connection between your Nokia N73 and a compatible Nokia Bluetooth device (such as a Bluetooth headset) to isolate the issue."

This is getting absurd! It worked before upgrading, now it doesn't. Why would I possibly be interested in buying a Bluetooth headset (I don't own one) to confirm that, yup, it still doesn't work with Leopard?!

[bitflung]

have you looked in the logs (Console.app) on your mac to see what is happening?

have you tried sending/receiving files with another phone, or device over bluetooth?

user: ctrl posted that his issues only cropped up after updating to macosx 10.5. 10.5 has a new bluetooth stack with A2DP built in. this may be related - can you connect the phone to other A2DP devices? i can envision an error occurring where either/both Nokia/Apple assume that any bluetooth device advertising A2DP must be an audio device (thus other bluetooth transactions may fail while passing through the bluetooth stack's A2DP layers).

if i had 10.5 i'd look into modifying the .plist's for bluetooth and see if i could disable A2DP to test this - it makes a lot of sense to me from a troubleshooting perspective. perhaps you'll even see it mentioned in the logs.

post a log snippet here if they don't make sense (i dont know how comfortable you are with the guts of your machine)


goodluck!

[eivindjo]

I have had the same problem since I upgraded the firmware to 4.0735.3.0.2. I did not have any problems at all with Leopard and the fw 3.0649.0.0.1 which was my prior fw. This is the error-message I get in Console.app when I try to pair the mac with my N73.

Mar 21 15:49:26 Glamdring [0x0-0xf20f2].com.apple.isync[1842]: 15:49:26.728 [iSync:1842] ERROR (.bluetooth.rfcomm): got immediate error at opening (openRFCOMMChannelAsync: kIOReturnError
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: Bluetooth Device Info Summary:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: svc/maj/min class: 720 / 2 / 3
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: manufacturer:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: Nokia
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: model number:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: Nokia N73
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: revision ID:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: V 05wk47v38
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: 20-11-06
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: RM-133
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: (c) Nokia.
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: IMSI:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: +CGATT: 0
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: GMM:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: Nokia N73
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: GMI:
Mar 21 15:49:30 Glamdring [0x0-0xf10f1].com.apple.BluetoothSetupAssistant[1830]: Nokia

[rodrohf]

Hello! I didnt have any problem with my N73 sync'ing with my Macbook on Leopard, until yesterday, when I decided to upgrade its firmware.


I have the 4.0738.2.1.1 Firmware
And My Mac is running on Leopard 1.5.2


It seems that nokie cant keep the connection active to my Macbook.

The console shows the following error:

21/03/08 05:29:32 p.m. System Preferences[28297] BluetoothSDPDataElement an SDP type "String" can not be encoded in an NSString (it is not UTF8)

21/03/08 05:29:32 p.m. System Preferences[28297] BluetoothSDPDataElement an SDP type "String" can not be encoded in an NSString (it is not UTF8)

21/03/08 05:29:32 p.m. System Preferences[28297] BluetoothSDPDataElement an SDP type "String" can not be encoded in an NSString (it is not UTF8)



Any help would be greatly appreciated

[sirius]

Thanks bitflung

My Console log shows:

22/03/2008 10:13:48 am [0x0-0xc40c4].com.apple.isync[3025] 10:22:48.137 [iSync:3025] ERROR (.bluetooth.rfcomm): got immediate error at opening (openRFCOMMChannelAsync: kIOReturnError

My son's Sony Ericcson phone can Bluetooth to my iMac with no problems.

[sirius]

I did get another reply from Dana at Nokia Care saying

"Nokia phones are designed to work with Windows operating systems."

I was also told to check to see if my phone works with other Nokia Bluetooth devices. This is not really any help to the thousands of Mac users struggling with the issue caused by the changes in the firmware.

[cmoussette]

I called Nokia Care in Sweden and they took a detailed report of the issue. The representative told me this report goes directly to the developpers in Finland and that he (or them) would call me back at some point. It's been 2-3 weeks now since I logged the bug report and no word from Nokia yet.

I guess the problem is between OSX 10.5 and the latest N73 firmware. Latest firmware (4.x) pairs fine with an OSX 10.4 configuration. And an old firmware (3.x) pairs fine with 10.5.

It's quite ridiculous that the latest firmware doesn't work with an up-to-date computer OS released 6 months ago. Really bad job from Nokia on this one.

Personally, I've went back to my Sony-Ericsson phone that works. The N73 is collecting dust and I don't miss an opportunity to report this absurd situation to all my friends and colleagues, especially if they are shopping for a new phone.

[eivindjo]

I just got a reply after posting my issue to Nokia via their feedback form:

"Thank you for emailing Nokia Care.

In response to your enquiry, if you are unable to connect your Nokia N73 via bluetooth with a MAC operating system, I would recommend that you contact them for further assistance.

Kindly note that the firmware update on any Nokia mobile phones enhances its existing features."

I would have done this if I had experienced the problem after upgrading to 10.5, but I have been using my phnoe flawlessly with 10.5, 10.5.1 and 10.5.2 until I upgraded the firmware on the phone. I do not feel Nokia want mac users as their customers. Kind of regret having bought a product from them, won't repeat the mistake.

[bitflung]

ok - i'm back from a weekend away - the log snippets posted give me only 2 useful nuggets of knowledge:

1. bluetooth is working well enough to get data flowing in at least one direction: big question,can we witness data flow (not control flow) from the phone to the mac? (control: initiating the pairing, expecting certain data objects; data flow: the device make/model/etc)

2. scv/maj/min codes. might be useful, i'll have to look into it. anyone with a lot of bluetooth implementation knowledge care to save me from walking down every path of the maze (you know, dead-end leads) - please feel free.

i'm expecting to find that the issue is related to A2DP support in OSX 10.5 as well as the N73. likely a flaw in one or both bluetooth stacks. clearly the mac will be easier to alter - wish i had a copy of 10.5 to help me find a way to disable A2DP temporarily...

i'll write back when i've got something for you,
cheers

[bitflung]

could you browse here:
/System/Library/Extensions

and look for files that start with, "IOBluetooth"

on my macosx 10.4 box, i have 2 files: IOBluetoothFamily.kext, and IOBluetoothHIDDriver.kext.

if you have only these 2 bluetooth kernel extensions, let 'Show Contents' on the Family.kext module.

in here we will find a folder called 'Plugins'.
there should be ~8 files here. we're looking for anything that might be related to A2DP. list the filenames here, please.

my idea: if the problem is related to A2DP, and if we can locate the kernel extension that provides this feature, we can try temporarily disabling the feature on your mac.

Pros: completely reversible, cuts away a significant portion of the list of "likely sources of error"

Cons: i am blind (i dont have 10.5, cant tell you what you'll see), you will need to take care to type EXACTLY what i tell you, in the event we find the kernel extension to disable (we will be moving system files around from a command prompt, move the wrong one, or delete the wrong one, and you will HATE ME. please don't do this, i don't like to be hated)

you might not be comfortable with the risks - if/when we get that far i will write BOLD WARNINGS indicating that the next steps are potentially hazardous. really, this is like warning you that your McDonalds coffee is really hot -- it will be clear to you which parts are scary and which aren't, but like McDonalds i'll give the warning and expect you to not spill coffee on an infant. (err - translate the analogy to something appropriate, i'm at work and only have so much imagination at the moment).

[papy_cartana]

---

24-Mar-2008 09:26 PM
bitflung wrote:
could you browse here:
/System/Library/Extensions

and look for files that start with, "IOBluetooth"

on my macosx 10.4 box, i have 2 files: IOBluetoothFamily.kext, and IOBluetoothHIDDriver.kext.

if you have only these 2 bluetooth kernel extensions, let 'Show Contents' on the Family.kext module.

in here we will find a folder called 'Plugins'.
there should be ~8 files here. we're looking for anything that might be related to A2DP. list the filenames here, please.

---

There you go!... my screenshot is in spanish, my main language there are seven files in the package, one is named A2DP Audio Driver, check it & tell me if I can help doing some testing.

Here's the link to the screenshot:

http://img301.imageshack.us/img301/3686/osx1052iobluetoothfamilzz0.jpg

Let's teach Nokia Developer's some good hacking x)

Message Edited by papy_cartana on 25-Mar-2008 02:44 AM

[sirius]

could you browse here:
/System/Library/Extensions

and look for files that start with, "IOBluetooth"

on my macosx 10.4 box, i have 2 files: IOBluetoothFamily.kext, and IOBluetoothHIDDriver.kext.

if you have only these 2 bluetooth kernel extensions, let 'Show Contents' on the Family.kext module.

in here we will find a folder called 'Plugins'.
there should be ~8 files here. we're looking for anything that might be related to A2DP. list the filenames here, please.

---

Here's a link to a couple of screengrabs: http://www.designermagic.co.uk/A2DP.html

The first one is the files listed as the Contents of the Family.kext. The second image is when I open the A2DPAudioDriver in my text editor.

[bitflung]

ok - so we've got an A2DP specific kernel extension - lets disable it.

note: THIS IS THE PART WHERE YOU COULD CAUSE DAMAGE.
theoretically, the mac might not boot properly, this could mean kernel panics on start up. it's not likely, actually it's very unlikely, but it is possible in theory that the kernel module is linked-to by poorly written code that crashes the kernel when when the extension can't be found.

if you proceed, have an exit strategy: look up info on how to boot your mac in "Target Disk Mode", allowing the mac to be used like an external USB drive, and document (paper and pencil) exactly what you need to remember to find the files you're moving around. i can't be too careful here - don't hate me: prepare for the worst, despite how unlikely it is.

you may be able to do this form the Finder, but i've done it for my I2C kernel extension via the Terminal in the past... pick your poison. the basic idea comes from here:
http://www.macfixitforums.com/php/showflat.php?Cat=&Board=Forum35&Number=731599&page=0&view=expanded...
(sorry, long url - in short, the link is a forum thread regarding powerbooks with bad temp sensors: disabling the I2C kernel extension prevents the temp sensor from being read, therefore prevents the mac from performing emergency thermal shutdown when it wasn't necessary. apple repair doesn't even fix the root problem: an LM75 thermal sensor that fails by asserting an overheat alarm)

ok, onto the actual ATTEMPT TO FIX BLUETOOTH (again POTENTIAL FATAL, but akin to choking to death on a tic tac - possible but not likely)

before starting: we want to remove all bluetooth devices that might talk to your mac via A2DP - and certainly the N73 since that's what we hope to fix. delete the entries in the Bluetooth preferences. if you have an A2DP headset or other device, delete those entries as well. we want the mac to see the device, essentially, 'for the first time' after the process prescribed below.

after deleting the bluetooth devices as per above, read all of the following steps, then perform them only if you are comfortable with the potential consequences.

1. open Terminal.app
2. enter the following commands, without the single-qoutes:
'cd /System/Library/Extensions'
'cd IOBluetoothFamily.kext/'
'cd Contents/PlugIns/'

3. you are now sitting at a command prompt, sitting in the path of the plugin that you want to disable. we're going to rename the file in order to disable it.

4. rename the file:
'mv IOBluetoothA2DPAudioDriver.kext IOBluetoothAudioDriver.DISABLED'

5. now we need to purge the cache - see, to make startup faster, the kernel extensions are not queried every time you boot - instead they are cached and only queried when the cache is purged (or perhaps on a boot count as well, i'm not sure, but purging forces them to be queried again)

6. purge the kext cache:
'cd /System/Library/'
'mv Extensions.kextcache Extensions_kextcache.OLD'
'mv Extensions.mkext Extensions_mkext.OLD'

7. cross your fingers and reboot.

8. IF YOUR MAC DOES NOT START PROPERLY: you will need to find a way to access the drive and undo the changes made above. if you cannot perform this yourself, contact this forum via another computer (don't have one? perhaps there is one at your local library). in short, your potential methods to access the drive are:
1. boot in single user mode
2. boot in 'safe mode' which should disable all extensions (thereby disabling anything that depends on the extensions you've disabled above - dont expect to be able to go online in this mode)
3. boot in "Target Disk mode" and connect your mac to another mac (perhaps even a PC? i doubt it though, likely only mac since windows isn't likely to support the filesystem type on your mac)

9. your mac boots up perfectly fine? good. this is expected - sorry to scare you with all that 'crisis management' mumbo-jumbo, but better to be safe than sorry. go ahead and attempt to pair your mac with your N73. i would attempt the pairing, of course, form the MAC side using Bluetooth Setup Assistant.

10. if it works, jump up and down, holler, maybe even get that self-reliant-proud feeling of fixing it yourself. if it doesn't work, sorry - perform steps 1 through 5 above, but clearly reversing the names so that .DISABLED becomes .kext. step 6 should be performed as it is written, thereby purging the cache and causing your mac to query the kernel extensions, resulting in A2DP being functional again.

-- if you've just read through this, haven't done it yet, and are confused about something i didnt explain clearly: please ask before attempting any of the above --

good luck!
let me know how it goes

[bitflung]

sorry - forgot one important note:

you will get a permissions error when you attempt to rename the files. the system will prevent you from doing this, but it will allow the 'root' user to do so. you can become the root user, temporarily, by typing the following command prior to step 2 (ie: when you first open the terminal, enter this before anything else):

'sudo -i'


the system will ask for your password, provide this password and you will have gained 'root' permissions. this means that the built-in safety net in macosx is gone: you will have permission to delete the system folder, or break your software by any means available via the keyboard. in other words, after entering this command, make certain that you're commands are entered properly.

note: when you have root permissions, the command prompt (what you seem before you type anything at all) ends with a '#' symbol. plain old user permissions, your command prompt ends with a '$' symbol.

when you are done working as the root user, it's always a good idea to type 'exit', which closes the session and returns you to normal-user-status.

[bitflung]

-----
4. rename the file:
'mv IOBluetoothA2DPAudioDriver.kext IOBluetoothAudioDriver.DISABLED'
-----
terrible place for a typo, note that if you follow my steps and want to reverse the process above, 'A2DP' was stricken from the filename accidentally.

this will only affect you in the process of 'undoing' the changes we made - please be sure to rename the files, when undoing the changes, back to their ORIGINAL filenames.

it is helpful, at a command prompt, to use TAB-COMPLETION. type part of a file-name, press TAB and it will be completed for you. for example:

'cd /Sys' will become "cd /System"
if the partial name is not unique, press tab twice to see a list of potential completions. type the next letter or two and press tab again.

sorry - i will read through again looking for typos - but in case i miss any others, use of tab-completion will prevent you from making mistakes.

[sirius]

bitflung

Thank you so much for taking the time to debug this. I really appreciate your help & your detailed instructions.

I'm going to try this tomorrow morning as right now I've got a couple of deadlines.

Thanks again - I'll let you know how it goes tomorrow.