yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tonyc0642:
I understand the idea. I just think it's strange what the Google devs didn't think was an issue. It's like they just said, "lets just make the Nexus S not do what every other phone, smart or not, has ever done." I'm too analytical. I should learn to dev.
[Captivate Android Development] TheEscapist:
I agree that it's a weird design decision from Google, but I know that I personally would never turn the phone off just to charge it, so it's not really an issue for me.

And yes, you should. 'Tis lots of fun. :D
[Captivate Android Development] tonyc0642:
I can find my own info, but where would you suggest I start? Apps? Kernels? Balls deep in some rom shenanigans? Where in your mind is a good jumping-off point?
[Captivate Android Development] AJerman:
Other phones using the same battery technology lie when they say 100%. They may set 100% to what is really 97% and slide the scale just a little bit. They decided not to lie and just tell the percentage as it truly is. I think that's better. We're talking about a couple of percent here, so it's not a big deal, but I can understand the confusion it could bring.

ROM development is actually easier than App or Kernel development*. App or Kernel development require fairly extensive coding experience. Most ROMs are just mash ups of different parts put into one package with varying degrees of modification depending on the creator's desires. Where to start depends on your experience and what you want to do.

*CM being an exception since it's an AOSP build that's actually being developed for our phone meaning a lot of coding does have to happen to get it all working.
[Captivate Android Development] TheEscapist:
What ever interests you. I happen to know C, and love low-level stuff, so I started in the kernel.

Rom development is probably easiest if you're just going to be modifying the stock rom, as it doesn't really require any previous knowledge that you wouldn't have already from the modding scene. App development requires knowledge of Java, and an idea for an app. Kernel modding requires knowledge of C and kernel development, but most of the ideas are already there, it just involves implementing them. Plus, all the kernels are open source, so you can look at other peoples code for tips.

And to be honest, it depends on how much time you're willing to put into learning it.
[Captivate Android Development] tonyc0642:
Lol I'm not confused about it, I understand. I just didn't understand why the google devs decided to switch it up on the NS rom. Quirky it is.
[Captivate Android Development] tonyc0642:
Time is my biggest issue right now. Well that, and zero coding knowledge. But its something I could probably get a feel for with enough independent research. Looking at other's work for tips is how I learned to theme WM lol. Thanks.
[Captivate Android Development] Johnston212:
Not sure if this helps, but I'm using a custom made vent mounted dock that works with my Otterbox and I use Car Home(beta) (best car dock imo), and things work nicely.

Just curious, but bluetooth voice commands still work right? Never used a CM ROM before and just wanted to be sure. I'm betting they are, but didn't really see anything in the OP. Might try this out tomorrow or tonight, since I'm off work for once.
[Captivate Android Development] Kaik541:
updates will be posted on cyanogenmod.com forums in the same thread. ota updates do not require wipes.
[Captivate Android Development] coderunner:
Are they going to be compiling updates to this and if so where do I follow it at?
[Captivate Android Development] sold1erjjt:
Looking good, I appreciate the hard work put into this, just to verify before trying, The RIL is the Radio Interface Layer right? so when I reboot I have to lock and the unlock to have a Connection? Just making sure, I know this is a total Test Release and problems are expected, but this is just looking pretty stable and great.
[Captivate Android Development] smokestack76:
Guys. I see far too many n00b questions in here. So please wait for a stable release. Its much safer. And better.
[Captivate Android Development] Kaik541:
see above

yes, that's what RIL is. small annoyance, but hey, CM7

this thread is specifically for end-user focus. if you have a long series of questions, please come to #cmsgs on freenode and we'll help you more directly, but this release is open to anyone, the disclaimers are just there because the team takes no responsibility for any damage done to your phone.
[Captivate Android Development] morgej:
In Call Recording

Anyone know if CyanogenMod 7 for the Captivate includes the ability to do in call recording from the South Korean version of the Galaxy S?

Thx.
[Captivate Android Development] techmik67:
Everyone is welcome to try, thats why its posted.... we have 3-5 people watching this thread and trying to answer all the questions....
[Captivate Android Development] Kaik541:
pretty sure it does not as the legality of this in a lot of locations is up in the air.

BUT I'M THE FASTEST!
[Captivate Android Development] coderunner:
I was over in the vibrant cm7 thread and they already have a 2.3.3 kernel with voodoo and other bug fixes.
[Captivate Android Development] h8rift:
You are, but techmik67 says this ROM does stuff. So he insta-wins lol.

Sent while mobile.
[Captivate Android Development] Kaik541:
kernel developers are welcome to take the source code and add whatever they want. our team will however NOT be adding voodoo sound as it can't be merged with the mainline (same as BLN). the only requirement for modifying the source code is that YOU MUST upload all your sources to a publicly available location (as required by the GPL... which a lot of people here don't seem to follow)
[Captivate Android Development] mcord11758:
So this rom will get ota updates through rom manager?

Rom manager says clockwork not flashed. Is it advisable to do so?
[Captivate Android Development] Kaik541:
as of right now, ROM manager will not do updates (we are waiting to push to mainline, ota is just the nomenclature for an update zip) and you should not attempt to flash CWM with rom manager
[Captivate Android Development] Rikusaki:
A question for the future:

When the Release Candidate is out, will it be a single. zip flashable through CWM (like a "normal" rom)?
[Captivate Android Development] Kaik541:
possibly, but can't say right now. efsbackup is still a necessary procedure that probably won't be integrated and you need to be on a kernel that supports CWM3 beforehand anyway (there are currently ZERO for the captivate).

so no matter what:

1) you must run efsbackup

2) you must flash a compatible kernel

before flashing (which is only two additional steps anyway)
[Captivate Android Development] jkat797:
Does this work on my samsung fascinate? I know its for the captivate but galaxy S's are similar. Please tell me if it works on the fascinate, thanks!
[Captivate Android Development] Kaik541:
no. your phone is CDMA, our is GSM.

use punk.kaos's release if you want CM7-like stuff on your fascinate.
[Captivate Android Development] DirtyRasa:
I can't charge my phone over 95%.

I'm pretty sure I flashed at 100%...

Any way to calibrate the phone or should I start over and see if that helps.
[Captivate Android Development] xxsxx:
I don't post too often (read daily though), but I just wanted to say thanks to everyone involved, including the speed in which questions are answered. You guys rock.

Everything is working fine except my wifi, says error everytime I try to enable it. Still trying to figure out why. Other than that, this rom is rocking for me.
[Captivate Android Development] Rikusaki:
Thanks.

I just wish Samsung would release the kernel source for their 2.3.2 build (JV1) so all these devs can start baking us some nice Gingerbread roms. :)
[Captivate Android Development] AJerman:
Yeah, I dunno. I'm not even sure where the change came. I know the Froyo ROMs we've been using do the same thing. I'm not sure if it's a device specific thing or something they changed in Froyo or something. Hadn't put too much thought into it since it makes no actual difference other than display.

I see it as something where the average consumer would like to see 100%, but Google is a technical company and I guess decided that telling the true percentage was better than lying for the sake of people seeing 100%.
[Captivate Android Development] whiteguypl:
ignore this please
[Captivate Android Development] TheEscapist:
Yeah, all it really takes is time and effort(and a helpful community like xda) to break into any of the dev scenes. And no problem, feel free to PM me whenever if you need help with anything.
[Captivate Android Development] TheEscapist:
Well, all of our Froyo roms were modified versions of the Samsung rom, so you can't really compare it. And the Nexus S isn't really designed for consumers. Yeah, they kinda advertise it, but you know the #1 buyer of Nexuses(Nexii?) is us. Still not the smartest decision, but at least most of us understand the idea behind it, instead of the average consumer raging that "OMG dis stupd fon wont chrge!!!!!!!?!?!?!?!!1!!!!FUKIN CR*P!1!!!!!!!!!!". :rolleyes:
[Captivate Android Development] AJerman:
To use your analogy, it's more like, the tank can hold 35 gallons, but you can only fill it 34 gallons because if you overfill it it could damage something. To say it's 100% charged would simply not be true. To say it's as charged as you can get it is, but it's not really 100% still. It's a little nitpicky, but hey, it's their decision right? Biggest thing is, we can only fill it to 34 gallons, so whether it says 100% or 97%, it's still got 34 gallons.

