Hello,
My Note 2 was stock, and I decided to root it because I was having issues with the screen turning on and wifi sometimes not connecting. I used Odin to flash TWRP, installed a number of ROMs including Cyanogen and Liquidsmooth (currently on Liquidsmooth 3.2), and everything works fine now except that Wifi won't turn on.
I read that Kit Kat has caused wifi issues for some people, so I even downgraded to Jelly Bean (CM 10.2), but that did not seem to help. Does anyone know of any fixes for this or alternatively, any Lollipop ROMs that wouldn't have this problem?
[One thing I just noticed when I was double checking that I was on 4.4.4 was that the "About" menu shows my model number as GT-N7105 even though I downloaded the ROM for the SGH-t889. If that means I installed the wrong ROM, I can restore my backup of my stock ROM and start again if needed]
Thanks in advance.
Solved!
Just wanted to post that I figured out that if I install Liquidsmooth alone first, without adding google apps, the wifi worked. In fact, I may have just been stupid to install google apps since it appears that Liquidsmooth already had google apps...
But in any case, the wifi stopped working after I rebooted, so I installed Jedi ROM from here: http://forum.xda-developers.com/note-2-tmobile/development/rom-jedi-source-project-4-4-4-t2895948, booted up, then went to recovery and installed the google apps for Jedi from the same link, and everything has been working great since then.
Hope this info is helpful.
svetzy02 said:
Hello,
My Note 2 was stock, and I decided to root it because I was having issues with the screen turning on and wifi sometimes not connecting. I used Odin to flash TWRP, installed a number of ROMs including Cyanogen and Liquidsmooth (currently on Liquidsmooth 3.2), and everything works fine now except that Wifi won't turn on.
I read that Kit Kat has caused wifi issues for some people, so I even downgraded to Jelly Bean (CM 10.2), but that did not seem to help. Does anyone know of any fixes for this or alternatively, any Lollipop ROMs that wouldn't have this problem?
[One thing I just noticed when I was double checking that I was on 4.4.4 was that the "About" menu shows my model number as GT-N7105 even though I downloaded the ROM for the SGH-t889. If that means I installed the wrong ROM, I can restore my backup of my stock ROM and start again if needed]
Thanks in advance.
Click to expand...
Click to collapse
Related
Hi everybody,
For a while I had been running Wicked rom (version 7 and then 8) without any issues at all. Data was great, wifi was working, calls and texts were made perfectly. Not a single issue as far as I could see. GPS was working just the way I was expecting it to (I use my GPS for navigation on a weekly basis).
I've explored other roms as well and I've never encountered anything serious or out of the ordinary.
Now this problem has appeared recently. Ever since I flashed a 4.3 rom (Infamous V9), my GPS has stopped working. It keeps trying to lock but never does. I've left it on for a long time too, it never locked; It just keeps searching.
I've even tried apps I've seen suggested such as GPS status & toolbox. Nothing I've done with those apps have worked. When I went back to the wicked rom (version 8), gps still did not work. Prior to the Infamous v9 rom, I had flashed the Cyanogenmod 10.2 rom and the gps was fine.
Now, regardless of what I do, the GPS no longer works on any of the 4.2 or 4.3 roms I've flashed.
When I flashed VirginRom (android 4.4), I had no signal on my phone at all, but that was due to my modem. I followed the instructions to odin flash the new modem and everything worked! On that 4.4 rom, everything worked perfect. More importantly, the GPS was working again and I was able to use it for navigation when I went out. I tried to test out other 4.4 roms. I flashed the dandroid google edition and cyanogenmod 11 on this forum. Both of these roms worked perfectly. The GPS was working and it locked within a few seconds.
When I tried to go back to any of the 4.2 or 4.3 roms, the GPS still did not work, even though everything else was fine.
I'm not the techie type of person, compared to so many people on this wonderful forum. I just do my best to follow instructions and learn from what is done ><. Does anyone here know what the issue I'm experiencing is?
Just for some added info:
I guess it's obvious my model is SGH-M919
Baseband changed though. It used to be MDL. Now it's M919UVUEMK2.
Any help would be much appreciated! Thank you.
Have you tried the app faster fix app? Also, do you have Google maps and earth installed?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !
Hi,
- Stock (or custom) rom 4.4.2 works fine. Wifi turns on and connects.
- Stock (or custom) roms 4.4.3 and 4.4.4 hang on "Turning Wifi on..." and stay that way. (The rest seems to work normally).
I have the exact same issue with my Nexus 4, but my Nexus 7 (2012/grouper/nakasi) doesn't have any wifi issues.
Things I tried:
Complete factory resets, factory images flashed (KTU84L/P), flashed Carbon nightly (20140621).
Flashed the radio from and KOT49H factory image (there isn't one in KTU84L or KUT84P), flashed the bootloader(s) from the 4.4.2, 4.4.3 and 4.4.4.
I even tried deleting (or rather renaming) the /data/misc/wifi and /data/misc/dhcp just in case.
Router is not the problem, I already tried resetting it, despite all my other wifi enabled devices having no problems.
Nothing turns on the wifi on my Nexus 7 (flo/razor) or 4 (mako/occam) when on 4.4.3 or 4.4.4...
I am suspecting Google of screwing up, but if that was the case, why don't I see a whole bunch of posts with this problem?
I'm running out of ideas. The weirdest thing is that on 4.4.2 (stock and carbon last 4.4.2 nightly) it works like a charm! And even weirder, it happens on 2 or my 3 different Nexuses.
Which roms have you tried? I'm running Pac-Man 4.4.3 (6/19 nightly) w/elementix kernel and WiFi works just fine.
Sent from my Insane S4 via XDA App.
Saturny said:
Which roms have you tried? I'm running Pac-Man 4.4.3 (6/19 nightly) w/elementix kernel and WiFi works just fine.
Click to expand...
Click to collapse
That helped, sort of... ElementalX 2.13 doesn't work for me either, but 2.12 does!
I will test some more, but I'm considering staying on this combo for now until 4.4.4 (or maybe higher) matures a bit.
I still find it highly suspicious that Stock is giving problems too. I found a few comments on 4.4.3/4 release news posts on the net with this issue too.
I'm on 4.4.3 on Nexus 7 2013 (LTE) and mine does "Turning Wifi on..." hang every day. I reboot and the problem is sometimes fixed. If I reset my AP and then reboot the Wifi always works.
This is relatively new. I associated it with a newly installed App, Wifi Scheduler, but maybe its not the App.
Interesting.
Thanks for posting your question.
PS: I'm on AT&T prepaid SIM card, FYI.
PSS: I just had a problem with my PC network access, seems my DHCP router issued a duplicate IP address. Unsure if related.
Whatever the guys over at Carbon Rom did, it fixed my WiFi problems! Thread is Here.
They put some special fix in their rom. Nightly of the 24th has the fix. Those on a deb/lte will be fixed in tomorrow's nightly.
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Hope you are on latest 4.4.4 firmware , link for the same should be in OP/FAQ of Viper.
fandam said:
Hi I pretty much know nothing about custom roms etc but I was forced to go for a custom ROM due to a friend wiping my phone but when I flashed Viper 3.2.1 everything was fine except the wifi button was greyed out, I also tried android revolution and the same problem occured. However it was fine when i tried candy5 but once i flashed google play the wifi stopped working again.
Does anyone know what the problem is and how i should fix it? thanks.
Click to expand...
Click to collapse
If you are only unlocked and not s-off you will need to manually flash the corresponding boot.img for each rom each time you flash a new rom. If you can get s-off you won't need to do this anymore.
Firmware needs to be updated. Confirmed on OP's other thread here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bricked-t2989202/page2
Also its not necessary to manually extract and flash boot.img on the M8, even when s-on. Folks giving this advice may be carrying over knowledge from an older HTC device.
Reposted in the correct forum
Afternoon everyone, I was hoping someone could assist with this problem, I have a Galaxy Tab 3 7" wifi only, I was running everything as stock inc 4.1.2 firmware, then I was prompted for an upgrade to 4.4.2, I stupidly did this without reading up ! I use to run the Tomtom software on my tab, used it everyday for work, now since the upgrade the tab will not find a GPS signal, no matter how long I leave it, after a few hours of reading and trying different things, cache cleared, reinstalled the app, restore to stock twice (still on 4.4.2) Im at a loss. I have read once its upto 4.4.2 it cannot go back to 4.1.2 as the boot loader is locked ? I am currently downloading a clean instal from Samobile of 4.4.2 to see if that will fix it, installed via Odin 3.10.6.
If anyone has cured a similar problem or can point me in the right direction I would be most grateful
Thanks
John
sort of fixed
Couldn't seem able to find a fix for this problem I had a dabble with my Tablet, installed TWRP, backed up the 4.4.2 stock ROM, found and installed the ROM by Jon Wesley Tranchida - uber cool ROM btw - fantastic boot logo's :good: but alas, the Tablet would still not run the GPS with Tomtom. So I took a risk and found a Stock 4.1.2 ROM from here http://stockroms.webs.com/downloads deleted everything and started again, Installed the 4.1.2 Ultimate ROM, installed Tomtom again and YES, everything works okay :highfive: I really miss all the addons though that were included in the ROM by Jon Wesley Tranchida. I still don't understand why Tomtom won't see GPS or the tablet wont access the GPS on 4.4.2, after 10 hours of reading up.. Although I did read it could be some thing to do with the baseband ? its beyond me lol