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

Still Confident Bravo is coming to Verizon

Status
Not open for further replies.
The N1 physically has 512MB of RAM. The limitations are most likely based in Android so if the Bravo has 320MB of RAM, well that's less, physically. But they'll be subject to the same limitations until the supposed kernel update opens things up. Right now, draw. Later, advantage N1.

From the leaked brochure, I think it's 512MB of ROM for each phone and Android sucks up half of that. Draw right there.

How is a custom UI sitting over Android and using more memory going to run faster than the stock experience? Add to that taking away 150MHz? I'm guessing huge advantage N1 here.

Last I checked any android phone that has specced RAM is about app storage. The Droid has 256mb. Low and behold how much room does the Droid have for App storage? 256mb.
Google fails to address app storage issue with Droid and Android 2.0 – Android and Me
Hence the N1 should have 512mb for app storage. Only it doesn't. I don't know why that is as I thought it was going to be a selling point. But its the 256. Hence the Bravo being specced at 320 means 320 for app storage. Hell even if you take the RAM requirements for the OS's you're still looking at 200mb for the N1 and 220MB for the Bravo. Advantage Bravo.
How is a custom UI going to run faster then stock? Well I guess if you've never paid attention to anything that has come before it it would make sense that the stock would run faster. But then you'd have to say stock android never runs laggy. You now thats not correct. Stock android has had complaints of lagginess since 1.6 at least. Sense on the other hand is not some program that is simply installed onto an android phone no matter how many people act like it is. It take Android and modifies then optimizes parts of it. Android OS, not so much (remember stock android is not optimized for particular devices like Sense). You can have easier scrolling on a Sense device and laggy on a stock device. So when you take into accoun traditional lag of the stock OS the possible lacking of 150mhz may not make that much difference at all.
 
Like Kyler said. You are a little wrong about the RAM. Android itself is limiting the RAM usage. So as upgrades come around you will be able to use more RAM for storage I assume. Also I am very surprised that RAM is used for app storage and not the internal flash memory. The Nexus one has 512mb RAM and 512mb Flash. Usually random access memory is used for holding info for active programs not actually storing programs. So my whole RAM argument was based on the idea that the Nexus One will be able to run complex programs with needs for high RAM usage better than the Bravo or at least more programs at once. But if RAM is actually used for App storage the Nexus one will lets say be able to hold 384mb of apps in ram and still have RAM left over for running processes.

With the Sense UI being upgraded my only big concern would be how long would HTC make upgrades for your phone? For example HTC may only want to upgrade their newest phones with the newest version of Sense, they may choose not to upgrade the older phones to make people buy a newer device. From what I read it is not uncommon for HTC to leave a phone on an older version of Android without giving an upgrade option. But I must admit that I am sure the Bravo will get the first few updates.

Finally you made a good point about how the Bravo can just be brought into Verizon while the Nexus One would need to be sent out if there are problems with the phone. That is def a Bravo advantage.

I personally am on the fence right now between the Bravo and the Nexus 1. My other big concern is price. I am on a family plan although I am the primary line. I am worried that Google may do something similar to what they did on T-Mobile and not give the discount to people on the family plan. If that is what occurs I would have to go with the Bravo if it means paying $529 for a nexus one versus a subsidized $250 or so for a Bravo.

All I know is every Android phone that says what the ram is, that amount equals the app storage space. Of course its also my understanding you cannot modify data on ROM (hence read only memory) unless its EEPROM. Where as you can make RAM disks in computers. I dont recall EEPROM being mentioned with Android phones. Maybe I'm wrong (its sure as hell wouldn't be the first time) and they just dont bother to make the difference between ROM and EEPROM.
I'm going to wait till the N1 launch hoping that something else comes out before then so I have a choice. The arduous support wouldn't be so bad if it wasnt for the reports of the N1 being so fragile. I'm also on a family plan. My hope is that Google could treat Tmobile the way they did because the N1 is so much better then the Mytouch 3G where as the N1 is not that superior to the Droid. I dont think anyone outside of the most devoted Google fanboi can make the argument the N1 is so much better then the Droid to get a N1 unlocked for $300+ more then the Droid if you want to keep a family plan. Hell I don't know if the N1 is superior enough to justify me paying $50 more to upgrade to the N1 on a 2 year contract then what I would pay for the Droid on a 1 year contract.
 
ok, is it TOTALLY confirmed that the nexus one RUNS at 1ghz?

how do you know what a phone is running at just by looking at it in an office meeting?
 
A website stating the specs of a phone mean nothing. has anyone checked what is being clocked at?

and like i asked, can you tell the current processor speed by looking at a device?
no
 
A website stating the specs of a phone mean nothing. has anyone checked what is being clocked at?

and like i asked, can you tell the current processor speed by looking at a device?
no
From what I've read, it doesn't look to be clocked down. It is clocked at 1GHz.
 
i had a feeling it wasn't at 1ghz.

jk. ok then, so will we see a difference in ~150mhz?
i don't care. just give it to me.

So was this device he used the verizon nexus unit? most likely not due to sense ui, right?
 
i had a feeling it wasn't at 1ghz.

jk. ok then, so will we see a difference in ~150mhz?
i don't care. just give it to me.

So was this device he used the verizon nexus unit? most likely not due to sense ui, right?
That's Android 2.1, not Sense. And the Nexus on Verizon won't have Sense either, if that's what you mean.
 
That's Android 2.1, not Sense. And the Nexus on Verizon won't have Sense either, if that's what you mean.
I would imagine, a month after the Bravo comes out, the Nexus will get sense because of their screen resolutions. But from what I know, a device that was actually made with sense, will always run best.
 
All I know is every Android phone that says what the ram is, that amount equals the app storage space. Of course its also my understanding you cannot modify data on ROM (hence read only memory) unless its EEPROM. Where as you can make RAM disks in computers. I dont recall EEPROM being mentioned with Android phones. Maybe I'm wrong (its sure as hell wouldn't be the first time) and they just dont bother to make the difference between ROM and EEPROM.
I'm going to wait till the N1 launch hoping that something else comes out before then so I have a choice. The arduous support wouldn't be so bad if it wasnt for the reports of the N1 being so fragile. I'm also on a family plan. My hope is that Google could treat Tmobile the way they did because the N1 is so much better then the Mytouch 3G where as the N1 is not that superior to the Droid. I dont think anyone outside of the most devoted Google fanboi can make the argument the N1 is so much better then the Droid to get a N1 unlocked for $300+ more then the Droid if you want to keep a family plan. Hell I don't know if the N1 is superior enough to justify me paying $50 more to upgrade to the N1 on a 2 year contract then what I would pay for the Droid on a 1 year contract.

You're totally confused. Most of the phones out prior to the N1 have 256MB RAM. This is dynamic and it's used for programs that are running. No different than a PC. To date, all the phones also have 512MB of ROM. Half of that is dedicated to the OS. Therefore that leaves 256MB ROM for app storage. You're mixing this up as it's mere coincidence that the remaining ROM is equal to the RAM amount generally found in phones. Nowadays all ROM is really just programmable flash memory. Write once ROM is a thing of the distant past. It's still referred to as ROM to differentiate from RAM. The write/erase operation is permanent until the next time you request the operation. RAM is dynamic in that it's constantly refreshed on a rolling basis. This is why RAM requires power to keep things actively stored. It also has a much faster read/write time compared to flash memory. If you were actually storing apps in RAM (you're not), you'd lose everything on a power cycle.

I get that Sense is optimized, but remember it's consuming RAM which means less is available. Most people claim that the Eris is very snappy until you start running multiple apps in the background. Then things slow down. I know stock Android has its moments of lag, but without Sense, there's more available memory. There's also no custom UI eating CPU clock cycles. Sense will consume more resources than stock Android. Now take away 150MHz and it's obviously a handicap. Probably won't see it on average but I bet it'll show up if you're running multiple apps. That's where the N1 will come out ahead. I still think they should be keeping the Incredible clocked at full speed if Sense is present, but it's probably both a battery saver and differentiator as to not compete with the N1 directly. Just my $0.02.
 
I would imagine, a month after the Bravo comes out, the Nexus will get sense because of their screen resolutions. But from what I know, a device that was actually made with sense, will always run best.
Yes, the N1 can have and probably will have Sense, but only via custom roms. I was merely stating that Google will not sell the N1 with Sense on board.
 
Nexus One does not run at 1GHz but at 998MHz|OCWorkbench.

And regarding the RAM issue, both Google and HTC list the N1 with having 512 Flash ROM and 512 RAM. The Bravo leaked specs list it with 512 Flash and 256 RAM (rumored upgraded specs list it at 320 RAM). So the N1 does have the advantage over the Bravo with regards to RAM.

That video is a GREAT find! That answered a lot of questions for me about the processor and if you can speed it up or not. Looks like we'll be able to speed up this phone to full processor speed if it comes underclocked. So, that issue is resolved, as far as I'm concerned. And what a valuable app that is! So many great settings to help you optimize battery life. Would definitely be a must have for me when I get this phone.
 
I get that Sense is optimized, but remember it's consuming RAM which means less is available. Most people claim that the Eris is very snappy until you start running multiple apps in the background. Then things slow down. I know stock Android has its moments of lag, but without Sense, there's more available memory. There's also no custom UI eating CPU clock cycles. Sense will consume more resources than stock Android. Now take away 150MHz and it's obviously a handicap. Probably won't see it on average but I bet it'll show up if you're running multiple apps. That's where the N1 will come out ahead. I still think they should be keeping the Incredible clocked at full speed if Sense is present, but it's probably both a battery saver and differentiator as to not compete with the N1 directly. Just my $0.02.
Well said. I love Sense, it's showed a little of what Android could be if Google got off their asses, but it's too much of a bear on the resources, as shown on the HTC Hero line of phones. And add on the 2-3 month wait on OS updates (android 2.0 was out november) and maybe longer, that is if they come at all, and Sense is starting to lose its shine. Having said all that, I still love my Eris and will continue to do so until October when I'm eligible for another upgrade. :D
 
Let's not even worry about that--we have enough on our plate.
Incredible ALL YOU CAN EAT BUFFET! ....uhm guys/gals, so is this thing really going to be the most seamless and interoperable phone on the Verizon market? I use Google Voice, and Wave, I was under the impression that it was going to have the 1Ghz Snapdragon, which would make it the fastest "F"ing thing out there.
 
Incredible ALL YOU CAN EAT BUFFET! ....uhm guys/gals, so is this thing really going to be the most seamless and interoperable phone on the Verizon market? I use Google Voice, and Wave, I was under the impression that it was going to have the 1Ghz Snapdragon, which would make it the fastest "F"ing thing out there.
I don't know. The (confirmed) Nexus will be their fastest phone. If the Bravo comes, I'm sure it will be pretty similar but specs are be thrown around right now.
 
Been reading this site for a while, just posted to throw in one thing...

This red backing on the rumored "Incredible". Anybody notice the two red backings on other phones on the leaked roadmap for 2010 by HTC? I personally don't think we are looking at the Bravo, but The Legend. For starters, Droid Developer says the same size as the Behold II. Last I checked, that is a 3.2" phone.
 
didn't he say it was 3.7 inches specifically.

"The screen was bright and with a nearby Samsung Behold II it was obvious the Incredible had the same 3.7″ AM-OLED screen just like the Nexus One."

I am thinking he was comparing the brightness of the behold (amoled) and comparing the size to the nexus.

More like: "The screen was bright and with a nearby Samsung Behold II it was obvious. The Incredible had the same 3.7″ AM-OLED screen just like the Nexus One."
 
Status
Not open for further replies.
Back
Top Bottom