Database Users

[09-06]SailfishOS & Multirom. How to set up guide

Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.

I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.

anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did

Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.

anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android

Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish

anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...

v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.

mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).

Works nicely on my n4. Looking for getting gapps to run....

mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic

iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.

iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.

mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.

iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).

Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you

Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...

Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?

Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...

Works perfectly on my oneplus one

cm-11 successfully ported to SM-T900 (Tab Pro 12.2

Updated 10/22/2014 10:20pm EST - Thread closed see new thread http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/cyanogenmod-tab-pro-12-2-sm-t900-t2914991
chhaggerty has now posted his source built cm11 for SM-T900 that has a full OP, why this post no longer is needed. Additionally, his build is the most complete and also runs smoother than its predecessors. However, without the initial work carried out by crpalmer, Valera1978 and bonuzzz this release would not have seen the light until much later, if ever.
I know this is not the correct place for this info, but the original thread is very, let's call it, chaotic. The OP is not maintained (do not flash .zip-files available in the OP), and it's very hard to find details unless you participated from the start and followed the development. Further, I believe this is of public interest for the community members, as the T-900 has not seen much development until now.
Tired of your laggy base ROM?
Valera1978 and bonuzzz from the P-900 forum has successfully ported crpalmer's cm-11 T-520 picassowifi to the SM-T900. The cm-11 ROM is very snappy and responsive, there is no reason not using it as a daily driver. Before flashing it's recommended to update to TWRP 2.8.0.0, see my note for details
Attention: This is a non-stock based ROM, why you also need to install gapps (set of packages - full, mini, micro, nano, pico). I prefer the Pico in order to be in control of the maximum of what is installed, but that's up to you.
Finally: Don't forget to make a backup of the ROM you currently have installed.
Do you want to try but are afraid to make the change? bonuzzz has released MultiROM for T-900. This will allow keeping your TouchWiz ROM, and concurrently install cm11. You can then, seamlessly, go back and forth between the two alternatives.
Alternatively, you can also try it the traditional way. However, some people had issues in going back to StockROM after having tried cm11, but after flashing bonuzzz's MultiROM kernel on the top of the TouchWiz ROM, it boots up immediately and radically improve the performance, isn't that a bonuzzz.
For the cm11, there might be some minor, non-verified, remaining issue(s);
- auto-rotation - screen orientation is always presented in landscape mode, independent of settings. However you can use an app, eg Ultimate Rotation Control, to lock the screen in any direction.
- IR blaster - I used IR 2.0 and had no issues with TouchWiz, but no reaction with cm11
I will try keeping a POST up to date with latest developments
- LED notification lights - don't look for it, functionality is not supported by the device
- Proximity sensor - don't look for it, according to Samsung's specs the device does not have one
Details of what has been fully tested can be found HERE
Valera1978 said:
cm-11-20141012-UNOFFICIAL-v2wifi
Merge with latest official nigtly 20141012.
Also included new kernel.
https://drive.google.com/file/d/0B-6...ew?usp=sharing
Please test it.
Click to expand...
Click to collapse
Note: the BROWN text contain links to the actual postings

Need help installing the rom
arcadia2uk said:
Updated 10/18/2014 08:40am EST
I know this is not the correct place for this info, but the original thread is very, let's call it, chaotic. The OP is not maintained (do not flash .zip-files available in the OP), and it's very hard to find details unless you participated from the start and followed the development. Further, I believe this is of public interest for the community members, as the T-900 has not seen much development until now.
Tired of your laggy base ROM?
Valeria1978 and Bonuzzz from the P-900 forum has successfully ported crpalmer's cm-11 T-520 picassowifi to the SM-T900. The cm-11 ROM is very snappy and responsive, there is no reason not using it as a daily driver. Before flashing it's recommended to update to TWRP 2.8.0.0, see my note for details
Attention: This is a non-stock based ROM, why you also need to install gapps (set of packages - full, mini, micro, nano, pico). I prefer the Pico in order to be in control of the maximum of what is installed, but that's up to you.
Finally: Don't forget to make a backup of the ROM you currently have installed.
Do you want to try but are afraid to make the change? Bonuzzz has released MultiROM for T-900. This will allow keeping your TouchWiz ROM, and concurrently install cm11. You can then, seamlessly, go back and forth between the two alternatives.
Alternatively, you can also try it the traditional way. However, some people had issues in going back to StockROM after having tried cm11, but after flashing Bonuzzz's MultiROM kernel on the top of the TouchWiz ROM, it boots up immediately and radically improve the performance, isn't that a Bonuzzz.
For the cm11, there might be some minor, non-verified, remaining issue(s);
- auto-rotation - screen orientation is always presented in landscape mode, independent of settings. However you can use an app, eg Ultimate Rotation Control, to lock the screen in any direction.
- IR blaster - I used IR 2.0 and had no issues with TouchWiz, but no reaction with cm11
I will try keeping a POST up to date with latest developments
- LED notification lights - don't look for it, functionality is not supported by the device
- Proximity sensor - don't look for it, according to Samsung's specs the device does not have one
Details of what has been fully tested can be found HERE
Note: the BROWN text contain links to the actual postings
Click to expand...
Click to collapse
Hello,
I tried to install your rom but it gave me an error. I installed twrp 2.8 and then I flashed the cm11 rom. See attached picture for the error.
I am very new in flashing stuff so I hope someone can help me and tell me what to do.
Many thanks.

Deslang16 said:
Hello,
I tried to install your rom but it gave me an error. I installed twrp 2.8 and then I flashed the cm11 rom. See attached picture for the error.
I am very new in flashing stuff so I hope someone can help me and tell me what to do.
Many thanks.
Click to expand...
Click to collapse
I hope that you started by making a backup of your current ROM. Thereafter, I assume you did a factory reset, and also wiped your system.
However, It looks like you are installing gapps before the ROM, it should be the other way around. First ROM, then gapps.

[Q&A] [FAQ] CyanogenMod 12 Noob-Friendly Q&A and FAQ

This thread is dedicated to those spamming mukulsoni's development thread.
Ask anything and get answered!
Posting Rules:
- English language only (but feel free to PM me in Arabic or French)
- No bad language. Explicit content and language, slandering, political talk, and any other inappropriate content will be removed by the moderation team according to the forum's rules.
- Slang and informal English is not prohibited as long as it does not contain bad language.
- PLEASE, PLEASE, PLEASE read the Frequently Asked Questions (FAQ) below before asking! Otherwise, your post would be considered spam and removed appropriately, with the moderators taking action as required.
- I do maintain this thread, but I'm only 15 years old and do not have Internet access at home, so I do this from school.
If I do not answer your question, somebody will.
People who break the rules are too be reported, at the nearest available opportunity, to the moderation team.
Latest Version:
This is the official link by the developer. Please do not make mirrors, as he needs to keep count of the number of downloads!
Link:
ROM:
Gapps:
SpiritF (FM Radio):
Code:
Changelog:
For all downloads, please visit the original thread at
Frequently Asked Questions (FAQ):
In the beginning, thanks to @Ahmed_Khalifa for inspiring this by leading me to a similar FAQ to get inspiration from!
a. Hardware
I cannot hear the caller's voice on SIM 2, nor he/she can hear me.
This is a known bug and the developer is working hard on it.
The problem is that he does not use Dual SIM, although he has a SM-G7102, and relies on testers, which slows down fixing.
The phone takes 10-15 seconds to boot up, and the boot animation is really slow. Is that a warning from God that I watched too much porn? (Screen lock bug users only)
Not in this case. The ROM build for screen lock bug users has that problem. It's a known bug.
But it might be a warning from God, too. Porn is bad.
The screen turns off, but would not turn on again.
Flash the latest version, the one marked "for screen lock bug users". Note that video recording is broken on that.
I cannot make or receive calls, SMS messages, or use mobile data on both SIM cards.
You aren't using the latest version of this ROM.
The <camera/Wi-Fi/Bluetooth/Auto rotation/whatever> doesn't work.
You aren't using the latest version of this ROM.
<Insert something here> is broken.
Make sure you have the latest release (from the link above) and that the broken feature is not on the Known Bugs list.
What variants of the Grand 2 does this ROM work on?
As of the build dated Feb. 11th, 2015, this ROM only works on SM-G7102 (the 3G Dual SIM international variant).
Users of other variants, such as the 4G LTE SM-G7105, the Brazilian SM-G7102T, and other variants would have to avoid flashing this.
Video recording does not work.
If you have faced the screen lock issue and flashed the build for screen lock issue users, video recording would not work.
Update: VivaVideo works.
FM Radio doesn't work and shows this:
FM operation failed. If the problem persists, please turn off FM and turn it back on
Click to expand...
Click to collapse
This issue occurs when using the bundled CodeAurora Forum FM Radio app.
To fix it, download the open-source SpiritF app, open it (obviously), and turn FM Radio on with the headset plugged in. You won't hear anything. Press "Menu" and choose "Analog". You will hear radio come on. Choose " Menu" then "Digital" again to get louder volume.
b. Programs and software
How do I enable root access?
Two methods:
Method 1:
Flash the SuperSU ZIP fire (UPDATE-SuperSU-*.zip)
Method 2:
- From About Device in Settings, tap the Build Number seven times to enable Developer Options.
- Go back and choose Developer Options, then choose Root Access. This option allows you to enable root access for ADB, apps, or both.
Can I import or export contacts to the SIM card?
No. AOSP-based ROMs, including CyanogenMod, do not have the ability to access the SIM card contacts due to legal restrictions.
Why are many CyanogenMod 11 options, previously found in Settings, gone?
The CM team is still integrating CyanogenMod sources into AOSP Lollipop. You can check CyanogenMod's website for details.
In the meanwhile, many Xposed modules can replicate that functionality for you, most notably GravityBox [LP].
Can I upgrade from CyanogenMod 11 and keep my apps and data?
Yes, but you will have to set a new pattern if you had a pattern lock 4x4 or over (as you'll face a glitch where any pattern unlocks the screen) and you will lose custom notification panel tiles, system apps and mods under /system, and Xposed (you will have to download the latest version by hand).
Can I upgrade from stock/GenNxt/Turbo/MicroKat/<insert stock-based ROM here> and keep my apps and data?
Unfortunately, no. You will have to wipe your /data partition prior to installing CyanogenMod.
Does DedS Kernel/Motion Kernel/<insert some kernel here> work on CyanogenMod 12?
No. TouchWiz kernels do not boot AOSP/CM ROMs.
Where is the Google Play Store? Why is it in a different download?
To get it back, flash a Google Apps (commonly Gapps) package, available as a separate download.
Google Play Store, and other Google apps, are not included in AOSP-based custom ROMs, like CM, because of a legal requirement imposed by the CyanogenMod v. Google lawsuit, where Steve Kondik, founder of Cyanogen Inc. (formerly CyanogenMod), was accused by Google of stealing intellectual property (Gapps + proprietary drivers), so he offered to remove them from his ROM. As a result, all AOSP-based ROM makers were required to perform the same action.
<Some app> does not work on this ROM, while it worked on <CyanogenMod 11/stock/some ROM>!
It may not be compatible with Lollipop/Android Runtime (ART). Check with the app's developer for an updated version.
Freedom does not work on this ROM! Do I have to actually pay for in-app purchases?
In fact, it doesn't work on all Lollipop ROMs. But don't worry, you ain't paying to get $9999 in Jetpack Joyride. You can use Lucky Patcher.
Why isn't this ROM updated via CyanogenMod Updates?
This ROM is an UNOFFICIAL build.
However, the developer offers an alternative that he maintains if you donate.
Can I use proprietary Samsung apps and features like S Note, Smart Screen features, GALAXY Apps, and Air Command?
No, due to the unavailability of Samsung framework resources in CyanogenMod. Why not switch to some stock ROM instead?
Does GravityBox [LP] work on this ROM?
Its developer says no, but I confirm it does. In fact, some options even work on TouchWiz!
OTA Terms and Conditions:
For Donors of this ROM:
1. Donation is an appreciation and a kind gesture toward the developer's hard work and his valuable time.
2. Being a donor means you can not expect or demand any fix for bugs or any mishappening with your device
3. Please do not donate if you think you are PAYING FOR PREMIUM SERVICE and expecting a lot like OEM customer care, the developer is not here for your service as he is making this rom just his love to android development.

Reserved
Reserved

WaseemAlkurdi said:
This thread is dedicated to those spamming mukulsoni's development thread.
Ask anything and get answered!
FAQ:
Will be added soon.
Click to expand...
Click to collapse
Camera app frequently stoped working..i am on 2.1..i cleared cache and data also..

Hello I have a problem of screen pinning
Please can any1 help me out here

xposed? will it work for our cm12? anyone here tried already?

prakash87 said:
Camera app frequently stoped working..i am on 2.1..i cleared cache and data also..
Click to expand...
Click to collapse
meetpanchamiya said:
Hello I have a problem of screen pinning
Please can any1 help me out here
Click to expand...
Click to collapse
doofenshmatz said:
xposed? will it work for our cm12? anyone here tried already?
Click to expand...
Click to collapse
Try Google Camera @prakash87
Explain please @meetpanchamiya
Xposed doesn't work yet on ART and Android 5, which is why I'm still a CM 11 holdout @doofenshmatz
EDIT: Lollipop got Xposed.

Hey, why i can't install some apk on v2.0
But the application i've successful installed on v1.3

xposed worked for grand2 version cm12 android lollipop
doofenshmatz said:
xposed? will it work for our cm12? anyone here tried already?
Click to expand...
Click to collapse
i already test it!! and it worked for me!!
for more detail ask me!!

solution!!!
GDay21 said:
Hey, why i can't install some apk on v2.0
But the application i've successful installed on v1.3
Click to expand...
Click to collapse
go to setting--->apps---->menu---->preferred install location and change it to internal storage
worked flawless for me

doofenshmatz said:
xposed? will it work for our cm12? anyone here tried already?
Click to expand...
Click to collapse
Recently xposed released for cm12 lollipop.it is working

sim 2 network change
I am on 2.0.1 Version
How to change sim 2 network mode from 2g to 3g or vice versa?

Shishir Singhal said:
go to setting--->apps---->menu---->preferred install location and change it to internal storage
worked flawless for me
Click to expand...
Click to collapse
well done, thank you so much bro

video saving..
guys help me out here , I tried cleaning data for camera
also tried google camera app
but video does not save..... I am gonna try motorola camera ... is there any other work around?

meetpanchamiya said:
Hello I have a problem of screen pinning
Please can any1 help me out here
Click to expand...
Click to collapse
As stated before for some reason the screen pinning does not work with normal keys so a solution for now is to enable soft keys by adding
qemu.hw.mainkeys=0
To the build prop in
/system/
And saving it and restart your device

faraz shafi said:
I am on 2.0.1 Version
How to change sim 2 network mode from 2g to 3g or vice versa?
Click to expand...
Click to collapse
first u have to be sure that ur sim 2 is default for mobile data.
now go to system settings.
system profiles > default (settings) click on the gear icon > preferred network type > then choose!

Xposed module - Xhalo floating windows works!
try it guys!!
HERE ARE SCREENSHOTS :​

prakash87 said:
Camera app frequently stoped working..i am on 2.1..i cleared cache and data also..
Click to expand...
Click to collapse
it is because you use location tag. so after clearing camera data and cache, relaunch camera and make sure you don't activate location tag. the first launch of camera will promt you whether you want to activate location tag or not. if you activate it, you will face the camera bug, but else if you don't activate it the camera work perfectly for taking photos. there is no need to install google camera or motorola camera. hope it will be help for you and others.

How to download videos from internet on cm12?

sim 2 messaging
Why cant i send msgs from sim 2 it shows 'msg nt sent. Touch to reviewew and try again '
Version 2.0.1

Hi, I can't hear any sound from sim1 when calling. How to fix it?
Sent from my SM-G7102 using XDA Free mobile app

Galaxy S3 [I9300] - Basics,Best Performance Package - Mod's and ROM's & Kernels

So, I have been using an S3 {yeah S3 , i know old, but duh i just love it } for over 3 years now . I started out as a complete noob, still am, and S3 was the first phone that i started working on. Over the years i have tried many custom ROM's , Kernel's and MOD's and i have tried here to create a List of Best Performing Custom Items over the course of 1 year, with special care for people like me who have just started out in the world of android, So here goes. {in 4 steps} :-
<1> Best "FAIL-SAFE" Method of Rooting/Installing a custom ROM - I know most of the people are afraid of bricking their device's, the first time they root. I have been in that situation and had my phone soft bricked many times while trying out different thing's. So the Most FAIL-SAFE Method that i have come up with is this:-
Many people suggest rooting the devices first and then installing a custom ROM. I have tried to do things a little differently so that the first timers can get comfortable.
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
B. Now that your device is has CyanogenMod, you get a rooted device and a custom ROM. But the problem with Cyanogen is that the Custom recovery which it provides has very limited options available. So the next step is to go to Google Play Store and download "TWRP Manager" or "ROM Manager" [i personally use TWRP]. This application will help you to Install the TWRP or CWM recoveries on your Phone. The process is fairly simple, After Installing the App, Choose your Device Model and Version and Let the app do the rest of the work. PS the apps require ROOT access which your phone can provide now.
C. By now if all the steps are performed correctly [very less chance of something going wrong because most of the tings are done automatically] your respective device should have a custom Recovery installed. Next and Most important step is to Create a NANDROID BACKUP [basically an ultimate backup to restore everything]. Go to recovery mode [Home+Volume up + Power button] and select backup, and make a complete backup on your SD card. It's really important to create a Backup before doing anything. This step must not be skipped in any case.
D. Now it's time to let your imagination run wild xD, Download custom ROM's, Kernel's MOD's etc and just copy the zip's to the SD card and install them using the recovery. In case anything goes wrong Just restore from the Backup you made earlier.
[PS: Update your backup's regularly]
<2> Now's the list of My Personal Favorite's which Have Improve the overall Performance of My Phone Greatly. All the ROM's, Kernel's etc have been personally tested by me for over 3 month's for Issues related to Stability, Performance and Bug's . I have tried to put forward the Best package for optimal performance.
1. Recovery [doesn't affect much] - - TWRP Recovery: Personally "Team Win Recovery Project (TWRP)" is my favorite because of it's easy to use touch control's , it's efficiency and Design. I like the cool blue texture theme of TWRP and the speed with which it create's backup and install's new things. The performance of the Phone does no depend upon the Recovery though and you may choose whichever recovery you are comfortable with.
2. ROM - BlissPOP v4.0.3 (CM 12.1 base) : Yes i have chosen this ROM out of the many other i tried. The reasons are very simple, This ROM provides outstanding stability and Performance to the device. There is no bloatware in the ROM and there are simply hundred's of features available for customization. It's compatible with generally all the Kernel's and Mods available for your device and the regular Nightlie's are an added bonus. It's the only ROM based on Lollipop(5.1.1) in which i haven't found any Bug's or stability issues.
Many people told me to try Paranoid ROM but personally i find Paranoid a little buggy, and i found that the PI controls and Halo, due to which the ROM is popular are not of any important use to people like us. They only add a touch of appearance to the device [strictly my view and i mean no offence to any other person ].
3. Kernel - Archie kernel for Galaxy S3 - http://forum.xda-developers.com/galaxy-s3/development/kernel-archikernel-v1-0-power-hands-t2785337
4. MOD's -
A. Audio Engine - Ac!d Audio - http://http://forum.xda-developers.com/galaxy-s3/development/mod-acid-audio-engine-v5-0-samsung-t2002197
Viper4Android -http://forum.xda-developers.com/showthread.php?t=2191223
6. Root Applications -
A. Titanium Backup:
You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. Available on Google Play
B. AdAway for Android [built-in app in BlissPop ROM]:
to block ads on your Android device this app is not avalibale on the playstore but you can still install it from this link
C. Greenify:
Is a good application to make your Android device more faster, by hibernating the background apps that you don't use. this application is completely free. Available on Google Play
These are the only Apps which i find useful in the long run as i have to use them constantly. Rest application's are used from time to time but not regularly. So this is My List, i'd be glad if anyone want's to add to it ^.^
I'd Like to Thanks the Amazing People who have Made the above Programs to make our Phone More performance and Appearance efficient. ------> CyanogenMod community, BlissPOP community, xda developers, Jeeko, JustArchie, amarullz, the Ac!d Audio Engine Team,zhuhang(Viper Mod), TWRP team.
Give a Thanks if u were helped by the post
================================================================================================================
Intense Testing Period -> Over 8 months [tried the new Lollipop ROMS's , over 20 kernels, Latest Android M ROM's , some personal opinions
================================================================================================================
Firstly sorry, for the delayed updates, i have been a little busy trying to develop my own ROM (surprise! surprise!, not for S3 unfortunately thought as i can never come close to the current ROM wiz's ), now in the second edition , I have tried to utilize my knowledge over 8 months to put up a new more enhanced guide and have also put up common and uncommon bugs which I experienced along the way and have provider the working solutions for them. Also I am extremely sorry for all those broken links and not working Mods, i'll try to keep my list precise, sharp and accurate this time.
1. Alternate method to Root (super easy, risk free, takes at maximum 5 minutes) - {for windows running PC, stock ROM or any other custom ROM can be used}
So, I would still recommend using my method 1 in order to initially root your device, install a custom ROM and a Recovery as i know the fear and anxiety or every new user trying to root his phone for the first time.
Now for a little more experienced users (quickie guide) [for I9300 version] who do not want to spend a lifetime to just get their devices rooted -
(a) Download the Chainfire's AutoRoot file here and place this file on your PC.
(b) Download Odin (latest version) on your PC here and unzip the file and start odin.
(c) Power down the device, then reboot in Download Mode [ press Power button + Home Button + Volume Down Key] and press volume up key at the caution screen. (little Hint: mostly the device reboots itself when you do not press the 3 buttons at the same time, to counter this press the volume up button and the home button first and hold them and then press the power button until you see the Galaxy S3 logo)
(d) Now connect your device to your PC using a sturdy USB cable. After doing this 2 outcomes are possible:-
~1. Your device is identified by Odin and a faint blue colour is shown on one of the top tabs indicating the port through which your device is connected. In this case proceed to step (e).
~2. If your device is not recognized by odin ie no blue colour, then the drivers of your device might not be installed on your PC. To tackle this download the Driver Suite from Samsung here and run the program. If done correctly when you next connect your device the drivers should get installed and odin should recognize your device.
(e) Click the "AP" button on odin and select the "Chainfire's v-xxx .mad5.tar " file which you downloaded above, odin will then take some time to check the file and when it's ready press start. CAUTION - do not change Odin's settings and assure that Reset Runtime and Auto Reboot are selected, never select re-partition on the odin interface.
(f) After the installation is complete your device should reboot automatically and you should have SuperSU installed (indiacting 99.99% times that your device rooted successfully ).
(g) If you want you can then install a custom recovery using the method indicated in my "method 1" [above].
-feel free to message me for any doubts-
Here are some of my new recommendations based on personal experiences:-
2. ROM's - I will try to divide this section based on firstly Android System and then further based on Stability, Features, Performance. Further i will be adding 2 ROM's for Android M . [i will not be naming ROMS which have a touchWiz interface]
(A) Android Lollipop and Below
Stability - Official CyanogenMOD 11.x [kitkat 4.1.1] - Zero Doubt, this one is the most stable thing out there for S3, old, yes but well you can do anything you want with this ROM and it will not seriously bug out on you when you need it. If someone does not mind going for an older version of android and needs epic stability, just go for it.
Features - BlissPop v3.0.x [CM 12.1 base][ Lollipop 5.1.1] - This ROM is filled with features, you name it, this ROM has it, PI controls, Built-in apps including AdAway, Kernel Modifier, Greenify, SuperSU etc, seamlessly integrated into the build environment. Each and every feature of this ROM is customizable, every font, colour and animation. Simply put, for someone who needs features and customizations go for this one. On the other hand, this ROM is less stable (crashes quite often ) and provides a slightly laggy gaming experience. No bloatwares in this ROM.
Performance - ArchiDroid [CM12.1 base][Lollipop 5.1.1] - Performance, Performance and more performance, all the technical aspects of your device will be enhanced and although the customization features are minimal but this ROM turns your device into a Performance Beast. All the gamers and performance lovers, what are you waiting for
Android 6.x.y Marshmallow
1. RESSURRECTION REMIX M - Fast, Durable, Amazing performance. Fell in love with this one when i used it, and this is my current ROM, no bugs so far and have been using it for over 1 month. Immensely Customizable, no lag during gaming, an amazing upgrade from Lollipop.
2. NamelessROM 3.0 - Feature Loaded, Minimal, good Looks and customization features and of course the ever caring support team of Nameless makes this a go to ROM.
>>> A bit more studying will be required before i finally divide the Android M ROMS's based on their features, performance and stability. Will be posting the results as soon as i am finished.
3. Kernels - AGNi pureCM and Boeffla-Kernel (26-03-2016) , tied, tested and proved that they are the best on very benchmark or performance test, although battery usage is better balanced on AGNi whereas Boeffla is more inclined towards performance.
You can find the Links to all the above ROM's and Kernels and many more in this thread - here
PS - Please Post your bugs in the thread and i will do my best to try and solve them out with an easy and sure solution
Cheers!

Awesome rundown for a new user like me. I've just got an S3 after using a Nexus S for 3 years. The S3 feels like such a beast compared to it!
I want to root and put a custom ROM on my device this weekend. I currently use cm11 on my Nexus S but it's a bit slow (which is understandable considering the hardware) so I can't wait to try it on the S3. My priority is long term stability ( I don't like flashing the emperors new clothes every 5 minutes). I just want to flash a ROM and forget it.
Have you tried any slimroms on the S3?
Sent from my Nexus S using XDA Free mobile app

[email protected][email protected] said:
A. First thing to do is install CyanogenMod on your specific devices. [without rooting] , The developers at cyanogen have made an application to directly install Cyanogen to your devices from your PC like a regular Software Install. The Link and the Instructions can be found on the official Website - http://get.cm. The process is very simple and easy to do and after the install your device gets automatic root access. The xda thread - http://http://forum.xda-developers.com/android/apps-games/app-cm-app-installer-t2959922 - {you get CM - 11 from this download }
Click to expand...
Click to collapse
Hi.
Can you just go over this again. Do I use my phone to download an installer from http://get.cm, install the apk then I will have root?
edit - damn I don't use WIndows, only Ubuntu. I can't use it.
Cheers.

Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers

Hi.
I was thinking the same. CM11 all the way! I used Slimrom on my Nexus S but it was very very slow. I almost smashed my phone in frustration.
Nice tip about using a virtual machine to install cm. I will have a think about that. At the moment I have found a very good guide that involves using Heimdall on Ubuntu and Chainfire,so i will probably go for that method.
I am definitely going to try arter97 kernel. It looks immense. It has boeffla sound which I am looking forward to trying.
Sent from my GT-I9300 using XDA Free mobile app

A little Confused....???
[email protected][email protected] said:
Hi warren
Yes I have used slimrom too on the s3. Its good but as u are looking for stability I would suggest go for cyanogen because in my experience cyanogen shells out a better performance as compared to slimrom. My gaming experience was a little reduced in slimrom and I experienced a little lag but no such issue in cyanogen.
Secondly if you use ubunto I would suggest going for a virtual box to install windows and then the cyanogen application as it's the safest way to install a ROM.
U have to got to " get.cm " from both your phone and PC
On PC a windows installerbwoll be downloaded and on the phone an APK will be downloaded first install the apk the install the windows program and then continue as given in the installer setup.
Else mate, I wud say first download the stock ROM of s3 as a backup and the continue to root in the traditional way .
Any problem just ask me
Cheers
Click to expand...
Click to collapse
My understanding is that unless you rooted your S3 quite a while ago, pre 4.4.2, you can't add custom ROMs. The late-rooters would have a locked bootloader and would be severely limited on what mods are possible. Is my understanding incorrect? Thanks!

Oh my I hope this isn't the case.
Is this not just on Verizon or all s3's?
Sent from my Nexus S using XDA Free mobile app

Sorry to confuse things. I believe the locked bootloaders only apply to those unlucky enough to have Verizon phones.

Yay not me then! NP.
P.S. Verizon suck!

Yes mate unfortunately Verizon version of S3 has a locked boot loader and it does not allow the user to install a new recovery. I would suggest using Odin to auto root your phone which in turn also unlocks the boot loader. I can make a step by step guide for Verizon version if anyone requires it. Personally I prefer the international version though. It has more optimized system functions.
Tell me if u want a Verizon guide

$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!

What about /EFS backup and locked boot loader?
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?

Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.

I can't believe it I bust my sim slot! I cut my old sim card with a tool cutter and it looked good but it was a little tight going into the slot and I pulled it out and that’s when I must of bent some pins. I'm gutted :crying::crying:
Thankfully a replacement is only £3 and swapping it over looks a doddle :fingers-crossed:
Looks like I will have to wait a week until I can have a proper play. I did download BlissPop ROM and I like it. Been playing around with that all day but Its still not a phone until I get my sim in it.
You live and learn

mathew_p_a said:
I have been an old time user of android starting with sony xperia X3. I had a bad luck with that phone. When sony updated android from 1.6 to 2.2 , the phone went into a boot loop and finally got dead. I sold the battery and screen separately to make some cheap buck!!
After that experience, I have been reading a lot for rooting and there seems to be lot of info on that.
My phone model is Samsung S3 GT-I9300 international version. I am still on the stock Rom with 4.3 on it.
I tried with kingroot app and it bricked the phone and was able to recover with kies.
What I want to know is that, you have mentioned option A, do I need to make any backups (not the contacts and personal stuff which I am not worried when I start playing with the phone) of EFS partition?
Will I be able to restore to old stock ROM just by using ODIN and the firmware which is available from the market?
What I need to know is , will I need any specific data (IMEI or EFS) unique from my phone?
Click to expand...
Click to collapse
Hi Mate,
First of all, don't worry at all about the bricking thing, with the option A that i have mentioned, it's 99.99% success, i haven't found a single person yet for whom the method didn't work.
Secondly i would suggest u take the backup of your phone contacts in a vCard format using Kies first so that u don't loose them. And copy all your Personal things on your PC (pics, videos etc).
Thirdly you do not need to make a separate disk partition for the method to work, the CM installed will do it for you. Also if u have an International i9300 version u need not do a single thing yourself. Just start the setup and sit back and relax. Just follow my method to the letter and you can have a great custom ROM with root access in no time.
MOST Importantly - You can go to stock firmware of samsung but this time you will have to use odin instead of Kies to do that. You won't be able to use Kies once you have installed a custom ROM, but trust me that's a small price to pay for a very efficient ROM.
You do not need to know the IMEI or EFS number though i would suggest u still make a note of it somewhere in case ur phone is lost. Prevention is always better Message me if u have any queries. Cheers!

Warren_Orange said:
Hi [email protected][email protected]
I used Heimdall in Ubuntu and I managed to root and put SuperSU on my phone ! I also put TWRP recovery on as well and then did a backup of my stock ROM. I am now ready for some ROM flashing!
I am unsure whether to go for CM11 or something like Tamasek's CM12.1 ROM. Have you used Tamasek's ROM before? Thinking about it for the first flash I think I will use CM11 snapshot and arter97 kernel. Then I will nandroid backup and then I have a stable ROM/kernel combo to fall back on in the future.
Looking at arter97 kernel can you tell me about f2fs support and how I get it? Does it speed up certain parts of the memory? Is it worth flashing? Also, the kernel mentions touch wake. Is this available for the S3?
Cheers.
Click to expand...
Click to collapse
Hello Warren,
Good to hear that you are having fun with your new phone.
Firstly yes i have used Tamasek's/JustArchie's CM12.1 ROM and it's quite good to be honest. So first i'll talk about it then i'll come to the kernel.
So 12.1 yes, the most noticeable change android L 5.1, all good, nice appearance, but i would say just think again for a bit.
A comparison between the two is a mammoth task but i'll try to brief it for you and tell you why i like the CM11 better even though it has android KK. It's upto to you though what you choose to flash. i even have a nice tip for you in the end
So first let's see the CM12.1 -
Quite stable, i used it for like a month or so for testing and got a good result. The performance was at par with the rest of the ROM available for S3. The Graphics, Audio and Processing quality is also good and is suitable for light use. Here's the catch though, Firstly the Gaaps, many gaaps available Android L are not compatible with the unofficial 12.1 so u'll have to look around to find the correct set of Gaaps.
Secondly i personally find that the CM 11 has a much neat finish as compared to CM 12.1, i don't really care about the android version as for me if i can have all the features of android L in a more stable KitKat ROM i don't usually upgrade my ROM. THe reasons are very simple
Firstly it's Unofficial, No Nightlies, rare updates. Also the unofficial ROM is alive only till the Developer is still working on it. Once he stops his work it's a very slim chance that you can get your bugs fixed.
As for the Official one, there are thousands of forums on Solutions to various Bugs and Numerous customization options. We can't really know whether the unofficial 12.1 supports all the things available for the official ROM.
Based on Performance both the ROMS perform equally, there's a camera Bug in the 12.1 which can be a problem sometimes but rest is all good.
On a personal side [not really of importance] i like the Calculator of the CM 11 better than CM 12.1.
Now the Kernel - arter97 is simply amazing, The most noticeable changes are - 1800 GHz overclocking [yeah from 1400 to 1800 BOOM!],
the Knock feature - Tap the screen to unlock the phone, no need to use any buttons, Battery Tweaks etc.
Also it used a custom engine to allocate the Files to various partitions to the memory so yeah it saves space plus we can even Increase our RAM a bit by using the Internal Memory of the Phone.
I am a Hardcore Gamer and use my phone to the limit sometimes [ Playing Asphalt 8, Real Racing, GTA: San-Andreas, FIFA 15 and WWE Immortals can take it's toll on the phone.] these games require very high end phones but with this kernel they all run liquid smooth on my phone without even a slightest bit of lag. So yeah i would surely recommend arter97's Kernel. PLUS u get Boeffla Audio Engine which is an added BOnuS
Touch WIZ -- Not Necessary, I flashed it using TWRP and it worked Just fine.
f2f - f2f has better memory allotments and it's pre configured, we usually don't have to enable it, it's much better than extD though.
TIP - arter97 supports dual Booting so you can even enjoy cm12.1 and cm 11 at the same tine [Dual Booting i'll cover in the next post if you have a problem doing it ]
-----> Also U can use the Siyah Kernal, which work's just fine and even has an amazing Boot Image but now as much features as arter's.

straykat said:
$$-
Thanks for your reply. Sure, if you have something that will allow me to unlock my Verizon Galaxy S3 bootloader, that would be great! Is that what your verizon instructions will allow me to do? I've never heard of any way of doing this, so that would be great if it works! Btw, I am running 4.4.2. Thanks again!
Click to expand...
Click to collapse
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!

Hi..I did a search but i am completely confused and bewildered by the vast amount of different posts and opinions in threads..so i apologise if this has broken any rules.
Basically i have a stock s3 i9300 (uk) with original samsung jellybean 4.3 rom,I am getting a bit sick of it now (and the bloat) and i am looking to move on to something more appealing..I have already rooted and installed Rom Manager and CWM..i was wondering what the "Best Simplistic dark themed (small footprint) rom" to go for As i want minimal installed size to make the most of my 16gb memory,i dont mind which android version as long as the process is easy and the battery life is among the best available..And of course it is as stable as my current Samsung android rom..
i would really appreciate any valued veteran guidance..many thanks.

[email protected][email protected] said:
Hello,
well i have two methods for Verizon Phones, One i have tried myself the other one was tested by one of my friends,
For the First one -
Using Odin Use the Chainfire's Auto Root Application to give root access to your phone. https://autoroot.chainfire.eu/ This application in turn also unlocks the bootloader and hence you can easily install further ROM's. Check the Xda general Samsung forum to learn how to use Odin if u don't know , or just message me
Second - This Method requires Root Access on you r Phone. THere's an app on Google Play named "EZ Unlock" to unlock the bootloader , I think this app can help you out but i haven't tried it myself so i can't really comment. But looking at the reviews i would say that this app really works. ----> http://www.mediafire.com/download/qozzz1p43kxzs3z/EZ-Unlock14.apk
Here's a custom Recovery that can help too - http://forum.xda-developers.com/showthread.php?t=2797314
Cheers!
Click to expand...
Click to collapse
[email protected]
Thanks for the info! I looked on a Chainfire thread here on xda to see if others have done what I would be attempting to do with my Verizon S3, but I don't see anyone else saying they've used this method to unlock their bootloader & install roms. By chance, do you know any place on this forum or any others that talk about peoples' successes using this method on a Verizon S3? I'm a little nervous about attempting this method without knowing that lots of other people have done so successfully.... Thanks for your help & your understanding of my feelings on this.

Broken Link
Your "Mods" links are broken.

Sailfish OS for the Samsung Galaxy S7

I doesn't have enougth rigth to post to roms, so will post here.
WARNING! Everything you do, you do at your own peril and risk. I do not bear any responsibility for your faulty devices.
Knox will tick. ROM in alpha and not suitable for every day use.​
Installation instructions:
1. Install TWRP
2. Reboot in TWRP (Menu unlock phone - Recovery)
3. Wipe -> Format Data -> write - yes -> Enter
4. adb push <LineageOS> /sdcard
5. adb push <SailfishOS> /sdcard
6. Into TWRP: Install <LineageOS>
7. Into TWRP: Install <SailfishOS>
8. Into TWRP: Install <Audio FIX>
9. Reboot in System
Enjoy!
Sailfish OS Android HAL based on Lineage OS 14.1.
Downloads:
TWRP for herolte
Lineage OS 14.1 for herolte
Sailfish OS 2.1.4.14 for herolte
Sailfish Galaxy S7 audio fix(based on work of painted.man)
Sources:
https://github.com/Driim
Build guide can be found here.
Problems:
1. WLAN worked partially(can't remember network to automatically connect after reboot)
2. Bluetooth not working
3. NFC not working
4. Fingerprint not working (Sailfish problem)
Debug:
In Ubuntu. Connect USB cable. telnet 192.168.2.15 2323 or ssh.
Changelog:
30.03.2018
Update to Sailfish OS 2.1.4.14
GSM calls fix
12.02.2018
Working mobile data and sms.

Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?

CyanogenLover said:
Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?
Click to expand...
Click to collapse
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.

Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store

dylanneve1 said:
Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store
Click to expand...
Click to collapse
I'm focused on hardware support. Android applications did not even look.

lSDriim said:
I'm focused on hardware support. Android applications did not even look.
Click to expand...
Click to collapse
Yeah you're right.

lSDriim said:
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.
Click to expand...
Click to collapse
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!

CyanogenLover said:
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!
Click to expand...
Click to collapse
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
I update release and add new screenshots.

lSDriim said:
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
Click to expand...
Click to collapse
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.

CyanogenLover said:
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.
Click to expand...
Click to collapse
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.

lSDriim said:
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.
Click to expand...
Click to collapse
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.

CyanogenLover said:
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.
Click to expand...
Click to collapse
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enougth to port new device.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.

lSDriim said:
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enough to port new device.
Click to expand...
Click to collapse
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
Click to expand...
Click to collapse
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.
Click to expand...
Click to collapse
Ah, Ubuntu Touch! That was a good venture. Too bad it didn't last. Let me know if it works better as the HAL for your project.

CyanogenLover said:
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
Click to expand...
Click to collapse
Almost all except UI.
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
Click to expand...
Click to collapse
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.

lSDriim said:
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
Not the entire logs! Just the ones with the errors that are produced from whatever needs fixing. Some commands that output constant log updates have filters. For instance, one way I diagnose a problem on Android is connect the device to my laptop, run "adb logcat *:E", repeat the action on the device that works improperly, then stop the output (usually CTRL + C) and scan the errors for the ones about my issue. If there is still too much to sift through, I try again, setting more filters. You can learn what filters you can apply by typing " adb logcat -h".
I don't know if adb works with Sailfish, but you might could discover logcat or something similar that will filter logs and output only the relevant information. As for what you just mentioned, I can diagnose issues with many Linux-based programs. I use Ubuntu. :victory:

As for the Wi-Fi not reconnecting; On the s7 atleast (probably more) there's a line in the build.prop "ro.securestorage.support"
Change that to the opposite of what it's on

solution for audio
I found solution for audio problem.
You have to edit /system/etc/audio_policy.conf:
- Delete AUDIO_OUTPUT_FLAG_DEEP_BUFFER flag on primary audio device
- Comment sections tms and playback_record
You also can pass argument config to pulseaudio-modules-droid and set location to your correct config file instead of editing vendor file.

continua el proyecto esta bien bueno 7u7

lSDriim said:
Almost all except UI.
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
plss for s7 edge

Mujeeb64 said:
plss for s7 edge
Click to expand...
Click to collapse
I do not have Galaxy S7 Edge, but someone else can do it.