yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Yea, Linaro is smooth, but good ole 2009q3 is fully stable and is IMO the best toolchain for this source.. Which if the issues in .13 are still in .14, then ill go back to Linaro since switching made no difference..but the bt issue some reported were turning on wifi, then turn on BT, and it introduces tons of lag .. Which it can very well be caused by the toolchains used, there were alot of changes in .13, but most of them were already in previous test (such as update to 2.6.35.13), it was in an older test and no one had issues, so i highly doubt thats whats causing it..toolchains is the other big change..but like i said, if it doesnt seem to fix some of the issues a few were having, then ill switch back
[Captivate Android Development] existz:
Ok,.so some i9000 users are reporting tthe wifi/bt issue is still present..so I will probably stick with Linaro toolchains since it made no difference..plus IMO linaro is smoother .. but ill try and get some testers to go through and see exactly what test build it started with, and hopefully eliminate this bug soon
[Captivate Android Development] rajendra82:
Installed 0.4.4.14, and a couple of weird issues noticed. In CPU Spy, the percent of time in each state is being shown as negative, and in Voltage Control, the I/O scheduler and CPU Governor lists are six times as long with each option being repeated. Never seen that before with any previous releases.
[Captivate Android Development] nyydynasty:
just to confirm - 0.4.4.14 and my wifi will not turn on via the notification drop down. But it turns on when I go to the settings and enable it there....wierd.
[Captivate Android Development] kodos96:
I don't know about the HTC status, but I also have a Nook Color, and the reason it has so much more memory free, despite the fact that it has the same 512mb physical memory, is because it doesn't have a camera (or a phone baseband) eating up memory.

The reason that the bigmem kernel breaks 720p video recording is because the way the camera controller/codec chip work is they need a block of CONTIGUOUS memory to write to, and the only way for the linux kernel to guarantee them that they'll have a contiguous memory region available when they need it is to set aside a chunk of it at boot time, and let it sit there, completely unused, except when you're using the camera. That's a massive waste of ram, but it's what the hardware requires.
[Captivate Android Development] existz:
I dont think its the kernel causing it, ive seen this happen on other kernels..as for cpuspy i had to uninstall it and reinstall it and all was good...with VC and io scheduler, ive seen that happen from time to time, when opening it it would show double, then exit and it show normal..but do the same, just uninstall and reinstall and all will be good..not sure what the problem is
[Captivate Android Development] existz:
Yea that happens every now and again, like ive said before..it fixes the wifi reboot issue, but sometimes it does that...either from notification dropdown or power widget, but you can enable it via settings menu..sometimes its different after a reboot, it will then allow you to do it from dropdown...but again, this is better than it rebooting..
[Captivate Android Development] rajendra82:
But then Samsung should have factored that in, and given us 1GB RAM like the Galaxys S II to begin with, not 512 MB.
[Captivate Android Development] manny05:
I use it very often. Matter of fact I used it to record a concert and it looks great. Camera on the Cappy is pretty solid. Probably had the best Camera that night

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] F1reEng1neRed:
I don't see why they would have done that. You seem to forget that when the Cappy was first released, it had some of the best specs on the market. The sgs 2 is the next generation of the sgs i9000, so I don't know how anyone can expect them to put more memory in a phone that's is based off the prior generation.
[Captivate Android Development] existz:
Ok, so i believe i figured out what was causing the wifi/bt issue.. give me a little bit and ill put another test up, also reverted back to Linaro toolchains..they seem to be alot smoother than CS2009q3
[Captivate Android Development] zacharias.maladroit:
nice ! :)

[meh - 10 chars]
[Captivate Android Development] lowlymarine:
The biggest consumer of RAM is the 128MB dedicated to the GPU (and possibly other components like the baseband). According to the Samsung block diagram for the S5PC110 (Hummingbird), only 384MB of our RAM is LPDDR1 allocated for system use, and the rest is oneDRAM for the various co-processors.

While not inherently a bad decision, perhaps something more modest would have improved system responsiveness. I believe the first-generation Qualcomm QSD/MSM8xxx (Snapdragon) chips use 64MB for this purpose.
[Captivate Android Development] topiratiko:
LMAO nice sig
[Captivate Android Development] existz:
0.4.4.15 Public Test

