yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] g1ddy:
bug

Works extremely well. Bugs:

1. See attached image. Browser menu seems to be incorrectly referencing the text for "Find on page". Display tethering text instead.

2. Wifi signal seems a bit weaker than usual.

3. Face unlock FC's. I know it's not a real issue since we don't have a FFC but you'd think the option would be hidden.

4. PICO TTS voice output example does not work

5. Cant change camera picture MP size or focus mode and restore defaults under camera settings

EDIT: fix attachment
[Captivate Android Development] nbell13:
I had that problem too. Installed the most recent update with titanium backup (had backed it up when i was running CM7)
[Captivate Android Development] MikeyMike01:
Yes.

Take an app like AndroIRC that has an ongoing notification. When you swipe it away the notification disappears because the app is closing.
[Captivate Android Development] MikeyMike01:
Is the Preferences menu from the home screen supposed to have an options? I just noticed it, and when I click it it brings up a blank menu that says Launcher at the top.
[Captivate Android Development] nbell13:
It probably will, eventually. Just not yet.
[Captivate Android Development] poolemit:
ok, sorry if this is a bit OT but maybe someone will have an idea. i've been using this modded skype for a long time: http://xdaforums.com/showthread.php?t=1148708

it's set to start automatically on every boot, which worked fine until ICS and now it won't start at boot. i'm know it's an issue with the app itself but nevertheless, does anyone have an idea of how to make this start at boot up and in the background? i installed the 'startup manager' app, which is able to launch it on startup, but in the foreground which is annoying...

ideas? thanks
[Captivate Android Development] pawitp:
It prevents users from flashing a Captivate build on a I9000 (or any other incompatible models) which would break things. We can't fix issues with other people's recovery or build.prop being broken, but in our recovery, you can use ADB to push or mount USB (as mass storage).

Stock didn't have it, someone started work on it which happens to be on the repo that we use to build. So yes, it's supposed to be empty at the moment.
[Captivate Android Development] Tarima:
Naaaa. Like I said check the ram usage after each kill and you'll see.
[Captivate Android Development] uzbeque:
My favorite programs are not working well with build 1. :( Seal (application locking program, is not working completely) and Go Sms pro...

thanks to devs, except abovementioned issues, rom is great.
[Captivate Android Development] skynet11:
Which is exactly what I did last night. + 1, MikeyMike01

Has anyone seen John Connor?
[Captivate Android Development] Tarima:
Go SMS works fine for me (aside from contact names not showing up). Just do a full wipe and flash build 3 and you should be good to go. Aldo don't forget that the Go devs probably haven't included ICS support yet.
[Captivate Android Development] 60hzrumble:
I have to say, this is by far the best my Cappy has run since I've had it. Great work!

Any chance of including the kernel support for the Dock Sound Redirector? Missing Pandora in the car, but the rest of the rom is so sweet it's not a deal breaker.
[Captivate Android Development] domo.kun:
The ROM works fine on my captivate, little bit laggy but fine for me. I'm looking for a way to overclock mi Captivate to 1.2ghz, i used to do it with tegraoverclock but does not work on this ROM.

Any idea?
[Captivate Android Development] gstern:
Use voltage control, stock kernel lets you oc up to 1.3
[Captivate Android Development] TheSoaresan:
Use voltage control, its in the market. It has a simple interface and is easy to use....however when the next build comes out, I don't think you'll need it anymore.

EDIT: looks like gstern beat me to it
[Captivate Android Development] mbonus:
Yes on build 14 for the Jawbone ERA; I flashed 16 and the riltest around the same time after a full wipe.

ICS has never worked with my car's bt. Pairs up, but get severe distortion when placing receiving calls.
[Captivate Android Development] nakedninja42:
Weird, I am running b16 w/ the riltest as well. I haven't tried syncing my BT earpiece or headphones but I know that it works in my car with no problems.
[Captivate Android Development] nkrick:
Agreed. The "link" to Google Voice here is that as soon as my test call went to voice mail (I hung up immediately leaving no message), my phone immediately "chimed" with Google Voice showing me that I had a missed call (I was connected to wifi, but my phone was in deep sleep, so wifi should have been sleeping). Without Google Voice installed, I would have received no notification that I missed a call because my phone never woke up or rang. The problem was in no way caused by Google Voice, Google Voice simply allowed me to see immediately that I had missed a call.

As I said in my previous message, I think this specific instance was a carrier issue because I also had not received an SMS that someone told me they had sent and I was unable to place any calls when I tried after missing my test call. Other than this one time, I have had no other missed calls since installing the testril.zip

---------- Post added at 10:48 AM ---------- Previous post was at 10:42 AM ----------

With winmobile, the reason to try different modems was also to find the best reception. But, in winmobile, if you flashed a different modem, you also wanted to replace the RIL file (I think it was a .dll) to a version that "matched" the new modem. I have read that in Android there is no reason to change the RIL files, but the fact that pawitp is able to fix a missed call issue by using RIL files from a different ROM build seems to contradict this.

So I was just wondering if there is any advantage to using the RIL files that come in the ROM that the modem being used is from. I can hunt down the ROM that my modem of choice came from and do my own testing, but I was trying to get an expert opinion first.
[Captivate Android Development] Ikonomi:
Just want to report that since flashing the new RIL files all calls have been received as normal. I'll update if this changes.

Thank you.
[Captivate Android Development] glwilliams4:
Anyone else having problems with Google push services working on build 16? Nothing is being pushed to me anymore, I have to refresh.
[Captivate Android Development] RichIrish:
I'm running build 16, test#2, KP1 on my Cappy.

After a Google + update earlier this evening my phone's showing me a "Low on space. Phone storage space is getting low." message. I tried rebooting and that didn't help.

Somebody please help me fix this.

Thanks in advance.

Update: Uninstalled Google + updates and the warning message vanished. Can somebody please explain why/how?
[Captivate Android Development] theyurtingyeti:
Lots of data is stored be g+ so that's why uninstalling it got rid of the message. The message comes up when your /Datadata directory gets too full.

Check that directory (disk usage is a good app for that: root folders) and see how full it is. if apps are the culprit the something like 1tap cleaner can organize the apps by data size for you to sort through.
[Captivate Android Development] rexthunder:
I just missed an IMPORTANT phone call that went straight to VM.. WTF?? Flashing the ril.zip NOW!!! Can't afford to loose calls like this..
[Captivate Android Development] SirBrettrick:
Probably safer to stay off alpha ROMs if you're expecting important calls.

Sent from my Captivate
[Captivate Android Development] rexthunder:
I didn't think I would have this problem up until now..Hopefully this ril file will fix it cuz i love this ROM.. Murphy's Law... Go figure!
[Captivate Android Development] SirBrettrick:
Yeah, I got you. Not trying to be rude, I was just saying maybe you should switch to something more stable until you can use your phone more for "play." But the RIL fix seems to be working for others, so good luck with that.

Sent from my Captivate
[Captivate Android Development] voldomart13:
Just noticed this... when I'm listening to music I looked at my battery consumption info and it shows music taking up battery but also mediaserver so both those together take up about 70-80% of my battery. Is this a bug? I ask because I'm not positive but in earlier android versions I don't think it had media server to drain more battery.
[Captivate Android Development] scrypt:
Anyone having aproblem running chrome? I can't get i tto work..gives me an "unable to parse" error

I am trying to run this version given here http://xdaforums.com/showthread.php?t=1485440

Also it's been so long since the last update :P just saying...
[Captivate Android Development] littlewierdo:
Unable to flash any version of CM (GB or ICS)

So, I was running ICS build 16 and while I was goofing with world of goo, the phone rebooted, showing the boot animation for several minutes and refusing to boot normally.

So I dropped the phone into download mode, flashed it to stock 2.1, Master Cleared (which basically formats the phone and does a factory reset), rooted, installed cwm (which was fun because rom manager is not on the marketplace anymore for 2.1 and below and on stock you cant sideload apps).

Upon picking the following versions of CM to install thru the recovery menu (latest GB stable, latest 'official' GB nightly 181, latest unofficial Kang dated a few days ago, and the latest ICS build 16), the phone simply boot loops (it says 'checking for BNL / Auto, the phone reboots, then a bunch of text scrolls on the screen too fast for me to read and reboots, spams a bunch of text, reboots, etc.). The version of clockwork is the last one made for Eclair / Froyo (somewhere in the mid 2's).

I have already done factory resets between each version I tried to install so I dont understand what is going on here. I assume that somewhere along the lines, CM lost compatibility with installing over older versions of Android? I mean, I cant see anything I am doing wrong - flash to stock 2.1, root, install CWM, reboot into recovery, wipe caches and factory reset, install rom. Its as clean as I can get it.

I should also mention, I tried all versions (using the same procedure) with stock Froyo as well with no luck, it does the exact same thing.

I am unable to get into recovery while it is boot looping so I am forced to put the phone into download mode and flash to stock again.

Oh, and I am using Rom Manager to install the latest recovery (although I did try the suggested method on the CM wiki that involves installing the speedmod kernel w/ recovery built in).

Any ideas what is going on here?
[Captivate Android Development] capefearless:
Maybe try going to stock GB instead of froyo? Also try changing bootloaders?
[Captivate Android Development] shane87:
Mine did the same thing coming from i9000 based gb. I pulled battery when it started bootlooping, replaced battery, then used vol up vol down power to get into recovery, reflashed ths ics, and it worked perfectly.
[Captivate Android Development] J0ESK0:
Same thing happening to me. Listening to music severely drains battery. At first I thought it was because I was using Pandora or Google Music. So I moved my music to my sd card hoping that would alleviate the problem.. but no dice. Using the stock music app with music on sd card still causes the drain of media server and music. :confused:
[Captivate Android Development] ptesmoke:
i can confirm this as well
[Captivate Android Development] nkrick:
hi battery drain by wifi when not connected to network

I noticed yesterday what may be a bug. After performing a factory reset I had forgotten to set the wifi sleep policy. This was causing slightly higher battery drain, but as long as my wifi was connected to a network (which it is 95% of the time) there was no noticeable high battery drain.

Yesterday around 4:30 in the afternoon I had about 85% battery left. I then spent about 2 hours away from work/home and more importantly, no where near any wifi access points. I also did not even touch my phone during that time. During that time, my battery drained down to around 40%. When I noticed the low battery much later, the "culprit" in the battery stats was "Android System." It was only by looking at the graph that I was able to see that the high drain was during the period of time that my wifi was not connected (and not using my phone at all). I then checked and noticed that my wifi sleep policy was set to never sleep (so I fixed it).

I don't think that having wifi enabled but not connected should drain so much battery. It seems like the phone spends the entire time actively searching for wifi networks causing excessive drain.
[Captivate Android Development] know50:
I know how you feel but I think that's exactly what happens. I just try to remember to switch wifi off when I leave the house or whenever im done with wifi. I don't think it's a bug though. I think when wifi is on without a wifi signal it's trying to find a router and that goes for all Android phones but I could be wrong
[Captivate Android Development] drwx:
install Y5 Battery Saver. It turns wifi on and off based on the cell towers that you are hitting. For example, if i hit 3 specific towers at my house, my wifi will turn on when I'm at my house. When I'm at work (i don't use wifi at work), I don't hit those towers, so my wifi is turned off.
[Captivate Android Development] RootTheMachine:
This isn't a ROM issue. Anyway, I use llama to automate this and much more

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] vileladelima:
Google apps

Didi'nt found in rom manager the option to install the google apps!

Where i found it?

Thanks!
[Captivate Android Development] capefearless:
Google apps are in the OP (called gapps).
[Captivate Android Development] morehush:
Or you can download the latest Clockwork flashable zip from here: http://goo-inside.me/gapps
[Captivate Android Development] Beny The Kid:
Its in ROM manager. Go into "download ROM", then its under the "free" list.
[Captivate Android Development] morehush:
Not I. And I haven't seen any other complaints of that in this thread.
[Captivate Android Development] ThreeofNine:
No problems here with push services either. Also no problems with faster battery drain when there's no wifi signal. I keep wifi always on.

Only problem with faster battery drain is when I can't get an AT&T signal which is normal with all/most(?) cell phones.

I'm getting 30-50 hours between charges depending on Twitter, Google+, & Facebook updates, phone calls, video and music/radio streaming, texting, etc on the stock build 16, test kernel #2, & stock radio. No 'sleep deaths' nor 'charge deaths' and bluetooth in my car works perfectly with the Ford Sync system. I came from CM7.1
[Captivate Android Development] nkrick:
I find it hard to believe that leaving wifi turned on when you are not connected should drain your battery by 40% in 2 hours. That means your phone would be dead in 5 hours if you leave wifi turned on but are not connected to a network.
[Captivate Android Development] Holmes108:
Definitely wouldn't be normal. I never turn wifi off, it never sleeps even, and get fine battery life.
[Captivate Android Development] littlewierdo:
Problem is, first off, Im using stock Eclair (i897 rom, not i9000). Second, I cant get into recovery when it is bootlooping (I tried several times).

CM is supposed to be compatible with Eclair/Froyo bootloaders and unless I hear differently, Im sticking with those. I dont really want to mess around with bootloaders if I dont have to.
[Captivate Android Development] thangphysk48:
Use GB stock with bootloader, then use any kernel has cwm (ex Talon) then flash THS ICS (or even cm7 nightly - even they require E/F bootloader, but I'm using GB bootloader w/o any problem at all).

So I recommend you use GB bootloader.
[Captivate Android Development] littlewierdo:
Again, why?

The GB bootloader is not the problem here, the only thing the GB bootloader does is change the buttons for getting into recovery.

I dont even know if this will correct the problem, CM is SUPPOSED to be compatible with Eclair/Froyo bootloaders which says to me, the bootloaders are not the problem.

Personally, I think it has something to do with incompatibility with earlier recoveries but I am not sure that is the problem.

Following the instructions on the CM forums, the CM wiki, and the original post of this thread and the thread for the GB version of CM, I have followed them all (they are pretty much identical). The only variance seems to be that you should flash to Eclair stock, insert the speedmod kernel via download mode (which gives you an early version of some sort of recovery menu), boot into recovery and 'install zip from sdcard' from the recovery menu. I get the same results if I sideload rom manager and flash the recovery menu from it.

This all stems from two problems.

The first is that while CM is installing, it doesnt pause to allow the user to see if everything went successfully or failed, it just reboots. Because of this, I have no way to tell you what exactly is going on because the log files arent staying around (when it bootloops, my only option is to flash back to stock which erases everything - besides, the user should be able to view everything that happened during an install / update, otherwise, what the hell is the point of giving the user ANY feedback?).

The second is a complete misunderstanding of what bootloaders are. CM has worked in the past (ICS and GB) on Eclair / Froyo bootloaders and now it isnt installing which means, something changed or I am forgetting something (which I might add, could be very possible). If you know for a fact that this is my problem, I can accept that but I am not going to just install them to test as a solution.

I am NOT going to just install new bootloaders because I know it will produce the same results. I have perma-bricked a cappy before because of this issue and just willie-nillie flashing new bootloaders because a version number is higher isnt a good enough reason to risk a perma-brick on a device that is now out of warranty, especially when these bootloaders do nothing more than create more problems than solve.

If it turns out the bootloaders are the issue, fine, I will stay on my currently rooted / debloated stock version of Froyo. Its running ok for me atm.

Oh, if I didnt mention, Cognition 4.5.3 installs just fine (I tried installing Cog and using the recovery from that to get CM installed and it just bootloops - same as from stock).

Something changed and the instructions are no longer accurate (there is something more that the user needs to do that is not listed) or CM is no longer compatible w/ installing from Eclair / Froyo.

I certainly hope I can figure out what is going on, I like CM. Its clean, has lots of fiddly-bits, and most importantly for me, stays current with Google and their security fixes. But if I cant run CM, I'll just stick with Froyo.
[Captivate Android Development] Joecascio2000:
In not sure what bootloop your talking about but if you flash CM9 from an unsupported recovery you get stuck in a bootloop. However all you have to do is pull out the battery, reboot in to recovery using the button combos. ( I believe you hold both volume buttons and hold power until you see the att screen. And then release power.) Once in recovery flash the CM9 zip again.

If that still doesn't work. As previously stated flash to GB bootloaders. Yes CM9 works with all bootloaders but everyone else seems to be having great results with the GB ones. Including myself. Plus it seems to be a booting up issue, hence "BOOTloaders".
[Captivate Android Development] thangphysk48:
You should know that when flash cm9, it'll flash it self recovery, so dont care about "decoy recovery".

When you got bootloop, you can easy turn off your phone by plug out battery, then go to recovery by combo button, right? Then you can make a full wipe then flash THS ICS again.

Anyway, I've just give you easy solution to install THS ICS (or any ICS rom). I'm not dev, so I cant explain to you why, what, how. If you didn't, pls dont assert.
[Captivate Android Development] kschumake83:
Littlewierdo,

Does the 3 button combo work with the boot loaders you are using? Cm always bootloops for me on initial flash all I ever do is battery pull then three button back into recovery. I do know that on certain phones if you flash the original eclair you loose the three button recovery. That's one thing I love about the gb bootloaders the recovery is always there unlike eclair where I had to flash the three button fix.
[Captivate Android Development] littlewierdo:
I can get into recovery on a NORMAL boot, when it is bootlooping during the install of CM, I cant. I currently have CWM 2.3.5 recovery installed and I can get into recovery just fine on a standard boot.
[Captivate Android Development] Joecascio2000:
Have you tried flashing CM9 over itself. Not sure what you mean by "NORMAL" boot. Either you can get into recovery or not. If you can flash it over. You should have to flash it twice in a row. Here is the process: flash stock, flash kernel with CWM, flash CM9, get into boot loop, pull battery, reboot into recovery, wipe then flash CM9 again.
[Captivate Android Development] thangphysk48:
Do you know how to use combo button to goto recovery?
[Captivate Android Development] littlewierdo:
I have after 3 days gotten this figured out, dont ask me how I did it, I couldnt tell you exactly.

What was happening:

From recovery, choosing install from .zip and picking the zip file, the phone would show 'BNL / Auto check' reboot, then bootloop. Happened with Eclair and Froyo stock and from Cognition (with stock froyo, I tried various tricks to get the recovery installed because the 3e stock boot menu doesnt allow any zips to be installed unless they are signed - this prevented the use of Rom Manager on Froyo to install CWM).

NOTE: While the phone was bootlooping, I was unable to access the recovery menu, pressing vol Up + Vol Down w/ power (releasing power once the screen came on).

What I suspect:

Bad SD Card. Oddly enough, my external sd card is now blank, this was where I was placing the cm install file.

Frustrating as hell, Im going to run memtest on the card when I have a few days to create a boot image to run it.

So basically, when I copied the file to the sd card, the file would disappear when the phone rebooted which would obviously create problems.

As a side note, Im still on original Eclair / Froyo bootloaders and everything is working fine now.
[Captivate Android Development] ptesmoke:
your supposed to flash from internal storage...not emmc.
[Captivate Android Development] littlewierdo:
Unfortunately, this isnt stated anywhere in the documentation :(.

But I still am not sure if the memory card is bad because my sdcard that once had data on it, no longer does. Its blank.

Actually, I just thought about it, it isnt the sd card.

I did actually put the rom into the root of the main memory of the phone and it still bootlooped so now I dont know...
[Captivate Android Development] grasshands:
I seem to have the same status 7 problem coming from ICSSGS RC4...I looked at my build.prop in system and it says SGH not i9000...any ideas as to why this would fail?

Thanks

J
[Captivate Android Development] dutch55:
It IS stated in the instructions:

"Install the ROM from internal sdcard using ClockworkMod Recovery"

Your memory card is probably fine. Certain wipe methods (I have forgotten the specifics) will erase an external SD card. It is safer to remove the external SD card and the SIM before flashing a ROM, which would also avoid any confusion over which SD card you should use.