#Moving over from "Device Porting Thread"#
bootlessxfly
I should have mentioned. Display link works just fine with the nexus 6p. That was my plan for the port
chev
droid
@bootlessxfly
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.
http://www.displaylink.com/downloads/android
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.
Regards
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."
cp ../kernel/msm/arch/arm64/boot/Image.gz-dtb device/huawei/angler-kernel
/Image.gz-dtb
Thanks for the tips. I do not have an nexus 5 device. I can try to grab a prebuilt image (or go ahead and build one) and extract it out of the system.img. If you have them available, do you think you could upload them?
--
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/3KxiW2ZVlQU/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/afd4a93e-9538-477f-ab47-e84f9c1915dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
+ test -d autom4te.cache
+ rm -rf autom4te.cache
+ aclocal -I config
+ autoheader
+ autoconf
+ automake --add-missing --copy
mkdir -p /media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler/obj/lxc && cd /media/chris/7A52302E3B535583/project-files/m
aru/out/target/product/angler/obj/lxc && \
cp -r /media/chris/7A52302E3B535583/project-files/maru/external/lxc/config /media/chris/7A52302E3B535583/project-files/maru/out/target/product/
angler/obj/lxc && \
/media/chris/7A52302E3B535583/project-files/maru/external/lxc/configure \
--host=arm-linux-androideabi \
--bindir="/system/bin" \
--libdir="/system/lib64" \
--disable-api-docs \
--disable-capabilities \
--disable-examples \
--disable-lua \
--disable-python \
--disable-bash \
--enable-configpath-log \
--prefix=/system/maru/lxc \
--with-runtime-path=/cache/ \
--with-config-path=/data/maru/containers/ \
CFLAGS="-nostdlib -Bdynamic -pie \
-fno-exceptions -Wno-multichar -fno-strict-aliasing -fstack-protector -ffunction-sections -fdata-sections -funwind-tables -Wa,
--noexecstack -Werror=format-security -D_FORTIFY_SOURCE=2 -fno-short-enums -no-canonical-prefixes -fno-canonical-system-headers -mcpu=cortex-a5
3 -include build/core/combo/include/arch/linux-arm64/AndroidConfig.h -I build/core/combo/include/arch/linux-arm64/ -Werror=pointer-to-int-cast
-Werror=int-to-pointer-cast -Werror=implicit-function-declaration -fno-strict-volatile-bitfields -Wno-psabi -DANDROID -fmessage-length=0 -W -W
all -Wno-unused -Winit-self -Wpointer-arith -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -DNDEBUG -O2 -g
-Wstrict-aliasing=2 -fgcse-after-reload -frerun-cse-after-loop -frename-registers -DNDEBUG -UDEBUG -I/media/chris/7A52302E3B535583/project-fil
es/maru/bionic/libc/arch-arm64/include -I/media/chris/7A52302E3B535583/project-files/maru/bionic/libc/include -I/media/chris/7A52302E3B535583/p
roject-files/maru/bionic/libc/kernel/uapi -I/media/chris/7A52302E3B535583/project-files/maru/bionic/libc/kernel/uapi/asm-arm64 -I/media/chris/7
A52302E3B535583/project-files/maru/bionic/libm/include -I/media/chris/7A52302E3B535583/project-files/maru/bionic/libm/include/arm64" \
LDFLAGS=" -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,--build-id=md5 -Wl,--warn-shared-textrel -Wl,--fatal-warnings -Wl,-maarch64lin
ux -Wl,--hash-style=gnu -Wl,--fix-cortex-a53-843419 -Wl,--allow-shlib-undefined \
-Wl,-dynamic-linker,/system/bin/linker \
/media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler/obj/lib/crtbegin_dynamic.o \
-lc -ldl \
-L/media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler/obj/lib \
/media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler/obj/lib/crtend_android.o" && \
make && \
make DESTDIR=/media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler install
checking for arm-linux-androideabi-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-linux-androideabi-strip... arm-linux-androideabi-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... arm-unknown-linux-androideabi
checking for style of include used by make... GNU
checking for arm-linux-androideabi-gcc... arm-linux-androideabi-gcc
checking whether the C compiler works... no
configure: error: in `/media/chris/7A52302E3B535583/project-files/maru/out/target/product/angler/obj/lxc':
configure: error: C compiler cannot create executables
See `config.log' for more details
external/lxc/Android.mk:54: recipe for target 'external/lxc/../../out/target/product/angler/system/lib64/liblxc.so' failed
make: *** [external/lxc/../../out/target/product/angler/system/lib64/liblxc.so] Error 77
make: Leaving directory '/media/chris/7A52302E3B535583/project-files/maru'
#### make failed to build some targets (02:12 (mm:ss)) ####
It must say 2 displayes but say just:
Displays (1 entries)
+ DisplayDevice: Built-in Screen
So until you see in the log that it have 2 displays you can not go next
graphics 591 1 5776 1904 __skb_recv 0000000000 S /system/bin/mflinger (u:3, s:1)
fingerprint=Android/maru_angler/angler:6.0.1/MMB29V/chris12101115:userdebug/test-keys
fingerprint=Android/maru_angler/angler:6.0.1/MMB29V/chris12101115:userdebug/test-keys
03-08 01:56:08.254 - wlan0: 5:IFNAME=wlan0 SET device_name maru_angler -> true
Proc mflinger:
783 kB: mflinger (pid 591)
783 kB: mflinger (pid 591)
root@jessie:~# startxfce4
/usr/bin/startxfce4: Starting X server
(EE)
Fatal server error:
(EE) Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE)
No protocol specified
xinit: giving up
xinit: unable to connect to X server: Resource temporarily unavailable
xinit: server error
/usr/bin/startxfce4: X server already running on display 1
I just changed to an armhf debian, so this log is from that.
I'll include a log for "journalctl -u mclient" but it looks like it fails to start.
It looks like you are right about displaylink showing up as virtual. So displaylink is using a virtual framebuffer to pass this information to the displaylink device? Do you think we could bind maru desktop to this virtual frambebuffer?
Since this virtual framebuffer represents a usb device(being our displaylink adapter), couldn't we post maru desktop to this. Our post would eventually be formed into an actual framebuffer by the adapter to send over hdmi.
I've attached dumpsys logs for both display and SurfaceFlinger
Thanks for the tips.
@Georgian Chituc. I must have confused my self. You can currently get displaylink to work with the app version? Is the app version using something like vnc to view the desktop? I'll go read through the app version thread when I get a chance later.
--
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/3KxiW2ZVlQU/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/bf23aa6f-95f2-4cea-9eb3-d129288aa23c%40googlegroups.com.
Dec 13 00:03:00 jessie systemd[124]: Failed at step EXEC spawning /usr/bin /mclient: No such file or directory
Sorry for the delay. I had lost my usb type c cord and just received a new one today. Good news though. I have been able to build the new chromecast patches without any errors. I also tested this out with my display link adapter and was able to get the linux desktop to post over hdmi.
I am going to post my manifest and an flashable image for people to try to my github pages in the next day or two.
On Thursday, February 9, 2017 at 3:02:39 PM UTC-6, Preetam wrote:I have pushed two "chromecast" branches to frameworks_base and packages_apps_Settings. Please check those out and try a build. Let me know how it goes, especially if you run into any issues.
--
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/3KxiW2ZVlQU/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/fac66a4a-2d97-4187-b5ff-55143f687ab8%40googlegroups.com.
Does phone charge while hdmi is attached over usb c ?
On Feb 22, 2017 6:05 AM, "bootlessxfly" <bootle...@gmail.com> wrote:
Sorry for the delay. I had lost my usb type c cord and just received a new one today. Good news though. I have been able to build the new chromecast patches without any errors. I also tested this out with my display link adapter and was able to get the linux desktop to post over hdmi.--I am going to post my manifest and an flashable image for people to try to my github pages in the next day or two.
On Thursday, February 9, 2017 at 3:02:39 PM UTC-6, Preetam wrote:I have pushed two "chromecast" branches to frameworks_base and packages_apps_Settings. Please check those out and try a build. Let me know how it goes, especially if you run into any issues.
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/3KxiW2ZVlQU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maru-os-dev...@googlegroups.com.
I do not know about wireless charging. Im do not believe the nexus 6p supports Qi charging though.
I have an usb type C to type A adapter that i plug a displaylink adapter into. The hdmi is plugged into the displaylink adpater. This is done with Preetam's chromecast patches as displaylink is also represented as a virtual framebuffer. Hope that answers your question.
On Tuesday, February 21, 2017 at 10:15:25 PM UTC-6, Georgian Chituc wrote:How about wireless charger ? It works if hdmi is attached over type c ?
--
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/3KxiW2ZVlQU/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/22fd3af1-64b7-4e12-82eb-ba455d299809%40googlegroups.com.
Thank you for info . if using displaylink ,there is same 30℅ cpu load like using chromecast?
On Feb 22, 2017 6:21 AM, "bootlessxfly" <bootle...@gmail.com> wrote:
I do not know about wireless charging. Im do not believe the nexus 6p supports Qi charging though.--I have an usb type C to type A adapter that i plug a displaylink adapter into. The hdmi is plugged into the displaylink adpater. This is done with Preetam's chromecast patches as displaylink is also represented as a virtual framebuffer. Hope that answers your question.
On Tuesday, February 21, 2017 at 10:15:25 PM UTC-6, Georgian Chituc wrote:How about wireless charger ? It works if hdmi is attached over type c ?
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/3KxiW2ZVlQU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to maru-os-dev...@googlegroups.com.
I only did a quick check. But I was using 5 - 10 % cpu load. Small spike on startup, then back down to around 5%.
On Tuesday, February 21, 2017 at 10:26:31 PM UTC-6, Georgian Chituc wrote:Thank you for info . if using displaylink ,there is same 30℅ cpu load like using chromecast?On Feb 22, 2017 6:21 AM, "bootlessxfly" <bootle...@gmail.com> wrote:I do not know about wireless charging. Im do not believe the nexus 6p supports Qi charging though.--I have an usb type C to type A adapter that i plug a displaylink adapter into. The hdmi is plugged into the displaylink adpater. This is done with Preetam's chromecast patches as displaylink is also represented as a virtual framebuffer. Hope that answers your question.
On Tuesday, February 21, 2017 at 10:15:25 PM UTC-6, Georgian Chituc wrote:How about wireless charger ? It works if hdmi is attached over type c ?
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/3KxiW2ZVlQU/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/22fd3af1-64b7-4e12-82eb-ba455d299809%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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/3KxiW2ZVlQU/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/d0d12564-aa24-44cb-a3be-111c695921ba%40googlegroups.com.
@bootlessxfly this is great news, let us know anything in particular you want us to break/test....I haven't had time to compile since a really old build and that failed all over, so having an OTA/Zip will be great, plus let me write about it a couple places.
I would love to see @maruos get the coverage that remix hasMTC20F
Charbax has an interesting video about Displayport technology
https://www.youtube.com/watch?v=ZWlkkM8SkDQ
--
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/3KxiW2ZVlQU/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/deffd4e3-a66c-4bda-9803-b62e10fd0982%40googlegroups.com.