Can you point me to the right direction/link about using tasker to do it?
I have been trying to search for this and couldn't find answer.
Using weekly MIUI and WhatsApp is not found in "More Dark Mode Options", where one can check/uncheck individual app to turn on/off dark mode.
Starting the app triggers the log below. So when tasker catches it, it will first disable the app, before tan2go fully launched. So I don't need to kill the app like you did. Same thing is done when closing the app (enable magisk app).
the logcat feature in tasker is really useful and powerful.
Gotcha. At the mean time I managed to create logcat event based catcher and used your command in shell. It works with launching tan2go app from app drawer and from notification menu. Thanks for the freeze command!
Has anyone tried to shake their Mi 10 Ultra shaking in left-right direction?
I can hear some "ball" stuffs hitting edges. Something like "liquid paper correction pen" sound when you shake it.
I didn't notice this until now. Is it okay?
See attachment. Something is not right with the charging process? :confused:
Last night and many nights before, when I plug in charger and leave the phone at the living room, this always happens.
Edit: reuploaded attachment.
I had the same problem, where my bank app detects root even it is hidden in Magisk. The bank app is DKB (Germany).
Solution is to use Magisk Canary. I'm not sure what the difference are between Canary vs Stable/beta, but it works with Canary.
Give it a try. Hope it helps.
Skill-wise it depends on your Android knowledge and confidence. Hardware-wise it depends on if your phone is rooted or not. Personally I used the method under EDIT1 because I know what I was doing.
Yes you need a persist file from other users. Correction to what I said earlier, the persist...
The solution is 100% working, IF (big IF) you have the exact problem like we did. Most of those who said didn't work basically have other problems and not this exact problem that we faced.
The persist file is in /root.
Yep, have been using the xiaomi.eu ROM for 4 days. I confirm the abovementioned method works.
1. Use another fastboot.exe (just take the one from miunlock when you unlock your bootloader)
2. Start the .bat file (after this step you will stuck in bootloop)
3. Go recovery and clear data (yep, the...
I'll add my observation here:
OTA update via magisk OTA update method works, but for some reason I kept having frozen screen after a few minutes usage. Rebooted at least 4-5 times and it worked.
I was using Taichi and its Magisk module doesn't work. Reflashing the module causes bootloop.
This is the guide with the download link.
For me it would be nice to keep the Mi Wallet from China ROM though. The phone can be a MiCare Level 1 NFC key.
so just real quick: Unlocking the bootloader is use the miflash_unlock right? Do I need to toggle on "OEM unlocking" in developers mode? I don't wanna wait a week just to realize I need to have that already checked beforehand.
In my case the phone is not charging wirelessly. Anyone has the same issue?
EDIT: Nvm found the solution. Apparently the coil is slightly off from the car charger position. Just need to insert the phone from top and it will have contact. 20W charging.
If some sensors work and some don't, then your problem's root cause is not the same as the issue that we faced in this thread. In our case, it is all sensors works in Pie but all sensors fails in Android10.
Doing whatever "fixes" in this thread will not help solving your problems.
what you could do is try to check if the sensors are fine in Pie. If it does, that means your hardware is working. If it is not, then contact google.
I suggest get someone else's persist folder because your sensors calibration file in the folder might be already corrupted. Ours did.
Or the app updated its security.
My bank app updated and with magisk+rename+magiskhide, it still detects alteration. https://forum.xda-developers.com/showpost.php?p=83132175&postcount=181
Solution is to use magisk canary. Maybe you can try.
Hello you both.
This issue is solved quite a long while ago. See https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Root cause: TWRP loggings are stored in /Persist folder and corrupted the sensor calibration files inside.
Solution: Restore the calibration files...
how do i setup/revoke usb authorization? Mine stuck on device unauthorized when performing adb devices
Seems like there is no "revoke USB debugging authorizations" anymore?
Currently on latest version on my backup U11 DUGL.
I'm just gonna bump this up again because there seems to be no solution to this. Anyone who manages to get this work please shred some light.
I'm on Google Pixel 3 XL, magisk rooted and had the modules installed but not working.
Ermm, I think you didn't understand the whole picture in this thread. This issue is solved. The main problem is the sensors stopped working in Android10, but the sensors work again when reverted back to Android Pie. The cause was TWRP used a folder "persist" when generating logs and it corrupted...
yes, provided magisk could find your original boot.img. I didn't disable those modules and they still work. Just make sure you follow the guide:
Sorry to say your situation doesn't sound like the issue that we had here. For us none of our sensors were working upon clean Android 10 installation.
I'm not sure what device he had in #110, but I'd assume he has a Pixel3XL (crosshatch), given that this is a crosshatch forum. Since you have a...
I'm on beta play services and on 19.8.29 but for me I still need to have indirect mocking to be ON to spoof.
Without indirect mocking, I could mock my location if I turn off Location Accuracy, but I can't move joystick around. Kinda bummer.