Bluetimes RK3288 boxes

[OZReddog]

Shomari, thanks for trying the camera and skype, all good news. Handy to know that the power supply is adequate. I know some queried if a 5v 2.5a power supply would be adequate.

[no_spam_for_me]

ahhh, ok, that's funny, open as text at ES file explorer (ignores the error) and than do a
adb shell dmesg > dmesg.txt

<4>[24510.787026] DVFS TREE:
<4>[24510.787053] |
<4>[24510.787053] |- voltage domain:vd_gpu
<4>[24510.787092] |- current voltage:900000
<4>[24510.787116] |- current regu_mode:UNKNOWN
<4>[24510.787147] |  |
<4>[24510.787147] |  |- power domain:pd_gpu, status = OFF, current volt = 900000, current regu_mode = UNKNOWN
<4>[24510.787198] |  |  |
<4>[24510.787198] |  |  |- clock: clk_gpu current: rate 198000, volt = 900000, enable_dvfs = ENABLE
<4>[24510.787249] |  |  |- clk limit(enable):[198000000, 480000000]; last set rate = 198000
<4>[24510.787281] |  |  |  |- freq = 198000, volt = 900000
<4>[24510.787309] |  |  |  |- freq = 297000, volt = 950000
<4>[24510.787335] |  |  |  |- freq = 313000, volt = 1100000
<4>[24510.787361] |  |  |  |- freq = 480000, volt = 1150000
<4>[24510.787392] |  |  |- clock: clk_gpu current: rate 198000, regu_mode = UNKNOWN, regu_mode_en = 0
<4>[24510.787423] |
<4>[24510.787423] |- voltage domain:vd_logic
<4>[24510.787460] |- current voltage:1125000
<4>[24510.787484] |- current regu_mode:UNKNOWN
<4>[24510.787513] |  |
<4>[24510.787513] |  |- power domain:pd_vio, status = OFF, current volt = 1100000, current regu_mode = UNKNOWN
<4>[24510.787564] |  |  |
<4>[24510.787564] |  |  |- clock: aclk_vio1 current: rate 297000, volt = 1100000, enable_dvfs = ENABLE
<4>[24510.787612] |  |  |- clk limit(enable):[99000000, 297000000]; last set rate = 297000
<4>[24510.787643] |  |  |  |- freq = 99000, volt = 1100000
<4>[24510.787670] |  |  |  |- freq = 297000, volt = 1100000
<4>[24510.787701] |  |  |- clock: aclk_vio1 current: rate 297000, regu_mode = UNKNOWN, regu_mode_en = 0
<4>[24510.787736] |  |
<4>[24510.787736] |  |- power domain:pd_ddr, status = OFF, current volt = 1125000, current regu_mode = UNKNOWN
<4>[24510.787786] |  |  |
<4>[24510.787786] |  |  |- clock: clk_ddr current: rate 456000, volt = 1125000, enable_dvfs = ENABLE
<4>[24510.787835] |  |  |- clk limit(enable):[200000000, 528000000]; last set rate = 456000
<4>[24510.787866] |  |  |  |- freq = 200000, volt = 1075000
<4>[24510.787893] |  |  |  |- freq = 300000, volt = 1075000
<4>[24510.787919] |  |  |  |- freq = 456000, volt = 1125000
<4>[24510.787945] |  |  |  |- freq = 528000, volt = 1150000
<4>[24510.787975] |  |  |- clock: clk_ddr current: rate 456000, regu_mode = UNKNOWN, regu_mode_en = 0
<4>[24510.788006] |
<4>[24510.788006] |- voltage domain:vd_arm
<4>[24510.788043] |- current voltage:900000
<4>[24510.788066] |- current regu_mode:UNKNOWN
<4>[24510.788095] |  |
<4>[24510.788095] |  |- power domain:pd_core, status = OFF, current volt = 900000, current regu_mode = UNKNOWN
<4>[24510.788145] |  |  |
<4>[24510.788145] |  |  |- clock: clk_core current: rate 312000, volt = 900000, enable_dvfs = ENABLE
<4>[24510.788193] |  |  |- clk limit(enable):[312000000, 1800000000]; last set rate = 312000
<4>[24510.788224] |  |  |  |- freq = 312000, volt = 900000
<4>[24510.788251] |  |  |  |- freq = 408000, volt = 900000
<4>[24510.788277] |  |  |  |- freq = 600000, volt = 950000
<4>[24510.788303] |  |  |  |- freq = 696000, volt = 950000
<4>[24510.788330] |  |  |  |- freq = 816000, volt = 1000000
<4>[24510.788356] |  |  |  |- freq = 1008000, volt = 1050000
<4>[24510.788382] |  |  |  |- freq = 1200000, volt = 1100000
<4>[24510.788409] |  |  |  |- freq = 1416000, volt = 1200000
<4>[24510.788437] |  |  |  |- freq = 1512000, volt = 1300000
<4>[24510.788463] |  |  |  |- freq = 1608000, volt = 1350000
<4>[24510.788490] |  |  |  |- freq = 1704000, volt = 1350000
<4>[24510.788517] |  |  |  |- freq = 1800000, volt = 1350000
<4>[24510.788547] |  |  |- clock: clk_core current: rate 312000, regu_mode = UNKNOWN, regu_mode_en = 0
<4>[24510.788577] -------------DVFS TREE END------------

