yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RashaMatt:
Mine will go all the way down to zero if I let it. I have unplugged mine when it says 100 and had it immediately do a low-battery (as in EMPTY) shutdown. God knows what it would do to the battery if I just let it continue to drain - seems like the OS is incapable of reading the battery voltage in this situation.

The really bizarre thing about this bug (on my phone, at least) is that every night I leave it on the charger, and every morning -without fail- it reads 100%, and after I unplug it, it STILL reads 100%... But any OTHER time during the day if I unplug it at 100%, it immediately drops down - how far depends on how long it's been since it reached full charge.

Why morning should be different than any other time of day beats me, but it's been 100% consistent with this for weeks, and across different kernels.

It only takes mine a few hours to drop from 100% to zero, since I'm running the WiFi AP all the time. I get a much more "normal" drain when I turn off AP (1-3% per hour).

Serendipity VII build 1

TalonDEV-0.4.1-1400
[Captivate Android Development] redjersey:
is anyone having the shut down issue? I have flashed 0.4.1 few days ago and having insane shut down problem. Sometimes when I turn on the screen with wifi signal on, it will cause shut down. Sometimes it will shut down even if wifi is off. not sure if it's the common known wifi problem or UV problem. (I have already turned off OC)
[Captivate Android Development] airtower:
What are your UV settings? Most here have found you will need to tweak you settings from 0.3.X...I know I did. I was running -150 in the two lower freq steps and -125 in the middle and -75 at 1000. Current UV settings are below and seem stable.
[Captivate Android Development] Rhiannon224:
I am not OC or UV and it soft boots on me. It appears to be random, it happens when I am not using the phone. I can't reproduce the scenarios because they are so random. Still love the kernel.
[Captivate Android Development] sstarre:
Nitrality App Broken by 0.4.1 ?

I use the market app Nitrality to flash zips (kernels,modems,themes,etc) because I can select the zip easily from the explorer-like interface and then it re-boots and flashes automatically. It's worked across many test & release versions of Talon (and others). But with 0.4.1, it no longer will re-boot. I can even just select to go to recovery and nothing happens. I flashed JVP-Voodoo 2.0 and then it's back to normal. Returned to 0.4.1 (both NO-OC & 1200 versions) and it's broken again.

Could you look into this existz ?

thanks....
[Captivate Android Development] Beny The Kid:
Same thing happens with SGS kernel flasher. I only started using it because Talon first came out in TAR format and I didn't want to have to use my computer to flash a new kernel when I was using the Talon nightlies....
[Captivate Android Development] sstarre:
SGS Kernel Flasher won't re-boot confirmed here also Beny...
[Captivate Android Development] existz:
I recommend just flashing with CWM when they are zips, the installer script is setup to remove unwanted scripts, ...etc..etc.. SGS kernel flasher can cause weird **** to happen and don't recommend flashing with those. When they are in .tar format only recommend flashing with odin/heimdall

Sent from my SGH-I897
[Captivate Android Development] sstarre:
I usually do use CWM, which is why I mentioned Nitrality because it just automates the task of selecting the file and re-booting into recovery. It then runs your script to clear dalvik,etc. it just seems as tho 0.4.1 has lost the ability for an app to trigger the re-boot. If I select the file and tell Nitrality to reboot, it does nothing, BUT if I then reboot from extended power menu, it DOES run the zip that I selected. It's just that re-boot to recovery command that seems to get ignored. Hope that's somewhat lucid, at least... :D
[Captivate Android Development] tehsam:
I'm also noticing this. maybe it just needs awhile to calibrate? I flashed 0.4.1 maybe 5 days ago.

above 75%, the battery performance is equal to or slightly better than the performance I had with the Onyx kernel. then once I get around 70% it starts dropping bigtime. on the whole, my battery life is considerably worse than I was getting on onyx (froyo 2.2.1)
[Captivate Android Development] gerc86:
CWM issue

There is something strange with CWM recovery in talon 0.4.1, i tried to flash a theme and nother modification but the system never get updated.

