yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
We got a little project in the works, should help with making everyone happy in regards to LMK settings... everyone needs to support Shane87 for taking on the role of building us an app to where you guys will be able to select different lmk preset settings from right within the app.. hopefully this will make it where those that want aggressive settings can set it, then those that want multitasking type settings, can set it...etc..

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
This sounds awesome

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
Oh it will be :-) ..so everyone thank/support him for taking on this project for free

Sent from my SGH-I897
[Captivate Android Development] johan8:
In 4.2.0,

SIO scheduler seems stable.

VR scheduler has sleep death.

BFQ scheduler seems has better performance but has wifi reboot.
[Captivate Android Development] zerkai:
If we're on the same page.... then by any chance are you guys bringing along the oom settings as well? To make it less likely for our launchers to be killed, etc etc.
[Captivate Android Development] johan8:
Is it possible to Disable Voodoo log ?

It keep making logs in /sdcard/voodoo

Or use speedmod kind of lagfix.
[Captivate Android Development] Uncle Irish:
Since the 4.x reelases I have been getting freezes and increasing lag over time. I am on Apex 8.2, ext4, using the no oc version of 0.4.2 reg mem. Checked os monitor and no runaways it just started to lag after about 2 hrs and gets increasingle worse to the point of freezing. Launcher is go launcher. Let me know what other info I can provide and i will.
[Captivate Android Development] eep2378:
Have you tried any other launchers? Arc, Tw, etc? If so, same results?
[Captivate Android Development] TonyStark R.I.P.:
EDIT

Rookie mistake, I'll take an extra 5 mile jog for punishment. Up hill, in the snow, -40, naked!

zach will that suffice?
[Captivate Android Development] Uncle Irish:
Yes, tried all you mentioned actually. I honestly feel bad reporting issues because I have always been a fan of existz's kernels (Talon has been my fav).

It's strange that it starts off fast as lightning, then starts to degrade over time (normally within a few hours). I've tried ext4 and RFS (yuk) and it's the same. I know it isn't related to my particular phone because at one point I had 2 (stolen) and the new replacement does the same as well. I did also try the IR status on voltage control as someone mentioned in the Apex thread and that did not help eliminate the degradation.
[Captivate Android Development] zacharias.maladroit:
take a look at the i9000 thread ;)

double-cross-posting isn't such a good idea ^^
[Captivate Android Development] TonyStark R.I.P.:
See post 3309
[Captivate Android Development] ngochuy:
Maybe Samsung will release the official 2.3.4 for i9000 in Q3, we are very happy if u keep going on this project. Any plans to add HDMI output via USB like some kernel in i9000 thread in the future?

Have a nice day, Existz
[Captivate Android Development] eep2378:
Hmm, not sure what the issue is. This degredation only happens on latest talon release? You mentioned previous builds have been solid. Maybe run 0.4.1 until this issue gets ironed out for you, if you really wanna run talon.
[Captivate Android Development] Uncle Irish:
It started with the 0.4x releases. Previous have been good.

I'm going to wait and see how things go on the next release. Not giving up yet
[Captivate Android Development] mrhaley30705:
I've been using the 1200 bigmem version with very good success. Just putting it out there for you.
[Captivate Android Development] existz:
I will try and get a release up today, just with 2009q3 toolchains..., Ive got some family stuff to do today, so if im not able to, then def will tonight/tomorrow.

Sent from my SGH-I897
[Captivate Android Development] existz:
Scratch my last post :P

UPDATE

0.4.3

reverted back to 2009q3 toolchains
[Captivate Android Development] topiratiko:
Question as im confused and totally aroused at an unexpected flash. Whats 2009q3 toolchains?
[Captivate Android Development] airtower:
Can anyone offer a crash course in OC/UV with the tegrak modules? I have 0.4.1 dialed in great with specs in my sig, and I'd like to update to 0.4.3 but I tried out the kernel with tegraks app, but the way by which one goes about defining the max freq and scheduler I just can't seem to figure out.
[Captivate Android Development] existz:
Its whats used to compile the kernel
[Captivate Android Development] topiratiko:
One last question dont want to be annoying but was there something wrong with 4.2 that i should flash this?
[Captivate Android Development] existz:
It causes reboots during phones calls, mainly at lower battery life... My main suspect is the newer toolchains (2010.09 and 2011.03).. Zach put a build out with older toolchains, but still uses a precompiled modem driver, with this version the modem driver is fully compiled in the source (like it has been in all previous Talons)...with Zachs, the reboots still happened, but im suspecting its from still having a precompiled driver...so, basically all this release is, is to fully eliminate if the toolchains are causing it... If it still happens, then we will know its nothing to do with the TCs, and then can start looking at other previous commits to see whats causing it.
[Captivate Android Development] shane87:
Max freq, sceduler, and uv values are still set with CF, VC, SETCPU etc. All tegraks app does is load the overclock module into the kernel, making oc possible. You still have to use one of the above apps to tell the kernel to actualy scale to the higher freqs.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Sqb:
Like control freak! It's the effing best. Thanks for the hard work

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] dkucera:
Linux 3.0

Any thoughts or plans for Linux 3.0?
[Captivate Android Development] zacharias.maladroit:
it's going to be a hard and bumpy road to 3.0 :D

most accurate answer: not gonna happen ;)

the issue is that several parts art not opensourced (unlike with the Nexus S),

besides that all driver would be needed to be ported to kernel-changes (2.6.35 -> 2.6.36 -> 2.6.37 -> 2.6.38 -> 2.6.39 -> 3.0)

hell of a job ! :eek:

besides that the android 3.0 kernel isn't even ready yet

the kernel used on android devices is NOT the same like the linux-kernel used in Linus' tree
[Captivate Android Development] leoriver42:
was it expected to have a significant free memory gain using 0.4.3?

With 0.4.1 & 0.4.2 my free memory stayed at ~ 50 mb, now it's at ~ 130 mb!

Sent from my Samsung Captivate running Apex 8.2
[Captivate Android Development] airtower:
Settings aren't sticking through reboot, and I'm capped at 1.3 without buying the app. Hopefully by "temporary" this means we can do away with having to load these modules at all. Do not like..so back to 4.1 for me.
[Captivate Android Development] existz:
No, nothing memory related was changed in 0.4.3, just toolchains, which were same ones used in 0.4.1...

Sent from my SGH-I897
[Captivate Android Development] mrhaley30705:
Don't know aobut settings not sticking, but existz posted a few pages back he's working on modules to handle the OC instead of loading 12 different versions everytime there is an update.
[Captivate Android Development] airtower:
I totally understand his distaste of having to do that. I'm very happy with 0.4.1, but I have a nervous tick about running the absolute most current version of everything. I'll just take my meds and deal with it until a better method comes to fruition :D
[Captivate Android Development] leoriver42:
Weird...but yeah, just reporting the thing :P

Sent from my Samsung Captivate running Apex 8.2
[Captivate Android Development] H3llstorm:
I flashed 0.4.3 & went into a boot loop.

I pulled the battery, booted into recovery, flashed back to 0.4.1 & booted normally.

Android Market indicated that a new version of the Voltage Control app was available, so I updated it.

When I tried opening Voltage Control, I received an error message saying that my phone wasn't rooted.

Root Explorer & TiBu were working, so I knew this wasn't the case, but I had an idea...

I booted into recovery and selected Fix permissions (even though I don't know what - if anything - it does). Then I selected wipe cache partition, Wipe Voltage Settings & Wipe Dalvik Cache, even though I looks like this is covered in the install script for the kernel.

I then flashed 0.4.3 & booted up without any problems. Voltage Control works now too.

Can anyone make sense of this?
[Captivate Android Development] Vivified:
Sounds like a bad flash... followed by a good one
[Captivate Android Development] H3llstorm:
WTF does "bad flash" mean? Aside from the process being interrupted, how does digital data flash "well" sometimes and "poorly" other times?
[Captivate Android Development] mrhaley30705:
It "missed" a spot. You never had a song/movie etc have a glitch because it wasn't properly written? Never tried to write a cd and have errors because of something "missed:? It happens.
[Captivate Android Development] H3llstorm:
I've burned CDs & DVDs that had errors due to buffering issues, but I don't see how that applies to this situation.
[Captivate Android Development] Vivified:
I can say that when dealing with PC's and the like(smartphones), random **** happens and stuff just doesn't work right sometimes. It happens. Doing it again is the best course of action in this situation.
[Captivate Android Development] topiratiko:
I can say that i've had my fair share of the BIZZARE
[Captivate Android Development] existz:
It happens...mainly alot with CWM.. if **** gets funky, reflash... thats mainly why I use to always make release Odin/Heimdall flashable...Cezar pointed out, it seems CWM only flashes to bml6, where Odin/Heimdall flashes to both blocks, bml6/bml7., giving less chance of a bad flash ...but it does happen, and alot with CWM...so if you run into weird issues, always make first step to troubleshooting to reflash

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
MrHaley30705....shot you a pm boss
[Captivate Android Development] edtonn:
Good to know
[Captivate Android Development] mrhaley30705:
After becoming accustomed to flashing with Odin, I would prefer to flash kernels with it. I know the rom dev's are going to cringe with this comment, but I wish we could flash roms that way too. It would eliminate a lot of bad flashes from cwm, plus force people to be aware of whether or not Odin will recognize their phone, instead of waiting for the " oh **** I bricked my phone" moment to realize it doesn't (which prompts a million "oh **** I bricked my phone" threads in the q&a forum).
[Captivate Android Development] Rhiannon224:
+1 10 char

ROFLMAO
[Captivate Android Development] shoman94:
+2 I agree
[Captivate Android Development] eliminat:
I don't have a problem with this at home, but this would really hurt my kernel updating while at work or traveling.
[Captivate Android Development] H3llstorm:
Is this a limitation of CWM? Can CWM or install scripts be modified to flash to both blocks?
[Captivate Android Development] mrhaley30705:
I understand completely. I try not to do that though, just in case something goes wrong, but sometimes it's just too hard to resist the urge.
[Captivate Android Development] shoman94:
I asked before and was told no. Odin is a low level flasher..... Kinda like flashing a bios on a PC.
[Captivate Android Development] geokilla:
Getting reboots when talking on the phone. Might be a bad flash. I doubt it's due to OC/UV since I'm using the same OC/UV settings as Talon 0.4.2 and 0.4.1.
[Captivate Android Development] existz:
Do me a favor and try the non-oc version with no UV, use the non-oc instead of just disabling 1.2ghz, and see if it still happens. Also what battery percentage is this happening at?

Also, anyone else still experiencing this? (Only reboots either during calls or as soon as you hang up)

Sent from my SGH-I897
[Captivate Android Development] Rhiannon224:
Cezar reported it on his forum earlier today when battery drops below 20% it happenned to him. I've had none on the non oc'd 4.3 kernel, the memory problems that I experienced on 4.1 and 4.2 I am not seeing with 4.3 on the latest Continuum 6.2 beta. I am on rfs and it is snappy and smooth.
[Captivate Android Development] geokilla:
As Cezar reported, my battery is below 20% when it happens. The phone was fine when I had over 20% of battery life remaining.

It happened to me when I hung up as well, so I think it's both. That or I accidentally hit the end call button with my face somehow, but that seems impossible as I've never hit the end call button with my face before.

I think I'll revert back to 0.4.2.
[Captivate Android Development] Nerz:
I'm on 4.2 :-/ I was looking to upgrade to he latest to see if it was a problem with this version.
[Captivate Android Development] Nerz:
Blah. Double post. Sorry.
[Captivate Android Development] topiratiko:
Woah woah woah. Does 4.3 support gpu oc???

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] Sqb:
Not right now. They said it isn't working right anyway yet

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] Oxicottin:
Is there a .tar file so I can use odin to flash or is there one for DL I didnt see?

Thanks!
[Captivate Android Development] oblivianz:
I also suffer from the same problem.
[Captivate Android Development] RonH54:
I am using the 0.4.3 1200 version of this Great Kernel. I know each phone is different but what are some UV settings you guys using that been fairly Stable for you?

Thanks
[Captivate Android Development] nyydynasty:
i'm still testing but I'm using -75 all the way down and its been stable so far.
[Captivate Android Development] Vivified:
1200 || -100

1000 || -100

800 || -125

400 || -125

200 || -150

100 || -150
[Captivate Android Development] Aus_Azn:
I'm on the 1000 version.

1000/-140

800/-140

400/-140

200/-140

100/-140

I use SetCPU to UV, hence the custom UV values.
[Captivate Android Development] geokilla:
Saw this on XDA Portal. Looks interesting. It's supposed to speed up your phone and save battery life.

http://xdaforums.com/showthread.php?t=991276
[Captivate Android Development] onetruejp:
Been having this same issue. The last Talon kernel that doesn't do this seems to be 3.3 R2 that comes with Continuum 6.1. Using ADW Launcher.
[Captivate Android Development] grasshands:
Cisco anyconnect for rooted devices fails missing tun/tap on TD0.4.3

