yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] grkmaster:
I ended up doing that after because for some reason switching keyboards would stick even after uninstalling my 3rd party program. Doing that fixed my keyboard issue but brought back the BT issue. Im flashing Continuum RC3 and will see if BT still has a issue. His changelog states Fixed Bluetooth bug
[Captivate Android Development] jcr81:
This is the weirdest thing. I flashed xcals, enabled bluetooth, flashed talon and everything was fine once again. I then converted to ext4 using CF's app and bluetooth is dead once again. I dunno...

Sent from my Samsung Captivate
[Captivate Android Development] jjtitus098:
I have been having random reboots but when it reboots, it only goes back to the boot animation. Not a full reboot. I'm sorry if this has been discussed, I haven't had the time to browse through everything. I don't understand what's causing it. Its almost like when I'm doing too much at one time it reboots. And I just got the charging drain. Woke up and it was at 86%.
[Captivate Android Development] grkmaster:
IN RC3, how do i enabled states for 100hmhz/deep sleep ... after flashing it, CPU SPY shows them as unused
[Captivate Android Development] minotaur507:
^^^

The number of states changed with the latest Talon kernel. Make sure you clear your voltage config through CWM.

Hope this helps.
[Captivate Android Development] grkmaster:
I had Talon 1.2 before RC3 and all states where showing in CPU SPY .. After flashing and wiping voltage, it still shows that. Maybe a wipe voltage and then reflash RC3 will help, i hope

EDIT: so icezar inclued a newer talon build which cpu spy shows unused states as 100, 200 and deep sleep .. i tried flashing back to 1.2 and the same thing shows
[Captivate Android Development] :
Where can I get vc ex
[Captivate Android Development] LNJ:
It's being used just fine. I monitor it. However there was a cpuspy update last night and anything under 400mhz is not showing anymore.

So it's the app.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] shoman94:
It definitely still works since my battery life is still excellent.
[Captivate Android Development] Yaantra:
Is this the latest 0.1.3 that cezar is refering to?

Sent from my un-captive Captivate
[Captivate Android Development] LNJ:
Nope. Go to the Sukerpunch IRC channel for it.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] johan8:
0.1.3 Test1 has already released for testing

http://berryfx.com/RobBeane/Test/
[Captivate Android Development] lownox:
I'm with you. I measure battery life based on standby power drain. IF standby drain is more than 2-3% per hour... I need to change something. Other than that... if the screen is on... Nobody is going to get much more than 4 hours of battery life.

Standby drain... that is the key to having the battery last. So yeah... I am with you.
[Captivate Android Development] pixbuf:
Wow! This is for sure the best kernel I've used. I had the 0.3.1T??R2 that came with Continuum v6, but that produced much lag and random freezes and reboots. I used JVP-Voodoo 2.0, which was much more stable for my phone. When the final 03.1 came out I tried it, and Zowee! Fast, stable, smooth. Great job, existz. Here's some beer money for you.

Confirmation number: 2XK60181229685501.
[Captivate Android Development] manny05:
Yea I did all that. I was just wondering if closing the app turns off the over clocking. Or its maybe just me...
[Captivate Android Development] existz:
You can close the app and everything will still be OC'd, all the app does is writes a file to /etc/init.d/, that is executed on boot, that file then sets the settings... So all the app does is just makes that file, so as long as S_volt_scheduler is in /etc/init.d/ then you can uninstall the app if you even wanted to ..

Sent from my SGH-I897
[Captivate Android Development] squishy5:
how do u configure gpu oc

does voltage control work to confriuge it
[Captivate Android Development] gerc86:
Battery consumption is relative, for me (in the way i use my galaxy s) is better than ever! XD
[Captivate Android Development] toy028:
The 1200 version is working great. First one if your GB kernels that my phone likes. Running at 1200 and 400 video. Smooth!!
[Captivate Android Development] tmng95014:
+1.

I only turn on wifi, BT... when needed. I only used the phone for making call, SMS and some time web browsing. Very rarely used GPS. With this usage, my phone lasts 3-4 days between charge. I just want to share the information and nointention to exaggerate. One's mileage will vary.
[Captivate Android Development] TheSoaresan:
I'm getting amazing battery life after calibration. Its been 18 hrs. I'm at 75% with 1hr 57min display time. Not bad at all. I'm still on rfs, does that make a difference?

