yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] waghoba:
I just flashed the kernel but I am not able to set the CPU governor to conservative. any idea what is wrong here???

Edit: nvm, got it to set min freq as 100 but what should be max freq? by default it is 1200 should I crank it up to 1400? Also I got a soft reboot while checking system information through quadrant.. :/
[Captivate Android Development] ytt3r:
SetCPU has to be open in the background, apparently. That's why I put it in the directions ;)
[Captivate Android Development] ytt3r:
I'm using the version in the OP, best advice I can give you is to flash it and hope for the best. If something isn't working and I'm not able to replicate it, there's no fix to be had. If you want, grab me a logcat from when you go to turn on tethering, that might help a bit.
[Captivate Android Development] waghoba:
ohh that was a quick reply but I managed to set it..actually after opening set cpu it asked me to select what settings I should use so I chose custom settings and then it got access to root. previously I was just opening it and leaving it at home screen where it asks you for the settings to use. :p ,, but what about soft reboot and where should I set the settings to apply @ boot time? in CM settings- performance ??
[Captivate Android Development] ytt3r:
I really wouldn't set at boot, but if you want to try, you're right. Soft reboot checking Quadrant you said? Quadrant is really, really, really bad, multiplied by 100000 in Gingerbread. You can get your info in SetCPU.
[Captivate Android Development] waghoba:
okay...btw thanks for this awesome kernel running smoothly so far, and you are right about the quadrant :D

but I have noticed that in cm settings my max freq is by default 1200 and when I try to set it to 1400 I get soft reboot. Any idea what is wrong or its just my phone not capable of 1400 ??
[Captivate Android Development] Torridred04:
Are you flashing Trident from the stock kernel in the Nightly? I believe if you flash from the stock Nightly kernel, you then install SetCpu. It should, I could be wrong, show 1400mhz as the max, 1000mhz as the min, with Ondemand governor. From there, go to CM Settings, Performance, CPU Settings, and change the governor to conservative & the min to 100mhz. That I believe is the only stable way to adjust frequencies. Anyone else feel free to chime in/correct me if im wrong.
[Captivate Android Development] ytt3r:
Don't set frequencies other than min to 100 MHz. Its a known bug with no known fix.
[Captivate Android Development] shaolin95:
Ha loving this, I scored 56192 pts in Browsermark with this ROM and Kernel. In the Anandtech review, the Atrix scored 53576 and the LG 2X scored 50877

Hey, not sure how accurate it is but looks damn impressive lol
[Captivate Android Development] ytt3r:
I beat you. 70206, right here :)
[Captivate Android Development] shaolin95:
wth did you do oced to 1.6 lol
[Captivate Android Development] ytt3r:
1400 conservative :) btw change your sig
[Captivate Android Development] shaolin95:
Working on a new sig now... :-)
[Captivate Android Development] ytt3r:
Conservative can be changed from anywhur
[Captivate Android Development] Danni3:
i think you have logo issues lol =P

heres an idea:

just contact me if you like it i could do some other ones or send you a high quality
[Captivate Android Development] ytt3r:
Wait are you running the kernel? I have a definitive logo in there :) designed by Dagnus, it looks really nice
[Captivate Android Development] jhernand1102:
So if I want to try this and if I have any issues can I just flash the original CM7 kernel using Odin and be right back where I came from or will I have to redo the whole CM7 process from scratch?
[Captivate Android Development] ytt3r:
You wouldn't have to redo from scratch, don't worry!
[Captivate Android Development] jhernand1102:
Well it appears I'm stuck in a bootloop. Oh well time to try to flash the original kernel back using Odin.
[Captivate Android Development] ytt3r:
Probably too late, but that happened to me once. You have to pull the battery and power on the phone like normal.
[Captivate Android Development] jhernand1102:
I did try that 3 times with no luck and even tried to re-flash the kernel with the same results. Anyways I'm back on stock now but I was looking forward to giving this a try. Any ideas what may have went wrong?
[Captivate Android Development] TheEscapist:
http://code.google.com/p/cyanogenmo...=ID Type Status Priority Device Owner Summary

Basically, if cwm comes to a bad block in your boot sector, it skips it, borking your install. Odin, on the other hand, maps it to somwhere else. That's why you can flash the initial stuff through Odin/the inital package.

This is a problem with all the kernels right now, mine, ytt3r's, even stock.

