yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] littlewierdo:
CM is pretty stable right now, Im running the latest nightly from 7/16.

No offense to the CM folks but the one criticism I have is that what they consider to be an 'RC' release or a 'stable' release is a joke.

They have no HARD standards on what they call these different milestone releases, it seems to be just when it 'feels right'.

If you look at other open source projects, there are hard guidelines on when something is considered an alpha, beta, RC#, and stable release.

So, that having been said, if you arent doing really strange things with your phone, CM is just fine right now.

Most of what I do is 'light' gaming (maybe an hour a week), phone calls, email, & streaming via bluetooth my podcasts/audiobooks (BeyondPod/Audible).

The only 'major' issue CM has (and I cant exactly blame CM for this) is the gps is awful, but again, this could be the phone hardware. To be honest, I have no idea whether the CM team has even worked on the gps and at this point, it might be a waste of their time to do so.

I myself dont do anything wacky with my phone, just basic stuff and I rarely have any issues with it so if you are concerned about it being stable, I would say its stable enough for me.
[Captivate Android Development] RTBee:
Does the TKGlitch kernel only work with CM7 and MIUI roms?, or is it not rom specific?

edit: please disregard this stupid question. totally overlooked the kernel thread.
[Captivate Android Development] tjsooley:
What is the holdup all other SGS versions have a new nightly today but us?
[Captivate Android Development] phlunkie:
According to atin m (from g+) the build bots are broken.
[Captivate Android Development] tjsooley:
Damn, anyone build from source?
[Captivate Android Development] tarheelblueboy87:
Ummmm, gps has been amazing since RC1, when they gave it a "swift kick in the rear end", if u even read that changelog. Who are you to judge the stability of the builds, and the overall project? You obviously don't read or keep up with the nightly chagelog, and you have little knowledge about how much goes into this project.

I mean, CM just reached a half million new installs!! Your criticism is offensive to CM because you have no clue what you are talking about, and nothing you said helps anybody, its merely insulting the development community's hard work.

Btw, using the GB bootloaders only works fine if you don't want access to the external SD folder. You have to access extra storage through the root, which is kinda a downer.

Sent from my SGH-I897 on CM7 clocked to 1.44GHz

Glitch v11 ML
[Captivate Android Development] tarheelblueboy87:
#62 is working great, especially with the 2g/3g toggle fix for GSM phones. However, toggling it from the notification power widget is giving me problems. I can't consistently toggle it from there, and it doesn't reflect changes when I go into the mobile networks setting and toggle it there. Being able to use just 2g now is great tho, even if the power widget toggle doesn't work right.

EDIT:::::: Same problem that the new code was supposed to fix just happened to me on restart. I'm on GSM, and now after restarting, it thinks I'm on CDMA. Guess I have to reflash the nightly to fix it. The new code says it fixes the problem where a data call while on 2g causes the GSM phone to think it's CDMA. No problems until I restarted the phone, then it thought I was CDMA, so the problem might run deeper than previously thought.

Edit, Edit: reflashing did not fix, I better wipe my phone settings data!

Edit, edit, edit: That's why you always do a nandroid backup! Restoring one now because I don't know how to fix this once it thinks I'm CDMA
[Captivate Android Development] cbasse:
Anyone else have an issue when trying to set a picture as lockscreen wallpaper? The dimensions of the picture you can use don't seem to be right... Am I missing a setting somewhere?
[Captivate Android Development] tarheelblueboy87:
Are you sure they are incorrect? You can only crop the lockscreen picture to fit the width of a single screen. The lockscreen background is not wide like your desktop where you can scroll, and therefore see a larger wallpaper.

Sent from my SGH-I897 on CM7 doin' 1.44GHz

Glitch v11 ML
[Captivate Android Development] cbasse:
Problem is when I choose a picture then choose the portion of the picture to use as wallpaper, the shape of the picture is a square not a rectangle (i.e. the shape of the screen). I've used other ROMs where the picture chooser is rectangular to match the screen dimensions.

