Skip to main content

Buying Android Device for Development


So I am thinking of getting Sprint Nexus S from ebay to do android development. I am wondering whether getting a locked phone will hinder me from doing any kind of development work on the phone (pushing to app market, connecting to internet(i don't care about 3/4G as long as I can use wifi I am good)). What are some things that I should be worried about when getting a locked phone for development? Will the locked phone even run without SIM?



Or is it really necessary for me to get an unlocked phone for development? I currently use iPhone ATT and I am not planning to switch to Sprint.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. There is nothing wrong with getting a locked phone. As long as you make sure the phone doest require a sim. If it does. Make sure the sim is in. If that isnt a issue i dont see anything wrong with it. Its perfectly fine using it over wifi. As i have 3 locked phones i use for development ive purchased from ebay. 2 Tablets, Nexus s. Works great for me. You should be fine. =)

    ReplyDelete
  2. I don't see any problems in buying a locked phone if you only have the Carriers SIM-card. Else you might not even get it starting. But I would always prefer a unlocked Phone.

    Edit: You dont push your applications to Android Market from your phone but from the web.
    https://market.android.com/publish/Home

    ReplyDelete
  3. Rooting provides you with an extra edge when doing Android development. I would make sure you're able to root this phone prior to purchase :)

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex