2740 replies to this topic

[moham96]

 

 

On more thing which is noted in this as well as in the last image is that when the box is rebooted then the saved channels in the channel list are "dimmed" and all tuner configuration is also lost. We have to setup tuner again and rescan the channels like in initial setup.

This happens because of the multimode tuner, the avl6862 starts in DVBT when you booted which confuses enigma2 if it was shutdown on a different mode

I solved this issue manually on my box by compiling the create_nimsockets tool and the dvb-fe-tool and added two lines to the /etc/init.d/mecool-setup

dvb-fe-tool -d DVBS
/home/root/create_nimsockets

this runs each time the device is booted which sets the mode to DVBS and updates the nimsockets before enigma2 starts

It's not an ideal solution( not even a good workaround) and doesn't always work which is why I didn't add it to the repo

 

 

Can we solve it by changing the default order: https://github.com/O...eConfig.py#L224 ?

 

I don't see how ? can you propse a change here so I can test it ?

[Persian Prince]

 

 

 

On more thing which is noted in this as well as in the last image is that when the box is rebooted then the saved channels in the channel list are "dimmed" and all tuner configuration is also lost. We have to setup tuner again and rescan the channels like in initial setup.

This happens because of the multimode tuner, the avl6862 starts in DVBT when you booted which confuses enigma2 if it was shutdown on a different mode

I solved this issue manually on my box by compiling the create_nimsockets tool and the dvb-fe-tool and added two lines to the /etc/init.d/mecool-setup

dvb-fe-tool -d DVBS
/home/root/create_nimsockets

this runs each time the device is booted which sets the mode to DVBS and updates the nimsockets before enigma2 starts

It's not an ideal solution( not even a good workaround) and doesn't always work which is why I didn't add it to the repo

 

 

Can we solve it by changing the default order: https://github.com/O...eConfig.py#L224 ?

 

I don't see how ? can you propse a change here so I can test it ?

 

 

I did add the patch: https://github.com/P...7d344eef6465deb

[engineerkhan15]

 

 

 

Can we solve it by changing the default order: https://github.com/O...eConfig.py#L224 ?

 

I don't see how ? can you propse a change here so I can test it ?

 

 

I did add the patch: https://github.com/P...7d344eef6465deb

 

Yes, in my view also, it should be DVB-S (default), DVB-C & then DVB-T.

[Persian Prince]

 

 

 

 

Can we solve it by changing the default order: https://github.com/O...eConfig.py#L224 ?

 

I don't see how ? can you propse a change here so I can test it ?

 

 

I did add the patch: https://github.com/P...7d344eef6465deb

 

Yes, in my view also, it should be DVB-S (default), DVB-C & then DVB-T.

 

 

If you read moham96's post he said mecool devices start with dvb-t mode not dvb-s and that's why I changed the enigma2 order

[engineerkhan15]

 

 

 

 

 

Can we solve it by changing the default order: https://github.com/O...eConfig.py#L224 ?

 

I don't see how ? can you propse a change here so I can test it ?

 

 

I did add the patch: https://github.com/P...7d344eef6465deb

 

Yes, in my view also, it should be DVB-S (default), DVB-C & then DVB-T.

 

 

If you read moham96's post he said mecool devices start with dvb-t mode not dvb-s and that's why I changed the enigma2 order

 

Yes, I had read that and also saw the patch you added, making default order as DVB-S/C/T. That is why, I seconded you that it should be the order.

[Persian Prince]

New test images for mecool devices, changes are about:

 

- amremote

- aio-grab

- wlan

- dvb-t

