yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Need a little bit more info guys...more than just 'its choppy'...make sure theres no runaway processes, check if cpu is scaling correctly..etc..etc.., Theres really no changes in 0.5.1.3 that would cause any noticable differences, im using the exact same fixes on my Inspire, only difference is JVT modules (which are mainly RFS and FM modules)...check the kernel logs (kmsg/dmesg)..etc.. need more info or I cannot do anything about it, so it wont ever change..Also, if it was kernel alone, it would he happening to everyone, so there's something else going on, or some certain setting, script, tweak..etc, need some more info before i can find out the issue

And Talon only runs on i9000 based roms (for the question above)
[Captivate Android Development] topiratiko:
For what its worth its nuthin but smoothness on my end. Try reflashing and wiping cache partition?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Same for my testers, but yea def try reflashing, along with caches wiped as mentioned above .. sometimes **** can happen
[Captivate Android Development] Dungeon47:
Reflash seems to have helped. Cleared caches manually before flashing.

Sent from my Android using the power of Greyskull.
[Captivate Android Development] reinbeau:
I too an enjoying nothing but smoothness :)

Sent from a state of Serendipity
[Captivate Android Development] Seanbest:
Flash the 0.5.1.3 1200 kernel and flashed Obession JVT. Had constant reboots. Went to 0.5.1.3 1000 and still have a few reboots, but not as many. Any reason to think the 1200 version would reboot so badly? Stick undervolt at all. Possible my Captivate can't even OC to 1200?
[Captivate Android Development] Nash123:
Great work. My sgs was never smoother.

Edit: Oops wrong thread. Haha.
[Captivate Android Development] Spidious:
Cleared cache manually first.

Reflashed...

Works OK now !
[Captivate Android Development] pikachu01:
How did you flash Talon? You're not using UV you mean?
[Captivate Android Development] Dungeon47:
Which version are you using, Rein? (BIGMEM, 1.2ghz, etc)
[Captivate Android Development] TheGoD:
F-word, just killed my low memory killer settings by mistake. How do I configure via memory freak? What is the memory for apps slider actually doing? Had my phone configured so that it starts closing processes when free ram is below 35 MB.

If I configure via ram.conf, how many Kb is one page?
[Captivate Android Development] reinbeau:
The BIGMEM 1000 one. For some reason I've never used the 1200 one. I tend to go with the mantra "if it ain't broke, don't fix it".

Sent from a state of Serendipity
[Captivate Android Development] aalh:
Cant use 0.5.1.3

phone is so laggy I think it is locked up

I have tried reflashing and clearing caches first

no diff

as soon as I move back to 0.5.1.2 phone is ok

1200-bigmem

MosaicVII
[Captivate Android Development] existz:
Like i mentioned earlier about this, need a little bit more info than its just laggy... apparently its not the kernel alone, otherwise it would happen to everyone (especially with over 2000+ dloads for cappy version and only 2-3 ppl have issues), plus the 2 earlier that had the issue reflashed and issue is now gone, so there is something else...not saying the kernel doesnt play a part, but theres another factor in there somewhere causing it.. Check cpu usuage, make sure its scaling correctly, check app processes, make sure nothing is hogging cpu, check memory usage..etc..etc..
[Captivate Android Development] Dungeon47:
It may be coincidental, but it seems like, if I enter MF and re-save, re-apply my settings, it performs a little better after the reboot. Is there any reason MF saved settings would change when flashing?
[Captivate Android Development] irishvandal:
Running that exact set up and the only issue I have incurred that made me question the build of either Talon or Obssession was an email FC issue that is obviously ROM.

With that said, I was on APEX 10.1 and Talon 0.5.1.2 and cwm Obssession on top (not my usual style, I tend to stock flash). After a manual reboot, went into cwm, flashed Talon 0.5.1.3 reboot. Manual reboot. And I believe I had to do a bat pull on the last reboot. Allowed for full boot-scan and cwm recovery, clear cache and dalvik with two manual reboots. The first boot seems to not allow certain things to stock under some ROMs.

Note - lagfix must be disabled during this transition add mentioned in OP.

How this helps. Obssession-Talon are well suited for each other.

Sent from .....a state of delusion ....
[Captivate Android Development] irishvandal:
Any lag issues, keep tweaking at your MemoryFreak, under old MF settings I was lagging, tweaked and resolved my lag for over five hours so far. Just an observation.

Stock ondemand.

-50v the whole run on 0.5.1.3 1200 stock

Talon

Background memory 32mb

ZRam 192

Swappiness 90

It still needs tweaking but its not lagging

Sent from .....a state of delusion ....
[Captivate Android Development] aalh:
I apologize for the dearth of info in my post

I will gather info

I do actually have an app that refuses to ask for SU (tegrak)

I was told reflashing the rom was the only way to fix that, maybe it is also a symptom of whatever is causing the bad behavior

I just hate using a reflash as a fix
[Captivate Android Development] Kyuta Syuko:
Have you updated the superuser apk? If not you should and it'll update the binary too which will wipe the permissions, but Tegrak might start asking for su permission.
[Captivate Android Development] rlorange:
@ Existz I recently flashed friends phone from froyo 2.2 stock with voodoo lagfix to simply honey 5.1 2.3.4 jvr and speedmod kernel. Then talon latest.

Something happened as I was updating su binary I think it failed and the screen suddenly turned pale and washed out like the gamma was off.

Assuming this was just a bad flash and voodoo color was acting funny I flashed first talon then the rom and then...

Well a bit panicky I realised this washed out screen problem had stuck :( did a complete format in cwm. Then reflash to stock jvk via odin. Not a, single flash failed and apart from the screen the phone is perfect.

I'm well aware that root access allows the potential for hardware being damaged through a bad setting so is it safe to assume that I am very unlucky and somehow superuser voodoo color hack has killed the screen controller hardware? Any suggestions to try to fix this?

Via voodoo control I can get a semi-normal looking screen with gamma set as low as it can go but if I push this too far then suddenly the green turns a very scary looking lime green with weird pixels. Set a little higher this green screen change happens only at the lowest brightness setting and just before screen time out crt off animation... I have heard of this green flash happening with other users of voodoo color enabled talon.

A thorough search has revealed only one case the same, interestingly in my country too but in this case no custom kernel flashing was involved.

This is the first time anything major has gone wrong in my sgs flashing career that seems permanent, i'm currently thinking the screen hardware controller was always going to go at done point due to	fault or being on the fringe of the quality control spectrum and that voodoo color hack aggravated the failure.

So for anybody getting the green flash using talon perhaps voodoo color hack may trigger then same thing.

my friends phone is under warranty so if I can't fix this via software hack then it is not the end of the world... It has spooked me bad tho!

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Captivate Android Development] rlorange:
try clearing the data from control freak our what ever app you use to control voltage and scaling. In the past I have had CPU stuck at 400 our 800mhz. CPU spy will tell you if scaling is screwy.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Captivate Android Development] aalh:
I have updated, no difference with Tegrak

I even uninstalled, rebooted, reinstalled SU and Tegrak with no change
[Captivate Android Development] daveshih:
For people with latest su issue, try clearing su's data. It will clear all current su permissions, but will not unroot your phone. It fixed my cc issue.

Also, for people with booting issues, please check your init.d scripts and make sure your busybox version is 1.17.

Hope this helps,

David
[Captivate Android Development] existz:
0.5.1.4 Public Test

UPDATE

0.5.1.4

- updated scripts removed during install

- added newmail's deep sleep detection

- added smartass2 governor by Erasmux

NOTE

Added NewMail's Ondemand deep sleep detection patch, let me know how things

are performance/battery wise. Also added Smartassv2 governor, this is only for

you guys to play around with and test..

if you have any issues then switch back to

ondemand before posting any issues

..Ondemand is still default and recommended
[Captivate Android Development] Kyuta Syuko:
Once the I897 sources are available (if ever) will you make TalonDEV usable on I897 ROMs as well?
[Captivate Android Development] existz:
Honestly, probably not... chances are i9000 GB kernels will not work with i897 GB.. not sure if we just got lucky with them working on froyo, so that would mean I'd have to start from scratch, and i don't plan on making anymore SGS kernels besides TalonDEV (atleast at the moment, don't even have a SGS anymore).. but the sources should be similar so most of the features/fixes in Talon should work on them as well..so it would be easy for someone to just cherry-pick everything over once sources are out
[Captivate Android Development] Kyuta Syuko:
Well if it doesn't work out maybe I'll attempt to put it together.
[Captivate Android Development] geokilla:
Rogers Gingerbread is out. Are there Rogers sources available?
[Captivate Android Development] JKenvin:
I'm flash test TalonDEV-0.5.1.4-1200-BIGMEM-CWM3.zip, but when use Voltage Control shall be FC :(

problem?
[Captivate Android Development] Kyuta Syuko:
Not sure. Only place I know to look is opensource.samsung.com and they're not very good at keeping the code organized or up-to-date.
[Captivate Android Development] existz:
No, Voltage Control works fine...you got something else going on, try clearing app data, uninstalling it and reinstall the app
[Captivate Android Development] JKenvin:
I'm go to Recovery, wipe cache, wipe dalvik, and flash again! but not sure!

Now, Install Talon 0.5.1.4 1200MHz - Voltage Control work fỉne! :(

may problem with ver BIGMEM?
[Captivate Android Development] existz:
No, they are the exact same in regards to what Voltage Control checks, so if its a problem with one, then you will have the same issue with the other..something else besides the kernel is/was causing it
[Captivate Android Development] Thunder22:
Flashed the new .14 kernel and lost 100mhz frequency. Checked in CPU spy. Noticed change when I applied new smartass v2 governor. Flashing back to .13 solved problem as well as wiped voltage setting in cwm
[Captivate Android Development] irishvandal:
Is SetCPU still able to manage all of the adjustments in Talon 0.5.1.x 1200? I dont go above 1200MHz at all, fyi.

And it would seem that smartass2 would enable smoother performance between freq, am I understanding this right?
[Captivate Android Development] pikachu01:
A potential fix for memory leak:

LINK

Try it and see if it triggers the lagginess when memory is low.
[Captivate Android Development] topiratiko:
Issue with 514

After setting control freak, after lettin fone sleep then using it will not scale to 1200 using 1200 kernel. Uses 800 400 200...switched back to 513 was good..then BACK to 514 problem returned. Ondemandx gov.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
Might be related to the sleep code patch.
[Captivate Android Development] existz:
Ill look into it, as pikachu01 mentioned its probably something in the deep sleep detection patch... i might know what the problem is and will look into it, might need to tweak it some for Talon ...anyone else having same issue?
[Captivate Android Development] topiratiko:
That sounds VERY right

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
As always existz, your the FREAKING man.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Pikachu01 your also a beast. I see what your doing with that tweaks/scrpts forum. Good **** man.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
So it looks like with the patch that it sets so it doesnt go over 800mhz once the threshold is reached during suspend, then when screen comes on it allows it to go back up to 1ghz, which it seems i left out setting it for 1.2ghz version (since theres no 1ghz step in 1.2ghz version, its just setting the new max cpu policy to 800)..so ill make an attempt to fix this for 1.2ghz version (this issue should not happen with 1ghz version if i understand it correctly)
[Captivate Android Development] Sqb:
Thank you for the hard work

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] existz:
1200 version? As this should not happen with 1ghz...also you might notice once it comes back out of suspend it will only use 200mhz as lowest frequency (which doesnt really matter that much when screen is on), but will drop back down to 100mhz during suspend... Im not 100% sure if i like this yet or not, so theres a chance i might revert the whole patch.. The way that it works (atleast from what i gathered from the code), is that during suspend it will drop down to 100mhz as min freq and sets 800mhz as max freq, so during suspend it will never go over 800mhz (kind of doing away with screenstate scripts), then when it resumes it should jump back up to max clock (ie 1ghz), and sets 200mhz as lowest..then when it goes back into suspend it starts all over again at min=100, max=800...But as for the 1.2ghz version, as theres no 1ghz step, its not setting the correct max policy when coming out of suspend..which this is an easy fix (and a mistake on my part), but i cannot decide if i want to keep the patch or not...
[Captivate Android Development] mgfjd:
These settings are working great.. Thanks.. Keep us informed if any changes
[Captivate Android Development] Sqb:
It was the 1200 not going over 800. Then I saw your post about it and decided that it was stupid to say anything about something you already pointed out. Thanks for all this hard work. That's what makes talon the beast it is

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] amtrakcn:
As the frequency problem already addressed I don't have anything to report. Just so much thanks for existz, from SuckerPunch to Talon.
[Captivate Android Development] viny2cool:
Hey, I am using Apex 10.1 and decided to try Talon kernel. I am using 352mb-non-oc version and I am experiencing problem with my wifi. Its just not turning on...It waits for sometimes and than resets....I looked into known issues and couldnt find it..so just asking....I want to use talon kernel to switch to Obsession....
[Captivate Android Development] pikachu01:
Remove your IP reservation setting or make your lease time be something other than forever (24 hours or 48 hours). It's a JVR/JVS/JVT ROM issue, not a kernel issue.

