Quote:
Originally Posted by Mylt1
how can you say that when it boots fine when there is nothing running in the background other than winmo itself? seems that somewhere between 60 and 65% mem usage and above can and does cause issues with android booting. and really, anything above 65% usages prevents android from booting period. so you just dismiss problems that people find because you dont believe in the way there finding them? thats real scientific. as far as my method, it most certainly is "consistent". if your using 65% of your mem in winmo according to task manager and android wont boot and its the same thing every time your using 65% thats consistent and repeatable. last i knew, something that was repeatable from start to finish with the same results was proof of concept with a scientific experiment. most developers and testers are running andriod off a fresh boot. they arent thinking about the "what ifs" like what if someone has been using there phone for the morning then wanted to switch over to android without doing a reboot or using something like task manager. again, i just ran the phone up to 65% usage and yet again, android would NOT boot. this may not be a problem for sprint users but for those of us that are VZN users it is indeed an issue we need to be aware of. so if a rom your using is not running less than 60% on boot then you can have issues with android not running. so wouldnt you say thats rom related?
so, any VZN users. you need to be running a pretty effecint rom if you want to run android too. if your running near the 60% mem usage mark then you need to either reboot or use something like task manager to kill any apps that are running in the background(IE they dont close all the way) before trying to boot android. another option is, if you want to run just android, to make a stripped down custom rom. 6.1 is a good option an you will need to drop the pagepool to get it as low as you can.
|
Mainly because you're the ONLY one to report it. I haven't had an issue, and I've booted Android from a WinMo phone that has been running for days, and fresh boots. Haven't had an issue. Perhaps it is just the craptacular VZW phones, but why would you intentionally run a bunch of programs before booting Android? I'll play with it myself, but that just sounds stupid. I don't leave programs running on WinMo for a reason, so I don't know why I would go out of my way to prevent Android from booting.
Again, with that said, I've never, EVER had an issue with Android booting because of "low memory" as you call it. Besides, those 60%, 65% numbers... what are they really? How do you know that piece of software is even reading it accurately? What are you using in Android to get the stats? My point is your procedure you say is repeatable, but there's no way to get stats from RAM if Android doesn't have full access of the device... How does this not make sense to you?
Alright, so here's what I had running.
Total Commander
Google Maps
Solitare
Streaming Media
HTC GPS Tool
TCPMP
Bubble Breaker
Teeter
Windows Mobile
Comm Manager
Word Mobile
Excel Mobile
PowerPoint Mobile
OneNote Mobile
Opera Mobile 10
Adobe Reader
ArkSwitch said I had ~50,000k free. I was able to get it down to 30,000k, but it kept bouncing back up. I think ArkSwitch was killing apps or something, not quite sure. Again, a reason why this isn't scientific whatsoever...
But Android booted just fine for me. So I encourage all the VZW users who have RAPH500's to do this test. I am calling schenanigans Mylt1!