Database Info

Developers of ROMs

Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.

Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.

Agreed! (This text is just to pass 10 char limit)

Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.

but arnt all these builds just different attempts at getting a working 1.5 build?

Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.

well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!

Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.

momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)

harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.

The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?

Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave

I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.

Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.

As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.

momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave

I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.

Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.

Google dropped 2.0 in AOSP!!!

It seems that as of now the new sdk is available for download and so on, that is a great news I can hardly wait to put my hands on a blazing fast 2.0 ROM!!!!!!!!!!! (as soon as someone releases one )
http://developer.android.com/index.html

Everybody that follows Cyanogen on Twitter already knows this man and there's no need for another thread (yea someone already beat you to it)

woo hoo! luckily the dream will be able to handle it

There's already a thread on this. Thanks.

Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.

matt_stang said:
Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.
Click to expand...
Click to collapse
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.

dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
I wouldn't expect anything this weekend.

chaosan said:
woo hoo! luckily the dream will be able to handle it
Click to expand...
Click to collapse
hopefully the dream will be able to run it, it all depends whether or not htc decides to give use the proprietary drivers to have 2.0 working on our phones.
RT @cyrowski
"Eclair won't build for ADP1 or ADP2 out of the box. Will need to wait on vendors for proprietary drivers."
RT @cyanogen
"cyanogen
Probably will start by backporting features- we need new proprietary drivers for our Dream/Magic devices."
====
jbqueru :
@maxisma Unfortunately, the drop doesn't compile for the ADPs
maxisma :
@jbqueru Whats the problem? Just the drivers in the kernel? Hope not more..
jbqueru :
@maxisma Actually, user-space libraries that talk to the various components (especially media-related stuff).
maxisma :
@jbqueru damn Hope @htc will provide support for our already "outdated" devices.. Thanks for your answer
EDIT:
cyanogen
Just booted Eclair on my G1

Pinesal said:
I wouldn't expect anything this weekend.
Click to expand...
Click to collapse
can't rush art....
just be a good boy and wait for the magic to happen

yoshitoshi said:
can't rush art....
just be a good boy and wait for the magic to happen
Click to expand...
Click to collapse
Already been released.
Sorry had to. Someone toss me in the PUN-tentary.

Honestly,
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
How did cyanogen just boot donut on his g1?

Frito37 said:
How did cyanogen just boot donut on his g1?
Click to expand...
Click to collapse
He backported features one by one until an official release of Donut was made. Also, booting is different than fully functional. Fwiw, someone out there actually booted up Android on a Treo 650 recently. Doesn't mean any of the drivers worked properly! Same here - booting is only the first step.

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
That Sony Xperia has the 1700 Mhz band. And it looks sexy as all get out.

Eclair, eclair, eclair, eclair.
Tasting some eclairs now.

coolbho3000 said:
Eclair, eclair, eclair, eclair.
Tasting some eclairs now.
Click to expand...
Click to collapse
Are you really testing it?

dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
Same here since day 1...!!!!!

lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
I don't think you understand Linux then. Linux is about as backward compatible as an OS gets. Can you put Windows on a i386 and expect it to work. No. Linux still boots just fine on a i386 and still runs very decent (Actually, it even runs on a i286). Linux also supports most architectures out there, unlike Windows and Mac. Only OS that supports more I believe is NetBSD.
Open-Android-Alliance wants to replace all proprietary with open source pieces. I don't know if that includes drivers or not. We will see. Actually, I see HTC releasing drivers for 2.0. Just not much after that. I just hope the Linux community can reverse engineer the drivers to create open source version so our phones can keep being updated.
There is no other phone on the market that I would want more right now than the G1. I use *nix for pretty much all my computing needs and having a five row keyboard with all the keys I need in *nix is very important to me.

We will get it working, don't worry

cyanogen said:
We will get it working, don't worry
Click to expand...
Click to collapse
I just might have to buy you a CASE OF BEER!!!!

Google Goggles in Market?

I'm running Fresh 0.6 but Google Goggles is not showing up in it. Anyone else having problems with this?
If you haven't come across it yet, check it out. Very cool visual search app.
http://www.google.com/mobile/goggles/#landmark

It is very likely as with the new Maps, this is only compatible with 2.1 and will not show up in the market for phones with 1.5.
Sorry to break your heart. Google has taken it away from us.

Never Mind
Never mind...just read somewhere that its for 1.6 and up Looks very cool....
Hopefully 2.0/2.1 is just round the corner

Yup.. Here's hoping us Hero users will get an update sometime before next year :|

