#Moving over from "Device Porting Thread"#
I should have mentioned. Display link works just fine with the nexus 6p. That was my plan for the port
okay good to know the 6p supports at least Displaylink, I didn't find any
HDMI-Out support, since it uses usb 2.0 with just the usb-c type connector not
usb 3.0 or 3.1.
The only bad thing about display link is, you need special hardware, even on the display/monitor side (or a dock/adapter) to get it work. But if it really support displaylink it would be amazing!
Another cool protocoll which hopefully future phone'll support is thunderbolt 3, which uses the usb-c connector. You could connect up to two 4k monitors and deliver up to 100 watts of power :)
I have a USB type c to USB 2.0 adapter. I also have a display link
adapter I plug that into. And this combination with the display link driver
from the play store allows me to hook my phone up to a moniter. Here is a link.
One downside right now is that the nexus 6p does not support being in USB host mode while also charging. A possible fix to this would be to add ACA_host mode to the kernel. I believe there is an aca_host mode path for the nexus 7 kernel. I may look into porting this over in the future.
Anyways, when I get a chance either today or this weekend. I'll move all of this over to a nexus 6p porting thread.
This will allow you to use mmma.
I've gotten this to compile and boot, however I am getting msm driver errors in my dmesg. Ill work on fixing these probably tomorrow.
prebuilts/clang/linux-x86/host/3.6/bin/clang++: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directorymake: *** [build/core/binary.mk:706: out/host/linux-x86/obj/EXECUTABLES/validatekeymaps_intermediates/Main.o] Error 127make: Leaving directory '/home/pheoxy/maruos'#### make failed to build some targets (54 seconds) ####
including ./vendor/maruos/Android.mk ...*** Overlay change detected, clean shared intermediate files...*** rm -rf out/target/common/obj/APPS/SystemUITests_intermediates out/target/common/obj/APPS/Contacts_intermediates out/target/common/obj/APPS/framework-res_intermediates out/target/common/obj/APPS/Settings_intermediates out/target/common/obj/APPS/Bluetooth_intermediates out/target/common/obj/APPS/Telecom_intermediates out/target/common/obj/APPS/TeleService_intermediates out/target/common/obj/APPS/SettingsProvider_intermediates out/target/common/obj/APPS/SystemUI_intermediatesPRODUCT_COPY_FILES device/generic/goldfish/data/etc/apns-conf.xml:system/etc/apns-conf.xml ignored.No private recovery resources for TARGET_DEVICE anglerbuild/core/tasks/vendor_module_check.mk:70: *** Error: vendor module "libperspective" in vendor/maruos/perspective with unknown owner "" in product "aosp_angler". Stop.make: Leaving directory '/home/pheoxy/maruos'#### make failed to build some targets (31 seconds) ####
No activity anymore, are you still working on this or is it not possible to get MaruOS on the Nexus 6p?
I ask this because i have found a good priced second hand Nexus 6p but the seller doesn't want to wait.
When i can buy it, i become a tester.
But then i need fast an answere that MaruOS will work the upcoming months on the N6p.
I switch from ios to android special for MaruOS.
I just started working on the port again. And I have maruos and the kernel built and booting on my nexus 6p. I have not been able to test out if lxc is launching and posting properly to hdmi. I will test this feature when I get back to my workstation tonight.
Now that my schedule is not as hectic, I plan on spending much more time on this project.
"This allows containers, i.e. vservers, to use user namespaces to provide different user info for different servers."