yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] jesssiii:
I've been using the 4.0.1 new Wi-Fi kernel and was wondering should I be using the test version? I don't experience skips, but don't listen much either. What are the differences/improvements?

Toro GNex
[Samsung Galaxy Nexus] DoesntPostAThing:
Hi tiny, I have one question. I'm trying to set colors via init.d script. For the multipliers, do I change values for /sys/class/misc/colorcontrol/multipliers or blue_multiplier, green_multiplier, and red_multiplier individually? Also, what do I change for offset, gamma, and contrast? Thanks!
[Samsung Galaxy Nexus] tiny4579:
You can wait for the 4.1 release which is due soon.

That I don't know offhand. I'd have to look up as I don't mess with sys for scripts. Is there a reason why you want to do it this way over an app? Just wondering.

So I just connected to a WEP 128 mobile hotspot (HTC One) with my Galaxy Nexus without any issues. It may work with WEP if it's 128bit. Can someone test this out on the latest release or test build?
[Samsung Galaxy Nexus] DoesntPostAThing:
I prefer using an init.d script to set colors as it is applied before the bootanimation. I do not like that all colors are at 400, it isn't too good for the display. Otherwise, this kernel is perfect. I don't even have to touch the tunables.
[Samsung Galaxy Nexus] zoomy942:
My fav part of this kernel is how close to stock it is.
[Samsung Galaxy Nexus] DoesntPostAThing:
Definitely. I've found that close-to-stock stuff is the best. Both the SuperNova ROM and Tiny Kernel are slim, fast, but still offer just the right amount of customization to keep the user happy.
[Samsung Galaxy Nexus] zoomy942:
If you feel like it sometime, give Tinys linaro ROM a try. Pure Disney magic.
[Samsung Galaxy Nexus] DoesntPostAThing:
Is it for toro or maguro? And is it on Rootzwiki?
[Samsung Galaxy Nexus] nitsua98:
It's for toro and it's on here too
[Samsung Galaxy Nexus] DoesntPostAThing:
That's too bad, then, I'm on maguro :(
[Samsung Galaxy Nexus] zoomy942:
How has anyone's luck with 230 as the min been?
[Samsung Galaxy Nexus] bigknowz:
230 min

I've run with 230 min for months, no issues. A small caveat, noticing more and more that each phone is different and you can't make universal statements with GNex. I have issues that no one else has in other areas, but I would give 230 a shot.
[Samsung Galaxy Nexus] tiny4579:
350/1200 interactive with cfq should work well universally. That's why it's a default. Universal statements are ok if they're used cautiously and not applied to every phone or situation.
[Samsung Galaxy Nexus] wmarcin:
+1.

But I've only been successful with the 'interactive' governor. I haven't been equally successful with other governors. I had daily screen freezes with 'ktoonservative', 'interactivex' and 'wheatley'. I didn't try others.

BTW, I love this kernel with the mmuzzy ROM.

Sent from my Fatty Tuna Belly.
[Samsung Galaxy Nexus] tiny4579:
OP updated. A couple of notes. Try the deadline I/O scheduler. You may see better results than before. Also, there is a new fast charge USB patch in this build. Anarkia reverted it but the dev who came up with this patch has confirmed it works as intended. Check OP for some more info. Fast charge still has to be enabled and you have to re-plug in your device to register it after turning it on. If it does not work for you, please provide a detailed description of the problem.

WiFi drivers are updated for the New WiFi build. I have tested WEP 128-bit encrpytion to my HTC One hotspot configured for WEP and it connected fine. Maybe the issue has always been the key not being correct before. Either way, WEP should in theory work but I have a tester testing this on the earlier test build. If you need WEP to work and don't want to test, use the old WiFi drivers build.

Enjoy!
[Samsung Galaxy Nexus] DoesntPostAThing:
Could you please add in the ability to charge the phone using a y-cable while hosting USB OTG? Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tiny4579:
Are you talking about the n7 patch?
[Samsung Galaxy Nexus] midnightdevil66:
Gonna give this a whirl. Thanks tiny.

Sent from my AXI0M Toro
[Samsung Galaxy Nexus] DoesntPostAThing:
I'm not sure, but it's included in AK Kernel and I think Franco as well. Basically it allows me to plug the charger into the Y-cable, USB into the Y-cable, then plug the y-cable into my phone and I can use the USB device while charging the phone.
[Samsung Galaxy Nexus] tiny4579:
We shall see. I didn't know it was already done. I'm not that good at porting low level code like that. I can check it out at least.
[Samsung Galaxy Nexus] DoesntPostAThing:
Awesome, thanks! It shouldn't be too hard, as many GNex kernels already have it.

I also just found the thread where the original code should be, it's here: http://xdaforums.com/showthread.php?t=1835720

Might be outdated, but iirc not much has changed since that version. Asides from that, the latest 4.1.0 version with deadline and dynamic fsync is working wonders for me! Also getting 3 bars of wifi instead of 1 in my room now (router is across the house).
[Samsung Galaxy Nexus] DoesntPostAThing:
A few more things I have noticed:

I had a bunch of apps stored in RAM, and then I started an instant mix in Play Music. It played for about 15 seconds, then just went to the boot animation. Clocked at 1.3 on v4.1.0. GPU clocked at 384, dynamic fsync on. Using deadline. All other things default. Not sure what happened, as Android should remove other things from RAM rather than hot reboot. Anyway, you can download last_kmsg here if needed: https://www.box.com/s/cmjrrtju0okyk7b6wiul

2. Perhaps an option to control BLX? So charging "stops" when it hits a certain percentage and slowly charges from there on. Better for the battery if you like to just leave it on the charger. Stock has it somewhere between 95 to 97, I usually have it at 97 on kernels that have the option.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tiny4579:
1. Last_kmsg doesn't help diagnose a soft reboot. Ideally, you'd want a logcat but that's tricky as it usually clears after a soft boot unless you start the logcat and leave it running before the reboot. That's what I've seen anyway.

2. BLX - why? The charge rate already decreases as the battery gets closer to full and trickle charges to keep the battery full. I haven't cared for the feature and don't see the use. It may make a very very small improvement to overall life of the battery. This is probably the first request for BLX which means it's not exactly a big deal.

If stock has it between 95 and 97 and you set it to 97 on kernels that have that feature do you even need it?
[Samsung Galaxy Nexus] nikulogical:
Kernel devs like franco had put the BLX to 100 by default to make it last longer. I thought that it extended short term battery life without affecting it in the long term.
[Samsung Galaxy Nexus] midnightdevil66:
The 4.1 kernel is running great. The only thing I noticed but doesn't bother me is that when I wake up the phone it takes about 10 second or so for the WiFi and signal bars to go from gray to blue so it seems that there is a delay in contacting Google servers.

Sent from my AXI0M Toro
[Samsung Galaxy Nexus] Nicuz95:
Installed yesterday on my maguro, I only changed min and max frequencies when screen is off and I set deadline scheduler.

Damn, it's fast as hell! :D
[Samsung Galaxy Nexus] wmarcin:
Can't see deadline in my list of governor choices in Trickster. :(

Dirty flashed 4.1 new Wi-Fi.

Sent from my Fatty Tuna Belly.
[Samsung Galaxy Nexus] zoomy942:
Its a scheduler not a governor.
[Samsung Galaxy Nexus] Nicuz95:
My fault in my previous post, sorry :/
[Samsung Galaxy Nexus] laureanop:
Tiny I'm getting horrible overnight drain on Wi-Fi with old or new drivers. This graph is for an 8 hour period. Would you attribute this to my modem being a power hog ? (No apps holding awake)

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] tiny4579:
That's weird to be both wlan and modem. I've seen high one or another. Are you sure it's not something in the os holding that lock? Do you have any failing syncs or hung syncs and does this come back after a reboot?
[Samsung Galaxy Nexus] laureanop:
None that I can see. These are cpu and background cpu used.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] Azrith:
Bootloop?

