yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] BaDaB!ng505:
i dont know if this will help much but been running 1.4 talon kernal on my rom for a few days and didnt have any F/C or soft reboot issues until i started testing a new launcher that supports landscape mode..been acting up and rebooting every so often when its switch back n forth between portrait and landscape mode..so i think who ever has dialer that is set up to auto rotate will have similar issues..

looking forward to your next release buddy
[Captivate Android Development] existz:
The problem is, when releases are put out, everyone wants to post issues in every thread except here. If bugs are not reported to me, either in this thread or my channel, I don't know about them, and if I don't know about them, they wont get fixed. Granted some have been posted here or directly to me and Im trying to get them fixed, but as for the "lag" issue, it seems its only being reported in the continuum thread. I've tested Perception and SubPression both today and there is no such issue in either of those, plus icezar said he found the issue and fixed it in his rom. People also need to remember that 90% of the time they are using apps that were made for froyo, and there's a chance it might not work 100% correctly on gingerbread...the same goes for those restoring backups/data with TiBu with stuff they made on froyo, which is generally not a good idea to begin with (mixing stuff from different android versions isn't recommended)... But personally, coming from a clean install, no backups or whatever, completley formatted internal/external sd's, I have yet been able to reproduce most of these issues..

But my biggest gripe is that post are being made in every other thread except here... This thread is the only one I regularly check, I usually skim through some of the others, but not on a daily basis or even an every other day basis...so unless they are posted where I will see them, they will probably be overlooked since I wont see them..Plus when they do post here, it's usually "This does not work" or "I can't do this now"...and that's all the information they want to give..You wouldnt take your car to a garage and just tell the mechanic "my car doesn't work"... the same thing applies here, i need a little bit more info than that...

Plus those that use my test versions, if theres any issues..they need to be reported back to me. The ones that do give feedback usually have no issues or if they do, they are fixed right away. If everyone keeps on just downloading test versions and not reporting back, ill have to keep them in a closed group to where i know who is using it and I can get feedback from them.. Versions labled TEST are not just builds put up for early release, they are ment to be tested and reported back on.. but no one wants to do this..and I know theres quite a few people in icezar and dagr8 channels that use these, but rarely get feedback from besides a handful of people.

/end of rant
[Captivate Android Development] ChikiBujia:
You are absolutely right Existz!

I'm one of those that haven't reported back to you, so here it is.

The kernel is excellent, and the ext4 just makes my phone fly!

My first flash was 0.1.5, and the only problem I had was that the phone would freeze during or after a call. I'd have to reboot :(

By freeze I mean I could not scroll through my screens, and when the phone started to react, it would take about 30 seconds for the commands to respond.

One time while on a call, I could still hear the other person, but she couldn't hear me at all.

Today, I was trying to open a messages from handcent right after a call, but handcent never opened.and then the phone froze :(

Some other people running Mosaic have had the same problems, but one of them adviced us to switch back to 0.1.4.

I switched back a little while ago, and will let you know if the issues continue :)

Thanks so much for your hard work and support!!!

P.S. I'm running Mosaic I :D
[Captivate Android Development] shane87:
So here is my report on talon 0.1.5:

Great kernel, super snappy, no major issues. Occasionally I have noticed lag and/or hesitation durring media play back through merridian. The audio plays fine, but the phone becomes laggy if I try to do anything else. However, I also noticed the same thing on froyo, so I would guess it is a merridian issue, not a kernel issue. Other than that, this has been the smoothest my phone has ever ran. Espescially after applying a –50 uv on 1200 and 1000, and -75 on the rest. All in all, an extremely good kernel to still be in the dev stage!!

Keep up the good work!!

ROM: Perception II beta 2

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

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] rlorange:
On the i9000 version running simply honey 3.0 rom. Rock solid exitz! Fantastic kernel. Has wifi AP tethering and speaker phone call running with voodoo sound activated AND web browsing for half and hour. Apart from evil battery drain as expected nothing fc'ed or lagged once.

**Simply Honey 3.1, Talon i9000 test kernel OC/1.2Ghz, JVK modem**
[Captivate Android Development] gsx-r:
I'm on Talon 0.1.5 with ROM Continuum 5.1. My Cappy often gets freeze about 30 seconds and then releases itself from freezing, especially when playing with GPS function (Google maps, GPS essentials...). Don't know the problem caused by ROM or Kernel.
[Captivate Android Development] Soccer_Dad:
I had the same issue with GR-12 and Talon. I don't think mine was related to the GPS - because my GPS has been crap with gingerbread - basically, it's not even worth turning it on. ...And it's why I'm back with a froyo rom (but waiting until GB moves out of the development stage).
[Captivate Android Development] gsx-r:
Have you tried Continuum 5.1? The GPS function on my Cappy with this rom is not bad, it locked in <15 seconds outdoor (with data connection turned on - but the "use wireless nteworks" was unchecked). In fact, that can not be compared to Froyo. The Froyo with PlumbBob GPS fix is the best ever. Hope that 2.3 will soon better.
[Captivate Android Development] GGXtreme:
Update to Continuum 5.2, it's a no-wipe flash (you should backup your texts first with Titanium Backup). If your issue still isn't resolved, flash a previous build of the Talon kernel.
[Captivate Android Development] breakthru_sep:
Hello existz,

I have used TalonDEV since 1.1.2 on several different ROMs. I had some issues with my phone since 1.1.4 that I have finally narrowed down to the OC/UV settings (which have nothing to do with either the kernel, or the ROMs I used).

It seems for 1.2 ghz, my phone definitely needs some UVing, I tried -50mV with grkmaster's suggestion and it solved my stability problems.

With ext4 and 1.2ghz cpu settings, my Captivate is really, really responsive most of the time. Other times when it's not as responsive, I'm beginning to think Voltage Control might be the one to blame. I'll take my chances with Pimp My CPU as suggested, and report back.

So in short, although it's still in its early stages, Talon is a very solid Kernel. Thanks for all the time you devoted in this!

B.
[Captivate Android Development] GGXtreme:
***For those who were having issues with DIVX3 and the latest Talon kernel***

Can you PM with a sample video? Only a few people reported issues like this, but I'd like to help narrow down if this is just a localized thing or a kernel/ROM issue with certain versions.
[Captivate Android Development] Tarima:
Is this really confirmed? I can't imagine that its happening to everyone and only a handful of people are noticing it (like I said in another thread a Nexus S with 2.3.3 is blazing quick in every way).
[Captivate Android Development] H3llstorm:
Unlike some people (in various threads), I posted what broke BT and how I got around it rather than blaming the ROM/Kernel. :cool:
[Captivate Android Development] DaUnderSheriff:
5.2 and lag

I agree that this is a solution. I flashed 5.2 over last night (I did the Titanium backup and also followed the factory reset recommendation) and nearly all of the lag and freeze is gone. +1
[Captivate Android Development] mrhaley30705:
I'm running Continuum 5.1, with Talon .1.5 and I have no issue with lag or performance. Phone is blazing fast. Only problem I have is that damn charging issue that no ones has found a cure for yet.
[Captivate Android Development] xThe Enforcer:
Not sure if it's kernel related or not but is it normal that it takes 1-1.5 seconds for the screen to come one after I press the power button from sleep? I could swear it wasn't this long on FireFly.

I'm running:

Mosaic + Talon 1.5 with EXT4

Stock everything.
[Captivate Android Development] pinoymutt:
Uh-oh, saw on another thread that a new GB ROM has dropped (JVH) -- so I wonder if we'll start seeing some updated ROMs and a new Talon branch to go along with it in the coming days? :D
[Captivate Android Development] Vivified:
Gingerbread is Gingerbread, Talon should work fine on a new gb ROM base
[Captivate Android Development] jde984:
Not according to the JVH thread... people are reporting jvb kernel is not working with it.
[Captivate Android Development] cnigro1279:
This is very interesting indeed!!! Maybe Samsung fixed the borked drivers they released??
[Captivate Android Development] cnigro1279:
Woot Woot...Senior Member Status with that last post!!!

But alas...I'm still a noob... :)
[Captivate Android Development] tmng95014:
@existz

I am running Talon 0.1.3 for a while now. I notice the phone would reboot regularly when the battery level is 30% or below. Since it is not random reboot, I am not bothered. Just want to report here in the kernel thread just in case you know of something.

This only happened recently when I moved from Paragon to Continuum.
[Captivate Android Development] existz:
Those on Continuum, don't use the latest hourlys, seems something in Continuum is conflicting with latest changes causing boot loop...but works fine on others ... will have to wait till icezar is around to figure out what's conflicting with new lmk settings and/or the way its set now..

As for JVH, seems JVB is the latest kernel sources.. if its anything like froyo/jpx, we will only have jvb kernel sources for awhile
[Captivate Android Development] pinoymutt:
Hi existz -- when running the test builds is there something specific you generally want people to test for (other than overall stability)? I wouldn't mind running specific tests if there are things specifically you are looking for.
[Captivate Android Development] krufttangoud:
Overclocking and you...

Is there a way to disable full processor speeds? superpower will not over rule the kernel settings.
[Captivate Android Development] existz:
?? not sure if I understand correctly, but you can use Voltage Control to limit max clock to 1ghz or whatever you want, then save as boot settings
[Captivate Android Development] krufttangoud:
CPU SPEED

[SOLVED]

Uhhhh. I dont know how to explain it. In Froyo I used SuperPower to lower the CPU when there was no demand and then it would jump to full speed once I opened something. Doesnt seem to work on this kernel.
[Captivate Android Development] surfed.tk:
It does this on any rom by itself..... its called freq scaling.
[Captivate Android Development] existz:
maybe the app is not supported for gingerbread yet...iono..but the interactive governor does just that, when theres no load it automatically jumps to 100, then when theres load it will jump to max clock, no in between ...basically the same as ondemand governor.. I dont use the conservative governor like in froyo, which scales through all the frequencies..with gingerbread the conservative governor doesnt play well, so i only use interactive governor, or besides that only recommend ondemand
[Captivate Android Development] krufttangoud:
Thanks for the reply, that has to be the reason. It would jump up, down, up down. Now with CPU Tuner I have achieved the desired effect with the ondemand feature. Sits like a good dog at 100 till I need it.
[Captivate Android Development] existz:
anyone here having issues with CIFS? ive got a test version so let me know, need someone to test it
[Captivate Android Development] XorZone:
JVH

existz,

Do you plan to make an update for the JVH initramfs?

There is the diff per supercurio:

@supercurio

François Simond

Still, fact that JVH and prior kernels are incompatible is a pain in the ass for developers. Differences in initramfs http://bit.ly/k9OAn2
[Captivate Android Development] krufttangoud:
Modems

Existz,

I am running JK4 it seems to be running very fast and no quality issues. Would there be a reason to replace it with KC1? If it ain't broke don't fix it?
[Captivate Android Development] Shammyh:
Yea, I'll give it a try. Shoot me a PM w/ a link?

Thanks!
[Captivate Android Development] GGXtreme:
I'd like to give it a try.

Also, after some testing I've determined:

-Flashing 0.1.5 DOES break DIVX3 playback (black frame, sound plays in backgroud)

-Flashing to a previous version from 0.1.5 does NOT fix the issue

-Only a clean flash with an older version of Talon (ie. a wipe flash of Continuum 5 RC3) brings back DIVX3 playback

I was going to take a look at github last night, but I fell asleep. I haven't tested any hourlies dated after 0.1.5, nor have I determined at what point does DIVX3 break, but I do know that 0.1.4 does not have the issue.
[Captivate Android Development] shane87:
Ok, so I just experienced an issue. I do believe that it is a rom issue, and I will be posting it in the perception thread as well. However, I want to post it here, incase it is a kernel issue. Basically, the problem is with my Phone app. When I launch my Phone, and hit the call log tab at the top, the app IMMEDIATELY exits. No fc, no hang, just closes. I did not experience this until I woke up today. I saw that I had three missed calls, so I clicked the link in the status bar, and it brought up the log, then immediately closed. I tried to launch it from my homescreen, my homescreen dockbar, and my app drawer all with the same result. I fixed it with a reboot, but I can not figure out why it happened in the first place. I have made no changes, except to download the ³ media player.

Also, on a side note, after I got it working right, I only had two missed calls, instead of the three that it had reported.

ROM: Perception II beta 2

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

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] H3llstorm:
Did you try editing system/build.prop? I edited mine the following way...

media.stagefright.enable-player: false

media.stagefright.enable-meta: false

media.stagefright.enable-scan: false

media.stagefright.enable-http: true

