yashsingh1/xdaforums huggingface dataset:
[Off-topic] ak700:
Also the OT Image Editing thread works great for this stuff
[Off-topic] 9breaker:
i tried to embed it but it wouldn't work so i just put a link. ill use that image editing thread next time
[Galaxy S II Q&A, Help & Troubleshooting] Eluc:
Hello,

I've got a huge issue with my GS2 this morning. When I woke up I've seen a warning about the SD card ("card empty or with an unknow file system" something like that if I translate from French). So I've no more access to the SD card from the phone, I'll test asap to read the card externally (I need a card reader...). But it was just the beginning, then there was an update for Titanium Backup and now it's no more working, couldn't get the SU right any more, but Super SU is still here and working. Then I shut off the phone, remove the SD card, replace it, reboot and the time/date was reset to 1.00 2000 (or something like that) inducing an error with Whatsapp. Plus within Go Launcher a lot of app went out of there folder, now I've 2 screen of unclassed app that were in different folder until yesterday.... And finally when I press power or home button to wake up the device it take like 1 full second or more to get the screen on sometimes.

This is very strange... I mean, it could only be related, no ?

Any clue of what went wrong and where to start looking for a clue ? (before the big formatting and re-installation, probably of a custom rom this time).

Config.:

Rooted Galaxy S2 I-9000 with stock rom 4.0.3

I use a lot of app but major one are Go Launcher, Titanium Backup (update recently), SuperSU, Lama, Droidwall, DoubleTwist (update recently).

Thanks in advance for any help

EDIT: Happen to be only an SD problem. It's readable in my computer (I've backed up what was not made already by Titanium or so) but not any more in the phone. This SD is a quite new one (2-3 months) with 32GB. However my older one (the 8GB included with the phone) is still working great.

The icon problem is related to the fact that app transfered on SD card was removed from Go Launcher then when it can read the card again (for 1 or 2 min) it adds all the app outside of these folder (bug feature from Go Launcher).

Finally Titanium root access was not really related I guess... I had to restart the phone to get a new prompt for root access then It was OK.
[Sony Xperia Miro, Tipo (Dual), J, E] Manneman32:
Hi guys!

I upgraded my sons Xperia J this morning. It´s unrooted and he wants it that way. However, after the 4.1.2 upgrade the statusbar shows battery percent. He gets really annoyed from this... but how can he "untick" it to not showing at all... just the batteryicon.

// Manne
[Sony Xperia Miro, Tipo (Dual), J, E] gavster26:
Quite simply you can't. or downgrade back to ics
[Sony Xperia Miro, Tipo (Dual), J, E] Manneman32:
I was afraid of that... Any easy guide to downgrade to ICS? The batterydrain is just tooo much

// Manne
[Sony Xperia Miro, Tipo (Dual), J, E] 2010matej:
Yes you can,but you must to found this option in framework files... It's hard,but one day,someone will find it ;)

And why you don't like battery percent? I was always downloading Battery HD to see my battery precent,now I like this in status bar very much!
[Sony Xperia Miro, Tipo (Dual), J, E] tasosl:
OF caurse you can..us i understand you want to remove the % icon battery of status bar!!use this UI learn at the comments how to port http://xdaforums.com/showthread.php?t=1762162 you can change and other setting there like make bar transparent..just you have to port it set right permission(of caurse you must have a back up of this systemUI.apk file) and reboot..give it some time for first time run!!no reason to downgrade the jelly bean!!;)
[Sony Xperia Miro, Tipo (Dual), J, E] Manneman32:
Sv: Battery percent after 4.1.2 upgrade

Still... he's on a non-unlockable bootloader and hence unrooted...
[Networking] hikhoa:
thanks everybody!

I have download Special... v1.2

I run on T-mobile very well.

But signal of my network where it gone .

No signal.

i use my Net work Mobifone in Viet Nam GSm 900

So how i can for my device run as well as first time in USA.

Please help me soon.

Best regads,

Khoa D.D.

