yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aper3caper:
Can't say I've noticed any difference in WiFi on r250. Doesn't seem better or worse to me but then again I usually have a pretty strong WiFi signal everywhere in my house. One thing I did notice is that I completely lost cell service for about an hour in a place where I normally have service. Not sure if that's kernel related or just an AT&T foul up. Keep up the great work Franco!
[Samsung Galaxy Nexus] ragnarokx:
WEP for my home personal router.

I can connect to my home office router though, which is WPA2. Signal might even be stronger, but I wasn't on r250 long enough to say with certainty.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrisgtl:
Rolling back to #249 fixed my #250 'obtaining IP address' loop.

Certainly not user error imo, too many reports saying wifi is broken for some on #250 for it not to be a credible problem.

---------- Post added at 04:50 PM ---------- Previous post was at 04:48 PM ----------

Looks like the newer wifi driver doesn't support WEP any more then.

Damn my work for still using WEP. :eek:
[Samsung Galaxy Nexus] franciscofranco:
Thanks for all the feedback, you guys are just great :)

I already merged the newest Wi Fi drivers from today and did some config changes in hope to fix those Wi Fi problems. The 3G connection is too unreliable here on the train so I will only upload r251 later today when I get some real connection...

In the mean time I almost finished coding the color user profile interface but most likely wont be ready for user release until the end of the weekend/monday.
[Samsung Galaxy Nexus] franciscofranco:
Thats weird!! Can you flash stock rom from Google, flash my kernel and see if it still happens?
[Samsung Galaxy Nexus] Marcb:
For people having wifi problems, can you post what ROM you are currently using and the config. of your router?

Example:

Stock ROM 4.1.1

Wifi N 300mbps - WPA 2 / AES security
[Samsung Galaxy Nexus] Exostenza:
Thought I would pipe in and say that r250 is working perfectly for me and the WiFi locks on so quickly it is ridiculous and the strength is full while the connection is solid.

Great work man!

Now if only you could figure out how to get 3G/H+ connectivity what it used to be on ICS things would be perfect.
[Samsung Galaxy Nexus] SpecRek9:
Installed r250 and have no problems so far, signal has increased one 'bar' from the same place I always get just two bars at work, my connection is with static IP, so, so far, so good.

Haven't yet tried dynamic IP wi-fi connection nor 3G.

Will try r251 whenever its available :)
[Samsung Galaxy Nexus] gm007:
Wifi is really better with the new drivers.

Download wifi analyser from play store and compare before and after.
[Samsung Galaxy Nexus] Wynnded:
I changed my router security settings from WEP to WPA/WPA2 and can now connect using v.250
[Samsung Galaxy Nexus] evodon84:
haha holy crap why were you still using WEP in the first place?

Thanks for the great kernel Franco
[Samsung Galaxy Nexus] Wynnded:
I'm an uneducated noob. And I didn't set up our wireless, some "professional" did. lol

Deal now is though, when everyone comes home from work today and can't connect, they're gonna be like WTF, and I'll have to sort it for them.:eek:
[Samsung Galaxy Nexus] Marcb:
but it's the best thing you did lol....

WEP is really, really old and insecure...

Also check if security is AES... don't use TKIP...
[Samsung Galaxy Nexus] clepsy:
With R250 I get around 10mbps lower speed on both down and up that from R249
[Samsung Galaxy Nexus] RevengeFNF:
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.

How can he push a new kernel to the phone memory to flash it in the recovery?
[Samsung Galaxy Nexus] danielvc:
mount usb storage in CWM, copy kernel, flash.
[Samsung Galaxy Nexus] drawde40599:
Reflash ROM then kernel from same flash. .. pretty common problem with a lot of kernels
[Samsung Galaxy Nexus] franciscofranco:
Fastboot.
[Samsung Galaxy Nexus] EDNYLaw:
I'm getting some random reboots on 250, so I wanted to check last_kmsg but I don't have it in /proc and I just noticed the ability to toggle logging isn't in Franco's app any more. Anyone know the terminal command to enable logging?

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2

Edit: nevermind, found the line in an init.d script disabling logger. However, anyone else getting random reboots? Seems to have happened after r250 and my phone typically thrives on Franco's kernels. CPU at 2xx to 14xx, no undervolting, smart reflex enabled, interactive governor no settings touched.
[Samsung Galaxy Nexus] meanwhile:
Have to admit, #250 data speeds much slower than last version of fugumod kernel #514. I thought they literally the same regarding WiFi and data configuration. Correct me if I'm wrong.

Sent from microwave
[Samsung Galaxy Nexus] osm0sis:
I'm getting wifi in the parking lot at school right now. This was impossible with my GNex previously. r250 continue to impress me! looking forward to 251. :good:

---------- Post added at 04:09 PM ---------- Previous post was at 03:49 PM ----------

Those with Wifi problems with WEP on r250, try the above? Forget your network, reboot and readd it. Any different?
[Samsung Galaxy Nexus] mestanr:
Im now testing r250-384GPU on stock JRO03C and all looks very good. Great battery, no random reboots, very good performance. Testing continue... :)
[Samsung Galaxy Nexus] SpecRek9:
I've just tested the data network and my bw measures 1M down and 116k up, this never happened in 249, Wi-Fi looks ok.
[Samsung Galaxy Nexus] osm0sis:
Solar winds? The kernel doesn't touch the radio.
[Samsung Galaxy Nexus] Swede2008:
No issues here with 250 on toroplus with blackbean v3. Wifi working fine with newer Verizon router, and with my friends old ass router. Seems to be getting better reception, though haven't actually tested thoroughly. Wifi is definitely not any worse than 249.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] derPianist:
Since the past few nightly I am getting INSANE Wifi signal but barely can get H or H+ on mobile data.

Anyone else also?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] Savant:
Lol don't have that problem.
[Samsung Galaxy Nexus] Easton999GS:
why me?

See for me 249 Gave me the best wifi reception and speed ever. with 250 my wifi reception sucks. Ive never actually had wifi issues until build 250 which is weird. My data seems a bit wonky too but i dont know if thats kernel related. I have a Verizon Gnex Toro newer I515.10 baseband
[Samsung Galaxy Nexus] mdomino:
After updating from m5 to r250 I lost the ability to connect to home wifi. All 3 laptops and the other smartphones work perfectly, reverting to milestone5 fixed it.

Every time it tried to connect:

Avoided connecting to <some negative word> internet connection
[Samsung Galaxy Nexus] nemotheblue:
I dunno what happened, but my battery life on r249 was abysmal, like <12 hours with average/moderate usage. I cleared cache and dalvik, downloaded a fresh copy of the kernel (just in case) and flashed again, but still got another day of awful battery.

Since the only change in r250 (and presumably r251) was the wifi driver, I've reverted to r248 for now. I wonder what it is about my phone that r249 didn't agree with it. I'm probably going to wipe the whole thing and clean install MiNCO v5 when it's released anyway...
[Samsung Galaxy Nexus] timbck2:
I had that problem the other day, except with my Nexus 7 (running Franco's kernel), not my GNex. A reboot fixed it.

I think "poor" was the "<some negative word>" in the error message.
[Samsung Galaxy Nexus] Wynnded:
I think that I saw something like "Avoiding Poor Connection" on mine.
[Samsung Galaxy Nexus] emd2009:
Franco's site is down, can someone upload the latest nightly?
[Samsung Galaxy Nexus] mihkohuy:
Yeah the server is down./
[Samsung Galaxy Nexus] Dr Byte:
Headphones cause random video playback pause events

[Video playback in stock media player pausing randomly, but only when headphones are connected - log shows "disconnect" events]

The ROM in question is almost identical to stock JB, compiled from source, with some trivial framework tweaks (battery %, power menu.) Deodexed. JRO03C, 4.1.1

Now that the "official" ROM is out, the obvious thing to do is flash that and see if it happens there too... but since this is a minor glitch in something I don't use normally, I'll try to round up some other headphones/speakers to try and reproduce it... while spelunking into the kernel code for the event text strings.

I used to have several pairs of headphones, but the last two puppies... :)

This is not something I'll be losing sleep over :) It might be an interesting challenge to take on, though!

I doubt it's a module you've even looked at, which is why I suspect it's a widespread issue - possibly JB-wide, if not GN-wide, given the exact preconditions.

I've just reproduced the issue with my (again) Bose Mediamate speakers and my Logitech 5.1 rig on this computer. I played the same minute over and over, and it never stopped in the same place twice.

WiredAccessoryObserver:: Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=0, DEVPATH=....

.... newState toggles between 0 and 2

I'll try diving into the source tonight, but for now a lovely spring Saturday beckons, and the dogs want to go play!

Update:

