yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a Questions & Answers] EngineerMind:
I think I know what happened...

If I dial a "contact", then the dialpad does not automatically pop-up.

But if the dialpad is showing, and I tap and hold on the "1" key to call my voice mail, the dialpad will disappear, then the options buttons appear (including the speakerphone button), but as soon as my phone connects to voicemail, it pops-up the dial pad and covers up the speakerphone button.

I can sort of understand why it might be doing this (because you'll probably need the dialpad to interact with voicemail), but often I like to listen to my voicemail on speakerphone, and just a 1-2 second window to tap the speakerphone button before the dial-pad appears is not enough time.
[OnePlus 7 Pro Questions & Answers] Locoman_:
Hi. Yes, I have looked but would like reassurance if possible. Does removing your lock screen disable your phones encryption? Thanks!
[Galaxy Note 3 General] tclark1:
I have a few unlocked / rooted devices around the house, I've flashed ROMs, Magisk, GApps, etc, on them, but I've never actually unlocked bootloaders or messed around with Odin myself - I purchased them already unlocked.

I'm looking to purchase a few cheap wi-fi devices (no network capability needed) for my kids to use around the house and on trips, and I wanted to inquire if people here still consider the Note 3 (specifically, the N9005) an easy device for a novice like me to be able to unlock? The instructions on TWRP and Lineage's websites seem pretty straightforward, I just wanted to know if there were any known modern-day pitfalls I should be aware of before I buy a couple of these. It looks like I can get them new for around $100 apiece on Ebay.

Here are the directions I was looking at on TWRP. I found the thread on this forum for updating the bootloader and CM, but the links were both dead, so I guess I was hoping that was no longer a necessary step. Updating the bootloader and CM are not referencedon the TWRP page - if I want to install an Oreo ROM like Lineage, will I need to update the BL / CM?

https://twrp.me/samsung/samsunggalaxynote3qualcomm.html

Thanks in advance for any advice / recommendations!
[Xiaomi Mi 10 Lite  Questions & Answers] corkyboy:
Has anybody found a combo of wireless charger and adapter that works with the Xiaomo Mi 10 Lite.? Currently I can charge my Honor and Sony phones which have Nillikin adapters from an Anker charger pad but this doesn't work with the Mi10 Lite. Any info greatly appreciated.
[Xiaomi Mi 10 Lite  Questions & Answers] DVC1985:
The Mi 10 Lite doesn't support wireless charging.
[Xiaomi Mi 10 Lite  Questions & Answers] corkyboy:
It's confusing some reviews say it does, with the use of an adapter presumably.

Is there a wireless charging in the Xiaomi Mi 10 Lite 5G? - Mr. Phone (themrphone.com)
[Samsung Galaxy S21 Questions] xdafly:
Is this even possible -- can't see any block function in "Messages"

How To Block Spam Text Messages on Android From an Email Address

If you use Google’s messaging app, you have more luck than some other Android users because Google developed a spam filter that should automatically eliminate spam texts. Here’s how to enable it:

Open the Messages app

Hit the three dots in the upper right corner

Select Settings from the drop-down menu

Choose the SIM card if applicable

Select Spam protection

Tap on the slider next to Enable spam protection so it becomes blue

You can repeat the same process for another SIM card if you have two.
[Samsung Galaxy S21 Questions] xdafly:
OK. confirmed. It works just as above
[Samsung Galaxy S21 Questions] SiNJiN76:
I've had that turned on, but still got the email texts...good thing I can still report those as spam and block tho.
[Samsung Galaxy S21 Questions] johnp357:
so i don't have this option .."choose the SIM.." or anything that says "Sam protection.."

under message settings

conversation categories

notifications

block numbers and messages

more settings

emergency alert history

about messages.

tried every area, nothing gives the option for spam protection.

I'm on a stock samsung build on VZ provider.

Any ideas ...anyone??
[Touch Diamond, MDA Compact IV General] eskasi:
Anyone here using SPB's full screen keyboard? I have having trouble with it at it seems extremely slow with a delayed reaction to my keypresses. I have fiddled with the settings but still cannot get it to work like it did on my old Touch.

Can someone else please share their experiences or fixes?

Thanks
[Zenfone 5 Q&A, Help & Troubleshooting] thebigdjamelo:
Mod edit - translated by https://www.deepl.com/translator:

Hello

I bought a motherboard for my daughter's phone an Asus zenfon T00P

When I bought I didn't pay attention to the telephone and in English and there's no choice to install French

Thank you for your answers

**********************************************************

Bonjour

J’ai acheté une carte mère pour le téléphone de ma fille un Asus zenfon T00P

En achetant je n'ai pas fait attention le téléphone et en anglais et y'a aucun choix pour installer le français et ce qu'il y'a un moyen de le mettre en français

Merci pour vos réponsesView attachment 5240963
[Zenfone 5 Q&A, Help & Troubleshooting] Oswald Boelcke:
@thebigdjamelo Please use the English language! [Veuillez utiliser la langue anglaise!]

XDA Forum Rules (excerpt):

Additionally I moved your thread to the Q&A section as it didn't qualify for the development sub-forum. Please read the sticked "Device Forum Rules (Read before posting)"!
[Zenfone 5 Q&A, Help & Troubleshooting] mrsiri:
When you startup fresh install, is there no language option in setup?
[General Questions and Answers] skynet.84:
Hi Guys! Checkout my new Hisense A5 Pro CC E-INK Color Review!

XXXXX

Hope you enjoy it and don't forget to subscribe to my channel! 👍

All the aspects I covered are here:

00:00 Intro

01:35 Specifications

03:03 Android 10

03:45 4G connection

04:01 Unlocking

04:25 Color E-Ink Screen

05:18 Outdoor reading

05:51 New matte screen protector

06:39 Frontlight

08:16 Display Modes

09:06 Web browsing

10:12 Comics reading

10:32 Watching pictures

11:15 Watching videos

12:24 E-Ink settings menu

15:36 Install any app

20:05 Social media apps

20:59 Lockscreen

22:02 Launcher

23:26 Notification management

24:34 E-Ink button

25:27 Camera test

26:51 Sound & Music

27:42 Gps Navigation

28:51 Battery

30:07 Conclusions

New videos are coming soon 😊
[OnePlus 8 Questions & Answers] bibiii79:
Hello Guy's, i have the instantnoodlep rom lineage 18.1 unoficial, with lineage custom recovery.

Question:

- How to format/wipe the cache partion from fastboot? I tried the command: " fastboot format cache " but i get an error...

any ideeas?
[OnePlus 8 Questions & Answers] StampedeLoader:
Double that, I can't find any wipe section in this recovery. and I can't boot twrp, even with the SDK platform tools.
[Google Pixel 5 Guides, News, & Discussion] myhuky3:
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images")

Some users have reported that booting (instead of flashing) the patched boot image works and makes root temporarily available but i didn't have any success with that.

The phone booted up but root didn't work.

I won't explain how to unlock the bootloader or set up adb here.

!Warning! This will wipe your phone so take a backup!

Also i do not take any responsibility if you break your device.

And if anything goes wrong just factory reset your device using the Android Flash Tool or by following this tutorial.

Here's what i did to get Magisk v22.0 working on the first developer preview of Android 12:

Install A12 with disabled AVB & dm-verity:

Make sure USB-Debugging is enabled in developer-options and you have authorized the pc you're using on your phone.

Boot your phone into fastboot mode.

You can do this by turning it off and then starting it by holding Power + Volume Down

until fastboot mode appears or just adb reboot bootloader

Go here and click on the link for the Android Flash Tool.

(I didn't copy the link directly so i don't have to update it everytime google releases a new update)

It should ask you to allow the website to access ADB Keys. Click Ok.

If the website somehow doesn't work, try using Google Chrome.

Select your Pixel 5. If it's not showing up click add device.

Click on the edit symbol (pen) in the box where the selected build is shown.

Make sure Wipe Device, Disable Verity and Disable Verification are checked.

Install and boot the phone when it's finished.

Patch & flash boot.img

Download and install the Magisk Canary App from GitHub.

Download the factory image from here and extract boot.img from it.

(Inside the downloaded zip-file is another zip file containing the boot image)

Copy the extracted boot.img to your phone and open the magisk app.

Click on Install -> Select and Patch a File and let it do its magic.

Copy the magisk-patched boot image that should be found in your phones download folder back to your PC.

Reboot into fastboot mode as i explained earlier and flash the patched boot image.

(fastboot flash boot magisk_patched.img)

Then reboot the device.

Now root should be working. If it bootloops and says your phone has to be factory reset, do it.

If for some reason you still get an AVB-Error and end up stuck in fastboot mode just flash the stock image and try to patch it again.

This is my first post on here and i didn't have much time but i'm glad if it helped at least one person.
[Google Pixel 5 Guides, News, & Discussion] Ivixmax:
Thanks for create this post.Works perfect,😊
[Google Pixel 5 Guides, News, & Discussion] ridobe:
Hey, thanks for this. FYI @LazerL0rd (zest kernel) detailed here (click on the spoiler) how to do this with just the command line and factory images and without the need for the AFT.

edit: formatting
[Google Pixel 5 Guides, News, & Discussion] vandyman:
I keep on getting the AVB-Error to no end.
[Google Pixel 5 Guides, News, & Discussion] morpheus620:
new beta magisk not working
[Google Pixel 5 Guides, News, & Discussion] myhuky3:
Make sure to disable verity & verification and use magisk canary, not beta
[Google Pixel 5 Guides, News, & Discussion] morpheus620:
okay. is working. sorry für the misstake.
[Google Pixel 5 Guides, News, & Discussion] myhuky3:
Alles gut 😀
[Google Pixel 5 Guides, News, & Discussion] greenlight63:
Anyone able to get safety net to pass on Android 12?
[Google Pixel 5 Guides, News, & Discussion] myhuky3:
Unfortunately no, universal safetynet fix 2.0.0 by kdrag0n makes basicIntegrity pass but since the update to dp3 CTS still fails.
[Google Pixel 5 Guides, News, & Discussion] tauio111:
Dirty flashing newer factory images will restore the verity and verification state, so when you patch the kernel with magisk it will fail to boot again.

Installing a verity and verification disabled image without wiping from the web based flasher will also corrupt your data and not let the phone boot, forcing you to wipe.

Wonder what the flags are for flashing factory images with verity and verification state off and giving the ability to continue on without wiping and being able to boot the magisk patched kernel again.

fastboot update --disable-verity --disable-verification image-redfin-spp3210325.010.zip maybe?

Or prepatch the boot.img before flashing it with fastboot, and then flashing it back before rebooting from after flashing the factory image as an update?
[Google Pixel 5 Guides, News, & Discussion] myhuky3:
Don't know but sounds interesting. I just use

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

after every update
[Google Pixel 5 Guides, News, & Discussion] caballon:
Works like a charm Android 12 pixel 4a 5g
[Google Pixel 5 Guides, News, & Discussion] THEVAN3D:
I just installed the newest Public Beta via OTA. Can I root? I was rooted on 11 before and just enrolled in the beta program and installed it via OTA. Without factory reset or reflash. Now I tried patching boot.img via Magisk Manager, but it wont boot. I mean it boots, but wont unlock phone to homescreen. I'm locked out of my phone. Reverted back to stock PB1 boot image. Any ideas without factory reset?
[Google Pixel 5 Guides, News, & Discussion] QuickInfo:
I just tried it using the canary build and it won't boot either. It gets stuck at the Bootloader screen and shows "Failed to load/verify boot images". Maybe we need to wait for an update to for Magisk?
[Google Pixel 5 Guides, News, & Discussion] kafisc:
Did you try it according to the manual from the first post from @myhuky3?
[Google Pixel 5 Guides, News, & Discussion] QuickInfo:
Not yet, I'll wait until the end of the beta program before I reset it. I can get temporary root by booting into the patched Magisk boot image
[Google Pixel 5 Guides, News, & Discussion] badapple420:
Following the OP it worked great on the public beta been running it since last night its awesome thank you for the guide
[Google Pixel 5 Guides, News, & Discussion] bubbyj:
delete
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Totally. I never OTA. I download the patch each month (and betas prior to A12) and manually patch boot, flash, flash patched boot. It's been flawless. The verity thing throws in a wrench to be sure.
[Google Pixel 5 Guides, News, & Discussion] snovvman:
I can't find the posts to which you refer. Did they have success with doing that? I always flash using ADB/fastboot, so it's not an issue.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I'm not entirely sure. I think a lot of people try things and just don't say anything when they succeed, so the rest of us are left wondering.

While I don't really want to wipe my phone again, there are a couple things I would like to test:

* Can we take the OTA to preserve /data, then dirty flash the system image (or vbmeta alone) to be able to run patched boot images? (Answer: Yes)

* Can we dirty flash the factory image without wipe after the OTA, using the Android Flash Tool?

(Answer: Also yes, but flashing vbmeta alone is easier)
[Google Pixel 5 Guides, News, & Discussion] snovvman:
I would really appreciate to know your test results. It can help a lot of people.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Here we go:

Rebooted to bootloader, flashed vbmeta.img without flags, rebooted. No boot: "failed to load/verify boot images". As expected.

Flashed vbmeta with flags:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Booted into system, obviously still have root because I didn't touch /boot.

I think that's our ticket, and the fastest way to do this without dirty flashing the whole image, which shouldn't be necessary.

I don't really want to wipe and downgrade right now for the sake of upgrading again.

It appears that the contents of /vbmeta still matter even if boot verification is disabled, because I tried

fastboot erase vbmeta

with and without the flags and still got the boot error. Flashed vbmeta again with the flags and all is well.
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Excellent work! Thanks for all your efforts and reporting. Based on what I can gather, would you agree that below is the procedure?

-Patch boot, have the patched boot.img for later

-OTA from A11 to A12b, data is preserved, root is lost

-Boot into bootloader

-Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

-Fastboot flash boot boot.img (patched)

-Boot into rooted system

-Win

Some questions/thoughts--

1) It's been a long time since I OTA'd. Can I still register the device for and receive OTA if I am rooted on A11 with bootloader unlocked?

2) The fact that A12 introduced the verification, I presume this is the new dance for future A12 patches?

3) I don't understand the part about the contents of /vbmeta and erasing it. Will you please provide a bit more background/context?

Again, thank you.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
The first time, yes. And make sure you keep that patched boot.img as well as the vbmeta.img on the PC, because this is what we'll do for subsequent updates (assuming you have Magisk installed)

1. Sideload OTA

2. Reboot to system, let update complete

3. Reboot to bootloader

4. Reflash vbmeta with disable flags

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

5. Live boot the patched boot image:

fastboot boot boot.img

6. Open Magisk (will have root) and patch the new boot image

7.Reboot, enjoy life

ALTERNATIVE:

1. Dirty flash the factory image with disable flags, let phone reboot and complete the update

2. Reboot to bootloader and proceed directly to step 5 above

You can still boot an "old" kernel as long as the Android version is the same, so extracting, patching, and flashing the boot.img each time should be unnecessary. Just boot the original patched image after the update, run Magisk, and patch the new kernel directly.

I don't know about stable OTAs, but when I enrolled in the beta program, I received the A12b5 OTA and updated that way.

I never received notifications for OTA updates while rooted on Android 11, but given the fact that an update would nuke root, I was OK with having to wait until I got home and could boot TWRP after the update to re-root.

