Quote:
Originally Posted by arrrghhh
+1 to what nate said, and I think I can speak to #3 specifically. This is most likely due to your SD card in general, have you tried a different card? Sometimes I wonder if this project is just slowly basting our cards until they eventually die a glazed and delicious death.
Sorry, I'm hungry.
Also in respect to #2 - seems to be related to this nasty system_server process absolutely hogging every processor cycle it can absorb. Devs are looking into the cause, but the reason seems relatively unknown at the moment.
|
That's really interesting, thanks. It's funny, with respect to #2, I had just discovered the same last night.
I wonder if it is something data.img related with that one. I was rebooting a lot testing out the new kernels, and after a while, the number of times it would boot into #2 was almost 100%. I've since moved back to a known good data.img I had backed up and it booted up okay. I'm not completely sure though, could be a coincidence.
I do wonder if the project is damaging our SD cards. Every time I reboot, even using the shutdown command, one of those FOUND001.fck files is generated, and that's not a good sign. Sure we can delete them, but if nothing is messed up, those shouldn't being generated.