Database Develop

[Q&A] CM-12.0 (LP) UNOFFICIAL nightly builds

Q&A for CM-12.0 (LP) UNOFFICIAL nightly builds
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for CM-12.0 (LP) UNOFFICIAL nightly builds. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Is this a unified build for all carriers?

network issues with xt1093 uscc
great rom! everything seems to work smoothly. the only issue i have had is trying to connect to my network. Do i need to configure the APN to my carrier or is there something i am missing? i installed correctly using TWRP, factory reset, flash zip, cleared dalvik, reboot,....

I'm assuming we'll lose the moto things like active display and the phone talking when at home and on the road?

network issues with xt1093 uscc
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.

NOOBSABOT said:
Well i flashed back to stock and had the same network issues with my stock rom. i found a number to re-register on the uscc network. it took like 15 seconds on an automated line and everything was setup, could make calls out, receive calls, texts, data,...etc.
I tried to reflash the newest nightly (01/16/2015) and setup the network using the same number from before. Had to change the network config file and modify the APN to my network. the config was LTE/CDMA/GSM auto (PRL) (prior to that it was set to LTE/GSM auto (PRL)) that put me into roaming long enough to dial the setup number. the setup went fine but after it finished......Nothing. i couldnt even force roaming in the network config.
I am thinking this is a modem firmware issue. I dont have an logcat files (working on that now). i tried to flash the stock modem firmware after flashing the nightly but didn't help
Still an awesome rom and would love to get networking running for this device.
Click to expand...
Click to collapse
I think that the radio is broken on the last couple of nightlies across many different devices. Try an older version and see if you have better luck.

i'm on stock 5.0 rooted xt1092
doing nandroid and flashing last build this evening.

flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?

michyall said:
flashed and no problems found, but have no more root permissions, do i have to re-root using chainfire?
Click to expand...
Click to collapse
Did you enable it in developers options?

matt99017d said:
Did you enable it in developers options?
Click to expand...
Click to collapse
Yes sir. I've solved fastbooting again CF. Maybe after format you loose root permissions.

No Network
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.

CrepuscularSoul said:
I've flashed several of the nightlies (both early and most recent) and none of them have a network connection. I've tried factory resets, cache wipe, the usual and no luck. Is there a specific baseband version I need to be on or any APN tweaks I need to do?
[edit] I have the tmo pure edition fwiw.
Click to expand...
Click to collapse
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).

crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
---------- Post added at 01:31 PM ---------- Previous post was at 12:38 PM ----------
CrepuscularSoul said:
I'm pretty sure that's what I'm on. System is 22.21.11.victara_tmo.en.US, build LXE2246-11, and Baseband MSM8974_4125.184.08.27.01R
If that's not the latest let me know and I'll grab the updated ones and flash those through fastboot and try again. If they are is there anything I could grab with the syslog app or adb that might help in figuring it out?
Click to expand...
Click to collapse
Got it. The APN protocol for fast tmobile com in my stock rom was IPV6, and when I flashed this it was IPV4. Changing that got my data connection working.

crpalmer said:
I don't do anything special on tmo pure edition. I installed the official LP update so I am on the latest baseband (which I recommend using).
Click to expand...
Click to collapse
I have the T-Mobile pure and left the base as 4.4.4 and flashed cm12. Signal is awesome as are the transfer rates.
I've tried liquid and slim with the same results.

How will the battery? Better or worse than stock?
Works in XT1097, right?

I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?

loic5032 said:
I did a clean flash on my xt1092. On reboot I get a screen that says encryption failed, with a button to do factory reset. Doing factory reset just brings me back to this same screen. I don't even think that my storage is encrypted on stock. Any help?
Click to expand...
Click to collapse
you have to go into TWRP, then WIPE then Format Data. then install rom and gapps.
you will format your memory loosing everything on your phone. i used to plug an usb otg with rom and gapps files.

double tap
Can we get some double tap to wake love? That was basically my favorite thing about my oneplus one and i put cm12 on that and works great
Let me know if thats going to happen or not because i cant live without that or the moto display

I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed

michyall said:
I think double tap to wake is not an interesting feature for a phone. Sure for a tablet but for your victara not. Waking up every two touches is not a good way. Ambient display is the best way for me, as good for looking for notifications as for unlocking.
I prefer power button indeed
Click to expand...
Click to collapse
Well i mean just having the option would be nice
its personal preference and my case makes it very difficult to press the power button

