Hi Folks,
I thought it might help if I put up a quick reference on how you can be most helpful when posting bugs...
Firstly - I love a good bug! It is only because people are kind enough to try out betas and post bugs that I am able to squash so many of them. This thread is not in any way meant to discourage people from posting stuff.
If you can, this is the info that will help me
1) What application
2) What version (press menu/about to get the version)
3) What device you are using
4) What happens (and if there is any doubt - what you expect to happen) - With Error information if possible
5) Steps to make this happen
1-3 should be easy. There is little reason not to provide these
4&5 are a bit more of an art - but if you get them right, you make it really easy for me to fix.
Posts like
Application X keeps crashing my device
are really unhelpful as they don't give me any idea what went wrong, so I can't fix it.
Posts like
When I select a contact in Initiate then tap and hold on the screen to show the actions list and tap on the rename icon, I get a reset with error -Dm line 366 invalid record-
make it incredibly easy for me to find the issue.
The key is to give steps that I can replicate to find the problem. The above example is a good one, someone else might have posted
I get a reset when I try to rename a contact
I might try to replicate that using the menu/rename option, or the rename button and not find the issue.
The best scenario is when you can tell me exactly what to do to get the problem.
Sometimes this isn't possible - in which case, the more info you can get the better. E.g.
Further, if I try to launch certain applications it reboots - Contacts, Calendar, DateBk, HotSync (when starting to hotsync)...
is better than
I keep getting resets
(the reason here is that there are two clues that this might be a cache issue - even though the poster probably didn't know that this was relevant)
Providing error messages can be very helpful.
Reset doctor can log your error messages (you don't need to register to use this function).
You can get the last error by dialing #*377
(different on some treos )so - please keep the bugs flowing and I'll keep squishing them.
Please give me as much info as you can and I'll do a better job
Home
Help
Search
Gallery
Calendar
Login
Register
