• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Switching from iOS to Android

Avi$hay

Lurker
Hi.
Last year i have posted here about pretty much the same issue.
I owned a 3GS and switched to HTC DHD.
I loved it for its openness. all the restrictions in ios didnt exist on the droid such as the bluetooth functionality, file sharing without itunes etc. i hated it for its bugs, lags, crashes, terrible battery life and terrible apps though. so much i was envious of iphone 4 users and switched to an iphone 4.

HOWEVER

As much as the iphone 4 is great, its restrictions still disturb me. i want my phone to be able to do basic bluetooth and computer file transfer without any shitty program like itunes, plus high-end android are extremely fully-featured. Moreover, with the dual-core era i really started reconsidering moving toward the android zone (Specifically Droid Razr and Galaxy nexus). I own an iPad 2 as well which serves me well with highest quality apps (specifically music production apps).

so i thought of selling my i4, getting an ipod touch 64gb (since i use many of the iphone apps as well) and getting a superb android device as my mobile phone.

Should i wait for the quad-core to come out? or would a droid razr/galaxy nexus suffice?

Please help!
 
The droid Razr is a nice phone and the Galaxy Nexus as well. But, the Galaxy nexus is one of Googles Android phones, so it will receive updates before any other android device. It also comes stock with the latest version of Android ICS. But, that doesn't mean the Droid Razr wont get it but, you would have to do some waiting for the newest version. Both are dual-core and you can do this without any buggy program too. Also, resolution wise the Galaxy Nexus is a beast at 1280x720HD with a 4.65 inch super AMOLED screen with 1080p HD video at 30fps. It has a 5 MP camera which even though it's at 5 mp is still a great camera and it takes pictures super quick!
It has GPS, Bluetooth,MicroUSB 2.0 and Wi-Fi 802.11 b/g/n. And it has 1GB of RAM and a 1750 mAh li-ion battery. And it has a 1.2Ghz dual-core TI OMAP 4460 Processor.
 
i want my phone the best build quality, screen, speed and stability. for apps as i've mentioned i got my ipad and will get an ipod touch. those two as I've seen have met those needs but the question is if i should maybe still wait for the quad-core phones to come out
 
I would wait even thought the dual-cores are nice, but the quad-cores will blow them out of the water. I would wait to get the new quad-cores. You might want to check this device out, it is quad-core and it comes with ICS and HTC's new Sense 4.0. HTC One X
I would wait to get a quad-core phone.
 
Thanks man. I also think i should wait (the galaxy nexus is tempting as hell)
even though the htc looks good, i always follow the idea of never getting a new technology as soon as it comes out i.e Optimus X2 (1st dual core) ---- Galaxy Nexus (one of the latest dual cores). Besides, i had my issues with htc in the past...
 
It was my pleasure man, glad I could help. I am thinking about getting a new phone some day too but, you can't go wrong with the Nexus or the Galaxy s2 which, both are really nice phones. And if you don't mind it's 5MP camera then go for the Nexus but, sense you said you want a speedy phone then I might suggest the Samsung Galaxy S2. The S2 hes a exynos processor which beats the OMAP the Galaxy nexus has. Check out the nexus here Galaxy Nexus
and the Galaxy S2 here. Samsung Galaxy S2
Also, do you have a preference in screen size?
 
Trust me, as long as its over 4-inch and not 3.5 i am happy. 4.3 - 4.7 is great (5 and above is too much like the galaxy note)
I didnt like the s2. i never liked samsung the only reason i'm considering the nexus is because google is involved.

but then again, i'd rather wait to see whats gonna come next with the quad-cores, as they begin to enter the market:)
 
That would be best when deciding on the phone you want. I would wait on the quad-cores considering that there going to have a lot to offer, as well as hardware.
The Galaxy Nexus is a very nice phone and your guaranteed to get all the latest updates from google first before any other device on the market. And with the new quad-cores coming out, who would want a dual-core when you can have a quad?
 
No problem. Oh, when you wait for the dual-cores phones make sure to wait awhile after they come out, to assure it gets any bugs worked out. I hope you find a good phone and enjoy the forums.
 
The difference between us is that I like Samsung over HTC and that cores aren't too much of an issue for me since I don't play games much.

My year old Galaxy is still as smooth as when I first bought it, and very rarely crashes if at all. I do have had force closing apps but that's about it.

Personally, I would say stay away from HTC if battery life is your concern. Quad cores IMO are.unnecessary.
 
I have an s2. It is still running Gingerbread. This is two generations ago. I have no idea why they would release an older OS and then make us wait for ICS.

I would personally go with a Nexus over the S2 if available with AT&T. In fact that is what I am doing since I have not exceeded my 30 day exchange period with AT&T.

Is the Google Nexus available for AT&T customers?
 
The reason I care so much is the multi-language keyboards. The environment has also changed dramatically. Check youtube for a look into ICS.
 
For now it's only on Verizon, but there have been reports of an HSPA+ and a LTE version of the phone meaning that it should be multi-carrier before too long.
 
I have an s2. It is still running Gingerbread. This is two generations ago. I have no idea why they would release an older OS and then make us wait for ICS.

I would personally go with a Nexus over the S2 if available with AT&T. In fact that is what I am doing since I have not exceeded my 30 day exchange period with AT&T.

Is the Google Nexus available for AT&T customers?

2 generations? Its not. Gingerbread was the latest OS for Android phones when S2 was released last July. Honeycomb was released earlier than that yes, but Honeycomb was never designed to work on phones. In fact, it wasn't supposed to work on phones with smaller than 7inch screen size. So basically, up until ICS was released last December, the S2 had the latest Android OS.

Also, its normal for OEM branded devices to get the update 3-6months later than official Google release. They have to make it work with their varying hardware first along with their own customizations, and they cannot release unstable beta test ROMs like the other ROM devs do.

Going NExus has its own share of problems. You're more like to experience app incompatibilities and FC after updates than if you go OEM branded due to possible problems arising on the new OS. Ever notice why apps on the market always updates with "now compatible for latest ICS" etc?
 
Going NExus has its own share of problems. You're more like to experience app incompatibilities and FC after updates than if you go OEM branded due to possible problems arising on the new OS. Ever notice why apps on the market always updates with "now compatible for latest ICS" etc?

In the very beginning this is usually a problem, but after the first month it really isn't. Most of the apps worked fine right off the bat too, there were only a few that took a little bit longer to update. Now, it is hard to find a popular app that doesn't work with ICS.
 
In the very beginning this is usually a problem, but after the first month it really isn't. Most of the apps worked fine right off the bat too, there were only a few that took a little bit longer to update. Now, it is hard to find a popular app that doesn't work with ICS.

What I meant was after every update, its more likely to have incompatibilities because you'll be receiving the updates at generally the same time the developers will. I was just saying that don't be surprised if one day right after an update an app doesn't work simply because the developer wasn't fast enough to launch his app's update a few hours later.
 
What I meant was after every update, its more likely to have incompatibilities because you'll be receiving the updates at generally the same time the developers will. I was just saying that don't be surprised if one day right after an update an app doesn't work simply because the developer wasn't fast enough to launch his app's update a few hours later.

Gotcha.
 
Back
Top Bottom