The slow start up issues we all are having are definately a firmware issue...I gaurentee its just a bug in the compiler. Think of it like this. he compiler is like the RAMs "transmission"....
No matter how much horse power you got under the hood, if ur stuck in second gear ur scewed.
The slow start up issues we all are having are definately a firmware issue...I gaurentee its just a bug in the compiler. Think of it like this. he compiler is like the RAMs "transmission"....
No matter how much horse power you got under the hood, if ur stuck in second gear ur scewed.
Please explain how long load times are a "compiler" issue.
The slow start up issues we all are having are definately a firmware issue...I gaurentee its just a bug in the compiler. Think of it like this. he compiler is like the RAMs "transmission"....
No matter how much horse power you got under the hood, if ur stuck in second gear ur scewed.
Please explain how long load times are a "compiler" issue.
I'll try to it as simply as I can. A compiler is code that regulates the flow of data in/out the OS using the RAM..kind of like a carburator and exhaust...but way more complex...It performs analysis, transformations and optimizations of data that are for a particular computer. Then, it generates code for a particular processor and OS. Basically its what allows the firmware and the software to interact efficently... So if there is a bug in the compiler long load times and input response would be the first symptoms of a that particular issue...(Sort of Like a knock in the engine)
You see most of the software testing is done utlizing emulators and until the System is completely integrated you won't know exactly how well it will interact...So i'm thinking in Prelim testing this thing past with flying colors...(which explains all the hype) but when it got to the system integration phase, unexepected problems occured...so they had a choice: release and fix or delay release and waste promotional dollars
if they put it all together and it was heat or processor issues (alla Xbox 360) I think they would have delayed...The cost of a recall is beyond Pioneer's reach...there big but not MS big.
The slow start up issues we all are having are definately a firmware issue...I gaurentee its just a bug in the compiler. Think of it like this. he compiler is like the RAMs "transmission"....
No matter how much horse power you got under the hood, if ur stuck in second gear ur scewed.
Please explain how long load times are a "compiler" issue.
I'll try to it as simply as I can. A compiler is code that regulates the flow of data in/out the OS using the RAM..kind of like a carburator and exhaust...but way more complex...It performs analysis, transformations and optimizations of data that are for a particular computer. Then, it generates code for a particular processor and OS. Basically its what allows the firmware and the software to interact efficently... So if there is a bug in the compiler long load times and input response would be the first symptoms of a that particular issue...(Sort of Like a knock in the engine)
You see most of the software testing is done utlizing emulators and until the System is completely integrated you won't know exactly how well it will interact...So i'm thinking in Prelim testing this thing past with flying colors...(which explains all the hype) but when it got to the system integration phase, unexepected problems occured...so they had a choice: release and fix or delay release and waste promotional dollars
if they put it all together and it was heat or processor issues (alla Xbox 360) I think they would have delayed...The cost of a recall is beyond Pioneer's reach...there big but not MS big.
Interesting. So, when my PC takes a long time to load Windows, it's because Microsoft used a buggy "compiler?"
Interesting. So, when my PC takes a long time to load Windows, it's because Microsoft used a buggy "compiler?"
Well PC systems are much more complex and have a lot more things going on at once than one of these units does... especially when you're talking about boot up procedures. You can't really compare the two. When you look at one of these F units as a computer, you have to think of it as a VERY simplified example.
NO clue what your talking about. EVERYTHING now days is compter based, they have RAM, A processor, Input devices and an Operating system etc. They are in essence a COMPUTER, they are just a different incarnation and designed to be in a car, handles high temps, has a small touch screen, has a amp for speakers etc.
AS for the long boot up issue, they need ot figure out a way to prioritize the boot up so primary control come sup FIRST allows you to manipulate the system, THEN load up everything else.
Right now it seems they are trying to load EVERYTHING at once and in a sequence, navigation, voice recognition, ROM drive, SD card, XM, IPOD control, Bluetooth.
So point is, have the system learn what the user will most likely use, and prioritize from there in the start up.
Right now it takes over a minute to do much of anything, xm takes 20 seconds to start with music, ipod takes over 30. The system is loading screen takes at least a min fifteen seconds to clear no matter what. If ipod is your primary source upon start up, you have a unclearable screen present for at least 2 mins 15 seconds.
NO clue what your talking about. EVERYTHING now days is compter based, they have RAM, A processor, Input devices and an Operating system etc. They are in essence a COMPUTER, they are just a different incarnation and designed to be in a car, handles high temps, has a small touch screen, has a amp for speakers etc.
AS for the long boot up issue, they need ot figure out a way to prioritize the boot up so primary control come sup FIRST allows you to manipulate the system, THEN load up everything else.
Right now it seems they are trying to load EVERYTHING at once and in a sequence, navigation, voice recognition, ROM drive, SD card, XM, IPOD control, Bluetooth.
So point is, have the system learn what the user will most likely use, and prioritize from there in the start up.
Right now it takes over a minute to do much of anything, xm takes 20 seconds to start with music, ipod takes over 30. The system is loading screen takes at least a min fifteen seconds to clear no matter what. If ipod is your primary source upon start up, you have a unclearable screen present for at least 2 mins 15 seconds.
exactly...you see the system is running the apps....reading your ipod, gathering, processing into VR data, translating satalite data along with executing a standard boot up sub routine...which can be all done simutaneously as long as the data is being compiled efficiently...if not you get lag lag lag
OK I am not sure if your getting your terms mixed up or what, a COMPILER is used to put code written by us, and translate it into code a computer can understand, this is only done once when the guys who write the code, "compile" it with a program called a compiler.
Now if that code is not optimized, yes you are right it will load slowely. But yes if your point is the code is not optimized and could use some work yes absolutely.
The programmers for this thing were obviously under the gun with time constraints, they had a deadline, did the best they could and were probably asked, "is it functional" they said yes, but it has some serious bugs, they said well, it works so put it out there. We can put out an update later right to fix the issues that are left? yes we can, so there you have it.
This is no different then Microsoft putting out MS vista with bug city.
So what can you do, even the modern home a/v receiver is computer based, I just updated it the other day. My tv too and even my phone.
So this is no different. Now its just a matter of how long they will take for a fix, my guess is they knew going out the gate this thing had issues, but instead of waiting, they had to set hte market, and here we are complaining.
Owell, what can you do, just wait for the firmware update if you have one and wait for the new ones to come out with a fix if you dont and want one.
[
Interesting. So, when my PC takes a long time to load Windows, it's because Microsoft used a buggy "compiler?"
no not necesarily...most likely you have to many programs in your start up....what make units like this different than pcs is that ur dealing with a custom interface combined with the navi data and the need to translate Apple code to something the VR system can recognize, not to mention general start up with custom settings really makes what should be simple code much more complex...think about it: you turn this thing on and the first thing it wants to do is figure where in the world it is and then read your ipod from top to bottom....the problem as I see it is that the GPS calculation is part of the boot sub routine....which should come after not during load...if anybody owns a garmin they can attest: you turn it on, then the OS loads, then it finds out where you are....The Avic is making harder on itself than it has to be...now it is possible to all of this simutaneouly but again the code starts to get really complex....and you'll start to have compiler issues
OK I am not sure if your getting your terms mixed up
First since this is a touch interface commanding muliple systems, and is windows based....its probably written in C++. Now C++ is an OOD language and for systems to interact there has to be compiler code that will allow the high level OS to into interact with low level mechanisms within the system...I'm trying not to get too technical...
OK I am not sure if your getting your terms mixed up
First since this is a touch interface commanding muliple systems, and is windows based....its probably written in C++. Now C++ is an OOD language and for systems to interact there has to be compiler code that will allow the high level OS to into interact with low level mechanisms within the system...I'm trying not to get too technical...
So, there is a compiler running on the headunit? You seem to know a whole lot about software development. Are you a developer?
Compiler on the head unit?
Not likely. Why in the world would they compile on the fly. You want to talk about slow...
Programmers write code for the unit. The program code is then "compiled" into machine readable code for the device. That code is then loaded into the units. A really crappy compiler could affect performance. My thoughts would be poorly written sorce code, poorly optimized startup of differnet aspects of embedded OS, or an underpowered CPU. Compilers these days are not usually an issue.
Really, unless Pioneer release the source code, and a detailed bill of meterials for the hardware (ram/rom/flash/cpu/bus), we are all just guessing. Anyone want to open theirs up?
Thank you, my point exactly!
schmiddytwo
So what you ar saying is that you can fix it?
LOL
Noting personal, but you are all WAY off.
Jesus.
No, that guy is NOT a programmer. If he was, he would be fired.
This is the flow.
You write code in whatever language you want:
C, C++, etc. Yes, there is a good possibility the underlying system was written in C++, especially if it's based on the Windows Mobile Operating System. Most companies are still using C however.
Once the programmer has written code in a high level language, he then uses a compiler to create "compiled objects" in the form of "machine code". This would be binary, 1's and 0's. These compiled objects are then "linked" together using a linker to create a single executable, or ROM file. It's this ROM file that is then eventually loaded (burned) in to the flash on the embedded system. The embedded system being the AVIC radio.
With all that said and done, it's likely the system is slow to boot because A. It has not been optimized and B. They are not jumping to the home screen until *everything* has loaded. This is typical when developers need to get a system up and going. later on they could come back and set it up so that the last used "module", be it radio, cd, ipod, etc. is loaded first and then the rest are loaded in the background.
Any questions? PM me.
http://en.wikipedia.org/wiki/Compiler