yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] iRide113:
Also don't know what's happening.. But my statusbar clock's time is frozen. It shows the same time while the clock app, shows the correct time. If I turn the phone on at 12:00 AM, and then wait 15 minutes exactly, the statusbar still says 12:00 AM while the clock app says 12:15 AM.
[Captivate Android Development] pikachu01:
Might be a misbehaving app or something you flashed in the ROM that made it unstable.

Did you flash any hacks that hacked the statusbar? This might be something connected with your reboots too.
[Captivate Android Development] chappatti:
On Talon 0.5.2.3. Lost ability to stream Bluetooth audio. Anybody else?

Flashed Galaxian kernel, and got it back..........Any clues?

Will try to go back to earlier Talon and test.
[Captivate Android Development] geokilla:
Remember how a long time ago existz said memory leak was associated with all Gingerbread kernels or something like that (vague memory)? Well I can pretty much confirm that existz is wrong. I don't mean it in a bad way, but now that I did some testing, maybe existz can find a way to fix it?
[Captivate Android Development] existz:
Ive always said memory leak is Talon only related..., it only happens on Talon. The issue is in swap/zram or similar (which swap support is only in Talon, no other SGS based kernel uses swap support).., but using more aggressive LMK settings seems to resolve the issue (hence why it now uses new LMK settings).. We have tested this issue verryyy throughly, issue does not happen when we disable swap support, but once we have swap support enabled with zram, issue reappears.. But using Piks LMK settings, this is an alternative fix (issue should be fixed in 0.5.2.5)
[Captivate Android Development] geokilla:
So why do we need swap/zram then? It might've been discussed before, but search isn't really useful when the whole thread has hundreds of posts mentioning swap/zram.
[Captivate Android Development] existz:
Because swap/zram is def worth having to reboot daily, with zram you can use more memory without actually having to have more physical memory.., (search compcache/zram).. But the extra improvements to speed/performance and the extra memory is WELL worth having to reboot daily.. But with 0.5.2.5, Piks new LMK settings should def help with this issue.. having more aggressive LMK settings seems to keep it from happening (or atleast it mask it so end user doesnt notice it).. The LMK settings before in Talon might have just been to much with swap/zram, but Pikachu01 has had very good results with latest LMK settings, with 48+ hrs uptime
[Captivate Android Development] manny05:
My phone keeps rebooting in the middle of a call.. The first time happens 5mins into the convo.. Then the second time. Like 15mins.. Maybe. More.. It's a annoying lol i haven't Added any tweaks at all. Just keep updating to the latest talon.

Captivate running MIUI

Talon kernel/MTD

Overclocked and undervolt
[Captivate Android Development] topiratiko:
What are your oc/uv values

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] existz:
If your on MIUI/Talon MTD, this is not the right thread, this is for SGS based roms
[Captivate Android Development] Aztecbandit:
Had that problem too. Uncheck automatic in the Settings under Date and Time
[Captivate Android Development] mrhaley30705:
I don't think memory leak is just a Talon problem. I am seeing it on the Platypus kernels for MIUI.
[Captivate Android Development] existz:
Completely different things, also we are talking about SGS based rom/kernels...if I'm not mistaking alot of CM kernels use swap/zram..so this would further support my theory of it being something in swap support and/or zram ..as talon is the only SGS based kernel using swap/zram (for jvr/s/t..etc) So when talking about Samsung based kernels (Talon, Xcals, Darkcore..etc), Talon would be the only kernel having this issue
[Captivate Android Development] mrhaley30705:
I didn't know that about CM kernels.
[Captivate Android Development] existz:
Yep, also you really cannot compare SGS based kernel vs CM kernel, as CM kernel uses a different source (built off Nexus S kernel source with some drivers from Samsung merged in).., so alot of things are different
[Captivate Android Development] Sqb:
+1 on performance being worth the reboot. Thanks for all the hard work. Each release getting better. New settings holding up great after a full day without reboot

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] manny05:
I forgot to change my signature. I'm running jvr 2.3.5 dlevrom..

Can this be happening because in undervolting too much? I'm not overclocking and im using the big mem version of talon.

Captivate running MIUI

Talon kernel/MTD

Overclocked and undervolt
[Captivate Android Development] existz:
Yes, undervolting and/or overclocking is usually 99.9% always the cause of random reboots/lockups... If you have any issues, always try without any oc/uv ...if the problem doesnt happen then, then its because of unstable settings
[Captivate Android Development] existz:
So how is the new lmk settings working for you guys? Doing ok after long uptime? If they in fact prevent the issue then its about time for a stable release (pending new oc app)
[Captivate Android Development] Sqb:
Phone holding up great Existz. Thanks for the hard work. Even more so for doing all this without a cappy to even test/play with. Thanks for keeping talon alive

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] white00gt:
No issues on my side with Obsession RC3
[Captivate Android Development] Darryl Henley:
already had Thunderbolt! 1.8.0 installed on top of Talon 0.5.2.4 and it was working great. installed Talon 0.5.2.5. 2 days uptime with no lag.

Apex 10.1

LauncherPro
[Captivate Android Development] dpaik:
just flashed 0.5.2.5 on Mosaic 8...will let you know if i get any sleep deaths...it seems ok so far...maybe a little hesitation on flipping through homescreens when screen first turns on after being turned off...but awesome so far...hope it treats me better than DC's kernel
[Captivate Android Development] bkimbel:
I flashed 5.2.5 bigmem about 24 hours ago on Mosaic 8. I got 2 sleep deaths with 5.1 and M8 the day before, but so far 5.2.5 has been divine. Haven't noticed any lags, no force closes, everything running amazing. No tweaks, haven't changed any memory freak settings, no OC.
[Captivate Android Development] IDoMy0wnRacing:
I am liking it on Continuum v6.1. No issues and I am using Thunderbolt 1.8. No uv, oc 1200.
[Captivate Android Development] CuriousTech:
Smooth and stable here using bigmem @ 1200 for 26 hours so far. Although it's hard to tell.
[Captivate Android Development] aalh:
looking good here

no reboots, shutdowns, or lag 30+hours

1300 no UV
[Captivate Android Development] bkimbel:
Lag started at about 35 hours. Tried "drop caches", but didn't help. Did not try clear ZRAM. Rebooted, and it quick again. Going to convert to Voodoo lagfix now ...
[Captivate Android Development] shane87:
Anyone running the new lmk settings, the version of mf that ex shipped out with the new lmk is broken. I coded in the wrong values, and it will overwrite the new lmk settings with the old ones, so if you have used mf to change any lmk settings, you are now back to the old lmk.

Fortunately, ex let me know it was borked, and I have fixed it, pending testing to ensure it really works this time.

Also, I am fixing up an app to control the oc module, and hopefully we can have a new version with the fixed mf and the oc app out in the next couple of days.

[EDIT] The MF issue will only affect you IF you have used mf to change your lmk setup. If you have not used mf with the new kernel release, you are still on the new lmk settings.[/EDIT]
[Captivate Android Development] rlorange:
I used mf to change zram only. Will this still revert lmk settings? Ill just flash thunderbolt again

**Simply Honey 5.1 JVR rom & Talon kernel @ 1.3ghz**
[Captivate Android Development] existz:
@Shane87...actually in last release I did NOT release with the new MF you sent me the other day..., I had a private user test before I posted, which we discovered the issue...so the MF thats in 0.5.2.5 is the older (1.23b), working version which doesnt have the new preset for older talon lmk settings..not the new 1.24b with new preset

So everyone can discard Shane87s comment about MF..., the version thats in 0.5.2.5 works correctly and the correct LMK settings are being set
[Captivate Android Development] Darryl Henley:
on 0.5.2.5 for 3 days 4 hours, been listening to tune-in pro, now phone app auto closes. showing 40mb free. it's not lagging, just keeps closing phone app.

got anything you want me to test before i reboot?

edit: drop caches and clear zram had no effect.
[Captivate Android Development] existz:
Nah, that should be good... but thanks for reporting back!., as long as we make it past the 24-48hr mark with no lag, then we should be good.. other than that a reboot might be needed anyways :P
[Captivate Android Development] shane87:
Ahh, I see. I've been out of the loop a little, I guess, lol. Oh well, just disregard the part about the mf update being borked and possible consequences.

