Quote:
Originally Posted by arrrghhh
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!
|
so because you have never had a problem that means there is no way someone else could? yeah, thats real scientific right there. guess since i have never had a house fire that no one else has either. do you see how stupid your logic sounds?
i can see by your statements you have no real scientific background at all. you can just say "why would you intentionally run a bunch of programs before booting Android?". why? because maybe im using winmo during the day while im at work then want to run android once i get home. maybe i dont feel like, or remember to reboot so i can to it or forgot to use task manager to kill the apps that i was running earlier. what difference does it make? the point is there is an issue there. really, it doesnt even need to be apps in the background. some of the 6.5 roms i was running would start off from a reboot at 60% or so and thats with nothing running.
where are you getting android has anything to do with the mem in winmo? your harping on that like thats the issue when it isnt. WINMO MEM IS THE PROBLEM NOT ANDROID. is that clear enough for you to understand? as for what my % actually mean. well, lets see, 65% of 115megs free is 74.75megs give or take. that leaves only leaves about 40 megs to boot android. that according to winmo's system info app. not some 3rd party app. you can call whatever you like that still doesnt change the fact that at 65% mem usage(or as you want it, only 40 megs of mem available) android WILL NOT START. so, infact if you have a VZN Touch Pro, you can have issues booting/running android depending on the ROM your running.