yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] F1reEng1neRed:
You have to change the DHCP lease time on your router setting to something other than forever or setup a static connection to your router. For those who have this problem, these are the only known fixes at the moment.
[Captivate Android Development] kitkitfok:
I want to flash 0.5.1.5 in Darky Resurrection packages for JVT i897.

Shall I need to del any scripts/hack come form this rom?
[Captivate Android Development] pikachu01:
What hacks were done in the ROM? The kernel will attempt to wipe some known tweaks but it's best if none were there before flashing the kernel.

---------- Post added at 02:05 PM ---------- Previous post was at 01:46 PM ----------

Yes, the author didn't chmod his init.d files but people claim it got faster (after many iterations). I do wonder how they measure the performance as the init.d files are not even executed at boot. Placebo + Fanboyism?

But yes, the app_process and system_server + sqlite files did improve performance (but they were from Fugu tweaks I think)

And I did see his settings in his init.d. Some were sane but some were not. Performance gain is so, so but battery drain is bad (if the user knowingly went and chmod the init.d files after that)

And yes, removing journaling is also one point where we can gain more performance (as Adrenaline Shot does) at the risk of corruption. I myself personally experience this when I disabled journaling to test out the performance gain. Yes, the performance gain was around ~10-15% but a power loss because of misbehaving app caused my Voice Search to FC at boot. Also found that my phone will suddenly restart without warning and bootloop after that.

Perhaps I should bundle my tweaks with Fugutweak as well. :)

Yes, it works.
[Captivate Android Development] ngochuy:
Can i use ThunderBolt with this talon on captivate ?
[Captivate Android Development] pikachu01:
Can I know what your "mount" without the quotes in terminal emulator, output is like?

This determines if you can install it on Captivate.
[Captivate Android Development] kitkitfok:
I dont't know what hack/tweaks is used in Darky JVT, but I know Darky rom has some ram tweaks in his older release.......
[Captivate Android Development] pikachu01:
You can check in the /system/etc/init.d area for tweaks :)
[Captivate Android Development] vileladelima:
Questions!!

Hi, good Morning!

I want to Know the diference of the TalonDEV CWM3 to the TalonDEV BIGMEN-CWM3.

There is any huge difference? Any changes?

Other question, i can only use TalonDEV on I9000 based rom's?

Thanks!
[Captivate Android Development] pikachu01:
Bigmem offers ~13MB more usable RAM compared to non-Bigmem but it breaks 720p video recording.

i9000 version of TalonDev is in:

http://xdaforums.com/showthread.php?t=1106075
[Captivate Android Development] fractaline:
If I understand your question, yes.

You need an i897 based kernel to use with i897 GB roms.

If i'm not mistaken.

<«Swyped from phone»>
[Captivate Android Development] pikachu01:
Ooh, I misunderstood your question.

You're a Captivate user using an i9000 based ROM?

Yes, TalonDev is compatible with that. You should use TalonDev in this thread for your Captivate that is running an i9000 based ROM.
[Captivate Android Development] vileladelima:
Yes!

I just i want to know if i can use TalonDEV on i897 based rom?

Thanks!
[Captivate Android Development] Gromlakh:
TalonDEV will work on an i9000 based ROM that is running on the Captivate. So, if you see a title that includes "JVQ/JVR/JVS/JVT", or something like that, you can use TalonDEV with it.

Captivate based ROMs, though, will NOT work with TalonDEV. If the title includes "KH3/KI1/KI2", then TalonDEV won't work.
[Captivate Android Development] neubauej:
Nope.

I897 rom needs i897 kernel.

I9000 based roms need a reoriented i9000 kernel.
[Captivate Android Development] aalh:
until the sources come out, then the gurus like existz can make them work together
[Captivate Android Development] fractaline:
Oh yeah

<«Swyped from phone»>
[Captivate Android Development] irishvandal:
0.5.1.5 1200 340mb running smooth. first 24hrs.
[Captivate Android Development] Gromlakh:
MemoryFreak doesn't save

For some reason, MemoryFreak isn't saving/writing changes correctly for me. When I make changes to the hidden app settings, those save. Changes to the bottom two sliders (ZRAM/swappiness) are not being saved. If I hit "save", it says they were written to /etc/ram.conf successfully. However, if I reopen MemoryFreak, the bottom two sliders will be back to the original default settings. Hitting "apply" and rebooting gives the same effect.

I can manually edit /etc/ram.conf just fine and the settings will stick, but MemoryFreak isn't working correctly for me. I have only noticed this problem on my most recent setup, but I will freely admit that I have not been checking it lately. Generally I've been setting the sliders in MemoryFreak and not bothering to look at them again until I reflash another ROM, so I don't know if this is a .5.1.5 error, specific to my ROM, or something that's been going on for awhile.

Setup's in the sig.
[Captivate Android Development] existz:
As far as the kernel, nothing has changed (like since early 0.4.x) in regards to how stuff is saved or applied, as far as the app itself goes, i know awhile back some things were changed in how it reads ram.conf, but there hasn't been any issues since then. So my guess its something rom related, possibly busybox (make sure ur using 1.17/1.19, as 1.18 does not have runparts and scripts will not get executed
[Captivate Android Development] pikachu01:
Did you try re-installing busybox 1.19.2 from the busybox installer (stericson's)?
[Captivate Android Development] Gromlakh:
Reinstalling Busybox fixed it. Which is odd, because I had already installed the latest through stericson's installer.

Regardless, it's fixed now and was clearly a Busybox issue. Thanks!
[Captivate Android Development] mspayde:
I just flashed TalonDEV 0.4.3 OC BIGMEM. I cannot get Wi-Fi to lock. It just scans and turns off.

I am running Apex v10.1. It worked with the default kernel that flashes with Apex. The only change was this kernel. I tried the regular Memory TalonDEV kernel as well, with the same results.

Any suggestions would be great!

mspayde

------------

Infuse 4G w/Infused v2.2.3, Infusion-GB 1.1 & Tweaked with AcidTweaks v6 and MattedBlue

Atrix 4G w/CherryPi v0.7, Faux123 v0.2.0

Captivate w/Apex v10.1, TALONDEV v0.4.3 OC 1200, MattedBlue
[Captivate Android Development] existz:
Dont use 0.4.3, use latest 0.5.1.5....0.4.3 is outdated and has alot of bugs that are fixed in 0.5.1.

As soon as i come up with enough fixes for a next release, it will be 0.5.1-rc1 and will replace 0.4.3
[Captivate Android Development] irishvandal:
APEX has some WIFI issues. i had the wifi issue under 10. and 10.1 where it would try and shut off wifi. try forever and never connect. blah blah blah. But i always had the ability to lock it in trying no more than three times in the MAIN wifi settings menu. APEX 9.3 worked hella better for me personally and would jump back to that if APEX goes no further. Alot of peps over there have stated the same.

CANT WAIT TO SEE the RC. working great here so far.
[Captivate Android Development] topiratiko:
Apex 9.3 IS the BEST cappy Rom period.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Ok, so heres another binary that i made, this one will clear out swap/zram completely.. This is ment to be a last resort before having to reboot, so dont over use it...

To Install

1) extract zip and copy 'clearzram' binary to /system/bin/'

2) set exectuable permissions to /system/bin/clearzram

3) use terminal emulator or adb shell and type 'clearzram'

After you do steps 1-3, after setup all you have to do is step 3

What the binary does

In short - unloads zram module and then reloads it, clearing out swap/zram

Detailed-

- executes 'swapoff' to zram

- unloads zram module completely

- re-loads and sets up zram module

-- sets zram size based on whats set in /etc/ram.conf

-- initiates /dev/block/zram0

-- sets 'mkswap' to /dev/block/zram0

-- sets 'swapon' to /dev/block/zram0

The binary will call /bin/post-boot.d/05-zram script, this ensures that when it loads the zram module again, it sets the ZRAM_SIZE that is set in /etc/ram.conf.. Only use this when the memory leak gets bad enough to where you have to restart. I will include this binary and the dropcache binary i made awhile back into the kernel and there will be options in MemoryFreak to execute both these, but until then, just install and use as posted above
[Captivate Android Development] AdamOutler:
..

And here's a one-click

http://files.teamkomin.com/Captivate/TalonDev-0.4.3-One-Click.jar

Here's a picture of the one-click

Edit... this is officially the easiest way to get CWM on your device.
[Captivate Android Development] existz:
0.5.1-RC1 Release

UPDATE

0.5.1-RC1 Release for Captivate

Changelog since 0.4.3

new tweaked LMK settings

updated 'MemoryFreak 1.23"

updated to JVT initramfs

updated to 2.6.35.13 base

updated latest samsung source

added new kernel boot logo

disabled sched_autogroup

disabled more kernel debug

