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

[acromack]

Visual not working

Deatils?? Such as..

What baseband are you running? Is it a newer phone (that has different lcd drivers)? What recovery version are you using? Did you flash the latest nightly, or a previous one? Did you make sure everything was wiped before starting (by using the Debug-FormatSYSTEM.zip file in the OP?

There's a good amount of additional information we need to know before a solution can be found..

Also, there have been others in this thread reporting similar issues. I'd start there to see what has been done about it.

 

[gk1984]

Zefie, got a suggestion that might make CM7 feel less like work, keep you pace, and reduce our expectations. However, I doubt many people would like it.

Move this to a private beta maybe until the Optimus issues are worked out. Only invite people you feel won't overwhelm you and contribute to development. I'm happy with where it is now to be locked out if it would mean you come back, even if it is at a slow pace. I understand your phone is acting up too and you need more help developing. Wish I could help there. Thanks for the hard work.

 

[zefie]

Zefie, got a suggestion that might make CM7 feel less like work, keep you pace, and reduce our expectations. However, I doubt many people would like it.

Move this to a private beta maybe until the Optimus issues are worked out. Only invite people you feel won't overwhelm you and contribute to development. I'm happy with where it is now to be locked out if it would mean you come back, even if it is at a slow pace. I understand your phone is acting up too and you need more help developing. Wish I could help there. Thanks for the hard work.

nah anything private just spells deja vu.

i've just decided to work at my own pace regardless. ;p

 

[pitmasterme]

just reflashed cwma .5 flashed new nightly, gapps, rebooted, then flashed v10 anykernal(got no bootloop), set things up to my likings and am gonna try to make a back up again and see what happens....



and bootloop again...........

 

[junkshow]

just reflashed cwma .5 flashed new nightly, gapps, rebooted, then flashed v10 anykernal(got no bootloop), set things up to my likings and am gonna try to make a back up again and see what happens....



and bootloop again...........

I was having the same problem...for me, "set things up to my likings" meant that I restored settings with Titanium Backup. That was the root cause of my problems. I don't know which setting it is, but restoring SOME system setting from a Titanium Backup causes the bootloop. Using Titanium to restore user apps and data is OK, system settings seems to cause problems, at least for me, on CM7. My suggested fix:

reboot recovery
install/restore a CM7 ROM, gapps, etc.
install Xionia 010 AnyKernel if you want it (OPTIONAL)
wipe data/factory reset

boot CM7 (now a clean install)
install titanium backup
BATCH-> restore missing data
NOTE: uncheck Sprint and LGE apps that aren't necessary on CM7)
NOTE 2: you CAN safely restore SMS/MMS...I have done so on my working configuration
set up system preferences manually in Settings

If you want to use Titanium Backup for system settings, you should probably use a different backup directory for CM7 than you do for Froyo builds (stock, ThundeROM, nROM, etc). I THINK the problem is caused by restoring froyo settings onto CM7

 

[gk1984]

nah anything private just spells deja vu.

i've just decided to work at my own pace regardless. ;p

Alright, well... if you go that route in the future, i won't blame ya. Was just thinking it might filter out some of those causing more headaches than anything.

 

[pitmasterme]

K

I was having the same problem...for me, "set things up to my likings" meant that I restored settings with Titanium Backup. That was the root cause of my problems. I don't know which setting it is, but restoring SOME system setting from a Titanium Backup causes the bootloop. Using Titanium to restore user apps and data is OK, system settings seems to cause problems, at least for me, on CM7. My suggested fix:

reboot recovery
install/restore a CM7 ROM, gapps, etc.
install Xionia 010 AnyKernel if you want it (OPTIONAL)
wipe data/factory reset

boot CM7 (now a clean install)
install titanium backup
BATCH-> restore missing data
NOTE: uncheck Sprint and LGE apps that aren't necessary on CM7)
NOTE 2: you CAN safely restore SMS/MMS...I have done so on my working configuration
set up system preferences manually in Settings

If you want to use Titanium Backup for system settings, you should probably use a different backup directory for CM7 than you do for Froyo builds (stock, ThundeROM, nROM, etc). I THINK the problem is caused by restoring froyo settings onto CM7

Good call.....I'll give that a shot. Thanks!

Sent from my LS670 using Tapatalk

 

[shawnirwin]

Does the hotspot widget work for anyone? I want to tether my Wii but the Wii doesn't work with ad-hoc.

 

[zevot]

I changed the option below in the build.prop file and in my limited testing it seems to help with the proximity issues a bit.

ro.lge.proximity.delay=200

The original value was 100.

 

[glitchsta]

Proximity has been working fine for me with the latest builds...

 

[simon.ponder]

Proximity has been working fine for me with the latest builds...

Which build, and the screen comes back on as soon as you get several inches from your face during a call? Anything special with this build (Clean Wipe, four hail mary's, or stood on your head for ten minutes during wipe, flash, and restore)?

You get the idea...

 

[acromack]

I changed the option below in the build.prop file and in my limited testing it seems to help with the proximity issues a bit.

ro.lge.proximity.delay=200

The original value was 100.

If this has any effect, wouldn't it be a lower number that you should be replacing it with (so the delay is shorter)?

 

[rc28a]

I bought my phone the week it came out back in November so I have the original phone and proximity sensors work with no problems for me in all the cyanogen releases


any rate I think we should have our own subforum on here with each issue getting its own thread otherwise going through 134 pages is a lot to handle for someone new

 

[ichihollow]

I changed the option below in the build.prop file and in my limited testing it seems to help with the proximity issues a bit.

ro.lge.proximity.delay=200

The original value was 100.

guide, or do you have a build.prop we can just flash

 

[shortyjacobs]

guide, or do you have a build.prop we can just flash

2nded...can't figure out how the tits to edit a buildprop....I can open it, but can't save it.

 

[timkaetzel]

guide, or do you have a build.prop we can just flash

Thirded - I've been trying to figure out how to edit and save build.prop... I must be really bad at Google

 

[pitmasterme]

I was having the same problem...for me, "set things up to my likings" meant that I restored settings with Titanium Backup. That was the root cause of my problems. I don't know which setting it is, but restoring SOME system setting from a Titanium Backup causes the bootloop. Using Titanium to restore user apps and data is OK, system settings seems to cause problems, at least for me, on CM7. My suggested fix:

reboot recovery
install/restore a CM7 ROM, gapps, etc.
install Xionia 010 AnyKernel if you want it (OPTIONAL)
wipe data/factory reset

boot CM7 (now a clean install)
install titanium backup
BATCH-> restore missing data
NOTE: uncheck Sprint and LGE apps that aren't necessary on CM7)
NOTE 2: you CAN safely restore SMS/MMS...I have done so on my working configuration
set up system preferences manually in Settings

If you want to use Titanium Backup for system settings, you should probably use a different backup directory for CM7 than you do for Froyo builds (stock, ThundeROM, nROM, etc). I THINK the problem is caused by restoring froyo settings onto CM7

Thanks again man. No more bootloop!

Sent from my LS670 using Tapatalk

 

[O.a.T.]

2nded...can't figure out how the tits to edit a buildprop....I can open it, but can't save it.

Notepad++

 

[debh945]

I use Root Explorer. Mount R/W, then long press on the build.prop > open in text editor. Make your edits and then press menu > save changes.

 

[shortyjacobs]

Notepad++

Sorry, should have been clearer, trying to do it on my phone.

I use Root Explorer. Mount R/W, then long press on the build.prop > open in text editor. Make your edits and then press menu > save changes.

This is probably much easier than the method I just attempted. I opened up a terminal emulator and did:

su
busybox cp /system/build.prop /sdcard

then went in with the efile editor and edited the build.prop on my sdcard. Then back into terminal emulator

su
mount -o remount,rw -t yaffs2 /system /system
mv /system/build.prop /system/build.prop.bak
busybox cp /sdcard/build.prop /system
chmod 644 /system/build.prop
mount -o remount,ro -t yaffs2 /system /system

then rebooted.

I don't know if the mount instructions were necessary, but it worked! I'm too cheap to buy root explorer.