• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[Kernel] 308 Kernel for official ICS roms, Updated 07/02/2013

190 posts in this topic

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted

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.

1

Share this post


Link to post
Share on other sites

Posted (edited)

Have no lag with smartass on launcher.

wtf is wheathley :D ( 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
0

Share this post


Link to post
Share on other sites

Posted

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-developers.com/showpost.php?p=21638852&postcount=56

and Wheatley explanation:

http://www.alliance-rom.com/community/wiki/governors-explained/

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!.

0

Share this post


Link to post
Share on other sites

Posted

hm, standard gov. lagfree?

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

0

Share this post


Link to post
Share on other sites

Posted (edited)

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
0

Share this post


Link to post
Share on other sites

Posted (edited)

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
0

Share this post


Link to post
Share on other sites

Posted

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.

0

Share this post


Link to post
Share on other sites

Posted

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 },

0

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Posted (edited)

No chance that I'll be able to make Huawei's features work properly... Maybe if Android were GPL rather than Apache licensed, and I had the knowledge required already... But even then, stuff like the "ICS Double Sdcard" feature is just plain wrong by design, and as such, completely fubar. The CyanogenMod team could teach Huawei a thing or two about what Huawei like to called "professional tuning". Huawei's kittens were malformed from birth and though it seemed unfortunate, I killed them in name of attempting to make the software they've published fit for purpose. ;)

There are some thing I've found that could be fixed which I lack the skills to tackle. High resolution video recording is a good example. As far as I can tell, the limiting factor is the crappy sensors drivers from CAF; they don't offer different resolutions for preview output and recording.

Edited by unaszplodrmann
0

Share this post


Link to post
Share on other sites

Posted

Nice. Yeah, Huawei make some really strange decisions with software. It is really odd to me. There are a couple of changes in the kernel to make hi res video work too. The board config needs more memory added to it but we have so little free, It may not be worth allocating a big chunk to a feature that may or may not be supported.

0

Share this post


Link to post
Share on other sites

Posted

Why is facebook so slow is it from the phone or the application

0

Share this post


Link to post
Share on other sites

Posted

And why are you asking that in this thread??

0

Share this post


Link to post
Share on other sites

Posted

Is this your release Paul? Or is it just #19 of the OLD kernel?

0

Share this post


Link to post
Share on other sites

Posted

PaulMilbank, does the new #15 support init.d? I only ask because i'm using it on infusion and i don't find the etc/init.d data

I wish to use the supremacy trilogy v3 script and i think is not installing cause need the init.d

0

Share this post


Link to post
Share on other sites

Posted

Should do, I included init.d initialization in the kernel ramdisk so if infusion does not have an etc/init.d folder, just add one and then put your scripts into it.

0

Share this post


Link to post
Share on other sites

Posted

Oh ok, and also, i saw in the slim rom that #19 test kernel is better than #15? How's that? lol

0

Share this post


Link to post
Share on other sites

Posted

Some people still prefer it. I feel that #15 is better personally as it has working swap and zram Which I could not get working before I broke my build environment for the #19 kernel, and a much cleaner source. I personally think some of the memory changes I coded into the kernel caused force closes, but they did help alleviate some of the low memory problems. It is just which one you prefer, they are both available to use, test and play with and all source is on github should anyone feel inclined to make changes.

0

Share this post


Link to post
Share on other sites

Posted

So i did what you said, created the init.d folder and now i have there the script :)

0

Share this post


Link to post
Share on other sites

Posted (edited)

"install zip from sdcard" missing , im using clockworkmod's rom manager, some help?

i get only this : http://i.imgur.com/VqPvt.jpg

Edited by exerullz
0

Share this post


Link to post
Share on other sites

Posted (edited)

it's stock recovery, it not have install zip from sdcard.

Edited by ficko98
0

Share this post


Link to post
Share on other sites

Posted

so what shall i do?

0

Share this post


Link to post
Share on other sites

Posted

instal cwm or twrp.

0

Share this post


Link to post
Share on other sites

Posted (edited)

what governor should i use for 480 min 1.19 max ?

what's the difference between smartassv2 and conservative?

or better: which is the best governor for both gaming performance and battery save?

Edited by exerullz
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.