yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mkr14:
I spent a lot of time dicking around to finally figure out a working combo. It sucks that this option isnt better supported but oh well.

Please note I was on a JB rom when this happened so not sure if it was the EU bug. Similar situation. No EU popup but the internal SD just went kaput. No access. Same cant mount issue you have. Maybe hardware failure.

I tried everyway to flash a stock rom and no dice. Oneclicks both Odin and Heimdall. PIT file with Tars. ETC. NO GO Always same error. Recovery cannot access it.

Your internal SD card is gone so forget about it. (unless someone figures it out) You now need to use your external SD card as internal.

I was able to fix it using the EU workaround. You need to get a recovery that has Partition SD card support under Advanced. I use the latest Semaphore for ICS, 1.2.6. Partition your SD card using this feature of older CWM. I recommend a 2GB or greater partition for data and no swap. You will end up with a 2GB+ partition for data and the rest will mount as sdcard. Once you finish that, try to install the latest Slim JB zip. It will give you a partition not compatible error. Flash again and it will flash Semaphore JB kernel and reboot. You might need to manually enter recovery. Install the ROM zip(I use slim, quick and painless) like you would normally with all the other zips. You can use any ROM as long as you use the Semaphore JB kernel from my experience. Devil would not accept the partitioning and neither would stock AOKP/CM. They always boot into recovery. You will need to edit the updater_script in meta-inf to get some ROMS to install in Semaphore so you might have luck using another kernel to install then installing the Semaphore kernel right after install or you can just edit the file. Not all of the kernels liked to play nice with this partition setup but I recall getting most of them to at least install a rom even though they wouldnt boot.

To get access to your SD card in Android. Flash this EMMC reverse fix zip provided by Jolufa after you install the rom. It does the vold.fstab change for you switching the mount of your external and internal SD card.

EMMCreversefix.zip can be downloaded here: http://xdaforums.com/showpost.php?p=32872147&postcount=923

Here is the thread for the EU bug: http://xdaforums.com/showthread.php?t=1447303

Should be good!
[Captivate Android Development] vbenkovskyy:
Copying/moving files on memory card via PC is very slow. (Latest version installed; MIUI rom)
[Captivate Android Development] uhm:
Hello Stratosk,

I tried to use slimbean rom but the screen becomes heavily tinted with blue color. I read somewhere that this problem is related to using Nexus S Framebuffer. I was wondering if you would consider providing a version/option to use stock framebuffer? I just hope that this is not an unreasonable request. If it is then I'm so sorry!

Thanks a lot in advance!
[Captivate Android Development] prbassplayer:
First part Stock kernel is exactly the same as 2.5. And I've used this kernel as well and not suffer that problem. Something else is causing it.
[Captivate Android Development] nedthehead:
Is there a version of this kernel that comes with Voodoo Colour? If there is, I haven't been able to find any information regarding it
[Captivate Android Development] uhm:
Not all phones are affected. All kernels that are based on pawitip's Nexus S framebuffer implementation have this problem e.g. semaphore, devil etc. The factory color calibration data(it is unique for each phone) in some cases is not compatible with this Nexus S framebuffer implementation and that's why only some phones encounter color related problems. Therefore I requested for the stock framebuffer version.
[Captivate Android Development] prbassplayer:
Sorry my kernel knowledge is limited however this is the first I hear from this. Can't you correct this with cmc?
[Captivate Android Development] shuyin1102:
All ICS JB kernels are based on Nexus S drivers, so we cannot ask for the perfect things for our device, like the lack of speaker volumn (compare to stock sammy roms), the noise suppression function... etc. Just accept it and shouldnt ask for ETAs :p
[Captivate Android Development] droyd666:
I'm on CM10 stable and i'm wondering if its possible to change live OC to 120% without the phone auto rebooting over and over again. If anyone has managed to do it, what are your settings?
[Captivate Android Development] mik101:
I'm 100% stable @120% live oc and I'm not doing anything special. Default voltages with semaphore 2.5.0sc on my i896 (rogers bootloader). My phone is also stable with deep idle enabled. It's really the luck of the draw. My girlfriends i9000 will not overclock at all at default voltages (and she doesn't want me to up it, so I haven't pressed the issue lol).
[Captivate Android Development] prbassplayer:
Each device is different. Usually 114% is stable on most devices with normal voltage. I suggest you start from there then go up 1% and test. When you hit unstable clock bump up the voltage to see if it stable again. Fine tune it until you find the max clock your bus & SoC can handle.
[Captivate Android Development] stratosk:
New version 2.6.1c

- Linux 3.0.52