upstream fixes for ZRAM

upstream fixes for ext4

upstream fixes for mm/sched

upstream fixes for ARM/S5P

upstream fixes for rcu/TinyRCU

upstream fixes for lowmemkill driver

use 'hard float' optimizations

set usb charging lock to 100mhz

USB signal and speed improvements

introduce OndemandX CPU Governor

introduce Smartass2 GPU Governor

added sampling down factor to Ondemand

fix issue with UV not working correctly

switch to TinyRCU (smaller memory footprint)

XZ kernel compression; initramfs to none

tons of general fixes from zacharias.maladroit

Linaro Android (GCC 4.5.4) + O2 and Graphite flags

Changelog since 0.5.1.5

updated MemoryFreak to v1.23b

- Now has options to clear zram and drop_caches

NOTE

Since alot of people are still using/downloading 0.4.3, ive decided to make this next

release a RC1 release..I advise everyone to update to this version

MemoryFreak Notice

NOTICE!!! "Clear ZRAM" should ONLY be used as a

last resort to delay a reboot!! This clears all data from

ZRAM, which will cause any active pages currently residing in

ZRAM to be flushed back to RAM or dropped, possibly necessitating

data to be fetched from the NAND memory again. You have been warned.
[Captivate Android Development] goodolsen:
dl'ing now, thanks for this.
[Captivate Android Development] Sqb:
Thank you so much for the update.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] melvinaury:
Do I need to wipe the battery stats too. I remember that on previous post it was discussed.
[Captivate Android Development] Gromlakh:
I swear, between you and Pikachu, I'm totally getting my crack fix for flashing this week...
[Captivate Android Development] goodolsen:
I did, just out of habit when I flash a new kernel.
[Captivate Android Development] mspayde:
0.5.1 RC1 worked like a charm! Thanks!

mspayde

------------

Infuse 4G w/Infused v2.2.3, Infusion-GB 1.1 & Tweaked with AcidTweaks v6 and MattedBlue

Atrix 4G w/CherryPi v0.7, Faux123 v0.2.0

Captivate w/Apex v10.1, TalonDEV v0.5.1 RC1

OC 1200 BIGMEM, MattedBlue
[Captivate Android Development] melvinaury:
Best version so far. My Capy is working like never before. I'm using Apex 10.1.
[Captivate Android Development] sinichi21:
been so long since i flash a kernel whats the difference of smartass and ondemandx just want to know which save more battery
[Captivate Android Development] shane87:
OndemandX is a variant of the ondemand governeor designed to maximize battery life, at a slight reduction in performance. Smartass2 is a governor that is highly customizable, and can be adjusted for different needs.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Gromlakh:
Just flashed the new RC over my current setup. Flash appeared to go fine, but now my system doesn't seem to have MemoryFreak installed. After rebooting, the icon is gone from my app drawer and my custom "Root" folder on my desktop just has the "loading" icon for missing/no longer installed apps.

I flashed the 1200/BIGMEM version.

Problem with the zip? Bad flash?
[Captivate Android Development] irishvandal:
so we are running 0.5.1 RC1 now. and MF continues to have the clear zram function intact. i got two questions for you exists.

1. Do we need to follow the previous post concerning the scripts or is that void now?

2. Does it have the traditional Talon logo back? Going to find out in a sec, just wanting to hound you on it. lol. I miss the EXTRA tweaked look the Talon logo added to boots. Would love to know what to replace to change that out for myself. lol.

anyways, tnx as always. 0.5.1.5 1200/340 was running great, cant wait.
[Captivate Android Development] existz:
The binary for clearzram is now in the kernel (/bin/clearzram), and MF just executes it, so you can disregard the post with installing the binary..I didn't know shane87 had a new version ready or I wouldn't have posted it... and no, it uses the new bootlogo as always, only way to replace it is compile from github, new one is not in it
[Captivate Android Development] pikachu01:
You might have a busybox issue. Look at the link Android Optimization Tips in my sig (CTRL-F for busybox)
[Captivate Android Development] shane87:
I can almost guarantee that it is a busybox issue. MemoryFreak is installed via a script that is ran each boot. If you are running a busybox that does not have run-parts, it can cause this issue. Try using stericson's busybox installer (available on the market) to install 1.17.1 or 1.19.1. 1.18.4 doesn't have run-parts.

