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

[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>

[x10guy]

Originally Posted by cflynt

Just have to be patient, I know it is tough. But we will get there. Have faith!

Probably puts a damper on those looking for Android to replace Winmo on their TP2 but a good dose of realism is always good.

[00_MACKIE_00]

Originally Posted by x10guy

Probably puts a damper on those looking for Android to replace Winmo on their TP2 but a good dose of realism is always good.

Honestly, I consider this a tune-up for me until I get the EVO. lol The TP2 will be auctioned off on Ebay.

Depending on how far this development gets, I may just keep the TP2 too.

I am getting bored with it though. I am getting bored faster with the TP2 than I did with my Treo Pro.

[steveoski]

Originally Posted by 00_MACKIE_00

Honestly, I consider this a tune-up for me until I get the EVO. lol The TP2 will be auctioned off on Ebay.

Depending on how far this development gets, I may just keep the TP2 too.

I am getting bored with it though. I am getting bored faster with the TP2 than I did with my Treo Pro.

Honestly i think it doesn"t matter what phone we got were gonna get bored of it there is really nothing special about the evo except a little faster and 4g. Even the iphone i got bored of. With windows at least you can run windows and or android on it now and customize it hower you want. If you want a new phone flash a new rom get some new shiony icons what not. Oncew the evo comes out and we all get it than the WP7 phones will come out and we will get bored of the evo and move on. The circle of life

[x10guy]

Originally Posted by 00_MACKIE_00

Honestly, I consider this a tune-up for me until I get the EVO. lol The TP2 will be auctioned off on Ebay.

Depending on how far this development gets, I may just keep the TP2 too.

I am getting bored with it though. I am getting bored faster with the TP2 than I did with my Treo Pro.

Sorry to hear that. But the Evo almost looks irresitable.
I'm just glad all that talk of "Android replacing Winmo on my TP" has died down. Believe me, I'd love to see it happen but realistically the only device where it even seems feasible is ONLY on the original Touch (Vogue) and that device is ancient in terms of hardware specs.
Cflynt's post about 7-8 modules that currently do not have any drivers is a big dose of realism. The devs are generally not paid and they are doing it in their spare time. Sometimes it's hard to stay interested and motivated.

We can certainly hope for the best but we have to be aware of the possibility that it will take some time... and it might not ever be 100% usable.

[bleachpuppy]

Originally Posted by x10guy

Cflynt's post about 7-8 modules that currently do not have any drivers is a big dose of realism.

Yeah that comment was eye-opening. I've been keeping an eye on this thread waiting for audio -- I would easily use android full-time if I could use ringtones, run pandora, use voice commands, etc. So hearing how far it has to go was a little disheartening.

So, rather than giving up or sitting back hoping and waiting... Do the devs have anything in particular they need help with? I'm a nerd with background in programming and DSP, though I've never dug into anything like linux kernel work. I'd be happy to tinker with the audio, but I don't even know where to start. Is there a dev thread (as opposed to this, which is more of a user thread) where developers are talking about the audio issue, and the nitty gritty details of what would need to happen? I might likely be in over my head, but still I've got a couple hours train ride every day, maybe I could poke into this if I had any idea where to start. I'd imagine there might be others in this same situation -- if anyone wants some help and knows how to make use of all of us aching for audio...

[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.

[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

[Technix2002]

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

[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