-
Notifications
You must be signed in to change notification settings - Fork 95
renyuneyun edited this page Nov 29, 2017
·
13 revisions
Some functionalities doesn't have official APIs so Easer uses some workarounds (reflection) to achieve that. However, they are unreliable and may not work on some devices; enabling root features will usually benefit these functions. Here is a list of these functionalities:
Functionality | Class | Non-root compatibility | Root-feature compatible? |
---|---|---|---|
Turn mobile data (cellular data) on/off | CellularOperationPlugin |
Maybe | Yes |
Turn hotspot (wireless AP) on/off | HotspotOperationPlugin |
Maybe | Not yet |
Execute commands | CommandOperationPlugin |
Probably not (it's said executing commands requires root permission, or it would faild) | Yes |
It is very welcomed to report compatibility situation on different devices and/or ROMs.
Currently, the UI of Easer is not pretty and needs a lot of improvements; some behaviors may not exactly follow your mind. They are listed here.
- Easer will use relevant system permissions to check events and change settings. Although there is runtime permission check, please do not REVOKE the permissions granted to Easer (or the relevant functions won't run correctly).
- Time (
TimeEventPlugin
) uses Android's system level notification mechanism (AlarmManager
), which is inexact (from Android 4.4) to minimize wakeups and battery use as said in the official document. My observation of the maximum shift is 3 minutes. - Similarly, Date (
DateEventPlugin
) also usesAlarmManager
so it may also be inexact (though this behavior is relatively less harmful because 3 minutes is only a small portion compared to a day). -
Before
andAfter
(EventType
) are inclusive (not sure if it will be useful to have them exclusive). - Most events won't be re-triggered if it is already satisfied and hasn't become unsatisfied yet. That said, you won't need to worry about creating an "after 3:00pm" event and it repeats triggering all the time. The small amount of re-triggerable events are designed to be so because of their natural property, so users won't need to worry about that -- just follow what you feel to use them.
See here for the full explaination.