yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Max94h:
Yes, this kernel scales automatically from 153-384-512 Mhz when needed

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] dr_kalel:
Does R395 support module Touch Control???
[Samsung Galaxy Nexus] Spoderman:
Omg guys, i need help :'(

I installed the rom Dream 5.0.3 ( 4.4.2)

And then tried to install osmosis franco r396.

Looks like i'm screwed now! My device will boot into fastboot, but won't boot onto recovery!

And i don't have a PC with the nexus drivers installed!

What do i do? Help!

Thanks in advance, :/

Edit: I know this isn't the place for help, but lots of people like me, just used the toolkit, and now with kitkat, that the toolkit doesn't help anymore, i'm just wandering around posts and topics, trying to find a good helpful topic for installing drivers, and pushing a stock rom into my device, and work from there.

Sorry.
[Samsung Galaxy Nexus] AndyYan:
Use the r384 module instead of the r391 one. Tried and true.

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] osm0sis:
Google Universal Naked Driver for Android. Then Google efrant's Galaxy Nexus Return to Stock thread. Google Google Google.
[Samsung Galaxy Nexus] mak81:
Hi gys can someone post the color value that use?
[Samsung Galaxy Nexus] Spoderman:
Galaxy Nexus up and running again, thanks Os!

So, FYI guys, don't try either r395 or r396 with 4.4.2 Dream 5.0.3 Rom!

Thanks!
[Samsung Galaxy Nexus] osm0sis:
That pretty much means I'm going to have to just to see what went wrong. ;)
[Samsung Galaxy Nexus] mangusZen:
Hi [MENTION=1143630]osmosis[/MENTION], sorry for the ot here. I really liked your modded twrp , work flawlessy and aromafm is nice and useful.

Could you make a version with the dark colors( black background, white ui)? It matches kitkat and its more stylish :p thank you for you work cheers
[Samsung Galaxy Nexus] osm0sis:
Not my themes. Already done here in the main thread:

http://xdaforums.com/galaxy-nexus/themes-apps/theme-twrp-holofied-black-dark-light-t2405512

Just apply it like you normally would. I prefer the Play due to the color coding, but all his themes are great. :)
[Samsung Galaxy Nexus] mangusZen:
My bad, I had already an old black theme from cody in there and didnt play nicely with the new recovery.

Installed new version linked of the theme and all is again nice and black :p

Tl'dr my fault, I messed up themes..thank you
[Samsung Galaxy Nexus] DroidOnRoids:
No joke. I'm paranoid because I had a dream last night that Franco is done updating the kernel for the GNex. Is this true?! :eek:
[Samsung Galaxy Nexus] osm0sis:
I posted a test r396 kernel compiled by him 2 weeks ago; does it sound true? ;)
[Samsung Galaxy Nexus] bigfnjoe96:
Osmosis, thanks for all the good work. By chance do you know where I could find 395 optimized? Can't find metalsprings original link with the download

Sent from my KitKat Rooted Nexus
[Samsung Galaxy Nexus] osm0sis:
Links were reposted two pages back. :good:
[Samsung Galaxy Nexus] bigfnjoe96:
Muchas gracias

Sent from my KitKat Rooted Nexus
[Samsung Galaxy Nexus] osm0sis:
Worked fine for me, I just had to let it boot up once first before flashing r396-AnyKernel. If I didn't, I got stuck at the boot animation.

Doesn't make sense why that would be, but that's my experience. No issues whatsoever with my recovery though, so I'm not sure what you did there. ;)
[Samsung Galaxy Nexus] hotrodwinston:
Well... It's end of the line for my gnex ride. My wife's refuses to take a charge and when it does it drains super fast and now mine is not holding battery - I got ticked at it and ordered 2 vzw LG g2's which should be here Thursday. I would donate the devices to a dev but vzw requires trade in on the edge program. So thank you [MENTION=3292224]franciscofranco[/MENTION] for all the awesome. And thanks to everyone here for helping me out when I needed and for putting up with me being a noob sometimes.
[Samsung Galaxy Nexus] :
Get a new battery? :p

Sent from my sushi grade tuna
[Samsung Galaxy Nexus] dehein:
How about the Kernel 3.4 thread. Some devs needed a Gnex there.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] sagara.sandaru:
Yea.. That would be great [MENTION=1937895]hotrodwinston[/MENTION] !

Just mention about this here http://xdaforums.com/showthread.php?t=2071021
[Samsung Galaxy Nexus] ribelle85:
The 95% max charge options is avaible only when the phone is on..?
[Samsung Galaxy Nexus] ribelle85:
No One?
[Samsung Galaxy Nexus] DR3W5K1:
Yes you are correct.
[Samsung Galaxy Nexus] namtombout:
Liquid smooth 04/03 and metalspring's r395
[Samsung Galaxy Nexus] BurningKoala:
I'm looking for this kernel but for android 4.1...any link? :confused:
[Samsung Galaxy Nexus] osm0sis:
I hunted them down out of the kindness of my heart not too long ago. Please search back a bit. Shouldn't be hard to find. ;)
[Samsung Galaxy Nexus] BurningKoala:
I've serched on google but I've only found dead links...I'm looking for the milestone 6, btw I'll try again
[Samsung Galaxy Nexus] osm0sis:
Search this thread, narrow it to posts by me.
[Samsung Galaxy Nexus] BurningKoala:
Found, thank you!

http://xdaforums.com/showpost.php?p=50580080&postcount=44681
[Samsung Galaxy Nexus] fleckdalm:
My wifi Hotspot doesn't work with this rom, it hangs on activating! Any solution?

Thanks,

Fleckdalm
[Samsung Galaxy Nexus] AndyYan:
More info needed - which ROM / what version of it are you using, plus a logcat is usually necessary.

And Franco is not a ROM, it's a kernel!

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] fleckdalm:
I'm using cm11 with the newest kernel version from the op.

Here is a logcat, I hope this helps! https://www.dropbox.com/s/1muwz5iddhdcrwx/2014-04-11-11-39-59.txt

Sorry, I meant kernel, this was only a typo!
[Samsung Galaxy Nexus] r00t4rd3d:
How do I change my boot animation with this kernel? Putting a bootanimation.zip in /data/local has no effect.
[Samsung Galaxy Nexus] osm0sis:
Did you use another kernel first? Specifically one that uses the Linux 3.4 Wi-Fi drivers? They're known to break AP, and kernel devs work around it by overwriting the ROM file /system/bin/hostapd - so coming to f.K you might have the hostapd mismatch in the opposite direction.

See if there's a backup of the original in /system/bin or dirty flash your ROM.

That's a ROM thing, not kernel. /data/local is where it should work though. Ask in your ROM thread. :good:
[Samsung Galaxy Nexus] fleckdalm:
Yes, I was on, DirtyV first, so this will most probably be the issue, thanks! I will try reflashing cm11 and see if it works then...
[Samsung Galaxy Nexus] osm0sis:
I wrote the ramdisk in DirtyV to actually clean up after itself if someone changes kernels, so it should be okay. But yeah, definitely give reflashing a try. :good:
[Samsung Galaxy Nexus] fleckdalm:
Thanks, reflashing worked! :)

So there must be a bug in the cleanup process...
[Samsung Galaxy Nexus] kansasboy001:
Does this kernel support the samgsung extended battery, because battery widget is reporting the max capacity as 1750 mah, not 2100mah
[Samsung Galaxy Nexus] pkgnex:
That's not a kernel-controlled item. I believe it is a framework modification required in your ROM. You should contact your ROM developer to see if they can point you to a mod for making the battery life data line up with your extended battery.
[Samsung Galaxy Nexus] ashclepdia:
To fully replace a ROMs boot animation, the file is located in /system/media.

You CAN also use data local, but I have always just replaced the one in /system/media. Be sure to set its permissions to rw-r--r--

But I think if you have one in data local it will override the system one
[Samsung Galaxy Nexus] andronexus:
Finally, I think franco will be updating the kernel in the coming days!! :highfive: :fingers-crossed:
[Samsung Galaxy Nexus] pkgnex:
Wrong thread.
[Samsung Galaxy Nexus] sunscape:
Right thread.
[Samsung Galaxy Nexus] andronexus:
Guess not everyone follows him on G+ :P :D
[Samsung Galaxy Nexus] Godra:
Can you post a link? I can't find it
[Samsung Galaxy Nexus] pkgnex:
farnco? ;)

(my humor was apparently a little too dry)
[Samsung Galaxy Nexus] mick.li:
"Pushed r47 for the Nexus 5! Will be focusing on my other devices through the next days, stay tuned!"

Published 3 days ago.

Mick
[Samsung Galaxy Nexus] andronexus:
Hahahaha xD wow... (better late that never). Kinda actually thought of it after i posted the reply :P but was too proud to admit it :P (MUUUWAAHAHAHAHAHHAHA *evil laugh*)

---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------

There you go! :)
[Samsung Galaxy Nexus] franciscofranco:
Pushed r396!
[Samsung Galaxy Nexus] osm0sis:
:laugh:

Rock solid as usual, sir! :D

I just uploaded a new updated version of my Kernel Emergency Reset script zip: http://v.ht/KEmR

Added Synapse support, updated f.Ku support for the recent newer versions and updated Performance Control support since that team's been doing great work to improve it. :)
[Samsung Galaxy Nexus] GamaX320:
This script work on every kernel ?
[Samsung Galaxy Nexus] osm0sis:
Every kernel, every (popular) tweaking app, and every device. Spread the word. :)
[Samsung Galaxy Nexus] ahmadairfan:
Did I missed something or RAM overclock was there in osm0sis' version early? (I don't see a performance improvements, though?)

Have no idea, going to flash, maybe tomorrow lol just a few final tests to pass.

Thanks fransisco and os ! :):highfive:
[Samsung Galaxy Nexus] osm0sis:
The RAM OC was the only change in the test r396 version. This is the final and has more changes. Check the Github. :)
[Samsung Galaxy Nexus] pianistaPL:
Any chance for vibration strange control? :(

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] ahmadairfan:
Same here, I personally think it may save battery even just a litle bit lol. :laugh:

Btw, how do you guys pick up between row and noop?

I personally take noop but maybe row is better since its been default in FK?
[Samsung Galaxy Nexus] metalspring:
Btw, [MENTION=3292224]franciscofranco[/MENTION] I saw you added Joe's RCU in source but never enabled it in the defconfig? (at least the defconfig on github anyway). Was that intentional or did you just forget to enable it in the defconfig?
[Samsung Galaxy Nexus] morfances:
Someone has already tried if it works the touch control?

Always module r384?
[Samsung Galaxy Nexus] Culex316:
Just install the latest touch control and use Franco kernel r395 module.

It works for me.
[Samsung Galaxy Nexus] creeve4:
Has anyone else who is running CM11 flashed the new r396? I've re-downloaded twice. Every time I flash the kernel, some weird sh*t happens to a few of my apps:

When I attempt to open any of these apps, they FC. I've even tried a clean install of CM11, let it boot, then went back to recovery and flashed r396, same thing.

Any ideas? All previous releases worked fine. This is something I've never seen before.
[Samsung Galaxy Nexus] Culex316:
Are you running a nightly or an M release? I had to go back to CM 11 M5 due to the system ui force closing.
[Samsung Galaxy Nexus] creeve4:
I'm running a nightly, 2014-04-30
[Samsung Galaxy Nexus] fleckdalm:
I have the same issue running the newest Vanir nightly!
[Samsung Galaxy Nexus] pianistaPL:
No problems with new AOSPAL (based on PA 4.3 BETA2)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] osm0sis:
Happened to me too on Carbon. Flashing forced a Dalvik cache rebuild for no apparent reason and then I noticed some icons were generic in the app drawer.

[MENTION=3292224]franciscofranco[/MENTION] It appears to be all paid apps get screwed and need to be uninstalled and reinstalled. If I had to guess I'd say it's one of the SELinux commits.

[MENTION=4328678]metalspring[/MENTION] any chance you could reproduce the issue and/or test compile for solutions?
[Samsung Galaxy Nexus] pkgnex:
This DID NOT happen to me. I'm running ShinyROM 4.4.2 (3-9 build), and I wiped both cache and dalvik cache in CWM recovery (not because it's needed, just because I hadn't done it in a long time) before flashing the zip (not .img).

I'm only posting this in hopes that info helps nail down the problem and get it fixed for others.
[Samsung Galaxy Nexus] osm0sis:
Weird. Maybe the SELinux commits made a ROM incompatibility from passive vs. enforcing or something?
[Samsung Galaxy Nexus] bsmitty83:
Easy to check , in terminal type getenforce to show selinux state (as root )
[Samsung Galaxy Nexus] osm0sis:
f.K leaves it enforced if I recall correctly. I force DirtyV to enforced at boot and have never had any issues, though I'm a little leery of your next nightly since you added those commits too. :p
[Samsung Galaxy Nexus] AutomaticFailure27:
I'm with pk, have no issues what so ever with r396. I'm on aospa 3.99.
[Samsung Galaxy Nexus] bsmitty83:
They'll be going byebye .....
[Samsung Galaxy Nexus] pkgnex:
FWIW, for me, su (enter), getenforce (enter), returns "Enforcing".
[Samsung Galaxy Nexus] pvkiniyan95:
link for Franco Kernel r396 optimized by [MENTION=4328678]metalspring[/MENTION] :highfive: [MENTION=4496256]pianistaPL[/MENTION], [MENTION=4328678]metalspring[/MENTION] please
[Samsung Galaxy Nexus] pianistaPL:
I will not give public link until metalspring will agree ;)

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] pvkiniyan95:
chk ur inbox :D
[Samsung Galaxy Nexus] osm0sis:
After I'm done weeding out the AdAway entry keeping me from streaming hockey on my set-top box (;)), I'll tackle some test builds metal sent me with those SELinux commits reverted individually.

Once we figure it out I'll inform Francisco and he can push a fix. No point in my mind of going public with metal's 3 optimized builds until we get that sorted though; 1 broken build is better than 4. :p
[Samsung Galaxy Nexus] bsmitty83:
That would be priority no 1 for me too lol , gotta see that habs game tonight [emoji106]
[Samsung Galaxy Nexus] osm0sis:
Haha exactly!

From 30947 entries I found the 2 that were causing problems and added them to the AdAway Whitelist and Wiki. :p
[Samsung Galaxy Nexus] ribelle85:
Does franco kernel support otg?
[Samsung Galaxy Nexus] osm0sis:
Should work. Yup! :)
[Samsung Galaxy Nexus] ad astra:
works flawlessly on CM11 snapM6.

bullet fast :D

the franco kernel app crashed on me (have the paid version). it wouldn't start no matter what. uninstall; reinstall; did the trick.
[Samsung Galaxy Nexus] skizofrenic:
With last kernel seems(to me) that input boost freq is not working anymore.

I Touch screen but freq remains low
[Samsung Galaxy Nexus] pianistaPL:
SystemUI FC after boot on latest CM-Remix.
[Samsung Galaxy Nexus] skizofrenic:
Confirm

Reflashed r395 and touchboost works.

Re-reflashed after re-download r396 and again not working
[Samsung Galaxy Nexus] jhonnyx:
Touchboost has been re-worked and boostpulse has been removed

https://github.com/franciscofranco/Tuna_JB_pre1/commits/nightlies-4.3

cpufreq: interactive: add changes to allow for input boost events. …

e6e17b79b2 Browse code

franciscofranco authored 3 days ago

Francisco Franco

input: touchboost: add the same generic input time driver from my oth… …

1112d124d8 Browse code

franciscofranco authored 3 days ago

Francisco Franco

input: remove old boostpulse fd write crap. …

5c5c0c8f1c Browse code

franciscofranco authored 3 days ago
[Samsung Galaxy Nexus] osm0sis:
Good/bad news.. None of the 3 test builds from [MENTION=4328678]metalspring[/MENTION] fix the issue... Even more, I decided to try going back to r395 and it still happened...

So, basically, it's not anything wrong with franco.Kernel at all, it's either ROM or some effect from the kernel ramdisk you're coming from (eg. the SELinux context files or binaries included).

This explains why it only happened for some people. Can those who have the issue and those who do not please report their ROM and prior kernel so we can try and figure this out?

Issue present:

[MENTION=4544860]osm0sis[/MENTION]: Carbon nightly 2014-05-03 - DirtyV-SR 5.3.14.

[MENTION=3444353]creeve4[/MENTION]: CM11 nightly 2014-04-30 - kernel?

[MENTION=3309440]fleckdalm[/MENTION]: Vanir nightly 2014-05-04 - kernel?

[MENTION=4953913]ad astra[/MENTION]: CM11 M6 - kernel?

No issue:

[MENTION=4496256]pianistaPL[/MENTION]: AOSPAL 4.3 BETA2 - kernel?

[MENTION=4793042]pkgnex[/MENTION]: Shiny 2014-03-09 - kernel?

[MENTION=2988507]AutomaticFailure27[/MENTION]: AOSPA 3.99 - kernel?

---------- Post added at 01:11 AM ---------- Previous post was at 12:32 AM ----------

Since we've determined it's not actually a f.K issue... ;)

That third one pretty much sounds like we could call it "Dirty f.K"! :laugh:
[Samsung Galaxy Nexus] pianistaPL:
[MENTION=4544860]osm0sis[/MENTION] I have only bug with SystemUI FC on CM based ROMs. I don't have problems with launching apps because i don't use any paid apps ATM. Sorry, i didn't know that problem is only with paid apps :) But i use third version of metalsprings kernel and it's extremaly flying. I believe this is the best kernel i have ever used.
[Samsung Galaxy Nexus] pkgnex:
My previous kernel was essentially the r396 test version you sent me the boot.img of. To be specific, I was actually running the r396 test version boot.img file you sent me, but I had swapped it into the r395 flashable zip file for 4.4 (replaced the boot.img in r395 with the one you sent me, then flashed that zip).
[Samsung Galaxy Nexus] creeve4:
My previous kernel was r396-AnyKernel (the test version of r396 from a month or so ago).
[Samsung Galaxy Nexus] AutomaticFailure27:
[MENTION=4544860]osm0sis[/MENTION]

Running r396 along with AOSPAL 3.99 RC 2.
[Samsung Galaxy Nexus] redj12:
Metalsprings kernel is compatible with 4.3 ? I am on SlimBean and the phone can't overcome the Google logo.

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] swarlesbarkely:
Cm remix (at least for toro) isn't compatible with kernels that use a cm ramdisk which the post says is anything that uses a boot.img
[Samsung Galaxy Nexus] pkgnex:
Good thing I'm not using CM Remix, then!

(I'm using Shiny ROM 4.4 and have had no issues with any of the Franco kernels from 395 to present).
[Samsung Galaxy Nexus] pianistaPL:
No, it doesn't because this is just franco r396, only optimized
[Samsung Galaxy Nexus] pkgnex:
-

I second this - there does not appear to be any touch boost on r396, or at least the timing/implementation of it has been changed such that it is almost always circumvented by the other interactive governor parameters (thus making it somewhat useless).

I set the boost input freq to 729, hispeed freq to 1036, and max freq to 1305 and on r396 the 729 slot is almost never used. While watching a cpu monitor, touching or swiping the screen either does not cause the freq to change from min., or it goes to hispeed freq (or above), depending on the resultant action of the touch / swipe.

On r395 with the same settings, 729 is used heavily and touch / swipe of screen usually causes freq. to go to 729 (at least initially before going back down or going even higher).

That said, overall device performance doesn't seem perceptibly different to me between r395 and r396.
[Samsung Galaxy Nexus] osm0sis:
So both those who did and didn't see the problem were running r396-test which certainly rules out the zImage, though for most it was AnyKernel so there would be a switch from the ramdisk files in use. That also still leaves ROM. Obvious pattern I see in the reports is AOSP is fine and those using CM's device trees have problems.

I'll downgrade Carbon today to see if I can figure out when it started.
[Samsung Galaxy Nexus] ad astra:
gladly: stock CM11 M6 is: 3.0.101-cyanogenmod-gbd85bbf

(build03@cyanogenmod #1

Sun May 4 16:57:41 PDT 2014)

there is a great deal of bugs in M6 but i haven't noticed any of them, even with FK r396.

hope this helps :good:
[Samsung Galaxy Nexus] aliesz:
Where is the link of optimized r396 kernel?
[Samsung Galaxy Nexus] osm0sis:
Read back a page next time please.
[Samsung Galaxy Nexus] osm0sis:
Downgraded back to 04-01 and it still presented with the issue, so next I'll explore whether it's something to do with newer CM-based ramdisks.
[Samsung Galaxy Nexus] nailz420:
Phone doesn't deep sleep on 3g, only on wifi. Sleeps fine on 395. Rom PA 4.3 beta 3.
[Samsung Galaxy Nexus] Culex316:
Install better battery stats and see what is causing the wakelock.
[Samsung Galaxy Nexus] Loureiro:
Did several wipes and mine doesn't sleep either on omni official builds
[Samsung Galaxy Nexus] osm0sis:
I can confirm the paid app breakage issue is due to CM's newer files in the ramdisk in use prior to flashing f.K. I rolled back my DirtyV ramdisk to my pre-4.20.14 one and flashing it had the exact same effect. So basically, once you go new you can't go back without this issue.

So, the question is, do we:

a) rebase the f.K ramdisk with the newer files?

