[DEV][ROM][17.11.] CyanogenMod 11 (Android 4.4.4) for ZTE Open C / Kis 3

[Guest KonstaT]

No further incoming call crashes today, but a complete random crash instead. Might that be related ? I attach dmesg pulled directly after the crash (does this even help at all ? i have the feeling it does not go back beyond the boot ...). This is really annoying ... my casing is beginning to wear out from all the times I have to pull the battery ...

Is that on the build I suggested you to test (twice)?

 

Nothing in dmesg survives a reboot. There should be last_kmsg for that but never seen one on this device. Also I have no idea why this device freezes when kernel panic happens - any other device would just reboot.

 

There's a changelog and list of previous builds in the second post. There was a massive kernel update in 20141029 (it's always possible I have fcked up something there). SELinux was set to enforcing before that in 20141012 (you can try setting it back to permissive in more recent builds - there's an app for it). All builds before 20141012 had a known issue with kernel panic related to weak wifi signal so those are not even available for download since it was resolved (wouldn't recommend anyone to use).

 

It is near impossible to anything about issues I can't reproduce myself. No logs, no ideas what it might be related to -> likely no fix.

[Guest KonstaT]

New build. One of the 'final' builds if not the very last. Basically all CyanogenMod development has moved towards CM12 and I'm going to focus my efforts there as well. Added some crazy-cool features this time. :P Nothing much new in CM upstream, mostly translations anymore.

 

cm-11-20150113-UNOFFICIAL-KonstaKANG-kis3.zip

http://www.mediafire.com/?xotcv0vv3rv7bt5

md5:36c86c8435465092c87ac68806c922c9

 

-add display color calibration option

-add performance profiles

-add key disabler (disables hardware virtual keys when navigation bar is enabled just like on OnePlus One)

[Guest okmikel]

Made an Update to this build today after going back to CM11 as I wrote in the CM12 thread. Works great, thank you.

[Guest lek669]

How to Fix bootloop, Now i use a remove battery and boot to recovery for wipe cache and Dalvik Cache and reboot it Work (V811W)

 

 

... Sorry I,m bad English

[Guest KonstaT]

My Open C crashes frequently when I have calls incoming. I pick up the call, I can talk some 5 seconds, and then the phone goes into a complete freeze. The latest log is attached and to me none of that really means anything. Any ideas ? Do I need to record more details in the log so anybody might be able to help me? I am about to put the stock rom back on and sell the thing ...

 

Any help would be greatly appreciated. I like the little phone and the rom, but with that kind of problems it is a bit difficult ...

Maybe it would have been worth mentioning that this behavior can be reproduced on all firmware, including stock Firefox OS and stock Android, not just custom ROMs...

 

Looks like this a known issue with some devices.

https://support.mozilla.org/en-US/questions/1003430

https://bugzilla.mozilla.org/show_bug.cgi?id=1017604

[Guest gepenk cunks]

its work on zte v811w?

[Guest KonstaT]

its work on zte v811w?

How about you start by reading the first three posts of this thread...

[Guest gepenk cunks]

sorry mister my english is bad.. i cant read ?.. are my zte v811w can use this rom? or cm 12

[Guest Wolfiuz]

Hey, do you know any method that works on a Zte open to install Android?
I updated my Zte open C with this post and installed gaps, Ty.  

[Guest KonstaT]

Hey, do you know any method that works on a Zte open to install Android?

I updated my Zte open C with this post and installed gaps, Ty.  

Slightly off-topic, but ZTE Open is Kis/V790 (codename roamer2). I know there's few different hardware revisions of that device though. Some Kis/V790 stock Android firmware will likely work on an Open (as Open Firefox OS firmware works on a Kis/V790 - http://firefox.ztems.com/).

 

MoDaCo has a dedicated forum section for that device.

http://www.modaco.com/forum/708-zte-kis-orange-dublin/

[Guest stadtmobi]

First of all: Thank you very much for your effort.

CM11 works fine on the Open C.

 

I wanted to go back to FFOS to do some app tests but the OpenCUpgrade tool that i've used does not recognize my device anymore.

 

