[Galaxy Tab S Themes and Apps] 3DSammy:
sp

I believe there is a mistake in the new 2.0 instructions. When you reference a new color that you defined in the apk's "res/values/colors.xml" file the reference should be "@color/my_new_color" this looks for "my_new_color" in the apk's "res/values/colors.xml" file. By using "@ANDROID:color/my_orange" you are referencing a colors.xml definition file outside of the apk itself and likely at the Android OS level. I have successfully used my own colors but needed to reference them as "@color/my_new_color". That may be why you commented "Please NOTE THIS MAY NOT BE WORKING ATM!".

Also you do not need to add the override color definitions twice as you commented with "you can add these right under it (to both settings theme and theme.settings)". You can use the inheritance that is already in the code for the style "SettingsTheme". Add this code as the first style in "res/values/styles.xml so it can easily be tweaked by other themers.

<!-- -->
<!-- START Settings Theme color pallet -->
<style name="ThemedSettings" parent="@android:style/Theme.DeviceDefault.Light">
<item name="android:colorPrimary">@color/setup_divider_color</item>
<item name="android:colorPrimaryDark">@color/setup_divider_color</item>
<item name="android:colorAccent">@color/color_accent</item>
<item name="android:colorBackground">@color/color_background</item>
<item name="android:windowBackground">@color/black</item>
<item name="android:textColorPrimary">@color/white</item>
<item name="android:textColor">@color/white</item>
</style>
<!-- END Settings Theme color pallet -->
<!-- -->

and change the "SettingsTheme" from

<style name="SettingsTheme" parent="@android:style/Theme.DeviceDefault.Light">

to

<style name="SettingsTheme" parent="ThemedSettings">

You will not have to add those same colors to "Theme.Settings" as that style inherits those colors from "Theme.SettingsBase" who's parent is "SettingsTheme".

For easier organization and theming going forward I added new colors to "res/values/colors.xml" right after the resources statement at the beginning of the xml:

<!-- -->
<!-- Start - Custom theme specific colors -->
<color name="color_accent">#ff3366ff</color>
<color name="color_background">#ff0a0a0a</color>
<!-- End - Custom theming colors -->
<!-- -->

That isolates any colors that were not already defined and will allow someone else to tweak a published theme that they "mostly" like. Plus will be easier to apply when you upgrade your OS for example to Lollipop v5.1.1 which I hope happens soon.

I'll have some comments about publishing themes by using diff and patch utilities which are available for free across Linux, Windows and OSX. But first I need to actually complete a theme especially now that I've put my framework-res shenanigans on the back burner.

Here is another valuable reference that you may want add to one of your OPs. Its another web based color utility but concentrates on foreground/background text contrast visibility. It even rates big and small text with a pass/fail grade along with interactive controls. I found it invaluable in reducing trial and error color experiments when trying to get rid of the notifications white background but not being able to change the text color from black.