Example: I have a picture of my two daughters - I should be able to fit the picture in the lockscreen so I can see them both, but the dimensions of the picture chooser (in the shape of a square) won't allow me to fit both of their faces in. If the chooser was in the shape of a rectangle (again, same as the screen), the picture would fit fine.

Clearly not the end of the world, but I mentioned it only because I have seen it done differently with other roms and I've used this exact photo on my lockscreen before. Hopefully this can be fixed/adjusted in a future nightly...
[Captivate Android Development] Haloruler64:
i897 GB bootloaders will work with CM7. But you can only go one way. From Cog to CM7, but not back. Gotta flash to stock and repartition.
[Captivate Android Development] Haloruler64:
Not at all true. Yes, i9000 GB bootloaders don't work with external SD (and probably many more issues). But i897 GB bootloaders work flawlessly with CM7. Me and a lot of others run our phones with GB bootloaders.

They aren't supported by the CM team, but they work.
[Captivate Android Development] tarheelblueboy87:
External SD folder does not work on i897 bootloaders, I'm running them. You have to access the extra storage through the emmc folder, meaning if you want to access it from recovery you can't. I just deal with it.
[Captivate Android Development] sixstringsg:
That's how CM7 is, not how your bootloaders are. I'm on eclair/froyo bootleaders and it's the same.
[Captivate Android Development] RTBee:
Mine's rectangular on build #57. Also did you try resizing the crop? If you tap on the square (or rectangular) crop box arrows should show up allowing you to resize.
[Captivate Android Development] RTBee:
Is there any advantages/disadvantages to using the I897 GB bootloaders with CM7 as opposed to leaving it as is?
[Captivate Android Development] RockRatt:
Even with the eclair/froyo bootloaders you cannot access external SD card. CM7 changed it so we CAN access the external SD card but it is NOW called emmc. You can access emmc via cwm, root explorer with no issues. You can set up almost ALL APPS like tibia to use the emmc, you can put things onto your external SD card even if you transferred it from a PC onto the card, then put the card back in the phone, then access the music, photos, videos, etc. That are stored on it with the apps. So YES it works like this NORMALLY with either the eclair/froyo bootloaders OR the i897 gingerbread bootloaders. WHEN YOU HAVE the i9000 gingerbread bootloaders you will NOT be able to access the emmc card also known as the external SD card.

The reason that was given I believe by Atmin as to why they do not support the new i897 gingerbread bootloaders is that since all CM7 devices basically work the same but NOT all the devices HAVE the new bootloaders yet. I believe the fascinate or one of the other i897 type named phones do not have the new bootloaders yet. Once they do then CM7 may support the new bootloaders officially. Only time will tell. BUT the i897 gingerbread bootloaders DO WORK JUST AS the eclair/froyo bootloaders do, no difference as far as I have seen at all.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] tarheelblueboy87:
Ahhh, I see, good to know! Thanks sixstringsg, and RockRatt! i897 bootloaders work perfectly here in that case!
[Captivate Android Development] cbasse:
Unless I missed it before, the lockscreen wallpaper option wasn't available until release #62. And I have tried cropping/resizing, but it still does it in a square, so I can't get it crop the way I want it.

Just to make my point, here's the original picture, followed by what I would like to use, followed by what the image chooser allows me to use..
[Captivate Android Development] RTBee:
Sorry, I was using homescreen wallpaper not lockscreen wallpaper, tho I'm not sure how to access the lockscreen wallpaper. I guess I thot whatever you changed in one applied to everything. I'm dl'g #62 now, if I come up with anything I'll let you know.
[Captivate Android Development] RockRatt:
Just tried it out and see what you mean. Maybe since this is the first release of it they will fix it in future nightlies. Mine does the same. I know what you mean though about the rectangular style though as I have used it on my other gingerbread captivate. So looks like for now this is how it is.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] cbasse:
Thanks. Didn't mean to come across as defensive, just trying to make my point more clear.
[Captivate Android Development] cbasse:
Glad its not just me! And I agree, they'll likely fine-tune this feature in a future build. For now I can live with it!
[Captivate Android Development] Haloruler64:
Well they're compatible with CM7, Samsung 2.3, and Samsung 2.2/2.1 ROMs. It's compatibility I guess.

Exactly
[Captivate Android Development] Johnston212:
Just curious, but has anyone been having issues with Market on #60? I originally thought it was just Glitch V11, but I have just reflashed 60 and Market still FCs constantly and ROM Manager doesn't even show CM7 in the downloads list, just Design Gears. Manually downloading 62 now, but wanted to ask.

Also, how is the GPS doing? It was actually great for once in the 30s, but the 40s went back to mostly useless. Haven't had a chance to retry, so I thought I would ask.
[Captivate Android Development] phlunkie:
Soft reboots

Anyone getting soft reboots? Using nightly62. Fresh install and over nighty 59.:confused:
[Captivate Android Development] Johnston212:
Ok, just wanted to throw out an update here. I am running 62 stock and Market continues to be non responsive. I have cleared the Market cache/data and it now FCs when I try to instal/update something, instead of just trying to do anything. I am running the newest build of the marketplace, so I don't know if that means anything.

Just in case anybody thinks about asking, yes I have flashed gapps. I do that every time I flash a Nightly.
[Captivate Android Development] jangeles323:
I'm running the new nightly and market seemed to working fine. I updated the market and it seems to work with no FC's. But when i flashed the new nightly, launcher pro seemed to be giving me problems. But now its working properly..
[Captivate Android Development] skeepon:
i flashed 62 a few minutes ago and now my phone is really sluggish. running stock kernel. i even rebooted a few times. >.<
[Captivate Android Development] melbourne408:
have you tried uninstalling the market and reinstalling the updated .apk

Sent From My Swaggin 1.5 Son Of A Glitch
[Captivate Android Development] zmore:
I was also getting FC's with the updated market app (logcat was complaining about 'java.lang.SecurityException: Invalid value for is_public_api: null') when installing/updating apps, so I reverted and everything's fine.

EDIT: The updated market is now working for me on #62. Weird. Only thing I did differently vs the previous fail (besides the nightly #bump), was to convert it to a system app in tibu after adb installing it.
[Captivate Android Development] Johnston212:
You mean uninstall the market updates and then install the new apk?
[Captivate Android Development] melbourne408:
Uninstalling market then installing the posted com.vending.android-new.apk a couple days ago.

Sent From My Swaggin 1.5 Son Of A Glitch
[Captivate Android Development] cowman4000:
Running #62 and I am getting soft reboots. Anyone else having this issue? I was on #49 before and I got one every once in a while but I installed #62 this morning and it rebooted already.
[Captivate Android Development] Johnston212:
I tried uninstalling, but got an unsuccessful outcome. I then went and re-installed the new marketplace app that I got from Android Central. It now seems to be working fine. I think this might be related to flashing the gapps.
[Captivate Android Development] RTBee:
No problem, sorry I couldn't be of more help. Cute kids btw.
[Captivate Android Development] melbourne408:
Hmm not sure there either, I installed gapps also with the update and market was fine, I'll look into it, glad your market is back up tho

Sent From My Swaggin 1.5 Son Of A Glitch
[Captivate Android Development] Johnston212:
Have you installed the new market though?
[Captivate Android Development] melbourne408:
Yea, have had it installed for three to four days

Sent From My Swaggin 1.5 Son Of A Glitch
[Captivate Android Development] superj3211:
anyone have any insight on the audio through usb? no one answered my last post......
[Captivate Android Development] RockRatt:
I had the market issue in the past and MOST likely it has to do with trying to apply gapps that has an older market in it causing the issue. I have NOT had any issues this time and I have been running the new market. I just used rom manager to download #62 and clicked on gapps and had no issue. My guess is that when I click on the gapps via rom manager if it finds gapps already it kind of skips it and if it is not there it installs it. No market issues here at all. I have opened it and updated some apps with their updates.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] pwnerman:
i think im gonna hold off on this build because of the random rebooting issue that ive been seeing comments all over the place about
[Captivate Android Development] melbourne408:
Don't know if I'm allowed to incorporate the new market over but here is a gapps I put together.http://db.tt/tei5vsA

(Just tested out the gapps and had no problems, new market working just fine.)

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] RockRatt:
I haven't had any of those issues. #62 does incorporate a few things in Settings like lock screen seperate from wallpaper screen that I like. Just download it via rom manager, hit gapps, and also choose to backup rom along with clear dalvich cache. Then if you are one of the unlucky few you have a backup to restore to. I think it is the minority though with this build. All the people that have no issues just don't have issues to report on.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] cbasse:
No issues here either...
[Captivate Android Development] Johnston212:
I don't know anything about random reboots either. I got one on 60 and it threw a lot of things off, but once I fixed market on 62, I'm good. The only other thing I need to figure out is why do modems "degrade"? The JV6 modem is at least 50% "effective" compared to about a month or so ago. I got a 5Mbps speedtest result and doing the exact same test, in the same spot, same server, everything, I'm now getting 1.5 at best.

This also happened with JK4 a while back. Modem quality just seems to degrade, no clue why. Anybody have any suggestions?
[Captivate Android Development] pigrew:
Crash-bugs with build 62

I was having quite a few of them with build 62, perhaps every 15 minutes. I'm in Indiana and using the (default) JL3 modem.

Also, ever since #52 or so, I've had long periods where the cellular modem cannot connect at all and the "baseband version" is being shown as unknown.

Here are some logcat of when the modem fails, probably from around build 54.

http://pastebin.com/sgWiES3v

http://pastebin.com/NuwDHYfG

-Nathan
[Captivate Android Development] cbasse:
Thanks!
[Captivate Android Development] mose2000:
I am having the same problem
[Captivate Android Development] superj3211:
is anyone having problems with the new market? it runs well but will not let me install apps...tells me error downloading. There is insufficent space on the device but there is...and other times it downloads the full bar of apps and then just says error downloading

using build 60
[Captivate Android Development] malbolgias:
I had the danger problem just reboot into recovery and clear cache and dalvik.
[Captivate Android Development] littlewierdo:
Wow, can we say over-reaction?

GPS has been awful for me personally (my phone is a build 11). GPS will vary for each person, perhaps I should have clarified that much but I assumed that most people would realize that GPS performance varies on the Cappies wildly.

And actually, I read every changelog and I do recall the 'swift kick' verbiage. However, it changed little (if anything) for me personally.

As to 'who am I to judge stability' blah blah blah, well, I was actually responding AS A USER to another persons question who asked about stability (I am pretty damn sure I quoted his/her original post).

Reading a changelog means diddly squat. Real world performance is what really matters. In the case of gps, it sucks. Is that the phone? Maybe. Is that the rom? Maybe. Is it both? Could be. Maybe its the alignment of the planets... who knows??

I believe my only criticism of CM is their lack of guidelines as to what is stable / RC / Nightly. If you know anything about software development, you should have an understanding of what I am talking about.

If you misunderstood the gps not working well for me as criticism against CM, I dont know what to tell you. I believe I clearly stated that it was likely because the CM folks have other more pressing issues they are working on before gps stuff. There has been VERY little with regards to gps changes in the changelog, thus, I assumed very little had been done with regards to gps, especially based on my experience with the gps in my phone (running CM since nightly 16 and updated nearly every nightly - I believe I have only skipped those that had no changes and only skipped one or two because I didnt use my Cappy that day).

Really, take a chill pill, a couple deep breaths, get a massage, do some yoga, whatever you need to do to relax. If the CM folks cant handle a little constructive criticism, let THEM defend it.

But, Ill let you in on a little secret, they probably could care less about my opinion.

