Did you mount system and data before you flashed them?
Sent from my HTC Vision using XDA App
Just tried mounting system and I'm getting this message
Error mounting SYSTEM:!
Did you mount system and data before you flashed them?
Sent from my HTC Vision using XDA App
Just tried mounting system and I'm getting this message
Error mounting SYSTEM:!
Just tried mounting system and I'm getting this message
Error mounting SYSTEM:!
Just tried mounting system and I'm getting this message
Error mounting SYSTEM:!
i flashed this on top of build 53 and it seem to be working just fine, but damm! no on and off animations, the settings are there but they don't work
The animations are buggy (prevents the screen from coming on) when you overclock on the G2 because of some race condition that I've not been able to track down yet.
I apologise if this is a stupid question but what is the different between this and the other cm7 thread .i am running build #54 just now, is this going to be any different? .i would appreciate it if someone could clear that up for me .
Video playback is still busted.
Sent from a Western Union telegram.
Stock twitter app won't hold account data or sync.
Sent from my HTC Vision
This has happened to me on other ROMs and usually running fix_permissions will fix it.
Anyone having trouble with tethering? With both wired and wireless, I can connect to the phone, but no outside connection to the web.
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.