yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] XsceneXhippieX:
I have never odined back to stock, i ALWAYS wipe my cache/dalvik cache almost every time i boot to recovery for any reason even if it isnt necessary, but i was using the new talonMTD kernel when i was getting the issues but factory reset via cwm clean install of nightly 91 and restore of all meh junk through titanium bkp (only apps/their data of course) and im up and running lightning fast again, i understand that 3rd party kernels can cause problems but the ONLY feature i want is the ONLY feature missing from the hacksung kernel: voodoo color with nexus s framebuffer port included, if anybody here on this thread would also like to see this included in the "official" cm7 for the cappy might we find a way to "rally the troops" and let the cm team know? i am willing to do whatever to get voodoo color included in the stock cm7 kernel because ive conditioned my eyes to the color difference and now "stock" looks EXTREMELY washed out, dull even, and i cant for the life of me figure out why voodoo sound is included yet not the at least near as popular voodoo color?

does anybody else share this desire for voodoo color? if so lets let the team know officially so that we can achieve said goal. the stock kernel seems to run MUCH smoother than glitch, NEO, talonMTD, etc..(all the most recent release) on the newest nightlies on my personal phone anyways honestly, at least since nightly 80ish
[Captivate Android Development] MadeInMex4usa:
Its a Facebook bug next time click on most recent then choose any other .let it load turn back to lost recent...
[Captivate Android Development] RockRatt:
First a reboot will normally fix the android is issue from what I have read over many months. NEXT use the app OS Monitor to see WHAT actually is making the android is issue happen. Normally it is an app that is causing it in the background. So you figure out which app and then figure out either how to fix it or get rid of it. NO NEED to go back to stock. IF it is a app causing it when you come back it will most likely come back again at some point. As far as your contacts as long as you save them to Google you will always have them after you set up your Google account. Also for your apps if you are having an issue with them make sure they are backed up with titanium backup so you can restore them whether or not the market shows them as installed.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] abee_13:
When Android system is high in battery usage try turning off the phone and taking out the battery for about 10 seconds or more. That always seems to help me out.
[Captivate Android Development] shaolin95:
Maybe you are right LOL

I think my phone got used to the extended battery and now does not like the thin batteries :eek:

Mine says Good... how knows :-)
[Captivate Android Development] FireRaider:
First phone call, no received sound?

Has anyone noticed an oddity where the first phone call that they recieve after a reboot has no sound from the caller? They can hear me, but I cant hear them. Calling back fixes it and then I don't notice it again for a while. I dont get a lot of calls so for a while it puzzled me but I have had it happen often enough now that I am almost positive it's the reboot doing it. Everything else works fine though.

I have several batteries so I reboot frequently as I swap them out.
[Captivate Android Development] XsceneXhippieX:
Honestly, there is no need to ever flash to stock 0.o i understand the process gets rid of nonsense that can build up but if you wipe every time the crap wont build up and stink up your performance (pun intended), and i had been monitoring WHAT was actually making android OS act up, there were no trouble apps whatsoever so i wiped, did a clean install of the newest nightly, and BAM my phone is running faster than my friends atrix without any weirdness once more lol :) titanium backup is actually pretty useful when you are staying on one rom that updates a lot, took me a literal 20 minutes to get back up and running exactly as i was before the wipe, which is only extra long because i did a factory reset (thats including the backup i made in the process)
[Captivate Android Development] sleither:
I know I get lag using Netflix 1.3 on my RC1 Captivate. If I roll back to 1.2 my issues go away.
[Captivate Android Development] gstern:
This has happened to me a number of times in the last few days. Haven't noticed its only on the first call after a boot though, seemed random to me. I'll reboot now and check into it.
[Captivate Android Development] littlewierdo:
1. Titanium backup has a market link feature. Open TB and hit your menu button, then hit More and then hit Market Doctor. This will re-link all your apps to the marketplace so they show up as installed.

2. Regarding the battery, I posted a link a few pages back to the exact extended battery I use. It is a 3300 mah seido battery. Costs about $60 but my phone will run for two days off this beast. Keep in mind, it will increase the weight of the phone (by about 15-20%), the thickness of the battery compartment (about doubles the battery area of the phone), and comes with a replacement back cover that has a rubbery texture. Alot of negatives but it keeps my phone running for nearly two days with wifi and bluetooth always on (if I had to, I could probably make the phone run for 3 days by turning off all the radios).

In that same post, I had several recommendations for battery saving techniques as well (including some more advanced options - I hope it was informative to advanced android users as well as beginners). If your battery starts draining quickly out of the blue, it likely is because of a rom or app you installed or updated.

Lets not forget why we prefer Android over the iphone - control. But with control comes responsibility. Use Autostarts to manage your apps that start up with the phone or the various conditions an app starts under (I cant stress this enough - this app is my number one required app on my phone - it is disappointing that more people dont know about or use this app). Use the OS monitor to look at what is draining the battery (this is after all, the reason it is in Android).

You can find the reason if you dig around. Or, if you dont want to do that, there is the PC solution, format and start over. Luckily, you dont have to install 200+ updates and have a 4+ hour process with the phone if you start over again.

Just make a list of the 'must have' apps and back those up (this means using TB to manually delete backups of apps you dont plan on having on your newly formatted/installed phone).

The major key is, keep your phone tidy and it will hum like a new engine. Fill it with crap and you will get alot of stinky performance.
[Captivate Android Development] littlewierdo:
Ok, I have a simple question, call quality is awful on my phone (for the other person receiving my call).

I saw this was mentioned a few pages back, something regarding the modem that CM uses is for i9000 phones that isnt always compatible with the cappy (i897).

As a side note, why did samsung have to use the letter 'i' before the models...?? Ugg...

So, in order to get the call quality for the person receiving my calls do I need to use a different rom (Cognition for example)? Can I try flashing a different modem (something I have ZERO experience with)?

Basically, I just want to know if I am screwed if I use Cyanogen on my particular phone or if there is an alternative solution (such as using an alternative modem)...

I tried looking to see if there settings for noise cancellation and so forth and could not find anything to try and tweak (I am using the standard kernel and standard modem that comes with CM) regarding phone quality...
[Captivate Android Development] MechaGen:
I too am experiencing the same thing. I only get one or two calls a day, so I too thought it was just a bad connection or something.

Sent from Tapatalk, since XDA App doesn't work with NOOK Color!
[Captivate Android Development] shaolin95:
Anyone here using any of the SDCard Speed tweaks with success?
[Captivate Android Development] nkrick:
Aside from some button differences, orientation, etc, the biggest difference between the i897 and every other Galaxy S phone is that the i897 has an Audience A1026 noise cancellation chip in it (I have seen divided opinions about whether or not the i896 & i9010 have the audience chip or not, but my impression is that they do not). For comparison, the Nexus One and iPhone 4 also have the Audience noise cancellation chip. You can see a "typical application" diagram here: http://www.audience.com/processors/a1026.php

The audience chip is a hardware solution that works in conjunction with the modem to do noise cancellation. This means that the i897 modems (such as KB1) expect for the Audience chip to be present to offload the voice processing to, so they don't have the same code to do the audio processing in the baseband that a i9000 modem has. Typically, the i9000 modems work fine on the i897 because you are just moving the audio processing into the baseband since the i9000 modem contains the necessary code to do it. However, this does take more processing power because it is doing the processing in software rather than hardware.

If the person you are calling is hearing a lot of background noise, try flashing a different i9000 modem to see if it helps. Also, make sure you don't have any air blowing over the microphone (wind, fan, etc).

If you use KB1, it is typical for the person you are calling to have static because CM7 is currently missing the Audience drivers. Once the Gingerbread source code for the i897 drops, team hacksung will pick it apart and see if they can get the audience chip working. If that happens, then the KB1 modem should give very good call quality, at the expense of losing HSUPA.
[Captivate Android Development] alkoholic:
I get the same...It's probably been happening for the last three weeks or so. Not sure before that.