0.4.4.15

Changelog from 0.4.4.14

- revert back to Linaro Android 4.6 (GCC 4.6.2) toolchains

- reverted "rfkill updates from Infuse source" (fixes wifi/bt issue)
[Captivate Android Development] topiratiko:
FIRST +10char
[Captivate Android Development] DaUnderSheriff:
Very smooth since the .13 update. Battery is much improved and much smoother performance. Just switched to .15 test, so will provide feedback later on that.

Sent from my Apex 9.x & Talon powered Captivate.
[Captivate Android Development] daverup:
4.4.15 is much smoother for me than 4.4.14, ran the 1200 version of both.

Also, wifi toggle seems to be working on .15 so far.

Nice work guys!
[Captivate Android Development] kodos96:
Well I'm certainly not going to argue with the idea that the phone would be better off with more ram, but keep in mind that a) back when it first came out, 512 was the most memory any android phone had, and b) what I'm describing is not unique to samsung or the captivate - its very common for phones and other embedded devices to have significant portions of their main ram set aside for various onboard hardware that requires contiguous regions.

It makes me feel kinda dirty having to defend Samsung, especially when it comes to the phone not having enough free ram, which bugs me more than anyone... I'm just sayin, it's not just samsung.
[Captivate Android Development] kodos96:
Yeah, but if you compare a recording in 720p to one in the next resolution step down from 720p, there's really not that much difference in visible quality... the phone's optics just aren't good enough to really do justice to 720p. There's nothing particularly wrong with the cappy's optics, is just that, like all phone cameras, its lens is really small... and there are limitations imposed by the laws of physics on how much meaningful optical data you can get through a small lens.
[Captivate Android Development] astrocrep:
I hear what your saying but on the x86 platform in 32bit there is 4gb of addressable space... So if you had 2 gb ram and a video card with 512mb, that 512mb doesn't overlap some of main memory... So the arm hardware address space should be mapping rom and other hardware past the system memory.

-rich
[Captivate Android Development] kodos96:
Thanks for the link to that block diagram - I hadn't seen that before, and it's very interesting.

I'm not really clear on the LPDDR1/oneDRAM distinction, but I know that there's not 128mb reserved for the GPU - by disabling just the MFC codec chip I'm able to get up to 420mb ram available to the kernel. I suspect that the "20M 3D / 2D VG" block in the diagram means that there's 20mb reserved for the GPU.
[Captivate Android Development] kodos96:
But if they did it that way, then it wouldn't be possible for us to steal any of the ram back with kernel configs like bigmem ;)

But seriously though, I think it actually makes more sense for all of your system's ram to be in a unified address space, and let the kernel allocate it as it sees fit... I mean if you have a 512mb GPU in your PC, that ram is just getting wasted whenever you're not playing 3d games. Wouldn't it be nice to be able to repurpose that ram for main memory when its not in use for graphics?

In fact, there are actually some upstream patches (written by a samsung engineer incidentally) that try to solve the problem of hardware needing a contiguous memory region, without needing to permanently reserve (i.e. waste) a big block of ram for it. The way it works is that you can specify a reserved segment of ram for the hardware, but then when that hardware is not in use, the kernel can use the "reserved" space for migration of data in zone_moveable allocations... so in other words the kernel could steal the ram back from the camera/gpu/codec and use it for pagecache whenever the hardware in question is not in use. Since pagecache is just a cache of what's on disk, its safe to just throw it out if you have to... so when the hardware needs its ram back, the kernel just frees the memory and hands it over. It's actually a really nice solution to the problem, and I have to give credit where credit is due to samsung for one of their guys working on it.

