yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ceejay83:
wait, so what's your question? lol
[Samsung Galaxy Nexus] bendirkss:
Are you guys flashing 384 or 512? Franco what do you recommend?
[Samsung Galaxy Nexus] bendirkss:
Franco wtf happened with 133... I flashed and my phone transformed into thisView attachment 995712
[Samsung Galaxy Nexus] nklenchik:
Okay after like 30 minutes on this thing I have to say its a beast. I don't say this often but milestone potential definitely.
[Samsung Galaxy Nexus] drawde40599:
My bad
[Samsung Galaxy Nexus] schizophrenia:
that's a piece of butter... if you did not get it
[Samsung Galaxy Nexus] drawde40599:
Ahhhhjhhh!!! That's funny I thought was a brick: ). Myyyyyy badddd
[Samsung Galaxy Nexus] mikeandjaimie:
Ditto.. I had a slight stutter occasionally on b130, 133 completely cleared it up and runs unbelievably.. Haven't posted enough yet to tell battery drain, but no doubt It'll kick 130s ass lol
[Samsung Galaxy Nexus] StyxJ:
I'm coming from fuax kernal, and I'm seeing major improvements for battery life, performance, and stability. Thanks for the kernal :).
[Samsung Galaxy Nexus] teiglin:
Sounds like you might have issues with 512MHz GPU. In the app there is a toggle for downloading 384MHz GPU version instead, or you can download it directly from franco's website.
[Samsung Galaxy Nexus] monkey hung:
You did it again Franky ol' pal. This is wayyy better than any kernel out there. Also, 133 is far superior than 130 which caused my phone to be stuttery and ****. 133 is great!
[Samsung Galaxy Nexus] mrfrag1337:
Flashed! i will test interactive governor tomorrow :D Speed seems the same or better than the last nightly but could be placebo.
[Samsung Galaxy Nexus] borneanheadhunter:
weird. probably ROM issue. 130 was super with me. I'm currently on Liquid Smooth 1.25 . what ROM u guys are on the 133? revert back to 130 for the time being and try to look for the prob.
[Samsung Galaxy Nexus] drawde40599:
I had a drain issue with 130, fixed it by flashing Rom and kernel back to back in recovery......try it may work 4 u 2 ... y any different who Nos
[Samsung Galaxy Nexus] wbknox:
r133 rocks.
[Samsung Galaxy Nexus] jeetS:
In reference to your first question. And questions like this belong in the q&a thread

A Google search brought me here

http://icrontic.com/discussion/95140/android-cpu-governors-and-you-setcpu-system-tuner-tegrak
[Samsung Galaxy Nexus] nikulogical:
So is everyone running 350 or 700 min?
[Samsung Galaxy Nexus] drawde40599:
Nm

---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------

I'm using stock settings ATM, I try run stock full day before messing with anything..... so I have " feel " to comparison
[Samsung Galaxy Nexus] nikulogical:
What did stock come with. My settings ate always set to boot.
[Samsung Galaxy Nexus] mistermojorizin:
with r133, i'm seeing really low temps, but still seeing about 1000mV IVA and Core voltages. I remember it used to be lower, in the 840mv range with 122 and older. running stock settings, with hotplug enabled.
[Samsung Galaxy Nexus] drawde40599:
Just uncheck everything u have checked in Franco app or whatever ur using and reboot should setbbaxk to stock.. 384-1228 ondemand

---------- Post added at 08:55 PM ---------- Previous post was at 08:53 PM ----------

Well were on 133 now: ) things change
[Samsung Galaxy Nexus] borneanheadhunter:
What ROM are u using?
[Samsung Galaxy Nexus] SubyWill:
I'm loving 133!
[Samsung Galaxy Nexus] stellaryt:
Just test set 384min or 729min again.

Play Temple Run 5 mins.

When set 384min,time in state: 384Mhz 37%,729MHz 34%,1228Mhz 27%

When set 729min,time in state:729MHz 86%,1228Mhz 14%

Which one could save more battery? Or maybe the difference could be ignored？
[Samsung Galaxy Nexus] kashix:
Is there a way to disable the colour control in the app and just use the one in AOKP? Thanks in advance
[Samsung Galaxy Nexus] raubkatze:
Flashed r133 (512).

1344

729

interactive

no uv

generic hotplug on

Looks very smooth and works great so far. There is no abnormal battery drain when idle that I had on r123 and r130 (512).

Thanks, Franco!

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

Just one way - don't use it)

Simply use color control settings in AOKP.
[Samsung Galaxy Nexus] kashix:
How to? It doesn't overwrite. Everything is overridden in the app
[Samsung Galaxy Nexus] splus:
+1

I'd also like to know this, since the voltages with smart reflex are same for 1228 and 1344 clocks, so it SEEMS that power consumption should be the same?
[Samsung Galaxy Nexus] kashix:
No difference as using same voltages
[Samsung Galaxy Nexus] kashix:
Are most of you guys running 512 or 384? Had artifact running 512 :(
[Samsung Galaxy Nexus] splus:
But I see many people using 1228 CPU clock. If the power consumption is same as faster 1344 then what's the point in using 1228 over 1344 clock at all?
[Samsung Galaxy Nexus] kashix:
Some devices may not clock well with 1344. Therefore retaining 1228 speed for max
[Samsung Galaxy Nexus] raubkatze:
Hmm. I tried on b29 - worked without issues as same as performance settings. Now I can't test it on device with b31 as I flashed CMPlus yesterday.

---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------

Flashed r133 (512) - no artifacts.
[Samsung Galaxy Nexus] kashix:
What did you put for settings in Francisco app in order for performance to override? Thanks mate
[Samsung Galaxy Nexus] sago62:
with buid 133, 512 gpu, cpu 384-1228, interactive + hotplug .... the phone freezes and 3D graphics is terrible .... nenamark2 with 17.5 …..

edit:also with ondemand:mad:
[Samsung Galaxy Nexus] jnr21:
Your phone can't handle 512mhz gpu clock, flash 384mhz version.
[Samsung Galaxy Nexus] sago62:
until yesterday was .... Has anything changed with the latest build? thank:rolleyes:
[Samsung Galaxy Nexus] schizophrenia:
i am having similar thing..

but i have been having 512mhz on r130 without any issues at all
[Samsung Galaxy Nexus] Hjorvarth:
For the first time ever I too experienced artifacts when flashing 512 r133 over 512 r130. 512 versions of this kernel have always worked perfectly for me. I then flashed the 384 version of r133 and the artifacts disappeared. Bothered that I was always able to use the 512 versions up until now, I rebooted into CWM recovery and wiped my cache, dalvik included, and then tried flashing the 512 r133 again. I am happy to report that I have no artifacts now and my phone is performing better than ever so far :) Perhaps those experiencing the artifact problem can try wiping their cache.
[Samsung Galaxy Nexus] schizophrenia:
i did exactly what you did...... coming back to r133 512 after 384, and later on the artifacts visited me again
[Samsung Galaxy Nexus] kashix:
You did wipe both caches?
[Samsung Galaxy Nexus] raubkatze:
My settings for r133 (512)

max cpu 1344

min cpu 729

interactive governor

no uv

generic hotplug on

---------- Post added at 11:02 AM ---------- Previous post was at 10:59 AM ----------

http://xdaforums.com/showpost.php?p=24695244&postcount=11845
[Samsung Galaxy Nexus] schizophrenia:
yes i did.. as i always do.

the artifacts are especially obvious when Nenamark2

it appears on Google Maps too sometimes
[Samsung Galaxy Nexus] latiszm:
I got a strange issue on 512 aswell, always been able to use 512Mhz version, this one, won't even boot, does not even get to the boot animation. The screen goes black after google with open lock logo. Then restarts to get back into the same loop again. 384Mhz is no issues in booting. Will go with 384 until next nightly to see if it will work better by then.

I did wipe both cache and dalvik cache.
[Samsung Galaxy Nexus] Hjorvarth:
It appears I spoke too soon. After playing Angry Birds for 20 minutes I started to see artifacts again, albeit not nearly as bad as they were originally. I am now running the 384 version of r133 which has solved the problem. I am guessing it may be caused by some voltage tweaks that may have been changed in this version which drives some phones over a fine threshold of reliability.
[Samsung Galaxy Nexus] raubkatze:
Strange. I have flashed 512 - no issues with booting.

Try battery pull out.
[Samsung Galaxy Nexus] sago62:
ok yes, but I do not understand why gpu 512 gives problems .... although with 384 is fine!
[Samsung Galaxy Nexus] raubkatze:
Some devices simply can't handle 512 GPU Clock.
[Samsung Galaxy Nexus] sago62:
I understand .... but I do not understand why until yesterday was fine with 512 ...:rolleyes:
[Samsung Galaxy Nexus] latiszm:
I did try battery pull out aswell. Also tried to flash it 3 times without any improvement. r130 on 512 was no issues at all.
[Samsung Galaxy Nexus] RTContent:
Anyone else getting this issue on the latest nightly? Lots of graphical artifacts and very laggy.
[Samsung Galaxy Nexus] raubkatze:
Then problem I think not kernel related.

But you can try to flash other build with 512 GPU OC and test it.
[Samsung Galaxy Nexus] schizophrenia:
as you can see from the previous couple of pages

yes, you are not alone

and a lot of us previously being able to handle the 512mhz, shows artifacts on the r133 512mhz.

i reverted back to r130 512mhz for the time being, without any sort of artifacts at all.
[Samsung Galaxy Nexus] raubkatze:
It's really strange on my opinion, guys, you was able to use 512 and now with r133 have these issues...

What roms and cpu options do you use? I have no any problems using r133 (512) with Skankwich CM9.
[Samsung Galaxy Nexus] kashix:
I had some success with certain builds on 512 and some to no avail on 512. It either works or break, nothing to worry about. Just use 384 if the latest build artifact on you. That's my 2 cents
[Samsung Galaxy Nexus] schizophrenia:
yup, I have always been ok with 512 until r133

and I have always been on AOKP and now on b31
[Samsung Galaxy Nexus] Diger36:
For me: I have the same setup and no problem at all. It works flawlessly on my side. Just bad luck?
[Samsung Galaxy Nexus] raubkatze:
Try to fix permissions.
[Samsung Galaxy Nexus] schizophrenia:
could be bad luck

i tried to wipe cache and dalvik cache

jumping back and forth 384 and 512, 4 times

and still 512 shows artifacts gradually.

then again, looks like more and more people having bad luck like me with 512, from r133
[Samsung Galaxy Nexus] kashix:
You just have a better silicon chip :p
[Samsung Galaxy Nexus] raubkatze:
Probably yes) But maybe someone who has problems now simply didn't observe issues or never thought that has them.
[Samsung Galaxy Nexus] Diger36:
I see that too... For me I had battery drain problems with r130 (without wakelocks) so I flashed back to r123. While a lot of people were having the best battery performance ever. It beats me how these things happen. I see a lot of people here with problems that others haven't. I don't have an explanation. I hope Francisco will have the chance to analyse this and come up with a solution.

I once solved some problems with a clean install of ROM, GAPPS and Kernel, with even wiping my SD by locking and unlocking bootloader. I know it is a little drastic thouhg... ;)

---------- Post added at 10:43 AM ---------- Previous post was at 10:41 AM ----------

True as I myself am not using a lot of heavy graphics. But then again: I see people with their homescreen infected too... :(
[Samsung Galaxy Nexus] itsfozzy:
Boy does my GN not like r133! (512)! It bearly got past the pink unicorn boot screen on AOKP 31 before goining into a SOD. I even had to have two goes at restoring it with a Nandroid backup. For what it's worth, my GN is usually happy with the 512 GPU.

Fingers crossed with the next version Franco.
[Samsung Galaxy Nexus] raubkatze:
I just wrote that someone could have minor screen lags on previous builds but now has serious graphics issues.
[Samsung Galaxy Nexus] andQlimax:
i bough the app, and happy with the nightly 133 kernel..the phone seems smooth and fast than with the stock kernel

just about one thing i'm not sure, the auto-flash perform an hot reboot (screen black soon and reboot, without shutdown), is it safe with possible data corruption or something?

maybe i'm paranoid :D
[Samsung Galaxy Nexus] raubkatze:
Don't worry) No and were not any issues with it.
[Samsung Galaxy Nexus] leelaa:
Kernel working great here 512
[Samsung Galaxy Nexus] AdamZA:
having a bit of issue with wakelocks with the Media Server process again. Kept phone awake for over an hour overnight.

Unlucky perhaps?

Settings:

AOKP b28

r133 kernel

1228 max, 729 min

interactive

generic hotplug on

smart reflex on

Started the day with r130, flashed r133 in the evening. Had problems with media server wakelock on earlier kernels but r130 had solved them.

Managed only 2 and a half hours screen on time.

Screenshots attached
[Samsung Galaxy Nexus] Turbii:
No problems with r133. Trying out interactive governor today.

729/1344 MHz CPU

512 HMz GPU

Testing governors: Interactive (Current), On Demand and Hotplug

Generic Hotplug: Disabled

Wifi Power Management: Enabled

High Performance Sound: Enabled

Smart Reflex: Enabled
[Samsung Galaxy Nexus] vomer:
R133 great so far! 3% battery used overnight....can't ask for a better standby time :D
[Samsung Galaxy Nexus] raubkatze:
Yes. It's cool) Great build!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nklenchik:
Hey Franco last night my sync dropped and I got grey bars... had to toggle wifi. Nor sure if its r133 but just letting you know
[Samsung Galaxy Nexus] bryant_16:
For stock rooted rom, recommended to go 512 or 384 gpu?

Thanks in advance.
[Samsung Galaxy Nexus] kashix:
Go 512 unless your phone can't take it then revert to 384
[Samsung Galaxy Nexus] RensoreK:
This kernel deserves props. Although all of them have been great, this kernel to me has been exceedingly awesome. I have been able to get through an 8hr shift with ~50% battery. This is with repeated constant usage (due to boredom ;) :D). Check the awake times you will see it was awake a lot of the time with the screen coming on often. I would be close to empty normally with that kind of usage. I've switched to Black Ice's Rom (Black Themed AOKP b31) to save even more battery and with this kernel, its AMAZING. Screenshots will give those who want to try, all the info they need =) . Also this is with stock battery and the 512mhz GPU version. No hardware magic.
[Samsung Galaxy Nexus] franciscofranco:
I think I know why some of you cant run 512mhz gpu anymore. I will post the possible solution in a sec, boarding the train now.
[Samsung Galaxy Nexus] inffy:
is Interactive now the recommended governor with r133?
[Samsung Galaxy Nexus] franciscofranco:
It seems to be in a very good place with the merged patches. Lets see in the next days if people keep reporting good things from it. If that happens Ill make it default for Milestone 3.

Users with artifacts with 512 gpu try this:

echo 1250 1127 962 > /sys/class/misc/customvoltage/core_voltages
[Samsung Galaxy Nexus] kashix:
Sorry for being ignorant, how do we go about doing this? With terminal or?
[Samsung Galaxy Nexus] apratomo:
Yep, where else. Terminal on nexus or adb
[Samsung Galaxy Nexus] aleve1983:
When do you upgrade your app for battery saver control?
[Samsung Galaxy Nexus] inffy:
when he has time...geez
[Samsung Galaxy Nexus] raubkatze:
Super build!

It looks really great - 0% for about 1,5 hour )
[Samsung Galaxy Nexus] Remoteconcern:
In the meantime, if you want it turned off, try:

echo 100 sys/class/misc/batterylifeextender/charging_limit

over adb or in terminal.

Hope that helps

EDIT: actually, doesn't seem to be working for some reason, can't look at it now
[Samsung Galaxy Nexus] Antob125:
Are people getting great life with interactive and hot plug? Cause I tried interactive alone and its not great for me. On demand still reigns king.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
If this is the case...will you explore the option of making the hotplug governor based on interactive too?
[Samsung Galaxy Nexus] schizophrenia:
done and running Nenamark2 without artifacts
[Samsung Galaxy Nexus] raubkatze:
Now using interactive governor with generic hotplug.

1334 729 no UV
[Samsung Galaxy Nexus] franciscofranco:
Why? I didnt create Hotplug governor, it came in the sources but I left it disabled until I managed to patch this up for not crashing the device with sods and crap.
[Samsung Galaxy Nexus] relax24:
Currently trying r133, interactive governor, 384/1036 mhz, generic hotplug on.

I'm more about battery life than performance...hopefully the reduced max cpu helps.
[Samsung Galaxy Nexus] vomer:
Oh I was not aware of this. I guess it is similar to using interactive with generic hotplug on
[Samsung Galaxy Nexus] yyz71:
Just gotta say this latest nightly #133. My phone seems slicker with this one :)
[Samsung Galaxy Nexus] Mrc527:
I've recompiled the 133 version, with CIFS support too! :D

Look at here:

http://www.kernel-xp.net/index.php/en/progetti/20-galaxy-nexus-kernel

I hope it helps.

Bye!
[Samsung Galaxy Nexus] Hjorvarth:
Hi Franco, your suggestion seems to have worked! This is my experience:

I flashed r133 512 version and rebooted, after clearing cache + dalvik beforehand. When my phone booted I saw artifacts everywhere. I opened the a terminal window and used the command you suggested. I then rebooted. When the phone had reloaded, I noticed the artifacts were still there, and were very bad. I re-opened a terminal window and applied the same command. This immediately made all artifacts disappear and I am currently running some GPU-intensive tasks to see how the phone holds up.

The bottom line is the voltage adjustments seem to have worked, and I can now use the 512 version no problem (so far!). Would I be correct to say the command must be entered upon every boot?
[Samsung Galaxy Nexus] Antob125:
I haven't played temple run since I flashed 133 yesterday but I just tried and it is go itching and lagging like crazy. Mean while phone interface itself is smooth? What can it be? I've tried each governor and I'm set at 729 1229 512gpu. I never had issues on previous builds.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Remoteconcern:
Try the 384mHz GPU version. Franco seems to have lowered the voltages for the GPU in this nightly, with the effect that some people can no longer run 512 effectively, even though they could before.

That, or enter the command which franco posted a few posts up in terminal or adb.
[Samsung Galaxy Nexus] raubkatze:
Try to flash 384 GPU build or this - http://xdaforums.com/showthread.php?p=24715288#post24715288
[Samsung Galaxy Nexus] Antob125:
So just type :

echo 1250 1127 962 > /sys/class/misc/customvoltage/core_voltages

In one line in terminal emulator?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Antob125:
What are artifacts and how do you see them?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raubkatze:
Yes in terminal or adb.

---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------

eg - http://xdaforums.com/showpost.php?p=24708640&postcount=11920
[Samsung Galaxy Nexus] Antob125:
Thanks it worked awesome! I'd like to know like the other guy if we have to write command in Terminal on every reboot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sago62:
is there a patch to solve the problem cwm 512?
[Samsung Galaxy Nexus] kashix:
I think what he meant was, is it possible to come up with a .zip to flash in cwm to rectify the issues of artifact on 512 for some of us here.
[Samsung Galaxy Nexus] jnr21:
I have huge artifacts with 512mhz kernel, can't even enter pin code. I will try if i can adb that code and see it it worked.
[Samsung Galaxy Nexus] franciscofranco:
Not from me. Only possible thing is to create an init.d with that command so it stays on boot.
[Samsung Galaxy Nexus] sago62:
Yesss...
[Samsung Galaxy Nexus] sago62:
Will be Choir the next build?
[Samsung Galaxy Nexus] pewpewbangbang:
I've been running 512 fine. No artifacts. Only problem I had was when quitting out of temple run, it got stuck on the screen. Became like the wallpaper and couldn't fix without reboot
[Samsung Galaxy Nexus] Turbii:
Just a little report back. I've been using:

r133

729/1344 MHz CPU

512 HMz GPU

Governor: Interactive

Generic Hotplug: Disabled

Wifi Power Management: Enabled

High Performance Sound: Enabled

Smart Reflex: Enabled

AOKP B31

And it's good, really good! Normally my phone is nearly drained when i reach 2 hours of screen time. But today it isn't (50% left). Can't say I've been using my phone different or something.

Flashed r133 this morning and set Interactive governor. (normally On Demand)
[Samsung Galaxy Nexus] jimyen:
You need to have adb or the sdk, boot your phone into bootloader, connect your phone with you PC, in command prompt, type fastboot flash boot boot.img, assuming the boot.img is in the same folder of your fastboot-windows.exe.
[Samsung Galaxy Nexus] franciscofranco:
It's out for an hour already :)

Download the .zip, go to recovery and flash it. Or use fastboot like the user above me described.
[Samsung Galaxy Nexus] stickjohnonaah:
Edit: not sure what I did here lol
[Samsung Galaxy Nexus] stickjohnonaah:
I must be missing it I can only find the boot image for lte not the zip
[Samsung Galaxy Nexus] franciscofranco:
Fixed, I mistakenly uploaded boot.imgs instead of the .zip packages.
[Samsung Galaxy Nexus] stickjohnonaah:
I appreciate all your hard work. Going now
[Samsung Galaxy Nexus] stickjohnonaah:
I don't know if I'm doing something wrong here. I install this just like I install a rom right? The zip package installed and then I rebooted and got stuck on the Google screen. I did a battery pull and went back to recovery to reinstall mikes rom over the top to change back to stock kernel.
[Samsung Galaxy Nexus] franciscofranco:
I used the boot.img you posted few pages back :confused:

Try to install via fastboot, if it works then it's something on the flashing script.
[Samsung Galaxy Nexus] bigxie:
Maybe I just have a weak chip, but mine doesn't seem to like 1.4GHz. It stutters and lags (thermal throttling?)

Everything goes back to normal at 1.2GHz though. Maybe in the next version you should set the boot frequency to 1.2GHz, and those who want to OC can manually set it to 1.4.
[Samsung Galaxy Nexus] JTECJ:
I've been using this for a day or two and its rock solid, loving it. A quality kernel for a quality device!
[Samsung Galaxy Nexus] Andrmgic:
I find the device getting quite warm with this kernel.. but it has always gotten warm for me when doing intensive tasks anyway.. so I'm not 100% sure if the kernel made it hotter than usual.. but it is noticeable.
[Samsung Galaxy Nexus] stickjohnonaah:
I will have to download sdk tools and adb and figure out that part of flashing tomorrow
[Samsung Galaxy Nexus] JCUK89:
Mine too does not work properly with the 1.4Ghz. How can I change it back to 1.2? THANKS.
[Samsung Galaxy Nexus] kfjunky:
Get a cpu setting tool from the market.

I recommend no frills cpu control.

Cheers
[Samsung Galaxy Nexus] nbeebe24:
My phone doesn't like 1.4. It starts to become unresponsive and laggy
[Samsung Galaxy Nexus] BlackDino:
Its definitely a lot more toasty,

no issues other then the phone getting quite hot.

Might down clock the CPU so it doesn't get so hot

Also voltage control is the best, it is also ics ready
[Samsung Galaxy Nexus] SS2006:
theoretically with kernels like this, and at 1.4 ghz

will battery life worse then stock
[Samsung Galaxy Nexus] mike1986.:
Mate keep in mind that lte probably use different zImage. So we need to wait for lte kernel source.
[Samsung Galaxy Nexus] siedkins:
Any chance of making a version that I can test on Paul's ROM? Or can I do it myself with a bit of guidance? I have come from the world of HTC Desire where obviously things were a bit more developed so I didn't think about flashing a different kernel via Boot.img before. Sorry
[Samsung Galaxy Nexus] franciscofranco:
Maybe...I thought of that too but had to give it a shot.

Unpack his boot.img, unpack my boot.img and replace pauls zImage by mine ;)
[Samsung Galaxy Nexus] gullygossner:
What os is your computer?
[Samsung Galaxy Nexus] theboo7:
This Kernel isn't OC'd atm.
[Samsung Galaxy Nexus] Grims:
Windows 7, it worked when I unlocked the bootloader..I did have USB debugging turned off before I crashed it though..