yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] grisha1:
So, additional to the log I attached before I have now some more information collected:

The problem with messing up the cpu core hotpluging occurs when new kernel settings are set through faux or trixster app. This can be scheduler, frequencies, UV, colors etc. The moment one of this settings is actually applied, things go mad. And if one then puts the device on standby, it will not wake up anymore.

As a workaround one can reboot right after changing settings in trixster (set on boot active), the changes then will stick and everything is fine.

No clue what might be the difference, since it all actually is echoing :confused:
[Nexus 4 Original Android Development] yyz71:
Device not waking up after screen goes off:confused: And s2w not enabled.
[Nexus 4 Original Android Development] bclark:
S2w disabled. Used trickster to set min192 max1134 no voltage and deadline as scheduler.

Phone instantly goes sod but even using the power button to reboot I'm not getting a last kmsg. I'll try it again because I can replicate it

Edit: when phone is asleep, I can hold the power button down for as long as I like it doesn't reboot. Let go and try again and it boots which is likely the reason I can't produce a last kmsg

I tried with system tuner and no sod, even set voltages.
[Nexus 4 Original Android Development] wera750:
The guys getting stuck at 384mhz. Try to reflash the rom gapps and kernel. Some of us had that problem when we swapped back and forth from bricked to other kernels. Turned out mpdecision the and thermald were renamed and causing the problem.
[Nexus 4 Original Android Development] shivasrage:
Woulnd´t be a cleaning script helpful in this case...?

Is it really necessary to reflash the whole ROM....?

In other kernel treads its always talked about to flash stock kernel before

if you getting trouble with custom kernel.
[Nexus 4 Original Android Development] grisha1:
This is not the problem here. And in the OP is a boot.img to reset.

The "problem" is, that this kernel reacts very *****y on changes applied by apps such as trixster or faux. I have it running "default" right now and all is fine.

It would just be nice to be able to change settings such as governor etc. without the danger of a kernel freak out :eek:

Overall: WIth default settings (on demand etc.) it is smooth, but not as smooth as stock but I hope battery life will improve thanks to the more restrictive cpu-scheduling.
[Nexus 4 Original Android Development] show-p1984:
Afaik that problem only exists with 0.75 beta, is that correct?
[Nexus 4 Original Android Development] grisha1:
yes, not with 0.7 and not with other kernels
[Nexus 4 Original Android Development] qpqpqp:
Story for being sidetrack with a nooby question but I can't verify if I have busy box installed or not. Wlan didn't work when after flashing the kernel so I use the terminal emulator to insert the modules and managed to get wlan to work. I am rooted, but I can't seem to find any sign of busy box anywhere.
[Nexus 4 Original Android Development] shivasrage:
You can download busbox from playstore.

When you start the installer you will see if busybox is installed or not.

:)
[Nexus 4 Original Android Development] pixiebob:
with s2w enabled, i have sometimes problem , can't turn on screen by sweeping .i can only waking screen by pushing button power but in this case screen touch does not response at finger ,so i don't have other choice to reboot from my pc with adb reboot. happen already twice, back to V7 that doesn't have this issues.

here last_kmesg + logcat when it happens:
[Nexus 4 Original Android Development] denimjunkie82:
On 0.7 with 192 min and -50 mv across the board and s2w off. This includes over an hour of navigation and a bunch of testing but otherwise light use.
[Nexus 4 Original Android Development] mko000:
Let me quote show-p for you:
[Nexus 4 Original Android Development] Crimsonthunder:
Had a randoom reboot. Her is the last_kmsg. Iam using codefirex rom. s2w enabled, undervolted -125mv.
[Nexus 4 Original Android Development] shr33kant:
Hi all, as promised a while back some screenshots of cpuspy and why this kernel is the best for gamers. :) Thanks for all your work show! v0.75, cm10.1 latest nightly.

