![]() ![]() a/arch/arm64/configs/odroidc4_android_defconfig a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dtsĭiff -git a/arch/arm64/configs/odroidc4_android_defconfig b/arch/arm64/configs/odroidc4_android_defconfig so you need to set it again after update.Ĭode: Select all diff -git a/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts b/arch/arm64/boot/dts/amlogic/meson64_odroidc4.dts ![]() This env variable will overwritten at update. When have a free time i will try to check why boot.ini and env.ini not reading while booting recovery. Any suggestion what I can do about it?Ĭode: Select all fw_setenv boot_recovery 'if test $ ' It's so bad that youtube or online content has to buffer constantly. There is very little radio interference (house), and other terminals have no problem achieving rates of 80Mbps - but the odroid with module 5 (and also module 0) gets a measly 2Mbps. I'm currently using a Wifi module 5 (the old one, ) and I get terrible performance at a 5m distance from the AP (2.5GHz, no walls). One problem that I haven't fixed, sadly, is wifi performance. I'll make sure to leave the screen in autodetection mode. I checked, and it's running the Oct 15 update (so the update finished correctly). I did a new reboot, and now I got the Android screen. This time it booted to system (still dark screen). Couldn't get touch input to work, nor a mouse, so I rebooted (from serial) again. So, I ran recovery in the serial shell, while in recovery, and it displayed the recovery screen. ![]() I booted and still the screen was black (though it didn't keep saying no signal as it did before). I mounted the emmc on a different system and changed boot.ini and env.ini and manually set the VU7 resolution (was 720p before). Ok, not sure what I did exactly, but I got it to boot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |