yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tbong777:
Very good post. I have been saying all along more that 15 hours or so is a waste unless one lives in the deep forest where there is no electricity.

That said. This is a "phone geek" forum. and people who mess with their phones are such, and as such, like computer geeks, they are concerned more with numbers and benchmarks than actual real world performance and use. People in AV forums watch their TVs not the content therein..HiFi geeks listen to their stereo systems....not the music,

Another 20 minutes of battery life or a few more hz of performance or the constant posting of meaningless quadrant numbers make all the difference in which ROM people use. All factors that are completely individual and good or bad completely depending on one's own idea of what the device should delver based on singular expectations.

Some choose certain ROMS because they need their hands held and the lesser used ROMS, or "new" ROMs (or better yet overtaken ROMs with ambitious new developers) get far more attention from and for those developers who are taking more time to peek in and answer their questions to estabish themselves as well while the longer more established developers have threads miles long with people with far less developer involvement as their is an experience community to deal with most of the questions that have been asked and answered multiple times in only the last 15 or so pages.

Axura has a "rep" in most threads when mentioned as a battery carnivore. Don;t know why I have used it and Assonance and Cog and Perception and my use has not changed and I see no measureable difference in battery life.

I do see OC/UV ROMs having far more issues than not on ALL ROMs. I have tried them all and personally don't see the benefits thereof. But the benchmarking crowd will put up with a lot to squeeze out yet a millisecond of scrolling time making their Cappy's feel...."snappier" a very common "scientific term" around here... whatever that means.

Battery life is terrible IF you need more than 15 hours and are away from a charger and do not take advantage of that luxury that is going away on many devices...the replaceable battery. It is terrible if you don't sleep, drive a car or work in a vacuum.

Sometimes I wish the developers would take ALL numbers of the battery icons....but that would dive some people insane...and send them back to stock,,or worse the iPhone where you have no choice BUT to ration your use.

Personally I don't want a phone a millimeter thicker than this for another 10 hours of battery life. This sides easily into a pocket unnoticed, and extra battery rests in my wallet. No need for more then really 8 hours and EVERY ROM has delivered that with heavy use WiFi on all day, syncs at minimums, calls, pics, music anything I wanted to do. Never blew out in less time than I needed to replace a battery or find some juice,

Don't get me started on GPS...it works now. end of story.
[Captivate Android Development] zelendel:
ok guys I am always up for a good debate but this has turned into more then just a debate. As far as battery goes each and every person will have a diiferent veiw on it. Take me for an example I have tried every rom on the forum and some that arent lol but my battery has always been around 10 hours or less but I know that is due to the way I use my phone. If adam cant reproduce the said issue then he cant fix it, and untill everyone flashes and runs thier phone the exact same way we will always have diff battery lives. So instead of complaining about it why dont we (those with the issue) dig in amd try to help find the issue instead complaining over and over about it.

Sent from my DarkDroid
[Captivate Android Development] Phoenix-Lead:
Zel,

Please close the thread. This is too much. I ask nothing and get **** on in return.
[Captivate Android Development] kangi26:
Have a great holiday everyone!
[Captivate Android Development] tbong777:
And this is why some developer threads are miles long and others come and go. If you are going to put something out there.One has to have a thick skin. the history of this Build is fraught with frustrated developers. Hang in there Adam. You have a good ROM.
[Captivate Android Development] gocats7:
If someone can post a rant about battery life, Im not sure why you think I cant illustrate that it is not as he stated for everyone. That was his experience, this is mine and I believe what I stated should have helped him so I was trying to contribute to the situation. I was not jumping on the bandwagon though.

Offering the information I provided should lead a person to realize that potentially its something unique to them or their situation since we are both loading the same ROM on the same phone with the same stock battery (assumption). I also pointed out I am not modifying the ROM in anyway so that he could have that as a comparison to his situation. I consider that to be helping as reading through the thread lead me to realize that it was something unique to me when I had battery issues. That knowledge is what lead me to investigate why MY phone was draining faster than others.

As I stated I dont know the answer but I have offered my experience and what I did to correct my battery life many times in this thread. To state it again, my corportate email was zapping battery. I turned off push email and my battery drastically improved. I was also using the JL3 modem which seems to use more battery as well and I changed the modem back to stock (when I was running 2.4). Now I am on 2.5 no changes with no push email and getting good battery life. Will this help others...no clue but I posted it several times and from what I can tell it was ignored and then onto more complaints about battery life.

So I have attempted to contribute to the solution, people only seem to want to blame the ROM. I contend that many of the situations are self induced, a bad flash, not flashing from 100%, not clearing battery stats, or maybe for some reason there is some variance in hardware. Either way I feel confident that many situations can be solved by people stopping to look to the ROM as the source and to their flash, their apps, their modifications, etc. I think it will take individual effort to solve.

To try to help more, when you were on Cognition or Perception were you running an overclocked version or one that wasnt overclocked? Perhaps that is a difference between the previous experiences. To get the the heart of the matter will require more details or effort.

Off my soap box, have a good day.
[Captivate Android Development] Phoenix-Lead:
I know it is good but my life can not keep revolving around this. I do this bc I enjoy it, get nothing in return(which is fine) and get **** on constantly. What am I hanging in there for??
[Captivate Android Development] joedon3:
Unfortunately I agree with you. XDA has a way of doing that to people. You're a gread Dev Adam and wish you the best! just let a few of us know where we can find you in the future if you continue to Dev! I'll run any ROM you're behind.
[Captivate Android Development] rockettman:
I second that! Thanks Adam for all that you have done for this ROM!
[Captivate Android Development] tbong777:
If you did this for YOU to make your phone better then shared it with the community you may not care so much what the community does or says.

The reason I always have an eye on DG ROMS is because although he has put out some real bummers since COG6 and P4..(REAL BUMMERS) he hangs in there. i KNOW he will be around for the longer term, I left DG's ROMs because the ROMS became so bad (as in unstable) as did some others leave as well . I then tried a few AXURAs and Assonance and liked both of them a lot but I KNOW DG will stay there and fix the problems and it appears anyway he be there a long time so I always keep my eye on that ball.

I also see other developers come and go and don't want to marry a ROM that will be devoid of support in a few weeks or months. I think if the developers want to plant a flag here they have to have a thick skin and more than that stick around through the mire.

Hand holding is nice but doesn't pay off. DG does not handhold. Never has and his threads require the noob to have a thick skin and READ. Not as friendly but DG stays out of them until he has something new or releases something new then hides. LOL and lets the feathers fly. I know now he is discontinuing OC/UV ROMS as the hassles are ot worth the benefits as I have been seeing all along. But I am not a bench marker. I favor stability and function over speed and excessive battery life.

I would say if you are fed up you should close up shop and develop for you own benefit. It is not worth the aggravation. And I can see how thankless people can be. Few donate to developers and hardly any to the site. I would not put too much importance those who don't give back anything but grief. They have a $500 device and piss and moan about a $2 Root Explorer Application that will save their asses.
[Captivate Android Development] zelendel:
As per OP request. Thread Closed. Good luck to you Adam and thanks for the great roms. Hope to see you around again soon, and as always feel free to hit me up in a PM if you need to reopen or for anything at all
[Captivate Android Development] Roof King:
I've never done a backup of the nv file and I started flashing when there was only the early versions of cognition out and I don't have any issues. Zelendel was working on including more info on this in the op.
[Captivate Android Development] Janax99:
I have the same issue. I first saw it, however, on the Axura 2.2 CE version, when RC1 (my first attempt at running non-stock) worked perfectly for me. Another issue I found starting with the 2.2 version - for me - was the short battery life problem that seems to be a major issue that gets discussed all the time. I re-trained it yesterday following the FAQ procedure, but after playing "Angry Birds" last night and leaving the battery at 70%, I woke up this morning with 4% battery remaining - the phone was locked and unused for the 6-7 hours I was asleep. So the problem seemed to come back(?)...

So I took the opportunity to upgrade to 2.3 this morning and I've been live on "2.3 CE xcal" for about 4 hours and battery life seems good again so far (I took advantage of the reboots to do battery "re"calibration at the same time). However, the phone has already "surprised" me again this afternoon by being powered down. At first I thought it may be the kernel, but I haven't tweaked OC/UV settings myself to date and now the "xcal" kernel doesn't even support that feature set, so I don't know where else to start.

I should also say thanks to the developers AND the support people in this thread who made things so easy to get things going! The phone definitely works more like a finished product with the tweaks included in Axura than it did when I first got it!
[Captivate Android Development] pimpnmaxima:
So is the Setiron Kernel 1.4.3 better than 1.4.6? Trying to understand the drawbacks of 1.4.3. Do headsets work with 1.4.3?
[Captivate Android Development] acornejo129:
GPS

For those getting good gps locks -

are you guys checking the USE WIRELESS NETWORKS box AND USE GPS SATELLITES box?

i get a lock with both on but its not accurate (within 10 meters, 50 meters etc..)

how is your guyss setup?

btw i changed it to supl.google.com and port

i did a position test and get satallite locks about 4-5 of them BUT when i use google maps it takes forever to get my exact location,

says location not available
[Captivate Android Development] mcord11758:
I do not click on wireless location
[Captivate Android Development] gunmetaldroid:
I have never even gotten headsets to work. I'm assuming these are the earphones with build in mics wired to them.

I used to just use earphones and talk through the phone's mic. 2.1 (Eclair) had that working, but anything further, it doesn't work. I don't understand how people keep saying that the headset issue is fixed.
[Captivate Android Development] double RL:
No mic on the headset for phone calls in 1.4.3. The best kernel I've used but that's the drawback. I'm using 1.4.6 1200 and my battery is good, headset mic works, and it's pretty dang smooth as well. If you're like me and use the wired headset, go with 1.4.6 1200. It's been stable and has no sleep death or charging issues either (at least not on my phone).
[Captivate Android Development] double RL:
On two Captivates, one running di11igaf 2.5 and one running Axura 2.2 and both running setiroN 1.4.6 1200, my stock wired headset and mic all work perfect. Never had an issue with the kernels with the fix in them.
[Captivate Android Development] soypoi:
was wondering if anyone that is currently using seti's kernel would be so kind as to post they vc settings? I know mileage varies on these but I just would like a slight guideline so that I can ballpark it a bit. Thank you in advance
[Captivate Android Development] mik3di3s3l:
in ce2.2 im trying to copy the stock wallpapers to my desktop but i cant find them through android commander??? are they hidden files???
[Captivate Android Development] KCutrer1:
Can anybody tell me where to find/or post that fight club sketch type wallpaper is located? I tried checking in the Launcher2.apk but I couldn't find it.
[Captivate Android Development] pimpnmaxima:
Did you just swapped out the zimage in the update folder to the 1.4.6 kernel?
[Captivate Android Development] double RL:
Mine runs great with -150, -125, -125, -100, -75, -50, noop 1200mhz. Some phones can uv more than others of course. I found where mine was unstable and backed everything down. Been stable under any load and no charging or shutdown issues.
[Captivate Android Development] Keland44:
okay i looked all over where exactly do you change this on the phone?

is this something we can only change on 2.3 or will this work on 2.2?

could a FAQ for this be added to the main page also?

Thanks for the great work everybody looking forward to flashing 2.3 later tonight
[Captivate Android Development] defnow:
Sgs tools>secret codes>gps test >supl setting....then change it there.
[Captivate Android Development] Keland44:
thanksssss

ZEL can you add this to the FAQ page please.
[Captivate Android Development] dizx:
Good luck with finals!

Go spend time with your family. A much deserved rest.
[Captivate Android Development] Falconary:
This is maybe a really newb question, but what is the difference between the two versions?
[Captivate Android Development] dizx:
+1

All this talk about the nv file makes me think we dodged a couple of bullets...?
[Captivate Android Development] lanisan:
Cannot connect to my bluetooth
[Captivate Android Development] mcord11758:
Odd I have been on the bluetooth in my cart all day
[Captivate Android Development] Roof King:
You can also create a shortcut to it because you will be using it from time to time. Long press on whatever screen you want to install it on.

shortcuts/activities/lbsTestMode

Now you have a direct link to it.
[Captivate Android Development] defnow:
Different kernels...its post on page 1 I think.
[Captivate Android Development] lanisan:
Ill try again after a reboot
[Captivate Android Development] ifederov:
Two questions:

1) If BLN is built into Setiron's, can it be disabled?

2) If I just flash 1.4.3 via CWM (adam posted the file earlier), should I disable voodoo first and then flash setiron? Is voodoo removed in the process?

I flashed 2.3 voodoo this morning - but want to give setiron's a try to see the results myself.

Thanks in advance.

Fed

EDIT: Don't know how I missed the posts saying you needed to disable voodoo before flashing setirons.
[Captivate Android Development] mcord11758:
This only exist on launcher pro
[Captivate Android Development] Falconary:
Which one is the best? :P
[Captivate Android Development] defnow:
Its more of a personal preference ....i've used both and they've worked fine for me. Im currently running with what 2.3 came with.
[Captivate Android Development] Roof King:
You mean not everyone is using Launcher Pro?

Get with it people!
[Captivate Android Development] Roof King:
BLN can be disabled in clockwork under advanced options
[Captivate Android Development] gunmetaldroid:
Anyone getting the message "There is no Seven service available" when synching their Windows Live accounts?
[Captivate Android Development] tsachi:
No problem on my phone, tried a couple different devices and both work

Sent from mobile xda

Captivate running Axura
[Captivate Android Development] id10terror:
I'm guessing my question got buried in the hundreds of posts. If noone has an answer or experienced this, then It must be something on mine alone.. I'll try 2.3 and see if it fixes this
[Captivate Android Development] gocats7:
I can't via the notification area in 2.3. I can only enable and if this doesn't make sense blame a long day at workand miller light
[Captivate Android Development] defnow:
I had that problem. When I flashed 2.3 the power widget was blank and wasn't working...my fix..just rebooted phone. Left it off for about a min...powered back on...then worked fine. So maybe just a reboot.
[Captivate Android Development] ifederov:
Thanks Roof King. I appreciate it.
[Captivate Android Development] Falconary:
I have flashed both versions but either one has SGS tools.¨

Edit: Nevermind, i downloaded it from market
[Captivate Android Development] Kizzmiazz:
well I'm loving 2.3 with set's 1.4.6 1200 kernel. Perfect combo so far.

Awesome work Adam ;)

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] AlsoNamedBort:
* splash *

I'm back in the pool, running v2.3 with the SetiroN kernel. Restoring apps via TiBu now... phone seems... uh... warm. I'm not used to it being warm.

Then again, it's cold down here, so maybe this isn't such a bad thing. Next steps, restore SMS and then try out the GPS settings.

Thanks again adam, hans, and the rest of the thank-you list.
[Captivate Android Development] The Balvenie:
hands free problem

great rom the only issue i'm having is the hands free doesn't work. i hear the incoming call through the headset (wired headset that came with the captivate) and the phone speaker but when i answer the call (via the phone screen because the headset button doesn't work) the headset doesn't have the call. i have to use the phone.
[Captivate Android Development] Haighter:
MMS Issue

Finally have a fairly serious bug. I can not get MMS to work. Text messages are no problem, but I can't send images. I've tried multiple APN settings (all the usual suspects) and keep getting "Error in server response."

Any suggestions on APN configurations are appreciated.
[Captivate Android Development] Roof King:
2nd post of the thread has the settings
[Captivate Android Development] lanisan:
I had music playing over a 3.5mm and turned on bt and have been.on that same call since.. the gallery is not.working for.me.right now.either
[Captivate Android Development] Kizzmiazz:
I have to ask the people having problems. First did you guys flash back to stock with odin 1 click and the then master clear . Second did you use tibu to restore your apps ? Both these things are usually major problem causers lol .

I only ask this cause I have not one problem yet with 2.3 every thing smooth as butter. Not one fc , knock on wood.

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] The_Zodiac:
i dont see it dude
[Captivate Android Development] lanisan:
I flashed to stock and did an MC. Im.actually having.some frustrationustration as we speak.. things keep crashing... but again I've been on a call for 2 hours
[Captivate Android Development] Roof King:
AT&T Wap Settings

ATT

wap.cingular

not set

not set

WAP@CINGULARGPRS.COM

not set

not set

http://mmsc.cingular.com

wireless.cingular.com

80

310

410

not set

internet+mms

This is in Zelendel's post.
[Captivate Android Development] Haighter:
Let me again emphasize I have tried several settings, including that one. I guess I will post each one I've tried... Sorry in advance for the clutter!

Attempt 1

Name: ATT

APN: wap.cingular

Proxy: Not Set

Port: Not Set

User Name: WAP@CINGULARGPRS.COM

Password: Not Set

Server: Not Set

MMSC: http://mmsc.cingular.com

MMS Proxy: wireless.cingular.com

MMS Port: 80

MCC: 310

MNC: 410

Authentication: None

APN Type: internet + mms

Attempt 2

Same settings as Attempt 1, just added CINGULAR1 as Password.

Attempt 3

Added Proxy: wireless.cingular.com and Port: 80

Attempt 4

Then dropped the User Name and Password

Attempt 5

Dropped the Proxy and Port

Changed User Name and Password to lower case

Attempt 6

Dropped User Name and Password and re-added Proxy and Port

Attempt 7

Went back to Attempt 1 and dropped http:// from MMSC

And then I lost track of the different combinations I've tried... It must be a combination of one or more of my attempts.
[Captivate Android Development] Kizzmiazz:
Hmm very weird. Flashing just seems to be hit and mis lol. How about using tibu , did you restore using tibu and if so what method?

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] AlsoNamedBort:
For my phone....

Ok so for my phone at least, let's call SetiroN a big old -1

Booted, played around a little bit, fired up TiBu, started a restore, froze up solid. Battery pull. Rebooted, played a little bit more, opened Market, froze up solid. Rebooted, tried to apply lagfix (e4), rebooted again, about 5x FC on the startup screen, then a solid hang, battery pull.

Opened CWM, reboot into download mode, started to Odin 1-click, froze, battery pull, 3-button power up failed, had to use the jig. Jig saved my tail a second time.

Just flashed back to stock. Battery is at 92%, so I'm going to let her charge up for 15 minutes or so and then try v2.3/xcal.
[Captivate Android Development] spacecase-25:
Can someone post up the old music player?
[Captivate Android Development] lanisan:
No I don't use tibu. I used astro to restore my home screen but no data, just appearance. I'm very careful not to do a data backup
[Captivate Android Development] The_Zodiac:
okay i see it now

but where can you change AT&T Wap Settings at?
[Captivate Android Development] Kizzmiazz:
Ok Adam request time lol next version can we get someone to theme the dialer, it looks so out of place or even just get the old themed one back maybe fixed with the new one.

Second , I know it just might be impossible but new dev maybe can happen , get the kernel info to show what kernel we are using. Just sucks when your like me flashing every new kernel and forget what one you have running when your ready to flash back or new lol.

Other than that man I'm loving it so far.

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] lanisan:
Check your pm and see my response above :)
[Captivate Android Development] Phoenix-Lead:
Another good combo is Axura 2.3 with SetiroN's 1.4.6 which I have right now:p
[Captivate Android Development] lanisan:
Your on...

Is there a link to 1.4.6 nearby? I'm in the xda application but can change to the browser
[Captivate Android Development] Kizzmiazz:
Hmm maybe just a bad flash. What kernel are you using and if oc what Mhz?

Not saying your a noob or bashing just so you know ;) I'm just running perfect with my setup below.

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] lanisan:
-1 speed dial, having issues with it as well as the previous build.
[Captivate Android Development] Kizzmiazz:
That's what I'm using to. I'm sticking with the 1200mhz though , very stable on my phone.

Sent from my SuperDuper!Captivate | AXURA Captivate Edition RC 2.3 | SetiroN's SuperOptimized v1.4.6 UV/OC @ 1200Mhz
[Captivate Android Development] Phoenix-Lead:
Do you know a themer? I don't. If you do see if they can theme the dialer. in regards to the kernel version. I think I can take care of that.