[Samsung Galaxy S9/S9+] Porting Thread

[Georgian Chituc]

UPDATE:

Samsung S9+ is officially supported by Maru Os ,you can use the official builds , just flash new vendor zip from https://androidfilehost.com/?fid=11410932744536982158 using TWRP , before flashing MaruOS for S9+

Old post :

Thanks to Google 's Project Treble ,which separates vendor files from Android framework the port of AOSP Android to devices that comes with Android 8.0 and newer is easier .

This will allow Maru OS to be also easly ported to newer devices like galaxy S9 .

Work that must to be done :

-Recompile Kernel with support for LXC
-Integrate MaruOs mods Into Android 8.1 AOSP and build Project Treble system image for S9

Here is the Maru Os for S9+ (star2lte)

The desktop  user is maru password maru

Sound is enabled by default using taik native pulseaudio server .

Mouse/keyboard are avaible to androd if desktop is not started .

Desktop linux image is Ubuntu 16.04 arch64 .

Here is the zip you have to flash via TWRP .

https://androidfilehost.com/?fid=11410963190603842634

Also for all lineage os based roms ,for S9+ , you need your vendor files to be BRE5 or camera will not work.

https://androidfilehost.com/?fid=674106145207489374

[Tyler Martin]

Doesn't this mean we could technically have one system image that would work for most Treble compatible devices?

[Georgian Chituc]

Yes , this is the dream , flash one system image for all devices , but we will still need to provide a  boot.img for every device , cause the kernel is different from device to device .

But lol Project Treble is great for MaruOS porting !

[Tyler Martin]

That would be amazing!

[Georgian Chituc]

Ok , just got a S9+ and managed to install los 15.1 on it.
Since lineage os is already supported by maru os we will use lineage os 15.1 to try to run Maru on S9 devices.
There is no generic project treble image that runs good on all new devices , but lineage os as base is very good .

I will try today to see if the patches for 14.1 works on 15.1 .
We may need or may not need the Dex Pad , I read that if we use a patched kernel we can have external display working without dex .
We ll see how it works

[Georgian Chituc]

Like usual, cool things dnt come easy .
There are good news and bad ones, and always the hope.

The Good news is that lineage os supports all phone hardware features , including fingerprint unlock .
I installed and used it and is really nice.
The bad news is that my Ms HD 500 dock did not worked , but I ordered a dex pad .
I hope the dex pad will work with lineage os, it have to work .
Samsung prevent non dex doks to work using some vendor Ids inside kernel .
I used a modified patch from s8 to enable non dex hardware but I have only USB ports working , no image on external display .
Any way , no problem I wait for the dex pad to come , and if lineage do not works with dex I will investigate why ,based from original rom logs .It have to work after all. Any way the hardware looks powerfull and I m very curious how linux app works . The device is good to do Android O Maru testing .
I ll keep you updated .

[PHoSawyer]

Good work Georgian,

I'm starting to look at a OnePlus 5T port, have you got a manifest you used for 15.1? Would save me some time if I had something to go off.

I've got 15.1 installed but the only thing that doesn't seem to work is the NFC.

[Preetam]

Nice work Georgian, keep us posted!

[Georgian Chituc]

All looks good til now .
My dex pad arrived today and it works with lineage is 15.1 ! Yes we have image over dex dock using Lineage is! This is very cool !

The next step is to rebuild kernel with lxc support , and to try the maru patches on los 15.1 . I hope will not be big problems patching los 15.1 .

We re near to have maruos running on the best hardware !
I will try today the patches !

[Georgian Chituc]

OK , I inspected the source of los 15.1 and did a dry-run of the 3 patches.

The framework native and base looks easy to adapt , and the patches looks to work 100% after some easy modifications , so this is great.

The Settings app patch looks to need some work .
It looks like Settings app from Oreo was changed a lot . And from my first look the patch we have will not work ,here I think we will need Preetam s help.
Any way I m sure all will work after all.
This are great news!

[Georgian Chituc]

Ok , i managed to start ubuntu using lxc-start , and to have mouse and keyboard working .

ALso the phone screen can be used like a touch pad .

There are 2 problems that I have to solve next :

-patch settings app .

-lxc container starts just one time , and after container shot down it refuse to start again until phone restart .

I tested the Ubuntu 16.04 armhf inside container , the speed is magnific .

For me Lg g4 was a a working one , HTC 10 a perfect  desktop , but missed the speed of S9 .

Now I hope will'll have all we miss .

I know about linux on galaxy project , but it looks to take for ever to finish , till it will be done , we have a very good desktop on S9 .

