yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] KJW979:
So far 263 reconnecting with my wifi without a problem.
[Samsung Galaxy Nexus] cyanoviper:
i just noticed the wifi drop issue too. wpa2 no wep here...
[Samsung Galaxy Nexus] The Gingerbread Man:
I told a lie, just found I have connection issue too. Went to local shop for a walk and WiFi didn't connect on return and now WiFi is stuck turning on. No wep security here

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ansysic:
After flashing r263:

- wifi toggle working again

- wifi direct working again

- reconnect works (for now)

hope that fixed it

(wpa2-psk aes)
[Samsung Galaxy Nexus] thuynh022:
263 gave me a sod after first reboot. Had to battery pull to get it run again.

Also, my phone always reboots when I make phone calls after 248. Any body have any idea what's going on? I wiped cache and dalvik. Still reboots. I can't make any calls at all.

I'm running bixie's 4.1.1 no mods, no oc/uv.
[Samsung Galaxy Nexus] osm0sis:
No problem with calls here.. try it with minco or stock?

Made another logcat in the last 15 to see what it's up to while things are connected and saw some stuff that still seemed sort of odd/looped. Filtered for wlan0 since that was the majority of it, and posted below.

Edit: Filtered for wifi and also got a few entries I didn't see before, with WifiService and ConnectivityService (308) connecting and disconnecting, and "NetTransition Wakelock for WifiStateMachine released by timeout."

[log removed]
[Samsung Galaxy Nexus] ChazzMatt:
:rolleyes:

You are really showing your ignorance of the dangers. WEP has been outdated for a decade now and criminals ARE taking advantage. Each of these situations could have been easily prevented -- just by not using WEP.

Last year:

http://www.cnn.com/2011/TECH/web/07/13/wifi.hacking.neighbor.sentenced.wired/index.html

http://www.itmanagerdaily.com/13-businesses-hacked-after-using-outdated-routers/

and even this year:

Hacked WEP Router Results in $600 Bandwidth Bill

http://www.dslreports.com/shownews/Hacked-Router-Results-in-600-Bandwidth-Bill-121024
[Samsung Galaxy Nexus] osm0sis:
Well that's good Chazz, but it is a standard (however outdated it may be) and some people are still forced to use it, so the kernel needs to support it correctly.

I'm sure everyone is putting in petitions to their workplace IT manager in your honor. :)
[Samsung Galaxy Nexus] Marcb:
It'd be best if router producers would stop supporting WEP and only provide WPA as an option...
[Samsung Galaxy Nexus] mssam:
Does anybody know what the recommended i/o sched is? Having a hard time keeping up w/ all the post...:)
[Samsung Galaxy Nexus] TEK112:
Not necessarily. Some older technology only recognizes WEP which still more secure than nothing.

---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------

Franco's default. He spoke about the others and has picked which he feels is the best. I forget which that is, because I just flashed a new ROM with air kernel and I am giving it time to bake.
[Samsung Galaxy Nexus] mssam:
Yeah, same situation I'm in. Thanks tho...
[Samsung Galaxy Nexus] frenchy714:
That's completely up to you. Some prefer "deadline" and some prefer "bfq". I haven't noticed any notable differences between the two (on my phone), but you may have a different experience than me. As always, YMMV. Here's a good post to help you understand the different schedulers and governors, and what they do:

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] harmohn:
bfq is the default scheduler.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] frenchy714:
Franco's default scheduler is BFQ.

EDIT: Sniped by harmohn :)
[Samsung Galaxy Nexus] franciscofranco:
People with re-connect Wi-Fi bug, can you tell me if it happens with this kernel please: http://minooch.com/franciscofranco/Galaxy Nexus/JB/Jelly Bean/wifi_tests/r666_test.zip

Thank you.
[Samsung Galaxy Nexus] tryceo:
Okay..

This was my little test. I put the phone into airplane mode and just let it sit there. However, when I got back from a roughly 2 hour break, the battery was at 96, down from 100. And it says that the phone was awake for some time before I actually opened the screen.

I don't know why this is happening... is there another battery logging program I can use that is more specific. I want to know why the phone is randomly waking up.
[Samsung Galaxy Nexus] ock:
Usually, the first few % after a fully charged battery are not representative.

About the awake bars, I get those even when battery drain is less than 1%/hr, so I usually ignore them since they don't make a difference

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
All of that yes, but max brightness, I love the screen too much.
[Samsung Galaxy Nexus] tryceo:
About how much drain per hour should I expect with airplane mode?
[Samsung Galaxy Nexus] lichti1901:
Maps, Facebook, Letitude, News & Weather, ... can wake your device.

Ive dalated facebook, email, exchange, newy&weather, books, maps, street and google earth.apk from my rom to make it cleaner.

i lose less than 1% an hour in idle.

---------- Post added at 08:13 AM ---------- Previous post was at 08:05 AM ----------

Download the bootloader and place the .img file in the fastboot directory.

Put your GN in fastboot mode, open cmd and navigate to the place you have put the file in. (C: - root on my pc) and then type fastboot-windows flash bootloader bootloader********.img! ******* --> the name of the bootloader!

Sorry for trolling this thread!

Best regards
[Samsung Galaxy Nexus] tryceo:
Can someone link the new boot loader. I can't find it.
[Samsung Galaxy Nexus] Dr_Ownage:
Here is a challenge for you. Search this thread. About 10pages back. There is also a link about 2pages back. There is a contextual search now implemented in xda. Use it! :-)
[Samsung Galaxy Nexus] viskas:
Forget me of I am asking something stupid.

How do I find the "draining" App?

Cpu Spy? What else could I use?

Sorry for my newbie question!
[Samsung Galaxy Nexus] kjwalker:
Battery Monitor Widget
[Samsung Galaxy Nexus] Dr_Ownage:
Battery monitor widget is a good one...

CPU spy.

Better battery stats.
[Samsung Galaxy Nexus] Stretlow:
May i also ask what rom you use mate and doesn't the brightness on max do your battery in a few hours?
[Samsung Galaxy Nexus] Sayan1987:
Installing the new bootloader doesn't wipe anything right?

Which benefits does it have?
[Samsung Galaxy Nexus] Dr_Ownage:
No it doesn't wipe anything.

Various improvements. Just give it a go...
[Samsung Galaxy Nexus] viskas:
Thank You!
[Samsung Galaxy Nexus] drawde40599:
color

Question -- maybe just MY eyes but the white color dose not look white to me?? Has tint to it?? Normal with this kernel? Or is it the phone or maybe just me?
[Samsung Galaxy Nexus] phenom9:
Just want to confirm - for the newbie who is buying this phone shortly:

1) use the GN tookit to root/custom thing

2) use the bootloader update

3) purchase the franco app from the app store to update "kernel"

is there anything i may have missed? (I tried my best, read MANY pages but could not understand what AOKP was).

Thank you!
[Samsung Galaxy Nexus] :
AOKP is just good and everyone should have or ;-)
[Samsung Galaxy Nexus] incomer:
AOKP is a great rom, it stands for Android Open Kang Project and you can find the most updated version here: http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-14/. Its a rom with a lot of tweaks, and his one customation menu!

You don't explain what AOKP is, only that everyone should have it, but if he don't know what it is....
[Samsung Galaxy Nexus] inffy:
Well there is always Google, which tells you what it is.
[Samsung Galaxy Nexus] mike216:
The recently nightly is kicking ass! Lovely :thumbup:

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] murdah204:
I don't know about the reconnect bug..... But after flashing 263... I always 1 bar of wifi in my room..... Where as before I got 2 or 3
[Samsung Galaxy Nexus] psxsnake:
try flashing...
[Samsung Galaxy Nexus] willl03:
I'm gonna try it. Is it possible that a kernel leaves some trace behind? I had trouble with 248-262 wifi / signal so I went back to 246 that I've been running for weeks without problem, and I get the stuck wifi problem on it too now

EDIT: I WAS STILL ON r262 WHEN THE PROBLEM HAPPENEND, DIDNT FLASH 246. NOW I'M ON IT AND IT'S GOOD
[Samsung Galaxy Nexus] ssCISengineer:
I disagree

please remember to thank me for e-peen points!

Sent from a Galaxy Nexus between here and there.
[Samsung Galaxy Nexus] bat0nas:
I am still getting that -1B :(:(

View attachment 1336774

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] psxsnake:
franco, 666 work

no more wifi problem
[Samsung Galaxy Nexus] franciscofranco:
Weird. Probably a problem on our host.
[Samsung Galaxy Nexus] Exostenza:
I just dl'd 263 and the -1B thing was there still.

Thought I'd let you know.

Really it doesn't hamper anything, but as a nice clean app you might care about it as the developer.
[Samsung Galaxy Nexus] maxwintrobe:
same here, wifi bug requiring reboot after going out of range fixed with r666_test.zip, thanks
[Samsung Galaxy Nexus] elnovio:
For me it solved that bug thanks. Not the strongest signal, but working :)
[Samsung Galaxy Nexus] osm0sis:
The log looks a lot cleaner with lucky number 666. ;)

The weirdness took a while to kick in previously so I'll report back later, but so far so good!

Edit: FYI the build number actually appears to be 667 in the updater and System > About..
[Samsung Galaxy Nexus] etche:
I'm trying #666.

I can't leave my office again right now to test reconnecting, but at least I can confirm disabling and re-enabling wifi is working ok!

Thanks.
[Samsung Galaxy Nexus] ac3theone:
R262 running fine for me, its crazy how so many ppl are having issues.

I have a linksys e1500

Wpa2 -aes

Wireless n only

Many other devices connect to my router, no issues

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leontine:
#666 fixed the reconnect problem for me!

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Bruistur:
Same here. r666 solved my WiFi issues. When the WiFi interface would lock up on disable, even mobile data would become unresponsive. Settings would say it was disabled, but the icon showed connection.

Thanks Franco r666 fixed it.
[Samsung Galaxy Nexus] franciscofranco:
It bothers me alright, but like I said I believe its a problem from my host. In the app there is a method called getContentLength() that gets the file size via the HTTP headers that are passed through the connection packets. If the size is not properly given then we have a problem and the app displays it incorrectly. Somethings are a little beyond my control ;)

Nice to know r666 fixed it, I'll push it officially as r264.
[Samsung Galaxy Nexus] nikulogical:
It must be the host because it shows the download process fine when flashing lean kernel.
[Samsung Galaxy Nexus] franciscofranco:
Yes its the host. Let me put it this way, I'm wasting 1TB bandwidth per month on the host. Considering every kernel is around 4,5Mb and all those other small files the app pushes, 1TB is monstruous. The demand is so high that its normal that some times its not possible to get the right sizes of the files just like I explained in the last post.
[Samsung Galaxy Nexus] sotoskawasaki:
r262 has significally weaker wifi signal comparing to r249. At 1.5m from my router the signal is only 2 lines (thats half)!

I just saw there is a newer version. Flashing now.
[Samsung Galaxy Nexus] franciscofranco:
It's the same Wi-Fi driver on both.
[Samsung Galaxy Nexus] sotoskawasaki:
You are right! I messed up the releases :) Was it r248 or r246 that had a different wifi driver? Anyway it doesnt matter much. I just find it odd that 1.5m from the router and the signal strength is down to half.
[Samsung Galaxy Nexus] franciscofranco:
Check the DBM and not the graphical representation, I'm 1 meter away from the router and I don't have all bars. With the SGS3 I have all the bars in the same place. only r250 and r251 feature different drivers.
[Samsung Galaxy Nexus] jsn:
I'm seeing it too, almost every day a different signal strength while sitting in the same spot at the same distance from my router.

These issues are hard to debug I guess. It can also be your neighbor using a leaky microwave oven, or an old wireless phone

or some other radio-interference. Even electrical charges and humidity in the atmosphere influence the signal.

But as long as I have a relative good signal and performance, I find it no biggie :cool:
[Samsung Galaxy Nexus] ac3theone:
I'm pretty sure the way it measures the signal isn't all that accurate. I'm always a couple inches away from my router and sometimes I'd only have 2 or 3 bars, sometimes ill have full 4 bars. Either way it should be full at all times since I'm right next to the router. Even though I don't always have full WiFi bars the connection quality is the same. It only degrades if I get far from the router. It was like this on my HTC mytouch 4g slide on a ICS ROM, even though it wasent full wifi bars it worked fine. So ppl unless your actually far away from the router don't pay that much attention to the signal bars.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] L-ViZ:
got a little question, using latest kernel, 264. pushing files via filezilla/swiftp to my phone, got a writing-speed of 3-4mb/s, but ever 5-10s the upload to my phone stops completely for a short moment :( anyone experienced the same?

just to make clear, it´s a 700mb file. these stops would make sense if it were mp3 files.
[Samsung Galaxy Nexus] harmohn:
Anyone else experiencing issues with touch sound on CM10_M1 / r264? Seems to work with r251 :confused:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] glennv17:
Franco, I'm still getting the freeze and reboot bug that I've mentioned a few times now. Auto-flashing your latest nightlies (I skipped all those Wi-Fi test ones because I was sick of it freezing and rebooting) all make it happen.

I don't know what's causing it, but it happens at varying times. Sometimes it's as soon as the toast notification shows that your app has been granted superuser access, others it is as soon as I unlock the phone.

It's frustrating, because it's been happening for a while now. It probably started around r245? I'm pretty sure I flashed Leankernel through your app not long after it first happened with your kernel, and it didn't reboot, so I don't know if it's the kernel or your app. Either way, I hope you can give me some insight into what it could be.

Edit: I downloaded the latest nightly zip from your app, denied the app SuperSU permissions and then flashed through recovery and I've now had no freeze and reboots. So one of auto-flash or SuperSU permissions is breaking it for me.

If it was the permissions side, could it be that it is competing with AOKP's ROM Control? Once when I watched it freeze, it only froze after your app gained SuperSU permission, which was about 5-10 seconds after ROM Control had gained them.
[Samsung Galaxy Nexus] nikulogical:
Latest nightly seems to be great for wifi.

Hopefully I didn't speak to soon this time lol.
[Samsung Galaxy Nexus] boysetsfire:
Wi-fi seems REALLY great for me too (r264) :)
[Samsung Galaxy Nexus] 15israellai:
Flashed 264, but I'm still at school so I'll report later :):sly:

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] joeyfong:
r264 working great with 802.1x eap, thx
[Samsung Galaxy Nexus] ÜBER™:
Beautiful... and not even from 100%

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] wisefreakz:
Gnex Dead after r264...

Well... 4 hours after applied the r264 (coming from r262), i was browsing internet thru wifi and it suddenly freezed with a screen panic (like an old Atari) then phones shutdown.

After that.. bye bye Gnex.

Not blaming the kernel directly, but... what a coincidence...

What a shame....:crying:
[Samsung Galaxy Nexus] kyokeun1234:
Wait... it died completely?

Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] wisefreakz:
yep...
[Samsung Galaxy Nexus] isinisterx:
Don't see how a kernel can 'kill your phone' ... did u try pulling the battery and recharging it?
[Samsung Galaxy Nexus] wisefreakz:
Well... i left the battery out for 15 min... no luck.

Battery was on 79%. I also tried pluging it on charger.. no signal...

Remember i`m not blaming the kernel directly (i have no knowledge for that)... but a coincidence...
[Samsung Galaxy Nexus] kyokeun1234:
I know you're not bashing anybody here... but wow... I feel really sorry for you man :(

But you can't Odin or do anything either? No omap methods?

Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] wisefreakz:
Thanks for you caring about... i feel terrible.

No nothing till now. Gonna get rest and report back tomorrow when i`ll have full access to my PC.

Cheers
[Samsung Galaxy Nexus] CADude:
Can somebody confirm this issue for me on Maguro?

With r264, if the screen is off, Wifi doesn't seem to connect even if Wifi PM_FAST setting is on. I tested this by turning off my mobile data and letting Wifi take over and lo and behold, things like Whatsapp messages don't come in until I turn on the screen.
[Samsung Galaxy Nexus] zubin111:
Hi franco, great kernel to start with, I am on CNA working great with r262 384, i tried to flash r263 512 from the app by auto flash, it stuck in a boot-loop at the flash screen, had to reinstall everything from the scratch again using tool kit, what is the correct way to install then, not from the app?
[Samsung Galaxy Nexus] drawde40599:
All u had to do was reinstall ROM and kernel from same flash in recovery, using the tool kit wasn't necessary unless u didnt have your ROM downloaded to ur phone for some reason, or just reinstall your backup. I'm sure Franco auto installer is great but manual flash gives u complete control my recommendation

---------- Post added at 09:13 PM ---------- Previous post was at 09:10 PM ----------

