yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] apsis:
@Franco

The Data Drops appeared to me somewhere in the 15x nightlies and dissappeared since nightly 999. It's back for me since Nightly 163.

Issue:

Turn on the screen while device was on deep sleep for a while and i sometimes see that the "H" symbol or whatever it was connected to before dissappeared, also the Connectivity Bars have dissappeared and the Bar-Background went gray. It needs about 20 Seconds to reconnect. I often receive Messages from Whatsapp after the screen is turned on and Data Connection is established again, so i guess the issue starts when the Device enters Deep Sleep, not when its coming up from Deep Sleep.

Galaxy Nexus

Liquidsmooth 1.4 (Issues have been there on LS 1.3 too)

Issues appear for me on : Franco Nightly (all 512 Mhz GPU) 163, somewhat in the 15x

Radio: SC04DOMLA1 (tried XKK6, LA04,KRKL1 and a few others i dont remember anymore) but issues stay the same

Franco App Settings:

Interactive / Ondemand (tried both, issues still the same)

Min. CPU 384 Mhz (tried 729Mhz a few days but didnt solve it)

Max. CPU 1228 Mhz

Generic Hotplug: disabled

CPU Mode: Dual Core

Profile: none

Undervolted: yes (but tested without undervolt a few days too on 15x build, didnt solve it)

Smartreflex activated: yes

Rom Control:

nothing related

Powersave Mode: disabled
[Samsung Galaxy Nexus] Theshawty:
Is that command supposed to boost signal speeds?after typing that my signal boomed up to two bars from a steady zero.
[Samsung Galaxy Nexus] metalspring:
It changes the way the phone sleeps and is supposed to keep deep sleep from killing the signal
[Samsung Galaxy Nexus] franciscofranco:
Can you try the command that I posted on top of this page and see if it fixes it?
[Samsung Galaxy Nexus] thoth_19:
No warning at all on miui since its a port but makes complete sense. Lesson learned. ^_^

*Sent From My Miui'd GNEX*
[Samsung Galaxy Nexus] metalspring:
Btw I'm noticing graphical glitches right after a reboot now on r165 512 gpu...I never had issues with 512 gpu before either....

I'm Not sure if it's just because I'm doing something different (flashing lots of fonts in recovery so lots of rebooting) or if you changed anything that might cause this?

Mainly what's happening is I'm getting tons of artifacts for the first 30-45 seconds after rebooting
[Samsung Galaxy Nexus] apsis:
@franco

Can I type it straight into terminal emulator? Cause adb isn't working for me
[Samsung Galaxy Nexus] franciscofranco:
I haven't messed with voltages :)

Yes you can.
[Samsung Galaxy Nexus] Flukester69:
Yes until my post got blown out of proportion I was going to say same. When I thought back I think this problem was noticeable more around the 150 nightlies. My phone blanks out for 5 mins or more and my signals drop and go gray until I start figeting with apns and my other wireless network as soon as I messed with system setting the connection restored.
[Samsung Galaxy Nexus] franciscofranco:
Can you try the command I posted last page please.
[Samsung Galaxy Nexus] LifeInAnalog:
.. Tried the command in Terminal Emulator and got back "permission denied" for my trouble. Damn android. Never had these problems with my rotary phone in the 1970s.
[Samsung Galaxy Nexus] Sveke:
Shout in the dark here but here goes....Is anyone having data drops on any other ROM besides liquid and cm9?

just curious?
[Samsung Galaxy Nexus] Claus1221:
@LifeInAnalog: Try executing "su" (without the quotes) before, that grants superuser rights

@franco: My signal got a two bars boost as well, awesome, thanks! Do I have to retype this command after reboot or does it stay?
[Samsung Galaxy Nexus] franciscofranco:
Two bars boost!? I wasn't expecting that. Yes, for now. Lets confirm this behavior I'm curious to see if that fixes the random drops. If we can confirm that then I'll fix it in the next build.
[Samsung Galaxy Nexus] LifeInAnalog:
@sveke...AOKPm5

@claus1221.. Ugh.. I just figured out how to get the blinking clock on my VCR to stop, and you expect me to remember superuser? Thanks. Will try again.
[Samsung Galaxy Nexus] nodstuff:
165 works great!!!
[Samsung Galaxy Nexus] isinisterx:
Thanks
[Samsung Galaxy Nexus] LifeInAnalog:
... Well, 10 minutes and no lessening or dropping of signal... But that could just be my positive vibes, man.
[Samsung Galaxy Nexus] Claus1221:
I have to say that I live right between two send masts and the signal bar randomly jumped between one and two bars no matter whether I've been moving the phone or not. This time the bars jumped from one to three bars, so some impact is probably caused by my bars of randomness. Nontheless I defenitely got a noticable improvement.
[Samsung Galaxy Nexus] shohratshankar:
Can you please explain how to do this, I'm a bit of a noob. Is it in terminal emulator? Exactly what do I type there?
[Samsung Galaxy Nexus] Claus1221:
You open your terminal, then type "su" (without "") and hit enter. If you haven't been doing this before, confirm the superuser rights for the terminal. Then you just type the command above exactly as shown and hit enter again, that's it.
[Samsung Galaxy Nexus] sing1gnis:
Upping the wlan voltage on r165 fixed my wifi dropouts. Thanks Franco. Keep up the great work!!!
[Samsung Galaxy Nexus] nklenchik:
Great idle times on 165
[Samsung Galaxy Nexus] superbobup:
I didn't have any cell drops but tried it out. It may have boosted my signal about 2-4 dBm but this boost may also be due to some other things. No real noticeable difference
[Samsung Galaxy Nexus] nklenchik:
Has anyone undervoted the IVA and Core voltages successfully?
[Samsung Galaxy Nexus] LifeInAnalog:
.. I'll say, tentatively, that after the command, signal drops have improved. Upon waking the phone, the bars are grey, but fairly quickly turn blue again.

I'm assuming that this command will need to be entered every boot? Can we make a script to run at boot? Or, will a future release incorporate this "fix"?
[Samsung Galaxy Nexus] Lambetts:
Random question....

I flashed M3, I thought I'd try a 'clean' flash from recommendations from some users here. Sounded great to me. So I extracted boot.img and flashed via fastboot. Weird, straight after its like I'm getting battery usage like stock. Pretty bad. I gauge 'standard' batt usage like 5% is normally about 15mins screen time. I'm barely hitting that unfortunately.

I love your kernel Franco, I bought your app really just to say thank you. I haven't used it extensively yet as I still get choppy calls on it occasionally. If I switch to glados or something, it goes away but of course I lose the awesome performance, and normally better battery life.

So, what I'm really saying is, should I flash from zip in CWM instead of just the img file in fastboot? Or is there absolutely no difference, scripting it otherwise?

Thanks for your time and patience guys.

Sent from somewhere....
[Samsung Galaxy Nexus] Keyser.Soze:
It's a bit strange for me. After running the command, I started getting dropped signals after idle. I restarted the phone and all seems normal...

KS
[Samsung Galaxy Nexus] drawde40599:
Answered ONE page back;)
[Samsung Galaxy Nexus] Culex316:
I was too quick to blame my sudden quick battery drain on this new build....I switched to ondemand from interactive and that seems to be a bit easier on the battery now..
[Samsung Galaxy Nexus] drawde40599:
165

Build 165 ( 512 ) liquid 1.4, 100% stock Franco settings screen 75% bright, GPS on, data on, Gmail sync on

Battery drain I had for some reason on 163 is gone got the my normal 3.8 hours with 9% left

Ran perfectly smooth, very fast no hiccups at all

Not one data drop, wifi works perfect

No SoD

No reboots

Phone never go's over 53°c (Franco app) unless on charger then 59°c

No issues I like this one the best out of the " 160's"

Thanks Franco
[Samsung Galaxy Nexus] LifeInAnalog:
... Oops, thanks. I have lousy short term memory ;-)

... UPDATE: Started getting drops again, seen Keyser.Soze's post so did a reboot and things seem perfect now. Didn't even reenter the command. Weird.
[Samsung Galaxy Nexus] Flukester69:
I guess I will try reboot but left phone alone for 10mins or so and picked it up both signals gray. Took minute or so go active.
[Samsung Galaxy Nexus] drawde40599:
Not saying u don't have an issue, but don't grey bars mean ur just not connected to Google servers? I thought I had similar issue on one of my phones and logging on and out of gtalk fixed it . I don't remember but may be worth Googling it ...
[Samsung Galaxy Nexus] Lambetts:
Bump

Sent from somewhere....
[Samsung Galaxy Nexus] navodwickra:
AFAIK theres no difference. But to be honest 163 and 165 is far better than M3 for me. Try one of those first.
[Samsung Galaxy Nexus] Flukester69:
You are right I clicked on Google+ and it actually gave me some security prompt for some webui update my icons went blue.

Edit: This didn't resolve problem. As I write this both wifi and data are gray.
[Samsung Galaxy Nexus] duowing:
I've been on 165 all day today. I was using 163 before they've both seemed to be very good on battery life as well as performance. I haven't noticed any signal drop other than the usual areas at work where I have poor to no service. I'm finding 163/165 to be a lot better than Milestone 3.
[Samsung Galaxy Nexus] Lambetts:
Now I'm having some serious data issues. Wifi especially. Not working, working, not working. Weird. Blue bars and everything, just stalling on pages, xda, everything. Reboot, works for 10mins then goes back to this. ****, I just can't win with this kernel. Its like it doesn't matter why I do or what rom or radio, my phone seems to just hate this kernel!!! Arghhhh! Hahaha.

Sent from somewhere....
[Samsung Galaxy Nexus] drawde40599:
Cool!! Ya Living in alaska and " crack flashing"since cm5, I have all kinds of useless info I've accumulated over the years ; )

Is crack flashing considered a hobbie; )
[Samsung Galaxy Nexus] Hanny:
lemme explain the phenomenon i see instead of just telling "data drops":

so the E/G/3G/H/whatever data icon is gone on the signal icon

because wifi is also turned off, phone failed to connect to google and icons become grey

the entire triangular signal icon becomes empty, and a cross "X" at the left bottom tip of the icon - which means the entire signal has completely gone

after 10 seconds, the basic phone signal comes back, which is without any of the "mobile data" icons so the 4 full bars of signal icon is grey

after 20 seconds (since signal loss), E/G/3G/H text comes back and my phone connects to the mobile internet, the signal icon is blue now

happening frequency - 4-10 times a day

signal loss DURING screen off? - NO, i get all my whatsapp, facebook, messenger, messages, phone calls DURING screen off. none missed nor receive a bunch when screen on

my setup in sig

recent nightlies? yes - it was really since the time that around 160 or 161 comes out. 160 gave me a really good impression though so i think it was since 161

come out from deep sleep? - yes, generally the signal drops happens when i turn the screen on

however - i today coincidentally found that the device doesnt really need to be in deep sleep to make this happen. because i was all the way playing music on speaker with Google Play Music app, turned the screen off for about 2 minutes, when i turn it on (the music is still playing), the signal icon is empty with an X. then the recovery process does the same.

oh, thought my signal drops were because of other environmental factors, but it seems not when reading so much reports and i got them quite frequently these days.

have done your command and will report back after some times :) thanks franco

oh and i have seen someone asked - no you dont need to worry about making a script for yourself or whatever. because this is gonna be temporary and franco said he will make a fix upon his conclusion on the next nightly. for now if in some cases you need to reboot your phone frequently and find the command annoying to recite, get tasker and make it run task Misc > Run Shell (type the command in)(rmb to check the root option) after boot completes.
[Samsung Galaxy Nexus] duowing:
Also I don't know if it matters but I use the jBroid Kernel Cleaning Script before I flashed my first Franco Nightly. Also when I installed CM9 I went to Mounts and storage and formatted /cache, /data, and /system twice each so everything would be nice and wiped. I think I even did factory reset after installing CM9 and gapps. Everything has worked exceptionally well. Franco's kernel also fixed my problem of the phone not going into Deep Sleep when on WiFi with the stock CM9 kernel
[Samsung Galaxy Nexus] drawde40599:
Wifi settings, forget network, reboot, redo network, happened to me on 163 did that and no issue since . Maybe just a quincedence or maybe it did something?? I don't know but not an issue anymore for me hasn't happen since maybe work for you 2??
[Samsung Galaxy Nexus] BigBake88:
Are any CDMA brothers getting these data drops? I have not experienced one. Seems to be only GSM guys. R163 has been awesome today with LS 1.4
[Samsung Galaxy Nexus] Flukester69:
Well both my signals are gray on latest nightly but I am able to use network. I see 3g etc and the wifi send receive.
[Samsung Galaxy Nexus] Dr Byte:
Data drops? Default network protocol (GSM/WCDMA)

Just in the last few days I've noticed my phone in "Edge" mode now and then. I've just been investigating the why...

...every time it boots, it changes from "WCDMA Preferred" (in the info page) to "GSM ONLY" even though I change it back.

I couldn't remember it doing this in M3, so I flashed that back. It does exactly the same thing (reboots in GSM ONLY).

The only other thing I've done is switching between the TDVKK6 and XXLA2 radios, which seems the next likely thing to check out. I reverted to the Telstra radio just after upgrading to yakju 4.0.4 a week or so ago, and still haven't seen any performance difference... BOTH can be very poor, even when on WCDMA. Both can be good, too. I'm blaming cell congestion.

However, I have a thought for those experiencing "screen-on data drops."

Are people experiencing this when in/leaving/entering a Wifi coverage area? In GB, I had the "Wifi Sleep: Never" set, along with "PM_FAST." Now, ICS is set the same way on my yakju 4.0.4 phone - though they changed the logic, it's now "Keep Wifi on during sleep: Always"

Until the last few posts, I thought people were referring to what happens when you wake the phone IN a known wifi network when it's been more than 15 mins since it was awake - that is, the Wifi connection went to sleep and fell back to 3G. Waking it up after that period will make the phone flip back to Wifi.

However, it seems there's more to it than that - but it bears consideration. I'm going to try the telco-specific radio now, and see if it still boots in GSM ONLY mode.

Update: Radio and Kernel made no difference - it always started up in GSM ONLY mode. In desperation, I tried GSM AUTO (PRL) and lo! The next time it booted it came up in "WCDMA Preferred" mode. ie, NOT the mode I actually set it in, but the mode I actually WANTED it in :)

Also: with the tdvkk6 radio, I'm now getting about -75 to -81dBm at my desk instead of -90 to -111 dBm. Even more reason to stay on it.

Hope this all helps someone someday (I've included the magic keywords so that 'search' button that so few people use, will find it :) )
[Samsung Galaxy Nexus] nklenchik:
None here, and I'm running 192 as my min frequency
[Samsung Galaxy Nexus] daddymatt:
Then that probably means you're not connected to Google...
[Samsung Galaxy Nexus] jnr21:
Hmm, what radio is tdvkk6? Test xxkk6, it solves data drops for me.
[Samsung Galaxy Nexus] Theshawty:
Exactly. Gray bars only mean you're not connected to Google. Why some seem to think it makes you completely lose network access is beyond me.
[Samsung Galaxy Nexus] xyzulu:
I tried 165 today.. lost data when unlocking the phone, this happened repeatedly. I was out, so flashed back 163 and the issue went away. Not had time to test more, just providing my feedback here on 165.
[Samsung Galaxy Nexus] Dr Byte:
xx is for Europe (typically 900/2100Mhz), dv is for the Oceania market (850/900/2100). TDV... is the carrier-specific variant of dvkk6. In theory, the only difference between the xx and dv version is the frequency preference/"tuning" and market tweaks.

Given no real downside, I'm inclined to use the carrier-tuned radio except when testing. In theory at least, it has been tweaked to a slightly higher SAR for better coverage. In practice, I can't pick a difference between tdvkk6 and xxla2. Any differences are attributable to cell congestion (lousy [1MB/s] in the late afternoon, great in the wee-small hours [3-5MB/s] at the same desk). Same phone, same boot, same hand hold.

I don't get data drops, touch wood :)
[Samsung Galaxy Nexus] Lambetts:
Thanks man. This is so frustrating, I really, really want to use this kernel but usability gets in the way. Wifi still weird. Slow page loading, or not at all. Xda doesn't work, then it does. I went on Mobile data, its fine. I thought it was a server issue. Can anyone recommended anything? Its unfortunate. Some people don't have a drama but the Franco kernel for me?? Bad phone calls, bad wifi connectivity etc....so strange.

Thanks in advance guys.

Oh BTW, using M3.
[Samsung Galaxy Nexus] 0kk0:
Wat is your setup? With stock Battery?
[Samsung Galaxy Nexus] atsavlis:
Could the europeans tell me what they have been running as far as radio and baseband is concerned? Im on xxkl1, is the change to xxla2 recomended?
[Samsung Galaxy Nexus] drawde40599:
Yes
[Samsung Galaxy Nexus] T-Loop:
I have constant signal drops with xxla2. I use KK6 currently, seems to be more stable but still has drops sometimes.
[Samsung Galaxy Nexus] nklenchik:
He got 2.5 days and 4 hours screen on time? I highly doubt that
[Samsung Galaxy Nexus] Theshawty:
Francisco, I'll see now if I have signal drops or not now. I flashed the XXKK6 radio and the matching interface layer for it.
[Samsung Galaxy Nexus] gknnn':
**battery_franco**

ROM : CM9

KERNEL # : 165

GSM/VERIZON/SPRINT ( 3G/4G/.... ) : GSM

BATTERY TYPE : 2000

BATTERY LIFE/SCREEN ON : 17h 11m / 7h 2m screen on

BRIGHTNESS : 50% on day, at night full down

MINFREQ: 192 / MAX FREQ: 1036 / GOV: ondemand

SMART REFLEX Y/N: Y

HOTPLUG: its automatic / CPUMODE: Dualcore / POWERMODE: Powersave

APPROXIMATE AMMOUNT OF DATA USED ON WIFI/3G: not looked

WIFI/BT/GPS/NFC ON ? : most time WIFI (when wifi than no mobile data), NO BT/GPS/NFC

OTHER SETTINGS:

SMART USAGE DESCRIPTION: Normal use much texting some tapatalk and surfing

NOTE: Amazing!
[Samsung Galaxy Nexus] TwinkyOfHope:
Same exact thing happened to me. Couldn't restore via CWM or flash to stock, ODIN hanged on NAND write start and then i got stuck at the yellow triangle screen. I ended up buying a new nexus and trying to get rid of the old one :(
[Samsung Galaxy Nexus] renna1992:
Wow
[Samsung Galaxy Nexus] skdinesh:
Best battery life & performance on R162

ROM: Liquid Smooth 1.4

Kernel: Franco r162, 384ghz gpu

Phone: Galaxy Nexus GSM

Battery: Standard 1750mah

Min CPU: 384

Max CPU: 1228

Max screen off: 729

Governor: Interactive

I've just updated to r165 and hopefully get as good battery file and don't come across the data drop issues mentioned. But one thing I've noticed on r165 is I get random occasional screen lags and stutters, especially when I first come out of sleep and start working on the phone. It never used to happen on r162 and older kernels.
[Samsung Galaxy Nexus] Booker-T:
Hi, Franco.

I love your works so much.

I would like to ask if there will be more frequency to be provided like 11XX?
[Samsung Galaxy Nexus] wayne850:
no i got this values but i got the 2000mah battery
[Samsung Galaxy Nexus] Basian Mile:
yep me too. I got 4 Day 3 Hours with 2.5H ScreenOn Time :-)
[Samsung Galaxy Nexus] skdinesh:
Thanks for sharing. What are your CPU settings? As you see my previous post, I managed just over 2 days with 2.5 hours screen time. That was on Liquid Smooth 1.4 with r162. My cpu setting were 384 - 1228 and on Interactive. Thanks again.
[Samsung Galaxy Nexus] Basian Mile:
192

1228

Interactive

Francos 157

SlimICS 3.6

