yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
Any more information than that? Do you see anything interesting in betterbatterystats or gsam battery monitor or even the regular battery info? I will do some investigation of my own as I'm curious why. I noticed android OS using a lot of CPU on a stock based ROM but not on CM but I think I'll try again and see what's going on. It may not be tonight when I can figure it out but for now use 3.1 if you're having issues and before switching back try to give as much info or logs as you can.
[Samsung Galaxy Nexus] ATTACK:
Yeah, I flashed v3.2 yesterday and as soon as i noticed my phone was getting hot, I switched back to v3.1 right away (Today). I didn't want to chance it, so I didn't take the time to pull any extra info. Everything seemed to be working fine though, I was getting deep sleep and it seemed to be scaling "normally", staying at around 700MHz in use (Gaming, Internet, blah, blah, blah...) with data connection off and only WiFi on but I did notice some lag and of course the heat thing.
[Samsung Galaxy Nexus] tiny4579:
I pulled the latest releases due to issues where the kernel was running the CPU higher than normal and causing Android OS (BBS)/ Kernel (GSam) to use an abnormal amount of battery. It doesn't seem to be an issue on CM but was on stock/AOSP ROMs. It's related to the KSM, cleancache, and zcache I enabled. I pulled them an all seems better. We will see about intellidemand. Hopefully it's stable and it was just the ksm making things go crazy.

So I was able to get another reboot switching from intellidemand to interactiveX. It doesn't seem like they play nice together. I'm debating abandoning all the intellidemand patches and removing all it's code from my kernel for 3.2.1.

Though if you guys want to play with it as is, I uploaded my test 3.2.1 kernel. In the kernel info it says 3.2.1 but that may not be the final build.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Mine locked up twice while using Facebook. It was running hot. But everything else seemed fine.

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

On the test or 3.2.0?
[Samsung Galaxy Nexus] Alpha_wolf:
3.2.1 kernel gave me google screen boot loop not even the boot animations just the google screen not complaining cause it does say "test" on it so bugs will be there but in the toro it gives me that issue

edit---3.1 give same issue im on the BAMF rom idk if its the phone rom or the kernels but yeah im lost on it
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Sorry....3.2.0

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Its fine on stock. Are you running the new bamf? Try a different kernel or check if they did ramdisk tweaks. Either way I can't see anything wrong in the kernel. Maybe a redownload is in order.
[Samsung Galaxy Nexus] Alpha_wolf:
ill try that cause im use the ak diamond ed kernel

edit--

and yes its the new bamf
[Samsung Galaxy Nexus] marshy73:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Reporting 3.2.0 & 3.2.1 Test both no troubles for me in any way.
[Samsung Galaxy Nexus] Alpha_wolf:
ok it was the rom i changed to a nightly of orca rom and tiny321 works fine
[Samsung Galaxy Nexus] Kyle C:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I've been running 3.2.0 since yesterday morning and have had zero issues. Furthermore I had amazing battery life yesterday, much better than my 'good' days. I'm happy.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I'm having deep sleep issues on 3.2.1 test running ix and cfq. Will roll back to see if it solves the problem and report back.
[Samsung Galaxy Nexus] tiny4579:
No deep sleep issues here. It's not kernel related. It rarely ever is. This isn't me being stubborn or ignoring an issue. It's the apps/ROM that decide to do a wakelock. The kernel has no say in that matter. On a rare occasion, there may be a kernel bug causing an OS process to keep a wakelock. The only changes are below from 3.2.

config: disable KSM/cleancache/zcache - seems to be cause of kernel issues

Revert "ksm enabled by default - may be overridden by some custom ROMs"

enabled intellidemand.

Two of the reverts reverted it closer to 3.1 which seems to be working so well.

You know what would help more than rolling back? Actually grabbing logs.

For the record my phone has been deep sleeping for 7.75 of the 9.5 hours it's been booted.
[Samsung Galaxy Nexus] tincbtrar:
Im going to guess wakelocks are app related too because I have no problems with deep sleep on my phone running MMuzzy and tinykernel

I dont use any social media apps (just mobile sites when necessary).

Bluetooth on the other hand is a mess as it disconnects/reconnects too much but this is a 4.2.2 problem I think.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Flashed back to 3.1 and no more deep sleep issues. No other changes. Looking back through my logs and android os was dominating BBS.

I will say on both 3.2.0 and 3.2.1 test I had new frequencies showing up and the phone did not use the 230 MHz state when idle, stayed mostly at 350... I can't explain it, I'm not technical enough to provide more than observed cause and effect.

