yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] drawde40599:
No lag here, its not the kernel

---------- Post added at 10:43 PM ---------- Previous post was at 10:35 PM ----------

249 is perfect, battery great 4.1 screen on , speed great, not one issue at all ,ran the hell out of it today, NO! Data drops like a few people have mentioned and if was going to happen today would have been the day was on phone over 10 hours today ( work) WiFi also perfect never been faster

Thanks Franco! !
[Samsung Galaxy Nexus] arhung:
Is the app useful with the battery life or something?/

CPU Sleeper Dual Core

https://play.google.com/store/apps/details?id=com.eugene373.cpu.sleep&hl=en
[Samsung Galaxy Nexus] Exostenza:
I'm suffering from data drops on 249 and I have traditionally never had the problem.

Just going to leave this here...
[Samsung Galaxy Nexus] giugiu:
Nope.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sachilleas:
I believe that r248 was way better than r249. Signal strength and the ability to maintain a connection is worse now.Other than that excellent kernel as always!
[Samsung Galaxy Nexus] Zantiszar:
Well gonna just got the app now to flash :D
[Samsung Galaxy Nexus] yellowdie:
I had the same thing happen when I was on AOKP. I just gave up trying to figure it out. But it stopped when I switched to Rasbean. :) So it's definitely ROM based, I just don't know what for sure.
[Samsung Galaxy Nexus] franciscofranco:
Yes it's not related to the kernel at all.
[Samsung Galaxy Nexus] yellowdie:
Last night I plugged my phone in, opened up CPUSpy and reset the timers, then turned off the screen and went to sleep. When I woke up, I refreshed CPUSpy and took a screen shot. Zero deep sleep. My screen-off-max is 384, so this makes perfect sense with what GB Man was saying. I charged to 100% in just a few hours, but the phone never went into deep sleep. This isn't a problem for me, I'm just throwing my data into the conversation. :)
[Samsung Galaxy Nexus] sotoskawasaki:
Is this the 4.1 or 4.1.1 stock Kernel? Or is it the same? After we flash this is it necessary to boot to the system once and then flash custom Kernels? Thank you!
[Samsung Galaxy Nexus] abalam:
Great kernel for cm10 love it :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] TEK112:
Do you have BLX set at 100%?
[Samsung Galaxy Nexus] VinceT3:
I reinstalled without an issue this time, go figure. Thanks :)

---------- Post added at 10:22 AM ---------- Previous post was at 10:19 AM ----------

FYI: It won't go into deep sleep when plugged in. Neither my tablet, nor any phone I've had ever goes into deep sleep while plugged in.
[Samsung Galaxy Nexus] osm0sis:
Wifi signal? I find them about the same. I thought r246 might have been a bit better but barely noticable.
[Samsung Galaxy Nexus] Marcb:
Franco, could this wifi driver be of any use to us?

https://github.com/renaudallard/gnexus_kernel/commit/9ce3c4afa475f5fa6301a7ba0afc8d4d4dfb6f5b

It seems people are really talking good things about it... nice signal strenght and stability...
[Samsung Galaxy Nexus] TEK112:
My biggest gripe since day one is BT strength. My headset constantly loses and regrabs the BT connection. Different ROMs, kernels and headsets. Also, I noticed that my BT "leash" is limited to about 6 feet sometimes, because otherwise the connection starts to break up.

edit: Actually, my biggest gripe is signal strength and 4G switching, but I digress...
[Samsung Galaxy Nexus] osm0sis:
TEK: You GSM or LTE? If you're GSM I definitely recommend the new UGLH1 radio.
[Samsung Galaxy Nexus] arhung:
Using 249-512gpu, 230/1536, interactive, no undervoltage, with androidme 1.9.0, 2000mah battery ,3g or Wi-Fi on all day, auto sync on, music for 1.5hours, whatsapp, 2.5hours of screen on time. I think this is not a bad result.

View attachment 1323798

ps. this is the first cycle of my new 2000mah battery.
[Samsung Galaxy Nexus] TEK112:
LTE sadly... I am on a fringe LTE network where I live which makes it harder. It constantly flips between the two. Essentially, killing my battery, so I usually leave it disabled until Verizon builds up their network a bit.
[Samsung Galaxy Nexus] franciscofranco:
Tricky question with few answers. Lets imagine two branches:

1 - Android 3.0 branch where our Tuna device is

2 - Android 3.4 branch where Google is pushing all the new and cool stuff

The newer Wi-Fi drivers in my kernel come from the Android 3.0 branch. They are in fact newer than stock drivers.

Those drivers that you linked and that nikademus is using come from the 3.4 branch and they are the next generation of Wi-Fi drivers for our wireless chips. I don't know if they are better or if they are worse, but I've been wanting to try them. Might not be a bad idea to try them.
[Samsung Galaxy Nexus] ac3theone:
Yes very much Worth it , I use it and I get amazing battery life

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SpecRek9:
Hmm what a great surprise, I've been using M5 and recently moved to 249, what a surprising battery life change.

Way to go FF!, thanks a lot :)
[Samsung Galaxy Nexus] yellowdie:
I do, yes.

Yeah, that was what I was saying. There was some back and forth about it a few pages ago, so I wanted to test it overnight and confirm. :)
[Samsung Galaxy Nexus] Marcb:
Nice man! Thanks for the explanation!

Looking forward to test them if you need extra beta testers! :good:
[Samsung Galaxy Nexus] osm0sis:
Oh hell yes! Count me in. Anything to further improve the abysmal Wifi reception on JB and the GNex in general!
[Samsung Galaxy Nexus] gianton:
I had the best WiFi and data cell connections with FuguMod kernel, definitely worth trying them.
[Samsung Galaxy Nexus] nuwan32:
Try clearing cache and dalvik cache
[Samsung Galaxy Nexus] Kurre:
This indeed sounds interesting. I have huge respect towards nika..And it origins back to his SGS development times. It's because this guy has a little different and interesting approach to the kernels and it's always nice to see those kinds of tests etc :)

I hope this could lead to even better wifi drivers :D
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't honestly remember which version it is, I uploaded it 1 month ago. If it doesn't boot on 4.1.1 then it will be a 4.1 version but I forgot sorry. When you flash a kernel I would boot to os then flash another after.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yeah I remember when he pushed .35 kernel to 3.0.8 commit by commit ;)

I will try those drivers and see what happens.
[Samsung Galaxy Nexus] CADude:
Hell yes! That's the only thing I think needs significant improvement. The Wifi isn't terrible but it needs to be better. Glad to see you are putting Wifi on higher priority, Franco.
[Samsung Galaxy Nexus] chugger93:
Hey guys/Franco;

I'm updating my wifes nexus tonight, from an 827 nightly to 913 (JellyBro). I did my usual wipe twice of everything and installed the rom. I installed the franco app (yes I purchased x2 to support Franco!) but what's weird is nothing shows in the whats new box, or if you hit download latest nightly normally you can see a change log etc. It's all blank. Works great on my nexus, always has.

I tried reinstalling, etc but get nothing. I find it important to have the changelog, and what's new for everytime I update the app.

Thoughts on resolving this?
[Samsung Galaxy Nexus] ac3theone:
hey quick question...If I use any colors over 200 will that burn out my display quicker? I ask since my colors are and they look amazing

Red- 280

Green-292

Blue-350

Rgb -4,0,9

Trinity contrast -24

Gamma -6
[Samsung Galaxy Nexus] chugger93:
NM...I think I figured out the issue. My bad
[Samsung Galaxy Nexus] CADude:
Considering you went to a new nightly of CM10 Jellybro, its probably causing the problem. We've always had issues with CM and Franco's kernel in here according to many posts I've read so you should do 1 of these things:

1) Wait for another nightly that solves the problem

2) Such to the M1 build of CM10 and see if that doesn't have the problem.