Do you know how to get back to Firefox OS (i use these builds http://builds.firefoxos.mozfr.org/doc/en/devices/zte-open-c-eu#support )

 

Thanks in advance!

[Guest KonstaT]

First of all: Thank you very much for your effort.

CM11 works fine on the Open C.

 

I wanted to go back to FFOS to do some app tests but the OpenCUpgrade tool that i've used does not recognize my device anymore.

 

Do you know how to get back to Firefox OS (i use these builds http://builds.firefoxos.mozfr.org/doc/en/devices/zte-open-c-eu#support )

 

Thanks in advance!

If you just need a Firefox OS build, there's my CAF B2G 2.0 build here. You can simply flash that in CWM now that you've already updated to Android KitKat.

 

Returning back to stock Firefox OS would happen the same way you've updated to stock KitKat. Boot/flash a stock recovery (this one to be specific) and flash EU_Android+to+FFOS.zip using it.

[Guest estefanocassu]

This Kernel support only 128MB at SWAP? :wacko:  and 5.0.2 support 256MB

[Guest ghostwheell]

Hi,

I install cwm no problem with install rom, but multitouch not working on my kis 3 any advice ?

[Guest KonstaT]

This Kernel support only 128MB at SWAP? :wacko:  and 5.0.2 support 256MB

zRAM - not swap. I've increased zRAM size from 128mb to 256mb in Lollipop but that might actually be a little excessive (it's more than 50% of total available RAM). Kernel supports both zRAM and swap and there's nothing stopping you from creating a swap file or a swap partition on your sdcard and using it.

 

Hi,

I install cwm no problem with install rom, but multitouch not working on my kis 3 any advice ?

Just multi-touch or touchscreen doesn't work at all?

 

Please post the touchscreen info from 'Kis 3 Hardware Info' app. Touchscreen doesn't work on devices with Goodix GT960F touchscreen hardware with the current kernel source ZTE has released. My CAF Android build with the stock kernel add-on is the only custom ROM that will work on devices with that touchscreen hardware.

[Guest Durreau]

Konstat, how to do for permanently the "disable hw overlays" in developer options?

[Guest KonstaT]

New build. Mostly just security updates and backporting relevant device changes. There's still some activity in CM's cm-11.0 branch but it's been mostly translations lately. Again, it's very possible that this is the final build but will see in couple of months if there's still changes worth doing a build.

 

cm-11-20150328-UNOFFICIAL-KonstaKANG-kis3.zip

http://www.mediafire.com/?l30pkj08bwml9i6

md5:d7f5ad69284ac8d43c74fbbc3eafe7ce

 

-use userspace implementation to set correct wlan MAC address

-add camera wrapper to disable unsupported HDR mode

-update 'Kis 3 Hardware Info' app to v0.7.5

-build iris fm and pronto wlan drivers into kernel and disable modules support (we're going moduleless :P)

-patch known vulnerabilities in kernel (CVE-2015-1465, CVE-2014-8160, CVE-2014-9683, CVE-2015-1420 and CVE-2014-8173)

-remove support for unused hardware in kernel

-tweak kernel build flags for Cortex-A7

-add optimized memutils in kernel (thanks to Motorola)

-patch OpenSSL FREAK attack (CVE-2015-0204 - merged)

[Guest KonstaT]

Konstat, how to do for permanently the "disable hw overlays" in developer options?

Why would you want that?

 

It seems that the option directly hooks to surfaceflinger so it can't be enabled persistently (vs. there was e.g. a system property it switches).

[Guest Durreau]

ah ok, thanks for the info... ^_^

[Guest ipk1]

Maybe it would have been worth mentioning that this behavior can be reproduced on all firmware, including stock Firefox OS and stock Android, not just custom ROMs...

 

Looks like this a known issue with some devices.

https://support.mozilla.org/en-US/questions/1003430

https://bugzilla.mozilla.org/show_bug.cgi?id=1017604

Oh my ... allright ... indeed, following the recommendations from this thread I have already installed a few older roms. Problems persist ... Guess I'll get rid of the phone then. Too bad ... 1000 thanks

[Guest samishal]

Hi,

 

I've just installed the latest build that you posted (Cyanogenmod 11) but I've run into an issue with the battery and charging and was wondering if anyone had experienced this.

 

Basically, just flashed the ROM installation went fine however when connected to a charger (tried both USB connected to pc and a wall socket) the battery does not charge. There aren't any charging indicators in either the status bar or the battery options.

 

It seems to charge normally when the phone is turned off and I have deleted the battery stats.bin and am waiting for the phone to fully recharge before switching it back on and regenerating the file.

 

Anyone else experienced this? Know any better solutions in case the one I found doesn't work?

 

Samishal

[Guest KonstaT]

Hi,

 

I've just installed the latest build that you posted (Cyanogenmod 11) but I've run into an issue with the battery and charging and was wondering if anyone had experienced this.

 

Basically, just flashed the ROM installation went fine however when connected to a charger (tried both USB connected to pc and a wall socket) the battery does not charge. There aren't any charging indicators in either the status bar or the battery options.

 

It seems to charge normally when the phone is turned off and I have deleted the battery stats.bin and am waiting for the phone to fully recharge before switching it back on and regenerating the file.

 

Anyone else experienced this? Know any better solutions in case the one I found doesn't work?

 

Samishal

Have you disabled Settings -> Developer options -> USB charging?

 

Removing batterystats.bin doesn't do anything besides clear 'Battery usage' statistics in Android setting. It has nothing to do with battery calibration, etc.

https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT

[Guest samishal]

Have you disabled Settings -> Developer options -> USB charging?

 

Removing batterystats.bin doesn't do anything besides clear 'Battery usage' statistics in Android setting. It has nothing to do with battery calibration, etc.

https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT

Ah man I feel stupid. Cheers man, also thanks for the kickass ROM. That was literally the only thing bugging me about it and it was my own stupidity lol. Cheer again.

[Guest mrDoctorWho]

Hello.

First of all, I would like to thank KonstaT for this awesome build.

Last time I was trying to install ArchLinux on ZTE Open C (in android chroot) to get some useful features, and just for fun I tried to run Xorg. This make me notice that Xorg can't open device /dev/graphics/fb0 (but /dev, /proc and such were properly mounted), so I tried to open the device directly from android and ran into the same problem as in chroot:

/dev/graphics/fb0: No such device

Is there any way to get the device working? Thanks.

Edited April 12, 2015 by mrDoctorWho

[Guest KonstaT]

Hello.

First of all, I would like to thank KonstaT for this awesome build.

Last time I was trying to install ArchLinux on ZTE Open C (in android chroot) to get some useful features, and just for fun I tried to run Xorg. This make me notice that Xorg can't open device /dev/graphics/fb0 (but /dev, /proc and such were properly mounted), so I tried to open the device directly from android and ran into the same problem as in chroot:

Is there any way to get the device working? Thanks.

There most definitely is /dev/graphics/fb0 or something has gone terribly wrong (you wouldn't have anything displayed on the screen without frame buffer). More likely you just don't have access to it for some reason (wrong permissions/owner or access is denied by SELinux).

 

Which documentation are you following? Have you bind mounted/symlinked original /dev to your chroot's /dev?