MD and it's users need to prepare...

MacroDroidDev

Administrator
Staff member
The BOOT_COMPLETE does sound like a big problem. It seems they are blanket banning apps running on startup without any user permission or tweaks. I really hope they provide a way to allow it for user chosen apps.
 

MacroDroidDev

Administrator
Staff member
The BOOT_COMPLETE does sound like a big problem. It seems they are blanket banning apps running on startup without any user permission or tweaks. I really hope they provide a way to allow it for user chosen apps.
Actually now I have read more carefully I *think* that only applies if the user places the app in the background battery restricted state
 

paresh996

New member
As BOOT_COMPLETED fires after someone unlocks the phone, is there no way for Macrodroid to send out an email or perform other actions after a boot before the screen unlocks?
I tried triggering on android.intent.action.LOCKED_BOOT_COMPLETED but it seems it's not received.

Is Macrodroid setting android:directBootAware ?
 
Last edited:

Endercraft

Moderator (& bug finder :D)
I think no user apps (at least on my device) are allowed to start before the device is unlocked. On an older one this isn't the case however.
 

paresh996

New member
Just checked, Macrodroid's Androidmanifest.xml *does* mention directBootAware="true" for some services and providers. In fact, Tasker doesn't havei it. So services in Macrodroid know they have to do something before the phone is unlocked after a reboot.


If Direct Boot doesn't allow sending emails/SMS, I'd suggest Macrodroid to mention that and have another trigger for the LOCKED_BOOT_COMPLETED intent which could at least perform any actions that can be done in direct boot mode.

And then... this needs to change. I wish it wasn't BOOT_COMPLETED.

XML:
    <receiver
      android:name="com.arlosoft.macrodroid.StartupReceiver"
      android:exported="true">
      <intent-filter
        android:priority="2147483647">
        <action
          android:name="android.intent.action.BOOT_COMPLETED">
        </action>
      </intent-filter>
    </receiver>
 
Last edited:

MacroDroidDev

Administrator
Staff member
It is not feasible to support direct boot mode as it is a very limited sandbox and there is no way any MacroDroid functionality can work in this limited scope.
 

paresh996

New member
You know better. But don't you think, it's too restrictive? I even tested Google's Find My Device thing, it can't find my phone when it's switched on but locked (after a boot)! This means if your phone's lost and someone presses and holds the power button, you're gone, the phone's lost forever. Macrodroid process doesn't start (I've also tried starting Macrodroid services from init.rc scripts, doesn't work).

But I have logs that mention Macrodroid stuff before the user unlocks.
I was wondering (just...), is it possible to just pass on location information to a pre-set HTTP URL?
Direct Boot Mode still gives you the location and calling a URL wouldn't need storage in my opinion. The URL could be bound to the user account.
 
Top