Where are you stuck? There is a fully functional CM 12.1 tree made by jianminglok on GitHub for example so maybe you can use some parts of it for 13.
Now i'm using cm12.1, and i'm not a developer so i don't know how to build it. So if u can or u know someone can, can u build it for us. Many user now are report about they need cm13. If u can we will respect to u or give some donations��
And sorry about my bad english��
It is totally fine that you ask but you have to remember that this is a forum of enthusiasts and idealists. Most of us don't do it for the money but because we want to enhance our own devices. I do not own the device so I won't develop for it. There's a good starting guide on CM's wiki if you want to start doing it though! Also please note that this thread is for development discussions.
I'm new to MTK kernel building, and after generating the code using mediatek/dct, I get the following errors when linking vmlinux:
LD vmlinux mediatek/custom/out/s6000_row_3gdata/kernel/built-in.o: In function `lcm_suspend': /home/george/Android/CyanogenMod/kernel/lenovo/s6/mediatek/custom/out/s6000_row_3gdata/kernel/lcm/bp101wx1_n.c:604: undefined reference to `mtkfb_led_off_ms_delay' mediatek/custom/out/s6000_row_3gdata/kernel/built-in.o: In function `lcm_resume': /home/george/Android/CyanogenMod/kernel/lenovo/s6/mediatek/custom/out/s6000_row_3gdata/kernel/lcm/bp101wx1_n.c:669: undefined reference to `mtkfb_led_on_ms_delay' Makefile:946: recipe for target 'vmlinux' failed make: *** [vmlinux] Error 1
Has anyone experienced this before? Any suggestions? Thanks in advance.
#define MTK_FB_LED_ON_DELAY_MS 200 // lcm_resume()
I forked my device (mt8127) from a generic 6582 on GitHub, and I've noticed several roms around for that chip. If there's not anything built for your device "specifically", you can probably try to port something (there's guides for that around here too)
MTK8127? That is what I have been hoping for (and so have lots of others here in Lenovo-land), as that is the MTK SoC on the Tab 2 F series with the hyper-unreliable stock and 3e recoveries (especially the A7-30F, like mine). For me personally, it stings particularly hard, as I got my Mom's VZW GNex (she bought it super-cheap on Amazon two years back; the only issue was the old/slow JellyBean VZW and Samsung hung them out to dry with) running on the unofficial CM for GNex - found right here @ XDA).
I have three questions -first, what are you using for a recovery? (I haven't been able to get ANY recovery to work reliably - and I'm including stock.)
Second, do you still have the link to the porting guides you used?
Lastly, what did you use for source (if not straight AOSP)?
That's rather odd, considering that Lenovo dropped them in the last OTA for 5.0.1 (S000117); that was, in fact, the biggest visual change from S000116, which brought Lollipop itself. So it's not all of MediaTek's OEMs.Mediatek still uses the Jelly Bean icons in Marshmallow? Jeeeeeeeeeez...
Hey guys, We are going to try something new for our china phones - cyanogenmod.
But we need some more devs to get everything going.
For now we have:
-Github tree for Lenovo P700i(mediatek 6577, android 4.0.4, kernel 3.0.8)
-Lens_flare - original port author(may work with system folder and configs)
-some kernel source from other devices like liquid gallant
The main problem is getting adb to work that could help a lot on remaining development. For now even zygote not starting, but all partitions seems mounted successfully.
We need more devs (especially that could assemble working kernel for device), working with p700i may lead to following porting for other mtk devices, as sources are nearly the same.