yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] beekay201:
#259 has been released.

Been running #258 for a day now, seeing less drain while listening to music, less idle drain as well, haven't run into wakeup issues, sod's, signal or any data drop, using default governor interactive device feels as fluid as before, both in transitions and opening apps. Seems it scales fast enough from lowest speed, dont see any lag at all. Cpuspy shows all frequencies have been used, looks normal to me. :)

Sent from my i9250
[Samsung Galaxy Nexus] renaud:
Well, it's there, but you have to click on "All other stable-4.0.4 versions" to see it. It's generally better to run latest version tough, unless you have specific problems.
[Samsung Galaxy Nexus] EVERED78:
Correct me if I'm wrong but r259 would be the newest right?
[Samsung Galaxy Nexus] Gregus59:
Battery Life on r259 is lower than r257.
[Samsung Galaxy Nexus] zurchpet:
R261 in testing is built with the linaro gcc toolchain :)
[Samsung Galaxy Nexus] pedmond:
This should be interesting :D
[Samsung Galaxy Nexus] fireon123:
any good experience?
[Samsung Galaxy Nexus] tibere86:
R261 flashed on CM9. Let the testing begin. So far so good. No lag noticed so far stepping up from 172mhz.
[Samsung Galaxy Nexus] renaud:
Now to be fair, it's compiled with linaro toolchain for quite a while now. R261 just has the latest one.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
I've noticed it in CPUSpy before. :D fugumod always at the front lines!

Tonight, I fully charged the device before going to bed. Left it on 2g all night, no wifi, no data. This is on #258, nightly 20120603. This is how I found it when I woke up.

What kind of usage scenarios are we looking at here? Has it improved over in #261? On #258, I have no issues. Will do more testing concerning battery usage/drainage, with wifi on, and after with data on.
[Samsung Galaxy Nexus] tibere86:
#261 & #264 have been running fine. Coming from other kernels, it seems as if 261 & 264 are running GPU @ 307mhz, correct?
[Samsung Galaxy Nexus] beekay201:
I think this was asked to nika almost when he started fugumod project for the i9250. oh right, that was me!

gpu is not oc'ed in fugumod, afaik. only cpu to 1344mhz (default).
[Samsung Galaxy Nexus] renaud:
Yes, gpu is at default speed. Nobody noticed any real human visible improvement running at higher speed.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rideriang:
Finally! wifi connected...and battery save alot!
[Samsung Galaxy Nexus] franciscofranco:
Nah, thats not true. Its much smoother on thr transitions and animations while using 384mhz. You can even run it on the same OPP as 307 so you wont notice a battery hit.
[Samsung Galaxy Nexus] tibere86:
Agreed. I too notice smoother screen transitions, scrolling, and animations on 384 vs 307. FuguMod r264 is still tops for me in terms of idle battery drain and drain during regular usage...sorry Franco :D (but franco kernel is still fastest smoothest out there)
[Samsung Galaxy Nexus] renaud:
Please try r265 which has 384mhz gpu
[Samsung Galaxy Nexus] zurchpet:
R265 with 384 MHz feels about the same as 307 MHz.

At least I don't see a difference.

Could someone point me to where I can see the difference?

Thanks nikademus for letting us try it anyways :)
[Samsung Galaxy Nexus] Treatcon:
Thank you, I've had ZERO signal drops so far using your kernel for the past 3 days and missed the faster GPU speeds that Franco provided in his kernel. Now everything is as it should be... no signal drops, fast and smooth scrolling! Thank you!! :cool:
[Samsung Galaxy Nexus] tibere86:
r266 running awesomely nikademus! Noticeably smoother. Many...many...thanks!
[Samsung Galaxy Nexus] Gregus59:
Hi Nika, are you using the last Linaro 4.7.1 toolchain for the FuguMod Kernel ?
[Samsung Galaxy Nexus] bigeyes0x0:
a quick "cat /proc/version" from adb/terminal or using CPU Spy should have let you know that.
[Samsung Galaxy Nexus] renaud:
I am using linaro compiler for quite a while now, like r100 or so.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gregus59:
r266 works so smoother with the latest build of CM9.
[Samsung Galaxy Nexus] tibere86:
I'm also running r266 with CM9 and it's pure bliss.

@nikademus - I notice a tad bit of lag in r266 when the CPU scales up from a min of 172mhz (using interactive governor). This lag is gone when I set min to 345mhz. Is there much voltage difference between 172mhz and 345mhz or is the battery savings between the two negligible?
[Samsung Galaxy Nexus] renaud:
Battery savings are noticeable mainly if you are playing music with the phone with screen off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pedmond:
In AOKP Milestone 5, using R264 considerably increased the current during sleep. Reverting to 256 solved that.

I wonder if anyone else noticed this behaviour, or is it just me?
[Samsung Galaxy Nexus] franciscofranco:
Hey nikademus. You've been merging new Wi-Fi drivers from android-omap-3.0 for a long time, yet I haven't seen anyone complaining about Wi-Fi tethering. I have the same drivers that you do and my users complain that tethering doesn't work. Do you know anything about this, or have you encountered this before?
[Samsung Galaxy Nexus] renaud:
My wifi drivers are not a verbatim copy of the stock ones. Feel free to copy my bcmdhd folder if you wish. I remember changing some things early, but I don't remember exactly why.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
Not really clear on what you're saying here.

doesn't really add up from what i can see. Try #264, up min speed to 345mhz.

--------------

Nightly 20120615, Settings > Advanced > General tab > Vibrator feedback tuning

is not available with #267.
[Samsung Galaxy Nexus] franciscofranco:
Hmm. Strange I dont remember you changing anything else besides merging the wifi patches from android-omap-3.0. Im probably wrong though. I will check.
[Samsung Galaxy Nexus] renaud:
r268 (now in testing) includes a modification of Interactive governor which may help bringing better responsivity and increased battery life. Please test and report.
[Samsung Galaxy Nexus] renaud:
I did it when I suppressed 4.0.2 branch.
[Samsung Galaxy Nexus] tibere86:
Flashing r269. Will report back.
[Samsung Galaxy Nexus] zurchpet:
R269 is Linux 3.0.35 btw :)
[Samsung Galaxy Nexus] franciscofranco:
Nice commit on Interactive. I'll merge it and see what my users say about it :)
[Samsung Galaxy Nexus] apratomo:
Pardon me if it's been discussed before. I just flashed latest #269, it seems cm9 gamma setting doesn't play nicely with this kernel.
[Samsung Galaxy Nexus] renaud:
Which release of CM9 do you have?
[Samsung Galaxy Nexus] tibere86:
I'm running CM9 nightly 20120618 + r269 and the gamma control works fine. Did you try fixing permissions after flashing?
[Samsung Galaxy Nexus] apratomo:
Yeah I'm running the same nightly, let me try fix permission. Thanks!

Color control does work but DSS gamma doesn't work. I like my screen a bit darker.

Edit: I just take another stab at it, using 0618 cm9 skankwich and #270. Color control works but gamma setting doesn't work.
[Samsung Galaxy Nexus] tibere86:
r270 is the fastest kernel I have tested as of yet. Everything is super smooth and very reactive. This maybe due to the new Interactive governor. Will stick with r270 for the rest of today to test battery life. Overnight drain is on par with Trinity kernel which has always given me the best battery life. Great work nikademus! Thanks again.

On side notes:

1) I am still running CM9 nightly 20120618 and DSS Gamma Setting does not work where it did on r269. It's not an issue for me, I just wanted to report what I have found such far.

2) WiFi speeds with r270 are the fastest I have experienced on 2.4ghz

Update:

I have been running r270 for a few days now and can say battery life is indeed very very good. Performance is silky smooth. I am running kernel at 1344Max/345Min and have color calibration modded manually. I would not change a thing :)
[Samsung Galaxy Nexus] tibere86:
Update 2:

What would make this even more perfect was if nickademus was on Google+ :)
[Samsung Galaxy Nexus] zurchpet:
He is: nikademus on G+
[Samsung Galaxy Nexus] Think420:
just flashed r273

been hearing a lot of good things about this kernel
[Samsung Galaxy Nexus] rideriang:
Really hope this kernel work with PGM aka slide2wake app :)
[Samsung Galaxy Nexus] tibere86:
I did not see any new commits. What has changed in r273?
[Samsung Galaxy Nexus] renaud:
Sorry, forgot to push, will do as time permits, mostly wifi changes

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
From what I have read about that app, my kernel shouldn't support it and won't support it in the future, sorry. It requires some things I have removed on purpose.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
reporting back: #269 had something going on, was using data in a area with good coverage (i often read the news there, while i'm waiting for the food), and first it dropped the data connection, then took quite a bit to get it back. hasn't happened again since #270.

only minor thing not working on #273 is customization of vibration force.

It seems interactive is better than ever. i throw one app at it, it loads it up. i throw another app at it, and it responds faster. freaking love this.

awesome kernel fugumod is becoming. i gotta say man, you should probably enjoy the summer! :good::laugh:
[Samsung Galaxy Nexus] renaud:
r274 (currently in testing) has major wifi changes, please report your experiences.
[Samsung Galaxy Nexus] hlubepet:
First amazing thing today was my change from sgsII to gnex.. second amazing thing is...... that you are here developing kernel.... I was in love with your kernels on sgs1... flashing right now and will never flash any other than fugu.. cheers!!
[Samsung Galaxy Nexus] franciscofranco:
Seems like a pretty big change. Interested to see the feedback from your users :)
[Samsung Galaxy Nexus] ceejay83:
Is this compatible with pgm?
[Samsung Galaxy Nexus] renaud:
No, it is not.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
What is PGM?
[Samsung Galaxy Nexus] renaud:
Slide2wake

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Think420:
What exactly is the aim of these major Wifi changes?

better battery, better wifi signal?
[Samsung Galaxy Nexus] renaud:
Mostly better wifi.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
If anyone has had bad experiences with my latest wifi commit, please speak now :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ohliu:
Been using r274 with CM9 for almost a day without any hiccups. FuguMod has always been snappy and flawless for me. =) Thanks again for the superb kernel.
[Samsung Galaxy Nexus] beekay201:
Yep, no issues so far.

Sent from my i9250
[Samsung Galaxy Nexus] rashidi_zin:
Works perfectly.
[Samsung Galaxy Nexus] jbeez:
http://www.speedtest.net/android/203136715.png

Good so far
[Samsung Galaxy Nexus] jbeez:
Disregard, my ip changes like twice a year and last night it changed I had to redo my Ipv6 tunnel config at HE to allow my new ip
[Samsung Galaxy Nexus] eezdva:
Hi are you making a JellyBean version ??

Look forward to it. Love ur kernel.
[Samsung Galaxy Nexus] renaud:
There is one in testing, look in testing-4.1 (r279)
[Samsung Galaxy Nexus] renaud:
r282 (for Jelly Bean) is out. It has not been tested yet as I cannot flash JB currently on my phone, please report.
[Samsung Galaxy Nexus] dsprank:
I have been running that for the last couple of hours with JB. So far seems to be good.

I had been using nstools, but in JB I don't have the option to change governors. I also was shown a ? on the max CPU until I changed it manually. Low end frequency was preset.

Seems to run a little smoother than stock, and does have the option to over clock, but that is the only reason to switch kernels.

Not bad for a shot in the dark.
[Samsung Galaxy Nexus] eezdva:
How come?? Should be rather easy?? Or you borrowed ur phone to someone like I did. I had to ask it back for JB :-)

---------- Post added at 02:03 AM ---------- Previous post was at 01:21 AM ----------

Ok with 282 I don't recieve messages anymore and the wifi gets cut as soon as I turn of the screen.

With the stock kernel I do get messages but wifi get's turned off when the screen turns off.

I used ur kernel for ICS because I had similar issues. But I'm sure you'll come with a fix ....
[Samsung Galaxy Nexus] eezdva:
Ok 279 ain't fixing the wifi screen off issue either. Even tried to flash with a 4.0.4 one hahaha but that was of course stuck at the boot screen.

So yeah. Hope you will get JB up and running soon and see what you can change so it works like in the kernels that you made like atleast when IMM76I came out.

Somehow that did the trick

Found this thread. With this widget installed I get normal notifications on wifi.

http://xdaforums.com/showthread.php?t=1625705

But the widget is not the best solution I guess. Also concerning battery life.
[Samsung Galaxy Nexus] renaud:
Is the option to keep wifi on in wireless settings gone on jelly bean? Press the menu when being in access point selection, there is an advanced tab where you can choose whether wifi gets disabled or not when screen is off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
You may have to remove nstools settings, not sure as I don't use it, but with pimp my CPU this is the case.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
OK, I am on jelly bean now. Not even need a wipe coming from stock

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ragnarokx:
Awesome! Always good to test kernels first hand.
[Samsung Galaxy Nexus] renaud:
I confirm the high frequency bug, I will have a look

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] eezdva:
No no it's on all the time :-) Wish it was that simple hehehehe
[Samsung Galaxy Nexus] beekay201:
Wifi doesnt turn off on #282 when screen off.

Sent from my i9250
[Samsung Galaxy Nexus] CMNein:
I noticed this on r279. Only 7 seconds was spent at 1344, the rest of the time at 1036. Seems like 1036 was 'set on boot'.
[Samsung Galaxy Nexus] marshall39:
Thanks , this widget is what I needed the time one kernel does the same thing "natively"
[Samsung Galaxy Nexus] eezdva:
Yeah the ICS version of Fugumod did. I'm sure he will update it soon. In the end this kernel is just the best.
[Samsung Galaxy Nexus] renaud:
Yes, let me some time to figure out the bugs now that I am also using jb. Notice that you still have a newer wifi driver than the jelly bean version.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] eezdva:
Yeah look forward to it
[Samsung Galaxy Nexus] renaud:
It's strange whatever I put in the initrc for frequencies is not respected by the os.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
Now frequencies will be correctly read by the apps (redownload and reflash r282). But there is still something setting max freq to 1200mhz after init, so currently you will need an app which sets max freq on boot or you won't go over 1036mhz. This may be and more than probably is in the rom itself.
[Samsung Galaxy Nexus] franciscofranco:
I had that same problem but didn't found a fix for it nor found anything in the kernel that could be doing it, so strange.
[Samsung Galaxy Nexus] jbeez:
With this smoothness initiative in the ui, not surprised they are putting in base OS instead of more device specific in the kernel.

It may tie into some functions related to smoothness and needs to be toggled on several different event triggers in userland stuff
[Samsung Galaxy Nexus] renaud:
Given the jelly bean version we have is a preview, they probably stuck some device specific code somewhere in the OS. A difference between 4.0.4 and now is the permissions of the frequency sys settings. I guess that making them 444 (or owned by root:root) instead of 660 will prevent the os itself to change the frequency after boot. But this will probably break some apps which expect default permissions.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pmcee:
Please add undervoltage support for JB. The kernel is already awesome but this would be a big battery saver.

Gesendet von meinem Jelly Belly mit Tapatalk 2
[Samsung Galaxy Nexus] renaud:
Smartreflex is integrated

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pmcee:
OK where can i set the voltages?

Gesendet von meinem Jelly Belly mit Tapatalk 2
[Samsung Galaxy Nexus] renaud:
It's automatic

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pmcee:
How about manual control?

Gesendet von meinem Jelly Belly mit Tapatalk 2
[Samsung Galaxy Nexus] renaud:
Frequency bug is solved as expected by my latest commit. If you have an application with no knowledge of basic security which sets frequency permissions like it should not (666) like antutu CPU master pro, uninstall it or you will be forcibly stuck at 1036mhz.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jbeez:
I know you're in jb, and imma let you finish but... tethering no bueno in 275 but it works in 273. Im in ics. Have 2 gnexes next to each other. Can't tether on 275. Flash 273 it works perfect
[Samsung Galaxy Nexus] renaud:
Tether with wifi or USB? Does it happen with r274?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
I forgot to say, to get rid of the frequencies bug, just download again r282 and flash it. There are no changes in the kernel itself, only initramfs hence why it's still r282.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jbeez:
One gnex doesnt have a sim yet. I was trying to wifi tether it. Ill flash 274 in a bit and report
[Samsung Galaxy Nexus] jbeez:
Happens with 274 as well. I reverted to 273 for the time being for wifi tether functionality. The client shows the ap cycle between full signal and one bar... holding the phones right next to each other.
[Samsung Galaxy Nexus] renaud:
The only difference between the 2 is the WiFi driver. I will check as soon as I can.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jbeez:
no rush on my part its not frequently used and 273 works great too
[Samsung Galaxy Nexus] KSTu:
Hi,latest stable version cannot be downloaded,there is any other mirrors?
[Samsung Galaxy Nexus] renaud:
There is no release tagged as stable for 4.1 if that's what you are looking for. Please download r282 in testing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
Using 282.. Very responsive and snappy. On cycle #1 now but will return and post battery stats once I'm done w/ 3 more..Very smooth and actually one of the better kernels I've tried on JB performance wise. Can't wait to see what bettery is like. Tks.

<Edit added below text>

*On idle I'm draining 1% per 25 mins! Really liking this kernel! No lag at all and smooth as can be!:D
[Samsung Galaxy Nexus] :
Okay so from my 1st run I tried out different governors and interactive is definitely the one that is best..will you be adding more at a later date? Just curious.. I got 3 hrs 35 mins screen time on 1st run, almost non stop ...Did some reboots messing with apps to control kernel. Using Glados kernel app to adjust gamma & cpu frequencies..(Had a few fcs) All in all I'm really happy, it just glides along, very smooth!!!! I tinkered w/it alot making adjustments ...doing different things...I'm quite sure I can get better time than I did after I get all setup right and get through more rounds. I spread the word.:D Will come back tomorrow afternoon and post more information on my experience. Tks!

*Ended up using rom toolbox cpu control to control CPU @ 1036-345mhz ,interactive seems great for me. Okay sorry for writing so much great kernel!
[Samsung Galaxy Nexus] rashidi_zin:
I'm currently running 282 on Jelly Bean. The battery life is amazing. However I notice that there's random lag.

For example when I click on camera icon it took about 1-2 seconds before it launches the application.
[Samsung Galaxy Nexus] sam razzy:
hw is the battery life with this kernel??
[Samsung Galaxy Nexus] rashidi_zin:
It's good. Mine drained 2% after an hour.
[Samsung Galaxy Nexus] :
I'm not so sure that's kernel related, could be the rom.. What governor are you using because there's no lag on my end at all. That's what I find so awesome about this kernel.. I am on toroplus Gnexus. I found that running at 1344 mhz max and 691mhz min was the sweet spot for me, interactive gov because for me I saw lag in the other two govs but not in interactive. I just run like that when I play games, download files..etc....Then when I know I'm not gonna use my phone and put it on standby I bring it down to 345mhz min and 1036mhz max and it gets killer standby time..:good:
[Samsung Galaxy Nexus] renaud:
To be honest, I only had interactive and conservative governors. I added ondemand because someone asked, even though I think it's not a really good idea to use ondemand.

I do not really plan to add any governor as interactive and conservative do their jobs very well.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Create a new governor called ChuckNorris with exactly the same code as Interactive. People will use it and report as being better than Interactive. True story.
[Samsung Galaxy Nexus] gknnn':
+1 hahahaha

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] beekay201:
Really LOL right now

Sent from my i9250
[Samsung Galaxy Nexus] Gregus59:
r284 is smoothy... :D
[Samsung Galaxy Nexus] rashidi_zin:
I'm using stock ROM and didn't make any amendments to the governor. I have just flash stock Kernel and now things back to how it was.
[Samsung Galaxy Nexus] odin13:
Yes :D i asked for the ondemand governor...still a great governor when properly tweaked

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] neoxyrel:
I have tested your latest JB testing kernel and it is rather smooth. One thing though, there is this big lag when the phone is outside my wifi access point range and data connection starts. I need to turn off the phone's wifi connection to remove the lag. Among the custom kernel, i love to use Fugumod as it is the only one that can run orbot without error.
[Samsung Galaxy Nexus] tibere86:
What are the changes in ICS (4.0.4) v284? I didn't see any new commits.
[Samsung Galaxy Nexus] renaud:
Strange I pushed it. The only difference is kernel 3.0.36

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tibere86:
Thanks for the update!
[Samsung Galaxy Nexus] beekay201:
#284 running well, 0 issues from what I've seen.

Sent from my i9250
[Samsung Galaxy Nexus] eezdva:
Has the wifi high performance been added so wifi stays working with screen off??:laugh:
[Samsung Galaxy Nexus] renaud:
My kernel has a different driver than all the other kernels. Try it first and be sure to set advanced wifi params to let wifi on when screen is off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
Playing music, end data connection, turn on wifi caused a break of aprox. 1 sec, resumed music on its own.

Cm9#20120704

Sent from my i9250
[Samsung Galaxy Nexus] Bosio91:
Man, I love your kernel...

Any suggestions as to which kernel control app works best with FuguMod?

It would be awesome to have a simple script to control everything, like LeanKernel and Popcornkernel have.
[Samsung Galaxy Nexus] renaud:
I don't use any control app since the defaults in my kernel are the parameters I use. So I can't really recommend one.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aamadorj:
FuguMod works great with ParanoidAndroid 1.5.

After a couple days using FuguMod (details at the signature) with ParanoidAndroid 1.5, I can say they are a great match. From bluetooth, to WiFi, Mobile Data and colors everything is working great.

The best for me: battery drain is very low. So far, I think battery life will be the longest I've seen at my Galaxy Nexus (and I've tried different kernels, like CM, franco and trinity).

Thanks for this kernel, nikademus.
[Samsung Galaxy Nexus] eezdva:
Thanks for the answer but I knew that tip already :-) Ran ur kernel and nope didn't work.

Only when the screen turns on it works.
[Samsung Galaxy Nexus] stark_br:
Can u post some screens from your battery time and screen on time?

Many tks :thumbup:
[Samsung Galaxy Nexus] aamadorj:
Sure, I will as soon as I can. Previous post was kind of first impression.