I'm not gonna BS anyone. I'm clueless!!
I lent my phone to a friend for a few days and he installed one of the ICS roms on it. A few days later I realized that it would no longer keep wifi active. Anytime I'd attempt to turn wifi on it would say error and time out.
I figured no biggie I'll just Odin back. So I Odin'd back to Eclair and still no wifi. Even worse... when I boot the phone it takes exactly 33 minutes to get past the "Galaxy S" screen. It isn't frozen as I can see the S throbbing.
Another symptom of my problems is that the haptic feedback is gone.
In recap, No wifi, no haptic and a loooong boot.
As I said earlier, the problems persist in stock form as well as CM7.
Any help would be greatly appreciated.
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Antiph3d said:
OK, The weirdness continues. I decided to try roms I've used in the past to see if anything changed. I started off with Andromeda 1.0. The boot time is now back to normal and I've regained haptic feedback.
Unfortunately I still don't have wifi. It'll now allow me to enable wifi and it'll attempt a scan but comes back with "unable to scan networks". I attempted to manually add multiple networks and get the error "unable to save the network" then wifi gets disabled.
I'm at a loss at this point so I'm hopeful someone can come through.
Click to expand...
Click to collapse
When you Odin'd back to Stock, did you Master Clear too?
Thanks for the reply.
Yes, I did do a master clear. Internal SD has been wiped but the problems continue.
The haptic feedback and boot time return to normal when I flashed Andromeda 1.0 but go bad again when I go back to stock.
Just went back to stock and am waiting the 30 minutes for the phone to boot so I can do another master clear. Can't see the second finding any residual files that the first didn't get but you never know I guess.
I just noticed that my Bluetooth isn't working either.
Data and cell work just fine though.
so... latest recap...
Currently running Andromeda3. The phone boots just fine in a nice fast timeframe. Haptic feedback is working fine.
Wifi and Bluetooth are no go's. Just don't get it
Related
A little background on my phone:
T-Mobile G1 USA, black
2300mAh battery
Amon_Ra's Recovery
CyanogenMod5 Test 6
Newest Radio
DangerSPL (Hayukos, however it's spelled)
Launcher Pro
Ok, so here's the issue:
A while back my Wifi stopped working completely. I flash my phone a couple times a month, every couple of months. I get bored and look for a good ROM every so often but once I find one I like I stick with it for a few months.
If I can coincide Wifi issues with a ROM, it would have to be KingKlick's 2.1 Espresso, but I'm not positive on that and I can't blame it on one ROM, at least I don't think so. It doesn't work with ANY ROM since around that time when I flashed that ROM (about 3-4 months back).
Since I flashed Super D 1.1x and up it works for about a minute or two and then I get an error saying there's no connection in the browser, Youtube, etc. It's doing this with CM5.0.7 test X.
I've done complete wipes of the phone through Amon_Ra's recovery, Data, Dalvik, EXT, battery, rotate... reflashed fresh ROMs... won't fix it.
I don't see how this could be a ROM issue at all, since it's across different 1.6 and different 2.1 ROMs. I also don't see how it could be a hardware issue since it works for a minute or two then stops.
So could this be a radio issue... or an SPL issue? I don't know exactly what those are, so I couldn't say. Would flashing the radio again fix the issue? Any help or suggestions is appreciated.
Download an application called "wifi fixer" from market. It seems to fix issues like this. Just a chance, though.
Strangely, I started having the same problem a few weeks ago. Wifi only works from a few minutes, to a few seconds. If I stream some music, it may last all night. Next to playing around with apps, I have not re-flashed my G1 at all. I found setting a static IP sometimes helps.
Trying wifi fixer now.
Downloaded it... doesn't work!
It seems to stay connected about another minute or two longer, but that's it. The app itself is really laggy and I keep getting a Not Responding error when trying to pop up the menu to get the logging to work.
When I finally get the menu to pop up I have no clue how to even get logging to work, there's the button for it but I have no clue if red/green is on or off. The pop up "Enable Logging"/"Disable Logging" doesn't really explain it well. I have no clue if it's saying I did enable or disable. And I have no clue where it saves the file.
Thanks for the suggestion though. And I don't know if it's T-Mobile, but my internet in general isn't working right now. 3G shows several bars but it won't load ****... I've had this problem before when T-Mobile was just the issue for a few hours.
Picolini said:
Downloaded it... doesn't work!
It seems to stay connected about another minute or two longer, but that's it. The app itself is really laggy and I keep getting a Not Responding error when trying to pop up the menu to get the logging to work.
When I finally get the menu to pop up I have no clue how to even get logging to work, there's the button for it but I have no clue if red/green is on or off. The pop up "Enable Logging"/"Disable Logging" doesn't really explain it well. I have no clue if it's saying I did enable or disable. And I have no clue where it saves the file.
Thanks for the suggestion though. And I don't know if it's T-Mobile, but my internet in general isn't working right now. 3G shows several bars but it won't load ****... I've had this problem before when T-Mobile was just the issue for a few hours.
Click to expand...
Click to collapse
Sorry, fixed my issues without any problems when I had them. =[ I don't know why it's so buggy for you, worked like a dream and that was the only reason I suggested it. Sorry to offer false hop. =[ I can't really be of much more assistance.
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
Hey there.
I have a stock Samsung Galaxy S4 Active on the AT&T network. Recently, I've been plagued by a number of troubles.
Bit of background:
For a while, I had the most bizarre issue: the screen thought I was touching it when I wasn't, near the bottom-middle of the screen, and would attempt to open/click on anything in that area. Often turning the screen on and off would help, for a little while. I was reaching my wits' end, because that would obviously be very frustrating to someone who uses their phone frequently throughout the day.
I thought maybe it had been new software I had installed, so I did a factory reset. Problem remained. I factory reset with NO backups. Problem remained. I updated to 4.4.2 via OTA. Problem remained...
And then mysteriously went away on its own.
I've been working in tech for a decade now, mainly in PC and server architecture, so I know better than to look a gift horse in the mouth - but I also know better than to think a problem that "mysteriously" goes away is gone for good. So the first part of my question: does anyone know what could have possibly been causing this?
I'm not super phone-savvy. I've rooted and flashed a few phones in the past couple years, but I'm by no means developer-level.
---------------------
Which brings me to my next problem... around the time that this issue went away, another one cropped up. Randomly, my phone will stop sending/receiving texts/calls, and the data connection will not function. This will continue until I turn on airplane mode and turn it off--at that point I receive all my missed texts, and it works again... sometimes for 5 minutes, sometimes for nearly 2 days. It's really frustrating. I've tried factory resets, I've tried restoring default APNs... but I'm at my wit's end with this. Can anyone help?
Thanks!
I should add that, with my last issue, it still shows a data connection in the notification bar - but there is none, or at least, no activity on it. It doesn't simply act as if it's in airplane mode and go "wah no data network" as soon as I try using it--it just simply hangs for ~30 seconds, then times out. Messages don't get received, webpages don't load, calls don't get placed, etc.
I received the latest update to 4.4.4 this past Wednesday. This is the update that included the HTC Eye Experience. The update went smooth and everything was all good until I was driving home from work. The phone randomly rebooted itself and ever since, I cannot get Wi-Fi to turn off. It stays off for approximately one minute and then turns right back on. I have searched this forum and others all day with no solution seeming to help. I also hard reset the phone earlier today but the problem persists. Anyone had this issue or have any solutions? Thank you in advance!
schakab said:
I received the latest update to 4.4.4 this past Wednesday. This is the update that included the HTC Eye Experience. The update went smooth and everything was all good until I was driving home from work. The phone randomly rebooted itself and ever since, I cannot get Wi-Fi to turn off. It stays off for approximately one minute and then turns right back on. I have searched this forum and others all day with no solution seeming to help. I also hard reset the phone earlier today but the problem persists. Anyone had this issue or have any solutions? Thank you in advance!
Click to expand...
Click to collapse
Do you Sprint Connection Optimizer running? That'll keep Wi-Fi on. See this http://support.sprint.com/support/t..._Optimizer_on_or_off_HTC_Onereg_M8/51761-1469
henderjr said:
Do you Sprint Connection Optimizer running? That'll keep Wi-Fi on.
Click to expand...
Click to collapse
Thanks for responding! Its not Connections Optimizer. It has been turned off from day 1 but I did recheck and it is still off. My M8 is not rooted and completely stock. It worked great up until this update. I tried soft reset and hard reset to no avail. There is a message that pops up in the notification bar sometimes (Wi-Fi notification with a red triangle) that says setup has not been complete but nothing happens when I click on it and it goes away. Sprint is, of coarse, no help at all. They want to send me a new phone but I really don't think this is a hardware issue. Maybe a bad download?
When turning on Bluetooth the toggle slides over for 10 seconds or so (still greyed out) before sliding back to off (the Bluetooth never actually comes on). It started yesterday out of the blue. At the time it started, I was running 6.0.0 (MRA58K) and had been for several weeks without an issue. Reboots don't fix it. Safe mode doesn't fix it. Wipe Bluetooth cache/data doesn't fix it. As part of my attempts to get it working, I upgraded to MRA58N. Then a round of trying all the above stuff all over again. Still no go.
I attached a log of an attempt to enable Bluetooth (trimmed). I waited until 0149 before I hit the toggle to turn it on and the log is from that point on. The point I see the obvious failure is 01:49:18.131 with the error message "Error enabling Bluetooth (enable timeout)" but I can't make enough out from the rest of the log to figure out why it's timing out.
Experiencing same issue on my Nexus 6. Worked fine for several days after upgrading to MRA58K. Then it quit. Same BT toggle symptom you described. Just did the OTA to MRA58N this morning. Tried reboot/safe mode/wiping BT cache and data. Still no workie.
I know none of this is really very helpful to you, but just wanted you to know you aren't the only one with this problem.
I ended up having to do a full wipe and re-install to fix it.
I'm having the same problem for weeks.
I tried for days to straighten it out. Uninstalled apps one by one and rebooted until I'd uninstalled everything, dug through logs, and did everything I could think of and nothing works. The silver lining was that wiping it and re-installing fixed it so it wasn't a problem with the hardware. I don't know if it was a bug or a glitch but I couldn't resolve it without a reinstall. Been over two weeks and I haven't had a problem since.
I had a similar problem, except Bluetooth wouldn't connect nor would it connect to anything. Toggle would act as though it turned off or connected, but 20-30 sec later, it'd go back to on and disconnected. A simple reboot fixed it for me, and this was on Lollipop a few months ago.
Sent from my Nexus 6