yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
If you could convert to WPA to use the newer kernel, I think it has better battery life. The new drivers seem to do better with idle battery drain IMO.
[Samsung Galaxy Nexus] omniatic:
Actually, now that you mention it, I was just about to flash it. My home system is WPA2. Here goes...

...okay, it's in. Too easy, too fast, gotta love it.

Any suggestions on the best governor and scheduler combination?
[Samsung Galaxy Nexus] tiny4579:
You can try default settings. I usually use interactive. I lowered the min on mine to 230 but haven't noticed that much better battery. I have nearly stock settings as far as governor/scheduler go. ROW is theoretically better overall but may slow down more during writes like app downloads/installs. CFQ seems decent but I like deadline and SIO as well. I am indecisive and can't pick a favorite.
[Samsung Galaxy Nexus] T-Keith:
I've been having random reboots lately. Usually when daydreaming. Using Wheatley at 1560.
[Samsung Galaxy Nexus] tiny4579:
Might be the 1560 speed. Last_kmsg please.

EDIT: I may have to bump up the voltage a tad.
[Samsung Galaxy Nexus] normanx:
Is anyone else having any deep sleep issues with this new one?
[Samsung Galaxy Nexus] klobkelosh:
Nope, deep sleeping just fine here
[Samsung Galaxy Nexus] BOY_:
I am at work. Damn wlan_rx_wake... Nothing seems to stop it. :mad:

Not kernel related as far as I can tell but maybe tiny can find a mod/hack/tweak :thumbup:
[Samsung Galaxy Nexus] tiny4579:
Maybe you can get your work's IT to change their router. Check something like wireshark or network log to get a log of the DHCP requests. You may have a lot of router requests. I'm not sure if you can prove the issue to your IT to try to get a static IP. You should be able to set it outside of the router's IP range for static and just copy your current DNS and gateway settings. That is what I've done for my home network.

Weird observation about the the wlan_rx_wake wakelock. BBS reports about 3 minutes and GSam reports over 40 minutes for the same wakelocks. Not sure what's going on. Definitely try network log to get evidence of the wakelocks.

Just wondering if you are subject to the random MAC address issue that shows itself on the stock kernel for some devices. It shouldn't make a difference but a stab in the dark is still better than nothing.
[Samsung Galaxy Nexus] klobkelosh:
Read something on one of the forums recently about Wi-Fi networks with lots of Dropbox users and something about a Dropbox lanshark might be causing the wake lock issue.
[Samsung Galaxy Nexus] EniGmA1987:
Nope, even with a hotplug out value of 5 I still get a system freeze that requires a battery pull. Interestingly enough, I do not get any freezes as a sleep of death, or when the system is idle. The freezes only happen when the phone starts to do something and the second core turn ON, not off. And it doesn't happen always, I went for 9 hours before I got a freeze up. So something just messed up with the hotplug driver or the ROM source itself on this phone ever since Jelly Bean. I never had issues like this back when I was running ICS and I always used a hotplugging governor then.
[Samsung Galaxy Nexus] BOY_:
Tiny, I've run lanshark and I definitely have a crappy plan setup at work. Dropbox traffic, lease renewals, ipv6 traffic despite having ipv6 disabled in our policy settings, its a mess. Tried a fixed IP to no avail, tried lean kernel with "wlan tweaks" (never got a reply on rootz as to what the tweaks actually are).

So frustrating! I sleep like a baby on all other WiFi networks and this is a relatively recent development (past month or so). Argh!
[Samsung Galaxy Nexus] klobkelosh:
Boy, maybe it's time for a dose of Wi-Fi kill...
[Samsung Galaxy Nexus] tiny4579:
People were reporting hotplugging issues since ICS though as I was following leankernel back when there were always issues with the hotplug governor. Try to pull the dmsg after the freeze:

adb shell

su

dmesg > /sdcard/dmesg.txt

