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

Root condemned cm7

Paleodust - did you get my pm? I'm gonna try it with the stripped version. I wonder if its not something in that. Had no problem on vanilla.
 
sorry to nag but just found another problem. The custom ringtones are not working, no matter what is selected, it will always play the default ringtone.
 
My eureka moment of the day:

For a while I've been having problems with various Twitter clients updating in the background on this ROM. It's the only thing I've had trouble with, and it was happening with various clients (Tweetdeck, my preferred client; Plume; Ubersocial, formerly Twidroyd; even the official Twitter app, which I really do not like all that much.) Background updates would happen for a while, but then would stop for hours at a time, and even manual refreshes did nothing.

I thought perhaps it was a Twitter issue, but I was not seeing the same problem on desktop twitter clients at all. And this was happening daily and consistently.

I even switched back to 2.1 Sense. I tried CS's 666 Sense, but the lack of cache2cache left me with too little free RAM; then went to a fresh install of xtrSENSE. But 2.1 Sense ROMs I always have little niggling issues with - first, the LED notifications stop going off after a while, so glancing a turned-off display leads no hint that there are waiting notifications. Second, there are times that swipes of the display are delayed and then over-swipe, scrolling away rapidly while I watch in irritation - this happens to me a lot. Third, the 2.1 based GMail app just isn't as good as the Froyo and above version. Fourth, the Sense ROMs just eat battery on my phone. Fifth, and my biggest complaint: calendar event reminders, which are supposed to display on the lockscreen with a "swipe to dismiss the notification", do so intermittently with just a plain lockscreen, and when I see the plain lockscreen that means I will get reminded every 5 minutes until the event, with no way to dismiss the alarm. This is particularly annoying when I am driving somewhere and cannot dismiss the alarms anyway.

However, Tweetdeck was definitely updating properly and consistently.

I finally decided to try one more thing on this ROM, and restored my latest Nandroid. I should now note that one of the first things that I do with Froyo and GB ROMs is to change the default governor to smartass, and I did that on 18.2 as well. I decided to try running the ROM with the ondemand governor (I know, that's the default), just to see what happens.

Eureka. Everything works perfectly. (It seems to be using less battery to boot.)

Lesson learned: do not use the smartass governor.
 
sorry to nag but just found another problem. The custom ringtones are not working, no matter what is selected, it will always play the default ringtone.

I am *definitely* not having this problem. I have custom ringtones for both default ringtone, default notifications, and Gmail notifications. They stay set and play.

Have you played around with the Profiles section of settings, by any chance? I wonder if that's causing it?
 
I am *definitely* not having this problem. I have custom ringtones for both default ringtone, default notifications, and Gmail notifications. They stay set and play.

Have you played around with the Profiles section of settings, by any chance? I wonder if that's causing it?
Just read my own post and I know why it confused you.
I'm talking about custom ringtones set for a particular contact. For example, when bob calls me, I want a different ringtone to play instead of the default ringtone that rings for everyone else. This feature is not working.
 
Just read my own post and I know why it confused you.
I'm talking about custom ringtones set for a particular contact. For example, when bob calls me, I want a different ringtone to play instead of the default ringtone that rings for everyone else. This feature is not working.

Aha. I never do this. This was a problem with GSB that (I believe) was fixed by adding the following line to the /system/build.prop file:

ro.ringtone_query_wait_time=3500


You can do this with the application Root Explorer; there are other ways, but that's how I always change files like that. Then restart the phone.

I'd Nandroid backup first, though.
 
One problem I've had is using the USB Storage feature. If I use this method to transfer files to my SD card, the ROM becomes erratic. Sometimes perform a cache wipe and Dalvik-cache wipe clears up the problem. Most of the time I end up having to reflash the ROM.

Anyone else experience this issue?

I'm rooted and using CM7 Vanilla v18.2 on an Eris. I've experienced this issue on every version since I moved to CM7 v17. Just so you know, it's not a showstopper for me. I started powering down the phone and removing the SD card to load files (mostly music files). I still love this ROM!!!:p
 
One problem I've had is using the USB Storage feature. If I use this method to transfer files to my SD card, the ROM becomes erratic. Sometimes perform a cache wipe and Dalvik-cache wipe clears up the problem. Most of the time I end up having to reflash the ROM.

Anyone else experience this issue?

Mine gets caught in a continual boot loop once in a while, which seems to be somehow related to installation but I'm not sure exactly what's going on. It fact, I just barely had one and stopped it by wiping the Dalvik-cache.
 
I just found out I'm eligible for an upgrade. I'm trying to decide between the Charge and the Bionic.

...or is there something else coming out soon that would be worth waiting for?
 
I just found out I'm eligible for an upgrade. I'm trying to decide between the Charge and the Bionic.

...or is there something else coming out soon that would be worth waiting for?

Rumors are htc vigor, iphone 5, nexus/droid prime all within the next few months. They are just rumors though.
 
CS, just a quick note that my phone is having that weird 3G thing going on today. It seems stuck on 1x data only. Switch to airplane and back did not fix it.


(18.2S2H.)
 
I'm holding out for the Vigor which is due to be reveiled 9-20 but we'll see.

I'm hoping for the vigor too :) but not eligibile until the end of November.

I'm trying to get a chance to dig into some of these issues guys. Just been real busy at work lately. Hopefully this weekend I'll be able to have something for you.
 
I've got an upgrade too. I'm going to hold out for a while. The Eris is still chugging along. My husband's Droid Pro is a lot faster, but it sure is an ugly phone.
 
Thanks, guys. Now I've got my eye on the Vigor. It looks like it'll be called the Incredible HD, based on newer posts. I kinda like "Vigor."
 
Thanks, guys. Now I've got my eye on the Vigor. It looks like it'll be called the Incredible HD, based on newer posts. I kinda like "Vigor."

I've also seen reports that it will replace the Thunderbolt and be either the Thunderbolt2 or Thunderbolt HD.

Another 4.3" display. Meh. I may have to just settle for something like this, I guess...
 
CS, just a quick note that my phone is having that weird 3G thing going on today. It seems stuck on 1x data only. Switch to airplane and back did not fix it.


(18.2S2H.)

Just as an update, I tried flashing GSB from scratch and had the same issue. Did the go back to stock and re-activate trick, then went to xtrSENSE, where 3G now seems fine.

I wonder, is VZW sensing that people are running unofficial, rooted ROMs on devices and stepping back the data speed? Or is that too paranoid?
 
Just as an update, I tried flashing GSB from scratch and had the same issue. Did the go back to stick and re-activate trick, then went to xtrSENSE, where 3G now seems fine.

I wonder, is VZW sensing that people are running unofficial, rooted ROMs on devices and stepping back the data speed? Or is that too paranoid?

I'm using an DINC now but have had a similar experiance a couple of times but I wonder if it was because of the transition to 4g with their system. There was a time where I would loose all data running CS's first couple roms for the Inc and had to flash back to nightly's but haven't had any problems with v6. My biggest issue was when flashing a new version nothing would sync but contacts and I didn't know if it was because I'm using Amon's recovery instead of clockwork.
 
Just as an update, I tried flashing GSB from scratch and had the same issue. Did the go back to stock and re-activate trick, then went to xtrSENSE, where 3G now seems fine.

I wonder, is VZW sensing that people are running unofficial, rooted ROMs on devices and stepping back the data speed? Or is that too paranoid?


Could be paranoid or could be a good theory lol. Hard to say for sure. I'm going to be posting a reissue of v17 soon since that was the most stable version of late. Still can't do much of an official update though because kernel.org is still down.
 
CS, do you keep a change log of what is changed when you release a new version? If not, maybe that's something you wanna put below the release so we know what should we look for. Thanks!
 
Back
Top Bottom