Unless, of course, ytt3r has a bug. :p
[Captivate Android Development] ytt3r:
I'm running this no problem. You can try Odin if you want it should give you good results.
[Captivate Android Development] EnemyOfGlaDOS:
Just flashed your kernel, but I'm getting a couple random reboots.. i flashed it from stock kernel and haven't even gotten setcpu yet.. should I reflash?

*edit* assuming its a random fluke, I went ahead and installed setCPU.. followed directions step by step.. and now we just play with the phone and see whats up.
[Captivate Android Development] captivated1971:
Tried flashing it last night with clockwork got the error 6 then i used sgs kernel flasher and it loaded the trident screen and soft bricked had to odin back is this mzybe cuz i didnt disable voodoo?
[Captivate Android Development] captivated1971:
Bu the way im on firefly rom
[Captivate Android Development] captivated1971:
But i get back into the recovery but it wouldnt let me do anything from there. So hit up good ole odin again.
[Captivate Android Development] EnemyOfGlaDOS:
hmm... was doing good, but just got another reboot. Will a reflash solve this issue or did I likely do something wrong?
[Captivate Android Development] jhernand1102:
So if I understand this correctly I must have a bad block and there is no way as of yet that I can use this kernel correct?
[Captivate Android Development] TheEscapist:
There's one guy in my thread who fixed it. I believe the latest initial package (zip and kernel) fix the problem.

First off though, can you flash kernels other than this? Try flashing the latest update, or my kernel. If the same thing happens (bootloops), you have this error. If not, it's a bug in this kernel.

If you do have bad blocks, try starting over with the latest initials.
[Captivate Android Development] jhernand1102:
Well when I was running the Froyo based ROM's I could flash different kernel with no issues but this is the first one I tried with CM7. If flashing over with the new initial packages fixes this then I will have to wait till the week end to get it done. Thanks for all the help. Bye the way I am running the latest update package of 20110313.
[Captivate Android Development] TheEscapist:
It would be a CM7 specific bug. Like i said, try flashing a different kernel (mine, or reflashing the latest update), and if it bootloops, you'll have to reflash using the latest initial. If not, it's this kernels fault.
[Captivate Android Development] redapex:
For the guys asking about FPSE. It runs... fast. I was playing Gran Turismo 2 a little earlier and its blazing fast. I didnt have the fps counter on but ill be damned if it was any slower than 35fps. If only it didn't slaughter my battery.
[Captivate Android Development] redapex:
Make that 61fps in Gran Turismo 2 with a full field of 6 cars and audio. Effing amazing work.
[Captivate Android Development] Mik3D23:
UV support in the next few days? ;D
[Captivate Android Development] sixstringsg:
This is a CM7 specific ROM.

Sent from my CM7 powered captivate
[Captivate Android Development] Torridred04:
See I've been having this exact problem others are mentioning. 7/10 times I'm stuck in a boot loop. Battery pull, try again. Sometimes it will boot up and then I'm golden, given a few random reboots.

I've flashed your kernel and it has worked fine every time, no boot loops. I was going to try the newest initials dated 0314 but I figured if I had bad blocks, I may get the same boot loops using your kernel, which I have not. I may start from scratch tomorrow using the latest initials and see if that fixes it.

Just digging the fact of being able to run Quadrant and GPU tasks at that frequency =] Love both kernels and all your guys hard work!!
[Captivate Android Development] Doug8796:
Would any of you guys care to benchmark nenamark and smartbench 10/11?? MuCH appreciated!! :-)

Also An3dBenchXL
[Captivate Android Development] staplebox:
Set up as instructed.

nenamar best of three = 38.0

smartbench 2011 =

prod - 1264

games -2055
[Captivate Android Development] shaolin95:
You only got 38 Nenamark at 1.4Ghz...something is not right I am getting 52 and even a few 54 runs.
[Captivate Android Development] Torridred04:
Guess my phone really doesn't like this frequency. I'm able to run Smartbench & Quadrant but Nenamark freezes within 1 second lol.

But for anyone who was experiencing the boot loop with this kernel, I started from scratch this morning with the newest initial kernel/zip and managed to avoid this issue. It also seems, based off of the phone mod info, that the newest initial is labeled as 0314 Nightly. So I left at that, flashed Trident, and have had a successful morning =] Minus Nenamark as my phone cannot handle it, probably PSX the same, everything else is running as it should!
[Captivate Android Development] staplebox:
You're right. The CM performance settings won't hold.

