yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] P3aK:
Ok finally signed up here and managed to get the required posts so I can give some feedback. Been lurking around for too long :)

165 - data drops

166 - data drops

172 - data drops

174 - data drops

Blind test - data drops

(Cant remember when it started anymore, but was after 162)

Slim ICS 3.8

XXLA2

Matching RIL

Always clear cache AND Dalvik Cache on each kernel flash

Always clear franco updater app cache and data after kernel flash.

512Mhz kernel version on all (except this blind test one which is 384).

Settings in Updater app is:

Max cpu: 1036

Min cpu: 192

Power Mode: Power Save

Set power mode at boot: Check

Maximum frequency for screen off: 192

SQLite: Check

Enable USB fast charge: Check

Rest... untouched

Phone and SMS works all the time, I lose data completely, never comes back on its own (with in 4h at least). I can NOT go to Flight

Mode or turn Mobile Data off and get connection back. I always have to reboot.

Data connection is lost within 3h after a reboot (174 so far took maximum 20min though).

I almost never use WiFi so this has nothing to do with me losing the signal. I personally cant find any common marker when I lose it.

On 174 I lost it while surfing with screen on and maximum ( 4 bars ) reception. Blind test when idling or sleeping. Others when I lose signal (tunnel/subway) others when I have good or bad reception.

My subjective feeling is that the data drops have escalated and happen more frequently and faster for each new version that has come out since I first noticed it. Could be that Im sitting here waiting for it now that I expect it though.

Hope that helps a little as feedback.

Thanks for you time and dedication Franco!
[Samsung Galaxy Nexus] nodstuff:
Time for some positive messages here I think.

Liquid smooth 1.4

Franco 174

XXLA2 radio

NO data drops. Never. On any release.

My only advice to people with data drops is you're holding it wrong :P

No, wait..... maybe I'M holding it wrong! :O
[Samsung Galaxy Nexus] Sveke:
Everyone in here should try eclipse roms by nitroglycerine.

Eclipserom.com

Never see anyone talking about it and there is a gsm version.

It's fantastic!
[Samsung Galaxy Nexus] laureanop:
It is ethical for a kernel dev not to really talk about what rom he uses (unless it's his own rom ). Kernel devs don't really want to skew you into choosing one rom or the other one. It could potentially create animosities between rom and kernel devs.

In the case of Franco and cm9 it's a different issue altogether and he never asked anybody not to use it. To be perfectly fair , cm9 is the only dev corp that creates consistency and uniformity in the fragmented android world ( not a cm9 user at the moment )

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Moz007:
Try to not use 192mhz slot.
[Samsung Galaxy Nexus] schizophrenia:
finally someone has the same symptom as mine

cannot go to flight mode or turn mobile data off

it happened only once in r174 a bit right after i flashed it and now within the last 11 hours it never happened again.

this data dropped happened since r165 (if i remember correctly which was released on last Friday) and I never had any problem with data drop before with the same set up min192 max 1344 (only data, not signal)
[Samsung Galaxy Nexus] kompressorgpl:
And is choice is...
[Samsung Galaxy Nexus] franciscofranco:
Im always answering that. Using rascream.
[Samsung Galaxy Nexus] :
I would use Liquid too if it would

have more languages !

Right now its just really frustrating to always set the colormultiplers again.

AOKPM5 runs fine for me...CM9 want to make there own business thats why I understand Franco ! Ezkeel wrote about that...

Im happy with AOKP M5 and Franco M3 but b37 was/is crap

tapatalked by AOKP powerd by TRINITY
[Samsung Galaxy Nexus] kompressorgpl:
OBRIGADO!!!! No so difficult after all!!!
[Samsung Galaxy Nexus] BigBake88:
He has stated it multiple times...use search function.
[Samsung Galaxy Nexus] kompressorgpl:
It was the first thing that I did! But my Internet has been crazy! Sorry...
[Samsung Galaxy Nexus] Bonvaz:
What'a your problem man?...He answered this question 10000 Times here....
[Samsung Galaxy Nexus] Prod1702:
I would have no clue what is causing the data drops for ppl, but I have updated the kernel whenever there is a update. I got my GN about 3 weeks ago and have never had any data drops at all. I am using Fits CM9 Kang which is updated nightly, I am using Radio: UGLA4 on T-Mobile USA. I do not use the 192mhz my lowest set with the kernel app is 384mhz. I am also UVed as well, my voltage is as follows

384- 950

729- 1100

1036- 1225

1228- 1250

I do not use the 1344 setting so I did not touch that. Over all Great Kernel. After 3 full charges i am getting around 3 to 3.5 hours of screen time on the stock battery. Great Kernel Running on CM9.

Edit: Not sure if it matters or not but I also have Smartreflex disabled in the app.
[Samsung Galaxy Nexus] mert2go:
Funny! Never had Data-Drops but with your newest kernel (174) i have them...
[Samsung Galaxy Nexus] P3aK:
Hmm ok, I could do that.

But then the question is.. what Power mode do I use? Power Save automatically sets minimum cpu to 192 if Im not mistaken. And an even bigger question is why has it worked before? Since the 192 slot was lastly re-introduced (around 130-140ish) without problems?
[Samsung Galaxy Nexus] drawde40599:
If u go to liquids rootwiki page in yesterdays posts he tells u how add languages;)

I've used every single rom available for this phone and I always go back to liquid, liquid and franco have been the perfect combo for me for months now
[Samsung Galaxy Nexus] thepawn:
r174 - So far I have not had a data drop yet, but I need to do some waiting.

I've done -

screen on, kill wifi - mobile data connect no problem.

screen off, kill wifi - mobile data connect no problem.

now I'm going to wait a bit for it to enter some sleep modes and then kill the wifi and wake it and see what happens.
[Samsung Galaxy Nexus] BigBake88:
Agreed, Liquid and Franco IMO cannot be beat. Performance and battery are top notch
[Samsung Galaxy Nexus] :
Could you give me a link ? I looked but didnt found it

tapatalked by AOKP powerd by TRINITY
[Samsung Galaxy Nexus] theneighbor:
Long time Franco user and supporter here. Finally decided to try cm plus as I've heard good things. I'm trying to adjust color multipliers using Franco's app but the app keeps force closing. I assume its a conflict with cm plus but wanted to get community thoughts
[Samsung Galaxy Nexus] franciscofranco:
Its because cmplus uses cm9 kanged ezekeel color control and its not compatible with my app and never will. /angry
[Samsung Galaxy Nexus] vomer:
Franco any game plan on how to fix drop issue?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] flolep:
Well. I tried the blind test kernel. I had one data loss in the first hour (obliged to do the trick of airplane mode on / off) then no more loss for the six hours after so I don't really know if it will help :-(
[Samsung Galaxy Nexus] theneighbor:
Thank you sir. Always nice to hear from the man himself
[Samsung Galaxy Nexus] :
After 30seconds my screen goes off and in this short moment my screen gets green, but only which is white...like inverted..

I only git this with Franco and ezkeels Kernel ! With Trinity and Lean everything is fine !

tapatalked by AOKP powerd by TRINITY
[Samsung Galaxy Nexus] ajm786:
Ok guys. Back from an entire day of testing, with 2 variables in the mix that has been changed.

I already had the UGLC1 radio; the 2 new things I tested are the UGLC1 RIL that was released from one of the guys in the baseband thread, and the r174 kernel.

I can confirm (at least on my phone) that the data drops have been fixed. Firstly, when I woke up in the morning and checked the battery history bar for signal, it was almost entirely green; it was never like that before. In addition, I was able to get excellent signal and browse the web in places I was never able to previously (namely, specific train stations underground). In addition, the signal never dropped ONCE.

Disregard the red towards the end in the second screenshot; that's when I was testing the signal underground, when I would go through tunnels (that's obviously when the signal would be lost). Otherwise, the pictures speak for themselves.

Obviously, the only side effect of this is battery loss. I guess it's really not that bad, since I'm getting about 3 hours of screen time, and I still have 16% battery left.
[Samsung Galaxy Nexus] sotoskawasaki:
You are located in Europe or US? Just asking to see if using the uglc1 baseband in Europe would work. And could you please elaborate on the RIL thing?

Glad you fixed your data drops.

Regards

EDIT: I don't see how this could cause more battery loss. On the contrary, having stronger signal would cause less battery loss.
[Samsung Galaxy Nexus] theneighbor:
How prevalent are the data drops? The GN is known for this even on stock kernel. I don't think I noticed any but am hesitant to come back if its an approved bug.
[Samsung Galaxy Nexus] sruel3216:
axi0m patient zero and franco cant be beat lol
[Samsung Galaxy Nexus] :
but not for gsm right ?

tapatalked by AOKP powerd by TRINITY
[Samsung Galaxy Nexus] Flukester69:
Ever try BlackIce and Franco? If not give it a whirl.
[Samsung Galaxy Nexus] ajm786:
I am located in the US. Here is the RIL thread. Read towards the end of the thread, where they start discussing the UGLC1 RIL (not baseband, but RIL).

http://xdaforums.com/showthread.php?p=26694685#post26694685

Remember, just because the phone is picking up signal better doesn't mean that the signal is "stronger". It could be directly related to some of the voltages that franco changed in his last two nightly releases that fixed this up. How I know this is that even with the matched UGLC1 baseband and RIL, I still got a data drop when I was on franco's kernel r166. Once I moved to r174, that pretty much solved it.
[Samsung Galaxy Nexus] eddie_gordo:
Since I've updated to 174 I can't get connection to Google Servers on 3G.. I can browse the web and practically everything but the icons don't get blue and I don't get Gmail nor Talk.. Airplane off/on don't solve, neither reboot.. Tomorrow I'll try to flash 162 back again to check if it is really Kernel related or not..!

If there is something that I can do, like getting some logs or something, that might help please let me know.. :)

Thanks
[Samsung Galaxy Nexus] metalspring:
Unless cm9 gets their s*** together and stops being so high and mighty and actually tries to work with the kernel devs, right?

kinda off topic but I think it's horrible that they don't try to resolve this considering 3 of the 4 "major" kernel devs for the gnex (imo, Ezekeel, and you but not faux) use the original color control and refuse to use cm9s version

("major" kernel devs determined by how popular they are and that most other kernels use them as bases or at least use their source)
[Samsung Galaxy Nexus] mtmjr90:
I don't know how productive this is...but I'll just throw it in there. I flashed r174 this morning and started getting data drops again after being fine for the past two or three releases. I'm back on r173 and sittin' pretty though:)
[Samsung Galaxy Nexus] franciscofranco:
Game plan is none. I've mostly wasted all my resources trying to locate a possible fix. There are two important variables here:

1st - my user base is HUGE so it seems that a lot of users are having data loss problems. Trinity users also have the so called data loss (its only Google services loss, not really data or connection loss), even morfic had one some hours ago without changing anything major in the kernel. So I'm pretty sure this is not just kernel related

2nd - I havent got any major reports of derp on the test build so I'm fairly positive I got it covered again.

I'm expecting r175 in the next hour, so stay tuned folks.
[Samsung Galaxy Nexus] sotoskawasaki:
Ok thanks for the info, I'll give it a look.
[Samsung Galaxy Nexus] georgito:
signal drop

correct me if Im wrong,but how can signal drop can be related to kernel??isnt it more related to radios ?..poor franco,his doing great job and signal issues is not his fault or kernels problem..
[Samsung Galaxy Nexus] Lambetts:
Hey.

Well different people do things differently of course but most users, I think just grab the zip of your choice, then I would grab Fauxs Reset 4.0.4 kernel from his OP. As mentioned also, a nandroid (backup in Clockwork Recovery) wouldn't be bad idea either as you can advance restore just the boot image (kernel) if you like. Which will bring you back to the kernel setup your running currently. The reset kernel zip will take the rom back to its compiled kernel.

Hope this helps. :-)
[Samsung Galaxy Nexus] franciscofranco:
99% of that is true. I'm gonna issue a r175 and be done with this series. Performance is great, battery is ****ing awesome, most of the bugs, if not all, are fixed. It's time for a Milestone 4 for sure.
[Samsung Galaxy Nexus] sotoskawasaki:
While I am not a kernel expert, it would seem that kernel is not related to the signal yes. But from my understanding it could be possible that some changes in the kernel to cause problems to the signal indirectly. To support my theory, I will say that the r17x series seem to minimize the signal drop problem. So the kernel does affect signal, even indirectly and at the minimum level. Having said that, I believe that Franco really made a beast here and certainly no one should point fingers at him for this problem!
[Samsung Galaxy Nexus] ajm786:
This I agree with. Franco has really done an outstanding job on the kernel; it's the reason why I dropped some coin for his app. You can tell quality as soon as you open and use an app. I don't doubt for a second that my Nexus is as great as it is if it weren't for his kernel and app that I installed on day one owning the phone.
[Samsung Galaxy Nexus] franciscofranco:
r175

* More changes to attempt to minimize the sudden data drops issues

* For more information visit my repository, it's too technical to write here
[Samsung Galaxy Nexus] thepawn:
Heh, love the armchair coaches making statements about coding that are wrong.

Mine was not a signal issue at all. After 163, something was wrong where when going from wifi to mobile data it was no longer switching. Signal strength was fine, it just didn't rejoin the data network . For me it looks like whatever he did in 174 worked. I imagine it had something to do with his awesome squeezing every ounce of battery out. :) It's rather easy for something to flake out when we're experimenting on how little voltage something needs or what you process you can force to sleep only to find it may have been needed elsewhere. A lot of trial and error and educated guessing.

Francisco, thanks for all the labor of love that we can enjoy!
[Samsung Galaxy Nexus] thepawn:
I'm impressed with the no compile error achievement... That shows an awesome attention to detail that many get lazy on. Kudos!
[Samsung Galaxy Nexus] vomer:
Thanks Franco :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] iGoogleNexus:
O_o hey i just woke up and saw r175 right ..I just did an auto flash and the weirdest thing just happened... when it reboots... my boot animation said Trinity xD

Wtf? Am I being Mind F**ked ? Or is this normal? xD

- Google
[Samsung Galaxy Nexus] nikulogical:
R175 is a collaboration between Franco and morphic.
[Samsung Galaxy Nexus] morfic:
As of today, Franco is replaced by Trinity, enjoy.

Franco needs time for HOX.
[Samsung Galaxy Nexus] iGoogleNexus:
O.o ohhhh ... thanks =]

