yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Bakedbread:
hey franco,

thanks for all your work - been using your kernel since the beginning

just wanted to report im getting bootloops with # 17 right now. The moment it boots to my homescreen it crashes and reboots.

I'm running Bixie's rom btw...i might need to battery pull

*edit....yeah..i cant boot back into my ROM. I even tried flashing 16.2 again but it wont get in and I didnt make a backup (my fault)

i'll just have to restore to an earlier one i had before...but yeah...has anyone else had any luck booting wiht #17?
[Samsung Galaxy Nexus] bradm23:
Franco- I see in your change log that you added steps back to gazelle, however I see that there are steps in turtle also now.

I am also curious what u found in testing regarding 400 min compared to 700. I typically still use 700 but didn't know if your research suggested using 400 for battery life
[Samsung Galaxy Nexus] darrendm:
If I'm not mistaken I think this may be because you have UV settings too low and "Set on Boot"

I guess a restore will do the trick.

#17 works perfectly here.
[Samsung Galaxy Nexus] ro_explorer:
I just put #17 and I already had 2 reboots while operating normally the phone. All settings are stock, no UV no OC .. 100% stock #17.
[Samsung Galaxy Nexus] yyz71:
Running this on Pauls 4.0.4 beta 2. At 1.5ghz min 400 and all is well :-)

sent from my pimped out galaxy nexus 4.0.4 :)
[Samsung Galaxy Nexus] sert00:
any chance to the ability of undervolting 1350 and 1500 steps?

francisco,how mv you set the 1500 step?normally with trinity my phone reboot if it isn't at least 1300 mv.here on yours i don't know how is the current mv.

thanks in advance for the reply!
[Samsung Galaxy Nexus] rizzxx7:
Same here, running ms3
[Samsung Galaxy Nexus] mzimand:
I am able to run at 1.5 safely whereas on other kernels I would not be able to run at 1.42. There must be magic dusk sprinkled on this kernel.

I am getting

95+ on Linpack

3600+ on Quadrant
[Samsung Galaxy Nexus] loudaccord:
can you complete AnTuTu?
[Samsung Galaxy Nexus] franciscofranco:
What? Open setcpu or my app undervolt panel and see for yourself? Stock voltage for 1500 is 1380mV.
[Samsung Galaxy Nexus] poopooface:
17 is making my phone reboot every time I hit the homescreen in GummyNex.

Didn't change my UV settings from 16.2 at all.

Flashing back to 16.2 until the next update.
[Samsung Galaxy Nexus] franciscofranco:
I wonder if there are devices that cant handle DCC force enabled on all frequencies (this is how 1,5ghz is achievable without being sluggish).
[Samsung Galaxy Nexus] ro_explorer:
I've flashed back the original apex rom and I put #17 on top ... no reboots so far (10 minutes) .. hopefully this move did the trick.
[Samsung Galaxy Nexus] franciscofranco:
Thanks. Again my device works without an issue with 1.5ghz even with DCC disabled xD I guess Im lucky enough to have devices that came from good sillicons.
[Samsung Galaxy Nexus] darrendm:
SetCPU force closes upon pressing the voltage tab.

1350 and 1500 are not changeable (they are not there on the UV screen) using your app
[Samsung Galaxy Nexus] duRin90:
Not sure if anyone had similar problem before but I'm having problem with your app updater. Randomly (and after reboot) it takes back my settings to 400/700 FrancoTurtle.

Please advise.
[Samsung Galaxy Nexus] ro_explorer:
I've hoped in vain .. it rebooted right after (ironic, I know) updating Franco Kernel tool from market :) ... I'll revert back to #16.2 until other stuff.

Of course, by the time the phone is rebooted, there is no more any usable logcat.

I'll try to watch the logcat from adb.
[Samsung Galaxy Nexus] franciscofranco:
Yes they are I changed the voltages myself to test it and they were there perfectly. My GN is at home atm otherwise I would screenshot you.
[Samsung Galaxy Nexus] poopooface:
No problem... I did undervolt slightly in 16.2, even though I was not actually using the 1.5 step when I booted in 17. Therefore, I might flash 16.2, up the voltage, then flash 17 again to see what happens. I'll let you know.
[Samsung Galaxy Nexus] slayp00n:
What file do I delete to get stock speeds back, bootlooping @1.5ghz...
[Samsung Galaxy Nexus] DarkGruf:
Same here set cpu FC on voltage tab, and UV controls go from 200 to 1200 in your app (200, 400, 700, 1000, 1200).

Also changes again don't stick. OC settings go back to 400 - 1000 after reboot.
[Samsung Galaxy Nexus] sert00:
already have yours app but sorry i made a typo...i mean OVERvolting the 1500 step..but if it's 1380 ma the 1500 mhz step then i have nothin to do...it reboot after 10 sec on 1500..thanks for the reply mate.

anyway all the app like yours,system tuner etc,don't see me the 1350 and 1500 step for under-or over-volting..only until 1200.now i try to reflash the kernel..

EDIT sorry,have not read last comment,it seems that all don't see the 1200+ step for undervolt
[Samsung Galaxy Nexus] darrendm:
This is what I am having/seeing. (Same as DarkGruf)

I can confirm this also. My 200-1000 was reset to 400-1000 after reboot. The set at boot box is ticked.
[Samsung Galaxy Nexus] ro_explorer:
More bad news .. the last reboot ****ed up my /data ... I have to start all over again :( ...

Franco, seriously, there is something terrible wrong in #17 ...
[Samsung Galaxy Nexus] darrendm:
Seems to be fine for me. I'll make sure I post if I get any random reboots.

I'm on AOKP23 if that makes any difference.
[Samsung Galaxy Nexus] poopooface:
Well, it seems that now I get an infinite bootloop whenever I try to flash back to 16.2 or even 15.2 from 17. I am gonna have to wipe everything now.

Buyer beware on 17.
[Samsung Galaxy Nexus] Elganja:
same here... all my **** is ****ed up... oh well... wipe and start all over again
[Samsung Galaxy Nexus] jan-willem3:
UV settings 1350 and 1500 are indeed not shown.
[Samsung Galaxy Nexus] atsavlis:
I can confirm set cpu freezes when you go into the voltages tab, but when I use system Tuner Pro to change my voltages, it opens, but only reads voltages up to 1.2GHz...

1.35 and 1.5 are missing...
[Samsung Galaxy Nexus] petsasj:
Same as the above. Rebooted once on its own, then ****ed up data and have to wipe and reflash ROM now.
[Samsung Galaxy Nexus] monkey hung:
Mine is doing great so far but there is no option in the Franco app that gives me the option to set the CPU to 1.5Ghz
[Samsung Galaxy Nexus] slayp00n:
Running 1,5ghz pretty much rock solid amazing.

Franco app needs an update though for multipliers & correct cpu UV settings.

---------- Post added at 10:04 PM ---------- Previous post was at 10:01 PM ----------

since you seem to have gotten around the dcc issues: is 1.65 and 1,7ghz next?
[Samsung Galaxy Nexus] sluflyer06:
Trying to apply undervolt in the FrancoUpdater app with the same values I've always used results in hard lock of the device as soon as you press the 'apply values' resulting in battery pull. #17

Clicking on Voltage tab of SetCPU also causes instant FC. this is the first time your Kernel has ever had stability issues for me.
[Samsung Galaxy Nexus] darrendm:
Just had my first freeze and reboot. No OC, no UV. (200-1000, francoturtle)

Nothing is effed up though, all my data etc seems to be fine.

Maybe it was having 200 as my min, will keep 400 as min and post back if it happens again.
[Samsung Galaxy Nexus] slayp00n:
what are people running for 1.5ghz voltage wise?
[Samsung Galaxy Nexus] Elganja:
even a complete wipe and reinstall with #17 reboots randomly a lot
[Samsung Galaxy Nexus] loudaccord:
Don't you guys do nandroids? I do a backup every time I flash a kernel.

START DOING BACKUPS.
[Samsung Galaxy Nexus] slayp00n:
Yes I get random reboots also which see to have nothing to do with load.

---------- Post added at 10:34 PM ---------- Previous post was at 10:33 PM ----------

guys how come when i put

echo "4200000000 4200000000 4200000000" > sys/class/misc/colorcontrol/multiplier

in an init.d script it doesn't work on boot?
[Samsung Galaxy Nexus] DaF1974:
Same here. I could use System Tuner though. I've also had several reboots even without using 1.5 GHz. It seems to be stable now with 400 to 1200 and default voltage settings.
[Samsung Galaxy Nexus] Elganja:
i reverted back to 16.2 ... something is def up with 17...

and this time... nandroid backup.. I have learned my lesson
[Samsung Galaxy Nexus] magn2o:
Flashed to #17 without issue. Update app, Min/Max @ 1500, Stock Volts (using franco's app). Running Stability Test right now, 6 passes in. So far so good. :p
[Samsung Galaxy Nexus] slayp00n:
same but still random reboots. they are unrelated to load.
[Samsung Galaxy Nexus] sandro.bertini:
Hi,

I think we have a big variance in the overclock tolerance of each individual GNexus Silicon. I am using #17 for some hours without issue (400/1500 - FrancoGazelle, no UV).

Runned some benchmarks as a stability check (CF-Bench, Antutu and Quadrant) with no problem whatsoever.

Just as a note, I have had rock solid stability from all Franco Kernells, including the infamous #15, which apparently caused a lot of problems for most people. I think I got realy lucky with my CPU.

Regards,
[Samsung Galaxy Nexus] marc.tulley:
Get crashes on 1.5ghz Franco.

Despite what you see, looks like no one else has voltage control for 1.35 and 1.5. AOKP and Franco app shows the same available voltage values.

Maybe if I had the ability to tap the 1.5ghz voltage up a bit it would stablise.
[Samsung Galaxy Nexus] loudaccord:
No reboots here... ran Quadrant (3732), NinaMark2 (24.9fps) and AnTuTu(6570)... all at 1.5ghz. No problems yet. I'm surprised AnT wasn't higher but I don't really care. Just surprised to see 1.5 working the way it should.

lol:
[Samsung Galaxy Nexus] poopooface:
These people who keep talking about "good silicon" and "bad silicon" seem not to understand what the f*** is going on. Myself and others have stated in no uncertain terms that we were fine using the same voltages on the other versions of this kernel. Furthermore, on boot, when I started 17, I got far enough into the settings to see that it was still set on 400/1350. I didn't even TRY to use the 1500 step before getting the reboots and subsequent corruption resulting in a wipe.
[Samsung Galaxy Nexus] diesel2k:
Just got reboot on #17. First reboot on Franco kernel I have experienced on all versions

Sendt fra min Galaxy Nexus med Tapatalk
[Samsung Galaxy Nexus] przemchess:
Flashed 17# so far so good

Running really stable for me on 1,5GHz

The only one thing missing is voltage setting for 1,3 and 1,5 GHz in Franco control app

Also is the first time I've scored on Franco Kernel over 7000 in antutu

http://imageshack.us/photo/my-images/15/screenshot2012021422364.png/
[Samsung Galaxy Nexus] slayp00n:
Exactly, just as I have said: reboots are UNRELATED to load.
[Samsung Galaxy Nexus] magn2o:
I've done about half a dozen reboots, opened and closed at least 30-40 apps, mucked around with various settings toggled on/off, received push notifications, and ran scaling stability tests. Not a single reboot, crash, or FC.

So, we'll see what happens over the next few hours/days.. but, so far so good.
[Samsung Galaxy Nexus] slayp00n:
Can anyone help me with an init.d script for multipliers? I just cannot get it to run on boot?
[Samsung Galaxy Nexus] Elganja:
just like to add.. I was experiencing issues with no oc, ov and on francoTurtle. I'm on codename android 1.3.3

first was the data issue, after wipe install I was getting random reboots.
[Samsung Galaxy Nexus] nikulogical:
Yeah looks like I'll stick to 16.2 for now..
[Samsung Galaxy Nexus] Gahh Its Lee:
So everyone who under volts is having issues with 17? It seems a lot of people think uving doesn't save battery but I can't see how that would be the case. It ran stable for me until I touched the voltages. Even bumped them up a lot from my 16.2 and still a no go. I'm back on 16.2 for now. Also is anyone else having issues with the app resetting to the kernel defaults on reboot?
[Samsung Galaxy Nexus] blackdub370:
yes... reboots with default configuration :S
[Samsung Galaxy Nexus] drawde40599:
17

@franco . 17 is smooth/fast as #$%&!!! Overclocked to 1500 been on phone last hour, texting, internet, YouTube . Not one hicup or reboot!!! THANK U!! This is y I bought this phone: )
[Samsung Galaxy Nexus] Elganja:
I wonder if it is people using francoTurtle whom are having the issues...
[Samsung Galaxy Nexus] CaspaTheGhost:
Auto flash didn't work, rebooted but still on previous so did it manually.

Had a one reboot to.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for all the feedback. This is what we get for experimenting new things and this 17 is definitely an experiment because of the high clock and the things I had to do to make it work. Im getting home (**** its freezing outside) and will look at the kernel code based on feedbacks.
[Samsung Galaxy Nexus] drawde40599:
I'm 400/1500 interactive stock UV . Build 23 AOKP
[Samsung Galaxy Nexus] minooch:
What version of Quadrant are you running? Looks weird!
[Samsung Galaxy Nexus] ratson:
I run #17 with 1.5OC without any issues for a few hours now, it is doing great on my phone with AOKP #23
[Samsung Galaxy Nexus] blackdub370:
Interactive Gobernor
[Samsung Galaxy Nexus] DaF1974:
That's exactly what happened here with the updated app.
[Samsung Galaxy Nexus] optmkleung:
Antutu down from 5700 to 3700 with same setting 400/1200 turtle, from16.2 to 17. Hang 4 times with 17 when playing games, need remove battery. Back to 16.2.
[Samsung Galaxy Nexus] franciscofranco:
I'm working at the moment to fix the ****, bare with me please.
[Samsung Galaxy Nexus] bradm23:
Franco,

I know awhile ago when you first released turtle you made it so that it was only two steps. CPUspy shows that all of the steps are being used again. I am not sure if this is what you were planning on, but wanted to point it out in case it is an error. I read that gazelle steps are suppose to be back, but did see anything about turtle
[Samsung Galaxy Nexus] lynxboy:
Glad I was able to resist the lure of 1.5Ghz! Sorry to hear that users are having issues with the kernel.

Once again, it seems 13.1 reigns supreme. I think it should be renamed 'Franco Pinnacle' and offered in a way similar to AOKP with the 'Milestone' release.

Seriously, none of the later releases have come close to the performance/battery life I achieve with this kernel, and it's bug free.

Regards.
[Samsung Galaxy Nexus] drawde40599:
Nope setting sticking here new update from market . 400/1500 interactive gov, stock UV settings AKOP Rom . Kernel smooth no reboots or lag of any kind!!
[Samsung Galaxy Nexus] whiteintegsg316:
What is the default setting in this new update
[Samsung Galaxy Nexus] loudaccord:
Haha... Quadrant updated in the market. New version supports dual core phones but I think the number is BS. My Nexus S can get almost 3000 still at 1.45ghz.
[Samsung Galaxy Nexus] rdoane:
Do you or anyone else have a link for 13.1? Want to try it again even though 16.2 is running great for me.

Found one: http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] Qortez1:
With all the new releases for Franco's kernel which version do you guys think is the best, battery life and performance in consideration, to use with AOKP?
[Samsung Galaxy Nexus] loudaccord:
#17

Fastest one yet, works great for me.
[Samsung Galaxy Nexus] franciscofranco:
#17.1 is out as a try to fix the reboots from #17. Need feedback from the users that had problems before.
[Samsung Galaxy Nexus] Elganja:
flashing now
[Samsung Galaxy Nexus] jsuresh:
I didn't had reboots with #17, now I have reboots with #17.1 :(
[Samsung Galaxy Nexus] franciscofranco:
The ****...I'm seriously starting to get royally pissed off at this omap **** cpu arch...

I need LOOOOOOOOGGGGGGSSSSSSSS.
[Samsung Galaxy Nexus] Gahh Its Lee:
Well here's hopefully some good news... Loaded up 17.1 and clicked apply to my UV settings its working great this thing is flying. I'm gonna throw you some money in a week when I can. Unrelated but what's a normal donation amount?
[Samsung Galaxy Nexus] whiteintegsg316:
What's the defaults set at
[Samsung Galaxy Nexus] Elganja:
using 17.1 now... no problems so far, but I don't have good usage time yet to say I have no issues

I did notice one thing in the app... when you click min/max it shows 350 still instead of 400. just a cosmetic thing me thinks
[Samsung Galaxy Nexus] franciscofranco:
Nop, I reverted back to 350 to make sure there are no issues coming from changing the value.

Just re-uploaded #17.1, I had forgot to change the min booting frequency to 350mhz as it was set to 400mhz before.
[Samsung Galaxy Nexus] Antob125:
What exactly is SQlite? What exactly is this device IO that it's speeding up? I'm not sure of the terminology. I usually have francoturtle with hotplug on to give me the best battery life. Will this improve it also? What about turn logger off? What does that do? I checked it because it said it could save battery.
[Samsung Galaxy Nexus] baggy247:
Definitely serious problems with 17/17.1, had a few reboots, last one messed up some data... looking forward for a fix!
[Samsung Galaxy Nexus] Elganja:
i rebooted my phone myself... now it is stuck at the boot screen

gonna attempt to retrieve from backup
[Samsung Galaxy Nexus] heo_con184:
I've had no reboot at build #17.

I'm going to install the build #17.1 and feedback to you guys.

Thanks Franco.
[Samsung Galaxy Nexus] franciscofranco:
#17.2 is up. Original DCC behavior is enabled again. This will seriously diminish the amount of users that can work with 1,5ghz, but stability > everything. Please users with previous issues flash this one. Sorry and thanks for all the testing, thats what nightlies are for.
[Samsung Galaxy Nexus] Gahh Its Lee:
If I have no issues is it worth it for me to use 17.2?? I'd prefer to have 1.5 available and usable incase I need it when using s game or something.

Edit if possible I'd like to see 400 MHz again
[Samsung Galaxy Nexus] MYAbln:
soo with 17, i had manyyy crashes...but with .1 still nothing! :D thanks for the fast fix...but however i send my logcat with 17.1 to you by PM! You deserve it! :D:D:cool:

regards,

MYAbln
[Samsung Galaxy Nexus] heo_con184:
So fast, my phone just reboots after flashing build #17.1 and 17.2 is already up.

Thanks.
[Samsung Galaxy Nexus] Elganja:
restore was successful, will try 17.2 now
[Samsung Galaxy Nexus] deezid:
FINALLY

color multipliers!!! :D

Missed this setting (was using it on my Galaxy S with Voodoo Color all the time).

Here are some values which are looking good in my opinion (will test them the next few days):

R G B

Multiplier (sys/class/misc/colorcontrol/multiplier)

2044318071 1864318071 2154318071

V1 Offset (sys/class/misc/colorcontrol/v1_offset)

-4 0 4

Now I'm only missing a saturation (oversaturated colors) and gamma control (dark greys are lifted...) :D

Edit: phone crashed -> will try #17.2 now ;)
[Samsung Galaxy Nexus] Niksko:
Flashing #17.1 now. I had reboots with #17, and I just got a reboot while booting on #17.1, but my apps are now upgrading.

I was also experiencing really poor cell signal on #17. Pretty sure it's related to the kernel as everything was fine before flashing #17 this morning.

EDIT: Flashed #17.2. Seems more stable. Also, signal issues seem to be purely cosmetic and may be unrelated to the kernel.
[Samsung Galaxy Nexus] nikulogical:
what does francoturtle boot at on 17.2?

i thought 400 min was perfect on 16.2
[Samsung Galaxy Nexus] Elganja:
350 is what mine says
[Samsung Galaxy Nexus] bradm23:
Franco thanks for your hard work. For what's it worth I loving running and testing your kernels and I have not had a single hiccup, sod, or reboot EVER! I guess my phone is not as picky as others.

Since I have tested every kernel u released, I personally had the most success with battery while using 15.2. 16.2 was also very solid with better performance, and I'm guessing 17 will be the same.

I could use 1.5ghz on 17 but on 17.2 it acts funny with some stalls here and there.
[Samsung Galaxy Nexus] Elganja:
in my 15min of random usage of 17.2 no random reboot (17.0 would not last this far for me)

