yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] slvrarrow:
268 far smoother for me both 384 and 512 than 272 and 273. Scrolling is where the more recent builds have suffered for some reason.
[Samsung Galaxy Nexus] yellowdie:
I'm still debating between Interactive and Dyninteractive. Right now I'm running normal Interactive with my specific tweaks. For those of you who are interested, here's my custom init.d file that I call "Lightning Tweaks." This is specifically for Franco.Kernel. If you've never used an init.d file, just unzip this, copy it to your SD card, then copy it to /etc/init.d. Then open the properties and change the file permissions (I check everything). Then reboot your phone and enjoy the awesomeness!

Everyone is is trying to get their cpu speed as low as possible to save battery, so I see people dropping down to 230mhz, or as low as they can, but honestly, bumping it up to 729 has been incredible! I highly recommend giving 729/1305 a try. (As a side note, I was running 1420 as the max until I just read Franco say that 1420 isn't handled by SR. So I dropped it to 1305 so SR kicks in, but my phone spends most of it's time in deep sleep or 729). LOVE IT!! :D
[Samsung Galaxy Nexus] chugger93:
I dont remember having the WIFI issue where if you let the phone sit idle for awhile and wake it up, the WIFI is trying to reconnect. I always thought in earlier builds, it always stayed on? Is this normal? Just curious. Seems like it would waste more battery if its gotta wake up and reconnect when you wake up the phone.
[Samsung Galaxy Nexus] creeve4:
Considerable choppiness in Nenamark2 with r273 512 GPU. No graphical glitches otherwise. Kernel or phone hardware issue?

The best I can get in Nenamark2 with 512 GPU is 33 fps and 29 fps with 384 GPU. Both seem low?
[Samsung Galaxy Nexus] styr:
Due to some lameass init.d script in my rom that i wasnt aware of, sorry about this :P
[Samsung Galaxy Nexus] franciscofranco:
There are no miracles, this GPU sucks ass.
[Samsung Galaxy Nexus] tuk1maar:
I get 34FPS with 384 GPU....

Roms also make up ALOT for performance. I am right now on MIUI with trinity kernel (franco r268 caused random crashes, will try r273 right now) and got 7.6k points in AnTuTu with 384Mhz GPU and cpu at 1350Mhz. Governor: interactive
[Samsung Galaxy Nexus] M3drvr:
I take it you probably prefer working with the Nexus7 GPU?
[Samsung Galaxy Nexus] nuwan32:
hmmm will definitely try this out. so far, its obviously smoother but gonna see how it affects battery. my 230mhz and 729mhz have only a 100 mV difference, so shouldnt be too bad. but we'll see :)
[Samsung Galaxy Nexus] J-Hop2o6:
This is true. But recent releases dropped in FPS in Nenamark2. I normally got 38FPS with r24X-512GPU and before. Now with the recent releases (I haven't flashed r27X yet tho) its capped/maxes at 33FPS. Anything different between r24X to r26X regarding the GPU?

And I also have an idea for the kernel. Seen another kernel dev working on this, but its called slide2wake. Is it possible to implement slide2wake / doubletap2wake? Would be one of the BEST features for our phone. :fingers-crossed:

---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------

Damn! I can't even past 7100 with Antutu, and I use 1.5GHz OnDemand.
[Samsung Galaxy Nexus] ssglackey:
This kernel is slide2wake compatible, just install Pgm from play store.
[Samsung Galaxy Nexus] mike216:
I would say he loves working with the galaxy s3 GPu:D

I'm not at all impressed with tegra quad core chip,supposed to be 12 core. That's all I'm going to say here on Francos galaxy nexus thread.

268 was so perfect for me I hope 273 is awesome but only time will tell. Will report any findings good or bad. Thanks Franco!

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] ÜBER™:
He actually hasnt touched the GPU clock on his N7 kernel although im patiently awaiting a 520mhz kernel :fingers-crossed:
[Samsung Galaxy Nexus] Blackcrx:
+1

same scrolling lag when web browsing

what is your cpu settings? mine were at 230/1228

I wonder if the scrolling lag has to do with the min freq. I tried setting it to 384 but haven't had time to test it
[Samsung Galaxy Nexus] tobitronics:
What battery performance do you get? And on which franco kernel are you?

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
3+ hours of screen time with either 50% or 100% brightness throughout the day. I didn't screenshot it yesterday, but that was better than I normally get. I was on r268, but just flashed r273, so we'll see how it goes. :)
[Samsung Galaxy Nexus] Hungry Man:
I'm a bit confused about the current GPU settings. Does the franco app still show the right frequencies?

---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------

Why? Just curious. I would think having more steps would improve battery life.
[Samsung Galaxy Nexus] ÜBER™:
It caused stuttering.
[Samsung Galaxy Nexus] Hungry Man:
Oh. Oh well, thanks.

edit: I have to change my core voltages with 273, they're all way too low for it.

edit2: I think I'll stick with 268. With 273 I'd have to bump up my CORE voltage quite a bit.
[Samsung Galaxy Nexus] creeve4:
Thought I would check. Thanks for your efforts to squeeze what we can out of it.
[Samsung Galaxy Nexus] EDNYLaw:
I just want to make sure I get this correct, right now with r273, SR is not affecting 230 slot and 14xx-18xx slots but will calibrate everything in between based on the nominal voltage? If that's the case that's pretty awesome. I'm trying some serious undervolting with SR disabled but if SR feels the need to calibrate lower than my voltages and it doesn't result in a crash, that's great.
[Samsung Galaxy Nexus] jericho7:
I'm now getting graphical artifacts with 273@512mhz, wasn't getting any with the previous versions
[Samsung Galaxy Nexus] ashclepdia:
Ahhhh

I'm glad i can back and read these posts!

Apologies for my misinformation!

Great info to have, thanks for the explanations!!
[Samsung Galaxy Nexus] jcmm11:
512GPU r273 gives me 38.4 fps, and no choppiness
[Samsung Galaxy Nexus] J-Hop2o6:
Really? hmm... Gotta check that out.
[Samsung Galaxy Nexus] leets4uc3:
i have never used an init.d script before.

question, do i need to uninstall the app for the values to change on there own?

i rebooted and nothing changed.
[Samsung Galaxy Nexus] chrisgtl:
Does anyone else encounter lots of stuttering when scrolling down the posts in the xda app?

Wish I could get it to scroll smoothly.
[Samsung Galaxy Nexus] nnnnr14:
Enable force gpu rendering under developer options in settings.

-tapped from my paradigm Franco kernel Galaxy nexus
[Samsung Galaxy Nexus] kyokeun1234:
That's the problem with app itself

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] yellowdie:
Which app? Shouldn't need to uninstall anything. You copy the file to /etc/init.d (if the folder isn't there, just make a new folder and call it that), then press and hold on the file and choose properties. Change the permissions, and check all the boxes that come up. Hit okay and reboot. Once it reboots let it sit there for a min or two (it should only take 30 seconds, but might as well give it a little extra room to work). After that, you should see the values change. Then if you want to uninstall it, just delete the 99LightningTweaks file and reboot. You'll be back to square one. :)
[Samsung Galaxy Nexus] a1exus:
I just updated my GNEX (toro) through OTA to Jelly Bean, seems like it's _MUCH_ faster then it was before))

I now also have root (woot) and I really like to give a "franco.Kernel Updater Free" a try).

I am a bit confused though: when I click download it, it gives me few options such as: Auto-flash Download .zip.

What's the difference? Which one do I need? how do I install it after downloading?
[Samsung Galaxy Nexus] CaspaTheGhost:
I was running 729/1305 way back, while we were still in double digit releases.

After a spell with the S3 (its now gone to phone heaven) I'm back with the Gnex and Franco.

Still rocking 729/1305! Keeping it real... :cool:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tjackbjorn:
Time for some r273 flash! Probably it'll be as awesome as the other versions :)

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] J-Hop2o6:
Thx! Tried it out and it works GREAT! +1
[Samsung Galaxy Nexus] slvrarrow:
Yes. A lot more stuttering with these versus 268
[Samsung Galaxy Nexus] J-Hop2o6:
Just as it says. You can let the app auto update for you or you can download and you can flash it manually via recovery. I prefer to Download it and have a few franco kernels in the folder just in case of any "hickups". So don't worry about the auto-flash part, just download it and flash it via recovery when you're ready.
[Samsung Galaxy Nexus] creeve4:
Differences is manufacturing tolerances on the GPU?

Is GPU performance in any way ROM related?
[Samsung Galaxy Nexus] franciscofranco:
I dont have any stuttering in anything. GPU stuff is being the same as always was. I dont see a reason for any type of stuttering, it was probably always there and now that one or two users that talked about it and now you noticed it.

Try other governors and see what happens.
[Samsung Galaxy Nexus] nnnnr14:
No, DD (droid does) told me a long time ago that all you have to do is enable force gpu.

-tapped from my paradigm Franco kernel Galaxy nexus
[Samsung Galaxy Nexus] garu12:
Yea but then it breaks other apps (ex flipboard goes nuts) so its not for everyone.

Hey Franco is there any reason you don't add vibration support for your kernel? I mean you have everything else. Just wondering as I love to tweak it when I swap over to trinity from time to time ;)
[Samsung Galaxy Nexus] shawnaye:
Hey guys. If I use francos app to under volt too much that it causes my phone not to boot up. What can I do? Is there any zip to flash via recovery?
[Samsung Galaxy Nexus] osm0sis:
@garu12: No problems with Flipboard here.

@shawnaye: Voltages aren't set on boot.
[Samsung Galaxy Nexus] Pkt_Lnt:
Franco's reply.

http://xdaforums.com/showpost.php?p=31547477&postcount=26754
[Samsung Galaxy Nexus] ssCISengineer:
Be really careful! How would you get INTO recovery if it won't boot due to voltage issues.....? See you really need to be careful doing that because that situation could very well happen!

Undervolting sometimes isn't really that much of an improvement on battery life. Smart reflex does a pretty good job on its own. But you're free to do what you like!

Just remember the situation I said above about being unable to even get into recovery. Even if you flashed some file in recovery it wouldn't do much good because you wouldn't be able to get in there to flash anything!

please remember to thank me for e-peen points!

Sent from a Galaxy Nexus between here and there.
[Samsung Galaxy Nexus] shawnaye:
Sorry dude. I meant if I could still get it into recovery. Trickster has a file for his app. Does Franco? Too used to uving on my s2. Know the procedure quite well.
[Samsung Galaxy Nexus] osm0sis:
I repeat... voltages aren't set on boot so that's an impossible scenario unless you force them with an init.d script.

As for recovery, it should always be able to boot since it uses its own kernel, so voltages set on franco wouldn't matter even if you did manage to somehow bork them.
[Samsung Galaxy Nexus] ssCISengineer:
Oh I see what you meant. I got it. I I'm not sure if he does or not.
[Samsung Galaxy Nexus] osm0sis:
Franco, are 1728MHz and 1804MHz somehow getting calibrated? Something odd happening with them, one way or the other. They show as 1425mV and 1450mV respectively in the nominal voltage table, but the Calibrated Voltages page shows both running at 1410mV.

(I'd never run my phone that high, though they seem stable, I was just checking out the new voltage table vs. calibrated and OC'd all the way for the hell of it).

And to those who are feeling r27x is a bit more "stuttery", try bumping up the voltage of 230MHz to around 840mV, since that's what it was SR callibrated to in r268, and report back if that improves things.

Edit: Running interactive, r273 with that voltage tweak feels just as smooth as r268. Same settings.
[Samsung Galaxy Nexus] nikulogical:
This feels so much quicker than the stock cm kernel, its ridiculous.

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] arhung:
After flashed 273, the Wi-Fi always disconnect itself and reconnect itself, it takes 1-2 second to reconnect but with 268, Wi-Fi was alright.
[Samsung Galaxy Nexus] franciscofranco:
Nothing changed on wifi in between.
[Samsung Galaxy Nexus] leets4uc3:
273 is perfect. No issues here.
[Samsung Galaxy Nexus] joeyfong:
of coz it is
[Samsung Galaxy Nexus] decoyknox:
Wow. I just applied your tweak, and I'm not sure if it's all in my head, but suddenly my gnex seems like its flying!
[Samsung Galaxy Nexus] Hungry Man:
Any plans to rework the 4 GPU steps instead of 3? Not sure if it's an issue that can get 'fixed' or if it's inherent to it. It would be really cool if it were possible.
[Samsung Galaxy Nexus] mike216:
Something good changed, my data would drop when I tethered long video's. I it didn't matter what kernel or rom it would eventually just drop data.

Ever since the last two nightlys I haven't had this issue. Don't know if the network improved or Francos just a beast but in either case I sure appreciate it!

Thanks Franco! :)

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] The Gingerbread Man:
That actually stops pictures loading up on xda app. That's the only reason I keep it off. Xda should really fix this concidering nothing new has come around for a long time. You would f thought the nature of xda would allow its app developers to keep it working properly on the newest 2 OS updates :rolleyes::p

Sent from my Galaxy Nexus

---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------

Franco did mention about a voltage for something being increased to help prevent data dropping, looks like its working for you! :thumbup:

Sent from my Galaxy Nexus

---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------

Mine calibrated 230mhz to 840 too, I found 800 worked fine and Lazy for me is working smoother than interactive and seems more battery friendly, perhaps give lazy a try?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] trinhtunglc:
Got battery drain with 268, i'm going to try 273, hope it works well :)
[Samsung Galaxy Nexus] Sayan1987:
Can someone gimme some tips about undervolting?

I know each phone is different, but i find default values a bit high, what do you guys suggest/use?
[Samsung Galaxy Nexus] The Gingerbread Man:
First look at what smart reflex is calibrating for you, then lower each stage gradually and checking stability at highest and lowest speeds until it crashes and then raise by 25 until stable. Or just allow smart reflex to work as it does a decent job already.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sayan1987:
Thanks.

Sry if i abuse of your patience, but i'm new to franco kernel and need some clarifications.

I have the franco app.

If i'm not wrong SR is enabled by default right?

If i go in undervolt menu i find for example 250mhz at 950mv, but if i look at "calibrated voltages" i see mpu voltage 900mv.

So what's the real mv value my phone is using? the one choosen by sr?

And how can i know which mv sr chose for me in other states (1200mhz, 700mhz, etc)?

Disabling sr and setting values manually can save some battery?
[Samsung Galaxy Nexus] bartolinio:
"smart reflex" work without the franco app? :)
[Samsung Galaxy Nexus] mariachi202:
Yes, it's on by default.
[Samsung Galaxy Nexus] mihkohuy:
flashed 273 , sometimes WIFI will drop and also disconnect,
[Samsung Galaxy Nexus] kyokeun1234:
Could you check if "Avoid Poor Connection" is checked under advanced wifi setting?
[Samsung Galaxy Nexus] joeyfong:
Back to r264, more smooth.
[Samsung Galaxy Nexus] CaspaTheGhost:
With regards to the XDA app stuttering, this is due to the app without a doubt. When you scroll you will notice that the scroll bar on the right changes in size and this correlates to the stutter.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
1Yup enabled by default

2 is maximum possible voltage

3 real value is shown in calibrated voltage

4 change your min max speeds

5 possible but not a lot

yes, its from our cpu

Try lazy working good here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chugger93:
What I normally do is goto calibrated voltages with smartflex enabled. Check and see what voltage its given you at specific frequencies. You may have to swipe back and forth fast to get the frequencies up. Take note of them. Now goto OC tab, CPU undervolt and adjust each frequency. Start with what smart reflex gave and adjust downwards until stable.

