I work with Cisco devices on a regular basis. To connect to them, I need to use a DB9 serial.
I have tried the usb to serial Prolific 2303 chipset but it isn't supported in the OS (I'm not sure why this was removed from the Android Linux kernel because it is standard in Linux kernel 2.4.31 and later but anyway...)
Anyone know of a way to get serial connectivity so I can use this tablet as a true laptop replacement? Maybe a serial to bluetooth would work? Samsung says the bluetooth supports SPP but I don't want to dish out $70+ to find out it doesn't work.
Maybe someone familiar with compiling kernel modules for Android could assist? I have the pl2303.c source code but I'm not familiar enough with compiling kernels or kernel modules to attempt this.
I've been looking into this myself the past couple of days. The kernel is not compiled with support for USB-Serial converters, but all of the code is there. It looks like the kernel would have to be recompiled along with the required modules. Here is the source I'm using: https://github.com/pershoot/galaxy-2636
So far I've just looked at config and it is easy to enable the required modules, but I haven't managed to get the kernel compilation and ARM toolchain to work just yet.
samsung source
I noticed the pl2303.c and pl2303.h are in the Samsung source I downloaded.
I'm going to try to compile a kernel module in the next week.
I'm fairly shocked this hasn't been a bigger issue. We can't be the only ones wanting this functionality - especially since Samsung support basically told me to pound sand.
I've managed to compile an ICS kernel with the required configuration and modules, once I figure out how to get it on the device I'll test it. If it works I'll build a honeycomb kernel as well and post both in the dev section.
That is fantastic! I'm having issues getting my cross compile to work properly.
Well, I managed to build the kernel & modules properly but the adapter still isn't recognized even with the modules loaded. I think there might be more to the problem than missing modules
I read today that the main linux kernel and the android fork are going to be merging. Maybe that will lead to better device support.
About the Shield TV PVR Project
I wanted to use my NVidia Shield TV not just for gaming and Netflix, but did not like the idea to loose the (in my view) really cool wifi remote and gamepad by switching to 'that other full android' image that is currently available on xda. So i decided to jump on the road and add those few additional features I was missing to the stock system by myself..
After some (many) hours of work to get the nvidia supplied source packages trimmed down and fixing bugs in the kernel, I can finally say its running pretty good now!
Here is what is working right now:
- A full kernel compile can be done in just about 3-8 minutes contrary to more than one and a half hours when using the unmodified nvidia package
- The stripped down development package I built is only taking about 1.5 GB of harddrive space, there is no need to download all of these 20+ GB of mixed stuff from the slow nvidia servers anymore, no need to wait for the repo tool to unpack and etc - its just fetch and compile a bootimage right away.
- I have added full NTFS (r+w) support to the kernel, so you can just plug-in any ntfs formatted harddrive or usb stick and use it like the fat32 formatted drives that were already supported.
- I have added DVBAPI support back into the kernel so you can plug-in a supported DVB-C/DVB-S/DVB-S2/DVB-T/DVB-T2 tuner stick and use it to watch, record and stream live TV from your shield - full PVR powers baby! (I had to patch the base kernel to allow that as there was some 32/64 bit ioctl compatibility issue that I think was one of the reasons why nvidia did not include dvbapi - it took a long time googling around to get this working..)
- I have built the latest tvheadend server version from source aswell, on my shield it gets started using a bootscript and its really easy to install using adb
This is my current setup:
I have connected 3 DVBSky DVB-C/T/T2 USB tuner sticks to a powered USB 3.0 hub and plugged that into the shield. Since there were no drivers for my usb stick brand available, I have patched the dvbsky branch of the kernel tree with a backported version of these drivers. (For those of you that have different brand sticks, there are 2 other branches available, one with all the stock kernel-supplied dvb drivers, one with all the drivers from media_tree). It is now easily possible to
watch live TV (using Kodi with tvheadend htsp plugin) with full EPG etc
stream live TV to the kids room (my kids are using kodi installed on a fire tv stick that is connected to an old 19" lcd screen)
stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet
record tv shows on demand, timers can be programmed using a smartphone (tvheadend helper app) aswell as through the kodi interface
All these features are in heavy use by my family right now and without any real impact on the overall speed of the shield console - read: completely transparent in the background! (I have attached a 500 GB USB 3.0 hard drive (ntfs formatted) to the shield for storage of the recorded tv shows - obiously.)
Get yourself a Shield PVR
Just grab a linux-supported tuner stick and a harddrive, flash one of the precompiled kernels and install tvheadend from my androidfilehost area - it surely is not for the fainthearted as there are currently no step-by-step instructions, but I think everyone with a little knowledge on how to use adb and fastboot can do it.
Of course I will try to help out if you run into problems, you can post your questions/suggestions/bug reports into the issue tracker or to my thread at xda.
Contribute
If you want to say thanks and help continuing my work you can hit that donate button on my androidfilehost area, it is not in any way required tho. If you want to contribute code/patches/ideas - just do so using the usual channels (issue tracker, xda thread).
How do I get set up for development?
Check the official repo wiki page, I have added some scripting code examples and etc to the wiki there.
Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!
Code:
Androidfilehost (prebuilt images): https://androidfilehost.com/?w=files&flid=48701
Github repo: https://bitbucket.org/nopnop9090/shieldtv-kernel
Wiki: https://bitbucket.org/nopnop9090/shieldtv-kernel/wiki
Great work!
I tried to follow the link to the wiki on your bitbucket, but only get a message that I don't have access to it. Maybe some permissions that should be changed?
This is excellent work. What usb tuners are supported?
---------- Post added at 10:09 PM ---------- Previous post was at 09:28 PM ----------
i just tried the version compiled on the 28th on retail firmware it doesnt boot
Wow! This is EXACTLY what I wanted to do with my Shield TV but didn't think it would be possible. Is that dvb-s2 by chance?
andersh said:
Great work!
I tried to follow the link to the wiki on your bitbucket, but only get a message that I don't have access to it. Maybe some permissions that should be changed?
Click to expand...
Click to collapse
should be fixed as of now - shame on me!
xd4d3v said:
This is excellent work. What usb tuners are supported?
---------- Post added at 10:09 PM ---------- Previous post was at 09:28 PM ----------
i just tried the version compiled on the 28th on retail firmware it doesnt boot
Click to expand...
Click to collapse
hm, please try to install the developer firmware first, and i would recommend the build id 11c80e6 for first testing - I will try to make it work on retail when everything else is a bit "matured" of course
gumbi2400 said:
Wow! This is EXACTLY what I wanted to do with my Shield TV but didn't think it would be possible. Is that dvb-s2 by chance?
Click to expand...
Click to collapse
dvb-t/t2/c/c2/s/s2 - doesent matter as long as there is a kernel driver for the tuner available. and if its not already included in the kernel you can use the media_build release where a lot more tuners are supported - its a little tricky to get it running because with media_build you would have to find out which tuner.ko file you need to "insmod" - so better try the "static" build id 11c80e6 before anything else and please post a dmesg capture if it doesnt recognize your tuner.
Haven't actually purchased a tuner yet, but am thinking about doing it soon now! I'll try and find one that's well supported under Linux already.
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
sorry for that, I made a silly mistake in my script when I built the stripped down environment and published it for the first time - i now have pushed the fixed source to the repo and a full set of new bootimages to the androidfilehost page. it should be all working now but please report any problems you may find as I cannot test everything by myself (because of lack of hardware, obviously)
could you enable Webcam drivers too so we can use Skype video
chemstar said:
could you enable Webcam drivers too so we can use Skype video
Click to expand...
Click to collapse
+1 to this.
Also, since you're compiling the kernel, it might be worth adding the systemless root.
at the end of the day, it makes no difference without the supersu app, so users can decide to have root or not, by installing the supersu app.
chemstar said:
could you enable Webcam drivers too so we can use Skype video
Click to expand...
Click to collapse
all available webcam drivers have been enabled in the media_build branch, you will have to find out which .ko modules to insmod though. the stock kernel
does not have much (if any) drivers for webcams I think.. hmm.
xd4d3v said:
+1 to this.
Also, since you're compiling the kernel, it might be worth adding the systemless root.
at the end of the day, it makes no difference without the supersu app, so users can decide to have root or not, by installing the supersu app.
Click to expand...
Click to collapse
hm, sounds like a pretty good idea - I will have a look at it shortly
Does this also work with [ROM][Full Android for Shield TV][v.2.2] shield-tv ?
ErAzOr2k said:
Does this also work with [ROM][Full Android for Shield TV][v.2.2] shield-tv ?
Click to expand...
Click to collapse
i dont know, the other rom doesnt use a full stock-based kernel I think. ask the rom creator?
This looks great, good job so far!
stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet
Click to expand...
Click to collapse
Does this mean you are using nvenc for transcoding? Or are you not using any hardware acceleration? How is that performing (how many streams can you transcode simultaneously)?
I am really looking for a solution to make transcoding easier. From what I've seen with using nvidia's nvenc is that the CPU is only decoding the streams, encoding is completely offloading, giving a massive decrease in overall server load. Now I know the new nvenc has a hard limit to allow up to 2 streams transcoding on normal GeForce gfx cards, but I wonder if the same limitation applies to the Tegra X1 chips..
In short: hardware transcoding makes this the ultimate tvheadend server/set top box!
PS: Also, the links in your Wiki entry to your Androidfilehost profile don't seem to work. I think they are account links (only for you when you are logged in). The correct link seems to be https://www.androidfilehost.com/?w=files&flid=48701. Maybe also add it linkable to your OP?
Can you please explain how exactly do we apply your file?...
Is it enough to just flash the zip file with twrp, or do we have to do something else?
nopnop9090 said:
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
About the Shield TV PVR Project
I wanted to use my NVidia Shield TV not just for gaming and Netflix, but did not like the idea to loose the (in my view) really cool wifi remote and gamepad by switching to 'that other full android' image that is currently available on xda. So i decided to jump on the road and add those few additional features I was missing to the stock system by myself..
After some (many) hours of work to get the nvidia supplied source packages trimmed down and fixing bugs in the kernel, I can finally say its running pretty good now!
Here is what is working right now:
- A full kernel compile can be done in just about 3-8 minutes contrary to more than one and a half hours when using the unmodified nvidia package
- The stripped down development package I built is only taking about 1.5 GB of harddrive space, there is no need to download all of these 20+ GB of mixed stuff from the slow nvidia servers anymore, no need to wait for the repo tool to unpack and etc - its just fetch and compile a bootimage right away.
- I have added full NTFS (r+w) support to the kernel, so you can just plug-in any ntfs formatted harddrive or usb stick and use it like the fat32 formatted drives that were already supported.
- I have added DVBAPI support back into the kernel so you can plug-in a supported DVB-C/DVB-S/DVB-S2/DVB-T/DVB-T2 tuner stick and use it to watch, record and stream live TV from your shield - full PVR powers baby! (I had to patch the base kernel to allow that as there was some 32/64 bit ioctl compatibility issue that I think was one of the reasons why nvidia did not include dvbapi - it took a long time googling around to get this working..)
- I have built the latest tvheadend server version from source aswell, on my shield it gets started using a bootscript and its really easy to install using adb
This is my current setup:
I have connected 3 DVBSky DVB-C/T/T2 USB tuner sticks to a powered USB 3.0 hub and plugged that into the shield. Since there were no drivers for my usb stick brand available, I have patched the dvbsky branch of the kernel tree with a backported version of these drivers. (For those of you that have different brand sticks, there are 2 other branches available, one with all the stock kernel-supplied dvb drivers, one with all the drivers from media_tree). It is now easily possible to
watch live TV (using Kodi with tvheadend htsp plugin) with full EPG etc
stream live TV to the kids room (my kids are using kodi installed on a fire tv stick that is connected to an old 19" lcd screen)
stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet
record tv shows on demand, timers can be programmed using a smartphone (tvheadend helper app) aswell as through the kodi interface
All these features are in heavy use by my family right now and without any real impact on the overall speed of the shield console - read: completely transparent in the background! (I have attached a 500 GB USB 3.0 hard drive (ntfs formatted) to the shield for storage of the recorded tv shows - obiously.)
Get yourself a Shield PVR
Just grab a linux-supported tuner stick and a harddrive, flash one of the precompiled kernels and install tvheadend from my androidfilehost area - it surely is not for the fainthearted as there are currently no step-by-step instructions, but I think everyone with a little knowledge on how to use adb and fastboot can do it.
Of course I will try to help out if you run into problems, you can post your questions/suggestions/bug reports into the issue tracker or to my thread at xda.
Contribute
If you want to say thanks and help continuing my work you can hit that donate button on my androidfilehost area, it is not in any way required tho. If you want to contribute code/patches/ideas - just do so using the usual channels (issue tracker, xda thread).
How do I get set up for development?
Check the official repo wiki page, I have added some scripting code examples and etc to the wiki there.
Since I am a new registered user at xda I am not able to provide a live download link right now - but I give you a hint: bitbucket and my nickname should get you going
Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
Click to expand...
Click to collapse
This is really great !!!!! congratulations for that... I'm looking for this since I shileld was released. Can you post a video on youtube of your system up&running tvheadend on Kodi ?
thanks!!!
Hi i am a new user, how do i download the link?
how do i download the link for the rom? thanks
nopnop9090 said:
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
About the Shield TV PVR Project
I wanted to use my NVidia Shield TV not just for gaming and Netflix, but did not like the idea to loose the (in my view) really cool wifi remote and gamepad by switching to 'that other full android' image that is currently available on xda. So i decided to jump on the road and add those few additional features I was missing to the stock system by myself..
After some (many) hours of work to get the nvidia supplied source packages trimmed down and fixing bugs in the kernel, I can finally say its running pretty good now!
Here is what is working right now:
- A full kernel compile can be done in just about 3-8 minutes contrary to more than one and a half hours when using the unmodified nvidia package
- The stripped down development package I built is only taking about 1.5 GB of harddrive space, there is no need to download all of these 20+ GB of mixed stuff from the slow nvidia servers anymore, no need to wait for the repo tool to unpack and etc - its just fetch and compile a bootimage right away.
- I have added full NTFS (r+w) support to the kernel, so you can just plug-in any ntfs formatted harddrive or usb stick and use it like the fat32 formatted drives that were already supported.
- I have added DVBAPI support back into the kernel so you can plug-in a supported DVB-C/DVB-S/DVB-S2/DVB-T/DVB-T2 tuner stick and use it to watch, record and stream live TV from your shield - full PVR powers baby! (I had to patch the base kernel to allow that as there was some 32/64 bit ioctl compatibility issue that I think was one of the reasons why nvidia did not include dvbapi - it took a long time googling around to get this working..)
- I have built the latest tvheadend server version from source aswell, on my shield it gets started using a bootscript and its really easy to install using adb
This is my current setup:
I have connected 3 DVBSky DVB-C/T/T2 USB tuner sticks to a powered USB 3.0 hub and plugged that into the shield. Since there were no drivers for my usb stick brand available, I have patched the dvbsky branch of the kernel tree with a backported version of these drivers. (For those of you that have different brand sticks, there are 2 other branches available, one with all the stock kernel-supplied dvb drivers, one with all the drivers from media_tree). It is now easily possible to
watch live TV (using Kodi with tvheadend htsp plugin) with full EPG etc
stream live TV to the kids room (my kids are using kodi installed on a fire tv stick that is connected to an old 19" lcd screen)
stream transcoded (bandwidth saving) live tv to my tablet and smartphone over the internet
record tv shows on demand, timers can be programmed using a smartphone (tvheadend helper app) aswell as through the kodi interface
All these features are in heavy use by my family right now and without any real impact on the overall speed of the shield console - read: completely transparent in the background! (I have attached a 500 GB USB 3.0 hard drive (ntfs formatted) to the shield for storage of the recorded tv shows - obiously.)
Get yourself a Shield PVR
Just grab a linux-supported tuner stick and a harddrive, flash one of the precompiled kernels and install tvheadend from my androidfilehost area - it surely is not for the fainthearted as there are currently no step-by-step instructions, but I think everyone with a little knowledge on how to use adb and fastboot can do it.
Of course I will try to help out if you run into problems, you can post your questions/suggestions/bug reports into the issue tracker or to my thread at xda.
Contribute
If you want to say thanks and help continuing my work you can hit that donate button on my androidfilehost area, it is not in any way required tho. If you want to contribute code/patches/ideas - just do so using the usual channels (issue tracker, xda thread).
How do I get set up for development?
Check the official repo wiki page, I have added some scripting code examples and etc to the wiki there.
Since I am a new registered user at xda I am not able to provide a live download link right now - but I give you a hint: bitbucket and my nickname should get you going
Check my twitter account aswell for latest updates and a preview video showing my actual shield in action!
THE BUILD SYSTEM HAS BEEN FIXED, NEW BOOTIMAGES WERE UPLOADED AND THE REPO IS BACK ASWELL. THANKS FOR YOUR PATIENCE.
Click to expand...
Click to collapse
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
umoraes2009 said:
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
Click to expand...
Click to collapse
to all asking how to do this.
you don't need to root for this, however, you need to unlock the bootloader
once the bootloader is unlocked, you need to boot into fastboot mode, and flash the boot.img.
you will need root to install tvheadend though, and knowledge of command line.
If we're nice maybe we can ask nop to package it up into an apk wink wink.
I managed to play with it for a while, and installed tvheadend, just can't figure out the web-ui password!
thanks again for the great work.
let me know if I can help in anything, I'm not a developer, but used to be a Solaris sysadmin back in the day.
angel2000med said:
Can you please explain how exactly do we apply your file?...
Is it enough to just flash the zip file with twrp, or do we have to do something else?
Click to expand...
Click to collapse
currently you need to flash the image with fastboot haveing previously unlocked the bootloader.
check nopnop9090/shieldtv-kernel/wiki on bitbucket - i have added some basic instructions at the bottom of the wiki.
umoraes2009 said:
This is really great !!!!! congratulations for that... I'm looking for this since I shileld was released. Can you post a video on youtube of your system up&running tvheadend on Kodi ?
thanks!!!
Click to expand...
Click to collapse
as i am still not allowed to post links here: search youtube for my nickname, i have a small video showing kodi live tv up there. i plan on producing a complete walkthrough sometime in the future..
icombina said:
how do i download the link for the rom? thanks
Click to expand...
Click to collapse
check nopnop9090/shieldtv-kernel/wiki on bitbucket - androidfilehost link is in there. i suggest starting with the boot-099a0b601ae3-dvb_static bootimage.
umoraes2009 said:
Hi,
I have shield on stock firmware 2.1.... it's not clear how to update it. should I root it ? How do I apply the update file ? thanks!
Click to expand...
Click to collapse
check nopnop9090/shieldtv-kernel/wiki on bitbucket - androidfilehost link is in there. i suggest starting with the boot-099a0b601ae3-dvb_static bootimage.
xd4d3v said:
to all asking how to do this.
you don't need to root for this, however, you need to unlock the bootloader
once the bootloader is unlocked, you need to boot into fastboot mode, and flash the boot.img.
you will need root to install tvheadend though, and knowledge of command line.
If we're nice maybe we can ask nop to package it up into an apk wink wink.
I managed to play with it for a while, and installed tvheadend, just can't figure out the web-ui password!
thanks again for the great work.
let me know if I can help in anything, I'm not a developer, but used to be a Solaris sysadmin back in the day.
Click to expand...
Click to collapse
try to manually start tvheadend from adb shell for the first time like this:
Code:
/data/dvb/tvheadend -C -c /data/dvb/tvheadend/hts
(the -C will let tvheadend enter into intial setup mode where you can enter passwords etc. for subsequent starts skip -C.)
i only want to give some feedback regarding webcam drivers.
my booth devices have been recognized
unfortunately i didn't have luck getting them to work with skype. i think there is something missing inside camera hal implementation. maybe zulu can give us some usefull hint how to fix this.
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