Hi

I've been running Apex and TalonDev for a few months and gotta say this is the best combo for battery life/performance and bln on my sgs phone. Recently cisco released the anyconnect vpn client for Android devices (two versions for Samsung devices and for rooted devices). I installed and tried both versions and both fail to connect saying there is no tun/tap driver loaded, yet I'm running TD0.4.3 which says it has TUN support...is the problem missing TAP?

Thanks

J
[Captivate Android Development] existz:
You have to load the module for it to work...type this in a terminal emulator/adb shell

su

insmod /lib/modules/tun.ko
[Captivate Android Development] harpo1:
How are you UVing with setcpu? Making a custom profile?
[Captivate Android Development] sremick:
Wow, intriguing... but a lot of lofty claims and way too many exclamation points. I think I'll wait to hear feedback here before I do anything.
[Captivate Android Development] grasshands:
Awesome! Worked perfectly...didn't have to reboot or anything. Is this change sticky or will it be lost upon rebooting?

Thanks

J
[Captivate Android Development] existz:
Yea there were some talk about it earlier and on i9000 talon thread... it seems to actually set lmk values correctly, unlike ramhack scripts... setting it in both places...I messed with it some but went back to talons settings, works best for me. Hopefully before to long we will have our app done, which will allow you to select different lmk settings based on stock, aggressive, multitasking..etc.. should make everyone happy. But as far as V6 Supercharger, it does work ..but recommend using talons if you don't have problems

Sent from my SGH-I897
[Captivate Android Development] existz:
It will reset on every boot, but you can take the script I have in the OP for loading conservative governor, edit it for the tun.ko module, its only a one line script, just replace it for tun.ko instead of cpufreq_conservative.ko ....then remove the .sh for end of file name and place in /etc/init.d/

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
I know this is the wrong forum...but its reported that att gs2 will have a slide out qwerty. YUCK

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] timn2bama:
Have you tried this script?
[Captivate Android Development] Rhiannon224:
This is some strange behavior I experienced this am.
[Captivate Android Development] Rhiannon224:
Just a few minutes later look at that battery drain.
[Captivate Android Development] existz:
Try restarting with a cache/dalvik cache wipe....something is pegged out it looks like

Sent from my SGH-I897
[Captivate Android Development] slayp00n:
why no more 1.6ghz OC? :(
[Captivate Android Development] Rhiannon224:
Yeah that's what I thought. I swapped battery and rebooted and it's stable now.
[Captivate Android Development] sjavvaji:
busybox thing worked...thanks
[Captivate Android Development] Doug8796:
any news on 1.3-1.5ghz?
[Captivate Android Development] thumper_1151:
I know scores are not a true indicator but I just had to post this.

Juwe 4.1 with talon 1.2 @1.2 most tweeks enabled.
[Captivate Android Development] rlorange:
Hey exits! Please check your pm :)

**Simply Honey 3.0, UltimateGB beta7 kernel, JQ1 modem**
[Captivate Android Development] CuriousTech:
I just flashed 0.1.3 from 0.1.2 using SGS kernel flasher since Odin3 was giving me errors. It usually doesn't but whatever.

In 0.1.2 the dock audio was left channel only no bass, now it's full stereo. BT stereo is full range too now.

All versions have been very stable. Quadrant/Linpack scores are really high. Quadrant Advanced is a little strange. The 3D tests don't have any textures, but Standard does but that could just be a Quadrant bug.

Great work!

I'm running Perception II btw
[Captivate Android Development] cumanzor:
So if for any reason I wanted to flash xcali's kernel, I guess I have to covert everything back to rfs right?

Sent from my GT-I9000
[Captivate Android Development] existz:
Yep
[Captivate Android Development] H3llstorm:
Can anyone tell me which ROM I should flash with this kernel? :D
[Captivate Android Development] existz:
Perception or Continuum, both are vary good
[Captivate Android Development] existz:
Glad to hear it's working...seems compiling sound/soc/codecs/ as O2 really cleared up some bugs..awesome
[Captivate Android Development] keitht:
Is this the same 0.1.3 included in the latest Continuum 5 RC3?
[Captivate Android Development] existz:
No, the one in this thread is more up to date...you can tell by the one in the rom, look in about phone..I forgot to change the version number so it will say 0.1.2 still...the one in this thread will actually say 0.1.3.... there is a few fixes for sound bugs in this one ...(unless icezar updated it) but I don't think he has yet
[Captivate Android Development] CuriousTech:
The button backlight always being on with the screen is kinda weird but might be a good idea. I could get used to this. :)
[Captivate Android Development] keitht:
Thanks and I am showing 0.1.2 in About Phone. I haven't experienced any sound issues so I will stay put for now. Everything is working great so far for me except Launcher Pro likes to hang sometimes but that may be compatibility issues with GB. Otherwise, everything else is crazy fast. I am scared my phone may fly out of my hands sometimes :)
[Captivate Android Development] H3llstorm:
Is it possible to use a Galaxy S I9000 ROM with this kernel on an i897, or is that asking for trouble? :cool:

BTW: It looks like MikeyMike01 has released a 2.3.3 ROM too - http://xdaforums.com/showthread.php?t=1055622
[Captivate Android Development] kodos96:
So I'm trying to build talon from git, but the kernel I get comes out severely unstable... it boots successfully, but then reboots within a few seconds of using it. I also noticed that its configured to use the ondemand governor, which is not what 0.1.3 is using, and I don't see anything in the commit logs about changing governors.... so I'm wondering, is this the same branch that you're building the release kernels from, or is there another branch somewhere (or a local working copy with uncommitted changes) that you've been building the releases from? Because comparing the changelogs in OP to the git commit logs, they don't seem to line up with each other....
[Captivate Android Development] roomtek*8525:
Logcat

hi there, Just flashed latest Kernel using ODIN, only to figure out Logcat was gone. Sad for me, cause i develop and need to see my logs. I noticed that many custom roms have removed logcat. Was there any benefits to remove Logcat from this Kernel, or does it matter??
[Captivate Android Development] wonner:
Logcat is disabled for improved battery life. There is a logcat enabled version...TalonDEV-0.1.3-DEBUG.tar
[Captivate Android Development] roomtek*8525:
Oh ok, thanks.
[Captivate Android Development] froli13:
ApeX 6.0 :D
[Captivate Android Development] tege989:
So, is there??
[Captivate Android Development] slayp00n:
just use the sgs kernal flasher
[Captivate Android Development] dkucera:
Thanks for the response did not know that they were that different. Will just have wait and do it on my desktop/laptop.

Thanks again

Don
[Captivate Android Development] mrhaley30705:
No. but its easy enough to use one of the old tar files and swap out the zImage. BUT, if you do that you must manually clear cache, wipe Dalvik, and clear voltage settings before flashing, otherwise VERY bad things will happen.
[Captivate Android Development] killer23d:
Still getting reboot during phone calls in low-bat situation about 17% left. UV -50 on all steppings.

I don't think the TC has anything to do with this.
[Captivate Android Development] oblivianz:
For some reason every time I'm about 20 mins into a phone call, the other side can't hear me but I can still hear them. This has never happened to me in the past and even when I change modems the problem still persists. Any ideas?
[Captivate Android Development] tege989:
When you say swap out the zImage do you mean just flash it in Odin in the PDA slot over one of the old kernel files that's already installed on the phone?
[Captivate Android Development] tege989:
I tried that and it said "Kernel flash failed"

I'm using the Talon kernel version 0.3.2 Continuum v6.1.
[Captivate Android Development] existz:
Just download the cwm zip in the OP and flash it via CWM...simple as that
[Captivate Android Development] Alexstarfire:
I know this ROM supports BLN, but when I try using with Darky's ROM it doesn't work. Does it just have to do with the combination? After using BLN for so long not having it is painful.
[Captivate Android Development] mrhaley30705:
Bln support isn't just the kernel. The rom has to have support (service.jar I think) in it. If Darky's didn't have it in it, no bln.
[Captivate Android Development] tkjeeper:
Well existz, you want it on your thread so here you go.

I realize you put a lot of work into these kernels and I appreciate that.

I'm not falling for it anymore.

Either it's my phone, whatever but EVERY kernel of yours works great for a day, or less, then things go to ****, sorry. Huge lag, I've tried everything, I give up. I have no issues with dark core, I'll stick with it. Thanks.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] Nerz:
Or you xould just build ur own before bashing someone elsea work eh?
[Captivate Android Development] Sqb:
Peace out rabbit!

Sent from a rock on fire in the middle of the sea