Posts by Pelican

Quote from Bruur

I received this week a new Q-Box (S905, 2GB / 16GB, 1GB Ethernet). I installed 7.0.3.012i temp_sensor_disabled succesfully to NAND. It works using the default device tree but also with gxl_p212_2g_nand.dtb. I'm guessing it's actually an S905x box because of this.

The problem is powering the box off. The red power button on the box reboots the box. Using the power menu results in this behaviour:

• Shutdown: results in a reboot
• Suspend: brings the box into sleep (led light stays on)

When doing a suspend, wake up and performing a shutdown the box actually powers down (led light goes off). It can be powered on again using the red power button.

I've tried all tricks I know to make this box shutdown such as using a custom shutdown.sh script. When using SSH using commands such as: halt, shutdown-P, the box doesn't properly poweroff (reboots or even hangs). It is not possible to make a script for first performing a suspend and then a shutdown, simply because after a suspend no more script code is executed.

Any ideas how to make the box powerdown properly and in 1 action?

Have you checked the ethernet (it's really gigabit)?
I've never seen an S905X box with gigabit lan. If yours has gigabit I would buy one right now. Could you give a link where you bought it? (In PM)
Have you tried to hold the power button for a few seconds?

Quote from kostaman

I'm DONE with the the S905X Chip Boxes.

I've researched a bit more on why these S905X Boxes are cheaper than S905 Chip Boxes and discovered the Circuit Boards are the first
crap shortcut in Quality and that is a Major no no for me.

Your conclusion is false.
There are very shitty boxes with S905 even with fake RAM chips and there are very good boxes with S905X (like the M8S II or MINI MXIII II)

Quote from kszaq

GUI scaling is not a hack, it's something actually merged for Kodi Leia. GPU is too slow to render 4K at 60Hz and that's why I won't revert that patch, sorry.

I don't mean you revert that patch to the "official" verrsion but to make a "test" version (as you once did with the 006), not even neccessary to make it public if you don't want.
I don't need support for it or new versions in the future or anything just build it once and I can use it until the end of time.
I don't want to buy another box with S905 (running that saved 006) just for watch my pictures on tv.
Thanks in advance.
I've just sent a coffee to you.

Quote from kszaq

7.0.3.012j in OP.

Changelog:

• fixed reading ethernet MAC address from eFuse and added reading from nand_env
• minor improvement in copying user data in installtointernal script
• experimental: better scaling of Mali cores for smoother GUI

Could you build a version without the fullhd GUI hack for pictures (I mean when I set 4k resolution the pictures only in full hd resolution after a downsclae and upscale)?
I have a 006 build with this feature, but the new S905X box doesn't work with that.
You put back this hack because the 4k video playing with gui was stuttering.
The whole system is much faster right now then it was in 006 maybe it worth to try.
Thanks in advance.

Quote from FaxeDeluxe

I have a quick question about the first recovery method. Is "boot into recovery" supposed to appear as an option when i insert the USB drive, or am i supposed to use an application like reboot manager?

Sorry if it's a stupid question

Is it really neccessary to quote the whole OP?

Quote from kszaq

I will always be less than 1/2GB because of RAM reserved for GPU and video decoder.

Yes, I know but on the other 2GB boxes it reports 1811 MB... so it is really 1GB as you said.

Quote from kszaq

I have a S805 box that shows 1GB in Android and has 2x512MB RAM chips on board but in reality only 512MB of RAM works and Android firmware fakes logs and visible RAM amount. This is to show how far there factories can go to save a few $$ on RAM.

The "default" dtb contains 4 device trees: 1GB/2GB, S905/S905X. If you leave default device tree on SD card, it's bootloader that chooses device tree depending on RAM amount and device type. The most obvious sign that you have only 1GB RAM is that when you use default DTB, the u-boot picks device tree with 1GB RAM. So either you need to flash a proper firmware that initializes your 2GB properly or you have fake RAM.

OK, thank you. Then it's probably a fake RAM.
But with the default dtb the box doesn't start at all.
[hr]
The free command says it is 775 MB total...

Quote from kszaq

Obviously your box has only 1GB of RAM.

As I wrote I can see the 2GB RAM in android, it's about 1.3 GB free after the system started.
I opened it and took a picture from the pcb

I see 2 Hynix H5TQ8G63CMR chip on the right. It is 2x8 Gbit, isn't it?

I bought this S905 box, it has 2GB memory (I can see in Android) but if I use gxbb_p201_2G.dtb then the box cannot boot with LE (it stucks at the S905 boot logo)
If I use gxbb_p201.dtb then the box boots and works (LAN and wifi OK) but with ony with 1 GB memory. The two dtb differs only in one bit.
I tried with 009, 010, 011, 012h, 012h_tsd and 7.95 beta6 tsd versions with the correspondent dtbs (009 and 010 has only 1GB dtb for p201) with the same result.
I also tried other dtbs for p200: The box can boot with the 1GB dtbs (but no LAN and wifi works) and cannot boot with the 2GB dtbs.
Same result with the default dtb.
The normal and the tsd versions are the same, the temp sensor works on the device if I use the normal version of LE.
The device is not rooted.
Could you help me to make a working dtb for this device?
What file do I have to provide from the android?

Quote from mmpp

These settings are necessary if you use spdif to connect to the receiver or the HDMI connection is limited by the device.

For any avr that accepts multi channel audio over HDMI you can input the actual speaker setup on a amlogic s905 device.

Why do you narrow it down to only S905? S905X is the same, isn't it?

Quote from steve_192

mmpp

It has the ASIX AX88179 chipset as recommended by Pelican on page 2 of this thread.

cabbresson

I didn't do anything. It worked upon boot.

[Edit: Got iperf working]

Code

[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  38.4 MBytes   321 Mbits/sec
[  4]   1.00-2.00   sec  37.8 MBytes   317 Mbits/sec
[  4]   2.00-3.00   sec  38.4 MBytes   321 Mbits/sec
[  4]   3.00-4.00   sec  38.2 MBytes   321 Mbits/sec
[  4]   4.00-5.00   sec  38.4 MBytes   321 Mbits/sec
[  4]   5.00-6.00   sec  38.2 MBytes   321 Mbits/sec
[  4]   6.00-7.00   sec  38.2 MBytes   320 Mbits/sec
[  4]   7.00-8.00   sec  38.4 MBytes   322 Mbits/sec
[  4]   8.00-9.00   sec  38.4 MBytes   321 Mbits/sec
[  4]   9.00-10.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  10.00-11.00  sec  38.4 MBytes   321 Mbits/sec
[  4]  11.00-12.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  12.00-13.00  sec  38.2 MBytes   320 Mbits/sec
[  4]  13.00-14.00  sec  37.1 MBytes   312 Mbits/sec
[  4]  14.00-15.00  sec  38.4 MBytes   321 Mbits/sec
[  4]  15.00-16.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  16.00-17.00  sec  38.4 MBytes   321 Mbits/sec
[  4]  17.00-18.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  18.00-19.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  19.00-20.00  sec  38.4 MBytes   322 Mbits/sec
[  4]  20.00-21.00  sec  38.4 MBytes   322 Mbits/sec
[  4]  21.00-22.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  22.00-23.00  sec  38.4 MBytes   322 Mbits/sec
[  4]  23.00-24.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  24.00-25.00  sec  38.2 MBytes   320 Mbits/sec
[  4]  25.00-26.00  sec  38.4 MBytes   322 Mbits/sec
[  4]  26.00-27.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  27.00-28.00  sec  38.4 MBytes   321 Mbits/sec
[  4]  28.00-29.00  sec  38.2 MBytes   321 Mbits/sec
[  4]  29.00-30.00  sec  38.4 MBytes   321 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-30.00  sec  1.12 GBytes   321 Mbits/sec                  sender
[  4]   0.00-30.00  sec  1.12 GBytes   321 Mbits/sec                  receiver

Display More

Edit 2: The above is with my Nexbox as the server (i.e. the Nexbox is receiving) The other way round the trasnfer is circa 186 Mbits/sec.

Display More

Congratulations!

Quote from coreire

Thanks, do you have it plugged into a USB 2.0 port? And does it actually connect in gigabit mode?

Of course, I've connected it to an USB 2.0 port (there is no USB 3.0 on these boxes).

ethtool usbnet0
Settings for usbnet0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Half 1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 3
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

[hr]

Quote from MrMagic

Is there a list of supported chips by the Linux kernel somewhere?

I found this one for example and it says "for Linux kernel", but it doesn't specify the chip.

I've been looking for an S905 TV box with 2 GB RAM and a working Gbit ethernet port, but sofar haven't had much luck.

I bought an H96 Plus from Gearbest and the ethernet port would connect, but upload speed was almost 0, making it unusable. Got refunded in the end.

I also bought an MXV box from Aliexpress, but it's very unstable and hangs all the time. I got LE working on it, but it only connects at 100M. Still in discussion with AE about it.

Why don't you buy a well known MINI MX or similar box which performs very well on the gigabit port.

Quote from coreire

Any recommendations on an adapter would be appreciated.
Thanks.

Look for ASIX AX88179 chip in the details when you buy USB 3.0Gigabit LAN adapter.
It works fine with the boxes because the Linux kernel supports it.
Mine looks like this:

Quote from kszaq

Thanks. Please also get udevadm info /sys/bus/sdio/devices/sdio*.

My Mini M8S II has 2GB/16GB

P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: MODALIAS=sdio:c00v02D0dA9A6
E: SDIO_CLASS=00
E: SDIO_ID=02D0:A9A6
E: SUBSYSTEM=sdio
E: [email protected]
E: TAGS=:systemd:
E: USEC_INITIALIZED=14327955
E: brcm_device=bcm43438a0

Quote from Inesca

Next problem: The remote is not working at all. I guess I have to find a working remote.conf for the V88 Pro somewhere?

Download this: v88_pro – Google Drive
copy to your card's root folder and reboot

stormrev, DEcosse, Poida:
Thanks for educating me.

I'm just wondering why someone tells bricked a box dead and then unbricked it.
If something has bricked then its bricked for ever and it means its useless as a brick, isn't it?
If you can use it later then it wasn't bricked.

The 011 version is out there...