yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Seanbest:
When I tried to paste it, it says not enough disk space to perform the paste.
[Captivate Android Development] kitkitfok:
1. Because you are using i9000 bootloader, if you are using i897 bootloader, you will see at&t booting screen.........

2. Yes.
[Captivate Android Development] johan8:
1. There are three boot logo in the system.

First boot logo is in PARAM, if you want to change it,

modo your own PARAM than flash back to your phone.

Second one is in Kernel, bascially you can't change it unless you recomplie the kernel on your own.

In stock rom, first and second logo are the same, so you only see one logo.

The third one is bootanimation.

2. Old CWM is in GREEN. Talon is in amber yellow,

I'm not sure your yellow is amber or yellow.

3. Don't make it too serious, it is just an illustration.

4. The stock auto brightness is just like that, there is tweak in this forum.

5. Try the different settings, see what fit you.
[Captivate Android Development] Kyuta Syuko:
you could just make a sanim.zip symlink to bootanimation.zip and that'll work too.
[Captivate Android Development] existz:
As of right now I personally don't plan on developing for ICS for SGS (would need a SGS to dev on, with TalonDEV its alot easier since so much as already been done, but starting from a fresh source/release I'd need an actual device) but that doesn't mean one of our team members won't take on something, then which I could contribute to some, but I couldn't take on the full project myself without atleast having something to dev on
[Captivate Android Development] iamprayl:
my phone froze when I put the 1300 module on init.d folder. now im bacj to 0.5.1.5. anyone experienced this problem?
[Captivate Android Development] existz:
Not all phones can handle 1300..., also you might have to adjust the voltages for your device so its stable.., for some devices the current default voltages for 1300 might be to much, which can cause lockups/rebooting just as if it wasnt enough.., also for other devices the current voltages might not be enough..., it all just depends on your device.. So you might have to tweak the voltages some, either up or down..
[Captivate Android Development] existz:
0.5.2.3 Public Test

UPDATE

0.5.2.3

- cpufreq: lower voltage a notch for 1300mhz step

- cpufreq: introduce 1120mhz oc version (experimental)

-- added new enable_oc_1120 script in oc-scripts.zip

To overclock, extract the oc-scripts.zip and use the preferred script

of your choice in /etc/init.d/ . Also make sure to set permissions on

the script so it works!. We will have the option to adjust oc via app

shortly, so just use the scripts for now. As of this test it still uses

normal Talon LMK settings, once pikachu01 is set on some new LMK

settings and they have been tested to be ok, I will include them in

the next test/release.
[Captivate Android Development] topiratiko:
Anyone who knows how to make a cwm zip pm me. I have new lmk settings that work great for me that id like to share...will be an update to oram+

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] JKenvin:
I have upgraded to the latest version - have enabled the OC mode, but there is a problem that the machine is restarted after a short time (which may be due to reduced electrical impulses down my 1300 to 50 / 800-50 / 400-75 / 200 - 100 / 100 - 100, before it is used normally with the 0.5.1 - RC). Is there any problem with this new version?
[Captivate Android Development] existz:
No, there's nothing wrong with latest version. 99.9% of the time when there's reboots/freezes it's due to unstable oc/uv, .. not every device can handle 1300mhz, also some users may need to adjust the voltages to get it stable (either it be by lowering them or raising them, there's a 50+ mv limit when raising voltages..you can raise them with VC+ or by manually editing the oc/uv script. If it doesn't happen with stock frequencies/voltages, or even @ 1.2ghz, then either the device simply cannot handle it or you need to adjust the voltages -/+ to your devices requirements..
[Captivate Android Development] topiratiko:
@Existz

Do yo miss the Cappy or do you consider Inspire the better mobile device?

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] existz:
Some things i miss about cappy, screen is of course nicer on captivate, but being larger on Inspire helps out.., other than that i prefer the Inspire. Plus for what I do (kernel developing) its a little bit better with the Inspire, not limited by propriatary closed source samsung drivers..which was main reason I went to another device..
[Captivate Android Development] Seanbest:
My wife has the Inspire. Nice device, too bad she won't let me do anything to it. It's S-OFF, rooted, and bloat removed. That's it.
[Captivate Android Development] chappatti:
Can the 1300 be accessed with Tegrak or do I have to move the script?

Thanks.

---------- Post added at 01:48 AM ---------- Previous post was at 12:57 AM ----------

