yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] fractaline:
Lol, talon has just been chiki'd...

Side note..... Only 24 hours up so far on 0.2.5.2, oc 1300 w/thunderbolt tweaks.

F'n awesome ... Hasn't been this fast and stable since onix.

Many thanks, existz , pica and the rest!

Sent from hither to thither
[Captivate Android Development] irishvandal:
glad to help out. not a dev or even a pro. just a noob with to much hands on and way to many questions for these devs. lol. hope it all works out for you, let me know if you need anymore help.
[Captivate Android Development] ChikiBujia:
Ok, I had to go back to stock GB because of a problem I had with another kernel :( but I am back :D

I followed the instructions in all those links, and Talon is now running on my phone alongside the thunderbolt tweaks :D

I UVed this time as well to give more stability to my phone :D

Thank you so much again for all your help!!!!!

:D
[Captivate Android Development] murauder:
Long time user of talon (since I first rooted my cappy. Like 3.1 or something). I been experiencing sleep deaths (phone shut off in my pocket all the time). Did it on mosaic 6, 7 and 8 and apex 9.1. With or without oc/uv. Tried all sorts of variations of uv and oc. The best so far was latest talon running the 1120 oc script no uv on mosaic 8. Got almost 48 hours. Only happens when phone isnt being used for a while. Happens on darkcore too. Any ideas?
[Captivate Android Development] mrsubway:
I had the same issue. I was using a cheap Ebay battery. Went back to my oem battery. No shutdowns in two weeks.

Sent from the warranty violation of a kickass Cappy. Mosaic/Talon. FTW
[Captivate Android Development] murauder:
Same battery since ive had my phone (about a year). So i dont know?
[Captivate Android Development] The Sonos:
I was on stock kernels for mosaic and started getting sleep deaths with M8. Got on talon and it was still happening. I had not had lagfix enabled since M6 (worked smoother without), enabled it last night and I have not had one yet *crosses fingers* don't know if it means anything but I thought I'd throw it out there.
[Captivate Android Development] shane87:
Can you check the hardware build version? It almost sounds like the hardware-related sleep death issue that was prevalent in earlier builds of the devices.

To check your hardware build, if you don't know how already, simply pull the battery out and look at the label that lists the imei and other serial numbers. Their will be a number labled Hardware Build, or something similar, it has been a while since I looked at mine, but the number will be four digits, with the firsr two signifying the year that it was built (10 for 2010, 11 for 2011) and the last two signifying either the month or the build batch, I'm not sure which.

Anyway, the problem seems to have been fixed by hardware build 1008 or so, so if your build is earlier than that, you may need to speak to Samsung about the possibility of a warranty replacement. I am runing build 1101, and have never experienced a sleep death issue.
[Captivate Android Development] gokartracer5:
Been running the Talon Kernel (0.5.2.5 BIGMEM) now for a couple days, default settings. Not sure if what I had was a sleep death, it was just that I couldn't unlock. I could call my phone and it would ring, i just couldn't answer because I couldn't unlock. I also noticed it didn't sleep at all for a while and the battery drained more than usual.

So, I am not sure it's a kernel thing or not. Never had this happen before Mosaic 8. It happened with the DarkCore Kernel too.

EDIT: btw, it doesn't say Talon in the Kernel version of the about screen.
[Captivate Android Development] murauder:
My cappy is a 1009 build. The battery says it was made 9/9/2010.

Idk what tge solution could be? Hopefully when the next talon release comes it will be fixed.

On a side note paul diddys black and blue xda app and blue rope light Swype look awesome with the stock mosaic 8 theme
[Captivate Android Development] shane87:
By unable to unlock, do you mean that when you awoke the phone you had no unlock controls? I have seen an issue similar to that across every rom/kernel combo I have tried on gb, including the leaked i897gb roms. If the phone just will not wake up, i.e. the screen won't turn on, then it sounds like a sleep death, although I have never heard of a phone in sleep death ringing, but then again, I don't know if anyone tried calling their phone when it was in a sleep death.

Those having issues similar to sleep death, try lowering the uv setting on the 100 & 200 mhz steps. I know some people were able to prevent sleep deaths by lowering/removing uv on 100 & 200mhz steps.
[Captivate Android Development] pikachu01:
Sleep death occurred to me due to misbehaving apps like the XDA app actually. Try looking at BetterBatteryStats and see which app unusually consumed the most battery (or one of the most) .
[Captivate Android Development] existz:
Also those with sleep death, try lowering UV on 800mhz as well.. as the deep sleep detection patch limits Max clock to 800mhz during sleep.. this can have an effect on things.. Also, those with deep sleep issue, does it happen on both 0.5.1-RC1 and latest test, or just the latest test?
[Captivate Android Development] gokartracer5:
So should I use the control freak app or the scripts to lower the uv.

Sent from someone else's phone
[Captivate Android Development] fractaline:
The app.

Sent from hither to thither
[Captivate Android Development] irishvandal:
+1 on PDiddys Black Swype.

havent come across sleep death myself, but the ring of death? oh yeah, bunch of times. but when i get the mad scientist death ring and wont stop for jack, it seems to pop up after a restart and generally when something like a missed call, voice mail or unchecked sms was in the system. happens once in a while and i just recheck all those and restart again and it does its job. Bamboo/Talon has not yet done such an act. just two cents.

btw, thanks again shane.

and existz, flying smooth. nothing abnormal under 0.5.2.5 1200oc, stock uv sets.

---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------

you should run Control Freak, it is the rec app for file reading reasons. i prefer SetCPU. however in SetCPU i cannot change my scheduler.

but yes, using an app is hella easier for the noob, almost noob, and general noob.

Most of us basically. lol.
[Captivate Android Development] gokartracer5:
I have only tried the latest test mainly because I was hoping it took care of the memory leak from 0.5.1. Should i give that a try instead of tweaking the latest test?
[Captivate Android Development] pikachu01:
The latest test is more stable than the latest version. The latest test doesn't have the memory leak as well. Been reported by many to be lag free for days.
[Captivate Android Development] gokartracer5:
I do really like the latest test myself. It seems very stable. I am only concerned about attempting to tweak it alot to keep it from sleep deaths or whatever the unlock issue is. It's not a sleep death, but more that i can call the phone an get a ring, just can't unlock it to answer. Very strange. I will try the suggested lowering the UV on 800MHz to see if that helps. Other than that pretty smooth and stable.
[Captivate Android Development] pikachu01:
As I've mentioned, sleep deaths are usually caused by rogue apps. These rogue apps drain battery while the screen is frozen. You can check it by using BetterBatteryStats. It will drain as long as the screen is frozen. The culprit is usually apps like the XDA forum app (happened to me before). Removing it got rid of sleep death.
[Captivate Android Development] gokartracer5:
ok i will give that a shot thanks.

---------- Post added at 09:39 AM ---------- Previous post was at 09:06 AM ----------

It seems like wifi scan is on 100% of the time and I am not using wifi. Strange. Otherwise I don't see any apps causing a problem.
[Captivate Android Development] gokartracer5:
OK. So, here is what I found after installing BetterBatteryStats.

No particular application process seems to be stuck on, I tried leaving XDA in the cached processes and deleting it from the cache with no effect.

Awake is about twice that of Screen On

Wifi Scan seems to be on 100% of the time when it was turned off all day except for the hour I had it off the charger before I left for work.

Battery drain seemed pretty bad until i toggled wifi on and off after installing the app

Are there any other tests I could run?

didn't try setting UV yet. No sleep death or screen lock issues so far. No lag or slow downs yet.
[Captivate Android Development] froli13:
lol..

10char
[Captivate Android Development] existz:
If you can make it work I will :P...j/k ...BLN does not work with i9000 gingerbread, been messing with it some but will probably have to wait till neldar finishes it up for i9000 2.3, hes working on it so hopefully its soon..

/end of topic for this also

Guys

PLEASE

read

atleast

the last 5 pages before posting a question...its just forum etiquette...the last few questions ive seen have already been answered multiple times
[Captivate Android Development] CuriousTech:
Another problem is that it changes the device ID like crazy causing Windows to load different drivers. I know someone mentioned to start Odin after putting the phone in download mode and plugging it in. That may get it to connect right, instead of having it switch drivers while Odin is running, screwing up its open handle to the port.

On the other hand, SGS kernel flasher has been working well for me.
[Captivate Android Development] shane87:
Hmm, very odd. If you used vcex to save the boot settings, it could be due to a bug in vcex that messes up the states enabled tab. I think I have vcex fixed, I just need to test it on froyo to make sure I didn't break it on froyo, but I have gb, and I don't want to go back to froyo. So as soon as I can get a few testers with froyo, I will be releasing an update to vcex that could fix the issue causing boot settings not to stick. I will look into it, though, I haven't tried to save boot settings yet on gb. Oh, and if the file is in /etc/init.d, it will also be in /system/etc/init.d. /etc is a symlink to /system/etc, so if you write something into /etc, the kernel will reinterpret /etc to be /system/etc.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] stinkynoon:
I'm having the same problems with it saving the boot settings. I tried reinstalling busybox, but I clearly did it very wrong. Now I have a buttload of "/sbin/ext/busybox" in my processes when I look at OS Monitor. My cpu is maxed out trying to deal with that. Is there a way I can end that?
[Captivate Android Development] shane87:
Reboot. I had the same issue when trying to re-install busybox. With a reboot, everything settled down. The reason it freaks out, is due to you not mounting /system as rw. If you mount /system as rw, it will not freak out, and it will install correctly. I am having no problem with my boot settings sticking. I also have a working version of VCEX for gb! I just need some testers for froyo, so I can make sure it isn't broken in froyo.
[Captivate Android Development] stinkynoon:
I tried rebooting several times and it was still silly. :( I think I know enough of linux to understand what you are talking about...it was trying to write somewhere that it was not allowed, so it kept on trying--hence the multiple instances? I ended up reflashing Perception (since I hadn't had it long, and it isn't hard to set it back up) instead of actually trying to solve the problem like I should have.

I've clearly already hopped to gingerbread, or I would have loved to tested VCEX for you in froyo. I gather you figured out what the problem was that you were having with the states and such when modifying the program for gingerbread?
[Captivate Android Development] shane87:
Yeah, well, chainfire pointed me in the right direction. The states tab still disappears occasionally, maybe one out of ten times, but it is much better now.

And I wasn't asking you to test vcex on froyo, I kinda figured you had gb, lol. I was simply stateing the fact that I need froyo testers for vcex before I am comfortable releasing the update to vcex.

And as far as updating busybox, I wouldn't worry about it too much. I actually reverted to the older busybox trying to fix vcex, and I am having no problems using thr old version. Of course, if you can get busybox to update, having the most up-to-date software is the best policy!

ROM: Perception II beta 2

Kernel: TALONDEV 0.1.4, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] FeO2:
Try the busybox installer from jrummy16 found in the market. the other updater doesn't seem to create proper symlinks. this fixed my uv settings not sticking problem
[Captivate Android Development] PhillyFlyer:
Just a noob question but I flashed talon 1.2 with CWM and now the latest releases are .tar and require Odin. Why is that? Why can't we use CWM anymore with a zip file? Thanks.
[Captivate Android Development] harpo1:
It has something to do with odin installs different stuff (technical ****) and CWM doesn't. Which is suppose to be safer. You can install tar kernels with sgs kernel flasher from the market.
[Captivate Android Development] dsmitty166:
Just use sgs kernel flasher. It allows you to flash tar kernels
[Captivate Android Development] dsmitty166:
Beat me to it
[Captivate Android Development] PhillyFlyer:
Thank you. did not know this. Big help.

mobile captivation
[Captivate Android Development] neubauej:
That and Odin is hardly difficult to use...

Thanks for the kernel.

Just reporting that voltage settings dont stick on reboot here either with busybox 1.18.4
[Captivate Android Development] fatttire:
CWM zip for the kernel? :D
[Captivate Android Development] Shammyh:
Jeeze. You didn't read like 4 posts back?

You don't deserve an answer, but I'll give you one anyway:

Currently, it's considered "safer" to flash kernels with ODIN as opposed to CWM. Hence there is no CWM version available at the moment.
[Captivate Android Development] kodos96:
talon-bigmem

temporarily withdrawn
[Captivate Android Development] meadhros:
Keep forums friendly. But please keep them smart. Read and read and read again the OPs. What you need to know is there. If you have a question...someone else probably does or did. Search it....use google and link it to your forum app. It is frustrating when a question is asked over and over, but it is disengenous and disrespectful to ridicule someone on a forum from behind a login. On a side note....about time. 10 years of anxiety....hopefully a little resolution for some who can get it.
[Captivate Android Development] harpo1:
Amen brother Amen. 21 year military veteran here who lost a couple friends in 9/11 and many in the Middle East.
[Captivate Android Development] IDoMy0wnRacing:
I am having the sleep death issue with the latest test only;TalonDEV-0.5.2.5.

I did not have it with TalonDEV-0.5.1.5-1200 or with TalonDEV-0.5.2.3 with the oc 1200 enabled.
[Captivate Android Development] reinbeau:
Actually it's back here for me, too. I'm on 0.5.2.5 BIGMEM. It was fantastic for a week, now it's sleep deathing again, and my DVR widget issue is back :(
[Captivate Android Development] pikachu01:
The test version changed the CPU frequencies to accommodate the OC module. With that, you should not UV your 100MHz too much until a sleep death can occur. Try increasing your UV of 100MHz by 25mv. It works well for me :)

