[ROM] [DEV] Archlinux Phone - GNU/Linux for Android devices project - Sony Xperia S, Acro S, Ion

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

Related

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

[discussion|support|F.A.Q] Porting Ubuntu Phone OS to Defy(+)

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

Android Wear 2.0 for SmartWatch 3 port progress Thread & Creation of OSS project

Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire
I need that so much any ETA ?
By the way keep up the good work !
Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs
Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk
great!!! thanks
Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:
thankx you great hard work and good luck my friend
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.
@PDesire :
You're the man...keep up a good work ???
Hey @PDesire , any news? I'm sooooo hyped!!!
Thank bro I hope
Thanks for this!
So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire
PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...
Thank you very much, hope you will finish it without problems~!

OmniROM Android R (11) for Pi 4

OmniROM
Download
Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/
Images tagged with WEEKLY can be used to setup
official Google gapps
64bit build
Tablet mode configuration (not Android TV)
At least 4GB model recommened
No HW accelerated video playback
Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
Support of booting from SD or USB by just changing config.txt (check README below)
GPIO support - monitor and set README.gpio
chrome (ium) is broken use alternative browser (firefox, edge)
for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
how to do updates? - check README.update
Adjust screen resolution:
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800
Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720
Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community
For current progress and how to build yourself check
README.build
XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4
Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/
ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP
Version Information
Status: Stable
Created 2020-10-28
Last Updated 2020-10-28
Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts
20201016
Just a snapshot of the current state
Non microG builds will come later
20201028
WEEKLY and MICROG build
20201105
TWRP included
IMPORTANT
Check new recovery section in README for all the details
EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
But after all of that hassle from now on updating will be much easier since with TWRP you can create
userdata backups on an external USB device very easy
So going from this release an update could work like this.
1) boot your current install into TWRP
2) create an userdata backup on an external USB device
3) flash the new build - you dont need to care about userdata
just do whatever you always do with it e.g. resize
4) boot new build
5) go into Advanced settings and switch boot mode to recovery and restart
6) in TWRP restore the backup you created before from external USB device
7) flash switch_boot_rom.zip and reboot system
8) enjoy
add boot mode switch in Advanced settings
add audio output switch in Advanced settings
whatever has been done since the last build
20201115
fixed 5GHz WiFi AP
fixed Fondar USB touch screen
actual development
20201122
switch to new kernel base - big thanks to Konsta - with update to 5.4.77
update mesa to v20.2
initial work to support pi camera - not yet working but close
initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
all core system updates and fixes
20201128
performance tuning
November security update
gpio support update
all core system updates and fixes
20201206
added gpioi-fan
cpufreq config in advancded settings
all core system updates and fixes
20201214
property persist.debug.drm.mode.force to adjust screen resolution
all core system updates and fixes
20201224
added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
enabled showing BT device battery level if applicable
all core system updates and fixes
Best Xmas wishes for those who care about it and looking forward to 2021
20201231
add WiFi firmware for p400
kernel update 5.4.85
add userdata resize and project quota enable script in TWRP
reduce dB of max media volume
all core system updates and fixes
Does this build support the original RPI 7" touch screen?
elhennig said:
Does this build support the original RPI 7" touch screen?
Click to expand...
Click to collapse
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
maxwen said:
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Click to expand...
Click to collapse
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
ich_mind said:
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
Click to expand...
Click to collapse
Depends mostly on mesa development - but nothing I would hold my breath for
elhennig said:
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
Click to expand...
Click to collapse
well - the thing is that this does not have anything to do with building ROMs
should all be possible by modifying config.txt
Looking at the LOST OS builds might give some hints since I think he supports it
Just one word of wisdom here from me since I saw in some reports as something negative
"It’s stuck in “tablet mode” instead of Android TV mode"
I really dont think a raspi is a well equipped device to be used for ATV when you get
a ATV USB stick from e.g. Xiaomi for about 40E that simply works without issues and
has official google support.
So while everyone feel free to use our repostories to create an ATV build dont ask me for it cause I wont do it.
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Growking99 said:
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Click to expand...
Click to collapse
I think you hit me already in TG - but just to reiterate here again - as it is in also the README
Using latest firmware is MANDATORY - 64bit support has been added a few months ago
without you will get the described no boot
Best is to flash latest firmware (which also includes USB boot even if you dont need it)
There are a long list of pages describing how to update. Just linking one here for reference
https://www.tomshardware.com/how-to/boot-raspberry-pi-4-usb
You MUST do that in e.g. Raspberry OS so best do it before even starting with Android
lernfaehig said:
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Click to expand...
Click to collapse
Long press the power button in the navigation bar -> shut down
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
flyl0 said:
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
Click to expand...
Click to collapse
Welcome captain obvious - tell us something new...
maxwen said:
Welcome captain obvious - tell us something new...
Click to expand...
Click to collapse
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
flyl0 said:
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
Click to expand...
Click to collapse
You are just too focused on what you want to do with the device
does it have google apps out of the box
vedforeal said:
does it have google apps out of the box
Click to expand...
Click to collapse
of course not - this would be illegal
We are not in China here ...
PS: I did not find any android-11 gapps out there that would work currently
So the only way is anyway microG for now - which is enough for most people
i tried to boot off 32gb usb and it wont work
and first thing before you say anything about my bootloader being out of date its not here is the bootloader output BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTFS /boot
BOOTLOADER: up-to-date
CURRENT: chu 03 set 2020 12:11:43 UTC (1599135103)
LATEST: chu 16 abr 2020 17:11:26 UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad
when i try to boot the build (from the website i didnt compile it) with either the microg or the weekly build after flashing the pi just simply wont start and the green and red light just keeps flashing and nothing happens i was able boot twisterOS just fine off this same usb so its this build i dont know if i did something wrong but the file system was present in gparted and i tried booting it without expanding the partition and with doing so. also i tried to "fix" all the partitions using gparted and that did nothing also i noticed that the /boot directory in this build seems a bit empty compared to my manjaro build i know your working hard on this but this might be a bug in your build and id be willing to help you fix it

Question which time can we have ROMs for xperia 10 III ?

I just can't wait anymore
Deemooo said:
I just can't wait anymore
Click to expand...
Click to collapse
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
sorry, i don't understand the system domain, i just a normal xperia user, just want to use native android likes los,dotos,rr etc. I'm sorry i can't help you, All i can do is wait, that's some sad.
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
Yes I see xperia merge fix in sources actually for kernel sources issue compile . I will create custom kernel for start . lineage later
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
I guess we can create repo vendor and extract proprietary blobs from stock vendor...
I tested phh gsi lineage and its fully stable guy - in bonus green tint is fixed -
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Kyrimeas said:
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Click to expand...
Click to collapse
for now no . I run actually gsi phh in daily use for stability . for sources I still work on it I have worked for compile kernel xperia https://github.com/Aarqw12/kernel_PDX213/commits/aosp/LA.UM.9.12.r1 but no luck actually its bootlop only for unknow reason.
Kyrimeas said:
Are you also building recovery?
Click to expand...
Click to collapse
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
zpk787 said:
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
Click to expand...
Click to collapse
for stability build-in is very recommanded
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
no need vendor image, need only flash oem.img xperia give really everything . lena sodp is no completly done for now , new features need to be implemented team sodp work on it. I guess just wait more
now xperia 10 III is officially added to open-source programm
Xperia 10 III added to Sony's Open Devices program - Sony Developer World
developer.sony.com
software binary released now we can compile rom
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
yeah,i also think we can have roms in the furture,im waiting
Kyrimeas said:
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
Click to expand...
Click to collapse
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
You can check "e foundation" GSI. It's ungoogled phones
ada12 said:
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
Click to expand...
Click to collapse
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
xinniethewuflooh said:
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
Click to expand...
Click to collapse
GSI is no a custom rom its a Generic System image , its update only /system ( os framework ) and use blobs,drivers from your /vendor , GSI is universal and run in all devices treble .
They are no custom rom available in public actually for this devices , source for custom rom is availlable but unstable in use ( sound only in headset , ril bug ... )
actually if you want run lineage or other custom android os use PHH GSI , or wait for custom rom ( NO ETA ).

Categories

Resources