yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] tiny4579:
The weird thing is that it actually works for the following user on my rootzwiki forums:

He's using ShinyROM - the latest build I assume - and I'm having an issue activating it on the latest Shiny build. Please test PGM and let me know.

About why PGM was not working initially. I built from Google's defconfig to start as close to stock as possible and this change disabled module support. It was re-enabled by me for beta3. Possibly some lingering defconfig updates are needed. See commit from Google:

https://android.googlesource.com/kernel/omap/+/fbc1a9de516ca3539bc28531f452912da284748a
[Samsung Galaxy Nexus] EvilDobe:
PGM works for me on beta 3. I'm using Kevdliu's ROM that I rooted with SuperSU 1.51.
[Samsung Galaxy Nexus] tiny4579:
Works for me now. Only change was that I updated supersu. I think it was an issue with my supersu version.
[Samsung Galaxy Nexus] zoomy942:
This is my battery 2100 with 350/1350. I am trying 230/1200 tomorrow. My usage on work days is very much the same.
[Samsung Galaxy Nexus] zoomy942:
Does beta 3 have the timer slack feature?
[Samsung Galaxy Nexus] tiny4579:
Nope but 4 will. 1440 and 1520 are still unstable for me.
[Samsung Galaxy Nexus] zoomy942:
Agreed. I;ve been using 1350 instead.

That timer slack feature is GOLD.
[Samsung Galaxy Nexus] sonicdeth:
Same here. Still running 1.2. Eagerly awaiting beta 4:D
[Samsung Galaxy Nexus] tiny4579:
Beta 4's up in the usual spots. I would have pushed it up sooner but i was doing other things.
[Samsung Galaxy Nexus] zoomy942:
Thank you sir.
[Samsung Galaxy Nexus] klobkelosh:
So what's the surprise?
[Samsung Galaxy Nexus] zoomy942:
Good call!
[Samsung Galaxy Nexus] tiny4579:
You'll see it if you check out Trickster Mod.
[Samsung Galaxy Nexus] DoesntPostAThing:
...force fast charge? I don't see anything new?
[Samsung Galaxy Nexus] tiny4579:
5.0 is out in the wild. I'm surprised no one saw the surprise yet. It's not new to be honest but it's new for this kernel.
[Samsung Galaxy Nexus] DoesntPostAThing:
timer_slack? Anyways, gonna download 5.0. I never really paid attention to what was in the kernel as unlike other kernels where I like to change around CPU settings, I just head straight to the color options in this one and everything else just works.
[Samsung Galaxy Nexus] tiny4579:
Timer slack wasn't the surprise. What's new is a fix for PGM and a 1.44 GHz CPU slot. The surprise was user voltage control. I refused it for a long time and decided to implement it now.
[Samsung Galaxy Nexus] ba_hamilton:
Same here. It's there a thread where people post their settings? It might be helpful. I want the top secret setting where you get 3 days on your battery. Ha!
[Samsung Galaxy Nexus] laureanop:
Pgm confirmed working on jellybro 08/03 as well as everything else. Great job as usual.

The relentless pursuit of the perfect rom

---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------

Now 4.3 has picked up exactly where 4.2.2 left off, at least with CM 10.2

The relentless pursuit of the perfect rom

---------- Post added at 09:06 PM ---------- Previous post was at 08:22 PM ----------

Tiny what's Google's reasoning in setting the go hispeed load to 99 and the hispeed at 700, while only lowering the above hispeed delay to 80000 ?

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
I don't know why they did it. They're using target_loads in their powerHAL now. I am not using my customized powerHAL now as of 5.0. That could change but I decided to start over with a more stock based kernel and only merge the most important commits.

commit 79a52b3542b2c9bf8072d23205b6b1b3c4f6ed5e
Author: Todd Poynor <toddpoynor@google.com>
Date: Thu Jan 31 20:04:13 2013 -0800

tuna: power: interactive governor target loads update

Target 70% at 350M/700M, 80% at 920M (and 99% at 1.2G as before)

Boost performance of short bursts / medium loads. Power effects
TBD.

Bug: 8096433
Change-Id: I17794870e636607fe2bb644692f5d9d0adf67b50

commit 5b393a2ac96e4d078c3d295da587508225a92b37
Author: Todd Poynor <toddpoynor@google.com>
Date: Mon Feb 4 18:39:21 2013 -0800

tuna: power: interactive governor params update for performance

above_hispeed_delay = 80000 (from 100000), this is now applied to each
step above 700MHz and is impacting short-term load burst benchmarks.

min_sample_time = 60000 (from 40000, back to jb-mr1.1 value)

Bug: 8096433
Change-Id: I652e60c54e93a4b593d89f3f38d36a1133decb55

I wish I knew how to look up their bug ID. i think it's part of the performance improvements though.
[Samsung Galaxy Nexus] laureanop:
Parameters seem more dynamic and adjusted to loads now. I'll run them stock for a couple of days. 4.3 does have better performance indeed

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] DoesntPostAThing:
Well, my secret to getting 3 days battery is to not use my phone much... I once went 2.5 days without charging but only had 1h screen time total. If you just leave the phone there on flight mode you could achieve 1 week maybe, as long as you don't use it.
[Samsung Galaxy Nexus] zoomy942:
With stock settings I can get maybe 20 hours of light use. But I just want to get from alarm clock to bed time. That's all I care about and Tiny with stock settings gets it no problem.

I'm trying 1520 for the first time and so far no freezes.
[Samsung Galaxy Nexus] trini.s2k:
on 4.3 roms what can we use to change the governor there is no settings in the phone for it?
[Samsung Galaxy Nexus] laureanop:
Still Trickster Mod

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] zoomy942:
Or the performance menu in cyanogen
[Samsung Galaxy Nexus] 7175:
Been waiting for this day.. really great stuff in Changelog, can't wait to give this a go on slimbean 4.3 alpha 3.
[Samsung Galaxy Nexus] zoomy942:
First time ever I have used 1520 for two days solid with not a single issue. I'm astonished
[Samsung Galaxy Nexus] itasoulas:
what a great kernel! I can't believe I missed that... On 4.3 I got nearly 4 hours of browsing with wifi. How can someone cook this into a custom rom? There is some clue on updater-script and OP but further help please?
[Samsung Galaxy Nexus] tiny4579:
I shouldn't have to explain everything about building in custom kernels into a ROM to be honest. That is also technically a generic question as many have integrated custom kernels into their ROM.

But in short it's this:

1. Unpack the boot.img.

2. Replace the zImage with mine.

3. Add anything from /system/lib/modules in the kernel zip to the ROM.

4. Repack the boot.img and add it to the ROM.

If you're using the old-wifi version of 4.3 that's it for integration. Also, be sure to only use the v4.3 kernel on 4.2.2 ROMs for the best compatibility. If you need Android 4.3 then it's v5.0.
[Samsung Galaxy Nexus] EvilDobe:
Hi [MENTION=3500210]tiny4579[/MENTION]. What's the good word? :)
[Samsung Galaxy Nexus] tiny4579:
I was thinking an update with interactiveX. Is there something this is missing? I know I've not included all the governors but are they really needed?
[Samsung Galaxy Nexus] EvilDobe:
Probably not. Has anyone been asking for it? I think you've nailed down the basics & have everything running smoothly. Why meddle with perfection?
[Samsung Galaxy Nexus] zoomy942:
I'm noticing the max 1520 setting isn't sticking in trickster. I tried 1440 too. Then I found this on their site.

Q: CPU/GPU frequency doesn't stick?

A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues. Unfortunately, it can't be fixed from app side
[Samsung Galaxy Nexus] zoomy942:
Installed Franco and its retaining 15XX correctly.

Maybe a bug? I'll keep testing tomorrow.
[Samsung Galaxy Nexus] ashclepdia:
might be the powerhal resetting it?

i know this used to happen.

I'll do some testing tomorrow. been a while since i installed tiny.

time to come home :D
[Samsung Galaxy Nexus] tiny4579:
Most likely yes. That would make it a non kernel issue. I'll have to see how I addressed this previously and if I did it without custom powerHAL.
[Samsung Galaxy Nexus] zoomy942:
I tested an unofficial cm and shiny ROM. Same result.

---------- Post added at 12:17 PM ---------- Previous post was at 11:43 AM ----------

Awesome. Glad to know is not just my crazy mind
[Samsung Galaxy Nexus] imablackhat:
What do you guys use to control colors etc.
[Samsung Galaxy Nexus] jesssiii:
Trickster.

Galaxy Nexus Toro
[Samsung Galaxy Nexus] tiny4579:
I'm not having the problem on CM 10.2 at all. 1440 is being retained with TricksterMod without any special tricks.

What unofficial CM did you try? I'm using a self compiled build and it works.
[Samsung Galaxy Nexus] zoomy942:
Whew. What a day.

I tried the fitsnugly unofficial build and the shiny 4.3. Here is what I did to test...

I installed the cm, used the built in performance menu to set 1520 and went on my way. CPUSpy said it was active but across the day I noticed that 1200 got all the usage while 1530 stayed at 15 seconds or so.

I installed shiny to test with 5.0. I used trickiest and set it to 1520 (and tried 14XX) and either I would leave the app go about my stuff and go back and look at it back to 1200 or I could even stay in the app and watch it go back to 1200. The speed is still listed at 1520 but then device status page of trickester would show the max was 1200. So odd and I can't figure it out.

So I installed Franco to test, but I like your kernel better as it uses the stock ram disk, and it held 1520 all afternoon no problem.

I hope this makes sense.
[Samsung Galaxy Nexus] zoomy942:
I tried it in terminal so we could see it better.
[Samsung Galaxy Nexus] zoomy942:
Did you have a chance to test this?
[Samsung Galaxy Nexus] tiny4579:
Yes and I had no issues in cm. See my previous post.
[Samsung Galaxy Nexus] zoomy942:
Okay.

So its a powerhal thing per the ROM I'm guessing? Just odd that all other kernels function fine. Just this one doesn't. :(

---------- Post added at 05:04 PM ---------- Previous post was at 04:50 PM ----------

I just noticed (post-coffee) that there is an option in trickester to lock the CPU max and min speeds. I turned that on and it's working so far.

---------- Post added at 05:14 PM ---------- Previous post was at 05:04 PM ----------

After more googling, is a patched PowerHAL a kernel or ROM issue?
[Samsung Galaxy Nexus] tiny4579:
Its not a kernel issue, just some kernels decided to include a patch powerhal or a ram disk hack. I use neither right now. It should work in cm for you as it does for me without the trickster mod hack.
[Samsung Galaxy Nexus] zoomy942:
Understood and thank you.

I'm using Shiny right now only because some of the CM nightlies for 4.3 have been a bit adventurous for me. I'll use the frequency lock option in trickster in shiny till CM gets a bit more stable then flash back.

I do love your kernel. Close to stock and very simple. Good stuff.
[Samsung Galaxy Nexus] Broadleynine:
Just flashed 5.0. So far all is well. Will update if I run into problems but I've rocked your kernels for awhile and never had a problem so I don't expect one now. Thanks Tiny!
[Samsung Galaxy Nexus] ashclepdia:
sorry i fully forgot about setting up new kernel on my phone today.(i no longer have network carrier on it, so i've turned to using my laptop more often now that i am staright wifi all the time).

if it IS a powerhal thing, i know on 4.2(&4.1.2? maybe...cant remember exactly when this came into the scene lol)

i know that there used to be a 'basic' 'hacked powerhal' flashable zip that would replace it with one that was identical to stock except for the fact that you could change min/max CPU and it would actually stick(without having to use the "lock cpu" setting in Trickster MOD. i love trickster mod by the way. those devs have come an insanely far ways from the small tweak script that they started with. love it)

but thats what i was going to test.(i never care or worry about bricking my device by using older files with new things. i just dont stress like that lol. if i can't fix it after something ive done then i deserve to have a paperweight if i cant figure out how to get it restored to working order hahaha)

but i have a feeling it might work. i know tiny chimed in, and i didnt read all of his recent posts yet, so apologies if it's been discussed and figured out already. (i get lazy after a few beers, sue me :silly: )
[Samsung Galaxy Nexus] zoomy942:
Awesome! Keep us posted!
[Samsung Galaxy Nexus] ashclepdia:
haha

that's what i get for not reading.

tiny already all but confirmed that.

now I'm thinking i might just wait to see what tiny does, if he DOES decide to tweak the powerHAL a bit.

mainly because if there were changes made to the stock powerhal, and i use one from 4.2, i won't be getting those specific improvements (if there were any) that would be in the newer one.

I'm curious as to what the target_loads parameter actually does. lol

i had seen it for a while now in gov. settings. but before when i had googled for info on it i didn't come across anything very relevant. (I'm probably just thinking to hard about it haha)
[Samsung Galaxy Nexus] tiny4579:
I might include CM's powerHAL for 5.1. I think that's what I did before. It should be close enough to stock with the only addition being the max frequency getting reset to 1200 fix.
[Samsung Galaxy Nexus] zoomy942:
Excellente!
[Samsung Galaxy Nexus] tiny4579:
Now I just need to decide if I need to add anything else. This is a possible final release (just because I don't know if anything needs adding). Sure I could apply Linux patches and various interactive governor updates but to what real gain?

I actually am already planning to introduce interactiveX back again. ktoonservative is a possibility if there is a demand for it.
[Samsung Galaxy Nexus] zoomy942:
Well to be honest. Part of the allure of your kernel is that its very close to stock and doesn't require daily flashing. It simply works.

As for interactive updates, if they don't add to the overall experience then meh I suppose.

I just use interactive and run with it. Not sure which governors the masses use. I'm just a stock (with oc'ing to 1520) guy.

Love the stock ram disk.
[Samsung Galaxy Nexus] omniatic:
Ever consider dynamic interactive? I've been using it on ASKP, seems to run pretty nice.

Just a suggestion...
[Samsung Galaxy Nexus] tiny4579:
Maybe, but I don't see what's so great about it. Interactive runs well enough for me. Also, I really haven't seen it used widely.
[Samsung Galaxy Nexus] tiny4579:
Correction: It uses the ROM's ramdisk. It's not going to be stock unless the ROM has a stock ramdisk. If you look in the kernel zip there's no boot.img.
[Samsung Galaxy Nexus] zoomy942:
My mistake. I meant to say that but you said it better
[Samsung Galaxy Nexus] EniGmA1987:
I still like Ktoonservative, but I wish the GPU boost worked on this device like it does for the Nexus 10 and GS4.
[Samsung Galaxy Nexus] DoesntPostAThing:
Honestly I think there is very little wrong with this kernel, if any at all. It works perfectly, combined with factory images I don't have to worry about anything. Updates are few and far between, meaning booting into recovery isn't something I'd have to do daily. It's one of those things where I set up once (the colors), then just leave it in the background and it silently does it's thing. I can't be the only one who's feeling this, seeing the quiet thread with very few complaints. Good job Tiny!
[Samsung Galaxy Nexus] zoomy942:
Agreed. It's a great kernel for recovering flashaholics
[Samsung Galaxy Nexus] DoesntPostAThing:
Definitely. I used to be a flashaholic, then I found that I spent way too much finding something that works. Cue intro of Tiny Kernel, now I reboot only when absolutely necessary and spend time doing more worthwhile things, such as learning some android programming.
[Samsung Galaxy Nexus] Broadleynine:
THIS!

Well said! In fact, I've got nothing to add except that Tiny's kernel was my first custom kernel. Of course I tried a few others but honestly I just didn't have the time to keep up with all the changes so every time I kept coming back. Thanks Tiny!
[Samsung Galaxy Nexus] tiny4579:
I looked at it to see if I wanted to include it again. I probably will not due to a couple of the main features being tied into certain hardware.

1. With the GPU boost, I suppose it could be modified to work for the GNex. However, the GNex by default has a static clocked GPU (307). Were you thinking a 384 or 512 boost? I think this is possibly doable; however, the other aspects make me not want to integrate it.

2. The disable hotplugging on bluetooth feature to prevent lockups was designed for the GS3 hardware so the feature would have been tricky if not above my ability to integrate.

3. The governor has hooks into to the interactive governor the way it's designed which made it kind of tricky to integrate in the older kernel releases.
[Samsung Galaxy Nexus] avyonix:
Looking forward to a N4 version.
[Samsung Galaxy Nexus] tiny4579:
As in hoping for one or expecting one? Either way its not going to happen as I don't have a N4.

EDIT:

Sidenote: Though I started work on a Nexus 7 (flo) kernel, I haven't gotten to the point of something that stands out as being something I'd want to release. It was stock with a couple features but felt like a copy at that point and now I just use custom kernels on my flo.

Did someone tell you I had a Nexus 4 kernel incoming? I won't build for a device I don't own.
[Samsung Galaxy Nexus] tiny4579:
5.1 is live! Check OP for changelog.
[Samsung Galaxy Nexus] zoomy942:
I'm quite curious about interactive v2 with hot plug
[Samsung Galaxy Nexus] omniatic:
Darn! If I had stayed on the nightlies, I'd be flashing this right now. As it is, I went back to your last 10.1 build while traveling (and cause I missed the battery bar). Soon as I get back to a reliable signal area I'll have to upgrade and try it out.

Thanks,
[Samsung Galaxy Nexus] tiny4579:
Nope. Its nothing new. InteractiveX v2 was in the older builds. Its synced to interactive though. The changelog has the changes for interactiveX in there as it was added back.
[Samsung Galaxy Nexus] itasoulas:
latest 5.1 shows as 5.0 in "about phone" section even though the build date is Monday Aug 19
[Samsung Galaxy Nexus] kevtrysmoddin:
[MENTION=3500210]tiny4579[/MENTION] great kernel :thumbup:
[Samsung Galaxy Nexus] AbhishekS:
Flashing this kernel on Maguro. Hopefully I like it! :D
[Samsung Galaxy Nexus] tiny4579:
I think I know what happened. I'll push an update with the proper name to prevent confusion to other flashers. This will probably be tonight.
[Samsung Galaxy Nexus] syphix:
I can't seem to get Fast Charge to be active. TricksterMod says it is, yet my phone charges as USB.
[Samsung Galaxy Nexus] tiny4579:
But how fast does it charge? Do you get USB or ac adapter speeds.
[Samsung Galaxy Nexus] syphix:
Wow....I never looked that closely! AC speeds, yet USB mounting. NICE!!

Do you make a kernel for the 2012 Nexus 7??
[Samsung Galaxy Nexus] AbhishekS:
Same fast charge issue for me. How do I check the charging speeds?

And I assume the fast charge+mtp mod is implemented in the kernel. I had somewhere read that it's not good and break something. Is using mtp with fast charge really safe?
[Samsung Galaxy Nexus] tiny4579:
Check the post above you. It works. I use battery monitor widget to monitor charge speeds.

Where do you hear its dangerous? Its not more risky than regular fast charge. It has a hard limit of a 1000mA charge rate.
[Samsung Galaxy Nexus] avyonix:
Just being wishful. Hoping that you will get an N4 one day and start making kernels for it.
[Samsung Galaxy Nexus] EniGmA1987:
New Nexus is rumored for release soon :p
[Samsung Galaxy Nexus] zoomy942:
Awesome work tiny.

Did timer slack ever make it into cm's kernel? That's probably my favorite feature of yours.
[Samsung Galaxy Nexus] tiny4579:
I don't really follow cms kernel. As far as I know its not in their kernel.
[Samsung Galaxy Nexus] drmxmyt:
i wrote to maguro thread, but writing here too.

..

i think this kernel is the only one that supports cd-rom emulation right now. i made a thread 1 month ago about it, and now i found this kernel. and cd emulation works ok.

my thread was: http://xdaforums.com/showthread.php?t=2383638

to use it properly, you should setup drivedroid as this:

usb system: standart android kernel

automatically change usb mode: untick

manually change usb mode: mass storage tehthering.

that is the only option that works, i tried many. then mount iso.

so thanks for all. finally search is over.

also usb fastcharge + mounting usb is also sweet.
[Samsung Galaxy Nexus] zoomy942:
I didn't see interactivex v2 in the list but I'm assuming its just interactivex.
[Samsung Galaxy Nexus] tiny4579:
It's the same interactiveX from before. The v2 is just what imoseyon called it as it was a different implementation in the galaxy nexus than previous phones where it was available. Make more sense now?
[Samsung Galaxy Nexus] zoomy942:
Let me go get some coffee and read the past few posts again. :angel:

---------- Post added at 04:07 PM ---------- Previous post was at 03:51 PM ----------

Okay. So InteractiveX IS InteractiveV2.
[Samsung Galaxy Nexus] tiny4579:
Its interactiveX v2 not interactive v2.
[Samsung Galaxy Nexus] wmarcin:
Anyone has 5.1 running on JB 4.2.2 (mmuzzy)?

Sent from my fatty tuna belly..
[Samsung Galaxy Nexus] tiny4579:
As promised, new builds with a patch that should eliminate the WIFI MAC address randomization. No other changes in 1.8.6/2.2.1 though I'm thinking about including ntfs-3g in a future build.
[Samsung Galaxy Nexus] donnyp1:
What size battery do you have? I'm good a battery saving, but not 4+ hours screen on!
[Samsung Galaxy Nexus] nate6138:
Just the OEM extended battery. I always make sure to turn off 3G when I'm not using my phone. Helps a lot.
[Samsung Galaxy Nexus] tiny4579:
1.8.6 and 2.2.1 may be a bust. I posted a workaround in the OP but will repost here:

From this change: don't randomize MAC address (imoseyon) - deep sleep issue - workaround is to cycle bluetooth (switch between off and on and then back) - possibly applies to 1.8.6
[Samsung Galaxy Nexus] ncvikingx97:
What exactly do you mean by bust??

Sent from an AOSP , Rasbean'd Nexus 7
[Samsung Galaxy Nexus] techspecs:
"doesn't meet its intended goal or introduces more problems"
[Samsung Galaxy Nexus] tiny4579:
Feel free to try it though. It may work fine for you all. I just saw deep sleep issues for me.
[Samsung Galaxy Nexus] mr.wizard:
Confirming deep sleep issues, and also confirming cycling bluetooth fixes issue
[Samsung Galaxy Nexus] markassbuster:
What percentages are you all seeing for deep sleep when not having issues you using the BT toggle workaround?
[Samsung Galaxy Nexus] tiny4579:
It depends on usage but it should be a majority of the screen off time except when playing music.
[Samsung Galaxy Nexus] tiny4579:
Confirmed by testers that 2.3.0, just released, fixes the deep sleep bug on 4.2 and reintroduces vibration control.
[Samsung Galaxy Nexus] ncvikingx97:
Cool
[Samsung Galaxy Nexus] butler360:
Car dock fast charge?

This fast charge kernel mod seems to indicate that it works with the phone in the pogo pin car dock:

With this kernel fast charge does not work in the car dock. It does work if I plug the same USB cable attached to the same car charger directly into the phone's USB port. Is this something that could be added?
[Samsung Galaxy Nexus] tiny4579:
That'd be a little tricky as I didn't write the kernel patch/mod and I don't have a car dock. I PMed the dev of the mod about this.
[Samsung Galaxy Nexus] d11dog11:
Switched to this 2.3 on mmuzzys 4.2.1 ROM and i am glad i did. Same great stability with a nice oc, volume boost and color adjustment. Just awesome. Used trickster mod app to adjust everything.