yashsingh1/xdaforums huggingface dataset:
[Vibrant General] zephiK:
This is the lagfix I use: http://android.modaco.com/content/s...fix-using-internal-memory-and-playlogo1-hack/ If you have Vibrant6 then just use ADB and type the commands in.

I prefer this lagfix,

compared to RyanZA.. since I actually get more app space, Will I use it all? No. but its nice for whatever reason.

Quadrant Benchmarks:

Stock Kernel.

But when I did use RyanZA.. I didn't notice any battery life drains, so it's most likely something else.
[Vibrant General] drhonk:
I have the lag fix installed and haven't seen any difference in battery drain.
[Vibrant General] DriftorX:
Im pretty certain i know i was doing.

The first phone was not even me at all. It was like that out of the box. Brought the phone home, put in my sim and nothing, no carrier network lock. Thought it might of been the sim card itself. Went to tmobile corp store and showed the phone and swapped out for new sim. It had the same issue.

Second phone carrier network locked fine. First thing i did was root it. Piece of cake. than did the lag fix.. no issues after install, than installed setcpu and juice up on it. after i set them up the phone would still get extremely hot and than basically reboot on its on even when i had setcpu clocked down to 800. 400 when screen is off. Even than when i did that the phone would go into a deep sleep and never come out unless i battery pull. uninstalled juice and setcpu seem to work where it wouldn't reboot, but still get extremely hot, not even being on it for 5-10 minutes. Than started to setup my emails and other apps and apps where forcing to close and freeze. phone calls would work but the screen would freeze where i could not get to the dial pad to enter numbers and look for contact info while on the phone, and than one day i was on the phone for like 2 minutes and the phone complete rebooted into the vibrant boot screen and loop at that only never getting past the vibrant boot screen image. It would just blank and go back to it, blank and go back. Took it back to tmobile and they never seen that happen.

Swapped out for third one now. Rooted but no lag fix and installed all same apps i use and emails etc.. and phone works flawless. So i don't think the lag fix is a necessity for me to use at this time. Only thing i saw with using it was that it open apps quicker. I dont see a huge point for me to use that if thats all it does. I dont see any other advantages of using lag fix at this time.
[Vibrant General] bauerlucas:
That's bad luck you made it sound like you briked your 2nd one installing the lag fix. I have not had any problems with my vibrant besides the gps. Well good luck man.
[Vibrant General] ttabbal:
Ummm... That IS the RyanZA fix, just without the scripts to make installing it easier.

I've used all the lag fixes, and run without one. The battery doesn't really change with them. The biggest problem I've found is that something in the System process occasionally goes nuts and runs at 100% all the time. The phone gets hot and the battery drains very fast. You can see it if you get the System panel app and scroll to the bottom. Rebooting fixes it, so it's probably just a firmware bug.
[Vibrant General] zephiK:
Oh it is? Never noticed, just noticed that when I applied the RyanZA's one-click, it would always appear with a error about low internal space so I tried the adb code one and ended up with more space. Thanks for the clarification!
[Vibrant General] DriftorX:
I dont think it was the lag fix itself. since it installed fine after i got the new phone and first thing i did was root it and applied lagfix very first two things i did with the 2nd phone. so i really dont know what it was or what happened. But oh well.

"Third times a charm" :) hehe
[Vibrant General] Mr Mufakka:
Have y'all tried disabling the phone's animations to help with lag?

settings > sounds and display > animation > no animation

Just set mine to that setting. Appears to be running quite a bit better.

I had the lag fix on mine last week but it crashed and I had to wipe the phone clean. I'm not too eager about doing it again.
[Vibrant General] red96turbols:
For some reason, my battery would drain like crazy (stock, non rooted,) after about two weeks of usage. One day, I had pulled out the batter and noticed the 4th quarter of the battery was swelling. I called TMO and they sent me a new battery free of charge. No more battery drains and this one lasted a full day of work while blasting Pandora in my ears to cut out all the idiots yelling at each other. So, before you start blaming apps and lag fixes for battery drain, physically check your battery. These Li-Ion batteries do it, not all of them, just some of them. It also happened on my G1, which TMO would not replace it and I just took the battery out of a friends G1 who was sending it back for warranty work.

