When installing apps the storage manager is not registering the correct size to start off with. For instance a 1.5gb app is showing as total size of maybe 59mb. Under data for the apps it shows maybe 200kb.
Now the worse part is when uninstslling apps it does not race the data for the app. In order to remove the data and get my space back I have to boot into recovery and wipe cache.
Tried removing external SD card and trying it again and it's th deer same issue.
Also when attempting to move data to SD card it doesn't seem to really move anything but takes at least 30 seconds to do it and still requires the SD in the 0hone to run the app
Does anybody know what's up here and willing to tell me?
Thanks maybe.
Yes I'm about to smash this **** ING thing.
Nickvanexel said:
Yes I'm about to smash this **** ING thing.
Click to expand...
Click to collapse
Try Odining the stock tar from www.sammobile.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Nickvanexel said:
Ok. Finally installed TWRP on the phone and made a backup.... I could just do it from there right?
Also considering trying either your rom or cm.. I had a couple more.precautionary questions if you could help..
1. When installing Rom I have found conflicting inforation on what needs to be wiped first ... most say just data, dalvik, and cache (so factory reset option in twrp) .... some say I need to wipe system as well. Witch is it?
2. Some roms seem to include supersu with them. If I have already installed it will that be any conflict ??
3. Installing stock rom require same process right?
4. Is there any version of cm that comes with kernel allowing over clock that is safexactly to flash from my current firmware ok3..?
I'm still not too sure about doing this but I can't figure another to solve the issues I am having with this phone, I got it used and it's off of warranty anyways.
Thanks...
Click to expand...
Click to collapse
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
bilgerryan said:
1. Some ROMs, like mine, have the austen wipe built into the ROM.
2. No
3. That depends on if you are using Odin or recovery
4. I don't use CM, too unstable for me.
Click to expand...
Click to collapse
So that means at this point you wouldn't really need to wipe before installing wicked rom anymore?
Also decided against any over clocking now, changed to performance governors and things are working great now, especially games. No hitching, we're I was getting 10fps or less I cod strike team it's now 30.. so if I install a rom it will be wicked, especially the function on it "fix external SD write" fixes my storage management issues than that alone would be great and the debloat and performance tweaks would be a great bonus.
Thanks.
Related
I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
try a task manager and see what is running in the background
try ending programs that may be chewing up memory
set up a swap
What do you mean by set up a swap? My SD card already has a main partition, an ext3 partition and a linux swap partition.
you made no mention of your sd partitions
something is most likely hanging up your memory which is why i said check with a task manager
you can always try flashing the adp again and then cyan
when i first went to cy's i had to do that
I'll try the task manager. Based on how slow it is, it may take me a few hours to get it installed.
i got a quick idea, try shutting off your phone, pull out your sd and try rebooting without it and see what happens without apps2sd going
update to ext3 if you are not already
delete your dalvik-cache if you are upgrading from a previous rom and didn't wipe
huh, did you not read his posts, he has ext3 and he has wiped
Don't know if it would make any difference, but maybe try to install HTC and 4.1.99 and then just flash .999 over the top of that.
hey knowfear, you are not too far from preme, right? do you guys know each other
gridlock32404 said:
hey knowfear, you are not too far from preme, right? do you guys know each other
Click to expand...
Click to collapse
Not personally but I have talked to him in PMs. He lives not too far away from me.
sweet, you might see me driving through your day in about 2, 3 weeks after preme gets me drunker than all hell
so just aplogizing before hand
The fact of the matter is that it simply is DEAD SLOW.
His development process is taken from the MS-developers-handbook.... just keep on shovelling on the bloat, and every once in a while release a new version and CLAIM that it is faster than the last, even when it is slower.
Then you get all the little kiddies, who update with every new version, each of which makes no appreciable difference, BUT because the release notes SAY it is faster, and the fact that they can't really tell, the placebo effect tells them that it IS faster. They keep doing this... several times, so the cumulative placebo effect tells them that it *must be WAY faster*, except that with every new version it actually becomes slightly SLOWER, so after MANY MANY "upgrades", what you turn out to have is something FAR FAR slower than the original.
Just to get a feeling for the differences, try out a stock cupcake build, then try FOUR CM cupcake builds that are evenly spaced out (in order), then again try the stock cupcake build. Then try the stock donut build.
If you want a fast donut that supports apps2sd, etc., and doesn't have the insane bloat, take a look at this one: http://forum.xda-developers.com/showthread.php?t=538456
This ROM is a simple rooted ADP1 donut base, with an "expansion pack" -- from which you can pick and choose the extra features you need/want so as to end up with a system that is optimized to YOUR needs, rather than just packing in everything including the kitchen sink and claiming it is the best thing ever.
zinite said:
I was running a G1 with Cyanogen Mod 4.04, Cyanogen Recovery 1.2. I updated to Recovery 1.4, installed the 1.6 .img, installed Cyanogen Mod 4.1.999, ran the fix permissions command in console, and rebooted. It is SOOO slow. Takes between 15 seconds and 1 minute for any button press or screen touch to be recognized. It is completely unusable. I have found a few posts about this, but nothing offered a concrete solution.
I have since done a wipe in console, and reflashed Cyan 4.1.999. It didn't fix anything.
My SD card is properly formatted for apps2sd, as it worked fine in Cyan 4.04.
Any ideas?
Click to expand...
Click to collapse
I had the same horrible lag when I went from 10.1 to .999, so I repartitioned my sd and tried again fresh and it worked perfectly...purrs like a kitten now...
kittens purring is a good thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fixed it.
I wiped, deleted dalvik cache in console (I can't find the command I used though), reinstalled, fixed permissions in console.
Thanks guys
This CWM script will reodex any custom ROM.
With BOOTCLASSPATH edit in dexo.sh it can work on any ROM and phone.
Reodexing gives some people perceivable speed up. And it frees data partition from system dalvik cache. So dalvik-cache rebuild is also accelerated.
I ran it with stock kernel (root injected). And had problems with running it on any custom kernel.
http://galaxytree.net/bravomail/universalOdex.zip
Also a good example of output from shell script into CWM console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great to see new tweaks. For me, flashing this mod went well, but it put me in an endless boot loop. I'm using a Cappy with a Jelly Bean custom rom. I know it's supposed to be "universal", but maybe some ROMs are not compatible. Any suggestions? Hope I can get it to work.
Using the android sdk you will want to try DDMS.bat and see what spew you get while the phone boot loops.
Sounds similar to what I used for all my roms.
Here are some tips I've picked up along my dev experience:
1. Make sure you have at least 50+ mb space free in /system. Else it may not complete and your /system/app and /system/framework folders may not work properly, thus causing many android core processes to force close and rendering your device unusable. If this happens, wipe, reinstall the rom, and delete more things using Root Explorer from /system. Such as unnecessary ringtones/notification sounds in /system/media and unnecessary system apps like *WallpaperChoosers.apk, stock launchers if you aren't using them, and other stuff you don't need. If you aren't sure what it is, don't delete it because it might be important for the use of your phone.
2. Also, it doesn't work on some roms, I'm not exactly sure why. But make sure you read the script's logs to ensure there are no errors. If you are getting mounting errors, make sure your phones /system partition is mounted as r/w (root explorer can do this). If it still doesn't work, try rebooting into recovery and mounting /system in mounts and storage and then try running the script.
3. Just because your phone is now odexed doesn't mean its gonna be a ton faster. In my experience, I found it to be a slight improvement from the original. In most cases it was unnoticable, so don't expect too much.
Cheers!
Sent from my SGH-I897 using xda app-developers app
Holy cow amigo. You started a bunch of threads. A little credit to original author would have been nice if you took the work and revamped it. All credit cause you didn't.
Sharing is caring. But I suggest you put where you got the script, etc, as well as the original author.
edit. upon further review, i see that you did change some things, mainly removing the original header (which is absolutely lame) and made it work with CWM. Also, you set a static BOOTCLASSPATH - which defeats the purpose of this script!!
Let me check my pms and emails. Someone contacted me a long time ago asking me review to their changes. Maybe it was you lol.
Sent from my EVO using Tapatalk 2
Nexus 4, rooted, CM, gravity box.
I want to update to CM11 M6 but I can't get my phone to make a nandroid (using ClockworkMod) because I keep getting an error basically saying I have insufficient storage. These are the steps I take:
Backup using titanium
Go into recovery
Backup using ClockworkMod
It's at this point where it lists backing up the system, but then it gets hung up backing up the data card. I have tried to go back in and delete everything I could possibly think of (w/out wiping the whole thing) but to no avail. I have cleared my cashe and even deleted the titanium backup which was around 1gb and still no dice.
Attached are some screenshots that may be helpful. There has to be something hidden but I just don't know where to look for it. I tried to install DiskUsage but I can't since I don't have enough room. How do I clear up this phone?! Any help would be much appreciated!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brahmaboba said:
Nexus 4, rooted, CM, gravity box.
I want to update to CM11 M6 but I can't get my phone to make a nandroid (using ClockworkMod) because I keep getting an error basically saying I have insufficient storage. These are the steps I take:
Backup using titanium
Go into recovery
Backup using ClockworkMod
It's at this point where it lists backing up the system, but then it gets hung up backing up the data card. I have tried to go back in and delete everything I could possibly think of (w/out wiping the whole thing) but to no avail. I have cleared my cashe and even deleted the titanium backup which was around 1gb and still no dice.
Attached are some screenshots that may be helpful. There has to be something hidden but I just don't know where to look for it. I tried to install DiskUsage but I can't since I don't have enough room. How do I clear up this phone?! Any help would be much appreciated!!
View attachment 2743357
View attachment 2743358
View attachment 2743359
Click to expand...
Click to collapse
You need at least 3GB of free space to make CWM able to create backup... but you won't find that backup in /sdcard/cloclworkmod folder it's in /storage/emulated/blablabla or something like that and you won't be able to get access there from your computer
parkourz said:
You need at least 3GB of free space to make CWM able to create backup... but you won't find that backup in /sdcard/cloclworkmod folder it's in /storage/emulated/blablabla or something like that and you won't be able to get access there from your computer
Click to expand...
Click to collapse
Ok, I'm not sure I understand. I'm in the emulated folder and went into the clockworkmod folder and keep descending and come to just 1 file that is just 7.63mb called "recovery-clockwork-....img". This can't be the solution, can it?
try in /storage/emulated/legacy/clockworkmod... or flash TWRP instead of CWM... if both won't help then you can try to make a backup with toolkit for PC, for example Wug's toolkit
Twrp is showing the backup size and a poseibility to compress it. You probably have much apps or there is some .something fokder what is using much or much cache just like on an desktop. Many things can cause it.
You may want to checkout what is using so much by deleting old folders from old apps or old things yiu dint use anymore.
Verstuurd vanaf mijn Nexus 4 met Tapatalk
I'm on an s5 neo, rooted but using the same software it came with.
I decided to try a factory reset, as I had done a few things I can't undo, like removing mtp application, with a root app remover whose restore function doesn't work on this device.
I was also thinking, that instead of personalizing everything, and downloading everything, and then debloating, I thought I'd start fresh and then debloat first.
Thank *god*I had gotten brave enough to download and install twrp and make a backup, that back up is where I am coming to you from now.
I used the twrp recommended wipe for the reset, not custom wipe. Worked fine. Powered back on. All looked well until I came across a screen that said "just a sec..." For an extremely long time, like 10 minutes...
Why wouldn't it fully turn on, any ideas? As of now I can't factory reset ever again.... :/ and I'd like to be able to.
I hasn't disabled anything crazy and could reboot normally before I tried the wipe. I just don't get what went wrong?
Any help is greatly appreciated.
I cant even start off with a new rom I don't think, they're all made for the 903m or 903f versions of this phone, and I'm on the international 903w. I'm guessing some thing significant is different or else it would just be called the 903.
Sent from my SM-G903W using XDA-Developers mobile app
what did you wipe in the custom wipe?
also this http://forum.xda-developers.com/galaxy-s5/general/rom-somewhat-incomplete-edition-v0-1-t3295464
I want to say it wiped data cache and dalvik cache
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
I want to say it wiped data cache and dalvik cache
Click to expand...
Click to collapse
Well, with a bootloop you can go to recovery and recipe, then wipe data then go to advanced options in twrp and delete the Android folder in both internal and external and that should fix the issue
Recipe? I should proof read this stuff before I post it. It should have said reset, not recipe
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
Like, as in deleting the "system" folder, should I have wiped that too?
Or would that totally erase this current android version? And I'd be even more stuck?
Click to expand...
Click to collapse
No, go to advanced options, file manager, then to either storage, touch the Android folder, hit the check mark in the lower right, select delete, swipe to confirm. Do this with both storages. It's not the system folder and doesn't contain anything that isn't rebuilt upon boot. But it does contain stuff from your previous install that is known to cause bootloops when going from an Android version to another. Nothing to worry about when you delete those folders. It's been the source of tons of bootloops for me
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G903W using XDA-Developers mobile app
Pawprints1986 said:
So, the android folder, in my case, I think I've only got the one internal storage path. I'd have to double check but I'm pretty sure. I have technically for some reason a bunch of storages called "USB drive". But I think they're all empty. And I think sd card and emulated lead to the same place. Its a weird setup lol
I just took a screen shot of it, I'll add it in here
Click to expand...
Click to collapse
Don't do it from within the system. Do it from within twrp
Here, I made a little video. I'm a 100% amateur videographer, so go easy on me lol
So ill try to put all the other information that's important here.
I tried flashing the Stock rom back to this phone through TWRP and I feel like I've flashed it about 8 times now. It comes up normally and I can go through the setup wizard and when I hit the home screen I tired getting Adaway. When I tried to download the apk to my phone and I try to choose a save location it keeps saying that I can't find a save location. Then I tried opening up the file manager and tried creating a new folder it says that the operation cant be performed. I have plenty of storage available on my 6T and I cant see what I'm doing wrong. I've flashed and reflashed both TWPR and the Stock ROM both Beta and official and I still run into the same issue. Is anyone able to lend a hand? Thank you in advance!
Edit: Fixed it!
I get this anytime I try to download anything to my PHONE. SD card not found
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Mi MIX 2S using Tapatalk
Coolaaron88 said:
I get this anytime I try to download anything to my PHONE. SD card not found
Click to expand...
Click to collapse
Format Data in TWRP
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Format Data in TWRP
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Let me try that and I’ll report back
Sent from my iPhone using Tapatalk
Coolaaron88 said:
So ill try to put all the other information that's important here.
I tried flashing the Stock rom back to this phone through TWRP and I feel like I've flashed it about 8 times now. It comes up normally and I can go through the setup wizard and when I hit the home screen I tired getting Adaway. When I tried to download the apk to my phone and I try to choose a save location it keeps saying that I can't find a save location. Then I tried opening up the file manager and tried creating a new folder it says that the operation cant be performed. I have plenty of storage available on my 6T and I cant see what I'm doing wrong. I've flashed and reflashed both TWPR and the Stock ROM both Beta and official and I still run into the same issue. Is anyone able to lend a hand? Thank you in advance!
Edit: Fixed it!
Click to expand...
Click to collapse
Hi, I'm facing same issue. Flashed many times stock ROM on both slots, and can't write any file or create folder.
How did you fixed it?
2be3_80 said:
Hi, I'm facing same issue. Flashed many times stock ROM on both slots, and can't write any file or create folder.
How did you fixed it?
Click to expand...
Click to collapse
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
bladestonez said:
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
Click to expand...
Click to collapse
Actually my data was encrypted but accessible through twrp. I did format data, couldn't boot system, but then I wiped data and it worked.
Thanks
Thanks!
bladestonez said:
As stated before enter twrp and format data/ factory reset. Something went wrong and your date was encrypted.
Click to expand...
Click to collapse
I ran into this same issue and this fixed it for me!