And yes, I agree it depends on Widgets and background apps and display time.
[Captivate Android Development] Holmes108:
It's not bad, but it's not insane. So you've been 16 hours in standby. A phone should be able to go 4 or 5 days in standby.

I'm probably in the same vicinity as you... I'm at 83%, just under an hour of display on (full brightness always)... only 4 hours off battery... but it's the display on time that matters... standby is minuscule.

Popping on the screen for a few minutes here and there (totalling an hour or two) to check an email, look something up, etc isn't going to kill the battery. Play a game for 2-3 hours, or do some real activity and that battery will be way below 50% quick.

But I see some reports and people are like "22 hours of medium to heavy use and at 75%".... medium to heavy use.... yeah right.
[Captivate Android Development] chappatti:
A huge kudos for this kernel................! I waited a long time before getting my phone on Gingerbread till quirks were worked out...and this kernel goes a long way!

A question or two: I notice "Set Light Sensor Polling to 1s" in the kernel features. Can one set the max brightness value also? I find that in auto mode the screen brightness does not want to increase beyond what would be equal to 50% brightness. Generally, it would go much brighter when needed. I do not right now care about batt since I need my GPS to be viewable under daylight in car--------NOT DIRECT SUNLIGHT, I know that, but still the screen is difficult to see in my car.

Also, WiFi signal is weak...no matter if I stand next to my router....is that kernel or ROM dependent?

Thanks.
[Captivate Android Development] jjtitus098:
I never know how people could possibly get some of the battery life they get when under "heavy use". I listen to music using Audiogalaxy for about 2-3 hours per day while at school and I am down to 25% by 3:00. That us heavy use. I've never gotten any better.

Sent from my Captivate running Continuum 6.
[Captivate Android Development] neubauej:
I have a hard time getting through a full day... on a custom built 2800mah battery (2 oem batts in parallel)

But I know Im a heavy user, and am actually quite happy with that.
[Captivate Android Development] Taderich:
WOW!! Flashed 0.3.1 1440/340 CWM and left it at the default 1.0Ghz and can't believe the difference! I don't even need to OC.

This kernel is impressive.

Really nice work! Thank you.
[Captivate Android Development] johan8:
problem with Talon

This is the problem of my i897 with Talon.:(

The AP seems connected, and the IP has already obtained,

but the status still in obtaining.....

cannot connect to internet.

I have tried different AP, tried public AP in shopping mall, library, Starbucks.....

But the status is the same, keeping obtaining, cannot connect to internet.

However, if switch to existz' JVP-voodoo or other kernel, this problem is gone, no problem at all !

I know it is weird, and seems that here is only me has such problem.:(
[Captivate Android Development] pikachu01:
Try a clean installation and a re-flash of the kernel? It might be other apps interfering with Wifi?
[Captivate Android Development] johan8:
I have also did fresh flash with re-partitions,

everything wiped and cleaned up and back to factory default.

All stock rom, tried JVA JVB JVO JVH JVP, asian JV5 JV6.....

Nothing in init.d, no oc/uv settings,

But the problem is the same.

existz also tried help me on this, but still can't find out what's wrong.

and seems that here is only me has this problem.

However flash to jvp-voodoo, wifi works again.

No luck with talon:(
[Captivate Android Development] hkeyman:
You hit a home run with this build exist! Phone is running smooth, cool, and at what seems so far after the whole day peak performance with no issues. I dont know about the other users having WiFi connectivity issues but I got onto my AP middle of peak time today and pulled 27Mb down/17Mb up on a 35/35 FiOS line. This is just Sweet, its amazing and how this phone should perform. I downloaded a 240mb rom in about 5± minutes. Just awesome! Battery seems a little weak...but I am a heavy user with many apps running and email push/pull. I have yet to try GPS or navigation on Phone or WiFi but I will post if anything is identified. I have received a few calls and no difference in quality that I can hear from all previous builds. But a big thumbs up and thank you for awesome work.

Transported From Hkeyman's (Phone)i897 Captivate,

(Kernel)Talon 0.3.1 1400/352

(ROM)Continuum v6rc1

(Modem)TDVJP9
[Captivate Android Development] johan8:
good for you !

I love to use existz' kernel, but no luck.

Maybe I will try Continuum later.

After 0.2.2, I can't get my wifi working.
[Captivate Android Development] Yuna:
My phone can't charge while from USB with wifi on e.g not sleeping, going to 75% 1200 freq and disacharging slowly.

if i turn off wifi - it's good. so relatively - some issues are there.
[Captivate Android Development] existz:
So eveything that you have tried have been stock roms right? .. Theres about 50/50 in i9000 forum with this issue as well, which most are reporting on stock roms.. If you can, try using a custom rom with Talon, like Continuum, Apex or Symply SGS2, and see if you can connect with it..
[Captivate Android Development] gerc86:
New Firmware

There is a new firmware, http://xdaforums.com/showthread.php?t=1145184

I am waiting for Darky to release the new rom (Darky 10.2 hope is based on JVQ), I wonder if the latest Talon Kernel will work on this firmware. Any body have tried this?
[Captivate Android Development] RashaMatt:
0.3.1: Max used freq reverts to 1GHz

I'm using TalonDEV-0.3.1-1400-BIGMEM, with 1400 as the max freq (set with Control Freak). Whenever my screen turns off, the max freq used is somehow being reset to 1000.

When I turn the screen back on and open Control Freak, all the settings are exactly as I left them (max freq is still 1400), BUT nothing above 1GHz is actually being used (I'm using Process Monitor to monitor the current CPU freq).

If I choose "Apply for Now" in CF, then all the freq's up to 1400 will get used again, but only until I turn off the screen - then it's back to not using anything above 1000. Rinse and repeat.

Not sure whether this behavior is new in 0.3.1, because I wasn't really paying attention to the actual frequencies being used before. I was previously running 0.2.2R2 and Zach's customized 0.2.1.

SGS Captivate

Serendipity VII ROM (build 1)

EDIT: After uninstalling and reinstalling Process Monitor, I can't reproduce this problem, so I guess it had something to do with PM....
[Captivate Android Development] johan8:
Yes, I only use stock rom.

I gonna try custom rom later.

And, I would also want to find out why custom rom doesn't have this problem.

On the other hand JVP-voodoo doesn't have this problem with stock rom.

I have tried APEX7.1 last week, it seems also have this problem.
[Captivate Android Development] shane87:
Yeah, sounds like a problem with PM. I run elixir to track my cpu stats, mem use, etc, but I have noticed that elixir consistently reports a much lower available memory than the built in app manager. For example, elixir will show 50mb free, but hitting settings > applications > running will show about 90mb free. Not sure which is right.
[Captivate Android Development] H3llstorm:
Hey existz, anything interesting here:

http://xdaforums.com/showthread.php?t=1137554
[Captivate Android Development] dmnall:
I would recommend try out Mosaic rom by team Phoenix! I have only experienced the issues you are having with stock roms when I ran Samsung leaked froyo rom however running i9000 based froyo and gb roms no problems with wifi! So far with m4 and talon dev 0.3.1 Oc 1200 runs sweet and smooth!

Hth,

Charlie
[Captivate Android Development] kodos96:
Yes, VERY interesting.... in the sense that I find the human mind's capacity to fool itself via placebo effect and confirmation bias to be completely fascinating ;)

The author of the script seems to misunderstand some really basic concepts... for instance, he doesn't seem to realize that PIDs get reassigned every time a process is restarted, so by just renicing those PIDs at boot time he isn't actually accomplishing much... as soon as the apps in question get killed and restarted (which happens pretty much constantly on android), the script will no longer have any effect. And that's actually a good thing, since the effect it WOULD have, if it had any effect at all, would almost certainly be negative - permanently setting high priorities to apps, even when they're running in the background, would cause major lag on your foreground app.

And then there's the thing with kswapd - setting it to low priority might speed things up as long it's just background processes doing the swapping.... but then when you switch to a swapped out app, you WANT kswapd to have high priority, in order to swap back in as quickly as possible.

But the real kicker is that this guy is almost certainly running this script on a kernel which doesn't even have swap enabled
[Captivate Android Development] zacharias.maladroit:
++

the negative effect was very noticable

it kind of hogged the cpu and/or system

and made things lag very much (I made it loop otherwise it wouldn't have "work"ed, or you'd need to hack it into the kernel which is stupid)

besides that kswapd from time to time still appears and causes high load in swapless kernels which is weird

talking about that

I have a patch which might improve this (it's already in the platypus kernel),

will add it to the Talon testing queue ...
[Captivate Android Development] jmtheiss:
I'm pretty sure I'm doing something wrong, but I can't get the voodoo control to un-ext4 my phone. I flashed the 0.3.1 kernel (TalonDEV 0.3.1 340MB 1200MHZ CWM3) with mosaic IV, and it's running great, but now that MV is here, I want to flash to that. As part of the directions, you have to get rid of ext4.

My first step was trying from CWM. It says it will do it on the next reboot, but it doesn't - it just skips it.

I then tried the control app. It says "Status: Ext4 lagfix active", and so I tried activating "ext4 conversion" to see if it just needed to be activated before going to CWM and undoing it. That didn't fix it.

I just tried the CWM option again after clearing the cache partition and the dalvik cache. No luck.

(I don't know if it matters, but I don't have the sound up during the boot sequence, so I won't be able to hear the voodoo voice.)

It's probably just me not understanding what I'm doing, but has anyone else had problems getting the conversion back to rfs to stick?
[Captivate Android Development] studacris:
That was an issue with xcal's kernels for a bit. Reflash the kernel with odin and try converting again. If that doesn't work time for a trip back to stock jvb.
[Captivate Android Development] jmtheiss:
Sounds good - one hiccup. I didn't flash this with odin, but CWM. Do you think that will make a difference?
[Captivate Android Development] studacris:
I prefer odin for kernel flashes...but you can try cwm I spose
[Captivate Android Development] jmtheiss:
Well, looks like it's a no-go. Back to JVB, soon as I find the tools to get there. Thanks, studacris.
[Captivate Android Development] mrhaley30705:
JVB is not necessary, use KF1 without bootloaders instead. Check my sig or look here. If the one click doesn't work on your phone, try waiting about an hour or so. I am about to upload a 3 file version for use with Odin 1.8x.
[Captivate Android Development] jmtheiss:
- post edited -

I just realized I'm hijacking this thread. I'll move to somewhere else.
[Captivate Android Development] -Thrive-:
Charging bug

I also posted this on the Continuum forum since I am not sure where this bug originates.

In have determined that the charging bug I am experiencing is related to wifi. If I disable wifi before I power down at night, I never experience a bug and always boot to 98 - 100%. If I leave wifi on and power down I always encounter a charging bug. I was late to realize this because I was leaving wifi on all of the time while at home and now on the road with it turned off, no bug.

My other observation is when I experience the charging bug the symptoms are always the same. If I power on immediately after unplugging, it always takes 3 long presses of the power button to get the phone to boot but if I do it immediately, the bug is minimized, often booting at 92 - 96%. If I don't boot immediately after unplugging, my battery percent falls dramatically, often into the 80 - 90% range.

It doesn't seem like everyone with the charging bug is experiencing the same symptoms and there may be different causes, but at least in my case, the charging bug is always related to whether or not wifi is on when I power off.
[Captivate Android Development] manny05:
I noticed that while using control freak, I set it to run 1440ghz however. Cpu spy shows that I'm running at 800. 60% of the time. Am I doing something wrong or what?
[Captivate Android Development] pikachu01:
Check with a few other OC/UV apps like Pimp my CPU and Voltage Control. You might be limiting your OC to 800MHz
[Captivate Android Development] chappatti:
Some quirks?

A couple of things I noticed: maybe its just me or maybe not. :p

1. Auto brightness - the max brightness is quite low. Is there a way to set the max level foe AUTO brightness.

2. Is lagfix necessary............I mean lagfix was an old captivate problem. Has this not been fixed as yet that one needs to enable lagfix all the time.

3. Screen sharpness in Froyo kernels was better..............Am I right?

Thanks !!

EDIT: OK, my reading suggests that Vodoo color is not yrt availaable for Gingerbread...yes? So is that the answer to 1 & 3?
[Captivate Android Development] existz:
1) auto brightness is a known problem since jvh+, its a samsung issue..there's a DIY fix on i9000 forum

2) whoever came up with the word "lagfix", well im not going to say...but its more than a lagfix, its a filesystem.. there's big debate over rfs vs ext4, but IMO ext4 is a great FILESYSTEM.. I personally get faster read/write scores with ext4 (what a filesystem should do, your probably not going to see a difference flipping through homescreens etc... but read up on the ext4 filesystem... but as far as the things that a filesystem are suppose to do, I recommend ext4.

3) actually yea we used voodoo color in earlier builds, more like what was for froyo, not Nexus S/CM7.. that voodoo color is for nexus s sources, and since CM7 uses nexS kernel sources, that's why it worked for CM7. But in later builds I changed it to Hardcores color/sharpness fix...IMO they are about the same, I cannot tell a difference, but all screens are different

Sent from my SGH-I897
[Captivate Android Development] Holmes108:
THANK YOU! lol.

I'm personally on the fence as to which is better. Personally I don't really notice a difference (on Gingerbread). But regardless of your preference, I much prefer it to be described as you did.... not simply "lagfix".
[Captivate Android Development] irishvandal:
@Existz -

Hey bro,

Doing very good with the set-up in my sig. I say it has proved to be the best personal set-up and experience since owning this Cappy.

I am having one issue though. It is random freeze/softboots. And I mean random. SMS. CAM. Movies. Settings. It does seems to follow a slight pattern of when something is selected. Not sure how much this would help. This issue has followed me under S7-v2 ROM and Talon 0.2.1, it did not show its head under S7 ROM and Kernel4.1. But it has followed me to APEX7.2 ROM and 0.3.1 1200 340mb and various other tested.

I am willing to throw this thing under some type of de-bug or log status, but i am totally inept to these procedures. If you would like to see if I can find this crazy issue for you or to see if it is a kernel issue as well. PM me with the gear links and procedures on helping out the cause.

Keep up the great work, I personally do not want to choose another Kernel.
[Captivate Android Development] harpo1:
Are you overclocking or undervolting?
[Captivate Android Development] sremick:
And yet, when I have speed/lag/performance issues... what suggestion do I get? "Try switching from ext4 back to RFS." :rolleyes:

After almost a year of lambasting Samsung for using RFS and *****ing about everything that's awful about RFS, it strikes me as odd how casually people now suggest switching to RFS as a possible solution for performance issues. How quickly we forget?
[Captivate Android Development] Koizuma:
so far still working good, one thing though existz every once in a while the phone will scale to 1 step higher then the set cpu freq. which isnt much of a big deal for me since its only once in a while thing and its only a single step from what i have seen from my cpu freq widget.

using the Big mem, 1440 version
[Captivate Android Development] rlorange:
Actually switching back and forth between ext4 and rfs will increase performance either way. For reasons hotly debated there is some sort of 'defrag' effect when converting the filesystem which boots performance but performance will degrade over time on both file systems, rfs happening faster. Hardcore subscribes to this theory /observation and has a backup then restore option in cwm to achieve the same defrag effect.

**Simply Honey3.8, Talon 0.3.2 t2 kernel1.4ghz**
[Captivate Android Development] H3llstorm:
People used to say that the world was flat and the Sun revolved around the Earth too.
[Captivate Android Development] shane87:
Not trying to start a debate, or a flame war, but I just don't buy the "defrag" theory. Defragging a hdd does wonders for the system, since putting a file all together in one place means it can read the whole file in one go instead of having to seek to a position, read two blocks, seek again, read one block, seek again, etc. Also, defragging an hdd moves files toward the outside, since hdds have faster seek times on the outer tracks. HOWEVER, these phones do not have an hdd. They have NAND flash memory, where seeks are practically instant, and there is no waiting for the read head to get in the proper position, since there are no moving parts. As for why the "defrag" effect occurs, I have no clue, but I do know that a fresh flash, or a fresh switch from ext4 -> rfs, or vice versa, does improve performance for a while. I just don't buy that it is like a defrag.
[Captivate Android Development] mrhaley30705:
It has been widely agreed that with GB, rfs was greatly improved. Some even claim that its just as good as EXT4. I personally think that with the improvements, the difference in perrformance is now down to how each performs with each system. My phone prefers ext4, but yours may perform better with rfs. It really does mean YMMV now. When the next version of android comes out, that may change. With froyo, my phone also preferred ext4. Bottom line, just try both. See which you like the best. After all, you are using phone more than I will use your phone.
[Captivate Android Development] watsa:
Agreed. The problem here is "This is how it was with froyo" mode that people dont want to give up. I really dont see any harm in trying all the available options, and see which one best suits you
[Captivate Android Development] panda703:
At first I was like eh, the other talon kernel is good enough. But WOW was I wrong, great work I love this new kernel.