Skip to main content
replaced http://android.stackexchange.com/ with https://android.stackexchange.com/
Source Link

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching the browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core with just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similarsimilar questionsquestions but I feel they deal more with a classical kiosk mode than with the separation of the console vs GUI mode.

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching the browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core with just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode than with the separation of the console vs GUI mode.

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching the browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core with just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode than with the separation of the console vs GUI mode.

Tweeted twitter.com/StackAndroid/status/684728953416904704
edited body
Source Link
WoJ
  • 591
  • 1
  • 10
  • 27

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching tghethe browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core wtihwith just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode tanthan with the separation of the console vs GUI mode.

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching tghe browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core wtih just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode tan with the separation of the console vs GUI mode.

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching the browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core with just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode than with the separation of the console vs GUI mode.

added 497 characters in body; edited title
Source Link
WoJ
  • 591
  • 1
  • 10
  • 27

Is it possible How to startboot the GUI so that one single GUI application upon bootis launched as part of it?

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching tghe browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is reasonably doablereplicable on Android? I would like to get rid of everything which is GUI soensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible in Android to separate theboot Android into a "headless" part of the OS from(console) mode, and then start the "GUI" partGUI core wtih just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode tan with the separation of the console vs GUI mode.

Is it possible to start one single GUI application upon boot?

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser).

Is this a scenario which is reasonably doable on Android? I would like to get rid of everything which is GUI so that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible in Android to separate the "headless" part of the OS from the "GUI" part?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

How to boot the GUI so that one single application is launched as part of it?

I would like to reuse an older Android phone as a digital controller for some applications. It would basically be a browser (or webkit) running full screen (which would display some buttons via javascript which in turn would interact with a backend API).

I have a similar (non-touch, display only) solution on Linux where I start at the end of the boot process xinit /path/to/xinit/config, where /path/to/xinit/config opens the browser full screen. Before xinit there is no concept of GUI, xinit starts the graphics core and then runs one single application (the browser). /path/to/xinit/config, before launching tghe browser at the end, does some logistical (non-GUI) tasks.

Is this a scenario which is replicable on Android? I would like to ensure that the only graphical element running is the browser (including the notification area, launcher, ...).

In other words: is it possible to boot Android into a "headless" (console) mode, and then start the GUI core wtih just one application?

Note: this is different from a classical "kiosk mode" where one tries to lock out users from accessing other elements of the GUI via an app. I do not have any security/usability considerations as this simple display will run in a safe environment.

EDIT: as pointed out by @Firelord, there were other similar questions but I feel they deal more with a classical kiosk mode tan with the separation of the console vs GUI mode.

added 127 characters in body
Source Link
WoJ
  • 591
  • 1
  • 10
  • 27
Loading
Source Link
WoJ
  • 591
  • 1
  • 10
  • 27
Loading