Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Just tried this on my V2 SAP cradle and it works! Thanks for the tip whitenemesis.
I tried again with the entry both on the downloaded contacts as well as on the Comand phone book but it did not change my V1 BT SAP shut down time.
I don't remember if I've tried it with a phone on the cradle, that would rule the V1 SAP BT device out.
T
You can force a shut down by pressing TEL for >2sec (again this is for my COMAND-APS)
This is a COMAND thing, not a SAP module specific thing. I guess your COMAND doesn't support the feature. The instructions don't mention bluetooth, it expects the phone to be in the cradle.
To get it to work for me I had to create the contact on the phone then re-sync with COMAND. I don't have a cradle.
You can force a shut down by pressing TEL for >2sec (again this is for my COMAND-APS)
I understand the disconnect feature being missing from the W221 when it does not have a specific button assigned for the phone but the lack of support for the shut down timer is strange. I even have the Comand SW updated, they should have received sufficient complaints about the phone staying on and re-introducing the shut down timer. Anyway, it does not bother me personally as I always lose connection very soon when leaving the car to the garage but many other owners report their phone remaining connected to the car when they are at home.
I guess it is obvious that his is Comand specific, I just remember some cradle manual explaining the shut down timer but the BT device manual does not, so "I kept it open".
My COMAND is 2.5, with the MY2001 update, and this worked on mine. Previously the BT connection stayed tied to the car for 10 minutes as whitenemesis said.
DieselBenz, it sounds like yours drops the connection within a minute anyway, so you may not notice a difference. Maybe the shorter connection time is integral to your version of COMAND?
I was still finding it took 10 minutes to drop the connection. Once I went into a my local Waitrose, far out of range of BT, and the connection stayed active in the car for the full 10 minutes, long enough for someone to make a call and leave a message, which I found waiting in the car for me upon my return.
I don't know how often the car checks with the SIM via BT to verify the SIM authorisation but wouldn't have thought it needs constant contact via BT to keep ownership of that authorisation.
I'm using a Nokia N73.
Since the BT SAP connection gets authorisation from the SIM to access the network I'm not sure if the scenerio is exactly the same as if the SIM card was physically removed from the phone. As far as the SAP BT device is concerned the SIM card is "virtually" there until the next time it checks.
I dont have the SAP I use a V3 Motorola via a dedicated Motorola BT cradle -- It too holds onto the BT for around 10 minutes.
Worse thing was when I was in the dealers -- I had disconnected the phone from the car and was making a call in the waiting area - obviously someone had started my car reconnecting it.... hmmm...I was saying hello hello what the f*cks going on here ... ..must have made interesting listening in the workshop if they had it coming through the speakers..
Then I realised what had happened and re-disconnected it again.....now when I take the car in and am staying I unclip the cradle...![]()
Diesel Benz, have you shortly returned to your car once your phone has disconnected and does it reconnect without you unlocking the car?
This could demonstrate COMAND is still "active" and your phone is recaptured once you get back into BT range
I agree with your latter sentence but the point is that the standards set a requirement for the phone to detect the presence of the SIM card. The standard does not care about the implementation, like quite a few phones rely on the fact that the battery needs to be removed before the SIM card can be removed and then don't "watch after" the presence of the SIM card. But those where the SIM card can be removed easily, like those old phones with a credit card sized SIM (small SIMs may have similar holders), have to watch after SIM being present. The intention is to avoid the card being moved from one phone to another (although there are means at the network side to detect this, it anyway creates unwanted tasks for the network). Now with the BT SAP approach, the MB BT SAP adapter should do the same (but never know about the Peiker implementation, perhaps this is not tested at type approval).
I would anyway assume the N73 behave the same way as my E90. Odd if the BT SAP devices behave differently. I'll anyway have to explicitly measure the time it takes when I leave my car until my phone shows service (as it looses BT connection). Perhaps you could test it again too, it could always be a bug in the phone that happens once in a while and prevents the phone to change to normal mode.
The point is it is not the N73 behaving this way, it is the car's phone controller via the BT SAP device that is retaining its hold on the SIM authorisation. As you say, we don't know about the Peiker implementation.
I've done some tests, altering the value of the run-on feature and it is consistent, with the phone switching back to non SAP mode in the time set. This is with my car in range of the BT though. I will have to try it moving out of range as you have done.
We use essential cookies to make this site work, and optional cookies to enhance your experience.