Edit: Oh, that is basically what you said, I misread something. Well, I dunno what to tell you. Write in and complain I suppose. It doesn't bother me either way personally.

Right, but was that something that the ROM developers changed? Or was it something in the Samsung Froyo too? I think I remember stock 2.1 saying 100%, I never used stock 2.2 though. Like I said, I don't know where it started.
[Captivate Android Development] FireRaider:
I Bluetooth through my Ford Sync and it seems to be working fine. I haven't tried the audio out from the USB connection or headphone jack though.
[Captivate Android Development] mcord11758:
We analyze battery too much around here

CM7
[Captivate Android Development] AJerman:
Haha, yeah.

Here's more info on Li Ion batteries if anyone wants: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries

It explains a little more about it.
[Captivate Android Development] RaptorOne3:
1 UP !

I couldn't agree more!

Cognition 4.1.1 which is based on 2.2 UCKB1 with stock Kernel, displays 100% charge when it's fully charged. It stays there for quite a while too. Battery life on Cog4 is absolutely astonishing. Seriously. WiFi will suck it down of course but it's still better than almost any ROM I've tested, to date. OCCASIONALLY it will drop to 99% when you unplug it from the charger. But CM7 doesn't even reach 100%, period. I've seen it get to 98%! Close! But no cigar...

Hell, even Eclair 2.1-update1 displays 100% when it's fully charged.

Inaccurate battery monitoring is another one to add to the list.

Along with absolutely horrible battery life.

I gave up running CM7 ROM for the time being. What is going on with the battery usage? I'm lucky if I get 5hrs out of my phone under normal usage on just my cell modem, no WiFi. Using WiFi makes it at least 15% worse...

As stupid of an issue as it is, it's a basic function of the device that shouldn't be compromised for any reason what so ever! This should be first and foremost for developers. If you cannot get the device to function long enough to get normal usage out of it then you fail. It's as simple as that. lol...

And I highly doubt the Google developers had anything to do with altering the percentile readout on battery monitoring. I know 2 people who have Nexus S's. Neither of them have the issue. As a matter of fact, the original Nexus S doesn't even have a percentile read out! (unless you go into settings, about phone, battery use) When their battery is fully charged, it reads Full. When they unplug it, it reads Full until you start using it. AS IT SHOULD!

Seen it with my own eyes... So all the hoopla about Google "telling the truth" about the battery percentage levels and what not, yea, it's exactly that, a buncha hoopla.

Yea this ROM has great visuals. Yea the Android Version reads 2.3.3. But its functionality at a basic level is compromised. Why the developers cannot reproduce the same results or diagnose the issue properly is beyond me. It makes no sense. Here we have almost every single person who's tested CM7 having battery issues, among other things, and they can't figure it out... Hmm... That's too bad...

No offense intended. But it's the truth. C'mon guys... What's REALLY going on behind the screens?
[Captivate Android Development] AJerman:
Yeah, I misread what you said. I made an edit on my post, sorry.

Regardless, bottom line, all ROMs charge your phone the same amount, and you get the same amount of battery out of them. It just depends on what they SAY when they are charged. Like I said, if it bothers enough people, send a complaint in. You might convince the CM guys to modify it in CM, but for the most part things are left AOSP which I'm guessing is where the issue lies. It hasn't bothered me enough to really think twice about it, let alone look up the code, but it may be in the kernel and if so, someone developing a kernel for CM7 could change it there. I'm bored at work, so maybe I'll look it up.
[Captivate Android Development] ksimilie:
For some reason when i turn off my data, my cell signal dies with it and I can't make any calls. Anyone aware of this?
[Captivate Android Development] RaptorOne3:
You couldn't be more wrong...

Flash to Cognition 4.1.1 and then tell me you get the same battery use out of all ROMs...

My phone on Cog4 runs 10-13hrs+ depending on how I use it. But even on heavy use it pushes itself 10hrs+. That's excellent battery life.

On CM7, even the latest "Nightly" I'm lucky if I get 5hrs out of it, MAX...

Hell I even went to the extent of leaving the screen on with the phone unplugged, no sleeping, just to see how long each lasted. On CM7 it lasted about 2hrs before it died. On Cog4 it lasted around 5hrs...
[Captivate Android Development] RaptorOne3:
Yes. You have to lock and then unlock your phone for the cell modem to reconnect.

