[ROM][4.4.4][ALL] SlimKat 9.1 UNOFFICIAL [29/12/2015]

[Guest hvdh]

Then there is this weird chrome bug that when pressing some/most links, a red border on the screen blinks.

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

[Guest hvdh]

Then there is this weird chrome bug that when pressing some/most links, a red border on the screen blinks.

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

[Guest hvdh]

Then there is this weird chrome bug that when pressing some/most links, a red border on the screen blinks.

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

[Guest hvdh]

Then there is this weird chrome bug that when pressing some/most links, a red border on the screen blinks.

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

[Guest xSeed]

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

I see. But it's already unchecked by default. Or do I need to check it to disable? Anyways, I checked then uncheked it for now. I'll tell you if it worked. Thanks.

[Guest xSeed]

Disable Options / Developer Options / [Monitoring] "Strict Mode enabled".
The red bars then indicate that the UI thread is blocked for some time.

Edit: Now it's getting even weirder. Blinks also in the app drawer whether Strict mode is checked or unchecked. 

Edited September 15, 2015 by xSeed
Double post and update.

[Guest Mr Voland]

Edit: Now it's getting even weirder. Blinks also in the app drawer whether Strict mode is checked or unchecked. 

I had the same problem and I couldn't find where is problem, you  need to deal with it, hey did u tried disabling developer options, not smart idea but might help xD

[Guest xSeed]

I had the same problem and I couldn't find where is problem, you  need to deal with it, hey did u tried disabling developer options, not smart idea but might help xD

Well I also thought about that but I know it would disable other more important stuff. So, yes, not really smart idea. It's a no go for me. :D Let's wait for another work around. I'll try figuring it out tomorrow too.

[Guest soul_0830]

I asked for a stage freight patch but what I got was a totally awesome Rom

Looks great, works like a charm and very happy with the latest build. 

Even though its having minor bugs here and there; I'm really happy with the new ROM.

 

Thank You Chil360 !!!

[Guest Mr Voland]

NEED HELP 

In camera I swiched picture format to raw and now I cant even open camera, it shows me message 'camera has stoped' same thing after reboot, any solution except factory reset?

[Guest Mr Voland]

Double post O.o

Edited September 16, 2015 by Mr Voland

[Guest Jairus1998]

Wipe camera data by going into setting or using any app like titanium  backup or etc.. 

 

[Guest Mr Voland]

Wipe camera data by going into setting or using any app like titanium  backup or etc.. 

 

I've fixed the problem allredy, but thaks anyway

[Guest keishi16]

Is the 'Display-CAF' rom for daily use?

How does it goes with UltraKernel?

Thanks.

[Guest xSeed]

How does it goes with UltraKernel?

 

Only legacy

[Guest xSeed]

[ Removed duplicate post ]

Edited September 17, 2015 by xSeed
double

[Guest UliZ]

Is the 'Display-CAF' rom for daily use?

I have it in daily use for 3 days now, mostly for office/business work.

Everything works fine and reliable so far, deep sleep problem seems to be solved.

Just some minor graphic blemishes, like when screen content changes, sometimes for a short second letters appear as black squares before changing to letters again.

Looks like CPU is shortly overstressed when this happens. Maybe this could be optimized by changing any settings, but I have no idea...

Edited September 18, 2015 by UliZ

[Guest UliZ]

(double post)

Edited September 17, 2015 by UliZ
double post

[Guest Kiodo1981]

Camera FC when I take a picture, reboot necessary.  Wipe didn't solve it.

Video works fine.

Casually when I turn it on, my MP3 ringote is replaced by an unknown ringtone.

[Guest hvdh]

Does the ART work?

No, enabling ART brings the device in a boot loop.

E/art     ( 4593): /system/bin/dex2oat failed: /system/bin/dex2oat [...]
F/art     ( 4593): art/runtime/gc/space/image_space.cc:148] Check failed: GenerateImage(image_file_name) Failed to generate image: /data/dalvik-cache/system@[email protected]

[Guest hvdh]

Does the ART work?

No, enabling ART brings the device in a boot loop.

E/art     ( 4593): /system/bin/dex2oat failed: /system/bin/dex2oat [...]
F/art     ( 4593): art/runtime/gc/space/image_space.cc:148] Check failed: GenerateImage(image_file_name) Failed to generate image: /data/dalvik-cache/system@[email protected]

[Guest jortizbayona]

Any tool to fix the camera? : D

good ROM

[Guest]

Does the ART work?

No, enabling ART brings the device in a boot loop.

E/art     ( 4593): /system/bin/dex2oat failed: /system/bin/dex2oat [...]
F/art     ( 4593): art/runtime/gc/space/image_space.cc:148] Check failed: GenerateImage(image_file_name) Failed to generate image: /data/dalvik-cache/system@[email protected]

Try to add this in build.prop (or change value) then switch from Dalvik to ART 

dalvik.vm.dexopt-data-only=0

 

[Guest hvdh]

Try to add this in build.prop (or change value) then switch from Dalvik to ART
dalvik.vm.dexopt-data-only=0

Doesn't help, same crash. The stack points to some memory allocation issue.
Maybe I look into that at some point. On the other hand, i'll get my new phone tomorrow morning.

libart.so (art::Runtime::Abort()+156)
libart.so (art::LogMessage::~LogMessage()+672)
libart.so (art::gc::space::ImageSpace::Create()+198)
libart.so (art::gc::Heap::Heap(..)+588)
libart.so (art::Runtime::Init()
libart.so (art::Runtime::Create()
libart.so (JNI_CreateJavaVM+880)

[Guest hvdh]

Try to add this in build.prop (or change value) then switch from Dalvik to ART
dalvik.vm.dexopt-data-only=0

Doesn't help, same crash. The stack points to some memory allocation issue.
Maybe I look into that at some point. On the other hand, i'll get my new phone tomorrow morning.

libart.so (art::Runtime::Abort()+156)
libart.so (art::LogMessage::~LogMessage()+672)
libart.so (art::gc::space::ImageSpace::Create()+198)
libart.so (art::gc::Heap::Heap(..)+588)
libart.so (art::Runtime::Init()
libart.so (art::Runtime::Create()
libart.so (JNI_CreateJavaVM+880)