I need to test how my app reacts when an incoming call interrupts execution. How can I do this in the simulator?
Go to Properties of your App(right click on solution Explorer), Select Debug tab and there you will find a checkbox(Tombstone upon deactivation while debugging), check that. After checking it whenever the apps gets deactivated , it will get in to tombstone state while debugging.
I think that Scenario is not possible to Test in Emulator. You can make call from your app in emulator but Receiving can be tested in only Device. for more Reference you can refer this Question Windows Phone 7 emulator : Can I simulate a phone call.
To test for making a call from your app, you can find Reference here How to use the phone call task for Windows Phone 8
Related
I am trying to develop an app for windows phone that will detect calls and send notification to PC through wifi. Similarly it will also send SMS that are received to PC and when an alarm goes off in phone, a notification will be sent to PC. How should I proceed about developing this app?
Thanks in advance.
There is no API exposed to allow you to spy on incoming calls or SMS in Windows Phone (like there was with Windows Mobile). The only option would be to build this as an OEM extension, but unless you work for HTC, Samsung or Nokia, this isn't going to be an option.
See it's not that you cannot but to some extent you can. Like you can use Obscured Event to detect call , lock screen etc. go through this msdn discussion for details
Detect lock and calls msdn
And as far as the alarm or the reminder is concerned you can go ahead and design a reminder system within your app. Limit is 50.
Obscured event Windows phone
My Windows Phone XNA game calls Guide.BeginShowKeyboardInput to get the user's name. While the Guide's input screen is shown, if the user presses the Home or Search (hardware) buttons, the game is deactivated as usual - but if the user then presses the Back (hardware) button, the game should resume but it doesn't. Instead it shows the "Resuming..." message until Windows Phone gives up trying to resume the game and kills the process.
Please note:
My app is failing Microsoft certification because of this problem - I really need to fix it!
This only happens in my game when the Guide input screen is shown - when it's not shown, the game
resumes properly after being deactivated.
This problem only occurs when the game is run on WP7.x (verified problem on WP7.5 and
WP7.8) - although the game seems to resume properly on WP8 devices.
I've created a blank XNA game project, called Guide.BeginShowKeyboardInput and tested it using WP7.x devices, and this problem-behavior doesn't occur.
I've tested the game without enabling Music & my Trial License manager (they use timers) and it still does this.
Exact same behavior occurs in the emulator (resume-failure on WP7.x emulators, works fine on WP8
emulator)
I used threads to asynchronously download content during the loading screen - but they already completed and exited.
I don't believe other threads are running, although this seems like
it could be a thread-blocking issue.
Any other ideas on what could be blocking the game from resuming when the Guide.IsVisible or how to debug/resolve this problem?
The solution to this issue was simply to NOT use SuppressDraw when dealing with any operation that passes control outside of the app, e.g. Launchers, Choosers and the Guide.
Have you tried calling "Guide.EndShowKeyboardInput" in either the Deactivating or closing events?
So that the guide is closed before the app suspends, you do get 10 seconds to suspend so this might be worth looking into.
If you want the guide to re-show on resume, then in your state saving code just have a flag and open the guide if it's set.
I don't have a WP7 device yet. Everything is functional in My App on a Simulator, but when my customer test it, app does not function at all. e.g. VDO is not playing.
Is there a way to get a crash log from Windows Phone 7? (like iPhone).
You can easily create your own crash report. Basically this is what you have to do:
In your App class add an handler for the UnhandledException event
inside the handler prepare a log with everything you need (stacktrace, memory allocated, etc.)
use an email composer Task to send the report.
You can also check BugSense which is a cross-platform(iPhone,Android and Windows Phone) tool that collects and analyzes crash reports from mobile apps.
Disclaimer: I have developed the WP7 plugin.
One of the requirements for a Windows Phone 7 application that I am writing is to handle the app going into standby and back when something interrupts it (e.g. a phone call). This is called "tombstoning" an application. Is there a way to simulate this behavior on the emulator? It will be fairly difficult to test unless we can either do this or get an actual phone (the latter of which is a trifle difficult).
You can simulate tombstoning by simply pushing (clicking) on the start or search "hardware" buttons on the emulator. This will cause your app to be "tombstoned".
There is no way to simulate incoming calls, etc. on the emulator.
Check out these two topic sections for details on what Matt/Amenti describe:
http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff806372(v=vs.105).aspx#BKMK_Toforceanapplicationstatechangefordebuggingpurposes
and
http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff806372(v=vs.105).aspx#BKMK_Toforceanapplicationstatechangefordebuggingpurposes
I am pretty new to WinMo development. I managed to write my first app, debug it via the emulators but I failed to run the debug session on my physical phone.
I connected my phone to the development PC via ActiveSync, but that alone did not make my phone show up on the list among the selectable emulators. Is there anything I need to do before this would work?
Alternative: I want to program with the G-sensor and the bluetooth capabilites of the phone. Is there a way to play with them via emulators? How on earth do you shake an emulator? :)
After you hooked up and confirmed that ActiveSync is working, you should be able to select the "Mobile Device" form the target list. It is not listed by name, it simply is the only entry not ending in emulator.