I tried merging the code at one point a while back, but there was a TON of stuff I was going to have to merge manually to get it working, and I gave up on it. I may try to revisit it if I get the time.
[Captivate Android Development] pikachu01:
Wow kodos96, if this was implemented in Talon, I would think that it would be THE most useful feature yet on the SGS.
[Captivate Android Development] timn2bama:
. 15 running good so far seems smooth! No uving for right now still have long ways to go until 24 or 48 hrs!
[Captivate Android Development] motive:
Yea .15 does seem alot better but i am still skipping from 800mhz to1200mhz in voltage control no matter what?!?
[Captivate Android Development] markmunsch:
Gotta be kidding me, apparently it's my wireless, I tried it on my phone just off the data network, and it's downloading now. Sorry for the trouble existz
[Captivate Android Development] existz:
I also want to point out that, with 2.6.35 kernel, the oc/uv seems to be WAY more stable than it was on froyo....again, take everything you know/learned about froyo and FORGET ABOUT IT!... so much has changed in 2.6.35/gingerbread... I can honestly say that with oc/uv , that it is just as stable as without it., unlike how froyo was..so if you dont want to oc/uv, just use Voltage Control to set max clock to 1ghz and save as boot settings..ive yet to find any issues with it...
[Captivate Android Development] harpo1:
Same here.
[Captivate Android Development] existz:
Its still working fine for me, just tried it on a different computer and dloaded every version fine...
[Captivate Android Development] markmunsch:
Hey yeah I finally figured it out, apparently it was my wireless router, on cell data network it downloaded just fine, flashed it already.

I also have noticed the OC/UV is much more stable, I've been able to push my UV farther than I ever thought with Froyo and no SD/CDs yet. Will continue to play til I find the limit.

Thanks existz and YTT3R for the hard work you're putting into this.
[Captivate Android Development] astrocrep:
Hey existz, any ideas on the home button not working? (Tried xcal's fix... worked in 0.1.2 now not in 0.1.3, nothing else changed)

Thanks,

Rich
[Captivate Android Development] existz:
The actual home button not working or haptic feedback? cause actual home button works fine here...
[Captivate Android Development] kodos96:
Ahhh... ok, I was using the latest codesourcery, that's probably the problem.... I know the readme said use 2009q3, but on onix you told me to disregard that and upgrade to latest codesourcery, so I figured it'd be the same thing here. Ok, I'll give that a try, and hopefully have bigmem kernels for people to try out soon.
[Captivate Android Development] astrocrep:
When I touch the home button, the back-light reacts, but nothing happens. I don't care about haptic, but the press doesn't register any actions on the UI, ie: doesn't go to the home screen.

I guess, I can try to flash back to 0.1.2 and see if it works again...
[Captivate Android Development] existz:
Yea i went through hell at first with 2010.09, it was a *****...kept causing all kinds of boot loops then when it would boot it would reboot when plugging in charger...but 2009q3 seems to work good, also make sure to set the localversion as it says in supercurios notes in the readme...also seems if you change config_hz to anything above 300 or so it causes instability...reboots..etc..
[Captivate Android Development] kodos96:
I actually never had any stability problems with froyo at 1.3ghz, UV, but on talon 0.1.3 @ 1.2, no UV, I've gotten a couple of lockups/spontaneous reboots. Not sure yet whether it has anything to do with the OC, I'm gonna cap at 1ghz and see if that changes anything...
[Captivate Android Development] TRusselo:
hey X i see that SnL rom has a version with a 2.3 kernel that runs 2.5 CWM allowing easy flashing back and fourth... between 2.2.1 and 2.3 roms. but his write up wasnt the best... hard to understand somethings

any chance of getting that for talon? CWM 2.5 or is there advantages to 3.0.. or am i missing something..?
[Captivate Android Development] johan8:
I rewrite the script, here is CWM2.5 flashable for whom want to upgrade from old CWM.
[Captivate Android Development] H3llstorm:
Can this be flashed over the CWM3 version of Talon?
[Captivate Android Development] TRusselo:
more information for the ones still learning helps....

so this is still CWM3 talon, but can be flashed from CWM2.5 other kernels/cwms........ but on 2.3roms only?
[Captivate Android Development] pizz0wn3d:
Is anyone else experiencing massive battery drain on 0.1.3? I'm pretty sure it's because my phone isn't going into deep sleep, or at least that's what cpu spy is telling me. Is this a known issue? I read a few pages back but didn't see anything on it.

Edit: I'm on C5RC3 if it means anything.

Edit 2: about phone battery usage is showing android OS as using 45% of my battery.

Herp derp Captivate XDA app.
[Captivate Android Development] rmntruexjr:
+1.....I also noticed that all of a suddon my cpu temp climbs and the cpu wont use any state lower than 400. Clearing memory in task manager doesn't fix it. Just like you during these times android os is using alot of batt. A reboot will sometimes fix it and then the cpu temp drops to normal. Tw4 was way too laggy for me to use so Im using arc and that is a little better. No reboots though, and my signal seems normal. I do think I had better wifi reception on 2.2 based roms & kernels like C4 though.
[Captivate Android Development] rajendra82:
I developed reorientation issues when I went to display -> horizontal calibration in Continuum V5, and did a horizonal calibration. Once I did it, the phone seemed to be out of orientation by 90 degrees. Luckily a reboot fixed it. This was never an issue with any of the Froyo reorient kernels.
[Captivate Android Development] Shammyh:
Couple of bugs to report:

1) CIFS support isn't working. It would appear that although the kernel supports it, the required cifs.ko module is not there, or not working. Maybe because we're flashing kernels with ODIN and not via CWM?