Sent from my Nexus 4
[Nexus 4 Original Android Development] show-p1984:
You are using interactive. I have not changed anything in there (it's still in 'mint' condition if you want to call it that way).

I suggest to use ondemand for the time being.
[Nexus 4 Original Android Development] Crimsonthunder:
Do you think interactive governor was the reason for this reboot?
[Nexus 4 Original Android Development] show-p1984:
The kernel panic says so.
[Nexus 4 Original Android Development] Crimsonthunder:
Okay thank you for answering.
[Nexus 4 Original Android Development] chokey84:
recently i used intersectRaven kernel.. i've found that sleep2wake is interesting.. restore nandroid backup to stock rooted rom and flash this bricked kernel.. my n4 is now bricked .. haha.. nice kernel you got here,, thanks.. :) really works..
[Nexus 4 Original Android Development] Anon87:
You did something wrong.
[Nexus 4 Original Android Development] trismegistos:
i think he is joking...bricked kernel -> bricked device :)
[Nexus 4 Original Android Development] shivasrage:
I don´t mind ....it was a little sarcasm thank´s.....for a very "useful" post IMO...;)
[Nexus 4 Original Android Development] qpqpqp:
I flashed bricked v0.75 a couple of days ago. I have to say so far this kernel is the best for me and I've tried a lot. Very good speed, very stable, and keeps phone doesn't get supper heated up like the other kernels. Thanks alot for all your work!
[Nexus 4 Original Android Development] maufega:
Solution display to sleep v0.75

The problem is that the configuration is not maintained

1 Install the kernel and reboot

2 Do not leave the screen in suspension, install and activate the program Trickster, the specifics of the window, press MENU and tap to start / enable

3 Now, most importantly, do not let the screen suspended, reboot and it works fine and gives no problem.

Please test
[Nexus 4 Original Android Development] shivasrage:
Means that every time I set new kernel configuration I have to reboot...or should it work after first one without any issues and I can set kernel values whitout reboot? :confused:
[Nexus 4 Original Android Development] maufega:
No, sorry for google translation

Only the first time

Install, activate and apply program startup menu, after the first restart no problems

EDIT: V0.75 idle screen solution

The problem is that the configuration is not maintained

1. Install the kernel and reboot the system

2 Install and activate "sweep" in the TricksterMOD program, in the "Specific details" window, press MENU and touch to start / enable

3 Restart so that values are applied and after that, there are no problems

Please test
[Nexus 4 Original Android Development] Anon87:
After following the steps above I don't get sod on 0.75 /w sweep2wake disabled.

If i enable s2w the sweep2sleep function works but then sweep2wake reverts back to disabled. Using the power button still works to wake.

Using trickster mod.
[Nexus 4 Original Android Development] pixiebob:
big thanks for your tips, but unfortunately that's not resolve this problem.

i will wait next update who will fix that and disable s2w.
[Nexus 4 Original Android Development] maufega:
Strange, works for me perfect

Two days with v0.75 with sweep, no problem
[Nexus 4 Original Android Development] Anon87:
Do you use trickster mod or another app to control CPU etc?
[Nexus 4 Original Android Development] maufega:
SetCPU to reduce the frequency to 192MHz

Immediately after installation, run trickster and SetCPU and return to restart (in this process do not let the screen into suspension)
[Nexus 4 Original Android Development] shr33kant:
Just so you guys know, I've had a couple of data drops. Very sporadic and completely random; only had two instances where the data has dropped since I flashed two days ago (using CM10.1 Nightly 10.01.13).

I'm going to try flashing a different Rom (CFX) to see if it is CM10.1 related because I've seen a few comments around regarding that it could even be a Rom issue...

I am on 3-UK Network. Sorry for lack of logs; I was at work the first time and just now I was driving.
[Nexus 4 Original Android Development] g5abiera:
Hi showp,

Been using ur kernel since HTC sensation. I like this kernel and find its hotplugging logic the best for my needs. Anyway, Harsh seems to have fixed data drop issues in his kernel. Maybe you can apply those to your kernel too soon data drop issues experienced by some may be addressed.

Looking forward to future releases.
[Nexus 4 Original Android Development] _ice_:
I had two data drops as well. Very minor not as frustrating as faux or harsh kernel tho on those my data drops every 10 minutes. This is a general 4.2.1 APN drop problem. Google needs to fix it. People reported this on stock as well.

My biggest problem is the nav bar buttons locking up. I'm on aokp never had this problem, touch works because if I swipe up I can get to my Google now or messaging or phone app. But I can't push or long press nav bar buttons I'm thinking s2w is causing this. I try to disable s2w but it keeps enabling (using faux 123 kernel app) any ideas? This is the only kernel good on data for me I don't wanna have to flash a bad kernel to compromise data for navbar!
[Nexus 4 Original Android Development] show-p1984:
This problem is not related to bricked kernel. Data is fine on the latest beta.

Only one person reported data issues and I am inclined to believe that it was the general apn bug. (without a log proving otherwise)

