Hi,
I'm a new MDA II owner (since yesterday) and already ran into some weird problems.
One prob is: the MDA II is closing open programms after some idletime in the backround. That means, if you e.g. open pocketinformant, and put it into backround (as an Icon in tray) and you wait some secs (about 30-60), the pocketinformant just pops away. Also with some other programms: Totalcommander, XCPUScalar, almost every programm with icon is being shut down by the MDA II (or some garbagetool).
If you hold them in focus, the resist.
It doens't matter if you are activesynced or not...
Tools like smallmenue or wisbaradv or pocket controller are not shut down.
Any idea?
Sincerely
Dejan
Common,
you're the XDA-Developers, whoelse as you might now, which tweak in the registry, which .dll or whatelse leads this device to handle open programm in such a bad manner.
How can I make the device not closing some programms? Does anybody knows a tool, which prevents other tools from being closed?
Anybody?
128mb and still 94% free RAM, because the device closes the software as soon as it goes in the backround....
Greets
Dejan Ivkovic
Yeah seen the same problem here, no way to fix it yet.
Re: MDA II closing programs after some ideltime
IvkovicD said:
Hi,
I'm a new MDA II owner (since yesterday) and already ran into some weird problems.
One prob is: the MDA II is closing open programs after some idle-time in the background. That means, if you e.g. open pocket informant, and put it into background (as an Icon in tray) and you wait some secs (about 30-60), the pocket informant just pops away. Also with some other programs: Total commander, XCPUScalar, almost every program with icon is being shut down by the MDA II (or some garbage tool).
If you hold them in focus, the resist.
It doesn't matter if you are activesynced or not...
Tools like smallmenue or wisbaradv or pocket controller are not shut down.
Any idea?
Sincerely
Dejan
Click to expand...
Click to collapse
Sounds like you're running low on program memory, if thats the case
your device is doing what its suppose to do! Open a few programs and then check your memory and see.
HTH
HTH
Not in my case, over 80Mb free...
@qman
well, this should be the normal way, IF I run into some memory trouble. :wink:
But, my Autostart/Startup is quite filled up with the default programms, which are being loaded by system to handle alle the little goodies form the PE AND which are being installed by default during first initialisation after hardreset.
Dispite that, I only load two other programms while booting: smenue and wisbaradvance (not worth being counted as memoryconsumer). Still have 94% of programm memory free, (or about 65MBRam. So If I load PI4, I might use some 100kb/s, and than PWord, which uses some more 100Kb/s. Ok. I still might have about 90-92% of programm ram free (aprox. 62-63MB, I cannot get the right value, because the MDA just closes the PI4 :x )
So the routine might do the right thing, but in wrong time and toooooo conservative.
BTW, this effect is also shown up on a fresh hardreseted device, just load pie and pword amd pexcel, you will see, how PIE is just vanished....
Greets
Dejan
BTW Does anybody know some dudes at MS Developing stuff (esp. Windows Mobile 2003 Phoe Edition)? In my eyes, this is one ofe these:
1. The memorycoresettings are copied from earlier days, while the devices only had 16-32 mb memory. :lol:
2. Is a bug.
Big Bug in memorhandling for open programms
Big bug in memoryhanding for open programms
I've posted following message to the microsoft.public.pocketps.phone_edition newsgroup with hope, that any of the Microsoft developer would read it, and post an reply:
to "Microsoft Mobile Stuff"
please confirm following bug:
The new Windows Mobile 2003 Phone Edition (at least german edition, might also be at english one) has a big bug at the memoryhandling routine, which handles the closing of open programms to keep programm-memory free.
Situtation: if you load programms and get over 16mb of used memory for programms at the shared memory pool of your device, the device (here especially MDA/XDA II) starts closing programms until it gets under 16 mb again, it doesn't matter, if your device has 128 Mb free, or you moved the slider at memory configuration to the left, so the programm memory is > 80 MB)
If you load enough load-and-stay-resident programms (traytools, menue extensions, desktop enhancments e.g. wisbar, smenue, pocket controler, aso.) to keep more than 16 mb used, you cannot load any further programms, because the device reports insufficant memory for execution. You can only use the loaded tools.
If you remove all \windows\startup entries and boot clean, you can load all the programms, which are being closed before, without any problems, the programms stay in memory for hours....
luck, the telephontool is somekind hardwired, so it functions even if other programms are quit with memoryerrors...
If this value of 16mb is not being set up into registry, than it is a hardcoded bug.
Anyway
Please check this out, especially an foreign language Mobile 2003 OS, and provide an bugfix fast, because with 16mb of usable programm-memory, you hardly can use your PE in a professional fashion!
Sincerely
a frustrated PE user.
Click to expand...
Click to collapse
You can check this effect just load programms and look at your memory consumption. It (MDA) should close all programms until you get under 16 megs again, if it cannot, because of resident programms, you will get insufficant memory errors.
Dejan
[/b]
Just don't want to retype it again
http://www.tekguru.co.uk/phpBB2/viewtopic.php?t=512&sid=524b13482c3e2596000dde9a7cc05e09
Is this a hardware problem or an issue with the ROM on HTC Himalaya Phone Edition devices? Or is it a problem with Windows Mobile 2003 Phone Edition?
I mean... Will/Can this be fixed through a software/firmware update?
From the Microsoft Newsgroup:
Windows Mobile 2003 supports only 33 Processes at a time!
After a normal start the XDA II has over 26 running processes, so removing the Flash-Programs and every not needed app in Autostart is a good idea!
Hi guys,
Hope this hasn't been asked before too many times. I did do a search but couldn't find anything.
I've just written a small app for ppc (works on 2002, 2003 and WM5) to act as a countdown timer. However, unless I set my Wizard to never shutdown, it turns off whilst the timer is still going.
I've had a look through the latest SDK's (I'm using Visual Studio 2005 and the latest version of the Compact .NET Framework) but can't figure out how to stop this.
The only way I can think of is to find the reg key that controls this (I assume there is one), copy it, set it to a rediculous or null value and then copy it back again on shutdown. But it seems like a god awful solution and prone to any number of errors where it doesn't get copied back.
Is there a simple ".NET" way to do this?
BTW Although I've been a developer for [cough] years, I've never written anything for PPC before.
Cheers,
Bassey
Hi
take a closer look at HKLM\System\CurrentControlSet\Control\Power. There you will find system and user idle timeouts. To prevent a PocketPC WindowsMobile system from going to sleep, you must reset the System idle timer periodically. This is done by a call to
void WINAPI SystemIdleTimerReset (void);
I think this will be the same for WinCe 3.0 up to WinCe5
If you think about a good programming starter book, I recommend Douglas Boling 'Programming Microsoft Windows CE .NET' (3rd edition). It talks about nearly everything. It is my favourite book.
regards
Josef
Thank you very much indeed. Have just ordered the book as well.
Cheers,
Bassey
Hi, I'am quite new to forums so sorry if this is not the right place, the right time or formulation. Tell me and I'll try to improvejavascript:emoticon(':wink:') Wink.
I have a brand new (second-hand but new for me) Qtek 9100 also know as HTC wizard. The rom is the Qtek version (latest I think).
I develop java applications for me (if one is interesting I will post it, promised!) and I would really like to build some tools for my wizard, especially one using bitmap images in relation with a GPS.
I found great tools on the Sun website with Netbeans, J2ME emulators, all integrated and working fine. I tried plenty of examples and now I discover that midlets can't access the filesystem through the MIDlet manager (Tao intent)!
That's a nightmare, everything was fine, I was ready to start developing. I tried to understand the specs (JSR 75 for files, JSR 82 for BT, ...) and I discover that I can't open a bitmap file (even PNG would satisfy me) on my storage card.
javascript:emoticon('') Sad
Can anyone help?
I also have tried to escape and go to odd VM.
I found great implementations but are they reliable enough? does someone use them?
My ranking is ...
1) EWE (http://www.ewe.com/): good installer, large doc, no Bluetooth but com port, graphic library. Is the speed correct?
2) Superwaba (http://www.superwaba.org/): Bluetooth, good library but memory issues : Image objects limited to 64Kb. How could I process a photo of 1Mpixel? Also a strange look&feel
3) Mysaifu (http://www2s.biglobe.ne.jp/~dat/java/project/jvm/index_en.html): why not ? Seems comprehensive and light, but little documentation (at least in Latin characters).
I would prefer to go on with midlets.
Do I have a security issue (need a certificate?) ?
Does it exist another midlet manager implementing the JSR 75 option?
Thanks for your help
Christian
Correction
For those who would like to browse information on JVM, I've made a mistake :
EWE can be found at http://www.ewesoft.com/
Found a good summary of JVM's at http://www.comp.lancs.ac.uk/computing/users/fittond/ppcjava.html
It seems that EWE is not that bad, I will try
Christian
I'd love to see some cool new midlets to run on these phones. Good luck getting things working, I'm no help though.
Hi,
I'm trying to develop a WM6 mobile application (for personal use) in VS2005
using C#. The application uses the microsoft.sqlserver.smo assembly in order
to connect to an instance of SQL Server and be able to manage it. The
problem is when I build and deploy the application, it copies a whole lot
of other assemblies to the WM6 emulator which causes it to run out of
storage space, causing the build and deployment to fail. Is there any way
around this? There's seems to be no way to increase the storage size of the
emulator. Is there a compact version of the SMO assembly? I understand that
the standard SMO version is for the desktop and therefore drags a whole lot
of other ones with it which are not necessary or usable on a WM6 device.
Please help me. I'm stuck with my development due to this.
Thanks.
Hello,
I have problems running a program and debugging the Win32 C++ project on the Sedna.
After i created a small application but got the same result when running in debug,
- breakpoints where not hit
- the messagebox showed different buttons then passed in the function
- calling the NkDebugPrintW function makes the program crash before something happens
Anybody else experiencing likewise problems, any solutions?
The program does not run properly and there's no way for me to test where my software goes wrong,...
Thanks in advance