Edit: I have now rooted my phone, and with the old swelling battery after 3 hours of up time, and simple usage (mms, two short 5-6 minute phone calls and Terminal Emulator) I'm already at 64% off a full "off-state" charge. Meaning I charge my batteries while the phone is off so it doesn't drain while charging, as they say you should do. With my new battery with an "off-state" charge, 3 hours of uptime and I am sitting at 96% battery life with minor usage.
[Vibrant General] Spiffywerks:
Ive had a very similar issue happen to me, my battery was daining completely in under 2 hours. But I found restarting the phone corrected whatever process got hung up. I thought it was Ryan's fix.. and it's possible it might be linked to it, but I don't think it's necessarily the cause of it. Just a combination of things going wrong.
[Vibrant General] ttabbal:
Please, do NOT use bulging batteries! They do that shortly before they fail internally and li-ions go up in a fireball when that happens.

You should dispose of that battery immediately. Don't have it in your home or near anything flammable. Treat it like it will spontaneously combust at any moment, as it has a good chance of doing exactly that.
[Vibrant General] reaton33:
my story is a bit different

I can personally say that RyanZA one click lag fix is what saved me from ultimately getting a different phone. I installed the lag fix one day and noticed I could go nearly 2 days on one charge with the same amount of usage. I did not install/uninstall anything other than apply the lag fix one weekend and bam, my battery is performing on par with what I'm used to on my old G1.
[Vibrant General] Shrivel:
Ouch, that bad, huh? ;)
[Vibrant General] bauerlucas:
Hahaha your funny
[Vibrant General] Chalup:
:facepalm: you used setcpu ane juice defender then wonder why your phone was acting the way it was? And on top of that you didn't even try to reflash back to stock using Odin?
[Vibrant General] boystuff:
i use OCLF downloaded from Marketplace (One Click Lag Fix) it's based on RyanZAOneClickLagFix 1.0 and I have noticed no battery issues whatsoever.

100% battery when I goto bed, 8 hours later 89% battery sounds about right for 8 hours of standby time.
[Vibrant General] *Haven*:
I have the RyanZAEXT2LagFix BETA 2-3 lag fix and no difference in battery life for me.
[Vibrant General] flameinthefire:
how long does your battery lasts? i don't know how i messed up my battery. its really bad. i think it might have been cheap car charger i got from ebay.
[Vibrant General] fnakfhe:
Why do you root to use wifi?

i have samsung V too, and i dont know what rooting is, but i can use wifi hotspots without rooting.

please explane
[Vibrant General] DriftorX:
I mainly root just to use non USB tether for use as a wifi hotspot for my laptops. I don't have any hotspots around my shop, so I use my vibrant as one. Foremost cause I get faster speeds with it than when I had att DSL service at the shop.
[Vibrant General] fnakfhe:
I am running the Vibrant from Bell mobility here in CANADA.

it has a wifi hot spot feature built in. its \

menu, settings, wireless and network, mobile ap settings.

then it will setup a hot spot from my 3g to my wifi without being rooted,

so again, why did you have to root?

maybe your provider phone does not give that installed on the phone?
[Vibrant General] thegreatcity:
Exactly, the T-Mobile variant has MobileAP removed.
[Vibrant General] DriftorX:
Yes, Unfortunately... Tmobile USA has disable that function on us so thats why it is rooted. :)
[Vibrant General] Relikk356:
@ Chalup

+1, I thought the same thing after i read his comment. Sounds like he burned up his own cpu with SetCpu. Hope he's still not using it as there has been numerous problems reported with it if you take it out of "conservative mode".
[Vibrant General] bauerlucas:
So iv had set cpu on for about a month witch is like a week after getting the phone. Haven't noticed anything should I be worried? I do have it so if it goes over 50°c it goes way down and that has yet to happen.
[Vibrant General] fnakfhe:
Really eh? (yes im Canadian)

tell me how i can remove those sh1tty apps that bell installed on my phone.

i am guessing if you can put back mobile app, then is hould be able to remove some of the things that come with my phone too. like the bell programs (pvr recorder and all other crap)