MRA58R build?

Alright, so I just flashed MRA58N yesterday, and today there is a new MRA58R image added? What's the difference here? The first build was a security update, but what's this new one? And why only a day difference? Thanks!
Sent from my Nexus 6

Changelogs aren't made readily available.
Perhaps this script will help people who update their local AOSP repo's will help.
https://groups.google.com/forum/#!msg/android-building/0DtsHawjs4k/And8o3Dni_UJ
Obviously some modification will be required

I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html

Quetzalcoalt_Lp said:
I'm in the same position. Yesterday I flashed the MRA58N build and today I saw they already uploaded the MRA58R build, LOL, so annoying.
http://www.androidpolice.com/androi....0_r2-to-android-6.0.0_r4-AOSP-changelog.html
Click to expand...
Click to collapse
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6

I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.

Rektifying said:
I am currently running 6.0 MRA58R / Rooted / No Encryption. I notice no difference at all between N and R. Not that I would anyways. I'm wondering what the difference is myself.
Click to expand...
Click to collapse
What kernel are you using?

H4X0R46 said:
Damn, I wonder if it's even worth flashing! I installed MRA58N and then re rooted my phone, reinstalled all my apps, reinstalled multirom, etc. Took a while, wonder if it's worth flashing!
Sent from my Nexus 6
Click to expand...
Click to collapse
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.

scryan said:
Did you do a full wipe/flash? You only really need to flash system... You'll need to reroot after, but don't need to mess with your apps and what not...
If you want to be a little more complete, flash boot, bootloader and radio too, none of which will mess with hour apps...
But if you flash boot, you will need to reflash your kernel and if your unencrypted you have to make sure you boot straight to recovery and flash kernel WITHOUT booting android.
Click to expand...
Click to collapse
I never do a dirty flash just to avoid conflict, but I guess it couldn't hurt to try right? So not wiping userdata should work?
Sent from my Nexus 6

If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...

I have always had zero issues applying newer stock images over older stock images on a Nexus device. I do this all the time when the OTA is not available and only the main updated Google Factory image is available.
I think the trick is to always wipe dalvik and cache after a flash of system and use TWRP that supports encryption. When you wipe the dalvik and cache the system acts like an OTA and performs an upgrade on all your apps. I *think* it effectively rebuilds the cache for all apps, but it never touches the app data or user data (sdcard/pictures/etc).
I also always flash the radios and bootloader *IF* they are updated from the last image. I used to flash the stock boot images too, but now that looks like from a going forward point we won't be able to do this and have root. I do look forward to system-less root

scryan said:
If its just the monthly updates, I wouldn't touch userdata.
If your on completely stock kernel, and encrypt do bootloader, boot, radio and system
If your unencrypted, flashing boot occasionally may help update ramdisk, but you run the risk that someday your tired or otherwise not paying attention and you boot android and it re-encrypts/wipes your device. Never done this so I am not sure if you would have the chance to stop it, or if it would just start formatting userdata out of nowhere...
Always best to take a backup right before. Then if there are issues you can restore backup things individually and install clean.
If I were on stock, most the time I would likely just backup, fastboot flash system.IMG and call it good unless issues popped up. Occasionally I would update bootloader/radios/boot... Maybe every other/every three... When people were talking about benefits of doing so here...
Click to expand...
Click to collapse
Cool dude! Thanks for the advice! Yea, I use ElementalX kernel on my device, unencrypted device makes no noticeable difference for performance to me, but the battery life is another story! ElementalX has superb battery life!
Sent from my Nexus 6

Any word on the changes between this and previous build yet?

Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.

dahawthorne said:
Surely we expect the security updates to show no visible differences? When my antivirus updates itself I don't ask to see the changelog, since it has no effect whatsoever on the machine's performance or user experience, no...?
If the security update is doing what it's supposed to, the only difference is that one day you won't see your device pwned.
Click to expand...
Click to collapse
The security updates were also in the previous build, MRA58N.
All we really know for sure is that the OTA for MRA58R is being pushed out by Verizon. The OTA path skips MRA58N.

Pushed out by big red.... I think that's something I'll definitely wait on.

jbeezley said:
Pushed out by big red.... I think that's something I'll definitely wait on.
Click to expand...
Click to collapse
I've never had a problem with their updates and, realistically, this is actually a Google update. I'm just impressed that they're leading the charge.
I'm on MRA58K after sideloading the first Marshmallow OTA. I just noticed there's an OTA from K to N but there's nothing from any Marshmallow build to R.

I'm on N and haven't seen anything detailing what's different in R. I'm just a bit suspicious of anything pushed by Verizon, although you are correct @GilmourD3. It's Google's update, but why would Verizon spearhead the rollout? I would rather just stay on N awhile until we have someone in the know look over the details of the update to R.

I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.

H4X0R46 said:
I flashed it and I see no difference, I'm running it rooted with that custom kernel I mentioned earlier, it runs exactly the same as N so my guess is just very small bug fixes that don't change anything on the user end.
Click to expand...
Click to collapse
Anything change from K to N? I might just sideload the N OTA since I'm currently on K and I'm not finding an OTA path from K to R.

R is apparently the OTA update to 6.0 and the November security update for Verizon Nexus 6. My wife got it Thursday and her build and security date both changed.

[ROM][STOCK[MM 6.0]XT1096 verizon flashable stock rom

Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
None as of now.
Downloads:
Current version
Custom rom with new build.prop by yahya1054:
Download

AGISCI said:
Due to the request of various members I have started a topic here for the rom for the xt1096 verizon model with android 6.0 marshmallow. This rom was developed by @hutchjim using the xt1097 marshmallow as a base.
Installation:
To install the rom, flash the zip from a custom recovery such as TWRP/CWM/etc.
Root:
To root this rom @donslade has stated that the files for the XT1095 work for it. They can be found here: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Known issues:
Some people are experiencing an issue where it says they are roaming.
Downloads:
Main download
Mirror 1
Click to expand...
Click to collapse
What the difference between this rom and 1095 MM Rom

kaktusmaier125 said:
What the difference between this rom and 1095 MM Rom
Click to expand...
Click to collapse
This one has support for verizon cdma. It is only useful for people who use verizon service.
Sent from my XT1095 using Tapatalk

AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade

donslade said:
AGISCI - Thanks for creating this thread. I hope we will have participation from folks who will test and provide feedback. I also hope that hutchjim will also provide info on how this ROM was created and what changes he made.
I believe the ROM is debloated from most of the Verizon apps and installs TWRP 2.8.7 as recovery. All of the Motorola Apps are there and function as expected from my experience. My phone connected to Verizon for voice and data. I do not know what other changes were made.
My experience to date has been mostly positive with just a few issues. I'll list those in a message a bit later. For now here is my interpretation of hutchjim's installation instructions:
1. Perform factory reset/wipe. THIS WILL WIPE YOUR PHONE AND ALL DATA ON IT. Either the built in reset/wipe of using TWRP. I used TWRP 3
2. Flash ROM
3. Perform another reset/wipe. I used TWRP 3
4. Phone will boot to initial setup. Follow prompts. Hutchjim says not to setup wifi during this phase but I see no way to avoid that. I connected to my home wifi at this point and continued setup.
5. As soon as you can go into Settings go to Cellular Networks > CDMA and select RUIM. No other changes should be made in the Cellular settings. You can also go to Backup & Reset > Reset Network Settings and reset there. Verify that the CDMA > RUIM setting is still selected.
6. Reboot and verify network settings.
7. Continue setup/restore from previous backup from Google. Any apps that need updating for MM will do so during the restore.
Doing the above results in a phone running 6.0.1 which identifies itself as a XT1097. I'll post a screen shot of the ABOUT phone screens later.
To root I used the files from here:http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Flash using TWRP
1. root-boot-6.0-xt1095.zip
2. UPDATE-SuperSU-2.65.zip (there might be a newer one out there but this one worked for me. It should update later if needed)
After this I was able to install the latest Exposed framework and app, Gravity MM, XGELS and AOSPSignal icons modules with no problems.
I had been using this ROM with no real issues since last Friday. Legacystar reported that his phone was Roaming after he installed the ROM. Mine was not Roaming worked great - until this morning when it went into Roaming a couple of hours ago. Nothing I did could make it change back. I restored a backup of this ROM from Saturday but the phone is still Roaming. I've now gone back to my last 5.0 backup and will try to reinstall the ROM later when am back home. Will update then.
Here is a list of items I think we need more info on:
1. What was the base ROM for this? I think it is XT1097 based but it may be XT1095 since the XT1095 root files work.
2. What changes were made to get this to work wit the XT1096 radio and allow CDMA operation?
3. How do the Cellular settings work and how can they be improved for this ROM?
4. How to bypass the network setup screen during initial MM setup?
Hope this helps. I'll update more after work and when I reinstall the ROM. Until then I hope more testers chime in with their experiences.
Don Slade
Click to expand...
Click to collapse
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk

Thanks for the update. I had notice that it did say retla in the system version. Need to pay attention to the baseband info.. Based on that I don't need to upload the About Phone screens then.

Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk

RamAir02 said:
Very excited for this. Do gapps need to be flashed as well?
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
It's a stock rom, gapps are in it already.
Sent from my XT1095 using Tapatalk

AGISCI said:
1) It is based on xt1097, specifically on retla which is the retail latin america variant. I am not surprised that the root files for xt1095 work since the xt1097 and xt1095 are extremely similar.
2) He sent me a list of some of the changes, I will dig through the files modified to get more details on what changed.
I was sent a new version by @hutchjim, it is uploading to google drive now. Hopefully in the new version the roaming problem is fixed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
has this new version been uploaded yet?

Legacystar said:
has this new version been uploaded yet?
Click to expand...
Click to collapse
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk

AGISCI said:
It's uploading right now, for some reason my connection is super slow today. I will post as soon as it's done uploading.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
awesome, thank you. any idea what he did to fix the roaming issue?

Legacystar said:
awesome, thank you. any idea what he did to fix the roaming issue?
Click to expand...
Click to collapse
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk

AGISCI said:
He said he added a verizon app in priv-apps.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
might have been the verizon apn app

Alright, sorry for the long delay. My internet is messed up right now. I started the upload last night and left it running. I woke up to a failed upload message. I started it again and it took 5 hours to upload... anyway, I have updated the first post with the link to the new version. Please try it out and let us know if you have issues with roaming still.

I have had the roaming issue since I installed the original MM posted a few days ago but even though the R is showing by 4g it still allows me to access data through 4g. Hope I am not going to incur the financial wrath of big red. lol. I was reading this forum using it. Anyway, I want to say thanks for those putting in the work to try and figure this out and support a stock MM rom for the xt1096. I will test the new version as soon as I get it downloaded and report back if the roaming issue persists for me.

I have updated to the latest version of stock MM offered on first post and can confirm that the R roaming symbol is gone. I have rebooted several times and finished setting my phone up how I want it. The only issue I had during the process of installing and setting up this version of MM is that upon rebooting the first 2 times I had a pop up saying "Unfortunately, Verizon Login has stopped."
I rebooted into twrp and installed reinstalled the root and su zips and upon reboot the pop up went away. I guess I was wrong to assume that the order for installing the zips were 1)root boot for 1095, 2)Super SU and 3) MM Rom. After reading that in order it makes more sense to load the Rom then the root and su zips. Oh well, all is well that ends well.

Has anyone figured out how to bypass the wifi setup screen during setup?

Wrong forum.

i just loaded the new version and still getting the roaming. also having the verizon app crash on startup.

To skip WiFi setup, put sim card in on welcome screen so after boot put sim,
also roaming is gone for me but I just get data, no voice on some reboots voice aval even when it says out of service same last build.
Roaming was an issue older build new build fixed, voice still wonky for me

Sim card issues after 7.1.1 update

Hey,
Just got a OnePlus 3T (Midnight Black) for my wife and wanted to get it rooted and updated to 7.1.1 as soon as I got it. I followed TK's suggestion on his video on using Opera VPN to change my region to Canada and got the update on the first try. After all was said and done I put my wife's sim card to start using the device and the 3T will not allow me to send phone calls, texts, or use data unless connected to Wi-Fi. I wasted a lot of time with AT&T thinking it was the sim card that was the issues but the device does receive text messages and calls so I am lost. The community on the OnePlus website has others who have issues after updating also to where their devices don't recognize the sim card(s) but they all seem pretty lost on any fixes to the issue. Anyone else have something similar or any solutions? Thanks in advance for anything positive.

