yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mik101:
Everything is working great so far on the Dec31 nightly with 2.9.0sc. Thanks Stratosk!

Edit: I'm getting a "Cannot connect to camera" error when I try to launch the camera app after a few runs of the Antutu Benchmark. If I restart, it'll work again, but if I run Antutu a couple times again, the same problem will occur.
[Captivate Android Development] Kyuta Syuko:
Sounds more like an Antutu/Camera issue than a kernel issue. You update/change either before you started having the issue?
[Captivate Android Development] mik101:
Haven't had a chance to play a game or two yet to see if something other than Antutu causes it. Was a busy New Years Eve.

I was running cm10 w/Semaphore 2.6.6sc without any issues (last nightly before the CM10 to 10.1 change) previously.

Now it's 10.1 running Dec31(1) nightly w/Semaphore 2.9.0sc, so yes the camera changed, but the build of Antutu is the same between both installs. I'll have to try with the default kernel when I get a chance to isolate it.

It only happens after a couple runs. I can always do a run or two with the camera still working afterwards but if i keep looping it then the camera will give that error when i open it -- if someone else wants to test on theirs.

Edit: I am using the bigmem libraries, but I don't think that'd be the issue either.
[Captivate Android Development] sephhi:
If you're running cm10.1 you should be using the 2.9.0c kernel. sc kernels are for roms with the huge mem patch such as slim or captivating.
[Captivate Android Development] mik101:
Im patching CM10.1 for hugemem manually as I (and many others on here) always have before with CM10. I accidentally typed bigmem in my previous post, but I did mention the patched libraries, which obviously has nothing to do with the bigmem option in the semaphore settings app. This method is far from new (have a read through this thread or the semaphore i9000 thread). My girlfriends i9000 is running with the hugemem patch installed and semaphore 2.6.6s (with bigmem enabled) in front of me as I type this on the last nightly of CM10. 403mb of ram available and everything works except 720p video recording. (I was running the identical captivate equivalent until I updated to CM10.1 the other night). Additionally In the CM10.1 thread it's reported that the same patching method from 10 works with 10.1 as well, so the yes the 2.9.0sc kernel would be correct when using the modified jb libraries. That's what allows it to function in Slim as well. They're just prepacked with the rom in that case.

Edit: Camera doesn't work on 2.8.3sc after running antutu either but works fine prior to the benchmarking. I'm going to just avoid benchmarking for now, and do a full wipe again tomorrow. Everything worked fine otherwise all day on the Dec31 night(lies) and 2.9.0sc with patched libraries for hugemem. It could be related to Antutu in particular as I was playing Eufloria for a bit earlier and the cam worked fine after that. I'll keep testing.
[Captivate Android Development] Kyuta Syuko:
I personally use CF-Bench just because I think Chainfire is an excellent dev and I like to support devs I think are excellent. I'm also running the Slim Bean 4.2.1 Beta 1 currently, but I'll run a few benchmarks with the CF-Bench and see if I have any issues with my Camera. Sure not an ideal comparison, but this way we should at least be able to agree it's not the kernel since I would think our camera apks are the same.

*edit*

Ran CF-Bench twice and had no issues opening the Camera.
[Captivate Android Development] sephhi:
Okay, that's a strange one. Just tested with antutu and the camera opened fine so I don't think it's the kernel. Does the same thing happen after playing a graphically intensive game?
[Captivate Android Development] mik101:
Thanks guys. I'll definitely play around with CF-Bench. I always forget about that one.

It seems to be something specific to antutu.

I played a few games earlier today (Eufloria, Streetfighter4, AngryBirds/Pigs) and camera kept working all day. It must be something to do with Antutu itself. That's much better than there being a kernel issue. Thanks for testing guys.

Edit: JetSetRadio and DeadTrigger don't cause it either. So I'm not so worried now. Working great here.
[Captivate Android Development] lavero.burgos:
Click on the clip image:

~ V
[Captivate Android Development] shuyin1102:
Tried new Interractive governor in v2.9.0 for 2 days, i charged the phone overnight and got up late for work with a dead phone :crying: Now back to 2.8.3 for stability
[Captivate Android Development] prbassplayer:
Or not use interactive?

Sent from my Slim Bean Beta 2 powered Nexus 4
[Captivate Android Development] Kyuta Syuko:
I agree what benefits are there to using interactive gov? From what I've read about the different governors there was nothing really appealing about interactive that would make me want to use it over OnDemand or what I currently use SmartAssV2.
[Captivate Android Development] shuyin1102:
Just want to test because i see the new update in the changelog, so if it doesnt work well it should be removed
[Captivate Android Development] BWolf56:
It's different from phone to phone. It doesn't work so well for you but could work quite well for someone else.
[Captivate Android Development] prbassplayer:
If you noticed 2.9.3 had upstream fixes for interactive governor from Google.

Sent from my Slim Bean Beta 2 powered Nexus 4
[Captivate Android Development] cnu4u:
Waiting for latest version :)
[Captivate Android Development] timf808:
Hi just wanted to make sure which version of this kernel should I use for slimbean 3.1 the one using 4.1.2 android.
[Captivate Android Development] m1batt1:
2.6.6sc I do believe. Anything higher than that is for 4.2. And the sc version is designed for slim
[Captivate Android Development] mik101:
Me too. :) Hoping for the 2.9.4 test. No more separate builds for CM LED / BLN. Stratosk is the man. :)
[Captivate Android Development] stratosk:
New version 2.9.4c

- Implement both CM LED and CM BLN

- fix to interactive governor (from 3.4 upstream)

- included logger from 3.4

- included Low Memory Killer driver from 3.4

- included timed gpio driver from 3.4

- removed: max frequency to 800MHz when screen off

- changes to init script for better module installation handling (thanks to mnazim)

- fixed init scripts for IO schedulers in /res/scripts (thanks to fernandofig)
[Captivate Android Development] Nick0703:
Hey guys, is this normal that when you use LiveOC, some apps start to force closed? It's been a while that I haven't use LiveOC and I don't remember having that problem the last time I used it. Should I increase the voltage more or something?
[Captivate Android Development] prbassplayer:
You can see if bumping the voltage helps to stabilize, but no sure thing.

Sent from my Slim Bean Beta 2 powered Nexus 4
[Captivate Android Development] jerkysh:
Each phone reacts differently when OC'd , i personally never had issues when OC'd, only slight battery drains...
[Captivate Android Development] Nick0703:
I'll try that. But I find it weird that when using LiveOC, my apps start to force closed, example like the browser or the XDA app. When I opened them, they just force closed right away. I have to LiveOC to default for them to work.:confused:
[Captivate Android Development] prbassplayer:
Used to happen to me when I live OC to high back on Glitch.

Sent from my Slim Bean Beta 2 powered Nexus 4
[Captivate Android Development] They Drew First Blood:
LiveOC

+1

I found that too- if I went too high the phone would start behaving strangely, not to mention start heating up too much for my liking. Some people have found the LiveOC works better on even number values, others found that multiples of five worked best, for me I think it was 113% however. I would find it interesting though if you could not hit at least get 110%. YMMV

Thank you for all the work stratosk, the devs for SGS are amazing and my phone is always like new. Well done!
[Captivate Android Development] grndnl:
123w

hat does "Implement both CM LED and CM BLN" mean?
[Captivate Android Development] prbassplayer:
That you can toggle between those services.

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] mik101:
Built in button backlight notifications are supported by default, and for those that wish to use features like blinking the backlight they can install the BLN app and enable its use through a setting in the Semaphore manager app. It works great. I personally use BLN.

Just a little overclocking update, my cappy is stable at 120%oc at default voltage, and can get a few benchmark runs in as high as 125% with much more voltage, but I've settled back on 120% a I can do it at stock voltage and it's 100% stable. It's interesting how quickly it "falls off a cliff" as far as stability and I now agree 100% with Stratosk limiting the Semaphore Manager to 120% overclock. It's not worth a few more points in benchmarks for increased power usage and potential heat/over volting issues. The 5% isn't enough to notice any difference in UI responsiveness, app loading, or anything like that anyway. (I'm not a big gamer either).

Many thanks to Stratosk as always. :)
[Captivate Android Development] grndnl:
I have checked that option and rebooted, then i downloaded the BLN app, however i do not get hte option to blink the LED. Can someone tell me what i'm doing wrong? I'm on the 4.2.1 SLimbean beta 2
[Captivate Android Development] Nick0703:
You need BLN Pro app for the blinking option. Regular version doesn't have it.
[Captivate Android Development] grndnl:
wow since when? that sucks!
[Captivate Android Development] Nick0703:
I believe it was always like that. But you could try downloading the app called Blinky from PlayStore. This one has the options for blinking.
[Captivate Android Development] M973:
also the app NoLED, has a lot of features
[Captivate Android Development] jdogg21:
Have the pro version cannot get app to work. Anyone else
[Captivate Android Development] swayjd:
Worked fantastic performance wise. But made me unable to install further nightlies (status 7 error)
[Captivate Android Development] andrewdroid:
Kernel has absolutely, wonderful performance. But I'll second the call to fix that Status 7 error that everyone's getting when they try to upgrade to the next Cm10 nightly.

Supposedly, the buildprop within the kernel has a wrong model number for our Captivate so the CM10 install script gets angry.
[Captivate Android Development] Bdev3:
Just had the status 7 error on upgrading to today's CM10 nightly. I had to flash another kernel first then CM10 and managed to slightly hose the phone in the process. Re-installing gaaps got me sorted out but not sure why that made a difference. Except for that, the kernel had been working great.
[Captivate Android Development] stratosk:
Could you please send me the /cache/recovery/last_log file and if possible the default.prop file of cm10 stock kernel?

Thanks in advance
[Captivate Android Development] Bdev3:
Sent you a PM with build.prop (think you meant this, can't find a default.prop), but my /cache directory is empty. Monfro suggests it could be that your script is identifying device as an I9000: http://xdaforums.com/showpost.php?p=30708677&postcount=210
[Captivate Android Development] stratosk:
Thanks for the file I will check it. Are you sure you don't have a default.prop file when you are in recovery?
[Captivate Android Development] Bdev3:
PM sent with file. I also found it with Astro (missed it there originally, sorry) and it's dated 07-31.
[Captivate Android Development] mik101:
The status 7 error is easily fixed by editing the update script in the nightly to remove the script assert lines. Youll want to remove everything before the show progress portion. It'll be about three lines and include the semicolon. That simply removes the device checks (so please know exactly what you're flashing if you do this). Then the update will install just fine.

The previous poster is correct: When you plug the captivate into the pc while in recovery it identifies itself as an i9000 (or maybe it was just galaxys? I forget, I'll check later), but if you do it when in cm10 it identifies itself as a i897 as expected.

I haven't had any instability what-so-ever. Running ondemand/noop@1200mhz all the time. Not using deep idle.
[Captivate Android Development] Bdev3:
Thanks for the tip on the update script. I found the lines on top of the file in \META-INF\com\google\android\updater-script in the nightly zip.
[Captivate Android Development] ninja_rancher:
Using 2.0.6c with the CM10 8/28 nightly, the video camera FCs when switching to it. I tried clearing the camera/gallery cache and data, but still had the same issue. If I use the stock kernel from CM10, I can switch to video and record correctly.
[Captivate Android Development] stratosk:
Please try to disable bigmem option in semaphore app.
[Captivate Android Development] ninja_rancher:
That, of course, did the trick. I guess I was under the impression from perhaps another kernel that bigmem was okay for video, but hugemem wasn't. Guess I'll just have to decide which is more important, video or RAM. Thanks.
[Captivate Android Development] Monfro:
Try to set video to 480 in camera app, instead of 720.

It should work then.
[Captivate Android Development] askpcguy:
Installing on miui jelly bean v2.9.7 and also bump to page 1.
[Captivate Android Development] fulii:
I cant install any rom after this kernel it says error in build prop
[Captivate Android Development] BitteredBro:
Flash devil kernel, reboot into recovery and then flash the new ROM
[Captivate Android Development] askpcguy:
As build.prop is in /system just reboot into Recovery and format/wipe System then reflash your rom. Don't think flashing a kernel would touch /system at all.
[Captivate Android Development] dongfangri:
New CM 10 ROM 0918 is out, would you please release the new kernel? Thanks.
[Captivate Android Development] prbassplayer:
What changed that requires new kernel?

Nevermind found out.
[Captivate Android Development] mundocapi:
The version on i9000 thread is 2.1.1.

There are any new semaphore for the cappy? I have checked at semaphore.gr also, but the latest version is 2.0.6.

Thanks.
[Captivate Android Development] grndnl:
does blinky drain battery life so much as people in the comments say on the play store?

Also if I may add, I don't understand why blinking LEDs are not a native option added to the kernel / ROMs using the kernel.
[Captivate Android Development] spacecase-25:
Can swap / ZRAM be added back in?
[Captivate Android Development] Nick0703:
Zram/Swap was never added. If you want those option, you'll have to compile the Kernel from the source and enable Swap/Zram in the kernel config file. That's what I did.
[Captivate Android Development] mik101:
It has and always worked fine if you have the correct kernel.

If you haven't enabled it in the semaphore manager app then no it won't work on 2.9.4+ as the default setup is CMLED and the BLN pro usage has to be enabled. You can also manually add the file to enable it without Semaphore manager. If instructions aren't in the op, search the i9000 thread or a couple pages back when Stratosk added 2.9.4c. I know I saw them somewhere.

Prior to that only specific versions support BLN. I believe 2.6.6 was the last for Android 4.1.2/CM10.
[Captivate Android Development] spacecase-25:
For real? I could have sworn it was in there. Hmmm, dare I compile?
[Captivate Android Development] Nick0703:
I could send you the ones that I compiled?
[Captivate Android Development] RashaMatt:
Just wondering why there is LiveOC support in this kernel, but not simple 1200MHz support?

My phone works great at 1200MHz straight, but LiveOC always kills it fast.
[Captivate Android Development] prbassplayer:
Because Stratosk doesn't add clock steps keeps the stock 5 steps. Most phones can live OC just needs some persuasion. The cappy I'm using for testing won't take any not par numbers and with +0.50mV it runs 120%just fine.

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] Kyuta Syuko:
Lucky. My phone seems to hate 120% LiveOC and throws a fit and reboots when I try to make it run at that :( Even tried tweaking the voltages to no avail :(
[Captivate Android Development] mik101:
Luck of the draw. Mine is stable at 120% liveoc at stock voltages. Then it quickly falls off a cliff, even with more voltage putting it past 122% is a challenge. I do wish we had combination overclocking, but it really does add another avenue for thing to go wrong as far as the kernel goes. My gfs i9000 throws a fit with liveoc too, but standard overclock with other kernels is fine. So obviously the issue lies with a part of the soc outside the cpu itself.
[Captivate Android Development] prbassplayer:
I had the courage to push voltage when I got a new daily phone. Else at stock voltage I was only able to achieve 114%. Also I just pushed +0.50mV to all 5 steps because I'm lazy might not need to. Like I said needs some coaxing in to it.

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] Kyuta Syuko:
Hmmm my phone seems to be working stably now with the same OV... Swear I tried +0.5 to all before... Might have not done the lowest lvl one though... Will continue to stress it with Stability Test to see if it reboots...

*edit*

Ran for over an hour with the classic CPU test but rebooted after a minute and thirty with the CPU/GPU test :|
[Captivate Android Development] spacecase-25:
Back and home keys are reversed with 2.9.5c. Could be the ROM (slim beta 2) but I noticed it after flashing the new kernel.
[Captivate Android Development] prbassplayer:
Shouldn't happen regardless. You sure it's the correct kernel/rom for your device?

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] Kyuta Syuko:
Where'd you get 2.9.5? On another note I've been using 2.9.4sc with no issues on Slimb Bean 4.2.1 Beta 2.
[Captivate Android Development] prbassplayer:
Actually that's it your using i9000 kernel not cappy. I forgot 2.9.5 wasn't released for our devices (been using for test builds myself).

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] spacecase-25:
I linked to the semaphore thread via the website so o may have ended up in the i9000 thread without noticing. It performs very well though!

---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------

If you wouldn't mind doing that when 2.9.5 is released I'd be grateful. I'm assuming Mac os isn't Linux enough to build on.
[Captivate Android Development] prbassplayer:
I can't tell you how, but it can be one on a mac (since it's Unix based). Can't be done on windows afaik

Sent from my Slim Bean Beta 2.x powered Nexus 4
[Captivate Android Development] spacecase-25:
I'll look into it. I assume it has something to do with musing macports
[Captivate Android Development] stratosk:
New version 2.9.5c

- Linux kernel 3.0.58

- fix to interactive from 3.4
[Captivate Android Development] Nick0703:
Alright, check ur pm!:)
[Captivate Android Development] lavero.burgos:
Hello dear dev. i wanted to ask if deep sleep is fully working because i have tried to use it with slim ROM beta 2 but my phone ends up turning off so i have to press vol+ plus power buttons to start the phone again.

I'm not sure if deep sleep depends of the ROM or kernel or both together, efharisto para poli

~ V

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

Can you pm it to me too to give it a try please ?

~ V
[Captivate Android Development] Nick0703:
Sure man! :)
[Captivate Android Development] stratosk:
Hello,

I guess you mean deep idle (it's different from deep sleep).

Many people reported issues with deep idle. The only solution is to leave it disabled.

Deep idle depends on kernel.

(parakalo :) )
[Captivate Android Development] shuyin1102:
I on 2.9.5c with the latest nightly and often got Charge of Death when charging the phone at night, i have no idea, here is the last kmsg
[Captivate Android Development] prbassplayer:
Re: [KERNEL] Semaphore JB 2.9.5c

Are you using Didle or OCing?

Sent from my Slim Bean powered Mako
[Captivate Android Development] shuyin1102:
Re: [KERNEL] Semaphore JB 2.9.5c

LiveOC 110%, smartass, sio, never use Didle, and im on i9000jvt bootloader
[Captivate Android Development] prbassplayer:
Re: [KERNEL] Semaphore JB 2.9.5c

Does it happen with no OC?

Sent from my Slim Bean powered Mako
[Captivate Android Development] shuyin1102:
Re: [KERNEL] Semaphore JB 2.9.5c

Im afraid of charging overnight because i need the alarm working :(
[Captivate Android Development] mik101:
But you obviously don't want to troubleshoot it. Prbassplayer asked you a question and you ignored it.

If deep idle is not enabled and you're not over clocking try bumping the voltages slightly. If that doesn't resolve your issue then you'll have to find a combination that works. I'd suggest staying away from hacked up ROMs period if stability is a must. Does CM10 or 10.1 behave the same way?

It's not a kernel problem (unless you're trying to use deep idle... It will never work correctly on some phones). Some of us haven't had to reboot in weeks and never get an SOD, so without more info we can't help you.
[Captivate Android Development] jdogg21:
Re: [KERNEL] Semaphore JB 2.9.5c

When I wake from screen off it scrolls SD card removed , reading SD card anyone else no other isuues phone is still responsive.Any Ideas?
[Captivate Android Development] Nick0703:
Re: [KERNEL] Semaphore JB 2.9.5c

Check if your SD card is fully inserted in the slot? Maybe it came off slightly??
[Captivate Android Development] cnu4u:
Where is the new version (2.9.7) for cappy??
[Captivate Android Development] Kyuta Syuko:
Probably in the works/being ported over.
[Captivate Android Development] shuyin1102:
Re: [KERNEL] Semaphore JB 2.9.5c

I never had this before until update to v 2.9.x, so i thjnk thats the kernel issue. Will try not OC if i have a chance
[Captivate Android Development] prbassplayer:
Re: [KERNEL] Semaphore JB 2.9.5c

You are the one and only complaint for it. Although you did provide a log for it, I commend you for that, it's easier to to see if it's OC or Didle by troubleshooting from your side. I don't remember what the log said specifically but it did show some errors. Also what rom you using?

If I remember when I looked aye git the changes only required to recompile the kernel. However Stratosk usually releases it for i9000 for a while to make sure nothing up before releasing to other 2 devices. At least what I think.
[Captivate Android Development] shuyin1102:
CM 17-01 nightly build sir, i got CoD on Captivating 7.x ROM too, all with Semaphore v 2.9.x thats why i post the log here
[Captivate Android Development] Kyuta Syuko:
Well if a recompile is all it takes then it makes sense to test it out on the "home" device for a while to make sure there aren't any serious bugs and then to compile it for the other devices. Thought there were some modifications to code that needed to be done, but I don't really know much about porting/compiling kernels...
[Captivate Android Development] prbassplayer:
Re: [KERNEL] Semaphore JB 2.9.5c

Well in semaphores case as long as the device Config file and device ramdisk folder doesn't change doesn't need much porting. Else you need to make the changes made to i9000 specific files to other device counter part. Usually not hard, time consuming at times though.

Sent from my Slim Bean powered Mako
[Captivate Android Development] laughingT:
Re: [KERNEL] Semaphore JB 2.9.5c

ditto. +1

Sent from my SGH-I897