yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] CMNein:
I've always

assumed

it was a power issue in that there wasn't enough power supplied to wake the radio back up from sleep. Carrier doesn't seem to influence it, at least from my observations here, not to say it's not a potential factor.

IIRC Fugo does have a higher minimum clock speed (384?). I'm sure there's more to it as it seems like the Fugo mod dev has looked into the issue quite a bit.

As to why it affects one person, and not their neighbour, makes me wonder if it's another one of the theories I've seen here, when/where the phone was built.
[Samsung Galaxy Nexus] gravis86:
You people with the signal drop really need to do some more reading. It has already been confirmed that it is a flaw in AOSP code, and has to do with the kernel running not supplying enough voltage. That's why raising the minimum frequency fixes it (the voltage raises with the frequency) and flashing a different kernel fixes it as well (some kernels just run higher voltages than others). Due to minor differences and tolerances in manufacturing, some devices experience the signal drops and some do not. Just as some can over clock their CPU/GPU higher than others.

If you have signal drop issues, flash a different kernel until you find one that works. Otherwise, wait for the latest OTA source to find its way into CyanogenMod (and all other ROMs that are based off AOSP) and you'll be fine.

And before you ask, there is no ETA for when that will happen.
[Samsung Galaxy Nexus] brunoisa10:
sorry to ask but how to flash ? seen only wipe , so no factory reset ?

I have installed CWM.

I've read : need a CM9 kernel and I've read the FuguMod Kernel is the best for phone signal

Are GPS , Wifi and camera working ? I'm not sure , reading many pages
[Samsung Galaxy Nexus] mad_vtak:
So you're telling me even if I was stock 4.0.4 I'd have the same issue? I did raise the min to 700 and experienced it only once instead of multiple occasions. For now I guess I can wait since this temp work around seems to be doing better. I didnt want to seem like a noob and complain I was just asking the question.

I had this gnex for a total of two days and i came from NS with cm9 and had no issues.

Anyways thanks for the quirky but helpful update.
[Samsung Galaxy Nexus] gravis86:
Sorry, I wasn't trying to go off on you. It just seems that this thread has turned in a signal drop, kernel, and wake-lock thread instead of a CyanogenMod thread. The last couple hundred posts are filled with signal drop questions and answers. People just need to read them. It's all there.
[Samsung Galaxy Nexus] mad_vtak:
I do understand. They are having issues with this rom so its going to be brought up and asked. Others will come and try to assist while others tell them to rtfm

What else is supposed to be discussed in this thread?

"This rom is so effing awesome everyone needs to install this on their gnex"

"I love cm9 nightlies I wish I could marry it"

Have I proven my point yet or shall I continue? Things will be discussed as they should. People who are too impatient to read close to 300 posts will ask what is happening even though its already been covered 75 posts ago. We live in an imperfect world filled with people with imperfections.

Good day sir :)
[Samsung Galaxy Nexus] triStateMindgate:
Flash normally through CWM, if you're coming from a different ROM/Stock just do a Data Wipe for a good fresh install. Currently there is some issues with 4.0.4 Kernel source which is causing data signal issues with some users, flash a custom Kernel if you wish, ie Franco, Trinity, Fugu, Glados ....

Yes, GPS wifi , camera, everything is working, just some features,code,forward ports are still in the process of being merged, this will take time.

This is a daily driver for me, go for and try it, have fun.
[Samsung Galaxy Nexus] mad_vtak:
Speaking of the devil
[Samsung Galaxy Nexus] olus:
signal drops issues comes to stock phones with the 4.0.4 update one month ago. build number was IMM76D. Google fixes it one week ago with another 4.0.4 update. build number IMM76I. so when cm9 merge the new source code we will have the imm76i build.

so far i have no signal drops. my brother with same rom + kernel has signal drops. we are working together, so same area. and same provider.

it has nothing to do with cm9 itself.. it was the source code of imm76d!!

try market app: no signal alert. or look at settings - battery - mobil.. (dont know in english language).. there you can see how many time you got no signal.. ;)

greets
[Samsung Galaxy Nexus] wbknox:
If you can download franco kernel it already has current fix ( milestone 3)
[Samsung Galaxy Nexus] CMNein:
Was/is an issue for some people on 4.0.3 as well; unsure of quantities.
[Samsung Galaxy Nexus] heinz gruber:
Cant connect to 5 ghz wlan and wlan connection is lost in stand by. But Wi fi sleep is set to never.

Any idea?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] beekay201:
fugumod uses smartreflex, which dynamically supplies needed voltage to phone components, and currently has 345mhz as first step.

I'm one of the early adopters and when we first had uv control, it was clear to me that if i lowered 350 step to 825mv, i would get signal drops. Up it to 850mv, all good.

Sent from my i9250 using Forum Runner
[Samsung Galaxy Nexus] andybarronuk:
FYI ive 0% signal drop. 27s up! :D
[Samsung Galaxy Nexus] gravis86:
I have run many combinations of ROMs and kernels, and radios with this phone and none of them has ever had reliable 5ghz connection. I think it's either a hardware problem or something with the AOSP wifi drivers. I heard we're supposed to get updated drivers in the latest OTA so we'll see what happens I guess. Until then just run on 2.4. Throughput isn't that much different in daily use anyway.
[Samsung Galaxy Nexus] gravis86:
Since this in in the Development section (not the General section) I would expect this thread to be mainly about... Development!

I understand that this is where issues will be raised since it is where most people frequent (I myself have read every single post since this thread began, and I'm sure there are many other developers/know-it-alls that do so as well) and while I was a bit short with you, I did answer your question.

Even if I'm being a **** about it (sorry I'm on a short fuse lately due to work) I at least try to answer questions in an intelligible manner.

I'll try to be less of a **** in the future.
[Samsung Galaxy Nexus] mad_vtak:
Lol I see 27 I hope it fixes this issue
[Samsung Galaxy Nexus] brian_o'fish:
Just booted a new (self) build with sources of roughly today at 18 o'clock middle european time.

5Ghz WLAN works for me (don't know whether it was broken before, I have it disabled at the AP usually because it does not go as far as 2.4Ghz anyway). The fix for that is probably in the last two nightlies already; in any case here is the merged gerrit change of two days ago: http://review.cyanogenmod.com/#/c/15100/

Also newly merged, today: 2G/3G toggle! gerrit change is http://review.cyanogenmod.com/#/c/12820/ - looking at the date of that merge and of the 0427 nightly I'm not sure whether it's already in there. In any case, I have it in my tested build, and can CONFIRM that it works. If 0427 nightly doesn't, the next one should!
[Samsung Galaxy Nexus] mad_vtak:
I usually stay in the dark and just read these things lately, i just wanted to say that i went a head and flashed the 27 build. No drops yet, it usually takes a while before it happens. Lets hope it doesn't

Happy Dev'ing sorry to be a nu some if i was earlier. :)
[Samsung Galaxy Nexus] daewond3r:
Anyone know of a centered clock mod or if there's any plan to make that a setting in CM9?
[Samsung Galaxy Nexus] slg60:
CM team...please fix kernel. Overclocking to 1350 is not working. You can set this freq but it is not used and Performance is quiet bad then.....

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] lazaro17:
Yes I can confirm 2g/3g toggle works. I just flashed the new nightly. Also if you go into phone app and settings you can turn on vibrate on answer, vibrate on call waiting, and vibrate on hang up. Something I really liked from cm7!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ArmanUV:
Try reloaded ics:
[Samsung Galaxy Nexus] NCguy:
Its at least 2x as fast on my stock GN and my network gear - when it works
[Samsung Galaxy Nexus] SupWiz17:
How do you get the notification light to show the status of the data connection with cm9?
[Samsung Galaxy Nexus] colocynth:
I saw some red zones in my signal records during this early morning. Do they mean signal drops?
[Samsung Galaxy Nexus] colocynth:
There is a ui mod, ics reloaded, for cm9 in xda nexus dev.
[Samsung Galaxy Nexus] nexus.prime:
yeap

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

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gravis86:
Hmm. I get roughly the same speeds. It seems like the bottleneck is the device's ability to render the page. Actual data throughput (using speedtest.net app) is practically identical. And 2.4 has better range, anyway.
[Samsung Galaxy Nexus] mad_vtak:
Might want to ask this guy
[Samsung Galaxy Nexus] NCguy:
Even when i just turn off bluetooth, which interferes with 2.4, I see a wifi performance increase.
[Samsung Galaxy Nexus] joeyfong:
2g/3G toggle works on 0427 nightly
[Samsung Galaxy Nexus] matthian:
Confirmed on the toggle, kernel performance not fixed, but I installed Trinity... Perfect combo.

Still don't understand the stock kernel issue.
[Samsung Galaxy Nexus] ZiCoN:
0427 with latest Franco 384/1228/interactive, my phone have had the best performance and battery ever.... This is just awesome!! :)
[Samsung Galaxy Nexus] brian_o'fish:
I'm curious - how do you (and others) judge battery usage after only hours of running with a new install?
[Samsung Galaxy Nexus] ZiCoN:
Normally my phone drains around 10% during 7 hours of sleep, this combo has drained 5% over 10 hours with wifi on.

My whole system runs perfectly smooth, which it never has before, running under 700mhz minimum.

I know it's fairly soon to give such review, but my experience is that the system keeps running as initial, maybe even better after the system has settled.
[Samsung Galaxy Nexus] bemymonkey:
What exactly is the problem? Is it really slower than previous nightlies?
[Samsung Galaxy Nexus] mad_vtak:
Still getting data drops :o
[Samsung Galaxy Nexus] Gregus59:
When does CM9 up to the IMM76I ?
[Samsung Galaxy Nexus] mbroeders:
Never ask for eta's. But probably soon...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] olus:
they will update on april 31. ;)
[Samsung Galaxy Nexus] kyleds:
When will the led flashlight toggle work?
[Samsung Galaxy Nexus] olus:
led toggle on april 31.. maybe.. its only rumor ;)

when will the people here stop asking for ETAs?
[Samsung Galaxy Nexus] paratox:
when will kids stop asking silly questions?
[Samsung Galaxy Nexus] matthian:
Yes, it is.
[Samsung Galaxy Nexus] bemymonkey:
Seems fine to me. Any scenarios where the difference is particularly obvious? Or only benchmarks?
[Samsung Galaxy Nexus] matthian:
Started with the last nightly, feels really laggy. Benchmark only confirms.

With Trinity Kernel, only one I tested, everything okay again, feeling and benchmark.
[Samsung Galaxy Nexus] Gregus59:
Or the week of 4 Thursday !
[Samsung Galaxy Nexus] wbknox:
you must mean april 30, only 30 days in april.
[Samsung Galaxy Nexus] AlbinoAsian:
No they didn't actually
[Samsung Galaxy Nexus] brian_o'fish:
I feel no influence when normally working with the phone. The top CPU frequency is missing (1200 instead of 1350), but with the usual interactive governor and normal usage it's a rare event to run at top frequency anyway.

Benchmark scores are down 10%, as is to be expected for the frequency reduction.

This is probably caused by the kernel changes merged in three days ago - you know, the "google has made changes, when will we get them" stuff. Part of that was related to voltages and smartreflex, probably meant to fix other problems.

I'm sure the kernel developers are already looking at the issue, and eventually 1350 will return.
[Samsung Galaxy Nexus] xgrind:
This means you didn't get their sarcasm :D
[Samsung Galaxy Nexus] bemymonkey:
So not bad performance, just normal... something people who don't overclock won't even notice? Why is everyone *****ing then? :rolleyes:
[Samsung Galaxy Nexus] brian_o'fish:
Well, there were some people reporting vastly worse benchmark scores than what I could reproduce + report. No idea _why_ they had these, there was no more information in these reports.
[Samsung Galaxy Nexus] M3drvr:
They're probably running 10 home screens all filled with scrolling Widgets and running at 5% battery at the time. I'm running the 4/25 nightly. But no kernel gets same performance as stock for me.
[Samsung Galaxy Nexus] ZiCoN:
ZZZzzz........

Are you satisfied with your rom?

1. Yes - GREAT!

2. No - Try something else...

I just ran Quadrant and clocked 3016, which I think is pretty good considering default Franco settings, and on my 5 homescreens I have 4 scrollable widgets...
[Samsung Galaxy Nexus] tibere86:
Stock CM9 kernel or stock IMDD76I kernel?
[Samsung Galaxy Nexus] brian_o'fish:
Does Franco still go with the fsync() syscall shortcutted to do nothing? That improves Quadrant (in the I/O department) quite a bit, and if I remember my tests of a month ago correctly, is good for some 300-400 quadrant points in the end result.

I never liked that choice, though, and stopped playing with the Franco kernel when I saw it. Taking shortcuts on application safety knobs for the sake of performance, is not to my liking, when it comes to kernels...
[Samsung Galaxy Nexus] CMNein:
I see so many screen caps of Quadrant tests with an IO part of the bar being a mile long, other areas not improved significantly. Does this make a real world difference, or is it merely a means of improving an artificial benchmark score?
[Samsung Galaxy Nexus] L-ViZ:
i´m new with the nexus, got a problem with adw launcher ex, after 10min it doesn´t react anymore. someone know how to fix/solve this issue? downloaded yesterday the latest nightly. is there a possibility yet to deny access e.g internet for some apps?
[Samsung Galaxy Nexus] CMNein:
If you're referring to the Phone Goggles available in CM7 that hasn't been ported to CM9 yet. If you poke around in the Data Usage menu you can restrict background data globally, or for specific apps.

I've run ADW Ex briefly on CM9 (was my go to launcher on CM7) and didn't experience any issues; I find Trebuchet/Nova/Apex more effective launchers for ICS.
[Samsung Galaxy Nexus] ZiCoN:
I'm not sure what Franco does, to be honest.... I've played with a lot of kernels, and always go back to LeanKernel, but for the first time I feel that Francos has made my phone smooth and with great battery life.

I just tried AnTuTu and got 6293.

What I use quadrant for mostly, is look at the fps in the 3D section :)
[Samsung Galaxy Nexus] msmall22:
Hi I'm using tablet mode but have the following issue;

Great rom! I'm using ADW launcher and its great but I'm stuck with a menu bar at the top of the screen, any idea how to get rid of this?
[Samsung Galaxy Nexus] lazaro17:
Exactly...benchmarks can be easily manipulated. I remember cyanogen had posted a nice explanation about the whole faking a benchmark thing a while back. The IO part can especially fluff up your benchmark.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] brian_o'fish:
droidwall (installed from the market^H^H^H^H^H^Hgoogle play) works nicely. There is nothing built into CM right now that provides that functionality.
[Samsung Galaxy Nexus] M3drvr:
Considering its in this thread and people complaining about stock kernel lagging, probably talking about cm9 stock.
[Samsung Galaxy Nexus] mariotme:
New build is cooking. :)
[Samsung Galaxy Nexus] brian_o'fish:
Hot after KalimochoAz committed the fix for the missing 1350 Mhz CPU speed:

http://review.cyanogenmod.com/#/c/15362/1

I built in parallel, just tested, 1350 is working again, quadrant score (setCPU pinned to 1350) back to 2900 for me :)

Jenkins build is complete, new nightly will be up soon, as far as I can tell.
[Samsung Galaxy Nexus] CMNein:
The longer options for email check frequency are welcome as well; 2, 4, 24 hours now available. Great for my spam accts.
[Samsung Galaxy Nexus] lazaro17:
Anyone else having issues scanning wifi networks? Doesn't seem to scan at all and trying to "forget" networks does nothing either

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mariotme:
and its up and ready:

http://download.cyanogenmod.com/get...pdate-cm-9-20120428-NIGHTLY-maguro-signed.zip
[Samsung Galaxy Nexus] chubb16:
Is CM9 still losing service with the screen off? Did they merge the kernel source with Google's latest update yet?
[Samsung Galaxy Nexus] triStateMindgate:
The Kernel source has been merged
[Samsung Galaxy Nexus] mad_vtak:
I'm on the latest nightly and Franco kernel and I still drop signal.

Edit: I had to wait for signal as I typed this.
[Samsung Galaxy Nexus] triStateMindgate:
Try another Kernel,or try to raise your voltage, not everyone is experiencing the issue, and those who are, it varies. I for one, have been flashing CM9/Rascream with trinity/Franco (Different types of Kernels) and I never had one issue. But given that you have Franco flashed that cancels out the question of Kernel source being merged with stock CM9 because you're running a custom Kernel anyway.
[Samsung Galaxy Nexus] mad_vtak:
Changed CPU to 729 I'm not sure what you mean by voltage?

Edit: I also see that the imm76I is the one that fixes this issue. And the nightlies are imm76d

I shall try and find some kind of work arounds.
[Samsung Galaxy Nexus] triStateMindgate:
You can try setting min to 729 too, that deffinetly might help, the only difference from what I know between IMM76D and IMM76I is the Kernel fix, supposedly the voltage parameters are causing "some" users to experience a signal loss in the 4.0.4 76D build while screen is off. All current custom Kernels should have the new source merged, thus eliminating the problem. Again, every person might have a different outcome. ;)
[Samsung Galaxy Nexus] Schiehallion:
Feel uber on nightlies. **** off a shovel.
[Samsung Galaxy Nexus] ZiCoN:
I'm on the same combo, default Franco settings and have no signal drops what so ever. Do you have the Prime03 bootloader or the 01?

Since 0427 and 0428 I haven't had any signal drops.

Combo:

Latest CM Nightly

Latest stable Franco - Default settings 384/1228/interactive

Prime03 bootloader

XXLA2 radio
[Samsung Galaxy Nexus] Hussainally:
Omg the latest nightly is crazy fast... Don't need no different kernels.. Awesome stuff.. Tks Dev team
[Samsung Galaxy Nexus] hanschke:
why are the nightlies on IMM76D if the IMM76I is merged :confused:
[Samsung Galaxy Nexus] bemymonkey:
And the battery life on 04.27 is AMAZING. Over 7 hours of screen on time (extrapolated, of course)... looks like I might not be trading in my GN so quickly after all.
[Samsung Galaxy Nexus] Hessi93:
I have always had problems with wlan_rx_wake, the phone won't sleep while wifi is on. Is there any solutions? I'm currently running CM9 #0427 with franco.Kernel M3.
[Samsung Galaxy Nexus] bemymonkey:
Are there any kernels or even other Android devices that *don't* have wlan_rx_wake wakelocks? I'd always assumed these were unavoidable in Android (unless you're willing to not use WiFi at all).
[Samsung Galaxy Nexus] Hussainally:
I do have wx lan Wake lock but my phone sleeps really fine on stock kernel
[Samsung Galaxy Nexus] crachel:
It would be great if you guys who have changed to a 3rd party kernel would quit posting in this thread. Thanks
[Samsung Galaxy Nexus] :
Yes that would e really great !!!

OP says NO support for different kernel ! Its annoying because always when i take a look here its about some kernels!
[Samsung Galaxy Nexus] mad_vtak:
How do i know what bootloader i have?

my combo:

Latest CM nightly

milestone3 kernel

bootloader primekj10

XXKK1
[Samsung Galaxy Nexus] colocynth:
I use the same versions of cm and kernel. Set Wi-Fi always on when screen off. But my phone can go to sleep.
[Samsung Galaxy Nexus] Vangelis13:
Keep power button pressed - choose reboot - bootloader - ok. Bottom left of the screen.
[Samsung Galaxy Nexus] mad_vtak:
Thanks i got primekj10 bootloader
[Samsung Galaxy Nexus] joelteixeira:
Do you guys reach 1.350mhz on latest kernel? I set 700 min and 1350 max but I never hit 1350 (not even stressing with a benchmark). Checked with CPU spy and tried both ondemand and interative.
[Samsung Galaxy Nexus] stevesteveLA:
But the build number still reads 76D. I'm a bit confused...
[Samsung Galaxy Nexus] Carlos_Manuel:
I tried to install CM9 music player to GSB Galaxy Nexus Android 4.0.4 stock ROM but I accidentally installed CM/ ZTE Blade CM7 music player to my Galaxy Nexus! :D

Anyway does anybody know why CM9 music player lagging on Stock Android 4.0.4 ROM when listening music on CM9 music player..?

:)

