yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] slyydrr:
You're pretty close - the full way to tell is that the radio itself seems to turn off. Normally even when you lose reception, the radio remains on. However, with a full signal drop, the radio seems to actually be rebooting (for lack of a better understanding).

Here's the best way I can tell:

1) Clear battery stats and start the phone up while plugged in OR Fully charge the phone (which also wipes the battery stats).

2) At this point, the battery time in the main battery usage screen should match the "Cell Standby" time-on value.

3) If at any point the two values don't match, your phone experienced a signal drop. Obviously exclude any abnormalities caused by using airplane mode.

Hopefully this helps and as always, please keep me honest if you notice any different behavior. This is the way I determine drops aside from the visual method (signal bars disappear AND the data connection icon goes away - usually a drop but not always.)
[Samsung Galaxy Nexus] ludow:
Installing r159, will report. :)

//////EDIT

I am using interactive.
[Samsung Galaxy Nexus] ludow:
r159 - phone boots itself. Back to 158.
[Samsung Galaxy Nexus] renaud:
Thanks. Can you get a log (last_kmsg, logcat) or something? So far you are the only one reporting this, so that's quite hard to draw a conclusion without logs :)

I should not be the overclock because you are able to run r158.
[Samsung Galaxy Nexus] slyydrr:
FYI, no drops on r157 yet. I'll give it a couple more days.
[Samsung Galaxy Nexus] Gregus59:
I am on 163 and no problem for the moment...
[Samsung Galaxy Nexus] renaud:
While you are here :),

I am on r167 atm obviously (I am always running the latest), but I reverted to xxkk6 radio some time ago because the MLA1 gave me a noticeably bigger battery drain. xxkl1 was also giving me more drain than xxkk6.
[Samsung Galaxy Nexus] Macke93:
I'm always running XXKK6, best signal and low drain! :D

Just flashed #167, gonna try it out, I'll be back! :)
[Samsung Galaxy Nexus] Gregus59:
Hi, me I am on UGLA4 and it's definitely the best for me, try it, I just flash 167...
[Samsung Galaxy Nexus] mekanismen:
Not sure this is correct, but I feel like it should be... Under Battery Stats you have a detail called Cell Standby. Under that view you can see "Time without a signal", and if this is above 0%, you've obviously had a/some signal drop/-s.

Right?
[Samsung Galaxy Nexus] slyydrr:
Nope, that % value is very inaccurate. It actually represents the time the phone had 0 bars. I've tested this extensively because I was horrified at my supposed time without signal compared to my SGS2 but it's just a bad measurement. My tests included having 0% initially, walking into my office where I'm frequently at 0 bars and placing multiple calls, browsing the web, receiving multiple calls, etc. After I checked and my time without signal was at 15% (30 straight minutes of testing almost entirely at 0 bars).

Another way to look at it: time without signal represents the % of time your signal bar shows the distinct yellow associated with a very low signal.

Hopefully that helps clarify!

EDIT: Just in case people are confused - the issue of "signal drops" is actually more a radio drop. People will lose reception from time to time most anywhere which is normal. This issue is the radio itself turning off/on, as if going turning on airplane mode very quickly.
[Samsung Galaxy Nexus] ludow:
Hi again. Now r158 gave me reboot too, doh. :p

I wiped cache and dalvik now, installed Apex 1.02 and gapps.

I'll install r167 now. These problems might be just my phone/configuration.
[Samsung Galaxy Nexus] Gregus59:
168 all right for me... :D
[Samsung Galaxy Nexus] Macke93:
Have tested #167 for about one day now and it is stable! :D

Edit: Just downloaded #168 and gonna flash it now!
[Samsung Galaxy Nexus] Flukester69:
Holy macaroni I just updated the other day and now there's 168?!.. Cool! I'll throw it on in a few mins. I've updated about 3 times already and have never had a problem with this kernel. Best kernel I've used and now with 3.0.24 kernel.
[Samsung Galaxy Nexus] frankyyy02:
CM9 and Fugu 168 Onwards

Just started having an issue with CM9 and Fugu on my GN.

I now find when coming out of sleep the screen flickers between "normal" white and a dull "blue" colour (almost like an overlay). Have tried flashing between the latest and nighly Fugu, and even tried with and older CM9 nightly i had - all have the same issue.

Tried franco's Kernel and it works fine (although i much prefer Fugu's stability), and am now running stock CM9 kernel and it works fine.

Anyone else experiencing the issue?

Thanks.
[Samsung Galaxy Nexus] renaud:
Do you use custom gamma color settings? On which version did that appear?

I can see the screen a little bit blueish during about a tenth of a second when lighting the screen, but it's hard to notice.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] frankyyy02:
I first saw it on the current stable release. I do not use any gamma colour settings at all. If i customise the gamma settings, on occassions when the screen wakes without the blueish colour, its super white. It happens randomly about 50% of the time from wake.

This is a pronounced blue - almost hard to see the screen well.
[Samsung Galaxy Nexus] Macke93:
One question about kernels overall !

Why has my phone a hard time locking on to a GPS satellite when I'm out running and using Endomondo Pro app?

It's sad because last time 1 kilometer didn't count when I ran my usual route! :O

It happens with a lot kernels I tried, even franco!

/Macke

Edit: My baseband is XXKK6
[Samsung Galaxy Nexus] rashidi_zin:
How certain are you that it's due to the kernel and not the app? I have faced few situations where Endomondo or Run Keeper failed to detect or lost my location. I was not on either franco's or FuguMod.
[Samsung Galaxy Nexus] Macke93:
It's not the app! I just find this problem wierd, it should go easy to lock onto a sattelite with the GPS!
[Samsung Galaxy Nexus] zurchpet:
It's not the app, but the app is what is failing?

I can't follow your logic.

I just tested. Locked to 9 of 10 satelites in 15 seconds (outdoors). And kept it steady for 3 minutes. Then I turned off the GPS Status app.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Macke93:
Maybe it is endomondo! :(

Well, look at this, two printscreens from when I'm trieng to use it!

higher resolution!

http://img84.imageshack.us/img84/6972/29087538.jpg

Really wierd that it can show my position on the map, but don't show that it have locked to a sattelite!?

Please help me out!

/Macke

Edit: now after another five minutes it have locked to sattelites and shows GPS OK!

Really annoying :S
[Samsung Galaxy Nexus] Flukester69:
Spent good part of night stressing my phone and without a power source for 4+ hours last night I returned home with 27% battery before plugging it back in. Impressive, especially when you are out in the middle of nowhere. Ran all my apps and stuff and played a bunch of games. So far I got zero problems and I notice that this kernel is more speedy than previous releases.

Thanks again for a great release!
[Samsung Galaxy Nexus] renaud:
It locates you using cell towers and wifi signals. That's what is called coarse location.
[Samsung Galaxy Nexus] slyydrr:
Ran r157 for over 2 days without a single drop - now I'm moving on to r168!
[Samsung Galaxy Nexus] logi43:
Good afternoon here in Spain, I installed one of its kernels to test it with the r160 milestone rom-4 and OS ANDROID rose to 47% during the rest of the night and played for 27 minutes at rest, in the day to day dropped to 30% and is not moved, my question is, these levels are extremely high or on the contrary, nothing happens because they are so high the Android OS

The operation of the kernel is good in general terms at 8am and drainage was 3%

thanks
[Samsung Galaxy Nexus] fireon123:
Update on #157 and drops:

Had been running #157 with recommended bootloader and radio for a week without a single drop. Then all of a sudden I have had my 3G and data connection constantly broke (works a while after a roboot however, then fails again after a while) for two days. Flashed back to #148 and now everything is working perfectly again.

Please observe that, unlike previous drops I have experienced, I only lost my data connection and not my phone reception, I had full phone reception and was able to call out and receive calls the whole time. These random drops really bugs me out! :(

I am glad that I have the 148 kernel which I have as a backup, never had a drop with that kernel.
[Samsung Galaxy Nexus] renaud:
Did you try with the method to disable smartreflex core described in the OP?
[Samsung Galaxy Nexus] quietriot84:
Been having issues with radio turning off when phone went into sleep mode. Previously had to set cpu to 700mhz min, but after flashing r160 have not had any radio issues (or reboots or sof's for that matter) and I am able to leave the min cpu at 350mhz. Been using this kernel last couple days with AOKP M4 and loving it.

Thanks for whatever it was that you did in r160 :D
[Samsung Galaxy Nexus] frankyyy02:
Blue Fade

Tried the latest stable after a full wipe and reinstalled CM 9 on my GN. Same issue still occurring. After a screen lock, when waking, screen starts normal and within a second fades to a blue overlay look and cannot get it back. Occurs practically every wake.

Using stock CM kernel for now but battery life and smoothness better with Fugu.
[Samsung Galaxy Nexus] renaud:
If you take a screenshot of the screen when it is blue, is the blue visible on the screenshot (when viewed on your PC of course :))
[Samsung Galaxy Nexus] frankyyy02:
Nope does not. Looks fine. ;)
[Samsung Galaxy Nexus] renaud:
Do you have the recommended bootloader? (see OP)
[Samsung Galaxy Nexus] frankyyy02:
Yep updated BL and radio last week to current latest.
[Samsung Galaxy Nexus] fireon123:
No, unfortunately I did not. But 148 is working great still! =)
[Samsung Galaxy Nexus] renaud:
If you do and it proves to be working great without problems, I may enable it by default

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] frankyyy02:
After a fair bit of testing, flashing and reflashing, I can now confirm that I started experiencing the fade issue with 160. 158 works perfectly. I also seem to have the issue with AOKP M4.