Hope that helps somewhat.

---------- Post added at 07:41 AM ---------- Previous post was at 07:31 AM ----------

On a sidenote. I'm sitting in Starbucks and am on r272. I only had 1 wifi bar. My Asus tf700 and my friends nexus 7 both had 3 bars.

I figured maybe its the kernel with all these driver updates lately. Decided to flash back to r249 before all this driver shindigs. Now I have 3 bars in Starbucks!! Just an fyi to Franco and friends
[Samsung Galaxy Nexus] slvrarrow:
After 2 reboots the stuttering scrolling I saw with 272/3 vs 268 has gone so most likely app/rom rather than kernel. Apologies
[Samsung Galaxy Nexus] franciscofranco:
Current Wi-Fi driver is the same as r249.
[Samsung Galaxy Nexus] billykxda:
May I ask - what outcomes were you looking for? Brighter white? Less of one color?

Thanks in advance!
[Samsung Galaxy Nexus] mihkohuy:
unchecked certainly
[Samsung Galaxy Nexus] chrisgtl:
I can't help but think #249 gave me the best battery.

My phone always gave me an almost flat line when looking at the battery stats. CPU spy also reported the highest deep sleep ratio.

Im going to give #273 a couple more battery cycles before deciding if #249 is my homebrew milestoneJB.
[Samsung Galaxy Nexus] Culex316:
Device rebooted again when listening to streaming radio o o latest nightly here is kmesg. Stock Rom 1536max interactive sorry about the name I needed to discern ir from other log files
[Samsung Galaxy Nexus] osm0sis:
Best way I've found to get the calibrated voltages is to switch governor to performance then adjust your max to the one you want to see.
[Samsung Galaxy Nexus] eng.stk:
All the Portuguese and Spanish laughed at that .zip filename :silly:
[Samsung Galaxy Nexus] osm0sis:
Franco?
[Samsung Galaxy Nexus] c_86:
Wondering... if its rom or kernel

I'm having rebooting issues... nothing random but whenever I do a regular reboot via power button it reboots fine then 2 mins after reboot is done it reboots again. Then repeats. Unless I pick up the phone as soon as reboot is done and unlock it... then it won't reboot on me... but if leave it and don't touch it... it'll reboot on me...

Thought?
[Samsung Galaxy Nexus] TEK112:
Need logs...
[Samsung Galaxy Nexus] mohaimed:
perfect kernel..havent had any problems so far.
[Samsung Galaxy Nexus] franciscofranco:
I have no idea to be honest.

Some app is making your device reboot for sure.
[Samsung Galaxy Nexus] osm0sis:
So you can reproduce it? Very odd indeed. Luckily it's up in the "crazy person" zone of frequencies. Just thought I'd make sure you knew about it in case it was a code bug that could affect all SR/voltages. :p
[Samsung Galaxy Nexus] B_sHorTy:
Franco, I notice a pretty good screen on time. 2 hours and 45 mins. With all day whatsapp, facebook(webbased, since the app is bad). But my idle time is not that good. After 8 hours i have 20% left. As said. No facebook app. And no gmail push(sync off) but android mail (sync every hour). I am on the latest jellybro nightly. Just want to share it with you. What are your suggestions? I'm running your latest nightly.
[Samsung Galaxy Nexus] franciscofranco:
I only see a GPU driver shutdown [ 8883.779052] PVR: PVRSRVDriverShutdown(pDevice=c789c000)

Try to lower your CPU OC, your device maybe can't handle it.
[Samsung Galaxy Nexus] franciscofranco:
I'll see if I can reproduce it.

That falls into the random **** type of problems. Idle is affected by MANY variables. Make sure you don't have rogue apps keeping your device awake. 3G/4G also drain quite a bit of battery during idle.
[Samsung Galaxy Nexus] B_sHorTy:
Thanks for replying. I van check it with cpu spy or something? If i have good sleeping time?
[Samsung Galaxy Nexus] franciscofranco:
Yes, that app gives you the Deep Sleep time.
[Samsung Galaxy Nexus] chugger93:
I agree with Franco on this one. I'm in the Detroit Metropolitan area and sprints service has sucked for so long. I noticed that with my 3G data on, even overnight my phone drops like 15%. I strictly use WIFI now and turn off 3G unless I'm on the road or somewhere where I need it. Too much of a battery drainer.
[Samsung Galaxy Nexus] hshaikh:
hi franco,

for the next version, could you please add in a sound mod to increase the IN CALL volume, the current tweak works well for the speaker and music, but does nothing for the in call volume.
[Samsung Galaxy Nexus] RevengeFNF:
Here using CM10 Milestone 1, and your last kernel 273(384Mhz version).

Almost 8 hours on Idle, with some use. No problem at all, so your kernel does not have anything wrong.
[Samsung Galaxy Nexus] franciscofranco:
Current Sound Control implementation is only for headset. Always was, always will. In call volume is ROM domain.

Exactly :)
[Samsung Galaxy Nexus] sachilleas:
273 is very nice for me! Only problem is that nenamark freezes my device when i use 512 gpu. Are we close to milestone this time?
[Samsung Galaxy Nexus] osm0sis:
Your device likely can't fully handle 512, use 384 instead. Or you could try one of the following (credit to rogersnm, I think?):
[Samsung Galaxy Nexus] franciscofranco:
Dunno. I'm testing some things with the interactive governor now. More news soon, I'm testing.
[Samsung Galaxy Nexus] creeve4:
Running r273-384 GPU

Seeing this in Settings/Advanced on CNA 3.6.0:
[Samsung Galaxy Nexus] franciscofranco:
Here we go again. CNA is prepared to read GPU frequencies through a custom sysfs interface and be able to change the freqs from userspace (rom). Since I don't have that interface that panel is not reading ****, can notice it being greyed out.
[Samsung Galaxy Nexus] creeve4:
Thanks, I did not realize this had been brought up before... sorry
[Samsung Galaxy Nexus] ChazzMatt:
I'm running AndroidMe ROM v1.4 for GSM Galaxy Nexus, which has a nice add-on volume modification. "HIGH" is the one to go with...

__________________

http://xdaforums.com/showpost.php?p=29485840&postcount=1173

Downloads at that link above.

(yeah, he's up to v1.9, but v1.4 worked so well I never updated past that. v1.6.1 was also a particularly fine vintage.)
[Samsung Galaxy Nexus] franciscofranco:
r275:

* Increase Core lowest entry voltage from 925mV to 950mV for stability

* Add a 10mV margin to 384Mhz CPU slot in case Smartreflex calibrates too much

* Increase priority of Interactive governor Kernel thread. Now it will have more priority than user land (rom stuff) threads. This will increase interactivity by a very nice margin. There are a few drawbacks: CPUSpy type of apps won't be able to track down frequencies anymore, but it will still show Deep Sleep accordingly.

* Add an Interactive governor entry allowing users to change which frequency the device ramps to when a finger touch is detected. By default it ramps to 1036Mhz. Path is: /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq. The app will be updated later to feature this entry

* Several small patches and improvements - check github commits
[Samsung Galaxy Nexus] kyokeun1234:
Dang another update already? Horah! :D
[Samsung Galaxy Nexus] leets4uc3:
275 is great so far. Never had an issue with any recent nightlies tho
[Samsung Galaxy Nexus] Fenvarien:
R275 installed just fine and is running very smooth.

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] tobitronics:
Flashing 275 now, fingers crossed :)

Beamed from my Asus Google Nexus 7
[Samsung Galaxy Nexus] RayGarden:
Please do not forget to Upload to AndroidPIT App Center ;)
[Samsung Galaxy Nexus] nikulogical:
What's the recommended governor at this point in time?

Sent from my PARANOID ANDROID