Yup, my mistake. :) Just too much flashing per hour and totally confused..........
[Captivate Android Development] johan8:
The first boot screen is not in bootloader.

It is in PARAM.
[Captivate Android Development] Kyuta Syuko:
Correct, but it's the bootloaders that load/call it.
[Captivate Android Development] mrhaley30705:
TRusselo just posted GB source,2.3.3, i896. Yes, I said SOURCE!
[Captivate Android Development] chappatti:
Really weird

I have a weird battery problem. I went thru 2 charge/discharge, calibrated and yet.......my battery meter always stays at 99% and it says fully charged. So i leave it on overnight to see if it reaches 100%. My battery is actually discharging !!!! I lost 25% charge when still on the charger.....?????????

Does this make sense?
[Captivate Android Development] IDoMy0wnRacing:
Might be a silly question... Did you clear the battery stats in CWM before recalibrating?
[Captivate Android Development] jde984:
This is a known issue when using an i9000 based rom. Not really anything you can do.
[Captivate Android Development] johan8:
I think that probably a problem of Samsung.

When the battery full charged and reach 4.2V, it is full, but the indicator still read 99%.

Just leave it for couple minutes, the indicator will raise to 100%, then unplug in that moment.

Don't keep charging, the battery will discharge from the charger.

It is due to bad design of the charge circuits.

Not a surprise many phone also like that, but not all.....
[Captivate Android Development] chappatti:
@ jde894, johan8:

Thanks guys, good to know. :) Yes, it does not happen on i897 ROMS. Been on KH3, KJ3 and this is not seen, now back on Apex 10.1 , so I thought I flashed all wrong or something. Never came across it before. :o
[Captivate Android Development] mangesh hotkar:
i m on pinaccle 1.2,last nite tried this kernal with CWM method,after installation phone reboot and a long conversation about lagfix, phone once again restarted shows at&t logo and loading screen of kernal repeatedly.what i did wrong?.
[Captivate Android Development] Gromlakh:
Pinnacle is a Captivate-based ROM. TalonDEV will only work on i9000-based ROMs that have been reoriented to run on a Captivate. Therefore, you cannot use this kernel with Pinnacle. Use boog's kernel that came with the ROM, or switch to an i9000-based ROM if you want to use TalonDEV.
[Captivate Android Development] mangesh hotkar:
thanks man,i m on at&t gb bootloader,can i use i9000 based rom on my cappy?. means can i use rom from galaxy s section ?. i m confused ,need help.......
[Captivate Android Development] watsa:
yes you can use I9000 ROMs. But if you plan on using ROMs from I9000 section be informed that you would need a reoriented kernel (Talon kernel from OP of this thread) & home button fix. Even after doing all this you would have reference to video calls and no home haptic feedback
[Captivate Android Development] mangesh hotkar:
is their any other kernal is avail which support voodoo color fix for captivate gb bootloader...
[Captivate Android Development] kitkitfok:
Would you include charging tweaks like GALAXIAN?

- uncapped charging current USB (96mA < 500mA) / AC (600mA < 800mA) [say whatever you want, this is SAFE and will not harm your device!]

I feel charging on USB/computer is too slow.
[Captivate Android Development] pikachu01:
I don't recommend increasing the charging current. This would happen:

http://xdaforums.com/showpost.php?p=18948861&postcount=6486

I reckon having your phone overheating every now and then wouldn't be good in the long run, reducing the life of the phone.
[Captivate Android Development] Time_Zone:
Would the source that trusselo just posted make it possible to make this problem disappear?
[Captivate Android Development] mrhaley30705:
That, and someone mailing existz a Captivate to use for development:D
[Captivate Android Development] existz:
I diff'ed the differences between the I896 GB source drop and with i9000 source, there is some differences, so ill put up a test version (not an official test release on only non-bigmem version for now), for those with the issue to try and see..if it does fix it then ill put up an official test release as normal..
[Captivate Android Development] topiratiko:
If anyones interested...I updated Oram+

If your experimenting with lmk settings try it. Working very well for me
[Captivate Android Development] existz:
Battery Test

0.5.2.4-BATTERY_TEST

- synced battery driver with I896 GB source drop

This test is for those with the issue where phone charges, once charged it starts to discharge even though its still connected to charger.. let me know if this helps or makes things worst... As of now, only providing non-bigmem version, this is just a pre-test to see if it even helps, if it does then ill merge changes into an actual public Test release as normal

To overclock, extract the oc-scripts.zip and use the preferred script of your choice in /etc/init.d/ . Also make sure to set permissions on the script so it works!. We will have the option to adjust oc via app shortly, so just use the scripts for now. As of this test it still uses normal Talon LMK settings, once pikachu01 is set on some new LMK settings and they have been tested to be ok, I will include them in the next test/release.
[Captivate Android Development] smully1:
Existz just so I'm clear, is this a kernel that could be used on a kj3 rom?
[Captivate Android Development] existz:
Nope, only i9000 based roms (JVR,JVS, JVT..etc)
[Captivate Android Development] CuriousTech:
The new one charged to 100%, then after 30 minutes it finished the real charge and switched to battery but still showed 100%. I played some games for about 45 minutes and unplugged it and it went from 100% to 85%. Kind of the same as older methods that show 100% while plugged in.
[Captivate Android Development] existz:
Ok, so its probably using the old method where it lies about the actual percentage ..well, was worth a shot... atleast we now know its nothing in the actual battery driver causing it...which could be a good thing, time to look else where
[Captivate Android Development] AceofSpades90:
Cant wait for the next release! I think i might end up trying the test version :p Is there anyway to implement gyroscope into the phone? I mean it has 6-axis accelerometer and all but its not the same thing as gyro-sensor in iphone4? while on the other hand i've heard people talking about playing 1080p video on the sgs captivate some how.. I know i sound demanding but this is the coolest kernel out there, captivate can really beat iphone 4 completely :)
[Captivate Android Development] holeindalip:
So far my battery doesnt drop down like it used too once at 100
[Captivate Android Development] mikehe:
how do i check and what will it say if i loaded the latest beta kernel properly
[Captivate Android Development] chappatti:
Post deleted !!
[Captivate Android Development] topiratiko:
Tired of lag after extended uptime? Cant leave Talon because its the ****? Wanna regain the smoothness WITHOUT a reboot? Run this 3-5 times and watch your free mem grow :D

http://www.appbrain.com/app/freememoryrecover/com.fantasmosoft.free_memory_recover
[Captivate Android Development] johan8:
It is just like all other TaskKiller apps.

Useless......

After tasks killed free mem will grow.... for a moment,

then used mem will grow again.
[Captivate Android Development] reinbeau:
I flashed the latest kernel here and a day or so later the +ORAM+ mod, now my phone shuts down whenever it's left for a long period of time (overnight, not on the charger, etc). This morning I had to turn it on, and the battery was at 76% when I turned it on, so the battery didn't die overnight. If I reflash the kernel, will it wipe out the ORAM mod? Then I can watch it to see if it continues to happen. That's about the limit to my abilities to troubleshoot :o

Oooh, sorry, edited to add my device info - Samsung Captivate, Serendipity VII Build 3 (new signature doesn't have the info in it).
[Captivate Android Development] pikachu01:
Try to flash ThunderBolt! and see if it solves your problem :)

Are you UV/OCing?

Any tweaks used?
[Captivate Android Development] reinbeau:
No other tweaks, no UV/OC. I'm a bit put off by ThunderBolt because of the journaling thing, correct me if I've misunderstood, but I don't want to bork anything by a battery pull...
[Captivate Android Development] pikachu01:
The journaling thing is optional. You can choose not to do it actually.

There are two features that risks corruption:

- remount

- patched libsqlite

Both are optional and can be opted out :)
[Captivate Android Development] topiratiko:
Early models of cappy suffered random shutdowns. Its a hardware issue

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] psych0phobia:
Not just early ones, though it is far rarer with new ones. I had an 1106 that had to be replaced for this issue.
[Captivate Android Development] topiratiko:
Mine used to shut down multiple times daily until jvp voodoo kernel by existz...since then it hasnt shut down..been 4+months

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] reinbeau:
Not this Captivate. I've had it over a year now, this just started to happen two days ago after flashing what I described in my post above. Trust me, I'm not a noob at observing my phone and learning. :)

Sent from a state of Serendipity
[Captivate Android Development] mrhaley30705:
Iirc, existz packs a kernels cleaning cleaning script in his kernel, which should wipe out the oram mod. If you want to be sure, I have a link for the kernel cleaning script I use on MIUI/CM7 kernels, except it's made for Samsung based roms.
[Captivate Android Development] reinbeau:
This is what I thought. I'll flash the kernel again, and just leave it be to see if that clears up the shutdowns, and proceed from there.
[Captivate Android Development] topiratiko:
@reinbeau

Wierd.

Its IMPOSSIBLE for oram to cause it as its ONLY changes to ram.conf

I havent upgraded to newest kernel as im perfectly content with 5 rc1 so i cant comment. I suggest trying 5 rc1 before newest oc modules were implemented to see if it helps.

I HIGHLY suspect the shutdown issue.

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] reinbeau:
I'm not saying it's +ORAM+, as I said, I flashed them both quickly in succession, I didn't test the kernel long enough. I'm sorry, but I just can't believe for one minute that it's the shutdown thing, it would have been an issue from day one, and it has *never* happened to me. Ever. Until two-three days ago. I'm reflashing the kernel as we speak, I'll let you know how it goes.
[Captivate Android Development] existz:
Also make sure you don't have any oc/uv scripts from 0.5-RC1 left over when flashing new test builds with oc module (ie Voltage Control or Control Freak settings)
[Captivate Android Development] topiratiko:
Good catch. THAT may very well be the one. Look in init.d folder and remove scripts regarding oc

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] mrhaley30705:
Shouldn't the cleaning script wipe those out?
[Captivate Android Development] reinbeau:
I have never messed around with OC/UV, I'm not that smart :o Seriously, I haven't found anything comprehensive that I can study to really understand it, so I leave it alone. I am no programmer, I'm a muddler, as in I muddle along. I've learned alot in a year, but not enough to feel comfortable messing around with settings like that. Ok, kernel is reflashed, I'll check that init.d folder anyways, just to be certain.
[Captivate Android Development] existz:
Yea just double check init.d...if your not oc/uv'ing then the kernel should be exactly the same as previous 1ghz version when the module is not loaded

It won't clear saved oc/uv settings (S_volt_scheduler), but it clears out almost everything else
[Captivate Android Development] reinbeau:
In my init.d folder are:

_99ramset dated today

S30edt_perms dated 01-Aug-08

s99acidext4tweak dated 01-Aug-08

Leave them?
[Captivate Android Development] pikachu01:
You flashed acid tweaks which is highly unstable at best. Remove all the files. Ramset will be regenerated by Talon after a reboot.
[Captivate Android Development] fuloplori:
To get rid off the S_volt_scheduler script u can do it in cwm as well under advanced/wipe voltage settings, just checked and it worked.
[Captivate Android Development] reinbeau:
Yes, I did, last kernel version. I'm getting rid of them now.

ETA I'm using Root Explorer, and it won't let me delete any of them, says they're read only system files.

ETA #2 nevermind, I am an idiot, have to set it to r/w. They're gone now :o See, I told you I wasn't that smart. :)
[Captivate Android Development] studacris:
^^ this is the guy in charge of our forum? :rolleyes:

Lol jk
[Captivate Android Development] white00gt:
Ann is a she
[Captivate Android Development] Mortem Tuam:
"Ann - Not a man"

LOL

She is in charge and don't forget it buster!! :eek:
[Captivate Android Development] mrhaley30705:
Says so in her sig.
[Captivate Android Development] studacris:
Oops, sorry bout the gender confusion:eek: . Use tapatalk mostly, no sigs.:eek:
[Captivate Android Development] Mortem Tuam:
Let me assure everyone who decides to respond to stud.....he is in all seriousness just joking.

don't think he was meaning any kind of offense....just saying, trying to avoid a stoning of my team mate....LOL

stud is a great guy.....don't hurt him please. :rolleyes:
[Captivate Android Development] mrhaley30705:
I know. But that don't mean we can't rib him a little when we get a chance:D
[Captivate Android Development] Mortem Tuam:
:cool::cool:

rib away....LOL
[Captivate Android Development] reinbeau:
I am 'in charge' of making sure you all behave yourselves - I profess no knowledge of anything technical with regards to Android, but I'm pretty astute when it comes to human relationships and forum interractions. I have learned a lot by hanging around here, and I try to help where I can.....we all have to learn somewhere.....

And thank you to those who defended my gender :)
[Captivate Android Development] Mortem Tuam:
Hi Ann :D

nice sig :)
[Captivate Android Development] topiratiko:
@ reinbeau

Nice touch with molon lave at the bottom of your sig.

---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------

