Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return (to be clear, I'm not saying this was the major factor in pulling the release - but it doesn't look good imo)
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com
Luckily I did not manually install it.
By the way, nicely done gGoolge! You've got enough information already and don't need people as guinea pigs for now.
I hope the coming up January update is workable and doable, I can not expcet an outstanding update, Google.
Alekos said:
Well, there you have it. For all those people who said it was my fault for flashing the December build and corrupting my 6 Pro - almost to the point of no return:
Google delists faulty December 2021 update for Pixel 6 & 6 Pro, preventing manual updates
Google has now removed the Pixel 6's faulty December 2021 update from its website, to prevent it from being manually installed.
9to5google.com
Click to expand...
Click to collapse
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.
bouchigo said:
I don't think they removed it because it was corrupting people's phones.
Most likely it was due to the many complaints of connection issues people were/are having, though I didn't experience any issues... I'm currently on ProtonAOSP just to test it out.
Click to expand...
Click to collapse
yeah that's fine. I agree. I should edit my post. I think there's multiple issues with this build. lots of reports of people corrupting their phones on this build. none for October or November, many for December. Can't say exactly why that is - but I feel there's a lot wrong with the December Build (not just connectivity issues). This is pretty huge. For Google to pull a build? I've only heard that once in the past 8 years for Google to do that.
December build works perfectly for me lol
P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.
Morgrain said:
The ancient problem. Some people are affected, others are not.
Now imagine that Googles QA consists of 10 people and all those 10 people were people with "build works perfectly for me" - so they pushed it out to the public, and kaboom.
I guess Google can only improve this process, by widening the QA across the globe (they need to test firmwares in all countries of sale + more device variations, meaning some with Google Backups, some with Backup transfers from an Iphone, from a Samsung, from an old Google etc.) - I have the feeling that they only test their firmwares on brand new devices, and we can see in this forum how many issues come from backups). Since - apparently - testing it in the USA does not help much for European network problems.
Click to expand...
Click to collapse
Yes sure you are right but it's kinda weird what they did there.
P6P said:
December build works perfectly for me lol
Click to expand...
Click to collapse
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not using Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Alekos said:
the thing is, to pull an update is kinda crazy. and the issue seems to mostly be in EMEA (and some parts of North America). this has to be directly related to not use Qualcomm. It sucks, but its true.
This isn't a small company we're talking about here. They need to do better. MUCH Better. Look, I've used pixels from the beginning, and will always, but they still need to do better.
Click to expand...
Click to collapse
Yeah and that's even more weird now because im using EMEA and also live in that region. Just crazy what they did there.
foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
Oh no lol. We won't have anything to play with then haha
foobar66 said:
Hmm ... then I'm thinking ... If I were Google: "Maybe we should remove the manual upgrade possibility completely" in the future ...
Click to expand...
Click to collapse
they pulled the update due to the connectivity issues. Google will never (and shouldn't ever) remove the manual upgrade process. It had nothing to do with that process anyhow. it was the build specifically that was the issue. It could have happened to any manufacturer. Google removing the ability to manually update has no bearing on this.
What would happen if users needed to roll back an update? Or they don't have internet? Or the ota update doesn't work? No way Jose
This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.
DanielF50 said:
This is an extreme move. Anyone who's flashing the December build manually should be tech savvy enough to flash the November radio if they're having network issues. Everyone should have the ability to choose what build they're running - I, for one, couldn't deal with all the November bugs again.
If they wanted to limit novice users from flashing manually, they could have removed the ability to flash Dec build from the Android Flash Tool - all that pulling the build does is leave the people already on Dec build with no backup plan in case of bootloop, etc.
I still can't wrap my head around why they haven't released a minor OTA update & carrier services fix to resolve the widespread radio issues - they could have negated all of this with a quick fix in mid December to tide everyone over until January, but instead are making people wait over a month for the next build to fix a simple problem.
Click to expand...
Click to collapse
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then
P6P said:
They just needed to replace the Dec radio.img with Nov radio.img and that's all. Like you said... That could be the mid dec build then
Click to expand...
Click to collapse
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here
Alekos said:
but pulling the build - means there's much more to this. it must. On the december build, I could force a Corrupt message simply by turning off location access to the "ImsSetting" service in the Privacy menu. November build it's fine.
I suspect there is something more going on here
Click to expand...
Click to collapse
Oh ok didn't know that. I have just heard about the data connection problems.
P6P said:
Oh ok didn't know that. I have just heard about the data connection problems.
Click to expand...
Click to collapse
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...
Alekos said:
yeah I think there's more to it. obviously I can't prove it. but October/november there weren't any "corrupt" messages appearing. December? tons on reddit and here...
Click to expand...
Click to collapse
Dunno. I had a few issues with October and November build but December is fine. No issues at all.
P6P said:
Dunno. I had a few issues with October and November build but December is fine. No issues at all.
Click to expand...
Click to collapse
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good
Alekos said:
yeah I didn't have issues either... October, November... then just flashed December's build and got the corrupt message. when I saved it, it was fine, but it was a close one. Almost couldn't get it back. nothing would work... bootloader, ota, factory reset etc etc.... finally flashing original build from October, did the trick.
but it's been great... no issues with signal, fingerprint, battery life....all good
Click to expand...
Click to collapse
Wait you mean corrupt message while updating? Never had that.
Related
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.
rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.
JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
They all say 'Android is updating' everytime you power the phone on ;-)
oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.
drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.
I heard that they are updating the baseband, not the software version...
Did anyone else get updated, my phone is not rooted or unlocked. so far update looks sleek, need to explore a lot.
enjoy all.
jhogal12 said:
Did anyone else get updated, my phone is not rooted or unlocked. so far update looks sleek, need to explore a lot.
enjoy all.
Click to expand...
Click to collapse
Mine is updating now but stated "security update will install?"
Looks like the N920AUCS4EQG1 update Nobarb found for all of us and referenced as unreleased a little bit back. (Thank you once again, Nobarb for all your hard work!!)
Probably just another security update. With the S8, S8+ and now the Note 8 forthcoming I can't imagine Samsung throwing us any more bones for our good old Note 5.
mattern1974 said:
Looks like the N920AUCS4EQG1 update Nobarb found for all of us and referenced as unreleased a little bit back. (Thank you once again, Nobarb for all your hard work!!)
Probably just another security update. With the S8, S8+ and now the Note 8 forthcoming I can't imagine Samsung throwing us any more bones for our good old Note 5.
Click to expand...
Click to collapse
well as I said I got Official Nougat, i will post some pics but security enhancements shows as April 13. Im sure ATT rolls these out in phases.
jhogal12 said:
well as I said I got Official Nougat, i will post some pics but security enhancements shows as April 13. Im sure ATT rolls these out in phases.
Click to expand...
Click to collapse
My apologies...I may have misunderstood what you were talking about. I just got an update yesterday and it was the QG1 update which brings in the July 1, 2017 update.
If you are not fully up to that build, keep trying for an update. You might try manually pushing your clock ahead a day if it is restricting you by the time limit.
I also received this new update and installed it. No difference in battery life or performance whatsoever... Just security updates.
Ever since my phone was updated to Nougat, it has been randomly rebooting (sometimes once a week and sometimes twice in 10 minutes). I can still use it fine but I'm honestly getting tired of finding it stuck at the "Enter PIN" (encrypted phone) screen after restarting. So I'm missing important calls without even realizing it when the phone is in my pocket. Anybody else seeing this? Suggestions welcome.
I did a cache wipe at least 10 times now and that didn't help. Don't wish to do a factory reset... It's a pain to setup android the way I like.
Thanks for any help guys.
someone can give me firmware N920AUCS4EQG1, im out side US,pls!
Figured I'd post this since it seems to have changed a few things.
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not. Still 8.0.0 oreo, but there are a few new things I noticed.
Calling Plus is no more. Appears to be replaced with VoLTE capabilities. Phone tried registering on the network, but I got an error. Regular calling seems to be fine.
Always on Display is different now. Similar functionality, but fewer options.
pjsnyc said:
Today I got an update notification and the size seemed a bit large (~900 MB). I kinda was hoping it would be a surprise Pie update, but alas it is not.
Click to expand...
Click to collapse
I know you're probably joking, but PIE is not going to show up as some random update. It's going to Korea carrier variants first. Maybe Q1 2019. Then everyone else. PROBABLY Q2 2019.
We will have plenty of notice about Pie, when it starts happening.
Sent via open market LG US998 V30/V30+
In any case, functionality has changed a bit. Just a heads up.
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Sometimes updates create issues on a phone running stable and fine with current rom and we wonder why we updated?
I bought this phone a month ago (living in India) and I find that phone is running absolutely fine, with great battery life and no issues whatsoever with August security update.
Now -- may be I will update to new update (whenever released for India phones) only after couple of weeks after going through feedback from users who updated.
I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???
Sabarixda said:
I have read that lg v30 is part of google enterprise recommended which need to be regularly updated every 90 days for atleast security patch. I am from india and i got last update at end of august but till i am posting this message i didn't got any update which shows avery pathetic promise breach. Which not good for brand like lg i didn't expect from lg???
Click to expand...
Click to collapse
Don't be concerned on not receiving update. From what I am reading on some other threads for V30+ -- believe me, you are saved from issues in new updates released in other parts of the world for our phone. Phone is running absolutely fine with last update. We should wait for an update which will not give us any performance issues.
jjairal said:
After update phone no longer has lte. Stays on 3g. Not sure why or how to fix it. Reset networks, Rebooted, updated prl and profile but nothing has fixed it so far.
Click to expand...
Click to collapse
Strange, I havent had problems with LTE after update.
Welp, it's about time they finally said it:
Pixel 6 December Update Situation Just Got Worse
Google confirms it has paused the December update for Pixel 6 lineup due to connectivity bug. When is a fix coming? Not until late January.
www.droid-life.com
And there you have what many had thought! Good old googleeeee
So for the few like myself that got it pushed to my phone on MetroPCS (TMobile), what does that mean? I haven't had any dropped calls but my speeds have been slower and battery has been worse than what I remember with November patch.
According to the post, if you aren’t experiencing issues after the update, no action is required and just rock out until the late January update. Unless you want to factory reset and revert back to the November update.
selayan said:
So for the few like myself that got it pushed to my phone on MetroPCS (TMobile), what does that mean? I haven't had any dropped calls but my speeds have been slower and battery has been worse than what I remember with November patch.
Click to expand...
Click to collapse
I doubt if it means anything. You can always flash the November image, although dirty flashing (not wiping), especially when "downgrading" can cause more issues and trouble than it's worth. Hopefully this Monday, January 3rd we'll get the regular monthly update, and if so, your current December version will be superseded anyway. Edit: I missed that the source Google article said fixes would come out in late January, so I'm now not expecting a new update until then or even the first Monday of February.
Im alright without the Dec. update, no issues with mine besides the AOD all of sudden does no respond. Found an an app that took care of that issue plus not notification indicator now
Figures, I already factory reset last week after the December update so I wouldn't want to flash a stock November image at this point. I have some other issues with the phone like the one user posted with lines across the screen on videos but have not been able to get in contact with support. Will try to after the holidays and hope they don't give me the run around.
I'd really like to know where the fault is. The modem or some other partition?
In November, I would drop calls in dead spots. In December I would just lose call audio and have to call that person back.
More fan fair:
Google paused the December Pixel 6 update, but is just admitting to it now
The Google Pixel 6 December 2021 update rolled out to a select few. Now, Google is finally admitting that update's problems.
www.androidauthority.com
Boo Google! What the heck is going on? Late January?
I guess I'll be using my 4 XL one more month then...
I guess Google now knows why Samsung doesn't use their own modems in their phones, especially in the US.
But hey.....look at all these cool animations they introduced in A12
It's a very capable modem but no other phone on the market has it. Samsung hasn't documented any differences from the international S20 or S21. Only thing it doesn't seem to support the moment is VoNR for voice over 5G.
But I've said this previously, Samsung rewrote the modem for December. The blame likely lies with them.
I have a really bad feeling about all of this.
So also on the Dec update and things seemed good until I noticed today that my Amazon apps (Music and Shopping) both appear to be crashing and complaining about either Chrome not being updated (when it IS), and/or no internet connectivity, when both 5G and/or WiFi are available and all other stuff works fine.
Not sure if this is related at all, but this only started today after I tried to install Amazon shopping, now Music and Shopping don't work right.
I had the same problem with Amazon apps. I was able to get them to work by disconnecting my VPN.
banshee28 said:
So also on the Dec update and things seemed good until I noticed today that my Amazon apps (Music and Shopping) both appear to be crashing and complaining about either Chrome not being updated (when it IS), and/or no internet connectivity, when both 5G and/or WiFi are available and all other stuff works fine.
Not sure if this is related at all, but this only started today after I tried to install Amazon shopping, now Music and Shopping don't work right.
Click to expand...
Click to collapse
Are you using ad blocking? Whitelist the following if so:
*amazon*
Click to expand...
Click to collapse
LLStarks said:
It's a very capable modem but no other phone on the market has it. Samsung hasn't documented any differences from the international S20 or S21. Only thing it doesn't seem to support the moment is VoNR for voice over 5G.
But I've said this previously, Samsung rewrote the modem for December. The blame likely lies with them.
Click to expand...
Click to collapse
Lol "capable" modem.. Ok buddy
opz187 said:
Lol "capable" modem.. Ok buddy
Click to expand...
Click to collapse
Capable as in it can combine 5G signals when most other phones can't or don't have it enabled.
I was worried earlier this year that it couldn't. I should've worried more about all these goodies and even basic call functionality being untested.
roirraW edor ehT said:
Are you using ad blocking? Whitelist the following if so:
Click to expand...
Click to collapse
Nice, thanks man! Worked perfectly.
Now I did temp disable AdAway earlier and that did not seem to fix it, maybe I did not fully restart the app then, but now its good.
Now on my previous LG V60 I used AdGuard for years and had no issues with Amazon apps, not sure why AdAway would be different?
LOL ... "If you aren’t experiencing issues after the update, no action is required and you’re apparently very fortunate." (Google: "If you are not experiencing mobile connectivity issues, no action is required.") ... not exactly a very solid (software) engineering analysis ...
Apparently I'm one of those "very fortunate" people ... upgraded manually and I have not had any issues at all since the upgrade (4G network in Belgium). On the contrary, since upgraded, phone has been working flawlessly for me.
Hopefully we'll get a bit better explanation than just "we found and fixed the problem".
Happy end of year festivities for all of you ... stay healthy and safe !
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
UPDATE:
I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Was it à regular updates from Honor ?
TotallydubbedHD said:
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
Click to expand...
Click to collapse
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
marcox92 said:
Was it à regular updates from Honor ?
Click to expand...
Click to collapse
Yes it's a regular and official update.
Curious, didn't receive the update
nico97470 said:
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
Click to expand...
Click to collapse
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
marcox92 said:
Curious, didn't receive the update
Click to expand...
Click to collapse
You should tape in the three points upper in right in the app Honor Club( system update). Trying versions.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
nico97470 said:
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
Click to expand...
Click to collapse
Agreed.
Doing a reset will solve it, I have not done it and it works fine, I have been lucky.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
wolfaas12345 said:
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
Click to expand...
Click to collapse
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Ja5ka said:
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Click to expand...
Click to collapse
Sorry to hear that but glad I could help!
TotallydubbedHD said:
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Click to expand...
Click to collapse
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
wolfaas12345 said:
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
Click to expand...
Click to collapse
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
No its garbage logic in fact yes its been in dev for 13 years it has also been adding features for 13 years changin things for 13 years for same 13 years its also been supporting over 20k+ devices and working on them bugs are about normal with majority phones we dont see a lot cuz devs squash them before they push the update but variables that i mentioned prevent devs from covering all scenarios so shenanigans happen my problem was not with bug itself my problem is people like you talking crap because they refuse to wipe or expect flawless experience every time nothing is perfect especially software
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
I think you are an expert. Do you think it is possible to install Google Services Framework on Magic5pro? I have one but dunno how to do so. Thank you for your sharing.