ok so I have 106 DB good or bad an if bad how can j get it to be better I do only have like 1 or 2 bars
ARCHIVED: [DEAD ROM]The Scott Pilgrim ROM (CM7 Gingerbread, Zefie Edition)
- Thread starter zefie
- Start date
- Status
i enabled it on mine and seem to have better roaming service over all...seems to be alittle less sticky with some of the crappy sprint towers around me.
Check the first post, there's a link to a google issue tracker which should give you an idea.
I tried juice defender and seemed to make it worse. I had to uninstall to get better battery life. Anyone else with this issue?
Sent from my LS670 using Tapatalk
Sent from my LS670 using Tapatalk
Juice defender is a placebo effect, it rarely does more help than harm. Not really an issue.
I was just looking at zefie's github and noticed that some of the source was updated on 5/22 with comments about "starting over from latest mik9..." I'm gonig to compile it tonight and test it out a bit to see what changes where actually made. If all goes well, I will post it for others to use if they want. This is in no way any work of mine other than compiling it. Eventually I may try to stream line it and tie it in with latest CM source changes, but I don't have a lot of time for it at the moment.
I also noticed that android_device_lge_vm670 was added to Cyanogen github. With a few LS specific changes we should be able to build from CM directly. I belive the only changes that would have to be made would be the key layout and some system.prop edits. I think everything else is the same. I could be wrong though. I will check it out later tonight. Just have to load zefie's back on my phone to get the proprietary files.
I also noticed that android_device_lge_vm670 was added to Cyanogen github. With a few LS specific changes we should be able to build from CM directly. I belive the only changes that would have to be made would be the key layout and some system.prop edits. I think everything else is the same. I could be wrong though. I will check it out later tonight. Just have to load zefie's back on my phone to get the proprietary files.
Last edited:
Nice, I'm up to test once you get it compiled
Too bad my computers suck or I would start compiling as well
Too bad my computers suck or I would start compiling as well
wishing new more so I could help good with computers just not sure about this stuff or ware to start
I will have to wait until tomorrow to download the source. Internet is out here at the house and it looks like I will have to tether the source. Thank god for unlimited data 
Sent from my LS670 using Tapatalk
Sent from my LS670 using Tapatalk
When did zefie stop keeping this up? I am syncing with latest CM as I type and will upload a new build shortly. Unless of course zefie PM's me and tells me not to, I havent been on this site in a while, but if you look I am mentioned in the OP 
If you could up load a new build it would be amazing he broke his optimus s
Sent from my LS670 using Tapatalk
Sent from my LS670 using Tapatalk
looks like i hit a wall, the same wall as zefie did, i think....
GRRRRRRRRRRRR!
this is the way we built/compiled before. i dont know whay or why it has changed, or what it has changed to. breakfast does not work either...
Last edited:
Looks like you need to take out some of the thunderc targets from the config file. I also remember seeing one of the mk files being changed to lunch full_eng. I am having issues syncing source right now or I would try it out, but maybe try lunch in stead of brunch. I have no clue what the differences really are. I'm still trying to get into this dev stuff, lol.
I have tried them all, its driving me crazy! It used to be easy to dump a nightly, never got errors like this. I even tried with my old git and got the same crap. It doesnt help that I dont even have this device anymore either. I will keep looking into as time allows. If anyone finds/knows a solution please post it
Same errors I was getting. AOSP somehow got his to sync though, because AFAIK, he used the device tree from the Optimus S. I've contacted AOSP to see if he could link me the source that he used, but he hasn't replied in about 2 weeks
Same errors I was getting. AOSP somehow got his to sync though, because AFAIK, he used the device tree from the Optimus S. I've contacted AOSP to see if he could link me the source that he used, but he hasn't replied in about 2 weeks
AOSP is the exact opposite, should be ACSP. Android Closed Source Project! At one time his source was requested for the HeroC and he denied it, didnt ignore the request, just said NO. It wasnt some n00b requesting either, it was Deca! Cold Hearted if you ask me, but things may have changed...
maybe we can find his git, fork it all and post online
How long did it go before you got the error? Just wondering because mine is compiling and has been for about 45 minutes. Then again, I forgot to dump the proprietary files too. So, I'm not sure what will happen. I only have 1gig of ram so I am compiling at a slower rate. Once it is finished I will double check that the changes listed on his github took effect, flash it and pray. If that goes well I will post it for testing.
Sent from my LG-VM670 using Tapatalk
Sent from my LG-VM670 using Tapatalk
I got the error right away, I probably have stuff all messed up from compiling for Evo, and I started a aosp rom for thunderc right before I switched devices. Though I did sync everything, build enviroment looks good, just wont happen
corey@corey-desktop:~/android/system$ . build/envsetup.sh
including device/lge/thunderc/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
Hope you get it!!!
- Status
Similar threads
- Locked
Trending Posts
-
-
Phone Wifi connected without internet
- Started by marthaHoopkins1976
- Replies: 3
-
-
Questions about older phones and bad reception
- Started by njira
- Replies: 1
-
eSim only - Hard pass
- Started by chevyman29
- Replies: 18
Facebook
Twitter
Instagram