I have tried multiple play store fixes from around the web and seemed to receive multiple force closes and various other issues when trying to launch Google play and Google apps. So, I decided to take the time to actually fix the files for the rom that I am currently using. Therefore, if you are someone who modified the DPI of your phone manually, happens to be running the Alpha for CM9 (or are willing to try with other roms) you can download the Vending.apk and GoogleServicesFramework.apk from this thread here and see if it helps you too. I should mention that you have to Clear data on the Google Play Store after replacing the files so it can again work properly.
I know many people are going to just say "why didn't you just download LCDModderPro, since it has the market fix?" Simple answer, because I wanted to do it myself. That is one of the great things about Android, it's open source and you can modify things to meet your needs. So why did I post this if I just wanted to do it myself? Well, once it was done I figured I might as well share... below are the links if anyone finds it to be useful.
Google Play 3.5.16:
My attempt at a CWM flashable zip: http://d-h.st/L5B
The files if you just want to copy them to /system/app yourself: http://d-h.st/AhT
The original files in case something goes wrong: http://d-h.st/5FS
Google Play 3.5.19
CWM Flashable Zip: http://d-h.st/d0t
The files if you just want to copy them to /system/app yourself: http://d-h.st/JGo
Google Play 3.7.13:
CWM flashable zip: http://d-h.st/fvz
The files if you just want to copy them to /system/app yourself: http://d-h.st/GfI
I am requesting that only people more experienced try this one ^^ out. I am trying something different this time around and I only actually edited a couple of lines, literally one in both the GoogleServicesFramework.apk and one in Phonesky.apk. It has been working for me for three days now, if you have an issue or it fails to work let me know.
Don't forget to clear data for the Google Play store after installing
Do what you do bro lol
Sent from my SGH-T989 using Tapatalk 2
Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....
SolsticeZero said:
Why didn't you just download LCD Modder Pr..... Oh..... Nevermind....
Click to expand...
Click to collapse
Ha! I guess that little rant wasn't totally necessary...
Thank you for sharing! I personally used LCD Modder Pro, but it's good to know another way to get it done!! Thanks again!
Good work. there is option if we dont wanna use lcd modder pro....
Thanks, works great. I like the fact that I can get Google Play working without the use of an extra application. I'll hope you keep this updated.
PlagueBoy said:
Ha! I guess that little rant wasn't totally necessary...
Click to expand...
Click to collapse
Yeah, I was just messin with ya, dude. Great work, by the way. This is a lot more convenient.
Google Play Version 3.5.19
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
Oh nice, I hope the issues will be a thing of the past so we can run custom DPI with no hassle. Thanks for the fix, its appreciated.
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod
elitrix said:
I can confirm this. Just installed 3.5.19 running 200dpi. Cleared data and rebooted. New version shows all my apps where before "incompatible" apps would not appear. Finally done with this mod
Click to expand...
Click to collapse
Yup. That is what I am seeing here as well. There should be a need to update the original post/files then. If people still want to use 3.5.16 until it is officially pushed to our phones then this will help, otherwise download 3.5.19 and you shouldn't have to worry about your DPI... as far as I can tell anyway.
I wish I would have found this before buying the LCD Density Modder Pro
Lol
Thanks for the hard work and the alternative approach to the app on the market! And thanks for the heads up about the new market
Sent from my SAMSUNG-SGH-I727 using XDA
PlagueBoy said:
I downloaded and installed the newest Google Play store version (3.5.19) and it appears that google has changed the display metrics from DPI to Height/Width. I am waiting to see if the old problem of apps becoming unsupported reoccur with the new version. As of now, after clearing data and toying with the DPI some more, I still have access to all my downloaded apps and the error hasn't occurred. I will update if it proves necessary...
Click to expand...
Click to collapse
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.
PlagueBoy said:
After flashing and trying different roms for a bit, I realized that Market 3.5.19 ultimately ended up having the same issues. I went ahead and updated the APK and updated the OP with the new link for the download. It is a CWM zip, don't forget to clear data after the install.
I have only tested this on CM9 and AOKP roms, it should still work on others… but I thought I should put it out there that I have only personally tested it on those two roms.
Click to expand...
Click to collapse
Yeah i can confirm this. 3.5.19 seemed to work for one day or so. But what ended up happening was that the apps just wouldn't show up at all. I normally use dropbox to test it but that always worked on this new market. Dolphin browser, Draw something, app quarantine wouldn't show up in a search. My phone is running sky ics 4.0.3, dpi 180.
EDIT: omg thank you! You are awesome! Thank you for doing this! You are faster with updates then LCD Density Modder pro, they are lagging it with updates. He is still running 3.5.15, amazing! You rock!
---------- Post added at 09:05 PM ---------- Previous post was at 08:37 PM ----------
I just flashed the 3.5.19 CWM flashable zip you made and it worked great! As soon as i rebooted clear the data and amazing. I cant thank you enough! Thank you
If we wanted to do it our selfs, could we extract your zip and take the files? Just wandering for future references.
Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you
s.sharm01 said:
Just wondering what dpi are you guys using? I tried toying with dpi values on atrix, wanted to get a reference of what the range to look for the sweet spot on the skyrocket
Also i just tried flashing and could not even make it to the boot animation. I'm running the sky ice off the latest leak.
Admittedly i wasn't sure if i was to change the DPI first, reboot, and the flash, or flash clear data then change DPI. I'm back to a nandroid backup, if someone could shed light on this it would be of great help.
Thank you
Click to expand...
Click to collapse
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.
Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.
PlagueBoy said:
I think, at least I found, when doing the math that the native DPI of the phone should be 207.32 and CM9/AOKP tends not to like DPI being set on an odd number, so 208 is what I have settled on. Although, as Voiid mentions he is running 180 and elitrix mentions 200, just find something that works for you!
As for your issue, I haven't been able to replicate it on my phone. You didn't clear the cache/d-cache in CWM after install did you? I have heard there are times when ICS has issues after doing so... if you did that it could be your problem. As for the proper way to do things, well, I have flashed this at many different times with different roms. I recommend clearing data in apps manager after the flash though, that way it has to resend the DPI information mimicking a first boot or launch of the Google Play store. Try downloading the files them selves, extracting them and manually copying them into the /system/apps folder in something like root explorer. Don't forget to change permissions to rw-r-r.
Voiid - I have uploaded the files in non-cwm flashable format so you can just have the modded files and the link is in the OP. However, for future reference, yes you can just extract the files from the app folder in the CWM zip and use them moving forward as updates come along.
Click to expand...
Click to collapse
Thank you PlagueBoy for the answer and the help!
s.sharm01 said:
Thanks for the reply Plague. The problem i am having seems to be with dpi modder app. I tried changing the dpi to 200, 180 and 210 and all of them sent me into a bootloop (not actually sure if it was a bootloop because the phone never got passed the samsung logo, i'm assuming it was still on). Either way i resolved the issue by using rom toolbox and changing the dpi to 200. Then i flashed the modded play store and its working great. Thank fully i am crazy about having nandroid backups so i didn't loose anything.
Click to expand...
Click to collapse
Yeah I had this issue too! Changing the dpi with LCD Modder Pro caused my phone to not boot too. I am not sure why though some apps that change dpi do that on this phone. On my old phone, the HTC aria, LCD modder worked. So idk. I just use root explorer and go to /system/ open build.prop as a text (make sure the folder is writeable) and change the dpi from within that my self. The line says
ro.sf.lcd_density=240
Its like in the center of the file.
You can change that number to whatever just make sure its a feasible number.
And then save it and reboot.
But you said rom tool box works so thanks for the heads up!
Sent from SAMSUNG-SGH-I727 using awesomesauce
Will this fix works on a galaxy s i9000
Sent from my GT-I9000 using Tapatalk 2
Related
Guys, I saw a bunch of people asking for a flashable 2.2.7 version of Market. I created a signed zip file for you to flash. I am using this on CM6.1.1, but I think it should work for any ROM. Hopefully a lot of you are getting the new market automatically...
To install:
Wipe market cash (under settings, applications, market, wipe cash)
Nandroid
clear cached, dalvik
flash this zip
everything should work great
Best of luck!
Market 2.2.7: http://rapidshare.com/files/438811534/market_2.2.7_signed_12222010.zip
Market 2.2.6: http://rapidshare.com/files/438805930/market_signed_12222010.zip
DISCLAIMER: Flashing a zip could always mess something up, so do this at your own risk and DO A NANDROID BACKUP FIRST!
Thanks, I've been looking for this.
I flashed the update via Amon recovery. I got a couple of network errors when trying to access the Marketplace the first time, but hit the retry button about four times and now it works fine. Thanks again.
let me know how it goes, make sure to nandroid first just to make sure!
Just an FYI, v2.2.7 has been out for a couple of days now
Calkulin said:
Just an FYI, v2.2.7 has been out for a couple of days now
Click to expand...
Click to collapse
if someone can get me the new Vending.apk, I can bake a new zip...I did read online that 2.2.7 was FC'ing for some people as well
adma84 said:
if someone can get me the new Vending.apk, I can bake a new zip...I did read online that 2.2.7 was FC'ing for some people as well
Click to expand...
Click to collapse
It's in my ROM as well as calkulin's, and probably others as well.
SteelH said:
It's in my ROM as well as calkulin's, and probably others as well.
Click to expand...
Click to collapse
thanks, I may get it from yours for us CM people.
ok, updated to 2.2.7, thanks to SteelH
New market apk!
I used this apk for my market and it's working perfectly. I never tried the flashable method, but i guarantee this is an easier method
MARKET APK: http://android.modaco.com/content/software/325980/new-style-market-apk-downloads/
theultimatev said:
I used this apk for my market and it's working perfectly. I never tried the flashable method, but i guarantee this is an easier method
MARKET APK: http://android.modaco.com/content/software/325980/new-style-market-apk-downloads/
Click to expand...
Click to collapse
How does this replace a system app in system/app? Seems like you wouldn't be able to replace a system/app with a simple apk install.
Thanks for this. I was getting a FC when I tried the other methods but, this worked just fine.
Any noticable difference?
I am running this on my Nexus One and besides the obvious visual stuff, it seems a bet slower. I know this is the EVO 4G thread so don't take my word on the performance thing as YMMV.
I doubt it would run that much better on the Evo than the N1. They are pretty similar when it comes to hardware.
How do you find out which market I have?
animal7296 said:
How do you find out which market I have?
Click to expand...
Click to collapse
Settings/Applications/Manage apps/all/Market
clamknuckle said:
I doubt it would run that much better on the Evo than the N1. They are pretty similar when it comes to hardware.
Click to expand...
Click to collapse
I guess it just needed to cache some of the info because it seems to have picked up a bit.
This should be in Themes/Apps. Might be seen by more foes
2.2.7 does not work on CM Nightly 203 with a fresh wipe, or previous install. And I have no freaking clue how I got v2.2.6 working a few days ago, so I'm just sticking with that.
Would someone mind attaching 2.2.7 to a post here? I can't get RS from work (blocked) and downloading from my phone gives me a corrupt zip (Dolphin HD & mini, android browser, Miren browser). Not sure what the deal is with rapidshare and my phone.
Also, has anyone had any success with CM 6.1.1 final and this 2.2.7? I haven't found a combination that has worked for me yet, but will try this.
recently some apps do not have a download button in the market but others do. ive uninstalled the update to market hoping that would do something but no avail. and ideas?
try clearing data and cache.
can you still download these apps from market.android.com? are these apps compatible with your phone?
Sent from my LG-P500 using XDA Premium App
im not entirly sure what wiping data encompasses. i have wiped cache, same problem, and unless facebook suddenly dropped 2.3 for support, my phone can support it. ive had it installed before.
update: i tryed installing facebook from the site, it says its unsupported. i havent changed roms since last time i installed it. :/
I have the same thing, I cleaned market cache but that did not work.
I tried to install Goweather, I had it installed via a APK file I downloaded.
And found that there was a Update but in the market the Update did not showup. I was using 1.9.8 and in the markted there now is version 1.9.9
1.9.9 showed up as installed (not so because I have 1.9.8) So I uninstalled 1.9.8 and wanted to install 1.9.9 But no download button.
So I tried to install it via Web market and there it says device not supported..
Weird..
I have the same problem, it says that my device is unsupported.
Have the problem since I downgraded from cm7 to cm6 on my milestone.
Clearing cache and app-data didn't help
I had a nandroid and could extract many apps that market says are unsupported and all of them work.
Sounds like the version your running isn't compatible with the app. Can you list a couple of the apps that you get the download link and a couple apps where you don't?
dakunesu said:
im not entirly sure what wiping data encompasses. i have wiped cache, same problem, and unless facebook suddenly dropped 2.3 for support, my phone can support it. ive had it installed before.
update: i tryed installing facebook from the site, it says its unsupported. i havent changed roms since last time i installed it. :/
Click to expand...
Click to collapse
primarily maps and facebook to not work. its a growing suspission that its my lcd density variable in my build.prop that i changed to make smaller on my screen. i verified that the rest of the file is the same.
chompsms as well doesnt but it seems that many of the games work
another update, build.prop doesnt seem to be affecting it
Have you tried APbrain or another pseudo market. APBrain has a instant downloader. Just sayin.
.... that doesn't seem to work for anybody
I've got absolutely no clue what's causing this but the release notes of the most recent CM7 version for my Optimus One P500 mentioned that this has been fixed. I'm not sure if this is specific to the P500 version, but if it isn't, then upgrading to the most recent CM7 version might help. In any case, looking through the commit log should tell you what the fix actually was and allow you to apply it to your version.
truthfully ide like to stick with google market. as much as fixing the phone and such so the check can go through, its moreso fixing symptoms than the problem(a descussion for another day)
ive been using cm7 nightly 144 for a while now. im not entirely sure if the new market is the problem or the nihtly. anyone else have any details on it?
Sometimes it happens if DPI is changed.
Transmitted from a Galaxy far far away via XDA telepathy.
Screen resolution was the culprit for me. Changed to default, clear market data/cache, go to market, download, change resolution back. Stock, rooted rom, nexus s 4g.
I had that problem too on my tattoo, i just backup only market (NO Data app) with titanium then wiped cache, and restored and it work again.
red250 said:
Screen resolution was the culprit for me. Changed to default, clear market data/cache, go to market, download, change resolution back. Stock, rooted rom, nexus s 4g.
Click to expand...
Click to collapse
How do you change your screen resolution?
ahsans said:
How do you change your screen resolution?
Click to expand...
Click to collapse
Download nitrality app from the market.
DPI change option is in UI tweaks menu.
Transmitted from a Galaxy far far away via XDA telepathy.
ahsans said:
How do you change your screen resolution?
Click to expand...
Click to collapse
LCDDensity for root. In the market. Must have root, obviously.
I have heard about the market app not working for some, have you tried installing an older version of the market?
Sent from my MB860 using XDA App
ahsans said:
How do you change your screen resolution?
Click to expand...
Click to collapse
you can also manually change the lcd density in build.prop
I have this same problem, and yes I have my dpi set to 190 when the default is 240.
I just flashed the first real version of my new rom, and it appears that the settings app is not installed?!?!?! I have no idea why, I can see it in /system/app with the file browser, but it does not show in my app drawer and if I try to install it it tells me I don't allow unknown sources. but if I click change settings it obviously force closes since settings doesn't exist. does anyone have any idea what could cause this?
The exact same thing just happened to me last night! Ironic...
I have not had time to dig into it again yet (hopefully tonight)... but I also had the setup issue and "this is not a blur device" when trying to use the stock home. I partially suspect the moto setup issue is related to cheescake... once i reinstalled cheesecake, switched to the default server, then setup worked fine...
I'll let you know what I find out about settings tonight... you likewise - let me know what you come up with..
Edit- to explain the cheesecake thing... i think I used a backup or some files from one after I had been checking different servers on cheesecake.. so i think the non-default server settings got transferred over.
Anyone know which files cheesecake affects?
Sent from my mind using XDA
So, I was just giving it another go, and for some reason or another, right after I hit build I decided to go back and change an apk - right before I started the zip-align process... and low and behold there was no Settings.apk in the working folder! Very strange.. i don't recall removing it... So, I tossed it back in.
We'll see what happens.. gotta finish up this draft.
Sent from my mind using XDA
I just had this happen to me last week. I flashed a ROM (don't remember the name) then decided I wanted to try Lithium. I didn't read the small print on the post that says you have to flash Lithium 1.2 first, do a full boot into OS, then reboot and flash 1.2.1. When I flashed directly to 1.2.1 I was missing my Settings just like you described.
Dude, I don't know if you figured it out, bricked your phone, or are furiously busy trying to crank out a new ROM... But, i've come to the conclusion that the mysterious missing Settings.apk has something to with the xml edits and/or recompiling the apk. Had another round of flashing, and I made a couple extra update.zips this time along with the full rom.
So, initially after flashing the rom, I went and checked with root explorer and the settings.apk was physically there.. but was not being recognized by the system (I think TB showed it as uninstalled). So, I flashed one of my settingsfix.zips that I made - first the one with my xml edits (that had previously been de/recompiled) - and it was a no go - still not seeing Settings. Then I flashed a version from a Stock set, and that fixed it.
I am still having the Accounts Setup issue though - that's my pain in the... But, I made another setupfix.zip and that helped me skip the Account Setup - I can add google accounts with no problem, but when I try to add a yahoo account I get a login failed... and when I check for software updates through settings and try to setup a moto account, I get connection failed...still suspecting cheesecake.
Edit - Yup. Cheesecake - I just reinstalled it - did not hit the top "install necessary files" button - just switched to the default production server, and then went back to settings to check for system update - and this time the moto account was setup no problem, and my device is up to date... What the heck does cheesecake modify?? Where are those servers listed?
still having the issue. the app is there, but will not be recognized, is it a permissions issue? any idea how to fix it?
Did you try just flashing the Settings.apk only? If that's a no go, then its the apk - if it goes, then it's a problem with the rom building...
I can't figure it out yet but I got all of my settings working, inverted.. I think I started from scratch again but flashed it separately.. I haven't had a chance to dig into it again recently.. but yea.. don't know..
Sent from my mind using XDA
alteredlikeness said:
Did you try just flashing the Settings.apk only? If that's a no go, then its the apk - if it goes, then it's a problem with the rom building...
I can't figure it out yet but I got all of my settings working, inverted.. I think I started from scratch again but flashed it separately.. I haven't had a chance to dig into it again recently.. but yea.. don't know..
Sent from my mind using XDA
Click to expand...
Click to collapse
I tried writing a zip to flash it again after install of the rom. next i guess I will try installing the rom by backup, as that will probably work better. I think flashable zips are much better though. I have been using JRW28's inverted settings app, so Maybe I'll grap a normal one from a stock rom and see how that works.
Try signing the Settings.apk - it worked for me. Here's what I figured out so far if you are decompiling apks... (no need for simple image editing/swapping...)
SIGN:
Settings
PerformanceManager
DON'T SIGN:
BatteryManager
DataManager
framework-res
moto-res
blur-res
SystemUI
Not certain about the **-res.apks and SystemUI since I did those so long ago, but.. I got all inverted settings/task manager/Battery&Data manager working!
alteredlikeness said:
Try signing the Settings.apk - it worked for me. Here's what I figured out so far if you are decompiling apks... (no need for simple image editing/swapping...)
SIGN:
Settings
PerformanceManager
DON'T SIGN:
BatteryManager
DataManager
framework-res
moto-res
blur-res
SystemUI
Not certain about the **-res.apks and SystemUI since I did those so long ago, but.. I got all inverted settings/task manager/Battery&Data manager working!
Click to expand...
Click to collapse
good idea, I'll have to try signing them, I hope this ends up being the problem.
The settings apk looks for a signature that matches the major system apks. If it doesn't match it will not run at boot.
Along with that (I think this helps with the signature check), I placed blur-res, framework-res, moto-res, and SystemUI apks in my \Apk_Manager_5.0.2\other folder, then opened the command line on that folder and set the framework dependees or whatever...
CODE:
apktool if framework-res.apk
(hit Enter)
apktool if blur-res.apk
(hit Enter)...
...for all of the apks
Then do your de/recompiling...
Well, I am baffled again.. I threw those new signed/unsigned apks in a rom build I was working on, flashed it, and Setting.apk was missing again... So, I flashed the small update zip with inverted Settings.apk and PerformanceManager.apk I made earlier that day and flashed successfully while on stock. And, Settings.apk came back (and was inverted), but Task Manager force closes - then I tried to flash a restore zip (with stock settings and task manager) - and it restores Settings, but doesn't fix the task manager - So, needless to say, I am back to square one in my understanding of all of this. I am assuming it is merely a signature check issue somehow??
Like I said, I had everything working yesterday on stock 2.3.6 after flashing a small update.zip with new signed Setting.apk and PerformanceManager.apk, and another one with unsigned battery and data manger apps.. Ended up restoring back to stock by the end of the day, and now today those same zip packages don't work like they did yesterday... Are new signatures created each time when the system is installed (or re-installed)? It was the exact same system restore on which I built the new inverted apks - so, I am very confused.
I will get to the bottom of this.. but, if anyone can shed some more light on the situation, that'd be great...
still no luck here either. I got my stuff working as a cwm backup, but it won't boot passed the boot logo (motorola M) now, so who knows. I am busy right now, but after next week I should have a lot more time to work on this.
Just tried another restore.zip, but nothing fixes Task Manager for me now.. Could it be that something is created in /data based on the apk in /system? So, when I flash older stock versions it doesn't fix it, since some link has been created outside of the apk?
Another thing possibly worth noting is that I am working with .apks and their .odex counterparts... but, that shouldn't be making a difference since I am not messing with the odex files.. plus, you've got similar problems, and I am assuming you are working with deodexed apks...
alteredlikeness said:
Just tried another restore.zip, but nothing fixes Task Manager for me now.. Could it be that something is created in /data based on the apk in /system? So, when I flash older stock versions it doesn't fix it, since some link has been created outside of the apk?
Another thing possibly worth noting is that I am working with .apks and their .odex counterparts... but, that shouldn't be making a difference since I am not messing with the odex files.. plus, you've got similar problems, and I am assuming you are working with deodexed apks...
Click to expand...
Click to collapse
yep, I'm using jrw28s inverted settings
Sent from my MB865 using XDA
OK.. Did a little more researching.. And, I think you need to resign all of the moto system apks with the same key.. then the signatures should match up, and apps shouldn't fail to be recognized...
I believe this is only if you are editing the AndroidManifest.xml, otherwise you can just copy the META-INF folder from the original apks with 7zip to retain the signature...
Not sure about the details and if it will actually work, also not sure exactly which apks to re-sign (probably the major 4), but that's my next game plan... trial and error... still trying to make sense of it all.
good idea, I'll have to try signing them, I hope this ends up being the problem.
What I discovered (through numerous trials and error) is that you can't mess with the AndroidManifest.xml... Something gets messed up with the signature (i.e. it doesn't match the framework signatures, or maybe it needs to match all of the moto apk sigs - not sure yet - because sometimes it worked when I pushed them separately), and the system doesn't recognize the apk.
But once I got re-did all of the apks without editing the AndroidManifest - all of my problems went away. I still was able to decompile the apks and edit /res/values xmls, just not that manifest..
So, as for the OP's problem, it looks like JRW's inverted Settings.apk (which were probably created by editing the AndroidManifest), is not matching the signatures of the other major apks in your ROM..
I will still try to figure out how to safely edit the manifest when I get around to it... any hints from JRW28 would be great! Is that the reason you had to originally make a separate update.zip for the inverted settings in Lithium?
Side note, I also figured out my setup issues... it was cheesecake related, along with my Settings.apk missing.
A couple of things finally clicked for me two nights ago...
alteredlikeness said:
What I discovered (through numerous trials and error) is that you can't mess with the AndroidManifest.xml... Something gets messed up with the signature (i.e. it doesn't match the framework signatures, or maybe it needs to match all of the moto apk sigs - not sure yet - because sometimes it worked when I pushed them separately), and the system doesn't recognize the apk.
But once I got re-did all of the apks without editing the AndroidManifest - all of my problems went away. I still was able to decompile the apks and edit /res/values xmls, just not that manifest..
So, as for the OP's problem, it looks like JRW's inverted Settings.apk (which were probably created by editing the AndroidManifest), is not matching the signatures of the other major apks in your ROM..
I will still try to figure out how to safely edit the manifest when I get around to it... any hints from JRW28 would be great! Is that the reason you had to originally make a separate update.zip for the inverted settings in Lithium?
Side note, I also figured out my setup issues... it was cheesecake related, along with my Settings.apk missing.
A couple of things finally clicked for me two nights ago...
Click to expand...
Click to collapse
Thanks, not sure whether I am even going to continue with this or not. With ics stuff starting to roll in I might save my time for that.
__
__
ATT seems to work
Sweet idea! Just tried this on an ATT GS3 and it seems fine. I did not test other apps. I do get an unsupported device tag at the top in the app but I don't think that impedes the function. When I use the Nexus device device, name and model (maguro, yakju and Galaxy Nexus) I don't get the warning but probably more likely to end up with incompatible apps.
Do you reset Google Wallet prior to flashing a new rom or do you just have the build.prop update before you run wallet?
__
I'm confused. I have Wallet installed on my Verizon GS3 and I have no problems now. I am rooted and running Synergy ROM. When installed Wallet, I had to use a patched APK and edit my build.prop prior to installing Wallet to trick the phone similarly to what your script does (Galaxy Nexus, yakju, and maguro instead) After installing and setting up Wallet, I restored my original SCH-I535, d2vzw, d2vzw settings in build.prop and rebooted again. I am running Wallet no problems and it doesn't even tell me that I am using an unsupported device.
When I reboot my phone, it does not affect Wallet and my build.prop is not modified. I don't understand why someone would need your script to keep modifying the build.prop to say it is the pretend device? Please don't take my reply wrong, I'm simply trying to figure out what I am missing, not be a jerk.
I am always leary about leaving my build.prop modified because you trick other things into thinking your phone is something it is not. I feel this leaves you open to potential problems. I used Goo Manager the other day to see if there were any updates for my ROM and because of a modified build.prop it thought my phone was an AT&T GS3 and if I had downloaded and tried to flash an AT&T ROM I might have bricked it. I'm not sure, but I wouldn't want to take that chance. Also, isn't there a possibility of downloading an app from the Play Store that is only for the Sprint phone you're pretending to be and causing problems?
Jim
__
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Oh OK... I'm not sure but that makes sense... You would know more than me! Thanks... Again I was just looking for clarification. Thanks for your work. Good luck.
Jim
jeremiahmegel said:
The "Unsupported device." error only shows up if you're running Google Wallet on a rooted device (unsurprisingly); you're right that it doesn't impede the function. And you don't need to do anything as the user before or after flashing a new ROM; once you update the ROM, your phone should reboot automatically within a minute or two of starting up to put the new build.prop into effect! Simply install this once and don't worry about it again! (Unless, of course, you uninstall Tasker or wipe your phone or something.)
Click to expand...
Click to collapse
So to clarify, when you say:
"And you don't need to do anything as the user before or after flashing a new ROM"
Do you really mean "you still have to reset Google Wallet before flashing a new ROM"?
Also, I'm wondering if it's possible that modifying build.prop might cause my Nfc.apk to stop functioning. I'm wondering this because it stopped functioning (after using 'Google Wallet Installer' - which does replace nfc.apk I believe, so that could be it, but not sure).
calaski8123 said:
Hi Jeremiah,
Thanks for the info. Just so you know, I used that Google installer few weeks ago and it worked fine. I changed to a new ROM last week and forgot to reset wallet before switching which caused bunch of problems. I was able to fix them but the installer did not work for me anymore. I was however able to get wallet working by manually editing build.prop and installing a patched apk of wallet. After wallet was up and running, I reverted back to the d2vzw and SCH-I535 version of build.prop. So you know, I have my correct build prop AND a working Google wallet. I can send you the link but its the Verizon Google wallet thread in the mods and app forum under Verizon GS3. I understand if you switch ROMs it would need to be reset and build prop edited again, but I don't think the is a need to keep your build prop edited unless you are using the play version of wallet. Perhaps the link could get you the patched version and that might help.
Take care,
Jim
Click to expand...
Click to collapse
Jim will you please tell me how you fixed it? I did not reset Wallet before installing a new ROM a couple months ago and unfortunately all my nandroids are bad due to a CWM bug involving partitions (I didn't do anything to my partition structure manually...).
Thanks a lot!
Hi,
I'll tell you what I did, but I was just trying anything so I'm not sure if I got lucky or if you have to do everything I say... First I went into application manager and I cleared all data and updates from wallet. Then I rebooted into recovery and did full wipe 3x. Then I went onto Google on my laptop and logged in. Go to wallet and then to your activated devices. Not sure what they are called but you will see all your devices that have wallet. Some might day deactivated. If there are any active then disable or remove them. I don't remember what the term is Google uses to Deactivate. Once you have no active wallet applications left on Google go back to your phone. Install the working ROM or good backup. I had a good backup with wallet working...i was able to restore that nandroid and reset wallet from within the app so that i could then install the new ROM. then After setup, reboot again and wipe dalvic cache in recovery. Then try to install wallet again. Thats pretty much how I got it fixed... The key was getting it deactivated online.
---------- Post added at 09:52 PM ---------- Previous post was at 09:28 PM ----------
Oh and I uninstalled wallet after clearing the cache and updates.. Forgot that part sorry.
Jim
I followed the instructions to the T and it worked perfectly. Thank you. But my question is, what happens to the Tasker Profile? After, I went back in to check out what you did. I am a relatively new Tasker user and was curious about what all was intailed. But when I went back the profile was gone and the only sign that I had imported the xml file was two variables. Is it supposed to disapear?
__
jeremiahmegel said:
As I recall, the patched APK isn't the newest version/update of Google Wallet, right? That's why I'm using the Play Store version: to receive updates to the app. If you don't care about updates, though, I suppose your way of doing things would be best. (I don't think it works throughout ROM updates, though. Let me know if I'm wrong about this.)
Click to expand...
Click to collapse
Correct, the patches lag behind the updates somewhat. You can only use Play Store Wallet if you build.prop matches Play Store Wallet accepted devices (d2spr being one of them). For this reason, I prefer to wait for the updated patched version - if you do that, you can keep d2vzw or whatever you want in your build.prop
As far as resetting when changing ROMs, back when everything was stored on the secure element resetting was a big pain in the ass. I don't even bother anymore - there's a separate "reset wallet" option in the menu of the actual app (different than clearing app data), but you don't need to use it. I just keep a version of Wallet Installer V3 in TiBu, and restore it after installing a new rom. After restoring Wallet Installer, just run it once and then reset build.prop - the installer downloads the latest patched Wallet.apk.
jeremiahmegel said:
No, it is not supposed to disappear. Since Tasker updated its UI, Step 4 ("Tap the green check-mark at the bottom-left of the screen to save the profile.") is no longer available. Instead, press the back button or home button on your phone (or just switch to another app) to save the profile, then continue to Step 5. Let me know if this works. Nice to know that I could help you get Google Wallet up and running!
Click to expand...
Click to collapse
I tried going through the steps again but I cant get Tasker to recognize the xml file when going through the import sequence. I downloaded and extracted (when extracrted its another file folder with the xml file in it), placed it on the root of my internal sd card. I go into tasker to import. It recognizes the file folder but when I select it, there isn't anything inside. Tasker wont recognize the basic xml file. I remeber when I first did this, the xml file was recognized without being in a folder. I can plainly see the xml file on the root of the sd card from Root Explorer in ROM toolbox. Would have it something to do with the permissions of the xml file? I show the permissions as rw-rw-r--.
I think I know why I am having to go this. I didn't follow the step to the T. I clicked "Run" before saving becasue I didn't see the green checkmark.
__
jeremiahmegel said:
What is the file name of your XML file?
Click to expand...
Click to collapse
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
08BajaBoy said:
I have the actually xml file on my sd card. It is named Replace_build.prop.prf.xml
When i go to the file through Root Browser in ROM Toolbox, its visible. I click it and it presents me with options to open it. I select Tasker and is says "Failed to move import to my sd directory"
Click to expand...
Click to collapse
I am not what was happening but I updated to CM10.1.0 RC2. I cleared anything I had tried previously with this tut. redownloaded the file and went though everthing again. It worked and the tasker profile stuck this time. Thanks for the help.
Great write up. Very simple to install. Google wallet was installed and running in less than 5 minutes. Thank you!
Galaxy S3 :good:
MOAR :BetteR:
Can anyone confirm this method works with 4.3? I made the jump to CM10.2 Nightly 8/27 (and tried 8/14, I think) and my phone goes into bootloop. It was working fine on CM10.1.2.
__
Hey guys,
I'm running Lollipop on my nexus 5 and totally hate the new Gmail app for various ui reasons. The rest of the OS I generally like. I'd like to downgrade to the previous 4.9 version of the app to get the old ui back, but just simply trying to install the apk doesn't seem to work. Since it's a system app, I was thinking about replacing the apk with root Explorer. What do you guys think? Possible to do?
Does the install fail? As with all previous versions, they've been installable.
You may just have to learn to live with it though or find an alternative app.
rootSU said:
Does the install fail? As with all previous versions, they've been installable.
You may just have to learn to live with it though or find an alternative app.
Click to expand...
Click to collapse
Yeah the install fails. I figured it out though. First what I did was freeze the original app through titanium backup, and then it allowed me to install the old version. Has been working great since. Renaming the app in the system and then trying to install the old version didn't work - it installed, but just crashed right away.
hungry4cheese said:
Yeah the install fails. I figured it out though. First what I did was freeze the original app through titanium backup, and then it allowed me to install the old version. Has been working great since. Renaming the app in the system and then trying to install the old version didn't work - it installed, but just crashed right away.
Click to expand...
Click to collapse
Oh. I didn't realise you still had the other version.
Yeah you can't have two apps the same. Its not based on package name either. So you can rename them all you want but that won't work
rootSU said:
Oh. I didn't realise you still had the other version.
Yeah you can't have two apps the same. Its not based on package name either. So you can rename them all you want but that won't work
Click to expand...
Click to collapse
Well I uninstalled all updates to the lollipop version (5.0) and then tried to rename the gmail apk in the system so the system wouldn't recognize it anymore. That removed the app and allowed me to install version 4.9, but after installing all it did was crash. I undid my changes and then tried to freeze the app in TB, which worked and allowed me to install version 4.9apk, which works great now. And then I just told the market not to update it to 5.0. I'm a fan of the older design on this app. Much more usable. The rest is okay and I like the new design.
Android likes to wait until ram is full. Then it clear ram when it needs it. This leads to lag since unlike iOS the ui is on the same thread(stupid). Also, android uses garbage collection which uses more ram unlike arc.
So, clearing processes does help but then it just builds up again.
With keyboards running at 40mb and gmail at 60mb this is only going to get worse.
There is also cache clearing that might help... But which cache doesn't lose settings? I'm also beginning to think that a lot of photos can slow things but I don't really know why since that should be static storage and nothing to do with RAM
I would really like to know how you managed to install gmail version 4.9 on lollipop... I have a oneplus one and I just got the paid version of titanium backup to try what you said worked for you - freezing gmail then installing a 4.9 APK, and while it looks like the freezing worked, when I try to install 4.9 it just says "App not installed".. no details or anything else. What else can I try?
tamale said:
I would really like to know how you managed to install gmail version 4.9 on lollipop... I have a oneplus one and I just got the paid version of titanium backup to try what you said worked for you - freezing gmail then installing a 4.9 APK, and while it looks like the freezing worked, when I try to install 4.9 it just says "App not installed".. no details or anything else. What else can I try?
Click to expand...
Click to collapse
Have you tried rebooting into recovery and wiping the dalvik cache and then trying to install and old version. I don't have a reason for an older version and right about now I don't really want to have to restore a backup if I bork it doing that
Sent from my N5
The old gmail runs on dalvik I think, whereas lollipop uses art. It won't work
Sent from my Nexus 5 using XDA Free mobile app
I got it. Just had to use the built in downloads app to open the apk, not es file explorer. For some reason that worked!
tamale said:
I got it. Just had to use the built in downloads app to open the apk, not es file explorer. For some reason that worked!
Click to expand...
Click to collapse
Congrats! Just saw this. Glad you got it to work. I've sort of given up /in to Google at this point since my note 4 is not rooted. If it was I would downgrade again. Hope others find this thread still useful.