DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Who is going to...[Re-Revisited]-Vending.apk
- Thread starter DF Smod
- Start date
MMs work on GB without issues when applying to framework, only is glitchy if applying into the SystemUI.apk..
But this MM works fine into either Froyo or GB...These battery icons are basically the ones you added to your theme, but just changed almost all to the blue instead of the yellow and red ones you had...
Black n Bold Market 2.3.6
Here is an update in thebowers' style.
BnBMarket_2.3.6.zip - Flash in recovery. Same things apply that mbk40 stated in his post (Post 782).
Here is an update in thebowers' style.
BnBMarket_2.3.6.zip - Flash in recovery. Same things apply that mbk40 stated in his post (Post 782).
Last edited:
is the new market version working for everyone?
..
I tried your recommended method, and still getting FCs with both versions.
I uninstalled updates (back to 2.3.4), even froze the market updater in Titanium and deleted the com.android.vending (or something like that) in the /data/data/ folder .. also have cleared apk cache and data, etc.
..any other ideas?
EDIT:
So this worked.. if this helps anyone else: I (on purpose) basically had 3 files in my system/app/ Vending.apk , Vending.blu , and Vending.bnb
All with rw-r--r-- permissions. and then I'd change the extension. I went back to the original Vending.apk that I backed up, made sure updates were uninstalled, market updater frozen, renamed Vending.apk to Vending.bak , then Vending.bnb to Vending.apk, and it seems to be working fine. (Same with the Blue version).
Thx guys
..
I tried your recommended method, and still getting FCs with both versions.
I uninstalled updates (back to 2.3.4), even froze the market updater in Titanium and deleted the com.android.vending (or something like that) in the /data/data/ folder .. also have cleared apk cache and data, etc.
..any other ideas?
EDIT:
So this worked.. if this helps anyone else: I (on purpose) basically had 3 files in my system/app/ Vending.apk , Vending.blu , and Vending.bnb
All with rw-r--r-- permissions. and then I'd change the extension. I went back to the original Vending.apk that I backed up, made sure updates were uninstalled, market updater frozen, renamed Vending.apk to Vending.bak , then Vending.bnb to Vending.apk, and it seems to be working fine. (Same with the Blue version).
Thx guys
Last edited:
No problems on either of my droids... my suggestion is for you to nandroid back to a backup when you had Vending 2.3.4 installed and then to immediately install the 2.3.6....
Yeah I did...still working fine... have you tried the nandroid first method?
Yes, but it never hurts to give it another go!
I've mostly been using Root Explorer, and just dropping the apk into /system/app/ then changing the permissions. (after creating backup of the original Vending.apk).
You should try doing it thru recovery...
I'm currently playing around with changing the markets colors and theme thru MetaMorph, and I've seen what you're talking about now... the MM works fine, but after updating some apps it started FC'ing on me as well... but my main Droid which was done thru recovery, and not metaamorphed, has updated many apps without that issue as of yet... so it may be associated to the method you are using, as it was for me trying out MetaMorph...because using Clockwork recovery worked fine...
Also as a footnote... It's not a Gingerbread/Froyo issue, because I nandroided my spare droid to a froyo ROM, and installed the 2.3.6 TruBlue market thru recovery and it worked perfect thru the updates, but as soon as I MetaMorphed it to another color version, it worked fine for a bit, then started FC'ing.... so I'm pretty sure just copying and overwriting thru RootExplorer may be your issue decalex
Last edited:
Thx for the response there. I've since tried it thru recovery and still had the same issue. I did find a version that worked, with (sort of) an explanation of what was happening. I also am going thru logcats to see what exactly is happening. I'll post findings tomor. Good times
Sent from my SPH-D700 using Tapatalk
Sent from my SPH-D700 using Tapatalk