yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mrcpu:
I hesitate to post this, because people confuse criticism for personal attacks.

But I updated to this version: TalonDEV-0.1.7-T17r2, wiped cache, dalvik, stats, voltage settings, and this kernel is worse for me than the may 14th one.

I rebooted it twice during the night when I woke up to check the time, and this morning, I work up about 1 minute before the alarm should've gone off, and it was SoD'd again. So I rebooted it, set the alarm ahead a few minutes, with 2 5 minute snoozes. Didn't touch anything else.

Alarm went off, swiped the snooze, and it died before the 5 minute snooze was up. Changed the display timeout to 10 minutes (after yet another reboot and clock) and Ii was able to get 2 5 minute snoozes in, but then it was dead by the time I got out of the shower.

When I checked it using task manage, only active application was "Clock". wifi, BT, GPS., and auto-rotate are all turned off, then it was dead. CPU spy showed time in 1000, 800, and deep sleep. I never re-enabled 1200 or changed scheduler.

I'm happy to try anything.

Continuum 5.4.1
[Captivate Android Development] existz:
PM sent
[Captivate Android Development] rajendra82:
An update on the bluetooth issue for anyone interested:

After I got back to my desk, I decided to Odin flash T1.17r2, to see if bluetooth would come on, and it did. I then decided to flash T1.19, hot off the existz test builds, and it too worked. It might have just been something about the T1.18 Odin flash, that broke bluetooth. Others with the same setup as me had it working fine.
[Captivate Android Development] Loftus:
I too was having Bluetooth problems after flashing Talon 0.1.7-T18, however I had flashed the new version using the SGS Kernel Fasher tool from inside Android, as I was away from my PC with Odin installed.

Recalling Existz's previous advice, when I was back at my PC I re-flashed the same kernel TAR using Odin3 - and Bluetooth is now working flawlessly.

My lesson learned: listen carefully to the Dev's instructions for applying their Kernel/ROM/MOD/whatever - they know what they're talking about

Loftus
[Captivate Android Development] aalh:
I have only had SD's in GB (on any kernel, not specific to Talon) after charging long past full on AC, have not tried USB long charge yet

I decided to try the bat drain solution (pull the battery for a couple min)

I havent hd an SD since, around 4hrs ago

I will update if it changes

EDIT:

No SD since pulling the battery yesterday

OC 1200, No UV

T17R2
[Captivate Android Development] toy028:
Having hard shut downs where i have to remove the battery on T18 and T19. I never had those issues on T15 and older. Im running CONT 5.4.1 OC at 1200mhz, no UV.
[Captivate Android Development] mrhaley30705:
Ext4 or RFS?
[Captivate Android Development] toy028:
RFS File system
[Captivate Android Development] PriTel03:
Where can I get access to the latest test build? I'm running T1.17rd, flashed through Odin and my bluetooth is dead.

Thanks.
[Captivate Android Development] toy028:
T19 is the latest test build. I dont think Im suppose to say where the builds are.
[Captivate Android Development] existz:
Test builds are not available unless I post them myself as a public test.. some builds are just not ment for the public...sometimes we are trying new stuff that might break certain things.. it might fix one thing, but break another...so I don't want test builds posted here, unless I know its a stable release, then ill post it myself.. but the bluetooth issues seems to be resolved ..so its been reported, acknowledged, and fixed..
[Captivate Android Development] mrhaley30705:
Try converting to ext4.
[Captivate Android Development] PriTel03:
Oh ok, I didn't know test builds were off limits to public, but it makes sense. I can live without bluetooth for a bit. I just use it for lazy file transfers mostly anyways.
[Captivate Android Development] harpo1:
Sorry my mistake. I just checked and KTLO is part of contiuum. What ROM are you running?
[Captivate Android Development] existz:
yea its a known bug with KTLO, im not sure if its due to using nexus s touchkey driver instead of old froyo driver or what..but its been acknowledged
[Captivate Android Development] wonner:
1.3 is working for me without errors.
[Captivate Android Development] sjavvaji:
can't get the voltage settings to stick...made sure the previous one was deleted and am on ext4...made sure the new file is there...it just won't stick...using the voltage control 3 on doc's jvb
[Captivate Android Development] slider2828:
Your kernel is ROCKING!!!! On JUWE 4.1 Rom... Glad I am back with existz although CF-ROOT was doing a pretty good job too over there, but avast I don't have a i9000! Donations and libations baby!......
[Captivate Android Development] :
Not running a certain rom. Rom kitchen + slightly modified.
[Captivate Android Development] jde984:
existz - if we flash a rom cooked with a different kernel, would it be in our best interest to convert back to rfs first?
[Captivate Android Development] LNJ:
Not necessary if you were already on ext4.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] squishy5:
where would the kernel go in odin the pda section or the pit or phone section
[Captivate Android Development] existz:
If your already on ext4, there's no need to convert back to rfs
[Captivate Android Development] existz:
In the Pda slot
[Captivate Android Development] squishy5:
i downloaded contumim rc1 yester day and it came with talon but when i downloaded the ext4 app and it says the kernel is not sopperted
[Captivate Android Development] existz:
The one included in rc1 was just a test version, not the same as the release
[Captivate Android Development] bamonkey:
Running on cont rc1 with this new kernel. So far so good the light sensor polling seems crazy its adjusting alot...unsure if this is a problem or not yet, lol.
[Captivate Android Development] ridethelight:
Waiting on BLN and a ROM from MikeyMike and ill be all over his. keep up the good work existz
[Captivate Android Development] ytt3r:
I have a surprise for all of you coming up soon... Something to do with increased CPU clock speeds... ;)
[Captivate Android Development] markmunsch:
Another tease???? You're kiling me. I'm just sitting here refreshing kernel and ROM threads looking for stuff to flash :D
[Captivate Android Development] momulah:
Same here!
[Captivate Android Development] Shammyh:
Hey existz,

Any idea when we'll be seeing cifs support?

I rely on it at work, and for entertainment at home, so I can't use any kernel as a daily driver without it.

PS, great job with the kernel so far. Glad to see some developers still love their Captivates!
[Captivate Android Development] Doug8796:
ytt3r. that sounds great! :) Many thanks
[Captivate Android Development] sinichi21:
i have a question does UVing the phone affects the way of toggling the wifi and bluetooth? sometimes i think when i set an aggressive uv when i turn the wifi or bluetooth it takes longer to be activated, don't know if that has something to do with the uv so i just want to know if it has something to do with it which state is responsible for the toggling the wifi and bluetooth
[Captivate Android Development] rajendra82:
I was playing around with test builds T18 and T19, and noticed worsening of a behavior that had been bothering me since upgrading to Gingerbread. I believe, I have found the solution, and would like you to try it, and let me know what you think.

I use ADW Launcher EX, and noticed that the launcher closed way too often in the background. This is very annoying to me, because when I exited an app, I would have to wait 15-30 seconds for the launcher to redraw itself, before I could do something else. I tried some other launchers, just to find out that the problem was not specific to ADW. There is a setting in ADW to keep it in memory (tagged dangerous, by the way), but it does not work past froyo. The behavior of launcher closing got a lot worse in the last two test builds. I think this is because of a change in initramfs compression, which has increased the file size and the memory footprint. I then stumbled across a solution that gives the launcher a much higher priority, and keeps it from closing.

Here is how to do it:

1. In Terminal Emulator or adb shell, type su, and then as root type

cat /data/local.prop

You will most likely get a file does not exist error message. If so proceed to step 2, otherwise skip to step 3.

2. Type

echo ro.HOME_APP_ADJ=1>/data/local.prop

3. If there already was a file called /data/local.prop, check to see if the cat output showed it containing this line

ro.HOME_APP_ADJ=1

If it didn't, add the line using the command in step 2.

4. Reboot the phone to give the launcher a higher priority (1 instead of default 4). This will keep it in memory for a lot longer, but will still allow it to be closed when absolutely necessary. Priority 0 would have forced it to never close, but then you are locking up that memory from apps that really need it.
[Captivate Android Development] Holmes108:
Interesting. I had this issue in Froyo, with Launcher Pro and Stock TW... but it seems to happen less for me since Gingerbread.

It was my biggest pet peeve. I didn't know what the issue was, but what you explained about the launcher being removed from memory makes sense. Every so often when leaving an App, my screen was just blank (except status bar), and eventually all my icons etc would reappear, but sometimes it took 10 seconds or more. This is the type of thing you're talking about, yes?

Again, this was actually worse for me in Froyo. It still happens, but much less often, and rarely takes more than 3 seconds or so to reappear.
[Captivate Android Development] rajendra82:
It is the same issue. The reason it might have been worse for you under Froyo, might have been due to you using a different (probably less optimized) kernel, that left you with less working memory. From what I have read, Gingerbread is actually a lot more aggressive than Froyo in closing background applications. This is a good thing, except we don't want it to close the launcher, every time you start a new app.
[Captivate Android Development] existz:
Do me a favor if you don't care with t19,..there's a file, /etc/lmk.conf, you can adjust the lmk preset (reboot after you change it), I think kodos96 has 5-6 presets in there (each one is listed in the file), try each one and let me know if its any better
[Captivate Android Development] baghera1979:
I've noticed something since I flashed t19 yesterday. All day yesterday had wifi running whole time and battery was just fine throughout the day ...today I pull phone off charger at 630am and by 1130 am I'm down to 53%battery left. I haven't done anything new as far as using the phone. Maybe 10 texts and some game play with a little time on the forums. Did some checking and I noticed that the VC settings have reset to stock. Was running at 1200mhz-50 and 75 rest of the settings. This happen to anyone else? Is this a kernel problem or is there something I'm overlooking.
[Captivate Android Development] rajendra82:
I will try them, but looking at it, it seems that what I tweaked effectively overrode Preset_x_ADJ_7. The original priority in preset 4 for the home app was 5, and under T17r2, the home app did close from time to time, but not nearly as much as under T18 and T19. I am liking priority 1 for the home app a lot so far, and none of the presets have it that high.
[Captivate Android Development] rajendra82:
Revert to busybox 1.17.1 to fix the voltage settings issue. Busybox 1.18.4 is missing some parts, so the scripts in /etc/init.d are not getting executed on boot.
[Captivate Android Development] baghera1979:
Thank you. Will try that
[Captivate Android Development] neffarious:
Existz,

This is the exact behavior i have been describing to you as lag for the past few days. I didn't articulate it as well but this is exactly what i am seeing too. BTW i only get it some times, i suspect it depends on how long i have been in the app, IE yahoo messenger causes the issue more than Handcent. Same for facebook. I did a full wipe, reinstalled one app at time. No single app caused the issue. It Happends only when going from launcher pro to an app and back.
[Captivate Android Development] existz:
Ok..gotcha... so its not really lag, just that the launcher is getting killed and is reloading, ... try experimenting with the different presets in /etc/lmk.conf ... try those and if it still doesnt work right, then try what was mentioned above about setting home_app_adj=1,...ill talk to kodos96 about adjusting the home_app_adj

I know none of the other presets set the priority that high, but they do allow more memory to be used before lmk kicks in, so that could solve the issue as well
[Captivate Android Development] kodos96:
So I guess I never got around to announcing it here on the XDA thread, but as of a few versions back, Talon has included my LMKset config scripts, which allow you to tweak LMK settings in the "correct" way... for a bit of background, android's lowmemorykill functionality consists of both a kernel component and a userspace (i.e. framework) component, each with their own settings - the kernels are adjusted with /sys/ knobs, the framework's are adjusted via those ro.WHATEVER properties.... and here's the thing: the two sets of settings need to match each other, or else the kernel and userspace end up fighting with each other about what apps to kill when memory runs low. That's bad.

So I wrote some scripts that let you define LMK settings (or select one of my presets) and it makes sure they get updated in both places. If you're going to try tweaking LMK settings, this is how you want to do it.

The file you want to edit is /etc/lmk.conf - to start with you can try choosing a different preset with the "PRESET=" setting near the top of the file. Currently presets 1-5 are defined, but don't bother with preset 1, it's the stock Samsung settings, which suck. And don't set an undefined preset (i.e. higher than 5), it'll make you bootloop.

If none of the presets solve your problem, you can set preset 0, then manually edit the values in the user-defined preset section.

All changes require a reboot to take effect.

So play around with these some, and please give me some feedback on them - especially if you work out a custom preset that you think works better for you.
[Captivate Android Development] kodos96:
I'm not sure whether or not the way you changed it in the local.prop would actually override the setting from LMKset... the properties are read-only, meaning they can only be set once per boot, so whichever gets processed first, the local.prop of my lmkset script, ends up taking effect... I'm not 100% sure, but I would suspect that lmkset is probably running first, and so your tweak probably isn't actually doing anything. I could be wrong though.

One thing to keep in mind when editing these values is that you want to keep them in the correct order... i.e. you don't want any of the ADJ or MEM values to be lower than the one that came before it - having them out of order can cause unintended side effects. So if you want to lower HOME_ADJ, you should lower all the preceding values so that they remain in their original order.

Setting it all the way down to 1 is probably overkill.
[Captivate Android Development] rajendra82:
Thanks for the detailed explanation. I did see the launcher sticking around several hours in memory, without being killed a single time, after I added the property in /data/local.prop, but I can't rule out that behavior being placebo effect. For some reason after removing that setting and rebooted for the purpose of testing preset 4, I can't find a reliable action that would kill the launcher in the background every time. Before all this, the launcher seemed to die every time I started an app (or at least it seemed that way).

Once I get the method to background kill figured out, I can report results of each preset. Do you have any suggestions?
[Captivate Android Development] TonyStark R.I.P.:
ADWs website talks about the FCs on GB. It has been happening less w/ there v1.3.3 but it is still being worked on.

I'm thinking it's probably not kernel related I would assume it's the Android version.
[Captivate Android Development] rajendra82:
ADW is not FC'ing. If it was doing that, there would be a dialog box, giving a prompt to kill or wait. It is getting killed by LMK settings, so when you exit an app, the launcher has to reload. The issue is also not specific to ADW. Someone with Launcherpro was complaining about the same thing.

By the way, the settings in the /data/local.prop do override the /etc/lmk.conf settings. Here is what getprop showed me under default boot, with no /data/local.prop:

...

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [1]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [3]

[ro.SECONDARY_SERVER_ADJ]: [4]

[ro.BACKUP_APP_ADJ]: [4]

[ro.HOME_APP_ADJ]: [5]

[ro.HIDDEN_APP_MIN_ADJ]: [6]

[ro.EMPTY_APP_ADJ]: [15]

...

Compare that to what it showed me when I put ro.HOME_APP_ADJ=1 in /data/local.prop and rebooted:

...

[ro.HOME_APP_ADJ]: [1]

...

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [1]

[ro.PERCEPTIBLE_APP_ADJ]: [2]

[ro.HEAVY_WEIGHT_APP_ADJ]: [3]

[ro.SECONDARY_SERVER_ADJ]: [4]

[ro.BACKUP_APP_ADJ]: [4]

[ro.HIDDEN_APP_MIN_ADJ]: [6]

[ro.EMPTY_APP_ADJ]: [15]

...

Obviously editing preset 0 gives access to all the settings, so it is the "correct" way, but this method works too.

I am also curious as to why ro.FOREGROUND_APP_ADJ, ro.VISIBLE_APP_ADJ, ro.PERCEPTIBLE_APP_ADJ, ro.HEAVY_WEIGHT_APP_ADJ, ro.SECONDARY_SERVER_ADJ, and ro.BACKUP_APP_ADJ should all be lower or equal to ro.HOME_APP_ADJ. I came across my fix while looking at some online Droid X forums, and they don't discuss changing priority of any others, just HOME_APP_ADJ. I am not doubting, I just want to learn to tweak it properly.
[Captivate Android Development] TonyStark R.I.P.:
It's all good, just sayin http://jbthemes.com/anderweb/ They are very receptive to questions and findings
[Captivate Android Development] toy028:
Im not impressed with ext4 on GB yet. Hopefully down the road when it has more time to mature.
[Captivate Android Development] rajendra82:
So you are loving the mature "Robust File System" over one Google themselves chose on Nexus S?
[Captivate Android Development] toy028:
I'm just seeing a more stable phone on Continuum's rom running RFS. I know ext4 is a better choice for a file system but its just not showing its colors for me yet.
[Captivate Android Development] Holmes108:
Many reports of this on Continuum. It's my experience too. First time I've preferred RFS.
[Captivate Android Development] mrcpu:
T19 update

Updated to 5.5 continuum and then flashed T19.

Laggy behavior appears gone. I use the Sony HE launcher, so my experiences have been different than most, but installed pauldiddy's remix theme, use the full window animations, albeit at fast speeds, and everything was fine. I press buttons, applications happen, feedback appears, all is well from a "peppy" perspective.

Did get a reboot using one of the lock screen, I think the MIUI one, but I prefer rotary unlock, so didn't explore it further.

However, I did get SoD during the night, so Ii have reduced the -50 UV to -25 across the board, and going to try that. Phone shows a lot of time in deep sleep, *but* it was able to go through snooze cycles w/o shutting down, and I've been carrying it all day and it's been up and running everytime I take it out of my pocket.

I do allow OC to 1.2gig, and I have disabled all tweaks except noatime.

So compared to kernel's past, T19 is working well, if I can get the SoD issue resolved. Not going to get excited about it until I see what a couple days UV do.
[Captivate Android Development] topiratiko:
Where is everyone getting these kernels? I want in!
[Captivate Android Development] mrhaley30705:
Test 19-bln working:

Started with a clean flash of C5.5 from jf6. BT and wifi not working. Wifi would cause reboot, BT just timed out. Converted to ext4 and problem went away.24 hrs later BT started timing out again. Cleared cache only from recovery, its good for now.

Something off I've noticed about wifi, when it caused a reboot, out would actually be on after phone finished booting.
[Captivate Android Development] Shammyh:
Just to check, you mean JF6 -> JVB/JVK -> C5.5 right?
[Captivate Android Development] mrhaley30705:
Sorry, should have been more specific. I used Cezar's safe method for jf6. I didn't do anything with bootloaders.
[Captivate Android Development] Shammyh:
Gotcha. I'd test it with bootloaders (while taking all the obvious precautions) and see if your problems still exist.
[Captivate Android Development] existz:
Yea I would try with bootloaders, cause I've had about 15-20 ppl confirm T19 fixes this issue, bt and wifi loads every single time.. which I've never had a problem with either one (bt or wifi loading)
[Captivate Android Development] mrhaley30705:
Ok. I'll start over with bootloaders. Any recommendations for loader package? I've only flashed bootloaders once, and I dont remember which one I used.
[Captivate Android Development] Shammyh:
Personally I just flash a stock JVB build on top of a fresh master cleared JF6 One-Click.

Throw on a kernel with CWM support, flash your desired ROM, and be on your way.

Check around XDA to find a stock package with bootloaders. Maybe someone nicer than me can find you a link, but there are plenty of packages floating around. You really only want it for the bootloaders, but flashing only a boot.bin and sbl.bin without anything else *could* be a recipe for problems.
[Captivate Android Development] mrhaley30705:
Flashed safe jf6, master cleared, flashed Cezars bootloader package, kernel w/o reboot, C5.5 from cwm, flashed T19 bigmem w/bln working, restored apps, converted to ext4, set tweaks (speed,no a time, dirtyness), flashed theme (FreshGingerblue).

Wifi worked off the bat. BT didn't work until I flashed theme.
[Captivate Android Development] geokilla:
I'm pretty sure this is kernel related. Lately I'm having trouble with WiFi. I can connect to the AP and obtain a LAN IP address just fine, but I actually can't surf the web. Turning WiFi on and off doesn't fix it. Or, the other situation that'll occur is that WiFi will work like it's supposed to, IF I give the Captivate a minute to load up whatever WiFi drivers there are, despite already being connected to the AP.

In short and I guess less confusing terms:

Turn on WiFi

WiFi doesn't work for the first minute or so

After that first minute or so, WiFi will work and I can browse like normal or WiFi will continue not to work
[Captivate Android Development] toy028:
What kernal are you using? Try T19 or T15 if you dont need BLN
[Captivate Android Development] H3llstorm:
Hey existz,

I'm not sure if this is helpful or useful, but I just saw this linked in another thread:

http://code.google.com/p/android/issues/detail?id=11126#c290

Supposedly it's a fix for the suspend/resume loop charging issue.
[Captivate Android Development] mrhaley30705:
Update

Now wifi is causing problems. Turn it on, connects quickly. But when I try to go to a website, it won't connect. With xda, I get a black screen with the address at the bottom. With gmail, it days no connection. Using cache mate, I clear cache, then it works.
[Captivate Android Development] slayp00n:
Based on what?