yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] lpsi2000:
Okay, you guys convinced me to try 1.3.3 again. I am going to configure it according Arffer settings.

BTW, I am also joining group in stealing signatures information:) save me the trouble of typing most of it.
[Captivate Android Development] stuff:
I've never been able to get the JPP modem to work properly. It just gives me either GPRS or no service.
[Captivate Android Development] zelendel:
I will be closing this thread for a short time today to do some cleaning. Just a heads up guys. Oh and come on, we are adults the flaming each other needs to stop. I am normaly an easy going guy so please respect each other and no more attacks or i will be forced to no be so easy going.
[Captivate Android Development] vinunleaded182:
since moving to 1.3 my phone startng having sleeping death issues just like Unhelpful's kernel.

Is there anyway you can compile a version that does not have the OC/UV feature?
[Captivate Android Development] thecellx:
Still with charging issues

Im still facing the AC charging issues reported by many people here. I can charge the phone without issues when the phone is on... but when its off the restarting appears. I take out battery and tested.. and nothing seems to change. Tested with another battery and cable from a phone running stock Eclair... and nothing. This issue is related with the kernel. I dont need to be a computer expert to charge a phone.. im not doing anything unusual... What can i do ??
[Captivate Android Development] shaolin95:
I guess it depends on the ROM and what not because if it was jut the kernel we all would have the issue and mine works perfectly fine and so do others.
[Captivate Android Development] thecellx:
Im on exactly the same ROM and kernel as you. When i was at Cog nothing of this happened... even with Darky and 1.2 kernel things works. What i want to confirm now, is that the phone is actually charging turned off... but it still restarting every +/- 5 minutes
[Captivate Android Development] shaolin95:
Then if you are in the same rom and kernel I am and mine works but yours does not, then guess what, it cannot be the kernel as I did not modified mine ;)

I suggest starting all over with Odin one click, and all that fun stuff in your case...at least that is what I have done when things are not working for me and do for others and usually that get rids of any issues lurking in the shadows. :eek:

I had issues with 1.3.2 charging and restarting so I went back to a ROM back up and reflashed 1.3.3 and all is good now.
[Captivate Android Development] Sulphur4724:
FWIW: Deviant rom JPA/JPP with 1.3.3. Mine does none of that charging snafu business (yet), tho it does shut itself off once in a while. (Frickin' annoying too, wish I knew where to start. Read a rumor that it may actually be launcher pro causing that but haven't had time to follow up.)

I did have the issue where when it's off and you unplug it the battery icon showing 100% stays on and you have to pull the battery to go forward tho. Once.

I had the shutting itself off problem way before setiron's kernel tho. On cognition mostly, several versions, and on Deviant a while back when it was Shep211's. JPK if I remember right (which would be something of a small miracle if it were true!).

I dunno.
[Captivate Android Development] thecellx:
Understood. And thank you for your answer.
[Captivate Android Development] shaolin95:
No prob mate, it was quite bad when it was doing it to me so I know the feeling, thankfully I had that previous back up and reflashing 1.3.3 solved it.

Mine was shutting down with either USB or AC before that.

I am pretty sure it was because I forgot to reset the UV before flashing 1.3.3 so that is one mistake I wont make again lol
[Captivate Android Development] TheTodFather:
This is definitely an advanced thread because their is soooo many variables even with he kernel itself.

*it has over clock

*it uses reorient

*it can be undervolted witch creates many varibles with the settings a user configs

*lag fix

Plus you have other varibles like

ROMs and the bugs they bring

Modem

and the sequence one does to flash these two.

Thats a lot of variables at least you have narrowed yours down a bit. Which is a good start.
[Captivate Android Development] arffer:
Use the Voltage Control app to set all UV settings to '0', and check the box to limit the OC to 1000. Save the settings, and set to load on reboot. That should then be the same as a kernel version with no UV/OC.
[Captivate Android Development] TheTodFather:
I have not experienced this sleep death as you are referring to. I am running the lastest of both reorient and voltage control with doc's rom. Everything is working for me my new voltage control settings are:

50/50/75/100/125/125 now have it on bfq. Running advanced JFS
[Captivate Android Development] joedon3:
I had this problem when I first charged after flashing. I didn't pull the battery, but it took over 2 minutes to acknowledge that I pressed the power button and then booted. Everything has been fine since.
[Captivate Android Development] arffer:
I don't think The TodFather has any issue with anyone that is 'checking' the thread. I know I certainly don't. The issue is those asking the same questions, over an dover, that can be answered by taking the time, and investing the effort into reading the whole thread. NOT by taking the shortcut and posting a question expecting those of us that have read the threads to save them the effort by answering them.

They complain that they don't have the time to read 70+ pages of posts. Guess what? There would be A LOT less pages of posts if people didn't keep being lazy and posting these questions over and over. If they read first, they would in all likelihood find their answer and no post at all would be needed. Making the thread MUCH shorter.

I've seen this over and over, a short concise thread starts, and as soon as the rom/kernel becomes popular and the masses want to get involved, the thread explodes in size with hand-holding requests. Just reading what has already been answered would keep threads so much shorter.

So, I add my vote to the request to the Mod that if you are cleaning up the rants/flames, please also clean up the scores of repeat questions and their repeat answers, and especially the please for help that contain no actual helpful details that allow help to be given.
[Captivate Android Development] smokestack76:
Thats what he is talking about. We need to keep the questions related. And not just the same ones over and over because no one reads. I can go back page after page and the same question is on there. Most with a answer. Zel is going to clean house post wise. Its up to everyone else to maintain that. Use PMs if its a dumb post. Or if it makes you mad or something send a PM and tell them to read. Lets not clutter this thread up again :eek: Please? :cool:

From my post on lets not talk about flame wars or what not. Just stay on topic or Zel is going to use one of us on the fire! Its not my fault or your fault. We can all agree to disagree lol.
[Captivate Android Development] Stephenv1971:
Right, this is why I ensured I was stable under xcaliburinhand for weeks before trying it out. And it wasn't easy. I know I should have just jumped to 1.2 and been happy but now that I know I am on a stable ROM for the way I use it I want to contribute to make this kernel all that it can be. I know I am one of the few bluetooth users, it is the main reason I jumped to the tatuyama rom, because it had voice dialing and the BT was good enough in sound quality. And I still have some bugs like a slow laggy browser that I won't mention in the thread. I have over 15 years of linux experience I can bring to this table and quite honestly these dev forums remind me of the linux culture from the mid 90's.

This kernel is based on xcaliburinhands so it should have some of the same history. I believe Setiron is being aggressive with some of the kernel tweaks and waiting to see if anyone has problems, at which point he can back them out a bit. When someone posts results they are giving the information and may not be necessarily asking for help or for someone else to tell them they are doing it wrong. So I stand by my results and wait for Setiron to come to conclusions.
[Captivate Android Development] lpsi2000:
Is it faster than reoriented optimized memory version?

I am interested on your lagfix configuration because you managed to stay with it knowing all the issues with i9000 kernels on the cappy. It must be pretty damn fast

Are you overclocking? I am currently running reoriented 2.1.2 with memory optimization and my phone pretty snappy now. It sounds like with this kernel my phone would be snappier but I am waiting to see how I should configure it when I flash this kernel

ridiculously fast sounds pretty good. If I have voodoo already and flash this kernel without disabling voodoo, can I switch from one lagfix to another without first disabling the first one? Also what is your current lagfix configuration for the blazing speed:D
[Captivate Android Development] andars05:
I can't seem to get JFS Advanced to work. It says it's creating everything, then just reboots back into recovery saying that configs differ. It does this over and over.
[Captivate Android Development] ThisWasATriumph:
http://xdaforums.com/attachment.php?attachmentid=428512&d=1288261929

Flash with clockwork.
[Captivate Android Development] glitterballs:
Yeah...and jfs overkill WITHOUT data bound doesn't work either. Just a shot in the dark here, but maybe jfs wasn't selected during the pre-compilation configuration.
[Captivate Android Development] opcow:
Running Darky's Raw Steel. Same here. Voodoo mode worked. Tried other options and either got the same behavior or a boot loop with a log screen scrolling lots of filesystem stuff. Even a CWM reflash of Darky's didn't fix it. Ended up doing an odin flash to 2.1 and then reflashing my 2.2 ROM from that.
[Captivate Android Development] amerikian:
same

Currently Master Cleaning :) going back to Doc's 7.5 with high speed data w/voodoo probably will still use it for the advanced CWM options and what not