2) CPU scaling seems to have some problems. I was benchmarking/testing a few things the other day, and noticed that even when the governor was set to "performance" the CPU would not scale above 800 MHz. Only when I used SetCPU and forced it up to 1200 MHz would it stay there, and even then, it appears to kick back down to 800 MHz after a few minutes. "Interactive" does seem to be working properly though, but at times, it also won't scale above 800 MHz either. Benchmarks confirm this is not a "reporting" problem either, the CPU actually isn't scaling up correctly.

Other than that, everything seems buttery smooth! And on a side note, *knock on wood*, I've been able to undervolt a lot further than with previous Onix 2.2.1 kernels. With Onix, setting the 100 MHz step to anything lower than -75 would cause sleep deaths, and charging deaths, but all that seems to be gone now. And I'm getting more stable undervolts at the higher end of the spectrum too, like with the 800, 1000, and 1200 MHz steps.

Keep up the good work Existz! :D
[Captivate Android Development] astrocrep:
Hey existz... so I flashed back to 0.1.2, and my home button is working fine again...

I saw in the change log for 0.1.3 you mentioned something about a key driver...

Any change that might have something to do with it?

Thanks
[Captivate Android Development] existz:
What do you mean skipping from 800 to 1200?
[Captivate Android Development] rajendra82:
I think there is something really weird about the memory situation on our phones. I am not technically competent enough to make sense of all this, but I am sure you can explain to me what is going on here. This evening I decided to check on the memory usage on the Captivate, HTC Status, and Nook Color. All three devices are running different flavors of Gingerbread, and all are specified to come with 512 MB of RAM.

When I looked using "Settings -> Applications -> Running", I see that the Captivate had 161 MB of memory used and 107 MB free, the Nook Color had 126 MB used and 272 MB free, and the HTC Status had 170 MB used and 212 MB free. If you explained the difference in the free memory between the Captivate and Nook Color is due to the Nook Color lacking the need for a reserved memory block for the Camera and another for the 3G Radio, how does one explain the large amounts of free RAM in the HTC Status, which also has a 3G radio, a 5MP camera, and a 1.3 MP front facing camera. Surely the HTC Status also needs the same or larger contiguous blocks of RAM as the Captivate does. How is it that the total amount of memory it shows is nearly the same as the Nook Color, while the Captivate has over a 100 MB less?

The second thing is that when I held home on the Captivate, the Task Manager dialog popped up, which has a button that took me to the Memory management app, where one can free up RAM. Unfortunately the recent apps window that comes up when holding the Home button on the Nook Color or the HTC Status does not have that button, so I can't compare what the equivalent usage is. How are the numbers in Task Manager so different than the numbers shown in the settings menu, and what is the relationship of the 161 MB used 107 MB free shown in settings versus 284 MB used out of a total of 340 MB shown in task manager, which were read seconds apart?
[Captivate Android Development] SuperSync:
I have lost the 1000MHz step since my first upgrade to .13 and all the way thru .15 I'm running now. 1200MHz version. CPU spy shows no 1000 state, nor does Voltage Control or Control Freak. Voltage settings wiped repeatedly in recovery.

Goes from 800 directly to 1200.
[Captivate Android Development] LNJ:
I had the Acer Liquid E before this which had the Snapdragon chipset like the Desire and Nexus One and upon boot I would have close to 270mb free.

But Hummingbird devices seem to reserve more for hardware acceleration and the rest is unknown.

Basically it's false advertising to me on Samsungs part when you only have 1/3 of advertised ram available!
[Captivate Android Development] existz:
Thats how its suppose to be, 1ghz step was removed in 1.2ghz version.... steps are (100-200-400-800-1200)
[Captivate Android Development] pikachu01:
Learn to read a few posts back. The 1.2GHz version removes the 1GHz step to increase stability and for it to scale better. Having 5 steps is better than 6 steps in increasing stability.

Edit: Wrong quote
[Captivate Android Development] artvandalay22222:
I know its off topic, but when I flashed talon 4.3, I lost Continuum boot and shutdown animations. The samsung boot and shutdown animations run instead. Ivesince flashed several newer versions of talon, same thing. Ive tried replacing the sanim.zip in sytem/media but its still just running stock samsung animations

Not a big deal, just trying to figure it out. Any ideas?
[Captivate Android Development] motive:
Oh... Its supposed to go from 800 to 1200... my bad. :-X
[Captivate Android Development] manny05:
This is true and I agree. But you do have to admit samsung does a great job with what it's got. I played with many htc phone like the inspire and evo and they both have 8megapixel camera yet the quality was worse than my Cappy.

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] georgem106:
Guys...can somebody help? I am on Dlev's 4.2 rom and i flashed Talon 4.14.15. It was working great for about 30 minutes and then it started to reboot. The at&t screen starts then it starts to load Talon but when the progress bar is half way, it reboots. How can I get back to the previous kernel? I cannot get my phone into recovery. Please help.
[Captivate Android Development] iXNyNe:
I'm no expert, but you could try extracting the zimage from a talon release and flash with Odin,then get into recovery and properly reflash the cwm zip

Be sure to use the same version for both and download a fresh copy before attempting

Also, feel free to take a second opinion over mine, that's just a loosely formulated idea.
[Captivate Android Development] georgem106:
I cant get my phone to go into recovery
[Captivate Android Development] existz:
Sounds like a bad flash, especially if it wont go into recovery, but Flash with Odin
[Captivate Android Development] georgem106:
Can you walk me thru flashing with odin? its been awhile.
[Captivate Android Development] existz:
I use linux and heimdall so its been awhile since i flashed with Odin, but basically...you will need to extract the zImage from the zip, then use something like 7zip and .tar the zImage, OR just dload an older version of Talon thats in .tar format (link in the OP to older versions), and just replace the zImage..

Open Odin, then place the phone in download mode (with i897 gb bootloaders: insert battery, hold both volume buttons and plug in USB.... with i9000 gb bootloaders: insert battery, hold vol-down and plug in USB), Odin should then recoginze the phone, place the tar in the pda slot and flash.., If you dont already have drivers installed on your PC, easiest way is to just download Kies, install it but you dont have to run it, just install it so it installs the drivers.

But its very very very very hard to permi-brick from flashing a kernel, ive pulled the cable in the middle of a flash 100x on accident, if something goes wrong, just put it back into download mode and flash again..

Not sure if Adams 'Unbrick' will help, havent messed with it much so im not sure what all it does, but worth looking into ...http://xdaforums.com/showthread.php?t=1153310 ..

Kies: http://www.samsung.com/uk/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
[Captivate Android Development] F1reEng1neRed:
For me anyway, it shows talon/galaxy s on first boot after kernel flash, but reboots after that show the continuum boot.
[Captivate Android Development] manny05:
Great job exist

Everything is looking mighty smooth :) every update brings a slice of goodness lol at least in my end

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] kodos96:
Well I'm just guessing about the HTC status, but it's possible its the same deal as with the samsung infuse - it's advertised as having 512mb, and has nearly identical hardware to the captivate, but it has over 100mb more free memory. I think the deal is that it actually has 640mb, which, after subtracting the 128mb reserved for the various hardware components, comes out to 512. The captivate on the other hand, has only 512 total, minus the 128 for hardware reservations.
[Captivate Android Development] jontoo:
It is very strangely, when I flash the latest 0.4.4.15 my back buton not working anymore it's hapen and with 0.4.4.14 yesterday, anybody with same problem :confused:
[Captivate Android Development] iXNyNe:
Make sure if you're using a captivate you grabbed the captivate file (not the i9000 one) and vice versa