yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nixholas:
Let's just say I left your maguro friends without any links xP The Build 13 link is here (:

Just saying, this is a PSM. I have not implemented any new feature into the kernel especially AMPlug due to its inconsistency. I believe that more test drives are needed to ensure you a better smoother, faster Super Milestone upon release.

Stay tuned for more (:

- Linux 3.0.86

- Fancy r35 upstream picks

- MIUI Compatibility

- RAMDisk Tweaks

- WLAN Drop fix from Fancy

- Some minor bugfixes for ASKP's hotplugging driver.
[Samsung Galaxy Nexus] ashclepdia:
Well well well!

Glad I stayed awake

Time to grab a coffee!

Thanks!

(Nice to see maguro having to come to OUR threads to download XP lol)
[Samsung Galaxy Nexus] csking33:
Sneaky sneaky ampheric ;)

You won't be disappointed ash :)
[Samsung Galaxy Nexus] ashclepdia:
Heyyyy

Where do I know you from? ;)

---------- Post added at 06:08 AM ---------- Previous post was at 06:05 AM ----------

Nice, just noticed the maguro in OP was changed to toro also lol

(Less confusion amongst those who don't know now: D)
[Samsung Galaxy Nexus] csking33:
You know, way back when we didn't have a choice what kernel we ran :) Now we get the pleasure of using this bad boy.

Taking out the hot plugging governors until it's fixed amp? Not a big deal to me, just wondering. Thank you again for this kernel.
[Samsung Galaxy Nexus] Citizen_Snips:
DX2 hahahaha......I was there. Sup Ash, sup csking? Did DzK ever get kexec working? Or is that phone still locked down?

Downloading now! Thanks Amp!
[Samsung Galaxy Nexus] mldiroff:
Ran 11 and 12 with some mixed results for stability and performance (on Axiom and CM). I'm seeing lots of posts about people tweaking with hotplug, etc. I know there's been lots of success from people running this, Amp, so I'm curious if maybe I'm not doing something right. Gonna try 13, too, on LiquidSmooth 2.8 and see how that fares. Thanks for all of your work for us GNex folk!
[Samsung Galaxy Nexus] nixholas:
Haha you're welcome :D

It's what I love to do :) Just thank me by pressing da' button xD

Okay. Time for a nice sleep :) Ciao~
[Samsung Galaxy Nexus] elliot2112:
i apolagize if this is a dumb question but build 13 is very experimental correct? or do i want to update from build 12? again sorry but i got a little thrown off by the excitement of some of the replys.
[Samsung Galaxy Nexus] justen7723:
Pretty stable for me the past 4 hours

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] huskerkate:
oh yeah, you want to jump on b13!! despite the disclaimers, Amp hasn't released a build that could be characterized as experimental/unstable for weeks and weeks. i hopped on the bandwagon at about b4 or 5, and they've all been rock stable.
[Samsung Galaxy Nexus] misterk267:
Hey amp I have a question. I noticed a while back in one of these threads that it was mentioned that multi-core power-saving is broken. That being the case, should it be left on 0, or is one of the other values best? I am running interactive and deadline if it matters.

~Nexus Powered~
[Samsung Galaxy Nexus] ashclepdia:
Yupp I remember lol

Ahh, so much I've Learned thanks to this(and now that I'm playing with my Linux laptop I'm noticing a lot of experience I've gotten from tweaking my Gnex is making learning the basic things in Linux MUCH easier to comprehend)

Been running this kernel all day, gotta say I'm very impressed, and I love the features included(so many! And I absolutely go crazy tweaking kernel parameters even WITHOUT this many choices and options so this is GREAT...) And not only are there a lot of options, but everything I've tried so far has worked beautifully!

I'll be hanging around for a while for sure! Even has somethings I've not yet seen before in other kernels I've used (sioPlus IO sched being one. I'm curious on the difference between this and the plain sio I've used on others)

---------- Post added at 04:54 PM ---------- Previous post was at 04:47 PM ----------

Locked down like its Alcatraz lol

I remember a tweet from Dragonzkiller couple months ago where he mentioned getting kexec to actually boot, albeit once and extremely bug filled but couldn't get it ever again to boot. We can still dream tho right? (Even tho I don't have mine anymore, it's nice to see they at least have CM7&9 & Even CM10/10.1 ALPHA builds to play with via 2ndinit. And would be cool to one day see the actual potential of the first dual core device come to full light with aosp and custom kernel with OC)

