Database Users

Nexus one Wifi

I just want to know has anyone had any problems with the wifi? and wep/wpa? ive heard some complaints about this and i jus want to see how common it is

I use mine on a wep and wpa network everyday with no problems at all.

I use wep at home and wpa at work, no problems.

no problems so far...

galaxys said:
no problems so far...
Click to expand...
Click to collapse
mines also good too.

Wifi on mine is 100% broken. Trying to turn it on makes the phone freeze and then reboot.
Phone arrived yesterday. Wifi never worked a single time, out of the box. Details / video below:
http://forum.xda-developers.com/showthread.php?t=618764
Buyer beware.

Ok thanks guys, it seems only a few are broken, fingers crossed I guess.

Paul has another, much larger post about this up here somewhere that you can probably pitch into.
I read that rebooting 4-5 times worked for someone. :shrug:

kozm0naut said:
Paul has another, much larger post about this up here somewhere that you can probably pitch into.
I read that rebooting 4-5 times worked for someone. :shrug:
Click to expand...
Click to collapse
To be fair, I've searched and searched and searched on here, Google's support forums, Google itself, etc, and have not yet found a single other person with broken wifi like on mine.
So I guess I'm 1 in 20,000, sigh.
Either way, I would caution against purchasing the device until the 3G/Edge switching problems have been fixed. I didn't care about those issues, because I thought I'd always be on wifi. Heh, boy was I wrong...

Thanks paul, I do suggest sending it back by the way

No Wifi problems here either WEP or WPA (no 3G/Edge issues either)

WPA works fine here, but doesn't always re-connect automatically after an incoming phone call. Sometimes need to force a re-scan when I'm at the far edges of the range.

[Solved]Wlan problem - loosing connection alot

Anyone else experiencing problems with the Wlan? Everyday I have to shut down Wifi, and start Wifi again to reconnect to my router. This mostly happens after the phone has been unused for a few minutes.
When I start using the phone again, it still says i´m connected, I still have the IP, and the signalbar. But when trying to use the internet there is no connection.
My X10, asus lamborghini, hp laptop and desktop pc works flawlessly, so there cant be anything wrong with the router.
Would like to confirm that this is a general problem, and not just my phone...

I didn't have this problem until I played with the WiFi sleep policy. I switched it from 'Never' to 'Sleep when screen is off' and I then got the problem you described. I have since switched my phone back to 'Never' and the problem has gone away.

Andrew Phillips said:
I didn't have this problem until I played with the WiFi sleep policy. I switched it from 'Never' to 'Sleep when screen is off' and I then got the problem you described. I have since switched my phone back to 'Never' and the problem has gone away.
Click to expand...
Click to collapse
Yeah, I have mine set to never also. Still have the same problem.

Just added a videon on youtube to show how it keeps disconnecting itself, and how I restore connection.
http://www.youtube.com/watch?v=sL-1aAQWPu0

I've got the same problem with my phone, its really annoying

There are three threads and one poll dedicated to Wi-Fi. There was no definitive answer in those threads so I doubt there will be one in this thread. Do a search.

Same problem here, not sure if it's down to running a customer rom, anyone having this problem on stock rom?

Yes I've had this problem and tried to send my phone back over it.
It appears to be a problem with WPA1 - the wifi driver hangs and the phone kills it (from adb logcat).
It happened on my home wifi - I switched it to WPA2 and it went away; however, my employer uses 802.1X and I have to use HSPDA at work as wifi keeps crashing.

Please god, not another ten pages of the same questions, theories, and debates. Here's the original Wi-Fi thread, continue your musings here:
http://forum.xda-developers.com/showthread.php?t=1067473

Finally solved the WLAN problem! It seems the Belkin N+ router is not fully compatible with the Galaxy S2. Bought the Asus RT-N56U router a few days ago, and the Wlan - Wifi connection to the phone has worked flawlessly since then!
So now you know!

