[i9300][2014/JUN/10][AOSP] Yank555.lu kernel v1.7a-beta3

[Luca.Brasi]

''mixed with bits of ROM side handling because of SlimBean 4.3 build 1.4''
My english not enough for this sentences :p What's the point? Are you prefer and suggest slimbean 4.3 build 1.4 for the best usage? What are you talking about build 1.4

[yank555]

''mixed with bits of ROM side handling because of SlimBean 4.3 build 1.4''
My english not enough for this sentences :p What's the point? Are you prefer and suggest slimbean 4.3 build 1.4 for the best usage? What are you talking about build 1.4

No no

That only means that SlimBean have merged stuff from newer CM using new CM LED controlling philisophy, so I had to make some more tricky patches in the kernel to deal with it.

Use the latest, that should be the best

JP.

[yank555]

OK guys, my first OMNI 4.4 kernel is cooking (aka. compiling) right now ... fingers crossed

JP.

[sherlock5545]

How stable is this OmniROM 4.4 build, though? I'm not sure if I'd like to stay on 4.3.1 or move on.

Sent from my GT-I9300

[yank555]

Kernel is working just fine, that's the god news

I'd still wait before moving to 4.4, looks a bit too experimental for now... (this is from playing with it for 5 minutes, so don't take my work for it !).

JP.

[yank555]

OMNI Beta Kernel Release

Changelog OMNI-4.4 v1.6g-beta1 (compared to CM10.2 v1.6g) :

• updated mali r3p2 drivers from Update 12 source drop (GPU OC is lost for now !)
• removed GPU OC settings from Aroma and script generator
• ramfs : updated to OMNI nightly 20131115

• Yank555.lu-OMNI-4.4-v1.6g-beta1.zip

  (MD5 037e82b0f36078ae76bbd648391007de)

  (8.53 MiB) Downloaded 736 times

[yank555]

Just a small update, in case you wondered what the new Aroma settings included in v1.6g were all about :

CPU Idle Mode :

1. IDLE - Clock is gated but power on CPU core remains (static power consumption still active)
2. AFTR - Clock is gated, power on CPU cores removed and L2 cache power remains. Static power consumption mostly eliminated.
3. LPA - Cache power removed.
4. AFTR or LPA cannot be entered if second core is active.

Multicore power saving :

Significance: Increases multi-core awareness!?

Sched_mc aims to schedule tasks between multiple cores in the CPU. Sched_mc can be a) OFF (value 0), b) load balance (value 2) the cores by keeping the load even between them or c) power-save balance (value 1) by loading first core until it's 100% loaded. Hotplugging does load balancing already by taking care of thresholds, run queues, process priorities, cut-off frequency, etc. So there's no use of sched_mc = 1. Powersave balancing which overloads first core will increase the time to relieve first core (as compared to same task balanced between both the cores). This will cause delay to hit deep-idle states, since only first core can enter AFTR/LPA states.
Disable sched_mc. There could be only one situation where load balancing or weird-overloading of first core can be useful - when we use dual core mode. Sched_mc is valid only when both cores are online. If someone uses dual-core mode sched_mc is worth a try to handle task-loads across cores.

Source

[MilTora]

Great work with the OMNI 4.4 kernel, device booted successfully running last OMNI nightly
So far good performance with this kernel, like always haha
What I want to see now it's the battery life, with the stock kernel, battery life with this ROM was the best I ever had. I'll test some more and report

[yank555]

What I want to see now it's the battery life, with the stock kernel, battery life with this ROM was the best I ever had. I'll test some more and report

OK, now that sounds like a challenge

JP.

[MilTora]

EDIT: Did both GFXBench tests (Egypt 2.5 onscreen and T-Rey 2.7 onscreen). I'm getting higher FPS than CM 10.2 with OC GPU! T-Rex went from 6.3 to 7.3 and Egypt from 15 to 19!!
All this looks really promising