- Reworked part of code of Semaphore Auto brightness driver

- touchwake fix

- improved kernel installation procedure (version checking)

- fix update of logger.ko module when installing new kernel version (thanks to DerTeufel)

- upstream sync with CM10 kernel

- CWM: update to 6.0.1.9

- CWM: enable Semaphore Auto Brightness driver (write /system/.disable_autobr to disable it)

- CWM: AROMA FM: Holo Dark theme by sUsH667 (thanks a lot)

- CWM: fix menu item 'backup to external/internal'
[Captivate Android Development] jdogg21:
Help,which version should I flash for Remics Over 3.01 on captivate ,any help would be appreciated
[Captivate Android Development] Nick0703:
Just flash the normal version. The "Semaphore_JB_2.6.1c..." version.
[Captivate Android Development] mik101:
2.6.1sc working perfectly here as always (Nov 26 CM10 nightly).
[Captivate Android Development] shuyin1102:
I flash the 2.6.1 version and the incall volume hack doesnot work for me, anyone experience that? Im on slim 3.0
[Captivate Android Development] mrsubway:
Still the baddest kernel around! 2.6.1sc=butter! :D

Sent from a heavily modded Cappy from parts unknown. Slimbean/Semaphore. FTW.
[Captivate Android Development] mindphaser2k9:
Me too. It is a known issue. Hope Stratos will kindly fix it someday, when he have some time. At least this is my biggest wish for now.

Other things are just great.

For me, the new kernel 2.6.1 is significantly smoother even than was 2.5.0.

Thanks for the great work, Stratos! :good:
[Captivate Android Development] kevinseto:
latest version working great with CM10 :D
[Captivate Android Development] Darkangels6sic6:
Amazing. Flashed sc with bigmem patch. 391Mb or ram, 720p, and great stability. Devil was fun, but just not as stable for me. You can actually see better and better performance with every semaphore.
[Captivate Android Development] Primus76:
Howdy. Installed semaphore 2.6.1c in hopes to fix the bluetooth connectivity issue I am having with CM10. Turns out that I am still dropping connection even after I am connected for 5-10 minutes. The time I stay connected varies so I haven't been able to narrow it down. I enabled the logger option in the semaphore manager app and restarted. Where do I see the logs? I have a few logcat viewers but they only display the log events from the time they are started and not the historical logs that I think the semaphore option has?

Any idea where they are located so I can take them offline for review?

Thanks
[Captivate Android Development] sephhi:
I use your kernels religiously. There are 2 good 4.2 roms out for the Cappy now. Any plans on doing a kernel compatible with the new update?
[Captivate Android Development] stratosk:
They are produced through a system device.

You can get them with 'logcat' command in a terminal emulator or 'adb logcat' if you have adb installed in your PC.

Yes, in my plans a version for 4.2
[Captivate Android Development] drewbag:
Hi,

Did version 2.6.1sc break youtube for anyone else? I'm on slim rom 3.0
[Captivate Android Development] prbassplayer:
Shouldn't as I compile with same source. Verifying

Edit: Just flashed Stratos kernel on 3.0.x and workes just fine. I doubt it would have been different on 3.0 as hardware/samsug/exynos3 hasn't changed.
[Captivate Android Development] drewbag:
Thank you I cleared cache and reflashed and now it's working perfectly.
[Captivate Android Development] kevria:
I am using that same combo and the youtube app works fine for me.
[Captivate Android Development] geek1st:
waiting for the 4.2 kernel update
[Captivate Android Development] prbassplayer:
It just came out for I9000 and you want it out now? :p chill out give Stratos time.
[Captivate Android Development] onlyu132:
I already flashed 4.2 semaphore kernel for i9000 on my cappy and happy to say it works just fine :D. I can feel my phone running much smoother and responsive now. I'm using latest hellybean btw and still testing. Great work!
[Captivate Android Development] mindphaser2k9:
But Home and Back buttons exchanged and orientation sensor works incorrectly, right?
[Captivate Android Development] onlyu132:
Confirmed. I already disable auto rotation.
[Captivate Android Development] cas0404:
hi stratosk,

Please before leave jelly beam 4.1.2 can you update your kernel to 2.6.2c like the galaxy s, to have linux 3.0.53 and touchwake issues fix. =D

Thx
[Captivate Android Development] mik101:
Does anyone else find the Aroma file manager REALLY touchy after updating from 2.6.0sc to 2.6.1sc? I can't scroll without selecting things, where-as it worked great before the dark theme was integrated. I switched to the other theme to see if it would make a difference, but it didn't.

Edit:

External SD card wont mount under CWM either.

Sideloading gives me a protocol error?

Had to mount the internal sd to the PC to load a rom to reflash after I broke it. Oops. Lol.

This is on 2.6.1sc

Works great other than those hiccups.
[Captivate Android Development] zingzing09:
thanks you very much i'm find it
[Captivate Android Development] jerkysh:
are we gonna get the 2.6.5 kernel for the cappy?:)
[Captivate Android Development] stratosk:
New version 2.6.5c

- Linux kernel 3.0.55

- CM LED notification (dropped BLN)

- build with Linaro 4.7.3 201211

- Fix logger loading issue when update kernel

- enable tracing

- enable O3 on GPU driver (thanks DerTeufel for idea)

- CWM: upstream sync
[Captivate Android Development] Wakamatsu:
2.6.5sc fixed an issue I was having connecting to VPNs in 2.6.1. :victory:
[Captivate Android Development] m1batt1:
Is this 4.2 compatible?
[Captivate Android Development] prbassplayer:
No. 4.2 kernel is 2.8.0 betas that aren't released yet. I've been compiling (poorly) for testing on Slim 4.2 :)
[Captivate Android Development] mik101:
Edit: I see the I9000 has both 2.6.5 wth CMLED and 2.6.6 with BLN readded, so I'll be patient. :)
[Captivate Android Development] TorqueWrench001:
Internal SDCARD

I am using Salty Bean v31 on my captivate and I am unable to mount my pc to the internal sdcard when in recovery. When I am booted up into the ROM I can mount the internal card but unless I am mistaken i believe it looks at the internal card as an external card. I also get the same results when using the Devil kernel, however I extracted the kernel from AOKP JB Milestone 1 and I can mount the sdcard fine with my pc. I do not have an external sdcard in this phone. I have searched the thread and not found an answer., or this issue discussed. My apologies if there is a simple answer that I have overlooked. Any insight is appreciated. Using Semaphore 2.6.5c

Thank you,

Sean
[Captivate Android Development] prbassplayer:
Not sure but I bet the rom isn't following CM's sd card naming?

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] TorqueWrench001:
I thought of that also, gonna look at it further, vold files I think. Thanks. made me think some more.
[Captivate Android Development] donclary:
2.6.5sc Problem with WiFi?

I am running AOKP JB Milestone 1 on my cappy, with the bigmem patched libraries (bigmem not checked in Semaphore Manager), and Semaphore JB 2.6.1sc. I have tried to upgraded to 2.6.5sc, but run into an issue where the setup screen showing my configured WiFi connections shows the message "Turning Wi-Fi on". The ON/OFF toggle is in the OFF position and will not respond.

I reflashed the 2.6.5sc package, thinking it was a bad flash, but no change. I flash back to 2.6.1sc and WiFi works correctly.

Is anyone else seeing this behaviour? (I tried looking at the log with CatLog, but it just sits and never displays any messages, even though it gets root.)
[Captivate Android Development] r_scotter:
I ran into the same problem with the same rom (AOKP milestone 1). Lost my wifi when I flashed 6.5 but I didn't really have time to troubleshoot so I flashed back to 6.1. From the sound of it, could be the rom isn't playing nice with the new update. If I get a chance today I'll restore a backup of AOCP 4.6 and I'll upgrade the kernel to see if it's okay with that rom.
[Captivate Android Development] Felipaoo:
Hi there,

I flashed a couple of days ago for the first time CM10 official stable rom for this device but the kernel used was boog KJ3 kernel 3 with Odin.

Works pretty well, but I noticed the device to be running out of battery quicker. Also, when I turn on the phone, It starts with more or less 140MB of available RAM, running Facebook and Whatsapp in the background, while I read here this RAM provides much more available memory.

So, first question, will I be able to flash this rom from odin again as I did with the previous one, but without flashing the ROM again? Should I check something before?

And do you guys think I will notice any difference in performance, battery life or anything?

Thanks in advance! Sorry for the newbie questions here..
[Captivate Android Development] r_scotter:
Ran into the same problem when I flashed 2.6.5sc over AoCP 4.6 (which already had the bigmem patch). Lost my wifi and I couldn't get it to switch on. So for now I've restored backups that have 2.6.1sc with the bigmem patch and wifi is fine. I also tried to flash the bigmem patch along with the kernel and I got the same result.
[Captivate Android Development] gado45:
2.6.5c break my wi fi on aokp milestone 1, flashed again the modem but still wi fi is dead