Also the LOS 15.1 patches can be used for other phone too .

All is goooood till now :)

[PHoSawyer]

Excellent work Georgian!

I'm very much interested in the patches you used to try and get LOS15.1 working on OnePlus 5T.

[Georgian Chituc]

I will make a diff soon , to extract the patches for framework base and native .

I choose S9 cause it supported wired HDMI , I think 5T will work with display link app but I m not sure

[PHoSawyer]

Yes the 5T should work with DisplayLink.

Was going to start properly this week but if you have already done some work on the LOS15.1 patch then I might as well look at yours and modify.

Let me know when the diff is up so I can have a look!

[Georgian Chituc]

Ok ,  all lxc container startup and restart problems are fixed now .

:) and It wooorks good -> like in HTC 10 :D

Nice and nice , reboot halt from container works without problems , and container do not have steartup problems .

We can keep this version of lxc ,I think is fine . I tested it a lot on HTC 10 and n problems . The problem come from eax kernel cgroup .

But once you instruct lxc to dnt use it all is fine :D

So we'll have a great new device to play Maru on it :D

What I have to do now is to patch settins app , so we can start desktop on demand .

Now it starts just when hdmi attached .

[Georgian Chituc]

MaruOs , the distro that allow you to use a real Linux distro , mouse , keyboard and monitor attached to your phone , so you to work on a phone like on a real desktop  ported to S9+  before "Linux on Galaxy" realeased :))))))))))))))))))))))))

[Georgian Chituc]

[PHoSawyer]

Nice dude! Well Done!!

Now get that pull request in!

On Tuesday, 19 June 2018 08:22:52 UTC+1, Georgian Chituc wrote:

[Georgian Chituc]

https://www.youtube.com/watch?v=iF7yK7HAyVM

min: 2:11 - "I can imagine that the desktop experience would work a lot better and a lot smoother on newer hardware "  

He was right ! :)  S9+ rock MaruOS :)

[Preetam]

WOW! Incredible work as always Georgian. It is truly amazing to see Maru working on the S9 before "Linux on Galaxy". Thank you so much for your work to push Maru forward.

As PHoSawyer said though, send me that damn pull request with your code so we can prepare to ship this to everyone as an official release!

I guess on my end I will have to push up a manifest for Lineage 15.1. I can help patch Settings so we can start the desktop on demand.

[Georgian Chituc]

Thank you .  Yes I will do it today , will make the framework patches  asap .

If you could help with the settings app patch will be great .

I see there are build of LOS 15.1 for Nexus 5 if you need to test LOS 15.1 settings app  inside Nexus .

https://forum.xda-developers.com/google-nexus-5/development/rom-lineageos-15-1-nexus-5-t3756643

[Georgian Chituc]

So for now I have the framework base , native and some selinux patches so vendor_maruos can compile inside LOS 15.1 . I also have rootfs.tar.gz of Ubuntu 16.04 to upload .
We need a new/patch Settings app . That I do not have yet . I m still testing the buils for few days already as my only and primary rom . No problems here all device features works , including fingerprint unlock .
After the manifest for LOS 15.1 will be up , I can help with building the official images for S9+ , I do not have a s9 just the plus one , but they share same kernel and if s9+ works s9 must too , and maybe we get a user with a s9 to test the build

[Georgian Chituc]

I made a diff and I uploaded the required patches for LOS 15.1 o the "Maru Os for Android 8.1" thread .

[Georgian Chituc]

Here are the kernel config for star2lte used :

diff -uN orig exynos9810-star2lte_defconfig
--- orig    2018-06-23 23:28:38.482332180 +0300
+++ exynos9810-star2lte_defconfig    2018-06-18 23:29:15.964966912 +0300
@@ -47,7 +47,7 @@
 # CONFIG_LOCALVERSION_AUTO is not set
 CONFIG_DEFAULT_HOSTNAME="(none)"
 CONFIG_SWAP=y
-# CONFIG_SYSVIPC is not set
+CONFIG_SYSVIPC=y
 # CONFIG_POSIX_MQUEUE is not set
 CONFIG_CROSS_MEMORY_ATTACH=y
 # CONFIG_FHANDLE is not set
@@ -136,13 +136,13 @@
 # CONFIG_CGROUP_DEBUG is not set
 CONFIG_CGROUP_FREEZER=y
 # CONFIG_CGROUP_PIDS is not set
-# CONFIG_CGROUP_DEVICE is not set
+CONFIG_CGROUP_DEVICE=y
 CONFIG_CPUSETS=y
 CONFIG_PROC_PID_CPUSET=y
 CONFIG_CGROUP_CPUACCT=y
 CONFIG_CGROUP_SCHEDTUNE=y
