yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Hanny:
Thanks franco, but just wondering what have been changed.

I have no more data/signal drops since i change my baseband to XXLA2 and matches the RIL. XXLA2 is also the default baseband for nexus's sold here in hong kong, too.

Really sorry for the inconvenience caused for you :o as i guess why before SC04DOMKKD was working fine for me/my friend was because the ROM is relatively older plus something else so the old baseband was still compatible. However thanks a lot for your work on improving the stability and create the secure zone for signal strength :) please add me into the solved list :p

here confirm lazy governor is removed in r174. (not affecting me but just reporting) maybe franco is too hardworking :eek:
[Samsung Galaxy Nexus] CaspaTheGhost:
My setup has been constant for a while now... Official extended battery with Interactive, 729/1344 with SR on... Was running the 512 version of 173...

Just flashed r174/384 so will see how that fairs (r173 was a little temperamental on wifi compared to the previous build, but only a little as the battery life shows)...
[Samsung Galaxy Nexus] rogersnm:
Yep, I run lightflow with 192-1344 MHz (interactive) screen on and 192-384 MHz screen off. The notification LED works fine in deep sleep (minus a few glitches which I'm pretty sure are nothing to do with the kernel).
[Samsung Galaxy Nexus] 15israellai:
Wait, Hong Kong buddy, so the stock devices sold here are having XXLA2 by default?

I guess I'll take that then.

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] Antob125:
To all the people that were on lazy gov like me which gov is closest?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kevinngck1:
Mine is xxkk6 by default.
[Samsung Galaxy Nexus] The Gingerbread Man:
Conservitive

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] Hanny:
yup, actually the both of them - XXLA2 and XXKK6 are included in nexus's sold here

however, as the RIL of recent ROMs are XXLA2, it is recommended to match them for maximum theoretical signal strength. therefore, i chose LA2 :)
[Samsung Galaxy Nexus] franciscofranco:
I removed lazy by accident, I will re enable it later.
[Samsung Galaxy Nexus] zok-star:
173 is running pretty good for me! I have a small request. Are we able to get a "reset" feature within your app please? So we can reset all the settings we have set etc?
[Samsung Galaxy Nexus] DexyG:
Apologies for such a noobish question, but can you download the updater app and use that to flash the kernel from stock?

Or do you have to have flashed the kernel using fastboot first before you can use the app?
[Samsung Galaxy Nexus] Theshawty:
You can use the app anytime you wish, given you're rooted.
[Samsung Galaxy Nexus] 15israellai:
I tried LA2 for a while but signal seemed to drop; I'm not sure though.

I guess I'll have to try and test for a longer time then.

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] franciscofranco:
Is anyone having drops on r174 or since there haven't been any reports it means that it's now taken care of?
[Samsung Galaxy Nexus] H2O_c:
still have data drop issue when loss the connection of wifi in 174

but the data will enable after few minutes
[Samsung Galaxy Nexus] marshy73:
I had one data drop on 174
[Samsung Galaxy Nexus] iGoogleNexus:
^ never had a data drop with this kernel

- Google
[Samsung Galaxy Nexus] Hanny:
what baseband did you come from? and is yours an SC04D? and how do you mean "drop" - signal is completely gone, or just weaker?

if so, XXLA2 feels relatively weaker signal (just down one bar to 3 bars from 4 bars) than the japanese baseband, but i am sure the stability is much better. together by using newer baseband (DOMKKD one can be regarded as old) and matching the RIL. ive tested the speed with speedtest.net app and it does not become slower. so i am living with it.

@franco, still not hving issues here. please reveal the secret when you have collected enough results:p
[Samsung Galaxy Nexus] Theshawty:
I have had five complete drops as well. And after each drop, my connection skyrocketed to full connection, only to drop down to two to three bars which is normal for my reception in this area.
[Samsung Galaxy Nexus] franciscofranco:
Ok guess there are still few people with drops.

Blind test for users with drops: http://minooch.com/franciscofranco/Galaxy Nexus/franco.Kernel-test.zip

Report back please.
[Samsung Galaxy Nexus] wingsiw:
I was all day on r173 = no data drop. Flashed to r174 @ the end of the day = data drop this morning :(
[Samsung Galaxy Nexus] RayGarden:
UGKL1 on Gnex GSM Europe

i have watched this video and made me curious, so i pushed radio-maguro-i9250ugkl1.img

My Signal / Data Drops are history :D

http://www.youtube.com/watch?v=JY2SNeQ5uUQ
[Samsung Galaxy Nexus] Theshawty:
I'll try it and see. Random question: When do you recommend doing a data wipe?
[Samsung Galaxy Nexus] castaway1:
no data drop for me on #174 and new baseband that found me RIL app.Ill not try new until i get some data drop. There is rule i will fallow - dont fix smth that works good :)
[Samsung Galaxy Nexus] franciscofranco:
When changing roms...
[Samsung Galaxy Nexus] Theshawty:
That's kinda obvious :p

I wasn't clear enough, I mean to ask you if you recommend doing a data wipe after a while when switching nightlies? Shouldn't be necessary, right? Only when changing ROMs/android versions I suppose?
[Samsung Galaxy Nexus] BigBake88:
I do not think conservative. I would say OnDemand, since it is tweaked governor based on OnDemand. ;)

---------- Post added at 09:28 AM ---------- Previous post was at 09:26 AM ----------

Go to settings>apps>click on franco app, and clear data???
[Samsung Galaxy Nexus] emerica243:
So my current settings are as follows.

Max 1036mhz

Min 192mhz

Lazy Gov

Apply cpu settings on boot

Powermode Power Save

min freq screen off 192mhz.

My battery drains about 1-2% for every like 3-5 minutes im actively using my phone. If im at 90%, i turn on my phone, browse the web/facebook/listen to a song. Then look ive already lost 1-2% within 3-5 minutes. It used to never drain that fast. Overnight it drains about 1-2% an hour when sleeping. My deep sleep is always super high and the other frequencys always add up to my usage.

It didtn always use to be this bad. It only happened after i flashed one of the newer nightlies in the 160 area. I thought it was maybe a bad build. But since then ive reverted back, wiped my rom and started fresh with aokp m5/franco m3. Latest franco builds, Now im on Liquid 1.4 and its still really bad, like half the efficiency my phone used to be. Could itjust be a quincidence the battery just took a crap on me? BEcause mbetterbatterystats adds up, theres no wakelocks, etc etc. Anything else i can do even though i already ordered a new batt to try to troubleshoot this
[Samsung Galaxy Nexus] franciscofranco:
Thats what I said, when changing roms. I dont switch roms for while already so barely do that and I flash a lot of kernels and never have issues...maybe thats why I cant reproduce bugs... Stable envirorment = all ok.
[Samsung Galaxy Nexus] Flukester69:
I got 2 drops yesterday but they lasted about 30 seconds max and each time it was when wifi was negotiating.
[Samsung Galaxy Nexus] BigBake88:
Yea my overnight battery drain has not been impressive to say the least, but overall I am getting good battery life. My overnight drain from last night was 9% (8hrs). LS 1.4.
[Samsung Galaxy Nexus] Zflash:
Haven't had datadrops, but a couple of WiFi drops. Not sure where they came from. I flashed back to 173 to check it and it wasn't on that kernel. Flashed back to 174 and enabled the wifiboost in your app. After this (about 4 hours now) no drops whatsoever.
[Samsung Galaxy Nexus] Diger36:
I didn't have a data/signal drop since I moved to Rascream and since r169... On AOKP with r169 however I did have signal drops. (Haven''t tested the last builds with AOKP)
[Samsung Galaxy Nexus] BigBake88:
Anyone having trouble with Fast USB charge? It seems to not work for me. I enable it before plugging the phone in, and when I plug it in it will do either one of two things. It will either state AC charging for a minute or two and then state "not charging", or it will just say "not charging" at all from the get go. I have checked liquid settings, and there is nothing that would not allow fast USB charge to work. I am currently on 169. Any ideas? Franco, have you heard any reports of this? :confused:
[Samsung Galaxy Nexus] supernova_00:
Nope, never had an issue with it.
[Samsung Galaxy Nexus] franciscofranco:
Quoting for re-posting.
[Samsung Galaxy Nexus] BigBake88:
Seems to be working now, but I did have to do some fiddling with it...
[Samsung Galaxy Nexus] marshy73:
A friend's encounter with 174. Data drop occurred and stayed off with no auto recovery. He turned off smartreflex and immediately data came back online.

Hope this occurrence helps in your investigation.
[Samsung Galaxy Nexus] marshy73:
Franc... Do you want this test with or without smartreflex on?
[Samsung Galaxy Nexus] flolep:
Well. I am sorry. I am not posting too much but I read all the posts on this thread.

The reason why I am am not posting is because I never had too many problems with this kernel so far or the little problems I saw were already described on the thread and corrected by you, Francisco, the next day the problem was found.

But here I just wanted to say that I had no big problems with data drops so far, maybe little ones when people began to talk about it some builds ago but not very frequently and not very problematic as most of the time I am surfing on Internet with wifi...

But for version 174, I want to report that the data drops are even worse now... I am sorry to report that as some people said the problem has gone for us with this build but really, for me, when it was a big problem for them it was not a big deal for me... And now it is worse: 5 drops since the beginning of the day...

I will try with your blind test kernel and report in 7 hours max.

FYI I am on Gsm, aokp b37, oc 729->1340, smartreflex disabled, some stable undervoltage for MPU, IVA and CORE, ondemand, sio, radio uglc1 and ril xxla2, wifi was off

I know you will find the definitive problem Francisco but I really wanted to report that, FOR MY PHONE, 174 is worse than 173.

Thank you so much for your work so far on this wonderful kernel.
[Samsung Galaxy Nexus] Theshawty:
What does smartreflex actually do? Is it just managing the over/undervolt?
[Samsung Galaxy Nexus] The Gingerbread Man:
Not had a data drop since I reported one the other day and that happened when moving out of range from wifi with wifi still activated. I keep up with all the latest nightlies. I won't be using wifi today (don't have it at home) so can't tell if its solved me. So all good so far I guess, paradroidandroid 0.9b, xxla2, ril match now using conservative in place of lazy and power save mode on

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] andQlimax:
i guess the mainly problem reported is the data loss when on 3g mode (also without wifi interaction)..isn't it? :confused:

here the first problem is to understand what problem the people have lol
[Samsung Galaxy Nexus] drawde40599:
The dev of light flow Nos there's issues with his app, and still hasn't fixed it, those glitches are not the kernel
[Samsung Galaxy Nexus] joeyfong:
Trying set min 384, so far no signal drop
[Samsung Galaxy Nexus] Dr Byte:
Data drops & Juice Defender

Just ran into a page on code.google.com discussing network dropouts, and one particular poster had success by changing Juice Defender options to stop it resetting the radio.

I don't get the issue, but perhaps someone who does and uses JD might like to try it. Of course, if people are getting the problem without installing JuiceDefender, it could be a similar issue in another app.

http://code.google.com/p/android/issues/detail?id=22503#c91

FYI
[Samsung Galaxy Nexus] Jiia:
I flashed 174 too and got data drop a few hours after. Returning back to stock kernel.
[Samsung Galaxy Nexus] vomer:
No data drops for 12 hrs so far on 174. Maybe it was lazy governor

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
I did wonder if that's why it was 'accidently' removed ;)

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] emerica243:
Anyone?
[Samsung Galaxy Nexus] kacongx:
Hi Franc..

Is your kernel already supported for hdmi?
[Samsung Galaxy Nexus] georgito:
Having battery drain as well.. Trying flash milestone 3 and will see...
[Samsung Galaxy Nexus] The Gingerbread Man:
Maybe try a good long offline charge and use cwm to wipe battery stats, charge some more till 100% shown again and uninstall Facebook and loads of people say its a battery hog, friend caster is better supposedly

Sent with a shake
[Samsung Galaxy Nexus] BigBake88:
Maybe go with a fresh install? IDK, but if with screen on you are getting 1% drain every 3-5 mins, you should be near the 4hr screen on range, so not sure what the issue is.
[Samsung Galaxy Nexus] franciscofranco:
Ahaha it was really an accident, I already enabled it on my test build.
[Samsung Galaxy Nexus] jnr21:
Nice battery life with 174. Almost 3h of screen on time and 60% left.
[Samsung Galaxy Nexus] The Gingerbread Man:
Fair enough, due to your mistake though I might be up for a personal best with screen on time using conservitive. 51% battery and 1 hour 56 screen on time so thanks :D

Edit;

Wish I had wifi at home to join in these ridiculous screen on time, still not doing bad for using 2g/3g/H

Sent with a shake
[Samsung Galaxy Nexus] apsis:
@jnr 21

Really nice battery stats, might wanna share some information about your screen brightness, color settings and gamma setting in Franco's app, governor, other settings within the app and your rom?
[Samsung Galaxy Nexus] relax24:
Settings/undervolts etc?
[Samsung Galaxy Nexus] leets4uc3:
For the people on aokp or similar roms with the startup init.d tweak, what tweaks do you have turned on? Also do you guys have gpu acceleration on?

Edit. Idk if I posted this earlier. Just popped up as a draft
[Samsung Galaxy Nexus] jnr21:
729-1344mhz, interactive, sr on, 512mhz gpu, omap gamma 1.0, color 150,160,210, 50% brightness, wifi on, liquidsmooth 1.4.
[Samsung Galaxy Nexus] vomer:
I jinxed myself. Data drop just happened :(
[Samsung Galaxy Nexus] 15israellai:
Currently xxkk6. When I used LA2 the signal generally was weaker and often disconnected and reconnected. Do we call this a drop? :P

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] rene_r:
Same here(Austria - Hutchinson 3G) with XXLA2 and the matching RIL I got a lot of signal drops, with XXKK6 and the matching RIL, I haven't got any drop(using your r174 kernel).

br

rene_r
[Samsung Galaxy Nexus] willl03:
174 was real nice for performance and battery, but I got yet another signal drop after a few hours of usage.. I'm out of here till 100% fix
[Samsung Galaxy Nexus] duowing:
For people experiencing data drops have you been able to go days on other kernels without a data or full signal drop off? Also like for me I get data/signal drops daily, but a lot of it is simply from areas at work having poor to zero signal.
[Samsung Galaxy Nexus] a1exus:
how does one install this kernel on their phone? and what's the procedure to roll back (just in case)?
[Samsung Galaxy Nexus] flolep:
Yep. On previous kernels from Francisco, nearly same conditions as I described earlier...
[Samsung Galaxy Nexus] BigBake88:
Download kernel to sd card, and flash via CWM, and make a Nandroid before you flash it...
[Samsung Galaxy Nexus] dyndragon:
was the problem with CM9 su binary and franco.kernel app not being able to set options on boot ever rooted out and fixed? I have updated the su binary from the superuser app and my settings still don't stick on boot. I tried searching this thread for more info but could only find that suggestion.

any help is appreciated, thanks.
[Samsung Galaxy Nexus] franciscofranco:
Don't use CM9, problem solved. I don't support any kind of CM9 roms, so you're on your own.
[Samsung Galaxy Nexus] thepawn:
My data drop use-case is repeatable:

Be on WiFi and then just go "out of range" of it...the fallback to mobile data never happens. I have to airplane mode on/off to get it to connect. You can simulate it by just joining your wifi then turning off your wifi router.

In my instance, I'm on WiFi at home, then I get in the car and drive somewhere...soon as I'm out of range of my home WiFi, bam, no mobile network data switch.

I started noticing it after r163... I can start testing older kernels to see when exactly it began if that's helpful Franco.
[Samsung Galaxy Nexus] ragnarokx:
That's too bad. Not a fan huh?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I released a test build yesterday night some pages ago.
[Samsung Galaxy Nexus] andQlimax:
don't u think that the cm9 settings can override/confict with the settings on franco app??

its so difficult to understand.. :)

solution: set the options that doesn't stick with cm9 settings..should work
[Samsung Galaxy Nexus] drawde40599:
I sent u pm u can read y, no cm fan
[Samsung Galaxy Nexus] ragnarokx:
That's what I've had to do.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Theshawty:
Franco: Why is it that you dislike AOKP and CM9 while promoting a ROM like LiquidSmooth?
[Samsung Galaxy Nexus] spinkick:
He is part of team liquid for one thing. So he has personal input.
[Samsung Galaxy Nexus] Theshawty:
Ah, ok. Well, it's always nice with subjective opinions. :rolleyes:

Looks like I need to go elsewhere for more objective answers instead. Still, great kernel which I will continue to use.
[Samsung Galaxy Nexus] justme1988:
The Franco app used to work for me... but after the latest update, it won't keep the settings for CPU speed and govenor

Send from my Galaxy Nexus using Tapatalk
[Samsung Galaxy Nexus] Stretlow:
It isn't just down to that, Franco helps and supports most developers on here, there's a big post about the problems the CM9 methods cause.

