Game Plan

[Preetam]

Hey guys!

Just wanted to lay down a quick sketch of my plan to get the ball rolling.

My goal is to get all of you involved ASAP so we can speed up development and get Maru out to a lot more people via device ports.

Over the next few weeks I am going to be organizing and uploading all of the different repositories that comprise The Maru OS Project to the project's GitHub.

Right now, that's basically 10 repositories, and probably a few more to split things out cleanly. I'll probably also have to make a few changes to the build process while doing this. My intention is to make this as clean and well-organized as possible so that you can easily get up and running with your dev builds.

As I add these repositories, I will be updating the project wiki to fill everyone in on how these puzzle pieces fit together to form Maru OS. I'll have the entire build process documented, from the kernel, to the Android side of Maru, to the desktop Linux side of Maru. I'll also post on this forum as each repo goes up to answer any questions you may have. Your patience is much appreciated in this process!

Here's how you can get involved right now.

If you have a Nexus 5, install Maru and test it out! Report feedback in the user forum, and file bugs/feature requests as issues on the central maruos repo (I'm working with Petya to migrate the current bug/feature sticky I was using previously for the beta program).

If you don't have a Nexus 5, are you interested in porting to your device? Because I'd love to have your ports! I know a lot of people contacted me over email a few months ago (when I initially started the beta program) offering to port to their devices--this is now finally happening. I'll go over my notes from then and post a separate thread where everyone can volunteer for a device.

At least one person has contacted me regarding reading material for learning Android platform development. If you, too, are not familiar with AOSP development, you can get up to speed by going through the official AOSP docs. The docs are really good; they are worth your time. Since Maru is based on AOSP, a majority of your development will be following a similar process.

Thanks again for taking the time to be a part of this project! I can't wait to start working with everyone.

Preetam

[Craig Errington]

Sounds good Preetam. I'm keen to start a port to the LG G2 (as it's the phone I have laying around to play on) - it's literally the same internals as the Nexus 5 so should be a fairly straightforward build.

Looking forward to seeing the repositories going up.

[Antonius Harijanto]

Hi Preetam!
Thanks so much for making an effort to make this open source! I'm so excited to help porting it to Nexus 5X. I have some professional experience working in Android OS platform development. Can't wait to get involved! :)

God bless!

[Prakash Srinivasan]

Hi Preetam,
Very interesting project. I am working on android porting since the android project started and having enough experience on Cyanogenmod as well, I would like to contribute on porting part. I am interested on the development boards like Odroid/RPI/Beagle. I am also having Nexus 7 tab.

Looking forward your code on GIT.

TIA,
Prakash.

[Preetam]

Sounds good, I'd love to have your (and Craig and Antonius' above) help with ports! It would be pretty interesting to see this on an Odroid...I have the XU actually.

The code is getting there steadily--shouldn't be much longer before everything is ready to build. Just 3/4 more repos I need to get out there.

Looking forward to working with you,

Preetam

[Dionis L]

@Preetam , maybe you think to make a version that use  Gnome ,Wayland and not Xorg .
If you will be able to do this , the device will rock .
They say  Wayland work better on mobile than xorg , and It also have support for libhybris so the android 3d acceleration will work .

[Preetam]

Yeah, I need to look into that. That's a big change but it would be really cool to have hardware acceleration! There are a few other things I want to get working first before I look at that though. There is a GitHub issue tracking it too: https://github.com/maruos/maruos/issues/38

[Dionis L]

I recompiled android for lg g4 , all is working except slimport lol .

I got a rom based of orriginal g4 rom , and in that is working all , cause is based of orriginal rom.

What will be the steps to just integrate maru binaries in this rom , without to recompile it ?

* Kernel can be recompiled with suport for lxc , here will be no problem.
* System image can be easly modified ,just unzip and re compress it.

Can we just try to add to the ziped system ,the maru files ? Rom is rooted we can do what we want .
I'm not realy sure how mouse and keyboard are added just to debian and not to android .
How is this done in maru?

[Robin]

