Sluggish Idrive upon startup
08-09-2009, 10:26 AM
#11
Senior Members
Join Date: Jun 2006
Location: Northern NJ
Posts: 630
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by sdg1871' post='970049' date='Aug 9 2009, 06:24 AM
I have the same issue with the iDrive in my 2009. I bet that the new iDrive in the 2010 is not so slow on startup given the major upgrade.
If you put money on that bet you would win
2010 idrive is awesome.. I love how responsive it is even right after start up. Not only did my new 2010 535i has turbo engines, but turbo computer too!
08-09-2009, 01:19 PM
#12
Senior Members
Join Date: Mar 2009
Location: Northern Virginia - USA
Posts: 421
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 2007 550i Jet Black|Black
Options: Sport|Premium|Cold Weather|PDC|Nav|Satellite Radio|Active Steering|Convenience Entry
Mods: Trinity Side Skirts|Trinity Black Grilles|LCI Tail Lights with Bruce V6|Fog Light Bezel Rings|MTEC V2 Angel Eyes|LED License Plate Lights
Originally Posted by jherm' post='963388' date='Aug 2 2009, 11:45 PM
My i-drive usually acts very sluggish immediately after startup. Just very slow to react to commands. After a minute or so it will react normally. Is this normal or should it respond quickly to every command immediately after startup? I believe I had a software upgrade just a few weeks ago.
Do you have a bluetooth phone with a large contact list that the car is syncing up with?
08-09-2009, 02:40 PM
#13
Senior Members
Join Date: Dec 2008
Location: The Netherlands
Posts: 311
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: '04 530d Executive, all options except sunroof and comfort seats
ECU remapped by ZipTuning to 260+bhp.
Originally Posted by wolf' post='970320' date='Aug 9 2009, 11:19 PM
Mine is this way as well but I think it has to do with the iDrive syncing up with my BlackBerry's phone book. I think it loads all the information on the fly at startup. After the phone information is all there, things seem to run faster.....
Do you have a bluetooth phone with a large contact list that the car is syncing up with?
Do you have a bluetooth phone with a large contact list that the car is syncing up with?
When the CCC is booting, it's turning on all computers one by one.
So, first would be the audio module, next GPS, next A/C, etc...
While this is happening, the iDrive is just pre-occupied with dealing with this stuff.
Compare it to an old single-core Windows XP computer that has lots of junk starting up right after a boot (like all the crappy ad-software, integrated "premium" software that some computer-companies provide, MSN, etc...).
The first couple of minutes, it takes forever to do anything. Starting up a browser takes a minute, but after all the sh*t has been loaded, starting a browser takes 10 seconds tops.
This is the exact same thing that's happening to an iDrive computer while booting. It's just loading the drivers and communicating with the different computers.
The iDrive doesn't exactly have a fast processor (it's in fact slower than most PDA's nowadays) and unfortunately: the more options you have, the longer it takes to boot.
08-09-2009, 03:36 PM
#16
Senior Members
Join Date: Jun 2006
Location: Northern NJ
Posts: 630
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by e6t' post='970382' date='Aug 9 2009, 06:56 PM
my bmc filter made my idrive boot faster.
08-09-2009, 03:39 PM
#17
Senior Members
Join Date: May 2009
Posts: 609
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Kzang' post='970411' date='Aug 9 2009, 06:36 PM
Amazing.. I bet the sprint booster further decreases lag time on idrive boot up as well!
actually, it makes the knob feel as though it spins faster.
08-09-2009, 06:08 PM
#18
Senior Members
Join Date: Mar 2009
Location: Northern Virginia - USA
Posts: 421
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: 2007 550i Jet Black|Black
Options: Sport|Premium|Cold Weather|PDC|Nav|Satellite Radio|Active Steering|Convenience Entry
Mods: Trinity Side Skirts|Trinity Black Grilles|LCI Tail Lights with Bruce V6|Fog Light Bezel Rings|MTEC V2 Angel Eyes|LED License Plate Lights
Originally Posted by OverSoft' post='970370' date='Aug 9 2009, 06:40 PM
No, it has nothing to do with the pairing.
When the CCC is booting, it's turning on all computers one by one.
So, first would be the audio module, next GPS, next A/C, etc...
While this is happening, the iDrive is just pre-occupied with dealing with this stuff.
Compare it to an old single-core Windows XP computer that has lots of junk starting up right after a boot (like all the crappy ad-software, integrated "premium" software that some computer-companies provide, MSN, etc...).
The first couple of minutes, it takes forever to do anything. Starting up a browser takes a minute, but after all the sh*t has been loaded, starting a browser takes 10 seconds tops.
This is the exact same thing that's happening to an iDrive computer while booting. It's just loading the drivers and communicating with the different computers.
The iDrive doesn't exactly have a fast processor (it's in fact slower than most PDA's nowadays) and unfortunately: the more options you have, the longer it takes to boot.
When the CCC is booting, it's turning on all computers one by one.
So, first would be the audio module, next GPS, next A/C, etc...
While this is happening, the iDrive is just pre-occupied with dealing with this stuff.
Compare it to an old single-core Windows XP computer that has lots of junk starting up right after a boot (like all the crappy ad-software, integrated "premium" software that some computer-companies provide, MSN, etc...).
The first couple of minutes, it takes forever to do anything. Starting up a browser takes a minute, but after all the sh*t has been loaded, starting a browser takes 10 seconds tops.
This is the exact same thing that's happening to an iDrive computer while booting. It's just loading the drivers and communicating with the different computers.
The iDrive doesn't exactly have a fast processor (it's in fact slower than most PDA's nowadays) and unfortunately: the more options you have, the longer it takes to boot.
If the iDrive is initializing each system sequentially, and then it hits the phonebook and has to load up a few hundred contacts it adds cycles. In-line with what you are saying - loading up the contact list at the front-end, causes a longer wait, while once the list is in memory, it runs faster.
If the start-up is sequential and the system will not allow user input / system control while the phonebook is being synced (which may be the case for a poorly implemented system or OS that will not allow multi-tasking) then it will without question hang things.
I don't know the overhead associated with loading up a contact but I assume that with iDrive, a few hundred contacts will cause a noticeable delay compared to no phone at all or a small contact list. Further I think the way contacts are implemented on your mobile device adds to complexity. Specifically, I think that iDrive takes individual contacts on the blackberry and converts them into multiple contacts on iDrive (i.e. mobile phone, work phone, home phone.) I think this is the case but would have to double check for sure...
My two cents...
08-09-2009, 07:55 PM
#19
Members
Thread Starter
Join Date: Jul 2009
Location: Atlanta, GA
Posts: 227
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by wolf' post='970568' date='Aug 9 2009, 10:08 PM
I agree with your comments on how the system initializes but my instincts tell me that pairing a large contact list can be a contributing factor for iDrive initialization delays.
If the iDrive is initializing each system sequentially, and then it hits the phonebook and has to load up a few hundred contacts it adds cycles. In-line with what you are saying - loading up the contact list at the front-end, causes a longer wait, while once the list is in memory, it runs faster.
If the start-up is sequential and the system will not allow user input / system control while the phonebook is being synced (which may be the case for a poorly implemented system or OS that will not allow multi-tasking) then it will without question hang things.
I don't know the overhead associated with loading up a contact but I assume that with iDrive, a few hundred contacts will cause a noticeable delay compared to no phone at all or a small contact list. Further I think the way contacts are implemented on your mobile device adds to complexity. Specifically, I think that iDrive takes individual contacts on the blackberry and converts them into multiple contacts on iDrive (i.e. mobile phone, work phone, home phone.) I think this is the case but would have to double check for sure...
My two cents...
If the iDrive is initializing each system sequentially, and then it hits the phonebook and has to load up a few hundred contacts it adds cycles. In-line with what you are saying - loading up the contact list at the front-end, causes a longer wait, while once the list is in memory, it runs faster.
If the start-up is sequential and the system will not allow user input / system control while the phonebook is being synced (which may be the case for a poorly implemented system or OS that will not allow multi-tasking) then it will without question hang things.
I don't know the overhead associated with loading up a contact but I assume that with iDrive, a few hundred contacts will cause a noticeable delay compared to no phone at all or a small contact list. Further I think the way contacts are implemented on your mobile device adds to complexity. Specifically, I think that iDrive takes individual contacts on the blackberry and converts them into multiple contacts on iDrive (i.e. mobile phone, work phone, home phone.) I think this is the case but would have to double check for sure...
My two cents...
You are correct that idrive converts multiple numbers under a single contact into multiple contacts. "Steve Mobile" will be a contact and "Steve Work" will be a contact.
08-09-2009, 11:51 PM
#20
Senior Members
Join Date: Dec 2008
Location: The Netherlands
Posts: 311
Likes: 0
Received 0 Likes
on
0 Posts
My Ride: '04 530d Executive, all options except sunroof and comfort seats
ECU remapped by ZipTuning to 260+bhp.
Originally Posted by wolf' post='970568' date='Aug 10 2009, 04:08 AM
I agree with your comments on how the system initializes but my instincts tell me that pairing a large contact list can be a contributing factor for iDrive initialization delays.
If the iDrive is initializing each system sequentially, and then it hits the phonebook and has to load up a few hundred contacts it adds cycles. In-line with what you are saying - loading up the contact list at the front-end, causes a longer wait, while once the list is in memory, it runs faster.
If the start-up is sequential and the system will not allow user input / system control while the phonebook is being synced (which may be the case for a poorly implemented system or OS that will not allow multi-tasking) then it will without question hang things.
I don't know the overhead associated with loading up a contact but I assume that with iDrive, a few hundred contacts will cause a noticeable delay compared to no phone at all or a small contact list. Further I think the way contacts are implemented on your mobile device adds to complexity. Specifically, I think that iDrive takes individual contacts on the blackberry and converts them into multiple contacts on iDrive (i.e. mobile phone, work phone, home phone.) I think this is the case but would have to double check for sure...
My two cents...
If the iDrive is initializing each system sequentially, and then it hits the phonebook and has to load up a few hundred contacts it adds cycles. In-line with what you are saying - loading up the contact list at the front-end, causes a longer wait, while once the list is in memory, it runs faster.
If the start-up is sequential and the system will not allow user input / system control while the phonebook is being synced (which may be the case for a poorly implemented system or OS that will not allow multi-tasking) then it will without question hang things.
I don't know the overhead associated with loading up a contact but I assume that with iDrive, a few hundred contacts will cause a noticeable delay compared to no phone at all or a small contact list. Further I think the way contacts are implemented on your mobile device adds to complexity. Specifically, I think that iDrive takes individual contacts on the blackberry and converts them into multiple contacts on iDrive (i.e. mobile phone, work phone, home phone.) I think this is the case but would have to double check for sure...
My two cents...
Splitting the contacts into multiple contacts is done by the phone, not by the car. This adds no noticable delay.