yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Tylog:
Do not get me wrong, it was not personal against you and no offense :) It's more generally about the people always complain about the battery life. We now use a smartphone, and once the part has to be charged every night, the days when you had to load his phone once a week are long gone.

When I get to 3-4 hours a day and in the evening still had enough battery that the phone does not go out then everything is good :)

As I said, I meant my statement because I generally this "I want to 7 hours on screen time have" can not hear. With most everything revolves only around the battery battery battery ( how is battery is my battery big green yellow battery battery, 50% of post are about the Battery in the Most Threads ) ;) and let's be honest, if there are now 4 or 5 hours, it's not going well below :)

So please dont fell you personally attacked , thank you :)

Best Regards
[Nexus 4 Original Android Development] stratosk:
If speed is not your concern, you may try less aggresive settings in ondemand governor:

Turn off io_is_busy, set sampling_down_factor to 1 and sampling rate to a higher value (50000).

Also, you may try undervolting.
[Nexus 4 Original Android Development] Ümit:
Battery life has something to do with custom colors?

and I use dark wallpaper. it's good for battery life?
[Nexus 4 Original Android Development] Tylog:
We have no Amoled, so no.
[Nexus 4 Original Android Development] reginickneo:
IPS screens are use more battery than AMOLED when the screen is black, but use less at white background.
[Nexus 4 Original Android Development] X DoZ3R:
Guys, if i wanna optimise for performance, what governor should i choose? Normally interactive but here the ondemand is tweaked so need some advice .... Ty :)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] hospital349:
Semaphore WIKI is now available. [MENTION=3750240]stratosk[/MENTION] - consider it a gift. Enjoy! :good:
[Nexus 4 Original Android Development] Naa Laa:
I would recommend using everything default for some days and tweak to your needs!
[Nexus 4 Original Android Development] aimcr7:
No, in the IPS no matter what color it shows it uses the same battery, more brightness more battery.

Amoled uses almost no power when showing black, because literally the pixel that showing black is turned off, that's why no matter how bright you put your brightness slider the black is still the same on AMOLED and it looks little greyish on IPS (last generation IPS already improve the black but still not as deep as amoled).
[Nexus 4 Original Android Development] reginickneo:
I meant it use less than AMOLED if you'd like to compare.
[Nexus 4 Original Android Development] ferroneee:
Red led (cpu)

how to disable red led when cpu is over 46°?!?!?
[Nexus 4 Original Android Development] jorrddan:
You can use Semaphore manager from Play store to setup the kernel options.
[Nexus 4 Original Android Development] malcho:
Very good job stratosk.

Only thing missing is color presets.

Many regards
[Nexus 4 Original Android Development] hughfollett:
Coming from the s2, i didn't see any difference using only black walls than any other wall..
[Nexus 4 Original Android Development] stratosk:
Thanks, my friend!

Do you mean presets in the app?

I'm not sure if I will find the time. I am interested in mainly for the kernel. :)
[Nexus 4 Original Android Development] C4SCA:
Please keep focused on the kernel it self (optimization)

Cuz for a long time im trying to choose a simple kernel (like the old school ones) just to keep my phone a bit faster and less warm... All it seem is that everyone is using each other extras and at the end they are all the same. Extremelly bloated kernel (its only my opinion).

Im currently using trinity but im sneak picking ur work for a long time. As soon has i get a PC working (my pentium fried...), i will flash stock, flash TWRP,... Well, do a very clean install of everything to then try your kernel

:D
[Nexus 4 Original Android Development] malcho:
Yes.

But it's not obligation.

Keep up the good work
[Nexus 4 Original Android Development] stratosk:
You too, my friend!
[Nexus 4 Original Android Development] stratosk:
I love kernel. My goal is a stable and fast kernel. My goal is to develop some original stuff and if possible to submit it to Linux.

I will be focused on this and only on this.
[Nexus 4 Original Android Development] malcho:
Preparing my rom.

Trying different base,probably will use aokp with your kernel.
[Nexus 4 Original Android Development] C4SCA:
:beer::beer::beer::beer::beer:
[Nexus 4 Original Android Development] BLADESMAN1889:
Perhaps someone with know how [which is not me] could do this job ? If the work is approved by Stratosk it could be added into the Sem app ?

Ps, This idea is not for my benefit as I don't twiddle around with kernel just keep it stock but because I see so many requests - remember folk Semaphore is not a team, but a 1 man job with 2 kernels to build for 2 devices & app for 2 devices also.

Sent from NEXUS⁴ via XDA app [AOKP\/\/hitehawkx]​
[Nexus 4 Original Android Development] edwardeutsch:
Amazing work stratosk! Best kernel ever used on CM. Great battery life and performance.

Only one bug...when i use pie on latest nightly i have the old problem of screen flickering when launching an app. Like on older cm nightlies.

Can you fix that? I rally want to stay with your kernel but that problem is really annoing me!

Sorry for my bad english!
[Nexus 4 Original Android Development] stratosk:
Thanks!

I'm not sure I undrestood the issue. I'm sorry for my ignorance what is the 'pie'?
[Nexus 4 Original Android Development] ratcav:
It's an alternative to the navbar wich is in CM and in PA
[Nexus 4 Original Android Development] edwardeutsch:
It's an old issue of older CM Nigtlies.

Pie Controls are quick controls that are triggered by swiping on the display. While not in use, they are hidden, but with the quick swipe of a finger, you have access to settings, home button...

When pie controls are active, when launching apps there is a flickering issue that shows for less the half second the home screen.

The bug on stock cm are now solved. But some kernel give me that issue!

I hope you will understand..

EDIT: look here http://xdaforums.com/showthread.php?p=41956544
[Nexus 4 Original Android Development] thracemerin:
[MENTION=3750240]stratosk[/MENTION] this commit will fix it: https://github.com/CyanogenMod/lge-kernel-mako/commit/4857f9b6dcb4bc2372815ca24f5eb3b23e983364

FYI: this commit has been reverted by Qualcomm on Codeaurora also, so there should be no detrimental effect for those without the CM Pie issue.
[Nexus 4 Original Android Development] stratosk:
OK, I will check the commit thracemerin suggested (thanks).

Most probably will be included in next version.
[Nexus 4 Original Android Development] edwardeutsch:
Amazing! Thank you very much! Great work again!
[Nexus 4 Original Android Development] X DoZ3R:
Anyone experienceing sometimes the screen off animation is lagging? Im using interactive governor and cm10.1....ty

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] jelle2503:
Actually sema app is open source:

https://github.com/stratosk/semaphore_manager

So anyone with the knowledge could add the gamma presets, i wish i could.
[Nexus 4 Original Android Development] io53:
Adding present values should be no problem at all. Provide values that you would like to have in the present list. I might do it if I have time. Got two kids, a full time job and away too many hobbies, but you never know :).
[Nexus 4 Original Android Development] ctfrommn:
Stratosk,

How do I change the default governor from inside the kernel code? I cant for the life of me find where that file is located.

Thanks :)
[Nexus 4 Original Android Development] franciscofranco:
Open your .config and do this for the governor you want as default

# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set

to

CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y

and change the already defaulted one to not set.
[Nexus 4 Original Android Development] jelle2503:
Here is the excel sheet. Just add a selection. Many users will be thankful.

https://dl.dropboxusercontent.com/u/43833650/franco_semaphore.xls
[Nexus 4 Original Android Development] ctfrommn:
Thank you kind sir....:)

---------- Post added at 03:10 PM ---------- Previous post was at 02:51 PM ----------

Ok, humbled now.....which config file and where is it....I feel like an idiot :)
[Nexus 4 Original Android Development] franciscofranco:
Kernel root dir, file called .config

find . -name ".config"
[Nexus 4 Original Android Development] ctfrommn:
Got it, thanks for your patience and sorry to clutter your thread Stratosk :)
[Nexus 4 Original Android Development] stratosk:
It's kernel discussion so, no problem at all. :)
[Nexus 4 Original Android Development] ctfrommn:
That worked great Franco....love learning new stuff :)

---------- Post added at 04:08 PM ---------- Previous post was at 03:23 PM ----------

Ok, so I changed ondemand=y to "is not set" and Interactive to =y and after I build the kernel its going back to the previous defaults. Is there another script controlling the building?
[Nexus 4 Original Android Development] thracemerin:
It's in the ramdisk, the stock ramdisk sets ondemand when the phone boots.

I believe it's in the init.mako.rc file, might be different depending on the ROM.
[Nexus 4 Original Android Development] ctfrommn:
Ok, found it....it looks like all the settings are for ondemand. How do I change that? I didnt see anything in there for Interactive and I dont want to remove the governor entirely.
[Nexus 4 Original Android Development] thracemerin:
change the line that looks like this:

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "ondemand"

to

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "interactive"

do this for cpu0, cpu1, cpu2, cpu3

you can also remove the other settings for ondemand or just comment them out.
[Nexus 4 Original Android Development] ctfrommn:
I thought about doing that, but dont I have to add all the separate lines for the settings like are in there? Above highspeed delay, boost, etc?

That command doesnt even show up except in the section below where it says "on charger" and there it is set to powersave.
[Nexus 4 Original Android Development] thracemerin:
I believe those are hardcoded into interactive, so you shouldn't need to, no. Unless you want to deviate from the defaults without recoding the governor, but I can't see what the point of that would be.
[Nexus 4 Original Android Development] ctfrommn:
Here's what Im looking at....

# Enable Power modes and set the CPU Freq Sampling rates

write /sys/module/rpm_resources/enable_low_power/L2_cache 1

write /sys/module/rpm_resources/enable_low_power/pxo 1

write /sys/module/rpm_resources/enable_low_power/vdd_dig 1

write /sys/module/rpm_resources/enable_low_power/vdd_mem 1

write /sys/module/pm_8x60/modes/cpu0/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu1/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu2/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu3/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled 1

write /sys/devices/system/cpu/cpufreq/ondemand/up_threshold 90

write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 50000

write /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy 1

write /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor 4

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq 384000

on charger

# Enable Power modes and set the CPU Freq Sampling rates

write /sys/module/rpm_resources/enable_low_power/L2_cache 1

write /sys/module/rpm_resources/enable_low_power/pxo 1

write /sys/module/rpm_resources/enable_low_power/vdd_dig 1

write /sys/module/rpm_resources/enable_low_power/vdd_mem 1

write /sys/module/pm_8x60/modes/cpu0/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu1/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu2/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu3/power_collapse/suspend_enabled 1

write /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled 1

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "powersave"

write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor "powersave"

write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor "powersave"

write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor "powersave"

write /sys/devices/system/cpu/cpufreq/ondemand/up_threshold 90

write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 50000

write /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy 1

write /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor 4

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq 384000

write /sys/devices/system/cpu/cpu1/online 0

write /sys/devices/system/cpu/cpu2/online 0

write /sys/devices/system/cpu/cpu3/online 0
[Nexus 4 Original Android Development] thracemerin:
Yeah, all that ondemand stuff is commented out in the ramdisk I stole from _motley for my kernel.

These specifically:

write /sys/devices/system/cpu/cpufreq/ondemand/up_threshold 90
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 50000
write /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy 1
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor 4

all have a # in front of them.
[Nexus 4 Original Android Development] ctfrommn:
Can I add those lines referencing Interactive? And should I do it in both fields? On charger and not?

This may not be tweakable with the stock ramdisk...
[Nexus 4 Original Android Development] thracemerin:
On charger is the same as the ones you posted.
[Nexus 4 Original Android Development] thracemerin:
I think the stuff in the on charger section is for when the phone is plugged in and powered off, because my device stays on the interactive governor while powered on and on the charger. Someone else with a little more knowledge on messing with ramdisks can probably confirm this.
[Nexus 4 Original Android Development] ctfrommn:
I appreciate all your help.... I tried all of that and it is still reverting to Ondemand. I'm going to try to build it with the Rom and s if that works.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] thracemerin:
You have to edit the actual ramdisk, you can't modify the files on a running ROM because they get unpacked again from the ramdisk on boot. (you may know this, but just in case)
[Nexus 4 Original Android Development] ctfrommn:
Nah... Im a total noob right now..... How do you do that then?

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] thracemerin:
What linux version are you using to do this?