- resolution (60hz removed and it's 1080p/bpp=24, if you still have problem report to use 720p/bpp=32 instead)

 

k1pro: http://www.mediafire...sdcard.zip/file

 

k2pro: http://www.mediafire...sdcard.zip/file

 

k2prov2: http://www.mediafire...sdcard.zip/file

 

k3pro: http://www.mediafire...sdcard.zip/file

 

k1plus: http://www.mediafire...sdcard.zip/file

[engineerkhan15]

Tested new image for K1 Pro. Here is the feedback:

Boot: OK as earlier.

Remote: Working as earlier.

WLAN: Wlan settings option available but when try to scan wireless networks, it keeps searching but does not find any network.

DVB-T: Same situation as earlier. After reboot, all channels lost and have to go through tuner setup again.

Resolution: Not OK. Earlier it was fine with full screen display at 1080p. Now interface covers only 60% of screen at 1080p as well as at 720p on all refresh rates, ( it has shrunk now).. 

[moham96]

@persian where do the enigma2 tuner settings saved? looking at the /etc/enigma2/settings file I can't see any settings regarding tuners other than these:

config.Nims.0.diseqcA=70
config.Nims.0.diseqcMode=single
config.Nims.0.powerMeasurement=false

So there is nothing related to the tuner mode, maybe this is the problem

[Persian Prince]

I have this:

config.usage.alternatives_priority=5

in /etc/enigma2/settings for my Zgemma H9 

Edited by Persian Prince, 13 August 2018 - 13:50.

[Persian Prince]

 

New test images for mecool devices, changes are about:

 

- amremote

- aio-grab

- wlan

- dvb-t

- resolution (60hz removed and it's 1080p/bpp=24, if you still have problem report to use 720p/bpp=32 instead)

 

k1pro: http://www.mediafire...sdcard.zip/file

 

k2pro: http://www.mediafire...sdcard.zip/file

 

k2prov2: http://www.mediafire...sdcard.zip/file

 

k3pro: http://www.mediafire...sdcard.zip/file

 

k1plus: http://www.mediafire...sdcard.zip/file

 

 

@mecool users:

 

Please test these ipks one by one as we need to identify wifi chips on the mecool devices, it seems k2pro and k3pro need 6335 but I don't know about the rest.

 

One of these ipks should fix your wifi problem, please test and report 

Edited by Persian Prince, 13 August 2018 - 14:12.

[moham96]

I have this:

config.usage.alternatives_priority=5

in /etc/enigma2/settings for my Zgemma H9 

Doesn't help, does the Zgemma H9 have a multimode tuner ? what is the content of /proc/bus/nim_sockets?

[moham96]

It seems like enigma2 does tune into the channel after you turn it on but it's kept in locked state after that.

after I turn on the device apparently the channel does send the ts stream but the amdecoder crashes which causes enigma2 to crash

Some logs:

[eDVBServicePlay] eventNewProgramInfo timeshift_enabled=0 timeshift_active=0
[eDVBServicePlay] have 1 video stream(s) (0921), and 1 audio stream(s) (0d07), and the pcr pid is 0921, and the text pid is ffffffff
[eDVBChannel] getDemux cap=01
[eAMLTSMPEGDecoder] SETTING UP DECODER                   ------------ WETEK
TuxTxt cache cleared
[eAMLTSMPEGDecoder::setVideoPID] vpid=2337, type=1 MPEG4 H264
AM_DEBUG:("linkhal/linkhal.c" 683)aml_change_vpid: vpid = 2337 vtype 2 ########################### isPlay 0

[eAMLTSMPEGDecoder::setAudioPID] apid=3335, type=0 MPEG
[eAMLTSMPEGDecoder::setSyncPCR] pcrpid=2337
[eAMLTSMPEGDecoder::setTextPID] textpid=-1
[eAMLTSMPEGDecoder::osdBlank] cmd=0
[eAMLTSMPEGDecoder::osdBlank] cmd=1
[eAMLTSMPEGDecoder::play] Amlogic CODEC open success apid=3335 vpid=2337!!!!!
[eAMLTSMPEGDecoder::setAvsyncEnable] enable=0
[eAMLTSMPEGDecoder::setAvsyncEnable] enable=1
[gRC] main thread is non-idle! display spinner!
audiodec_init!media.amplayer.audiocodec = ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,raac,cook,amr,pcm,adpcm,aac_latm,rm, t->type = mp3
set_multichs_prop: aud_cap support channel number: 2 ch
[find_audio_lib 97]audec->format/0 audec->codec_id/0x0
audio_lib_list[i].name libmad_aml.so
f->name libmad_aml.so
f->codec_id 0
Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46E5BC]
linux-vdso.so.1(__kernel_rt_sigreturn) [0x7FA43E3510]
/usr/lib/libamavutils.so(itemlist_find_match_item) [0x7FA303A504]
-------FATAL SIGNAL
[gRC] main thread is non-idle! display spinner!
Killed




[eDVBSectionReader] ERROR reading section - Value too large for defined data type

TuxTxt cache cleared
AM_DEBUG:("linkhal/linkhal.c" 683)aml_change_vpid: vpid = 2337 vtype 2 ########################### isPlay 0

audiodec_init!media.amplayer.audiocodec = ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,raac,cook,amr,pcm,adpcm,aac_latm,rm, t->type = mp3
set_multichs_prop: aud_cap support channel number: 2 ch
[find_audio_lib 97]audec->format/0 audec->codec_id/0x0
audio_lib_list[i].name libmad_aml.so
f->name libmad_aml.so
f->codec_id 0
Backtrace:
/usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x46E5BC]
linux-vdso.so.1(__kernel_rt_sigreturn) [0x7F7FDDF510]
/usr/lib/libamavutils.so(itemlist_find_match_item) [0x7F7EA36504]
-------FATAL SIGNAL
Killed



 [ 1301.972711@0] codec:vdec_create instance ffffff8003ce5000, total 1
[ 1301.973393@0] codec:set pcrid = 0x921
[ 1301.977177@0] DMX: demux0 smallsec buf disable
[ 1301.981273@0] DMX: demux0 timeout disable
[ 1301.985241@0] DMX: demux0 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1301.992428@0] DMX: demux1 smallsec buf disable
[ 1301.996796@0] DMX: demux1 timeout disable
[ 1302.000765@0] DMX: demux1 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1302.007952@0] DMX: demux2 smallsec buf disable
[ 1302.012321@0] DMX: demux2 timeout disable
[ 1302.016290@0] DMX: demux2 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1302.023682@0] DMX: demux0 smallsec buf disable
[ 1302.027846@0] DMX: demux0 timeout disable
[ 1302.031815@0] DMX: demux0 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1302.039000@0] DMX: demux1 smallsec buf disable
[ 1302.043371@0] DMX: demux1 timeout disable
[ 1302.047340@0] DMX: demux1 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1302.054524@0] DMX: demux2 smallsec buf disable
[ 1302.058896@0] DMX: demux2 timeout disable
[ 1302.062865@0] DMX: demux2 timeout enable:timeout(9000),ch(0xfffffff8),match(1)
[ 1302.070256@0] DMX: demux0 smallsec buf disable
[ 1302.074421@0] DMX: demux0 timeout disable
[ 1302.078390@0] DMX: demux0 timeout enable:timeout(9000),ch(0xfffffff8),match(1)

After that If I run enigma2 again I get the previous "timeout reading pat" error and I have to restart the device to be able to tune again.

This is annoyig and makes debugging the amdecoder a pain in the ass.

I think tvheaded works because it doesn't use the hardware demuxer (/dev/dvb/adapter0/demux0) instead it uses some sort of software demuxing.

[thmls]

New test images for mecool devices, changes are about:

- amremote
- aio-grab
- wlan
- dvb-t
- resolution (60hz removed and it's 1080p/bpp=24, if you still have problem report to use 720p/bpp=32 instead)

k1pro: http://www.mediafire...sdcard.zip/file

k2pro: http://www.mediafire...sdcard.zip/file

k2prov2: http://www.mediafire...sdcard.zip/file

k3pro: http://www.mediafire...sdcard.zip/file

k1plus: http://www.mediafire...sdcard.zip/file

KI pro
I tried this image on 2 TVs. on the Samsung monitor TV 24 the image started but the screen is at 1/3 of TV . if you change HDMI input the mecool logo appears if you restart the image boot normally . I tested 720p 1080p resolution with the same result. On the second Panasonic 42 plasma TV if you change HDMI input and if restarting the mecool logo appears and can not start it again

[engineerkhan15]

 

 

New test images for mecool devices, changes are about:

 

- amremote

- aio-grab

- wlan

- dvb-t

- resolution (60hz removed and it's 1080p/bpp=24, if you still have problem report to use 720p/bpp=32 instead)

 

k1pro: http://www.mediafire...sdcard.zip/file

 

k2pro: http://www.mediafire...sdcard.zip/file

 

k2prov2: http://www.mediafire...sdcard.zip/file

 

k3pro: http://www.mediafire...sdcard.zip/file

 

k1plus: http://www.mediafire...sdcard.zip/file

 

 

@mecool users:

 

Please test these ipks one by one as we need to identify wifi chips on the mecool devices, it seems k2pro and k3pro need 6335 but I don't know about the rest.

 

One of these ipks should fix your wifi problem, please test and report 

 

What you recommend, should we test these wlan drivers on the latest image or on the earlier image?

[moham96]

Tested new image for K1 Pro. Here is the feedback:

Boot: OK as earlier.

Remote: Working as earlier.

WLAN: Wlan settings option available but when try to scan wireless networks, it keeps searching but does not find any network.

DVB-T: Same situation as earlier. After reboot, all channels lost and have to go through tuner setup again.

Resolution: Not OK. Earlier it was fine with full screen display at 1080p. Now interface covers only 60% of screen at 1080p as well as at 720p on all refresh rates, ( it has shrunk now).. 

change the skin to the fullnight hd and the resolution issue should be resolved

[engineerkhan15]

 

change the skin to the fullnight hd and the resolution issue should be resolved

 

Yes, you are right. Resolution OK with PLi-FullNightHD.

[moham96]

 

New test images for mecool devices, changes are about:

- amremote
- aio-grab
- wlan
- dvb-t
- resolution (60hz removed and it's 1080p/bpp=24, if you still have problem report to use 720p/bpp=32 instead)

k1pro: http://www.mediafire...sdcard.zip/file

k2pro: http://www.mediafire...sdcard.zip/file

k2prov2: http://www.mediafire...sdcard.zip/file

k3pro: http://www.mediafire...sdcard.zip/file

k1plus: http://www.mediafire...sdcard.zip/file

KI pro
I tried this image on 2 TVs. on the Samsung monitor TV 24 the image started but the screen is at 1/3 of TV . if you change HDMI input the mecool logo appears if you restart the image boot normally . I tested 720p 1080p resolution with the same result. On the second Panasonic 42 plasma TV if you change HDMI input and if restarting the mecool logo appears and can not start it again

 

First remove the for loop in the start of amlsetfb (I mentioned in my previous posts) to pevent the bootloader from overriding the parameter

then try re-adding 60hz to the 1080 and reboot and then try 50hz

like this

mode=1080p50hz

and reboot

and try the other resolution defined in the files with combination of 60hz and 50hz, also try changing bpp between 24 and 32

play with this these parameter untill you find the right ones for your device

each change you should either reboot the device or run

/etc/init.d/amlsetfb

and then restart enigma2 only

 

if enigma doesn't fill the screen change the skin to the fullnight hd skin

[takitr]

#!/bin/sh
#
# Start Neutrino
#

. /etc/profile

export PATH=$PATH:/storage/vitmod/neutrino/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/storage/vitmod/neutrino/bin:/storage
export HAL_DEBUG=0xff

enable_video() {
echo 0 > /sys/class/video/disable_video
echo "0 0 0 0" > /sys/class/video/axis
echo 0 > /sys/class/graphics/fb0/blank
echo 1 > /sys/class/graphics/fb1/blank
# for new kernel
echo "dmx0" > /sys/class/stb/source
echo "ts0" > /sys/class/stb/demux0_source
echo "ts0" > /sys/class/stb/demux1_source
echo "ts0" > /sys/class/stb/demux2_source
echo "dmx1" > /sys/class/stb/dsc0_source
}

tv_on() {
echo "10 04" > /sys/class/cec/cmd
}

tv_off() {
echo "0f 36" > /sys/class/cec/cmd
}

wait_network() {
/usr/sbin/connmand-wait-online --timeout=15
}

while true; do
tv_on
rm -f /tmp/.halt /tmp/.reboot /tmp/.timer
remotecfg /storage/vitmod/neutrino/var/tuxbox/config/remote-neu.conf > /dev/null
enable_video
wait_network
/storage/vitmod/neutrino/bin/neutrino;
exit_value=$?
case "$exit_value" in
0) echo "Neutrino exit with shutdown" >&2
tv_off
poweroff
;;
1) echo "Neutrino exit with reboot" >&2
reboot
;;
50) echo "Neutrino exit with start Kodi"
/storage/vitmod/run/kodi.start
;;
60) echo "Neutrino exit with start Android"
/storage/vitmod/run/android.start
;;
esac
exit $exit_value
done

[mihaip]

@PersianPrince ... Please ! How to boot KIII image from SD ?

written on SD and does not start ...

Edited by mihaip, 14 August 2018 - 05:14.

[jserv]

@PersianPrince ... Please ! How to boot KIII image from SD ?

written on SD and does not start ...

use the software for amiko a5