Related
Like many others, my phone has a tendency to drop 3g unless I enable Data Roaming. This has been the case with My D1 with 2.3.3.
Now that I have the Droid 3, I have the same thing. No surprise there.
HOWEVER, when I enable Data roaming on my D3 and then go into an area where the phone drops to 1x then no data, I get a notification that Data connectivity has been lost because Data Roaming is Disabled.
If I pull down the notification bar, it says I can select the bar to go to the setting. I do. Sure enough, the Data Roaming Enable box is Unchecked.
I check the box. Go to my home screen, and the notification will reappear. I can do this all day.
If I go to my home screen, ignore the notification and go to settings, battery & data manager, then data delivery, the setting is unchecked....BUT....If I access the menu this way; the setting will be retained until the phone is brought to an area where data signal does the 3g to 1x to no signal thing. Then it starts all over again.
Any suggestions? Anyone else getting this? I received my D3 over a week ago, and finally exchanged the phone for another one. That phone lagged and had random freeze issues. This phone has none of those issues, but still has the Data Roaming Enable setting not retained problem.
Wasn't this an issue with CM7 at one point? The d3 claims to be running 2.3.4, but it is hard to tell with all the Motoskin draped over it.
I have also noticed that (in my area) if I have data roaming enabled, my battery life is much improved. With it off, my battery drops like a rock.
I have contacted Moto about the issue and reported the bug; but all I am getting is the "we'll look into it" brief email. Like I'm some kind of first-time Android user who doesn't know how to use my phone.
Please tell me someone out there is having this too, or that there is a patch that Moto just hasn't released yet....
Thanks in advance everyone.
UPDATE:
2nd phone, all data connection is lost. No phone, 1x or 3g. Phone is awake, and battery settings are set to Performance (No Battery Savings).
Data manager is disabled (no stoppage of data)
When going into an area where I ALWAYS had "EXTENDED NETWORK" data available at 1x speeds prior to this phone, the phone says no data connection.
I look and my Data Roaming Enabled checkbox has been unchecked.
I check the box, click OK to agree that I may incur Roaming charges. The phone will reconnect to data at 1x or 3g depending on where I am.
If I look at the phone 5 minutes later, the checkbox is Unchecked again for allow data roaming. Sometimes less.
This only happens after the phone goes into a weak coverage area.
I have tried rebooting the phone. The setting stays retained after reboot, but is lost as soon as I go into poor coverage.
I have tried factory reset. Setting stays until I reach a poor coverage area.
Already exchanged for another phone. Same issue.
Changed phone from Global to CDMA mode and network to automatic. Setting still does not hold.
It is most strange though, that it doesn't happen until after my home network is lost. The setting will hold until then.
Without that setting checked, I cannot connect to my "Extended Network", which in my area is a no-cost option. I keep checking the box, only I can't get the setting to stick when I go to a weak coverage area.
The coverage area should not make changes to the retention of allowing of data roaming checkbox. Something is improperly referenced in the software.
Motorola's out-of-country sweat-shop customer-no-service department wants me to ship my 2nd brand new phone to them (5-7 days for them to process and receive it+whatever it takes to ship to them) and take between 14-21 days to "repair" the phone, and then take another 5-7 days to package, ship and return to me (all at my expense). Why am I sending a new phone that is defective "out of the box" to be repaired??
So I'm supposed to go without my phone for 5 WEEKS because they have a software problem??? It can be duplicated every time, and on more than one phone. They have the old one. Fix that and send out the update please!!
Am I the only one that has had this issue? Seriously, no one else?
Any help would be greatly appreciated. This is frustrating as heck. I love the phone, but this is ridiculous and makes it rather un-usable depending on where I am. I NEVER had this with my D1! Moto, what happened?
Thanks everyone. +1 if you've had the issue please.
Same Problem
I also have this same problem.
After reading other forums, I thought it may just be the Droid 3 or a Motorola problem. I ended-up turning back in my Droid 3 after Motorola said it was a Verizon problem (which really is not the case). Now, after reading your thread, it makes me wonder if this is a Android OS issue.
I really hope it is not a OS issue, I have wanting an Android phone for a long time.
At my house it always kicks off the data roaming option. I really have no idea what is causing it.
Just wanted to post so that you know your not the only one!
Thank you.
I have run a logcat and have traced the problem to Motorola's battery and data manager service. It is not the OS itself, from what I can see.
It seems that under these particular conditions, the battery and data manager service crashes. Though this should not be a major problem in and of itself, though still not right and needs fixing there too. The service promptly restarts and then loads the settings that were enabled at the time of the crash from a secure data folder. (Or it's supposed to)
The problem comes into play when these settings are loaded. Enable Data Roaming is "loaded" as No(off) any time the service loads these values after a crash of the Battery and Data Manager service.
Unfortunately, as usual, Motorola is dragging their feet at releasing the source code for the Droid 3. This may or may not help the issue, as the Battery and Data Manager service that crashes is a part of Motoblur. Meaning, they aren't going to be forthcoming with the information.
They also are being a typical OEM in their refusal to believe that they could have made a mistake when programming and that they have something to fix.
My Droid 1 has run 2.3.3, 2.3.4, and 2.3.5 and this has NEVER been an issue keeping the setting retained. This is not an issue on our INC2, which is running 2.3.4 in all the same areas that cause my D3 phone to lose the setting. I am also running an Eris with 2.3.5 and it does not have the issue. This is strictly with the D3 from what I have seen.
It's funny how Moto is blaming Verizon for an issue they say doesn't exist. If there isn't a problem, how can that be the network's fault??? The network doesn't change that setting in the phone. Software changes it. In this case, poorly written software added onto the Android OS. Too bad, the OS works fine until Moto putzed with it (Blur).
The OS is not the issue here, it seems the D3 software has two problems:
1 the Battery and Data Manager service shouldn't crash like that.
2 it should return the proper settings if it does.
If I had the chance to do it all over again (knowing what I know now), I would have said send me an INC2 as a replacement. I honestly figured it was a phone hardware problem and the new phone (under warranty) would fix it.
Honestly, I am completely disappointed with this device. That may change when root is obtained and I can get rid of the poorly written trashware that seems to plague this phone. But right now I'm most disgusted with the fact that it doesn't work right and Motorola couldn't care less, even though it's their sofware that is the problem.
I have pruchased my last Motorola product, and am not holding my breath that Motorola will either care or fix their problem. I am certain the future rooted ROMs will be able to transform this lagtastic, glitch-ridden, battery pig into the elegant piece of hardware it has the potential of becoming.
Sorry Moto, sometimes the truth hurts.
Thanks for the support that it isn't only my phone or service area.
Others please +1 as you experience it. The issue is logcat documented and now confirmed on at least 4 devices.
Sent from my DROID3 using XDA Premium App
I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?
This is the response I received from Motorola. They need to get a move on with a fix for this huge goof up.
"Thank you for reaching out to Motorola.
We apologize for all the inconvenience and appreciate your patience. The Support Engineers have been made aware of the issue with the "Data Roaming" feature of the phone; and there are currently working on a possible resolution for a future update. You will need to manually change the roaming option back until fix is available. The Support Engineers have not provided an ETA on when this will be available.
If you have any additional questions or concerns please contact Customer Care at (800) 734-5870."
blkwlf said:
I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?
Click to expand...
Click to collapse
The latest developer update, which is currently in soak testing, has fixed the issue for me.
No formal release date yet on the over the air (ota) version's release date, but I would expect out in the next couple of weeks as long as everyone else had the same results I had with the test update.
Update will upgrade system version from 5.5.959 to 5.6.890, and the baseband radio will be updated at that time as well as the kernel.
So there does seem to be a fix, despite the terrible customer service at Motorola. Honestly, it sucks! I had this update last week, and I'm sure somebody knew this was intended to fix the problem. Not once has Moto asked for information or applied for releasing a phone that was not ready.
Instead, we got canned bot responses and the general feeling that Moto just doesn't care now that they have our money. It is really sad.
Lets hope Google can straighten it out.
Fingers crossed. Though now that we have root, and a custom recovery possibly by week's end; I could care less about Moto. My next phone won't be Motorola...fool me once, shame on you; fool me twice, shame on me.
Sent from my rooted, de-bloated, test-updated DROID3 using xda premium
wattnxt said:
The latest developer update, which is currently in soak testing, has fixed the issue for me.
Click to expand...
Click to collapse
I have also flashed to 5.6.890, re-rooted and de-bloated. So far, the new radio has done nothing to help my issues with the data roaming becoming disabled. Have you tested the new software under the same conditions as the old?
I may have to retract my last statement... my phone did auto disable the Data Roaming once after updating, but since then it has been fine. Hopefully the update truly did fix it!
Sent from my DROID3 using XDA App
I have purposely tried to get the setting to fail. Same result for me as you saw; I got the same old warning once and have not seen it again in over a week now.
For me this was huge, as it failed 20 plus times a day at work. All I had to do was walk down one specific corridor, and by the time I got to the other end my setting would have been unchecked. So going a week with it staying retained (in global mode too by the way) is monumental proof for me it is fixed.
Now I have seen this on the D2 global twice this last week. They don't have a fix yet either, but technically this one isn't official until it's pushed ota.
Good luck all. More news as I have it.
Sent from my DROID3 using xda premium
I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!
Baconstrip said:
I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!
Click to expand...
Click to collapse
So... do the update. You won't regret it
blkwlf said:
So... do the update. You won't regret it
Click to expand...
Click to collapse
I was thinking about it, but I was hoping to wait until it's officially released. Taking longer than I expected
Still happening in 5.6.890
I'm also suffering this very annoying problem, and have found no solution for it.
I'm using stock XT862 5.6.890 and I need to re-enable data roaming 20 times a day. I use a carrier in Spain that has very little owned towers so it's doing national roaming very often. Every time I switch from an owned tower to a roaming tower, I get the "Data roaming is disabled" notification and need to go to "Battery & data manager" -> "Data delivery" to re-enable it.
I have searched A LOT and tried all solutions I have seen, i.e. modifying build.prop in a myriad of ways, but it still happens.
I have also tried Minimoto v1.7 which has XT862 5.7.906 but it's even worse: It still happens but that ROM has stripped out Battery & data manager so I can't even enable Data roaming. A shame because the ROM is really awesome.
Please help a poor soul! :angel:
I finally took the problem in my own hands and managed to make a small app that re-enables data roaming at the touch of a button.
I needs to be installed as a system app for it to work, but it works! :laugh:
You can get it here http://forum.xda-developers.com/showthread.php?t=2165364
As some of you may have read, my phone is somewhat hosed.
I have a new one on the way (which might be a refurb). But I have nothing to lose playing with this one.
I highly suspect, one or more of the bands are disabled.
If you google around you see lots of folks fiddling around with Band Priorities and/or Enabling. Especially with "TirBand" phones (which this is). (Nexus 5 and HTC One, HTC One Max).
Most of the time people access this through EPST using ##4636# but my phone does not respond to this.
But the Galaxy S5 and HTC One (M8). Are in new Territory with Spark and even more bands I believe. So their might be new Menus for these phones and that info has not been leaked out yet.
Currently if I'm in a formally strong 4G area I get great 3G (no 4G at all). Yes 4G is enabled.
If I'm in Moderate to Weak 3G area. I get 1x or nothing. It really feels like a Band got shut off.
I'm not sure what caused it.
I was running Corporate PRL (56018). That seemed to not be causing any harm. Ran it for a few weeks.
Ran Barebones 1.0 (on stock firmware) and that ran fine too. After that it was down hill.
My only issue was Roaming Guard was on and Locked out. Which others have reported is a long standing issue (was a problem on M7 too).
All I needed to do was do a Full Wipe and enable it before it gets locked again. Not everyone has this locking issue, but MANY do.
I updated to OTA firmware. Not sure of status here because I had WIFI on normally.
Then I decided to run BadBoys Harman. Without firmware. Again not sure of status here as WIFI was on.
Somewhere I believe I did an Update Profile. I suspect at that point I was hosed.
It was when I put BadBoys on that I noticed an issue because he shows when you are on 1x.
Not sure if I started to see 1x that was before or after update profile.
I don't know if it's combination of having been on the corporate PRL when I did the update Profile or what.
I always try to do update Profile over mobile network.
I was not clear what the problem exactly was until I "Fully" upgraded (Harman with Harman firmware).
Just to be clear, I'm not blaming anyone but me. And there may be nothing wrong with anything out there than more or my phone. I just don't know.
I highly suspect it's something trivial that got turned off or the phone so happened to lose a band or antenna.
But I suspect it's some combination of SuperCID, Corporate PRL, new OTA Firmware or Harman Firmware along with Update Profile hosed me.
I do have new phone on the way. But I sure would like to know what happened.
I didn't do anything "out of bounds" from this forum. I simply may have done things in a different order or something.
I am S-OFF and running TWRP 2.7.0.2
I have reactivated, wiped the gazoo out of it. Ran Harmon RUU. etc.
I sure wish there was an RUU for the Shipped Config. Or even for the OTA version.
Seems a coincidence the phone "Broke" just when I started Flashing Firmware and Updating Profile.
I know I was good on Stock Rooted, S-OFF, Corporate PRL. Because I'd even see 4G at my house occasionally which is a reach. Now I'm lucky to get 1x at my house.
I will tell you this, I'm staying on Stock Firmware and Stock PRL when the new phone arrives until more is learned.
I will try to compare phones as best I can.
Which is another reason I sure would like to see the Band configuration on this phone so I can compare it to the new phone.
Thanks for any tips.
I think you were trying to do *#*#4636#*#* to access the Menu. The EPST command would be ##3282#.
I'd be interested in your comparison. I think I may have a hosed phone as well. I have it on cdma only and I'm constantly losing data, dropping calls, and missing calls in places I didn't before. The only roms I have flashed are Captain's 1.54.651.8, and my BareBones rom.
Captain_Throwback said:
I think you were trying to do *#*#4636#*#* to access the Menu. The EPST command would be ##3282#.
Click to expand...
Click to collapse
Thanks when I saw people posting *#*#4636#*#* I stupidly assumed they were trying to get past some HTML issue with ##. *#*#4636#*#* works !!
Turns out when you use the Google Play app called "Advanced Signal Status" when you click "Advanced" it brings up the same Menu as *#*#4636#*#*.
I didn't realize it was bringing up something built into the phone.
Any way,
It looks like on HTC Max it was *#*#3282#*#* which does not exist on HTC One (M8). You have to use ##3282# but that does not offer the same Band settings that HTC Max has with *#*#3282#*#*.
Just a quick reminder that Questions go in the Q&A section.
metalfan78 said:
I'd be interested in your comparison. I think I may have a hosed phone as well. I have it on cdma only and I'm constantly losing data, dropping calls, and missing calls in places I didn't before. The only roms I have flashed are Captain's 1.54.651.8, and my BareBones rom.
Click to expand...
Click to collapse
When and how often have you:
Updated Profile?
Changed Firmware?
Changed from factory PRL?
I think my problems may have started after I flashed Captains Firmware for OTA (which I got the link from you ROM thread).
I'm not saying it was, but it was around that time. It may have been something to do with PRL's but those are usually harmless and very revertible.
I'm 99% sure I was ok on your ROM with Stock Firmware. Except for Roaming Guard on and locked out. Not sure if that is an early symptom of problems though.
Some things in firmware (on past phones) are not revertible (ever !!!)
Your symptoms sound a lot like mine. I only get good 3G in locations where I used to get good 4G. And I get no 4G at all now.
My phone generally works but many calls go to voice mail or get dropped. Or end up being one way (one of us can't hear the other).
I think it's one of these:
Band issue (disabled or low priority)
Some sort of ID issue that got lost (like a lost security Key)
Some of Power Saver issue (i.e. Extreme Power Save kicking in when it shouldn't)
The reason I mention power is it does this.
WIFI On
Running "Advanced Signal Status"
All looks ok.
Shut off WIFI and things go nuts.
EVDO (data) RSSI Signal: drops to -120db (0%)
Then network type switches to 1xRTT from eHRPD.
It's like the extreme power saver is on. Which, guess what, OTA firmware was supposed to enable !!!
I have tried disabling it in settings. But I think something is haywire.
This is what extreme power save does. And came with the OTA update.
QUOTE: Basically it shuts down all connections but still allows phone calls and texts to come through. You can manually refresh e-mail if you want — but only in HTC's e-mail app. Your smartphone essentially is turned into a dumb phone. And to make sure you don't cheat and try to actually make it do things, the M8 gets a new home EXTREME home screen, with shortcuts to the Phone, Messages, Mail, Calendar and Calculator apps. To exit EXTREME mode, you'll need to hit the dedicated "Exit" button.
HTC says that with only 5 percent battery remaining, you can eke out 15 hours in this EXTREME mode. On a full battery? It'll last something like a dozen days. We'd consider this to be more of an emergency mode than EXTREME, however. END QUOTE
It sure feels like this is what my phone is doing. I think it's stuck on Extreme Power Save mode (in the RADIO only).
I flashed the firmware twice, updated prl many times, never changed prl. Sounds like same symptoms.
metalfan78 said:
I flashed the firmware twice, updated prl many times, never changed prl. Sounds like same symptoms.
Click to expand...
Click to collapse
I highly suspect it's not PRL. When you say "update prl" I assume you mean from settings -> system update menu.
I suspect firmware. Of which there is nothing available to go back to.
Can you get 4G?
I rarely get 4g, it hasn't been fully implemented where I am. I got it on my gs3 only sometimes. And yea, updated prl through settings
---------- Post added at 08:58 PM ---------- Previous post was at 08:18 PM ----------
I'm definitely going to a Sprint store. I was just on Sprint chat and they confirmed it is not network related but a defective device. Dammit.
This is what extreme power save.came with the OTA update.
HTC/Sprint removed the band priority section from the menus in the Max so it's either hidden deep OR it's not there and Sprint is controlling what band you actually use on their end which is highly possible....
Sent from my 831C using Tapatalk
sgt. slaughter said:
HTC/Sprint removed the band priority section from the menus in the Max so it's either hidden deep OR it's not there and Sprint is controlling what band you actually use on their end which is highly possible....
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Ahh, thanks for the info. I think that's what is messed up on my phone some how. Some Key or ID so it knows the appropriate ones to pick.
I've been switching back and forth on firmware and flashing mainly between Viper Rom and Bad Boyz H/K Rom without any issues at all. I had one issue where I couldn't get data or roam, I temporarily fixed by flashing some stock files, but since a clean install all has been well. I've updated profile and prl quite a few times without any issues so far.
I don't get lte at home, but it worked great in Indianapolis over last weekend. Just thought I would share the info.
Also s-off and super cid if that helps any.
dazednconfused said:
I've been switching back and forth on firmware and flashing mainly between Viper Rom and Bad Boyz H/K Rom without any issues at all. I had one issue where I couldn't get data or roam, I temporarily fixed by flashing some stock files, but since a clean install all has been well. I've updated profile and prl quite a few times without any issues so far.
I don't get lte at home, but it worked great in Indianapolis over last weekend. Just thought I would share the info.
Also s-off and super cid if that helps any.
Click to expand...
Click to collapse
That's interesting you lost Data / Roam and managed to got it back. Perhaps if I had put the dialer on like you did at that first problem I would have got it back too.
So you are running H/K firmware as well?
I've made it as close to stock as I could including recovery. Went to 4G area (where I can get 3G). Factory Reset (from boot loader), Redid Activation, Updated Profile/PRL etc. All worked (albeit slowly).
But still no 4G and no 3G when in normally 3G only areas.
Then I tried running H/K RUU back to back twice. Still stuck.
I may try RUU one more time, then try reactivate/profile/prl again in the 4G area.
Is there any need to change hboot? I have left what the H/K RUU put on there sometimes and other times used the one posted here that removes the red unlocked text etc.
The only thing I've messed with on hboot was the mask to remove the tampered text and red text on boot screen.
Yeah I was the one that sent you the message about losing mine until I flashed stock phone apk. But you said it didn't work for you though. But after I did a clean install of the Rom I haven't had any more issues luckily. Hopefully your replacement will work a lot better for you. Maybe just got a bad phone hopefully.
Yes I'm back on H/K firmware again. I went back to old firmware when I flashed viper a few days ago.
Sent from my 831C using XDA Premium 4 mobile app
dazednconfused said:
The only thing I've messed with on hboot was the mask to remove the tampered text and red text on boot screen.
Yeah I was the one that sent you the message about losing mine until I flashed stock phone apk. But you said it didn't work for you though. But after I did a clean install of the Rom I haven't had any more issues luckily. Hopefully your replacement will work a lot better for you. Maybe just got a bad phone hopefully.
Yes I'm back on H/K firmware again. I went back to old firmware when I flashed viper a few days ago.
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe I need a round of Viper to fix it
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
HueyT said:
Try to unlock bootloader, install TWRP, root the stock rom, then install lastest bootloader (v72.03) and latest radio (v05.45):
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Use WUG Fresh NRT tool to accomplish above when hooked to Windows PC via microUSB in 2.0 USB port with correct Windows drivers installed (OK for ADB): https://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
I'm already unlocked, rooted, TWRP'd and using the PureNexus that came out end of april (I haven't flashed the one in may yet). I believe I'm also currently using the latest radio and latest bootloader.
Edit - I actually was not on the most recent radio, but I did flash that, no change.
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Morpherios said:
Hell of a story, I apologize in advance for the length, but maybe it'll be intriguing to some of you. Pure Nexus rom as of i think april 23rd?
I have a Nexus 6 that I bought 2 years ago in April on Verizon (purchased from verizon). My contract ran out April 27th, went to AT&T with my girlfriend because I was going to get on her plan to save money on our phone bills. Ported over the number to my N6 fine. But I noticed I only got an H+ symbol, no LTE. I asked the guy if that was normal, he said yes. I got data and could make calls so I figured it was fine. Did some speed tests, 2 mb/down at best. My GF was getting 15-20 in the same spot on her Galaxy S7.
Long part of this story short, the tech they put me on the phone with said it was due to it being a Verizon variant and was not capable of full LTE speeds on AT&T. I went to the Verizon store and asked if they could put me back under Verizon after explaining the problem. He said sure, and then worked up pricing to have my GF switch to Verizon with me instead, and to get a Pixel XL.
So far so good, they had to do a temporary number for me because there's issues porting a number twice in a 24 hour span, but they cleared it up, got my real number ported, happy camper, good speeds. Except this one issue.
Now when I'm on the phone (actual phone call), my data drops. The LTE signal actually disappears, and nothing displays except signal bars. As soon as the phone call is over, it comes back. I never had the problem before this whole back and forth mess. I can't seem to figure out any options to make it not do this. I was thinking about reflashing my rom in case that would help, maybe something got messed up in the switch back and forth to GSM and then back to CDMA?
Click to expand...
Click to collapse
In others countries we don't get the same bands management, then I can't say anything about LTE.
But I'm on PureNexus 7.1.1 and I get the same "issue" about network droppin when calling. When the call starts, my phone turns into don't disturb-mode and recover the network only when the phone call ends.. It doesn't really cut my network connection, but it looks like. It may be rom settings.
However I don't care as long as everything works good, it's just an icon. (how a phone call can be done while network is shutted off ^^)
When I was on the stock ROM, this autumn, 7.1 version of Android did the same thing, loosing data connection while being still connected to the network (but at anytime not just phonecalls). Finding it back some minutes later. That was fixed with 7.1.1. Stock.
Hope that might help you (looks not ) if it's the same problem. May be give an eye to the Rom settings..
Have you tried if your device do the same thing with an another Rom ? (stock for example)
Larzzzz82 said:
The volte provisioned flag turned on in the testing menu? I have a setting for enhanced 4g lte mode in my settings, wireless networks/more/cellular networks settings. Did they remove the advanced calling from your account? Just throwing some things out there.
Click to expand...
Click to collapse
I knew something looked like it was missing. I don't have any enhanced 4g LTE settings in that section. Normally there's a tick box to turn it on there. It's missing. Is that due to them not having it turned on in my account?
Also for everyone else, this problem only started when I tried the whole at&t switch. I was on this rom when I switched and it worked fine before then. I didn't factory reset since then though, wondering if I need to try that.
zelendel said:
The tech may not be wrong as Verizon uses band 13 as their main LTE band and ATT uses band 17
http://www.phonearena.com/news/Chea...on-T-Mobile-and-Sprint-use-in-the-USA_id77933
Click to expand...
Click to collapse
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
BlockOfDynamite said:
The tech is definitely wrong; since it's a Nexus 6 (presumably XT1103) it has all the possible LTE bands used in the US. There should not have been any issue when switching. I had something similar happen to me, when I just switched to verizon and did the "reset network settings" button, it screwed up my phone so I couldn't use LTE period, I had to reflash the modem in order to fix it. I know you already said you reflashed the modem, but I'm not sure what to suggest. There is absolutely nothing physically wrong or incapable about your phone, just some config got screwed up somewhere along the way. I'd just try to flash as many things as you're comfortable with without losing your userdata. Like modem, bootloader, etc. until your data comes back. If nothing else, press the network settings reset button and flash the latest modem. Make sure your twrp is up to date as well.
Click to expand...
Click to collapse
I think i'm going to reflash my rom today. I did the modem, twrp is up to date, bootloader is fine. I did the reset network settings (I was sure that was going to fix it, no dice). So I'm going to reflash the rom today and see if that fixes it. After that I have no idea what is left to try other than reverting to stock, which I'd like to avoid.
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Larzzzz82 said:
Yes, it is a feature that needs to be added to your account. Go online and check their website or go into the hidden menu and activate it. If it sticks, it's on your account.
I tried the wifi and video calling flags and they didn't stick. Go figure... C'MON big red...
Click to expand...
Click to collapse
How do you enter the hidden menu on the n6? I thought I found it but it wasn't working.
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Larzzzz82 said:
.#.#4636#.#. select the phone info tab. In there, there will be either a drop down menu or buttons to tick and they'll change color
Click to expand...
Click to collapse
I got in, VoLTE was not ticked. I ticked it. I got the setting for it then in settings. But making a phone call gave me an error. I rebooted, and it's not ticked now. So does that mean I need to call Verizon to have them flag my account?
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Larzzzz82 said:
You need to add it in your account then. Easy enough to do online. You want to, "manage features."
Click to expand...
Click to collapse
That did the trick. All fixed. Thank you! That was driving me nuts. I never considered the idea that the setting would be turned off . But since I did leave and come back...
Thanks again!
Glad you're all set. ?
Back in July I got a steal on a new US Cellular Galaxy Note 9, so I immediately threw my iPhone 6S SIM card into it and went through several rounds of software updates. After the last update the splash screen switched to AT&T and it suddenly had several AT&T apps. It didn't TOTALLY eliminate the US Cellular stuff because I had to delete at least one app and change the Samsung browser's default home page.
Due to the iPhone SIM card and some stuff on AT&T's side, it would not do VoLTE or WiFi calling until I got a new SIM and had AT&T use the IMEI from an AT&T Galaxy Note 9 (read it off one from the store). I did that in late August and the only remaining issue O noticed was that my MMS messages will not download as long as I am on WiFi.
I just noticed what may be a new issue: I think I stopped getting carrier updates. Looking on AT&T's site, I see that they have multiple newer updates with the latest from September 18th:
https://www.att.com/devicehowto/tut...tep_KM1278532?make=Samsung&model=SamsungN960U
My "Security Patch Level" says May 1, 2019, while AT&T's website says that there have been 4 updates since then (latest at Security Patch Level September 1, 2019).
My baseband version doesn't quite match any of the ones associated with AT&T updates, though their May 22nd update seems to be the most similar (AT&T's N960USQS1CSE1 compared with my N960USQU1CSE3).
I recall that the new phone updated multiple times and was still on Oreo before it updated again to Pie, and again to AT&T-flavored Pie. I figure the final update was really just adding the AT&T apps and splash screen, but it somehow stopped me from getting further updates from US Cellular. I'm pretty sure I had an AT&T SIM card inserted for all of my updates.
On that note, I believe I tossed the original SIM and US Cellular does not operate in my region (only showed up here through a salvage store). I'm not easily able to get another US Cellular SIM for triggering it to revert to a US Cellular ROM. I'm not interested in custom ROMs and all that and ultimately just want to keep my phone up to date the same way a normal AT&T customer would after buying theirs from AT&T. I thought the Note 9 adding carrier customizations to match the inserted SIM would take care of all this automatically (half the point, right?) but I guess I was wrong.
Is it possible to get carrier updates like I was getting before? If not, what would you guys recommend for getting up to date and staying up to date? Thanks!
CZroe said:
Back in July I got a steal on a new US Cellular Galaxy Note 9, so I immediately threw my iPhone 6S SIM card into it and went through several rounds of software updates. After the last update the splash screen switched to AT&T and it suddenly had several AT&T apps. It didn't TOTALLY eliminate the US Cellular stuff because I had to delete at least one app and change the Samsung browser's default home page.
Due to the iPhone SIM card and some stuff on AT&T's side, it would not do VoLTE or WiFi calling until I got a new SIM and had AT&T use the IMEI from an AT&T Galaxy Note 9 (read it off one from the store). I did that in late August and the only remaining issue O noticed was that my MMS messages will not download as long as I am on WiFi.
I just noticed what may be a new issue: I think I stopped getting carrier updates. Looking on AT&T's site, I see that they have multiple newer updates with the latest from September 18th:
https://www.att.com/devicehowto/tut...tep_KM1278532?make=Samsung&model=SamsungN960U
My "Security Patch Level" says May 1, 2019, while AT&T's website says that there have been 4 updates since then (latest at Security Patch Level September 1, 2019).
My baseband version doesn't quite match any of the ones associated with AT&T updates, though their May 22nd update seems to be the most similar (AT&T's N960USQS1CSE1 compared with my N960USQU1CSE3).
I recall that the new phone updated multiple times and was still on Oreo before it updated again to Pie, and again to AT&T-flavored Pie. I figure the final update was really just adding the AT&T apps and splash screen, but it somehow stopped me from getting further updates from US Cellular. I'm pretty sure I had an AT&T SIM card inserted for all of my updates.
On that note, I believe I tossed the original SIM and US Cellular does not operate in my region (only showed up here through a salvage store). I'm not easily able to get another US Cellular SIM for triggering it to revert to a US Cellular ROM. I'm not interested in custom ROMs and all that and ultimately just want to keep my phone up to date the same way a normal AT&T customer would after buying theirs from AT&T. I thought the Note 9 adding carrier customizations to match the inserted SIM would take care of all this automatically (half the point, right?) but I guess I was wrong.
Is it possible to get carrier updates like I was getting before? If not, what would you guys recommend for getting up to date and staying up to date? Thanks!
Click to expand...
Click to collapse
Attached is the link for my last update , I'm using it on AT&T , phone is original from AT&T, and all is Ok for me, I hope can help you.
https://www.google.com/amp/s/forum....note-9-att-rom-update-sept-2019-t3979303/amp/
Thunderxxx said:
Attached is the link for my last update , I'm using it on AT&T , phone is original from AT&T, and all is Ok for me, I hope can help you.
https://www.google.com/amp/s/forum....note-9-att-rom-update-sept-2019-t3979303/amp/
Click to expand...
Click to collapse
I'll check it out when I get back to my PC. Thanks! I assume it's something I need to flash with Odin?
I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".
This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.
Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?
Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?
If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?
I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?
Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.
Seeing this forum has so little activity, on 1/21 I ended up getting a used Moto E6 (XT-2005-3 is a tmobile aka carrier unlocked MetroPCS version). While overall this is not as nice a device and has fewer features than Note 4, it does cover what for me are the essentials - removable battery, SD card slot, support for 5.8GHz wifi. Best of all, it supports B71 which will be helpful for, well, making phone calls!
I still ponder someday getting one of these as a hobby device, but that would be second place to the E6 for use as a phone, and won't be for a couple more months yet (too many expensive household issues are taking their toll on my "toy" budget right now).
ForestCat said:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice.
Click to expand...
Click to collapse
Thank you, this was the part I needed to find out. With that in place, the only thing missing would be the B71 coverage but the E6 is already in place for that.
Re your Verizon adventures, I have no experience with any of that. What I read about T-Mobile dropping support for the verizon version in the last network update is all I know, and I don't have the skills to dispute what they say there. The best I could do is offer some links to threads on this forum but on double checking them it seems you've already been there and got no answers.
The only thing I see that might help you with that is if you could update just the t-mobile modem without disturbing the verizon bootloader. I see you tried that but it didn't stick when using Odin. I don't know if it would be any different using SmartSwitch that seemed to work for MarineWonder as he posted at https://forum.xda-developers.com/t/...pgrade-on-jan-29th-2021.4224237/post-87464609 ?
Then again he may have been putting it on a t-mobile phone rather than mixing with the verizon bootloader so who knows?
My guess since it has been so problematic for you on the verizon phone is that you may need to only use a tmobile phone since that may be the only way to get the last t-mobile modem update. Bummer that the one you bought has a dead usb port. How are you charging it? Is there any chance you could return it to the seller since it came pre-broken? Then put the refund money toward another, hopefully working, tmobile phone? And would that MODestROM work on a non-verizon phone?
The only other thought I had is there are apps to connect to ADB over wifi. Sadly most of these need root. The ones that don't, seem to need at least once using a usb connection to do the "adb tcpip 5555" command to set it all up. . . . how annoying that it is all so circular!
There is also https://telnetd.en.aptoide.com/app?store_name=apps&app_id=59202144 , maybe a telnet connection could do the "adb tcpip 5555" command instead of using the USB connection? Sadly the documentation (at https://waxrain.com/docs/010.html ) appears to be written in Chinese, and I never had much luck with google translate.
The N910T still supports VoLte.. It is still compatible with cellular networks.