yashsingh1/xdaforums huggingface dataset:
[Tasker Tips & Tricks] djparent:
I'm a little late to the party but wanted to share a workaround I found in case anyone else is having trouble accessing Samsung backup with Securetask set as device owner.

I have a S21 Ultra, and after enabling backups via the plugin only Google backup was working. I needed Samsung backup to work so I kept looking around. While what I found isn't automatic, you can't still manually backup and restore from Samsung cloud. The steps are:

1. Go to settings and click ACCOUNTS AND BACKUP

2. Select MANAGE ACCOUNTS

3. Select your SAMSUNG ACCOUNT

4. Select MY PROFILE

5. Select SAMSUNG APPS AND SERVICES

6 Select SAMSUNG CLOUD

Once in Samsung Cloud you can manually backup and restore your phone as normal! It seems Samsung only greys out the menu shortcut in settings without actually disabling the Cloud. I hope this helps someone!
[Google Pixel 3 XL Questions & Answers] jessepatty:
I think I may have inadvertently snoozed or killed all notifications from my home security system's app.

I stopped getting motion alerts from my cameras about 2 weeks ago and not sure why.

When I go to settings, apps and notifications, then look at the app itself it says they are on but I'm not getting any of them. If I go into the app, it shows they were sent but my Pixel is not displaying them.

Where else can I go in settings to find where they may have been blocked?

I contacted the system app developer and they said their system shows they are sending them to my account in the app.

Thanks in advance for any information you can provide.
[Google Pixel 3 XL Questions & Answers] Eudeferrer:
Perhaps uninstalling the app and reinstalling again might fix your problem.
[P3300, MDA Compact III ROM Development] winston0122:
:confused:hello guys can you tell me how to format the mmc card by artemis. which software do i need.
[P3300, MDA Compact III ROM Development] soardiac:
i use a card reader for my windows pc (actually, my laptop has one built-in).

i think with SKTools you can do it one your PPC.
[Xiaomi Mi 8 Questions & Answers] denzel09:
Sometimes after the "raise to wake" happens that IR face unlock function remains off. So in these cases i need to use the fingerprint sensor.

I have all batteries save options off.

Any solutions?
[Xiaomi Mi 8 Questions & Answers] galakty:
Works fine for me.
[Xiaomi Mi 8 Questions & Answers] denzel09:
Yeah it works, but sometimes has the behaviour written above :confused:
[Xiaomi Mi 8 Questions & Answers] motherninja:
Face Unlock is working fine for me, never had any single issues with it. I'm always with Xiaomi.EU latest weekly releases.
[Xiaomi Mi 8 Questions & Answers] galakty:
No issues for me ;)
[Xiaomi Mi 8 Questions & Answers] denzel09:
Strange, i don't know. Sometimes happens that after raise to wake the IR face unlock remains off indeed i don't see the "red" light, btw...
[Xiaomi Mi 8 Questions & Answers] denzel09:
Really no one has sometimes this problem with IR face unlock? Really never?
[OnePlus 6T  Questions & Answers] molitar:
I am unable to switch to speaker phone when I take a call from lock screen. This is a big problem for me so how can I answer with speaker phone? Otherwise I am trying to unlock screen while call coming in and miss the call!
[OnePlus 6T  Questions & Answers] Frankenscript:
Hi folks,

I will set up my 6t on Tuesday, switching from my 3t. Does the 6t (direct from OP, NOT the T-mo) have a built in APN set up for ATT? Or do I need to configure one? And if so, what is the current optimal setting list to use?

Thanks!
[OnePlus 6T  Questions & Answers] sharksfan7:
The device should pick up the APN once you insert your SIM. I didn't have to manually enter anything when I set mine up.
[OnePlus 6T  Questions & Answers] Frankenscript:
I've setup my new 60. It's going great! The SIM card did result in not one but two AT&t APNs and it automatically chose one called something like next-gen smartphone. The other one AT&t phone is the setting that I used to use on older devices. for now I'm leaving it on the next-gen one because everything seems to be working including visual voicemail with speech to text. The only thing I haven't noticed is VOLTE coming on but I don't really care that much about it.

Picture attached.View attachment 4673156
[OnePlus 6T  Questions & Answers] p51d007:
Could you go into the APN setting, and see if there is anything different, than the standard at&t settings

see if any of the following are different

MMSC

MMSC Proxy

MMS Port

MCC

MNC

APN Type

APN Protocol

TIA

Just curious
[OnePlus 6T  Questions & Answers] sharksfan7:
The Nextgenphone APN supports faster LTE speeds as well as VoLTE. I had issues when I first got my 6T and lost LTE service for a couple of days when I was using the Nextgenphone APN. When I switched to AT&T Phone APN, I was able to get data but it was only 3G speeds.

To enable VoLTE, you need to follow the instructions in this post, https://xdaforums.com/showpost.php?p=78073766&postcount=6. After you tick the VoLTE switch, in OnePlusLogKit, go into the SIM settings and you should now have the option to enable VoLTE. Turn that on and if your line is provisioned properly, you should have VoLTE. You may need to reboot.

Were you able to activate AT&T Visual Voicemail app?
[OnePlus 6T  Questions & Answers] Frankenscript:
I'm attaching screen shots of the Next Generation APN settings here. The only difference I see is that the APN Type / Protocol support both IPv4/IPv6 (ATT Phone supports just IPv4).
[OnePlus 6T  Questions & Answers] Frankenscript:
I haven't yet gone through the VOLTE process described above. PResumably I will one day but I rarely use the phone for talking and when I do the standard stuff works fine. :) :D

No problems activating ATT Visual Voicemail. After activating it, I called from another phone, left a message, and almost instantly got a notification, and when I went to the app, my transcribed text was waiting as well as the listening controls. Note, I did have to go into settings after activation and turn on the transcribe function, which is off by default.
[OnePlus 6T  Questions & Answers] borijess:
Where are u getting the visual voicemail app
[OnePlus 6T  Questions & Answers] Frankenscript:
Not sure actually. It came either from my Google backup or via OnePlus switch. But it's in the play store. I'm using a version dated October 2018.
[OnePlus 6T  Questions & Answers] borijess:
This one?
[OnePlus 6T  Questions & Answers] borijess:
This one

Update: I just tried it out. It worked.
[OnePlus 6T  Questions & Answers] borijess:
.View attachment 4673727
[OnePlus 6T  Questions & Answers] Frankenscript:
? Was there supposed to be a picture? I'm on Tapatalk now and not seeing one.
[OnePlus 6T  Questions & Answers] p51d007:
Except for mine saying tfdata (Straight talk, tracfone card, at&t towers), the settings are the same.

the links for mms are different, but everything else is the same.

Thanks!
[OnePlus 6T  Questions & Answers] borijess:
Yes for some reason not uploading the screenshot. Here is the link.

https://play.google.com/store/apps/details?id=com.att.mobile.android.vvm
[OnePlus 6T  Questions & Answers] Frankenscript:
That's the one I am using.
[Nook Touch General] Pajamaman:
I have a rooted NST running relaunch. I like the keyboard. I like the left and right arrows that allow me to position the cursor easily. Is there any way to extract the apk for the keyboard? I want to use it on an Onyx ereader.

I remember finding here on this forum a while back a post with a zip that contained all the NST apk files.
[Nook Touch General] nmyshkin:
Here you go. It may not work on other devices or have need of missing library files. It may not run as a user app.
[Nook Touch General] Pajamaman:
Many thanks!
[Shield Android TV General] whiteak:
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
[Shield Android TV General] ACiDxCHRiST:
I don't modify the system partition if I can avoid it. I just disable System Apps if I want them gone; however, I am fully confident that I could delete anything in /system if I wanted to. Is /system mounted as +rw? Not all Root File Managers are created equal. I recommend Root Explorer. It is not the most modern and feature rich file manager, but when it comes to Root File Managers specifically, I haven't found any other that can compare.
[Shield Android TV General] whiteak:
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
[Shield Android TV General] ACiDxCHRiST:
I would test it for you if I had a system.img for v7.2.1 that I could reflash real quick. I just don't feel like flashing v7.2.0 then updating to v7.2.1 again to restore an unmodified system partition.
[Shield Android TV General] sconnyuk:
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:

C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat

Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))

Finished. Total time: 10.295s

Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))

Finished. Total time: 15.641s

< waiting for any device >
[Shield Android TV General] ACiDxCHRiST:
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0

If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.

Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
[Shield Android TV General] sconnyuk:
I have 2017 Shield TV 16gb, which is on stock 7.2.1

I am using platform tools you suggested previously.

im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.

Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?

Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it. Also i can adb push/pull/install no problems.

I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.

Im running out of ideas to be honest, quite the nightmare im having.
[Shield Android TV General] ACiDxCHRiST:
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.

Also try running with an elevated Command Prompt with admin rights.
[Shield Android TV General] sconnyuk:
Yes i always use admin rights with CMD.

I will try re locking and unlocking again later today. (i cant see how nobody else has had issues like mine)

