Related
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
How does I set up teh linux?
1- you dont know anything about linux. go ubuntu. we will tweak it after that. version 10.xxx (cant remember exactly).
2- you've used linux before and feel comfortable when thinking about it. go ubuntu/fedora.
3- no worries. you can troubleshoot alone when leenucks acts funny, you su everyday. go arch linux.
bottom line, it all comes to a few package versions.
make, python2, git, jdk, maybe a few others, need old versions. even in ubuntu, if you would like to start from a more updated base image, you'll need to downgrade. arch linux allows this with more freedom, since its more modular.
i havent used fedora for a few years now. used it back when red hat quit doing desktop images, didnt stay long and switched to slack.
i prefer archlinux because it's 300mb'ish iso, allows lvm, luks from live cd, doesnt have a text-based installer but install scripts, rolling release system (prebuilt packages/packages built from src using abs/aur, testing repo), customizable/modular, cli package manager (pacman ), systemd, grub2..
basically, if you like bleeding edge and power to yourself, try archlinux. read the wiki, begginer guide, install guide. first time i did it, i used another pc to help me go through all the steps.
sent from my i9250
When you're interested in Linux you can take a easy to use Distro like Ubuntu.
Packetmanagement resolves dependencies autocratically and nearly each software is available as a precompiled Packet
Also such Distros are running 32 and 64bit Programms out of the box.
If you want to learn linux in deep (and have enough time to solve issues) i recommend a Distro like Arch or Slackware.
I use Slackware64 and learned a lot about Linux and the packet and library dependencies.
Because the Packetmanagement does not resolve dependencies.
Even GUI Tools are rare on this Distro, you have to struggle with config files.
Slackware is a pure 32 or 64bit Linux (can be build to a Multilib Linux).
For Example the Android SDK mainly uses 32bit.
Maybe you should try some Distros and use that one you feel familiar with.
Also there are good Resources out in the net which you should read (Filesystem Hierarchy Standard, File Permissions, Basic Shell Tools)
Google and en.wikibooks.org/wiki/LPI_Linux_Certification would be a good starting point.
You could also try some Live-CDs, mess with it and when all went wrong only reboot.
Good Luck
Indeed, start Ubuntu, you can even stay with it if you like. But Arch and the install guide give you a good grasp on how Linux works.
Of course, you can develop apps in Windows or OSX, and OSX and Linux are the only two that allow you to build Android from source (basically ROM development). You also need to know Java to develop Android apps, less fun than screwing around with Ubuntu lol.
Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Thanks for all the replies guys! Wish me luck lol.
RoyJ said:
Thanks for all the replies guys! Wish me luck lol.
Click to expand...
Click to collapse
Just to give one final thought, I think Slack would be a better learning experiencing, since it's even more close to Unix than Arch. With Arch you learn a lot, that's a fact, but with Slack you understand even how libraries and dependencies work, kinda the hard way, since you don't have a package manager to take care of it for you.
I think both might be a steep (maybe too steep) learning curve, and Ubuntu will be easier but, Ubuntu does things more their way. It's Linux, but things are different. Eventually, you'll know what i mean.
sent from my i9250
Thanks for the input. That's something to look into for sure. I am in no rush to just jump in and try it. I'd really like to learn everything on a basic level like that first.
I'm trying to get the research down before I start messing with the development.
Well this thread is dedicated about the possibilities of getting a port of ubuntu phone os. Recently displayed and would be launched around MWC 2013, Ubuntu OS will be launched for galaxy nexus! .
although there are short threads present about the topic, aim of this thread would be to provide Support/Bug-Report/F.A.Q if any port of ubuntu shows up for our phone from our great developers.
This is refreshingly new OS.
HERE IS THE LINK TO THREAD--> http://forum.xda-developers.com/showthread.php?t=2174544
I am damn sure some-one will take up this great job
Latest: Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
Some of Features of ubuntu phone:(taken from wikipedia)
OS family Unix-like
Working state Current
Source model Open source
Initial release February 2013; 30 days' time
Available language(s) Multilingual
Update method Ubuntu Software Center (+ APT, …)
Package manager dpkg
Supported platforms i386, ARM
Kernel type Monolithic (Linux kernel)
Userland GNU
Default user interface Unity shell
So what may be the hindrances:
What kernel version is it based on
will it require bootloader unlock ;-(
UBUNTU PHONE OS
since it is yet to be released this is an open discussion, if any developer takes this project for defy, this thread will be a F.A.Q/support/Bugreport thread (if ever it happens )
i'm here for tests.
i'm not a developer, but you guys can count with my defy+ for tests. I really would like to have ubuntu phone on my defy+.
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
what is ubuntu's packaging method? i mean the OS image?
pgreed said:
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
Click to expand...
Click to collapse
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone. Plus, as far as I remember (though I can easily be wrong on this, since I haven't touched an Ubuntu machine for months, now), this OS (specially considering it was specifically deployed for running on phones) doesn't take more than 2GB when installed. Again, I can be wrong, BUT... What about multiboot? A class 6 8GB card (or even a class 4, like the one included with our phones) may do the job, and we will still be able to boot CM10+ and ask silly questions to Google Now.
vedhasd said:
what is ubuntu's packaging method? i mean the OS image?
Click to expand...
Click to collapse
I may be wrong, but I think I read in more than one place it'll be available as a flashable zip. Since the folks there at Canonical were able to boot this little beauty in a Galaxy Nexus, and they intend to release the GNx version (without many workarounds needed to install) before the end of january, I think it's pretty safe to bet on a recovery-flashable zip file. Last, but not least, I think an install script (like the ones devs use in current Android flashable zips) may be slightly modified to install Ubuntu from a system image, specially if you consider Aroma-based installers are doing wonders in matter of personalizing Android installations. This not considering (and in this matter I have absolutely no idea) the possibility of the disk installer of linux distributions be already running scripts very similar to those used on Android flashable zips to install desktop OSs on computers. Devs will be better suited to tell about the latter.
P.S.: if anyone there tried Android-x86, you guys can see the installable image is very similar to an Ubuntu (or any other linux) installation zip. This might lead us in the opposite direction, looking at which modifications were made for the installer to work with Android, and reversing them for a Ubuntu installer to work in a flashable zip.
K3n H1mur4 said:
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone.
...
Click to expand...
Click to collapse
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
pgreed said:
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
Click to expand...
Click to collapse
It may depend on how far our devs will be able to strip down the OS for our phone, I think we may not require full fledged running desktop compatibility but it still depends by what extent we can strip down the footprint!
Sent from my MB525 using xda premium
Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
red lens defy+ guinea pig
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
'm not developer but my red lens defy+ is available as a guinea pig.
Then I can make rather a system as primary OS alpha and p500 use my day-to-day
sorry my english
It would be nice if we had more one option rom. Live freedom!
are there some news? i've founded this video, but I can't understand if this is related to the thread in android development...
in youtube: watch?v=hglLF3dM8Zk (i'm not allowed to post link ^^ )
Kayant had released an alpha preview.. but the ubuntu project will be helpful iff we some how boot up 3.0.x kernel with RIL
Sent from my MB526 using xda premium
I've finally managed to root my Nokia X, which is a prerequisite for installing the Xposed Framework and some modules for it (which is something I've been wanting to do for a while). After trying out various tools, starting with the more open-source ones (like Kernelchopper), I ended up using Framaroot. Why? Because Framaroot doesn't require a computer and is extremely simple to use (and it works ); personally I don't mind if a rooting method requires the usage of a PC, but ideally all you'd need to do would be to download and execute an .apk.
Now, Framaroot is hardly the ideal solution, because it's not (free and) open source and not even source-available (reference). What's more, the superuser app that Framaroot installs -- SuperSU -- is not free and open source software either. There are open-source alternatives, such as Koush's Superuser.
I'm sure some of you are thinking, "but Framaroot's/SuperSU's developer is a great and trustworthy person!"; while I don't have a good reason to doubt that, I still have a reason to be wary of what code I execute on my mobile device; it's not like you go clicking around every single .exe on a Windows computer either. When the source code is free and open, people are able to see what it does, compile it and submit improvements to it.
I therefore propose that we create an easy-to-use, one-click rooting app for devices like the Nokia X family (Qualcomm chipset, Android 4.1.2 or otherwise vulnerable to CVE-2013-2595). How? From what I've gathered, the "Framaroot Gandalf exploit" source is on GitHub (also see this Tweet by Pau Oliva), so it shouldn't be too hard for an expert Android developer -- which I'm sure we have plenty of in this forum -- write a graphical front-end for it and have it drop Koush's Superuser onto the device after a successful exploit (instead of SuperSU or $your_favorite_proprietary_superuser_app).
Thoughts?
towelroot is opensourced
https://github.com/f0go/Towelroot-by-Geohot
Jack Phoenix said:
I've finally managed to root my Nokia X, which is a prerequisite for installing the Xposed Framework and some modules for it (which is something I've been wanting to do for a while). After trying out various tools, starting with the more open-source ones (like Kernelchopper), I ended up using Framaroot. Why? Because Framaroot doesn't require a computer and is extremely simple to use (and it works ); personally I don't mind if a rooting method requires the usage of a PC, but ideally all you'd need to do would be to download and execute an .apk.
Now, Framaroot is hardly the ideal solution, because it's not (free and) open source and not even source-available (reference). What's more, the superuser app that Framaroot installs -- SuperSU -- is not free and open source software either. There are open-source alternatives, such as Koush's Superuser.
I'm sure some of you are thinking, "but Framaroot's/SuperSU's developer is a great and trustworthy person!"; while I don't have a good reason to doubt that, I still have a reason to be wary of what code I execute on my mobile device; it's not like you go clicking around every single .exe on a Windows computer either. When the source code is free and open, people are able to see what it does, compile it and submit improvements to it.
I therefore propose that we create an easy-to-use, one-click rooting app for devices like the Nokia X family (Qualcomm chipset, Android 4.1.2 or otherwise vulnerable to CVE-2013-2595). How? From what I've gathered, the "Framaroot Gandalf exploit" source is on GitHub (also see this Tweet by Pau Oliva), so it shouldn't be too hard for an expert Android developer -- which I'm sure we have plenty of in this forum -- write a graphical front-end for it and have it drop Koush's Superuser onto the device after a successful exploit (instead of SuperSU or $your_favorite_proprietary_superuser_app).
Thoughts?
Click to expand...
Click to collapse
TBH, it is a good idea. But there is already a Rooting procedure so creating an app would be useless. No?
mdfzhi said:
towelroot is opensourced
[GitHub link I had to remove because xda is stupid and thinks everything posted by "new" users is spam, no matter what]
Click to expand...
Click to collapse
Thank you for the suggestion, but unfortunately there are multiple issues here:
It doesn't work. I tested out a variety of different rooting methods, of which one was Towelroot. The concept is great, but it just wouldn't work on my Nokia X, running the original firmware. lifehacker.com/towelroot-roots-android-kitkat-devices-in-one-tap-no-p-1592226618 notes that "[Towelroot] works on phones running Android KitKat", and the Nokia X isn't running KitKat.
Towelroot is actually not FOSS. Someone took the original tr.apk file from towelroot.com, ran it through apktool (code.google.com/p/android-apktool/) and posted the result on GitHub. It was not released there by its author, which makes it effectively a blatant copyright violation, tool. Furthermore the resulting thing won't compile either. Several sources (such as tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/ and clevcode.org/cve-2014-3153-exploit/) note that "TowelRoot is closed source and heavily obfuscated" and that there are (or rather, weren't) any public exploits of CVE-2014-3153 (Joel Eriksson rectified that, though).
Of course it'd be great to see tools like Framaroot and Towelroot go open source, but I don't see that happening anytime soon. Why the developers cling to the source so hard when they're distributing their work entirely for free is beyond me; I'm no big fan of freeware personally.
All that being said, I'm not proposing we reinvent the wheel, but rather invent the wheel and release the invention under a suitable license for everyone to study, amaze and contribute to. That's something you can't do with tools like Framaroot and Towelroot.
(Sorry about the lack of clickable links, btw; I blame that on XDA. Sorta ironical that the initial post can contain links, but subsequent replies cannot. Makes total sense...not.)
Dom3616 said:
TBH, it is a good idea. But there is already a Rooting procedure so creating an app would be useless. No?
Click to expand...
Click to collapse
If by "procedure" you refer to the fact that you can flash a recovery firmware or whatnot, then no, I don't think creating an app would be useless at all. Flashing requires a computer (unless I'm horribly mistaken here) and it can seem intimidating for, well, someone who hasn't done it before (like me!). I'm still somewhat of a smartphone newbie, and definitely an Android newbie, although I have plenty of programming experience and IT experience in general.
Framaroot was really simple to use and you really can't go wrong with it, but as I wrote in the original post, the sad truth is that it's still proprietary and that's at least a major ideological concern for some (like me), but also a practical concern. When the source code is available, you can look at it and see what it does, or if you lack the skills, you can ask an experienced (Android) dev to check it for you. When the app is closed-source, all you have is the dev's word on it, and occasionally that of the app's users. It's something, but it's not ideal -- for anyone, I believe.
Google Play Store and other app stores are full of Flappy Bird clones and whatnot, and despite Play Store not accepting apps meant to root the device, I firmly believe that this utility should be built, for it serves a practical purpose and essentially hasn't been done before: there are rooting utilities that are easy-to-use, there are FOSS implementations (well, at least the one I linked in my original post) of the CVE-2013-2595 exploit, but there isn't a FOSS version of the CVE-2013-2595 exploit that would have a GUI and be easy to use.
It's all about choices, and I wish there are options available to the users, and not just "which proprietary rooting app you want to use?".
well if u really must use opensource tool to root the nokia x family, that too can already happen.
first just flash custom recovery, eg cwm or twrp. both are foss. both can be flash using fastboot, not closed source tool needed.
then just boot into the custom recovery and flash either chainsdd superuser flashable zip or koush superuser flashable zip, both are foss too.
mdfzhi said:
well if u really must use opensource tool to root the nokia x family, that too can already happen.
first just flash custom recovery, eg cwm or twrp. both are foss. both can be flash using fastboot, not closed source tool needed.
then just boot into the custom recovery and flash either chainsdd superuser flashable zip or koush superuser flashable zip, both are foss too.
Click to expand...
Click to collapse
This is indeed true, but flashing can be intimidating for newbies and as mentioned in my original post (and also in the thread title), an .apk is so much better. My main motivation for gaining root access was so that I could install Xposed Framework and the resOverloader module for it, which enables to make the device support a language not supported by default, as the X's language selection is not like that of your average Android device's.
Should you sacrifice functionality if you want to be free and stay free? While the answer way too often is "yes", it obviously shouldn't be that way, given the obvious advantages of free and open source software. Admittedly this proposal's scope is somewhat narrow in that the initial target would be devices equipped with Qualcomm chipsets and running Android 4.1.2 (or older), and I probably should have posted this in a more generic Android app development section of the forum instead of the Nokia X subforum. However, it certainly wouldn't hurt anyone if this app would be built, as community members could then contribute to it and add support for other devices, SoCs and versions of Android...which, in the long run, would have the potential to become something like a free and open source clone of Framaroot.
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