Quote:
Originally Posted by natemcnutty
I doubt we have the same problem as the HD2 because they can't even format that section, but I guess we could test it pretty easily by taking some space away from the data partition and see if the issue goes away. Could it be running out of space on the cache? What if we upped it to 64 MB instead?
|
nahh the cachent isnt running out of space. That was the first thing i checked, but then i noticed errors on dmesg.
Since cache partition begins at 1E000000, the errors start showing up at 1ff31000 which is really close to the end. We will need to try a few things to see whats up.
A good test to see is if you or lmiller can move your dalvik cache over to this partition. And recreate my issue. Simple link should do the job. Right away android gets angry since a corrupt dalvik cache is trouble for any app in the bad area.
I'll try to reduce the mtd parts and see if the problem keeps happening. I'll reduce the mtd from to end at 1FE00000 which is about 510mb (skipping the last 2mb).
Now a separate issue is the recovery. which is marked as protected. we can read it but writing to it does not work. So i get the feeling this needs to be extended as well.