Did you have issues on faux's intellidemand? It hotplugs but less aggressively.
[Samsung Galaxy Nexus] EniGmA1987:
I hadnt ever used Intellidemand on this kernel, and it is taken out now right?

Ill try and get a log for you the next time I have a freeze.

Also, I just realized I was a bit dumb and didnt look back at the setting once I tried to set the "down_hotplug" value. The governor on this phone isnt letting me go any lower than 35, which is default. I did change a bunch of other settings, including what value the hotplugging turns the core on so I am testing quite a few things still. I just wish I could properly set the hotplug out value down much lower. Oh well. If I get a lockup today I will pull the dmesg for you Tiny.
[Samsung Galaxy Nexus] EniGmA1987:
Here is the dmesg from right after booting after the phone froze:

https://www.dropbox.com/s/38nwhflqziqepur/dmesg.txt

Do you need me to try and get it while the phone is frozen?
[Samsung Galaxy Nexus] tiny4579:
Yes. On a fresh reboot it wouldn't have much value.
[Samsung Galaxy Nexus] Kyle C:
Tiny, I'm running your lastest (with Mmuzzy's latest FV ROM) and its perfectly smooth and battery life is amazing.

Thank you :thumbup:

---------- Post added at 07:57 PM ---------- Previous post was at 07:14 PM ----------

