Mice With Mac (READ ONLY ARCHIVE)

[ianian]

I came upon this thread because of a nagging problem that has been happening ever since I got the VX Revolution. The delay after waking up thing. I got use to it but yeah once in a while I the waiting gets annoying. Using the mouse on a MacBook and Mac Pro and I get the same problems on both systems (OS 10.4.8, LCC 2.1.3). What made me finally research the problem on the Logitech forums was that 3 times today my brand new Mac Pro 2.66Ghz out right crashed. Crashed. I had to do the Hold Down Powerbutton to shut down the machine and then restart. I would get this as well on my MacBook. This would happen randomly upon waking up the mouse. Instead of stalling for the 20 seconds it would crash and have the screen go dark with it saying "Hold down power button to shut down..." There wasn't anything out of the ordinary going on with my systems when this happened. It would be just like any other time I would let the system go to sleep, from not touching it for a while. Then when I wake it up, pause 20 seconds then works or no pause and crash.

LCC 2.1.4 in the works?

[iPhone]

It is same symptoms correctly with ianian.

Problem is serious enough to can not use at all.

[jozero]

Can we get an update on what is happening ?

I sent in my system profile.

[ianian]

I'm no longer using my VX Revolution due to its incompaibility with my systems. I will go back to my one button mouse for now until Logitech steps up and fixes their broken product.

Message Edited by ianian on 02-04-200712:19 PM

[burhan]

So far, unable to reproduce it.  Still trying to see where the problem lies. 

[huvakraftSD]

I have been experiencing the same problem. If I leave the mouse unattended for a period of time, when I go to use the mouse again, on occasion it causes a kernel panic and I'm forced to restart. I rarely have the computer "sleep" since I use it to record via an eyeTV. Most of the time it runs with the screen blacked out, but fully awake.

I'm running 10.4.8 an an intel imac. Up until the installation of the mouse, I never experienced a kernel panic on this machine, and it runs 24/7.

I am at the point where I feel that I'm going to have to stop using the mouse. That being said, the mouse itself is great, and I'm sure the incompatibility lies in software.

[sdf1]

I am experiencing the same problem described in the previous posts...kernel panics upon wake with the mouse.

Oddly enough, the problem does not always occur when I try to recreate the scenario. Sometimes if I intentionally turn the mouse off (by holding the power button for 3 seconds) and then turning it on again, the crash will occur...while other times it works fine.

Obviously this issue is frustrating, and I've lost work due to the crashes.

I've read the statement that you believe the issue is related to 10.4.8...whether the problem is caused by a deficiency in MacOS or Logitech's mouse software doesn't matter to me, as long as the problem is being investigated and a solution is communicated (or a software updated is provided) when ready.

My system: MacBook Pro 2.33, 2 GB of RAM, MacOS X 10.4.8

Thank you support team for fielding these questions and providing responses...your continuing communication is appreciated.

[jozero]

"So far, unable to reproduce it. Still trying to see where the problem lies."

Pardon my confusion, but since we were told for 3 months it was being worked on diligently, how can you now say you are just trying to find the problem ??

[print61]

Could the problem lie with the battery guage? I have uninstalled the software a few weeks ago used the mouse without it. Now that the battery is weaker (not dead) it is taking 10 seconds to respond after sitting unused a while. Once again, without the driver installed.

Can the battery guage be disabled? I have 6 other Logitech wireless devices that respond quickly right up until the battery is completely dead.

[burhan]

jozero,

There have been some fixes incorporated into the latest build of LCC and things are being worked on.  There is still active interest in this issue and several things have been tried but the issue remains as some users continue to report it.  We're looking at various things including reproducing the issue.