yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] :
Can I just say that this kernel has the best balance between battery life, performance and stability? Also the concept of determining the touch boost based on the actual CPU load(like in this kernel) makes much more sense to me than having a set frequency to which the CPU is boosted to(like in almost every other kernel). Thanks [MENTION=3750240]stratosk[/MENTION] !
[Nexus 4 Original Android Development] Ryanrioz:
used it for 3 months ago and still kicking good :D
[Nexus 4 Original Android Development] bboran:
Can i use this kernel with latest cm 11 nightlies? Do you recommend?
[Nexus 4 Original Android Development] gialakias:
Jolie belle works with cm11. http://xdaforums.com/nexus-4/development/kernel-jolie-kernel-mako-2-2-2-t2547149
[Nexus 4 Original Android Development] omer7:
I'm on purity and semaphore latest version. Just now got SOD.

Here's last_kmsg.

https://www.dropbox.com/s/ieujyx3utoteyeh/last_kmsg

Thanks
[Nexus 4 Original Android Development] twowheeler:
What are your settings? Undervolted?
[Nexus 4 Original Android Development] omer7:
Only disabled boost voltage. RH size to 256, and everything else on default.
[Nexus 4 Original Android Development] Rohit02:
Missing [MENTION=3750240]stratosk[/MENTION]..

Hope you are good.. Enjoying life.. Tc
[Nexus 4 Original Android Development] ceejay83:
your environment plays a big difference and what tasks you're doing. i'm in california and indoors i usually get anywhere from 30-40c and outside 40-50c. i'm on a fast binned chip
[Nexus 4 Original Android Development] ctfrommn:
Thats a huge difference from me and Im in cold MN. Why UV is critical for me. I can attain those temps if I UV.
[Nexus 4 Original Android Development] Drmol:
No idea what you're asking me about :D

But after 20 minutes of playing my battery got up to 40.5°C and the CPU was 57°C, so that's fine I guess. Is it safe to keep the Trickster app installed or will it interfere with Semaphore Manager in some way?
[Nexus 4 Original Android Development] ceejay83:
Think it's fine as long as you don't set to boot on trickster
[Nexus 4 Original Android Development] emanuele1986:
i installed semaphore 0.7.5 but the led is always on with red colour. How do i must deactivate it? I use trickster mod
[Nexus 4 Original Android Development] Drmol:
Semaphore Manager from Google Play
[Nexus 4 Original Android Development] kenshinta:
One notable thing coming from Franco kernel + stock Rom

Semaphore seems to have a hard time waking from deep sleep. Phone lags and there is full CPU load while doing so. This takes from a few seconds to under 30 second depending on what app was left open before sleep. It especially takes a long time if the camera is last app.

Is this expected behavior with semaphore?what can be tweaked to make it more snappy waking from deep sleep?

Thanks
[Nexus 4 Original Android Development] JmPTaz09:
Never had even the slightest bit of "grogginess" when waking from deep sleep and I've run this kernel on a handful of ROMs(never stock granted). I've not seen anyone else comment on this either so maybe you need a fresh ROM then kernel flash or so?
[Nexus 4 Original Android Development] sirxdroid:
[MENTION=231687]kenshinta[/MENTION] - did you dirty reflash the ROM or flash a reset kernel before flashing Semaphore? Franco kernel may have left something behind.
[Nexus 4 Original Android Development] pnut22r:
Is this kernel near stock, with some improvements?
[Nexus 4 Original Android Development] apatal:
Yes, and boy, what improvements! :D
[Nexus 4 Original Android Development] qtekker:
I too come from franco kernel, and I also encounter the same lag as described. I haven't flashed a reset kernel. I'm on stock rom. I hope someone can help me out...

By the way: I'm glad jou joined the N4 development stratosk. I was a big fan of semaphore kernel on i9000.
[Nexus 4 Original Android Development] stratosk:
It depends how to define it.

I try to keep it clean with no unnecessary (IMO) stuff.

But I also update it to 3.4.44 that has tons of fixes against stock. (I count 2672 more commits).
[Nexus 4 Original Android Development] stratosk:
Franco changes a couple of libs. So, yes you need to reset some stuff.

Thanks for your comments.
[Nexus 4 Original Android Development] stratosk:
As you already know Linux 3.10-rc1 released.

I'm happy because my small contribution is included there :)

