Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es
evnStevn said:
Recently, when I decided to receive the OTA for 13 Dev Preview#2, among some of the changes from Tiramisu, or build #1, was my Pixel 6 Pro no longer had the feature Vo5G for voice calls.
This feature with it's own toggle used to reside at the bottom of the internet settings screen, right underneath the setting, "Allow 2G".
I did a beta feedback report on this, and will update this post when/if they find a solution for this issue. es
Click to expand...
Click to collapse
Beta 1 should come out tomorrow, so I guess we will see what happens.
Doug8796 said:
Beta 1 should come out tomorrow, so I guess we will see what happens.
Click to expand...
Click to collapse
Where did you hear the 13 beta would drop tomorrow?
opz187 said:
Where did you hear the 13 beta would drop tomorrow?
Click to expand...
Click to collapse
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse
Gotcha, makes sense now
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Well said, and as I said on reddit:
"The first build was released on 2nd Thursday, the 10th of February. The second build was released the 3rd Thursday, the 17th of March. Due to the dirty pipe exploit and taking an average of the two dates of the month (roughly 13.5 day of the month (rounds up)), the build will almost certainly come out tomorrow, April 14, 2022."
roirraW edor ehT said:
DP1 came out on the 2nd Thursday of February Android 13 Developer Preview 1 is here with themed icons, privacy changes, and more
DP2 came out on the 3rd Thursday of March Android 13 Developer Preview 2 arrives with notification permission requests and other changes
But March was when we had the late update for the Pixel 6/Pro as well (I think), so maybe that affected DP2.
More generally, here's the monthly plan for Betas, although it doesn't mention dates or particular Thursdays, probably because it's always tentative: Android 13 Developer Preview
Click to expand...
Click to collapse
here you go, tell me if you need something more. es
LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
a magenta fan too, I take it? was that what you were looking for? If you need something different just let me know. es
The modem in DP2 is older and less refined than the newer builds of Android 12+.
This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.
LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
LLStarks said:
This is not a modem issue as far as I've seen. It's possible that the early modems didn't support it, but the carrier config is the culprit here. There are clear differences between DP1 and DP2 where a flag that literally says vonr/vo5g is missing.
Maybe I'm doing this wrong, but replacing the DP2 one with the DP1 version doesn't seem to enable it. I was trying to adapt a magisk module to do that. But it's a little weird because sometimes the carrier configs are encoded and other times they are mostly plain text.
At least Google is acknowledging it.
Click to expand...
Click to collapse
Hey, I was just reading your comments, and yes, now, they are acknowledging the missing field. The first time I sent beta feedback on this issue was two weeks prior. They got everything from me, bug report, screen recordings from #1 & #2, as if "the before, and after" weight -loss ads! So a day or goes by, got the buginizer confirmation in my inbox, and I looked for the report filling in the beta feedback app grouped together with others I reported and the whole thing had been deleted, it wasn't anywhere! So I said fuc$ this shi#, I did the whole thing over again, even flashed back to DPB #1, to make sure Vo5G was still there! (lol) This time around, I made mention (several times) throughout my feedback report, that this first report seem to fall off of the radar, and could someone explain how & why, it had to be human error, blah, blah blah, & anyway this time around, it seems to be getting worked, but not vanishing into thin air. A friend of mine that I spoke to about this, got me in his mindset that this was maybe something that wasn't supposed to get out for public consumption until their Pixel 7 Series rollout, of course equipped with (stable) Android 13, and Vo5G Voice Calls included in their "Feature Blitz". To be honest, I'm still not so sure some of that isn't going on, as we all know both Google & Samsung been playing that shi# for years (because they can)!
LLStarks said:
This setting is controlled by the carrier setting. And yes, for T-Mobile specifically it was removed between DP1 and DP2.
Please provide the feedback entry if you have it.
Click to expand...
Click to collapse
hey, thanks for the hit. es
they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.
Beta 1 still doesn't include this.
NewDev4IOS said:
they better include that feature when they release android 13 for pixel 6 series, i currently dont even have voLTE which is extremely annoying, even when i have 2 sims installed, if I make a phone call it disconnects my data on both lines and I am unable to use internet at all, its making me want to switch to another phone.
Click to expand...
Click to collapse
I heard it was omitted (not included) from DP#2 affecting only T-Mobile customers?! It may be just a rumor, others may be experiencing the same as us. I happy to learn we will see it again soon, next update or Android 13 Beta along with Face Unlock!
Doug8796 said:
The modem in DP2 is older and less refined than the newer builds of Android 12+.
Click to expand...
Click to collapse
how did that happen...another of Google's attempts to get all the teams back under one roof, post-covid 19 style-ish, by bringing back the ever popular, "Bring Your Medical Marijuana To Work" week?! lol
The QPR modems have generally been the newest.
But with respect to Vo5G in particular, I'm not really sure where the carrier settings are being read from. Overwriting the protobuf files for T-Mobile doesn't seem to help.
Related
Are there any important difference between NOF26V and NDE63P updates? Any advantages or disadvantages between the two?
I have a Verizon Pixel XL that arrived about a week ago. It came with NDE63P. I immediately enabled developer options and disabled automatic system updates. I have not yet decided if I am going to unlock the bootloader, and I am not asking for advice on whether or not I should. I am trying to keep my options open. I like to keep things simple, which is why I like the Nexus and Pixel phones. Taking an OTA is much easier than sideloading an update. But there are still good reasons to unlock/root.
I am still weighing my options. I don't feel any need to rush right now.
I've read of people having bluetooth or battery issues, none of which I am experiencing right now on NDE63P. Until I make a decision, is there anything other than current security updates that NOF26V fixes or breaks?
Thanks!
Here is a great big disadvantage to taking it as your device sits now. Any ota you take before unlocking the bootloader renders it un-unlockable. So, theres your choice. Unlock and take any otas you want and maintain the ability to customize or not, or, leave it locked, take an ota, and no more choices. You decide.
Sent from my VK810 4G using Tapatalk
wyrdtrtle said:
Here is a great big disadvantage to taking it as your device sits now. Any ota you take before unlocking the bootloader renders it un-unlockable. So, theres your choice. Unlock and take any otas you want and maintain the ability to customize or not, or, leave it locked, take an ota, and no more choices. You decide.
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
I am completely aware of that. That is why I disabled automatic system updates, so I can make this decision after I have had a chance to use the device and decide what changes, if any, I want to make. I am just trying to make an informed decision on my own.
Are there any key differences, pros or cons, between NDE63P and the current NOF26V?
stm8 said:
I am completely aware of that. That is why I disabled automatic system updates, so I can make this decision after I have had a chance to use the device and decide what changes, if any, I want to make. I am just trying to make an informed decision on my own.
Are there any key differences, pros or cons, between NDE63P and the current NOF26V?
Click to expand...
Click to collapse
Many people have disabled the updates but then it mysteriously updates itself and then cry for an unlock, so we are warning you is all. The difference between the 2 is mainly security updates but they did add a few features, like waking the phone can't remember exactly what. Some small tweaks and fixes too. There's change logs somewhere.
jjayzx said:
Many people have disabled the updates but then it mysteriously updates itself and then cry for an unlock, so we are warning you is all. The difference between the 2 is mainly security updates but they did add a few features, like waking the phone can't remember exactly what. Some small tweaks and fixes too. There's change logs somewhere.
Click to expand...
Click to collapse
Thanks. I have read about the mystery updates happening despite disabling automatic updates.
I'll review the change logs, but Google doesn't usually list their "bugs" in the change logs...
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
stm8 said:
I am still weighing my options. I don't feel any need to rush right now.
Click to expand...
Click to collapse
Weighing your options? You have 2 options, unlock or don't unlock. What's the dilemma? Ok, so here ya go. 50% say unlock and the other 50% say stay locked. Solved?
bobby janow said:
Weighing your options? You have 2 options, unlock or don't unlock. What's the dilemma? Ok, so here ya go. 50% say unlock and the other 50% say stay locked. Solved?
Click to expand...
Click to collapse
I am not asking advice about whether or not to unlock, just the differences/bugs/upgrades between these updates.
TonikJDK said:
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
Click to expand...
Click to collapse
Thanks, I appreciate it. That's the kind of info I am looking for!
stm8 said:
I am not asking advice about whether or not to unlock, just the differences/bugs/upgrades between these updates.
Click to expand...
Click to collapse
I understand that but you first need to decide if you're going to unlock or keep the bootloader locked. Because, at some point you "will" upgrade whether or not you are in a rush. I'm just not getting your dilemma. Google has resources which you can search that outline what has changed besides the security updates which you obviously should get. And as you know if you stay locked and update then you're stuck. So once again, your options are to lock or unlock not whether to update or not.
TonikJDK said:
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
Click to expand...
Click to collapse
Are you certain?
https://www.google.com/amp/www.gott...ruary-android-nougat-update-what-to-know/amp/
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Are you certain?
https://www.google.com/amp/www.gott...ruary-android-nougat-update-what-to-know/amp/
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I wasn't 100 percent sure until your link, thanks. From the article:
"From what we’re seeing and hearing the February Android 7.1.1 Nougat update doesn’t actually have any other changes. There are no new features, bug fixes, or performance tweaks. This is simply a security update, like we can expect to see at the beginning of each month."
TonikJDK said:
I wasn't 100 percent sure until your link, thanks. From the article:
"From what we’re seeing and hearing the February Android 7.1.1 Nougat update doesn’t actually have any other changes. There are no new features, bug fixes, or performance tweaks. This is simply a security update, like we can expect to see at the beginning of each month."
Click to expand...
Click to collapse
The problem is that Google doesn't exactly advertise or even admit to any bugs introduced in their updates, whether it's firmware or applications.
stm8 said:
The problem is that Google doesn't exactly advertise or even admit to any bugs introduced in their updates, whether it's firmware or applications.
Click to expand...
Click to collapse
Very true, and Google doesn't disclose fixes much either. So all we can do is give the OP our opinion and experience. I have not seen any bugs fixed, or seen any introduced on my phone. So if he wants to wait while he decides on unlocking i dont think he is missing much. I stand by my advice.
TonikJDK said:
Very true, and Google doesn't disclose fixes much either. So all we can do is give the OP our opinion and experience. I have not seen any bugs fixed, or seen any introduced on my phone. So if he wants to wait while he decides on unlocking i dont think he is missing much. I stand by my advice.
Click to expand...
Click to collapse
But you selectively left out the important part.
Overall we spotted 35 changes to the February Nougat release. At least according to Google’s security blog and change log. That said, eight of them were considered “critical” and needed to be addressed right away.
It's ridiculous to wait. There are bug fixes, You just need to search for them. Personally I don't care what he does, but then he is taking a security chance. I think your advice is wrong. His choice.
Sent from my Pixel using XDA-Developers Legacy app
New update for me to install. I downloaded it, but haven't installed it yet.
I'm in the US on the Sprint network. Showed the August 2017 security update. I can't remember if there were other fixes or updates. It was only 168mb.
Just had it pop on mine in the last 5 minutes... On AT&T in North Dakota, already 50% though updating... I grabbed the url though: https://mobilesupport.lenovo.com/us/en/solution/MS122856
Moto G5 Plus - Maintenance Release Notes
INTRODUCTION
Motorola is excited to announce a new software update for Moto G5 Plus by Motorola. This update brings important improvements to your phone.
For more information on Motorola updates and repairs, visit us at www.motorola.com/mymotog.
NOTE: You cannot downgrade to a previous software version after installing this update.
ENHANCEMENTS
This update introduces changes including the following:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.
INSTRUCTIONS
For a successful installation, we recommend installing this update when the battery in your phone is at least 50% charged and you are connected to a Wi-Fi network.
If you have received a notification message for this update:
Select "Yes, I'm in".
After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated.
If you have not received a notification message for this update, follow the steps below to manually update your phone:
Select the Settings icon in the apps menu.
Select "About phone".
Select "System updates".
Select "Yes, I'm in". After the software is downloaded, select "Install now".
After the software is installed, your phone will re-start automatically.
Your phone is now updated.
Additional Information
If you have difficulty with this upgrade, visit us at www.motorola.com/mymotog.
Click to expand...
Click to collapse
After boot system info for those interested...
acejavelin said:
After boot system info for those interested...
Click to expand...
Click to collapse
Installing now myself.
Does Lenovo ever publish what the changes actually are? Hopefully some security updates.
androcraze said:
Installing now myself.
Does Lenovo ever publish what the changes actually are? Hopefully some security updates.
Click to expand...
Click to collapse
Moto says the same as most other manufacturers... see the post or link above.
acejavelin said:
Moto says the same as most other manufacturers... see the post or link above.
Click to expand...
Click to collapse
Thanks. I've come over from the N5. We discussed my ROM at one point. How are you liking the G5+?
EDIT:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.
androcraze said:
Thanks. I've come over from the N5. We discussed my ROM at one point. How are you liking the G5+?
EDIT:
Android security: Includes the updates of Android security patches through 1 August 2017.
Stability improvements: Includes changes that fix bugs and improve the stability of your phone.
Calling updates: Enhancements to emergency calling functionality.
Click to expand...
Click to collapse
Ahhh... I knew the name sounded familiar and it just clicked.
I like it a lot actually, battery life is amazing and that seems to be my major thing lately, most other things seem of less importance now days, but to be honest it has been a solid device going on 6 or 7 weeks now. It just works.
acejavelin said:
Ahhh... I knew the name sounded familiar and it just clicked.
I like it a lot actually, battery life is amazing and that seems to be my major thing lately, most other things seem of less importance now days, but to be honest it has been a solid device going on 6 or 7 weeks now. It just works.
Click to expand...
Click to collapse
I agree. I have no complaints, and the battery life is crazy compared to the N5. Four days compared to nightly charges.
It's a solid device right now, and appears to more than equal the N5.
I'm on factory for the time being. I may try rolling my own, but this is a different ecosystem than the Nexus world.
Anyone in india got that update??
Another update? UGH! I guess it is going to be like this from now on.... Repetitive updates...
Still on -35 and getting -35-5 announcements. Still haven't even updated to -35-5, -35-67 showed up, now -35-83?
Is it still rootable? Are there FULL FW's so I can upgrade or do I need to upgrade to -35 and let it update to -83? Do I need to be on -35-67 before the -35-83 is capable of being installed?
m4f1050 said:
Another update? UGH! I guess it is going to be like this from now on.... Repetitive updates...
Still on -35 and getting -35-5 announcements. Still haven't even updated to -35-5, -35-67 showed up, now -35-83?
Is it still rootable? Are there FULL FW's so I can upgrade or do I need to upgrade to -35 and let it update to -83? Do I need to be on -35-67 before the -35-83 is capable of being installed?
Click to expand...
Click to collapse
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.
I'm on NPN25-137-67 XT1686 Indian Varient
I didn't got any update?
Can someone grab the update zip? I'm on Verizon and it doesn't show for me....
acejavelin said:
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.
Click to expand...
Click to collapse
Don't get me wrong, updates are great, but not if you are rooted and you have to go through a process to root then reconfigure the phone since it's not an OTA, you have to reflash a STOCK rom to allow OTA's, then you have to root (if possible, not sure if -83 is yet...) and then setup the phone the way you want it..
mikeyinid said:
Can someone grab the update zip? I'm on Verizon and it doesn't show for me....
Click to expand...
Click to collapse
Same here,a update zip would be much appreciated. Thanks
acejavelin said:
You are the only person I know of that is complaining about Moto deploying too many updates. lol
BTW, if anyone is curious this only contains security updates as of August 1, 2017... It still shows as Vulnerable to the Blueborne vulnerability.
Click to expand...
Click to collapse
Huh... Why not wait and add the patch for BB? Odd... So the safest thing to do is to not even be using BlueTooth at all until it's patched? It's been 3 weeks right? 9-12 or was it 9-11 (what a coincidence)
m4f1050 said:
Huh... Why not wait and add the patch for BB? Odd... So the safest thing to do is to not even be using BlueTooth at all until it's patched? It's been 3 weeks right? 9-12 or was it 9-11 (what a coincidence)
Click to expand...
Click to collapse
Well... that's debatable... Although this vulnerability is real, the chances of being effected by it are so remote in most cases is so infinitesimally small that changing your usage habits probably isn't necessary.
Why the August one, probably because that is when they had is scheduled and it was nearly complete when the Sept update came out so they decided to just finish and release it anyway, why let the work go to waste. For Moto it is usually a couple months behind anyway.
acejavelin said:
Well... that's debatable... Although this vulnerability is real, the chances of being effected by it are so remote in most cases is so infinitesimally small that changing your usage habits probably isn't necessary.
Why the August one, probably because that is when they had is scheduled and it was nearly complete when the Sept update came out so they decided to just finish and release it anyway, why let the work go to waste. For Moto it is usually a couple months behind anyway.
Click to expand...
Click to collapse
My bad, I went out of sync with time for a min. It's AUGUST security the one on this -83 (not SEPTEMBER) so I am guessing there is another update coming!
Did you root your -67 (if you have -67?) My bootloader is already unlocked, do you know if Moto will eventually lock this (maybe Google forcing them to any time soon?)
Moto devs can unlock bootloaders and phone has ugly start image but other than that it all works as intended. (BTW, I am using SuperSU and BusyBox on my -35, not the Magisk root - I use Wifi Tether Router and doesn't work with Magisk)
m4f1050 said:
My bad, I went out of sync with time for a min. It's AUGUST security the one on this -83 (not SEPTEMBER) so I am guessing there is another update coming!
Did you root your -67 (if you have -67?) My bootloader is already unlocked, do you know if Moto will eventually lock this (maybe Google forcing them to any time soon?)
Moto devs can unlock bootloaders and phone has ugly start image but other than that it all works as intended. (BTW, I am using SuperSU and BusyBox on my -35, not the Magisk root - I use Wifi Tether Router and doesn't work with Magisk)
Click to expand...
Click to collapse
Another update coming? I suppose, but since we just got this one I don't expect it for 3-4 months and that puts it in the timeframe of Oreo so this might be our last update to Nougat.
As far as the bootloader thing goes, I don't see Moto stopping this or actively blocking rooting, nor do I see Google doing this either.
I don't unlock or root anymore, just don't see the benefits.
mikeyinid said:
Can someone grab the update zip? I'm on Verizon and it doesn't show for me....
Click to expand...
Click to collapse
+1. I'm on 43-5, a Verizon-exclusive update, and am not seeing an OTA. Chances are it's incompatible with my version and I'll have to reflash -35 and get the OTA. I'd suggest anyone else having this issue does as well. I'll report back as soon as I flash.
As of this posting on 11/19 there has been no November update sent to the first gen Pixels Android Developers Image Page.
I know we are guaranteed security updates for the next 11 months, but I feel this is the beginning of the end. Does anyone have any experience with when the sun started to set on previous nexus devices?
Updates usually ends then announced date is reached. Zero Android updates after it. Not sure how huge and critical flaw must be to get an update after that.
They are working on it but there must be a bug they are trying to overcome.
https://www.androidauthority.com/android-november-2018-security-patch-921950/
Sent from my Pixel XL using Tapatalk
Looks like the update was just released. I checked manually and am getting a 47.1 mb update
Security update installing at the moment, on Pixel XL.
pcoulson said:
Security update installing at the moment, on Pixel XL.
Click to expand...
Click to collapse
Really strange that you are getting it over the air...it isn't even posted on the Google Factory/OTA image pages yet. I wonder if this is some sort of Beta or otherwise controlled release...
sb1893 said:
Really strange that you are getting it over the air...it isn't even posted on the Google Factory/OTA image pages yet. I wonder if this is some sort of Beta or otherwise controlled release...
Click to expand...
Click to collapse
Not sure, but is sure taking a while to install for such a small update.
Yep ... slow update ..
smokinjoe2122 said:
Not sure, but is sure taking a while to install for such a small update.
Click to expand...
Click to collapse
Looks like they are posted on Googles official update pages now...
#SeemsFaster
Hi all.
Yesterday, I've got Android 10 on my Moto One Vision (Brazil Variant). But my wife and friends with he same device did not get it yet.
I"m wondering if the release is already official, or only for MFN members? I did register there, but did not receive any survey or anything like that yet (Like it happened with my old Moto G5 Plus).
Did anyone else got the update? If yes, how's your experience with it?
Can you post some screenshots of the version number etc?
I can't upload a screenshot right now, since i'm at work, and uploads are not allowed in the internal network (Sry). But below is the info on the About screen:
Android Version: 10
Android Security Patch Level: November 1, 2019
Google Play System Update: 2019-11-01
BaseBand Version: S337AP_KANE_SGCS_QB2594168
Kernel Version: 4.14.113-g0d0c343-dirty #1 Mon Nov 11
Build Number: QSA30.62
So far, it's been a good update.
Dark theme is great, also, the notifications are a lot better on this one (Divisions between Active and Silent Notifications, as well as the ability to "Seek" the music playing in Spotify via the notification itself).
Gestures navigation were weird in the first hour using them, but now, they make a lot of sense, and "feels natural" somehow.
TheLorencini said:
I can't upload a screenshot right now, since i'm at work, and uploads are not allowed in the internal network (Sry). But below is the info on the About screen:
Android Version: 10
Android Security Patch Level: November 1, 2019
Google Play System Update: 2019-11-01
BaseBand Version: S337AP_KANE_SGCS_QB2594168
Kernel Version: 4.14.113-g0d0c343-dirty #1 Mon Nov 11
Build Number: QSA30.62
So far, it's been a good update.
Dark theme is great, also, the notifications are a lot better on this one (Divisions between Active and Silent Notifications, as well as the ability to "Seek" the music playing in Spotify via the notification itself).
Gestures navigation were weird in the first hour using them, but now, they make a lot of sense, and "feels natural" somehow.
Click to expand...
Click to collapse
What software channel are you using? Also available in About Info and it's very important
I think Android 10 closed beta testing has started by 26/11 for Brazil and India. At least that's what I've seen in tg group.
Yeah, confirmed on Lenovo Forums. Seems like the update is live for the ones that are on MFN only. I forgot i was registered (And did not get any email).
My software channel is: retbr
tys0n said:
I think Android 10 closed beta testing has started by 26/11 for Brazil and India. At least that's what I've seen in tg group.
Click to expand...
Click to collapse
I hope and expect the final release to come in mid/late December. Would be a nice X-Mas gift
I'm from Brazil and I was not subscribed to mfn, I received the update yesterday, it's very good, very fast screen transition, but the app openings are a little slower, but I only have compliments so far, I'm finding it very good
Maintenance Release Notes for December says nothing about Android 10 but I guess we have to wait to be sure. Maybe they update pie first, then Android 10 at the end of the month.
Would be nice if it's stable enough to be released before the end of the year
TheLorencini said:
Hi all.
Yesterday, I've got Android 10 on my Moto One Vision (Brazil Variant). But my wife and friends with he same device did not get it yet.
I"m wondering if the release is already official, or only for MFN members? I did register there, but did not receive any survey or anything like that yet (Like it happened with my old Moto G5 Plus).
Did anyone else got the update? If yes, how's your experience with it?
Click to expand...
Click to collapse
hey man... i thought the phone may not see the update since motorola didn't even announce the timeline on their blog like they usually do, but are there any new additions to the moto app? like swipe to shrink screen, screenshot editor or the features seen in older non-Android One motorola devices?
tys0n said:
Maintenance Release Notes for December says nothing about Android 10 but I guess we have to wait to be sure. Maybe they update pie first, then Android 10 at the end of the month.
Would be nice if it's stable enough to be released before the end of the year
Click to expand...
Click to collapse
No, Dec 1st patch will be released in the middle of January 2020 and Android 10 between Februrary and March of 2020.
rafikowy said:
No, Dec 1st patch will be released in the middle of January 2020 and Android 10 between Februrary and March of 2020.
Click to expand...
Click to collapse
The patches has so far rolled out during the same month, so why do you believe that the pie December patch won't be available untill mid January? Second half of December sounds more right.
rafikowy said:
No, Dec 1st patch will be released in the middle of January 2020 and Android 10 between Februrary and March of 2020.
Click to expand...
Click to collapse
no, what are you talking about? they've been releasing the monthly patches in the same month in mid-late to the same month
@TheLorencini can you send me the oem.prop located at /oem so I can try to pull the update from motos server?
@TheLorencini Please have a look at this app from the attachments. Is an app I've made to try and download OTA updates from mororul servers.
SnoopDoggyStyleDogg said:
@TheLorencini Please have a look at this app from the attachments. Is an app I've made to try and download OTA updates from mororul servers.
Click to expand...
Click to collapse
Hey man, i'm sorry, but i don't think i'll be able to.
As per the requirements for the testing, we should not be talking about the tests on anywhere else except the private MFN forums, let alone help download the update...
I own the third Moto phone. In the base of my previous experiences I guess the stable 10 will not come before the end. I guess any January/February. I would like to be wrong in this case
Received a 94 MB update number PSA29.160-55-7 just now, still has the november patch but i guess its the preliminary update to Android 10 which i expect this month. Fingers crossed :fingers-crossed:
gee2012 said:
Received a 94 MB update number PSA29.160-55-7 just now, still has the november patch but i guess its the preliminary update to Android 10 which i expect this month. Fingers crossed :fingers-crossed:
Click to expand...
Click to collapse
Same for me ....
gee2012 said:
Received a 94 MB update number PSA29.160-55-7 just now, still has the november patch but i guess its the preliminary update to Android 10 which i expect this month. Fingers crossed :fingers-crossed:
Click to expand...
Click to collapse
muppetzoyou said:
Same for me ....
Click to expand...
Click to collapse
haha , it seems it was a global release
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
I assume if your phone rooted, automatically updating will fail
It doesn't, and I lose root, that's what I thought last security update— which is why i'm concerned
christiebunny said:
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
Click to expand...
Click to collapse
Yes tap build 7 times for Developer Settings and disable automatic updatea
You could unlock the bootloader (which would require a device wipe) and then reinstall your current build of Android manually. That would be one of the only ways to officially disable automatic updates as well as update notifications.
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
You may be able to delay it some buy factory resetting and some other things, but it's a big "maybe", and ultimately I don't think there's any way for you to avoid it.
biggiesmalls657 said:
Yes tap build 7 times for Developer Settings and disable automatic updatea
Click to expand...
Click to collapse
The OP you quoted says:
christiebunny said:
I've already got 'automatic updates' turned off, but that isn't stopping it.
Click to expand...
Click to collapse
roirraW edor ehT said:
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
Click to expand...
Click to collapse
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Maybe it was even the same person mentioning it 3 times, lol. Not really sure.
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or just a fluke situation.
Lughnasadh said:
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Didn't go back to check the posts.
Click to expand...
Click to collapse
I think I've seen more than one person report this too, but wasn't sure, and as I always say, I keep forgetting the old stuff. What was I talking about?
Lughnasadh said:
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or something else is going on.
Click to expand...
Click to collapse
I suspect (but pretty obvious) that they have ways of force-pushing updates through despite the automatic update setting (or it's broken in typical Google fashion), but I think it's the former.
Then I believe they made a command decision that the vulnerability is too bad and that they felt they must force it on everyone. Again, given Google's reputation, this could've easily been an accident as well - "who pushed the red button!?!?!?"
And then the further command decision to push over top of modded, or at least simply rooted, devices as much as possible. I wonder what happens in the case someone has truly modified their software more aggressively at the root level. It wouldn't surprise me if it would've still overridden in those cases.
While, of course, those would be questionable actions for them to take (if these are actually true in the first place), I either partially or mostly agree with them, but just on principle, I can't wholeheartedly agree with them. Somewhere in the 40%-99% range.
If true, hopefully this is a very rare occurrence and not going to be how it is from now on. I will wait patiently to observe how things go.
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Annil said:
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Click to expand...
Click to collapse
V4A, at least in my case. I'm not updating until its compatible, or I find a better alternative.
96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
Android 13 cannot be modified is one reason...
Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
Could you explain your theory on this?
christiebunny said:
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Click to expand...
Click to collapse
Compatibility seems remarkably intact, magisk works as intended, and there is no evidence of any change in what control you have.
96carboard said:
Could you explain your theory on this?
Click to expand...
Click to collapse
Modified SystemUI bootloops.
Tulsadiver said:
Modified SystemUI bootloops.
Click to expand...
Click to collapse
Ok? How are you modifying it?
96carboard said:
Ok? How are you modifying it?
Click to expand...
Click to collapse
Same way I always have.
Tulsadiver said:
Same way I always have.
Click to expand...
Click to collapse
That answer really doesn't help anyone.
96carboard said:
That answer really doesn't help anyone.
Click to expand...
Click to collapse
Any like these:
Stand alone Clock, Navbargone, Battery Icon Gone, etc. Mods
For stock rooted only. For most part, these cannot be flashed together. These mods use the SystemUI Patcher Module Template by @Jai_08 By @cool_modules on telegram. After Installing this module, your screen will relock after every reboot of...
forum.xda-developers.com