Vicious JellyBean V2 - WiFi issues

[njguy0414]

I've successfully connected to the wireless at home. I'm now at work and can't connect. We have a secured and unsecured network. What I usually do when I get a new phone or need to configure the secure settings is connect to the unsecure wireless first to verify that I can connect.

When I go to the WiFi screen to choose a network to connect to, and choose the unsecure one, it says "Failed to connect to network." Long press on that network and the only option I get is "Connect to network".

If I tap on the secure network, that is labeled as "Disconnected", the pop up window allows me to Cancel or Forget. But if I tap on Forget, it fails to forget network. Long press options are to Forget or Modify. If I select modify, it allows me to change settings. After I enter in the settings it says "Failed to save network."

I've turned WiFi on and off, and rebooted the phone. I also manage the wireless on my campus and I do not see my phone attempting to connect on the controller. (Mix of Meru/Bluesocket controllers and AP's)

Is there something I need to do to allow the phone access to a file? Do I need to do something with credential storage?

 

[2defmouze]

First thing to try.. in Wifi Settings > Advanced > uncheck the Avoid poor connections option.

Second check dmmarck's Jelly Bean thread for the wifi fix if you haven't already, its a quick flash that might help.

If nothing works it might just be something you'll have to live with for now if no one else has any ideas... as you know these JB ROMs are not 100% and aren't even designed for our devices, lol, so this might just be one of the hiccups you'll find right now..

 

[njguy0414]

Thanks.

Unchecking 'Avoid poor connections' didn't work. I thought the V2 ROM had the wifi fix rolled up in it, but I'll look into that now. I don't think it's a signal issue though.

 

[njguy0414]

Rebooted *Again* and now I see an authentication problem. It's asked me for a lock screen PIN or password before I can use credential storage. After I did that, it connected to the unsecure network. And then I was able to run the secure settings.

I'm guessing it was just a hiccup due to not having the lock screen setup. But now with the lock screen, I don't get the Google now option.... any ideas how to get to that screen?

 

[2defmouze]

Rebooted *Again* and now I see an authentication problem. It's asked me for a lock screen PIN or password before I can use credential storage. After I did that, it connected to the unsecure network. And then I was able to run the secure settings.

I'm guessing it was just a hiccup due to not having the lock screen setup. But now with the lock screen, I don't get the Google now option.... any ideas how to get to that screen?

Just drag up from the Home softkey

 

[Muddyml]

Jellybean v2 for CDMA has a very weak WiFi signal.

There is a fix for it though that is implemented onto v3. Or you can download and install it on v2 yourself.

http://forum.xda-developers.com/showthread.php?t=1739097

Sent from my Galaxy Nexus using Tapatalk 2

 

[dmmarck]

Jellybean v2 for CDMA has a very weak WiFi signal.

There is a fix for it though that is implemented onto v3. Or you can download and install it on v2 yourself.

[FIX] Fix for WiFi on Verizon Jellybean 4.1 ROMs - xda-developers

Sent from my Galaxy Nexus using Tapatalk 2

In case he loses track, that's the same fix in my JB guide.

 

[njguy0414]

Jellybean v2 for CDMA has a very weak WiFi signal.

There is a fix for it though that is implemented onto v3. Or you can download and install it on v2 yourself.

[FIX] 07-01-12 - Fixes for WiFi, BT, GPS, & MMS on Verizon Jellybean 4.1 ROMs - xda-developers

Sent from my Galaxy Nexus using Tapatalk 2

I'll give this a shot and see if it helps. I'm still not getting wireless correctly where I work but at home it's fine. This is my first root, so I'm a bit unsure on how to get this updated.

