Related
So yeah, I updated to a Dev build about a month ago so I could mess around with it. Slightly buggy though (Google keyboard has totally crapped out on me now) so I'm anxiously awaiting the public release.
Is it a simple update affair or have I gotta do a restore?
CasuallyDressed said:
So yeah, I updated to a Dev build about a month ago so I could mess around with it. Slightly buggy though (Google keyboard has totally crapped out on me now) so I'm anxiously awaiting the public release.
Is it a simple update affair or have I gotta do a restore?
Click to expand...
Click to collapse
it is available and you can download the image from google site and flash it. Note: this will wipe your device, so take required backup of your data.
kmaq said:
it is available and you can download the image from google site and flash it. Note: this will wipe your device, so take required backup of your data.
Click to expand...
Click to collapse
Thanks for the link, didn't realise it had been put up yet. I've just installed build lrx21p (I'm assuming this is the correct build for the latest public version) using NRT. All is good again!
Any exciting improvements in the newest beta firmware? Hopefully the battery drain problem got solved.
They can't speak, they signed NDA
While we do have a policy to not talk about the Betas themselves, I can report there are no Betas as of recently...Take that info however you'd like
what about marshmallow update then..
Well im betatester but i unlocked bootloader so i cannot have more OTA.. i'll just say that today there was another OTA with minor fixes.
gREENNNNN said:
Well im betatester but i unlocked bootloader so i cannot have more OTA.. i'll just say that today there was another OTA with minor fixes.
Click to expand...
Click to collapse
WW_2.20.40.164 ... but its only bugfixes.
i have just got this update on my mi5s, is it good?
No idea you tell us as bugger all on my Mi5S.
I checked the Update app, didn't get the update.Is this a soak test of sorts?
It's out for the Mi5S Plus maybe that's what he is on about.
silverblack said:
It's out for the Mi5S Plus maybe that's what he is on about.
Click to expand...
Click to collapse
no, me also got update for my MI5S
Just released today for the Mi5S apparently ,but not for me.
It's likely another "leak"
Download link directly to xiaomi's server:
Recovery
http://bigota.d.miui.com/V8.2.1.0.MAGMIDL/miui_MI5SGlobal_V8.2.1.0.MAGMIDL_fde8a722df_6.0.zip
(I don't have the link for fastboot ROM)
It hasn't been officially released.
It's a nightly pushed to a number of users.
---------- Post added at 22:20 ---------- Previous post was at 22:12 ----------
Here's the link:
http://bigota.d.miui.com/V8.2.1.0.MAGMIDL/miui_MI5SGlobal_V8.2.1.0.MAGMIDL_fde8a722df_6.0.zip
Pictures and link has been taken from official forum.
I'm using xiaomi.eu, so I don't know how this ROM is working.
If in doubt, check the official forum.
Got it installed, sofarno problem, they fixed some UI bugs I was angry about too.
Seehank said:
Got it installed, sofarno problem, they fixed some UI bugs I was angry about too.
Click to expand...
Click to collapse
Except that now you should have the qfp-service bug, like in China or Xiaomi.eu version.
https://forum.xda-developers.com/mi-5s/help/miui-eu-7-2-9-poor-battery-life-t3557879
gnazio said:
Except that now you should have the qfp-service bug, like in China or Xiaomi.eu version.
https://forum.xda-developers.com/mi-5s/help/miui-eu-7-2-9-poor-battery-life-t3557879
Click to expand...
Click to collapse
Or not, we will see. I let you know.
gnazio said:
Except that now you should have the qfp-service bug, like in China or Xiaomi.eu version.
https://forum.xda-developers.com/mi-5s/help/miui-eu-7-2-9-poor-battery-life-t3557879
Click to expand...
Click to collapse
There we go, its eating battery like crazy How do I fix it my friend?
Big amount of users from 4pda report that they don't have troubles with battery.
My phone is running Stable 8.2.3.0 MAGCNDL for a couple of weeks and it's more stable than previous version, at least when I take screenshot, the preview doesn't super-fast-blink.
Hence that my mom phone (Mi 5) has been running that version for about 2 months before my phone was updated. Yes, it's a stable version, not nightly or any kind of experiment...
If your device is rooted, freeze the app com.qualcomm.qti.biometrics.fingerprint.service
If not, try disabling any kind of unlock with fingerprint and delete all saved fingerprint.
After using it since Friday, its a pretty nice update. I liked the new quick toggles animation and the overall smoothness is improved.
i have it on my mi 5s and is good.
I prefer custom ROM like LineageOS because, even if it is official, it is less complete and usable
Hi guys, mi5s on 8.0.3.0 here. Should I flash this or should I wait until the ota comes?
You should wait. There are chances that the version we will get might be 8.2.3.0 (or similar) which includes a few more fixes to found issues.
have you read something about when it will be released?
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Update has landed. Found links on teammt site few moments ago.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v133897/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L24_hw_usa/update_full_BND-L24_hw_usa.zip
http://update.hicloud.com:8180/TDS/...97/f1/full/public/update_data_full_public.zip
MD5 verified numbers ( from my working downloads)
Code:
e75a21769f049430840ea900b11600c4 c:\android\honor_7x\l24-oreo\update.zip
73414b5383e5fb3391e77a13c17dca53 c:\android\honor_7x\l24-oreo\update_data_full_public.zip
122f0e91d77fba6e399300926d1ef289 c:\android\honor_7x\l24-oreo\update_full_bnd-l24_hw_usa.zip
So can I just flash those update files with TWRP and be good to go?
I don't know if that's the stable or not, I've had that version for over a week now.
My update says C567?
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
johncro13 said:
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
Click to expand...
Click to collapse
Why would it be available if it's not official? I don't get that lol. The app is a little funky.
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
mparma13 said:
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
Click to expand...
Click to collapse
I'd say weeks, but that is just a hunch based on my experience with the rollout of the previous two patches... Once again, it would have been nice when Honor USA announced it that they didn't just say "Coming April 30" but instead were a bit more honest about how the release was being pushed out.
They shoyld have said that it will be around a certain week or something cause the frustrating lag is killing me badly and i even have a Oneplus 5t...but still is the worst lag i have seen in since 2013
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
mrmazak said:
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
Click to expand...
Click to collapse
How did you install it?
allrockedout said:
How did you install it?
Click to expand...
Click to collapse
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
mrmazak said:
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
Click to expand...
Click to collapse
Ok thanks I'm on stock bootloader still locked I'll just wait for official update
yeah....
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Looks like they crapped the bed on the update....
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this hype about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
pcaseiro said:
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this the about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
Click to expand...
Click to collapse
Well some group is getting it(probably beta testers), because it is on firmware finder
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
allrockedout said:
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
Click to expand...
Click to collapse
Then why would they be so set on the 1st, shouldn't they have said the 2nd? Lol
Anyone receive official update yet?
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...