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

[Guest spalock]

Thanks for the clarification.

I've seen a CM 12 branch in your repos, is it related to lollipop? :P

[Guest KonstaT]

Thanks for the clarification.

I've seen a CM 12 branch in your repos, is it related to lollipop? :P

Nothing to see there yet. ;)

[Guest haybat]

 

OK, so it controls nothing then. :P I remember there being some discussion about dual-SIM network mode tile but I couldn't remember what that was about. Unfortunately this is something I can't do anything about without having a dual-SIM device myself.

 

I found a list of CM11 dual-SIM issues/limitations from an another device. These should apply here too:

 

 

okay KonstaT

thanks for your information...

actually after couple of restarting my phone i can lock 3G only via *#*#4636#*#*

altough it will be set to 3G preferred again after turn off the phone

thanks for your great build KonstaT

will be waiting for your next great build...

Thank You...

:)

[Guest skynetdev]

Very strange but now my phone is working fine 3 days

I love this build thank you so much

[Guest arifmams]

btw, how to make external sdcard as internal sdcard on stock rom?

[Guest KonstaT]

btw, how to make external sdcard as internal sdcard on stock rom?

Completely off topic but iirc there was an option which storage to use as primary in stock KitKat. So why is this necessary?

 

Internal and external sdcards can't be 'switched' because ZTE uses emulated internal sdcard (/data/media) on Android builds (Kis 3 partition layout). It would be a lot easier if there was a physical internal sdcard partition like in Open C partition layout. Removing the internal sdcard completely (and setting external as primary) is a bit tricky because you'd need to decompile/compile framework and split the boot.img to access kernel ramdisk to make the necessary modifications.

[Guest andy1971]

I just thought i would pop in and say Thank You, This build just saved my Life.

Somehow i lost all ability to use 3G in Australia, and the standard FFOS is absolutly horrible.

Now i have android 4.4 and Google Play. Services installed. OMG and can even download stuff from the store, make a new account and have google love me again :P

 

For the last 3 days i have been trying builds with no success, and tonight finally when i installed this Mod my phone came to life, so far no issues, i would recomend this to anyone who has a ZTE Open C.

 

You guys are a credit to Society. And please keep up the good Work

 

Thanks Form a Poor old Aussie.

 

Im never gonna remove this, well unless you make a awesome 5.0 :)

Edited December 15, 2014 by andy1971

[Guest mojojojo67]

@andi1971:->android 5.0 (cyanogenmod12)

http://www.modaco.com/topic/373968-devrom2011-cyanogenmod-12-android-50-for-zte-open-c-kis-3/

 

 

:)

[Guest alfcup]

@KonstaT

 

Hi Sir, do you think this rom can be ported to Huawei Y530. Same specs.

 

Thanks in advanced.

[Guest KonstaT]

@KonstaT

 

Hi Sir, do you think this rom can be ported to Huawei Y530. Same specs.

 

Thanks in advanced.

AFAIK Y530 has unlocked/unlockable bootloader and the kernel source is also available. This means there's nothing stopping anyone from building CyanogenMod for your device. There's no point in speculating possibilities of a winzip port when there are far better methods are available.

 

This is the place to start:

http://wiki.cyanogenmod.org/w/Development

[Guest mpontes]

Hello,

I'm getting crashes on every single application that calls android.app.ContextImpl.getExternalCacheDir() (quite a few, CM's Apollo, YouTube and Google Newsstand crash on startup because of it) when running without an SD card. Does this ROM require an external SD card in order to work properly? getExternalCacheDir() should just return null in this case rather than throw a runtime exception, the applications aren't ready to handle that and crash.

 

Here's the logcat excerpts for the 3 applications I mentioned above:

E/AndroidRuntime( 5662): FATAL EXCEPTION: main
E/AndroidRuntime( 5662): Process: com.google.android.youtube, PID: 5662
E/AndroidRuntime( 5662): java.lang.RuntimeException: Unable to create application com.google.android.apps.youtube.app.YouTubeApplication: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
E/AndroidRuntime( 5662):  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4476)
E/AndroidRuntime( 5662):  at android.app.ActivityThread.access$1500(ActivityThread.java:144)
E/AndroidRuntime( 5662):  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1265)
E/AndroidRuntime( 5662):  at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 5662):  at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 5662):  at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 5662):  at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 5662):  at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 5662):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 5662):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 5662):  at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 5662): Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
E/AndroidRuntime( 5662):  at android.app.ContextImpl.getExternalCacheDir(ContextImpl.java:969)
E/AndroidRuntime( 5662):  at android.content.ContextWrapper.getExternalCacheDir(ContextWrapper.java:235)
E/AndroidRuntime( 5662):  at clf.e_(SourceFile:235)
E/AndroidRuntime( 5662):  at clh.b(SourceFile:262)
E/AndroidRuntime( 5662):  at clh.e_(SourceFile:255)
E/AndroidRuntime( 5662):  at ato.a(SourceFile:932)
E/AndroidRuntime( 5662):  at ezs.b(SourceFile:92)
E/AndroidRuntime( 5662):  at ezs.e_(SourceFile:76)
E/AndroidRuntime( 5662):  at atp.a(SourceFile:950)
E/AndroidRuntime( 5662):  at ezs.b(SourceFile:92)
E/AndroidRuntime( 5662):  at ezs.e_(SourceFile:76)
E/AndroidRuntime( 5662):  at ari.S(SourceFile:2194)
E/AndroidRuntime( 5662):  at com.google.android.apps.youtube.app.YouTubeApplication.e(SourceFile:190)
E/AndroidRuntime( 5662):  at ckz.onCreate(SourceFile:33)
E/AndroidRuntime( 5662):  at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
E/AndroidRuntime( 5662):  at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4473)
E/AndroidRuntime( 5662):  ... 10 more
 
E/AndroidRuntime( 5582): FATAL EXCEPTION: AsyncTask #1
E/AndroidRuntime( 5582): Process: com.andrew.apollo:main, PID: 5582
E/AndroidRuntime( 5582): java.lang.RuntimeException: An error occured while executing doInBackground()
E/AndroidRuntime( 5582):  at android.os.AsyncTask$3.done(AsyncTask.java:300)
E/AndroidRuntime( 5582):  at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
E/AndroidRuntime( 5582):  at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
E/AndroidRuntime( 5582):  at java.util.concurrent.FutureTask.run(FutureTask.java:242)
E/AndroidRuntime( 5582):  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/AndroidRuntime( 5582):  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/AndroidRuntime( 5582):  at java.lang.Thread.run(Thread.java:841)
E/AndroidRuntime( 5582): Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
E/AndroidRuntime( 5582):  at android.app.ContextImpl.getExternalCacheDir(ContextImpl.java:969)
E/AndroidRuntime( 5582):  at android.content.ContextWrapper.getExternalCacheDir(ContextWrapper.java:235)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache.getExternalCacheDir(ImageCache.java:652)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache.getDiskCacheDir(ImageCache.java:629)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache.initDiskCache(ImageCache.java:159)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache.access$000(ImageCache.java:50)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache$1.doInBackground(ImageCache.java:140)
E/AndroidRuntime( 5582):  at com.andrew.apollo.cache.ImageCache$1.doInBackground(ImageCache.java:135)
E/AndroidRuntime( 5582):  at android.os.AsyncTask$2.call(AsyncTask.java:288)
E/AndroidRuntime( 5582):  at java.util.concurrent.FutureTask.run(FutureTask.java:237)
E/AndroidRuntime( 5582):  ... 3 more
 
