2/26/09 Conflippers UC ROM (5.2.21018 Build 21018)

[w0rdie]

Since I'm not unhappy with my stock Alltel rom I think I might wait until the next build of this ROM... any tough ETA con?

[conflipper]

Originally Posted by w0rdie

Since I'm not unhappy with my stock Alltel rom I think I might wait until the next build of this ROM... any tough ETA con?

soon, next day or two. Updated Dshow graphics, Updated Opera, tweaks to registry, tweaks to gyrator.

also have a generic version.

[oolimee]

Originally Posted by conflipper

soon, next day or two. Updated Dshow graphics, Updated Opera, tweaks to registry, tweaks to gyrator.

also have a generic version.

Awesome! Can't wait. It's running real smooth, and battery life is excellent.

One suggestion is adding no2chem's 1% battery drivers and FInixNOverBattery cab..

You mentioned dshow graphics. Is that the same as D3D drivers that Juicy updated a while back? I remember that made the TF3D scrolling so much smoother. Not that your scrolling's slow, but I've seen faster.. Just 2 cents

[julidelara]

I dont want to sound dumb but how do you hard reset the diamond?

[oolimee]

Originally Posted by julidelara

I dont want to sound dumb but how do you hard reset the diamond?

you need 2 people to do it.

Hold Power + Vol Down + Enter (round button) buttons together. And press reset button with stylus.

Release the reset button, but keep holding the other 3 buttons. Then follow the prompt

[conflipper]

Originally Posted by oolimee

Awesome! Can't wait. It's running real smooth, and battery life is excellent.

One suggestion is adding no2chem's 1% battery drivers and FInixNOverBattery cab..

You mentioned dshow graphics. Is that the same as D3D drivers that Juicy updated a while back? I remember that made the TF3D scrolling so much smoother. Not that your scrolling's slow, but I've seen faster.. Just 2 cents

I will look into no2chem battery. Do you have a link for the FinixNoverBattery.cab.

I am testing out a new system and build now. 20757. Having a hard time with the XIP, but if i can not get it by tomw, then i will not worry about it, and just do some smaller updated.

I will look into Juicy d3d drivers update.

Thanks for your input. the more you input the better ideas i have on what to update. So keep it up.

[Calkulin]

Originally Posted by conflipper

I am testing out a new system and build now. 20757. Having a hard time with the XIP, but if i can not get it by tomw, then i will not worry about it, and just do some smaller updated.

20757 has the same problems 20755 has, so stick with 20924 for now, once the xip is ported, it should be a very stable and fast OS


On a side note, did you know the title of this thread is wrong? It says 20775 when it should read 20757

[conflipper]

i am working on the XIP, that has been my problem, I have nbmerge crashing on my, so i am unable to get it all going, but i spent a good part of the day porting it over, now i cant get it tested because i am unable to recontruct the flash file for the base.

[Calkulin]

If you were porting it over, why didn't you do 20924 instead?

[conflipper]

20757 makes a better base then 20924. true 20924 is fast, i like the better base. take a look at the version of each build in the system folder.

Also if you look at the Facebookproxy.dll, it is calling back to the CoreDLL.DLL from the 20757 xip, so i am thinking we might need a full xip port of 20757 to make the facebook work. that is what it looks like. if you look at UDK post on XDA, he has well used the same XIP, and he has it working. so for me that is the only thing that makes sense.

So i was going to try that. I can maybe try 20924 sometime, but if i cant get nbmerge to work then i have no way to test at all.