Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Jam on linux

Jam on linux

Plan

Premium

Country

 

Device

Xenia 14

Operating System

Linux

 

My Question or Issue

Hello!, thanks for the app in Linux!. I have question my self when it could implement the function Jam, it's only this.
Greetings.

Reply
2 Replies

Same here, Jam are a cool feature but we can't start one in Linux, this is real sad and we feel like second-class users while we are paying like the others !

Update to jam feature.  I was able to start a jam, but was unable to join an existing jam.

When trying to join jam, app does receive something from opening the link (see below).  But nothing beyond this.  

02:19:10.843 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:11.044 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:13.002 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:13.043 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:13.245 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:15.387 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:15.393 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:15.593 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:17.381 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:17.393 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:17.595 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:20.108 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:20.143 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:20.344 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:24.920 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:24.943 D [f:764 ] ConnectManager cluster changed: reason NEW_DEVICE_APPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:25.145 D [f:294 ] ConnectState cluster changed: reason NEW_DEVICE_APPEARED
02:19:25.718 I [f:202 ] ConcurrentCollector ran mark cycle for 16.012ms, total: 48.035ms.
02:19:32.994 I [f:243 ] aq: LWS got LWS_CALLBACK_CLIENT_RECEIVE
02:19:33.043 D [f:764 ] ConnectManager cluster changed: reason DEVICES_DISAPPEARED ack id changed devices = <device number here unsure of full meaning so blanked it out>
02:19:33.244 D [f:294 ] ConnectState cluster changed: reason DEVICES_DISAPPEARED
02:19:40.041 I [f:1598 ] No product state was retrieved, unable to update

Workaround: join jam on phone and swap active device to desktop.

 

Suggested posts