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

Root [ROM][WIP] CyanogenMod 7 | Android 2.3.5 (Gingerbread) | Current Version: 09122011

KOLIO said:
The "LAZY" term is referring to whether your particular handset can tolerate the CPU being overclocked past it's original factory clocking of 600 MHZ.
The majority of ASCENDS can tolerate O/C up to 710 MHZ,a few more,(748 MHZ).
Unfortunately,some do not tolerate overclocking very well,to varying degrees.
That is why some updates of CM7 are available w/overclocking to 672 MAX(aka the LAZY version of a particular update).
The typical overclock maximum setting for ASCEND CM7 ROMS is 710,w/a few versions available @ higher overclocking for those fortunate enough to have one of the handsets that can tolerate the highest stable overclocking of 729 to 748 MHZ,depending upon which update is flashed.
Click to expand...

oooh okay thanks :)
 
my friend had his phone on the official metro pcs updated froyo, he rooted his phone trying put playfulgod latest build but know it will boot up right.. he is using the gapps on the the wiki i even did the wipe but still will not boot up when it get to the the spinning andriod it will reboot and say driod like 50 times. HELP ME OUT
 
wayne137 said:
my friend had his phone on the official metro pcs updated froyo, he rooted his phone trying put playfulgod latest build but know it will boot up right.. he is using the gapps on the the wiki i even did the wipe but still will not boot up when it get to the the spinning andriod it will reboot and say driod like 50 times. HELP ME OUT
Click to expand...

Wipe and format everything again and reflash. (Format everything except the sd card) then flash the gapps, the go to advanced and select fix permissions and reboot.
 
wayne137 said:
my friend had his phone on the official metro pcs updated froyo, he rooted his phone trying put playfulgod latest build but know it will boot up right.. He is using the gapps on the the wiki i even did the wipe but still will not boot up when it get to the the spinning andriod it will reboot and say driod like 50 times. Help me out
Click to expand...

droidddddddd :d
 
I have the latest version of cm7 the 091211 from here and when I go to make a call a get a dsp manager force close. After I close it I usually dont have a problem until I reboot my phone and then the first call it will close again. It doesnt affect anything that I can tell. I even wiped out and formatted everything and reinstalled fresh and i still get the force close on dsp manager when I place a call. Does anyone know why this is happening or how to fix it? Thanks
 
kevinmck2009 said:
I have the latest version of cm7 the 091211 from here and when I go to make a call a get a dsp manager force close. After I close it I usually dont have a problem until I reboot my phone and then the first call it will close again. It doesnt affect anything that I can tell. I even wiped out and formatted everything and reinstalled fresh and i still get the force close on dsp manager when I place a call. Does anyone know why this is happening or how to fix it? Thanks
Click to expand...


Go into CWM or ROM MANAGER & run "FIX PERMISSIONS".
 
wayne137 said:
my friend had his phone on the official metro pcs updated froyo, he rooted his phone trying put playfulgod latest build but know it will boot up right.. he is using the gapps on the the wiki i even did the wipe but still will not boot up when it get to the the spinning andriod it will reboot and say driod like 50 times. HELP ME OUT
Click to expand...
PlayfulMod doesnt require Gapps to be installed ;)
 
travioso said:
All cm7 builds take awhile to pinpoint location.. Sometimes a couple minutes.. Navigation usually syncs quickest for me.. Just gotta be patient with it..
Click to expand...

Wait till you see how fast the Esteems pin points! ahaha


A trick to pin point it faster enable the wireless location box above the gps box. It help some people
 
okay so i upgraded to the 0913 and i realized i wasnt receiving pictures from sprint and verizon users. then i flashed 0708 i think and i was getting pics from all users except for verizon.
 
Titowashere1 said:
okay so i upgraded to the 0913 and i realized i wasnt receiving pictures from sprint and verizon users. then i flashed 0708 i think and i was getting pics from all users except for verizon.
Click to expand...


Ive heard of a couple people having troubles receiving pics from certain carriers not sure what causes it and dont think anyone has found a fixx for it yet.
 
ShinySide said:
Wait till you see how fast the Esteems pin points! ahaha


A trick to pin point it faster enable the wireless location box above the gps box. It help some people
Click to expand...

Hehe rub it in why don't ya.. still waiting on fedex.. everytime a damn truck goes by i get excited for nothin lol..

but yeah enabling wireless location does speed it up to..
 
ShinySide said:
Ive heard of a couple people having troubles receiving pics from certain carriers not sure what causes it and dont think anyone has found a fixx for it yet.
Click to expand...

Yeah its weird.. Had issues with HTC and Iphones for awhile but now out of the blue they work.. Think it may have to do with all the upgrading Metro is doing.. Thats just a guess though.. I always run APN Manager though just to make sure Metro is enabled..
 
ShinySide said:
Ive heard of a couple people having troubles receiving pics from certain carriers not sure what causes it and dont think anyone has found a fixx for it yet.
Click to expand...


my friend has an iphone could that be the reason why? and my friend from sprint has a droid idk which on though and i wasnt getting the pics at all. and that was for the 09132011 update and then i flashed the 07082011 file and i wasnt getting pics from my friend who has verizon. i got pics from my gf who has att and then i was getting pics from my friend who has sprint. is it the phone or the phone carrier? also whne i flashed the 0913 file my phone kept rebooting and it kept foreclosing all the apps i opened.
 
I dont have an answer for the MMS. I never had the problem personally so Im not sure.

For the rebooting that could be caused by overclocking or when you wiped and formatted everything in CWR it didnt wipe everything. Also recommended to run fix permissions in CWR before rebooting after you flash the rom and the gapps.
 
You must log in or register to reply here.
Back
Top Bottom