Android/Linux for CDMA Touch Pro 2 Rhodium Updated 5-20-2010

[cflynt]

Originally Posted by gambit07

I have a question, when (hopefully not if) we get sound, where will it come from most likely? Will it come from the kernel site? Will it be an update from Pippy? Just wondering if anybody knows. Thanks!

Good question, and there is a lot of confusion with that issue. The quick answer to your question is it will most likely be in the Kernel. The Kernel houses most of your drivers.

Now as far as the Pippy role. MrPippy is one of many developers working on Android/Linux stuff. It is thanks to 95Civic for getting the desire to make Rhodium CDMA data work, they already have CDMA working with other devices. Just Rhodium for some reason was handled differently. 95Civic managed to make the phone work, which is more than most had accomplished, mind you most didn't have a CDMA Rhodium to play with. Then 95Civic ran out of time to dev, and in came MrPippy, whom was already a major developer for what Android is today. And he had just gotten himself a CDMA Rhodium, hence desire to fix it. So he managed to figure out that the RIL which controls our radio was a lot different, so to get us going he modified the RIL. It was so different that it in current state can't work with the other RIL's till it gets merged in, hence why we have to run a separate rootfs.img where the RIL exists, than all other devices. And why anytime a new rootfs.img comes out with changes, like the Wifi Tethering that Stinebd accomplished we have to go in and implement the RIL MrPippy changed into it in order for us to use it.

So the jist is, yes MrPippy rocks for getting us going, but don't forget all the other developers out there that have worked their tails off to get us where we are today, INCLUDING MrPippy, who continues to develop as well as all the others. I do in fact believe that MrPippy is focussing a lot of his attention on sound, hence some of the commits for H2W which is our audio jacks. As well as some other developers. They all work together and then we come up with a working product.

Unfortunately the adsp chips in the Rhodium are very different I guess than most other devices, hence why we don't have sound to this day. Every day they make a little headway but there is a lot to be done from my understanding. So it very well could be awhile unless a major breakthrough happens, which often does.

Hope that novel answers your questions in more ways than one, I just didn't want you guys thinking that MrPippy was the ONLY one that gives us anything of value. There are numerous developers that do this for us, and without them we wouldn't be having this thread at all.

[unkellsam]

Here's some tasty news for sprint users:

http://gizmodo.com/5500343/sprints-h...e-new-terrific


-

[gambit07]

Thanks! Sorry I didn't mean to diss the other devs out there certainly, I was just only aware of pippy working on the tp2 specifically. Anyway I guess we'll just have to keep holding our breath.

In other news my TP2 is successfully running at 691.2 mhz! works awesome, the slide down menu specifically is smooth for once and has no stutters which is awesome. Also programs seem to open up quicker and everything generally feels more responsive. Awesome improvement, I'll try higher speeds soon.

[cflynt]

Originally Posted by gambit07

Thanks! Sorry I didn't mean to diss the other devs out there certainly, I was just only aware of pippy working on the tp2 specifically. Anyway I guess we'll just have to keep holding our breath.

No worries, that's not how I took it, I just wanted to make sure that everyone knew that more than MrPippy is bringing us this great stuff. No doubt he is the bomb for giving us the CDMA Rhodium data, hence we wouldn't be having this discussion without heh. Just wanted credit to goto all developers.

[one80oneday]

Originally Posted by Ludacrisvp

Anyone want to OVERCLOCK their Touch Pro2?

I was over at XDA last night and ran across some info posted by phhusion about a command line switch that allows for overclocking of the MSM7600 system under android.

It only raises clock speed and doesn't mess with voltage to the chipset so it should be ok to use. HOWEVER WITH THAT SAID NOBODY ON XDA OR PPCG ARE RESPONSIBLE IF YOU DAMAGE YOUR DEVICE.

He posted that several Rhods have been running at 768Mhz for over a month without any issues.

He believes that the theoretical top speed would be 1.2Ghz but that our device would crash before we could get it that high.
I tried 700Mhz, and 768Mhz and they both seemed stable... a nice jump from 528mhz.
Just for fun I tried 968Mhz but it just locked up while loading Haret.
This is the cmd line switch you need to add to the cmdline text in your startup.txt remember to add it before the keyboard entry.
Replace the XXXXXX with the frequency you want in Khz not Mhz.

"acpuclock.oc_freq_khz=XXXXXX"

You have to enter speeds in Khz though so
528000 = 528Mhz Stock speed
700000 = 700Mhz
768000 = 768Mhz Reported to be stable
And so on.

I tried it and it works, but I still have some lag in Android that I think is SD card related only have a class 2 and class 4 cards to work with, I'm sure once we get around to nand flashing it will be more beneficial to overclock.

I haven't really noticed any battery change but under Android it doesn't last too long anyways when you are actually using the device.
Using the battery monitor app on android it seems that a full charge is about 4.6 and when it gets down to 4.1 you have less than 10% when you get back to WM. - just my personal exp.

Good luck, post some stable speeds and we can have some fun with a faster device!

Can someone please post or PM me a startup.txt with the overclock mod? I keep getting errors when I try

[slow4g63]

Originally Posted by one80oneday

Can someone please post or PM me a startup.txt with the overclock mod? I keep getting errors when I try

mine crashed when trying the 768mhz, but worked with the 700mhz.
I also added the 3d acceleration support, here's my startup.txt:

set RAMSIZE 0x6000000
set RAMADDR 0x10000000

set mtype 2292
set KERNEL zImage
set initrd initrd.gz

#pwf dm.txt 0x8e0000 0x20000

set cmdline "acpuclock.oc_freq_khz=700000 hw3d.force=1 msmvkeyb_toggle=off gsensor_axis=2,1,3 lcd.density=240 htc_hw.force_cdma=1 physkeyboard=rhod400"

boot

[slow4g63]

the original "set cmdline" is:

set cmdline "msmvkeyb_toggle=off gsensor_axis=2,1,3 lcd.density=240 htc_hw.force_cdma=1 physkeyboard=rhod400"

[slow4g63]

it also seems when you set/add "hw3d.force=1" you will no longer see the X startup graphic.

[cflynt]

Originally Posted by one80oneday

Can someone please post or PM me a startup.txt with the overclock mod? I keep getting errors when I try

Key to the startup.txt's is you can't put anything after "physkeyboard=x" put all your stuff before that with a space after each one. This will be fixed they say in time but currently, the physkeyboard must be last.

[cflynt]

Originally Posted by slow4g63

it also seems when you set/add "hw3d.force=1" you will no longer see the X startup graphic.

That is definitely a known issue when enabling 3d.