Ok. So here's a little tidbit of info.
I had a tenderloin ics build (the first ics one, 0.4 based).
Everything worked fine. But every time i would upgrade to a newer nightly build based off .6 or whatever, wifi would never work.
It would just not turn on, you could toggle it on but it just wouldn't do anything.
I was using CWM to update, and after every update i would have to back down to that first ics build to turn on wifi.
So i practically gave up for a week or so. Then i broke down and tried the ACMEInstaller2 method. Booted to the latest nightly build and presto, wifi turned on first try.
So those who are stuck with a broken wifi, try that install method. Not sure what's different. Maybe i have a broken CWM that doesn't update everything. Maybe it's some sort of bug, not too sure.
Enjoy.
report back after a week and if you didn't encounter any issues at all i'll do that
Related
here's my problem:
when ever i leave phone to be in deepsleep mode,
i cam back to find it looking for GSM signal with no hope,restarting fixing the signal.
tried diffrent roms, CM7, MIUI,with all kind of kernels nothing works
phone condition is fine,did't drop it or hardware issues on it.
was working great for last 6 months, but after i flashed a ton of diffrent CM roms this starts to happen,
my thoughts:
could it be a NVdat.bin issue doing this?
if so, what i can do to let the phone re build fresh ones,
+ i have old backup of EFS folder.
can you share your thoughts please?
I had the same thing happened to me and my friend's phone in the last week. Both running the ported gingerbread roms. Had to Odin back and finally working. Not sure if it was the Rom or something. My phone says it shows a baseband of UVKB5 which is the correct modem.
Finally flashed back to froyo and had it working, now just reflashed a gingerbread rom and it's working again.
Dattack said:
I had the same thing happened to me and my friend's phone in the last week. Both running the ported gingerbread roms. Had to Odin back and finally working. Not sure if it was the Rom or something. My phone says it shows a baseband of UVKB5 which is the correct modem.
Finally flashed back to froyo and had it working, now just reflashed a gingerbread rom and it's working again.
Click to expand...
Click to collapse
will try this option today and give a feedback.
thank u
Edit:
odining back to JFD solved the problem.
Hey gang. Have to post this here until the post count goes higher.
I've been installing the updates for DSC as they are released, due to the nagging wifi freeze issue. Everything else works great.
However, something changed after .63b, perhaps the wifi_supplicant mod?
While at work, no ROM after .63b will authenticate to the WIFI. It scans and attempts connect 3 times, then goes to disabled.
Re-running ROM install for 63b and then new DSC_Test.zip (I like reboot menu option) works like a champ. Wifi freezes still occur, but are relatively infrequent. I'm on 406 Baseband.
As such, I'm unable to install the new .7, or anything after .63b.
I haven't seen anyone else mention a similar problem, perhaps they're only dealing with a single network. I use two, my home network and work network. My home network is WPA2 AES encryption, and seems to work fine with updated ROMs. My work network, nothing after .63b.
Just tried .7b again, nothing.......reloaded .63b, wifi fine.
Just wanted to bring this up. Thank you all so much for your efforts. Still the best ROM, and the best ROM support available.
Have you tried flashing Olleh kernel from Phoenix release post?
I believe I have, but was a while ago. I'll go try it again, to be sure. Thx.
UPDATE: tried several updated kernals, no avail. As soon as .6b, then .63b go on, my WIFI connects immediately. It's not in the kernal, but the ROM/framework.
I recommend a factory reset after flashing .7
Let's check this:
http://www.littlemaruko.com/Nopteam/DSC_Check.zip
--
It will revert WiFi-related binaries to 407.
--
And be sure to flash Olleh kernel, it's the only actual thing that was changed in 0.64b
I recommend a factory reset after flashing .7
Click to expand...
Click to collapse
Ya, I had done resets and cleans installs on the earlier releases after .63b, all had the same issue...WIFI connects to home network, but not work network (801.x EAP)
As everything is configured and re-installed now, its easier to reload .6b and .63b, without reloading everything.
_n0p_
Let's check this:
http://www.littlemaruko.com/Nopteam/DSC_Check.zip
--
It will revert WiFi-related binaries to 407.
--
And be sure to flash Olleh kernel, it's the only actual thing that was changed in 0.64b
Click to expand...
Click to collapse
Looks like you're onto something here. Have both the Olleh kernal and the DSC_Check loaded and my work WIFI authenticated properly.
Since changing 2 things at once isn't proper troubleshooting protocol, I reloaded .7b. WIFI problem came back. Reloaded DSC_Check (not Olleh Kernal), and WIFI is fine now. So there's something in those binaries my work network wouldn't authenticate to.
If I can help you figure it out, I will. All working now though. You the man!
It's enough info. I'll revert to 407 wifi binaries in future releases.
--
I just wish we figure it out before 0.7 release
It's enough info. I'll revert to 407 wifi binaries in future releases.
--
I just wish we figure it out before 0.7 release
Click to expand...
Click to collapse
Sorry about that......it was the .7 release not working that finally motivated me to speak up.
Thank you for keeping the Streak relevant and rockin.
rodeorat said:
However, something changed after .63b, perhaps the wifi_supplicant mod?
While at work, no ROM after .63b will authenticate to the WIFI. It scans and attempts connect 3 times, then goes to disabled.
Click to expand...
Click to collapse
OMG!!! I was hitting my head all of yesterday. I converted my home network to WPA2-Enterprise (801.x EAP) after installing OpenLDAP and FreeRadius on my servers for AAA and keep getting the connect 3 times and then disabled. It appears from my FreeRadius logs that it send a challenge to my AP which then perhaps sends it to the DS5 and something happens there that is out of spec.
I started using DSC at .65b and that also had the same issue before I went to .7 yesterday. No idea that this would have worked on .63b.
Thanks man for helping me eliminate the LDAP or FreeRadius as the issue since these had passed with other test tools.
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
Device: Galaxy S3
ROM: Slimkat
ROM version: Slim-4.4.4.build.6-OFFICIAL-5242
Build: slim_d2lte-userdebug 4.4.4 KTU84P 5242 test-keys
Kernel: 3.4.95-cyanogenmod-gd56ed95
I purchased my S3 in April of last year (4.1 Jellybean), and at the time the wifi worked perfectly. After the first (or second?) OTA that was pushed to my device, my wifi started acting up. It would cut out and I would have to cycle the wifi off and back on in hopes it would work again. I have been patient hoping they would push an OTA that would finally fix it. A year or so and a few OTA (I don't recall how many, or which versions) later and it still doesn't work properly, so I decided to finally try a custom rom to see if it would solve the issue. The last stock version of android I was using was the 4.4.2 OTA.
I rooted my device using towelroot, flashed CWM Recovery (CWM_6.0.4.7_Non-Touch_GT-I9300) using ODIN 3.04, then proceeded to flash the Slimkat rom listed above using CWM recovery. The wifi seems to be better, but it still cuts out and is unresponsive even though it says I have full wifi signal. A wifi cycle seems to fix it temporarily, but I'd like to solve this issue.
So as far as I can tell the last working modem I had was stock 4.1 or so. So I guess my question is, can I flash previous modems to try to get a working one with this rom? I have tried using WIFI Fixer from play store, and even with full signal on WIFI I get signal poor, signal hop scan messages spammed. Any and all help would be greatly appreciated!