TNAP-4.1-Test Images for Edision MIO/MIO+

Status
Not open for further replies.
I downloaded from online and installed the August 13 TNAP 4.1 image. All images loaded prior to this did not solve my clock issue when I switched my Mio+ to standby. My Mio+ clock has always been accurate if I left the receiver powered. However, this latest release may be the magic bullet. So far, the clock is remaining correct even in standby. I will continue leaving the receiver in standby whenever I am not using it to test if it remains accurate.

Added: This morning I installed the new August 15 image. Continuing to monitor.
Perhaps I have a unique hardware issue with my Mio+. But it is clear the clock issue continues after all. As I've been sitting here for the past 30 minutes, the clock has deviated dramatically 2 times. It is now 3 hours in the future and probably the date is in the last century (1969 or 1970). I would have to power it up to check that.

For the record:
1) I have carefully followed the updates for TNAP 4.1. The current time shows Friday, January 2, 1970 11:16 am. Time is approximately 3 hours in the future and the date is 51 years behind. My current software is TNAP 4.1 2021-08-15.

2) I have never used anything but the Internet time synchronization method. I have never used transponder time sync since owning this receiver. I learned years ago with previous receivers that transponder sync doesn't work in Canada. My Internet is stable and reliable.

3) When needed, lately if I reboot, I am using the deep standby selection. It seemed in past, this provided a better reboot since it powers down the receiver completely. When powering up, the receiver goes to clock mode. I then press POWER on my remote to switch on the receiver.

4) If I only do a restart, then the receiver restarts but the TV does not display anything. I must cycle the power on the receiver so the TV then syncs and displays a picture.

5) My workaround is OK for me. I simply never power down the receiver to standby. Doing this keeps the receiver totally accurate. Some don't like to leave the receiver on all the time. I don't mind.

6) It seemed when I first installed this software update that it had resolved the issue since I could leave the receiver in standby for long periods (even overnight) and the clock remained accurate. It almost seemed like the issue developed again over time. As I'm using the receiver, it has just corrected itself automatically. It will remain accurate now as long as I don't go to standby.

7) Months ago, we had a very bad lightning storm. One particular strike nearby caused a power hit. This seemed to have an impact on receiver operation. I changed HDMI cable, etc. This is why I'm wondering if I have a hardware issue.
 
Post your settings file located in /etc/enigma2 of receiver files. It will be OK to do this as long as you have no logins to Facebook or any other website that requires a password.
 
Perhaps I have a unique hardware issue with my Mio+. But it is clear the clock issue continues after all. As I've been sitting here for the past 30 minutes, the clock has deviated dramatically 2 times. It is now 3 hours in the future and probably the date is in the last century (1969 or 1970). I would have to power it up to check that.

For the record:
1) I have carefully followed the updates for TNAP 4.1. The current time shows Friday, January 2, 1970 11:16 am. Time is approximately 3 hours in the future and the date is 51 years behind. My current software is TNAP 4.1 2021-08-15.

2) I have never used anything but the Internet time synchronization method. I have never used transponder time sync since owning this receiver. I learned years ago with previous receivers that transponder sync doesn't work in Canada. My Internet is stable and reliable.

3) When needed, lately if I reboot, I am using the deep standby selection. It seemed in past, this provided a better reboot since it powers down the receiver completely. When powering up, the receiver goes to clock mode. I then press POWER on my remote to switch on the receiver.

4) If I only do a restart, then the receiver restarts but the TV does not display anything. I must cycle the power on the receiver so the TV then syncs and displays a picture.

5) My workaround is OK for me. I simply never power down the receiver to standby. Doing this keeps the receiver totally accurate. Some don't like to leave the receiver on all the time. I don't mind.

6) It seemed when I first installed this software update that it had resolved the issue since I could leave the receiver in standby for long periods (even overnight) and the clock remained accurate. It almost seemed like the issue developed again over time. As I'm using the receiver, it has just corrected itself automatically. It will remain accurate now as long as I don't go to standby.

7) Months ago, we had a very bad lightning storm. One particular strike nearby caused a power hit. This seemed to have an impact on receiver operation. I changed HDMI cable, etc. This is why I'm wondering if I have a hardware issue.

I will BET MONEY, that regardless of these receivers being set to grab time via NTP, they somehow ALSO randomly sync time to whatever transponder you are sitting on. IF that time is wrong (which we all know in the USA is most are wrong), then it goes to that time. At least until the next time sync interval.

WHY that happens, I don't know, but I'm pretty sure that's what's doing it.
 
I know I use a startup service with a good time accurate Transponder and clock stays accurate. The reason I do that is my internet is a hot spot and not always online. The ATSC channels using the Hauppauge tv tuner are good startup services and I think 103W ku has some transponders that have accurate time the one with DW English was the last I checked and I believe the transponder with NHK world is accurate but not 100% sure on that one. I use an ATSC channel.
 
I know I use a startup service with a good time accurate Transponder and clock stays accurate. The reason I do that is my internet is a hot spot and not always online. The ATSC channels using the Hauppauge tv tuner are good startup services and I think 103W ku has some transponders that have accurate time the one with DW English was the last I checked and I believe the transponder with NHK world is accurate but not 100% sure on that one. I use an ATSC channel.

On 99W, scan in AFN 3900 V DVB-S2 8psk 27500 2/3. One of the channels is called: "Bars & Tone". Save that one to a Bouquet, and use it for the Startup Service, as it seems to keep perfect time.
 
Lately, I have been using the Media Player more than previously since it offers access to a lot of channels I can't receive via Ku. I notice today that the receiver time went back to January 1970 while I was using the receiver and I wasn't in standby. I noticed this when I started using the Media Player. I wonder if using the player may trigger the receiver to lose its clock accuracy? When the date goes wrong, then the Media Player no longer will stream channels. Lack of ability to stream was one reason why I noticed the time had gone wrong earlier today. So I left the Media Player and went back to normal satellite use. And waited. There is no way now to force an immediate time update without restarting the receiver. The time was eventually updated.

My Settings file is attached.
 

Attachments

This setting makes your receiver turn Off when you turn it On...
config.usage.startup_to_standby=yes

There are a few other changes that can be made. So we will see if we can find something that works.
 
The reason I set the receiver to turn off when it deep restarts is because then when I power it on I can see a picture on my TV. If I just allow a restart without that, the receiver ends up being on but there is no picture on the TV. So I have to manually turn off the receiver and then turn it on to sync with the TV and show a picture.
 
Check your messages and you will find an image link. Your settings file has been modified a bit and is installed in that image. Save your lamedb and lamedb5 files that are in /etc/enigma2. Then install the image. Do Not allow an auto restore to take place, and really that option should not be present because your settings file is in it. Once the image is installed, stop enigma2 using the init 4 command in telnet, then transfer the lamedb and lamedb5 files that you saved back into /etc/enigma2 folder of the receiver. Restart enigma2 using the init 3 command, and the receiver should be setup with your channels and settings.
 
I read your instructions here after I installed the image you sent. It didn't do an auto restore. So all I had to do was reset the GUI (I like PLi-FullNightHD), restore my channels and bouquets via Dreamset, and deep restarted the receiver. It is running now normally on TNAP 4.1 2021-08-20. I have reinstalled my m3u8 playlists so I can use the Media Player. I will continue to monitor the receiver.
 
If you put those m3u8 files into a bouquet they will play as a channel then you don't have use media player.
I'll share my list here as an example and using notepad++ you can edit the file and add your channels to it.
The file goes in etc/enigma2
When you extract the zip it may be in a folder but you want just the bouquets IPTV file not folder in etc/enigma2.
To add to this some characters when editing your URLS will need to be changed. I Know a : after http: will need to be http% in the URL.And after the .com,.org. get another % instead of:. I guess that is the way e2 handles it.
 

Attachments

Last edited:
If you put those m3u8 files into a bouquet they will play as a channel then you don't have use media player.
I'll share my list here as an example and using notepad++ you can edit the file and add your channels to it.
The file goes in etc/enigma2
When you extract the zip it may be in a folder but you want just the bouquets IPTV file not folder in etc/enigma2.
To add to this some characters when editing your URLS will need to be changed. I Know a : after http: will need to be http% in the URL.And after the .com,.org. get another % instead of:. I guess that is the way e2 handles it.

I second this. I found this out last year, and that's how I do them also. Works perfectly. Only issue I see, is that IF you are recording any of them, (yes, you can set timer recordings for IP channels) AND they have a break or hesitation in the streaming, the recording will quit immediately.
 
Crap? Dreamset causes problems? I haven't experienced any that I know of. I only use it to copy my info as a backup to my PC. Or to write it back. I don't actually use Dreamset to edit anything.

I can re-install the new image if necessary.
 
Last edited:
If you put those m3u8 files into a bouquet they will play as a channel then you don't have use media player....
I guess my question is why do all those maneuvers? I have hundreds of channels categorized in playlists according to US, Japan, Canada, English, etc. I never want to record these, just roam and watch. Unless there is an issue with the Media Player, it works fine for me. And when it's time to update them, then I source them again and just update the playlists.
 
Crap? Dreamset causes problems? I haven't experienced any that I know of. I only use it to copy my info as a backup to my PC. Or to write it back. I don't actually use Dreamset to edit anything.

I can re-install the new image if necessary.

Your settings file had some crap in it that may/may not have caused problems. When you restored using Dreamset, then you most likely restored the settings file which put the same lines back in that I deleted....
No worries. Just see if the time works better.
 
I guess it would take a long to do hundreds. I only have about dozen. lol I stream mostly youtube but I am watching Super Channel IPTV right now it has some good American movies but it got some greek words on the screen.
 
Check your messages and you will find an image link. Your settings file has been modified a bit and is installed in that image. Save your lamedb and lamedb5 files that are in /etc/enigma2. Then install the image. Do Not allow an auto restore to take place, and really that option should not be present because your settings file is in it. Once the image is installed, stop enigma2 using the init 4 command in telnet, then transfer the lamedb and lamedb5 files that you saved back into /etc/enigma2 folder of the receiver. Restart enigma2 using the init 3 command, and the receiver should be setup with your channels and settings.
I re-installed the new image. All went well except I ended up with no bouquets. The channels and settings are there. So I repeated the whole process. Same result.

Once I used init 4 via telnet to stop enigma2, I used Filezilla to copy lamedb and lamedb5 overwriting the existing lamedb and lamedb5 in the receiver. I exited Filezilla and went back to telnet to use init 3.
 
Status
Not open for further replies.
Back
Top