yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MBQ_:
Download this and figure it out. :good:

There is no 'go-to' Governor due to each phone reacting differently to Governors.

http://goo.im/devs/MBQsniper/Apps/MBQs CPU Guide/Alpha/MBQsCPUGuideAlpha0.0.5.apk
[Samsung Galaxy Nexus] nixholas:
Actually MBQ, It depends on how old your battery is and how your OMAP chipset's quality is in your device :)
[Samsung Galaxy Nexus] MBQ_:
That too
[Samsung Galaxy Nexus] cruel91:
I just have a freeze after end a call. Here is the logcat. I uses default settings instead of changing governor to hotplug with min of 192mhz (both min and min screen on) with PA ROM 05JUL. I'm very appreciated for your work, no mean rushing
[Samsung Galaxy Nexus] lost_:
Amp, so far so good with 8 hours of running b12 on hotplug gov, 384 min, mps 0, undervolted about -100mv . No sod or freezes. I think 192 is just problematic for some phones to begin with.

I'd love to see the frequency steps from Faux Kernel brought here (350, 525, 700, 810, 920, 1060, 1200, 1350, etc). The stock-like 350 MHz minimum frequency is low enough to yield great battery life.
[Samsung Galaxy Nexus] parkson:
Not sure you'd get much savings from 384 to 350 to 192 considering they pretty much all draw the same voltage :confused:
[Samsung Galaxy Nexus] LibertyMonger:
I've been running this kernel all day with Liquidsmooth, making calls, answering calls, listening to bluetooth and all with no issues at stock settings. Everything is running great so far, great work!
[Samsung Galaxy Nexus] MBQ_:
CPU Guide for those interested. :)
[Samsung Galaxy Nexus] spupuz:
MBQ, to be honest the apps layout is quite unusable, i suggest you to group gov sched and other thing and leave a left side menu with less entries.
[Samsung Galaxy Nexus] nixholas:
Okay. After reading this whole page, I have a few answers :)

- 350MHz stock like clock is the default lowest, so no need for changes :)

- And, I'll see to the logcat. I fix if possible(99% yes xD)

Last but not least, I'm finally leaving the comfort zone. 3.10 Porting has begun. I'll try my best to fix adb :) Just to say, This kernel will head on to battery consumption, I'll focus on core hotplugging first, once all's well there, we'll focus on RAM, then, Clocking and voltaging. I'll try to create a new Modified DVFS by myself, and try to reduce as much processes needed to control the voltage.

Also, Please do not rant at me for upcoming 3.10 releases. It'll either be in bootloop, or "Android is Upgrading" loop. And yes, I have an experience in porting Linux kernels, I'm a computer engineer and has worked on UNIX. So please be patient for me to get 3.10 working :)

Peace.

if I take too long, I'll leap to the latest Linux kernel and retry porting.
[Samsung Galaxy Nexus] MBQ_:
Oh absolutely, it is quite messy.

I have ideas about how im going to re-do the layout.
[Samsung Galaxy Nexus] Ziyan:
Nice! If you have some progress, I suggest you to create a topic in the developer section, so other devs can help you, and users can see the progress, so they wont keep asking about it :good:
[Samsung Galaxy Nexus] erestrepo92:
Which one of the B's files do you recomend? My first worry is about getting the battery last longer. I read on the very first pages that you cannot have wifi, is that true? Thank you
[Samsung Galaxy Nexus] Bl4ck3urn:
Flash B12 and you are good to go!
[Samsung Galaxy Nexus] erestrepo92:
thank you. I'll give it a try, hope everything works right!
[Samsung Galaxy Nexus] nixholas:
Always use the latest build.

WIFI didn't work in the initial open alpha release. Why? Because I was building WLAN as a module. And didn't put it in the flashable zip. So then, I merged WLAN with the zImage, and now it worked. So everything after B2 Is super safe for use.

I'm dissatisfied. I'm removing Multicore power Saving. I was right, It is broken. Take note guys! From then on, Hotplug is 99% bugless! :) And also, MPS isn't really efficient. So please do not rely on it heavily to save power.
[Samsung Galaxy Nexus] Citizen_Snips:
Amp I had a freeze up on hotplug with multi core set to 0.

From my understanding a sleep of death is when you put the phone to sleep and upon trying to wake it again nothing happens? I have never had that happen on your kernel. Exactly the opposite, actually. I will be using the phone and everything will just freeze. Power button / plugging it in gets no response and neither does waiting for it to clear itself up. Must pull battery, so no logs. This happens to me roughly once every day or two. I can't seem to replicate it either. Sometimes I am playing a game with a lot of open apps in the background and others I will just boot the phone and only have 1 foreground app open.

Changes I made in trickster...

Min frequencies 384 (happened more often on 192)

Max freq @ 1344

GPU oc 512

Westwood / sioplus

MCPS 0

Morfic colors

Edit: running the same setup on two sperate toros with similar results. Slim bean 7 official
[Samsung Galaxy Nexus] TheMysteriousOne:
Trying lowering CPU and GPU to 1228 and 384 respectively.
[Samsung Galaxy Nexus] Citizen_Snips:
Never had any issues running 512 GPU until now and I only OC max freq one step because I set it to 512. Works wonders on fancy kernel. I will give it a shot, but like I said I can't replicate it. So if it doesn't happen in 3 days from lowering those 2 steps I guess I'm good. Well I'll give it a shot, thanks!
[Samsung Galaxy Nexus] nixholas:
Use deadline. SIOPlus is still unstable.

Deadline is always my recommendation :)

Anyways,

We gotta focus on clocking management.

The OC is eating up battery by 30% according to tests from my friend. I shall focus on optimisation :)
[Samsung Galaxy Nexus] lost_:
No freeze here

hotplug

384 to 1344 (underclocked -100 to -50 mv)

GPU 307

westwood deadline

MCPS 2
[Samsung Galaxy Nexus] LibertyMonger:
Running flawlessly like a champ on hotplug/deadline min 384 all day, no issues whatsoever! Anybody know which IO scheduler is best with hotplug?
[Samsung Galaxy Nexus] misterk267:
I usually find that schedulers are a matter of preference. I personally prefer either deadline or bfq, with Franco's winning tunables. Whatever you find works best on your phone is what you should use. :)
[Samsung Galaxy Nexus] nixholas:
Customization is always BFQ.

Optimized speed is always deadline :)
[Samsung Galaxy Nexus] miqz:
I don't know why but with b12 i always got freeze when i on lockscreen.

But with same settings on b11 i never got a problem with freeze or sod

Interactive deadline

192-1220

Maybe because not compatible rom? :confused:
[Samsung Galaxy Nexus] OU']['lander:
Are you on stock voltages? Try to raise the min freq to 384 MHz, some devices don't get on very well with 192 MHz freq, independently of the governor. It's also proved that lower freqs such as 180/192/230 MHz don't effectively help to save battery, because the gap between min and max freqs is bigger, for example, than using 350/384 MHz instead as min, and 1228 MHz as max (bigger gap = bigger scaling).

'][' Maguro powered by Slim Bean 7 & ASKP b12 ']['
[Samsung Galaxy Nexus] miqz:
Yes i already set 384mhz but still the same..

is this because i flash b12 from b11?
[Samsung Galaxy Nexus] nixholas:
Yes. Note that your compression on Build 11 is fully XZ.

On build 12,

The kernel compresses on XZ

But,

Decompresses on LZ4

And GZIP for RAMDisk on Build 11

LZ4 for RAMDISK for Build 12
[Samsung Galaxy Nexus] miqz:
thanks for your response :good:

i will test tonight with full wipe and also new rom..

the best kernel so far i use :D
[Samsung Galaxy Nexus] erestrepo92:
How does the battery life extender work? I mean do i have to do something else after installing the kernel to improve battery life?
[Samsung Galaxy Nexus] Alphav00:
The battery life extender is just too avoid charging to 100, set it to 99, it will only charge to 99. Set to 98... and so on. Our batteries slowly die, and not charging fully supposedly helps. Never noticed any benefits in short term tho
[Samsung Galaxy Nexus] info[]box1:
Jumping on the new update now. Downloading now and Excited..
[Samsung Galaxy Nexus] schukje:
You wont be sorry friend!

grtz from the crazy basterd from holland. powered by kickflip/axiom and askp kernel
[Samsung Galaxy Nexus] spupuz:
why not?
[Samsung Galaxy Nexus] nudou350:
Hotplug doesn ' t work for me.. Lots of freezes.. It destroyed my battery /:
[Samsung Galaxy Nexus] quickstang:
Umm.. As in this is a bad ass kernel & you should flash it. He said you won't be sorry, not you will be sorry.

Sent from my iphone killing Galaxy Nexus running fancy kernel & apophis9283 AOKP ROM. For the love of everyone on forums READ BEFORE YOU POST.
[Samsung Galaxy Nexus] LibertyMonger:
Until I woke up this morning to an SOD. Phone sat by my bedside all night untouched and when i woke it was stuck with SOD. So i will go back to trying stock settings I guess. Still freakin awesome kernel.
[Samsung Galaxy Nexus] Saythis:
Getting SOD's as well with hotplug and 384 min after its been sitting for a while.
[Samsung Galaxy Nexus] Edgarngg:
Also getting SOD s and freezes on min 348 hot plug, 2 mcps,
[Samsung Galaxy Nexus] nixholas:
I'm freaking gonna swear at the creator of Hotplug xD OF ALL BUGS ON CHIPSETS WHY TUNA MUST BE BUGGED :( xD LOL. Well, I see a couple of fixes for multicore management again. I'll merge with linux-next branch and see if we can rectify the issue :)

In conclusion, NEVER CHANGE hotplug stock settings and NEVER set MPS to 1/2 when hotplugging. And from the looks of it, only 30% of the users are having a bugless hotplug, including me. I'll carry on fixing it.

Also,

Do follow the new twitter :)

twitter.com/amperific

I'm a frequent twitter user, I tweet anout 100-200 tweets/day. So yeah, kinda crazy xD follow that account for more news and secret releases xD
[Samsung Galaxy Nexus] jpg3927:
Will you make new thread for all new 3.10 kernel for gnex?
[Samsung Galaxy Nexus] lost_:
I'm on the minority then. Going on battery for 1d 17h with Hotplug and MPS 2. Min 384, Max screen off 525, Max 1344. Zram off. Undervolted. Dimmer screen setting than stock FWIW.
[Samsung Galaxy Nexus] nixholas:
Yes and it's not so soon. I'm still gonna focus on the current ASKP Project first.

Not really :) Just customize your own settings. Different phones have different behaviour just like humans, so well, you need to set what's best for your phone.

Also,

I'm adding a group of new fixes.

If all's well, Expect one of the next few builds to be the Super Milestone.

Super Milestone means an extremely major update, with more than 200 commits.
[Samsung Galaxy Nexus] lost_:
My comment about being in the "minority" was referring to your 30% post of bugless hotplug. My phone is one of those - knock on wood.

EDIT:

Nice to get an old school phone experience. Going on 2 days 19 m, with battery down to 25% and 2h 6m screen-on, 37m voice calls. This include few hours in a low to no signal spot, some GPS, some browsing and a few play store updates.

On Mirage ROM. Trickster Mod settings a few posts back.
[Samsung Galaxy Nexus] openlatedotorg:
SOD on slim build 7.

After idle (3 hours). OC 1.3 interactive/deadline
[Samsung Galaxy Nexus] miqz:
i'm also on slim build 7 and no sod or freeze after more than 4 hours

interactive 1220

deadline

MPS 2
[Samsung Galaxy Nexus] nixholas:
Brother, More details and a log :)

That'll help me a million times. :)

I'm porting some sound features. So stay tuned.
[Samsung Galaxy Nexus] huskerkate:
cool!! i'm getting twitchy - i haven't flashed anything in, like, 3 days...!! :cyclops:
[Samsung Galaxy Nexus] Starsream88:
Can't wait :thumbup:
[Samsung Galaxy Nexus] sebby d:
Every night I am getting pretty high idle drain. It shows that kernel(android os) is keeping phone awake. It is not a big problem for me but I just wanted to let you know that I am losing anywhere from 8-12 percent over a 5 hour period.
[Samsung Galaxy Nexus] MBQ_:
Next up:

Super duper milestone ;p

Followed you on Twitter.
[Samsung Galaxy Nexus] vlc_marcos:
Amperific, is possible to make this kernel to work with the miui rom? could be nice :D thanks
[Samsung Galaxy Nexus] killersloth:
Boss kernel

Running good ;)
[Samsung Galaxy Nexus] adrianmak:
miui rom compatible ?
[Samsung Galaxy Nexus] killersloth:
Most kernels that flash just a zImage (any kernel updater) are miui compatible. Or you can unpack boot image and get the zImage yourself to flash with miui.
[Samsung Galaxy Nexus] nixholas:
Shall follow back in 10mins. (:

Right now, I'm just gonna stone on my ed because of a love message xD

yes. Like I said, Next build :) Super milestone :)
[Samsung Galaxy Nexus] vlc_marcos:
very good news.

:)
[Samsung Galaxy Nexus] frenchy714:
Thanks for the hard work Amp! I have a possible dumb question and couldn't search the thread from the XDA app. I know that kernels for our device should work with all variants "Tuna", but I'm a little thrown off by the OP "This is Maguro specific", then it says that downloads here compatible with all variants or something to that affect....Will this in fact run on toroplus? Thanks in advance for the response!
[Samsung Galaxy Nexus] huskerkate:
yes, this is a tuna kernel. it's just the thread that is maguro-specific - i.e., for addressing issues relating only to maguro devices. Amp has created various threads to discuss topics for each variant, but it's the same kernel. i download the kernels from this OP, but flash them on my toro.
[Samsung Galaxy Nexus] frenchy714:
Thanks for clearing that up :thumbup:.
[Samsung Galaxy Nexus] huskerkate:
Enjoy! this thing flies!
[Samsung Galaxy Nexus] nixholas:
OF COURSE :)

Have my big bacon on the bext build :)

200 Commit :) 1/4 my way there :)

Shall release a PSM build :)
[Samsung Galaxy Nexus] irizwan:
Impatiently waiting :P
[Samsung Galaxy Nexus] frenchy714:
Running the latest stable, and it's BLAZING! Keep up the great work Amp!
[Samsung Galaxy Nexus] sebby d:
Eagerly awaiting next release. This kernel is super smooth. Idle drain over night randomly stopped last night. Only thing I changed yesterday was governor to hyper.
[Samsung Galaxy Nexus] nixholas:
On the next build, I'll remove Hotplug from the line and put AMPlug in. Also, we're gonna release the PSM build eiter tomorrow or tuesday, so stay tuned for the Pre-Super Milestone :)
[Samsung Galaxy Nexus] info[]box1:
What is your twitter tag...?
[Samsung Galaxy Nexus] rebretz000:
Can't wait to try this kernel. Getting a brand new GNEX Tuesday. Sold my S3 and going to sale my XT926. I've missed all the ROMs and Kernels.
[Samsung Galaxy Nexus] parkson:
Downgrade from S3 to GN? :confused: I would have gladly traded you my gf's like-new GN for it lol
[Samsung Galaxy Nexus] killersloth:
Definitely not a downgrade ;)
[Samsung Galaxy Nexus] justen7723:
Agreed, its all about preference. I don't care about a better camera, bigger screen, bigger battery all of the better hardware for that matter. I'd rather have the fun open sourced software of the gnexus. my wife has an s3 with both of them on aosp ROM, there isn't much difference in performance at all. I have spare batteries so I don't care about battery life all that much, sure I try and get the most out of it but I'm not really struggling to make it through a day anyways. :thumbup:

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] misterk267:
Cannot wait. This kernel got me away from Franco's. And it just keeps getting better. :D. Eager to see what you have in store for us in this upcoming release.
[Samsung Galaxy Nexus] nitsua98:
If def snag one of those dna's though now that they're only $50. Too bad my contract isn't over yet.
[Samsung Galaxy Nexus] PatimusXPrime:
Yeah my dad just got a DNA, they're real sexy. I cant justify spending money to get off the Gnex though lol

Maybe wait for the N5? OT, ill stop now
[Samsung Galaxy Nexus] nixholas:
[MENTION=986006]greens[/MENTION]pecsguy :) Personal [MENTION=5310723]Amperific[/MENTION] :) Official

Oh and by the way, There will be patches from linux upstream also ;)
[Samsung Galaxy Nexus] Starsream88:
Waiting for tomorrow :D
[Samsung Galaxy Nexus] huskerkate:
we gotta have something to occupy all of our nervous in-anticipation energy...

i haven't really seen much about the N5 - any decent rumors out there? i'm guessing it's gonna be LG again, or maybe Sony...?
[Samsung Galaxy Nexus] info[]box1:
Following now @ twitter... thanks
[Samsung Galaxy Nexus] nixholas:
LG. And I'm definitely getting it. Cause I'm an LG Fan :) But of course, that would be at the end of the year. And that after October 11th, I'll be slacking around doing nothing till Next year April xD
[Samsung Galaxy Nexus] OU']['lander:
I think it will be worth to follow you Amp ;)

'][' Maguro powered by Liquid Smooth 2.8 & ASKP r12 ']['
[Samsung Galaxy Nexus] rebretz000:
IMO the GS3 sucked. Constantly rebooted, tons of SOD's. Once in awhile the EIN number would disappear after flashing.

The Droid RAZR HD is nice but not enough development,

Getting the GNEX again and saving money for the Moto X.
[Samsung Galaxy Nexus] justen7723:
I just got a droid RAZR today for free lol. Gonna rock this for a few weeks I think. Very true not nearly as much development but I think it will give me a nice litte break from the gnexus.

One thing I can say, the audio on this thing kills the gnexus. I've never owned a Moto android phone before, I've always heard the hardware is exceptional though.

I've heard a lot of rumors about the moto X. Some claim its going to be the next nexus, others claim its not?????

Sent from my DROID RAZR using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] cmoG530:
Well, since it's free, there's no downsides, but you'll soon see why Nexus devices rock and Motorola....not now. If Google does their job, then yes.
[Samsung Galaxy Nexus] justen7723:
Ya, this guy I work with was like I'm tired of this thing its yours. You can see what I went through to get it working well again here http://xdaforums.com/showthread.php?t=2363792

Won't charge past 80%
Sent from my Razr

I think its pretty funny how easily I got it fixed and now its mine for free lol.

Sent from my DROID RAZR using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] huskerkate:
i haven't owned an LG since i had a flip phone 8 yrs ago. LOL!! i haven't researched it much, cuz we're still months away - but, other than the glass back, i think the N4 has been a pretty good device, right?? how does the LG radios/hardware stack up against Moto? the GNex radios are passable, but certainly not great. i'm willing to sacrifice a little in that department for a Nexus device, tho.

....of course, i'm probably just pi**ing in the wind, since it's unlikely VZW will allow another Nexus device any time soon....
[Samsung Galaxy Nexus] nitsua98:
Or... Maybe it's the other way around. Maybe Google doesn't want their devices on Verizon ;)
[Samsung Galaxy Nexus] nixholas:
Okay. Let's shut all of that.

Bad news.

-AMPlug is not being friendly with MPS (Expected)

I can now confirm that Hotplug is conflicting with MPS even if it's set to 0.

- The kernel is beginning to have SODs when Playing music while asleep. So it's time to chill and stop.

I'm gonna go into fix mode again. So I'll inform you guys againa to see if PSM's good to come.
[Samsung Galaxy Nexus] miqz:
take your time bro..:good:
[Samsung Galaxy Nexus] rebretz000:
The Moto X is definetely not the next Nexus device. It will be a pretty decent device though even though it has "last years specs".

Good RAM, decent chip set with GPU, but only 16 GB storage and no SD slot.

According to the latest leaked benchmark of a ATT branded Moto X, they have it optimized to near perfection with the results they got for only being a Dual Core 1.7

http://www.androidauthority.com/lea...s-to-be-a-dual-core-snapdragon-s4-pro-243648/
[Samsung Galaxy Nexus] nixholas:
Yes! DA AUDIO SYSSSTAMMMM IS FIXED LOL XD

