HPH RK3288 Lollipop ROM v1.6 By Mo123

[orionas21]

I will try to build some new firmware soon.

Hi mo123

Any update regarding the new firmware?

[mo123]

Hi Mo,

just to confirm that passtrough is broken in 1.8 with Nagrace nt-v6 regardless of kodi version: nighties, ntmc, ftmc, spmc, etc.. (tried them all)
Hope to see a new release from you!
Thank you as always!!!!

I will try to build some new firmware soon.

[brio]

Hi Mo,

just to confirm that passtrough is broken in 1.8 with Nagrace nt-v6 regardless of kodi version: nighties, ntmc, ftmc, spmc, etc.. (tried them all)
Hope to see a new release from you!
Thank you as always!!!!

[jona5]

I will experiment a bit.
The problem is setting it toÂ*HDMI_ENABLE then users with 4K tv's will get 4K resolution and they will complain again as they want 1080p resolution set as default to run faster.
But I can make 3 different bootloaders and then users can use what they want, I just have to check that it then overwrites the kernel settings.

I don't have a 4K screen, but I just checked by setting the display to 480p resolution and it remembers it between reboots. The boot animation even comes up in 480p.

[mo123]

To be honest I'm struggling to make sense of what I'm seeing...!! Forgive for me jumping to conclusions etc!

If I use your 1.8 uboot loader V2.30.10.bin (or Ugoos V2.19.10) flashed with:

upgrade_tool UL RK3288UbootLoader_V2.30.10.bin

I get android coming up in 720p.

In the kernel log (dmesg) I see:

[ 0.000000] Kernel command line: vmalloc=496M console=ttyFIQ0 androidboot.hardware=rk30board androidboot.selinux=permissive androidboot.console=ttyFIQ0 board.ap_has_alsa=0 quiet coherent_pool=1M init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0 x00002000@0x00004000(misc),0x00008000@0x00006000(r esource),0x00008000@0x0000e000(kernel),0x00010000@ 0x00016000(boot),0x00010000@0x00026000(recovery),0 x0001a000@0x00036000(backup),0x00040000@0x00050000 (cache),0x00002000@0x00090000(kpanic),0x00200000@0 x00092000(system),0x00002000@0x00292000(metadata), 0x00020000@0x00294000(radical_update),-@0x002b4000(userdata) storagemedia=emmc uboot_logo=0x02000000@0x7dc00000 loader.timestamp=2016-11-27_10:05:28 hdmi.vic=4 tve.format=-1


If I use the Wasser 4.0.11 RK3288UbootLoader_V2.30.10.bin

I get Android booting straight into the best mode my screen supports,
and I see in dmesg:

[ 0.000000] Kernel command line: vmalloc=496M console=ttyFIQ0 androidboot.hardware=rk30board androidboot.selinux=permissive androidboot.console=ttyFIQ0 board.ap_has_alsa=0 quiet coherent_pool=1M init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0 x00002000@0x00004000(misc),0x00008000@0x00006000(r esource),0x00008000@0x0000e000(kernel),0x00010000@ 0x00016000(boot),0x00010000@0x00026000(recovery),0 x0001a000@0x00036000(backup),0x00040000@0x00050000 (cache),0x00002000@0x00090000(kpanic),0x00200000@0 x00092000(system),0x00002000@0x00292000(metadata), 0x00020000@0x00294000(radical_update),-@0x002b4000(userdata) storagemedia=emmc uboot_logo=0x02000000@0x7dc00000 loader.timestamp=2016-08-26_18:34:18

It looks like your 1.8 uboot is struggling to read the EDID from my screen and putting in that hdmi.vic=4 entry

uboot output:
rk_hdmi_register:fail to read deviceinfo
failed to find part:baseparamer
[EDID-EXTEND] It is a CEA 861 Series Extension.
[EDID-CEA] error version.
no edid message:use default vic config:4
hdmi_dev->video.vic is 4

From rk_hdmi.c:

[FONT=courier new]/*if read edid error,use default vic mode, or not check pos_baseparamer and selete best video mode*/[/FONT]

rk_hdmi.h:

[FONT=courier new]#define HDMI_VIDEO_DEFAULT_MODE HDMI_1280x720p_60HZ//HDMI_1920x1080p_60HZ

/*
* If HDMI_ENABLE, system will auto configure output mode according to EDID
* If HDMI_DISABLE, system will output mode according to
* macro HDMI_VIDEO_DEFAULT_MODE
*/
#define HDMI_AUTO_CONFIGURE HDMI_DISABLE[/FONT]

I imagine this should be HDMI_ENABLE ??

I don't know how Wasser uboot gets it right because I don't get any uart output with his loader, maybe this setting or he has rk_hdmi v2?

I will experiment a bit.
The problem is setting it to HDMI_ENABLE then users with 4K tv's will get 4K resolution and they will complain again as they want 1080p resolution set as default to run faster.
But I can make 3 different bootloaders and then users can use what they want, I just have to check that it then overwrites the kernel settings.

[jona5]

The v1.8a firmware defaults to 1080p@60hz resolution now instead of 720p as in the v1.8 firmware, it might only be a problem for users with 720p displays.

What uboot file is that?
I can build some new uboot images for testing.
If you build a kernel like I have it can be 720p or 1080p and overwrites any other setting. You can also build a kernel which is supposed to remember the resolution set, but I think this uboot setting you mention is then overwriting the kernel setting.
Is there a different non standard resolution your display is using then I can find out how to get it to work better?

To be honest I'm struggling to make sense of what I'm seeing...!! Forgive for me jumping to conclusions etc!

If I use your 1.8 uboot loader V2.30.10.bin (or Ugoos V2.19.10) flashed with:

upgrade_tool UL RK3288UbootLoader_V2.30.10.bin

I get android coming up in 720p.

In the kernel log (dmesg) I see:

[ 0.000000] Kernel command line: vmalloc=496M console=ttyFIQ0 androidboot.hardware=rk30board androidboot.selinux=permissive androidboot.console=ttyFIQ0 board.ap_has_alsa=0 quiet coherent_pool=1M init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0 x00002000@0x00004000(misc),0x00008000@0x00006000(r esource),0x00008000@0x0000e000(kernel),0x00010000@ 0x00016000(boot),0x00010000@0x00026000(recovery),0 x0001a000@0x00036000(backup),0x00040000@0x00050000 (cache),0x00002000@0x00090000(kpanic),0x00200000@0 x00092000(system),0x00002000@0x00292000(metadata), 0x00020000@0x00294000(radical_update),-@0x002b4000(userdata) storagemedia=emmc uboot_logo=0x02000000@0x7dc00000 loader.timestamp=2016-11-27_10:05:28 hdmi.vic=4 tve.format=-1


If I use the Wasser 4.0.11 RK3288UbootLoader_V2.30.10.bin

I get Android booting straight into the best mode my screen supports,
and I see in dmesg:

[ 0.000000] Kernel command line: vmalloc=496M console=ttyFIQ0 androidboot.hardware=rk30board androidboot.selinux=permissive androidboot.console=ttyFIQ0 board.ap_has_alsa=0 quiet coherent_pool=1M init=/init mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0 x00002000@0x00004000(misc),0x00008000@0x00006000(r esource),0x00008000@0x0000e000(kernel),0x00010000@ 0x00016000(boot),0x00010000@0x00026000(recovery),0 x0001a000@0x00036000(backup),0x00040000@0x00050000 (cache),0x00002000@0x00090000(kpanic),0x00200000@0 x00092000(system),0x00002000@0x00292000(metadata), 0x00020000@0x00294000(radical_update),-@0x002b4000(userdata) storagemedia=emmc uboot_logo=0x02000000@0x7dc00000 loader.timestamp=2016-08-26_18:34:18

It looks like your 1.8 uboot is struggling to read the EDID from my screen and putting in that hdmi.vic=4 entry

uboot output:
rk_hdmi_register:fail to read deviceinfo
failed to find part:baseparamer
[EDID-EXTEND] It is a CEA 861 Series Extension.
[EDID-CEA] error version.
no edid message:use default vic config:4
hdmi_dev->video.vic is 4

From rk_hdmi.c:

[FONT=courier new]/*if read edid error,use default vic mode, or not check pos_baseparamer and selete best video mode*/[/FONT]

rk_hdmi.h:

[FONT=courier new]#define HDMI_VIDEO_DEFAULT_MODE            HDMI_1280x720p_60HZ//HDMI_1920x1080p_60HZ

/*
 * If HDMI_ENABLE, system will auto configure output mode according to EDID
 * If HDMI_DISABLE, system will output mode according to
 * macro HDMI_VIDEO_DEFAULT_MODE
 */
#define HDMI_AUTO_CONFIGURE            HDMI_DISABLE[/FONT]

I imagine this should be HDMI_ENABLE ??

I don't know how Wasser uboot gets it right because I don't get any uart output with his loader, maybe this setting or he has rk_hdmi v2?

[mo123]

This is a problem.

The new rockchip v2 hdmi drivers are FINALLY able to read the EDID information from my odd screen,
only to be foiled by a hard coded hdmi.vic=4 (1280x720p60) in your u-boot (v1.8)
which is passed to the kernel on the cmdline every time it boots.

Before I try another bootloader, is there a way to override the uboot environment or will perhaps adding vic=0 to parameter.txt cmdline help?

/**
* hdmi_find_best_mode: find the video mode nearest to input vic
* @hdmi:
* @vic: input vic
*
* NOTES:
* If vic is zero, return the high resolution video mode vic.
*/

The v1.8a firmware defaults to 1080p@60hz resolution now instead of 720p as in the v1.8 firmware, it might only be a problem for users with 720p displays.

What uboot file is that?
I can build some new uboot images for testing.
If you build a kernel like I have it can be 720p or 1080p and overwrites any other setting. You can also build a kernel which is supposed to remember the resolution set, but I think this uboot setting you mention is then overwriting the kernel setting.
Is there a different non standard resolution your display is using then I can find out how to get it to work better?

[jona5]

Flash it.
Resolution dont save. After reboot resolusion reset to 1280x720.

This is a problem.

The new rockchip v2 hdmi drivers are FINALLY able to read the EDID information from my odd screen,
only to be foiled by a hard coded hdmi.vic=4 (1280x720p60) in your u-boot (v1.8)
which is passed to the kernel on the cmdline every time it boots.

Before I try another bootloader, is there a way to override the uboot environment or will perhaps adding vic=0 to parameter.txt cmdline help?

/**
* hdmi_find_best_mode: find the video mode nearest to input vic
* @hdmi:
* @vic: input vic
*
* NOTES:
* If vic is zero, return the high resolution video mode vic.
*/

[mo123]

Mo, can you kindly confirm that the wifi drivers for Orion Pro is supported in your rom. Thank you.

It supports AP6335 wifi not AP6210.

[Cypher]

Yes it is different, mo123 has to verify what drivers has in his ROM.

Mo, can you kindly confirm that the wifi drivers for Orion Pro is supported in your rom. Thank you.

[orionas21]

Hi mo123!
Any update in your investigation?
Looking forward for your resolution!!

[lonely2k5]

hi mo123
can i ask a favour? could you make img to boot from SD?
i read other posts and it supposed to be running smoother from sdcard. i have mk902II and all android 5 roms are choppy so i bought sandisk extreme 16gb card and would like to try your rom on it as it is the best. i have many problems with other roms without keyboard fix etc.

thanx

p.s. as for the image other day that i couldn't extract with 7zip. i guess it's the problem as i run win10 32bit. on other pc with win10 64bit it inpacked without problem.

[orionas21]

Strange. But in 1.8 and 1.8a i lost HDMI bitstream (noise). Work only spdif passthrough

This is the problem i also mention.
I sent to mo123 the syslog and NTMC debug logs to investigate.
Collect them also especially if you have another device (I have a Tronsmart r28 Meta 2G/16G).
Maybe mo123 will need them also to find the solution.

[bib]

Strange. But in 1.8 and 1.8a i lost HDMI bitstream (noise). Work only spdif passthrough

[orionas21]

Hi mo123. The problem with noise remains also in this rom.
I pm you the syslog and ntmc logs from my system.
I will leave the 1.8.a temporarily in case you need anything else.