Ok - I feel stupid. 4.1.0 w/ new wifi is putting my phone in a boot loop (tried downloading it twice from two different sources so it's not corrupt). I'm coming from AK 256 and currently using the newest Muzzy FV rom. Is there an issue coming from AK's kernal?
[Samsung Galaxy Nexus] zoomy942:
If AK has its own ramdisk then it might cause problems.
[Samsung Galaxy Nexus] bluerez79:
Ak has a revert WiFi driver zip in op. Might try flashing that and then new kernel maybe?
[Samsung Galaxy Nexus] tiny4579:
Reflash the ROM and kernel. The ramdisk in AK's kernel isn't compatible with most other kernels. I think it has something to do with the compression method AK uses in its ramdisk that most kernels don't have added support for.
[Samsung Galaxy Nexus] laureanop:
Yes, no other kernel will flash after ak. Reinstall Rom and kernel.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] dereaper:
not true just flash lean kernel then tiny it works every time
[Samsung Galaxy Nexus] tiny4579:
True I didn't think about that but you have leans ramdisk instead of the roms. Not necessarily bad but not fully tested.
[Samsung Galaxy Nexus] dereaper:
leans ramdisk isn't too bad tho plus it will save a reflash and setup :p
[Samsung Galaxy Nexus] tiny4579:
Reflashing the Rom doesn't require a wipe at all. So no setup required. You are welcome to use leans ramdisk but don't report any issues until you switch back to the roms ramdisk. Fair enough.
[Samsung Galaxy Nexus] laureanop:
In my opinion, CM s ramdisk does the best job at managing ram at this moment.

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] refthemc:
Just flashed this kernel and seemed to have lost the option to enable full speed WiFi while the screen is off in TricksterMOD. Was wondering if this option is just already integrated and always on or if it is just not available as an option.
[Samsung Galaxy Nexus] tiny4579:
Which kernel version and is it new Wi-Fi or old Wi-Fi?