Ok - a quick google suggests that this is definitely not an isolated phenomenon. It's been reported at least as far back as March this year, on a Toro in ICS. Given the history of sloppy programming in the volume rocker issue, my money is on a software cause - whether it be "disconnection" for a tiny period or the emulation of same by an impedance transient. Gating it for 100ms or so should be enough. Same fix as the volume/GSM interference bug. I've never used the earbuds on this or my previous phones. Might have to try and find them!

Update 2:

It seems to be a known issue with kernels using Ezekeel's Sound Controls - If I turn off the Sound Boost (Level 0 of 3), it doesn't happen :) Just played three entire videos without a pause... but could barely hear them :)

At least that gives us a place to start looking for the fix! One for the FAQ, methinks. Not that anyone ever reads them :) This affects music playback, too, btw.
[Samsung Galaxy Nexus] osm0sis:
removed (since so is the corresponding troll).
[Samsung Galaxy Nexus] incomer:
Is it possible to add NTFS support in your next update?

Great rom further, have bought your franco.kernel app to support you and make it even easier for me! Thanks

Another thing what I'm missing in the app is to possibility to choose your own map where the kernel will be downloaded to..

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Vangelis13:
It'd be interesting to see an educated test; though it does sound reasonable that it'd perform better. Oh well, will flash once I get back to a pc & find out. Obrigado
[Samsung Galaxy Nexus] franciscofranco:
People keep asking me for NTFS and I keep forgetting. I'll do it for the next one!!

Yes, changing the location of the download will be implemented in the future ;)
[Samsung Galaxy Nexus] ratson:
I also don't know what is going on but have way better battery life with new bootloader. did it reset battery stats? I can't understand what the correlation could be...
[Samsung Galaxy Nexus] incomer:
Hehe thanks..!

Can't wait to see it, but I'm loving it right now already!!!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] dpaine88:
Ok I did like 3 google searches and still cant find info on the bootloader...can someone please send me a link?
[Samsung Galaxy Nexus] Vangelis13:
Just bought the app to show you my continuous support; keep up the hard work!!

P. S. If you keep adding features, setcpu will become obsolete.. ;-)
[Samsung Galaxy Nexus] yohinomura:
Yup bought your apps too, Franco.
[Samsung Galaxy Nexus] esoomenona:
I just purchased the Updater as well. Would definitely love to see NTFS support.
[Samsung Galaxy Nexus] franciscofranco:
http://www.google.pt/search?ix=hca&sourceid=chrome&ie=UTF-8&q=PRIMEKL01
[Samsung Galaxy Nexus] dpaine88:
Thanks a bunch Franco!

I don't want to get too off topic from Franco's awesome kernel, but I am really curious on why a bootloader would have an effect on device performance/battery life at all? I thought it was just something that allowed you to install custom recovery and ROMs and get root/superuser.
[Samsung Galaxy Nexus] Thracks:
PRIMEKL01 bootloader for GSM/LTE Galaxy Nexus: http://www.multiupload.com/YUXRJC8M98

Put your phone in fastboot mode, connect it to USB and start "flash-windows.bat". The whole process takes ~30 seconds.

You must have your ADB/Fastboot drivers installed.

//EDIT: Franco, is there a way to buy your app outside of the market? I have an American Express card that (infuriatingly) does not work with the Android market. I want you to take my money, but I can't see a way to get the app w/ reliable updates without market purchasing capabilities. :(
[Samsung Galaxy Nexus] esoomenona:
Maybe you can buy a prepaid Visa gift card, load that into Google checkout, and then put money on it whenever you have some to spare, or feel like buying something? Just a suggestion...
[Samsung Galaxy Nexus] dpaine88:
Thanks for the link Thracks.

I have flashed a million ROMs and Kernels for my Droid and now Galaxy Nexus, but do not have much experience with the bootloader since I didn't have to deal with that on my Droid 1.

Would you be kind enough to give a *brief* explaination of how to flash this? Specifically, how to "put phone in fastboot mode"(is that just into the bootloader?)

Also, how to start the "flash-windows.bat" file? Just double-click it?
[Samsung Galaxy Nexus] cbkitt:
Francos Kernal With AOKP KANG Build 14
[Samsung Galaxy Nexus] razzbaronz:
Actually this is for maguro which is the GSM version. For CDMA/LTE, the bootloader can be found here: http://rootzwiki.com/topic/12866-ra...ootcdma-galaxy-nexus-toroupdated-dec-23-2011/

You'd need to replace the maguro bootloader with the toro (CDMA/LTE) and then make the corresponding changes in the flash-windows.bat file in your link. That said, I think thew bootloaders are exactly the same, but I'll be using toro just in case.

Checked MD5 on both files, they are exactly the same. You can use the method above on both the CDMA/LTE and GSM versions of the phone.
[Samsung Galaxy Nexus] Pierre118:
Is the bootloader for all Nexus versions the same? (cdma, lte , gsm)
[Samsung Galaxy Nexus] razzbaronz:
Just did an MD5 Sum on both, they are one and the same. Sorry to alarm anyone.
[Samsung Galaxy Nexus] drawde40599:
Aosp 14 rom and new 10 kernel, wow its fast!!!! Ima stop crack flashing, so I can get actual idea how good battery is . Thanks!!!

---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------

Primekk15 is bootloader that came with 4.0.3, what is that one?? ( i could be wrong )Probably shouldn't just go posting bootloaders in kernel forum without more info if at all, one way destroy someones phone . All just my option,just saying .
[Samsung Galaxy Nexus] dwang:
build #10 is really awesome. Best quandrant scores yet at 3116. Cpu max set at 1.350 and min at 350.
[Samsung Galaxy Nexus] TwinkyOfHope:
r250 Wi-Fi not working for me either, just stuck on Obtaining IP Address. Even full wipe and ROM reflash didn't help.

Reverting back to r249 got it working immediately.

Just reporting
[Samsung Galaxy Nexus] markop90:
R250 fixed my WiFi issues! Thank you Franco!
[Samsung Galaxy Nexus] Pkt_Lnt:
Yeah, well, I saw someone else with radio issues too, and it bit me today. I know it makes no sense, is illogical, but the r250 kernel was the only change I made.

Wifi was great last night, this morning. On my (bus) commute, I noticed no updates of email, twitter, GMail, etc. Got to work and all data indicators looked fine, except I could get no connection with browser, Play Store, etc. So I rebooted, and still no connection. I booted to recovery, wiped cache & dalvik, rebooted, same problem, no data throughput.

Back to recovery, cleared cache, dalvik, and fixed permissions. Boot to ROM, data shows on, all my signal tech widgets state strong 3g, no throughput, browser and Play store fail to connect. Reflashed r249 in recovery, boot, all my notifications came pouring in as normal.

I know it makes no sense..................

CNA 3.5.0 nightly 09122012, franco r250-384, UGLH1 radio on an i9250 GSM.

Home on wifi with weak edge, so I will test r250 again tomorrow to see if I get the same lack of data.
[Samsung Galaxy Nexus] JkdJedi:
Awesome kernel here and excited about the new drivers, can't wait to test this out

In real time.

Is there a tweak to have the kernel jump to max cpu frequency when I open this thing up from interactive governor? Thanks for the killer kernel!

Tapatalk sent from the future.
[Samsung Galaxy Nexus] drawde40599:
my data was acting funny earlier today got real slow reset itself ( data icons not phone) things seem normal now and only happened once ( never has happened with JB) was it the kernel the rom was it at&t or the boogie man ? I don't no but hey y not mention it ;)
[Samsung Galaxy Nexus] bat0nas:
Something's wrong with the size.

Latest app version as of now.

View attachment 1327865

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Is PC USB working for all on 250? I'm trying to work out if my USB port is broken or maybe a possible bug.

Full explanation here http://xdaforums.com/showthread.php?t=1887303

(This is not USB fast charge related before anyone asks I don't rally use that)

Sent from my Galaxy Nexus

---------- Post added at 08:54 AM ---------- Previous post was at 08:48 AM ----------

Try changing your network security, its been reported quite a few time WEP security won't work with 250

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] farfromovin:
Damn, I was going to say fast charge lol. I don't use 250 because of slow WiFi connections but I'm assuming you've restarted the phone already?
[Samsung Galaxy Nexus] tobitronics:
Can i flash franco nightlies over another wolithout wiping anything? Im running 250 now but would like to see if 249 is better.

Sent from my deodexed Jelly Beaned Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Maybe try the latest version (gsm) uglh1 for me at home it boosted my signal 2 bars.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kurre:
@Franco, I just had a little idea...might be stupid, but anyway :p

Since someone's are having problems with the newer wifi drivers (might be also sometimes user/router error), maybe you could make it user-selectable. I have an example of this.

