Related
i found the android vncserver project on google code and thought it would be a fun thing to have. so i taught myself how to cross-compile the android kernel. it is actually not that difficult. then i cried for help because the kernel patch was only available for an older kernel. after that i noticed it was actually a piece of cake to manually patch the kernel sources, as the patch was rather small.
so the result of all-night kernel compiling is the kkernel-1.0! mainly teknologists kernel and config, so still the props goes to him (and the others that worked on the kernel), my part was only patching the kbde keyboard emulator sources into the kernel and putting an update.zip together. this is compatible with mcr2.9, i didn't test it with other roms. should work with every rom that accepts the teknologist kernel.
the update.zip also places the fbvncserver binary (precompiled from the project page) in /system/bin. start with "adb shell fbvncserver", connect to heros ip port 5901.
now we just need to figure out how to send mouse events to the server and we're good to go!
as always no responsibility for your phone going berzerk (or your girlfriend )
somehow i am having difficulties uploading the file, please refer to modaco, i will try again later.
thread @modaco
It works great. Will be better when input is supported! Thanks
Hi
I am trying to play around with making my own android driver (just basic things at the moment) but cannot figure out how to compile them. Before trying to write my own driver i would like to compile one of the included ones (in this case its one of the gadget drivers for mass storage). I cannot work out what i need to add where to make it compile. I have compiled the kernel successfully.
What do i need to change so that when i type make modules it will compile the drivers i want into a .ko file (at the moment this would be the gadget driver but in the future it would be my own drivers)?.
Thanks for your help
got it
Worked out to compile the built in modules i just needed to fun make modules. As far as a custom module, make a Makefile as outlined in
yatsec.blogspot.com.au/2011/01/guide-to-compiling-custom-kernel.html All compiled and worked.
Hey XDA!
I've been trying to learn to compile AOSP so I can customize ROM's from scratch instead of having to steal someone else's compile and make modifications from there. I definitely don't want to take the work of others and back track to make changes.
I've got a Nexus 7 2013 LTE and I've setup a Linux build environment. I've installed the correct packages, followed all the instructions on the AOSP site, and downloaded the proprietary binaries (both the current 4.4.4 and preview binaries) to try and create a AOSP Lollipop 5.0.2_r1 build. I know there are ones out there that are working almost flawlessly, but I can't seem to get it to boot. My file sizes for system.img and all other packages are the same after compiling, I "make clobber" once executing the shell scripts to create the vendor folder in my source root, and I see the vendor files being processed during the build, but once the package (both ota and manually built attepts) are fastboot loaded, I get a boot loop, and I'm not sure why, it instantly hangs and reboots as soon as the "ANDROID" screen appears.
If anyone can give me any guidance, I want to start building ROMs for the community, but I just can't seem to get a bootable build to compile.
I may have missed some details, so if anyone can help me with figuring this one out, feel free to PM me, or leave a note on this topic.
Thanks!
fhd kernel ( ZE551 ) & POSSIBLY hd (ZE550) with KVM & Bridge compiled. *need help*
MODERATOR NOTICE:
All thread posted in the Development section must have a link to kernel sources to meet GPLv2 requirements. Because this thread does not have proper sources linked and because development has stopped, the thread has been closed.
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Edit:
I uploaded a new flashable kernel img based off 2.19. This one should support: kvm, bridge and NTFS read/ *LIMITED* write, swap and ignore kernel module signatures. XDA only allows 8mb for .img files, so I tar'd it.
Edit2:
I compiled a ZE550 kernel ( called hd ) and if some brave souls want to try it, I also put together a boot.img.
Edit3:
New fhd kernel has been compiled with additional usb modules. Kernel should now load kvm related modules automatically, so you shouldn't need to use the script anymore.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Edit 4:
New fhd & hd kernels for 2.20
Edit 5:
New exfat.ko module
ycavan said:
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Click to expand...
Click to collapse
Why 2.12? 2.18 kernel source is available...
That just happened to be the kernel source linked in Android development. If this test works out, I can probably do the same thing with whichever kernel source is available.
Our phones are pretty amazing to be able to compile their own kernels natively on the device.
Sent from my ASUS_Z00AD using XDA Free mobile app
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/ *LIMITED* Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
One suggestion would be to flash the zImage using
Code:
fastboot flash zImage nameofzImage
or test it using
Code:
fastboot boot nameofzImage
but I dont know if the phone supports the "boot" command.
I´m not sure about the modules either and I can´t test it, as my phone didn´t arrive yet.
Other solution, try this:
http://forum.xda-developers.com/showthread.php?t=2670512
ycavan said:
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
Click to expand...
Click to collapse
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
TheSSJ said:
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
Click to expand...
Click to collapse
I added CONFIG_NTFS_FS=m ( you could set to that y ) and CONFIG_NTFS_RW=y in /{working directory}/device/asus/moorefield/fhd/mofd_fhd_diffconfig
when you make the kernel, it's going to ***** about the config files not matching; follow the directions and manually update all of the other config files and it will finally compile.
Building for Android is a pita. )
Well, then here come the disappointing news (I discovered that when I wanted to include NTFS USB-OTG support directly by the kernel for my TWRP and it didn't mount it as R/W):
CONFIG_NTFS_RW is just a partial write support. It won't create files or folders, it can only overwrite existing files and only by the size they currently have
config NTFS_RW
bool "NTFS write support"
This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to.
Click to expand...
Click to collapse
Only possibility available is to include ntfs-3g driver using fuse
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
ycavan said:
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
Click to expand...
Click to collapse
Please keep me posted, I'd like to remove the dependency of ntfs-3g in recovery. I fear there actually is no native support of NTFS (googling was not helpful unfortunately)
1) modify module loading function to ignore module version/magic strings.
2) compile the kernel with toolchain used by ASUS (or close to it)
3) use pre-compiled tntfs.ko from original boot.img
I don't have right now the patch for module loading procedure. Need to check old Galaxy S3/S4 custom kernels source (but it's should be easy to patch by finding error string). In time when exFat module source wasn't available, this trick was very common in samsung custom kernels for exFat support.
Thanks
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
LUCKYSHOT52 said:
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
Click to expand...
Click to collapse
It's only in theory.
In reality, there is no Z35xx support in windows, and i doubt anyone will write drivers by himself (windows isn't opensource). Officially Z35xx is Android-only SoC.
FajarMF28 said:
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
Click to expand...
Click to collapse
The source is already available, so no worries there, since this is source that Asus released.
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
ycavan said:
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
Click to expand...
Click to collapse
is there extra features such as other governor or i/o scheduler?
cangcan said:
is there extra features such as other governor or i/o scheduler?
Click to expand...
Click to collapse
To be honest? I can't remember since my main focus was getting kvm compiled in.
I've attached my .config for the 20150707 build ( in the boot image ).
I've also attached a screenshot of Windoze 7 being installed.
Commandline for Arch Linux x86_64 to start qemu-kvm to install windoze:
qemu-system-x86_64 -display none -vnc :1,password -monitor stdio -m 1G -smp 4 -enable-kvm -drive file=/mnt/0/machine1.img,format=raw -cpu host -cdrom /mnt/MicroSD/Vcd/en_windows_7.iso -boot menu=on --usbdevice tablet
breakdown of the command line:
-display none = no display, I did this to test the virtual machine. normally, you would probably use -display sdl w/ XServer-XSDL running
-vnc :1,password, This says to set up a vnc server with normal port + 1 ( 5901 ) and you expect a password to be set later
-m 1G, 1 gig of ram
-smp 4, our VM will use 4 cores
-enable-kvm, enable Kernel support Virtual Machines
-drive file=/mnt/0/machine1.img,format=raw, my "disk" file
-cpu host, use the same cpu information
-cdrom /mnt/MicroSD/Vcd/en_windows_7.iso, my Windows 7 install cd turned into an iso
-boot menu=on, enable the boot menu ( hit F12, etc.. )
--usbdevice tablet, Qemu's Vnc server sucks at tracking mouse positions so using tablet mode keeps the mouse pointer .. well on-point
Tks for share
Kernel great work
But how to install window 7 ? ?
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk
Archlinux Phone for Sony Xperia S
Part of GNU/Linux for Android devices project
First of all, this project is not ready for end users but everything is provided to build an archlinux system for the Sony Xperia S. So you will be able to have a complete system with GPU hardware acceleration, support of vibrator, sensors, GPS, wifi etc (everything is not yet tested like bluetooth, nfc...). Graphical applications are already able to display (Qt/Kwin tested but GTK3/kwin should be ok too).
This project is not just for this device and is really open to support multiple devices and GNU/Linux distributions. So you can share this project everywhere (xda, distributions forum...) ! Contribution are welcome and can be discussed directly on this thread to share efforts.
Introduction
This is a project to create a convergence between the desktop and the mobile/phablet/TV... so to build new mobile OS based on existing GNU/Linux distributions with the most common parts possible. We share some common base between mer-hybris (SailfishOS) and Ubuntu Touch but the architecture and integration are different (refer to Architecture).
Cell phone are powerful and expensive for flag ship so why just use it as a phone ?
Imagine that your cell phone can become your core device ! Plug it to a big screen and this is your workstation ! Plug it to an 'empty' laptop (no CPU, no RAM needed ...) and this is your laptop ! Move everywhere and this is just your mobile phone !
This is what motivate this project.
Applications
Applications are critical on a mobile platform and we hope to support Android application as soon as possible (need further studies to complete the architecture).
GNU/Linux applications are already compatible but not always adapted for a mobile phone for now but... We hope a lot of plasma mobile and KDE convergence guideline for Application developers
Source code
There is few projects and some fork available under my github but if you want to start to port a new distribution or a new device, everything is documented in the gnulinux_support project.
Android needs to be modified but we deliver a solution that permit to be integrated upstream and so to compile Android or Android for GNU/Linux with the same code.
For now we have only Android 5.1.1 patches available but 6.0 will come soon. CyanogenMod 12.1 and 13.0 can be a good target to support a lot of devices in the future (or at least to simplify the portage process per device).
manifest for Sony Xperia S
manifest for Pure AOSP 5.1.1 (can be used for Nexus devices)
Documentations
Architecture schema
Main documentation
Archlinux installation
Videos
https://vimeo.com/177893595
Distributions supported
archlinux (archlinuxarm)
Project status
This project is in an early stage and for developers but we created solid base of works and the portage of plasma mobile, ofono, ... and amazing features will start over those solid base to provide an end user product
Todo :
pulseaudio support for GNU/Linux - Android Hw (and maybe for Android to support sound from Android application)
fix libinput/kwin environment
ofono (or maybe an alternative/hybrid solution that can use the Android Telephony Framework ? no study yet on this point)
flashing after boot.img package update + generation of a custom initramfs
security with crypto, firewall and SELinux (SELinux or equivalent integration will mainly depend of the distribution support but for now this is disabled)
plasma mobile or other ?
localisation framework (see freedesktop project)
OMX
merge everything possible to every upstream projects used to create GNU/Linux for Android devices
overlayfs into kernel ? (not mandatory but can be a great solution for the Android rootfs and schroot)
... (a lot that I forget)
BUT despite this long list of todo... We already did :
New architecture (GNU/Linux and Android integration, systemd, libhybris, chroot, wayland ...)
SurfaceFlinger Composer supported by Qt and Kwin
schroot for Android (Android can run into a chroot and we can interact easily with it)
systemd integration (with reboot to bootloader and recovery, Android /init support, etc)
libhybris_ext (compatibility version with support of Android 5+)
Android integration with GNULINUX_SUPPORT (rc, init, busybox, ramdisk, OTA ... adaptation)
clean rootfs with only 2 symlinks that permit to see that we are on an Android device (nothing more)
OpenGL support (with backend hwcomposer or SurfaceFlinger)
Archlinux support (OTA and packaging)
Design a possible solution for a lot of other GNU/Linux distributions (share architecture and Android adaptation)
Documentation
Download
Binaries will be available when really usable for end user. For now everything can be compiled from source code
Devices supported
Sony Xperia S (nozomi): work in progress (this is our reference device)
RESERVED
I will provide OTA file, binaries (archlinux packages), images and video to show what is working and how really soon
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Demetris said:
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Multi screen is not yet supported on kwin_wayland so for now I have just focused to render on the main screen (0) but it will be possible to do it for hdmi (1). But for sure I hope to support hdmi output.
For now I will focus to port plasma-mobile/ofono/pulseaudio.
Impatient to try another gift from genius mickybart.
Waiting............
wow something new
waiting eagerly...
lovely, cannot wait to try it
finally there is hope to ditch android, ios and windows
I have not a lot of time to work on this project with the release of nAOSP b11 but once done I will rework on it and provides binaries for Devs.
But, I think that this "new OS" powered with plasma is a good choice and I'm happy to see that plasma 5.7 integrate such kind of features :
https://www.kde.org/announcements/plasma-5.7.0.php
https://blog.martin-graesslin.com/blog/2016/05/virtual-keyboard-support-in-kwinwayland-5-7/
Great improvement have been done on Wayland support too.
If some of you are interesting to do some packaging with Archlinux, I'm really interested to get some help to provide a usable system for end user. The work for now is more too package/install user tools (so integration of components). I miss pulseaudio and ofono patching but I'm optimist to solve every issues.
finally nAOSP 6.0 b11 and b12 took me more time than expected but I'm back on this project.
For information, I updated everything to Qt 5.7.x support.
Some pull request have been done and are in discussion for at least qt5-qpa-hwcomposer-plugin (mer-hybris).
I decided to don't provide binaries for now as there is not a lot of sense to do it except if you are interesting to help the project (mainly to package some stuffs, integrate tools for GPS, ofono, pulseaudio etc).
I just finalized to record a small video. I will cut it and upload it to prove that archlinux arm phone can be a reality with the proposed new architecture (and on our Xperia S).
I will work again on the kwin/libinput issue. Maybe just a logind/dbus/kwin discussion issue. Once fixed that should permit to have a graphical keyboard by default (I know that for iOS or Android this is normal... but not really on a GNU/Linux desktop) !
I continue to look for help on this project and if you can create some packages like the one for plasma-mobile and derived repo let me know in PM or in the thread.
small video of the project
https://vimeo.com/177893595
Great achievement today
libinput is working and so I'm now able to move windows, plug a keyboard to write a text file, plug the mouse (pointer is not visible) ...
Menus are well displayed now with the good size.
Next steps : pulseaudio, wifi, plasma-mobile... (and bug fix on the kwin backend).
wow mickybart !. u just struck my interest in coming back to this phone! amazing work. my phone was unusable and parts needed replacement. looking at the activity of yours in this section made me repair the device and try out your work.. cheers mate! keep going with ur awesome work!
OnePlus X (onyx) port
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
nik012003 said:
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
Click to expand...
Click to collapse
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
mickybart said:
...
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future !
Let me know your advice and if you thing to base your work on CM 13.0...
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Click to expand...
Click to collapse
I've not tried arch but have attempted similar to this project with Debian (raspbian) on ancient hardware with partial success.
As free time rears its rare head I'll be trying to adapt your project for my newer HTC based on cm13.
By the way, your work on N ril from github is great, allows my cm14 to get/make calls without rebooting. Now if I can just figure out why rild takes forever to stop dying and respawing and start actually running...
mickybart said:
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
Click to expand...
Click to collapse
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
nik012003 said:
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
Click to expand...
Click to collapse
Thanks. I will give it a try but to have a more automatic process I will maybe follow what is done in mer-hybris :
https://github.com/mer-hybris/pulseaudio-modules-droid