yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] BlueFlame4:
Doesn't this kernel have any hotplug options (aka all cores are always online)?

Even if i turn on MPDecision, they're still online o_O

Thanks in advance! :)
[Nexus 4 Original Android Development] Alex0901:
AW: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

No..

Here it works.. Kernel are offline..

Stock settings without any changings..

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Original Android Development] galaxys:
After a few days, no kernel issues and battery life seems better!
[Nexus 4 Original Android Development] Ieatnoobs:
Re: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

Battery life is really good!
[Nexus 4 Original Android Development] Vahndroid84:
guys do i need to flash something particular coming from franco? Im in stock with franco kernel now...and i wanto to return with harsh just to make a little comparison :)
[Nexus 4 Original Android Development] renna1992:
just to make sure dirty-flash your rom (and gapps) first and then harshs kernel :)

it SHOULD work without flashing the rom first but just to be on the safe side :)
[Nexus 4 Original Android Development] Vahndroid84:
im in stock now...so i need to reflash the system image? :confused:
[Nexus 4 Original Android Development] ctfrommn:
If you are stock, flash the stock reset kernel here http://faux.androidro.ms/mako/mako_422_reset_kernel.zip or here http://xdaforums.com/attachment.php?attachmentid=1737875&d=1361118181 and then flash Harsh.
[Nexus 4 Original Android Development] undercover:
Gents, I must be blind. I'm looking for stock 4.2.2 UV+gamma (no hsic fix). I'm sure Harsh posted it somewhere, anyone got a link? THanks.
[Nexus 4 Original Android Development] ctfrommn:
It was in his devhost folder but I dont see it anymore....I think he pulled it.
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

Harsh do you have that version available with FauxSound patch? If so can you please post it?

stock 4.2.2 UV+gamma+faux sound patch (no hsic fix)

Thanks much!

Rome
[Nexus 4 Original Android Development] Lownita:
Currently thinking: Would halfbreed look like this

echo "208 [COLOR="Red"]64 [/COLOR]68 118 0 25 4 66 [COLOR="Magenta"]32 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 [COLOR="Red"]64 [/COLOR]68 118 0 25 4 66 [COLOR="Magenta"]32 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 [COLOR="Red"]64 [/COLOR]68 118 0 25 4 66 [COLOR="Magenta"]32 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_b

or like this?

echo "208 [COLOR="Magenta"]32 [/COLOR]68 118 0 25 4 66 [COLOR="Red"]64 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_r
echo "210 [COLOR="Magenta"]32 [/COLOR]68 118 0 25 4 66 [COLOR="Red"]64 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_g
echo "212 [COLOR="Magenta"]32 [/COLOR]68 118 0 25 4 66 [COLOR="Red"]64 [/COLOR]1" > /sys/devices/platform/mipi_lgit.1537/kgamma_b
[Nexus 4 Original Android Development] DynamicRam:
The first one
[Nexus 4 Original Android Development] Harsh:
Re: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

Compile new build today.

My regular kernel, and also stock with faux sound as undercover asked for.

Sent from my Nexus 4
[Nexus 4 Original Android Development] fluffenforliberty:
Re: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

No more performance/smoothness to squeeze out? :P
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.35] Harsh Kernel build Mar-12

I hope battery life get even better. :p

Here is mine today,

Fyi, its 3G all the time, dont have wifi so no wifi. Sync on.
[Nexus 4 Original Android Development] BlueFlame4:
There's a possible WiFi-Fix around. Is it already included in the kernel or are there plans to merge it?

Thanks in advance for your answer!

Blue
[Nexus 4 Original Android Development] sean222:
This script is included with Xylon Rom by default in /system/etc/init.d ... is any of it harmful to Harsh kernel? I removed echo "1024" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; since Harsh uses 512.

#!/system/bin/sh
# PrimeDirective, Sonicxml, DHO, Nuclearmistake
# With inspiration from DroidTh3ory

sync
sysrw

MTD=`ls -d /sys/block/mtd*`;
LOOP=`ls -d /sys/block/loop*`;
RAM=`ls -d /sys/block/ram*`;
MMC=`ls -d /sys/block/mmc*`;

