https://developers.google.com/android/nexus/images#ryu
https://developers.google.com/android/nexus/drivers#dragon
Is the MXB48J just an older version than MXB48K? Or are they for different hardware?
i'm not sure what is happening with the images. it could be one is u.s.a. and one is international. i've read that upon first boot there is an OTA so it might be one 48j was from factory the 48k is the new update. but i do not think it would be a newer hardwre situation. the binaries are 48k though soit might be a hardware thing. perhaps keyboard related. again complete guessing on my part.
I'm on 48J after getting the 58mb OTA on first boot, got the Pixel C yesterday(I'm in the UK). No system update available to 48k as yet?
Sent from my Pixel C using XDA Premium HD app
I'm also on j, got mine today and during setup it did an ota. I'm in the us
Also now on J in the UK after a small OTA update.
Any news on kernel sources / device tree?
Who have OTA links?
New factory image has been posted for the February security update. Anybody wanna flash it and see if they've fixed the touchscreen and wifi issues?
I'll flash this later today, hopefully it is still compatible with our current boot images.
Sent from my iPhone using Tapatalk
Since Google skipped the Jan update for the Pixel I really hope this one has the fixes for touchscreen etc
Hopefully a Dev can jump in on this and find out.
CharlesW123 said:
I'm on 48J after getting the 58mb OTA on first boot, got the Pixel C yesterday(I'm in the UK). No system update available to 48k as yet?
Sent from my Pixel C using XDA Premium HD app
Click to expand...
Click to collapse
There wss no OTA to 48K it was a developer build not released to the public other than a factory image.
I just did a Clean flash of the latest factory image and at least for me my wifi is back to normal!!! More testing will be required to see if its really fixed but just ran speedtest and looks promising
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
Got a keyboard update as well, having trouble installing it though
andreoidb said:
I just did a Clean flash of the latest factory image and at least for me my wifi is back to normal!!! More testing will be required to see if its really fixed but just ran speedtest and looks promising
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
Got a keyboard update as well, having trouble installing it though
Click to expand...
Click to collapse
Can you unlock and relock the bootloader okay on the pixel c? no bootloader flags or anything?
Roxas598 said:
Can you unlock and relock the bootloader okay on the pixel c? no bootloader flags or anything?
Click to expand...
Click to collapse
Yeah it was easy. I did speak to soon. The issue is not completely fixed. Before I was getting 5 mbps down and 80 up. Now I'm getting 20 down and 80 up. Better, but not fixed. That is on 2.4ghz, 5ghz is fine.
andreoidb said:
Yeah it was easy. I did speak to soon. The issue is not completely fixed. Before I was getting 5 mbps down and 80 up. Now I'm getting 20 down and 80 up. Better, but not fixed. That is on 2.4ghz, 5ghz is fine.
Click to expand...
Click to collapse
The wifi i've never had an issue with tbh and i'm on my 2nd tab.
it was the touchscreen fixes I was looking for but as of yet I haven't heard anything. dunno if I cba unlocking the bootloader etc or waiting for someone to grab the OTA link.
since im off stock recovery i cant apply OTA's if they come out cant I?
Just tried to flash the new update (30 seconds boot delay? WTF!) and it kept failing at the bootloader stage :/
Just relocked it. Guess i'm waiting.
beardymcgee said:
since im off stock recovery i cant apply OTA's if they come out cant I?
Click to expand...
Click to collapse
That is correct. You need stock recovery (along with all the other stock partitions), or the OTA flash will fail everytime. Whenever I want to update, I just flash all the images (except Userdata) from the new factory image that Google posts. That way, I don't have to wait for the OTA.
Roxas598 said:
Just tried to flash the new update (30 seconds boot delay? WTF!) and it kept failing at the bootloader stage :/
Just relocked it. Guess i'm waiting.
Click to expand...
Click to collapse
Just flash them one by one, the flash all scripts always fail for me.
Sent from my Pixel C using Tapatalk
superchilpil said:
Just flash them one by one, the flash all scripts always fail for me.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I don't think I have ever once had that flashall script work. I don't even know why they include it.
Related
here is the link for reference: https://developers.google.com/android/images
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
http://www.androidpolice.com/2016/1...-nmf26o-rolling-today-possibly-android-7-1-1/
Eager for this update!
Are all 3 on the same version now?
ahent said:
I have a Google play Store phone, but since I have a Verizon SIM it installed the Verizon firmware and so I have to wait until they release. I had hoped this wouldn't happen with Verizon stating they would release the same time as Google, but here I am.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I am in the same boat... It should be available shortly (or so I hope). No reason to believe otherwise this soon after release. :good:
I guess it looks like O is for the V version. I wish they would just label this stuff every time.
https://developers.google.com/android/ota#marlin
OTA is up.
7.1.1
Can this OTA be flashed over NPF26J?
New features are also included
From JCASE:
dePixel8 has been patched with the 7.1.1 update. Please dont ask for further support.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Rydah805 said:
The full factory images are available so yes. Just remember to remove the -w command from the script so it won't wipe your data.
Click to expand...
Click to collapse
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
I didn't try, sorry. I'd assume it'd work but I couldn't be sure as I already flashed the full image.
JAYNO20 said:
Can this OTA be flashed over NPF26J?
Click to expand...
Click to collapse
Try it out and let us know ?
I personally do fully images. Only have like 6 apps installed lol pretty quick set up
JAYNO20 said:
So the OTA can not be flashed over it then? I am asking about specifically the OTA not the full image.
Click to expand...
Click to collapse
Yes it can. I just did it without problem.
---------- Post added at 01:33 PM ---------- Previous post was at 01:33 PM ----------
AmesCell said:
Are all 3 on the same version now?
Click to expand...
Click to collapse
There's only one version available for December.
cam30era said:
Yes it can. I just did it without problem.
Click to expand...
Click to collapse
Excellent!
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Installing now, this better fix my lack of bluetooth in the car or I'm going to be sad.
Mrbobrowitz said:
Hey all, quick question and sorry if this should be in a different section...
I have the VZW Pixel, but used beups depixel8 for bootloader unlock. I am running stock NDE63V with a T-Mobile Sim. Can I flash the factory image with leaving out the bootloader? Or can I go ahead and just flash the whole image without the -w command.
Thanks!
Click to expand...
Click to collapse
Just take out the -w. I just did and all is good. ??
Sent from my Pixel XL
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Sadly no.
Thanks I had a feeling
Have you even tried?
Scott said:
Have you even tried?
Click to expand...
Click to collapse
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
cam30era said:
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
Did this myself. Unlocked bootloader, rolled back from Q to O. Was unable to flash OTA (with locked bootloader), due to being older.
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
ahent said:
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Thanks, I hope it just pushes OTA I don't want to mess with flashing it. By the time I get around to flashing it January may be out and it will be a moot point.
Sent from my Pixel XL using Tapatalk
cam30era said:
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
cam30era said:
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Click to expand...
Click to collapse
IMHO I think the band 4 issues is pseudo.. since it does not update the radio or boot at all.. Unless its a "setting" that's changed that makes it work.
clockcycle said:
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
Unlocked bootloader definitely makes a difference, you can't flash a factory image without it.
Click to expand...
Click to collapse
mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Return the phone if you can and get another one. Odds are that the stock on the shelves hasn't been updated yet.
Sent from my Pixel XL using XDA Labs
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Also, it seems they have added an automatic video creation "Highlights" feature to the Gallery app, utilizing Quik video editor. Not sure if this was already included in previous versions.
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Gr8 and battery life?
I guess they mentioned it in updates?
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Can u share a screenshot of ur about page after the update please?
Sent from my Honor 8 using XDA Labs
ayush rao said:
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
Can u share a screenshot of ur about page after the update please?
Click to expand...
Click to collapse
Here you go.
peterchen1999 said:
Here you go.
Click to expand...
Click to collapse
Awesome. I can't wait for the update to reach my device!!!!
Sent from my Honor 8 using XDA Labs
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
cant wait!!!
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
You need to be on stock and unrooted for the official update process to work.
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
unroot then do update
PS: My L04 still not get this update
blackbuffalo said:
unroot then do update
PS: My L04 still not get this update
Click to expand...
Click to collapse
Mine too. Might take another 1-2 weeks probably for every device to receive the OTA.
Sent from my Honor 8 using XDA Labs
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Even me, an FRD-L04 user, didn't receive it. Once we receive the update u can expect it on ur phone within a week or two. That's what happened in the case of the B385 update.
Sent from my Honor 8 using XDA Labs
Got it last night. Currently using phone on first day of the update.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Got it last night on my L14.
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Thanks! Hopefully I get it soon. Any major changes? Heard there were some apps that were added.
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
nestojean said:
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
Click to expand...
Click to collapse
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Sent from my Honor 8 using XDA Labs
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Well I got the phone about a week ago and just activated my new tmo sim card last night to get cell service on it so I'm probably not the best judge of whether any performance changes occurred. Based on the change log I wasn't expecting much though.
FYI I'm still completely stock, locked bootloader for now if that made any difference in the delivery of the update.
ayush rao said:
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Click to expand...
Click to collapse
Thanks for the explanation. This is the route I had to take. I have FRD-L04. I was on B385 with TWRP and Magisk 14.0. Unrooting and flashing boot.img and recovery.img from 385 did not help to install the new update. I keep getting the same error of Package failed. No matter what I seemed to try nothing worked.
So, this sucks, but, I factory reset. Then RE-locked bootloader. Then, I had to download *latest full package* otherwise I still received same error. But, now I am on B388 and i'm going to try flashing TWRP and installing Magisk now.
Live photos seems interesting. Pretty excited about that.
Question to anyone who got the update, any changes in battery life?
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
skaforey said:
https://developer.android.com/preview/download.html
You'll need an unlocked bootloader to flash the images.
You can also sign up for the ota program without an unlocked bootloader being required:
https://g.co/androidbeta
Click to expand...
Click to collapse
Thanks!
My phone is not here yet, should arrive today, so I'm going to hold off until I decide that I'm keeping it.
I will enroll my OG Pixel though!
Deleted
Salval said:
That isn't for our devices.
Click to expand...
Click to collapse
They just haven't updated that yet. The system images are available for the 2 and 2 XL so it certainly is for our devices.
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
clnzx2 said:
I have flashed 8.1 on my XL but it seems to just sit at the Google logo. Verified the checksum so I know the download is fine. Any ideas?
Click to expand...
Click to collapse
How long you been waiting at the google logo? May take awhile for it to load up
20 minutes+
It doesn't show my new Pixel XL 2 in the ota beta list, just my old Pixel XL.
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
---------- Post added at 12:35 PM ---------- Previous post was at 12:35 PM ----------
OTA's are not ready yet for the 2 line - they require manual flash.
But, for what it's worth, I (re)enrolled my OG Pixel and the OTA has not dropped yet.
clnzx2 said:
20 minutes+
Click to expand...
Click to collapse
That's kinda long
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
beerbaronstatic said:
Images seem bad, flashed successfully and get a device corrupt error. Flash back to 8.0 and things work just fine again. No luck flashing the OTA as well from 8.0 (OPD1.170816.010)
Click to expand...
Click to collapse
Same here
clnzx2 said:
Same here
Click to expand...
Click to collapse
Color me three!
Whew...thought I had a bunk device.
Welp.
Is it stable? Anything annoying?
Is HDR processing faster as they say it should be?
To those asking "is it stable" or "what's changed" - I don't believe anybody has successfully gotten 8.1 on their Pixel 2 XL yet. I'm with those above who get the red "corrupt" screen and then essentially hangs on a google logo. I went back to the bootloader to reinstall 8.0.
Has anyone tried sideloading the ota file?
https://developer.android.com/preview/download-ota.html
Pixel 2 XL is in the beta list now for the enrollment. I haven't received the update yet though
It boots
Sent from my Pixel 2 XL using Tapatalk
danon.brown said:
It boots
Click to expand...
Click to collapse
OTA or factory image?
Enjoy!
Currently two builds: QP1A.190711.019 and QP1A.190711.020
Factory Image: https://developers.google.com/android/images#sargo
OTA Image: https://developers.google.com/android/ota#sargo
No OTA here in Germany so far
Anyone know the difference between the two builds?
Sent from my Pixel 3a using Tapatalk
Neither in France
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
They have diferent checksums
jerethi said:
Anyone know the difference between the two builds?
Click to expand...
Click to collapse
"Within the .19 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565300664 which equates to 08/08/2019 @ 9:44pm (UTC).
Within the .20 image META-INF\com\android\metadata, the post-timestamp UNIX value is 1565743352 which equates to 08/14/2019 @ 12:42am (UTC).
Based on one of Google's release tool's code, this value seems to be utilized to determine whether it should perform an incremental or full OTA.
If I'm understanding their upgrade process correctly, the .19 image does not contain the September security patch. The .20 appears to be the full stable release with the September security patch.
It would appear .19 should support an incremental upgrade from the latest Android Pie (9) version, PQ3B.190801.002 but not bring you to the latest September security patch.
This leads me to believe that the .20 image is suitable for almost all OTAs. There may be carrier specific cases that one or the other should be utilized but nothing stands out too clearly within any of the immediately available metadata files."
- https://www.reddit.com/r/Android/comments/cz7lb1/android_10_images_are_live/eywlgww/
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Sent from my Pixel 3a using Tapatalk
Atiqx said:
Do I have to do a factory reset , if I'm rooted on Android 9 to archive android 10 without any problems ?
Click to expand...
Click to collapse
No, just uninstall magisk or flash stock boot.img. once that is done, you should OTA just fine.
upinsmoke7610 said:
I have just got the ota update, I'm updating from beta 6 and it's saying the update size is 41mb, is this correct?
Click to expand...
Click to collapse
On reddit they say that coming from beta the update file is only this small.
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
Well I knew banking apps would not work on the beta but now I'm on the stable release and my banking app still will not even open, but of a nightmare really as I rely on it.
Sent from my Pixel 3a using Tapatalk
Got the OTA from pie right now 1188.8mb
I've just received the OTA notification here in Spain
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
anyone knows if is there any difference, or added feature compared to the last beta version?
yabadabadooo said:
They have diferent checksums
Click to expand...
Click to collapse
A factory image is a full replacement - and is meant to replace everything (you'll lose all your data and else that isn't backed up). An OTA is an update - you lose nothing. If you're coming from a STOCK factory image (either a beta of 10 OR 9) and your phone is fine, you want the OTA; otherwise (including AOSP), you want the full factory image.
germany here, installing the update now, takes quite some time for being only 41mb, hope it works
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Got it 30 mins ago from stock rom over ota (1.1GB) in France.
Install was smooth and fast.
So far so good!
Enjoying the dark mode
#Edit: weather widget shows temperature in °F instead of °C while everything is setup right. Strange ^^
sic0048 said:
I didn't want to wait for the OTA to be pushed to my phone, so I sideloaded it and the rooted it again with Magisk. My directions are accurate if anyone else wants to sideload the OTA. To be honest, the whole process is faster when you sideload anyway. So it is really a better solution than waiting for the OTA.
The initial boot took about 5 minutes. Don't get impatient and try to mess with the phone. Just let it do it's thing.
Click to expand...
Click to collapse
Thank you sic0048! I followed your guide when my Pixel 3a was on 9 and it was smooth. The best instructions I have found and even bookmarked it.
I do have one quick question. I followed your instructions about updating the phone and keeping root, but I lost root after reboot. I probably did something wrong. :silly:
In your instructions under the "Custom Recovery Installation method" you state that TWRP doesn't support Android 10. So how do I root my phone again? Is it safe to use this method or should I use another one of your methods in this tutorial?
After update to 10, I was able to see "Enable DDS" toggle in phone information shortcut.
Now the toggle is gone.
Anyone else has this issue?
yabadabadooo said:
On reddit they say that coming from beta the update file is only this small.
Click to expand...
Click to collapse
I came from RC2 - the update is indeed that little.
However, you will have to wait for a 10-ready build of TWRP; the current TWRP is not ready (of course).