Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Apple Tankwatch -- Ignore unavailable to you. Want to Upgrade?

To: sylvester80 who wrote (8746)	8/25/2011 1:31:06 PM
From: iggyl	Read Replies (2) \| Respond to of 32692

... or buy an iPhone and avoid this POS.

To: sylvester80 who wrote (8746)	8/25/2011 3:12:39 PM
From: pyslent	Read Replies (2) \| Respond to of 32692

Thanks for your suggestions. My phone is supposed to have 512 MB RAM, actually, but when I go to the Running Services tab, I show 196 MB used, 124 MB Free (doesn't add up to 512 MB, does it?) htc.com Anyway, I don't see many services that I'd want to kill (other than some related to HTC Sense). Is it your experience that 124 MB free RAM is not enough for trouble-free operation? Some of my niggles seem to be Sense UI related, but some are just things that every Android user I know learns to live with, like I have. My wife has a Nexus S (also 512 MB of memory), and it doesn't seem better in any appreciable way. Is running out of RAM or overloading the processor the problem, I wonder? Here's a typical example of "multitasking" with my phone... 1) Launch Youtube. 2) Start playing a video 3) Get a notification of an incoming email, and switch to email. 4) Video stops playing. 5) Go back to Youtube. 6) Some of the time, I can resume playing where I left off. Some of the time, I have to reload the videos page, and playback starts from the beginning. That's not the kind of multitasking I'm used to on a modern device. I understand that the video doesn't need to continue playback in the background (very few platforms allow this). But my state should be saved no matter what. And yes, I expect the saved state to survive even if the OS needs to close the app while in the background, because I have no control over that. So yes, maybe you're right that technically, Android does true multitasking, but that only lasts until it doesn't. And true multitasking might have some advantages in certain situations. But in my experience, I need a reliable "save state" far more often.