I was talking about before flashing. Before flashing the el29 kernel I was making sure I was supposed to select the wipe.data cache and dalvik options, for flashing the kernel itself
Wiping cache and Dalvik before flashing does nothing.
The Dalvik cache is an association of apps to one another.
Example - you cannot launch the dialer without launching contacts.
Android = embedded Linux operating system (including the kernel) + Dalvik Virtual Machine + apps that run inside the Dalvik and use Linux services
The main cache is the operating system cache - just like your browser has.
Those two caches are in a separate partition from the kernel.
Shouldn't matter to ever wipe those before flashing. If a developer says to with his payload, fine. There's probably an exception that I can't think of.
But always wipe afterwards, no matter what.
The first sign of app trouble, what's the right thing to do?
Fix permissions, wipe cache and Dalvik.
By default, you're going to end up doing it at some point after any flash anyway - get the first one out of way, do it right after flashing.
Next to checking md5 sums, and always making nandroid and app/data backups, that's an essential flashing habit to pick up.
Make sense??
PS - and for some apps, you want to wipe their individual caches while attacking trouble.
Android has a lot of caches lol.
This is possible. Just seems weird that even my original battery went bad overnight, going from perfectly fine and usable to totally shot. And then for this new battery to have issues immediately after Iinstallation independently of the old battery would be a weird coincidence. Thats what makes me lean towards a problem not involving the battery itself, but something the phone is doing.
Remind me - have we replaced the cable?
Cables can and do go intermittent and can develop faults where they appear to be correct - but simply aren't.
Never underestimate Murphy's Law in any of this. Coincidences, however bizarre and unrealistic, happen. Never rule them out.
Let's just say that they keep life interesting.
I just did a clean flash over to project x 2.8 from a newly downloaded el29 direct boot and battery still srems bad. Ive lost 7% battery in ten minutes. What could it mean if im on a newly flashed rom and still having trouble? Wouldnt that fix any permission issue right there? What could I have done that would alliw the battery issues between roms when everything is wiped?
I've been on a rom development team - I've had to fix permissions on my team's roms, which passed every test flashing and beating - right up to the point where I went ahead and did a final clean flash so I could enjoy my own work.
:rofl:
Bad flashes can happen any time and take any form.
Outstanding!
Sorry for flood posting - can merge all of those in a little bit if you prefer.
Done!