yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] halfsoul:
It's not. Only faux G

---------- Post added at 07:20 PM ---------- Previous post was at 07:00 PM ----------

Well, it's the same behavior for me every day when I get home from work -- battery starts tanking even though I'm barely using it. Any suggestions for investigating/troubleshooting?

I looked in the logcat, and one thing stood out: a BUNCH (hundreds) of these entries:

I/TelephonyRegistry( 201): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=pdp0 networkType=3
I/TelephonyRegistry( 201): notifyServiceState: 0 home AT&T AT&T 310410 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 201): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=pdp0 networkType=8
I/TelephonyRegistry( 201): notifyServiceState: 0 home AT&T AT&T 310410 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 201): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=pdp0 networkType=3
I/TelephonyRegistry( 201): notifyServiceState: 0 home AT&T AT&T 310410 HSDPA CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
I/TelephonyRegistry( 201): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=pdp0 networkType=8
I/TelephonyRegistry( 201): notifyServiceState: 0 home AT&T AT&T 310410 UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false

Can anybody tell me if this is normal or maybe indicates a problem? Any other suggestions or info would be great too (in case I'm barking up the wrong tree).
[Captivate Android Development] Raul77:
anyway to get BLN working with this ROM ?

Thanks,
[Captivate Android Development] sixstringsg:
Read a few pages back before asking please.
[Captivate Android Development] skatcat31:
Pay do I installed the latest nightly. Any idea why the att bump charge screen and boot screen came up before it booted?

Sent from something from somewhere
[Captivate Android Development] parkerdjohnson:
im most likely an idiot

I am running the #123 nightly and I decided to flash the latest glitch kernel. I can't get past the CM7 Boot animation....

Help :p
[Captivate Android Development] shaolin95:
First of all asking for help for another kernel on this thread is asking for troubles...you wont be treated nicely...just so you know.

Second, that is a know issue....need to wait for an update and there is a thread for that kernel in this forum so best to post there when having issues with it.

Regards
[Captivate Android Development] flucks:
This may be the wrong place to ask this, but is anyone getting better battery life with different modems? I lost 30% of my battery to "Cell Standby" last night. Appreciate the help.
[Captivate Android Development] johnhazelwood:
I noticed my microcell isn't connecting (which I literally got working again the night before I flashed 124. Your logcat indicates utms (which is what I noticed becomes active when I connect to my microcell), so I'm wondering if you have a microcell as well and it looks like my novice look at your logcat shows umts isn't supported.

Edit: Just looked at my logcat and I get the same, so presumably it's normal.
[Captivate Android Development] SweetwaterBurns:
I've had good luck with BVJJW2 but it depends a lot on your area and phone. JK4

is a pretty good one by consensus. Check the modem thread to see what people are saying about them.
[Captivate Android Development] nkrick:
I just recently tried out KG3 and had better battery life than JL3. I ended up switching back yesterday afternoon when I was not able to send or receive text messages. I think it may have been a carrier issue though, so I will probably try KG3 again soon...
[Captivate Android Development] Mmcavoy:
Installed latest nightly...seems to be working well.

However, I was hoping to do a restore with Titanium Backup and there is no android market. I tried installing it from the web and it says that it's installed however, it's not in my app pages or my app settings.

I have my google account synced.

Wondering if maybe someone has a quick fix...
[Captivate Android Development] Raul77:
same here... i dont have anything either. i would use NOLED but the problem is i find it sucking my battery like there is no tomorrow !!
[Captivate Android Development] yuhenyo:
just to be super sure.. i can flash the gb bootloader using the orange cwm that comes with cm7?
[Captivate Android Development] johnhazelwood:
It looks like there was a kernel change in 123 or 124. How do I get back to the old kernel? I assume a nandroid restore will not do that, do I need to reflash a full 103?
[Captivate Android Development] airtower:
Correct, nandroid doesn't restore kernel or modem.
[Captivate Android Development] ninjuh:
Am I the only one that has a hard time understanding the changelog? I read it all the time but literally only understand 1-2 words out of the whole thing.
[Captivate Android Development] Kaik541:
actually, nandroids DO restore kernels on CM7
[Captivate Android Development] Spritely:
Sounds like you haven't flashed a gapps package. Pretty sure I found my copy in the rc1 thread.
[Captivate Android Development] J-Wall:
If I flashed CM7 over MIUI would it wipe my data or mess up battery calibration?
[Captivate Android Development] sixstringsg:
Nandroid restore does restore kernels, it's /boot.
[Captivate Android Development] Mmcavoy:
Thanks, I had not. However, I have just used rom manager to flash the latest google apps package (20110828 universal, Aug 28, 2011) and there is still no market.

Do you have a link to a hard copy I could install from SD?

Thanks for the help.

* It appears that clockwork recovery had not installed properly therefore phone was rebooting before installing the package....I downloaded and installed the package from http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps and now have the market installed....however it crashes frequently and I can't go into "my apps" without a crash.
[Captivate Android Development] johnhazelwood:
LOL shoot! So I installed 103 to get the kernel back (assuming that's whats causing the utms issue), restored my nandroid of 123, which means I reverted back to the kernel....frizzle frazzle..feeling stupid now...

Hmm just checked and realized 104 had the kernel change..so maybe it's not the kernel that caused problems in 123 after all. Aha 124 updated kernel again.
[Captivate Android Development] airtower:
That I did not know. Thanks.
[Captivate Android Development] halfsoul:
Yes, I have a Microcell, I am trying to figure out why using it drains my battery so fast.

You get the same messages when you're connected to the Microcell or when you're connected to regular AT&T towers?
[Captivate Android Development] johnhazelwood:
I checked when not connected to microcell and got same I/Telephone entries. I'm not sure about battery life, as I usually have phone plugged in when home, but did notice when I got the microcell working again it went to UTMS, otherwise it's HSDPA. This morning it wouldn't work with microcell again. I've reverted back to 123 to see if when I get home it works again, and then I might try 103 or 104 to see if that fixes it.
[Captivate Android Development] glos7777:
it seems "Led Notification Setting" coming in next nightly isnt it ?
[Captivate Android Development] simple man:
I flashed it over miui, but I formatted; system,cache,data,datadata, then factory data reset, to avoid problems.

Sent from my SGH-I897
[Captivate Android Development] parkerdjohnson:
Got it. Sorry bout that. Ill take a look.
[Captivate Android Development] smeltn:
so I just got an email from AT&T about tethering myself.

I have NEVER gotten one in the past, until upgrading to CM7 nightlies..

Coincidence? Maybe but strange
[Captivate Android Development] Jemack:
They had to start sometime, so coincidence......absolutely.
[Captivate Android Development] nkrick:
That is what the changelog indicates.
[Captivate Android Development] yuhenyo:
clear market data in application settings and also, change the language of your phone to English (US).
[Captivate Android Development] stewtang:
I got one today too, what a bunch of BS!
[Captivate Android Development] yuhenyo:
Can you give a link to the bootloader you're using? I'd feel a lot more safe flashing something I know that works from somebody else already. :)
[Captivate Android Development] RichMD:
Is stock KF1 OK to use before flashing this ROM?

I have already successfully flashed KF1 stock and then CM7 a couple of times before. However, I've never been certain that couldn't cause any problems. I know the OP states to use stock eclair/froyo rooted. I have a 1011 build and am already running KF1 bootloaders. I prefer not to flash anything with bootloaders at this point. I know Cezar created a JF6 OneClick without bootloaders but it says that can cause problems for builds newer than 1010. I "assume" it only causes bootloops which would be fine since I would next flash a kernel with CWM and then flash the CM7 zip. However, I've never been certain that wouldn't cause problems so I have opted to use MrHaley's 3 file KF1. I assume that is fine but could someone confirm? If it is OK then maybe the OP should include starting with stock rooted GB as well?
[Captivate Android Development] mystichobo:
hey guys, flashed nightly 123 on a whim the other day,

Is it just me or is the graphical fidelity severely reduced?

I came from pinnacle, and my wallpaper which has very fine lines across it, seemed sharp, wheras in cm7 it was kinda blurry, almost as if the amount of compression had increased on it or something.

Same launcher (zeam), using its inbuilt wallpaper management.

Anyway,

I've moved back to apex now (mainly missed the dialer) and the problem is gone.

Does cm7 handle the graphics driver differently or something or am I just imagining the difference?
[Captivate Android Development] Jusrertiner:
Does anyone else have the problem of no 3g?
[Captivate Android Development] pandakh:
How do I check what nightly im on?
[Captivate Android Development] hauj0bb:
Hmm, I wifi tether all the time to my tablet - not received an email yet. Must be coincidence, I'm pretty sure the tethering features are the same across the various roms, at least I can't imagine CM7 being any different.

Not sure how they can detect whether or not you're tethering... maybe it's some sort of pattern recognition.
[Captivate Android Development] rsx19:
i dont need to clear system/cache before updating? ive always updated by clearing cache/system/dalvik then installed the rom

but under the instructions it just says to do a nandroid then flash over
[Captivate Android Development] RockRatt:
I ONLY wipe dalvich cache when I am updating via rom manager, and IF/WHEN I decide to flash through cwm I wipe cache and dalvich cache ONLY then apply the update. I have ONLY ONCE OR TWICE EVER did a factory reset/wipe data but that was when I had some kind of issue and wanted to start fresh.

So to answer your question NO you don't need to.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] rsx19:
Cool does the flashover require to reflash gaps stil
[Captivate Android Development] RockRatt:
When I use rom manager to download and install I always tick the gapps also, I believe it just then checks for it and if you already have gapps it just bypasses it or something. As long as you only check the wipe dalvich cache NONE of your apps will be lost or its associated data. If you use any kind of metamorph you will need to reapply it, also you will need to set/reset whatever voltage settings and Undervolt settings again but both of these are very easy and quick.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] RichMD:
To clarify, I flash KF1 after trying other custom ROMs like Apex 10, etc. I want to keep the KF1 bootloaders so I can run anything but I want to clarify if stock KF1 is just as "clean" for a base before flashing CM7 (or MIUI) as eclair or froyo. I know the filesystems are different so I "assume" everything is wiped but I'm not certain if all partitions are reformatted during an install and I could have space issues, etc if I started with KF1.
[Captivate Android Development] ou812bkewl:
Is anyone else having problems with ROM Manager not seeing that there are any builds newer than #124? I didn't see any post about this yet. I have the latest version of ROM Manager Premium and have Captivate(MTD) selected with CWM 3.x.x.x as my CWM option. It is the same setting I have been using and showed the current build to be #124. I have even tried switching it to 2.x.x.x CWM option but have had no luck. I can still download from the site listed in the OP just fine.
[Captivate Android Development] XsceneXhippieX:
or you can use any root explorer thats capable to backup your scripts (that may or may not be deleted upon the update depending on the script type) and after updating, and setting anything you desire up, then a reboot, placing the scripts back directly into system/etc/init.d and fix their permissions manually is faster but through cwm would also work, and voila! you're done, updated with everything still in place.

the one piece of the process that takes me the longest upon an update now-a-days is the chainfire3D graphics driver, thats because it requires a reboot to install and the 45seconds-1minute boot time takes longer than anything else in the update process (other than the first boot)
[Captivate Android Development] ballz0iron:
+1 seeing the same thing
[Captivate Android Development] techguy615:
Same here..

Yep... was wondering that myself. I did a manual download of the #126 build and installed from recovery this morning with no issues. Rom Manager didn't see the latest nightly when I told it to check yesterday (#125). I thought it might be a fluke, but it did the same thing again this morning.

:confused:
[Captivate Android Development] smeltn:
You know looking at the nightlies though, I see they changed something to do with ATT data

New AT&T APN data (android_vendor_cyanogen)

I wonder if that has anything to do with it?
[Captivate Android Development] jacorso:
I had the same thought after reading about how they catch tethering on the iPhone through the APN.

Does anyone know how to check this?
[Captivate Android Development] lanisan:
I'm curious about this overclocking (I get) undervolting (have no clue) action. My battery life pretty much sucks but then it always has. I don't blame the rom at all because I see tons of people with great battery life. I heard undervolting greatly helps battery life and wondered if you could point me in the direction (or pm me ) where to get started.

Thanks
[Captivate Android Development] loserskater:
They reverted that change a couple days after (all on the same nightly). I think AT&T are just cracking down. Not entirely sure how though.
[Captivate Android Development] ou812bkewl:
The AT&T APN entry was updated but then reverted back to original before nightly #125 was released. They updated it to the 4G APN, but we would need a 4G plan to use it so they changed it back.
[Captivate Android Development] EnemyOfGlaDOS:
sup lanisan!! here's a short quick helpful guide to get an idea of OC and undervolting.. It takes LOTS of time and patience to nail some high OC steps, but undervolting should be less painful ;)

