Device for Android development [closed] - android

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
not much of a programming question, but development related still,
I'm starting Android development and have been at it for just a little over a week. So far so go regarding progress, specially for someone who hadn't touched Java in his life (but have good C#, Objective-C, VB.NET and Fortran experience)
As I'm looking into a testing device I'm undecided on the phone to get. I need it to be unlocked, so I'm looking into Dev Phone 2 or Nexus One. The difference being $120~ish in price.
Anyone having one of those and using it for development? which do you consider is the best choice. Is the extra speed and screen in the Nexus One worth it?
I'm targetting SDK 1.6 but down the road I can see myself playing with 2.1.
Any input is appreciated
Regards

Something I learnt today was not to let a developer work on the faster model of mobile device when most of your users have the slower model. If it's good on the faster one, it's not always good on the slower device. I'd get a retail G1 as they can be flashed to all kinds of Android revisions. Plus they'll be cheap.
If you go for the Nexus 1, your apps will look better but only to Nexus 1 owners, mostly!

From what I've heard all Android devices are going to get a bump to some form of 2.1 in the future. The specific feature set of each particular build would depend on the hardware capabilities of the device. Neil makes a good point about speed and polish but with a device like the G1 (which I have and love) you will yourself to be limited by the hardware whereas with the Nexus One you can choose to limit yourself or you can choose to develop Live Wallpapers!
Also, you've asked 7 questions and haven't accepted any answers. If you keep that up you'll soon find that people are less willing to spend the time answering your questions.

If you want a test device go for the g1. If you want a good android phone for everyday use go for the droid or the nexus one.
For development be careful which carrier you buy the phone from, some of them like AT&T will change them to forbid installation of software from unknown source etc. to enforce the market. Those are pretty useless for a developer then.

Related

What are differences between same ROM for different devices? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
For example, can anybody give some concrete examples of differences between Cyanogen Mod 10 for Samsung i9100g and CM 10 for i9100?
As far as I know, they have different hardware and that's why their drivers are different, as a result their HAL are very different from the other. However, I'd like to have an example contains -maybe- several lines of code.
I am aware that there are many many people who wants to get into Android porting/development and does not know how to start what to modify/change, I am one of those. I think the answer of this question will be beneficial for those.
The biggest is going to be the kernel and the RIL (radio interface layer).
Different devices have different hardware. Different hardware needs different drivers. If you have two similar devices often little modification needs to be made to run one OS on a sibling device. However, even hardware that looks the same externally can have drastically different internals.
If you want to get into platform development, follow some of the people who do it and look through what they're doing. jt1134 does a lot of the kernel and platform dev for the Samsung devices. The CyanogenMod org has a lot of code worth looking at too and the team even has a wiki that goes into some of the finer details about building from source.
You should also sit around in the Android development IRC rooms on the Freenode and Mod-a-droid servers. You can ask questions but don't always expect to get an answer. You can even try PMing jt1134 on freenode (if he still hangs out there), he's pretty responsive if you can convince him you know what you're doing << as in read all the publicly available documentation first.
Here is an outline of the process you need to follow.
Milestones:
0.5. Setup a development environment http://source.android.com/source/initializing.html
Download the kernel sources from Samsung.
Compile the Linux kernel.
Wade through all the developer docs at source.android.com
Download the Android platform sources from googlesource.
Make any modifications required for your device (for example: you may need specific vendor files (drivers) for your device, you might need some custom init scripts, etc.).
Compile the android platform <-- this takes a long time
After this, you should have a OTA flashable copy of the Android Open Source Project that you can test on your device. This process took me about a month to research and get down, it's not a trivial endeavor, I wish you luck.

Google Nexus 4 for Android Development? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to buy a phone for android development and testing. I know that Galaxy Nexus has good reputation among developers what about new nexus 4?
In Nexus 4 my minimum OS version will be 4.1.2 or 4.2. If I wanted to test previous versions would I need another phone?
If I upgraded nexus 4 to next OS verson (for example android 5.0) I would be able to downgrade it to 4.1. How complicated is to flash ROM on Nexus series?
Overall, using the most recent version of Android for development is the way to go. (E.g.: Pre-honeycomb versions stored raster data of images/bitmaps in native memory, thus the Memory Analyzer Tool, when you searched for memory leaks not showed the actual size of a bitmap leaked, just a few hundreds of bytes.)
On the other hand, vendors are customizing their phones, they have different drivers for example the camera. So testing only on one phone, in some situations might not be enough... I'd advise to have an older phone (with low available memory, pre-honeycomb os), and a newer one...
You should integrate ACRA, or other crash reporter tool, that enables you to track your product out in the wild. Bugsense or similar solutions provide you a nice Web interface, where you can see the different Exceptions that occured in your code for users...
If you don't have access to an actual phone, TestDroid from bitbar.com can provide a solution, as they have a cloud of different android phones (>100) where you can execute your test cases...
As for downgrading, I don't know if that is supported...
But the latest phone you can get. Longevity is better that way. You can test for other phones on the in-built emulators.
Here are some links to help you out:
https://developer.android.com/tools/testing/testing_android.html
https://developer.android.com/tools/testing/index.html
http://www.vogella.com/articles/AndroidTesting/article.html

Are physical devices necessary for android, ios and blackberry testing [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Buying devices to test your apk/ipa/alx on different android/ios/blackberry phones is getting heavy burden on pocket since it turns to be a dead investment very fast as technology is progressing too fast and you can't just keep on buying to know your app's user experience.
Is there any company that provides the services to save our dead investment? I've explored Keynote DeviceAnywhere which is pretty good but the rates are quite high.
I'm waiting for a solution asap.
Thanks.
Definitely.
I am not familiar with Eclipse or the Android simulators/emulators (nor BB or winPhone 7), but in any case you want to test on the real thing.
Even if the behavior is the same (some times it isn't), the performance is completely different between a real device and a simulator.
Android
Definitely YES. Applications run munch faster on devices than on emulator. In the long run , buying devices will save developers time thus save you money. The best devices for developers are Nexus line unaffected by OEM software (think of Samsung Touchwiz , HTC Sense).
Samsung lets you use their real device over the network for a certain period of time.
iOS
YES . The simulator is pretty close to reality. If you're on budget, you may buy second hand :
iphone 4 or wait for the upcoming iphone 5
iPad only if you're
targeting this support.
Add the developer licence extra cost too , to run on a device you must have a licence . iOS developer Standard = 99 USD and more for Enterprise Program = 299 usd
Blackberry
Don't know

Android vs iOS development [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I have just finished learning application development on android platform, as In matter of language it was easier to understand. However the convention drove me crazy yet simple enough to understand. Now the dillema is I am about to jump in iOS development. Language part wont be hard to understand but I am bit worried about design pattern or use of Xcode.
What challenges I might face which differentiate these two develoment enviroment? And which one is easier to deal with and more productive?
See the "Java" section in this post. Ease and productivity are in the eye of the beholder. Many find Objective C to be incredibly natural and beautiful. Others find it bizarre and frustrating. If you're willing to embrace the iOS way of doing things, you can pick it up very fast. If you fight it and try to keep coding in Java ways (or C way, or C++ ways), then it will be very challenging. The trick is to really work through the tutorials and not just try to figure out "how do I do X that I'm used to doing?" Often the answer is "you don't do X. X happens automatically when you do Y." But the place to start is working through some tutorials.
The Apple documentation is mostly excellent. You should spend time reading through the Programming Guides. Don't just jump to the References. You'll be very confused.
Now i can give you some facts about both that i find really important for clearing your dilemna :
1. Ios development is really costly as it requires a mac as well a hardware device such as iphone to stimulate which costs much more than other phones that you might already know by yourself
2.Android developer have to pay 25$ to become android developer while for Ios it take 100$ per year and your subscription dies after that so yeah again Ios costs much more.
3.Now, swift is used in case of Objective C which is incredibly easy,efficient and I ensure you will fall in love with it(according to me its easier than java itself).
4.Lastly,I myself have worked with the android studio and believe me, Xcode is now easier than android studio(with bugs fixed).
So,the zest is Ios development is costly but its worth learning it and now apple shifting to the new Swift, its super easy now and for the layout stuff don't worry, with time you will get a hang for it
Android and iOS operating system are best at its place. Both are doing good, but it is obvious that one OS can have any feature as pro while other can have it as a cons.
Well, this is my personal opinion that i will choose Android over iPhone for below reasons.
Obviously the first is Price. You can afford a pretty good Android Smartphone with awesome hardware configuration in same or cheap than the price of the iPhone.
Customization: You can customize the way you want like install other OS like Cyanogen and a lot custom Android OS is available over internet (Flexible OS). iPhone is limited to customization. Though jailbreak option is available, but who wants to knowingly spoil that handsome price iPhone. Tons of customized screen launcher available in Android.
Battery: Early battery drain is always the problem in iPhone. Well, battery saving gets better in Android with the Doze feature introduced in Marshmallow. And the good part is, most Android phone’s battery are replaceable and it is pretty easy stuff as compare to iPhone.
Multi-tasking support with multi-window feature and flexible widget in Android.
More free apps as compare to iOS
Custom ROMs. Android gives full control (root) over your phone as compare to iPhone
Memory: In iPhone memory comes at huge cost and no expandable memory as compare to Android. Android supports expandable memory and it does not get that pricey with the increase in the in-built memory
Developer: For those who are willing to develop Application in Android can get the huge community support and can build apps on the affordable hardware rather than iOS. iOS hardware comes at handsome cost as compare the Android.
Well, above are the few points that makes me feel Android is better than iPhone. And no offense to the iPhone users. iPhone is best at its place.
Ref : enter link description here

Android Development Device [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I'm looking to get a device (phone, tablet, etc.) for developing Android applications. I know I can use the emulator to get me started, but I feel like that will only get me so far along. I'm looking for something reasonably priced, and I don't want a phone contract, data plan, etc. Anyone have any suggestions?
I would recommend either a Nexus One or ADP2 ( you can get via Market once you sign in as developer. ). Other option is ebay. All attendees of google i/o got moto droid as a gift. And several devices are on ebay, priced around 350-400.
I wouldn't buy G1 for a reason i think it close to end of life. I'd also avoid devices alternative homes and ui ( blur, touchwiz, sense ). You want to clean google experience phone.
Advantage of Nexus of Dev phone - you'll have engineered bootloader, which let you to install custom roms and you can get root access which among other things allow you to use awesome tool hierarchyviewer ( from SDK ) on the device .
As a registered Android developer you can get an unlocked phone for $399. However, I am sure if you keep an eye on ebay you can find something that will suit your needs at a cheaper price. I see a bunch of Motorola Droids listed for a little over $300.
While the Nexus One and ADP2 are great because you can load custom builds of Android on them, that doesn't really sound like what you are most interested in. In fact, doing so will preclude you from running the Market application. For application development, you really just need any phone that lets you load non-market applications over ADB. You may want to consider getting a phone that has a keyboard to ensure that it works properly for your application. Finally, take into consideration which version of Android you are targeting. Newer phones run newer versions of Android.
If you plan developing something that might take an advantage of a hardware keyboard, get Motorola Droid/Milestone or a G1 (which you can turn into ADP1). I'm using the latter as my apps are targeted at 1.5+. Nexus One is the other option.

Categories

Resources