yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] llohcyoing:
hi Francisco..i would to d/l your app but market return to me that my device isn't compatible...i've read to cancel my carrier but..how can i cancel my carrier? thanks in advance...

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] jhericurls:
Have you tried Market Enabler?

https://market.android.com/details?...?t=W251bGwsMSwxLDEsImNvbS5ub3RlbmtpbmcubWYiXQ..
[Samsung Galaxy Nexus] llohcyoing:
dont work with market enabler...

im on CM9 with franxo.kernel nightly8

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] Shetlander:
I know that but I was curious to know if there had been any further developments. I know they where having trouble to get the DDC? to lock at a certain frequency but that was some weeks ago.
[Samsung Galaxy Nexus] franciscofranco:
Thats a known problem of some roms, must be because of the build.prop. Nothing I can do.

No, and I already added 1,35ghz without wanting it, I don't care to much another 50mhz, this is a dual core god damnit, its not 50mhz thats gonna do any bloody difference....
[Samsung Galaxy Nexus] Bram77:
I am. Works perfectly. I'm using #8.
[Samsung Galaxy Nexus] llohcyoing:
ok...thank you and sorry for keyboard error (franxo...)

i will try with another rom next days..

amazing kernel Francisco... ;)

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Nice!! Would it be possible to throw in options for mofics Contrast and Content Adaptive Brightness? That would be truly fantastic. Thanks so much!:D
[Samsung Galaxy Nexus] GNEXc:
Thanks for the reply Franco. Looking forward to your update.
[Samsung Galaxy Nexus] metalspring:
how about being able to have custom voltages set on boot...i know its not recommended but you could throw in a big warning in a "apply voltages at boot" option
[Samsung Galaxy Nexus] franciscofranco:
Morfics contrast option will be there. Content Adaptive Brightness? What in the blazes is that?
[Samsung Galaxy Nexus] franciscofranco:
I'm not flexible on that sorry. I've had my share of troubles with people applying and then not booting. I'm already getting 1 star ratings because people say "app no vork for jelly beans, fix nao" (and JB is isn't out yet), now imagine if one applies voltage on boot and it doesn't boot up. It's a no go, sorry.
[Samsung Galaxy Nexus] superbobup:
Does manual UV work properly in your ICS kernel? I can set the 384 slot to 0mv and it still works :p
[Samsung Galaxy Nexus] franciscofranco:
Have you disabled SR? One of the OMAP patches that were merged for JB prevent any type of UV with SR enabled as far as I can understand.
[Samsung Galaxy Nexus] superbobup:
Yup, SR is disabled for the MPU (the only one I tried to UV). It didn't seem to work pre-JB patches (r196) or post-JB patches (r200)

When I turn SR on, it instant crashes and needs a battery pull so I'm quite confused..:cyclops:
[Samsung Galaxy Nexus] franciscofranco:
Now this is a good score.
[Samsung Galaxy Nexus] chesirecat21:
hello guys, greetings from indonesia

let's get straight to the point. I'm running JellyBean ROM by bigxie and having no problem at first. after that, i changed the kernel with franco's r210 and having a problem with FIFA 12 game. after reading the instruction in the thread, i push the sdcard bin provided by the thread, and i can't see the contents of the sd card. so i'm following the other instruction in the thread: "type this on the terminal: chmod 0755 /system/bin/sdcard﻿ and reboot" but it's not working, the terminal says something like "operation not permitted" and then i tried to flash the stock kernel. unfortunately, nothing fixed. i still can't see the sd card contents. so i'm going into the recovery, wiping all the data, cache, dalvik cache, and fix permissions and then re-flash the JellyBean ROM. and this is when the problem happens, after flashing the ROM, and reboot the system, I'm stuck in the Google Logo. i can't do anything except pull out the battery. then i flashed ICS ROM (rascream one) and finally i made it into the system. and after that, i go back into the recovery, and re-flash the JB ROM, and the problem still happen (stuck in the Google Logo). and then i tried to flash another JB ROM (JellyBelly) but it's also not working. anybody can help me with this? should i wait for another JB release?

thanks for reading my post
[Samsung Galaxy Nexus] sotoskawasaki:
You need to get admin provileges first. type in the terminal "su" (without the quotes), press enter. Then enter the command chmod 0755 /system/bin/sdcard . That is why you get the "operation not permitted" error. Now as to your other problem I cant think of anything...
[Samsung Galaxy Nexus] chesirecat21:
thanks for answering my question, i managed to solve the problem by formatting the system in recovery= mount and storage, format system

i will try to flash this kernel later. thanks :D
[Samsung Galaxy Nexus] The Gingerbread Man:
The content adaptive brightness basicly auto dims down the brightness of the screen according to the level if whites on screen. If there's lots if white ie web browsing the screen brightness is lowered slightly to save battery. Supercurio has this feature in his voodoo display preview app.

Also about this custom voltage on boot I have an idea to save you hassle of dealing with idiots and please the rest of us;

So you have a button to set the voltage on boot, pressing the button gives a warning and then proceeds into downloading a script in cwm zip to then apply safe (stock voltages). So if you get boot loop then just flash the file to return to safe voltages and phone boots up. Set CPU had / has something similar and its a pretty good idea.

Check here http://setcpu.com/documentation_mobile.html under safe mode. Here is copy paste;

If you're trying out new CPU speeds on an overclocked kernel or trying out new voltage settings, it's always a good idea to uncheck the Set on Boot checkboxes in the corresponding menus before doing so. This way, your phone will not boot loop if you get stuck on an unstable CPU frequency or voltage. To be safe, you can extract a Safe Mode update.zip to your SD card in the Main tab. Access the menu here, and press Safe Mode Instructions to do this. Flash the setcpu_safemode_toggle.zip file in recovery mode as a normal update.zip to recover if SetCPU causes your device to boot loop. Flash the zip again to toggle safe mode off. Alternatively, you can make a file called setcpu_safemode with no extension and place it on your SD card or internal storage, /data, or /data/local to active safe mode.

If you didn't get a chance to extract the safe mode zip, download the safe mode update.zip here. Flash it in recovery mode just like any other update.zip.

Here is the script http://db.tt/mFuZiIQN to give an idea of the coding required

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Brilliant! Content Adaptive Brightness adjusts the brightness depending on what's showing on the screen (whites+text). Sounds like a great idea, in theory. In reality, disabling it helps a lot with the "graininess" people get on white backgrounds at low brightnesses.

It's controlled with this:

echo 0 > /sys/class/backlight/s6e8aa0/acl_set

0-off 1-on.

An option in the Kernel updater display settings would be stellar though! :D

Thanks for your consideration and keep up the great work.
[Samsung Galaxy Nexus] franciscofranco:
Its an idea! I'll think about it for v5.6, v5.5 is closed soon.

I didn't know that!! I'll add it now.
[Samsung Galaxy Nexus] The Gingerbread Man:
Edited my post further take a look

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yep, that seems like a good idea, will add it on v5.6.
[Samsung Galaxy Nexus] DaLoona:
The link is in the OP/first page of this thread, just look under nightlies link at bottom of OP.
[Samsung Galaxy Nexus] The Gingerbread Man:
Would only work if you force the download when the button is pressed though. A warning and simple instructions to cover your back completely as I'm sure people will still try and complain and then you can point and laugh at them ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] arvylas:
Even though everything is pretty fast scrolling is a bit lagy with r210.with stock is much better...
[Samsung Galaxy Nexus] DaLoona:
Franco, bought you a piece of pie and a cup of coffee. Thanks for your hard work.
[Samsung Galaxy Nexus] franciscofranco:
5.5

* Built with the newest SDK but still retro-compatible with ICS devices

* Re-coded how the preferences get saved into the SharedPreferences interface as an effort to have settings persist on reboot

* Add Trinity Contrast option

* Add Content Adaptive brightness option

* Add fsync() toggle

* Add a new first page with the app version, Galaxy Nexus and One X support threads

One X:

* Fix attempt for CPU settings to persist on reboot, its not easy to counter Tegra3 control over the frequencies...

The new version should be up as soon as Google pushes it to Google Play.

AndroidPit users will have the app updated to the latest version by the end of the day.
[Samsung Galaxy Nexus] splus:
Supercurio's Voodoo display app for turning off the adaptive brightness is probably the single most useful mod to get the better display quality and white whites on Nexus' screen!

http://xdaforums.com/showpost.php?p=24783215&postcount=110

When you turn off the adaptive brightness option (Nexus comes with this option turned on) the whites become fully white (not grayed out as they are normally) and entire display looks much clearer and cleaner. The Nexus' display simply looks MUCH better with adaptive brightness option turned off, almost like a new display... Just go into a browser straight after turning this option off and compare it with before.

I've been using this amazing little app since April and the major hassle with it is that the adaptive brightness option doesn't stick after reboot, you have to turn it off after every reboot.

Franco, if you could add this option in your app and make it stick on boot, you'd definitely make many Nexus owners very happy!
[Samsung Galaxy Nexus] sago62:
I don't see Franco.apk upgrade in market...
[Samsung Galaxy Nexus] jnr21:
"The new version should be up as soon as Google pushes it to Google Play."
[Samsung Galaxy Nexus] metalspring:
Read the bottom part again...
[Samsung Galaxy Nexus] zephiK:
It says,

The new version should be up as soon as Google pushes it to Google Play.

AndroidPit users will have the app updated to the latest version by the end of the day.
[Samsung Galaxy Nexus] franciscofranco:
Ups I think I did it backwards... Will recheck when I get home.
[Samsung Galaxy Nexus] ragnarokx:
Still getting minor launcher stutter on r210 JB compared to stock. But thanks for the amazing work so far Franco.
[Samsung Galaxy Nexus] franciscofranco:
Change interactive hi_speed tunable to your max frequency value. Done.
[Samsung Galaxy Nexus] Enhanced:
I've had a little higher idle drain than stock with r210 when I did my overnight test.

On WiFi, slept for 7 hours - battery drained 5%. With the same test on stock, I only dropped 2%.

I'll test it again when I sleep tonight though as this is only one time.
[Samsung Galaxy Nexus] ragnarokx:
I try and follow your thread closely, but it seems I missed this. Thank you for answering my question - the fix works like a charm.
[Samsung Galaxy Nexus] mullemulle86:
if i change this my phone only uses min and max value. if i set this value to 700000 it uses all frequencies between to. isnt that the better solution or am i wrong?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] sago62:
Sorry....

in a hurry I did not read well ..
[Samsung Galaxy Nexus] zephiK:
It's ok... the 5.5 update is live on Google Play Store now! downloading :)
[Samsung Galaxy Nexus] Tito2007:
If your frequency is 1.2 you need to set it at 1200000 and you will use all frequencies.
[Samsung Galaxy Nexus] gdmlaz:
I don't see the 5.5 still 5.4
[Samsung Galaxy Nexus] The Gingerbread Man:
Same, give it time it will come :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gdmlaz:
will do :P
[Samsung Galaxy Nexus] jnr21:
Max freq still goes itself to 1,2ghz sometimes.
[Samsung Galaxy Nexus] renaud:
Franco, as expected setting freqs as 0444 in initramfs solves the frequencies problems on jb. But if an app sets frequencies back to 0666, like antutu CPU master pro does, of course bug comes back.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zephiK:
I had the same problem. Try this,

Uninstall Franco Kernel

Go to https://play.google.com/store/apps/...kernel&feature=nav_result#?t=W251bGwsMSwyLDNd

Install from website.

You will know when the app opens, it'll appear with a app changelog and say 5.5.

edit:

^^
[Samsung Galaxy Nexus] dwang:
Yeah I've noticed this as well. Strange
[Samsung Galaxy Nexus] franciscofranco:
Happens with all the JB kernels. I think they have a daemon somewhere or just something to lock the frequency. Since its a preview they must be locking it for safety testing. It's just a guess though.
[Samsung Galaxy Nexus] renaud:
It does not happen anymore with my jb kernel.

Frequency goes back to 1200mhz max as soon as you lock/unlock the screen. It uses root permissions and is set from the os. Read my former post. It is probably a battery saving feature.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lovelymobile:
+1
[Samsung Galaxy Nexus] KingDavid63:
Gotta turn smart reflex off

Sent from my Asus TF201 Prime Virtuous Loaded Quad Core +1 Beast!
[Samsung Galaxy Nexus] saar73:
Hi all,

just purchase the kernel updater from the market, but i cant find the JB kernel (r210). im i missing something?
[Samsung Galaxy Nexus] splus:
Franco, I just did some tests and the Content adaptive brightness option in the new app changes the adaptive brightness properly. When it's turned off the display is brighter and clearer, especially when there's more whites on the screen.

However, the option doesn't stick on boot. The check box in the app stays the same after reboot, but the adaptive brightness itself is reset back to on, regardless of the value in the app.

I tried checking it with Supercurio's app and whenever I change the option in Franco app the Supercurio's app shows that the option has changed. But when I change the adaptive brightness option in Supercurio's app then the check box option in Franco app doesn't change (shows a wrong value).
[Samsung Galaxy Nexus] saintsmmx:
JB kernel are still experimental so you can't download them through the app, but you can find them on the first post of this thread
[Samsung Galaxy Nexus] bboran:
what value do you suggest on Trinity Contrast option? Thanks.
[Samsung Galaxy Nexus] franciscofranco:
Yep makes sense. I'll probably just do a little trick on the app changing permissions to 0666, change the frequencies and then back to 0444, I had to do that for the One X otherwise the OS would change them back.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the testing. I had already send the update to Google when I realized I built the adaptive **** incorrectly.

Supercurio's app is probably reading from the file, but I'm reading it from the SharedPreferences interface, thats how my app is built upon.
[Samsung Galaxy Nexus] jnr21:
Nice. It's very annoying to use stock cpu freqs with oc-capable kernel :P
[Samsung Galaxy Nexus] stick1300:
Will the Content Adaptive setting work on older kernels?

EDIT: Answered my own question. Works great!
[Samsung Galaxy Nexus] spaceman860:
Its still fast as **** with stock freqs

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] mullemulle86:
if i set it to 1200 cpu spy says that my phone only uses 300 and 1200.

if i dont change anything the phone uses all freqs.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] zephiK:
what governor are you using.
[Samsung Galaxy Nexus] mullemulle86:
interactive

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] MS.:
Yay, finally JB kernel feels stable enough to be used daily. Thanks Franco.
[Samsung Galaxy Nexus] Kapetan:
Any new ics nightly which in terms of battery usage performs better them r181? Sorru for not reading all those pages, just curious if someone else knows that ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
196 or 200

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tbbo514:
How does the jb kernel for 4.1 run :) good reviews ?
[Samsung Galaxy Nexus] franciscofranco:
It runs with 4 legs if thats what you're asking ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Damn just damn my screen looks so good right now. Credits to Morfic for his contrast and many thanks Franco for a nice easy toggle for us!

I got 135, 135, 200, c.a.b on, contrast -10.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ArmanUV:
I think the stock JB kernel performs well. I can't really tell the difference between stock and JB nightlies in terms of speed. Ofcourse stock doesn't come will all the goodies like fast charge and colour controls.
[Samsung Galaxy Nexus] osm0sis:
It's your typical boolean, 0=off, 1=on. We want to be able to disable it (0) to improve the graininess issues. :D

Thanks a billion for adding it. I finally don't have buyer's remorse for my Nexus screen thanks to you!
[Samsung Galaxy Nexus] MistaBishi:
Those options look great! Best I've seen this screen look for a long time!
[Samsung Galaxy Nexus] msedek:
Any news from franko on when are we gonna be able to flash jb kernels with francos app? I hate coming here to get the latest and go cwm to flash it
[Samsung Galaxy Nexus] sway40:
Agree, very good numbers for the settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] giugiu:
I set omap4 @ 1.6 + your settings - looks very good.

Thanks a lot!

Ciao

Giulio

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
Don't thank me, thank morfic and franco my settings are loosely based on the famous trinity colours (135, 135, 214) i just found it a little too blue and the contrast at -10 seems good but not spend a huge amount of time finding what looks absolutely the best.

Any way glad you like it :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joeyfong:
When will have updated app at androidpit??
[Samsung Galaxy Nexus] mingkee:
The updated version which posted today still can't keep color settings; however, I use a previous version which dated "5 June" worked (can change the color to preset value few seconds after home screen shown).

Version: 4.9.2
[Samsung Galaxy Nexus] franciscofranco:
Later at night.

It works for me.
[Samsung Galaxy Nexus] spaceman860:
Reporting none of the color settings stay for me after reboot or CPU freqs or gov controls

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] mingkee:
This is interesting why 4.9.2 works but 5.5.0 does not for me with JB.

Kernel #210

US version hardware (GSM)

