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

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

For the past week or so, I've been having an odd problem occasionally. Every now and then, the status bar will freeze. I can pull it down and push it up, but I can't use any of the power control buttons, and I can't tap or clear any notifications. It's always solved by a reboot or by killing the status bar process, but it's really odd and kind of annoying. I just updated to the latest build yesterday, and I even tried running a fix permissions in CWM. Any idea what could be causing this/is anyone else having this issue?

+1
Almost exactly this, except mine only started since the latest 1/21 build.
I wiped dalvik and cache and fixed permissions before updating this on top of the 1/14 build. My first boot failed, so I battery pulled and rebooted to CWM and reinstalled it again. Then the first boot was successful, but I forgot to add gapps, so one more time into CWM and installed gapps again. Now the notification bar sometimes becomes unresponsive as above.

I am tempted to do a wipe and clean reinstall of everything...
probably about time. But this it the only niggling issue.
 
I have also had the locking of my status bar state. When it is locked up content can still come in but the only input accepted is to close the window. Everything else seems to continue to work fine. Most often the one item I started to slide stays in the partly moved state.

I suspect that it is not related, but I have noticed one odd case that started with the kernel just before this ROM and seems to be getting a little worse. When I turn on the network, there's a long pause before it seems to start the radio (no indicator on the status bar). I did not notice this on early TG kernels or TheOC from December. I did notice it on my TG ROM with the last TheOC kernels I tried.

Since whyzor's usage patern (services on by hand when needed) is like mine I figured it would get fixed quickly, without me saying anything.

And this is still a great ROM! Great work on this and for your work on Cm9.
 
I too am having the status bar issue since the last update. Not really much of a bother.

A few pages back, I posted about poor battery life. As luck would have it, after upgrading to the new version, clearing cache and dalvik cache again and installing BBS, life has improved quite dramatically. However, I've had a bad day again today. Nothing really sticks out for partial wakelocks, with the worst offender at a minute and a half.

However, under kernel wakelock, I have bq275x0 at almost 2 hours, and mmc_delayed_work a minute and 5 seconds shy of bq275x0. Phone has been off the charger for about 4 hours currently and am at 50%.


Otherwise, this is fantastic! Thanks

Also, any updates on using the compiled bits from the ideos x6 / cherry magnum 2.3 rom?
 
whyzor can you increase the media volume in the rom? like raise the min volume higher, so it starts out pretty loud like stock. then also raise the max, so it will reach the same maximum volume as the stock froyo rom? :D i know this might sound like another personal request, but this bug alot of people one here. so it wouldnt just benefit me. thankyou
 
whyzor can you increase the media volume in the rom? like raise the min volume higher, so it starts out pretty loud like stock. then also raise the max, so it will reach the same maximum volume as the stock froyo rom? :D i know this might sound like another personal request, but this bug alot of people one here. so it wouldnt just benefit me. thankyou
Check out Volume+ in the Market.

As a sidenote, quite a while ago I noticed that there were separate media volume settings for the speaker and headset. Did you add this, Whyzor?
 
I was thinking about the "phone flashes when on a call" bug. How does the proximity sensor work? If it senses distance, then the threshhold could be too short. If it works like an LSD, then I don't know.

Proximity sensor only has a on & off switch, and it only sends an event when the state changes. So it can easily get "stuck" in one state. But it only starts listening when on a call. I haven't looked into it much.

I too am having the status bar issue since the last update. Not really much of a bother.

A few pages back, I posted about poor battery life. As luck would have it, after upgrading to the new version, clearing cache and dalvik cache again and installing BBS, life has improved quite dramatically. However, I've had a bad day again today. Nothing really sticks out for partial wakelocks, with the worst offender at a minute and a half.

However, under kernel wakelock, I have bq275x0 at almost 2 hours, and mmc_delayed_work a minute and 5 seconds shy of bq275x0. Phone has been off the charger for about 4 hours currently and am at 50%.


Otherwise, this is fantastic! Thanks

Also, any updates on using the compiled bits from the ideos x6 / cherry magnum 2.3 rom?

The bq275x0 is a battery process, 2 hrs wakelock seems odd. But I have noticed some weird wakelocks sometimes, events or something. I'll have to see if it stays in the next build. Maybe something got picked up in the CM sync that broke things.

Speaking of which, the status bar may be fixed upstream in CM. I can't remember if I'm running a build that includes the fix, which was checked in 3 days ago. So I haven't noticed it.

https://github.com/CyanogenMod/andr...mmit/75cc792af262175d7a4b85352779fa0b69294d59

Next release build will have this fix included.

Check out Volume+ in the Market.

As a sidenote, quite a while ago I noticed that there were separate media volume settings for the speaker and headset. Did you add this, Whyzor?

I haven't done anything with the media volumes, I notice it's fine. And if I change the default level, it may break other things. So would rather not mess with it.
 
The danger with bumping the volume is if it ever decides to go back to unbugged full volume. As it is, when my Triumph is actually doing "full" volume, it distorts pretty badly with some songs, and I have to pull it down a few notches. Of course, the regular bugged full volume seems pretty flat and seems to lack bass, even if I bump up my speakers to compensate.
 
