ARCHIVED: [DEAD ROM]The Scott Pilgrim ROM (CM7 Gingerbread, Zefie Edition)

Status
Not open for further replies.
Are you using CWM recovery? If so, if you ever get stuck at the boot screen, try running the Recovery Boot Loop fix. It's helped me before even when it wasn't automatically going into the recovery. Also, I've had times where the phone would do the first boot in like 30 seconds, and times where the first boot would take 5 minutes. I still suggest wiping data as well as cache, but not formatting /system when upgrading from 317 to 327. Also, I'm not sure if it helped me or not, but make sure if you are using CWMR that you have the newest version installed (1.2518.6).
 
Are you using CWM recovery? If so, if you ever get stuck at the boot screen, try running the Recovery Boot Loop fix. It's helped me before even when it wasn't automatically going into the recovery. Also, I've had times where the phone would do the first boot in like 30 seconds, and times where the first boot would take 5 minutes. I still suggest wiping data as well as cache, but not formatting /system when upgrading from 317 to 327. Also, I'm not sure if it helped me or not, but make sure if you are using CWMR that you have the newest version installed (1.2518.6).

My suggestion in the order listed...

1. Nandroid backup of your existing setup
2. Debug format all zip
3. Wipe data/cache (keep in mind format all doesn't wipe sd card stuff like android_secure)
4. Install current nightly
5. Reboot into android
6. Reboot back into recovery then flash gaps
7. Reboot back into android.

This has always worked for me when random stuff stopped working.
 
I flashed the 3-27 nightly last night and my prior issues with geolocation have gone away which is very nice. So this is pretty darn close to a daily driver for me now if only the bluetooth for calls worked. I know that it has never worked but is it being worked on? Also, can anyone recommend a good wired headset? I (or rather the people I have been calling), have been getting more and more frustrated with bluetooth for calls anyway.

Sorry to burst your bubble, but I have a wired headset and the mic doesn't work for this phone either. The headphone part works fine. But I haven't tried the latest build to say it doesn't work on that 1 yet.
 
So, is it safe to say that enough people are content with their speakerphone volume that we won;t expect any future updates to help the problem?
 
Sorry to burst your bubble, but I have a wired headset and the mic doesn't work for this phone either. The headphone part works fine. But I haven't tried the latest build to say it doesn't work on that 1 yet.

Ah hell... my bubble is burst. So what do you all do in the car? Speakerphone?
 
Ah hell... my bubble is burst. So what do you all do in the car? Speakerphone?

Either that or just talk like normal. Like a boss.


Out of curiosity, is there a changelog for 03272011 anywhere?

The running list of fixes on the OP sortof acts as such..


EDIT - anyone have weird issues with the screen-on animation? For me it flashes on then off then does the animation, all very quick. Everything else performs fine, and I've rewiped/flashed numerous times, to no avail. Not a huge issues, but it did look pretty cool. I flashed back to 17 and it works as expected, but a flash to 27 does this. Flashing to nandroid of set up 27 as well as a fresh flash of it both yield the same results.. Odd..
 
Last edited:
Either that or just talk like normal. Like a boss.




The running list of fixes on the OP sortof acts as such..


EDIT - anyone have weird issues with the screen-on animation? For me it flashes on then off then does the animation, all very quick. Everything else performs fine, and I've rewiped/flashed numerous times, to no avail. Not a huge issues, but it did look pretty cool. I flashed back to 17 and it works as expected, but a flash to 27 does this. Flashing to nandroid of set up 27 as well as a fresh flash of it both yield the same results.. Odd..

Lol jerk...you broke my phone! I didn't have the animations enabled, and no problems without them enabled, so I turned them on. Sure enough, screen on animation is broken as you say.

So I turn them back off. Screen off animation goes back to normal fadeout, but screen on animation stayed broken... weird.

Edit: a quick recovery reboot and clearing cache and dalvik fixed my problem at least.

Sent from my phone...excuse the spelling mistakrs.
 
Last edited:
Oh well, like I said, not the biggest problem. Nice to look at tho lol.. But I'll take that in exchange for working wifi AP..
 
My screen won't turn off when I press the power button anybody else having this issue

Sent from my LS670 using Tapatalk
 
on the latest build, when i try to use the native hotspot utility, the phone resets itself
if nobody has any ideas, i'll probably reflash tomorrow night to see if that solves it
 
Last edited:
Both posts above me, I would reflash.

There is no reason I can think of for the screen not turning off. Does it time out? Any apps that control screen?

For the wifi, it restarted the device the first time I tested it and it was fine after that. Also check overclock settings. Still having a problem, then reflash.
 
Hate to ask a repetitive question since I've seen it on this thread many time, but I did a seach on this thread for battery life and there are way too many options that don't answer my question. - Can anyone point me in the right direction on how to stop this ROM from sucking the life out of your battery so quickly? I know it's a known issue (so no need for reminders), but I also tried the thread on using #*#*4636*#*# or whatever is it and it didnt do anything for my battery life. I'm wondering if there is another fix. Thanks
 
Hate to ask a repetitive question since I've seen it on this thread many time, but I did a seach on this thread for battery life and there are way too many options that don't answer my question. - Can anyone point me in the right direction on how to stop this ROM from sucking the life out of your battery so quickly? I know it's a known issue (so no need for reminders), but I also tried the thread on using #*#*4636*#*# or whatever is it and it didnt do anything for my battery life. I'm wondering if there is another fix. Thanks

I'm still trying to get a battery benchmark for myself.. Just took it off charger now stop I'll give a better answer tonight but I would first check what apps you got running in case there's something sucking up the juice there..I found there was a big with handcent Sms that made it kill my battery in hours after trying to receive a video mms. I'm also thinking the 4636 trick is largely ineffective now, but like I said, I'll try to get a typical reading today..
 
I'm still trying to get a battery benchmark for myself.. Just took it off charger now stop I'll give a better answer tonight but I would first check what apps you got running in case there's something sucking up the juice there..I found there was a big with handcent Sms that made it kill my battery in hours after trying to receive a video mms. I'm also thinking the 4636 trick is largely ineffective now, but like I said, I'll try to get a typical reading today..

Appreciate the follow-up. Thanks!
 
Status
Not open for further replies.