• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root condemned cm7

Just flashed v18 S2H, pretty snappy CC. ;-) Once things get loaded/sync'd and settled down. It is quite fast. I enjoy things being lean in a rom for the Eris. Have not seen any lag in keyboard or dialer.
 
BTW, I know that this has nothing to do with the ROM, but I hate the new market. What a mess. I think it was designed for devices with more RAM - probably the same issues that people are having with the last several versions of Maps - but I regularly see the thing get confused, about whether the status of an app installing (I'll see notifications saying that it is downloading, installing and installed at the same time), I'll see app updates stop mid-way through without installing, report themselves as uninstalled in the new market, though when you tap them you get an open button and they are definitely on the phone, though unupdated - searches still are useless. Just a mess. I hate to say it, but iOS's app store is 10000% better than this garbage. Google should be ashamed of this.
 
As much as I loved the xtrSense 5.x ROM, my li'l Eris that could was getting all blocked up with memory cram, so I took the plunge into the GB roms. After experimenting with several (Thankful to God that I had Titanium Backup and nands!!!) I settled on the Condemned CM7 v17.

I love this ROM almost as much as the xtrSense! It's crisp, fast and has much of the functionality of ROM i previously used.

I really pushed some of the features, especially the SD card storage. I went so far as to try storing apps not specifically designed to use the feature. I paid a dear price on the 3 times I've tried it. I get into a perpetual reboot of the ADW Launcher.

Because of the Quick Boot app, with some finesse between the launcher reboots I've been able to boot to the recovery screen and flash the ROM again, which seems to clear up all of my problems. I do have to restore my non-compliant apps from Titanium.

I'll probably upgrade to v18 one day this weekend. when I do this i'll probably follow doogald's approach of installing only apps I've used int he past week.

Did I mention how much I really like this ROM?! :D

Thanks Condemned Soul for all of your work!!!
 
paleodust said:
My phone keeps rebooting itself now after a few minutes of bluetooth use.
Click to expand...

I tested it out on the previous version and it works just fine so I know it must be something in the ROM.

Is there anything you can do to clear it up, CS? I can't function without my bluetooth.
 
Sounds like a few people are having issues with email. I can't take any chances. This phone is my only link to the outside world until we get power , phone and internet back. Who's up for a barbeque? I have a freezer full of meat that won't keep much longer unless I can find more ice.
 
nomarsgirl said:
Sounds like a few people are having issues with email. I can't take any chances. This phone is my only link to the outside world until we get power , phone and internet back. Who's up for a barbeque? I have a freezer full of meat that won't keep much longer unless I can find more ice.
Click to expand...


Hope things get better up there for you guys soon. Not much has improved down here yet. Still have dams ready to give out and roads and bridges collapsing and sinking. I do have an update I'll be posting soon as I can with the email fixed along with a couple other little quirks worked out. Last I heard Bluetooth is back to normal as well.
 
CondemnedSoul, Thanks so much for reviving my dying droid eris. I am running V17 (Vanilla) and it's awesome! Couple of things/bugs I noticed, not sure if others have the same issues:
1. The lock screen (slider or rotary) will show up everynow and then when the phone is turned on, normally it will go straight to the unlock pattern.
2. The camera has a shutter sound, I didn't see any settings to turn that off.
3. While playing music in random mode, the player will stop at the end of songs i.e won't go to the next song unless phone is turned on and the play button is pressed.
4. Custom assigned ringtones to contacts will not play, it will always play the default ringtone.

Again, these are some of the issues that I see, other than that, it's the best ROM!!!
You rock dude!
 
aphlatoon said:
CondemnedSoul, Thanks so much for reviving my dying droid eris. I am running V17 (Vanilla) and it's awesome! Couple of things/bugs I noticed, not sure if others have the same issues:
1. The lock screen (slider or rotary) will show up everynow and then when the phone is turned on, normally it will go straight to the unlock pattern.
2. The camera has a shutter sound, I didn't see any settings to turn that off.
3. While playing music in random mode, the player will stop at the end of songs i.e won't go to the next song unless phone is turned on and the play button is pressed.
4. Custom assigned ringtones to contacts will not play, it will always play the default ringtone.

Again, these are some of the issues that I see, other than that, it's the best ROM!!!
You rock dude!
Click to expand...

For the music playback, try upping the minimum cpu setting. The phone might be too underclocked to handle switching songs with the screen off.
 
I'm on V18.1 and, unfortunately, I'm still having the same problem with my phone resetting itself after a few seconds of running my bluetooth. Please help!
 
Thank you CS for v18.1. I am running S2H and have not had any problems, however I do not use bluetooth so I can't report on that.
 
paleodust said:
I'm on V18.1 and, unfortunately, I'm still having the same problem with my phone resetting itself after a few seconds of running my bluetooth. Please help!
Click to expand...
I'm on v17 and bluetooth works fine when turned on. Are you having a problem when you first turn it on or when you pair it?
 
paleodust said:
I'm on V18.1 and, unfortunately, I'm still having the same problem with my phone resetting itself after a few seconds of running my bluetooth. Please help!
Click to expand...
We might get some clues if you could run a logcat that outputs to a file on the sdcard while running bluetooth. In terminal emulator or adb shell run these commands:
Code: 
#get root privileges
su

#clear the log
logcat -c

#start a verbose logcat output to an sdcard file with timestamps
logcat -v time *:V > /sdcard/mylog.txt
Now start bluetooth and then after it causes a reset, take the contents of the text file, put them up at pastebin.com and post the link to it here so we can take a look.
 
MongooseHelix said:
We might get some clues if you could run a logcat that outputs to a file on the sdcard while running bluetooth. In terminal emulator or adb shell run these commands:
Code: 
#get root privileges
su

#clear the log
logcat -c

#start a verbose logcat output to an sdcard file with timestamps
logcat -v time *:V > /sdcard/mylog.txt
Now start bluetooth and then after it causes a reset, take the contents of the text file, put them up at pastebin.com and post the link to it here so we can take a look.
Click to expand...


Thanks for this helpful post. I have often wanted to capture crash information and never was able to learn such a simple and clear method.
 
So far I'm lovin' v18 except for one annoying thing. Anyone know how to turn off the vibrate buzz when you dial a number and hit the "phone" Kinda like a buzz to let you know it's connecting.
 
manderle said:
So far I'm lovin' v18 except for one annoying thing. Anyone know how to turn off the vibrate buzz when you dial a number and hit the "phone" Kinda like a buzz to let you know it's connecting.
Click to expand...

Is that settings->call settings->vibrate on answer?

Even if it's not, this is something I would turn on anyway. This always lets me know that the call is going through and I can now put the phone to my head, rather than dial, hold to my head, get nothing but silence and finally look at the display, only to discover that it never dialed because I have a poor signal or something.
 
I accidently deleted browser.apk while in the terminal window, now the browser won't come up. I tried copying the browser.apk file from the original build, moved it back to /system/app/ directory but it still won't work, any ideas how to bring it back up?
 
aphlatoon said:
I'm on v17 and bluetooth works fine when turned on. Are you having a problem when you first turn it on or when you pair it?
Click to expand...

My wife's phone is still on V17 and it works fine on hers. On V18 and V18.1, it pairs just fine but, as soon as I make a call, answer a call, play a game or music or YouTube or anything that uses bluetooth for audio, it causes the phone to freeze for a few seconds and reset itself. Typically, this happens within less than a minute of running audio through it.
 
MongooseHelix said:
We might get some clues if you could run a logcat that outputs to a file on the sdcard while running bluetooth. In terminal emulator or adb shell run these commands:
Code: 
#get root privileges
su

#clear the log
logcat -c

#start a verbose logcat output to an sdcard file with timestamps
logcat -v time *:V > /sdcard/mylog.txt
Now start bluetooth and then after it causes a reset, take the contents of the text file, put them up at pastebin.com and post the link to it here so we can take a look.
Click to expand...

I'll have to try that.
 
You must log in or register to reply here.
Back
Top Bottom