The good news is, I just put up updates to mf, and the oc control app. So as soon as ex has the time, he can roll those up into talon, and get a new release out.
[Captivate Android Development] rlorange:
**** you guys are awesome. The day the sgs1 is abandoned I feared would have already come. Thank you so much for continuing support. Talon is almost complete and you guys should be proud!

**Simply Honey 5.1 JVR rom & Talon kernel @ 1.3ghz**
[Captivate Android Development] RashaMatt:
Charge bug workaround (works for me... Please test!)

I just figured out that the infamous Gingerbread charge bug (where the Cappy starts discharging as soon as it reaches 100%) only happens for me when plugged into the original Samsung charger.

When I plug my Cappy into a cheap-o replacement charger (also 700mA) - eureka, problem solved, the phone stays at 100% indefinitely. I've verified it a bunch of times and the different behaviors on the two chargers are perfectly consistent (meaning each charger always acts consistently).

So go get yourself a cheap replacement charger and see if you get the same results...

_____________________________________

TalonDEV 0.5.2.1_1300_BIGMEM

Apex 10
[Captivate Android Development] Gromlakh:
Assuming this is correct, it sounds like your cheap charger is just constantly charging your battery, which is really bad for it. So this isn't so much "fixing a bug" as it is "not doing what it's supposed to and messing up your battery in the process." Go back to the better charger.
[Captivate Android Development] dpaik:
2+ days....no sleep deaths and everything seems ok...a little hesitation at times but other than that no fc's and errors...noice on Mosaic VIII...using 5.2.5 no oc/uv
[Captivate Android Development] goodolsen:
If you are having some hesitation or lag try Pikachu's Thunderbolt tweaks. They are working well on my phone.
[Captivate Android Development] fractaline:
how could a fellow on his phone find those thunderbolt tweaks?? ;)

<«Swyped from phone»>
[Captivate Android Development] white00gt:
http://xdaforums.com/showthread.php?t=1296927
[Captivate Android Development] Kyuta Syuko:
I don't see how the charger itself could control that. I'm pretty sure existz said something about it being controlled within the kernel (don't quote me on this...). All I know is I never really had an issue with it until recently when my original USB cable that came with my phone has started falling apart and so I got a not so cheap-o replacement that has been working wonders as well as a cheap-o replacement that I haven't really used so I can't comment on but has functioned well enough for what I've used it for which is pretty much everything else but a long charge (periodic short charges at work is what I usually use it for or to hook to my computer for adb stuff)
[Captivate Android Development] trekie86:
The kernel does control some of that but the cheaper charges can't detect the resistance of a full battery and reduce the amperage, thus stopping the phone from being able to charge. Essentially the cheaper one, although the kernel/battery are saying "no more" keeps pounding it with power. So two things are happening, you are running more electricity and your battery is being beat up.

^^^Post above should not be taken as words from an expert, just speculating on past experience.
[Captivate Android Development] markmunsch:
Phone has been up for 84 hours now and still running strong on 5.2.5. Whatever you changed is working, long time user and this is the best it has been in awhile. Thanks for the continued work guys.

As for charge bug, which I've had since the beginning of gingerbread, best thing I've found is having something drain your battery while it's charging overnight. I get emails overnight and the notification bln is enough to make it start recharging I think. When I get no emails my battery is down in the 70s, when I get 1 it seems to always be at 100. I know that's no help but just an observation I've made.
[Captivate Android Development] CuriousTech:
The AC adapter is simply a power supply, just the same as a USB cable connected to your computer or a backup battery. How much current it supplies varies, and the stock supply has a resistor on the D+/D- to denote higher than 500mAh is available so it can charge faster. The phone has a Li-Ion charger built-in which manages charging and is controlled by the kernel. Although I believe the i9000 and i897 have some differences which aren't implemented in the reorient.

A different adapter won't harm the phone or battery, but charge time will be slower with a non-Samsung adapter.
[Captivate Android Development] lospulpo:
This newest test build is running great. Flashed yesterday around noon, and of course some more testing will be needed, but this is the first time I've woken up overnight and didn't immediately require a reboot. You guys are doing freaking great. Best build yet by far. Can't wait to follow you over to the Gal Next and get Talon there as well. Since you're on At&t ill assume you're planning on getting the HSPA+ version?

Love the work. TY.
[Captivate Android Development] existz:
More than likely yes.. but chances are ill have to buy out right, so might take me awhile to save up..but galaxy nexus is my planned next device
[Captivate Android Development] reinbeau:
Widget error fixed

I just wanted to say I'm very happy with the newest BIGMEM version. Not only am I not suffering any more sleep deaths (they had just started within the last few weeks), but a widget error that was driving me crazy is fixed - for some reason one or two of my Desktop VisualizeR icons would revert to the standard icon, see below (The XDA and Mileage icons:

I installed the latest version last night, and that error hasn't happened once today. Thank you very much! Conf. #4BP60573A0078253P
[Captivate Android Development] evrionis:
Not sure this is a charger bug or feature. I have been using the same samsung charger since the beginning. I have been on many ROMs, and just installed M8 yesterday.

It is the first time I see my charger stop charging after it hits 100%. Never had this issue or feature before. It would always charge constantly. I would even hear it throughout the night sounding off a notification that it reached 100%.

How do you explain that?
[Captivate Android Development] markmunsch:
Just wanted to update, my phone has been up for over 125 hours without reboot and running strong, amazing work existz and pikachu. Whatever y'all did has made my phone work like never before. Thanks again.
[Captivate Android Development] irishvandal:
Totally forgot what to set permission to for the oc module. Can anyone help? Lol.

Exists, stock 0.5.2.5 with Bamboo run very smooth and snappy. Better together than any other combo I have come across thus far. Great work as always. Thnx.

Sent from .....a state of delusion ....
[Captivate Android Development] shane87:
If you are using a graphical interface, such as root explorer, make sure that you mount the filesystem rw, by click the "Mount RW" button at the top, and then long-press on the oc script, select "Permissions" and then make sure the file has "Read" and "Execute" permissions.

If you are using a terminal emulator, do this: (press enter after each line)

su

mount -o remount,rw /system

chmod 777 /etc/init.d/enable_oc_1200 (or 1300, which ever script you use)

mount -o remount,ro /system

On a similar note, I have an app written to streamline the oc process. I still have a few more things to tweak before it is ready for release, but its just about there. The app will allow selection of the oc level you wish to activate, and will allow you to enable it without requiring a reboot. It will also allow you to save your selected oc level into an init.d script so it will be activated at every reboot as well.
[Captivate Android Development] irishvandal:
yeah, got all that rolling as you described.

I guess the real question is, do i need to set any special permissions? Set UID? Set GID? Sticky?

Presently All permissions are checked for

Owner-Read, Write, and Execute

Group-Read, Write, and Execute

Others-Read and Execute.... Write is NOT checked

Special Permssions- NONE are selected..

Not getting OC module to show in SetCPU. Should I jump back to ControlFreak?

TermEmu is not how I would prefer it to activate. That is something I would have to redo each boot?

Thank you for the reply.

EDIT - i am copying 1200 and 1300 oc scripts to etc/init.d and have set permissions on both scripts to those mentioned above. nothing. am i supposed to move the scripts to system/etc/init.d as well or possibly only?

this is with talon 0.5.2.5 340mb. i have both terminal emulator and script manager. not understanding what i am missing.
[Captivate Android Development] fractaline:
How exactly do I create the oc script for .5.2.5?

I'm following the permissions part but not sure what to use to make the script... Tia

<«Swyped from phone»>
[Captivate Android Development] goodolsen:
Pick which one you want from the oc-scripts.zip and move it to /etc/init.d. Then reboot and it should be applied then. Or you can install Script Manager and run it after you copy it to init.d.
[Captivate Android Development] fractaline:
thanks

i was trying to find it from the xda app.......... used the browser and went to the paperclip...... duh....
[Captivate Android Development] shane87:
Ok, so the biggest problem you are having is that you only put ONE of the scripts, not both. The scripts just replace the 1ghz step with 1.2ghz(enable_oc_1200) or 1.3ghz(enable_oc_1300). They do NOT add extra steps, and it is recommended to use control freak, since SetCPU does things differently. I hope this clears up your issues.
[Captivate Android Development] irishvandal:
okay, got it working. i believe my error was i didnt apply the term emu commands. i was following all the proper steps you had described (which i was doing first). This time i applied the commands you mentioned for TermEmu and it is working correct upon boot.

next step, MF is not accepting that Talon is installed. is this the issue described in previous posts? not a big deal, i can wait for the updated Talon/MF.

tnx for the support bro.

btw, SetCPU showing correct values. I wish we could have an all in one app with the control of MF, CF, and SetCPU. But such is life, always wanting. lol.
[Captivate Android Development] shane87:
Which version of talon are you running? There was one version where the kernel version string got messed up, and didn't have "talon" in it. You can easily check by going to Settings > About Phone, and check where it says "Kernel Version." If that field does not contain the word "talon" then MF will not detect the kernel as compatible.
[Captivate Android Development] MikeyMike01:
Would it be possible to get one of these that doesn't install MemoryFreak?
[Captivate Android Development] dpaik:
you can just uninstall it...even without TiBu....but anyways...this kernel (5.2.5) ain't too great after testing it out on Mosaic VIII....granted it stopped the sleep deaths i got from DC 4.1 from occurring but there were hesitations and lag everytime i woke it up from sleep and the transition of going in and out between apps, especially task manager, was laggy and stuttered a lot. battery life wasn't too bad but wasn't too great either...battery drain during usage and sleep was pretty fast and i wasn't using OC/UV at all...i'm trying out Semaphore 1.8.2 and will compare...but so far the stutter and lag is totally gone...we'll just have to see everything else with a couple of days of use :o
[Captivate Android Development] pikachu01:
Did you try it with ThunderBolt! ?
[Captivate Android Development] mmalka:
Well, I am using 0.5.2.5 with Serendipity VII and my phone has never been better. No lags anymore, everything responding fast. Battery life has been great. I am OC to 1200, no big mem version. IMHO this is the best kernel so far.
[Captivate Android Development] melvinaury:
If you think this the best kernel. Add thunderbold script to you're configuration. Then you're going to feel the difference.
[Captivate Android Development] mpencexda:
Which version of the thunderbolt script did you use? 40/50/60.. Also did you use any of the addon scripts?
[Captivate Android Development] melvinaury:
I use the 50 version with all the addons installed. This is the best of both worlds.
[Captivate Android Development] ChikiBujia:
Hi!!!

I am not too savvy when it comes to kernels :eek:

Where can I find the Thunderbolt addons and where do I place it? in the init.d folder?

Thanks so much for your help!!!!! :D
[Captivate Android Development] Sqb:
Thunderbolt has it's own thread with all the explanations and add ons. pikachu answers all the questions. Runs great stacked on talon. Which is already a monster

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] irishvandal:
i currently use ThunderBolt-CWM i9000 v1.9.3 60MB LMK Talon.zip found here

there are a few to choose from. at the top of the post you will notice a note about the 40mb script being very aggressive, which will lead to lag issues. i am running the 60mb and cruising with no lag or loss of response at all. follow the directions and you should be just fine.

this is a nice post/reading here about oc/uv and a slew of differnet topic that may help before you ask more questions. information is knowledge.

this post here describes how to engage the oc modules in full. remember to confirm it got placed into the etc/init.d AND the system/etc/init.d folders with permissions for read and execute under both files.

not sure if this covers all of your questions, but i tried. hope this helps. if you have anymore questions, feel free to ask if you have any issues. i will try to do what i can.

bro,

Talon is overall one of the best Kernels out for the cappy world. and since the 0.4.x series it has only gotten better. 0.5.2.5 is showing the real stablity and control that the end user should expect from ALL kerenls. I was on Semaphore for one day when i flashed Bamboo 1.1 and did not care for it much, experienced the usual kernal issues without enough control to de-bug it myself. so i jumped back to Talon and de-bugged and now it all i expect from a kernel. Try and reflash, give it a day and do some de-bugging if it doesnt feel up to par. after that i am sue you will never go back to another kernel.

and curious questions, why remove Memory Freak?

just my 2cents.
[Captivate Android Development] ChikiBujia:
Thank you so much!!!!

And thanks for all those links!!!!! :D
[Captivate Android Development] studacris:
Talon has just been Chiki'ed!!!!!!!!!!!!!!!!!!

:D
[Captivate Android Development] ChikiBujia:
hahahahahahahahaha my phone subtly let me know that it was time to start asking questions instead of trying to figure out the Kernel tweaks and tricks on my own :p

Plus, I think Existz needed a bit of pink and exclamation marks here!!!! :p