#task #CheckRadiosSignalStrength
DESCRIPTION
This task includes different methods by which you can get the signal strength for the device radios.

Available radios:
• Wi-Fi
• Cell
• Bluetooth

Notes:
- Thanks to @plepleus (Reddit) for Cell signal base task, and @gerardo246 for contributing and testing also.
- You can go here (ASU signal), here (CellSignalStrength API) to get relevant information.

CREDITS
@SmartPhoneLover
@plepleus
@gerardo246
@darkskiiiin

CHANGELOG
- New: Added %(CELLSIG) built-in variable as a new method. (thanks @darkskiiiin)

VERSION
v1.1

#task #CheckRadiosSignalStrength
DESCRIPTION
This task includes different methods by which you can get the signal strength for the device radios.

Available radios:
• Wi-Fi
• Cell
• Bluetooth

Notes:
- Thanks to @plepleus (Reddit) for Cell signal base task, and @gerardo246 for contributing and testing also.
- You can go here (ASU signal), here (CellSignalStrength API) to get relevant information.

CREDITS
@SmartPhoneLover
@plepleus
@gerardo246

VERSION
v1.0

#task #CheckInternetAvailability
DESCRIPTION
This task includes different methods by which you can check if Internet access is available.

Notes:
- Thanks to @MadManX99 (Reddit) and @agnostic-apollo (Reddit) for helping on improving it.
- As ICMP traffic can be blocked/filtered by Google (as other servers too), you can use the following root servers sites: Site_1, Site_2.

CREDITS
@SmartPhoneLover
@MadManX99
@agnostic-apollo

CHANGELOG
- New: Added 'method 8' as a new way to test connection. (thanks @MadManX99)
- Other: Removed unused variables. (testing purposes)
- Other: Added root servers sites if you have problems with the default one included. (thanks @agnostic-apollo (Reddit) for the suggestion)

VERSION
v1.1

#task #GetPowerampPlaylistDataDB
DESCRIPTION
This task was created based on a request from a Reddit user.

It will allow you to retrieve data from the playlists table, located inside the Poweramp database.

Notes:
- Click here to go to the Reddit thread.
- As it needs to access '/data/data/com.maxmpz.audioplayer/*' files, root is needed.
- You can use the task for other table queries if you want too. Just modify the table and columns where the calls are made.

CREDITS
@SmartPhoneLover

VERSION
v1.0

#task #GetPowerampPlaylistDataDB
DESCRIPTION
This task was created based on a request from a Reddit user.

It will allow you to retrieve data from the playlists table, located inside the Poweramp database.

Notes:
Thanks to @Jandalf81 (Reddit) for helping on improving it.
- Click here to go to the Reddit thread.
- You can use the task for other table queries if you want too. Just modify the table and columns where the calls are made.

CREDITS
@SmartPhoneLover
@Jandalf81

CHANGELOG
- New: Database query without the need of root. (thanks @Jandalf81)

VERSION
v1.1

#warning #TaskerDev
[HOW-TO] Randomly set a beautiful Google Earth image as your wallpaper every X hours
Google just came out with a website that allows you to browse beautiful Google Earth images: https://earthview.withgoogle.com/

I instantly thought that it would be cool to use those in an automatic wallpaper changer in Tasker, so I created one! :)

This profile will get images from the website and update the wallpaper every 2 hours automatically.

Check out the demo here: https://youtu.be/ojhDAfs6hs4

Import it here: https://taskernet.com/shares/?user=AS35m8ne7oO4s%2BaDx%2FwlzjdFTfVMWstg1ay5AkpiNdrLoSXEZdFfw1IpXiyJCVLNW0yn&id=Profile%3ASet+Google+Earth+Wallpapers


If you want to see me creating this profile live, check my Patreon Live Creations post here: https://www.patreon.com/posts/33966942 (need to be $5 Patron or more to see).


Enjoy! :)

Source: Go!

#warning #TaskerDev
Tasker Removed From Google Play
Here I was enjoying a nice relaxing Saturday morning with my family when I got a notification from twitter alerting me to the fact that Tasker was not on Google Play.

Indeed, I checked my email and there this was:

Publishing status: Removed
Your app has been removed due to a policy violation. This app won’t be available to users until you submit a compliant update.

Issue: Violation of Permissions policy
After reviewing your app, we found that it doesn’t qualify to use the requested permissions for the following reason(s):

- Unable to verify core functionality of app
When you submitted your app, you specified your app's core functionality as follows: Device Automation. However, we couldn’t find evidence that the app offers the declared core functionality during our review. Please submit an updated Permissions Declaration Form that includes instructions on how to verify your declared functionality, and include details such as test account information. If portions of your app are restricted, please share a link to a video of your app to help us verify the core functionalities you’ve declared.

- Missing runtime permissions
Your app needs to use runtime permissions for us to complete the review. Please update your app to target API level 26 or above. If you have non-compliant APKs in different tracks of the app releases section of your Play Console, please deactivate (for Internal Test track) or create an empty release (a release without any APKs) before submitting your app again.
For additional guidance, please review the documentation on how to request app permissions.


Wow. Just wow...

So, arguably the most well known and oldest automation app out there is now no longer a Device Automation app.

Also, for some reason an app that targets API 28 and has implemented runtime permissions for nearly 2 years now, suddenly no longer does either.

As per Google Play Requirements When you upload an APK, it needs to meet Google Play’s target API level requirements. Both new apps and app updates must target at least Android 9 (API level 28) which means that it would've been impossible for me to have updated the app in the last few months, which obviously I have. A simple check of the last uploaded APK would check that.

n conclusion, I don't know what Google is on about. This makes absolutely no sense at all.

To make things worse I was in the process of building a new beta with new added functionality that I can't simply put out for everyone to use all of a sudden because nothing's been tested by users yet, so now, on a Saturday morning, I'm going to have to waste my time by trying to remove functionality from my app and hope that I don't break anything in the process so I can put it out for everyone to use...

I'm also losing any potential sales of the app until this is fixed.

Hope this gets resolved soon.

Source: Go!

#warning #TaskerDev
Tasker Removed From Google Play
EDIT: Seems like Tasker is now back! Crisis adverted. Still shouldn't have happened in the first place.

I have a theory on what triggered this, but it's just a theory and I can't really prove it.

Take a look at these fields in the app submission form on the Google Play Dashboard:

https://i.imgur.com/CZfELZj.png

I had never noticed these 3 fields before:
- Instructions for app review
- Video instructions
- Non-compliant APKs

My theory is that these fields are now mandatory for all Device Automation apps (possibly other types of apps that need the SMS/Call log permissions as well).

I had never filled them in so I'm guessing that what happened was this:
- update to the Google Play Dashboard website added new mandatory fields
- bot scanned for apps that didn't fill in all mandatory fields and removed those apps from Google Play

To make it perfectly clear, this removal was not triggered by a Tasker update. It just happened at some random time which makes my theory even more plausible.

Now I've put out an update that didn't update the APK but simply filled in those fields and Tasker is now back, so hopefully things can return to normal. I've lost half a day worth of purchases. Hope that doesn't bring Tasker down in the rankings on Google Play too much.

Source: Go!