NEOMODE CUSTOM ROM MK809III AP6210 Version 1.9a *UPDATE*

[tobr]

Hi tobr,

do you mean that you are using an overclocked version of kernel from stock rom for cloudnetgo CR11S, flashed on Neo 1.9a and with a RK3188-T?
Have you used phjanderson's tool for overclocking?

Thanks for your attention.

Yes to kernel and rom neomode 1.9a with bootloader 2.07 or 2.06 (the one from 1.9a rom).
I use either 1080p from cloudneto (overclocked) or basic kernel from neomode 1.9a 720p (overclocked). Both of them dont flicker or blink (my box is otherwise heavy blinking).

But I only think I have 3188T (it can be 3188 as well) in my box mk902 (on motherboard produced in 12/2013). I already have bought thermal adhesive to remove heatsink and to look at it. I guess 3188T because of blinking, the fact that nearly none of the roms works and overclocked kernels usualy dont work. But stock kernels overclocked are working very fine. So I use either stock kernels (720 or 1080) or the only working for me custom 720p kernel from neomode. I dont know what is basic kernel in neomode 1.9a like, but it is the only one custom working without blinking. Kernel 3 dont boot at all.

Yes phjanderson's tool without changes in source code.

[ToBe]

Yes to kernel and rom neomode 1.9a with bootloader 2.07 or 2.06 (the one from 1.9a rom).
I use either 1080p from cloudneto (overclocked) or basic kernel from neomode 1.9a 720p (overclocked). Both of them dont flicker or blink (my box is otherwise heavy blinking).

But I only think I have 3188T (it can be 3188 as well) in my box mk902 (on motherboard produced in 12/2013). I already have bought thermal adhesive to remove heatsink and to look at it. I guess 3188T because of blinking, the fact that nearly none of the roms works and overclocked kernels usualy dont work. But stock kernels overclocked are working very fine. So I use either stock kernels (720 or 1080) or the only working for me custom 720p kernel from neomode. I dont know what is basic kernel in neomode 1.9a like, but it is the only one custom working without blinking. Kernel 3 dont boot at all.

Yes phjanderson's tool without changes in source code.

Care to share that 1080p kernel? I wanna test it on my mk908ii. neomode 19a is one of the only roms that don't blink, but i can't seem to get fluid video out of it.

[Pet2001]

Ok, thanks for your answer.

In last days I've been with Neo 1.7 and sam kernel in order to get overclock (i had to plug the dongle directly to monitor and set the scaling to performance in order to avoid screen blinks), but I would prefer to use Neo 1.9a, which was running very fine with kernel3 on my device (i suppose it is different from yours) before.
After reading some posts through the forum I was thinking that Neo1.9a would not allow to have overclocking on RK3188-T, but now you encouraged me.

As soon as I'll get some spare time, I'll try to patch and overclock kernel3 and report here.

[Pet2001]

I patched kernel3 of Neo 1.9a with overclockomatic, but I ended with no overclock at all (cpu runs at 1,4GHz max).
Moreover, in dmesg I found:

...
<4>[ 0.743050] cpufreq: delete arm freq(1608000)
<4>[ 0.743084] cpufreq: delete arm freq(1800000)
...

which with no doubts indicates that kernel3 was compiled with the limitation patch for T-models.
This means that there is no hope to get oc to work on RK3188-T devices by using the kernels delivered with this rom, and I've to look for another kernel which both allows for overclocking T-models and which runs on neo 1.9a (and supports all drivers I need).

...but if you, tobr, succeded in getting oc on basic kernel from neomode 1.9a 720p, then it also means that your device is a true RK3188! ;-)

[HighRise]

Could one of you guys, (Tobe or Pet2001) or anyone really help me out with this quick question?
I'm new and using the Rkloader that came with this and I hit erase and it erases IDB successfully, but when I hit run, it fails to find image. I have the 3 folders it comes with in an Android folder, so when I run the RkDevoper tool it fails. Am i supposed to take the image out of the RockDev folder and put it in the Developer folder? Trying to figure out why it's failing when I hit run but erases IDB fine.
Thanks for any input guys!

[Pet2001]

Could one of you guys, (Tobe or Pet2001) or anyone really help me out with this quick question?
I'm new and using the Rkloader that came with this and I hit erase and it erases IDB successfully, but when I hit run, it fails to find image. I have the 3 folders it comes with in an Android folder, so when I run the RkDevoper tool it fails. Am i supposed to take the image out of the RockDev folder and put it in the Developer folder? Trying to figure out why it's failing when I hit run but erases IDB fine.
Thanks for any input guys!

When you unpack the rom you should have three folders (Driver, RKDevelopTool_v1.37, rockdev) on the same directory. Then you have just to walk into the folder RKDevelopTool_v1.37 and run the RKAndroidTool.exe
All should go fine because the paths to the rom images are already set into the conf file.

