yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] henge:
understood! either way, you're doing a great job! Even if I try other things I always come back to Talon
[Captivate Android Development] shane87:
Just came back from Cog5. I forgot how great Talon is!! Running 0.4.4.22 BIGMEM 1200, and it is great!! SO far no issues. Well, one minor issue. After flashing Continuum 6.1 and Talon 0.4.4.22, then restoring apps ONLY, pus my contacts, sms/mms, and wifi settings, I went back to my home screen, Go Launcher, and proceeded to fix my widgets, since they always have to be replaced after every restore. I then rebooted, to get my contacts and sms/mms to show back up, followed by a flash of RedGingerbread for Continuum 6.1. I noticed that my wifi and auto rotate options were disabled, so I enabled them from the Status bar. After closing the status bar, two of my widgets disappeared, showing a little box that says "Problem Loading Widget." I am going to try toggling those two switches, individually and at the same time to see if it is reproducible. Im not sure if it is due to kernel, rom, or theme. However, it is a minor inconvenience, and im not complaining, just letting the devs know what is going on!!

[EDIT]I just finished a reboot, applying voodoo ext4, and now my main home screen is empty. My other two screens are still full, only the main screen was affected. Weird.[/EDIT]
[Captivate Android Development] morpheus_1987:
Phone Rebooted

My phone was sitting on my table for 2-3 hours and it rebooted on me. I'm running the 1.2GHz of 0.4.4.22 but if it was idle, it shouldn't be due to the O/C right? CPU Spy does show that the phone goes into deep sleep. I'm don't have much of a lead as to what caused it.:(
[Captivate Android Development] existz:
Yes, it can still be from oc/uv, might try adjusting voltages some
[Captivate Android Development] pikachu01:
Restoring widgets in Go Launcher has always been a problem for me for a new flash. You should readd your widgets manually. Never had an issue after that.
[Captivate Android Development] shane87:
Yeah, I have always had to readd widgets manually after a flash, that's not the issue. The issue is, two of them disappeared when I toggled auto-rotate and wifi on with the status bar controls. And then everything, including three widgets, two shortcuts, and four application launchers disappeared from my center home screen after a reboot to apply ext4.

I just rebooted, due to seeing the android system drain bug, and it did not affect my home screens. I also tried various combinations of disabling/enabling wifi and auto-rotate from the status bar, and nothing disappeared this time either. Very odd.

One other thing I have noticed is that my wifi is always off after a reboot.

This is still a great kernel, just trying to get to the bottom of these minor annoyances.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] nh5:
Running smoothly on DlevRom 5.0 with .22 1200Mhz, Got mem freak set to Nexus S settings and ZRAM at 160 with Swap at 50%
[Captivate Android Development] edtonn:
FYI flashed .22 this morning (about 13 hrs ago) and everything's working great. Switched to Nexus S LMK settings and haven't experienced any lag whatsoever. So far so good!

Edit: Running 1000mhz 240mb kernel
[Captivate Android Development] Kyuta Syuko:
Well it's been a little over a day running 4.4.22 No OC/UV and no Big Mem with topiratiko's LMK settings and I'm happy to say it's been running as smooth as can be expected. Nice job. I've been afraid to flash TalonDEV because the last one I flashed (4.4.9 I think it was) made my phone unusable. Would lag whenever I would run just about any app. Glad that's not the case this time :D
[Captivate Android Development] morpheus_1987:
I'm not UV at all though and the only OC is the top state. Sadly the version of Voltage Control that I have only lets me UV not OV.
[Captivate Android Development] geokilla:
Incorrect. It still shows 100% when the charge bug kicks in while the phone is off. I turn off my phone while it's charging and it said 100%. Turn it on and unplug it, wham! 50%. Now I'm not sure if it'll last me throughout the day at work till 5pm. :mad:
[Captivate Android Development] pikachu01:
You charged it while the phone is off (and it shows 100%)? Never experienced that before. Try swapping your battery with someone else's. You might have a faulty battery.

And the kernel only changed the indicator when the phone is turned on. When phone is off, everything runs off the bootloader, hence it's not kernel related.
[Captivate Android Development] watsa:
Did your phone ever charge? I have never seen and heard of 50% drop
[Captivate Android Development] geokilla:
Yea it charged. I had low battery last night. I didn't check my phone till like an hour after I unplugged it. When I turned it on I didn't check the battery level, so maybe it was at 60% instead of 50% when I unplugged it.
[Captivate Android Development] cnu4u:
After 33 hours, I had to power off and on the phone to make it better...
[Captivate Android Development] pikachu01:
What settings are you using for MemoryFreak?
[Captivate Android Development] cnu4u:
Nexus S with 50% swappiness...
[Captivate Android Development] existz:
Again, that's the memory leak.. no LMK settings are going to fix it ...we are aware of it and still working on it
[Captivate Android Development] topiratiko:
@Existz. When i encountered leak yesterday...i cleared memory and used a task killer and only had like 50 free....then i launched browser, fb, and xda, then cleared everything again with both task managers and number free jumped to over 100. Could it be one of those apps not completely clearing or something?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] cnu4u:
Thanks. I am aware of this and I just want to say its better than before....
[Captivate Android Development] topiratiko:
To anyone that gets the mem leak, when u get mem leak, launch fb,xda app and browser all at the same time, then go to task manager active applications clear them AND clear memory. If its confirmed that that brings ram usage down maybe it can narrow down what existz & co have to look at

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] CuriousTech:
That's about what I'm seeing. It charges up to 99%, then discharges to 80% and then charges back up to 99% but doesn't know it's charging. It's probably a voltage level trigger that kicks it back on but doesn't change the charge status.
[Captivate Android Development] Koizuma:
So far my memory issues seems to have been resolved with about 19 hours of up time woke up this morning with 100+ free MB of ram.where any other time it would be like 40MB

Swyped from my SGH-I897 using XDA App
[Captivate Android Development] carey:
Hmm, stock wall charger?

I just had this happen. Have the stock charger, and a usb cable plugged into an adapter for my standalone battery charger. Mixed them up and woke up to 50%

Can't remember if that was the case last time I saw the bug or not though.

I came, I saw... I left confused
[Captivate Android Development] iXNyNe:
@existz

In regards to ondemandx using the nonstandard file location (so the advanced tab in setcpu shows all -1) do you think a symlink would work to trick setcpu into reading the correct values?
[Captivate Android Development] mpencexda:
I think it would... I set / as r/w and used an ln -s to set one up real quick.. You would need to setup a boot script or find mount tab file.. To make it stick beyond reboot...

sent from an alternate reality
[Captivate Android Development] rlorange:
@Existz For me, personally, rebooting my phone once or even twice a day is a small sacrifice to make in order to enjoy so many apps staying in memory. Talon with zram is the king of multi tasking kernels.

Perhaps as a stop-gap it would be possible to somehow disable zram, clear ram, re-enable zram from the android vm via a module as a super memory clear app that everyone seems to want?... probably not possible without a soft reboot but a soft reboot is quick :)

Btw isn't a regular reboot good for any os platform? Whether a clear memory leak or not my phone has never ran well after days without a reboot on any version of android. Not to mention windows. Only win7 seems to run just as well... er badly indefinitely.

Edit: I played Asphalt 6 for hours on end yesterday and clocked it. As well as testing oc stability I witnessed the memory leak first hand as I saw performance deteriorate across the board. Still I wanted to reboot to let my phone cool down! And charge the battery .... three times!!

**Simply Honey4.0 JVP, Talon kernel & Tegrak OC app 1.38ghz@1335mv**
[Captivate Android Development] rlorange:
Yep many phones will find 1300mv more than enough for 1.2ghz. Mine can run 1.3ghz even lower than this at 1280mv and 1.2ghz at 1250mv. 1300mv is stock value to please the majority. An unlucky few might need more than 1300mv

**Simply Honey4.0 JVP, Talon kernel & Tegrak OC app 1.38ghz@1335mv**
[Captivate Android Development] mpencexda:
Android is unix.. Unix doesn't require reboots.. Lol.. I agree with you but the beauty of this os is it will can and will be better than that given enough work

sent from an alternate reality
[Captivate Android Development] mrcpu:
open the terminal app, su, then do an ls /bin and find the script that creates the ramfs. I don't have my phone in front of me, but the name is obvious.

Then just run it at the su prompt inside terminal.

# /bin/whateverthescriptnameis

That's it.
[Captivate Android Development] RashaMatt:
Good news - on .21 and .22 I am no longer experiencing the charge bug (discharging after reaching full), ever. I switched from Serendipity VII to Dlev starting with .20, which could also be a factor.

____________________________________________________________

AT&T Captivate SGS I897, Dlev ROM 5.0, TalonDEV 0.4.4.22, KC1
[Captivate Android Development] eliminat:
Geek nitpick - technically it's not Unix, it's Linux.
[Captivate Android Development] shane87:
+1

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Kyuta Syuko:
Isn't Linux based off Unix though? Kinda like how Windows before XP were based off DOS?
[Captivate Android Development] Coak5:
It has been 4 days since I have been on .22 and I have gotten the charge bug everyday and everytime I charge overnight. It would be fully charged and I would unplug and the battery would drop to 90% and even sometimes 85%. Never had this problem with .21 .
[Captivate Android Development] zacharias.maladroit:
actually windows xp is based on windows nt 4.0 and that on the other side on windows for workgroups, etc. (right ?)

but we're losing focus

so back to topic !

shall we ? :D
[Captivate Android Development] pikachu01:
Nothing was done from 0.21 to 0.22 regarding the charger and its indicator. You've probably installed something that drained the battery overnight.
[Captivate Android Development] tmng95014:
Hi, I am running Apex 9.2. Tried to flah talon 0.4.4.22 and got caught in a boot loop. Please help!
[Captivate Android Development] Dungeon47:
Did you remove any ramhacks you might have had?

Were you running a different lagfix before?
[Captivate Android Development] tmng95014:
I am running plain Ape 9.2 with Darkcore kernel 3.1. No ramhacks no lagfix. And got caught in bootloop
[Captivate Android Development] Dungeon47:
Do you have another kernel on your phone you can flash to?
[Captivate Android Development] CuriousTech:
It's just not lying to you now. Give it time. It will run down to around 80% then back to 98-100% before switching to external power. It could be a battery health test for calibration AFAIK. It just doesn't indicate charge during the 2nd run up.
[Captivate Android Development] tmng95014:
Yes, I try to flash Darkcore 3.1 which comes with Apex 9.2 BUT it i still bootloop.

i am thinking may be to reflash Apex 9.2
[Captivate Android Development] Dungeon47:
That's what I would do. If both kernels are looping you have something else going on there.
[Captivate Android Development] tmng95014:
Re-install Apex 9.2 worked. Install Talon 0.4.4.22 again.

Working! Don't know what happened...
[Captivate Android Development] Dungeon47:
Been there many times, friend. Not with boot loops specifically, but with things working the second time for no apparent reason. Our machines are more like us than we realize.
[Captivate Android Development] surfed.tk:
Amen.
[Captivate Android Development] WickedNite:
I'm running Continuum 5, I need to convert system file to ext4 right? Cos it says rfs on the ext4 app.

Captivate, Serendipity, XDA Premium
[Captivate Android Development] harpo1:
If you want ext4 then yes. Use the app ext4 it was included in rc3.
[Captivate Android Development] WickedNite:
Ext4 is better than rfs right?

Captivate, Continuum, XDA Premium
[Captivate Android Development] harpo1:
Depends who you ask but I think so.
[Captivate Android Development] meadhros:
Is anyone else using spb shell? On the 1.3 talon with cont. Rc3. Having an issue where it eventually seems to use up all my resources and locks up phone. Runs sharp for a while and then simply scrolling app drawer freezes up.
[Captivate Android Development] nybmx:
I don't think anyone would say rfs is better. Even samsung themselves are no longer using it as they are releasing the S2 with ext4.
[Captivate Android Development] rlorange:
@exitz thanks for helping me get your kernel running... testing now and its amazingly fast and smooth! Wow! Oct/UV seems totally stable already... only issue is a mysterious problem with ext4... which I'm sure ytt3r will work out. So for now no ext4.

You guys are going to be superstars when Talon hits our forum... hope you dont ruffle any feathers or bruise any fragile egos ;)

**Simply Honey 3.1, Talon i9000 test kernel OC/1.2Ghz, JVK modem**
[Captivate Android Development] iwapu:
wow, super kernel. Do you consider adding BLN?
[Captivate Android Development] amarpatel:
I think he already mentioned that he's working on implementing it. I too am looking forward to it...lack of BLN is the only thing keeping me from flashing this and a nice gingerbread ROM
[Captivate Android Development] Grandelama:
I'm using 0.1.3 with the latest MikeyMike's GR-10...everything works fine but it seems that every time I reboot I lose all my Voltage Control's settings.

