SailfishOS on Nexus 6 (shamu) - Nexus 6 General

Disclaimer WARNING: "Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck."
What is SailfishOS? Sailfish OS is a GNU/Linux based mobile operating system, which is gesture-driven for the ease of use. It runs natively as glibc (not Android's bionic), has bash and busybox (not toolbox), uses Qt for UX, and other opensource projects in its middleware -- which basically is just like a Linux on your desktop, but needs Android drivers for some of device's hardware.
What works Screen (Display, touch) LED WLAN Audio Buttons (Volume and Power) Vibrate SMS USB (Charging and developer mode) What not works Camera Calling Mobile data Browser Jolla Store ( I've not put required files to mer's OBS system now.) What not tested Other stuffs _з」∠)_ How to install Flash latest stock firmware ( Image can be acquired from Google Developers website )
Unlock bootloader and flash TWRP Recovery ( TWRP can be acquired from https://twrp.me/motorola/motorolanexus6.html )
Download required files:
lineage-14.1-20180324-nightly-shamu-signed.zip : From Google Drive | From my website sailfishos-shamu-release-2.2.0.zip : From Google Drive | From my website Enter TWRP, transfer downloaded zips to your Nexus 6 and flash them or use adb sideload Flash LineageOS first , and flash SailfishOS without reboot. (Since device encryption is required on Nexus 6's Android while SailfishOS cannot run on a encrypted /data )
Reboot and wait SailfishOS logo appears on your screen, follow the instructions to complete initial settings .
Well done

https://sailfishos.club/topic/152/sailfishos-on-nexus-6-shamu/2

I installed it so I could check it out and its very interesting if everything ends up working in a future release and it became capable of being a daily driver then I would use it to see how well it runs, Thanks for sharing !

This is wonderful to see. Sometime ago I believe there was Ubuntu touch in development for the Nexus 6, but ceased? This is great to see a new OS in development and will follow with great interest

Very nice, very pretty system but need to fix phone functions

Oh hey, you got as far as I did about. I didn't have enough time to polish things up though, and I just kinda lost steam on it all.
I never could figure out the call issue but I got most other things working. Here's my sources, if it helps!
https://github.com/Lyokanthrope/droid-config-shamu
https://github.com/Lyokanthrope/android_kernel_moto_shamu
https://github.com/Lyokanthrope/android_device_moto_shamu

Related

[INFO] "New User Guide Terms Android"

we decided to extend this guide in more threads, to give new users the chance to read more easily
Hi! I saw that many (myself initially) fail to understand the discussions of various topics of modding on this and other forums because of certain terms that are now characteristic of speech in any argument.
-Android operating system for mobile devices based on Linux kernel. Android is an open source project developed by the Open Handset Alliance (OHA). Google was the first company to work on Android and HTC has designed and implemented the first Android phone.
-ADB (Android Debugging Bridge): application via command line (command prompt, DOS), is used to flash rom, make changes to the system, backup, install applications (using the command: adb push nomeapp.apk / system / app /), copy files from your device to PC (via the command: adb pull / path / inside / of / Android / filename nome_file_destinazione) and more. ADB is a tool included in the SDK of Android that allows you to manage your phone simply by connecting it via USB. For programmers, ADB is also used to execute commands on a virtual machine Android. detailed instructions.
- Apk (short for Android Package): is the file format used to install the Android software (it works similar, more or less, that is for Windows. Exe). Renaming the extension of this file. Zip you can open it with any operator of compressed files.
-App or Apps: abbreviation of the term application or applications
-App2sd (A2sd): procedure inherent in many Roma coocked, to move applications installed, or install later, the memory card instead of phone memory. to use it you must have an ext2 or ext3 or ext4 on the memory card. part of the application (the Dalvik cache) is still stored in the smartphone does not reduce the speed of execution. app2sd this is not to be confused with the various applications on the market, as those of the market allow the movement or storage of only applications that allow it.
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled) through which you can do many things, including obtaining root permissions, flash ROM, make backups, pushare files, remove files etc. ... the bootloader mode varies from terminal to terminal, refer to those sections for how to go into bootloader on your device.
-Brick (brickare, brickato): literally (translated in Italian) "BRICK". making the cell like a brick, a something of unusable if not as paperweights.
-Digital compass: The digital compass is able to detect the direction in which the device is pointing. This information can be used together with an appropriate mapping software to assist in navigation to unknown places.
-BusyBox: BusyBox is important because it lets you install it on your Android poteziare with many basic Linux commands. In fact, some powerful programs, such as Titanium backup and others, use busybox to carry out the instructions. In virtually a few kb there are so many beautiful little programs. guide: using titanium or backup.
-Cache: a temporary memory in which data are stored as may be eliminated without compromising the functionality of the system.
-Digital certificate: encrypted code issued to two or more parties by an authorized organization, and used to verify the identity of those parties by exchanging their public keys.
-Cupcake: Android 1.5 or relaise first official operating system pounces April 13, 2009
-Encryption: Procedure for the encoding of a systematic bit stream before transmission, aimed at avoiding that the contents can be decrypted by third parties.
Dalvik-Cache: cache used by the system to increase the execution speed of programs.
USB-Debug: mode of Android that is (turning the feature on your device via menu / settings / apps / Development / Debug USB) to allow the system to undergo special modifications.
Direct-Push Technology: Direct Push technology (push e-mail capabilities), developed by Microsoft, lets you receive new e-mail messages on their device, they are not received by your mailbox Inbox or Exchange Server. Items such as contacts, calendar and tasks are immediately updated on the device if they are changed or added on the Exchange Server.
-Emulator: it is found in the SDK and is a software that allows you to emulate (simulate) an android device. usually serves to developers (developers) to test applications.
-Digital Signature: A digital signature assures the recipient about the identity of the person who sent the file, and the absence of alterations made ​​after signing this.
-Firmware: Software comlpleto the phone, android rom often contains (the only operating system) the radio (software designed to handle all communications) and hboot (the part on the base, and boot management and partition of the phone) . The format depends on the parent company that issues them and shall be flashed through the tool or program.
-Flash (flash, flashed): install, installed.
-G. E. often written or GE (Google Experience): There are those phones that have the OS (see ROM for a definition) fully developed by Google without any addition or customization by the manufacturer that sells the device (for example the number of mobile Nexus is entirely GE). This designation often means that these phones are the first to receive updates of new versions of Android, because there being no additional software, as well as those developed by Google, the release is much quicker.
Another (more common) is that With Google.
Are those phones that despite having some customization software by the manufacturer, are fully compatible with the Google software and services with Android.
-GPRS: GPRS (General Packet Radio Systems - Radio systems for generic packages) is a data service for mobile devices. It is available for the devices that meet the GSM standard.
-GPS: GPS (Global Positioning System - Global Positioning System) is a radio navigation system based on satellites that allows the DENTIFICATION of a geographical position through a triangulation of points. The GPS is used on mobile devices for applications software for navigation.
-GSM: Short for Global System for Mobile communications (Global System for Mobile Communications), is the platform for mobile computing worldwide.
-HSDPA: HSDPA (High-Speed ​​Downlink Packet Access) is a technology for mobile devices that allows higher data speeds than traditional networks. Often referred to as 3.5G for faster downloading.
-HSPA: HSPA (High-Speed ​​Packet Access - High Speed ​​Packet Access) is a technology for mobile devices that improves the speed at which you can send and receive information on their mobile device. HSPA technology is used in 3G networks.
HSUPA: The HSUPA (High-Speed ​​Uplink Packet Access - access to packages for the high-speed) is a technology for mobile devices that provides (along with HSDPA) the possibility of having connections with fast download and upload very high by optimizing use of bandwidth.
-HVGA: The HVGA (Half-size Video Graphics Array) indicates a particular display resolution of 480 x 320 pixels.
-hboot: the part on the basis of partition and boot management and the phone
-Kernel: is the essential part of any operating system. Without going into technicalities, it manages hardware (drivers and other information about the hardware, for example). Android uses a modified Linux kernel and is entirely open source (ie source code is freely available and modifiable).
- Launcher: It 's the software that handles the desktop (icons, widgets, wallpapers etc..) Android operating system. In essence, is what appears when you access the phone after the unlock screen, called Lock Screen (see below) if it is enabled.
Android allows for excellent customization Lacuncher. Although all versions of Android will already have a default, it is possible (when this option is not blocked by the manufacturer) install as many as you want from those in the Market. Launcher The best known of those owners are not ADW Launcher, Launcher Pro, Helix Lancher.
Most producers customize more or less heavily, their phones (as long as they are not GE, see above), and modification of the launcher is usually the most common personalization. Motorola for example sviluppaMotoBlur (non-removable, and includes an additional set of changes including the Launcher), the HTC the Sense (removable; this also includes modifications to the deepest only launcher which also include the framework), Samsung TouchWiz the (removable) etc..
The change of Lacuncher makes it very often no longer available widgets developed for another Launcher.
-Leak Leaked or (escaped): this refers to the ROM or firmware that (strangely) escape to the Mother House, and is circulated on the net. are semi-official, in the sense that they are developed directly from 'manufacturer, but are not officially released (and therefore not fit to restore the guarantee of a device).
Screen-Lock or unlock screen: is the screen that appears after turning on and / or whenever you press the on / off the phone. Used to not press the keys when not using the phone. It requires a combination of specific touches, or gestures to be "removed"
-Nandroid (found in the recovery as amended): application that creates an image of the entire operating system, like norton gost and true image for windows.
-ODEX: type of compression that is used to free up memory and speed up your system. ODEX unzip the file compresses everything and creates a file. ODEX dall'apk deleting the file. dex then you end up with after launcher.apk and launcher.odex (so 'you have saved so much space and improved
the speed reading application). rom the ODEX can not be changed the subject.
-OTA: Over The Air - system that allows applications to receive updates directly from the network or system
Ext2/ext3/ext4-partition: partition on the memory card (which usually can be made using modified recovery) used to install applications on this media instead of filling up the phone memory. the ext is a type of file system used on Linux and is seen as part of the Android smartphone's internal memory. to partition the SD card in the sections and guides for your device.
-Profile A2DP: Advanced Audio Distribution profile (Advanced Audio Distribution) is a specification that refers to how two Bluetooth devices can transmit and receive streaming high quality audio. The A2DP allows the transfer of a unidirectional stream audio in stereo with two channels, such as music from one phone to a headset.
-Pull: used command in command prompt (eg adb pull / path / inside / of / Android / filename nome_file_destinazione) copy to your PC for a file or folder in the Android system.
Radio-or banda or baseband (not the FM radio): software designed to manage all the communications device (phone, wifi, bluetooth, gps, etc. ...
-Recovery: a kind of mini operating system that is used to retrieve the cell from critical situations (brick, malfunction, etc. ....), do nandroid backup, perform the wipe, flash rom coocked and file format. Zip. The Recovery is properly called Recovery Mode and means the recovery mode in which you can perform actions such as, installing updates, format the phone, format and partition the SD and more. Updating the recovery.img (you can also do without the root) with a different and we have modified provisions advanced features without having to do other steps.
-RSS: RSS (Really Simple Syndication - Guild simple): indicates an Internet protocol used to distribute information that is updated frequently, such as a blog on the Internet, audio or video broadcasts or news headlines.
-Rom: the operating system. coocked roms are usually in. zip and go through recovery flashate
Coocked-Rom: cooked rom, created by chefs (who put together parts of rom applications, modifications, patches and so on) composed and enriched with new features
-ROOT (I take verbatim from androidpedia): What is root? In Unix-like operating systems is denoted by the root user with the highest privileges, ie, system administrator, also known as super user or superuser. (Cited in Wikipedia). Android being a linux system, then the user is root, which allows you to have total control of the phone. What a privilege we have to have root permissions? We have TOTAL control of the telephone. rootare the procedure for your device varies from terminal to terminal, consult the relevant sections to find out how to make your root device ..
G-sensor (gyro): The G sensor detects the position and movement of your device. It helps to orient the display to view both vertically or horizontally depending on how you hold the device. The G-sensor can be used in games to control the actions and other applications that require a movement to be able to be activated.
-SDK (software development kit): Software development kit, which we find in the tools folder that contains the file ADB. You can download it from for all platforms (Windows, Linux, Mac OS).
-S.O. (operating system): see ROM. In fact ROM and SO tend to coincide but while the first term is used to indicate the contents of any memory or the memory itself (it is in fact for Read Only Memory), the second indicates more specifically at a very specific piece of software and not any content that a memory can accommodate.
-Streaming: The term indicates the transmission of streaming audio or digital video using the Internet.
-Superboot: method to become the superuser (root-administrator) of your smartphone, with which you can make changes to the system, such as flash ROM, modify system folders etc. ...
-Tap (capped, plugged): equivalent of left-click on PC, then click in, clicked. TAP LONG = equivalent to right click on pc
-Thetering (wifi, bluetooth and usb): Mode is a connection between the phone is another device (mostly PC), through which you can take advantage of the internet's first, and basically use it as a modem, the second ( which as I said before can be a PC or another phone yet). May be predominantly via USB connectivity, bluetooth or wifi phone.
-Tablet is a tablet device that differs from a smartphone to the screen size (usually greater than the 5 "and for its strong propensity to navigation and document management. It usually does not incorporate a module for telephone calls (one exception is the Galaxy Tab), but often have a data connection via 3G or 4G as well as the WIFI.
Google has developed a special version of Android, called HoneyComb (3.X) for release in 2011. Nevertheless, there are Tablet with Froyo.
-VGA The VGA (Video Graphics Array) indicates a resolution of the display of 640 x 480 pixels.
-WCDMA: The WCDMA (Wideband Code Division Multiple Access) is a protocol for the transmission of data in a 3G cellular network.
-WVGA: The WVGA (Wide Video Graphics Array) indicates a display resolution of 480 x 800 pixels.
Wipe Dalvik-CACHE: reset the system cache. amended by recovery takes place.
Wipe-DATE (factory reset): hard reset (reset phone to factory settings, deletes all data and applications in your phone, no memory card). some recovery in the wiping the data format factory, not a complete hard reset, but a reset of all data in your phone, for a complete hard reset you should also wipe the system and boot from the recovery of the advanced settings or proceed with the procedure manual keystroke! how to do the hard reset via keyboard shortcut see the guides in their respective sections of your smartphone.
-ZIPALIGN: A form of compression that is used to speed up execution of applications. zipalign unzip the file and aligns the compressing apk file limit so 4byte 'Android takes up less ram to read and read more' quickly and then recreates the file. apk ^ ^
If you know other terms that do not understand, this thread is yours.
P. S. I hope to be helpful
I know all of this personally but this is a very useful guide for noobs and should be made a sticky.
jonny68 said:
I know all of this personally but this is a very useful guide for noobs and should be made a sticky.
Click to expand...
Click to collapse
+1
Sticky plz
Sorry but:
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled)
Is wrong. Bootloader and fastboot are not the same. Also USB debugging mode is an android thing, when you are not booted into android (eg into fastboot or bootloader) then usb debugging mode is not used
rootSU said:
Sorry but:
-Bootloader (FASTBOOT): phone mode (while connected to USB mode with usb debug enabled)
Is wrong. Bootloader and fastboot are not the same. Also USB debugging mode is an android thing, when you are not booted into android (eg into fastboot or bootloader) then usb debugging mode is not used
Click to expand...
Click to collapse
This.
And debug has to do with adb not fastboot.
Sent from my GT-I9300 using xda premium
if you have to add terms or tips, write

[TWRP][OFFICIAL] TWRP for LAVA Pixelv1

FEATURED ON THE PORTAL
Thanks @Doug Lynch for the mention!​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.2-0 for LAVA Pixelv1, Tool/Utility for the OEM Cross Device Development
Contributors
MSF Jarvis, varun.chitre15
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-20
Reserved
Credits
varun.chitre15 for his base trees
@DHARMESH17 for being a great tester
@arvinquilao for making me jealous!
Reserved
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
body150165 said:
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
Click to expand...
Click to collapse
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
@body150165 thanks for bringing up your concern. Official TWRP build for the Snapdragon variant is already available via dl.twrp.me/seed, but the website is yet to be updated (probably in the next couple of days). As soon as it's updated I'll make a new thread here for the Snapdragon variant.
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Nur_Alom said:
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Who needs it?
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
I'll get back to you in a while after checking these. And this is TWRP 3.0.2-0, not 3.0.0-2.
I would like to know what steps have you taken to port it to determine whether I can source build for the device and make it official.
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
@cuvetto : No, these bugs don't exist in my build. Tested as working fine by @DHARMESH17.
Will these work on 1st generation android one device i mean sprout 4 ?
DarkHeart Z said:
Will these work on 1st generation android one device i mean sprout 4 ?
Click to expand...
Click to collapse
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
MSF Jarvis said:
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
Click to expand...
Click to collapse
Then I am waiting for that
Bootloop
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
ashokvishnoi1994 said:
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
Click to expand...
Click to collapse
After fastboot flash recovery twrp-3.0.2-0-seedmtk.img, what exactly did you do?
You need to press both Volume Up + Power for about 15 seconds till device reboots back into bootloader mode and then go to recovery mode and open it. This has been tested as working. What steps did you take?
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
anarchtic said:
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
Click to expand...
Click to collapse
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
MSF Jarvis said:
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
Click to expand...
Click to collapse
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
anarchtic said:
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
Click to expand...
Click to collapse
Don't own one. I believed it would boot, just like it does for Android One first gen devices(One recovery for all devices)

OXI Rom (CM 13 Based Rom) Turn your Nexus 5x in computer

Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation​
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorial​Important! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
Download​OXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670​Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:​
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
Sources​Our code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/​
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
neth15 said:
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
Click to expand...
Click to collapse
Like MS Windows Continuum but better
It work with miracast or chromecast for share the screen
it's based on Cyanogenmod 13 but modified
i haven't test this rom but for the vendor i think it's the latest 6.0 Marshmallow
you can go to see the github and website for more info
OP Refresh for more info
Renaf2 said:
OP Refresh for more info
Click to expand...
Click to collapse
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
neth15 said:
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
Click to expand...
Click to collapse
If you have a chromecast you can try
Renaf2 said:
If you have a chromecast you can try
Click to expand...
Click to collapse
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
neth15 said:
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
Click to expand...
Click to collapse
No try it at this moment sorry and i have the honor 6x now
I try it in few minutes
The Vendor.img is MTC20K
it's a simple Cyanogenmod Rom with Oxi system into it
Excellent
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
i have try that with my chromecast and work like a charm no problem here just cast your screen in quick settings in notification and run oxi remote if you haven't mouse and keyboard you can use oxi control for that you have the keypad for mouse and keyboard and if you want to play you have the pad for that
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
0x4A4A said:
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
Click to expand...
Click to collapse
You can open a new theard in apropriate section and i ask to delete this theard if you want no problem i just want to share your interesting and great work
I'm happy to meet you
Sinon je suis aussi sur frandroid meme pseudo mais je n'y vais plus je suis a la source maintenant sur xda c'est mieux pour apprendre
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
0x4A4A said:
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
Click to expand...
Click to collapse
Oh yeah thank you so much for your hard work bro
Renaf2 said:
Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation​
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorial​Important! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
Download​OXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670​Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:​
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
Sources​Our code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/​
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Click to expand...
Click to collapse
Love the idea but the UI looks awful, i don't dig it, not one bit... I like the idea that you want to bring this to other devices, because so far the only ones that have this feature are all lumias, samsung s8 and the new huawei. I offer to help with the UI, to make it prettier.

Sailfish OS for the Samsung Galaxy S2 (i9100)

Initial post for Sailfish Os for the Samsung Galaxy S2 (i9100) device.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! !!
!!(Although I am using this on my backup phone)!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! ROM IS NOT SUITABLE FOR DAILY DRIVE !!
!! ONLY FOR EXPERIMENTAL PURPOSES !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Making this port was challenging because Sailfish OS, from version 3, doesn't support kernel version 3.0 which is apparently the kernel on the S2.
Fortunately, the SailfishOS-porter guys do very seriously know their business and they are extremely helpful.
From here I would like to emphasize my gratitude towards them for helping me in this project! Thank you!
Requirements:
Before you start to download anything, please read it carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
For this ROM you can either use the stock partitions or you can re-partition to give more space to /system and /data. It doesn't matter which one you chose, I tried and both worked well.
Or if you scroll down to the New partition layout, you can use a completely unique partition layout which gives the most of the internal storage to Sailfish OS. (I currently use my device with this setup.)
Installation instructions:
1. Download all files, CM12.1 zip, Sailfish OS zip, twrp2.8.7.img and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (hold buttons: Power on + Home + Volume up)
3. Do a factory reset
At this point if you want you can repartition the S2 internal storage. (Later you can put the stock layout back if you want to go back to Android.)​
The steps for repartitioning are:​
​
Download the 'Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB' or the 'Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB' .zip file and put into the external SD card. (The difference between these two is explained down at the New partition layout section
Then boot into TWRP and flash the zip as any other zip file. The script first will warn you that it cannot do the partitioning with mounted partitions and it also copies the script itself into /tmp. You just simply need to flash the copied version from /tmp and that will do the trick. The script will format the new partitions accordingly, so once it is completed you can go ahead with the next step.
4. Still in recovery, flash the CM12.1 image
5. Still in recovery, flash Sailfish Os image
6. Still in recovery, flash twrp2.8.7.img to recovery partition
7. Still in recovery, flash kernel*.img to boot partition (this step is not required since sfos 4.4, kernel is installed by flashing the zip file)
8. Reboot
9. Enjoy the latest (4.4.0.68) Sailfish OS on your i9100.
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on CM 12.1.
Downloads:
kernel12_mtp.img for Sailfish OS 3.2.1.20
kernel33016.img for Sailfish OS 3.3.0.16
kernel34024.img for Sailfish OS 3.4.0.24
kernel41024.img for Sailfish OS 4.1.0.24
kernel43015.img for Sailfish OS 4.3.0.15
twrp2.8.7.img for i9100
CM 12.1 for i9100
Sailfish OS 3.2.1.20 for i9100
Sailfish OS 3.3.0.16 for i9100
Sailfish OS 3.4.0.24 for i9100
Sailfish OS 4.1.0.24 for i9100
Sailfish OS 4.3.0.15 for i9100
Sailfish OS 4.4.0.64 for i9100
Sailfish OS 4.4.0.68 for i9100
Sailfish OS 4.4.0.72 for i9100
Odin v1.83
AOSP-LP-Kernel+_25-08-2015_TWRP-2.8.7.0.tar
Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB
Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB
Stock partition pit file
kernel07_flatpak (kernel with Flatpak support. Flatpak install/usage instructions.)
Some useful tips:
Low power mode aka ambient mode (in Fingerterm):
Code:
mcetool --set-low-power-mode=enabled
Disable lock screen animation (in Fingerterm):
Code:
mcetool --set-lockscreen-animation=disabled
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
Now the old clunky method is no longer needed. Once you flashed the twrp2.8.7.img to the recovery partition you can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Instructions for Bluetooth (On Sfos 4.3, BT works normally, don't need this magic)
BT works however turning it on/off is not as user friendly as I hoped. Here is a little instruction/troubleshooting.
Turn BT on (It only works from Settings/Bluetooth!!!!! DON'T try from TOP MENU!!):
If BT hasn't turned on since last boot:
go to Settings/Bluetooth
tap on the dot next to the Bluetooth option
If BT has turned on at least once since last boot:
go to Settings/Bluetooth and tap on the dot next to the Bluetooth option
go back to Settings
go to into Settings/Bluetooth again
tap on the dot next to the Bluetooth option (if it is not turned on repeat from Step 2! Eventually, BT should turn on.)
Turning BT off: Go to Settings/Bluetooth and tap on the white dot next to the Bluetooth option.
Notice: Never try to tap on the white dot twice without going back to the main menu of Settings.
Never try to turn BT on from Top Menu.
However, if you accidentally did any of these BT cannot be turned on again unless you:
reboot the device (this is the easiest) or
in a command line as root issue the following command 'systemctl restart bluetooth-rfkill-event.service' (this will restart the bluetooth-rfkill-event service)
I am not sure how pairing works with different devices.
New partition layout
I mentioned that I tried this Sailfish OS installation with the stock partitions and with another what created for Android 7.1.2. With the stock partitions however was a bit more sluggish than the other one. No wonder as in the stock partitions the /system has only 0.5GB and the /data has only 2GB storage and the rest 12GB is the separate internal storage (eMMC). In Sailfish the entire os (rootfs) including all directories (like /home) live on the /data partition so the 2GB was a bit tight. (The OS itself consumes about 1GB so not much left for apps and other stuff.)
With the other partition layout, the picture was a bit better as the /system had 1GB, the /data got 4GB and the rest 9GB remained for the internal storage. But the partition where the OS lives was separated from the 9GB partition. When I installed a few apps and copied some big files into the /home, I felt the limitation very soon.
Although this layout was sufficient for android but not good enough for Sailfish.
Therefore I have created my own partition table where I restructured the sizes accordingly to my need. (The lanchon repit zip file is available in the download section.)
In this new layout I gave 1GB for the /system (the prior 0.5GB was also fine as the CM12.1 base consumed only 400MB which let a 100MB free space, but I thought that might be not enough in the future so I have chosen 1GB here), I gave only 8MB for the internal storage (eMMC which is mounted into /android directory in this rom), and this made me possible to gave all the rest 14GB to the /data partition. So basically the Sailfish apps and /home can utilize the entire internal storage.
As an extra, on the S2 there is a 0.5GB /preload partition which is hidden and unused by default. In my partition setup I set 7MB to this and the rest almost 0.5GB is also added to the /data.
Go back to stock partitions
In case you would like to do this, you can download the stock partition pit file from the download section.
For this use Odin v1.83 which is also in the download section.
The steps are:
Boot the device into download mode and connect to the PC.
Open Odin v1.83 and tick the 'Re-partition' checkbox at the Option.
Then click on the PIT button and select the downloaded stock pit file.
Then click on the PDA button and select the downloaded TWRP (AOSP kernel) file.
Then click on start.
Done. You need to boot into TWRP and wipe all partitions (system, data, emmc) then you can install the stock rom back. (or if you select the stock rom at PDA instead of the AOSP kernel, it will do the repartition and install the stock rom as well. In this case, you don't need to wipe anything and the device will reboot into the stock Android at the end.)
Changelog:
15.02.2022
=========
General advice:
Patience! All (except camera) apps do start and work but they do need time. This is true for websites. When you clicked on something, wait patiently, eventually, it will start/load.
Work:
Same as previously
Improvement: Stock browser stable and works!
Do not work:
The camera app crashes the device into reboot.
03.09.2021
=========
Work:
Same as previously
Bluetooth does work, but once it is off, needs to be toggled a few times in Settings to make it turn on again.
14.06.2020
=========
Work:
Same as previously + Mobile data is fixed! (To make it work: change Protocol to IP in Settings/Mobile network/Data access point.)
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
06.05.2020
=========
The latest version of Sailfish OS 3.3.0.16 is available to download. This requires a different kernel. Both of these can be found in the download section.
Note: With the new version the patch that displays the provider logo at the bottom on the lock screen stopped working. This issue is not related to the OS. The owner of the app should fix it.
Update: In openrepos Kodi is fixed for SFOS 3.3.0.16!
29.04.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
MTP
Bluetooth (instruction is above)
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (Can be changed to 0.82 which is more appropriate for the device's screen. to do this as root run the 'kimmoli-diyicons.sh 0.82' command. It will fail to install imagemagick but will set the ratio to 0.82 and as we have all icons in place it will work.)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly, however, there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
The softkeys (each side of the home button) work as notification leds
Do not work:
Mobile data (WIP)
Video recording (It doesn't really work in other 3.x versions either. See my test results here.)
There is an extra little issue that is a delay in screen refresh which is related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin. I managed to improve this but there is a little delay still. Probably this is the reason why we need to jump back to Settings every time before trying to turn BT on, but I am not sure.
04.04.2020
=========
Work:
Same as previously + Softkeys are used as notification leds
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
23.03.2020
=========
Work:
Same as previously + with 'kernel12_mtp' the MTP works!
Bluetooth partially works (to switch on BT requires a reboot or issue a command manually, it is still WIP)
Do not work:
Same as previously
25.02.2020
=========
Work:
Same as previously + with 'kernel07_flatpak' the Low Power Mode (AKA "sneak peek" or "ambient display") works! (install instruction is in this post)
Do not work:
Same as previously
23.02.2020
=========
Work:
Same as previously + but from now on you don't need PC and heimdall to flash kernel and twrp
Do not work:
Same as previously
19.02.2020
=========
Work:
The same as listed earlier + with the new kernel (kernel06) I attached you can boot into TWRP with the usual button combination (hold buttons: Power on + Home + Volume up)
Do not work:
Same as previously except the TWRP/Sailfish OS boot which has fixed.
08.02.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_
(where _sdcard_name_ is the name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (can be changed, I set 0.82 which is more appropriate for the device's screen resolution see the download section)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
Do not work:
Mobile data
Bluetooth (the bt driver is in the kernel, so in theory, with some config file changes on the device it can work)
MTP
Video recording (It doesn't really work in other devices with CM12.1 base.)
Screen delay in refresh (related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin)
the charging icon doesn't work properly: when the device is not on charger still shows it's charging (when I unplug the cable the message appears: "Charging..."
cannot boot into TWRP recovery (See Notes above)
Battery life:
In my experience the battery life is good. On standby, it can survive 10 days. (Almost 11.) I have checked once or twice daily during this period.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pictures:
App drawer
Top menu
Settings
About product
In case somebody missed these I would like to highlight some improvements since day 1:
Now both the kernel and twrp can be flashed as an .img from twrp (no need for PC and heimdall anymore)
Plus I uploaded a kernel with Flatpak support
With kernel07_flatpak, I have installed Flatpak and Angelfish but got an error when started Angelfish.
It looks like this is a limitation of the old kernel, but there might be a workaround.
I'll keep you posted.
With kernel12_mtp, MTP works. (and bluetooth partially)
The soft keys each side of the home button are used as notification leds. As this device doesn't have leds, the softkeys can be re-used as "leds". They do blink if the device is fully charged or there is an unread incoming text message. When the device is on charger they are on, otherwise both of them are off.
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Galaxyninja66 said:
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Click to expand...
Click to collapse
Sorry for delay in my reply.
The necessary repos in github are:
local manifest
dhd (in here the dhd submodule has to be refreshed from mer-hybris repo upgrade-3.2.1 branch)
droid-hal-i9100
droid-hal-version-i9100
android_device
kernel
The file (path to android base kernel image) command gives me: "Linux kernel ARM boot executable zImage (little-endian)"
A new image has been generated and can be downloaded. This one includes the patch of reusing the two softkeys (each side of the home button) and they do work as a notification leds!
Currently I am working on the mobile data and bluetooth (this latter partially works but is not reliable yet).
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Galaxyninja66 said:
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Click to expand...
Click to collapse
I am not sure what you d understand under 'any service' but except the mobile data, everything else works fine (calls in/out, texts in/out).
I don't know the difference between the i9100 and i9100m but on the internet you probably can find something about it.
One suggestion, before you start porting, install an android onto and boot into that and note the mounting points. This can save a little time when you need to set the fixup_mountpoints in hybris-boot.
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
I think the reason why this doesn't get more hype because this is a very old device and except some old fashioned folks like us, not many are using anymore. I don't mind it because this is my hobby. I am going through a to-do list until all I wanted works.
Currently, as the new version 3.3.0.14 is out) I am working on to update my port to 3.3.0.14. Unfortunately currently there is no OTA but hope eventually it will be sorted.
Changing the pixel ratio is not essential as the default 1.0 is ok-ish. I have found the 0.82 better so I included the icons into my image. As the script (kimmoli-diyicons.sh) is also included, we just need to run one command as root. I may try to set the 0.82 out of the box but currently it is not my to priority. As I will need to re-build everything for 3.3.0.14, I will try to set 0.82 in the pattern file.
Please keep me posted with your progress.
edp17 said:
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
Click to expand...
Click to collapse
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Galaxyninja66 said:
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Click to expand...
Click to collapse
I remember that I built gstreamer and un-commented the related stuff in the pattern file. I don't know whether easier to build now because I don't know how difficult it was before. I only can compare this project against my hammerhead one a few months earlier. For the hammerhead I needed to build the image with MIC, now the rpm/dhd/helpers/build_packages.sh command does everything for you. (For this you need to export the RELEASE, EXTRA_NAME values in your .hadk.env)
Unfortunately I still don't have OBS account so I couldn't add this device into the wiki. Thank you for doing that! Unfortunately new account creation on the mer bug wiki is restricted at the moment.
I have checked the wiki you have added and if you don't mind I would like you to amend a few things:
LED works (the two softkeys have repurposed as notification leds)
GPS works
Sensors Gyro and Magnetometer both work
(I need to double check the RTC alarm and USB net.)
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Galaxyninja66 said:
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Click to expand...
Click to collapse
Thank you for the update and for the congrats but I think it is only partially my merits. I probably couldn't done this without the help of sailfishos-porter guys.
As I mentioned in the main comment, I am using my S2 with this image on it as a secondary phone already. Mobile data is not crucial as my main phone can be a hotspot and with my S2 I can connect to it via wifi. Of course this doesn't stop me trying to make that work. (The BT was almost done but I then broke something.)
The camera is a different story. Afaik the video recording generally is broken in the CM12.1 base that I chosen for this device. (That doesn't work on my hammerhead which is also using CM12.1 base.) So I think that will remain outstanding unless I try to port with a different android base.
I think will stop with this for while because the new version (3.3) is out soon and would like to upgrade to it first, then continue working on the missing bits.
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Galaxyninja66 said:
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Click to expand...
Click to collapse
I think the video recording also works in cm12.1 on the android side, but the problem is a, between the android and Sailfish or b, on the Sailfish side. I am not sure but when I tried to fix it on the hammerhead (same cm12.1 base) I was told the recording was broken in general with cm12.1 base. I'll see how it works (what I can do about it) after Sailfish 3.3 is out.
Have you thought about to purchase a cheap android phone to use as daily driver and using the i9100m for your Sailfish project? (You probably can get a decent second hand android phone for sub 20 maybe with better spec than the i900.)
Thanks again for the kind words. This phone (the S2) is my favorite old friend. It is indestructible . I have soft bricked so many times and managed to install many other OS but as couldn't find Sailfish OS, so I though worth a try to port. And with support of the Sailfishos-porters guys, my dream became real :good: .
Sailfish
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I am glad you managed to install it. Have you tried to re-partition the internal memory as I advised?
Yeah, the bt and mobile data is still WIP status. Hopefully will have some time to complete them soon.
For the browser, the native one doesn't hang for me. You can try to look for and install one from the openrepos. (I suggest to install the Storeman as you will find more useful apps for Sailfish OS.)
I don't know linusdan but have seen he has checked this post already. Hope he also found it useful.
I am aware of the postmarketos for the S2 and tested it on my S2. At that time (about a year ago) there was no mainline linux kernel option for the S2. Unfortunately the mainline kernel doesn't help with Sailfish because the Samsung proprietary blobs are missing from there. This means Sailfish wouldn't work. It needs the drivers from the Android layer.
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I forgot to mention that there should be a folder '/edp17packages/bluetooth' where you can find the missing packages for the bt. Once you installed it, probably only need to tweak some config files and need to create some scripts. I currently started working on it.

[ROM][TESTING] postmarketOS on Sirius

Disclaimer: I am not responsible for your device malfunction, software error, power failure, imei loss, ..
Hello, it's been a long time since I've done anything for mi8se. since it's my daily use phone, recently, I have some free time to play with mi8se
This is postmarkerOS. It is not android : postmarketos.org
Status:
Working:
Boot
Charging
Display
Touch
Button
Battery
Not working:
Other things not mentioned here
Link of postmarketOS with Gnome : https://drive.google.com/drive/folders/1QPGqo3fzZZQG68BzxnJamaPYIzkc69nU?usp=sharing
How to install : read #4
I have successfully built postmarketOS with Gnome UI about 3 days ago after spend 2 days from scratch. Sorry for being late, I'm very busy right now
If someone can fix what not working, you're welcome
Source code:
Kernel : https://github.com/thinhx2/msm-4.99 branch pmos
Device config : https://github.com/thinhx2/device-xiaomi-sirius
Linux config : https://github.com/thinhx2/linux-xiaomi-sirius
Thank:
Google
Xiaomi
postmarketOS team
@UIxDess
My old laptop ??
Picture
Sorry for quality of images, captured from a lumia prototype 2014 ??
Gnome and plasma mobile is booted but plasma mobile is pretty lag
plasma-mobile : https://drive.google.com/drive/folders/16raF9efH8u1KxGv0GFYZejLOJ8YiEykC?usp=sharing
plasma-mobile-extras : https://drive.google.com/drive/folders/1zNZZN9xS9V6ngPfL6QT2VpwQUHnE4EI0?usp=sharing
How to install:
1, download this folder : https://drive.google.com/drive/folders/1Kg-PyOFQRqCjN7LnAqy-joRpIVGsWLAG?usp=sharing
2, you must use fw10 on mi8se
3, go to custom twrp/shrp
4, unmount system, flash pmos-sirius.zip
5, you'll see it cant install, go to main menu of recovery,unmount system, push/copy folder chroot to /tmp/postmarketos by adb or file manager.
6, flash pmos-sirius.zip again
7, when it done, reboot and relax
8, default password of Linux User is 12345
cant login
linux user cant login
tdsngl said:
linux user cant login
Click to expand...
Click to collapse
Sorry for my mistake, default password is 12345
Can dual boot with android??
ok.
thanks,so I knows
Hi There, First off. Thank you for all your hard work. I was able to build PostmarketOS by following their build tutorial and reading/interpreting everything you have posted here and on GitHub. It was great fun but sadly even though the build completed successfully I was unable to get my Sirius to boot it.
I tried the build you supplied here as well, noticing that you used a kernel fork, however I also can't get this one to boot.
I've tried from older official FW, all the way down to android 9. Nothing seems to let me boot the postmarket os Image. Do you remember which FW you were on when this worked? Was there anything special you did during the build to get the image to boot on mi 8 se?
Regards,
Dom
It will be great if we have a fully working stable PostMarketOS.
sinan33 said:
It will be great if we have a fully working stable PostMarketOS.
Click to expand...
Click to collapse
Maybe not fully stable, but with GPU acceleration.
thinhx2 said:
Disclaimer: I am not responsible for your device malfunction, software error, power failure, imei loss, ..
Hello, it's been a long time since I've done anything for mi8se. since it's my daily use phone, recently, I have some free time to play with mi8se
This is postmarkerOS. It is not android : postmarketos.org
Status:
Working:
Boot
Charging
Display
Touch
Button
Battery
Not working:
Other things not mentioned here
Link of postmarketOS with Gnome : https://drive.google.com/drive/folders/1QPGqo3fzZZQG68BzxnJamaPYIzkc69nU?usp=sharing
How to install : read #4
I have successfully built postmarketOS with Gnome UI about 3 days ago after spend 2 days from scratch. Sorry for being late, I'm very busy right now
If someone can fix what not working, you're welcome
Source code:
Kernel : https://github.com/thinhx2/msm-4.99 branch pmos
Device config : https://github.com/thinhx2/device-xiaomi-sirius
Linux config : https://github.com/thinhx2/linux-xiaomi-sirius
Thank:
Google
Xiaomi
postmarketOS team
@UIxDess
My old laptop ??
Click to expand...
Click to collapse
Thank you for developing the ROM for Xiaomi 8SE, but the download link has expired. Can you send it again
Thank you for developing the ROM for Xiaomi 8SE, but the download link has expired. Can you send it again
Mras.a said:
Thank you for developing the ROM for Xiaomi 8SE, but the download link has expired. Can you send it again
Click to expand...
Click to collapse
I would reccomend you to setup chroot inside android, this rom does not support audio input/output, internet access, hardware acceleration etc.
You can use termux for audio, termux-x11 for fullscreen display(latest version support touch input), and you can either use virglrenderer on android gl es or compile turnip+zink in chroot for utilizing GPU.

Categories

Resources