Related
....if this specific question....very specific question....was already answered...
I can't stay connected to a 4g network. My evo will connect to 4g, stay on for 10 secs, and then disconnect. Then I have to manually reconnect, and the entire process repeats. Before you go passing judgement please read the following:
- I've used terminal emulator to make sure my WiMax Mac is correct.
- I'm using radio 2.15.00.09.01
- Installed a stock version of the OTA 3.29.651.5 and rooted it using this thread: [Guide] How to apply the new OTA 3.29.651.5 when you have clockwork and s-off (sorry can't post links yet)
- WiMax radio is 26023
- PRI is 1.77_oo0
- PRL is 60670
I read something about increasing the timout reconnect from 10 to 300 in another thread that I have bookmarked.
My question is this
Is this the normal function of the WiMax code or does this have something to do with the rooted rom I installed?
Is the only way to fix this done by changing the timeout value mentioned before?
Once again, I will blow my head off if this has been answered before.
Thanks
Shouldn't have anything to do with the rom. Have you ever been able to connect (and stay connected) to 4g? Are you in an "official" 4g area? from what I've seen, the disconnect issues you're describing are normal in areas where they're still rolling out 4g, but it isn't fully up and running yet.
You can also try renaming the xxxx.tree.xml file in /data/misc/wimax/ while the wimax is off, and letting it rebuild the xml file again the next time you turn 4g on - but I think this only helps for the constantly scanning issues. Note that you're renaming that file (instead of deleting it completely) so you can go back to it if you run into any issues.
Sent from my blah blah blah blah
there is a thread in the dev sectin on how to change your 4g connection timeout. One simple thing you can try is to update your profile in software updates.
If people had more useful thread titles, don't you agree that it would be easier to search them?
Might have to blow my head off......
rutter9 said:
there is a thread in the dev sectin on how to change your 4g connection timeout. One simple thing you can try is to update your profile in software updates.
Click to expand...
Click to collapse
Thanks for responding....I've already updated my profile and I know about the 4G connection timeout thread.
I mentioned in my original question I already have that thread bookmarked (not tyring to be a ****, didn't know if you caught that).
fachadick said:
Shouldn't have anything to do with the rom. Have you ever been able to connect (and stay connected) to 4g? Are you in an "official" 4g area? from what I've seen, the disconnect issues you're describing are normal in areas where they're still rolling out 4g, but it isn't fully up and running yet.
You can also try renaming the xxxx.tree.xml file in /data/misc/wimax/ while the wimax is off, and letting it rebuild the xml file again the next time you turn 4g on - but I think this only helps for the constantly scanning issues. Note that you're renaming that file (instead of deleting it completely) so you can go back to it if you run into any issues.
Sent from my blah blah blah blah
Click to expand...
Click to collapse
I have never been able to connect and stay connected to 4G.....but I'm not really aware of any official 4G areas around here. I live in north jersey as well.
I picked up a strong 4G signal by coincidence while near the border of two towns (Clifton and Passaic....not sure if you're familiar with them) and that was when I started experiencing the disconnect/manual-reconnect issues.
I never connected to a 4G network before I rooted my phone because I could never get a signal. It was only until recently, after I rooted, that I've only been able to connect semi-successfully. I tried a good 10 times with the same results.
i.e.
I'd get a strong signal, do a speed test (which was blistering at 8577/1049 on the first try and 7699/1020 the second), and then let the phone sit idle. It will always disconnect, but I have no problems whatsoever manually reconnecting.
My confusion was whether or not this was common for people who have stock, non-rooted, clean as your baby sister's "you know what" Evos when trying to connect to a non-official 4G network, or is something wrong with how I rooted/the rom I used/whatever. Should I have to manually reconnect? Should the phone automatically disconnect from the 4G and go to 3G after a certain idle time? Should the phone automatically use 4G as the main connect if I have the WiMax radio on and the signal is really strong?
I assume I'm connecting to a non-official 4G signal.
Don't get me wrong I enjoy modding anything that has a circuitboard, but keeping up with all the issues can be a little annoying. Being a novice coder, this platform (new to Android) doesn't seem to be to complicated and I'm learning quickly. I have a spare PS3 sitting in my closet still running YDL. You used to be able to install an addtional OS on the PS3 before Sony got pissed because people were f***in up their PS3's. Sony "forced" an update that removed the ability to install another OS on the system, and the update actually wiped-out any other OS you had already installed. I put YDL on the PS3 so I could run NES/SNES/Genesis roms.
Back on topic, and to make a long story short (waaaaaaaaaaayyyyyy to late for that I guess), I'm just wondering whether or not my phone is working as it should.
Like I said, the phone connects...I do some stuff like a speed test....then disconnects automatically. Then I get a 4G notificiation in the main Android notification pull-down menu....and re-connect manually. The 4G signal is really strong, not sure if it's official.
Thanks for responding btw, I really appreciate your comments and I'll check out what this tree.xml file is all about. I understand the annoyance though. Not only is it annoying to have multiple threads all talking about the same thing, programmatically it's extremely inefficient and redundant.
Hence, if this question has been asked, I'll blow my head off with a 12 guage.
yes...agreed....but
Minjin said:
If people had more useful thread titles, don't you agree that it would be easier to search them?
Click to expand...
Click to collapse
sometimes getting good advice comes with grabbing attention from the right person. I've elicited an informative response from a couple other members. I thank them for being helpful to someone new.
can't I change the title of my own thread later on?
EDIT: An as soon as I changed the title, views dropped dead...cause I knew a title with good keywords would get no attention.
And you've ensured that while YOU may get advice and a solution, no one in the future will be able to use that same advice because this thread isn't likely to show up in a proper search.
Also, how many people know the answer but don't click on threads with titles as useless as this one? I would bet far more than who would click on it.
This is just basic forum etiquette, not anything unique to XDA.
Minjin said:
If people had more useful thread titles, don't you agree that it would be easier to search them?
Click to expand...
Click to collapse
This.
10char
Minjin said:
And you've ensured that while YOU may get advice and a solution, no one in the future will be able to use that same advice because this thread isn't likely to show up in a proper search.
Also, how many people know the answer but don't click on threads with titles as useless as this one? I would bet far more than who would click on it.
This is just basic forum etiquette, not anything unique to XDA.
Click to expand...
Click to collapse
......you are correct....I understand....that is why I'm going to change the title of the thread. Are you looking for me to say I'm sorry or something?
correct me if I'm wrong, but the site also indexes the content of the message as well. I'm very familiar with SEO and understand that a lot of indexing logic places heavy emphasis on the title of the thread, but the keywords in the content of the page also have a lot to do with how the thread pages get indexed. It doesn't solely rely on the title.
Just to put this to an end, I'm sorry for titling this thread as such?
Now, any thoughts on the actual question that I posted or are you going to stay mad at me forever?
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?
If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.
movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while
Noob post incoming. I did my best to search around and didn't find much. Hate creating a new thread but was locked out from posting in CM dev thread for obvious reasons. Not too experienced in the world of root, so forgive my ignorance. This will hopefully be a quick question:
I've tried running the CM nightlies for the last two days on my T-Mobile M8, and the only big problem is a complete lack of cell data. It displays that I have bars, and while it cuts in and out often (which I expect), I can't get a drop of data to go through. Even at full bars.
I've seen a few people mention connection issues, but didn't see anyone saying anything about a complete lack of cell data. I'd normally just chalk it up to being a nightly build issue, but since I can't find it mentioned elsewhere, I'm wondering if maybe I'm just doing something wrong. If not, no worries, but I'd be stoked if I can run it as a daily at the moment.
Anyone have any advice on what I might be doing wrong, or how I can resolve it?
Edit:
Chrome itself displays error that "Wi-Fi and mobile data are turned off" when only wifi is turned off.
I just tested calling and SMS and both are working with Wi-Fi off. So obviously I'm maintaining some type of radio connection.
Thanks a ton in advance!
New nightly. Same problems.
Bump.
@thefunkyprimer
I just got your PM. Unfortunately I know nothing about T-Mobile and/or why you would be having the issues. What have you tried? Switching APNs? Switching from 3G to 4G? I also haven't run CM longer than five minutes in a couple years. So I'm not much use in terms of running it personally.
Try my ROM and see if data works for you. That's pretty much all I got for you at the moment. But if you did try my ROM and data works, that might be a starting point. Make sure to fully wipe your device prior to flashing.
Anyone seen the firmware for the M9 that supports Marshmallow ? It's definitely out there as some users are running Marshmallow ROMs....
Any leaks ? Any news on official release ?
Is this what you are looking for?
http://www.htc.com/us/support/htc-one-m9/news/
No, that's not for Verizon plus it's a full ROM/RUU.
Sent from my HTC6535LVW using Tapatalk
Yeah, I have been wondering the same thing. I figured something would have got leaked by now. Or at least some info...
Sent from my HTC One M9
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
hgoldner said:
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
Click to expand...
Click to collapse
Oops! Sorry...
I believe Marshmallow firmware is only out for the dev / WWE devices.
VZW will most likely be the last variant to the update to MM, so don't hold your breath waiting on it.
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
PrizmaticSmoke said:
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
Click to expand...
Click to collapse
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
The Venom team, and a few others, do have a test build for Verizon from HTC. However sharing this build would mean violating an agreement between said testers and HTC/Verizon. This, in turn, would mean no more early test builds would be released to them. This is not what any of us want.
You, and I, have Verizon M9's. We understand our devices are not the same as International/Developer... and thus we wait, patiently. Our turn will come.
hallstevenson said:
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
Click to expand...
Click to collapse
Yep there's an XDA thread, but it's over in the general M9 section, here ya go: http://forum.xda-developers.com/one-m9/development/rom-t3265048
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
So to confirm, Verizon is actually testing a marshmallow build?
Aganar said:
So to confirm, Verizon is actually testing a marshmallow build?
Click to expand...
Click to collapse
Of course. Have been for a while. No release date though.
PrizmaticSmoke said:
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
Click to expand...
Click to collapse
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
hallstevenson said:
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
Click to expand...
Click to collapse
Honestly everything is working great for me on the build from 01-08, nothing is broken that i can tell. Data, wi-fi, gps, bluetooth, camera, flashlight, SD card, calls, texts, all are good to go. I haven't tested IR blaster as I don't use it for anything. And you will not have advanced calling/VoLTE available as far as I'm aware. But all good otherwise. :good:
I did see another VZW user reporting some issues on the same build like not getting a GPS lock, and their network incorrectly showing as Sprint and losing service whenever they drop to 3g or 1x coverage. But I have not had any GPS issues myself, and can't speak to the coverage issue as I live and work in an area with pretty solid LTE coverage and have had no problems.
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
The 01/08 build is the one I have downloaded too.
Sent from my HTC6535LVW using Tapatalk
hallstevenson said:
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I never had a gps lock when I went from sense to aosp. That was my problem. Switching from LTE to 3g and 1x because of fringe coverage , and having it read sprint pcs was just odd. Other than that, it's a great rom
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
hallstevenson said:
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
Click to expand...
Click to collapse
locks super quick too. Once i went and flashed a sense rom, got my lock, then went back to aosp, all was good. Do me a favor, download 4g switcher from the play store (its got a red power button logo). Since your in good 4g coverage. in this app, goto the dropdown menu that lists the radio bands (CDMA/EVDO/GSM/WCDMA/LTE Auto is set by default) select CDMA auto (PRL) (this will force you into 3g mode). Then see if you see either 3107 or sprint PCS as your coverage. Then try to browse to a webpage or something on the 3g, i couldnt get data to work in that mode whatsoever. Then at least ill know if im sane. Thank you
Don't need an app for that - just dial "*#*#4636#*#*"
It shows "Sprint PCS" when I switch to 3G mode. I'm not going to chance any data roaming charges though... Sorry
Did you toggle Settings, Cellular Networks, Data roaming to 'on' ? It's off by default. That could be why you couldn't browse on 3G.