[makkonen]

Originally Posted by ChaosTheory

Are you referring to someone with a native android device? Or is that something I can do with my TP? It is the only one I have, so if I can use it for advancment without a huge risk (I know anything carries some risk ) I would be willing to try.

Nah, it's something you can do with your TP, but it's not something I would want to attempt with a phone I actually use on a daily basis. I'm talking about making either an Android-only ROM, or a lightweight WinMo ROM which stores the Android system and/or data on the internal memory. I don't really have any idea how far people have gotten with that, but it could use some more attention.

I am a coder by nature, and while C may be far ahead of what I am actually good at I know that learning any programming language only advances knowledge and capacity in others. So if you can point me somewhere to get started I'm ready (Though it may take a while before I am good enough to be useful )

Here's my writeup on how to start building your own kernels:

http://www.androidonhtc.com/wiki/Get_Involved

My current complaints are the same ones everyone else has i.e. camera, gps, battery life, and SD access. If there is something specific in any of those areas you can point me to work on (particularly the camera or SD access) I would appreciate it! Side note: MMS doesn't work with smartphones on my carrier last I was aware Don't really ever use them, but I hope they catch up with things soon, as I really like their rates and customer service, the phone selection and network features just leave much to be desired.

I'm with you on MMS -- Sprint's has never worked that well, but it's never seemed like a big deal to me, since my phones have been able to send and receive email since 2004.

Camera and GPS.. you'll have to ask more knowledgeable coders than I. (They hang out on #htc-linux on freenode)

Battery life... there's a few things that could probably benefit from some attention. You could use the phone and use android's built-in battery monitor, start to figure out the main culprits, and see if there's any glaring bugs (things not shutting down on sleep, running full-bore all the time, etc.), or you could find a copy of powertop compiled for Android and see if that gives you anything. (Cyanogen has one -- I can't find a link at the moment).

Also, you could try to figure out what's waking the phone from sleep (I have a suspicion that cdma is less amenable to sleeping than gsm, which is why we get less battery life than our gsm counterparts). If you add pm.debug_mask=2 to your cmdline, you'll get little vibrations every time sleep is interrupted. From what I understand, it should happen every few minutes. For me, it happens every few seconds (but I haven't played with turning off all my data access to see if that helps it).

I haven't done this part, but if you add irq.debug_mask=8 to your cmdline, then every time the device wakes up, an msm_irq_exit_sleep1 message will be posted to the dmesg. Wake up reason will be the third figure, and you'll have to cross reference the kernel source (arch/arm/mach-msm/smd_private.h -- SMSM_WKUP constants) to see what they correspond to.