yashsingh1/xdaforums huggingface dataset:
[Nexus S 4G Android Development] kevincwelch:
Zigg:

Are you still using these voltages?

These are the ones that gave me SODs, etc. Was using Pool Party and franco 11/23/2011.....

It is, perhaps, because I changed the overclock prior to the voltages.
[Nexus S 4G Android Development] ZiggSVO:
Yep. Running strong since then. It is possible that would happen. You should always raise your voltages before over clocking. Some phones just need more voltage than others. I would raise them, then oc, then go back and test for stable voltages.
[Nexus S 4G Android Development] JohnCorleone:
Strange because I changed live OC to 110 before I saw your post and it worked flawless. I was still on first version. How do I miss these updates. What's Max OC on this kernel? Can you go to 130 or 140 on live OC? Testing in two phones I miss things. I am using MathKid's latest but I like to try everything.
[Nexus S 4G Android Development] ZiggSVO:
Stone phones play nice without raising voltages...but if it's set to set at boot and your phone is always rebooting or freezing. No telling if you would have to wipe and reflash to fix it. Always better up be safe :p
[Nexus S 4G Android Development] jdh10475:
Is there anything that makes a kernel different for a NS4G vs a NS?
[Nexus S 4G Android Development] ZiggSVO:
Yes some kernels are and some aren't. Always check the OP of a thread for specifics and flash anything at your own risk :p
[Nexus S 4G Android Development] lackonne:
I have random reboot with latest kernel so I back to 17 Nov version

All setting is by default
[Nexus S 4G Android Development] rahadianfreedom:
My Nexus S 4G running well with franco latest kernel :)

Really happy with the kernel and never had any restart...

Maybe each phone has different problem
[Nexus S 4G Android Development] kevincwelch:
Having trouble...

Not sure what more I can do to tweak this kernel.

Currently running Pool Party 1.5 and 11/23 release of franco. I'm basically back to stock voltages.

I found that using lazy and screen off max frequency options were not good with my phone...basically had to pull the battery a couple times per day due to SODs.

Wasn't able to overclock to 110/880, even when I played with the voltages. I got plenty of phone freezes with the phone in use.

So far, I have been running 11/23 with ondemand and 100/800 with deep idle on. Battery life is fine, but I've been running only for a few hours since the last SOD when I changed from lazy to ondemand.

Tried doing a wipe x3 and nandroid backup of the last franco (11/17) and then flashing 11/23. Still encounter the same problems.

May go back to 11/17.

Have been using reset_NSTools as well.
[Nexus S 4G Android Development] franciscofranco:
First increase your minimum frequency to 200 or 400, I recommend 400. Then don't play with the voltages if you have SOD, just let them be stock. Tell me if it fixed.

A new testing release is up in the FTP server.
[Nexus S 4G Android Development] kevincwelch:
Fixing 11/23

I set the minimum to 200, but that didn't go the trick unfortunately..... I'll give the 400 minimum a try.
[Nexus S 4G Android Development] grifforama:
Amazing kernel. Amazing battery life.
[Nexus S 4G Android Development] wild1z:
Have you tried to install fresh 1.9 with no nandroid restore to see if you can replicate the same problems?
[Nexus S 4G Android Development] kevincwelch:
Haven't tried that....probably won't unless I can't pin down the problem. I have a feeling it was the lazy/max freq screen off issue. I haven't had the problem with GLaDOS 1.9 set to ondemand 100/1000. If this works, may try francos latest with the lazy governor again but turn off the screen off max frequency. I'm using stock voltages in all my settings.

Maybe it's Pool Party? Maybe it's my phone? Dunno yet.
[Nexus S 4G Android Development] Tiffany84:
Hi, I've got a question. I just picked up a nexus s 4g cause I wanted to check out ICS and I was using aosp's ICS rom and your 11/25 ICS kernel. When I first flashed your kernel I could not get over at how good it made the colors look on the phone. Then I decided to try your 11/26 release and it doesn't seem like the colors are as good. So I'm just wondering if something changed or if there's something I can do to make it look the same? Regardless you did an awesome job. Thanks.
[Nexus S 4G Android Development] method2madness:
Just download Voodoo Control (if it's not already installed) and you can adjust the colors to your hearts extent. There are even lists of what setting people think works best with the NS4G.

This is what I have mine set at:

COLOR PROFILES

Original <2.3.3 rating 3/10

RGB MULTIPLIERS

RED: 2238777950

GREEN: 2078663420

BLUE: 2714180800

GAMMA

RED -14

GREEN -17

BLUE -18
[Nexus S 4G Android Development] Tiffany84:
Ok. Thank you for the quick reply.
[Nexus S 4G Android Development] method2madness:
No problem. :-)
[Nexus S 4G Android Development] snrbobo:
WEW!

hey thats great stuff man!

do you have any special settings?
[Nexus S 4G Android Development] kevincwelch:
What was your screen on time?
[Nexus S 4G Android Development] ZiggSVO:
How's this for screen on time :p
[Nexus S 4G Android Development] corythug:
Jesus, nice. Any uv?

Follow the leader @corythug ;)
[Nexus S 4G Android Development] ZiggSVO:
see below post
[Nexus S 4G Android Development] ZiggSVO:
max freq is 880 and using on demand governor with these voltages.

Running on oxygen.

Those were my settings
[Nexus S 4G Android Development] corythug:
I have similar uv on tuev, plus an 800mhz frequency but it's rare my phone performs that well. Occasionally it'll pleasantly surprised me...

Perhaps ill have to give this kernel some more time in the spotlight.

Follow the leader @corythug ;)
[Nexus S 4G Android Development] ZiggSVO:
Yea I uv'd to teuv levels
[Nexus S 4G Android Development] grifforama:
Not really. 800/200 smartass governor. 30 seconds screen timeout..usual stuff. Just an amazing kernel.
[Nexus S 4G Android Development] franciscofranco:
New version is up, enjoy.
[Nexus S 4G Android Development] belvedere:
Is this more or less the same release as the 'testing' version from 25 NOV? I went ahead and flashed it anyway :D

For a while my phone would freeze at least once or twice a day. I hadn't done a 'Fix Permissions' in a while and it seems like since I did that I haven't had a SoD. Now that I said that I expect my phone to implode, but I guess it's been a good run so far anyway...
[Nexus S 4G Android Development] kevincwelch:
Pretty good, Zigg!

I see you're hooked on Spite and Malice...;)

---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------

Oxygen 2.3.1 or 2.3.2?

Also, what program is that?
[Nexus S 4G Android Development] lackonne:
No more random reboot with amazing bat life, wouw...thousand of thanks for amazing kernel
[Nexus S 4G Android Development] ZiggSVO:
Yea thank my wife for getting me on spite and malice lol.

And i'm pretty sure it was 2.3.1 but I updated to 2.3.2 and battery life was the same if not a little better.

Edit...and that program is setCPU
[Nexus S 4G Android Development] kevincwelch:
Thanks, Zigg.

I haven't updated my SetCPU in a while since I was using primarily NS Tools to change voltages, etc.

I'm gonna give it a go. Last time I changed to 110/880 and changed the voltages, I had problems. Will start with your profile and adjust up if needed.

Installed the latest franco.

EDIT: Ha! Even before I finished posting this, I got a "SOD"... Bummer
[Nexus S 4G Android Development] bearsblack:
Latest ics release is reallll nice. Thanks again!

sent from google ns4g via xda app
[Nexus S 4G Android Development] ZiggSVO:
For what its worth I believer those settings were either the 0811 or 1311 version
[Nexus S 4G Android Development] grifforama:
whoah. not so good for me on the latest.

Had 6 reboots after flashing so far.

Edit. Managed to Flash. Deep Idle doesn't appear to be working for me from the off. Are stats enabled on the latest ?
[Nexus S 4G Android Development] grifforama:
F**king deep idle drives me nuts.

I was running 13th with Deep Idle enable perfectly.

That's when I uploaded my recent battery stats.

I just flashed 25th, and deep idle not working.

Flashed back to 13th Deep idle still not working.

what's going on ?
[Nexus S 4G Android Development] AwesomeTurtle:
Did you install/enable anything between the two kernel installations? Also, did you reboot your phone twice (once to get into recovery to flash the kernel, and again after the first startup of the new kernel)?

I asked myself the latter question because I wasn't getting TOP=OFF numbers either, and that ended up being the solution.

Edit: By the way, the 1125 kernel is awesome. Everything works in half a heartbeat.
[Nexus S 4G Android Development] kevincwelch:
Grifforama,

Don't feel so alone. I would have to say that with the last two versions of franco and the last two versions of GLaDOS, I have been having tons of problems with freezes and SODs (I don't know if they are truly SODs...but they occur after the phone goes to sleep).

Would have to turn on/off the camera before deep idle would work. Occasionally, I would see deep idle reset itself in NS Tools for no apparent reason.

I tried using reset_NSTools, and this didn't fix the problem either.

I was getting so many crashes that I did a fresh install of Pool Party, booted up with the stock kernel and then went back to reflash franco 11/25.

With deep idle off, these are my settings: deadline, ondemand, 100/800, BLN off, stock voltages.

Running fine. No "SODs." No freezes...but no deep idle either. Idle battery loss is acceptable: 3-4% per hour.

Colors are rich with 11/25, but I installed voodoo to increase the contrast a bit.

Waiting to see if it was the deep idle issue that caused my crashes.

---------- Post added at 03:55 AM ---------- Previous post was at 03:51 AM ----------

I did reboot the phone, but not strictly for that purpose. I did it to create a nandroid backup. Wasn't precisely after the first boot after the kernel install.

---------- Post added at 04:02 AM ---------- Previous post was at 03:55 AM ----------

OK.

So I reboot the phone again and used reset_NSTools to wipe the data. This time when loading up NS Tools, I was able to confirm that I could actually set deep idle. After doing so, I put the phone into sleep mode. Checked it some minutes later -- no deep idle stats (TOP=OFF).

Launched the camera and then closed it.

Turned the phone off for a few minutes then went back into NS Tools...TOP=OFF was active!

So, it appears that it is now working again. Just will have to see whether the deep idle is the cause of the freezes.

May make min freq 200 (max 800) and see if this prevents these "SODs" that I was getting.
[Nexus S 4G Android Development] derekwilkinson:
hey franco, i love your kernels... is there a way you can make a special version for me? i have different preferences
[Nexus S 4G Android Development] grifforama:
haha. Sorry, this just made me laugh.
[Nexus S 4G Android Development] nmoreman:
I am currently running Franco 2.6.35.14 on the asop ice kernel. I just downloaded tis morning and everything is running great.

I just wondered if this would be a better kernel to upgrade to since you are constantly tweaking and improving day by day.

Thanks
[Nexus S 4G Android Development] zyrtek69:
Just tried out the new kernel and when ppl call me they can't hear me,any solutions?
[Nexus S 4G Android Development] info[]box1:
Need more information like what rom are you using? Which of Francisco new kernels gingerbread or ice cream sandwich?

That's only if your post was a request for some help, not sure.
[Nexus S 4G Android Development] zyrtek69:
Lol whoops.. I'm on aosp ICS, its Franco's newest kernel 11/29. No overclock , deep idle off
[Nexus S 4G Android Development] info[]box1:
Install voodoo setting from market and disable hi-fi recording. If that doesn't help then try fresh wipe and install. I had your same setup rom+kernel and didn't have that issue. Let us know how that worked out.
[Nexus S 4G Android Development] zyrtek69:
Thanks for the quick reply brotha!

I used a buddies fone and called myself before I made a big hoopla and evidently it was just a reception fluke earlier.. false alarm sorry guys ;)
[Nexus S 4G Android Development] zyrtek69:
I mean come on Franco u should do it, this Kat drives a Saab!
[Nexus S 4G Android Development] SA-07:
Derekwilkinson would be happy with that! Isn't that right derek? ;)
[Nexus S 4G Android Development] derekwilkinson:
lmao yeah it would be great haha
[Nexus S 4G Android Development] Tiffany84:
Love your work. Just got a quick question. Is it OK to use set-cpu with this kernel? Thanks again.
[Nexus S 4G Android Development] belvedere:
As far as I know it is. But now that NSTools has become more all inclusive I imagine not as many people are using SetCPU anymore. I still do.. I have it set the min and max frequency and voltage. NSTools I used to enable/disable some of the extra kernel features like BLX and Deep Idle.

Just user preference really.
[Nexus S 4G Android Development] Tiffany84:
Thanks for the response. I really like ns tools but I've heard people saying that using the live oc has caused some lag and I don't know much about that feature and I've never used the app before I got this phone a week ago but I've always used set CPU and I know where everything is at so I'm more comfortable with it.
[Nexus S 4G Android Development] franciscofranco:
Update is up.
[Nexus S 4G Android Development] TheBurgh:
Think I will go back to GB to run this baby. By far your builds are the smoothest for me. Thanks for all of your efforts
[Nexus S 4G Android Development] ZiggSVO:
Why go back...he has an ICS kernel lol
[Nexus S 4G Android Development] TheBurgh:
Just to try the GB version. I am already running his 12/3 ICS kernel and as expected it is by far the best for me.
[Nexus S 4G Android Development] tcol41:
So I'm really frustersted because in about 1/2 hour my phone uses like 9% battery when I'm using it to browse the internet, download an app ect... ihave syncing off I force stop the background apps running I took fb off I'm using this kernel. I tried to download voodoo and it says my device is not supported too. Any advice will b appreciated. I also have my screen set to 30 seconds. Thank you!
[Nexus S 4G Android Development] Romonster:
9% battery drain in half hour browsing & downloading is actually pretty good.

Force closing background apps won't do anything good to battery life, infact it can drain more battery.
[Nexus S 4G Android Development] AwesomeTurtle:
Maybe he doesn't want ICS and/or ICS as a whole is overrated. Why get a Super Nintendo when the Nintendo 64 is out?

Kernel's a boss, by the way. I was forced into an 8-mile walk home from work (the start of which having my battery at 10% due to having not fully charged it that morning) and this, coupled with deep_idle, kept my phone alive for the whole thing. You best believe I'll be updating this kernel now.
[Nexus S 4G Android Development] kevincwelch:
Try watching your battery over the course of a day or two; then judge the ROM/kernel.

Did you calibrate your battery to begin with?

Are you running a lot of widgets?

Are your programs syncing in the background?

I'd say 10% in 30 minutes is pretty good if you have the screen on during the whole time and are doing 3G (or even wifi) downloads.

On top of that, battery meters aren't exactly accurate and while the battery meter may have said 100%, the actual charge may have been 94-96%...so, a discharge to 91% with that activity may have been pretty good.

The point is that the kernels really optimize the hardware, and the hardware is quite limited in terms of battery life. You can't expect to push your phone and not expect it to respond.

Other options: lower your max frequency. Change your voltages. Change your govenor.
[Nexus S 4G Android Development] tcol41:
I'm still learning about all these things. I'm not running any Widgets, I have wifi and a full 3g signal too, I have syncing off. How do you calibrate the battery? Also I'm not. What to sure which governor I should use. If I lower the Max frequency then do I need to lower the minimum frequency? I really appreciate your help :) I do use fancy widget clocks and the Google widget too.
[Nexus S 4G Android Development] corythug:
I've never calibrated my battery I just give it a day or to so I'll let someone else chime in on that.

As for the frequency adjustments, no you do not need to lower the lower if you lower the highest. Try 800mhz as the highest. Works great for many .I generally use lazy governor if available. Otherwise ondemand is a good mix of battery and performance.
[Nexus S 4G Android Development] grifforama:
I'm already getting bananas battery life from 25nov so I'm excited for this.
[Nexus S 4G Android Development] kevincwelch:
You can get a battery calibration program from the Android Market; I personally like BatteryCalibration by marosige.

I do not think you need to have syncing off, unless you manually check your GMail, manually update your calendar, etc. It doesn't use that much battery.

If you install franco's kernel, the stock settings (frequency, voltages, governor) are just fine. I thought I would get more battery life by using a min frequency of 100 and max of 800, but I've increased my max to 1000 (stock) and haven't noticed any significant decrease in battery life--maybe some. Not practical declines anyway.

Some people may need to set the minimum frequency to 200 since some people have trouble coming out of sleep mode (phone crashes, freezes -- Screen of Death, per se). I've been pretty good with a minimum of 100 if my governor is on "ondemand" and not lazy. I'm using deep idle as well.

As for governors, you'll just have to experiment with them. I've tried lazy, ondemand, smartassv2, performance, conservative (while using my Epic 4g), and interactive. I've gotten pretty reliable preformance from ondemand. Your mileage may vary. Again, out of the box franco's kernel is great, so you may not need to change your settings at all.

I recommend either getting Voltage Control, SetCPU, or NSTools (search for "nstools"). NSTools is more versatile in that it can manipulate all of Ezekeel's modifications. You should also download a CWM flashable utility to reset those modifications by reading this thread. In any event, as you experiment, make sure you do not let the program to apply the settings you make at boot time until you are comfortable with the settings and they aren't causing problems with your phone.

Just make sure you make a nandroid backup and be prepared to have to pull your battery if the phone crashes. This is the troubleshooting phase...
[Nexus S 4G Android Development] grifforama:
17 hours and I'm done. I'm not sure I want to upgrade to the new kernel yet... anyone got as good as this?
[Nexus S 4G Android Development] nmoreman:
Question on new kernel 12/4. I' running aosp v21, stock settings, no tweaks, and have calibrated the battery with light to medium usage.

I'm not getting outstanding battery life, yet, and know it needs to settle in.

The only trouble I'm having is no GPS (which I don't think kernel can fix).

A little laggy on some openings, but loving it, so no complaints.

Would changing to 12/4 from 12/3 help anything? There are no changelogs for these two, just the November.

And I also have no problem waiting a couple of days to see how it works, again no problems, just looking for stability and battery life.

And good writeup above to help explain how it runs.
[Nexus S 4G Android Development] jeffreynothing43:
Sleep of death every time. Bah...anyone?? Ideas?
[Nexus S 4G Android Development] corythug:
Bump your minumun frequency to 200 or maybe even 400
[Nexus S 4G Android Development] Paul627g:
Do a cache/dalvik cache wipe. Otherwise try the other side.. If your using CFS try the BFS...

If that don't work then it could be one of those strange deals where a kernel just doesn't gel well with your device.. I can't run morfic's TUEV kernel on mine, if it does flash it only works for a short period of time before freaking out.. Otherwise I get boot loops on flashing, so I had to start using morfic's TUV instead.

Got to give these kernel guys a big hand, they test em out and get them working on 99.9% of devices out there unfortunately some of us fall into that .1 percent of those that have a picky device...
[Nexus S 4G Android Development] t1n0m3n:
Using Nightly 164, 06112011 CFS Kernel... The colors seem to be washed out looking.
[Nexus S 4G Android Development] Sputnikk23:
yep. Tried both and I wipe dalvik and cache before any flash. :(. I heard such great things about this kernel. Its almost worth flashing another rom and build it up to the themeing I have now + apps (good portion of my market links are broken, gotta redownload anyway), but seems pointless w/ ICS around the corner.

They DO get a big hand. I was more hoping someone had the same combo and perhaps had a solution. :)
[Nexus S 4G Android Development] FL0OD:
I think that is ROM related. Please check the CM Nightly and Kang CM thread as I believe that is where you will find your answer.

Sent from my neXus s 4G
[Nexus S 4G Android Development] FL0OD:
I have almost always run this on Oxygen. I put this together with a couple Kangs and Nightlies with no problems. I guess it's hard for folks to help when others have not had the same experience. You may have to tinker with your "setup" if you want to try it. There's always a full wipe. Sounds like your phone may not be wiping everything and there's still stuff left over. What recovery are you using?

Sent from my neXus s 4G
[Nexus S 4G Android Development] Sputnikk23:
Clockwork 5.20
[Nexus S 4G Android Development] Paul627g:
I would give the full wipe a thought... Might be the ticket...

Otherwise revert back to what I said earlier, just might be a kernel that doesn't play well with your device...
[Nexus S 4G Android Development] solesonfire:
loving this kernel... my phone its basically flying so thanks a lot
[Nexus S 4G Android Development] roadrunnrr:
I switched from franco kernel bfs v19 on p500 to nexus s 4g and what do i find here.....franco kernels!!!!!!!!!!!!! Hell Yeah!!!
[Nexus S 4G Android Development] franciscofranco:
I'm everywhere...

Jokes aside, enjoy your new Nexus ;)
[Nexus S 4G Android Development] FL0OD:
Agreed or try multiple wipes. Clockwork is notorious for not fully wiping caches.

Sent from my neXus s 4G
[Nexus S 4G Android Development] t1n0m3n:
That was it, thanks. This kernel has been super smooth all day. Good stuff.
[Nexus S 4G Android Development] fergie716:
Morfics dalvik wiper for those who want

http://db.tt/A12Fc1FF

Flash in recovery before flashing kernel
[Nexus S 4G Android Development] FL0OD:
Thanks for posting this for other's. I use that everytime I wipe and just sort of do it out of habit. This is a great tool to make sure you are truly clean.

Sent from my neXus s 4G
[Nexus S 4G Android Development] Braneless:
I used to run wipe zips on my Evo until a couple of other devs advised that they can cause more problems than they're worth. Something about not properly mounting drives.

Not sure if there's any weight to that, but I had boatloads of issues with my Evo!
[Nexus S 4G Android Development] FL0OD:
I had a Evo also and I have had zero problems or issues I had with my Evo. I had to try some things that I completely stayed away from with my Evo, because of bad experiences, and I have never been disappointed with the results of of my ventures. I can say before using that wiper I was running into bootloops often and would have to go back and do multiple wipes to fix the issues. BTW Franco said there's a speedy update coming so be watching for that hopefully tonight as the best kernel gets even better.

Sent from my neXus s 4G
[Nexus S 4G Android Development] AwesomeTurtle:
Dammit, francisco. Stop following me.

Back when I first received my LG P509, you were there, makin' cool kernels for that little thing. Now my Nexus S 4G is set to be delivered tomorrow and what's this? You again?!

I've got my eye on you.
[Nexus S 4G Android Development] Ibn Saeed:
I also have Bugless Beast ROM, will this kernel further show an improvement over BuglessBeast builtin Kernel?
[Nexus S 4G Android Development] franciscofranco:
Yes.