lewinator56

[lewinator56]

Not replied on this in a while, ill try the latest version, seeing as only the issue now is the white screen, i cant see how its a shared memory issue in the android kernel, unless its something to do with GPU memory.

 

[lewinator56]

The only problem now is  I login to a white screen, I’ve tried the fix changing /usr/NX/etc/node.cfg, and it hasn’t worked,
The desktop manager appears to be lightdm

[lewinator56]

yep, thanks! that worked!

[lewinator56]

I’ll give it a go and report back,

sorry for the late reply, the notification went into spam

[lewinator56]

so, i checked nxerror.log and its effectively the same as nxserver.log:

 

20292 20292 10:56:21 870.199 Socket: WARNING! Can’t create the IPv4 socket.

20292 20292 10:56:21 878.682 Socket: WARNING! Error is 13 ‘Permission denied’.

20292 20292 10:56:21 878.737 Socket: WARNING! Can’t create the IPv6 socket.

20292 20292 10:56:21 878.745 Socket: WARNING! Error is 13 ‘Permission denied’.

20292 20292 10:56:21 878.767 Socket: WARNING! Can’t create any local socket.

20292 20292 10:56:21 932.012 OpenSocketToListen: WARNING! Socket creation failed with error 13, ‘Permission denied’.

mesg: ttyname failed: Inappropriate ioctl for device

 

so, the chroot has access to the network as standard vnc and ssh work fine, as do normal network connections, its running on android 9 on a snapdragon 845 (ARM64).

the environmet was set up using linux deploy (i know you obviously wont provide any support for that, iv’e already contacted the dev and its just a standard chroot environment so should have no differences).

its set up as a separate linux image on the drive, rather than as a directory.

 

i may well need to mount certain partitions to access the network hardware, but im suprised if this is the case as, like i’ve said, vnc and ssh work fine.

[Author]

Posts