Do you have MORE useful tips like this?


EDIT:
adb shell cat /sys/dvfs/dvfs_tree
befor the dmesg also helps

[pedorie]

how to update?

[QUOTE=Shomari;226289]New firmware for the Bluetimes QPRO brings updated kernel (1080p of course), HDMI compatibility fixes and Wifi Direct improvements. Released 09/11/14:

DOWNLOAD: https://mega.co.nz/#!acxVQASb!-8ZFJU...NblLgYdAl3yEc0

---

hi, Shomari and other forum members,

i have ordered a measy B4S, and received it last week.
It also conains this same PCB.
What tools do i need to program this firmware?


kind regards,
Pedorie

[Shomari]

[QUOTE=pedorie;226772]

New firmware for the Bluetimes QPRO brings updated kernel (1080p of course), HDMI compatibility fixes and Wifi Direct improvements. Released 09/11/14:

DOWNLOAD: https://mega.co.nz/#!acxVQASb!-8ZFJU...NblLgYdAl3yEc0

---

hi, Shomari and other forum members,

i have ordered a measy B4S, and received it last week.
It also conains this same PCB.
What tools do i need to program this firmware?


kind regards,
Pedorie

...do you mean to install the firmware?

[pedorie]

[QUOTE=Shomari;226774]

...do you mean to install the firmware?

Yes, sorry. Installing not updating..

Regards,
Peter

[Shomari]

[QUOTE=pedorie;226777]

Yes, sorry. Installing not updating..

Regards,
Peter

It's OK just wanted to be sure. Use the Rockchip Batch Tool 2.3 https://mega.co.nz/#!nFwjXLZa!EqRJNX...XaZRRR9wiU3U6w

As a reminder, it's always best to have a backup before making any system changes.

[Shomari]

Also, the latest firmware (linked above) limits the DDR clock speed to a lower freq. I have another firmware I recommend over this one.


From my testing, of all the compatible firmwares posted here I'd recommend this one over the others. Not signifcant differences, but this one is stable and has the highest clock speeds for memory and scales from 126MHz-1.8GHz. Some users may not like that. If so, you can simply use the kernel from the 09/11/14 firmware instead, which scales form 312MHz-1.8GHz.

https://mega.co.nz/#!LAwVgIyK!MoQkX45n7LcucCXxLiHxKIGBFUV3kwGtbrZQRT-sKdw

[pedorie]

[QUOTE=Shomari;226779]

It's OK just wanted to be sure. Use the Rockchip Batch Tool 2.3 https://mega.co.nz/#!nFwjXLZa!EqRJNX...XaZRRR9wiU3U6w

As a reminder, it's always best to have a backup before making any system changes.

Thank you.

I don't have a backup. but i will search for it..
Now i have android 4.4.2 on the RK3288 player. the Cloudnetgo version is only 4.2 ??

see picture.


Do you think i should install the new firmware?

Regards,
Peter

[Shomari]

[QUOTE=pedorie;226786]

Thank you.

I don't have a backup. but i will search for it..
Now i have android 4.4.2 on the RK3288 player. the Cloudnetgo version is only 4.2 ??

see picture.
[ATTACH=CONFIG]7941[/ATTACH]

Do you think i should install the new firmware?

Regards,
Peter

It's not 4.2. You saw a typo. It's 4.4.2; as are all RK3288 ROMs in the wild.

[pedorie]

[QUOTE=Shomari;226788]

It's not 4.2. You saw a typo. It's 4.4.2; as are all RK3288 ROMs in the wild.

Ok, I give it a try..
Thank you!

[Shomari]

[QUOTE=pedorie;226789]

Ok, I give it a try..
Thank you!

..no problem! Good luck

[OZReddog]

Okay, now I am confused as we have 3 firmware visions (7z files) I think:

1. bluetimes_firmware082714 - 263,660 KB
2. bluetimes_QPRO_091114 - 204,833 KB
3. Bluetimes_QPRO - 207,475 KB

Plus, presumably the firmware version supplied with the box.

So, given your advice earlier, which version is which? Which gives any advantages?

Nuby question, how do you back up the original firmware? Do you use the tools as referred to earlier? Is there a tutorial?

[OZReddog]

Related question, what would happen if you installed firmware from another brand or a ROM from here on this box? Will it brick it? If so, can it be recovered by installing another correct version?

Pedorie, I assume that you have opened the Measy B4S? If not, how do you know that it has the same PCB?

Interesting observation, the Measy PCB appears to be the other way up, i.e. if you use the Bluetimes as a reference, the Measy PCB is installed upside down, or vise-versa. I wonder if this would have an effect on cooling given the vents are in the bottom of the box on the Bluetimes. Pedorie, does the Measy have slots or holes in the base?

[Shomari]

Re: Bluetimes RK3288 boxes

Related question, what would happen if you installed firmware from another brand or a ROM from here on this box? Will it brick it? If so, can it be recovered by installing another correct version?

Pedorie, I assume that you have opened the Measy B4S? If not, how do you know that it has the same PCB?

Interesting observation, the Measy PCB appears to be the other way up, i.e. if you use the Bluetimes as a reference, the Measy PCB is installed upside down, or vise-versa. I wonder if this would have an effect on cooling given the vents are in the bottom of the box on the Bluetimes. Pedorie, does the Measy have slots or holes in the base?

Yeah I don't like the fact the QPRO has the heatsink facing inwards towards the bottom of the box - some would call it upside down.

The Measy has the heatsink facing up (presumably, I've never opened one to see the heatsink setup) but it doesn't have vents along the top. At least the QPRO has vents along the bottom, but I would call them less than optimal.

If you install incompatible firmware the device would simply be rendered inoperable until proper firmware is installed.

I like the firmware I linked [today] simply because it has better connectivity, better read/write speeds, and higher DDR clock frequency.

Apart from that, the CPU scales down to 126MHz when idle, something I like given the fact I never unplug mine, I simply use the included remote to put it on standby/resume.

As for all the different firmwares, that's a huge plus. Plenty users of RK devices wish they had the broad ROM comptatibility this device (the QPRO) enjoys; in the long run it will allow for easy construction of custom ROMs and with additional baked in features/mods.

[Shomari]

Nuby question, how do you back up the original firmware? Do you use the tools as referred to earlier? Is there a tutorial?

There's an easy (though involved) tutorial to dump the ROM linked somewhere in the forums; I'm sorry I can't link it now as I'm entertaining guests.

Using the RK Batch Tool 2.3 you can also dump the major partitions such as resource, misc, system, kernel and recovery.