yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
wlan_rx is caused by wifi enabled. The other one I don't know, I think its some media stuff, dunno really.

Test4 is out. Grab it here: http://minooch.com/franciscofranco/Galaxy Nexus/test_kernel/
[Samsung Galaxy Nexus] samizad:
Don't bother trying to get rid of those two wakelocks. I think everyone has them.
[Samsung Galaxy Nexus] shafty023:
Just saw this in the OP and thought I'd comment on it

This isn't actually true. When you undervolt the kernel it lowers the total voltage that can be dispersed between the various components including the cell radio. This is actually a very common problem with many undervolting if done too aggressively. You can ask kmobs from the Cyanogenmod team for validation of what I'm saying as we've encountered this before. So if after flashing this kernel or any other kernel and the cell radio drops a lot the kernel cooker needs to raise the undervolting a bit until this issue stops. That's when you know you've found the perfect voltage value.
[Samsung Galaxy Nexus] franciscofranco:
That's 100% true, but I'd say thats pretty rare, if non-existent, with the current ~87% undervolt compared to stock, so if one undervolts too much = not kernel issue, but user issue.
[Samsung Galaxy Nexus] psycho2097:
I know that...but there has to be something...I mean,I see a lot of battery reports with no wakelocks. Even franco's logs show very low wakelocks. They are the ones getting 1% in 7hrs...:( I want that.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shafty023:
Ya I wasn't saying your kernel specifically as compiled would cause it. Just making sure people know it is possible if someone were to undervolt too low they wouldn't just get reboots, they could see other symptoms such as the cell radio dropping signal often too.
[Samsung Galaxy Nexus] psycho2097:
Changelog?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the reminder, I'll update the OP with that information just in case.

Not giving changelog in this one, I don't want biased feedback.
[Samsung Galaxy Nexus] jrichardsMav:
This Kernel is too dope. Much better battery life. Appreciate it.
[Samsung Galaxy Nexus] rye&ginger:
Is full wipe the only way to fix this?

http://code.google.com/p/aokp/issue...ype Status Owner Summary Modified#makechanges

What steps will reproduce the problem?

1. open settings > apps > running

2. compare to OS Monitor app report and it shows more free RAM and actual RAM used by apps.

3.

What is the expected output? What do you see instead?

system screen should show RAM used etc.

What version of AOKP are you using? What kernel? Have you installed any

mods?

M3 maguro with 15.2 Franco kernel. No mods.

Comment 1 by project member romanb...@gmail.com, Today (4 hours ago)

This is a commonly known issue when switching to Franco's kernel. I believe you need to wipe ALL data to get this resolved (like /data and /sdcard)
[Samsung Galaxy Nexus] samizad:
I don't want to dwell on this subject in this thread as it is off-topic but just to emphasize that you might get 1% drain in 7 idle hours on a fresh ROM flash with zero apps and airplane mode but, as a normal user, I have never got better than 2-3% in the same idle period; which is still fantastic!

Use AOKP with power saving options and you'll get pretty amazing idle drain.
[Samsung Galaxy Nexus] weirdg:
Hi Francisco,

I've noticed people are having problems connecting or finding 5GHz wifi networks with their GNexes. I can connect to my 5GHz wifi network, but I'm experiencing weak signal strength compared to my 2.4GHz network. Any chance you can look into this?

Here are the settings for my network.

Router: Asus RT-N56U

Wireless: 5GHz

Wireless Mode: N only

Channel Bandwidth: 40MHz

Channel: Auto

Authentication Method: WPA2 Personal

WPA Encyption: AES

TIA,

WG
[Samsung Galaxy Nexus] Kaboosey:
App is getting better now after the recent update. Loads faster than before (usually have to wait for it to load).

Testing test4 now.
[Samsung Galaxy Nexus] chamonix:
There is something that can be done against rx_wake. That wakelock is caused by incoming wifi packets waking the phone. If you find/remove the cause (wireshark) or prevent the phone from listening to wifi when screen is off (wifi policy) that specific wakelock should disappear.
[Samsung Galaxy Nexus] sishgupta:
It's part of 802.11's nature for the AP to poll a connected device periodically. The only way is to disconnect the device from the AP.

AOKP has a power save feature to turn wifi off when the screen is off.

Really though it doesnt waste that much battery life. I left wifi on this weekend and my phone had 13 minutes wifi_rx wakelock after 16 hours on the network. I think my battery went down 2-3% after a 10 hour sleep. (Franco 15.2 has been great on wifi imo)

There is a need to reduce unnecessary wakelocks for sure, but within reason.
[Samsung Galaxy Nexus] CaspaTheGhost:
Test 3 overnight drain of 5% in 9 hours, with two push accounts and wifi on...

Nicely done sir!

No SOD on this version for me.
[Samsung Galaxy Nexus] Leandros_Ger:
Unlockscreen laggs a bit on #15.2 and AOKP M3. Minimum CPU speed is set to 700 MHz and francoGazelle governor.

But laggs only if you unlock fast after pressing power.

I thought you should know it. :D

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] danielvc:
Do you have your Gnex on auto brightness? Try to adjust is manually and check if it still happens.
[Samsung Galaxy Nexus] johno168:
No issues here, using francoGazelle + AOKP M3 350/1200mhz working fine!

However don't see much difference in performance over turtle? Anyone else?
[Samsung Galaxy Nexus] Leandros_Ger:
Thanks all. Auto Brightness solved it.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Mondfahrer:
grey signal/wifi bars, anything to do with the Kernel? Running 15.2 and had never a issue with my signal but today my signal bars are all the time grey and I can't connect to the internet. My Wifi is working and my GN is connected but not working. Also when I switch Wifi off and try via my Provider, it's not possible.

Yesterday everything was ok and I didn't changed any settings or installed any new apps. I tried to change Baseband and flashed already my Backup, but everything won't work.
[Samsung Galaxy Nexus] JcMalta:
I am pretty certain this is a ROM issue.
[Samsung Galaxy Nexus] CaspaTheGhost:
Its grey as your not connected to the Google servers... Wont be a kernel issue...

Sometimes happens to me but it tends to come back on...
[Samsung Galaxy Nexus] slide83:
Franco, love the kernel and appreciate your work on it.

Are you going to go ahead and start working on compatibility with 4.04 since it leaked or will you wait for the official verision to drop before starting?
[Samsung Galaxy Nexus] delvirtud:
/cheers

Francisco:

[Off Topic] I don't chime in too much on forums, but here is my 2 cents. You obviously enjoy the work you do and you provide a great service to the modding community, which I for one greatly appreciate. The reason why I don't chime in is because I know how to read and I know how to search because chances are whatever issues I am having someone else is experiencing or has experienced the same thing.

TLDR: Ignore these lazy people asking questions THAT you just answered and keep up the good work.

[On topic] T3 ran great, but was getting SoD (3 nights in-a-row) on GN LTE @700/1200, turtle, with your default frequencies ONLY overnight (6ish hours idle). Trying T4 now. Edit: On AOKP M3.

/ty

del
[Samsung Galaxy Nexus] coleburns:
Are you using power saving on kang? If yes, turn it off and toggle wifi on and off or worst case, restart phone.
[Samsung Galaxy Nexus] franciscofranco:
Like I already answered I can't work on something without having sources. As far as I know this ramdisk works just fine on 4.0.4. When the sources drop I'll work on it ;)
[Samsung Galaxy Nexus] CaspaTheGhost:
Update:

I switch my SIM between the work BB and my GN, so had the GN on flight mode from 9am this morning... Just switched back as the powers that be are not around... AND...

Had 2% drain from 9am - 3:30pm whilst in flight mode, so about 1% per 3 hours!!!

That plus my overnight drain tells me that the Test3 kernel is rocking!!!

FYI - I'm running Bigxie's Apex ROM and use his in built 'Performance' settings rather than the ones in Franco's kernel app... Kept it all as Franco intended though...

Gonna give Test4 a try so will report back when I have some useful info!
[Samsung Galaxy Nexus] poopooface:
If you could deign to explain this to a relative kernel noob, how often does the phone do a kernel tick? Obviously not as often as the CPU cycles. Does the internal kernel tick frequency scale with cpu speed?

I just pretty much want to know how often it will be checking the cpu load when I flash test4 tonight.

Also, I was going to do a real battery test on test2, but then I decided to swap back in my stock battery so I could let google buy me $10 worth of ketchup and toilet paper. So I never got a chance. But I will test with test4 starting tonight, promise!
[Samsung Galaxy Nexus] minipaolo:
Why don't you link the test kernel in the OP?
[Samsung Galaxy Nexus] franciscofranco:
The timer tick is a timer interrupt that is usually generated HZ times per second, with the value of HZ being set at compile time and varying between around 100 to 1500. Something like that. At the moment in the test4 kernel the function that checks for the dynamic hotplug is called every HZ*20.

It's in the FTP, that isn't hard to figure out.
[Samsung Galaxy Nexus] poopooface:
Ah, thanks for the reply, Franco. So what is the value of HZ in the Test4 kernel?

And just to clarify, if the value of HZ is set at 100, it would check the cpu load 5x/second, whereas if HZ was 1500, it would check 75x/second?

Thanks so much for your work on the kernel. Even with 15.2 I could go to sleep for 7 hours and not lose a single percent of battery.
[Samsung Galaxy Nexus] kilian7th:
Hi Franco, thanks again for your work, I always installed your release and I am very happy with it, only one option doesn't seem to work for my configurations : on cyanogemod 9 developped by Codeworkx or on Vicious Miui, when I activate cpu 1 down when screen is off, my phone don't wake up with governor turtle or ondemand with others settings by default via franco kernel updater.

This was just a feedback and nothing else :)

Thanks again ...
[Samsung Galaxy Nexus] renaud:
This is probably not a kernel problem. The main problem with 5ghz is penetration through walls or other objects. The shorter the wavelenght, the harder it has to pass through objects.

For example, I am running two Ubiquiti rocket (one M5 (5ghz) and one M2 (2.4Ghz)). Both have a dual polarity 13dbi antenna. My rocket M2 is configured to deliver 6dbm less in power than my M5. But where I am right now, I get -45dbm on my M2 and -55dbm on my M5 (-45 is much better than -55). There are "only" 2 walls in between and the antennas are located at the same place.

5ghz has the advantage of getting less interferences because it is in a less crowded frequency zone, but it really easily dissipates.

Also I am not really sure the Galaxy Nexus supports 40mhz band, but if your AP is capable of delivering both 20 and 40mhz, that should only cause less speed. You will only get only 65mps max as the phone is not MIMO either.
[Samsung Galaxy Nexus] weirdg:
The GNex must support a 40MHz band, because that's how my router is setup and it can connect to it. I did more playing around on the router last night, and I tweaked a few settings which seem to fix the signal strength on my GNex a bit. It's still weak, but better than before. That's for the info nikademus.

WG
[Samsung Galaxy Nexus] crecsky:
If you are running AOKP Milestone 3 you are likely having WiFi issues if you are running this kernel.

As for contacting Franco and informing him of the problem I guess I wasn't quite specific enough, but I've narrowed down the problem to the kernel. I would like to use this kernel as I like it, and I purchased the app. It sometimes stays blue, but isn't connected to WiFi, or it goes greyed out. I don't know if he's working on a fix, but if there is any way for me to help him I would be glad to help.

"On Feb 3, 2012, at 5:21 PM, Cory Recsky wrote:

I know you were saying that the old wifi setup was causing problems but I think this new one is giving me grief. Had been working fine until I updated and now I get a still connected blue color but its not connected to the internet.

Francisco Franco

Feb 3 (3 days ago)

to me

Hmm I can't help you right there because my wifi works just fine being close or far from my router. Check your baseband."

Changelog:

#15.2

* Stability release: back to the old wifi driver as the new one was causing instability issues

* Other small stability reverts

I know that 15.1 was working properly, or at least I'm 90% sure. I'm guessing the change in the wifi driver between 15.1 and 15.2 is what is giving me grief. I don't know if there is a way to include both?
[Samsung Galaxy Nexus] joelteixeira:
Just to say that I'm using AOKP M3 and latest franco kernel without any Wifi issues. Note that I use Wifi almost 100% of time (both house and work).
[Samsung Galaxy Nexus] renaud:
I guess that if you do strict 40mhz, you won't be able to connect, but your router probably forces a dual 20/40mhz band like almost all consumer devices. If I do remember well, when set at 40mhz on my APs (carrier grade, no 20mhz compatibility), I cannot connect from any android phone.
[Samsung Galaxy Nexus] crecsky:
Sorry, I guess there is something weird about my phone, but I know other people are also having issues.
[Samsung Galaxy Nexus] danielvc:
I'm also having this problem, but only after a few hours when I don't use the phone (so not when it goes to sleep, but after a longer period of not using the phone, like 2 hours). When it happens, I don't receive Whatsapp-messages/mails etc.

Only having it on work though, but maybe I'm playing more with my Nexus at home. It's a bit of an annoyance that occurred when I flashed Franco's kernel, but I'm loving it too much to change :-)
[Samsung Galaxy Nexus] crecsky:
Maybe some of our settings are off, I'm not too sure. I know I was using francoTurtle with min of 300 and max of 1200 and hotplug. No undervolting.
[Samsung Galaxy Nexus] mikeandjaimie:
I'm using M3+ 15.2 and now test 3 and like the other person, use wifi pretty much exclusively, except when between destinations.. I've had none of the issues with wifi and I'm usually connected for most of the day straight through.

what are your oc/uv settings or are you? Just throwing it out there, but maybe your settings are too low and its dropping connection? Sorry if its been suggested, just had problems myself once when I payed with it manually and it didn't have enough power

Edit: nvm guess you beat me to it lol
[Samsung Galaxy Nexus] joelteixeira:
Maybe it's a specific type of router, I read about some CM9 users having issues with 5Ghz routers. Maybe we can find a standard among the users with wifi issues.

Update: BTW, I'm using Turtle with 700~1000 w/o Hotplug. I didn't change nothing in undervolting settings.
[Samsung Galaxy Nexus] crecsky:
It's not likely the router as I have the problems at work as well as at home, and I've also changed some settings on the router to apparently "fix" the issue. Believe you me, I didn't want to believe it was at all the kernels fault.

And when I run just the stock M3 I don't have any problems.
[Samsung Galaxy Nexus] psycho2097:
Interesting... i m losing battery like crazy on test3. test 2 was pretty awesome. 14.4/15.2 were pretty good too.

On test 3, i am on 1:20mins screen on, 14 hrs going on i am at 38%. it would be 60-70% on test 2/14.4.
[Samsung Galaxy Nexus] franciscofranco:
Try test4 please.
[Samsung Galaxy Nexus] alec534:
Running francoturtle at 700 max and 350 min. Voltages that came with the kernel and hotplug turned on. Great battery life and no lag.
[Samsung Galaxy Nexus] DarkGruf:
Weird problem with last version of the app. At each reboot I'm set at franco turtle and 700 to 1000 whatever I choose to set on boot (in my case gazelle with 700-1350). Never happenned before.
[Samsung Galaxy Nexus] lamecake:
Try fixing permissions from cmw / deleting app caches, might help..
[Samsung Galaxy Nexus] franciscofranco:
I tried it just now and it sticks fine for me, I had that fixed long ago.
[Samsung Galaxy Nexus] Cutting-TM:
I've tried everything but I can not save turtle as default governor. And the unit.d file deletes itself it seems...

Any ideas?
[Samsung Galaxy Nexus] oli20021978:
Maybe you should disable all extra settings for the guys. No extra settings no extra problems. :-)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
What? Turtle is the default governor...
[Samsung Galaxy Nexus] Cutting-TM:
After a while interactive is set to default... I don't know why. Should I change the rom to milestone? I'm on the latest eagle blood rom.
[Samsung Galaxy Nexus] MasterLapa:
Hi there! I flashed your kernel on ARHD 2.1.5 rom but i got a boot loop at the first logo, tried to wipe dalvik and normal cache but it didn't help..sounds weird to me, i got no mods nor anything else just the plain rom. Am i missing something? Thanks for the answers!
[Samsung Galaxy Nexus] opensourcefan:
Are your rom kernel settings interfering by any chance?
[Samsung Galaxy Nexus] CaspaTheGhost:
Its the default so it must be something over riding it. Does your ROM have settings for CPU performance or do you have Set CPU installed?
[Samsung Galaxy Nexus] Cutting-TM:
I think i found the error... system tuner pro changed the governor. Such a shame :-D
[Samsung Galaxy Nexus] franciscofranco:
I'm sorry but that is on your end, I can't help you there.

This is only for 4.0.3 as it's written on the thread title....
[Samsung Galaxy Nexus] Cutting-TM:
Please take a look at page 1 and find your error...
[Samsung Galaxy Nexus] yyz71:
Ya just flashed back stock kernel. This one was heating up like muthafucker...
[Samsung Galaxy Nexus] franciscofranco:
Ok update is up. Test it and provide feedback please.
[Samsung Galaxy Nexus] DJTaurus:
It doesnt shows it anymore.Dont know why.
[Samsung Galaxy Nexus] Shetlander:
Great. Just flashed it so I will fully charge the phone and report back tomorrow with feedback.

Thanks
[Samsung Galaxy Nexus] beekay201:
will get it when i get home, working on a sunday :p

that reminds me, i flashed 10th dec rls over aosp built 10/12 as well.

voltage control does not report steps/voltages correctly. Changing 1200mhz voltage actually sets 350mhz voltage, changing 700mhz voltage tweaks 900mhz. an app problem, i'm sure. haven't seen any screen artifacts. setcpu works fine, though.

here is my UV values:

1200mhz: 1100mv

920mhz: 1000mv

700mhz: 925mv

350mhz: 875mv

Francisco, could you please update first post with stock voltages, when you have the time?
[Samsung Galaxy Nexus] gandalf027:
Another one testing your kernel :)

Objective .. get the usb host with pen drive access.

Gona test this new version, see if the battery drain is gone.

Great work ;)
[Samsung Galaxy Nexus] 3c:
Stock voltages are:

1200Mhz: 1300mV

920Mhz: 1250mV

700Mhz: 1100mV

350Mhz: 1050mV

That's what you get after booting this kernel without tweaks. Maybe you might want to consider using System Tuner, you can save the stock values after booting without tweaks.

EDIT: Tried your settings: phone frozen almost immediately, stuck @ 900Mhz, then reboot.

I'm using -100mV on all frequencies fine so far. Yours seem very low?!
[Samsung Galaxy Nexus] gambiting:
Shame you had to disable the USB Host support, that was the reason why I flashed your kernel.
[Samsung Galaxy Nexus] beekay201:
I was talking about stock kernel voltages.

In regards to UV, every phone is different mate. I'm actually surprised my phone can handle these voltages, my sgs was so much more sensitive (a small 25mv UV on 1ghz caused SoD's). Will keep testing for a few more days.
[Samsung Galaxy Nexus] JCUK89:
Which ROM?

Hey guys,

I am a bit confused. Which rom is recommended for us with Franco's kernels? Im on the Ir5 from Modaco...

Cheers.
[Samsung Galaxy Nexus] Shetlander:
Im on Android Rev HD and with Franco's kernel I get an even greater boost in 3D. Also the ROM is fast and slick.
[Samsung Galaxy Nexus] DebauchedSloth:
Just installed the latest. So far so good, but the kernel is BUG() a lot in dmesg:

BUG: using smp_processor_id() in preemptible [00000000] code

With a stack trace each time. That can't be helping battery life much.
[Samsung Galaxy Nexus] nmesisca:
graphic glitch

Hi franco,

sorry to disappoint you mate, but the graphic bugs is still there. actually for me its much worse than in the previous release. still when coming back from lockscreen. seems to stick a lot more, cant seem to get rid of it with simple on-off..

N

PS this using the kernel (non OCed) you just released of course.
[Samsung Galaxy Nexus] franciscofranco:
Thank you. I'll look into it.
[Samsung Galaxy Nexus] curioisty:
Thx for your work!

Confirmation Number: 5NX47579PB421762J
[Samsung Galaxy Nexus] dwang:
Latest kernel doesn't seem to be showing wifi strength correctly. Didn't have that issue with the previous version.

EDIT: Never mind, a reboot seems to have fixed it.
[Samsung Galaxy Nexus] faux123:
Hey man, long time no see ;)
[Samsung Galaxy Nexus] drawde40599:
Ya i did the same , the stock kernel and radio seem to be the fastest and smoothest for pauls rom , phone not getting hot and no more lil glitches , cant wait for this kernel in few months it ran great on my nexus s !! But pretty badass for a new kernel from a dev that dont even have phone . THANKS !!
[Samsung Galaxy Nexus] gn00my:
Wakelock from your latest, is this normal??
[Samsung Galaxy Nexus] franciscofranco:
The 11/12 version?
[Samsung Galaxy Nexus] CaspaTheGhost:
The clue is the title, 4.03. Your ROM ain't.
[Samsung Galaxy Nexus] MasterLapa:
I don't know why but i was sure this kernel had retro compatibility >__> nevermind!
[Samsung Galaxy Nexus] DarkGruf:
I know and I never had this issue with previous versions, only with this one. I can set whatever governor/frequency I want and that works, but when I reboot I'm back to turtle 700-1000 in every case.
[Samsung Galaxy Nexus] franciscofranco:
You click set on boot right? And you have the latest app update? I just tried it again and it's booting just fine with my desired frequencies O.O
[Samsung Galaxy Nexus] DarkGruf:
Yes and yes !
[Samsung Galaxy Nexus] jan-willem3:
Test 4 is also ok not stability issues so far with heavy undervolt battery life is hard to tell.
[Samsung Galaxy Nexus] weirdg:
My router is doing strict 40MHz, and my GNex is able to connect to it. I'm also only running wireless N. No wireless G, wireless B, etc.

WG
[Samsung Galaxy Nexus] killyouridols:
I gotta say, I found anything after #8 not ideal for MY needs, but this latest one is spot on with gummynex 0.7.0. Excellent battery life and performance. Top work.
[Samsung Galaxy Nexus] clefster:
After having test3 die on me overnight, test4 seems to be stable so far (one night down :)
[Samsung Galaxy Nexus] slide83:
Has anyone tested if this kernel works with 4.04?
[Samsung Galaxy Nexus] StuMcBill:
Franco,

Thanks for all your hard work, I plan on flashing Test 4 later on tonight and see how I get on with it, but I wondered if the following would be possible, once you are happy with your dynamic hotplug of course.

Would it be possible (in your app, maybe via init.d scripts), to have one kernel with options for:

1. Normal Running (2 x cores work as if the device was factory fresh)

2. Franco Hotplug (CPU1 off when screen goes off)

3. Franco Dynamic Hotplug (CPU1 off when load < specified amount)

4. CPU1 Disabled (Maybe for extreme battery savings, at the expense of performance - could be used when you are going to be away from a charger for a loooong time)

Maybe this is something you have thought of previously, or maybe it is not possible?

Keep up the good work!!

Stewart