Posts by edit4ever

Quick question - if I try a nand install...in theory it won't overwrite the existing dtb.img file and might work?

Since I have two boxes for testing - I'm willing to try this approach.

Quote from kszaq

edit4ever I will look at the device tree you posted in the other thread.

Don't bother - that was from a firmware that I suspect is the earlier (more common) version of the KII Pro. It's not the firmware that I am running. I could try loading it to see if it works - but I may wait for Videostrong's response on Monday to see if they can supply the correct file for my version.

Thanks!

Quote from kszaq

Try using gxbb_p200_1Gbit.dtb

gxbb_p200_1Gbit.dtb doesn't boot to LE on sd card - it boots into nand (android)

For my KII Pro, if I use the gxbb_p200_k2_pro.dtb neither the wifi or lan work. If I use the others mentioned earlier...lan works.

Here is the log when running gxbb_p200_2G_beelink_minimxIII.dtb: log-2016-09-17-15.42.44.zip

When running gxbb_p200_k2_pro.dtb there doesn't seem to be an updated logfile being generated. And since I can't access the network, I can't ssh to run dmesg. Also, the time resets on every reboot (which I guess makes sense since there is no network). Is there a reason the logfile wouldn't generate?

As for the Broadcom 4239/30 report - that came out of the Android Spec Device app:

You'll see that the installed firmware is from an M8S+ 4K - hence my belief that different hardware may have been used in this Videostrong KII Pro. Of course, this app may just be reporting back what the firmware is telling it. According to Videostrong, the wifi/bluetooth is the AP6335. I'm still awaiting the firmware or dtb.img file from them...hopefully on Monday.

My Videostrong KII Pro (2G/16G) seems to use the Broadcom 4329/30 wifi chipset. I've tried most of the dtb files that are in the downloads for 006 and 007 but can't get wifi to work. I do have ethernet when using gxbb_p200_2G_mini_mxg_2_16.dtb or gxbb_p200_2G_beelink_minimxIII.dtb

Is there an existing dtb for this setup or should I try to track down an android update file?

Also - just to make sure - is the Broadcom 4239/30 supported in 007?

Quote from kszaq

What I do is I convert dtb to dts with dtc tool, compare manually and create a patch.

Thanks for the info...I'll see about making a version once I get the original firmware. In the meantime, ethernet is working with gxbb_p200_2G_beelink_minimxIII.dtb

Might be time to pop the box and look inside to see what chips are in play!

KII Pro: KII Pro 2G 16G dtb.zip

As an FYI - the gxbb_p200_2G_100M.dtb, gxbb_p200_2G_100M_RealtekWiFi.dtb and gxbb_p200_k2_pro.dtb files booted but wifi did not work.

As a second note, these are sample boxes I am using to test an ATSC version of the KII Pro - and Videostrong shipped them with the M8S+ 4K android firmware. I have asked them for that dtb and will submit once I receive.

Thanks!

-- @kszaq Just to clarify...can I extract the dtb.img file from exisiting firmware and use directly on the sd card, or do you need to modify it first?

Quote from mhewitt

I am using a Raspberry Pi 3 running version 7.0.2. I have a Raspberry Pi 2 running the back end of TVHeadEnd. The receiver is an HDHomerun Connect.

I will assume that you have configured the backend and have all your services (channels) setup.

If you're running the client on the same Rpi as the backend, make sure the client ip configure settings are set to 127.0.0.1

If that is set and you still can't connect...open the tvheadend web interface and take a look at the log window to see what happens when kodi tries to connect. If there is an error showing...post that info here.

balbes150 here is the version for the Acemax M8S+ that dankec needs. It from the Acemax download center:

MEGA

I have similar issues to dankec and hope your build method works!

It is fixed in latest builds. Turned out to be a member of error issue in the code.

Quote from dankec

Anyone tried this:

LibreELEC

with M8S+?

Would love to - but I'm traveling for a couple of weeks and won't have the opportunity. Hopefully someone gives it a go and posts their results.

buzzmarshall
Would you be willing to share your M8S build? Should work on our M8S+ models as the only difference should be ethernet speed - although there is a possible wifi difference.

Better yet - could you share your git?

@Deezel defintely worth checking inside to see what wifi chip is in there. The M8 build has working wifi running on an M8S+ which has the AP6330 chip.

Quote from rhartinger

can someone help

Why can't you connect to the LE addon repo? Both 4.0 and 4.2 versions of Tvh are in there.

You could always download the addon file directly from: index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/)

Quote from burimek

i am sad, for this clone box

Can you post a picture of your remote?

Fix has been submitted to tvheadend...hopefully they'll merge the pull request and new builds will once again contain the ATSC muxes!

Thanks to CVH for the help in testing the fix.

Quote from dankec

Yes in my case...

That version had a fully working remote for me as well. Just the issue with live tv playback from a usb tuner. The 7.0.2 version MEGA can power on if I use the shutdown menu to turn off the system...but not if I power off from the remote's power button.

I may have discovered the issue to this problem - but am having trouble testing.

At commit f02851ab9c60bdd326fdba9afee4255b7b07a06c on tvheadend, the ATSC network was split to atsc-t and atsc-c. However, the dvb-scan git was never updated to the new naming system. I believe the issue is being caused by the fact that there are no dvb-scan files/folders with the atsc-t and atsc-c networks.

Since the dvb-scan folder is pulled from from the git source when compiling the add-on for LE, I am unable to get my test changes to stick. I can't seem to find a way to get it to pull from another source to test this theory.

Any help would be appreciated. Thanks!