What were u over clocked at?
[Samsung Galaxy Nexus] wisefreakz:
I was on stock kernel... max 1228
[Samsung Galaxy Nexus] justme1988:
My Phone died once, i was able to repair it using Nexus toolkit and flashing full stock rom
[Samsung Galaxy Nexus] wisefreakz:
point is mine doesnt give signal of life... not even turn on...
[Samsung Galaxy Nexus] drawde40599:
Do u have a jig? If u do put it in and it should go to boot loader or Odin mode on its own, if it don't , put in jig and hold power button till boots, or pull battery install jig install battery hold power. If that don't work call SAMSUNG u should still be under warrenty
[Samsung Galaxy Nexus] jltorrente:
Same story: Flashed 264 on top of CNA 3.5 & Milestone 5 and now it's stuck on logo, tried nandroid restore from recovery, full wipe + install cna 3.5 and milestone5 and no luck... :(
[Samsung Galaxy Nexus] zubin111:
Nope nothing worked that time, did factory reset, wipe cache, and installed CNA, no luck.. again went to recovery did factory reset, wipe cache, wipe system... again stuck on bootloop on splash screen... While starting it does update some apps, then again goes to the splash screen and loops... I had no other way out but to wipe it all and reinstall fresh from the toolkit...
[Samsung Galaxy Nexus] jltorrente:
Crap... that's exactly what's happening to mine... :S...Sooooo, I guess that toolkit it is... :(
[Samsung Galaxy Nexus] Pete7ate:
Just on the side here, a quick one.
[Samsung Galaxy Nexus] ace-user:
so i flash r262 and battery life is really good…but for some reason, the battery starts draining really quick from 40%…it drains 1% almost every 5 mins on idle without wifi on…anyone knows wat's the reason?

i'm using stock battery btw…
[Samsung Galaxy Nexus] Fenvarien:
R264 installed well and is running very stable and fast @230-1305. WiFi and battery life are great :)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Jose Viegas:
Is it me or the wifi icon has changed to fade out color after r264 upgrade? Almost invisible :confused:
[Samsung Galaxy Nexus] Mayday_XL:
My settings are Interactive/ Deadline (230-1305 Mhz), but with the r264 my phone did not use the 1036 Mhz. :confused:
[Samsung Galaxy Nexus] michi_1983:
hm.. for some reason, with r264 my phone won't connect with my wifi at home at all. flashed back mileston5 meanwhile.
[Samsung Galaxy Nexus] RevengeFNF:
Im using the last R264 release.

Wifi is working great. Just a doubt. I have Connectify on my laptop to share Wifi over Ad-Hoc.

But the Nexus can't see the network. I know that Android by default don't do that eather.

Just asking because with my P500 and your kernel for it, i can connect to that Ad-hoc Wifi.
[Samsung Galaxy Nexus] Mayday_XL:
I am back to the stable version and everything is fine.
[Samsung Galaxy Nexus] meanwhile:
Still running #666, so far so good. Whilst at home managed to connect/disconnect from WiFi without a glitch. Will test once back again, since left WiFi on.

Sent from microwave
[Samsung Galaxy Nexus] 15israellai:
Just now I was testing Tasker and tried to get out of the wifi range, but utterly failed. Usually I would easily do so. That was awesome, franco!

Anyway you guys' problems are kinda scaring me... I'm CNA3.5 on 264. Somebody should investigate this.

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] The Gingerbread Man:
I was having some micro lags scrolling on #666 1036mhz interactive. Lazy gov seems to sort it out. This isn't specific to just #666 it seems to be a general thing since the dynamic interactive. Using 512 version as always. Will test latest version of kernel when I get back from work.

Sent from my Galaxy Nexus

---------- Post added at 11:36 AM ---------- Previous post was at 11:28 AM ----------

This is why nightlies are best to the experienced as sometimes things don't go as expected, anyone can join in the fun though. Its all good as long as you know you can return to stock from what ever you have done.

Arhd differs in the fact it is based on major google releases not based on aosp which is a little different. Both a pure Google experience.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Care to be a little more specific?
[Samsung Galaxy Nexus] mpokwsths:
Absolutely true!

Micro lag in scrolling and also some ms delay before the window and transition animation starts. Also noticed that happens after the dynamic settings version. Older versions didn't exhibit that behavior. Also happens with ondemand. Verified in many ROMs, with other kernels that doesn't happen.
[Samsung Galaxy Nexus] saintpanache:
Having issues is à great learning experience. A bit stressful sometimes though :P.
[Samsung Galaxy Nexus] franciscofranco:
I'll make the dynamic settings a choice for next nightly ;)
[Samsung Galaxy Nexus] rodnar77:
I had to go back to 251 for WiFi to work properly. I tried each revision until it worked properly. It will connect, but after awhile with screen off, it can't find my wifi,. Turning off and on (wifi) takes for ever. Just restarting phone gets connection back...

Thanks again for your work!
[Samsung Galaxy Nexus] The Gingerbread Man:
Awesome, thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Franco has been messing with WiFi stuff, I don't see how a few issues posted here are even related, problems described here sound like user error to me, or pushing the phone to hard ,agn user error. ( my opinion!!)
[Samsung Galaxy Nexus] CADude:
I can confirm this on r264. Even with Wifi PM_FAST turned on, wifi won't connect when the screen is off.
[Samsung Galaxy Nexus] Wynnded:
Sometimes after reverting to a previous kernel for half a day or so, and then going back to a version that wasn't working so well can be successful. For example, last evening I flashed r264 and my device wouldn't boot past the Google screen. I booted into recovery and flashed r249 from my SD card and ran it for an hour or so then tried r264 again and all has been well for the last 10 hours or so. There are just so many variables with these devices that a person can't always condemn a particular kernel on the first try....