Technical Plugin MobileManager

Technical: MobileManager plugin

Defines mobile-app settings and integration/callback pages.

Audience: developers, advanced administrators and AI-assisted diagnosis. Plugin catalog.

Source baseline

• Review date: 2026-10-29. Method: static source analysis; runtime/provider behavior was not exercised.
• Code ownership: AVideo Streamer repository.
• Reported version: 1.5.
• Source revision: 7d48f2dfc0289236718a3f9fba7c5ffecff4a37f.
• Entry class file: MobileManager.php.

Confirm the installed plugin version independently of the Streamer version. Configuration defaults below are not a dump of this installation's saved settings.

Dependencies

No literal dependency declaration was extracted. This does not prove the plugin is standalone.

Literal runtime plugin references: Chat2, CustomizeUser, LoginApple, YPTSocket. These calls do not mean every referenced plugin is mandatory.

Hook integration

Override	Implementation
getTags()	MobileManager.php:7

Configuration assignments

These are direct assignments inside getEmptyDataObject(), not evaluated effective defaults. Stored plugins.object_data, globals, structured values and conditional branches may alter runtime behavior. Private/default credential values are omitted.

Field	Literal default or expression type	Literal source label/help	Evidence
doNotAllowAnonimusAccess	false	—	source
doNotAllowUpload	false	—	source
hideCreateAccount	false	—	source
hideTabTrending	false	—	source
hideTabLive	false	—	source
hideTabSubscription	false	—	source
hideTabChat2	false	—	source
hideTabPlayLists	false	—	source
hideViewsCounter	false	—	source
hideLikes	false	—	source
EULA	Computed/structured; inspect source	—	source
themeDark	false	—	source
portraitImage	false	—	source
netflixStyle	false	—	source
netflixDateAdded	true	—	source
netflixMostPopular	true	—	source
netflixMostWatched	true	—	source
netflixCategories	true	—	source
netflixBigVideo	true	—	source
disableWhitelabel	false	—	source
disableComments	false	—	source
approvalMode	false	—	source
showMeet	true	—	source
goLiveWithMeet	true	—	source
doNotAutoSearch	false	—	source
playStoreApp	Computed/structured; inspect source	—	source
appleStoreApp	Computed/structured; inspect source	—	source
pwa_background_color	Computed/structured; inspect source	—	source
pwa_display	Computed/structured; inspect source	—	source
pwa_scope	"/"	—	source

Files and request surface

This inventory distinguishes implementation files from an API specification. Includes, templates, callbacks and CLI workers are not interchangeable HTTP endpoints. Request-field names below are direct source references, not a complete schema or permission declaration.

File	Source role	Direct request fields observed
MobileManager.php	plugin entry class	—
getConfiguration.json.php	JSON entry point; inspect caller and guard	sort
getRandomVideo.php	PHP page/include/worker; inspect caller	—
index.php	PHP page/include/worker; inspect caller	key, live_index, live_servers_id, logoff
loginPage.php	PHP page/include/worker; inspect caller	SignUp, logoff
oauth2.php	PHP page/include/worker; inspect caller	type
oauth2Error.php	PHP page/include/worker; inspect caller	—
oauth2Success.php	PHP page/include/worker; inspect caller	—
upload.php	PHP page/include/worker; inspect caller	base64PNG, can_share, categories_id, description, pass, title, upl, user, video_password
userButtons.php	PHP page/include/worker; inspect caller	—

Data and migrations

No CREATE TABLE names were extracted from available plugin SQL. The plugin can still use core tables, PHP-created schema or another component's data. Apply installation/update behavior through the owning plugin; this reference is not a script for running historical migrations manually.

Main-file named symbols

Visibility and implementation semantics must be checked in source. Nonempty string defaults are represented as . This is a symbol reference, not a stable public API promise.

Function or method	Source
getTags()	7
getVersion()	14
getDescription()	19
getName()	26
getUUID()	31
getPluginVersion()	36
getEmptyDataObject()	41

Diagnostics and validation

1. Check the installed/enabled version and the dependencies/settings above.
2. Identify the actual failing page, request, callback or worker and correlate its timestamp with the AVideo log.
3. Follow the linked method and caller. Check business-state changes and output artifacts as well as HTTP status.
4. Reproduce the relevant workflow in a test environment. External provider, Encoder, live-server, storage, payment and authenticated flows require their real integrations.

Shared diagnostic workflow. This page is not a security audit or a claim of end-to-end validation.