https://git.kernel.org/cgit/linux/k...id=refs/tags/v3.10-rc1&qt=author&q=Stratos+Ka
[Nexus 4 Original Android Development] H-Body:
Damn, this night my N4 got a sod and because of that my alarm wasn't ringing and i missed breakfast with my grandparents :D

Which kind of log should i provide?
[Nexus 4 Original Android Development] stratosk:
I'm really sorry about that.

If you only reboot once, please post /proc/last_kmsg

Please also post your configuration.
[Nexus 4 Original Android Development] H-Body:
Dont worry, it's all right :)

Hmm that file is empty, but i'll post my configuration:

Paranoid Android 3.5

Semaphore 0.7.5 (Standard settings with sai enabled and custom lcd configuration)
[Nexus 4 Original Android Development] qtekker:
Thanks for your fast response. I assume reset kernel means reflash stock kernel and then semaphore kernel. I'll give it a try.
[Nexus 4 Original Android Development] stratosk:
I'm sorry I can't help more on this.

But, please keep me informed about this issue.

I don't think this will help.

There some reset kernels in other threads that seems to restore some stuff. I've never tried them, so I'm not sure how they work.
[Nexus 4 Original Android Development] TheRebel:
If anyone can please explain me the function of "Read Ahead" size option (I have googled it but couldn't really find a satisfactory answer)? Default in semaphore is 128, bigger value means higher performance?

Thanks
[Nexus 4 Original Android Development] Gu$houn*:
Of course he is, look at that new avatar, he's just chilling out. :)

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] twowheeler:
Bigger values could mean better performance on memory read (like viewing photo's or accessing music files). Too much however can have a negative effect. 256 to 512 is what most people use ;).

Edit: better explained by [MENTION=5140864]TheNerd:][/MENTION] :

SD card read ahead is the amount of data your device reads every time it performs a task. Lower read ahead means your device will read less data each time, so your device will have lower latency but less throughput. Higher read ahead means your device will read more data each time it performs a task so higher latency but more throughput. [/quote]
[Nexus 4 Original Android Development] emanuele1986:
Works perfect with omnirom. No problem for me
[Nexus 4 Original Android Development] stratosk:
I'm sorry, I can't find something in last_kmsg.

"Last boot reason: hw_reset_or_poweron"

I'm OK, thanks!

I hope your are good too! :)

A little bit... :)
[Nexus 4 Original Android Development] omer7:
Thanks for the reply ☺

Can u plz tell me what does this error/boot reason mean? hw_reset_or_poweron?

Thank you.
[Nexus 4 Original Android Development] stratosk:
I don't really know.

A reset from hardware, but no additional info.
[Nexus 4 Original Android Development] Malkemid:
i'm using this kernel on omnirom and i use DT2W . sometimes specially when i have a call...the touch will freeze and does nothing...so i have to reboot using power bottun.

i think this is only happens when i use DT2W. can this be fixed?
[Nexus 4 Original Android Development] Gu$houn*:
There is a workaround for unresponsive screen issue, when you touch it with let's say >4 fingers, it will get responsive again, try it a you'll see ...

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] fabian.m:
Hey guys, I posted in my rom's thread as well, but is there any reason this init.d script doesn't get applied properly?

#!/system/bin/sh

FREQMIN=384000
FREQMAX=1242000
echo "$FREQMIN" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "$FREQMIN" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo "$FREQMIN" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo "$FREQMIN" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo "$FREQMAX" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "$FREQMAX" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo "$FREQMAX" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo "$FREQMAX" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq

echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo "810000" > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo "40000" > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay

echo "1" > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/idle_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu0/standalone_power_collapse/suspend_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu1/standalone_power_collapse/idle_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu1/standalone_power_collapse/suspend_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu2/standalone_power_collapse/idle_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu2/standalone_power_collapse/suspend_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu3/standalone_power_collapse/idle_enabled
echo "1" > /sys/module/pm_8x60/modes/cpu3/standalone_power_collapse/suspend_enabled

GPUMAXFREQ=200000
echo "$GPUMAXFREQ" > /sys/class/kgsl/kgsl-3d0/max_gpuclk
echo "sio" > /sys/block/mmcblk0/queue/scheduler
[Nexus 4 Original Android Development] krizina:
Does your Nexus get hot on Semaphore kernel?

