186 replies to this topic

[cazad]

PaulMilbank, on 22 January 2013 - 08:20 AM, said:

You need to enable and set it up with a script. It will not be enabled just because it is in the kernel.

Could you provide a working script, because I can't get zRam enabled on #11 with mine ?

[PaulMilbank]

What have you tried?

[cazad]

Quote

#!/system/bin/sh

DISK_SIZE=128

echo 1 > /sys/block/zram0/reset

echo$(($DISK_SIZE*1024*1024)) > /sys/block/zram0/disksize

mknod /dev/zram0 b 253 0
mkswap /dev/zram0

swapon /dev/zram0

exit 0

and

Quote

echo 104857600 > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0

Edited by cazad, 26 January 2013 - 11:07 PM.

[PaulMilbank]

OK, #13 kernel is up now. Try out the same scripts as above. The scripts seem to be enabling a swap area compressed in ram (zram) and that side would have worked. I had not enabled swap though so it would not have enabled the kernel to make use of the swap area. I have enabled swap now as well as a couple of other small tweaks. Hopefully that should do it.

[Pain_Deluxe]

Testing it out now on b944 infusion

[cazad]

It works now, thanks!

[PaulMilbank]

Cheers man, glad to finally have it sorted. @pain_deluxe, let me know how you get on with b944 based infusion b06.

[Pain_Deluxe]

Must test again...

the most annoying on stock roms are stucking on games sometimes.(with your old kernel)

[Pain_Deluxe]

PaulMilbank, on 29 January 2013 - 07:14 PM, said:

Cheers man, glad to finally have it sorted. @pain_deluxe, let me know how you get on with b944 based infusion b06.

PaulM #13(@1,19Ghz) Kernel and Supremacy Trilogy Script.
Games now runs smooth as before. But now its lagfree (Got with old kernel and NO scripts  hard lags sometimes (e.g Tempelrun 1+2)
On Batterylife i have no idea.But i mean no difference.

[Combat Gerbil]

Release 19 seems the quickest on My phone, can't get a stable overclock out of any of them.. Antutu 3684+- on 19...and only 2965+- on newer releases. Quite a difference there..

[kyan31]

Combat Gerbil, on 01 February 2013 - 08:42 PM, said:

Release 19 seems the quickest on My phone, can't get a stable overclock out of any of them.. Antutu 3684+- on 19...and only 2965+- on newer releases. Quite a difference there..

I agree, when using lightning ROM, release #19 keeps the phone running smooth. The newer releases made the phone actually lag quite alot, for example in the launcher.

To be honest, release #19 works so well, so I don't really need any updates.

[PaulMilbank]

Yeah, I think I am going to remove wheatley governor from the next one. I had to enable an include in the defconfig and it works great with wheatley but every other governor seems to suffer a lack of smoothness.

[Pain_Deluxe]

Have no lag with smartass on launcher.

wtf is wheathley ( found it)

Yeah you should remove it. On smartassV2 and stock Clock everthing is sloppery (Lagging scrolling and launcher)

But @ 300-1,19Ghz everything is fine.

and wtf? 300-600mhz(smartassv2= no lags @ homescreen and scrolling ?`only if i select stock clocks it lags.

ony wheathley the stock clocks lag , too.

Edited by Pain_Deluxe, 03 February 2013 - 08:09 PM.

[PaulMilbank]

OOPS:
Yeah, wheatley was an oops. #14 is up with wheatley removed and cpu idle commented back out of the defconfig. Smoothness is back.

Wheatley explanation from the dev:
http://forum.xda-dev...52&postcount=56
and Wheatley explanation:
http://www.alliance-...nors-explained/

Quote

So with the new highly-flexible Wheatley governor one can have the best of both worlds.
This governor is only available on multi-core devices.

No wonder it messed things up on our single core phone!.

[Pain_Deluxe]

hm, standard gov. lagfree?


damn i restored CM9 Kernel . 3G works but rom was lagging:D

[Pain_Deluxe]

hm 14 is a bit laggy to on scrolling.

just reinstall infusion with your kernel. lets see....

Lagfree governor

'lagfree' - this driver is rather similar to the 'ondemand'
governor both in its source code and its purpose, the difference is
its optimization for better suitability in a battery powered
environment. The frequency is gracefully increased and decreased
rather than jumping to 100% when speed is required.

So its good with battery too?

Edited by Pain_Deluxe, 04 February 2013 - 03:19 PM.

[unaszplodrmann]

Could've been worse; it might've been Governor Wheatley. Arnie was quite weird enough a choice...

I got my G300 back recently, so I'm going to start having a play again. What weirdness did the init I gave you cause?

Edited by unaszplodrmann, 04 February 2013 - 08:25 PM.

[PaulMilbank]

Once I changed to MTP, I could not get mass storage mode back. Also It mixed my sdcards up if I remember correctly. Would you mind giving a tutorial of how you made it? Would be keen to see what changes you made and see how you made it.

[unaszplodrmann]

Ah, really? Thats interesting because it sheds some light onto the modifications Huawei have made to the CAF source. The ROM I'm working on is based on B952 but has most of their flakey, semi-functional "value added" features removed; it just provides an AOSP-like user environment (and will eventually include LVM, hopefully)... Hence I didn't come across those issues... Huawei's dodgy feature hacks are unfixable without even uglier kludges, so I disabled/removed them instead.

Unfortunately, it sounds like fixing persisent MTP for stock ROMsin general would be a faff. Working with the sources from CAF, you'd need to replicate the behaviour of Huawei's init in order to support their hacked up vold... I just added a few property/id combinations to the property_perms array in system/core/init/property_service.c to get bluetooth working, like so:

{ "service.brcm.bt.", AID_BLUETOOTH, 0 },
{ "service.brcm.bt.", AID_SYSTEM, 0 },
{ "persist.service.brcm.bt.", AID_BLUETOOTH, 0 },

[PaulMilbank]

Great job man. Would love a rom that is closer to aosp source. Hope you manage to get all of Huawei's kludges fixed.