yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
You might be able to talk to supercurio on #project-voodoo on IRC (freenode server)...but to be honest i don't know if he's even developing anymore for voodoo color, mainly the only thing he's still doing for SGS is voodoo sound.

If you don't use IRC or dont know how, you can goto http://talon.darkirc.info and click the IRC link, that will take you to the #suckerpunch channel on freenode server, then just type

/join #project-voodoo
[Captivate Android Development] gcamp0730:
Same thing in Apex 9.2 (JVR) with 0.4.3. And, yes, fortunately a reboot fixed it.
[Captivate Android Development] rlorange:
while waiting for the talon OC module to be implemented, you can do the exact same thing using Tegrak OC ultimate app from the market. It doesn't conflict with talon if you are careful and the couple of dollars it costs should be considered a donation for the dev who is a true kernel dev like Supercurio with voodoo sound plus which uses kernel modules injected from and app via root access... not just an app maker looking to make money.

Tegrak allows 1mv increments in voltage and clock frequencies. The only caution is to only use tegrak to control that Lo top frequency and use a standard voltage control based app to control everything else.

It's great that talon team are going to come up with their own OC module but I don't mind supporting Tegrak instead as it works flawlessly with talon and allows finger control than talon OC module will be capable of when it's released. Bumping up internal voltage by just 10mv allowed me to drop the core voltage by 45 mv at OC speeds of 1.4+

impressive stuff.

**Simply Honey4.0 JVP, Talon kernel & Tegrak OC app 1.38ghz@1335mv**
[Captivate Android Development] Szighy:
Can somebody please tell me what were the defaults in memory freak?
[Captivate Android Development] tmng95014:
@existz, I lost Memory Freak bin from my phone. Please let me know where can I retrieve a copy. Thanks.

EDIT: I got MF from shane87. Thanks!
[Captivate Android Development] IDoMy0wnRacing:
LMK was: Talon

ZRAM was: 256

Swappiness was: 90

** if you select Talon for the LMK settings, the option to "Reset to Talon Default" button will appear.
[Captivate Android Development] shane87:
Reset to Talon Default ONLY changes zram setting back to Talon default. The swappiness and lmk set are NOT affected!

And yes, talon defaults are:

LMK >"Talon"

ZRAM > 256

Swapiness > 90

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Szighy:
Thanks for both of you...
[Captivate Android Development] mrhaley30705:
Ok. I unplugged this morning.to 86%. That is not the strange part. The battery voltage showed almost full. 4191mV is an absolute full charge on my phone. It showed 4183mV when unplugged. Normal?
[Captivate Android Development] tmng95014:
I think something is wrong with battery stats. Time to recalibrate...
[Captivate Android Development] topiratiko:
Off topic. Did u get another cappy? Last time i saw you was on a farewell cappy post

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] watsa:
see toldya. You are being followed :D
[Captivate Android Development] Kyuta Syuko:
I'm not sure what's causing it or why it's happening, but the brightness on my phone keeps changing or reseting to the default brightness. I usually notice it when I pull it off the charger, but I'm not 100% sure that it happens while the phone is charging.
[Captivate Android Development] MaxRabbit:
I am experiencing abrupt reboots during phone calls. It's my only problem. Does anyone have a suggestion to fix this?

Thanks!
[Captivate Android Development] existz:
What version are you on?
[Captivate Android Development] mrhaley30705:
Me? Sure you doing have me mixed up with mcord from miui thread? I have commented in a couple if those, but I still have (and love) Captivate.
[Captivate Android Development] mrhaley30705:
New batteries here today, think I will hold off a day or two.
[Captivate Android Development] topiratiko:
Dude your right. It WAS mccord. Lol. That dude was a helpful sob. So are u and names start with a m so hence the confusion

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] mrhaley30705:
@top

Thanks, I think?

@existz

