yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sluflyer06:
Its not that its not smooth running, but isn't running at 1200 so much gonna impact battery life more than we'd want?
[Samsung Galaxy Nexus] SS2006:
Would be cool if you can increase volume and increase auto brightness in this kernrel so I dont have to flash 3 diff fixes each time: d
[Samsung Galaxy Nexus] minooch:
If you have your rom on your sdcard as a zip. Just flash it again
[Samsung Galaxy Nexus] Grims:
First thing I tried, didn't work.
[Samsung Galaxy Nexus] Unoid:
I understand, I thought fransico integrated some of cool's OC/UV
[Samsung Galaxy Nexus] JcMalta:
As far as I understand, this kernel is slightly UV'd for battery performance.

Full OC/UV support was removed - mainly for stability reasons - it may return in the future as and when Franco is fully satisfied with its usefulness and stability.
[Samsung Galaxy Nexus] Unoid:
A Very good reason.

It's obviously the omap 4460 metal wise is too unknown , or else we'd be running at 1.9ghz
[Samsung Galaxy Nexus] beekay201:
this file comes inherited from the kernel itself? or from aosp?

i found the same file in aosp tree, project device_samsung_tuna.
[Samsung Galaxy Nexus] superbobup:
i believe it comes from ROM as i can find it in the bigxie ROM zips

EDIT:

not really sure about above statement as franco says he will include .cfg file in next kernel nightly...
[Samsung Galaxy Nexus] jbdan:
nvm finally found what the .so file is!
[Samsung Galaxy Nexus] beekay201:
if i remove that line from egl.cfg in the source and compile, i get bootloop. doesn't even go to boot anim, stays at google screen. just reverted the change and no more bootloop.
[Samsung Galaxy Nexus] franciscofranco:
Sometimes I wonder if Google developers codes Android whilr being drunk...
[Samsung Galaxy Nexus] offenberg:
Is anyone using this kernel with bugless beast?
[Samsung Galaxy Nexus] beekay201:
lol

ya think? who can blame them?

"bugless"? there's no such thing.

edit: formatting text/blanks
[Samsung Galaxy Nexus] stevonyc35:
works fine for me using Pete's BB.
[Samsung Galaxy Nexus] offenberg:
Its the name of the ROM. So. You are a liar.
[Samsung Galaxy Nexus] Andrmgic:
I have been and it works well..

However, I'm getting about twice the battery drain (around 2% an hr vs 1%) with franco's kernel vs the stock kernel..

Battery detail screen -

Top-level battery info screen -

Better Battery Stats Kernel Wakelocks -
[Samsung Galaxy Nexus] zenzip:
brightness around 50%?

I'm using hotplug governor and batterylife is good but not amazing...around 20h with 2h of screen_on.
[Samsung Galaxy Nexus] drawde40599:
133, 512 retry

Build133, 700/1200 on demand, battery is crazy good so far, 4.5 screen on yesterday, today, I've been reading the news for the last 35 min, and it hasn't moved from 98% WOW very nice, normally I loose the first 15% within 30 min then battery slows down, im stuck at 98 liove it!!!! (Stock voltage working great here no " artifacts" or whatever there called, smooth as hell no glitches, lag or anything else 133 is perfect!!! GPS on, data on, screen 80%, sync on, stock battery
[Samsung Galaxy Nexus] relax24:
35min of screen on time and it hasn't moved from 98%??? What brightness setting? And are you using generic hotplug?
[Samsung Galaxy Nexus] spaceman860:
R133 is going to be my milestone 3 great job Franco :thumbup::D

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] Remoteconcern:
That won't be a genuine battery reading, something has gone awry there!

You can't get 35 minutes of screen on time for nothing...
[Samsung Galaxy Nexus] relax24:
exactly what I was thinking. When my screen is on, I can visibly see the battery percentage dropping
[Samsung Galaxy Nexus] nth0814:
Anyone have a uv setting to share?
[Samsung Galaxy Nexus] drawde40599:
I dont use that hot plug stuff, setting r like I wrote screen 80%, and to reply to the next 2 or 3 posts yes I am lying I'm just trying to show off my big battery wtf!!! I've never seen battery act like that on this phone but its normal on my gs2 .... but agn I'm a liar o_O . But I did just speak too soon cuz I just had a sleep of death
[Samsung Galaxy Nexus] relax24:
Noone was calling you a liar...just saying your stats look inaccurate. Precious much?
[Samsung Galaxy Nexus] theMaDHakkeR:
Just noticed that I'm still getting high core and Iva uses. Tried 7xxMhz min and 3xxMhz min with on demand and interactive but its not doing anything.

Running latest CM nightly with r133.
[Samsung Galaxy Nexus] bjames2785:
On every governor except conservative my phone constantly ramps up to max freq then back down to min. This happens even when im not using the phone. Can anyone help me figure out why this is happening. I have better battery stats and i dont see any abnormal wakelocks. Any help is appreciated

Kernal: Franco kernel r133

Rom: MIUI V4 2.4.6
[Samsung Galaxy Nexus] drawde40599:
Naw there correct I even did a reboot for u guys, yes it don't seem normal but seriously both my euro and at&t do this so ...... Precious??? Hmmmm?? I don't understand, but thanks beautiful:)
[Samsung Galaxy Nexus] asim0:
Hi franco, I noticed that the (nightlies) changelog is not scrollable in you app;

Sorry if it's been reported already (1200 pages :eek:)
[Samsung Galaxy Nexus] Turbii:
Auto ;)
[Samsung Galaxy Nexus] stereoprologic:
Everytime I see someone write "kernal" instead of kernel it makes my eyes bleed.

r133 seems great so far - I'm expecting at least 4 hours of screentime on automatic brightness, 384 - 1228 MHz ondemand, Generic Hotplug, light usage, mostly WiFi. Can't wait for the next Milestone :)
[Samsung Galaxy Nexus] svan71:
Sick

I installed 1.33 on Bamf 1.1 and the speed is ridiculous...
[Samsung Galaxy Nexus] GibMcFragger:
Kernal

Kernal Kernal Kernal Kernal Kernal Kernal Kernal

I'm sorry, you were saying? :D

Lol

Sent from Nexus using xda premium
[Samsung Galaxy Nexus] sago62:
We hope not to have written 1200 pages for the kernel's slow :D.... Put gpu to 384 ....
[Samsung Galaxy Nexus] inffy:
Try with BAMF1.2 and it will blow you.
[Samsung Galaxy Nexus] bendirkss:
There's a bamf 1.2? I just said eff it to roms and went to stock, idk how I'll resist bamf 1.2
[Samsung Galaxy Nexus] nklenchik:
Liquid 1.3 fasho
[Samsung Galaxy Nexus] mrcool007:
There's something strange, sometimes i get Big lags with apex launcher it happens when you enter the drawer. I tried other kernels toi see if it was kernel related and it didn't happened with gladOs nor fauxkernel.

There's a simple method o fix the lag. Long press on power button. I have no logs but you can use apex and see.

EDIT: it's not JUST the animation which lags, when you press the drawer button, the animation lags, then everything you do in the launcher will lag for like 10s. Sliding between homescreens, between apps in the drawer etc.
[Samsung Galaxy Nexus] spovat:
.. forgot to say away
[Samsung Galaxy Nexus] loudaccord:
I can't seem to find the answer but is Smartflex enabled by default?
[Samsung Galaxy Nexus] raubkatze:
Yes. But you can disable it using Franco's app eg.
[Samsung Galaxy Nexus] nikulogical:
Use nova launcher.
[Samsung Galaxy Nexus] dwang:
Is blx working properly in r133? I'm still able to charge to 100%.
[Samsung Galaxy Nexus] aleve1983:
133 is much faster than 130 but less smooth for me in launcher transitions
[Samsung Galaxy Nexus] raubkatze:
Absolutely agree. I'm using Nova lately - no any lags at all.

---------- Post added at 10:38 PM ---------- Previous post was at 10:36 PM ----------

With default and Nova launchers on CM9 I have no any lags.

By the way. What build do you use? 512 or 384? If you have lags with 512 try to flash 384 GPU or - http://xdaforums.com/showthread.php?p=24715288#post24715288
[Samsung Galaxy Nexus] schizophrenia:
i actually changed the value of the file using ROOT explorer..

and it appears to have driven away the artifacts..

hope this is an acceptable way
[Samsung Galaxy Nexus] cyanoviper:
so i updated to update-cm-9-20120411-NIGHTLY-maguro earlier today and now the phone keeps dropping wifi when screen off/sleeping. is that a kernel related issue? i set it to never disconnect while sleeping in rom settings
[Samsung Galaxy Nexus] drawde40599:
Lag in SMS came back read this uninstalled apex launcher and fixed, I didn't even think about launcher causing ..... thanks guys
[Samsung Galaxy Nexus] raubkatze:
I'm using CM9 but Skankwich rom - no such issue.
[Samsung Galaxy Nexus] CaspaTheGhost:
What is this sorcery? Franco, you getting all warlock on us again?!!

They are anomalies during visual representation of digital graphics and imagery, aka dodgy looking stuff on your screen! Best bet for seeing them is using your eyes, but on a serious note they will appear during GPU intensive tasks if your phone is that way inclined.

Yep, its called SmartFlex.

Yeah, I tried to use Apex as Nitrozk now has it as the default launcher for Black Exodus, but it lagged like crazy all over the place. Nova performs well so sticking with it.

@Franco

Been on 133 for about 20mins and it definitely feels great performance wise so far. Giving Interactive a try also.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] krazie1:
Just was wondering where is this Liquid 1.3?
[Samsung Galaxy Nexus] mistermojorizin:
correct, and one of the fixes of 133, if you look at the changlog, is fixes to bringb the gpu voltage back down. min is still at 1000, like it was on 130. Much higher than it was on 122. Understand?
[Samsung Galaxy Nexus] theMaDHakkeR:
Im having this also, and using the 512 Kernel. Doesn't matter if i run 384 or 729, Interactive, or Ondemand, AOKP, or CM9. Once in a while i check and they are back to normal, hovering around 840mV same as the CPU, but generally they are stuck at 1076mV for Core & 1000mV for Iva.

Franco, should i be worried about this or are you still looking into it? Ive been flashing 512 & 384 Kernels through your app and all do this.
[Samsung Galaxy Nexus] johno168:
I'm on the new r133, testing interactive on 384/1228 mhz. (512GPU)

I've noticed the responsiveness on my phone (AOKP b31) is slightly better with interactive. I did not use benchmarks to test this but everytime i switched back to ondemand the ui seemed to be slightly less fluid. I'll stick with interactive for now. Battery wise i still need to test it for longer, but i'm guessing it should be about the same or slightly worse than ondemand since the scaling is more aggressive.
[Samsung Galaxy Nexus] theMaDHakkeR:
Just trying to figure out if this is ok for now "safe" or if i should disable smart flex and use my own voltages so its not stuck?
[Samsung Galaxy Nexus] mrcool007:
Well in fact apex launcher lags just with franco's kernel. I don't know what is causing it. And i posted to help him to make a STABLE kernel for everyone.

Uninstalling apex is not a fix
[Samsung Galaxy Nexus] dwang:
I just tried it and apex launcher doesn't lag for me with r133 and cm9. Drawer is fine as well.
[Samsung Galaxy Nexus] Booker-T:
Is smartflex enabled by default ?

If not, how can I turn it on without the app?
[Samsung Galaxy Nexus] Nitemare3219:
Is there any difference between using SetCPU and the app CPU controls?

Is there any need to change min CPU to 700~ when using hotplug?
[Samsung Galaxy Nexus] raubkatze:
http://xdaforums.com/showpost.php?p=24728626&postcount=12005

But it's called Smartreflex - not Smartflex
[Samsung Galaxy Nexus] drawde40599:
Oh I understand, I can read just fine, the voltages r lower no were did he say he was bringing back to 122 ..... so while u sit there and stare at voltages I'm going us my phone and not worry petty ****

.... Understand??.... Btw I'm sure u will have some dumb **** to say in reply but I'm not gunna waste anymore of my unlimited data plan with u . : )
[Samsung Galaxy Nexus] raubkatze:
Unfortunately Apex lags not only with franco.kernel. I had minor lags (same as on franco.kernel) with CMPlus.
[Samsung Galaxy Nexus] theMaDHakkeR:
Not talking about the other guy but my only worry is that i don't want my GPU or Iva core to take a beating at a higher voltage constantly. It not that I'm sitting looking at the core voltages but just have some concern.
[Samsung Galaxy Nexus] raubkatze:
What reason to use SetCPU if you have installed Franco's app? But I think no difference.

No it is not needed. You can set 729 for more performance if you need it)
[Samsung Galaxy Nexus] drawde40599:
512 gpu? Try in and out of SMS screen, were I'm getting lag its happening with nova also, ima try different Rom later .... been going on, on everything after 121 build don't not if its the kernel tho ...

---------- Post added at 01:42 PM ---------- Previous post was at 01:37 PM ----------

Franco said back 100 pages ago not to worry about it,but I get what ur saying tho....
[Samsung Galaxy Nexus] dwang:
Yep 512gpu.. No problems with sms either. No lag.
[Samsung Galaxy Nexus] raubkatze:
I tried Apex with r133 (512) now. There are no serious issues but just minor screen lags as same as I had earlier with other 512 builds.
[Samsung Galaxy Nexus] dwang:
Ok its actually starting to lag a bit after I added a bunch of icons and widgets. Oh well. Back to nova launcher.
[Samsung Galaxy Nexus] jhericurls:
Another day over, now with 133

15 hrs 17 mins

2 hrs 24m screen time

32% left
[Samsung Galaxy Nexus] nklenchik:
Are you using a live wallpaper?
[Samsung Galaxy Nexus] nikulogical:
My drain seems higher than usual with r133 and 350min rather than 700. Thoughts? Wake locks were mostly notification sounds.
[Samsung Galaxy Nexus] raubkatze:
Usually not but just now tried - works fine.
[Samsung Galaxy Nexus] nklenchik:
I was just gonna say live wallpapers lag a bit for me on Apex and Nova. Static ones work just fine.
[Samsung Galaxy Nexus] drawde40599:
Oh I forgot, only happens in portrait mode it's fine in landscape.... I dunno so small of a issue, not gunna worry about its probably the Rom .
[Samsung Galaxy Nexus] jeetS:
Battery life hasn't been that special for me … only getting about 2.5 hrs screen time to a charge (about 12 hrs)

r133, lower gpu, 1344-384cpu

stock gsm battery

foxhound latest rom

data always on

wifi on for about 5 hrs

i'm using interactive governor, I just turned hot plug on ill see how that works tomorrow
[Samsung Galaxy Nexus] Antob125:
Will the next nightly include the fix for gpu for playing games like temple run?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nklenchik:
What was wrong before? To be honest, I haven't had a problem with any of Franco's kernels since nightly 18 or whatever it was back then. All of the newer ones have been an improvement from the last.
[Samsung Galaxy Nexus] stellaryt:
What kind of issue?I play Temple Run everyday,no any problem,no matter which build of franco's kernel.
[Samsung Galaxy Nexus] Antob125:
This is what Franco posted earlier today. I was having issues with temple run glitching and command fixed it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] darrendm:
13h23m and 12% remaining

3h screen on with 50-60% brightness

Interactive with generic hot plug

Wifi mostly

AOKP31 with r133 (384 GPU)

Only weird thing is the constant 1025mV core voltage. Any reason for this? Even on prior nightlies with 512 GPU it was not at 1025mV constantly
[Samsung Galaxy Nexus] drawde40599:
Temple run acts up for me also, upping the voltage that Franco posted helped a lot but still issue, ....
[Samsung Galaxy Nexus] bendirkss:
Is there a secret for that?
[Samsung Galaxy Nexus] hawkye:
echo 1250 1127 962 > /sys/class/misc/customvoltage/core_voltages

This made it a lot better but still have some artifacts in games and Nenamark2.
[Samsung Galaxy Nexus] franciscofranco:
Dont use 512 then, thats why I spend my time building two kernels otherwise I wouldnt.
[Samsung Galaxy Nexus] GibMcFragger:
I love how some people keep asking for fixes and help with artifacts and lockups on 512 when the solution is already readily available. Don't run 512 if your gpu can't handle it.
[Samsung Galaxy Nexus] nklenchik:
I love how people use 384 as the min too when 700 is recommended haha
[Samsung Galaxy Nexus] schizophrenia:
although you are right.

but as one of those who used to be able to enjoy the 512 performance flawlessly and now I can't, i understand they hope the 512 can be tweaked back to the usable state on r133 or later.

I did the echo the voltage thing and i can run 512 on r133 now.

just my 2 cents
[Samsung Galaxy Nexus] Antob125:
Totally agree. I've been running 512 since Franco started it. Sucks that from now on it won't work for us. But like he said the echo thing is a great quick fix. My comment earlier was meant to say I hope the next nightly for 512 has the old voltages so everyone including myself who ran 512 all this time won't have issues.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hawkye:
That is what I am doing. I guess you don't want feedback?

---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------

What the fock you think I am doing? I never asked for a 512 fix. I was giving feedback that the tweak doesn't work either.
[Samsung Galaxy Nexus] vomer:
relax dude... ^ :rolleyes:
[Samsung Galaxy Nexus] triStateMindgate:
Any1 running latest nightly with Skank able to get GTA to boot?
[Samsung Galaxy Nexus] ChongoDroid:
Fixed.

Gear down

Sent from my francoPhone
[Samsung Galaxy Nexus] GibMcFragger:
Lol simmer down. If it's something a simple as a voltage tweak that is causing all the new issues, it can easily be fixed (permanent fix, not just the terminal command he already posted) if and when he chooses to.
[Samsung Galaxy Nexus] bendirkss:
133 results, stock 4.0.4

1.5 hours of screen time

View attachment 998196
[Samsung Galaxy Nexus] heo_con184:
Idle time on r121 - 512 GPU is so much better than on r130/r133 512 GPU.

My phone is actually really fast and responsive with interactive governor.

Thanks Franco.
[Samsung Galaxy Nexus] sishgupta:
Franco,

7DY05847GX116400R

Thank you!
[Samsung Galaxy Nexus] drawde40599:
great kernels

No real issues on any kernel from 121 on '512 gpu ( small glitch here and there from gpu speed not the kernel ( yes my choice other options available .....) battery great 4+ h battery (specialty 133 got longest battery yet ) but something about 121 just seems better, phone seems snapper / cleaner?? . Just some input u probably don't need: ). Thanks for ur time Franco ....
[Samsung Galaxy Nexus] BrUhNiGGs:
Okay, Im new to this kernel and everything and don't really have the time to really research this long thread for the answers to my questions. Sorry to bother or if this question has been asked several times but I'm just asking if it recommended to put 729 MHz as the min frequency rather than 384 MHz (if my device can handle it)

And is the regular nightly kernels GPU speed at 512 by default?

Im running good so far with r133. Liking it so far.
[Samsung Galaxy Nexus] nklenchik:
Yeah 729 is what most of us use I want to say. The voltages are the same for 729 and 350, plus with 729 you can get to deep sleep faster.

And there's a choice between 512 and a 384 gpu if you look.
[Samsung Galaxy Nexus] pewpewbangbang:
voltages are the same for 384 and 729??

384mhz voltage doesn't go lower than 729mhz?
[Samsung Galaxy Nexus] BrUhNiGGs:
Thanks man. Didn't know that they were the same voltages, I thought it would kill battery faster since its a higher min speed. And yeah, the parent directory confused me cause all the 512 nightlies are listed first and there is a folder for 384 GPU kernels.
[Samsung Galaxy Nexus] raubkatze:
CPU voltages are not the same by default for 729 and 384: 729MHz - 1203mV but 384MHz - 1025mV. Voltages are the same for 1228 and 1344MHz - 1380mV.
[Samsung Galaxy Nexus] pewpewbangbang:
doesn't smartflex automatically undervolt them?

Wouldn't it be able to undervolt 384mhz a lot more than 729?
[Samsung Galaxy Nexus] schizophrenia:
it seems to be just that simple that I just used ROOT explorer and tweaked the voltage as suggested by franco and things are working fine.

just hope the new version will be pushed out with that tweak included
[Samsung Galaxy Nexus] raubkatze:
My results using r133 (512)

Skankwich CM9

auto brightness on

max cpu 1344

min cpu 729

no uv

interactive governor

generic hotplug on
[Samsung Galaxy Nexus] bendirkss:
I haven't gotten an answer yet so sorry to bring this convo up here but is there some secret to getting 4+, or even 3+h of screen time? I can't get over 2.
[Samsung Galaxy Nexus] pewpewbangbang:
what rom are you running?

On r121 and liquidsmooth v1.25 I had over 11 hours battery time, 3 hours 30 minutes display time, and 40% battery life left with hotplug governor.

Edit: Stock 1750mah battery.
[Samsung Galaxy Nexus] raubkatze:
No secrets) You can get 4+ or 5+ hours using 2000mAh battery. But using 1750mAh I had 3+ hours lightly:
[Samsung Galaxy Nexus] superbobup:
Really like r133...

3 hour 10 min screen with 7% left

1.5 hour temple run

80% brightness

Wifi all the time

The best part is I only lost 2% in 20min of 3g music streaming :)
[Samsung Galaxy Nexus] GibMcFragger:
That's cool. I know it's frustrating when something is working fine then suddenly stops after an update, and nobody is completely sure why. If it indeed is simply a voltage issue (which makes sense, if your GPU is borderline unstable when overclocked, lower voltages would push it over the edge of stability) it should be easy enough to fix. :)
[Samsung Galaxy Nexus] drawde40599:
If its been a few days and ur not " crack flashing " over and over and u still can't get over 3.5 hours, my suggestion would be few things make sure ur on a 4.0.4 rom a 4.0.4 boot loader ( Google it ) make sure ur on a 4.0.4 radio ( not necessary) but could help ( Google it ) do a FULL! Wipe with format system in recovery, reflash Rom and Franco kernel and see what happens . My opinions my suggestion I'm sure someone disagrees but I get at least 3.75 hours every day stock battery close to 6h with extended Samsung battery....

.......

---------- Post added at 09:55 PM ---------- Previous post was at 09:37 PM ----------

2% in 20 min, ya!!! I was called full of **** this a.m. for similar results:). It dose happen!!
[Samsung Galaxy Nexus] isinisterx:
What governor?
[Samsung Galaxy Nexus] drawde40599:
On 133? I was using interactive
[Samsung Galaxy Nexus] drewlim:
Hells no 350-729 voltage are not the same. 729 has much higher voltage than 350. Even 1228-1344 has much less voltage diff than 350-729. Even franco says 350 works much better with the interactive changes he recently did. Im using 350 with interactive and ive never have much better battery/performance on and off screen. Phone sleeps much faster now. Thanks for the awesome work franco r133 gets my vote for m3
[Samsung Galaxy Nexus] schizophrenia:
i am with you...

when I am on 3G data, if I really have to have a screen on time of over 2 hours, the battery wont' last for more than 8 hours.

For Wifi, it lasts a bit longer like 8 hours to 10 hours

I really dont know why they can have such good battery life
[Samsung Galaxy Nexus] raubkatze:
On my expirience the great battery eaters are screen brightness and cellular network when using combined 2G/3G/H+ mode. 2G only with 30-40% brightness gives me +20/30% battery life... But, lol, I use WCDMA preferred, auto brightness and hight cpu frequency as I want my GNex could look smooth and fly like a bird -)
[Samsung Galaxy Nexus] schizophrenia:
thanks. but I am always on 30% brightness only...
[Samsung Galaxy Nexus] raubkatze:
Try to use 384 GPU OC build with:

min cpu 384 (also you can uv it to 962mV eg)

max cpu 1228

ondemand gov

generic hotplug on

data - 2G only
[Samsung Galaxy Nexus] schizophrenia:
thanks for suggestion

already have 384 uv to late 900
[Samsung Galaxy Nexus] raubkatze:
It's strange... Maybe you have problem with battery health?

Try to discharge battery to 4-5% and then leave it on charging for 5-7 hours. Make it 2-3 times.

By the way one can use adapter with less amperage.
[Samsung Galaxy Nexus] asim0:
I live in a cave with auto brightness :D
[Samsung Galaxy Nexus] raubkatze:
I looked now what amperage has my blackberry adapter. It has 750mA - charges for a little longer but I think for battery it's better.