Its an unfortunate shame because I find it to be the most stable, im trying my hardest to find an equal rom but I cant. Liquid smooth is good, but there's niggley bugs all over, only little things but its enough to put me off.. Things like keyboard popping up in browser when it shouldn't. Someone will come along soon an tell me they dont have it but ive completely wiped my phone and reflashed on numerous occasions and the bugs are there...

Simple fact is since i've had my nexus (day one) francos kernals give me the best performance and battery to the point where ill choose the rom to suit the kernel..
[Samsung Galaxy Nexus] spinkick:
What do you want him to do, test every rom himself? I run liquid and have tested them. I am unaffiliated.
[Samsung Galaxy Nexus] rye&ginger:
I have only used AOKP, but M6 and Faux 17m were very stable for me. But I had a drop after many days amd then flashed the most recent AOKP build. Its been a lot of data drops since.

I will full wipe and try to go back to M6 most likely, or try Liquid.

No offense Franco and to anyone, but I think this question is good. Also I see Liquid seems to be based on CM9 and AOKP? Just reading their documentation makes it seem that way. All devs clearly put in good efforts and its appreciated.
[Samsung Galaxy Nexus] kid1da:
Franco just some feedback on your latest test build for the data drops. My problem was losing service from going wifi to 3g/h. The latest test build solved that issue. I haven't had any data drops solely on 3g/h.
[Samsung Galaxy Nexus] Theshawty:
Not really, but what's the need for almost bashing other ROMs?

Today he told us not to use CM9 and the other day he told CerB to install a stable ROM since AOKP's nothing but unstable (source: here)

I get that some people don't like certain ROMs for certain reasons, but there's no need to be rude about it.
[Samsung Galaxy Nexus] renna1992:
changing my baseband and ril back to xxkk6 and the matching (android 4.0.3 ril) solved my signal drop issue. running great here with 174.

thank you very much franco :)
[Samsung Galaxy Nexus] Hanny:
yup then that should be a signal drop. well it must be phone/rom/android version(i dunno which ure using) specific - then you should stick with xxkk6 no matter it matches the RIL or not because as someone have said some time ago - dont fix things which are working :D
[Samsung Galaxy Nexus] franciscofranco:
I'm not on Team Liquid, I'm not affiliated with anyone or any team or organization or whatever. I work solo now, and forever. I helped Team Liquid in the past and will help them again if I feel doing so.

If I don't like X rom I'll say it, if I don't like Y rom I'll say it. If I like rascream I'll say it, if I like LiquidRom or Bamfs I'll say it. It doesn't mean X, Y or any of the other roms are bad or worse, it's just my personal preference, I don't receive money to sponsor any rom.

Also I didn't told "you" to not use CM9, I said I wasn't supporting it anymore - different things.

Why people tend to put things on my mouth that I didn't say =(
[Samsung Galaxy Nexus] grognaz:
i noticed that when i turn my device on after some time it has to connect to data, i ls this a kernel feature that data gets disabled when the screen is off?

im using aokp and all power save options are disabled.
[Samsung Galaxy Nexus] Flukester69:
Hey I got that problem too, my wife says I say a lot of things I didn't. :p
[Samsung Galaxy Nexus] kompressorgpl:
Francisco: I asked you, at least, 2 times. What ROM are you use? I dont see any problem on that!
[Samsung Galaxy Nexus] BigBake88:
So, Franco. When do you think M4 is gonna drop? :D Tired of all these data drop posts! Let's get some positive energy going in here!!!
[Samsung Galaxy Nexus] vomer:
How can you have a milestone which has problems? I thought 174 fixed things but still got drops.

Running M3 now and no drops. So definitely something going on. Maybe we should roll back to the nightly with no drop issues after M3? When did it start?
[Samsung Galaxy Nexus] thepawn:
Ah I see it, r173 was still broken for me, but r174 is looking good so far. Just did a wifi drop test and it connected to mobile data, will watch it some more over the rest of the day.
[Samsung Galaxy Nexus] odin13:
I think it's a real pitty that great dev's like you and Ez won't support CM9 anymore although i understand your reasons

Keep up the good work and as for datadrops...no problems here so far on any of your kernels (nor on glados btw.)

I only had drops when i flashed Bugless Beast nightly from 6th of april

Since i'm running the nightly from the 9th i never had a single datadrop

Radio = xxla2 with matching bootloader

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Benji1983:
he uses the rom of his choise