yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] gangpe:
Something weird happened this morning....

Hi Guys,

Let me start by saying existz, you are the man. I've been looking forward to your 2.2 build, and you have not disappointed.

Here's what happened this morning. I just got a new 32GB micro SD card and tried to move my stuff from the old card to the new. It decided not to play nicely and not transfer all the data, but this is where it gets weird. I was originally on rfs; I had not made the jump to ext4 because I had no problems with it. Phone freaked out for a minute, so I rebooted. Next thing you know, it's converting to ext4 without my consent. Maybe my phone is possessed; I don't know. After the conversion, I check the internal "sd" card, and there's nothing there. I had originally 1GB free; next thing you know I've got 13GB. Once again, this is probably a fluke (possible user error), but has anyone else run into this? Thankfully I was able to open up TiBU and back up all my programs, but yeah.

Ok, enough of that - it's running fine now, and thanks again!
[Captivate Android Development] alexige:
When you restart your phone the way the lagfix works with this kernel it is set to do it automatically on first boot. It should have done it the first time u started the phone after installing the kernel but oh well. If you want to disable lagfix it's in recovery under voodoo.
[Captivate Android Development] Captivate2010:
I try diferent laptop to and nothing.....still no recognizing the phone.....I can't go to recovery just download mode but the laptop not recognicing.
[Captivate Android Development] apetrakian:
Bluetooth bug

Great kernel. Very smooth. Running 1600 mhz. No pbm.

Except...

When I connect a bluetooth headset, clock always goes to 1400 mhz. Stuck there. Even when u disconnect headset, it goes briefly to 100 mhz then stuck again at 1400 mhz until I toggle bluetooth off altogether then goes back to nl. 100% reproducible even after reboot. 1400 mhz is not even a checked state on my vc setup.

Running continuum 5.4.1 and 2.2 R.

Thanks.
[Captivate Android Development] Koizuma:
Got a different computer u can try (as in a desktop?) I know a friend of mine had that same issue when i was walking him throw the froyo upgrade and he ended up having to use his desktop and not the laptop which was his main computer.

Then theres also been the issue of my roommates laptop not seeing my phone and my desktop does, just throwing some ideas out for ya
[Captivate Android Development] Captivate2010:
I using 2 diferent laptop and same result windows message "USB device not recognize" I going to try buy a new usb cable and see......thanks
[Captivate Android Development] Koizuma:
Try a Motorola USB cable if u can find one, they seem to have the best fit overall. alot better then the cable that came in the box with the phone.
[Captivate Android Development] Time_Zone:
Ran into similar problems on apex. The 1200 version works fine however. Must be launcher pro
[Captivate Android Development] existz:
Well next version will probably be 1.2ghz then till I can get 1.6 stable...but I've already added in something new you guys will be able to play with, configurable gpu overclock from TheEscapist... you will be aable to adjust the gpu max clock just like the cpu clock, will be able to set it for each frequency, some steps like higher gpu, some like lower.. As of 0.2.3-T1 we have to edit it via a sysfs file, but shane87 is working on adding it to Control Freak so it can be adjusted there ... stock gpu clock is 200mhz, I've managed to get 340 stable, haven't messed with it anymore yet...but it will be just like the cpu, different for everyone
[Captivate Android Development] rlorange:
Really? I find it hard to believe anything is wrong with your overclock code. I could never reach 1.4ghz on froyo/onix nor undervolt beyond 25mv at 100mhz. Without sleep /charge deaths. Yet here I am stable at 1.44ghz and 125mv on 100/200mhz on gingerbread Talon...

Same phone yet worn out! I think reported problems are either rom related or we have a lot of noobs who don't yet know how to run a custom oc/UV kernel. I don't think there is ANYTHING wrong with the code and I feel you should not be spooked to much by all these random reports which, frankly, make little sense to me beyond people just not knowing enough yet thinking they do... no offence to anyone.

**Simply Honey3.5, Zak'sTalon 0.2.1 kernel 1.3ghz, ZSJV5 modem**
[Captivate Android Development] Time_Zone:
That has to be it. I am totally running bluetooth.
[Captivate Android Development] zerkai:
Existz, do you recommend using the 2 scripts by Zach that he provided for his last modded version of your kernel? His two scripts include: system tweaks, and scaling tweaks.

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] Reynaldinho111:
+1 Ive been stable at 1.5 for a couple days, no uv. Just eased off a little to 1.4 to see how much I can undervolt. GPU OC might be fun though. I guess existz has to do what he thinks is best for everybody though.
[Captivate Android Development] 13_:
What he said.

This kernel is ridiculous stable,fast and smooth. Current clock 1.44, 1.5 is totally stable, I just backed off a taste. 1.6 runs fine, I just didn't feel like pinning down the right UV on it to test :P

This from a phone that previously clocked 1.3 on SP#54 as a high point. All others 1.2 was the only stable freq ( not even 1100 or 900). ALL kernels crashed on this phone bad @ 1.3 or above.
[Captivate Android Development] simple man:
Good job Existz! 0.2.2 r2 is soo smooth right out of the box.	Running with Simply Galaxy.

Sent from a Galaxy far...far...away!
[Captivate Android Development] tmng95014:
+1. Good job Existz!

0.2.2R2 seems to fix the soft reboot problem. I am running on Continuum 5.6 with KC1 modem. Always clear memory after wifi or BT use.
[Captivate Android Development] Captivate2010:
Finally I fix back my phone......new cable save my day.
[Captivate Android Development] TonyStark R.I.P.:
existz, simply thank you

5VS88685LW659444M

Sent from a bank at gunpoint;)
[Captivate Android Development] H3llstorm:
Yeah, I'll probably leave things the way they are and finish this bottle of wine. :D
[Captivate Android Development] shane87:
Yep, thats right, gpu overclocking!! I am working on testing settings that works, and hopefully I will have it added to CF soon, maybe next week sometime!
[Captivate Android Development] Peaster111:
I must be in the lucky group. No issues and running at 1400 (no UV). We need it stable for all though.

GPU overclock!? Holy mother of god. Smoke will come out of my phone!
[Captivate Android Development] BigMc71:
This is a great kernel. Completely stable at 1400 and going to try higher. Only issue i have is getting my voltage max and uv settings to stick after reboots. Anyone else? I'm running continuum 5.6.
[Captivate Android Development] mrhaley30705:
If you are using the latest version of Voltage Control by Xan and it still doesn't work, try Control Freak. Don't let the beta part fool you. It works very well.
[Captivate Android Development] irishvandal:
Found a post for the SGSII camera here. It is an install pack of SGSII camera only. Hope you all enjoy.

On a side-note, I am having a slight issue of deadlock/softboots at random. Just did a fairly fresh install yesterday. Got SetCPU and Voltage control, haven't played with either. I am a total noob to UV this Cappy though. So if anybody wants to throw in some advice or a link for How-to-UV-For-dummies(me, lol), please feel free to reply or PM. Tnx in advance.

My current set-up is in my sig for any info, currently running at 1200GHz under Set-CPU.
[Captivate Android Development] mrhaley30705:
Does it happen when you have alot of windows open? toggling wifi? trying to use camera? Did it start after you installed the camera?
[Captivate Android Development] BigMc71:
I'm dumb. Wasn't saving as boot setting only apply changes.
[Captivate Android Development] mrhaley30705:
We all have moments like that occasionaly.
[Captivate Android Development] tmng95014:
Here is a good guide on OC/UV, http://xdaforums.com/showpost.php?p=10936691&postcount=1102

Enjoy!
[Captivate Android Development] Time_Zone:
Avoid using Bluetooth and TW4 and see if you still have random reboots.
[Captivate Android Development] mrhaley30705:
I thought existz put a BT fix in the 0.2.2.r2 kernel?
[Captivate Android Development] Time_Zone:
It seems that using Bluetooth causes the cpu to race for some users. Well, me and another guy at the least. I definitely did quite a bit of testing today and using BT is the culprit for me. The 1200 version caps it nicely though. I might, if I have time maybe apply Cezars BT permissions fix and test again, I could see permissions causing such evil actually. I'll definitely post my results. I can do 1500 stable if I don't turn on BT, if we get over that obstacle and the TW4 one I bet we'll have quite the winner here. The problem with the race situations is they have the potential to damage ones phone, with unpredictable results, which is what I think is of concern to existz. I'd hate to see OC above 1200 go though, it is pretty incredible.
[Captivate Android Development] topiratiko:
Realisticaly speaking....all that excess oc is really NOT of any benefit. I ran oced a while back and really only diff. i seen was higher benches....can anyone say they notice a huge diff @1.5?

As far as tw4 goes, i couldnt give that up....its smooth n crisp like hd on your phone so i switched to Existz' jvp-voodoo kernel no oc but you CAN uv :) I AM curious as to what gpu oc can do for higher end games....

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] irishvandal:
No, not really. At random. I was previously under the Zac-Talon with the 2 files, had some kind of issues that basically force my phone into a continued "Auto-Rotate" and phone calls could be made and received but would not link the connection together on either end. And I am going to SixFlags tomm with the brady bunch(my fam) so I was forced to drop the Zac-Talon until I could fiugre out if it was the kernel/rom/theme/launcher or what.

Picked up Talon 0.2.2R2 BigMem and dropped it under the hood after a complete reset. Kept the same gear as previously. Thinking it might be a TW4 deal.

It has happened in opening/closing settings not so long after a manual restart. After a few hours from manual restart in SGSII cam. Contacts. Honestly, random. Haven't been able to dup it as of yet. The wifi/bt deal has NEVER been an issue on my cappy. Other than complete ignorance, lol.

tnx, will read over this after coaster day tomm. THANKS ADDED

was shopping and in settings, closing it out to HOME, and deadlock. bt was not on and wifi was not toggled or even changed there. never had an issue with wifi/bt before.

now the TW4 launcher, you just may be on to something, didnt have this issue under the zac-talon. it seemed to like the tw4 from pauldiddy. but i see he has an updated tw4, tw4 4.5, so i will see if that changes things for the good/bad. i will throw the tw3 and tw4 4.5 in the trunk of the crappy and flash back if needed on the run.

i think he did mention it somewhere. never had an issue with it under Serendipity or Talon kernels.

Thanks again guys for the input and keep it rolling, i love to absorb it to help the next fellow down the way.
[Captivate Android Development] Holmes108:
I'm on Continuum 6, and just upgraded to TalonDEV-0.2.2R2-1200-BIGMEM-JVP... while it was loading I heard the audible message that my filesystem was being converted... several minutes in it said something about not having enough space on partition, but I didn't catch the rest of the message.

So is it pretty much safe to assume I'm just on RFS still then? Did talon/C6 convert me to EXT when I installed version 6 of the ROM?
[Captivate Android Development] mrhaley30705:
Use Voodoo Control App to check.
[Captivate Android Development] golfslicer:
FYI: The exists Talon r2 Kernel may have the charge bug. I get a full charge and take it off of the charger and drops to 91%. I turned the phone off and charged to 100% and it still would not hold 100% I flashed the eXistZ JVP-Voodoo v1.0.0 and eventually can get a full charge to hold after removing from the charger and plugging it back in several times. I could not do this on Talon r2 version. I then reflashed Talon r2 big memory version and it is holding at 100% after removing from the charger. Running Apex 7.1.
[Captivate Android Development] mrhaley30705:
Charge bug isn't kernel related, its a GB problem.
[Captivate Android Development] golfslicer:
Just stating the facts?
[Captivate Android Development] mrhaley30705:
Yes. If it were kernel related only the people running this kernel would have it. If ir were rom related, only certain rom users would be effected. The only commonality between everyone that has it is Gingerbread. Currently, the ATT bootloaders are being evaluated to determine if charge drop occurs with them as well.
[Captivate Android Development] alexige:
Running the At&t bootloaders on c5.6 and have the charging bug. Which thread are they talking about this?
[Captivate Android Development] CuriousTech:
i9000 kernels have always had worse problems with charging. There are probably hardware registers that are different for reading the charge status. That's why CurrentWidget for example will only work on kernels made for the same model.
[Captivate Android Development] schtuka:
Hey guys,

I got 2.2r running without issues, but my CWM is not recognizing kernel.... Says Unknown. Thus the Ext4 Tweaks says CF-Root kernel was not detected........

I tried to flush different versions and even go back to 2.2 and still same thing. Any clues?
[Captivate Android Development] bballer182:
I'm getting the 1440 bug on launcher Pro as well.

[edit]

Serendipity 7 build 2

[/edit]
[Captivate Android Development] watsa:
tweaks, CWM, EXT4 will no longer work as existz has changed initramfs
[Captivate Android Development] superdave69:
Thanks!

Caught your reply in the Apex thread, and yeah, that was the issue, thanks!
[Captivate Android Development] krufttangoud:
Anyone had a problem with your sound being set to almost off and you cant get it back up?

FIXED! Thanks to kodos96. Two goods wacks on the wall should fix it. LOL
[Captivate Android Development] schtuka:
Thanks man. I was worried.
[Captivate Android Development] mrhaley30705:
Voodoo control app will do the ext4/rfs conversion, or boot into recovery. It's under voodoo
[Captivate Android Development] Sqb:
Lagfix is now voodoo instead of chainfire. The voodoo control app will show lagfix options also instead of just sound. The ext4 and tweaks app are pointless now. Existz added voodoo lagfix options to the recovery menu also.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] existz:
If some of you have issues flashing certain zips in recovery, goto cwm->mounts and storage, then mount system and data..then flash zip... will correct this in next release
[Captivate Android Development] Captivate2010:
So I can delete this apps or need stay for some reson
[Captivate Android Development] LNJ:
Please don't remove the current OC values just cause some people can't get their phones stable.

I have mine running 1.5Ghz @ 1.375v for the past 2 days and I even let stability test run overnight with no issues!

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] watsa:
you can delete those apps if u plan to stay on Talon
[Captivate Android Development] existz:
Its really not just about people not being able to get higher clocks stable, theres tonnns of users who cannot do above 1.3ghz or so, and with certain launchers/apps, its causing it to scale to 1.6ghz, even if max clock is set to 1ghz... Which if this problem didnt happen, i wouldnt worry about it , people could just set max clock to whatever they want, either be 1ghz or 1.6ghz...but since it scales to 1.6ghz no matter what, this is a big problem for alot of users (theres more people who cannot hit these higher values than what there is with people who can)...so even with no OC, this makes the kernel very unstable for some users
[Captivate Android Development] LNJ:
To tell you the truth, I don't know how reliable these reports are. Since most have no experience in OC/UV.

I'm on Go Launcher and C5.6 and as long as the slider in VC is set to 1.5Ghz, I don't get the spiked to 1.6Ghz.

I did notice when I disabled UV for 1.6Ghz and didn't limit the slider to 1.5Ghz, I was getting spiked to 1.6Ghz

I doubt it is your OC code cause I've been testing it extensively and monitoring frequency scaling and it is super stable!

Please leave the 1.5 or 1.6Ghz option for the next release and a 1.2Ghz version for those not wanting to experiment.
[Captivate Android Development] existz:
No it really happens, ive confirmed it myself..actually found this out along time ago when i first started adding in 1.3ghz, this is why i never added it... TW4 is the worst, and is how i picked up on the problem.. when using it, scrolling through app drawer it runs at 1.6ghz, no matter if no OC/UV is set.. we tested this alot awhile back and never found a fix for it.. but we just didnt catch it when testing 1.6ghz... So if you use TW4 and cannot handle over 1.3ghz (which is a **** load of users) this is a major stability problem

But since Talon is used in a lot of roms, both captivate and i9000, stability is the #1 issue... I will add 1.6ghz back at some point, once its fully stable..
[Captivate Android Development] existz:
oops double post..sorry
[Captivate Android Development] LNJ:
Is it only with TW?
[Captivate Android Development] existz:
No, thats the thing..theres some other launchers, apps and games that cause this
[Captivate Android Development] LNJ:
I must be lucky that I have yet to experience it then.

I use the browser heavily on wifi and 3G and some Navigation as well.
[Captivate Android Development] Captivate2010:
I had problem yesterday my phone turns itself off and had to remove the battery to get him back. I was using this version TalonDEV-0.2.2R2-JVP.tar. Treat 1300 and 1400 but was not stable.

Install the version TalonDEV-0.2.2R2-1200-JVP.tar and I have no problem.

Another problem I had was with the Wifi every time I turned it on and off and it rekindled my phone restarted.

I'm just writing to let you know what problems, which are minor things.

Keep up good job
[Captivate Android Development] mrhaley30705:
Have you upgraded to att bootloaders?
[Captivate Android Development] Captivate2010:
no, were I can found. Please

and Igoing to use recovery mod.

thanks

edit: I foundet. thanks
[Captivate Android Development] goob1284:
Wow running my phone at 1.6 ghz never thought I would see this day!
[Captivate Android Development] nappent:
I've noticed it spiking to 1440 when I'm recording a video. Then randomly the camera app will close but no FC window is shown.
[Captivate Android Development] eep2378:
Are these different than GB bootloaders? Will Att bootloaders fix the wifi soft reboot issue?
[Captivate Android Development] mrhaley30705:
The new att bootloaders are GB, but they were made for the captivate, unlike the ones we have been using that were made for the i9000. No, they won't fix the wifi bug, not for me at least.
[Captivate Android Development] eep2378:
Ok. No real reason to flash att bootloaders as everything is working fine for me(other than wifi reboot issue). Hopefully the problem gets identified soon :)
[Captivate Android Development] ctleng76:
For me the light sensor does not seem to be working. I noticed someone else on the Apex thread also has this problem. I cover it with my finger and hold it there for 10+ seconds but the screen continues to stay bright. I double checked in the display settings and the box is checked to automatically control brightness.
[Captivate Android Development] tjarrard:
I noticed it this morning but in reverse. It stays dim and doesn't get brighter.

Sent from my Captivate running Apex 7.1 / Talon 0.2.2
[Captivate Android Development] existz:
There is a known issue with auto brightness and JVH +, auto brightness works fine on stock kernels, or stock kernels with modified initramfs (such as supercurios kernels, cfroot), since they are actual samsung compiled kernels (from newer unreleased source), but with custom kernels compiled from source (all we have is jvb source) there seems to be a nasty auto brightness bug causing it to not work at times.. Theres a DIY fix in the i9000 forum http://xdaforums.com/showthread.php?t=1130336
[Captivate Android Development] Yuna:
Trying to do mine DYI fix - now rebooting. Say after reboot how it works :)

Okay - rebooted, i will try to lower min brightness there.

Don't you know how to get smooth auto-brightness too? e.g not discrete changes but smooth, just like on froyo?
[Captivate Android Development] zerkai:
I heard it was a problem with having CRT animation prevent smoothness in brightness transitions.

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] Yuna:
can anyone confirm that?
[Captivate Android Development] zerkai:
I think I read it in cognitions changelog, I'm not sure if it relates though.

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] kodos96:
Hmmm... that sounds kind of similar to the bluetooth issue we used to have back on cf-root initram, but the switch to voodoo with 0.2.2 should have fixed that.... the next time you have this happen, could you go into adb shell, type "top" and tell me if you see a process called "rild" at the top of the process list?
[Captivate Android Development] kodos96:
Dude, just stop... seriously... you don't get any extra credit points for posting a variation on this theme on every single forum thread you participate in, and I'm sick of trying to reply to it in every single one. In case you still haven't gotten it yet, the answer to your question depends entirely on how you use your phone, and for at least some people, the answer is definitely YES. If the answer for you is "no", that's fine, nobody's forcing you to OC.
[Captivate Android Development] existz:
Next release Im going to start doing independent OC versions, as of right now im only doing 2, so dont ask for higher clocks right now ...got a few things im working on and might do it later... but there will be a 1.2ghz version (100-200-400-800-1000-1200), then a 1.4ghz version (100-200-400-800-1000-1400).. I have yet to find what's causing it to scale to max frequency no matter what max clock is set to with code above 1.2ghz, so..with the 1.4ghz version TW4 and some others might make it scale to 1.4ghz even with no OC, but if your running the 1.4ghz version there's really no point in NOT overclocking, just use the 1.2ghz version if u dont want to run any OC
[Captivate Android Development] irishvandal:
i am starting to wonder about mixing talon kernel and s7 rom. i have tried various set ups, mixed uv and oc and have feel short every time. sometime within 2hrs and sometime as long as 2days. calls being the worst issue of them all for every single try. drops not so much. the initial connections from or to seem to be the winner in this race. no real facts to hold what i say is true. just an observ. had to flash the s7 4.1 kernel while in a line at six flags, with the s7kernel and s7 rom rolling, everything was solid and stable(no fkn oc though, grrr) for a quick 24hr run till i woke today and started playing with talon again. lol.

anyone else having talon-s7 set-up problems or care to share the installation, oc speeds, uv settings that proved to be stable? feel free to post or pm.

there is my two cents.