The WiFi speed are not available with the new drivers and I think have disabled with the old drivers a while back. Are you having issues making this a concern?
[Samsung Galaxy Nexus] tiny4579:
The ramdisk only controls the default minfree settings and I believe CM's is the same as stock here. I can't remember Leankernel changed the minfree with the exception of when zram is enabled via script.
[Samsung Galaxy Nexus] laureanop:
With 4.2.,2 the closer to stock the better

The relentless pursuit of the perfect rom
[Samsung Galaxy Nexus] kobik77:
Great kernel.

Also I like the fast charge with storage available feature.

Thanks!
[Samsung Galaxy Nexus] branedamig:
What's the stock read ahead buffer setting on the latest tiny kernel? I'm afraid trickster may have changed it. Thanks!

Sent from my AXI0M GNex on Tap2
[Samsung Galaxy Nexus] tacosrdelicioso:
Just clear app data on trickster and look at it again

---------- Post added at 08:43 PM ---------- Previous post was at 08:34 PM ----------

Also, this is a really really great kernel..so good!
[Samsung Galaxy Nexus] tiny4579:
I missed some of the features I wanted to include in the release and when I checked my github they weren't in the release branches. I'll have to add them in 4.3. Also bigknowz mentioned timer_slack from fancy kernel. Sounds interesting and I may include it in the next 4.3 build.
[Samsung Galaxy Nexus] nomad4ever:
I'm sorry for the noob question. I just downgraded/reflashed my GSM Galaxy Nexus (from Liquid Smooth 2.5 with Fancy Kernel) back to CM 10.0 (which is Android 4.1.2) and wanted to use the latest TinyKernel for Android 4.1.2.

Is it correct, that the last TinyKernel for 4.1.2 is the 1.13.0? And this is the same for the GSM Galaxy Nexus?

Just want to make sure, before I flash any wrong files. Thank you!
[Samsung Galaxy Nexus] jesssiii:
I believe this is the latest 4.1 kernel: http://goo.im/devs/tiny4579/gnex/kernels/tinykernel-4.2.0-jb41.zip

Tiny, correct me if I'm wrong.

GNex Toro
[Samsung Galaxy Nexus] tiny4579:
Yep you're right.
[Samsung Galaxy Nexus] nomad4ever:
Okay, thanks guys! I think, I just got confused with the naming scheme then. ;)
[Samsung Galaxy Nexus] zoomy942:
Tiny

