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

[Guest KonstaT]

I posted a log

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

Is that even the same issue? Other people (nine of them) are saying screen remains black. You're saying it doesn't accept input. Is everyone with this issue using pin/pattern locks? More logs? Posting "me too" just clutters the thread which means you're part of the problem - not part of the solution.

[Guest MJonMoDaCo]

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

 

While this may be true, it's the thing that has fixed the problem with the phone not being answerable. I don't know what causes it, but flashing the patch seems to have fixed it, even though it's now twice. I couldn't tell you what caused that without reproducing the problem. I'm going to have issues since it's not happening anymore, and what I did. Considering I was one of the 8 (or 9), It thought it'd be worth saying so.

[Guest Otila]

Is that even the same issue? Other people (nine of them) are saying screen remains black. You're saying it doesn't accept input. Is everyone with this issue using pin/pattern locks? More logs? Posting "me too" just clutters the thread which means you're part of the problem - not part of the solution.

 

Hmm, it does not remain black. But I can use emergency dialer! I just tried, I was able to trigger the bug by sleeping/waking up the device three times. 20140521 did not have this bug.

Also, when going to sleep, I get these:

06-26 20:16:42.847 E/rmt_storage(  121): write_log_file: [MyTag]open: fd=-1
06-26 20:16:42.847 E/rmt_storage(  121): block rmt_storage client thread
06-26 20:16:49.674 I/PowerManagerService(  501): Going to sleep by user request...
06-26 20:16:50.104 D/SurfaceFlinger(  108): Screen released, type=0 flinger=0x41149450
06-26 20:16:50.715 I/HK/LatinKeyboardBaseView(  994): closing org.pocketworkstation.pckeyboard.LatinKeyboardView{41c4e440 V.ED.... ......ID 0,0-480,256 #7f07000a app:id/LatinkeyboardBaseView}
06-26 20:16:50.775 W/View    (  870): requestLayout() improperly called by android.widget.TextClock{41e67208 V.ED.... ......ID 0,0-106,129 #7f0b0013 app:id/clock1_regular} during layout: running second layout pass
06-26 20:16:50.775 W/View    (  870): requestLayout() improperly called by android.widget.TextClock{41e9eb20 V.ED.... ......ID 106,0-229,129 #7f0b0014 app:id/clock2_regular} during layout: running second layout pass
06-26 20:16:50.775 W/View    (  870): requestLayout() improperly called by android.widget.TextClock{41f03bf8 V.ED.... ......ID 86,1-183,26 #7f0b0018 app:id/date_bold} during layout: running second layout pass
06-26 20:16:50.775 W/View    (  870): requestLayout() improperly called by android.widget.TextView{41e68698 V.ED.... ......ID 225,1-293,26 #7f0b001b app:id/nextAlarm_bold} during layout: running second layout pass
06-26 20:16:50.775 I/ActivityManager(  501): Delay finish: com.cyanogenmod.lockclock/.ClockWidgetProvider
06-26 20:16:50.785 W/View    (  870): requestLayout() improperly called by android.widget.TextView{424b47d0 V.ED.... ......ID 69,6-133,35 #7f0b0021 app:id/weather_city} during layout: running second layout pass
06-26 20:16:50.785 W/View    (  870): requestLayout() improperly called by android.widget.TextView{425da608 V.ED.... ......ID 104,35-133,37 #7f0b0027 app:id/weather_condition} during layout: running second layout pass
06-26 20:16:50.785 W/View    (  870): requestLayout() improperly called by android.widget.TextView{42658fb0 V.ED.... ......ID 78,37-133,37 #7f0b0022 app:id/update_time} during layout: running second layout pass
06-26 20:16:50.785 W/View    (  870): requestLayout() improperly called by android.widget.TextView{41e6aa00 V.ED.... ......ID 1,0-65,41 #7f0b0024 app:id/weather_temp} during layout: running second layout pass
06-26 20:16:50.785 W/View    (  870): requestLayout() improperly called by android.widget.TextView{424f8fb8 V.ED.... ......ID 5,43-61,43 #7f0b0026 app:id/weather_low_high} during layout: running second layout pass
06-26 20:16:50.865 E/wpa_supplicant( 6232): wpa_driver_nl80211_driver_cmd: failed to issue private commands
06-26 20:16:50.875 I/HK/LatinKeyboardBaseView(  994): closing org.pocketworkstation.pckeyboard.LatinKeyboardView{41c4e440 V.ED.... ......ID 0,0-480,256 #7f07000a app:id/LatinkeyboardBaseView}
06-26 20:16:51.025 I/ActivityManager(  501): Resuming delayed broadcast

[Guest zeploit]

images not appearing in the new internet browser

[Guest chrysn]

images not appearing in the new internet browser

i've experienced that as well; to be precise, when the browser is directed to show one image, it shows it as white or only partially. (in the tab preview, it is shown correctly though). it is very unlikely that such an issue is stems from KonstaT's device specific adaptions, so the better place to look for a solution are android generic support pages (admittedly, i didn't find a clean bug report either). it seems that a google productforum post [1] is about the problem and claims to have solved it, but they failed to link to a version or commit (or even piece of software; as the tint browser is affected too, it might be a graphics library issue) that did.

[1] quoting: "Update on May 2: We have implemented a fix for this issue, so it should be working. If it does not, try restarting your phone or clearing cache and cookies. Thank you for your patience!"

Edited June 27, 2014 by chrysn

[Guest KonstaT]

images not appearing in the new internet browser

Thank you very much for this next to useless 'issue report'. WTF is this even supposed to mean? What images? Where? What _new_ internet browser? There's no such thing... Please provide exact steps to reproduce this issue and attach appropriate logs (logcat, dmesg).

 

Next time I see a post that says nothing else than "X doesn't work", I'm seriously going trash my device. :P

 

i've experienced that as well; to be precise, when the browser is directed to show one image, it shows it as white or only partially. (in the tab preview, it is shown correctly though). it is very unlikely that such an issue is stems from KonstaT's device specific adaptions, so the better place to look for a solution are android generic support pages (admittedly, i didn't find a clean bug report either). it seems that a google productforum post [1] is about the problem and claims to have solved it, but they failed to link to a version or commit (or even piece of software; as the tint browser is affected too, it might be a graphics library issue) that did.

[1] quoting: "Update on May 2: We have implemented a fix for this issue, so it should be working. If it does not, try restarting your phone or clearing cache and cookies. Thank you for your patience!"

This is not a Nexus device so you shouldn't post anything to Android bug tracker. This is not an official CyanogenMod device so you shouldn't post anything to CyanogenMod bug tracker. And we're not even using the web rendering engine we're supposed to...

 

Android 4.4 KitKat introduced a new Chromium webview that doesn't work with our ancient display drivers. That's why we've forward ported classic webview that was used in previous Android versions. Android 4.4.3 introduced bunch of updates to Chromium webview and it also broke the old webkit. There were some quick fixes by anroidarmv6 guys to fix build but it's likely not quite there yet. I've been waiting for Qualcomm to update it because it was initially their implementation for KitKat anyway (https://www.codeaurora.org/cgit/quic/la/platform/external/webkit/). No sign of it yet though.

 

I could reproduce similar issues with image rendering on another device while using classic webview. I never saw it on my Blade III though. I think I hunted it down to some change between 8th and 11th june, but it might have broken all along since 4.4.3.

[Guest dubstep774]

It's official there is a new android version (Andtoid L) in the making. It is still at a developer stage but it's out there (It hasn't got a version number yet)

A tech youtuber(MKBHD) who is at Google I/O did a review on some of the new Android L features. Hope they get implimented here too :p

[Guest deki032]

Hi again to all...after instalation 7.6 version my phone clock start to late 10-15 min during 24 hours and also my radio during the listening turn off,I must pull off hedphones to start it again..Somebody with same problem??Solutions??Thanks..

[Guest Dionis]

KonstaT any news?? Going to be upgraded to Android 5.0L or not??

[Guest Saky]

Come on...we already have fully working android 4.4 kit kat on our device thanks to KonstaT! Most of better and more expensive devices will never had android 4.4 anyway...so stop asking for android 5.0 or whatever...Our device is old and hardware limited so asking something like this makes no sense at all if you ask me! :)

Still waiting for possible "deep sleep" bug so I can post a log...but damn phone...all working just fine now :D

Edited July 1, 2014 by Saky

[Guest KonstaT]

KonstaT any news?? Going to be upgraded to Android 5.0L or not??

How about you ask that 4-5 months later when L-version (and it's source code) is released...

http://www.cyanogenmod.org/blog/the-l-is-for-later

[Guest zeka111]

where is transparent status bar

[Guest KonstaT]

where is transparent status bar

FAQ, third post!

[Guest KonstaT]

New build. Mostly untested as usual these days. No major device specific changes/improvements, just keeping up with upstream.

 

cm-11-20140702-UNOFFICIAL-KonstaKANG-atlas40.zip

https://www.mediafire.com/?1yzhjbd7xc1nel8

md5:cee0dec8b0c61fbf56741d03bd210f73

 

-Android 4.4.4

-Heads up notifications (merged)

-Searchable settings (merged)

[Guest Saky]

Wohooo thats a suprise  :D Thanks KonstaT...downloading right now! Will post some results soon  ;) I just knew you are "coocking" something! Respect!

[Guest dubstep774]

I already installed it just to find out those dumb badword at google don't support 4.4.4! WTF? I got a message that this version is unsupported by google play services and my play store along with vending.apk from /system/app dissapeared. It's not your fault KonstaT bit I'm reverting back to 4.4.3 untill those google morons fugure things out >:( (I Did play around with the searchable settings though. It was fun)

[Guest Otila]

kitkat 4.4 seems to have this bug

https://code.google.com/p/android/issues/detail?id=63738

 

these from my blade iii 20140702:
 

07-02 19:40:54.904 I/PowerManagerService(  517): Going to sleep by user request...
07-02 19:40:55.404 D/SurfaceFlinger(  108): Screen released, type=0 flinger=0x40e5e450
07-02 19:40:56.455 E/libgenlock( 1452): perform_lock_unlock_operation: GENLOCK_IOC_DREADLOCK failed (lockType0x1,err=Connection timed out fd=89)
07-02 19:40:56.455 E/gralloc ( 1452): gralloc_lock: genlock_lock_buffer (lockType=0x2) failed
07-02 19:40:56.455 W/GraphicBufferMapper( 1452): lock(...) failed -22 (Invalid argument)
07-02 19:40:56.455 W/Surface ( 1452): failed locking buffer (handle = 0x51e307f8)
07-02 19:40:56.455 E/ViewRootImpl( 1452): Could not lock surface
07-02 19:40:56.455 E/ViewRootImpl( 1452): java.lang.IllegalArgumentException
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Surface.nativeLockCanvas(Native Method)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Surface.lockCanvas(Surface.java:254)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2431)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.draw(ViewRootImpl.java:2405)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2249)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1879)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5600)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Choreographer.doCallbacks(Choreographer.java:574)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Choreographer.doFrame(Choreographer.java:544)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.os.Handler.handleCallback(Handler.java:733)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.os.Handler.dispatchMessage(Handler.java:95)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.os.Looper.loop(Looper.java:136)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at android.app.ActivityThread.main(ActivityThread.java:5140)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at java.lang.reflect.Method.invokeNative(Native Method)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at java.lang.reflect.Method.invoke(Method.java:515)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
07-02 19:40:56.455 E/ViewRootImpl( 1452): 	at dalvik.system.NativeStart.main(Native Method)
07-02 19:40:56.785 D/dalvikvm(  517): JIT code cache reset in 5 ms (1535948 bytes 1/0)
07-02 19:40:56.926 I/ActivityManager(  517): Delay finish: com.cyanogenmod.lockclock/.ClockWidgetProvider
07-02 19:40:57.196 I/HK/LatinKeyboardBaseView( 1588): closing org.pocketworkstation.pckeyboard.LatinKeyboardView{41af3fd0 V.ED.... ......I. 0,0-480,256 #7f07000a app:id/LatinkeyboardBaseView}
07-02 19:40:57.216 I/Choreographer( 1452): Skipped 39 frames!  The application may be doing too much work on its main thread.
07-02 19:40:57.256 W/View    ( 1452): requestLayout() improperly called by android.widget.TextClock{422dc9a8 V.ED.... ......ID 0,0-106,129 #7f0b0013 app:id/clock1_regular} during layout: running second layout pass
07-02 19:40:57.256 W/View    ( 1452): requestLayout() improperly called by android.widget.TextClock{4232d8d8 V.ED.... ......ID 106,0-229,129 #7f0b0014 app:id/clock2_regular} during layout: running second layout pass
07-02 19:40:57.256 W/View    ( 1452): requestLayout() improperly called by android.widget.TextClock{423d61b0 V.ED.... ......ID 89,1-175,26 #7f0b0018 app:id/date_bold} during layout: running second layout pass
07-02 19:40:57.256 W/View    ( 1452): requestLayout() improperly called by android.widget.TextView{42193970 V.ED.... ......ID 217,1-291,26 #7f0b001b app:id/nextAlarm_bold} during layout: running second layout pass
07-02 19:40:57.276 E/BufferQueue(  108): [Keyguard] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
07-02 19:40:57.276 E/Surface ( 1452): dequeueBuffer failed (Invalid argument)
07-02 19:40:57.276 E/ViewRootImpl( 1452): Could not lock surface
07-02 19:40:57.276 E/ViewRootImpl( 1452): java.lang.IllegalArgumentException
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Surface.nativeLockCanvas(Native Method)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Surface.lockCanvas(Surface.java:254)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2431)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.draw(ViewRootImpl.java:2405)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2249)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1879)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5600)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Choreographer.doCallbacks(Choreographer.java:574)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Choreographer.doFrame(Choreographer.java:544)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.os.Handler.handleCallback(Handler.java:733)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.os.Handler.dispatchMessage(Handler.java:95)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.os.Looper.loop(Looper.java:136)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at android.app.ActivityThread.main(ActivityThread.java:5140)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at java.lang.reflect.Method.invokeNative(Native Method)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at java.lang.reflect.Method.invoke(Method.java:515)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
07-02 19:40:57.276 E/ViewRootImpl( 1452): 	at dalvik.system.NativeStart.main(Native Method)
07-02 19:40:57.316 E/wpa_supplicant( 1297): wpa_driver_nl80211_driver_cmd: failed to issue private commands
07-02 19:40:57.326 I/HK/LatinKeyboardBaseView( 1588): closing org.pocketworkstation.pckeyboard.LatinKeyboardView{41af3fd0 V.ED.... ......ID 0,0-480,256 #7f07000a app:id/LatinkeyboardBaseView}
07-02 19:41:34.001 I/wpa_supplicant( 1297): rfkill: WLAN unblocked

[Guest KonstaT]

I already installed it just to find out those dumb badword at google don't support 4.4.4! WTF? I got a message that this version is unsupported by google play services and my play store along with vending.apk from /system/app dissapeared. It's not your fault KonstaT bit I'm reverting back to 4.4.3 untill those google morons fugure things out > :( (I Did play around with the searchable settings though. It was fun)

Gapps from the OP? Play store works just fine for me and Google Play Services updated itself to the latest version.

 

/system is mounted read-only, nothing can just disappear...

[Guest Jowat]

Delete this Post

Edited November 9, 2014 by Jowat

[Guest dubstep774]

 

Gapps from the OP? Play store works just fine for me and Google Play Services updated itself to the latest version.

 

/system is mounted read-only, nothing can just disappear...

 

I believe what I saw (more what I didn't see) and that was vending.apk missing from /system/app

IDK what was te problem but reinstalling the 4.4.3 gapps package fixed it.

 

I did screw around with the protected apps function. ended up blocking my ES file explorer and I can't get it to unblock it, but I'll fugure that out some how :blink:

Eddit: Reinstalled the ROM (and the gapps to make sure the play store didn't dissapear again) and got ES unblocked! YAY :D

Edited July 2, 2014 by dubstep774

[Guest KonstaT]

Hey Dudes, I have a question, is that file really important for the installation: "gapps-kk-core-20140608.zip". It only contains the gapps package and some essential Google services. But I don't want to have this annoying google services. So it is possible to install 4.4.4 without "gapps-kk-core-20140608.zip"?

Yes, it is possible to use CyanogenMod without Google apps package if that's what you want. Not exactly sure why you've chosen Android in that case. All Google apps (Gmail, Maps, etc) depend on the Google services framework as well as increasing number of third party Android apps.

 

I believe what I saw (more what I didn't see) and that was vending.apk missing from /system/app

IDK what was te problem but reinstalling the 4.4.3 gapps package fixed it.

It was probably never there. ;) Play Store is /system/priv-app/Phonesky.apk.

[Guest dubstep774]

It was probably never there. ;) Play Store is /system/priv-app/Phonesky.apk.

That may be true IDK all I care about now is that I have 4.4.4 and ultimate braging rights among my friends for having the latest Android :P

[Guest Saky]

Play store working just fine here too! Google play services updates automatically. No problems at all! One small bug so far...notification led blink ok on new sms but stays on (not blinking but stays on) even after reading the message. Not a big deal anyway  ^_^

One more thing I noticed...there is no Google Chrome on Google Play Store, only beta version show up! But I guess recent version of Chrome is not compatible with android 4.4.4 just yet.

So far everything works, maybe a placebo effect but seems a bit faster also  :ph34r:

[Guest umr1975]

Thanks, KonstaT.

Good job

[Guest alekcacko]

Great job, the rom is good for me.