I suffered from this problem at a home network (that I wasn't able to mess with). After a few months of trying every fix I could on my end I came to the conclusion that it can't be fixed without changing the router at which you're connected too.

Luckily I had everything needed laying around my house for this next part. First, I found a Trendent TEW-647GA gaming adapter (all it really is is a router with one Ethernet slot in the back, for the most part). I then connected that to the existing network. I then configured a router (a cheap Cisco Linksys), that I had used preciously and that didn't cause these wake locks. I made sure it was on a different channel then connected it to the gaming adapter via an Ethernet cable, set static IPs just for good measure and waited to see if it solved anything. My devices are now connected to my new setup and battery is back to "normal" and sleeps like myself after a night on the town. I still see the wake locks in BBS but my battery doesn't seem to be draining anymore than it used to BEFORE the issue. I'm a happy camper. You'll also notice that I didn't do anything that involved messing with the existing router. I simply "caught" the existing WiFi with the gaming adapter and passed it along to a new router of my own.

I hope this helps or gives you an idea to try for yourself.
[Samsung Galaxy Nexus] normanx:
97 percent deep sleep. Great job Tiny.
[Samsung Galaxy Nexus] omniatic:
Working very well on the latest CM nightly.

Got anything to help it charge faster? It's like watching water boil. (lol)
[Samsung Galaxy Nexus] Txwolf1980:
It is fast charge capable. If cm doesn't have a toggle, grab trickster mod, and toggle it there
[Samsung Galaxy Nexus] tiny4579:
Are you hoping for faster a/c or USB charging?
[Samsung Galaxy Nexus] JohnKuczek:
I would be interested in a solution for a faster a/c charge. 0 to 100% takes me almost 4 hours. That's almost double what I got on stock CM10.1 or recall from 3.2 or 3.3. I normally charge at night when I'm sleeping so that's not a big deal, but if I have heavy use I charge on the way home using a high quality car charger that provides a full amp and it barely gives me enough on my drive home to make it to tucking in my tikes...
[Samsung Galaxy Nexus] omniatic:
Faster A/C would be nice. Seems it's a phone issue, as someone else mentioned it on a post about the new stock vzw update.
[Samsung Galaxy Nexus] tiny4579:
Remember the charger output can be the limiting factor. As far as kernel changes, nothing was done that would effect charging rates.

And I meant if your charging was slow over USB or a/c. There is no a/c charge patch as the limiter is only for USB.
[Samsung Galaxy Nexus] omniatic:
I was pretty sure it wasn't a kernel issue. Just thought I'd ask, in case there was a way to speed it up.

Thanks,
[Samsung Galaxy Nexus] jekern77:
Check your charger first...stock charger is a big 1000ma, where as a lot of cheaper ones are only 500ma...same 5V, but less juice behind it makes a much slower charge. Also..don't use daydream...my phone barely maintains charge on USB with daydream, almost loses charge...charge is agonizingly slow on a 850ma charger with daydream active.
[Samsung Galaxy Nexus] EniGmA1987:
Its been 5 days now waiting to try and get another system freeze from hotplugging so I can try to get a log. Still havent gotten 1 freeze in these 5 days yet. It is so weird how completely random the error is.
[Samsung Galaxy Nexus] tiny4579:
With screen on hotplugging all bets seem to be off as far as stability. This phone has already been known not to like hotplugging in use except deep sleep. Hopefully you can turn up something.

For the next build I thought it'd be nice to include dynamic fsync which would be off by default.
[Samsung Galaxy Nexus] zoomy942:
That'd be rad. People seem to think it'll help.

On a stock/rooted rom, it'll be defaulted off still right?
[Samsung Galaxy Nexus] tiny4579:
It defaults to off regardless as the default value would be in the sysfs value.
[Samsung Galaxy Nexus] zoomy942:
Awesome. I've been using stock kernel for a while but that feature will be something I'm very interested in.
[Samsung Galaxy Nexus] tiny4579:
Hey, can WEP users test this build out and let me know if it works with WEP? I saw a commit that says:

net: wireless: bcmdhd: Fix WEP-104 authentication

so hopefully it fixes WEP for you guys.

tinykernel-3.4.2-test1.zip - 3.54 MB
[Samsung Galaxy Nexus] scotty1825:
Tiny I have wep at work. I'll download and let you know how it works when I get to work in a couple of hours.
[Samsung Galaxy Nexus] scotty1825:
I couldn't connect to wep. Worked great otherwise.
[Samsung Galaxy Nexus] tiny4579:
I didn't have the chance to say don't bother. All the same, thanks for testing.
[Samsung Galaxy Nexus] tiny4579:
You WEP users should force your IT to switch from it as it's insecure. Scotty1825, if you can grab a logcat and dmesg after the failed connection, that'd be great. Maybe I'll be lucky and find something that will point to the problem though I don't know of a kernel dev that's figured out the WEP problem with 3.4 on the Galaxy Nexus. Also, to the group:

Can someone still on Android 4.1 test this kernel out and see if bluetooth works? I'd like to have a unified kernel base that supports 4.1 and 4.2, though if I can't do it with just a defconfig I still need two branches. This is also for curiosity as to what specific change in the 4.2 kernel breaks bluetooth for 4.1. I've made a quick revert of one of the 4.1 to 4.2 changes to test and don't have the time/energy tonight to test. I have a feeling it was one or more of the UHID changes and not any of the changes to the board file.

tinykernel-3.4.2-backport-test1.zip - 3.54 MB
[Samsung Galaxy Nexus] normanx:
Yes the bluetooth works now on mine....
[Samsung Galaxy Nexus] tiny4579:
Bluetooth is working on 4.1 with that kernel? Sweet. Maybe this will be the point I can call it 4.0 and just make a jb41 and jb42 version.
[Samsung Galaxy Nexus] tiny4579:
That may not even be necessary. I tested it quickly and it still seemed to power on. Someone can try it on 4.2 as well. It seems this may be working on both versions.
[Samsung Galaxy Nexus] scotty1825:
Sorry I didn't get the logcat for you. I'm going to attempt to change the security on my WiFi at work as soon as I get a chance.
[Samsung Galaxy Nexus] JAKETHESNAKE28:
Hello,

Thank you Tiny for the great kernel! I have used it for weeks and have had great success with it. I have a request though. Lately, I have been running the abyssplug governor on a different kernel that works well for on-screen hotplugging. Is there any way you can implement this into your kernel?

Thanks,

Jake
[Samsung Galaxy Nexus] tiny4579:
I don't really want my kernel to be so bloated with CPU governors that do about the same thing. I already have a hotpluggable governor that can be disabled on user request - ktoonservative. GNex+screen on hotplugging=freeze town. Plus hotplugging doesn't help that much and I've never seen it to be reliable.

The answer is a no. Use another kernel if you need it that bad.
[Samsung Galaxy Nexus] tiny4579:
I haven't heard any feedback on this yet. I know for a fact that I have found a fix that makes the kernel boot on 4.1 and 4.2 but I want to make sure there are no negative side effects with this patch.
[Samsung Galaxy Nexus] normanx:
Well the for 4.1 is great... I'm not having any issues with it at all.... Thanks again dude.
[Samsung Galaxy Nexus] marshy73:
Tiny.. It boot on 4.2.2 just fine for me.
[Samsung Galaxy Nexus] tiny4579:
I was referring to bluetooth not working or having weird issues caused by a change I made. I'm not having any issues on 4.2.2 or 4.1 with this new test kernel but it's good to have additional testers.
[Samsung Galaxy Nexus] ashclepdia:
Regarding my tethering to Xbox issue tiny:

U said try any above 3.3 kernel

I'm on a 4.2.2 ROM

Should using your newest release kernels give me that hostapd you spoke about?

Any and as much info you can provide will be well absorbed and tested soon tonight. This issue had been plaguing me ever since 4.2 came a long in any form. 4.1.2 everything works great. ;)