---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------

Actually, I made a script that can activate custom color settings with a touch (executable with prompt). Now I have to find out how can it be executed automatically upon reboot (stock JB ROM).
[Samsung Galaxy Nexus] metalspring:
grab script manager in the market, it should be able to run scripts at boot
[Samsung Galaxy Nexus] chocoyo00:
How about Gamma? Are you modifying that at all or just 0's?
[Samsung Galaxy Nexus] momomok:
mind explaining what is "Content adaptive brightness"?

like those dynamic contrast thing on PC monitor?

Brighter when more white, darker when lots of black are shown?
[Samsung Galaxy Nexus] syncopy:
Here:

http://xdaforums.com/showpost.php?p=28101540&postcount=21407

http://xdaforums.com/showpost.php?p=28103944&postcount=21417
[Samsung Galaxy Nexus] dracon6ai:
So in a nutshell content adaptive brightness on = better battery. Content adaptive brightness off = better whites? If that's right doesn't anyone know the impact on battery life with it off?

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] zephiK:
Probably significant. Whites consume more power on Super AMOLED devices.
[Samsung Galaxy Nexus] Antob125:
So 135,135,200 gamma 0 0 0 and omap gamma 1.0?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dr Byte:
I feel that pain. Back on my Desire, I used to have trouble getting all the way through the boot because the default voltage in the kernel was lower than that required to complete the process on my phone. I suggested to EViolet what I'm about to suggest to you, Franco, though in a more precise manner:

Boot using "known safe" voltages/clock speeds only; hardwired into kernel. Always.

Using some generally available "time since boot" quantum, wait for 30s before applying voltage/clock tweaks.

Have a quick-access "Use default settings" widget available and/or a "persistent" file that is deleted after (say) 5 minutes uptime. If the file is still present at boot, assume that the last settings were unsafe and remain on defaults. (kinda like the generic ROM behaves with respect to re-flashing the default Recovery partition unless the flag file is deleted)

Delete the "boot successful/failed" flag file on a controlled shutdown.

In other words, time-gate the application of "dangerous" settings to give the user time to recover from silly values "set on boot."

Which is preferable: using a poofteenth of extra battery charge and/or time each boot, or having to dive into recovery and restore a backup or push a script?

Offered for consideration... just my over-conservative engineering thoughts. I prefer stability and safety over ultimate speed any day.
[Samsung Galaxy Nexus] revolt1:
where is the 200 kernel cant seem to find it
[Samsung Galaxy Nexus] zephiK:
http://minooch.com/franciscofranco/Galaxy Nexus/JB_test/Ice Cream Sandwich/
[Samsung Galaxy Nexus] Antob125:
What does fsync do in layman terms? I looked up data integrity on Google and there is many different meanings so I'm not really sure. Not sure if I should keep fsync on or off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ThatTechShow:
Props to whoever gave the Color settings! My screen looks much much better!! Feels like a brand new phone! :D
[Samsung Galaxy Nexus] atsavlis:
Franco, could you suggest some settings for "governor control" that you think are best for performance and battery with interactive...
[Samsung Galaxy Nexus] metalspring:
I'm sure his suggested ones are the preset ones
[Samsung Galaxy Nexus] metalspring:
With fsync disabled, an unexpected reboot (like a freeze and reboot) can corrupt data, anything from erasing app data (for one or several apps), causing apps to randomly force close, and even corrupt system data to the point where the rom will bootloop

However with it enabled it greatly decreases I/O performance (basically read/write performance)
[Samsung Galaxy Nexus] osm0sis:
Reproduced, BUT it only started happening after SuperUser updated my su binary to 3.1, so I rolled it back to 3.0.3.2 and now everything's playing nice again. I was also getting some FCs with Franco updater app when 5.5 initially updated; cleared data, uninstalled and reinstalled and now that's fine too.

Confirmed/reproduced here. Stock ICS 4.0.4, unlocked and rooted, Franco.kernel #196. Even with su 3.0.3.2.

I haven't noticed it change very dramatically. I prefer to have my screen looking like it went through SOME kind of QC. :p
[Samsung Galaxy Nexus] simacai:
can anybody tell me what's c.a.b? and how to set the contrast?

I'm using 210 on jelly bean, and updater still 5.4

Sent from my Galaxy Nexus