Notices


Reply
Thread Tools
Posts: 17 | Thanked: 13 times | Joined on Feb 2017
#71
Originally Posted by r0kk3rz View Post
You can upgrade, OTA or image, everything seems to be fine with it.

I haven't pushed the anbox kernel yet, i thought id test the update first just to minimise potential breakage
Latest image works okay for me, can you upload anbox-enabled kernel version?

Thanks
 

The Following User Says Thank You to GCR For This Useful Post:
Posts: 350 | Thanked: 1,806 times | Joined on Jul 2014
#72
Originally Posted by GCR View Post
Latest image works okay for me, can you upload anbox-enabled kernel version?

Thanks
Ok i've uploaded the new HAL with anbox patches, if you want to OTA to it you will have to run the kernel flashing script manually because I don't have things quite set up right.

/var/lib/platform-updates/flash-bootimg.sh

I've also kicked off a new image build on the gitlab-ci if you prefer to do it that way

https://gitlab.com/sailfishos-porter...indy_ci/-/jobs
__________________
SirenSong v0.5
Like my work? buy me a beer
 

The Following 2 Users Say Thank You to r0kk3rz For This Useful Post:
Posts: 17 | Thanked: 13 times | Joined on Feb 2017
#73
Originally Posted by r0kk3rz View Post
Ok i've uploaded the new HAL with anbox patches, if you want to OTA to it you will have to run the kernel flashing script manually because I don't have things quite set up right.

/var/lib/platform-updates/flash-bootimg.sh

I've also kicked off a new image build on the gitlab-ci if you prefer to do it that way

https://gitlab.com/sailfishos-porter...indy_ci/-/jobs
If I want to upgrade via OTA: zypper ref, zypper dup and then sh flash-bootimg.sh?Am I right?

Thanks for your reply.
 

The Following User Says Thank You to GCR For This Useful Post:
Posts: 17 | Thanked: 13 times | Joined on Feb 2017
#74
Hello again,

I did an OTA update (zypper ref, zypper dup) and then command in sh, but anbox still doesn't work - the same case as earlier.
In journalctl I've got "Failed to connect to socket /run/anbox-container.socket: No such file or directory
Couldn't get a connection with the session manager.

Please help
 

The Following User Says Thank You to GCR For This Useful Post:
Posts: 350 | Thanked: 1,806 times | Joined on Jul 2014
#75
Originally Posted by GCR View Post
Hello again,

I did an OTA update (zypper ref, zypper dup) and then command in sh, but anbox still doesn't work - the same case as earlier.
In journalctl I've got "Failed to connect to socket /run/anbox-container.socket: No such file or directory
Couldn't get a connection with the session manager.

Please help
I did say that it doesn't work very well

From memory you need to remove the networking stuff from one of the service scripts, then start the service, and then maybe after restarting the service 4-5 times and trying the anbox launcher you might get it to work briefly.
__________________
SirenSong v0.5
Like my work? buy me a beer
 

The Following 2 Users Say Thank You to r0kk3rz For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 17:04.