[ROOT] K ROOT on T-JZ* and T-HK* fws up to 1169

[zoelechat]

Don't forget TV needs user approval to receive keys/commands, once for every new/unknown device (in case you're not looking at TV )

rccli_allow.png

when i run the comand un comand line its saying ok

App never "says ok"

Code: Select all

C:\temp>rccli 192.168.1.7 -w blah0blah1.ROOTK
rccli v0.2 for Samsung TV series K/M/Q by zoelechat @ SamyGO
* Requesting widget launch with ID:blah0blah1.ROOTK to 192.168.1.7 ...

C:\temp>

ps: all builds for every platform have been tested. Windows->check firewall maybe...

[asiersan]

when i say ok im saying as expected......, but widget is not runing

C:\>rccli 192.168.1.6 -w blah0blah1.ROOTK
rccli v0.2 for Samsung TV series K/M/Q by zoelechat @ SamyGO
* Requesting widget launch with ID:blah0blah1.ROOTK to 192.168.1.6 ...

C:\>

[zoelechat]

OK. Any useful report otherwise?

[racocvr]

On T-HKMFK nothing happens..

Code: Select all

D:\>rccli.exe 192.168.0.51 -w blah0blah1.ROOTK -d
rccli v0.2 for Samsung TV series K/M/Q by zoelechat @ SamyGO
libwebsocket_client_connect: direct conn
__libwebsocket_client_connect_2
__libwebsocket_client_connect_2: address 192.168.0.51
connected
ext x-webkit-deflate-frame vetoed
GET /api/v2/channels/samsung.remote.control?name=cmNjbGk= HTTP/1.1
Pragma: no-cache
Cache-Control: no-cache
Host: 192.168.0.51
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: KSO+hOFs1q5SkEnx8bvp6w==
Origin: 192.168.0.51
Sec-WebSocket-Protocol: dumb-increment-protocol
Sec-WebSocket-Extensions: deflate-frame
Sec-WebSocket-Version: 13


* Requesting widget launch with ID:blah0blah1.ROOTK to 192.168.0.51 ...
Websocket connections opened
lws_client_interpret_server_handshake: cPprotocol='dumb-increment-protocol'
no client extensions allowed by server
rx 241 '{"event":"ms.channel.connect","data":{"id":"e4dfbb60-4617-11e8-ab81-7dbbd2892f2e","clients":[{"id":"e4dfbb60-4617-11e8-ab81-7dbbd2892f2e","connectTime":
1524392907286,"attributes":{"name":"cmNjbGk="},"deviceName":"cmNjbGk=","isHost":false}]}}'
sending close indication...
sent close indication, awaiting ack
Exiting ...
libwebsocket_close_and_free_session: just_kill_connection
not calling back closed due to old_state=0
libwebsocket_close_and_free_session: just_kill_connection
calling back CLOSED
LWS_CALLBACK_CLOSED

Code: Select all

localhost~ # dlogutil WasClient:*
arc = 2, optind = 1 ,Kb 0, rotate 4
--------- beginning of /dev/log_system
--------- beginning of /dev/log_main
W/WasClient(  932): was_sso_client.cpp: sso_get_guid(667) > sso_get_guid START
W/WasClient(  932): was_sso_client.cpp: sso_get_login_state(638) > sso_get_login_state START
W/WasClient(  932): was_sso_client.cpp: sso_get_login_state(660) > sso_get_login_state END
W/WasClient(  932): was_sso_client.cpp: sso_get_guid(685) > SSO not login, please login first.
W/WasClient(  932): was_sso_client.cpp: sso_get_guid(667) > sso_get_guid START
W/WasClient(  932): was_sso_client.cpp: sso_get_login_state(638) > sso_get_login_state START
W/WasClient(  932): was_sso_client.cpp: sso_get_login_state(660) > sso_get_login_state END
W/WasClient(  932): was_sso_client.cpp: sso_get_guid(685) > SSO not login, please login first.

But no user approval message is shown on the tv


On T-JZM widget is launched (also without any user approval message)

Code: Select all

D:\>rccli.exe 192.168.0.52 -w blah0blah1.ROOTK -d
rccli v0.2 for Samsung TV series K/M/Q by zoelechat @ SamyGO
libwebsocket_client_connect: direct conn
__libwebsocket_client_connect_2
__libwebsocket_client_connect_2: address 192.168.0.52
connected
ext x-webkit-deflate-frame vetoed
GET /api/v2/channels/samsung.remote.control?name=cmNjbGk= HTTP/1.1
Pragma: no-cache
Cache-Control: no-cache
Host: 192.168.0.52
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: KSO+hOFs1q5SkEnx8bvp6w==
Origin: 192.168.0.52
Sec-WebSocket-Protocol: dumb-increment-protocol
Sec-WebSocket-Extensions: deflate-frame
Sec-WebSocket-Version: 13


* Requesting widget launch with ID:blah0blah1.ROOTK to 192.168.0.52 ...
Websocket connections opened
lws_client_interpret_server_handshake: cPprotocol='dumb-increment-protocol'
no client extensions allowed by server
rx 241 '{"event":"ms.channel.connect","data":{"id":"f5cff980-4617-11e8-b8d9-6ddb9367c9c1","clients":[{"id":"f5cff980-4617-11e8-b8d9-6ddb9367c9c1","connectTime":
1524392935704,"attributes":{"name":"cmNjbGk="},"deviceName":"cmNjbGk=","isHost":false}]}}'
sending close indication...
sent close indication, awaiting ack
Exiting ...
libwebsocket_close_and_free_session: just_kill_connection
not calling back closed due to old_state=0
libwebsocket_close_and_free_session: just_kill_connection
calling back CLOSED
LWS_CALLBACK_CLOSED

[zoelechat]

Thanks
Can you at least send RC keys to T-HKMFK with rccli? Otherwise it's possible it doesn't have server capabilities. Actually these low-ends look not capable of much...
Would be worth to try latest Smart View app on mobile to see what it does offer as features towards HKMFK (remote control? launch widgets?).

[racocvr]

Sending RC keys works ok on T-HKMFK but launching app is not present even in the Smart View app, only Picture/Video/Music share and Remote Control.

[zoelechat]

Now we know not capable, again too bad for HKMFK autostart

[zoelechat]

Well, instead of using rccli widget launch feature, it's still possible to use it to send KEY_HOME + KEY_RIGHT * n + KEY_ENTER to launch widget

[juusso]

result is unpredictable indeed

[mastero122]

New widget starts reliably. No spinning wheel issue (tried several times). Replacement recommended. No autostart anyway...