for j in $DM $MTD $LOOP $RAM;
do
echo "0" > $j/queue/rotational;
done;

busybox mount -o remount,noauto_da_alloc,nosuid,nodev,noatime,nodir atime /data /data
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier =0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodir atime,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodir atime,barrier=0,nobh /cache

# Enable Sysctl Tweaks
sysctl -p /system/etc/sysctl.conf

# Set SD Card Cache
echo "1024" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;

# Breaking the lease
echo "15" > /proc/sys/fs/lease-break-time
echo "-16" > /proc/1/oom_adj;

# TCP Tweaks
echo "0" > /proc/sys/net/ipv4/tcp_timestamps;
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse;
echo "1" > /proc/sys/net/ipv4/tcp_sack;
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle;
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling;
echo "5" > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo "30" > /proc/sys/net/ipv4/tcp_keepalive_intvl;
echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout;
echo "404480" > /proc/sys/net/core/wmem_max;
echo "404480" > /proc/sys/net/core/rmem_max;
echo "256960" > /proc/sys/net/core/rmem_default;
echo "256960" > /proc/sys/net/core/wmem_default;
echo "4096 16384 404480" > /proc/sys/net/ipv4/tcp_wmem;
echo "4096 87380 404480" > /proc/sys/net/ipv4/tcp_rmem;
setprop net.tcp.buffersize.default 4096,87380,404480,4096,16384,404480;
setprop net.tcp.buffersize.wifi 4096,87380,404480,4096,16384,404480;
setprop net.tcp.buffersize.umts 4096,87380,404480,4096,16384,404480;

# Battery Tweaks
echo 500 > /proc/sys/vm/dirty_expire_centisecs
echo 1000 > /proc/sys/vm/dirty_writeback_centisecs

# Unknown
echo "-16" > /proc/1/oom_adj;

sync
sysro

Thanks.
[Nexus 4 Original Android Development] odeccacccp:
Which ROM is that?

and Harsh as is?

Thanks
[Nexus 4 Original Android Development] Harsh:
For you both, Update is ready... :D

Sotck 4.2.2

with UV, Gamma, and faux's sound (no hsic fix)

Download link: http://d-h.st/8z8

Will post in OP too if anyone want to get it later, easy searching.

I would not want to change anything in wifi for this release, would test that version of Prima drivers first for power consumption and notifications before integrating it into kernel.

And for rest of friends :D

Here is new build March 21, nothing new from previous build, just updated linux version as in kernel.org. And nothing broken either :D...

Download build March 21: http://d-h.st/qdA
[Nexus 4 Original Android Development] mkamal23:
So.... what EXACTLY do I have to do to get this? lol
[Nexus 4 Original Android Development] undercover:
Tried reflashing stock images?

Harsh, thank you very much. Although it seems notifications are not bad at all on later builds. Will compare over the weekend.
[Nexus 4 Original Android Development] odeccacccp:
does it happen to you guys, every time I flash Harsh kernel is TeamW Rec. if says I need to fix permission there?
[Nexus 4 Original Android Development] undercover:
I had that at some point but it disappeared by itself. Are you on latest TWRP? I'm sure it's not due to Harsh.
[Nexus 4 Original Android Development] odeccacccp:
Yes 2.4.4.0, I don;t want to say its Harsh, but it only happens after this kernel. It does not go away, it's been happening since March 8 build.

Edit: never mind i figured it out
[Nexus 4 Original Android Development] thebrainkafka:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Hi harsh, awesome work. Really appreciate it.

Im looking for a stock cm kernel with faster/ nominal support including UV and swipe to unlock.

May i ask briefly for a build?

THX

Kafka
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Paranoid android, harsh kernel 12 march

Using PA, Harsh.

UV -75 from stock harsh

Interactive governor, custom tunable (if you want my custom tunable PM me ;) )

And the rest is default.
[Nexus 4 Original Android Development] ashishv:
Pls share your custom tunable here,not via pm.:cool:
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Yes pls

---------- Post added at 07:07 AM ---------- Previous post was at 07:05 AM ----------

Is stock 4.2.2 here uv'ed already same as custom?

I flashed at uv values are same. 1512=1050000
[Nexus 4 Original Android Development] Frenky94c:
This is the PA rom with a specified theme or it is the stock theme?
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Here is my custom interactive tunable:

Beware: it will make your cpu stay at 384 and 1026 longer, and i make it harder to move above 1026, usually it only spend 1% of total cpu usage on 1512 while on default is 5-8%. it depends on your usage tho.

If it doesnt smooth enough for you try reduce timer rate by -5000. :)

Look at my cpu stats, only whatsapp, twitter, g+, tapatalk, and a bit browsing with chrome:

Its Sony Xperia Z theme :)
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Cool thanks, do you turn off mpdecision off?
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

No, i keep mpdecision on.
[Nexus 4 Original Android Development] billydroid:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Anyone else having trouble with the devhost link for the March 21st build?
[Nexus 4 Original Android Development] rubenswing:
yep me too
[Nexus 4 Original Android Development] nokkenas:
Yeah, "Memcache::connect(): Server localhost (tcp 1337, udp 0) failed with: Connection refused (111)".
[Nexus 4 Original Android Development] 75markus:
you can get it from my dropbox : https://www.dropbox.com/s/u1j2kukcki9o9w8/harshkrnl-nexus4mako-Mar-21.zip
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Any reason there is fast charge on this kernel?
[Nexus 4 Original Android Development] ashishv:
To let u charge faster over usb?what else?

:cool:
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Sorry for got to put not, I mean there is no fast charge here.

Is it possible to add?

Its car USB issue for me not charging . just need to disable data transfer.
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

I used thin wire to connect two middle pins on usb end of the cable. Works a treat ;)
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Is implementing fast charge a problem?
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

No idea. :)
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Anyone have issues with trickster? It locks the cores to 384 mhz for me. I don't have any other cpu app to interfere with it

I uninstalled trickster, then rebooted and it was still stuck at 384. Reflashed the kernel again and it's normal now
[Nexus 4 Original Android Development] odeccacccp:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

If mpdecision is on u can't change the more n value, kernel decides on its own

---------- Post added at 09:05 PM ---------- Previous post was at 09:05 PM ----------

@harsh

Can fast charge be added to the kernel?
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Yea I understand what mpdecision is, but it won't go above 384 mhz, no matter what I do.
[Nexus 4 Original Android Development] ctfrommn:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Are you coming from a kernel that didn't have mpdecision? If so, you will need to dirty flash your ROM and then harsh.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Yea that's what I did. It was working fine until I installed trickster.
[Nexus 4 Original Android Development] ctfrommn:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Harsh's kernel doesn't over write the whole ram disk I don't think cause I've had that issue in the past ..... always dirty flash and then kernel to avoid it.

Sent from my blazing bionic Nexus 4
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Think I found the issue. I'm using a liquid smooth nightly that comes with Franco. I just dirty flashed the rom, then harsh. Once I turn off the screen the frequency gets stuck. So it might be the rom+ Franco causing the issue because I don't even have trickster installed
[Nexus 4 Original Android Development] ctfrommn:
Yep, dirty flashing a rom with a kernel without mpdecision definitely wont fix it. Flash the stock kernel in Motleys thread and then Harsh's.
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

I think Franco went back to mpdecision, so it's weird this is happening
[Nexus 4 Original Android Development] ctfrommn:
It depends on what kernel they bundled in the Rom. It could be an older one of his.
[Nexus 4 Original Android Development] ceejay83:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

It's his latest one. Thanks for your help, flashing the reset kernel solved it
[Nexus 4 Original Android Development] themrjason:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Anyone else experiencing sleep of death issues?

Sent from my Nexus 4
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Nope. Too low voltage?
[Nexus 4 Original Android Development] mohit1234:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Yeah I am. I'm on a themed and customized version of Modaco ROM and using TWRP recovery if that makes any difference.

Tried upping the voltage to stock values, didn't help.
[Nexus 4 Original Android Development] Junglist86:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