I made a kernel backup with SGS kernel flasher, installed another kernel and now I can flash anything on CWM recovery, but I cant live without Talon kernel so i restored talon kernel with the same app.
[Captivate Android Development] existz:
Theres some zips where you have to mount /system and /data inside of CWM, under mounts and storage, its something in the installer script with certain zips that do not like voodoo initramfs...its not all zips, just some...mostly theme zips..etc..
[Captivate Android Development] mrhaley30705:
No problem with shomans or vivs ports for Continuum, for me.
[Captivate Android Development] RichMD:
I do this all the time now - it takes a few more seconds but the flash always works
[Captivate Android Development] geokilla:
It seems that Talon breaks downloading using the stock Android browser. Every time I switch from another kernel to Talon, I have to download Astro as well in order to re-enable downloading with the stock Android browser. Is there a workaround to this? It's fairly annoying.
[Captivate Android Development] VFO:
I was also having market download issues but the new market update solved that for me. Maybe try the new market update to see if that helps.

Sent from my Happy Snappy Cappy :-)
[Captivate Android Development] gerc86:
Thanks existz.

One more thing, yesterday i noticed that my screen became all green, I was scared because i thought that my screen was damaged, i rebooted my galaxy and the splash screen and everything was ok but when the system got started the screen got green again, so i flashed another kernel and came back to talondev without OC the GPU, any idea about this?
[Captivate Android Development] pixbuf:
Did you try adjusting the color using the Voodoo control app?
[Captivate Android Development] gerc86:
yes, i tried and nothing worked
[Captivate Android Development] pikachu01:
It's something to do with Voodoo color. Try reseting the setting in Voodoo color, or wiping the data from voodoo color then starting the voodoo color application.
[Captivate Android Development] zacharias.maladroit:
wait for the next test-kernel or official kernel-build

it's only a settings thing with voodoo color

I just uploaded a fix for it to the repo
[Captivate Android Development] gerc86:
Thanks guys!
[Captivate Android Development] tehsam:
in addition to the battery dropping fast once it gets below 80%, i'm having some music playback issues. there were really nasty skips/stutters on 0.3.1 and I thought 0.4.1 fixed them. however, it seems they are still there, just not as bad as before. I'm listening to music stored on the internal SD card with the app "player pro". I've tried the anti-jitter setting in voodoo control but no luck.

also note I don't have hacked volume key mapping set in voodoo. I saw zacharias posted something way back in the thread to address this- has it still not made it into the standard kernel build?
[Captivate Android Development] zacharias.maladroit:
not sure what change you exactly mean :o
[Captivate Android Development] tehsam:
sorry- was referring to this post:

http://xdaforums.com/showpost.php?p=14534674&postcount=1928

I'm having trouble following the conversation back there- not sure if this is in fact a fix for playback stuttering or what.
[Captivate Android Development] zacharias.maladroit:
that stuttering is related to limited max cpu frequency while screen is off

100 MHz is not enough with e.g. equalizer and other stuff,

200 or 400 MHz at least is needed

if you're only playing music with stock mp3 player and nothing else 100 Mhz (e.g. powersave govenor while screen is off) is enough - so no stuttering
[Captivate Android Development] tehsam:
thanks, that makes sense- so do I have any options?
[Captivate Android Development] Dlev7:
Hello.

I'm trying to figure out the bootanimation situation on my ROM. I've tried renaming the animation to bootanimation.zip or sanim.zip in system/media. Neither change the bootanimation to the custom one I'd like.

I'm on my 3.8.1 ROM. Any help will be greatly appreciated
[Captivate Android Development] watsa:
Does it work second boot and after?
[Captivate Android Development] Dlev7:
What do you mean?

Whenever I drop a bootanimation.zip or sanim.zip file into the system/media folder it just plays my SGS II Bootanimation thats named samsungboot.qmg
[Captivate Android Development] watsa:
I mean reboot it a second time and see what bootanimation it plays
[Captivate Android Development] Dlev7:
Well with bootanimation.zip on second boot isnt working right now I'll try renaming it to sanim.zip and trying on the second boot.

But this is also when I tried to include it in my ROM and package it, it did not work
[Captivate Android Development] watsa:
It will not work for the first boot, but should work thereafter
[Captivate Android Development] Dlev7:
Alright I'll try right now, I'll keep you posted. Thanks!

