A second February update just posted, SQ1D.220205.004. It showed up OTA on my phone at 10.24 MB. No idea what it contains.
poit said:
A second February update just posted, SQ1D.220205.004. It showed up OTA on my phone at 10.24 MB. No idea what it contains.
Click to expand...
Click to collapse
https://twitter.com/i/web/status/1494419768186748933
I also got the update and so far i don't see any changes. Looks like urgent bugfix and security fix update.
No problems with root on the 004!
sakerhetz said:
No problems with root on the 004!
Click to expand...
Click to collapse
Here's where you post root issues.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
...
I just installed the new Update. In setting tick check for update to get it.
I've tested Wi-Fi as best I can and seems to be normal now.
Power Off, On Charger, Reboot, Wi-Fi On. Connects OK
Turned Wi-Fi Off/On several times. Connected OK. Forgot Wi-Fi. Re-entered w/password. Connected OK
Rebooted and phone and it was connected to Wi-Fi as normal.
I notice nor Bluetooth issues.
I haven't had WiFi turn off randomly, but it's only been a couple hours.
Edit:
Still haven't suffered WiFi randomly turning off. May be purely coincidental though.
I spoke too soon.
Took a 50 mi drive.
WiFi and Bluetooth issue is back
Weird, but I started to hear my OIS rattling after this update
mosio said:
Weird, but I started to hear my OIS rattling after this update
Click to expand...
Click to collapse
Yeeeeah, software isn't going to change your hardware.
Related
For those of us who hate the over saturated color of the Nexus 6P, and got the sRGB mode turned on, I have bad news. I'm testing the latest Nougat, and I found that the setting resets with every reboot. Only a mild inconvenience, but I wish there was a way of making it permanent. Are you guys experiencing the same?
FreemanAMG said:
For those of us who hate the over saturated color of the Nexus 6P, and got the sRGB mode turned on, I have bad news. I'm testing the latest Nougat, and I found that the setting resets with every reboot. Only a mild inconvenience, but I wish there was a way of making it permanent. Are you guys experiencing the same?
Click to expand...
Click to collapse
I've been experiencing this issue on Marshmallow too. I just got used to turning it on after a reboot. Then again, I rarely reboot these days. AFAIK, there's no solution.
Sent from my Nexus 6P using Tapatalk
Yes I'm experiencing the same thing but it's not a new "bug" for me. Ever since I got the phone on Marshmallow it's been doing this.
Been happening ever since I got the phone on release, nothing new. Was happening during N beta as well, have reported it several times in both M and N but they don't seem to care.
Can it be set to auto start with tasker?
Sent from my Nexus 6P using Tapatalk
With Android 6 I didn't have the same problem, after updating to 7.0 yesterday night yes...I can confirm it resets after the reboot hope someone can find a solution...
Knight77 said:
With Android 6 I didn't have the same problem, after updating to 7.0 yesterday night yes...I can confirm it resets after the reboot hope someone can find a solution...
Click to expand...
Click to collapse
Strange. It sRGB resets for me even in M. I thought this was a default behaviour. It's never stuck for me since I purchased the phone since last nov
Echoing all previous statements. It's the same issue with Marshmallow for me.
kyzn said:
Echoing all previous statements. It's the same issue with Marshmallow for me.
Click to expand...
Click to collapse
I didn't have the problem with Marshmallow but anyway there was a method to avoid it (not using secure boot), this method here with 7.0 doesn't work - I tried that too.
It was like this before, it's not a bug actually, just standard behaviour.
coolkingler1 said:
It was like this before, it's not a bug actually, just standard behaviour.
Click to expand...
Click to collapse
Not it wasn't for me and many others. I didn't have the same problem before.
I read somewhere that was related to the fact that the phone is encrypted. If you don't use secure boot then that sticks. That was the same in Marshmallow.
Even unencrypted it has never stuck for me.
It sticks, just don't open the developer options everytime you reboot otherwise it will be reset.
adhya said:
It sticks, just don't open the developer options everytime you reboot otherwise it will be reset.
Click to expand...
Click to collapse
When I reboot I can clearly see the colors are not in sRGB mode...
Knight77 said:
When I reboot I can clearly see the colors are not in sRGB mode...
Click to expand...
Click to collapse
Strange, maybe that's because I'm rooted and decrypted.
adhya said:
It sticks, just don't open the developer options everytime you reboot otherwise it will be reset.
Click to expand...
Click to collapse
This worked for me on Marshmallow, but not now on Nougat.
I don't know if I did anything to fix this in marshmallow. But I had no problem with sRGB on M. Ever since I got Nougat, it's back to Developers Options after every dang boot. It's getting old. I just installed the September update and it's not been fixed.
os2baba said:
I don't know if I did anything to fix this in marshmallow. But I had no problem with sRGB on M. Ever since I got Nougat, it's back to Developers Options after every dang boot. It's getting old. I just installed the September update and it's not been fixed.
Click to expand...
Click to collapse
I've had to do this since I got the phone when it was released so I'm used to it. I didn't even realize that some people were actually getting the setting to stick after reboots on Marshmallow.
Why is it so hard for Google to just release screen profiles ? :/ Let us have the option tucked under display options !
Gesendet von meinem Nexus 6P mit Tapatalk
This seems way passed overdue. I've tried manually updating with no luck. Has anyone else been experiencing the same issue?
Same here, smartswitch and ota see nothing. Gonna probably need to use odin to get it done.
Do you guys check on setting , system UPDATE (manual mod )
Gabe2014 said:
Do you guys check on setting , system UPDATE (manual mod )
Click to expand...
Click to collapse
Yeah I've tried manually updating. This seems ridiculous that I still haven't received the update; and I'd prefer not to root the phone...
Yes. No update for me either. I heard it's possible the date your imei was activated could impact your update. I activated mine on Feb 14th.
Same. No update. I usually do all updates for apps and system manually. Still nothing...
jaketc said:
Yes. No update for me either. I heard it's possible the date your imei was activated could impact your update. I activated mine on Feb 14th.
Click to expand...
Click to collapse
Do you have a T-Mobile firmware right? Because I remember one time went I flashed unlock version Thant I back to to mobile for some reason my csc changed and my UPDATE center stoped work but this happen to me one time , I don't know if this is your case ...
motojdm said:
This seems way passed overdue. I've tried manually updating with no luck. Has anyone else been experiencing the same issue?
Click to expand...
Click to collapse
https://support.t-mobile.com/docs/DOC-36189
Temporarly on Hold.
T-Mobile stopped the OTA Oreo update right now for Note 8. This is due to problems with this update. Samsung and Google are working on a fix. Once they fixed the problems then they will resume OTA Oreo update for the Note 8.
I posted this in another thread days ago. If you have questions or you feel there is no problem, since you didn't have any problems this far, then read my post on the other thread.
https://forum.xda-developers.com/tm...lunge-via-odin-quick-qs-t3775980/post76298713
My wife and I both received the update before the hold. Did they say why they stopped the update?
ptfdmedic said:
My wife and I both received the update before the hold. Did they say why they stopped the update?
Click to expand...
Click to collapse
Yeah, me to... and my phone has worked beautifully ever since Oreo installed. I STILL can't figure out what the issue is.
ElaineD said:
Yeah, me to... and my phone has worked beautifully ever since Oreo installed. I STILL can't figure out what the issue is.
Click to expand...
Click to collapse
Mines starting to heat up more during a charge...and using android auto. Before, the phone used to be nearly cold to the touch. Now it's very warm.
SiNJiN76 said:
Mines starting to heat up more during a charge...and using android auto. Before, the phone used to be nearly cold to the touch. Now it's very warm.
Click to expand...
Click to collapse
I charge my phone using the 2.0 amp wireless charger (I have a few scattered around) and I haven't noticed ANY heat change. In fact, I'd say the phone is cooler if anything. When I tried to update to Oreo by connecting to the computer (Smartswitch), I got Error 807******(don't remember) repeatedly, so I gave up and updated OTA.
I got tired of waiting and updated to Oreo via Odin. Haven't noticed any major issues.
I think T-Mobile stopped the OTA update because of battery life. I received the update on April 2nd and battery life is pretty bad for me. I only get 3Hrs 45min screen on time. Deleted a lot of apps that I don't use but didn't help much only get 4hrs screen on time. I also had to turn off Always on Display which I hate to do because I was use to looking at the screen without unlocking the phone.
RaymondPJR said:
I got tired of waiting and updated to Oreo via Odin. Haven't noticed any major issues.
Click to expand...
Click to collapse
where you got the Oreo update willing to share it on Google Drive or something that doesnt make you wait 20+ hours?
Hello all. My wife and I have note 8 and I received the update and she did not. My phone is working better than before. Her phone is acting up, random question been out of the scene for quite some time. If I flash via Odin will that trip knox?
bluediablito said:
Hello all. My wife and I have note 8 and I received the update and she did not. My phone is working better than before. Her phone is acting up, random question been out of the scene for quite some time. If I flash via Odin will that trip knox?
Click to expand...
Click to collapse
No. Flashed mine via odin a few weeks ago and didn't trip the Knox counter.
Sent from my [device_name] using XDA-Developers Legacy app
just got mine update yesterday.
Just got mine, the new build number is CRD7, not really sure what's new compared to the last oreo update, but that 1.3 GB update installed surprisingly fast.
Hi guys,
I'm still on Nougat 7.1.2 with my Swift 2+. I'm waiting for the OTA, don't want to side load if I can help it.
I'm trying to get an idea of the proportion of people that are still waiting for their OTA and those that have already received it.
EDIT: nobody received Oreo via the OTA? oh boy...
I just got the OTA, posting this from Oreo
I manually updated (to check for OTA), and am downloading it now
Updated to 8.1 using the official download and now stuck in boot loop. Fortunately remembered to back up my data first.
Update - factory reset got me going again. The next day the battery crashed to 0% charge in no time at all.
All OK now... fingers crossed.
wish I had not chaged to Ori,,
Hi
Have two swift 2x phones in family
my one received the OTA wedensday,
performed the change,
now have no on line data, only over wifi,
Some paramiter like ATP that needs changing but Virgin does not knwo how to
Other phone received invitation to change to 8.1,
weve declined for now thank you....
Mine works fairly well, except for a camera issue (and less than stellar battery life).
wish I had not chaged to Ori,,
AN update on this
It seems to be a Virgin "feature"
Managed t get the phone to have mobile data now,
virgin did some tweaking,
so updated the other wiley fox phone,
thats on Id, and upgraded perfectly
andrewmm said:
AN update on this
It seems to be a Virgin "feature"
Managed t get the phone to have mobile data now,
virgin did some tweaking,
so updated the other wiley fox phone,
thats on Id, and upgraded perfectly
Click to expand...
Click to collapse
No issues with the camera? I can't make any pictures or movie clips.
dryhte said:
No issues with the camera? I can't make any pictures or movie clips.
Click to expand...
Click to collapse
Did initially have camera problem,
but after power of and reset,
all good,
after received the phone did 3 OTA upgrades in a row, 2 nougat then oreo. After oreo you have to restart the phone to make camera work again. Still I wish there was LOS or RR or AEX roms on 8.1
Turns out it was an issue with my SD card (128GB, which is not officially supported). With 32GB it works fine. Still disappointing (because it worked before the update)
Got it last night.
Phone been utterly terrible since.
Just done a factory reset hoping it would fix it.
It's taking time to re-setup because of constant repeating steps..
This update has made my phone so much poorer.
I thought it might be the SD card so I went from 64gb down to 32gb.
I even made the SD portable instead.
Done 3 factory resets...
It's randomly (but often!) unresponsive
I have two T-Mobile's OnePlus N200 5G
One of them got Android 12 about 6 weeks ago.
Second one (received from T-Mobile few days ago under Trade In offer) is still on Android 11 and does not get any update (April 1 security patch of Android 11 is the last). Manual check does not get updates too.
How can I install Android 12 on this device?
it depends on what you want out of the phone.
T-Mobile pulled the Android 12 update back into development:
OnePlus 10 Pro 5G: Update to Android 13
Find out about the Android update on the OnePlus 10 Pro 5G.
www.t-mobile.com
I've not read anywhere as to the reason why they pulled it back, but clearly it must have been something significant enough that they suspended the rollout, rather than just fixing it with the next update.
My family also has two N200s, and one of them did the upgrade to 12. My son's is on 12 and has had few issues with his, and nothing significant to my knowledge. i kept delaying the update on mine until finally the update message went away when they pulled the update back, so i'm still on 11 and working just fine.
You could wait until T-Mobile addresses whatever they wanted to fix, and they push the update back out again via OTA (this is the solution i'm going to go with)
Not sure if the OOS12 image for the T-Mobile variant has been available on XDA, but you could check other threads here to see if anyone has it to download and install. you'd need to check whatever instructions are available on whatever thread you find it in to do that.
but, if you are wanting to go through the work of doing an OS install outside of the normal OTA, you may want to just check about the new official LineageOS being available for the N200. (if you want to try LineageOS, you would need to be on 11 to begin with anyway, which is conveniently where you are currently at)
HeadMajor said:
it depends on what you want out of the phone.
T-Mobile pulled the Android 12 update back into development:
OnePlus 10 Pro 5G: Update to Android 13
Find out about the Android update on the OnePlus 10 Pro 5G.
www.t-mobile.com
I've not read anywhere as to the reason why they pulled it back, but clearly it must have been something significant enough that they suspended the rollout, rather than just fixing it with the next update.
My family also has two N200s, and one of them did the upgrade to 12. My son's is on 12 and has had few issues with his, and nothing significant to my knowledge. i kept delaying the update on mine until finally the update message went away when they pulled the update back, so i'm still on 11 and working just fine.
You could wait until T-Mobile addresses whatever they wanted to fix, and they push the update back out again via OTA (this is the solution i'm going to go with)
Not sure if the OOS12 image for the T-Mobile variant has been available on XDA, but you could check other threads here to see if anyone has it to download and install. you'd need to check whatever instructions are available on whatever thread you find it in to do that.
but, if you are wanting to go through the work of doing an OS install outside of the normal OTA, you may want to just check about the new official LineageOS being available for the N200. (if you want to try LineageOS, you would need to be on 11 to begin with anyway, which is conveniently where you are currently at)
Click to expand...
Click to collapse
I updated to 12 on my phone and had some issues so I msm'd back to 11 a week or so ago and just this morning got the notification for 12 again but with security updates for july. Perhaps they fixed some things up. Now that I know I can fall back to 11 no problem I will try out 12 again eventually.
I updated to 12 a couple weeks ago, I straight away noticed a problem receiving text msgs. I'd get the notification but when I went into messaging the text were gone. I was thinking about getting the phone replaced but thought to check for an update and Boom, there was an update saying RCS publish fix. I'm hoping I will no longer have the text disappearing. So far it looks fixed. I hope this helps
strange. Tmobile must be in some wonky dual development path hell.
I never completed the update to 12 when it was temporarily giving the messages to update, and it currently is still not giving me any messages about update, and Tmobile website says 12 is still in development. So they must still be working to put out a full 12 package for people to update from 11 to 12 who have never done so.
but if you've already updated to 12, then like duhhhm8, Tmobile is pushing an incremental update?
then there is Deejayadhd, who did update, then downgrated, and is getting the incremental message too? perhaps your device is tagged as having already updated to 12 so it's sending the incremental to you. it will be interesting how that will work. will the system figure out that it needs to send the full package again, or will it try to send the incremental 12 update to install into the current 11 system.
well, wtf.
my phone is just sitting there charging.
i go and doubletap the screen to wake it up, because i hear that i received a notification.
for a fraction of a second it shows the tmobile logo, and goes black/off.
turn it back on, and 12 gets installed and i'm looking at the app optimization %
no prompt to choose whether i wanted to or not, nothing.
just shut itself off and upgraded itself
whelp. bugs or no bugs, i guess i'm getting to see how 12 works out
HeadMajor said:
well, wtf.
my phone is just sitting there charging.
i go and doubletap the screen to wake it up, because i hear that i received a notification.
for a fraction of a second it shows the tmobile logo, and goes black/off.
turn it back on, and 12 gets installed and i'm looking at the app optimization %
no prompt to choose whether i wanted to or not, nothing.
just shut itself off and upgraded itself
whelp. bugs or no bugs, i guess i'm getting to see how 12 works out
Click to expand...
Click to collapse
if you hated 12 (I won't blame you), MSM back to 11 and go in developer options and disable automatic system updates and you should be able to install the april patch. after that, it shouldn't automatically reboot.
justauserthatusesaphone said:
if you hated 12 (I won't blame you), MSM back to 11 and go in developer options and disable automatic system updates and you should be able to install the april patch. after that, it shouldn't automatically reboot.
Click to expand...
Click to collapse
well, so far i think i've been ok. no major issues on 12 for me.
i think the one most irritating is the poor gmail/google notifications.
but my previous phone had the problem of the background updater kept getting killed so i would frequently go into accounts and uncheck gmail sync and recheck gmail sync to restart the background process and get my notifications working again.
so i'm already in the habit of regularly checking if gmail sync/notifications are working anyway. just a bummer that it was ok on 11, and now it's borked on 12 and i'm now back to old habits to address
I had absolutely nothing but problems with 12.. I had the original update.. Msm's to 11... Got the new android 12 update... Fixed a lot... But honestly... Didn't work great. I eventually called oneplus' support line to fix the bug about having a snapdragon 855... They said they were putting it on there to do list. So.. Cool. But then... Lineage OS was released for it.. And I was like: by Oxygen OS (Color OS brother/sister at this point). I had one issue with Lineage, but I think it might be device-specific (meaning my individual device). The Lineage OS update is phenomenal! It makes Color OS... I mean Oxygen OS 12, seem slow. Very slow.
symnok said:
I have two T-Mobile's OnePlus N200 5G
One of them got Android 12 about 6 weeks ago.
Second one (received from T-Mobile few days ago under Trade In offer) is still on Android 11 and does not get any update (April 1 security patch of Android 11 is the last). Manual check does not get updates too.
How can I install Android 12 on this device?
Click to expand...
Click to collapse
in an update it does get android 12. Mine is one android 12 now after an update 2 weeks ago
I ended up downloading the update before it was pulled and have so many regrets. The most crippling issue is a seemingly unfixable bug that causes both wifi and cell signal to cut out at random, which is effecting both me and my other family members with the same phone. I also just generally hate the weird psudeo-ColorOS that i've been using. Sadly an authenticator app I need to use for work would make wiping the thing in the name of the OS downgrade too much of a pain, so I've just decided to order a different phone at this point.
As I'm rooted, I have to manually check for updates via xperifirm. There was an upsated released: version 64.1.A.0.913.
Anybody updated and tested? Apparently camera apps have been updated! Any new features?
I wont get time to update yet, just thought I'd ask.
Thanks
Unless I'm mistaken, this update allows you to switch from android 12 to android 13
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
viper. said:
Huh we have android 13 for months now ...so i would say no .
Its for sure a security patch.
Chinese 72 got it 2 weeks ago , european 54 got it a week ago and US has to wait for another two weeks , i wish it would be all at the same time .
Click to expand...
Click to collapse
Yeah, you're right about security patch. Thought perhaps something has trickled down from the new phone releases, like improved camera apps as they have changed their version numbers. Thanks
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
Ouch, sorry to hear that. I will update in a few days and see if I have the same issue. Though tbh, I havent had as many issues as some have, perhaps because of root and cleaning up some bloat and adding in adblockers etc.
You should do a full all apps cache wipe and see if that helps.
arthurham said:
Hello,
The only feature I expericence since the upgraded is the "phone too hot warning" issue. I use the phone since late november without any trouble.
For the latest week, the phone displayed the orange warning sign and closed the camera app maybe 10 times. It couldn't even go through a 10 minutes google meet call...
It may not be related to the latest release, and I may be the only one having this issue...
Click to expand...
Click to collapse
I had overheating problems with meet and 5g i was outside but on older different firmware.
You also have to understand now its summer time (probably in your country too) so you cant really compare november temperatures with current ones unless you did that in room with AC on.
I'm on the latest US version so still waiting for our update for this cycle. But since my last update, the phone has been very warm to the touch during normal use and I've seen the heat warning many times while using camera. I have never seen it before. Battery life is crap now too and used to be fantastic. Maybe you guys lucked out last month and the US version got whatever it was to cause the heating issues first? My last update was around 300mb so it was bigger that usual I think.
.913 QR reader from statusbar dont work. only black screen.
hasztagL said:
.913 QR reader from statusbar dont work. only black screen.
Click to expand...
Click to collapse
I had that sometimes on .891 ,couldnt get it to work no matter what but it goes away eventually with restarts .
Edit: i just got the .913 and qr reader works fine. Been using my phone before that for 2 hrs and no overheating ,after installing 913 and checking camera apps for 1 minute my top part of the screen got extremly hot but didnt show any overheating warnings.nothing changed so far in camera related apps (no portrait mode)