[JBabey]

Originally Posted by CFdragon

BigJ, I am a total neophyte when it comes to this stuff...absolutely no computer training or understanding. Everything I have done to my phone is as a result of literally days of reading various threads, fuelled by redbull and a thirst for a better operating phone. I have a Sprint PPC 6700 running your newly updated Rom.
I noticed in a previous Rom Sar Aku 3.5+pr that VC1.6 would read incoming text messages even if they were threaded thru the SMS Text Manager program. However, as of yet, VC1.6 has not read any incoming text messages thru the PalmSMS integrated software.
Is it possible to patch this so I can have incoming text messages read by VC1.6? If I download email, it will read the headers no problem.
Maybe I am doing something wrong?
Should I remove the PalmSMS software and go back to SMS Text Manager?
As I said...lots of caffeine..not a lot of experience, and absolutely no idea how to find my root directory with both hands. I just need some help because I really love how this Rom operates!!

Thanks!!

i dont have sarids registry information or VC OEM so im unable to see what he did to allow it full integration to the threaded messages.

My phone randomly seems to get into a state where it turns off due to inactivity (I just checked and the "turn off if inactive for 3 minutes" thing is turned on), but is unable to come back! I just tested it and I am unable to receive phone calls when the phone is in this state. The only way to get out is to soft-reset.

I have not experienced this issue since the AKU 2.x kitchen, nor have any of my beta testers, you failed to specify which ROM you are running, your carrier, what applications you have installed since flashing, and what was currently running when it happened. I dont feel that this is something to do with the ROM per-se but a modification made after the fact. Keep me posted.

The only problem I have is that since I flashed, after pluging in the device at night, I wake up to find that the device has frozen (like the olden days). This has happened almost every night since flashing.

you failed to specify which ROM you are running, your carrier, what applications you have installed since flashing, and what was currently running when it happened. I dont feel that this is something to do with the ROM per-se but a modification made after the fact. Keep me posted.

aside from that, im not sure, this has not happened to me for a VERY long time, and when it was, i exchanged my phone and it stopped happening. (albeit i was a n00b back then).

2nd: When trying to listen to streaming XM via IE, I can't get the stream to launch. I noticed that about 2 weeks ago MusicDock changed their website. Ever since then I haven't been able to listen to XM. I have tried with both WM and TCPMP by changing the file associations for each player, but nothing. Oddly, even another site I use for XM streams which hasn't changed, xstreamxm won't launch the stream either. This is very irritating because I listen to xm about 3 hours a day while commuting. I have checked on my PC that I can go to either link and it will launch WM on my computer, so I don't think it's a problem with the site, maybe how it works now since they changed it.

the 1st issue is a boggle to most people that use this phone, using stereo headsets.... well.... it just plain sucks. You may want to try installing the broadcom stack and putting in a toggle to allow you to switch back to headset mode.

2nd, does this happen on a stock kitchen flash? or just my own ROM. I know TCPMP came out with a retail update yesterday, but nobody has shared the retail program and registration info with me as of yet. As soon as i get ahold of a copy of the new media player, im going to test it with orb and if working, build an OEM package for the kitchen.

I am also working with some people on xda to try and pull the latest directshow files for our phone and integrate them but the progress is slow at best, i will keep you guys posted however if anything changes on that front.

The fact that it will not stream with both media player and TCPMP however leads me to believe that there is another issue that is not related to the media players.