EDIT: Dang, pikachu beat me to the punch!!
[Captivate Android Development] sinichi21:
is there an app that i can use to customized it or it needs to be adjust on the compile kernel? thanks for the reply shane
[Captivate Android Development] Gromlakh:
Found the problem, since this is my second busybox related issue of the day. Obssession pre-installs a version of busybox at /system/bin, so everything was using that one instead of the stericson version in /system/xbin. Deleting the bad one solved the problem. I did a test reflash to see, and MF was installed properly on the next boot.

Thanks!
[Captivate Android Development] geokilla:
You can customize smartass? How?
[Captivate Android Development] existz:
/sys/devices/system/cpu/cpufreq/smartass2/ <--only when its the current governor, theres various sysfs files that can be tweaked, plus smartass2 has alot of tunable options via source over ondemand
[Captivate Android Development] shane87:
No problem! I really wish we could get all of the rom devs and kernel devs on the same page as far as busybox goes. If everyone would agree on a busybox version, such as 1.17.1 or 1.19.1, and install it in the same location every time, it would make things much easier.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] mikehe:
Just flashed this kernel onto my Mosaic VII Rom hoping to fix some of the lag i was having, and i have seemed to have lost the option to use the "go back" arrow on the Cappy, did i do something wrong
[Captivate Android Development] goodolsen:
Go back works just fine for me. Also, I wouldn't rely on the kernel to fix the lag issues on MVII. I tried this kernel on MVII and it was still laggy, that's why I went back to MVI.

But you might have better luck.
[Captivate Android Development] mikehe:
I to will try MVI, let me see how that works

---------- Post added at 09:17 AM ---------- Previous post was at 08:29 AM ----------

MVI seems to smoke going to stick with it , only if it would come in red
[Captivate Android Development] geokilla:
Just flash a red theme. Mosaic VII lags because of the animated drop down menu.
[Captivate Android Development] goodolsen:
Look for the dark fire theme by 10tonhammr it is the red one I am using.

Sent from Mister Red
[Captivate Android Development] mrsubway:
Just installed the 1200BIGMEM version. (I can live without the high def video) Awesome! Runs great in combination with Mosaic VII. Cappy is faster than ever, even with the animated dropdown. Talon is one of the best Kernals I've tried yet!
[Captivate Android Development] ugoff:
I've recently flashed Talon 0.5.1-RC1 on Continuum 6.1. I'm experiencing the charge issue(I've actually had this with every version of Talon past 0.4.3...). Older posts advise recalibrating the battery. So, I tried to shut down, but the phone did not turn off, it rebooted. So I put it in recovery and tried to power off from there, but it just rebooted. I pulled the battery and reinserted it and the phone did not turn back on, but it did when I plugged in power.

Is there some incompatibility between the ROM and the kernel that is not allowing this? Or something else entirely?
[Captivate Android Development] thatotherguy28:
Same here, I've been running talon on MVII for at least a week and its by far the fastest my phone has ever been, with no known problems so far. I don't think I could be more happy with it, for now anyway :)

Sent from my smooth awesome MOSAIC powered Captivate on the XDA app.
[Captivate Android Development] existz:
So thanks to Shane87, the deep sleep detection patch from Newmail now actually works correctly, when it comes out of suspend it will properly set the max clock back to whatever you have set as max, instead of 800mhz as it done in last test with it... The way the patch works is, when the phone goes into suspend, it will set min/max to 100/800, then once the phone comes out of suspend, it will set min=200mhz and max back to whatever you have set as max... Which having 200mhz set as min during runtime should not cause any issues, as most of the time when you have the screen on you are using it anyways, and with the way ondemand scales, chances are its not setting at the lower freqs anyways... I will include the new modified version of the deep sleep detection patch in the next release. If it proves to be an issue then ill revert it, but it should def help with battery during suspend
[Captivate Android Development] topiratiko:
Wont this burn more battery while phone is in use? For example, when browsing xda forums and then checking cpu spy 100 mhz is by far most used frequency(ondemandx)..with new patch it will disable 100 and it would idle @ 200 instead...is the benefit of this to disable highest frequencies during suspend?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Honestly, its not really going to make much difference, 100mhz and 200mhz run at the same voltages, plus with UV on 200mhz its going to have less than what stock 100mhz does, so battery life should not change much. Plus each time you even touch the screen it scales up, so just scrolling a page up or down scales up to max clock.. The only way it makes a difference is if you have the screen on and the phone just setting there, not touching it.. But again, theres not much difference, if any at all in terms of power consumption between it running at 100mhz or 200mhz (during use).. But yes, the point of the patch is for it to limit the max clock during suspend.. almost like the screenstate scaling scripts by Zach, but its a little different with Ondemand being modified for deep sleep detection.. Which the whole point is to limit battery use during suspend, but if 200mhz set as min during runtime proves to be a battery hog, i can always set it to 100mhz... But setting it to 200mhz during runtime should help speed things up during use, as its one less frequency the cpu has to scale, plus 200mhz runs a tiny bit quicker than 100mhz, should help with any microlag
[Captivate Android Development] topiratiko:
Makes sense. Thanks!