google goggles
yeah in the feed i read about it in said 1.6+ so cupcake is left out yet again...wow i cant wait for 2.1 to be stable.

Doh! The app seems very cool

Bummer
Yeah I tried to download it too when I saw it on Gizmodo. Seankk what do you mean you can't wait for 2.1 to be stable? Is there a way to get it loaded on our hero now? If so I'd like to play around with it.
Never mind I just read this thread.
http://forum.xda-developers.com/showthread.php?t=593015
Cannot wait for 2.1 on hero btw.

anyone know where i can get the apk, just to try?

This is bull**** ... an updated Maps and Goggles and Favorite Places all happen on the same day - yet we can't use any of them, because we're stuck on 1.5. What the ****!
And I know Eris will get 2.0 before Hero does, because Verizon is way more into Android than Sprint. UGH.

Damnit
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.

Amen, brother.

amen to that too.

5tr4t4 said:
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.
Click to expand...
Click to collapse
Start twitter bombing @sprint and @htc

Amen as well. What good is open source when you have to rely on proprietary code from the handset manufacturers? And time is clearly not of the essence for these guys. It's really disappointing that HTC's flagship phone is taking this long to update. It really feels like they don't give a ****.

Hey, I just found this article and thought I'd post it.
http://htcsource.com/index.php?option=com_content&task=view&id=791&Itemid=50

5tr4t4 said:
Alright, this is getting ridiculous now. I bought a Google phone (it's emblazoned on the back for god's sake!) and can't use two of Google's flagship mobile apps, Navigation and now Goggles. Even when 2.0 arrives, there are sure to be more pointless delays like this in the future.
We have GOT to get off of the "waiting for carrier updates" ride as soon as is humanly possible. This is open source, right? Then why are we waiting and hacking? Let's demand the GPL code from HTC, fork it, get a vanilla 2.0/2.1 community build, and move on. The carriers and manufacturers are clearly not Linux people and should not be allowed to hold back development like this. On my Desktop Linux box I'm updating constantly. Every day there are newer, faster, better things. Waiting weeks for an optimization (or at least for the code to test it out) would seem absurd to any standard Linux user.
So far I've just been contributing ideas/suggestions (many thanks to the may excellent devs on this and other pages!!), but I'm going to set up a development environment here and see what I can do to get started....
Sorry for the rant (not my first on this board, I'm afraid) but my hopes for Android are being dashed day by day. "Open handset" my ass.
Click to expand...
Click to collapse
Just an FYI many of the devs here are working on a version of the 2.1 Eclair or Flan update. They have gotten the system dump from a 2.1 GSM phone and are working on getting it ported to CDMA. So check that thread and try not to reinvent the wheel. Seems like the one thing they cannot get working is the Data. Text and Calls work, but useless without Data. From what i have gathered all that is very specific to sprint and is rolled into the kernel. Which we don't have yet, and without ground up building one we are kind of at a standstill.

Android on HTC Fuze (Raphael 110) - Crashes and Questions

**Let me begin by saying that, as a newcomer to the forum, I apologize of this has been posted in the wrong place. I considered posting it in various HTC Fuze specific or Android subforums, but decided on this one as it is "(Android) Software...General". If there's a problem, please notify me and move this thread accordingly. I have no intention of creating problems.**
I've been doing a great deal of experimenting with Android on my Fuze, and (after trying XDAndroid 2.0.1) am trying to get 1.6 (Donut) working.
I've been using the (1.6) build on connect-utb.com. My phone is an HTC Fuze, or a Raphael 110. Apparently, it (the build) was last made/modified on 11/22/09, and (quoting from the download/version description):
"This Android package is based on the Current phhusson/leobaillard's release from 22.11.2009."
The problem I'm having is that, among other things, 1.6 seems to be VERY unstable.
A program (google maps/voice/android keyboard/marketplace/etc...) seems to crash every minute. I've become rather exasperated with it, and, after multiple manual restarts and re-installations, I've come to the oasis of mobile phone knowledge asking for assistance.
I'm confused (regarding 1.6), as this is supposedly the more stable build. I shied away from XDAndroid 2.0.1 due to the small bits of UI lag I was experiencing. 1.6 attracted me due to the claim that it's much faster (as well as having a couple more features working).
Can somebody give me some advice in regards to whether I might be doing something wrong? I'm sure I'm using the correct startup.txt, and don't quite know what the problem could be.
Granted, if somebody also has ways of optimizing XDAndroid 2.0.1, or providing an optimized build, I'd welcome that alternative.
In short, I'm looking for an Android build that will run very fast, and with exceptional stability, on a Raphael 110.
Thank you in advance.

Get the latest builds from here: http://forum.xda-developers.com/showthread.php?t=601751

Thank you for pointing me in that direction, JR_de, but, as I understand it, that thread pertains solely to Android 2.0.1 Eclair.
When I used that version, I found the graphics and response times (overall system speed) were somewhat laggy. Is that normal (for my phone)? Is there a way to optimize it?
I know that the HTC Fuze (Raphael) has a 528Mhz processor, as well as 288Mbs of RAM, which is on par with the HTC Magic - another Android phone.
Can you please provide some insight as to whether I could either 1)optimize Eclair or 2) download a stable 1.6?
Thanks again.