Sorry for the off topic guys! (Us old x2 users got into this habit when we didn't have much else to do...darn Melvin!! Lol).. just got a bit nostalgic lol
[Samsung Galaxy Nexus] jsgraphicart:
I was there...unfortunately. lol. It was fun though.
[Samsung Galaxy Nexus] ashclepdia:
I recommend not worrying so much :D

One thing I've learned is half the fun is just "going for it"/"live on the edge" so to speak lol.

Just make sure you have either a nandroid, your original ROM zip(just install if you have issues, dirty flash, wipe only cache and dalvik, this will restore you to original kernel and ramdisk) or a kernel (in boot.img form like this one) that you KNOW works properly, that way if you have any issues you can just go ahead and install one of those three things and be back in the game! :D

Build confidence in the fact that almost EVERY developer I've seen, for the Galaxy Nexus at least, has never put up a kernel that has serious issues that are highly unstable(and if they DID there was ALWAYS a HUGE warning "banner" for said kernel, followed by hoards of users reporting issues.

(This post is not intended to be condescending AT ALL. Sorry if it came off that way even a little :eek: )

---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------

I think 90% of us went to the Gnex at some point. Went from locked down to full on open! (Besides vzw prop stuff.. but that doesn't mean much considering what we came from HAHAHAHA)

---------- Post added at 05:10 PM ---------- Previous post was at 05:03 PM ----------

This kernel has a highly customizable OnDemand governor, way different than any I've come across EVER.

I MUST figure out exactly what each parameter does in detail. Google here I come!! Lol

Unless Amp can point me towards any kind of description concerning these. Even if its just details about it on github wit basic information :)

(I'm speaking of the ondemandplus governor of course..)
[Samsung Galaxy Nexus] t1.8matt:
For being experimental, B13 is definitely running great. Great work Amp, I'll be sticking around for sure to see what else you come up with.
[Samsung Galaxy Nexus] 55Pegasus:
B13 is running really smooth on TreyM MIUI ROM. First day but battery seems very good also. Thank you for this.
[Samsung Galaxy Nexus] KillerVamp09:
B13 is running great with uXylon over here. Speed is very much improved over build 13 and battery life seems to be steadily getting better after several cycles. Thanks for the great kernel Amp.
[Samsung Galaxy Nexus] sickopsycho:
Yeah I had a dx and dx2 as well, followed dzks builds of cm offshoots. To the best of my knowledge development stalled out on kexec... that phone will be locked down until the end of time. Lol... that's why I gave Motorola the finger and decided to go with manufacturers that build phones with capabilities that users want. Wow, what a concept!
[Samsung Galaxy Nexus] 7175:
I flashed b13 and noticed that the previous hotplug governor additions to fancy kernel base weren't included. Is the hotplug project being scrapped? Damn I hope not. It would be good to include some additional tweak options that fancy doesn't have, like with Rubik kernel from Anarkia's kernel. A few things that would phenominal to see are more tcp algorithms since Westwood isn't always good when signal is weak and packet loss is high (useful ones like YeAH, h-tcp+, illinois, veno, Vegas -- for high to low latencies), the full range of regulator voltages, and of course hotplug governors.. the best: ZenX, Intellidemand, Ktoonservative... maybe some other cool ones? GallimaufryX from popcorn, Abyssplug, AdaptiveX, Nightmare... can't forget Hotplug. I think making an OndemandplusX addition would be useful for hotplugging screen off at 384k MPU.

Still really happy to see a new Colonel in development, especially one throwing down some hotplug magic. :D
[Samsung Galaxy Nexus] huskerkate:
if you want to keep up on all the changes and plans for future builds, check out the Maguro thread - that's the primary thread for info. this thread is to address toro-specific issues. Amp is really active in the Maguro thread, and keeps everyone pretty well informed and updated on his plans - you should check it out. :good:
[Samsung Galaxy Nexus] sandrewmorrison:
I went from my battery dying after about 9 hours to this. Thanks very much for this.
[Samsung Galaxy Nexus] sandrewmorrison:
I went from my battery dying after about 9 hours to this. Thanks very much for this.

View attachment 2136186
[Samsung Galaxy Nexus] nixholas:
Okay, enough said my bros xD

Hotplugging will never be scrapped xD

And I'm utterly sorry for the long waits ever since build 7. I'm trying to make every single build big enough. Maybe not big, but at least in a substantial amount.

Having said that, Build 14 May most probably bring back in Hotplugging, and then you'll a bunch of other stuffs.

But still, I won't be releasing it so soon due to 4.3. Just take note there's no work done on any other device. Just saying, When I'm working on a particular phone, I'll most probably stay here for at least a year :)
[Samsung Galaxy Nexus] shag_on_e:
Okay so I'm psyched with b14 so far, first run is looking good! I had to change the hotplug governor though because the first boot SOD'd on me, but once setting my preferences things are smooth. Nice to have a new beast kernel! Thanks Amperific

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] t1.8matt:
I'm having zero problems with hotplug on b14. Its running like a champ.
[Samsung Galaxy Nexus] shag_on_e:
Edit: nevermind, sorry.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] nixholas:
Next build is full of wonderful governors.

