diff --git a/4k+/Readme.md b/4k+/Readme.md deleted file mode 100644 index e4f201b..0000000 --- a/4k+/Readme.md +++ /dev/null @@ -1,9 +0,0 @@ -# Yi 4k+ - -Things specific to the yi4k+. - -[Bitrate Mod](bitrate/) The bitrate mod. - -[Firmware Unpacker](firmware_unpacker) Can be used to unpack the obfuscated firmware files for this camera. - -It seems that most of the stuff ([telnet](../telnet), [enable_logs](../enable_logs), [dump_camera_settings](../dump_camera_settings), [dump memory](../dump_memory) (you need to pick a valid memory address) and more.) that works on the yi4k works on the yi4k+. diff --git a/4k+/autoexec.ash_research/chg_res.txt b/4k+/autoexec.ash_research/chg_res.txt deleted file mode 100644 index 6ba939f..0000000 --- a/4k+/autoexec.ash_research/chg_res.txt +++ /dev/null @@ -1,20 +0,0 @@ - -This command can be used to change the resolution/framerate to any of the ones -in the bitrate addresses table. Note that many of the resolutions that are not -exposed by the interface (like the HDR resolutions) will crash the camera likely -because there isn't any code in the firmware to actually use them properly. - - -The command is: -t app test chg_res [index of resolution] - - -The index of the first resolution in the bitrate addresses table is 0, the -second one is 1 and so on. - -For example on firmware 1.3.11, 4k 60fps is at index 3 so: - -t app test chg_res 3 - -will switch to 4k 60fps on firmware 1.3.11. - diff --git a/4k+/autoexec.ash_research/record.txt b/4k+/autoexec.ash_research/record.txt deleted file mode 100644 index 4c72188..0000000 --- a/4k+/autoexec.ash_research/record.txt +++ /dev/null @@ -1,27 +0,0 @@ - -This command can be used to enable hevc. Only problem is that trying to record -with hevc enabled crashes the camera (firmware 1.3.11). This command may start -working properly in a future firmware version. - - -Usage: t app test record