.
xyrovice said:
Thank you for pointing me in that direction, JR_de, but, as I understand it, that thread pertains solely to Android 2.0.1 Eclair.
When I used that version, I found the graphics and response times (overall system speed) were somewhat laggy. Is that normal (for my phone)? Is there a way to optimize it?
I know that the HTC Fuze (Raphael) has a 528Mhz processor, as well as 288Mbs of RAM, which is on par with the HTC Magic - another Android phone.
Can you please provide some insight as to whether I could either 1)optimize Eclair or 2) download a stable 1.6?
Thanks again.
Click to expand...
Click to collapse
try agian when its update almost everytime its improved speed wise
some have said that the febuary 22 build is faster

jul644 said:
try agian when its update almost everytime its improved speed wise
some have said that the febuary 22 build is faster
Click to expand...
Click to collapse
Would that also include every build thereafter, or just the one from February 22nd?? I downloaded and am using the March 1st build in the hopes that, as it's the most up to date, it will be the 'best'.
Also, I saw something about enabling 3D in Windows Mobile (before launching Haret, I assume). It said you could do this by launching TouchFlo3D.
I booted back into WinMo, launched TF3D, and am now going to see if it's any faster.
Thank you both for your help so far.

You might have more luck posting your questions on the XDAndroid forum. I too would definitely recommend using the later Eclair versions, I remember a massive performance leap around two months ago when that version number shot up. The Eclair builds will obviously be updated more regularly too.
The graphics lag is completely normal for your Fuze. The reason isn't a hardware problem, it's because the drivers for the graphics chip and just about everyting else in your WM phone need rewriting for Android, and they haven't been optimised yet, hence them not running as smoothly as on phones whose drivers have been written specifically for Android by HTC themselves.
My Touch Pro would require a soft reset every ~5 minutes with the XDAndroid 1.6 builds, but I could probably use it for 24 hours now on Eclair without it crashing.
If you're still unsure, why not just give Eclair a go? You can always switch back if you find it slower. As for your search for a build "that will run very fast, and with exceptional stability, on a Raphael 110", I'm afraid that the development just hasn't got there yet, especially for the stability. Relative to Windows, it's still miles off for that.

ben_duder said:
You might have more luck posting your questions on the XDAndroid forum. I too would definitely recommend using the later Eclair versions, I remember a massive performance leap around two months ago when that version number shot up. The Eclair builds will obviously be updated more regularly too.
The graphics lag is completely normal for your Fuze. The reason isn't a hardware problem, it's because the drivers for the graphics chip and just about everyting else in your WM phone need rewriting for Android, and they haven't been optimised yet, hence them not running as smoothly as on phones whose drivers have been written specifically for Android by HTC themselves.
My Touch Pro would require a soft reset every ~5 minutes with the XDAndroid 1.6 builds, but I could probably use it for 24 hours now on Eclair without it crashing.
If you're still unsure, why not just give Eclair a go? You can always switch back if you find it slower. As for your search for a build "that will run very fast, and with exceptional stability, on a Raphael 110", I'm afraid that the development just hasn't got there yet, especially for the stability. Relative to Windows, it's still miles off for that.
Click to expand...
Click to collapse
Thanks for taking the time to write this.
Since my last post, I have indeed given Eclair a second chance, and find it performing a bit better than I remember. Granted, I'm using the 'standard' home screen, not the Home++ one (if that makes any difference).
Also, thanks for clarifying that it's the graphics drivers that are hindering performance. That gives me hope, seeing as it's (more or less) a software issue that can, and hopefully will be, fixed.
While I would love to see the OS become faster one my phone, right now my biggest issue lies in battery life. Past that, it's camera capability, and then GPS. I'm also fiddling with a 3g/data issue, but I'm sure I'll work that out. I have never used bluetooth for the years that I've owned a cell phone, so I'm not too worried about that.
Honestly, though, I've been using Eclair for the past few days with very few reboots. I've never has any major crashes (usually only one when I boot into android and it says the latin keyboard process has crashed), and thus haven't had to reboot out of "necessity."
In short, I have given it a second chance, and am very thankful for doing so.