What DVR issue?
[Captivate Android Development] reinbeau:
I don't OV or UV anything, I've never found a good guide to tell me how to do it (I am not 'geeky' enough, I guess :o). I just use the kernel. I posted a picture earlier in the thread of what happens to my widgets, it stopped for a week after flashing this newest version, now it's happening again.
[Captivate Android Development] pikachu01:
I'm afraid to say this but the XDA app was what caused my sleep death the last time around. Installing Tapatalk and uninstall XDA app resolved sleep deaths for me.

You can check BetterBatteryStats to see what apps are consuming the battery. Once I had a sleep death overnight, I checked that the XDA app was consuming CPU cycles much more time than the time I had my display on. That was a telltale sign.
[Captivate Android Development] Elad92:
Hey,

I used the latest kernel with 1300 oc (0.5.2.5)

I have some questions:

1. What was the settings in the previous version of the kernel?

Because now my phone becomes laggy after few days when in the RC1 version it lasted for a week.

2. I've downloaded the control freak but didn't find how can I overclock the GPU :S

3. I'm working on my under voltage settings now, can someone share a good values or teach me how to set the values correctly?

Thanks!
[Captivate Android Development] gokartracer5:
I seem to have really good battery today after uninstalling a couple apps that seem to want to startup on their own alot. I still seem to have wifi scan and wifi lock at 100% even when not using wifi, but now it doesn't seem to be a problem. It mst have been those apps. Really didn't need them anyway. XDA Premium doesn't seem to be a problem, but i have been manually removing it from the cached processes anyway.
[Captivate Android Development] pikachu01:
Try setting swappiness and ZRAM size to 0. There's still a memory leak in the compcache.

