Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Kit Kat 4.4.2 RK3066 (Fully Working)

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Akure
    replied
    MK808B with MTK chipset

    Rom works well pairs with Bluetooth mouse and keyboard but does not work, RKRemoteControl FAILS TO DETECT STICK eHomeMediaCenter is working, I did not flash OC CWM file unavailabe for download. What do i need to do to fix these issues MY STICK MK808B with MTK chipset

    Leave a comment:


  • tonyk3
    replied
    Hello

    I've installed this & looking great! But I'm also trying to get my 20" touchscreen overlay working:

    touchscreen model 03fc:05d8
    and I've got this ko from the manufacturer: https://drive.google.com/file/d/0B3Q...ew?usp=sharing

    I've tried using an idc to load the ko - it changed the touch but still wasn't working (all I get is a single touch registered wherever the mouse already is, not where I touch).

    Sorry, I don't know enough about this, what should I do??

    Thanks

    Tony

    Leave a comment:


  • KRWiFi
    replied
    Hello.

    I have Imito MX1 and i would like to map/mount network drive (WD My Cloud) to expand memory. Is there any way to do this. Cifs manager doesn't work.

    regards

    Leave a comment:


  • fr4nc3sc0
    replied
    Hello, can anyone give me the zip file (4.4.2) to be loaded via CWM? Or cyanogenmod?
    I've a mk802III (8g) with rk3066

    Leave a comment:


  • doz
    replied
    Could anyone reupled the cwm-flashable OC kernel? The link in the first post is deleted.
    Thanks

    Leave a comment:


  • dirtytuga
    replied
    Hi.
    Please confirm (or not) if this rom is also for MK808 (without B).
    Thank you

    Leave a comment:


  • sam tyler
    replied
    i may have come across an answer to ramdom reboots,black outs and Lock ups with this rom.this is not a cure, all but it worked on my mk809ii(with this rom installed)what i did was to install no-frills cpu control from playstore,(hopefully you have rooted this rom)and i checked the max.clock freq,and it was set to 1.512ghz. i took it down to 1.272ghz,(i didn`t touch the min.clock freq) and i also set the governer to performance.(it was set to interactive)i pressed apply and rebooted the device.the only problem i find as the rom does not have a power off setting,just a standby or reboot setting.so if you leave the device on standby,the no-frills cpu controls you set will stay,but if you turn off the device,you may have to re apply the settings.im also using a reboot apk from a finlessbob rom(4.2.) to turn the device off, and as i said,if you do that you will have to re apply the settings in no-frills cpu.but so far so good,the device has been on for over six hours using xbmc,watching films and using a usb memory stick via a usb powered hub,and ive had no reboots,blackouts etc.as i said,this may not work other devices,its working on mine.hope this helps other people out,as i do like this rom,(except for the reboots! ) and yes my device does get hot but not as it did before,again,i hope this helps,and dont blame me if your device goes pop!

    Leave a comment:


  • davidw
    replied
    Originally posted by Shomari View Post
    This ROM carries with it a minor HDMI audio bug persistent in KitKat update.

    HDMI doesn't send audio to the TV when device is resumed from standby.

    To solve the issue, always resume device from standby before powering on TV. Turn device on, then turn TV on.

    The audio issue is caused by Rockchip's KitKat audio kernel configuration. The device expects a specific response from the HDMI sink, if it isn't found it effectively mutes the HDMI audio by treating the device as a DVI interface. 'rk30-hdmi: warning: EDID error, assume sink as DVI'
    I just have to ask since this seems so related to my troubles on the Neo X5 (on both this and Finless 1.3). I find when I turn on my HDTV, it can often crash the machine. Lots of research shows the machine enters some kind of loop putting output on the kernel log but is effectively dead and has to be powered off. I have seen this sometimes in the kernel log:

    Code:
    [  431.776475] lcdc1: dclk:74250000>>fps:60 rk30_load_screen for lcdc1 ok!
    [  431.783143] rk30 lcdc1 clk enable...
    [  431.786737] lcdc1: dclk:74250000>>fps:60 rk30_load_screen for lcdc1 ok!
    [  431.793394] lcdc1 wakeup from standby!
    [  431.797168] lcdc1 win1 open,atv layer:2
    [  432.111393] rk30-hdmi rk30-hdmi: Removed.
    [  432.115435] no layer of lcdc1 is used,go to standby!
    [  432.120420] rk30 lcdc1 clk disable...
    [  432.124096] lcdc1 win1 closed,atv layer:0
    [  432.142390] [EDID] check header error
    [  432.146512] rk30-hdmi rk30-hdmi: [HDMI] parse edid base block error
    [  432.152820] rk30-hdmi rk30-hdmi: warning: EDID error, assume sink as HDMI !!!!
    [  432.159891] rk30-hdmi rk30-hdmi: warning: no CEA video mode parsed from EDID !!!!
    ******** Show Sink Info ********
    [  432.171232] Support video mode: 
    [  432.174503]  1920x1080p@60Hz.
    [  432.177503]  1920x1080p@50Hz.
    [  432.180497]  1920x1080p@30Hz.
    [  432.183483]  1920x1080p@25Hz.
    [  432.186464]  1920x1080p@24Hz.
    [  432.189441]  1280x720p@60Hz.
    [  432.192345]  1280x720p@50Hz.
    [  432.195452]  720x576p@50Hz.
    [  432.198272]  720x480p@60Hz.
    [  432.201077] ******** Show Sink Info ********
    [  432.205408] lcdc1: dclk:74250000>>fps:60 rk30_load_screen for lcdc1 ok!
    [  432.212099] rk30 lcdc1 clk enable...
    [  432.215809] lcdc1: dclk:74250000>>fps:60 rk30_load_screen for lcdc1 ok!
    [  432.222502] lcdc1 wakeup from standby!
    [  432.226285] lcdc1 win1 open,atv layer:2
    Similar to but not quite what you mention. And not shown at the time of the crash (see below for that).

    I have my Neo X5 connected to other HDTV and this seems to happen only on mine and only after the Neo has been sitting for a long time (many hours) with the TV off. I have tried using the Android Developer option to prevent the device going into standby. But I am not sure this is enough since I do see references to return to and wakeup from standby for the lcdc1 in the log info.

    Here is what is shown at the time of the crash:

    Code:
    [35102.147945] ******** Show Sink Info ********
    [35102.148041] Support video mode: 
    [35102.148099]  1920x1080p@60Hz.
    [35102.148168]  1280x720p@60Hz.
    [35102.148215]  720x480p@60Hz.
    [35102.148259] Support audio type: LPCM
    [35102.148319] Support audio sample rate: 
    [35102.148373]  32000
    [35102.148420]  44100
    [35102.148453]  48000
    [35102.148486]  96000
    [35102.148526]  192000
    [35102.148561] Support audio word lenght: 
    [35102.148614]  16bit
    [35102.148654]  20bit
    [35102.148693]  24bit
    [35102.148728] Support audio type: AC3
    [35102.148785] Support audio sample rate: 
    [35102.148839]  32000
    [35102.148871]  44100
    [35102.148911]  48000
    [35102.148945] Support audio word lenght: 
    [35102.149004]  16bit
    [35102.149045]  20bit
    [35102.149078]  24bit
    [35102.149111] ******** Show Sink Info ********
    [35102.149213] lcdc0: dclk:148500000>>fps:60 rk30_load_screen for lcdc0 ok!
    [35102.149342] rk30 lcdc0 clk enable...
    [35102.149423] lcdc0: dclk:148500000>>fps:60 rk30_load_screen for lcdc0 ok!
    [35102.149531] lcdc0 wakeup from standby!
    [35102.149594] lcdc0 win1 open,atv layer:2
    [35102.149679] lcdc0 win0 closed,atv layer:2
    [35102.149757] lcdc0 win2 closed,atv layer:2
    And then it loops printing dump information on the log.

    This is a real pain and I am not sure how to deal with it. If you can provide any more details on this bug maybe I can find out more about my problem. Or maybe I can find a way to prevent the device going into standby.

    Thanks for any tips.

    Leave a comment:


  • sam tyler
    replied
    http://www.freaktab.com/showthread.p...-UG007II-Stick I use this one now.and I no longer get power issues or frozen screen problems. and I still use my normal charger.

    Leave a comment:


  • chsmith1976
    replied
    Originally posted by uniextra View Post
    I agree, i had to work extra to get this working.

    for me a step by step wuld be:

    1- Download Links
    a- ROM https://mega.co.nz/#!6cJkWDDY!-VT74e...kqkTYcjPm_KVn4
    b- Batch tool https://mega.co.nz/#!fJgADI6S!RBael7...XKqKSv_U903xGA

    2- Disconect your device from Anything HDMI air remote etc.

    3- Hitting reset button conect your device OTG micro USB to your machine and install drivers (Win8 allow unsigned drivers)

    4- Open Batch tool and you will see your device recogniced as MaskROM

    5- On batch tool, under "Upgrade firmware" select "firmware" (download A) and then hit Erasa Flash and after "Upgrade"

    6- Now device should be flashed and able to boot and Android 4.4.2

    7- Time to download CWM
    https://mega.co.nz/#!zNpiSTZB!DIy4BRWSmq29bJU66sSXvuPBxN3H-aHVlfLfglAWA8I

    8- select (OMA / CrewRKTablets) CWM Recovery 6.0.3.1 for Android 4.4.2 KitKat on RK tablets (loader Gen2) in packages. Download and install, reboot. You must select the Oma package for full CWM compatibility.

    9- Now i recomend installing the last Google Apps to be able to go ART http://forum.xda-developers.com/showthread.php?t=2397942 install by CWM with a keyboard connected using arrows to move


    well this is out of my memorey, i flashed a couple weeks ago.. so i might be missing something... i would be nice if someone pastes this on the first page and correct if any error!

    Awesome, thanks for the write-up. I managed to get this ROM installed, using slightly different steps as I ran into a couple of additional issues which I'll try to give resolution links to below.

    - Rockchip USB drivers (mine were totally messed up), so go to the link below and install the autoinstaller from the bottom of the page - worked like a dream. I would make this point 1. c.

    1. c. Rockchip USB Driver AutoInstaller
    Download Windows drivers & Android tools voor Rockchip RK3188, RK3066, RK2918. Firmware upgrade, CPUset tool, overclocken. Win 8, win 7, win XP, win 2K


    - Hitting reset button - Cozyswan 809ii has a reset button, but don't bother trying to poke a needle through the hole in the side of the case - IT DOESN'T GO ANYWHERE. To access the reset button, you actually have to pop open the case and you will find it on the pcb, but not where the case hole is!

    Question - are there any versions of TWRP that work on this build (4.4.2)?

    Persistent Issues:

    1. After installing the ROM, I find that rebooting only works correctly about 20% of the time. 80% of the time the ROM gets stuck in the moving circles screen and have to pull power repeatedly until it boots. After about 20 reboots, I've had all apps lose their settings twice now - good thing for TB backups! I will try a better power adapter, but so far, after using a high quality power adapter from my HP Touchpad, still no luck.

    2. Noticed quite a bit of tearing near the bottom of the screen in MX Player. Seems to happen on just about any file I play (locally and across the network (wired connection)).

    Other than that, the ROM is actually quite nice.
    Last edited by chsmith1976; 11-10-2014, 03:27.

    Leave a comment:


  • qepaxhiu
    replied
    why i get this error on mk809II when i press upgrade

    Leave a comment:


  • ultimatexbmc
    replied
    Originally posted by sam tyler View Post
    Bought that charger,but the charger was dead.maybe because there's no guts inside it? thanks for the link.and my own fault for using **** cheers.

    Really sorry to hear that, I just found you the cheapest link to that charger on ****, but I have 3 of them all working and they are all made by Belkin.

    Leave a comment:


  • sam tyler
    replied
    Originally posted by ultimatexbmc View Post
    We have never had a problem using these on any Android device that is USB powered and I have been running my MK809II on this PSU for over 12 months with no issue.

    http://www.****.co.uk/itm/Belkin-Uni...item19ebaa616e
    Bought that charger,but the charger was dead.maybe because there's no guts inside it? thanks for the link.and my own fault for using **** cheers.

    Leave a comment:


  • r0ottm
    replied
    Could anyone reupled the cwm-flashable OC kernel? The link in the first post is deleted.
    Thanks

    Leave a comment:


  • sam tyler
    replied
    Originally posted by aldinezi View Post
    For me.. sometimes it last for few hours sometimes faster if I run some heavy apps/games. I was using USB port of my TV, and then switched it to a nearby router USB port.. I guess I have to find a right adaptor. I have also tried lowering the top limit for CPU freq at ~800 MHz... but it did not helped. It happens with the stock and with the 4pda ROM.

    EDIT: After trying a brand new adapter with 3A and 5V, I got the same issue. Screen just freezes, stucks.. and it looks a little bit pixelated.

    Any info regarding this problem, or solutions would be really appreciated? Thank you.
    I'm still waiting for my charger/adaptor to turn up but I think its to do when standby is selected or something with the power off button. and mine has a heatsink(which i fitted)on it,and its still turning off. so I think its not a power issue.maybe someone who can read and understand the prop build and kernel etc might know the answer,also I find after some research that this is a 'beta' build,so maybe we should expect some issues. but I yet to find an update for this.

    Leave a comment:

Working...
X