3) Stop using CM10 and go to something like AOKP.
[Samsung Galaxy Nexus] franciscofranco:
r250:

* Completely new Wi-Fi drivers from Google's Android 3.4 branch - thanks nikademus for your commits, was much easier for me to follow your path and committing them from your repo
[Samsung Galaxy Nexus] J-Hop2o6:
I wouldn't attempt over 200 (Samsung default). Try mines:

Red 142

Green 125

Blue 200

RBG -7, 0, 7

Trinity contrast -24

Gamma 1.0 (5)

---------- Post added at 07:10 PM ---------- Previous post was at 07:06 PM ----------

What? Never had problems using JellyBro (CM10 Nightly CP's) and Franco.Kernel. Can't believe you told him to stop using CM and use AOKP when AOKP pulls a bit from CM. Makes no sense.
[Samsung Galaxy Nexus] kyokeun1234:
According to AOKP team on Twitter, AOKP is not cm based... Just fyi

Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] J-Hop2o6:
I didn't say BASED, a said they pull a bit from CM.
[Samsung Galaxy Nexus] jcmm11:
It's possible, especially if you run at 100% brightness all the time. I have mine set at well over 200, because when I'm outside in the desert sun (Las Vegas) I can't see the phone otherwise, but I use auto and most of the time it's on the lowest setting, although sometimes I run it at 2% (which is dimmer than even the lowest auto setting). 25% is bright enough for almost all situations. Auto is just more convenient than switching presets though.
[Samsung Galaxy Nexus] willl03:
Let's see if I get grey signal bars with 250, thanks for the update
[Samsung Galaxy Nexus] osm0sis:
Reception seems to be back to where it was in ICS, if not better! :D

Feels fast. Giving it a bit more time before I comment on wifi stability but so far so good!
[Samsung Galaxy Nexus] nuwan32:
honestly ive never tried that high because people SAY that its bad for the amoled, but ive never heard of anyone with a burnt screen.

but anyway try my settings, theyre a bit lower and also look super awesome

200

215

280

-2

0

10

trinity: -12

omap: 1.0

disabled content adaptive
[Samsung Galaxy Nexus] erezak:
Very cool. :cyclops:

That's not already in github, right?

Thank you again for your amazing work.
[Samsung Galaxy Nexus] farfromovin:
Could someone please help me out with downloading a 512Mhz GPU 249 version? On 250 all my WiFi seems a little slower with the next gen drivers but I've already deleted 249 off my device and can't get it back from within the app anymore :banghead:
[Samsung Galaxy Nexus] fatappel:
r250 wifi not working for me. Able to see my network but keeps refreshing and saying obtaining ip but never does. 9/12 AOKP nightly with Verizon fios router.
[Samsung Galaxy Nexus] Zantiszar:
Yo Franco funny bug or dunno in the app it says latest nightly 249 but if you download it shows changlog for 250 and if you download it again shows 249 but installs 250 lol confusing but works :D
[Samsung Galaxy Nexus] fatappel:
You can find links to all previous releases on the OP. Link you want is:

http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/
[Samsung Galaxy Nexus] johno168:
Auto flashed 250 384 GPU. Wifi seems fine. Thanks franco! :good:
[Samsung Galaxy Nexus] AndAllThingsWillEnd:
Not working for me either.
[Samsung Galaxy Nexus] sruel3216:
250 performance didnt seem as smooth. i like 248 out of the last few release for performance
[Samsung Galaxy Nexus] vasumit:
r250 Working fine on CM10 latest nightly. No wifi issues for me. thanks franco!
[Samsung Galaxy Nexus] prembox:
**Post Deleted**
[Samsung Galaxy Nexus] Culex316:
New Wifi driver is working just as fine as with the last driver for me.
[Samsung Galaxy Nexus] drawde40599:
Flashed 250 , WiFi came on and is working fine no issues like few here , I can't tell if faster or slower in speed feels the same ? I don't use speed tests since results are never constant .. just wanted report all is well
[Samsung Galaxy Nexus] Dattack:
this new wifidriver is a definitely improvement. now I get a signal in my garage which I was unable to before. thanks
[Samsung Galaxy Nexus] funkyblue04:
New wifi driver is Ok here so far.
[Samsung Galaxy Nexus] 3oudreaux:
Does anyone else have any issues with setting the rgb gamma for Green -4 or less? On my gnex the screen goes blocky green at that setting. I was gonna upload a screenshot but when I view the screen shot after putting the value back it looks normal. Is this a software problem or maybe a bad screen? On stock deodex JB. Franco milestone 5
[Samsung Galaxy Nexus] mrfleetwood:
I noticed same thing with 248 & 249 already. Problem was very minor and momentarily thought.

250 feels good, very good so far.
[Samsung Galaxy Nexus] leontine:
New drivers don't work for me, less signal strength, so I went back to 249.

249 is doing great for me, good battery and performance no complains at all using CNA snapblacked. Thanks!
[Samsung Galaxy Nexus] LibertyMonger:
Working great for me. Had to give it some time to settle in, didn't have wifi for a few minutes but now it is steady and strong. I wonder how long you tested it before switching.

***EDIT***

I do not get the great battery life people have been talking about, I get like 10 hours with about an hour screen on with stock settings, I don't know why would appreciate some advice?
[Samsung Galaxy Nexus] P30SiNa:
New Wifi drivers are just AWESOME.
[Samsung Galaxy Nexus] TyroneLT:
From what I've heard and read yes. I've also read that setting your contrast too high will do the same thing.
[Samsung Galaxy Nexus] rnjsgurwn96:
With 250, wifi won't connet to network
[Samsung Galaxy Nexus] ectodroid:
Works for me with 250

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bartolinio:
have you tried to restart the router?
[Samsung Galaxy Nexus] sachilleas:
It's very strange how different performs each kernel to everyone of us. From my experience still r248 is the best kernel as far as wifi strength is concerned.

I' ve used r250 and it's worse than r249. I get no wifi reception in places i did before.
[Samsung Galaxy Nexus] Kappa Lamda:
Wifi works good for me with r250!!!
[Samsung Galaxy Nexus] Fenvarien:
Wifi works great here too, with very good reception.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] erezak:
I believe it comes from two factors:

1. Personal "bias" - we don't actually perform exact lab tests.

2. Usage scenarios are individual.
[Samsung Galaxy Nexus] Hessi93:
Can you add an "Reset all settings" in the app?

Thank you very much for your great work!

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] kalintka:
Stick on r241 for long, now 250 is good

sent from Jelly bean tapatalk
[Samsung Galaxy Nexus] rnjsgurwn96:
It isn't the router's problem. It won't connect to any network at all.
[Samsung Galaxy Nexus] Marcb:
weird...

did you wipe cache and dalvik, just to be sure?

Also, make sure your router is set in WPA2 TKIP / AES security...

For anybody out there still using WEP... please change immediately :D

It's a regular driver for our wifi chipset... it shoudn't perform like that...

I have great wifi signal and speed with these drivers...
[Samsung Galaxy Nexus] rnjsgurwn96:
I did a wipe on both of those..

Running on PA 2.1.

Any version before 250 worked fine with 512 gpu
[Samsung Galaxy Nexus] yellowdie:
So far I like r250. Wifi signal is good, definitely better than before. I'm not sure about idle yet, but performance is great. :D :good: Thanks, Franco!
[Samsung Galaxy Nexus] osm0sis:
I've been using "Keep Wi-Fi on during sleep" set to "Only when plugged in" to avoid wlan_rx_wake locks that I haven't been able to sniff out to a particular app. This has drastically improved my battery life and my mobile data isn't taking much of a hit from it either. Awhile back franco improved the speed at which the wifi driver connects and that made that setting viable since it was suddenly seamless whereas before you might have to wait. Only issue I was seeing with that setup and r241-r249 was sometimes it would instantly connect but then the bars would go grey from losing its connection to Google Services, then go blue again in a minute or so.