You can disable s2w over sysfs (#2 post). Use a init.d script to make it stick across reboots.

However sweep2wake is not disabling the nav bar area (it can't), so this might not be the issue. If something goes south on the s2w part of the kernel it is likely to freeze your whole touchscreen and not parts of it.
[Nexus 4 Original Android Development] _ice_:
Thank you for your fast response, I think you maybe correct. Because now I tried changing nav icon, ROM control keeps fcing :'( I'll send my log cats over to roman and have him check it out, thanks bro!
[Nexus 4 Original Android Development] daishou:
Hey. Can someone link me to the recommended settings for this Kernel?

Thx
[Nexus 4 Original Android Development] FirelordAzula:
Has anyone noticed a reduction in undervolting ability in 0.75? In 0.7 I was able to UV 192MHz to 700mV, 384 to 712mV, going one step up in voltage levels for each clock step. but with 0.75 I cannot have 192 below 800mV; anything lower and I cannot unlock the device after locking it, I get no response from the power button.
[Nexus 4 Original Android Development] g5abiera:
I've been using the same uv settings as before. -187500 on all voltages.
[Nexus 4 Original Android Development] daishou:
Didnt change anything. Had 2 crashes because s2w didnt function properly and the whole system wasnt smooth. Restored back to CM kernel.
[Nexus 4 Original Android Development] show-p1984:
Recommended = defaults

There was no change to the voltages between 0.7 and 0.75.

Didn't see one log in there, or any helpful information for that matter. Thanks for nothing I guess.
[Nexus 4 Original Android Development] FSRBIKER:
I'm getting great performance & very good battery life with 0.7 kernel. No data drops at all, I do get them on Faux kernel so I'm sticking with what works.

What app is best for tweaks, I have been using the Faux app.

Sent from my Nexus 4
[Nexus 4 Original Android Development] romeoliny:
Show-p, I have a lot of respect for you as a dev. I think you're very good at what you do but sometimes the way you answer people is a bit demeaning.

I realize this is xda and most feel the need to ridicule people who don't read or follow threads properly but in the end we are all here to support and appreciate the devs work and help each other.

I know you were responding to someone else but that's my 2 cents anyway. Just something to consider.
[Nexus 4 Original Android Development] benjimatt:
I wouldn't let these people get to you because they can't read an op. I figure if your not going to post a log cat for a dev to fix a problem then you may as well not even say anything.

It's my biggest pet peeve when someone says something about a Rom or kernel then says I went back to bla bla bla. Nobody cares what rom/kernel your on lol.

Anyways I can't wait for sweep2wake 2!!!! It's my favorite and most used kernel feature.
[Nexus 4 Original Android Development] Rafase282:
Well I'm back to this kernel for version .75 if not new version is coming up I will report back after a couple of day/battery cycles.
[Nexus 4 Original Android Development] FirelordAzula:
Alright. Thanks Show.
[Nexus 4 Original Android Development] iKarido:
This post needs to be stickied everywhere! Lots of respect for you show-p. Loving your work since the sensation days.
[Nexus 4 Original Android Development] IImanuII:
hello in the future, you'll develop an app to control features?
[Nexus 4 Original Android Development] giantflash:
Is it really that hard to use the search function? I think he has enough to do and you have the time to use it.
[Nexus 4 Original Android Development] batman368:
hang in there, showp :) life is tough, and to say it with wiser words:

Bullet Tooth Tony: You should never underestimate the predictability of stupidity. (Snatch)

keep up the great work, i know it's tough to stay motivated against all odds, but your work is very appreciated among a lot of people
[Nexus 4 Original Android Development] giantflash:
Don't want to be annoying and I know some others had mentioned this too. I lost 18% battery over about eight hours without doing anything just after a restart. I had fly mode on and GPS, bluetooth etc all deactivated.

BBS shows me that I had just two real wakelocks, "msm_hsic_host" and "suspend_backoff". I know that the first one is a known problem of our device, but I didn't actually thought that it will hold my device awake about 5/7 of screen off time. And I did some research on "suspend_backoff" but didn't find any helpfull solutions.

Because I didn't thought about it, I forgot to make a dump of this with BBS, just made a screenshot. After one and an half hour using it for media playback I made one but surely that isn't what I wanted to show.

I attached both of them so maybe you can do anything with it. I'm on AOKP and your kernel v.0.7 because with 0.75 I always got the SOD problem.

Thanks in advance for any help and if I forgot something than please ask me.

And because I don't think that it is really a bug of your kernel, show-p, I posted it here in the forum so maybe someone could help me. If I was wrong than please just say it.

I had installed this version of AOKP and your kernel after a full wipe about three days ago, so I didn't tried a full wipe like I do normal, because it existed directly after the fullwipe.

In small form:

Device: mako

Android version: 4.2.1 AOKP

Kernel version: Bricked 0.70

Settings: Undervolted about 150-200mv I think, ondemand, 192MHz-1,24GHz

Problem: Two wakelocks from the kernel, "msm_hsic_host" and "suspend_backoff", which hold my device awake 99% of screen off time
[Nexus 4 Original Android Development] sideeffects:
The msm_hsic wakelock is fixed in 0.75. Like you said it has a SOD when changing settings though. To avoid the SOD you can change voltages using Android tuner and set on boot then restart before the phone sleeps (changing anything other than voltages still gave me SOD after reboot).

I would recommend using another kernel though until a new bricked beta/stable is out to fix the SOD as many of the newer developments and fixes are not in 0.7.
[Nexus 4 Original Android Development] giantflash:
oO read all the 76 pages but didn't remeber that it's fixed. Sorry for that. :o

I knew that with the voltage but that isn't really a solution for me because when I change for example the min frequence or the max frequence it gets the SOD anyway. Also I can't, like another user here, change the voltage for 192MHz lower then 800mV, not a big deal anyway but just to mention it.

I hope show-p gets enough time to work on the new version of this kernel, I just love his work, just incredible like on sensation :)

