yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Original Android Development] nikhilbhalwankar:
Hi [MENTION=4929759]raghav84[/MENTION] ,

Can you please confirm whether the latest build dated 30th July has root access? I mean whether the phone will be still rooted? Please let us know.
[Galaxy Note GT-N7000 Original Android Development] jaiiscool:
just flashed, not working for me

also the phone got stuck at boot screen on reboot, not complaining, just stating......
[Galaxy Note GT-N7000 Original Android Development] nikhilbhalwankar:
ohh. ok. Thanks for update :)

Does this mean that you have lost root access and now u have to re-root your note?
[Galaxy Note GT-N7000 Original Android Development] hhhwwe:
Root working fine now and no issues with rebooting. I am also able to restore some apps with titanium backup (confirms su is fine).

As correctly edited by xplodwild in OP, only issue left with this build is the some graphical glitches and lack of video recording. Havent notcied any other issue so far. :)

EDIT: Also screenshots which i think [MENTION=2162789]XpLoDWilD[/MENTION] has purposely disabled coz of mali issues
[Galaxy Note GT-N7000 Original Android Development] AA1973:
Same here. Root apps working for me:

AdAway, Better battery stats, better wifi on/off, Rom Toolbox, Root Explorer, Total Commander, Zip Installer...

30/07 build.
[Galaxy Note GT-N7000 Original Android Development] XpLoDWilD:
As I said on G+, no bug reports on Focal. It hasn't been tested on a wide range of older devices, so bugs are to be expected on those, especially when the device bringup is in early phases (and when I can test for myself). Some config overlays are missing, so wait a few days.

Everything capturing the screen will be disabled for now, because of Mali issue yup. This includes browser glitches, screen capture, rotation animation, screen off animation.
[Galaxy Note GT-N7000 Original Android Development] shahtheass:
Review 4.3 update for Galaxy Note

Hello guys. I just did a review on the latest update and pls check it out when u guys have the time :D:)

Youtube video: http://www.youtube.com/watch?v=XPZDJJAuuJQ
[Galaxy Note GT-N7000 Original Android Development] wierzbik:
EFS cleanup O_O

Hello!

I don't know is this only single case, or is this caused by this rom, but I want to warn you!

I've installed this rom today and I've been playing with it a bit. When focal stopped working I have rebotted the phone and it stopped on GT-N7000 logo. So I rebooted to recovery and restored CM10.1 backup. After that phone didn't requested for SIM card PIN number any more. Now I discovered that my imei is 00...0000. Fortunately I have EFS backup and starting to restore it :)

I'll edit post and post the result.

EDIT:

Worked!
[Galaxy Note GT-N7000 Original Android Development] noteandfound:
That IMEI corruption happens rarely. Thats not the cause. Actually I had it 3 times already. 1 on TW jb. 2 on cm10.1..

I also did what you did and there is no IMEI corruprion on my phone.
[Galaxy Note GT-N7000 Original Android Development] ThaiDai:
Trim command in 4.3

The german website "Heise Online" wrote an article about the support for the trim command in Android 4.3.

Normally deleted files on SSDs are only "registered" by the OS. So the flash controller didn't get an information which files/blocks to delete. Resulting in devices getting slower with the time (N7000 is one of the listed devices).

In 4.3 the fstrim command will physically delete files on the chip (once a day, after 1 h without user actions and enough battery power).

Is this command already activated here for the Galaxy Note (maybe it is always activated in 4.3 for all devices).

In the related discussion forum one user writes without any evidence that this command will surely brick your device because of the faulty eMMC-Chip. And is already quoted in a german Android forum.

So: When using fstrim is there any chance that deleting files will "activate" the faulty write command on the eMMC chip? Or is this impossible because of the precautions in the safe CM kernels?

And: If the trim command really is a part of Android 4.3 minimizing these resulting lags, then we will see soon a lot of members switching to CM (right now building the latest version myself...).
[Galaxy Note GT-N7000 Original Android Development] DeKubus:
Came here to ask exactly the same question about the brick bug. The lagfix app from the market (which just calls the system TRIM function) especially states that users with faulty memory should not use it. Hope the Cyanogenmod team has considered this. Just in case...

In b4 new hardbrick wave :)
[Galaxy Note GT-N7000 Original Android Development] invalidcracker:
Cm 10.2 is too much faster. Greatly improved multi tasking, Atutu score is 9000s it used to be around 7000s for cm10.1