:rolleyes:
[Captivate Android Development] glitterballs:
Advanced ext4 worked for me.
[Captivate Android Development] Dani897:
has this been tested on cog 2.3 b1? some ji6 kernels work some dont so i have no idea about i-9000 kernels.

also how would i activate one lagfix or another?
[Captivate Android Development] topshelf95:
I just flashed this right over the latest Cognition 2.3b (not 2.3b1). Seemed a little slow at first, ran a linpak and the mflop came back 30 secs later at a score of 2.35!! :eek: Boooo! I rebooted and it seemed to take after that. Now running noticibly faster than before. This is almost as good as the faster Eclair Roms that were available, but still some lag in browsing pages with larger content. I did flash this right over voodoo without disabling it first, everything went fine. First screen shot here is of Quadrant Advanced running straight Cognition, Second is Cognition running this kernel. You can see from the breakdown at the bottom that this kernel has an increased effect on all areas. (I'm already missing DG's boot animations! :() :D All the other shots are using this Kernel. Everything seems stable so far, no FC's, I can download from market, wifi, 3g all work, I even tried 3 button download and can confirm it works fine. Hope this helps.
[Captivate Android Development] peachpuff:
Ditto, running just fine for me with killer23d's v7.5 rom.

Reboot your phone to recovery mode. Under "Advanced ULK", there are some new options:

Reboot to download: switches to download mode

Run 2e recovery: Switches to 2e recovery

Install superuser: installs busybox and superuser to the phone

Lagfix options: switch between various lagfix schemes

Tweak options: switch between various startup tweaks

BLN options: Turns BackLightNotification on or off

Reset permissions: Resets permissions to the same state as init does

You'll have all your lagfix options in there.
[Captivate Android Development] WickedStyx:
BLN support not working for me either with cog 2.2b9. Is there something that needs to be done to enable it?

EDIT: disabled and enabled BLN in recovery. Still no luck.
[Captivate Android Development] DOAlaboratories:
a little off topic, but is anyone getting the best GPS results ever with the JPP modem? without altering any settings i'm getting instant perfect locks.
[Captivate Android Development] bts0uth:
ext4 advanced works but nothing with JFS does.
[Captivate Android Development] Dani897:
working awesome, now just needs bootanimation.zip support and control over the gpu clock.
[Captivate Android Development] DOAlaboratories:
and then an espresso maker and a chinese wok add on and we're set :D
[Captivate Android Development] rob989_69:
Mmmmm Chinese... ANyone else hungry???
[Captivate Android Development] crazililazn:
So, i flashed the kernel, and using the undervolt tool, I am running stable at 1.2 ghz, with a 0.25 mv undervolt. Stability tested with the setcpu stress test and asphalt for 30 min each.

Gonna try to get lower :]
[Captivate Android Development] WickedStyx:
Did you set 0.25 mv for both 100-800mhz and 1000-1200mhz?
[Captivate Android Development] crazililazn:
0.50 for the 100-800 mhz, and 0.25 mv for 1-1.2 ghz. Btw, EVERY CPU IS DIFFERENT. not all chips will overclock the same. so you have to find out what is stable for YOUR individual chip.

This is not only for you, but for everyone else trying to find their "perfect" overclock. For example, some may be able to undervolt A LOT and still be stable, while some can be unstable without undervolting.
[Captivate Android Development] tytdfn:
Go for it!(and tell us the results obviously ;) )

I have made an update.zip file. It should be flashed in CW. I'm not sure if it will work in 2e since its not signed or self-signed.

Warning: Use at your own risk

^^ goes without saying

I took the template from both the reoriented kernel and the cognition update.zips.

i haven't tested it but it will work. Im too busy with hw right now to do this. I wish i could. Anyways have fun!

Sorry can't upload to xda cause the file is too big

EDIT: No bln version because apparently its not working. When SetiroN logs on ill tell him about the package i made.

Edit2: http://www.mediafire.com/?39rv408qddtbo76 <- Working version (its been confirmed)
[Captivate Android Development] TheTodFather:
THen what makes this even more insane is that not all silicon is made equally. So your CPU/GPU may hiccup when uv or oc. hahaha
[Captivate Android Development] joedon3:
Is there a way I can verify my UV is actually UVing.... My current setup is: -100, -100, -125, -150, -150, -150. with no problems at all. I'm starting to wonder if it's working. :-)