-# CONFIG_MEMCG is not set
-# CONFIG_BLK_CGROUP is not set
+CONFIG_MEMCG=y
+CONFIG_BLK_CGROUP=y
 CONFIG_CGROUP_SCHED=y
 CONFIG_FAIR_GROUP_SCHED=y
 # CONFIG_CFS_BANDWIDTH is not set
@@ -152,9 +152,10 @@
 CONFIG_SOCK_CGROUP_DATA=y
 # CONFIG_CHECKPOINT_RESTORE is not set
 CONFIG_NAMESPACES=y
-# CONFIG_UTS_NS is not set
-# CONFIG_USER_NS is not set
-# CONFIG_PID_NS is not set
+CONFIG_UTS_NS=y
+CONFIG_IPC_NS=y
+#CONFIG_USER_NS is not set
+CONFIG_PID_NS=y
 CONFIG_NET_NS=y
 CONFIG_SCHED_AUTOGROUP=y
 CONFIG_SCHED_TUNE=y
@@ -162,7 +163,7 @@
 CONFIG_DEFAULT_USE_ENERGY_AWARE=y
 CONFIG_SCHED_USE_FLUID_RT=y
 # CONFIG_SYSFS_DEPRECATED is not set
-# CONFIG_RELAY is not set
+CONFIG_RELAY=y
 CONFIG_BLK_DEV_INITRD=y
 CONFIG_INITRAMFS_SOURCE=""
 CONFIG_RD_GZIP=y
@@ -1132,7 +1133,7 @@
 #
 CONFIG_UEVENT_HELPER=y
 CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-# CONFIG_DEVTMPFS is not set
+CONFIG_DEVTMPFS=y
 CONFIG_STANDALONE=y
 CONFIG_PREVENT_FIRMWARE_BUILD=y
 CONFIG_FW_LOADER=y
@@ -5003,7 +5004,7 @@
 # CONFIG_QFMT_V1 is not set
 CONFIG_QFMT_V2=y
 CONFIG_QUOTACTL=y
-# CONFIG_AUTOFS4_FS is not set
+CONFIG_AUTOFS4_FS=y
 CONFIG_FUSE_FS=y
 # CONFIG_CUSE is not set
 # CONFIG_OVERLAY_FS is not set

[Georgian Chituc]

Just to keep track of it , here is the star-common diff it include changes needed by S9 and S9+ , and no required changes to star2lte dir .

diff -ruN android_device_samsung_star-common star-common
diff -ruN android_device_samsung_star-common/BoardConfigCommon.mk star-common/BoardConfigCommon.mk
--- android_device_samsung_star-common/BoardConfigCommon.mk    2018-06-23 23:39:06.136570189 +0300
+++ star-common/BoardConfigCommon.mk    2018-06-16 04:04:58.443922696 +0300
@@ -2,7 +2,7 @@
 # SPDX-License-Identifier: Apache-2.0
 
 COMMON_PATH := device/samsung/star-common
-
+BOARD_KERNEL_CMDLINE += enforcing=0 androidboot.selinux=permissive
 # Platform
 BOARD_VENDOR := samsung
 TARGET_BOARD_PLATFORM := exynos5
@@ -121,7 +121,7 @@
 
 # SELinux
 BOARD_PLAT_PRIVATE_SEPOLICY_DIR += $(COMMON_PATH)/sepolicy/private
-
+BOARD_PLAT_PRIVATE_SEPOLICY_DIR += vendor/maruos/sepolicy
 # Lineage hardware
 ifneq ($(findstring lineage, $(TARGET_PRODUCT)),)
 BOARD_HARDWARE_CLASS := \
diff -ruN android_device_samsung_star-common/rootdir/etc/fstab.samsungexynos9810 star-common/rootdir/etc/fstab.samsungexynos9810
--- android_device_samsung_star-common/rootdir/etc/fstab.samsungexynos9810    2018-06-23 23:39:06.140570178 +0300
+++ star-common/rootdir/etc/fstab.samsungexynos9810    2018-06-16 03:58:41.350107110 +0300
@@ -5,7 +5,7 @@
 
 #/dev/block/platform/11120000.ufs/by-name/SYSTEM         /system     ext4    ro,errors=panic                                             wait
 /dev/block/platform/11120000.ufs/by-name/CACHE          /cache      ext4    noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic       wait,check