The danger with bumping the volume is if it ever decides to go back to unbugged full volume. As it is, when my Triumph is actually doing "full" volume, it distorts pretty badly with some songs, and I have to pull it down a few notches. Of course, the regular bugged full volume seems pretty flat and seems to lack bass, even if I bump up my speakers to compensate.

And that's why you go and get a pair of skullcandy earbuds :D. Or you could get some plug in speakers. I haven't noticed any lacking of bass with my skullcandys plugged in so I think using headphones or speakers are gonna be the best bet. The built in speakers aren't the greatest especially at loud volumes :/
 
And that's why you go and get a pair of skullcandy earbuds :D. Or you could get some plug in speakers. I haven't noticed any lacking of bass with my skullcandys plugged in so I think using headphones or speakers are gonna be the best bet. The built in speakers aren't the greatest especially at loud volumes :/
Should have clarified it was external audio. And I do have Skullcandys as well, although I don't use that much. The few times I have, when I have the once in a blue moon pause-play, my ears started bleeding. :eek:I haven't been bothered to change the head unit in one of my cars. It came with a Monster tape adapter. Doesn't do it with all songs, just certain bass heavy ones.
 
Should have clarified it was external audio. And I do have Skullcandys as well, although I don't use that much. The few times I have, when I have the once in a blue moon pause-play, my ears started bleeding. :eek:I haven't been bothered to change the head unit in one of my cars. It came with a Monster tape adapter. Doesn't do it with all songs, just certain bass heavy ones.

huh... i have a pair of skullcandy 50/50's and I use dsp manager and put bass boost to extreme and equalizer on bass booster then listen to some dubstep and I swear they shake! :D and I don't notice any distortion either, but then again with that much bass going thru my ears who know :p... I haven't tried with anything else though so yea... Maybe its your speakers? Or the tape adapter?
 
I don't understand why people feel the need to raise the volume to the point of "deafening" *mumbles something about "kids these days".*
 
I don't understand why people feel the need to raise the volume to the point of "deafening" *mumbles something about "kids these days".*

There is a known volume bug. Sometimes it's loud enough to hear and sometimes it's nothing but a whisper.
Occasionally, removing the headphone jack for a few seconds and replacing it will correct it, but other times it won't which makes volume enhancing apps like Volume+ (my preference) or DSP Manager necessary.
 
I don't understand why people feel the need to raise the volume to the point of "deafening" *mumbles something about "kids these days".*
I have mine connected to an FM transmitter in my car, and even if I don't encounter the volume bug, its often not quite loud enough.
 
huuuuuuuuuuhhhhhhhhhhh??????????????/

Not only dows that not help anything being discussed, but I have no clue if you have a question. Even simply typed "huh" doesn't clue anyone in on a thing.
Are you confused about something? Or just leaving a comment that isn't clear or helpful.
 
Not only dows that not help anything being discussed, but I have no clue if you have a question. Even simply typed "huh" doesn't clue anyone in on a thing.
Are you confused about something? Or just leaving a comment that isn't clear or helpful.
I think it was supposed to be a joke relating to the posts about pumping loud music into one's ears.
 
I don't understand why people feel the need to raise the volume to the point of "deafening" *mumbles something about "kids these days".*

It's not deafening if I can hear it :p. Anyways its not like I have a car with a sub (or a car at that) and am pumping bass through it.
 
I'm not saying the volume's the loudest-but I'm glad everyone understood I was making a joke about it. :P
The volume is usually adequate.Not extremely loud, and certainly not as loud even as my old Intercept. My earbuds isolate most sounds passively (I live in a major city and trains are generally the only things louder. And sirens) so I guess it's not as much of an issue.
 
i have the same issues with the sound and headphones sometimes loud enough to blow my eardrums out.......sometimes so quite i cant hear it.....the pause for 5 seconds or unplug and plug back in always used to work for me now it doesnt.......



edit.....on another note i have a question bout this rom......should i still moves apps to the sd card ike i did on 2.2 or just leave them cuz it seems ike all of them can now be moved?????
 
I would just install everything on the internal memory (there's about 1 gig available). It causes less app problems too.

Yep. Especially if they are apps you require to start immediately upon boot. Apps on the SD card are not available until a minute or so after boot up when the SD card is mounted. At least that's my experience. Apps like SetCPU, Incredicontrol, should ALWAYS be on internal memory not to mention the widgets that belong to an app will be unusable if moved to SD card.

(In my opinion, apps like Netflix, Fruit Ninja etc. can be on SD card no problem because those are typically only user initiated.) I would like to have all of my apps on internal memory but I have way too many apps to be able to do that ;)
 
Also, under Cyanogenmod settings there are settings for "Applications"
You can set it to "Internal", "External", or "Automatic"..
I believe Automatic will only moves apps that are supported by the applications developers to be moved to sd. In other words, apps that can be moved to sd on Froyo will automatically be moved to SD with this setting.

[and the obvious: Internal automatically installs ALL apps to internal memory.
External automatically installs ALL apps to SD card.]
 
Back
Top Bottom