However, which error do you get, exactly?

[vihru]

I patched kernel3 of Neo 1.9a with overclockomatic, but I ended with no overclock at all (cpu runs at 1,4GHz max).
Moreover, in dmesg I found:

...
<4>[ 0.743050] cpufreq: delete arm freq(1608000)
<4>[ 0.743084] cpufreq: delete arm freq(1800000)
...

which with no doubts indicates that kernel3 was compiled with the limitation patch for T-models.
This means that there is no hope to get oc to work on RK3188-T devices by using the kernels delivered with this rom, and I've to look for another kernel which both allows for overclocking T-models and which runs on neo 1.9a (and supports all drivers I need).

...but if you, tobr, succeded in getting oc on basic kernel from neomode 1.9a 720p, then it also means that your device is a true RK3188! ;-)

Can you share that kernel that will work rk3188-T and 1.9a? Mk802iv model? Or do you know some?

[HighRise]

When you unpack the rom you should have three folders (Driver, RKDevelopTool_v1.37, rockdev) on the same directory. Then you have just to walk into the folder RKDevelopTool_v1.37 and run the RKAndroidTool.exe
All should go fine because the paths to the rom images are already set into the conf file.

However, which error do you get, exactly?

Error I get is "Error download IDB faild"

Thanks for the reply this been driving me nuts!

[Pet2001]

Error I get is "Error download IDB faild"

Thanks for the reply this been driving me nuts!

This is not connected with the images paths. Rather, it means that the IDB was erased but the operation of downloading a new one was not completed.
Sometimes this error happens when the usb cable you are using is not of good quality.
I would try to change it with a better (shorter?) one and repeat the procedure.

[Pet2001]

Can you share that kernel that will work rk3188-T and 1.9a? Mk802iv model? Or do you know some?

I really would like I'd just found one!
Still searching...

Edit: if you are not interested in overclocking, kernel3 coming with neo 1.9 works good for my MK809III (images here) which mounts a RK3188-T

[HighRise]

This is not connected with the images paths. Rather, it means that the IDB was erased but the operation of downloading a new one was not completed.
Sometimes this error happens when the usb cable you are using is not of good quality.
I would try to change it with a better (shorter?) one and repeat the procedure.

Tried new cable, same result. Is there anything else that can cause this? If it uses image from rockdev folder what location should this folder be in? I even tried different pc. I would welcome you to teamview in my pc if you would like as well... thanks.

[Pet2001]

Tried new cable, same result. Is there anything else that can cause this? If it uses image from rockdev folder what location should this folder be in? I even tried different pc. I would welcome you to teamview in my pc if you would like as well... thanks.

"rockdev" folder must be in the same folder (level) of "RKDevelopTool_v1.37" folder. But it seems to me that your problem is not connected with it.
Try to flash the stock rom for your device (differently from custom rom, it should be in the form of a large, single .img file) with RKBatchTool 1.6, and then try again to flash your wanted custom rom.
Again, I would also try another cable.. and I would never invite an unknown person to teamview my pc! ;-).

Be patient, but now I must break and go to sleep.

[tobr]

Care to share that 1080p kernel? I wanna test it on my mk908ii. neomode 19a is one of the only roms that don't blink, but i can't seem to get fluid video out of it.

I already have done it. See post #199 (and #188) here http://www.freaktab.com/showthread.p...l=1#post138787
It's the version with stock GPU freq, but 800MHz is working fine for me. I think you can again apply rkpatchomatic (phjanderson) for different frequencies.
It's kernel from stock Cloudnetgo rom for their CR11S 5MP you can find the firmware somewhere if one overclocked kernel is not suitable.
p.s. In fact now I use basic 720p kernel from neomode 1.9a because my mk902 is on it's place and my panasonic plasma is only 720p so that no need to have 1080p rom at the moment. cpu:1.7, gpu:800, ddr:667. Antutu 720p 20200.
But before on my 1080p tv I used this combo.

[deeps452]

Root file manager SU

First - thanks to all for your great efforts...

Running this ROM on MK802IV latest version. Everything works fine, except two things:

SU:

I need to change the file libmedia.so in /system/lib to a patched one. But SU doesn't work as I expected. I am not allowed to change any permission with Root File Manager, even though it's been granted rights with SU app.

Any remarks in this?

Sound settings:

Settings are forgotten on reboot.

Again - any comments to this?

Thanks in advance...

[neomode]

AW: NEOMODE CUSTOM ROM MK809III AP6210 Version 1.9a *UPDATE*

Please upgrade to Version 2.1 Beta.

Neomode

Gesendet von meinem GT-I9305 mit Tapatalk 2