Related
OTools------------------------------------------------------------------
OTools is an opensource toolkit for windows and linux that helps you manage your oppo or oneplus device.
Click to expand...
Click to collapse
Code:
This program has enough knowledge to brick your device, destroy your computer,
void warranties, eat cats and burn your flowers.
The developer disclaim every damange caused from the usage of this program.
Supported devices
------------------------------------------------------------------
OnePlus One
Oppo Find 7(a/s)
Oppo Find 5
Oppo N1
Features
------------------------------------------------------------------
User friendly gui
Management features
Backup and restore (adb)
Push and Pull files
Import camera photos
Install apk
Record Screen
Shell
Modding
Root
Unlock Bootloader
Lock Bootloader
Backup EFS
Flash zip files
Install roms (optional backup)
Flash boot.img files
Install recovery
Root Mode
Dipendecies
------------------------------------------------------------------
ADB
FastBoot
XTerm (only for linux amd64)
Downloads
------------------------------------------------------------------https://github.com/linuxxxxx/O-Tools
Sources
------------------------------------------------------------------
Github - Master
Windows
Linux (amd64)
Unix / Linux
Notes
------------------------------------------------------------------
It's fully written using qt (c++), some parts are written in bash (batch for windows), if you want to compile, just import the sources into qt
It's not avaible yet, I just got my opo, so NO ETA
It's based on my XiaomiTool
Contributions and suggestions are welcome
XDA:DevDB Information
OTools - An opensource Toolkit for Oppo and OnePlus devices , Tool/Utility for the ONEPLUS ONE
Contributors
linuxxxx
Source Code: https://github.com/linuxxxxx/O-Tools
Version Information
Status: Alpha
Created 2014-12-25
Last Updated 2015-01-16
Placeholders are not allowed on XDA. When are you going to fully release it with a downloadable file?
TiVON said:
Placeholders are not allowed on XDA. When are you going to fully release it with a downloadable file?
Click to expand...
Click to collapse
There are sources, if u cannot live without compile it, I've written WIP
Not really a placeholder as source code is given.
Thanks!
linuxxxx said:
There are sources, if u cannot live without compile it, I've written WIP
Click to expand...
Click to collapse
justmpm said:
Not really a placeholder as source code is given.
Thanks!
Click to expand...
Click to collapse
Ah yes! My sincere apologies!
I was a bit too quick in judging, sorry. It's just that I am used to "Super Hax0r Skillaas Tools" placeholder threads, so I was expecting this to be one too.
Missed it
Will compile this evening, and report back if anything didn't work out for me.
Alpha released for unix and linuxamd64 (on Linux you may need qtwidget to make it start)
There are bugs and missing features!!
@ windows users: the code is (almost) ready, I just have to find a PC (or setup a VM) where I can compile and test this
Can u port this tools for Yu Yureka
ela1103 said:
Can u port this tools for Yu Yureka
Click to expand...
Click to collapse
Add a device support is pretty easy, so maybe
linuxxxx said:
Add a device support is pretty easy, so maybe
Click to expand...
Click to collapse
Waiting for the YU Yureka
OTools------------------------------------------------------------------
OTools is an opensource toolkit for windows and linux that helps you manage your oppo or oneplus device.
Click to expand...
Click to collapse
Code:
This program has enough knowledge to brick your device, destroy your computer,
void warranties, eat cats and burn your flowers.
The developer disclaim every damange caused from the usage of this program.
Supported devices
------------------------------------------------------------------
OnePlus One
Oppo Find 7(a/s)
Oppo Find 5
Oppo N1
Features
------------------------------------------------------------------
User friendly gui
Management features
Backup and restore (adb)
Push and Pull files
Import camera photos
Install apk
Record Screen
Shell
Modding
Root
Unlock Bootloader
Lock Bootloader
Backup EFS
Flash zip files
Install roms (optional backup)
Flash boot.img files
Install recovery
Root Mode
Dipendecies
------------------------------------------------------------------
ADB
FastBoot
XTerm (only for linux amd64)
Downloads
------------------------------------------------------------------https://github.com/linuxxxxx/O-Tools
Sources
------------------------------------------------------------------
Github - Master
Windows
Linux (amd64)
Unix / Linux
Notes
------------------------------------------------------------------
It's fully written using qt (c++), some parts are written in bash (batch for windows), if you want to compile, just import the sources into qt
It's not avaible yet, I just got my opo, so NO ETA
It's based on my XiaomiTool
Contributions and suggestions are welcome
XDA:DevDB Information
OTools - An opensource Toolkit for Oppo and OnePlus devices , Tool/Utility for the Oppo Find 7
Contributors
linuxxxx
Source Code: https://github.com/linuxxxxx/O-Tools
Version Information
Status: Alpha
Created 2014-12-27
Last Updated 2015-01-16
Nice, looks good. Will be giving it a try once it's ready (and when I have time).
Released for unix and linux amd64 (on linux you may need qtwidget to make this work)
There are bugs and missing features!!
@ Windows users: code is (almost) ready, i just have to find a pc (or setup a vm) where i can compile and test this
linuxxxx said:
Released for unix and linux amd64 (on linux you may need qtwidget to make this work)
There are bugs and missing features!!
@ Windows users: code is (almost) ready, i just have to find a pc (or setup a vm) where i can compile and test this
Click to expand...
Click to collapse
I'll be on my computer tomorrow morning (GMT +8), I can help if I can.
An important question
Does this software work with Find 7's that are OTA updated to current specifications?
imei backup
can we backup imei with this
sheraz1015 said:
can we backup imei with this
Click to expand...
Click to collapse
Yes, but just on bacon. I don't think it's needed on oppo devices (AFAIK)
help for oppo find 7
i need to backup imei and partition on my oppo find 7 , has anyone done it
thanks in advance
sheraz1015 said:
i need to backup imei and partition on my oppo find 7 , has anyone done it
thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/find-7/development/tutorial-how-to-save-restore-partition-t2958467
Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirementsTo run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
DownloadsNo Download as no longer maintained and buggyQR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issuesYou tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06
FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit
I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...
GOOD JOB .....Bro
kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you
Anyone already try this tool? I want download, but size so damn high
zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)
I can´t flash twrp with this toolikt any one have a clue?
Do you have the adb drivers installed? Or is it throwing an error?
Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk
Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.
dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...
Download link is not working. Please re-up. Thanks
godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1
If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.
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
When will sailfishos ever appear? I love Linux/GNU and I want to see this OS on whyred
If you port it.
Not worth it. Not enough people will use it
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Not worth it. Not enough people will use it
Click to expand...
Click to collapse
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
TITANIST26 said:
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
Click to expand...
Click to collapse
We have lineageos 14.1
https://www.google.com/amp/s/forum..../development/rom-lineageos-14-1-t3765529/amp/
I think its a pretty good idea. Just because some people don't use them doesn't mean its useless.
Sailfish is already present for redmi note 5 / 5 plus. It would be a great addition for our note 5 pro too
a2p1k02 said:
We have lineageos 14.1
Click to expand...
Click to collapse
Need not assembled ROM * .zip, and you need to have a device tree, branch cm-14.1 (device_xiaomi_whyred, kernel_xiaomi_whyred, vendor_xiaomi_whyred on Github). And it is not there, only lineage 15.1. I will try to collect lineage
karan5chaos said:
reply
Click to expand...
Click to collapse
I did not find the https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 instruction for building specific files for the device tree and google too not found. Found the old for cm 11 or others do not describe a sufficiently assembly system. Help me find this guide!
I think people have ported sailfish using lineage 15.1 as well. Did you check maemo.org? I'm sure you will find the required guide there.
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
TITANIST26 said:
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
Click to expand...
Click to collapse
You are my hero !
Thank you so much for your efforts and persistence. It's because of members like your this community is thriving. I will gladly be a tester and report back issues and feedback if any.
karan5chaos said:
Reply
Click to expand...
Click to collapse
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
TITANIST26 said:
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
Click to expand...
Click to collapse
I think the question at stack overflow did mention some fix in second answer. Did you try that ?