[Nexus 7] Porting Thread

[Preetam]

See Tyler's main post below for latest builds:
https://groups.google.com/d/msg/maru-os-dev/zdT_qHydRXA/yXys5u0dAgAJ


*moving grouper porting discussion over to it's own thread*

@Tyler
 

checking for arm-linux-androideabi-gcc... no

Looks like make can't find the android cross-compiler and is using your host's gcc instead.

Here's the path I have:

dev@host:/var/maru/aosp$ which arm-linux-androideabi-gcc
/var/maru/aosp/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/arm-linux-androideabi-gcc

This should be automatically downloaded with repo sync to prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8.

Can you check that this path exists in your workspace and that it is in your $PATH?

On Tuesday, August 30, 2016 at 12:54:26 AM UTC-4, Tyler Martin wrote:

That log was when I was trying to build a 3.4 kernel from xda. The reason I tried it is because at first I couldn't get the kernel source from Google to compile even before adding the options needed by Maru. I finally fixed it and got it to build with and without the options. I do have another issue so I'll post a few logs in the morning.

Update:

Here are the two logs.

Terminal Output

Config.log

Thanks for the help!

Edit 1/31/17: Add link to Tyler's latest builds

[Tyler Martin]

Latest Build for Nexus 7 2013 Wifi aka Flo (01/31/2017):

Download Link

• Download MaruOS from link provided above 

•  Download Arm 6.0 Pico package from opengapps.org

• Reboot to TWRP 

• Backup your device 

• Do a Factory Reset in the Wipe section (Please DO NOT wipe your system. It causes issues)

• Flash the MaruOS zip 

• Flash OpenGapps zip 

•  Reboot

I just flashed this myself and haven't really come across any issues. Please let me know if you find anything.

Thanks! 

[Tyler Martin]

@Preetam

Still getting the same error. When I run ' which arm-linux-androideabi-gcc' I get '/media/data/Android/MaruOS/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/arm-linux-androideabi-gcc' returned back.

EDIT: Well I guess it's a little different. Attached two logs

[Preetam]

OK, cool, it can find the right toolchain now so we are making progress!

Now to the next error:

LDFLAGS=" -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,--warn-shared-textrel -Wl,--fatal-warnings -Wl,--icf=safe -Wl,--fix-cortex-a8 \
		-Wl,-dynamic-linker,/system/bin/linker \
		/media/data/Android/MaruOS//home/tmartin/Android/Out/MaruOS/target/product/grouper/obj/lib/crtbegin_dynamic.o \
		-lc -ldl \
		-L/media/data/Android/MaruOS//home/tmartin/Android/Out/MaruOS/target/product/grouper/obj/lib \
		/media/data/Android/MaruOS//home/tmartin/Android/Out/MaruOS/target/product/grouper/obj/lib/crtend_android.o" && \

Okey, I see the problem here...

Are you using a custom build output directory? Looks like you have it set to /home/tmartin/Android/out/MaruOS, whereas the actual source is stored in /media/data/Android/MaruOS.

It looks like the AOSP build system uses relative paths for targets if the ANDROID_PRODUCT_OUT is the default, i.e. it is under the source workspace (/media/data/Android/MaruOS). But it uses absolute paths if it is not under the source workspace. Weird.

I've never used a custom output directory, so never ran into this issue. The Android.mk I wrote for LXC doesn't handle the case where the target paths are absolute, as it is in your case. I'll try to see if I can make it work for absolute paths too by experimenting with using a separate output dir like you did. I've even filed this as a bug: https://github.com/maruos/platform_external_lxc/issues/1.

Until then, can you try compiling everything with the default out directory? That should get you past this error.

[Tyler Martin]

Okay. I changed it to the default out directory. Looks like I get a similar issue but somewhat different. Seems like this LXC will be the death of me lol

[Tyler Martin]

And now I think I know why. Somehow it's not looking at the arm-linux-androideabi that I have in my $PATH. Changing that and trying again

[Tyler Martin]

And now it's fixed! Thank you! I did run into another quick snag. I thought I'd ask you before I started to mess with system image sizes.

Running:  mkuserimg.sh -s out/target/product/grouper/system out/target/product/grouper/obj/PACKAGING/systemimage_intermediates/system.img ext4 system 681574400 -j 0 out/target/product/grouper/root/file_contexts

make_ext4fs -s -T -1 -S out/target/product/grouper/root/file_contexts -l 681574400 -J -a system out/target/product/grouper/obj/PACKAGING/systemimage_intermediates/system.img out/target/product/grouper/system

Creating filesystem with parameters:

    Size: 681574400

    Block size: 4096

    Blocks per group: 32768

    Inodes per group: 6944

    Inode size: 256

    Journal blocks: 0

    Label: 

    Blocks: 166400

    Block groups: 6

    Reserved block group size: 47

error: ext4_allocate_best_fit_partial: failed to allocate 2240 blocks, out of space?

error: failed to build out/target/product/grouper/obj/PACKAGING/systemimage_intermediates/system.img from out/target/product/grouper/system

Out of space? the tree size of out/target/product/grouper/system is (MB): 

721 out/target/product/grouper/system

The max is 650 MB.

build/core/Makefile:974: recipe for target 'out/target/product/grouper/obj/PACKAGING/systemimage_intermediates/system.img' failed