Remember that strange flicker I kept telling you about, when screens are transitioning? I've taken a break from MIUI, and while on a Samsung room I noticed that it didn't start again until I converted to EXT4. Ran rfs most of the day and no flicker.
[Captivate Android Development] geokilla:
Hrm. My phone is charging at 1200Mhz. It doesn't drop down to 100Mhz or Deep Sleep while charging. No wonder it's been taking forever to charge lately.
[Captivate Android Development] mrhaley30705:
You tried reflashing? That's not normal.
[Captivate Android Development] geokilla:
Yea I'm going to try that soon. Just gonna wait till it gets some battery first. It was fine before.
[Captivate Android Development] Kyuta Syuko:
Did you flash anything recently? Like say the USAS Tweak formerly known as Acid Tweaks?
[Captivate Android Development] geokilla:
Nope. Flashing nothing. Well nothing that is related to Talon. Maybe an Apex theme or modem, but that's about it.
[Captivate Android Development] MaxRabbit:
I am on 0.4.3 BIGMEM non-OC.
[Captivate Android Development] watsa:
I think 0.4.3 had a problem where you might get reboots during phone call when your battery is below certain %. You may want to upgrade to one of the latest test builds
[Captivate Android Development] pikachu01:
That is correct. It was fixed in 0.4.4.8 or 9 (I forgot). 0.4.3 will face reboots when battery is low when in call. 0.4.4.22 is the latest test version that is actually more stable than 0.4.3 itself.
[Captivate Android Development] edtonn:
+1 and +1 version 0.4.4.22 has been very stable (and lag-free on Nexus S LMK settings) for me since it came out
[Captivate Android Development] existz:
I highly recommend anyone on 0.4.3 to update to 0.4.4.22 if your having any issues..well, even if ur not, .22 is better all around. Also, conservative governor is added as an add-on for those that want it, but ondemand/x is recommended,... so if u don't know what it is, or what it does, stick with kernel default ondemand ..
[Captivate Android Development] tmng95014:
+1 have been using 0.4.4.22 for a while now with Continuum and very happy!
[Captivate Android Development] existz:
I've only made 3 small changes to the source since last release, 1 just is to clear up a small compiler warning, the other 2 just fixes some cflags for hard float compiler optimizations and the other reverts the mass storage speed hack (seems to slow read/write down instead of making it faster).. once i get enough changes to make up a new release, ill release 0.4.4 as a stable version, that way we can get most people off of 0.4.3.. just bare with us, not much going on atm
[Captivate Android Development] MaxRabbit:
Thanks guys. Upgrading now. Just one more question: what're the "Nexus S LMK settings"?
[Captivate Android Development] pikachu01:
Look at the app MemoryFreak. You can change the LMK settings there.
[Captivate Android Development] pikachu01:
I forgot to post this in the captivate section.

I have posted a modified version of Zach's init.d scripts that work well for Talon.

Try it out and let me know if it works well.

My Memory Freak settings:

Hidden App Size - 48

ZRAM Size - 160

Swappiness - 50

http://xdaforums.com/showpost.php?p=17400617&postcount=3147
[Captivate Android Development] MaxRabbit:
I've been having the problem with Memoryfreak being blank. I downloaded the Busybox installer and installed it to /system/xbin and rebooted--no luck. Based on another suggestion, I deleted my ram.conf and installed Busybox to /system/bin.

After multiple reboots, my ram.conf has not come back. I do have a "/bin/ram.conf.default."

How do I get ram.conf recreated?

Edit: Solution was simply copying ram.conf.default to /system/etc and renaming to ram.conf. Also installed busybox to /system/xbin as well.
[Captivate Android Development] pikachu01:
Busybox 1.17.x? And you need to remove all other instances of busybox (sbin and any other paths in the sdcard comes to mind)
[Captivate Android Development] MaxRabbit:
Yes, I did that.
[Captivate Android Development] pikachu01:
Come to the chatrooms #suckerpunch webchat.freenode.net. I'll troubleshoot it with you.
[Captivate Android Development] Kyuta Syuko:
Alright for my brightness change issue it does happen when I pull it off the charger which I have plugged into an outlet.
[Captivate Android Development] iXNyNe:
So far so good. Not noticing any real differences yet but I haven't put my phone through anything really.

Note my sig shows other stuff I'm using (including usas tweaks)
[Captivate Android Development] Kyuta Syuko:
You have the full USAS tweak installed? Or just the non-script files? I remember someone having just the non-script files installed...
[Captivate Android Development] iXNyNe:
Sas includes tweaks, usas does not, I have usas.
[Captivate Android Development] Kyuta Syuko:
I see. Well the USAS does include the one mount tweak that turns off journaling and what not. I wonder how well Zach's/pikacu's tweaks will work with SAS. Granted I thought VM Tweaks were a no-no with TalonDEV...
[Captivate Android Development] pikachu01:
VM tweaks are related to memory/RAM. If you set something that conflicts with ZRAM/Swap, you'll get worse off performance than when you didn't set it.