I wouldn't worry too much about battery life, GPS and the camera as they're the most commonly asked about things on the thread. The developers are well aware of how many users want these working, and I'm sure that if the project continues to be updated, these things (particuarly battery life) will be prioritised.
I asked svetius to open a board for Raphael Android Development, and he has very kindly done so. In the future, you'll probably get more replies here.

This is very, very much appreciated.
Thanks for your time, as well as the link (and your efforts in regards to the creation of that board).

does anyone have a good startup.txt file for their raphael
i need one because my raph has android preformance issues.
thanks

This is ridiculous...

Anyone still on 2.1 is officially obsolete. Google has released a ton of new features for froyo and gingerbread users. Including google instant, new gmail app, and other things.
Which leaves 2.1 users with old software never to be upgraded again.
I still haven't flashed (due to warranty issues) but even if I did I would be upset because it still is based on buggy pre-release software.
Based on the epic 4g leak the froyo should be version 2.2.1 so new roms would be 2.2.1 instead of buggy 2.2
Why doesn't samsung care about their customers!

Yea, I share your sentiments. I tried most of the 2.2 leak ROMs, but most had troubles. The list of apps that don't work on 2.1 and below is growing. I wonder if Google Maps 5 will be the same way.

I really thinking about just buying an unlocked nexus s but then i realize its still samsung!!!
I returned a samsung tv i bought for my family for christmas because they suck so much ;D

The more I read about this (and the GPS malfunction), the more I think that when my Captivate arrives tomorrow I may just take it into an AT$T store and demand a refund and contract cancellation.

What we need is a Samsung Customer Service number we can start calling to voice our opinions. Any have a good Samsung number for this or a similar purpose?

Yes more than half of android devices are "obsolete"...

Return it? Because your too lazy to flash your phone with functional software instead of the junk Samsung and att gave us? I've been rocking the beta cm 6.1 for quite awhile and blows the doors off any 2.1 variant that was out there.....and as far as voiding your warranty its almost impossible to brick these phones so its completely easy to flash back to an out of the box state. So quit whining. This is what makes android so great. Take a phone with amazing hardware with crappy software and put amazing software on it
Sent from my SAMSUNG-GT-I9000 using XDA App

For one, I'm not lazy or whining. I shouldn't have to flash my phone to get basic functionality out of it. The GPS should work without my having to invest in searching through a myriad of unauthorized solutions and risk not only voiding my warranty, but bricking my phone. If I wanted to put this much effort into making a phone work I would have stuck with WinMo 6.5 and my Tilt 2, which I know inside and out already. I moved to Android hoping I'd no longer have to spend so much time dicking around with my phone just to get things to work. You know, the whole "Droid Does" marketing ploy? The main reason I agreed to buy this phone was because I read on several different sites where Samsung said they were definitely going to update it to Froyo. I understand that their timetable may be off, but they should at least keep their promise. Is that too much to ask or expect?

Samsung promised Froyo by the end of the year for the US Market. They still have a 20 days. Their stance has not changed, so I don't see what anyone has to complain about.
As for GPS mine works as good as the one on my Bravo - my Tracks, Turn by Turn are the same. If your GPS has problems, take it back. If you try multiple phones and still have a problem, then make them switch you to another phone.

everyone knows they won't make the end of december date

It's not that I don't want to try custom ROMs. However, all the custom ROMs are built on leaked (and often buggy) Froyo ROMs. The sooner AT&T releases an official release Froyo ROM, the sooner we can get a stable (or more stable) custom Froyo ROM....hopefully they release the source code too. There's code in the custom ROMs that comes from all sorts of other ROMs lol

Ditto^^^ Well, according to Mr. Smalls, we're just lazy, whiny jerks with no valid excuse for not wanting to use a custom ROM on our phones.

emuneee said:
It's not that I don't want to try custom ROMs. However, all the custom ROMs are built on leaked (and often buggy) Froyo ROMs. The sooner AT&T releases an official release Froyo ROM, the sooner we can get a stable (or more stable) custom Froyo ROM....hopefully they release the source code too. There's code in the custom ROMs that comes from all sorts of other ROMs lol
Click to expand...
Click to collapse
try axura.. VERY stable, fast, practical rom with good themes. its a work of art. been rocking it with very minimal issue (less issues compared to stock).

