Mine is still doing it. Only happens when the drives are spinning up. I'm wondering if it's related to what drives you have and how much power they draw?

Is anyone with only 1 drive getting this?

I have 2 players both with one drive. 1 is a 10GB the other is a 20GB. They both show the icon coming off standby.

both of mine doing it with one drive.only when i turn on from stand bye,not when it boots.

I have had the battery icon come on several times especially in the morning. So since my vehicle has a standard wimpy 65 amp alt. I had it upgraded to 195 amp G3? and for some reason still get the batt icon but just not as often, mostly in the morning. You could be suffering from short trip driving and it's not charging up the system each time or have the basic wimpy factory alternator. I do have 1200, 300 and 50 watt amps drawing off mine the guy that upgraded my alt. said if I needed more than 195 amps then somethings wrong, so I'm going to upgrade my stereo wires to 0/1 gauge, that should do it. Good luck with yours, check your wires.

both of mine do it only when hijack is on them.

Hmmm I've never tried my player w/o Hijack on it, I love it too much. I'll try it on my spare to check mine as well I could also check, since I have both, MK2 & Mk2a for any differences.

yes thats why I put it back on.I'm getting used to the icon now.I was just worried that it might hurt my drives.

definitely not wiring or alternator output.
Happens in my VW GTI and my Jeep identically. Jeep has an extra heavy duty alternator.
Problem disappears with the removal of hijack.

Oooo.. an idea: go into the Hijack menu, and set the "Hard Disk Detection" to "One or Two Drives". .. any difference in behaviour?

-ml

I'm not allowed that option because HiJack detects that I have 2 drives, but maybe that will help the 1 drive peeps.

still doing it.thanks for the idea though.

Yeah, here too.

Oh well I'm keeping Hijack on my player, small price to pay for cutting edge excellence. I think some of what I experienced was alternator related for it doesn't happen as often. The player doesn't pass out at stoplights anymore, just the icon appears w/no break in the sound. It'll soon be resolved I'm sure.
These guys are good.

bumping this for what its worth

im still getting this problem... for those semi-new to the thread, it is not a wiring problem or a current draw issue with your vehicle, or a 1/2 drive thing. or an issue with a component 'wearing out' since it is rectified if you go back to hijack 279 or earlier.

so it is some 'kernel talking to voltage sensor' thingy that got changed and hasnt been tracked down, or something like that.

anyway.. learnt to live with it like the others here.

Oh yeah, I've forgotten.. has anyone seen this on a Mk2a(RioCar), as opposed to a Mk2(EmpegCar) unit?

EDIT: seems to happen on mk2a's, now that I've read backwards in this thread.

Thanks

Okay, help me out with a theory here:

Can you reproduce this issue when the DIMMER settings are BOTH at 100% on the player (set dimmer too 100% with lights off, and again with lights on).

Next, try it again with BOTH dimmer settings at 50%.

Thanks.

I was able to reproduce the issue in both instances.

Is button illumination set to OFF in the hijack menu (regardless of whether you actually have illuminated buttons..)?

uh... no.
Hold on...

Still get same same.

Okay, I'll put out v333 shortly, with the fake_tuner fixed (I think), and a possible fix for this particular problem..

Cheers

and a possible fix for this particular problem..

I'm dying to know what you think might be causing the problem.

Well, the only possibilities are the diffs (posted earlier) from v279 to v280, which added synchronous access control to threads trying to write to the display controller. I suspect this "enforced serialization" is slowing things on in-car players for certain combinations of player setttings.

So, Hijack v333 now only enforces the access control when Hijack itself wants to write to the display controller -- to do this, it still has to track the player's accesses, and force those to wait when Hijack is in there, and vice versa.

Maybe this will help.

Cheers

Interesting!

Well, hijack v333 is out there now. Any change?

Thanks for all your help and time on this.it's still doing it on both my players.it not a big deal it just stays on for a few seconds then goes away.Thanks agian.

Just thought I'd bump this to see if there is any new news. I am having the same problems.

Bump.

Has anyone tried wiring the player directly to the battery to fix this?

I had my whole system rewired and removed the tunner and it is not doing it any more.

Okay, I have managed to reproduce this condition again (finally!) with a Mk2a in a Home Dock. But only when an Empeg Tuner is attached (special dock!).

Unplug the tuner, and all is normal. Plug in the tuner, and we get the battery icon off of standby condition. Happens with at least two of my three players (haven't bothered trying the third).

So.. I've been poking at the theory that the voltage takes longer to rise when a tuner is attached, and so if I simply disable powerfail detection a bit longer than the default of about 100ms after resume (from standby), the problem ought to go away again.

A 2-second delay definitely works for me! Now I'll try shorter delays. I may also revamp the entire "delay" mechanism, as currently the code (from original Empeg kernels) uses a 100ms in-line busy-wait loop, with interrupts disabled. Much better, at least for the coming from standby case, would be to simply schedule_timeout(HZ/10) for the same approximate delay in a friendlier fashion.

I'll poke at it some more, and release a fix (for my players anyway) in Hijack v352 later today.

Cheers