[Q] Nexus S WiFI Issues - Nexus S Q&A, Help & Troubleshooting

Hi There!
I just got a Nexus S to try and first thing I noticed is that it can't find the wireless at my house. I have 7 other devices which work fine, and it's not a reception issue since I can't find it standing right beside it either. I am running AndroidME 1.2.3 based on 4.0.3.
I have the same WiFI access points at work and they are working fine with this device, but on the same token, all my other devices are working ok at home!
Any ideas?

Most likely on something like channel 13 and the locale chosen limits the channels it picks up (for legal reasons? all stupid imo). Try changing the channel on the router or have a search for how to remove the restriction.
Otherwise, it may be an issue with your router only using the 5GHz band, I'm unsure if the Nexus S can handle that or not. They'd be the main things to look for.

Could it be the "wifi_country_code" issue? I've seen this problem in ROMs based on 4.0.3.
What band are you using on your Wireless device? As Harbb stated, have you tried changing channels (1,6,11), or only allowing b/g standards?
Can you try another ROM based on 4.0.4 ICS?
----------------------------------------------
BTW, there is a WIFI fix on CyberGR v9 OPs. You might want to check it out:
http://forum.xda-developers.com/showthread.php?t=1425344

Related

[DEV] AOSP Bluetooth Stack on CM6/7, help & testers needed

I cannot pair my vehicle's headunit to a CM-powered device, starting with CM6 RC2. (RC1 worked as expected).
I would like to build the stock Android Bluetooth stack and replace that portion of CM with it, in an effort to see if it resolves this problem for me. I'm also curious how the new Bluetooth stack in Gingerbread will behave, as it's apparently received an overhaul.
Ultimately, I'd like provide a package so that CM users could easily "flash" a new BT stack if they're having problems with CM's modified version.
I'm a junior developer, and I have Ubuntu on my machine, as well as AOSP Gingerbread and CM6/7, all building correctly. However, I lack the knowledge (or even a starting point) on what I need to do to accomplish this.
Anyone willing to offer some advice?
Additionally, if anyone else out there is having problems, please post here--once I get this working, I'll need test candidates to see if it helps resolve their issues as well.
EDIT: Starting here. http://source.android.com/porting/bluetooth.html
Never had an issue with bluetooth and my vehicle or a couple of others while running CM 6.x or any of the nightly builds of cm6. Sometimes a kernal I flashed would break it, but otherwise it worked fine. I done this one both a alpine blue tooth module and factory ones.
What are you syncing to?
aduljr, the type of headunit I have is called "BlueConnect", and is built-in to my 2009 model year Hyundai Elantra. This is the manufacturer's website: http://www.autointelligence.com/
Like I said, it worked with CM6.0.0 RC1, but stopped working starting with RC2 and hasn't worked since.
So far I've started reading about the BlueZ stack, but haven't made more progress than simply reviewing some make files.
As always, if anyone has any pointers (or if anyone is also having BT-related problems), please post.
Thanks.
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
timwoj said:
While you're working on the bluetooth stack, can you look into the lack of DUN/PAN support on the the Evo?
Click to expand...
Click to collapse
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Shidell said:
I suppose I might as well--I'll have to delve into Bluetooth pretty deep I suppose, so I'll see what I can do.
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
have you tried updating to cm6.1 and trying with a stock kernel?
jsseidel1 said:
The Savage Team will help.
my suggestion is start a private google group, its a great way to collaborate with your team
Click to expand...
Click to collapse
Interesting, and appreciated. I'll look into a Google Group, although for now I'll work out of this thread unless this grows into a large project.
BrianDigital said:
have you tried updating to cm6.1 and trying with a stock kernel?
Click to expand...
Click to collapse
I have tried 6.1 with an alternative kernel (Kings) to no avail. Do you have a kernel you'd suggest I pair with 6.1 for testing purposes? I'm more than willing to do so for testing purposes.
Shidell said:
What are you hoping to do with DUN/PAN support? Mobile networking/Ad-Hoc of some sort?
Click to expand...
Click to collapse
Basically, I'd like to be able to tether my phone over BT. The Evo doesn't provide a DUN or PAN service that OS X can see (never tried windows), so things like Android-Wifi-Tether don't work in bluetooth mode.
does you phone work with any other bluetooth device?
aduljr said:
does you phone work with any other bluetooth device?
Click to expand...
Click to collapse
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
BuddaBelly said:
This is appreciated. I stopped using CM because they changed something with bluetooth that would cause my Motorola Rokr headphones to constantly cut in and out. I asked the question over at CM's forums but never received any help there. Before with RC6 the headphones worked flawlessly and I could actually ride my mountain bike on the trails and never have it cut out. Seems they have cut some power out to save battery or something but hey I'm no dev so who knows. Maybe in your quest to get better bluetooth you could figure out if the power can be turned up for those of us that just want a stronger connection.
Click to expand...
Click to collapse
+1 I have this same problem. CM has a much weaker bluetooth connection than Sense ROMs. I would love to be able to flash something over CM7 to increase bluetooth reliability, even if it hurts battery life (you could always turn bluetooth off when you need to save battery).
Shidell said:
I've created an update package from CM6.0.0 RC1 with (what I believe to be) all the pertinent Bluetooth files. This will replace your current files when you run this update script.
I'm going to test this using a CM7 nightly, and wholly expect this to fail. This may actually work with CM6, however, but I'm testing CM7 first.
If anyone else tests this, please let me know your results.
Also, if anyone is more tuned in as to what needs to be done/fixed, please let me know that as well. I'm basically treading water in the middle of the pacific, hoping I find an island.
Click to expand...
Click to collapse
ill try this as i have the cutting out issue as well
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
allroy1975 said:
When I've had problems with audio dropping in and out,it's because my wifi is on at the same time.
You can't have wifi and do a2dp at the same time. I've seen that around,so I think it's a known bug.
The whole reason I switched to cm was because the bitpool is set too low in all the sense roms. From my understanding, it should be set to something in the 50s or 60s (sorry, I haven't looked @ it in a few weeks) and sense roms have it set in the 30s resulting in a lot of high frequency distortion or clipping.
I'm not sure if that's helpful. ..but I wrote some stuff.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
my wifi is never on. and even when it is it doesnt do it on sense roms.
zikronix said:
my wifi is never on. and even when it is it doesnt do it on sense roms.
Click to expand...
Click to collapse
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
BuddaBelly said:
Yeah my wifi is not on when Im riding my bike. I do agree sence has a pretty crappy bluetooth stack but the early CM releases were amazing. I could ride even on a open road with no trees to bounce signals of off and never get a signal drop.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, wouldn't it be easier to look back into the git commits for the CM repository. And see what changed in the bluetooth files after 6.0.0? That way you should be able to drop in the older bluetooth stuff, and have it work. Then you can try to convert that stuff to work in CM7?
timwoj said:
It works fine for other Bluetooth profiles (phonebook, etc) but it doesn't provide a PAN service at all. I haven't tried with the new AWT, but I don't hold much hope.
Click to expand...
Click to collapse
If you use AWT and set it to Bluetooth mode and then turn it on, the PAN service will magically be created, but only while tethering is turned on. However, I still wasn't able to get Bluetooth tether to work because of some kind of IP address error in AWT. I think AWT wasn't able to set an IP address for the Bluetooth PAN adapter. My computer was able to see the Bluetooth PAN but wasn't able to pull an IP address to fully complete the connection.

gps not working

I am rooted and unlocked. Using tiamat 1.4.1.
I can not aquire a GPS signal anywhere inside or out. I do have GPS turned on. I can hold my EVO right next to the Xoom and the EVO receives a GPS signal perfectly. Are there some settings I am missing?
is there a system GPS.apk that I can push or anything?
I had the same thing happen when I tried the tiamat 1.4.1 kernel too. I ended up returning the Xoom and getting a new one lol. This time I only rooted it and gps works fine.
really? So its a tiamat kernel thing? I will post the question in the DEV forum and see what they think. Thanks for the reply.
I noticed the post in the DEV forum and unfortunately (due to my post count below 10 was not able to answer). I mostly provide support through the freenode #xoom channel where I am sure we will be able to resolve your issue. Most likely, a module is missing. (modules are what make various components work such as wifi, bluetooth, and gps) I can confirm that GPS is working on my wifi xoom running any and every version of tiamat including 1.4.1.
I'm having sorta the same issue. My GPS couldn't find signal b4 I updated to 3.1 and now also after having 3.1.
Sent from my Xoom using XDA Premium App

Xoom ICS & Cisco Access Points

This thread is only for people running a Cisco Access point, preferably a Aironet 1200.
I currently have the 3g/4g version, and this behavior seems exist on all ICS builds I've tried.
I started a thread on Motorola's forums here.
I have 35/35 at home, and on pre-ics builds I get about 25/25 on my xoom. With ICS builds however my download is about 400kb-1200mbits. With upload being 25mbits. So it seems to only be on the downlink where the issues exist.
I've tried building it from source, I've tried other roms, everything that is ICS is slow download which makes streaming terrible.
My Nexus S running ICS does not have this issue so it seems something specific to ICS and the XOOM.
Anyone running the same sort of equipment as me, and running into the same problem?
Thanks
I got a Xoom on stock ics, and I have a bunch of aironet 1231g and 1242ag aps at work. I could try some stuff out if I knew what you meant by the 35/35 or 25/25 stuff, I probably wouldn't want to change my xoom that much with roms or anything (I just rebuilt it tonight to see if it fixed some slowness I was seeing after the ota to ics) but could test on stock ics, just tell me how your testing it... if it makes a difference the aps are all light weight aps managed by WLCs. I could probably snag a 1242 ( and maybe a 1231 if I can find a spare one) and dumb it down with autonomous image if that is more how you are rolling, but it might take me a couple of days...
Sent from my SPH-D700 using XDA App
I'm running
Cisco IOS Software, C1250 Software (C1250-K9W7-M), Version 12.4(25d)JA, RELEASE SOFTWARE (fc1)
What I mean by 35/35 is thats what my internet is at home. But any speed test will show the issue if it is a cisco issue. You'll see that download is terrible, and upload is normal.
Im still not sure what 35/35 means, i've never seen any metrics for throughput / network performance displayed this way...
Sent from my SPH-D700 using XDA App
35mbits over 35mbits.
I have a symetrical fiber connection that gives me somewhere between 35-45mbit download, and 35-40mbit upload.
We found a solution on the other thread. It appears that the new broadcom drivers are now 802.11 certified and there appears the be a bug that causes 802.11 draft APs achieve data decent data rates.
So here are the 3 fixes.
1. Buy a new AP
2. Disable you're mcs rates and lose 802.11n
3. Pray that motorola fixes it.
I'm currently running with 2. Shopping around with 1. Oh and have no doubt in my mind that 3 is a pipe dream.

[Q] Is there an ICS Rom with a solid working WiFi Tether connection?

I am looking for an ICS rom that has a solid working Wifi-Tether program/connection/solution?
I'm a sys admin and like to work remotely...sometimes in places where there is no net connectivity.
If anybody has a suggestion for me...I am greatly appreciative!!
Even if its not ICS, I am open to downgrade until they hopefully sort it out with CM9.
Thanks everybody!
On any ICS ROM:
1) Download Barnacle and Wifi Tether for Root Users.
2) Open Barnacle, check "skip wpa supplicant" in settings, run it, then turn it off once it's closed.
3) Run Wifi Tether and connect your device to your phone.
Sent from Spaceball One.
Thanks...I understand about barnacle and skipping the wpa supplicant...but what do I do after that, because I still cannot get it to work properly??
not sure but I think VirtuousRom's primadonna might do; they say it's alpha but I use it as a daily driver and only have to reboot once a day ;-)
The latest cyanogenmod9 alpha5 by tbalden & korneyone now natively supports the wifi tethering. I've been using it for several months and the bugs are almost non-existent (certainly unnoticeable to the majority). I think the only one that most people would notice is the lack of 1080p support (but 720p still works perfectly)! There's a few others out there, but they are mainly only in the more obscure features.
Sent from my Transformer TF101 using Tapatalk 2
crucialdnb said:
Thanks...I understand about barnacle and skipping the wpa supplicant...but what do I do after that, because I still cannot get it to work properly??
Click to expand...
Click to collapse
Read my instructions again. Completely.
Sent from Spaceball One.