BarryH_GEG said:
Please god, not another ten pages of the same questions, theories, and debates. Here's the original Wi-Fi thread, continue your musings here:
http://forum.xda-developers.com/showthread.php?t=1067473
Click to expand...
Click to collapse
Yup noobs shouldn't be able to make threads...only replies on posts for a at least a year. Saves a lot of junk. Plus we get a variety of useful threads page after page.
Sent from my GT-I9100 using XDA App

corb06 said:
Finally solved the WLAN problem! It seems the Belkin N+ router is not fully compatible with the Galaxy S2. Bought the Asus RT-N56U router a few days ago, and the Wlan - Wifi connection to the phone has worked flawlessly since then!
So now you know!
Click to expand...
Click to collapse
Already discussed. Next time make use of the search button before making new topic please.
Sent from my GT-I9100 using XDA App

Get off your high horses. I found a solution in this 'noob' thread that I did not find in the pages of waffle on the main thread.
It may have cost me £100 but it is a solution which is what some of us pragmatic types want. The rest of the high and mighty around here can cast around for an understanding of the underlying issue but some just want to get things to work and get on with our lives. Both attitudes are valid and one camp should not set themselves as more 'worthy' than the other.
A sense of superiority is seldom founded on anything useful.
"Up here for thinking, down there for dancing."

C2k6 said:
Get off your high horses. I found a solution in this 'noob' thread that I did not find in the pages of waffle on the main thread.
It may have cost me £100 but it is a solution which is what some of us pragmatic types want. The rest of the high and mighty around here can cast around for an understanding of the underlying issue but some just want to get things to work and get on with our lives. Both attitudes are valid and one camp should not set themselves as more 'worthy' than the other.
A sense of superiority is seldom founded on anything useful.
"Up here for thinking, down there for dancing."
Click to expand...
Click to collapse
At least give us thread link then close this thread . I am not finding the particular NOOB thread

Xoom 3.2 and Bluetooth Tethering...

Affter the update to 3.2 on the Wifi model, some people have reported issues with Bluetooth tethering and some have not. It seems that both people are right. It works once, but then after you disconnect, then it will not work again until you restart your Xoom.
There might be other ways around restarting, but so far that has worked every time that I have tried it. Which is annoying since it does take a while to restart. I just go ahead and restart when I have time, and then it is ready to go when I need to enable the connection.
Hopefully this is a minor issue that Google will resolve in 3.2.1
I am currently running stock 3.2 on a wi-fi only Xoom.
-Matt

i have the same issue and its pretty annoying ......hopefully someone can help with an easy work around

I have never been able to bluetooth tether to my Samsung Vibrant. I can connect but tapping on the wrench icon doesn't bring up anything but UnPair.

1+
Sent from my Xoom using XDA Premium App

bt tether does not work from nexus s 4g either...

Matt112211 said:
Affter the update to 3.2 on the Wifi model, ... Bluetooth tethering ... works once, but then after you disconnect, then it will not work again until you restart your Xoom.
Click to expand...
Click to collapse
Same problem with my Defy running CM7. Sucks!
At least we know a reboot will allow us to get back online

+1 tethering to n900

MY Turtle Beach PX5s work just fine on my Xoom via Bluetooth. I can hear music and listen to Netflix just fine.

+1 htc hero, worked before 3.2 now only works on first boot of xoom

Matt112211 said:
It works once, but then after you disconnect, then it will not work again until you restart your Xoom.
Click to expand...
Click to collapse
This is definitely an issue with 3.2.
I started working on it yesterday with Solarnz and BRD. More info to come soon.

Nice one was talking to brd about it earlier but good to know its already being looked at
Sent from my Xoom using Tapatalk

Still no BT working for me.
C_K

OK, since nothing is happening anymore here, I'll get that thread up again.
This issue really sucks, so I tried different things to get it fixed...
What I know: It seems to be a dhcp-problem. If you are rooted and type "netcfg" in a terminal, you'll see that the interface "bnep0" (that's the one for bluetooth-tethering) will only get an IP-address and a subnet-mask on the first connect.
After reconnecting the IP keeps stuck at 0.0.0.0/0. Anyway, it seems that it gets an IPV6-address!?
By typing "su dhcpcd" you sometimes can get a valid IP for bnep0 and a working tethering, but that's not sure... Sometimes you'll get an IP, but the subnet is stuck at 0.
At first I thought it was a bug with the dhcp-deamon, so I pulled /system/bin/dhcpcd out of a 3.1 ROM and pushed it to my 3.2 ROM. Unfortunately there was no difference...
My new ideas are:
1) Maybe it could be possible to define a static configuration for bnep0. My problem is that I don't find the proper config-files. Surely someone can tell me. This way we could maybe work around a dhcp-issue (if it is).
2) Maybe it could(!) also be something with IPV6... It could help to deactivate IPV6, but here it's the same, I don't know how.
Maybe you guys have more ideas! This issue really, really sucks and I am sure we can at least find a workaround! Rebooting can't be the solution.

McDV said:
Maybe you guys have more ideas! This issue really, really sucks and I am sure we can at least find a workaround! Rebooting can't be the solution.
Click to expand...
Click to collapse
Where I last left off, I found that dhcpcd was still running after terminating the initial successful Bluetooth tether. Pre-3.2, both kbnepd and dhcpcd would be stopped.
Killing dhcpcd before attempting a re-tether may be an interim solution. On my device (MZ604 Wi-Fi, 3.2 stock, rooted), if I killed the orphaned dhcpcd process, I could re-tether successfully without a reboot. Savvy users with root, please try this on your device and let me know your feedback:
From a fresh boot, initiate a successful Bluetooth tether
Before terminating the tether, bring up a terminal/adb shell
Run ps, note the kbnepd and dhcpcd processes and their pid's
Terminate the tether
In the terminal/adb shell, run ps again
Note the absence of kbnepd, but dhcpcd still running (same pid as before)
kill dhcpcd
Try re-tethering via Bluetooth
I compared getprop during a successful tether with that after terminating the tether to see if there was a property change which we could use as an init trigger for a hack (kill dhcpcd when x = y), but there was no change. kbnepd doesn't even show on getprop, unfortunately, at least on my device.
Note also that the 3.2 update patches dhcpcd (brd also pointed out changes to ramdisk [init.stingray.rc] regarding dhcpcd) and libnetutils. Comparing logcats between 3.1 and 3.2 and digging through pre-Honeycomb source code gives some indicators that the bug might be in libnetutils. Time wasn't very permitting for me to continue following up on it this week, however.
Until we find a better solution, I was considering putting together a quick and dirty 1x1 widget which rooted users could tap to manually kill dhcpcd before re-tethering. I'll await feedback first on whether manually killing dhcpcd (steps above) works for others. So lemme know.

I've tried it, with no result.
For me there isn't the problem that dhcpcd isn't terminated. Anyway, I've tried to "su kill dhcpcd", but it doesn't help at all...
The idea with libnetutils.so sound good. So I've tried to replace it with the one from 3.1. Unfortunately it ended up in bootloops. Maybe someone could try to fix libnetutils.so

Does s.o. know, if it would be possible, to port the DHCP-client from 3.1 to 3.2? Maybe it would be sufficient to just copy mor than only /system/bin/dhcpcd or libnetutils.so. But I don't know which files need to be copied to not end up into bootloops.
For the moment I downgraded to 3.1, but that's not really satisfying...

No fixes, workarounds or other solutions by now? OK, looks like I'll have to stay at 3.1 'till Ice Cream Sandwich. ;-)

Same issue here, very irritating!

Anyway, it seems that we, who want to use bluetooth-tethering, are a minority, so no one really cares. Neither Google, nore the devs here. ;-) Not even the Tiamat-Team seems to care.
Maybe we'll have to wait until Ice Cream Sandwich is released or maybe there is a 3.2.1 or 3.3 update...
I think it would be possible to port the DHCP-client from 3.1 to 3.2 to solve the problem, but I don't know how.
So the only workaround is using 3.1 - optionally with Tiamat 1.4.4 kernel, because Tiamat 2.1 doesn't work with 3.1 anymore.

Maybe add a comment and star here:
http://code.google.com/p/android/issues/detail?id=18835

Wifi connected but doesnt work.

We have 3 SGS2 at home and a Billion 7800N modem
There is a recurring problem on my wifes phone where there is no dataflow. I cant even reach the modem. It will just start working all the sudden for a short period then stop again.
Things I have tried.
1. Using it right next to the router
2. have tried using different channel
3. have reset modem
4. made sure sleep policy is on never
5. Update firmware and hard reset phone - no new apps installed - worked at first but now having problems again.
It never loses wifi connectivity....internet just does not work. Turn 3g on...works fine.
What could be the problem?
Only things I can think of
1. Faulty phone
2. Virus? That phone is sometimes used to check out Chinese websites...and I know some of them can be dodgy. I forgot to ask her not to go to any of those sites after the hard reset as trial and error.
3. Not certain but this problem may only started when we updated to 2.3.4.
If need be Ill hard reset AGAIN when XXKG6 is out - I dont want to flash back to 2.3.3 to try

auswill2 said:
What could be the problem?
Click to expand...
Click to collapse
I have the impression, that the Broadcom WiFi drivers of Android are still buggy, because my Asus Transformer's WiFi also isn't very good.
When using a static IP address and setting Google's free DNS 8.8.8.8 as a secondary DNS server (the router as primary), my SGS2's WiFi works best.
Maybe give it a try.

I have the exact setup and tried all the things you mentioned to no avail. It works sporadically after I reset the phone wifi on and off but it won't maintain data connection for long. Although the signal indicator says it is still connected. the billion 7800 works on my wifes sgs and connects without problem to my work htc legend.
Sent from my GT-I9100 using XDA App

If you google for "galaxy s2 wifi no internet", you'll find out, that several SGS2 owners have exactly the same problem.
I all cases it seems to be the router's firmware, that causes this problem. I found two users reporting, that the only solution was to download a new firmware from ...
http://dd-wrt.com
But maybe it helps to drop the speed from 802.11 N to G?

I have the exact same problem and my firmwire on my router is the latest. What I do to fix this problem is just unplug my router and plug it back in. I find that fixes it for me. Post back if that doesn't work
Sent from my Nexus S using XDA App

isinisterx said:
... firmwire on my router is the latest.
Click to expand...
Click to collapse
That's why two guys reported, that they had to download a new FW from DD-WRT, which solved the problem for them.
Sorry, that I don't post links ... it were german forums.

I have the exact same problem. You say that the other two S2's work perfectly? If that's the case then it must be a hardware fault. I'm gonna take mine to be fixed or replaced.

steviewonders said:
If that's the case then it must be a hardware fault.
Click to expand...
Click to collapse
Likely ... maybe different firmware?

Yes....my SGS2 and my brothers work fine. When I update....I update all 3 so we are all using the same firmware.
Thats why I believe its a problem specific to 1 phone....not the router (although I did update my router to latest firmware just in case.....same problem)
As a side note - my brother has a microphone echo problem when using a specific gel case. When my wife and I use the exact same case - no problem. I dont know how Samsung build their phones - but its not very consistent.

auswill2 said:
Thats why I believe its a problem specific to 1 phone...
Click to expand...
Click to collapse
Shure ... in this case THIS phone has a hardware defect.
I dont know how Samsung build their phones - but its not very consistent.
Click to expand...
Click to collapse
That's why we have a thread about the "Made in ..."
But that's not only a Samsung problem ... I know that from the Asus Transformer forum.

