yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] wallsg:
Go back and look into the double-digit and low triple-digit posts. This thread has always been hostile compared to friendly ones like the Nook Color threads.

It reminds me of the early days of the Inter-Tubes when someone would post something commercial on a newsgroup. The bile and venom would just flow in rivers.
[Captivate Android Development] melbourne408:
Are you truly sworn to this? Attack everything as if your the most knowledgeable person around? I'd never want to think I knew it all, then what would be the point. I think it's called oppositional defiant disorder...

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] shaolin95:
I guess the supercharger V6 off topic posts and Glitch questions are still a bit better than this sudden Royal Rumble dont you agree? LOL
[Captivate Android Development] nkrick:
???

What are you talking about? My post was not attacking anything or anyone. Shaolin mentioned that he wonders what changes require a new kernel. I was just saying that in the change log, if one of the changes is "kernel," it means that the team hacksung kernel was updated.

I did not mean to imply in that post that all 3rd party kernels always need to be updated when the team hacksung kernel is updated. But, if I were using a 3rd party kernel, I would ask someone (such as the 3rd party kernel maintainer) if their kernel needs to be updated since the team hacksung kernel was updated before I tried out the newest nightly. That is all I was ever trying to say, though I freely admit that I did a poor job saying that in my initial post.

My initial post was not mean to sound as though I am uber knowledgeable, I originally started the post because I was excited that the orientation fixes could potentially have a positive impact. Then I decided to re-write to mention the other fixes also.

The kernel comment was perhaps a bit out of line and related to the fact that it seems that anytime there is an update in the nightly specifically for aries or captivate, someone asks if kernel-x works with the latest nightly. I was actually trying to avert the 3rd party kernel discussion from occurring again. I should have left that part out, or if anything, said something to the effect of, "if you use a third party kernel, check with the developer to see if any updates are required."

How about we all forget about my initial post and replace it with what I was originally going to post which was something like:

"Nightly 75 has some orientation fixes, is there any positive or negative feedback or experience with it?"
[Captivate Android Development] melbourne408:
:)

Agreed, I took it a little one sided :D

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] KohjiNagata:
Maybe but I think we can all agree there's no way its better than a ladder match...

I have one thing to say to all the bickering, come at me bro
[Captivate Android Development] melbourne408:
Haha we need forum skype, then we'd know the irony put in each sentence and how to take it, I'll address each place properly, for now everyone getting good results with the latest nightly?

Sent From My Swaggin 1.6 Son Of A Glitch
[Captivate Android Development] shaolin95:
Good point! lol
[Captivate Android Development] FireRaider:
I haven't yet dared to update again after my Bluetooth fiasco. What is the orientation update supposed to improve? I haven't ever noticed any problems with it.

And how do most of you decide if its worth the bother to update? I didn't bother with the CDMA signal update a couple nightlies back since I didn't figure it would affect me. I even wondered why it was included under the Captivate heading.
[Captivate Android Development] nathanjones:
I go by the "if it aint broke, don't fix it" rule personally and stick with a build that's working.

That being said, eventually my curiosity gets the best of me, and I update. For instance, I was on the first RC1 build up until yesterday when I jumped to 72.
[Captivate Android Development] gabby131:
My ATT cappy stayed on the cyanogenmod swirling bootscreen all night for 7 hrs! Spooky.....:D

Sent from my Cappy
[Captivate Android Development] Jusrertiner:
When I out the power shutter on and try it just locks the screen any fix

Samsung captivate

glitch kernel

cyanogenmod 7 #71

OC and UV
[Captivate Android Development] cbasse:
I'm on the latest nightly and have suddenly started experiencing numerous force closes and random reboots. The force closes I'm somewhat used to - there seems to be something with LauncherPro that causes a force close right after the phone boots up. But the random reboots are new - I can't really tie them to anything specific. I've tried this latest nightly with the stock kernel and Glitch, and I've experienced both FC's and reboots with both kernels.

Could the modem I'm using make a difference/cause the phone to reboot? Anyone have any suggestions for the LauncherPro FC? I took someone's advice from several days ago and tried fixing permissions (through ROM Manager and CWM), but that didn't help.

Any thoughts, comments or otherwise are appreciated!
[Captivate Android Development] shaolin95:
I just did a clean install on mine after experiencing similar things but I have been updating with nightlies and test kernels so many times that I guess it is normal at some point to need a clean install.

I never had that error with LP with CM7 though (only with froyo roms) but you may want to check Go Launcher. After many tries this new version has finally replaced LP for me in every respect.

About FCs always check your /datadata to make sure it is not full.

Regards
[Captivate Android Development] br123:
LauncherPro FC: let it be for a few minutes after booting up. Don't try to change homescreens or launch applications. If you do, it will FC. Leave it alone for a minute or so after the phone first boots and you'll be fine.

Other FCs: did you restore system apps+data? If so, that's the cause of your problem. Never restore system data - only app data if need be. The fix is to wipe and reflash.
[Captivate Android Development] EnemyOfGlaDOS:
I doubt the modem has anything to do with but..:rolleyes: I used Launcher Pro for the longest time.. and just delt with the occasional FC's. However, i started using ADW that comes stock with CM7 and am quite happy. It's little different and takes a little getting used to.. but pretty happy with it. The new transition animations are killer and there is zero lagginess to screen scrolling. Only thing i miss is the 3D app drawer and facebook themed widget, everything else ADW does pretty darn well. Give it a try:o

Check your datadata in terminal emulator in your apps. Type "df" and see where your at. If your over 80 or 90%, than its getting pretty full, and you will need to move some of your apps to your SD card. That should help with the FC's. The random reboots.. I have no idea. I have NEVER had that problem (unless im overclocking, but that is not what i would call a random reboot). It sucks, but a good flash to stock and master clear sometimes does wonders. Another user was having some weird reboot issues as well, and he bit the bullet and FTS and came back to CM7 and where he was.. he said the phone feels much better, cleaner, snapier.. so, up to you- but might be worth a shot.

(if you have your back button set to kill apps via long-press, you can kill Launcher Pro when you boot up, or whenever you think your gonna get a FC, and that will kill LP. It loads up much faster than waiting .. that was a little trick i did when i didn't want to see the FC pop-up ;) )

*EDIT* ..what shaolin said :p
[Captivate Android Development] shaolin95:
Good stuff!

You know Corey... every year of my life I grow more and more convinced that the wisest and best is to fix our attention on the good and the beautiful...if you just take the time to look at it" .... sorry couldnt resist! :D
[Captivate Android Development] cbasse:
thanks for the suggestions and feedback...

I've been hesitant to try something other than LP since I paid for it and it was one of the first apps I bought, but I may just have to give GO or ADW a try.

And I guess I may just have to flash to stock and start over again...see if that clears up my issues and gives me a better experience. Hate to have to do it, but I agree it is probably something that should be done "every now and then". Will have to block off some time so I can re-install/re-customize the way I want it!

As for the datadata...I don't fully understand what this is all about. I did read about it some time ago, so I went ahead and moved a ton of my apps to the sd card. but when i just typed df into the terminal emulator, i think (if I'm looking at the right entry) I'm at 83%. Is that saying the internal space for app installations is 83% full, so I have to try to find more apps that I can move on the sd? is there a rule of thumb as far as what types of apps should/should not be moved to the sd card? for example, can I move dolphin browser, or powerAMP or beautiful widgets to the sd card without impacting performance in some way?

Thanks again! I'll be hitting your thanks buttons! :D
[Captivate Android Development] EnemyOfGlaDOS:
haha.. just when i forgot about that line :D
[Captivate Android Development] EnemyOfGlaDOS:
not entirely sure what can get moved where and what can't. 83% seems like it's gettin there. And yeah, im pretty sure that is your internal space. :o