Thanks, il report back.

---------- Post added at 09:00 AM ---------- Previous post was at 08:36 AM ----------

Just tried re locking my bootloader then unlocking again and get same output:

Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.

C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat

Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))

Finished. Total time: 6.297s

Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))

Finished. Total time: 15.853s

< waiting for any device >
[Shield Android TV General] ACiDxCHRiST:
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
[Shield Android TV General] sconnyuk:
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.

As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.

I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.

I'll be in touch. ?
[Shield Android TV General] ACiDxCHRiST:
Here is the cable that I use: https://www.amazon.com/Cable-Matters-2-Pack-Male-Black/dp/B00HSS9IDW
[Shield Android TV General] sconnyuk:
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time :)

Thanks for all your help.

Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
[Shield Android TV General] ACiDxCHRiST:
Awesome
[Shield Android TV General] sconnyuk:
So from a virgin 7.2.1 we can after all flash a modded boot ??.

Just have to wait for a TWRP that is working on 7.2.1 now.

Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.

I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
[Shield Android TV General] ACiDxCHRiST:
What do you need TWRP for?
[Shield Android TV General] nadia p.:
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.

I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?

Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
[Shield Android TV General] sconnyuk:
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.

Also if any magisk/xposed modules make my box not boot to restore also ??
[Shield Android TV General] ACiDxCHRiST:
The SHIELD TV will only force you to update when you are going through the Initial Setup after a data wipe. If you follow the guide exactly as written and your bootloader is not unlocked yet, you will be forced to update to v7.2.1 after unlocking the bootloader. But since there aren't any more data wipes and the last step is to flash the v7.2.0 image that we modified, you will end up on v7.2.0 without being forced to do the Initial Setup again. In fact, you could likely use the same steps in the guide to install other versions.

As for what Magisk patches, it modifies the bootloader to trick the OS into thinking that the SU binary is in the system partition without actually modifying the system partition.

Roger that, makes sense.
[Shield Android TV General] sash11:
That is strange. I logged in and see all 7.2.3 images right on top. Here are direct links to different models:

NVIDIA SHIELD ANDROID TV Pro (500GB version)

NVIDIA SHIELD ANDROID TV (16GB version)

NVIDIA SHIELD TV (2017, 16GB version)
[Shield Android TV General] arifnihat:
I would like to do the method described in this topic: https://xdaforums.com/shield-tv/orig-development/netflix-amazon-5-1-hdmi-arc-optical-t3894442

I did exactly what was described in this thread, without any problems. But I still get the following error. I didn't get root.

Any solution?

(Firmware 7.2.2.)

adb root
adb remount

Not running as root. Try "adb root" first.
[Shield Android TV General] mLgz0rn:
Are you running the developer build or the ota one?
[Shield Android TV General] arifnihat:
As described in the first message of this thread, i have downloaded "NVIDIA SHIELD TV 2017 Developer Only OS Image 7.2.2"
[Shield Android TV General] mLgz0rn:
It might be because the /system and /data folders are read only on 7.2+.

Try doing adb disable-verity

And then reboot into the bootloader.

Patch the boot.img without ticking preserve dm-verity in magisk manager and flash it onto your shield.

Then reboot into android and see if it works.

If not, you should be able to manually place the files in the folder now using a root explorer.
[Shield Android TV General] Largewoodenspoon:
Evening guys.

If someone has a minute, could they upload the (magisk 18.1) 7.2.3 developer image patched boot.img for 2017 16gb model please.

Many thanks guys!
[Shield Android TV General] el7145:
would that give us the ability to mount the sytem and make changes to the system folder (ie. delete system apps)?
[Shield Android TV General] DumbKing@letthemeatspam:
Wiat so you didn't need to downloaded the rooted developer image? Interesting i thought that was required

Could OP update the original post with instructions on how to upgrade from existing root?

edit--nvm, I figured it out following your guidance thank you! Hopefully magisk will be able to do this automatically in the future

also, has anyone try installing directly via magisk with the "direct install (recommended)" option? adding an additional computer to this is complicating it and making it harder
[Shield Android TV General] mLgz0rn:
Yes :).

I can at least, using an app like titanium backup.

---------- Post added at 15:39 ---------- Previous post was at 15:36 ----------

So I just did some testing.

And I could only get adb root to work with the stock boot image and not the one patched with magisk.

So you could try flashing the stock boot, do what you need to do and then flash the patched one again.
[Shield Android TV General] elliwigy:
lol you are looking at the update.zip... the one who got the boot.img said he did a "full" update so no patch files.. theres a setting somewhere to always dl full images for future reference
[Shield Android TV General] elliwigy:
with an unlocked bl u can magisk patch stock boot.img and use it.. the dev os images basically allow a root shell without anything being patched.. at a regular user level with an unlocked bl theres not much of a difference between stock and dev os