[Q] Is there a quick fix for sms delivery report stuck in status pending?

Rom: CM7.2. kernel: faux123-050 - baseband mar12.
My sms delivery reports gets stuck in pending on all data options. However, the reports send when using wifi calling... . Is there a quick fix to this like changing the apn setting or changing kernels?
Edited for brain fart
Sent via G2x on CM7 b135.1 w/faux 52 kernel
stej16 said:
I've did a bunch of searching with no definitive answer... I'm running cm7.2 kernel faux123-050 - baseband mar12. My sms delivery reports gets stuck in pending unless it's on wifi calling, then it works(sms sends successfully). Is there a quick fix to this like changing the apn setting or changing kernels?
Click to expand...
Click to collapse
I've never come across this before. I know that for me, WiFi Calling is the death knell for texting (SMS or otherwise). It's got me bothered because my phone is only functional due to WiFi Calling for where I live. If I come across anything I'll pass it along, but possibly doing a logcat when you're not able to have them reports send might help resolve the issue.
New2my8125 said:
I've never come across this before. I know that for me, WiFi Calling is the death knell for texting (SMS or otherwise). It's got me bothered because my phone is only functional due to WiFi Calling for where I live. If I come across anything I'll pass it along, but possibly doing a logcat when you're not able to have them reports send might help resolve the issue.
Click to expand...
Click to collapse
Thanks. I'll do a logcat. It's not that big of a deal, I'm just being anal and thought there might be a quick fix for such a small problem.
My WiFi calling works flawlessly ... did you try a bunch of different roms and kernels?
stej16 said:
Thanks. I'll do a logcat. It's not that big of a deal, I'm just being anal and thought there might be a quick fix for such a small problem.
My WiFi calling works flawlessly ... did you try a bunch of different roms and kernels?
Click to expand...
Click to collapse
I've been running Modified ROM's on my phone ever since I got it back in Aug. of 2011. Stock just sucked (was the 2.3.3 GB Stock). I've tried just about them all. Hell's GB and ICS ROMs, Euroskank's GB and ICS ROMs, TonyP's ICS/JB ROMs, etc, etc, etc. I'm surprised my onboard flash chip is still working with all the flashing I've done over the 14+ months. Currently using Temasek's GB Build 135.1 Final. The phone for the most part works, and works well. I've tried all the kernels too ranging from Faux's, to Morfic's, to Harsh's. Morfic's ELP Kernel has been the most solid for me.
I don't use ICS ROMs because their WiFi Calling is borked beyond all recognition. I just hope and pray that IF we get an official release of ICS for our phone, it fixes the WiFi woes I've had with ICS ROMs. I'm too dependent on WiFi for my cell network connection. If only T-Mobile had a Microcell for their network. They have that repeater cell tech, but it requires a 3g/4g connection, and my house doesn't even get a 2g connection outside (although their map "claims" I am to have 2g service). It's just frustrating.
I saw an article about AT&T's Microcell back in 2010, and was hopeful the technology would catch on, but it flopped.

Categories

Resources