Yet another annoying issue they can't figure out.
[Captivate Android Development] AJerman:
Sounds like issues on your end. You get the same charge capacity regardless. How optimized the ROM is may differ, but the capacity doesn't, it's regulated in the hardware. If you are getting 5 hours out of CM7, you have something draining your battery. I have no battery issues with CM7 at all, and I have gotten 20+ hours out of it many times. I have 4 hours on it now and am still at 70% with a decent amount of usage and ****ty signal here at work.

Have you re-enabled wifi sleep since it's been fixed in the newer builds (if you are leaving wifi on)? That's the only thing I can think would lower your battery life dramatically. Check your battery usage and see what's draining it.
[Captivate Android Development] mcord11758:
So why post here? If you are happy with stock kb1 to each his own.

I get 10hrs with 4hrs screen time. Not sure how much harder you can use it.

CM7
[Captivate Android Development] TheEscapist:
He didn't say battery life, he said battery, as in charge. There is still the same amount of voltage in the battery, CM7 is just less efficient right now.

Also, how the hell do you get only 5hrs? I get 16hrs with moderate usage even on the stock kernel, let alone when I'm undervolting.
[Captivate Android Development] RaptorOne3:
Umm, I never said anything about capacity. A battery is a battery. Thanks captain obvious.

It's the USAGE that's in question here.

Its something with the ROM and I do not believe your claims one bit. Either your lying through your fingers or your definition of "decent amount of usage" is WAY different than mine.

I reflashed from JF6 on every update. Master Clear'd too. It's not the phone or anything I'm doing wrong, I'll guarantee that. A hardware malfunction wouldn't make sense at all considering I get more usage out of the battery on other ROMs. Almost any other ROM for that matter.

On CM7, with EVERYTHING off (airplane mode) I STILL get battery drain, with the screen OFF! What's up with that?

Honestly, I don't see it guys. 16hrs+ of usage? 20hrs+ of usage?????? CMON that's a bunch of BS...

The damn battery is only rated for 5hrs 50minutes from Samsung with the screen on...

I don't understand how you are achieving these amazing battery life feats. Our definitions of "usage" must be much different.

16hrs aye? And how much of that is with the screen actually ON?
[Captivate Android Development] hkk:
Unread Email Counts

Hi,

Does not having unread email counts not bother anyone else than me? I like to see the counts on the home page icons.

For GMail, LauncherPro has the option to show it on the dock, but it's not working with CM7.

For Exchange email, I was using '1x1 Ultimate unread widget' , but it force closes on CM7.

Any alternatives?

Thanks,
[Captivate Android Development] whiteguypl:
pst.. follow my lead and lets not keep up the battery talk.. its just cluttering up there thread and its rude, and i feel like an ass for becoming part of it myself.

edit: on a lighter note cm7 seems to be falling together nicely. your chat logs are pretty funny sometimes too. keep it up.
[Captivate Android Development] RaptorOne3:
Right on... My apologies.

I understand it's a WIP. And on that note, no pun intended... However, a little criticism never hurt the perfection of something awesome did it?
[Captivate Android Development] chasesavestheday:
lost wifi after flashing 3/13 update. wifi error.
[Captivate Android Development] SweetwaterBurns:
Look for ADW notifier on the market.

LauncherPro's notifications are working fine for me except for the occasional refusal to clear every once in a while.
[Captivate Android Development] atinm:
md5 == hash so you can check whether your download was correct, usually compared with some sort of md5 checksum program. Please start with another ROM for now - something that is a lot easier to use than CM7. Try one of the many good Froyo ROMs please.
[Captivate Android Development] TheEscapist:
Try reflashing, sounds like it didn't flash the kernel modules correctly.
[Captivate Android Development] atinm:
If anyone had working Audience, we'd have it in CM7. That's on my list of sound things for Captivate.
[Captivate Android Development] AJerman:
[snip!] Not even gonna bother! Hahaha

You're right. I'm done talking about the battery. That could be an entire thread of it's own.
[Captivate Android Development] FireRaider:
MMS blank?

Has anyone had trouble with receiving video on MMS?

I can receive pictures just fine, although they say in properties that they are only 1kb.