Ill see where our phones are made if I have time. If anything though, my brother should be the odd 1 out as his was bought in Australia whereas I got the other 2 from UK.
Ill get to the bottom of this....even if I have to keep doing hard reset and trial and error tests. Not being able to use wifi is a huge deal.

Just to confirm, the problem's not only apparent in 2.3.4. My phone has the same problem with 2.3.3. I've sent my phone in for repair now so i'll post my findings here in a week or so. Have you got any further with it?

I sure hope they do fix it somehow....It's becoming increasingly annoying having to flick wifi on and off, downloading apps is the worst. This never happened on mine or my girlfriends htc's.

Anyone able to find a solution for this problem? Just picked up my Galaxy S2 and have the exact same issue Wifi connects, surf the net for about 10 sec, then nothing.. still connected to Wifi and everything.
At work at the moment so can't really play around with the router settings but will try once I get home. Have been looking forward to getting this phone for a while now and to have Wifi issues right off the bat is quite disappointing..

wifi connected no data flow
i had the same problem
i tried different ways no sucess
i tried Set DNS Pro from market
tried different settings
applied different dns
shift from open , custom to google ang keep checking the internet in browser
after few try it works everytime
its to do with assigning ip address in android
thanks

I posted a solution a few weeks back....but i think most people overlooked it....so the solution is
Go to settings>>>>wireless and networks>>>>>wifi settings>>>>hit menu and go to advanced>>>>regulatory domain>>>>change the channel to 14.....thts it....it worked for me on vibrant,nexus one and even on sgs2..hope this helps
Sent from my GT-I9100 using XDA App

zainqaiser said:
change the channel to 14
Click to expand...
Click to collapse
Channel 14 is not allowed in most countries ... my german router e.g. doesn't have channel 14, only 1-13.
I had similar issues with my Asus Transformer and found out, that a static IP works best, BUT only if a secondary DNS is assigned too. I used Google's 8.8.8.8
Give it a try. The Broadcom drivers seem to have a bug, when no secondary DNS is assigned.

The "regulatory domain" setting isn't there on my galaxy s2 ;/ Will give the static IP solution a try.

zainqaiser said:
I posted a solution a few weeks back....but i think most people overlooked it....so the solution is
Go to settings>>>>wireless and networks>>>>>wifi settings>>>>hit menu and go to advanced>>>>regulatory domain>>>>change the channel to 14.....thts it....it worked for me on vibrant,nexus one and even on sgs2..hope this helps
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thx mate ..... this worked for me

I have the same problem currently on 2.3.4 (KH3) and I also had it on 2.3.3 (KF3).
I currently can't find the Regulatory Domain setting.

WiFi Issue

Flashed 3-669-SuperScaryStable on top of nightly cm7 212. Subsequently, WiFi could not maintain a lock. The phone would find the wifi network get a lock for a moment and immediately lose the lock. Get a lock, lose the lock. . . . Settings I tried were Scary and smartass governors 245mhz - 1.2ghz
Anyway, flashed nightly 220 (back to regular cm7 kernel)-- back to wifi working fine.
Maybe I looked too quickly but all I saw in the development thread pertained to Super Scary not working with sense roms.
Hmmmm.

sdk234 said:
Flashed 3-669-SuperScaryStable on top of nightly cm7 212. Subsequently, WiFi could not maintain a lock. The phone would find the wifi network get a lock for a moment and immediately lose the lock. Get a lock, lose the lock. . . . Settings I tried were Scary and smartass governors 245mhz - 1.2ghz
Anyway, flashed nightly 220 (back to regular cm7 kernel)-- back to wifi working fine.
Maybe I looked too quickly but all I saw in the development thread pertained to Super Scary not working with sense roms.
Hmmmm.
Click to expand...
Click to collapse
Download wifi analyzer from market and figure out what is conflicting with your wireless router.
toastcfh's stock kernel is considered the most stable kernel because it's been tested and proven to work with everything time and time again.
However, I have no problems with wifi on Scary's kernel. Again, I'm not saying there are no issues because when I'm at work I do have issues but I have wifi issues on my laptop with the wifi here as well, they have way too many APs broadcasting on the same channel (4-5 APs for channel 3, 4-5 APs for channel 7, 4-5 APs for channel 11) so I seriously doubt it's a problem with the kernel but more a problem with your local wifi router configuration.
Run wifi analyzer and it will answer this question.

Am I right to assume that I should run the test you recommend after flashing Scary and recreating the problem - cause on Toastcfh's kernel there is no problem connecting to that router whatsoever?

sdk234 said:
Am I right to assume that I should run the test you recommend after flashing Scary and recreating the problem - cause on Toastcfh's kernel there is no problem connecting to that router whatsoever?
Click to expand...
Click to collapse
You can run the same test on toast's kernel.

Well, you know, maybe it's just all about the goofy phone itself after all.
Trying to do the test (following a reboot) I'm just about sitting on top of the router (that I've confirmed is working) with wifi enabled on the shift and all I'm getting is "not in range." Can't get the wifi icon to even display at the moment.
Thanks for the help.

sdk234 said:
Well, you know, maybe it's just all about the goofy phone itself after all.
Trying to do the test (following a reboot) I'm just about sitting on top of the router (that I've confirmed is working) with wifi enabled on the shift and all I'm getting is "not in range." Can't get the wifi icon to even display at the moment.
Thanks for the help.
Click to expand...
Click to collapse
Open ROM manager and run fix permissions and reboot again, then turn on wifi and open wifi analyzer again.

VICODAN said:
Open ROM manager and run fix permissions and reboot again, then turn on wifi and open wifi analyzer again.
Click to expand...
Click to collapse
Did it. But seems that I've got the same problem. Connects for a little bit and then disconnects. It just can't maintain the wifi link. Doesn't stay up long enough to even get a screen shot of wifi analyzer.
Maybe I should try another nightly, stable cm7 or sense?

sdk234 said:
Did it. But seems that I've got the same problem. Connects for a little bit and then disconnects. It just can't maintain the wifi link. Doesn't stay up long enough to even get a screen shot of wifi analyzer.
Maybe I should try another nightly, stable cm7 or sense?
Click to expand...
Click to collapse
You can't take screenshots on wifi analyzer. Just analyze it yourself. How many APs are broadcasting on the same channel as you? More than 1? Change the channel.

There are two and they don't overlap. One is centered over channel 6, the other (weaker one) centered over channel 11. But the problem is that the parabolas that show the signal strength disappear pretty quickly and the wifi indicator at the top of the phone just disappears. What do you think about the possibility that I should switch to a different nightly or sense?

sdk234 said:
There are two and they don't overlap. One is centered over channel 6, the other (weaker one) centered over channel 11. But the problem is that the parabolas that show the signal strength disappear pretty quickly and the wifi indicator at the top of the phone just disappears. What do you think about the possibility that I should switch to a different nightly or sense?
Click to expand...
Click to collapse
Ignore the APs disappearing. It sounds like your router is either a piece of junk or misconfigured.
Try configuring the wireless radio on channel 1.

Shouldn't be a piece of junk. wasn't that cheap ;-)
Works fine with my computer anyway.

sdk234 said:
Shouldn't be a piece of junk. wasn't that cheap ;-)
Works fine with my computer anyway.
Click to expand...
Click to collapse
That means nothing.
What kind of router is it? Manufacturer / Model number?
Also please remove ScaryKernel from the title of this thread since we have proven this problem happens on toastcfh's kernel as well.

VICODAN said:
That means nothing.
What kind of router is it? Manufacturer / Model number?
Also please remove ScaryKernel from the title of this thread since we have proven this problem happens on toastcfh's kernel as well.
Click to expand...
Click to collapse
Netgear N600 WNDR3400
Why's it meaningless that I have no trouble with WIFI on laptop?