make: *** [out/target/product/grouper/obj/PACKAGING/systemimage_intermediates/system.img] Error 1

 

[Preetam]

Great, we are past the LXC part!

Yikes, looks like the system.img is ~70MB too large to fit on grouper's system partition. I believe that the system partition size is fixed based on grouper's hardware, so I don't think you can change it reliably.

It's definitely the size of the desktop rootfs image that's eating up the extra space. It's around 450MB right now. Looks like I'll need to shrink to ~350MB to fit comfortably.

Let me work on a minimal build of the desktop that'll hopefully shrink the size and get that to you sometime tomorrow.

[Tyler Martin]

Thanks for all the help! I've working on getting a build for the 2013 Nexus 7 as well. Have you made any attempts to rebase to marshmallow or nougat? Since there are a few Nougat builds for the Nexus 5, I thought about attempting it.

[Preetam]

Got that slimmed down desktop for you, 318MB. Download here.

I just dropped LibreOffice so everything should work fine, but just a heads-up that it hasn't been thoroughly tested or anything. It should be good enough to get the port going though.

I've started work on merging in Marshmallow actually. I don't see Maru OS officially moving to N for a while since it's so new; I like seeing some stability fixes and minor revisions come in from the Android team first.

[Tyler Martin]

Awesome! Thanks. I'll give that a go. I'll be able to build and test shortly.

I actually have a build ready for the 2013 Nexus 7 wifi. I don't have the device so I'll upload and see if chev or someone can test it as well.

That's awesome to hear. I'm interested to see how merging marshmallow goes. Maybe I'll try an unofficial Nougat build.

[Tyler Martin]

Built fine. Flashed fine. Android ran fine. Plug the cable into the tv then into the phone, switch to turn Maru on still can't be switched. I'm wondering if it even has MHL or Slimport.

[Preetam]

Oh yeah, only the 2013 model has SlimPort: http://www.slimportconnect.com/slimport-supported-devices/.

2012 and other devices without SlimPort/MHL will need to wait till at least https://github.com/maruos/maruos/issues/5, which would make it possible to launch the desktop in the background and SSH or VNC in.

chev can probably test out your 2013 build!

[Preetam]

On Sunday, September 4, 2016 at 5:28:40 PM UTC-4, chev droid wrote:

Hi Tyler

I tested it right now. Sadly my n7 won't boot.

I had ubuntu installed so I flashed stock 5.1.1 and after wipeing I flashed your boot.img and system.img. After the bootloader (google logo) it takes a few secounds after that it reboots and not even showing any android/maru boot logo.

And idk if android writes some logfiles that early in the boot process, I'll have a look this evening if I can find something.

 

Sounds like it is an error really early in the boot sequence... possibly the kernel or some critical failure in Android's init sequence.

If you have TWRP then you may be able to boot into recovery right after the device boot loops, and use the Terminal Command in TWRP to look at /proc/last_kmsg:

$ cat /proc/last_kmsg

It's even easier if you have a device with TWRP/MultiROM installed since you have that ROM selector right after the boot loop, and you can choose to boot into recovery right from there.

It's probably too early for there to be adb logs as you said, but you can try and adb shell in as soon as possible too. If this is a userdebug build then adb should be on by default and you may be able to get in.

[chev droid]

I'll flash again twrp (currently stock recovery installed) and will try to get some logs for you!

[chev droid]

Please find attached the kmsg.log

Looks like a kernel error for me. (Didn't really analysed the log that much, because it's already midnight here :D )

cheers

chev

[Preetam]

Thanks Chev!!

[    0.487884] Unable to handle kernel paging request at virtual address 34797474
[    0.488098] pgd = c0004000
[    0.488403] [34797474] *pgd=00000000
[    0.488708] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[    0.488891] CPU: 2    Tainted: G        W     (3.4.0-g12ac319-dirty #1)
[    0.489227] PC is at kmem_cache_alloc_trace+0x68/0x1b4
[    0.489410] LR is at con_insert_unipair+0xa0/0xec
[    0.489715] pc : [<c0125844>]    lr : [<c0347458>]    psr: 20000013
[    0.489715] sp : e4945ed8  ip : 00000003  fp : c0fb56f4
[    0.490173] r10: 00000001  r9 : 00000080  r8 : c0347458
[    0.490356] r7 : c0f32940  r6 : 000000d0  r5 : e4900200  r4 : 34797474
[    0.490661] r3 : 00000000  r2 : 03ff2000  r1 : 00000266  r0 : e4944000
[    0.490844] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    0.491149] Control: 10c5787d  Table: 8020406a  DAC: 00000015

Yup, looks like a classic kernel oops to me. And doesn't look like it's anything related to maru.

@Tyler I think something may be wrong with the kernel you built... Which branch did you use?

Good night chev and thanks again for the log diving!!

[chev droid]

Good Afternoon guys (or probably night for you) ;)

msm-gpio-regulator: probe of msm-gpio-regulator.174 failed with error -22
[    0.242950] saw_probe: id=0, name=8921_s5
[    0.243316] saw_probe: id=1, name=8921_s6
[    0.243682] saw_probe: id=2, name=8821_s0
[    0.244049] saw_probe: id=3, name=8821_s1
[    0.252197] Sensors:DSPS: initial dsps.
[    0.253204] [ELAN] Touch dirver register
[    0.253601] persistent_ram: found existing buffer, size 25709, start 25709
[    0.342742] console [ram-1] enabled
[    0.343353] apq8064_init_fb: lcd_type=0
[    0.343566] apq8064_init_fb: register mipi_JDI_panel_device
[    0.344970] msm_gpiomux_install: write failure: -22
[    0.345092] msm_gpiomux_install: write failure: -22
[    0.345214] msm_gpiomux_install: write failure: -22
[    0.345336] msm_gpiomux_install: write failure: -22
[    0.345428] msm_gpiomux_install: write failure: -22
[    0.345642] msm_gpiomux_install: write failure: -22
[    0.346557] Registering gpio keys
[    0.346771] Reconfigure VOL_UP(GPIO155) and VOL_DOWN(GPIO189) with PMIC
[    0.347015] 8921_l17: Failed to create debugfs directory
[    0.348937] ------------[ cut here ]------------


found something similar here: (marked error with gpioregulator)
https://forum.cyanogenmod.org/topic/85914-stuck-on-google-logo-after-compilation/

Here what they found out:

" The problem was that $ ./get-prebuilts step wan't completed properly."


This maybe gives a hint to the source of the problem. (error is not exactly the same as mine)

[Tyler Martin]

It's either android-msm-flo-3.4-lollipop-mr1.1 or android-msm-flo-3.4-lollipop-mr1.2. I can't remember exactly. I don't think I ran into any error at all.

[Tyler Martin]

Hey @Preetam,

Attempting to get things moved over to Nougat. Not really having too many issues getting things merged. Had 3 quick questions for you. Since this really isn't official Maru, I understand if you don't have time to check it out.

1) There is no dashboard_categories.xml in packages/apps/Settings/res/xml anymore. I've been trying to find the commit that changed that around but haven't been able to locate it. I didn't know if you had a suggestion or ran into that with attempts with marshmallow.

2) Regarding frameworks/base/core/java/android/app/ContextImpl.java They removed all the registerService stuff and I can't seem to find it or a commit for it as of now.

3) Does this look okay? 

Thanks for any tips!

On Saturday, September 3, 2016 at 1:10:30 PM UTC-4, Preetam wrote:

[Preetam]

On Thursday, September 8, 2016 at 10:01:13 PM UTC, Tyler Martin wrote:

Hey @Preetam,

Attempting to get things moved over to Nougat. Not really having too many issues getting things merged. Had 3 quick questions for you. Since this really isn't official Maru, I understand if you don't have time to check it out.

1) There is no dashboard_categories.xml in packages/apps/Settings/res/xml anymore. I've been trying to find the commit that changed that around but haven't been able to locate it. I didn't know if you had a suggestion or ran into that with attempts with marshmallow.

 
Did not run into this with M since M still has it. Did some git searching and looks like this commit was the main one: https://github.com/android/platform_packages_apps_settings/commit/4da79e088f9e8d9c6123fbbb7590c779e280c893. Big refactor there so you'll have to dig in to see how the settings tiles are implemented in N.

2) Regarding frameworks/base/core/java/android/app/ContextImpl.java They removed all the registerService stuff and I can't seem to find it or a commit for it as of now.

Service registration was refactored in M and has already been merged appropriately on maruos/.../frameworks/base master. Please use latest on master.

 

3) Does this look okay? 

Not sure what the context is here? Looks like Display.java to me and superficially looks OK.

[Tyler Martin]

Trying to get a build for the Nexus 7 2013 again

@Preetam

I rebuilt everything and recorded logs. Would you mind taking a look at them? Here's the one when I compiled the kernel and this is the one for compiling the rom.

@chev

Here's a new system.img and boot.img for the Nexus 7 2013

[Preetam]

@Tyler Thanks for rebuilding everything!

I took a quick look at the logs and everything looks OK...except I don't see the vendor files being pulled in for flo?

 

including ./vendor/asus/fugu/proprietary/app/Android.mk ...
including ./vendor/asus/fugu/proprietary/framework/Android.mk ...
including ./vendor/asus/fugu/proprietary/priv-app/Android.mk ...
including ./vendor/asus/grouper/proprietary/Android.mk ...
including ./vendor/asus/tilapia/proprietary/Android.mk ...
including ./vendor/broadcom/grouper/proprietary/Android.mk ...
including ./vendor/broadcom/manta/proprietary/Android.mk ...
including ./vendor/broadcom/tilapia/proprietary/Android.mk ...
including ./vendor/invensense/grouper/proprietary/Android.mk ...
including ./vendor/invensense/tilapia/proprietary/Android.mk ...
including ./vendor/maruos/Android.mk ...
including ./vendor/nvidia/grouper/keymaster/Android.mk ...
including ./vendor/nvidia/grouper/proprietary/Android.mk ...
including ./vendor/nvidia/shield_common/proprietary/vendor/app/ConsoleUI/Android.mk ...
including ./vendor/nvidia/tilapia/keymaster/Android.mk ...
including ./vendor/nvidia/tilapia/proprietary/Android.mk ...
including ./vendor/widevine/grouper/proprietary/Android.mk ...
including ./vendor/widevine/manta/proprietary/Android.mk ...
including ./vendor/widevine/tilapia/proprietary/Android.mk ...

I would expect to see something like "including ./vendor/asus/flo/...".

Missing the graphics drivers in particular would explain why @Chev's device boot-looped right after the bootloader logo.

Can you double-check you have downloaded and extracted the vendor files from https://developers.google.com/android/nexus/drivers#flolmy48m?

[Tyler Martin]

That's really weird. They are definitely in vendor/asus folder.

EDIT: Figured it out. device.mk was point to vendor/asus/flo/device-vendor.mk (which doesn't exist) instead of vendor/asus/flo/flo-vendor.mk. I'll have a new build to test tomorrow.

[Falo Yeh]

Am Freitag, 16. September 2016 23:08:00 UTC+2 schrieb Tyler Martin:

That's really weird. They are definitely in vendor/asus folder.

EDIT: Figured it out. device.mk was point to vendor/asus/flo/device-vendor.mk (which doesn't exist) instead of vendor/asus/flo/flo-vendor.mk. I'll have a new build to test tomorrow.

@ Tyler

Is there any new build you want someone to test? I have a device available and happy to give it a try, just in case.


 

[Ramanathan Balakrishnan]

@Tyler Me too having a device and happy to try if you have a build

[Tyler Martin]

@falo and @Ramanathan - Looks like I got the vendor files pulled in but it's still boot looping. I rebuilt the kernel. If it boots, I'll send you a download link.

[Tyler Martin]

@Preetam - 

I don't know what it is but I can't this to boot for the Nexus 7 2013 (flo). It just bootloops on the Google logo. Since I got the vendor files to load, I'm assuming it's definitely a kernel issue. I don't know what else to do. I think I got a booting kernel for the Nexus 7 2012 the first try.

Quick question regarding kernel config. It looks like you only have CONFIG_CGROUP_DEVICE=y, CONFIG_CPUSETS=y, CONFIG_DEVTMPFS=y, CONFIG_DEVPTS_MULTIPLE_INSTANCES=y and CONFIG_NAMESPACES=y in your kernel for the Nexus 5. Do I only need those 5 or all 9 you have listed on the kernel wiki?

[Preetam]

@Tyler

Can you try compiling the kernel with the stock defconfig and seeing if you still get the bootloop? It is possible that the flo kernel has some incomplete patches for the Maru-specific options. If the stock defconfig causes no issues then we can narrow it down to the Maru options. Maru will still boot off of the stock kernel (provided it's been built correctly of course)--you just won't be able to start the desktop.

The options you listed are the ones enabled in the minimized config (defconfig), which should automatically enable the other CONFIG_*_NS options. Basically, all you need are those 5 if you are adding them to the flo stock defconfig. I've updated the wiki so it's not confusing.

Also which version of Maru are you building? master? master is now on Marshmallow so make sure to use the marshmallow kernel branch.

[Tyler Martin]

@Preetam

I'll give that a try and see if it boots.

I'm currently on 0.2.4. I'll be switching to 0.3 after I get it booting.

[Lucien Begert]

@Tyler Martin @Preetam

Great Project! I Just joined, and want to help out on porting to N7 (possibly more). I am just wondering on progress.

Also not sure about the structure to have in order to create a flo debug (and user) entry in lunch and to separate the hammerhead binaries from the flo ones.

Also, how would I proceed in creating an alternative lxc container with ubuntu instead of debian for example? Where would I be able to add this?

Anyone can guide me how to do this?

Thanks,
Lucien

[Tyler Martin]

@Lucien

I have it up and running for the 2012 Nexus 7 (Grouper). Still trying to get it to boot on 2013 Nexus 7 (flo). 

Adding items to lunch is inside the vendorsetup.sh file located in vendor/maruos.

The last thing would be a preetam question.

[Preetam]

@Lucien

Regarding adding an alternative lxc container: please take a look at https://github.com/maruos/blueprints. Maru OS uses blueprint plugins to build root filesystems that are used to launch LXC containers. The README describes how you can add your own blueprint (for ubuntu or any other Linux variant). Each blueprint has a subdirectory where any scripts and configuration files are stored for that blueprint. The best way to understand how blueprint plugins work is to look at the debian blueprint that builds Maru Desktop: https://github.com/maruos/blueprints/tree/master/blueprint/debian. There are essentially two scripts: plugin.sh (entry point to each blueprint) and chroot-configure.sh that are responsible for building the container. I would just copy the debian directory as a starting point and then tweak it to install ubuntu instead.

[Tyler Martin]

@preetam

I've made some progress. I have both Lollipop and Marshmallow booting with stock kernels. I just got a marshmallow kernel built with the minimal configs and it boots. It fails to start Maru Desktop. I've attached a logcat.

[Dionis L]

Can you post the logs from the debian ?

[Tyler Martin]

I can't get debian started.

[Dionis L]

if you have  root on android you can access the debian partition , is in /system/data ... somewhere  and maybe you can go into debian /var/logs , and check what it say

[Preetam]

@Tyler Thanks for the new builds! I believe the desktop fails to start because this is the stock kernel after all. Can you try building a kernel with the Maru OS options enabled one at a time and testing to make sure you can boot the device? This way we can diagnose which exact config option(s) was causing the earlier kernel boot failure, and see how we can fix it.

[Tyler Martin]

@Preetam It's failing with a kernel that has the Maru OS options enabled. I can rebuild to make sure.

[Preetam]

Ah ok, I thought these were the stock kernels. That's good if you were able to get the kernels to boot fine with the Maru options enabled!

Let's see what's going on with the desktop then. One thing to try really quickly is to do a userdebug build and start the desktop container directly from a root shell:

root@hammerhead# lxc-start -n jessie

You should immediately see some error logs that will help diagnose the problem. Please paste the logs and we can go from there.

[Tyler Martin]

I'll give that a go right now. 

Btw...this is one of the java errors I get. If I switch to 8, then it tells me 1.7.x is needed. Don't have the cm commit that I cherry picked to fix it.

============================================

Checking build tools versions...

************************************************************

You are attempting to build with the incorrect version

of java.

 

Your version is: java version "1.7.0_95" OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-3) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode).

The required version is: "1.8.x"

 

Please follow the machine setup instructions at

build/core/main.mk:171: *** stop.  Stop.

    https://source.android.com/source/initializing.html

************************************************************

#### make failed to build some targets (18 seconds) ####

[Tyler Martin]

Here's the output

root@flo:/ # lxc-start -n jessie

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/start.c: must_drop_cap_sys_boot: 554 failed to clone (0x20000011): Invalid argument

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/namespace.c: lxc_clone: 67 failed to clone (0x2c020000): Invalid argument

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/start.c: lxc_spawn: 894 Invalid argument - failed to fork into a new namespace

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/start.c: __lxc_start: 1080 failed to spawn 'jessie'

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/lxc_start.c: main: 342 The container failed to start.

lxc-start: /media/data/Android/Maru_Marsh/external/lxc/src/lxc/lxc_start.c: main: 346 Additional information can be obtained by setting the --logfile and --logpriority options.

On Sunday, November 13, 2016 at 7:04:05 PM UTC-5, Preetam wrote:

[Preetam]

OK, cool, LXC is unable to fork into a new namespace. It looks to me like this is a missing config option in the kernel. 

I stalked you on GitHub and looks like I found the defconfig you are using, is this it: https://github.com/TMartinPPC/maru_kernel_flo/blob/master/arch/arm/configs/maru-flo_defconfig ?

If that is the one you are building with, you will need to delete the following lines to enable the necessary namespaces:

# CONFIG_UTS_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_NET_NS is not set

This is why I had them explicitly listed in the wiki on building the kernel earlier, they are selected by default in the defconfig with CONFIG_NAMESPACES=y unless there is a line like "# CONFIG_* is not set". So your kernel is currently being build without UTS, PID, or NET namespaces which are needed for Maru OS, resulting in the lxc errors you see.

You will also need to add this option since it has been removed from AOSP kernels from Marshmallow onwards (wiki is updated with this):

CONFIG_SYSVIPC=y

I sent you a pull request with these changes to make it easy, check it out: https://github.com/TMartinPPC/maru_kernel_flo/pull/2. I also cherry-picked a tiny patch to fix the kernel build when CONFIG_PID_NS is set: https://github.com/maruos/android_kernel_msm/commit/9cd79909941cd1411ffb13452c2ee2522350accc. I was able to successfully build the kernel with this, but can't actually test it.

Go ahead and build the kernel with my updated defconfig and patch, and try another build with the new kernel. Let me know what happens, including the lxc errors if there is still an issue.

Hopefully we get one step closer with this, thanks for keeping at it!

[Dionis L]

Dear Preetam ,

I 'm building for LG G4 , lg instruciton to compile android  say , I have to download orriginal android 6 from google and ,untar some files over it (files from lg).

- Download original android source code ( M 6.0 ) from http://source.android.com
  - Untar opensource packages of LGH815_Android_MOS_V20i.tar.gz into downloaded android source directory
       a) tar -xvzf LGH815_Android_MOS_V20i.tar.gz
  - Run following scripts to build android
    a) source build/envsetup.sh
    b) lunch 1
    c) make -j4