-/dev/block/platform/11120000.ufs/by-name/USERDATA       /data       ext4    noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic       wait,check,encryptable=footer,quota
+/dev/block/platform/11120000.ufs/by-name/USERDATA       /data       ext4    noatime,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic       wait,check,encryptable=footer,quota
 /dev/block/platform/11120000.ufs/by-name/EFS            /efs        ext4    noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic       wait,check
 /dev/block/platform/11120000.ufs/by-name/MISC           /misc       emmc    defaults                                                                                      defaults
 /dev/block/platform/11120000.ufs/by-name/DQMDBG         /dqmdbg     ext4    noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic       wait,check
diff -ruN android_device_samsung_star-common/rootdir/etc/init.samsungexynos9810.rc star-common/rootdir/etc/init.samsungexynos9810.rc
--- android_device_samsung_star-common/rootdir/etc/init.samsungexynos9810.rc    2018-06-23 23:39:06.140570178 +0300
+++ star-common/rootdir/etc/init.samsungexynos9810.rc    2018-06-15 01:53:40.878142439 +0300
@@ -3,6 +3,7 @@
 import /init.wifi.rc
 import init.gps.rc
 import init.baseband.rc
+import init.maru.rc
 
 on early-init
     mkdir /efs 0771 radio system
diff -ruN android_device_samsung_star-common/star-common.mk star-common/star-common.mk
--- android_device_samsung_star-common/star-common.mk    2018-06-23 23:39:06.140570178 +0300
+++ star-common/star-common.mk    2018-06-15 01:50:09.675217406 +0300
@@ -111,3 +111,4 @@
 
 # Call proprietary blob setup
 $(call inherit-product, vendor/samsung/star-common/star-common-vendor.mk)
+$(call inherit-product, vendor/maruos/device-maru.mk)

[Georgian Chituc]

vendor/maruos same like on maruos github but with some selinux mods , external/lxc and /system/usr2 (twaik android pulseaudio server) used on S9+ just to keep track of them :

https://www.androidfilehost.com/?w=files&flid=277779

[Georgian Chituc]

To make the S9/S9+ a officially device we just have to use https://wiki.lineageos.org/devices/star2lte/build   .

Before brunch star2lte ,just use the patch for framework native and base , kernel and device ,  add external/lxc , vendor/maruos and /vendor/samsung/star-common blobs  . And compile it .







[Preetam]

Great!

I will take a look at 15.1 on the Nexus 5 so I can test this out myself. Maybe we can just jump straight from M to O for the next Maru release if things are stable. We can still use the cm-14.1 manifest for any devices not supported on 15.1 yet.

[Georgian Chituc]

Yes ,  the cm-14.1 manifest  is very good  to have cause LOS 15.1 is a work in progress  . LOS 14.1 was very stable , but some features of LOS 15.1 like multiple windows sometimes have problems .  But of course all will be fixed and in about 6 month we'll have a stale LOS 15.1 too .

[Georgian Chituc]

Just to keep track of the /init.maru.rc  used on S9+ right now is here :

mcprepare service script also start the android pulse audio server .

------------------------------------                        

on init
    mount tmpfs none /sys/fs/cgroup mode=0750,uid=0,gid=1000
    mkdir /sys/fs/cgroup/devices 0750 root system
    mount cgroup none /sys/fs/cgroup/devices devices
    mkdir /sys/fs/cgroup/freezer 0750 root system
    mount cgroup none /sys/fs/cgroup/freezer freezer

on post-fs-data
    mkdir /data/maru 0770 system system

service mflinger /system/bin/mflinger
    class late_start
    seclabel u:r:mflinger:s0
    oneshot

service perspectived /system/bin/perspectived
    class late_start
    seclabel u:r:perspectived:s0
    oneshot

service mcprepare /system/bin/mlogwrapper /system/bin/mcprepare
    class late_start
    seclabel u:r:sudaemon:s0
    user root
    group root
    oneshot

-----------------------------------------------------------------

/system/bin/mcprepare                                        
#!/system/bin/sh

export HOME=/data/pulse

export TMPDIR=/data/pulse

export LD_LIBRARY_PATH=/system/usr2/lib:/system/usr2/lib/pulseaudio/:/system/usr2/lib/pulse-11.1/modules/

/system/usr2/bin/pulseaudio_android --disable-shm -n -F /system/usr2/etc/pulse/android-pulseaudio.conf --daemonize=true --use-pid-file=true --log-level=0 --system=false --dl-search-path=/system/usr2/lib/pulse-11.1/modules/ --exit-idle-time=-1 --disallow-exit=true

####next must be the orig mcprepare script that restore/create  /data/maru ,is safe to put here cause pulseaudio runs in background

[Georgian Chituc]

system-maru.tgz that become /system/maru and /data/maru  .

