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

Status
Not open for further replies.
I would suggest either a google voice number or a skype number. Either should work with wifi only.

The technology is there, but there are no free all in ones yet. There is a way to set up calls with Sipdroid, some calls might still be a problem unless Skype to Skype, fringe to fringe, etc.

Lifehacker.com did an article on the Sipdroid setup.

EDIT - See here, they may have figured out more. I had the lifehacker setup on my phone. I tried this on my retired hero, couldn't get it to work.

Sent from my breaded GingerNook...
 
Last edited:
I made a thread somewhere on here. Search our section of the forum for voip.

Sent from my LS670 using Tapatalk
 
Problem is I looked Into springate but there not giving out new numbers I made it work through whistlephone and Google voice but I made it work oh and sipdroid ill post instructions in the morning. Thanks to all of u for ur help

Sent from my LS670 using Tapatalk
 
Problem is I looked Into springate but there not giving out new numbers I made it work through whistlephone and Google voice but I made it work oh and sipdroid ill post instructions in the morning. Thanks to all of u for ur help

Sent from my LS670 using Tapatalk

It appears internet calls are not working with cm7 settings :(
 
can somebody explain the steps a little better on how to install this rom coming from the latestest TRom, steps on the 1st few post got me a bit confused. ( i dont want to brick )
 
1) Back up your stuff. I recommend Titanium Backup, as it will also back up your SMS/MMS data and you can do a selective restore in case anything goes wrong (like, one of your apps doesn't play nice after the ROM switch). You'll also want a Nandroid backup, in case things go bad so you can just restore (should be a backup option in your custom recovery)

2) Wipe data/Cache in recovery

3) Flash the Debug/Format System zip in the first post

4) Flash the ROM

5) If you want Google apps, flash the Gapps zip that's included in the first post.

6) Reboot

Should now have the ROM on a clean installation; from here you can either restore your apps from Titanium backup, or just start from a clean slate and install from the market, once you've set your Google accounts up again.
 
  • Like
Reactions: omarnova
1) Back up your stuff. I recommend Titanium Backup, as it will also back up your SMS/MMS data and you can do a selective restore in case anything goes wrong (like, one of your apps doesn't play nice after the ROM switch). You'll also want a Nandroid backup, in case things go bad so you can just restore (should be a backup option in your custom recovery)

2) Wipe data/Cache in recovery

3) Flash the Debug/Format System zip in the first post

4) Flash the ROM

5) If you want Google apps, flash the Gapps zip that's included in the first post.

6) Reboot

Should now have the ROM on a clean installation; from here you can either restore your apps from Titanium backup, or just start from a clean slate and install from the market, once you've set your Google accounts up again.

thanks a million, this is alot clearer to me...tomorrow i shall be on gingerbread! thanks
 
Yep, just follow the steps, and you'll be fine. It's definitely worth checking out IMO.

EDIT: To avoid a double post, I'll just put this here. Anyway, I'm wondering about the new MIUI gingerbread rom that was released to a handful of devices. Would there be any effort to get this on the Optimus S? Of course I'd be willing to help where/how I can (which, at this point, is pretty much limited to bug testing and occasional fixes), but I'm lost in terms of the actual port. Just thought I'd bring up the idea, and see what kind of reaction it gets. Here are the devices that are supported right now, and this seems to be a start?
 
Last edited:
So I have been running two ROMS for a while now, but something surprised me today, and I am not sure why/how its happening. Usually I flash between the two every other day or so, to keep them both updated. I have the most recent kernel of zefies on both, and use his cwma version 6. I flash between the CM7 build and ThundeROM.

I flashed the 3/17 build and updated the apps on that ROM within a couple hours of it being released. I have not touched that ROM, until this morning. I was runing ThundeROM1.8.2, and this morning I flash formatted system, and factory reset from inside cwma, and restored to the backup of CM7 I had.

The (knock knock ... me knocking on wood) proximity sensor has not failed me once since 6 am when I recovered the ROM. Crazy huh?

Not a partial working, but the instance I move the phone from my melon, the screen comes back on. I wish I knew why it was working.

EDIT *** So, after about 20 hours of using this ROM, the proximity sensor started to act up again, and has become progressively worse. It almost makes you think that some setting is being stored somewhere and it's value is not being set correctly. ***

I find that after a day or two, the sensor acts up. But if I boot into recovery and wipe cache, it will go away again for a day or two.

It's dirty, but it has worked for me pretty consistently.
 
Ok I have tried searching and haven't come up with a fix that worked for me yet... I am having trouble getting a cell location. My GPS gets a fix just fine but when I turn GPS off it can't get a lock on anything. I allowed Google to track but its not... hmmm... any ideas? I am using 3-17-11
 
Hey zefie, any idea when the next nightly will be, or if you have taken a break from the project like you mentioned earlier that you would? No pressure, just wondering if I should wait to do a full wipe and reflash (in order to clean up my phone), or if i should wipe and reflash this nightly. Again, not trying to harass you. Thanks for all the work you do/have done.
 
Ok I have tried searching and haven't come up with a fix that worked for me yet... I am having trouble getting a cell location. My GPS gets a fix just fine but when I turn GPS off it can't get a lock on anything. I allowed Google to track but its not... hmmm... any ideas? I am using 3-17-11

I had this problem, WAY back in the forum a "fix" was found... worked for me, hopefully it helps you too...

MAY require full data AND system wipe
Upon fresh install of the ROM and gapps, it asks for permission to gather information (I forgot the exact wording), if you choose not to allow this, location finding through cell towers is broken. SO, allow this and problem should be resolved.
 
Problem with dialing numbers with a '+' in front of them

Ok, I'm relatively new to Android custom ROM's even though I've been flashing custom Windows Mobile ROM's since 2006 so, I'm not sure if this is a me problem or a ROM issue.

I have most of my contact phone numbers stored in the format +1 (xxx) yyy-zzzz However, whenever I try to dial a number in that format, I get a message stating 'Call has been lost.' But, when I dial the same number without the '+' sign, I connect just fine. I've been storing my numbers in this format since 2005 when I got my first Windows Mobile device and now I have hundreds of numbers in that format that I am REALLY not looking forward to changing. Since this format worked just fine with the ZV9, ZVC, and ZVD stock ROM's, I'm guessing that either I did something dumb when flashing or that this is just a problem in the current version of the ROM.

I appreciate any help that I can get here. Thank you ^_^

EDIT: I forgot to note that I'm using nightly version 20110317 of this ROM. Also I did remember to clear system, data, and cache/davlik cache from my device prior to installing this ROM.
 
Last edited:
Anyone know if there are any negative effects or charges if you accept the international roaming even though you're just roaming in the same country? I'm going out of state for a couple days where I normally roam but for me any roaming on CM7 is recognized as international roaming. I know it's a bug but trying to figure out if I should switch to another rom for the trip. Thanks.
 
1) Back up your stuff. I recommend Titanium Backup, as it will also back up your SMS/MMS data and you can do a selective restore in case anything goes wrong (like, one of your apps doesn't play nice after the ROM switch). You'll also want a Nandroid backup, in case things go bad so you can just restore (should be a backup option in your custom recovery)

2) Wipe data/Cache in recovery

3) Flash the Debug/Format System zip in the first post

4) Flash the ROM

5) If you want Google apps, flash the Gapps zip that's included in the first post.

6) Reboot

Should now have the ROM on a clean installation; from here you can either restore your apps from Titanium backup, or just start from a clean slate and install from the market, once you've set your Google accounts up again.

Just to add one thing to this, some app data may be lost with a titanium backup due to Froyo vs Gingerbread. I lost save game data when I went from CM 7 to TR. Hopefully all app data is forward comparable though. I'd be interested to know if you lose any if you do an app backup.
 
Just to add one thing to this, some app data may be lost with a titanium backup due to Froyo vs Gingerbread. I lost save game data when I went from CM 7 to TR. Hopefully all app data is forward comparable though. I'd be interested to know if you lose any if you do an app backup.

Almost positive that you are correct - app data restores fine, but system data will give you problems. I had many problems doing that myself, but when I stuck to app data and redid all my settings manually when it came to system data, all was fine.

Anyone know if there are any negative effects or charges if you accept the international roaming even though you're just roaming in the same country? I'm going out of state for a couple days where I normally roam but for me any roaming on CM7 is recognized as international roaming. I know it's a bug but trying to figure out if I should switch to another rom for the trip. Thanks.

Only reason you might not want to do that is if you live near a border (Canada or Mexico). Otherwise, I'd have it checked, as it gives me better roam reliability.

Ok, I'm relatively new to Android custom ROM's even though I've been flashing custom Windows Mobile ROM's since 2006 so, I'm not sure if this is a me problem or a ROM issue.

I have most of my contact phone numbers stored in the format +1 (xxx) yyy-zzzz However, whenever I try to dial a number in that format, I get a message stating 'Call has been lost.' But, when I dial the same number without the '+' sign, I connect just fine. I've been storing my numbers in this format since 2005 when I got my first Windows Mobile device and now I have hundreds of numbers in that format that I am REALLY not looking forward to changing. Since this format worked just fine with the ZV9, ZVC, and ZVD stock ROM's, I'm guessing that either I did something dumb when flashing or that this is just a problem in the current version of the ROM.

I appreciate any help that I can get here. Thank you ^_^

EDIT: I forgot to note that I'm using nightly version 20110317 of this ROM. Also I did remember to clear system, data, and cache/davlik cache from my device prior to installing this ROM.

Now that's interesting. Never heard of that before.. Does the same thing happen on an older nightly? In the OP you can see an archive of older versions. If that problem still happens, then it's a bug related to the latest nightly. Otherwise, which is what I'm leaning toward, it's a gingerbread thing. In that case, might as well start reworking all your contacts' numbers.. Gotta start sometime, right? PS... why have the +1 anyway, unless you do a lot of international calling??
 
Only reason you might not want to do that is if you live near a border (Canada or Mexico). Otherwise, I'd have it checked, as it gives me better roam reliability.

Thanks, so it doesn't matter if it sees it as international? (I'm smack in the middle of the states, no borders to worry about)
 
I find that after a day or two, the sensor acts up. But if I boot into recovery and wipe cache, it will go away again for a day or two.

It's dirty, but it has worked for me pretty consistently.

Saw this and thought I'd try.
Proximity sensor was basically nonresponsive for me. After calls the only way to get the screen back was to wait.

Booted into recovery and only wiped cache...proxy sensor starts working right....
 
ok so iv been running cm7 for awhil an iv been using adw launcher an iv notice that there are alotmof launchers out there like launcher pro. whats the best launcher that works well with this rom
 
Status
Not open for further replies.