But incoming video comes through blank and says its also only 1kb.

The video was only 263kb so it shouldn't have been a problem with ATT's 600kb limit.

I looked in settings and cant find anything pertinent to video MMS. And searching this and the other thread turned up nothing. I even rebooted, didnt help.

Any ideas? I am running the 03/13/2011 nightly.
[Captivate Android Development] atinm:
If you have zero coding knowledge, App or Kernel is not the place to start. Coding requires study from the very beginning - basically "Hello World" stuff first. Many of us went to college for that type of knowledge :-).

ROMs are a different type of beast and do not require coding knowledge usually - at least not the level of coding knowledge that Apps or even more the Kernel, requires.
[Captivate Android Development] chasesavestheday:
flashed back to 3/11 update and everything works fine.

prior to this happening i was running 3/11 with kb1 radio.

flashed jk4 radio along with 3/13 update. lost wifi.

flashed back to kb1 with 3/13, no wifi.

flashed back to 3/11, kb1, wiped cache again and wifi works. weird.
[Captivate Android Development] atinm:
It's a ROM thing that we haven't bothered with.
[Captivate Android Development] TheEscapist:
Flash back to 3/13, and grab me a logcat of when you turn on wifi.
[Captivate Android Development] hkk:
Thanks, will check it out.

Update: Gmail notification is working fine, but not the corporate email using the email client.
[Captivate Android Development] Zilch25:
Just wanted to stop in and say: Awesome job atinm, Unhelpful and the rest of you all :)

I think I'm annoying the crap out of my girlfriend with all the poking and prodding I'm doing to my phone now that I have CM7 to play with >=)
[Captivate Android Development] atinm:
You did read the part which said this is under active development, yes? What part of that do you not understand? Cognition . . . I mean c'mon - do you even understand what this is about.
[Captivate Android Development] atinm:
That's because we haven't optimized it yet. Please, go away until this is actually ready. Until then, stick with your favorite ROM.
[Captivate Android Development] atinm:
We aim to please ;-)
[Captivate Android Development] chasesavestheday:
okay went back to 3/13 and wifi error again. how do i logcat? possible to do without adb?
[Captivate Android Development] mcord11758:
I have stopped reading all other rom threads for the most part. very pleased here

CM7
[Captivate Android Development] TheEscapist:
Go into terminal emulator and type "su", then "logcat > /mnt/sdcard/log.txt". Make sure you press home to exit, not back. Then go and try to turn on wifi.

You'll have a log.txt on your sdcard after, post that.
[Captivate Android Development] chasesavestheday:
okay, sorry never did this before. the log.txt file i got was 93K, and is HUGE! can i perform a clear cmd and possibly just capture what im looking for?
[Captivate Android Development] AJerman:
Not really, it's the system's log output. When you run the command, it starts logging to file, and it doesn't stop until you stop the command. Most of what is in the file is probably excess after you attempted to turn on the wifi. You could run the command, go immediately into settings and try turning on wifi, or better yet, from the pull down drawer, then go back and stop the command in terminal to make it as short as possible, but the devs know what they are looking for so it's not as big a deal.
[Captivate Android Development] chasesavestheday:
ok so its basically running a capture. i wasnt aware i had to stop it. i found the command "logcat -c" which is suppose to clear it. re-ran the command and now my log is only 12k.

where should i post this thing?
[Captivate Android Development] atinm:
It would actually be useful to also have the dmesg - go into terminal emulator on phone and in the shell, do dmesg > /sdcard/dmesg.txt and then pull it off. The error is usually when your system modules don't match the kernel image. How did you do the update?

This is all easier with adb . . .
[Captivate Android Development] AJerman:
Oh, I never even knew about logcat -c, haha, nice find. I usually just do a search for whatever I'm looking for and jump past the extra junk, haha.
[Captivate Android Development] pparavas:
For all those who think battery life is poor, especially the one i quoted.

The battery life on this is really amazing, i did not get such a battery life even with stock froyo... after moderate to heavy usage,
[Captivate Android Development] chasesavestheday:
dmesg.txt

http://www.mediafire.com/?h3g925323l4tzpy

log.txt

http://www.mediafire.com/?oinnyv8hr2ngp8t