Bugs till now:

-Graphical gliches

-SU but it works well after trying install latest superuser binary

-Some Focus FCs with halting cam

-Kill app back button not working

Tons thanks devs :D
[Galaxy Note GT-N7000 Original Android Development] galaxys s:
rom s still many bug ...thanks team so quick
[Galaxy Note GT-N7000 Original Android Development] nicorottye:
too many errors

Sent from my GT-N7000
[Galaxy Note GT-N7000 Original Android Development] masiushc:
Come on guys stop trolling it said that this is experimental release.so wait and sit quite.
[Galaxy Note GT-N7000 Original Android Development] moviecut:
wow, useful. thank you!

could you please give us more details or simply shut up?
[Galaxy Note GT-N7000 Original Android Development] projeto56:
Do not feed the trolls guys. No one is that stupid.
[Galaxy Note GT-N7000 Original Android Development] AA1973:
I got stuck once and rebooted in recovery, cleared cache and dalvik cache and it booted fine. With imei and everything :)

Situation was that the phone shut down due to an empty battery and after the full charge it got stuck.

Don't think that restoring a backup is the first of all options.
[Galaxy Note GT-N7000 Original Android Development] deepaklunked:
A Bug report

Hi XpLoDWilD..

Hats off to ur hardwork..

Well, i just wanted to say that in the latest build, i am facing a bootloop!! Am i the only one with this issue??
[Galaxy Note GT-N7000 Original Android Development] karamelos:
For su acess

Go in developer option disable root, go out

Come back to developer enable root acess .
[Galaxy Note GT-N7000 Original Android Development] dragoslav.nikolic:
Cant find developer options? Any pointers where it could be?
[Galaxy Note GT-N7000 Original Android Development] korado:
Try settings,about phone,5 or more clicks on build number
[Galaxy Note GT-N7000 Original Android Development] AA1973:
7 :P
[Galaxy Note GT-N7000 Original Android Development] t0kgrumps:
Performance is improved in 4.3 but could someone explain why my battery drains super quick? I got from 100 to 77% in 30 mins. The weird thing is that I did not turn on anything I just leave it after I've charged it fully and my battery is 5200mah battery
[Galaxy Note GT-N7000 Original Android Development] AA1973:
Install better battery stats
[Galaxy Note GT-N7000 Original Android Development] paultje162:
I do not have problems with that. I'm at 2d and 3 hours now and i have 13 precent left.
[Galaxy Note GT-N7000 Original Android Development] LordManhattan:
Meanwhile at Samsung:

- "Hey John! I just noticed a bug here. I'm working on the 4.3 update for the S4, and I noticed that all 15 test phones died and caught fire. Shouldn't we investigate this further?"

- "Steve, pack your bags; you're fired."

BREAKING NEWS: Samsung employee, Steve O'Donnell missing. More at 11.
[Galaxy Note GT-N7000 Original Android Development] b00gieMan_droid:
Huh? Dafuq I just read?
[Galaxy Note GT-N7000 Original Android Development] MR.Samo:
Congratulations U have just read the ......... TRUTH
[Galaxy Note GT-N7000 Original Android Development] XpLoDWilD:
http://xdaforums.com/showthread.php?p=44132997#post44132997

Please move your nonsense there. Not three days and I'm already locking this thread...
[JAM, MDA Compact, S100 Software Upgrading] saquib:
Hi,

I wonder if you could advise which ROM is the 'best' one to upgrade to? I've had my T-Mobile UK MDA Compact for a few days, just backed-up the ROM, now need to decide which ROM I should move to. Current version is 1.01.00 WWE, Radio 1.00.10. So, will moving to anyone of the above 2 ROMs make a difference and what?

Thanks!
[JAM, MDA Compact, S100 Software Upgrading] dangel:
I've just ordered my QTek s100 so the same quesion is floating round my mind too... :)
[JAM, MDA Compact, S100 Software Upgrading] kta:
IMHO if you're not experienced with flashing ROMs go for the imate upgrade. Trying the big storage might make you hate the JAM if something goes wrong :wink:

Having said that, I went for the Big Storage (not very experienced, but have a good idea).

