yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gohamstergo:
that i can agree with. even tho i do have paid trickster, its always good to be able to have all users on the same level.
[Samsung Galaxy Nexus] Hetalk:
Deal breaker point !

Exact same thought here:good:
[Samsung Galaxy Nexus] aosp:
Everybody loves bonuses and freebies fresh kernel with a side of synapse can't complain
[Samsung Galaxy Nexus] Grarak:
The main reason why I prefer to use synapse is that I can decide myself what features I want to add and add descriptions. And another reason is that trichster mod has not been written by kernels devs. So some descriptions are wrong or missing.
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] I heard you like Windows :p https://play.google.com/store/apps/details?id=org.redscorpio.xfile
[Samsung Galaxy Nexus] poondog:
[MENTION=4608636]bsmitty83[/MENTION]

I just saw your git.. that piggy issue was from my commit? LOL SORRY :D
[Samsung Galaxy Nexus] büscher:
1 hour idle on DirtyV-RSR-2.21.14-early_suspend2: 2.5%/h (1 minute screen on)

Have seen better. best was around 0.8%/h on DirtyV SR 4.

Don't know if this all is kernel related but I'm still on the same ROM. Even did a clean install 3 days ago...
[Samsung Galaxy Nexus] cmoG530:
True, it does sometimes, but that isn't a deal breaker for me though and it doesn't break anything. Plus, I've been installing so many kernels left and right, that I often tend to clean flash a ROM like every other day. As one person said though, synapse will allow those who cannot purchase paid Trickster, a chance to fully utilize kernel settings, so everyone will be on the same page and I support that whole heartedly.

However, I just like and trust Trickster too much (including its interface) to leave it. If huge bugs start coming along (which I hope to God not) then I'll try Synapse, but even then, the dev can probably work on those bugs hopefully. I did download the app though and I'll keep my eyes on it most definitely. :)
[Samsung Galaxy Nexus] Hetalk:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=2853378]Nephilim[/MENTION]

I'm running dirty sr4 on the carbon unofficial build from yesteryday, and it's been running quite well.

Problems that I had on previous build like

1) hot reboots

2) long freezes

3) unlock delay

are all gone.

So far a rock solid kernel.

Awesome job. :good::highfive:
[Samsung Galaxy Nexus] juju2011:
Really I flashed that as well but had a ton fcs and screen would become unresponsive things happened on screen but my touch wasn't recognized had to pull battery to hang up in a phone call
[Samsung Galaxy Nexus] Hetalk:
Did you flash it on carbon?
[Samsung Galaxy Nexus] juju2011:
Yah the unofficial kk
[Samsung Galaxy Nexus] bsmitty83:
Not sure but a lot of people have been saying cm nightlies have been broke since 1/18 , alot of the same issues people have had on my kernel others are experiencing with the ROM , so since everyone syncs with cm , maybe it was a ROM issue as well . not saying it was totally ROM issue , but might have contributed
[Samsung Galaxy Nexus] aosp:
Outdated and lack of omapzoom support is gonna do the same to all kitkat roms soon old tuna hwc hardware composer is causing these recent blanks issues segfaults the logs told me :/
[Samsung Galaxy Nexus] sd3993:
[MENTION=4608636]bsmitty83[/MENTION] could you please add a proper hotplug governor? Or atleast include in the early suspend cpu1 into interactive? Either one of them save a lot of battery! :)
[Samsung Galaxy Nexus] klobkelosh:
Yeah, someone said it was a change to bionic by code Aurora, but I can't find any commits that would have caused it (but I haven't looked all that hard). might try rolling back to a pre 1/18 libc.so anyway to see there is an effect. That said, I'm on cm official nightly and do not experience the problems, but i see the ims errors in log cat. I'm perplexed.
[Samsung Galaxy Nexus] RajatPatel:
I have been on sr4 for almost 8hrs now and I must say this is the best update so far. No lag, no freeze, no unnecessary cpu boosting... nothing. Running on PA-Beta3

Just slight more battery drain than previous version, but its worth it. Keep up the good work...
[Samsung Galaxy Nexus] juju2011:
All is well in slimkat 2.4 :) will try carbon again later
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4608636]bsmitty83[/MENTION] ,not to be a bother,but for sh*ts and giggles,mind if i try your personal build? the actual one you run on your phone..maybe ill have good luck and feel the smoothness you do :P
[Samsung Galaxy Nexus] bsmitty83:
Sure . next time I build , probably tonight , I'll shoot you a pm with a link :thumbup:
[Samsung Galaxy Nexus] pattyboi:):
aye bro thanks! :) btw,sr4 been running wonderful from 6:45 am till now and still going strong,only dropped 20% all day :good: great work

1:D
[Samsung Galaxy Nexus] Blackcrx:
Running slim 2.4 also, and same results as you. Flawless!
[Samsung Galaxy Nexus] fracama87:
Ok fc and freeze happen a lot to me too from today :( cm-remix 2.4.2

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pattyboi:):
we need logs buddy.
[Samsung Galaxy Nexus] fracama87:
I was out, and it was a really bad bad moment (familiar problem, when you need your phone and can't think to anything else)

In the same time my phone is gone out of battery... So no log sorry. :(

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] pattyboi:):
i understand bro,been there before :) just next time if you can,please get us a log,it helps make smittys's life alot easier :)
[Samsung Galaxy Nexus] fracama87:
The strange thing is that like Nephilim it's happened on low battery!

First under 40% started first fc, then on 20% and under 10% 2 frezees, now in charge no problems at all...

Next time I should have the log... I think too is the rom however... The problems are started after last update on cm-remix..

Probably cm nightly is fixed, but noy yet on cm based roms

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Vekhez:
So strange that there are so many different problems that only select people are having...
[Samsung Galaxy Nexus] Hetalk:
Another important thing, I think, developers will like is they can disable settings(which could cause serious issues), that they don't want users to mess around with.
[Samsung Galaxy Nexus] GilGameshn1:
Please check earlier smitty anykernel version . 2% in 4 hours .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] büscher:
Will do that, 4.1%/h now, with very little usage... No wifi, battery saving location, screen dimmed, 3G

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GilGameshn1:
Also with flight mode on 1% in 4 hours. I can't believe this .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] piterdemon:
Can someone made a anykernel version ? Because ramdisk version dont work on miui v5

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] GilGameshn1:
http://xdaforums.com/showthread.php?p=50569791

Heres a kernel I just built , its Anykernel so flash over a ramdisk of your choosing , shoud be more stable

SmittyV-Test

Sent From My Nexus Prime
[Samsung Galaxy Nexus] aosp:
Is this what amazing is? :eek:
[Samsung Galaxy Nexus] büscher:
1 hour airplane mode, 1 minute sot: 0.9%/h

Damn... what is causing this drain with data enabled??
[Samsung Galaxy Nexus] DevVorteX:
Clear all recent apps before running it.
[Samsung Galaxy Nexus] aosp:
We need those timers

You check better battery stats?

[MENTION=4608636]bsmitty83[/MENTION] You gonna merge in the newer WiFi drivers with the fixes below?

https://github.com/android/kernel_common/commits/android-3.4/drivers/net/wireless/bcmdhd

[MENTION=5513848]cod2xnp[/MENTION] is using them here

Bring bcmdhd driver settings up to date · 70abfeb · cod2xnp/android_kernel_samsung_tuna · GitHub - http://goo.gl/1Qwlq5

Also you missed some of these?

timerfd: add alarm timers · 58e05f9 · android/kernel_common · GitHub - http://goo.gl/3Y0hxb

timerfd: support CLOCK_BOOTTIME clock · 73ef089 · android/kernel_common · GitHub - http://goo.gl/RrBMXs

android: lowmemorykiller: add lmk parameters tunning code. · 597e366 · Christopher83/samsung-kernel-msm7x30 · GitHub - http://goo.gl/CqiV1A