Miami_Son said:
For one, I'm not lazy or whining. I shouldn't have to flash my phone to get basic functionality out of it. The GPS should work without my having to invest in searching through a myriad of unauthorized solutions and risk not only voiding my warranty, but bricking my phone. If I wanted to put this much effort into making a phone work I would have stuck with WinMo 6.5 and my Tilt 2, which I know inside and out already. I moved to Android hoping I'd no longer have to spend so much time dicking around with my phone just to get things to work. You know, the whole "Droid Does" marketing ploy? The main reason I agreed to buy this phone was because I read on several different sites where Samsung said they were definitely going to update it to Froyo. I understand that their timetable may be off, but they should at least keep their promise. Is that too much to ask or expect?
Click to expand...
Click to collapse
Am I correct that you don't even have your device as you're typing that?! Try it first..a lot of the stuff you read isn't what you will experience. I.E.: my gps has worked a charm since I picked mine up in mid October..it's an excellent device. I've had a Samsung DLP for more than 2 years and it works flawlessly. People like to rant..find out for yourself for chrissake. It's nice to be happy with a cell device for the first time in awhile for me..only complaint is att dragging heels on 2.2. I'm too busy and old (55) to have the energy to do all that stuff that many do..but it's also nice to know that if I get tired of waiting and get a wild hair, I'll root and flash when I'm good and ready. Meantime I think the Captivate is a great companion

From what I've heard, I think that it might be the carriers that are delaying the update. Don't know if this is true or not but I kinda doubt this is Samsung's fault.

@fldude, Thanks for the encouragement. I used to love fiddling with my WinMo phones and I enjoyed modding my Tilt 2 to where it runs great and does (almost) all I ask of it. I'd still be using it if WinMo wasn't a dead platform and the thing wasn't so laggy. That saidI was hoping the switch to Android would mean I finallly would have a phone that I could tinker with if I wanted to, but didn't HAVE to, like WinMo. I guess reading through these forums exposes one mostly to the negative since most people only post when having problems. I brushed most of it aside, but the GPS issue really stood out because I use GPS-enabled apps a lot and it works so well on my Tilt 2. I can't wait for the Cap to get here tomorrow so I can start playing with it. Thanks to running XDAndroid on my Tilt 2 I already have some idea of what to expect and how to use it.
I will say this, reading about rooting and flashing of Android, kernel this and apk that is a lot more intimidating than working with WinMo. I never hesitated to edit my registry, but modding Android sounds pretty scary.
By the way, does fl mean you're a fellow H-D rider?

alphadog00 said:
Samsung promised Froyo by the end of the year for the US Market. They still have a 20 days. Their stance has not changed, so I don't see what anyone has to complain about.
As for GPS mine works as good as the one on my Bravo - my Tracks, Turn by Turn are the same. If your GPS has problems, take it back. If you try multiple phones and still have a problem, then make them switch you to another phone.
Click to expand...
Click to collapse
They were previously quoted saying by the end of November. There was that whole JH7 fiasco. And your argument doesn't change what he was saying. His whole point was that he shouldn't have to **** around to make it work. It just should.

david717;971 His whole point was that he shouldn't have to **** around to make it work. It just should.[/QUOTE said:
Ummm, I'm stock, never rooted, make phone calls, email, navigate with gps, surf the web, play games, usw.. How is this not a working phone? By my calculations this phone does "just work" and has since I pulled it out of its box in July.
I too am waiting for, now, v2.2.1...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse

Before I bought mine I knee of the GPS issues and swwvthat a fix was coming. It still is. Besides the GPS my phone just works. Texting browsing g music video all just worked email too. Running the froyo leak my phone now completely 100% percent works. I'm excited to see how much more stable the official release will be.
Sent from my SAMSUNG-SGH-I897 using XDA App

Also Frustrated
I have been following the forums regarding the so called Froyo release and I have to say that I am rather frustrated as well. I actually called AT&T last week to complain about the delay with Froyo with Gingerbread's release within a few weeks. Not to mention Honeycomb on the horizon.
In speaking with one of the techs he also shared his frustrations and was hoping that it would be released in early January. I told him that it was understood that it would be release at the end of the year and he confirmed that same understanding. However his sources revealed that it is now for early January. Let's hope this is true, but as you all know we have been given so many empty promises.
Furthermore,I read an article that Samsung is undecided whether to release Gingerbread for the Galaxy devices. For a product that has been so popular and successful, what are they thinking? Or maybe they are not!!
Either way my fingers and toes are crossed for Froyo for now...