search

Cathwyler / MagicRemoteService

Use your LG Magic Remote as a Windows mouse and control your PC with the LG Magic Remote from your LG WebOS TV
GNU General Public License v3.0
48 stars 2 forks source link

LG55EG9109, Blackscreen with small box, no inputs, no traffic? #11

Open MPX10L opened 7 months ago

MPX10L commented 7 months ago

Hi! I was very excited when I discovered this program! Thank you very much for working on it!

So, here is my problem: I installed everything using your description and I don't think I missed anything (I hope). When I start the app on the TV I get a black screen with a small version of my PC-Display at the top left corner. I also get no inputs from the remote on my PC.

I looked at the other resolved issues, but I was not able to solve mine.

My Setup: TV: LG 55EG9109 Software version: 04.06.75

PC: Win10 Pro Version 10.0.19045 Build 19045 Path: C:\Program Files (x86)\MagicRemoteService_1.2.2.2 (I have to run it as Admin)

image

image image image

I tried to log the traffic with wireshark. I saw something happening on port 9922 after pressing the "install on TV" button.

image

I was however not able to see anything happening on port 9942 when just moving the remote or pressing buttons on it. Although I am not sure if I set everything up correctly ... I am not exactly good with networking. image

Would be super happy if you could help me to get this working. :)

Cathwyler commented 7 months ago

Hi,

Thanks for all given infomation. Unfortunately, you have webOS version (2.2.0) which is running an older web engine (WebKit) and i am unable to debug on this older engine. See webOS version

I just made a new release 1.2.2.3 which will help to see what error occur on your TV app. Give a try at the new release and tell me if you see or not a new error message and if yes please send me a screenshoot.

Regards

MPX10L commented 7 months ago

Hi! Thanks for the quick answer! Ohh I see, I just read the firmware version and thought I had version 4.

I deleted the app from the TV, cleared the cache and restarted the TV. I stopped the app on my PC, stopped the service within the taskmanager and deleted the folder. I extracted the new folder, started the new version, checked that all settings were the same and hit "install on TV".

On the TV I got the black screen with the little box top left. No error message. I restarted the TV, opened the app and got the following error message: "ERROR - Failed to add device [Already exist same device when added device]"

I once saw this message with the version 1.2.2.2 as well, but forgot to mention it.

Again, Wireshark did not catch any communication on port 9942.

Not sure if it matters: I am using two displays: My PC-monitor and the TV. They are set up as mirrored displays.

PXL_20231121_204844797

Cathwyler commented 7 months ago

Please give a try at this one 1.2.2.4 and tel me if you see something new.

Regards

MPX10L commented 7 months ago

No real difference as far as I can tell. I did not see the "Failed to add divice"-Error again. (But I also didn't get it everytime before and I am not exactly sure how to reproduce it.)

Btw, there is always some traffic between the TV and my PC. Just not on the port 9942 and it does not seem to be correlated to actions on the remote control. If you think that this might be interesting, I could maybe send you the capture file.

Thanks for all your effort. I know the TV is not exactly new but it is an OLED an still looks pretty amazing. :)

Cathwyler commented 7 months ago

Finally found a way to debug on webOS 1.2.0 and 2.0.0 and i solved planty of bugs.

Can you give a new try 1.2.2.5 ?

Regards

MPX10L commented 7 months ago

Progress! The small top-left box is now gone and the image scales to the entire screen.

But still no response to actions of the remote. Do you need some info form the inspect-window?

Cathwyler commented 7 months ago

Nice to see some progress finally.

I inadvertently deleted an else statment after my tests. Should works better now 1.2.2.6

With inspector you can see if there is any exception happening on the TV app. I added this button in case i can’t reproduce a bug with the simulator. You can see if an exception occured if you press the bottom left button. Sans titre

But be carefull, if you restart MagicRemoteService on PC you need to close all inspector else it could result in a binding connection error due to a child "Node.js" proccess not closing.

If you don’t see any logs, this is normal and it’s a good sign because I disable debug messages for the release version.

MPX10L commented 7 months ago

Sorry for taking so long. Finally got around to trying it, but I didn't notice any difference. (TV shows mirror image of desktop but no reaction to the remote.) The inspector window shows the following. image

At some point I noticed there was an error window but I am not sure at what point exactly it appeared. image

I deleted the app from the TV, cleared the cache and re-installed it again. No error and no changed behaviour.

And then I got this one after switching off the TV. (Inspector window still being open.) image

Cathwyler commented 7 months ago

You don't have any exception or error. Theses css errors on the right are normals and ares-inspect dialog errors are not important too.

I think i understand what is happenning. The undocumented input subscription API seems to not work with your webOS version. The TV app is not initiating the connection at all.

To gain times i send you a special build with debug and force connect activated. MagicRemoteService_1.2.2.7_Debug_ForceConnect.zip

Can you send me the consol log information from inspector to confirm my therory ?

MPX10L commented 7 months ago

image

This time I did get some mouse actions! The normal windows mouse pointer disappeared. Things happened when clicking and scrolling on the remote. But the movement of the remote did not get transfered. I could only click where I last had my PC mouse (I think).

Cathwyler commented 7 months ago

Progress again.

I think i understand what happen with the connection and the mouse. It could take some try to get it working properly.

Edited (Changed my mind on something) MagicRemoteService_1.2.2.7_Debug_ForceConnect.zip

Again, can you send me the console log information from inspector to confirm my theory? Thanks for the time spend on it.

MPX10L commented 7 months ago

directly after installing: image

after restarting the TV image

At first, it didn't work, but after some minutes it started working again (invisible cursor, clicking and scrolling works, mouse movement does not work).

(Same instance as the screenshot above:) image

No, thank YOU! You are doing the actual work here. :)

Cathwyler commented 7 months ago

I'm pretty confident in this one.

MagicRemoteService_1.2.2.7_Debug_ForceConnect.zip

Even if it work, can you send me the console log information from inspector ? i need to confirm some error code.

If you have some connection issue, you can try kill all node.js process in your task manager and restart inspector.

MPX10L commented 7 months ago

Right after install:

restart TV: I had some connection issues at first. image

This will probably my last entry for a bit more than a week, as I'll be on a work trip. Have a happy second and thrid advent!

Cathwyler commented 7 months ago

No probs, take your time.

The problem is the application is thinking she is in background. I send you another build. This one for sure will not work it but will help me to understand why AppVisible function is not working on your webOS Version.

MagicRemoteService_1.2.2.7_AppVisibleLog.zip

Have a nice trip.

MPX10L commented 6 months ago

Hi! I am back from my trip and can test again. I saw that you now have a second tester with an old TV and did quite some changes. :) Let me know what you want to be tested.

Cathwyler commented 6 months ago

Hi

Can you test this one ? MagicRemoteService_1.2.2.9APILogForceConnect.zip

I miss the begining and mouse move log from other tester's test.