yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ashclepdia:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03

To be more specific, here are just a few lines I see repeating constantly before the "nativekernelwakelock" error you mentioned Tiny. And they do repeat A LOT lol

StatsProvider(19443): Trace: Finished root operations2013-03-25 14:18:32
I/ReferenceStore(19443): Serializing reference ref_current
I/ReferenceStore(19443): Saved ref ref_current
D/Globals (19443): Wakelock BBS_WAKELOCK_WHILE_SAVING_REF released
E/WriteUnpluggedReferenceService(19443): Destroyed at2013-03-25 14:18:32
I/SmallWidgetProvider(19443): onReceive method called, action = 'BBS_WIDGET_UPDATE' at 2013-03-25 14:18:32
I/StatsActivity(19443): OnCreated called
I/ReferenceStore(19443): Reference ref_custom was not found
I/ReferenceStore(19443): Reference ref_custom was not found
I/StatsActivity(19443): Since: n/a
I/ReferenceStore(19443): Reference ref_custom was not found
E/StatsProvider(19443): Reference from or to are empty: (3, ref_current)
[Samsung Galaxy Nexus] tiny4579:
Quoting myself from rootz from this morning:

These have been uploaded as promised.
[Samsung Galaxy Nexus] tiny4579:
The io_is_busy patch is for Linux 3.4 and the patch does not apply without some backporting or forward porting. Either I'll figure it out or scracth it. The other sysfs interface is above_hispeed_delay which is already in the standard Google interactive governor so by extension in mine.

However, commit e43dde3 -- cpufreq: interactive: allow arbitrary speed / delay mapping -- applies cleanly so I can add that one in without a problem.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Thanks for the help everyone. I installed GSAM and will run a comparo tomorrow. Having the phone work great, then randomly not is quite frustrating and I didn't think it was exclusively kernel related.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

If its any consolation tiny, I'm not having any issues and deep sleep has been running in the high 93s. Battery life is way better then before with the same amount of use.
[Samsung Galaxy Nexus] midnightdevil66:
Interesting... after the excellent 30+ hour run on the battery over the weekend, I got deep sleep issues as of yesterday. I woke up today to see 50% of battery gone after 8 hours. I checked gsam and it was pointing to phone app using it. Then checked trickster and no deep sleep. I rebooted the phone and back to deep sleep OK.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Guys, here's a gsam log. Still having deep sleep issues today.

GSam Labs - Battery Monitor - Export Data

Kernel (Android OS)

Mar 26, 2013 12:04:16 PM

Usage Details

CPU Usage:9m 51s

CPU Usage (Background Only):9m 51s

Keep Awake:1h 48m 8s

App UID:0

Included Packages

Included Processes

irq/379-rtc0

irq/320-modem_u

dhd_cfg80211_ev

vold

migration/1

file-storage

kworker/u:4

kworker/u:3

kworker/u:6

kworker/u:5

kworker/u:8

kworker/u:7

kthreadd

kworker/u:9

kworker/0:0

kworker/u:0

kworker/0:1

kworker/0:2

kworker/u:2

kworker/u:1

kworker/0:3

bdi-default

debuggerd

kworker/u:21

kworker/u:20

sh

ueventd

jbd2/mmcblk0p12

dhd_watchdog

mmcqd/0boot0

mmcqd/0boot1

kswapd0

twl6030-irq

/init

ksoftirqd/0

ksoftirqd/1

irq/206-mms_ts

flush-0:19

cfinteractive

mmcqd/0

netd

zygote

kworker/1:1

flush-179:0

kworker/1:0

kworker/u:19

kworker/u:18

kworker/u:17

kworker/u:16

khubd

kworker/u:10

kworker/u:11

kworker/u:14

kworker/u:15

kworker/u:12

kworker/u:13

dhd_dpc

sync_supers
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Change that to the view kernel wakelocks screen by tapping the drop down menu at the top. Then repost.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Rild looks to have gone crazy. This would in no way be kernel related.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

