Quote:
Originally Posted by babijoee
Last time i checked it was no where near ready for end user. Its still being tested and better developed to make flashing easy as flashing a normal winmo rom.
|
I kind of agree with this statement, there are still a lot of little things to iron out...
With that said, the Vogue also still has some issues to iron out, and there's been a NAND available for that device for quite some time now.
At first I agreed that Android on the TP/Fuze was not anywhere near ready for a NAND. Battery life was a big issue, but with these newest builds I'm getting pretty good uptimes without being tied to a charger. Mind you it's not as good as WinMo, but you can't really expect that considering it's running the OS off of an SD card - which to me seems like another good reason to start building a NAND, Android would probably enjoy much better battery life if it was running natively.
So is something else holding it back? We can calibrate the screen, audio seems to be working fairly consistently... I mean GPS would be nice, but I don't think that feature alone would keep devs from building a NAND. Heck, they still don't have the camera sorted out for the Vogue (although they do have GPS and BT, BT audio doesn't work for them either!)
I'm definitely not trying to be a troll, I'm just curious as to what is preventing a NAND, because I don't think where the Android project is on this device would be so bad for the typical "end-user" we have on these forums.
However, if the issue is actually figuring out the best way to flash a NAND to the device, that's a completely different matter. I was under the impression that the project status was holding it back from being converted to a NAND.
So for what it's worth (I'm sure not much :P) I feel Android is ready to be flashed onto our phones. I know I would flash it, I've been using it full-time now for a couple of weeks!
|