Maybe I'm just cursed?
[Samsung Galaxy Nexus] Efrenjr15:
Anyone running this on the new BAMF 3.1?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I'm not sure. 3.2 had an issue I could reproduce but no problems with 3.2.1 test. Everything running great. Also some say 3.2 was fine yet on stock 3.2 had issues.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

No worries, I'll wait for 3.2.1 final and install it happily :). This batch just isn't jiving for me. Still love all your hard work!
[Samsung Galaxy Nexus] ArnieG:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Running baked ROM version 8. 3.2.0 ran hot but 3.2.1 is fine.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I can't just do that. What if final has the same issue? Need to figure it out.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

OK...I reinstalled 3.2.0 I made sure that I wiped the dalvik and have had no issues since. I have not installed any new apps, I'm running CM 10, ix, no changes to the gov settings.

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Are you sure it was the flashing back and not the reboot? What did you see in better battery stats under kernel and partial wakelocks?
[Samsung Galaxy Nexus] CondemnedSoul:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Test kernel is working great so far for me, tiny. No issue with what I've used yet. Just wanted to keep you posted.
[Samsung Galaxy Nexus] tiny4579:
Thanks for the update. @normanx, the 3.2.0 version was pulled due to a noticeable issue with the CPU usage ramping up and not calming down and also the higher battery drain. If anything higher than light to moderate usage, the phone would get hot. I don't officially support that version, if you get reboots and don't want to run a test build, flash back to a stable release.

@CondemnedSoul,

Thanks for the update! Looks like the only reported issues with 3.2.1 are from BOY_ and I'm waiting for more info.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Just point me to the test build.... I'm good with anything.....I just don't see it on goo

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Check again it's literally the first one on goo if you check under my Dev page under gnex using the app.
[Samsung Galaxy Nexus] hogowner:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Installed 3.2.1

No problem at all.....I did notice after install phone didn't sleep....all it took was another reboot.....working good so far!!!

Sent from my "Blazing" fast Nexus
[Samsung Galaxy Nexus] aperseghin:
:\ im going to wait for more reports.. 3.1 is working just fine for me, i see no reason to upgrade until all you bleeding edge guys are done testing. (thank you for your testing:))
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

So far so good on the test... Thanks Tiny.

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

This one is better.... Sorry for the double post....

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] tiny4579:
Quick question. Does anyone here actually need WEP to work for WiFi? The WiFi drivers from the Linux 3.4 kernel are supposed to be much better but don't support WEP. Please let me know. I already have a test kernel built with the new drivers and am doing some usage to see how well it works.
[Samsung Galaxy Nexus] ATTACK:
v3.2.1-TEST seem's to be working fine, but battery life seem's to be worst. It could just be me, I don't know. No on the WEP as well

<Ok, my bad... You said you wanted logs... And it was a Info Dump and

not a Logcat

(Misworded) and it provide's more info then just a pic.>
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Why a log cat of BBS and not a screenshot? Doesn't even make sense. There also shouldn't be anything to hurt the battery. I take bad battery claims with a grain of salt without any proper proof.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Tiny, I've been on the road today and 3.1 has been rock solid. I'll flash test again and get you logs tomorrow or Saturday.
[Samsung Galaxy Nexus] ATTACK:
Ok, my bad... You said you wanted logs... And it was a Info Dump and

not a Logcat

(Misworded). It provide's more info then just a pic.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

No worries.

See how it runs after a few charge cycles and your usage patterns are the same as when you ran the 3.1 build. I'd be surprised of anything that has a noticeable battery impact good or bad. Everyone's chips or slightly different. The additional frequencies is probably the only thing I can think of that could hinder battery life. Hard to know if adding them was wise or not.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Sorry if the pics are not helpful.... Was not my intent to upset anyone.

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Tiny reinstated test but did an extra dalvik and cache wipe this time... Seems to be sleeping but it's only been 10 min.

Cross your fingers for me, will report tomorrow.
[Samsung Galaxy Nexus] DavidFlory:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

WPA2 is what I need
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Same here.
[Samsung Galaxy Nexus] tiny4579:
Ok, I get the idea now that it doesn't seem that people will need WEP support. I'll throw in the new drivers on the next release and put a warning in the OP.

Thanks for the feedback everyone.
[Samsung Galaxy Nexus] EvilDobe:
WEP is stupid. I believe you're doing a great service by "blocking" the usage of it.
[Samsung Galaxy Nexus] tiny4579:
I don't think I have anything configured with WEP at my house anyway.
[Samsung Galaxy Nexus] EvilDobe:
I can't imagine anyone, in their right mind, that would.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Tiny, I can report that after doing a dirty reflash of Mmuzzys and test (as close to clean as I was willing to go), everything has settled down. I'm deep sleeping like a baby.

No idea what was causing the issue but it appears to be resolved.
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

Ok. Been on 3.2.1 for 24 hours here's my bbs. 3.2.1 actually fixed a gps wakelock I was having on 3.1.0

Still not sure why I was even getting it (I never got a chance to pull out my computer to run a logcat), but it's gone, now

Great work
[Samsung Galaxy Nexus] tiny4579:
GPS wakelock is not kernel related as I think I've said 100 times in this thread. Are you sure you didn't change anything else. It's not something I can chase down as nothing changed gps related and never has from stock. GPS is strictly ROM code. I'm not going to release 3.2.1 as I am releasing 3.3.0 instead.
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I know you have. And I know it doesn't. Hence the reason I didn't post about it, on this thread. The only reasons I mention it now are

1.that it was showing as a kernel wakelock on bbs

2. Other than moving from 3.1.0–3.2.1, nothing else changed

I'm not saying 3.1.0 was the problem. Just that 3.2.1 fixed it.
[Samsung Galaxy Nexus] tshelby73:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

I'm on Cm10 stable 4.1.2. What version of tiny should I use?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.2.0(4.2.x)/1.11.0(4.1.2) [JB] Updated 03/18/13

It has to be the latest v1 kernel otherwise Bluetooth won't work.
[Samsung Galaxy Nexus] EvilDobe:
Did you, by chance, have GPS turned off when you upgraded your kernel or is it always running? Disabling gps & rebooting is one of the known fixes to the gps-wakelock so maybe you did it on accident.
[Samsung Galaxy Nexus] tiny4579:
New build up!
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Normally, it's always on, given my job. I had actually setup a profile in Tasker to turn it on, when I opened an app that I needed it for. It may have been off, when I flashed the new kernel, but I don't think so because I had opened maps to check in, shortly before flashing.

I'm not even sure why it was showing as a wakelock, at all. Tiny is right. The gps files are in dev and etc, and have nothing to do with kernel, beyond the drivers, which don't change across kernel builds. Maybe the reboot itself, with gps being in whatever state it was in fixed it, and the flash was coincidental. Or it could be that the rom I'm on simply wasn't playing well with that particular version of this kernel. Or, I could be insane (the latter is the most probable). I'm really not too worried about it, though.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

3.3.0 "breaks" wep?