E/AndroidRuntime( 5470): FATAL EXCEPTION: NSCLIENT_PRIVATE #1
E/AndroidRuntime( 5470): Process: com.google.android.apps.magazines, PID: 5470
E/AndroidRuntime( 5470): java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
E/AndroidRuntime( 5470):  at android.app.ContextImpl.getExternalCacheDir(ContextImpl.java:969)
E/AndroidRuntime( 5470):  at android.content.ContextWrapper.getExternalCacheDir(ContextWrapper.java:235)
E/AndroidRuntime( 5470):  at com.google.apps.dots.android.newsstand.upgrade.Upgrade$2.run(Upgrade.java:78)
E/AndroidRuntime( 5470):  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/AndroidRuntime( 5470):  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/AndroidRuntime( 5470):  at com.google.android.libraries.bind.async.Queue$3$1.run(Queue.java:103)
E/AndroidRuntime( 5470):  at java.lang.Thread.run(Thread.java:841)

[Guest KonstaT]

Hello,

I'm getting crashes on every single application that calls android.app.ContextImpl.getExternalCacheDir() (quite a few, CM's Apollo, YouTube and Google Newsstand crash on startup because of it) when running without an SD card. Does this ROM require an external SD card in order to work properly? getExternalCacheDir() should just return null in this case rather than throw a runtime exception, the applications aren't ready to handle that and crash.

Yes, it does. You must have an external sdcard inserted on your device for everything to work properly. Many apps write data to Android directory on the root of the primary sdcard which in this case is the external sdcard.

[Guest boogyboo]

so, i just hooked the phone to my service using the most recent of your builds

 

and

 

so far,

 

no major complaints.  good job.

 

i've got hspa+ so it's using the best connectivity.  i have the english standard open c that was sold by zteusa on ebay.

 

 

the only thing negative i have to say is that there really needs to be some overlay work done in the device tree, so that's exactly what i'm doing in the source right now to perfect the build for my daily use.

 

i appreciate all your hard work.

[Guest Koetermann]

Hi KonstaT,

 

thank you so much for your support for the ZTE open c. My 8 year old son got this one at his birthday in august. Until now I had installed an AOSP 4.4.2. but there were many issues with the Google Play Store.

 

Yesterday I took a look if there is an alternative for this phone and found your thread here. So I decided to install your compiled TWRP recovery and CM 11. And that's pretty cool. Now the phones works like a real android phone. :wub:

 

Just one question: Is there a way to switch the right button to an overview button (like on the Nexus or I guess on Lollipop)? I know that's not a native thing to your ROM but maybe you have a solution for this?

 

Thanks and regards

 

Koetermann 

Edited December 23, 2014 by Koetermann

[Guest KonstaT]

Just one question: Is there a way to switch the right button to an overview button (like on the Nexus or I guess on Lollipop)? I know that's not a native thing to your ROM but maybe you have a solution for this?

Settings -> Buttons. All hardware key actions can be reassigned there.

 

By default recent apps view can be accessed by long pressing the home key. This is the AOSP default for devices with hardware keys, but ZTE did something strange and changed it in their stock Android firmware IIRC. I'm not sure if removing menu action altogether is a good idea. There still might be some older/outdated apps that don't show the virtual action overlay button (three dots) on devices with hardware keys and you'd be left without access to app's settings menu.

[Guest johnyrocks2014]

So as I mentioned in the CM12 thread I flashed cm11 and found mostly everything working fine just one weird bug, when the phone is turned on the home button will not work, the other two buttons work fine but without haptic feedback, also using any app/drawer button will not give haptic feedback. For some reason after launching Settings home button and haptic feedback work fine, same behaviour happened with the onscreen navigation bar.

 

Also I haven't been able to reproduce it again but after locking the phone and waking it up the haptic feedback was gone and had to launch Settings to restore it.

I have been installing this and other of your roms a couple of times, everytime I format system, wipe cache, wipe data and factory reset then flash the rom.

 

I can't understand how to accurately track an issue with logcat, but let me attach it here.

 

What I did is turn on the phone, wait 2 mins, verify home button and haptic feedback are not working, launch logcat using the shortcut, start recording in verbose, check again home button and hf are not working, swipe down from the top to show settings, open settings, touch home button and confirm its working and hf is also working, swipe down and stop recording.

