Do you have the remote.conf for me auslander ?
The remote.conf that was bundled with kszaq's builds works perfectly for me on my v2 W95 box.
Do you have the remote.conf for me auslander ?
The remote.conf that was bundled with kszaq's builds works perfectly for me on my v2 W95 box.
I have a similar issue.
I have two W95 s905w boxes with different board revisions. Using the same build and DTB as mentioned earlier in the thread (https://sx05.eu/s905/8.2/8.2.0.1/Lib...8.2.0.1.img.gz and https://sx05.eu/s905/8.2/device_tree...xl_p212_2g.dtb) the revision 2.0 device boots fine from usb, let me install to internal and has been running absolutely flawlessly ever since - It's been a great little player for the living room. Decided to get another, got a rev 3.0 board. This one goes directly to a black screen on boot from usb (after the initial logo from the manufacturer) - Same usb in the other device boots into a clean copy of kodi without issue.
I think the builds working with the DTBs from S905x is a fluke, and your mileage may vary.
Well, darn.
If you do decide to add support - let me know - I'll be happy to provide you with whatever I can to help with the effort.
Attached is the device tree and additional info for an s905w-based AZW W95 media player - Board Rev 3.0.
I have a rev 2.0 that works perfectly with gxl_p212_2g.img, but the v3.0 box gets stuck at a black screen after the initial boot logo.
Attached is output from the following commands:
1) adb shell dmesg > dmesg
2) adb shell cat /proc/device-tree/amlogic-dt-id > amlogic-dt-id
3) adb shell dd if=/dev/dtb | gzip > dtb.img.gz
Any help getting past the the black screen would be greatly appreciated!