I am at the moment at motley because the fix is in there and it works very good. I hope you integrate this fix in your kernel!

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] UnitedOceanic:
yupp
[Nexus 4 Original Android Development] thebrainkafka:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

No sleep of death.

How do i use swipe to wake? Amy further APP needed?

Thx
[Nexus 4 Original Android Development] aletto:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

You can enable it with an app such as trickster or use an init.d script. Just search in the thread, or was posted several times already.
[Nexus 4 Original Android Development] thebrainkafka:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Searching with xda app is a pain.

---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------

Anyone?
[Nexus 4 Original Android Development] skatashock:
#Sweep2Wake
chmod 777 /sys/android_touch/sweep2wake
echo "1" > /sys/android_touch/sweep2wake

place it on init.d folders
[Nexus 4 Original Android Development] thebrainkafka:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

OK, and after that its enabled and no need oft further APP?

Could this also be enabled by Trickster?
[Nexus 4 Original Android Development] skatashock:
if your ROM have init.d support, no need for another app like Trickster

on Harsh's, sweep2wake only active for bottom part of screen (navigation bar area)
[Nexus 4 Original Android Development] themrjason:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Can anyone try and post a log of the sod? If not, I can try tomorrow afternoon or something. It happens almost instantly as soon as it sleeps me thinks.

Sent from my Nexus 4
[Nexus 4 Original Android Development] romeoliny:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Hey Harsh,

Have you looked into the WiFi notification delay fix as of yet? I'm not seeing any adverse effects from it and it would be an amazing add-on to your already amazing kernel.

I really hope to see it soon or even perhaps have a few of us run a beta on it with results. No wake locks but on time alerts. The way it should have been when Google put it out lol.

Thanks again!

Rome
[Nexus 4 Original Android Development] Heini_:
Quite often actually. I have two situtations:

1. Device won't wake up from sleep. -> Pressing all keys to reboot.

2. I look at my nexus and it seems like it just rebooted (I have to enter my PIN).

For now I switched to Matrix Kernel to determine if this could be ROM related but no problems with Matrix so far.

Any thoughts on how to fix this? Could higher voltages help? How should I change them?

Are you aware of any of those problems, harsh? Any plans to get fastcharge implemented?

I would really like to switch back to this awesome kernel....
[Nexus 4 Original Android Development] ctfrommn:
Are you running stock voltage or are you uving further? Matr1x uv's better than most.....never had a random reboot or sod with it.
[Nexus 4 Original Android Development] themrjason:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

I don't think it is the voltages.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Harsh:
I have not experienced single reboot or bosd. Can you get me last kmsg when it reboots?

Higher voltages wont help, we need to know the reason first.

And fastcharge I would not implement for battery health concerns.

For wifi drivers I have them, and testing.
[Nexus 4 Original Android Development] ckret:
didnt flash build 21 yet

but never experienced sod or random reboots so far

since there werent significant changes during last versions, could there be problems through build flags?
[Nexus 4 Original Android Development] Higgsy:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

LG and SOD's - its like the Optimus 2x all over again, never got rid of them in the whole time I had the phone. In this situation I would wipe everything inc internal storage install stock ROM/ kernel and monitor, if no SOD's I would then install the ROM of your choice with its stock kernel, if still No SODs install Harsh kernel. Basically see where it starts to fall over. If it is doing the same in stock then its deffo a hardware fault IMO. In fact I have just done the same over the last 2 weeks with mine as mine has just been powering off for no reason a few times a week, and it continued to do it on stock, So I have RMA'd yesterday. I think people need to be doing this kind of investigation before reporting in various threads of their ROMs etc or a Dev can be wasting their time looking I to something that doesn't exist in their work( This is not a dig at anyone!)
[Nexus 4 Original Android Development] UnitedOceanic:
i think it could be hardware related on my end but unfortunately i don't have time the next few days to do a thorough investigation.

i once had a red blinking led for about 1 second after a freeze and a force manual reboot while the phone was charging. i am not really informed on the "red blinking light of death" issue but perhaps i should take a look.