I also rebooted a few times for good measure and it booted up fine
[Samsung Galaxy Nexus] kimboinatl:
Just installed 17.2. I'm also noticing some stalls here and there at 1500OC.

EDIT: Tried setting my governor to Interactive, still getting stalls. Didn't notice any problems w/ 17.1, going to back off to that version and go back down to 1350OC.
[Samsung Galaxy Nexus] franciscofranco:
Aye, thats normal, very few users will be able to use 1,5ghz without stalls, thats the price to pay to have a stable kernel for 99% of the users.
[Samsung Galaxy Nexus] Antob125:
Anyone?
[Samsung Galaxy Nexus] GchildT:
I'm still using 17. I've been using it for about 5 hrs @ 200-1500. No freezes, no reboots. Played games, listened to FLAC files, made calls. No problems. I tend to get low CPU scores on AnTuTu though. Aside from that, phone has zero lag and is very snappy.

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] kimboinatl:
Thanks. I'll try 17.2 w/ 1350OC and see how it is. It seemed to be doing ok with 17.1, though.
[Samsung Galaxy Nexus] whiteintegsg316:
What rom are you on
[Samsung Galaxy Nexus] GchildT:
A modified version of BIGXIE B9.

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] magn2o:
I've been on #17 going on 8 hours @ 700-1500 with -0- problems. Is there any reason to upgrade to 17.2? My device is flying right now, and I'd hate to get my wings clipped if not necessary.
[Samsung Galaxy Nexus] Seano.:
trying this setting out. looks pretty good.
[Samsung Galaxy Nexus] heo_con184:
What are exactly color multipliers ?

Thanks
[Samsung Galaxy Nexus] drawde40599:
17.2

Phone running great on 17.2 stock settings and 350/1350 interactive gov no reboots . Overclocked to 1500 is stable for everything but internet reboots sometimes ( not complaining just saying ) I was reading the china made GN can handle the 1500 setting better than the Korea made GN ,thru or not who Nos, in time hopefully 100% stable on all GN ( if that's even possible )

Thanks agn!
[Samsung Galaxy Nexus] samizad:
I had no problems with 17. It was stable and fast. Here are some Quadrant results all with Performance governor:

#17 set at 1.5 Ghz: 2948

#17.2 set at 1.5 Ghz: 1016

#17.2 set at 1.35 Ghz: 2638

So my phone loved 1.5 Ghz with #17 but not with #17.2. Not that I care. It is all so bloody smooth and stable with my favourite settings: francoturtle, 700-1000 Ghz, default voltages.

Keep up the amazing work. I was worried your attention would be diverted away from Galaxy nexus and on to Galaxy Note.
[Samsung Galaxy Nexus] MontAlbert:
thanks for these values- looks good- do they stick after a reboot? or do they need to be applied each time?
[Samsung Galaxy Nexus] marc.tulley:
Nice one Franco
[Samsung Galaxy Nexus] monkey hung:
My phone is always freezing when OC to 1.5Ghz on 17.2 so I'm having major problems with that.
[Samsung Galaxy Nexus] sishgupta:
I'm not one to OC really but I was curious about 1.5ghz. Unfortunately my device stalls on it.

Wouldnt increasing voltage at this hz improve this?

Not knowing the Max voltage range on this chip I'm not too keen on testing the theory myself without more information.
[Samsung Galaxy Nexus] stesmi:
It may but would at the same time increase heat and heat is bad. Heat makes it throttle itself to a lower speed.

// Stefan
[Samsung Galaxy Nexus] franciscofranco:
I will probably release a second flavored kernel for the users that can run 1,5ghz like it did on #17 and #17.1. And no dont worry I can multi task just fine =)
[Samsung Galaxy Nexus] ugapug:
I cannot get my phone to boot with 17.2. It hangs at the Google logo and reboots. This is the first time I've had any issues with any version of your kernel. Reverted back to 16.2 and it's fine, but I really wanted to try the new one.
[Samsung Galaxy Nexus] yyz71:
Can somebody please post a zip for 17!! 17.2 locks and freezes my phone 17 ran lag free on 1.5 . Having a hard with this one...
[Samsung Galaxy Nexus] monkey hung:
How the hell did you get this? With aokp 23 and 17.2 at 1.35 Ghz I still get about 2500 in a quadrant score.