yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Tuftylb:
Thanks for the links, I've seen them before hand. I was curious because the Droid X seems to be the only Android device that has it and I didn't think they did it just for Ford. I own an HP TouchPad (Costs must less than a whole car) which is capable of Sending/Receiving SMS from my phone through bluetooth as long as my phone supports that feature (MAP). I tried it with an old school Black Berry and an iPhone 4 with no issues. I wonder if some Ice Cream Sandwich could remedy this..
[Captivate Android Development] airtower:
there's a 154 build, but the changelog only shows changes pending in 7.1.0.1, nothing about 154

I spot checked a few of the long list of changes for 7.1.0.1 and haven't found any in 154. Didn't check anything related to service mode.
[Captivate Android Development] ou812bkewl:
Thanks for the explanation. I'll keep that in mind in the future. Guess I'm stuck on 850mhz until that change merges. 850 works better than 1900 down here though.
[Captivate Android Development] pandakh:
I need some help, i used to have cyanogen a while ago and i remember i could change the notification bar options...can someone guide me back there?
[Captivate Android Development] sixstringsg:
Cm settings > interface > status bar tweaks > profit
[Captivate Android Development] comdei:
Anyone have the link to CM7 modems?
[Captivate Android Development] nkrick:
There is no difference in speed between 1900 Mhz and 850 Mhz. What I mean by that is one is not inherently faster than the other. Both are HSPA (or HSPA+, but your Captivate can't take advantage of that). Some people find that 850 Mhz is faster for them because it is less congested, meaning there are fewer devices in their area using 850 Mhz. I don't know exactly how it all works, but it seems that some 3G devices "prefer" 1900 Mhz and won't check 850 Mhz to see if there is less congestion. By having service mode available you can manually toggle between 1900 & 850 to see if it makes a difference for you.
[Captivate Android Development] nimper:
http://goo-inside.me/captivate/radios

http://goo-inside.me/galaxys/radios <-- these will work too
[Captivate Android Development] shaolin95:
Have you seen a link for KG3? I cannot find it and some people were raving about it....I swear I had it somewhere :D
[Captivate Android Development] RichMD:
http://xdaforums.com/showpost.php?p=16528695&postcount=105
[Captivate Android Development] pandakh:
im having some issues that i hope someone can help me with

first: i flashed cyanogen recently again after coming from some other rom, and my battery life is draining incredibly, its like draining a number per minute. how can i fix this?

second: when i send sms, the inbox appears as if there is an error, but normally the person receives my message, and sometimes it sends like 5 duplicates to my recipient,and sometimes it doesnt send anything....any help?
[Captivate Android Development] CptTwinkie:
Did you flash to stock before cm or just flash cm over the other rom?

If you did flash stock then clear caches.

If you didn't flash to stock first then I would consider doing so.

Sent from my Captivate w/ CyanogenMOD 7.1
[Captivate Android Development] dohboy15:
i have a bug that I've never had before. It happens every time i open a contacts page (The app it self opens up, only when i select a contact) or when i click on a contacts pictures in, say, the messaging app, or phone app, the process "android.process.acore" stops unexpectedly and goes back to the home screen.. any fix for this?
[Captivate Android Development] pandakh:
I flashed over another rom, and now i know i forgot to clear cache and system, ill reflash and see if that fixes my issue, thanks.
[Captivate Android Development] Kaik541:
sounds like someone installed the leaked ICS google+ 2.0 build. get rid of it and the error goes away.
[Captivate Android Development] Gromlakh:
There's no need to wipe caches or system, or to flash stock before coming from another ROM. The CM7 zip will completely delete and reformat everything on your phone except your SD card during installation. Flashing to stock just means another step in the process with no benefit to you.

It is possible, though, that you got a bad flash. Try flashing again, but this time do wipe cache & dalvik. The installer is no wipe if you're already on CM.
[Captivate Android Development] dohboy15:
Holy crap it worked! Its not all that different from the current one so I'll wait. Thank you good sir!
[Captivate Android Development] matmanchu5:
do you know which odin does the "Master clear" I just want to make sure its not one of the ones that includes the BLs so I can be extra sure to hit only the master clear and then use another one-click to return to stock, also does master clear also format the internal sd on the captivate??
[Captivate Android Development] ou812bkewl:
For those of your who are on nightly 154 and want service mode back, just open the nightly 152 zip and extract SamsungServiceMode.apk from system/app inside the zip. Then mount your file system as writable and copy it to system/app. I used es file explorer. It should now work just as it did before without reboot.

Edit: Don't forget to mount your file system as "read only" after your done. :-)
[Captivate Android Development] Gromlakh:
Master clear isn't done by Odin. It's an option from CWM. Wipes all your user data and formats the internal SD card. So, master clear from CWM, then flash back to stock for resale.

Of course, if you're going to sell, you may not necessarily want to flash to stock. You might have more success selling the phone if you give the buyer a choice of what OS is on the phone...
[Captivate Android Development] sixstringsg:
Master Clear is an Odin thing. In CWM you could do wipe data/factory reset, then go to format /sdcard, but it is not called Master Clear in CWM.
[Captivate Android Development] skatcat31:
Well this us sort of true. Many phones are international handsets that use 1900 for overseas capability. However 1900mhz waves are tiny, and lead to massive packet loss, resulting in lower speeds whereas the 850 band has a tiny amount of packet loses in comparison. Like next to none. Our so it's being explained to me by my professor... He started doing math and diagrams and I kind of tuned him out when he started doing calculus...

Sent from something from somewhere
[Captivate Android Development] XsceneXhippieX:
That makes perfect sense, and he was probably showing you the proof integral which isnt that complicated, but yeah that sounds about right to me and i appreciate you asking a professor :)
[Captivate Android Development] littlewierdo:
Sorry guys, I just completely disagree with the notion that flashing to stock does nothing and is just an 'extra step'.

When my phone had garbly and quiet sound for the person receiving my call, I originally had the stock cwm kernel and modem. Clearing the caches and doing a factory reset did NOTHING to fix the problem and simply reflashing the rom BOTH did NOT work (oh, and I did do a permissions fix as well). Only after trying the above did I try different kernels and modem combinations (both did absolutely nothing to fix the issue).

I finally resorted to a stock flash and then back to CM and everything was resolved.

---------- Post added at 01:46 PM ---------- Previous post was at 01:29 PM ----------

Having been looking thru my phone, I have been uninstalling apps I do not use in order to keep my phone in good working order (Im at 30 apps installed which I am quite happy with).

However, I came across two apps that have me puzzled as to why they are included with CM in the first place, especially seeing as they are available on the marketplace.

Starting with Google Books, my understanding is, this app provides the ability to purchase and read books from Google. Great, except, why is this included with the rom? Shouldnt this be an optional app installed via the market or via the Pacman script from Gapps? For me personally, it is completely unnecessary to have installed as I use Amazon with a Kindle for purchasing books. If there ever was an 'optional' app, this is for sure one that does not need to be there for most users (oh, and the one included with CM is out of date as well).

Secondly, Google Music. As it turns out, I have two versions of this installed, the version included with CM (version 2.3.4 I think) and the newer version from the market, 3.0.1 which adds support for Googles' cloud music storage service. Taking a minimalistic attitude, one could ask why it is included if the app is included on the market (in other words, make this app an optional install via the Pacman script via Gapps). I have always been of the opinion that if it is on the Market, why include it in the stock rom? But, ok, maybe I can see why it is included, but what I cant see is why Google music is not/has not been updated to version 3.0.1 and why it is not linked to the market.

