On 7/31/07, <b class="gmail_sendername">John Seghers</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
No, it was definitely the SIM. Certain handsets with certain SIMs would not<br>download off our server (They would download the JAD, but not the JAR)--and<br>the JAR was being blocked, it wasn't a case of it downloading and then
<br>refusing to install because of a bad certificate.<br><br>Changing the SIM would allow it to proceed.<br><br>Also, log into Samsung's developer boards and you will find commentary that<br>other developers were running into the same issue.
<br><br>- John</blockquote><div><br><br>I wouldn't put it past any telco to do something like that. I never encountered it myself on tmobile, but I generally only browse with gprs/edge and save downloads for wifi or pc.