[ROM] [4.4.2] SlimKat (jordan) [STABLE 4.0] [Weekly 3.85] [Unofficial]

Should I add transparent status bar with the low memory flag enabled?


  • Total voters
    103
  • Poll closed .

Stefano2991

Senior Member
Dec 7, 2013
109
11
0
Sorry for my stupid questions but.....is possible overclok the "slimkat 3.0 stable rom"?? because with areokernel don't work. And what are the difference between 3.0 stable and the newest releases like 3.8 4 ect?? It is better to have a stable rom?
 

Casteleugim

Senior Member
Dec 26, 2013
59
15
0
Bs.As.
Sorry for my stupid questions but.....is possible overclok the "slimkat 3.0 stable rom"?? because with areokernel don't work. And what are the difference between 3.0 stable and the newest releases like 3.8 4 ect?? It is better to have a stable rom?
I don't remember if v.3 can set other values for overclock, but you can try using bootmenu directly. I recommend you that read old post looking for something about.
My experience is newest version have better manage over memory and have more flexibility for customization. I'm really don't sure if newest versions are more stable that v.3. In addition versions 4+ have new other problems you can see.

Enviado desde mi MB526 mediante Tapatalk
 
Last edited:

Proverbs2

Senior Member
Feb 1, 2012
291
319
0
Sorry for my stupid questions but.....is possible overclok the "slimkat 3.0 stable rom"?? because with areokernel don't work. And what are the difference between 3.0 stable and the newest releases like 3.8 4 ect?? It is better to have a stable rom?
As TJKV explained in this post from a few days ago, the "stable" label in this context means that the rom is ported from a stable release from the SlimRoms team. The latest 4.0 build uploaded yesterday is also based on a stable SlimRoms release, but both "Stable 3.0" and "Stable 4.0" have been ported to the Defy in the same way that CM11 has been ported by Quarx, and the porting introduces various bugs.

IMHO, the latest 4.0 build by TJKV is the most stable KitKat rom for the Defy, and I highly recommend it. :good: It still has some of the same bugs as CM11, which are listed here, but it does not have all of those bugs (for example, bug #32 does not exist on TJKV's SlimKat) and as far as I know it does not have any additional bugs besides those on CM11.

In my own experience, the infamous RIL ("telephony layer" reboot) bug is much less common on SlimKat than on CM11, and reboots in general are extremely rare. (I've only experienced them shortly after install, before the phone had a chance to "settle".) Lags and freezes are also less common, probably because SlimKat uses slightly less ram than CM11.
 
Last edited:

stirlitz99

Senior Member
Jun 11, 2012
148
59
48
Budapest
Sorry for my stupid questions but.....is possible overclok the "slimkat 3.0 stable rom"?? because with areokernel don't work. And what are the difference between 3.0 stable and the newest releases like 3.8 4 ect?? It is better to have a stable rom?
I'm on 3.6 ( Slim-mb526-4.4.2.build.3.6-UNOFFICIAL-20140311-0257 )... not fully convinced with the newer versions. Perfectly working, overclocked and undervolted with SetVSel. No FCs, camera is fine, Wi-Fi also, superb on the battery and on the memory. 3.6 is almost perfect.

Minor flaw is that it doesn't charge the battery when the device is OFF. It starts it up, but you can go to Airplane mode if you don't want to be "online"

Read my short review here

Just above that post I had some OCd & undervolted settings that is working perfectly fine FOR ME.
 
Last edited:
  • Like
Reactions: runeupo

Lord_Flaya

Senior Member
Jun 1, 2012
558
121
73
37
Tomelilla
Is there a way to exclude folders from media scan? In cm i just tic a box in folder properties, but i cant find that function in simple explorer. :(

Sent from my MB526 using XDA Premium 4 mobile app
 

Casteleugim

Senior Member
Dec 26, 2013
59
15
0
Bs.As.
I don't remember if v.3 can set other values for overclock, but you can try using bootmenu directly. I recommend you that read old post looking for something about.
My experience is newest version have better manage over memory and have more flexibility for customization. I'm really don't sure if newest versions are more stable that v.3. In addition versions 4+ have new other problems you can see.

Enviado desde mi MB526 mediante Tapatalk
I´m testing build 4 (04.07) since couple days ago and I must to say that is much better that other versions for me.
While we wait for a solution for 720p camera recording, I suggests test Camera ICS+, you can take 840 x 480 (full defy screen) compared to 640 x 480 of rom camera, with acceptable quality.

Enviado desde mi MB526 mediante Tapatalk
 
Last edited:

no_means_no

Senior Member
Mar 18, 2012
244
31
48
Facing the same problem :rolleyes:
In recovery its shows 99% but after booting it shows 14% and then after a reboot it shows 89% :confused:
I flashed the 4.0 from 06.04. and it seemed ok for a couple of days. Then I went to recovery to flash a mod or something, and then the percentage got crazy. Showed either 99% continously or 1%, but always different from what was shown in TWRP. Got back to 3.80 and everything is fine.
Just wanted to let TKJP know, but if there's almost nobody else with this problem it seems not to be a ROM problem...:confused:
 

TJKV

Senior Member
Jun 25, 2011
1,927
2,746
0
I flashed the 4.0 from 06.04. and it seemed ok for a couple of days. Then I went to recovery to flash a mod or something, and then the percentage got crazy. Showed either 99% continously or 1%, but always different from what was shown in TWRP. Got back to 3.80 and everything is fine.
Just wanted to let TKJP know, but if there's almost nobody else with this problem it seems not to be a ROM problem...:confused:
Right click "Raw" over here and save as onto your computer. Put it in /system/etc/init.d on your phone, set the same permissions as the other files in there and reboot, charge fully, reboot and see if it works

Same for @souviktherocker
 

no_means_no

Senior Member
Mar 18, 2012
244
31
48
Right click "Raw" over here and save as onto your computer. Put it in /system/etc/init.d on your phone, set the same permissions as the other files in there and reboot, charge fully, reboot and see if it works

Same for @souviktherocker
Thanks for all your effort. I'll try that later and report!

and sorry @TJKV for spelling your nickname so terribly wrong ;)
 
Last edited:

Proverbs2

Senior Member
Feb 1, 2012
291
319
0
@TJKV, I noticed that this fix isn't yet included on your GitHub.

When you have time, it would be great if you could add that fix so that the phone reboots normally (instead of booting into recovery) after a BP panic. I haven't been experiencing any such reboots on your rom anyway, but just in case... ;)
 

TJKV

Senior Member
Jun 25, 2011
1,927
2,746
0
@TJKV, I noticed that this fix isn't yet included on your GitHub.

When you have time, it would be great if you could add that fix so that the phone reboots normally (instead of booting into recovery) after a BP panic. I haven't been experiencing any such reboots on your rom anyway, but just in case... ;)
Yes that is from yesterday, I haven't had time this week yet. I usually merge all repos (quarx and slim) just before building, then sync+build and go to bed, next morning upload if it has built succesfully or fix any errors and let it build again while I head to college...