Sad news with Android 14 and MacroDroid

Endercraft

Endercraft

Moderator
That said, if for whatever reason you want or need to install an outdated application, it will still be possible through a command shell, by using a new flag. Given the extra steps required, it’s less likely that someone would do this by mistake and inadvertently install malware
Click to expand...
At least it will still be possible then ?
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
It can be installed via the adb tool, so most users here will be fine and have the ability to install/update it etc.

Of course most other users will be very confused, annoyed and angry so it will just drive away new users who don't understand or think it looks super dodgy what they are being asked to do. Of course Google has made this change to "improve security", so if an app is trying to do this then it must be up to no good!

I hope there will be major backlash and they will at least put some option deep in the settings to allow installation of older APKs.
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
Yep, it looks like the time has finally come. Unfortunately I have not been able to install via the ADB tool either as this seems to be blocked as well (I had previously heard that this should work).

I will need to spend some time soon looking if there is any way around this awful new restriction and if not will have to build a "Special" new version of the helper that targets SDK 23 (and loses some of the functionality currently allows). I do so enjoy spending days of effort to make the app worse and create new support requests/1 star reviews when things that used to work no longer do!
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
It is possible to install via ADB with the following command:

adb install --bypass-low-target-sdk-block FILENAME.apk

I think for now I'm going to mandate Android 14 helper file installs via this mechanism as from what I've read the target SDK restrictions will keep ramping up over time so the helper file will eventually become useless in this case if I keep increasing the target SDK version.

Once Android 14 is out properly I will put some effort into making all this as clear and easy as possible for less knowledgeable users.
 
B

badhabit_wb

New member
MacroDroidDev said:
It is possible to install via ADB with the following command:

adb install --bypass-low-target-sdk-block FILENAME.apk

I think for now I'm going to mandate Android 14 helper file installs via this mechanism as from what I've read the target SDK restrictions will keep ramping up over time so the helper file will eventually become useless in this case if I keep increasing the target SDK version.

Once Android 14 is out properly I will put some effort into making all this as clear and easy as possible for less knowledgeable users.
Click to expand...
That worked great for me. Thank you!
 
D

D_H

New member
I am quite worried about that some functions will not work anymore as soon as I update my Google Pixel to Android 14. Is there any overview which triggers and actions will still work with Android 14 and what will not work anymore?
According some announcements Android 14 will only allow calendar apps and alarm clock apps to schedule exact alarms. Will Macrodroid sill be able to schedule exact alarms with Android 14?
For example I use the regular interval trigger with the alarm option as a trigger. Will this work with Android 14 like before with Android 13? What will be the limitatations with Android 14?
 
S

sampleuserhere

Active member
developer.android.com

Schedule exact alarms are denied by default | Android Developers

developer.android.com developer.android.com

SCHEDULE_EXACT_ALARM, the permission introduced in Android 12 for apps to schedule exact alarms, is no longer being pre-granted to most newly installed apps targeting Android 13 and higher (will be set to denied by default).
Click to expand...

If you meant this behaviour change, then as long as MD declares the said permission, the user just has to grant the permission manually in A14.
 
J

JStefanski

New member
A noob here. I'm trying to use this adb command to install mdhelper with ashell app connected to shizuku. With Ashell I've managed to use the adb commands from macrodroid to allow the use of NFC actions ecc. I've tried this adb command adding the file path:

adb install --bypass-low-target-sdk-block /storage/emulated/0/Documents/MacroDroidHelper_v1_13.apk

And I get this error:

sh: adb: inaccessible or not found

Am I doing something wrong? I can't figure this out. I'm using a pixel 7.
MacroDroidDev said:
It is possible to install via ADB with the following command:

adb install --bypass-low-target-sdk-block FILENAME.apk

I think for now I'm going to mandate Android 14 helper file installs via this mechanism as from what I've read the target SDK restrictions will keep ramping up over time so the helper file will eventually become useless in this case if I keep increasing the target SDK version.

Once Android 14 is out properly I will put some effort into making all this as clear and easy as possible for less knowledgeable users.
Click to expand...
 
D

Dimlos

Well-known member
It appears that aShell cannot be used because it does not support the required installation options.
Currently, the only way to do PC-less installation may be to use Termux.
 

Attachments

  • aShell.jpg
    aShell.jpg
    262.4 KB · Views: 18
  • Termux.jpg
    Termux.jpg
    244.3 KB · Views: 20
J

JStefanski

New member
The First command is adb connect to IP address right? I've tried that at least and I failed. Also I didn't mentioned that my device is not rooted. Does it work without root
Dimlos said:
It appears that aShell cannot be used because it does not support the required installation options.
Currently, the only way to do PC-less installation may be to use Termux.
Click to expand...
 

Attachments

  • Screenshot_20231011-095645.png
    Screenshot_20231011-095645.png
    147.5 KB · Views: 18
D

Dimlos

Well-known member
First of all, I would like to confirm that you have installed Termux from F-Droid?
If you have installed it from the Play Store, please reinstall it from F-Droid.
From the screenshot I can confirm that Termux is not ready to use adb.
Please run pkg install android-tools command first.
 
D

Dimlos

Well-known member
After installing adb, you will need to enter the pair code using the split screen.
adb pair 192.168.x.xxx:XXXXX

Then connect via wireless debugging.
adb connect 192.168.x.xxx:XXXXX

You may find the information in the following thread on setting up Termux helpful.

Wifi ADB debug mode lost on restart?

oh that was it , sorry, i just search only the digits .-) thanks so much @MacroDroidDev I wish we could search just the numbers
www.macrodroidforum.com www.macrodroidforum.com
 
You must log in or register to reply here.
Top