Enviado desde mi SGH-I897 usando Tapatalk 2
[Captivate Android Development] stratosk:
WiFi is not gonna work on older ROMs that are trying to support WiFi direct.
[Captivate Android Development] BWolf56:
Not sure what you mean by older ROMs, AOKP jb milestone 1 is 4.1 based and a couple months old?

EDIT:

Lol good point, thanks for the clarification ^^
[Captivate Android Development] prbassplayer:
Old :p. Compare github and you see the difference. I believe that change happened about the time Slim 2.8 came out (on or about don't remember).

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] donclary:
Thanks stratosk! I guess that I will be sticking with 2.6.1, for now.
[Captivate Android Development] stratosk:
New version 2.8.0c

- Linux kernel 3.0.55

- upstream sync (thanks to pawitp)

- dropped incall volume settings

- enable O3 in GPU driver (thanks DerTeufel for idea)

- CWM: update to 6.0.2.0

- CWM: fix usb mounting internal SD

This version works on JB 4.2
[Captivate Android Development] vbenkovskyy:
Anyone have problems with USB storage mode ?
[Captivate Android Development] jdogg21:
Help which version do I use?

Any help would be appreciated!
[Captivate Android Development] mindphaser2k9:
2.6.1c :D
[Captivate Android Development] sephhi:
Getting random reboots on pawitp's aosp rom. I'll try to get a log.
[Captivate Android Development] prbassplayer:
You sure you aren't messing with Didle and/or voltage? Seems to be working fine on my device, I admit not for to long.

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] sephhi:
I did turn didle on. I'll try with it off. I'm on I9000 bootloaders so I've never had problems with didle but you never know.
[Captivate Android Development] mindphaser2k9:
Thank you very much for your great work, I was waiting for this new kernel with 4.2 support.

Does "dropped incall volume settings" mean that in-call volume boost will not be supported anymore?
[Captivate Android Development] mik101:
Guess I'm the only one that was hoping for 2.6.6sc ? Everything is perfect for me on 2.6.5 other than lacking BLN.

I don't want to jump to pawtips 4.2 test builds yet. Seems to be some instabilities in that one.

Note: I haven't tried USB mass storage mode or purchases which people seem to be reporting issues with.

Cheers guys.
[Captivate Android Development] stratosk:
Yes, most probably will not be supported. They cause too much distortion (IMHO).

Please find 2.6.6 (BLN instead of CM led implemented) attached.
[Captivate Android Development] mik101:
Thank you so much stratosk. Sorry for being a bother. I just miss being able to flash the LED and time them out with BLN. I wish I could afford to donate something towards your future N4. Hopefully once the Christmas season clears up a little.

Edit: Anyone else getting a liblights doesn't support bln warning from the BLN app (and then BLN is shown as not working in the app)?
[Captivate Android Development] Nick0703:
Yeah I got the same problem with 2.6.6sc about the liblights. But I'm using 2.8.0sc now.
[Captivate Android Development] stratosk:
If someone can test, please unzip and then push the light.aries.so to /system/lib/hw/

Please let me know if this resolves the issue with BLN.
[Captivate Android Development] jerkysh:
2.8.0 works with 4.1.2?
[Captivate Android Development] stratosk:
No, it doesn't.
[Captivate Android Development] Thunder22:
I'm using helly bean with 2.6.1, I also have a broken internal SD which this kernel works, but will 2.8.0 work with broken SD also?
[Captivate Android Development] jdogg21:
Stratosk which version to flash I have 4.1.2 based RemICS-JB v3.0.1tried flashing 2.6.6c but won't get passed boot screen flashed 2.6.6 sc everything works but WIFI? Any help would be appreciated.
[Captivate Android Development] Nick0703:
About the WiFi, Stratosk posted a post a few pages back explaining why WiFi is broken.

"WiFi is not gonna work on older ROMs that are trying to support WiFi direct."

Maybe that's why WiFi is not working for you.
[Captivate Android Development] mik101:
That works great. Thanks stratosk!
[Captivate Android Development] BitteredBro:
Hi. Some questions popped on my mind:

It's Smooth UI redundant on JB 4.2? I read that 4.2 came with something along that way included.

It's that feature kernel dependant?

when I change kernel to semaphore is Smooth UI needed to get the same behaviour?

I didn't use Smooth UI on previous version because I think it affects battery life. If that's true, then inherently 4.2 lose battery in a way that can't be avoided?

Oh! And 2.8 it's working great on the Pre-nightly:thumbup:
[Captivate Android Development] quocthanhjs:
hi bro, I use semaphore kernel 2.8.0c on rom 4.2.1 crashes on screen semaphore, if normal using kernel pawitp,.(Internal card machine broken my captive, I use the sd card) sorry my bad English
[Captivate Android Development] HoangTuBot:
First of all try to say exactly the name of your ROM which you're using, because 4.2.1 is so general.

