Database Users

Has anyone noticed Google took off the wireless "n"

Before, you would go to http://www.google.com/phone/static/en_US-nexusone_tech_specs.html and it would show wireless b/g/n now, it only shows b/g. So what gives? Does it have it or not?

Very interesting find. I do remember seeing n

Yea, I remember HTC never listed it as having "n" but Google did. And it seems the Desire doesn't have it either...hmmm

It has and "n" WiFi radio, but there is some sort of cap/limit to save battery. There are several threads where members on here have run the tests and measured "n" speed data transfer using their N1, but IIRC they were running a CM rom, which is built from AOSP, and wouldn't have a limit like that in it.
The HD2 is in the same boat, HTC capped data speeds... someone found the registrey entry and edited it to enable full "n" speed, but it kills the battery really, really, really fast.

This is already known. Here are a couple articles if you want to read about it.
Posted January 6th, announcing that the teardown revealed the 802.11n
http://www.engadget.com/2010/01/06/nexus-one-teardown-reveals-possible-802-11n-radio-and-fm-transmi/
"Update: Just noticed that Google does list 802.11n on the specs page although HTC does not."
Posted January 8th, with the realization that the N support was removed from Google's N1 page.
http://www.engadget.com/2010/01/08/google-nexus-one-not-supporting-802-11n-for-the-time-being/

Mi|enko said:
This is already known. Here are a couple articles if you want to read about it.
Posted January 6th, announcing that the teardown revealed the 802.11n
http://www.engadget.com/2010/01/06/nexus-one-teardown-reveals-possible-802-11n-radio-and-fm-transmi/
"Update: Just noticed that Google does list 802.11n on the specs page although HTC does not."
Posted January 8th, with the realization that the N support was removed from Google's N1 page.
http://www.engadget.com/2010/01/08/google-nexus-one-not-supporting-802-11n-for-the-time-being/
Click to expand...
Click to collapse
Whoah! Thanks bro, I check out engadget like every couple hours, I remember seeing that first article, but I guess I missed the second. Thanks for the link!

No problem man. Truth be told, I'm not sure why they removed it, as it's proven to still connect to N networks (on the 2.4Ghz band). I use it on my N dedicated network at home, with a registered 65mbps throughput. Granted, it's not the full N speed, but it's still 11mbps faster than G. lol

Mi|enko said:
No problem man. Truth be told, I'm not sure why they removed it, as it's proven to still connect to N networks (on the 2.4Ghz band). I use it on my N dedicated network at home, with a registered 65mbps throughput. Granted, it's not the full N speed, but it's still 11mbps faster than G. lol
Click to expand...
Click to collapse
I can only dream of what the speed is with N, on G its already wicked fast!

[Q] Wireless Auditing with XOOM

Hi, I am looking at the XOOM for doing some wireless Auditing around work. I was hoping that you would be able to provide some insight on its feasibility...
things on my wish list to find & map are: infrastructure mode AP's, Ad Hoc & polling/active clients.
I have some experience using Kismet on a laptop and it is the kind of functionality i would like.. just would like a more portable form factor for this, it will involve driving around a large campus style location and walking through buildings..
My Questions:
from what i have read, the Broadcom chipset used in these devices do not have a "Monitor" or "RFMON" Mode that would allow it to see all the packets flying by.. I have read a bit in some other forums about some work being done on this, but no recent activity... does anyone know of any current efforts on this?
I have read in previous discussions that the Xoom has problems connecting to a Ad-Hoc mode devices, does it still detect it?
I havent played with the Android war-driving apps too much, are they listening for packets or is it a probe and respond due to the lack of RFMON?
For those with experience, which war-driving apps would you recommend with the pros & cons?
Thanks in advance!

I can't answer most of your questions but I can say that my Xoom does not see my Samsung Epic when I set up wireless tether in Adhoc mode, only when I set it up in Infrastructure mode. It doesn't even see the SSID, but my netbook sees it fine.

