yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] pedmond:
It will definitely not harm your phone. If you read some of the kernel threads around you will find more details about what can and cannot be done. 1300 is on the safe side though.
[Samsung Galaxy Nexus] renaud:
Let's say your device can live 10 years and overclocked it could only live 9.5 years. What are the odds you will still be using it in 4 years?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rene_r:
Thx in advance...

br

rene_r
[Samsung Galaxy Nexus] renaud:
CONFIG_USB_OTG=y

if that's what you mean :)
[Samsung Galaxy Nexus] renaud:
Newer wifi driver and newer compiler for r148

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bleomycin:
I just wanted to say that using v147 on AOKP build 27 my phone spends ~50% of the time at 350Mhz and the other 50% in deep sleep. Without any changes a switch over to the latest lean kernel has deep sleep at 80%. Is anyone else experiencing this? For both kernels android os is using by far the most battery at 49%! (probably not the kernels fault)
[Samsung Galaxy Nexus] renaud:
Was it on charger most of the time in 350mhz?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bleomycin:
Nope, off charger and i reset the stat's in cpu spy just to make sure. Sorry i can't be of much more help.
[Samsung Galaxy Nexus] Macke93:
Trying this out now :)

I did also notice that #147 did drain more battery!

#143 is the best I've tried yet :)
[Samsung Galaxy Nexus] manager77:
r148...what can l say?....it's just amazing...best WI-FI and battery life! Thanks again.
[Samsung Galaxy Nexus] renaud:
r148 gives me very good battery life, but phone seems stuck at 350mhz when charging, which is not a really big issue but may affect statistics.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Macke93:
I've now tried #148 for several hours, seems very stable och battery friendly! :D
[Samsung Galaxy Nexus] Ianxcom:
Will this work for toro?

Edit: it does. Just tried.
[Samsung Galaxy Nexus] slyydrr:
Do you mean your phone won't go above 350 when charging, or that you can't get into deep sleep. I've never been in deep sleep with any kernel while charging.
[Samsung Galaxy Nexus] bleomycin:
Just wanted to say i *think* the android os issue was related to the power button flashlight option in AOKP, possibly the battery % on home screen as well. Disabling those has brought the percentage for andorid os back down to 16% so it was probably never a kernel issue :)
[Samsung Galaxy Nexus] renaud:
I meant cannot go into deep sleep when charging. I never noticed that before to be honest, but that may indeed be normal.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slyydrr:
Yep, I believe that's 100% normal. I've never been able to, regardless of kernel/ROM/stock/etc..
[Samsung Galaxy Nexus] Macke93:
Back on #143 again because it is more battery friendly for me than the latest ones! ;)
[Samsung Galaxy Nexus] renaud:
I will have a look in the changes after 143 to find the culprit. Although 148 is working fine for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Macke93:
Sounds great! I'm really happy using your kernel, keep up the good work :D
[Samsung Galaxy Nexus] odin13:
Hi nikademus,

Could you add the ondemand gov back into the kernel?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
Yes I can. Why do you use it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] odin13:
well...with cpu tuner i can adjust the up threshold and the performance/powersave bias of the ondemand governor...

with the right settings this works very well in combination with a conservative off screen profile ( including hotplug mode )

would be great if you could consider it, your kernel works very nice on cm9 and i love the color control :)

*if it is too much hassle don't mind because the interactive gov works really well too
[Samsung Galaxy Nexus] renaud:
OK, I will add it in next build

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] odin13:
cool! :)

thnx
[Samsung Galaxy Nexus] renaud:
It's in r149

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] odin13:
just flashed nr.149 :)

thnx nikademus!!!
[Samsung Galaxy Nexus] Gregus59:
Hi Nika, what's new in 149?
[Samsung Galaxy Nexus] renaud:
I only added back ondemand governor.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rene_r:
@Nika: Would you think it would be an good idea to add Hotplug?

Or are there aren't really advantages?

I would be interested in your position.

br

rene_r
[Samsung Galaxy Nexus] pedmond:
I really hope not. This is a very stable kernel, and I have seen nothing but trouble with hotplug. Let's not get adventurous here - there's plenty of kernels for that.
[Samsung Galaxy Nexus] renaud:
Switching off one CPU is only useful when CPUs are not in deep sleep. Which means you have to do that when you are actually using the phone, when probably asking for performance. So that means CPU will be switched off only on very low use, which is unlikely to bring tremendous amounts of power saving.

I may be wrong here but with current architectures, savings are not significant enough to be worth the hassle.

It's just like start/stop features on current cars, I am not convinced the drawbacks are worth the gain. (Note: I have a car with that feature and while I am using it, I am not convinced in the long term).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rene_r:
Thx for your explanation.

Br

rene_r
[Samsung Galaxy Nexus] Macke93:
Please tell me if you found what makes #143 more battery friendly! :D

I hope you find it soon :) Keep up the good work man :cool:
[Samsung Galaxy Nexus] slyydrr:
I dunno man, r148 seems fine to me. I'm having trouble uploading multiple images but that's 1hr 20m screen on, running r148 on CM9.
[Samsung Galaxy Nexus] renaud:
is r144 any different battery wise?

The only big difference after that is the upgrade to 3.0.23
[Samsung Galaxy Nexus] Macke93:
Haven't tried that one, but just to be nice I will flash r144 now :D

I'll be back :)

Edit: Now I'm on r144!
[Samsung Galaxy Nexus] ogdobber:
hey nikademus does the security update prevent wallet cracker from working?http://xdaforums.com/showthread.php?t=1487725

or is that another exploit related to the wallet apk itself?
[Samsung Galaxy Nexus] renaud:
No, it doesn't protect from that vulnerability, only a change in Google wallet will do. The main problem with wallet is that the pin code is stored in the app DB (encrypted), but bruteforcing a 4 digits code is trivial.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
I got a Wallet update two days ago. Maybe that hole is already fixed.
[Samsung Galaxy Nexus] verve50:
Thanks nikademus this is the best Kernel i've used, and i tried all of them.
[Samsung Galaxy Nexus] Flukester69:
I'm glad I am running this kernel. It's made my phone really stable and battery usage is very decent for stock battery. I am running AOKP with the latest FuguMod kernel with zero problems.
[Samsung Galaxy Nexus] renaud:
Maybe, what does the change log mention? I cannot see google wallet in the market here.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
IIRC it said security fixes. Nothing more specific. Also Google Authenticator was updated also with 'security fixes' in the "changelog".
[Samsung Galaxy Nexus] bleomycin:
I just wanted to share these screenshots from badass battery monitor and cpu spy, this is running V149 on AOKP 27. The reason i bring them up is yesterday i ran the latest stable leankernel as a test and kernel battery usage was significantly lower in badass battery monitor and my Deep Sleep was around 78% with very similar phone usage as today (mostly screen off with an hour of runkeeper or so in between). Hopefully this is of some help!
[Samsung Galaxy Nexus] renaud:
Thank for the report, but unfotunately, with the small amount of time you ran the kernel, it's not really informative, you should always run at least 24 hours to get significant reports.
[Samsung Galaxy Nexus] renaud:
r154 (currently in testing) may give better battery life. Feel free to test and report.
[Samsung Galaxy Nexus] franciscofranco:
Smartreflex 1.5 disabled (like you had prior to r154) is good to achieve greater OC values, but it may cause instability for some devices so enabling it was a good decision :)
[Samsung Galaxy Nexus] renaud:
Smartreflex class 3 does not work on this device, so it's 1.5 or no smartreflex at all.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Where did you read that?
[Samsung Galaxy Nexus] kendong2:
vpn seems to be broken:

racoon E Cannot allocate TUN: Operation not permitted
[Samsung Galaxy Nexus] zurchpet:
Any plans to backport 3.2 kernel features?
[Samsung Galaxy Nexus] renaud:
There are already some of them. Getting the full kernel to run will take a little bit longer.
[Samsung Galaxy Nexus] zurchpet:
Running R47 on fitsnuglys latest CM9 KANG :)
[Samsung Galaxy Nexus] zurchpet:
Wooohooo, R49 is Linux 3.0.17 :D
[Samsung Galaxy Nexus] renaud:
I upgraded to 3.0.17
[Samsung Galaxy Nexus] renaud:
Given that nobody seems to need the 4.0.2 version, I decided to kill it since it was really a hassle to update it
[Samsung Galaxy Nexus] renaud:
I have now published a CWM flashable version too.
[Samsung Galaxy Nexus] Ranatsu:
maybe its just me but I'm having complications downloading over the ICS browser.. it downloads 100% and then says download unsuccessful. Downloads fine on the PC though.. Strange.
[Samsung Galaxy Nexus] beekay201:
works fine here; what kind of file were you trying to download? apk here

updated to r52, didn't have any majour issues with r44.

@nikademus, i have tried gpu oc with other kernels and also a kang build from stock+gpu oc, and i've reached the conclusion that it renders artefacts on black transitions to other colors on my screen (for example in phasebeam lwp). also doesn't make much of a difference in general. i also don't see those artefacts with your kernel. will you be including gpu oc in the future?
[Samsung Galaxy Nexus] mazenimad:
I need the 4.0.2 version on cwm but the official site gives me a 404 gateway error! Can someone guide me.
[Samsung Galaxy Nexus] beekay201:
cwm flashable yes, 404 error

fastbootable img, link is up
[Samsung Galaxy Nexus] renaud:
4.0.2 has been discontinued and is not available in cwm format.

Sent from a Nexus
[Samsung Galaxy Nexus] renaud:
To be honest, I did not plan to add OC anytime soon given that the phone is fast enough like this. When I look at the time in different states, it is not that much at 1200. Apart for benchmarks, I am not sure there is any benefit in OCing the phone. Yes, you will get a bigger quadrant/antutu score but you will probably not even notice it in real life, while you will drain battery faster with odds of getting crashes (weak tough).
[Samsung Galaxy Nexus] renaud:
Given that 4.0.4 (or maybe 4.0.3 official, who knows) is really around the corner now and introduces the same kind of incompatibilites that 4.0.2->4.0.3 did, I may drop 4.0.3 development when 4.0.4 (presumably) is out.

EDIT: in case you wonder why I post this:

commit c885fad9bb18f3649d5eef1d3ba2a659946bf196

Author: Alistair Strachan <alistair.strachan@imgtec.com>

Date: Thu Jan 19 17:07:23 2012 +0000

gpu: pvr: Update to DDK 1.8@794370

is incompatible with current 4.0.3
[Samsung Galaxy Nexus] slyydrr:
With 3.0.17, I was able to run 4.0.3 quite well, however the battery drain was much more significant. Any ideas?
[Samsung Galaxy Nexus] renaud:
I doubt this is due to 3.0.17 only, but it may be due to one of my latest patches. I am investigating. In the meantime, you can also try a former version.
[Samsung Galaxy Nexus] slyydrr:
Will definitely do so - much appreciated. For what it's worth, I've had major stability issues w/ 4.0.3 - abundant connection drops. The problem is 100% non-existent with 4.0.2 and was non-existent with your r61 kernel based on 3.0.17. However, that one did cause the drain for me that I was mentioning. I'll try r62 now. Did 3.0.17 start with r61?
[Samsung Galaxy Nexus] renaud:
No, 3.0.17 began in r49
[Samsung Galaxy Nexus] renaud:
r62 seems to solve the battery drain problem. but I have to test on a longer time period.
[Samsung Galaxy Nexus] slyydrr:
I thought that too but let it run all night and saw the same results as r61. It seems like in the battery graph shows the phone being awake for randomly long periods of time at some regular interval.

In the meantime, I'm currently working my way backward through the releases (on r58 now) to see if I can't find when the problem started.
[Samsung Galaxy Nexus] Macke93:
Now testing #155

Did not felt that the battery time were better with #144 ;)
[Samsung Galaxy Nexus] renaud:
Thanks for the report, can you be more precise by telling which kind of VPN has been used and post logcat and dmesg?
[Samsung Galaxy Nexus] renaud:
I did not read that, I tested it. You cannot enable autocompensation when using class3, which more or less means smartreflex is useless.
[Samsung Galaxy Nexus] kendong2:
will do, might take a few days until i can tho.
[Samsung Galaxy Nexus] mekanismen:
What color values are people using?
[Samsung Galaxy Nexus] zurchpet:
Gamma:

Red: 51

Green: 53

Blue: 62
[Samsung Galaxy Nexus] Gregus59:
I have an amazing battery life with 155... The best I never had, ty Nika... ;)
[Samsung Galaxy Nexus] renaud:
Are there many people here with make wlan_tx_wake kernel wakelocks? This is due to a noisy network, but I'd like to understand how to solve this, so if you can post your wifi/network config, that would help me. Especially if there are devices on your network that are known to be noisy in broadcasts/multicasts.

Please specify the kernel version you are using too, without this information there is nothing I can use.
[Samsung Galaxy Nexus] chadouming:
I know that Gokhanmoral's siyah kernel for galaxy S II had this problem too and he made his way to correct it. Might want to ask him.
[Samsung Galaxy Nexus] renaud:
As far as I can see, he just reverted to older drivers :D
[Samsung Galaxy Nexus] odin13:
That would explain why i only get these wakelocks on your kernel...as far as i know yours is the only one with these new wifi drivers

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
Note that they don't really affect battery life that much

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zurchpet:
it seems to be the noisy wifi indeed. Was in another office today the whole time on wifi and the drain was noticably lower.

PS: I run the latest test kernel: R157

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Macke93:
Having great battery life with #155!

I use Extended battery from samsung @ 2000mAh :)
[Samsung Galaxy Nexus] renaud:
Well, here is mine with standard battery

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gingernut78:
Nikademus,

I just had a total freeze and reboot on R157 and latest CM9 nightly.

The phone was off, low battery, I plugged it in to charge, turned it on and it froze on the entre pin screen rebooting on it's own, once rebooted it was fine.

I've attached the last_kmsg file.

I've tried your last four or five releases but just keep going back to CM9 stock kernel, despite what is said in previous posts your kernel seems to have quite higher drain. Kalimocho, even though his might not have all the bells and whistles, it does have second to none battery life.

Anyway, thanks for all your hard work and dedication.
[Samsung Galaxy Nexus] renaud:
Use the kernel that fits you the best. Though I would say your crash is probably not due to the kernel, but I cannot be sure. I never experienced any crash in the kennels in stable folder. That said, there is no attached file in your post.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gingernut78:
Sorry about that, I don't know what happened to the attachment, reattached.

I hadn't any crashes either up to now, only this one, and as you said probably not you kernels fault.
[Samsung Galaxy Nexus] fireon123:
I have been using 148 together with AOKP B26 to fix my signal drops on 4.0.3 roms. Thanks for providing a solution for those signal drops!

However, when I flashed AOKP M4 yesterday together with FuGuMod Kernel 157 I experienced these signal drops again. So I went into recovery and flashed the FuGuMod 148 again which solved all my problems. So as far as my experience goes you should have changed something between 148 and 157 which affects the performance of the radio... Can you change this back?

I used the same radio on all occasions.

Thanks anyways for providing a great kernel! :)
[Samsung Galaxy Nexus] renaud:
Do you have the recommended bootloader and baseband? See first post.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
Guys and girls, if you experience radio drops with kernels >	r154, please check if you have the recommended bootloader and baseband versions. If you do, please report, this is important to understand why this happens.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fireon123:
Thank you so much! :)

I was on the wrong bootloader. I had no idea that a bootloader could affect signal drops. I had the 4.0.2 PRIMEKK15 bootloader with XXKK6 radio.

Now I am running the recommended PRIMEKL01 bootloader for 4.0.3 roms with XXKK6 radio and FuGuMod Kernel #157 without any signal drops!

I will report if I get some signal drops!
[Samsung Galaxy Nexus] renaud:
A report will greatly help, even if it's to say it works. I already have a very precise idea of what could cause this, but I want to be absolutely sure because bootloader and radio may be part of it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gtizon:
How would I know what bootloader I have? Thanks!
[Samsung Galaxy Nexus] Vangelis13:
Reboot into bootloader, it's mentioned there.
[Samsung Galaxy Nexus] beekay201:
#154, been getting those wifi wakelocks. Not affecting battery life very much i'd say, speeds seem ok, knowing that i dont have the best signal everywhere inside my house. I normally leave wifi on while at home, so that would make like 7, 8hrs on wifi.

When i'm at home i'll post a better battery stats screenie.

If i can do anything else to help, i'll be glad to.
[Samsung Galaxy Nexus] jake2k1:
I tried #157 with the recommended boot loader and radio. I get signal drops on it. Going back to kernel #143 it seems to work the best for me. I'm running aokp m4.
[Samsung Galaxy Nexus] fireon123:
For me 157 together with AOKP M4, bootloader PRIMEKL01 and radio XXKK6 works fine. Have been using it all day without any drops.
[Samsung Galaxy Nexus] slyydrr:
I'll check in Monday night. Out of town and won't be at a computer until then but I experienced drops on other kernels so I'll be sure to let you know.
[Samsung Galaxy Nexus] renaud:
From what I can see now, radio drops are due to the voltage. flashing radio and bootloader may help. But for those with phones still having radio drops after that there seems to be no other way than disabling smart reflex.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fireon123:
By voltage, do you mean that the phone sometimes does not push enough power to the radio, and by that causing these drops?

What exactly is smart reflex and how could you disable it?

Sorry for the n00b questions =)

Edit: Found this: SmartReflex is an advanced, multi-level and multi-parameter power management approach that can be found at some TI DSPs of the OMAP35x series.

So SmartReflex basically undervolts and handles the voltage to the SoC for the phone during certain occasions. Like a built in power manager within the processor. This would mean that the only way to disable SmartReflex would be to have a kernel that disables it? Am I right?
[Samsung Galaxy Nexus] Treatcon:
I'm running current everything and haven't noticed signal drops at all. Your latest stable kernel 157.
[Samsung Galaxy Nexus] renaud:
You can disable it manually, I will post on that later

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
Only some phones seem to have a problem if running latest firmwares

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
For those where Radio problems persist after flashing recommended versions, try echo 0 >	/sys/kernel/debug/smartreflex/sr_core/autocomp

And report obviously

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
That can cause some adverse ****. When I had smartreflex disabled some people had SoD's when returning from sleep, specially users with my hotplug mod. It was rare, but some got it.
[Samsung Galaxy Nexus] jake2k1:
I've tried this and so far no radio drops with #157.
[Samsung Galaxy Nexus] renaud:
If you read my post, it's only for selected people with well defined problems, it's certainly not recommended for most people.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yep I know I just wanted to point out "possible" problems coming from it, just in case =)
[Samsung Galaxy Nexus] kendong2:
seems to work for me.
[Samsung Galaxy Nexus] T!m:
Yup seems to solve my signal drops two.
[Samsung Galaxy Nexus] renaud:
R158 has Linux 3.0.24

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
r160 _may_ solve radio drops (without manual intervention), it has some changes in smartreflex. Please report if it works as this is something I am not able to test myself as I don't have radio drops.
[Samsung Galaxy Nexus] slyydrr:
I'll give 157 a try and then follow up w/ 160 once I experience a radio drop. I'll report back in a bit.
[Samsung Galaxy Nexus] stevesteveLA:
Still dropping...

Just downloaded and flashed r160. Unfortunately, I'm still experiencing signal drops. Happy to provide more information to help you solve this issue. I received the GNEX from a friend at Google, so returning it is out of the question.

Thank you for all of your hard work!
[Samsung Galaxy Nexus] beekay201:
Drop on 158 just now (edge, forum runner), going up to 160 later.
[Samsung Galaxy Nexus] renaud:
With smart reflex disabled as described on first post?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
As is.

Never had drops with your kernel nika. I'll try disabling smartreflex like you said.
[Samsung Galaxy Nexus] renaud:
This only disables a small part of smartreflex, if it does not affect battery negatively, I may set it as default.
[Samsung Galaxy Nexus] rashidi_zin:
I'm currently on #160. I'm loving the battery life!!! :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ludow:
Just got SOD with r160. Back to r158. I know, not much info. :o

No tweaks, Apex 1.02 ROM and Fugu. R158 is ultimate choice for battery and performance too, thanks.
[Samsung Galaxy Nexus] Flukester69:
So how does one ascertain they have a problem with drops? How can you know it's not your environment but its the phone. Mine goes from H to 3G a lot. That's a drop no??? I'm just curious how people know it's the phone or kernel or whatever.
[Samsung Galaxy Nexus] rashidi_zin:
I don't know how others make their judgements. But I will use the kernel for at least a week.

If situation remains the same I will convert to previous working build. If the situation changed, I will then blame the kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fireon123:
That is not a drop!

My definition of a drop is when you at the same place where you usually have full reception all of a sudden have no reception at all. The signal meter is just blank...
[Samsung Galaxy Nexus] renaud:
Thank you for reporting. It would be interesting to know if you can still have a SOD in r159.
[Samsung Galaxy Nexus] Flukester69:
Ok, well that's strange. I never had that problem or never noticed. I've seen it go gray when I am in the basement of my house but moving around I get it back either 3G or H. That's about it.
[Samsung Galaxy Nexus] renaud:
Which governor were you using?