Yep :( and I'm stuck with WEP at home and several of my hotspots. Tiny, are the new drivers something you are working on "fixing" or is this the new direction for the kernel?
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

This is the exact comment I feared. Can you really not switch your home router?

Afaik no one has fixed wep on those drivers.

As for the direction that remains to be seen. I'd like to keep using these.
[Samsung Galaxy Nexus] techspecs:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I'm very much in favor of the newer drivers and have no need for wep. Don't let one user change your direction on you.
[Samsung Galaxy Nexus] BOY_:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

No, just debating if I wanted to go update the dozen devices that are connected via wep or if this was an interim version. Lazy as charged.
[Samsung Galaxy Nexus] pkgnex:
Wow! I'm having a franco.kernel thread flashback. It's like deja-vu all over again.

Most everyone on the franco thread LOVED the 3.4 wifi drivers, but too many people complained about not being able to connect to WEP networks and the drivers were later removed. Kind of hope that doesn't happen here... would be a good differentiation between Tinykernel and Franco.kernel.
[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, after locking myself out of my router (don't ask) everything is smokin!

General question for comment, with the additions of noop and fifo schedulers, what gov/sched combo(s) are working best for everyone? Performance/battery life/other?
[Samsung Galaxy Nexus] midnightdevil66:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Downloaded this kernel and gonna give it a try on mmuzzy. Will report back.
[Samsung Galaxy Nexus] normanx:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Deep sleep is great...

Sent from my TINY powered nexus.
[Samsung Galaxy Nexus] Txwolf1980:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

And I am an idiot. That "gps lock" under kernel wakelock was my kernel keeping gps in the foreground, because I was using navigation. At least that's cleared up, even if I lose my brain card.
[Samsung Galaxy Nexus] techspecs:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I love the fifo scheduler. That is all. Carry on.
[Samsung Galaxy Nexus] artjef:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Coming from the networking world, I think that WEP is being phased out. There are a lot of people who believe WEP is no better than no encryption. In several of the security shows, fairly complicated WEP keys are broken in a matter of minutes. I would not be surprised to see WEP dropped from new drivers for various products this year.
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

WEP should have been phased out ages ago. And it's worse than no security since it provides the illusion of security where none exists.
[Samsung Galaxy Nexus] Azrith:
Oh man... flash backs to easily cracking my neighbors wifi WEP pw and free loading.

Anyways - this update seems to have solved my wifi rx wake problems. I know we talk about kernal not being involved with wakelocks but damn if I didn't get a ton less wake lock with the new version w/ my wifi.
[Samsung Galaxy Nexus] artjef:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I agree, a false sense of security is bad. I did a little more digging, WEP started being phased out in 2010 and should be longer supported by new products or drivers by 2014 at the latest.

All this to say, Tiny please leave the new drivers in.
[Samsung Galaxy Nexus] aperseghin:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

I have no problem with sleep in 3.3, everything seems to be running smoothly so far, I'm glad I skipped 3.2, thanks again tiny
[Samsung Galaxy Nexus] midnightdevil66:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Unbelievable stats on muzzy ROM. Still cranking.
[Samsung Galaxy Nexus] midnightdevil66:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Simply extraordinary battery life! Thank you very much for sharing.
[Samsung Galaxy Nexus] bunnahabhain:
There are two new Interactive patches that some other Kernels have incorporated... Does this one have those patches?

As for WIFI i think it is great that you decided to use the new WIFI Drivers - they should work better for most :)

---------- Post added at 01:32 PM ---------- Previous post was at 01:01 PM ----------

On another note:

Why can't i set color multiplier values over 200 via init.d script? Not possible with tiny kernel? Nothing changes on tweaked values in TricksterMod as well... :(
[Samsung Galaxy Nexus] big blue:
Wow! You don't have to speak with people very often, huh? 4 minutes of talk time in 2 days? Wish I could avoid people like that!
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

On interactive patches, details please. I may already have them. On the WiFi it doesnt seem to work so well for me on idle wifi battery life. Will check again tonight. On the color settings you need to turn off the safety feature for init.d. color control works on trickster mod out of the box. Check the forums for the safety disable script.
[Samsung Galaxy Nexus] midnightdevil66:
Yep, most is texting, browsing, email, etc... I do most of my talking during the week (not much though), weekend is quality time.
[Samsung Galaxy Nexus] kevdliu:
it adds io_is_busy and above_hifreq_delay or something that i think delays cpu scaling when freq is higher than hifreq
[Samsung Galaxy Nexus] Azrith:
Tiny,

While this is far less than helpful to your situation with wifi, I've actually had the opposite happening. On my wifi home network with previous versions of the kernel I would get 50-60% of idle wake locked by wifi rx, now with 3.3.0 - that has been WAY reduced. It's an odd thing though - because other wifi networks (at work for example), I don't have the lock issues at all. I could never quite figure out what it was, but I assume it was something with my router conflicting or some setting that I was overlooking even though I swear I tried mostly everything. Regardless, it was a pleasant surprise to see that wifi rx wake lock reduced WAY down with 3.3.0.
[Samsung Galaxy Nexus] BOY_:
Tiny et al,

I need your help figuring out what's going on with my phone. I was getting terrible battery life on 3.3.0 yesterday and I was running HOT, I figured it was a misbehaving app so I rebooted and everything was great. In fact, amongst the best battery life I've had, Today, however, I'm back to wakelock issues but I'm not running hot and I can't seem to find a misbehaving app. Here is a logcat, can anybody spot what is causing me to not enter deep sleep? I don't want to accuse the Kernel but I'm stumped.
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

Hmm. Nativekernelwakelock errors in logcat. Never heard of that one. Cannot look at this logcat in detail right now but my advice is better battery stats for info particularly the kernel and partial wakelocks and provide a screenshot of that.
[Samsung Galaxy Nexus] ashclepdia:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

It's weird, but looking at that log cat, it kind of looks like to me that Better Battery Stats is whats actually causing an issue.

It seems like it's having trouble finding a custom reference set.

You might need to check the settings in BBS, from what I see that's where errors are coming from and there's a lot of em.

(Personally I've always preferred to use gsam batery monitor, I've found it easier to understand and find exactly which apps are using battery/CPU/causing&holding wake locks. Hell, it MIGHT even be able to tell you if its BBS app that's calling/holding wake locks.. At least worth a shot to quickly install Gsam battery monitor and look thru it. Easily uninstall if u don't like it/can't find info to help)
[Samsung Galaxy Nexus] tiny4579:
Re: [KERNEL]Tinykernel 3.3.0(4.2.x)/1.12.0(4.1.2) [JB] Updated 03/22/13

If this theory is correct, freezing and force stopping BBS should lead to deep sleep.