X11 can run on ereader via ssh -X, but unable to use the touch-screen as the main display
0
I have successfully accessed X11 on a nook touch via ssh -X and started lxsession on a debian chroot. I tried being clever by making use of the omapflb driver. My intentions are to be able to use the current display.
I've looked into /dev directory and assumed that tty must be the display. After running these commands there is no desktop or mouse.
Even disabling android stack it still does not work.
# cat devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
29 fb
89 i2c
116 alsa
128 ptm
136 pts
180 usb
189 usb_device
252 usb_endpoint
253 DspBridge
254 rtc
I use the echo command to test the tty
# echo "test" >/dev/tty
test
tty is a pts in /dev/pts/#
I cat into the init file to show information about tty's.
# cat init.rc
on early-init
# Give the kernel time to enumerate the internal and external MMC/SD cards
# before init creates the devices in /dev
sleep 2
on init
setprop ro.boot.console tty0
export PATH /bin:/sbin:/usr/bin:/system/bin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export FRAMEBUFFER /dev/graphics/fb0
# Set up busybox's shell
export ENV /etc/profile
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mkdir /rom
mkdir /boot
mkdir /misc
on boot
ifup lo
hostname localhost
domainname localdomain
setprop persist.service.adb.enable 1
setprop wifi.interface tiwlan0
class_start default
# Enable automatic screen refreshing
write /sys/class/graphics/fb0/pgflip_refresh 1
write /sys/class/graphics/fb0/epd_refresh 0
# Give baseimage and bridged time to start
sleep 2
start omap-edpd
start system_ready
write /sys/devices/platform/usb_mass_storage/lun0/file /dev/block/mmcblk1p1
service system_ready /bin/sh /sbin/system_ready
disabled
oneshot
service network_failed /bin/sh /sbin/network_failed
disabled
oneshot
service network_ready /bin/sh /sbin/network_ready
disabled
oneshot
on property:dhcp.tiwlan0.result=ok
start network_ready
on property:dhcp.tiwlan0.result=failed
start network_failed
on property:wlan.driver.status=ok
sleep 1
start wpa_supplicant
sleep 2
start ifcfg_ti
sleep 2
start dhcpcd
service adbd /sbin/adbd
# load DSP firmware
service baseimage /sbin/cexec.out -T /etc/dsp/baseimage.dof
user root
group system
oneshot
service bridged /sbin/bridged
user root
group system
oneshot
service omap-edpd /sbin/omap-edpd.elf --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /etc/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/etc/dsp/default_waveform.bin
oneshot
disabled
service wlan_loader /sbin/tiwlan_loader
-f /etc/wifi/firmware.bin
-i /etc/wifi/tiwlan.ini
-e /rom/devconf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /sbin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /sbin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd /sbin/dhcpcd -ABKL -d tiwlan0
disabled
oneshot
service dropbear /usr/sbin/dropbear
disabled
oneshot
# start
x11 on nook touch instructions
linux x11 android
edited 2 days ago
Rui F Ribeiro
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
add a comment |
0
I have successfully accessed X11 on a nook touch via ssh -X and started lxsession on a debian chroot. I tried being clever by making use of the omapflb driver. My intentions are to be able to use the current display.
I've looked into /dev directory and assumed that tty must be the display. After running these commands there is no desktop or mouse.
Even disabling android stack it still does not work.
# cat devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
29 fb
89 i2c
116 alsa
128 ptm
136 pts
180 usb
189 usb_device
252 usb_endpoint
253 DspBridge
254 rtc
I use the echo command to test the tty
# echo "test" >/dev/tty
test
tty is a pts in /dev/pts/#
I cat into the init file to show information about tty's.
# cat init.rc
on early-init
# Give the kernel time to enumerate the internal and external MMC/SD cards
# before init creates the devices in /dev
sleep 2
on init
setprop ro.boot.console tty0
export PATH /bin:/sbin:/usr/bin:/system/bin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export FRAMEBUFFER /dev/graphics/fb0
# Set up busybox's shell
export ENV /etc/profile
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mkdir /rom
mkdir /boot
mkdir /misc
on boot
ifup lo
hostname localhost
domainname localdomain
setprop persist.service.adb.enable 1
setprop wifi.interface tiwlan0
class_start default
# Enable automatic screen refreshing
write /sys/class/graphics/fb0/pgflip_refresh 1
write /sys/class/graphics/fb0/epd_refresh 0
# Give baseimage and bridged time to start
sleep 2
start omap-edpd
start system_ready
write /sys/devices/platform/usb_mass_storage/lun0/file /dev/block/mmcblk1p1
service system_ready /bin/sh /sbin/system_ready
disabled
oneshot
service network_failed /bin/sh /sbin/network_failed
disabled
oneshot
service network_ready /bin/sh /sbin/network_ready
disabled
oneshot
on property:dhcp.tiwlan0.result=ok
start network_ready
on property:dhcp.tiwlan0.result=failed
start network_failed
on property:wlan.driver.status=ok
sleep 1
start wpa_supplicant
sleep 2
start ifcfg_ti
sleep 2
start dhcpcd
service adbd /sbin/adbd
# load DSP firmware
service baseimage /sbin/cexec.out -T /etc/dsp/baseimage.dof
user root
group system
oneshot
service bridged /sbin/bridged
user root
group system
oneshot
service omap-edpd /sbin/omap-edpd.elf --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /etc/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/etc/dsp/default_waveform.bin
oneshot
disabled
service wlan_loader /sbin/tiwlan_loader
-f /etc/wifi/firmware.bin
-i /etc/wifi/tiwlan.ini
-e /rom/devconf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /sbin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /sbin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd /sbin/dhcpcd -ABKL -d tiwlan0
disabled
oneshot
service dropbear /usr/sbin/dropbear
disabled
oneshot
# start
x11 on nook touch instructions
linux x11 android
edited 2 days ago
Rui F Ribeiro
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
No,ttyare "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as/dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking throughdmesgto see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, tryevtest.
– dirkt
Feb 22 at 14:49
add a comment |
0
0
0
I have successfully accessed X11 on a nook touch via ssh -X and started lxsession on a debian chroot. I tried being clever by making use of the omapflb driver. My intentions are to be able to use the current display.
I've looked into /dev directory and assumed that tty must be the display. After running these commands there is no desktop or mouse.
Even disabling android stack it still does not work.
# cat devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
29 fb
89 i2c
116 alsa
128 ptm
136 pts
180 usb
189 usb_device
252 usb_endpoint
253 DspBridge
254 rtc
I use the echo command to test the tty
# echo "test" >/dev/tty
test
tty is a pts in /dev/pts/#
I cat into the init file to show information about tty's.
# cat init.rc
on early-init
# Give the kernel time to enumerate the internal and external MMC/SD cards
# before init creates the devices in /dev
sleep 2
on init
setprop ro.boot.console tty0
export PATH /bin:/sbin:/usr/bin:/system/bin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export FRAMEBUFFER /dev/graphics/fb0
# Set up busybox's shell
export ENV /etc/profile
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mkdir /rom
mkdir /boot
mkdir /misc
on boot
ifup lo
hostname localhost
domainname localdomain
setprop persist.service.adb.enable 1
setprop wifi.interface tiwlan0
class_start default
# Enable automatic screen refreshing
write /sys/class/graphics/fb0/pgflip_refresh 1
write /sys/class/graphics/fb0/epd_refresh 0
# Give baseimage and bridged time to start
sleep 2
start omap-edpd
start system_ready
write /sys/devices/platform/usb_mass_storage/lun0/file /dev/block/mmcblk1p1
service system_ready /bin/sh /sbin/system_ready
disabled
oneshot
service network_failed /bin/sh /sbin/network_failed
disabled
oneshot
service network_ready /bin/sh /sbin/network_ready
disabled
oneshot
on property:dhcp.tiwlan0.result=ok
start network_ready
on property:dhcp.tiwlan0.result=failed
start network_failed
on property:wlan.driver.status=ok
sleep 1
start wpa_supplicant
sleep 2
start ifcfg_ti
sleep 2
start dhcpcd
service adbd /sbin/adbd
# load DSP firmware
service baseimage /sbin/cexec.out -T /etc/dsp/baseimage.dof
user root
group system
oneshot
service bridged /sbin/bridged
user root
group system
oneshot
service omap-edpd /sbin/omap-edpd.elf --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /etc/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/etc/dsp/default_waveform.bin
oneshot
disabled
service wlan_loader /sbin/tiwlan_loader
-f /etc/wifi/firmware.bin
-i /etc/wifi/tiwlan.ini
-e /rom/devconf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /sbin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /sbin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd /sbin/dhcpcd -ABKL -d tiwlan0
disabled
oneshot
service dropbear /usr/sbin/dropbear
disabled
oneshot
# start
x11 on nook touch instructions
linux x11 android
edited 2 days ago
Rui F Ribeiro
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
I have successfully accessed X11 on a nook touch via ssh -X and started lxsession on a debian chroot. I tried being clever by making use of the omapflb driver. My intentions are to be able to use the current display.
I've looked into /dev directory and assumed that tty must be the display. After running these commands there is no desktop or mouse.
Even disabling android stack it still does not work.
# cat devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
29 fb
89 i2c
116 alsa
128 ptm
136 pts
180 usb
189 usb_device
252 usb_endpoint
253 DspBridge
254 rtc
I use the echo command to test the tty
# echo "test" >/dev/tty
test
tty is a pts in /dev/pts/#
I cat into the init file to show information about tty's.
# cat init.rc
on early-init
# Give the kernel time to enumerate the internal and external MMC/SD cards
# before init creates the devices in /dev
sleep 2
on init
setprop ro.boot.console tty0
export PATH /bin:/sbin:/usr/bin:/system/bin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export FRAMEBUFFER /dev/graphics/fb0
# Set up busybox's shell
export ENV /etc/profile
mkdir /sdcard
mkdir /system
mkdir /data
mkdir /cache
mkdir /rom
mkdir /boot
mkdir /misc
on boot
ifup lo
hostname localhost
domainname localdomain
setprop persist.service.adb.enable 1
setprop wifi.interface tiwlan0
class_start default
# Enable automatic screen refreshing
write /sys/class/graphics/fb0/pgflip_refresh 1
write /sys/class/graphics/fb0/epd_refresh 0
# Give baseimage and bridged time to start
sleep 2
start omap-edpd
start system_ready
write /sys/devices/platform/usb_mass_storage/lun0/file /dev/block/mmcblk1p1
service system_ready /bin/sh /sbin/system_ready
disabled
oneshot
service network_failed /bin/sh /sbin/network_failed
disabled
oneshot
service network_ready /bin/sh /sbin/network_ready
disabled
oneshot
on property:dhcp.tiwlan0.result=ok
start network_ready
on property:dhcp.tiwlan0.result=failed
start network_failed
on property:wlan.driver.status=ok
sleep 1
start wpa_supplicant
sleep 2
start ifcfg_ti
sleep 2
start dhcpcd
service adbd /sbin/adbd
# load DSP firmware
service baseimage /sbin/cexec.out -T /etc/dsp/baseimage.dof
user root
group system
oneshot
service bridged /sbin/bridged
user root
group system
oneshot
service omap-edpd /sbin/omap-edpd.elf --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /etc/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/etc/dsp/default_waveform.bin
oneshot
disabled
service wlan_loader /sbin/tiwlan_loader
-f /etc/wifi/firmware.bin
-i /etc/wifi/tiwlan.ini
-e /rom/devconf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /sbin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /sbin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd /sbin/dhcpcd -ABKL -d tiwlan0
disabled
oneshot
service dropbear /usr/sbin/dropbear
disabled
oneshot
# start
x11 on nook touch instructions
linux x11 android
linux x11 android
edited 2 days ago
Rui F Ribeiro
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
edited 2 days ago
Rui F Ribeiro
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
edited 2 days ago
Rui F Ribeiro
41.4k1481140
edited 2 days ago
Rui F Ribeiro
41.4k1481140
edited 2 days ago
Rui F Ribeiro
41.4k1481140
41.4k1481140
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
asked Feb 21 at 16:16
Travis WellsTravis Wells
103
103
No,ttyare "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as/dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking throughdmesgto see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, tryevtest.
– dirkt
Feb 22 at 14:49
add a comment |
No,ttyare "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as/dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking throughdmesgto see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, tryevtest.
– dirkt
Feb 22 at 14:49
No,
tty are "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as /dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking through dmesg to see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, try evtest.– dirkt
Feb 22 at 14:49
No,
tty are "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as /dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking through dmesg to see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, try evtest.– dirkt
Feb 22 at 14:49
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502118%2fx11-can-run-on-ereader-via-ssh-x-but-unable-to-use-the-touch-screen-as-the-mai%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502118%2fx11-can-run-on-ereader-via-ssh-x-but-unable-to-use-the-touch-screen-as-the-mai%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
No,
ttyare "teletype" (serial character) devices or pseudo-devices. Framebuffer devices often show up as/dev/fb*, but the Nook very likely does some proprietary stuff, where it's likely the display isn't easily accessible. You might have more luck looking throughdmesgto see if you can find anything that looks like display hardware. The touchscreen may be available as standard input, tryevtest.– dirkt
Feb 22 at 14:49