yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ssglackey:
I had datadrops on 162, flashed imoseyon's kernel just for performance test and than flashed 162 back and since that I had no datadrop. Don't know if it is just coincidence, but I am ok since that.

Currently I am on 163 with excellent battery life that I had last on r123. Now I have 3:30 screen time and still 25% left, power save, dualcore half on wifi half on 3G, custom auto brightness (lowered) levels, Gsm 1750batt.
[Samsung Galaxy Nexus] mikespe:
Guys I don't think this is a kernel issue. I'm still on 163 & I had a drop earlier today...I'm betting it's carrier related...
[Samsung Galaxy Nexus] drawde40599:
GSM, xxla2 radio, At&t, USA (Alaska, ) liquidb1.4 (i dont use powervsaver settings )no data drops, no wifi issues on any franco build
[Samsung Galaxy Nexus] Diger36:
I also have XXLA2 in Holland but I had data drops on r163. I just also had one on r165.
[Samsung Galaxy Nexus] nodstuff:
OK so far cdma looks like there are no drops, but we have a small sample size.

GSM is having mixed results, drops and no drops, more interestingly I have no drops on.XXLA2 and the last poster has the same radio and has drops.

there must be a correlation.

Any ideas anyone??

Hardware revision??
[Samsung Galaxy Nexus] TyroneLT:
I've noticed that stock settings have seemed to work the best after trying a bunch of different settings. With a mix of wifi and some 3G with customized auto-brightness I've found that on CM9 I average at least 4 hours screen time a day. Great work Franco!!!
[Samsung Galaxy Nexus] Sveke:
Looks like a central Europe issue to me.

Gsm guy in Alaska was good.
[Samsung Galaxy Nexus] renna1992:
I have no problem with Franco kernel but it was very bad with lean kernel.
[Samsung Galaxy Nexus] Theshawty:
I might just possibly have data drops as well. GSM Galaxy Nexus, XXLA2 radio.
[Samsung Galaxy Nexus] nodstuff:
So far from two results western Europe is OK.

Any more USA GSM users wanna chime in?

Francisco is western Europe too and he has no signal drops.

So ireland, UK and Portugal OK so far in Europe and Belgium

, Slovakia and Sweden not OK.

at&t USA Alaska OK.

Hardware versions people?? Visible in bootloader.

mine is revision 9
[Samsung Galaxy Nexus] opethrocks:
Im gsm on at&t in the us, and ive had signal drops with the last, id say, 10 nightlies. But it seems to have started when i switched from aokp to cm9, i never had a single drop on aokp b28-32. But a few pages back someone posted some terminal commands to reset the modem. Since i ran those commands i havent had a single drop
[Samsung Galaxy Nexus] nodstuff:
To get as much info as possible maybe we should include:

Rom

radio

Region

Carrier

Hardware version.

Am I missing anything??
[Samsung Galaxy Nexus] celyst:
UGLC1 radio + AOKP b34, had 3 data drops on the r163 kernel, once even while on wifi (data on my phone just stopped even though everything else connected to my router was working). Switched back to r156 and 0 data drops for the last 24 hours of usage, both on wifi and 3G.

If it's a problem with my carrier, then it must have been really coincidental to only happen right after I flashed r163...
[Samsung Galaxy Nexus] Diger36:
Mine is 9 too... It seems to occur only when the phone is in deep sleep and I unlock it. It looses (or shuts off) final that second. If I look at my usage my signal wasn't red before that. And it is not always. So far on r165 I only had it once in about 3 hours. Yesterday on r163 i had it almost every time... So it had improved so far. Let's see how it goes.
[Samsung Galaxy Nexus] DebauchedSloth:
USA / UGLC1

Drops with 162 definitely an issue, along with generally lower signal values. I have a very good idea what my signal values should be in various low-signal areas and what should have been a usable signal was no service with 162.

Also saw a few instances where wifi showed signal but data was not connected.
[Samsung Galaxy Nexus] Diger36:
ROM AOKP M3

Radio XXLA2

Region Dutch (Europe)

Carrier Vodafone

HW 9

Ondemand 729- 1344

Powermode balanced

No other performance tweeks
[Samsung Galaxy Nexus] wayne850:
no signal drops in good old germany ;) i'm on aokp 37. i never had a single signal drop since i have my device (march)
[Samsung Galaxy Nexus] Diger36:
Tried that too. Didn't work for me....

Wiped cache, didn't work. Want to do a clean install tonight to see if that makes a difference.
[Samsung Galaxy Nexus] nodstuff:
The only difference between me and you is rom, I'm on LS 1.4

Same carrier, same hardware revision, same settings. Everything.

There must be a common denominator.

Its a mystery.
[Samsung Galaxy Nexus] andQlimax:
i would say just different hardware..every hardware component is different from an other..that why for example some people can get lower uc or higher oc, and some not...

so there is some kernel low level setting that cause this data drops..the same data drops that happened with the 4.0.4 imm76d (partially fixed for most user with the imm76i, even some users still have it!)
[Samsung Galaxy Nexus] franciscofranco:
I dare you all with signal problems, mother-in-law problems, over heat problems etc to flash this rom cleanly and report back after a few days:

http://fitsnugly.euroskank.com/rascream/?id=maguro

Thank you.
[Samsung Galaxy Nexus] Diger36:
Thanks, will do...
[Samsung Galaxy Nexus] CMNein:
'tis a ridiculously awesome ROM.
[Samsung Galaxy Nexus] nodstuff:
Great idea, clean results!

Good thinking!

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

Uc and ov is CPU related, that's a CPU manufacturing tolerance issue, signal is different.
[Samsung Galaxy Nexus] ssglackey:
Guys, just try to flash imoseyon's stable kernel for a while and then flash franco back. Nothing to loose.

Btw. I had datadrops on xxla1 and xxla2 too.
[Samsung Galaxy Nexus] andQlimax:
ya..its same, there is an hardware component for the signal also..and every hardware component have its tolerance as u say..

also the data drop on imm76d was not happening setting the min cpu freq at 700mhz..so cpu and signal drop can be also related

anyway lets see what's happen using the rom franco suggested
[Samsung Galaxy Nexus] zenzip:
r163/165 charging AC is very slow how know a way to fix?
[Samsung Galaxy Nexus] BigBake88:
Make sure you are using the stock charger, and check to see in settings>battery that it is displaying it charging as "AC" and not "USB". I know I have plugged in my phone to an AC outlet before, and it said it was USB and charging very slowly. Unplugging it and plugging it back in worked for me.
[Samsung Galaxy Nexus] zenzip:
stock charger and cable...but show USB in battery charging...unplugging and plugging it back don't solve issue :(
[Samsung Galaxy Nexus] Flukester69:
How do you flash it cleanly? Recovery mode? Autoflash with your app FC's every time after 100% but then again I said that over a month ago right? Sure glad I paid for this app with literally no active support. I've had the signal problems (gray bars) for a while now and I've used many different ROM's but really only your kernels (nightly). Funny though that while it's gray most times I can still cruise the internet etc.
[Samsung Galaxy Nexus] Gahh Its Lee:
No idea if this will help you but it helps me. If they are gray go into accounts and manually sync everything for Google. The gray bars are linked to something with syncing (I read this idk how true) so manually syncing always makes them blue again for me.
[Samsung Galaxy Nexus] martin.capeletto:
Basic question: how can detect a data drop??
[Samsung Galaxy Nexus] Flukester69:
Ya I myself have been trying things too, my APN's I had 2 in there one for tethering and I combined my 2 Rogers one into 1 APN setting. I thought this actually resolved the problem but then realized that it was still there. I'll give the Google sync thing a shot and see what happens.
[Samsung Galaxy Nexus] drawde40599:
Download" no signal alert 2.0.3 from market its free works great .
[Samsung Galaxy Nexus] rascarlo:
Nice. Thanks man
[Samsung Galaxy Nexus] aquavalanche:
franco, i read at the euroskank website about the mods he use..

and i saw at the kernel==> Kernel: bcmdhd: Enable ad-hoc networks

is it possible to enable ad-hoc network in your kernel?
[Samsung Galaxy Nexus] martin.capeletto:
thanks!!! will try
[Samsung Galaxy Nexus] BigBake88:
Hmmm...make sure all the plugs are nice and secure to your phone and to the charger. Try maybe a different outlet. Not sure if this will help, but make sure fast USB charge is disabled. If non of that works, try flashing a kernel before 163 and see if that solves the issue.
[Samsung Galaxy Nexus] Hanny:
just some dirty stuffs appear when **** happens. had that once when i got reboot with a exceedingly low UV as experiment.

simply turn on USB fast charge, turn it back off, now plug and see. if not? reboot and plug in then it will be fine

edit: ofcoz, unplug before making changes to those fast charge options
[Samsung Galaxy Nexus] vomer:
What rom is this? Never heard of it before....?

Also, I thought you were working on Liquid ROM?
[Samsung Galaxy Nexus] mtmjr90:
I'll just add that I'm using the GSM GNex on T-Mo USA and I've had data drops too. I was still registered on the network but no data. Adding the APN manually didn't work, nor did rebooting. I finally fixed it by removing the SIM, rebooting, replacing it and rebooting.

I've also been having multitasking issues whereby downloads get killed in the background, Skype signs out, and other apps like Boid have to entirely reload data upon returning to the app. Dunno if that's a kernel issue or not, but I thought I'd include it.

Info:

AOKP 36

FK 163

Rev 9

Baseband I9250XXLA2
[Samsung Galaxy Nexus] rascarlo:
It's my rom. Compiled from source.
[Samsung Galaxy Nexus] sago62:
It seems to me that in the last 2 builds the temperature of the phone is more ... Warms up just using 3g ... also 55 °
[Samsung Galaxy Nexus] vomer:
Could you please point me to a list of features? I do not see any thread for it on xda.
[Samsung Galaxy Nexus] sruel3216:
can you make toro plz??? i have heard good things about your rom
[Samsung Galaxy Nexus] BigBake88:
Any chance for a CDMA version? :D

---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------

+1
[Samsung Galaxy Nexus] raubkatze:
Here's secret rascream thread) - http://xdaforums.com/showthread.php?t=1455874
[Samsung Galaxy Nexus] rascarlo:
Status bar toggles, customizable lock screen targets, navigation bar customization, volume rocket wake and skip track, battery percentage, long press to kill, CPU settings, themed in black
[Samsung Galaxy Nexus] franciscofranco:
No active support? I've delivered tons of updates, I mean literally tons. I've been re-coding and improving everything in small bits. If you think thats 0 support you can buy LauncherPro that hasn't been updated in an year.
[Samsung Galaxy Nexus] vomer:
Dude... don't feed the trolls :D

---------- Post added at 03:16 PM ---------- Previous post was at 03:15 PM ----------

thanks man, looks interesting. Will check it out.
[Samsung Galaxy Nexus] Theshawty:
It's funny how you seem to think you're entitled to 24/7 support just for buying an app. I think the price tag is mostly a donation to keep Francisco's motivation up, not to receive on-the-clock support. Try buying an Apple product. No support unless you open your wallet very widely.

He does, in fact, bring support in the way he can, but people tend to ask the same questions thousands of times instead o searching.

Also, if I were you, I wouldn't depend too much on what the signal bars show. As Erfant once said, if they're gray or completely gone but you can still do the things you do in an acceptable speed, why bother with them? They are very flaky, jumping all over the place.
[Samsung Galaxy Nexus] celyst:
True, sometimes my signal bars are grey but reception works and data works.
[Samsung Galaxy Nexus] franciscofranco:
Should be easy. I'll take a look.
[Samsung Galaxy Nexus] franciscofranco:
Can you try r165 please.
[Samsung Galaxy Nexus] nodstuff:
You shouldn't have bothered answering.

That comment about no support was idiotic to say the least, the app is updated nearly as often as the nightlies.

Thanks for your work Francisco and we all appreciate your hard work and diligent attitude towards bugs.

Some people are just ungrateful.

He has kernels for numerous devices and apps too while juggling college work.

Give the man a break.
[Samsung Galaxy Nexus] gknnn':
Break... Tell you all when at end and yes its boring at work ;)
[Samsung Galaxy Nexus] franciscofranco:
O_O That's wizardry.
[Samsung Galaxy Nexus] raubkatze:
Looks really fine) 2000 mAh battery?
[Samsung Galaxy Nexus] BigBake88:
Franco, I think I may know the answer, but I figured I would ask. Plus, it will break up all these posts about data issues ;) Will a 192Mhz slot be included in your next Milestone release?
[Samsung Galaxy Nexus] Theshawty:
192 Mhz? Is such a low underclock even safe for the processor?
[Samsung Galaxy Nexus] chlehqls:
What the...extended battery right? The most I can get consistently is 3 hours screen on after hitting roughly in the high 40 percent on battery.
[Samsung Galaxy Nexus] Flukester69:
fc for auto flash has been there for almost 2 months and latest app of yours don't fix problem I don't care somewhat because kernel flashes but fc should be fixed but you never showed any interest. Is that good support? 2 times I mention it now and it occurs on both my nexus phones using cm9 and kangorade ROM.
[Samsung Galaxy Nexus] CMNein:
Logcat?
[Samsung Galaxy Nexus] andQlimax:
do you mean the hot reboot? its not a force close...its an hot reboot

well..i was worried a bit at first, but data should not be corrupted
[Samsung Galaxy Nexus] nodstuff:
Tbh you are in the minority, i don't know if anyone else suffers the same problems you do.

Francisco works hard to fix bugs, people report them, he fixes them.

Don't be a ****.

If you have a problem post it in an informative way and it will be fixed.

Your problem seems limited to you/your from maybe.

No one else reports it.

He will fix it if you tell him.
[Samsung Galaxy Nexus] Flukester69:
I can get that later sure but everyone has the problem I am sure. As I said, I have 2 phones on different ROM's that does it. I seriously doubt it's a stray and barely seen issue. Guess like me, it's not a big deal if the kernel flashes anyhow.
[Samsung Galaxy Nexus] andQlimax:
look my previous post, its an hot reboot..not force close
[Samsung Galaxy Nexus] 0kk0:
Franco...your kernel(s) rocks men!

Really! Also your app... Thnx a lot! Btw....this thread...what the hack? read over a million times!! Lol
[Samsung Galaxy Nexus] apsis:
@Flukester69

Try to clean the Cache and Data of Francos App, or reinstall it. Never had those issues.

No reason to blame Franco btw, he's doing a really great job here, so much App and Kernel Updates and also active in this thread all the time. But i guess its kinda hard for him to keep the overview on this thread the whole day so you should be more understanding to him.
[Samsung Galaxy Nexus] Flukester69:
Tbh, I did tell him, 100+ pages back. Maybe everyone else is just blind or don't care because it applies regardless. Ever think about that? Love the rest of your post, the tough guy behind his LCD act. Classic.
[Samsung Galaxy Nexus] raubkatze:
Sorry but fc for auto flash sounds like a joke...

You have two way to flash franco.kernel: auto flash with hot reboot and manually using recovery.

As andQlimax wrote it is not fc, it's just hot reboot. Don't worry about it)
[Samsung Galaxy Nexus] Flukester69:
Sigh. I'm not BLAMING ANYONE ffs. Dude I flash ROM's almost every day. It happens on EVERY ROM and on 2 phones, that after data/factory reset, wipe cache, wipe dalvik restore from titanium or from google. Like I said to the other guy, you are probably just missing it. Try paying closer attention after the progress bar hits 100% and reboots.
[Samsung Galaxy Nexus] zenzip:
after full wipe and fresh install of ROM and kernel I've solved my battery issue...

my batterylife improve around 30%, on AOKP b36 franco r163 power ode full power so interactive 729-1344 byt max screen off freq. 384mhz...

