Droid 2 Global, Unlocking + Rooting Success, Canada - Droid 2 Global General

I had trouble finding information on this variant of Droid, so I thought I'd share my own findings now that I have it working the way I wanted.
I ordered a brand new, Verizon Wireless locked version of this phone off eBay. I'm in Canada, so I was unable to activate the phone as it requests after the "touch the droid" screen. The nearest Verizon tower is very far away.
I found out (maybe this is common knowledge about Android phones, my searches were probably too specific) that I could bypass that activation by touching each corner of the screen.
I used SuperOneClick to root the phone, which went completely painlessly; seems like a great tool. This isn't a necessary step to unlock it, I just wanted it rooted.
I gave $30 USD and my phone's IMEI to CellUnlocker, and they got a working unlock code to me in 2 days. Some people have had problems unlocking the phone, but it worked immediately for me, maybe it's luck.
I haven't tried a brand unlock, since I don't plan on using my phone in the states soon!
I followed these instructions to improve my signal strength, but I haven't thoroughly tested it.
I am now using the phone without a hitch on Telus' network, data included. I had to set up an APN for them, with information from here.
I applied a fix mentioned by Kositch here to prevent Google Maps from crashing my phone. The min free KBytes setting was 2845 by default, as reported by the sysctl config *root* tool. It seems to have worked.
Unfortunately my battery doesnt last more than a day with moderate use. I've setup setcpu to underclock the processor based on battery life in hopes that it helps. It's hard to tell if it does or not without any kind of benchmarking. Based on the built-in battery usage app, I would say it probably does not affect my battery life much to underclock the phone, it is mostly the display that drains it.
One bug I have had is that my Internet connection will stop working after the phone has been out of use for some time or in airplane mode. A restart of the phone seems to solve this every time, though I'd rather not have to do that.

I am having a nasty bug when using my D2G on Telus - every time I dial out, immediately call drops and then reconnects in background. Very annoying and prevents you from dialing conference bridges automatically. I have tried with both normal sim that came with my Telus milestone at the time as well as a fresh new microsim and experienced this in both cases. On Fido and Rogers it is fine. Haven't tested on Bell as I don't have active account with them.
Sent from my XT860 using Tapatalk

My phone does the same, but it does not cause me problems as I only make ordinary calls. It's certainly a bit weird.
Sent from my DROID2 GLOBAL using XDA App

Related

[Q] mobile network disconnects and gets stuck "turning on"

Hello all, i have had my HTC sensation 4G (on Bell) for just over a month and a few days ago i started losing my connection to the network intermittently. Super annoying. Anyways i tried deleting some recent apps, figured that might be the issue but nope didnt help. It happened about 3 days in a row until i finally did a Factory Reset on the phone. It worked fine for a bit and then began stopping its connection to the network. Anyways super frustrating, i read some forums about tunring ciphering on and off, i tried that didnt work... needless to say im chapped.
Sorry for the length, but basically wondering if anyone knows how to fix this as its to late to return the phone and i have read through similiar forums on other phones
sorry to hear abt ur problem. i experienced the same thing but i think mine was triggered when i installed juice defender. it would turn off mobile data when the screen was off and when i went to use the phone, i didn't have a connection. i uninstalled the app and did a power cycle and that seemed to fix the problem after i went back into settings and checked the box to turn mobile data on.
charronegro1971 said:
sorry to hear abt ur problem. i experienced the same thing but i think mine was triggered when i installed juice defender. it would turn off mobile data when the screen was off and when i went to use the phone, i didn't have a connection. i uninstalled the app and did a power cycle and that seemed to fix the problem after i went back into settings and checked the box to turn mobile data on.
Click to expand...
Click to collapse
This. The phone seems to have trouble (on the stock kernel at least) when switching data from wifi only to cell when cell is turned off. This happens to me when I use wifi calling. The solution I came up with was to connect to a wifi network then turn on mobile data in the quick settings manually. Works every time for me.
HTC really needs to fix this.
Under mobile network in wireless settings, enable always-on mobile data.
This somehow fix my connection whereby it hampers with JD app by not turning on when it needs to.
Thanks for the help guys. I did also recently install a "battery optimizer: in Droid Utilities or soemthing like that, although i did a factory reset. ill try and do a full battery cycle like you mentioned and see if that helps
so the phone worked fine on the weekend, and even friday and i thought it was cause i stopped using a non "htc" charger and got rid of Android Utilities. but now its Tuesday again and like clockwork at 1pm it just stops connecting, if i reset it i get network for a few minutes and then boom out again. Very frustrating mid work day to be without my phone for hours on end. Dont know what to do.
Are you using WiFi at the time it goes out?
Sent from my HTC Sensation 4G using XDA App
No i havent been, not allowed to use private phones on the corporate wireless, but so far i havent found a problem with it switching between wi-fi and H+ while at home.
I have a feeling that Bell Canada may be updating the network or something in the area but they havent said anything both times i called and i asked. so who knows. Its just to much like clockwork for me to think it would be the phone, but who knows.
So i believe i have this figured. I talked to tech support once again yesterday and i point blank asked if it was network problems he said no (3rd person from bell to tell me this) then reccomended i get a sim card change if that didnt work he said send the phone in for repair.
So i went to the downtown bell store talked to the girl, explained why i needed to replace a brand new sim, and she told me that it was because Bell doesnt have towers downtown they share the Telus towers, however because of network bottleneck bell users get less priority and thus i cant use my phone... Not only is this unnacceptable for a phone company to not provide service DOWNTOWN in a major city but having denied it multiple times forcing me to troubleshoot for hours and spend almost an hour talking to bell representatives...
NOT HAPPY. Bell - 5 in my books, lucky my contract is up in a few months and i can switch to telus where i will be able to get signal downtown...

[Q] Telus/Koodo & XT925

Hello,
Peculiar situation I am currently in so any feedback/suggestions are welcomed.
Purchased XT925 at launch. SIM unlocked. Unlocked bootloader. Using Koodo SIM card. Non-rooted. Stock OS. Correct APN. No task killers or CPU governors.
Able to establish LTE or HSPA connections.
However XT925 signal randomly drops. Signal bars go from full to nada resulting in packet loss and dropped calls. Usually within 5 to 10 seconds, connection is re-established.
Upgraded to SFR Vodafone Jellybean using recommendations via URL:
http://forum.xda-developers.com/showthread.php?t=1953943
Issue continues.
Try using Telstra ICS followed by JB upgrade; issue continues in both versions.
SO
Downgrade to native OS (Rogers ICS), fix IMEI issue, patch 'bootloader unlock screen' and return phone under extended warranty plan (citing issues with connectivity).
NOW
Get new XT925. Purchase new SIM. Unlock only SIM. Confirm with both Telus and Koodo that phone should work on network.
Issue continues.
THUS
I am left to conclude that this model's radio and Telus/Koodo don't operate properly despite documentation stating that bands should work. Love the phone but I need network reliability. Am finding that using *#*#4636#*#* to change the network type works more often than not but still a band-aid solution.
A_H_E said:
Hello,
Peculiar situation I am currently in so any feedback/suggestions are welcomed.
Purchased XT925 at launch. SIM unlocked. Unlocked bootloader. Using Koodo SIM card. Non-rooted. Stock OS. Correct APN. No task killers or CPU governors.
Able to establish LTE or HSPA connections.
However XT925 signal randomly drops. Signal bars go from full to nada resulting in packet loss and dropped calls. Usually within 5 to 10 seconds, connection is re-established.
Upgraded to SFR Vodafone Jellybean using recommendations via URL:
http://forum.xda-developers.com/showthread.php?t=1953943
Issue continues.
Try using Telstra ICS followed by JB upgrade; issue continues in both versions.
SO
Downgrade to native OS (Rogers ICS), fix IMEI issue, patch 'bootloader unlock screen' and return phone under extended warranty plan (citing issues with connectivity).
NOW
Get new XT925. Purchase new SIM. Unlock only SIM. Confirm with both Telus and Koodo that phone should work on network.
Issue continues.
THUS
I am left to conclude that this model's radio and Telus/Koodo don't operate properly despite documentation stating that bands should work. Love the phone but I need network reliability. Am finding that using *#*#4636#*#* to change the network type works more often than not but still a band-aid solution.
Click to expand...
Click to collapse
Stick to the Rogers Official ICS and try this...
I compared the RAZR HD build.prop with the Atrix HD build prop and have some recommendations, you'll need to be rooted to make these changes:
On line 152, put a # in front of it:
#persist.radio.sms_sync_sending=1
Add the following lines at the end:
Code:
ro.telephony.default_network=9
persist.cne.UseCne=none
ro.mot.FTR.NSUI=true
ro.mot.fid.30544.tty=true
net.early.sockets=0
ro.mot.ds.fastdormancy.disable=false
ro.mot.ds.fastdormancy.incall=false
Good luck and let me know how it works!
Follow-up
Thank you for both response and assistance,
The first line '#persist.radio.sms_sync_sending=1' was already added and enabled so no changes needed.
Took the additional lines suggested and added them, saved, reset, but the disconnects continue to happen.
I've attached my build.prop and if you the have time, perhaps you can see if I added the requested information appropriately. Alternatives changes are welcomed if you or anyone has them.
Ultimately, if the community is at lost for a solution, I plan to report the issue to Motorola and likely, at some point in the next week, return the XT925 because disconnects aside, I would like a better camera (incidental but the amount of noise in each shot tends to ruin the overall quality).
A_H_E said:
Thank you for both response and assistance,
The first line '#persist.radio.sms_sync_sending=1' was already added and enabled so no changes needed.
Took the additional lines suggested and added them, saved, reset, but the disconnects continue to happen.
I've attached my build.prop and if you the have time, perhaps you can see if I added the requested information appropriately. Alternatives changes are welcomed if you or anyone has them.
Ultimately, if the community is at lost for a solution, I plan to report the issue to Motorola and likely, at some point in the next week, return the XT925 because disconnects aside, I would like a better camera (incidental but the amount of noise in each shot tends to ruin the overall quality).
Click to expand...
Click to collapse
Another recommendation is, see if you can load up the Atrix HD ROM from Bell.
Sent from my XT925 using Tapatalk 2
Definitely NOT! Do not try to install a rom from another device... Your going yo be left with a brick likely

[Q] HTC One S, CM11, and poor data/cell signal (if any)

Hey everybody:
This is kind of a last gasp for me. My HTC One S suffers from the usual that you read about - "Preparing SIM" messages, constant error reports on bootup, random reboots. I honestly hate the phone.
So I installed a custom ROM. I unlocked the bootloader via HTCDEV, then I used the 12/20/13 CM11 (KitKat 4.4.2) with the 12/15 GAPPS.
The phone worked OK except now I was able to see what I've read about, and probably unknowingly experienced with the stock ROM, and that is the phone constantly flipping between Edge, 2g, HSPA, HSPA+, etc.
So, I decided to try a new radio. Did it a million times on my old G2. In order to get S-OFF to update it, I used the RLL to bring it back to stock Jelly Bean, then Moonshine to set S-OFF, SuperCID'd, and restored it with CWM. Then I installed the 1.20.x radio and at that point, all heck breaks lose with the data network connectivity and even cell signal. I might have no cell or data signal. I might have a cell signal with Edge. If I get up and move, it might go to HSPA, then I might lose everything again. This is much more pronounced than what I witnessed when I first installed the CM11 ROM.
I've tried reflashing the original 1.13 radio and it's no better. I went back to the 1.20 radio and even wiped and reflashed CM11 and GAPPS from scratch. Still very inconsistent data connectivity, so I'm not necessarily convinced it's the version of the radio because they're both pretty darned bad including the original version.
Has anybody been through this and gotten it straightened out? This is strange that even going back to the old 1.13 radio doesn't seem to help.
Thanks for any ideas...
Type: HTC One S, S4, S-OFF, SUPERCID
HBOOT: 2.15.4444 (Moonshined)
Image: CM11 (12/20/13 - 4.4.2)
Radio: 1.20.50.05.16_10.31.50.08L
Who is your carrier? If it is TMOUS you will probably need to make some adjustments to your /system/build.prop file. When I flash a new ROM I have to make the following additions/changes before my data connectivity is stable:
Code:
pm.sleep_mode=1
ro.ril.hsdpa.category = 24
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 4
ro.ril.radio.svn=19
ro.ril.fast.dormancy.rule = 0
The setting "ro.ril.fast.dormancy.rule=1" probably already exists in the file, so it will either need to be edited or removed. The other settings should not exist.
The changes that actually allow the phone to maintain a data connection (as I recall) are "ro.ril.radio.svn=19" and "ro.ril.fast.dormancy.rule = 0". "pm.sleep_mode=1" allows the CPU to completely power off, and the "ro.ril.h*" settings set max speeds for different data connections. I'm going off of what I've culled from various posts and forums, so I may be off the mark on some of my descriptions.
Here's one post briefly talking about these settings:
http://forum.xda-developers.com/showthread.php?p=48276115#post48276115
You will need root access and your /system partition will need to be remounted as read-write to make the changes. Ask or search if you need help with those. Of course if you're not on TMOUS, then I have no idea...
Yes, T-Mobile US is my carrier. There's another thing I found. If it go into the phone's testing facility (*#*#4636*#*#), I notice that it's set to WCDMA preferred. If I set it to WCDMA Only and give it a few, it does go to an HSPA/HSPA+ connection. However, that setting appears to be lost between restarts.
What I don't get is that when I first flashed the CM11 ROM, I at least had the intermittent E/2g/3g/HSPA connections. How, if I go into that testing facility, it is stuck on Edge (and more consistent since my last flash). I will read the thread you provided a URL to. Thanks very much!
benyto said:
Who is your carrier? If it is TMOUS you will probably need to make some adjustments to your /system/build.prop file. When I flash a new ROM I have to make the following additions/changes before my data connectivity is stable:
Code:
pm.sleep_mode=1
ro.ril.hsdpa.category = 24
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 4
ro.ril.radio.svn=19
ro.ril.fast.dormancy.rule = 0
The setting "ro.ril.fast.dormancy.rule=1" probably already exists in the file, so it will either need to be edited or removed. The other settings should not exist.
The changes that actually allow the phone to maintain a data connection (as I recall) are "ro.ril.radio.svn=19" and "ro.ril.fast.dormancy.rule = 0". "pm.sleep_mode=1" allows the CPU to completely power off, and the "ro.ril.h*" settings set max speeds for different data connections. I'm going off of what I've culled from various posts and forums, so I may be off the mark on some of my descriptions.
Here's one post briefly talking about these settings:
http://forum.xda-developers.com/showthread.php?p=48276115#post48276115
You will need root access and your /system partition will need to be remounted as read-write to make the changes. Ask or search if you need help with those. Of course if you're not on TMOUS, then I have no idea...
Click to expand...
Click to collapse
OK, I did these build.prop edits. Unfortunately, they've gotten me nothing. Then I went and investigated them a bit more and tried two other minor changes to build.prop (one of your parameters and added another). I'm still stuck on the Edge network. If you do a lookup, you'll see plenty of others. I think this phone is pretty much worthless - as it's been from day one. It will be my last HTC phone. By contrast, my old G1 and G2 are still working. There are tons of reports about One S phones suffering serious issues like this.
I appreciate your help and certainly, if anybody has a eureka moment, I'd love to hear about it. For the time being, I'll most likely see about getting my old G2 reactivated. Others have reported that the only way they've gotten this fixed is sending it back to HTC under warranty. Mine is out of warranty, which is the only reason I decided I'd do it. It was such a bad phone, I had nothing to lose. The next one I buy will most likely be the Moto X.
Thanks again for the help. I absolutely appreciate it.
whealton said:
Yes, T-Mobile US is my carrier. There's another thing I found. If I go into the phone's testing facility (*#*#4636#*#*), I notice that it's set to WCDMA preferred. If I set it to WCDMA Only and give it a few, it does go to an HSPA/HSPA+ connection. However, that setting appears to be lost between restarts.
What I don't get is that when I first flashed the CM11 ROM, I at least had the intermittent E/2g/3g/HSPA connections. How, if I go into that testing facility, it is stuck on Edge (and more consistent since my last flash). I will read the thread you provided a URL to. Thanks very much!
Click to expand...
Click to collapse
Sorry I can't be of more help. I'm still fairly new to this phone, but I quite like it. I suppose I've been more fortunate than others in that I haven't had any real problems with it.
It's not a problem and I'm grateful for you trying. The information you provided was also interesting from a learning perspective.
I reran the RUU on it, just to see if it would make any difference. This made it so I USUALLY have 2g connectivity, but that's as far as it goes and it's not good enough. I have lost that at times, but for the main part, it's consistent with 2g.
T-Mobile is sending me a new SIM to get my old G2 reactivated. While it's only about a quarter of the One S speed, it'll suffice. Unfortunately, the SIM it had couldn't be used because too much time had elapsed since the phones last use. That should be here Monday and that particular phone was WAY more tolerant of different images and radios (knock on wood!). It's currently running a Jelly Belly image of Android 4.2.2 (if I remember), so this should be interesting.
As for my HTC One S, I'll most likely give it to my son to use for games and media. With nothing more than 2g speeds, it's worthless to me. This phone has been a complete and utter piece of garbage since the day I got it. It's funny that my excellent experience with the T-Mobile G1 and G2 by HTC was my reason for buying the One S over a Samsung model. Now that phone is the reason I won't be getting another HTC. Strange how that works.
Again, thanks VERY much for the help!
benyto said:
Sorry I can't be of more help. I'm still fairly new to this phone, but I quite like it. I suppose I've been more fortunate than others in that I haven't had any real problems with it.
Click to expand...
Click to collapse
Weird, I had a desire z (same phone as g2) and it had really bad reception while holding it. Would lose all signal in the house. All my other phones used have been fine and pretty well equal - nexus one, desire hd, one s, my girlfriend's iPhone are all about the same.
This summer at a cottage my sister gs3 had no service all week, same network and the one s and iPhone
4s both could squeak some signal if you didn't touch them. A slight edge going to the iPhone most of the time I think.
Probably either a radio issue with that phone on your provider or defective hardware?
Sent from my HTC One S using xda app-developers app
It's not the provider (T-Mobile). My wife's Samsung has 4g here in the house - no issues. I took the One S out and had 2g everywhere. It's the phone.
I'm also guessing it's most likely the radio, as in a bad chip. Once you try to burn a new firmware into it, it finishes it off. Don't get me wrong, I'm certainly no engineer. It may or may not be that, or may be WAY more involved. Some people said the only way they got it fixed was by HTC replacing the main board.
The phone was a POS even before installing a custom ROM. Random reboots, constant startups with messages asking if I wanted to report the errors to HTC, random instances of NO data connectivity and then a message saying the phone is "Preparing the SIM card". I finally realize now that the occasional drops I would get while working remotely in Mexico (using a Movistar SIM) were most likely a result of this thing losing it's data connectivity while "Preparing the SIM card." The issues with this phone and the fact that it was out of warranty were the only reasons I took a chance on installing a custom ROM.
I'm sorry that I most likely sound like I'm ranting. However, I've searched all over and found SO MANY issues with this phone, that there's no way they should NOT have been recalled. Even T-Mobile told me there were many reported issues with these things. Both companies failed their customers.
350Rocket said:
Weird, I had a desire z (same phone as g2) and it had really bad reception while holding it. Would lose all signal in the house. All my other phones used have been fine and pretty well equal - nexus one, desire hd, one s, my girlfriend's iPhone are all about the same.
This summer at a cottage my sister gs3 had no service all week, same network and the one s and iPhone
4s both could squeak some signal if you didn't touch them. A slight edge going to the iPhone most of the time I think.
Probably either a radio issue with that phone on your provider or defective hardware?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Here in Canada we don't even have 2g on Telus, Bell, virgin mobile and koodo (I am on Telus), so the several phones that seem to have network problems on 2g or switching back And forth only have those issues on Rogers/fido or the small carriers like wind.
A guy I knew from highschool years ago works at fido and I remember him telling me last year this phone had some reception issues.
When telus had this phone on their website still they had pretty well all 5 star reviews. So my phone would probably be a piece of **** on a 2g/3g network too luckily they work perfectly on hspa only.
Sent from my HTC One S using xda app-developers app
Interesting. It's nice to have the option in the case of there ONLY being Edge/2g/3g service available, but not to be stuck on it when HSPA is there.
350Rocket said:
Here in Canada we don't even have 2g on Telus, Bell, virgin mobile and koodo (I am on Telus), so the several phones that seem to have network problems on 2g or switching back And forth only have those issues on Rogers/fido or the small carriers like wind.
A guy I knew from highschool years ago works at fido and I remember him telling me last year this phone had some reception issues.
When telus had this phone on their website still they had pretty well all 5 star reviews. So my phone would probably be a piece of **** on a 2g/3g network too luckily they work perfectly on hspa only.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
True, at least around here though the amount of area without service for Telus/bell or Rogers seems to be pretty equal. So I'm happy not to have the issues with switching between 2g, 3g and LTE. It's hspa or hspa I guess.
Sent from my HTC One S using xda app-developers app

OnePlus One giffgaff/O2 POOR RECEPTION/ NO SERVICE

Hi,
I have recently purchased a used OnePlus One 16GB Unlocked phone from CEX, and it looks and performs great. However, upon trying my SIM it shows No Service/emergency calls only.
Ironically enough emergency calls arent possible either. I'm with giffgaff, (O2's network) and it would not make/receive calls where I live (West-London). Tried a Lebara sim too, same results.
IMEI number is fine, checked with CheckMend. Faffed about with APN settings, manually connecting to the network, but while I'm home it could hardly find O2's network and even then it shows no service. (usually finds EE and Vodafone but I haven't got those sims.)
Took it to work today and it seems to be working "fine" at work. What I mean by "fine" is that I can make/receive calls, watch HD youtube videos no problem, but download speed from various websites and from the play store would be about 20kb/s and connection would drop every now and then. Switching between 3G and 4G makes no difference whatsoever. Also tried the *#*#4636 options but if I switch preferred modes it doesn't save, it defaults to whatever it wants to upon reboot.
It improves outside of work and it's pretty usable, but it drops just before I get home. This area does have bad O2 coverage but with my old Samsung Galaxy S2 and sh*tty Sony Xperia E1 I always get a decent signal even at home.
So originally when I thought it had a dead antenna, I thought I would return and get a replacement, but upon googling around I found that OnePlus is at war with O2s network on some devices, so I might have the same issue. Flashing isn't really an option as I've never done it and even though I'm within 30 days I don't think I should brick it.
At this point if I get a replacement I might have the same issue, if I change networks I might have the same issue. I have a hard time convincing anyone at work to lend me their sims for a day.
Any advice would be appreciated. :fingers-crossed:
OS: Cyanogen 13.1.2. ZNH2KAS3P0-bacon
Elderberry 5
neverhangover said:
Hi,
I have recently purchased a used OnePlus One 16GB Unlocked phone from CEX, and it looks and performs great. However, upon trying my SIM it shows No Service/emergency calls only.
Ironically enough emergency calls arent possible either. I'm with giffgaff, (O2's network) and it would not make/receive calls where I live (West-London). Tried a Lebara sim too, same results.
IMEI number is fine, checked with CheckMend. Faffed about with APN settings, manually connecting to the network, but while I'm home it could hardly find O2's network and even then it shows no service. (usually finds EE and Vodafone but I haven't got those sims.)
Took it to work today and it seems to be working "fine" at work. What I mean by "fine" is that I can make/receive calls, watch HD youtube videos no problem, but download speed from various websites and from the play store would be about 20kb/s and connection would drop every now and then. Switching between 3G and 4G makes no difference whatsoever. Also tried the *#*#4636 options but if I switch preferred modes it doesn't save, it defaults to whatever it wants to upon reboot.
It improves outside of work and it's pretty usable, but it drops just before I get home. This area does have bad O2 coverage but with my old Samsung Galaxy S2 and sh*tty Sony Xperia E1 I always get a decent signal even at home.
So originally when I thought it had a dead antenna, I thought I would return and get a replacement, but upon googling around I found that OnePlus is at war with O2s network on some devices, so I might have the same issue. Flashing isn't really an option as I've never done it and even though I'm within 30 days I don't think I should brick it.
At this point if I get a replacement I might have the same issue, if I change networks I might have the same issue. I have a hard time convincing anyone at work to lend me their sims for a day.
Any advice would be appreciated. :fingers-crossed:
OS: Cyanogen 13.1.2. ZNH2KAS3P0-bacon
Elderberry 5
Click to expand...
Click to collapse
Could be band issue,but as you say it works on work(outside home) then for sure the sim is compatible with OPO bands.
This issue can be fixed by changing firmware of the device.
I know it would be seem hard at first but it's worth the work.Flashing firmware can greatly increase your signal strength and likely to cop out any issues with data and calls.
But first you need to flash Custom Recovery Twrp and before that you need to unlock the bootloader of your device.
To start with,
https://forum.xda-developers.com/showthread.php?t=2788632
You don't need to do the root section,just the bootloader unlocking then flashing Twrp.Its easy.
https://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Here's a firmware compilation thread just try them and use the one which suits your carrier the best.
Good luck

[Global ROM] MMS and Verizon - Called Verizon Support, Still Broken

Hello all,
Phone: Mi Mix 2S
MIUI: Global 9.6.4 Stable
Model: M1803D5XA
Carrier(s): T-Mobile(SIM1) & Verizon(SIM2)
Issue: MMS receiving is limited to 30kb when using the stock Xiaomi and Android Messages messaging apps. APN settings do not show on device for Verizon SIM(doesn't matter if in Slot 1 or Slot 2).
So I called Verizon and worked with level 2 tech support to try and troubleshoot this issue. Basically, the MMS and/or Device server on Verizon's end cannot verify the device and therefore limits MMS sending to the device as it cannot authenticate. This verification is done by verifying the IMEI of the SIM and the device identification.
So basically level 2 tech support cannot verify the device manually and cannot submit a request to add the device information either, it has to come from the vendor(Xiaomi) to Verizon.
Anyway we can request this from Xiaomi going forward? Seems weird to have all the bands for Verizon, can get full 4G LTE coverage but I can't receive more than 30kb per image.
I had this issue at first. Flashed latest stable and it was fixed. It's fixed on miui 10 beta and its fixed on treble builds
aeppacher said:
I had this issue at first. Flashed latest stable and it was fixed. It's fixed on miui 10 beta and its fixed on treble builds
Click to expand...
Click to collapse
Well I flashed to 9.6.4 stable, which I thought was the latest stable?
I'm flashing MIUI 10 right now...guess we'll see what happens.
*Edit, still not working on Verizon. And now on MIUI 10, Dual 4G is broken.
*Edit 2, now I have Dual 4G back. Verizon needs to be SIM 2, but be the default for Internet....
I'm on VZW only and I'm on the latest MIUI 10 beta. I'm experiencing this as well. My wife receives good quality images from my phone but when she sends from her Pixel XL to me they are terrible. As are images I receive from anyone else. Kind of a bummer.
Are you guys having issues getting connected on Verizon now? I'm not able to reliably connect at all, most of the time it just sits on 1xRTT on VOICE, and won't connect to data. I can get it to connect to LTE/VOLTE by smashing airplane mode or disabling radio over and over again. Occasionally it will go to LTE, but it doesn't stay working and drops out. I can't drive anywhere and even conduct a phone call as that doesn't stay up either. When it drops, it hard drops and acts like the modem is being reset, instead of roaming to a new cell tower.
Edit, forgot to mention, called VZW, they gave me the finger and tried to sell me an iPhone XS Max 512GB as a "suitable replacement" for my 8GB/256GB phone. They were not helpful, and told me that they have "teams taking steps to make uncertified phones not work on Verizon's network for security and safety reasons". I have tried two different sim cards as well, both with active service and both work in all 3 generations of Pixel XL that I have.
Why the hell would Verizon troubleshoot a phone they haven't certified for their network? Quit complaining.
Sent from my Mix 2S on VZW & Google Fi
JonMS said:
Why the hell would Verizon troubleshoot a phone they haven't certified for their network? Quit complaining.
Sent from my Mix 2S on VZW & Google Fi
Click to expand...
Click to collapse
Cause I pay them every month to provide me with service. They could've atleast escalated to someone with a brain and ability to look at logging on their side and tried to help. Your comment was not needed.
I have been struggling for days with my Verizon connected Mi Mix 2s. At times I could connect with VOLTE but I lost my MMS. This past weekend I tried various ROMs with no difference. I finally cleared everything, loaded TWRP and then flashed the Global developer beta.
I also put my SIM back into a phone that Verizon would recognize and reset the card.
When I was up and running again I did the *#*#86583#*#* to unlock VOLTE and then the 4636 dial to set LTE only. So far so good. I was then able to go back and add a correct apn for verizon. With Verizon Messaging app everything is working and stable, including MMS. Afraid to mees with it again. But it is possible to get the phone to work with Verizon.
mesament said:
I have been struggling for days with my Verizon connected Mi Mix 2s. At times I could connect with VOLTE but I lost my MMS. This past weekend I tried various ROMs with no difference. I finally cleared everything, loaded TWRP and then flashed the Global developer beta.
I also put my SIM back into a phone that Verizon would recognize and reset the card.
When I was up and running again I did the *#*#86583#*#* to unlock VOLTE and then the 4636 dial to set LTE only. So far so good. I was then able to go back and add a correct apn for verizon. With Verizon Messaging app everything is working and stable, including MMS. Afraid to mees with it again. But it is possible to get the phone to work with Verizon.
Click to expand...
Click to collapse
Hi - is your SIM a newer (or brand new) SIM? I am seeing something in the logging on the radio logs that the SIM doesn't contain any carrier information, and was also seeing several errors about missing CMDA specific settings. This weekend I spent most of the day on Saturday and Sunday testing build.prop edits, and messing with the apns-conf.xml file settings. I could not get anything other than 1xRTT most of the time (I modified one of the existing entries in the list of APNs to be an exact match of what my Pixel 3 XL has) and by forcing LTE Only in *#*#INFO#*#* I was able to get LTE for brief periods of time, but not consistently. On 8.11.29 and 8.11.23 builds I can't get data working consistently, and if VOLTE isn't turned on, I can't get it to even act like it's going to connect LTE. I checked the APNs and played with it for hours, but not much success. The device just seems to "connect" but if you try to call on VOLTE or use LTE data to do something, the radio appears to reset. I am wondering if someone at Xiaomi neutered something in the RIL setup for their builds that broke CDMA compatibility. When I have time again, I will do some more comparison to see if I can figure out why it's not working. I'm planning on decompiling some of the files in question and looking at the code and configurations to see if something in there is the cause. The radio logs do not have a smoking gun. I also grabbed a copy of the build.prop file from MIUI9/Oreo and I am going to compare to see if they have some kind of prop flags that are missing in the MIUI 10 builds and or PIE builds.
I am going to find a way to make this phone work on Verizon.
Eventually, I rolled back to MIUI9 on Oreo (I don't know the build off the top of my head and the phone isn't near me) via fastboot. I have been able to get decent connectivity with that software version on Verizon where I live. I had to create my own APN, and have been using that with limited success. I submitted a bug report on the MIUI bug reports page. If you want to upvote that bug, the link is here: https://en.miui.com/thread-4724630-1-1.html
Edit: I just went to lunch and couldn't get the phone to connect to anything but 1xRTT the whole time we were at lunch (I didn't force LTE only, as I haven't had to previously since I rolled back). My next steps when I have time is to compare the build.prop between the builds, but I am not expecting to find anything. I am starting to suspect from the differences in the way the logging looks that they may have messed with the code or config information for the the RIL setup in the Android before they built it.
Please keep posting what you try, I'll be following with interest! I had everything working for a while but since MIUI 10.0.6.0 mms has broken.
DeadJenkins said:
Please keep posting what you try, I'll be following with interest! I had everything working for a while but since MIUI 10.0.6.0 mms has broken.
Click to expand...
Click to collapse
Can you get data and phone services? Mine won't stay connected, but that could be a hardware problem.
PWn3R said:
Can you get data and phone services? Mine won't stay connected, but that could be a hardware problem.
Click to expand...
Click to collapse
Yeah, data and phone have been fine so far, I think a few times it's disconnected but messing with the APN has fixed it. In general, I'd say my data and phone have been pretty stable. MMS on the otherhand, I had working for a bit on 9.6. On 10.0.4.0 it's been really slow to send and receive or not working at all. When it did work, picture quality was awful.
PS, I have my phone set to Vietnam by mistake. I have an older SIM card, at least a few years.
PS still working fine.
Mine has been repaired, they had to resolder a connector for the antenna on the board and the logic board was dropped. I saw this happen, however, signal levels are as good if not better than the pixel devices in the same spots for me, so I don't think anything is permanently damaged. I've been debating trying to order another Mi Mix 2 from somewhere or ordering a Mi Mix 3. I have built roms and have a lot of android troubleshooting experience, and I can't seem to figure this one out. What I am seeing on my device is that once it is connected, it seems to not want to roam properly. Like disconnecting from one cell causes a modem reset and then it takes a long time to reconnect. I am going to keep working on it though.
PWn3R said:
Mine has been repaired, they had to resolder a connector for the antenna on the board and the logic board was dropped. I saw this happen, however, signal levels are as good if not better than the pixel devices in the same spots for me, so I don't think anything is permanently damaged. I've been debating trying to order another Mi Mix 2 from somewhere or ordering a Mi Mix 3. I have built roms and have a lot of android troubleshooting experience, and I can't seem to figure this one out. What I am seeing on my device is that once it is connected, it seems to not want to roam properly. Like disconnecting from one cell causes a modem reset and then it takes a long time to reconnect. I am going to keep working on it though.
Click to expand...
Click to collapse
So you had a hardware issue? After the fix, which things work and which don't work for you? When I disable VoLTE carrier check, I get the VoLTE symbol, but I can't make any calls. I've been messing with the SMSC, where it seems changes aren't persisting. I can't get mms to work anywhere but the stock app, which sucks because the stupid MIUI stock messaging app doesn't have group mms >.>
I had a screen break due to it falling on a very sharp corner of an object from about 6 inches up. I took it to a phone repair place locally. They dropped the logic board, camera, front facing camera/charging interface board as well from like 4 feet up onto concrete. The person who tried to repair the screen (which I provided the replacement for) did not follow the instructions on the video either and removed the plastic lining bezel from the phone body (you are supposed to remove the screen from the bezel with a heat gun). They had to send the phone out for micro-soldering to re-place and reattach the antenna connectors for the cellular and wifi antennas. They had to pay for that. I know what the phone looks like inside from watching the videos of how to replace the screen. When they gave the phone back, there was a substantial gap between the edge of the screen and the bezel in a couple spots (atleast 3 or 4 sheets of paper thickness). I ordered a new frame, bezel and screen all in one and replaced it myself (moved all the components from the original phone body to the new one). Everything appears to work, signal levels are good, but the cellular part will not stay connected, and the modem acts like it's resetting all the time. Sometimes it will stay connected to the repeater in the office I work in for 8 hours straight with no issues, and I can text and call. When I leave that area or go home, it doesn't seem to want to roam to service, and instead of switching cell sites it seems to just reset the modem. There is absolutely a possibility that some small transistor, resistor, cap or something else on this board got damaged when it fell. Given that you guys aren't reporting issues with your devices staying on the network, I'm starting to think I need to go back and make some serious noise at this repair place. I am no stranger to working on sensitive electronics, and I was extremely careful not to damage anything inside when I moved the components (and it was already exhibiting this behavior when I got it back from them before I took repairs into my own hands).
That said, I've spent the last two days trying to figure out if I can do anything that might be helpful with QPST and QXDM as well as playing with various additional build.prop configuration. Nothing there that seemed to help. Rolling back to MIUI9/Oreo seemed to help some but was not a magic bullet. I still had to manually configure APNs and find myself needing to reboot or airplane mode every time the device should roam to a new cell site. I am planning on trying to copy the "carrierconfig.apk" file that is part of the system settings off of a Pixel 3 XL onto the Android Pie MIUI10 beta to see if possibly Xiaomi has something jacked there, but since you guys aren't reporting issues, I am seriously starting to suspect that something is physically damaged after that drop on the logic board, but the intermittent behavior and the fact that the signal looks correct and normal when it's working is going to make it nearly impossible to identify the cause.
As a side note, there's a Mi Mix 3 on it's way from GearBest....
---------- Post added at 04:00 PM ---------- Previous post was at 03:10 PM ----------
DeadJenkins said:
So you had a hardware issue? After the fix, which things work and which don't work for you? When I disable VoLTE carrier check, I get the VoLTE symbol, but I can't make any calls. I've been messing with the SMSC, where it seems changes aren't persisting. I can't get mms to work anywhere but the stock app, which sucks because the stupid MIUI stock messaging app doesn't have group mms >.>
Click to expand...
Click to collapse
So on mine, I can't get it to connect whether VOLTE check is enabled or not. At the office I'm like 10 feet from a repeater, and it seems to connect on LTE/VOLTE (if that's toggled on) very quickly. I have VOLTE enabled on my Verizon account. On the extender, I can make calls on VOLTE, but can't call without VOLTE enabled. I can't get it to connect to VOLTE with the VOLTE carrier check enabled, I have to shut that off and manually toggle. I am noticing massive inconsistencies in the configuration information contained inside the carrierconfig.apk that is loaded in the system build by Xiaomi. I don't see a smoking gun there, but there's a metric crapton of differences.
If I am not next to this Verizon repeater, it usually takes multiple airplane mode cycles or reboots to get onto LTE, it just sits on 1xRTT forever, no texts or data come through when stuck in that mode. Any type of cellular roaming that should happen seems to just cause a radio reset, and it goes to blank bars with X and then it acts like it can't find a network to connect to for a while or goes 1xRTT with full bars and keeps resetting every 20-30 seconds.
PWn3R said:
Cause I pay them every month to provide me with service. They could've atleast escalated to someone with a brain and ability to look at logging on their side and tried to help. Your comment was not needed.
Click to expand...
Click to collapse
How is Verizon supposed to support a device they aren't familiar with? This post comes off as whiney. Verizon does NOT have to support every phone capable of their bands, that isn't up to them. Way too many variables using an outside device. With that said, running the latest global beta with the sim card out of my Pixel I have zero issues running Verizon Wireless as primary and Google Fi sim as secondary. Both networks getting VoLTE.
JonMS said:
How is Verizon supposed to support a device they aren't familiar with? This post comes off as whiney. Verizon does NOT have to support every phone capable of their bands, that isn't up to them. Way too many variables using an outside device. With that said, running the latest global beta with the sim card out of my Pixel I have zero issues running Verizon Wireless as primary and Google Fi sim as secondary. Both networks getting VoLTE.
Click to expand...
Click to collapse
I expect Verizon to use the standards defined for how these devices communicate. I expect Verizon to assist with troubleshooting by providing information and looking at logs as to what my device is doing on the network. This is not unreasonable. I am not asking them to tell me how to fix the problem on a device they don't support. I am not expecting them to just suddenly support a device, but I do expect them to be willing to look at logs and information on their side and provide feedback. I am glad to hear yours is working and am starting to suspect mine has some kind of hardware damage. The local repair place has refused to do anything to help out because "if it's got a signal, it's a software problem".
PWn3R said:
I expect Verizon to use the standards defined for how these devices communicate. I expect Verizon to assist with troubleshooting by providing information and looking at logs as to what my device is doing on the network. This is not unreasonable. I am not asking them to tell me how to fix the problem on a device they don't support. I am not expecting them to just suddenly support a device, but I do expect them to be willing to look at logs and information on their side and provide feedback. I am glad to hear yours is working and am starting to suspect mine has some kind of hardware damage. The local repair place has refused to do anything to help out because "if it's got a signal, it's a software problem".
Click to expand...
Click to collapse
Well, if it worked before the repairs.. it is definitely a hardware issue.
Check your APN settings. I had the exact same issue with my phone, especially after the latest update. I called Verizon for the customer support and they couldn't figure out as well. Then, I pretty much looked at every settings on my phone and tried almost everything, only to have the issue fixed by modifying the APN settings. For some reason, after the update, the SIM card removed the custom APN settings that I added when I first purchased the phone. Instead, it had the CBS, FOTA, IMS, LTE - Verizon Internet APNs available with the APN set as the CBS (Sorry I'm not an expert, so I really don't know what exactly they are. I suspect that those were pre-saved on my SIM cards as I have used the same one for 3-4 different phones?). Anyway, I googled Mi Mix 2s Verizon APN and set it according to the very first result I found. Since then, the MMS has started working well again. Hope it helps.

Categories

Resources