If you turn Wi-Fi off does it deep sleep properly? Also, I assume your are still on mmuzzy's ROM?
[Samsung Galaxy Nexus] BOY_:
Haven't tried it, I get so much better battery life on WiFi that I am rarely on data. I will say that I've tried multiple WiFi APs in the office and am having the same issues over the last few days (each day, different router) but at home the phone seems to be much more solid. And what's really wild is this afternoon (after the last screenshot), the wakelocks seem to have subsided. This is weird!

I do appreciate all the help, I've always had such good results with this kernel and Tiny has been so helpful in the Mmuzzy thread. I hope I'm alone here and no one else is struggling with these wakelock issues.
[Samsung Galaxy Nexus] klobkelosh:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I think we all get better battery on Wi-Fi! From what I have read, the wakelock on your screenshot (wlan_rx_wake) is likely caused either by your router or by another connected device on your network constantly pinging your device thinking you are a server. Setting a are static ip supposedly helps, if you can do it. Or, kick off other connected devices one by one, if you can, and see which is the offender.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

OK I rolled back to 3.1 to see if it made a difference and so far it's comparable. Still getting WiFi wake lock. So, question I have is were the WiFi drivers from 3.3 replaced when I rolled back or would they stay resident? Reason I ask is no one in the office is having battery issues but me. I don't doubt it could be network related but I want to cover all the bases.

Thanks!
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

The WiFi drivers are in the kernel. You'd still have the newer hostapd file but that's only for tethering.

I'm really not sure but this seems to be an issue that plagues galaxy nexus users even those on stock.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I might be on to something. I'm playing with settings will report back. Before I get too excited, I'm going to flash 3.3 again and test. Will keep you posted.
[Samsung Galaxy Nexus] Kyle C:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

That infamous wlan_rx_wake has plagued both my GNex and stock Nexus7 for months now. I've tried different ROMs and kernels (on the GNex), as well as setting static IP's and disabling DHCP, and disabling dropbox lanshark all to no avail.

As hinted above; I'm able to adjust settings in the router but I'm not able to switch to a different router all together.
[Samsung Galaxy Nexus] ThePlasticBling:
Are there any bluetooth issues or any other issues if you use this with the latest cm10.1? Thanks
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Whatever issues are in cm10.1 will exist with this kernel on Bluetooth. With that said I'm running it fine with no Bluetooth issues on cm 10.1.
[Samsung Galaxy Nexus] tiny4579:
I was able to find a commit that backports the io_is_busy patch so that will be in the next release along with a wifi driver update (still 3.4) and a few other patches.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Got it! Tiny the avoid poor connections setting is the culprit. I've always had it on so I don't know if something changed in the kernel or ROM or the new drivers but once I turned it off my phone started sleeping like a baby.
[Samsung Galaxy Nexus] tiny4579:
That could be it. I may have had that enabled in my stock ROM that had poor wifi drain (I think it's default). I've noticed that I have it disabled on CM. I'm guessing that setting doesn't work quite properly on this hardware sometimes. This has been recommended in the past to be off. I don't know why that setting is there. I'd think even poor wifi connectivity would still be less of a battery drain than 3g as long as it's stable.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Spoke too soon. Today the wake lock is back. :banghead::banghead::banghead:
[Samsung Galaxy Nexus] ashclepdia:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I have a 2 questions for people who have this "wifi wakelock" issue.

1.- do you have the "optimize battery drain" setting ON or OFF in WiFi advanced settings.

&

2.- are you really seeing a big difference in battery life?

I only ask because I've never encountered this issue(but I also rarely use WiFi lol) and I'm just curious :D
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

1) off

2) yes. 15-20% worse.
[Samsung Galaxy Nexus] Kyle C:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

2. I don't know percentages but my Nexus7 used to last roughly four days with moderate use. Now its about 18-24 hours with light use. That's a drastic change.
[Samsung Galaxy Nexus] tiny4579:
I'm not really sure about the wifi issue. It doesn't seem to happen to everyone. BOY_ do you have that issue on 3.2.2 as well?

To keep my xda users up to date. I have 3.4.0 in planning. Updated wifi drivers and various interactive patches are in planning. You know the ones that kevdliu mentioned.

