So much pique!
ok what ever... even though iv already fixed this in the G300 with a script for memory management,... that's how i'm not speculating
lol you are speculating - see above for my fact-tastic answer. You have drawn concluions beyond the limits of the available evidence.
are you even working on anything for the g300 / its community ? or been looking into this matter....
Read about, you'll see I've been fiddling with the kernel and supplied a couple bits and pieces.
or do you just like to troll its threads lol, taking up peoples time who actually are doing things for the community... like in the guide threads, polls, etc..
But please, don't allow ignorance of my modest contributions prevent you from to launching into an ad hominem! Feel free But back on topic...
I'd concur that its likely a memory related issue of some kind. Like you said, the kind-of regular, lengthy interval between hard resets is pretty indicative. I feel no need to divulge my technical background, but suffice to say, I have one and it was, at one stage, professional. Android being what it is, it could be a leaky app. Or, being that this is a beta quality release, it could be that the OS itself is leaking. It could a range of things; one that I understand, one that you understand, one that somene else understands or one that no-one around here can fathom. We don't know, but the clues may be there in the logs I mentioned.
Setting memory thesholds etc may well alleviate the problem, much like a sticky plaster, but applying simple diagnostic methods is no less appropriate... No need for voodoo.
Kill the bee... and ultimately... you'll have nothing to spread on your toast — John Shuttleworth