Razer Abyssus 2014 support #114
Comments
|
Are you willing to help us get support? As it's hard to code for it without owning one. |
|
Yes, I could help with it, of course. |
|
Alright. I will do my best :) |
|
That's all we ask ;). I have decided to go through the wiki page and finally add the images it should of had ages ago. |
|
I guess a virtual box is essential to capture things, right? |
|
Yep, or vmware but virtualbox is easier in my opinion |
|
And installing windows in a VM |
|
Alright. |
|
Its a bit involved but is all that can be done, short of you sending me said device that is lol. |
|
I don't understand the sentence completely :) |
|
I'm just saying its a lot of work just to get a mouse working 😉. The only other thing you could do is mail me your mouse and I do all the hard work. |
|
Ah, alright. But I guess it is rather easy compared with other devices, as it does not have many functions. I am currently downloading a Windows image. |
|
Well it should take near no effort once I have some packet captures as my Once you have the windows installed, install synapse. Once synapse is As your giving the VM full control over your mouse, the mouse wont work on On Thu, Apr 21, 2016 at 10:09 AM, Claudius Ellsel notifications@github.com
|
|
Alright. Good that I have a spare mouse |
|
Installed synapse now. Will continue later when I have time again. |
|
After installing the extension pack from Virtualbox I managed to pass the mouse through to Windows. It seems it got recognized. Shell I upload the screenshot zip here? |
|
yeah here is fine |
|
Ok. It just installed the driver. |
|
Alright. Took screenshots from every page of the driver I could access. |
|
Ok whats the output from |
|
Ok not being able to speak or read german this is what I think we've got.
Am I right? |
|
Correct (Checkbox to toggle X and Y DPI is translated: activate sensibility for x- and y- axis, don't know, whether this is the same). |
|
OK now you need to run also output of |
|
Follow the rest of the Wiki to result in some packet captures |
|
relevant output of lsusb: Bus 001 Device 003: ID 1532:0042 Razer USA, Ltd |
|
Started wireshark and selected all usb entries. Applied filter usb.bus_id == 1 && usb.device_address == 3 |
|
What do I need to do now? Just send some commands to the mouse from synapse and log with wireshark? Do I need to protocoll which commands I sent at which time? |
|
Ahh I didnt know if there was a limit. If you have google drive that isnt a bad place to put them |
|
I upload them to jumpshare as I don't want to mess up Google drive. Should be fine as well. |
|
BTW: There is also an option in the software to automatically deactivate lighting when screen turns off. Is this a driver specific or only software feature? |
|
That's part of the Synapse software |
|
Ok |
|
Here is the link: http://jmp.sh/bvn13aQ I did a capture of just ticking the X Y checkbox, probably not needed. Also note that I first slided the Y slider and after that the X slider. |
|
Also with "frequeny checkbox" (filename) I mean "frequency dropdown". |
|
Ok I've got the logo and the refresh interval drop down. But the other captures didn't contain anything useful. The filter Can you redo all of them but the logo. and for the refresh rate ones can you note down what option you selected as I have the refresh rate but I dont know what lines refer to what option. |
|
Im specifically after the packets of 154 bytes of length. |
|
In the dropdown menu I started with the lowest rate (I think 125) and went up to the highest. I will redo all captures with the new filter. |
|
Dropdown List: I didn't get data for the sliders with your filter applied. |
|
I also tried usb.bus_id == 1 && usb.device_address == 3 && (usb.endpoint_number == 0x00) |
|
Here is a short sample of me recording a short random change of clicking on the DPI slider. Maybe you can identify some characteristic patterns leading to a good filter. |
|
Tomorrow I can continue testing. |
|
Nothing in the DPI. Got the Refresh Rate done though. Try the DPI again without any filters, it will collect a mass of data but it might get something. I am starting to think that you mouse might not actually change DPI in hardware but it will take more packet captures to prove that. |
|
I also thought that it might only change it in the software, but I think I noticed a change of behaviour when switching back to the Linux system. I will collect some data without a filter. |
|
After some testing you might be right that it is not applied in the hardware. It seems to have no effect when changing to Linux. Although I thought that DPI has increased after connecting to synapse for the first time and switching to Linux after that. |
|
Here is a capture without filters. I also closed the synapse software at the end. After closing it the applied settings persist. However when making the mouse available to Linux and then again to the VM the settings seem to be reset until I restart the synapse software. |
|
Nothing again well there was a logo change and refresh rate change but that's it. From what you've said it could quite possibly be that synapse is just changing the windows mouse speed, or doing something clever in software. The driver is currently undergoing a massive overhaul, ill add this to it at some point soonish. |
|
Strange. I did not change the logo nor the refresh rate. I just changed DPI and closed the software after it. I also opened the Windows Mouse speed window and it does not appear to be changed by the software. So it is probably some hidden thing, if it is only software specific. |
|
I guess it is pretty clear that the changes are only software changes, right? |
|
So I just think that I noticed a DPI change on Linux: There is a difference when deactivating pass through with synapse open and synapse closed before. On the Linux system is a change in DPI for me, so a hint that there is something stored on the mouse probably. |
|
I know synapse sets all settings to the last settings it knows which is probably why it set the refresh rate and the logo. There could be, I've emailed my razer contact to see if they are willing to shed any light on the issue |
|
Ok, this is probably the reason. Hopefully your contact can help. |
|
I shall say for now this issue is closed. I have the codes for refresh rate but want to investigate that further + am talking to razer about mice in general too. As for the controller app, well I've got alot of things I plan to do before updating that to work with more devices. |
|
Thanks for the help and support for the device. Any news from your contact, whether setting DPI and acceleration is supported or only software specific? |
|
No news yet, they have only discussed keyboards with me so far, am trying to move the topic onto mice but the 7hour time difference makes the conversation take days. Will let you know if I ever hear anything relating to DPI |
|
Alright |
I post this as an issue to express my demand for support of the Razer Abyssus 2014. Maybe it can get supported one day.
The text was updated successfully, but these errors were encountered: