Jump to content

biggiesmalls

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About biggiesmalls

  • Rank
    Newbie
  1. Forgive me if this has been asked before: when start a new line in a text message (i end the previous sentence with a .) The next line never starts with an uppercase character? I'm still running the old 6.1.4 ROM but i don't really feel like upgrading, so a registry tweak for this would be awesome. (edit: i do have the option that should make this work enabled somewhere, just doesn't seem to do anything)
  2. Interesting, didn't know that trick. The compass doesn't seem to work so well though, it's never really pointing north... :) Anyway, here's my list (not really any software specific for this device, but seems to work just fine): - HTC Task manager 2.1 (you'll have to reboot after installing this for it to work) can't remember where i got this from. - Clean RAM (must have for me, apps seem to get shutdown randomly when low on RAM) http://htcaddicts.com/download.php?id=165 - Microfi Nitrogen, an excellent audioplayer http://code.google.com/p/microfi-nitrogen/ - nanogroove, an (unofficial) native grooveshark app http://www.nanogroove.net/
  3. Well other than the "memory leak" problem i'd say it's a great device. I've been using it for a couple of months now and really like it. Sure it can be a bit laggy at times, that's just windows mobile. If you can't live with that, don't buy a WM phone. I'm very impressed with the quality of the screen (not so good when viewing outside in direct sunlight though). But watching a movie on this thing is awesome.
  4. It does make sense that some part of the RAM is reserved for the "phone part" but i think that memory must then be somehow mapped to the radio chipset, bypassing the OS. (i think some of you mentioned that windows itself doesn't show the advertised amount of memory, only Samsung's own app does?). I'm sure the device contains 256 MB of RAM but what value do those numbers have if they're being abused like they are now? That's like saying my PC has 4 GB of RAM when in fact it has 3 GB of actual RAM and 1 GB of video memory on the gfx card. The good news is that I found out that while apps are running in the background (or the device is locked) and apps start closing, they receive a WM_CLOSE message. Applications are free the ignore this message but the default behavior of this window messages is to proceed destroying the application's window. So to test what happens when an app explicitly ignores a WM_CLOSE message i made an app that does just that. While other applications got closed my app got the WM_CLOSE message but ignored it. I was expecting that the phone would just kill the process eventually but that didn't happen. The WM_CLOSE message also made me think that only Samsung is the one to blame here, since Windows Mobile will send a WM_HIBERNATE message to applications (asking them to free as much memory as possible) when the amount of free RAM is below a certain level. But i never got a WM_HIBERNATE message (which probably means the system wasn't that low on RAM anyway, which is also confirmed by the Samsung application that usually shows around ~35 MB of free RAM when it starts closing stuff).
  5. 1) It's the only OS (along with desktop/server versions of Window) who's API i know inside out, i've been using it for years. 2) Both as a developer and user: The freedom you have to modify and install just about anything. 3) As a user: nothing really, Android based phones look awesome though. As a developer: I'm not really into managed programming languages, Android has very limited support for applications written in C++.
  6. I'm holding back when it comes to blaming Microsoft for this, i don't think there are leaks in Windows Mobile 6.x (or at least not serious enough to cause the problems we're having with the Omnia II). You shouldn't forget that OEMs can and will heavily modify Windows Mobile by adding their own drivers/utilities and what not. On my Omnia II for example i have noticed that with the message application open (i don't really know what the official name is but it is the screen where you can view your text messages/e-mail accounts etc.) most of the scrolling operations, at least that's where i find the effect to be the most noticeable, will kind of stutter and also the Samsung Touch player will show hick-ups while playing a movie (you can clearly see it while playing the "imploding helicopter" demo movie). When you kill the message application, all scrolling operations (in the file explorer for example) and the touch player will work just fine. In my opinion the Windows Mobile graphics subsytem is probably just fine, i think the modification made by Samsung (e.g. an app leaking memory, poorly coded driver etc.) are the more likely causes of the problems we're experiencing.
  7. I'm not entirely sure how it works on Windows Mobile but i would suspect that any (GDI) handles still in use by a process that is about to exit would be freed by the operating system. I've got some gfx drive experience when it comes to windows NT but, again, i'm not sure if the same applies to windows mobile. But freeing bitmap memory would be delegated to the display driver since it was probably also used to allocate it in the first place. A 7 year old PC would probably also be able to run Windows XP and 20 instances of Internet Explorer while having Microsoft Word open (without automatically closing any of them because it is low on memory ;) ) I'm not stating that all of the 100 MB memory is video memory, or that any of that memory is video memory at all. Just writing down my experience about how it is odd that applications which consume a lot of memory from the heap - but aren't allocating a lot of video memory - won't get closed and some applications (one i'm working on for example) gets closed while i barely allocate any data memory but i do make a bunch of GDI calls to create bitmaps. Edit: Anybody noticed that the Samsung Touch player usually doesn't get closed? I sometimes notice that other applications get closed in favor of the touch player.
  8. Hey all, Stumbled across this thread while looking for some Omnia 2 RAM/app closing information. I develop applications for windows mobile devices and also experienced my application unexpectedly sometimes while in the background. (Still using official WM 6.1.4 ROM, no modifications whatsoever) I starts closing applications when about 40 MB of ram is left. But one thing i'm still investigating is that i don't seem to get any WM_HIBERNATE messages at all. A WM_HIBERNATE message would normally be sent to windowed applications to ask them to free any resources not in use because the system is low on resources. However my application never seems to receive a WM_HIBERNATE message, instead a WM_CLOSE message is what i get. Which (if no special precautions are taken) gracefully shuts down the application. I suppose i could ignore a WM_CLOSE message if the "Exit application" action wasn't initiated from inside the application but i think Window Mobile/Samsung utilities just start killing applications if they aren't responding to a WM_CLOSE. However, this shouldn't be the cause of any "app closing problems" because i wasn't expecting a WM_HIBERNATE message in the first place since it shows ~40 MB of free RAM when it starts killing app. But i thought it was worth mentioning it. Also wanted to mention another thing i noticed: (if you're not a Windows (Mobile) developer you probably won't understand a lot of what i'm saying here...) When creating a lot of DC/BITMAP handles (Create(Compatible)DC/CreateCompatibleBitmap) it seems that the application gets killed sooner. When there's still 40 MB of free RAM left my app will get killed more quickly than say a personal navigation application. I'm not saying the navigation app is more lightweight regarding resource usage (on the contrary, taskman shows it uses ~8 MB of RAM while my app only uses 1.8 MB) but i'm suspecting the navigation application just creates one full screen Bitmap and does all it's drawing on there, while my application creates a whole lot of Bitmaps/DCs. Mind you, my application barely allocates any memory from the heap... This is just a wild guess: Could it be that the video memory is exhausted (is this the ~100 MB reserved RAM memory?) And that, while there's still RAM left that isn't going to be used as video memory, the device thinks apps should start closing because it's low on memory (although that memory is video memory). I'm saying this because i once got an OUT_OF_MEMORY error while creating a bitmap and there was still 40 MB of free RAM. Also, while my app probably uses around 8 mb of memory because of my CreateBitmap calls, taskman shows only 1.8 MB. This seems to support the theory that Create(Compatible)Bitmap memory is allocated as video memory. If you made it this far... thanks for reading my novel. ;)
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.