rbd said:

Sorry to be a pest, but just to clarify -- have you used any QC chargers via a direct wired connection to the USB-C port on your S20, or only indirectly through wireless charging? I can imagine those two scenarios could be quite different.

Thanks!

Click to expand...

I'll be honest I'll have to check. Like I said, was was mixing and matching charging blocks, cables, and when applicable, wireless chargers.

It looks like it's time to "uninstall" your partner...

MrJavi said:

https://forum.xda-developers.com/galaxy-tab-a/how-to/sm-root-t4050329/page29


TWRP

https://drive.google.com/file/d/1TGNBgQeL8ZYZUQyGPVaubAA3iwOzExbH/view

I highly recommend you start from the beginning of the thread before flashing. @James L provided the link above.

Good luck and welcome to Android Forums @Jaqueek

Click to expand...

Great! Thank you <3

Links in emails do work, so it has to be a problem with your app or your settings rather than Android itself.

Unfortunately we need to know more than "this doesn't work" in order to have a chance at providing a solution. So to start, what email app are you using? Can you open links from other apps (news sites, Twitter, or whatever)? I also suggest you check the email app's settings to make sure that it doesn't have this function disabled (e.g. as a security measure, since clicking on a link in an email can be a high risk activity ). If you've installed any security app (often, misleadlingly, marketed as "anti-virus" is that set to interfere with such actions? I'm just speculating at this point because we don't know anything about your setup.

kuddus said:

You can also download screen shoot apps from google play store

Click to expand...

That is what I did, and it has been working fine!!

Main requirement: Enabled USB DEBUGGING

Man, I Nearly Died cuz rhis Happened with my 1st new 2month old phone.. just now..
But i actually fixed it without Factory Reset..
Ofcourse i searched up web badly too..
But every Answer said Factory Reset in the and..
So what i did was The Command u already know to reset Dpi through ADB, but even if u had your Usb Debugging on the shell gives error as "error: Closed". So my USB Debugging option happened to be ON cuz i was playing around in the phone's developer Option.

Then The Main TRICK GOES HERE:-
I COPIED THAT ADB COMMAND & STARTED SPAMMING IT ON MY COMMAND PROMPT / TERMINAL AND I WAS GIVING ERROR: CLOSED BUT SUDDENLY THE COMMAND WORKED WHEN THE MIUI BOOT LOGO SHOWED UP. AND THEN IT CAME OUT OF THE BOOT LOOP AND OPENED UP MY ANDROID LIKE BEFORE

Here ADB COMMAND= **adb shell wm density reset**

thakorsh said:

Hi guys,
Have any of you played Brain Test 2? it's a puzzle game that you've to find the patterns, and it's kinda cool, but I have a problem with a level. Where can I get some walkthrough or solution videos for games like this?

Click to expand...

Have you tried searching on Google, Bing, or Baidu?[/QUOTE]

Avivi said:

[QUOTE = "ocnbrze, post: 8008028, member: 123763"] συγγνώμη [USER = 2132448] @Avivi [/ USER], αλλά αυτός είναι ένας ιστότοπος μόνο στα Αγγλικά
Το google το μεταφράζει σε:

επεξεργασία:
έχετε τη σημείωση 2; Αν ναι, θα πρέπει πραγματικά να αναζητήσετε ένα νέο τηλέφωνο. [/ QUOTE]
Ευχαριστώ. Πραγματικάyou.

Click to expand...

again.....please use google translate or find a different forum that works with your language.

Try R-HUB remote support servers, a well know remote application for iPhone and iOS. It is easy to use and can be freely downloaded from Apple store. Plus works on all platforms viz Windows, MAC, Android, iOS etc.

Thanks everyone for your advice

Have you tried visiting calendar.google.com from a browser, logging in to your account and checking whether the calendar events are there. If they are then you just need to sync the new phone with them and it's done, doesn't matter about the old phone. There is a "bin" there, so it might be worth looking for deleted events there if you can't see them. There's also an "import and export" option in the settings there, so if you can find the events you could export everything so that you have an independent backup.

If the events weren't synced from the old phone then their being deleted from the old phone is the end of it. One of these setup apps (each manufacturer tends to have its own) shouldn't delete anything from the old phone, so something clearly went wrong, but that doesn't help now that it's happened. I don't think it's a "synced the wrong way" issue since they don't sync (two-way transfer), they just transfer (one way), and everything else transferred so you didn't do the process the wrong way round. But unfortunately that just leave "a bug in the app" as the explanation, which isn't something that offers any solution.

markdoc said:

I can tell you how, but before clearing the data, I would wait for ocnbrze. Clearing the cache won't mess up anything and could help. Clearing the data, I'm not sure. Anyway, go to Settings - General - Apps &amp; Notifications - App Info. Wait for the list of your apps (a second or two). Scroll down to Instagram and tap. Then tap Storage and you're there. I'm just not sure what clearing the data will do, I know cache is safe.

Click to expand...

Or just long press on the app and select the info button when it pops up

IMEI/IMSI would be a dumb way to ban someone, since changing phone/SIM would obviate the ban.

But I can confirm that 3rd party system info apps on my phone just show "unknown" for these vales these days.

(I have to confess that I'd not be comfortable with trying to help someone work around a ban from Tinder, since many of the reasons for banning people in Tinder's rules come under the heading of "protecting other users" and, with all due respect, we've no way of knowing why someone was banned or whether they are telling the truth about it. Plus of course even if we could be sure of your friend, any advice posted publicly could be of use to someone banned for very good reason, so there's a risk involved that way. It's moot because I can't tell you how to do it anyway, but questions of this sort are more problematic than you may see if you are only thinking from your friend's perspective).

codesplice said:

The screenshot shortcut has been removed from the power menu with Android 11. You can still capture a screenshot using the Volume Down + Power button combo, as shared by @ocnbrze, or with the screenshot option at the bottom of the Overview (recent apps) screen.

https://support.google.com/pixelphone/answer/2811098

Click to expand...

Thanks for your suggestion
please keep it up

yep just looked at a few apk websites that offer health sg and quite a few people are experiencing the "apk is hooked" error. after some research "hooking" is a term used in coding android applications.....but that is as far as i get in understanding what that exactly means.

i think you need to find a different app to use then this one as most are saying that the developers have not responded to their complaints.

I'm totally frustrated with the same issue on regular Galaxy S20

Welcome in @Emmi331. Pleasure to meet you.

Problem Solved! I was right that it had to do with permissions, but wrong about where the problem was. The problem is not in the manifest. It was my old working app was targeting SDK 22, and after updating Android Studio I targeted API 26. Starting with API 26, so called "dangerous permissions" like location must be established at run time. (Since Bluetooth can access location from external devices, location permission is required to scan for Bluetooth). What I was missing was that run-time code to ask the user for permission to access location. The relevant API calls are:

checkSelfPermission() to see if the permission has been granted already...

shouldShowRequestPermissionRationale() to check if I should display an educational dialog informing the user why I need the permission...

requestPermissions() to actually initiate the operating system dialog that asks the user if my app should be allowed that permission..

There is also a callback from the requestPermissions() call telling me if the user said yes or no.

If you search out these APIs you will find all the Google docs on how to properly request run-time permissions.

Since these APIs are not available for earlier Android systems, if you want to include those earlier systems, all these APIs must be wrapped in:

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M)


That's it. Once I implemented run-time permission checking, my app started working just like it did two years ago.