No other changes.
[Samsung Galaxy Nexus] celyst:
I decided to try r165 to see if somehow my problem has been fixed. I also did the GENTLE_FAIR_SLEEPERS tweak that was recommended by franco. Looks good so far but it's only been 3 hours so gotta give it some time before I can confirm that the data drops aren't happening for me.
[Samsung Galaxy Nexus] wayne850:
i got cpu 384-1034mhz so a bitt underclocked. undervolted every frequency ~100mv
[Samsung Galaxy Nexus] skdinesh:
Thank you. I've never tried SlimICS ROM before. Does it have all the features Liquid and AOKP has? Btw what are your screen of max cpu settings? :)
[Samsung Galaxy Nexus] relax24:
Using any of the 160 builds, my idle drain seems so much higher. I've not changed any applications, plus all my wakelocks are the same as they always are. The phone is also in deep sleep for the majority of the time, but it still drops so much. Nothing has changed in my tests. Not sure why this is happening
[Samsung Galaxy Nexus] skdinesh:
Yeah me too. When I was on 156 or 157 I used to get under 2% drain for an entire 8 hours of sleep with sync on. Now since switching to 160s I'm getting an average of 5 to 6% each night of 8 hours sleep without any new apps or change of settings.

---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------

However, my screen on time is better with the 160s kernels :)
[Samsung Galaxy Nexus] Moz007:
Same hear !!! I change Interactive to Lazy to compensate... I thought it was me but now i know we experience the same thing !
[Samsung Galaxy Nexus] Lambetts:
Bump
[Samsung Galaxy Nexus] andQlimax:
no one have this problems, maybe its rom related..

u could give 165 a chance..then if still no joy, i would try a wipe data/factory reset in recovery (do a nandroid backup first just in case u want go back)
[Samsung Galaxy Nexus] SirOcelot:
Can you post your settings, please?
[Samsung Galaxy Nexus] Basian Mile:
SlimICS is just a Perfect Rom. I like it.

Got lots of Settings but no Useless ones!

ScreenOff Settings is not changed. So its default.
[Samsung Galaxy Nexus] viskas:
I saw somebody already asked this, but there was no answer. does this kernel works with modaco IR8?

thank you very much!!!
[Samsung Galaxy Nexus] :
Thanks, tried that. Same thing, opens to a black screen then closes?

Thanks thou.
[Samsung Galaxy Nexus] skdubg:
yes it works.

Paul includes android 4.0.3 kernel support at Ir8
[Samsung Galaxy Nexus] jonata:
possible to flash this kernel on 4.0.2 rom ?
[Samsung Galaxy Nexus] viskas:
I tried to install it, but I had a bootloop. I'll try again!

thank you!!!

done, it worked
[Samsung Galaxy Nexus] kjwalker:
Nope, have to be on 4.0.3.

Sorry
[Samsung Galaxy Nexus] Pliind:
Strange.. this was with his and your version #4, i flashed your kernel after flashing his rom, then a day later i noticed my root was gone, so then i tried your version #5 and i was still without root until i upgraded to bixie's #5 :/
[Samsung Galaxy Nexus] Thracks:
Between kernel 7.x and AOKP M1+, my GNex has never been this smooth. Thank you so damn much, Franco. You are doing amazing work.
[Samsung Galaxy Nexus] CdTDroiD:
Hey dude, do you have a kernel for the Nexus S to fix the Android OS issue as you have done here? Im no good with kernels lol
[Samsung Galaxy Nexus] schriss:
This: Bye CIFS - from my testing it was causing horrible battery life while idle

I do not agree, I always had CIFS and still have it and I am now getting great idle battery life, for example 2-3% over night when airplane is on. Yesterday I was playing a movie over CIFS mapped share, so I definitely have it and not complaining about battery life.
[Samsung Galaxy Nexus] manson28031991:
is the kernel for 4.0.2 stock too? because i have already bootloop
[Samsung Galaxy Nexus] MultiCulti:
OMG :eek:

i would delet you´re question ... or you risk a ban xD

NO, it´s 4.0.3 ONLY
[Samsung Galaxy Nexus] ock:
I thing this got lost in the changelog: