[DEV][ROM][24.4.] CyanogenMod 12.1 (Android 5.1.1) for ZTE Open C / Kis 3

[Guest KonstaT]

Here's an early taste of Lollipop for ZTE Open C / Kis 3 (Beeline Smart2, Moche/MEO Smart A16, ZTE V811W, ZTE V811, Skinny V811, Optus Hop Smart, ZTE Blade M, etc). It is unofficial and unsupported by the CyanogenMod team. It's for advanced users only.

 

Important. Prerequisites!!! You need to install Android KitKat on your Open C first (e.g. EU_FFOS+to+Android.zip will do). You also need to have this ClockWorkMod or this TWRP recovery installed.

 

  

 

Do not mirror my builds! Please post a link to this page instead.

 

cm-12.1-20160424-UNOFFICIAL-KonstaKANG-kis3.zip
http://konstakang.com/devices/kis3/CM12.1
md5:672fe805309a73004cac796c79d9e24e

 

Google apps:

Google Apps - CyanogenMod

TK GApps - tk_gapps-modular-pico-5.1.1-2015xxxx-signed.zip recommended

 

Working:

• RIL (mobile network, SMS & data)
• Wifi
• Audio (playback/input/routing/headphones/etc)
• Bluetooth
• Camera (photos, camcorder & panorama)
• FM radio
• GPS
• Hardware acceleration and OpenGL rendering
• Hardware video decoding & encoding
• SD card
• USB-storage (on external sdcard) & adb
• USB-tethering
• Wifi-tethering
• Touchscreen/multi-touch
• Sensors
• LEDs

Not working:

• ???

Issues:

• dual-SIM (V811W) not supported

 

Important!!! If you’re using my open sourced work as a part of your project, be fair and give proper credits, and contribute back by keeping your project open source as well. I've put countless hours of my spare time into this project and I deserve at least this (I'm not getting paid to do this). Free and open source doesn't mean without respect!

 

Sources:

• Device
• Kernel
• Proprietaries

Thanks:

• CyanogenMod team & everyone who's been working on CM12.1

Like my work?

Edited November 10, 2018 by KonstaT

[Guest KonstaT]

Merged commits not mentioned in the changelog.

 

24.4. 2016 changelog:

• add proximity wake gesture on supported devices
• patch known vulnerabilities in kernel (CVE-2015-5697, CVE-2015-7872, CVE-2015-8539, CVE-2015-8215, CVE-2015-8543, CVE-2015-8575, CVE-2015-7550, CVE-2016-0723, CVE-2015-1805, CVE-2016-0821, CVE-2015-8785, CVE-2015-7509, CVE-2016-0774)
• Android security patch level: 1 April 2016 (merged)

17.11. changelog:

• patch CVE-2015-8019 and CR-930533 in kernel
• Android security patch level: 1 November 2015 (merged)
• C-Apps compatibility (merged)

9.10. changelog:

• add BFQ i/o scheduler and enable it by default
• Android security patch level: 1 October 2015 (merged)

5.9 changelog:

• add keymaster firmware for encryption
• patch CVE-2015-1534 in kernel
• patch one more stagefright vulnerability (merged)

31.7 changelog:

• more gesture settings translations
• add fiops i/o scheduler
• patch CVE-2015-3339 in kernel
• patch recently disclosed stagefright vulnerabilities (merged)

9.7. changelog:

• revert volume levels back to the original
• update few blobs from recent ZTE stock firmware
• update Adreno blobs
• add translations to gesture settings
• patch CVE-2015-5366 in kernel

4.6. changelog:

• enable ambient display
• add 'hand wave' and 'pocket' gestures to pulse ambient display (only available on devices that have a proximity sensor)
• update sensor HAL
• unhide in-call volume boost option (again)
• minor audio/bluetooth/media updates from CAF upstream

20.5. changelog:

• disable dex2oat watchdog (large apps like Facebook, Play Services, etc can take over allowed 6 mins to dex2oat)
• disable 'Phone number lookup' options by default
• fix duplicate sdcard entries when importing/exporting contacts
• disable panic to download mode in kernel (should now reboot instead of freezing)
• patch CVE-2014-2523 and CVE-2014-9529 in kernel

6.5. changelog:

• increase volume (speaker, handset and headphones)
• updates from new ZTE kernel source release (i.e. Goodix GT960F touchscreen support)
• patch CVE-2015-3636 in kernel
• address some SELinux denials
• LCD density option (merged)

23.4. changelog:

• option to change button backlight brightness
• disable unused kernel logger and reclaim some RAM
• patch CVE-2015-2041 in kernel
• Android 5.1.1 (merged)

17.4. changelog:

• unbreak headset detection (headset with mic and call button is again registered correctly)
• patch CVE-2014-9715 and CVE-2015-2922 in kernel
• tweak auto-brightness levels

2.4. changelog:

• initial CM12.1 release
• decrease zRAM size to 192mb
• enable call recording (available in whitelisted countries where its legal status clear)

 

Previous builds:

cm-12.1-20151117-UNOFFICIAL-KonstaKANG-kis3.zip
http://konstakang.com/devices/kis3/CM12.1
md5:0be2fa18be996376b61370e70fbcc306

cm-12.1-20151009-UNOFFICIAL-KonstaKANG-kis3.zip
http://konstakang.com/devices/kis3/CM12.1
md5:b435cbfa0c67a1bcf36987b4557b6697

cm-12.1-20150905-UNOFFICIAL-KonstaKANG-kis3.zip
http://konstakang.com/devices/kis3/CM12.1
md5:e3b4cfe5f90e7a7ec3b2104b5d45b3f5

Edited January 8, 2017 by KonstaT

[Guest KonstaT]

How to install:

1. boot into ClockWorkMod
2. backup and restore -> backup (create a nandroid backup of your current ROM)
3. mounts and storage -> format /system
4. wipe data and factory reset
5. install cm-12.1-xxxxxxxx-KonstaKANG-kis3.zip
6. install gapps-lp-xxxxxxxx-signed.zip
7. reboot now
8. if/when recovery asks to fix root - choose no

 

FAQ:

 

Q: I can't find developer options and performance settings, why?

A: Settings -> About phone -> Click 'Build number' several times

 

Q: I don't have reboot options in power menu, why?

A: Settings -> Developer options -> Advanced reboot

 

Q: I have no root, why? What is that hashtag on my status bar?

A: Settings -> Developer options -> Root access. Root management is now integrated as part of CM's Privacy Guard and you can manage per app permissions under Settings -> Privacy -> Privacy Guard. You'll have a persistent notification in the status bar when you're running an app that uses root permissions.

 

Q: When I'm connected with an USB cable to my computer, I can't see my internal sdcard as a storage, why?

A: I've made an executive decision not to include a mount point for internal sdcard. This is because recent Android versions don't allow setting emulated sdcard as secondary storage. Setting rather small emulated sdcard as a primary storage caused issues with games/apps that want to download large amounts of data to the sdcard. Also partition layout is different on Open C and Kis 3 and internal sdcard is handled differently between device variants.

 

Q: 'OK Google' voice command doesn't work, why? There's no Google Now page on the homescreen, why?

A: These are features of proprietary Google Now Launcher. 'OK Google' voice command is also disabled on low memory devices (you can enable it by removing/commenting/changing to false 'ro.config.low_ram=true' in /system/build.prop).

 

Q: There's only a home button on an Open C. How is this going to work?

A: There's 'hidden' back and menu keys on left and right side of the home button. There's also an option to use software navigation bar instead of the capacitive keys.

 

Q: There's an option to enable auto-brightness but it doesn't work, why? Proximity sensor doesn't work either...

A: Open C doesn't have ambient light/proximity sensor. Some Kis 3 variants on the other hand do, so that's why I've kept the support.

 

Q: How do I enable dual-SIM features on my V811W?

A: Add 'persist.radio.multisim.config=dsds' to /system/build.prop or optionally 'setprop persist.radio.multisim.config dsds' in rooted adb shell/terminal session.

 

 

How to build:

 

1. Follow instructions on initializing a build environment up to a point of downloading the source code.

2. Initialize CyanogenMod 12.1 repo.

repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1

3. Add local manifest that downloads ZTE Open C / Kis 3 device config, kernel source and proprietary files from my github.

curl --create-dirs -L -o .repo/local_manifests/manifest_zte_kis3.xml -O -L https://raw.github.com/legaCyMod/android_local_manifest/cm-12.1/manifest_zte_kis3.xml

4. Sync source code.

repo sync

5. Apply patches. No patches currently required.

 

6. Compile.

cd path-to/cm12.1/
. build/envsetup.sh
brunch kis3

Use 'repo sync' to pull merged changes from upstream. Use 'make clobber' to clean the build environment. Repeat step 6 to make a new build.

[Guest Nanolx]

I just wanted to thank you for your hard work on this device. This versions feels just as smooth as cm11. That's more than just a minor speed up compared to 5.0. Is 5.1 in general faster or has cm12.1 optimizations for low-end devices?

Only issue so far: battery is draining faster than on previous versions.

Another Question (not on topic): are you planning on getting and supporting the Open L, aswell?

Edited April 2, 2015 by Nanolx

[Guest KonstaT]

I just wanted to thank you for your hard work on this device. This versions feels just as smooth as cm11. That's more than just a minor speed up compared to 5.0. Is 5.1 in general faster or has cm12.1 optimizations for low-end devices?

Only issue so far: battery is draining faster than on previous versions.

Another Question (not on topic): are you planning on getting and supporting the Open L, aswell?

It's just the improvements in Android 5.1 in general (same thing on high-end devices too). CM12.1 currently isn't much more than Android 5.1 merged into CM12 and fixed to build. ;) It's still very early days of CM12.1 - it was branched only few days ago and even the nightlies haven't started yet. I'm sure there's still plenty to be done. CM12 still performs slightly better in benchmarks but CM12.1 is indeed much smoother in real life usage.

 

I don't think you're going to be able to say much about battery life after a couple of hours of usage. ;) I've been running this for few days and I haven't noticed any significant battery drain overnight.

 

I'm not planning on getting an Open L. I'm going to go with something with a next generation Snapdragon next (Snapdragon 410/615 - 64-bit, ARMv8, Cortex-A53/A57). I'm open for suggestion if a device meets the criteria for hackability (unlocked/unlockable bootloader, kernel source available, etc).

[Guest okmikel]

Installed it today and I will test it during the easter holidays. First impression is very good, I also think it is smoother than CM12.

 

If there is anything not working like it was in CM12 I will report.

[Guest debian2]

enable call recording (available in whitelisted countries where its legal status clear) = 2WCR? And, please, give whitelist into this forum.

[Guest KonstaT]

enable call recording (available in whitelisted countries where its legal status clear) = 2WCR? And, please, give whitelist into this forum.

2WCR? Call recording is a built in CyanogenMod feature and it's been there a while but it's not enabled by default because it's illegal in many countries.

http://www.androidpolice.com/2014/08/22/cyanogenmod-adds-call-recording-to-nightlies-but-it-isnt-enabled-by-default/

 

And actually it would be technically more accurate to say it's available in countries that are not blacklisted. :P AFAICT it should be available in Russia (MCC 250) if that's what you're asking. I'm not going to maintain a list of countries.

 

During an on-going call, press options (three dots in the top right corner) and select 'Record call'.

[Guest hemanx]

Can someone be able to port this rom for Canvas Nitro a310?

[Guest Durreau]

Can someone be able to port this rom for Canvas Nitro a310?

 

Thi is not the place for such petition, make a thread in the appropiate forum and wait for any response...

[Guest qiib]

Hello, KonstaT! Once again, very grateful for your work.

So: I have a cm-12.1-20150402-UNOFFICIAL-KonstaKANG-kis3 + pa_gapps-modular-pico-5.1-20150315-signed.zip.

However, the nasty "Google maps" does not want to run. Here's the log, maybe you would be interested ..

With respect and gratitude, qiib.

 

2015-04-09_01-32-50.zip

[Guest KonstaT]

 

Hello, KonstaT! Once again, very grateful for your work.

So: I have a cm-12.1-20150402-UNOFFICIAL-KonstaKANG-kis3 + pa_gapps-modular-pico-5.1-20150315-signed.zip.

However, the nasty "Google maps" does not want to run. Here's the log, maybe you would be interested ..

With respect and gratitude, qiib.

 

2015-04-09_01-32-50.zip

 

I tested Google Maps on my device and it works just fine. I've never received any other reports about it not working either.

 

Fact that you have the same problem on other ROMs too and with several gapps packages would rather indicate something related to how you've set up your device. Make sure you've followed installation instructions in the third post (including formatting /system) and you're using the correct gapps package for your Android version.

 

If you could be a little more specific what you mean with 'does not want to run' might help (force-closes, closes without any message, freezes, what?). Also a 'regular' logcat (e.g. 'adb logcat > filename.txt' from a computer connected with USB) would give a better overall picture of what's happening.

[Guest ncrxyz]

i'm using cm12 and found some lag and force close in some app ex: twitter/clash of clans,

then i'll back to cm11 or kitkat. how to back to prev?

sorry my english to bad

[Guest KonstaT]

i'm using cm12 and found some lag and force close in some app ex: twitter/clash of clans,

then i'll back to cm11 or kitkat. how to back to prev?

sorry my english to bad

And logically this of course belongs to CM12.1 thread... :P

 

You can either restore a nandroid backup you've made of your CM11 installation or follow installation instructions and start again from the scratch. Doing a 'dirty' downgrade is not possible.

[Guest qiib]

 

I tested Google Maps on my device and it works just fine. I've never received any other reports about it not working either.

 

Fact that you have the same problem on other ROMs too and with several gapps packages would rather indicate something related to how you've set up your device. Make sure you've followed installation instructions in the third post (including formatting /system) and you're using the correct gapps package for your Android version.

 

If you could be a little more specific what you mean with 'does not want to run' might help (force-closes, closes without any message, freezes, what?). Also a 'regular' logcat (e.g. 'adb logcat > filename.txt' from a computer connected with USB) would give a better overall picture of what's happening.

 

Hi, KonstaT! You are right as always! Everything works fine. Most likely, the problem was that I first launched the phone without gapps, and installed them only after a reboot. But when I installed all at once, and then loaded the phone, it worked. Thank you very much for the support and assistance! I'm happy now! This ROM best of all.

With gratitude, qiib.

[Guest soyvmva_]

Hi, i need an optimizer, which you recomend me? I not speak good english

Edited April 11, 2015 by soyvmva_

[Guest KonstaT]

Hi, i need an optimizer, which you recomend me? I not speak good english

No idea what this 'optimizer' is, but I seriously doubt you need one... ;)

[Guest Richard Miller]

Why do i keep getting force close in the follow apps: Camera, Gallery, File Manager, Music. First boot works fine after one rebot those app won´t open.

[Guest KonstaT]

Why do i keep getting force close in the follow apps: Camera, Gallery, File Manager, Music. First boot works fine after one rebot those app won´t open.

Because you removed your external sdcard from your device during that reboot. ;) None of my builds supports internal sdcard (FAQ, third post) so you must have an external sdcard inserted on the device. Some apps still write data to primary storage (external sdcard in this case).

[Guest IvanIvanov97]

No idea what this 'optimizer' is, but I seriously doubt you need one... ;)

'Optimizer' means more performance in Russian :)

[Guest soyvmva_]

Exactly ;)

'Optimizer' means more performance in Russian :)

[Guest KonstaT]

'Optimizer' means more performance in Russian :)

 

Exactly ;)

Which still doesn't quite explain what you wanted to ask. :P There's a 'performance' option under Settings -> Battery -> Battery mode. It will lock your CPU/GPU governors to the highest available frequency but it will of course have negative impact on battery life. There's really not any magical ways to increase performance or it would have been implemented already.

 

If you want better performance - buy a better device. This is an entry level/budget device and it performs exactly like what you'd expect from a 50€ msm8610 device. And it's really not even bad compared to some other devices (e.g. on AnTuTu, my Open C scores ~15k vs. ~19k on my Moto G). :)

[Guest alvarogilfalco]

I use your roms since 1 year and found perfectly, but in the las try with lollipop, i find 1 error or bug, when i change of energetic profile (batery save, balanzed and high performance) the screen of mi mobile turns off, the mobile continues turn on exceptly tehe screen, I told you because I have enough knowledge to fix it myself.

The problem is only on cyanogemod 12 and 12.1 versions.

[Guest KonstaT]

I use your roms since 1 year and found perfectly, but in the las try with lollipop, i find 1 error or bug, when i change of energetic profile (batery save, balanzed and high performance) the screen of mi mobile turns off, the mobile continues turn on exceptly tehe screen, I told you because I have enough knowledge to fix it myself.

The problem is only on cyanogemod 12 and 12.1 versions.

Please attach an appropriate log (logcat) and some additional info of your device (model, country/place of purchase, screenshots of 'Kis 3 Hardware Info' app, etc). Make sure you've followed installation instructions in the third post (including formatting /system) and you're using the correct gapps package for your Android version.

 

I can't reproduce this issue on my device and I haven't received any reports of such issue before either.

[Guest firecm]

KosTaT, I'd like to flash the 12.1, do you plan to release a new build this week?