Related
I'm opening a new thread so people don't have to dig thru other threads to find this.
Leaked documents show that Windows Phone 7 will indeed have multitasking after approval by Microsoft. Appearently you will need to ask Microsoft for special permission, and as such you will need to prove your need for multitasking. I'm sure it will be limited to apps such as Pandora that show a specific need for running in the background.
http://www.wmexperts.com/leak-windows-phone-7-documents-developers
Thanks for posting this. It looks like I need to start learning silverlight which I expected would be the case.
The multitasking is annoying. I dont want to have to ask for permission to enable this. Do they plan on controlling this through the app store? If its just some hidden API's they would get leaked in minutes and everyone could use them.
Weird interpretation
From the leaked documents provided, I cannot figure out how did they come to the conclusion that developers would need to ask for permission to do multitasking. It seems that the authors of the article are not really technical and had things mixed up. OEMs and MOs will have to request access to some native APIs if Managed API and provided limited native API set is not enough for their needs, which is something totally different from processes and threads. Processes and threads, or in layman terms multitasking is business as usual. I don't see any restrictions there.
Of course the OS can multitask. That's never been a question.
The question is whether third party applications will be allowed to run in the background.
There is no word on whether this is the case, and in fact, every official statement from Microsoft currently hints to this not being the case. It seems like they're going the Apple way of not allowing third party applications to run in the background.
Did anybody read the document? There's no connection between multitasking and approval. It's not going to be done with hidden APIs that can get leaked. It's not completely clear but here's what it seems to say to me:
Anyone can write C#/Silverlight apps that use the .NET Compact Framework and install them. Hopefully this will let you do most things you want to do. The big problem would be if .NET CF 4 is missing any of the "normal" useful stuff. Personally, if I can interact with calls, texts, contacts, location services (e.g. GPS) and the internet then I'm happy.
If you want to write unmanaged (i.e. C++) code or call some extra managed APIs you'll need to get the code signed. This will probably go through a similar process to Apple's app store. This should only be required for low level stuff - drivers, etc. The wording of the doc suggests that it would only be phone carriers that are likely to be using this.
Multitasking isn't mentioned, so it's only guesswork between now and MIX10.
freyberry said:
Of course the OS can multitask. That's never been a question.
The question is whether third party applications will be allowed to run in the background.
There is no word on whether this is the case, and in fact, every official statement from Microsoft currently hints to this not being the case. It seems like they're going the Apple way of not allowing third party applications to run in the background.
Click to expand...
Click to collapse
I think it may work more like the way Android does than the way iPhone does. Android multitasks properly, but suspends non-foreground processes. Looking at the built in calendar demo, it pops in and pops out to the same place, so it's not being restarted, merely resumed.
l3v5y said:
I think it may work more like the way Android does than the way iPhone does. Android multitasks properly, but suspends non-foreground processes. Looking at the built in calendar demo, it pops in and pops out to the same place, so it's not being restarted, merely resumed.
Click to expand...
Click to collapse
That's not how multitasking on Android works. Android applications save their state when they are sent to the background, but they continue to run. They are not suspended, unless the system runs out of RAM.
If the system runs out of RAM, then the "oldest" process that's running in the background gets killed. Since it saved its state when it was sent to the background, you can reopen it and continue where you left off.
That's exactly how multitasking *should* work.
freyberry said:
That's exactly how multitasking *should* work.
Click to expand...
Click to collapse
Really? Isn't it the same as stated by MS that apps will be "paused" in background? Also, how is it going to help my satnav app be at the right position when I minimize the dialer in a call?
vangrieg said:
Really? Isn't it the same as stated by MS that apps will be "paused" in background? Also, how is it going to help my satnav app be at the right position when I minimize the dialer in a call?
Click to expand...
Click to collapse
No, it is not at all the same. Read my post again.
guys take a look at this.. this guy is playing music while navigating trough the phone..
http://www.wmexperts.com/wme-mwc-video-hands-no-2-windows-phone-7-series?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+wmexperts+(WMExperts)&utm_content=Twitter
may i ask for this thread to list facts only?
i would love this thread not to be dragged into the debate of hints and speculations. I would say, as long as we don't have something solid let's keep the speculations at the other thread.
i have seen some videos where by mistake shows multi tasking cappabilites, and i believe as long as the cappability is there (even if locked down) we can find a way around it. but we are still in the dark, maybe Microsoft will simply say that hey developers, yes we have full multitasking but not for .net cf apps, only unmanaged code can? maybe! just to ensure that not anyone can write an app to stay in the background.
Mostly the usage of multitasking is not that high, i don't keep much apps in memory. infact alot of the users of Windows Mobile (5, 6.x.x) do set their phones to close the app on X click. and most of us (including me) didn't want to run multiple apps in the background, actually that's why HTC built the Taskmanager into their ROMS. even SonyEricsson.
Of course there are exceptions for that, i would love for my Navigation app to stay in the background while my friend is playing on the phone.
the main point is we don't have any clue yet, if we get any info that is official/confirmed leak then we can get either UPSET or releafed
take it easy mates.
young blade said:
guys take a look at this.. this guy is playing music while navigating trough the phone.
Click to expand...
Click to collapse
Music (Zune) is not a 3rd party app.
pilgrim011 said:
Music (Zune) is not a 3rd party app.
Click to expand...
Click to collapse
okay so its about 3th party apps in running in the background.
I'm sure it will be possible.. whats the point of not doing it and having 500+ ram in the device..
thats like tuning a car up to 999 of horse power and restricting it down to 300.
young blade said:
okay so its about 3th party apps in running in the background.
I'm sure it will be possible.. whats the point of not doing it and having 500+ ram in the device..
thats like tuning a car up to 999 of horse power and restricting it down to 300.
Click to expand...
Click to collapse
Don't be so sure. Unfortunately, Microsoft is heading Apple's path, the dark side...
Honestly if they make is so you have to actually program it to run the background instead of natively making everything work in the background, I beleive that would be a good thing. I have to pull the task manager up to close every app after I open it because I don't really need it in the background. For example when I use a calculator to compute something why does it need to stay up after I'm done with the calculation?
On the otherhand, If they are making it so you have to get direct permission from Microsoft and not just from the OS to run in the background that probably means they want some more money or something outta the deal and I don't think thats the best way to go. Phone these days usually have a good amount of ram to be able to run task in the background and they shouldn't underpower the device if it can handle it.
I don't think that iPhone is the way to the dark side.... they are able to make "dumb users" (I don't think you are dumb, it's a way to put it into), a way to make what they want with their device. As a higher user, you know how to manage properly a system unmanaged because you know to play properly with the system, resources, and more over, but some people just has problems knowing how to open a file...
Really, the iPhone way is bring the IT technologies to people that not usually knows or likes the IT, and use them because they must, or they like the services but not the tech itself.
I belive that maybe WP7S has become so iPhone, and we may want to drop it, but really, the human history has ever been the same. It's not about how good or how many features has a device/technology/thing, it's about how many people use it in daily life. Try to think about a space travel agency, the people will believe in space travels once people become able to go to the moon by themselves, not because the NASA did it. And no matter that NASA was able to take a "car" for the astronauts and an space agency only can bring you an your package, it just doesn't matter.
Yes, it will indeed multitask for the native apps at least. In the presentation, Joe goes to a maps app, then goes right back to the calendar app where he was. Looks like the iPhone push stuff.
Kloc said:
Honestly if they make is so you have to actually program it to run the background instead of natively making everything work in the background, I beleive that would be a good thing.
Click to expand...
Click to collapse
That would be the best thing they could do. That's how it *should* work.
yes, not all apps require to be able to run in the background. things like calculator for example, i hate killing it using task manager.
things like sending sms or email, when I hit the send button and close the gui, the msg should be sent to the background service and really close remove the gui interface from the memory. i hate killing tmail.exe.
and there are a lot more examples why current winmo multitasking is not right. tweaks required just to be able to completely close app like htc album, opera, etc.
i am glad that finally microsoft will address this seriously. i am not surprise that ability to run in the background will be controlled by them. it is still better being controlled rather than not allowed at all (like Apple iPhone?).
freyberry said:
That would be the best thing they could do. That's how it *should* work.
Click to expand...
Click to collapse
Careful, careful....!!
You don't know HOW they're going to adress the issue. If they completely forbid multitasking, like Apple, then things will get a LOT WORSE than they are now.
I agree that not every application has to run in the background. But some MUST run in the background and it would be a huge failure if they didn't allow third party developers to use multitasking at all, like Apple.
Multitasking for each and every application, like on WM6.5, is still a lot better than no multitasking at all!!
Seeing as WP7 will be almost as crippled as the iPhone, let's see ways in which it will be better, besides replaceable battery and memory card(and it's not certain every OEM will follow up on those either). So far it has two weaknesses that only the iPhone has: Lack of multitasking and apps must go through the marketplace.
In order to pick up iPhone users it will have to offer some advantage that the average iPhoner will notice.
Some advantages:
Information at a glance a la today screen with the hubs. iPhone has nothing like this.
It will (supposedly) have some degree of multitasking.
Two more hardware buttons.
Its funny since I've had my HD2 I've not really used multitasking and when I had my iPhone only not being able to use Spotify in the background bugged me so maybe certainly for me multitasking isn't a be all and end all.
Having read lots of stuff about WP7S, the conclusion I have come to is this...
There will be two types of apps
1. Apps with no need to run in the background
2. Apps that do need to run in the background
Examples of type 1 are games, spreadsheets and word processors.
Examples of type 2 are IM apps like palringo, and music streaming services such as pandora.
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive.
That's my take on what's going to happen, and we'll see if I'm right at MIX 2010 next month.
So your answer is - yes it will multitask but only when it is truly needed. Which to me is the best of both worlds. It will ensure a smooth user experience whilst still allowing background operations.
Jim Coleman said:
In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Click to expand...
Click to collapse
Lets hope theyre not too stingy with giving out access to these API's!
The hubs/services (I'm not sure what MS is calling these) system looks good; getting new relative options available on multiple hubs just from installing a single app (like they demo'd with Facebook) should make all the apps work together much better than on an iPhone. I already want to try to make one to generate a music playlist based on past plays, and another to find lyrics to the currently playing song; If I understand the system properly, these would automatically integrate into any 3rd party apps using the appropriate media API's.
Also the context-sensitive search looks to be awesome.
One disadvantage: possible lack of native code execution and probably no OpenGL support - making it harder for iPhone app developers to port their existing apps to Windows Phone.
weesals said:
One disadvantage: possible lack of native code execution and probably no OpenGL support - making it harder for iPhone app developers to port their existing apps to Windows Phone.
Click to expand...
Click to collapse
why the heck should iPhone devs have an easy migration to WP7 if WM 6 devs don't?
weesals said:
Lets hope theyre not too stingy with giving out access to these API's!
Click to expand...
Click to collapse
The impression I'm getting so far is that they will be very stingy indeed. The only people who will ever get access to non-standard API's will be phone manufacturers and networks, and even they usually won't get access to the native API's most of the time. Microsoft will not publish any documentation about native API's. To get access to them the manufacturers will have to apply to Microsoft on a case by case basis. If Microsoft judges that a native API is required (and if there actually is one that might help) then only at that point will they release any information, and a condition of this is that they will vet the resulting piece of software to verify that the native API is being used correctly, and forbid the release of the software if it isn't.
What we don't know yet is where multi-tasking sits within all this. Is it a standard managed API, an extended managed API, or a native API?
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
The only thing I like about iPhone is how I use the virtual keyboard to type text.
I have tested HD2 and iPhone in a store, and from my own perspective, iPhone is more responsive and accurate compared to HD2.
I hope WP7 can be better than those 2 platforms in this task.
giggles33 said:
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
Click to expand...
Click to collapse
gogol said:
The only thing I like about iPhone is how I use the virtual keyboard to type text.
I have tested HD2 and iPhone in a store, and from my own perspective, iPhone is more responsive and accurate compared to HD2.
I hope WP7 can be better than those 2 platforms in this task.
Click to expand...
Click to collapse
that isnt aways based on the OS or software, but the quality of the touch screen.
Jim Coleman said:
Having read lots of stuff about WP7S, the conclusion I have come to is this...
Click to expand...
Click to collapse
This definitely seems like the best thing to do for multitasking in WP7.
We are going to need a task manager though...
As for comparing to the iPhone:
-WP7 will be available in different hardware configurations, giving the consumer a choice in the style and capability of their device.
-Xbox integration, which will most likely include Arcade games (ported for playability of touchscreens)
-Better hardware standards
-Not quite as locked down (hopefully)
RAMMANN said:
why the heck should iPhone devs have an easy migration to WP7 if WM 6 devs don't?
Click to expand...
Click to collapse
Because that's where the money is.
Seems people are struggling to come up with any, maybe something magical will appear in the next few weeks, although I doubt it, the advantages of WM seem like they will be gone with WP7, people on forums like this and blogs have been asking for a windows mobile iphone [without being an iphone] and it looks like they're going to heed the demand.
The most important advantages are gone.
They've made an exact copy and think it is enough. But it's not. When you try to catch up, you have to be better.
There's almost nothing WP7 is better at. It's an exact copy of iPhone OS with a better UI on top, but lacking the thousands of applications. That's not going to be enough and I really can't think about a reason why consumers and developers would be excited about this.
(and don't get me wrong - I LOVE the UI - it's just not enough)
Free Microsoft Office (Document viewing, creation, downloading, and editing)
Abobe Flash Player 10.1 is coming
File downloads (possibly)
Apps like a Wi-Fi router and file manager will likely come and be allowed
XBOX LIVE! Enough said.
Zune integration and support (I'm a Zune user)
1GHz Snapdragon is the processor minimum (This will lead to awesome apps and games)
WVGA display minimum (You might not care too much about this one, but I've seen the difference, and it's AMAZING!)
Bing search (That's just my preference.)
Contextual search (A handy feature, I suppose.)
There is not an app collection of 100,000 with most of which being totally useless. This means that you"ll be able to find the good apps.
Even if Microsoft won't allow apps like a Wi-Fi router and file manager, all we would need to do would be to get all WinPhone7 users on XDA to install the XNA Game Studio (and possibly the Win Phone7 SDK) and we could simply upload .ccgame files to XDA instead of .cab files.
giggles33 said:
why must every phone be compared to an iphone...personally I never liked the iphone, never will...only good thing about iphone is the apps..otherwise it sucks..and high end smartphones should not be compared to it!
Click to expand...
Click to collapse
I know! Why must smartphones always be compared to a simple feature phone! I've tried the iPhone/ iPod touch (3rd generation) at Best Buy stores, and, let's just say, they froze more and gave out more errors in 5 sec. than 5 WinMo devices did combined over the course of 2 hours. The iPhone's keyboard isn't too great either. It's (the errors thing) 100% true.
Jim Coleman said:
There will be two types of apps
1. Apps with no need to run in the background
2. Apps that do need to run in the background
Examples of type 1 are games, spreadsheets and word processors.
Examples of type 2 are IM apps like palringo, and music streaming services such as pandora.
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive..
Click to expand...
Click to collapse
This is the right answer. Anybody who calms down would see that this makes sense. More Apple-like approval process for Type 2, free reign for Type 1
Shasarak said:
The impression I'm getting so far is that they will be very stingy indeed. The only people who will ever get access to non-standard API's will be phone manufacturers and networks, and even they usually won't get access to the native API's most of the time.
What we don't know yet is where multi-tasking sits within all this. Is it a standard managed API, an extended managed API, or a native API?
Click to expand...
Click to collapse
Yeah, you're talking about native vs managed stuff, which is not the same as simply allowing an app to have a background process. True, AT&T and HTC will have to apply to for native API use for stuff relating to making calls, etc, but that was only about OEMS and network operators.
Regular 3rd party guys, of which there are many, will be expected to get a way to do what they need on the device. Pandora we've seen in Music, you can expect apps like Palringo showing up in People
burnblue said:
This is the right answer. Anybody who calms down would see that this makes sense. More Apple-like approval process for Type 2, free reign for Type 1
Click to expand...
Click to collapse
Just because it makes sense doesn't mean Microsoft will act like that. In fact, I'm sure they will not.
The mass market will not benefit from every joe having all the API's because it's going make programs that cause glitches/crashes/memory leaks, etc. They are doing what they think is best for mass market and that is make sure things work well on the device and everything is user friendly with the least amount of hiccups possible. So that means more restrictions on us.
^^^ +1
Jim Coleman said:
What will happen is that when you develop an app, by default it will not have the rights to use the background APIs. In order to gain access to them and have an app run in the background, you'll need to ask Microsoft to provide the access and make it a type 2 app. Microsoft will only allow this if you can convince them it is necessary for the functioning of your app.
Type 1 apps will simply pause when the user switches away from them. They will remain in memory but will be unable to execute any code until the user switches back to them, whence they will resume execution. This will ensure the app cannot hog any CPU and cause the UI to stutter or slow down. This is definitely a good thing.
Type 2 apps are given access to particular APIs to allow them to, for instance, download updates or postings on IM systems. This will be strictly controlled and priority will always be given to the UI, again to ensure it remains smooth and responsive.
That's my take on what's going to happen, and we'll see if I'm right at MIX 2010 next month.
So your answer is - yes it will multitask but only when it is truly needed. Which to me is the best of both worlds. It will ensure a smooth user experience whilst still allowing background operations.
Click to expand...
Click to collapse
This neither solves problems nor guarantees anything though. Poor code is still poor code. Too many apps running is STILL too many apps running (slows the UI). MS can police neither. So, your #2 solution really makes no sense and has no advantages. MS has no way of predicting who will run what app and when on their phones. What if a user chooses to run several "Type 2" apps? Will you get some sort of error message? Will the MS police arrest you for ruining the UI experience? What happens after several years of approved type 2 apps hitting the market? Now were back to the same problems of WM.
Dude, we're talking about 1Ghz+, 512MB+ RAM phones here! You can run lots of apps without slowing anything down. Really, the "multitasking slows down the UI" argument is utter bull****. A good OS handles multitasking in a way that doesn't slow down anything. Restrictions are only necessary if the OS itself sucks. A good OS doesn't need them.
as my assumption ,OS freeze the application but still allow application to update the hub
http://www.engadget.com/2010/03/17/windows-phone-7-series-multitasking-the-real-deal/
We've definitely learned a ton about Windows Phone 7 Series here at MIX, but getting the full picture on multitasking has been difficult, since the OS isn't ready, no one has final hardware, and the emulator seems to behave differently than actual devices and Microsoft's descriptions. So let's set the record straight on multitasking: it's not going to happen, at least not in the traditional way. Not only have we directly confirmed this with Microsoft executives several times, but the developer sessions here are totally clear on the matter -- you don't tell 1000+ devs that they should expect their apps to be killed whenever the user switches away from them if you don't mean it. Now, that's not to say that the OS can't do multitasking: first-party apps like the Zune player and IE can run in the background, and third-party apps are actually left running in a suspended state (Microsoft calls it "dehydrated") as long as the system doesn't need any additional resources. If the user cycles back to an app, it's resumed ("rehydrated") and life continues merrily along, but if the user opens other apps and the system needs additional resources, the app is killed without any indication or remorse.
If that sounds familiar, it's because it's basically a single-tasking riff on Android and Windows Mobile 6, both of which also purport to intelligently manage multiple running applications like this, and both of which usually find themselves greatly improved with manual task managers. We'll have to see if Windows Phone 7 Series can do a better job once it ships -- we have a feeling it will -- and later down the line we'll see if Microsoft decides to extend multitasking to third-party apps. But for now, just know that you're not going to be running Pandora in the background while you do other tasks on a 7 Series device -- it is a question we have specifically asked, and the answer, unfortunately, is no.
so it doesn't support multitasking... at least not in a tradition sense.
but i guess this isn't too bad.. i mean, as long as i can start writing an email and then go online and then come right back to my cursor... or play a game, hit pause, send a text, and then come right back to pause screen.
hopefully i can connect to a site, switch to text... while i'm writing a text, wait for the webpage to load, and come back.
anyway, i'm pretty sure if MS can't compete w/ the ipod, MS can't compete w/ the iphone.
They have actually did a demo on loading websites in the background while doing other stuff so that will be possible.
why is it so hard to update my Yomomedia feeds while sending a text message?
It's plain dumb. RAM is made for a reason.
Now, that's not to say that the OS can't do multitasking: first-party apps like the Zune player and IE can run in the background...
Click to expand...
Click to collapse
Thats nice for the Zune-Player and the IE, but what if I want to use a different player or browser?
rorytmeadows said:
why is it so hard to update my Yomomedia feeds while sending a text message?
It's plain dumb. RAM is made for a reason.
Click to expand...
Click to collapse
WORD! Its really funny thoug how all those people here defending the decision not to include MT by asking what application really needs it. My opinion, every app that loads longer than 1 second, because that is how fast I activate a minimized application right now!
And on a sidenote, notebooks had limited amounts of ram and processing power combined with terrible running times for decades, and no fool ever came up with the idea of disabling MT to solve those problems...
Both the stock iPhone and WPS7 supports multitasking only for their own applications, so you will be able to play music in the background, browse the net with either the stock browser or third party browser. In the case of stock iPhone, a third party application called Nike can also run in the background but that's a rare exception Apple has made.
To be able to run third party applications in the background, the jailbreaking community gives us tweaks such as Backgrounder, Kirikae, Circuituous, Multiflow.
I think something similar might happen to WPS7. Some technical gurus either from the XDA community or other places might do something similar and jailbreak and introduce background processing capability for third party applications.
rorytmeadows said:
why is it so hard to update my Yomomedia feeds while sending a text message?
It's plain dumb. RAM is made for a reason.
Click to expand...
Click to collapse
Why?
OS still allows application keep running,OS just stops the UI rendering ,stops the playing music
eaglesteve said:
Both the stock iPhone and WPS7 supports multitasking only for their own applications, so you will be able to play music in the background, browse the net with either the stock browser or third party browser. In the case of stock iPhone, a third party application called Nike can also run in the background but that's a rare exception Apple has made.
To be able to run third party applications in the background, the jailbreaking community gives us tweaks such as Backgrounder, Kirikae, Circuituous, Multiflow.
I think something similar might happen to WPS7. Some technical gurus either from the XDA community or other places might do something similar and jailbreak and introduce background processing capability for third party applications.
Click to expand...
Click to collapse
It is patently absurd that Microsoft, of all companies, would enforce such a limitation. What about applications that you want to respond to the Accelerometer? Light sensor? Any other system events built into the OS/tool-kit? They have written all sorts of cool stuff like the Reactive Extensions (which isn't just for mobile) - how is this supposed to work if it doesn't support multitasking? How is my app supposed to respond to environmental events if it isn't freaking running?!
bjhill2112 said:
How is my app supposed to respond to environmental events if it isn't freaking running?!
Click to expand...
Click to collapse
Well, to be fair, MS has a way for it in WM, it's called persistent notifications, which works in many (not all) cases. It doesn't seem to be included in WP7 though, I don't see any traces of SNAPI.
vangrieg said:
Well, to be fair, MS has a way for it in WM, it's called persistent notifications, which works in many (not all) cases. It doesn't seem to be included in WP7 though, I don't see any traces of SNAPI.
Click to expand...
Click to collapse
I've been poking around in the tool kit and I can't find anything either.
MS says new multi-task in wm 7 is more like as iphone's
some apps will suspenses, then system will shut them automatically to clean up system resources
bestfan said:
MS says new multi-task in wm 7 is more like as iphone's
some apps will suspenses, then system will shut them automatically to clean up system resources
Click to expand...
Click to collapse
No ,it is different, on wp7s, while apps suspense to background ,apps still allow update the hubs and tiles and multi apps can be suspended to background
I'm trying to find out how to lock down a WM7 so that It Is only able to use its basic functions phone, camera, gps but blocks access to the to certain sites and the downloading of certain apps (i.e. games).
Would I be looking at a creating Custom Rom or is there another way to control what the phone can have access to.
Any Ideas or help would be appreciated.
K
at present there is no capability to perform this.
Well, who do you want to lock it down for?
You won't be able to download apps without a Live ID, so if your kids don't have it, they'll have pretty locked down devices.
kaisersolo said:
I'm trying to find out how to lock down a WM7 so that It Is only able to use its basic functions phone, camera, gps but blocks access to the to certain sites and the downloading of certain apps (i.e. games).
Would I be looking at a creating Custom Rom or is there another way to control what the phone can have access to.
Any Ideas or help would be appreciated.
K
Click to expand...
Click to collapse
I think it is not possible at the moment.
Desktop Windows has only had effective parental controls since Vista (2007). (There were relatively ineffective third party ones before.) Windows CE 6 (2006) only supports basic controls: http://msdn.microsoft.com/en-us/library/ee499001.aspx. And WP7 is built on CE6. Although WP7 is heavily controlled by its own mechanisms, so it could be added.
Management of controls was connected to Windows Live with Windows 7. This system could be added to phones, but it's all fairly new and there are other things to do first.
Thanks for the response guys
From what has been said it seems that this not really possible.
We are currently looking at what devices we need to acquire, and we need devices that can be locked down (Don't ask me why - management decision, probably related to data usage costs) so that user can only use it for work related tasks.
So OUT go things like gaming and social networking,
And IN are normal phone tasks's calling, texting, email, camera and the ability to sync to the cloud aslo, gps navigation.
We are looking at the WP7 phones because of Sharepoint as we have a lot of development planned that way and would like the ability to access that information remotely via a device.
Does anyone know of another way to achieve this or do I have to delve deeper Into the inner workings Wp7. Or failing that look at at different hardware/software.
Regards
K
MS should eventually update WP7 to be compatible with all the Exchange Activesync security policies which will give you the capability to achieve what you want. Additionally they have said they will add features so that enterprises will have the ability to lock down devices as they choose so if you are using Exchange already you may want to wait and see what MS produces. And you could always contact MS and see if they will let your company know what is coming down the road so you can decide whether to wait or not.
efjay said:
MS should eventually update WP7 to be compatible with all the Exchange Activesync security policies which will give you the capability to achieve what you want. Additionally they have said they will add features so that enterprises will have the ability to lock down devices as they choose so if you are using Exchange already you may want to wait and see what MS produces. And you could always contact MS and see if they will let your company know what is coming down the road so you can decide whether to wait or not.
Click to expand...
Click to collapse
efjay Or anyone - Where at MS should I enquire about this, is there a email address for these type of enquires.
kaisersolo said:
efjay Or anyone - Where at MS should I enquire about this, is there a email address for these type of enquires.
Click to expand...
Click to collapse
to lockdown marketplace (disable totally) you simply have to mod "LKG_Tuner_Config.xml"
and there would def be a reg mod to disable facebook
maybe this (I am looking for more
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Facebook\{A27A1782-535E-8F2D-9B81-4B6BA08FC179}]
"AccountState"=dword:3
[HKEY_LOCAL_MACHINE\Software\Microsoft\Facebook\[email protected]\Auth]
"State"=dword:[B][U]1[/U][/B]
[HKEY_CURRENT_USER\Software\Microsoft\GameFoundation]
"XboxLiveEnabledFlags"=dword:3
after you did that you can relock the phone and off you go
ceesheim said:
to lockdown marketplace (disable totally) you simply have to mod "LKG_Tuner_Config.xml"
and there would def be a reg mod to disable facebook
maybe this (I am looking for more
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Facebook\{A27A1782-535E-8F2D-9B81-4B6BA08FC179}]
"AccountState"=dword:3
[HKEY_LOCAL_MACHINE\Software\Microsoft\Facebook\[email protected]\Auth]
"State"=dword:[B][U]1[/U][/B]
[HKEY_CURRENT_USER\Software\Microsoft\GameFoundation]
"XboxLiveEnabledFlags"=dword:3
after you did that you can relock the phone and off you go
Click to expand...
Click to collapse
Sorry I'm New to this
To change the registry would you have to unlock the Phone?
Can you confirm that You can unlock and lock a WP7 Phone?
What are the implication of doing this ?
Is there a way of creating and deploying an wp7 app that would be only available to our company agents.
As far As I understand this you can only deploy any app via the Market Place - this is useless for any internal business application.
Do I need to wait for better mobile device management or is there away around this ?
Any pointers appreciated guys.
Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
2. Side-load it
tiwas said:
Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
2. Side-load it
Click to expand...
Click to collapse
2 won't work, as it could be redistributed.
1 might, but we all know how well registration models work (cracks)
this might be a job for phone-home drm.
tiwas said:
Two ways to do it, the way I see it...
1. Add the program to marketplace, but require an registration number to be inputted in the program for it to work.
Click to expand...
Click to collapse
This would probably be the best, especially considering that your agents probably need to login anyway.
But I think that you won't pass certification if they can't test the app.
I don't know what your company does, but maybe you could release an app that is many targeted at your customers and everyone could use. This app could then have a hidden setting to enable special functions after a agent has logged in.
Microsoft are planning on supporting this in the future, their current suggestion, IIRC, is to use some sort of login though.