yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Kyuta Syuko:
I'll admit I rarely use my phone as a phone and more as a handheld PC so with the exception of data/wifi I don't pay too much attention to the quality of the modem I'm using. I will say that I've as of yet to try a modem (that supports 850 by default) that just didn't work at all. Never really paid all that much attention to signal strength and call quality so they all seemed about the same to me...
[Captivate Android Development] iXNyNe:
I'm in a similar boat. I could care less about voice quality, and sending text is nice, but my real concerns are definitely data speed and battery life. For those reasons I try out modems a lot.
[Captivate Android Development] geokilla:
I just choose whichever is the latest. whatsa and I both live in Toronto and he prefers KC1 haha. Honestly, I can't tell the difference between modems.

Edit: I used OndemandX today in an effort to conserve battery life because I was doing a one day shopping trip to Buffalo and Niagara Falls and started with only 80% battery life. I'm never using OndemandX again. It caused my phone to reboot multiple times when typing out a text message or trying to multitask, and when I was streaming BT audio to the car and I receive an incoming call, the phone just completely hangs causing me to miss the call. I was driving too so it's not like I could play with the settings either. Luckily my sister was with me so she could call with her Samsung Wave. I never had this problem when using Ondemand.

According to control freak, here are my time in states:

1200Mhz (1225mV) = 17 minutes (2%)

800Mhz (1125mV) = 8.5 minutes (1%)

400Mhz (975mV) = 5 minutes (1%)

200Mhz (875mV) = 2.7 hours (20%)

100Mhz (850mV) = 30 minutes (4%)

Deep Sleep = 9.7 hours (72%)
[Captivate Android Development] Dungeon47:
Call quality is only important to me so far as we can understand one another. Beyond that it is speed and battery. Does anyone know of a list of modems by region? I would like to see weekday works best for others in my area.

Sent from my Android using the power of Greyskull.
[Captivate Android Development] Wdustin1:
there is a thread in the general section where somebody made a website and they got like 60 modems, and they got a google map where people have tagged the areas where different modems work the best

Treading the waters on Fasty 1.7
[Captivate Android Development] iXNyNe:
Hmm sounds fun, ill go look, can you link to it here though?
[Captivate Android Development] shopealope:
I'm using talon 0.4.4.22 on my phone with apex 9.2 and I love it, its been very stable for me. I'm oc'd at 1.3ghz with tegrak and it all runs great. No random reboots or anything. I'm a build 1012. Great work, keep it up man.

Sent from my Captivate :D
[Captivate Android Development] aryn.galadar:
Modem link

http://xdaforums.com/showthread.php?t=1227717
[Captivate Android Development] whyareyou:
Can this kernel be used with UCKH3 and a I9000 modem like JK4?
[Captivate Android Development] Rrryan2:
Probably. But you'll probably lose audience chip by doing so, which sort of begs the question, "Why would you want to?"
[Captivate Android Development] bigbooty:
Why would you do this?
[Captivate Android Development] Kyuta Syuko:
I'm pretty sure I9000 based kernels will only work correctly with I9000 based ROMs.
[Captivate Android Development] mrhaley30705:
This kernel can be used with i9000 modems with no ill effects, other than losing audience chip support. I don't think (pretty sure) you can use this kernel in the KH3 ROM. Trying to do so will most likely cause a boot loop.
[Captivate Android Development] Rrryan2:
Right. But he's talking about swapping both modem and kernel to I9000. Such a combo would probably work ok, it just doesn't make much sense to do so.
[Captivate Android Development] mrhaley30705:
The kernel won't boot up.
[Captivate Android Development] whyareyou:
Thanks for all the response guys. I was asking because it was fairly common in Froyo days to use Speedmod/Firebird kernel with Captivate based roms. The downside being you lose audience chip and bluetooth and on the upside you get HSPA speeds, Voodoo Sound + Color etc. Agreed you can just as easily switch to a I9000 rom + kernel + modem combo. I like complete stock look and was just looking at various options.
[Captivate Android Development] mrhaley30705:
If you think back to froyo, that was possible after source was released for it. Don't have Captivate GB source yet.
[Captivate Android Development] RashaMatt:
Stericson (author of BusyBox for Android) asked for feature requests, so I asked him to add run-parts.

He said he'd add it today :-) With any luck then, all that will be needed to resolve these pesky BusyBox/MF issues will be to just update BB from the market, uninstall old copies, and install the LATEST version of BB.

____________________________________________________________

AT&T Captivate SGS I897, Dlev ROM 5.0, TalonDEV 0.4.4.22, KC1
[Captivate Android Development] iXNyNe:
@existz

Any opinion about this?

http://xdaforums.com/showthread.php?t=1246883

Anything in there seem like a major no-no or any potential compatibility issues with talon?
[Captivate Android Development] existz:
i highly recommend not using it .., atleast the tweaks script.. it changes alot of settings that could have bad side effects with talons memory management and swap setup..havent really looked at anything else in it so i cannot comment on those.., but the same probably goes for it also.. However the no-journaling on ext4 is fine, but i only recommend on /cache partition for better chances of no corruption.
[Captivate Android Development] iXNyNe:
So far its running very well for me on apex 9.2 with talon 0.4.4.22. Ill try both with and without their tweaks script. I don't know enough about the rest to tell what is or isn't safe but there seems to be some really good benefits as far as I/O goes.

Edit:

They have two files with tweak in the name, and they both seem to have more than just memory tweaks. I know this is asking a bit but if you have the spare time and wouldn't mind pointing out the specific lines that clash with talon it'd be great to be able to run these tweaks with talon. Otherwise if there is a way to make talons settings override the acid tweaks settings (doesn't unit.d run by order of filename in some way?) That I'm sure would save some time.
[Captivate Android Development] oblivianz:
Is memory leak problem still occurring on this kernel? I had to switch to Dark Core cos of it but would love to change back!
[Captivate Android Development] existz:
Yes but its not near as bad as it originally was.. plus you can use memoryfreak to adjust memory management on talon to where its not as bad, doesn't fully resolve it, but some say it helps. ..worst case just reboot once a day and ur fine
[Captivate Android Development] Kyuta Syuko:
I'm also playing around with it. I am in no way a Dev though I have dabbled in programming (C++ and some ASM) and random scripting (pre-Lua eAthena, mIRC) so I'm not totally in the dark about this stuff. The 06Tweaks file is the one that sets all the various mem/swap settings while S98edt_tweaks tweak the scheduler settings. There are however a few lines in the 06Tweaks file that tweak scheduler settings as well though I'm not really sure what they do.

It also adds/replaces a few files to/in the system/bin and system/lib directories that have me wondering their purpose.
[Captivate Android Development] existz:
Yea from the little ive even looked at it, 06Tweaks script is the main one that should not be used, or atleast all the swap/lmk/vm settings be removed.. Its not just it will conflict with Talons settings, its also going back to the rule of thumb to not have more than one thing, in different locations, setting the same thing.., this can cause conflicting results and possibly lead to higher battery consumption and/or degrading performance.. Most of these type things are already tweaked in Talon, atleast as much as it can be..(lmk/swap/vm settings wise) ...also depending on the scheduler you use, the scheduler tweaks will have no effect (ie.. sio/vr/bfq..etc)...most of these tweaks are geared towards more of stock like type kernels that use stock kernel default settings..so its probably best used with kernels like Xcals, Darkcore..etc..etc.. instead of Talon where its already tweaked and various things are setup around it..such as our lmkset, zram settings..etc.
[Captivate Android Development] IDoMy0wnRacing:
Boot and shutdown sounds.

With all of the work that has been put into this kernel;

An additional bonus (that you all should be credited with) is the ability to create custom boot and shutdown sounds.

For the boot sound: Create a .wav file. Rename it to "PowerOn.wav". Place it in /system/etc/

Should read: /system/etc/PowerOn.wav

** bootanination sounds are limited to 10-ish seconds.

For shutdown sound: Create a .wav file. Rename it to "PowerOff.wav". Place it in /system/media/audio/ui/

Should read: /system/media/audio/ui/PowerOff.wav

Custom boot animations work wonderfully also.

Place your bootanimation.zip in the /system/media/

Should read: system/media/sanim.zip

Remember when making a boot animation file; it is a .zip file, it is named: sanim.zip, and the .png's CAN NOT be compressed to work.

Reboot the phone and enjoy your BootAnimation with sounds.

If you would like boot or shutdown sounds removed, simply remove, rename or delete the before mentioned .wav files from their location.

To eXistZ and crew.

Thanks for all of your hard work. It is truly appreciated.

Confirmation number: 399441387T860770G
[Captivate Android Development] shane87:
Okay, so seeing this talk of these tweaks, I decided to look into them. I just gave them a quick scan, and, from what I can see, there is very little that is beneficial to the Talon kernel. Before anyone mistakes me, I am not trying to say the tweaks are useless, they look pretty promising for a stock-type kernel. Just with all of the tweaking that ex, kodos, ytt3r, zach, and any other talon devs (there are so many now that I loose count, lol) have already added to talon, these tweaks would have little effect. I mean, the lmk/kernel/vm settings are a no-no, since setting different values in different places almost always leads to trouble. Also, the settings disable swap, and change some of the beneficial tweaks that the talon devs have worked up.

A couple intriguing things, though, are the two executable binaries in /system/bin, system_server and app_process. They have been ported from honeycomb, according to the op. Unfortunately, the op does not mention what they do, and I have not had time to do much research.

Also interesting are the hexedited sqlite modules, included in /system/lib. According to the op, they were ported from cm7 and increase io speed, but nothing is said about what was acctualy changed in the sqlite modules.

Personally, I think these tweaks would be beneficial on a stock-type kernel, depending on the users typical use pattern. However, for talon, most of the tweaks are already incorporated into the kernel, and are tweaked for talon's unique setup.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] psych0phobia:
During all this talk, yesterday, I repackaged the tweaks to include only the items mentioned above, along with the updated zip-align script. No ext4 or other init.d modifications. While I have no doubt there is some kind of improvement, I cannot tell the difference empirically.

I'm using Apex 9.2 and Talon 0.4.4.22.
[Captivate Android Development] Kyuta Syuko:
Actually the LMK/VM settings get changed in two locations in the 06Tweaks file. In the first location four or so settings are set/changed which include Swappiness being set to 0, but a little further down those same settings get changed again along with one or two others and Swappiness is set to 60. I questioned the OP about it with no response, and according to the header in the 06Tweaks file the OP was the one who made/tweaked it. Can't say for sure what, if anything, is doing it but my phone does seem a bit smoother...
[Captivate Android Development] pikachu01:
I have a feeling that the script was Kanged from a lot of sources into one file with the author not knowing what those tweaks are doing. Best to cherry pick the tweaks and use it only when you know its beneficial. A quick google will suffice (as well as some statements Existz posted here about LMK/Swappiness)
[Captivate Android Development] topiratiko:
I deleted 06tweaks file....also anywhere in other files that listed cfq i changed to vr (someone advise) runnin great and over 2800's on quad no oc

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Kyuta Syuko:
As far as I could tell from my limited knowledge changing all instances of cfq to anything won't really have much, if any affect other then setting the Scheduler on boot. At least that's what it looked like to me, but like I said my knowledge is very limited so I could be wrong.

One strange side effect some people are noticing is that their phones will idle at or near max speed while charging thus causing them to charge slower.
[Captivate Android Development] existz:
Greatly appreciated kind sir! Thank you

Just a little update incase you guys are wondering.. the reason there hasn't been much activity lately is because ATM I'm without my Captivate, i should be able to get some work done here shortly. I'm shooting for a RC1 release for v1.0, or at the least a 0.5.x build in the next release, 0.4.4.22 seems to be very stable, and basically waiting to release an update until the memory bug is fixed or atleast contained to a point where it does not effect much. So without a device I'm unable to trial and error it to test various things.. but just so you know, development has not stopped, nor will it..we will always continue to build for SGS...so just bare with us, updates will still come
[Captivate Android Development] nappent:
Ok i installed the tweak and it does seem to run faster but battery usage is higher. How do i uninstall this.
[Captivate Android Development] Kyuta Syuko:
Just delete all the files in the system/etc/init.d directory. Not sure if deleting the other 4 files in the system/bin and system/lib directories will cause problems or not...
[Captivate Android Development] topiratiko:
Thank you!

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
@existz

I took your advice and removed some things i felt would contradict talon settings, but i left some things that seem beneficial. Whats your opinion, should i remove any of the files i left?

*uploading pics now

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] visionlogic:
I also had a non-working Memory Freak. I followed all the steps in shane87's post, rebooted, and no ram.conf was created. I reinstalled the talon kernel, rebooted, still no ram.conf was created. Finally I used root explorer to copy ram.conf.default from /bin and pasted it into /system/etc, then renamed it ram.conf. Memory Freak now works. :)
[Captivate Android Development] topiratiko:
Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] iXNyNe:
I noticed the acid tweaks (seemingly now renamed Samsung adrenaline shot) did cause some pretty good battery drain, so I wiped the init.d folder and restored a backup of my previous init.d folder (made just prior to installing the tweaks) so all I have from the tweaks package now are the binaries.

I hadn't run a quadrant score prior to installing but just now I pulled a 3100.

I'm running apex 9.2, talon 0.4.4.22, and the binaries from acid/sas.

I'm at 1200 oc, using ondemandX governor and sio scheduler. I'm not using bigmem talon release.

I don't know for sure but I believe the binaries improve database I/O because I notice my cappy has always hung during the database read and write speed tests of quadrant, now it speeds through the write test and I don't even see it do the read test, it almost seems like it skips it and goes right to the rendering tests.

So I don't think the tweaks are all bad, it just seems the init.d scripts are poorly pieced together.
[Captivate Android Development] Kyuta Syuko:
I'll agree that the scripts are poorly pieced together. Some only have 1 or 2 lines... I'm currently taking what I think might be useful and putting it all into one script file with the exception of Darky's zipalign script which I'm leaving by itself. I fortunately didn't have to worry about backing up my init.d folder because I didn't have one =o

On another note does anyone know anything about this Apps2SD+/Apps2SDEXT?
[Captivate Android Development] Kyuta Syuko:
Doesn't work for me. Are there limits on how big the file can be or anything like that?
[Captivate Android Development] iXNyNe:
You should post your results, I'd like to see what you come up with.

Also what rom are you on? For me apex puts a bunch of stuff in init.d and talon also adds a script for memory freak I believe.

Edit

Btw the zipalign script 1.0 and 1.1 were made by Wes garner. Darky tweaked it and dubbed his version 1.2.

Also the app2sd scripts you asked about I think they mess with the filesystem and are probably a bad idea.

I lost my copy of the cwm flashable zip and the mediafire link seems to be down so I can't look at them anyway :(
[Captivate Android Development] Kyuta Syuko:
I just happened to find the App2SDEXT when I was googling one of the lines to try and figure out what it does but never managed to do so...

I didn't really do much I just removed the VM Tweaks and moved everything into the S98EDT_Tweaks file and removed the barrier=0 flag from System and Data.

The line I couldn't figure out what it does though is the

setprop cm.filesystem.ready 1;

line and when I googled it two other similar lines generally showed up with it

setprop dm.filesystem.ready

setprop oxygen.filesystem.ready

which aren't included in the tweak file. I mean based off the command arguments I'd say it's telling the system that specific filesystem is ready, but why? And what are those different filesystems?
[Captivate Android Development] radraz:
could some one post up the stock files that are locatated in the init.d folder. I believe that there are only 3-4 files. Running continuum 6.2.1 on 4.4.22 ext4.

side note, is it possible that these tweeks could make my home and search button stop working? they stopped working and reflashing the kernel doesn't fix it :(
[Captivate Android Development] shane87:
Ok, so after reading this, I decided to look into the props a little more. As it turns out, these proos are flags used to let the init.rc script know that the filesystem is ready and init.rc may continue running. cm.filesystem.ready is used by cyannogenmod, and other roms, dc.filesystem.ready is used by damagecontrol, and other roms, and oxygen.filesystem.ready is used by oxygen roms. All of these props are the same, except that some roms check for cm.filesystem.ready, some check for dc.filesystem.ready, and oxygen checks for oxygen.filesystem.ready. These are not in reference to a specific file system. They simply send a message to init.rc that the main filesystem is ready, and a specific rom will check a specific flag. Apparently, all (or most) sgs roms use cm.filesystem.ready, and that is why the gingerenhancer6 script only uses the cm.filesystem.ready flag.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] nappent:
You can find the three files in the flashable rom.

Use root explorer to extract them.
[Captivate Android Development] AdamOutler:
Is the `su` binary present in this kernel?
[Captivate Android Development] AdamOutler:
I decided to try this with UCKF1 2.3.3 and failed... Oh well.

Here's a one click if you want it..

http://www.mediafire.com/?qstaugkulqb970m
[Captivate Android Development] Kyuta Syuko:
Ok that makes sense. Guess the random scripts I found included all three to be compatible with all ROMs.

Might tweak or remove vm.vfs_cache_pressure. My phone seems to get laggy faster after applying this tweak pack and with all the VM settings gone I'm thinking this is the culprit. That and from what I found a lower setting causes the OS to retain specific cache while values over 100 cause it to be more aggressive in retrieving the mem used by the specific cache. It also stated that 100 is the default value.
[Captivate Android Development] geokilla:
So... in conclusion that means the scripts are good or bad?
[Captivate Android Development] IDoMy0wnRacing:
I kept mine relatively short, 1.68MB in size, runs for about 10 seconds.
[Captivate Android Development] IDoMy0wnRacing:
LOL, I tried the same thing today with UCKH3, it didn't work either... Right to boot loop. Oh well.

I was able to use it in recovery for CWM3. UCKH3 made a good base for Continuum... :D
[Captivate Android Development] Kyuta Syuko:
The VM parts of the scripts are bad when using Talon. The rest of the scripts are still up for debate with the exception of the few changes existz mentioned.

Hmmm the one I'm trying to use is 326Kbs and only 2 seconds... Worked fine back on Froyo...
[Captivate Android Development] FocuseD83:
@exists, I know that you said you were not going to do a 1440 variant of your test kernel, but I implore you too. Please, lol. We know that these variants can potentially harm our phones, but some of us are speed junkies. I reverted back to a version of Talon (snail9) with the 1440 variant and used the S.A.S. tweak.

My results : plus 4000 quadrant score!

I know quadrant is pretty much meaningless, but I do notice a huge difference in the ability to multitask. Can receive a call while using N64oid with Tiger Arcade in the background with no lag whatsoever. Ideally, would want a 1440 variant, big men version of your current wonderful kernel. I know you have much better things to do, but I do also think that it will please your speed junkie fan base even more!

Thanks for all of your hard work regardless!

Clearer pic. WWW.tinypic.com/r/1zbqvcy/7

Sent from my Gingerbread Cappy
[Captivate Android Development] sremick:
http://www.youtube.com/watch?v=uCUsPnKD1gk

;)

Anyway, figured I'd try again since I didn't get a response last time: I'd really like to return to Talon as I've been using Darkcore for a while now due to the memory issues. I don't like Darkcore though because it doesn't allow the brightness to be lowered as much as Talon and it lacks Voodoo Color. One thing I'd like though is a way on the Voodoo Control app to adjust colors with more than just a grayscale bar for reference. Would be really nice to actually have red/green/blue bands so one can do a proper calibration with filters.

Tried asking this also in what I thought was the proper Voodoo thread but no answer there either.

Thanks :)
[Captivate Android Development] existz:
This is something that would have to probably be modified in voodoo control app
[Captivate Android Development] existz:
There will be higher OC, probably after kernel hits v1.0 status... Im currently without my captivate, once i get it back im going to start on the oc module (thanks to startosk), once i get it working with talon and added to the source, plus make sure its stable up to 1.2ghz, then ill start working on higher oc for the module.. But the module will only replace L0 (ie.. when the module is unloaded (default), the frequency/voltage source will be identical to stock 1ghz..then when you load the module, it will only replace 1ghz with 1.2ghz.. then once higher oc is added, say 1.4 for example, when the module is loaded it will only replace 1ghz with 1.4ghz..) With there not being as many frequencies, its possible it wont be as stable as it was on earlier versions of talon with multiple oc steps in one kernel..so what was stable before, might not be able to run that high...but this is the only way i can do it without bringing back the 'scaling to max frequency no matter what max clock is set' bug..(ie..scales to say 1.4ghz even if max clock is set to 1ghz)
[Captivate Android Development] sremick:
I figured. Any idea on the proper channel to suggest/discuss that? Direct emails got no response, nor did posting in this thread.