IIf indeed for some reason I am NOT in reality DeOdexed after applying what was supposed to be a DeOdexed 2.3.13 and 2.3.15, then i am not sure why it turned out that way. I just checked the system/app folder and there are indeed files in there that say .odex at the end. So perhaps a system format WAS necessary even though the directions on the 2.3.13 and 2.3.15 pages said to do so only if the update failed.
Hope this all helps and thank you so much for the quick reply.
Dave
You have confirmed my suspecions and the results of my investigation.. here is the deal I have found.
The "leaks" are missing 2 files in framework folder as compared to the stock OTA 2.2 I compared it to.
Those files are:
1- android.test.runner.jar (which is not originally odexed, there is no matching odex file in the OTA)
2- guava.jar and guava.odex .. obviously an odexed file, but it si not showing up in the "leaks" at all , Deodexed or Odexed.
When these 2 files are still in framework..somehow (don't ask me, I have no clue) it is evidently interferring with the services.jar file in some fashion as the code changes for the text colors do not show up.
I did delete the guave.jar file when I manually dleated all the .doex files after I THOUGHT I had transferred good Deodexed framework files.. that experiement did show that the clock was white on the bext boot up, but I had other issues requiring a Nandroid restore.
You can try one of 2 things.. Rename that file to bac and reboot and see what happens... if there are no side effects (trust me it will be obvious) and the clock day/date ERI and now changed leave it at that. IF NOT, then do the same for the Android-Test-Runner and reboot to see the effects.
Even if you get into a bad reboot or bootloop , pulling the battery in the middle of the next few reboots atempts will eventually throw you into clockwork recovery so you can restore a backup.
The other thing you can do, will solve the issue, BUT doesn't help me research :-( .... is to download the DeoDexed 2.3.15 (forget 2.3.13, waste of time IMHO) and install that as specificed at MDW BUT but sure to add the FORMAT SYSTEM step..this will delete as those left over pecky files (app and framework), you can then install my 2315 Theme and be good to go. FWIW, I ran the DeoDexed 2315 leak exclusively from the day it came out until he OTA dropped and never had a single issue AND all of the current DeOdexed Themes are based on it. (until I get a PERFECT DeOdexed version of the OTA 2315 I can trust, I will still use it)
This is why I complain so much about users and even Devs mixing versions like this, and it is aplified on a Droid x (and 2) becuase all these leaks are only 1/2 leaks (system files only) and not the whole leak/update... I wish we could ALL get to OTA 2.3.15 so we can get everything uniform and smooth...at least for a while. Then we could could all make much better more reliable Themes, ROMS, and Mods....and you guys would spend more time enjoying those mods instead of troubleshooting "mixed nuts" like we both are now. (and I could be releasing more Themes)
Now if some one smarter than me could tell us what those 2 pesky files are for and why they aren't in the 2315 leak, but are in the Official OTA 2315.. I would be a happy camper. I have done a Google search and there is a lot of mentions about the guava file, but none seem to relete to what it does or even framework (more about lib folders). Also it seems there is a "bad or double version"??? o this in the Droid 2 Official software that needs to be deleted before the D2 framework can be successfully DeOdexed according to some accounts across 3 forums... very odd.
