Thread: Centrafuse 1.13 Bugs

First off, the weather plugin said there was a newer version already installed and it wouldnt continue instalation?

The playback resume after phone call issue seems to be resolved. Cool! I havent tested recieving/accepting phone calls yet. I'll give that a try tomorrow.

1. The XM static bug I mentioned in 1.12 is still present. Same issue as before. XM does work after resuming from hibernate when in the media section though!

2. Most every time I have tried to seek through a song, it would stick and fast forward all the way through the song. It required me hitting another button for it to stop.

3. I am still able to reproduce the media playlist count issues with cd's with mp3's on them. Once loaded, CF adds a count to the USB media playlist count, but tells me there is no USB device when I go to play them back. Upon clicking CD, it reloads everything and adds another count to the USB playlist. I don't recall how, but I was also able to get the CD count to 1 with no media in the CD drive. Not quite as bad as it was before, but still not perfect.

4. Last thing I noticed tonight... I inserted a CD that had a few scratches on it to test the playlist count issues that I had before, and CF came to a crawl, forcing me to end task it. I am not sure if this was due to the potential bad/lacking data on the disc, or something else.

Other things to note:

With front set as master, the volume up down arrows do not work, and it always shows "Volume Min" Not sure if that's as designed or not... it doesnt seem right. I use a powermate, so its not a super huge concern as I can still adjust the volume with it, but I figured I would note it. All of the volume control options seem somewhat confusuing, esp if using the volume plugin. Any clarification there as to how it should all work together nicely?

Edit 2: After messing with the volume stuff some more late tonight, I did notice that with or without the volume plugin, the pre and wav volume levels would default to level 50 upon restarting the app or hibernating. Is it supposed to do that? It kinda kills the ability to set a max level using the wav output as well as as causing a few other issues. Bug?

It was pretty much as simple as loading any CD with mp3's on it. I'll go ahead and check it out again just to verify.

Edit: This is one of the annoying CD/USB errors that I can reproduce with any CD with MP3s on it.

Step 1: HDD playlist playing
Step 2: Insert CD with MP3 music files. (data disc, not music disc) CF proceeds to read music files (which takes forever). Once finished, CF adds a count to the USB media count and it is highlighted blue as its playing.
Step 3: Click back to HDD media playlist. CF plays HDD media.
Step 4: Click back to the USB media playlist with a count of 1Displayed. CF displays "No USB storage devices found".
Step 4: Click on CD (in hopes of it being there, even though count is 0) CF proceeds to load the files yet again and adds another count to the USB media playlist, making it 2.

I should note, as I have before, that my optical drive is in the glovebox with a USB to IDE converter. Windows recognizes it as a DVD/CD-R drive and WMP etc all behave nicely.

Edit 2: I was able to get the CD count to freak out, too. This is with a normal store bought audio CD, too. Norah Jones, specifically.
Step 1: Have HDD media playing.
Step 2: Insert CD into drive.
Step 3: Wait a few secs, and press the CD playlist icon. (media hasnt auto started from putting the CD in quite yet) CF will highlight the CD icon, and wait. Media begins playing, CD count jumps to 2. Pressing the eject button ejects the physical media, but CF keeps the count at 2, as well as leaving the names of the tracks in the playlis. They are highlightable, also, but obviously do not play. Pressing eject again does not reduce the count from 2.

I'll keep at this some more and see what else I can find. ;-)

I have no idea where this problem lies, but I think I noticed it with 1.11 first.

For some reason CF is interfering with CFiG / iGuidance's ability to read my serial GPS. I have the GPS on COM1, and when I start up the system, it boots CF (non-shell) and CFiG auto starts within CF. When this happens I get an error from iGuidance asking me to check my GPS. Sometimes it starts working after a minute or two, sometimes not, and I have to reboot or restart CF a couple of times.

I know it's not my GPS because I can quit CF, open iG, and it starts working immediately. I know it's not loss of fix because my GPS is also powered constantly. (It's an old Rand McNalley and the acquire time sucks, so it has its own 5v supply)

Any ideas? I went out and got the S&T 2007 gps because i'm going out of town in the morning and that works fine (on COM3)

Originally Posted by midiwall

At 1.11, the problem was found out to be that CF's internal NAV software was grabbing COM1 even when it was disabled. You may want to either move your serial GPS or try reconfiguring CF's NAV to be some other port and see if that helps.

Can't really do either. The computer only has one physical serial port (COM1), and the only options for CF's NAV is 'None' (selected) and COM1.

This would explain the issues i've seen in the past, though. At one point I was running XPort to duplicate my GPS signal to iG and CF (so I could have speed on my VFD) and I think you're right, 1.11 broke stuff.

I had a problem with keyboard control in the navigation section all the time and hoped that it would just disappear with the new engine but it didn't. I’m not talking about the bug I posted for 1.12 already where the map took the focus completely, this is solved in 1.13 (thanks David). Now it is exactly the same as it has been before 1.12 but I could finally find the reason or at least a way to reproduce it so I hope it can be solved easily.

The problem: when entering nav-screen I get keyboard-control for 2-3 sec (i.e. can cycle through the buttons) then the kb-control stops working till I press tab which gives me 2-3 sec of kb-control again and so on. This never happened on my normal pc, just in the car and now I know the reason, cf runs on fullscreen in the car but never did on my desktop. As soon as the resolution is set to fullscreen or the fullscreen option is selected the bug occurs. When I set the resolution below fullscreen res everything works perfect. I can reproduce this on my normal pc as well.

I am having some issues with phonecontrol and accepting incoming calls.

I found that this issue was already posted a few months back on the phonecontrol forums, but I figured I would add it here as its one of the last few bugs ive noticed using phonecontrol... maybe you and zorro can figure it out.

Here is the thread from the forums there.

http://zhorvat.dyndns.org/PCForums/S...px?PostID=5064

"On an inbound call when I hit accept, the phone stops ringing, but the call isn't answered (on the callers side, it sounds like I picked up, but there's silence)"

My phone is a Sprint PPC-6700 with WM5.