Anyone else having this issue? After one of the most recent updates, I noticed my storage space dropped by about a gig. I found that the Xposed installer had over a gig of data saved. I went into the app and cleared the logs and got the majority of that gigabyte back, but after a few days it has gone up to a gig again.
There is no option to disable logging, why the sudden change to allow Xposed to keep such a large running log file? I'm on an S4 that is already internal-storage-challenged...
The problem isn't Xposed, it's with one of your modules. See which is throwing errors all around and report it to the module's author.
You called it sir... Greenify module is listed for every error... part my fault, I haven't updated the app to the latest version because the author removed a feature that I like.
Thank you man for pointing me in the right direction!
Related
well since i been reading thru the forums and noticed many "free" apps now charge..
i have like 60 apps installed and prob like 40 of them have "update available" next to them maybe is because i put a recent backup on my phone? or perhaps is just many "free" apps goign to add a code to convert it in to trial?
should i update em? and test? and later on just put a backup of my apps?
thats just a screenshot of one chucnk the list goes on.. :/
It's most likely because you flashed a backup of your phone recently.
ill try updating them, thanks.
Okay, this has been bugging me for a long time. I've been around since the beginning of G1 and have never seen a solution to this. I'm out of town on vacation, so my updates and responses may be slow. I've found a partial solution for this. If you don't want to read the fluff, drop down to Partial Solution sections, but be warned, this is not perfect (yet). Below is a quick spilling of my guts on this. Please excuse any grammar mistakes and fragmented thought. I posted this in DEV because more research needs to be done by someone that knows how this stuff works. If we get this worked out, I'll update this post with whatever information is necessary.
This post takes for granted the reader has some knowledge of file management and manipulation, so I won't get too detailed with how to copy/move/delete files. There is a lot of information here and I know most won't read it all, but I'm trying to get all the detail into this I can think of in hopes others have ideas that we can share.
I DO NOT KNOW THE RAMIFICATIONS OF WHAT THIS DOES! ANYTHING THAT HAPPENS TO YOUR PHONE IS YOUR FAULT, NOT MINE! Etc... Etc... Etc...
Issue: After flashing/Odin/wiping, sometimes the Market takes about a minute to load as does the app and security info screens. The Top Paid button is missing and all that's available is Top Free and Just In. Installing an app takes quite a bit of time. It eventually clears up, but it may take up to a week.
If you restore Market preferences via Titanium Backup or similar app, it can speed it up, but in the long run, you may get cross referenced apps over time or Market problems in general. For example, I install app1 and when it's finished, I select it in notifications and it takes me to app3. Some apps are also missing from Downloads and have to be installed again for them to show up. I also experience Titanium Backup not linking the Market correctly if at all. How to fix that is below, also.
How I Tested: I renamed /dbdata/databases/com.android.vending which reproduced the problem reliably and gave me a working set of databases and .xml's to look at.
Partial Solution: Save a copy of /dbdata/databases/com.android.vending/shared_prefs/vending_preferences.xml and put it back after you've restored your apps and opened Market once (just to lay down the directory structure). There are other files that will get more "stuff" back, but because of issues I've had between vending.apk versions, I choose to restore just this one file. It doesn't seem to change much. You can look in it and find some interesting things, but I've found changing it does very little if anything. Changing local_db_sync_required didn't do anything and it just reverted back to "false" for me.
What you will find, is Market will run quickly again BUT, you have no links so none of your apps show as installed. Although it will probably sync over time, the point of my messing around was fairly instant gratification. Thus the next section.
New Problem: Market speed is normal, but no apps are linked. Hey, I use Titanium backup! Fix Market links works, partially. I have 226 apps backed up in TB (Yes, this is why I wanted to get this working) and when I fixed Market links, it found 167. I fixed them again and it found 9, then 17, then 6 etc... It repeated some apps and never detected others. I checked and some of the "fixed" apps did not show in downloads... So I started looking. Menu -> Legend showed me part of the issue. Smiley face -vs- green M. For some reason, some of my apps were not linking properly. Here's how to get that part working.
Partial Solution: Here's what I did in TB. I filtered by Status: Backed up and Type: User. Starting at the top of the list, I long pressed on the first "smiley face" which means it didn't back up the Market link and if it was "Attached to Market", I Detached it. View in Market and installed the app. When it was done, I backed the app up again and viola, green M showing it backed up the Market link. I did this many, many more times to fix my links. It worked in all occasions as long as I could find the app in the Market. Of course, some apps installed outside the Market cannot be fixed (duh), but all others worked fine.
I still have a problem getting everything attached in one shot. If I fix Market links in TB, I still get strange results, but this is as close as I can get and I found quite a few apps that have not been linked for so long, they were a few revs behind, so I'm happy with how far I've gotten.
Questions that will be asked:
- Why didn't you force attach to Market with TB? Because it didn't work. Some indicated it did, but they didn't show up in Market as installed, they didn't back up as linked and some even reverted back to not being attached and the forced button was available. The above is how I got around all of that.
- What about the other cool DB's and .xml? I didn't find that it was worth any possible issues to restore anything else except this file. That is probably what got me into this in the first place. Your mileage may vary. DB's usually need an update script if any changes are made. If that doesn't happen and the schema doesn't match, that's usually bad. That's why a lot of ROM's require a wipe. The old doesn't match the new...
- Why can't you backup Market with TB now that it is working well? I could and it would probably work, but I know it won't work forever because it didn't before. It also won't help someone else who is in a similar situation. I've been using TB (paid) since it came out and I love it. But, it's not perfect.
- Why should I mess with this instead of waiting for it to fix itself? You probably shouldn't. I've found that if I did a restore of apps, some NEVER go back to the Downloads section without a re-install. That's my concern.
- I don't have any of these problems, why are you posting this? Because I and others have. The universe does not revolve around you. Please move on.
- Why did you post this in Dev? As I said in the beginning, because we need someone who knows how this OS works so maybe a reliable workaround can be had for all. I didn't post in DEV for exposure, I posted here because I started it and I don't know where to go. Maybe a fix can be turned into an app or incorporated directly within a ROM. Who knows? I'm not a DEVing, but I am troubleshooting an issue within the OS.
One thing I've found that helps, is I kinda ignore if it shows up in Downloads in the market after a restore. I check for updates using AppBrain app, it finds all the apps on the phone whether they're in the market or not. Then, whenever an app is updated, it directs you to the market download page. If the market link was broken, that will say "Install" instead of "Update", but an install at that point will update properly, and you'll now have a working market link.
The main goal of having apps show up in the market, IMHO, is updates and uninstalls. Use the system uninstaller rather than the market for uninstalls, and use AppBrain to find updates. Works for me.
Thanks a lot for putting this up! I was banging my head against the wall last night, as I ran into this issue again and couldnt remember how I fixed it on my G1
zimphishmonger said:
Thanks a lot for putting this up! I was banging my head against the wall last night, as I ran into this issue again and couldnt remember how I fixed it on my G1
Click to expand...
Click to collapse
yw
lotherius said:
One thing I've found that helps, is I kinda ignore if it shows up in Downloads in the market after a restore. I check for updates using AppBrain app, it finds all the apps on the phone whether they're in the market or not. Then, whenever an app is updated, it directs you to the market download page. If the market link was broken, that will say "Install" instead of "Update", but an install at that point will update properly, and you'll now have a working market link.
The main goal of having apps show up in the market, IMHO, is updates and uninstalls. Use the system uninstaller rather than the market for uninstalls, and use AppBrain to find updates. Works for me.
Click to expand...
Click to collapse
I rarely uninstall via market. Have an app that throws me straight to the system uninstaller from the apps icon. I like appbrain, but it exhibits the same issue as the Market for me as far as detecting installed apps in some cases. I use the Market for updates and it works fine for me as long as the apps are linked. I think it has something to do with the hash getting messed up in the assets.db
Is there a limit on the number of applications that can be installed? I have 150 installed, and have been getting unsucessfull installs on the apps downloading now.
Sideloading works, however downloading fails. There is plenty of space on both tablet storage, and app storage.
TNT Lite 4.2.0 layered over 4.1.0.
More information. This is not isolated to the Gtab, apparently there are a lot of similar market issues on the phones as well. When clicking on the error itself the message box reads
Unknown Error -18.
Internet search leads to .android_secure or the sd card as the culprit. However neither solution works for this.
To further complicate the issue I downloaded another free app, the army field survival manual, and that installed just fine. Some updates are installing, some are failing. This is really odd. Might have to giveup trouble shooting, and just do a windows fix when all else fails wipe out and start from scratch.
the market has been having download problems for a few weeks
I don't remember having this problem before, it only happens sometimes and with different results, it's very random.
Scenario A) When I open Xposed, it starts checking for updates and notifies me of every new update, if I go to the "Dowloads" activityand press the reload button, nothing new adds. <-- normal scenario, it always was like this before 2.6.1.
Scenario B) When I open Xposed, it starts checking for updates but doesn't find any new update (and doesn't give out any error, at least on a toast), when I enter the "Downloads" activity, and press the reload button, new updates appear..
Scenario C) When I open Xposed, nothing happens. It doesn't load ANY update or tried to get new ones, even if I had some updates pending to install before, it won't show anything until I enter the "Downloads" activity. There the updates to-do are like normal and pressing reload gets new ones.
Also, I noticed that from 2.6.1 is when I started choosing specific update configuration for some of the modules only (global is STABLE and for some apps EXPERIMENTAL now).
This doesn't only happens to modules, today I had an scenario B when after entering the "Downloads" activity and pressing reload, I got notified of the new Xposed experimental1 update..
I didn't do the "all modules disabled" test because since this is very random and I rarely find updates for my mods, It would mean having xposed disabled maybe for hours/days which sucks
Updates from the repository are only refreshed every 24 hours. The downloaded repo.xml is kept in the cache and still needs to be loaded every time the app is started - unless the app was still in the memory.
So the different situations can be explained like this:
A) The last refresh was more than a day ago, so the installer first downloads the new XML, then loads it.
B) The last refresh was less than a day ago, so the installer just loads the cached XML. When you press the refresh button, the 24 hour limit is ignored, so you see new updates.
C) The app might still have been running in the background, so no refresh was necessary. Or maybe you have cleared the cache, so nothing was downloaded and the XML to load was empty.
It isn't really worth looking into this in more detail as 2.7 experimental1 handles downloads quite differently.
rovo89 said:
Updates from the repository are only refreshed every 24 hours. The downloaded repo.xml is kept in the cache and still needs to be loaded every time the app is started - unless the app was still in the memory.
So the different situations can be explained like this:
A) The last refresh was more than a day ago, so the installer first downloads the new XML, then loads it.
B) The last refresh was less than a day ago, so the installer just loads the cached XML. When you press the refresh button, the 24 hour limit is ignored, so you see new updates.
C) The app might still have been running in the background, so no refresh was necessary. Or maybe you have cleared the cache, so nothing was downloaded and the XML to load was empty.
It isn't really worth looking into this in more detail as 2.7 experimental1 handles downloads quite differently.
Click to expand...
Click to collapse
That explains a lot. However, doesn't fully explains the C scenario, since on it, the main activity doesn't show all the "pending to install but already notified (in green letters) updates", it doesn't show anything, not even any module or download on any of the activities (forgot to mention this), hitting the reload button fixes everything tho.
The question is.. why does the system works like this? Why it has to be that "manual"? (I spend the entire day pressing the reload button lol). Why it couldn't just check for updates everytime the app was loaded / everytime the main activity was opened / or even without the app opened, in the background. Maybe bandwith? not sure otherwise
If the system is changing in the next version (and for now in experimental), yeah we'd be losing time checking there. How does the new system works? does it do anything of the ideas I said just above? I'd love to test it, but im not moving from STABLE releases of xposed, it is way important for me :good:
Thanks a lot for your fast reply!!
RusherDude said:
That explains a lot. However, doesn't fully explains the C scenario, since on it, the main activity doesn't show all the "pending to install but already notified (in green letters) updates", it doesn't show anything, not even any module or download on any of the activities (forgot to mention this), hitting the reload button fixes everything tho.
Click to expand...
Click to collapse
That's really strange, not intended and I never had that situation. Do you have an app that constantly clears the cache? Loading the XML of course happens independently from the 24 hour limit, so the only possible explanation is that the cached file was deleted.
RusherDude said:
The question is.. why does the system works like this? Why it has to be that "manual"? (I spend the entire day pressing the reload button lol).
Click to expand...
Click to collapse
As mentioned, THIS is definitely not working as intended. I suspect something is deleting the file in the background on your system, as I never heard of such issues before.
RusherDude said:
Why it couldn't just check for updates everytime the app was loaded / everytime the main activity was opened / or even without the app opened, in the background. Maybe bandwith? not sure otherwise
Click to expand...
Click to collapse
Sure it's bandwidth. The repository index has grown to about 350 kB and is always growing. The Xposed Installer 2.6.1 has been downloaded more than 1.25M times, 2.4.1 even reached more than 2.5M downloads. That surely includes duplicate downloads, bots, users who decided to abandon Xposed etc. But still, the repository index has been downloaded 4.5M times in May, generating more than 1.1 TB of bandwidth. Now imagine what would happen if the installer checked for updates twice daily, or even in the background (which would also generate bandwidth for the many users who don't open the app daily).
Apart from that, traffic caused for the user, waiting times until the file is downloaded etc.
With the database approach and partial updates, I might be able to lower the update rate a bit, but I don't really see a necessity for that. There are about 10-20 updates per day, which affect usally none, sometimes one or two of your installed modules. And even when there are updates, there is hardly any reason that you have to update right now, instead of half a day later.
RusherDude said:
If the system is changing in the next version (and for now in experimental), yeah we'd be losing time checking there. How does the new system works? does it do anything of the ideas I said just above? I'd love to test it, but im not moving from STABLE releases of xposed, it is way important for me :good:
Click to expand...
Click to collapse
Just check the thread, I explained it there. There are no changes in the framework, only in the downloader, so it won't affect your modules.
rovo89 said:
That's really strange, not intended and I never had that situation. Do you have an app that constantly clears the cache? Loading the XML of course happens independently from the 24 hour limit, so the only possible explanation is that the cached file was deleted.
As mentioned, THIS is definitely not working as intended. I suspect something is deleting the file in the background on your system, as I never heard of such issues before.
Click to expand...
Click to collapse
Well, now that I remember the times that happened I was cleaning some so it may be the reason.
rovo89 said:
Sure it's bandwidth. The repository index has grown to about 350 kB and is always growing. The Xposed Installer 2.6.1 has been downloaded more than 1.25M times, 2.4.1 even reached more than 2.5M downloads. That surely includes duplicate downloads, bots, users who decided to abandon Xposed etc. But still, the repository index has been downloaded 4.5M times in May, generating more than 1.1 TB of bandwidth. Now imagine what would happen if the installer checked for updates twice daily, or even in the background (which would also generate bandwidth for the many users who don't open the app daily).
Apart from that, traffic caused for the user, waiting times until the file is downloaded etc.
Click to expand...
Click to collapse
Yeah, I understand that , well at least on BD you're gonna save some bandwith
rovo89 said:
With the database approach and partial updates, I might be able to lower the update rate a bit, but I don't really see a necessity for that. There are about 10-20 updates per day, which affect usally none, sometimes one or two of your installed modules. And even when there are updates, there is hardly any reason that you have to update right now, instead of half a day later.
Just check the thread, I explained it there. There are no changes in the framework, only in the downloader, so it won't affect your modules.
Click to expand...
Click to collapse
Done. Thanks a lot
And about that "there is hardly any reason that you have to update right now, instead of half a day later", there are flashaholics and there are xposaholics :laugh::laugh:
Thanks mate!
I just want to note that there doesn't seem to be any system to automatically clear logs from xposed installer.
I was sorting apps by size and found that xposed installer was using 1.36GB!! After clearing the logs the problem was solved.
It would be nice to have a setting to automatically clear the logs (it could be a log maximum size setting, a log maximum age setting or whatever else).
That's all, thanks for this great software!
You have an incompatible module that keeps crashing. Find it, uninstall it. Clearing the logs does not fix the problem.
Q
Olkflx said:
It would be nice to have a setting to automatically clear the logs (it could be a log maximum size setting, a log maximum age setting or whatever else).
Click to expand...
Click to collapse
You're by far not the only one who has suggested this. As a developer, it's surprising for me that many people want to fix only the symptoms instead of the root cause. Anyway, it's planned to limit the log size to avoid such big files, but that obviously doesn't fix anything.
GermainZ already said what you should do, it's also mentioned in the FAQ.