- Google
[Samsung Galaxy Nexus] iGoogleNexus:
=[ not that your not good... but I feel like I lost my Besty when u said its been replaced by Trinity

- Google
[Samsung Galaxy Nexus] morfic:
I illustrated the hung wifi outside my company's metal building to show how easily the illusion of a data problem can be created.

What users reported was due to a core voltage drop below 880mV, which basedon initial feedback seemed worth testing, upon broader testing user reports suggest 880mV is still my bottom i can not punch through, which on your kernel is at least another 60-80mV higher anyway.

So the issues are not related.
[Samsung Galaxy Nexus] bongostl:
Franco--I just want to make sure that you are aware that people are reporting data drops on Faux, as well (see AOKP thread on rootzwiki for more info). At least a few reports are saying that this is not happening (or is better) on Glaados.

I have never had a data drop, and am very happy with your kernel!
[Samsung Galaxy Nexus] MFD00M:
awesome thanks for confirming. Now to find a micro usb adapter
[Samsung Galaxy Nexus] GchildT:
It's disables software 3d rendering. You will notice the difference in Quadrant and other apps written the same way.
[Samsung Galaxy Nexus] Redflea:
I rebooted after making this change and no issues.
[Samsung Galaxy Nexus] razzbaronz:
I did this as well, my system automatically replaced the file with the original and that file was renamed to egl.cfg.bak (my edited one). Check whether yours did this as well. I'm on AOKP milestone 1.
[Samsung Galaxy Nexus] loudaccord:
Do you get more than 8fps on the planet/moon test during the Quadrant bench? lol
[Samsung Galaxy Nexus] Redflea:
Mine was not reverted...still my edited version. I'm on Winner00'a CM9 ROM...da best kine ROM, love it. :)
[Samsung Galaxy Nexus] kabauterman:
Never had a better battery life then with nightly 7.1 !!
[Samsung Galaxy Nexus] Guitarfreak26:
Mines still bad battery, im wondering if it's the 2G toggle in aokp that makes it use more?
[Samsung Galaxy Nexus] Redflea:
Same! So glad I found this Kernel.
[Samsung Galaxy Nexus] luffyp:
So we have some mixed results regarding the battery life...
[Samsung Galaxy Nexus] fiftyclick:
It seems on par or only slightly worse than my battery life, however I know mine suffers because of Exchange sync, Gmail, RSS, GTalk, Facebook, XDA notifications, and much more. How many accounts do you have configured? I am curious to see why Android OS is talking up 48%.

--- edit ---

I am running AOKP v11 on a GSM phone that can only use HSPA (no 2G toggle, won't work on Bell)
[Samsung Galaxy Nexus] akellar:
I'm at 9 hours off charger, on wifi, about 3 hours screen on and battery is at 47%. Good in my eyes.
[Samsung Galaxy Nexus] davey11:
Just d'led...seems like the most developed kernel.

Got here from Redflea's recommendation over at rootz. He is a one man ad agency! lol

Will check it out...I be on rootzboat.

More vzw owners need to know about this kernel.
[Samsung Galaxy Nexus] Guitarfreak26:
1 gmail account, i do have fb app installed though and tweakdeck on half hour refresh?
[Samsung Galaxy Nexus] fiftyclick:
whoa, that is hardly anything. Try doing a wipe and clean install to see if there is a difference. I have way more background services going on with AOKP #11 and kernel 7.1 with roughly the same or better battery life, and no 2G battery saver. If you are on an LTE phone, I know AOKP has issues. This is a solid kernel for battery life now.
[Samsung Galaxy Nexus] Guitarfreak26:
Nope im a european gsm.. I may backup in titanium and wipe in a bit... complete reinstall.. i do usually wipe though..
[Samsung Galaxy Nexus] King Shady:
Will this kernel run smooth on Axiom 2.1? It's a 4.0.3 LTE Rom. Thanks guys.
[Samsung Galaxy Nexus] triStateMindgate:
Yes this Kernel works with both GSM and LTE devices running 4.0.3
[Samsung Galaxy Nexus] Syn Ack:
This kernel + wipe battery stats fixed my battery issues
[Samsung Galaxy Nexus] sirj00:
Is all good. Been using 2.1 with 7.1 for 2 days and it's wonderful.

Best battery life and very smooth.
[Samsung Galaxy Nexus] simms22:
now that is classic ;)

---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------

im sure that hes aware that its a general galaxy nexus thing. seems that some get them and some dont. its just that he has more users, and more users mean more reports of it happening.
[Samsung Galaxy Nexus] nklenchik:
You guys should keep the hybrid kernel thing going. I like the idea of a kernel being developed by more than one dev, not just roms :P
[Samsung Galaxy Nexus] bongostl:
Is this a joke?
[Samsung Galaxy Nexus] neos_83:
I can confirm this in my experience. I get data drop issue (after leaving a wifi area) on faux 17m. I don't think it happened all the time but enough to notice and be annoying. If you check the phone status in settings during this time, "mobile network state" will say either disconnected or connecting (cant remember which one off the top of my head). Also switching on airplane mode when this happens, I would have to wait maybe 30-60sec before the signal bar changes to the airplane. Then i can switch off airplane mode and data reconnects.

On Glados 1.33 and 1.34 haven't yet experienced data drop.

Last franco kernel i used was 162 and no data drop on this either.

However an issue I have on all kernels I have used (and this is probably not related to the data drop issue) is when I wake my phone after deep sleep (when i am not using wifi), the signal bars switch from blue to grey, and then back to blue after several seconds (maybe 5-10 secs). However I have 3g or H connection throughout this whole process. So it seems connection to google services disconnects during the phone is asleep or immeaditely after it wakes up, and then reconnects after a few seconds. I think this is preventing me from push notifications from gmail, google+, etc while my phone is asleep.
[Samsung Galaxy Nexus] iGoogleNexus:
=\ Nu uh... my boot animation doesn't lie lol

- Google
[Samsung Galaxy Nexus] simms22:
maybe you flashed the wrong kernel?? what does it say in the about phone, screenshot?
[Samsung Galaxy Nexus] arby80:
I do not get any data drops through 166. And then on 173 it barely connects at all. 174 was better. I have not tried 175 yet. It could also be a location thing.
[Samsung Galaxy Nexus] vomer:
Yup :rolleyes:

My first reaction was:

then I was like:
[Samsung Galaxy Nexus] iGoogleNexus:
Lol yeah

- Google
[Samsung Galaxy Nexus] iGoogleNexus:
Lmao

- Google
[Samsung Galaxy Nexus] fatappel:
r174 was working perfect with great performance. r175 seems to still perform well but the rotation settings are not able to be controlled. Phone auto rotates all directions even with auto and 180° off. AOKP b37.

Edit: Rebooted and all seems ok now. That was weird. Sorry for the false alarm.
[Samsung Galaxy Nexus] franciscofranco:
Yes its a joke :)
[Samsung Galaxy Nexus] iGoogleNexus:
Then yes... you Mind F**ked me Franco lol

- Google
[Samsung Galaxy Nexus] vomer:
Haha! Franco, this is how I imagine your reaction after people freaked out :

:p
[Samsung Galaxy Nexus] ntorresla:
Where's the r175?
[Samsung Galaxy Nexus] thepawn:
I was able to get it from the market app.
[Samsung Galaxy Nexus] 15israellai:
That joke was so fun lol

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] tcchuin:
Guys how's the boot animation? I'm on paranoid android rom and flash r175 doesn't change the boot animation
[Samsung Galaxy Nexus] neos_83:
There's no bootanimation in the zip package!
[Samsung Galaxy Nexus] iGoogleNexus:
Then how did I get the trinity animation? O.o

- Google
[Samsung Galaxy Nexus] simms22:
if you flashed or were running trinity beforehand, youd get it. i got the trinity animation before when i flashed franco kernel.
[Samsung Galaxy Nexus] iGoogleNexus:
=\ nah man I've been running Franco since takju was released ... and I was running r74 and it was fine.. until I flashed r75 lol

- Google
[Samsung Galaxy Nexus] vomer:
There is a boot animation option in Franco app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ntorresla:
I have no trinity animation... I'm on 75 now
[Samsung Galaxy Nexus] iGoogleNexus:
Lol its not checked tho ...

- Google
[Samsung Galaxy Nexus] iGoogleNexus:
I'm leaving it now =) it looks nice

- Google
[Samsung Galaxy Nexus] morfic:
Just open it up and ease your mind.

or heck look, his kernel zip around 3.5MB

you see that, you know you got caught cheating on Franco
[Samsung Galaxy Nexus] drawde40599:
huh?

Trinity and Franco?? I thought u 2 didn't get along o_O .:). 175 running great btw!!