- Shall fix the final bug which is hotplugging (:
[Samsung Galaxy Nexus] nixholas:
GOD. Thanks xD Okay.

Yeah. I was using your RAMDisk (:

Anyways guys, I've rebased somethings. And yeah, I implemented boype's fix (: So it did work well (:
[Samsung Galaxy Nexus] okanb3:
So, where is the new version?
[Samsung Galaxy Nexus] nixholas:
Patience (: I'm still adding in commits. (:
[Samsung Galaxy Nexus] okanb3:
Waiting for it:)
[Samsung Galaxy Nexus] Ashtrix:
Okay, keep up the work going bro !! FYI the GPU governor implementation doesn't work properly so it's removed from r32 of Fancy kernel.

Plus, as this is a Kang please consider Morfic's Git repo also...his work is unremarkable & True Performance :good: !
[Samsung Galaxy Nexus] nixholas:
Here's ASKP's pick plan

1. Fancy

2. FK

3. AirKernel

4. AK

5. Lean

(:

then maybe morfic (:

Also, I'm not removing it, I shall rework the GPU governing code.
[Samsung Galaxy Nexus] jjhrrsn:
I personally wouldn't pick from air. Its my opinion but that was like add in every feature under the sun with no reasoning.
[Samsung Galaxy Nexus] Idrito:
Hi, i'm who made the banner .__.

Look, i don't know from development, i just design, but you can base the kernel (if that is possible) on Franco Kernel because he says everyone can use his kernel as base (if i read correctly).
[Samsung Galaxy Nexus] boype:
You can use all kernels as base, as everything posted here on XDA is open source ;)
[Samsung Galaxy Nexus] nixholas:
Thanks to all the developers of GNex's Kernels.

Build 3 -Upcoming-

* Release as Beta

* AK Cherry Picks

* LeanKernel Cherry Picks

* Patch to 3.0.83

* GPU Governor workaround Attempt #1

* A few minor wakelock fixes

Oh and by the way, after this build, I'll release two kernels subsequently. One with 3.0.83 versions and another with 3.1. Note that 3.1 will not be tested and functions of the phone may not function properly.

The RAMDisk will be reverted to stock RAMDisk.
[Samsung Galaxy Nexus] MBQ_:
^ congrats bro :)
[Samsung Galaxy Nexus] nixholas:
Thanks (: Good luck to BLK too (:

Oh guys, I also added the new hotplug drivers from 3.10 rc5. So yeah (: It's running well (:

Have fun people (:

Linaro 4.8.1 In da house

WLAN FIXED!!!! FTWWWW

And oh yeah, There's a new generic hotplug driver. Note that ASKP is not using OMAP's hotplug anymore.

We are using Linux 3.10's hotplug. In performance wise, the new hotplug allows you to control the cores more easily and improves processing by 23%.

Enjoy~

edit

Build 4 temporarily reverts to the old generic hotplug helper. The 3.10 helper has issues with differentiating deep sleep mode and screen on mode.

Guys, build 4 is for people like me. I know that my OMAP 4 is damaged to a small extent (Let's just say i did some over-overclocking.. xD) yeah. the new hotplug has issues for me and the phone burned up to 80 degrees celsius.
[Samsung Galaxy Nexus] thenemis:
after repo sync, how build it from command line?

or where to set url to local linaro gcc

(export parameter ?)
[Samsung Galaxy Nexus] spupuz:
this morning i tried with B3 and i got to restore from nandroid backup because phone bootlooped just right after "application otpimization" like hell... for now going back to franco.
[Samsung Galaxy Nexus] nixholas:
to set the correct filepath, you need to export CROSS_COMPILE=~/android/kernel/toolchains/arm-2013/bin/arm-none-eabi- . I renamed 4.8.1 to "arm-2013". This allows me to link it easier xD (A few letters is alot to me) And Yes, you need to git clone the linaro 4.8.1 GCC repo. Just google it and you'll find it. It should be a github of a user.

By the way, 4.8.1 is causing stupid problems. I don't know why but I'm going back to compiling with codesourcery
[Samsung Galaxy Nexus] Idrito:
Hi, this kernel got 1.0ghz frequencies?? Franco got it but i want to test this kernel

-=| uXylon + Franco.K |=-
[Samsung Galaxy Nexus] okanb3:
It has these,

http://i.imgur.com/iijMDGN.png
[Samsung Galaxy Nexus] Idrito:
Yup! Gonna flash it

-=| uXylon + Franco.K |=-
[Samsung Galaxy Nexus] nixholas:
Yea it does (:

Okan, i'm sending you a secret build xD

Sorry. Try Build 4. Build 3 has issue as it's Linaro 4.8.1 compiled. Build 4 reverts back to 4.7 with inclusion of new commits and fixes.
[Samsung Galaxy Nexus] okanb3:
Looks like secret version smoother than b4