Is this possible and how can it be done? July update is horrible, full of bugs, empty of fixes and has worsened battery life exponentially.
You can if you use the full image : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
But phone might be wiped, so backup your data. And disable OTA after flash so your phone will not install july update again
novak.vujacic97 said:
Is this possible and how can it be done? July update is horrible, full of bugs, empty of fixes and has worsened battery life exponentially.
Click to expand...
Click to collapse
Allowing you to downgrade means they admit to make mistakes and bring up bugs to new updates that are supposed to FIX whatever was wrong until then.
You can revert by flashing a stock image, but note... you'll start up fresh and next months maybe you'll get a fix for what's wrong this month, or you can get even worse. Because ... why the hell shouldn't we make Android One like iOS and ... phones in the One class get Pixel updates... let's give them Pixel updates with mods by Xiaomi... Then why this program, just for monthly security patches with no bug fixes and even more bugs?
Related
I updated my new Lineage OS device for the first time yesterday to the May 9th build and I had to redo my Tingle patch (which I use to prevent having to use Google crap on my phone).
I don't really care about new features (unless its a theming engine), so should I continue to update my phone weekly, or just check the release notes to see if any security patches are pushed?
If I hold off on updating, will it make it more difficult to get updates OTA in the future?
(I realize this is a major noob question, this is my first Android device.)
z0m8i3 said:
I updated my new Lineage OS device for the first time yesterday to the May 9th build and I had to redo my Tingle patch (which I use to prevent having to use Google crap on my phone).
I don't really care about new features (unless its a theming engine), so should I continue to update my phone weekly, or just check the release notes to see if any security patches are pushed?
If I hold off on updating, will it make it more difficult to get updates OTA in the future?
(I realize this is a major noob question, this is my first Android device.)
Click to expand...
Click to collapse
Can be more changes than just the android security patch level that affects security. I've seen stuff in change logs that indicates replacing the old built-in browser to some new webview based browser, encryption related changes and stuff.
If you don't have any serious issues you could use LOS Changelog or Lineage Downloader for downloading and review changelogs before updating. That could help with knowing if a new build is good for you or if you could skip it without losing out on important changes.
Sent from my XT1650-03 using Tapatalk
z0m8i3 said:
If I hold off on updating, will it make it more difficult to get updates OTA in the future?
Click to expand...
Click to collapse
No
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
https://photos.google.com/photo/AF1QipMGQweIqQu9IQJQpNYtX2M5qKA2qgdgiXq8Jw-Y
https://photos.google.com/photo/AF1QipNPuzUO-CJC00WicsTdNQpFrBZBmv9avNUYY474
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
ATTACK said:
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
Click to expand...
Click to collapse
I have MTK device, XT1771. I got on myne little bit low sound, it was ok but now it is pritty loud and clear sound from him, and fingerprint is better. I didnt try headphones but i think that they are fixed to, i got little lower sound on them, i didnt try them but when i do i will report. xD
Just a hint, If you're using custom recovery DO NOT run the system update. The device will bootloop into recovery, and the only way to restore is wipe data, cache and dalvik, and after that boot into bootloader and type fastboot continue into CMD. This at least worked for me.
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
ya i got update in my device XT1770
Camera
any bugs in the camera? or does it works fine?
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
what were the problems with the clock? she froze?
I got the update three days ago and from what I can tell it seems that the issues with clock freezing and alarm not going off are fixed.
When it comes to the camera, the videos that I took were all very dark, but with the update this issue seems to be fixed as well for me. Pictures, well I was never a fan of the quality of the pictures anyway, I don't know.
Request for stock boot and recovery for this update
I need the recovery and boot of this release to carry on to next OTA update via stock recovery ... But fails to do that. After boot is not stock
Are you 100% stock? That's the only way to take an OTA. I know there were builds here to return to stock, but I'm not sure if they if they deleted. I'll have to look around.
Hi
Have Someone X1944-4 latest firmware to share?
if possible retbr (i am from brazil)
today i got the security update for january. since then, my smartphone has just restarted twice. no idea if the problems like echo voice or something like that have been fixed. hope so. but if the sudden restart continues like this, i'm really disappointed
Got the update as well. None of my problems (see other thread) are fixed. Useless update
It's a security update. Why would it include bug fixes?
Well, it listed an update besides the security update.
And it borked my phone.
"enablefilecrypto_failed"
edit: Attempted to sideload, failed miserably. Gave up and did a factory reset. 4 hours of my life wasted. Guess I am lucky.
gumbyx84 said:
It's a security update. Why would it include bug fixes?
Click to expand...
Click to collapse
I can only hope you will never work for a service related company....
The answer is: because they should / can / must!
Every update is a chance to get rid of some bugs and maaaaaaaan there are a lot of bugs in the first Android 10 release...!
Barthlon said:
I can only hope you will never work for a service related company....
The answer is: because they should / can / must!
Every update is a chance to get rid of some bugs and maaaaaaaan there are a lot of bugs in the first Android 10 release...!
Click to expand...
Click to collapse
Yes they should fix the issues, but it's a security update. They don't bundle bug fixes with them. That's just how it goes.
We have to hope bugs will be fixed before the model is excluded from support (October?), cause even custom ROMs rely on the stock vendor partition unless there will be someone who will work with it.
Can anybody describe to me in short lines about latest software update (official ofc) which as i see is november 2020 update in my place, Europe - Serbia. Is there any big/new changes in comparation with stock one? Battery life? Bugs? I got new phone, currently is everything stock and i am completely satisfied with everything, even without gms and rest things....just wanna know about those updates, do i missing it or isn't much big deal. I see there is roll back too using hisuite, one more thing that encourages me.
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...