yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] thair7391:
Thank you! I must confess, I've known a lot about overclocking and have toyed with it for years, but after coming across "bins" yesterday, I realized I'd never heard of them. I always knew there were natural variations one two different chips even of the same model that could impact performance and temperature in different ways but I never heard it referred to as a bin number and never knew the mechanism behind the phenomenon until now. Thanks for you explanation.

Your Nexus is air cooled?? Man I don't know what your deal is but I'm hydrocooled on mine! An occasional, often unintentional dip in the toilet keeps my chip running 4.3 GHz at room temperature! Battery lasts about 35 minutes for some reason though... Hmm...

---------- Post added at 08:10 PM ---------- Previous post was at 08:06 PM ----------

I feel like I just posted my salary and made a remark about not being certain that it was that great and then someone on unemployment came along and told me theirs... If I could send my two additional bin units to you I would! I'd at least split the difference anyways. I don't have any desire to go beyond 2.8 honestly. 2.7 quad core is so fast!!! Plenty fast for anything a current generation mobile OS will EVER tackle.

Wait... I have an idea! Just change the value of the integer in the cpu_pvs file to whatever you want and save it!!

Hahahaha
[Nexus 6 Android Development] Xileforce:
I do feel a little better with my new binning now, 10ghz here I come!
[Nexus 6 Android Development] Mistertac:
Anyone in here who is Encrypted want to join us on Hangouts to test something?
[Nexus 6 Android Development] Xileforce:
Wish I was encrypted so I could join the cool kids club :(
[Nexus 6 Android Development] spd2230:
Pm sent
[Nexus 6 Android Development] thair7391:
I don't think you saved and rebooted did you?? Try that and then send me an in-app screenshot! Haha
[Nexus 6 Android Development] Xileforce:
Sadly when I save it doesn't stick :( Ill try and see if I can't make it :P
[Nexus 6 Android Development] thair7391:
Haha I'm scared... Half of me wants to try and the other half just enjoys my new Nexus too much even stock to give it a try! In do have SquareTrade though... Hmm...

You have to wonder what governs the value of that file. If you saved it as root and rebooted and it changed, then something is rewriting it obviously. Do you think Qualcomm or whoever writes that bin value to a very core, low-levek firmware built into the chip and then Android reads the value and writes it to the file we're seeing? That would make more sense. I doubt the processor is "reading" that file and changing it's bin lol. That would completely contradict the idea of what a bin is! I'm sure you could chmod the file and male the value stick though!

Why do you think Android (stock anyways) needs to know that bin value in the first place? Perhaps it over and under clocks on its own based on the thermal conditions it thinks it can get away with...
[Nexus 6 Android Development] Mistertac:
Well I'm not encrypted either, just needed one of each that's all.

Don't you worry... You're one of the cool kids [emoji6]
[Nexus 6 Android Development] EniGmA1987:
Well on the desktop side of things it generally isnt referred to as binning so that is probably why you havent heard of it. There are variations like this in the same model for sure and you will see different leakage processors on the same model. You can usually tel leakage by the stock VID of a processor. On the desktop side a "bin" is actually a different model. Take for instance AMD's FX 8370 processor. It is exactly the same as the FX8350, 8320, 6250, etc etc. They make one processor die and then when it is finished being made on a large wafer, they cut them up into individual processors and test them. This is the bin (when testing all the chips after they got cut up, which bin does the die get thrown into for classification. Hence the name ;)). Processors that meet full spec are sold as 8370's. Processors that dont quite meet the top spec but are still fully functional in all areas and fit within the 8350 bin are sold as FX-8350 processors. The next bin down is the 8320. The die's that have a malfunctioning core of one reason or another might have two of it's cores cut off and then it is sold as a 6350, or 6320 and so on down the line. The different models are the different "bins" and are all the exact same processor made on the same wafer from the fab. Intel does this too, but to a more extreme level. Some of their processors are binned for different caches and sold as different models that way. Because a processor may have fully functional cores but part of the cache was made bad and is malfunctioning, so where AMD would junk the processor since they dont have models with different cache, Intel cuts out some of the cache and sells the processor that way. This makes the most out of their investment because No company has ever gotten 100% all working perfect processors on every single wafer that is made. But the fabs contract may sell the wafer as a whole, not the individual processors. It would be a very bad investment indeed if only 10 out of 100 processor dies on a wafer were actually fully functional and that was all AMD and Intel were able to sell. Qualcomm of course does the same thing when they have their processors made and they test the individual processors once they are cut from the wafer. Top grade ones are sold as the highest clocked version of an SoC and processors that dont meet the spec are sold as lesser model SoCs. And then again within each SoC model you have the "bin" for leakage of that specific processor which is again seen in the stock VID (VID = voltage ID and it is how much voltage the processor needs for "X" speed).

Sorry for derailing the thread so badly.
[Nexus 6 Android Development] DespairFactor:
Well, I live in Canada, we get sub zero all the time
[Nexus 6 Android Development] Xileforce:
Well it does use the CPU binning to give you a voltage table AFAIK. RIPng would probably know for sure. But my understanding is based on your CPU binning you get different voltages. For instance a bin 5 at 2.6ghz may be set to use 1145mv but a bin 10 may be set to 1115mv at that same frequency. Though I believe that only works with stock kernel. Probably am wrong somewhere in there though. And its not that it reverts on boot. If I change the number and trt to save the file it won't let me :(

---------- Post added at 06:55 PM ---------- Previous post was at 06:50 PM ----------

Yay I'm cool!
[Nexus 6 Android Development] thair7391:
Brilliant information!! Makes perfect sense. I saw how semiconductors were manufactured on How it's Made once and I wondered how they cut identically performing chips out of that round shaped wafer they get halfway through the process. I guess "error margins" apply here as much as they do anywhere else in manufacturing. People think electronics/technology to be SO "precise" but not necessarily so...
[Nexus 6 Android Development] Jduncan312:
random boots on r11
[Nexus 6 Android Development] DespairFactor:
It is based on the binning it's in the aq8084.dtsi file iirc where they define the tables.
[Nexus 6 Android Development] Xileforce:
Revert to R9 for now. R12 will fix the issues.
[Nexus 6 Android Development] aSquard:
Voted 5 stars!
[Nexus 6 Android Development] mindflayyer:
Voted 5 stars. This kernel is the real deal. Excellent work sensei RIPng ?. I'm running smooth on R10, eagerly awaiting R12. I'd like to donate to you since you're running on so little sleep!

Edit: donated via Google wallet
[Nexus 6 Android Development] rignfool:
He needs moar coffee
[Nexus 6 Android Development] DespairFactor:
I actually do, I finished my last mug about an hour and a half ago:/ I am still working out issues in R12, I may bring a new cool feature for us:)
[Nexus 6 Android Development] EniGmA1987:
let me know if you need me to test stuff on an encrypted phone RIPng
[Nexus 6 Android Development] Xileforce:
Any hints on this secret new feature or are you going to just let us blindly guess :(
[Nexus 6 Android Development] DespairFactor:
for now, blindly guess, I don't want to promise it if it doesn't work:(
[Nexus 6 Android Development] mindflayyer:
Go buy a few cups on me then! Keep the excellent updates coming!
[Nexus 6 Android Development] Xileforce:
Hmmm...GPU oc....Or maybe....intelli governors....or.....maybe lower frequencies...orrrrr....maybe you decided to skip R12 and go straight to R100? That's all I got. :/
[Nexus 6 Android Development] DespairFactor:
All those are wrong, it's a new feature.
[Nexus 6 Android Development] old_fart:
Does it involve shaking it ? . ( moto deep hooks )
[Nexus 6 Android Development] Zyxxeil:
Try R1,000,000(#NOTALEAK), LOL JK.

It's something fairly new and should make this kernel very unique :P
[Nexus 6 Android Development] mmessina:
:confused:IPhone 6 Jamming?
[Nexus 6 Android Development] Xileforce:
Gah you guys and your top secret talks! Hmmm....if its something unique and new then I pretty much will never guess it :(

---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------

This would be a nice feature.
[Nexus 6 Android Development] DespairFactor:
Sorry guys, I can't implement it, its way too complex of a merge at this time:( Now you see why I didn't announce it
[Nexus 6 Android Development] frenchy714:
Np RIP, you do so much already. Keep up the great work!

I pooped my pants once, it's a long story....
[Nexus 6 Android Development] Xileforce:
No worries! Just gives me more time to guess what it is!
[Nexus 6 Android Development] DespairFactor:
If you noticed, we now have lkconfig. I have added 5 more things we can tweak through it.
[Nexus 6 Android Development] PWn3R:
It says 9 there.
[Nexus 6 Android Development] Xileforce:
That's the real bin. Lucky u!
[Nexus 6 Android Development] DespairFactor:
R12 is up, this should fix the issues from earlier
[Nexus 6 Android Development] carlz28:
lkconfig like normal?

Typing su then lkconfig in terminal and sayin' not found. Maybe I missed a step/post...
[Nexus 6 Android Development] DespairFactor:
su then sbin/lkconfig

EDIT: there is an issue with the script, I will fix it tomorrow, I haven't slept in 22 hours and I'm on 2 hours sleep.
[Nexus 6 Android Development] carlz28:
Hmm. Typed just as posted. Getting this error:
[Nexus 6 Android Development] Alex740il:
There is a typo in the script. Use root explorer or similar to edit /sbin/lkconfig file. Scroll to the bottom, and add ";;" after the last echo "Done! (also will persist at boot)" line. Should look like below.. After the edit, script runs..

11)

echo -n "To enable sweep to wake enter the values as detailed below:"

echo -n "disable = 0 sweep right = 1 sweep left = 2 sweep up = 4 sweep down = 8, for any combination you must add them together:"

read value

echo "$value" > /sys/android_touch/sweep2wake

echo "Done! (also will persist at boot)"

;;

*)
[Nexus 6 Android Development] Xileforce:
R12 running great! FIOPs is significantly faster in my androbench testing vs deadline. Also the optimal read ahead for fiops seems to be 1536 in my testing.
[Nexus 6 Android Development] digweed4me:
Yep it's running really great now earlier versions had reebot issues

---------- Post added at 10:05 AM ---------- Previous post was at 10:00 AM ----------

It doesn't persist at boot
[Nexus 6 Android Development] Xileforce:
Yay threads five stars!
[Nexus 6 Android Development] freebee269:
I'm on r12 and the kernel has been running great for the past 7 hours. Awesome job on this release. I just fastboot flashed it like I do all kernels. That's the old school android in me at work.

I do have a question though. In the bootloader log after I fastboot flash any kernel there is a partition size mismatch in the log for the boot partition. Does anyone else have that? Should I be doing something to fix that?
[Nexus 6 Android Development] aoaleman:
Absolutely LOVE fauxsound. Thank you again [MENTION=5169465]RIPng[/MENTION] and all testers, for all your hard work! :D
[Nexus 6 Android Development] DespairFactor:
It must have not shipped with my newer script, I fixed a few things and stored a file that it would have copied from on bot.
[Nexus 6 Android Development] agarth1050:
Nice!!
[Nexus 6 Android Development] DespairFactor:
IIRC it can be ignored
[Nexus 6 Android Development] Mistertac:
If anyone else would like to get their hands dirty testing shoot me a PM with your gmail address and I can add you to Hangouts.

A couple more Encrypted users would help but obviously anyone who is comfortable and knowledgeable will help.
[Nexus 6 Android Development] DespairFactor:
We got it working on encrypted, here is my screenshots, I actually went back to stock just to test for you encrypted users.
[Nexus 6 Android Development] PWn3R:
Thanks for the quick issue resolution. I was getting non-stop bootloops on R11 and thought there was something wrong with my setup.
[Nexus 6 Android Development] DespairFactor:
I will work on fixing lkconfig script today. I need a day off from coding so I will be releasing the new R13 with the lkconfig fix and then taking a break for today then back at it tomorrow.
[Nexus 6 Android Development] PWn3R:
Amazing work thus far, and remember you don't owe anyone here ANYTHING! Thanks for everything!
[Nexus 6 Android Development] DespairFactor:
The guys having issues, are you AT&T variants? What kernel were you on before? What ROM? Encrypted or decrypted?
[Nexus 6 Android Development] Jduncan312:
Was on stock and not even 10 mins ago my phone rebooted 3 times as soon and now it stopped. im on att and I'm decrypted
[Nexus 6 Android Development] Alex740il:
Coding machine! ;)

Some explanation to the two new features you brought up in r12.

source: http://xdaforums.com/showpost.php?p=24233069&postcount=1
[Nexus 6 Android Development] DespairFactor:
so it is still not working?
[Nexus 6 Android Development] Jduncan312:
It is now just has its moments where it acts up I'm on sinless ROM if it helps
[Nexus 6 Android Development] Alex740il:
That last commit.. you lier!! LoL!! :good::good:
[Nexus 6 Android Development] DespairFactor:
That branch may be a decoy...
[Nexus 6 Android Development] Alex740il:
Ooohh.. Bumping up to r16 instead..? :P
[Nexus 6 Android Development] DespairFactor:
next release won't be for a bit, I am working with a couple people who were getting bootloops on the kernel to get it up and running stable, battery friendly and fast as hell. I can only slowly merge code while they test. Next release should be awesome, we may lose some unstable eatures, but overall performance will be better.
[Nexus 6 Android Development] rignfool:
Any news on the logcat spam from the powerhal?
[Nexus 6 Android Development] DespairFactor:
Sorry? What logcat?
[Nexus 6 Android Development] Alex740il:
No worries!
[Nexus 6 Android Development] rignfool:
This one
[Nexus 6 Android Development] DespairFactor:
I haven't seen that logcat until today:eek: touch_boost is intelliplug stuff, not too sure why it's getting denied:eek: Let's look at it again once I release the rebased version.
[Nexus 6 Android Development] angieri918:
Where do I navigate to to find that file?
[Nexus 6 Android Development] DespairFactor:
/proc/cpu/msm_acpu_pvs
[Nexus 6 Android Development] Pilz:
Is there a change log anywhere? I was running R10 but it kept force rebooting my phone so Im going to try R12 now
[Nexus 6 Android Development] DespairFactor:
Whenever I am working on a new build I post a summary of what I am adding or what I have added. I am working on rebasing the kernel right now so we are a lot more stable.
[Nexus 6 Android Development] Pilz:
OK that sounds good, I wasn't sure I I should scan through all of the comments for the changes.

I just flashed R12 hopefully it will be more stable now because I like what you have done with this kernel.
[Nexus 6 Android Development] DespairFactor:
It should be, but if not, I may have Rsomething up tonight, I don't know what I want to name it, maybe I will just go with R10000000000000000000000000000000000
[Nexus 6 Android Development] Pilz:
Have you thought about under clocking the CPU to 233MHz? I have been using lean kernel with the under and overclock for a while now and I liked the ability to down clock the CPU further.
[Nexus 6 Android Development] DespairFactor:
That underclock isn't really worthwhile to be honest, when you are at that frequency your screen is usually off and deep sleeping. I don't want to mess with clocks right now because I think that is the source of most of the instabilities in this kernel. It has been a thought before, it isn't exactly needed and its not an immediate requirement even if it was needed. Stability comes first in the rebase with the useful features from the original builds.
[Nexus 6 Android Development] jermaine151:
Thanks for the new release. I just installed it. The ramdisk still has the boot image secure though. I just wanted to be able to adb remount to make it easier to work on mods and push them to /system. Not a biggie. I can unpack and repack the kernel.

Thanks!
[Nexus 6 Android Development] Pilz:
I see, I never tested it to see if it was worthwhile, but that makes sense. I usually keep mine with a max clock of 2.9GHz because anything higher crashes.
[Nexus 6 Android Development] DespairFactor:
I turned off all those things in the default prop.:S
[Nexus 6 Android Development] jermaine151:
I installed and cat'd it:

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.zygote=zygote32
camera.disable_zsl_mode=0
persist.camera.HAL3.enabled=1
persist.camera.ois.disable=0
persist.sys.usb.config=mtp
ro.qualcomm.perf.cores_online=2
ro.adb.secure=1
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0

Kernel version:

root@shamu:/ # cat /proc/version
Linux version 3.10.61~SENSEI.R12-gd053053-00241-g102bf0c9-dirty (RIPng@Dojo) (gcc version 4.9.3 20141101 (prerelease) (SaberMod-4.9.3_arm-graphite) ) #1 SMP PREEMPT Tue Dec 9 01:12:30 EST 2014
[Nexus 6 Android Development] DespairFactor:
That is interesting. On my machine in my build setup it's different.
[Nexus 6 Android Development] jermaine151:
Weird. On another note, doesn't: ro.qualcomm.perf.cores_online=2, mean that 2 cores will be the minimum that are ever online? I wonder if changing it to 1 will increase battery at all. I'll test it as soon as I figure out how to unpack the boot.img on my Mac. I haven't had it too long and it's a little different than Linux. LOL!
[Nexus 6 Android Development] DespairFactor:
Perhaps, I will edit that. This has to do with MPdecision, I believe.
[Nexus 6 Android Development] philsfan:
Am I the only one who thinks OnDemand runs smoother with Lollipop?

Just seems all the transitions of opening/closing apps flow better.
[Nexus 6 Android Development] jermaine151:
Repacked it. Let me know if you'd like me to post the zip

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
ro.zygote=zygote32
camera.disable_zsl_mode=0
persist.camera.HAL3.enabled=1
persist.camera.ois.disable=0
persist.sys.usb.config=mtp
ro.qualcomm.perf.cores_online=1
ro.adb.secure=0
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0

root@shamu:/ # cat /proc/version
Linux version 3.10.61~SENSEI.R12-gd053053-00241-g102bf0c9-dirty (RIPng@Dojo) (gcc version 4.9.3 20141101 (prerelease) (SaberMod-4.9.3_arm-graphite) ) #1 SMP PREEMPT Tue Dec 9 01:12:30 EST 2014

P.S. Kernel is running smooth for me!! Thanks again for all of your work on it!
[Nexus 6 Android Development] DespairFactor:
You could've just edited it on your phone. Also, that cores online bit only applies to qcom mpdecision I believe
[Nexus 6 Android Development] jermaine151:
Default.prop is in the Ramdisk, so editing it on the phone wouldn't last through a reboot. Okay.
[Nexus 6 Android Development] puertorecon:
I have a question. Does this Kernel work on Stock Lollipop 5.0? Stock ROM?
[Nexus 6 Android Development] Mistertac:
It sure does.
[Nexus 6 Android Development] Xileforce:
Fiops should be quite a bit faster in every way. You can read about the different governors on this website: http://androidmodguide.blogspot.com/p/io-schedulers.html?m=1
[Nexus 6 Android Development] DespairFactor:
He meant to CPU governor and it will because ondemand scales more aggressively
[Nexus 6 Android Development] eurominican:
my N6 says 8
[Nexus 6 Android Development] xenx:
I've got an AT&T N6. I'm not encrypted. I've tried Elixir, Euphoria 1.0 and beta 0.4., and Pure 2.95. I've used leankernel up to beta 9. I've even completely wiped back to stock and reinstalled Euphoria 1.0 and R12. Sometimes it just bootloops at Google right away. Sometimes, the intial boot up and works just fine and then starts looping when I reboot.
[Nexus 6 Android Development] Xileforce:
Omg I'm a moron xD I read that as deadline for some reason.
[Nexus 6 Android Development] DespairFactor:
Try R14
[Nexus 6 Android Development] rignfool:
Still have the touch boost errors in logcat...

Otherwise... Running smooth
[Nexus 6 Android Development] DespairFactor:
Double posts suck, screw you xda
[Nexus 6 Android Development] angieri918:
I can't find this for the life of me. I have both root explorer and es file and haven't had luck locating it. What folder would it be in??

Edit: Nvm found it... 6 :(

---------- Post added at 10:23 PM ---------- Previous post was at 10:18 PM ----------

Is there a change log for 14?
[Nexus 6 Android Development] DespairFactor:
Sorry, not sure if I mentioned, R14 has a couple faux sound fixes and is a complete rebase to the google source, so should be less bugs. I had to remove OC, fastcharge and wake gestures(they weren't fully working anyhow).
[Nexus 6 Android Development] anthonyp326:
Did the double tap to wake get removed?
[Nexus 6 Android Development] eurominican:
Go to root folder then proc -> CPU -> le file ( msm_acpu_pvs )

Or download terminal emulator app and type "su" then "cat /proc/cpu/msm_acpu_pvs"
[Nexus 6 Android Development] DespairFactor:
Yes, for now, you can use the app if you really want it.
[Nexus 6 Android Development] ChaosMinionX:
OC has been removed from R14? Will this be the new norm for Sensei?
[Nexus 6 Android Development] DespairFactor:
It may be, it was causing issues with a lot of people's phones, I am suspecting its the main culprit of the reboots.
[Nexus 6 Android Development] lightsout:
Sweet dt2w is finely truly disabled. I have not been able to disable it with trickster or the app. Often would wake up the phone on accident. Thank you.
[Nexus 6 Android Development] EniGmA1987:
I never got that command to work great for me, I just use "dmesg | grep pvs" and it tells me my PVS bin and SVS PVS bin. My PVS is 6, but my voltages are in line with 13 which is what my SVS PVS says it is. This means my stock voltage is pretty great, but how much you can undervolt doesnt have much bearing on what number you have here. I can only do -40mv across the board and be stable, but a guy I was talking with in Hangouts tonight is able to run -75mv pretty well and he has the same table 13 voltages as I do with a lesser PVS bin.

EDIT: So I looked up some info on Qualcomm's website, and apparently the SoC we have in our phone has 8 bin's only: 0,1,2,3,4,5,6,7. So the table 13 voltage is not necessarily the bin, and you can have that voltage table in multiple PVS bins which I found tonight.
[Nexus 6 Android Development] xenx:
So far so good on R14.
[Nexus 6 Android Development] Xileforce:
Yea I got no clue what's up with the binning on this thing.
[Nexus 6 Android Development] phillysmako:
I don't know if this is rom or kernel related but, this didn't happen until flashing r14. My auto rotate isnt working. Anybody else have that issue?
[Nexus 6 Android Development] Xileforce:
Nope, just checked. Fine here
[Nexus 6 Android Development] phillysmako:
What rom are you running? Im on pure shamu 2.95. I'll try a fresh clean install see if it fixes it.
[Nexus 6 Android Development] DespairFactor:
R15 is up, I have added a few governors and zen io scheduler.