Now, with r250, this problem is gone too! And the signal remains strong, fixing this issue for me; even with my old signal-blocking crappy case (waiting for a replacement for my broken new one in the mail). Amazing! :D

Update: It does still go grey briefly, but seems to reconnect more quickly with r250 than other builds. :good:

Edit: To everyone experiencing problems, uncheck "Avoid poor connections" in Wifi Advanced settings. The wifi driver in r250 is better than any I've seen in JB but it still might not compensate for that issue.
[Samsung Galaxy Nexus] Marcb:
Well, there's a newer driver: https://github.com/renaudallard/gnexus_kernel/commit/974fa3a344a19cff0fcd0c9e3857a575ac0c0e71

Let's see if Franco will update and maybe it will fix the issues some of you have...
[Samsung Galaxy Nexus] kalintka:
Franco please add tunable vibration strength

sent from Jelly bean tapatalk
[Samsung Galaxy Nexus] Marcb:
Well, I'm on stock 4.1.1 so can't comment on PA 2.1, but maybe, could it be a ROM issue?
[Samsung Galaxy Nexus] dehein:
Fastcharge

Hi i have encountered something strange.

I have created to widgets on my homescreen, which enable and disable fastcharge mode.

But then i start the app. In here nothing changes under enable Usb fastcharge. It stays the same.

Seemed odd to me. But in the end, i have my to widgets and they both work great. (with SManager)
[Samsung Galaxy Nexus] babyporch:
Hi Francisco, git not updated for #250 ? Need to recompile for eth support.

Thanks.
[Samsung Galaxy Nexus] osm0sis:
Hmm, I'm also stock 4.1.1. Could be.
[Samsung Galaxy Nexus] Inpain:
Which Nightly release of r250 should i get for my Galaxy Nexus ? the 384GPU or 512GPU ?

Thanks :D
[Samsung Galaxy Nexus] Marcb:
Try the 384Mhz...
[Samsung Galaxy Nexus] osm0sis:
384 is factory spec for the gpu. 512 is o/c, uses a slight bit more power and only some phones can handle it. If you're interested in 512, install it first and see if you get any weird graphical glitches. If you don't, you're good to go; if you do, switch to 384. Easy peasy.
[Samsung Galaxy Nexus] franciscofranco:
Thanks. Im on a trip today, I'll see if I can get a reliable 3G connection when I board the train and tether to my computer.

I already said a few times that I dont want to add that feature. Use Trinity, it has vibration control.

Yes my git is not updated yet. I created a new test branch where I pushed all these wifi patches but I wanted to make sure it was 100% working and merge it with the main branch instead of having different branches causing some confusion.
[Samsung Galaxy Nexus] Pkt_Lnt:
Get Better Battery Stats and CPU Spy (XDA versions available) and see what is keeping wakelocks or alarms running, sucking juice.

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

You might want to check on Better Wifi on/off. It may not help, but it might.

http://xdaforums.com/showthread.php?t=1801284
[Samsung Galaxy Nexus] ac3theone:
#250 working fine for me here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Already have BBS, and I've gotten rid of everything big under Alarms and Partial, including Facebook, but still wlan_rx_wake was top under Kernel. That's why I tried the sleep policy, and now wlan_rx_wake is good. chamonix does fantastic work so I've had my eye on Better Wifi for awhile too but I'm waiting for it to become a bit more robust. Thanks for the help though! :)
[Samsung Galaxy Nexus] !crazy:
Isn't 384 OC too?
[Samsung Galaxy Nexus] phydo:
Franco with 250 I can't even connect to my work WiFi due to poor signal. Normally I'm great here. All other devices are fine. Just tossing my vote. Back to 249 :)
[Samsung Galaxy Nexus] frenchy714:
307 GPU is stock

Yes, 384 is a slight oc.
[Samsung Galaxy Nexus] Pkt_Lnt:
The BWO/O works for me as it is since I only have wifi at home and keep it connected for voip. I know you don't miss much. The louder app and such. :)

R250 is good for me, will see how battery life is today.

Galaxy Nexus / Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
My WiFi is working on 250

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
"Stock" is a matter of semantics. 307 is stock GPU clock on the Galaxy Nexus, but 384 is the factory spec clock for the actual GPU chip, which is why I specifically said "factory spec". So technically the GNex GPU at 307 is underclocked. Think of it how you want to though, 307 and 384 have the same voltage the way franco implemented it, so no impact on battery at the higher clock, just better performance.
[Samsung Galaxy Nexus] AndyGnex:
**edit**

literally same post as above..

btw, i've been using the 512gpu version, not noticing any major diff in battery usage, in other words, battery is as good as ever :o
[Samsung Galaxy Nexus] Marcb:
No quite...

307 is underclocked... our TI OMAP 4460 supports 384mhz speed but Google has decided to underclock to 307...
[Samsung Galaxy Nexus] TheMorpheus:
I'm unable to recharge my phone on #250; back to #249
[Samsung Galaxy Nexus] osm0sis:
Nothing changed except the wifi, everything else is freak occurence, user error or placebo. I'd suggest trying it again.
[Samsung Galaxy Nexus] AndyGnex:
Set min cpu speed for screen off not sticking, returns to 729 after reboot..

im on #249.or was it always that way
[Samsung Galaxy Nexus] Dr Byte:
@Franco - headphone jack debounce?

Not sure where this falls, but there is probably a driver component.

For the first time tonight, I tried using headphones to watch a video on my GN. It keeps pausing at random intervals, as short as one second. I checked the log, and it does indeed have spurious disconnect events related to the headphone jack (which was securely in.)

Through the internal speaker, it always plays perfectly. No pauses.

Given the notorious "volume rocker" issue that plagued the GN in the early days, my first instinct was to check the log and confirm it was a real event (it behaves as if the plug is removed: pauses the video)

I've only just noticed/confirmed this moments ago; anyone else noticed anything similar?

FWIW, #248 with the Bigxie 4.1 ROM and Bose QuietComfort Noise Cancelling headphones. I mention the type, because it could be relevant: an impedance mismatch issue, since they're active (powered) headphones.

There seems to be no particular rhyme or reason to the spurious events. I can't "produce" one by manipulating the plug, but it will do so without intervention while sitting securely on a desk and away from vibrations. That suggests more of a signalling/impedance/bounce issue than a physical one.

I tried raising my Fmax from 1036 to 1536Mhz, and even rebooting. Still happens randomly.

Thoughts? I haven't dug up the code yet, but I suspect there's no time gating/debouncing on the "disconnect" event... and it's possibly a widespread problem over many kernels. I'd probably never have discovered it otherwise, but I was trying to test the frequency response tonight with an "ultrasonic" ringtone :)
[Samsung Galaxy Nexus] chrisgtl:
Exactly same here!!!

Rasbeanjelly latest with WEP D-Link router. (I have no control over it, this is my work wifi)

Will try #250 with my WPA2 network when I get home.....

Possibly just a WEP problem??
[Samsung Galaxy Nexus] ragnarokx:
Can't connect to my home router either, gets stuck on obtaining IP address. Flashing back to r249 fixed things.
[Samsung Galaxy Nexus] chrisgtl:
WEP or WPA on your home network?
[Samsung Galaxy Nexus] drawde40599:
WiFi

I have 2 Gnexus one had no issue with 250 and WiFi ,other had issue actually staying on.. . All I did was remove account from PHONE" forget network " reboot and log back into WiFi now works fine ///AOKP build 9-14-2012.

---------- Post added at 07:43 AM ---------- Previous post was at 07:40 AM ----------

Reinstall ROM then kernel from same flash.. .
[Samsung Galaxy Nexus] Savant:
WiFi works great on the newest nightly kernel . It doesn't interfere with my Cisco router or my Motorola cable modem. I get great speeds and no complaints from me.

Problem with people it can be user error or it may not be compatible with the ROM they are using. I am using sourcery ROM.