I was on Semaphore (latest and slimkat build 6) for two months and noticed that it is hotter then before. Undervolted 150mV, all default, tried with 2 cores only and lower max freq, but no help.

I like kernel because dt2w is working great along other features. Now, I switched back to faux, and phone is never hot like on semaphore.
[Nexus 4 Original Android Development] twowheeler:
Semephore used to be a bit hotter than other kernels in the beginning. Latest releases are a lot cooler for me at least.
[Nexus 4 Original Android Development] vampire36:
Can someone tell me their exponential brightness settings...

I am currently at 80-114...looks good :)

Btw do i need to off auto brightness settings to use exponential brightness...or it works same as linear with range slightly different ?
[Nexus 4 Original Android Development] Gu$houn*:
AFAIK the auto brightness doesn't work with exponential brightness.

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] stratosk:
Auto brightness should work.

Kernel driver will continue to receive brightness level from framework.

But as you said the range will be different (much more).
[Nexus 4 Original Android Development] lndulgence:
Before it was like more than 6 fingers needed for the the screen to become responsive again, now it's only 5. Kinda funny tho :D But still, awesome kernel. Thank you Stratosk!
[Nexus 4 Original Android Development] Gu$houn*:
Oh, sorry, it was meant as one hand and I completely forgot I have six fingers on each. :D

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] manpildo:
Okay, here is the kmsg that I saved after the boot. Couldn't find last_kmsg anywhere, though I have logger enabled.

Can anybody tell me what's causing my phone to shut down looking at that log?
[Nexus 4 Original Android Development] Midomad:
Stratos it's been a while...hope you're fine bro!

My mako is on the need of you're magic kernel.
[Nexus 4 Original Android Development] Fenvarien:
Stratos was on vacation ;)
[Nexus 4 Original Android Development] stratosk:
New version 2.4.0

- Linux kernel 3.4.103

- ondemand: a small fix in check load condition (thanks to moddingg33k)

- tick-sched: Remove unnecessary statistics calculation required by mpdecision (thanks to moddingg33k)

- tick-sched: A couple of fixes from mainline
[Nexus 4 Original Android Development] Italico:
Thank you for the update.

I have a problem, sadly: I can't tick the 'disable touchwake during calls' option to ON state, because it is grayed out. reboot does not help...
[Nexus 4 Original Android Development] stratosk:
Are you sure that you have enabled 'Touchwake' in 'Tweaks' tab?
[Nexus 4 Original Android Development] Italico:
Stratosk, I feel guilty now... you're right! I disabled it for some days and I wanted to switch it on again, but instead I only worked on the SAI tab! Sorry...

BTW, it works perfect!

---------- Post added at 12:53 PM ---------- Previous post was at 12:31 PM ----------

Me again, Stratosk [emoji6]

I forgot to kindly ask you what I could do to save a bit of juice without sacrificing the performances...

For now, I have changed from standard settings:

- ondemand up threshold to 99;

- touch load threshold to 100 (to disable it);

- unticked 'IO is busy'

- hotplug threshold to 50;

- down time counter to 2;

- minumum online cores to 1;

- SD buffer readahead to 2048kB.

It seems ok, fast enough (can't tell the difference from the standard settings performances).

Thanks in advance!
[Nexus 4 Original Android Development] stratosk:
Please don't feel guilty... It happens to everyone :)

About your question:

Yes, your settings are less aggressive. I think they will help if your phone usage is also less "aggressive".

I mean that lower frequencies don't always lead to less consumption. But you can try these settings.

I think your read ahead value is too high. You always get 2MB of data on every read operation.

Finally, try to use a lower brightness. I think display uses more power than the CPU.
[Nexus 4 Original Android Development] Italico:
Thank you for the suggestion.

For sure, I will not lower the max freq, because... well, I think that we have to use our powerful phone, not restricting the performances to mid-level territory!

But I think it is good to optimize the CPU usage, as you did with ondemand frequency calculation.

Now, I have lowered SD readahead to 512kB, let's se...

Just asking, does No-op scheduler (default, and my choice too) have any advantage over deadline, that seems one of the preferred ones?
[Nexus 4 Original Android Development] vampire36:
[MENTION=3750240]stratosk[/MENTION] : Hi bro...Hope your vacation going well and you enjoying :)

As usual Semaphore rocks as a die hard fan have no complains...Just perfect :)

Another post expressing the same...

http://xdaforums.com/showpost.php?p=54936249&postcount=837

Now I would be making a request just like dt2w days...when I made the request and told you to keep in mind even if touchwake was there and voilà one day you finally worked out the best implementation of dt2w till date :)

On similar lines if you could look into some sound patches even minimal would do...I know there exists Jolie which adds this to Semaphore yet I would be extremely pleased if you kept this in mind if someday just include some patches for sound improvement with simple profiles like synapse provides to adjust sound into semaphore nothing like it...

As dumb as it may sound this request might be an outcome due to as I said sheer love for Semaphore even for a small thing going away from it and using another devs kernel even if its same base with just sound patches it kinda somewhere bothers me :P So maybe if you could just give it a thought and add up as and when you get time would be great.

Thanks again and whatever you decide...as the post I quoted says...roms keep changing...but kernel just 1 :)
[Nexus 4 Original Android Development] stratosk:
Noop is the simplest scheduler. Actually, it does not perform any special algorithm for read/write.

That's why is my choice. :)

Hi,

Vacation was over 2 weeks ago. :(

But it was fine :) thanks. I hope you enjoy yours too.

Thanks for your kind words!

I'm sorry no thoughts about sound patches at the moment. Maybe in the future. :)
[Nexus 4 Original Android Development] karthi89:
Maybe > No [emoji1] [emoji1]
[Nexus 4 Original Android Development] domg73:
Thanks for the new version :)

What about "Suspend DT2W by Power Button"?

When screen is turned off by power button dt2w get disabled to save battery... I think it comes handy when you need to save some battery (low charge) or when you know you would not use the phone for some hours (night)...

Much easier than opening Semaphore Manager and untick dt2w.
[Nexus 4 Original Android Development] xflori:
is something wrong with the new version o.O?

I updated and the battery consumption is huuuuge
[Nexus 4 Original Android Development] snak3ater:
There shouldn't be that much of a difference in Battery Life.Check you Apps for battery drainage ..

It's the same Semaphore kernel with added Awesomeness:fingers-crossed:
[Nexus 4 Original Android Development] xflori:
i changed nothing no new app or anything
[Nexus 4 Original Android Development] snak3ater:
It's not just the new apps,Old apps can also misbehave anytime..You never know.

Try Gsam,Wakelock detector or better battary stats..Try any of these apps to track down this high drainage problem.
[Nexus 4 Original Android Development] xflori:
flashed a older version and its much better,.
[Nexus 4 Original Android Development] stefat77:
Battery life with new version is good for me but performances are decreased a lot :eek:

With 2.3.3 i had 21xxx antutu points and now with 2.4.0, after some tests, the best score is 18360.... should I try a full wipe and clean install? :confused:
[Nexus 4 Original Android Development] Fenvarien:
Semaphore 2.4.0 works just fine here. Antutu and similar synthetic benchmarks can't measure the real world performance and smoothness of a device.
[Nexus 4 Original Android Development] stefat77:
I'm sorry for my post on this morning... I talked too soon... after a reboot a had 21200 points on antutu and my n4 is smoothly. :victory:
[Nexus 4 Original Android Development] DontPushButtons:
Why not just use one of those apps recommended and track down what's causing the battery drain? Or just keep using an old version forever.. Lol

Troubleshooting problems requires time and effort on your part.
[Nexus 4 Original Android Development] snak3ater:
+100 :good:
[Nexus 4 Original Android Development] Italico:
Hey there!

I was just going to try another kernel (because of the instinct) but then I decide to remain still on Semaphore (using my rational mind). I would like a bit more performance, but... Stratosk kernel just just goes, no problem so far, no headaches of any sort.

May I ask the function of up/down timer counter? I am curious about, and it would be interesting for anyone who likes to tweak the settings on their needs.

I searched for, in the thread, but found nothing...
[Nexus 4 Original Android Development] juhwie:
Battery drain caused by wireless charging/QI?

I also partly experience an extreme battery drain after the last updates.. For me it seems to be related to wireless charging. If I just recharge by cable the consumption is <<2% per hour in standby. After charging by QI (or even on the charger!) this jumps to >>6% caused by "Android OS" or "Kernel" in battery trackers.

Looks to me like wireless charging starts a process that kills the battery. After rebooting it seems ok, but the wireless charger can not be used...

Can somebody confirm?

Cheers, Juhwie
[Nexus 4 Original Android Development] sitong1991:
good will try soon thanks
[Nexus 4 Original Android Development] migueldbr:
[MENTION=3750240]stratosk[/MENTION] may i request sweep2dim?its very useful imo...
[Nexus 4 Original Android Development] vampire36:
[MENTION=3750240]stratosk[/MENTION] : Do have a look at 'lower i2c clockrate' finding whenever you have time...battery saving with it ? if that can be added to improve semaphore further
[Nexus 4 Original Android Development] snak3ater:
It can have a big impact in Hammerhead when coming down from a clock rate of 50Mhz to 19Mhz.

If you look at Mako kernel sources,We are already running i2c at 24Mhz.So i don't think that bringing it down would save any power :)
[Nexus 4 Original Android Development] stratosk:
I'm not aware about it. What is it?

I'm also not aware about it. Can you post any links?

Reading snak3ater's post it doesn't sound very useful. :)
[Nexus 4 Original Android Development] Gu$houn*:
Sweep to dim uses swipe over navbar to set the brightness level lover/higher.

P.

[sntfrmnxs4]
[Nexus 4 Original Android Development] Fenvarien:
[MENTION=4363175]migueldbr[/MENTION] Many ROMs have the option to swipe over the status bar to change the brightness. IMHO this is something you should ask your friendly ROM dev ;)
[Nexus 4 Original Android Development] vampire36:
https://github.com/AICP/kernel_lge_hammerhead/commit/723c44a5c53f47e730ea6812c9e789aaf9cd2995

Sana Venkat Raju from Code Aurora dig it...though nothing drastic as hammerhead yet i feel it can improve mako battery too :)
[Nexus 4 Original Android Development] migueldbr:
it is a very useful feature imo..check the video from the furnace kernel thread ( http://xdaforums.com/nexus-4/orig-development/kernel-furnace-1-0-0-nexus-4-t2817681 ), the sweep2dim demo starts from the 20 second mark.

thanks for the reply, but statusbar brightness control has nothing to do with sweep2dim. check the link in this post to understand what sweep2dim is=)
[Nexus 4 Original Android Development] snak3ater:
Can we have sweep2sleep & sweep2dim both working at a same time?

Also.. Is there any difference between swiping on statusbar or swiping on navbar to change brightness?

One feature is integrated in the rom & the other feature is integrated in kernel. But both doing same job. I find both the same [emoji3]

Ps: Not asking to include these in the kernel, just curious to know more about this feature
[Nexus 4 Original Android Development] vampire36:
I doubt...had a chat with savoca too...sweep2sleep and sweep3dim are mutually exclusive...so only 1 of them can work not both...logically too if both activated kernel won't know what to prioritize...dim brightness...or put to sleep...then you might need to look at it from direction point...maybe like right to left sweep2dim and left to right sweep2sleep :P which would be super complex...:)
[Nexus 4 Original Android Development] zakk87:
hi [MENTION=3750240]stratosk[/MENTION] I have problem with multiRom on your Kernel. MultiRom said: "doesn't have kexec-hardboot patch!". Can I do something to run MultiRom on your super kernel?

Regards
[Nexus 4 Original Android Development] migueldbr:
ok mate, you are missing the point on sweep2dim but i will try to explain it the best way i can. So when you swipe on the statusbar you either go between the minimum and maximum brightness that the android os allows right?lets say you are in a dark room and swipe the status bar to the minimum brightness. to some people(me for example), the minimum brightness is still too high. With sweep2dim enabled, when you swipe from the right to the left on the navbar, it lowers the brightness even further from the minimum allowed by android (it lowers the rgb values by 73 or something like that, i dont really know the details). And if you keep swiping it continues to lower the brightness even more. You can actually have almost 0 brightness but sweep2dim has a smart security setting so that you dont get stuck with a completely dark screen and no way to see what is on the screen. When it detects it is almost completely dark it triggers the power button and turns the screen off, and when you turn it back on its back on the minimum brightness allowed by android.

btw yeah, you cant have sweep2sleep and sweep2dim enabled, but some kernels have the option to have either one or the other enabled, it lets the user select which one he wants!

oh and sweep2dim can work parallel with autobrightness, which makes it even better=p