There you go!
http://wmpoweruser.com/?p=15451
Techticker.co.uk have published this summary of the recently held UK TechDays seminar held by Microsoft to introduce developers to their new mobile OS.
While the 9 minute video by and large cover information we have heard earlier, one issue of note is that apparently each application will only have access to 2 GB of storage on the device, irrespective of the actual size of storage.
Don't really see that as a problem; the main storage hogs are going to be music/videos/pictures, which are handled through accesible libraries without this 2GB limit. Maps for GPS apps could hit the limit, although I think I see the envisaged scenario being more on streamed data with caching.
Yeah I don't see what's the problem here. Just more BS drama from WMPoweruser to generate traffic.
Tito662 said:
Yeah I don't see what's the problem here. Just more BS drama from WMPoweruser to generate traffic.
Click to expand...
Click to collapse
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Yea, this is pretty restrictive, but you guys make it sound like 512MBs. How many apps do you have installed on your device as of now?
Spike15 said:
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Click to expand...
Click to collapse
No, it's Silverlight Isolated Storage for saving stuff 'on disk'. SIS stores have specificed, finite sizes. Who knows, it might be fat32, might be exfat.
Spike15 said:
The problem is that it's just heuristic restrictions on the usage of the operating system.
Why would you limit the size of the space an application can use? Is the underlying OS FAT32 and Microsoft is worried that stupid app developers will store everything as one monolithic file and therefore break their app when the store reaches 2GB?
It doesn't make sense, and restrictions that don't make sense -- regardless of what they are -- are a problem.
Click to expand...
Click to collapse
This is limited by Silvelight...
but i don't think this is a big problem,this limitation can easy change by update
This isn't really accurate. They haven't fully decided on a max space. WP7 uses exFAT and isn't limited to a single file size. I believe this can be configured per app and developers will be able to request more than 2GB if their app needs it for whatever reason. 2GB is just the 'default' and isn't even enforced in the CTP. http://msdn.microsoft.com/en-us/library/ff402541(v=VS.92).aspx
My bigger problem with this isolated storage is that for no reason at all other than bad engineering it's incredibly slow. sviluppomobile.blogspot.com/2010/04/wp7-isolatedstorage-speed.html about 127x slower.
When I posted about this on the msdn forum, some MVP just basically told me to "use a webservice" and if i don't than this is not the platform for me.
I had issues with that when i was making some silverlight apps some time ago. But i figured them out. What microsoft is doing here with windows phone 7 is that they are using the phone to marry apps with their cloud counterparts. Apps like netflix ap mobile nytimes will use if at most 10 mb of local storage on the device. anyone that need more than 512 mb of local storage for their app, is doing something really wrong. in regards to speed of the local storage i have realised that each local storage created is essential a true isolated storage area. meaning its essentially a small partiton formatted in some format (might be fat) and all the process of reading from that and storing to it really gets some painful io problems. But it seems with windows phone 7 the unified storage engine seems to fix that. Essential from my views of the way my programs are working. when an app is launched. all other apps are essentialy frozen in their last state, so only essential apps and stacks are running. during this process the local storage is put into ram and the application access the program at close to the native speed of the ram. when a user hits the back button it essential takes the local storage and saves back to the slower storage medium and saves the state of the application..
hope this makes sense.
What do you plan on installing on your WP7? World of Warcraft?
Imho, you don't need more than 2 gigs per app, hell, even my Tomtom with all Europe installed on it fits on my 2 gigs microSD card.
Remember, it's a freaking phone!
Related
OK, I got my Sprint TP2 yesterday and was playing around with it. I installed my SD card that had some files on it and when I tapped on one document file by mistake it "unzipped" it to the internal storage completely filling it.
I've looked all over but cannot seem to locate the internal storage memeory on the phone.
HELP!
Thanks in Advance.
OK, never mind. But.....
OK, after I opened it back up today I started looking at it like my old PDA and found the file and deleted it.
But..
I'd like to free up more internal memory as it shows I only have 158MB free. And only 59MB free for program memory. I'll be getting a 16GB card soon to replace my 2GB I have but I'd like to have more internal memory.
What programs/files can I delete safely from my Sprint TP2 to free up more space?
JohnMcD348 said:
I'd like to free up more internal memory as it shows I only have 158MB free. And only 59MB free for program memory. I'll be getting a 16GB card soon to replace my 2GB I have but I'd like to have more internal memory.
What programs/files can I delete safely from my Sprint TP2 to free up more space?
Click to expand...
Click to collapse
158MB of "Storage" memory is actually quite a bit -- it's 60% open/empty. Considering that a lot of applications are less than a 1 MB, and a huge one is 5MB -- you still have room to install dozens directly to the device. To minimize use of Storage, install as many apps as possible to your card. And, wherever possible, configure settings on apps to store their data to the card...and set the camera to save to the card, etc. Even a 2GB card is a lot of space -- unless you're carrying full-length, high-quality movies.
Program memory gets filled up by stuff that's currently running, so deleting installed programs won't free up more of that -- unless these programs run automatically/all-the-time.
MCbrian said:
158MB of "Storage" memory is actually quite a bit -- it's 60% open/empty. Considering that a lot of applications are less than a 1 MB, and a huge one is 5MB -- you still have room to install dozens directly to the device. To minimize use of Storage, install as many apps as possible to your card. And, wherever possible, configure settings on apps to store their data to the card...and set the camera to save to the card, etc. Even a 2GB card is a lot of space -- unless you're carrying full-length, high-quality movies.
Program memory gets filled up by stuff that's currently running, so deleting installed programs won't free up more of that -- unless these programs run automatically/all-the-time.
Click to expand...
Click to collapse
Yeah, if you have 158MB storage free on the phone right now, be sure to take a screenshot if it so you can look back later and remember "back when" you had still had that much free space
MCBrian is right, moving stuff to your memory card is the best way to free up space on the phone's memory and keep it from filling up unneccesarily. Like he said, first change the camera settings to always save to the card, otherwise that will always eat into your available on-board storage, and quickly. I would also suggest going into the current album of pics on the phone, deleting anything you don't want to save, and move whatever you do want to save into a "pics" folder on your card (HTC's photo album can include pics saved there as well). Same for music...store any and all of it on the card, not the phone's memory. The one caveat with that is that the HTC music player (the music tab in touchflo) doesn't always find music on the card, not for me anyway, but I never liked that player anyway.
Managing my memory that way has given me enough space that even with dozens of programs on the phone, all of them installed to the phone's memory, I still have 95MB free space for programs on there. In fact, I still have a fair amount of junk (stuff I tried but don't use, etc) in there that I need to go clear out. Installing some of your programs to the memory card can help too, but if you're careful you can keep enough storage memory on there available to be able to avoid ever needing to do that (and the hassle that comes with trying to figure out which programs are ok with being installed on the card, as well as managing/maintaining separate install locations).
If you're going to start using file explorer to dig around in your directories, I highly recommend you first install File Explorer Extension. It simply adds a lot of the stock destop file explorer functionality that's missing in the mobile version ("open with>" in the context menu, for example!)...makes a HUGE difference in ease of use when digging through your file structure. I attachted it below, "fexploreext v2.05.CAB"
For keeping your RAM ("running" memory) from growing too fast, I also suggest running the other 2 cabs I have attached below (SSK TP2 Dynamic Resource Proxy.cab and nopushinternet.cab), they make a big difference in the active memory management on the TP2, you'll probably see a noticable difference right after soft-reset.
Thanks for those CABs. I'm pretty good at managing the storage on things like this, I just couldn' find the files/folder on the newer phone using the options available in WinMo6+. I've been using an Axim for years runnign WinMo5 and earlier versions. Storage cards are pretty easy for me as I'm use to running stuff between the Main/CF/SD cards that I had on the Axim. I just have alot to learn about the newer 6.1 OS. Probably, by the time I get used to 6.1, Sprint will come out with 6.5(6,7,whatever) and I'll get to relearn everything all over again.
If there are any other programs you'd recommend to help me out I'd greatly appreciate it.
JohnMcD348 said:
Thanks for those CABs. I'm pretty good at managing the storage on things like this, I just couldn' find the files/folder on the newer phone using the options available in WinMo6+. I've been using an Axim for years runnign WinMo5 and earlier versions. Storage cards are pretty easy for me as I'm use to running stuff between the Main/CF/SD cards that I had on the Axim. I just have alot to learn about the newer 6.1 OS. Probably, by the time I get used to 6.1, Sprint will come out with 6.5(6,7,whatever) and I'll get to relearn everything all over again.
If there are any other programs you'd recommend to help me out I'd greatly appreciate it.
Click to expand...
Click to collapse
Well the file structure is obviously still pretty much the same windows-standard, just some locations moved around. The bad news is that none of the programs installed by default in the stock rom are removable through the normal remove programs dialog, or any 3rd-party app I've seen. However you can just go perform the same steps manually by deleting any folders matching the program/publisher's name in these locations:
<root>/program files
<root>/application data
<root>/windows/start menu
...and then searching in the registry to delete any keys in there for the program as well. You'll need a registry editor to do that, I've attached my favorite free one, PHM Regedit...just search your registry by the name of the program you're removing. If you're not familiar with messing around in the registry, there's guides available here, let me know if you need me to point you in that direction. And, as always, be SURE to make a backup copy of your registry (PHM can handle that for you) before making any changes.
Here's a couple of other utilites I've found useful:
Advanced_Configuration_Tool_v3.3.cab -Gives you acccess to all sorts of advanced UI and system configuration options, a favorite and often-referenced tool here at xda.
Extra Camera Modes.cab -unlocks some capture modes that the TP2 camera is capable of, but aren't enabled from the factory on US models. New modes include MMS video, Burst, Sport, and geotagged images
SDK certs.cab -windows authentification certifcates necessary for installing many hacks/apps/cabs/etc that are available here
DivXPlayer_PPC.cab -a lean, mean .avi player from the people who came up with DivX (the codec standard, not the movie rental crap lol). I rip my DVD's at home to ~700MB DivX files, save them on my memory card, and use this app to play them...it gives far better performance and quality than any of the other players I've tried.
Very Much appreciated.
Now, I seem to have another probelm and I don't know if it's my unfamiliarirty with the newer Sync Center or am I just doing something wrong, or if it's an issue with the programs I've got.
I'm new to both Win7 and WinMo6+(and touch flo, etc). Up to now I had XP(w/ ActiveSync) and my WinMo5 Axim.
I can't seem to get my programs installed onto my TP2. I use a prgram for work called Tarascon. It's a medical reference program. I tried to install it yesterday and I never got the repsonse on the TP2 to request permission to install it. Today, I tried to install SOTI's Pocket Controller and this time I did get the request and I installed it to the device but I can't find it anywhere on it. It didn't install an Icon on the device and I've looked through every place I could think and can't even find an installation file for it. I didn't get an install error or failure notice and my memory size dcreased 2MB so something happened.
Glad to help
Since I don't really know anything about the medical reference software you're using, my first suggestion would be to check with the publisher and make sure that the version you have is compatible with Win7 and WM6.x...often software that worked on WM5 won't work just right on 6.
As for SOTI Pocket Controller, the latest version available on the site should be compatible with your setup. When you install it, are you doing that by running a .exe file on your PC and then letting Mobile Device Center (the new generation of ActiveSync) handle the install from there? It might be advisable to just moving the .cab file for the program straight to your phone (device memory or storage card is fine), and run it from there to install...bypasses the MDC, and ends up doing the same thing in the long run. In fact, it might be worth trying the same thing (running the .cab straight from your phone) with the medial software you've got.
It might just be that I'm using Ver4 and it doesn't want to run right with the newer install setup(MDC).
It worked fine when I installed it on my Axim(WinMo5) and using WinXP(ActiveSync).
Another odd thing, every time I plug in my TP2 and MDC starts to Sync, I get the request from Win7 for the Tarascon program to initialize. So that tells me something, somewhere set a pointer to my TP2 to update the program. I think.
So, with WP7, we lose all support for the .cab and associated API as it exists now. Replacing it is the .xab format.
What's a .xap?
A .xap is a simple, every day .zip file, renamed to .xap. Inside, it contains the app and all relevant dependencies. There are a number of possible .xml files that could be included inside the .xap to determine things like required security access level, to tell the system which .dll contains the main() for the application, etc.
I believe the .zip also provides a container for the virtual filesystem available to the app (not sure on that, it may be stored in a separate container, have to analyze more)
At least initially, .xaps will only be available for deployment through the Marketplace.
Regarding preloaded applications by OEM/MO: Requirements are much more strict in this regard now due to frequent end-user complaints about "slow, laggy, etc" Stock ROMs. I know every one of you reading this knows what I mean Preloaded App Requirements (which will be distributed as .xap) as follows:
Maximum of 6 preloaded applications on the device, not to exceed 60MB
All preloaded apps must pass Marketplace submission process (some extended APIs are available to OEM/MO so the process is slightly relaxed in that regard)
The application(s) and all future updates must be free of charge.
The apps must launch without dependency on network availability.
The apps must persist through a "hard reset".
The apps must be updatable and revocable (!!!!) through the Marketplace.
The apps must notify the user at first launch of any capabilities to be utilized and get user consent (to access compass, accelerometer, network, etc.)
I've attached a .xap to this post for your examination. It's renamed to .zip for the attachment system to allow it.
Hehe.. this reminds of the "widgets" for Vista and 7 or the "apk"s for Android. Same stuff it sounds like Thanks for the info master Da_G
Does this mean .cab.pkgs are being changed too?
The .cab.pkg format remains intact for imageupdate (actually I haven't examined it in depth just yet, but all indications are that they have not changed .cab.pkg format)
Bump for visibility
Interesting...Wonder if there will be a process to convert some cabs to xabs.
Highly unlikely. xab's are silverlight applications meaning you have to use xaml , c# code and libabries all in one small zipped file. Cab's are Cabinent files that has an inf file that specifes what libabries and files are going to be enclosed in the file. To put it simply a xab is a standalone application that does not require extraction or installation to run and a cab is an application which requires an extraction and for its contents to be placed in specific areas in order for the dependents to find and use them.
Also to clarify. Local storage for xab's are not defined or stored in the xab file. they are defined by the silverlight runtimes which is handled by the os. As of now since there is little information as to how the windows phone internal structure is (apart from us knowing that windows phone will utilised microsoft unified storage.). on windows 7 and windws vista after u install the silverliht runtimes all xab's that request local storage is stored in <SYSTEMDRIVE>\Users\<user>\AppData\LocalLow\Microsoft\Silverlight\is .. Just note silverlight local storage works just like flash local storage. the only exception so far for windows phone is that u will not be able to access a lot of local directories just predefined stuff like music, pictures and documents.
Just before people get into bad habits; they are xap, not xab files. No relationship to cabs whatsoever save as a container format.
Da_G said:
Regarding preloaded applications by OEM/MO: Requirements are much more strict in this regard now due to frequent end-user complaints about "slow, laggy, etc" Stock ROMs. I know every one of you reading this knows what I mean Preloaded App Requirements (which will be distributed as .xap) as follows:
[*]Maximum of 6 preloaded applications on the device, not to exceed 60MB
Click to expand...
Click to collapse
That is just brain damaged. Pre-loaded apps add clutter, but they also cut down on cost. Choose your poison. Pre-loading has little to do with with speed penalties, when done properly. Frankly, if roms have the same ancient architecture under WM7, then Microsoft really needs some technical leadership replaced.
[*]All preloaded apps must pass Marketplace submission process (some extended APIs are available to OEM/MO so the process is slightly relaxed in that regard)
Click to expand...
Click to collapse
Now this is where some quality review comes in. It all depends on how good the standards are, and I dare say they will seem lower and lower as time passes. Hell, they're already admitting that OEMs will have relaxed standards.
[*]The application(s) and all future updates must be free of charge.
Click to expand...
Click to collapse
That's just silly. You'll get a bunch of lite software versions with next to zero shelf life instead of upgradable versions with marginal shelf life.
[*]The apps must launch without dependency on network availability.
Click to expand...
Click to collapse
what does this even mean? Does that mean no internet based app can be installed? All it really means is you have to quit gracefully if the network isn't available.
[*]The apps must persist through a "hard reset".
Click to expand...
Click to collapse
This is a good thing, but primarily a reflection of back when flash memory was in short supply. Haven't run into it in forever.
[*]The apps must be updatable and revocable (!!!!) through the Marketplace.
Click to expand...
Click to collapse
Well, updateable is good...but revocable? Maybe removable would be more consumer friendly. Makes me think of the PS3.
[*]The apps must notify the user at first launch of any capabilities to be utilized and get user consent (to access compass, accelerometer, network, etc.)
Click to expand...
Click to collapse
What I take from all of this is that
a) they want to drive more traffic through the marketplace.
b) they want to drive more traffic through Windows Certification
Good for the average consumer, great for Microsoft. Personally, the only point that has any value to me at all is a central marketplace. The rest of the bullets are ways for Microsoft to drive seperation between their brand name and many software vendor's crappy products.
ahhhha , sound interesting .
gguruusa said:
That is just brain damaged. Pre-loaded apps add clutter, but they also cut down on cost. Choose your poison. Pre-loading has little to do with with speed penalties, when done properly. Frankly, if roms have the same ancient architecture under WM7, then Microsoft really needs some technical leadership replaced.
Click to expand...
Click to collapse
I don't know, I wish MS enforced that same restriction on the Desktops OSes too. Nothing worse than getting a Dell or Sony PC full of preloaded gunk.
gguruusa said:
That's just silly. You'll get a bunch of lite software versions with next to zero shelf life instead of upgradable versions with marginal shelf life.
Click to expand...
Click to collapse
It's a big leap to come to that conclusion seeing as most software that ships with phone doesn't have additional charges. The restriction as I read it really means you just won't get a tonne of unwanted trial-ware on you shiny new phone.
Eoinoc said:
I don't know, I wish MS enforced that same restriction on the Desktops OSes too. Nothing worse than getting a Dell or Sony PC full of preloaded gunk.
Click to expand...
Click to collapse
maybe, but that same preloaded gunk cut the price of your dell and sony. While I don't like preloaded gunk, I don't like expense either. What I do like is being able to make the decision myself of how much gunk vs expense I am willing to tolerate.
It's a big leap to come to that conclusion seeing as most software that ships with phone doesn't have additional charges. The restriction as I read it really means you just won't get a tonne of unwanted trial-ware on you shiny new phone.
Click to expand...
Click to collapse
I agree it is target at no trial-ware. Any idea how people in the business world get around that? Lite versions of software (aka cripple-ware). Pay per use software. I'm sure there are other strategies. Frankly, if they enforce the ability to remove, I'm not that particular on how much gets pre-loaded. The fact of the matter is that the problem isn't how much crap comes with your phone; it is that you don't get to pick whether it is installed.
great find Da_G, so its XAB no more cabs
the0ne said:
great find Da_G, so its XAB no more cabs
Click to expand...
Click to collapse
XaB no.
XaP
tighoor said:
XaB no.
XaP
Click to expand...
Click to collapse
oops ..
How bad this is for the guys that dev here?
or... how good?
guessing .xap is short for XNA Application Package ?
vladimir2989 said:
guessing .xap is short for XNA Application Package ?
Click to expand...
Click to collapse
close, but no. In fact, it's actually a silverlight application package - it's been used for web stuff since silverlight released.
how to convert XAP to OEM/EXT package ?
I'm not sure what you mean by "OEM/EXT" package, but it's probably not possible. If you want to include an app with the phone, that *is* possible but the only way I know of is to include the XAPs in the ROM and then install them on first bootup. Probably not the best approach.
Similar to the CE5 kernel that we're used to, the CE7 kernel is a 32 bit OS and runs a 4GB Virtual Address space. Similar to CE5, 2GB is reserved for the kernel and 2GB is reserved for user space.
This is where it begins to differ. CE5 handled the user space by splitting the process memory up into 32 slots of 32MB each. (This accounts for 1GB of user space, the rest is used for memory mapped files, fixed up modules, etc.) Any app currently in the foreground was swapped into slot 0 during execution, and swapped back into it's slot while it's backgrounded.
CE7 similarly uses 1GB for the process code, however now it's handled differently. Each running process is mapped to the entire 1GB space, allowing the full 1GB of VM available for use without the trickery needed to accomplish using more than 32MB of VM in CE5. This should allow for much more rich apps to be developed (whenever MSFT decides to allow us to write native code, which is coming at some point...)
This 1GB VM space will be dedicated to the process, and not accessible by any other process. The remaining 1GB of user space has to be utilized for inter-process memory sharing.
There are 256 priority levels as with CE5, for each individual thread within an app. Scheduling is handled on a round-robin basis for threads sharing the same priority level. Priority level 0 functions as a "real time" priority level and any thread running at this level will run through til completion before the scheduler runs another thread. True multitasking will not be accessible to programmers initially, though MSFT intends to unlock that later down the line (presumably around the time native code is allowed). There is no hard limit to the number of threads a program can utilize, it is only limited by the system resources available.
Regarding the limited APIs available to us "normal" programmers - OEMs and MOs will have access to an extended set of Managed APIs and a limited set of Native APIs that "normal" programmers won't get access to. This likely includes things like RIL.
Just give me an ARM build of it that is already ported over to run MSM7x00.
Thank you
Bump for visibility
good bump message too short grrr
Da_G said:
Similar to the CE5 kernel that we're used to, the CE7 kernel is a 32 bit OS and runs a 4GB Virtual Address space. Similar to CE5, 2GB is reserved for the kernel and 2GB is reserved for user space.
Click to expand...
Click to collapse
Are you sure it's CE7 and not CE6? Tweakers.net (which appears to have received the same docs you have) says it's 6 and 6 makes much more sense to me being that CE7 hasn't RTM'd yet.
Yes, i'm sure it's CE7. The docs do in fact say CE6 but the docs are dated, things move fast, and that's no longer the case
CE7 "Chelan" will likely RTM around the same time WP7 does.
Interesting. That's a lot of risk for the WP7 team to take on.
Windows 7, Windows Phone 7, so CE must be 7
What do u mean by "much more rich apps". 3D Games or what? I think that aplications on WM 6.5.5 are good and fast. Can u explain that rich applications?
where do you get this info from.. it does sound interesting
Keep it coming
CE7 supports directx 9 acceleration. XNA & SL 4. Do they sound any familiar?
Awesome information! Thanks and keep it coming; I can't wait for WP7 to be released!
Da_G said:
This should allow for much more rich apps to be developed (whenever MSFT decides to allow us to write native code, which is coming at some point...)
[...]
(presumably around the time native code is allowed).
Click to expand...
Click to collapse
what makes you think that microsoft is going to allow developpers to write native code on windows phone 7?
the whole wp7 sandbox architecture is based on .net, so it's hard to imagine that microsoft would allow native code...
aren't they going to allow it only on windows phone 7 "business edition", which much users won't have ? that would make sense...
if they do that then we are in luck the guys on here will eventually pull it apart and give it to us all, i serously doubt thats going to happen tho, i suspect 6.5 code base will continue side by side until devs support WP7 at which point there wont be such a big outcry.
FWIW I was told by members of the WP7 team that it's CE6. They weren't directly related with that aspect and weren't 100% certain (more like 99%) though.
RustyGrom said:
FWIW I was told by members of the WP7 team that it's CE6. They weren't directly related with that aspect and weren't 100% certain (more like 99%) though.
Click to expand...
Click to collapse
A MS spokesman has confirmed it is running on a hybrid CE6 R3 (meaning CE6 R3 + added features that are from CE7). No doubt in my mind that a update in a year or so after launch they will update it to the full CE7.
According to the OS Version that the device returns, its running CE 7. Check around the 6 minute mark here: http://live.visitmix.com/MIX10/Sessions/CL16
Sangheili said:
According to the OS Version that the device returns, its running CE 7. Check around the 6 minute mark here: http://live.visitmix.com/MIX10/Sessions/CL16
Click to expand...
Click to collapse
It says 7 as in Windows Phone 7.
While this is quite interesting, I have a couple of questions about this. First, since each process is now free to use the entire slice of memory assigned to userspace, does this mean that it now conducts multitasking similar to iPhoneOS and Android where it saves the application's state when backgrounded instead of the entire process itself? How does the OS handle background activities, such as background network transfers and job completions?
This leads me to my second question. Since memory allocation is done on a round-robin basis, does this mean that all backgorund activity (if backgrounded) must be completed within a certain amount of time? (For those unfamiliar with OS concepts, round-robin scheduling is a method some OSes employ where it gives a pool of jobs a set amount of time, a quantum, to complete their work. If some job in the pool doesn't finish by the end of that quantum and another job needs resources, that job is killed off in favor of the new one. More information here.) Or is the activity suspended until whatever process needs the memory is finished using it?
Thanks for the scrutinous research!
If you're referring to 3rd party apps, there is no multitasking for 3rd party apps. Depending on what the user does, the app will be "tombstoned" (application state saved).
RustyGrom said:
It says 7 as in Windows Phone 7.
Click to expand...
Click to collapse
Why would it say "Windows CE" and then append a version number that doesn't apply?
Anyway, even if it runs a WinCE 6 hybrid kernel, I hope there's SMP support there. I'd like to see a Tegra based phone. Such a device however would be a terrible waste of CPU power, if the system can't use both cores.
Yesterday I stumbled across a curious error. Zune told me that I had reached the maximum allowed amount of media on my HD7. It's not that my SD card was full or so, there's still 15 GB left on it. I had about 3 GB of music, 2 GB of videos, 400 MB of podcasts and 5 GB of pictures on it. I removed the media and am currently synchronizing again, since I can't believe that WP7 limits the amount of media in any way. Did anybody else ever experience such an error?
Just in case somebody else may face the same situation as I did:
there doesn't seem to be a limit for the total amount of media on a device. The issue I had was caused by a folder containing about 12000 pictures. Apparently WP7 can't handle or doesn't allow that many pictures in one single folder. I solved it by making several child folders containing 3000 images each.
dkp1977 said:
Just in case somebody else may face the same situation as I did:
there doesn't seem to be a limit for the total amount of media on a device. The issue I had was caused by a folder containing about 12000 pictures. Apparently WP7 can't handle or doesn't allow that many pictures in one single folder. I solved it by making several child folders containing 3000 images each.
Click to expand...
Click to collapse
Hello old friend ...
I see you find the solution ...12.000 files in one folder ??? wowwww.
Thanks for the tip anyway
colossus_r said:
Hello old friend ...
I see you find the solution ...12.000 files in one folder ??? wowwww.
Thanks for the tip anyway
Click to expand...
Click to collapse
Hi mate
Well, seems I was wrong. There really appears to be a limit to how many images you may have stored on the device. Even though I splitted the folders, it synchronized only 1300 images back to the phone. So around 10700 pictures remained unsynced. I'll try and contact winphonesupport via twitter. Maybe there's some workaround. I have tons of images of my family I use to carry around on my device. And I want to keep it that way.
I had a nice chat with the WinPhoneSupport on Twitter. It appears that Zune uses a database on each device which is quite limited concerning the amount of media it can handle. That means that - totally independent from the storage space left - it's possible that you just cannot sync anymore files if you have a huge amount of pictures on your device. I can't exactly tell what that limit is, but I had the error at about 35000 files. The support told me they'll escalate my report to the team, whatever that may mean. Let's hope they simply increase that limit.
dkp1977 said:
I had a nice chat with the WinPhoneSupport on Twitter. It appears that Zune uses a database on each device which is quite limited concerning the amount of media it can handle. That means that - totally independent from the storage space left - it's possible that you just cannot sync anymore files if you have a huge amount of pictures on your device. I can't exactly tell what that limit is, but I had the error at about 35000 files. The support told me they'll escalate my report to the team, whatever that may mean. Let's hope they simply increase that limit.
Click to expand...
Click to collapse
yes!! please get back to us with what transpires! what device are u using?
professorwol said:
yes!! please get back to us with what transpires! what device are u using?
Click to expand...
Click to collapse
I use a HTC HD7.
Btw, here is the error code: C1010032 (8004A211)
dkp1977 said:
Hi mate
Well, seems I was wrong. There really appears to be a limit to how many images you may have stored on the device. Even though I splitted the folders, it synchronized only 1300 images back to the phone. So around 10700 pictures remained unsynced. I'll try and contact winphonesupport via twitter. Maybe there's some workaround. I have tons of images of my family I use to carry around on my device. And I want to keep it that way.
Click to expand...
Click to collapse
Put your images on skydrive. Smartphones aren't media PCs, and I simply cannot even fathom a reason why anyone would want that many on a phone nevermind waste support's time dealing with a non-issue...
N8ter said:
Put your images on skydrive. Smartphones aren't media PCs, and I simply cannot even fathom a reason why anyone would want that many on a phone nevermind waste support's time dealing with a non-issue...
Click to expand...
Click to collapse
First of all it's my decision whether I want to carry my pictures with me on my device or put them somewhere on the net. Secondly having all those images stored on a server would require a fast internet connection if you want to quickly browse through the (sorted) images if you're looking for something specific. Sadly you don't always have such a fast connection. Third and last: I consider it an issue when the amount of media - whatever kind it may be - is limited by a database with a too low capacity rather than the storage.
N8ter said:
Put your images on skydrive. Smartphones aren't media PCs, and I simply cannot even fathom a reason why anyone would want that many on a phone nevermind waste support's time dealing with a non-issue...
Click to expand...
Click to collapse
If he has enough space on the phone then why not keep the pics there? skydrive is not always accessible and could end up costing you if you don't have an unlimited data plan...
Just found a huge and very annoying bug in WP7 BackgroundTransferService (it's a task for background file transfers, downloads or uploads).
If you create and add BackgroundTransferRequest, but cancel and dispose it shortly, during download process (i.e. download not finished yet), or even uninstall application (sic!), the OS does NOT release the reserved space (equal of the total file size, doesn't really matter how much data you've already downloaded!) The only way to avoid that problem is to wait until transfer completion. But if your app will be uninstalled during non-completed transfer, you're (i.e. user) out of luck
I did some investigation with interop-unlocked phone. Actual files are stored in \My Documents\Zune\PimentoCache\Lib\<numberic subfolders>; on interop-unlocked phone you may easily delete unwanted "space eaters" (in my case, files are .mp4 video files with real huge sizes, from 250 to 800 MB) but on regular dev-unlocked device you have no choice than do a hard reset - as I supposed to do with my Lumia 900
So, my note to WP7 developers: use these "BuggyTransferService" with care, you can easy damage the user's phone. I believe that bug is the main source of some rare complains about "I've magically lost phone storage free space". And shame on Microsoft to ruin the perfect "sandbox" concept by buggy and untested API!
P.S. As for me (personally) the most annoying thing is: because of "super-duper-STUPID" protection, I can't cleanup my Lumia 900 (and MS didn't provide any tool for that!) and should (damn!) do a hard reset, and reinstall whole stuff For the first time I start thinking, I've chosen a wrong platform to live and work with...
sensboston said:
Just found a huge and very annoying bug in WP7 BackgroundTransferService (it's a task for background file transfers, downloads or uploads).
If you create and add BackgroundTransferRequest, but cancel and dispose it shortly, during download process (i.e. download not finished yet), or even uninstall application (sic!), the OS does NOT release the reserved space (equal of the total file size, doesn't really matter how much data you've already downloaded!) The only way to avoid that problem is to wait until transfer completion. But if your app will be uninstalled during non-completed transfer, you're (i.e. user) out of luck
I did some investigation with interop-unlocked phone. Actual files are stored in \My Documents\Zune\PimentoCache\Lib\<numberic subfolders>; on interop-unlocked phone you may easily delete unwanted "space eaters" (in my case, files are .mp4 video files with real huge sizes, from 250 to 800 MB) but on regular dev-unlocked device you have no choice than do a hard reset - as I supposed to do with my Lumia 900
So, my note to WP7 developers: use these "BuggyTransferService" with care, you can easy damage the user's phone. I believe that bug is the main source of some rare complains about "I've magically lost phone storage free space". And shame on Microsoft to ruin the perfect "sandbox" concept by buggy and untested API!
P.S. As for me (personally) the most annoying thing is: because of "super-duper-STUPID" protection, I can't cleanup my Lumia 900 (and MS didn't provide any tool for that!) and should (damn!) do a hard reset, and reinstall whole stuff For the first time I start thinking, I've chosen a wrong platform to live and work with...
Click to expand...
Click to collapse
Hmm what about subsequent reboots? I know that I've done what you've just stated above multiple times in testing BGTransferService, yet I see no files within those multiple folders. Maybe syncing the phone helps clear the cache? I don't know.
Reboot doesn't help. If you saw many empty folders, it means your transfers successfully completed and downloaded files are in your app's isf (it's a normal situation).
Try to:
- start a few transfers (AFAIR limit is 2 simultaneous transfers)
- remove and dispose transfers
Code:
BackgroundTransferService.Remove(transferToRemove);
transferToRemove.Dispose();
or just uninstall app.
You'll see "lost" files in these folders. Try to download huge files (like in my case - video recordings) to be sure they will not complete soon.
sensboston said:
Reboot doesn't help. If you saw many empty folders, it means your transfers successfully completed and downloaded files are in your app's isf (it's a normal situation).
Try to:
- start a few transfers (AFAIR limit is 2 simultaneous transfers)
- remove and dispose transfers
Code:
BackgroundTransferService.Remove(transferToRemove);
transferToRemove.Dispose();
or just uninstall app.
You'll see "lost" files in these folders. Try to download huge files (like in my case - video recordings) to be sure they will not complete soon.
Click to expand...
Click to collapse
Oh so basically you have that switch enabled that allows you to download over 10 MB (or whatever that limit is). That may be the issue then with that switch and the API.
Of course I do (transferRequest.TransferPreferences = TransferPreferences.None; ) but it's a default value. Actually Background Transfers API is very useful for the large files: you shouldn't care about power loss/battery drain/connectivity loss - the whole idea is a brilliant (and I like it). But implementation is kinda buggy And MS-side support is awful. The official from MS just confirmed what "bug is well known and will be fixed" but that's all - I did a damn hard reset and spent lot of time to reinstall stuff (also lost my game progress/sms/etc. and so on 'cause MS+NOKIA are really care not for bugs but for "protection") At least they may send me a provisioning file packed in .cab, to clean-up the mess. But... seems it sounds like a "project" for MS