07-24-2008 05:29 AM
I too confirm the same on OS 184.108.40.206 but it works perfectly in below versions.
07-24-2008 08:29 AM
What I have is 220.127.116.11. Won't have a chance to try this on other versions for next couple of days. Mark Sohm, do you still need to sample code to reproduce it? I can't share the entire app, so I am gonna have to extract just enough code to share with you. Let me know.
07-24-2008 11:58 AM
07-24-2008 05:57 PM
Following yosoh's comment, I downgraded my device to 18.104.22.168 and the problem went away. Originally I had 22.214.171.124.
I still don't have a 4.3x device to try this. I am working on getting you the code.
08-05-2008 12:29 PM
This issue was reported in early bundles of 4.5 and 4.6 and is confirmed to be resolved in 126.96.36.199 (and above) and 188.8.131.52 (and above).
10-24-2008 08:02 AM
I like my apps to be as 'OS version transparent' as possible (how could I ever convince all my customers to update their OSs' ? )
I have checked the mentioned KB article but the fix seems to have something to do with
So I conclude that the bug was related to startup.
But I would like to change app's name/icon on a particular event -> in a phoneLog listener, for instance. So, my app already has an icon set, but if there are any unanswered calls, my app icon and/or name would change.
I got an IllegalArgumentException thrown message ;(
Is it allowed to change the app icon/name after the initial icon/name are set?
If yes, what am I doing wrong?
10-24-2008 08:19 AM - edited 10-24-2008 08:43 AM
I am sorry.
After reading through thread: Setting a rollover icon I found out two things:
1) Drawing on the screen must be made in a separate thread (invokeLater)
2) The icon must be set for the non-system project (in my case the second entry point -> how intelligently disinclined of me )
Point 2) solved my problem.
But since now I am aware of the bug, Is it safe to assume that by using invokeLater older OSs won't have problems ?