EDIT: I Just found 100% working CM9 music player for my galaxy nexus stock ROM! :P
[Samsung Galaxy Nexus] AlbinoAsian:
Can you share a link... please :)
[Samsung Galaxy Nexus] Carlos_Manuel:
Here: http://www.theandroidsoul.com/download-cm9-music-player-ics-app/

before on ARHD 4.0 ROM I used other CM9 music player that was maybe from Galaxy Nexus s and it didn't work so fine:

But this works perfectly on my Nexus!
[Samsung Galaxy Nexus] AlbinoAsian:
It is fast! And no weird color problems now either
[Samsung Galaxy Nexus] M3drvr:
So what the build number says that? The kernel source has been merged. That's what you wanted. Sit down, shut up, and smile that the CM team keep putting out quality builds like they're doing. Maybe its still that build version for a reason. If the build is working be happy. Who cares if its older still and working flawless.
[Samsung Galaxy Nexus] stevesteveLA:
Not sure why the violent reaction. I wasn't complaining. I asked because I'm still getting signal drops.

CM9 ROM+ kernel, latest bootloader and radio.
[Samsung Galaxy Nexus] brian_o'fish:
It looks like there is still stuff being merged / prepared for merging. Today it is changes to the interactive governor, prepared but not yet merged, probably because the devs have some testers playing with it first.

The displayed build number is something separate from any incremental merging done on all the different components, and if I remember the 4.0.4 merge period correctly, it is changed roughly last.

Regarding the kernel stuff being incrementally merged, I think that that is a very good approach, giving more chance to catch problems and/or react when problems arise.

Unfortunately the process is not "open" right now in the sense of a plan being produced and steps documented on the way. Interested people would have to be developers comparing the kernel trees (or git repositories for other components, for similar cases), to judge whether stuff is done completely, or not.

Note that the "unfortunately" in the former paragraph, is not meant as a complaint - I'd rather have the limited crop of developers spend their time on quality code work than on producing overhead to keep the bystanders happy.

EDIT: just saw that behind the scenes, kernel was already updated to upstream 3.0.30 today! That's another thing I really really like about the gnex kernel development, that it tracks the long-term-stable vanilla kernel changes that closely, and thus profits from all kinds of security and correctness fixes to the mainline linux kernel.

EDIT2: built and tested a bit with the 3.0.30 kernel and also the interactive governor changes-in-the-works added in. No problems noticed. Top CPU frequency still 1350 :) Quadrant scores stable around 2900.

The changes to the interactive governor, especially the boost-on-screen-touched part... it's just so easy to fool oneself into seeing what one expects to see. So with that grain of salt I report: it's clearly again much snappier and faster to the touch!!!!

As I happen to have recently loaded up battery to 100% and replaced the extended battery I had with the normal one, I'll now try to run my "usual activity" three to four day test cycle, where I previously got around 4 hours screen on at about 60% wifi on, back in the 3.0.24 or something like that kernel days.