(obviously still don't know how to multi-quote :p)
[Captivate Android Development] Smasher816:
I don't know how to multi-quote eather...

I just click quote on one, copy it, quote other, paste first quote thing above the second one.

As for what apps to move. You should be able to move most stuff besides widgets and services fine.
[Captivate Android Development] EnemyOfGlaDOS:
lol.. yeah smash, that's how I usually multi-quote too :p

..thanks for the info!
[Captivate Android Development] shaolin95:
Nobody knows how to multi quote..we just fake it. :D

75 is working nice and smooth for me so far btw but I still do not quite like the new market...
[Captivate Android Development] wetwhere:
Howdy All,

I too have had problems with LPP (paid version) crashing/hanging on boot and often when coming out of sleep; I also experience spontaneous reboots. However, I ONLY see these problems when using custom kernels (Glitch and the other two). With the stock kernel LPP works normally and the phone never reboots spontaneously.

If you are having issues with with the size of /datadata keep in mind that some apps store large shared library files in /datadata. For instance, Netflix stores 20MBs worth of libraries there. Although moving an app to the sdcard doesn't move everything, it does appear to move libraries and this can provide significant reductions in the size of /datadata. Please note, when I say move apps to sdcard, I am referring to the built-in method (Settings>Applications>Manage Applications>Netflix>Move to SD card).

You can tell which apps use large amounts of space on /datadata by executing this command as root (which will list apps that take up MBs of space):

du -hd1 /datadata | grep -E '.*\.[0-9]M'

You can tell which apps have large shared libraries by executing this command as root:

du -ha /datadata | grep .so$

I hope this helps.

Regards,

WW
[Captivate Android Development] melbourne408:
Time to test #76 stock

then I'll elusively flash something, later...let you know if it's stable and not too glitchy ;)
[Captivate Android Development] sixstringsg:
To multi quote, press the multiquote button on all but the last one you want to quote, then on the last post you want to quote push the normal quote button.
[Captivate Android Development] nkrick:
I think everyone may have been referring to the fact that it doesn't always work right. Or, i could be wrong and it may only be me that it doesn't always work for...

Sometimes I can do what you describe and it works perfectly fine. Other times I will only get the quote from the last one (the one I hit the "quote" button on).

edit: To clarify, the problem I have seen doesn't come and go. It worked for a long time, then sometime in the past few months multi-quote stopped working for me. I have not tried recently. If there was an actual problem aside from my browser/computer, it may well be resolved now.
[Captivate Android Development] makelegs:
Ok....stupid question of the day. Keep in mind that I'm only a casual captivate maintainer. It's not a phone that I live with. I don't quite understand the perceived need to flash back to stock first, when doing a "clean install". Why not just go into recovery.....wipe system, data, dalvik, cache.....then just reflash ROM/gapps, set everything back up, and call it a day?? Why the extra step of flash back to stock? What's the point?

Sorry if this evokes a facepalm....maybe it's just a weird samsung thing. ;)
[Captivate Android Development] Smasher816:
In the next nightly (will be 77), it says

"kernel: support for emmc on gingerbread bootloaders (android_device_samsung_captivatemtd)".

So does this mean we can/should use the new gingerbread bootloaders.

Or are there still some things that need to be worked out?
[Captivate Android Development] Haloruler64:
That's curious. I think they mean i9000 bootloaders? Because EMMC works fine on Captivate KF1 bootloaders. I just accessed it. and I flashed with KF1 bootloaders without flashing to stock.
[Captivate Android Development] pigrew:
Battery charging fails

Yes, as noted a few days ago, I also encounter this issue, especially while using gmaps navigation with the GPS in the car.

This has been going since before 19 June. I'm not sure if it was caused by a code change, or just by the weather getting hot. Thinking about that, (and this is way off topic), but I also had some issues with my phone during the winter (when the temp was around 0 F / -20 C).

The only way to resurrect my charging is to remove the battery. Another side effect seems to be that if I shut down the phone, connecting the USB cable does not cause the phone to turn back on (like it normally would).

-Nathan
[Captivate Android Development] RockRatt:
I followed it to the gerrit review and it sure does state it for the captivatemtd so I wouldn't think that would be so many typos. My guess is that EVEN THOUGH it works now as you said they are basically making it more of support for using them now. I know they said they wouldn't support it until ALL the samsung phones had the NEW gingerbread bootloaders. I MAY decide to next time I want to clear everything out and start fresh to flash the i897 ginger bootloaders and then start over. (If this is the actual case that they are now supporting it).

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] Haloruler64:
Did you notice actual changes in the code? I mean it'd be great if it was officially supported, but it seems to work perfectly as it is.
[Captivate Android Development] Mortem Tuam:
So I've been on CM7 now for more than a few days. Battery life is not good. Any ideas on how to improve this? I unplugged at 7am it is now 11am and I am at 50% battery.

Someone suggested to change kernels but I was also told to be very careful on CM7 of doing this.

edit: I should also say phone use has been very light....no heavy browsing or anything. Just texts and a few g+ updates
[Captivate Android Development] Keland44:
i've noticed the same

i've been using glitch kernal but i've noticed that after a while my governor will switch from smartass to ondemand for me i noticed i get great battery life when my phone is set to smartass and noop
[Captivate Android Development] Mortem Tuam:
I am downloading build 76 now, maybe that will help
[Captivate Android Development] whyareyou:
I am not seeing this steep drop, I have about 25 mins of usage time between 7-11 and my battery is at 70%. It usually lasts me all day with about 75 mins of usage (i.e., screen on time) and background data turned on. I am on everything stock CM7 except for JK4 modem.
[Captivate Android Development] Mortem Tuam:
I am all stock CM7 no changes to modems or kernels

I dunno why the sharp drop in battery :( but I am sure I will find an answer :)
[Captivate Android Development] kmakiki:
Are you guys running the most recent nightlies? I'm using an older nightly (I think it is 66, I've been having issues with the latest ones) and Glitch of course. My battery is at 76%, phone has been on for 5.5 hours, screen on for 44 minutes about. Also have 15 minutes of voice calls.

If you guys are not using it, try JuiceDefender. There is a free version, and it helps with battery a lot, especially if you are using background data.

Also, V6 Supercharger, the 3G script, and the kernel script are all running on my phone. Don't know if that is helping or not, but I'm just throwing it out there as a suggestion.

EDIT: Also, UVing seems to help a lot as well.
[Captivate Android Development] nkrick:
I have never flashed back to stock since I started using custom or 3rd party ROMs. With CyanogenMod, I use the factory reset option in ClockworkMod Recovery when I want a fresh start.
[Captivate Android Development] RockRatt:
+1

The ONLY time I have flashed back to stock is when I screwed something up royally on my other cappy going from i9000 bootloaders to i897 bootloaders. Other than that I do not just go back to stock randomly.

As above said just perform a wipe cache format data and your pretty clean. If you want even MORE CLEAN you can delete everything off your sdcard, factory reset data and cache, wipe dalvich cache, then load up whatever rom your trying to do.

IF your going from CM7 to a different rom you need to repartition though but I have never had to do that as with my primary phone I haven't left CM7 since it was first put out for our phones.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] Smasher816:
Alright im thinking about flashing the gingerbread bootloaders...

First is there a eclair/froyo bootloader package, or is one click the only way back?

Second will i be able to use the gingerbread bootlogo changer?
[Captivate Android Development] nkrick:
Thanks, I forgot to mention that case. If you want to flash back to a Samsung based ROM, you do need to flash to stock using Odin.

Like RockRatt, I have not flashed anything except for CM7 since the first compiled CM7 release by team hacksung back in March.
[Captivate Android Development] halfsoul:
Your sig disagrees with you. ;)
[Captivate Android Development] RockRatt:
I have TWO captivates. One with CM7 running the Escapist Kernel to 1.5Ghz and have NEVER left CM7. The second cappy runs Apex 8.3 right now but I use it as a test phone with running anything from the froyos to almost all the gingerbread i897 and i9000 based roms with testing out both the i897 bootloaders now and was on the i9000 bootloaders.

But WHAT exactly in my signature states that I am NOT on CM7? If I am using my second phone then that is when you will see a different signature from the xda app than the CM7 captivate which I am on NOW and you can see from my signature.

Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
[Captivate Android Development] halfsoul:
...which also explains why you said "primary" phone. :)

I was talking about the signature appended to every post (only visible on web) which says "Cognition or Perception..Gotta have my flash fix for the week". Figured it was just outdated.
[Captivate Android Development] RockRatt:
I guess I should change that huh. Haven't been on xda from the web in a LONG TIME and about a year ago is when I was using cognition or perception roms.

I have used the xda app mostly for a long time and all I saw was that you quoted my signature saying "Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted" so I was confused.
[Captivate Android Development] stuff:
After coming from a fresh install, everything installed great. I installed gapps, and that worked.

I opened the market, and it closed (not force close) but just closed, and I assume it's cause it was updating it to the latest.

Behold, it did update it to the newest market.

Now, I can't open the market for more than 5 seconds and it will force close. It does it every time.

I cleared market data, cache, and even fixed permissions. I factory reset/cleared data, and reinstalled the rom. Still has this problem.

Please tell me there's a silly, easy fix.
[Captivate Android Development] makelegs:
Right on, guys. Thx for the confirmation. I don't see flashing anything but cm7 on that phone....EVER ;). I do imagine that a full wipe is due any time, now. I generally just flash a nuclear wipe script when I clean install (double wipes system, cache, dalvik, data), but some of the things folks are used to doing with samsung phones have always seemed foreign and seemingly avoidable for me.

Better safe than sorry, so figured I'd ask. Thx again
[Captivate Android Development] sixstringsg:
As far as the battery question, I run glitch and get 16 hours ish of life, hour and a half screen time, that brings me to 20%
[Captivate Android Development] stuff:
Update on this:

I flashed all the way back to 2.1 eclair. Then flashed back to CM7 latest, while formatting everything in the process. Cleared all data, etc etc.

Market updates as normal, then force closes :/
[Captivate Android Development] xueqintan:
thanks. i love cm
[Captivate Android Development] makelegs:
Use TB to wipe data for market. Usually fixes that FC issue. Ymmv
[Captivate Android Development] disellusional:
how's the battery life on this compared to custom roms (mosaic/apex/continuum?)
[Captivate Android Development] superj3211:
what is the script you run when doing that....i.e.- were can i get it......
[Captivate Android Development] techmik67:
just a slight correction.... there are heimdall packages out there now to flash to kb1 and/or kf1, so you dont *need* odin anymore... =)
[Captivate Android Development] Smasher816:
Happy 1000the page.

On topic: is the build bot broken, I want 77.
[Captivate Android Development] mortuus.x:
Just an update that will highlight the idiocy I occasionally capable of; I'm using droidwall and had gps blacklisted. Enabling it yielded a near instant ability to obtain a lock.

I couldn't understand why I could see satellites yet no matter how many times I tried to obtain agps data I couldn't use any satellites. Then it dawned on me....
[Captivate Android Development] cbasse:
There now...
[Captivate Android Development] dan96815:
#78 is up!!
[Captivate Android Development] FireRaider:
Working good so far on mine. (meaning Bluetooth issue didn't return)

As noted in a few posts above I think its a good idea to clear everything once in a while. It sure fixed all my odd issues I had going on.
[Captivate Android Development] cbasse:
seeing all of the changes in this latest nightly, i decided to clear everything and do a "fresh" install.

:confused: question: not sure when it stopped doing this, but not too long ago, when I performed a fresh install and had to go through the setup process upon boot, it would get to a point where it would basically reinstall all of my market apps for me. It doesn't seem to do this anymore (I have to manually restore apps through MyBackup or TiBu). Does anyone know if there's a way to "force" it to do this?

Thanks!
[Captivate Android Development] dan96815:
I have noticed this also it use restore my apps and even my themes! but now it doesn't :(
[Captivate Android Development] dan96815:
Happy Cyanogen 10000!!!!!!!!
[Captivate Android Development] nkrick:
LOL. I was waiting for someone to correct me on that. As I posted I thought of it, but I was in a hurry and didn't have the time to look up how to spell "heimdall." ;)