Edit: errr, damn! it just froze on me loading Android Info App.... I guess I went a little too far... :-)
[Captivate Android Development] thecellx:
Wired headset

I was wondering why after multiple kernel and rom versions, we still have issues with wired headsets. I know that many people have BT headsets, but as a basic accessory, the wired headset (even the included in the box) should work. I dont know what is the exact cause of this issue, but is really that hard to fix? Is impossible?... is anyone of the kernel masters, working on this specific topic?

Thank you
[Captivate Android Development] lpsi2000:
I am running Launcher Pro and I did have the issue once so far since updated to 1.3.3

Are you running Launcher Pro?
[Captivate Android Development] netnerd:
do you know.. you can flash other rom without disabling voodoo?

i using "No-RFS Advanced: all partitions are ext4" and i just flash (clockworkmod) congnation 2.4 without disable voodoo! nice!
[Captivate Android Development] joedon3:
CogKernel doens't support ULF, so I wouldn't try it. But if you do, let us know if you run into problems. :D
[Captivate Android Development] Stephenv1971:
Well that makes sense, ext4 is built into the kernel so in theory it should be able to work with all ext4. The thing to be aware of if you try to "disable-lagfix" is that it is only going to convert your data partition back. You'll need to go back to a ULF kernel to convert everything back or sledgehmmer everything out with oneclick and start over like most people do anyways.
[Captivate Android Development] TXRangerXDA:
I was running Cognition 2.3b2 ROM with 1.3.3 yesterday and had several of these issues. It did randomly shut down a couple of times, and if I left it charging to 100%, it would lock up and I had to pull the battery or 3 button recover it. If it was charging while off, it would cycle... Charge for a while, shutdown, start up (to the normal off charging state), repeat.

I also use Launcher Pro, and had no UV enabled.

I backed up to 1.2 and am having none of these issues, but I also switched to a Deviant ROM last night at the same time.

Thought I'd post in case this helps with the debugging/changes.
[Captivate Android Development] opcow:
Running 1.3.3. The phone was plugged into the USB cable charging. Discovered it on kernel panic screen. When I booted the phone it was at 100% charge. Set the phone aside and 10 minutes or so later when I picked it up it wouldn't wake up. Held power+up+down for 5 or 6 seconds--this key combo seems to get me out of any state the phone is stuck in so I can reboot without having to remove the case to get the battery out--and rebooted.

Had 2 more black screen freezes after that. Once while plugged in, once not.

Edit: just as a posted this I got another kernel panic.
[Captivate Android Development] keeng james:
I tried every combination of modem and installation with cog and mibile AP never worked for me. I switched to the glossy i9000 rom that came with this kernel, and its awesome. Thanks devs!
[Captivate Android Development] tnayrbj:
sorry to ask

I have tried to ask this question 3 times in the deviant forumn with no answer. I am sorry for the newbee question but I messed up my captivate and had to start all over last time.

Question:

do I just flash the flashable zip file w/modem using Rom Manager or Odin?

and if Odin do I put in PDA section?

sorry still trying to learn and I read alot of forums.

Thanks

Jon
[Captivate Android Development] opcow:
Rom Manager.
[Captivate Android Development] lpsi2000:
I got it again today. I am now switching to 1.2 until a newer version. I have to say there is definitely something going on with the kernel.
[Captivate Android Development] huyem83:
Mine was having tons of problems until I uninstalled SetCPU. Now it's stable and fast.
[Captivate Android Development] SetiroN:
I'd once again like to remind you that you should stick to 1.2 releases if you don't wish to run into any trouble, as raspdeep's OC/UV ALPHA 2.1 has proven unstable to some, and that UV settings are incompatible between 1.2 and 1.3: always delete your script when up/downgrading.

Sorry the releases are so late but I had a lot to do at work.

v1.3.4 OUT

rebuilt from scratch

even more stability fixes

build # updated according to version (#134->v1.3.4)

v1.2.5 OUT

rebuilt from scratch

additional FS optimization script to remount partitions with -noatime included in the I/O Scheduler script

fixed script execution

kernel HZ back to default

build # updated according to version (#125->v1.2.5)
[Captivate Android Development] darkamikaze:
cool i'll check it out

working great on my end X: -- 1.2.5 maybe ill try the 1.3.4
[Captivate Android Development] ferris2375:
hmmm nevermind
[Captivate Android Development] joeshmoe08:
Help

CAn someone please help me with three questions I have?

1) Will mobile AP work in this kernal?

2) Does this kernel overclock the captivate to 1.2 ghz?

3) Why should I not use setcpu? WHat will it do?

Someone please answer
[Captivate Android Development] arffer:
1- I've tested Mobile AP with this kernel, running Tat's 1.0.3 superlite ROM and the JPP modem. Mobile AP worked perfectly.

2- Yes

3- Lots of reports, on various OC kernels, not just SetiroN's, of instability issues.
[Captivate Android Development] shaolin95:
since Setcup seems to not be a good choice, what programs do you guy use to test stability?

I wish we had prime95 here :-)
[Captivate Android Development] Sulphur4724:
Setcpu just force closes on me if I try to change anything with it.
[Captivate Android Development] lpsi2000:
We you even using the SetCPU? I had it installed but I was not using it. So I uninstalled it just in case

Time for me to try 1.3.4.

Edit: Tried 1.3.4 and I have the same issue of phone shutting down and showing the green 100% battery while charging on the A/C. I going to take a look at 1.2.5
[Captivate Android Development] huyem83:
Yes, I wasted hours playing with different setting combinations with setcpu and voltage control. I finally had it with the constant reboots and decided to uninstall both programs; suddenly no more freezing or rebooting. I really want to under volt the cpu so I decided to reinstall voltage control only and so far I haven't have any problems. -50 at 1200 Mhz-1300Mhz
[Captivate Android Development] Haloruler64:
I'm doing a one click restore (is it supposed to do Master Clear for a few minutes? Bad section to ask :P but Im worried, never done it). Installing Cog 2.4, then probably this kernel (1.3.4) over it, because this just makes it run AMAZING. Thanks for all your hard work!

Also, never had an issue with reboots or shutdowns, even using SetCPU (which I stopped using)

EDIT: Haha Im a total idiot, did Master Clear in Download.... I AM a n00b in that respect! Sorry about that! Just saying, I am not a n00b otherwise
[Captivate Android Development] arffer:
Speaking of prime95, how about this app?

http://www.androidzoom.com/android_applications/tools/stabilitytest_kzml.html

Realize that a stress test will by definition push the processor to its allowed max. So, if you use Voltage Control and do not limit the max freq to 1000, then this will only test your UV stability for the 1200 setting.

If you do limit the max freq to 1000, then this will test your stability for the 1000 UV.

I have read that due to the nature of our phones, there is no other minimums that can be enforced (even using setcpu app). Even if you set the config for a max of 400, if it needs more then it will bypass the limit.

Bottom line, stress testing can only test UV at 1000 and 1200.
[Captivate Android Development] Haloruler64:
Worth it on T959UVJK2 Cog? Please don't start with bashing Cognition, I use it and love it and this kernel worked amazing (sans wired headset and MobileAP) on the I897UC ROMs. It works just the same right? Since that ROM is using the I897UCJJ4 Captivate kernel anyway I assume this will work. Correct me?
[Captivate Android Development] crazililazn:
Basically, the way to test your uv and see if it is stable at lower clock speeds is to use it for a couple of days doing your normal stuff.
[Captivate Android Development] MikeyMike01:
Backup

Give it a whirl

See what happens

????

Profit!

That's what I do, works great. :cool:
[Captivate Android Development] Haloruler64:
Thanks! Love the structure, /b/ro
[Captivate Android Development] lpsi2000:
Well, 1.2.5 is doing the same thing 1.3.4 was doing for me. It is basically shutting itself down during charging. I am going back to 1.2 to see if still happening.
[Captivate Android Development] SetiroN:
Any chance you could master clear, wipe battery stats, one click to JF6 and try on a fresh install? It's been reported before that problems caused by earlier 1.3 kernels persisted until doing a fresh install, and I'd like to confirm it.
[Captivate Android Development] newter55:
I did that when the new kernel came out yesterday and had no problems until I borked it doing something crazy this morning. Restored a nandroid and flashed new kernel, problem reappeared even before I changed voltages so I am going to start fresh again.

So, I believe you are correct setiron, or restoring the nandroid caused issues, and will update later with my results. Currently using doc's jpo with your kernel as it "seems" quicker than jpa...that and I like to be different......