There's no way of overclocking the GPU. The initial code to do that is buggy, hence it was removed.

See my Android Optimization Tips and look for undervolting.
[Captivate Android Development] geokilla:
Would it be possible for someone, aside from existz to compile Talon without ZRAM/swap? I know existz has been really busy lately as you can tell from his activity on XDA here. I think Talon is still one of the best kernels, but it will never be the perfect kernel for many simply due to the memory leak caused by ZRAM/swap. Not everyone needs ZRAM/swap, nor do they need the added multitasking ZRAM gives.
[Captivate Android Development] studacris:
^^^Why don't you just turn both zram size and swappiness values to 0?
[Captivate Android Development] geokilla:
Memory leak still exists from what I've read. I've been using Semaphore and not getting any slowdowns or lags or memory leaks, aside from today when I got some abnormal crazy lag.
[Captivate Android Development] pikachu01:
Nope, flolep tried the swappiness to 0 and ZRAM size to 0 and it completely solved his lagginess for him after more than 72 hours of uptime.

It is actually possible to use that configuration to avoid the second cause of memory leak = ZRAM. The first cause, LMK was solved when using ThunderBolt!'s LMK.
[Captivate Android Development] AceofSpades90:
A quick question.. am i the only one that cant run firefox cuz it lags to death. it takes half an hour to load then suddenly it closes on its own after opening tiny fraction of sites(like one? psh lol). The phone lags even more even after shuts itself down...??!!!

Please confirm this because i don't think its memory leak anymore... I was thinking its Firefox poor coding? xD

P.S: my phone sometimes freeze and restart if i try to use samsung builtin task killer (I know this is because talon uses swap and it may not be supported as existz mentioned earlier??)
[Captivate Android Development] reinbeau:
I deleted Firefox for the same reason, it was just too laggy and slow.
[Captivate Android Development] watsa:
nope freeze is because u r using tw4. use another launcher and then try and use task killer. i can bet there will be no freezes
[Captivate Android Development] Elad92:
Thanks!

Another question,

After I've OCed to 1300, I started using SetCPU.

I've made a profile that tells the phone to use 100 min 400 max and ondemandX scaling.

When I'm using the 3G data and the phone is idle, it's holding up just fine, but with wifi it draining my battery very fast!

Did somebody else notice that his wifi drains his battery?
[Captivate Android Development] irishvandal:
I don't receive crazy WiFi drains(unless i am testing and tweaking and something gets hung up) with Talon. BTW, WiFi is also impacted by ROM. IT could be scanning like crazy. It could be in ur settings for GPS, location, sensors, etc. check all those out in ur settings. Compare usage currently to new settings if any. Poss reflash. Talon is solid, minus a stupid lag bug, but its getting dealt with behind the scenes. But i have heard that ondemandX is a little crazy red-headed step child. I believe the OP has a reference to ondemandX, not saying thats even a wifi issue, but something to mention.
[Captivate Android Development] Elad92:
Changed to ondemand, solved the problem.