I will be donations generosity if one of ur kernel versions fixes this. I remember your posts initially concerning the hostapd and such which made me want to try it then vutbhadnt had time. I do Tonigt tho and will for sure post back here and the hotspot issue thread i started if ur kernel drivers/modules tweaks fixes this bug that has been killing me ever since 4.2 :( :D :( :D excited!!!
[Samsung Galaxy Nexus] tiny4579:
If you flash 3.3 or newer it will replace the ROM's hostapd file which has an impact on tethering though you won't be able to use WEP on it.
[Samsung Galaxy Nexus] marshy73:
Aite... Just successfully bluetooth paired with my N7 and transferred some picture files. No problems.
[Samsung Galaxy Nexus] mnbrightblade:
On mmuzzy vanilla so I have no tools for over clocking and governing; anything in particular you recommend with this kernel?
[Samsung Galaxy Nexus] tiny4579:
I always use Trickster Mod even on CM.
[Samsung Galaxy Nexus] mnbrightblade:
That's the one I was looking at.
[Samsung Galaxy Nexus] claytonjn:
+1
[Samsung Galaxy Nexus] ashclepdia:
Tricksters mod is amazing

I remembered when it was a script and app and just starting out.

They really have gone all out on the. My favorite kernel tweaking app.

I've heard redline is also good.

I wish trickster had a way to do some of the system tweaks like u can in system tuner. I lover playing around with tons of parameters and learning about them all.

Hopeful I can built custom kernel one day soon even if just a kamng that i don't release custom for my usage and power lol.

Always wondered what tinys kernel would be like if it only had 384(or537even!}mhz min 920, and 1350mhz max(or 1305 or 1400/1420)

Always wondered how less amount of freqs to choose from, if it would be smoother especially with a tuned ondeman for some reason
[Samsung Galaxy Nexus] claytonjn:
Sorry it took me so long, but I flashed the 3.4.2 test last night. I had no issues listening to music over blootooth during my 45 minute drive to class today, on a 4.2.2 ROM. Also, I like the idea of dynamic fsync.
[Samsung Galaxy Nexus] EniGmA1987:
Well, I have been using my phone for 11 days now with hotplugging enabled (and over 5 days of uptime since I last rebooted) in hopes that I would get a freeze so I could try to pull a log. Unfortunately I haven't had a single problem in these 11 days, still on 3.4.0 version too. I am going to switch over to another kernel to try out the update for a few days but I will definitely be back as this kernel with Ktoonservative has been the best combo of smoothness and battery out of anything I have been on so far. Thanks for all your great work Tiny!
[Samsung Galaxy Nexus] tiny4579:
Tinykernel 4.0.0 is live.

Along with some WiFI driver updates and other small updates the most prominent feature of this release is the bluetooth changes in the board file to support 4.1.x now as well as 4.2.x. The only issue that was holding this back in 3.0 was that bluetooth would not start. I've verified that with this change in the 3.4.2 test and now the 4.0.0 release that now bluetooth works in 4.1 and 4.2 Jellybean.

A secondary promiment feature though not as neat is dynamic fsync. I took faux's dynamic fsync and fixed a bug where dynamic fsync control was always on and applied one of his later enhancements. This is probably my favorite kernel release yet.
[Samsung Galaxy Nexus] tiny4579:
About dynamic fsync:

It's safer to use dynamic fsync over the old fsync but the warning still exists as there's still a risk. I still will leave the disclaimer up and like before it still is off by default meaning normal operation. Before fsync on was normal but now dynamic fsync off is normal as dynamic fsync being on enables the dynamic fsync control.

I am comfortable leaving dynamic fsync on as it will sync on screen off vs being disabled completely with fsync off before. It still carries a risk so enable it at your own risk.
[Samsung Galaxy Nexus] slider112:
Thanks tiny, gonna take 4.0.0 for a spin now :D
[Samsung Galaxy Nexus] artjef:
Up and running on the new kernel with mmuzzy's ROM. Everything is running great.
[Samsung Galaxy Nexus] SL556:
I really like the ktoonservative governor and I realize its still experimental, I just wanted to report that it doesn't seem to be going into deep sleep according to Performance Control. Otherwise everything is amazing. This is the only kernel that really performs like one should with no hangups and it always stays snappy. Great work!!
[Samsung Galaxy Nexus] tiny4579:
Check from here on. I can't reproduce anyone's issue with deep sleep problems:

http://rootzwiki.com/topic/34189-kerneltinykernel-400-42x-412-jb-updated-041813/page__st__1460
[Samsung Galaxy Nexus] tiny4579:
Think I'm taking a short kernel break. No updates until I figure out a deep sleep issue I cant even reproduce myself.
[Samsung Galaxy Nexus] BOY_:
Do you have logs from the rootz thread? I can provide another if you want it. Suspend_backoff is the culprit on mine. Dynamic fsync on or off.
[Samsung Galaxy Nexus] tiny4579:
Logcat and dmesg please. I haven't asked for them yet as if I can't re-create the issue I'm a prove it person but I'll see if I notice anything.
[Samsung Galaxy Nexus] tiny4579:
Ok just to eliminate other causes can someone with the deep sleep issue do a clean install and just load CPU spy no user apps? You can nandroid prior so you can revert back if you still have the issue.

This may be related to people's issues but I don't know for sure

http://mobility.forumsee.com/a/m/s/p12-9248-0234530--google-chrome-suspend-backoff-kernel-wakelock.html

There was a 3.4.2 test kernel back a few pages back entitled 3.4.2 backport. Can someone test it who's having this issue?
[Samsung Galaxy Nexus] EniGmA1987:
Are you sure it is a kernel issue? Like you said on rootz, I have always seen it be caused by issues with apps or the ROM rather than kernel. Unless there are binaries missing which sometimes happens on a new Android release.
[Samsung Galaxy Nexus] tiny4579:
I'm not positive it's a kernel issue. I can't reproduce it and the wakelocks are not even kernel related but yet people who never get this issue seem to be hitting it full force.

Who's with me to try a few test builds?

First one:

tinykernel-test.zip - 3.54 MB
[Samsung Galaxy Nexus] BOY_:
Tiny, I'm having a hell of a time with xda tonight. Won't let me upload anything :banghead:. Anyhoo, I checked chrome first and it's fine (no settings changed after flash, tilt scrolling off).

I was on your 3.4.2 test and it was solid. Will gladly try new test kernels.
[Samsung Galaxy Nexus] tiny4579:
Which test? I did two of them. xda is having issues tonight. It's been offline a lot tonight.

tinykernel-3.4.2-backport-test1 and tinykernel-3.4.2-test1.

Especially If you used the backport one get me the version string after the version number for example on tinykernel 4.0 it's 06502-gf4223f0 after the version. Can you get me that part on the kernel of the one you used? If both were fine let me know as well.

I can pull either by flashing the relevant build since I have the builds but if you can do it quickly it's a bit easier.
[Samsung Galaxy Nexus] BOY_:
I was on test1. Just installed from the link above. Will report back.
[Samsung Galaxy Nexus] tiny4579:
From rootz regarding the new test:

User:

My response
[Samsung Galaxy Nexus] BOY_:
Yep, new test is deep sleeping just fine. :)
[Samsung Galaxy Nexus] tiny4579:
Ok, I got some reports from some users that the new test kernel (first one) fixes their deep sleep issue.

In a way I feel relieved about this being something I caused. I guess dependin on hardware not everyone was having this issue.

So can someone who was having a deep sleep issue on 4.0.0 please test the second one? If it goes well, 4.0.1 might be in business with what I wanted to accomplish still. It's posted above as test2.
[Samsung Galaxy Nexus] tiny4579:
So I can't have my cake and eat it too. It looks like the first test will have to be the release. I wonder if I should call it 4.0.1 or 3.5.0 as the 4.0 was designed to indicate that it can run on 4.1 or 4.2 with working bluetooth. I suppose 3.5.0 as a new release after 4.0 would be confusing since it's based on 4.0.

There is one user on rootz who said test1 didn't fix his issue however he also had the gps-lock wakelock which I am certain is ROM related.
[Samsung Galaxy Nexus] laureanop:
On carbon Rom. Issue fixed. Before and after. Thank you Tiny

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Alton (Halo 2):
Is it safe to oc my GPU to 512?
[Samsung Galaxy Nexus] tiny4579:
If it were super dangerous, it wouldn't be a an option in my kernel. There is the standard risk of overclocking but I haven't seen any fires or issues so far of overclocking. If your phone starts freezing, go down to 384 or 307.
[Samsung Galaxy Nexus] aperseghin:
Ok so at this point between the 2 test kernels and the version numbers im confused.. what should i flash because 4.0 certainly does not sleep. im flashing 3.4.1 now but what replaces that ?
[Samsung Galaxy Nexus] tiny4579:
The first test kernel has reported success. Or if you want to stay an an official one then do so. Test1 will become the next stable. I just can't decide on the version numbering as my hopes in 4.0 was that it'd work properly on 4.2 and 4.1.
[Samsung Galaxy Nexus] aperseghin:
i would call it 4.0.1 because you are not going backwards, you are just fixing a bug that was introduced.

---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------

besides when versioning, you are always going forward. 4.0 existed you reverted some commits to resolve an issue, now you have 4.0.1 thats very common practice

thats why its called a point release
[Samsung Galaxy Nexus] tiny4579:
That is true but the bugfix is actually a reversion of a commit that aimed to have support of Bluetooth in 4.1 ROMs. With that said it makes it seem like it should be 3.5 but that may just confuse people.

Even though it's just a bugfix it reverts key functionality that allowed it to run on 4.1 properly which is why I'm having this dilemma.
[Samsung Galaxy Nexus] aperseghin:
Tiny, just move forward.. version numbers are not based on commits, they are based on releases. 4.0 was released. 4.0.1 is a fix for it, how you fixed that is of no importance to the consumer. always go forward

---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------

also as far as bluetooth goes, when its fixed you can just jump to 4.1
[Samsung Galaxy Nexus] tiny4579:
Tinykernel 4.0.1 is up with a fix for deep sleep for many users. You'll still need to use v1.13.0 for Android 4.1 if you need bluetooth.
[Samsung Galaxy Nexus] Broadleynine:
Agree 100%. Of course this is your kernel and thread so it's obviously your choice but IMO don't go back to the 3's. Not because it might be confusing but because numbers truly don't matter.

Edited for spelling