Keyboards and Keyboard/Mice Combo Sets

[kirkmc]

I have a new solar keyboard, and I noticed in Console that Solar Service is writing literally thousands of log entries. I get entries such as this, several times per second:

9/12/11 4:22:32.419 PM Solar Service: Event = 1 device index = 1

9/12/11 4:22:32.478 PM Solar Service: Input data callback for device 0x1912440

9/12/11 4:22:32.479 PM Solar Service: End of data

Plus entries like this sometimes when I type:

9/12/11 4:22:52.754 PM [0x0-0x2d02d].com.Logitech.Solar-Service: [0x1019125a0]: 20 01 01 00 33 00 00 00 00 00 00 00 00 00 00 

9/12/11 4:22:52.754 PM [0x0-0x2d02d].com.Logitech.Solar-Service: [0x1019125a0]: 20 01 01 00 33 09 00 00 00 00 00 00 00 00 00 

9/12/11 4:22:52.754 PM [0x0-0x2d02d].com.Logitech.Solar-Service: [0x1019125a0]: 20 01 01 00 09 00 00 00 00 00 00 00 00 00 00

 9/12/11 4:22:52.754 PM [0x0-0x2d02d].com.Logitech.Solar-Service: [0x1019125a0]: 20 01 01 00 00 00 00 00 00 00 00 00 00 00 00 

9/12/11 4:22:52.754 PM [0x0-0x2d02d].com.Logitech.Solar-Service: [0x1019125a0]: 20 01 01 00 0c 00 00 00 00 00 00 00 00 

This is the kind of thing that will eventually lead to very large log files, and is a Very Bad Thing. Can anyone explain what's up, and why this is happening? 

[ljimber]

Just got my K750 for the Mac a few days ago and also noticed the same thing. 

Every key stroke writes to the system.log file???? Way too VERBOSE!

Also my VX Nano does not seem to support unified usb

Waiting for a fix.

[MT-]

Yeah, this seems like the developers forgot to remove their debug statements before making the software available for download. Seems like something they could fix easily - would've thought a new release would be out by now to fix it

[JML54]

Same problem.  Even if the Solar keyboard is NOT connected, and even if the Solar.app is removed, the entries continue to be generated until they number 4001.  I've submitted a query to Logitech.  I hope they do something.  This is a constant drain on system resources, running from single to double digits.  

Some entries are for Logitech.Solar-Service and some are for Solar Service.

[JML2]

(Same user as JML54 - logitech username gets screwy).

I used the Activity Monitor to find that the Solar Service is running from this location: 

/Users/{username}/Library/Application Support/Logitech/

I zipped a copy, stopped the service, and then deleted it.  All seems OK so far, but I don't have the keyboard connected at home.  Will see if there's a problem on Monday at work.

[JML2]

I looked into the Solar App package.  The "Solar Service.app" is there, so it was installed when the master application was installed.  But it wasn't REMOVED when the app was removed.  Running AppCleaner shows the dependent folders and files, but somehow it wasn't removed.

So it appears to me the optional Solar App is faulty, and of course you can remove it whenever you want, as long as you remove EVERYTHING.  All it does is monitor the battery level of the keyboard, and if you don't have a problem, don't bother with it.

[JML54]

Logitech support, what is wrong with you?

I filed a formal request for support on this problem, and then I received a request for more information.  I supplied EXACTLY the information listed in this thread - the logging, the problem with removal of  Solar.app, etc., and then I received a notice that the request was "solved."  As I noted in response to that, NOTHING has been solved, or even acknowledged.  And you closed the request again.

I will never understand this company.  Superbly designed hardware, often troubling software for Mac and Windows, and the world's worst support for software problems.

[zigmoo]

I agree VERBATIM with the post above.

[dafire]

Was there an update ?

It's not longer spamming the keys but spamming every second 7 lines containing the current energy level and light levels

Apr 19 09:10:02 charon-win Solar Service[400]: Input data callback for device 0x122920
Apr 19 09:10:02 charon-win Solar Service[400]: End of data
Apr 19 09:10:02 charon-win Solar Service[400]: Event = b device index = 1
Apr 19 09:10:02 charon-win Solar Service[400]: ModuleFeature_x4301::BatteryLightFsm_1(): m_LastAveBattLvl 100.00
Apr 19 09:10:02 charon-win Solar Service[400]: ModuleFeature_x4301::BatteryLightFsm_1(): new_state 1 m_LastBattState 1
Apr 19 09:10:02 charon-win Solar Service[400]: device: 49CAC770 battery capacity: 100%
Apr 19 09:10:02 charon-win Solar Service[400]: device: 49CAC770 Illuminance: 168lx

it looks like it is only spamming it some time after the light button was clicked .. after about 4 minutes it stops logging it.

[stevek1977]

same problem here.  can't believe logitech hasn't fixed this yet.

the logs are dumped to /var/log/system.log

May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40
May 16 15:55:18 MGWALWDV13 Solar Service[393]: End of data
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Event = 2 device index = 1
May 16 15:55:18 MGWALWDV13 Solar Service[393]: Input data callback for device 0x13fa40