yashsingh1/xdaforums huggingface dataset:
[Tasker Tips & Tricks] Marienkaefer:
Hello,

I'm going crazy here.... I've installed Tasker on my new Lenovo Tab M7 TB-7305F (7 Inch with Android 9.0 GO - NOT rooted). Tasker works fine. Since I want to kill apps I installed the plugin "SecureTask". And: I succeeded to get it working. Everyting is working fine. Until I reboot. After a reboot: When I try Tasker to execute the plugin-command SecureTask - Tasker waits long and can't execute the plugin. It seems Tasker can't call the plugin SecureTask / can't connect to it. When I manually load SecureTask (Icon on the desktop - only a config-screen comes up - I leave the config-screen with the back-button): After that everything works again. It seems: After SecureTask was loaded once everything is OK. But Tasker can't start the plugin.

Humpf? After a lot of hours of investigating..... I'm out of ideas. Any help?
[Tasker Tips & Tricks] ktmom:
That sounds like there's a problem getting a background process running after boot for SecureTask. Assuming that all of the permissions for SecureTask have been granted through ADB, I would contact the developer and see what he says.

A work around might be to use Tasker to launch SecureTask after boot. You could then use it to close itself :)
[Tasker Tips & Tricks] Marienkaefer:
Thanks... exactly the opinion I have at the moment. In the meantime I found a contact address in SecureTask itself - so I will contact the developer.

Enabling SecureTask after boot by Tasker.... good idea :) That will be a screen-flickering... but that's at 5 am - so nobody will care about that. I will test this... :good:
[Tasker Tips & Tricks] Marienkaefer:
Just to report my efforts.... I contacted the support of SecureTask - and got an email-chat within minutes. Incredible support - thank's a lot, John Doe (support of SecureTask)!!!

He told me how to get a logcat. Reason, why it's not working:

BroadcastQueue: TabletMaster Service: not allowed to launch app com.balda.securetask/10110 for broadcast Intent { act=com.twofortyfouram.locale.intent.action.FIRE_SETTING flg=0x14 cmp=com.balda.securetask/.receivers.FireReceiver (has extras) }

=> The OS is blocking the broadcast. No clue why. So it seems my Lenovo Tab M7 TB-7305F has a strange behaviour... no chance to get it working.

Btw: Killing SecureTask with it's own didn't work. So I had to choose now a complete different approach without SecureTask.
[Tasker Tips & Tricks] Lord Sithek:
airplane mode

Hi, bit off topic maybe, but I saw that this is a quite recent threat and it is involved with SecureTask plugin, so I decided to hook up instead of creating new one :D

This week I bought Samsung Galaxy Tab S5e. It's operating on Android Pie and UI One interface. I'm reluctant to root it yet (all the more the procedure is not obvious), but I want to recreate as much functionality as possible from my old rooted Samsung tablet :) So SecureTask plugin is the obvious choice.

I'm trying to find a way to automate turning the airplane mode on/off. On my old tablet I created a profile that triggered airplane mode according the time schedule as soon as Tasker detects that the device is plugged in to a power source. I've tried to recreate this profile with the help of SecureTask. Of course in advance I granted to the plugin all possible permissions using adb and even successfully set it as the device owner. Then I found a secure setting responsible for turning the airplane mode on/off and set appropriate values. And when I test the created tasks, the green circle appears and the quick toggle in the notification drawer turns on, but it seems that the system doesn't listen to the call - the airplane mode actually doesn't turn on. The system seems to listen only when I turn the quick toggle on manually. So I wonder if there is something I'm missing or maybe it is not achievable at all without root on this firmware? :confused:

Would be grateful for any insight, maybe from you [MENTION=6617276]ktmom[/MENTION], boss :D Thanks in advance.
[Tasker Tips & Tricks] ktmom:
[MENTION=9630286]Lord Sithek[/MENTION], AFAIK, the only way you can toggle mobile data or WiFi radios is after a reboot and that may not work on all devices. Google "long ago" removed the ability to directly control those radios, even with root. Bluetooth does tend to toggle though.

So if it's going to work at all, you would have to toggle off and then reboot.

My opinion is its best to use touch emulations to activate the quick setting tile.
[Tasker Tips & Tricks] Lord Sithek:
:eek: Ok, thanks for the response. I have Auto Input plug installed as well, so I'll give it a shot
[Tasker Tips & Tricks] Lord Sithek:
The problem is that it needs to turn the screen on. I keep my device in book cover so... pain in the arse :cyclops: I think I'll probably switch to "do not disturb" mode, at least it works right away
[Tasker Tips & Tricks] maybeme2:
I too just purchased a lenovo Tab M7 TB-7305F (7 Inch with Android 9.0 GO - also NOT rooted).

Sorry for intruding.

Have you found a forum for this tablet?

One specific question I have is with screen rotation. In android pie you get rotation control by turning off auto-rotation in settings. That way when you rotate the tablet a small icon appears briefly in a corner. When that icon is tapped the display rotates. If not tapped on the display does not rotate.

That is what happens in my other android pie devices. But for some reason this icon does not appear on this tab. So I'm looking for a forum for help. Have you found one?
[Tasker Tips & Tricks] hyborian:
I don't know if it needs root (I am always rooted), but there is an Airplane Mode On and Off in Tasker, under Net category.

I have a task that checks if %AIR is on or off, and turn on and off accordingly.

---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------

It still is fine to toggle mobile data on and off (in my case, either Mobile Data 1 or 2 due to having dual sims), as well as wifi, without rebooting. Even works in Macrodroid (the mini Tasker-like app)
[Tasker Tips & Tricks] lennon_nz:
Android app Tasker
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Metzex08:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Metzex08:
boot command from mtty reads:

Cmd>boot

InitDisplay: Display_Chip=1

Fill RSVD information for block 288 to 309

Storage start sector=0xAB80, total sector=0x10740

Storage start block=707, total block=1053

Total Bad Block in CE: 0

Erase physical block from 995 to 2032

formatstorage Bad block found: 1045

si backup: Erase physical block from 2032 to 2048

No card inserted

OSSIPreLoad ++
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Try this

Try flashing this ROM and see what happens.

http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html

What does your bootloader screen show?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Metzex08:
Please Help!

Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".

I tried booting through MTTY, no dice.

My bootloader screen reads:

KAIS1*0 MFG

SPL-1.0.01OliPof

CPLD-8

I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
Threads merged.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] redbandana:
Some people go to far ahead before figuring out the real issue. Don't **** yourself.

Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] redbandana:
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] redbandana:
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?

Did you believe your bootloader screen would change after you flashed a rom?

Damn!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] redbandana:
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pfcsabre:
I had the same problem (continuous reboot) as before, see this thread:

http://xdaforums.com/showthread.php?t=383678

but the problem that I had is because of bad blocks, post your info 8 and maybe I can help :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Metzex08:
ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Metzex08:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved. :)
[Samsung Galaxy S10+ Questions & Answers] RashedTlass:
I have an S10+ and i live in france i recieved the update on samsung members however i registered 16 hours ago and still recieved nothing in the settings app i check the page and my status is "withdrawn" is this normal or is there something wrong?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Well, they're on the Google site. Now...to figure out which one is which ??
[Google Pixel 4 XL Guides, News, & Discussion] radiohead7778580:
Sweet!!
[Google Pixel 4 XL Guides, News, & Discussion] spencer92a:
Check here: https://support.google.com/pixelphone/thread/18553639?hl=en
[Google Pixel 4 XL Guides, News, & Discussion] iceman4357:
Wish we would get more details. Improvement on smooth display and camera doesn't give us much. Maybe they fixed some of the yellow tinted pictures in the camera.
[Google Pixel 4 XL Guides, News, & Discussion] Bwyan Benton:
I'll probably just keep mine on force 90hz anyways. My battery life has been just fine. Even running white theme all the time.
[Google Pixel 4 XL Guides, News, & Discussion] Jiggs82:
-14 looks like for me:D
[Google Pixel 4 XL Guides, News, & Discussion] StrangerWeather:
So nothing for QD1A.190821.011?
[Google Pixel 4 XL Guides, News, & Discussion] Jiggs82:
That's oct patch, you need to flash nov patch
[Google Pixel 4 XL Guides, News, & Discussion] iceman4357:
I have mine forced 90hz all the time. I always have a charger available and like the extra speed.
[Google Pixel 4 XL Guides, News, & Discussion] TheUndertaker21:
update without losing root ?
[Google Pixel 4 XL Guides, News, & Discussion] StrangerWeather:
I don't think so tbh, it's one of three variants: 014, 007, 011 based on this and this.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Not really. You'll need to flash the November update with the -w removed, let it boot up, then put a copy of the November boot.img on your internal storage, then patch it with magisk. Then you'll need to fastboot your patched boot.img, and you should be good to go :good:
[Google Pixel 4 XL Guides, News, & Discussion] TheUndertaker21:
Thanks figured as much