Would it also work with ondemandx?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Yes, it will actually work with ondemandX and smartass2, the only thing is Ondemand is just tweaked a little bit more for the deep sleep detection, so it would actually still work on Ondemand even if it was not modified

Im actually running a modified version of this patch i ported to the Inspire, running with Ondemand, OndemandX, Smartass, Smartass2, BrazilianWax, Interactive governors
[Captivate Android Development] Tweak4fun:
existz, yet another great Kernel. Thanks!
[Captivate Android Development] aznxprd:
does 5.1.2 fix the memory leak bug?
[Captivate Android Development] Nash123:
Yeah mine uses 100 mhz most of the time. 200 almost never. I don't see the advantage to limit it to 200 mhz.
[Captivate Android Development] RashaMatt:
I don't see that there's any way to answer the question of whether upping the minimum to 200 would be an overall win, unless you actually measure the differences in power consumption and change in responsiveness.

Being a software developer myself, I would say, sure, try it, but beware that you'll more than likely introduce a few subtle bugs in the process.. So maybe make it an optional beta instead of forcing this change on everyone.

Is there a way to make it user-selectable? Because that would be ideal.

____________________________________________________________

AT&T Captivate SGH-I897 build 1010, Apex 10, xcal I9000 vG3.0 kernel, KC1 modem
[Captivate Android Development] existz:
The reason yours does not use 200mhz now is because with Ondemand it usually jumps from min to max, so 200mhz is not used that much, if even at all right now... Rememeber though, with the patch it only sets 200 min when screen is on, when screen is off it sets it to 100mhz.. And when the screen is on, your 99% of the time using it, even when you just touch the screen or just swipe it, it jumps to max clock..then when you let off, it goes to 100mhz.. So, with it being 200 when screen is on, its that much shorter of a gap it has to scale from min to max.. With ondemand, it usually scales from 100mhz to 1ghz (or 1.2ghz), no in between...then when it scales down, it goes from 1ghz and might skip through some of the other frequencies.. So technically your shortening the gap from min to max, plus when its at 200mhz min, it should def eliminate any microlag there is... Trust me guys, theres really no difference at all battery wise during runtime
[Captivate Android Development] Nash123:
Ok you have me convinced. Thanks for the longer explanation ;)
[Captivate Android Development] pikachu01:
No, but it does have a "Clear ZRAM" button if you experience lagginess.
[Captivate Android Development] amtrakcn:
Hi, I did a little research on the memory over commitment and read somewhere says that setting the value to 0 still over commits memory... So I tried to set it to 2, then bricked:o
[Captivate Android Development] eliminat:
Yeah, pikachu01 had already tested that in his thread and came up with the same result.
[Captivate Android Development] existz:
Well the first steps of the oc module has begun.. there's still a little work left that needs to be done, and probably some fine tuning for voltages..etc, but initial support has been added to git (oc_module-test branch).. as of right now its only up to 1.3ghz, but once its merged in ill add 1.4ghz.. This is probably as high as ill go, as it will probably be unstable for alot of people..Unlike CM kernels..etc, the oc will replace L0 (1ghz), so 1.3/1.4ghz will probably not be as stable for alot of people because of the 800-1300/1400 gap.. But for now that's the only way I'm doing it, to keep number of frequencies the same as stock
[Captivate Android Development] irishvandal:
Couldn't you tune the mid frequencies to higher value to help comp for the gap to 1200, 1300, 1400?

Just two cents, as always.

Sent from .....a state of delusion ....
[Captivate Android Development] mrhaley30705:
Or what about dropping 800, then adding 1000 back. Just an idea.
[Captivate Android Development] pikachu01:
Recalibrating the battery only requires you to delete the batterystats.bin (or using Battery Calibration app). Not sure about your reboot issue though. Never saw it before. How did you shut down in the first place?

Umm, were you able to resolve this issue? Or is it still bricked?