Second, what you mean "crashes"? Hanging semaphore splash screen forever?
[Captivate Android Development] quocthanhjs:
Yes, all rom 4.2.1 crashes on semaphore 2.8.0 kernel, and semaphore screen hanging forever, the button can not be used to enter recovery, I must be up to the semaphore 2.6.5 kernel on the bootloader, to up kernel pawitp in recovery, the device will run.
[Captivate Android Development] acras:
Bigmem option in 2.8.0c breaks 720p recording for me. I'm on cm10.1 nightly.
[Captivate Android Development] stratosk:
This is normal. More memory but breaks 720p
[Captivate Android Development] acras:
But before on cm10 with devil kernel and your kernel it was ok as i remember.
[Captivate Android Development] Nick0703:
Maybe it's because you had the bigmem patch that's why it was working? Like me I use the "sc" version with bigmem patch and 720p recording works. But I don't enable the bigmem option in Semaphore Manager because the "sc" comes with 391 Mb which is OK for me. But if you enable bigmem option in Semaphore Manager then 720p will be broken even with the patch.
[Captivate Android Development] acras:
Which patch do you use?
[Captivate Android Development] prbassplayer:
There's a difference between big mem (toggle on semaphore app) and hugemem (s). Huge mem is a kernel and rom mod. You need a patch if the rom doesn't include it. Else it breaks a whole list of things like 720 recording and then playback. Bigmem always breaks 720 recording.

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] mik101:
Search through the semaphore kernel thread for the i9000 and you'll find it.

I'm assuming those libraries haven't changed on 4.2? (Question for those already running 2.8.0sc or greater)
[Captivate Android Development] Nick0703:
Nope. It's still that same.
[Captivate Android Development] jdogg21:
Anyone that can help,I know it seems old but which version of 2.6.1 c or sc Thanks in advance
[Captivate Android Development] Nick0703:
Use the "sc" version of 2.6.1. But 2.6.1 is an old version. The latest ones are 2.6.5 (CM Led Notification) or 2.6.6 (BLN Notification). 2.6.5 and 2.6.6 are the same except one has CM Led Notification and the other one has BLN Notification.
[Captivate Android Development] jdogg21:
2.6.6 doesn't support WiFi correct?
[Captivate Android Development] sephhi:
zRam support? 2.8.0c
[Captivate Android Development] mindphaser2k9:
Fortunately, no.
[Captivate Android Development] quocthanhjs:
Who have helped me, THANKS
[Captivate Android Development] jerkysh:
when will we get the 2.8.3 kernel? :)
[Captivate Android Development] BWolf56:
Asking for ETAs is sorta taboo. Be patient guys ;)
[Captivate Android Development] demoicurn:
I've read about others getting booted off xda for that very question. I appreciate all the devs here. I read about how to theme and rom development. Then I took 2 tylenol. Wow. Y'all rock.
[Captivate Android Development] shangxiaole:
I got the issue too. Can not boot with 2.8.0 sc

BTW, my internal sdcard is dead. I use external SD instead..
[Captivate Android Development] stratosk:
New version 2.8.3c

- Linux kernel 3.0.57

- CWM 6.0.2.3

- upstream sync
[Captivate Android Development] noone.dk01:
how to wake my phone up went it's deep idle?
[Captivate Android Development] prbassplayer:
Reboot if it dies with dildle and disable ;)

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] noone.dk01:
so what is purpose of deep idle feature?

i think it help save energy but.... :laugh:
[Captivate Android Development] prbassplayer:
Helps to save juice while listening to music. But doesn't work on all devices.

Sent from my SlimBean 4.2 Alpha powered Captivate
[Captivate Android Development] stratosk:
Merry Christmas everybody! :)
[Captivate Android Development] noone.dk01:
Merry Christmas! in my hometown, Christmas isn't holiday

so sad
[Captivate Android Development] stratosk:
New version 2.9.0c

- WiFi driver: couple of fixes from google source code

- Interactive governor: all latest changes from google source (3.4 kernel)

- Implemented ROW IO v4 scheduler (module)

- Reduce number of frame buffers for more RAM (thanks to DerTeufel). Available RAM - normal version: 384MB - 396MB, 's' version: 397MB - 409MB

- CWM: update to 6.0.2.7

- build with Linaro 4.7.3 201212
[Captivate Android Development] Darkangels6sic6:
Where is 2.6.6?