Thanks a lot for the help.
[Nexus 4 Original Android Development] barrybear:
-Deleted post after doing some hard searching-
[Nexus 4 Original Android Development] Mahdi786:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

If you come from Franco's kernel you have to flash a reset kernel you can find it in Motleys thread op.
[Nexus 4 Original Android Development] exadeci:
Is this app https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix useful on this kernel or is this kernel using -discard mount option ?
[Nexus 4 Original Android Development] show-p1984:
discard is a mount option = rom side.
[Nexus 4 Original Android Development] g5abiera:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Hi showp,

Just wondering if you will be implementing the patches that faux released for gamma control.

Thanks
[Nexus 4 Original Android Development] :
AW: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Too bad this kernel is dead, i liked it.
[Nexus 4 Original Android Development] samthe2can:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Dead? show-p1984 last post on here was only a week ago.
[Nexus 4 Original Android Development] raiderep:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

What? Its working fine for me on black bean 7 ROM. Looks more like a case of "if it isn't broken don't fix it" :p

Sent from my Nexus 4
[Nexus 4 Original Android Development] sideeffects:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

But the beta is broken:o(SOD)
[Nexus 4 Original Android Development] rskyline:
Maybe that's why it's called BETA
[Nexus 4 Original Android Development] Ace42:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Showp is busy, or busy with his HTC toys if I'm not mistaken.
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

@show-p1984 I think I know why the SODs are happening. Attached is a picture and as you can see the max screen off freq is set to 192mhz whenever an app changes the settings. I guess it'd be fine but it's grayed out and I can't find the parameter manually either. Hopefully you can point me to it?

Edit: Well I deleted kernel tuner, then went into the init.d script and got rid of all the lines for the error, also changed the max screen off freq to 384000mhz :) Now everything is running great. No SODs.
[Nexus 4 Original Android Development] Sebz4n:
Yo I am having battery issues and it seems that the Kernel is keeping my phone awake. I am using AOKP build two.

I really can't figure out what the cause is, I have uploaded a bunch of screenshots from GSam Battery Stats and Better Battery Stats in this thread: http://xdaforums.com/showthread.php?p=37451238#post37451238

GSam Labs - Battery Monitor - Export Data

Kernel (Android OS)

01/02/2013 07.32.06

Usage Details

CPU Usage:6m 28s
CPU Usage (Background Only):6m 28s
Keep Awake:3h 17m 49s
App UID:0

Included Packages

Included Processes

com.bigtincan.adfree
kworker/u:31
migration/3
kworker/u:30
vold
migration/2
kworker/u:33
migration/1
kworker/u:32
file-storage
kworker/u:35
kworker/u:34
kworker/u:37
kworker/u:36
jbd2/mmcblk0p23
kworker/u:38
kworker/u:39
kthreadd
loop0
loop1
jbd2/mmcblk0p20
jbd2/mmcblk0p21
jbd2/mmcblk0p22
bdi-default
MC_Thread
kcryptd_io
debuggerd
kworker/u:22
kworker/u:21
kworker/u:20
kworker/u:26
kworker/u:25
kworker/u:24
kdmflush
kworker/u:23
kworker/u:29
kworker/u:27
kworker/u:28
kswapd0
/init
msm_sat0
msm_sat1
kworker/u:40
kworker/1:4
kworker/1:3
kworker/1:2
flush-179:0
kworker/1:1
kworker/1:0
kinteractiveup
kworker/u:44
kworker/u:43
kworker/u:42
kworker/u:41
khubd
workqueue_trust
ext4-dio-unwrit
kworker/3:3
kworker/3:4
kworker/3:1
kworker/3:2
kworker/3:0
sync_supers
RX_Thread
kworker/u:4
kworker/u:3
kworker/u:6
kworker/u:5
kworker/u:8
kworker/u:7
TX_Thread
kworker/u:9
su
kworker/0:4
kworker/0:5
kworker/u:0
kworker/0:0
kworker/0:1
kworker/0:2
kworker/u:2
kworker/u:1
kworker/0:3
flush-254:0
flush-254:1
sh
ueventd
ksoftirqd/0
ksoftirqd/1
flush-0:17
ksoftirqd/2
ksoftirqd/3
app_process
mmcqd/0
netd
zygote
kworker/u:19
kcryptd
kworker/u:18
kworker/u:17
kworker/u:16
kworker/u:10
kworker/u:11
kworker/u:14
kworker/u:15
kworker/u:12
kworker/u:13
kworker/2:1
kworker/2:0
kworker/2:5
kworker/2:4
kworker/2:3
kworker/2:2
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

If you want I can upload my init.d scripts. You can then just adjust them to your liking :) I'd recommend adjusting the voltages for sure though, my chip is fast bin.

Placeholder for link to zip with init.d scripts. http://db.tt/LuyXiD0M

PS: don't forget to set the right permissions ;)
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

I don't know if any of you guys still use this kernel but it's still the best one IMHO so I compiled it with some little stuff.

-FIOPS I/O acheduler

-Dynamic FSync (not sure if it's actually working though o.O, i applied the patches though)

-Gamma control (with init.d support thanks to harsh)

-some of the s2w fixes that faux made

-veno tcp congestion (I personally like this one, not sure if it is any better, could be placebo)

I've tried it for a good while and hope it works great out of the box. If not please try to use the init.d scripts installed to change anything. For some reason apps don't play nicely with this kernel.

Defaults are as follows:

-Interactive gov

-192mhz-1512mhz

-FIOPS I/O sched

-default voltage from showp1984 (it installs an init.d script that has the voltages I use, but it's commented out on install, also like I said please adjust voltages with that to avoid SOD)

-s2w on

-gamma... Um, I forgot the exact numbers but once again you'll find them in the init.d)

http://db.tt/OH1h79y7

Hope you guys like it.

I'm no programmer, just a guy who likes this kernel so I won't be able to fix bugs (unless I get help ^_^) but like I said in the beginning I just made some little changes for usability.

(hope you don't mind that I posted on here @showp1984, but I don't think it deserves it's own post when most of it is your work (and none of it mine ^o^))
[Nexus 4 Original Android Development] dakunesu:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

I still use it. still waiting for updates. did he go to a new thread?
[Nexus 4 Original Android Development] Stryder5:
Not that I'm aware of. Was hoping he'd release S2W v2. Been using TouchControl but that is still buggy.
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

No he's been busy with life. Iirc I saw him say he's looking for a job.

You should try the kernel I posted. It feels smoother than before and my internet speeds also seem better (more consistent to be exact)

I'll be adding some more patches today, there are few that have caught my eye.
[Nexus 4 Original Android Development] Rafase282:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

So are you going to keep the kernel updated?
[Nexus 4 Original Android Development] jassycliq:
Re: [KERNEL][DEC.24]Bricked-Kernel|3.4|v0.7|thermalguard|mpdecision|stickyfre q |OC&U

Not updated per se since I'm not even a programmer. Just kanging the crud out of everything :P

In all seriousness I'm just just adding features that I like. Gamma was one of those. If you guys like something point me to it and I'll see about adding it. For ex I'm thinking about fastcharge since one of my chargers is crap, reason I'm thinking about it is because I don't always use it but when I do it takes forever.