|
||||
Just to add a little perspective, looking at the apple touch/iphone
128mb RAM On boot, darwin locks down 16MB ram for itself, leaving 112mb for everything else... then the OS loads up.... eating roughly 88-94mb ram to get to the pretty springboard (icons, aka "today") screen. Like WM, iMacOSX (or whatever you call it) apps don't actually close, generally, when you go home. Apps like safari (web) eat that last 22MB like candy. So yeah, WM5/6 is a hog. But there are other hogs out there. It does make sense to just give up on the wimpy 64mb ram though - it's 2007, we have terabyte drives selling for $120 and a 4gb stick of ram is $100, for heaven's sake! |
|
||||
Only because nobody's pointed it out already, RAM (besides being fast) consumes power all the time whether it's in use or not, and that affects battery life. The Windows Mobile Team blogged that they believed (at the time, for WM5 anyway) that 64MB was the optimum RAM/battery life tradeoff point for the foreseeable future. Unfortunately I can't find that link, but here's another one that addresses the crux of the OP:
http://blogs.msdn.com/windowsmobile/...14/438991.aspx Overall it seems to me this thread should be dead by now - the OP's question has been answered. I apologize for extending it (especially since I'm not a Titan owner).
__________________
XV6700 w/ Custom Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) - from Helmi_c and the guys at PPCGeeks.com
|
|
||||
Also, RAM is volatile.... You would need scripts and settings and whatnot if you want to have volatile solid state memory... It would be slow enough to defeat the purpose.
__________________
|
|
||||
Quote:
battery - 800mah (yep, HALF) cpu 400mz screen 480x320 (yep, 2x) ram 128mb (2x) store 8gb (don't even get me started) wifi, 802.11g run time ON WIFI -> 5+ hours (vs for my 6700, er, 2.5 hours with a good tail wind) I think the tiny, microscopic, nearly unmeasurable 1-2mah drain of another 64mb of ram is NOT the issue, nor could it POSSIBLY be the extra $2 in the bill of materials cost for the OEMs. Honestly, I do not know what the problem is over at redmond. Oh wait... Quote:
Apparently the WinMobile team needs to read some more |
|
|
|