About ktoonservative, it's one of the more interesting CPU governors I've seen or used. I like the idea that hotplugging can be disabled if it gets too unstable. I'm not sure how to port the commit that allows hotplugging on bluetooth to be disabled separately. That should help as I had an SOD soon after using music over BT with ktoonservative.
[Samsung Galaxy Nexus] tiny4579:
What helped fix your wifi wakelock on your N7? Maybe it can help here.
[Samsung Galaxy Nexus] Kyle C:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Sorry I misspoke. My N7 is not fixed, it's stock and suffering the same way my GNex is.

I've come to the conclusion that it really can't be fixed unless you switch out the router that's causing the issue. Obviously that's not really an option for most of us.

As mentioned before, I've set a static IP, disabled DHCP (?), disabled lanshark from Dropbox, all to no avail. This does not seem to be ROM or kernel related. I've been on three different kernels and two ROMs with no difference on my GNex. And my N7 has always been stock. Both are plagued on the same network and only that single network.

Anywho, Tiny, you have a great kernel. Keep it up, I'm a big fan :beer:
[Samsung Galaxy Nexus] artjef:
uPNP disabled on the router?
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Tiny, I didn't test this time on 3.2.2 but come to think of it, this may have been the same issue.

It has to be router related. Since it's the weekend, I'll be home on my he router. If I don't have wake lock issues then I think its fair to say it's my work router setup.

If anyone has had the WiFi wake lock and found a solid solution, I can speak with my network admin and try some experiments.

Thanks again for everyone putting up with my troubles.
[Samsung Galaxy Nexus] gkaurin:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Kyle are you using a router from your ISP or is it an aftermarket, either way if it is the ISP's see if you can swap it out with a different model or ever same if different is not available. If aftermarket you could look into flashing it with DD-WRT or tomato. Both are good firewalls for routers.
[Samsung Galaxy Nexus] tiny4579:
I was planning to release 3.4.0 today and did get everything I wanted in the build basically but I still want to do some more tweaking on the powerHAL as it's not optimal for supporting multiple CPU governors though at least boost pulse should work on interactive, interactiveX, ondemand and ktoonservative.
[Samsung Galaxy Nexus] tiny4579:
I decided to release it tonight. No changelog tonight though. I'll let people flash it and provide some feedback. I like ktoonservative but with hotplugging on it can get unstable but fortunately it can be turned off from the terminal or Trickster MOD.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

97% deep sleep....
[Samsung Galaxy Nexus] marshy73:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

How to turn of hotplugging from Trickster MOD?
[Samsung Galaxy Nexus] tiny4579:
In the section where you pick your governor go to governor control after setting ktoonservative. Then change disable_hotplug from 0 to 1.
[Samsung Galaxy Nexus] tiny4579:
What ROM is that? As much as I love CM the amount of free RAM on that is nice. You may also have fewer apps installed.

Nice to see it running well so far.
[Samsung Galaxy Nexus] Jdely31:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

I don't think I'm getting wake lock issues. I'm running Elemental X with tinys' 3.3 as u can see from the screen shots. Awesome kernel Tiny!!!

View attachment 1846084
[Samsung Galaxy Nexus] SirBindy:
delete me
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Its CM10.0 stable, and I have 47 apps installed but they don't run unless you use them.
[Samsung Galaxy Nexus] tiny4579:
That would be why. I seemed to have better luck with not running low on RAM in CM 10.0. Your user app count is much lower. I can probably uninstall most of my games and apps I never use to free up some storage and probably a bit more RAM but storage I think for the most part.
[Samsung Galaxy Nexus] tiny4579:
No changes. I built 2.1.0-exp1 again to mall as stable.
[Samsung Galaxy Nexus] scadilla:
Question about kernel settings

Hello all,