/data/maru/lxc/share/lxc/config/debian.common.conf  contains small changes from maruos/github variant  like :

lxc.mount.entry = /dev/input dev/input none bind,ro,create=dir 0 0

lxc.mount.entry = /sdcard mnt/sdcard none bind,optional,rw,create=dir 0 0

[Georgian Chituc]

/data/maru/containers/jessie/rootfs must be populated with a aarch64 Linux image for S9+ now is Ubuntu 16.04 .

I will post the container images inside "[LXC] Container Images " thread .

Now are uploaded all pieces that combined make the MaruOS on S9+ with sound enabled and Ubuntu 16.04 aarch 64 .

 We now just miss the settings app patch .Hope to have it done .

/system/lib64/liblxc.so.1 must link to /system/lib64/liblxc.so

/system/lib/lxc/rootfs/ must be created manualy if build scripts do not create it so lxc to start .

maru-lxc-binaries.tar.gz to manualy run lxc-stat -n jessie are atatched too .

[Georgian Chituc]

Ok , I inspected Settings app from Android O , and it looks easy to fix .

I got some time to investigate it . I'll put soon the patch  .

[Georgian Chituc]

Under intensive CPU load the phone battery may discharge while docked , because dock itself drain 9W of power , so the  5v-9v -2A  adapter that comes with your phone can not give ehought power to your phone  .

So to use the S9 docked and to fast charge in same time , you need the Samsung EP-TA300CWEG 25W adapter . I got mine from Amazon , but is same it comes with the Samsung TabPro S tablet . It can give 12V 2.1A  .I just tested it and the phone do not discharge anymore while docked

[Los Angeles]

Well done, Georgian! Which variant of the S9+ did you buy? (SD845 or Exynos 9810)

[Georgian Chituc]

Hello  and glad to raed from you again :)

SD845 variant is not supported by Lineage OS , mostly because it can not be bootloader unlocked .

So if you want to flash a custom rom on your S9 , you must carefully choose a Exynos .

[Los Angeles]

thanks for all your hard work, guys. this is such a fantastic project 

[Don White]

Something  of  interest....

There's an explanation  of  how  the  Huawei Mate 10 Android smartphone

  connects  to  a  monitor about  half way  in  this  video   by  charbax

https://www.youtube.com/watch?v=lYfJm82EuRI

________________________________________

[Adam Kaesberg]

i am beyond excited for this!! i have some server hardware im not using that i want to donate to be a host for builds or as a build machine if your interested.

[Georgian Chituc]

Hello , yes this kind of help will be great appreciated . We really need a host to keep Los 15.1 build on. Can you tell us the server specs ?
Thank you !

[Georgian Chituc]

Adam , my email is dianaxxyyzz at gmail.com about the host to make  a shared MaruOS buiild

[Georgian Chituc]

This are the complete  framework MaruOS patches for LOS 15.1 that incoude the patch to cast to miracast and chromecast

It still miss the Settings App patch . That will be posted separately

[Adam Kaesberg]

this is great to see and so far the Z2 port is coming along very well! soon we will be able to get it to a RC1 level

[Don White]

Samsung wants its customers to spend $100 extra for  the DEX   hub,

however  a  tech writer  has found  that  a much cheaper  USB-C hub  will show  the  DEX

desktop.  ARKTEK's USB-C hub that features two USB-A ports.

 https://www.androidcentral.com/how-use-samsung-dex-regular-usb-c-hub

It might  be  possible  to   use Maru OS  with this hub ???

[Georgian Chituc]

If it works for dex it may work for maru os too. But without a patched kernel or without a hub with a chip that tell the phone is samaung I dnt think it works until somebosy confirm this

[PHoSawyer]

Hi all, I've ditched my OnePlus 5T port. I've now bought an S9 and got it today!

So I'll be heavily into testing and helping for the S9 port. I actually have the Artek hub above as I use it for my Dell XPS13. If it's the same one it has HDMI, 2x USB-A, Ethernet and PD in (USB-C). I'll have a look this afternoon to see what it comes up with. I've tried it with an S8 and the S8 came with with a desktop I'm sure. Unfortunately the S8 has no treble support.

Anyway I have the 64Gb S9 UK Exynos version so I should be good. Where can I get hold of the build? One available or do I have to compile a new one?

[Georgian Chituc]

hello , 

I will give you my build so you to dnt lose time polishing it . 

I have to make a backup anyway of the rom cause I want to try smth .

I will upload soon 

[PHoSawyer]

Excellent!

Re the dock above, it's actually a Cable Matters one. USB, fast charging (I think), HDMI (mirrored screen) and even the Ethernet all work so I'm hoping for good things!