I'm a diehard Android fan to say the least I'm an anti-apple but I do keep my options open. I own a few Touch, iPad, SGS Fascinate and Samsung Galaxy tab 2.2 and the Xoom is/was on my list. Last night I spend sometimes with the iPad that I own or should I say my kids owns it, I got IOS 4.3 GM on it to see the improvements. All I can say it's the same, no big changes except for better Apple TV support and browser speed. It's been months since I looked what was available on iTunes for it and to tell you the truth on what I saw was impressive. This has not changed my mind on getting the Xoom or did it? Now on Xoom, I've been reading almost every reviews on the net about it, spend a few hours with it at the local store "BB Bj's etc" and after reading the Ars review, I feel a little bit more hesitant about getting now than 2 days ago! I intend to get the Xoom Wifi only ver but no one knows when it will arrive, and what’s up with Europe getting it first? I have the deepest feeling that in six to ten months Honeycomb support will explode for it but that's in the future. With the release of the iPad 2, anyone getting it will look away from Android tablet for at least a year even if the Android tablet support quadruples. Starting March 11, the road is going to get very bumpy for Android and companies releasing Tablet for it. Just like harsaphes said, I too is on the fence for the Xoom…
Let me know what do you think about the Xoom no fanboys argument…Thanks guys

mjbeam said:
I can't answer most of your questions but I can say that my Xoom does not see my Samsung Epic when I set up wireless tether in Adhoc mode, only when I set it up in Infrastructure mode. It doesn't even see the SSID, but my netbook sees it fine.
Click to expand...
Click to collapse
Have you tried with a wardriving app?

Blaisun said:
Have you tried with a wardriving app?
Click to expand...
Click to collapse
No. I was just in the settings looking for the Epic wireless tether SSID.

Update broke my 802.11n Wi-fi

Anybody else?
Before the update I had my D-Link DAP-2553 wireless access point set for 802.11n only even though my stock, unrooted hardware version 3 Evo would never show connected faster than 65Mbps (WPA2+TKIP), it worked fine.
After the update, it won't even connect unless I set my AP to b, g, & n mixed mode. Then the phone phone will connect but only at 54Mbps.
I've rebooted a few times, disabled fast-boot and even pulled the battery but so far wireless N has been broken for me by the update. Did a "forget" in the wireless settings and even reset my AP to factory defaults and set up everything all over from scratch but still no go.
Any ideas?

limpiador31 said:
Anybody else?
Before the update I had my D-Link DAP-2553 wireless access point set for 802.11n only even though my stock, unrooted hardware version 3 Evo would never show connected faster than 65Mbps (WPA2+TKIP), it worked fine.
After the update, it won't even connect unless I set my AP to b, g, & n mixed mode. Then the phone phone will connect but only at 54Mbps.
I've rebooted a few times, disabled fast-boot and even pulled the battery but so far wireless N has been broken for me by the update. Did a "forget" in the wireless settings and even reset my AP to factory defaults and set up everything all over from scratch but still no go.
Any ideas?
Click to expand...
Click to collapse
limpiador31, feel your pain. I thought this had only happened to me. I tried everything you mentioned with no success on fixin the issue. When I went into settings About Phone, Hardware Information I see that Wi-Fi is listed as 802.11 b/g when before it had n also. Since I'm rooted I nand back and Wi-Fi n is back. Just glad I'm rooted. Not sure why HTC would bork up something like that as that is taking steps backward and definitely not forward with respect to speed.

Thanks for the feedback.
Like you, I was trying too hard to fix the problem and didn't look at the obvious - 802.11n support has been removed from this update.
This is unacceptable and I consider it an unwelcome downgrade as my SpeedTest numbers on wi-fi have gone from about 11-12 down and 5 up to now 5 down and 3 up.
I'm going to do my best to stir up some trouble about this. People have been kind of meh because there's not a lot to see in the new update but for me, this new "feature" of losing half my connection speed jumped out and ate my face.
Everybody is so damned concerned that they can't get their Netflix fix which isn't HTC's problem, but losing a wireless protocol that's been there from the start is HTC's problem and I want it back!
I work in IT and am a geek/tech kinda gal but have strongly resisted rooting just because I know how much of my time I would invest in it but this may be the last straw that pushes me over the cliff.

limpiador31 said:
Thanks for the feedback.
Like you, I was trying too hard to fix the problem and didn't look at the obvious - 802.11n support has been removed from this update.
This is unacceptable and I consider it an unwelcome downgrade as my SpeedTest numbers on wi-fi have gone from about 11-12 down and 5 up to now 5 down and 3 up.
I'm going to do my best to stir up some trouble about this. People have been kind of meh because there's not a lot to see in the new update but for me, this new "feature" of losing half my connection speed jumped out and ate my face.
Everybody is so damned concerned that they can't get their Netflix fix which isn't HTC's problem, but losing a wireless protocol that's been there from the start is HTC's problem and I want it back!
I work in IT and am a geek/tech kinda gal but have strongly resisted rooting just because I know how much of my time I would invest in it but this may be the last straw that pushes me over the cliff.
Click to expand...
Click to collapse
I sent an e-mail to Peter Chou, CEO of HTC, to vent my frustration at his tech team for taking a step backward by removing 802.11N support. I also posted a short note on HTC's facebook page. But HTC is only addressing "kind" posts and not those reporting issues. Go figure. I loved the ROM but I use WIFI at work and 4G the rest of the time except when traveling then I usually am forced to go back to 3G due to spotty coverage.

My wi-fi says 802.11b/g after the update to 2.3.3 as well. Not sure what it said prior to the update to be honest. But before the update the best I could get on SpeedTest when in the same room as my Cisco E4200 was 10.65Mbps down and 3.61Mbps up with a 30ms Ping. Just a couple minutes ago, post-update and in the same room as my E4200, I got 14.01 down and 3.67 up, with a 21ms Ping.
Not really sure if my EVO is now faster on wi-fi, but I don't think the update hurt my wi-fi speeds...
YMMV...

It hurt my speeds on mu wifi. I was usually getting around 20-25 down and mow on getting like 10
if you cant live large, look big in the coffin!!!

After posting this all over the world, someone told me the Evo never supported wireless N so I did a little digging... according to most of the published specs I've reviewed, they only list the b/g standards.
When the Evo first came out with Eclair, even though the hardware had a chip capable of 802.11n, it was crippled by HTC. The great dev's here figured out that by changing a few lines of code, wireless N could be enabled. http://forum.xda-developers.com/showthread.php?t=707218
When Froyo came out, the above wireless G speeds were unlocked in the update making the Eclair hack unnecessary. I'm guessing that due to lack of "antenna diversity" i.e. the Evo only having one wireless antenna that this fell short of the 802.11n standard so they maybe never advertised wireless-N? This would also explain why Evo's could only connect at 65mbps rather than at 150 or 300 like true N should do.
All I know is I use to connect to my A/P which was in N only mode (no mixed b/g/n) at 65mbps. After today's update, my Evo can see my A/P in N only mode but not connect to it. If I set my A/P to mixed b/g/n, my Evo will connect at 54mbps and no higher.
Regardless of the standard or b/g/n letter, my Evo now connects into my network at 11mbps slower than it did before the update.

Wow, that's some bull....!!! Is this the same with 2.3.4?? I am going to try SavagedZen 2.3.4 and see.

Same here
Router shows my EVO only connecting as 802.11g, though other devices successfully connecting to 802.11n at the same time. Settings > About Phone > Hardware Information only shows Wi-Fi: 802.11b/g. Why would they reduce such a key feature?!?
I sent a tweet to @sprint and @htc yesterday, no response yet. I'm trying @sprintcare now.

limpiador31 said:
After posting this all over the world, someone told me the Evo never supported wireless N so I did a little digging... according to most of the published specs I've reviewed, they only list the b/g standards.
When the Evo first came out with Eclair, even though the hardware had a chip capable of 802.11n, it was crippled by HTC. The great dev's here figured out that by changing a few lines of code, wireless N could be enabled. http://forum.xda-developers.com/showthread.php?t=707218
When Froyo came out, the above wireless G speeds were unlocked in the update making the Eclair hack unnecessary. I'm guessing that due to lack of "antenna diversity" i.e. the Evo only having one wireless antenna that this fell short of the 802.11n standard so they maybe never advertised wireless-N? This would also explain why Evo's could only connect at 65mbps rather than at 150 or 300 like true N should do.
All I know is I use to connect to my A/P which was in N only mode (no mixed b/g/n) at 65mbps. After today's update, my Evo can see my A/P in N only mode but not connect to it. If I set my A/P to mixed b/g/n, my Evo will connect at 54mbps and no higher.
Regardless of the standard or b/g/n letter, my Evo now connects into my network at 11mbps slower than it did before the update.
Click to expand...
Click to collapse
Yeah i got slammed by someone in the sprint community saying too may ppl complaing about a feature gone that was never supported by sprint/htc to begin with.
I did some looking and sure enough I couldn't find a single thing that stated the EVO supported wireless N officially from sprint or htc.
What I find real odd is that with the 2.2 update they tweaked the kernel to allow wireless N support in the first place. I am going under the assumption this update was rushed and hence there are some bugs and things lacking in return. I can't see them having a reason to take it out other than they rushed the update. I guess its slightly possible that it coulda borked the kernel or messed with other stuff but I highly doubt that.

I saw the latest kernel modified to fix WiFi n in the dev section under one of the ofical release threads
Sent from my Misfit Speedy Evo using the XDA app

[Q] Antenna issues - deal breaker or just a slight pain in the arse?

About to make the gut churning leap into the chasm of smart phones from the safety of my old nokia dumb'n'easy phone, i have just about settled on purchasing the Razr M due to reasonably hi specs, supposed good build quality and convenient pocket size. But then i came across a lot of posts on various websites, with people saying the antenna(s) are rubbish in this phone, they can't maintain good wifi or cell reception if they hold the phone a certain way and/or suffer from call drops and text message failures when other similar phones have no problems.
Are these just isolated problems on some phones or is it a general design fault? Have motorola done anything to rectify these problems with s/w updates or re-design? And are these problems enough to put me off buying or are they minor flaws in an otherwise good phone? I have been trawling the web for about 10 days now trying to find out these answers and it seems i can't find anything on this subject since early this year.
Any info i can get will be gratefully received i don't want to spend a sh1t ton of cash on a lemon (or an apple for that matter!). Thanks.

I live out in the country and have no issue with reception or wifi... I did a while back but that was due to my router... Even when I'm in areas that no one else has signal (like areas that have the"end of state maintenance" sign)I still manage to get at least 3g
Sent from my XT907 using xda app-developers app

Thanks for that, good to know. I wonder was/is the problem a hardware issue and only on some devices?

Some of the older software versions would disconnect my BT headset when on wifi, but I have not had that issue in the more recent updates.

Moto phones are noted for their radio & audio performance. I see no problems here. Get the X if you want state of the art.

Thanks all for opinions. I pulled the trigger just now. I will update this thread with any info i have after i use it for a while.

Is there anyway to make a WIFI Direct connection on the 5GHZ band?

Hi everyone,
I'm part of a robotics club in my school, and we use wifi direct with 2 phones to communicate between the robot and the remote control. We found that at times there would be a big delay between an input and a response from the robot at competition. We're assuming it has to do with a ton of other teams all using wifi direct at the same time and crowding up the 2.4 GHz band. So we were wondering if there was anyway to use WIFI Direct on the 5 GHZ band with the Nexus 6P or possibly any other phone you know of.
Thx in Advance

Bump... Huge problem at Worlds (lost our first two matches), because between FTC and FRC, there are over 1,000 WiFi devices communicating (or trying to and failing) on just 3 channels!!! Matches were being won and lost on the whims of the team phones' Wifi connections, rather than which teams were actually better. Our team (FTC #10298) is getting two Galaxy S5s for next season and really wants a way to use 5Ghz.

Build jammers and win your match that way. Lol. All jokes aside, I don't think there is a way for wifi direct on 5ghz.
Just came up in my mind. No idea how much dev time you have left, but you could build something to control your drone/device using a cellular connection like 4g?
Googling "drone 4g control github" should help you out.

We are actually in the off-season right now. Unfortunately, we are only allowed to connect via WiFi-direct. However, there are no rules against rooting/custom ROMs, so if there are any ways to force it to use 5GHz through rooting, that would be great.