18h with 3h screen on ...

+1 Franco! :D
[Samsung Galaxy Nexus] nodstuff:
No one else has your problems.

Not trying to be a **** regardless of what you think.

I was trying to help.

and again, no need to be a ****.
[Samsung Galaxy Nexus] Flukester69:
K then why is there a Report button if it's not FC? I can make out the report button just as it reboots. I'm not overly worried about it, I posted about it 100+ pages ago. Do I look worried about it? Did i post about it over and over again throughout the thread? No I didn't, but seeing how I paid for the app and posted the problem and some 50+ kernels and app updates have gone out without a fix, yes, I do wonder.
[Samsung Galaxy Nexus] nodstuff:
Its supposed to reboot after an auto flash, that's the idea.

Any other problems please tell Francisco.

He welcomes bug reports.

I have ZERO problems with Franco app whatever way I use it.
[Samsung Galaxy Nexus] Gahh Its Lee:
Wait so its still working fine it just flashed a fc real quick?
[Samsung Galaxy Nexus] 0kk0:
Btw... With nightly 165 my Battery drain on idle is: 0.1% per hour!! A-Mazing!!
[Samsung Galaxy Nexus] Flukester69:
Yes, I just tried now and updated to latest nightly 165 but this time reboot occurred too fast and I didn't see it or it didn't occur. My last nightly 162 it did it. I will grab logcat and send it to him when it happens again.
[Samsung Galaxy Nexus] wayne850:
Very nice can you please post your settings?
[Samsung Galaxy Nexus] raubkatze:
I didn't read +100 pages ago and didn't see that you had an error message. So if you have app fc and want for Franco support use CatLog and post/share your error log.
[Samsung Galaxy Nexus] Meannekes:
What is the stock Voltage of wlan, and what is the wlan voltage in #165?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Lambetts:
Quick one. Is M3 384mhz gpu or 512mhz? And what's stock speed, 384??

Thanks guys.
[Samsung Galaxy Nexus] nodstuff:
I think I'm in love with your logic <3
[Samsung Galaxy Nexus] BigBake88:
Milestone releases are always stock 307Mhz GPU clock
[Samsung Galaxy Nexus] 0kk0:
my settings are almost default...

using rom aokp m5 + nightly 165 (384mhz gpu). no undervolting or something like that... i do turn off wifi on screen off. so only 3g... and if my drain was higher i noticed with use of an app... the drain was caused by an app/service running on background. yesterday i was running nightly 160 for 28 hours... 1.75 hours screen time and still 28% batt left.

what do you get?
[Samsung Galaxy Nexus] Sveke:
I used to bug out about stuff like that but the only thing that suffered was my blood pressure.

It's nearly impossible to **** this phone up= don't give a ****.

So as long as the kernel flashed and everything looks ok.....I'm good with it.
[Samsung Galaxy Nexus] Theshawty:
Not that hard. Just searching for posts by you in this thread and look for a post that describes what you have said.

I may not agree with you on all things, but even I think that there should be way more use of the search button. It's there for a reason and we're not each other's servants.
[Samsung Galaxy Nexus] drawde40599:
+1000000000
[Samsung Galaxy Nexus] wayne850:
I always get about 4hours screen time and about 2,5days battery time on 163. I'm trying now 165
[Samsung Galaxy Nexus] franciscofranco:
Well I can't reproduce the bug in my app. I don't mean it doesn't exist, but I can't reproduce it. Can I get logcats please?
[Samsung Galaxy Nexus] franciscofranco:
Stock voltage is 2.0V, nightly r165 is 1.850V.
[Samsung Galaxy Nexus] willl03:
There you go
[Samsung Galaxy Nexus] nodstuff:
Well any test known to man will conclude that this is indeed a logcat.

Tried thanking but I'm limited to 8 per day

BUT!!!! My diagnosis as a fake doctor is that this is indeed a logcat
[Samsung Galaxy Nexus] Theshawty:
And a mighty fine example if I may say so. A fine example indeed.

All kidding aside, I flashed the 165 nightly and it seems to only get better and better with each release. Wifi seems smoother and more receptive and the battery feels slightly better and the overall performance feels better (might be a placebo, though)
[Samsung Galaxy Nexus] tixed:
Is checking "Enable fast USB charge" in your app in settings the same as using toggle from AOKP ROM feature?
[Samsung Galaxy Nexus] Nutsonfire:
Using the Franco app, go for auto flash nightly, window opens, bar doesn't move stays at 0%. Leave the app try again, same, leave app, go to browser, suddenly phone reboots and 165 is installed.
[Samsung Galaxy Nexus] Theshawty:
Franco: Is there a special reason you added Immoseyon's kernel to your app?

Also, does the auto-flash clean anything? It doesn't seem to clean cache and I though it was recommended to do when flashing kernels?
[Samsung Galaxy Nexus] KennyG123:
Let's all try to be mature, courteous adults in here.

In other words stop flaming and trashing each other.

I will be back in a little while to clean this crap up!

Now behave

Thank you for your cooperation

Friendly Neighborhood Moderator
[Samsung Galaxy Nexus] franciscofranco:
Somehow the activity didn't behave correctly but it still downloaded the file in the background... hum.

It doesn't clean anything because nothing needs to be cleaned!

I need some help here. The strange signal losses started in nightly r161? And it happens when coming out of deep sleep right?
[Samsung Galaxy Nexus] thoth_19:
Anyone else having issues mounting storage to pc. With this kernel it only charges when i plug into pc. I can flash faux kernel and have no problem mounting storage.

Rom - miuiscotland

kernel - nightly build 165

PC OS: Ubuntu 12.04

Franco keep up the great work!

Edit: When USB fast charging is enabled phone wont mount storage. Disabling fixed my issue.
[Samsung Galaxy Nexus] Diger36:
For me it started with r163, And yeah..., when coming out of deep sleep and waking it up. Making a Backup right now to flash the ROM you recommended. Will be tomorrow....

EDIT: I think I passed r161.... So I can't tell for sure....
[Samsung Galaxy Nexus] LifeInAnalog:
.. sigh... I had such high hopes for your wizardry... the mother-in-law is still here after flashing.
[Samsung Galaxy Nexus] Theshawty:
Ah ok, I best listen you since you're the kernel dev ^^

I can't really say if I really have signal drops and/if when these arose either. I don't even know if it's because of this kernel or the ROM I use (CM9 nightly 235)

But it would be fair to say my signal actually drops when coming out of deep sleep (real deep sleep and not just a 350 Mhz-ish sleep) and quite randomly while I use the phone the signal dies twice or trice. This, however, may be because of my carrier, though.

I'm sorry, though, I cannot say what specific kernel version of yours it would be, all I can say is that I've used your kernel for a long time now.
[Samsung Galaxy Nexus] KennyG123:
Thread Cleaned

FNM
[Samsung Galaxy Nexus] chakra:
Wow Franco, they are going to have to make a bigger thanks meter for you.
[Samsung Galaxy Nexus] franciscofranco:
People with the signal/data drop when coming out of idle can you do this:

echo "GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features

Report back if it fixed.
[Samsung Galaxy Nexus] nodstuff:
All is good on liquid smooth 1.4

R165

XXLA2

Ireland

Vodafone

Oh and 512mhz too,my phone only likes 384 normally.

Franco FTW
[Samsung Galaxy Nexus] lucas4ever:
Franco. Would u recommend to replace default kernel with your kernel ?
[Samsung Galaxy Nexus] franciscofranco:
Well do I really need to answer that question? :D
[Samsung Galaxy Nexus] nodstuff:
maybe..... dates please781]Franco. Would u recommend to replace default kernel with your kernel ?

Derp a derp, derp derp derpy derp.

Yes please.
[Samsung Galaxy Nexus] holyzombiejesus:
That's standard. Dunno about your ROM, but on AOKP when you activate fast charge it tells you in big bold letters that you won't be able to connect to your PC with that on. It even repeats the warning after every reboot :p