thanks.
[Vibrant General] remixfa:
i had a huge battery drain for the first few days but after just letting the battery drain out a few times, it fixed itself by the 4th day. i use less than half a battery on a light day.. .3/4ths on a normal day (some might say heavy), and i kill it within 6 hours on a heavy day... as in bored at work playing games and reading for those 6 hrs.. lol.
[Vibrant General] ryan562:
i just flashed the vibrant 7 rom and ryanza's lagfix and my battery life hasn't changed.

in fact, my battery life has greatly improved ever since i started flashing eugene's roms, specifically vibrant 6 and the lag fix.
[Vibrant General] mr2t32:
i just found out running ebuddy drains the batter while the phone is on idle. normally, the battery will go down about 3 percent within 15min while the phone is on idle meaning the screen is locked and off. Today, i had ebuddy off with the phone fully charged before i left for work and drove in traffic home which is about an hour drive and the phone still have ~99% battery life left.
[Vibrant General] Berserk87:
Ive seen quite a few users complain about fast battery drain, then claim that its been fixed after they their IM application.
[Vibrant General] Dougefresh91:
My battery life is the same it always was. Lasts a good 12 hours with normal usage.
[Vibrant General] Bruzkee:
I'm having the same problem. I applied the OCLF from the market yesterday. At first, it seemed like there was no difference in battery life. Charged it last night and my battery is getting eaten alive.

I'm already down to 28% after about 5 hours of really light usage.
[Vibrant General] sunnybwoy1:
Had the same issue as everyone else once installed battery died like 3× faster plus had GPS issues once. uninstalled

Everything went back to normal once that is fixed it will be great to use
[Vibrant General] zoid_99:
I don't think he/she is wrong. I just experienced the same thing. I installed the one click lag fix and my battery life went south. I uninstalled the lag fix and it still had issues. I installed Vibrant9 and all is good. It may be a combination of the lag fix and something else but I'm not sure what that something else is. Looking in "Spare Parts" battery history the "Running" usage is around 50% and if I select it it says "Time spent without sleeping". After flashing Vibrant9 the "Running" has gone down to 6%. No applications were using an unusual amount of battery during this period.
[Vibrant Android Development] ttabbal:
Maybe we can get a group knowledge base going, I'm attempting to build CM6 right now. The idea is to help out with Vibrant porting, but I'm getting stuck and thought you guys might have some hints. If I can get it going, I'll update the wiki or create one somewhere else for Vibrant specific stuff.

So, right now my build system is 64-bit Ubuntu 9.04. I can switch, it looks like it might be better to be on a 32-bit setup, so there's one option.

The basic path to where I am now, following basic directions from here: http://wiki.cyanogenmod.com/index.php?title=Building_from_source

sudo aptitude install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

sudo aptitude install ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib

curl http://android.git.kernel.org/repo >~/bin/repo

chmod a+x ~/bin/repo

export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

(Path modified to match my local path)

repo init -u git://github.com/CyanogenMod/android.git -b froyo
repo sync

source build/envsetup.sh

make -j4 adb

This results in a segfault....

host Executable: adb (out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb)
true
Install: out/host/linux-x86/bin/adb
make: *** [out/host/linux-x86/bin/adb] Segmentation fault (core dumped)

Using "lunch" and selecting a target, then "make clean" gives me the same error building adb. Attempting to build the ROM also gives me a segfault, so at least I'm consistent. It always seems to be on an "Install" step, if that helps.
[Vibrant Android Development] bchalk:
If you get it to compile be sure to post, I'd love to start helping I just lack motivation and free time... And knowledge around Android, but I'm working on that piece ;)
[Vibrant Android Development] turtleman13:
This usually meanings that there is a memory management issue but im no dev hope this helps
[Vibrant Android Development] ttabbal:
Now if we had others posting about what they have done.... hint...

:)