I am running mmuzzy's latest 4.2.1, was considering trying this kernel out. What I wanted to know is if Franco's app can be used with this kernel? Or if I need to use trickster's app? Any thoughts are welcomed.
[Samsung Galaxy Nexus] code_311:
Sweet, you must have moved over from the Incredible just a little before I did. I used your kernels on my Inc and I was hoping that I might get to enjoy your good work on my new nexus as well. Can't wait to flash!:good:
[Samsung Galaxy Nexus] CovXX:
will this work on 4.2.1 ?
[Samsung Galaxy Nexus] I Am Marino:
I don't see why not as the .1 was basically just the calendar fix as far as I know.
[Samsung Galaxy Nexus] Txwolf1980:
Yes. Ruining it on eclipse build 1, now.
[Samsung Galaxy Nexus] tiny4579:
It should work fine. I don't know what his app supports but most features are similar and kernels usually have the same sysfs interface.

I actually got my nexus the day Verizon started selling it. I just didn't do any work on this phone until a few months ago and just now posted this kernel on xda a few weeks ago and wish I did sooner.
[Samsung Galaxy Nexus] Pender1:
Hey tiny, I'm having some freezing problems with this kernel. I'm running mmuzzy's latest ROM and since installing your kernel about 2 days ago I've had 3 lockups that required a battery pull. Any ideas on why or how to stop this?
[Samsung Galaxy Nexus] tiny4579:
Try to reproduce on stock kernel to check if its an app doing it. Then test for 2-3 days without installing or uninstalling apps or flashing anything. None of the features in mine could cause freezing except GPU and CPU overclocking

Second part is are you overclocked with the CPU and/or GPU?
[Samsung Galaxy Nexus] Pender1:
Underclocked CPU. Was on stock kernel for a couple of days with no changes before loading up your kernel and never had a problem. Had it occur while using 2 different apps that I've had the whole time. Oddest part is I was on speaker phone during the most recent freeze, it didn't hang up on the call and we could still hear each other but the phone was nonresponsive to touch or button presses.
[Samsung Galaxy Nexus] tiny4579:
Try to get a logcat because the phone is not fully frozen. That almost sounds like the touch drivers died until a reboot. That happened to me yesterday. Still not enough to determine if its a kernel issue.
[Samsung Galaxy Nexus] klobkelosh:
This has been happening to me on and off with this kernel as well as stock and Franco kernels. I'm still diagnosing, but i think it might be content adaptive brightness. My clue was when the screen froze (sod) while using the phone, i twice noticed a bright flash in the back light level before black. On a hunch i turned off cab and haven't had another sod... yet.

Edit: So much for that theory... Sod listening to a podcast and trying to open facebook app.
[Samsung Galaxy Nexus] Pender1:
I switched to another kernel for now. If I don't have a recurrence I might switch back and see if I can replicate the problem.
[Samsung Galaxy Nexus] BOY_:
Tiny, reinstated the kernel and turned off the sound options and everything seems to be running great. Thanks.
[Samsung Galaxy Nexus] KennyJive:
And I just came from the DInc to the Nexus. Glad to see a familiar name. Love this product.
[Samsung Galaxy Nexus] code_311:
What app do you recommend to set the kernel parameters?
[Samsung Galaxy Nexus] tiny4579:
Trickster mod. Its quite good. On the play store.
[Samsung Galaxy Nexus] fk.gregor:
What governor are you guys using for max battery life?
[Samsung Galaxy Nexus] fk.gregor:
Is anyone having issues with google play? Songs stop playing randomly.
[Samsung Galaxy Nexus] normanx:
I have always had less issues with CM roms...Even on my Incredible I used CM and your Kernels...
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

I was comparing ram in cm 10.0 vs cm 10.1. Cm 10 wins this category. However either cm is better or nova not redrawing seems to be minimizing lag in cm 10.1. Maybe my new kernels are helping.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

I think it is getting better or I'm getting used to it. Even after uninstalling more apps I still get apps killed and even services killed and restarted. I may have to go back to cm 10 as much as I prefer cm 10.1.

That also means my JB 4.1 kernel will get an update.
[Samsung Galaxy Nexus] tshelby73:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

I agree. Like 4.2 better but everything seems to work on 4.1 especially Bluetooth.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Tiny, I was playing around with ktoonservative and noticed I would lock up when d/l'ing and installing updates from play store and browsing in chrome (ie high load multitasking). I tried with hp enabled and disabled.