media.stagefright.enable-rtsp: true

... leaving stagefright on for added performance with streaming media, but turned off otherwise (for greater compatibility). This seems to help with multiple codec-related issues.
[Captivate Android Development] GGXtreme:
I'm already aware of stagefright breaking Samsung's format support, it's an unrelated issue. In this case, DIVX3 (and possibly other codecs) is completely dysfunctional whether or not stagefright is enabled once Talon 0.1.5 has been flashed and until a full wipe has been performed.
[Captivate Android Development] H3llstorm:
Good for you. I wasn't aware that people were still using outdated/antiquated codecs like DIVX3.
[Captivate Android Development] GGXtreme:
I personally don't :rolleyes: But DIVX3 is a special case, since it's not an MPEG4-compliant codec. I'm also a bit paranoid, because I always have issues with things like seeking in MKV's I encode, and I don't know if something like this could affect other codecs.
[Captivate Android Development] kodos96:
Does it happen with the non-bigmem version of the kernel?
[Captivate Android Development] H3llstorm:
I suppose I don't see the point in complaining about issues with codecs people don't use (like DIVX3) or issues that haven't come up yet.

But hey, whatever makes you happy. :D
[Captivate Android Development] GGXtreme:
Well, the way I see it, if something that should work isn't working, I can't consider my phone stable as long as I know there is an issue. Maybe it's OCD, but if something is broken, there is a cause, and that cause might affect more than outdated codecs.

Time for me to stop derailing the thread >_>;
[Captivate Android Development] ChikiBujia:
Hello Existz!

So, after switching from 0.1.5 to 0.1.4 my problem now is hot reboots.

I no longer have the freezing problem after a phone call, but my phone hot reboots after locking it :(

What happens is that a couple of minutes after I lock my phone, it hot reboots.

I don't see the SGS screen, or the android logo, the screen just turns on and I see the "media scanning" going on. I unlock it and my screens are loading as in after a reboot.

I also have the 50% without signal fix app, which is activated after every reboot, and that happens as well.

I didn't UV'ed either version of Talon, I kust kept it as is.

This might be a known issue for 0.1.4, so i'm sorry if i'm being repetitive.
[Captivate Android Development] existz:
I would try a fresh wipe install and see if it happens then, sounds like a rom/framework issue...this is the first time I've seen the issue.. I've personally been through every jvb rom in the last 2 days and have not had any issue
[Captivate Android Development] ChikiBujia:
Ok, I will do that! :D

Thanks so much!!!!
[Captivate Android Development] kodos96:
According to the testers on IRC, the commit I pushed about an hour or so ago seems to have fixed the bootloop problem.... so latest hourlys should be safe for continuum users now.
[Captivate Android Development] LNJ:
Any of the hourly builds bigmem builds?

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] existz:
Nope..but latest TEST version (TEST5) is bigmem + debug...Those on Continuum, the latest hourly does work, so its safe to use
[Captivate Android Development] tmng95014:
Hi existz,

I just updated the kernel from 1.3 to 1.4. Will observe to see if phone sleep when battery is below 30%. By the way, after reboot, phone is fine and drained down to less than 10% without reboot. Something happened around 30%...

Let me know if you have any idea. Thanks.
[Captivate Android Development] existz:
0.1.6 should eliminate any "lag" issues that people are seeing with Continuum...hopefully i should have it up tomorrow
[Captivate Android Development] pizz0wn3d:
Yes!

Herp derp Captivate XDA Premium.
[Captivate Android Development] surfed.tk:
Lag Issue

never mind
[Captivate Android Development] CuriousTech:
Well, I've got one for you if you have a desk or car dock. Find any video that plays, plug the phone into a dock and it won't play video or audio. It will if Dock Sound Redirector is disabled, but not if it is. All it does is reroute audio to the USB as far as I know, but for some reason it breaks all the hardware decoding.
[Captivate Android Development] shane87:
So, someone just messaged me with a question, and I am unsure of the answer.

The question is, can the build.prop file be edited to show that we are running a captivate, since all of the code is based on i9000, and build.prop shows we have an i9000?

I think the answer would be yes, and that is what I told the person, but I am unsure of whether or not that would work.

I know this is more of a rom issue than a kernel one, but everyone in this thread, in theory, is running a captivate with i9000 sources, so it does fit.