(Questions I'm sure are answered somewhere already)
If I go to V3, do I lose all the work I've done to set the phone back up after the wipe? Or should I just add in this fix? I think I have a bit more reading on the forums to do.

 

[dmmarck]

I'll give this a shot and see if it helps. I'm still not getting wireless correctly where I work but at home it's fine. This is my first root, so I'm a bit unsure on how to get this updated.

(Questions I'm sure are answered somewhere already)
If I go to V3, do I lose all the work I've done to set the phone back up after the wipe? Or should I just add in this fix? I think I have a bit more reading on the forums to do.

You should be able to simply wipe cache/dalvik and flash V3, preserving your data. However, if you have any crazy issues (like force closing, random reboots, etc.), you should probably consider wiping everything and starting anew.

 

[njguy0414]

OK, easy enough! Should I delete V2 or just keep it there if I decide to roll back? I'm assuming that I could have a list of ROM's to choose to boot to and that wouldn't cause any issues.

For me, and anyone else following, I cut this from the sticky:

Do I need to wipe the data when flashing themes, kernels, mods? No, only when flashing between different ROMS. Just wipe the cache partition & dalvik cache.

Do I need to wipe the data when upgrading to a newer version of the same ROM? You could most likely get away with not wiping the data going from ROM ABC v1.2.3 to ROM ABC v1.2.4 without a problem, but it's better to be safe then sorry.

I can't access ROM Manager, How do I get back into recovery mode? Power off your phone. Once the phone is turned off, Hold volume down + volume up + the power button at the same time until the phone starts up in Fast Boot. Use the volume keys to choose Recovery and press the power button to select it. The phone will boot you into ClockworkMod Recovery the same way ROM Manager would have. You can now access your backups or whatever else you need to get to.

 

[dmmarck]

OK, easy enough! Should I delete V2 or just keep it there if I decide to roll back? I'm assuming that I could have a list of ROM's to choose to boot to and that wouldn't cause any issues.

For me, and anyone else following, I cut this from the sticky:

Do I need to wipe the data when flashing themes, kernels, mods? No, only when flashing between different ROMS. Just wipe the cache partition & dalvik cache.

Do I need to wipe the data when upgrading to a newer version of the same ROM? You could most likely get away with not wiping the data going from ROM ABC v1.2.3 to ROM ABC v1.2.4 without a problem, but it's better to be safe then sorry.

I can't access ROM Manager, How do I get back into recovery mode? Power off your phone. Once the phone is turned off, Hold volume down + volume up + the power button at the same time until the phone starts up in Fast Boot. Use the volume keys to choose Recovery and press the power button to select it. The phone will boot you into ClockworkMod Recovery the same way ROM Manager would have. You can now access your backups or whatever else you need to get to.

I would suggest wiping your phone completely and starting anew with Jelly Belly. It's by far the most stable of the roms, the dev is giving it constant support/attention, and it's actually being developed. The other roms are simply adding useless nonsense, while this one actual and legit coding is going on to improve Jelly Bean and the experience for us.

Once you're on Jelly Belly, you need not wipe a thing to flash an update. That and the whole "wait 5 years at the Google screen before the boot animation starts" thing is a thing of the past.

In all, it's as close to a "stable" JB rom that we're going to have before the actual JB source comes out, and it's the one I personally use and recommend.

 

[njguy0414]

I would suggest wiping your phone completely and starting anew with Jelly Belly. It's by far the most stable of the roms, the dev is giving it constant support/attention, and it's actually being developed. The other roms are simply adding useless nonsense, while this one actual and legit coding is going on to improve Jelly Bean and the experience for us.

Once you're on Jelly Belly, you need not wipe a thing to flash an update. That and the whole "wait 5 years at the Google screen before the boot animation starts" thing is a thing of the past.

In all, it's as close to a "stable" JB rom that we're going to have before the actual JB source comes out, and it's the one I personally use and recommend.

Man - you're part psychic aren't you? I was just wondering if that was one of the better/stable ROMs available. That's all I want right now, a vanilla Jelly bean. I appreciate the info!

1) Any quick suggestions on how to preserve any settings, or shortcuts to getting apps/things set up faster?
2) What does "separated from gapps" mean?
Let me clarify. In your guide you say that "Be sure to follow the thread for installation procedures, particularly since GAPPs are not separated from the rom.
But on the wiki page under the features it says,"first rom separated from gapps (proper)"

 

[dmmarck]

Man - you're part psychic aren't you? I was just wondering if that was one of the better/stable ROMs available. That's all I want right now, a vanilla Jelly bean. I appreciate the info!

1) Any quick suggestions on how to preserve any settings, or shortcuts to getting apps/things set up faster?
2) What does "separated from gapps" mean?
Let me clarify. In your guide you say that "Be sure to follow the thread for installation procedures, particularly since GAPPs are not separated from the rom.
But on the wiki page under the features it says,"first rom separated from gapps (proper)"

I have seen success with using stuff like Titanium Backup. Personally, I tried it on a very early port and it destroyed me and my will to ever use it again, at least for the time being.

Yes, this is the first port to have GAPPs separated. Long story short, CyanogenMod used to include google applications (like your core google stuff, ala Play Store, GMail, etc.) with their rom. They got a cease and desist order from Google, saying "hey man, our stuff, back off." So a separate flashable zip solved that. A lot of "small time" roms still include GAPPs, so you don't have a separate zip to flash. This doesn't; in theory, that's how it should be (separate), but most fly under the radar, b/c let's face it, the only reason Google cared about CM was because it was monstrously big.

If you notice with other roms, the bigger roms always have separable GAPPs (AOKP, Gummy, etc.), while the others (Liquid) don't.

Also, my apologies. The "not" in what you quoted should have been a "now" lol.

 

[njguy0414]

Ha! One small typo really changed the meaning. Glad to help 'proofread'. Nice to learn some of the history. I'm all set now, but since I'm at work I'll leave the wiping of the phone for later tonight. Sounds simple enough from here on out. (famous last words)

 

[dmmarck]

Ha! One small typo really changed the meaning. Glad to help 'proofread'. Nice to learn some of the history. I'm all set now, but since I'm at work I'll leave the wiping of the phone for later tonight. Sounds simple enough from here on out. (famous last words)

lol thanks. I type this stuff very quickly and am human, unfortunately.

Good luck and you know where to find us!

 

[njguy0414]

All went well with the change to Jelly Belly v1.7. But man.. it's a PITA setting up apps again, although I am getting faster at it. Everytime I seem to be setting things up and grouping things more efficiently.

So now I see a new v.18 out. I can now simply download it, and just flash it and that's it? No resetting everything back up?

 

[dmmarck]

All went well with the change to Jelly Belly v1.7. But man.. it's a PITA setting up apps again, although I am getting faster at it. Everytime I seem to be setting things up and grouping things more efficiently.

So now I see a new v.18 out. I can now simply download it, and just flash it and that's it? No resetting everything back up?

100 percent correct

Sent from Oliver, my Nuclear-Powered, Orb-Shaped Candy Device.

 

[hoofaarted]

Is anyone else having the issue of not being able to connect to 802.1x EAP Wifi? Encryption method: PEAP. I have a similar issue to the OP's. It attempts to connect but gives "Authentication Problem" - So far this is my only issue, less the weak wifi signal - but already remedied that issue.