Develop Bugs

Samsung Galaxy Tab Development Environment

Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.

Count me in. I am getting a Tab tonight and I plan to develop for it. Currently, I have got the froyo source on my machine and want to integrate the open source code that Samsung released for this device.
Has anyone successfully built a custom ROM using the Samsung source code? Any help on this will be appreciated.

Awesome!
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
I've put a small amount of stuff into the Dev Environment, most just shell files etc to make installing everything easier. One click sort of thing.
My first task though is going to be to try and fix the failure that is the Samsung display driver. Most noticeable are the 4 by 1 widgets that don't stretch across the whole screen.
After that I'm going to start work on a GUI for the environment and the iOS Emulator.
thoughts?

Whats wrong with Android SDK and Eclipse?

It's not the most straight forward thing. I'm looking to make something that includes its own libraries too. It's aimed at beginning developers mostly, so you can literally download one file which includes everything you'll need then start editting and then one click to compile and have it all work. Simplicity

I'm also interested in this... The SGT is my first android device, and my company will want android apps for internal and external uses... and a one click dev environment would be a most welcome option!

DevShroom said:
I've got Froyo working on the Tab, which I built from the source code from the android open source project website but it's just a generic build from the straight source, nothing special. not with the samsung code though. do you have any links for it?
Click to expand...
Click to collapse
Straight up AOSP? Could you have a crack at CM?

Anything you need, including testers, I'm in.

I have programmed some programs in android. If you need my help, i will be glad to help,
Sent from my GT-P1000 using Tapatalk

i'm currently setting up a new galaxy Tab ubuntu 10.10 VM but I always fail at installing java5-jdk, but when im ready i'm going to have a look at the CM and AOSP source and i !try! to port CM to the tab!

I am working on a custom rom , if you need any help do not hesitate

yann06 said:
I am working on a custom rom , if you need any help do not hesitate
Click to expand...
Click to collapse
are u building from source or are you modifing a stock rom?

DevShroom said:
Hello developers,
I'm starting this thread because I'm interested in designing a development environment for the Samsung Galaxy Tab so that developers, like myself, can have an easy environment for modifying the Android OS. I'll be aiming this environment at all Android Devices but I want to start with the Samsung Galaxy Tab.
At the moment I don't have much of a structure for this project, nor much direction, so if anyone has any ideas for what tools etc I should include in this please let me know. If anyone wants to get on board with the project it would also be appreciated. Send me an email.
tool ideas:
- integrating the GCC and Javac compilers into the environment.
- integrating a way to generate make files and to build from these files.
- GUI for editing files from the kernel and application framework.
- easy to use way of setting up branches for projects with the Repo and Git included in the Android Source Code.
Click to expand...
Click to collapse
I'll be interested in getting involved in a community driven project for the SGT. I'm a unix admin with lots of experience in the OS and system development field. Interested in what ideas you have on this.

Try using openjdk. It works for me.
Sent from my GT-P1000 using Tapatalk

Thanks everyone for the positive feedback on all this! it'll be good to have as many people on board as possible.
if you have troubles downloading the sun-java5-jdk there is a good tutorial on it on this site, it doesnt come as part of the repository by default so until you add it in sudo apt-get install sun-java5-jdk will not work.
atm i am only working with AOSP not CM, i am trying to set this dev environment up for a nice simple build and then i'll start working on more complex builds so we can start developing custom roms.
@paulshields - do you know much about linux/android drivers? i wanna fix the widget sizing problem on SGT but my driver knowledge is limited

[ROM] [DEV] Archlinux Phone - GNU/Linux for Android devices project

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

A humble request to build a modded kernel with rt2501 support

So first of all, here's the disclaimer: I know NOTHING about building stuff, and I have a VERY slow network to even sync the sources required to make it on my own (I live off of 90KB/s)
For the past 2 days I've been banging my head into the wall trying to figure out a way to get my TP-LINK TL-WN321G to work on OOS or CM or a chrooted Kali Linux. Apparently some modules need to be configured into the OnePlus 3 kernel in order for the rt2501/rt2573 to be recognized by the device via USB OTG.
So the humble request is as follows: Is there ANYONE nice enough to actually sync a kernel source (OOS or CM13) and modify the kernel to support the modules necessary for all of this to work? If I can make a chrooted kali linux along with a working wifi adapter that supports monitor mode, I can practically ace my Senior Project.
Thank you!

Building LineageOS for Samsung S6 (zeroltexx)

I am after some help in building LineageOS 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx). I know it isn't officially supported (only 14.1 is official), however there are unofficial builds and apparently all the sources required are on GitHub.
I have tried LOTS of times to build this but each build has the same issues when flashed to the S6 Edge I have to test with.
I have followed the guide here - https://wiki.lineageos.org/devices/zeroltexx/build which officially covers building Lineage 14.1. I have wiped an i7 PC with 24GB RAM and 2 * 1TB disks. I installed Ubuntu 18.04 desktop, installed all updates, added all the required components listed in the guide (I also needed to add python that wasn't listed). I changed the repo sync command to be 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.1'. I then pulled in the 'zero.xml' repo manifest from here - https://github.com/Exynos7420/local_manifests and added it to /.repo/local_manifests/ and then built the ROM.
It appears to build OK - there are lots of errors in the log, however I think this is correct? It takes about 37-minutes and it outputs a .zip file in the out/product/zeroltexx directory. This installs OK to the S6 Edge, however there is an error at the start of it booting about selinux (small red text at the top of the screen for a couple of seconds). Once booted the audio doesn't work and neither does the RIL. This is compared to the unofficial ROM that Enes Uzun has created.
I have asked (and asked...) for help on the telegram group, however I keep getting told I am not doing anything wrong. If this is the case then I am doing something wrong in creating my build environment - i.e. Ubuntu or the Lineage build parts.
I am hoping someone on here has had a similar experience and managed to solve the issues or can point me in the right direction as I am stumped. I have wiped the machine and rebuilt Ubuntu 18.04 desktop 3 times so far. Following the build the results are the same each time so whatever I am doing wrong I am doing it each time.
Any help is really appreciated.
Andy

Help....
In my continuing failed attempts at building this I have now wiped another PC - Intel Core 2 Quad-Core Dell XPS with 16GB RAM and 2 * 640GB hard drives, installed Ubuntu 18.04, followed the guide etc etc etc and have hit EXACTLY the same issue so I am definitely doing something wrong.
I found this guide - https://forum.xda-developers.com/android/software-hacking/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 16.0, however there is a link to this - https://web.archive.org/web/2018061...ng/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 15.1.
So I wiped the original i7 24GB machine and installed Windows 10 Insider Preview 18290, enabled WSL and then added Ubuntu 18.04 from the microsoft store and then followed the guide TO THE LETTER and added the zero.xml from https://github.com/Exynos7420/local_manifests to the /.repo/local_manifests folder, did a 'repo sync' etc etc. Guess what? same f'cking issue..
Help please anyone? I just want to build my own Lineage 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx) so that I am not reliant on someone else releasing randomly periodic ROMs that are likely to stop when the developer stops building Lineage 15.1.
Help...

Fixed it....
The zeroltexx sources were incomplete. They were missing some files and a couple of files were wrong. These have now been updated by the maintainer (https://github.com/Exynos7420/android_device_samsung_zeroltexx), however these haven't been pushed to the official Lineage repositories yet (https://github.com/LineageOS/android_device_samsung_zeroltexx). Therefore if you are going to build it yourself you will need to use the Exynos7420 repositories (for the S6 Edge zeroltexx that is - the S6 zerofltexx has the right stuff).
Andy

Hi ADB100,
many thanks! I will try the same, after my lovely S5 get's the black-screen-of-death.
My colleague gave my an old S6, but I had lerned to love los 16.
My problem was to know howto add additional sources to the los 16 sources. Here your thread gave my some important tips.
I started to learn a build with the official sources of los 14.1, but it failed of less ram on my computer and an out of memory error message.
So I grabbed 6 gb of an old pc to give it a next try next week. If it will work I will tdy los16.
I'm not a developer, but familiar with Linux. My problem is to add all sources and to manage git and repo.
Additional to use the zero.xml. I put it on your mentioned folder, but "breakfast zero" or "breakfast zeroltexx" sent me a nothing found!
Do you have a good tutorial which I can follow?
I spent a lot af time to search for it, but all tutorials was for official build, same like the los build guide.

SailfishOS For Redmi Note 5/ Redmi Note 5 Pro

When will sailfishos ever appear? I love Linux/GNU and I want to see this OS on whyred

If you port it.

Not worth it. Not enough people will use it

Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Not worth it. Not enough people will use it
Click to expand...
Click to collapse
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.

TITANIST26 said:
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
Click to expand...
Click to collapse
We have lineageos 14.1
https://www.google.com/amp/s/forum..../development/rom-lineageos-14-1-t3765529/amp/

I think its a pretty good idea. Just because some people don't use them doesn't mean its useless.
Sailfish is already present for redmi note 5 / 5 plus. It would be a great addition for our note 5 pro too

a2p1k02 said:
We have lineageos 14.1
Click to expand...
Click to collapse
Need not assembled ROM * .zip, and you need to have a device tree, branch cm-14.1 (device_xiaomi_whyred, kernel_xiaomi_whyred, vendor_xiaomi_whyred on Github). And it is not there, only lineage 15.1. I will try to collect lineage

karan5chaos said:
reply
Click to expand...
Click to collapse
I did not find the https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 instruction for building specific files for the device tree and google too not found. Found the old for cm 11 or others do not describe a sufficiently assembly system. Help me find this guide!

I think people have ported sailfish using lineage 15.1 as well. Did you check maemo.org? I'm sure you will find the required guide there.

After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.

TITANIST26 said:
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
Click to expand...
Click to collapse
You are my hero !
Thank you so much for your efforts and persistence. It's because of members like your this community is thriving. I will gladly be a tester and report back issues and feedback if any.

karan5chaos said:
Reply
Click to expand...
Click to collapse
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors

TITANIST26 said:
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
Click to expand...
Click to collapse
I think the question at stack overflow did mention some fix in second answer. Did you try that ?