EDIT: It worked! You are the man!
[Captivate Android Development] shane87:
Also note that clearing cache/dalvik cache will revert to samsung bootani on the first boot. After that, it will show the custom bootani on subsequent boots. This was mentioned shortly after the release of 0.4.1, not sure which post exactly. This was done to keep from showing a black screen with no bootani after cache/dalvik cache wipes. Again, this only affect the FIRST BOOT after clearing cache/dalvik cache. Hope this clears up some confusion!

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] IDoMy0wnRacing:
The custom bootanimation does have to have the sanim.zip name. an dthey do work with 4.1.

Just asking... when you made the custom bootanimation, did you store the files in the .zip and NOT compress them? compressed file wont animate.
[Captivate Android Development] johan8:
I have the same problem.

Same sanim.zip, the custom bootanimation works in previous kernels, 0.3.x, 0.2.x,

and also work in Froyo Onix (bootanimation.zip)

But doesn't work in 0.4.1
[Captivate Android Development] harpo1:
Reboot the phone a second time and your custom bootani will come back.
[Captivate Android Development] johan8:
just flash to 0.3.x, custom animation show during bootup.

flash to 0.4.1, no custom animation.
[Captivate Android Development] Holmes108:
As Harpo said though, did you reboot a second time? It's not going to work on the first boot, that's expected behavior.

After that, it should work fine.
[Captivate Android Development] Ranulf WolfSage:
Need more sleep!

My apologies if this is not the right place to ask, feel free to direct me elsewhere if necessary.

I am currently running Continuum 6.1 with Talon 0.4.1 @1200 MHz, 100 through 800 UC'd by 25mv each and I897 GB bootloaders.

I've noticed when I go into CPU Spy, that my phone is spending 50+% of it's time running @100MHz, Deep Sleep is much lower than that. Although 1200MHz and 100MHz tend to be the most used states on my phone when it's being used, Deep Sleep has always by far been the highest percentage.

Now I know that I've read that this is sometimes caused by a rogue application, however I even have Watchdog running on the phone, and it's yet to have reported anything sucking up CPU cycles. Is there any other way to try and figure out what is preventing the phone from entering deep sleep as often as it should? Is this a known issue with Talon? Should I be asking elsewhere? I apologize if this is not the right place, but as the states are controlled by the kernel (I believe) I figured this would be the best place to start looking for answers, thanks!
[Captivate Android Development] lownox:
Phone charges at 100. Clear cpuspy and check after an hour.
[Captivate Android Development] -Thrive-:
I am running Playerpro and not experiencing stutter with the screen off. Also just used Cardio Trainer Pro (GPS on) and Player Pro simultaneously for 40 minutes with the screen off and without music playback stutter. Of course Cardio Trainer is a major CPU hog and probably pushing CPU above 100 Mhz.
[Captivate Android Development] johan8:
Of coz, reboot many times.

First reboot from recovery(cwm) till full load up,

then power off completely until it vibrate.

Power on again.... no show.

power off again and again until it vibrate, then power on.... no show.
[Captivate Android Development] tehsam:
hmm that's strange- it is definitely still happening for me. it's pretty infrequent but every now and then I hear it.

it really improved when I moved from 0.3.1 to 0.4.1, I'm hoping the same will be true with the next release.

for me, it is only a small issue. major thing I'm trying to deal with now is the poor battery life once I hit 75-80% charge.
[Captivate Android Development] sstarre:
Possibly a permissions problem ???
[Captivate Android Development] tehsam:
just experienced my music stutter issue- this time with the screen on.

thinking back, I believe this has happened previously as well. it seems to stutter when i'm doing something cpu intensive. most recently, I was signing into the twitter app while player pro was playing in the background and the music skipped/stuttered pretty bad.

anything else that could be behind this? it seems the screen being off and causing a cpu limitation is not the only cause.
[Captivate Android Development] -Thrive-:
Besides trying a different music player (Player Pro and DoubleTwist are great), you may want to get a program like Process Monitor Pro to see what's running on your phone and kill unneeded tasks. I have been experimenting with various modems to try to improve battery life. My current ROM/Kernel/modem combination seems to be eating up battery a little faster than some prior Continuum/Talon combos I have tried but I'm not exactly a moderate user so there's only so much improvement I can expect.
[Captivate Android Development] watsa:
may i know if you are on AT&T bootloaders?
[Captivate Android Development] zacharias.maladroit:
this happened before on Talon ?

if not - it might be a regression

could be related to VM, cpu scheduling or other parts in the kernel

depending on the cpu intensive task ...
[Captivate Android Development] mrhaley30705:
Remind me again, which player are you trying to use with which lock (Player pro and epic lock, right?).
[Captivate Android Development] toy028:
Im experiencing what i think is a memory leak in the kernel. It gets slow and laggy after days of usage and shows only 40MB free with only a few things running.
[Captivate Android Development] tehsam:
I'm using player pro with the 4-tab unlock. I do not have the playerpro EQ enabled, but I am using a lockscreen widget with it.

to answer another question, yes I'm on AT&T bootloaders.
[Captivate Android Development] mrhaley30705:
Which widget (try saying that 5 times fast)?
[Captivate Android Development] tehsam:
the player pro 4x4 lockscreen widget.
[Captivate Android Development] mrhaley30705:
Have you tried Player Pro with any other lockscreen?
[Captivate Android Development] watsa:
Does the music player cause a reboot too?
[Captivate Android Development] tehsam:
no- but as I said i have also experienced the skipping/stuttering with my phone unlocked.

worth a shot though- i'll try it out.

someone asked about my bootloaders- could switching to i9000 BLs fix the issue?
[Captivate Android Development] watsa:
Yep that "someone" thinks that it might be a BL problem. At least with samsung music player its a problem
[Captivate Android Development] mrhaley30705:
I am trying player pro with 4 tab and 4x4 widget and it hasn't yet. But its only timed out twice so far. I have been reading Apex thread and I know where your going:D
[Captivate Android Development] 2Quik:
toy028 I agree with you on that memory leak.
[Captivate Android Development] mrhaley30705:
Appears to be a negative on reboot. Times out like 7 times. But, you do have doubting my decision to flash 897 loaders.:confused:
[Captivate Android Development] zacharias.maladroit:
could be from the autogroup patch

it would be shame being forced to remove that

I tried to fix it on my cm7 kernel but wasn't completely successful

ported changes from pre-2.6.38 kernel back & could include the memory leak patch but in return it led to some non-functional adb (reboot) and some data corruption :p

hopefully a solution can be found - otherwise -> autogroup OUT :\
[Captivate Android Development] mrhaley30705:
Just tried your setup and couldn't replicate problem. When you flashed your rom, did you restore player pro or redownload it from market?
[Captivate Android Development] tehsam:
interesting- thanks for the suggestion. is there somewhere I can find an i9000 bootloader package to flash thru odin? also, are there any known downsides to using the i9000 BL? I know cezar had recommended the AT&T bootloaders to continuum users.
[Captivate Android Development] mrhaley30705:
Check HERE

That is Cezar's I9000 bootloader package. Watsaa also has one in his Apex flasher pack HERE.
[Captivate Android Development] existz:
If im not mistaking, theres been a few reports from awhile back (pre-autogroup patch) about "lag" after days of use with no reboot...
[Captivate Android Development] mrhaley30705:
Is it possible to go days without rebooting? Jk
[Captivate Android Development] topiratiko:
@existz...just out of curiousity is SIO still your choice of scheduler? Ive been using VR and seems better for me.
[Captivate Android Development] mrhaley30705:
+1 <><><>^^
[Captivate Android Development] zacharias.maladroit:
ok thanks for the clarification

so it could be another memory leak in the system or kernel

... or something else :\
[Captivate Android Development] cnigro1279:
+1 for me as well.

Sent from my couch on my phone.
[Captivate Android Development] csoller:
Guys, my back key stopped working after flashing 0.4.1.

Does anyone else have this problem?
[Captivate Android Development] mrhaley30705:
If the home key actually goes back, I'd say you flashed the i9000 version
[Captivate Android Development] csoller:
I have an i9000 running stock JVQ.

The option key and the home key work as they should, but the back key does nothing.
[Captivate Android Development] existz:
Are you sure you dloaded the i9000 version and not the captivate? This is the captivate thread... all i9000 versions have -i9000 at the end of the filename
[Captivate Android Development] zacharias.maladroit:
++

behavior I got once I flashed a captivate kernel onto my i9000

@csoller:

please download a i9000 kernel and flash again :)
[Captivate Android Development] csoller:
Sorry guys, you're right I feel stupid.

I got here from google, and I did not know there were 2 versions...
[Captivate Android Development] existz:
Lol, ah it happens, dont sweat it :P
[Captivate Android Development] leoriver42:
Is it ok to flash with battery not at 100%?

Sent from my Samsung Captivate running Apex 8.2
[Captivate Android Development] tmng95014:
Yes. just don't get too low. If you ran into trouble, you may run out of battery and have to recover :-(
[Captivate Android Development] mrhaley30705:
QUOTE=tmng95014;15662231]Yes. just don't get too low. If you ran into trouble, you may run out of battery and have to recover :-([/QUOTE]

+ 1 10 charac
[Captivate Android Development] topiratiko:
Is there any chance that this "memory leak" which ive experinced after 8+ hours of use has anything to do with lmk settings? i used factory task kill AND some kill all app and ram usage was still 290+ out of 340

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] johan8:
If I go back to 0.3.x, the custom animation show instantly.

it is not about permission I think.

I always get problem which most people doesn't have.....
[Captivate Android Development] zerkai:
Hey, is the ram.conf saved in a new location? I don't see it anymore.
[Captivate Android Development] shane87:
No, its still located at /etc/ram.conf like it always has been. Maybe you are looking for it in /etc/init.d?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] djinferno806:
I'm experiencing the same problem. I always have to end up rebooting after a few hours due to there being almost no free ram.
[Captivate Android Development] pikachu01:
I do experience this lack of memory (free memory was around 30MB causing major lag) with both the old preset and the new preset. Rebooting solves the problem.
[Captivate Android Development] krisvek:
I experience stuttering and laggy behavior in general when there is an active sync being performed.
[Captivate Android Development] -Thrive-:
+1

I have noticed ram usage creeping up over time (using process monitor pro). Wiped Dalvic cache and cache partition and rebooted and got maybe 50 mb back.
[Captivate Android Development] kodos96:
Well there is an actual issue here - I've seen it myself - but I'm pretty sure it's not related to LMK, cause when you do a "kill all" in a task manager or whatever, that pays no attention to LMK settings and just kills everything... and the issue is that after doing a "kill all", the amount of ram free, with no user apps running, decreases over time.

LMK controls how many user apps to keep open at a time, so if the problem happens even with no user apps running, then it doesn't have anything to do with LMK. I currently have no idea though what IS the source of the problem... not sure if it has anything to do with Talon or not (but it might). Has anyone seen this on other kernels?
[Captivate Android Development] Jep56:
existz, thanks for the work on the kernels...donation confirmation # 36P609841W9034226
[Captivate Android Development] irishvandal:
okay, finally going to make the jump to JVQ. The JVP set-up was very solid and is going to be my new CWM back-up from here on out. The lag issue was seen but did not impair my ability to patiently wait for it to work its magic which gave the same performance as it should of when i waited. A re-boot did refresh the i897 to its glorious performance. wondering if it may be a scheduler issue(just a two cent opinion), since when i waited it did give the same performance as it should have.

i am gathering together the flash pack right now and will flash today or tomm depending how my freakin algebra test goes tonight.

existz - talon is becoming very-very solid brotha. keep up the good work. i am hoping to buy you a beer or two this w-end or next.
[Captivate Android Development] eccezarathustra:
KSwapD

Just a note, was using Talon (dont know exactly which version, whatever is packaged in Apex 8.2) and I noticed that kswapd was spiking into the 30% range constantly. Causing a lot of lag and a lot of battery drain.

I can't say what the cause is, but I do remember this from SuckerPunch unfortunately.

I did a quick search on the forum to see if any one else posted this but apparently not.

If you need something from me, let me know. I'm running xcal's i9000 reoriented now but i can switch back if need be.
[Captivate Android Development] zerkai:
Im looking in the right spot, it's just not there. Im on a fresh flash of apex, i even reflashed the latest talon kernel (0.4.1 1200 bigmem) with system and data mounts but I still don't see it.