Just Sayin' xD
[Samsung Galaxy Nexus] 7175:
[QUOTE

Yeah, I've been running hotplug going on 18 hours now, no problems at all, alarm woke me up this morning no sods. I got it set with screen off min at 384 and min at 384 for frequency. I'm using YeAH TCP algorithm, my custom MPU UV's SR-OFF,PWMvib@55, colors at -4,6[0,0,0];[163, 160, 200], rest is STOCK. Testing VAUX3_6030=2600, VMMC=1500.

[!!!]Nice, I can't wait![/!!!] Great job with b14, I'm loving the extra TCP congestion algorithms and hotplug goodies upgrade from b13. Keep up the awesome work man. And I'll definitely be sticking with 4.2.2 til we got a freshly baked askp 4.3 out of the oven.
[Samsung Galaxy Nexus] cujo6801:
You know it took me almost 30sec. To find b14

You know you could just post it here too.

I'm just saying... :p

sent from the DOG pound
[Samsung Galaxy Nexus] parkson:
Min + Screen off min set at the same 384 enables true hotplugging, but also brings freezes. Phone slept fine all night on Hotplug and upon waking I was able to browse the web for a couple of mins but then I got a SMS and phone froze, required battery pull, etc

[edit] b14 stock settings other than MPS=0, mins 384/384
[Samsung Galaxy Nexus] shag_on_e:
So has anyone else been getting(not sure what to call this) random cases where the screen stays black upon wake-up? It's not frozen because I can still touch the screen and feel vibrations from unlocking and opening things, but the screen stays black. I've seen this multiple times here and there with different kernels, but it seems to be back, for me at least. I have to keep guessing where the reboot button is to get my screen to come back, I hold the power button, then click around the area I remember the buttons to be until it reboots.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] parkson:
[MENTION=4243910]shag_on_e[/MENTION] That's a SOD

and lol @ feeling around for reboot. Just pull the battery
[Samsung Galaxy Nexus] shag_on_e:
I thought a "sleep of death" was when the screen went black and was frozen with no response. I've heard tell of folks calling it the "black screen of death" who knows, but I try not to pull the battery if possible to avoid improper shutdowns. I do if I get frustrated enough though!

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] nixholas:
Yours is not a SoD :) Just click lock the phone and await for sometime and it'll be back :)
[Samsung Galaxy Nexus] 7175:
You're definitely right about avoiding battpulls, especially if using dynamic fsync ON which is stock value here. I've lost my whole system doing a battpull after a screen freeze with dyn. Fsync ON. All fs operation was asynchronous before that batt pull, which effects a high chance of data loss from recent writes or in my situation data corruption, ergo f*****. If you turn dyn. Fsync OFF, you should just get normal fsync or completely synchronous operation. I know it's one or the other from tests I've done. If you're running hot plug kernels in test phase or pushing your system to crash to find UVs, I definitely recommend turning dynamic fsync OFF as a preemptive safeguard.

I've only gotten a couple crashes when I was in trickster and applying a governor setting for hotplug. A good way to eliminate this is to apply a grace period in trickster settings. This is specifically there for unstable kernel changes, i.e. doing undervolts with smart reflex. I know setting "ignore nice load" ironically caused one or both crashes.
[Samsung Galaxy Nexus] nixholas:
Enjoy build Fifteen :)
[Samsung Galaxy Nexus] xain713:
Anyone else get there CPU stuck at max freq ?
[Samsung Galaxy Nexus] NeverSeparate:
You didn't accidentally select the performance governor did you?
[Samsung Galaxy Nexus] xain713:
Nope I just change min screen on to 192 and just gets stuck on max freq if I leave it alone it just goes from default min screen to max freq no deep sleep it might be ROM related but all other kernels don't do this

:edit: also referring to b15 mr2 for 4.3
[Samsung Galaxy Nexus] shag_on_e:
Oh yeah man, my system got jacked up testing AK kernels with dynamic fsync on when the system froze. I lost a lot, so since then I leave fsync on. Now I wish I could figure this black screen mess out I'd be happy. The kernel is smooth and has most of the fun features I like so, you know.

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] justen7723:
I use spoons all the time. They are nice for cereal, oatmeal, yogurt, ice cream, cottage cheese, soup, mac n cheese, and many other things. You should invest in a few, they are also very inexpensive. :rolleyes:

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] NeverSeparate:
I think that wasa black and green screen reference he was making about the spoon.
[Samsung Galaxy Nexus] shag_on_e:
Womp Womp Womp...

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] justen7723:
U sure???? :p

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] NeverSeparate:
Nah man, that's women's deodorant. Running this now. Looking forward to seeing the results after a work day tomorrow.
[Samsung Galaxy Nexus] shag_on_e:
I'm a Matrix junkie, what can I say?

~~~~There is no spoon~~~~
[Samsung Galaxy Nexus] xain713:
OK so did a updated ROM and flashed m

The kernel again And all is fine now so must have been my ROM
[Samsung Galaxy Nexus] nixholas:
GREAT! Glad that you solved your issue :)

Now time to prep for 4.3 :)
[Samsung Galaxy Nexus] ThePhantom97:
Alright, I flashed build 15 and I am more than pleased with the performance! You sir are doing an awesome job and hope you keep up the good work. Here is a screenshot and this is with about 50 minutes of screen on which is about average for me on a work night:

I have never been over 50% battery when I get home from work. Not sure if it is hotplug or what it is that you have tweaked/adjusted to help save the battery but I am greatful!
[Samsung Galaxy Nexus] nixholas:
To me, the drain is still bad :)

Still, you'll see commits in the future that improves deep sleeping which reduces power consumption when asleep :)
[Samsung Galaxy Nexus] Citizen_Snips:
Amp.... when I flash b15 over any 4.3 ROM I get com.android.phone has stopped. I didn't think it was your kernel but once I just flash ROM & gapps it works fine. If I flash the kernel that error pops up every time I hit OK. So I can't get rid of it or even open the power menu. I must pull the battery. Happens to me on Cookies cm10.2 / FTL aosp / mmuzzy ROM

:( what am I missing? I read your posts I'm pretty sure b15 is for 4.3......halp
[Samsung Galaxy Nexus] nixholas:
ASKP-BuildXX are for 4.2.x releases.

ASKP-BuildXXMR2 are 4.3 releases :)

Take note. and get back here :)
[Samsung Galaxy Nexus] jsgraphicart:
Just flashed build 15MR2 and everything seems fine. I'll see how this thing performs over the next day or so. So far, everything seems nice and smooth. Except the "Max screen off" was kind of set low by default causing things to stutter for a couple seconds when turned on. But I moved that up a little and its all good.
[Samsung Galaxy Nexus] sruel3216:
mr2 is running smooth as ever on fitsugly cm10.2
[Samsung Galaxy Nexus] nixholas:
I had that too. Well, it depends on whether out chip in the phone likes low clockrate
[Samsung Galaxy Nexus] NeverSeparate:
Hey amp, I ran b15 with liquid and it seemed to do well. Only had 1 issue. I can't say for certain this is kernel related, I don't know if it's phone related even, but I will let you know in case it is something related.

