Database Info

HTC/Sapphire Exchange Mail Application

Is it possible to port the Mail/Exchange.apk that's on the "Magic" to the G1?
Not a developer so don't know figured i'd ask
thanks

saul972 said:
Is it possible to port the Mail/Exchange.apk that's on the "Magic" to the G1?
Not a developer so don't know figured i'd ask
thanks
Click to expand...
Click to collapse
It's "possible" but the answer is more detailed then that. Do some research on Android packaging. I good start is by looking what JF has accomplished. If this is too much for you than I suggest you sit back silently and let the hackers play.

Has anyone looked into this at all?

Here's an idiea, run a Haykuro build.

CBowley said:
Here's an idiea, run a Haykuro build.
Click to expand...
Click to collapse
Maybe I would rather run my current JF build instead of go up to the Magic build?
I have tried Haykuro's builds and enjoy them, but there are still some bugs out there and I honestly don't really feel like messing with them.
I was just wondering if anyone has looked into this at all.

That's fun, but I find the bugs in 5.0G to be very minimum

CBowley said:
That's fun, but I find the bugs in 5.0G to be very minimum
Click to expand...
Click to collapse
5.0G doesn't have HTC's Exchange does it?

No, G builds do not have Exchange Sync

CBowley said:
That's fun, but I find the bugs in 5.0G to be very minimum
Click to expand...
Click to collapse
ghoonk said:
No, G builds do not have Exchange Sync
Click to expand...
Click to collapse
Owned! Also, I agree that having the Exchange Sync ported to at least the G builds would be AWESOME. Then again, it'd also probably be fairly difficult since it seems to be built into the system since it shows up under the main settings menu. Would probably require haykuro himself to actually pull this one off.

No g does not, I am sorry for the confusion, but h is also not bad enough where you couldn't use it on a normal basis, as I used it for a couple days as my main device...

I agree. H is stable. I just don't want to commit all the time to redoing the phone just to have cupcake come out on Tmo and me prefer that and have to do the whole process over again.
Other than exchange, there isn't enough on the H and G builds to make it worth flashing for me. That's why I would love to be able to install the exchange support as stand alone.

Minker17 said:
Other than exchange, there isn't enough on the H and G builds to make it worth flashing for me. That's why I would love to be able to install the exchange support as stand alone.
Click to expand...
Click to collapse
Are you joking? There's loads of good reasons to move to the H build over the standard JF build.
Virtual Keyboard throughout
Proper cut/paste
Better battery life
Faster overall performance
New widgets (music, calendar)
Camcorder (for those intimate moments )
HTC Dialer (this is much better than the stock Google one)
Better looking throughout
Stereo Bluetooth (omg this is awesome)
These all rock. The exchange support will come I hope. That's really the only major advantage of winmob right now for professionals (Even though winmob is crap).
I'm flashing mine almost daily right now and can get back to full install in about 15 minutes (trust me, i've done it enough times to do it quick). As soon as the exchange app works I'll stop flashing all the time and just flash when there are important bug fixes or the next coolest thing comes along.
Long live android

clarkee said:
Are you joking? There's loads of good reasons to move to the H build over the standard JF build.
Virtual Keyboard throughout
Proper cut/paste
Better battery life
Faster overall performance
New widgets (music, calendar)
Camcorder (for those intimate moments )
HTC Dialer (this is much better than the stock Google one)
Better looking throughout
Stereo Bluetooth (omg this is awesome)
These all rock. The exchange support will come I hope. That's really the only major advantage of winmob right now for professionals (Even though winmob is crap).
I'm flashing mine almost daily right now and can get back to full install in about 15 minutes (trust me, i've done it enough times to do it quick). As soon as the exchange app works I'll stop flashing all the time and just flash when there are important bug fixes or the next coolest thing comes along.
Long live android
Click to expand...
Click to collapse
I agree, Magic is oh so magic. It's basically cupcake, all it needs is flash . Oh and 15 mins? Pff ameature... jk I flash mine almost once a day as well, still can't decide between g and h, plus once in a while I'll jump back to jf for themes, then miss the camcorder, or soft keyboard. Oh boy this device is amazing. Really is a dream..... come true.

clarkee said:
Are you joking? There's loads of good reasons to move to the H build over the standard JF build.
Virtual Keyboard throughout
Proper cut/paste
Better battery life
Faster overall performance
New widgets (music, calendar)
Camcorder (for those intimate moments )
HTC Dialer (this is much better than the stock Google one)
Better looking throughout
Stereo Bluetooth (omg this is awesome)
These all rock. The exchange support will come I hope. That's really the only major advantage of winmob right now for professionals (Even though winmob is crap).
I'm flashing mine almost daily right now and can get back to full install in about 15 minutes (trust me, i've done it enough times to do it quick). As soon as the exchange app works I'll stop flashing all the time and just flash when there are important bug fixes or the next coolest thing comes along.
Long live android
Click to expand...
Click to collapse
this is the truth....
**********
but exchange support does work...
had to set mine up over wifi, but it worked..

clarkee said:
Are you joking? There's loads of good reasons to move to the H build over the standard JF build.
....
I'm flashing mine almost daily right now and can get back to full install in about 15 minutes (trust me, i've done it enough times to do it quick). As soon as the exchange app works I'll stop flashing all the time and just flash when there are important bug fixes or the next coolest thing comes along.
Long live android
Click to expand...
Click to collapse
How do you do that? I need at least half an hour to set-up the whole device [including installing all the programs..]
Or do you have all your programs on SD [and they dont need installing then?]?

Minker17 said:
That's why I would love to be able to install the exchange support as stand alone.
Click to expand...
Click to collapse
It is emminently possible (probable even) that Exchange support requires API support that isn't available in builds prior to Cupcake. I'm not saying that is definitely the case of course, but I really don't see any developer being particularly interested in checking it out in the older builds when there is new stuff to be played with unless they specifically want it themselves. YMMV of course!
Regards,
Dave

How did people do exchange? I tried and get account cant be created. Im not trying to create an account! Is there any trick to it?

froggymike911 said:
How did people do exchange? I tried and get account cant be created. Im not trying to create an account! Is there any trick to it?
Click to expand...
Click to collapse
There was no trick to it when I used it. I kept reading where people were saying it doesn't work, but I tried it anyway...
I had it up and running in just a couple of minutes, no trouble at all. I was connecting to an Exchange 2007 server.
Another option, for now, is to use the Moxier Mail beta. Right now it's free, so until the Magic ROM bugs get worked out (MMS not working for no reason, microphone too sensitive to background noise) I'm using that for my Exchange needs. It works just as flawlessly as the built-in support in the Magic ROM, so far.

I'm currently getting my work email using POP3 access. It works and I get my emails, but I have one gripe. The phone never notifies me when I have email, I have to open HTC Mail and to find out. I have Mail Notifications on, as well as Vibrate and Sound...Anyone having similar issues?

froggymike911 said:
How did people do exchange? I tried and get account cant be created. Im not trying to create an account! Is there any trick to it?
Click to expand...
Click to collapse
I got the same problems as you. I have tried and tried but keep getting authentication errors saying my username and password arent correct but I know they are correct. I think it might be that my employer uses exchange 2003 and maybe the activesync/exchange cant use exchange2003. I dunno though, just a guess.
I will use touchdown in the meantime.

Vote for the Magic port you prefer!

Based on the builds (available here: http://forum.xda-developers.com/showthread.php?t=498026) which would you guys like me to continue development on for 5.0 ?
Some food for thought: 4.5 is stable, and I can most likely port aesthetics over from 4.0(4.9) to 4.5.
The pro's and con's of each build thus far:
4.0: Stable, no google apps, no wifi/bluetooth, inverted camera. made by HTC.
4.5: Stable, google apps, no wifi/bluetooth, inverted camera, older cupcake build than the HTC one. made by Google. (i believe.)
4.9: Rather unstable, google apps (slightly buggy, and no maps), no wifi/bluetooth, inverted camera, same build as 4.0. This build was a "i'm-not-sitting-on-my-ass" build for those of you who were complaining
Which one should dominate to 5.0? (5.0 will mainly be wifi/bluetooth fixes and some other minor fixes such as keyboard stuff)
Quick edit:
Voting for 4.0 indicates you do not need Google apps, and instead want a stable phone (almost identical to the ADP builds).
EDIT 2:
I will begin development on 5.0 on Thursday. This will give you 2 days (today and tomorrow) to vote, and gives me time to rest ;P
EDIT 3:
Code:
(6:21:09 PM) **removed for privacy**: hey man, I voted 4.5. I'm a form follows function kinda guy, but are you able to meld the looks of the htc build with the function of the google build?
(6:21:27 PM) haykur0: yea most of the stuff i can port over
(6:21:45 PM) haykur0: stuff like the dialer and **** won't be able to be ported (i think) but 5.0 will be more concentrated on bug fixes
EDIT 4:
WIFI / BLUETOOTH HAS BEEN FIXED IN ALL THE BUILDS.
EDIT 5:
At the time of my arrival on todays date (April 02, 2009 @ 3:42 PM [gmt-5]) the current count is:
4.0 - 15 (no google apps)
4.5 - 99 (google apps, older build)
4.9 - 117 (google apps, newer build)
The winner is 4.9.
My development over the next few days will be based on 4.9 (keep up with it on twitter, and the occasional forum post [which will also be on twitter]).
Thank you everyone for your interest.
I'd also like to mention that this does not mean my development with 4.5 will cease. This was just to help with priority.
It seems the community would prefer to have google apps on the newer build (which makes sense) so it shall be my goal for this week and, if need be, the following.
I will have more information later tonight (i have to go to work today, sorry guys.)

4. i love the htc feel of 4 and have been rolling with that one since release

before i vote, what exactly would be the major differences between version 4.9 becoming 5.0 and 4.5 (with ported aesthetics) becoming 5.0?
atm i would vote for 4.5 because it's stable, but the Google OS sucks compared to the HTC one. It looks so much better
i think you should decide ultimatly, it's you who's put in all this hard work and effort. We've all just been mashing the refresh button for about a week hoping for an update
edit: that being said, i don't think 4 should dominate, purely because a lot of people are going to want/need google apps (myself included) as this phone is, after all, a google phone.

I want Google apps, Exchange, a vk and the sexy sms front end from 4.9. What do I vote for?

I voted for 4.5 assuming you can port the aesthetics from 4.9

4.5 all the way............
I voted 4.5. everything we need, nothing we dont. Plus its much faster and more stable than the htc build, more applications seem to work with it from the market also. I do like some parts of the htc build, like the dialer, but considering it wont work with sync we wont get it anyway.
PS I spoke with haykuro, if 4.5 wins, he'll port most of the looks from the htc build (4.0, 4.9) so its a win win.

How are people voting for 4.9 when it doesn't even have maps?????

My suggestion:
Don't use nummers, based on 4.0,4.5,4.9 because this is psychologically not that good, I think some people will choose 4.9 only because they think 4.9 is better than 4.0...
this is not an offense to you or the community, just my thoughts...

I say, 4.5 with a 5.0 spin on it..

momentarylapseofreason said:
How are people voting for 4.9 when it doesn't even have maps?????
Click to expand...
Click to collapse
because i have Big Planet which works beautifully.
Big Planet > Google Maps
A mixture of all 3 would be absolutly perfect, but that's probably asking a little too much lol

momentarylapseofreason said:
How are people voting for 4.9 when it doesn't even have maps?????
Click to expand...
Click to collapse
It will be included in 5.0 most likely (at least that will be my attempt if 4.9 wins.)

haykuro said:
It will be included in 5.0 most likely (at least that will be my attempt if 4.9 wins.)
Click to expand...
Click to collapse
wont 4.5 and 4.9 be basically the same when you've finished with them?

Meltus said:
wont 4.5 and 4.9 be basically the same when you've finished with them?
Click to expand...
Click to collapse
No. One is based on HTC's build (a newer cupcake build).

haykuro said:
No. One is based on HTC's build (a newer cupcake build).
Click to expand...
Click to collapse
my only concern is the virtual keyboard. the 4.9 HTC version is much better then the 4.5 google version. when you say you can "port the aesthetics" can you port the vk from the htc build as well?

haykuro said:
No. One is based on HTC's build (a newer cupcake build).
Click to expand...
Click to collapse
aesthetics aside though what are the major differences? assuming they will both have google apps etc.
also when the 'looks' are ported over from the 4.9 build, will that also include the keyboard? (or can this not be ported across like the dialer?)
wouldn't the 4.9 be better anyway if it's an updated cupcake build?
sorry for all the damn stupid questions, i bet you're sick of them by now ><

A2DP Profile is important to me.
I voted for 4.9, but only because I like the aesthetics, and really want the A2DP bluetooth profile. If it is just as easy to get the look ported to 4.5 and get A2DP working in it, then I am all for that.
As a side note, I am sure that theme developers will create themes that look even better then what HTC put out, if that is worth considering. Really, the technical hurdles should be the top priority in my opinion.
Cheers, and thanks for all of your hard work!

Well since you asked
1. Above all the build should be 100% stable. No bootloops and no more crashes that a vanilla system gets.
2. Google apps, or at least the market.
3. The look of 4.0 may be acheivable by theme makers so is not vitale to the 5.0 build, but would be a bonus.
4. Working headphone socket, wifi and bluetooth at least to vanilla g1 standard.

fochizel2000 said:
I voted for 4.9, but only because I like the aesthetics, and really want the A2DP bluetooth profile. If it is just as easy to get the look ported to 4.5 and get A2DP working in it, then I am all for that.
As a side note, I am sure that theme developers will create themes that look even better then what HTC put out, if that is worth considering. Really, the technical hurdles should be the top priority in my opinion.
Cheers, and thanks for all of your hard work!
Click to expand...
Click to collapse
Well said. Function before form.
Google Apps/Sync
VK
Widgets
EXCHANGE
I could give a rats ass what it looks like.

i guess i will have to wait until the release of 5.0. i tried 4.0 its a little buggy/no google apps; 4.9 is buggy as well/no wifi however i heave not tried 4.5. speaking of 4.5, does all google apps working besides wifi? and will i have to update my radio as well unlike 4.9 which includes everything right?

i would hate for you to think you could port the aesthetics over and then you end up not being able to. But if you can port the 4.0/4.9 aesthetics over to 4.5 for sure, then 4.5 sounds good to me. i voted 4.9 though.

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.

Is anyone going to make custom rooted builds of the official T-Mobile 1.5 release?

Just wondering. The reason I ask if for the IM app, not myFaves. I know there are other IM apps out there, but none of them work as well (reliability-wise) and are as simple as the stock IM app, especially when you compare it to the complicated apps that try to use multiple IM clients. Meebo is the best one I've used so far, but I still have issues with that one. Unless someone is working on getting that to work for ADP1.5?

someone is definitely going to make one when we get our hands on the official update.zip
I just can't believe it's taking this long for T-mobile to push the updates (or are then even doing it on a large scale?)

On official update.zip by T-Mobile is already aviable. But the problem in my sight is, that this update.zip is only including patches, and not the full Update. So it would take a lot more time.

^
What he said.
I'm sticking to my good ol Android Open Source based builds with a touch of ADP1.5
So much more possible that way.

[Think Tank] Eclair video codecs issue ...

So I've been looking at the video codecs issue that blocks YouTube HD and video recording on the Dream. Seems there are two underlying issues, libsgl from donut was merged into a new library, and that theres an API break in libhardware.
On the first issue, its fairly easy to build donut's libsgl.so on eclair with some minor changes to source to get it, build it, and it seems that it works properly (as far as I can tell, the OpenGL 3D interface it binds to has had a stable API). I don't have a strong test case to use it on.
The second problem is more interesting. It seems to me that the problem with the API break is that Qualcomm is using enum's in a way that is absolutely stupid, and added new numbers that broke the magic numbers copybit needs. This causes a set of copybit failures when blitting stuff to the screen. Rebuilding the proprietary libraries would fix the problem, but as we only have libraries built against 1.6, this obviously won't work, so I'm seeing if theres a better solution we can use to solve this problem. Any ideas welcome.

NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.

Noting is impossible
jcarrz1 said:
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Click to expand...
Click to collapse
Camera didn't work but now it does. Youtube will work 100% very soon

Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....

if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)

