How to get 1600Mhz on the mx1?

[gianpaoloc]

Hi Bob and all you out there.
I am an happy user of the finless 1.5 rom on my mk809ii (a clone of the imito mx1). The only thing I would like to change is the max cpu speed that apparently cannot go above 1200Mhz. I put a heatsink on my device so overheating should not be a problem for me. I found that this requires to patch the kernel (changing file board-rk30-box.c where it says devfs_clk_enable_limit, if I understood it correctly) and was wondering if this is possible, how to do it, or how to get the same result without recompiling the kernel. Indeed I imagine that kernel recompilation is not possible due to lack of certain drivers, e.g. wlan.

Any suggestion?

Bob, have you recompiled the kernel yourself to produce the 1.5 finless rom for mx1, or you used an existing kernel?

Sent from my Nexus 7 using Tapatalk HD

[marcedli]

Re: How to get 1600Mhz on the mx1?

enabling 1.6 is just a thing. the current freq steps and voltage values will probably not be that stable on higher freq

so when you find a way to enable full load of the cpu you'll have to pay attention for finding the proper settings for those too

Sent from SGS III GT-I9300 🙋🙎🙍🙇🙅🙌

[Finless]

The main reason they locked the kernel to a max of 1.2 is HEAT! There is nothing in these stick to pull the heat off the Proc. If you go above 1.2 (if we unlock the kernel) you will FRY your device in a few minutes!

So stock kernel will not allow this for obvious user burn up reasons!


Bob

[gianpaoloc]

Re: How to get 1600Mhz on the mx1?

The main reason they locked the kernel to a max of 1.2 is HEAT! There is nothing in these stick to pull the heat off the Proc. If you go above 1.2 (if we unlock the kernel) you will FRY your device in a few minutes!

So stock kernel will not allow this for obvious user burn up reasons!

Bob

First of all, thanks a lot for your work Bob, your roms are much better than those coming with these devices.

I fully understand the risks connected with going full speed, and this is why, as I mentioned, I installed a heatsink on my cpu (and I am evaluating installing a fan, also).

This premitted, may you give me some hints on how to "unlock" the kernel as you have done in your 1.7 ROM? In principle I could use that rom directly, but it does not support my wlan chip. Notice that I am a relatively expert linux user, so I am not scared by patching, compiling, etc. :-)

Thanks in advance to everyone may provide suggestions

Sent from my Nexus 7 using Tapatalk HD

[Ridata]

The main reason they locked the kernel to a max of 1.2 is HEAT! There is nothing in these stick to pull the heat off the Proc. If you go above 1.2 (if we unlock the kernel) you will FRY your device in a few minutes!

So stock kernel will not allow this for obvious user burn up reasons!


Bob

Hi finless, let me tell you that what you say is correct. I have an IMITO MX1 which suffers from random reboot issues/freezing and the device aluminum case is practically burning after some minutes of being used.

As you said the stock clock cpu speeds are set to 1.2GhZ maximum by factory (we can lower this speed with programs like android tunner, and we sure don´t want to overclock! it is burning and crashing at 1.2GHz already!)

I have been running tests, because the room temperature here it is summer and you will not belive how hot the device gets in the summer. I started testing, different power supplies,and thats not the problem, problem is heat, i even had artifacts showing in a live wallpaper after some minutes of usage, thats not the ac adapter, its heat

I DO HAVE A PROBLEM ...I CANNOT DownCLOCK THE GPU SPEED, and lower it.
I have been trying to lower the GPU clock by half, but i have no experience with android whatsoever. Someone told me that the GPU speed can be downclocked with the boot.img modified. Is it possible that you can create a boot720p.img with the gpu speed clocked by half? I think that would at least help the people with reboots and freezes to actually get a working device with lower score but at least it would not fail so much.

the reason i am asking this is practically because the device is getting useless because of heat, and i have clocked the CPU speed at 200mhz and 500mhz but still it gets very hot in the case, the antutu score for CPU goes lower, but the score for GPU is always high.

[Finless]

The only thing I can find in boot.img to set GPU is this line in init.rc

insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50

Not sure what these values do? So if you can find more info on downclocking I can look into making a boot.img that is GPU downclocked.

Bob

[Ridata]

The only thing I can find in boot.img to set GPU is this line in init.rc

insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50

Not sure what these values do? So if you can find more info on downclocking I can look into making a boot.img that is GPU downclocked.

Bob

bob
thats it! can you change it to:

insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200 mali_init_clock=50

with that we will downclock it. if it still freezes i will let you all know
i will flash the bootimg and test it!

[gianpaoloc]

Coming back to the issue of "overclocking" (or better "correctly clocking" :-), while I was waiting for an help from the experts, I made some tests myself. In particular, I tried flashing the Finless 1.7 "overclocked" kernel only to my mk809ii, which has Finless 1.5 on board. I left all the other parts (including boot and system) as they are (i.e., Finless 1.5). The device booted perfectly and I was able to clock the CPU up the expected 1.6Mhz using an appropriate governor. Benchmarks had the expected boost. Unfortunately the wireless does not work. I tried doing:

insmod wlan.ko

where wlan0.ko is the kernel driver (in /system/lib/modules) for the Mediatek MT5931 wifi chip integrated into my mk809ii. The command does not return arrors, and seems to work (even looking at dmesg and logcat I could not find errors), but a subsequent:

iwconfig wlan0

reveals that the device is still unknown.

Any help from the experts out there?

There is really no chance of using the "overclocked" kernel with mk809ii and the other devices which use the same wifi driver (e.g., iMito mx1 and mx2, UG007, MK802iiis)?

[daemonium]

Coming back to the issue of "overclocking" (or better "correctly clocking" :-), while I was waiting for an help from the experts, I made some tests myself. In particular, I tried flashing the Finless 1.7 "overclocked" kernel only to my mk809ii, which has Finless 1.5 on board. I left all the other parts (including boot and system) as they are (i.e., Finless 1.5). The device booted perfectly and I was able to clock the CPU up the expected 1.6Mhz using an appropriate governor. Benchmarks had the expected boost. Unfortunately the wireless does not work. I tried doing:

insmod wlan.ko

where wlan0.ko is the kernel driver (in /system/lib/modules) for the Mediatek MT5931 wifi chip integrated into my mk809ii. The command does not return arrors, and seems to work (even looking at dmesg and logcat I could not find errors), but a subsequent:

iwconfig wlan0

reveals that the device is still unknown.

Any help from the experts out there?

There is really no chance of using the "overclocked" kernel with mk809ii and the other devices which use the same wifi driver (e.g., iMito mx1 and mx2, UG007, MK802iiis)?

Hi gianpaoloc, we're on the same boat. My stick is a MK802IIIs (same as Imito MX1), i'm trying to "correctly clock it" too. We are at the same point, i've compiled my own kernel (without the mediatek drivers, of course) and also tried to insmod wlan.ko with same result. You've gone a little bit far than me by "correctly clocking" with finless 1.7 kernel.
I've missed to change this in my custom kernel but i will recompile it changing the values to upper ones.

 #ifdef CONFIG_MACH_RK30_BOX_HOTDOG
        dvfs_clk_enable_limit(clk_get(NULL, "gpu"), 133 * 1000000, 266 * 1000000);
        dvfs_clk_enable_limit(clk_get(NULL, "cpu"), 252 * 1000000, 1200 * 1000000);

Just for curiosity, can you share a pic of your heatsink? I will add one to mine but i'm in doubt which kind of it is better.
So, long story short, you're not alone

[Finless]

wlan.ko is not the full driver.

Try this:
Copy out everything from
system/etc/firmware
system/etc/wifi/wifi_supplicant
system/lib/modules/

key here is you may need drivers from there, and rkwifi.ko and wlan.ko

If this does not work, then driver is in the kernel.

Bob

[Ridata]

wlan.ko is not the full driver.

Try this:
Copy out everything from
system/etc/firmware
system/etc/wifi/wifi_supplicant
system/lib/modules/

key here is you may need drivers from there, and rkwifi.ko and wlan.ko

If this does not work, then driver is in the kernel.

Bob

hi finless any chance you change http://www39.zippyshare.com/v/53680947/file.html


from this insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50

to this:
mali_dvfs=50,100,133,160,200 mali_init_clock=50


i really wanto to twast the imito freezes

[daemonium]

wlan.ko is not the full driver.

Try this:
Copy out everything from
system/etc/firmware
system/etc/wifi/wifi_supplicant
system/lib/modules/

key here is you may need drivers from there, and rkwifi.ko and wlan.ko

If this does not work, then driver is in the kernel.

Bob

Do i need to do that even if i'm flashing my own kernel over your ROM ?

[daemonium]

hi finless any chance you change http://www39.zippyshare.com/v/53680947/file.html


from this insmod /system/lib/modules/mali.ko mali_dvfs=50,100,133,160,200,266,400 mali_init_clock=50

to this:
mali_dvfs=50,100,133,160,200 mali_init_clock=50


i really wanto to twast the imito freezes

Please Ridata, we are not talking about that right here... I told you by PM i will try to do it but also keep in mind i don't know which will be the result, so be patient , ok? If you're in a hurry you can take a look at this thread, there's all the info you need. I've learnt a lot by reading it. --> http://www.freaktab.com/showthread.p...cks-by-Finless

[gianpaoloc]

wlan.ko is not the full driver.

Try this:
Copy out everything from
system/etc/firmware
system/etc/wifi/wifi_supplicant
system/lib/modules/

key here is you may need drivers from there, and rkwifi.ko and wlan.ko

If this does not work, then driver is in the kernel.

Bob

Hi Finless, thanks for jumping in.

I agree with daemonium (nice nick, btw, especially today :-) that the steps of copying system/etc/firmware etc. should not be required as we are using the 1.7 kernel with the 1.5 rom, so the entire /system partition is that of 1.5, which already includes the right driver firmwares, if any.

As far as your suggestion of loading rkwifi.ko instead of wlan.ko I am also not sure it is correct. Indeed, I looked at my dmesg (using the working 1.5 kernel), where this line appears:

"MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 1.07) init"

and I found this exact string into the wlan.ko driver. Moreover, the 1.5 rom does not load the rkwifi.ko driver (I am attaching the list of modules loaded with the 1.5 rom, where wifi works; it includes wlan.ko but not rkwifi.ko)

For daemonium... currently I cannot take a picture of the heatsink I am using, but I got it from an old celeron. It is similar to the one in the attached picture.

Again, any help will be appreciated (and I will notify the thread of any step I am able to do in the right direction)

mk809ii_finless15_lsmod.txt

[daemonium]

Re: How to get 1600Mhz on the mx1?

Do you plan to use the fan or just the heatsink? I do belive the heatsink should be enough.
About my nick.. Yeah, today is shining more than ever with all the Pope thing XD