http://xdaforums.com/showthread.php?p=12910471#post12910471
[Captivate Android Development] airtower:
+2

Also, I don't know what I did, but ROM Manager cannot pass commands into recovery for me. The phone simply reboots without doing whatever I instructed ROM manager to perform through recovery

edit: had wrong recovery version selected in RM. works ok now (still doesn't pick up nightlies though)
[Captivate Android Development] zj4x4:
Re-loving my CM7 Captivate after finally deciding to go back to stock and start over again. Went from battery drain of 60-80% over a 12 hour period to 28% in the last 14 hours with e-mail sync in Touchdown and wifi on the 'never sleep' setting. I had been updating nightlies about every other week since we got on the build bot and am now on a fresh 125.
[Captivate Android Development] lanisan:
Thanks Coreym, which kernel are you using?

(also I can't see how but the radio/modem wont make a diff right?)

I see Shaolin's post from April and updated for CM7, do these #'s still hold true today?
[Captivate Android Development] mgfjd:
Anybody knows what are the Ondemand settings for CPU governing?

I think we need another Ondemand2 with 95% load for better battery life.

Thanks
[Captivate Android Development] EnemyOfGlaDOS:
For the most part the numbers still hold true. I haven't seen a difference using different modems. Also testing the glitch beta kernels at the moment :)
[Captivate Android Development] RockRatt:
++ here. I am downloading it now via http://download.cyanogenmod.com/?device=captivatemtd

I will see after updating if it will see the nightlies again.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] sixstringsg:
More than likely, if you want different governors, flash a custom kernel.
[Captivate Android Development] Raul77:
those who OCed to 1.5 or even 1.6, how did you get that high? my max is 1.3 cant go any higher than that, i assume u r using some other kernel ?
[Captivate Android Development] sixstringsg:
A lot of them use the kernel I maintain (the glitch kernel) or Zach's kernel.
[Captivate Android Development] airtower:
Third party kernel. I use glitch, but it doesn't currently work with the latest nightly (soon though I hear). The max on it is 1.7

but that's not to say your particular phone will be able to get that high
[Captivate Android Development] astrocrep:
Anybody else having poor battery life since upping to the nightlies? I was hanging on 104 with everybody, then I upgraded to 123 and then 125, battery has been terrible...

Edit: Stock Kernel, 1ghz Max, -125 u/v @ 1000, 800 with 400, 200, 100 @ -150

Anybody else seeing that?
[Captivate Android Development] johnhazelwood:
Anyone else have luck with attaching to microcell on builds greater than 123? I reverted back to 123 and attached perfectly to microcell again. It seems like 124 might have done something that the microcell doesn't like. I'll try the latest again just to confirm.
[Captivate Android Development] Raul77:
same here ! i thought it was me only. i am having HORRIBLE bat. life as well. i used to charge my phone before going to bed (still had 15-20% left), now at around 8pm, phone is dead.

---------- Post added at 08:14 PM ---------- Previous post was at 07:46 PM ----------

I just flashed your kernel (glitch) its stuck on android on skateobard for over 10 min, is this normal?
[Captivate Android Development] EnemyOfGlaDOS:
3rd party kernel.. le glitch!
[Captivate Android Development] Raul77:
i just flashed glitch, its stuck at android on skateboard and rotating arrow for over 10 min. what do you suggest?
[Captivate Android Development] EnemyOfGlaDOS:
That's because the v12beta (im assuming that's what you flashed) isn't working with the latest nightlies yet. Should have everything solid in the next few days, but Glitch was very ill and Six has been doing his best to keep development going. He is working on it as we speak ;)

To get stock kernel back, just reflash the nightly. OR, if you wanted you could hop on IRC to get a beta to test with the newest nightlies.. but those as well are being tweaked and redone.. but i do know that they will flash and work for the most part with nightly 126.. :/
[Captivate Android Development] Raul77:
i actually tried V11 LL . but will try nightly now.

thanks
[Captivate Android Development] EnemyOfGlaDOS:
yeah v11 def won't work sorry :(
[Captivate Android Development] Raul77:
thanks, i am on 124 build, which version of glitch works? (if any) ?
[Captivate Android Development] EnemyOfGlaDOS:
For anything past 104 your gonna need to hop on IRC in the glitch kernel thread (first page in the OP about half way down) and get one of the latest betas. They will flash and work and you may even really like it, but like i said- they are still being tweaked as they are not ready for final release.
[Captivate Android Development] sixstringsg:
I don't have one out yet. Wait a day or two and I'll have it on that note, let's leave the discussion on the glitch thread please.
[Captivate Android Development] EnemyOfGlaDOS:
That's what we're doing ;) . We should KEEP the discussion on the glitch thread :D

..lol, jk of course :p
[Captivate Android Development] n0stalgia:
LED Notifications! Thank you so much! <3 <3

(now you'll just need to merge voodoo color and this will be perfect ;))
[Captivate Android Development] Kaik541:
not to give too much away, but stuff is in testing...
[Captivate Android Development] XsceneXhippieX:
this.... is..... everything ive been waiting for :) WOOOOO!

(generic statement about a feature i want implemented on top of the awesome features in testing like maybe togglable KTLO in cmsettings ;P seriously jk though voodoo color is AWESOME!)
[Captivate Android Development] mnjm9b:
Haven't had problems on any of the nightlys....on 125 now.
[Captivate Android Development] ninjuh:
Flashed latest nightly. Amazing work as always...gets better and better.

I recommend allowing at least a week between flashing each nightly.
[Captivate Android Development] iphone=closedsystem:
Loving it, super snappy. :)

Quackafella Records INC
[Captivate Android Development] cfili:
Loving the LED notifications, thank you devs!

Sent from my SGH-I897
[Captivate Android Development] halfsoul:
LEDs aren't lighting up when I get emails (using K-9). SMS works fine. Anyone else?

Edit: this fixed it for me:

- Uncheck blink LED in K-9 settings

- change app K-9 setting to force on event in LED notifications settings
[Captivate Android Development] Mmcavoy:
Just wanted to share some love for the Devs I was comfortable with my OCed Perception ROM but this was an amazing upgrade! You all rock hard.

Thanks!

Big Daddy Mac.
[Captivate Android Development] DrunkenWonton:
Quick question, I have never updated a rom, but do i just download the newest file, and use rom manager to flash in recovery?
[Captivate Android Development] Sublim3_Tilt:
Does the output of the cappy running the latest nightly work?
[Captivate Android Development] EnemyOfGlaDOS:
Yup or flash manually in recovery yourself!
[Captivate Android Development] EnemyOfGlaDOS:
What do you mean? There is no TV out if that's what your asking?
[Captivate Android Development] Sublim3_Tilt:
Yes, thats what I was asking, Is there a tv out or progress on getting the TV out functioning?
[Captivate Android Development] EnemyOfGlaDOS:
We all want it so I doubt its being overlooked but there is other stuff of more importance being worked on. Not sure where they are at progress wise w/ TV out. :(
[Captivate Android Development] Jusrertiner:
New glitch kernel out now working with new nightly
[Captivate Android Development] tiuk:
Works great, huge accomplishment for all involved.
[Captivate Android Development] dalythu:
I just want my softkeys to stay backlit in the dark instead of them turning off after two seconds. Any help?
[Captivate Android Development] musicalmindz:
You know, I think I REALLY need to do this. I am getting massive drain over 12 hours and I know it can't be correct.

Can anyone point me to some instructions for the best way to start from stock again? (I am currently on 101) I think this is the rough procedure but wanted to know if I was missing anything:

0. Titanium Backup

1. Odin 1 click

2. Root

3. Install ROMManager

4. Flash ClockworkMod Recovery. Pick Captivate (MTD)

5. Install latest nightly (wipe all)

6. Restore titanium backups

7. Profit!

I can't imagine the battery drain I am seeing is normal so I think this is my only recourse at this point.