[solved] MPTvScheduler - Android client for MediaPortal and TvServer (2 Viewers)

[bartmanson]

Can you tell me if it happened when you watched live TV or recordings?

I'm not sure and I'm currently at work. Will try/test this evening and give feedback. I think it was, when I was neither watching live tv or recordings but fiddling with settings. But as I said I'm not sure and will give feedback this evening.

Btw: I'm running MPExtended 0.5.4. Do I need 0.6 in order for the app to work correctly? I thought that it works with 0.5.4 as well ...?

 

[regeszter]

I'm not sure and I'm currently at work. Will try/test this evening and give feedback. I think it was, when I was neither watching live tv or recordings but fiddling with settings. But as I said I'm not sure and will give feedback this evening.

Ok. Please check that if the MPextended plugin is enabled in SetupTv.

I'm running MPExtended 0.5.4. Do I need 0.6 in order for the app to work correctly? I thought that it works with 0.5.4 as well ...?

The 0.5.4 is better (stable) now. The 0.6.0 is beta but you may try it. The 0.6.0 needs for delete recording only.

 

[bartmanson]

Ok. Please check that if the MPextended plugin is enabled in SetupTv.

Ah, OK. That plugin is definitely not enabled. I didn't know there is a server plugin for MPExtended. Will activate it this evening and report back.

 

[regeszter]

Ok. Please check that if the MPextended plugin is enabled in SetupTv.

Ah, OK. That plugin is definitely not enabled. I didn't know there is a server plugin for MPExtended. Will activate it this evening and report back.

That plugin the interface between MPExtended and TV Server Powerscheduler.

 

[regeszter]

Well, it´s obvious: Black on dark blue won´t be good visible

Is it better?

 

[catavolt]

 

[bartmanson]

OK, here we go.

Sorry for the delay. I could't test yesterday because my significant other recorded something and I couldn't restart the tvserver

But, I did some testing this morning and these are the results:

First, I changed the MAC address to capital letters and now WoL works. I will check this later and change it back to lower letters. If it doesn't work then you should maybe add something like sMACAddress.toUpper() to your code . Maybe case-sensitivity is related to the NIC vendor? I think mine is a Intel.

Second, I did some testing and here is what I did (TVServer logs attached; The MPExtended log has no entry for the respective time slot between 9:02 and 9:51).
Enable the MPExtended-Server-Plugin and reboot the server.

9:02: Start app -> Serves wakes up. App stays on "home page" (the one with the menu)
9:05: Server goes into standby although app is still opened
9:06: Start app -> Serves wakes up. App stays on "home page" (the one with the menu)
9:09 Server goes into standby although app is still opened
9:09: Start app -> Serves wakes up. Switch to "Now/Next" screen
9:13 Server goes into standby although app is still opened (and still on Now/Next)
9:15 Start app -> Serves wakes up. Switch to "EPG" screen. Server stays on.
9:21 Switch app from EPG to Home Screen. Server stays on.
9:26 End app. Server stayed on until 9:51 because MPExtended was preventing the standby although the app (and no other MPExtended client) was not active.

Summary: It seems a little bit random, if MPExtended reports correctly whether the app is running or not.

Please let me know if you need additional testing.

HTH
BartManson

Update: Replace TVService.zip. It now contains the correct server log.

 

[regeszter]

But, I did some testing this morning and these are the results:

It seems it is a MPExtended bug. Some API calls do not call powerscheduler to prevent standby.

 

[bartmanson]

It seems it is a MPExtended bug. Some API calls do not call powerscheduler to prevent standby.

Hm. OK. Do you know if MPExtended is still under development?

Anyway, I did some more testing regarding WoL and that is really weird:

1. Started the app on my smartphone (MAC in lower case): Server not starting (as expected)
2. Changed the MAC to upper case, closed it and started it again: Server not starting (that was not expected ... )
3. Started the app on my tablet. WoL worked all morning during the other tests: Server not starting (well that was really not expected AT ALL )
4. think ... think ... think ... Maybe it's related to WLan. Solution: Install WoL app on my tablet from play store. I took the first one in the row when searching for "WoL".
5. Configure htpc in WoL app (copy MAC from mptvscheduler, just to be sure that it is the same). Push the htpc icon -> server starts.
6. Wait until server goes to standby. Start mptvscheduler app on tablet -> Server starts. WTF?
7. Wait until server goes to standby. Wait some longer time (20min or so). Start mptvscheduler app -> server doesn't start.

Here I stopped testing because the apps behavior seems quite random to me. All I can say, that all other clients or WoL programs do _always_ wake the server. I have several other mp clients on laptops (WLan) or desktop PCs (LAN) that always wake the server. I have a php script on a raspberry that wakes the server every time I call it. The WoL app from the play store (tried it twice) woke the server. To me it seems that something is wrong with the WoL function in MPTVScheduler (or maybe not 100% according to the WoL protocol (magic packet, port 9, ...)). Or it is dependent from the time that the server is already in standby. Maybe your app wakes servers from standby but not from hybrid standby (which means "send pc to hibernate after some time in standby" I think)? That would explain why it worked right after the wol app but not 20mins later? During my tests this morning the server was running before, then went to sleep and was then woken by mptvscheduler so that would fit into my assumption.

What do you think?

Regards
BartManson

 

[regeszter]

Hm. OK. Do you know if MPExtended is still under development?

No.

Anyway, I did some more testing regarding WoL and that is really weird:

I can create a new build for testing WOL issue. Can you install my apk to your device using usb cable?