occasionally after quitting a large game on a long day my nexus freezes, this happened with:

liquidsmooth rc1 + harsh 12.03

liquidsmooth daily (20.03) + harsh 21.03

liquidsmooth daily (20.03) + franco #110

stock kernel settings on all variants.

however the "screen of death" instantly appeared with harsh 21.03, never had it on 12.03. it only happened if the phone went on it's own to sleep.
[Nexus 4 Original Android Development] ctfrommn:
Unless youre are running stock Rom, stock kernel I wouldnt assume hardware. The Roms you are listing are probably the cause. I would definitely flash one of the stock Rom's out there and run that a while. Then if no issues you can start experimenting with custom kernels. I've NEVER had a SOD with the stock kernel, so they are definitely related to something is a Rom or custom kernel.
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Using this kernel since months ago, no sod or anything, this kernel is one of the most stable kernel for N4. I am using PA.

If you experienced SoD, grab last_kmsg and post it here, it will help us find what exactly your problem is.:)
[Nexus 4 Original Android Development] Heini_:
How do I do that?

Edit: Nevermind. I will flash harsh and let you know when it crashed again.
[Nexus 4 Original Android Development] Heini_:
Ok, my second issue just occured: I had to reenter my PIN. But the phone didn't restart before. No idea what happened and why.

I have Llama running to enable/disable wifi and change ringtone mode. Could there be a problem between Llama and harsh's Kernel?

Waiting for SOD now...
[Nexus 4 Original Android Development] undercover:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

What radio are you on?
[Nexus 4 Original Android Development] KLoNe1:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

You've mentioned this befits, Harsh. You've also something about custom charging currents; is this still in the works? Charging via USB is hideously slow!
[Nexus 4 Original Android Development] Heini_:
2.0.1700.48

Edit: And hooray, new issue. Freq keeps stuck at 384MHz -> ~7000 Points in AnTuTu Benchmark. Reboot resolves this issue for some time before it starts lagging again. wtf?

I am going to flash my old baseband and the new aokp build and the latest harsh later. Maybe that helps.
[Nexus 4 Original Android Development] mundixx:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Did you turn off mpdecision? I wouldn't touch that :D

Tapatalked from my AOSPA Nexus 4
[Nexus 4 Original Android Development] aimcr7:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Do you use any kernel app? Try clear that app data or uninstall that app then reboot.
[Nexus 4 Original Android Development] ctfrommn:
More importantly, are you coming from another kernel that doesnt use mpdecision? If so you need to flash the reset if on stock Rom or dirty flash your Rom then flash Harsh kernel. This happens to me each time I switch from non mpd kernel to one that is.
[Nexus 4 Original Android Development] Heini_:
I have TricksterMod installed although I am not using it at the moment. Checked the settings and it wasn't even set to do anything on boot.

I cleared data for trickster, removed it from SU access and updated to latest aokp build. I guess that fixed the freq issue but I doubt that it has anything to do with my SOD and reentering PIN issues.
[Nexus 4 Original Android Development] albundy2010:
Re: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

Those are not kernel issues. A kernel will never trigger a pin input request. Its not the way it works.

Your issues are either ROM related , app related or user error related. Probably a combination of the above.
[Nexus 4 Original Android Development] Heini_:
I dirty flashed my ROM, so there shouldn't be a problem.

Right. The PIN doesn't seem Kernel related. Initially I thought so because I assumed that the system rebooted before, but that isn't the case. I'm still not sure about the SOD though. hope I can deliver last_ksmg soon.

"combination of the above"... sounds fantastic :D
[Nexus 4 Original Android Development] thebrainkafka:
AW: [KERNEL][UV][Linux 3.4.37] Harsh Kernel build Mar-21

How mich battery is swipe2wipe using?
[Nexus 4 Original Android Development] oddlyshapedstickman:
The only time I've ever experienced SOD with Harsh is when I used Stock 4.2.2 ROM + Harsh. It usually occurred when connected to 3G, less when connected to WiFi.

Never once have I had a SOD with CM10.1/PA + Harsh.