My concern is, while you could change the settings to show this as a captivate, how would the market react? I mean, the captivate has never officially had gb, so what would it even find for the cappy running gb?

Any thoughts or responses would be greatly appreciated, and if you decide this should be asked elsewhere, just let me know, and I will move it.

ROM: Perception II beta 2

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

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] Tankmetal:
Running 1.5. Having issues with imbedded in browser non YouTube flash video playback. Really choppy. Tried with continuum and mosaic don't think the Rom is the culprit. Also in mosaic, launcher pro freezes for 30 seconds after a boot but is fine after that. Launcher pro was far worse in continuum almost unusable.
[Captivate Android Development] GGXtreme:
You can make the 'About Phone' screen show a Captivate without touching the market fingerprint (which you probably shouldn't). But doing so will prevent ThinkFree from activating if it was bundled with ROM, and it will disable the Samsung Apps market.

Do you have Flash 10.2 installed from the market?
[Captivate Android Development] goob1284:
I love you.:')
[Captivate Android Development] topiratiko:
Yes! Cant wait for 1.6!!!
[Captivate Android Development] meadhros:
Ok. Not a bug but looking for guidance

On tweaking usable ram on this kernel. Too many widgets is my issue but I like them. Can't pollen app drawer after setting up. Looks like with spb. Running I mac out half way through opening and Then lags. Have about 60 ,free before open. On .1.1.5. Or is memory something the .6 will be freeing?

how bout them beastie boys!

Edit: not on continuum but was. Spb didnt run until after going to the 1.4 kernel.
[Captivate Android Development] xThe Enforcer:
No one?!
[Captivate Android Development] momulah:
Its instant on my phone. Gr-12 plus talons 1.5 1.2gh ext4.

XDA presents....Samsung Captivate $4G
[Captivate Android Development] shoman94:
Instant on mine.
[Captivate Android Development] CuriousTech:
Never mind. New stagefright settings in Perception II b3 fixed that.
[Captivate Android Development] Tarima:
I think its funny that you copy pasted my EXACT post from the Mosaic Q&A thread. :D

But to answer your question, only 5 or 6 of us have reported the problem from what I've seen. If it doesn't go away with Talon 1.6 I'm gonna try a complete reflash.
[Captivate Android Development] existz:
I'm not sure if its the lock screen, but I've noticed different ones react differently.. for example, android and glass take about a second, but miui and epic are instant...
[Captivate Android Development] goob1284:
The lock screen issue only happens to me if it falls into a deep sleep. Like if I don't use the phone for a half an hour or so

Actually no matter which I use they all do that. There is a delay in the screen appearing
[Captivate Android Development] stuff:
As said in here, I get the little lag when waking my phone from sleep. It's annoying to me cause sometimes I'll press the button twice and the screen will come on and right back off.
[Captivate Android Development] existz:
UPDATE

TalonDEV-0.1.6

-set initial max frequency to 1ghz

-enable asynchronous I/O support

-disable some kernel debug

-some ARM optimizations

-slight cosmetic change to CWM

-new lmk settings from kodos96

-reverted OOM rework/fixes

-attempt to fix CIFS issue
[Captivate Android Development] TRusselo:
ok i have a new odin.... ... umm.. quirk...

this isnt "talon" kernel but ... i didnt want to start a new thread...

and could use an oppinion of people that have been using odin alot lateley..

umm..

odin "sees" my phone connected, and turns yellow (good to flash) while my phone is ON, normally, not in download mode..

this is not normal... or have I been smokeing crack and it always acted like this without download mode? because it is happening... i can unplug and replug and odin will say added and removed... and the box goes yellow "com 5"

wtf? should i try to flash while booted? see if it works?

odin 1.82 continuum talon
[Captivate Android Development] existz:
Not sure why it's doing that, I'm on Linux and use heimdall, but only flash when its in download mode
[Captivate Android Development] trekie86:
Updated to 1.6, I'll post if any issues occur. Thanks for the update. Hope this will fix the battery issues I've been having.
[Captivate Android Development] TRusselo:
I KNOW>>>

thats why i had to say something....

its not supposed to do this...'

but it is.. i can take video...

others have trouble getting odin to do this WITH download mode..

is it a new bootloader thing or fix.?? anyone else experience this?