yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] adampdx:
Vampire Gapps

I just flashed 35 about two hours ago and here are my thoughts: I listened to a one hour podcast and didn't pay attention to the phone at all. The battery level was at 65% when I started. I was driving, and when I stopped about a half hour after the podcast was over the phone had lost no battery. At this point after a phone call and several screen checks my battery is at 61%. What's the question, I asked myself? I discovered the answer when I went to make a phone call. All of my contacts were missing! I realized that my Google account hadn't connected because this particular flash of the ROM wiped Gapps and I hadn't reflashed it. I checked the running services and saw that Google Framework Services wasn't on. So I'm guessing some of the excess battery usage has something to do with a sync or something that requires background modem or processor use. I thought that I had read something about this a couple of pages back, but I didn't realize that the decrease in battery use was going to be dramatic. So, it begs the question...

What apk(s) do I need to pull out of the Gapps package to just get my contacts back and then market, so that I can install email, maps etc. in order to eliminate the culprit app by trial and error?
[Vibrant Android Development] cashyftw:
Contacts apk, and vending apk, oh and another one about sync.
[Vibrant Android Development] jzero88:
I'm trying to figure out why CM7 absolutely kills the battery. What is the difference from the stock roms and CM7. Is it the kernel or what? It gives less then 50% of the stock roms.
[Vibrant Android Development] Phateless:
Got it, thanks for your effort. So you have a vibrant but you're not on tmobile?
[Vibrant Android Development] Nabeel10:
I USED to have mute/unmute problem back in nightly #8, but then I odined and flashed #25, and now I don't have the problem no more, I don't know why it would follow u guys though
[Vibrant Android Development] jimmyhawk:
I can confirm that I had 3 reboots last night on 34 WITH neo9 kernel. Today 35 stock and no probs at all
[Vibrant Android Development] Segnaro:
A T-Mobile prepaid sim may be sufficient for using Wifi Calling. :)