Also, keep in mind that the Big Storage ROM will soon be out-dated unless someone finds a way to implement the same "hack" to newer ROMs (or Anansky returns to the forum).
[JAM, MDA Compact, S100 Software Upgrading] John R:
Try the I-mate Rom first, the only difference is the storage. If you can live without big storage fine. Also you can try big storage once you are comfortable with your device.
[JAM, MDA Compact, S100 Software Upgrading] PapaDocta:
yep go for the imate update (latest version is 1.11) which has better sound quality and more stable than the other.......
[JAM, MDA Compact, S100 Software Upgrading] dangel:
Great thanks for the tip - any idea where on the ftp site the rom is?
[Samsung Epic 4G Touch] No4g4Me:
i have been on ics gallery and viewed gif mms that played when i opened them from the inbox and selecting gallery, since the upgrade to jb the phones gallery stays at a still image instead of animation.... is there some binaries i can flash to enable this feature? also is thier a program where i can edit any apps functions ex.. set program to open by default when selecting a file ex... select the mms gif inside my default sms app to open a gif viewer? because i have a gif viewer installed it doesnt show up though as a optional program when i click on my gif inside sms? thanks in advance.
[Samsung Epic 4G Touch] bilgerryan:
Settings/Applications... Press menu, hit "reset app preferences"
[Nexus 7 (2013) General] nhidog:
Anand hinted that these CPUs are just underclocked Snapdragon 600, I'm curious what speed cpu binning are we receiving. Similar to this thread http://xdaforums.com/showthread.php?t=2215710

I'd like to know what PVS people are getting. If you are rooted, open up a terminal

su
cat /proc/last_kmsg | grep acpu

mine is

SPEED BIN: 14

ACPU PVS: 3
[Nexus 7 (2013) General] DebauchedSloth:
Mine:

SPEED BIN: 14

ACPU PVS: 3
[Nexus 7 (2013) General] Sleepy!:
So how is the Speed binning graded? Any idea?
[Nexus 7 (2013) General] jc monkeyballs:
Mine is:

Speed bin 14

Acpu pvs 4
[Nexus 7 (2013) General] Nburnes:
shell@flo:/ $ su
root@flo:/ # cat /proc/last_kmsg | grep acpu
[ 1.092751] acpuclk-8064 acpuclk-8064: SPEED BIN: 14
[ 1.092904] acpuclk-8064 acpuclk-8064: ACPU PVS: 3
[ 1.095589] acpuclk-8064 acpuclk-8064: CPU0: 12 frequencies supported
[ 1.095772] acpuclk-8064 acpuclk-8064: CPU1: 12 frequencies supported
[ 1.095864] acpuclk-8064 acpuclk-8064: CPU2: 12 frequencies supported
[ 1.096047] acpuclk-8064 acpuclk-8064: CPU3: 12 frequencies supported
[Nexus 7 (2013) General] nhidog:
Higher the PVS the better, check first post regarding HTC One. Probably won't have the voltage table until someone takes a look at the kernel source.
[Nexus 7 (2013) General] Sleepy!:
Yeah. I got that about the PVS.

PVS is basically a grading of the optimum voltage of the CPU at the highest default clock speed.

Just wanted to know how Speed binning is graded.
[Nexus 7 (2013) General] husker91:
Here's mine.
[Nexus 7 (2013) General] zaclimon:
I think this would be the voltage table basing from the kernel source (I may be wrong, the device has like config for 3 different chipsets :eek: however flo is based on mach_apq8064 so I took the information from acpuclock-8064.c)

PVS3:

static struct acpu_level tbl_PVS3_1512MHz[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 900000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 900000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 900000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 900000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 900000 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 925000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 950000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(14), 975000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(14), 987500 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(14), 1000000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(14), 1037500 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(14), 1050000 },
{ 0, { 0 } }

PVS4:

static struct acpu_level tbl_PVS4_1512MHz[] __initdata = {
{ 1, { 384000, PLL_8, 0, 0x00 }, L2(0), 875000 },
{ 1, { 486000, HFPLL, 2, 0x24 }, L2(5), 875000 },
{ 1, { 594000, HFPLL, 1, 0x16 }, L2(5), 875000 },
{ 1, { 702000, HFPLL, 1, 0x1A }, L2(5), 875000 },
{ 1, { 810000, HFPLL, 1, 0x1E }, L2(5), 887500 },
{ 1, { 918000, HFPLL, 1, 0x22 }, L2(5), 900000 },
{ 1, { 1026000, HFPLL, 1, 0x26 }, L2(5), 925000 },
{ 1, { 1134000, HFPLL, 1, 0x2A }, L2(14), 950000 },
{ 1, { 1242000, HFPLL, 1, 0x2E }, L2(14), 962500 },
{ 1, { 1350000, HFPLL, 1, 0x32 }, L2(14), 975000 },
{ 1, { 1458000, HFPLL, 1, 0x36 }, L2(14), 1000000 },
{ 1, { 1512000, HFPLL, 1, 0x38 }, L2(14), 1012500 },
{ 0, { 0 } }
[Nexus 7 (2013) General] cmbeid:
No such file or directory

Apparently there is no /proc/last_kmsg on my device. Any idea why?
[Nexus 7 (2013) General] droyd4life:
Cpu Speed

Here's mine!
[Nexus 7 (2013) General] plh233391:
Speed bin: 14

Acpu pvs: 6
[Nexus 7 (2013) General] nhidog:
Do you have root? If so reboot your device. If your file is 0kb, you are not root, thus you cannot read it.
[Nexus 7 (2013) General] cmbeid:
Yeah, I am rooted. Apparently reboot did it. Although I have rebooted several times, so not sure why this time fixed it.
[Nexus 7 (2013) General] nhidog:
Wow PVS 6, I believe thats the highest well looking at the HTC One thread. Guess all Qualcomm did was clocked these at lower speeds. Doesn't appear we have rejects. I want a 6 ;)
[Nexus 7 (2013) General] ZBoater:
Speed bin: 14

acpu pvs: 2
[Nexus 7 (2013) General] flyinion:
I'm having the same problem. I definitely have root. Unlocked the bootloader and installed SuperSU. Titanium, Root Explorer, and my Terminal app all gained root access. The closest file I have in the /proc folder is a kmsg file that is 0kb. I don't have a last_kmsg file at all. No idea what I'm doing wrong.
[Nexus 7 (2013) General] nhidog:
Reboot then look for file
[Nexus 7 (2013) General] phonic:
For anyone having issues finding last_kmsg or being able to grep for those lines even though they are rooted, do the following:

1) Power off your device normally.

2) Power it back on.

3) Soft reboot the device using the terminal (ie: su; reboot) or a reboot widget.

4) Check /proc/last_kmsg again. It should be there with those lines now.

On a fresh power up, for some reason I'm not sure of, that file doesn't seem to be present. If you do a soft reboot it suddenly appears, but if you had your device on for too long the earlier messages get truncated. Powering off/on and rebooting clears this up.

BTW, my scores are 14 and 4, respectively.
[Nexus 7 (2013) General] Brenex:
14 / 3 here. I was hoping to be surprised with a 6 too :D
[Nexus 7 (2013) General] rmkilc:
Speed Bin: 14

ACPU PVS: 3
[Nexus 7 (2013) General] brainard52:
14 and 2 for me.

In the case that these are indeed just underclocked snapdragon 600 chips, how would one go about getting the most out of them?
[Nexus 7 (2013) General] phonic:
Custom kernel will likely help. Will have to wait for the official source though.
[Nexus 7 (2013) General] zaclimon:
Official source is already out here:

android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-jb-mr2/
[Nexus 7 (2013) General] phonic:
Thanks, I didn't know that. Well that's good news. Now we just need one of our ace kernel developers to cook something up.
[Nexus 7 (2013) General] Ironclad Lou:
14 / 3 for me as well.
[Nexus 7 (2013) General] flyinion:
Thanks that worked. I got a 14 and a 2.
[Nexus 7 (2013) General] Deathman20:
14 / 3 here.

Can't wait to bump the speed up.
[Nexus 7 (2013) General] conan1600:
So exciting. Can't wait to see what gets cooked up
[Nexus 7 (2013) General] tweaked:
14 / 3 here.
[Nexus 7 (2013) General] V8vroom:
14/4
[Nexus 7 (2013) General] Artood2s:
14/3 for me.

Sent from my Nexus 7
[Nexus 7 (2013) General] gerald410:
14/3 for me.
[Nexus 7 (2013) General] smirkis:
12/3 here

How can this even be possible when ifixit did the tear down and saw the s4 pro?
[Nexus 7 (2013) General] mike.r.olson:
14/4.

Anybody know how well the Snapdragon 600 in the One OC's/UV's?
[Nexus 7 (2013) General] Poser:
14/3
[Nexus 7 (2013) General] tiny4579:
14/4. The voltage control / overclocking code can be adapted from mako or an s600 device fairly trivially. I started looking at it yesterday.

Oh and congrats to the person with a PVS of 6. My HTC one is a 2 sadly.
[Nexus 7 (2013) General] jiggytom:
14/3
[Nexus 7 (2013) General] stab244:
14/2. Damn...
[Nexus 7 (2013) General] mac404:
14/3...could be worse. Not like I really have a desire to OC this anyway.
[Nexus 7 (2013) General] d1ez3:
14 / 4 here. Can someone give a more detailed explanation of what these numbers mean
[Nexus 7 (2013) General] zaclimon:
http://xdaforums.com/showthread.php?t=2215710
[Nexus 7 (2013) General] dch921:
14/5 here
[Nexus 7 (2013) General] george241312:
14/4
[Nexus 7 (2013) General] nhidog:
I'm running tiny kernel with max oc set to 1728 and UV set to -100mw from PVS3 all stable... essentially running lower voltage than PVS6. I'm liking this CPU.
[Nexus 7 (2013) General] Sleepy!:
That's the beauty of Krait, my friend. :)

Though I doubt it'll be able to OC much more than that.
[Nexus 7 (2013) General] immunityx:
i wonder whats the max we can push these chips, i heard they are actually snapdragon 600's underclocked instead of the S4 Pro which is awesome if thats true
[Nexus 7 (2013) General] Deathman20:
Followed your thinking with that one. Set mine to UV just -75mw as well having the PVS3 tablet.

Gives it a nice boost in benches.
[Nexus 7 (2013) General] desire amit:
what is the use in my android smartphone
[Nexus 7 (2013) General] demandarin:
They didn't see the S4 pro. Qualcomm has ttheir naming schemes all jacked up. Official S4 pro krait 200 cores. It was seen that this new N7 has krait 300 cores with Andreno 320 gpu. So this is actually a variant of Snapdragon600. Just clocked lower than qualcomms own official spec speed for other S600 models. Plus this has 2 fb of ddr3 ram. So this is completely different setup than in the nexus4. Qualcomm and Asus/Google just caught themselves trying to be slick calling it S4 pro. Having people think it's the older one. When in fact this is a new variant of Snapdragon600.
[Nexus 7 (2013) General] CiDhed:
Damn, 14/2.
[Nexus 7 (2013) General] conan1600:
14/2
[Nexus 7 (2013) General] JPOKeefe:
Its not working for me
[Nexus 7 (2013) General] nhidog:
reboot as in a 'reboot'

terminal

su
init 6

then try again, if your device has been up for a while the file may have cleared
[Nexus 7 (2013) General] JPOKeefe:
Still not working
[Nexus 7 (2013) General] nhidog:
Did you 'reboot' or type "init 6", apparently init 6 doesn't work on android.

su
reboot
[Nexus 7 (2013) General] JPOKeefe:
yes i tried rebooting and doing it
[Nexus 7 (2013) General] nhidog:
You know 'reboot' does not mean 'power off' then 'power on' right?

http://xdaforums.com/showthread.php?p=44026642&highlight=reboot#post44026642
[Nexus 7 (2013) General] muyoso:
To the guy who isn't able to do it, try updating superuser. That worked for me. Open it up and it will prompt you for an update.

14/2 BTW for me. Absolutely no idea what that means.
[Nexus 7 (2013) General] JPOKeefe:
yes i know it doesnt ive tried that and updated superuser still wont work. i checked the filesystem and the file is there but its not working i tried to pull it on adb but that doesnt work either
[Nexus 7 (2013) General] nhidog:
well since you can reach adb, you can pull up adb shell and check unless your file is 0kb.

~ qdinh$ adb shell
root@flo:/ # cat /pro
proc/ property_contexts
root@flo:/ # cat /proc/last_kmsg | grep acpu
[ 0.808837] acpuclk-8064 acpuclk-8064: SPEED BIN: 14
[ 0.809020] acpuclk-8064 acpuclk-8064: ACPU PVS: 3
[ 0.811553] acpuclk-8064 acpuclk-8064: CPU0: 15 frequencies supported
[ 0.811737] acpuclk-8064 acpuclk-8064: CPU1: 15 frequencies supported
[ 0.811828] acpuclk-8064 acpuclk-8064: CPU2: 15 frequencies supported
[ 0.812011] acpuclk-8064 acpuclk-8064: CPU3: 15 frequencies supported
root@flo:/ #
[Nexus 7 (2013) General] phonic:
Did you try the instructions I posted in this thread here:

http://xdaforums.com/showthread.php?p=44026642&highlight=reboot#post44026642
[Nexus 7 (2013) General] darkrom:
14/3
[Nexus 7 (2013) General] mortzz:
Speed bin 14, PVS 3.
[Nexus 7 (2013) General] nhidog:
Wouldn't boot at 2160... but booted at 1890 just fine... good times
[Nexus 7 (2013) General] bso44:
14/3
[Nexus 7 (2013) General] corythug:
14/3
[Nexus 7 (2013) General] jlevy73:
mine is

SPEED BIN: 14

ACPU PVS: 5
[Nexus 7 (2013) General] nhidog:
@1890 cpu/533 gpu
[Nexus 7 (2013) General] Shikyo:
My 32GB ended up 14/3

Of course the 16GB I got for my girlfriend a week later is 14/5
[Nexus 7 (2013) General] Semantics:
Mine has a 14/3 also.
[Nexus 7 (2013) General] Deathman20:
What kernel are you using to of up that high?
[Nexus 7 (2013) General] nhidog:
Built my own modified from tiny's.
[Nexus 7 (2013) General] Dagnet:
Just got mine today

ACPU PVS: 5

SPEED BIN: 14

yay!
[Nexus 7 (2013) General] zim2dive:
Bottom of the barrel for me .... PVS of 1 :(
[Nexus 7 (2013) General] immunityx:
What voltage did you try to run the 2.1ghz step at?
[Nexus 7 (2013) General] Jayrod1980:
Seriously don't even pay attention to this if the nexus 4 is any indication. Having gone through many nexus 4s, there's lower binned models that perform better than cat 4/faster examples. The bin is just a rough guide. I had a fast model n4 that couldn't even overclock by 100 MHz. Don't take the bin id as gospel
[Nexus 7 (2013) General] dems86:
14

3
[Nexus 7 (2013) General] nhidog:
Default pvs3 whatever elementalx has @ 2.1. Don't think it's a voltage issue as I increased max to 1450000 from 1300000 default. Seems 1.89 is the wall, since 1.945 also sits at Google logo. Maybe someone with more knowledge will be able to break it.
[Nexus 7 (2013) General] cryogenist:
Mine 14 / 3.. 32GB
[Nexus 7 (2013) General] aa_chow:
14/2
[Nexus 7 (2013) General] lopri:
I ran bug report on one I saw at a Bestbuy and it reports speed bin 14 / pvs 1. I guess it's a rarity.
[Nexus 7 (2013) General] [TSON]:
I was deathly afraid I was gonna be stuck with a terrible bin, YES!!!
[Nexus 7 (2013) General] Wraith91:
14 / 4 for me. I probably won't go all out, but I've always enjoyed occasionally overclocking and undervolting just for fun
[Nexus 7 (2013) General] andrewNY:
14/5 (32gb purchased at Best Buy)
[Nexus 7 (2013) General] jev3gs:
32gb with a 14/6 from Officemax

So after years of trying to overlooking and failing finally I have a mobile cpu that should be good.

Makes me remember my good ole Celeron 300a.
[Nexus 7 (2013) General] Deathman20:
Ah the good old days of Celeron's. Just got rid of mine last year.
[Nexus 7 (2013) General] zaclimon:
Not bad for myself. :P

SPEED BIN: 14

ACPU PVS: 4

Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
[Nexus 7 (2013) General] mailboy1412:
So does this mean devices with higher numbers are better?
[Nexus 7 (2013) General] Imppy:
14/3

So the higher the number the better undervolting?
[Nexus 7 (2013) General] jev3gs:
Wow that awesome, I threw mine out last year but the pc was decommissioned years ago. Love that 300a!
[Nexus 7 (2013) General] ÜBER™:
Yep, if you go to the thread linked in the OP it explains it.

0,1,2,3,4,5,6.

The higher the number the better the binning and lower the voltage the CPU will perform at.

On topic I got

14/4
[Nexus 7 (2013) General] SaberJ2X:
speed 14

pvs 2

but I've set it up with pvs 5 voltages and runs perfect...
[Nexus 7 (2013) General] Sleepy!:
So I finally checked mine today.

Speed bin 14

PVS 3
[Nexus 7 (2013) General] mdamaged:
14/3