I use an auxiliary cable to listen to music in my car. I had it hooked up steaming slacker when it started pausing randomly. I could hit play and it would start back for a few, then pause again. I thought it was either slacker, or a bad cable (it's not old but you never know). I got home yesterday and listened to slacker with headphones while mowing the yard. So that somewhat eliminated slacker being the issue. I tried power amp and Google music in the car today with the same results. So I messed with the cable and it would cut off while doing that so I though that was it. But i think it may have been pausing anyway and I just happened to be messing with the cable. I flashed another kernel on my way home and was able to stream with Google music no problem. So I'm not sure what to think. With your kernel music wasn't working in my car but did with headphones. It wasn't a long test but it worked in my car with a different kernel. Does the phone recognize headphones and auxiliary inputs differently? And could a kernel cause this?
[Samsung Galaxy Nexus] nixholas:
It's an USB/Headphone jack related issue. Double check for any faults :)
[Samsung Galaxy Nexus] NeverSeparate:
It isn't your kernel. With a little testing on my drive to work it seems like it may be the high performance sound and/or headphone volume boost in trickster. Maybe it's messing with my stereo or something. It seemed fine with headphones. I will test more to try and be sure but with those off it stopped.
[Samsung Galaxy Nexus] itslels:
Agreed! Nice work on this kernel!
[Samsung Galaxy Nexus] JPBeard21:
Your theory should be correct. I've also had this issue with high performance audio enabled set on 2 and would need my media volume set about halfway to keep the issue from happening. No longer use it.
[Samsung Galaxy Nexus] nixholas:
Apart from that, this function is hard coded into the kernel, so it is natively problematic. If it has issues, It will have it no matter how the ROM attempts to fix it. I suggest you guys to switch it to 0 and choose sound libs such as NexusLouder to tweak your sound performance :) That way, it's ROM coded, and thus, is less buggy.
[Samsung Galaxy Nexus] NeverSeparate:
I just turned those off. I am probably gonna try the nexus louder mod soon. Now that I know it isn't kernel related I gotta get back and try b15 again. :)
[Samsung Galaxy Nexus] nixholas:
Use your eyes and see the latest version xD Boom Magic xD SUPER MILESTONE XD
[Samsung Galaxy Nexus] parkson:
SM for 4.3?
[Samsung Galaxy Nexus] justen7723:
Go to any of the links in the op. When the link takes you to dev host click on amperific and look for b16mr2.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] sruel3216:
i have had this problem from time to time with purity rom and various kernels. im not sure what it is. for me it usually happens when i have the volume on the device at max, especially if i have volume boost set to 3. try lowering your volume on device and raising the volume with your car stereo
[Samsung Galaxy Nexus] NeverSeparate:
Thanks we have resolved it. It's an issue with the settings in trickster mod. Amp, I will look that up, thanks for looking out!
[Samsung Galaxy Nexus] db306:
So b16m2 is specific for 4.3? Just don't want to flash wrong one. Thanks
[Samsung Galaxy Nexus] misterk267:
Exactly. The BxxMx builds are for 4.3.
[Samsung Galaxy Nexus] ArnieG:
SM is headed my way! Will try it with 10.2 from ccb1208.
[Samsung Galaxy Nexus] nixholas:
Read the first three paragraphs of the OP thoroughly and you'll learn more :)
[Samsung Galaxy Nexus] cujo6801:
Whoa whoa whoa let's not get crazy now...

One paragraph okay

two paragraphs maybe

three paragraphs Now you've gone to far.....

sent from the DOG pound
[Samsung Galaxy Nexus] Citizen_Snips:
Seriously amp, you want us to read three paragraphs??? You want a written reflection about what we just read, too? Sheesh, what is this college?

J/k always read the op. :p B16 running smooth so far on 4.2.2 pacman ROM milestone release for toro. No freezes and very smooth so far.
[Samsung Galaxy Nexus] nixholas:
OH DANG IT ALL OF U. READ THE W

THE WHOLE C PROGRAMMING BOOK XD JK. xD

Well, the first three paragraphs are just a sentence. each :) But they are crucial so take note :)
[Samsung Galaxy Nexus] cujo6801:
Edit : Changed my mind....

sent from the DOG pound
[Samsung Galaxy Nexus] quickstang:
So I'm on my 4th freeze. This time it was about a day before it happened again. On b16, no weird settings or hotplug. Just interactivex, rab 512 & thats about it.

I was in es file explorer deleting a file & the phone just froze. Screen stayed on & had to battery pull.

I do have logcat extreme installed as well as catalog but have no idea what I'm even looking for.

Sent from my iphone killing Galaxy Nexus running ASKP kernel & AOKFP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] nixholas:
I suggest rab to be lower. It's hurting your phone xD You should lower because hotplug is also using rab for plugging :)
[Samsung Galaxy Nexus] misterk267:
I've seen a lot of people talking about having lower RAB settings being optimal, and how it's based on your storage size, etc. How exactly is this calculated?
[Samsung Galaxy Nexus] quickstang:
I'll play with it & see what happens. I've actually used 512 for quite sometime on Fancy kernel & even ak kernel & never once ran into this issue so it's odd that's what you think may be the issue. I have it at 384 right now so well see.

Sent from my iphone killing Galaxy Nexus running ASKP kernel & AOKFP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] nixholas:
Yep :) I understand :) But different kernels have different behaviours so yeah xD That's why xD 384 is the best for me :)

Okay, explaining it with the normal way is way too techie. I'll say it in a simple way where mainstream users will understand :) Think of RAB as a multitasking process or module. Its like saving a process and then letting it start/load quicker. If the memory is low, RAB will be affected. Also, the more the apps, the worst the performance on RAB. Use 384 to retain optimum performance. If you use 512 or even higher, you'll have to be sure you have as less apps as possible.