Database Info

A cautionary note about the Theme Chooser app (as seen in CM7)

I've really been loving CM7. One of the features that caught my eye right away is the Theme Chooser: while it is still being ironed out, it has some great functionality.
That said, I've come to realize that it causes some very strange interactions on my phone and have stopped using it. I just wanted to give the heads up to other users.
Some specific examples:
I use Autoruns to control what apps are allowed to automatically run on my phone. After flashing CM7 and experimenting with the themes, Autoruns stopped working. Specifically, when started, it would no longer show all of the apps that have autostart privileges on the phone. Instead, it just showed a few entries for Android itself.
It didn't occur to me that the issue was because of the Theme Chooser. I thought it was just a Gingerbread and/or CM7 issue with Autostarts. But after speaking with the developer, he related to me that this was a known bug with applying a theme with the chooser. I switched back to "system" in the Theme Chooser and he was right: Autostarts returned to full functionality.
As a workaround, you can apply changes with Autostarts, then apply a theme afterwards. Your changes from Autostarts will stick, but if you need to make future changes you will need to revert back to the system theme temporarily.
The other major issue I was having was with WidgetLocker. WL would remember all my settings and sliders, but if I placed any 3rd party widgets onto my lockscreen, they would disappear on reboot. I tried all sorts of wipes / uninstalls / reinstalls, but the problem persisted. Frustrated, I again believed that this was because of Gingerbread and/or CM7. But as soon as I reverted my theme back to system in the Theme Chooser, this problem also went away completely.
I never contacted the WL devs, so I don't know if this second one is a recognized issue with interaction, but I can reliably induce the problem.
So I just wanted to pass this along. If you are using the Theme Chooser, consider reverting back to system if you are trying to investigate any weird problems. If two of the major apps that I use were affected, I'm sure some others are as well.
I'm not saying that the Theme Chooser has to be avoided: just that it should be considered as a variable when investigating buggy behavior.
(I am posting this outside the Nightlies thread as I'm not sure what other roms might be trying to user this theme chooser.)

Well that may be a valid point. However I am more inclined to believe the majority of people having app issues is because a good deal of developers have not yet updated their respective apps for GB compatibility. Seeing how there's only... what the Nexus S running official firmware? Not discrediting your statement of course. Just another idea relating to improper function or nonfunction of apps.
Sent from my HTC Incredible using Tapatalk

sunder74 said:
I am more inclined to believe the majority of people having app issues is because a good deal of developers have not yet updated their respective apps for GB compatibility.
Click to expand...
Click to collapse
I am not saying that Theme Chooser should be considered the primary culprit for all problems. Rather,
byrong said:
...that it should be considered as a variable when investigating buggy behavior.
Click to expand...
Click to collapse
That is all.
Your point about GB compatibility is of course valid, but I gave two specific examples of repeatable bugs that I was able to directly link to the Theme Chooser.
I also must not be the first person to have experienced the issue with Autostarts, because the developer responded to my initial query within minutes. I thought it was a GB issue and asked when GB would be supported. Right away he asked if I was using the Theme Chooser in one of the CM7 nightly builds, which I was.

I understand. I wonder what's happening with it specifically, have you ran a logcat while duplicating it?
byrong said:
I am not saying that Theme Chooser should be considered the primary culprit for all problems. Rather,
That is all.
Your point about GB compatibility is of course valid, but I gave two specific examples of repeatable bugs that I was able to directly link to the Theme Chooser.
I also must not be the first person to have experienced the issue with Autostarts, because the developer responded to my initial query within minutes. I thought it was a GB issue and asked when GB would be supported. Right away he asked if I was using the Theme Chooser in one of the CM7 nightly builds, which I was.
Click to expand...
Click to collapse
Sent from my HTC Incredible using Tapatalk

sunder74 said:
I understand. I wonder what's happening with it specifically, have you ran a logcat while duplicating it?
Click to expand...
Click to collapse
Here you go...
With theme set to "system" (I.E. Theme Chooser isn't active), starting Autostarts logs the following:
Code:
I/ActivityManager( 170): Start proc com.elsdoerfer.android.autostarts for activity com.elsdoerfer.android.autostarts/.ListActivity: pid=2431 uid=10112 gids={}
I/ActivityManager( 170): Displayed com.elsdoerfer.android.autostarts/.ListActivity: +486ms
With a custom theme applied, starting Autostarts now shows:
Code:
I/ActivityManager( 170): Start proc com.elsdoerfer.android.autostarts for activity com.elsdoerfer.android.autostarts/.ListActivity: pid=2646 uid=10112 gids={}
I/ActivityManager( 170): Displayed com.elsdoerfer.android.autostarts/.ListActivity: +380ms
W/AssetRedirectionManager( 170): No such resource found for com.android.music:drawable/progress_horizontal
W/AssetRedirectionManager( 170): Unable to attach target package assets for com.android.carhome
W/AssetRedirectionManager( 170): No such resource found for com.upwardspiral.theme.Red_Remix:@drawable/wallpaper
Since the Theme Chooser is redirecting the system to utilize separate resources, I guess some apps just don't appreciate having a "middle man."
I'm not knowledgeable enough to say whether:
1. Apps can be modified to deal with this issue
2. Some Theme Chooser themes themselves may be built in a such a way that causes this
3. Theme Chooser itself is the only thing that can be changed

Hmm... could it be that the theme developer didn't account for extra options that are now available? Seems to me like it could be a theme issue, not a theme-chooser issue.

Could be. That was one of the theories I posted above.

Thanks for this thread, will pass the info along to the MT4G guys.

Thanks for this note; I have been having the issue with Widgetlocker losing all the widgets after a reboot, and switching to the system theme resolved that issue.

Now that CM7 has a labeled stable release, I'm bumping this thread. A lot of people will be trying CM7 for the first time and may wonder why they are seeing weird behavior.
I've noticed a lot of people asking in the CM7 threads when the CM team will fix this issue. Please understand that the Theme Engine is T-Mobile's app: it was not written by the CM team. Any fixes that come down the pipeline for it will presumably be from T-Mobile, not from the CM team.
Also, just to add some more detail to the issue, here's a quote from the author of WidgetLocker:
[email protected] said:
WidgetLocker attempts to bind to a widget according to the SDK docs and how Google's launcher2 is implemented. CM7 w/ Theme Chooser denies WL from doing so. If WidgetLocker doesn't have access to the widget, there is nothing to display.
Click to expand...
Click to collapse
Some users have even reported this problem on their home screen with certain launchers, while other launchers are problem-free. This would seem to suggest that there are two different methods that developers are using to bind to widgets, but that is just speculation on my part.

How do I disable or remove themechoose as it comes with CM7 builds? And I'm not able to remove system apps.

mit90 said:
How do I disable or remove themechoose as it comes with CM7 builds? And I'm not able to remove system apps.
Click to expand...
Click to collapse
There are lots of ways to remove system apps. Titanium Backup is probably the easiest, and the newest versions of it also allow you to back-up system apps themselves (rather than just their data, like in the past)
You can also just delete apks from system/app using something like Root Explorer
You can also use ADB
...you get the picture: lots of options
The theme chooser apk is "ThemeChooser.apk" under system/app
You could also just remove ThemeChooser.apk from the CM7 flashable zip before you flash the next build.
All that said, removing it is not necessary to avoid interaction issues, but it's your call.

how do i remove or disable theme chooser? cm7 release htc desire

Seriously?
Sent from my ADR6300 using Tapatalk

I have been using Theme Chooser for a while now and have had no problems with autostarts, it seems to run normally for me. But the problem with widgetlocker is there, good to know the cause.

Its also in OMFGB. Just thought id put my experience in.
Id like to thank everyone that helped me root, rom, & nand.
OMFGB, Slayher#27, CWM 3.0.0.8

[Q] Market Keeps Updating!!!

I have a custom Android Market that is really nice looking. I want to keep this one, but the Market app keeps auto updating it everytime I open the app...
I've already tried the terminal "pm disable com.android.vender.updater" thing.
I've already tried to "freeze" the Market Updater app.
I've already tried to "remove/uninstall" the Market Updater app.
I've tried to clear (reg/Dalvik) cache via recovery.
Is there no way to stop the updates? What can be done??? Help!

The theme market your using most(probably) not developed/modded(maybe not completed), most themed markets prevents itself from being updated.
Edit: Are you using a ROM? If so, then which?

austrie said:
The theme market your using most(probably) not developed/modded(maybe not completed), most themed markets prevents itself from being updated.
Click to expand...
Click to collapse
I'm using Princely's Blue, black, white 2.7.5 rom... The Market version included with the ROM is 3.0.x and it keeps trying to goto 3.1.3.
I love the transparent blue, and not the ugly green/grey/black market... : /

533y4 said:
I'm using Princely's Blue, black, white 2.7.5 rom... The Market version included with the ROM is 3.0.x and it keeps trying to goto 3.1.3.
I love the transparent blue, and not the ugly green/grey/black market... : /
Click to expand...
Click to collapse
Hm, cause I use BBW as my daily ROM, and I always have blue market, I know when the theme version isn't very modded it allows market to update itself, but I'm sure it's not the market this time because I use it too. Did you follow full install steps, that is main reason some system apps don't install? Your second option is, pull the Vending.apk from the V.2.7.5 zip and put it on your SD Card, Go to settings the applications, go to market, then click uninstall updates, if you get the themed market then good, but if it uninstalls the whole market app and you don't have market anymore, go to es file explorer or astro explorer(any file explorer than can ), then install from your SD Card. You should be ok from those steps, but if it fails by some strange reason, then reflash ROM full steps.
Edit: Before doing those steps let it update itself first, also, it's trying to update to 3.1.5 now.....

austrie said:
Hm, cause I use BBW as my daily ROM, and I always have blue market, I know when the theme version isn't very modded it allows market to update itself, but I'm sure it's not the market this time because I use it too. Did you follow full install steps, that is main reason some system apps don't install? Your second option is, pull the Vending.apk from the V.2.7.5 zip and put it on your SD Card, Go to settings the applications, go to market, then click uninstall updates, if you get the themed market then good, but if it uninstalls the whole market app and you don't have market anymore, go to es file explorer or astro explorer(any file explorer than can ), then install from your SD Card. You should be ok from those steps, but if it fails by some strange reason, then reflash ROM full steps.
Edit: Before doing those steps let it update itself first, also, it's trying to update to 3.1.5 now.....
Click to expand...
Click to collapse
I did the full install steps but originally installed RBT first... then the BBW over the Red... Could this cause it? Also, I've already uninstalled updates, and it just keeps reverting to the regular market right after I accept the TOS...
I think I'm gonna have to reflash the full ROM again...
{[EDIT]}
The other issue I have is that the battery icon in the status bar keeps chainging between a percentage and a battery icon... Another over install issue?

Try reflashing them full steps, if the steps above don't work for you. The battery and percent is my "fault", it turns to a buttery icon at 30, 50, 70, and 90 percent. Not sure which looks better though, the light blue battery looks pretty nice, it matches, but the battery icon is a bit more helpful being as the number percent.

austrie said:
Try reflashing them full steps, if the steps above don't work for you. The battery and percent is my "fault", it turns to a buttery icon at 30, 50, 70, and 90 percent. Not sure which looks better though, the light blue battery looks pretty nice, it matches, but the battery icon is a bit more helpful being as the number percent.
Click to expand...
Click to collapse
Reflashed the phone with the BBW again... (no over installing this time). As soon as the phone booted I uninstalled the Market Updater and it still updated as soon as I pressed "Agree" on launch... WTF?!
Other then the fighting market place and the every switching battery icon, I love the ROM... : ) Faster then my Epic 4G and Droid Charge by a land slide.
{[EDIT]}
I uninstalled the update, and the blue market came back (again)... But it keeps making my accept the TOS... and then boom! Updated...

OK, when you have the blue market don't except TOS yet, go to titanium backup, backup the blue market, then accept TOS, If it updates then let it update, after it updates then go to titanium backup and restore the blue market.
I'll try to get a up to date market in V2.8.

I downgraded to the 2.x version of the market (before any fancy crap, definitely before videos and books)... guess what? It's fast and responsive.
Definitely going to think hard about going to the latest version.

austrie said:
OK, when you have the blue market don't except TOS yet, go to titanium backup, backup the blue market, then accept TOS, If it updates then let it update, after it updates then go to titanium backup and restore the blue market.
I'll try to get a up to date market in V2.8.
Click to expand...
Click to collapse
No go... Removed updates. Made a back up. Then started the app and accepted TOS. Let it update. Then tried to restore.
Android won't restore over the new version... Keeps saying "Application not Installed". Tried to delete just the app, but when I restored the TOS was needed again... Was a good idea tho.
{[EDIT]}
Just tried something else... I directly replaced the com.android.vender(-1).apk apps over the whole rom... Seems to work for now... Wish me luck...
{[EDIT 2]}
Stayed for about 10-20 mins and then was replaced... What is causing this?

Theoretically you COULD delete the app, but that seems a little risky...something you should only try after a full backup (and something I would only try with a lot of Red Bull early in the morning)...
Or theme the latest market apk too. If it is recompiled, and assigned with a different key than the One Google uses, it might stick. But then, you may be voiding your ability to use Marketplace too...
Sent from my ADR6400L using Tapatalk

Substratum issues

Hey all so i have pixel 2 and i have this issue with substratum where it applys some of the theme but not all of it EG: YOUTUBE is supposed to be black/purple so js playstore and gmail however only gmail is black/purple
Its applyed the theme for the ui etc so i dont get it

With some of the themes you will need to apply only 3 or 4 parts of a sub theme overlay to get it working. Doing them all at once doesn't always work for some reason... Also a reboot after applying (even though it says not required) is necessary. You can also try disabling and enabling the part of the theme that did not apply in Manager section, or disable then enable all etc. to get them working
Sent from my Pixel 2 XL using Tapatalk

In some themes, you have to select the app version as well, or it won't work. Make sure there aren't any drop down menus at the individual apps in your theme building window.

Lag in recent apps overview

I'm on a Pixel 3 XL with the latest Android update (not rooted, no custom ROM, or anything like that). I am using Nova Launcher. When I try to switch to a recent app, there is a long lag time. It doesn't happen all the time, but it happens more often than not.
In the video link below, I have the "show taps" on so you can see what is going on. I clear all the recent apps. Open just 4 apps. And then try to switch to the most recent app. I tap two times, and nothing happens. But the screen is not frozen since I can still scroll through the recent apps. I tap one last time and there is still no response. And after a while, the app finally opens.
Is this a common issue on Pixels. Is there anything that can improve this? Any help would be appreciated. Thanks!
https://youtu.be/Z37r_Vd32sg

IamNe0 said:
I'm on a Pixel 3 XL with the latest Android update (not rooted, no custom ROM, or anything like that). I am using Nova Launcher. When I try to switch to a recent app, there is a long lag time. It doesn't happen all the time, but it happens more often than not.
In the video link below, I have the "show taps" on so you can see what is going on. I clear all the recent apps. Open just 4 apps. And then try to switch to the most recent app. I tap two times, and nothing happens. But the screen is not frozen since I can still scroll through the recent apps. I tap one last time and there is still no response. And after a while, the app finally opens.
Is this a common issue on Pixels. Is there anything that can improve this? Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
It's a pretty common issue with third party launchers. Try using the stock launcher to see if the issue persists

crixley said:
It's a pretty common issue with third party launchers. Try using the stock launcher to see if the issue persists
Click to expand...
Click to collapse
Tried it with the stock launcher and it did not happen. This is super frustrating. Pixel phones are becoming iPhones now, limiting our choice. I don't know how they haven't fixed this issue yet, despite having Android 10 out for so long.

IamNe0 said:
Tried it with the stock launcher and it did not happen. This is super frustrating. Pixel phones are becoming iPhones now, limiting our choice. I don't know how they haven't fixed this issue yet, despite having Android 10 out for so long.
Click to expand...
Click to collapse
It has to do with everything being built into the launcher now, including animations. If it makes you feel better this seems pretty much completely fixed in Android 11. Are you rooted? There is a magisk module that fixes this completely on Android 10 as well.
Edited to add: it's called quickstep switcher I believe in case you're wondering

crixley said:
It has to do with everything being built into the launcher now, including animations. If it makes you feel better this seems pretty much completely fixed in Android 11. Are you rooted? There is a magisk module that fixes this completely on Android 10 as well.
Edited to add: it's called quickstep switcher I believe in case you're wondering
Click to expand...
Click to collapse
Thanks! I'll look into it. This is the first phone I haven't rooted or had a custom ROM on, mainly because of the ease of monthly OTA updates. But now I am leaning towards rooting. I'll have to research a bit about how to deal with monthly updates while rooted.

IamNe0 said:
Thanks! I'll look into it. This is the first phone I haven't rooted or had a custom ROM on, mainly because of the ease of monthly OTA updates. But now I am leaning towards rooting. I'll have to research a bit about how to deal with monthly updates while rooted.
Click to expand...
Click to collapse
Root it but keep the old boot image. Flash the original boot image before taking the OTA. Then download the fastboot files for the new OTA from the Android site, patch that new boot image and flash that.
Feel free to PM me anytime you need any help, I'll even patch the boot image for you if you like.

Has anyone managed to get substratum or swift installer working on user apps?

It seems that I can only theme system apps. WhatsApp, Google home, Google translate... Etc. stay as they are even though the theme is installed and active.
10.5.7.IN21BA
Magisk 20.4

No major issues with Swift Installer, here. But thing is, a certain app can't be themed until an update provides a proper overlay for it.
I'd stay away from substratum, however. One wrong move, such as an incompatible overlay, could be problematic. I've found that out the hard way.

Revenant Ghost said:
No major issues with Swift Installer, here. But thing is, a certain app can't be themed until an update provides a proper overlay for it.
I'd stay away from substratum, however. One wrong move, such as an incompatible overlay, could be problematic. I've found that out the hard way.
Click to expand...
Click to collapse
Even when they're updated, user apps don't change for me. System apps like Google Chrome change theme just fine but user apps like Google translate don't.