I've downloaded original android from google , I untared oer it , the files from all .And all looks fine .
I'm trying first to build it fallowing the isntruction from them so me to be sure all code from LG compile ok.
All looks good with compilation for now.
My question is : when I need to compile maru , they say do lunch 1 ,but mauru say to do a lunch 23 .
If I will do lunch 1 , will lxc and all data mauru needs included?

Or is better just to untar the source from LG , over the source of maru ?
I think source from LG do not overwite files that you modified .
Thank you

[Preetam]

Let's move this conversation over to your LG G4 thread so we can follow it more easily. See my post here: https://groups.google.com/d/msg/maru-os-dev/-K_lysxngD4/xdJFqZooBgAJ. Please post in that thread for any follow-up questions.

[Tyler Martin]

That did it!!!! I was able to get into Debian. I didn't realize I needed to remove those lines. 

Are you using make dist -j# instead of the normal make -j# to get a flashable zip?

[Dionis L]

OK that's rock! Contrats you have a working debian!
I thinked 100 times , who will be the firs who will finish at least 1 port ,I saw nobody advertised a positive result , so I started myself to work at it but seams you did it before me ;)
That;s cooooool!

[Preetam]

AWESOME! Debian is working over HDMI too?

Yeah, you can do a "make dist" for the flashable update zip.

[Tyler Martin]

Yep. Working over HDMI. Thanks for all your help. Anyway to have it so that the screen switches to always on when maru desktop is on?

Sweet. I'll give that a go.

[Preetam]

Np, really really glad to have Maru running on another device! Thank you for your perseverance!

If you are connected to power while using HDMI, you can enable Daydream mode, which will keep the screen powered on. This is the default behavior on the official builds for the Nexus 5.

You can add this overlay from the hammerhead repos to make daydream enabled by default: https://github.com/maruos/android_device_lge_hammerhead/blob/master/overlay_maru/daydream/frameworks/base/core/res/res/values/config.xml

You will also need to add it to DEVICE_PACKAGE_OVERLAYS in maru_flo.mk: https://github.com/maruos/android_device_lge_hammerhead/blob/master/maru_hammerhead.mk

I think I tred to move those overlays to vendor_maruos so they would automatically be used but it didn't work and they need to be included in the device mk itself.

[Dionis L]

Is was good you fallowed the same goole instruction regarding the blobs , but for me at Lg G4 , It seams I have all I need but i do not kmnow exactly how to set up the blobs ,or if the source from lg taht I put over maruos , will bring that blobs .But i'm tring to read and read and read ....lol

[Ramanathan Balakrishnan]

So is the next step to create an easy installer for flo? I want to understand more about the easy installer, as to how it unlocks bootloader and how it flashes ROM, is there somewhere i can read about this?

Tyler, was curious how you were testing it in the device without the flashable zip? Asking this coz i'm also interested in building os from scratch, just for learning, and try it out in my device

On Wed, Nov 16, 2016 at 9:55 AM, Dionis L <diana...@gmail.com> wrote:

Is was good you fallowed the same goole instruction regarding the blobs , but for me at Lg G4 , It seams I have all I need but i do not kmnow exactly how to set up the blobs ,or if the source from lg taht I put over maruos , will bring that blobs .But i'm tring to read and read and read ....lol

--
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/zdT_qHydRXA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maru-os-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/maru-os-dev/c63df417-9f8b-4d71-860d-e856c14e5f92%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Tyler Martin]

When you compile with make -j#, it creates boot.img and system.img inside an out folder (actually out/target/product/flo). When you're bootloader is unlocked, you can boot your device to bootloader and use fastboot to flash partitions.

I'll be providing a zip file that you can flash in a custom recovery like TWRP. A Nexus device is pretty simple to unlock and flash custom recovery.

On Wednesday, November 16, 2016 at 12:43:55 AM UTC-5, Ramanathan Balakrishnan wrote:

So is the next step to create an easy installer for flo? I want to understand more about the easy installer, as to how it unlocks bootloader and how it flashes ROM, is there somewhere i can read about this?

Tyler, was curious how you were testing it in the device without the flashable zip? Asking this coz i'm also interested in building os from scratch, just for learning, and try it out in my device

On Wed, Nov 16, 2016 at 9:55 AM, Dionis L <diana...@gmail.com> wrote:

Is was good you fallowed the same goole instruction regarding the blobs , but for me at Lg G4 , It seams I have all I need but i do not kmnow exactly how to set up the blobs ,or if the source from lg taht I put over maruos , will bring that blobs .But i'm tring to read and read and read ....lol

--
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/zdT_qHydRXA/unsubscribe.

To unsubscribe from this group and all its topics, send an email to maru-os-dev...@googlegroups.com.

[Preetam]

Hi Ramanatham, If you're interested in the easy installers, please take a look at this GitHub repository: https://github.com/maruos/installer. This contains the easy installer scripts for Linux, Mac, and Windows that are bundled with the official Maru OS releases. Basically, the easy installer zip files released for Maru OS bundle together an installer script, with recovery, system, and boot images. These images are flashed via fastboot (including bootloader unlock on Nexus devices).

Also, once Tyler gets his build tested out and it's proven to be pretty stable, I can go ahead and integrate his work with the official Maru OS builds, and they will be bundled with the easy installers just like on the current hammerhead builds.

[Dionis L]

How did you create boot.img after you compiled the kernel ?
I want to try to flash first time just system.img .will my stock kernel boot it ?

[Dionis L]

i send just system image :

fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [  0.716s]
sending sparse 'system' (490211 KB)...
OKAY [ 12.161s]
writing 'system'...
OKAY [  8.714s]
sending sparse 'system' (514659 KB)...
OKAY [ 12.551s]
writing 'system'...
OKAY [  7.108s]
sending sparse 'system' (163339 KB)...
OKAY [  4.056s]
writing 'system'...
OKAY [ 28.382s]
finished. total time: 73.690s

Device try to boot , but it soon reboot and TWRP recovery apper.
I did not send also boot.img for kernel , just system.img .
Does it not boot by default if I use the stock kernel?

[Tyler Martin]

It probably won't boot with a stock kernel. It might boot with one of the aosp kernels if the system is right.

[Tyler Martin]

Would anyone with a Nexus 7 like to test? Here's something you can flash in recovery. For whatever reason, it seems to replace recovery but you can easily reflash your custom recovery.

https://drive.google.com/open?id=0ByR5uBE8p7qmQkdoMEYya1QxZ2c

[chev droid]

Hi guys,

looks like a similiar error which i've got in the beginning of this thread, tablet boots, google logo appears and then reboots. If I remember correctly (haven't done much stuff the last month) Preetam said that the system won't boot with a stock/aosp kernel, or back then we had the same problem?


EDIT: didn't saw the last post :) I'll gladly flash it today and give it a try !

