Related
Well it looks like 5.0.1 has started to roll out to the Moto G 1st and 2nd generation. I hope it fixes the freezing problem I have on my xt1064 running 5.0
Post here if you receive and/or install 5.0.1, and let us know how it works out for you. Such as improvements, bugs, problems with installation, etc. Please include what model you have.
http://www.androidauthority.com/android-5-0-1-lollipop-moto-g-575758/
Indian soak test user received it yesterday
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
gnubash said:
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
Click to expand...
Click to collapse
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
What does that matter, when it's all Lollipop, after all? Would you prefer they release 5.0 and not a more updated, polished release version instead? They'll release on time, believe me.
Yep just got it, lets see what it shall bring!
Sent from my SM-P600 using XDA Premium HD app
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Have successfully upgraded to 5.01 on ma XT1033 BRAZ FRAMEWORK Soak LP N now waiting for XT1068.. Its awesome n more smoother now..
sent From My XT1033{LP} using TapatalK
gnubash said:
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Click to expand...
Click to collapse
It would also be nice if people would also make note of the baseband version associated with each release. There already been enough tears from fools flashing baseband firmware willy-nilly.
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
pastorbob62 said:
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Click to expand...
Click to collapse
Correct
Android The Greek said:
Correct
Click to expand...
Click to collapse
To which question?
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
Correct, 5.0.2 has been released for Nexus 7 today.
And PLEASE, PLEASE before updating go here and try to capture the ota.
kzakhar said:
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Click to expand...
Click to collapse
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
rufflove said:
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
Click to expand...
Click to collapse
You could be right.
I got this phone happy in the knowledge I'll always be running (nearly) the latest clean version of Android, instead I have a phone with a memory management issue running at least a month behind other continents.
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
rufflove said:
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
Click to expand...
Click to collapse
That sounds like the most plausible reason they may have, if they have one. To be honest, I've got better things to think about than when a frivolous software update arrives for a non-cricital device, but your thoughts certainly are rational ones
Well I was part of the xt1069 Brazilian soak test and I have to say it's a bad joke. A lot of users didn't get the update, there was almost no support or even feedback from Motorola in the forum. And to finish it off, they had an issue with their forum software that got all comments deleted. I don't think EU users are missing much
Those who are using Indian soak test before and now using official release in India.... Do you notice any changes?
Sent from my XT1068/69 using XDA Premium 4 mobile app
Soak Testers didn't get the final OTA and will not get it. Reason is, the final OTA rolled out today is the same one soak testers got. They just got it a little early. You can see in the screenshots that everything under About Phone is same in soak test version and final version.
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
bla7e said:
So does this in theory then mean that those of us who installed the captured soak test from the other thread will not need to use any other captures in the future and be able to use the ota update just fine without any chances of bricks etc
Click to expand...
Click to collapse
Correct. It is like we got the final OTA a little early.
Sri2702 said:
Correct. It is like we got the final OTA a little early.
Click to expand...
Click to collapse
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
bla7e said:
Cool so we won't have any worries about our phones bricking if we do an ota as is then I guess? Then that puts me at ease of mind.
Click to expand...
Click to collapse
What do you mean by "we do an ota as is"?
Sri2702 said:
What do you mean by "we do an ota as is"?
Click to expand...
Click to collapse
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
bla7e said:
I mean we'll be able to download ota's without worries of getting our phones bricked because of it being from soak. I remember reading the other day someone was talking about how if we want to be able to use ota we'd have to use a stable capture first in order to be able to use ota. It seems that won't be an issue though since soak and stable are the same with just different release dates so we shouldn't have to worry about that right? Sorry for being silly here. I'm not exactly an ape man when it comes to tech but I'm not feeling the need to fiddle around with roms and bootloaders on this phone when I shouldn't really need to
Click to expand...
Click to collapse
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Sri2702 said:
Well, it was me who said that the other day. That time the official update hadn't rolled out and we thought it would be a newer system version. But, now that it's released; we now know that it is the exact same OTA, so no problems for future updates either. It's like we never installed soak.
Click to expand...
Click to collapse
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
bla7e said:
Yea i suspected something like that was going on when I saw that new thread about the stable and people were saying everything's exactly the same but just wanted some sort of confirmation. Now the only thing that I don't know if it'll affect anything in the future is that my build number on 4.4.4 was kxb now it's lxb (unless k stands for kitkat and l for lolipop lol. dunno) but i don't think it would be a problem since the system version has only the numbers changed and everything else is as it was on kitkat. Seems like the indian release works on european xt1068's as well contrary to what I read some people were saying but I guess it depends on some things...
Click to expand...
Click to collapse
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Sri2702 said:
Funny, but you're right. The Build number on KitKat was "KXB21.85-23" on mine, but now it's "LXB22.46-28".
Click to expand...
Click to collapse
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
bla7e said:
Well that pretty much solved all questions I had regarding lolipop on my moto g. Now the only mystery that remains is if the indian update works just fine when you install it on a eu moto g (well you need to manually install from recovery doe doesn't detect it in the ota screen) why is the eu xt1068's update nowhere to be talked about. All I've seen is india brazil and so on but eu is so silent that even babies can sleep
Click to expand...
Click to collapse
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Wolfcity said:
That´s a mystery for sure!
The only difference between the indian and the european XT1068 is the fact, that the indian version has 16 gb of memory,european model has 8gb.
But there must be something more that differs! In europe even a soaktest is rumored,surveys were sent,so everthing looks like we have to wait in europe for a few more days/weeks.
But why? In another thread I considered that Motorola is afraid of being taken to court or something by european users if something doesn´t work right. European laws are tough. Isn´t that a bit far out?
Or are there any technical differences between these models which are barely known?
Click to expand...
Click to collapse
Aside from the ram I highly doubt there's any real difference since when I got mine in the first few days of fiddling around it had the hindi, korean and pinyin keyboards which i disabled so I don't think that would be the case....I mean why would most eu phones need these inputs from the get go. As far as laws go I can't really see much reasoning there either since it's a 130-50eu phone so they can't really have much to complain and unless it somehow magically bricks the device I doubt there would be many if any at all issues...Dunno doe. I'm not motorola so i have no idea what's going on through their heads but it's just kinda silly to me considering that everything's running fine on mine at least without any factory resets or anything....could be just me doe. On another note I think one of my little gripes about lollipop is that it doesn't hide the signal bar for my secondary sim when it's inactive and just shows it. Is this just for me or does everyone have that cuz I didn't pay attention to that on screenshots the last few days
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
cmahendra said:
Did some one backed up latest Indian Lollipop rolled on 23 Jan in TWRP in recovery mode and uploaded somewhere? Please share.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Sri2702 said:
http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t3002426
Click to expand...
Click to collapse
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
cmahendra said:
The link is old version uploaded on 14 January. I am asking about 23 January version with new Baseband ver 1032.3105
Click to expand...
Click to collapse
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Sri2702 said:
The 14th Jan one does have 1032.3105.
EDIT: Looking at a screenshot in that thread, it doesn't have the above mentioned version.
Weird though, I have installed the same version, but using a .zip captured by one soak tester. How could the version be different, when the update is same?
Click to expand...
Click to collapse
Yes, weird but there is reason. MD5 of old link and new capture matched perfect. Update in link by you and new both are same. Looks like Motorola fooled everyone and rolled same update again.
Anyways! Can anyone share TWRP backup of this version?
some apps bugs ..
Some apps like fifa 15 ut and some others are not supported for locked device and while installing from play store it showed error 505.
Stop making such threads...use the search option instead.
I bought G935FD from Amazon 3 weeks ago- it's unlocked and carrier-free. I've been using it out of the box, no root. Some parts of the box was typed in Arabic indicating it's from/for UAE.
I live in US and have been using MetroPCS (uses T-mobile network). It seems to work flawlessly.
1. Will I get OTA updates? I doubt MetroPCS will do it for this international version from UAE.
2. If above is no, what's the best way to get the latest updates / how do I know my phone has the latest version?
3. What are CSC and PDA?
4. I came across this link: Which country is best for me living in US? Should I continue to use the stock UAE it came with? Any advantage for other countries? (some countries get latest updates faster?)
As for updating FW- a step-by-step guide is appreciated. I've been reading up, and it involves using Odin, but there seems to be tons of different country/region versions for G935FD- and I get concerned about bricking my phone or messing it up.
So many questions.
*#1234 shows:
AP: G935FXXS1APG3
CP: G935FXXU1APEQ
CSC: G935FOJV1APF1
Android security patch level: July 1, 2016
1. You should get OTA updates. They will come from Samsung and not your carrier.
3. CSC is your region and or carrier code that identifies your Samsung firmware.
4. OJV may not update as often as the other UAE firmware (XSG). A lot of Americans run XSG or Spanish AMO. If ya need help. You can PM me and I'll help get ya sorted.
Sent from my SM-G935F using Tapatalk
WhataM said:
1. You should get OTA updates. They will come from Samsung and not your carrier.
3. CSC is your region and or carrier code that identifies your Samsung firmware.
4. OJV may not update as often as the other UAE firmware (XSG). A lot of Americans run XSG or Spanish AMO. If ya need help. You can PM me and I'll help get ya sorted.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks.
1. So why XSG or AMO for G935FD users in US over hundreds of other countries? What's makes those two compatible? If I use other countries, what happens to the phone?
2. Which one do you use?
3. This is bit of a different topic, does your phone suffer from Media Server battery drain? Mine does and that's what prompted me to update my phone hoping there's a fix out (deleting/backing up pics help, but it reoccurs)
acf3passion said:
Thanks.
1. So why XSG or AMO for G935FD users in US over hundreds of other countries? What's makes those two compatible? If I use other countries, what happens to the phone?
2. Which one do you use?
3. This is bit of a different topic, does your phone suffer from Media Server battery drain? Mine does and that's what prompted me to update my phone hoping there's a fix out (deleting/backing up pics help, but it reoccurs)
Click to expand...
Click to collapse
Most people use those firmwares over others because they support Samsung pay. I personally use AMO because it has the add benefit of wifi calling and and white pages. As for the battery drain issue. You shouldn't be having that issue. I know I don't experience that issue with AMO. It could be a problem that was fixed in a later patch.
Sent from my SM-G935F using Tapatalk
WhataM said:
Most people use those firmwares over others because they support Samsung pay. I personally use AMO because it has the add benefit of wifi calling and and white pages. As for the battery drain issue. You shouldn't be having that issue. I know I don't experience that issue with AMO. It could be a problem that was fixed in a later patch.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Nice.
Then I'll give AMO a go, that's this one right?
http://www.sammobile.com/firmwares/download/88307/G935FXXU1APGS_G935FAMO1APEK_AMO/
Install Odin and follow the instructions on that link? Will it wipe my phone/settings? Any other special instructions or cautions?
acf3passion said:
Nice.
Then I'll give AMO a go, that's this one right?
http://www.sammobile.com/firmwares/download/88307/G935FXXU1APGS_G935FAMO1APEK_AMO/
Install Odin and follow the instructions on that link? Will it wipe my phone/settings? Any other special instructions or cautions?
Click to expand...
Click to collapse
That's the correct one. Since you're switching firmwares use the AMO_CSC file rather than the Home_CSC file. That way it'll wipe your phone clean. Make sure youve got security PIN setup because you'll be asked for it after reset. Other than that. Just follow the instructions and it'll be smooth sailing.
Sent from my SM-G935F using Tapatalk
WhataM said:
That's the correct one. Since you're switching firmwares use the AMO_CSC file rather than the Home_CSC file. That way it'll wipe your phone clean. Make sure youve got security PIN setup because you'll be asked for it after reset. Other than that. Just follow the instructions and it'll be smooth sailing.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks. I'm learning a lot here. Getting ready to do it now. More Qs:
1. So with AMO, I can now use Samsung Pay? Is this the correct version for my phone? I presume this is not available on Google Play because it bypasses Samsung bloat if done through the phone? (if so, I need to manually update this app as new versions get released?)
2. Will wifi calling also work too as MetroPCS supports too right? (it did for my previous phone on MetroPCS)
3. This G935F firmware should work flawlessly despite my phone being G935FD right? I think I read this, just making sure.
4. How does whitepages work- AMO comes with it or do I need to download White Pages app?
acf3passion said:
Thanks. I'm learning a lot here. Getting ready to do it now. More Qs:
1. So with AMO, I can now use Samsung Pay? Is this the correct version for my phone? I presume this is not available on Google Play because it bypasses Samsung bloat if done through the phone? (if so, I need to manually update this app as new versions get released?)
2. Will wifi calling also work too as MetroPCS supports too right? (it did for my previous phone on MetroPCS)
3. This G935F firmware should work flawlessly despite my phone being G935FD right? I think I read this, just making sure.
4. How does whitepages work- AMO comes with it or do I need to download White Pages app?
Click to expand...
Click to collapse
You'll need to install the Samsung pay framework and Samsung pay app in that order from APK mirror website. Just read the description for the app before you download to be sure its the US version and it's compatible with the frame work. In order to make white pages work you'll need to enable it from the Phone app settings. G935F works with FD.
Sent from my SM-G935F using Tapatalk
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Sadly no.
Thanks I had a feeling
Have you even tried?
Scott said:
Have you even tried?
Click to expand...
Click to collapse
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
cam30era said:
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
Did this myself. Unlocked bootloader, rolled back from Q to O. Was unable to flash OTA (with locked bootloader), due to being older.
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
ahent said:
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Thanks, I hope it just pushes OTA I don't want to mess with flashing it. By the time I get around to flashing it January may be out and it will be a moot point.
Sent from my Pixel XL using Tapatalk
cam30era said:
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
cam30era said:
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Click to expand...
Click to collapse
IMHO I think the band 4 issues is pseudo.. since it does not update the radio or boot at all.. Unless its a "setting" that's changed that makes it work.
clockcycle said:
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
Unlocked bootloader definitely makes a difference, you can't flash a factory image without it.
Click to expand...
Click to collapse
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Return the phone if you can and get another one. Odds are that the stock on the shelves hasn't been updated yet.
Sent from my Pixel XL using XDA Labs
I have a 64gig 6P on T-Mobile. I don’t know when the issue started, I use the phone as part of the digits program, but the cell signal is constantly dropping. It rotates through LTE, 3G, H then drops and starts over again in a few min. My S7 sitting next to it stays on LTE with no issue.
I thought it was a digits program beta issue so swapped sim cards. Did not help
I was on the android beta program, so took the device off and did a full reset with no additional apps installed. Did not help.
I did a search on the forum and the only advise I can find is to flash an older radio, but I haven’t read anywhere that this helped.
Has anyone found a way to fix this?
Phone is currently stock, non rooted, on 7.1.1 with march update and warranty just expired...
Thanks
gbaz1 said:
I have a 64gig 6P on T-Mobile. I don’t know when the issue started, I use the phone as part of the digits program, but the cell signal is constantly dropping. It rotates through LTE, 3G, H then drops and starts over again in a few min. My S7 sitting next to it stays on LTE with no issue.
I thought it was a digits program beta issue so swapped sim cards. Did not help
I was on the android beta program, so took the device off and did a full reset with no additional apps installed. Did not help.
I did a search on the forum and the only advise I can find is to flash an older radio, but I haven’t read anywhere that this helped.
Has anyone found a way to fix this?
Phone is currently stock, non rooted, on 7.1.1 with march update and warranty just expired...
Thanks
Click to expand...
Click to collapse
Have you tried a different radio?
sting5566 said:
Have you tried a different radio?
Click to expand...
Click to collapse
No, I have not seen anyone say that it has actually solved the problem.
gbaz1 said:
No, I have not seen anyone say that it has actually solved the problem.
Click to expand...
Click to collapse
What radio are you currently on?
sting5566 said:
What radio are you currently on?
Click to expand...
Click to collapse
Whatever the stock one is for 7.1.1 on the march 5th security update.
gbaz1 said:
Whatever the stock one is for 7.1.1 on the march 5th security update.
Click to expand...
Click to collapse
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
sting5566 said:
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
Click to expand...
Click to collapse
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
gbaz1 said:
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
Click to expand...
Click to collapse
You can use fastboot to flash the radio.
gbaz1 said:
Looks like I am on 3.78. Just checked. I wonder if that could be the problem, and if there's anyway to update to 3.79 without rooting and flashing?
Click to expand...
Click to collapse
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
v12xke said:
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
Click to expand...
Click to collapse
Where did you find 3.81 radio?
sting5566 said:
Where did you find 3.81 radio?
Click to expand...
Click to collapse
Both a new radio and bootloader came with the new 7.1.2 image, but it is also available in General. There is a dedicated thread there. If you don't intend on updating to 7.1.2, I'd suggest you download both the baseband (03.81) and bootloader (03.67) and fastboot flash them. If you don't like it, you just flash back.
v12xke said:
Both a new radio and bootloader came with the new 7.1.2 image, but it is also available in General. There is a dedicated thread there. If you don't intend on updating to 7.1.2, I'd suggest you download both the baseband (03.81) and bootloader (03.67) and fastboot flash them. If you don't like it, you just flash back.
Click to expand...
Click to collapse
Downloading now and I might ty out the radio, thanks.
I'm having the same problem on a different carrier. It just started recently. Flashing an older radio did not fix the problem for me.
I loaded 7.1.2 with the new 3.81 but it's doing the same thing.
sting5566 said:
Well I'm using 3.79 on T-mobile and don't have any real signal issues, you could always try 3.78 to see if it helps.
Click to expand...
Click to collapse
v12xke said:
Baseband version 03.81 came with 7.1.2 and is available in the forums. 03.79 was intended for Verizon devices, but I used it on AT&T until 03.81 came out. Have you tried a different APN or modifying your APN. T-Mo has many. I would also try using a different carrier SIM, preferrably a non-MVNO. I've seen a lot of T-Mo users complaining on XDA of constant signal drops, cycling and having to reboot the phone to get it to reconnect to LTE. I hear you with the S7 comparison, but I'm still suggesting you try a different carrier SIM to rule out a hardware issue, which it could be.
Click to expand...
Click to collapse
I'll see if anyone with a different carrier will let me use their sim.
Question have you updated carrier services in the play store?
tnerb123 said:
Question have you updated carrier services in the play store?
Click to expand...
Click to collapse
Yep, everything is updated. Taking off the beta program again to try. Turns out my warranty runs out in April. So going to try to have it fixed under warranty...
Huawei is going to repair or replace it under warranty. I'll post on if this fixed the issue in a week or two.
Guys I am having the same issue. My Nexus 6P went out of warranty this Feb. I flashed 3.72, 3.75 and 3.79 but the issue still persists. I am on AT&T. Has anyone had any success with the newest Radio?
pronoyc said:
Guys I am having the same issue. My Nexus 6P went out of warranty this Feb. I flashed 3.72, 3.75 and 3.79 but the issue still persists. I am on AT&T. Has anyone had any success with the newest Radio?
Click to expand...
Click to collapse
No, but it only takes a minute to try it out. If it doesn't work for you, just flash back to the radio that matches your bootloader. Like many have said the answer is not going to be a different radio.