Any chance someone can upload the latest Mms.apk please? I dont have internet right now, and i am throattled on my phone. Thank you.
Sent from my T-Mobile G2
Sent from my T-Mobile G2
Any chance someone can upload the latest Mms.apk please? I dont have internet right now, and i am throattled on my phone. Thank you.
Sent from my T-Mobile G2
I put a copy in my dropbox for you.
http://db.tt/okxzekS
Sent from my HTC Vision using XDA Premium App
philosophics said:I must have missed something. Why do you need a new mms.apk?
Sent from me CM7 Nightly HTC Vision using XDA App that needs to show signatures
Nuts! The Swype copy that came with my G2, which I've been restoring from way back with each flash, no longer works for swyping. It still works as a regular touchscreen keyboard which is odd.
I get an error that the Swype copy is for another phone and to contact Swype.
Sent from my HTC Vision using XDA App
With regards to the google navigation issue about the screen dimming after 30 seconds and only turning back on during turns, was there any fix to this? Maybe an app or something that will force the screen to stay on? This isn't a CM7 problem but more of a google maps/navigation one. I figured I ask here since there were some questions sever pages back. If no solution is out there, I will prolly create a new thread in the general android forum. Short of using an older version of maps, is there anything else we can do?
It is a new feature in Navigation and there are many complaints about it. Until Google does something about it, if they decide to, the only workaround is installing an older version.
http://www.google.vu/support/forum/p/Google+Mobile/thread?tid=4cc9c887d2e02712&hl=en
Older versions of Maps can be found here:
http://www.freewarelovers.com/android/app/google-maps
Sent from my HTC Vision using XDA Premium App
From time to time, my physical keyboard will begin to map certain keys to an application (ie, "e" key taking me to email or "s" key opening sms.). When I had a g1, there was a "function" key that could be used to map specific apps to keys. It seems like this is what's going on, only without the use of a function key. A reboot seems to fix it. I asked this before and someone suggested assigning apps to the three shortcut keys. I did that and thought that it was fixed but it happened again today. I know a few folks have experienced it. Is there any fix for this?
Sent from my HTC Vision using XDA App
From time to time, my physical keyboard will begin to map certain keys to an application (ie, "e" key taking me to email or "s" key opening sms.). When I had a g1, there was a "function" key that could be used to map specific apps to keys. It seems like this is what's going on, only without the use of a function key. A reboot seems to fix it. I asked this before and someone suggested assigning apps to the three shortcut keys. I did that and thought that it was fixed but it happened again today. I know a few folks have experienced it. Is there any fix for this?
Sent from my HTC Vision using XDA App
This may sound dumb (and probably is), but where is the control to change how the volume up/down buttons work? ie, Silent/Vib/Sound or Silent/Sound, Silent/Vib/Sound + Vib, etc? I can't seem to find it in the menus. Thanks!
menu > settings > applications > quick launch > and clear those (long press on them to clear). Its meant to be used if you hit the "search" key and another keyboard key to launch an app, but it bugs out from time to time. If you don't use them, just clear em.
look under settings > cyanogen settings. should be there, some where. (i know, its kind of cluttered, but you will find it )
Wait, there is a way to change what the Vol Rocker buttons do to your phones sound profile? No way...I have been trying to figure this out since upgrading to GB from Froyo.
Anyways, I always managed to get these ring settings (but only through the notification power widget, not the vol up and down buttons) by going into Settings/CM Settings/Interface/Notification Power Widget/Widget Buttons
and scrolling all the way down to Sound modes and changing it there. Of course u have to add the Toggle sound button to the Power Notification Widget.
That is how I have always got my phone to go from Ring + vib to Ring to Vib to Silent. Please someone shed some light on how we can make the vol up + down buttons function the same way?
Go to Settings>CyanogenMod settings>Sound and put a check mark in Silent state.
su
flash_image recovery /sdcard/recovery.img
reboot recovery
I'm syncing the t9 changes and building.... I'll update after it's uploaded.There are a couple of new commits with fixes for the T9 dialer (not directed at the question about Chines chars).
Sent from my Desire Z running CM7.
We’ve been hard at work on CM9 since Google released Android 4.0 (Ice Cream Sandwich) into the wild last month, and things are slowly starting to come together. Google did a great job with ICS and added some really awesome features which in some cases replace or deprecate functionality that we had in CM7, so we are reevaluating all of our customizations. A number of devices are already up and running with CM9, and the focus is currently on getting as many devices ready as we can. The first devices (besides the Nexus S, which you can already get from Koush’s section on ROM Manager) that we’ll have ready will mostly likely be devices based on OMAP4, MSM8660/7X30, and Exynos. We also have some Tegra2 tablets in the pipeline such as the Galaxy Tab 10.1 and Asus Transformer. Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. I don’t want to make any promises at this time, but that is the plan. And sorry Droid1 owners, we’re dropping support for you. Time to upgrade
There are a number of challenges that we are up against. Google has made some pretty major changes to the Android framework that break compatibility with older proprietary camera and graphics drivers in order to achieve some pretty insane performance, but I am confident that the team will be able to overcome these issues like we have in the past.
For those of you who like to build CM from source yourself, you probably know that the spin-up time when starting a CM7 build is absurdly long due to the high number of devices in our repository. Koush and Arcee have put together a solution to this problem that adds new devices on-demand to your local repository, saving on both bandwidth and the long startup time. Some other great enhancements are coming too, like a completely overhauled music app, a new file manager, and a new launcher based on stock 4.0.
If you have a Nexus S, you can check out the code and build for yourself today. More devices are on the way, and I’ll send out these status updates as we make more progress.