It seems that if I press volume rocker or power buttons to take screen out of standby, and wait 5-10sec before pressing the slide unlock, I can see the screen fade to a grey/blue overlay colour. It's almost like its underpowered. It fades up and down between a few shades. Once I unlock, it almost certainly stays faded until I relock the phone and repeat the process and unlock before it fades.

Stock CM9 kernel and franco kernel still seem to be fine. As above 158 is also ok.
[Samsung Galaxy Nexus] da900:
Nikademus, any chance to get UV in your kernel or manual voltage control?

Sent via Tapatalk.
[Samsung Galaxy Nexus] renaud:
I will take a look and try to see what changed between those 2 released which may cause this

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] renaud:
There is already UV, it's just automatic, managed by smartreflex. you will not get manual UV because all it does is cause problems without any benefit and I want my kernel to be stable.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] da900:
Thanx

Sent via Tapatalk.
[Samsung Galaxy Nexus] beekay201:
had one drop on #158, like i reported earlier. did not happen again, did not "echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp". i have a pretty good network coverage pretty much wherever my normal routine takes me, and normally always run on data call/edge, so i don't know if it happened again but i just didn't see it.

if it drops signal totally, it should display it under Settings > Battery Stats, Time without signal percentage right?
[Samsung Galaxy Nexus] frankyyy02:
Thanks. I'm baffled :)
[Samsung Galaxy Nexus] renaud:
177 has color multipliers

178 is based on Linux 3.0.25-rc1

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] frankyyy02:
Just a quick query for anyone running CM9 and Fugu. Are you able to change governors? Mine is currently set on interactive and I cannot seem to change to conservative or on demand. When I try the setting does not seem to change.

Is this by design?

Thanks in advance.
[Samsung Galaxy Nexus] zurchpet:
Indeed. mine stays in INTERACTIVE too when changed in Performance settings...
[Samsung Galaxy Nexus] frankyyy02:
Cool thanks for the info. ;)
[Samsung Galaxy Nexus] renaud:
I have to change a permission in the initramfs for this to work

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] odin13:
I'm running fugumod 178 on latest nightly...no problems changing governors here. Conservative/ondemand profiles working fine for me

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] renaud:
Yes, it only happens on cm9 with the integrated menu. You can change governor just fine with any app asking for root

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mennozon:
changing governors works for me with this kernel and CM9
[Samsung Galaxy Nexus] beekay201:
read nikademus last two posts.

#178, can't change governors through Settings > Performance > Processor in CM9 latest nightly as of 03/18/2012 UTC 01:54pm (update-cm-9-20120316-NIGHTLY-maguro)

does #179 have http://t.co/pshbs3bh in it?
[Samsung Galaxy Nexus] renaud:
Yes that's 179 :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slyydrr:
Nope, and that's a common misconception. Take a look at my post clarifying on this a few pages back :)
[Samsung Galaxy Nexus] renaud:
That should be solved if you use r179 from now on. Given only the initramfs has to be changed, it's still called r179, but is different from the one before.
[Samsung Galaxy Nexus] frankyyy02:
Thanks - great work!!

Following my previous posts regarding the screen fading grey/blue upon taking the phone out of wake. Tried r178 last night with the same issue again. From the OP, i ran echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp.

It seems to have fixed the issue. No more screen fades!

Looking at previous posts - it was recommended for radio drops, of which i did not experience.

Can you shed any light why this would differ to r158 which was the last version i did not experience this issue with?

I assume this is something i will need to do following each kernel flash?

Thanks again!
[Samsung Galaxy Nexus] renaud:
What you did is disable smartreflex (automatic UV) for the core board. It seems smartreflex fives some problems on some phones. This may be due to a bad batch. I will add your issue to the OP.

It seems enough people have problems, so I will probably do a version of the kernel which disables smartreflex for the core.

You need to do that at boot time.
[Samsung Galaxy Nexus] franciscofranco:
Why does this is only affected by core smartreflex and not mpu or iva?
[Samsung Galaxy Nexus] frankyyy02:
That would explain why my battery is looking like crap today :)

Using double what it normally would to be honest. I may have to go back to r158 if battery continues this way.

Thanks again!
[Samsung Galaxy Nexus] renaud:
It should not consume more than 158.
[Samsung Galaxy Nexus] renaud:
Probably because mpu and iva voltages are independent from the screen or the radio.
[Samsung Galaxy Nexus] Gregus59:
With 180 I have an amazing battery life... :D
[Samsung Galaxy Nexus] renaud:
r181 is linux 3.0.25 final.

Technically, there is no change between 3.0.25-rc1 and 3.0.25 apart from the numbering.
[Samsung Galaxy Nexus] beekay201:
nikademus, saw this commit, is it possible to have kernel shutdown wireless chipset to save power?
[Samsung Galaxy Nexus] renaud:
It's in the kernel for quite a few releases now.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
:D

Another question nikademus.. Like wifi, would it be possible to shutdown power to other components when not in use.. like screen or nfc? :D
[Samsung Galaxy Nexus] renaud:
r184 has the newest wifi driver version 6.10.67.2

before, it was 5.90.195.35
[Samsung Galaxy Nexus] renaud:
They should already go down :);)
[Samsung Galaxy Nexus] beekay201:
i think i'm flashing this at work :D

:cool:
[Samsung Galaxy Nexus] comelus:
Hi. Anyone had lost the phone signal with the kernel r180? Thank
[Samsung Galaxy Nexus] Gregus59:
No problem...
[Samsung Galaxy Nexus] beekay201:
had a freeze today with #184, just pressed install (Google reader from GPlay), all froze (nav buttons etc). Tried power off 10s to no avail, battery pull always as a last resort for me!

Fresh install of cm nightly (20120319) + fugu#184, on wifi.

Weird or not, after getting back in, Android had a notification for me, google reader had been installed already.
[Samsung Galaxy Nexus] Sdobron:
Were you able to pull a kmsg?
[Samsung Galaxy Nexus] beekay201:
Unfortunately no, I was not near the pc.

Today, device immediately rebooted when turning wifi off. :(

Why this stuff always happen to me when I'm not near a pc that I can use to get logs I don't know. :mad:
[Samsung Galaxy Nexus] Flukester69:
I had same thing. Wifi was weak, mobile data off and I was loading a page and it just totally froze. Have never had a problem until now. Had to pull battery, I don't know if there is some power button sequence to force reboot. I'll see if I can grab log if it helps.

fugumod #184

aokp build 28 (upgraded from m4)

radio XXKL1

nova launcher prime
[Samsung Galaxy Nexus] sakuhei:
Just got frozen when browsing with stock browser

freshly flashed modaco 4.0.4
[Samsung Galaxy Nexus] Flukester69:
If it happens again, I might fall back to #181 as I didn't have problems with that. I got my kmsg and dmesg but I don't know if it goes back enough to when it hung. I don't just want to attach blindly without knowing if there is any private info in the logs.
[Samsung Galaxy Nexus] franciscofranco:
Don't worry it's just kernel logging output.
[Samsung Galaxy Nexus] Flukester69:
K I will attach them shortly, thanks
[Samsung Galaxy Nexus] chiensibut:
i have a question... so there is a problem with 184?? i want to update but i want to mess up my phone again.
[Samsung Galaxy Nexus] Kelvino9:
r184 has been flaky for me too. When connected to WIFI everything is good, but once on 3G I get frequent spontaneous reboots until I'm conneted to WIFI again. r181 was flawless so far.
[Samsung Galaxy Nexus] Flukester69:
Just curious Kelvino9, what radio version are u running?
[Samsung Galaxy Nexus] renaud:
I pulled r184 until I understand what happened.

I am unable to replicate the issue, so logs would really help. Please also try r189 to see if it solves the issue.
[Samsung Galaxy Nexus] renaud:
I have now replicated the issue using speed test and switching wifi on/off

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
Will do when I get home. Thanks for your hard work nikademus.

Sent from my Transformer Prime TF201
[Samsung Galaxy Nexus] Sdobron:
No issues here with 184. Rock solid all day with XXKL1 radio. Btw wiped dalvik and cache.
[Samsung Galaxy Nexus] yohinomura:
R189 also has same issue as r184
[Samsung Galaxy Nexus] Flukester69:
I switched back to 181, I don't want my phone crapping out at an inopportune time.
[Samsung Galaxy Nexus] Kelvino9:
I used every FuguMod Kernel on XXKL1 and tried r184 on XXKL1 and UIKL3 with the same results. I'm running r189 on XXKL1 now, but haven't checked if it auto reboots while on 3G.
[Samsung Galaxy Nexus] Flukester69:
I can't say for me it hangs on 3G but if it's been sitting inactive for a while and then I go launch something it would just sit there unresponsive, hang or just lock up the phone. I'm just gonna stick with 181 until the problem is ironed out.
[Samsung Galaxy Nexus] Sdobron:
Did those with issues wipe cache and dalvik? I've been streaming last FM all day on 3G. Been on and off Wi-Fi since yesterday and been switching between 2G and 3G modes with not one reboot. Flashed this kernel yesterday morning. Running AOKP latest build and XXKL1.

I think your issues are not completely kernel related, post last kmsg after next reboot.
[Samsung Galaxy Nexus] Flukester69:
Never did that myself but then since like 158 I just applied ROM and no problems. So I would suspect it is something in the kernel that changed and caused the problem. Why switching back to 181 without any cache wipe is everything working wonderfully again? It's not the end of the world and I expect them to figure it out.
[Samsung Galaxy Nexus] odin13:
Nika will fix this issue without any doubt...

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] beekay201:
No need to wipe cache or dalvik when flashing a ROM (cache/dalvik gets rebuilt everytime you flash a new rom, as it has different HASH signature than the previous rom), and I flashed every other build of fugu (without wiping anything), and never had any issues because of it.

