• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Switched from art back to dalvik, still have no storage

CrimsonToker

CrimsonToker

Android Expert
I knew the apps would fill up storage, but when I decided to switch back I figured it would be back to what it was. I did make a backup beforehand but when I restored it still had the full internal storage. So what's taking up all the memory and how do I delete it? I had just flashed cm11 last night and installed only the basics to get my phone up and running, so there aren't that many apps
 
Wait, so you restored your apps off a pre-runtime switch backup after you switched runtimes? If that's the case you just reinstalled the ART compiled apps. That's why they're taking up so much space.
 
OK, so would my only choice be to uninstall and reinstall said apps? That would be annoying but it's early enough that I could simply reflash the ROM
 
Just switching from ART<->Dalvik should be enough to recompile the apps. You shouldn't have to manually backup or restore anything.
 
EarlyMon said:
Depending on what you have, I can dig it. :)

But stay away from other. ;) :)
Click to expand...
What about stock task killer, EarlyMon? By which I mean, holding home button and closing recent tasks? I've given up App Killer and Clean Master, but I still use this constantly. Is it really a bad thing?
 
CrimsonToker said:
What about stock task killer, EarlyMon? By which I mean, holding home button and closing recent tasks? I've given up App Killer and Clean Master, but I still use this constantly. Is it really a bad thing?
Click to expand...
It depends on the phone manufacturer or the rom developer.

Sometimes that hooks into the Android app manager, and even if it does, it's still a force close so you have to watch for orphaned services and creating zombies. Sometimes even that is done right.

Sometimes it just removes the app from the recent apps list.

And sometimes it's just baloney.

I've had that baked into roms that I trusted because I was a member of the rom team and knew what was going on.

Even still, use judiciously and only with good reason.

I believe you'll find that things like Google Play Music won't respond to that hack at all, in a great many cases.

And that should tell you something. ;)

Assume that you're just clearing your list - if you get more, bonus.
 
EarlyMon said:
It depends on the phone manufacturer or the rom developer.

Sometimes that hooks into the Android app manager, and even if it does, it's still a force close so you have to watch for orphaned services and creating zombies. Sometimes even that is done right.

Sometimes it just removes the app from the recent apps list.

And sometimes it's just baloney.

I've had that baked into roms that I trusted because I was a member of the rom team and knew what was going on.

Even still, use judiciously and only with good reason.

I believe you'll find that things like Google Play Music won't respond to that hack at all, in a great many cases.

And that should tell you something. ;)

Assume that you're just clearing your list - if you get more, bonus.
Click to expand...
Lol. Good Sir, Google play music is one of the first things I debloat. Along with a good majority of the rest of the Google bloatware. Usually all I keep is play store, play services and play games.

What are you talking about when you say "orphan services" and "create zombies"?
 
Below Lollipop and ART (the new Android Run Time) the equation is -

Android = compact, real-time Linux + Dalvik Virtual Machine + apps that run inside the Dalvik and use Linux/system services.

A music player is simple and starts up built-in services. It's why you can switch to another app but the music keeps playing.

Kill the app and the services looking for the owner/controller app can get mighty confused.

Even if the music stops, you can get a lost service looking for its daddy who ain't never coming home. So they sit in an unkillable state known in unix as a zombie.

You restart the app, get a new copy of the service that works - but the zombie copy is left behind, consuming ram and confusing the kernel.

Not always.

But probably more often than you know.
 
Excellent explanation of zombies, EM. I don't think I've ever heard it explained that clearly and concisely. :thumbsupdroid:

Also, this is all up in my head now:

It's in my head, in my head...
 
EarlyMon said:
Below Lollipop and ART (the new Android Run Time) the equation is -

Android = compact, real-time Linux + Dalvik Virtual Machine + apps that run inside the Dalvik and use Linux/system services.

A music player is simple and starts up built-in services. It's why you can switch to another app but the music keeps playing.

Kill the app and the services looking for the owner/controller app can get mighty confused.

Even if the music stops, you can get a lost service looking for its daddy who ain't never coming home. So they sit in an unkillable state known in unix as a zombie.

You restart the app, get a new copy of the service that works - but the zombie copy is left behind, consuming ram and confusing the kernel.

Not always.

But probably more often than you know.
Click to expand...
Oh man... Just when I start to think I have the android basics figured out, some new info throws a curve ball... Lol
 
So EM, would it then be better to just press home and leave an app in the background for the system task manager to take care of? I think I read in one of these threads that android is hard wired to kill a task that has been left alone for too long, is that true? Thank you very much for all the knowledge you share and work you do for this community, all out of the kindness of your heart :)






And for e-peen. Let's never discount good e-peen lol
 
You must log in or register to reply here.
Back
Top Bottom