yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] iEternalHero:
I got a strange issue, each time i turn off the screen and then when i turn it on back, the maximum frequency goes back to 1200Mhz. I'm running CM10 Nightlies ( Jellybro ). SuperUser was installed, and it had this issue, so i thought uninstalling it, and flashing SuperSU on top would work, i got the same issue. Well, i tried to update the SuperSU binary and it's still the same, i tried to search in the thread but i didn't find how to make the MAX frequency stay all the time.

EDIT: i uninstalled all "CPU" apps like SetCPU or NSTools, and it's the same, in Franco app i also tried to put the MAX Cpu screen off at 1536Mhz but it always goes back to 1.2Ghz
[Samsung Galaxy Nexus] Redflea:
Look two posts above yours.
[Samsung Galaxy Nexus] Dr_Ownage:
well if Franco says that that will work then there is your first clue. secondly you can open rootexplorer and go to:

/sys/module/omap2_cpufreq/..../.../ and if the file we were "echo"ing is there then it work.

all the echo command is is writing some text (in this case its a "1") to a file.

echo hello > text.txt would write a file that is named text.txt with hello inside.

the kernel that Franco has made looks into that directory and if there is a file there it checks the file for a 1 or a 0 (binary)

if its a 1 its on.

if its a 0 its off.

1 = on

0 = off

tada :)
[Samsung Galaxy Nexus] kara mustafa:
after using this method parametr is still 0. Can we change it in root explorer?
[Samsung Galaxy Nexus] ro_explorer:
For "non-terminal" users there is an easyer way :)

Just install root browser from market. This will allow you to mavigate in the respective path and edit the hotplug_enable file like any other file (make sure you change permissions to write first). You can also check the content of the file with the same tool.
[Samsung Galaxy Nexus] raimondomartire:
Hi Franco, can add call recording function in your kernel?
[Samsung Galaxy Nexus] meilstone:
well if i use the terminal emulator i can change the setting. but when i do a reboot it goes back to 0. so its disabled again.
[Samsung Galaxy Nexus] grinch247:
I experience the same...unless you switch to 3g mode then battery will last all day long no problem @ all :)
[Samsung Galaxy Nexus] meilstone:
ok on every method i use i get the same results. if i use the terminal emulator the changes are away after a reboot in the hotplug settings.the same happens if i change the settings manually via root explorer.
[Samsung Galaxy Nexus] daandman:
I can confirm this, I edited it in root explorer, rebooted & it was reset to 0.
[Samsung Galaxy Nexus] grinch247:
I am not 1 for benchmarks etc...however this kernel did give me the highest results thus far! however 2 x's screen wouldnt come back on :( had it set to interactive 1200max-700min :(
[Samsung Galaxy Nexus] beekay201:
Not kernel related. Not even aosp related, i believe.
[Samsung Galaxy Nexus] manager77:
hey, Franco

why on conservative min. frequency is set to 700 000 and not to 350 000KHz?Thanks!
[Samsung Galaxy Nexus] franciscofranco:
I already answered that 40 times, sorry I'm not gonna repeat it =(

Guys if you want that hotplug_enabled to stick you have to create an init.d script, I think that's pretty obvious eheh
[Samsung Galaxy Nexus] kara mustafa:
bur if we change to 1 via Root Explorer, it will be permanent?
[Samsung Galaxy Nexus] kjwalker:
It is kernel related, actually.
[Samsung Galaxy Nexus] :
Just create file in init.d (i named mine s99hotplug) with correct permissions (if not sure set all) with following:

#!/system/bin/sh

echo 1 > /sys/module/omap2plus_cpufreq/parameters/hotplug_enabled

Reboot!

Edit: franco was faster!
[Samsung Galaxy Nexus] Dr_Ownage:
Yes i agree, it appears that after reboot the settings are reverted...

i dont find myself rebooting that much anyway, and as Franco mentioned above just create a script.
[Samsung Galaxy Nexus] kjwalker:
Or "maybe in an alternate universe" :D
[Samsung Galaxy Nexus] manager77:
ok...but why don't you release a kernel (alternative) with 350 000 by default?Thanks!
[Samsung Galaxy Nexus] meilstone:
well you can change that via setcpu and the option set om boot
[Samsung Galaxy Nexus] Hussainally:
Reflash the new updated Franco kernel v223
[Samsung Galaxy Nexus] Tarun95:
U uninstalled Facebook. Why ? It works great for me
[Samsung Galaxy Nexus] decarre:
Yes :)
[Samsung Galaxy Nexus] simms22:
thats ok, we still love the gingerbread man :)
[Samsung Galaxy Nexus] iEternalHero:
Hahaha it worked, Thanks ;)
[Samsung Galaxy Nexus] Flukester69:
Removed my post. It was a stupid post anyway. I didn't mean to judge or anything but when I read my post I didn't like it. Turns out I am having drops with other Roms/kernels too. Its a game of hit and miss for me with roms. I'm truly grateful for this kernel and all the other stuff here.
[Samsung Galaxy Nexus] Cheezhead19:
Forgive me if this is a dumb question, if my max cpu randomly changes to "1200" from "1228" so no option is checked, that is the ROM's doing right?
[Samsung Galaxy Nexus] GeekMcLeod:
Reflash r223, it has a fix for that issue.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] franciscofranco:
Thank you for the post :)
[Samsung Galaxy Nexus] ntorresla:
Bro Can you share some battery saver volting settings?

Edit: I just read the previous post... I wl research more

Saludos desde Ecuador
[Samsung Galaxy Nexus] simms22:
i dont undervolt. quite opposite, i set my voltage to perform better, not to save battery. and btw, undervolting can cause the opposite effect, more battery drain. if the voltage isnt enough for your phone to get to where it needs to be, your phone will work harder getting there, therefore using more battery. if i do want to save battery, i just lower my cpu speed. i usually set my cpu speed to 1036mhz(trinity) if i need the battery life. with the cpu speed lowered, i regularly see 5+ hours of screen on time, no undervolting at all from the default settings.
[Samsung Galaxy Nexus] :
If u get 'better battery stats' from the playstore you can troubleshoot and see what's keeping your phone awake. It takes some reading and searching to figure it out but definitely pays off. I've been using that app for months...works really well.
[Samsung Galaxy Nexus] :
Have UV been proven useless for battery life beyond maybe increasing it by life 2% under ideal conditions.
[Samsung Galaxy Nexus] LNJ:
I believe that app is free for XDA members. Just have to download it from the original thread.
[Samsung Galaxy Nexus] renna1992:
got awesome battery life with #221, updating now on #223

ondemand/deadline, 384/1036, no uv or oc

a few screenshots:
[Samsung Galaxy Nexus] ntorresla:
Good, 2g or 3g?

Saludos desde Ecuador
[Samsung Galaxy Nexus] Cheezhead19:
I am on r223, Preview AOKP probably is the problem. Never happened on vicious v4.1
[Samsung Galaxy Nexus] renna1992:
well with wifi only 2g, but after that with a few exceptions of maybe 1 hour or something allways 3g :)
[Samsung Galaxy Nexus] zephiK:
Here it is, http://xdaforums.com/showthread.php?t=1179809
[Samsung Galaxy Nexus] franciscofranco:
****... almost 3 Million views...
[Samsung Galaxy Nexus] defconoi:
Hey franco got an idea for your app, since most people have color issues below only a certain brightness percentage, can you see if we can customize the color only for certain brightness percentages? My color above 15 percent is fine. Or adding the ability to set a minimum brightness to avoid the tint issues all together.
[Samsung Galaxy Nexus] imreezm:
Is it only me of Trinity contrast not sticking with reboot? (Jellybro + R223)
[Samsung Galaxy Nexus] svan71:
?

So when did Franco retire ics builds?
[Samsung Galaxy Nexus] zephiK:
R200: Latest ICS kernel w/ some JB goodies (Flashable on ICS)

R196: Latest ICS w/o JB goodies.
[Samsung Galaxy Nexus] franciscofranco:
ICS is old school by now, but r196 is the latest stable ICS kernel.
[Samsung Galaxy Nexus] indoline:
sorry if I haven't read the entire thread, but the latest JB kernel says "unknown" under kernel in phone info?
[Samsung Galaxy Nexus] franciscofranco:
No?
[Samsung Galaxy Nexus] zephiK:
It actually does appears as unknown. At least on CM10, I noticed this since yesterday but the kernel itself still works (and appears as franco-kernel on third-party apps that determines kernel version). It just doesn't display in About Phone. When I switch to another kernel, kernel version appears again.
[Samsung Galaxy Nexus] indoline:
^ thx
[Samsung Galaxy Nexus] Culex316:
Any plans on merging the latest Linux kernel mainline release to this kernel?

By the way kernel is running great. :)
[Samsung Galaxy Nexus] franciscofranco:
What the ****. Which CM10 nightly is that?

No, no need for that.
[Samsung Galaxy Nexus] Cheezhead19:
Any idea about how to fix the max cpu? I am on r223 already. AOKP test rom, probably their fault...
[Samsung Galaxy Nexus] GeekMcLeod:
This has been mentioned a lot, he made a small fix and pushed it out as r223 again. Just reflash it and you'll be fine. Searching is your friend.
[Samsung Galaxy Nexus] britoso:
I'm getting bootloops using the nightly version (franco.Kernel-r196.zip), same result using both 384 and 512MHz.

Should I try some other version ?

edit: "nightlies" probably refers to CM9 nightlies (says 4.0.4 in the log)! Trying the 4.1.1 version now. (franco.Kernel-r223-512GPU.zip)

edit2: that works fine. :)

W/Zygote ( 1474): Class not found for preloading: android.database.sqlite.SQLiteDatabase$DatabaseReentrantLock
D/dalvikvm( 1474): WAIT_FOR_CONCURRENT_GC blocked 0ms
D/dalvikvm( 1474): GC_EXPLICIT freed 31K, 85% free 631K/4096K, paused 0ms+0ms, total 2ms
D/TextLayoutCache( 1474): Using debug level = 0 - Debug Enabled = 0
E/JNIHelp ( 1474): Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
F/libc ( 1474): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1474 (zygote)
I/DEBUG ( 116): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 116): Build fingerprint: 'google/yakju/maguro:4.0.4/IMM76I/330937:user/release-keys'
I/DEBUG ( 116): pid: 1474, tid: 1474, name: zygote >>> zygote <<<
I/DEBUG ( 116): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
[Samsung Galaxy Nexus] zephiK:
http://fitsnugly.euroskank.com/?rom=cm10&device=maguro

cm-10-20120722.1609-maguro and cm-10-20120721.1755-maguro. i never used the ones before that because the kernel wasnt updated to boot with cm10

indoline posted a screenshot (but he removed it) where he had the same problem using paranoidandroid as well... might have something to do with code relating to CM10

Using benchmark apps show the kernel version just fine,

@Cheezhead19: Re-download r223 and reflash it. A new version of r223 was released to address the 1200mhz problem.
[Samsung Galaxy Nexus] spaceman860:
This one http://xdaforums.com/showthread.php?t=1771534

[CM10][Jellybro] Maguro Nightly Kangs put it shows up under CPU spy app

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] Cheezhead19:
Thanks, sorry I missed the memo about re-release for r223.
[Samsung Galaxy Nexus] pwvandeursen:
hee franco sorry for bugging. just another bump. if it is not possible also fine, just want to know what I am up against.

thanks again!
[Samsung Galaxy Nexus] CADude:
Congrats on collaborating on your first ROM, Franco! Here's the link for anybody who wants it.

http://xdaforums.com/showthread.php?t=1790532
[Samsung Galaxy Nexus] bat0nas:
Hi,

Power mode - none. I set min and max cpu and select governor. I check to set cpu settings on boot:

View attachment 1216223View attachment 1216224

But after the restart - cpu frequencies change and another governor is selected.

View attachment 1216227

I tried clearing franco app data.

But still I Ahave the problem.

Please help. Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
For some reason the 1036 MHz is hardly used and it stays more on 1228. Before it used to be more on 1036 than 1228. Will it drain battery ?
[Samsung Galaxy Nexus] slvrarrow:
Use setcpu to adjust 'powersave' to 100 this causes the cpu to throttle down more quickly and use a lesser adequate frequency more often without being too high a setting as to cause lag. You can try a higher setting upto 1000 but id recommend no more than 200. 100 seems effective for me.
[Samsung Galaxy Nexus] Eugene1991:
Same story here :confused:

Wasn't like this before, but not a big problem I guess.

Was on interactive (as in everything was default) :)
[Samsung Galaxy Nexus] slvrarrow:
I use ondemand by the way
[Samsung Galaxy Nexus] Tarun95:
I don't use setcpu. I use Franco kernel updater. Any changes similar to this to be done in his app ?
[Samsung Galaxy Nexus] era_:
r223 it's seem the battery gone faster :(
[Samsung Galaxy Nexus] slvrarrow:
No I don't think so - running the two side by side doesnt impact negatively on performance OR battery life as far as I've noticed.
[Samsung Galaxy Nexus] TEK112:
I noticed this as well. 221 was much better on battery.

DISCLAIMER: For my specific type of use.
[Samsung Galaxy Nexus] vinny13:
I've been seeing random disconnects here and there with 223.
[Samsung Galaxy Nexus] T-Loop:
This little tweak helped me, now it stays ALOT in 1036Mhz slot.

http://xdaforums.com/showpost.php?p=28767430&postcount=22824

Goto Franco's app, Governor Control and set hispeed_freq to 1037000.

Edit: More info here http://xdaforums.com/showpost.php?p=28778756&postcount=1
[Samsung Galaxy Nexus] Tarun95:
This seems to work thanks :)
[Samsung Galaxy Nexus] Tarun95:
Hey guys kinda off topic but I would like to share my colour settings. They seem to be great at least on my phone. Wrong thread but I see people using colour control in Franco app so posting it here.

Colour multipliers

Red:200

Green:150

Blue:200

Red:-3

Green:0

Blue:2

Trinity:0

Gamma:1.0

My display looks better than s3 now.:p Side by side comparison. This thread is most popular and would like to help :)

Edit : I set blue to 210 and it is perfect but I read somewhere setting these values above 200 damages the screen
[Samsung Galaxy Nexus] dyndragon:
I got an SOD on the latest r223 kernel CM10 Kang. No logs of course on a battery pull, just FYI.

I'm also not seeing that parameter to tweak in the previous few posts in Franco's kernel app's governor control.

Edit: Nevermind, its only present for interactive.
[Samsung Galaxy Nexus] Antob125:
Content adaptive brightness checked or unchecked?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] garu12:
Dunno if its just me but the app will not auto flash or download the 384 kernel. Using cm10 skank. Rebooted twice. Re installed app. Cleared data. Even tried superuser instead of superSU and no go. Worked fine last night.
[Samsung Galaxy Nexus] Tarun95:
Unchecked for me. I didn't touch it but when I first opened the app I think it was checked. I am not sure anyway that doesn't affect colours much just uncheck it :)
[Samsung Galaxy Nexus] Tarun95:
Sorry by mistake
[Samsung Galaxy Nexus] JediDru:
I'm on 223 512 gpu. Min 384 max 1420 Wheatley and noop. I hadn't touched my phone in 11 hours and lost 5%. This is the type of standby I need. While using feels lag free. Thank you for your hard work.
[Samsung Galaxy Nexus] Antob125:
Tried them. Too yellow for me. I haven't found anything that beats this:

135 135 200

0 0 0

C.A.B checked

Trinity -10

Omap Gamma 1.2

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tyraelasd:
Hey guys, I just got my Gnex a few days ago.

if Im after better battery life, should I install this kernel? I dont want better performance since Im jeally bean, just want better battery life.

Cheers.
[Samsung Galaxy Nexus] Tarun95:
Feels too dark and bluish on my display. Maybe it suits your display well :)
[Samsung Galaxy Nexus] Tarun95:
Flash this. Franco is known for great performance without sacrificing battery ;)
[Samsung Galaxy Nexus] GeekMcLeod:
Tried it, like it. Don't find it yellowish at all. Althoguh, I prefer a bit darker.

160 172 180

-4, 0, 5

-5

1 or 1.2

I do really like that. Might keep some values but make it a bit darker. Only changed he Omap4 Gamma to 1.2

Someone should make a thread for this sort of thing. Be better than clogging up this thread even though they basically go hand in hand. Would also be quite helpful for people looking for good displays.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] fatappel:
Thanks for sharing. Tried and too pink/red on my device. For me the best is:

Multipliers

Red: 215

Green: 200

Blue: 230

Red: 2

Green: 0

Blue: 5

D.A.C. Unchecked

Trinity Contrast: -5

Omap4 Gamma: 1.0

Give it a try. A touch cooler than warm, deep, rich colors and very dark blacks. Screen burn is unproven and has not been an issue for me running multipliers over 200 for 4 months.
[Samsung Galaxy Nexus] Tarun95:
Does setting value above 200 damage the screen ?
[Samsung Galaxy Nexus] goldleader:
Here are some findings of mine regarding r221 & r223: On r221 i get gps signal look no problem. After flashing r223 gps never locks. I flash r221 again and gps works fine. Just thought you'd like to know...

Phone: Galaxy Nexus GSM

ROM: Bigxie's deodexed 4.1.1
[Samsung Galaxy Nexus] GeekMcLeod:
I am on r223 and my gps locks as quick as usual. It wasn't yesterday but apparently there was solar flare ups that were causing ****

If it damaged the screen, I'm sure someone would have said something by now or Fraco wouldn't allow such values.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] barrist:
Using franco updater... is the cpu settings NOT supposed to stick after reboots?
[Samsung Galaxy Nexus] zephiK:
check the box that says... set cpu settings on boot
[Samsung Galaxy Nexus] barrist:
yeah i did that... they don't survive a reboot though. (i'm on cm10 jellybro nightlies)
[Samsung Galaxy Nexus] zephiK:
Hmmm, it could be a bug. I'm playing around with other kernels for the time being at the moment otherwise I would try it out myself.

Are you using SuperSU instead of Superuser? I remember reading about Superuser not working too well with rooted apps on JB.

Here's the link, https://play.google.com/store/apps/...upersu&feature=nav_result#?t=W251bGwsMSwyLDNd

Download that and open the app to update SU binary.
[Samsung Galaxy Nexus] GeekMcLeod:
Mine don't stick either. They haven't for a while but never really cared and figured other people had the same problem and would've mentioned it before myself.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] zephiK:
I just tried.. changed max cpu to 1GHz and rebooted and sticked after reboot. I'm on CM10 Jellybro... although I am using Trinity kernel at the moment (still using Franco Kernel App to control CPU)

Update to SuperSU if you haven't (as I mentioned above) and see if that resolves the problem.
[Samsung Galaxy Nexus] barrist:
Great, seems to be working now!
[Samsung Galaxy Nexus] GeekMcLeod:
I always have mine at 384 - 1305,lazy. When I reboot its 384 - 1228,interactive.

I will ty SuperSU rather than superuser and see if it helps.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] isinisterx:
http://xdaforums.com/showthread.php?p=29210454#post29210454

I made this thread so we can talk about various color configs.
[Samsung Galaxy Nexus] Tarun95:
For some reason my computer doesn't detect my phone. Restarting helps at times but not always. My phone charges though when I connect to the computer.
[Samsung Galaxy Nexus] GeekMcLeod:
Sounds like you have the fast usb charge selected. Go into his app, and disable it. It won't charge as much but it will connect to your computer.

GSM Galaxy Nexus -- ParanoidAndroid -- franco.Kernel Nightlies
[Samsung Galaxy Nexus] goldleader:
If a solar flare was causing the issue it would persist when changing kernels, and it didn't...
[Samsung Galaxy Nexus] GeekMcLeod:
I didn't state that as a fact, I was just saying again what I had read previously about GPS issues.Thanks for the "this-guy-is-a-****ing-idiot" attitude though, I really appreciate it. Also, if it were a kernel issue my GPS would still be completely off like it was yesterday except today it worked like normal.

Disabled SuperUser. Installed SuperSU and let it update itself and get superuser permissions. Everything is sticking on boot like it is supposed to. Thank you, whoever it was that mentioned this.
[Samsung Galaxy Nexus] bat0nas:
Anybody?

My setup: stock jb+r223+latest updater.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GeekMcLeod:
Just had this problem, and on the previous page or 2 there is a solution.

You are using SuperUser, switch to SuperSU. I just did that and now everything that should be, is setting on reboot.
[Samsung Galaxy Nexus] bat0nas:
Thanks!!! I will try asap.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Galaxy Nexus Collaborative Optimal Color Settings

Has an open Google Docs spreadsheet for everyone to share their color settings without cluttering up threads. :)
[Samsung Galaxy Nexus] bat0nas:
Thanks! It worked. Just got rid of superuser and now I'm a supersu fan :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stick1300:
Just chiming in to say that making the switch to SuperSU solved my "settings not sticking" issue as well
[Samsung Galaxy Nexus] isinisterx:
What governer are you all using? And what CPU frequencies?
[Samsung Galaxy Nexus] GeekMcLeod:
I use Lazy and 384-1305. Been doing too much flashing, rebooting and installing of stuff to know how well my battery is on these settings.
[Samsung Galaxy Nexus] renna1992:
Ondemand/deadline 384/1036
[Samsung Galaxy Nexus] franciscofranco:
SuperSu fixes **** not persisting on reboot, thats for sure :)
[Samsung Galaxy Nexus] GeekMcLeod:
Glad it worked! But if you are a Tibu user, I would suggest keeping Superuser. Completely got rid of it then all of a sudden my Tibu wasn't reading any of my backup data. Re-intalled Superuser and then Tibu had all my apps/data back in it.
[Samsung Galaxy Nexus] CADude:
Yeah Superuser is pretty much obsolete these days. SuperSU is currently much better solution. All ROM devs should use it by default right now.
[Samsung Galaxy Nexus] simms22:
hmm, persisting ****.. constipation? :p
[Samsung Galaxy Nexus] splus:
Franco, I think it was reported few times before but here's again - fsync on reboot is always checked.

I'm using SuperSU and all other settings stick on reboot.

However, I just noticed that fast USB charging option also sticks on reboot. Shouldn't that be automatically disabled on boot in case of some problem so that phone can always be accessible via USB on boot? I think that's how it worked before, if my memory serves me right.
[Samsung Galaxy Nexus] sway40:
Wtf I just noticed this, something borked? It says 0 even though I change it, but when I click to change it it says 4. Noticed my colors were off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yes, and an ugly one.

The fsync **** is fixed on my local files. The FastCharge bug I didn't know about. I'll take a look.

Thanks, seems like a small bug that I wasn't aware of :)
[Samsung Galaxy Nexus] GeekMcLeod:
The 'tick' shows on boot, but the option doesn't stick. I have that checked a lot and when I reboot, while still plugged into the computer, it will connect to the computer once done booting.

This has happened to me on previous versions of Francos app. Are you on 5.8.4?
[Samsung Galaxy Nexus] sway40:
Yeah im updated, it just happened, I can notice my colors messed up easily.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dyndragon:
I also just noticed....on r223 for some reason my phone stopped charging at 26%. I had to go into Franco app to set the max battery level to something other than 96% and then back to 96%. Then it will continue charging. This happened kind of randomly. I'll see if I can reproduce.
[Samsung Galaxy Nexus] bigroof:
Does anyone know the color settings in Francos app to match trinity? I love Francos kernel but I hate losing Trinity's color.
[Samsung Galaxy Nexus] bat0nas:
Just tested titanium backup pro with su granted by supersu. No problems at all. I backed up Amazing alex, uninstalled it and restored app+data w/o problems.

Sent from my Galaxy Nexus