I just take a look and it appears that B11 is up to download from http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6 but i've yet to get an OTA from my device is self.... ZTE really need to step up their software strategy and dev and it going to hit them hard if they continue to deliver crappy OS to users.
Same hardware and they are putting different kind of software variant and this is really stupid....
ramnkc said:
I just take a look and it appears that B11 is up to download from http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6 but i've yet to get an OTA from my device is self.... ZTE really need to step up their software strategy and dev and it going to hit them hard if they continue to deliver crappy OS to users.
Same hardware and they are putting different kind of software variant and this is really stupid....
Click to expand...
Click to collapse
Have you tried forcing the German firmware update? The updates seem pretty universal for G models.
I'll admit, the current approach ZTE adopted for firmware updates for G models is poorly thought out, but at least the German dev team has been as active as the US one, so we still can receive updates/fixes pretty frequently.
Hamburgle4 said:
Have you tried forcing the German firmware update? The updates seem pretty universal for G models.
I'll admit, the current approach ZTE adopted for firmware updates for G models is poorly thought out, but at least the German dev team has been as active as the US one, so we still can receive updates/fixes pretty frequently.
Click to expand...
Click to collapse
Haven't did that yet as i'm busy with my stuffs... but will find some time to do it over the weekend.
I just need to put 7.0 nougat downloaded from http://www.ztemobile.de/support/downloads/?product_id=2100, rename it to update.zip then move it to my root folder. Update via the updater software, after successfully updated i need to wait for the OTA to 7.1.1 again right? Is there anyway to 7.1.1 B02? I'm currently still on MM B10
ramnkc said:
Haven't did that yet as i'm busy with my stuffs... but will find some time to do it over the weekend.
I just need to put 7.0 nougat downloaded from http://www.ztemobile.de/support/downloads/?product_id=2100, rename it to update.zip then move it to my root folder. Update via the updater software, after successfully updated i need to wait for the OTA to 7.1.1 again right? Is there anyway to 7.1.1 B02? I'm currently still on MM B10
Click to expand...
Click to collapse
I think you need to put it onto an SD card. After updating to 7.0, if you aren't prompted for an update to 7.1.1 (I dunno if this has changed since), you want to manually update again, this time to B01 using any of the links floating around the forums.
Once you are on 7.1.1 B01, it should this time prompt you with the B02 update.
ramnkc said:
I just take a look and it appears that B11 is up to download from http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6 but i've yet to get an OTA from my device is self.... ZTE really need to step up their software strategy and dev and it going to hit them hard if they continue to deliver crappy OS to users.
Same hardware and they are putting different kind of software variant and this is really stupid....
Click to expand...
Click to collapse
So is this the official upgrade from B02 (7.1.1)?
Apparently no just ZTE remove the B10 rom file and placed B11.
What's the point of doing that with so many months delay.
ZTE should had upload the latest B02(7.1.1) and not old B11(6.0.1) to everyone want manually upgrade to latest version since many users don't get OTA anytime.
Sent from my iPad using Tapatalk
paatha13 said:
So is this the official upgrade from B02 (7.1.1)?
Apparently no just ZTE remove the B10 rom file and placed B11.
What's the point of doing that with so many months delay.
ZTE should had upload the latest B02(7.1.1) and not old B11(6.0.1) to everyone want manually upgrade to latest version since many users don't get OTA anytime.
Click to expand...
Click to collapse
Whether that B01 is a final release or a leaked version, you will get an official B02 update prompt.
Regarding the update strategy, It's a poorly thought out process by ZTE. Clearly the German devs are the only ones actively working to keep our devices (G variant) up to date. ZTE should've made this clear to users in other markets once the nougat updates started rolling imo.
It definitely isn't perfect, but it's at least reassuring knowing that we can at least receive updates for our model.
Finally upgraded to nougat 7.1.1 B02 (normal way isn't working now... i had to use this - https:// in front :
dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/HK/ZTE/ZTE A2017G/401523/B01%20to%20B02.zip
And issues at MM still exists in Nougat... SO SO SO disappointed.
1. Whatapps voice playback issues still exists
2. Still no prevent pocket dial features
ramnkc said:
Finally upgraded to nougat 7.1.1 B02 (normal way isn't working now... i had to use this - https:// in front :
dl1.ztems.com/zxmdmp/download.do?doWhat=getUp&filename=firmwarepackages/HK/ZTE/ZTE A2017G/401523/B01%20to%20B02.zip
And issues at MM still exists in Nougat... SO SO SO disappointed.
1. Whatapps voice playback issues still exists
2. Still no prevent pocket dial features
Click to expand...
Click to collapse
Might be an isolated problem. I'm not having any WhatsApp playback issues. And no problems with pocket dialing, even with double tap to wake on and thin pockets. Have you considering doing a factory reset?
I'm also using a HK purchased A7.
Hamburgle4 said:
Might be an isolated problem. I'm not having any WhatsApp playback issues. And no problems with pocket dialing, even with double tap to wake on and thin pockets. Have you considering doing a factory reset?
I'm also using a HK purchased A7.
Click to expand...
Click to collapse
Big issues on voice playback, when u playing a voice message try cover the proximity sensor the voice message play out loud via laud speaker. It supposed to play with interspeaker instead. I am hitting hard when I tried to listen to my private voice message by putting near my ear and u know what happened next... It boom at close encounter... Wth.
As the prevent pocket dial feature is never there... It prevent phone accidentally unlock and press while in my pocket. Not dialling in my pocket.
ramnkc said:
Big issues on voice playback, when u playing a voice message try cover the proximity sensor the voice message play out loud via laud speaker. It supposed to play with interspeaker instead. I am hitting hard when I tried to listen to my private voice message by putting near my ear and u know what happened next... It boom at close encounter... Wth.
As the prevent pocket dial feature is never there... It prevent phone accidentally unlock and press while in my pocket. Not dialling in my pocket.
Click to expand...
Click to collapse
Not entirely sure what you mean by the first part. I tried playing back messages (sound from both speakers) then moving the phone to my ear/covering proximity sensor to listen and it seemed to work as intended (sound only from the top speaker). It also adjusted automatically from full blast, to a lower/safer volume level. Sounds like the opposite of what you're experiencing.
I'm curious how your phone is unlocking by itself. I'm on fingerprint/pin setup which seems improbable that it could unlock itself. If you're using smart unlock... I guess the only work around for now is to not use it. Or is it dialing with the emergency dialer? That would be a problem...
Hamburgle4 said:
Not entirely sure what you mean by the first part. I tried playing back messages (sound from both speakers) then moving the phone to my ear/covering proximity sensor to listen and it seemed to work as intended (sound only from the top speaker). It also adjusted automatically from full blast, to a lower/safer volume level. Sounds like the opposite of what you're experiencing.
I'm curious how your phone is unlocking by itself. I'm on fingerprint/pin setup which seems improbable that it could unlock itself. If you're using smart unlock... I guess the only work around for now is to not use it. Or is it dialing with the emergency dialer? That would be a problem...
Click to expand...
Click to collapse
That's strange, it play from the top speaker but it's at full blast.
Manage to update to B04 manually and seems smoother data speed is faster... but my battery drain more faster compare to MM.
ramnkc said:
Manage to update to B04 manually and seems smoother data speed is faster... but my battery drain more faster compare to MM.
Click to expand...
Click to collapse
That's my feeling too but compared to B02.
Faster battery drain while on standby and using it.
Let's see next couple of days for more safe conclusion.
Sent from my iPad using Tapatalk
Related
Nokia is pushing the newest update out to Lumia's now, available through Zune update. Firmware version: 1600.2483.8106.11500
This is meant to be the battery fix. Read more here.
Happy updating
tjramage said:
Nokia is pushing the newest update out to Lumia's now, available through Zune update. Firmware version: 1600.2483.8106.11500
This is meant to be the battery fix. Read more here.
Happy updating
Click to expand...
Click to collapse
I got an update from Zune, but it was OS update only. There was no firmware. Should I restore and try it again?
It'll come later, some have got the firmware and not the OS.
Thanks for letting me know.
I just got a similar reply on Nokia Support. They're being pushed seperately. The user I replied to had received the firmware, but not the OS update yet.
I'll try to be more patient.
I just did the disconnect trick, and it's downloading 8107, will report what firmware I have when it's done
---------- Post added at 09:42 PM ---------- Previous post was at 09:18 PM ----------
Got 8107 + new firmware in one go
Tried the disconnect trick when the last update was being rolled out but wasn't working. :S I thought they fixed it?
Clearly not
Also, MVNO's are better supported now, my phone shows Giffgaff instead of O2-UK, not seen that in a while!
I'll give it a go.. Hopefully it works this time around.. Any tips?
Took me about 5 goes to time it right. Best tip is preserver I guess. I also turned flight mode on as I read that helps.
Rusty! said:
Took me about 5 goes to time it right. Best tip is preserver I guess. I also turned flight mode on as I read that helps.
Click to expand...
Click to collapse
+1 to this. took a few attempts, worked in the end
Just managed to get it updating. It's getting new Windows verison, not sure about FW tho, will have to wait for it to finish and check.
Any noticable improvements yet? I know it's too early though
Mine only said Windows version, but firmware was included too. Auto-brightness seems better, diagnostic app contains more stuff. Charging now to see new capacity.
I just flashed back to 11451 via NCS, then forced the update through Zune.
I got both the OS update and firmware (8106.11500). I'm hoping this firmware is the answer to all our battery problems. Full charge capacity is sitting at 1483mAh. Will post back if it starts to drop (like on all the other firmwares)...
T-Mobile USA Zune Force Update Worked..
Flashed and have joy now..
Like others mentioned above, battery capacity reads 1481 rather than 1517; so was this the correction I wonder?
Will have to see how it performs over the coming days.
Autobrightness seems to work MUCH better; that alone will conserve some power.
Going to close down my system and go home now; I am curious if Bluetooth will be any better. I have a Nokia J - works better than non-Nokia, but have had to re-pair it a few times due to repeated connection dropoffs. Want to see if A2DP will work now. And of course, will try the camera to see if there is anything else good there (in spite of prior reports..)
Cheers
[1st Edit]
Ok, so far BT is holding together but we'll see.. I'll have to see if the belt holster throws it off. Still no A2DP though.. Podcasts, music, and Nokia Drive voices still play through speaker and won't route through headset.
[Edit 2]
Camera.. Nuts.. Spoke too soon. At work under fluorescents.. No pink spot. Came home .. Under halogen, spot is still there unless I use flash. So looks like nothing changed after all except the focus default setting (whoop dee dee... )
[Edit 3] Bluetooth seems very stable.. Going to try now with a non-Nokia earpiece..
apollo15rover said:
Flashed and have joy now..
Like others mentioned above, battery capacity reads 1481 rather than 1517; so was this the correction I wonder?
Will have to see how it performs over the coming days.
Autobrightness seems to work MUCH better; that alone will conserve some power.
Going to close down my system and go home now; I am curious if Bluetooth will be any bettery. I have a Nokia J - works better than non-Nokia, but have had to re-pair it a few times due to repeated connection dropoffs. Want to see if A2DP will work now. And of course, will try the camera to see if there is anything else good there (in spite of prior reports..)
Cheers
[1st Edit]
Ok, so far BT is holding together but we'll see.. I'll have to see if the belt holster throws it off. Still no A2DP though.. Podcasts, music, and Nokia Drive voices still play through speaker and won't route through headset.
Camera.. Hey whaddaya know? The horrid pink spot on non-flash indoors is GONE!!! Hoorah
Now I gotta see if the camera still paints outdoor night shots in the ghastly green as before..
Click to expand...
Click to collapse
Wait... did you flash or update via Zune?
anseio said:
Wait... did you flash or update via Zune?
Click to expand...
Click to collapse
Zune. Didn't appear at first so did a force update..same as how I got Mango before..
apollo15rover said:
Zune. Didn't appear at first so did a force update..same as how I got Mango before..
Click to expand...
Click to collapse
And you got the firmware update, as well as the OS update? No fair! I only get the OS update. I hate being patient.
anseio said:
And you got the firmware update, as well as the OS update? No fair! I only get the OS update. I hate being patient.
Click to expand...
Click to collapse
Nah. Just the f/w.. Got the OS via cab sender 2-3 wks ago. Took the risk because the disappearing keyboard was driving me crazy.
apollo15rover said:
Nah. Just the f/w.. Got the OS via cab sender 2-3 wks ago. Took the risk because the disappearing keyboard was driving me crazy.
Click to expand...
Click to collapse
I'll keep trying. It'll come up one of these days.
I didn't notice the keyboard issue until it was pointed out.
Not getting any updates at all?
Im using the mac os x windows phone connector not sure if thats the problem...
Regions are UK
Following my recent technical issues that were caused after updating my ZF3U to Android 7.0, I contacted ASUS and was told that "we have checked this for you and sent this info through for analysis. The Android N update has been stopped for OTA updates. So we would advise to downgrade the unit back to Android M for now. And do a factory reset for the unit".
This advice did not work and eventually my problems got worse (see other threads I posted about my problems). Few days a go my ZF3U completely died on me. Prior to this fingerprint recognition did not work, serial number was misreported in settings, no sound in calls was present even after downgrade to Android M. ASUS should not have released the Android 7.0 firmware in the first place pending proper testing on the ZF3U.
Eventually, I sent the phone to repair (through my insurance as ASUS insisted I had to send the device to Taiwan as it originated from there for the Asia market -POOR Service for an international company) and was advised that my ZF3U was beyond economical repair so a replacement was needed. I have now ordered another one as this phone is the only phone available that caters for my needs. I am really annoyed with ASUS, their service and the really poor software update they first rolled via OTA and then through their servers and then withdrew without any advice to those of us who have already installed it on our precious devices. They should never have released an incomplete, faulty firmware update. I hope those of you who have either downloaded the OTA or used the manual file do not experience the issues I had but if you do then good luck to you unless you have insurance.
Lets hope they learn to fix their phones properly with good after-sales support and I am still waiting for compensation from them following my recent complaint.
What's up with this update anyway ? I received it and my phone functions perfectly...
Why did Asus pull the update ? What's the official reason ? Is it a widespread problem ? Or just corner cases ?
Thanks.
Latoc said:
What's up with this update anyway ? I received it and my phone functions perfectly...
Why did Asus pull the update ? What's the official reason ? Is it a widespread problem ? Or just corner cases ?
Thanks.
Click to expand...
Click to collapse
Not sure why it was pulled. I got the manual update second hand from a user on this site as it was already pulled from ASUS before I could get it. I knew the risk and updated anyways. No issues at all. Phone works perfectly, maybe even better. My bootloader was unlocked and rooted just like AWFRONT was. Not sure why I didn't get the same issues they did, but I am 100% issue free on the 7.0 update.
doctahjeph said:
Not sure why it was pulled. I got the manual update second hand from a user on this site as it was already pulled from ASUS before I could get it. I knew the risk and updated anyways. No issues at all. Phone works perfectly, maybe even better. My bootloader was unlocked and rooted just like AWFRONT was. Not sure why I didn't get the same issues they did, but I am 100% issue free on the 7.0 update.
Click to expand...
Click to collapse
do you mind sharing the manual nougat firmware image and instructions to manually update?
nerdyone255 said:
do you mind sharing the manual nougat firmware image and instructions to manually update?
Click to expand...
Click to collapse
https://forum.xda-developers.com/zenfone-3-ultra/help/stock-recovery-t3585965/page2
doctahjeph said:
Not sure why it was pulled. I got the manual update second hand from a user on this site as it was already pulled from ASUS before I could get it. I knew the risk and updated anyways. No issues at all. Phone works perfectly, maybe even better. My bootloader was unlocked and rooted just like AWFRONT was. Not sure why I didn't get the same issues they did, but I am 100% issue free on the 7.0 update.
Click to expand...
Click to collapse
this explains why my ultra didn't get the update yet.. probably it was rolled out to some devices, and encountered intermittent issue like above and rolled back..
What is the latest update you got ? Because i do not get OTA updates i dont know why , i have to keep flashing kdz files everytime there's uodate available
I show Software version VS98811A
Akhayev said:
What is the latest update you got ? Because i do not get OTA updates i dont know why , i have to keep flashing kdz files everytime there's uodate available
Click to expand...
Click to collapse
There's only been one update since the phone came out, and that was in April.
Went out to get the mail, came back and I noticed a download icon on my phone, turns out its in the middle of an update. File size is 477.3mb. I already have the update from April, so Im not sure what this'll be. Guess I'll know within the hour, as its downloading quite slowly.
strodda said:
Went out to get the mail, came back and I noticed a download icon on my phone, turns out its in the middle of an update. File size is 477.3mb. I already have the update from April, so Im not sure what this'll be. Guess I'll know within the hour, as its downloading quite slowly.
Click to expand...
Click to collapse
I just finished downloading it myself. It's at updating now... (1/2) stage right now. I hope they fix all the issues and complains people had, or at least most of them.
It went from 11a to 12b. I do not notice any differences yet, but I didnt experience issues prior to the update either.
Hopefully this fixed my Bluetooth issues. I installed it and will try it when I leave work to see if my streaming issue goes away (static/crackle).
Sent from my VS988 using Tapatalk
I just saw the update coming down, it's downloading atm.
Unfortunately it looks like it was just security updates. My Bluetooth issue is still present.
Sent from my VS988 using Tapatalk
I hope it fixes the only issue I have. Intermittent battery drain when idle.
just lou said:
I hope it fixes the only issue I have. Intermittent battery drain when idle.
Click to expand...
Click to collapse
And....It doesn't.
The latest update bricked my phone this morning. It got stuck on the LG screen, then occasionally flashing the "Your device is corrupt. It can't be trusted and my not work properly." I couldn't even factory reset it. Took it to a Verizon store and they couldn't do anything either. At least they will FedEx me another phone overnight.
just lou said:
And....It doesn't.
Click to expand...
Click to collapse
I'm not seeing any heavy-duty battery drain. Possible you have a rouge app?
rfarrah said:
I'm not seeing any heavy-duty battery drain. Possible you have a rouge app?
Click to expand...
Click to collapse
I doubt it. The only thing showing serious battery drain is "Phone Idle", and I have the same exact apps on 2 other devices without a problem.
I just got 12b update today.
xceebeex said:
Hopefully this fixed my Bluetooth issues. I installed it and will try it when I leave work to see if my streaming issue goes away (static/crackle).
Sent from my VS988 using Tapatalk
Click to expand...
Click to collapse
For me, this update broke the BLuetooth transmission of audio track data to my car stereo head unit. I post in the general G6 forum earlier:
'I have a new G6 and a new problem with Play Music. When connected via Bluetooth to my 2016 Subaru Outback head unit, Play Music track info does not appear on the head unit display. My previous LG G5 had no problem doing this consistently. Other apps like Pocket Casts displays track info, no problem. I reviewed the G6 supported Bluetooth profiles and they are compatible with the Subie head unit.
This is maddening! Has anyone else experienced this and then found a solution?
cheers,
mordango
UPDATE: I had this phone replaced with fresh G6. It was still on the 11a Verizon software version. Connected it to the car head unit via Bluetooth, played Google Play Music, got all the info on the head unit as it was supposed to do. Updated to 12b software version, no more music information displayed on the head unit. So, the 12b update breaks this for Play Music. Some other audio apps still display info but Play Music and Soundcloud are broken."
Hi, has anyone had any popping, crackling, or skipping when listening to music? I get it about twice to 3 times per hour when listening to spotify or local music. There was one time in particular where i was listening to music, when opening the recents menu and opening a recent app caused a serious crackling distortion.
Should I return my phone?
Side note: have tried safe mode. Crackling still occurs. Have tried repeating the same file. Crackilng does not occur at the same time.
Second side note: on version 119. Phillipines has no updates beyond that.
Mine does it too. This phone has more bugs than a bush tucker trial!
Haha. Yeah, it does. I've also have had apps randomly open sometimes and another music player play for a few seconds when I press play on Spotify, then return to spotify. I'm planing to try and have my handset exchanged tomorrow at the store. Hopefully they will.
I do believe this phone has really great potential, if only it wasn't so buggy.
Had too sometimes.
However, I think problem is Oreo, not the phone!
I want to believe it's oreo, since everything else on my phone works great (minus the hiccups mentioned above). No wifi or reception issues. Not even sure I want to get a replacement and do a lottery again.
so glad to see its not just me. phone is terribly buggy. settings turning on and off. sometimes after being on the phone for like 5 mins, the phone locks itself. sometimes without me even touching the phone eg when im watching youtube with it propped up on my desk. has anyone who exchanged their phone actually received one that doesnt have these issues though?
whats up with the blue light remaining on in settings when you turn a setting off? UI nightmare
Hmm. This makes me think we should run a poll so we can identify the common issues everyone is having to rule out hardware issues.
sonydesouza said:
Had too sometimes.
However, I think problem is Oreo, not the phone!
Click to expand...
Click to collapse
A lot has to be with Oreo as these issues don't exist in other Huawei phones. Also i wonder if some of these unreleased roms that folks are using have bugs in it compared to the official roms received via OTA.
warea said:
A lot has to be with Oreo as these issues don't exist in other Huawei phones. Also i wonder if some of these unreleased roms that folks are using have bugs in it compared to the official roms received via OTA.
Click to expand...
Click to collapse
Yeah me too...
I'm waiting an update !
I have some bugs with contacts sync, gmail and music popping.
Except that, everything is fine !
Ah well, i guess I'll just lean on the huawei warranty instead.
SabreFury said:
Ah well, i guess I'll just lean on the huawei warranty instead.
Click to expand...
Click to collapse
As you want but really think huawei is not the problem...
I'm currently holding the A526U1 bought unlocked and on Metro as a carrier - my CSC appears to be TMK. (Unrooted, though I probably don't need to specify that with that U1) As of right now I still haven't gotten the Android 12 update, though a friend with the A52 5G on T-Mobile has, and that was about a week ago. I sort of expected to get mine pretty soon afterwards, with Metro being owned by T-Mobile and all, but nope, not the case. Was wondering where everyone else in the US is on the update, both on the large carriers and the smaller ones. I'm curious as to whether we're "mostly there" or still just getting started on the rollout.
Actually, it says on the T-Mobile website that their latest update is 12. https://www.t-mobile.com/support/de...a52-5g/software-updates-samsung-galaxy-a52-5g - I haven't asked him what model number he has, but he otherwise has the A52 5G and lives in the northeastern US just like I do. So it's definitely here, but not on my model/CSC.
Ah, yeah! I provided the info about my particular model but really was curious about the full, wider net in the US; my bad not clarifying further on that part!
I'm non T-Mobile and have had mine for the last week... I live here in Texas
doubledragon5 said:
I'm non T-Mobile and have had mine for the last week... I live here in Texas
Click to expand...
Click to collapse
Interesting - any idea what your model is?
Kissies4Pigeons said:
Interesting - any idea what your model is?
Click to expand...
Click to collapse
Model Galaxy A52 5G
Model number SM-A526U
Kissies4Pigeons said:
Interesting - any idea what your model is?
Click to expand...
Click to collapse
In my first post it should have read "Im on T-mobile
Ooh haha gotcha, okay that lines up with the other T-Mobile release - I guess they probably put that out nationwide. The U1 still doesn't have the update as of today, which I find curious. I wonder if the other US models not attached to T-Mobile have theirs yet or if it's just the U on T-Mobile. Anyway thanks!
Kissies4Pigeons said:
Ooh haha gotcha, okay that lines up with the other T-Mobile release - I guess they probably put that out nationwide. The U1 still doesn't have the update as of today, which I find curious. I wonder if the other US models not attached to T-Mobile have theirs yet or if it's just the U on T-Mobile. Anyway thanks!
Click to expand...
Click to collapse
I also got the latest security patch just a few days ago.. I will say, there seems to be some glitches in this latest Android. For instance when typing sometimes the keyboard just disappears.. Plus the soft keys disappear and I can not exit back to the home screen.. This is mostly after watching videos online.. And a few times when I had the phone app open, I could not view recent calls or access my contacts, except opening up the contact app.
[Erased and pasted into next message because I can't figure out how to delete it lol]
doubledragon5 said:
I also got the latest security patch just a few days ago.. I will say, there seems to be some glitches in this latest Android. For instance when typing sometimes the keyboard just disappears.. Plus the soft keys disappear and I can not exit back to the home screen.. This is mostly after watching videos online.. And a few times when I had the phone app open, I could not view recent calls or access my contacts, except opening up the contact app.
Click to expand...
Click to collapse
My friend on T-Mobile says he's gotten at least two follow-up patches after the main patch and was actually complaining about having to update so often, to which I said "dude you WANT those patches after a big OS update, they're cleaning up stuff that you're otherwise going to run into" - and I'd guess this is a good example of some of that stuff they haven't gotten to yet. I still have not received the new update, interestingly - I'm not sure whether Metro is being careful not to release a update that isn't quite finished baking or if my exact model isn't prioritized, but it would be nice to think that the version I end up with is a little more polished than the one you're having to deal with (boy figuring out quotes took me a hot second)
This is what I was talking about. The missing soft keys. They came back after swiping to take a screen shot
doubledragon5 said:
This is what I was talking about. The missing soft keys. They came back after swiping to take a screen shot
Click to expand...
Click to collapse
That's very weird. Okay Metro if you want to take your time making sure I don't gotta deal with that I'm cool honestly. Tho tbh this patch from Android 11 I'm on I have weird activity happen with Gboard - Gboard will try to activate but end up flashing open and then shut again, sometimes with what may be a real flash of noise on the screen that is hard for my eyes to actually detect. It's hard to predict when it will happen but it happens often enough! On the videos, not even scrolling back upwards makes the soft keys come back? (I ask because scrolling down in the gallery makes them disappear for me until I go up again)
Nope not even scrolling. I have let the screen time out then open again. Then the keys reappear.
doubledragon5 said:
Nope not even scrolling. I have let the screen time out then open again. Then the keys reappear.
Click to expand...
Click to collapse
That's bananas. Hope that gets fixed soon for you, that sounds like a hassle and a half. Have you looked to see if the gesture navigation bar does the same thing? Probably not that easy, but whack either way
Kissies4Pigeons said:
I'm currently holding the A526U1 bought unlocked and on Metro as a carrier - my CSC appears to be TMK. (Unrooted, though I probably don't need to specify that with that U1) As of right now I still haven't gotten the Android 12 update, though a friend with the A52 5G on T-Mobile has, and that was about a week ago. I sort of expected to get mine pretty soon afterwards, with Metro being owned by T-Mobile and all, but nope, not the case. Was wondering where everyone else in the US is on the update, both on the large carriers and the smaller ones. I'm curious as to whether we're "mostly there" or still just getting started on the rollout.
Click to expand...
Click to collapse
I have the same exact model as you: A526U1, but I'm unlocked on AT&T. I too still do not have the Android 12/One UI 4 update. So it's definitely not a Metro thing that's holding up your update. I think they haven't updated it because not every carrier has finished testing it? Really not sure, but I'm super frustrated that other A52 5Gs got it here in the US but not the U1.
I do (and I assume you also do) have the January security patch.
broder107 said:
I have the same exact model as you: A526U1, but I'm unlocked on AT&T. I too still do not have the Android 12/One UI 4 update. So it's definitely not a Metro thing that's holding up your update. I think they haven't updated it because not every carrier has finished testing it? Really not sure, but I'm super frustrated that other A52 5Gs got it here in the US but not the U1.
I do (and I assume you also do) have the January security patch.
Click to expand...
Click to collapse
I recently found that information that said that unlocked phones need to be tested on every carrier before being updated, and truthfully at this point seeing the bugs that they're still working through, I feel like that might come out as an advantage for us unlocked users? I'm not sure if it works the way I think it works but it's almost like everybody who isn't unlocked ends up beta testing for the unlocked users?
I do have the January security patch like you, but yeah, no big update yet. But I've contented myself with that on the logic above.
For anyone curious, I received the update last night for my unlocked A52 5G on Metro - so far I haven't noticed any bugs - in fact I think some minor issues I had seen with my display are gone? But there's still time lol. Hex theming is running successfully on it, as a sidenote
I actually got my update for Android 12 and One UI 4.0 a couple weeks ago and another security patch about a week later. From what I have read it has only been released for the A52 5G phones that are not carrier locked. Mine is the SM-A526U and I use with MetroPCS. So far I haven't had any issues with my updates and everything is working good. I did flash a custom GCAM 8.3 port from the new Google Pixel before the 12 update but both camera apps work pretty well with GCAM only having slightly better features. It does take some tinkering with as the ported app at first would take between 1-2 seconds to actually take the picture
Arobase40 said:
Actually there is no Android 12 atm.
Click to expand...
Click to collapse
My A526U (MetroPCS, unlocked) is now on Android 12.