Get that build over! I need to get the propriety blobs before I can build lineage (and maru) so need to root I think. Stuck on breakfast

[PHoSawyer]

Hey dude, you had anytime to do this yet?

[PHoSawyer]

Hey Georgian,

Have you had anytime to do this yet?

[Georgian Chituc]

Yes , I'm compiling it right now into maru sources , so it to become a official device for maru os . So it will be ready soon

[Georgian Chituc]

Here is the Maru Os for S9+ (star2lte)

The desktop  user is maru password maru

Sound is enabled by default using taik native pulseaudio server .

Mouse/keyboard are avaible to androd if desktop is not started .

Desktop linux image is Ubuntu 16.04 arch64 .

Here is the zip you have to flash via TWRP .

https://androidfilehost.com/?fid=11410963190603842634

Also for all lineage os based roms ,for S9+ , you need your vendor files to be BRE5 or camera will not work.

https://androidfilehost.com/?fid=674106145207489374

[Georgian Chituc]

Linux on dex beta will be avaible to try next week , but samsung say that you dnt have a full desktop like because some packages will not work cause of andorid security . So Maru OS still win here but is good cause maybe we'll get hw acceleration on Maru too :D

[Preetam]

Incredible work Georgian. It's pretty awesome that Maru runs on the Samsung S9 even before Samsung's own Linux on Dex :)

The next step is to get your port integrated as an official build. Let's talk offline to get this going soon.

[Jovan Smith]

If i got a rootfs what then do i do. Theres not a great guide nowhere. And do u hve the htc maru and ubuntu zip. Please reply.

[Georgian Chituc]

I assume you want to switch your Linux desktop from Ubuntu to Debian or something like this. A rootfs.tar.gz is a Linux compressed that is decompressed when maruos first boot , at /data/maru/containers/jessie/rootfs or atdata/maru/containers/default/rootfs starting with maru 0.6 . We need to know what exactly you want to do , cause for example for HTC 10 it already comes with Ubuntu

[Georgian Chituc]

The s9+ TWRP image I uploaded here have inside /system a file names rootfs.tar.gz , that will be uncompressed at /data/maru/containers/default/rootfs , at first phone boot and after any factory reset . This rootfs.tar.gz contains the full Ubuntu file system structure that allow you to run the Ubuntu desktop after it will be decompressed at /data/maru/containers/default/rootfs . If you want to switch to Debian you can get it from wiki and uncompressed it at data/maru/containers/default/rootfs after you delete the existing one . You have to get suaddon installed using TWRP cause you need root access for this

[Bart Jitter]

Hi 

This Debian image from the wiki is a modified one to get it working inside MaruOS, if i understand well. 
Is there a Arch image? If not; What are the steps to create a modified one for MaruOS? 

Is there a step by step guide to get the Debian or if existing the Arch image instead of the Ubuntu one? 

Thanks! 

Op vrijdag 16 november 2018 18:30:17 UTC+1 schreef Georgian Chituc:

[Georgian Chituc]

I don't know about what phone model you talk , for S9 you can use the already existing Ubuntu arch64 , the Debian arch64 from wiki , or a arch Linux image too . The idee is you need a arch64 Linux image on a arch64 supported phone . if your phone is not arm64 like Nexus 5 you need the armhf one . You can find armhf Debian and Ubuntu around here too .

It is some time since I build a arch Linux image and I think I will have to build one again , probably tomorrow . Any way I found Ubuntu 16.04 the best working and best overall.
Arch Linux worked perfect too , but I did not liked some windows had some lag like .
For example in arch Linux oppening terminal prefferences looks to lag , but other programs don't have problems . This I saw only for arch Linux , maybe they have different build options .

[Georgian Chituc]

Thanks to Preetam help , S9+ is on the way to become a officially supported device .
Until we finish set up some repos you can find here some pre official builds .
Pulseaudio server is now compiled at Android build time , no more already build binaries

[Bart Jitter]

Hi 

HTC 10, maybe I switch it for a S9. 

Yes, I know 64 hardware needs best 64 system. Anyway I believe that Arch has stopped supporting 32 bit. 

Don't like Ubuntu, but Debian is ok for now and works well! 

Will try to put openBox on it to night. 

Does that mean that we can put any Linux inside that has arm64 image?

Maybe it's the Terminal application that Arch uses as default?  

Which one for Arch I have to chose from this list if I want to take the risk: 

https://archlinuxarm.org/about/downloads

The ARMv5 Multi-platform? 

It seams this is the right one: ARMv8 AArch64 Multi-platform?

Op vrijdag 30 november 2018 19:59:38 UTC+1 schreef Georgian Chituc:

[Georgian Chituc]

If your existing ubuntu inside HTC 10 is arm64 ARMv8 AArch64 arch linux  is ok .

If you have armhf linux inside HTC 10 you need a armhf then .

I dnt remember what the last build of HTC 10 had inside , but because a 32 bit mflinger requires a 32 bit mclient  , you need a prebuild armhf linux , or if you have a armhf linux in htc 10 , and you want to put a arch64 linux  , you have to compile a 32 bit mclient to run inside arch64 container . This only if your orriginal build had a armhf linux , meaning your mflinger is 32 bit too .

If you have a arch64 linux inside HTC10 , you can just start testing any arch64 linux distros , adding mclient (arch64) inside them ,if they are build by yourself and dnt have a mclient inside.

[ACM]

Hi, Georgian !

Before everything, congrats, man !!! And thanks for this excellent work !

I am trying install this on my s9 plus, following your orientation... so I used TWRP, flash vendor zip and then the build zip as you said: "Here is the zip you have to flash via TWRP . https://androidfilehost.com/?fid=11410963190603842634".

But when reboot, device didn't evolve from splash screen and after 40 mins, I gave up... 

Just to mention, comparing the zip to s9 plus and the one to htc10, I can figure out at first the huge difference in size... and the file structure are different too... but I didn't find rootfs.tar.gz as you said there was in s9 plus build... 

So could you help me to solve this ? Are your zip files OK ?

Thanks !

On Friday, 23 March 2018 13:52:15 UTC-3, Georgian Chituc wrote:

UPDATE:

Samsung S9+ is officially supported by Maru Os ,you can use the official builds , just flash new vendor zip from https://androidfilehost.com/?fid=11410932744536982158 using TWRP , before flashing MaruOS for S9+

Old post :

Thanks to Google 's Project Treble ,which separates vendor files from Android framework the port of AOSP Android to devices that comes with Android 8.0 and newer is easier .

This will allow Maru OS to be also easly ported to newer devices like galaxy S9 .

Work that must to be done :

-Recompile Kernel with support for LXC
-Integrate MaruOs mods Into Android 8.1 AOSP and build Project Treble system image for S9

[Georgian Chituc]

You got wrong maru - vendor combination .You flashed the new vendor that is required by
official s9+ maru os , and one of my old onofficial build from androidfilehost .

-if you want to run one of my old unofficial builds you have to flash first the vendor from the bottom of first post - bre5 .

-if you want to run official maruos s9+ builds from GitHub , you need the ari9 vendor

[ACM]

All right, I got it !!! You disclosure the mistake... I will try what you said. Thanks !

Although I'm felling myself a little newbie... following github link for maru 0.6.3 (https://github.com/maruos/builds/releases/tag/v0.6.3) we can see 2 types of files between changelogs and checksums: maru-gf283c12-xxxxxx.tar.gz, with rootfs; and maru-update-xxxx.zip

Then, I'm not sure if I'm right, but I guess we need to combine those files to create a "flashable" TWRP zip... so, would you mind explain how can we do that ? 

Again, thanks !

[Georgian Chituc]

 Just flash vendor ari9 and maru-v0.6.3-update-star2lte-83993fa5.zip

[ACM]

All right, thanks !!!

So, I understood that we don't need to pre processing any of those tar.gz files, because Ubuntu or Debian was compressed inside that 670MB maru-update-xxx.zip.

Is that correct ?!

By the way, thanks in advance for your kind help.

[Georgian Chituc]

Yes

[ACM]

Hi Georgian,

Now, I'm figuring out what's happening when Maru start on my s9 plus... 

I'm getting a weird (and useless) desktop, sometimes without applications menu and menu bar malformed (e.g., clock and user spaces didn't appear... restarting maru solve this, but it's annoying!) or without applications menu... 

Just to mention, I got always a solid dark wallpaper and light menu bar, with application menu on the left and user spaces + clock on the right.

Mouse and keyboard recognized and seems to working, indeed I didn't get a left/right mouse click menu options.

Some hints to what's happening ? Any guidance to heal this ?

Thanks !

On Wednesday, 30 January 2019 08:08:59 UTC-2, Georgian Chituc wrote:

Yes

[Georgian Chituc]

Yes, that wired my phone works just perfect everything .
You have to tell me what exactly you have flashed some to understand what's going on. Do you run a GitHub downloaded or a filehost one and what exactly is the name of rom file you flashed , you have Ubuntu or Debian?

[ACM]

