yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] artvandalay22222:
Ok I'm having some issues.

First, not a big deal, but after I flash a rom, namely continuum, the boot animation works fine. When I flash any newer version of talon, it reverts to the samsung boot anim.

secondly, after flashing continuum beta 6.2.1 and trying both talon 4.3 and 4.4.2.1 I get random reboots. Except that instead of a complete reboot, the phone will freeze up, screen will go black, no buttons work, for about 20-30 seconds. After which the phone comes back on just as if it had rebooted running media scanner. At no time does the boot screen or animations run. Very strange.

I just flashed back to continuum 6.1 and so far no"reboots"

I'm wondering, do you think I should try flashing back to stock?

Any ideas are appreciated.
[Captivate Android Development] Wdustin1:
Wow I am extremely happy I don't use bluetooth thats kinda scary that you could brick a phone over something simple like that
[Captivate Android Development] TheSoaresan:
The same thing started happening to me when I accidentally turned Bluetooth on...let me know if it starts boot looping at the continuum logo. If so, take out the sim card (and all other cards to be safe) and flash back to stock GB, then back to Talon..
[Captivate Android Development] artvandalay22222:
I havent messed with blue tooth, I dont use it. The reboots happen probably 3 or 4 times a day.
[Captivate Android Development] artvandalay22222:
also, whats a safe way to revert to stock rom? I have a newer batch 1102 I beleive. I would like to not have to reflash GB bootloaders if possible.
[Captivate Android Development] Spidious:
I will try these suggested setting today and see how well it does...
[Captivate Android Development] rajendra82:
This is actually a temporary side effect of flashing the kernel. The kernel flashing CWM script wipes your Dalvik cache. On the first boot after that, you'll only see the Samsung animation, because that's what is shown when the Dalvik cache is being rebuilt. On subsequent boots, it should show the sanim.zip custom boot animation.
[Captivate Android Development] artvandalay22222:
Thanks for the response, however its been like that for weeks now, many boots several different roms, kernals, modems themes etc. still, only samsung boot anim.
[Captivate Android Development] IDoMy0wnRacing:
UCKF1 No Bootloaders! 1 click or Full Odin Back To Stock GB:

http://xdaforums.com/showpost.php?p=15158920&postcount=1
[Captivate Android Development] pikachu01:
You flashed a no-wipe version of Continuum beta 6.2.1 right? After flashing, could you try wiping the dalvik and cache? A no-wipe is usually unstable. Best is to do a wipe.

Are you using OC/UV? How about lagfix? Which lagfix? CF or Voodoo?
[Captivate Android Development] Vaanhoot:
I've flashed stock with repartition checked and with 512.pit, 513.pit, and 803.pit. I have flashed 100‘s of times before and never had this problem. I can no longer get the phone to boot, always stuck at bootup. I just tried jf6 one click and still the dreaded can't mount mckblock0p1 error when booting up. Just got my phone back on warrenty. Dlev 4.2 and Talon 0.4.4.21 is bad mix. I literally just installed Dlev 4.2 and Talon 0.4.4.21 from getting phone back from repair with Rogers Stock JL1 and nothing else, had installed a weather app and xda app not running a lagfix, I was using bluetooth all day at work listening to music. I had lost my Titanium Backup files as they were only saved on my sdcard so no backups restored. This morning I have been trying to repartition mckblock0p1 manually by pushing parted to my phone and using it in shell. But it tells me Unknown Disk Lable. Try to write a new disk lable and it says Unable to write to mckblock0 - I/O error. I also tried to format everything and chose repartition sdcard in recovery, but it always tells me that it can't mount sdcard. I don't know what causes this but this is second time running Dlev 4.2 and Talon 0.4.4.21 that this problem happened to me. Repair center replaced main board on my phone to get it working again so it was like a new phone. Guess I have to send it in again.
[Captivate Android Development] Doug8796:
Thanks for this kernel, I am greatful. Is there anyway the dev could remove the 56fps limit ? I have seen many other kernels with this option
[Captivate Android Development] existz:
For those wondering about home haptic feedback, the reason it might have worked in 0.1.2 was from nexus s touchkey driver, I've reverted back to the one initially ment to be used, it fixes some other touchkey issues and will be easier to add BLN., I know there's a theme for continuum now with working home haptic...so rom devs will be adding it in on the rom side soon
[Captivate Android Development] existz:
Its already removed ...u might have to lock your screen once and unlock it...but I'm getting around 64...I'm not sure if ill keep it, I think I read somewhere there was an issue with it,(maybe from supercurio?) can't remember what at the moment, but for now its already unlocked until I see what the side effect is...might be removed later on.. it might not be worth the extra points in benchmarks as that's all it pretty much does

EDIT

Found it...supercurio noticed that it "can" cause colors to be washed out at low brightness for some, causing the brownish tint instead of black...up to you guys if you want to keep it or not...doesnt matter to me.
[Captivate Android Development] froli13:
Then you just put the finger on what was causing this. I thought it was just somewhat normal.

I don't think the extra benchmark points are necessary..
[Captivate Android Development] existz:
I personally agree...would rather colors be more vibrant and actually the color they are at low brightness as i mainly use my phone at min brightness (you can really tell the issue with my Onix kernel, where it has the extra min brightness and its darker than stock...it gets really brown.. Theres really no "performance" gain with it, imo having more cpu mhz will give more/better performance than a few higher refresh rate.. but thats just my opinion... I can always build a kernel to my likings, so its up to you guys what you want.. (i will only do one version as of right now during development, so dont ask if there can be one with it and one without it...maybe later on when its all about the features and not development) but whatever you guys think and ill include/leave it for tomorrows 0.1.4
[Captivate Android Development] abee_13:
I vote for leaving it out. Want my screen to be at its best.
[Captivate Android Development] nybmx:
Same here. I can't imagine people being able to notice a difference in framerates above 56. People will however see a difference with washed out colors.
[Captivate Android Development] froli13:
Also, did you get my suggestion previously? It was about mounting /system at boot in CWM. So we wouldn't have to do it manually when needing to push system apk. (Which I personally do often).

Thanks for taking this in consideration.
[Captivate Android Development] Doug8796:
I vote leaving it in. Future games need every frame they can get, and lag is not fun. This phone is beginning to get irrelelevant. The dreamcast emu I use works well with it on CM7. If you remove it bridge the kernels into 2 downloads because many like this option.
[Captivate Android Development] froli13:
Existz could remove it without telling and no one would see the difference and no one would talk about it until someone post about benchmark scores...

edit: we would notice that the brownish tint is gone though...
[Captivate Android Development] nybmx:
This is what I don't understand. Maybe I don't know how this works but I'm assuming that right now the max fps is capped at 56 and you're saying that for gaming purposes this is a bad thing. I don't think it's humanly possible to tell the difference between 56 and 70+ fps.

All games have points where there are drops in fps (think explosions and tons of artifacts on the screen) but capping at 56 doesn't seem like it would affect it negatively because it's just a cap on the maximum amount shown.

This is not a personal attack at you it's just something I don't understand about the situation in general. If I'm wrong about any of this then I apologize.
[Captivate Android Development] froli13:
Agreed. And even if there was a difference in performance, it would still prefer a clean white screen rather than a brownish one, but with a small performance increase.

Removing the fps cap is only to increase benchmark, IMO. No noticeable difference for me in the past with Onix/SuckerPunch.
[Captivate Android Development] johan8:
If you are serious gamer,

you can even see the different between 60fps and 70fps.

But on the small screen, the differences is very little.
[Captivate Android Development] H3llstorm:
If you're a serious gamer, you probably have a PC or console for serious gaming. :cool:
[Captivate Android Development] cashyftw:
That's extremely true.
[Captivate Android Development] johan8:
I'm just mention how people feel the difference.:p
[Captivate Android Development] surfed.tk:
What I don't get is if the screen refreshes at 60hz how can you see 70fps, those extra frames just get droped and you never get to see them. Or am I completely wrong here?
[Captivate Android Development] Doug8796:
no, the game will run faster than it normally does (at least in emulators). some games that are emulated require 60fps
[Captivate Android Development] FeO2:
I can't get the UV settings to apply on reboot. I've tried the Voltage Controller app and am currently using Pimp my CPU. The S_volt_scheduler file is being successfully created, it's just not running the script on reboot. I've re-installed busybox from the app (1.18.4) but that hasn't helped. The last thing I tried was wiping voltage stats, re-flashing 0.1.3 with ODIN, wiping cache (Dalvik as well), re-installing busybox, and then re-applying the UV settings. Still didn't take on the next reboot.

Anyone have any suggestions?
[Captivate Android Development] kodos96:
The screen's refresh rate is 55Hz. If you compute any more frames than that you're just wasting cpu cycles on frames that are never displayed.
[Captivate Android Development] Spidious:
Applied suggested settings. Real laggy at 1200. runs pretty good at 1000. Will check later to see if it stays running smoothly.

Sent from my phone in a secret location.
[Captivate Android Development] Wdustin1:
So I don't know if its any help but running talon .21 I used bluetooth to send a file to my wifes phone and had no issue I haven't tried a bluetooth headset and now I don't intend on using one either. By the way my wives phone running the same as mine and no issues with hers either.
[Captivate Android Development] Koizuma:
Hmm wonder if the Bluetooth thing is hit or miss, I've used my Bluetooth head set several times on .21 now and not a single issue from using mine.
[Captivate Android Development] existz:
What rom are you using??

Also to those thats suffered from this, what rom were you running also??

Until more info is gathered on this subject, Ive pulled latest version, do not use Bluetooth to be on safe side..
[Captivate Android Development] demarton:
Lag is unbearable overtime, not even surviving a day without rebooting to clear out memory leaks.

About to given up captivate or any sgs1 with miniscule 512 ram, maybe that just not enough for gingerbread to operate normally?
[Captivate Android Development] Koizuma:
I'm on Apex 9.0 and i have had 0 issues with it, infact some places around here u can only be on the phone if your on a Bluetooth headset so when I'm out I always have one on, and about 60% of the time its actually in use.
[Captivate Android Development] existz:
Thanks

If im not mistaking, those that had this issue were all on Dlev..., i dont think anyone from Apex or Contiuum is having this issue (if im wrong someone please correct me), thats why those that DOES have this problem, let me know what rom....its possible it could be rom specific, but its to early to say just yet, so until more people chime in, will keep the latest test pulled

EDIT

not rom specific, reports of Apex also...test will stay down till futher notice, or alteast figure out why its doing this for some and not everyone
[Captivate Android Development] pikachu01:
Did you try tweaking Memory Freak with these settings:

Nexus S LMK

Zram: 160

Swappiness: 50
[Captivate Android Development] Koizuma:
No problem, I've wanna say I've heard about it off of another rom too but I cant put my finger on which one
[Captivate Android Development] TheSoaresan:
I was using mosaic...this may not be fully Bluetooth related because I accidentally turned on Bluetooth again, nothings happened yet. But incase you're wondering, this what happened a few days ago before I went back to stock bootloaders: 1) severe lag- phone froze for a few minutes and then rebooted itself. This happened a few times..

2) got stuck on mosaic bootanimation after clearing caches (not sure if it's related)

3) pulled out sim card and it started booting normally.

My phone is working fine now though even after I turned Bluetooth on...so I'm kinda mind-boggled..
[Captivate Android Development] existz:
Let me ask one more, any of you know around about when this started? Do you remember the last test that this did not happen?
[Captivate Android Development] geokilla:
No problems here with regards to BT!
[Captivate Android Development] Time_Zone:
The first time I noticed the reboots I was on Sensation by crisis. 4.4.15. It would reboot and start trying to convert /data (voodoo voice) even though I was already on ext4 then it would say "no space left on device" (voodoo voice) and reboot . I could recover by flashing back to stock. My trashed filesystems have both been 4.4.21 and apex 6.1. Also, if you remember back in 4.3, there was a racing cpu issue when BT was enabled.
[Captivate Android Development] geokilla:
How do you run /bin/install-ramfs-setup?
[Captivate Android Development] Time_Zone:
Just to confirm:

MOSAIC VI ?
[Captivate Android Development] geokilla:
Yep. In sig ;)
[Captivate Android Development] nappent:
My Wife is running Continuum 6.1 and I'm running Continuum 6.2 Beta both with the .21 and had no issues with bluetooth
[Captivate Android Development] -Thrive-:
Thanks. These settings are awesome on my phone!
[Captivate Android Development] Vaanhoot:
I was using Dlev 4.2 and had my Bluetooth running through Ford Sync listening to music. As a side note, both times it happened it happened right after I disabled Voodoo lagfix. That is what I originally thought caused the problem. Just went and sent my phone away again for repair, just told them it wasn't fixed. They called Samsung repair center and just issued me a brand new captivate. After almost one year they gave me a new phone on warrenty.
[Captivate Android Development] tmng95014:
+1. Please do tell.
[Captivate Android Development] warri:
I'm Running Dlev (Latest) and .21 and have been using bluetooth constantly. Not a single issue here
[Captivate Android Development] johan8:
0.4.4.21 is good for me.

Stock i9000 rom, no BT problem.

After 20hrs usage, memory raised over 280MB, but still smooth.
[Captivate Android Development] tmng95014:
I have been running Continuum and 0.4.4.21 with BT. I used BT every day when I am driving to/from work. There is no issue except Memory Freak is all blank.
[Captivate Android Development] Wdustin1:
Dlev 4.2 talon .21 used bluetooth to transfer files from one captivate to another no issues if it helps phone builds 1010 and 1007
[Captivate Android Development] Time_Zone:
A bluetooth headset or car audio? Or For file transfer? How were you using Bluetooth?
[Captivate Android Development] mpencexda:
I am assuming Memory Freak is an app.. Where do I get/access it.. ?
[Captivate Android Development] warri:
I use it for both my car audio, and car speaker/car hands free . I have not used it for file transfer
[Captivate Android Development] Holmes108:
If you have the latest Talon, it should already be in your app drawer.
[Captivate Android Development] warri:
Check the Themes and App Sub-section of the Samsung Captivate Forum
[Captivate Android Development] mpencexda:
Hrm.. Not listed but I do have a ram.conf.. Running talon 0.4.3 - 1200
[Captivate Android Development] timn2bama:
memory freak

Can memory freak be used on 4.3 1200?
[Captivate Android Development] existz:
Probably not, as MemoryFreak checks the current LMK settings from ram.conf which is different than the ones in 0.4.3...

On another note, we have a 'possible' fix for the Bluetooth causing corruption issue. Will get another test up sometime today. We are starting with the obvious and going from there, so labeling it a 'possible' fix until its 100% confirmed fixed, but this should fix it.
[Captivate Android Development] shane87:
Technicaly, yes. However, as of right now the Talon defaults are hard-coded into the app, and they are the defaults used in 4.4.x, so they may not work as well.

I am working on a new version of MemoryFreak. The new version will be both backwards AND forwards compatible with talon. It will read Talon default settings from ram.conf.default, so those settings will match the ones designed for whatever version of talon you have on your phone. As an example, if you are running 4.3, it will read the defaults for 4.3, instead of using the 4.4.x defaults. Also, if kodos/existz changes the ram.conf settings, they will put them in ram.conf.default, and it will read them in so that it will use any new settings properly as well. The new version will also have a few changed labels, and it will allow a zram size of up to 1gb.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] radraz:
My memory freak is all blank. Can't pick any presets and and can't see any values for sliders. Any fix for that? reflash kernel?
[Captivate Android Development] Time_Zone:
I can test. But if this kills my phone I am pretty sure I have outwarmed my welcome at the ATT warranty center.

edit: I will test of course. I am like that...
[Captivate Android Development] tmng95014:
Try flash this courtesy of topiratiko, http://xdaforums.com/showthread.php?t=1221709.
[Captivate Android Development] geokilla:
I'd like to add that I also have the same version of busybox installed in both bin and xbin locations.
[Captivate Android Development] Spidious:
Tried the different settings.. Few hours later severely laggy. Installed darky 3.0 and it is smooth as silk...???

Sent from my phone in a secret location.
[Captivate Android Development] existz:
Changing lmk settings is not going to cure memory leak.., it might help in some cases having more aggressive settings, but its not going to solve the memory leak, so its still going to happen and get laggy after some uptime...

AGAIN, we are still trying to locate the issue.., we are aware that its there, give us some time to find it and fix it...As of right now theres really no work-around to fix it.., as mentioned though, some are having luck with more aggressive LMK settings, but note that you are trading off multitasking..etc.., so if you dont usually have alot of apps open in the background, then it might help you some..IMO nexus s settings in MemoryFreak are better than Stock SGS
[Captivate Android Development] topiratiko:
Another thing that helps. Reboot your phone in the morning.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] mpencexda:
I just use the clear memory setting from within Task Manager if my phone ever seems laggy.. Noticed no one else really mentioned it. Also Terminal Emulator is a great program to run commands from /bin and what not.. I use the command "free" to ensure that my swap is being used and what not..
[Captivate Android Development] Spidious:
Rebooting the phone every three hours isn't a option. Check out the darky 3.0 and see if it will help you, as I don't have the problem with that kernel...

Sent from my phone in a secret location.
[Captivate Android Development] mpencexda:
Anyone out there with the memory leak under talon willing to switch to the jk4 modem. I moved to it from gk1 and suddenly my memory leak seems to have disappeared.. May just be a coincidence but was hoping someone else may be adventureous enough to try it out.. You can get any modems you want to play with from this thread.

http://xdaforums.com/showthread.php?t=876391
[Captivate Android Development] tmng95014:
+1. But I am fine with Continuum 6.1 and talon 0.4.4.21 using nexus s/10/50 Memory Freak setting. It is working fine and i clear memory in task manager once a while. Only turn on wifi,BT, GPS when needed. Battery is superb and stable running 1200OC, -75 UV all the way.

No reboot or switch kernel is needed.
[Captivate Android Development] RashaMatt:
That combo is actually working pretty good for me right now.

But my Bluetooth headset has never stayed connected on ANY of the 2.3 ROMs and kernels I've tried (and takes about 20 tries to get it connected). At least it doesn't bootloop though.

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, JJJV5
[Captivate Android Development] geokilla:
Got tutorial on how to make it work?
[Captivate Android Development] mpencexda:
Which part?

sent from an alternate reality
[Captivate Android Development] studacris:
The what not...

Lmao
[Captivate Android Development] geokilla:
The part on getting MemoryFreak to work, where you said you used terminal emulator to install something.
[Captivate Android Development] tmng95014:
Flash this courtesy of topiratiko, http://xdaforums.com/showthread.php?p=16720928#post16720928. This will get MF to work. You can also use terminal emulator and execute the /bin/ramset-install-conf. But the topiratiko flash is a quick fix.
[Captivate Android Development] topiratiko:
You can flash file in my sig to correct issue. You can keep my custom settings if u want think of them as nexus s settings just a little more strict, or you can adjust through memory freak

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] geokilla:
Flashed it but MemoryFreak is still blank. Either way, I've given up.
[Captivate Android Development] topiratiko:
Try to mount system and data in cwm

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
Don't give up :(

It's a busybox problem. Install the busybox installer from the market and try installing version 1.17.x to your xbin (and remove all other instances of busybox you find elsewhere).

Install first before removing!
[Captivate Android Development] Rrryan2:
I haven't had BT problems since about JVB or so, and even then it was just a matter of toggling it 4-5 times until it "caught." Using Apex since 9.0 and 9.1, Talon (this time around) since about 0.4.4.14 or so, never had a single problem with BT, which I use about every other day, sometimes for hours at a time.

Also having no issues at all with Memory Freak using Busybox 1.18.4 (stock Apex 9.1 I believe). The memory leak is still there, though its ill effects seem ot be blunted somewhat using Nexus S LMK. But I'm mostly content to just reboot every 12 hours or so.
[Captivate Android Development] pikachu01:
MemoryFreak is bundled from 0.4.4.21 onwards. :) Too bad it's removed right now because of the BT issue. Try checking back later for a new version.

You probably have conflicting versions of busybox in your kernel. Try installing busybox installer from the market and installing version 1.17x into your xbin. After that, remove all other instances of busybox elsewhere in your *bin folders. Note: Install first before removing all others.

Try disabling ZRAM and swap. I'm guessing that one of your apps are doing RAM accesses faster than the ZRAM can swap, hence the lag. Use Nexus S LMK settings too.
[Captivate Android Development] geokilla:
I think this worked! I can finally see MemoryFreak!

I see that ZRAM size and Swappiness is pretty much maxed. I guess these were the settings that you found were good for you? Since stock Nexus S settings are different if I remember what people posted correctly.

Amazingly multi-quote works again. It stopped working for a while.