FAQ
Q: Why theme a TouchWiz ROM? Why not use an AOSP-based ROM?
A: I tried AOSP-based ROMs. I love them. Unfortunately, I live in a low-signal area. The RIL stack in AOSP-based ROMs has difficulty locking onto a 1xRTT signal in low-reception areas. The TouchWiz RIL stack doesn't appear to have this problem. Basically, I can't make or receive calls from my bedroom with AOSP-based ROMs and this gives me an AOSP look and feel without the signal issues.
Q: Can I use your ROM as a base for some other work?
A: I don't care. I don't even care if you give me credit. However, please be sure to give credit to those that are credited in my OP. They worked very hard and deserve the kudos.
Q: Will you be updating this to use NDC as a base?
A: No. The NDC base doesn't include the framework necessary for native tethering support.
Q: Will you be including an advertisement blocker in a future update?
A: I will never include an advertisement blocker in the ROM. A developer's bread and butter is often comprised of the advertising revenue that they take in. See
this article over on Ars Technica for a detailed explanation of why ad blocking is harmful.
Q: I have a super great idea for something I'd like to see included in your ROM. How do I get it into Conquest?
A: Ask for it in the thread. I monitor this thread as much as I can. If I feel a "feature request" would not improve the experience of the ROM, or if it is not possible to implement due to technical reasons, then I won't include/implement it. Feel free to do so on your own.
Do not PM me with feature requests. Any such requests will be referred back to the forum thread and FAQs. Such requests are also far less likely to ever be implemented.
Q: Why is this ROM almost 3 times a big as an AOSP ROM?
A: The ROM zip file includes not only the base system, but also the Google apps and most of the TouchWiz apps that come with ND8. Not all of the apps that are in the zip file will be installed. You can customize your installation via the included Aroma installer which runs when you flash the ROM from recovery. So the installed ROM is really only as big as you make it.
Q: I tried to install a full release and/or update. Why can't recovery open the file/why did the install fail?
A: This is usually caused by a corrupted download. Please check the md5 of the file you downloaded against the md5 posted on this page.
Q: I didn't wipe the recommended partitions during installation/update. Why are some features not working after flashing/why is my phone unstable?
A: There are recommended areas to wipe for a reason. At this point, I would recommend starting from scratch with the latest full release.
Q: I want to install the latest release and all updates in order. I found the download link for the latest update, but where are the links for the previous updates?
A: Updates are cumulative unless otherwise specified. You only need to install the latest update after a full release.
Q: I installed the latest update. Why am I experiencing force-closes and/or other errors?
A: While installing updates normally requires wiping only cache and dalvik-cache, your experience may vary. I test all of my updates from a clean install of the latest full release and can guarantee that they will work when installed in this manner. If you experience any errors, follow the instructions for a full install.
Q: I just installed a full release. Why is my phone stuck on the Samsung logo/KT747 splash screen/boot animation?
A: This is a bootloop. Wipe system, data, cache and dalvik cache and reinstall. If you still bootloop, your phone may not be compatible with the KT747 kernel. Post in the thread with details of what steps you took to install/troubleshoot, as well as what options you chose during install (as many as you can remember), what baseband your phone is on, and what recovery you are using.
Q: I chose to make a backup prior to installing and/or wipe a partition via OTA Update Center before flashing an update, but there's no backup and/or nothing got wiped. Why?
A: Philz recovery isn't fully compatible with the scripting language that OTA Update Center uses. I do not recommend flashing updates from within OTA Update Center. You can find the files that OTA Update Center downloads in the /scdard/OTA-Update folder. Please navigate there in recovery and flash the files manually after making a backup.
Q: Why don't I have the option to install TouchWiz Messaging when I choose AOSP/Google on the dialer selection screen?
A: TouchWiz Messaging is incompatible with the AOSP in-call app (TeleService.apk) and requires the TouchWiz in-call app (SecPhone.apk) to properly send and receive messages. While AOSP Contacts works fine with the TouchWiz in-call app, the Google Dialer cannot access call history from the TouchWiz in-call app.
Q: Why can't I find feature xyz?
A: If it's not in the list of features in the OP or in the changelog, it probably doesn't exist in this ROM. Feel free to implement it yourself.
Q: I have Xposed framework and xyz module installed. Why isn't feature xyz working?
A: Some Xposed modules conflict with the functionality built into the ROM. I don't personally use Xposed, therefore I will not test for compatibility with the framework or modules.
Q: Why does my device lag/stutter/etc. when the screen is off?
A: The KTweaker app included in the ROM has the ability to set separate minimum/maximum frequencies when the screen is off (screen off profile) as a means of prolonging battery. The values can be customized in KTweaker.
Q: Why doesn't anything happen when I enable/disable "Battery precentage on icon," "3Minit Battery Mod," or "On-screen navigation bar" in settings?
A: These options require you to reboot your phone after enabling them to activate them.
Q: Where is the Roaming settings/motion settings menu?
A: The Roaming settings and motion settings menu were removed from the settings app because they are hard-coded to work only with the TouchWiz apps.
Q: Why don't the special dialer codes work?
A: Special dialer codes (a.k.a. secret codes or ## codes) don't work in the Google dialer. However, a link to the hidden dialer code menu has been added to the Developer options menu in settings.
Q: Why can't I set contact photos in the TouchWiz Contacts/People app?
A: The Contacts app was originally hardcoded to use only the TouchWiz Gallery app to select photos. This limitation has been removed as of Conquest: Singularity 4.1 with the caveat that selecting photos using Google+ Photos does not work. Most other apps should work fine. You can still set contact photos from within the Google+ Photos app directly.
Q: Why can't I send/receive MMS/picture messages in 8sms?
A: 8sms requires a little extra configuration for some users in order to get MMS working properly:
- Launch 8sms
- Open the settings menu within 8sms
- Scroll down and select "Multimedia (MMS) messages"
- Scroll down and select "MMS settings"
- Scroll down and select "Extra http headers"
- Enter X-MDN: ##LINE1## and tap "OK"
- Press back until you are back to the main 8sms screen
- Send a MMS to yourself or ask someone else to send one to you to test
If these steps don't make MMS work for you, please send a bug report to the developer of 8sms.
Q: Where can I find themes for this ROM/how do I apply a theme/how do I make a theme for this ROM?
A: All of my themes, along with a theming-related FAQ and a brief tutorial on theme making can be found
here.
Q: I sent you a private message about a problem I'm experiencing with this ROM. Why haven't you answered?
A: I don't provide support via private messages. If it's a legitimate problem/bug, post it in the forum for everyone to see. That way, there are more people that can potentially answer and everyone can also see the solution. Sending me a private message with a bug report (unless I have approached you via private message prior regarding an issue or feature testing, etc.) is a great way to get yourself added to my ignore list.
Q: I don't like your bad attitude, rude answers, or lack of willingness to help. What should I do?
A: Use a different ROM.