(Not hearing the caller on the first call, that is...forgot to quote)
[Captivate Android Development] nkrick:
No... Of what SDCard speed tweaks do you speak?
[Captivate Android Development] C3P0LOL:
On the latest nightly #92. When I reboot the phone, I have to pull the battery to get the phone to turn back on. Anyone else having this issue?
[Captivate Android Development] XsceneXhippieX:
AFAIK, cyanogenmod has included the tweaks you speak of since about a week after xda tweeted about it some odd months ago, therefore yes everybody is having luck with it technically :) at least on my last phone it was included and i believe cyanogen is quite good at keeping features across multiple hardware
[Captivate Android Development] Jusrertiner:
I do on 89

Samsung captivate

glitch kernel

cyanogenmod 7 #89

OC and UV
[Captivate Android Development] C3P0LOL:
I'm also using the glitch kernel. I'm going to go back to 88 and see how it goes.

edit - reboot works for me on 88
[Captivate Android Development] abee_13:
Same thing happened to me . Turns out it was my UV
[Captivate Android Development] RockRatt:
Are you undervolting? If so change the 100 and 200 MHz to no more than -100

This has been an issue when I have used any OC/UV kernels and would Undervolt the 100 and 200 down to -125 or more.

If you are not undervolting then I am not sure without knowing more of your setup. Are you overclocking? If so how much. Are you undervolting? If so what are all your settings. These are just things that come to mind that I have seen do this in the past. Also you never need to actually pull out the battery, just hold down the power button and the volume+/volume- until the phone rebooted. It may take a few seconds to do it so just keep holding it until it goes black screen. If you hold it until the att screen comes on then it will take you to the recovery screen. Then you can reboot from there.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] C3P0LOL:
Thanks, that's probably it. I had 100 -125 or something. I'm on 88 now with -100 at 100 and seems to be good. I only OC to 1300 and use -50 there.
[Captivate Android Development] hernan078:
Hi my android os problems are still draining my battery when I woke up this morning I lost almost 80% in battery in 7 hours thanks to android os using too much battery I flashed the glitch kernel and now my android os is taking 20% of my battery and android system is taking almost 18%, i lost almost 60% in about 4 hours of almost no usage please help me I have moved apps to the same card I don't know what more I can do, thanks in advance.
[Captivate Android Development] XsceneXhippieX:
so -100 all the way down 1300-100 with exceptions of 800, 200, and 100 being -125 for battery saving purposes might be a bad set-up? or should i just keep what im using if it is working with no issues on my personal device?
[Captivate Android Development] C3P0LOL:
If it's working with no issues, I would assume your set up is fine. :)
[Captivate Android Development] CougarBroker:
Judas Priest you all are a bunch of whinny cry babies, Install Spare Parts from the market and find out what is going on, Lightbox was accessing the camera on my cappy and it kept it "awake" by using the camera sensors in the AndroidOS, do just a little basic research and diagnostics before complaining.
[Captivate Android Development] nimper:
My battery graph is ****ed, I think.

It's definitely been off the charger longer than 5 hours. Looks like there's a segment that just got chopped off somehow.

Anyone else had this happen? Nightly 89. Although Nightly 91 addresses battery issues, I don't think I'll ever be able to replicate this and it hasn't happened before as far as I can recall.
[Captivate Android Development] nkrick:
The only time I have seen a sudden drop like that, followed by an increase of charge (while not on a charger) is after a reboot. But the drop has never been nearly that big.

I think Atinm described the reason for the sudden drop quite a while ago. Something related to the way that it shows 100% charge now instead of 96%, and after a reboot it, it loses the calculations to account for that 4% difference over time, or something like that. I am not sure why the battery power will increase for a time after rebooting, but it is all related I think.