I used TWRP, flashed vendor VENDOR-27_ARI9.zip first and maru-v0.6.3-update-star2lte-83993fa5.zip from github (I've checked sha256 sum and OK). 

As I downloaded and flash the file from github, I guess it's Ubuntu on board.

Everything on Android works flawlessly !

Thanks.

[ACM]

I used TWRP, flashed vendor VENDOR-27_ARI9.zip first and maru-v0.6.3-update-star2lte-83993fa5.zip from github (I've checked sha256 sum and OK). 

As I downloaded and flash the file from github, I guess it's Ubuntu on board.

Everything on Android works flawlessly !

Thanks.

On Thursday, 7 February 2019 12:06:53 UTC-2, Georgian Chituc wrote:

[Georgian Chituc]

Yes it is strange , cause that is a official build and I tested myself the official builds and they have Debian as desktop but was working .

However you can try to format all cache partitions and system and data except internal storage and flash one of my unofficial builds who have Debian inside to see all is fine for you too.

To do this you have to flash
https://androidfilehost.com/?fid=11410963190603842634

https://androidfilehost.com/?fid=674106145207489374

Flash bre5 vendor again before flashing rom

[Georgian Chituc]

Also can you give us the exact phone model you have? Is it a G965f , right?

[C G]

If you have time you can set up a PC with TeamViewer inside , and USB adb phone to it . I can check what a going on there 

On Thu, Feb 7, 2019, 5:50 PM Georgian Chituc <diana...@gmail.com wrote:

Also can you give us the exact phone model you have? Is it a G965f , right?

--
You received this message because you are subscribed to a topic in the Google Groups "Maru OS dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/maru-os-dev/YVkUiwuKMRQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maru-os-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/maru-os-dev/230861d2-c067-4a5f-bc64-46fc531464d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ACM]

Yeah, SM-G965F.

[ACM]

OK, I'll try that unofficial build tonight... and come back with results ASAP... 

[ACM]

Sure, thanks !

I'll come back to this suggestion after try unofficial build... I guess it'll work !

[ACM]

I see BRE5 was in a tar file... TWRP can flash tar file too ?

On Thursday, 7 February 2019 13:48:28 UTC-2, Georgian Chituc wrote:

[Georgian Chituc]

For that you need odin

[ACM]

Hi,

These unofficial builds work as expected... by the way, I'm using it right now ! ;)

Before going flash BRE5 and these builds, I've tried new maru build v0.6.5 star2lte checking if something would be different and maru start as expected, but nothing gonna happened... and again, I got a malformed desktop... 

I'm suspecting of some configuration might causing this... I'll check this hypothesis later...

 Anyway... thanks for your attention, kind response and effort, without any of that (from all of you, guys!) maru wouldn't be a real (and unique) OS that give the real Desktop experience besides an up-to-date Android environment.

Cheers !!!

[Georgian Chituc]

Ok, I'm very happy that you have good working the unnoficial one . However that build is having a Ubuntu bug that make your Gmail to DNT load emails after Maru os is started . To fix this you have to start Ubuntu and do:

sudo rm /lib/systemd/system/sys-kernel-debug.mount

Then restart phone and problem gone .

I also remember I tested myself the official maru-v0.6.5-update-star2lte-a816ab75.zip of course flashing ARI9 vendor before rom , and that worked good . I will have to test again the latest official builds

[Georgian Chituc]

Yes I can confirm
maru-v0.6.5-update-star2lte-a816ab75.zip from
https://github.com/maruos-bot/builds/releases
Worked for me , I just checked logs . If you wanna switch to official builds you can start with that , just remember all time before flashing a official one to all-time flash ari9 vendor before rom

[Preetam]

@Georgian Can you try the official builds from the maruos org, not the maruos-bot user? The maruos-bot user is just used for test builds.

See https://github.com/maruos/builds/releases

[Georgian Chituc]

Oke , great , thanks , I will try tonight

[ACM]

Hi...

I just checked this build https://github.com/maruos/builds/releases/download/v0.6.5/maru-v0.6.5-update-star2lte-b1dbfb26.zip remembering flash ARI9 vendor before and I got the same issue... you can see attached, observe the time stamps... one time Desktop appeared malformed... few minutes later, I got a Desktop, but without any response...

[PHoSawyer]

Georgian,

Have you the repo for the kernal and device build? I really want to get started and try and build maruos for the S9 (starlte)

[Georgian Chituc]

Yes they are in maru os github . I can build them and you to try . Basically all should work same as s9+ but i did not had a device to test on

[PHoBwz]

If you dont mind building on starlte then I can try! Go for it!