Edit: I think I'm wrong here. Try turning on wifi on/off again. It'll resolve itself. It's the infamous wifi bug that happens randomly.
[Captivate Android Development] viny2cool:
Did what you said..no use. It is trying to scan the Wifi networks and than restarts itself..I even tried reflashing kernel again and did reboots of the phone too...no use.
[Captivate Android Development] irishvandal:
It is in the ROM. I had the same set up as you described and had the same issue. However, after turning wifi of and on several rings in a row allowed me to get it synced. This was a random issue and wouldn't have to be done each and every time. Also, allow your wifi to try even if it takes five minutes to not connect.

If you got Talon running and are wanting to jump to Obssession, flash away. Make sure you disable lagfix before you flash.

Sent from .....a state of delusion ....
[Captivate Android Development] reinbeau:
Are you turning it on and off from the notification toggle, or via settings? If you do it via settings, it should work. This is a known bug, it's in the ROM and there's a fix for it, I just don't know where (I am no developer!).
[Captivate Android Development] existz:
0.5.1.5 Public Test

UPDATE

0.5.1.5

- reverted deep sleep detection patch

NOTE

Reverted deep sleep detection patch due to issues coming out of suspend with oc

versions...things should scale properly like before, smartass2 should also scale a

little different than it did in 0.5.1.4, as the deep sleep patch effected it as well
[Captivate Android Development] baghera1979:
You're a freaking work horse Existz.
[Captivate Android Development] fuloplori:
Thx a bunch existz for the quick fix ;)
[Captivate Android Development] pikachu01:
Eagerly awaiting for a "Talon" implementation of the sleep code patch :)

Thanks existz :)
[Captivate Android Development] tazman171:
Did the same thing to me on the first use after flashing to TalonDEV 0.5.1.5 1200, and yes I had already upgraded SU to v. 3 and updated the binaries. I ran it again, applied and saved the settings and rebooted and have had no issues since. :cool:
[Captivate Android Development] fractaline:
+1 .... And even without a cappy to test!

That's dedication!

<«Swyped from phone»>
[Captivate Android Development] oriveradel:
would it work with miui or Cyanogenmod roms???
[Captivate Android Development] H3llstorm:
Have people experiencing "charging issues" tried powering off the phone, charging to 100%, booting into recovery and deleting battery stats?

Just sayin' :cool:
[Captivate Android Development] mrhaley30705:
Yes. Charge issue there, even with phone off.

I'm thinking the charge issue may have something to do with auto rotate. I disabled it and things got better.
[Captivate Android Development] nakedninja42:
Did that last night on GR on my new warranty replace phone and did it when C5 first released on my old phone (had a single bad pixel)... still an issue
[Captivate Android Development] H3llstorm:
Just a shot in the dark, but I wonder if it's build related. I don't seem to be having charging problems with my 1007 Captivate.
[Captivate Android Development] harpo1:
If you under volted you want to wipe voltage settings.
[Captivate Android Development] nakedninja42:
The phone I did the warranty with was 1007 and my new one is 1012.

The first time I did the charge with the phone off, it told me 100% on the phone and so I turned it on and went to recovery and deleted stats. Reboot the phone and it told me it was 92%.

Last night with the new phone, I used it till it died and charged all night. This morning I unplugged it and plugged it back in (powered off since the night before) and the battery showed me it was not fully charged. Half hour passes so I look again and it said it fully charged. Tried again... was not done. Frustrated at this point, I let it go until 100% (less than 5 minutes this time) and then booted and deleted battery stats.

Ill report back if anything changes... but I doubt it since devs chalked it up to JVB bug.
[Captivate Android Development] WickedNite:
Okay, I'll do that. Thanks!

Captivate, Continuum, XDA Premium
[Captivate Android Development] froli13:
Why? There's no changes to the oc/uv code.
[Captivate Android Development] alexige:
I have the same issue atleast with the downloads not sure about the full change log although im about 75% in thinking it shows. Didn't check before I typed this.
[Captivate Android Development] Lencias:
Can we get the option to OC to 1.4-1.6ghz? I could actually run stable on 1.4ghz. BLN support would be wonderful. Also, an option to do ext2 loops (as ULK allowed) would be great!

(and I'm not sure if init.d support is a kernel thing or a ROM thing, but if it's a kernel thing, please and thanks! Hate having to adjust my UV settings at reboot)
[Captivate Android Development] shane87:
Ok, it has been co ered numerous times before, but I will reiterate anyways. Existz has stated that he may add oc to 1.4/1.6, but first he needs to get everything else working. Bln is the same way, he wants to add it, but he needs to get the basic parts of the kernel fully implemented and stable first. And init.d support is built in already. I have a zipalign script that is in init.d, and it is getting called at each boot.

I'm not trying to be mean or demeaning, but the oc and bln requests have been posted many times in the past few days, and existz has stated numerous times that he is more concerned with getting the basics correct before he starts adding bells and whistles. Please search the thread before you post.

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] H3llstorm:
Existz has already answered this question.

With that...
[Captivate Android Development] squishy5:
do i have to change bACK FROM EXT4 TO RFS when updating the kernel
[Captivate Android Development] studacris:
No, only if you are going to change kernels completely.
[Captivate Android Development] H3llstorm:
After "fully charging" my phone last night, it dropped to 98% as soon as I unplugged it (Oh noes! LMAO!).

Seven and a half idle hours of later, it's at 91%.

I keep auto-rotation off when I'm not using it, Wi-fi on with policy set to "When screen turns off" and auto-brightness turned off (set a few notches above the lowest setting).
[Captivate Android Development] existz:
If your voltage settings are not sticking on reboot...

1) First make sure its getting saved to /etc/init.d/

2) Try reinstalling/updating busybox, its fixed it for others..plus it works fine for me.

BLN will be added once its working with i9k gingerbread, as of right now it does not work ...and they answered the rest for me above :P
[Captivate Android Development] FeO2:
Use the busybox installer from jrummy16. the other installer didn't work for myself and others to run scripts
[Captivate Android Development] rajendra82:
I discovered the CPU Tuner app today. It seems to be a good way to set up governers, create battery saving profiles,depending on the charge level, check time in states, and many such tweaks, and is free to boot. I love it so far. Add this to voltage control ex to enable and disable specific states, and you've got a very high degree of control on scaling of frequencies.
[Captivate Android Development] nakedninja42:
ON NOES THATS NORMAL! :eek:

It when it drops to 92% or 87% or heck... even 75% I've seen before on build 1007.... now that is an issue to say OH NOES too

This morning, I unplugged it and it was at 99% :D.
[Captivate Android Development] geokhentix:
Sorry to double post, but it's really bothering me because I'm not a noob and I feel crazy. This kernel just won't work. I've went back to stock, master cleared, cleared voltage settings, factory wipe etc etc, and it just loops on the I9000 screen. xCal's GB kernel works fine, it's making me go carazay! Anybody have any ideas? :confused:
[Captivate Android Development] pikachu01:
No. Only working for Samsung roms :)
[Captivate Android Development] mrhaley30705:
No. Not at all.
[Captivate Android Development] GoombaVinnie:
Did ya read the first page?
[Captivate Android Development] pikachu01:
Just released ThunderBolt! tweaks :)

http://xdaforums.com/showthread.php?t=1296927

Also I found that SIO will theoretically perform the fastest on Android devices.

Explanation here:

http://xdaforums.com/showpost.php?p=18291071&postcount=251
[Captivate Android Development] IDoMy0wnRacing:
pikachu01, Have you tried or compaired to Adrenaline Shot?
[Captivate Android Development] geokilla:
Since you posted here, I'm guessing it's one of the many tweaks that you created which works with Talon?