sdk234 said:
Netgear N600 WNDR3400
Why's it meaningless that I have no trouble with WIFI on laptop?
Click to expand...
Click to collapse
Netgear sucks. Do yourself a favor and go buy a Linksys WRT610N or one of the new models.
Other than that all I can tell you is switch your wireless channel.
It's not a problem with the phone or the kernel, it's the router.

VICODAN said:
Netgear sucks. Do yourself a favor and go buy a Linksys WRT610N or one of the new models.
Other than that all I can tell you is switch your wireless channel.
It's not a problem with the phone or the kernel, it's the router.
Click to expand...
Click to collapse
Ok - I'll try switching the channel first ;-)
Also - going to find some other routers to test the phone against
Thanks for all the time spent troubleshooting here

Ok - Vic - here's the end of the story, since you've been good enough to work with me on this - -
Installed and ran an app called "FXR WiFi fix and rescue" from the market. Didn't appear to help.
So, restored nandroid of Mik 1.6 and WIFI WORKS PERFECTLY once again. Strong, stable, consistent lock on the Netgear signal (and another close-by router as well.) Problem solved for me.
Not going to make any rash accusations about what the culprit may be which caused wifi to fail for me on cm7.
I'm happy I've confirmed it's not the phone.
Maybe my shift just likes MikRoms and Supreme Sense and was punishing me for experimenting!!

sdk234 said:
Ok - Vic - here's the end of the story, since you've been good enough to work with me on this - -
Installed and ran an app called "FXR WiFi fix and rescue" from the market. Didn't appear to help.
So, restored nandroid of Mik 1.6 and WIFI WORKS PERFECTLY once again. Strong, stable, consistent lock on the Netgear signal (and another close-by router as well.) Problem solved for me.
Not going to make any rash accusations about what the culprit may be which caused wifi to fail for me on cm7.
I'm happy I've confirmed it's not the phone.
Maybe my shift just likes MikRoms and Supreme Sense and was punishing me for experimenting!!
Click to expand...
Click to collapse
Glad to hear it but I'm still wondering.. did you even TRY changing the channel?
I get 20+Mbps over Wifi on 2.4ghz.

I was planning to try changing the channel, but you know what -- just happened to restore Mik 1.6 first.
And the result was dramatic. On the nightly CM7 the graphs displayed on wifi analyzer weren't stable at all. Even when the parabola's appeared for a few moments, their height was shifting up and down. It was like the signal strength was fluctuating.
On Mik's rom the height of the parabolas is higher than I saw before and just stays put.

sdk234 said:
I was planning to try changing the channel, but you know what -- just happened to restore Mik 1.6 first.
And the result was dramatic. On the nightly CM7 the graphs displayed on wifi analyzer weren't stable at all. Even when the parabola's appeared for a few moments, their height was shifting up and down. It was like the signal strength was fluctuating.
On Mik's rom the height of the parabolas is higher than I saw before and just stays put.
Click to expand...
Click to collapse
Did you do a wipe data/factory reset when flashing CM7? Did you wipe dalvik? Did you wipe cache? Did you wipe battery stats? Did you flash the latest CM7 nightly and then right after that did you flash google apps 828 and new talk?
Not wiping properly before flashing a new rom could cause weird issues like that.

VICODAN said:
Did you do a wipe data/factory reset when flashing CM7? Did you wipe dalvik? Did you wipe cache? Did you wipe battery stats? Did you flash the latest CM7 nightly and then right after that did you flash google apps 828 and new talk?
Not wiping properly before flashing a new rom could cause weird issues like that.
Click to expand...
Click to collapse
Yes-wiped that & more - prboy trained me well
After wiping according to steps on mik's forum (& battery stats) , flashed cm7 and google apps and talk just as you instructed
Sent from my PG06100 using xda premium