It could be that the battery changes in nightly 91 change how this works. I haven't seen any official information from team hacksung what "improved battery calculations" means exactly.
[Captivate Android Development] abee_13:
Have you tried powering off and taking the battery out for a minute? That fixes that problem for me.
[Captivate Android Development] hernan078:
I did that but now the percentages are worst. I used os monitor but I'm not seeing anything being on, I don't know what more I can do to fix this problem

Edit. I'm now seeing the process of drm protected media something how can I prevent of this being open or how do I know if this is really consuming my battery?
[Captivate Android Development] z28james:
This works but is like cracking a peanut with a hammer.

When I would encounter this bug, it was due to some corrupt media file on my SD card and the Media Storage service would go wacky and not let the phone sleep. Clearing the data for that app would "fix" it although I eventually removed and re added all of my media. I've set to see it pop up again.

Also, my buddy with a vibrant had some similar issues. Turns out that the browser was constantly running and was not letting the phone sleep.
[Captivate Android Development] hernan078:
Can you please tell me how can I see. What processes are acting strange because I don't see any abnormal activity in os monitor
[Captivate Android Development] mod777:
This happened for me the first time yesterday after I flashed #91
[Captivate Android Development] cesierra:
I noticed that when I flash a nightly over a previous nightly, I end up with poor battery life. Odin is the way to go for me.
[Captivate Android Development] littlewierdo:
Thanks for the infos on the audience chip, I will play with a modem or two and see if I can improve my call quality - it isnt often a nice description like that is given that clearly explains how it all works.

A tip for battery problems:

I would recommend looking at any changes (new apps or updated apps) you may have installed. It is highly unlikely that an app would just out of the blue start draining the battery (this would include system apps).

It might be beneficial to remove the battery stats (do this from the recovery menu) and recalibrate the battery. It is possible that your battery may have lost a cell (if this is the case, expect a significantly reduced battery life - around 20% less) but recalibrating will at least force the phone & battery to report accurate percentages.

The way most Lion batteries work is, if one cell drops below 2 volts, that cell is permanently taken out of service and is NOT recoverable without tweaking the firmware in the actual battery - this CANNOT be resolved with the phone - it is the batteries firmware that would need to be tweaked (and even then, not in all cases). So what happens is, the phone battery management (sometimes referred to as power management) monitors the power in each cell and essentially reduces the drain on cells with less juice and increases the drain on higher juiced cells to compensate. This keeps the battery at a fairly even charge across all cells. This is also done as the phone charges - lower cells receive more power to charge them slightly faster than more filled cells which keeps all the cells fairly even in charge.

I am a bit concerned about the recent battery tweaks, hopefully the CM peeps know how to properly manage the battery - would hate to see batteries start dying permanently because something was missed or not understood by the CM peeps. Not meaning this as an insult mind you, just saying, it is easy to miss something like this and battery management is pretty tricky stuff.

But, I would start with a battery recalibration and see if that resolves the issue.

1. With the phone on, charge the battery to full.

2. Keep the phone plugged in and reboot into recovery and delete the battery stats.

3. Power off the phone and unplug. Boot the phone and let it stabilize (about 2-3 minutes AFTER the lock screen appears).

4. Power down the phone and plug in to the charger. Use the volume up and down screens to turn the screen on and check the current charge of the battery. When it is completely charged, it will show a 100% in white text inside of the green battery displayed on the screen when it is fully charged.

5. Once fully charged, disconnect the power and boot the phone. Let it stabilize (about 2-3 minutes AFTER the lock screen appears).

6. Power down the phone and recharge to full (using the volume keys to check the status of the battery - it will show 100% in white text inside the green battery displayed on the screen when it is fully charged).

7. Disconnect the phone and power up the phone.
[Captivate Android Development] makelegs:
Battery calibration always seems to draw controversy. Not sure that bump charging is universally accepted as wise battery maintenance....even though I've done it before. ;)
[Captivate Android Development] boog:
is it possible to smylink or hardlink emmc to /sdcard/external_sd ?? I haven't tried yet. But the theory in my head says it should work, other than the fat filesystem not liking symlinks.
[Captivate Android Development] tiuk:
That would be the reason why it won't work.
[Captivate Android Development] sixstringsg:
You could format your card as ext4.
[Captivate Android Development] boog:
The thought has crossed my mind!