My radio version 4.2 ( i had download RUS of O2 on T-Mobile )

T-mobile have Radio ver 6.2 . Does it have any problem.
[HTC Droid DNA] minjiet:
can anyone help yo create the sense 5 font in flash zip for venom?

thanks
[HTC Droid DNA] v-b-n:
Here u go -> http://vps.rana.sg/fonts/Font_Sense5_Stock.zip
[Captivate Android Development] ts1506:
This kernel is based on Semaphore Kernel by stratosk with a few changes I felt to be missing in semaphore.

This kernel combines the speed and stability of semaphore along with few additions for the best combination.

It is compatible with all JB 4.3 ROMs based on official CM10.2 layout.

Kernel versions 2.9.0 and lower are compatible with JB 4.2.x.

Differences with Semaphore

General Features

Thanks to

Stratosk for his source and all his help

Fishears for some of his code

kasper_h for some of his code

derteufel1980 for some of his code

Atomixxx and didhiy (for bootlogo)

Nick0703 for normal OC code

Christopher83 for toolchain

Franco's Dev Team [ malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres ]

All people on stratosk's list

All people who have inspired me , supported me and stood by me

Changelog of latest version

1. Updated Linux Kernel v3.0.99

2. Updated Ramdisk for 4.3 support

3. Lazy Cache Flushing on non-mapped pages

4. Yaffs Filesystem patches.

5. Bigmem patch updated for 4.3

6. FUSE FS now compiled into kernel

7. SIOPlus tweaks

8. Lagfree tweaks

9. Block update (recursively merge requests)

10. Dynamic management of Dirty Page Writebacks (thanks christopher83)

11. Tons of patches to ION

12. Build Logger into kernel

13. Using Latest 2013/09 Toolchain

14. Disabled In-Call Volume Control

15. Lots of other patches (see source for info)

Point to note

Ticking BigMem will break 720p recording

To control modules , please use script in SGS thread, and rest via NSTools.

All bug report of this kernel must be posted in this thread , with a clear description of the error , its reproducability , your ROM , any custom settings etc.

Please use it at your own risk! I am not responsible for any damage that may occur to your device.

Please note that I personally dont have a Captivate , I use the i9000, so that means , you tell me the bugs and issues.

Sources

CyanCore Kernel - Click Here

Semaphore Kernel - Click Here

ICS-Ramdisk - Click Here

Other versions

1. Galaxy S i9000 - Thread Link

2. Vibrant - Thread Link
[Captivate Android Development] aliver.dun:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.5

very nice thanks for your hard work
[Captivate Android Development] Darkangels6sic6:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.5

Cool. So have you yourself been able to reach 130% or seen it done by anyone?
[Captivate Android Development] noone.dk01:
good news :D

thanks man for your work
[Captivate Android Development] ts1506:
130% is the limit set in the kernel. I personally cant go above 114% and be stable , but I know a guy in i9000 forum whose phone is stable at 128% (with a few voltage changes).

I have benchmarked my i9000 with 130% OC(faced over 10 reboots before a successful benchmark) but it results in 6k + scores in antutu.

Without OC , it is about 4.4k , and with 114% , it varies from 4.9 to 5.3k with a peak score of 5433
[Captivate Android Development] Val D.:
Thank you very much for sharing this kernel! I have tried it and it shows good potential but I see a problem on my phone: I'm getting about 1sec black screen every time I dial a number, check e-mail, open maps etc... looks like on every app with screen refresh. Currently running unmodified SlimBean 4.2.1 stable. After flashing your kernel I did cache/dalvik clear + semaphore manager settings default. The only custom setting I have is 0.5X animations/transitions in developer options.
[Captivate Android Development] aliver.dun:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.5

can you a rom for captivate.if that it will be famous and popular....
[Captivate Android Development] ts1506:
Please dont flash the 1.7 version , I messed something up. It wont boot up , and you will have to flash back to GB using Odin then.

I am making a fixed version now. Please wait for it.
[Captivate Android Development] Thunder22:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.7

I was able to flash semaphore kernel in Odin fixed it.
[Captivate Android Development] ts1506:
Cheers , fixed version of 1.7 uploaded and added to OP
[Captivate Android Development] Yuna:
Sorry, but i see only 1.5s version...?

Edit:

Also swap enabled, but not used?

C:\Users\Yuna\Desktop>adb shell free

total used free shared buffers

Mem: 407364 332292 75072 0 2696

-/+ buffers: 329596 77768

Swap: 0 0 0

Edit2: Don't see zram module in semaphore manager. Why trying to manualy enable it:

shell@android:/system/lib/modules # insmod zram.ko

insmod zram.ko

insmod: init_module 'zram.ko' failed (No such file or directory)
[Captivate Android Development] ts1506:
It is clearly written that ZRAM is enabled from Settings->Performance->Memory.

For SWAP to work , you need to partition your SD card and run swapon with that memory block .

I removed the 1.7 version cause WiFi wasnt working for some reason.
[Captivate Android Development] Yuna:
In settings i have zram enabled, but dont see it in /dev/block/zram0.
[Captivate Android Development] mindphaser2k9:
I confirm that ZRAM seems doesn't work neither if enabled in Settings->Performance->Memory, nor with the script below:

#!/system/bin/sh
echo $((70 * 1024 * 1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0

Command "free" in a terminal shows zeros.
[Captivate Android Development] Yuna:
But if me manualy insmod lzo_compress.ko lzo_decompress.ko e.g dependencies for zram.ko, then insmod zram.ko will load and /dev/block/zram0 will appear. so we need init.d script to handle this... again... I just wanted to use GUI for enabling zram...

Edit:

As temporary solution i am using this init.d script, and calling it 91zram.

#!/system/bin/sh

insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/zram.ko

echo $((70 * 1024 * 1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
[Captivate Android Development] ts1506:
CyanCore 1.8 uploaded , fixed Wifi issues. Full changelog in OP
[Captivate Android Development] sephhi:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.8

Nice to see more i9000 devs here. Thanks for the kernel.
[Captivate Android Development] ts1506:
Re: [JB 4.2][Kernel] CyanCore-cappy v1.8

The main issue an i9000 dev faces is that he / she can't test their works before releasing.
[Captivate Android Development] mindphaser2k9:
Hi ts1506, thank you for the update and for your hard work! Can't wait for a normal OC ( upto 1400MHz ), that would be very cool.
[Captivate Android Development] ts1506:
I found the cause of ZRAM not working when enabled using the settings menu.

I will try to put out a new version soon with ZRAM fixed.

The sources are already fixed, so you can try to compile it yourself too.
[Captivate Android Development] Yuna:
Cool!

> I found the cause of ZRAM not working when enabled using the settings menu.

And what was the reason? ;)
[Captivate Android Development] ts1506:
Re: [JB 4.2][Kernel] CyanCore-cappy v2.1

Check my repo and search for Fix ZRAM commit.
[Captivate Android Development] Yuna:
Lol, m -> y? Serously?
[Captivate Android Development] cannondaleV2000:
Re: [JB 4.2][Kernel] CyanCore-cappy v2.1

Zram not working on vibrant eather
[Captivate Android Development] Yuna:
When can we expect zram-fixed build to be uploaded?
[Captivate Android Development] ts1506:
Re: [JB 4.2][Kernel] CyanCore-cappy v2.1

Today or tomorrow. My net is damn slow due to some underwater cable which got cut, disrupting internet in my country.

Sent from my cyanogenized tab 10.1
[Captivate Android Development] Thunder22:
Re: [JB 4.2][Kernel] CyanCore-cappy v2.3

Thank you for the update. Love this kernel. Also in your threads people asked about TWRP bit have you looked at cwm touch like devil kernel, its pretty sweet. Food for thought. Keep up the great work.
[Captivate Android Development] ts1506:
CyanCore 2.3 uploaded and attached to OP.

Linux Kernel updated to 3.0.71, read ahead fixes.

Some memory leaks and binder fixes quickly snagged from Devil kernel (@DerTeufel -thanks).

Full changelog in OP
[Captivate Android Development] Kyuta Syuko:
Nice to see more devs working to keep the Captivate alive. Once you get step OC working I'm going to be giving this kernel a try.
[Captivate Android Development] mindphaser2k9:
Me too, waiting for OC, since my CPU doesn't support big LiveOC...
[Captivate Android Development] Yuna:
Yhere is still something wrong with zram

type free in terminal and swap is 0 suze, used 0, free 0.
[Captivate Android Development] They Drew First Blood:
RE: zram

Forgive my ignorance, but is this a kernel-related or ROM-related issue? The modules do exist but have not yet been loaded (inserted)... are they supposed to be inserted by the kernel or rom? Hmm on second thought, zram issue is confirmed across multiple ROMs so I guess I have answered my own question. In any case, thank you for providing another kernel for us to flash.
[Captivate Android Development] Yuna:
Now the modules are inserted, but if i use the zRam script - my phone goes to reboot...
[Captivate Android Development] Val D.:
I've noticed recently that my Captivate runs MUCH faster and smoother with zRam disabled.

Looks like loading our single-core CPU on every RAM read/write actually slows down the phone.
[Captivate Android Development] kinggame992000:
Thank you for making this kernel sir.. Using it on sephi captivating ROM. Work good
[Captivate Android Development] They Drew First Blood:
RE: zram

Agreed, I tried it out for a little bit because dheeraj (dhlalit11) had a tweak, but my phone runs better without it. Flashing kernel version 2.4 now! Thanks again ts1506 :good:

Edit: Hmm, bootloop with v2.4, flashed over v2.3. Redownloading now...

Edit: Odin Semaphore 2.9.15sc success, flash new download of CyanCore v2.4 = bootloop again. Reverting to v2.3 for now, thanks. Initial Semaphore logo stays on screen 10-15 seconds until phone reboots itself, rather than the logo "blinking" before proceeding to boot into the OS.
[Captivate Android Development] ts1506:
I have uploaded a fixed CyanCore 2.4 .

It should fix the bootloop , please try this one. If the issue persists , let me know.
[Captivate Android Development] ts1506:
Looking good eh....

Normal OC , work in progress.

No ETA's please.
[Captivate Android Development] Val D.:
Try to extend step OC settings to 100-1400 and include more governors and I/O schedulers. :good:
[Captivate Android Development] Kyuta Syuko:
Any Governors/Schedulers outside the default Semaphore ones cannot be set with Semaphore Manager. Either that or Nick0703 didn't set them up properly in his kernel for them to be setable with Semaphore Manager. Not a big deal sure just wanted to give fair warning.
[Captivate Android Development] Val D.:
Some kernels offer multiple choices directly in Performance Settings so no need to use Semaphore Manager.
[Captivate Android Development] Kyuta Syuko:
Which is why I said it wasn't a big deal. I was just stating it for those that might expect to be able to do it from Semaphore Manager and think something's wrong when they can't (like I did...)
[Captivate Android Development] Val D.:
Lets get those options in CyanCore first and then we'll figure out how to use them... :cool:
[Captivate Android Development] sephhi:
I wonder what would happen if someone removed a step? 800mhz is barely used or 200mhz. Hmmm, just thinking out loud.
[Captivate Android Development] ghoster76:
You should add more options like 1300 and 1400 :silly:

Good looking at all, watting for 2.5 :highfive:
[Captivate Android Development] ts1506:
There are some issues in normal OC as of now. Once I fix them, I will add those steps too.
[Captivate Android Development] ts1506:
CyanCore 2.4.2 uploaded and attached to OP.

Changelog

1. CWM Updated to 6.0.30

2. Linux Kernel updated to 3.0.73

3. Semaphore 2.9.21s base.

4. New bootlogo , finally no more semaphore logo.
[Captivate Android Development] ts1506:
CyanCore 2.4.3 is uploaded and attached to OP

Changelog

1. Linux Kernel updated to 3.0.74
[Captivate Android Development] ts1506:
CyanCore 2.4.4 is uploaded and attached to OP

Changelog

1. UHID Driver Implemented.
[Captivate Android Development] ts1506:
CyanCore 2.5 uploaded and attached to OP

Changelog

1. hrtimer: Consider preemption when migrating hrtimer cpu_bases

2. hrtimer: Prevent enqueue of hrtimer on dead CPU

3. mutex: Make more scalable by doing less atomic operations

4. mutex: restrict mutex spinning to only one task per mutex

5. rwsem: steal writing sem for better performance

6. lib/rwsem.c: fix compatibility issues with Linux 3.0.y

7. drivers: mmc: disable CRC

8. ext4: prevent kernel panic in case of uninitialized jinode

9. lib/string & lib/memcpy: use GNU implementation.

10. mmc: core: Fix possible memory leak

11. input: evdev: Move wake_lock_destroy call

Sorry for the technical looking changelog , I had no idea how I should call these in layman terms , the most I could say that they are under-the-hood changes which improve performance and which was brought to my notice by mnazim.
[Captivate Android Development] mindphaser2k9:
Thanks for your hard work! Does the new version support OC?
[Captivate Android Development] ts1506:
Only Live OC for now.
[Captivate Android Development] casper846969:
Nice work I just installed it thank u
[Captivate Android Development] ts1506:
CyanCore 2.5.1 uploaded and attached to OP.

Changelog

1. ROW Scheduler tweaked (thanks for crack bringing this to my notice)
[Captivate Android Development] ecselite:
Working on slimbean ?
[Captivate Android Development] Kyuta Syuko:
I don't see any reason it shouldn't. I'm not using it yet. Still waiting for the step OC...
[Captivate Android Development] ts1506:
CyanCore 2.5.5 is uploaded and attached to OP

Changelog

1. Update Base to Semaphore 2.9.23s

2. Update Linux Kernel to 3.0.75

3. Some stuff I had forgotten before

4. Tweaks to CFQ Scheduler

5. Fixes to ROW Scheduler
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6 uploaded and attached to OP

Changelog

1. Normal CPU OC Steps ( 1400,1300,1200 and 1100MHz )

There is a slight bug, CPU steps dont persist after reboot, they go back to 100 and 1000MHz.

There are two solutions

1. Use NSTools or equivalent software

2. Use my init.d script

#!/system/bin/sh
# Sets the min frequency
echo 400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# Sets the max frequency
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

The 1st one is the minimum frequency and the 2nd one is the maximum frequency.

Another thing , dont change voltages using Semaphore manager , and it doesnt support all the steps , use NSTools instead.
[Captivate Android Development] mindphaser2k9:
Finally!!! :victory:

I'd say it is not a kernel bug but more possible a bug of ROM, because it happens with Unofficial Semaphore too. I use Voltage Control to persist frequency settings. Works good.
[Captivate Android Development] ts1506:
I found that cpu steps persist if you dont use semaphore manager to live oc.
[Captivate Android Development] Yuna:
Why classic OC is better than live oc?
[Captivate Android Development] mindphaser2k9:
Because to use LiveOC you need to be lucky. My phone almost doesn't support it.
[Captivate Android Development] Yuna:
Well my phone handles 120% oc
[Captivate Android Development] mindphaser2k9:
What I tell you, you're lucky one. My phone can do only 108%.
[Captivate Android Development] Yuna:
Did you tried to set 120%? Cos @ 109 my phne unstable.
[Captivate Android Development] mindphaser2k9:
Please do not think I'm dumb. Of course I have tried to set 120% and my phone hangs immediately. And everything higher than 108% works unstable for me. And I tried to play with voltages. Now I use 1200 OC + 108% LiveOC and that works just fine.
[Captivate Android Development] They Drew First Blood:
Re: LiveOC

LiveOC overclocks the entire system bus, which includes both the CPU and the GPU (I may be using the wrong terminology here, but both the CPU and GPU are affected). The regular overclock only affects the CPU clocks. A CPU overclock can be more stable than a LiveOC, because the CPU overclock is only stepping the CPU frequency rather than affecting the entire underlying bus speed. Some Cappys can handle the LiveOC well, others can not. Hopefully this is helpful info and a language barrier is not getting in the way :)
[Captivate Android Development] Val D.:
Yes, same like in PC overclocking. When you pump the bus, every device attached to it may fail, hence greater chance to get unstable system.
[Captivate Android Development] Yuna:
Interesting counter-question: can liveoc help me pump OC even further? my cappy handle 120 liveoc and can handle 1300 classic oc. can i combine 1300*115 for example to raise overclocking limit? (1.5 ghz)
[Captivate Android Development] Val D.:
Nothing interesting here. If you know 1300 is the maximum your CPU can handle, then there is no way to run it at 1500.

To reach higher CPU clock you need to raise CPU voltage, but don't go over 1450mV. Max acceptable GPU voltage is 1250mV. Anything over and you may damage the phone. Your battery will have shortened live too, as expected. Change the phone if you really need something fast. Captivate is 3y old device already, remember?
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6.1 uploaded and attached to OP.

Changelog

1. Updated base to Semaphore 2.9.24s

2. Updated Linux Kernel to 3.0.76
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6.2 Uploaded and attached to OP

Changelog

1. Updated Linux Kernel to 3.0.77

2. Changed Normal OC Voltages for more stability

3. BigMem Libs patch fixed.

Enjoy.
[Captivate Android Development] sephhi:
Thank you for the fast updates.
[Captivate Android Development] Yuna:
> 3. BigMem Libs patch fixed.

what was fixed?
[Captivate Android Development] ts1506:
The updater wasnt setting the correct permissions to the libs, hence video playback didnt work, now it flashes correctly
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6.3 uploaded and attached to OP

Changelog

1. Updated Linux Kernel to 3.0.78
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6.4 uploaded and attached to OP

Changelog

1. Updated Semaphore Base to 2.9.25

2. Max_lux input set to 6000.
[Captivate Android Development] ts1506:
CyanCore kernel 2.6.5 uploaded and attached to OP

Changelog

1. Compiled with Latest Linaro 4.7.3 2013/04

2. Added XZ Compression for Kernel and initramfs
[Captivate Android Development] ghoster76:
It's good to see there's still a man working in Captivate Zone here :good: Keep it
[Captivate Android Development] Kyuta Syuko:
Semaphore and Nick's Unofficial are still updated. Semaphore you'll have to compile the newest one yourself and Nick doesn't post to his thread but he did update the OP.
[Captivate Android Development] ts1506:
CyanCore Kernel 2.6.6 uploaded and attached to OP

Changelog

1. Compiled with ARM Cortex A8 optimized Linaro 4.7.4 2013/05/18 by [MENTION=4825437]Christopher83[/MENTION]

2. Updated Linux Kernel to 3.0.79
[Captivate Android Development] sephhi:
I seem to be getting smoother scrolling with this latest version. I'm not sure if it's just my eyes.
[Captivate Android Development] Thunder22:
I agree very smooth
[Captivate Android Development] Avikar:
CM 10

Which version is compatible with CM 10?
[Captivate Android Development] ts1506:
Could be due to XZ compression and optimized toolchain

None. CyanCore supports 4.2.x ROMs only, i.e like CM10.1
[Captivate Android Development] Avikar:
Thanks for developing this kernel but had to install official Semaphore bcause I am on CM10 because i wanted Xperia locksreen.. :laugh: :good:
[Captivate Android Development] HoangTuBot:
Can port Mackay kernel 4.1 and 4.2 for captivate. Please.

Or help me to port it. Thanks:laugh: