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

[zefie]

Well, I did a "sysctl -a" and looked up each feasible value that wasn't network related... I'm not seeing anything sensor-related. But now I understand development frustration... Since I've spent an entire 30 minutes on this

now go 30 hours and you'll see why I sometimes snap. lol

 

[timkaetzel]

now go 30 hours and you'll see why I sometimes snap. lol

Quite understandable!

Well, as I said, I only dabble in this kind of stuff and I'm pretty n00bish with Linux-related things, but if there's any sort of monotonous task in the project like that, hit me up and I'd be more than happy to throw my hand in. Your work has been massively appreciated by all.

 

[zefie]

nothing really at the moment only thing delaying me in releasing nightly is the fact I had to keep starting over..

first time my VM ran out of RAM, so I give it more RAM
second time my wifi dropped, so I switched to wired
third time I ran it under screen just in case my wire dropped magically lol, is still going

anyway yeah it delays me because I don't like to take a chance with a dirty build so if it gets interrupted I clean it all out and start over.

then we get to hope the updater-binary issue is fixed lol

 

[ichihollow]

im am chewing up batteries and I need a good app to help. Wherer I work I go into roaming all day long. With thunderrom I used juice defender and got much bettery life. But it will nto work with gingerbread. anyone have a saver that works?

As an absolute last resort you can always go into airplane mode, this will allow for wifi, and bluetooth but no mobile network, i say last resort because you will have to come out of AP mode ever hour or so, thats how often i would come out of AP mode anyway, last resort but if you have to stay with GB and you don't have some method to be charging the phone at work, then thats all i can suggest for you.

 

[simon.ponder]

I shouldn't have added the line about the add into the rom. My fault, and I am gonna modify that post. Testing different values gave me different results so I am unsure if its really placebo or somewhat related even if it's just barely related. A value of a thousand gave me a reboot at the end of the call. 5 or less made the issue worse.

That being said, you know a whole lot more about Linux/android than I do and I will accept your explanation.

Sent from my breaded GingerNook...

 

[zefie]

have fun whenever it uploads. if the zip doesnt work use cwma .6 because i tested it it worked it just didnt update progress

 

[heckja11]

Is it safe to say that we need to be on VD to use the new nightly? (Because of the Xionia v013 kernel)

 

[00_wrath_00]

do i have to reinstall the Xionia v013 kernel after i flash?

edit: no i didnt answered my own question

 

[ichihollow]

Is it safe to say that we need to be on VD to use the new nightly? (Because of the Xionia v013 kernel)

can't answer this fully but v9 failed the install on v.5 cwma, will try installing v.6 and flash again in a bit


EDIT: can not install with cwma v.6 and v9 radio, this makes me really really sad...

EDIT2: because I never came back and fixed this post. This is not true, I just had tochange the name of the Tom, its length was causing a problem. I would also recommend anyone getting an unknown error 0 message in either thunderclap or xionia recovery try renaming the file something shorter and flashing it again.

 

[pitmasterme]

Sweet....flashed right over 03142011 nightly with cwma .5 and v10 experimental. Running great. Seems a lot smoother.... Thanks Zef!!

Vd'd ls670 with original LCD..



Sent from my LS670 using Tapatalk

 

[ichihollow]

not done tinkering, but original ls670 with venereal disease, cwma v.6 and still getting

(Unknown error: 0) installation aborted

not done tinkering be back in a bit

EDIT: Ok so where i'm at and what i've done.

wiped everything, data via recovery, cache, dalvik cache, data via .zip
tried flashing 317 nightly, error:0 install abort

that was all v9 from v.5cwma

restored from back up flashed v.6 cwma
same wipe procedure, same error:0 install abort

wipe procedure again, flash TR 1.2, once inside flash thunderc 1.1.0, preform nand and then contract venereal disease
... BRB

 

[hamagc]

Flashed nightly no prob. V9 baseband still. Running good as always

Sent from my LS670 using Tapatalk

 

[ichihollow]

Flashed nightly no prob. V9 baseband still. Running good as always

Sent from my LS670 using Tapatalk

... this makes me think

 

[donbudafuko]

can someone give a link to show me how to flash a rom an not have to install everything all over an lose all my saved game data

 

[hamagc]

I don't know if it makes a difference but I'm on cwma v.4

Sent from my LS670 using Tapatalk

 

[hamagc]

can someone give a link to show me how to flash a rom an not have to install everything all over an lose all my saved game data

Easy answer: use a good backup program that can restore data. A popular one is titanium backup.

Sent from my LS670 using Tapatalk

 

[ichihollow]

ok I am latest and greatest everything, with an original ls670. getting cannot open alsdkjfalkdsjflaksdjfasdlkjasdf.zip unknown error: 0 installation aborted.

 

[donbudafuko]

nice installed new custom recovery then the new nightly an it works very nice

 

[ichihollow]

ok I am latest and greatest everything, with an original ls670. getting cannot open alsdkjfalkdsjflaksdjfasdlkjasdf.zip unknown error: 0 installation aborted.

all i had to do was change the name... flashed in just fine, and now i've still got vd. After work later today, that will be gone...

 

[simon.ponder]

yeah coz its not really a kernel parameter it is an android parameter

even if it was a kernel parameter there would still need to be code in the framework to read the prop value and assign it to the kernel parameter.

If you are looking for kernel parameters look around in /proc maybe we can just write a number to a proc value and fix it? xD

Yeah, so after beating the $#!% out of my phone for about a minute (at least that is what it felt like as I had to swipe many times on the sensor to finally get it to wake up), I truly believe we were hoping for the best and adjusting accordingly so that we thought the sensor was better. Short phone calls never seemed to have a problem and the voice mail test that I did was just as successful, but who knows. I am done fuxing with it, must have been placebo, like you said.