Yes, I 'could' simply uninstall these apps via TB every time I flash or I could possibly write some sort of script to clean the apps off the phone but I think you can see the point I am making here.
[Captivate Android Development] nimper:
Google Books, Music, etc., are included in the gapps package, which is a separate install. Gapps are specifically not part of CM.
[Captivate Android Development] WillyWonka23:
After installing the newest nightly my power button won't work. Any ideas? I can't turn on the screen and it won't work in recovery either.
[Captivate Android Development] Aus_Azn:
This didn't work for me at all... Nightly 155. Tried after reboot too, still no dice.
[Captivate Android Development] ou812bkewl:
Did you use es file explorer? It worked like a charm for me.
[Captivate Android Development] Aus_Azn:
Used CM's native file browser and Root Explorer...I really don't think it would make a difference if even Root Explorer didn't get it done.
[Captivate Android Development] Gromlakh:
Epic FAIL on my part. I could have sworn there was a Master Clear option under Advanced in CWM.

Der.
[Captivate Android Development] sixstringsg:
I do like that idea though... Maybe I'll add it to the Glitch recovery.
[Captivate Android Development] Gromlakh:
I don't think anyone will disagree that there are some circumstances in which flashing back to stock can be beneficial. Those instances, however, are rare. The situation you just described is one where you may just need to flash back to stock, because you've tried everything else and it's just not working.

The problem is that people keep recommending "flash to stock" as the first option for almost everything, which it should never be, and add in a ton of other completely unnecessary steps as well. Half the time people ask about flashing a new ROM, someone pipes up and tells them to:

1. Wipe cache, dalvik, and data

2. Odin 1-click (including bootloaders) back to JF6

3. Rewipe cache, dalvik, and data

4. Root JF6

5. Flash something gingerbread, including going back to the GB bootloaders you were already using before step 1.

6. Rewipe cache, dalvik, and data

7. Root gingerbread

8. Rewipe cache, dalvik, and data

9. Flash kernel w/CWM

10. Rewipe

11. Flash the ROM zip file in CWM.

Whereas the proper instructions for switching to a new ROM 90% of the time should be:

1. Flash the ROM zip file in CWM.

All "full wipe" ROMs delete everything in /system, /dbdata, /data, and /cache as a part of the install. So, there's no need to wipe manually, although I don't see how that would hurt. Everything else is a waste. If there's a problem, assume a bad flash and just reflash. If it still doesn't work, do the manual wipes and try again. If all else fails and you just have no idea how to fix it doing anything else, then and only then should you try the "flash to stock" method.

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

Do that, then tell me when you've done it. Then I'm going to come back, delete my posts, and pretend like I was right all along! :D
[Captivate Android Development] mark72501:
Glad to see this. Of course if someone isn't on GB bootloaders, as I'm not, there would be a little more involved in flashing a GB ROM. But your point is well made and this is the process I usually use...your second set of steps. Well, step. Just flash the new ROM! :D

EDIT: What is the best way to go about getting GB bootloaders when running CM7.1? I saw this post but it says for CM users to stay away!
[Captivate Android Development] pparavas:
Battery life a little concern

I am currently running cm7 on JL3, although the battery life is better than JK4 by a billion times with the same performance, i still am not getting an optimal battery life. Is it because of the experimental rom(It delivers the performance of a stable rom) or is it the feature of gingerbread to drain battery faster?
[Captivate Android Development] whitesox311:
Is there issues with not shutting down cyanogen mod properly? It odd that all of a sudden everything video related went caputz
[Captivate Android Development] techmik67:
There is still memory draining from somewhere that hasnt been nailed down yet. I can say that if you toggle wifi off when not using it you will find a dramatic increase in performance, tho still not perfect....
[Captivate Android Development] whitesox311:
Take it off wifi
[Captivate Android Development] pparavas:
But don't you think the 3G is gonna take more power than wi-fi if i keep auto sync on of all my accounts?
[Captivate Android Development] grkmaster:
I got to say that this ROM is if not the most smoothest rom i have run to date. But the few things that dont work correctly bug me. One is the car dock doesnt work with it and it also doesnt charge on the car (oem dock with wire). And the glitches here and there.

