Panel |
---|
panelIconId | atlassian-info |
---|
panelIcon | :info: |
---|
bgColor | #E3FCEF |
---|
|
Please read the Terms of Use for Materials on ZennoLab |
Description
In addition to user variables, there are also environment variables. They contain various emulator parameters (resolution, geodata, SIM card data, data generated device, etc.), variables and dates, project variables (name, folder, proxy rules, the last error ID, etc.), numerous profile variables (mail, gender, name, etc.).
Below you can read the list of available variables and a description of what is stored in each of them.
...
Note
In Zennodroid, there are some environment variables that were inherited from Zennoposter and later will be deleted from the program. Such variables are
...
written strikethrough text.
The description of these variables is missing here. You can find it in a similar article for ZP - Environment variables in ZennoPoster
...
There are also unique variables for Zennodroid. But in versions 2.2.4 and 2.2.5 they are either an empty string or -1
. In future versions, these variables will contain values. You can manually assign it to them using the Profile processing action. These variables are labeled with a yellow background.
...
...
The background is unique to ZennoDroid variables, which do not yet contain values.
...
This background is used for variables that will be deleted from the program in the future.
Variables Page
Expand |
---|
title | Click here to expand |
---|
|
In the version of Zennodroid 2.2.4 and 2.2.5, the variables of the group may be available ({-Page.Url-} , {-Page.Dom-} , {-Page.LastAlertTitle-} ), but all of them are empty. In future releases of the program, they will be deleted. |
Profile
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-Profile.AcceptCharset-}
| - | {-Profile.AcceptLanguage-}
| - | {-Profile.AcceptEncoding-}
| - | {-Profile.Age-} | Age | {-Profile.AndroidID-} | ID Android device | {-Profile.AvailScreenHeight-}
| - | {-Profile.AvailScreenWidth-}
| - | {-Profile.BornDay-} | Birthday | {-Profile.BornYear-} | Year of birth | {-Profile.BornMonth-} | Month of birth | {-Profile.Country-} | Country profile | {-Profile.CpuCount-} | The number of the processor cores allocated to the emulator. | {-Profile.DisplayDensity-} | Density (DPI) of the emulator screen | {-Profile.DisplayHeight-} | Emulator screen height | {-Profile.DisplayWidth-} | Screen width emulator | {-Profile.Email-} | E-mail address profile | {-Profile.EmailPassword-} | Password of Profile’s E-mail | {-Profile.GeoLatitude-} | Emulator latitude (geodata) | {-Profile.GeoLongitude-} | Longitude of the emulator (geodata) | {-Profile.HTTPAccept-}
| - | {-Profile.IMEI-} | IMEI (Wikipedia) | {-Profile.IMSI-} | IMSI (Wikipedia) | {-Profile.Language-} | Profile language (value depends on the chosen nationality) | {-Profile.Login-} | Login profile | {-Profile.Name-} | Profile name | {-Profile.NickName-} | Nickname profile | {-Profile.None-} | Outdated variable | {-Profile.OperatorCode-} | Operator code | {-Profile.OperatorCountry-} | Country of operator | {-Profile.OperatorName-} | Name of operator | {-Profile.OuterHeight-}
| - | {-Profile.OuterWidth-}
| - | {-Profile.OuterHeightShift-}
| - | {-Profile.OuterWidthShift-}
| - | {-Profile.Password-} | Password profile | {-Profile.PhoneBoard-} | ro.product.board (Details can be read in the description of Action with VM, Device model section) | {-Profile.PhoneBrand-} | ro.product.brand (Details can be read in the description of Action with VM, Device model section) | {-Profile.PhoneHardware-} | ro.hardware (Details can be read in the description of Action with VM, Device model section) | {-Profile.PhoneManufacturer-} | Device manufacturer | {-Profile.PhoneModel-} | Device model | {-Profile.PhoneNumber-} | Phone number | {-Profile.RAM-} | Number of RAM allocated to the emulator | {-Profile.Region-} | Region profile | {-Profile.ScreenSizeHeight-}
| - | {-Profile.ScreenSizeWidth-}
| - | {-Profile.ScreenLeft-}
| - | {-Profile.ScreenTop-}
| - | {-Profile.SecretQuestionAnswer1-} | Answer to the secret question #1 | {-Profile.SecretQuestionAnswer2-} | Answer to the secret question #2 | {-Profile.Sex-} | Gender profile | {-Profile.SimSerial-} | SIM Card Serial Number | {-Profile.Surname-} | Surname profile | {-Profile.Town-} | City profile | {-Profile.UserAgent-}
| - | {-Profile.UserAgentAppCodeName-}
| - | {-Profile.UserAgentAppName-}
| - | {-Profile.UserAgentAppVersion-}
| - | {-Profile.UserAgentBrowserLanguage-}
| - | {-Profile.UserAgentCpuClass-}
| - | {-Profile.UserAgentLanguage-}
| - | {-Profile.UserAgentOsCpu-}
| - | {-Profile.UserAgentPlatform-}
| - | {-Profile.UserAgentProduct-}
| - | {-Profile.UserAgentProductSub-}
| - | {-Profile.WiFiMAC-} | Generated MAC address emulator | {-Profile.WiFiName-} | Generated WiFi Name | {-Profile.ZipCode-} | Profile index |
|
Time and date
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-TimeNow.Date-} | Current Date and Time in Format dd/MM/yyyy HH:mm:ss (example - 01/25/2020 14:41:18 ). You can change the format of the displayed string! To do this, you need to add a format template before the closing bracket. Example: {-TimeNow.Date dd.MM.yyyy HH.mm-} , after execution we get such a string - 25.01.2020 14.41 Read more about formatting can be found here and here. | {-TimeNow.Day-} | Day of month | {-TimeNow.Month-} | Current month (number) | {-TimeNow.Year-} | This year | {-TimeNow.DayOfWeek-} | Day of the week, in English. | {-TimeNow.Hour-} | Current hour (in 24 hour format) | {-TimeNow.Minute-} | Current minute | {-TimeNow.Second-} | Current second | {-TimeNow.Millisecond-} | Current millisecond | {-TimeNow.TimeNow-} | Current Date and Time in format YYYY-MM-DD HH-MM-SS--millisecondes (2020-01-25 14-41-59--834 ) Note |
---|
Does not support formatting! |
| {-TimeNow.UnixTime-} | Unix-time. Format - 1629891362.23929 |
|
Project variables
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-Project.BrowserProfileFolder-}
| Full path to profile folder (or empty string if the profile folder is not used).- | {-Project.Directory-} | Directory template | {-Project.PluginDirectory-} | Directory plugin (if the executed template - plugin) | {-Project.Name-} | Template name | {-Project.Proxy-} | Current proxy project. | {-Project.ProxyRules-} | Used rule from ProxyChecker | {-Project.LastExecutedActionElapsedTime-} | Time spent on the work of the last performed action | {-Project.LastExecutedActionId-} | ID of the last action | {-Project.LastErrorComment-} | The text of the last action ending with an error Note |
---|
If the action has no custom comment (Right-click on action => Comment), the empty string will be back. |
|
|
System Variables (Environment)
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-Environment.CurrentUser-} | Zennoposter user ID, from a personal account running with a template. | {-Environment.EmulatorDirectory-} | Full path to the directory, where Memu program is installed. | {-Environment.TickCount-} | The number of milliseconds that have passed since the computer is turned on. Note |
---|
This variable is based on Environment.tickCount from C#, therefore, one feature is inherent in it: If the computer will work for a long time and continuously, then after ~ 24.9 days this variable will reach the maximum positive value.- 2147483647 . After that, it jumps over to the minimum possible value - -2147483648 and starts counting to zero (reaches it through ~ 24.9 days). After reaching zero, an increase in the counter will begin to the maximum possible value (2147483647 ) and so in a circle. |
|
|
String
...
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-String.Enter-} | Transition to a new string | {-String.Space-} | Space | {-String.Tab-} | Tab symbol |
|
Other
Expand |
---|
title | Click here to expand |
---|
|
Name | Description |
---|
{-//-}
| The path to the directory where Zennodroid is installed. Example for Russian version 2.2.5 - C:\Program Files\ZennoLab\RU\ZennoDroid Pro\2.2.5.0\Progs\ |
|