Develop Bugs

Radio fix GPS? Wtf is a radio?

What's a radio?

Well, maybe you need to flash a new radio more efficient than what you have. I have newer g2 radio ending in .27. Check out the radio threads in here.
Sent from my HTC Vision using XDA App

Radio, according to wikipedia, Radio is the transmission of signals by modulation of electromagnetic waves with frequencies below those of visible light.
lol sorry i had to do that
but I would like to know too, from what I've seen radio seems to fix many things like reception, GPS signal, battery life and maybe more?
so i assume its some type of firmware?? tho i think i'm very off so please correct me

Might be wrong here but radio for a cell phone if you think about how without it you have no gps, signal, wifi...radio equals cell phone for all the generic reasons lol
Sent from my T-Mobile G2 using XDA Premium App

I would also like a good answer to this.

Interestingly, I flashed the .27 radio and used it for some time .. Just today, I reverted back to the stock .26 radio, and now my GPS issue is resolved!!

No radio equals no reception.
Sent from my ADR6400L using XDA App

The radio is the part of your phone that interacts with cell towers. Without this software on your phone, it would not be a phone, rather a very small tablet computer. Changing or upgrading the radio to a newer version is just like updating any software; the newer version probably has some bug fixes, might be more efficient at doing things than the older versions, etc.
This is what you were asking, right?

Gwanatu said:
The radio is the part of your phone that interacts with cell towers. Without this software on your phone, it would not be a phone, rather a very small tablet computer. Changing or upgrading the radio to a newer version is just like updating any software; the newer version probably has some bug fixes, might be more efficient at doing things than the older versions, etc.
Click to expand...
Click to collapse
He's pretty much described it. At its core, a cell phone is simply a type of microwave radio. It simply has been given a familiar interface similar to a landline phone (dial tones, number pad, etc.) since that is what people have been accustomed to for so long.
When "flashing a radio" is being discussed here, it refers to the software component, and there is also a hardware component as well, but you don't need to really worry about that.
The radio is also how your phone communicates with the GPS satellites.
If you are referring to the GPS issues some people have had with CM7 (not finding the satellites at all), its been found that flashing a different radio solves the problem for many people. But its been well discussed on the CM7 thread, and other threads.
But are you trolling? You seem to more than enough to have to ask such an elementary question.

convolution said:
What's a radio?
Click to expand...
Click to collapse
A radio is that which causes or reads the vibrations of electrons in the air.
More specifically, your cell phone is actually two computers, which are somewhat interdependent. These two computers run two separate operating systems. The more "basic" computer runs the radio operating system and controls the air interface. The "user" computer runs ANDROID. The two computers pass data back and forth to each other.
There are different versions of the radio operating system available, which have different characteristics. Sometimes upgrading the radio OS will have benefits like improved reception.

[ CDMA / Verizon ] question on bad signal issues..

I tired to search but unsure if I pulled CDMA 100% or not..
None the less, Im going to move over to Verizon and Im after the Nexus. I see people say the signal is bad etc etc. Im coming from the HTC evo and Ive always prety much ran AOSP roms. As we know ( or us Evo users ) the AOSP roms dont show " full " signal. But it shows actual signal. Is this the issue people are ***** about? IS this what they are talking about, in terms of bad radios etc?
AOSP roms show the true signal, but not a masked/boosted signal similar to HTC phones done, right?
The bad radio rumor isnt a bad radio, just the way AOSP roms show the signal... right?

The bar reading was jacked up a notch in 4.0.4 (2 bars of signal in 4.0.1/2 will show up as 3 or even 4), but the db reading in Settings is still correct (though, read issue #2 below). The phone is fine hardware wise. What confuses (or convinces) people are three things:
1) Some people got duds. This will be very obvious because you won't get signal even in areas where other people on VZ can connect. You need to get the phone swapped.
2) The GN has a weird way of reporting signal strength. They completely over-do the hysteresis, so if you test/compare with another phone, you have to keep the GN in one spot for 10-20 seconds before you get the same reading.
3) Software bugs in the baseband which will crash the radio interface and leave you without data for up to a minute. There also appears to be some hand-off issues that may keep you on 3G when you should be on 4G.
The GN has no worse reception than any other Verizon handset, aside from the fixable bugs in the baseband, which really aren't "reception" issues anyway.

So with what you said, all the apparent issues that are there, are fixable in terms of ROMs or official fixes? I like to tinker with my phone, but not to keep it running correctly, ya know?
Is this issue still reported on the current batch of Gnex's?

I just got my Nexus a week ago, but it has worked perfect in terms of signal and data. No dropouts. My radio is whatever it came with, but my ROM is BAMF Paradigm

mroneeyedboh said:
So with what you said, all the apparent issues that are there, are fixable in terms of ROMs or official fixes? I like to tinker with my phone, but not to keep it running correctly, ya know?
Is this issue still reported on the current batch of Gnex's?
Click to expand...
Click to collapse
Personally, I've had fewer issues with the Galaxy Nexus than I did with the Nexus One (that phone DID have bad reception. Great call quality though) or the WinMo phone I had before that. Whenever I have connection issues, I just turn on and off airplane mode and the phone will come back and reconnect to 4G in ~15 seconds. Nothing serious beyond that.
Some people have had more serious issues, and I can't say if it was their phone or the network equipment used in their area or what. Only way to be sure is to try one out. I have little doubt that ~99% of GN users have little/no issue, but the ~1% that do have problems are vocal about them (they should be, this thing isn't cheap).
EniGmA1987 said:
I just got my Nexus a week ago, but it has worked perfect in terms of signal and data. No dropouts. My radio is whatever it came with, but my ROM is BAMF Paradigm
Click to expand...
Click to collapse
ROM has nothing to do with signal. Only the baseband matters.

ATnTdude said:
ROM has nothing to do with signal. Only the baseband matters.
Click to expand...
Click to collapse
Actually, if they have updated telephony, it can. For example, there are signal improvements in 4.0.4, but you must run the rom and the radios.
That said, Paradigm has made no telephony changes from aosp 4.0.3.

adrynalyne said:
Actually, if they have updated telephony, it can. For example, there are signal improvements in 4.0.4, but you must run the rom and the radios.
That said, Paradigm has made no telephony changes from aosp 4.0.3.
Click to expand...
Click to collapse
I was really simplifying things since this was a non-technical question. If you go from 4.0.2 to 4.0.3+, you may have more hooks into the kernel and from there into the baseband, but jumping randomly from ROM to ROM isn't the best way to solve a signal problem. Changing the baseband is the best way, kernel the next, and finally the Android version. Basically go in order of distance from the hardware, noting that each level is significantly less likely to cure you.

ATnTdude said:
I was really simplifying things since this was a non-technical question. If you go from 4.0.2 to 4.0.3+, you may have more hooks into the kernel and from there into the baseband, but jumping randomly from ROM to ROM isn't the best way to solve a signal problem. Changing the baseband is the best way, kernel the next, and finally the Android version. Basically go in order of distance from the hardware, noting that each level is significantly less likely to cure you.
Click to expand...
Click to collapse
After reading hundreds of posts on connectivity issues, yours is the first to bring some lucidity and sanity to the hardware issue. Now someone needs to focus on the BS from the carriers and the inadequacy of their distribution systems.

[Q] What Do I need to know?

Hey guys, I just recently got a surprise when I got the Galaxy Nexus Demo my father had, instead of his GSII (Sprint, if you can't tell)
Anyways, this isn't my first time with rooting a phone -- I've been into modding and tinkering with phones since the HTC Hero.
However, this is my first Samsung phone since the Rant.
Coming from an Motorola Photon 4G, here's what I'd like to know:
- Is Samsung a stickler like Moto when it comes to drivers and the modding community?
- Does rooting and unlocking the bootloader break 4G LTE?
- Where's the 4G switch in settings (coming from a MoPho, there was a switch in settings)? I did see, and switch on, the "CMDA and LTE" Option under Mobile Data in settings.
- Does this mean that it scans in regular intervals, like scanning for WiMax 4G? Or is it like 3G and simply finds info from the tower and determines the connection?
- My battery was at 57% by noon today. I woke up at 6 and had all of about 40 minutes of screen time. No core games. The exception was 1 minute of Temple Run. Is this normal?
- Do you have a Kitchen Sink Project? As in, An Amor installer with multiple ROM options and mods.
-Does it matter what my baseband and bootloader versions are? (coming from MoPho, 2.3.5 was a dreaded number)
- (info) -- Hardware Version: 1.4? -- BootLoader Version: PRIMELC02 -- Baseband Version: L700, FD02
- Lastly, What's a ROM you'd like to reccomend? I tend to stay away from MIUI because I don't like a half-Chinese Andro-iPhone ROM(unless it's not a half-translated ROM and has an app drawer, unlike the MoPho). And CM9 Nightlies, becuase... well, it gets boring really fast.
Feel free to answer all or any of the questions~

rsjc741 said:
Hey guys, I just recently got a surprise when I got the Galaxy Nexus Demo my father had, instead of his GSII (Sprint, if you can't tell)
Anyways, this isn't my first time with rooting a phone -- I've been into modding and tinkering with phones since the HTC Hero.
However, this is my first Samsung phone since the Rant.
Coming from an Motorola Photon 4G, here's what I'd like to know:
- Is Samsung a stickler like Moto when it comes to drivers and the modding community?
- Does rooting and unlocking the bootloader break 4G LTE?
- Where's the 4G switch in settings (coming from a MoPho, there was a switch in settings)? I did see, and switch on, the "CMDA and LTE" Option under Mobile Data in settings.
- Does this mean that it scans in regular intervals, like scanning for WiMax 4G? Or is it like 3G and simply finds info from the tower and determines the connection?
- My battery was at 57% by noon today. I woke up at 6 and had all of about 40 minutes of screen time. No core games. The exception was 1 minute of Temple Run. Is this normal?
- Do you have a Kitchen Sink Project? As in, An Amor installer with multiple ROM options and mods.
-Does it matter what my baseband and bootloader versions are? (coming from MoPho, 2.3.5 was a dreaded number)
- (info) -- Hardware Version: 1.4? -- BootLoader Version: PRIMELC02 -- Baseband Version: L700, FD02
- Lastly, What's a ROM you'd like to reccomend? I tend to stay away from MIUI because I don't like a half-Chinese Andro-iPhone ROM(unless it's not a half-translated ROM and has an app drawer, unlike the MoPho). And CM9 Nightlies, becuase... well, it gets boring really fast.
Feel free to answer all or any of the questions~
Click to expand...
Click to collapse
1) no not really. the drivers are on samsung's website
2) no
3) there should be an option for CDMA only. since you're sprint i would use just that
4) it constantly tries to get a LTE connection
5) having LTE on will kill your battery if you do not have LTE in the area
6) dont know
7) just make sure its for your version of the phone, thats it as far as i know
8) depends on what you want. just read the descriptions of the roms for your version of the phone (spring)

I kinda ran into a brick wall.
My model number is 14, but the build serial is the same as model 13.
It makes me wonder if they're just the same thing, or if any major modifications took place that could soft/hardbrick my phone if I decidedly rooted and unlocked the bootloader.
Having the same build number.. I would assume they're running off the same stock android 4.0.4.
Still, I don't know.
And I don't want to end up bricking two phones in one week.

rsjc741 said:
I kinda ran into a brick wall.
My model number is 14, but the build serial is the same as model 13.
It makes me wonder if they're just the same thing, or if any major modifications took place that could soft/hardbrick my phone if I decidedly rooted and unlocked the bootloader.
Having the same build number.. I would assume they're running off the same stock android 4.0.4.
Still, I don't know.
And I don't want to end up bricking two phones in one week.
Click to expand...
Click to collapse
Its pretty much impossible to brick a nexus.
Just flash the right from for your version which would be sprint and the name of your version is toroplus.
Maguro is GSM and toro is Verizon's gnex.

nodstuff said:
Its pretty much impossible to brick a nexus.
Just flash the right from for your version which would be sprint and the name of your version is toroplus.
Maguro is GSM and toro is Verizon's gnex.
Click to expand...
Click to collapse
Something's up with my device.
And actually it's not impossible. They said the same thing for the Motorola Photon, but I managed to brick it by unknowingly upgrading CWM to a shoddy version that couldn't mount /system.
Even worse, their was no way to charge my battery.. so I couldn't use fastboot to push a working CWM recovery to my device.
Result? a brick.
Anyways...
I'm going to make a new thread for my issue, since it's completely unrelated to the OT.

LTE on won't kill your battery if there is no LTE towers.
LTE WILL kill your battery if there is low LTE signal.