Unless Google pulls something weird and decides to completely eliminate boot verification from Android 12, this will indeed be the new process.

No problem.

So my thought process was this: if we disable boot verification, meaning the device will no longer compare the /boot hash to that contained in /vbmeta, do the contents of /vbmeta matter?

The answer is yes, to a degree. What I don't know is whether a valid vbmeta image has to be there, or if just *something* has to be there. My guess is the latter, because I believe the device still loads the known hash from vbmeta, but just doesn't compare the hash from /boot. There is a possibility that it might also ignore /vbmeta altogether and just checks for data in the partition, although I doubt it.

And, given that vbmeta won't actually be compared to anything, I think we'll be able to use the same image over and over and over again through subsequent updates, instead of having to extract the new one each time.
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Re #1, by sideload, I presume you mean using Android Flash Tool? I've never used AFT. In the past, I just used ADB/Fastboot and flashed the patched boot.img immediately after the full image flash. The phone boots fine and it's rooted. Looking at AFT, I see that I can disable verity and disable verification. Doesn't this do the same thing as step 4? (I'm not clear on the difference between verity and verification).

Re #5, why is live boot necessary after #4 if I already have the patched boot.img? Why would I not just flash the patched boot in bootloader before booting?

Re #1, I thought doing it this way causes "corrupted data", which was why OTA was the only way to keep data without having to wipe?

