There are no Pixel security patches in the April 2019 Pixel Update Bulletin.
There are no Pixel 2/ Pixel 2 XL related patches.
Pixel 3, Pixel 3 XL
1. A-119823747 A - 120135659 - Assistant
Improves Voice-Unlocking performance for Google Assistant
2. A-122883482 - Setup
Adjust Wi-Fi connectivity during eSIM activation on certain carriers
3. A-119327025 - Display
Removes screen flash when ambient display wakes for some
Pixel, Pixel XL
1. A-119109648 - Bluetooth
Improves Bluetooth connectivity on Pixel devices
Source: https://source.android.com/security/bulletin/pixel/2019-04-01.html
What that's disappointing????? Damn are we the forgotten one?
That's not true. right now i've got an ota update on my pixel 2 xl april security patch. they just didn't add any improvements maybe that's why pixel 2 was not mentions there.
astaineakash said:
That's not true. right now i've got an ota update on my pixel 2 xl april security patch. they just didn't add any improvements maybe that's why pixel 2 was not mentions there.
Click to expand...
Click to collapse
Yes. Pixel 2 will get all the security updates every month and OS versions until October 2020. This patch contains all the security patches from the AOSP line.
Source: https://source.android.com/security/bulletin/2019-04-01
So we got many security updates but no Pixel specific.
Our device now working perfectly. According to Google.
Some has managed to root again with Magisk after april manual update?
failax said:
Some has managed to root again with Magisk after april manual update?
Click to expand...
Click to collapse
No problem at all with magisk 19.0 beta :good:
Badger50 said:
No problem at all with magisk 19.0 beta :good:
Click to expand...
Click to collapse
I'm on Pie, i downloaded the ota zip and flashed on device, all ok, but i lost root, so i tried to patch img.boot again and pull to the device.Result is Android remains stuck at middle.I pulled the boot.img again and the os starts, but with no root.
failax said:
I'm on Pie, i downloaded the ota zip and flashed on device, all ok, but i lost root, so i tried to patch img.boot again and pull to the device.Result is Android remains stuck at middle.I pulled the boot.img again and the os starts, but with no root.
Click to expand...
Click to collapse
Then just fastboot into twrp and flash the magisk zip from there. It's what I do every month after fastbooting the factory image :good:
Badger50 said:
Then just fastboot into twrp and flash the magisk zip from there. It's what I do every month after fastbooting the factory image :good:
Click to expand...
Click to collapse
I've not installed TWRP, it is necessary?
failax said:
I've not installed TWRP, it is necessary?
Click to expand...
Click to collapse
Not necessary, but makes things a lot easier if you ask me. Hasn't caused me any grief since the August 2018 release :good::good:
failax said:
I've not installed TWRP, it is necessary?
Click to expand...
Click to collapse
No need to install TWRP, just plug in the USB cord, and boot the twrp.img, it is temporary, and goes away when you boot the system.
I'm seeing an increase in battery life after this update. Also i did few settings correct which was eating my battery i suppose.
What about you guys?
100rabh7791 said:
I'm seeing an increase in battery life after this update. Also i did few settings correct which was eating my battery i suppose.
What about you guys?
Click to expand...
Click to collapse
No complaints from me
Droid_Nut said:
No need to install TWRP, just plug in the USB cord, and boot the twrp.img, it is temporary, and goes away when you boot the system.
Click to expand...
Click to collapse
Thanks, it worked
Badger50 said:
No complaints from me
Click to expand...
Click to collapse
9h of SOT at 33%?????
Le_Combattant said:
9h of SOT at 33%?????
Click to expand...
Click to collapse
Yeah, that's pretty normal for my usage patterns
Badger50 said:
Yeah, that's pretty normal for my usage patterns
Click to expand...
Click to collapse
What type of usage do you have? Can you share us your battery stats (trough android parameter)
Le_Combattant said:
What type of usage do you have? Can you share us your battery stats (trough android parameter)
Click to expand...
Click to collapse
I will if you want after my next cycle. Typically it's mostly participating on xda, 1-2 hours of phone calls, some texting, NO social media, some browsing on the web. I also turn off things like, find my device, I freeze my google app, have little to no hapetic feedback, on wifi 80% of the time, I run stock Ex kernel, and since I'm retired, the phone gets to sit and sleep regularly, and my device is 18 months old. SOT is really to subjective to try and duplicate, so I wouldn't put to much stock in it
Is it possible to install the April update WITHOUT the new Magisk version? I have Magisk 18.1. Can that version STILL be used with the April Update?
I would rather not install Magisk 19 - as it seems to be having issues with Google Play. Thanks.
Badger50 said:
I will if you want after my next cycle. Typically it's mostly participating on xda, 1-2 hours of phone calls, some texting, NO social media, some browsing on the web. I also turn off things like, find my device, I freeze my google app, have little to no hapetic feedback, on wifi 80% of the time, I run stock Ex kernel, and since I'm retired, the phone gets to sit and sleep regularly, and my device is 18 months old. SOT is really to subjective to try and duplicate, so I wouldn't put to much stock in it
Click to expand...
Click to collapse
It's very impressive
I have Facebook/Messenger and Snapchat it's why I never overtake 8h of SOT.
What is the app on your previous post showing your SOT?
Related
Google Pixel 2 XL October Factory and OTA Images are available to download with 4 functional updates and no security fixes.
OTA: https://dl.google.com/dl/android/aosp/taimen-ota-ppr2.181005.003-b1969df7.zip
Factory: https://dl.google.com/dl/android/aosp/taimen-ppr2.181005.003-factory-f0a1d2c1.zip
Boot image on my Google Drive: https://drive.google.com/file/d/1MtCsZjPw0bu2Q9BXbrHhlPe6fcbRV6y4/view?usp=drivesdk
Changes:
Code:
- Improved performance for certain protected media formats (Pixel 2, Pixel 2 XL)
- Improved stability when using Android Auto (Pixel 2, Pixel 2 XL)
- Improved fast-charging behavior for Pixel devices (Pixel, Pixel XL)
- Modified Call Screening behavior when using Maps Navigation (All Pixels)
October security bulletin: https://source.android.com/security/bulletin/pixel/2018-10-01
Nice to see! And fast Oct availability!
Try it yet?
https://forum.xda-developers.com/pixel-2-xl/how-to/try-october-update-t3849237
Pretty sure I'm skipping this one. Nothing I really care about. And definitely not enough to warrant having to go through the re-root process. I'll wait for November.
oreo or pie ?
ranasrule said:
oreo or pie ?
Click to expand...
Click to collapse
Maybe KitKat...
gettinwicked said:
Pretty sure I'm skipping this one. Nothing I really care about. And definitely not enough to warrant having to go through the re-root process. I'll wait for November.
Click to expand...
Click to collapse
Just flash the ota through twrp, it's easy & quick
gettinwicked said:
Pretty sure I'm skipping this one. Nothing I really care about. And definitely not enough to warrant having to go through the re-root process. I'll wait for November.
Click to expand...
Click to collapse
mickyw1980 said:
Just flash the ota through twrp, it's easy & quick
Click to expand...
Click to collapse
Yep, it's super easy. Boot to TWRP, flash the OTA zip file, reboot to OS, reboot back to TWRP, flash Kernel (optional) then Magisk and you're good to go! Super simple.
I just noticed December's images are up for og pixel xl and pixel
Zehlek said:
I just noticed December's images are up for og pixel xl and pixel
Click to expand...
Click to collapse
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
jaytv said:
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
Click to expand...
Click to collapse
I heard for other devices (Pixel 2) the UI (At least on the home screen) has been much more fluid with the updated Pixel launcher. I would agree with this on the Pixel XL too now...I have far less stutters using navigation gestures and swiping right to go to the Discover feed. Good update!
This is really random, but after updating anyone else having an issue with the screen turning off when a right to far left of the screen is performed? Noticed it when I was swiping a word from far right of the screen to far left, and it turns the screen off. Does the same thing outside of the app. Checked the Gestures settings and couldn't find anything relevant. (Wiped data on upgrade) Any suggestions are appreciated!
chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
I'm not 100% sure I would ask @razorloves he is the expert on this one
chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
razorloves said:
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
Click to expand...
Click to collapse
Yeah figured that out. Initially I just flashed the two and it boot looped. Had to do the lot and reroot. :/
Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Before the update, I had to manually enter my apn, but After December update, all my apn automatically work. I noticed better signal reception too. I don't know if it's the update related.
I liked it,
Rebooted after initial setup and fastbooted into twrp...
Installed king kernel 3.16
Installed magisk.
Perfection, battery lasts forever now. 5.5h sot is an daily thing, 3.5-4h if streaming pandora
A-124279741 - Pixel 2
Bootloader |-> Fixes an issue causing some devices to freeze during boot
A-111660442 - Pixel 3, Pixel 3 XL
Camera |-> Fixes an issue causing the camera to crash during video recording
A-122466831 - Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Media |-> Fixes a bug that causes the Netflix app to hang
A-129149296 - Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Hotword |-> Updates to improves accuracy on "Ok Google"
There are no Pixel security patches in the June 2019 Pixel Update Bulletin.
Size: 52.3MB
I actually find it reassuring that they are not needing to do much on the updates. Maybe naive but heh...
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
I actually find it reassuring that they are not needing to do much on the updates. Maybe naive but heh...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Now the Pixel and Android line have more focus on Android Q. All the improvements, bug fixes new features are in the Q. There is no need to add features or fix minor bugs in P unless it is cause real problems like NetFlix is broken or the recording stops during a very important event...
I belive Android Q Beta4 with the final APIs will give us more features and Bugs
Any idea when beta 4 for Q will drop?
tylermrsh said:
Any idea when beta 4 for Q will drop?
Click to expand...
Click to collapse
Should release in a day or two. I hope it's good
100rabh7791 said:
Should release in a day or two. I hope it's good
Click to expand...
Click to collapse
Hopefully Ive had an issue with my signal cutting in and out constantly apps not disappearing from recents after I've cleared them etc hopefully all those get fixed
tylermrsh said:
Hopefully Ive had an issue with my signal cutting in and out constantly apps not disappearing from recents after I've cleared them etc hopefully all those get fixed
Click to expand...
Click to collapse
Oh i don't have any of the mentioned issues but yes hopefully it will make things better for all of us
Has anyone successfully updated and applied magisk?
Thanks
docluv01 said:
Has anyone successfully updated and applied magisk?
Thanks
Click to expand...
Click to collapse
Yes. I used the factory image with "-w" removed, then fastboot TWRP 3.2.3-1 and flashed magisk 19.2. Everything works fine.
Yes, Magisk 19.2 works for me. Although twrp decryption is now broken for me regardless if it is 3.2.3-1 or 3.3.0-0. I have to remove my PIN code before I boot into twrp temporarily to flash stuff.
bb709394 said:
Yes, Magisk 19.2 works for me. Although twrp decryption is now broken for me regardless if it is 3.2.3-1 or 3.3.0-0. I have to remove my PIN code before I boot into twrp temporarily to flash stuff.
Click to expand...
Click to collapse
Same here magisk 19.2 working, have to remove pin also.
Sent from my Pixel 2 XL using Tapatalk
And one more for the books...June update with -w removed, twrp 3.2.3-1 and magisk 18.1 are all that works for me, however, decryption works fine with fingerprint + pin. Gotta love the consistent quirkiness of the P2XL!! :silly::laugh:
Booted twrp 3.2.3.1 and flashed the June OTA followed by Magisk 19.2, everything seems to be working so far. Twrp was also able to decrypt my device and I didn't remove my pin prior.
Twrp 3.3.0 and Magisk 19.2 worked fine for me with pin and fingerprint.
How are you guys liking the update? Generally I do a clean wipe and flash every two months, doesn't seem like it was much worth upgrading to this month, might just Wait for July
I did a clean install of June stock with 3.2.3.1 and 10.2 and my decryption using pattern works fine.
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss
SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now
What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)
anyone know how to root on beta5??
jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below
Where is everyone getting beta 5? I only have beta 4 available.
stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here
Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.
stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:
Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?
xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.
jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.
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).