it is, with a qwerty keyboard it's gonna be callled the HTC Vision.Originally Posted by JUS3
The HTC Desire looks dope. It's basically the Nexus One, but instead of the trackball, there's a sensor pad. I wish that phone was going to T-MobileOriginally Posted by i3allistic
any android phone coming out for AT&T? my contract is up in nov but i can upgrade in july ...android is really catching my attention ....
posted May 24th 2010 3:47AM
t-mobile has been subsidizing this phone for new contracts since da phone's inception in january for 179.Originally Posted by blackngold1z
is this confirmed?Originally Posted by NostrandAve68
Originally Posted by ninjahood
yo im on da worldstar home screen and all da flash ads at da top are playin, all 4 videos can be seen FROM DA TITLE SCREEN. and play right there..pssh..nothing is seeing
my nexus one right now...nada
i gotta film this and post it here this is epic
son made hype
Naw forreal tho I think ima pass on the Evo and stick with Tmobile and get the Nexus One when they become subsidized at the Tmobile store in a few weeks.
that would be amazing. i haven't heard anything but Ive been on vacation for a week and I usually find info online before work anyway
wasnt that online only though and through google? and also you have to get a plan they chose or something like that?Originally Posted by ninjahood
t-mobile has been subsidizing this phone for new contracts since da phone's inception in january for 179.Originally Posted by blackngold1z
is this confirmed?Originally Posted by NostrandAve68
Originally Posted by ninjahood
yo im on da worldstar home screen and all da flash ads at da top are playin, all 4 videos can be seen FROM DA TITLE SCREEN. and play right there..pssh..nothing is seeing
my nexus one right now...nada
i gotta film this and post it here this is epic
son made hype
Naw forreal tho I think ima pass on the Evo and stick with Tmobile and get the Nexus One when they become subsidized at the Tmobile store in a few weeks.
that would be amazing. i haven't heard anything but Ive been on vacation for a week and I usually find info online before work anyway
Truth. Lookin at HTC's 2010 roadmap, all the good phones have released already for the most part so holdin out for a better Android phone is pointless. I'm tryna wait to see what the Sk Twist looks like but if the N1 starts poppin up in stores, I'm gon make that leap. Hope Walmart gets em so I can save some money
Wasn't the roadmap for the first half of the year.Originally Posted by Dathbgboy
Truth. Lookin at HTC's 2010 roadmap, all the good phones have released already for the most part so holdin out for a better Android phone is pointless. I'm tryna wait to see what the Sk Twist looks like but if the N1 starts poppin up in stores, I'm gon make that leap. Hope Walmart gets em so I can save some money
Cellphones, HD Misc., HD Content, Mobile Handsets, Mobile Software
[h4]How to get Hulu running on Android 2.2, for now[/h4]
By Donald Melanson
Android 2.2 and Flash 10.1. A perfect combination for combination for a little Hulu on the go, right? Not quite, as Hulu has decided to block videos (for legal reasons) when it detects a mobile device, but it turns out there is a surprisingly simple workaround. As Absolutely Android explains, all you have to do is make Hulu think you're using a desktop browser, which can be done simply by entering "about:debug" in the address bar and switching the UAString setting from Android to desktop. The only downside to the trick is that you'll now also get the full desktop version of the Hulu site (and any other site, until you switch it back), and there's a better than decent chance that Hulu will close this loophole before you can finish your first episode of Kojak.
[table][tr][td]
Mashable
Absolutely Android
[/td][/tr][/table]
[table][tr][td]
http://www.absolutelyandroid.com/guide-hulu-on-android-2-2-froyo/
[/td][/tr][/table]
Quote:
[table][tr][td]
Originally Posted by RenegadEEE
Can someone explain in normal language what has been achieved so far? And what are the problems we're facing now?
[/td][/tr][/table]
I'll have a go at that
The Mondrian NBH posted in this thread is a format that HTC uses, that you can consider a "container" like a cup or a box. We know this format fully and can dump and create it at will (NBHImageTool)
The qualcomm snapdragon can be thought of a miniature dual-core computer. It is different from a normal computer that has dual cores in an important way: Each core is assigned it's own block of memory, and runs its own operating system. There is a shared block of memory allowing the 2 operating systems to communicate with each other.
Inside that .nbh container, are some more containers. One is "radio.nb" - inside here is the various software that drives the "second processor". Another is "spl.nb" - this contains the tri-color bootloader that most of you are familiar with as HardSPL. This bootloader has changed considerably for WP7 and it's layout will need to be determined. Another is "unknown-0x0804.nb", as you might guess we don't know what that is yetFinally, there's "os.nb" - the last container. This one has the OS we want to work with (WP7), and really it's not os.nb as that is the format used on WM6, so far all the WP7 ROMs ive seen use the "flash.store.bin" container format. My NBHImageTool currently names the output file incorrectly as os.nb. I will update a future version to check the actual content of the file and name it properly (flash.store.bin)
In order for us to port the OS from one device to another, one basic thing we need to be able to do is "dump" the "flash.store.bin" container format to its components (I did this manually with a hex editor, and posted on post 2 of this thread), and re-build the flash.store.bin from those components (after we've edited them to do the actual "porting")
We don't yet know the flash.store.bin container format, which is the current hurdle i'm working on. Once we are able to easily dump/rebuild that, there are a number of other challenges to meet, such as how we relocate modules to function on another device. Modules are built with a pre-determined memory layout, and each device has a different memory layout. On WM6.x ROMs we have the tool "g'reloc" or "wmreloc" or "platformrebuilder" to handle this for us. With WP7 ROMs the memory layout is entirely different, so a new tool needs to be developed.
We currently don't yet know how the memory layout looks, i've just been going by CE6 documentation on MSDN. If we're lucky not much has changed in that regard, and we'll be able to create a relocation tool based on that documentation.
Anything that has changed since then will need to be reverse engineered. If that is necessary it probably won't be likely until we can get hands on a device running WP7, inject some native code, and figure out the memory layout and other such goodies.
So, assuming we have those things hammered out (we don't yet), we need to make our current device bootloaders able to load the WP7 OS. This would be accomplished using some ARM assembly trickery. This is where JTAG comes in because there's a high probability of bricking and we will be able to obtain debug output from the process to determine where any failures are occuring (and there will be failures!) - another hurdle with this is that it's looking like there is only one JTAG unit capable of supporting the snapdragon at this moment, and it costs upwards of 4x the original donation drive guesstimate, which is far too expensive for this project. I'm currently researching alternatives. It's looking like I will end up having to go with one of the less expensive "home brew" JTAG models and writing my own Snapdragon support into OpenOCD (the open source debugger platform that the "home brew" JTAGgers use) - that is far from a trivial task and i'm not looking forward to it at all
Once that's hammered out, we'll be at a place where the OS itself is loading up. However it is quite likely at that point, some of the drivers will fail to work (hopefully not basic ones such as the kernel, display, etc.) - here we'll have to perform some more trickery to get the drivers functioning properly. One potential problem is that since we will be using our original device's radio.nb, more than likely the protocol the drivers use to communicate with it will be different. This will need to be changed.
Now, all of the above stuff needs to be packaged into a deployment system that's user friendly, and relatively fail-safe (we don't want bricks!)
At that point, it's "done" - not complicated at all, right?
Yeah the i5 is just fine, i built my pc before i5 was even out, also cant go wrong with a SSD or velociraptor, if you do get the velociraptors try to put it on a raid array. Raid 0 for speed.
I'm hearing another device will be out soon with a physical keyboard. I always say this, technology moves so fast, the EVO will most likely not be the top phone out within a year. It won't be garbage, but don't worry if you miss out on it. Also, Android is pushing manufacturers to get off their behind. And to quote one of leaders of Android, what they bring in the future will "blow your mind." If that's the case, I don't mind waiting on something worthy of moving off of this SERO plan ...
anyone?
it says it does erase everything.