Re #2, same as above, why wouldn't I just flash the patched boot before booting the first time? I typically extract the boot.img from the flash and use Magisk to patch the file before I do any flashing so it's ready to go.

Thanks for the explaination and sticking with this discussion. It's been immensely helpful. I'm almost ready to give this a try...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
AFT flashes a factory image, not the OTA; installing the OTA is either done automatically via system, or manually via ADB sideload. You can do either. Keep in mind that checking "force flash all partitions" requires a data wipe IIRC.

Here is a guide on using ADB sideload.

Flashing vbmeta takes about 2 seconds. Flashing the whole image takes 10+ minutes. I'm just trying to save you time here. But, if you're updating (say to A12 final or to subsequent updates) you can indeed update that way using AFT.

Again, to save time.

To take full advantage of an update, you want to be running the latest boot image. Of course, if you want root, it has to be patched. However, you don't HAVE to run the latest kernel; an older kernel will still boot and run the system just fine. So, you could flash the same original boot image over and over again, although I do not recommend this.

So, instead of extracting, patching, and flashing the new boot image every time there is an update, using *one* patched boot image to boot the phone will allow us to boot system with root, whereupon we can use Magisk to directly patch the new boot image.

Here's how it works:

- After the update, the image in /boot is stock and unpatched.

- We live boot the patched image via ADB; the phone does not boot the image in /boot. This is the same way we could temporarily boot TWRP on Android 11.

- The patched boot image has root, therefore functions that require root work when booted into /system.

- We just use Magisk to directly patch the image in /boot.

Otherwise, we would have to extract the image, patch it with Magisk the "unrooted" way, then move the patched image to the computer, reboot to fastboot, and flash the new patched image. This saves a lot of time negating the need to extract, patch, and flash the new image. All we do is patch it in Magisk using the rooted kernel, then reboot, and the *installed" kernel will be patched. Sorry if this is confusing.

If you're coming from a previous version of Android, yes. So someone who upgrades from A11 to the 12 beta or the 12 public release will want to update via OTA if they don't want to wipe.

Subsequent updates (same version of Android) can be done either via OTA or dirty flash factory zip without fear of data corruption.

You can absolutely do that if you want to do the extra steps each time. As I mentioned above I'm just trying to make things easier and faster.

You bet. I'm happy to help. I certainly don't know everything, but I'm willing to share what I do know. That's what makes forums like this work - people helping each other out.
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Based on the A12 page "You should only apply an Android 12 OTA image to a device running an Android 12 Developer Preview or Beta build", I guess I can't sideload the current A12b5 on top of A11. I suppose enrolling in A12b for OTA will install iterative versions of A12? For sideloading, it sounds like I might need the first A12 preview before flashing A12b5?

This clarifies my question, thanks!

Ah, this might have answered my question above. When you say OTA, I presume it means truly over the air rather than sideloading? Do you know if Over The Air will first install the A12 preview, then the latest beta?

But we would need to flash "

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" each time there is an update in order for the patched boot to work, correct?

Thanks again!
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Update: I found my old P3 XL (w/ A10) and used it as a test mule with success, this is what I did:

1) Sideload OTA A12b5

2) Reboot into bootloader

3) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

4) fastboot flash boot --slot all magisk_patched.img

5) Start

It booted with zero issues, data intact, and is rooted! Now I need to work on getting past SafetyNet. I though I read that the A11 method still works?

@V0latyle many thanks for your help! Cheers!
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Update 2: Magisk hide + SafetyNet Fix = SafetyNet passed!
[Google Pixel 5 Guides, News, & Discussion] prgopala:
Reckon this would also work if we flashed the factory beta images (without '-w' to preserve data)?

So like below

- flash factory images with -w removed

- Reboot into bootloader

- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

- fastboot flash boot --slot all magisk_patched.img

- Start

Thoughts??