Ben N Voutour

does it fix the issue with dvi to hdmi on devices that don't support 1920x1080? in multitool the monitor worked but after flashing the emmc and rebooting the monitor went into power saving mode. the monitor is an lg L196WTQ-BF in android it was locking to 1280x1024

what about using the emmc on the device instead of the sd card?

it seems that the mali-450 gpu can be clocked at 750 MHz and the ram can be clocked to 1.066 GHz and the cpu can be clocked up to 1.512 GHz

i used this in ubuntu wslg dtc -I dts -O dtb -f rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dts -o rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dtb and the thing threw warnings about missing phandle references and it compiled as you can see... it appears that the format syntax is as follows: the start of the settings uses a curled bracket without a semicolon and the end of that part has 2 line endings opp_table0 { compatible = "operating-points-v2"; opp-shared; phandle = <0x05>; opp-408000000 { opp-hz = <0x00 0x18519600>; opp-microvolt = <0xe7ef0>; clock-latency-ns = <0x9c40>; opp-suspend; }; opp-600000000 { opp-hz = <0x00 0x23c34600>; opp-microvolt = <0xe7ef0>; clock-latency-ns = <0x9c40>; }; opp-816000000 { opp-hz = <0x00 0x30a32c00>; opp-microvolt = <0xf4240>; clock-latency-ns = <0x9c40>; }; opp-1008000000 { opp-hz = <0x00 0x3c14dc00>; opp-microvolt = <0x10c8e0>; clock-latency-ns = <0x9c40>; }; opp-1200000000 { opp-hz = <0x00 0x47868c00>; opp-microvolt = <1200000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1296000000 { opp-hz = <0x00 0x4d3f6400>; opp-microvolt = <1225000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1392000000 { opp-hz = <0x00 0x52f83c00>; opp-microvolt = <1250000>; clock-latency-ns = <0x9c40>; status = "okay"; }; opp-1512000000 { opp-hz = <0x00 0x5a1f4a00>; opp-microvolt = <1350000>; clock-latency-ns = <0x9c40>; status = "okay"; }; }; rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dtb rk3318-box_1.5Ghz_SDCARD_v1b_ST_shr104.dtb rk3318-box_1.5Ghz_SDCARD_v1b_ST_sdhr104.dts log3318.txt

all i did was edit the raw dts file in notepad++ but the 1.5GHz is broken but it is just a bad setting in the dts file. how exactly do you edit the dts file in windows? should i use nano in ubuntu-wslg?

I Don't Know if this will work but please try this if it doesn't help, then i'm out of ideas for now... rk3318-box_1.5Ghz_SDCARD_v1a_ST_sdhr104.dts

try using it in android 9 and see if it works there first...

anyone who wants to experiment with higher cpu clocks and ram clocks at max , hope these work.

try these dtb/dts files https://drive.google.com/file/d/1bqYyalJLKCArETHCDF_6O7JocuAS-gUk/view?usp=sharing rk3318-evb-oc.dtb rk3318-evb-oc.dts

is there any chance that the rk3318 and rk3328 are one and the same? i found a lakka firmware for rk3328 , but i want to be sure it will work on rk3318...

how would i go about putting retroarch and emulationstation as the ui instead of the desktop? and how do i get a complete dtb dump from android 9 as root? and can the dtb file frrom android 9 be used for armbian?

i'd like to test the new version and see if it is any better the last build

could you do a log with the cpu clocked at 1.3 GHz?

https://docs.armbian.com/User-Guide_Fine-Tuning/

set your boot settings so that verbosity=1 is verbosity=7 and then run armbianmonitor -u and upload that.

it was in the google drive from the dms mod rom mine seems stable at 1.3 GHz but i want to test if it can go to 1.5 GHz. the overclock is more than just the cpu, it is also the ram clock so the cpu in theory should be able to hit 1.5 GHz and the memory should also be able to hit 1066 MHz without any major issues up front. in android the power limit is 5v 1.1a at idle i am using a 5v 4a power brick and it seems rock solid. look for the v3a rom from 4pda and get the dtb file if you can. (H96 MAX ?RK3318 Android 9) made by DMSSRU and it is called DMS Mod

what about recompiling the overclocked dtb file i sent? can it be used in a armbian build? i am trying the most recent build and it is fairly stable still testing ... Cheers

is there an option to boot from USB 3.0 hdd? and not sure how many devices have 2GB ram and some have 4GB

i just finished compiling a 2GB multitool from git in debian wsl still having compile issues with armbian in debian wsl where it says that wsl is not supported.

should i go for the legacy kernel, or mainline? i wanna test my overclocked dts file i'll probably need to convert it to dtb.

i'm trying to test these tweaks with android, soon possibly armbian...

here is a useful repo https://github.com/kthejoker20 it has the same tool i just uploaded to my G-Drive. and some more... i'll keep looking for other tools and newer versions as well when available.

https://drive.google.com/file/d/1dENjFNr1VTjxBLOJNyOHvcvTCi0jzkQI/view?usp=sharing ^ RK3xxx_firmware_tools_5.99.07.00 by Sergio Poverony Is there any newer version?

a newer version has appeared... http://www.mediafire.com/file/prt20aq5s0tqxbu/RK3xxx_firmware_tools_5.78.35.00.rar/file

i fixed it can it be reapplied to the ocvr npi image? 1.5GHz and 1066 MHz uncommented. Don't know if this helps in armbian but i'm looking forward to testing it. 3318-OCVR.nPI.dts