2740 replies to this topic

[frankviana]

 

I'll test today too my k2 pro (v1) and K3 pro to see some features...

If you can test image k3 pro work or not.

 

 

No boot k3 pro.. stop android logo.

[frankviana]

 

 

I'll test today too my k2 pro (v1) and K3 pro to see some features...

If you can test image k3 pro work or not.

 

 

No boot k3 pro.. stop android logo.

 

 

K2 pro (v1) no boot too...

 

I see only blink pink screen and restart my Samsung TV. After "no signal".

 

K3 stop android logo... k2 "no signal" after pink android logo

Edited by frankviana, 14 August 2018 - 14:04.

[frankviana]

duplicate post.

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

[thmls]

 

 

 

For mecool users.I've build and tested an image with latest sources.

-for k1plus(my box) or which boxes that stays on blank screen or doesn't boot.I've used linkdroid-amlsetfb and it boots and works without any problems (when restart the box it boots again).just have a skin resulation problem.changing pliHD-skin to normal pli-skin solves this.

-tuner finds channels.sometimes needs restart sometimes doesn't when using single transponder search.

-no video and audio still on channels.and after a while it says pat "No data on transponder (Timeout reading PAT).

-network works but no wireless lan.

-on open-webif I can't see cuurent screen.I can use and see everything on open-webif but no actual screen on box.I don't know why.

 

Thanks a lot for your tests, please test this new image: http://www.mediafire...sdcard.zip/file

 

I did some updates:

 

- enigma2 default skin changed (PLi-HD now)

- mecool-amlsetfb changes regarding k1plus only (https://github.com/P...ol-amlsetfb/aaa)

- Realtek 8189es installed by default (WiFi problem)

 

thanks a lot. I'm downloding and will test it now.

 

 

For mecool users.I've build and tested an image with latest sources.

-for k1plus(my box) or which boxes that stays on blank screen or doesn't boot.I've used linkdroid-amlsetfb and it boots and works without any problems (when restart the box it boots again).just have a skin resulation problem.changing pliHD-skin to normal pli-skin solves this.

-tuner finds channels.sometimes needs restart sometimes doesn't when using single transponder search.

-no video and audio still on channels.and after a while it says pat "No data on transponder (Timeout reading PAT).

-network works but no wireless lan.

-on open-webif I can't see cuurent screen.I can use and see everything on open-webif but no actual screen on box.I don't know why.

if the linkdroid-amlsetfb works, maybe we just need to change to 720p instead of 1080, please try this:

-First delete the linkdroid-amlsetfb files if you have them and use the mecool-amlsetfb

-edit the start of /etc/init.d/amlsetfb https://github.com/P.../amlsetfb#L3-L6

 

comment out the mode=1080p60hz (by adding a hash at the start of the line) and uncomment the mode=720p60hz (by removing the hash) and then reboot

- if you still don't have problems change the bpp=24 to bpp=32 and reboot

- if you still have a problem use bpp=32 with the older 1080 resolution (comment the 720 and uncomment the 1080)

 

@Persian Prince and @moham96

yes exactly.I've changed linkdroid-amlsetfb;

 

In amlsetfb file;

bpp=24
mode=1080p60hz
hdmi=`cat $HPD_STATE`
if [ $hdmi -eq 1 ]; then
    echo $mode > $DISP_MODE
fi

In aaa file;

#!/bin/sh

bpp=24
mode=1080p

that fixed pliHD-skin resulation issue:)

 

Sorryforgot to mention this.In mecool.inc I added 'sdio' here,too

 

MACHINE_FEATURES = "bluetooth usbhost vfat alsa dvb-c nolcd hdmicec fb skins1080 sdio emmc aml-plugins mecool-pli"

 

as I said in the git commit by persian prince, the aaa file doesn't get executed so if you delete it or keep it will have no effect, all the work is in the amlsetfb

please don't use the linkdroid-amlsetfb as it is not very well written and I had problems with it on my k2pro which is why I replaced it, try to use the edits I pointed it (playing with mode and bpp and reboot everytime) 

also if after all this it didn't help

Try to remove the this from the file

for x in $(cat /proc/cmdline); do
        case ${x} in
                m_bpp=*) export bpp=${x#*=} ;;
                hdmimode=*) export mode=${x#*=} ;;
        esac
done

maybe the problem is that mecool-amlsetfb gets the mode from the bootloader while linkdroid-amlsetb doesn't(remember after removing this to rever your changes to the mode and bpp above and reboot)

 

I have made many changes to the amlsetfb file with no luck

in setup audio/video   if changes screen resolution  does not change  It is the same as the amlsetfb file has

Maybe that is the problem?

Edited by thmls, 14 August 2018 - 17:46.

[mihaip]

@jserv --- yes ! I have KIII Pro and A5 and many others ...

 but I don't know how to start E2 on KIII Pro ... SD card is OK

but does not boot ! is there a special procedure ?

[jserv]

i think it's only boot in k2pro new version as it have the same chipset with amiko a5 (S905D).

tell me how to become a member to www.sat-support.tv,i don;t see register button anywhere only login.

i want to buy amiko a5 and i'm interesting to see how enigma2 works in a5,can you upload a video to youtube with a5 working enigma2?

[sauna]

To start the image, use the LibreELEC + v1.1.apk application.this is also suitable for openpli.if there is no launch,through the recovery wipe cache partition.

 

http://www.mediafire...C_v1.1.zip/file

[Persian Prince]

New test images for mecool devices, changes are about:

 

- IanSav's new virtual keyboard

- Persian Prince's patch (prince.patch which I borrowed it from PLi vision image so you could taste it)

- wlan (autoload dhd)

- resolution (60hz added and it's 720p60hz/bpp=32 now, if you still have problem try using 720p50hz/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

[mihaip]

@jserv --- automatic registrations are disabled due to

spammers , most of them scripts ! but you can register

sending a mail to : satsuport22@yahoo.com with desired

user/password !

I will make a movie with OpenATV Enigma2 on Amiko A5 !

where the u-bood was modified to detect the SD card presence

and to test if is an SD Enigma2. BTW ... the OpenPLi Enigma2

early build for Amiko A5 ... boot was OK ! but the rest ... 

 

Tanks @sauna !

Edited by mihaip, 15 August 2018 - 12:48.

[mihaip]

@Persian Prince --- we welcome if you can build OpenPLi Enigma2

for Amiko A5 Combo ! I can test it and report the behavior !

Edited by mihaip, 15 August 2018 - 12:53.

[moham96]

@persian prince, After the last commits I can no longer build an image, I can't do testing or patching,

CoCollected errors:
 * calculate_dependencies_for: Cannot satisfy the following dependencies for enigma2:
 * 	libamcodec (>= 0.1) * 
 * opkg_solver_install: Cannot install package enigma2.
nfiguring enigma2-plugin-extensions-audiosync.

ERROR: openpli-enigma2-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/oealliancebuilder/openpli-oe-core/build/tmp/work/k2pro-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_rootfs.9044
ERROR: Task (/home/oealliancebuilder/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6113 tasks of which 6096 didn't need to be rerun and 2 failed.
NOTE: Writing buildhistory

Summary: 2 tasks failed:

I can't understand where this libamcodec  dependency come from, bitbake-layers also doesn't provide a clue:

=== Matching recipes: ===
libamcodec:
  ?                    0.1

I cleaned the build directory of the machine and still doesn't help

[engineerkhan15]

It also happens with me if I clean the build directory of machine (k1 pro in my case). But if delete entire build directory then it builds without any such errors.

[Persian Prince]

@Persian Prince --- we welcome if you can build OpenPLi Enigma2

for Amiko A5 Combo ! I can test it and report the behavior !

 

Isn't it alien5? https://github.com/P...-extras#amlogic

 

If it's another machine we need the sources ...

 

@persian prince, After the last commits I can no longer build an image, I can't do testing or patching,

CoCollected errors:
 * calculate_dependencies_for: Cannot satisfy the following dependencies for enigma2:
 * 	libamcodec (>= 0.1) * 
 * opkg_solver_install: Cannot install package enigma2.
nfiguring enigma2-plugin-extensions-audiosync.

ERROR: openpli-enigma2-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/oealliancebuilder/openpli-oe-core/build/tmp/work/k2pro-oe-linux/openpli-enigma2-image/1.0-r0/temp/log.do_rootfs.9044
ERROR: Task (/home/oealliancebuilder/openpli-oe-core/meta-openpli/recipes-openpli/images/openpli-enigma2-image.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6113 tasks of which 6096 didn't need to be rerun and 2 failed.
NOTE: Writing buildhistory

Summary: 2 tasks failed:

I can't understand where this libamcodec  dependency come from, bitbake-layers also doesn't provide a clue:

=== Matching recipes: ===
libamcodec:
  ?                    0.1

I cleaned the build directory of the machine and still doesn't help

 

I have no problem but try removing these lines: https://github.com/P...bbappend#L9~L11

 

Still I didn't commit anything related to libamcodec ...

 

You can try removing build/tmp/buildstats/* too.

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

[moham96]

 

 

 

I have no problem but try removing these lines: https://github.com/P...bbappend#L9~L11

 

Still I didn't commit anything related to libamcodec ...

 

You can try removing build/tmp/buildstats/* too.

 

I don't think those patches are the problem, I also searched the last commits and didn't see anything related to libamcodec.

The strange thing is that I can build for other machines(I tried k1pro and builds fine)

but the problem is only with the k2pro which I normally work with, It's probably something messed up in my build directory.

I will try the buildstats trick you pointed.

 

Regards

[moham96]

It also happens with me if I clean the build directory of machine (k1 pro in my case). But if delete entire build directory then it builds without any such errors.

Yeah I'm trying to avoid that

[frankviana]

 

New test images for mecool devices, changes are about:

 

- IanSav's new virtual keyboard

- Persian Prince's patch (prince.patch which I borrowed it from PLi vision image so you could taste it)

- wlan (autoload dhd)

- resolution (60hz added and it's 720p60hz/bpp=32 now, if you still have problem try using 720p50hz/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

 

 

tests:

 

k2 pro (v1) no boot... only message: "bootimg..."

k3 pro no boot, no message, only android logo.

 

k1 pro: now, with this build, all picture pink screen and first setup not full screen. If change to night HD appear full screen. Previous build, normal screen, not pink.

[frankviana]

 

 

New test images for mecool devices, changes are about:

 

- IanSav's new virtual keyboard

- Persian Prince's patch (prince.patch which I borrowed it from PLi vision image so you could taste it)

- wlan (autoload dhd)

- resolution (60hz added and it's 720p60hz/bpp=32 now, if you still have problem try using 720p50hz/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

 

 

tests:

 

k2 pro (v1) no boot... only message: "bootimg..."

k3 pro no boot, no message, only android logo.

 

k1 pro: now, with this build, all picture pink screen and first setup not full screen. If change to night HD appear full screen. Previous build, normal screen, not pink.

 

 

Strange... after some reboots, pink screen disappear. Now show "normal" screen (night hd for full image)

Edited by frankviana, 15 August 2018 - 14:39.

[rantanplan]

another spin of trying to build an image for spark7162 fails on 'No rule to make target openpli-oe-core/build/tmp/work-shared/spark7162/kernel-source/multicom/mme/mme_linux_user.c

Any suggestion how to fix this appreciated



NOTE: Running task 5706 of 6065 (/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/pli-extras/meta-fulan/recipes-bsp/extra/libmme-host_git.bb:do_configure)
NOTE: recipe libmme-host-2.1+gitAUTOINC+cd23474d1b-r0: task do_configure: Started
NOTE: recipe libmme-host-2.1+gitAUTOINC+cd23474d1b-r0: task do_configure: Succeeded
NOTE: Running task 5707 of 6065 (/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/pli-extras/meta-fulan/recipes-bsp/extra/libmme-host_git.bb:do_compile)
NOTE: recipe libmme-host-2.1+gitAUTOINC+cd23474d1b-r0: task do_compile: Started
ERROR: libmme-host-2.1+gitAUTOINC+cd23474d1b-r0 do_compile: oe_runmake failed
ERROR: libmme-host-2.1+gitAUTOINC+cd23474d1b-r0 do_compile: Function failed: do_compile (log file is located at /media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.31551)
ERROR: Logfile of failure stored in: /media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.31551
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'sh-common', 'common-linux', 'common-glibc', 'sh4-linux', 'common']
| DEBUG: Executing shell function do_compile
| NOTE: make -j 2 DRIVER_TOPDIR=/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work-shared/spark7162/kernel-source DESTDIR=/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/image SUBDIRS=libmme_host
| ERROR: oe_runmake failed
| Making all in libmme_host
| make[1]: Entering directory '/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
| make[1]: *** No rule to make target '/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work-shared/spark7162/kernel-source/multicom/mme/mme_linux_user.c', needed by '/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work-shared/spark7162/kernel-source/multicom/mme/mme_linux_user.lo'.  Stop.
| make[1]: Leaving directory '/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
| Makefile:388: recipe for target 'all-recursive' failed
| make: *** [all-recursive] Error 1
| WARNING: /media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/run.do_compile.31551:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.31551)
NOTE: recipe libmme-host-2.1+gitAUTOINC+cd23474d1b-r0: task do_compile: Failed
ERROR: Task (/media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/pli-extras/meta-fulan/recipes-bsp/extra/libmme-host_git.bb:do_compile) failed with exit code '1'
NOTE: recipe mt7610u-3.0.0.2-r0: task do_compile: Succeeded
NOTE: Tasks Summary: Attempted 5708 tasks of which 4468 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /media/ubuntu/b6236065-6145-472b-99ba-a50420f28231/openpli-oe-core/pli-extras/meta-fulan/recipes-bsp/extra/libmme-host_git.bb:do_compile
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.



Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "linuxmint-18.2"
TARGET_SYS        = "sh4-oe-linux"
MACHINE           = "spark7162"
DISTRO            = "openpli"
DISTRO_VERSION    = "pli-extras"
TUNE_FEATURES     = "sh4"

 

Have no problem with the current version to build an image.

Everything works fine.

[engineerkhan15]

 

 

 

New test images for mecool devices, changes are about:

 

- IanSav's new virtual keyboard

- Persian Prince's patch (prince.patch which I borrowed it from PLi vision image so you could taste it)

- wlan (autoload dhd)

- resolution (60hz added and it's 720p60hz/bpp=32 now, if you still have problem try using 720p50hz/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

 

 

tests:

 

k2 pro (v1) no boot... only message: "bootimg..."

k3 pro no boot, no message, only android logo.

 

k1 pro: now, with this build, all picture pink screen and first setup not full screen. If change to night HD appear full screen. Previous build, normal screen, not pink.

 

 

Strange... after some reboots, pink screen disappear. Now show "normal" screen (night hd for full image)

 

There was no pink screen with me on K1 Pro. From your description, I suspect that your HDMI cable may be faulty.

[sauna]

on k1plus while the same darkest screen.I tried to change permissions in amlsetfb.no results yet