No, I don't face this type of issue Sorry

After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.

I've always had an issue having the SIM card show up. I have to eject and reinsert the SIM slot after a reboot with the phone still on.

SIM issues after update seem to be a known problem on this phone, according to the following post. Either do a clean install of the full OTA, or do factory reset (somewhat obvious, backup any data you want to keep before doing either):
https://forum.xda-developers.com/showpost.php?p=71825477&postcount=1104

pitrus- said:
After the 7.1.1 update, did you do a factory restore to make sure no data structures for the old ROM/apps is in place that could cause issues like this? In other words format the data partition.
Click to expand...
Click to collapse
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.

rsnyc said:
I did do a factory reset, one from settings and then two others from TWRP. I thought about it some more and since the 3T is so close to stock Android I remembered what another member suggested as far as flashing a previous version of the OS (like one would do with a Nexus device). I flashed the OnePlus 3T 7.0 version and it's working now for my wife. I downloaded the update straight from the OnePlus website. I do miss the features 7.1.1 brought but I guess I need to wait for OnePlus to iron out the bugs. Thanks all for the suggestions! Much respect to the XDA community.
Click to expand...
Click to collapse
Unless you do like me, and run latest Lineage OS (Cyanogenmod), then you'll get 7.1.1 and working dual SIM. ?

T-Mobile Oneplus 7 Pro Android 11 Update

The T-Mobile website is showing the update is complete and it is going out to devices. Has anyone received the update?
OnePlus 7 Pro: Update to Android 11
OnePlus 7 Pro Software version: Android 11 Phase: Complete The software has been approved to launch and is now available. When it's ready for you, your device will provide a notification that t
www.t-mobile.com
Wondering if anyone has taken the update and been able to keep root and TWRP.
Edit: Just getting the update now. Will let you know how it goes.
Edit 2: I was not able to keep root and TRWP, the update installs after it restarts so flashing the TWRP retention script then Magisk into inactive slot just cause the update to fail. Will have to boot TWRP then install both liked normal I hope...

Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root

_-..zKiLLA..-_ said:
Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root
Click to expand...
Click to collapse
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.

DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk.
Click to expand...
Click to collapse
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download

_-..zKiLLA..-_ said:
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download
Click to expand...
Click to collapse
I will try some more versions of TWRP tonight hopefully. I had to stop and work. E should be able to use the normal process, just need a working TWRP.

Twrp isn't supported for oos11 on 7 series yet

I haven't seen the rom to download...but switching to inactive slot should work....for magisk...if not...search how to extract n patch boot.img with payload dumper and magisk....I did it super easy...however...while doing I decided to install magisk to inactive slot (Global) and install keep_data.apk n all went well ...so I didn't have to push the rooted boot.img externally

DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.
Click to expand...
Click to collapse
Same issue with the speaker here too.. this is on a virgin/untouched t-mobile 7pro

I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?

to the guys having that speaker issues are you guys having black screen issues at 90hz and wake up issues at full resolution?
because I have those all those.

Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.

Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
toggling the bluetooth on and off works for me

technocrat7 said:
toggling the bluetooth on and off works for me
Click to expand...
Click to collapse
Do you have to do this for every call, or does it work after doing it just once?

tperki said:
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.
Click to expand...
Click to collapse
do you have to do this every boot or just once?...because i downgraded just like you to 10 because it was annoying and the worst is the lockscreen dpi change that made it hard to put my fingerprint or pattern...forcing me to reboot...

A few days ago I got another update. It fixed the speakerphone issue.

guitardoc64 said:
A few days ago I got another update. It fixed the speakerphone issue.
Click to expand...
Click to collapse
Can someone upload the TMobile update?? Why is it nowhere online?

teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
OnePlus7ProTMOOxygen_11.O.20_GLO
Full Android 11 T-Mobile OTA ,Haven't seen it anywere . If for some reason someone needs. Don't think you can flash with twrp, but I have unpacked and flashed in fastboot...
forum.xda-developers.com

does anyone have a oos 10 tmobile rom that i can use to downgrade?

teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com

weakNPCdotCom said:
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com
Click to expand...
Click to collapse
People do not know how to get root with the stock Tmo Rom. Took me forever to figure that out.