12.19 3d package with better performance for testing

[[ACL]]

Originally Posted by friedmjb

FPS2D results, on FRX03, OC'd to 700Mhz: 19 FPS after about 3 minutes of running

Does FPS2D really measure anything having to do with the HW3D driver?

yes and no. Some 2D can be accelerated using the gpu. But the point of the test is to see if the frambuffer can even handle a higher frame-rate. Answer is yes, im doing 30 right now and hopefully we can do more.

[friedmjb]

What do I need to do to get to 30? Do I have to switch to the FRX83 version, or are you getting 30 on a custom build that you compiled yourself?

[manekineko]

Originally Posted by friedmjb

What do I need to do to get to 30? Do I have to switch to the FRX83 version, or are you getting 30 on a custom build that you compiled yourself?

He's the main developer for NAND development, and he's getting 30 on the NAND fork that is flashed into the ROM.

He mentioned before that it is difficult to integrate these changes into the main XDAndroid haret build because these changes are extensive and create difficulties for the Diamond and Rhodium.

[tiad8]

OK, GUYS LOOK AT THIS

thank god i had this files in one of sd card.

1- i was playing with oc setting in startup. i was trying deffirent setting. i was testing oc 626800 and oc 616800. with 3d driver 11.26-11.27 and gralloc 11.30

now. i like to do alot of experiment. i have alot of old files from 2008. look, this is what i have mount it on my phone.

1- bootanimation.zip 10.21.10
2- build.prop. 12.09.10
3- copybit.msm7k.so 8.20.08
4- egl.cfg 8.20.08
5-gralloc.msm7k.so (11.29.10)
6- liGLES_qcom.so 08.20.08 (11.26)
7- libGLES_android.so 08.20.08
8- lights.msm7k.so 8.20.08
9- sensors.goldfish.so 2.28.08
10- sensor.msm7k.so 2.28.08
11- sensors.sepphire.so 8.20.08
12- 2.6.35.7-cyanogenmod 12.10.10

with 3d 11.26 and gralloc 11.30 (neocore 18.5 18.2 18.1) (quadrant 572, 560, 580 (oc 626800)

with 3d 11.27 and gralloc 11.30 (neocore 20.1, 19.5, 19.4 ( quadrant 612, 615, 610. (oc 626800)

3d 11.29 not test it

with no oc im doing 17.8, 18.1 17.5

I DON'T LIKE TO USE OC. BUT IF I USE 626800. MY PHONE JUST PERFORM BETTER. MY PHONE GET VERY UNSTABLE USING 716800, 710000 ETC.... I THINK IF I FIND THE RIGHT OC SETTING, WITH THE RIGHT FILES COMBINATION I COULD HAVE A VERY SMOOTH OS.

to be honest, you guys, i don't know why this files are so old but they are good. with this setting my (wifi, 2x data speed. i mean good speed.

man, ANGRY BIRDS LITE RUN GREAT. ALMOST LIKE AN ANDROID PHONE.

I think this old files are orginal files. i have alot more files.

i will do more testing. thanks

[[ACL]]

Originally Posted by friedmjb

What do I need to do to get to 30? Do I have to switch to the FRX83 version, or are you getting 30 on a custom build that you compiled yourself?

yeah im one of the kernel devs for both nand and haret. Its difficult to make changes of this caliber since so many devices and OSs depend on this kernel. Last time i patched for USB we even ended up breaking the glemsom autobuild since the change was not rhobontu friendly.

But the good news is i do have the green light to commit the .35 fb to the haret kernel. This will take time so hopefully in a week or two i'll be up. Only concern is rhobontu. If i break that.. there is going to be plenty of pissed off people ..lol.

[tiad8]

Originally Posted by [ACL]

yeah im one of the kernel devs for both nand and haret. Its difficult to make changes of this caliber since so many devices and OSs depend on this kernel. Last time i patched for USB we even ended up breaking the glemsom autobuild since the change was not rhobontu friendly.

But the good news is i do have the green light to commit the .35 fb to the haret kernel. This will take time so hopefully in a week or two i'll be up. Only concern is rhobontu. If i break that.. there is going to be plenty of pissed off people ..lol.

this is great news. ACL.

i'll be prayin for you, and all the devs. thanks

[arrrghhh]

Originally Posted by [ACL]

But the good news is i do have the green light to commit the .35 fb to the haret kernel. This will take time so hopefully in a week or two i'll be up. Only concern is rhobontu. If i break that.. there is going to be plenty of pissed off people ..lol.

Good news on .35 dude... Good luck

Originally Posted by manekineko

I said this on XDA as well, but what makes you think that build.prop is only for neopeek builds? Doesn't say anything about that in the first post, and it definitely makes a difference for me on FRX03.

It's easy to verify it's doing something. Take FRX03 and try and run Angry Birds Lite (Lite is key). It won't run and will crash to home screen. Install the updated build.prop and it will run.

Originally Posted by InvincibleLiving

I can CONFIRM that build.prop runs on FRX03 as well, Angry Birds Lite runs impressively well when build.prop is mounted... without build.prop continual FC's

I stand corrected on the build.prop, I'm not sure why I thought those were just for Neopeek builds... was getting signals crossed on that one.

Also, I didn't see Lite in the Market, and since I never play the game (I just boot it up to see the framerate lol), I didn't see the point in going out of my way to test the Lite version

[tiger2wander]

Great to see the .35 is coming
Hopefully u can handle to make it work properly soon!
Thanks

[[ACL]]

Originally Posted by tiger2wander

Great to see the .35 is coming
Hopefully u can handle to make it work properly soon!
Thanks

just the framebuffer.. not the whole .35.

[tpdjr]

Hey guys I just wanted to let you know that I tested neocore on a friends htc incredible and it only averaged about 27 fps so i think we are doing really good so far if everybody is on average about 20. O and ACL you think we can get up to this speed?