[DEV][ROM][2.7.] CyanogenMod 11 (Android 4.4.4)

[Guest bezkintos]

Guys help me please. Im getting that status7 error when im trying to install cm-11-20140607-UNOFFICIAL-KonstaKANG-atlas40.zip.I cant use my phone now D:

 

Cant even restore, it says md5 mismatch

 

&

 

cm-11-20140607-UNOFFICIAL-konstakang-atlas40.zip I'm getting the following warnings when installing.

http://img496.yukle.tc/image.php?id=7773IMG_20140620_192624.jpg

 

Better edit your posts before KonstaT see it! :P

He wrote in red:You will need updated recovery image (CWM, TWRP) to install this build!!!

So you have CWM recovery 6.0.2.7 and you need 6.0.4.9 (see the first post). You can instal it from your current CWM recovery, just restart your phone after that

Edited June 20, 2014 by bezkintos

[Guest ArmenMM]

&

 

 

Better edit your posts before KonstaT see it! :P

He wrote in red:You will need updated recovery image (CWM, TWRP) to install this build!!!

So you have CWM recovery 6.0.2.7 and you need 6.0.4.9 (see the first post). You can instal it from your current CWM recovery, just restart your phone after that

 

 

Awh man, finally! Love you [no homo], thanks!

[Guest Jowat]

Delete this Post

Edited November 9, 2014 by Jowat

[Guest 988twister988]

KitKat use more battery

CPU-Z 

Stock rom       3750-3850 mV

CM 11             4020-4090 mV

Edited June 21, 2014 by 988twister988

[Guest Madaz]

WARNING:

 

Android Version 4.4.4 is released. And it is really important to update, because 4.4.3 has a big bug! It is possible to spy your whole Internet-Activity, through an OpenSSL bug (Heartbleed Bug), so even if you are using an encrypted SSL Connection you can get hacked with the MITM-attack! So don’t use Online-Banking until 4.4.4 is released for Blade III.  CyanogenMod already released a Custom-ROM for 4.4.4, but we have to wait until it is released for Blade III. In 4.4.4 also few other bugs get fixed.

 

For more information read: 

https://blog.whitehatsec.com/ssltls-mitm-vulnerability-cve-2014-0224/

http://www.theinquirer.net/inquirer/news/2351339/android-444-kitkat-unexpectedly-arrives-with-openssl-fix

http://stadt-bremerhaven.de/cyanogenmod11-android4-heads-up/

 

No need to start a hysteria, a little bit of googling and you would of found that heartbleed was fixed in 4.4.3 and added in the June 6th build of CM

 

http://www.androidpolice.com/2014/06/19/google-rolling-out-android-4-4-4-update-ktu84p-with-a-security-fix-factory-imagesbinaries-up-for-nexus-devices/

[Guest MJonMoDaCo]

 

No need to start a hysteria, a little bit of googling and you would of found that heartbleed was fixed in 4.4.3 and added in the June 6th build of CM

 

http://www.androidpolice.com/2014/06/19/google-rolling-out-android-4-4-4-update-ktu84p-with-a-security-fix-factory-imagesbinaries-up-for-nexus-devices/

 

^^ He didn't even have to go that far:

 

 

please release new version since heartbleed bug fix (openssl git 96db9023b881d7cd9f379b0c154650d6c108e9a3) is already in CM

http://heartbleed.com/

 

only Android 4.1.1 is affected. to be paranoid I grep'd through the 4.4.2 src trees and HEARTBEAT does seem to be off everywhere.

 

Phew. Indeed, external/openssl/build-config.mk has -DOPENSSL_NO_HEARTBEATS 

 

Ooh mah heart, there it is... XD

 

KitKat use more battery

CPU-Z 

Stock rom       3750-3850 mV

CM 11             4020-4090 mV

 

Yeah cool.... that's about 7% better...

Do you think your stock ROM is 7% better than CM11? Each to their own I guess....

Personally, I think my stock ROM is 70% worse.

[Guest KonstaT]

WARNING:

 

Android Version 4.4.4 is released. And it is really important to update, because 4.4.3 has a big bug! It is possible to spy your whole Internet-Activity, through an OpenSSL bug (Heartbleed Bug), so even if you are using an encrypted SSL Connection you can get hacked with the MITM-attack! So don’t use Online-Banking until 4.4.4 is released for Blade III.  CyanogenMod already released a Custom-ROM for 4.4.4, but we have to wait until it is released for Blade III. In 4.4.4 also few other bugs get fixed.

 

For more information read: 

https://blog.whitehatsec.com/ssltls-mitm-vulnerability-cve-2014-0224/

http://www.theinquirer.net/inquirer/news/2351339/android-444-kitkat-unexpectedly-arrives-with-openssl-fix

http://stadt-bremerhaven.de/cyanogenmod11-android4-heads-up/

Please get your facts straight before posting silly warnings with red, cat sized, capital letters!

 

Heartbleed is old news (april) and it never affected Android besides one rare version (Jelly Bean 4.1.1). Three more recent OpenSSL vulnerabilities (june) were pathed in CM11 immediately after they were announced. Patched OpenSSL is already included in the latest 4.4.3 build like you could have read from the changelog in the second post (or CyanogenMod blog). Android 4.4.4 brings nothing much but a version number bump to CM11 (http://review.cyanogenmod.org/#/c/66093/).

[Guest Saky]

Does anyone have "sleep of death" bug in latest build? Everything else is working fine just sometimes when I try to wake phone with power button screen stays black! Only capacitive buttons lights up. Only thing I can do is to remove and reinsert battery or hold the power button for 10 sec to reboot the device! It happens randomly and not so often but...Tried reflashing, download rom again, factory reset,formating everything in latest CWM recovery before and after installing latest build of CM11...After some search I noticed that others have same problem with different phones and roms but found no fix for it.

[Guest Something Wierd]

Noticed it only once,today when the phone was charging. If it happens so often to you why not get a log cat the next time it happens.

[Guest Jowat]

Delete this Post 

Edited November 9, 2014 by Jowat

[Guest papars]

Logcat from my Acqua regarding a wifi issue.

 

From time to time the wifi is stuck showing old access points.  Like is loading a snapshot from the past.  Obviously is not connecting to any network even if this exists in this old scan.

 

Often turning off and on wifi will restore normal operation but usually a reboot is needed.

The log is from such situation.  After the log is taken I've rebooted the phone to get wifi back.

 

Acqua patch is applied.

2014-06-23-19-03-10.rar

Edited June 23, 2014 by papars

[Guest Saky]

I will post a logcat...as far as I can understand after doing some research it is a android 4.4.3 bug...

Jowat 

what build are you using that has no "sleep of death" bug?

Edited June 23, 2014 by Saky

[Guest vuj1ca]

I'm having this bug too.

The phone just sleeps and i can't get it on, untill removing the battery.

Sometimes the phone just stop responding while in use, when the screen is on.

Not responding to touch, volume rocker, or a power buton.

Then the screen goes black, and battery must be removed....

[Guest alekcacko]

I have that bug too. 

[Guest dubstep774]

I have experienced that bug too but in my case the reboot necessity is not as high because when I see only the capacitive buttons light up I quickly sleep the phone back and wake it up after a short wait and hey presto the screen lights up. (When I experienced this bug in older builds Reboot was certain everytime) Now I can say that the only resets I get are the ones I want to do for various reasons, thus making this build the most stable one so far (my opinion)

Edited June 24, 2014 by dubstep774

[Guest MJonMoDaCo]

Whereas in my case today I couldn't answer a phone call because the phone wouldn't wake up! Didn't happen on the last build, and this is the only phone call I've received since flashing, so idk. Installed the logger and hope to catch this one...

[Guest chrysn]

i'm having issues with wifi with the cm11 version which are not present in cm10.2 and stock images. to be precise, the wifi button is always set to "off" and disabled, while in the wifi settings dialog it says "Turning Wi-Fi on...".
 
i've uploaded logcat files from the working (cm10.log) and non-working (cm11.log) versions to  https://gist.github.com/anonymous/484cdfb13234c90d1e97 ; the images used to create them were  cm-10.2-20131220-KonstaKANG-atlas40.zip and cm-11-20140607-UNOFFICIAL-KonstaKANG-atlas40.zip, respectively; the device is a ZTE Blade III (baseband version ICS_P772N10V1.0.0B12, everything else in the `about phone` screen is probably the image talking anyway).
 
is there anything more i can provide to find the cause of this, or somewhere i can look into?
 
thanks for providing cyanogenmod sources+images; apart from the cm11/wifi thing, everything works flawlessly for me.

 

edit: it seems i just forgot to do a factory reset both times i flashed the cm11 image; after a factory reset, wifi works. leaving the details around in case someone faces the same issues.

Edited June 25, 2014 by chrysn

[Guest Dionis]

Any news?? Will be updated to 4.4.4??? And can you make 

http://forum.xda-developers.com/showthread.php?t=2397942

Google Stock Package same like this for Zte Blade III ?  Because those package cant be instaled on ZTE Blade 3 because phone doesent have enoght space...

[Guest dexta]

Same problem with waking up phone.. Somethimes i can't answer the call... I think I will go back on 4.4.2. If Konsta don't fix this bug..

[Guest MJonMoDaCo]

 

Any news?? Will be updated to 4.4.4??? And can you make 

http://forum.xda-developers.com/showthread.php?t=2397942

Google Stock Package same like this for Zte Blade III ?  Because those package cant be instaled on ZTE Blade 3 because phone doesent have enoght space...

 

Those are huge!! The smallest, which is probably acceptable on some Blade 3 roms is still 80+MB. Trying to use the 220MB installation is crazy - at least when compared to the Gapps packages in the first post (a relatively svelte 20.4 MB).

 

Same problem with waking up phone.. Somethimes i can't answer the call... I think I will go back on 4.4.2. If Konsta don't fix this bug..

 

I'm sure it will be, as it was working before on CM11, and so is most likely fixable. I can hear him saying something like:

 

You optimize a little somewhere and you break stuff elsewhere. I know what's going on with this.

 

He probably already does.

Edited June 25, 2014 by MJonMoDaCo

[Guest KonstaT]

Any news?? Will be updated to 4.4.4??? And can you make 

http://forum.xda-developers.com/showthread.php?t=2397942

Google Stock Package same like this for Zte Blade III ?  Because those package cant be instaled on ZTE Blade 3 because phone doesent have enoght space...

Like already said, Android 4.4.4 brings nothing new to CM11. OpenSSL vulnerabilities 4.4.4 targeted are already patched in the latest release.

 

There's already a trimmed gapps package in the OP. :o You don't need to put Google apps that you can download from the Play Store to your /system partition.

 

Same problem with waking up phone.. Somethimes i can't answer the call... I think I will go back on 4.4.2. If Konsta don't fix this bug..

Please go and go running all the way back to stock so you don't need to write such stupid posts anymore. Everyone posting "me too" and making some silly threats without any leverage (I give exactly zero f*cks what ROM you use) doesn't help at all! Maybe if I actually got something other than bitching and whining if someone used my ROMs... Total of 10€ I've received in donations this year(!!! - thanks kk75 :D) really doesn't motivate me to continue supporting a device I havent used in ages for anything. In the subject of silly threats, what if I told I'm going to stop doing the work if you don't start paying. :P

 

I'm sure it will be, as it was working before on CM11, and so is most likely fixable. I can hear him saying something like:

 

He probably already does.

There hasn't been any device specific changes in a long time. Please do point out what I've done to break this! Also I've never encountered this issue myself though I'm currently running a day newer build than what was released.

[Guest dexta]

I just said that my phone with this custom rom have bug..

What is problem? I didn't say anything bad for you, or your work..

[Guest MJonMoDaCo]

There hasn't been any device specific changes in a long time. Please do point out what I've done to break this! Also I've never encountered this issue myself though I'm currently running a day newer build than what was released.

 

Quite right... but I had a feeling it was the proximity calibrator again, even though I'd flashed it (with the compatibility patch), and yet it happened again, which hasn't happened before (having trouble waking the phone whilst using it). I have now come to tell you that I've flashed the proxycal.zip instead, and it works again! It's an odd one.I'm not suggesting you broke it, but rather that you'd have a clue as to the reasons why this is happening. I guess I'm mistaken! Sorry.

 

 

Same problem with waking up phone.. Somethimes i can't answer the call... I think I will go back on 4.4.2. If Konsta don't fix this bug..

 

Did you see that?

 

 

*Wonders which thread we had that on...*

 

Nevermind. Flash this in ClockWorkMod Recovery. Reboot and call someone. Smile.

 

 

You already had this problem a few weeks ago. did you get the file? Did you flash it again? You have to do it again too. I find it mighty strange that it's happening on a Blade though! It's normally amongst the Acqua users.

[Guest KonstaT]

I just said that my phone with this custom rom have bug..

What is problem? I didn't say anything bad for you, or your work..

That was the eighth(!!! - I counted) "me too" post on one fricking page. Not a single log has been posted. Use something that works for you and gtfo then. I don't work for you and I don't fix bugs for you!

 

Quite right... but I had a feeling it was the proximity calibrator again, even though I'd flashed it (with the compatibility patch), and yet it happened again, which hasn't happened before (having trouble waking the phone whilst using it). I have now come to tell you that I've flashed the proxycal.zip instead, and it works again! It's an odd one.I'm not suggesting you broke it, but rather that you'd have a clue as to the reasons why this is happening. I guess I'm mistaken! Sorry.

Proximity sensor has nothing to do with device waking from sleep mode.

[Guest Otila]

That was the eighth(!!! - I counted) "me too" post on one fricking page. Not a single log has been posted. Use something that works for you and gtfo then. I don't work for you and I don't fix bugs for you!

 

I posted a log

http://www.modaco.com/topic/367241-devrom76-cyanogenmod-11-android-443/?p=2215753