Thought I was the only Greek on these forum....as for the acid tweaks i find that desextons version xix works spectacularly for me after you properly set permissions to most but not ALL of the init.d files...quadrant is nothing to judge by but i pull down 3506 with this kernel @1.2
[Captivate Android Development] white00gt:
didn't think he was serious just thought I would point out she is not a he :D
[Captivate Android Development] pikachu01:
Acid Tweaks is the other spectrum of tweaks, disregarding some rules by increasing the threshold to 15 and removing journaling by setting commit to 500. Beware when using it, as commit is a high number, any power loss is likely to cause corruption. Battery wise, v12 was a hogger as well.
[Captivate Android Development] Aztecbandit:
Ok.. so please don't make me feel bad or stupid.. but i can simply just flash this over apex stock kernel through CWM no problem right? I've never actually had to flash a kernel unless it was to flash bootloaders or a ROM, and those were through Odin.
[Captivate Android Development] existz:
0.5.2.5 Public Test

UPDATE

0.5.2.5

- updated lmk settings from Pikachu01

NOTE

New modified LMK settings should prevent memory leak, let me know how these work for you guys.., they are a little more aggressive than the recent talon LMK settings..

We are working out a couple bugs with new OC App, once its ready for release ill get a new test build up.. To OC, simply place script of choice in /etc/init.d/ and set permissions
[Captivate Android Development] Gromlakh:
Yes, you should be able to just flash it. Do all the necessary backups (TiBu and/or Nandroid) first before you flash. I've had some glitches arise on rare occasions through kernel flashing.
[Captivate Android Development] Aztecbandit:
Thank you for the kind response. And I'm sorry, but I prefer Odin. :)
[Captivate Android Development] Gromlakh:
Then I must take back my kind response!!! :P
[Captivate Android Development] reinbeau:
I have to ask you - why? You can flash a kernel without being near a computer, you don't have to know any commands, other than knowing how to reboot into recovery and select the zip - why is Odin better? Truly asking, not being sarcastic at all.
[Captivate Android Development] geokilla:
Odin flashing rewrites all the blocks or something. CWM doesn't.
[Captivate Android Development] mrhaley30705:
Yeah, I think it rewrites bml 6 and 8, whereas cwm flash only rewrites one of them(I don't remember which one). In the first 20-30 pages you should find the answer.
[Captivate Android Development] reinbeau:
I'll take your word for it - I have a difficult enough time trying to follow simple Android internal stuff, let alone wading through 20-30 pages looking for.....something......I'm not lazy, just overwhelmed :o
[Captivate Android Development] Gromlakh:
I believe he was referring to my "Support Heimdall" sig, not CWM.
[Captivate Android Development] TonyStark R.I.P.:
He... She.... What???? I thought it was an androgynous android:eek:

Just wanted to go back off topic;)

btw I'm an old noob.... will this work on cupcake:D:D:D:D:D:D
[Captivate Android Development] Gromlakh:
The "he" I was referring to was Aztecbandit, who was ribbing me about Heimdall. I believe Reinbeau mistakenly thought he was knocking on CWM.

I know Ann is a girlie. ;)
[Captivate Android Development] TonyStark R.I.P.:
Dude it's all gud... It's just all funny... You explaining it is even funnier
[Captivate Android Development] iRide113:
Am I the only one getting random reboots like crazy? :cool:
[Captivate Android Development] Aztecbandit:
If you look at the signature of the person I responded to, it says promote heimdall instead of odin. I was making a joke. :P

EDIT: Whoa 0_o i didn't notice my little joke made an entire page of posts.
[Captivate Android Development] Gromlakh:
See what you've done???
[Captivate Android Development] pikachu01:
Are you UVing/OCing?

Did you install any tweaks?
[Captivate Android Development] iRide113:
OC to 1200, and using Oram. Tried each separately - just Talon, Talon and OC, Talon, OC and Oram. Get it with all three.
[Captivate Android Development] topiratiko:
Check your init.d files for any leftovers and make sure tw4 is not your launcher

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] topiratiko:
Also if anyone doesnt mind can someone post a snapshot of the new ram.conf? Curious to see new values

Sent from my Samsung Galaxy S Captivate on Blue Apex
[Captivate Android Development] existz:
Its the same as what's in Pikachu01s latest thunderbolt
[Captivate Android Development] topiratiko:
K cool ill dl and check it out

Sent from my Samsung Galaxy S Captivate on Blue Apex