yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Poser:
Couple of quick comments and then a question:

1. Enough of the MXXX bashing, whether justified or not... its unecessary clutter added to this thread (atinm already addressed it succinctly). We discuss CM7 Nightlies here, and we all know there is plenty to discuss on that topic alone.

2. Judging battery performance really takes a re-cal and several discharge cycles... so when you comment on batt performance, it would be very helpful if you note whether you re-cal'd and have undergone several cycles. For brand new nightlies (i.e. #43) it is obvious that several discharge cycles have most probably not been performed... unless you are getting 4-5 hours per charge... and then we know there are batt problems.

[/*****ing]

Now, I know we all like to tweak our settings and CMparts settings like Ozark meth pushers... have people found that restoring Ti backups of these settings have impacted performance and/or resulted in anomalous behavior. I ask because it is ***** to redo these settings when you start flashing regularly.

Happy fourth everyone.
[Vibrant Android Development] FATEOWNZYOU:
Shoot, I have always seen battery statistics that people post saying they got 30 hrs batterylife and so on.. lmao, I am on my phone NON-stop, and I don't think IV seen over 7 hours within my whole battery. Must be doing something wrong
[Vibrant Android Development] SBboundbRONCOS:
ya i get nowhere near what some people get, they must not do anything on it other than a few calls and some push notifications from email.
[Vibrant Android Development] shreddintyres:
I can get 20 he's on my phone if I don't do anything if I use my phone as heavily use it I get about 7-10 hrs
[Vibrant Android Development] Hung0702:
I get 14-16 hrs with very light usage and push notifications, very light widget updates. 9-10 hours when I actually used my phone like it's meant to be used. >1 hour calling, near constant texting/email, and frequent reddit browsing + general internet. Probably ~ youtube/netflix. I don't play any games, but 3D games eat up my batt like nothing else.

It used to get to me that people were getting double my batt life, but seeing hundreds of posts like ours (not just for 2.3+, 2.1 and 2.2 as well) led me to realize those people are too frugal with their battery to enjoy their phones as we do. I want my homescreen weather widget, damn it, and I'll let it autorefresh every 3 hours, too! I only turn off background updates if I'm about to start a night out with <15% batt.
[Vibrant Android Development] }{Alienz}{:
So what's the consensus of #39 vs latest for battery life? I hear good and terrible posts.
[Vibrant Android Development] xriderx66:
same here. I'm not leaving #39 with the 20+ hours i've been getting unless the latest one can make me grilled cheese.
[Vibrant Android Development] nedlog:
I've been using my phone for about seven hours and have 72%, running 43 wiped battery bin two flashea ago, moderate use.
[Vibrant Android Development] atinm:
Battery issues - unless we make a noise about it in the changelog, assume that battery life hasn't changed from one nightly to another. Don't let that be a reason for you to stay on one nightly vs another. Other things like "no changes worth the time", sure. :)
[Vibrant Android Development] Relikk356:
After several days worth of battery wipes I'm at 70% in about 9 hours. I've taken several phone calls, YouTubed it, angry birds and text it up. Nothing to stressful on the battery, and maybe 20 minutes tops on each of those. I'm on number 40. According to system panel "calendar storage" was always running in the foreground. Not sure if you need it but I sure dont't. I froze it with titanium backup. It seemed to have improved battery life some for me.
[Vibrant Android Development] VeryCoolAlan:
Once again, well said.
[Vibrant Android Development] xriderx66:
@#2

We're asking for estimations, not accurate readings.

Also, since these nightlies are UPDATES, how does it exactly erase batterystat.bin like flashing a rom that wipes everything????
[Vibrant Android Development] jzero88:
So I have unzipped CM7 rom, and can't seem to find the keyboard.apk inside the app folder. Is it called something else? Or is it built into the system? Thanks.
[Vibrant Android Development] cwalker29:
Don't really see the point of complaining about battery life until the source code is release. But I do LOVE great battery life with my phone. My opinion, cm7 is the best rom out for the vibrant. But the battery life isn't so great(#39 nice). So in other words, if you want a fresh, up to date phone. Then cm7 is the way to go. If u worry about battey life. Try 2.2.1 roms out first! Until then keep the chargers close by:)
[Vibrant Android Development] cwalker29:
O'yeah. Thanks for the great work on cm7! If it's wasn't for you guys, my vibrant would have been sold a long time ago.
[Vibrant Android Development] upsalarunvk:
CRO VK GalaXy S
[Vibrant Android Development] VeryCoolAlan:
Since this is an AOSP ROM.

Would TV out ever be supported?
[Vibrant Android Development] Phateless:
System/app/latinime.apk
[Vibrant Android Development] jwleonhart:
I do have to ask something that may seem repetative.... why cant u take the gps drivers or whatever it is that isnt working off of a gingerbread build tyat has gps working at least somewhat...? Just curious
[Vibrant Android Development] konigswagger:
read the first post in this thread and see how cm7 differs from other roms........
[Vibrant Android Development] adyscorpius:
The drivers are dependent on TouchWiz frameworks and other elements built into Samsung ROMs, which are very different from AOSP ROMs like CM7... Hence, the problem...
[Vibrant Android Development] krazie1:
Nightly #44 is UP!
[Vibrant Android Development] Kaik541:
unfortunately it cannot. if you use another kernel, you do not *have* to utilize the oc/uv if you don't want it though.

voodoo lagfix is not needed on CM7 as it doesn't use samsung's bml partition layout or the RFS filesystem

please do not spread information if you do not have the knowledge. CM7 contains both yaffs2 and ext4 (don't believe me? look at the output of the "mount" command on your phone). these filesystems combined with the MTD partition layout make the phone much more responsive than stock samsung.
[Vibrant Android Development] tsnow247:
Dude I was just trying to get them off the voodoo drug.

Thanks for clearing it up though. I knew it was some combination just wasn't 100% sure what was what

Sent from cm7
[Vibrant Android Development] diorDNA:
/dev/block/mtdblock2 on /system type yaffs2 (rw,relatime)

/dev/block/mtdblock3 on /cache type yaffs2 (rw,relatime)

/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev
[Vibrant Android Development] anilo:
OK - I think I've tried a lot to make GTalk video work but still clueless why it is not sending my video. Here is what I did so far:

A fresh install of CM7 (yes, ODIN'd back to stock, installed a Froyo ROM (Trigger), then, flashed CM7. On top of it, I installed GApps using gapps-gb-20110503-signed.zip.

I was able to see other party's video, see myself on my phone (the little picture) but the other party could not see me. So I flashed update-cm-7-05092011-NIGHTLY-Vibrant-signed.zip and once again GApps. Still, no luck.

In a last attempt, cleared dalvik cache, wiped partitions, full factory reset. Flashed the nightly AND Gapps but still nothing.

In between, I always cleared the camera data. In the computer that I am trying, it says "Voice/video chat is not yet available for anil's system." and you cannot start a video call from computer --> phone.

What am I missing in this picture?
[Vibrant Android Development] Saiboogu:
Have you ever actually setup voice/video chat for your Google account from a PC? While signed into gmail, check the settings page to make sure everything is enabled for your account.
[Vibrant Android Development] mulcahyd:
Just wanted to know if the most recent nightly is stable enough as a daily usage, also is data and signal corrected?
[Vibrant Android Development] anilo:
Yep! Been using the audio/video chat from my PC for a while now. I should also add that I see the camera icon next to my name in the GTalk application on my phone but the other party (PC user) does not see it there.

I think you and I were thinking the same thing: this is a setup issue. I was right in the Gmail settings trying to figure out if I missed something out just before I read your post!
[Vibrant Android Development] Kaik541:
quite odd as it seems to work fine for some other vibrant users. unfortunately, we can't debug this right now as the people looking into it don't have vibrants (atinm will hopefully have one soon). a number of questions though I'd like anyone who's having issues with gtalk to answer though:

1) Can you *confirm* that libtalk_jni.so is in /system/lib with -rw--r--r- permissions?

2) Can you *confirm* you have enabled voice and video chat in gtalk settings?

3) Do you have the FFC mod installed on your device?

3a) Do you have the first generation one (aka i9000) or second generation one (aka galaxys 4g)?

3b) Have you tried switching camera inputs?

4) Whether you do or do not have the FFC and are having issues, what is the result of pushing this file: http://dl.dropbox.com/u/10640272/libcamera.so to /system/lib (and overwriting the current one) with permission -rw--r--r- (NOTE: this will give you access to only the BACK camera)

please let us know your results
[Vibrant Android Development] anilo:
*EDIT* (I was wrong about the permissions in my first post. I used the terminal emulator and everything has -rw--r--r-)

1) It's in /system/lib and the permissions are right on.

2) Yes, I confirm those are enabled in gtalk.

3) Yes, I have FFC mod installed and I switch back and forth seamlessly.

3a) I have the first generation

3b) Already answered this in 3.

4) Haven't tried this yet!

Thanks for the quick response!
[Vibrant Android Development] Gd_JOSEC:
Just to make sure im running bionix thats a 2.2 rom. When flashing to this rom I	do not need to odin right? Just copy and run the files. Also this is still a beta rom correct?
[Vibrant Android Development] gehzumteufel:
Yes, it is still beta. You are correct that you no longer need ODIN. Copy both files to root of SD card.
[Vibrant Android Development] Mannymal:
I installed Gapps but accidentally cancelled the prompt to install all its applications. Is there a way to get that again?
[Vibrant Android Development] fishman0919:
For anyone who wants the default AOSP GB launcher from the Nexus S, for CM7 on the Vibrant.

I pulled the Launcher2.apk from the zip and used Root Explorer to drop it in /system/app... you could adb push.

After installing I had to reboot to see the Launcher.

LINK to Launcher2.apk

Original Thread
[Vibrant Android Development] hitman818:
There is a gb launcher from the market, its basically the same.
[Vibrant Android Development] fishman0919:
Yeah, by Eugene373 for $2.00... that's fine If you want to spend 2 bucks... or you can install this for a little bit of work and it's free.
[Vibrant Android Development] diorDNA:
I don't think it works, I rebooted 3 times and nothing
[Vibrant Android Development] fishman0919:
You can't flash the zip...

And you got to fix permissions to look like...
[Vibrant Android Development] diorDNA:
Yeah I already got it to work. Thanx though
[Vibrant Android Development] Mannymal:
Been playing around with it. Very slick, very smooth so far. Much better than when I tried it some builds ago.

FWIW, Quadrant is up to 1650 from Bionix's 1490. But Nenamark is down to 34fps from 50.7fps. I dont play very 3D intensive games, but I hope 3D performance improves before I do find one worth playing.

Will test battery life tomorrow during the day.
[Vibrant Android Development] Kaik541:
put your phone to sleep and then wake it up before running the benchmark.
[Vibrant Android Development] krazie1:
I would like to say that i moved on back to CM7 from being on Asgard v3 and i am LOVING it. So the Mute/Unmute problem that was so horrendous to me in the past, is not here on Nightly #43. Some of you having the problem i don't know what to tell you, all i did was flash back the froyo bootloaders then i odined back to Stock 2.1 JFD. After that i Wiped EVERYTHING then flashed. After the phone rebooted and booted into CM7's main screen i let it sit for 10 minutes then rebooted to flash the Gapps and a different modem. And i've had like 15 calls all day and they all sound fine, everyone can hear me perfect and i can hear them perfect. I'm thinking if your having the Mute/Unmute problem i'd suggest to try odining back to stock 2.1 JFD, then flashing CM7. Do it the way i said; flash CM7 reboot and let it sit for 10 minutes before rebooting into recovery to flash gapps. Well, yeah i just thought i post my thoughts and say that i'm really liking this rom everything is running perfect. Oh BTW battery isn't to shabby, 11HRs and 54Ms the phone is at 64%.

PS I say that i was using the phone and all but it's actually my G/F using it and i tried everything for her to make sure there aint no issues because she can get annoyed if something don't work; she knows GPS dont work though.
[Vibrant Android Development] adyscorpius:
You sure you flashed CM7? Lol... :P
[Vibrant Android Development] krazie1:
Yeah. I thought the same thing to be honest. I thought i was going to have all kinds of problems thats why i kept hesitating coming back to CM7 and when i flashed it i was amazed that problems that i had in the past weren't present here. Good to be back to CM7. ;)
[Vibrant Android Development] shaiu22:
atnim,

First I want to say that CM7 is wonderful.

Why not implement in the code an action of mute/unmute everytime a call is received? Isn't it only a few lines of code?
[Vibrant Android Development] movieaddict:
If it was that easy dont u think a big developing team like cm would have figured that out by now.

Plus #44 is smooth for me, ty again cm!
[Vibrant Android Development] Hung0702:
This had been mentioned several times, and atinm has done precisely that in I think 38-40 and even uploaded an flashable .zip that that does only that a few pages back. It may be difficult for some to use the search function. But please try your best to keep this thread at a minimal amount of redundancy
[Vibrant Android Development] atinm:
I actually did in one of the most recent nightlies - and it is still there. Didn't seem to help - so must have missed something. I am taking a break for this for a few days (hours, minutes..) while I work on SGS2. Will come back to this when I have another brainwave, or when Vibrant drops source, or there is a regression that needs attention!
[Vibrant Android Development] moonfire711:
I haved always flashed in the exact method you described and have still had the issue when someone calls me. You must have a super vibrant. Can we switch? Purely for test reasons, of course.

Thanks for the work Atnim. Always appreciated. A break...? :( Just kidding.
[Vibrant Android Development] nedlog:
Running #44 and all is well; no real issues to report other then the ones well known. Thanks again guys for all the hard work...enjoy your break. Who knows maybe the code will drop soon. :D
[Vibrant Android Development] iynfynity:
Man I miss CM7, the last time I flash this was #4.
[Vibrant Android Development] notverycreative:
According to the changelog, the next build will have screenshots and touch to focus :D
[Vibrant Android Development] cashyftw:
Omg yes!!

Sent from my T959
[Vibrant Android Development] atinm:
Touch to focus is hardware dependent - so not all phones (including ours).
[Vibrant Android Development] Locksmith81:
Dang son! You're 40 builds behind!
[Vibrant Android Development] Binary100100:
According to the changelog we haven't had anything new since Nightly #40 which was only fix agpsd path, removed libsecgps.so
[Vibrant Android Development] beren28:
Really? Because i played with the new night mode mentioned in 43 and enjoyed it.
[Vibrant Android Development] Binary100100:
Just going off of what the change log says.
[Vibrant Android Development] }{Alienz}{:
@atinm: I believe the "fix agpsd path, removed libsecgps.so" directly relate to battery life. On Nightly #39 where you disabled the agpsd, I have AMAZING battery life. On nightly #40, where those changes listed above are implemented, battery life returns to what it used to be prior to nightly #39-----Mediocre.

Ofc that is just my experience but if battery life is ****ty because of the agps or something like it, could you look into disabling it? Something in nightly #39 makes the battery life be amazing.
[Vibrant Android Development] beren28:
How so?

I don't think you understand how the changelog works.
[Vibrant Android Development] iynfynity:
what touch to focus? The one in the camera?
[Vibrant Android Development] notverycreative:
Awwww :(
[Vibrant Android Development] masr1979:
Wait, but doesn't the stock touchwiz camera app have touch to focus?... have I drank too much today?
[Vibrant Android Development] geoffcorey:
The touchwiz is not aosp, and we don't have all the info needed to get aosp stuff working 100% (I.e. Samsung rom source).
[Vibrant Android Development] adyscorpius:
What he really means to say is that if the TouchWiz has support for touch to focus, then the hardware surely must be supporting it. And since Cyanogenmod is implementing the feature to the ROM, we might as well get it, because it shall function for us too !!!
[Vibrant Android Development] treyvaporizer:
Damnnn..

Sent from SGH-T959 (CM7)
[Vibrant Android Development] xriderx66:
+ 22222

I'm stuck on 39 out has too good battery life to leave
[Vibrant Android Development] Phateless:
Just like gps? Drivers might be tied to touchwiz framework too.
[Vibrant Android Development] vud911:
So quick question. Is light sensor working for anyone else? Every time I try to turn on the light to make it brighter, it wouldn't work. Stays the same regardless of the amount of light present. But I did found the changelog above. :confused:
[Vibrant Android Development] Locksmith81:
Been averaging over 14+ hours on heavy use +24 hours on moderate to light. I have lotabof emails tweets xda Netflix and Facebook all day long!!
[Vibrant Android Development] geoffcorey:
Just because it works with touchwiz, doesn't mean anything back in aosp land, as evidenced by our vibrant, with the mute/unmute and GPS.
[Vibrant Android Development] numberoneoppa:
The stock samsung firmware had touch to focus, so why wouldn't the CM? Sorry if I'm misunderstanding something here.

edit: My question seems to have been for the most part already covered in the last page. I'll go ahead and assume a source drop should alleviate this. <3

edit2: Atin, a question for you. Should I be buying a Galaxy S2? Since you're playing with it a whole lot lately, I figure you'd have a pretty strong opinion on the phone. What do you think? I'm an AOSP nut, but I like the functionality present on the stock SGS2 (I don't mean TW). Will CM be able to do 1080p recording and the like?
[Vibrant Android Development] adyscorpius:
Ohh yea, I'd want to ask that too... What phone from the latest releases should I buy for getting the best of CM love? SGS 2 or some other dual core?
[Vibrant Android Development] numberoneoppa:
Well we know for certain that they've already been making good progress for a good while now on the SGS2 and having atin personally working on the project for me is a very big advantage as I've grown to trust his work ethic and skill.
[Vibrant Android Development] krazie1:
Nightly #45 is UP!
[Vibrant Android Development] krazie1:
So yeah i know i said that the mute/unmute problem wasn't present, well im sorry but it IS. I was on a call earlier and they couldn't hear me (sounded far away) so i had to press the mute/unmute so they could. If it helps any its usually on Landline calls and Sprint calls. When i get calls from other T-mobile people or Cricket they sound good.
[Vibrant Android Development] adyscorpius:
I would surely buy the phone cuz Atin is working on it, but at the same time, don't want the Samsung's locked RIL n GPS stuff n all to plague me later on my experience with CM7...
[Vibrant Android Development] atinm:
Thanks :-)

And no, we are not facing any RIL or GPS stuff on SGS2 - this time we've got more exotic requirements and want to get codecs working well too which is our biggest challenge at the moment. Everything else seems doable as of now - I used GPS yesterday and use the phone functionality and sms all the time. Battery life is as good as stock, no weird drain at all.
[Vibrant Android Development] atinm:
It should still be disabled. If you do a logcat, you should not see anything related to gpsd coming in. If you do, it got enabled again - which it better not have.
[Vibrant Android Development] te_quiero_forever_girl:
flashed and touch to focus is no where to be found, even though it's said to be implemented in the changelog
[Vibrant Android Development] atinm:
Only on supported devices. SGS phones are not supported yet.
[Vibrant Android Development] Binary100100:
Not everything on that changlog applies to our specific device.
[Vibrant Android Development] hd2life:
Do you guys intend to implement aac and other codec's that are in touch wiz roms. There is and easy fix for xvid,divx, but i have still not found a program that plays aac.
[Vibrant Android Development] atinm:
No. These are closed source licensed codecs that Samsung paid for, we cannot rewrite them ourselves. And Samsung put in hooks in the framework to play them, hooks we do not have the source to. We are trying some things on the SGS2 to allow us to use the codecs and if we succeed, we will revisit SGS as well. But that is a ways away still.
[Vibrant Android Development] apollo15rover:
SGH-T959..

I know the touch focus doesn't apply but what about screenshots? Couldn't find anything in settings, CM7 settings, apps or Widgets?
[Vibrant Android Development] atinm:
Try the power button, there should be a screenshot option now in addition to Reboot, Power Off.
[Vibrant Android Development] apollo15rover:
Found it - thank you. Very slick!!!!
[Vibrant Android Development] bdubs4200:
Ok two questions, everyone who claims to get great or amazing battery life is on the stock kernel correct? Every custom kernel I've ran I can literally watch it go down, about 5 hours max, even on stock ... I unplugged at 850 @ 100% I'm @ 63% in an hour...

Also (let the obvious flame begin) why do I have 2 of everyone in my contacts? Whatever I check or uncheck its 2 of everyone or none...
[Vibrant Android Development] }{Alienz}{:
I use Glitch and nightly #39 for battery life. Non-stock kernels CAN lead to poor battery life but not always, all depends on what you use. I'mma look into the logcat today.
[Vibrant Android Development] VeryCoolAlan:
Does this mean that every Samsung phone released will only have kernel source and not full source?
[Vibrant Android Development] bdubs4200:
I can't find glitch anywhere.... unless its the i9k one but doesn't that need to be modified??
[Vibrant Android Development] beren28:
No, but a lot of things apply to ALL CM, even if it doesn't say vibrant on it . . .
[Vibrant Android Development] ZeroIsntTheHero:
If you look in the i9000 thread, there is a Vibrant variant of the kernel.
[Vibrant Android Development] apollo15rover:
He only posts in the i9k area, but he does have the Vibrant download there. I was getting fc's in later builds but when he releases V11 Ill give it a try again.. he generally does a pretty good job with those.
[Vibrant Android Development] cal4877:
Buy a HTC phone if you want full working gps. I currently have the inspire and cm7/miui works great
[Vibrant Android Development] vud911:
So weird. Yesterday noticed my light sensor doesn't work and now when I woke up, it says device not recognized on my computer. Can't get it to recognize it is connected via a usb cable no matter what I tried or cable.

Had to Odin back and reflashed the whole thing flesh. Now my usb is working properly again+light sensor too. Guess it pays to spend the extra time to go from stock->cm7 instead of Bionix->cm7.