Need some here.Wanna port Maru for Xperia ZR(dogo) but keep getting errors.this after another  inside obj related error.Solved the kernel error temporally by putting prebuilt kernel from my another source based on mm.

make: *** No rule to make target 'out/target/product/dogo/obj/SHARED_LIBRARIES/libqservice_intermediates/export_includes', needed by 'out/target/product/dogo/obj/SHARED_LIBRARIES/libOmxVdec_intermediates/import_includes'.  Stop.

 

[Preetam]

Where did you get the device tree for dogo from? Sony Xperia AOSP sources? You may want to chat with Noel (cc'd) who knows a bunch about Sony devices and is working on some Xperia ports. Also check out his thread here: https://groups.google.com/forum/#!topic/maru-os-dev/s5miAGjwpDQ.

[Robin]

I used CM device tree.AOSP binary on Sony dev. site is unavailable.I'll contact with him,Thanks.

[Luka Panio]

Idk but it it will be cool to use libhybris.

[daren han]

hi,

Can Maru OS be ported for Asus Fonepad ME371MG ?

regards,

Daren

[Twaik Yont]

Hi. What do you think about creating GSI builds based on AOSP GSI? It will let everybody who can patch kernel (or download already patched one) to run MaruOS on his device. 

суббота, 11 июня 2016 г. в 17:47:48 UTC+3, Preetam D'Souza:

[Preetam D'Souza]

Hi Twaik!

On Friday, September 11, 2020 at 2:50:59 PM UTC-4, Twaik Yont wrote:

Hi. What do you think about creating GSI builds based on AOSP GSI? It will let everybody who can patch kernel (or download already patched one) to run MaruOS on his device. 

That would be awesome. Are there any good examples I can look at to see how to set up the GSI?

[Twaik Yont]

Android already has treble device tree. You can read https://github.com/phhusson/treble_experimentations/wiki/How-to-build-a-GSI%3F but I think you know everything that is written here. 

суббота, 12 сентября 2020 г. в 00:08:33 UTC+3, Preetam D'Souza:

[Preetam D'Souza]

On Friday, September 11, 2020 at 5:13:16 PM UTC-4, Twaik Yont wrote:

Android already has treble device tree. You can read https://github.com/phhusson/treble_experimentations/wiki/How-to-build-a-GSI%3F but I think you know everything that is written here. 

суббота, 12 сентября 2020 г. в 00:08:33 UTC+3, Preetam D'Souza:

This is a useful reference - thank you!

[dare...@gmail.com]

hi everyone,

can maru OS be ported for xiaomi max? it has 3 gigs of ram and 32 gig storage.

regards,

Daren

[Twaik Yont]

Are you available in telegram/whatsapp? I think I can help in making Maru capable to use Android's sound and graphic subsystem without modifing Android's lowlevel source.

суббота, 12 сентября 2020 г. в 03:25:52 UTC+3, Preetam D'Souza:

[luka...@gmail.com]

It can be done with libhybris, i have no other ideas about GPU, audio uh either libhybris or implementing android audio client

субота, 12 вересня 2020 р. о 17:34:14 UTC+3 twai...@gmail.com пише:

[Twaik Yont]

Actually we do not need to embed libhybris into system inage to use GPU or audio features. Using HAL weill make using sound in Debian countainer and Android impossible, but there is another choise: embed cross compiled pulseaudio server and start it with Android's init. 

We already have SLES sink for pulseaudio and pulseaudio makefiles for AOSP. About graphics: I think we can port android-emugl to forward GLES command queue to Android side of graphic server. I am still thinking how to make this right without modifying Android source codes.

суббота, 8 мая 2021 г. в 19:35:16 UTC+3, luka...@gmail.com:

[nift...@gmail.com]

for audio you could use pulseaudio with openal backend if that exists, openal for android is available here: https://github.com/kcat/openal-soft

there is also an older port directly to android inside "XServer XSDL" from https://github.com/pelya

GPU for Qualcomm devices could be done with https://github.com/Heasterian/mesa-turnip-kgsl it has been tested on OnePlus 7T