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

Root [ROM][FINAL] CM7 7.2 RC1 - g60 style [7.11.12]

Attention endless barrage of questions! You will be answered shortly! I am working on drafting up some documentation for this ROM, but please be patient. I only have time on the weekends! I will attempt to sort out what is a bug and what is just a fixable problem. If I can't answer your question, I'm sure that one of the more experienced members here at Android Forums would be glad to. Luckily, even though I cannot yet program, I consider myself a power user, and can probably answer 80% of your questions. I will try my best since g60madman needs this time so he can work on fixing HDMI.
 
sqwerl said:
One other more serious thing...
In the past when I've installed fresh ROMs, I could open Google Play and Tapatalk would be a purchased download so I would never have to pay since my original purchase. Now, when I open My Apps, all of my previously downloaded apps are listed but Tapatalk is $2.99.
Click to expand...
Are you signed into your Google Account yet? If this is happening after a fresh wipe, shoot the dev an email and I'm sure he'll be glad to respond.
 
EHokie said:
I can't get the volume fix to work. In build 0.2 I could pause for 5 seconds when the bug occurred and it went back to full volume every time without fail.

Today I flashed the new Codename Android rom briefly, went back to 0.2 and it didn't work. Now on 0.3 it still doesn't work...

I loved you for what you'd done when it was working. Help, someone!
Click to expand...
Have you performed a full wipe of the data and cache yet? Make sure you backup first! You may have to go step by step in doing the recovery manually if you need to do a fresh install. (All of your old apps will be available if you swipe left under My Apps in the Play Store). It probably happened because you flashed two completely different ROMs over top each other. No worries though, I make the same mistake myself from time to time.
 
MikeRL said:
Are you signed into your Google Account yet? If this is happening after a fresh wipe, shoot the dev an email and I'm sure he'll be glad to respond.
Click to expand...
Yes I was signed in to my account because I could see my previously downloaded apps. I cleared the Google Play app cache and data so it synched correctly when I reopened it.

It may have had something to do with the fact that when I switched themes I immediately was shown the Google android with the "Touch here to begin..." message. I chose to skip because I had already setup my account.
 
As for your brightness issue, I'm not particularly sure on how to fix it. You could try tweaking the settings under Cyanogenmod Settings > Display > Automatic Brightness. Or something like that. It may be a hidden value somewhere. If this issue persists, I could file it as a minor bug.
 
MikeRL said:
Have you performed a full wipe of the data and cache yet? Make sure you backup first! You may have to go step by step in doing the recovery manually if you need to do a fresh install. (All of your old apps will be available if you swipe left under My Apps in the Play Store). It probably happened because you flashed two completely different ROMs over top each other. No worries though, I make the same mistake myself from time to time.
Click to expand...

Isn't working...
 
EHokie said:
Isn't working...
Click to expand...

EHookie,

viget had the same issue. The fix was the following

Before starting read the instructions first. Make sure to download the newest version of gapps as well as the froyo ROM and then boot into CWM

Stock Froyo ROM
http://www.mediafire.com/file/zgp2i5svyhjdvcv/Stock_ROM_SplashImage_b_randon14.zip


1. Wipe Data/Factory Reset
2. Wipe Cache partition
3. Mounts and Storage Menu < Format System
4. Advanced < Wipe Dalvik
5. Install Froyo Rom
6. Reboot in to Froyo
7. Once in Froyo Shutdown
8. Boot back into CWM
9. Wipe Data/Factory Reset
10. Advanced < Wipe Dalvik
11. Install cm7 g60 current version
12. Install gapps
13. Reboot system but do not install any apps

Test sound by playing music and while the music is playing go into settings < sounds and mess with ring tones and also notifications to play tones over the music. The music should not change volume level. Once that is verified then install one app at a time and test again to find out what app is causing the issue.

I know this is a long played out fix but one of the apps you are installing is causing the problem. Here is what vaget found out

viget said:
Hey,

I've just found the way to replicate the problem.
There is a game called "brain age test free."
Just open that game and exit out; the audible selection goes mute.
Works all the time and works on both Go launcher and AWD.

I'll also post this on the thread.

Thank you very much good man.
Click to expand...
 
MikeRL said:
As for your brightness issue, I'm not particularly sure on how to fix it. You could try tweaking the settings under Cyanogenmod Settings > Display > Automatic Brightness. Or something like that. It may be a hidden value somewhere. If this issue persists, I could file it as a minor bug.
Click to expand...

It is normal behavior of the Auto setting.
 
g60madman said:
EHookie,

viget had the same issue. The fix was the following

Before starting read the instructions first. Make sure to download the newest version of gapps as well as the froyo ROM and then boot into CWM

http://androidforums.com/triumph-al...eodex-roms-triumph-now-resets-splash-img.html


1. Wipe Data/Factory Reset
2. Wipe Cache partition
3. Mounts and Storage Menu < Format System
4. Advanced < Wipe Dalvik
5. Install Froyo Rom
6. Reboot in to Froyo
7. Once in Froyo Shutdown
8. Boot back into CWM
9. Wipe Data/Factory Reset
10. Advanced < Wipe Dalvik
11. Install cm7 g60 r0.3
12. Install gapps
13. Reboot system but do not install any apps