smackdown85146 said:
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
Click to expand...
Click to collapse
In theory, it would allow any opengl call to be handled on the GPU. Not only would the livewallpaper speed up, but you'd have more available CPU time for other operations.
The idea is sound, the tricky part is making them efficient enough to actually be a net benefit. It could decent stopgap until new drivers are released.

????-????
So your saying that the first eclair roms where 1.6 with 2.0 skins?

llxll0m3g4llxll said:
So your saying that the first eclair roms where 1.6 with 2.0 skins?
Click to expand...
Click to collapse
No, not entirely...when the Eclair Roms roms were first being made in the beginning Devs didnt have the drivers for the camera. But, thanks to NCommander we do now =)

Android G1 2.0 Update
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.

pinkolin said:
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
Click to expand...
Click to collapse
Isn't january ending... tomorrow?

vincom2 said:
Isn't january ending... tomorrow?
Click to expand...
Click to collapse
yeah, my senses tell me that it is

Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.

Eh would probably be too lazy to go back to stock anyways, will just have to wait for those video drivers =)

pinkolin said:
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Click to expand...
Click to collapse
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.

shawe_ewahs said:
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
Click to expand...
Click to collapse
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?

olearyp said:
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
Click to expand...
Click to collapse
Its probably the default rom that comes with the phone.

How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?

menace said:
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
Click to expand...
Click to collapse
yup with the 2.1 upgrade ur g1 can take 10mp pics

bakgwailo said:
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
Click to expand...
Click to collapse
Sounds like ndiswrapper for linux

gregnotcraig said:
Sounds like ndiswrapper for linux
Click to expand...
Click to collapse
doesnt it though