b) blame CM and call it a regular week. ;)
[Samsung Galaxy Nexus] nailz420:
I flashed r396 back and it started sleeping. I am not sure why.
[Samsung Galaxy Nexus] andronexus:
Another awesome update! I always clear the cache and dalvik before I flash anything as well as after. Smooth and fast as always. Might be the ROM (since I updated it along with the kernel) or maybe the kernel but my boot time is faster since r396. No problems with any apps and also working fine with the f.K updater.
[Samsung Galaxy Nexus] osm0sis:
Think I'm going to have to go with (a) here; there's no downside to updating to the new SELinux files, but if you downgrade again somehow then you see the paid app issue.

Since all CM device tree based ROMs' included kernels likely use the updated versions, it's more likely than not that someone might boot them at least once before flashing a custom kernel like f.K, and we don't want people's paid apps to get borked when that happens, even if it is CM's failure to make things cross-compatible again which is really at fault.

Sigh.. I'll look into doing it later tomorrow and email it to [MENTION=3292224]franciscofranco[/MENTION]. I'll look into the reports of the new input_boost being broken too once I get the new ramdisk working.
[Samsung Galaxy Nexus] n1kolaa:
Also Sound High Performance missing script in ramdisk :)
[Samsung Galaxy Nexus] osm0sis:
That has nothing to do with scripts or ramdisks. It was buggy as hell so Francisco removed it and rewrote the headphone boost from scratch.
[Samsung Galaxy Nexus] n1kolaa:
i tipe other spripts on terminal but it says cant find,what scripts work?

i edit it manualy with file menager.
[Samsung Galaxy Nexus] osm0sis:
No idea what you're asking. franco.Kernel updater, Performance Control or Trickster will show you what features are present in f.K.
[Samsung Galaxy Nexus] osm0sis:
Uploaded a fixed version with a rebased ramdisk to resolve the paid apps issue caused by flashing AOSP's ramdisk SELinux files over a CM-based ROM kernel.

I'm still looking into the input boost stuff but it seems to jump to 1.0GHz okay for me.. then again if you look at Francisco's flo Github commits from yesterday you can see he's having troubles with the global boost driver everywhere.

franco.Kernel-tuna-nightly-r396-KK-fixed:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod/

Hopefully [MENTION=4328678]metalspring[/MENTION] can repackage his optimized versions and post them here for us as well. :)
[Samsung Galaxy Nexus] garuhhh:
input boost seems to be working on mine as well, r396.
[Samsung Galaxy Nexus] creeve4:
Input boost is work for me as well with r396
[Samsung Galaxy Nexus] pkgnex:
How are you all verifying the input boost performance?

I'm just looking at the CPU monitor in trickster, and it either does nothing (touch) or jumps to hispeed_freq (swipe).
[Samsung Galaxy Nexus] creeve4:
I use CPU Spy+, since TricksterMod seems to have a sampling rate that is too low.
[Samsung Galaxy Nexus] osm0sis:
I was using the monitor in f.Ku. hispeed is 700 MHz and input boost is 1.0 GHz, and it definitely seems to jump to 1.0 GHz more than 700 MHz. :)