Test sound by playing music and while the music is playing go into settings < sounds and mess with ring tones and also notifications to play tones over the music. The music should not change volume level. Once that is verified then install one app at a time and test again to find out what app is causing the issue.

I know this is a long played out fix but one of the apps you are installing is causing the problem. Here is what vaget found out
Click to expand...

Couldn't I just delete apps from what I currently have? Or is it that once you install an app it automatically causes the problem permanently?
 
Ok, here's a weird one. When I launch the browser from the app drawer, it is fine. When I put it on the main screen or the dock, it launches You Tube. Tried deleting it off the dock and screen, moving it again from the app drawer, still only launches You Tube. Any thoughts?
 
Bull Shark said:
Ok, here's a weird one. When I launch the browser from the app drawer, it is fine. When I put it on the main screen or the dock, it launches You Tube. Tried deleting it off the dock and screen, moving it again from the app drawer, still only launches You Tube. Any thoughts?
Click to expand...
Try clearing the data for the Browser under Settings > Applications > Manage Applications > All Applications > Browser.
 
EHokie said:
Couldn't I just delete apps from what I currently have? Or is it that once you install an app it automatically causes the problem permanently?
Click to expand...

Hard to say. It's possible if the app changed some setting that may stay that way even after uninstalling. Hence it didn't change when you rolled back to r0.2
 
Bull Shark said:
Ok, here's a weird one. When I launch the browser from the app drawer, it is fine. When I put it on the main screen or the dock, it launches You Tube. Tried deleting it off the dock and screen, moving it again from the app drawer, still only launches You Tube. Any thoughts?
Click to expand...

i think that's a site you were looking at before you closed the browser, then you have YouTube set as the default playing method for the video.
I would reboot, if the problem persists, I would check my Home Page to see what it points to. It could be a bad link. Send your self an email or text with a link so you could follow it.

As a last resort, reflash.
 
I think I finally have the random reboot issue narrowed down. After doing some debugging, it seems that many apps seem poorly written. There is a constant slew of major and kernel faults in aLogcat, especially with this one app, which helps explain the random reboots I'm getting with that app. I wonder if I should inform the developer of this app about the kernel faults? (I still don't have an aLogcat of right before a reboot) P.S. is there any way I can get the error that caused the reboot to be dumped anywhere, so I can get to the bottom of these things? They're driving me nuts! And I plan to look into the cause so I can let app developers know. And yes, I've wiped time and time again. I have no other problems with Android besides troubleshooting the random reboots.
 
I just reported three new feature enhancement/minor bugs. Take note that these are not of bleeding importance, but it would be nice to see some of them (if g60madman wants these feature requests put in, that is) incorporated into the next release, if possible.
 
g60madman said:
Yeah you will need to go to

Settings < CyanogenMod settings < Interface < Status bar tweaks < Battery status style < percentage
Click to expand...

If you toggle percentage to bar then back to percentage you'll see the percentage and small bar if anyone isn't aware of it. This isn't a bug that I know of because CM7 TGR did this also.
 
This release is so damn sexy that it pains me to ask...anyone else still getting the in call proximity black screen? I'm hoping no, so I can blame it on my hardware and call VM for my 1st replacement phone ;^)
Great work sixty! I'm very much used to that particular bug, don't kill yourself.
 
Bruce777 said:
This release is so damn sexy that it pains me to ask...anyone else still getting the in call proximity black screen? I'm hoping no, so I can blame it on my hardware and call VM for my 1st replacement phone ;^)
Great work sixty! I'm very much used to that particular bug, don't kill yourself.
Click to expand...

Glad your enjoying it :D The screen stays black for me while I am on the call and as soon as I move it from my face it lights up so I can use the dial pad. So far I have not had any issues with the proximity after I updated the kernel with mantera's fix!

Edit: You may want to try a wipe factory, cache, dalvick and reload.
 
g60madman said:
Glad your enjoying it :D The screen stays black for me while I am on the call and as soon as I move it from my face it lights up so I can use the dial pad. So far I have not had any issues with the proximity after I updated the kernel with mantera's fix!

Edit: You may want to try a wipe factory, cache, dalvick and reload.
Click to expand...

Ok I'll try a fresh install. Thanks again!
 
thangfish said:
Hey, madman... I know this is off topic, but your handle...
Do you drive one of those super charged VWs?
:D
Click to expand...

LMAO! Funny enough I used too back in 1998-2000, used to have a 1991 g60 Corrado and I used to drive it like a madman and also had a custom logo put on the windshield that said g60 Mad Man. The handle just kind of stuck after that. Sure do miss that car, I always enjoyed watching the spoiler come up at 45 MPH. I chipped it, did the ram air intake and had a smaller pulley installed. Was a fun ride :cool:
 
You must log in or register to reply here.
Back
Top Bottom