I tried to update busybox to 1.19, to change its installation folder, to remove settings from VC + reboot + remove voltage settings from CWM then reboot again and obviously to reinstall the kernel via Odin a couple of times, but no luck...

I didn't have this problem on Continuum5.

EDIT: it seems that no matter how and in which folder I try to update Busybox through Busybox installer. after a reboot busybox v.1.16.2 returns back in /sbin...it's probably something rom related, like the original version of busybox is getting restored upon reboot

EDIT2: just for the record, I finally solved upgrading busybox through another app, busybox installer by jrummy16. Now Voltage settings are kept correctly after reboots
[Captivate Android Development] froli13:
I think I have found a part of solution to my battery drain problem. Running Cpu Spy for a couple of days now and I just noticed that the most used state is 100mhz (with 94%-8:16:58) when Deep Sleep got 0% with only 0:03:23. All other steps have the similar usage except 1200mhz with 0:34:02 (6%).

Is it cause by the kernel, rom, apps or settings? My phone is configured the same way it was with froyo, but I had no problems concerning battery with froyo.
[Captivate Android Development] LNJ:
Mine goes to deep sleep just fine on all versions. Did you flash via Odin or kernel flasher?

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] GGXtreme:
Any chance of Speedmod/Suckerpunch/Onix-style screen color tweaks? My screen looks pretty awful with Voodoo color, it's a gradient from brown to pink to offwhite.
[Captivate Android Development] froli13:
Odin. I never use kernel flasher.
[Captivate Android Development] existz:
Also take in to consideration that deep sleep is not actually a "state" like 100 or 200...etc..it's not an actual frequency..the time in state for deep sleep is figured by calling os functions...you will have to talk to storm717 or shane87 about this... however deep sleep shows fine for some but not others ..but its not an actual state that the phone scales to like the others (100 ,200,400...etc)
[Captivate Android Development] geokhentix:
Having kind of a perplexing issue. And that issue is; this Kernel just plain despises my phone. xcal's works fine, this one doesn't. I've went back to stock, master cleared, tried multiple GB roms(GR-10 / Continuum5), but it loops @ the GT-I9000 screen. Wut?
[Captivate Android Development] pinoymutt:
I've heard of the multi touch fix, but not the one for the backlight. Mind sharing a link or is it in the i9000 forums?
[Captivate Android Development] existz:
UPDATE

TalonDEV-0.1.4

Add 341MB RAM (kodos96's config)

Revert back to stock refresh rate

NOTE

Reverting back to stock refresh rate

seems

to solve washed out colors at min brightness, where it causes blacks to turn brownish
[Captivate Android Development] harpo1:
Nice job. It's running great for me.
[Captivate Android Development] mkr14:
I got a new Captivate and I see now what you mean about the red tint bug with a raised FPS cap. I am using the Snail kernel with the cap raised to 65 and I get a redish tint in blacks with my new Captivate.

This can be fixed using Voodoo Control color settings however. I was able to fix this by lowering the screen v1 gamma hack settings and lowering the red. IMO, people should be using this anyway because the results are great. The colors almost pop out of the screen!

I still have hope that you raise the FPS cap at some point. It seems to me that there is no reason to leave it capped aside from catering to people that don't want to use Voodoo Control.
[Captivate Android Development] IDoMy0wnRacing:
Just checking... Did you wipe casche partation and Dalvik cache before flashing the kernel 0.4.4.22?
[Captivate Android Development] Reynaldinho111:
Installer script should wipe everything afaik. I honestly dont even remember my last manual cache/dalvik wipe.

sent from my beloved cappy!!
[Captivate Android Development] tmng95014:
Thanks. I am trying to set MemoryFreak but is is all blank. Any suggestion?
[Captivate Android Development] tmng95014:
Yes, I did wipe cache and clear dalvik cache just in case. Have to reflash Apex 9.2. Don't know what happened...
[Captivate Android Development] watsa:
Did u reboot into Apex after flash or flashed Talon from CWM right after apex?
[Captivate Android Development] tmng95014:
I reboot after flashing Apex 9.2 then installed talon kernel.
[Captivate Android Development] watsa:
Dont know what went wrong, but you can always replace ZImage in updates folder of a rom/update package so u need to flash only once.
[Captivate Android Development] ngochuy:
Me too, i still prefer talon.
[Captivate Android Development] existz:
Have you modified /etc/ram.conf any?
[Captivate Android Development] pikachu01:
Try to install the busybox installer from the market. Then install busybox to /xbin.
[Captivate Android Development] saobang3886:
I have freeze when batterry < 10%, more time, using 0.22 and older version ~~! But with <= ver 0.8 it run smooth !
[Captivate Android Development] pikachu01:
Never had that. Try reducing the UV that you applied. At low batteries, any UV you do are particularly more impacting (I think, as I saw someone who had the same thing and reducing UV solved the problem).
[Captivate Android Development] saobang3886:
Maybe, but I use same UV with 0.8 and 0.22, 100-100-150-150-150 ( from 1200 - 100 mhz) with 0.8 it run smooth, and have freeze with ver > 0.8 when batterry < 10% I will try reducing the UV :D
[Captivate Android Development] VFO:
I just went to try and flash Apex 9.2 and for some reason it got stuck on "extracting kernel/modem to tmp...." waiting for what seemed an eternity (almost an hour) and finally pulled the battery. Now when I try and reboot I get the AT&T screen then the loading Talon screen. The progress bar goeas all the way and then it just stays on that screen. I have tried the three button into recovery to load my backup but the phone does not go into recovery. I am able to get into download mode but would like to not have to go back to stock and have to re root and all that. Is there anyway I can get recovery back to load my backup? What would people suggest?
[Captivate Android Development] pikachu01:
Might be a bad CWM flash. You can try flashing an Odin kernel (like Semaphore) to see whether recovery works, or extracting the Talon zimage then tar-ring it, and flash using Odin.
[Captivate Android Development] VFO:
I have some older talon versions in .tar format. Would you think that would be worth a shot? if it was a bad ROM flash could I atleast get into CWM with a reflash of the kernel?

Edit: I just flashed an older Talon via Odin but I still cant get passed the Loading Talon screen and still no CWM. Any other ideas would be greatly appreciated.
[Captivate Android Development] topiratiko:
It sounds like its done dude. Flash back to stock. :/

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
It's not a kernel problem. Probably the modem corrupted. Try flashing a modem using Odin? I have not tried this before, but considering your circumstances you should give it a shot.
[Captivate Android Development] tmng95014:
I have done it but still blank.
[Captivate Android Development] VFO:
Will it matter if I am still on ext4 file system? I realize now that I never converted back to RFS. :(
[Captivate Android Development] pikachu01:
Try removing any other busybox other than the one at xbin. And you should install version 1.1.7.x only. 1.18.x seems to not work on some binaries like MemoryFreak.
[Captivate Android Development] tmng95014:
I installed busybox 1.1.7.4 and still blank. Where to look for other copy of busybox?
[Captivate Android Development] pikachu01:
At /system/sbin or /system/bin.
[Captivate Android Development] topiratiko:
No. Flashing stock puts u on rfs regardless im 95% sure

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Try mounting system and data then reflashing oram

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] tmng95014:
i did and still blank after reboot.
[Captivate Android Development] tmng95014:
I did and still blank.
[Captivate Android Development] pikachu01:
Try deleting ram.conf and rebooting, letting it recreate the file. You might have changed the file and MemoryFreak can't read it.
[Captivate Android Development] tmng95014:
I check an there is no ram.conf in /system/bin.
[Captivate Android Development] pikachu01:
ram.conf is at /system/etc. Please read at least 10 pages back to know more about Talon before trying to use it. :)
[Captivate Android Development] topiratiko:
Ram.conf is in etc folder...

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] tmng95014:
Sorry i mean /system/etc. i deleted it and still blank.
[Captivate Android Development] topiratiko:
Did u try mounting system and data then flash oram?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Just to be sure...9.2 switches u to darckcore....u DID reflash talon right?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] tmng95014:
I did and it got MF to work but then back to blank after reboot.
[Captivate Android Development] tmng95014:
Yes, i flashed Talon after reboot Apex 9.2 with Darkcore kernel.
[Captivate Android Development] topiratiko:
Chek pm's

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
This is weird. The kernel doesn't actively delete ram.conf. Try reflashing Talon or go back to stock and reflash. Might have a deeper underlying problem here.