Any input on governor settings that might make it more responsive? The screen off performance and battery life was killer even with hp disabled.

So far ix with cfq scheduler seems to be the most consistent balance of battery life, performance, and stability for me. Any thoughts/insights on governors (and settings) and schedulers?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Use stock interactive or interactiveX. I am torn about schedulers but I am favoring cfq, deadline and row.

About ktoonservative, its really new on the gnex as I may be the only one to port it to this phone so far.

If you're having issues, disable all the hotplugging related settings by setting them all to 1. If hotplugging is off it should run a lot like conservative.

Also you may not be locking up the device just pegging the CPU to 100%. There is a difference.
[Samsung Galaxy Nexus] chazzdjr:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

I've been using Wheatley and sio. It's been very stable. Very fast.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Tiny, I've been running ktoonservative all day with hot plug on and actually seems more stable :what:. Will keep you posted.

Thanks!
[Samsung Galaxy Nexus] kevdliu:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Hows the battery life with wheatley compared to interactive or other governors?

It stays at max freq much longer but maybe more frequent c4 state will save battery?
[Samsung Galaxy Nexus] T-Keith:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Wheatley has been much more stable for me. Interactivex always gives me sod.
[Samsung Galaxy Nexus] kmcrane:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Agreed. Ix and my phone don't play. Wheatley is fast, but I always seem to come back to Interactive and cfq.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Whelp, after my 3rd lock up, I'm giving up on ktoonservative. It worked great, until it didn't.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.4.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/30/13

Thanks for the feedback. Unfortunately I'm not in a position to work on the kernel for a bit. Use what's stable. Ktoonsevative was added on request but it was made for another phone so there may be issues with it on the gnex.
[Samsung Galaxy Nexus] marshy73:
I've only experienced a lock up on Ktoonsevative when Hotplugging was still on.

After turning off Hotplug, it's been smooth sailing with Ktoonsevative and good battery life.
[Samsung Galaxy Nexus] tiny4579:
Just a quick update with a WiFi update for 3.4.1 as well as a possible fix some are seeing with ktoonservative. 1.13.0 has been brought up to date with 3.4.1
[Samsung Galaxy Nexus] kevdliu:
I have created a google drive spreadsheet to attempt to gather and organize battery information about cpu governors. The link is here https://docs.google.com/spreadsheet/ccc?key=0Ar5SpYLsGt0WdEdxOE5VS2dRc2N5Z19Id3NyemdiSUE&usp=sharing

This way we can at least get a sense of the power usage of each governor. I will post my data tomorrow
[Samsung Galaxy Nexus] omniatic:
...and let the tweaking begin...

Does the new kernel break WiFi? I'd like to give it a try on CM10.1. Being new on this phone, I'm still getting used to it. Just need a little input when you get some time.

Thanks,
[Samsung Galaxy Nexus] tiny4579:
The op has this info already. But it only breaks wep support. Use 3.2.2 if you need WEP.
[Samsung Galaxy Nexus] EniGmA1987:
I have been using Ktoonservative since it became available and have found the exact same thing. It is unfortunate that hotplugging has so many problems on this phone since Jelly Bean. Thankfully the governor has the ability to turn off hotplugging so it can still run great with that one little tweak.

I am doing a test today with hotplugging on. I am thinking that since the phone locks up when a core gets hotplugged (but only sometimes) then parhaps things are not being routed properly between cores and certain processes are not getting the signal that core1 went offline. My thought is that if I change the tunable so that it doesnt hotplug the second core until load is down below 10% (or maybe even 5%?) then that would mean when nothing is going on the phone should still hotplug, and hopefully this will keep lockups from happening since there is nothing much really going on when load is this low.

I have been doing this test for the past hour only so far, and there have been no problems at all. I will update tomorrow with what I find.
[Samsung Galaxy Nexus] II12yanII:
I just flashed this kernel to try it out and I'm wondering what the nightmare govener does?
[Samsung Galaxy Nexus] omniatic:
Sorry...brain's been trying to absorb too much information in the last two days.

Installed the 3.2.2, interactive and SIO, 230/1200. Already impressed.

Thanks,