android/lowmemorykiller: Account for total_swapcache_pages · f7da93b · Christopher83/samsung-kernel-msm7x30 · GitHub - http://goo.gl/pHvlhg

Power: add an API to log wakeup reasons · 520bc07 · android/kernel_common · GitHub - http://goo.gl/0JfKdH

POWER: fix compile warnings in log_wakeup_reason · 39129ef · android/kernel_common · GitHub - http://goo.gl/F6nOZJ

cpufreq: interactive: fix NULL pointer dereference at sysfs ops · 0ac276e · android/kernel_common · GitHub - http://goo.gl/crJR9N

cpufreq: Interactive: Implement per policy instances of governor · 65f53ba · android/kernel_common · GitHub - http://goo.gl/L18fwp

cpufreq: interactive: delete timers for GOV_START · b430123 · android/kernel_common · GitHub - http://goo.gl/LK0axj

mm: limit growth of 3% hardcoded other user reserve · c9b1d09 · android/kernel_common · GitHub - http://goo.gl/GpXTL9

page-writeback.c: subtract min_free_kbytes from dirtyable memory · 75f7ad8 · android/kernel_common · GitHub - http://goo.gl/ZuW7fN

ping: prevent NULL pointer dereference on write to msg_name · cd998f9 · android/kernel_common · GitHub - http://goo.gl/jksBpf

nf: xt_qtaguid: fix handling for cases where tunnels are used. · 7974d28 · android/kernel_common · GitHub - http://goo.gl/cDMt7g

SELinux: Fix possible NULL pointer dereference in selinux_inode_permissi... · 0b9228d · android/kernel_common · GitHub - http://goo.gl/xFIhvw

netfilter: xt_IDLETIMER: Revert to retain the kernel API format. · 348fbab · android/kernel_common · GitHub - http://goo.gl/QhOmwZ

SELinux: Fix kernel BUG on empty security contexts. · 196bc24 · android/kernel_common · GitHub - http://goo.gl/nLV19i

fix false disconnect due to a signal sent to the reading process · f88ea89 · android/kernel_common · GitHub - http://goo.gl/xOB5OJ

tcp: add a sysctl to config the tcp_default_init_rwnd · 45604c6 · android/kernel_common · GitHub - http://goo.gl/zER93e

android: configs: add TIMER_STATS back, helps with sysrq t. · 7aee29d · android/kernel_common · GitHub - http://goo.gl/Xn7gHK

tcp: add a sysctl to config the tcp_default_init_rwnd · 2266676 · android/kernel_common · GitHub - http://goo.gl/BDTy08
[Samsung Galaxy Nexus] büscher:
Yep I'm monitoring BBS

I'm trying to face down the cause by disabling things like location, wifi scanning, greenifying system apps like fused location etc.

Atm RILJ is causing 88.8% of wakelocks (disabled "scanning always available" in wifi settings). Did not see that before I disabled this option (K9 imap folder push was on top before)

Kernel wakelock was mipi_link (dont remember the percentage, but it was more than 40% for sure) on top, folowed by nfc. now it is powermanagerserice.wakelocks (25%) obviously, followed by mipi_link and nfc.

Com.android.gms is has caused 64 wakelocks in 30 minutes now.

Will monitor and report later
[Samsung Galaxy Nexus] aaron13:
lag

I'm on cm11 with Dirty V 21-02 Ramdisk edition and noticed some lag while while backing out from the app drawer to home en from for example whatsapp to home.

Can this be solved with some kernel setting?
[Samsung Galaxy Nexus] Nephilim:
With all this Synapse talk going on lately, I would like to chime in and say, do not auto install it, I use Trickstermod and will not be switching to Synapse so I would like to not have a conflicting app force installed on my device. I paid for Trickster and although there are issues sometimes, they are easily fixed. I see no reason to switch to Synapse so I am hoping this choice won't be forced upon me.

My settings will at this point continue to be made for Trickstermod btw.

Just my 2cents since everyone seems to have decided we have to use Synapse now. Maybe in the future, when I can add every single setting I have for DirtyV on Synapse I may try it but until then, I'll pass.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ASHURiCAN:
- CM11 latest nightly

- SmittyV-anykernel-2.23

- illinois

- noop 768

- 180k, 1400k, 525k, 180k

- interactive

--> SOD! :(

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] aosp:
Try increasing the min cpu freq from 180 yet?
[Samsung Galaxy Nexus] GilGameshn1:
Flash gs2kernelwipe.zip with cwm -> flash dirtyv 2.20 -> flash dirtyv 2.23 any kernel -> clear cache/dalvik

I am on CM remix and no issues since ~16 hours ago .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] ASHURiCAN:
Will try ... trying now without charger.

Thx, will try.

Edit : Seems to not occur when not in charge ...

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Samsung Galaxy Nexus] Nephilim:
Or just flash the 2/23 SmittyV ramdisk version osm0sis posted. I haven't had a single issue with it since yesterday. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ASHURiCAN:
SmittyV-anykernel-2.23 ?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Samsung Galaxy Nexus] aosp:
Should I wipe before flashing this?
[Samsung Galaxy Nexus] bsmitty83:
2-ply , single finger , circular motion ONLY .........
[Samsung Galaxy Nexus] chongns:
LOL.... can i post that photo? :D
[Samsung Galaxy Nexus] aosp:
Umm I just did but I get the same error BBQ posted below :what:
[Samsung Galaxy Nexus] cdfreak:
Where can i found the 2/23 SmittyV? Its not in the opp
[Samsung Galaxy Nexus] GilGameshn1:
Here ... Take a look

Sent From My Nexus Prime
[Samsung Galaxy Nexus] ASHURiCAN:
Synapsed ? Are you using this one ?

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
No I use smitty one . [MENTION=2853378]Nephilim[/MENTION] mentioned he using synapsed one . so your choice .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] Atento:
I'm getting SODs with DirtyV with no customization. Changing kernel, because this is too unstable, unfortunately.

I thought these freezes were because of neph settings, but after 4 hours of normal usage and default settings I got a SOD.
[Samsung Galaxy Nexus] ASHURiCAN:
Ok, did flashing the way you described me and got a nice freeeeeeze while writing here ! :D

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
Sometimes after flashing new kernel the older scripts left . it will cause some problems I think . it is my experience . always clear Tickster cache a and reboot . always flash gs2kernewipe.zip with cwm if you do not want clear scripts manually . I have smitty-test ... Have some lags but no SOD so far . it could just me . don.'t know . :thumbup: with or without [MENTION=2853378]Nephilim[/MENTION] 's settings .

Sent From My Nexus Prime

---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------

Also see some micro freezes . not so micro :cool: . changing to GPU 384 mhz somehow give me better no freeze time . also with 384 MHz I get 12229 antutu rating . so you can think about the rating of 512 GPU .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] ASHURiCAN:
I'm guessing all that freezes and SODs appear only while on charge ...

Edit: just got a freeze while not on charge! I was surfing on Chrome. Will try Synapsed ...

Envoyé de mon Galaxy Nexus en utilisant Tapatalk
[Samsung Galaxy Nexus] GilGameshn1:
OK ... Did you increase you soc temperature to 75 or higher ? Could help for freezes if not .

Sent From My Nexus Prime
[Samsung Galaxy Nexus] Nephilim:
Synapsed is the one I'm using because it includes ramdisk. If you still encounter lag or freezing wipe data for trickster mod, then reboot and reapply settings. I've been using this with no issue, battery life is much improved also. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ASHURiCAN:
It's 75.

Envoyé de mon Galaxy Nexus en utilisant Tapatalk

---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------

Thx, that's what I'll do ... Will let know how it goes ... :)

Envoyé de mon Nexus 5 en utilisant Tapatalk
[Samsung Galaxy Nexus] Cliff666:
Am I really the only one with this problem? Had this wir early KK Kernels, and for me it is came back with the latest two builds of DirtyV.

