BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 03-22-2009, 07:44 PM   #1 (permalink)
New Member
 
Join Date: Mar 2009
Model: 8830
PIN: N/A
Carrier: Sprint (NMCI)
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Exclamation Blackberry 8830 - Bluetooth Headset profile disabled

Please Login to Remove!

Hey all,


I have a friend with a Blackberry 8830 WE through Sprint, issued by NMCI. He does HVAC work. I am an IT professional, and as such, whenever there is a problem that he cannot fix, he brings it to me. I've never set up a BES before, but all a Blackberry is, is a handheld computer (basically). I am having an issue that is frustrating the *you know what* out of me!

He uses his Blackberry with a Bluetooth CAC card reader. The kind of work he does requires him to use his blackberry to send and receive emails, and answer calls. He cannot carry his Blackberry with him while he's working in a panel, because it's a little hard to answer a phone while you're working in a panel with 480 volts circuits that are hot, so he leaves it in the truck, which means he misses calls. He decided to get a bluetooth headset to fix this problem, figuring it would be no issue, right?

WRONG!!!

He tried it, then handed it to me.

I had no problem pairing it with the headset, but when I went to connect it, I got the "Headset has been disabled by your system administrator". message. Short of flashing the firmware (current version: 4.2.2.196) on the phone (which would not be advisable), is there a way to fix this?

Nevermind, I KNOW there's a way to fix this. Can someone please explain to me what I have to do to re-enable the Bluetooth Headset Profile on the 8830 W.E.? I'm sure he's not the only person who's experienced this problem, but I was unable to find any information on this forum, or using google, or every other search engine (including DogPile).

Any help would be greatly appreciated. I've hacked phones before, but I do not want to damage the firmware installed on this phone in any way, shape, or form; just modify one simple setting to make his work life a whole lot easier.

Any help would be greatly appreciated! Thanks!
Offline  
Old 03-22-2009, 09:25 PM   #2 (permalink)
CrackBerry Addict
 
VIOLATOR's Avatar
 
Join Date: Oct 2008
Location: Cajun Country
Model: BOLD
OS: 5.0.0.900
PIN: Pulled - 1, 2, 3 run!
Carrier: AT&T
Posts: 615
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

If I am understanding everything - this feature has been disabled by the administrator of the BES from his place of employment.

He needs to get with that individual to see about getting that particular feature enabled.

I hope I am not missing something here but from what you have described that is the solution?

David
__________________
F'em & Feed'em Fishheads...

Twitter
Offline  
Old 03-30-2009, 10:34 AM   #3 (permalink)
New Member
 
Join Date: Mar 2009
Model: 8830
PIN: N/A
Carrier: Sprint (NMCI)
Posts: 2
Post Thanks: 0
Thanked 0 Times in 0 Posts
Unhappy

Quote:
Originally Posted by VIOLATOR View Post
If I am understanding everything - this feature has been disabled by the administrator of the BES from his place of employment.

He needs to get with that individual to see about getting that particular feature enabled.

I hope I am not missing something here but from what you have described that is the solution?

David
This is not a solution (see last paragraph). The admin doesn't have the capability to do anything about it.

If no one on this board is willing to give advice or lend a hand, which is painfully obvious considering the number of views this thread has, then here's my fix-all solution:

(P.S.- I'm going to post results when this is done, along with detailed instructions, so that anyone else who needs to do it, can do it, with little to no problem, and without having to touch ANYTHING at the BES level).

--Open phone, to make sure no pins are pulled (none are, thank goodness)

--Back up the DoD Root Certificates (DONE)

--Extract the bluetooth pairing PIN from either the reader or the phone (DONE)

--Extract firmware image. Make backup for "oops" purposes.

--Make sense of code (iffy). Identify portion of code that deals with settings.

--Wipe the firmware, restoring it with the version it already has on there (4.2.2.196)

--Lock setting out from WAP push, or modify settings update switch (if possible, if exists)

--Re-install S/MIME

--Re-connect smartcard (CAC card) reader.

--Re-install DoD Root Certs

--Assuming coding was at least *somewhat* understandable-- Import critical and non-critical settings into phone (such as phone book info)

--Connect Bluetooth headset

--Boot phone

Not trying to criticize, but since I don't hesitate to help others (regardless of the circumstances), I will do the work on this one, document the results, and work on some sort of automation to make this job easier in the future (like perhaps an executable?). And the viewing public of this board (all 200 and-some-odd of them that were interested in this thread, anyway) will get to reap the results.

After having to deal with this for the last two weeks (and the lack of interest...I guess mine is the only brain that cares about solutions to problems like this, everyone else seems to cop out), I am never buying a blackberry. Yes, I've thought about owning one for years. Yes, they're pretty. Yes, they're convenient. Yes, they even deliver email messages in real time (MOST of the time). Yes, I even like them. They're shiny, and I like shiny things with fancy features and lots of buttons (I'm a geek! Surprise!). I do not, however, like shiny things that are a pain in the butt to fix something this *bloody* simple on. Furthermore, from a sys admin perspective (at least, judging by this ONE problem, and the lack of people/online resources to fix it), I'd much rather deal with something else, like Palm, or Windows Mobile.
Blackberry's programming pretty much seems to be shrouded in mystery. I don't like that. When it comes to smartphones, I'm quite happy with my Nokia N95, personally. The next phone is either going to be a Palm or Windows Mobile (GSM). I may yet consider owning a blackberry, but with some of the apps I use, unless the programming changes significantly, forget it.


David, thank you for your suggestion. (However....it's a BUREAUCRACY!!) I did indeed speak with the person in question that handles such things, and she said she doesn't have the ability to change it. She didn't have a problem with it being changed for this person, because of the nature of the work he does. She gave me all the relevant documentation on BES's (which were an interesting read, to say the least), which weren't a help. We can't update the setting via WAP push. If this is successful, the results will be sent to her, so that the other people in this department, with this problem, can get it fixed.


Last edited by waterheart776 : 03-30-2009 at 10:35 AM.
Offline  
Old 05-30-2009, 09:11 AM   #4 (permalink)
New Member
 
Join Date: May 2009
Model: 8830
PIN: N/A
Carrier: verizon
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I was receiving the error , "headset has been disabled by your system administrator." on my BB 8830 with BES. Solution on my end turned out to be as simple as going into the BlueTooth application on my BB --> bring up MENU --> OPTIONS --> Scroll down until you see SERVICES: Check the box next to HEADSET which was previously unchecked. The default is for the service to be turned on. In my case I was troubleshooting using the phone as a modem and in that process turned this off.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.