How are the miui guys doing it? the external card is mounted in the external_sd folder.
[Captivate Android Development] rico_fiasco:
anyone know why android market isn't included in this rom??? Ive tried to install it via apk file. It'll install but it force closes every time it asks me to add an account to the the market so that i can download apps. any help will be appreciated. thanks!
[Captivate Android Development] gstern:
Check the op for gapps.
[Captivate Android Development] Kaik541:
because it's illegal to redistribute google's apps. so technically every ROM on xda that redistributes them is violating the EULA you agree when you use the android market (but meh)
[Captivate Android Development] hernan078:
Hi when I went to check my battery usage I saw that media part is using 31% and when I went to process manager I'm seeing that "my uploads" is continously running, now my android system has reduced almost to 19% and my android os to 12% I have removed some apps butbi haven't being able to go back to a normal usage of battery please help, thanks
[Captivate Android Development] TheTodFather:
Hey guys I work for At&t and have been reading in our internal docs that if you use tethering after August 11 you will lose your unlimited plan and be put on a tiered plan most likely the 45dollar tethering plan.

When tethering At&t will be able to see if your mac address is different. If tethering it will see the device your tethering to Mac address then they will cross check that to your phones mac and if not the same then well you know what happens next.

Is there a way to spoof the mac address while using the CM7's mobile hotspot feature?
[Captivate Android Development] EnemyOfGlaDOS:
Umm.. ok, but its past August 11th and I have yet to hear ANYTHING from att telling me that my unlimited data plan is now void. So... uh, what's the deal yo?
[Captivate Android Development] TheTodFather:
That's what i'm saying! I'm just the messenger.

My next question is why is it easier for At&t to catch iphone users over android.

The reason I've asked is that in my daily LSO classes we have been reading a lot on this subject. I'm just trying to understand the whole process of catching users. I would think iphone and android users are just as easy to catch, but statistically I've only seen iphone users get busted. Hmmm so if their was a way to spoof the mac of the tethered device then I see absolutely no problem.

Anyone want to chime in?
[Captivate Android Development] EnemyOfGlaDOS:
Yeah, I still don't get it. You said one thing than agreed with me that it didn't make sense.

..ok :p
[Captivate Android Development] mindbullet:
Thanks for the heads up, but I kinda find that hard to believe. The MAC address should change every hop. How are they saving the first MAC address?
[Captivate Android Development] TheTodFather:
IMEI is the phones serial number I know this is also used in the check as well. Thus i kinda used the first term "mac" with quotes.

Regardless if it's hard to believe this is how they catch you. Like i said previously, this method is what they have used for iphone users and it the docs I read were also implying the same method for android. So my real question, why go after iphone users and what would make going after android users more difficult.
[Captivate Android Development] Malorkus:
Somewhere between 85 and 89 my phone started randomly shutting down or freezing when it was in standby in my pocket. I'm running the stock kernel and never had this happen before but it's happened 3 or 4 times in the past few days. Anyone else notice this?
[Captivate Android Development] Spritely:
Apparently so far they are only catching and penalizing iPhone tetherers. http://www.engadget.com/2011/08/04/atandt-no-more-unlimited-data-for-illegal-tetherers/

It could be that something we do when rooting (and thus opening up the illegal tethering) affects how they can track it. I really have no idea how any of it works I just saw the comments here and thought I'd link a little more about it. It's been popping up a lot lately.

Oh and if you just use it a little here and there (like I only really have a use for it if I'm out with my Kindle and want a new book with no Wi-Fi available) they were never really saying anything about it, just the heavy users being the ones that sparked the backlash.
[Captivate Android Development] EnemyOfGlaDOS:
Interesting indeed. Must be targeted towards heavy users. I occasionally will use tethering for some COD if I need to ;).. buy I consider myself a light tetheror :p.

..thanks for the info.