In an effort to stave off upgrading as long as I can, I'm looking to maximize my gnex usable life.

I have noticed that 1520 my device is a bit unstable, not sure about anyone else. I was wondering if any consideration could be given to either adding maybe a 14XX slot or changing the 1520 to something 14XX?

If not no sweat but since the Inc days you've always had an open door policy for questions.
[Samsung Galaxy Nexus] tiny4579:
1350 is my middle overclocking frequency. It's been fine the way it is. I don't see the need to change. Maybe if you can provide justification for it. I don't know if there's a real gain between 1350 and 14xx.
[Samsung Galaxy Nexus] zoomy942:
In that case what voltage is 1500 using?
[Samsung Galaxy Nexus] tacosrdelicioso:
There's a gain because moarrr
[Samsung Galaxy Nexus] SahilC:
Hey guys! How's idle drain in Tiny?
[Samsung Galaxy Nexus] jekern77:
What idle drain?

:D
[Samsung Galaxy Nexus] tiny4579:
Not 1500 MHz but 1520 MHz.

It's using 1395000 - 1395 mV.

For your reference 1350 MHz uses 1388000.

You can try disabling MPU SmartReflex with TricksterMod and seeing if stability improves for the 1520 slot.

Also, 4.3.0 is out featuring timer slack from Fancy kernel.
[Samsung Galaxy Nexus] abhishek93:
hey guys i m thinking to try this kernel.. but i m confused with the difference between new and old wifi version... can someone plz tell me the difference between the two of them?
[Samsung Galaxy Nexus] ashclepdia:
I noticed before(it's been a while so forgive me for not remember which kernel or the exact freq) I just remember it being 14xx, it gave me what I can only describe as the agility and speed of 1520 but took my CPU considerably longer to heat up to the thermal throttle point. My CPU always heats fast due to how I use it(which is why I was ecstatic way back when you agreed to add in the ability to raise that) but it shoots thru the roof when 1520 is set. 1350 is nice, is usually what I run, but if I had a choice of something around 1450/1480, I'd probably use that more often. My device handles 1520 no problem, except as I said just heats up insane fast.

No matter what you decide, your kernel is still top notch and I highly appreciate your work! Thank you!

---------- Post added at 05:31 AM ---------- Previous post was at 05:24 AM ----------

I know for me personally I have to use the old WiFi drivers version due to the fact that I connect to my neighbors WiFi and he uses WEP(he aint changing it lol) and if I use new version it just hangs on obtaining IP address (it will do that with any WEP secured router I try to connect with) WPA secured work fine on both for me.

I believe that's the main thing with the reasoning behind having both versions. If you use wep security on router you might need to use the old Wi-Fi version of the kernel
[Samsung Galaxy Nexus] BriVG:
Reeaaally quiet in here:)
[Samsung Galaxy Nexus] zoomy942:
That's cause this kernel works. 100% of the time. :o
[Samsung Galaxy Nexus] DoesntPostAThing:
Agreed. Can go on for days without rebooting on this, no issues whatsoever. On 4.3 now though, and really miss this kernel already! 4.3 + TinyKernel will be a perfect match (some quick toggle mods would be nice too...)
[Samsung Galaxy Nexus] kmcrane:
Absolutely! Nailed it on both, Tiny first though!
[Samsung Galaxy Nexus] tiny4579:
You're in luck because I started looking at the kernel source already. It will take me some time as it won't be a simple merge this time. Repeat from rootzwiki - copy and paste because I'm lazy:

V5.0 will be the next kernel release as Google has already released kernel sources for 4.3.

Due to there being a lot of changes (tons more than any of the Jellybean updates so far), I'm going to drop Android 4.1 and Android 4.2 and only use the official Google WiFi drivers for now. There will only be one version of my 5.0 kernel starting out until I can peer into the changes a bit better.
[Samsung Galaxy Nexus] tiny4579:
What is this I see now?

