Related
My wife surprised me last night and took me out to get my gTab a week early! I brought it home and charged it, played with the default installed for a bit, and as we all know...it was awful. I proceeded to install VEGAn b5.1.1, that went as smooth as one could want...15 minutes and I was chugging along on a MUCH better/faster interface. The issue I am seeing now is there are certain apps (not Angry Birds) that aren't showing in the Market. I can't seem to find ADW Launcher, Facebook or Launcher Pro. Any thoughts on this? I cleared the cache and user data when I did the install so I don' think there should be any lingering issues there.
Thanks
Scott
When they are talking about clearing the cache and data for the Market fix, they are talking about clearing it for that app and not the full cache/data wipe when installing the ROM.
Menu/Settings/Applications/Manage Applications and then select the All tab, scroll to find Google Services Framework and Market. You clear the data/cache of those and force stop them. Back out to the main home screen and try to access the Market again. It should error out....reboot the device and after it boots...just wait for a few minutes. Try the Market again...it should ask you to accept it's terms again and hopefully show you more apps then before.
It's just one of those things with having a device that isn't supported by Google and hacking the Market to work.
LauncherPro is one I've seen appear and disappear in the available apps on my Gtablet running VEGAn 5.1. Without real Google support, even tricks and hacks can only go so far.
Luckily for me, I have a Motorola Droid and use that to grab anything my tablet doesn't see and then push it to my Dropbox account and get it from there for my tablet.
Most things I can see with all the Market fixes, do-overs and what not. My test being LauncherPro....saw it once...then it never appeared again after many "fix" attempts. That particular app is also available from the developers site ( http://www.launcherpro.com/ ).
This (using Dropbox) really works well since my other tablet will not boot so once I nvflash boot it....it needs to stay on. Market fixes (requiring a reboot, etc..) aren't possible, so Dropbox has been awesome for that tablet.
Two things that may help
Bluetooth File Transfer might help.
I put this link up a few days ago because I had the same problem.
http://forum.xda-developers.com/showthread.php?t=930036
Also, This video really worked for me with getting full market (roughly 98.9% really) http://www.youtube.com/watch?v=7l-ny...eature=related
tcrews said:
Menu/Settings/Applications/Manage Applications and then select the All tab, scroll to find Google Services Framework and Market. You clear the data/cache of those and force stop them. Back out to the main home screen and try to access the Market again. It should error out....reboot the device and after it boots...just wait for a few minutes. Try the Market again...it should ask you to accept it's terms again and hopefully show you more apps then before.
Click to expand...
Click to collapse
Tried this again and it did the trick! Thanks! (Must have missed something the first time I tried).
Scott
Intermittently when installing apps from the market I get the above error. I've tried clearing the cache and re-installing the app. Neither has any effect. Anyone get the market to work predictably on the kindle fire? I'm using the app from the guide that calls for vending.apk
Uninstall vending.apk and use the one that ends in amarket.apk instead.
That causes the market to crash every time I try and launch it.
kodemage said:
That causes the market to crash every time I try and launch it.
Click to expand...
Click to collapse
Strange, it works fine for me. I've never used the vending.apk always used the com.amarket.apk
Did you try clearing the storage or deleting vending one first? If that doesn't help, then I have no clue. I have no issues with the market with that APK.
Did you push it to the /system/app folder before installing?
I have it working perfectly, thus far. Cn you list apps that are failing so I can try it?
//Tapatalk.EVO3D//
Ok, I uninstalled the market app and cleared the card. I re-downloaded and re-sideloaded everything. I have the market. I can click install but the apps I want to install are stalling at "starting download". I'm on wifi, I can access the web fine.
Apps that won't install.
Google Music
Retro Clock
OTA rootkeeper
I just installed Google Music without error. Did you install the market from the system/app folder?
//Tapatalk.KindleFire//
I have the same problem. I installed the vending.apk in systems/app ensured all the permissions are correct (when they weren't market would insta-crash) so I re-installed, corrected permissions and it loaded but now whenever I try and download it hangs on, "Waiting for download to start"
Also if I search for say, "Official Twitter App" it will bring up the first 15/20 or so options covering 2/3's of the screen of 15,000 or whatever but there's no option to see more.
Is that normal? I've never used Android before.
Apps I've tried to download,
Busybox
Twitter
OpenVPN Installer
OpenVPN Settings
(BTW until there's a tun.ko don't bother with VPN...)
I had this problems too, i tried 10 diffrent versions of the market.
The solution was to clear cache and data from the "Download Manager" app. I also cleared cache and data from all google apps, but i think the download manager was the main problem.
Thanks for the tip to clear the download app data but didn't work for me...
I'll have a go with the other suggested apk tomorrow.
Problem Solved! / Solution? Not really.
I've got it working.
I have two different vending.apk files. I didn't hash them to see if they're exactly the same but they have the same size to the byte. One installed the phone market version and the other installed the tablet market version. The tablet version not only looks slicker but it crashed exactly once and after I restarted the device it's worked flawlessly as far as I can tell. Installed many nice apps.
My initial thought is that I missed a step in the process early on, serves me right being a script kiddie type and just following the steps instead of understanding why each step is taken. I think I've learned a lot about how security works in android from this experience.
Also, google reader on the kindle fire rocks. Get the articles to fill the screen and you can page through them like the best magazine ever written.
I got Market working by integrating it into the ROM through Titanium Backup. It seemed to be the only way I got it to work.
I posted this on another tech forum too, but I am looking to anyone and everyone for answers before I go crazy.
I have an HTC Wildfire S, currently with version 4.2.2 Jellybean. This error has been pestering me ever since my first ICS ROM 4.0.4. I have tried numerous versions of gapps, numerous resets. This has come to happen daily no matter what I do. It only affects the Play Store. I have endlessly searched online and tried different things to no avail, now across 3 Android versions built by different developers. It got worse as of 4.1.2 and is no better in 4.2.2. Using the standard gapps flashables and the built in one to the 4.1.2 ROM, this error will come daily out of nowhere. Usually it shows when I open the Play Store or when I try and run a paid app. In that case(running paid app), it will get so relentless that I can't do anything with my phone but clear dalvik and reboot. It will stop any work I am doing with the constant error. Clear data no help. Force stop just has it restarting on its own. Clear cache no help. Clear Google Account no help. Only clearing the dalvik like a good little girl and rebooting clears it for a little while and lets me use paid apps and the Play Store, only to have it resurface hours later. Reflashing gapps, even after totally wiping them only does about as much as just clearing the dalvik cache. In desperation, since it seemed to mostly happen when launching paid apps, I tried a Play Store with the licensing system hacked. Besides being able to launch my BOUGHT apps offline(like offline games should be able to), this offered 1 improvement. I no longer have it flash up randomly during work with other apps or when launching a paid app. But, I do still have it come up as soon as I try and launch the Play Store in about the same amount of time. The temporary cure: same thing. At least I am not forced out of other apps. My guess is the hacked version does not make the crashing library load to check the license online, hence this improvement. But it still sucks when I want to install or update an app. I would have quit the Play Store and bought from Amazon and others if I have not already paid for so many apps over time I can't use or update without it.
Given I have got it so that it only happens when I launch Play(with hacked Play Store only, otherwise the random relentless error happens(usually when launching or working with a paid app) with any normal version of Google Apps and Google Play in addition to when I launch Play), I am about to either become a pirate and install black market(can have paid apps and avoid launching Gay Store, which would avoid this with the hacked Play Store as unlike the regular builds, it only happens when I actually launch Play) or get an iphone. After over a year, I am just so sick of this error and it's driving me loony. Have never found an answer to it or a fix when searching online. Nor have I been able to trace or figure out why this is happening. Only common thread(besides the hardware) is the ROMs are all stable CM builds, but different Android versions and different developers. I hate to become a pirate to solve this, but I am at wits end and really don't want Apple. I just want something stable, which my setup otherwise is, except for the Play Store. Again, clearing the dalvik cache is the only thing that lets me use it again, but the error will rear its ugly head again anywhere from hours to a day or 2. Please help me. Piracy is not a good fix but iphones are even worse. I will not pay for all my apps again through Amazon. That is just not an option for me, with money being tight and all. The only reason I would consider splurging on an iphone is so I never lose an investment due to a faulty appstore again and to punish Google for this miserable failure by handing over no more money to them.
Selenia said:
I posted this on another tech forum too, but I am looking to anyone and everyone for answers before I go crazy.
I have an HTC Wildfire S, currently with version 4.2.2 Jellybean. This error has been pestering me ever since my first ICS ROM 4.0.4. I have tried numerous versions of gapps, numerous resets. This has come to happen daily no matter what I do. It only affects the Play Store. I have endlessly searched online and tried different things to no avail, now across 3 Android versions built by different developers. It got worse as of 4.1.2 and is no better in 4.2.2. Using the standard gapps flashables and the built in one to the 4.1.2 ROM, this error will come daily out of nowhere. Usually it shows when I open the Play Store or when I try and run a paid app. In that case(running paid app), it will get so relentless that I can't do anything with my phone but clear dalvik and reboot. It will stop any work I am doing with the constant error. Clear data no help. Force stop just has it restarting on its own. Clear cache no help. Clear Google Account no help. Only clearing the dalvik like a good little girl and rebooting clears it for a little while and lets me use paid apps and the Play Store, only to have it resurface hours later. Reflashing gapps, even after totally wiping them only does about as much as just clearing the dalvik cache. In desperation, since it seemed to mostly happen when launching paid apps, I tried a Play Store with the licensing system hacked. Besides being able to launch my BOUGHT apps offline(like offline games should be able to), this offered 1 improvement. I no longer have it flash up randomly during work with other apps or when launching a paid app. But, I do still have it come up as soon as I try and launch the Play Store in about the same amount of time. The temporary cure: same thing. At least I am not forced out of other apps. My guess is the hacked version does not make the crashing library load to check the license online, hence this improvement. But it still sucks when I want to install or update an app. I would have quit the Play Store and bought from Amazon and others if I have not already paid for so many apps over time I can't use or update without it.
Given I have got it so that it only happens when I launch Play(with hacked Play Store only, otherwise the random relentless error happens(usually when launching or working with a paid app) with any normal version of Google Apps and Google Play in addition to when I launch Play), I am about to either become a pirate and install black market(can have paid apps and avoid launching Gay Store, which would avoid this with the hacked Play Store as unlike the regular builds, it only happens when I actually launch Play) or get an iphone. After over a year, I am just so sick of this error and it's driving me loony. Have never found an answer to it or a fix when searching online. Nor have I been able to trace or figure out why this is happening. Only common thread(besides the hardware) is the ROMs are all stable CM builds, but different Android versions and different developers. I hate to become a pirate to solve this, but I am at wits end and really don't want Apple. I just want something stable, which my setup otherwise is, except for the Play Store. Again, clearing the dalvik cache is the only thing that lets me use it again, but the error will rear its ugly head again anywhere from hours to a day or 2. Please help me. Piracy is not a good fix but iphones are even worse. I will not pay for all my apps again through Amazon. That is just not an option for me, with money being tight and all. The only reason I would consider splurging on an iphone is so I never lose an investment due to a faulty appstore again and to punish Google for this miserable failure by handing over no more money to them.
Click to expand...
Click to collapse
Full wipe should have been done between different dev's roms.
Then flash your favorite rom and start from scratch with everything.
It will fix your error definitely.
Lgrootnoob said:
Full wipe should have been done between different dev's roms.
Then flash your favorite rom and start from scratch with everything.
It will fix your error definitely.
Click to expand...
Click to collapse
Thanks for trying but definitely not. I full wipe before every flash of a new ROM and even did it a few times and reinstalled the last 2 ROMS to no avail. Seems to fix it a bit longer than wiping dalvik, but inevitably, the error comes back within days. This is even without restoring my Titanium backup and reinstalling apps from scratch via Play. But again, thank you for being the first to try. But I do know to full wipe /system, /cache, and /data, and sd-ext before even restoring backups, let alone a new ROM install. I do this in TWRP 1 partition at a time then flash or restore(whichever applies) then usually wipe dalvik after for good measure
Selenia said:
Thanks for trying but definitely not. I full wipe before every flash of a new ROM and even did it a few times and reinstalled the last 2 ROMS to no avail. Seems to fix it a bit longer than wiping dalvik, but inevitably, the error comes back within days. This is even without restoring my Titanium backup and reinstalling apps from scratch via Play. But again, thank you for being the first to try. But I do know to full wipe /system, /cache, and /data, and sd-ext before even restoring backups, let alone a new ROM install. I do this in TWRP 1 partition at a time then flash or restore(whichever applies) then usually wipe dalvik after for good measure
Click to expand...
Click to collapse
Any more ideas? I never said this would be easy. In fact, the fact I posted here suggests that it will not. I am experienced with Linux systems and troubleshooting thereof and generally pretty good with Androids and modding. I love helping people but despise asking questions of others and only do so in desperation. Usually content to troubleshoot and lookup info myself and always been that way. But I feel I have reached a dead end, so now I call upon a forum I see as loving challenges to hopefully bail me out. Thanks again, guys. Note:had this issue with 1 other device that dropped dead before I could troubleshoot: a Pantech Burst, also with ICS and JB(was fine on GB as was this HTC Wildfire). It also had no other issues outside of a few minor things listed under bugs for its ROM, just like this phone.
Selenia said:
Any more ideas? I never said this would be easy. In fact, the fact I posted here suggests that it will not. I am experienced with Linux systems and troubleshooting thereof and generally pretty good with Androids and modding. I love helping people but despise asking questions of others and only do so in desperation. Usually content to troubleshoot and lookup info myself and always been that way. But I feel I have reached a dead end, so now I call upon a forum I see as loving challenges to hopefully bail me out. Thanks again, guys. Note:had this issue with 1 other device that dropped dead before I could troubleshoot: a Pantech Burst, also with ICS and JB(was fine on GB as was this HTC Wildfire). It also had no other issues outside of a few minor things listed under bugs for its ROM, just like this phone.
Click to expand...
Click to collapse
How 'bout the forum here for the wildfire s?
So this happens even if you run completely stock with no user installed apps? (Other than CM?)
Your s-off right?
Lgrootnoob said:
How 'bout the forum here for the wildfire s?
So this happens even if you run completely stock with no user installed apps? (Other than CM?)
Your s-off right?
Click to expand...
Click to collapse
Not S-Off, which was deemed impossible with Wildfire S at the time I started flashing ROMS. Bootloader is unlocked, however, which is said to be good enough for flashing from zip files. All changes I make to /system from TWRP stick permanently. As to whether I had the issue on GB, didn't as far as I left it on there, which was not long at all. Just a matter of days. I loathed the stock Sense 2.1 ROM and only bought this phone off my friend because it was very capable of being modded, otherwise, I would have passed, even at $25 I paid over a year ago. The other phone with same issue started the issue with stock ICS, which continued with custom ROMs. I mention this because that phone had no secuflag. Just a locked bootloader that was easily hacked to unlocked. All root apps do their job with no issue and all my added init scripts(mostly for internet tweaking, etc) stick.
Selenia said:
Not S-Off, which was deemed impossible with Wildfire S at the time I started flashing ROMS. Bootloader is unlocked, however, which is said to be good enough for flashing from zip files. All changes I make to /system from TWRP stick permanently. As to whether I had the issue on GB, didn't as far as I left it on there, which was not long at all. Just a matter of days. I loathed the stock Sense 2.1 ROM and only bought this phone off my friend because it was very capable of being modded, otherwise, I would have passed, even at $25 I paid over a year ago. The other phone with same issue started the issue with stock ICS, which continued with custom ROMs. I mention this because that phone had no secuflag. Just a locked bootloader that was easily hacked to unlocked. All root apps do their job with no issue and all my added init scripts(mostly for internet tweaking, etc) stick.
Click to expand...
Click to collapse
I just think that it might because of tweaking.
Partly right. I wiped the phone. Reapplied basic tweaks and was fine. So before letting it pull all my apps back in, I fired up a cheap Chinese tablet that is often used as a victim to my experiments. I installed my previous apps 1 by 1, as this tablet never had the issue. Went on a sudden hunch I had and set Cache Apps to SD Card up and let it run as it binds all app caches. Let it go overnight. In the morning, BAM! Play Store was stopping. Restored apps on my Wildfire S but used a shell script I wrote instead of that app. No Play crashes all day. Funny it probably caused it on my Burst too(RIP). I used the app on several GB phones with no issue but either a Play update, an update to the app, or ICS+ cause this app and Play not to play well. This app does not have many settings to try and fix it. Thus I would avoid that app until further notice. Funny how it's on Play but crashes Play
Sent from my Wildfire S A510e using xda app-developers app
most specifically my Facebook app. whenever I force quit it or reboot the phone, my Facebook app reverts back to an old version. it says its the most up to date version when I check the version # and there's no updates available. I am rooted and have turned auto update off on the app within play store. this is really obnoxious having to uninstall and then reinstall the app multiple times a day bc the old version is AWFUL. any help would be appreciated GREATLY!
coupey said:
most specifically my Facebook app. whenever I force quit it or reboot the phone, my Facebook app reverts back to an old version. it says its the most up to date version when I check the version # and there's no updates available. I am rooted and have turned auto update off on the app within play store. this is really obnoxious having to uninstall and then reinstall the app multiple times a day bc the old version is AWFUL. any help would be appreciated GREATLY!
Click to expand...
Click to collapse
What ROM are you running and what version of Google play store do you have? Haven't noticed this issue.
RevelationOmega said:
What ROM are you running and what version of Google play store do you have? Haven't noticed this issue.
Click to expand...
Click to collapse
stock ROM and 4.5.10. its actually not just or force quits and reboots but that generates the problem 100% of the time. I noticed sometimes when I go to my Facebook app it'll just be an old version. although it has the same and most up to date version when I check the version #. when I uninstall and then install again its back to the newest version. reverts randomly a few hours later.
coupey said:
stock ROM and 4.5.10. its actually not just or force quits and reboots but that generates the problem 100% of the time. I noticed sometimes when I go to my Facebook app it'll just be an old version. although it has the same and most up to date version when I check the version #. when I uninstall and then install again its back to the newest version. reverts randomly a few hours later.
Click to expand...
Click to collapse
Is it only the Facebook app doing this? I'd try wiping data/cache for app, going to recovery, backup, wipe data/cache, reboot and try to see if problem persists. If it does, something between the Facebook app and google play is not working correct.
heres screenshot of app before and after a soft reboot.
RevelationOmega said:
Is it only the Facebook app doing this? I'd try wiping data/cache for app, going to recovery, backup, wipe data/cache, reboot and try to see if problem persists. If it does, something between the Facebook app and google play is not working correct.
Click to expand...
Click to collapse
it is the only app doing it that ive noticed but since im fairly new to android, its hard for me to tell older versions from new ones, this one is just SO obvious and frankly that old version is just awful.
i wiped data/cache from the app, went into recovery and wiped cache partition but didnt wipe the data, i assume that completely wipes the phone? sorry like i said i have only had this phone for 2 weeks from long time iphone user minus a short stint with a moto droid in 2009.
coupey said:
it is the only app doing it that ive noticed but since im fairly new to android, its hard for me to tell older versions from new ones, this one is just SO obvious and frankly that old version is just awful.
i wiped data/cache from the app, went into recovery and wiped cache partition but didnt wipe the data, i assume that completely wipes the phone? sorry like i said i have only had this phone for 2 weeks from long time iphone user minus a short stint with a moto droid in 2009.
Click to expand...
Click to collapse
It's perfectly fine. Yes, don't wipe the data since that will wipe everything. But, since this did not clear up the issue, it sounds like a Facebook problem. I've heard many people complain about layaway build. Best thing I could say to do is try uninstall, reboot phone, and try reinstall. If that doesn't work, I'd try to find last version Facebook apk file (or current Facebook version apk file) NOT from play store, install,and wait for Facebook to fix the app from this problem. Still seeing possible other way to fix. By installing apk not from play store would allow phone to hopefully not reset to old version since play store doesn't realize you have Facebook anymore (since not from play store). A quick work around until fixed.
If this is facebook only, it might very well be a Facebook problem. Especially when you say that it changes even though the version of the apk stays the same.
Facebook has been testing the new layout by having both the new and the old one in the same apk, then they enable or disable it server side by accounts in order to try different versions of the new layout for different people and see the different responses in usage and so on. This sounds like a bug with that mechanism inside the Facebook app, and is not fixable as such. I for one have yet to see the new layout on my device.
You could try clearing the data for the facebook app to see if that helps.
RevelationOmega said:
It's perfectly fine. Yes, don't wipe the data since that will wipe everything. But, since this did not clear up the issue, it sounds like a Facebook problem. I've heard many people complain about layaway build. Best thing I could say to do is try uninstall, reboot phone, and try reinstall. If that doesn't work, I'd try to find last version Facebook apk file (or current Facebook version apk file) NOT from play store, install,and wait for Facebook to fix the app from this problem. Still seeing possible other way to fix. By installing apk not from play store would allow phone to hopefully not reset to old version since play store doesn't realize you have Facebook anymore (since not from play store). A quick work around until fixed.
Click to expand...
Click to collapse
ill give it a shot! is that 2nd picture i posted an old version or is that possibly a new version yet to be released?
uninstalling and downloading the apk online fixed it. thank y'all so much!
Yes the second picture shows the new version facebook is testing.
bump. it started doing it again :| downloading apk no longer works. this is beyond frustrating!
coupey said:
bump. it started doing it again :| downloading apk no longer works. this is beyond frustrating!
Click to expand...
Click to collapse
bump
Are you sure you aren't registered to facebook beta testing?
99.9% sure as I've never opted into a beta test for android.
Hello,
I have just installed tarkzim's Lineage OS 18.1 - the latest - version on my Z5 without Gapps. Unfortunately it turns out to be unusable because of a serious bug (at least on my phone it shows, and I have no better name for it than to call it a bug): launching the browser (indispensable on a smartphone) crashes the whole system and causes an immediate reboot.
I wonder if anyone else has encountered the same problem or if there is someone who has been able to fix this or has a workaround at least.
Otherwise I hope that the developer reads this here, too, and will look into the problem. For now my Xperia is bricked, but I will follow the development and forthcoming versions, of course, hoping for improvements.
I have another mobile - so I can live with that bricked one for a while ;-)
Hey,
I´ve got basically the same bug, but managed to play around a bit further. From what I could gather, the Phone crashes and reboots every time I open certain apps. I have Gapps istalled and notized two problems.
Crashes and reboot on startup of certain apps, like Chrome, pre istalled browser, Outlook, G-Mail, Mattermost or Amazon Shopping. Other apps seem to do fine. Firefox, k-9 Mail, Whatsapp, Telegram, Sotify work more or less without a problem.
Crashes and reboot on sign in. From the few that I tested, Vanced was the most interesting one because I could open and play Youtube Videos normally but it always crashed when I tried to log in. I could login through microg but since then my phone started to crash and reboot every few minutes. Uninstalling all vanced related apps did not solve the problem. Some apps crashed on sign in and since then werent able to get running again.
I really like the Lineage version, and I wouldn´t even mind finding the "working" apps using them (does´nt really matter to me if I use Chrome or Firefox) but certain apps I need to work like Mattermost.
I hope someone could help with our problem because I really want Lineage to work on the Z5. It feels so... clean and smooth.
Good to hear that someone else has similar issues with this LineageOS version - and regrettable, too, of course. Even without GApps it is unusable so far. But I really hope that this version is not the 'last word', and will continue improving. I know it is a big task for a programmer.
I have just seen that a new version is available. When I find the time, I will replace the version on my phone with the new one and report.