What needs to be changed in the framework? :cool: Currently, I can get Wifi Calling to connect to the T-Mobile network (after adding kineto to the kernel), but the calls instantly end. :(
[Vibrant Android Development] cwalker29:
Man bro that's the same **** I want to know.. wth is it with the suck ass battery life? O'well I guess I'll have to keep it charging while in use. I took it off the the charger at 5:30. I'm at 19% at 10:30:(
[Vibrant Android Development] movieaddict:
I got 2 random reboots on 35 never happened before, my mom wasnt happy i hung up on her..LOL:D

As for the battery maybe u guys have a bad battery because i use my phone alot heavy streaming etc text etc and i can last all day or all night long without charging. I know cm7 battery straining effects some people but not everyone but we need to see why some peoples battery drain so fast because i love cm7 with my battery
[Vibrant Android Development] Locksmith81:
I did lol was a joke. Reason was I was on Neo9 CM7 #35 so I wanted to confirm and used the stock kernel as well. Using process of elimination to determine whether its Neo9 or #35 build.
[Vibrant Android Development] GreenDroidX:
Atinm this remind me of a problem that the CM7 of nexus one had. Basically the sound would be pretty bad quality until u mute then unmute the mic. Cyanogen seem to have fixed it after multiple kernel alterations for like weeks. Maybe he can tell u not really sure
[Vibrant Android Development] playonline53tms:
Battery is sucky but you can fix that easy

Vibrant owns cm7
[Vibrant Android Development] treyvaporizer:
Glitch kernel seems to fix a lot of battery issues for me, but what ideas do you have, good sir?
[Vibrant Android Development] playonline53tms:
glitch is my fix

Vibrant owns cm7
[Vibrant Android Development] tripleintegral:
I had the mute/unmute issue when I was on the nighties. Then I moved to another rom for a few days. Last night I ODIN'd to JFD and flashed nightly 35 and had someone call me five times but I can't reproduce the problem. Anyone here who stopped having the issue after going to stock and flashing a nightly?

Edit: I also flashed KB5 after flashing the nightly.
[Vibrant Android Development] cwalker29:
And where is this glitch kernel?
[Vibrant Android Development] shreddintyres:
it is a unsupported kernel, search the vibrant dev section
[Vibrant Android Development] playonline53tms:
Seems preaty good bo problems oc at 1.6 (someti,es 1.5) works great

Vibrant owns cm7
[Vibrant Android Development] krazie1:
Nightly #36 is UP and Posted!
[Vibrant Android Development] treyvaporizer:
Hah awesome

Sent from SGH-T959 (CM7)
[Vibrant Android Development] rschenck:
CM7 Vibrant Users!

In order to help us all keep track of CM7 Nightlies, a community wiki was started for the i9000 in order to share info about CM7 updates which are so frequent now that new ones seem to be appearing..well...ummm....nightly.

At the request of Atinm, the Nightly Wiki is now expanding to include CM7 Vibrant users as well. You lucky dogs you.

The Nightly Wiki is there for all your Nightly Flashing questions, such as "What bugs does this one have?", or "What do I do if this Nightly bootloops?" or "Will flashing this Nightly make Peggy Ann realize that I am the only man for her and that Johnny is a no-good rat?"

The best thing about this Wiki is that all you have to do to add your own input to each Nightly report is ask to be a User. Therefore it is a one stop information source maintained by the entire community. What FUN! Thanks to everyone who have been pitching in thus far for the i9000, especially my co-admin zpon.

A new page has been prepared just waiting for Vibrant users to rush in and begin filling in essential data on the most recent Vibrant nightlies. All you need to do is either send me a PM asking for User access in order to edit the pages, or send a request directly from the Wiki.

Now, don't push and shove, there is plenty of room for all of you. Just aim your browsers at http://sgscm7nightlies.pbworks.com to get started.
[Vibrant Android Development] atinm:
An XDA user sent me his slightly broken vibrant so I could test - so yes, I have a vibrant but am not on tmobile. The AT&T sim works in it so I can test basic functionality.
[Vibrant Android Development] atinm:
Vibrant users - especially the helpful kind, please get on this. It really helps to have one place where "general" nightly issues show up so us devs have a place to go to quickly see the status. We don't really have time to wade thru the forums, and so if someone takes this on, it will be awesome. Galaxy S has a few ppl who are on this, and it makes the Galaxy S a pleasure for us.
[Vibrant Android Development] atinm:
We don't have all the code that shuts down devices and puts them into deep sleep. It is mostly the radio that is the problem, if you're in a bad signal area, or have apps that want to go out to the net to sync etc, you'll get serious battery drain. This is a combination of kernel and framework issues. Kernel source is open and so we have fixed most of what we can - framework is not, and the radio interface is in the framework.
[Vibrant Android Development] atinm:
What is the CONFIG you enabled? Maybe I can try it sometime too - I have nothing TMobile, so I don't know whether the SIM card will work for wifi calling. One of the HTC phones does have internet calling working with CM, so a similar config change might be needed in framework to make sure it works for vibrant.
[Vibrant Android Development] cwalker29:
Yeah I found it. In my sleep! Lol flash the first one I saw and **** up the buttons on my phone. Lmao half sleep flashing will always mess something up. It's cool, I flash the right one this morning:)
[Vibrant Android Development] jrod33084:
A few of you had said that when you odined back to stock and then flashed a recent nightly you did not have the M/U problem so when I get home tonight I will test that out because I still have the issue but haven't odined to stock in a while.
[Vibrant Android Development] zaelia:
My vibrant wont mount the SD card in recovery I get can't mount error every time. Any help would be great thank you
[Vibrant Android Development] Binary100100:
I have one for ya!

Any chance to get the TV-Out working for CM7?

It might be too much to ask but I figured that it wouldn't hurt to give it a shot.
[Vibrant Android Development] compuguy1088:
Hate to post this question again, but has nandroid been fixed? Backup and restore has been broken since nightly 25.
[Vibrant Android Development] atinm:
Should be fixed in last night's build.
[Vibrant Android Development] Adapt0r:
External_sd

I've recently flashed the latest nightly build from freshly rebuild stock JFD.

What I've found that content of external SD card could not be seen. However, both music players that I have can show and play audio files located on external flash card.

It seems that this can be fixed relatively easy.

Cheers!
[Vibrant Android Development] wergeld:
36 appears to have video glitch with the boot animation. Lines and flickering through it.

So far everything else is fine.
[Vibrant Android Development] benwhite:
Yeah, wifi to wifi, although there is a check to ensure your connection is over wifi.

Also, I noticed that the account I'm using for my SGS does not show up as supporting video to the person I'm calling. I wonder if this has anything to do with it?
[Vibrant Android Development] Kaik541:
can you confirm that you have libtalk_jni.so in /system/lib and it's permissions are -rw-r--r-?
[Vibrant Android Development] benwhite:
Yeah, it's there with -rw-r--r-

I had updated to CM7 20110509 this morning and install the gapps-gb-20110503-signed.zip this afternoon when you pointed out it was available.

I have not installed any other kernel, although I typically run the kang kernel.

I can place video calls, and see everything perfectly on my SGS, it's just the recipient does not see my video.
[Vibrant Android Development] Kaik541:
my last guess. have you ensured your video chat option is enabled? press your name at the top and set "allow video and voice chats" to yes and set your status as available? if all of the above is true and still not working, I'm not sure to be honest as it does work on mine. sorry :(
[Vibrant Android Development] cal4877:
yup we need another update now my camera isnt working on none of the updates.
[Vibrant Android Development] Kaik541:
camera works just fine for myself and a number of other users. have you tried clearing the camera app's data? (settings, applications, all, camera, clear data) or performing a cache wipe. worst case scenario a full factory reset.

unless you have done ALL of the above, we are going to chalk it up to user error (as well as the fact that you have provided neither a logcat nor a dmesg for your issue, it's hard to take it seriously)
[Vibrant Android Development] rsfaze:
phone charges to 95 and says its charged. I rebooted to recovery wiped battery stats and no change. It did saying charging after I wiped the stats but then it went to charged and still the highest I got to was 95, and this is being read from the CM status bar tweaks with % enabled.

awesome fast rom with zero issues aside from the battery % reading off
[Vibrant Android Development] atinm:
Thanks for not reading the FAQ! We just wrote it for the users we actually want to support.
[Vibrant Android Development] atinm:
I'll get right on it.
[Vibrant Android Development] numberoneoppa:
Loled.

Seriously loving the current nightly. :-)

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] lilg754367:
mute/unmute

would someone be kind enough and guide me through to do that code so you do not have to always mute/unmute ill donate
[Vibrant Android Development] numberoneoppa:
Pretty sure that was a joke. There is currently no fix as far as I am aware.

Sent from my Vibrant using the XDA for Android app.
[Vibrant Android Development] :
My cam works good o_O i wonda whats wrong
[Vibrant Android Development] blahbommer:
Lol he was joking but a while back he did say he needed a tester for the issue
[Vibrant Android Development] I7oobie:
Really?

The one dated today isn't good enough? Give him a break.

Atinm, Good job on the latest nightly. Your work is appreciated.
[Vibrant Android Development] Soldi3rxx:
I've ready the questions and answer section about the 100% battery charge but can some elaborate please. If other custom roms can get to 100 why can't CM7?

Also, whats up with not being able to charge the phone while its off?

What purpose do they "cm7-vibrant-radio-xxx.zip" file serve. Like what exactly do they do

I'm only asking questions to inform myself and possibly inform other people, sry if i seem like a noob but I'm coming from Bionix and just trying out new things.
[Vibrant Android Development] Mannymal:
I'm considering installing this for a daily test, but before that I want to verify on some issues that are not clear on the OT or the support thread linked there.

- Whats with the 'Mute/Unmute' thing? I can't find details on this.

- Do we need to use a widget in order to use headphones?

- Can someone explain these:

"Polling problem on RIL (works after lock and unlock)

2G/3G toggle (works if no data connection is active)"

What are these issues and how do they affect daily use?

Thanks a bunch!
[Vibrant Android Development] gehzumteufel:
1. The person on the other end can't hear you or they hear you very badly. Muting and then unmuting seems to clear this up.

2. No, you do not need that at all.

3. RIL polling has to do with just general connectivity. It isn't much of a problem right now. Works quite well as fo late.

4. 2g/3g toggle should NOT be used unless data connection is off.
[Vibrant Android Development] rsfaze:
sorry man, I skimmed through the pages I will go back and read the faq ;p
[Vibrant Android Development] Mannymal:
Another question. I've been looking but can't find a clear answer on my own.

Does the included kernel have Vooodoo Sound? I don't want to install a kernel with UV and overclocking. But I really want Voodoo sound. If the stock one doesnt have it, is there a barebones kernel that has all the neat features but no OV and OC?
[Vibrant Android Development] cojonesx:
Not being ungrateful here but why not use the cm wiki?
[Vibrant Android Development] nedlog:
Installed #36 via the ODIN route to see if the M/U problem is fixed. Waiting for a call; everything else is working fine so far....Update M/U still needed to clean up voice...no need to ODIN to stock first it didn't work for me.
[Vibrant Android Development] beren28:
Not for me.
[Vibrant Android Development] jzero88:
That makes a lot of sense. I see you are doing all you can with what you have at the moment :) I absolutely love CM and love the work you guys put into reviving our devices. System Panel just wasn't showing where the drain was going so I wasn't sure what exactly was going on. Great work atinm
[Vibrant Android Development] Relikk356:
+1, I have no problems with that.
[Vibrant Android Development] njuncos:
I appreciate very much atinm's refocused efforts on these bugs plauging the vibrant. You rock! Are there absolutely no vibrant devs on T-Mobile that van help resolve these bugs and bring the vibrant to a stable status? Cause that would rock
[Vibrant Android Development] Segnaro:
Added module:

https://github.com/cyanogen/cm-kernel-exp/commit/9158026851f843c5af0239fe16fbd99f0ecc37b8#diff-0_

CONFIG_KINETO_GAN=y

I think what they changed in the HTC phones was libmedia.so, since

AudioRecord.cpp and AudioTrack.cpp have this flag

#ifdef USE_KINETO_COMPATIBILITY
// Really dirty hack to give a Froyo-compatible constructor

but I see HD2 uses the Gingerbread wifi calling app that doesn't need libmedia modified.
[Vibrant Android Development] playonline53tms:
What I did was odin back to stock and then follow the directions at http://xdaforums.com/showthread.php?t=980241 fix the problem after all is done

Need help with cm7? Pm me I can try to help
[Vibrant Android Development] atinm:
Did you actually look at what this wiki does? This is talking about each nightly individually. I requested him to add Vibrant and Captivate to the list so I have some place where I can look for what issues are plaguing users, as we don't really have time to wade thru all the posts across all the different threads.
[Vibrant Android Development] Phateless:
Ok good, lol.
[Vibrant Android Development] atinm:
And that's why I pay very little attention to Vibrant compared to say Captivate - it isn't my primary network and so things like wifi calling etc just fall by the wayside. Coolya also doesn't have tmobile, and so he doesn't really do anything tmobile specific either. The tmobile android developers seem to be on non-samsung phones.
[Vibrant Android Development] jimmyhawk:
File manager,sd,emmc=external sd card
[Vibrant Android Development] Phateless:
Well we've always had some great htc phones on t-mobile so that makes sense. Thanks again for your efforts.
[Vibrant Android Development] playonline53tms:
About this gps not working other gb roms have gps partly working do you think we could sortof copy the other roms to make our roms gps work or is it imposible?

Need help with cm7? Pm me I can try to help
[Vibrant Android Development] atinm:
Our code is all available on github, so have at it. The issue is that all the other GB roms are using the TW framework - so they don't have to do anything much to get GPS "working" as well as stock, the rest is just tuning. The issue is that the framework code is not open, and the GPS interacts with the modem as well (which is a wtf, if there was ever one . . .) which is also closed.
[Vibrant Android Development] atinm:
It isn't that the Vibrant was a bad device compared to the other HTC offerings at the time, in fact, I'd put it up with any of them. It was more that the code was done quite differently from other phones and so when the tmobile CM developers tried to get CM working on the Vibrant, it was way out of their comfort-zone and so they abandoned it and went back to their HTC phones. It required us to take it on, because we had no history and so it was all new to us and since i9000 and Captivate are quite similar to Vibrant, we ended up doing Vibrant as well. But that isn't the same as a motivated Vibrant developer to take it on (we aren't motivated enough on Vibrant to go hack in the TW framework to figure out what it does so we can duplicate the things we need for GPS, wifi calling etc). We've done about as much as we can really do with it - now we're waiting on some source drops (GB source drop for Vibrant could help things along a little bit), and then we'll see how far we get.
[Vibrant Android Development] Relikk356:
Odin back to stock just for fun. Then not expecting much installed #36. I had my buddy call me and It seemed to have cured the mute unmute problem. Only tested with that one phone call so far but it was good.

ATINM, do you think the updates you gave me might not have been updating the kernal? Do the updates change the kernal every time? Since I already had the GB kernal from previous CM7 do you think it just skipped replacing the codec's you changed?

Well, it seems to work now, so that's great. Of course I probably shouldn't get this excited over one received phone call.
[Vibrant Android Development] Relikk356:
ATINM, I'm not even sure if you put the "Dirty Hack" fixes in #36, never actualy checked. LOL.
[Vibrant Android Development] compuguy1088:
True, though there are some of us that use the vibrant at&t...
[Vibrant Android Development] compuguy1088:
Honestly, if GPS can be made functional using the galaxy s 4g code ( which isn't that great to begin with on any of the first gen galaxy s), that would be a grand accomplishment.
[Vibrant Android Development] nedlog:
I'm sure most of us are thankful for the time you spend on the Vibrant; and frankly I'm surprised more developers on T-Mobile don't use them...I'm not a SW developer by trade but some dev on Vibrant/TMobile please come forward....

P.S. It's only until TMobile becomes AT&T...then we'll all have the same bugs!:eek:
[Vibrant Android Development] atinm:
I actually did - and it should have been flashing the kernel for you too. All the hacks I put in for mute/unmute are in the latest nightly, so you have them.
[Vibrant Android Development] atinm:
As I have a working Captivate, an SGS2 and a cracked but mostly functional Vibrant on AT&T, I tend to use the Vibrant purely to keep the Vibrant up to the same level as Captivate and I9000 - but tmobile specific stuff falls behind because I really would like a tmobile developer to do them because the activation energy required to work on something that I can't actually test is way too high.
[Vibrant Android Development] Phateless:
Yeah so I've heard. Rfs file system and nonstandard partitions as far as kernel and bootloader right?
[Vibrant Android Development] amwilliams9:
While I really do appreciate all the hard work all of you have put into making CM7 a reality for the Vibrant...I must admit it is disheartening to hear that there is not a dedicated developer who is familiar/uses Tmobile. I believe that is why it is such hit and miss with updates/features. Strange though that the Vibrant has its own forum with all the bells and whistles (ie subforums) Alas such is life on the forth largest cellphone company. Keep up the great work however. I for one really do appreciate all that you guys have don thus far!!
[Vibrant Android Development] liridonb:
Hi, Does the mute/unmute was resolved? No more issues with calling / no voice?

I have back to stock only because of this. If it's resolved I'll immediately back to 2.3.4 Cyanogen.

Please if someone can tell me...
[Vibrant Android Development] parmijo11:
I'm not having the issue, that's not to say it may not still be there.
[Vibrant Android Development] numberoneoppa:
We should try to convince one of the other Vibrant devs to jump ship to CM7. There are a handful that should be capable... okay, maybe only a couple. :P
[Vibrant Android Development] liridonb:
I left the CM7 on build 25, did you have any time at any of built??? Call issues, other part not hearing you anything ???
[Vibrant Android Development] playonline53tms:
I would but idk how to do it haha no obuntu... Not yet

Need help with cm7? Pm me I can try to help
[Vibrant Android Development] cpittman:
though i've moved on to the sensation i'll fire up odin and contribute HELPFUL information to the wiki for as long as needed. i admire atinm for his patience when dealing with us so anything i can contribute to the cause i will. if only my c, java and reverse engineering skills were up to par i could contribute more. until then this is all i got lol.
[Vibrant Android Development] Trev420:
Okay guys. Flashed 36 coming from 24. It bootlooped on me, reinstalled and cleared cache and it booted up. But with auto rotation enabled it gets stuck on horizontal and Doesn't go back to landscape until I disable auto rotation. I flashed to nightly 25, no problems. Then flashed back to 36 with the same auto rotation problem. Redownloading 36 to see if I got a bad file.
[Vibrant Android Development] Phateless:
recalibrate your rotation sensor in settings
[Vibrant Android Development] ipeench:
I been kinda Mia to the scene for a bit.

Im reading through this thread but how's the progress been on this if I missed any key things?
[Vibrant Android Development] Trev420:
Where do I recalibrate the sensor setting? I can't seem to find it.
[Vibrant Android Development] zhuzf:
But why i9000 and captivate can get GPS working on CM7？ T-mobile did something specific on Vibrant？
[Vibrant Android Development] atinm:
Different chip.
[Vibrant Android Development] Poser:
That's just frustrating. I know that i9000 uses a broadcomm chip... what does t959 use... and does t959v use same chip?

On side note... I must be having a blonde moment: digging through camera menus, I can not find how to save pics to external (emmc). Is it possible?
[Vibrant Android Development] notverycreative:
I don't think so, no.