From my previous pixels
[Google Pixel 4 XL Guides, News, & Discussion] Jiggs82:
If you receive the OTA, you can just try this method from pixel 3 xl thread a while back as i did before on my pixel 3 xl too :
[Google Pixel 4 XL Guides, News, & Discussion] Sashtheflash:
So .011 Variants have to wait? No Update available yet.
[Google Pixel 4 XL Guides, News, & Discussion] Geekser:
I noticed that they show one of the downloads available are specifically for Verizon and ATT. I have a Google Unlocked Device - but I am on ATT. Does anyone know what happens if I flash the firmware intended for ATT? If my bootloader is locked when I flash it - will my bootloader be locked after flashing ? Just curious.....
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
No, it won't lock your bootloader. Only you can do that manually. I just updated mine to November, and all is well :good:
[Google Pixel 4 XL Guides, News, & Discussion] Bwyan Benton:
I usually would have had my ota by now. Still nothing for me. Kinda weird.
[Google Pixel 4 XL Guides, News, & Discussion] Msan2000:
Nothing for me yet either :(
[Google Pixel 4 XL Guides, News, & Discussion] Bwyan Benton:
It's weird. I wonder what's up with that.
[Google Pixel 4 XL Guides, News, & Discussion] CyberpodS2:
My guess is it's been replaced. Shouldn't matter seeing the radio is probably the only variation. Just pick the one that closest matches your provider.
[Google Pixel 4 XL Guides, News, & Discussion] wrongway213:
So... Face Unlock with eyes closed still isn't fixed? That's what I'm getting out of all this...
[Google Pixel 4 XL Guides, News, & Discussion] bobby janow:
I haven't seen it mentioned as fixed. Maybe an OOB update once they figure it out?

---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------

Which one did you pick? You threw a dart?
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
I used the 014.C2 version since I'm a big red customer. Seems to be working fine :good:
[Google Pixel 4 XL Guides, News, & Discussion] bobby janow:
Try it now.
[Google Pixel 4 XL Guides, News, & Discussion] [Fenix]:
That's sick

https://www.reddit.com/r/GooglePixe...ness/?utm_medium=android_app&utm_source=share
[Google Pixel 4 XL Guides, News, & Discussion] Bwyan Benton:
Yeah updating now.
[Google Pixel 4 XL Guides, News, & Discussion] dhorgas:
The green tint switching reported on Reddit was there from day 1. Glad I wasn't crazy. I figured out about a week ago it's related to the 90Hz display. By the way, getting the update now. It's a light 21.1MB. Seems a bit small but whatever.
[Google Pixel 4 XL Guides, News, & Discussion] Msan2000:
That sure took quite a while to update..
[Google Pixel 4 XL Guides, News, & Discussion] Bwyan Benton:
Yeah I know. But done now nonetheless.
[Google Pixel 4 XL Guides, News, & Discussion] chriskwarren:
I've been on Bell with my 2XL and it seemed that it was 3:30-5pm before I got mine, same as my wife on her regular 2.
[Google Pixel 4 XL Guides, News, & Discussion] sta3b:
steps to follow :

disable modules

boot.img ==> patch with magisk

copy image to pc

fastboot flash bootloader "path"

fastboot reboot bootloader

fastboot flash radio "path"

fastboot reboot bootloader

fastboot --skip-reboot update "path"

flashboot reboot bootloader

fastboot flash boot "magisk"

done!
[Google Pixel 4 XL Guides, News, & Discussion] Paz9:
is there any details as to what theyve changed with smooth display?

if its worth turning off force 90hz we may see a modest increase in battery when watching movies or watching <90fps videos / games
[Google Pixel 4 XL Guides, News, & Discussion] antiochasylum:
Turn it off. As long as you have Ambient EQ and adaptive Brightness on, it works as low as 0%. This is on the XL.

It you have a regular 4. It will stop working at 42% display.
[Google Pixel 4 XL Guides, News, & Discussion] madgooner2810:
Still haven't gotten the OTA. I have magisk installed, is that a possible reason why?
[Google Pixel 4 XL Guides, News, & Discussion] Paz9:
Great so now it works regardless!

I just turned out off, I don't have adaptive on or ambient eq on and it seems to stay on 90hz now
[Google Pixel 4 XL Guides, News, & Discussion] dtsjunk:
Hmm i have a German Pixel 4 (Flame) what image suits for my Phone?
[Google Pixel 4 XL Guides, News, & Discussion] Dilbert83:
Tis indeed the October patch.
[Google Pixel 4 XL Guides, News, & Discussion] wgrant:
I'm in the same boat and would like to know. I normally just do a fresh flash of the update but I'd rather do the OTA with keeping magisk.
[Google Pixel 4 XL Guides, News, & Discussion] EeZeEpEe:
Strange the update was dated a day ahead, November 5th, instead of the 4th.
[Google Pixel 4 XL Guides, News, & Discussion] bobby janow:
It's been that way for some time now. All patches have been dated the 5th even if you got them on the first.
[Google Pixel 4 XL Guides, News, & Discussion] EeZeEpEe:
Oh didn't realize that. Always thought it matched the first Monday of the month like it gets released.
[Google Pixel 4 XL Guides, News, & Discussion] gettinwicked:
If you're rooted with the Magisk patched boot image, then yes. You won't even get a notification I don't think. Flash the stock boot image from last month's image. At that point, it shows as stock and you should get the OTA notification.
[Google Pixel 4 XL Guides, News, & Discussion] spaceman860:
Even if you're rooted with a custom kernel you'll still get the OTA notification it just won't install unless on stock unrooted kernel
[Google Pixel 4 XL Guides, News, & Discussion] matssa:
I'm trying to do the same however it doesn't find the factory boot image, my guess is that when you flash magisk via twrp it backups the boot image whereas when you fastboot it doesn't. Therefore it cant find the backup.

A nice fix would be to add the stock boot image as the backup (where and what file name?) So that you don't have the issue. However need to do the same each time, just avoids you to use magisk, patch boot image, fastboot.
[Google Pixel 4 XL Guides, News, & Discussion] hrdc69:
As a relative noob to rooting I am confused as there seem to be several ways of taking the update once rooted. The above poster gives one way and I read the tutorial on the Magisk GitHub page on how to retain root after an OTA update and it doesn't say anything about downloading and patching the boot image of the update. This conflicting advice is confusing so which is the easiest way to update without risk of a $1,000 paperweight. Thanks in advance for any guidance.
[Google Pixel 4 XL Guides, News, & Discussion] sta3b:
hello, i update the old fashion way, so follow these steps, it takes like 5min to update ur phone and restoring root

-disable all magisk modules

-reboot phone

-download the october update from google website https://developers.google.com/android/images#coral , select the appropriate model for ur phone

-take the boot.img located in the zip update file, and paste it in ur download folder on the phone

-make sure OEM is unlocked and USB debugging enabled from dev. options

-open magisk, patch specific file and choose boot.img

- disconnect/connect phone

-go to your downloads folder again and copy paste magisk_patched.img to ur PC

- download fastboot and adb from : https://wetransfer.com/downloads/63...e2932c748ef515a62c68fff520191105173148/6c3a4c

-copy magisk_patched, boot.img , image.zip , bootloader.img , radio.img to your fastboot folder.

-make sure oem and usb debugging are on

-boot ur phone to fastboot mode : turn it off, turn it on and keep ur fingers on the power button and volume down

-open CMD and type CD "path" path is the path of the fastboot folder

then via cmd execute those commands :

fastboot flash bootloader "path" (bootloader.img path)

fastboot reboot bootloader

fastboot flash radio "path" (radio.img path)

fastboot reboot bootloader

fastboot --skip-reboot update "path" (update.zip path)

flashboot reboot bootloader

fastboot flash boot "magisk" (magisk_patched path)

reboot ur phone when done, keep in mind if the phone does not reboot from the 1st time and is stuck on a boot loop, u need to flash the boot.img back , boot phone, then reflash magisk image so :

fastboot flash boot "path of boot.img"

fastboot flash boot "path of magisk_patched.img"

enjoy !
[Google Pixel 4 XL Guides, News, & Discussion] matssa:
Hey anyone know which one I should use for Europe (France)? Cuz US carriers and all is nice, but doesn't give any info for the others. Otherwise a link showing which carriers are concerned for the octobre update?

EDIT///

Ok so flashed back the October update and OTA-ed without magisk and the version I got is QD1A.190821.014, even though I'm in FR and not UK...
[Google Pixel 4 XL Guides, News, & Discussion] krabman:
The magisk shortcut for taking the OTA and then doing the uninstall//reinstall with Magisk dosn't work well with Pixels or at all in some cases. Easiest way I know is to get the full image extract the boot image and plug in. Send the boot to the phones root and then flash the full image with the wipe removed. Boot up and have magisk patch the boot image and then drag the patched boot over to the PC and flash it. Usually takes about 10 minutes all in once you've done it a few times. Little longer for me because I always create a new Ti backup before I install the monthly, I'm often out of internet coverage so I need to maintain an offline fallback position.

About getting the OTA, sometimes it's quick or it can take days or even a week or more but you will eventually get it on the unlocked devices rooted or not. Not sure about the carrier versions because I've never owned one. On the unlocked though my 3 and 3a would sometimes take as much as ten days after the OTA starts rolling out before it would show up. That's rooted all the way, don't know if the variable delay also applies to the non rooted phone, Never owned one of those either.