Kitkat Kernels for All (well most!)

[d33]

DMESG + GPIO dump on NCR 3.1 (not NCR MTK 1)

You think we can get it working?

[ATTACH]7298[/ATTACH]

I tested debug10_oc on NCR MTK 1 and it does work, I must have switched to NCR 3.1 when I tested before. Disregard debug10 wifi not work, it does work.

debug11_oc

I've selected 1.8V Lcdc as someone once said that helped stop flickering.

[m4f1050]

debug11_oc

I've selected 1.8V Lcdc as someone once said that helped stop flickering.

Testing. Is this for NCR MTK 1 or should I try NCR 3.1?

[d33]

Testing. Is this for NCR MTK 1 or should I try NCR 3.1?

I don't know the difference

Whichever you want I guess. Originally you said WiFi only works on MTK1.

[m4f1050]

I don't know the difference

Whichever you want I guess. Originally you said WiFi only works on MTK1.

That's correct. I'm playing a movie now to try to gather some logging so far I havent had any flickering. Maybe it's TV related? I have a Vizio 3D 65" and I have never experienced these "flickers" or lines people complain about... Something should show up in logs if its wrong I assume.

Giving it about 5 more mins, will post DMESG + GPIO dump (if you still need GPIO dump)

debug11.txt

NOTE: On my test TV (Sceptre 40") at 1080p I get the flickers and lines (just about anywhere, not just playing movies but I did not get any sound problems and the flickers/lines are barely noticeable while playing a movie - you really have to watch closely and on dark scenes) but not on my other TV's last night I watched 2 full movies with 0 issues.

[Benobi]

NCR 3.1 is Android 4.2 i think.
NCR_MTK1 is KitKat ...

[m4f1050]

NCR 3.1 is Android 4.2 i think.
NCR_MTK1 is KitKat ...

NCR 1.3 is 4.2, NCR 3.1 is KK. But these kernels do not have wifi working on any ROM except NCR MTK .9 or 1

[Benobi]

To clear all . ..

I use firmware from first post:

http://www.freaktab.com/showthread.php?14028-Neomode-Custom-Rom-MK809III-MTK-WiFi-Version-0-9

and just change kernels.

Thats KitKat.

[m4f1050]

To clear all . ..

I use firmware from first post:

http://www.freaktab.com/showthread.php?14028-Neomode-Custom-Rom-MK809III-MTK-WiFi-Version-0-9

and just change kernels.

Thats KitKat.

Yes, that one is KitKat. So is NCR 3.1 ( http://www.freaktab.com/showthread.p...4-4-2-*Update* ) but Wifi doens't work on NCR 3.1

d33, did you notice this?

<4>[    2.362168] mt6622_probe.
<4>[    2.362196] mt6622 power_gpio is busy!
<6>[    2.362234] [MT6622] mt_bt_power_init

Maybe it has something to do with BT not working? I posted GPIO from working 720p kernel on earlier posts, could you find any clues how to get BT working?

[nagper]

Thanks for the deatiled explanation!!

If I am getting you right you are keen to make a dedicated kernel for just me and the others would like native 1366x768? That would be perfect
Is it correct that issuing "wm size 1366x768" from a terminal inside android sets the desktop resolution? If it is, we just need your dedicated kernel to put our Tv-s to 1366x768.

Thank in advance.

So can we expect a dedicated kernel for our 1366x768 displays anytime soon? MK908II works without problems so nothing else needs to be fixed.

Thank you

[m4f1050]

Here is a DMESG + GPIO on stock 720p MTK 1 (I turned BT on and off a few times, renamed the device and turned it off)

stock_mtk1_bt_test.txt

This DMESG + GPIO is after turning it back on

gpio.txt

I did notice on stock 720p there is no gpio busy message on BT...

<6>[    0.514916] Bluetooth: Core ver 2.16
<6>[    0.514993] NET: Registered protocol family 31
<6>[    0.515033] Bluetooth: HCI device and connection manager initialized
<6>[    0.515090] Bluetooth: HCI socket layer initialized
<6>[    0.515139] Bluetooth: L2CAP socket layer initialized
<6>[    0.515201] Bluetooth: SCO socket layer initialized
<4>[    0.516322] rk fb probe ok!
<4>[    0.521154] act8846_set_init,line=17
<4>[    0.521190] act8846_set_init:g_pmic_type=3
<4>[    0.522898] act8846_set_init  act_dcdc1 =1200000mV end
<4>[    0.524698] act8846_set_init  vdd_core =1000000mV end
<4>[    0.526491] act8846_set_init  vdd_cpu =1000000mV end
<4>[    0.528288] act8846_set_init  act_dcdc4 =3300000mV end
<4>[    0.529482] act8846_set_init  act_ldo1 =1000000mV end
<4>[    0.531173] act8846_set_init  act_ldo2 =1200000mV end
<4>[    0.532862] act8846_set_init  act_ldo3 =1800000mV end
<4>[    0.534554] act8846_set_init  act_ldo4 =3300000mV end
<4>[    0.536245] act8846_set_init  act_ldo5 =3300000mV end
<4>[    0.537938] act8846_set_init  act_ldo6 =3300000mV end
<4>[    0.539030] act8846_set_init  act_ldo7 =1800000mV end
<4>[    0.540719] act8846_set_init  act_ldo8 =2800000mV end
<4>[    0.540770] act8846_set_init,line=78 END
<4>[    0.540805] The PMU device is act8846 
<4>[    0.540875] i2c-core: driver [act8846] using legacy suspend method
<4>[    0.540927] i2c-core: driver [act8846] using legacy resume method
<6>[    0.541004] Switching to clocksource rk_timer
<6>[    0.547323] Switched to NOHz mode on CPU #0
<6>[    0.547971] Switched to NOHz mode on CPU #3
<6>[    0.548003] Switched to NOHz mode on CPU #2
<6>[    0.548018] Switched to NOHz mode on CPU #1
<4>[    0.550337] lcdc1:reg_phy_base = 0x1010e000,reg_vir_base:0xdf0ac000
<4>[    0.550437] fb0:win0
<4>[    0.550443] fb1:win1
<4>[    0.550448] fb2:win2
<4>[    0.550549] rk3188 lcdc1 clk enable...
<4>[    0.575672] rk3188 lcdc1 clk disable...
<4>[    0.611490] fb0:phy:97d00000>>vir:e0000000>>len:0xb00000
<4>[    0.611799] rk_fb_register>>>>>fb0
<4>[    0.612163] rk_fb_register>>>>>fb1
<4>[    0.626876] rk3188 lcdc1 probe ok!
<6>[    0.688110] IT66121 probe success.
<3>[    0.689342] emmc emmc: internal_storage is NOT emmc
<6>[    0.689546] NET: Registered protocol family 2
<6>[    0.689697] IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>[    0.690069] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
<6>[    0.691126] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
<6>[    0.692259] TCP: Hash tables configured (established 65536 bind 65536)
<6>[    0.692314] TCP reno registered
<6>[    0.692350] UDP hash table entries: 256 (order: 1, 8192 bytes)
<6>[    0.692413] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
<6>[    0.692755] NET: Registered protocol family 1
<6>[    0.692975] Unpacking initramfs...
<6>[    0.763293] Freeing initrd memory: 1344K
<6>[    0.763422] PMU: registered new PMU device of type 0
<4>[    0.763557] efuse_version_val: efuse version = 51
<4>[    0.763602] DVFS MSG: core: dvfs_adjust_table_lmtvolt get leakage_level = 5000
<4>[    0.763663] efuse_version_val: efuse version = 51
<4>[    0.763704] DVFS MSG: aclk_gpu: dvfs_adjust_table_lmtvolt get leakage_level = 5000
<4>[    0.764917] rk3188 cpufreq version 2.2, suspend freq 816 MHz
<4>[    0.765250] vpu: power on
<6>[    0.765323] VPU_SERVICE: checking hw id 4831
<4>[    0.765860] vpu: power off...done
<6>[    0.765919] VPU_SERVICE: init success
<6>[    0.766288] audit: initializing netlink socket (disabled)
<5>[    0.766367] type=2000 audit(0.700:1): initialized
<4>[    0.767057] highmem bounce pool size: 64 pages
<6>[    0.767238] ashmem: initialized
<6>[    0.773555] fuse init (API version 7.16)
<7>[    0.773889] SELinux:  Registering netfilter hooks
<6>[    0.775413] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
<6>[    0.775480] io scheduler noop registered
<6>[    0.775516] io scheduler deadline registered
<6>[    0.775605] io scheduler cfq registered (default)
<6>[    0.783537] rga: Driver loaded succesfully
<4>[    0.783812] rk_serial.c v1.6 2013-12-23
<6>[    0.784145] rk_serial rk_serial.0: dma_rx_buffer 0xffdfc000
<6>[    0.784194] rk_serial rk_serial.0: dma_rx_phy 0x7d0b4000
<6>[    0.784248] rk_serial rk_serial.0: serial_rk_init_dma_rx sucess
<6>[    0.784304] rk_serial.0: ttyS0 at MMIO 0x10124000 (irq = 66) is a rk29_serial.0
<6>[    0.784506] rk_serial rk_serial.0: membase 0xdf0c4000
<6>[    0.784637] rk_serial.3: ttyS3 at MMIO 0x20068000 (irq = 69) is a rk29_serial.3
<6>[    0.784817] rk_serial rk_serial.3: membase 0xdf0c8000
<6>[    0.785169] Rockchip ion module(version: 1.0) is successfully loaded
<6>[    0.788186] loop: module loaded
<6>[    0.788255] Android kernel panic handler initialized (bind=kpanic)
<4>[    0.788340] mt6622_probe.
<6>[    0.788368] [BT-PLAT] mt_bt_power_init
<4>[    0.919753] ******** Show Sink Info ********
<4>[    0.919785] Support video mode: 
<4>[    0.919808]     1920x1080p@60Hz.
<4>[    0.919829]     1920x1080p@50Hz.
<4>[    0.919849]     1280x720p@60Hz.
<4>[    0.919869]     1280x720p@50Hz.
<4>[    0.919890]     720x576p@50Hz.
<4>[    0.919909]     720x480p@60Hz.
<4>[    0.919928] Support audio type: LPCM

EDIT: This is debug11 turning on and off bt a few times (not working of course)

DMESG + GPIO

debug11_bt_test.txt

Notice the gpio busy on debug11

<4>[    2.361862] mt6622_probe.
<4>[    2.361889] mt6622 power_gpio is busy!
<6>[    2.361927] [MT6622] mt_bt_power_init

Stock:

<4>[  880.868798] GPIO gpio3 278 BT_EINT
<4>[  880.868818] GPIO gpio3 279 BT_PWR_EN
<4>[  880.868844] GPIO gpio3 280 wifi_power
<4>[  880.868881] GPIO gpio3 281 wifi reset
<4>[  880.868913] GPIO gpio3 282 (null)

debug11:

<4>[  135.244195] GPIO gpio3 278 (null)
<4>[  135.244200] GPIO gpio3 279 (null)
<4>[  135.244206] GPIO gpio3 280 wifi_power
<4>[  135.244212] GPIO gpio3 281 wifi reset
<4>[  135.244218] GPIO gpio3 282 BT_EINT

[m4f1050]

*** d33 please read last post on page 74!


Can someone else with Mediatek help out? I have to get ready for work... Or I can't afford to buy these magnificent toys

If you want to add GPIO dump to DMESG, use this:

gpio_rk3188_kernel_3.0.36+.zip

On a terminal, after decompressing files to sdcard, do this:

su
mount -o rw,remount /system
cp /mnt/external_sd/user-gpio-drv.ko /system/lib/modules/
cp /mnt/external_sd/gpio /system/bin/
chmod 777 /system/bin/gpio

When you're ready to add GPIO dump to DMESG do this on terminal:

su
insmod /system/lib/modules/user-gpio-drv.ko
gpio dump gpio
dmesg > /mnt/external_sd/filename_of_dmesg.txt

this will attach the GPIO dump on DMESG.
Thanks!!!

[d33]

Actually if you follow this thread it tells you how to discover the GPIOs by a combination of switching off/on

[d33]

So can we expect a dedicated kernel for our 1366x768 displays anytime soon? MK908II works without problems so nothing else needs to be fixed.

Thank you

try this

Is a MK908 a box or a stick?

[Benobi]

Actually if you follow this thread it tells you how to discover the GPIOs by a combination of switching off/on

Hi,

I will do that today.
Will send debug11 dmesg today later.

[d33]

Hi,

I will do that today.
Will send debug11 dmesg today later.

GPIO dump from stock: Thanks
DMESG debug11: Not needed - it is for flickering only