The kernel itself has its default VM settings (That by itself is setting the VM setting right?). What Zach's script does is to tweak that (based on Talon's default to make sure certain conditions are met that doesn't conflict with the ZRAM/Swap configuration.)
[Captivate Android Development] Kyuta Syuko:
Yeah I know the kernel itself has its own VM settings which is why I thought it was a no-no to have anything else that messes with them. Granted my main concern is if Zach's tweaks + SAS will cause my phone to decide to bootloop or something... Wish there was a way to modify only the init.d directory in Recovery...
[Captivate Android Development] dsmitty166:
Nice, just flashed I will try it out!
[Captivate Android Development] joeshmoe08:
Nice update exist. Also just curious on your opinion of the battery bug in JVB. Do you think it is a kernel problem or do you think it has to do with the rom itself?
[Captivate Android Development] keitht:
Flashed and running great so far.
[Captivate Android Development] CuriousTech:
So far it looks like the sleep power drain issue from 0.1.3 is gone.
[Captivate Android Development] dsmitty166:
Working great so far!
[Captivate Android Development] joeshmoe08:
crossing my fingers but i doubt it is solved. nothing was done to solve it and it usually happens randomly for me on random chages. Apparently the charge thing is supposed to be a "samsung feature".
[Captivate Android Development] existz:
The "charge issue" is something from Samsung, it happens with any kernel or rom..I'm not sure if it can be fixed or not
[Captivate Android Development] keitht:
It must be fixable, not saying by you, but it is a big problem. The problem is that the battery drains fast when it occurs while plugged in. Much more than if you manually watched it hit 100% and pulled the plug.
[Captivate Android Development] existz:
Ive seen some say to switch wifi sleep policy to never instead of when screen off (or vice versa? ) dont remember...nor have i tried it..some says it helps..but im not sure about it..just something i read..you know how that goes around here :P
[Captivate Android Development] Rodman101:
Will higher Oc/Uv be available in the future such as onix's 1.6 ghz?
[Captivate Android Development] joeshmoe08:
exist said yes but not a priority right now
[Captivate Android Development] silent.bob:
I have read that is speculated that the phone charging enters a discharge state when the phone is on charger and hits 100%. The phone discharges itself then stops to recharge. This has been said to be the reason why some drop a few % when on froyo after pulling phone on charge. Some say its to prevent over charging and reduce the likelihood of burning up the battery.

Now skip to the current issue. What is the possibility that this issue is due to that same discharge state either not stopping to allow the phone to recharge, or that the recharge doesn't kick back in causing it to continue to discharge.

I personally don't know enough about the werkings of the phone and os to a great degree, but this does sound possible.
[Captivate Android Development] existz:
Thats what I think it is...but i dont know for sure..to me it seems like once its gets to battery full state (97-98..etc like froyo), it quits charging and once it drops down to a certain percentage, it should kick back in and start charging again..but of course for some its not kicking back in..mine does not drop below 91% or so then it kicks back in, but theres some that report that it never kicks back in and when they unplug the charger it drops to the 80s.. But i think its the same logic that was in froyo, but for whatever reason its just not kicking back in
[Captivate Android Development] joeshmoe08:
Well maybe... but that doesn't explain why it consumes more battery while connected. What I mean is I have ~1% battery drain per hour. So even if the phone was stopped charging the entire night (8 hours) after 100 I would be at ~90%. That is not the case. Whenever the battery bug occurs I am at like 80% so it mean that after the phone hits 100% it purposefully sucks battery. Thats just my take.
[Captivate Android Development] silent.bob:
My theory is that the "discharge" cycle would consume a few % an hour. Like 3 to 5.

Ex, is there some kind of logging that could provide that level of details as to the charging?
[Captivate Android Development] mrhaley30705:
Sounds crazy, but if you can do without Maps for a few days,try uninstalling it. My battery drain seemed to go away after I did it. If it doesn't improve, just re install from market.
[Captivate Android Development] JWallstreet:
Running GR-10 with Talon 1.4. Converted to Ext4. Running very well. Getting a quadrant score of approximately 1888 - 2010. Linpacks around 16.0 - 18.0.
[Captivate Android Development] froli13:
Come on guys, stop asking for higher OC states. If your phone is not fast enough at 1200 then your phone is not working properly or you are playing 2 games at the same time....

Even at stock frequencies my phone is faster than froyo at 1200...
[Captivate Android Development] existz:
Ill say it one more time guys...as of right now its just about the development, once everything gets fully working and we get everything we want added in and working, then once it gets to being just about features, then ill probably add in some higher steps..but until then, im just focusing on getting everything added in and fully working..we have to start fresh with everything and make everything work again, so its going to take time to get everything added back that we had in froyo..plus some new additions.. /end of topic!
[Captivate Android Development] froli13:
I think this should be added to OP. ;)
[Captivate Android Development] iXNyNe:
Full sas isn't recommended with talon (or for that matter at all unless your device is galaxy s 4g, in which case you wouldn't be running talon ...)

If you have full sas installed I recommend removing it and just using usas.

Also as I said earlier I have Zach/pikachu tweak and usas both installed, no bootloops here, but not yet noticing a real performance difference. Things are nice and smooth as always.
[Captivate Android Development] pikachu01:
If it bootloops, go to recovery and do an adb. After that, delete those files. From what I see in the scripts, there's nothing on it that could cause a bootloop as these VM settings are meant to be changed on the fly.

SAS tweaks may conflict with Talon's own VM settings as they are not based on Talon's default settings. They may run without problems, but you might experience microlags from memory trashing or inefficient swapping.
[Captivate Android Development] Kyuta Syuko:
Yeah I modified the SAS tweaks and removed the VM settings. Might compare the two tweaks and remove from SAS what's being modified by Zach's and then push the remodified SAS with Zach's.

Was browsing Zach's tweaks and noticed under

TWEAKS: MEMORY SETTINGS for general operation + zcache/zram usage

at the top it has its explanations of a few of the settings with I guess examples and then down below it's actually setting some of them, but the

echo 0 > /proc/sys/vm/laptop_mode

in the "explanations section" isn't commented out so it's being set twice. Not that it hurts anything I'm sure. I was just curious if it was just something that was missed or if there was a reason for it.
[Captivate Android Development] pikachu01:
That is a typo there. It sets the same settings, so its no biggy. I'll let Zach know about this :)

Thanks!
[Captivate Android Development] Geezer000:
Any fix for this yet. I get it as well.
[Captivate Android Development] topiratiko:
Experienced 2 reboots under 20% today on 4.22

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shane87:
I am not sure as to whether or not the autobrightness on i897 is smooth, as I never use autobrightness. However, on the cog5 features list, it mentions that the tv-style screen off animation will cause autobrightness to make noticeable jumps, instead of smooth transitions.

As far as the rapid switching between brightness levels, I have never seen it, again I don't use autobright, but have you checked to see if the ambient light sensor is dirty/dusty? I have my cappy in an otterbox, and it is bad about catching dust around the ambient light/proximity sensors, which causes dificulties durring calls, i.e. the screen will stay disabled even after I pull the phone away from my face. Maybe the rapid brightness switching is caused by a similar issue?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] pikachu01:
Logcat? You should have a window to get a logcat out before it reboots.
[Captivate Android Development] iXNyNe:
My light sensor seems fine, no scratches or dust on it, so I don't know what's triggering the rapid switching.

Is there an easy way to disable the screen off animation so I can test if it solves the issue?
[Captivate Android Development] reinbeau:
I don't know about that, I've had that flicker long before I ever had the CRT animation on any ROM. With my current configuration (Serendipity VII and this kernel) I'm not seeing it at all.

Sent from a state of Serendipity
[Captivate Android Development] shane87:
I'm not sure myself, as I NEVER use autobrightness, I stay at 0, with a widget to change it if I need to. I do know that the OP of cog5 says "Enabled TV Off Animation (Removes smooth brightness transitions)"

And to remove the tv off animation, I think you would have to flash a different services.jar. I remember when I first came to i9000gb, the package I used came with a cwm flashable package to enable tv off animation. However, there was no disable package.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] ngochuy:
JVS has been released. Do u have any plan to build talon for this?
[Captivate Android Development] iXNyNe:
@existz

Here's another mod I'm curious your opinion about :)

http://xdaforums.com/showthread.php?p=16612294#post16612294

So I'm wondering, does this method seem safe and efficient? And if not (or even if yes) is there a better way to accomplish the resulting outcome this mod provides?

P.s. I know this is off topic to talon so I'm sorry in advance, and this question is open to anyone, I've just noticed ex seems to know his stuff so I consider him a good person to ask.
[Captivate Android Development] Kyuta Syuko:
That tweak only changes the Cache size so the Market won't throw that "insufficient space on device" error at you when you try to download a large file. Should be fine to use with TalonDEV. Was thinking about trying it out myself after someone else had pointed me to it. I wonder if it'd let me download that 50Mb game I want...
[Captivate Android Development] johan8:
You're right.

That mod is create a 54.5MB virtual partition in /data/local then mount it as loopdevice to /cache.

By default /cache is just 30MB in GalaxyS, so it maybe problem if download app bigger than 30MB from market.
[Captivate Android Development] Kyuta Syuko:
Yeah most people know you can't download anything over 30Mb from the Market on our Capys, but you're saying with this script we should be able to download up to 54.5Mb sized files from the Market as I understand the point of the script to be?
[Captivate Android Development] Kyuta Syuko:
Going through the tweaks to modify the SAS to not modify any of the settings I noticed the build.prop tweaks. Do the two HTC lines really help our phones any?

setprop ro.ril.htcmaskw1.bitmask 4294967295;

setprop ro.ril.htcmaskw1 14449;

Also the 2G security tweak I think was written wrong.

# =========

# TWEAKS: optimized for 2G security [not sure if it works]

# =========

ro.ril.enable.gea3=1

shouldn't it be

setprop ro.ril.enable.gea3 1;

like the rest of them?

Also noticed the next three settings threw in the = sign.

setprop ro.ril.def.agps.feature=1 # also default ?

setprop ro.ril.def.agps.mode=2 # default value

setprop ro.ril.disable.power.collapse = 1
[Captivate Android Development] sremick:
I'd rather not. :P

I recall you didn't want to release 0.4.4 final until you had fixed the memory leak for good. How's that going?
[Captivate Android Development] existz:
Anyone on JVS that would test a new test build out for me, please msg me..just need to verify wifi is working ok
[Captivate Android Development] dkucera:
would love to who has a jvs rom?
[Captivate Android Development] existz:
There's a few in i9000 forum
[Captivate Android Development] existz:
So, if all goes as planned, ill hopefully have 0.5.1.1 public test up tomorrow.. Ive bumped up the version to 0.5.x since its JVS based. Other than that ive reverted the mass storage r/w speed hack and fixed some cflags for hard float optimizations.. so nothing major, just an update for JVS
[Captivate Android Development] aobmax:
Trouble with fasty rom

Sorry, noob here. Is this kernel compatible with GB fasty rom? I flashed 0.4.4 and now I am having boot loops.
[Captivate Android Development] watsa:
Nope. Only boog kernel is for KH3 roms. This is for I9000 roms like JVQ, JVR
[Captivate Android Development] aobmax:
Thanks, flashing back now. Is there any voodoo kernel compatible with GB fasty? My gps signal improved alot with this rom but now I really need voodoo sound&color.
[Captivate Android Development] apparition:
Nope.

Fasty II is KH3 based, and boog321's kernel is the only kernel for KH3. I suppose once they release the source, ppl can get some voodoo magic on it, but for now......:confused:
[Captivate Android Development] watsa:
No there is no KH3 kernel that has voodoo sound/color injected into it.
[Captivate Android Development] aobmax:
Ouch...I just flashed fasty again and it's now stuck in at&t boot screen....sigh lol gonna spend some time to revert it i guess
[Captivate Android Development] watsa:
you need to disable lagfix first
[Captivate Android Development] aobmax:
Is there any other cappy rom with great gps signal other than fasty?
[Captivate Android Development] watsa:
Wrong place to ask. Also no ROM will give you a GPS working guarantee. Captivate GPS cannot be trusted
[Captivate Android Development] alexige:
Unfortunately he's right, wish my job wasn't occasionally reliant on it.
[Captivate Android Development] aobmax:
alright...my bad. Well once I disable lagfix in cmw. it says right now it is enabled but will be disabled next boot....what should I do now?
[Captivate Android Development] watsa:
let it disable lagfix. Once done u will get bootloop again. Pull battery out and reboot into recovery. Flash KH3 rom.