Related
So i click on my explorer tab on the main screen and get a message saying "NO application found" so i try to find a back way and go to google search type in like say nfl and search then nothing wont budge. Basically i think the world icon on the main screen is gone now i want to know how to get it back. DO i have to get a new rom??
My android version is 2.2.1, running ultimate droid 2.5.0, kernel version [email protected]#2, baseband version 15.42.50.11U_2.15.50.14 any other info you need i can get just ask.
I would back up my data then either
press menu - settings - wireless and networks - mobile networkS - Access point names - menu button - reset to default, then return to the fron page and try again
then if needed
Flash the same rom again (easy option)
Or
Choose a different rom (not much harder)
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 tutorialImportant! 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/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need 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.
SourcesOur 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 tutorialImportant! 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/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need 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.
SourcesOur 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.
Hi.
My Teclast Master T10 just got upgraded to PhoenixOS 2.0.0 via OTA. I got no warning that this would make me lose widgets, which are a key feature for me. I've tried both "tablet" and "fake Windows" mode.
Is there any way to get widgets in PhoenixOS 2.0, or to get rid of it and get back to something sensible ? PhoenixOS won't even let me install an alternative Launcher...
Thanks for any help.
Olivier
obarthelemy said:
Hi.
My Teclast Master T10 just got upgraded to PhoenixOS 2.0.0 via OTA. I got no warning that this would make me lose widgets, which are a key feature for me. I've tried both "tablet" and "fake Windows" mode.
Is there any way to get widgets in PhoenixOS 2.0, or to get rid of it and get back to something sensible ? PhoenixOS won't even let me install an alternative Launcher...
Thanks for any help.
Olivier
Click to expand...
Click to collapse
Widgets are just like gadgets on Windows 7.
Why won't you get it back in Phoenix OS 2.6.7?:laugh:
No, really I'm not joking about that.
Hey - Hello. total newbie with a Teclast TBook and wanting to move to an all android system. It dual boots to wither Win10 or Android. I want to blow it all away and simply do Android. Any written step-by-step or videos available?? Russ. [email protected] (many many many thanx for any help or direction)
I found the missing widgets!!!
I've found a way to get widgets back! The side effects are we loose a little screen/desktop area on the side of the screens, and the app drawer reappears.
To accomplish:
1) Download total commander (file explorer)
2) navigate to: /System/App/FileManager
3) rename FileManager.apk to FileManager.apk1
4) reboot your system
5) enjoy
To revert back:
1) Navigate to same path as above
2) remove the 1 from the end of the file name
3) reboot your system
Thoughts:
1) You will loose a little screen space, as the resolution, screen settings will revert to Android x86
2) To use widgets long press on the home screen
3) This does not remove the Phoenix os navigation bar
4) This will get rid of your recycle bin and "my computer" functionality
The developers were really sneaky, and FileManager.apk is what's driving the hiding of widgets, app drawer, etc. I haven't figured out yet what else it manages, but I do not it is not responsible for not being able to load new launchers. Haven't figured that part out yet.
Enjoy!
~ FateWillHappen
Fatewillhappen said:
I found the missing widgets!!!
I've found a way to get widgets back! The side effects are we loose a little screen/desktop area on the side of the screens, and the app drawer reappears.
To accomplish:
1) Download total commander (file explorer)
2) navigate to: /System/App/FileManager
3) rename FileManager.apk to FileManager.apk1
4) reboot your system
5) enjoy
To revert back:
1) Navigate to same path as above
2) remove the 1 from the end of the file name
3) reboot your system
Thoughts:
1) You will loose a little screen space, as the resolution, screen settings will revert to Android x86
2) To use widgets long press on the home screen
3) This does not remove the Phoenix os navigation bar
4) This will get rid of your recycle bin and "my computer" functionality
The developers were really sneaky, and FileManager.apk is what's driving the hiding of widgets, app drawer, etc. I haven't figured out yet what else it manages, but I do not it is not responsible for not being able to load new launchers. Haven't figured that part out yet.
Enjoy!
~ FateWillHappen
Click to expand...
Click to collapse
Can you tell me how I can get access rights that I can rename the file?
I would like to make the same change to myself.
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.
Barren Lab_v3.8 apk - will not Load on my android TV- it is installed , but when it Loads -it just quits when u press ok ? is this a bug or does only run on mobile phones ? I have the same version ""working"" on my mobile.