yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] X DoZ3R:
Hi

Mpdecision is cool. I like that, thats why i install this kernel. I really miss input boost from interactive governor, i know its a stock kernel mostly but it helps a lot in scrolling i think. I satisfied with the battery life, got 4hours on wifi. Enough for me. Keep up the good work :)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] Mahdi786:
I like mpdecision because it's very smooth but it gives you no control over frequencies, you can only really control cpu0 for example if you underclock to 1350 only cpu0 would underclock, the other 4 cores would still ramp up to 1512, so for customization mpdecision is not good and that's why most devs have moved away from it and decided for in kernel hotplug
[Nexus 4 Original Android Development] spr33:
Hopping on over to this kernel from Motley b49 and I must admit that this does seem a lot smoother. Unsure of how it compares in terms of battery life yet but I'm pretty sure this is going to be a winner.

Yet another great kernel for the N4! :)
[Nexus 4 Original Android Development] sxp:
woow :D may favorite kernel captivate/SGS and now nexus 4

stratosk thanks ! :D

edit:

i try 0,2 kernel realy fast but missing gamma control

maybe use Faux gammacontrol ..
[Nexus 4 Original Android Development] masterchif92:
What about cm10.1 ? Next release ?

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] stratosk:
Color control is not in my priority list. :)

The truth is that I don't know what exactly is the problem with CM.

We use identical initramfs (I thought that this could be the problem).

I have to flash CM and make tests, but this needs free time...
[Nexus 4 Original Android Development] masterchif92:
I try it on a cm base rom and doesn't work ....when u have time man ;)

Inviato dal mio Nexus 4 con Tapatalk 2
[Nexus 4 Original Android Development] BlueFlame4:
I'm sure, you'll find a solution soon. You were awesome on the i9000!
[Nexus 4 Original Android Development] Yhez:
I've tried to install your kernel over my cm10.1 and it's stock on boot but when I installed your kernel over franco kernel,

(also on cm10.1) It's start OK but then I got force close (system and phone)... Maybe it'll help.

I don't know what scripts Franco used for his kernel
[Nexus 4 Original Android Development] JmPTaz09:
Really loving this kernel; so nice and smooth. Running perfectly well with whitehawkx aokp build from 4/15. I haven't flashed another kernel since trying this (except upgrading to version 2!). Thanks for the nice kernel. :beer:
[Nexus 4 Original Android Development] jarjar124:
Maybe because this kernel isn't compatible with cm10.1 yet?
[Nexus 4 Original Android Development] drewtang:
Franco uses his own ramdisk, you always need to reflash your nightly(when on cm, reset kernel on aosp based ROMs) prior to flashing a different kernel when coming from Franco kernel.
[Nexus 4 Original Android Development] eRajesh:
Any plans on adding support for fauxsound?
[Nexus 4 Original Android Development] JmPTaz09:
I'm personally hoping for less additions; I like a lean, mean, efficient kernel. So far so good with this kernel. I'm one of few who doesn't care if a bunch if stuff is added. The colors and sound don't bother me at all and 1.5 GHz is more than enough. Just need a fully optimized kernel that makes this beast run like butter :beer:
[Nexus 4 Original Android Development] stratosk:
I don't know. I don't know what it does. I have to check the code.

What's wrong with N4 sound?

I totally agree. This is my goal. :)
[Nexus 4 Original Android Development] ctfrommn:
Sound, OC, and other tweaks are unimportant to me too, but Gamma control is a must and UV would be nice.
[Nexus 4 Original Android Development] sxp:
very bad news because stock Color not good N4 :(

all other kernel supported gamma control
[Nexus 4 Original Android Development] Zetok:
Sad but true. Gamma control and sound are must be for this device.

One good example for sound is when using aux in the car. Max car volume + max nexus 4 volume and it still hears low. It's a big problem.

Gamma control is needed too cause the stock colors and gamma actually sucks.

You can check that all the other kernels have support for franco and faux apps to UV, boost sound and change color-gamma settings
[Nexus 4 Original Android Development] DontPushButtons:
Maybe when he gets the kernel working to his standards he'll worry about more of the extraneous additions. In fact, he did say it's not a priority, meaning it IS a consideration, just not as important as a fully functional kernel..

If sound and gamma are THAT important to you, just use a different kernel. As you said, they're included in almost every other kernel in development. I, for one, appreciate that he's not throwing in extra features till he works more on under the hood enhancements. They usually just cause more maintenance and debugging.
[Nexus 4 Original Android Development] Sad56:
Just 2 things

Faux speaker work to increase the speaker volume.

And with Trickster we 've got a little control of RGB for the screen.

I'm not old in Nexus 4 world but I've tried all the kernels around there (and over) and this is the only one who give me more than 5h screen of time with no uv. :)

Keep the good work mate ;)

Envoyé depuis mon Nexus 7 avec Tapatalk
[Nexus 4 Original Android Development] aaronrw:
My 1 and only request and I believe it's been addressed... CM support when you are comfortable? Thanks for your work

sentfromybrain
[Nexus 4 Original Android Development] torana355:
How does it compare to Trinity and rasbean if you have used it?
[Nexus 4 Original Android Development] edwardeutsch:
I would like a better integration with cm 10.1 (stable or not). For me mpdecision si ok!

Great kernel btw! Great work! Smooth, stable band battery friendly!
[Nexus 4 Original Android Development] noobiekins:
Franco's smoothness is from his touch boost in his tuned interactive gov. His hotplugging turns all cores on if you pass a threshold, retaining smoothness in games and etc.
[Nexus 4 Original Android Development] stratosk:
Thanks!

What do you mean better integration?
[Nexus 4 Original Android Development] Luigi_2:
Faux gamma exposes all possible tunnables while franco's doesnt

And the simple GPU gorvernor from faux is pretty good, franco merged it too.
[Nexus 4 Original Android Development] edwardeutsch:
Maybe including the changes of cm kernel in your! I feel that cm kernel is the only one that works perfectly with cm,

;) obviusly. Others aren't smooth like stock kernel on cm based roms!

I'm not a developer and then i can only post my ideas!

And sorry for my bad english!
[Nexus 4 Original Android Development] nedooo:
WOW N4 has 5 CPU cores just WOW...cpu0 + 4 cpu cores maaaaaaan how on Earth did we all missed this part of specs :p
[Nexus 4 Original Android Development] a g bell:
I disable mpdecsion have done for ages my phone hasn't cooked itself and my battery last between 15 to 18 hours with my normal use includes 2hours soc l have also modded system/etc/thermald. config my phone/battery temp stays below 40c :)

Having been using semaphore since GB its awesome:)

I only have 4 cores:eek:
[Nexus 4 Original Android Development] C4SCA:
The first core is called cpu0, second cpu1, third cpu2 and fourth cpu3 ... Check any app u want that recprds your cpu log (system monitor for example)
[Nexus 4 Original Android Development] stratosk:
Any specific issues with CM and Semaphore?
[Nexus 4 Original Android Development] franciscofranco:
Sometimes less is more ;)
[Nexus 4 Original Android Development] Luigi_2:
Haha, not saying yours' bad, just a statement :fingers-crossed: still waiting for your next nightly with simple gpu gov and I'll be back, hehe
[Nexus 4 Original Android Development] sirxdroid:
And other times less is less ;) I hope stratosk doesn't remove the kernel wakelock reporting from Semaphore :D
[Nexus 4 Original Android Development] stratosk:
I believe that this is true most of the times...

...but there is nothing wrong with wakelock stats. I will not remove them. :)
[Nexus 4 Original Android Development] stratosk:
If anyone want to try this: 1.4.0b

- Linux kernel 3.4.51

- an update to framebuffer to fix some visual glitches (thanks to CM team, thracemerin)

- removed mpdecision, msm run queue statistics

There is no other hotplug driver or something. 4 cores are online all time.

The stock behavior push the CPU to max freq on touch (this may change in future if mpdecision will finally be dropped)
[Nexus 4 Original Android Development] sirxdroid:
Why does everyone hate MPDec so much? I think it works very well.

Sending 4 cores to max freq on touch sounds very aggressive.
[Nexus 4 Original Android Development] a g bell:
Sorry forget to ask if LEDs could be disabled by default seem to cause conflict even after disabled in semaphore app :confused:
[Nexus 4 Original Android Development] stratosk:
I don't hate it. I also think it works very well.

I am just try to test the kernel without it.

I also believe it's aggressive. This can be 'fixed' easily (if I will finally decide to drop mpdecision)
[Nexus 4 Original Android Development] stratosk:
I will think about it. Though, what exactly is the problem?
[Nexus 4 Original Android Development] a g bell:
Its closed source,it works well yes but things get better/updated personally l don't use l prefere being able to adjust settings:)

---------- Post added at 12:21 AM ---------- Previous post was at 12:03 AM ----------

I m on slim and use LEDs settings in the ROM l install semaphore and they stop working correctly the red light seems to overwrite all other colors even after disabled in semaphore manger
[Nexus 4 Original Android Development] emanuele1986:
i use now cyanogen mod stable 10.1. With stock kernel cyanogen all is perfect.

After i flashed your kernel(i always use your kernel with cyano and now i think that the fault is your kernel or some kernel tweak) and with pie control enabled when i open the app show a strange flash, i solved activating disable overlay hardware and use only the gpu in developer option. The icon app into the home screen contained in folders when i move it into the folders sometimes go fluid at times jerky. The same lockscreen, also the lockscreen, when crush to unlock the dots sometimes go fluids sometimes jerky. The same for the lockscreen options sometimes are fluid sometimes go jerky

Now try 1.4.0b.
[Nexus 4 Original Android Development] stratosk:
Please for your feedback. I think the commit in this beta will help.
[Nexus 4 Original Android Development] emanuele1986:
Therefore, i installed the kernel. I don't see flash with pie control enabled when i open the app. The icon into the folders when i move it sometimes go at jerky and the same into lockscreen but less. Now go at jerky the setting menu when i open and immediately scrool it or scroll fast!

Why you don't implement hyper governor and change the scheduler?

---------- Post added at 12:50 AM ---------- Previous post was at 12:42 AM ----------

After 20 minuts:

The situation in better for pie control, no flash. But for me the fluidity has worsened

---------- Post added at 01:08 AM ---------- Previous post was at 12:50 AM ----------

I changed scheduler and governor. Interactive + row, now is perfect. For me are the tweaks into the governor and scheduler, ondemand + noop.

Enable again the mpprecision so i try with interactive and row the behavior
[Nexus 4 Original Android Development] apatal:
Semaphore kernel without mpdecision?! Now this got me interested. Question though, you said all 4 cores are push to maximum frequency upon touch. Is this regardless of whatever you are doing with your phone? Wouldn't this be hard on battery? Because I know hotpluggers like those in other kernels at least try to scale the cores' frequencies depending on the task. Still looking forward to whatever innovation you're working on. :)
[Nexus 4 Original Android Development] Luigi_2:
Didnt think interactive could be that good with mpdecision

Just tried Interactive with go_hispeed_load = 75 , hispeed_freq = 1026000 , above = 10000, timer_rate = 20000, min_sample = 60000 , boostpulse = 60000

with ROW (512), and my phone is sooo smooth, no lag, doesnt get hot as fast as ondemand
[Nexus 4 Original Android Development] capoooro:
Installed the 1.04b version. Testing and reporting.

By the way the 1.03 was rocky stable with rasbean family ROM

pizza mandolino pasta
[Nexus 4 Original Android Development] nedooo:
Now you try to make me look like a fool...NOOOO WAAAYYYYYY :cool:

You clearly said CPU 0 and other FOUR cores...FOUR + ONE is what??? 4 - FOUR??? since CORE 0 doesn't count????

So who is silly now and before U or me? U silly :silly:
[Nexus 4 Original Android Development] stratosk:
Another beta 1.4.0b2

- ondemand: touch will produce a pseudo-load 50% for 750ms and this will force CPU to 810MHz

- Removed some unused stuff from ondemand
[Nexus 4 Original Android Development] franciscofranco:
Suggestion: make it 1000ms, 750ms might be too fast, some UI animations take longer to render and it might sttuter ;)
[Nexus 4 Original Android Development] C4SCA:
It wasnt me who said that... Check the names

Is just wanted to clarify this thing about cores names and number of cores
[Nexus 4 Original Android Development] philidor:
Is without mpprecision?
[Nexus 4 Original Android Development] stratosk:
Thanks for you suggestion.

I experiment with different delays and loads.

I also tested 1000ms and then I thought that maybe was too aggressive because 4 cores are online.

Anyway, if I will keep this approach with mpdecision drop these will become tunables.
[Nexus 4 Original Android Development] stratosk:
Yes, as 1.4.0b
[Nexus 4 Original Android Development] philidor:
I'm testing with ondemand (all stock only under volt). Is as you want we test it?
[Nexus 4 Original Android Development] stratosk:
Yes, thank you.

This is fine!
[Nexus 4 Original Android Development] emanuele1986:
the situation seems to have improved
[Nexus 4 Original Android Development] snak3ater:
It would be great if we could have some more options for the GPU frequencies
[Nexus 4 Original Android Development] stratosk:
I'm sorry, no plans for changes in GPU frequencies.
[Nexus 4 Original Android Development] JmPTaz09:
Everything going well so far on 1.4.0b2. Seems just as smooth as 1.3.0; which is a good thing.
[Nexus 4 Original Android Development] stratosk:
One more beta: 1.4.0b3

- ondemand: touch_load increased to 65% (1026MHz) for 2sec duration

- ondemand: touch_load is applied only to CPUs the load is above 15%. So, CPUs with low load (and most probably unused) are not boosted.

- built with Linaro 201306 (gcc 4.8.2)

Thanks everybody who testing betas. Usually I don't provide betas but I think it's necessary to decide if I will drop mpdecision or not.
[Nexus 4 Original Android Development] fabian.m:
You put so much work into this... Thanks so much
[Nexus 4 Original Android Development] nedooo:
Ooops...sorry my bad...I was just kidding anyway ;)

Though it was funny how he wanted to act smart and said there are 4 CPU cores and another zero core, that's 5 when you count all of them :D

Sorry again :angel:
[Nexus 4 Original Android Development] C4SCA:
No problem!

5 cores -> yeah! We have a tegra processor!!!! NOT :banghead:
[Nexus 4 Original Android Development] io53:
Thank "god" for the tegralessness :p.

I like this kernel. Seems to be the "it just works" kernel for N4 :).
[Nexus 4 Original Android Development] philidor:
B2 work very well good battery smooth for what it mean antitu
[Nexus 4 Original Android Development] emanuele1986:
Well done ! With this beta is again more fluid the system. But i have doubt for the core always online for the battery. If you want to drop the mpprecision, reduce the low frequency under 384mhz.
[Nexus 4 Original Android Development] a g bell:
What ROM do you use?
[Nexus 4 Original Android Development] JmPTaz09:
No offense, but I don't think you need to teach Stratosk about the effect of online cores to battery. Additionally, the minimum frequency really has little to do with a decision to remove MPDecision. Lowering it likely doesn't do much for battery (tiny save on battery for a tiny bit less smoothness), but that's up to Strat to decide on. :beer:
[Nexus 4 Original Android Development] sirxdroid:
And it's unclear whether the CPU can actually run at anything less than 384Mhz. Sure it can report whatever number, but kernel devs suspect it doesn't actually run at lower frequencies.
[Nexus 4 Original Android Development] a g bell:
I don't l have been running semaphore for awhile without mpdecision and get between 15 and 18 hours with 2hours sot :)
[Nexus 4 Original Android Development] stratosk:
Thanks. I guess we will find out soon how much this affects battery.

I'm optimistic with beta 3. I think the cost will be low.

I don't think I will reduce low frequency.
[Nexus 4 Original Android Development] emanuele1986:
Tomorrow i will send my feedback for the battery with beta 3.

PS: for the message to reduce the MHz. It is only my opinion
[Nexus 4 Original Android Development] stratosk:
Thanks, I appreciate and respect any opinion. :)
[Nexus 4 Original Android Development] a g bell:
So has anyone had bad battery life with betas?
[Nexus 4 Original Android Development] Anrikus:
For me, battery life didn't change. But the first beta is kinda 24 hours old, so for me it's not really representable.
[Nexus 4 Original Android Development] philidor:
CM 10.1 with with beta 2
[Nexus 4 Original Android Development] capoooro:
For the moment no sensible difference between beta2 and 1.3 the battery life is similar and also smoothness. Going to try beta3... But your work seems always very good, in all variants

pizza mandolino pasta
[Nexus 4 Original Android Development] philidor:
[MENTION=3750240]stratosk[/MENTION] can you make a beta with the possibility to enabele-disable mpprecision. Will be simpler to feel the difference with or without (all your kernel work great, I don't feel great difference between 1.3 e 1.4 betas after only one day of usage)
[Nexus 4 Original Android Development] stratosk:
I'm afraid it's not so straightforward to do this. It will require more code to control both cases.

Our goal is to make the device feel at least the same without mpdecision.

Even if the results are exactly the same I will drop it, because of simplification.

My only concern of course is battery drain. If it's almost the same we are in the right path. Because, with couple more optimizations we will get the same results.

My observations so far:

- Device feels a little bit more snappier in different tasks (like opening and using apps)

- The UI feels almost the same smooth (maybe we can improve it a little bit)

- Battery: I wake up with full charge. Tonight I will have results about this. It seems OK so far. With my usage with mpdecision I get 1d and few hours uptime with 4-4.5 hours screen on time.

[MENTION=535343]all[/MENTION]

Please for your feedback. I need confirmation for the above.

I will leave the beta for few more days. If it's OK I will make the new tunables in ondemand available through sysfs and I will finalize it.
[Nexus 4 Original Android Development] emanuele1986:
[MENTION=3750240]stratosk[/MENTION]

i see again micro shots when i open the drawer and scroll the app
[Nexus 4 Original Android Development] stratosk:
We can arrange this with the new tunables in the final version.
[Nexus 4 Original Android Development] a g bell:
Tunables yes please:)
[Nexus 4 Original Android Development] philidor:
[MENTION=3750240]stratosk[/MENTION] after 11h+ 51%... But with only 1h and 1/2 of screen time. Performed many antutu test (21k + ). Call and whats app. Update to today nightly. Near the same with 1.3. All work great and smooth. UV -150. CM 10.1 with beta 3.
[Nexus 4 Original Android Development] a g bell:
Well it comes as no surprise to me battery life is still excellent on B3 16hrs 45%:rolleyes:
[Nexus 4 Original Android Development] philidor:
[MENTION=3750240]stratosk[/MENTION]: "Show CPU table" don't show UV setting. Working right with 1.3. Now don't work with beta3. It's only me?
[Nexus 4 Original Android Development] stratosk:
Works fine here. Did you press 'Apply'?
[Nexus 4 Original Android Development] philidor:
Yes I press apply and I see the message from SU that Semaphore manager is asking for permission but I can't see the table, all the table :). Pressing "Show CPU table" don't show the table don't show anything. I upgrade cm this may be the problem. With beta2 all work. There is a terminal command to show the UV settings? I retry to flash ROM and kernel.

---------- Post added at 06:41 PM ---------- Previous post was at 06:35 PM ----------

Sorry [MENTION=3750240]stratosk[/MENTION] for spamming your thread . dirty flashing cm and after beta 3 solved the problem (or maybe was privacy guard new cm features). As always all work! Thanks
[Nexus 4 Original Android Development] lyfkevin:
Hi [MENTION=3750240]stratosk[/MENTION],

I dun have nexus 4. but so much thanks for your kernel work!

I learnt a lot from you.

I am doing the same test (without mpdecision, adopted ur ondemand commits) on my dualcore device, LGNitro HD (msm8660)

It works great.:good:
[Nexus 4 Original Android Development] capoooro:
After three days with beta2 it seems stable and smooth. I don't see any appreciable difference between this and 1.3

pizza mandolino pasta
[Nexus 4 Original Android Development] Necromancer3:
Startosk, followed you from SGS1 ....

is there any way to battle the notorious msm_hsic_host wakelock that drains the battery life?
[Nexus 4 Original Android Development] cryingrock:
A noob question about the "reset to default" option in semaphore manager: what does "default" refer to? Kernel default or system default?(the same?) I ask this because some ROMs may overwrite the kernel default value when booting.

Sorry for my bad english:p

Sent from my Nexus 4
[Nexus 4 Original Android Development] stratosk:
It reset app's values to Semaphore kernel's default settings. If ROM overrides kernel's settings is another story.
[Nexus 4 Original Android Development] kingofu7:
+1
[Nexus 4 Original Android Development] philidor:
This my be helpful?

http://xdaforums.com/showthread.php?t=2102986
[Nexus 4 Original Android Development] Necromancer3:
i already looked at this thread and the other 50+ pages thread about this, but there is no definitive answer.

does this kernel really helps? i'm a bit skeptical because if it does, why other dev's don't include those changes?

aren't you guys suffering from it?
[Nexus 4 Original Android Development] stratosk:
I'm skeptical too. I will not merge those changes.
[Nexus 4 Original Android Development] io53:
It does reduce the wake lock quite a bit. Try it and see for yourself, you will not notice a big difference if you're using Wi-Fi a lot tho as it only happens on 3G.
[Nexus 4 Original Android Development] rusak2:
Hi,

what about the early demand settings? If I activate it, will I get more smoothness and more battery drain too?
[Nexus 4 Original Android Development] capoooro:
I use early demand normally with no battery drain

pizza mandolino pasta
[Nexus 4 Original Android Development] rusak2:
Thanks,

but it gives a speed boost or not?
[Nexus 4 Original Android Development] stratosk:
Early demand was dropped in latest version (1.3.0)

Soon, it will be removed also from Semaphore Manager app.
[Nexus 4 Original Android Development] rusak2:
Ok, so I could use instead of early demand the interactive governor to get some extra smoothness?
[Nexus 4 Original Android Development] capoooro:
So if you switch it on it do nothing?

pizza mandolino pasta
[Nexus 4 Original Android Development] stratosk:
In version 1.3.0, nothing.