Edit: come talk to me in the m+ thread so we stop spamming this one :)
[Nexus 4 Original Android Development] alexiscarrascom:
I'll love to have screen presets in Semaphore control app, with PA3+ Halfbreed and iPhone 5 I'll be so happy... PLEASE :D
[Nexus 4 Original Android Development] C4SCA:
Row is it still being updated and tweaked?

Are u anning to try fiops? Its a new io scheduler made for ssd...

Thanks

---------- Post added at 03:31 AM ---------- Previous post was at 03:26 AM ----------

I read a bit more about noop and now i get why u use it... Reduces cpu usages = more battery and more cycle free to do other stuff

Am i wrong? Or did i get it right?
[Nexus 4 Original Android Development] zevim2005:
Hi Stratosk,can you see why semaphore doesn't boot with MIUI??was using your kernel with slimrom and its too good to change to MIUI and be without it.

Thanks for the awesome kernel!!!
[Nexus 4 Original Android Development] stratosk:
Thanks for your kind words!

To be honest, I'm not sure I want to check it.

Diverging from stock kernel/behavior maybe and indication that custom kernels are not welcome in a ROM.

I did it once for CM, but I can't do it easily for every ROM. Developers should think twice when they break stock functionality, if they care for compatibility.
[Nexus 4 Original Android Development] X DoZ3R:
Can i tweak the kernel to get bigger touch boost? I didnt find touch boost option in sem. Manager or in zhe system files.. Ty

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] Remoteconcern:
No, this kernel uses mpdecision which has a fixed touch boost of 2 seconds, and isn't changeable.

Just out of interest, what language is that in your signature?
[Nexus 4 Original Android Development] X DoZ3R:
Ok thx. Hungarian, im from hungary:)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] Comporellon:
Your hungarian isn't perfect:

helyesen: az én Nexus 4-emről :)
[Nexus 4 Original Android Development] reginickneo:
Haha. :D Túl sok itt a magyar, azthiszem. :)

Sorry for the offs.
[Nexus 4 Original Android Development] X DoZ3R:
Nem foglalkoztam meg vele, alapbol ezt rakja be a tapatalk :D s*cks... :)

Tapatalk 2-vel küldve az én Nexus 4-ről
[Nexus 4 Original Android Development] klasszsrac:
Micsoda egymásra találás :) Boruljatok össze ;)

Nexus 4 <~> custom Aokp
[Nexus 4 Original Android Development] C4SCA:
English please
[Nexus 4 Original Android Development] emanuele1986:
Hi stratosk!

In the last cyanogenmod stable 10.1 for nexus 4, there are incredible setting for touchscreen sensitive!!!!!!! Please extract it and implement in your kernel ;).

Bye
[Nexus 4 Original Android Development] thracemerin:
CM 10.1 stable uses the stock touchscreen settings.
[Nexus 4 Original Android Development] emanuele1986:
Are your sure?!?!? before installing the stable, I had problems with the pie control because I had to touch with a good part of the finger, is leaving the cyano is installing the kernel and semaphore and with stock rom was again worse. Now just only the tip of the finger and pie control appears on the first shot. The same goes horizontally. Trust me they changed something!
[Nexus 4 Original Android Development] thracemerin:
Not kernel side they didn't, touch drivers are the same, I looked on github.
[Nexus 4 Original Android Development] emanuele1986:
thank you, and what's happened? :confused:
[Nexus 4 Original Android Development] stratosk:
So, any comments about this kernel?

What do you think about it? Any thoughts?

What's your opinion?

Any feedback is welcomed. :)
[Nexus 4 Original Android Development] Anrikus:
First, I'm very happy with the kernel.

Coming from faux (and its huge ammount of tweaks in that kernel) I was supprised how small the difference in performance and battery life is (if there is any).

Buuuuuuut (now the whine starts):

Knowing your work for the SGS1, I hoped you would implement franco or faux gamma / sound commits as modules like the support for vodoo sound or BLM for the SGS1.

There would be no need to maintain an interface in the semaphore app, since there are allready apps from faux, franco or trickster to manage the commits.

Still I have no idea if something like this can be done as easy as it sounds... (I have no experience with compiling kernels at all)

In the end you have profen that you know what you are doing by providing a rock stable kernel with some unique features.

Thanks again.

Best Regards

Anrikus.
[Nexus 4 Original Android Development] Kocai:
I love the smoothness of this kernel. But seems that mpdecision is quite a battery drainer since it would ramp up the CPU frequency to 1026 which obviously would drain the battery more. Do you have any future plans regarding the hotplug? Or are you going to stick with mpdecision?

Sent from my Nexus⁴
[Nexus 4 Original Android Development] stratosk:
Thanks for your comments. I noted all your points.

I have one question. Why do you need franco/faux gamma control? I mean what's the difference?

Practically you may have the same result with Semaphore.

Thank you too for your comments.

I have some thoughts about mpdecision but I'm not sure yet.

mpdecision is a quite battery drainer compared to hotplug?

No offence at all (I really need to know), how did you compare these two?

I mean did you compare hotplug with less 'aggressive' tweaks with mpdecision?

Did you have any compromise in smoothness using a hotplug approach?
[Nexus 4 Original Android Development] mikeman8484:
I'm very happy with your kernel ;) touch to wake included is a big plus, gamma control works great although presets would be nice too ;) I've seen people asking for it, that would be a great option.

I'm not a big gamer, just the end user but performance is good.

Sometimes when scrolling on xda for example or a browser small lag appears but it might be my set up ;)

Great work! :D

....battery seems to worst than on previous versions 1.0, 1.1 but again it might be my current set up ;)
[Nexus 4 Original Android Development] Kocai:
First, I don't know much about faux gamma control but I think Franco kernel is a little bit brighter (with the same value for gamma control) compared to the other kernel. But it maybe because my ROM (PA). Of course this is just probably my eyes.

Second, regarding your question, I don't have a scientific approach. I just get more screen on time with other kernels that I use, specifically motley (which is continued by thracemerin). The difference is not that much though. Using yours for a few days, the best I can get is around 4+ hours screen on time which is not bad at all. With motley, I can get 5 hours. As far as smoothness, I don't see any difference.

My noob examination is that since mpdecision would ramp up the frequency to 1026 mhz, it would drain the battery more since higher frequency means more battery consumption, no?

Motley uses thalamus auto hotplug, Franco recently just start to implement his own. So I'm just curious if you have any plans to implement your own.

And no, no offence at all. I admire your work. I'm still using your kernel on my SGS.

Sent from my Nexus⁴
[Nexus 4 Original Android Development] mikeman8484:
I agree with Kocai regarding SOT time.
[Nexus 4 Original Android Development] Anrikus:
You are right, practically I can use Semaphore to adjust gamma and if you know the trick it's easy to apply a present from franco.

To get a present from faux working is a ton of work, since faux implementation is way more difficult to read / convert from the values given.

In the end, you created a kind of third standard after franco and faux. Sharing presents from one of the other standards are tricky (franco presents) or nearly impossible (faux presents) for someone who don't want to look up in some tables and start calculating.

I have no problem to maintain my excel sheet with the converted values from franco on a regular base, but on a absolutly selfish base I wish I could use the faux display app (and it's presents) to adjust gamma with 2 clicks :p

In short: Your implementation is fine and working flawlessly, but after 2 well-established standards (that are allready used by other kernels) with a lot of presents, the only thing it lacks, is a compatibility to get presents from faux/franco running.

Best Regards

Anrikus
[Nexus 4 Original Android Development] stratosk:
Regarding gamma control, you should have exactly the same results using the same values.

I just expose the gamma table through sysfs. As far as I know other devs do the same. There is no change in how the kernel behaves.

I think hotplug (at least Franco's approach) also ramp up freq on touch.

As I said, I'm not convinced that in kernel hotplug is the best approach.

I was thinking to try an absence of a mpdecision/hotplug driver approach. :)

But no specific plans.