Command line switch for hiding main window on startup about solaar

[pwr]

Hm, the main window should be hidden at startup if the systray icon appears. I assume you're using the latest version? What distro, and what desktop environment?

As for the battery -- I don't have a Performance MX to test with, but I think this model does not report the battery percentage, just a sort of a general status (good/bad), and there's no documentation on the exact values.

To confirm this, please start solaar with "-dd". You'll get a lost of debug messages, look for something like "failed to read 'battery' from default register 0x0D, blacklisting" -- this means there's no battery percentage available.

To read the battery status register, you can run "echo '10 01 8107 000000' | tools/hidconsole --hidpp" (you'll need to download the solaar source for this, hidconsole is not available in the packages).

[terwarf]

Thanks for the quick response.

I'm using the git version.
Distro is openSuSE 12.2 x86_64 with KDE 4.10.60, python is 2.7.3
On startup window keeps open and DPI settings won't be restored (not sure if the software is supposed to restore them).

As for the battery:
You`re right, I get the "failed to read battery" string:

alex@linux-7jg6:~/bin/Solaar/bin> ./solaar -dd
2013-01-16 18:24:24,646    ERROR [MainThread] root: Could not find any typelib for Notify
2013-01-16 18:24:24,769     INFO [ReceiverListener] LUR.listener: started with <Receiver(/dev/hidraw0,T9)> (9)
2013-01-16 18:24:24,770     INFO [ReceiverListener] listener: notifications listener has started
2013-01-16 18:24:24,770    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 8000 FFFFFF]
2013-01-16 18:24:24,773    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8000 000000]
2013-01-16 18:24:24,773     INFO [ReceiverListener] LUR.receiver: device notifications enabled
2013-01-16 18:24:24,773    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 8002 020000]
2013-01-16 18:24:24,777    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 4104 121A10]
2013-01-16 18:24:24,777    DEBUG [ReceiverListener] LUR.listener: queueing unhandled Notification(1,41,04,121A10)
2013-01-16 18:24:24,779    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8002 000000]
2013-01-16 18:24:24,779    DEBUG [ReceiverListener] listener: status_changed <Receiver(/dev/hidraw0,T9)>: active No devices found. (1) 
2013-01-16 18:24:24,780    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 200000]
2013-01-16 18:24:24,783    DEBUG [ReceiverListener] LUR.base: (9) => r[11 FF 83B5 200708101A0400020600000000000000]
2013-01-16 18:24:24,783     INFO [ReceiverListener] LUR.receiver: found device 1 (101A)
2013-01-16 18:24:24,783    DEBUG [ReceiverListener] LUR.base: (9) pinging device 1
2013-01-16 18:24:24,784    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 001D 000082]
2013-01-16 18:24:26,207    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 8F00 1D0100]
2013-01-16 18:24:26,208    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 400000]
2013-01-16 18:24:26,212    DEBUG [ReceiverListener] LUR.base: (9) => r[11 FF 83B5 400E506572666F726D616E6365204D58]
2013-01-16 18:24:26,212    DEBUG [ReceiverListener] listener: status_changed <Receiver(/dev/hidraw0,T9)>: active 1 device found. (0) 
2013-01-16 18:24:26,213    DEBUG [ReceiverListener] LUR.status: <PairedDevice(1,Performance MX)>: connection notification: software=True, encrypted=False, link=True, payload=False
2013-01-16 18:24:26,213    DEBUG [ReceiverListener] listener: status_changed <PairedDevice(1,Performance MX)>: active  (1) 
2013-01-16 18:24:28,217    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 210000]
2013-01-16 18:24:28,220    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8F83 B50300]
2013-01-16 18:24:28,220    DEBUG [ReceiverListener] LUR.base: (9) device 0xFF error on request {83B5}: 3 = invalid value
2013-01-16 18:24:28,221    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 220000]
2013-01-16 18:24:28,224    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8F83 B50300]
2013-01-16 18:24:28,224    DEBUG [ReceiverListener] LUR.base: (9) device 0xFF error on request {83B5}: 3 = invalid value
2013-01-16 18:24:28,224    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 230000]
2013-01-16 18:24:28,228    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8F83 B50300]
2013-01-16 18:24:28,228    DEBUG [ReceiverListener] LUR.base: (9) device 0xFF error on request {83B5}: 3 = invalid value
2013-01-16 18:24:28,228    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 240000]
2013-01-16 18:24:28,232    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8F83 B50300]
2013-01-16 18:24:28,232    DEBUG [ReceiverListener] LUR.base: (9) device 0xFF error on request {83B5}: 3 = invalid value
2013-01-16 18:24:28,232    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 250000]
2013-01-16 18:24:28,236    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 8F83 B50300]
2013-01-16 18:24:28,236    DEBUG [ReceiverListener] LUR.base: (9) device 0xFF error on request {83B5}: 3 = invalid value
2013-01-16 18:24:28,236    DEBUG [ReceiverListener] listener: polling status: <Receiver(/dev/hidraw0,T9)> [<PairedDevice(1,Performance MX)>]
2013-01-16 18:24:28,237    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 030000]
2013-01-16 18:24:28,240    DEBUG [ReceiverListener] LUR.base: (9) => r[11 FF 83B5 0368A19F6E0106070000000000000000]
2013-01-16 18:24:28,240    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 81F1 010000]
2013-01-16 18:24:28,244    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 81F1 011201]
2013-01-16 18:24:28,244    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 81F1 020000]
2013-01-16 18:24:28,248    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 81F1 020019]
2013-01-16 18:24:28,248    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 81F1 040000]
2013-01-16 18:24:28,252    DEBUG [ReceiverListener] LUR.base: (9) => r[10 FF 81F1 040214]
2013-01-16 18:24:28,252    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 FF 83B5 300000]
2013-01-16 18:24:28,256    DEBUG [ReceiverListener] LUR.base: (9) => r[11 FF 83B5 30E367D0E00400000001000000000000]
2013-01-16 18:24:28,256    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 81F1 010000]
2013-01-16 18:24:28,286    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 81F1 011501]
2013-01-16 18:24:28,286    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 81F1 020000]
2013-01-16 18:24:28,392    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 81F1 020062]
2013-01-16 18:24:28,393    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 81F1 040000]
2013-01-16 18:24:28,496    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 81F1 040211]
2013-01-16 18:24:28,497    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 810D 000000]
2013-01-16 18:24:28,600    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 8F81 0D0200]
2013-01-16 18:24:28,601    DEBUG [ReceiverListener] LUR.base: (9) device 0x01 error on request {810D}: 2 = invalid address
2013-01-16 18:24:28,601    DEBUG [ReceiverListener] LUR.base: (9) pinging device 1
2013-01-16 18:24:28,601    DEBUG [ReceiverListener] LUR.base: (9) <= w[10 01 001C 000096]
2013-01-16 18:24:28,706    DEBUG [ReceiverListener] LUR.base: (9) => r[10 01 8F00 1C0100]
2013-01-16 18:24:28,707  WARNING [ReceiverListener] LUR.hidpp10: <PairedDevice(1,Performance MX)>: failed to read 'battery' from default register 0x0D, blacklisting

The reading results in the following output:

alex@linux-7jg6:~/bin/Solaar/tools> echo '10 01 8107 000000' | hidconsole --hidpp
.. Opening device /dev/hidraw0
.. Opened handle 3, vendor 'Logitech' product 'USB Receiver' serial None.
.. HID++ validation enabled.
<< (   0.023) [10 01 8107 000000] '\x10\x01\x81\x07\x00\x00\x00'
>> (   1.343) [10 01 8107 050000] '\x10\x01\x81\x07\x05\x00\x00'
.. Closing handle 3

While the battery indicator on the mouse reports "full" (3 of 3 LED's) - i will fire this one again as soon as the battery indicator changes.

[pwr]

Okay, so the good news is the 0x07 register is the same as on the M510 mouse (the battery does not work on that model either). There is a user with that mouse, and the register reads 0x05 on it as well. Unfortunately, there isn't much I can do until I know, at least, more possible values.

I'll be doing some testing with KDE to see what could be wrong with the systray icon.

[terwarf]

So am I readding the wrong Adress?

With the power indicator down to two LED's it seems to give the same reading as last time...

alex@linux-7jg6:~/bin/Solaar/tools> echo '10 01 8107 000000' | hidconsole --hidpp
.. Opening device /dev/hidraw0
.. Opened handle 3, vendor 'Logitech' product 'USB Receiver' serial None.
.. HID++ validation enabled.
<< (   0.020) [10 01 8107 000000] '\x10\x01\x81\x07\x00\x00\x00'
>> (   1.995) [10 01 8107 050000] '\x10\x01\x81\x07\x05\x00\x00'
.. Closing handle 3

[pwr]

No, I think it's the right address -- the Windows Logitech software shows no battery percentage either, but reads the 0x07 register before displaying somethink like "good"/"excellent"/etc (from some other reports I've read on the web).

My guess is that the values returned from that register signify, each, a rather wide range of the battery charge; but I don't know if 4 means a lower or higher charge than 5, what's the highest possible value, and so on. So unfortunately, until I know more about the possible values returned from that register, I don't know what to display about the battery.

[pwr]

I think I've fixed the problem with the main window showing -- could you check with the 0.8.7 version?

[terwarf]

Confirmed - 0.8.7 hides the main window on startup.

Thank's a lot...

[pwr]

Okay, I'll close this bug for the systray issue. The battery issue is still open (#5).