also, i wouldnt cpunt on magisk ever doing it automatically lol.. with securoty updates n who knows what else chances are high itd break stuff.. would cause more issues than anything for the dev..
[Shield Android TV General] elliwigy:
sounds like u have some other issues lol if by stock u mean dev images then that is typically only a root shell.. patched boot should have worked
[Shield Android TV General] illalliance:
You're right I found the setting in developer options at the very bottom. Thanks for pointing that out!
[Shield Android TV General] mLgz0rn:
Well it does not, and seeing what others a saying here im pretty sure it's correct.

You try using a patched boot image on 7.2.3 and see if you can do adb root.

I tried this on a freshly factory reset stv 2017 with 7.2.3 flashed.

With the stock boot image that came with 7.2.3 dev I could use adb root.

After patching that boot with magisk 18.1, adb root did not work. Has been like this with all the 7.2+ builds.
[Shield Android TV General] elliwigy:
i have been on 7.2.2 with 0 issues since it launched.. others also posted they updated with 7.2.3 and is working fine was all i was saying..

it seems ppl have trouble every update but others dont have any trouble

with that being said, dev img has adb root by default.. magisk patches it and clearly in that process removes adb root inadvertently but usually doesnt matter because you have root anyways
[Shield Android TV General] jeffshead:
I followed the original post and installed 7.2.2 dev, a couple of month ago. So if I update to 7.2.3 using the auto-downloaded OTA update, I won't notice any functionality differences than if I manually download and update using the dev image from the NVIDIA site? I'm mainly asking if I will loose any root privileges with the OTA update vs the dev image. Will all of my settings, apps and data remain after the 7.2.3 update regardless if I use the dev image or the OTA?

UPDATE: I went ahead and downloaded the 7.2.3 Dev image and used it to update. I just followed steps E-F. So far, so good. All pre-existing apps, data and settings seem intact.
[Shield Android TV General] elliwigy:
just updated and tested.. you can easily get adb root on magisk patched boot.img.. you are probably getting a permission denied correct? That is because you not only need to flash patched boot you also need to install magisk manager then run it and let it set up environment..

without the manager when you run su from adb it has no manager to grant it so it denies it automatically..

in the past patching the boot.img would also install magisk manager when flashed but now u must install magisk manager manually after you flash the patched boot..

it works business as usual and as intended same as all the 7.0+ builds
[Shield Android TV General] elliwigy:
yea, i personally always clean flash but yep, magisk is super easy no matter how you update.. once on 7.2.3 you only need to patch the boot.img then flash it in fastboot then if needed install the magisk manager.. its the same for all the updates so far
[Shield Android TV General] mLgz0rn:
I'm not talking about su in the shell, I'm talking about "adb root" so you can actually do adb push to the system folder.

I know that you must manually install the magisk manager, I already have that :)
[Shield Android TV General] elliwigy:
you should be able to do the ssme things for the most part.. just gotta use root shell, mount system rw then u can push to system.

if u want u could also modify the patched boot.img to get adb root back along with magisk
[Shield Android TV General] mLgz0rn:
I mean, I myself has no issues with it not working, since I did it manually.

But people are trying to use koyings guide here

https://xdaforums.com/shield-tv/orig-development/netflix-amazon-5-1-hdmi-arc-optical-t3894442

Hence my post in the first place.

You can't do those steps with the "default" patched boot using magisk. Without as you are saying, modifying the patched boot yourself.
[Shield Android TV General] elliwigy:
sure u can.. just need to slightly change the scripting you can use shell commands.. like a 1 click batch or something.. put everything in a folder.. have script push files to data/local/tmp, adb shell su, mount system rw, backup w.e u want and push the files to system all in one script.. now if ppl r lazy to do one extra step or have no idea how adb/shell works then dunno wat to say lol

but magisk for some reason changes some prop values in kernel like userdebug to user, debuggable to 0 etc etc so in theory could change it back and should work again

to add, ppl should just do that first then root with magisk so they dont have issues
[Shield Android TV General] mLgz0rn:
I just figured out what in magisk that was changing the prob values and why.

It's MagiskHide.

After disabling magiskhide and rebooting, adb root, adb remount and adb push now works.

So I guess you could use the Magisk module MagiskHide Props Config to make it not change debuggable to 0, build to user instead of userdebug etc.

https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props