Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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.

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

Here's some tasty news for sprint users:

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


-

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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.

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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.

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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"

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

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.

Re: Android/Linux for CDMA Touch Pro 2 Rhodium Updated 3-23-2010
 

That is definitely a known issue when enabling 3d.