http://mbqonxda.net/tiny4579/gnex/kernels/tinykernel-5.0-beta1.zip
[Samsung Galaxy Nexus] DoesntPostAThing:
Thank you!! Even the beta is super smooth and stable. Nice to have color control again :)
[Samsung Galaxy Nexus] wmarcin:
Thanks! Will this work with JB 4.2.2, or is it intended for 4.3 only?

Sent from my Fatty Tuna Belly.
[Samsung Galaxy Nexus] tiny4579:
4.3 only. I don't recommend trying it on 4.2.2 but try if you would like. I am curious to see if it will work. It definitely will not work on anything prior to 4.2.2 as I don't have the patch that allows the kernel to work with the older GPU binaries.
[Samsung Galaxy Nexus] fcisco13:
5.0 working on carbon 4.2.2 running smooth thanks.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] marshy73:
It's working so far on my 4.2.2.
[Samsung Galaxy Nexus] zoomy942:
installed on 4.3. I saw there wasn't a 230 slot quite yet. No sweat.
[Samsung Galaxy Nexus] JohnKuczek:
Working fine on CM 10.1 7/25 nightly.
[Samsung Galaxy Nexus] dougdirt:
Wow Tiny, thanks for this. Working great and I don't have to put up with a yellow phone running 4.3. Trickster and color control works fine.
[Samsung Galaxy Nexus] tiny4579:
Since you guys all just flashed 5.0 beta1, I thought I'd make another test build just to make you flash again. Mwahaha!

http://mbqonxda.net/tiny4579/gnex/kernels/tinykernel-5.0-beta2.zip

I didn't have CPU overclocking yet in the first beta and dynamic fsync wasn't enabled.

Most of the features have been added back as of this beta. I didn't add all the previous patches from before. 5.0 is a from the ground up build so it took a while.
[Samsung Galaxy Nexus] zoomy942:
Installed. Thank you.

Thoughts on 230 slot?
[Samsung Galaxy Nexus] tiny4579:
Possibly. I just haven't done it yet. Did you see the new 1.44 CPU slot?
[Samsung Galaxy Nexus] claytonjn:
PGM isn't working with 5.0 beta2 (I didn't have a chance to test with beta1 before you posted beta2). Is that just an issue of you not including all patches yet, is it an issue I need to bring up in the PGM thread, or does 4.3 warrant a complete re-write of the PGM modules?

EDIT: I'm running 4.2.2 until 4.3 is merged into RootBox. Also, enabling Dynamic FSYNC causes an imediate reboot, in 4.2.2 at least.

EDIT2: The reboot might have been 1.44 CPU, I'm doing more testing

EDIT3: Yup, it was definitely 1.44. Sorry about that. I'm still curious about PGM though.
[Samsung Galaxy Nexus] zoomy942:
Heck no I didn't!! AWESOME
[Samsung Galaxy Nexus] tiny4579:
The voltage may need to be tweaked for that speed. Its voltage is the same as 1.35. I probably need 25-50mv more.

About pgm, can you get a dmesg after trying to turn it on? Since you're on 4.2.2 it might be kernel related. Does it not work or not even turn on?

Edit: Module loading was disabled which is why the PGM module wouldn't load. Fixed for beta3. I guess Google for whatever reason decided to turn it off in their defconfig.
[Samsung Galaxy Nexus] claytonjn:
I think you're right about voltage, I didn't think about the clock speed at first because I've run 1.52 before and only very rarely had reboots.

I got the dmesg but I guess I wasn't fast enough (I just left work). Looking forward to beta3!
[Samsung Galaxy Nexus] imanol01:
Hey!

Sorry for this stuped question But

if you got boot the kernel 3.4 in galaxy nexus Do you think we see the Bluetooth 4.0 LE?
[Samsung Galaxy Nexus] tiny4579:
I don't know. I never saw an actual source that 3.4 was required for le or where it was added to the kernel is kernel updates were even needed.
[Samsung Galaxy Nexus] DoesntPostAThing:
I think LE was removed from the GNex due to hardware limitations. Perhaps our bluetooth hardware isn't new enough?
[Samsung Galaxy Nexus] tiny4579:
Beta3 available below and goo.im:

http://mbqonxda.net/tiny4579/gnex/kernels/tinykernel-5.0-beta3.zip