When I were using SGS with Devil3 kernel, DerTeufel the dev made it possible to choose between different ram settings, even though those are usually hard coded to the kernel. Method he used, was to compile needed driver files with necessary changes (stock ram, big ram & huge ram) and user was able to choose between these ones by echoing value (0,1,2) to a file in a /data/local/devil folder and rebooting after that. While booting system then copied correct files to corresponding folders and selected configuration was in use.

Dunno if this is worth of all the trouble, but this was just a wild thought while drinking my morning coffee :D this method could be also used with other features also..Maybe for GPU OC, etc also?
[Samsung Galaxy Nexus] GrimReaper24:
Please keep things on topic folks.. Other wise infractions will be issued.. Due to some folks going off topic..

Have a good weekend.
[Samsung Galaxy Nexus] tobitronics:
Anyone? I assume I can just dirty flash?

Sent from my deodexed Jelly Beaned Galaxy Nexus
[Samsung Galaxy Nexus] glennv17:
I'm having some issues lately, where I've auto-flashed the kernel through the app, and then on reboot, about 5-10 seconds in regardless of whether I've unlocked the phone or gone into a menu or two, my phone will freeze and then reboot about 5 seconds later. I'm pretty sure this didn't occur when I flashed r249 through CWM recovery (after having the problem occur a couple of times).

Has this happened to anyone recently? I've uninstalled and reinstalled the app hoping that will fix it, but I'm wondering if it could be related to the settings I have had set in the app and through AOKP's performance settings, things such as CPU settings and setting my own voltages. Any help would be appreciated, whether I stop auto-flashing or how I should manage the the app vs AOKP's performance settings, given they both relate to the CPU/undervolting side of things.
[Samsung Galaxy Nexus] danielvc:
yes, flash away :)
[Samsung Galaxy Nexus] franciscofranco:
Im not entirely sure thats possible here. But I will think about it.

Im semi away for the weekend, came to visit my GF. Have fun peeps.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah iv been forced to restart as the phone just turns off when USB is connected. I guess its not kernel related was just a long shot. My USB is probably damaged

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] supernova_00:
Just changing sound boost to level 2 should fix this. If I remember correctly the issue only happens at level 3.
[Samsung Galaxy Nexus] Easton999GS:
249 had the best battery life ive ever had with this phone. 250 was probably the worse battery life. over wifi.
[Samsung Galaxy Nexus] Fenvarien:
Same here, just reverted back to r249 because r250 was much to battery hungry. My connection is primarily WiFi.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] mestanr:
Same here. Now i have primary H+ and battery use is very good, but if i turn on WiFi, battery is much faster consumed with r250 than on r249.:eek:
[Samsung Galaxy Nexus] emd2009:
Anyone have a link to 249
[Samsung Galaxy Nexus] Fenvarien:
Sure, http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/franco.Kernel-r249-384GPU.zip

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] hasnol143:
So after flashing 250, then trying to connect to my wifi (I changed roms so I had set it up again), it would refuse to connect because of poor signal. after reverting back to 249, everything works again!
[Samsung Galaxy Nexus] JkdJedi:
I'm on Codename 3.5 and new wifi drivers is working, getting stronger signals to boot. (I use to barely get a signal from my bedroom, I'm now one bar away from getting full signal) . FYI. Just reporting. :p

Tapatalk sent from the future.
[Samsung Galaxy Nexus] Crwolv:
I agree there are a ton of things that don't make sense like a kernel should have nothing to do with your radio and signal but sometimes it does and I also noticed that using clockworkmod Latest touch version) there so many more problems. , after advice from my friend Jared(jrummy) i switched to TWRP 's latest. And now have zero problems. Running Maddoggin rom so I have all the latest over the air binaries but my radios were still on old (Fho1..toroplus) so I asked Shabbypenguin and he sent me the new radio zip file (Fho5) wos big difference everyone. if you can do it why is the radio it sounds more like Motorola photon and not a Samsung I'm impressed. Running imossion lean kernel using franco's play store app. it is so cool to flash a kernel with 1 click without going into recovery thank you for Franco:cowboy: and I hope this helps someone:cowboy:
[Samsung Galaxy Nexus] mrfleetwood:
Me too. The battery use of r249 is just incredible.

The wifi worked mostly ok with r250, but now and then I faced the situation where the wifi signal was very low - even if the phone was right next to the router - and the phone was in 'Obtaining IP' loop.
[Samsung Galaxy Nexus] derPianist:
With 250 i am also facing problems where downloads are failing.

I cant download a cm10 nightly without a fail.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for all the feedback. I will try to release r251 very soon, probably in the next hours.