eta - had to reopen setcpu - 50.7
[Captivate Android Development] doctahjeph:
I do this, but the settings do not hold in CM7 they revert back. Anyone else have this issue?
[Captivate Android Development] ytt3r:
They revert back? What do you mean? On a reboot? They don't apply in the first place?
[Captivate Android Development] insaneturbo13:
When I set the min it just stays at 1000... Its like I never selected 100mhz
[Captivate Android Development] doctahjeph:
No, I set them and minutes later if I go back in to check the settings they are back to defaults.
[Captivate Android Development] doctahjeph:
Not sure what I did, but seems to be holding now.
[Captivate Android Development] ytt3r:
Setcpu has to be open to change the min frequency.
[Captivate Android Development] Doug8796:
btw i am getting

1259

2841

on Smartbench 2011
[Captivate Android Development] miahsoul:
Well, this is annoying. At first, I loved this kernel, was getting 2390's on quadrant. Then I found out they way I set the clocks through setCPU caused my phone to constantly reset, so I did it the way the author said it and now I only get 1200. I'm going back to the other modded kernel. This one is a little unstable/unreliable for me.
[Captivate Android Development] Doug8796:
which modded kernel was that?
[Captivate Android Development] EnemyOfGlaDOS:
Probably referring to the other OC kernel for CM7
[Captivate Android Development] doctahjeph:
it was! oh well either way I got it working. thanks again for a nice kernel!
[Captivate Android Development] ytt3r:
Glad you like it.
[Captivate Android Development] pewpewbangbang:
worked for me...........installed setcpu, opened it up, pressed home button.

Went to cyanogenmod settings, changed governor to conservative, set MIN clock to 100mhz, set max clock to 1400mhz (You should mention this also, as its set at 1200mhz default)

Did some tests, Quadrant scored a 1600 (better than running 1ghz on CM7 stock which nets like 1200) this is a horrible benchmark though.

Nenamark1 got me 52 FPS avg. Neocore scored a 64.7 FPS (Some kernels have a limit at 55.4 FPS so yea.....)

Either way, the scores are higher than before running 1ghz and 1.2ghz with the other CM7 kernel.

But 1.4ghz is too much and a battery drainer.......going back to the other CM7 kernel with voodoo and everything and UV. 1.2ghz with UV is good enough and saves battery =)

This is a good kernel though if you want the absolute best performance
[Captivate Android Development] shaolin95:
Mine always defaults to 1.4 so something was wrong there.
[Captivate Android Development] ytt3r:
Released #30.
[Captivate Android Development] Doug8796:
Shaolin what did u get on Smartbench 2010/2011?

An3DBenchXL
[Captivate Android Development] Auridran:
Just wondering if BLN will ever be added to this kernel? Love it so far though!

Also Shaolin, how are you using FPSE? I cannot get it to run for the life of me on CM7.
[Captivate Android Development] shaolin95:
I have installed this latest version of CM7 2 times now and both times FPSE works without any issues. Only on the first version I tried 2 weeks ago or so it did not work and I am thinking it could have been some of the restored settings from a 2.2.1 ROM so now I just install fresh and it plays perfectly.

BTW, any chance to get a non 1000Hz version of #30 and any newer version. I was never very fond on those.

Anyone has comments on these:

#1 My gmail was working fine...meaning push email was working but then it stopped working..I no longer get notified about new email.

#2 Is video quality a bit off compared to other roms?

#3 Rock player is among the only video players working consistently but it cannot play using hardware anymore only software...normal for this build?

Thanks!
[Captivate Android Development] ytt3r:
I could definitely do a 256 Hz version. I can do it tonight hopefully.
[Captivate Android Development] shaolin95:
Thanks mate. I just never experienced much difference between 100 and 1000 other than lower benchmarks at 1000...at least with 2.2.1 roms.

Any thoughts on the video stuff I mentioned?
[Captivate Android Development] Auridran:
Where did you get the latest version? I've only been able to find RC0.

EDIT: Nevermind. Found it under the "All Models" rather than just the Captivate post.
[Captivate Android Development] EnemyOfGlaDOS:
.. i guess it's official. I tried to run Trident a couple of times.. freezing on the android skateboard bootani then rebooting. Didn't have these issues in intial release, but :rolleyes: hopefully i will try again later down the road!
[Captivate Android Development] flashman2002:
Same thing is happening to me. It froze and now it is just going into reboot from At&T to the trident screen.
[Captivate Android Development] EnemyOfGlaDOS:
i know.. just when I thought it was gonna make it through it's fits.. nope. FROZE.

tried relentlessly.
[Captivate Android Development] Doug8796:
anyone else having issues?
[Captivate Android Development] flashman2002:
Lol...did you even read the last couple posts?

This is my Captivate. There are many like it but this one is mine
[Captivate Android Development] shaolin95:
I flashed #30 and it still shows 28 in the About Phone section. Did you forget to change that?
[Captivate Android Development] ytt3r:
You can't just change/not change things in kernels. It automatically ups the build number. Your kernel flash didn't work somehow.
[Captivate Android Development] shaolin95:
Odd...oh well I am flashing yet again after testing some themes lol

Going with #30 from the get go to see if I like it.
[Captivate Android Development] Auridran:
While I didn't have any boot issues with this kernel, I did have issues with WiFi not working after awhile, it would just say "Error" and not enable or disable.

I'm going to go back to 2.2 while I wait for CM7 to become more stable on the Captivate and wait for the kernels to be more feature-rich. There were just way too many issues so far, and I missed my BLN dearly. Plus, I abhor the stock GB theme and there aren't many Theme Engine themes, or Captivate CM7 themes yet. None with the level of polish that the Samsung theme has anyway (except for maybe MattedBlues, but I could not get any version of it to work).

I'll miss the decent speed boost over 2.2, but not so much so that it will make up for the mountain of bugs yet to be squashed.
[Captivate Android Development] shaolin95:
Matte Blue worked fine for me...just too simply only. No other issues and no way I can go back to Froyo now. :-)
[Captivate Android Development] ytt3r:
I wont be able to get a 256 HZ kernel out tonight, it should be out tomorrow night.
[Captivate Android Development] Auridran:
Well I'm glad you're not having any issues, because I'd love to be using gingerbread. It's fantastic. I just had way too many bugs to make it worth my while.
[Captivate Android Development] shaolin95:
Sorry, hopefully they will iron the issues soon.

No worry on that 256 one I am testing the 1000Hz right now.

Update: My phone does not like 1000hz as it reboot just doing a Smartbench run so yeah, I will wait for the 256 version thanks :-)
[Captivate Android Development] Doug8796:
shaolin was wondering what your smartbench was.
[Captivate Android Development] ytt3r:
Meh again with benchmarks... I will have a 256 HZ out soon though, don't worry ;)
[Captivate Android Development] flashman2002:
So what was the issue with us that couldn't get this to boot? It was never addressed by you.
[Captivate Android Development] shaolin95:
More than likely the phone cannot handle 1.4Ghz ..not all CPU are created equal and OC capabilities vary a LOT specially with these phones.

What voltage are you using for 1.4Ghz ytt3r?

Thanks!
[Captivate Android Development] TheEscapist:
ytt3r has the max initial boot speed set to 1Ghz, meaning that it can't be that their phones can't handle it. Both mine and his are set up that way.

Oh, and ytt3r, I talked to atimn about the bad block issue, he said he'll look into it and probably pull the fixes in. Just thought I'd give you a heads up about it.
[Captivate Android Development] shaolin95:
Well they are not booting so something is not working obviously but ...
[Captivate Android Development] flashman2002:
It's strange. Cleared cache to see if that would change things yesterday but it was no dice. No biggie, I was just curious to see what could be done to help.
[Captivate Android Development] shaolin95:
Weird after installing the latest update my linpack remains the same in the high 19s but Nenamark went from 44 at 1Ghz after the upgrade to 37 after installing Trident at 1.4Ghz...anyone else experincing this? I used to get 52-54 when I first tried this kernel I remember.