Features 230 MHz underlocking and hopefully more stable voltages for 1.44 and 1.52 GHz speeds.

I enabled loadable module support but was still unable to load PGM on beta3. Might need to check with bponury to see why.
[Samsung Galaxy Nexus] breakthestatic:
The problem seems to be partially with supersu. Several of us were able to get PGM working by uninstalling the supersu app, then activating PGM. Afterwards, PGM works, and you can reinstall supersu from the play store.
[Samsung Galaxy Nexus] zoomy942:
Thank you. Installed and using 230/1200 for now.
[Samsung Galaxy Nexus] Alton (Halo 2):
So tiny do you think you can get Bluetooth LE to work like you did with Dinc Beats Audio? ;)
[Samsung Galaxy Nexus] jon9314:
I'll second that
[Samsung Galaxy Nexus] tiny4579:
I got it working by accident based on how I ported the evo gingerbread sense kernel to inc. I don't know how I did it then. Plus I don't know if the hardware on the Galaxy Nexus supports LE. I've heard conflicting opinions.
[Samsung Galaxy Nexus] jon9314:
I read the chip in the gnex is the dual chip that supports it but there is something in the other kernels ie n7 that enables it but I'm not a programmer and am confused with it all. I know I've been waiting for it and I'm disappointed that Google didn't enable it for us. Now its in our great dev's hands. Thanks for all your hard work
[Samsung Galaxy Nexus] DoesntPostAThing:
I did a quick bit of Googling on this subject, and it appears that the GNex uses the exact same bluetooth chip as the iPhone 4s, which has bluetooth 4.0 (smart, LE, whatever you want to call it) support. This means that we can get bluetooth 4, if someone enables it. At least there is hope!

---------- Post added at 04:45 PM ---------- Previous post was at 04:02 PM ----------

Also, Chainfire released an update to SuperSU, fixes a few root issues such as CPU spikes caused by su daemon, etc. Get it here: http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
[Samsung Galaxy Nexus] jon9314:
Just found this. http://xdaforums.com/showthread.php?p=43938595.

It explains why gnex doesn't have blue support. Maybe you could look at it tiny and see if there is anything you can do. Thanks
[Samsung Galaxy Nexus] zoomy942:
Working great so far.

Something I have been testing. I've always been interested in using the ROW scheduler so I tried it, among others, and I gotta be honest. In my "very scientific" analysis... CFQ really is the smoothest.
[Samsung Galaxy Nexus] DoesntPostAThing:
I've found this in 4.2.2 mmuzzy as well. While other schedulers may be smoother in certain parts, cfq performed the most steadily for all sorts of tasks (for me, at least). Perhaps this is why it's the default governor?

Also:

This is interesting. Tiny, any comments on whether this may be possible? At least two things are confirmed, though, and those are that the GNex hardware can support BLE, and that at least some part of 3.4 kernel is needed.
[Samsung Galaxy Nexus] zoomy942:
Edit. Never mind.

As for speeds. I'm finding 350/1350 and GPU 384 working well
[Samsung Galaxy Nexus] DoesntPostAThing:
Tiny, could you take a look at this? http://xdaforums.com/showthread.php?t=2380195&page=19

Apparently Carlos has managed to get some sort of BLE working in CM 10.2. I'm not sure if it's ROM related or kernel related.
[Samsung Galaxy Nexus] tiny4579:
Yeah, I saw it earlier today. It's not kernel related changes though, just ROM. A couple commits need to be reverted in the device trees. Since there was a bug referenced, I think BLE will not work on the Galaxy Nexus right now but it's hard to know without the details of the bug referenced.
[Samsung Galaxy Nexus] zoomy942:
Which build is your kernel based on? I was reading here...

http://xdaforums.com/showthread.php?t=2382880

And looks like the JWR66V has some wifi changes in it? This may not be kernel related at all, but thought I would let you know.
[Samsung Galaxy Nexus] tiny4579:
I'm android 4.2.2 based other than the v5 betas.
[Samsung Galaxy Nexus] EvilDobe:
Oh noez!!! This is very sad. Good luck, Tiny.