Thaks :D
[Captivate Android Development] upNsmokeAllDay:
Bump
[Captivate Android Development] aalh:
HUH??????????
[Captivate Android Development] Sqb:
Keeping the thread moving and in the top portion.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] existz:
Thanks for the bump guys... i should have an update soon, been a little busy lately but once it settles down ill get an update rolled out
[Captivate Android Development] pikachu01:
Hey existz,

The wifi issue starting from XXJVS isn't resolve by the init.rc fix I did :(

I'm now delving into the Platform source code to see what changed in terms of wifi conf/supplicant etc.
[Captivate Android Development] Sqb:
@Existz nice to see you going green! Looks good on you

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] shane87:
I'm running Contiuum 6.1, with a custom build of Talon, using the xxjvt initram, and I have no wifi issues. I just double checked and toggled wifi on/off 8 times using the power control widget in the notification drop down and it always turned on or off with no errors. The only possible wifi issue I have seen on jvt is occasionally wifi will be turned off at boot, even though it was turned on at shutdown. And that usualy happens on boot following a kernel flash, after wiping cache/dalvik-cache.

[EDIT]I spoke too soon, lol. Right after posting, I toggled wifi twice, and the second time I turned it on it freaked out. I guess I haven't noticed it yet because I don't toggle wifi often, usualy off once and on once each day. Off when I leave for work, and on when I get back home.[/EDIT]
[Captivate Android Development] funkym0nk3y:
ummm, i flashed talon kernel 0.4 previously which wasn't working (fasty, cognition)

even 0.5.1 isn't working, any compatibility issues ? (srry for being a noob :P, however no change of soft-bricking the phone-Unbrickable so you can free suggest different methods to make it work)
[Captivate Android Development] pikachu01:
The wifi issue I'm talking about is not the toggle wifi issue. It's the disconnected wifi every few minutes issue.

Only way to workaround this is removing the address reservation setting and setting the lease time to something other than forever.

What compatibility issues are you facing? Details?
[Captivate Android Development] existz:
If your talking about flashing talon on cognition (or any other i897 sourced roms) it will not work. .. talon is an i9000 reoriented kernel , ment for use on i9000 based roms (jvr-jvt-jvs.. etc) such as Apex.. etc
[Captivate Android Development] funkym0nk3y:
yes, i mean if i install talon kernel along with fasty or cognition, phone stucks in a bootloop,

ohh, can we hence use talon with i9000 modem flashed on any rom ?

EDIT: lol i think m wrong :p
[Captivate Android Development] pikachu01:
Reoriented kernels are different from Captivate native ROMs is my best guess. If you want to use Talon, you'll have to go for reoriented ROMs as well.