Ive tried with stock 2.3.6, CM7 and CM6 and although the CM roms improved wifi reception by leaps and bounds, my N1 will still not recognize some very necessary wifi SSIDs, namely the one at work. On my laptop, my old phone (Optimus T), and everyone elses smartphones there is no problem connecting at work. The access point is provided by a Fortiwifi 60c server. fortinet.com/products/fortiwifi/60C.html
Has anyone else had this problem or know the right direction for a solution? Wifi at work is a must!
it's not an adhoc network is it?
try moving closer to the source and see if other android phones can see it too
No, the network in question is not an ad-hoc. Yes, as I said in my original post, other smartphones and wireless devices have no problem making this connection.
I flashed and upgraded my phone's baseband radio to the most up-to-date version and my phone still doesn't see the network in question. I'm just about out of ideas.
Radio has nothing to do with WiFi.
Try different kernels.
Make sure that the visible access point isn't Wifi N.
Thanks for the experienced suggestion, thats just what I needed. Is there much risk involved in flashing kernels like there is with radios? Is the process the same, boot into recovery then install zip? Ill do the research myself here in a few hours when Ill have the free time but I'd like your input as well, Jack_R1, since it sounds to me like you know what you're talking about here. I'm hoping that you'll reply before I give this a try.
There is no risk when flashing kernels - in the worst case, if the flash went wrong, you can always boot to recovery and flash again.
The process is the same.
Kernel should be compatible with your type of ROM (AOSP GB/AOSP ICS/CM7/CM9/MIUI/etc).
Related
I bought a second-hand G1(no data plan) since I wanted to play with my phone. It ran 1.6 DMD64 stock with the newest radio; and it had WiFi problems.I did some research before purchasing and knew it could be flashed; so I tried flashing it to a modern ROM to see if that would solve the problems. After figuring out it was an American phone(I live in Holland) I managed to root it and flash CM6RC2. I now sometimes have a lot of reception; sometimes not. I tried installing WiFiReEnabler and WifiFixer; WifiFixer made connections overall a bit more stable; but half of the time I still don't have WiFi. I also tried to use my laptop's WiFi for my phone via USB; followed the instructions but failed. My phone managed to get semi-bricked 3 times in that period(stuck at G1 screen), and I tried flashing another ROM too; so I flashed CM 4 times. I'm using a Belkin N1 wireless router; switched channels, security and looked at my keyphrase.
The problems I have with WiFi:
- Not finding my router even though being quite close to it; happened only with 2 of the 5 times I flashed
- Finding my router but not connecting; happened 3 of the 5 times I flashed
- Saying that it's connected but not allowing me to browse; happened all times but WifiFixer occassionally fixes this
I'm still running CM6RC2 with Amon Ra recovery 1.7 on an American phone; my router is a Belkin N1 with firmware version 3.01.04 and hardware F5D8631-4 v3 with WPA-TKIP, broadcast SSID on, channel 4.
Is there a way that allows me to get stable internet on my phone without a data plan?
This could be either a hardware or software issue, not quite sure. Your options are listed below
1. Root and flash to a different more updated rom
2. Flash the newest radio(not sure if it effects wifi signal strength, forgot)
3. Open up the G1 and see if any connectors are loose.
Option 3 is probably out of the question, option 1 and 2 can be done by looknig into the rom bible(sticky) in the G1 dev thread, this will give you threads with new roms, how to install them etc, as well as flashing the new radio(if you have not yet done that)
I already flashed the newest radio, since I tried to install CM6 and in that guide I was instructed to flash the newest radio. I also obviously have installed CM6RC2 which is the newest version of CM.
I did read somewhere that more people had WiFi issues with CM6RC2 or deratives; I'll try running an older version of CM.
Edit: Doesn't work; at least I can't browse when I'm connected. Doing a nandroid restore right now; I'm intending to use Froyo.
In the case that doesn't work, how hard and dangerous would it be to open up my casing and look for those wires? It's second-hand, so warranty would likely not be a problem.
Thanks for answering anyway.
Is it possible that your router is using a different band?
I don't know about Holland, but sometimes different countries allow different wireless bands.
Try changing the channel on your router to something like channel 7 or 11, something varied from the norm.
Well. I found a solution. Connecting my old sitecom wl-167 which has no wireless N support seems to give me no problems.
(Holland has different channels then America, but my G1 was surprisingly already configured for Europe)
Thanks for your help anyway!
P.S. My XDA does seem to have some problems. "No route to host" when trying to post.
Edit: It appears it isn't 100% fixed; WiFi-fixer still solves it right now but it might not be the solution.
Edit 2: Well, WiFi-Fixer is able to fix my problems all of the time for now; but ocasionally I have WiFi for 10 seconds then 10 seconds no WiFi, et cetera.
Sent from my HTC Dream using XDA App
Edit 3: It isn't threatening to my WiFi anymore. Thanks everyone who tried to help me.
Hi,
I've been having a problem where my phone is restarting itself intermittently while I use the wireless network at my school (Purdue). I've tried both WPA and WPA2 (the school provides networks for both) and seen problems with both. The networks are the "enterprise 802.1x" version which requests a username and password to connect. I sometimes have to try a few times to get it to connect to WiFi (it sometimes takes a minute or two after I first turn on "Wi-Fi". Then, every few hours, the phone reboots itself: I'm in the middle of doing something (can be anything) or the phone is idle in my pocket and then the AT&T boot screen appears. I assume that there is some sort of kernel panic or something else that causes the hardware to reset itself.
I'm fairly sure that this issue only happens in a specific building on campus, so perhaps there is a misconfigured access point here. Even so, this is still a bad problem and could have security implications (perhaps a malformed packet is causing some buffer to overflow).
My phone is a non-rooted, stock AT&T Captivate with the JH7 firmware
I've tried talking to Samsung, but they want me to send the phone to them so that they can "repair it". I've swapped out the phone at the store where I got it for a new unit and the new unit (with new battery) also has this same problem.
The 802.11g at my house works flawlessly.
Ideas?
Assuming that this is a kernel-panic issue, how would I extract a stacktrace or other debug information? Do kernel panics cause the phone to restart itself? Have the 802.11 drivers been updated in newer kernels (what's the chance that a custom firmware based Froyo would solve this issue?)
(disclosure: This question was posted on samsungcaptivateforum last month without any
productive responses. I'm a new user here, so I cannot link to that post yet....)
pigrew said:
Hi,
I've been having a problem...
Click to expand...
Click to collapse
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)
Do you use "enterprise"/RADIUS/802.1x authentication? (This (roughly) means that you need to enter a username and password in order to connect to your network).
I was trying to wait until AT&T releases 2.2, but I'm getting impatient on that front. I'll try to look for the speedmod kernel, perhaps. My office is in an electronics lab, so I wonder if something is spewing out RF interference in here.
-Nathan
joeshmoe08 said:
Thats weird because my phone has no problems like that and I have connected to many WPA networks. I don't know the source of the problem but my suggestion would be try a custom rom before sending to samsung because it can't hurt. If it doesn't work for you then just restore to stock and send it to them. (kernel suggestion: latest speedmod kernel. works flawlessly.)
Click to expand...
Click to collapse
I just flashed my with the Cognition 3.02 firmware and the issue is still present. My hunch is that it is a wifi firmware or driver bug. I doubt that these things are changed in the various kernel builds.... Maybe the official Froyo release will fix it, but at this point I doubt that it will.
Someone in my building suggested that the issues may be caused by us having two separate networks on different sides of the building that have the same ESSID.
I ran into this article yesterday, How to Flash CyanogenMod 7 ROM Samsung Captivate AT&T, and felt it was about time to learn about this. Plenty of you have already ROOTED your phones, and know from experience, what to do. But, I don't. Right now, I'm stuck with the options of accepting things don't work right, because of AT'T's unwillingness, or inabilility, to correct the issues I have, or reinsiall new, and lose all I've put on, or send back to Samsung for repair, and have them lose all I have on it, or try Rooting and adding a ROM, that may solve my issues. But to do that, I need a little help in understanding it.
First, if I try and run a program, like CyanogenMod 7, and it doesn't work correctly, snd screws up my phone, is there a way I can reinstall Android, and start over, or is that the proverbial kiss of death for my Captivate, and I'm stuck with it like that?
Second, is this the right ROM to try? AT&T can't fix my BLOCKS, of UNKNOWN APPS. The Settings change is easy, you click on activating Unknown, in Application settings..., unless you have no UNKNOWN, to choose. Also, in MMS settings, AT&T shows in a tutorial, that you have the option, of activating Delivery Report and Read Report. It shows this as plain as day, on that tutorial for the Captivate, yet mine, has NEITHER OF THOSE OPTIONS. Also, to TURN ON EDGE, the setting is missing, so I can't activate EDGE, which I guess is no big thing, since the towers AT&T has for us to connect with, THAT ARE 2G, are in such poor condition, no one can connect to them. Thank you, WIFI, for helping me get, ONLINE. Will this, or other ROM's, solve this for me?
If there are any suggestions of how to do this, and what to use, I'd appreciate hearing it from you. Again, I thank any effort, to help me.
1.cm 7 would not be the best rom to flash for your first time.
2. All roms are android, you are running at&t/samsung version of an android rom...
3. Yes you can get back to your stock rom if you don't like/something goes wrong (other than a bad bootloader flash)
4.all custom roms have all the blocking done by at&t removed so switching to 2g(edge) is possible and also faster 3g speeds known as hspa. And unknown sources is in the settings so you can install apps from outside the market.
5.the threads at the top of every section with a little thumb tacks are called stickies, give those a read through.
Like he said above. If you want the pretty much stock experience that your used to but want it fixed then I would suggest starting off with Cognition 4.4 or whatever it is now.
Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
From newbie to a newbie, I took the advice of others and read threads for atleast a month before I flashed my first rom. My choice was Andromeda3, It has a written tutorial and a video on how to from start to finish. From what tools or apps you will need and how to use them , I watched that atleast 6 times and also while I was flashing the kernel and the rom. It may have been overkill but my flash was perfect and I'm real happy with my phone now. You may not go with the same rom I did but do your self a favor and do what I did to prepare for your first flash.
Hi guys (and girls),
I'm going slightly mad trying to figure out a stable setup for my O2X. I have been switching between the latest CM7 nightlies, and MoDaCo FR19. In general, CM7 gives me quite frequent black screens, and FR19 seems quite stable. However, there is one issue that is present in both ROMs.
I am unable to get a stable mobile data connection when I switch from WiFi. Sometimes it works, and sometimes it doesn't. To get it to work again, it sometimes works to switch to 2G only (and possibly back again). I have tried several different radios recently: 218, 606, and 622, all with the appropriate RIL. The mobile data connection for 218 drops in and out at random without any clear pattern. For the other two radios switching on or off 2G only seems to achieve stable connection. However, it does not actually seem to affect whether I get a 3G or 2G signal. The display can say H or G, even when 2G only is checked. Bluetooth did not work correctly with 606.
To top everything off, the GPS does not seem to behave consistently for a all the different radio versions.
I guess that people have different experience with different radios, so which radio are the guys in Norway using? Do I really have to slog through every released radio and spend the day checking each one of them? Can I expect to find a radio/from combination that blacks to give me a stable GPS and mobile data connectivity, as well as good WiFi?
I know this has been discussed numerous times before, but people never seem to reach any conclusions. I'm just looking for advice on how to proceed to fix my problem.
I'm on cm7 .77 and i honestly havent had a blackscreen since i flashed it (yesterday morning) + battery is good now. For me this is the most stable nightly so ill stick with it for 2 weeks on my holiday )
Edit: bb .502 ril 218(i think) dont have any problems with network switching btw
Sent from my Optimus 2X using XDA App
kolaf said:
Hi guys (and girls),
Do I really have to slog through every released radio and spend the day checking each one of them?
Click to expand...
Click to collapse
You probably have to, yes. This sounds more like a problem with the specific coverage in your area and how the phone interacts with the cell-towers than an actual problem with the phone. You may be in an area with weak signals from several stations, you may be in an area suffering from sudden bursts of noise, there could be a lot of reasons for why this is happening.
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
Then you should probably do a manual scan (in phone settings) for networks, and pick one manually.
Also try using the INFO menu (*#*#4636#*#*) and see if choosing a specific protocol helps.
If you're still unable to maintain a stable connection, I'd say that'd be grounds for returning the phone for a replacement.
Weak advice, I know, sometimes there just aren't any quick solutions.
::Trym
TrymHansen said:
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
::Trym
Click to expand...
Click to collapse
Thanks for your reply. Do you by any chance have a link to the firmware?
kolaf said:
Thanks for your reply. Do you by any chance have a link to the firmware?
Click to expand...
Click to collapse
Sort of. In this thread http://forum.xda-developers.com/showthread.php?t=1035041 you'll find complete ROMs of the previous versions. Install one of those with SmartFlash, then run the LG Mobile Update tool to get the latest.
::Trym
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
kolaf said:
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
Click to expand...
Click to collapse
No, you don't have to use NVFlash. The advantage of using the smartflash method is that you get a completely "factory fresh" phone, with all the stock content present (movies, music, pre-installed apps) and you're sure to get a matching baseband and ROM.
Note that you have to flash both files, both the baseband and the ROM. The LG update tool won't update if you have a "new" baseband on an old ROM.
::Trym
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
kolaf said:
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
Click to expand...
Click to collapse
Yes, it does. Each firmware pack comes with TWO files, the baseband and the ROM. To make sure you avoid any trouble, just flash them both, though, as you say, you can probably stay on the one you have, as yes, the LG Mobile Update tool will overwrite both the baseband and the ROM with the new versions.
::Trym
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
I guess rooting it shouldn't affect performance in any way?
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
kolaf said:
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
Click to expand...
Click to collapse
Yeah, you probably should, as your mission right now is to find out whether you can get a stable mobile data connection or not.
kolaf said:
I guess rooting it shouldn't affect performance in any way?
Click to expand...
Click to collapse
Not to my knowledge, but I'd still advise you to wait a few days while sorting out the connection issue. Not that I think rooting it would affect that one way or another, but if you can't get it work as it is, you can return the phone in the state it is now, factory fresh.
kolaf said:
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
Click to expand...
Click to collapse
It certainly is. It also *stays* snappy over time, which can't be said for the 10a/b versions.
::Trym
The first test drive with the new firmware has been completed. On the way out it switched to mobile data flawlessly, but a longer drive it started falling out and reappearing for only short periods. When we stopped at the destination seemed to stabilise with a 3G connection again.
For the return trip I selected use only 2G network. The network connection remained stable for the entire journey.
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
kolaf said:
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
Click to expand...
Click to collapse
The 2G only setting in the phone menu equals the "GSM only" setting in the INFO-menu. I'm far from an expert in these matters, this thread has an overview: http://forum.xda-developers.com/showthread.php?t=675136& of what the different modes do.
::Trym
More testing seems to indicate that as long as i leave "use 2G only" check, my mobile data connection seems to be pretty stable. It even switches between 2G and 3G, although apparently a bit more conservatively.
I guess I get to keep my phone anyway
Now for some rooting...
Just an update on the results from my testing. The second time I went out my mobile connection never appeared. This was with only 2G checked in the settings menu. In the Info menu, this corresponded to GSM only.
I then changed it to GSM auto (PRL), and then I got my intermittent mobile data again. I then change it to WCDMA preferred, and my data connection seems to be stable for now. This apparently requires much more testing...
F another chapter in the connectivity saga. Having WCDMA preferred selected in the Info menu, things mostly work, although the data connection drops sometimes.
Another problem I'm noticing with the stock ROM is that it usually is unable to reconnect to my home WiFi network when it comes within range. I have the money was selected to reconnect. Sometimes I even find it disabled in the list.
Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
gibosi said:
Updating from CM9, I notice that the phone now loses it's authentication with the router multiple times in one day. That is, the icon changes from blue to white, and no data can pass through. It is necessary to turn wi-fi off and then back on to restore the connection.
On the premises, we also have a Motorola G, Nexus 7, Samsung Galaxy Nexus and a Nexus One. All but the GNex have no problems with this router. The GNex is still stock, so it would appear to have something to do with these older Samsung phones running 4.3. Searching Google, someone suggested forcing the phone to use the 2.4 band, and doing so with the GNex doesn't completely fix it, but it does happen less often. However, I can't find a "wi - fi frequency band" setting in CM.
So, does anyone have any idea what's going on? And is there a way to force the Captivate to use the 2.4 band?
Thanks much
Click to expand...
Click to collapse
CM9 is quite old, chances are that the kernel modules don't support it.
BWolf56 said:
CM9 is quite old, chances are that the kernel modules don't support it.
Click to expand...
Click to collapse
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
gibosi said:
Thanks for your reply.
Before, while running CM9, the phone would remain properly connected to the router indefinitely. This problem of losing authentication did not occur until after upgrading the Captivate to CM10.2.1
Click to expand...
Click to collapse
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
BWolf56 said:
Oh misread your post.
If forgetting and re-entering the network doesn't work, try another kernel (make sure it's compatible).
Click to expand...
Click to collapse
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
gibosi said:
I am willing to give this a try, but I am still pretty new at this sort of thing. While I have rooted and put Cyanogen Mod on two phones, I have never tried different kernals. Would you be able to give me a short list of 3 or 4 compatible kernals that I could try?
Thanks much!
Click to expand...
Click to collapse
Just look in the Dev section and use one that matches your version (4.1, 4.2, etc).
NeatKernel seems to be popular around here.
Installed NeatKernal today so will see how it goes.
Thanks much for your help!
Installing NeatKernal didn't solve the problem, so decided to try the most recent CM 11 nightly....
After installing CM 11, the router and the phone still do not play nicely together. I contacted Linksys about this issue quite some time ago, but never received a response, so it is beginning to appear that the best solution is to simply replace the router. However, the Captivate is just a spare phone to play with, so it's not worth the extra expense and time, so will probably leave things as they are...
Cheers