2014-12-27-17-25-10.txt

Edited December 27, 2014 by johnyrocks2014

[Guest KonstaT]

So as I mentioned in the CM12 thread I flashed cm11 and found mostly everything working fine just one weird bug, when the phone is turned on the home button will not work, the other two buttons work fine but without haptic feedback, also using any app/drawer button will not give haptic feedback. For some reason after launching Settings home button and haptic feedback work fine, same behaviour happened with the onscreen navigation bar.

 

Also I haven't been able to reproduce it again but after locking the phone and waking it up the haptic feedback was gone and had to launch Settings to restore it.

I have been installing this and other of your roms a couple of times, everytime I format system, wipe cache, wipe data and factory reset then flash the rom.

 

I can't understand how to accurately track an issue with logcat, but let me attach it here.

 

What I did is turn on the phone, wait 2 mins, verify home button and haptic feedback are not working, launch logcat using the shortcut, start recording in verbose, check again home button and hf are not working, swipe down from the top to show settings, open settings, touch home button and confirm its working and hf is also working, swipe down and stop recording.

Strange as it sounds but issue with home button not working is quite often related to wrong Google apps package. This usually happens when people don't know how to properly wipe their devices (/system is not formatted and wrong gapps are restored during ROM installation) or they've installed gapps package for the wrong Android version to begin with.

 

I've never experienced such issue myself.

[Guest andy1971]

@andi1971:->android 5.0 (cyanogenmod12)

http://www.modaco.com/topic/373968-devrom2011-cyanogenmod-12-android-50-for-zte-open-c-kis-3/

 

 

:)

 

thanks ill try this, i did notice randomly the phone would die and id have to reove the battery, seems to happen randomly mostly during phonecalls (on the 4.4 kitkat)

[Guest ipk1]

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 ...

Log_2015-01-10_09-32-12.txt

Edited January 10, 2015 by ipk1

[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 ...

What device do you have? There's even at least two different versions of Open C. Were you using a bluetooth headset? Can you get dmesg too?

 

I can't reproduce that issue on my device but I see bunch of audio errors in the log. Some other people have reported the same thing during calls. It could possibly be something about audio or maybe even sensor related (my device doesn't have a proximity sensor). Also you could test the previous builds from the second post to see if the issue present. There was a big kernel update after 20141012 so it would be good to know if there's difference between the two.

[Guest ipk1]

Dmesg attached ... but i am not sure whether that would cover the latest crash from this morning ...

dmesg.txt

[Guest ipk1]

And I did no know there are different devices. How can I tell which one I have ?

Not using a bluetooth headset at the time.

If all fails I will try and install a previous version as you suggested.

[Guest KonstaT]

Dmesg attached ... but i am not sure whether that would cover the latest crash from this morning ...

When did you take this log? It has at least some voice call happening at the end?

 

And I did no know there are different devices. How can I tell which one I have ?

Not using a bluetooth headset at the time.

If all fails I will try and install a previous version as you suggested.

I wrote an app for it - Kis3Info. It's included in my CM builds. Please post screenshots info what model you have and where/what country you've purchased it to the appropriate thread.

[Guest ipk1]

 

When did you take this log? It has at least some voice call happening at the end?

 

I wrote an app for it - Kis3Info. It's included in my CM builds. Please post screenshots info what model you have and where/what country you've purchased it to the appropriate thread.

 

Yes ... not all phone calls crash it. Just every other incoming call. But it also crashes spontaneously randomly. I'll try and grab dmesg after the next crash and post here. Should be soon :-(

THIS one was, i think, not recorded right after a crash. I tried to call myself a couple of times now to crash it, but it does not do me the favour right now. Have to wait ... sorry ... 

Edited January 11, 2015 by ipk1

[Guest ipk1]

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 ...

dmesg.txt

Edited January 12, 2015 by ipk1