OK, I know there aren't a ton of us messing with things at this level. Hopefully someone else has seen this. I'll try to install a 32-bit Ubuntu 10.whatever tonight and see if that helps. It is possible my issues are being caused by the 32-bit compatibility libraries or similar.
[Vibrant Android Development] d_bot:
I just installed ubuntu32, and am going through the repo sync, as soon as that finishes, I'll pack up and head home and finish there, hopefully it compiles on 32bit. I'll post back as soon as i know.
[Vibrant Android Development] ttabbal:
I've considered contacting them that way, I was hoping the community would be interested in getting a few more devs going. I'm downloading the Ubuntu 32-bit ISO now. If you want to send them a message, cool. I'll fool with things a bit more and if I still can't get anywhere, I'll see if I can get in with thouse guys. If I do get it working, I'll try to document everything that's not covered elsewhere. I just hate to take time away from their work to help out a newb. :)

If you can't build, you can't contribute. The Android build system is somewhat custom and weird, so it can be off-putting to people that would be interested in helping. :) More people hopefully means we can get more done. :)
[Vibrant Android Development] dcchristopher:
ttabal, seg fault during a "make" usually means it tried to access something that wasn't there. Make sure you have all dependencies installed. Someone said seg fault has to do with memory management ... yeah, only when running an app. When building (aka "make"), there are a lot of things being linked and each thing has a ton of dependencies and that continues recursively ... it's why I hated working with Unix back in the day. You change one thing, you have to change everything and its mother.

Still, I have been frustrated at the lack of progress recently that I am toying with the idea of jumping back in the pool and building things myself. I wish one of the more experienced folks here would offer a primer. I know what they're afraid of though ... every noob coming back with a million questions, like, "what's apt-get?" or "what's a make file?".
[Vibrant Android Development] ttabbal:
Yeah, maybe we should start up an invite-only dev forum and only allow public read-only access to a wiki or something so we can share with everyone. I'd love to be more open, but I do see why the big devs don't do their dev conversations here.

I did install the depandancies they listed on the Cyanogen Wiki, but it is possible they need something new that isn't listed. Hopefully someone can help us out. It's also possible my versions of the libraries need updating as I am on an older build of Ubuntu. I have another machine I can install the newer version on, and I'll try that first. May as well make sure I'm doing everything I can. I just can't install on the other machine as it's a production server for my home system. The wife gets mad if I break the TV server. :)
[Vibrant Android Development] bullale:
I know you are attempting to build the source, and I'm sorry I cannot help you with that. I just wanted to put a link up here for people that are getting inspired by you and are considering contributing to the rom development community.

http://xdaforums.com/showthread.php?t=667298

It's a post by cyanogen about how you should go about getting in to rom development.
[Vibrant Android Development] anomalous3:
I managed to get it to build for Dream/Sapphire by first doing

#repo init -u git://android.git.kernel.org/platform/manifest.git

THEN

#repo init -u git://github.com/CyanogenMod/android.git -b froyo
#repo sync
#source build/envsetup.sh

on 64 bit Ubuntu. Did a bit more fidgeting after that to get it working, I'll see if

I can figure it out next time I'm home.
[Vibrant Android Development] ttabbal:
Interesting. I'll try pulling the aosp manifest first. Perhaps that will help. Did you do a repo sync on the aosp or just init?
[Vibrant Android Development] lqaddict:
There was a core dump, so if you have the core.dump file in the same directory where you ran "make" run strings against it, it might tell you what's segfaulted on you.
[Vibrant Android Development] elderberry:
I got past make adb on Ubuntu 10.04 64-bit. Compile has been going for quite some time now. I haven't tried building a kernel yet.
[Vibrant Android Development] CharonIDRONES:
Will be attempting a build on Monday with my secondary box at work running ubuntu. I have a knack for jury rigging things to work and more than willing to contribute, despite lacking the experience. For reference, you could try to converse with then on irc, freenode.net server, in #cyanogenmod or #sgs_dev, a bit more of a direct line to #teamdouche
[Vibrant Android Development] devoinregress:
From what I understand (witch is very little) the G1 drivers have all been reverse engineered for some time and building it from source is incredibly easy at this point. While the Galaxy S is incredibly hard to develop for because all the drivers are wrapped up in all the kernel mods Samsung did, even though they open sourced much of it, its hard to unravel the code.
[Vibrant Android Development] elderberry:
Build completed. Only issues I ran into:

1) repo sync didn't complete at first because I had never talked to android.git.kernel.org. Running "repo init -u git://android.git.kernel.org/platform/manifest.git" as anomalous3 said fixed that.

2) make complained about not being able to find RomManager.apk, so I went into vendor/cyanogen and ran get-rommanager. While I was in there i ran get-google-files and extract-google-files as well, but not sure if that was necessary.

At this point I'm not sure of the kernel requirements for attempting to run this system.img. Until I learn a bit more about the kernel and ramdisk I'm hesitant to do anything with this.
[Vibrant Android Development] ttabbal:
Thanks! I'm running repo sync after the kernel.org init now. I'll see if that gets me building. I don't suggest installing anything you build yet, I want to see if we can get a couple people building before we take that step. Though it looks like we can create some nice update.zips now that flash the kernel and such. Very cool.

Anyone know how to replace parts of a local git with your own repo? I would like to clone my fork of wesgarner's vibrant tree into the main tree so I can do commits and such without messing with anyone else's stuff. git rebase? I'm a little new to git, I've only ever used it for basic stuff that SVN can do. :)

Looks like the sync is going to take a bit for me. Damn. I'll install the latest Ubuntu in a VM while I'm waiting on it. Who do I have to kill to get FIOS in Utah? :D
[Vibrant Android Development] ttabbal:
Hmmm... Still no joy for me. Must have done something wrong I guess. Build still segfaults and I don't get a coredump. Weird.

Thanks for the contact info for teamdouche, I'm trying to avoid bothering them until I at least have a working build. This isn't the sort of level one should bother them about IMO. :)
[Vibrant Android Development] rhcp011235:
Looks like you guys are talking to wes and the others :)

If you guys get it working. I have a build env setup + a build bot. Just let me know
[Vibrant Android Development] funeralthirst:
i'm installing the dev support packages right now. i'm worried, though. how much space are we looking at? my linux partition is only 8gb. so i may have to modify some things so it's all on my raid storage.
[Vibrant Android Development] rhcp011235:
It's HUGE. to get the src + all the stuff.

I used 30G just to get basic 2.2 :)
[Vibrant Android Development] sastian:
Just out of curiosity, is Ubuntu totally necessary or can development happen on OS X?
[Vibrant Android Development] lqaddict:
You are better off working on it on a linux box, if OSX has development libraries needed to support compilers, etc. it should do fine as well.

Sorry, I am not familiar with OSX outside the realm that it is a BSD ripoff :) - not hating LOL
[Vibrant Android Development] feanoth:
I've been able to compile the official Android source on Snow Leopard after applying a patch to allow building with Java 6, but Cyanogenmod source always runs into errors. I just don't know enough to resolve those, but maybe a more knowledgeable person can try it and help out?
[Vibrant Android Development] devoinregress:
OSX should work fine. You may need to work out the dependancies but I think Koush works on a Mac.
[Vibrant Android Development] wergeld:
I re-synced to the CM tree just now.

This is just a default build. Nothing added/removed.

Ran:

Will let you all know how it went.

EDIT: Well, that was fast. Just got the ROM Manager not found issue =)

Will add that and then see what happens...again.
[Vibrant Android Development] justanothercrowd:
http://xdaforums.com/showthread.php?t=767844

This is a vibrant CM6 build i built while i slept last night. Have fun. Its just the system folder FYI.

And yes 32-bit will make your life easier when building Android
[Vibrant Android Development] thechadhall:
The CyanogenMod Wiki Full Update Guide for the Samsung Vibrant

The CyanogenMod wiki has the instructions for the Full CM6 update. I am unable to post the link since I am a new member! :mad: I haven't flashed the ROM since I just got my phone last night.
[Vibrant Android Development] wergeld:
chad658eku: this is for building from source. not just flashing. there is currently no official release of CM for the vibrant.
[Vibrant Android Development] thechadhall:
No worries! I'm still new to everything and trying to be more active. I just noticed the wiki had instructions for both the Vibrant and Captivate. I wish the best for the building!
[Vibrant Android Development] wergeld:
And my build failed. Seems like it died on the OTA package creation:

So...what is the gameplan from here on out?