Switched back to DirtyV-SR-2.14.14 and everything is working fine.

As ROM I'm using Vanir.
[Samsung Galaxy Nexus] ASHURiCAN:
[MENTION=2853378]Nephilim[/MENTION] until now, everything is running flawlessly ... cross fingers :)
[Samsung Galaxy Nexus] Charmacas:
I am very curious how the new DirtyV will run. Because the test SmittyV runs sooo great. (Besides some micro stutters which are not obviously related to the kernel) With the hopefully added early suspend it could be the bomb of all GNex kernel ever made. ;)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] ak:
I have send 3 month ago a request for have 2 features implemented into app without success.

Trickster is the best app ever but I need an app for new implementation ... I don't want to mess my brain into java code.
[Samsung Galaxy Nexus] GilGameshn1:
First SOD encounter with smitty-test version . I provided some dmesg if help ... Changing to osm0sis version : :)

Sent From My Nexus Prime
[Samsung Galaxy Nexus] büscher:
I also got "micro" freezes today on metalsprings latest build. Nothing undervolted, gpu on 307.

Also battery drain was so bad (12%/h on normal use)... I had to go back to V4 because in the next few days I need my phone urgently.

I'm sorry not being able to send you logs or give more info about the drain, dont have the time atm.

Ps: back on V4 I have an idle drain of around 0.9%/h without airplain mode...
[Samsung Galaxy Nexus] Charmacas:
Yeah if we could make the micro stutters vanish that would be awesome!

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] poo706:
I'm with you on the battery drain on the last bunch of builds. I've been falling back to 2/14 which is pretty decent on battery, although I think I might give 2/10 another try. I can't go back any further because touch wake was still present prior to 2/10 and I'm now hooked on touch control's double tap to wake.

[poo]
[Samsung Galaxy Nexus] pattyboi:):
Everyone's giving issues...I'm just like "whatttttttt"
[Samsung Galaxy Nexus] bsmitty83:
Although I don't have cell data , my WiFi was on the whole time . this was when I was at work my nexus was at home , came home and this is where the battery was at. You can decide if its good or not
[Samsung Galaxy Nexus] DR3W5K1:
It's working fine for me.[OT] Had to send my phone back to factory earlier pita
[Samsung Galaxy Nexus] gohamstergo:
seems really good, but active phones probably never see that X_X. still tho, good battery life in general on your kernel. keep up the good work :P
[Samsung Galaxy Nexus] p34rp34r:
not bad, considering it was awake the whole time. :confused:
[Samsung Galaxy Nexus] bsmitty83:
it was awake because of wifi id imagine or my phone is like me , no sleep lol
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3685904]ak[/MENTION] You don't need anything but the line to run uci, then just follow my instructions here and you're done:

:)

Edit: Since you're doing it AnyKernel style, I'd use the AnyKernel zip to inject the files I mentioned into the underlying ramdisk before repacking.

One of my upcoming evil plans actually; I'm going to make a zip to inject Synapse support into any ramdisk. ;):cowboy:
[Samsung Galaxy Nexus] metalspring:
speaking of wifi, any plans to update the wifi driver at all? If you are using a ramdisk now it wouldnt be too difficult to make it as a module so its easily replacable (for anyone with issues) or maybe not updating to the latest 3.4 version but still updating to a newer version might work?

I always got better reception, performance and stability out of the 3.4 driver myself (But I'm sure any newer version would help too)

Also, how much benefit would there be to compiling as much as possible as modules?

I know one thing would be the ability to add lots of other features while keeping the actual boot.img size to a minimum, but not entirely sure if that makes a big difference or not
[Samsung Galaxy Nexus] Swede2008:
Could somebody link me the bigmem v4 please. I must have accidentally deleted it.
[Samsung Galaxy Nexus] aosp:
https://github.com/android/kernel_common/commits/android-3.4/drivers/net/wireless/bcmdhd

Bring bcmdhd driver settings up to date · 70abfeb · cod2xnp/android_kernel_samsung_tuna · GitHub - http://goo.gl/1Qwlq5

What you think¿ ;)
[Samsung Galaxy Nexus] GilGameshn1:
[MENTION=4608636]bsmitty83[/MENTION] and other great devs and mates here ... Thanks for hardworking ... I think Smitty lack one or two rings in great chain he made for reaching best kernel for GNex ... I am not ruining works of other devs ... Just speaking my exp here . with Smitty 2.23 and settings of omnimetal op that [MENTION=4328678]metalspring[/MENTION] recimmanded settings I reach this rating and no sod so far ... Not battery friendly but speedy ...

Sent From My Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Just a guess, but try your min at 325MHz and see if it fixes it. franco.Kernel had issues with 180MHz causing SODs That's why he moved to 192MHz in the end.

[MENTION=4608636]bsmitty83[/MENTION] I also have a hunch some of the default voltages here might be borderline too low for some devices.
[Samsung Galaxy Nexus] bsmitty83:
Agreed , they used to be stock , but on the rebase they got switched back to UV . I'll also bump up the 180 MHz , even thought 230 or whatever is as far down as I've ever used .

Right now I'm on [MENTION=2838735]aosp[/MENTION] 's commit trail for WiFi . having trouble getting a working build and there's like 3 pages of commits lol , so I'll be on it for awhile .

Thanks as always for the input , it helps tremendously with making this kernel as smooth as possible for everyone .
[Samsung Galaxy Nexus] ASHURiCAN:
It helped so much! No more SOD! ^^ Thx! ;)
[Samsung Galaxy Nexus] büscher:
Wow, decent battery life!

I really cant tell you what it is. I did not change anything as I switched to your V4...

you have a toro, smitty?

I more and more think your newer builds do not like maguros...
[Samsung Galaxy Nexus] bsmitty83:
Yes , I'm stuck on Verizon unlimited data , but I've been thinking about that for a while now and thought its just a crazy thought because I really don't think they're THAT much different . maybe the stock (ish) voltages I'm gonna put back will help
[Samsung Galaxy Nexus] osm0sis:
I'd just bump all your current ones up by 25mV. Probably enough to take everyone with issues out of the borderline zone. :)

My maguro is running like a champ with the current defaults, but not all silicon is made the same!
[Samsung Galaxy Nexus] aaron13:
Terrible lag

After using Dirty v R 21/02 on cm11 I noticed some lag from the app drawer back to homescreen and from watsapp back to home.

Trying other settings in Trickster helped but not fully so I decided to try Dirty V Smitty's R2.23.14Synapsed kernel and deleted trickster mod also.

However it gave a few fc's(googlebackuptransport/Gplay/Swiftkey) and also lags like before.

Opening any app and pressing Home is delaying.

Is there something that can be done to solve this?

Ps. cache/dalvik cache is was wiped and gs2kernelwipe is also used
[Samsung Galaxy Nexus] GilGameshn1:
This i think

And

Sent From My Nexus Prime
[Samsung Galaxy Nexus] AndreiLux:
Just put it into system if the ramdisk is such a fuss on this device. No point in injecting it.
[Samsung Galaxy Nexus] robbnsade:
So coming from the rezound I look at things a little different...downloaded a dual core monitor app I had used before and noticed cpu1 not modulating properly like cpu0 does. Cpu0 follows the set frequencies but cpu1 follows only the interactive set tunables that I have set.

Also tried downloading kernel tuner which I had used before to kill cpu1 on a few kernel tests and it actually worked...had went downhill quick on the rez lol. Just thought I'd mention what cpu1 was doing and see what you guys thought.

BTW... This kernel has always run awesome! My battery life sucks even with the battery I order last month and this made me look into the second core. Running the synapse 2-23 kernel. I am running 180 min freq with not a single reboot or anything! Guess this phone doesn't mind the low n slow :D

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2