[Tyler Martin]

I think he's talking about his LG G4 build.

[chev droid]

Probably I may didn't read it properly^^

also saw your link with the image to flash after i posted my previous answer, I will flash it today on my n7 and give it a try, you made great progress so far with the port awesome!!

[Dionis L]

Yes , the boot problem was about my Lg ,Sorry I had to post that in other thread.

Any way ,taht eror is strange I will recompile all now from begining  I also tried with a aosp kernel from somebody who compiled aosp for H815  ,and error is same .
It may be because I have mixed some  different directories from different android versions in frameworks folder .
I'm not sure but I startd any way from begining , without to mix aything.
I will check now to be sure from begining i have version android-6.0.1_r72

[Lucien Begert]

Cool guys, thanks for the tips/hints! I will try. Also thanks for the update zip, I will try it with multirom tonight and give feedback. Great advancement :)

[Tyler Martin]

I have no idea if this will work with multirom. I'm familiar with what multirom does but not sure if I would need to make any changes to make this compatible.

[Dionis L]

is device/lge/hammerhead-kernel/   needed when compile kernel ? I do not have one for lg g4.

and how did oyu created the boot.img ?

[Tyler Martin]

Mine is created from the kernel located in that hammerhead-kernel. We can do something similar for your device but we're going to have to change the device tree.

[Dionis L]

Kernel Build  
  - Uncompress using following command at the android directory
        a) tar -xvzf LGH815_Kernal_MOS_V20i.tar.gz

  - When you compile the kernel source code, you have to add google original prebuilt source(toolchain) into the android directory.
  - Run following scripts to build kernel
    a) cd kernel
    
    1) H815
        make ARCH=arm64 p1_global_com-perf_defconfig
        make ARCH=arm64 CROSS_COMPILE=../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- -j4
        
    * "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
  - After build, you can find the build image(Image.gz) at arch/arm64/boot

THis are the instruction from lg to build the kernel , they  give kernel source too .
I will try to build the kernel in his own directory but I do not undestand how to convert Image.gz into boot.img ?

[Lucien Begert]

Works perfectly fine! Multirom works,bluetooth devices work, iceweasel extensions as well.

Only issue I had was upon initial boot after flashing zip, the desktop would not run, neither automatically nor manually. However after a full reboot this worked!

Bravo! :) Well done!

[chev droid]

Same here working fine!!

Had no problem with booting the desktop automaticly after install, but my Nexus 7 shutdown (0% power, booted back up again 100% after a few minutes again 0% and shutdown) and com.qualcomm.timeservice sometime crashes.

Just let me know if I sould deliver any logfiles for debugging.

[Tyler Martin]

Awesome! That's great to hear! And did you load it as a secondary rom?

[Lucien Begert]

Yep! As Secondary! Oh and yes got that qualcomm time error as well, I think it's linked to network, as I only got it once I connected to WiFi.

[Dionis L]

I resync with repo ,but your manifest do not give latest version of platform_frameworks_base , i think is the one from android 5 , i had to get it from maru os using git clone https://github.com/maruos/android_platform_frameworks_base  . It still compile I wait to test it if at least boot for the LG

[Tyler Martin]

Latest version doesn't always mean stable version. I just grabbed a device tree from CyanogenMod so I'll see if I can get something built using it.

[Dionis L]

No , not the device .The device is great. thank you! , problem is when i do repo with your manifest it give me a different and old android platform frameworks base , so I had to do a git clone https://github.com/maruos/android_platform_frameworks_base 

[Falo Yeh]

Am Donnerstag, 17. November 2016 15:46:03 UTC+1 schrieb Tyler Martin:

Would anyone with a Nexus 7 like to test? Here's something you can flash in recovery. For whatever reason, it seems to replace recovery but you can easily reflash your custom recovery.

https://drive.google.com/open?id=0ByR5uBE8p7qmQkdoMEYya1QxZ2c

I have a Nexus 7 2013 (LTE) - deb, your build is for Nexus 7 2013 (WiFi) - flo. I tried both methods, install Zip via recovery and Multirom but both fails being the Zip is for flo and not deb device. 

Would it be possible to build for deb too?

Thanks!

[Tyler Martin]

I think so. Give me a few days.

[Dionis L]

Hello , how did you get past this ?
I have it running in my LG , I ca connect to adb , but nothing on display yet .
I just see this error in logs :
SurfaceFlinger: hwcomposer module not found

I do not know why this  hwcomposer is missing , any ideeas?

[Tyler Martin]

Try this

On Thursday, November 17, 2016 at 7:06:09 PM UTC-5, Falo Yeh wrote:

[Dionis L]

I have succeded to compile Slim6 rom (a aosp based rom ) using the devices from CM 13 .
I have a android that looks like AOSP . All works except slimport lol.Kernel detect it but android do not knows how to use it .Or something like this i read problem can be because of hardware/qcom/display . Maybe this custom roms use a too old dir .I do not know . But is bad slimport do not works . All other works even double tap to wake up .

[Falo Yeh]

Am Samstag, 26. November 2016 06:00:39 UTC+1 schrieb Tyler Martin:

Try this

Marvelous!! Thank you Tyler!

I tried it both methods, Multirom and standalone. Unfortunately, it does not pass the Google logo screen. It sits there forever with both methods.

Any idea what could went wrong?


 

[Dionis L]

If your boot animation keep animating , it seams linux kernel started ok , but for some reason some android services fail to start . You have to connect to your device using adb and run :logcat .
But to connect using adb , you have to instal a custom recovery and use that custom recovery to add some parameteres to build.prop to make adb to start .

[Tyler Martin]

If it's looping at the Google screen, that sounds like kernel. That's odd because the LTE and wifi variants use the same kernel and that same kernel boots on my wifi Nexus 7. Let me upload a build that has the stock kernel to see if it boots.

[Tyler Martin]

Would you mind trying this? It's the same build but with a completely stock kernel. Won't be able boot into debian but just want to see if the rom will boot.

[Dionis L]

What you see in dmesg ,kernel logs , when you attach hdmi out cable?In adb ?

[Falo Yeh]

Am Montag, 28. November 2016 18:41:36 UTC+1 schrieb Tyler Martin:

Would you mind trying this? It's the same build but with a completely stock kernel. Won't be able boot into debian but just want to see if the rom will boot.

Thanks Tyler. 

There is no difference with that new build. The Zip flashes fine. I trigger a reboot and the google logo appears. It never passes that screen. It just sits their endless. Must be very early in the boot process. I have no idea how to debug further at this stage. 

The device is sane, I mean I can flash a factory image and it comes up successfully.

[Falo Yeh]

Am Montag, 28. November 2016 21:37:05 UTC+1 schrieb Dionis L:

What you see in dmesg ,kernel logs , when you attach hdmi out cable?In adb ?

No idea if at that stage (google logo) something useful being written somewhere. 

I have never customized build.prop to add something for further debug. Once the device it at that google logo, I can just power off. Would a reboot into recovery allow to collect files post mortem for further trouble shooting?

[Dionis L]

yes , like I writed in a previous post . Your linux kernel boots , but some android services fail to start .
You have to install twrp recovery and boot into that recovery , you can google how to install this .
Then while you are in twrp connect using adb and mount /system from twrp .
Then go from your pc adb go to /system and do this:

echo "">> build.prop
echo "persist.service.adb.enable=1" >> build.prop
echo "persist.service.debuggable=1" >> build.prop
echo "persist.sys.usb.config=mtp,adb" >> build.prop


so your /system/build.prop will have that lines in it .
Then you can restart ant let it boot normaly .

You can now connect using adb to your phone and run logcat , or dmesg and see why it can not boot.

[Falo Yeh]

Thank you! Great, let me try that.. I do have TWRP installed 

[Falo Yeh]

Done the above but getting the below error:

$ adb shell

error: device unauthorized. Please check the confirmation dialog on your device.

$ adb devices

List of devices attached 

0922b320 unauthorized

Any hint how to avoid that error?

[Falo Yeh]

FYI.. the below fixed the above error, let me try if I can get collect something useful for you now

 cd ~/.android

adb push adbkey.pub /data/misc/adb/adb_keys

[Dionis L]

ok ,that 's great . You can now check live logs and see what's going on

[Falo Yeh]

Am Dienstag, 29. November 2016 00:31:20 UTC+1 schrieb Dionis L:

ok ,that 's great . You can now check live logs and see what's going on

Flashed 1st deb build, amended build.prop and collected a "adb logcat 2>&1 > logcat.maru_deb-ota-eng.tmartin" output right from the beginning. Output file attched

[Dionis L]

Your main problem is here:

11-29 00:33:35.200   442   442 I SurfaceFlinger: SurfaceFlinger is starting
11-29 00:33:35.201   442   442 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
11-29 00:33:35.201   442   442 F libEGL  : couldn't find an OpenGL ES implementation
11-29 00:33:35.201   442   442 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 442 (surfaceflinger)

I think you have a diferent device from the one rom was build for , The rom must be build with the "device tree"  for your specific device

[Tyler Martin]

Pretty sure vendor files didn't get pulled in and that was causing the issue. Here's a new build.

https://drive.google.com/open?id=0ByR5uBE8p7qmQXI2U1hFMmI2TjA

[Falo Yeh]

Am Dienstag, 29. November 2016 22:32:40 UTC+1 schrieb Tyler Martin:

Pretty sure vendor files didn't get pulled in and that was causing the issue. Here's a new build.

Bingo, its booting maru os now. I will let you know how it goes with maru os on Nexus 7 2013 (LTE). Marvelous! 

Thank you both!

[Tyler Martin]

Awesome! Let me know how it goes.

[Preetam]

Nice work guys! Happy to see all these N7 builds coming along!

[chev droid]

@ Falo Yeh  just wanted to ask if the last build from Tyler worked on your Nexus 7 LTE (deb)?

If yes, we can change the "status" from in development to port working, which would be awesome.

[Preetam]

Just pushed up a --minimal option to the debian blueprint that you can use to build for the N7. It results in a desktop image ~332MB. More details: https://github.com/maruos/blueprints/commit/e0a9a3503ad4e117a4baa7569732de216fee9085

Build it by passing either "-m" or "--minimal" as a blueprint option:

$ sudo ./build.sh -n jessie -- --minimal

Please give this a try within your docker container and let me know if it fits on your N7 builds! This moves us one step closer to officially supporting the N7.

If anyone else needs a slim desktop build for a device with limited system space, give this a try!