Related
Make no mistake, I do not condone the use of Rom Manager due to our neglect.
Still, it has its purposes. I have fixed the "Fix Permissions" function. Do NOT install the market version!
Install this one instead. It may not work with Rom Manager Premium license. (I can live with that).
This has only been tested with superclean.
RomManager.apk
Fr just the script (run via adb shell or terminal emulator)
http://dl.dropbox.com/u/2056318/update-template/fxpms.zip
Install via clockwork, then run fxpms. Requires superuser permissions.
adrynalyne said:
Make no mistake, I do not condone the use of Rom Manager due to our neglect.
Still, it has its purposes. I have fixed the "Fix Permissions" function. Do NOT install the market version!
Install this one instead. It may not work with Rom Manager Premium license. (I can live with that).
This has only been tested with superclean.
RomManager.apk
Fr just the script (run via adb shell or terminal emulator)
http://dl.dropbox.com/u/2056318/update-template/fxpms.zip
Install via clockwork, then run fxpms. Requires superuser permissions.
Click to expand...
Click to collapse
Ok stpiid question. Do I have to do all of this or just install the apk?
Either or, but not both. That would be silly.
That's what I thought. Thanks. And this will work in cwm also?
Thanks, does this include the battstat fix as well?
Can't get the apk to install.
Other forums show that you need to uninstall the market ROM Manager before installing this one. That's how I did, uninstall, then install through root explorer or super manager.
Thanks man works!
Sent from my SCH-I500 using XDA App
Worked like a charm, installed through astro. Great work as always adrynalyne.
when do you sleep man your a beast! thanks a ton!
Had to uninstall the liscence. Duh
What was wrong with it to begin with? I just ran it on my phone about an hour before seeing this post. Did it not do what it's supposed to do?
Anyone running Froyo had issues with it. It would run in 1 second which obviously is too fast. It was not fixing any permissions. Just acting like it was.
Will it still not work in clockworkmod? I flashed the zip and still couldn't run it. Runs in Rom manager t though
Sorry for being ignorant, but exactly what permissions is the permissions fix supposed to fix, and why would I need to apply such a fix?
Edit: Nevermind, was having a hard time finding this answer on Google, but I finally found it. Looks like it just simply reapplies all proper permissions to system app files to fix FC errors and such, presumably in the event that you are messing with the system files and the permissions get messed up on them. I'm guessing I'll never need this function unless I start manually changing system files around or something.
ivorycruncher said:
... I'm guessing I'll never need this function unless I start manually changing system files around or something.
Click to expand...
Click to collapse
Such as, for example, deleting batterystats.bin
Another Fascinating post by my XDA app...
jmcintire said:
Such as, for example, deleting batterystats.bin
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
Doubtful, seeing as it's kind of hard to change permissions on something you've deleted.
Posted from my EB01 SuperClean Fascinate with Voodoo
dalrym05 said:
Will it still not work in clockworkmod? I flashed the zip and still couldn't run it. Runs in Rom manager t though
Click to expand...
Click to collapse
I'm curious about this as well.
Thanks for all of the hard work so far!
ivorycruncher said:
Doubtful, seeing as it's kind of hard to change permissions on something you've deleted.
Posted from my EB01 SuperClean Fascinate with Voodoo
Click to expand...
Click to collapse
Wouldn't deleting any system file like that affect the permissions on other apps, making it necessary to fix the permissions every time? Besides, the system rebuilds batterystats.bin from scratch immediately after it's been deleted.
Another Fascinating post by my XDA App
How on earth would deleting one file affect permissions on other files? That just doesn't happen. As for the file getting recreated, the OS should be smart enough to set the correct permissions on it.
The only time I can see this being necessary is if things don't work right after installing a new rom, or if you manually change apks or other system files. I've messed around with system files before, and never once had to fix any permissions, probably because I always took care to set the correct permissions manually when doing so.
Posted from my EB01 SuperClean Fascinate with Voodoo
Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
duble08 said:
Hey everybody -
This is my first post here. I'm sorry if there is an answer already posted to this and if i'm just reposting, but i haven't seen any of this information anywhere, and apparently i have to make 5 q&a posts before i can start posting stuff where i need too, so i'm trying to throw some useful info to the community to gain this privilage
Anyways, onto the topic -
Many people that are installing a new ROM on there EVO 3D are getting an error when google tries to auto install apps after flashing. The error states that there is not enough space left on their devices to continue installing apps, even though there are reports of users having 700+mb free for app storage. Developers are claiming that it's because you didn't wipe dalvik/cache before flashing. I've found that this is not true, but I do know the fix, but don't completely under stand why this happens.
The fix:
The fix to this problem is a very simple one.
1. Install the rom like you normally would (boot to recovery, NAND backup, wipe data/factory reset, wipe dalvik cache, wipe partition cache, and wipe cache, then flash from zip, then select reboot device)
2. When the phone is booted up, type in all your info as usual to sync your accounts. When your done with this step, you'll notice google tries to start installing all of your apps, which it'll eventually crash on due to space.
3. You can do this before or after it throws you the error message about space, but the next step is reboot your phone back into recovery. From there, you're going to wipe your dalvik cache and cache (again), and then reboot the phone again.
That's it! You should now be able to install all of your apps again without getting storage errors!
I'm not a developer, but if i'm to take a guess at why this happens, i'm guessing something about the install, or maybe even the initial boot process of a rom being ran for the first time, for some reason is flooding our cache space, thus firing false alarms for being out of space. Therefor, by cleaning the cache space after the rom install is completed and booted, the phone no longer notices the space issues. I could be wrong on this, but this seems like a logical answer to me.
If this helps, let me know! Also feel free to correct me if i'm wrong on anything i posted, but this method seems to work for me! If this needs to be in a different category, feel free to move it! As a new member, i'm very limited on where i can post things...
Enjoy your newly rooted and modded EVO 3D!
Click to expand...
Click to collapse
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
k2buckley said:
Welcome to the community, and nice first post! I haven't had the issue that you're referring to, but I have indeed noticed others having the issue. Good to know that fixes it up, in case I ever encounter it. Thanks.
Click to expand...
Click to collapse
no problem! this community has helped me TONS in the past, even though i haven't said anything about it (due to not being able to post in developer threads yet). I reflashed and wiped my phone about 4-5 times before realizing that the cache had to be cleaned AFTER the install and first boot of the new rom, and all the dev's kept stating it was from not wiping prior to flashing, which i did every time. Hopefully this will save some people time and headaches and i'm sure the dev's will soon find a fix to this, as they seem to work very fast at finding bugs and cleaning em up.
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Welcome to xda.
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
newkidd said:
more or less i would say its because the market will download apps to the cache first...then install them to the phone...
the insufficient space is mostly what happens when the cache gets filled.
thats my educated guess on the matter.
also welcome to xda. you're gonna like it here
Click to expand...
Click to collapse
that would make a lot of sense as well - if that's the case, maybe people should let google market crash the cache before they clear it out again? that's what i did when i got it working... it was one of those things where i just watched and wondered, "is it going to do it all this time?", and of course when it didn't, that's when i discovered re-clearing the cache again in recovery fixes it. I noticed that by clearing the application cache (settings/applications/manage programs/market/clear cache) the problem still persists, and the only way to get google apps to install again is by clearing cache in recovery, which made me think it was an installation/boot thing. but i'm still learning, like many of us here
thanks for the input!
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
this is an issue i noticed as well - i had to re-add my apps manually after it only added 24 of the 120 i had going. but hey, beggers can't be choosers, and i'm just mostly happy that i got a new rom going with everything functioning properly within 2 weeks of the phones release!
If anyone knows how to re-start the app sync succesfully without space errors, that might be good info to include in this post
awesomeindeed said:
When I do this, it forgets all my 130 apps and I have to go look for them manually. Only ROMs that are using the new market do this to me.
Click to expand...
Click to collapse
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
-viperboy- said:
Did you clear the cache or data in the app itself or from recovery?? If you clear cache from recovery, this shouldn't happen. If it still does, usually downloading another app rebuilds the market cache.
What you can do to fix it is use Titanium Backup and there is a setting: Menu > More > Market Doctor and it fixes this issue. But, I think it only works in the paid version. It's well worth the few bucks though!
Click to expand...
Click to collapse
Recovery. Downloading another app doesn't rebuild the cache either. Now it's gotten to the point where no ROM will restore any of my apps at all, it basically thinks I've never downloaded anything. So now I've gotta try and remember the 130 or so apps I had installed.
Not complaining, just an observation. One of the caveats of rooting a new device
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
empiire said:
Welcome to the community.
A really easy way to fix this is to just clear the cache and data for the Market in Settings > Applications, and that has worked for numerous people using my ROM but I don't think it'd be any different for any other ROM.
Click to expand...
Click to collapse
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
You can also go into terminal emulator and delete the Download.apk files in the cache.
You'd think Google would be a little smarter at this. All the market would need to do is download fewer apps at a time, as the files are cleared once the installation is complete.
Sent from my PG86100 using XDA App
I feel a s0be market fix coming on. Although I have not seen the issue, you could pwn the cache and symlink it out of /data and into /system. A genious linux guy, seriously, genious, made this hack back on the hero, fixed market download errors EVERY time.
See this post:http://forum.xda-developers.com/showpost.php?p=11055157&postcount=4650
If you like it, go find s0be and thank him
duble08 said:
I tried this method on vipers rc1.2 and supra ROM, and it didn't fix it for either - I continued to get insufficient space warnings, even after rebooting. The only thing that worked for my device was going into recovery to clear the cache.
Click to expand...
Click to collapse
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That won't make any difference if there is no room to actually store the downloads. Downloads from the Market go into /cache while downloading and then move to /data/app or /system/app, depending on the app. Hence why clearing cache fixes it.
laie1472 said:
You could try reflashing the rom and signing into your google account right away. And let it sync. Just a thought.
Locked & Loaded
Click to expand...
Click to collapse
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
duble08 said:
That's what causes the market problem - I tried wiping and flashing both roms multiple times with the same result - if you flash a new ROM with the new market, and your market tries to sync a large number of apps, its going to flood the cache space and stop allowing the installation of apps until you go into recovery and clear the cache there... Then it all works fine, except for having to add all your apps one by one.
Click to expand...
Click to collapse
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
laie1472 said:
Well have you tried my suggestion I posted before the last one???
As in this
Another suggestion to add to the nice info here is. When you boot up a rom for the first time dont sign in. Immediately go to settings/accounts & sync and uncheck auto sync. Then head to settings/privacy then uncheck automatically restore. Then sign in. This is a option for anyone who doesn't want to reboot.
Locked & Loaded
Click to expand...
Click to collapse
I tried something similar, but not exactly like you said earlier. I set my accounts to sync, but immediately went into the market while it was syncing, and cancelled everything. This would've still left the user picking each app to re-download one by one, because I believe there's no way to restart the app sync. I ended up buying titanium, and used that to put all my apps back on - its much less of a headache.
Big fan of the Skydragon ROM. :good:
The issues Im having are after the 1.1 update
I applied the update to fix (primarily) the gallery issue (as without it you cant view images in MMS messages)
The issue appears to be access to the SD card once the update has been applied (as well as the already acknowledged Gmail crash)
Both gallery and music are unable to access the external SD card, yet ES file explorer can.
I've tried to 'fix permissions' , and it seems to fix it temporarily, but after a reboot the issue returns.
Hope MaartenXDA can reproduce the issue and its an easy fix!
Cheers for the hard work..its really appreciated!
Okay, thanks for the report.
The fixing permissions should fix it even trough reboots. (In theory). But apparently it doesn't.
If you fix the permissions again, is the issue solved?
Sent from my awesome fridge
MaartenXDA said:
Okay, thanks for the report.
The fixing permissions should fix it even trough reboots. (In theory). But apparently it doesn't.
If you fix the permissions again, is the issue solved?
Sent from my awesome fridge
Click to expand...
Click to collapse
Send them and OTA with an init.d script to fix permissions in /system/etc/init.d. That should work...
Stereo8 said:
Send them and OTA with an init.d script to fix permissions in /system/etc/init.d. That should work...
Click to expand...
Click to collapse
Thanks. I've already been testing a set permissions script and it seems to work.
But @OP, is the issue solved after you set permissions?
MaartenXDA said:
Thanks. I've already been testing a set permissions script and it seems to work.
But @OP, is the issue solved after you set permissions?
Click to expand...
Click to collapse
Maarten..sorry for the late reply.
Im just doing a NAND backup and I`ll let you know in a little while. Ive just re-downloaded the OTA just in case something has changed/corrupted etc.
Cheers
Maarten,
unfortunately fix permissions isn't retained after a reboot.
on the plus side, when you do fix permissions, all issues I'm having, gmail, gallery and music are fixed.
cheers
chocyman said:
Maarten,
unfortunately fix permissions isn't retained after a reboot.
on the plus side, when you do fix permissions, all issues I'm having, gmail, gallery and music are fixed.
cheers
Click to expand...
Click to collapse
Thanks, that's what I needed.
For now I'll just add an init.d script that will fix the permissions on boot. After that I'll look at the problem, it's possible the installation doesn't set the right permissions.
Sent from my awesome fridge
MaartenXDA said:
Thanks, that's what I needed.
For now I'll just add an init.d script that will fix the permissions on boot. After that I'll look at the problem, it's possible the installation doesn't set the right permissions.
Sent from my awesome fridge
Click to expand...
Click to collapse
One suggestion, there are probably some problems inside updater-script, cause permissions are set while flashing. So I think it would be much better to recheck the updater-script than to build scripts to run on boot.
nlooooo said:
One suggestion, there are probably some problems inside updater-script, cause permissions are set while flashing. So I think it would be much better to recheck the updater-script than to build scripts to run on boot.
Click to expand...
Click to collapse
I know, that was my plan. But to keep the users happy while I'm checking the installation, I'll give them a fix first.
MaartenXDA said:
I know, that was my plan. But to keep the users happy while I'm checking the installation, I'll give them a fix first.
Click to expand...
Click to collapse
Thanks for looking at this. Speaking for myself, its no big thing having to manually set permissions when my phone reboots. Unless I'm flashing ROMs, it rarely reboots. If a permanent fix is simpler then perhaps just post the work-around on the ROM thread until it gets included in the next update.
If the init.d script is easy to apply, then I guess its a good way to as you say "keep the users happy ". We are quite a demanding lot aren't we
Top work...keep it up! Lots of ppl are liking this ROM.
cheers
Just applied the 1.2 update and although I can see there's a temp init.d fix, it hasn't worked on my DX.
Same as before, reboot in twrp, fix permissions and app good.
Haven't had a chance to check the other additions. So can't comment on those.
cheers
Hi there,
I'm running cyanogenmod 11 on my s3 and I'm having difficulty updating/installing whatsapp. I had whatsapp installed and was told I needed to update the app otherwise it'd stop working. I didn't update in time and sure enough it stopped working. I tried to update the app to continue using it but it said I had insufficient storage available. I've got plenty of storage space on both my SD (internal) and external cards and I've checked every partition and there's lots of space. The issue does not seem to relate to lack of space.
Since then I've tried everything to get it working, first uninstalling the app and reinstalling, deleting everything manually through root explorer, then wiping the cache and davik cache, odexing all my apps and then removing all the odex files through lucky patcher. Nothings worked. Unfortunately it doesn't let me use lucky patcher troubleshoot which I've heard works. Everytime I press on troubleshoot in lucky patcher it says I need to update busybox and install supersu, which I've done plenty of times to no avail.
Please can anyone help out. I'm fearing that I'm going to have to restore everything. If anyone knows how to get the troubleshoot in lucky patcher working or just fix my whatsapp issue all together that'd be great. Thanks!
Can anyone help with this?
Thanks.
Have u tried to reboot ur phone?
Jumaqidi said:
Have u tried to reboot ur phone?
Click to expand...
Click to collapse
Yeah of course. I've had to reboot plenty of times but nothing I've tried so far has worked.
kesteral said:
Can anyone help with this?
Thanks.
Click to expand...
Click to collapse
Did you do a hard reset?
verny94 said:
Did you do a hard reset?
Click to expand...
Click to collapse
Not yet. I'm trying to avoid that if possible because I'm currently abroad and away from my computer. A hard reset would put me back onto stock wouldn't it? Is there any other solution out there?
Hello there.
My OnePlus 5T has got an issue today that is driving me crazy. Its storage is acting up in stupid ways.
I can browse its storage through the stock file manager and SD Maid without too many issues. However, everything else cannot access it, so it becomes impossible to save/download anything, upload anything, or even read anything (like these gallery pickers on social apps). Even the Play Store cannot update an app. I can't take screenshots either.
That OnePlus 5T is two years old and a half. I've tried removing a lot of files through SD Maid and nothing helps solving that issue. Rebooting my phone doesn't change anything either. Permissions are all good as well.
I haven't rooted my phone, however the bootloader is open.
Thanks for checking in.
It might be your File Explorer/Manager not showing the file i have that issue with Files by Google it doesn't show .img files on my sdcard and internal memory
ineedroot69 said:
It might be your File Explorer/Manager not showing the file i have that issue with Files by Google it doesn't show .img files on my sdcard and internal memory
Click to expand...
Click to collapse
As I pointed out in the first post, absolutely nothing shows up in Files by Google, stock Gallery app, or even Discord or Telegram. The Play Store cannot download anything, same for Google Chrome and any other apps. Somehow only the stock file explorer and SD Maid can manipulate storage without issues.
At random reboots I face the same issues too. Not sure why.
thechloroform said:
At random reboots I face the same issues too. Not sure why.
Click to expand...
Click to collapse
Did you manage to fix it? I've cleared the cache from the recovery menu and the problem persists, even after several reboots.
have you tried checking this app "Storage Permission" if they are allowed?
ineedroot69 said:
have you tried checking this app "Storage Permission" if they are allowed?
Click to expand...
Click to collapse
This was the first thing I checked and everything was okay. Double checked just in case and storage permissions are still granted.
ImJulienB said:
Did you manage to fix it? I've cleared the cache from the recovery menu and the problem persists, even after several reboots.
Click to expand...
Click to collapse
Unfortunately no. I am using a Moto Z play rom and sadly rom development for my device is meager due to the unpopularity of the device. The storage permissions have been granted by me too but yet some apps completely hang and restart when I try to download in them. Browsers and all are working fine. Even download manager. It is stuffs like Edxposed which freezes when I click on download on a particular module. Same thing happens to certain other apps like image downloading apps. Storage permissions are intact. I'm on Lineage OS 16.
Another concerning issue is sometime both the inbuilt gallery app and Quickpic completely fail to recognize any images or videos. I did a clean install of the ROM too.
I can't take screenshots too (at times). I can download and upload anything with the help of solid explorer or es file manager. Camera app sometimes cannot save an image to its own storage even though permissions are intact.
Trying to download or update anything makes the Play store crash. Sometimes it updates, mostly it crashes. Things get way annoying when I'm urgently trying to download an app and play store just rage quits on me.