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

[dem0n2001]

anybody can edit those kernel comments... and it doesn't look like the normal change log so i guess somebody is messing with us...

[neilson]

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

what are the key sticking points within the kernel or chip that store preventing sound from being a reality?

[00_MACKIE_00]

Originally Posted by neilson

Wirelessly posted (Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; IEMobile 8.12; MSIEMobile6.0) Sprint T7380)

what are the key sticking points within the kernel or chip that store preventing sound from being a reality?

I had heard something about the speaker being amplified was part of the problem.

To be honest though, I don't think anyone has dug deep into it yet.

[cflynt]

As already mentioned, the comments are just that, comments that anyone can put in there, you would hope you could rely on them, but anyone can write anything in there. I would mainly go by the actual changelog, if sound is working, I can guarantee you something will be in that changelog mentioning sound working.

As far as the issues, I have mentioned this numerous times, there are many developers working on many things, sound is definitely a desire for them, but the Rhodium sound system is a beast. There are like 7 or 8 different modules that have to be written for it. Compared to a normal system that has 1. The drivers don't exist, they have to create them. It obviously isn't an easy task or it would be done. And if you have ever developed for anything, you should understand that it is a very time consuming task trying to debug and create drivers for something that doesn't exist, and then when you fail it becomes very frustrating and you need to take a break and work on other things to keep your motivation going. They are always working on things, and trying to make other things work as well. They help each other, 2 heads are better than one, and when one dev is working on something and is stumbled a lot of times they all pitch in and work together on whatever that issue was. So some things get pushed around on the burners. And during this, they find out bugs and issues and if it looks to be easy fixes they go ahead and pursue fixing those issues. It is what developing is about.

So quit worrying about it, quit complaining about it, if you want to help, help them. But constantly bitching cuz you don't have what you deem is important to you isn't working isn't helping anything. Look at what they have accomplished so far and take praise upon that. We will have things working in time. Just have to be patient, I know it is tough. But we will get there. Have faith!

[NxtGenCowboy]

Originally Posted by cflynt

As already mentioned, the comments are just that, comments that anyone can put in there, you would hope you could rely on them, but anyone can write anything in there. I would mainly go by the actual changelog, if sound is working, I can guarantee you something will be in that changelog mentioning sound working.

As far as the issues, I have mentioned this numerous times, there are many developers working on many things, sound is definitely a desire for them, but the Rhodium sound system is a beast. There are like 7 or 8 different modules that have to be written for it. Compared to a normal system that has 1. The drivers don't exist, they have to create them. It obviously isn't an easy task or it would be done. And if you have ever developed for anything, you should understand that it is a very time consuming task trying to debug and create drivers for something that doesn't exist, and then when you fail it becomes very frustrating and you need to take a break and work on other things to keep your motivation going. They are always working on things, and trying to make other things work as well. They help each other, 2 heads are better than one, and when one dev is working on something and is stumbled a lot of times they all pitch in and work together on whatever that issue was. So some things get pushed around on the burners. And during this, they find out bugs and issues and if it looks to be easy fixes they go ahead and pursue fixing those issues. It is what developing is about.

So quit worrying about it, quit complaining about it, if you want to help, help them. But constantly bitching cuz you don't have what you deem is important to you isn't working isn't helping anything. Look at what they have accomplished so far and take praise upon that. We will have things working in time. Just have to be patient, I know it is tough. But we will get there. Have faith!

Your a god. Amen. =D>

[distaula]

I gave a quick search but haven't found an answer to this. (I'm probably just blind)

Is there a way to re-map the hardware keys? Specifically I use ConnectBot quite often to do SSH stuff but without an OK key I don't have access to escape or control.

Is an OK button mapped anywhere? If not is there a way to map one?

Another option would be the ability to map the Control/Esc buttons elsewhere.

[Technix2002]

I wonder if the HTC Evo 4G will have any drivers that will work for the Touch Pro 2 hardware?

[1900]

Originally Posted by distaula

I gave a quick search but haven't found an answer to this. (I'm probably just blind)

Is there a way to re-map the hardware keys? Specifically I use ConnectBot quite often to do SSH stuff but without an OK key I don't have access to escape or control.

Is an OK button mapped anywhere? If not is there a way to map one?

Another option would be the ability to map the Control/Esc buttons elsewhere.

Alas, i know of no app to perform this dynamically...

Using linux, download the kernel build stuff - lots of directions in this forumn, 95civic has good pointers - you need this to run the kcm program to create a compiled version of the kcm file.

unzip a full android build onto you system
mount the rootfs.img
(mount -loop -o rw rootfs.img somediryoucreatedasamountpoint)

update a kcm file (ie rhod400_microp-keypad.kcm) (its a text file) and change the mappings as desired. compile the kcm to create a kcm.bin

copy the updated rootfs to you storage card.

It is probably easier to ssh to you phone over wifi

[wherestheanykey]

So regarding the wifi tethering, the answer in the FAQ section is says we need the latest kernel pack, but in the XDA post it says you need to use his modified kernel pack with link provided, however the date is something like 2-26. So which is it? Do we have to have the specific kernel found in the link provided in the answer, or are all of the new kernels including whatever change was necessary to make it work, and all we really need from the XDA post is the xdandroid tether.apk? Could we pease get just a littel more detail in the answer for this FAQ?

Thanks

[cflynt]

Originally Posted by wherestheanykey

So regarding the wifi tethering, the answer in the FAQ section is says we need the latest kernel pack, but in the XDA post it says you need to use his modified kernel pack with link provided, however the date is something like 2-26. So which is it? Do we have to have the specific kernel found in the link provided in the answer, or are all of the new kernels including whatever change was necessary to make it work, and all we really need from the XDA post is the xdandroid tether.apk? Could we pease get just a littel more detail in the answer for this FAQ?

Thanks

That post was made before it was merged. His changes now co-exist in the current kernel. So as long as you are running the current you should be fine. Hence the FAQ.