I don't have an issue with 3g/2g, I have issue with wifi, i think it maybe because of last update to wifi driver.

Sent from my Transformer Prime TF201
[Samsung Galaxy Nexus] renaud:
Yes, I will have a look tomorrow, today I was away looking old Alfa Romeo.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kelvino9:
Yes, always wiping cache and dalvik before flashing anything system related. r189 din't changed anything either so I went back to r181 with no issues so far.
[Samsung Galaxy Nexus] beekay201:
Was downloading #181 on wifi from nikademus mirror. All of a suden, phone got real slow, then responded with a signal drop, and then rebooted itself after a few secs. After reboot, notification pending "Download unsucessful".
[Samsung Galaxy Nexus] Flukester69:
Yep that is my suspicion as well.
[Samsung Galaxy Nexus] franciscofranco:
Wiping cache and dalvik has nothing to do with the kernel.
[Samsung Galaxy Nexus] franciscofranco:
I took a look into that dmesg and saw it crap itself:

[79650.305328] PVR_K:(Error): PVRSRVSwapToDCBuffer2KM: Failed to get space in queue [1714, drivers/gpu/pvr/deviceclass.c]

INFO: rcu_preempt_state detected stall on CPU 0 (t=7680 jiffies)

L3 standard error: SOURCE:IVAHD at address 0x61c0c MSTADDR=0x0 hdr=0x804

More than that I dunno, I only looked at the log.
[Samsung Galaxy Nexus] beekay201:
it's not that i can't bear with it, but this time (happened again later at work) i had to pull out the damn case and the battery to get it running again. i'm sure it will be temporary :)

Sent from my Transformer Prime TF201
[Samsung Galaxy Nexus] renaud:
Please try r190.

If you had crashes, please wipe cache too when installing it.
[Samsung Galaxy Nexus] mekanismen:
I'm not sure if this is worth mentioning, but after flashing r181 my color multipliers were doubled on startup, and the screen was insanely bright. I'm on AOKP B28.
[Samsung Galaxy Nexus] Kelvino9:
Didn't had that problem going back from r189 to r181. Will give r190 a shot.

Edit: r190 works without a problem. Tested it on two radios.
[Samsung Galaxy Nexus] beekay201:
+1

Thanks nikademus, will report back.

Edit: #190 seems ok, toggling wifi on/off while speedtesting and it holds its ground, no crash. Also tried downloading a file (again #181 :p), installing an app from market then turning wifi on/off while downloading, no crash to be found so far. :)
[Samsung Galaxy Nexus] renaud:
thank you for the report. Can anyone else confirm?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yohinomura:
Confirm working fine.
[Samsung Galaxy Nexus] franciscofranco:
What was the problem by the way?
[Samsung Galaxy Nexus] manager77:
r190 works good..no more freeze and reboots.Thanks!
[Samsung Galaxy Nexus] Flukester69:
Yep running 190 too, no problem so far. When my wifi has a really lousy connection it doesn't affect my phone anymore. 4.5 hours, playing games, cruising net, installing and uninstalling apps etc. Thanks Fugumod dudes!!
[Samsung Galaxy Nexus] renaud:
Wifi driver v6

Sent from my Galaxy Nexus