I cant wait for a more polished update as this is a very usable rom. Now to decide which rom to DOWNGRADE to :( .. i think i was spoiled with 2.3.3 lol
[Captivate Android Development] whitesox311:
I've narrowed my problem down to the SD card scanner...it pops up and then goes away right away when I power on my phone but ie still continually scanning in the background for some reason and causing everything to be choppy
[Captivate Android Development] cruiserbax:
Anyone ever have the error "assert failed: write_raw_image("/tmp/modem.bin"." it fails every time at flashing radio with the initial package. I followed all the steps exactly and even watched the video a few times. I also tried flashing one of the CM radio zips by it's self and it fails exactly the same. I wiped everything and started over with freshly downloaded packages again in case of corruption but it fails at the same spot. I did some searching and found that error at the boot.bin but not the modem. anyone have any experience with this?
[Captivate Android Development] techmik67:
normally, yes, but in this case, we KNOW that 1 of the unusual memory leaks is related to wifi, so it is using an abnormally high amount of juice =)
[Captivate Android Development] majinzen:
Try re-installing the update package. That's what I do if it starts to act really weird and it fixes the problem without wiping anything.
[Captivate Android Development] shaolin95:
What a bummer...I was liking until I tried FPSE which I use a lot and it just crashes...oh well...back to waiting until its fully stable I guess :(
[Captivate Android Development] whitesox311:
Yeah I'm about to do that for sure thanks

Now my service stopped working too...wwwwwtttttfffffff

This has definitely got some loose ends
[Captivate Android Development] whitesox311:
Probably more to do with 2.3.x than cyanogenmod.
[Captivate Android Development] Kaik541:
update to android 2.3.3:

*drain battery faster to confuse users

*have them buy bigger batteries

*profit

never heard of this happening, logcats are more useful than complaints

samsung dock hooks into touchwiz framework (this is akin to complaining that it doesn't work with the Kies computer software), but charging function *should* still work.

you don't need to flash the modem separately, one is already included. are you sure you're running the captivate build and not the i9000 or vibrant (or trying to flash an i9000 or vibrant modem?)

seems to be a problem on your end as most of us have been running this for 1 week+ and have had none of these issues.
[Captivate Android Development] h0ckey10:
Here's a list of bugs I've come across:

-Home/search button don't work

-many force closes

-cannot have phone off while charging( it powered itself back on)

-some connectivity issues

-after rebooting all I had in the extended power menu was reboot and power off

Overall a pretty good rom and very smooth and customizable. I know its still a test and there will be issues, I'm just telling what I found to have problems with. Also an odd thing that happened to me was that almost none of the above bugs were present when I first flashed it. Only after a reboot...
[Captivate Android Development] cruiserbax:
Sorry let me explain better, I only tried flashing one of the CM captivate modems by it's self because I was curious to see if it would fail with the same error that the initial package did when it gets to the flash radio stage. I am sure that I am using the CM7 captivate packages yes. I re-downloaded them earlier in case they were corrupt but same error. each time I start over fresh following the steps exactly. I watched the video also.
[Captivate Android Development] lpfansether:
http://code.google.com/p/cyanogenmo...=ID Type Status Priority Device Owner Summary
[Captivate Android Development] MikeyMike01:
1. They work just fine

2. I've had but one or two

3. Also incorrect

4. I've had none

5. That's how it's supposed to be

Captivate, XDA Premium, Cyanogenmod
[Captivate Android Development] Kaik541:
home and search button work fine, seems to be a problem with your phone. I have only seen force closes on "WordFeud" so unless you provide a logcat, we're just gonna ignore it. Read the FAQ in the OP and you will see the charging-while-off issue is known and being worked on. "Connectivity issues" means nothing without elaboration. CyanogenMod does *NOT* have an extended power menu, the only thing I see when I long press the power button is "silent mode", "airplane mode", "choose profile" (coming in future updates), "reboot" and "power off"... that is all there has ever been, that is all you will ever see.

very strange, perhaps the changeover from captivate to sgh-i897 naming convention has broken this? if so, the zips will be updated
[Captivate Android Development] chipsa964:
Odd, I seem to have lost video on youtube also....
[Captivate Android Development] keller.jeff:
Can any one confirm one way or another of Wii mote connection working?

Sent from my SGH-I897
[Captivate Android Development] RichMD:
That is the exact method I use to flash KF1 bootloaders months ago. You can run any the Captivate ROMs on them. CM7 stated a while back to not use GB bootloaders (not supported) but the OP doesn't say that anymore (at least the last release). I have switched back and forth between CM7, MIUI, and SamSung ROMs quite a few times without ever changing the BLs. I've given up on trying anything other than CM7 at this point though. It's just the best in my opinion and only gets better. :D
[Captivate Android Development] ou812bkewl:
Ok. This works with ES File Explorer with its root option enabled. That's how I did it. Try again with ES File Explorer. It's free in the market. Once downloaded, go to its settings menu and check "root explorer" and "mount system writable". I'm on nightly 155 and have service mode working fine. You can uninstall the file explorer when you are done. It works.
[Captivate Android Development] Gromlakh:
At the time Cezar posted that thread, CM could only be booted from the Froyo bootloaders. So, he warned CM users to stay away. That's not a problem anymore, so flash away.
[Captivate Android Development] Gromlakh:
If you can get to the splash screen, you should be able to get to either recovery or download mode. I'd suggest trying to restore a nandroid if you have one, or reflash the CM zip file if you have it, and try to reboot. It's no wipe if you're already on CM. Worst case scenario, use Heimdall to flash back to stock, then start over.
[Captivate Android Development] Gromlakh:
Apparently I was too slow... ;)
[Captivate Android Development] mark72501:
Well I thought so but not really...PM'd you...
[Captivate Android Development] gilpdawg:
If I have problems and I want to flash to stock, I just flash to a stock GB without bootloaders. No reason to EVER flash bootloaders if you are already on GB loaders.
[Captivate Android Development] anishz:
can anyone confirm if service mode is back in 155. Are there any more steps remaining to be completed, i ask as there is nothing regarding it in change log.
[Captivate Android Development] cursedwave:
This worked for me! Though I used Root Explorer & had to actually restore ServiceMode through Titanium Backup, possibly because I had done a data wipe before moving to #154.

Sent from Russia, with love.
[Captivate Android Development] WillyWonka23:
How do I go about fixing my sd card issue? It says it isn't mounted with everything that uses it for storage. I can't access it in root explorer either.
[Captivate Android Development] anishz:
i tried the apk from152 for samsung service mode but it is not working using *#*#0011#*#*. Am i doing anything wrong?

Edit: Ok got it, the owner read and write options in permissions for the app were unchecked, checked it and its working fine.
[Captivate Android Development] ballz0iron:
i was able to connect a wiimote with bluetooth but i had to use another app that converted that input to keyboard commands and then once i had those keyboard commands i set them as the inputs in my emulator and it worked wonderfully. cant remember the name of the app for the life of me though....
[Captivate Android Development] littlewierdo:
Then why are both system apps?

And, drilling into the actual rom, they are included under system/app in the cm.zip file.

---------- Post added at 12:40 PM ---------- Previous post was at 12:34 PM ----------

Flashing to stock and reflashing to cm takes only 10 minutes or so and is a foolproof way of guaranteeing a clean install.

So, I can either play around with the phone trying clearing all the caches, reflashing cm, jumping up and down, blah blah, OR, I can quickly flash to stock (takes about 3 minutes to do so), 'inject' CM using AIO and in 3 additional minutes have CM installed (total of 6 at this point), setup the Market and install TB and finally restore my app backups. All told, I can do this in less than 10 minutes and have a nearly guaranteed working phone again.

Now, if you are flashing to stock, manually having to root, set the market up, installing rom manager to get clockwork, this is a bit more troublesome. AIO allows you to avoid manually doing any of this while on the stock rom, you click install custom rom, point it to the zip, then reboots the phone into recovery for you (well, you do have to select reinstall packages twice in the stock recovery menu to get cwm recovery menu but thats much quicker than having to root, set market up, install RM...).

AIO makes it pretty painless...