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

Status
Not open for further replies.
Woa! Houston we have a problem!! A second ago i had 87% battery, i press the camera button and it like turns off, gets stuck on the white lg screen... so i take the battery out, turn it on and somehow i have 31% battery even though what i did was like a minute. WTF!!!

try reflashing?

Personally, I'd try charging it to 100% with phone off, boot into recovery, and wipe battery stats under advanced menu (if you have CWMA recovery).
 
I switched to Nrom meanwhile... too many bugs here. Even though its the best rom out there it wasn't the best for me. Keep improving this and I will show this to all my friends.
 
Loving the new nightly. The proximity sensor seems to be much better...no need to swipe my finger across the Sprint logo to get the screen to come on during a call. Headphones seem to work a lot better, allowing both music and in-call sound to come through no problem. Headset mic is still a no-go (I tested with my wife, fiddling around and saying "can you hear me now" more times than that Verizon guy), but it's getting a lot closer.

Thanks a ton! Keep up the great work!
 
I'm pretty sure he has the VC radio. When I last corresponded with him he had done the process of rooting and upgrading to VC "blind", ie with blank screen.

It is not that there is a newer release of software. There is a newer release of hardware with a new LCD display which requires drivers made available in VC.

The symptoms of not having those drivers is the phone boots fine, the touchscreen works, you just have a blank display.

Since he is seeing the blank screen, there is the possibility this driver has not been included in the kernel CM7 GB is based on.

eh both the kernel and the files we use in CM7 are copied from VC so idk.
well to elaborate, the xionia kernel is 008 which uses vc drivers.

the blank screen thing is possibly just LGE's answer for our hacks :P
 
How odd. This time around I'm having proximity issues with the screen not turning back on lol. Other than that great so far!

Sent from my LS670 using Tapatalk
 
How odd. This time around I'm having proximity issues with the screen not turning back on lol. Other than that great so far!

Sent from my LS670 using Tapatalk

I had that problem too initially but a quick reboot fixed it..
 
Is there a way to get swype and the lg keyboard from lego rom to work on this because that'd like the only reason I don't use it
 
i think we also need a list of heroc/evo/cm7 bugs so that ya'll arent sending me on a wild goose chase to fix stuff that even the pros that ported for the evo/hero/other sprint devices couldn't fix, that'd be helpful and less stress on me.....

this is one of the reasons im mostly focusing on stuff I *know* is Optimus specific like libaudio, the camera zoom, ect.

Stuff like Sprint Provisioning, Three Way Calling, Google Maps, Sprint Voicemail, and other sprint-specific stuff that is likely broken on all AOSP roms I tend to ignore, especially if I can confirm the issue exists on another sprint device.

Remember the goal of this port is to bring us up to CM7, not to 100% port 2.3.3 to the Optimus.

You are going to have to wait for LGE for that one.

Now granted, if something like 3-way calling works on both CM7 HeroC and EVO then that makes it a Optimus Specific bug, but stuff like Sprint VVM, and provisioning are not my goal.

Once we have reached the same stability as the other Sprint devices, then we can worry about trying to fix everyone else's problems :P
 
newest nightly runs alot better. was having alot of issues with calls and the screen staying off/ freezing the phone. works much better now, screen wakes right up when i take out away from my face or end a call.
 
So who else is having proximity sensor issues? The "Always Use Proximity" hack worked fine, until 302, (the 2.3.3 update). In both 302 and 307 now, "Always Use Proximity" seems to affect nothing, and the sensor is giltchy coming out of calls again. A full data wipe, /system format, cache/Dalvik wipe and fresh flash of 307 didn't change it.

Just want to make sure it's more than just me before I go updating the issue tracker...

Edit: Seems like it's working better for some, worse for others?
 
So who else is having proximity sensor issues? The "Always Use Proximity" hack worked fine, until 302, (the 2.3.3 update). In both 302 and 307 now, "Always Use Proximity" seems to affect nothing, and the sensor is giltchy coming out of calls again. A full data wipe, /system format, cache/Dalvik wipe and fresh flash of 307 didn't change it.

Just want to make sure it's more than just me before I go updating the issue tracker...

Edit: Seems like it's working better for some, worse for others?

yea same here hasnt worked in awhile for me. thats the major issue that i hope gets fixed soon. but im not complaining. love this rom dev are doing a great job. patience is key
 
works fine here perhaps the ones with issues have v9 radio?

I can confirm the issue, with clean screen (ocd about that) and vc. Sometimes it works, sometimes even swyping the sensor doesn't wake the screen back up.

Edit: this is after a clean install of newest version, 03072011

Sent from my LS670 using Tapatalk
 
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
957,383
Messages
6,972,707
Members
3,163,782
Latest member
Ephraim