Hey there, so I recently upgraded from cleanrom 5.0 (android 4.0.4) to Android 4.2 on a number of different ROMS, (Cleanrom JB, AOKP JB, VIPER XL, CM 10 Nightlies both unofficial and official and so far, none of them recognize my D-Link Router in the wifi settings.
While on Ice Cream sandwich my wifi would work just fine. Ive tried just about everything, Full wipes of everything even the SD card. I factory reset before each new ROM, I flash the boot.img for each one as well.
Ive tried messing with my router settings and switching through all security types, as well as powercycling the router and fixing the permissions via recovery.
I don't really know what else I can do and not having wifi working is kind of terrible. Anyone know what I can do remedy this?
S-off (very important), and then run the 3.18 ruu. There is some sort of incompatibility in earlier firmware and the new JB base that causes wifi to go haywire for some people. I was getting reboots because of it, and upgrading phone-wide solved it.
iElvis said:
S-off (very important), and then run the 3.18 ruu. There is some sort of incompatibility in earlier firmware and the new JB base that causes wifi to go haywire for some people. I was getting reboots because of it, and upgrading phone-wide solved it.
Click to expand...
Click to collapse
After much trouble I was able to get S-OFF and I ran the 3.18 RUU I found here:
http://forum.xda-developers.com/showthread.php?p=37227608
Still nothing. Ive wiped and flashed numerous ROMs both Sense and non. Not really sure what else to do at this point.
i have having the exact same problem as you do, have you try a custom kernel?
right now i am running HatkaXL 4.4.0 with Elementalx 5.4 the phone connects to my dlink router much faster than before, but still cant compare to ICS roms.
I'm not able to use any AOSP 4.2 ROMS due to having an AT&T router, I'm guessing it being due to WPA2. The phone simply refuses to connect. I just use stock rooted OTA roms. The teams need to fix this problem, I'm sure there's not much you can do, sorry.
It's not due to WPA2. Try setting WPA algorithm to AES only. Worse comes to worse. Just buy a new router and bridge your ****ty AT&T router.
And for the record this is an issue with 4.2 and nothing to do with the Devs on XDA
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
claudiuslu2011 said:
i have having the exact same problem as you do, have you try a custom kernel?
right now i am running HatkaXL 4.4.0 with Elementalx 5.4 the phone connects to my dlink router much faster than before, but still cant compare to ICS roms.
Click to expand...
Click to collapse
As for your slow connection, try flashing other radios and testing. Stick with the one that gives the best speed
exad said:
It's not due to WPA2. Try setting WPA algorithm to AES only. Worse comes to worse. Just buy a new router and bridge your ****ty AT&T router.
And for the record this is an issue with 4.2 and nothing to do with the Devs on XDA
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
As for your slow connection, try flashing other radios and testing. Stick with the one that gives the best speed
Click to expand...
Click to collapse
I like the way you think exad. I was going to write this but you beat me to the punch. Lol.
Figure out what's wrong with your router config first. That was my problem and it's probably yours too.
Sent from my HTC One X
Related
Hi,
Yesterday sudelly my wifi and BT isn't working, Wifi giving me "error" when I am tring to enable it.
Today I flashed a new kernel with a new ROM and it is still not working.
I tried to use Wifix manager and it didn't help either.
Anyone one got any idea what to do?
I am currently running CM10 by Kang rom and his kernel.
I'm not to familiar with that rom but have you tried to do a clean install with full wipe? I'm running jelly bean too but different rom and was having Wi-Fi problems it just would not connect. So I did a full wipe and another clean install then it started working perfectly for me. It' couldn't hurt to try. Hope this helps. It worked for me. Best wishes
Sent from my HTC Sensation
I wiped everything from the recovery and installed new rom.
Did you have the problem with the masseage "error" on wifi?
Mine kept saying "connecting" but never connected. It just kept connecting over and over. But would not actually connect. After I wiped again and did another install it connected without a problem however I never got a message actually saying "error".by chance have you tired another rom to see if it connects ? Could be rom related? Maybe try another rom and see if the error continues to appear?
Or is this happening on all roms you install?
Sent from my HTC Sensation
First I tried to reinstall my old rom and still didn't worked but now I tested with different rom and still having that issue.
I hope its not an hardware problem.
Have you tried wifix? I believe you can download from here it might help.
Sent from my HTC Sensation
---------- Post added at 09:32 AM ---------- Previous post was at 09:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1445766 here is link with instructions. Hope this helps
Sent from my HTC Sensation
Tried and didn't help me.
astd said:
Hi,
Yesterday sudelly my wifi and BT isn't working, Wifi giving me "error" when I am tring to enable it.
Today I flashed a new kernel with a new ROM and it is still not working.
I tried to use Wifix manager and it didn't help either.
Anyone one got any idea what to do?
I am currently running CM10 by Kang rom and his kernel.
Click to expand...
Click to collapse
Im having same problem! But in JB roms my BT IS working so I think its not hardware problem coz BT and WIFI are on same chip. And more and more ppl are getting this problem and looks like no one can help us. So pls DEVS help us somehow .
Anyone might know the answer for this?
Could be a hardware issue. It's happening on my phone too, and i've flashed several roms.
This occured right after I dropped by my phone, and since it's both BT and Wifi, which the antenna's are located in the same relative area on the phone - i'd assume that's the issue.
Here's the odin tar for the new jellybean release
http://hotfile.com/dl/204016374/8aa...m-SGH-T699-TMB-T699UVBMC5-1363439562.zip.html
I should have a tethering fix and a flashable modem (for people on cyanogenmod) out by tomorrow
nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?
Braccoz said:
nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?
Click to expand...
Click to collapse
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.
Jax184 said:
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.
Click to expand...
Click to collapse
awesome, i'll wait for the tethering fix then
I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?
I've been using the new JB ROM for a few hours now and have found a quirk or two.
When manually adjusting the brightness, sometimes the screen takes on a blue tint. Like, things that should be a dark blue become much brighter. This goes away if I tweak the brightness back and forth a few times.
I rooted the ROM using the CWM+flashable root file from previous ROMs. It worked, though last night I kept getting "radio is requesting superuser access" until I restarted the phone. I don't know what that was about. Hopefully it doesn't happen again.
The compass is STILL misconfigured. Every time you boot the phone, it needs to be recalibrated before it has any idea which way is up or north.
burbs said:
I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?
Click to expand...
Click to collapse
No idea what you mean. Got a picture?
---------- Post added at 12:48 PM ---------- Previous post was at 12:12 PM ----------
Okay, so we may have something a little deeper here. Today I'm seeing the "radio is requesting Superuser permissions" dialog again and again. I'm unsure what this means, but as a wild-ass guess, it may be the ROM checking to see if the phone has been rooted. This could be bad for people out there who still have their warranties.
I can't seem to get a screen shot, but it's like what you'd expect the hard drive LED to do when accessing data. I've looked up different "solutions" through Google, and it seems to be a developer's mode attribute, but I turned it off. One person says to uncheck the strict mode setting, which hasn't worked.
Well, whatever it was, it's done doing its thing now. As the day went on, the red flashing border appeared with less frequency. Throughout this morning I didn't experience it at all. Maybe it was some type of optimization thing going on?
Tethering
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
conspirator.of.crisis said:
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
Click to expand...
Click to collapse
I'm waiting on tethering as well.
Jax184 said:
I'm waiting on tethering as well.
Click to expand...
Click to collapse
Thanks - I just wanted to make sure I wasn't missing something - guess that means I'm going back down to LJ1 until we get tethering!
---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------
Now I'm in trouble - I got distracted while trying to go back to LJ1 and ended up applying the LJ1 tethering fix to the JB ROM. Phone rebooted and got stuck on the screen with SAMSUNG with the pulsating blue background and just wouldn't go further. Got back in through ODIN and flashed back down to the LJ1 ROM but again when the phone reboots it is still stuck on the same screen. Did I just brick it? Anyone got any suggestions as to how I can get back up and running on *ANY* ROM?
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
The only reason to downgrade though for me is that I need to tether. Hence faced with this problem I started going through all the Wifi Tether apps (that I tried before the tethering patch was out for the previous versions and none worked) and discovered the FoxFi works. It seems to override the T-Mobile tethering restriction in that when it is active the normal Mobile Hotspot icon appears (as well as the FoxFi icon) in the notification bar and when you pull it up it shows as On with the devices connected listed. Using FoxFi isn't as elegant as just using the built-in software hence I'll hobble along with the new image and FoxFi but still hopes that someone is kind enough and smart enough to figure out a tethering fix for this image.
Anyone got any comments or suggestions?
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors
gee one said:
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors
Click to expand...
Click to collapse
Wouldn't this help?
http://forum.xda-developers.com/showthread.php?p=40591848#post40591848
That is the full rom, I was looking for the actual OTA update because I wanted to look at the updater-script.
Here it is:
http://rapidshare.com/files/1683651545/update_mc5_7bda365f.zip
7bda365f9db8d24235b22787ed0c560c update_mc5_7bda365f.zip
Does GPS work on the new stock rom for you guys?
conspirator.of.crisis said:
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
Click to expand...
Click to collapse
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
I'm having some gps issues and radio is requesting superuser access. This is on rooted,debloated jb with the jb radio.
Let me know if you need logs, data, or want me to flash something.
sent while running with scissors
JB downgrade to ICS + GPS
Thanks for the info Nardholio! I guess that means I'm staying at JB then. Overall I'm happy with it and having no problems perse. However to address your specific comment about GPS, although I haven't had any issues with it I have noticed that it has taken up to 5 minutes to fully sync and get a position lock now. I hadn't attributed that to the upgrade necessarily though as this happens from time to time as being way up here in Calgary Alberta sometimes satellites aren't as easily visible as they could be and this happens occassionally with all of my GPS receivers. My old G2 used to have quite a lot of problems that way. Haven't noticed anything about root requests though as Gee One indicated.
Nardholio said:
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
Click to expand...
Click to collapse
does making a cwm backup cover that, and all other stuff needed too?
Hi Guys.. I own an T-Mobile branded HTC One S with the S4 processor.
Here's the problem: I can't connect to Wi-Fi at my job... and only at my job. I can connect at home just fine with my personal router, and just about everywhere else. What's interesting to note though is that I only can't connect when using an AOSP/AOKP-based ROM and also when using the latest STOCK T-Mobile USA Jellybean ROM.
The phone can connect from both at work and at home when running stock ICS and when running ViperROM 2.0, which I believe is based on the European JB update, not the American one.
At work, we have these Cisco MERU wireless access points throughout the building. The phone can pick up the SSID (we have two SSID's actually; one for guests and one for corporate) but I can't connect to either one. When I try to connect, the phone says "Scanning, Connecting to ..., Disconnected" and just loops. If I go into the more detailed Wi-Fi view, I see the name of the SSID I am trying to connect to, and underneath it says "Saved, Secured." Eventually it changes from "Saved, Secured" to "Authentication Problem."
I actually work in two seperate buildings that both have these Cisco MERU access points, and both buildings give me the same problem. They are using WPA2-AES
I have tinkered and tinkered for weeks now, and eventually lost SuperCID and S-OFF. I thought I could fix the problem by going back to stock everything. Little did I know that upgrading to the latest T-Mobile USA JB would no longer allow you to S-OFF and SuperCID. Anyway, even on this latest stock ROM, I can't connect at work. Like I said, I could only connect when I was on ICS or on a European JB ROM.
Just for a little background, this isnt the same Wi-Fi problem everyone else is having where they need to flash the "extra JB partitions" zip file or the "Archive.zip" file floating around. Even the "temporary radio installer.zip" doesnt solve this.
Is there any way at all that I can extract the Wi-Fi "drivers" from ViperROM 2.0 and install them on my phone for use with the latest USA JB ROM???
Here are my phone stats by the way:
VLE PVT SHIP S-ON RL
HBOOT-2.15.000
RADIO-1.13.50.05.31
And I am running the latest T-Mobile USA Jellybean stock ROM which I got from using the latest RUU. (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2)
I would really, really, really appreciate any feedback from someone a lot smarter than I am. I know I typed a ton.
It seems like there's some kind of Wi-Fi "security protocol"(for lack of a better term) or what-not that this latest JB update doesn't support. For some reason ICS supported it, but the American JB and AOSP/AOKP do not. I obviously can't change what kind of security the Wi-Fi at my job uses, so I'm really thinking there must be a way to just copy the Wi-Fi "drivers" (for lack of a better term) from ICS or from ViperROM and put them on my phone.
Does anyone know how to do this? Is this even possible? I read something about /etc/lib and something involving .ko files, but I would just like someone with a little more expertise than myself to chime in.
In case anyone is actually curious(I doubt it) I at least made SOME progress. I can now get Wi-Fi to work on Sense-based roms that are based on the latest T-Mobile USA Jellybean OTA. Here's what I had to do:
S-OFF'd my device using "Moonshine" method (THANK YOU THANK YOU!!!!!)
1. Flashed ViperROM 2,2
1. Using "Root Explorer" app I copied every file in /system/lib/modules folder from ViperROM 2.2 and put them on my SD card.
2. Flashed "United Basics" ROM (based on JB OTA)
3. Confirmed that Wi-Fi was working at home, but not at work.
4. Copied all of the modules from Viper to /system/lib/modules and overwrote everything using "Root Explorer"
5. Rebooted into recovery.
6. Flashed "Sense-Radio-Installer-v6.zip" from this thread: http://forum.xda-developers.com/showthread.php?t=1998270 and made sure I selected the checkbox for "Sense Wi-Fi fix" (it's selected by default)
7. Rebooted back into system and bam... Wi-Fi now works perfectly.
Flashing the "sense radio installer" alone was not able to fix the problem; you have to copy those modules first. Now I just need a similar method to get this to work on AOSP/AOKP roms.
xsytrance said:
Hi Guys.. I own an T-Mobile branded HTC One S with the S4 processor.
Here's the problem: I can't connect to Wi-Fi at my job... and only at my job. I can connect at home just fine with my personal router, and just about everywhere else. What's interesting to note though is that I only can't connect when using an AOSP/AOKP-based ROM and also when using the latest STOCK T-Mobile USA Jellybean ROM.
The phone can connect from both at work and at home when running stock ICS and when running ViperROM 2.0, which I believe is based on the European JB update, not the American one.
At work, we have these Cisco MERU wireless access points throughout the building. The phone can pick up the SSID (we have two SSID's actually; one for guests and one for corporate) but I can't connect to either one. When I try to connect, the phone says "Scanning, Connecting to ..., Disconnected" and just loops. If I go into the more detailed Wi-Fi view, I see the name of the SSID I am trying to connect to, and underneath it says "Saved, Secured." Eventually it changes from "Saved, Secured" to "Authentication Problem."
I actually work in two seperate buildings that both have these Cisco MERU access points, and both buildings give me the same problem. They are using WPA2-AES
I have tinkered and tinkered for weeks now, and eventually lost SuperCID and S-OFF. I thought I could fix the problem by going back to stock everything. Little did I know that upgrading to the latest T-Mobile USA JB would no longer allow you to S-OFF and SuperCID. Anyway, even on this latest stock ROM, I can't connect at work. Like I said, I could only connect when I was on ICS or on a European JB ROM.
Just for a little background, this isnt the same Wi-Fi problem everyone else is having where they need to flash the "extra JB partitions" zip file or the "Archive.zip" file floating around. Even the "temporary radio installer.zip" doesnt solve this.
Is there any way at all that I can extract the Wi-Fi "drivers" from ViperROM 2.0 and install them on my phone for use with the latest USA JB ROM???
Here are my phone stats by the way:
VLE PVT SHIP S-ON RL
HBOOT-2.15.000
RADIO-1.13.50.05.31
And I am running the latest T-Mobile USA Jellybean stock ROM which I got from using the latest RUU. (RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2)
I would really, really, really appreciate any feedback from someone a lot smarter than I am. I know I typed a ton.
Click to expand...
Click to collapse
Just flash this and voila!!
vatsaman said:
Just flash this and voila!!
Click to expand...
Click to collapse
is that for AOSP/AOKP?????
vatsaman said:
Just flash this and voila!!
Click to expand...
Click to collapse
First, I just want to thank you for taking time out to read this thread and offer a solution. Unfortunately, flashing that zip file didn't work. As a matter of fact, after flashing it, I can't even turn Wi-Fi on at all anymore. I tried flashing it in the Xperia Z ROM by Taylor_Swift and Dark Jelly S Edition Build 31. In both cases, I couldn't turn Wi-Fi on anymore after flashing your zip. But thank you for trying.
xsytrance said:
First, I just want to thank you for taking time out to read this thread and offer a solution. Unfortunately, flashing that zip file didn't work. As a matter of fact, after flashing it, I can't even turn Wi-Fi on at all anymore. I tried flashing it in the Xperia Z ROM by Taylor_Swift and Dark Jelly S Edition Build 31. In both cases, I couldn't turn Wi-Fi on anymore after flashing your zip. But thank you for trying.
Click to expand...
Click to collapse
Oops!! You mentioned that you are on stock ROM! So, that fix is intended to work ONLY on Stock or Sense based ROMs.
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
xsytrance said:
is that for AOSP/AOKP?????
Click to expand...
Click to collapse
Try it on stock and report.
vatsaman said:
Oops!! You mentioned that you are on stock ROM! So, that fix is intended to work ONLY on Stock or Sense based ROMs.
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
Try it on stock and report.
Click to expand...
Click to collapse
Oh OK. In my latest update, I mentioned that I already found a fix for stock/Sense-based ROMs. I am now looking for a fix for any non-Sense ROMs. I tried the "temporary-radio-installer but that doesn't do it.
I did manage to find ONE non-Sense ROM where the Wi-Fi actually works at my job. It's a ROM called "liquid_ville-ics-eng.v1.5mr1"
I am trying to see if I can somehow copy some files from that ROM to get my job's Wi-Fi working on other, newer non-Sense ROMs. That ROM is ICS-based and so is a little too outdated for me.
Thanks again, though. At least you tried.
I'm at then end of my rope troubleshooting this... maybe someone can help me out. I don't think this could possibly be a hardware problem, but I can't find a software solution.
The problem:
I can connect to WEP and open wifi networks without any problems.
However, when I connect to a WPA/WPA2 network, the connection either fails to transmit data immediately, or dies out over the first few minutes. It stays "connected", but can't send or receive data.
Diagnosis:
It started around the fall of last year when I was on the Infused v2.2.3 ROM. Both my home and work wifi networks started having the same issue, and both are on WPA2.
I tried a new router at home and had the same issue with WPA2.
I messed around with the home network trying to troubleshoot different settings and discovered that WEP worked fine. I can also connect to open hotel and coffeehouse networks without any issues. I did it on my vacation and didn't have any issues.
Troubleshooting
I used this problem as an excuse to upgrade to JB. A new kernel and ROM flash ought to fix the issue, right?
Nope. Same problem on both CM10 and SlimBean ROMs.
I didn't like JB, so I Odin'd back to stock and loaded Infused 2.2.3 again. Same problem.
I figured it must be something in the kernel... so I flashed the CWM Community voodoo kernel v8. Same issue!
Could this problem be caused by hardware in the phone? I didn't think it could...
Despite all these flashes, and the Odin wipe, could some lingering thing be staying on my phone in a folder I don't know about that could cause this through all these changes?
When I search for this issue, I find people with other Android models having the problem, but never solutions... or people with laptops who fixed it by upgrading their drivers. Drivers are in the kernel, right? So a reflash should fix that?
Is there a log file I should look at or something?
You can try flashing a new modem. Here is list of BML modems. They'll work for most roms that are ICS and below. And here is a list of MTD modems. You should use these for all JB roms and some ICS roms (depending on the file system). The modems were put into CWM flashable packages. Good luck!
jkakkanad said:
You can try flashing a new modem. Here is list of BML modems. They'll work for most roms that are ICS and below. And here is a list of MTD modems. You should use these for all JB roms and some ICS roms (depending on the file system). The modems were put into CWM flashable packages. Good luck!
Click to expand...
Click to collapse
No offense but another modem won't help him at all.
Sent from my SGH-I997 using xda premium
FauxAffliction said:
No offense but another modem won't help him at all.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
None taken. And sorry to the OP for sending you down the wrong road. Scott.hart.bti has been working hard on the Infuse kernel and there have been some recent changes. Check out some of his roms if you haven't yet. The wifi drivers may have been updated in his recent releases.
FauxAffliction said:
No offense but another modem won't help him at all.
Click to expand...
Click to collapse
Any idea what might help? Can you recommend a newer Gingerbread/Samsung kernel I could try?
AtomicCEO said:
Any idea what might help? Can you recommend a newer Gingerbread/Samsung kernel I could try?
Click to expand...
Click to collapse
You say you've odined...have you also repartitioned your phone? Go here and try that if you haven't.
Assuming sure you have Already factory reset your phone and wiped it clean,
It sounds like it might be a router issue
Things to Try:
1. On the router, dhcp release..renew..change the lease time
2. Reset the router and set it up again..you may have to do this twice..thrice.
3. New router at home
For some reason, certain wifi doesn't play nice with i997.
Maybe sure you Reset and wipe your phone if you want to make sure no traces of older connection causing issue with new
Might not hurt to take out any micro sd card while testing
Gl
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?