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

Nexus Vs Razr

Hard to say. Where I live I actually get better Sprint than Verizon 3g performance. And my Evo 3D is not leaving me, period.

But I am getting a bit tired of one phone for work and pleasure. Many is the time I've had to wait on root customizations for fear a playful instability could impact my work.

I was looking at the Photon, but have decided to curtail my international travel, so now that there's a decent Android world phone, I really don't need it.

So the RAZR decision for me will come down to an assessment of what Verizon monthly plans will shake out and how.

I already have rgb qHD made by Sharp on my 3D, and believe it can't be beat for color accuracy and sharpness, so the whole screen difference thing on RAZR vs Gnex is a total don't care for me.

And while I was among the first insisting that bigger is better when 4.3" screens came out, the Gnex seems too moosey to me, just from the vids.

And I like Motorola, kinda maybe that cultural thing I alluded to earlier.


I hear ya...Well stay tuned brother! There is a good deal of us that are going to get it and review the heck out of it as soon as it drops. Myself, as well as Rush will put that thing through a heavy marathon of paces the first few days! Plus the Build Quality on the Razr looks awesome, my #1 gripe is always about build quality...looks like moto payed alot of attention to the Build Quality this time around.

I have always liked the Photon, and would have 100% grabbed it if it was on vzw...Sprint where I am is terrible as far as data goes...
 

Not unexpected. My problem with Motorola is how WELL they lock their bootloaders. HTC locks them as well, but hackers usually have them unlocked around release. When a bootloader is locked to this degree, it reduces the number of community developers that get the device, and by the time it is unlocked, they've all moved on to something better. Cyanogen(mod) is a solid case study for this. Moto's devices are usually last in support because of this bootloader policy.

And, I hate Blur. There's no way around it. It's sluggish and unresponsive. At least Sense and Touchwiz are mostly smooth. The RAZR was always a longshot for me, but I will still give it a fair shot when it comes out.
 
Not unexpected. My problem with Motorola is how WELL they lock their bootloaders. HTC locks them as well, but hackers usually have them unlocked around release. When a bootloader is locked to this degree, it reduces the number of community developers that get the device, and by the time it is unlocked, they've all moved on to something better. Cyanogen(mod) is a solid case study for this. Moto's devices are usually last in support because of this bootloader policy.

And, I hate Blur. There's no way around it. It's sluggish and unresponsive. At least Sense and Touchwiz are mostly smooth. The RAZR was always a longshot for me, but I will still give it a fair shot when it comes out.


Have u tried Moto's new UI ? If your going by the old Blur with your statements, that's understandable! However, the new UI is pretty damm good....Very smooth, and appealing I must say.
 
Have u tried Moto's new UI ? If your going by the old Blur with your statements, that's understandable! However, the new UI is pretty damm good....Very smooth, and appealing I must say.

I've tried the Bionic and thought it was a vast improvement over the X2, which is weird given same hardware. However, it still lags in place my Incredible doesn't. Likewise, my Incredible lags in places the Bionic doesn't. But should the Bionic be just as flaws as such a weaker phone, in terms of specs?

Earlymon has it nice, he's running outstanding hardware and HTC Sense.
 
X2 has a Tegra 2 and the Steve Austin has a 4430. The key probably is that the Bionic has 1gb ram and the X2 512mb ram, of which almost 100 mb is taken by the gpu (per their tech support).
 
X2 has a Tegra 2 and the Steve Austin has a 4430. The key probably is that the Bionic has 1gb ram and the X2 512mb ram, of which almost 100 mb is taken by the gpu (per their tech support).

Oh snap, it is Tegra 2. For some reason I was thinking it was OMAP. Thank you for pointing that out! Got a question on the discreet GPU memory. Do you have any links for that? Last I heard, only the Galaxy S did this (not specific to Hummingbird, as the Nexus S doesn't do this).
 
S3 also appears to memory map a portion of ram for gpu use. Like the PC graphics cards that do so well at video and also use this approach, the practice doesn't surprise me, especially for a media oriented phone.
 
Oh snap, it is Tegra 2. For some reason I was thinking it was OMAP. Thank you for pointing that out! Got a question on the discreet GPU memory. Do you have any links for that? Last I heard, only the Galaxy S did this (not specific to Hummingbird, as the Nexus S doesn't do this).


Moto tech support stated it and if you go to the DX2 forums, you will find plenty of "Where is the memory" type posts.

The Droid 3 also has 512mb ram, but a 4430 of course. Far zippier than the DX2 and the same as my Thrive with Tegra 2 and 1gb ram. Flyer smokes them both though.

Not sure what OMAPS do and only know the Tegra 2, since I was also wondering why the DX2 lagged so bad (had one and returned it) and that is the response from their techs. Per others in DX2 and XDA, the same thing was stated.


Added:

DX2 was rough, "out of the box".
 
With these unified memory architectures, I was pretty certain most devices mapped memory on the fly as needed, but then, hardware is my thing not software (hence why I called myself a half-assed developer). The original Galaxy S actually had discreet memory for the GPU (128MB).
 
They are really pushing the RAZR. I called last week and inquired about the Nexus and they noted my account to call me when it comes available.

So just now i called and inquired about the Droid RAZR and the gentlemen told me the obvious (not ready for pre-order) and that it is 10 times better than the iPhone and I should wait LOL. I like playing ignorant to see what they say. So i said "really" and he said "I would like to sell you a phone now but trust me its going to be an excellent phone. It will be our best."

He then noticed the note about the Galaxy and mentioned it. I asked would it be 32 or 16 gb for storage and he said he couldnt disclose that and said the RAZR will be a much better phone and to just wait for it. Now we all know the RAZR and Nexus are compatable and each has its own audience but i found it really strange how he was pushing the RAZR.

Usually they will try to get you into whats available and to push it over the iPhone was bizarre. Maybe he was just an Android fan but I thhought i would share this story because I thought it was a bit odd to be told to wait.

I do wonder why verizon is so stoked on this handset. Its a great handset yes but why the excitement? We'll find out soon enough.....

You also have to figure the salesman are probably told to try and sell more droid phones that are loaded with bloat since verizon would make more money off of those phones. I think both will be great phones just depends on what you are looking for you wont be disappointed by either.
 
Catch being, the Nexus might be a month or more later, if the Verizon statement means later, rather than earlier.

I think if the Razr turns out to be a great device, a lot of Nexus hold outs might cave.

Motocast alone will push people over the edge. Simple to use and amazing performance.

Well yes it could be a month but the leaked map's had the nexus coming out the 10th which is a little over 2 weeks away. It also had the razr as oct 27 which we all know is preorders so it may be the date but with android things change all the time so we shall see.
 
The Razr has my interest but I have some concerns.
1. Battery life / working and living in LTE coverage w/o wifi during the day.
2. Stability - I've owned the Droid (x2), Droid X, and my wife had the Droid 2. All would randomly reboot :-(
3. Heat....I hope it's not an issue but something Ive noticed on Moto phones.

I'm digging the thin design, Kevlar body, fips 140-2 compliance, and UI. Rooting the phone is all that's needed to remove bloatware, I'm not worried about custom ROM'S. I'll keep my eye open for more information on this phone.
 
The Razr has my interest but I have some concerns.
1. Battery life / working and living in LTE coverage w/o wifi during the day.
2. Stability - I've owned the Droid (x2), Droid X, and my wife had the Droid 2. All would randomly reboot :-(
3. Heat....I hope it's not an issue but something Ive noticed on Moto phones.

I'm digging the thin design, Kevlar body, fips 140-2 compliance, and UI. Rooting the phone is all that's needed to remove bloatware, I'm not worried about custom ROM'S. I'll keep my eye open for more information on this phone.

Battery life is the biggest thing for me. I want a phone that can last through a day and the lte phones now just can't do that. I am not always able to charge my phone so a good 8 hours should be able to get done.
 
The Razr has my interest but I have some concerns.
1. Battery life / working and living in LTE coverage w/o wifi during the day.
2. Stability - I've owned the Droid (x2), Droid X, and my wife had the Droid 2. All would randomly reboot :-(
3. Heat....I hope it's not an issue but something Ive noticed on Moto phones.

I'm digging the thin design, Kevlar body, fips 140-2 compliance, and UI. Rooting the phone is all that's needed to remove bloatware, I'm not worried about custom ROM'S. I'll keep my eye open for more information on this phone.


Just a heads up...

My Bionic doesn't get hot at all!

Hopefully the Razr follows that trend.
 
Not unexpected. My problem with Motorola is how WELL they lock their bootloaders. HTC locks them as well, but hackers usually have them unlocked around release. When a bootloader is locked to this degree, it reduces the number of community developers that get the device, and by the time it is unlocked, they've all moved on to something better. Cyanogen(mod) is a solid case study for this. Moto's devices are usually last in support because of this bootloader policy.

And, I hate Blur. There's no way around it. It's sluggish and unresponsive. At least Sense and Touchwiz are mostly smooth. The RAZR was always a longshot for me, but I will still give it a fair shot when it comes out.
...and "yeah, but"....

The Droid X is a perfect example of the above NOT happening. Locked bootloader promised from pre launch, and still uncracked. Yet there are/were numerous Froyo and beyond based ROMS that completely removed Blur and any hint of bloat once we had root.

Funny thing is? a lot of the custom ROMs had "dial-a-blur", where you could reinstall some blur elements from a pure AOSP experience. Because not all blur sucked that hard.

And with simple root and TB or Root Explorer, you could quickly and easily remove bloat, while running a slew of alternative UIs that allowed you to customize the phone out the wazoo. My final iteration on my DX ended up just freezing bloat and running an alternative free launcher because the performance at this point is hardware constrained, not impacted by blur.

After seeing Blur on the Bionic, I can tell you it is much further refined/reduced from the DX experience. I just don't see it being that big a deal unless people really need to fall on the sword on this one branding issue.

A much bigger branding issue is that fugly MOTOROLA silver badge up top. Hope that goes away...otherwise I'll need a black Sharpie or something...
 
With these unified memory architectures, I was pretty certain most devices mapped memory on the fly as needed, but then, hardware is my thing not software (hence why I called myself a half-assed developer). The original Galaxy S actually had discreet memory for the GPU (128MB).


Agreed on the dynamic allocation, but when I posted this (especially at XDA) I got flamed by True Believers. If you go by Moto techs, they are correct in their assertions. Also helps explain why so much ram is not accounted for and the device is a memory management needing mess.

One of the TBs linked an Nvidia page that appeared to support their assertions of an allocation as well (I gave up and returned the DX2- not worth the hassle). Summary being, the Tegra 2 and 512mb ram is not a good mix- for whatever reason.
 
Just a heads up...

My Bionic doesn't get hot at all!

Hopefully the Razr follows that trend.

Like the D3, the Bionic gets hot when running browser based Flash video, but this is not an issue just for the 4430, since worse for the Tegra 2.

Flash appears to be the main weak spot for heat and battery life. The one chip that appears to defy this and is supported by Anandtech's review is the 1.5ghz Scorpion in the Flyer. It does not get hot and performs better than the 4430 and the Tegra 2 for Flash video and video in general.

Flash based video and apps/games that get the cpu and gpu sweating will be the big test for how well the Razr manages heat and battery life. Yes, I have mentioned this a few times, but IMO, a legit concern.

All of that said, I use Netflix and Zumocast (aka Motocast) and the D3 barely gets warm and that is with 3G or higher def content over wifi.

The more I think about it, FLASH appears to be the problem and still not ready for prime time on phone form factors. Sure, the Scorpion 1.5ghz is better, but the Flyer has a bigger form factor and may dissipate heat better.
 
Yea my lady's flyer has never gotten Hot!

However...Flashhhh? Hmmmm?

I remember a certain CEO of a company named after a certain Fruit that plays a big part in Snow White refusing to use Flash!

Ring any Bells?
 
Yea my lady's flyer has never gotten Hot!

However...Flashhhh? Hmmmm?

I remember a certain CEO of a company named after a certain Fruit that plays a big part in Snow White refusing to use Flash!

Ring any Bells?


Yep. If they ever feel threatened in marketshare, watch their stance on not allowing Flash to change
 
As for heat - any phone will heat up if you use data continuously for some time. Just try to download a 50MB file and you will see.
 
Back
Top Bottom