rsjc741 said:
Something's up with my device.
And actually it's not impossible. They said the same thing for the Motorola Photon, but I managed to brick it by unknowingly upgrading CWM to a shoddy version that couldn't mount /system.
Even worse, their was no way to charge my battery.. so I couldn't use fastboot to push a working CWM recovery to my device.
Result? a brick.
Anyways...
I'm going to make a new thread for my issue, since it's completely unrelated to the OT.
Click to expand...
Click to collapse
A nexus is COMPLETELY different to a Motorola photon. I don't think you understand that.
It is almost impossible to hard brick a nexus phone.
There is always a solution unless the problem is hardware related.
Whoever said it was impossible to brick a mopho was an idiot and lying.

The worst that can happen while flashing roms is that you flash the wrong one (say a Maguro rom on Toroplus) but all that would do is break data, no bricks. Easily fixable by flashing the CORRECT rom.
This is a Nexus device after all, I hope you realize that.

rsjc741 said:
Something's up with my device.
And actually it's not impossible. They said the same thing for the Motorola Photon, but I managed to brick it by unknowingly upgrading CWM to a shoddy version that couldn't mount /system.
Even worse, their was no way to charge my battery.. so I couldn't use fastboot to push a working CWM recovery to my device.
Result? a brick.
Anyways...
I'm going to make a new thread for my issue, since it's completely unrelated to the OT.
Click to expand...
Click to collapse
A nexus is way different than a locked moto. Nexus is purposely open and easy to flash anything. It really can't be bricked unless you pull our the battery in the middle of flashing a radio. That's about the only way.

Is FM Radio Usable on Rooted with Spirit?

Having successfully rooted my Verizon LG G4 phone just last week via instructions found on this website (along with some added trial and error being that it wouldn't at first show the port information on Windows 8 end until I eventually tried installing the Verizon LG G4 software onto the computer), I am now trying to see if I can enable the FM Radio chip to work on the phone. I had downloaded the NextRadio app from the Google Store and got the screen indicating that it wasn't supported on my device due to the carrier's (Verizon's) restrictions. I also just read in here right now some info that suggests that perhaps the chip could be grounded to make it physically unusable? I work with electronics and wouldn't mind having to do something to the chip to UN-ground it if I knew what to do or look for specifically. In any case, with my phone being rooted, I was hoping that a program such as Spirit would be good enough to allow access to the chip, it apparently having its own driver for it. I checked the Spirit information page here and couldn't find my phone under either list for supported or unsupported devices. So I'm just not clear what the case would be. Any ideas on both this as well as whether I would have to alter the chip physically and in what manner would be greatly appreciated. I would rather know first about whether an app such as spirit will work on my specific rooted phone before buying the app. It's not important to have FM radio, but it would be nice if POSSIBLE. My expertise is in programming in 'C' for Windows so far, mainly using the full Cygwin C/C++ compiler environment download. Plus I used to work on Unix systems early on and loved them, so I will eventually be writing programs for this new Android smartphone of mine as well as also eventually installing a Linux or related Unix-based operating system onto my personal computer. So although I've been fairly good with computers for quite some time now, especially concerning programming them, I'm not yet an expert on Android systems, with my perhaps currently being at about the beginning-intermediate stage. And I used to solder some of my own circuits together as well as making ones up for myself via trial and error, although I'm not quite yet at the electrical engineering level. Thanks for any help in advance!...

[Fix] [MiA1] Network Issue [best solution]

Before I begin, I'd like to thank:
phhh for assisting Sooti
@sooti for his work on Pixel Experience
@joeyhuab for his work on the modem
Mentor.37 for the GSM patch
And to many other XDA contributors who have addressed similar troubles on other devices.
I'm writing this in narrative, use of "I" in any of it's applications denotes my effort to utilize what I've learned.
I stood upon the shoulders of giants.
Disclaimer
If you pursue anything mentioned or alluded to here, you assume all risk.
Please don't ask me any how to's. All you need to help yourself is here and the search function works fine.
Depending on region or network or both, MiA1 stock had inherent network trouble. This is especially true if using a custom ROM. The phone never, from unboxing, successfully registered itself to the network, so I had to research and install all the appropriate APN settings for my MVNO. There are several, and all are needed.
The mobile network worked well on stock until around the December 2017 update. It was initially blamed on the update from 7.x.x to 8.0, calling it a bug. It was in the following February that I stumbled across a report that Germany identified the MiA1, specifically, as generating the greatest emmission of RF out of all current phones (link (1)).
It appears, and I assume, that in response to this government report, Xiaomi modified the firmware to reduce RF emmission to bring rhe device into compliance. Likely, the radio power was reduced.
I began searching for modems, ROMs, kernels, band availability, whatever work was being done in regard to the network problem up to and including all the hardware information that I could personally verify or felt comfortable building upon.
Hardware may complicate our issue, but it is not the cause or the solution. However, if an aftermarket plastic battery cover becomes available I will swap battery covers to observe the effect. I'm aware the metal battery cover is integrated into the atenna function.
What I've done, and what has worked;
I found a thread for the stock modem (link (2)) and I flashed the file, but the network dropped dead from area to area.
Later, I stumbled across a CDMA to GSM patch (link (3)). A script, developed several years ago that fully enabled the GSM function on phones sold originally for CDMA. Ours was initially capable of operating on both GSM and CDMA. I flashed it, and it helped greatly, but the network reset to 2g after every reboot.
I Flashed the modem on top of the patch, and found the OS became laggy and later I started getting an error "android has stopped".
I have long since flashed PE (link (4)). The June update included the GSM patch. I have flashed April modem over PE stock as a matter of preference.
The network issue has stabilized, with exception of indoors- which I still believe to be either a firmware or hardware issue, but likely both. Ultimately, indoors I have steady reception but it spends half of the time on 2g. I can call out nicely from indoors and with WiFi, that's all I need.
**Edit**
A significant volume of this is based on educated assumption, of which was inferred as opposed to verified by me- this contradicts my ethics as a mechanical technician- but I do as I'm able until I have learned coding, logcats, and commands successfully enough to hash out what I must in the name of accuracy. You must, and I encourage you to, do your own research. I will do my best to correct anything here as appropriate.

(1) https://www.rfsafe.com/first-time-e...f-excessive-levels-of-hazardous-rf-radiation/
(2)
https://forum.xda-developers.com/mi-a1/themes/twrp-baseband-modem-april-stock-rom-t3777901
(3) https://www.internauta37.altervista.org/en/patch-fully-enable-gsm-cdma-global-phones-android
(4)
https://forum.xda-developers.com/mi-a1/development/unofficial-19-03-18-t3765500
Sent from my tissot using XDA Labs

I did conduct a physical breakdown of the device.
I found the battery cover is indeed of a "unibody" design. The internal antenna, receiving, has inegrated the aluminum battery cover into it's function. There are no frequency optimized antennae to speak of, any optimization would be done on the pcb, which would be fine except for the effect of capacitance from the broad faced aluminum cover.
https://training.ti.com/importance-antenna-design-optimized-range-performance
Plastic endcaps on the battery cover are supposed to provide an egress for RF emitted, but I imagine their placement presents a narrowed plane of efficient egress.
I believe some firmware adjustments may help the device to better compensate for it's hardware, but as-is there will be a drawback; indoor reception, especially for MVNOs that utilize narrower band access.
The indoor issue will be a result of declining ingress. RF degrades for many reasons as it penetrates building materials. This is specific and the effect will vary with material and frequency.
Add in the integration of the battery cover as designed...
Sent from my tissot using XDA Labs

I have noticed that network is losing connection in some low covered places and it bothers me a lot. My question for that is.. will the problem persist if i install another rom, lets say lineageOs?

dejano said:
I have noticed that network is losing connection in some low covered places and it bothers me a lot. My question for that is.. will the problem persist if i install another rom, lets say lineageOs?
Click to expand...
Click to collapse
I had noticed that too. I can't speak for the devs of Los. I tried 3 ROMs before setting on PE. (I'm a Nexus fanboy ). I think XDA has the best devs that money couldn't buy, so be patient and do your best to contribute.
Sent from my tissot using XDA Labs

Are you still searching for some solution. What if u search for modem settings that was in december 2017? Maybe that will fix the problem?!

dejano said:
Are you still searching for some solution. What if u search for modem settings that was in december 2017? Maybe that will fix the problem?!
Click to expand...
Click to collapse
Yes and no. I'm much more interested in seeing where development goes for this device and doing what I'm able to further the discussion.
Unfortunately not. Prior to the O update, I couldn't call while traveling. If I did get a call out, the quality degraded from from start to drop as I moved between towers. My device works better now than it did out of the box.
Sent from my tissot using XDA Labs

Network signal still drops (all modem versions). I don't believe it's as much a matter of fluctuation as is likely a power management feature. It occurs always in low signal environments and I can regain signal by opening network signal guru which appears to wake the radio. If I let it go too long I can't wake it up and have to toggle airplane mode, reboot, or wait for it to wake up. This makes me think it's a flaw in power management. Is it possible the radio may be scheduled for hibernation or sleep in a low signal environment? Could such an operation not be optimal for the radio function? I know device radios are supposed to scale up and down. It may may not be scaling back up for a number of reasons (too great a packet loss preventing successful network ping?)
Sent from my tissot using XDA Labs

Is it possible to alter the power management values?

Anand Prabhu said:
Is it possible to alter the power management values?
Click to expand...
Click to collapse
I think yes, I also think it's important to point out that while this approach may be broadly helpful it may not be as helpful to everyone.
Unlocked and international/global devices generally have network issues in many parts of the world. It depends greatly on the network the device is used on. MVNOs appear to have the greatest instability in this case.
I'd recommend searching network specific forums before making any changes.
A word of warning;
Changing power management values for the modem could result in catastrophic failure (hard brick).
Sent from my tissot using XDA Labs

findrome said:
I think yes, I also think it's important to point out that while this approach may be broadly helpful it may not be as helpful to everyone.
Unlocked and international/global devices generally have network issues in many parts of the world. It depends greatly on the network the device is used on. MVNOs appear to have the greatest instability in this case.
I'd recommend searching network specific forums before making any changes.
A word of warning;
Changing power management values for the modem could result in catastrophic failure (hard brick).
Sent from my tissot using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply.Network fluctuation issue is bothering from the first day of purchase.When 2 Sims are used the issue is even worse.Playing with different network settings/network reset didn't help.The issue is prominent only when either one or both the Sims have 50% or less network.

Anand Prabhu said:
Thanks for the reply.Network fluctuation issue is bothering from the first day of purchase.When 2 Sims are used the issue is even worse.Playing with different network settings/network reset didn't help.The issue is prominent only when either one or both the Sims have 50% or less network.
Click to expand...
Click to collapse
I don't have the skill to tell you with certainty if your problem is hardware or firmware in nature.
The approach I suggest is to assess (as we've done in this thread), diagnose or rule out (as we're able), and then lastly, intervene.
I'd be very interested to know what has been done by anyone with the power management. I feel strongly that this is one of the root problems, but as I implied, not solely.
If your skill in programming languages is limited as mine is, I'd start with APN settings. If you're using an mvno, you'll probably need a carrier APN too. I've attached a screenshot of my apn menu as an example. All but two are researched and entered by me. Next, I would try looking into some of the resources included in OP.
And finally, if you're much more advanced than I and you're brave enough to experiment with the power management; I'd like to know where that takes you.

As promised.
Both MetroPCS 260 are as provisioned by the Sim card. I am using only one Sim card.

Some recommended reading
https://forum.xda-developers.com/xperia-z2/help/supporting-2-3-frequency-bands-carrier-t3651540
Sent from my tissot using XDA Labs

After a great deal of research, it appears an additional complication is the lack of comprehensive band support. The result is inadequate band aggregation for some users, depending on mobile operator.
There are a few threads suggesting that additional bands may be enabled on our device, and I recall one user reporting success for the device, but I haven't heard anything more.
Sent from my tissot using XDA Labs

More recommended reading
https://forum.xda-developers.com/lenovo-p2/how-to/enabled-4g-ca-p2-t3707584
Sent from my tissot using XDA Labs

findrome said:
After a great deal of research, it appears an additional complication is the lack of comprehensive band support. The result is inadequate band aggregation for some users, depending on mobile operator.
There are a few threads suggesting that additional bands may be enabled on our device, and I recall one user reporting success for the device, but I haven't heard anything more.
Sent from my tissot using XDA Labs
Click to expand...
Click to collapse
Have you checked / have information regarding Mi5X network performance?(since both phones are one and the same)

Anand Prabhu said:
Have you checked / have information regarding Mi5X network performance?(since both phones are one and the same)
Click to expand...
Click to collapse
From what I've read in the forums, it appears that the MiA1 and the 5x have similar, if not the same, issues in this regard. They are indeed the same hardware.

I reverted to nougat 7.12 and the network issue resolved. This issue happened after Feb update.
---------- Post added at 07:08 AM ---------- Previous post was at 06:57 AM ----------
Request senior developers of this community to get the firmware of 7.12 for flashing again after sept update. thanks

Anyone having issues with band 20
https://forum.xda-developers.com/mi-a1/how-to/lte-t3854592/post77886299