By the way, post # 9519 (posted yesterday, AFTER the post you were responding to), the last paragraph states the following:

"Also, how is the GPS doing? It was actually great for once in the 30s, but the 40s went back to mostly useless. Haven't had a chance to retry, so I thought I would ask."

So, fyi, Im not the only one.
[Captivate Android Development] kurrptsenate:
I got quite a few soft reboots on #62. I had to regress to an older version as it just scared me.

Weird thing here but my "black screen of death" problem that was plaguing my phone for so many builds in a row randomly disappeared around nightly 57-58. After upgrading past that point it reared it's ugly face yet again. I think I'm going to stick with 58 at this point until i have a reason to change it.

I tried using my GPS on google maps this morning with mixed results. I gave the phone about 6 minutes to find a lock with full bars but to no avail. I had to restart my phone which did give me a lock. After closing maps and reopening it, it started acting weird once again.
[Captivate Android Development] littlewierdo:
I havent had any random reboots or shutdowns since CM 30ish.

I went thru and uninstalled ALL apps that I did not use, used Titanium Backup to back them up on my sdcard, flashed to stock 2.1, master cleared, installed CM using AIO to 'inject' the rom (AIO installs the recovery menu and copies the rom to the phone and reboots into the recovery menu - bypassing having to root and setup your google account on the stock 2.1 rom. Much cleaner and faster this way imo), then setup market account on freshly installed CM, installed TB and recovered all my apps. I did not even install any apps via the Gapps (altho I did have to install Gapps to get access to the market, I just left all the apps unchecked and unchecked the option to restore my apps automatically).

Since then (Nightly 16), I have updated nearly every day to the new build (it gives me an excuse to reboot daily) and have not had any issues except gps and on one nightly build, they broke the bluetooth and fixed it the next day.

I have heard that the 'charge death' is a hardware problem with some Captivates and if you are experiencing this, you might consider exchanging your phone with the carrier if you can. FYI, charge death is when you have the phone battery at full charge and it is plugged into the charger, when you disconnect the charger, the phone becomes unresponsive (screen will not turn on unless you do a battery pull or the button combo to 'force' a reboot).

If you are experiencing this when the phone is NOT on the charger, you might consider a stock/master clear/start from scratch approach and see if that helps.

Spring cleaning is a good thing when you have the option (and thankfully, we do).
[Captivate Android Development] kurrptsenate:
The BSoD I speak of is inherently different from the "charge death" you speak of. It's when you go to make a call and block the proximity sensor, the screen goes black and will not turn on after pressing a button or unblocking the sensor. The easiest fix I've found besides plugging the phone into a computer is to light a lighter right by the sensor. Any bright light shined in the sensor is the only I've found to fix the problem while out-and-about.
[Captivate Android Development] Dorilife:
Flashed #62 last night, no random reboots no big issues..

Noticed one thing though..

Last night was 1st time i succesfully

Get CM7 on either of my sgs's..

I had CM7 on my old htc and it used to have the theme manager..

Im sorry for asking but is this available on current nightly?

For the captivate?

if so i dont have it..

Also when i try to go in cyanogen mod settings it just takes me back to home.

Only issues ive had.

Great job guys.
[Captivate Android Development] RTBee:
I've been reading lots of folks having some issues with #62, so thot I might hold off a bit, but as for your modem issue, I too live in Indiana and was having a couple of things like dropped calls (just randomly) and some other intermittent stuff. I've flashed a different modem (JK4) and haven't had a problem since.
[Captivate Android Development] saobang3886:
I don't have any problem with GPS, open Google map and it find my location just in 20 - 30 second, work well ! Every things work good for me until now with no problem, Should you make a clear install with RC1 build? ( Back to stock rom, then flash again, wipe all data) maybe it will work good!
[Captivate Android Development] Dorilife:
Update on this

I did a complete wipe and it fixed everything, no more force closing of cyanogenmod settings and got theme manager.

Weird beacause when i 1st flashed it was from freshly flashed froyo..