Neocore also went down from 64 to 56.7 (is FPS locked on #30 maybe). Still even with a locked FPS that would not explain the lower nenamark...testing #28 again. Perhaps it was the latest CM7 update?
[Captivate Android Development] ytt3r:
I'm still getting the same benchmarks with #30, might just be your install or maybe something else went wrong. It might just be that your phone doesn't like the 1000 HZ.
[Captivate Android Development] Doug8796:
why is it a huge conspiracy that no one can post smartbench 2010/2011 scores? No one tried it ?
[Captivate Android Development] jsphoto:
CM7 w/ Trident to conservative min 100hz, max 1200hz

Smartbench 2011: 617/1467

Quadrant: 1251

With max 1300hz

Smartbench 2011: 736/1464

Quadrant: 1336
[Captivate Android Development] shaolin95:
Is not a conspiracy mate is that you seem to be way too much into benchmarking...truly obsessed with it almost...click on your name then select All Posts by yourself and look at how many of your posts are just asking how much this ROM/Kernel scores in this or that...seriously...is like 90% of your posts.

I get around 2700 best and 1200 with Bench2010. I have gotten higher with Paragon but trust me, that does not tell the story on how much better the phone is...Neocore gives me about 64 so on par with Paragon ROM using SuckPunch kernel. Nenamark around 52 to some runs of 54.

So the lowest for me have been the 3D performance in Quadrant (like it matters)

In any case my phone with CM7 is like on steroids for sure.

Regards
[Captivate Android Development] Doug8796:
I saw your score on 3d3DBenchXL did u use suckerpunch with paragon on that?

BTW no offense but you are obsessed with flashing roms XD XD :P
[Captivate Android Development] ytt3r:
Does it matter what he used? This is a support thread for the Trident kernel.
[Captivate Android Development] flashman2002:
Why didn't those of us that had issues yesterday get support lol? :D
[Captivate Android Development] ytt3r:
Sorry about that, I was away from my computer. I'm only going to be on for a few today to upload the new build.
[Captivate Android Development] ytt3r:
BTW, I just uploaded the 256 HZ version. Its in the OP, hidden too ;)
[Captivate Android Development] flashman2002:
Its cool. Just throwing a jab for some humor.

This is my Captivate. There are many like it but this one is mine
[Captivate Android Development] shaolin95:
Ah but flashing ROMS do make a difference unlike running benchies ;)

Thanks for the 256 version...testing.
[Captivate Android Development] Auridran:
Yeah. Benchmarks on Android still seem to have a long way to go. I currently have the highest benchmark for any Captivate on the Antutu leaderboards with this kernel, and I haven't been able to get anywhere near that score again since.

Also, a bug to report with this kernel: WiFi will not activate if you haven't activated it prior to flashing this kernel, it seems.
[Captivate Android Development] ytt3r:
That's interesting, but not kernel specific (at least I don't think!). Sounds like an issue you should take up with atinm/codeworkx/coolya/guiper.
[Captivate Android Development] Auridran:
I didn't have the issue using The Escapist's kernel, but there's a possibility I did something different in the flashing fresh and flashing kernel process that would've caused things to act differently. Either way it's not a huge deal because if it happens I can always make a CWM flashable stock kernel, fix it, and come back.
[Captivate Android Development] apples2droids:
Can't set 1400 in cm settings. It's like it's locked to 1300. Tried setcpu and all that does it reboot, (like you said it would). Is there something I need to download? Thanks.
[Captivate Android Development] ytt3r:
You could try going in SetCPU and setting your governor to conservative, then going to 1400 max and 100 min. Should work. 1300 is going to be the best frequency for your phone though.
[Captivate Android Development] apples2droids:
Lol. changed to conservative, 1400 in cpu settings, and bam froze up. I guess I have to except my cappy hates 1400....for now. :)
[Captivate Android Development] apples2droids:
What kind of battery life are we seeing with this kernel.
[Captivate Android Development] Dani897:
does this kernel have undervolt? and is the 1400 setting more stable than the tw froyo kernels or did you test it on captivates that were already known to run at 1400?
[Captivate Android Development] shaolin95:
It does not UV yet. For me is the only 1.4Ghz kernel that has been fully stable and I tried every OCed kernel from the Froyo camp. YMMV of course
[Captivate Android Development] Dani897:
sounds good to me
[Captivate Android Development] viny2cool:
flashed over CM7 using clock work recovery...and went into phone loop...any suggestions?
[Captivate Android Development] xidium:
FWIW I had this kernel installed for a couple days and got many reboots. While the phone was idle or in use, it would randomly restart. Maybe my phone isn't meant to hit 1.4ghz....
[Captivate Android Development] ytt3r:
Its a known bug. There are bad blocks in your /boot partition. Kernels can be flashed with Odin or heimdall, but not clockworkmod 3.
[Captivate Android Development] ytt3r:
Did you set up any profiles? Make any changes to setcpu settings?
[Captivate Android Development] Mik3D23:
Flashed #30 over CM7 today, and I get a constant wifi error. Am I the only one? Is there a way to fix this?
[Captivate Android Development] Mik3D23:
..? also, I tried switching to ondemand, and it froze. just a side note. but I can't figure out why my wifi won't work. it worked on the nightly cm7 before i flashed this kernel, and it detected the network after i flashed this, and then i rebooted and the wifi gets a never ending error.
[Captivate Android Development] viny2cool:
but I think, the latest nightly update fixes that....i flashed after flashing nightly update