yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Lanchon:
the kernel changes whenever it changes, and when it changes it's because there's a new commit here...

https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/commits/cm-12.1
[Galaxy S II Original Android Development] cactusman2:
Play Store and Camera Issues

I assume the Play Store issue is from the latest nightly I installed (2015-08-01) and the camera one has been since I installed the ROM first.

First, the Play Store crashes when I go into the settings or when I hit install or update on an app. That and it isn't installing apps when I hit install on the website.

Second, the camera isn't recording video. The app freezes whenever I try. This also happens in Snapchat, it just refuses to record video and after that it won't allow you to switch from the back camera to the front.

Anyone having similar issues? I've seen other camera related bugs.
[Galaxy S II Original Android Development] Leodacompito:
Unknow in call list

Hi,

when I call someone from the contacts at the end of the call the call list show me "Unknow number". It happens so frequently but not every time. It happens also for the incoming calls.

I see that it happens with direct numbers dialed.

The version I run is the 20150801.

Thanks.
[Galaxy S II Original Android Development] Dr.Fix:
Nightly builds for i9100 stopped two days ago, on 01/08... anybody knows why? The other devices have 02/08 and 03/08 build...
[Galaxy S II Original Android Development] kal4metal:
Viper4android is what you need. Flash stericsson's latest busybox zip and visit V4A xda thread. ;)
[Galaxy S II Original Android Development] chrisXL:
H3G carrier? Many people have this problem in italy.
[Galaxy S II Original Android Development] Leodacompito:
Yes H3G is my carrier.

It is a provider issue?

Thanks.
[Galaxy S II Original Android Development] tnttrx:
CM 12.1 works great.

one step further could be... oh, no... wait...

two steps further could be introducing TRIM enabled kernel:

1. NAND relief (guarantied)

2. performance boost (likely)

[MENTION=6159291]Lysergic Acid[/MENTION]:

will it happen any time soon? :)
[Galaxy S II Original Android Development] chrisXL:
Yes
[Galaxy S II Original Android Development] ajislav:
last_kmsg

Hi,

my S2 crashed this morning due to low memory.

I have a tasker profile which turns on sync automatically at 7am, shortly after the phone rebooted.

last_kmsg here

http://pastebin.com/9KQ2cdrV

Anybody facing the same issues? Any workarounds?
[Galaxy S II Original Android Development] Leodacompito:
Thanks, so there is some fix to do on the build side? Why in the CM11 it did not happened?
[Galaxy S II Original Android Development] kostelo:
[MENTION=6159291]Lysergic Acid[/MENTION] I am bringing this post to your attention, in case you didn't catch that. It's a solution hopefully for green lines in online video, thanks to [MENTION=2222292]rINanDO[/MENTION]
[Galaxy S II Original Android Development] LeBourrin:
No, others devices don't have nightly (I look at S6, Nexus 6 and One M8) so it's general bug. Maybe a compilator problem.
[Galaxy S II Original Android Development] Dr.Fix:
http://download.cyanogenmod.org/

A lot of devices have 02/08 build... only one "vs980" has 03/08 build.
[Galaxy S II Original Android Development] Kurt Krummbein:
See yourself: CyangenMod Jenkins Dashboard.

Cheers

Kurt
[Galaxy S II Original Android Development] Weib67:
Random reboots or freezes on clean install

Sorry for quoting the same posts again, but I would like to ask [MENTION=6159291]Lysergic Acid[/MENTION] if there is any clue about the sudden freeze problem. It seems that we are quite a few to experience it regularly.

Thank you.:)
[Galaxy S II Original Android Development] Fr4nz83:
I second your request. These freezes/reboots seem to happen 99% of times whenever I'm seeing videos or browsing the internet (or both).
[Galaxy S II Original Android Development] Weib67:
We are a lot actually. Unfortunately, the last posts are full of recovery feature request.

And even if I totally agree that the CM one is very limited, I think such a stability problem shoud be the number one priority.
[Galaxy S II Original Android Development] kudos1uk:
Saying your phone freezes and reboots is of no help at all, if you want help you need to provide logs.

Not trying to be rude but LA's phone (like most) is stable so the problem cant be recreated without something to go on.
[Galaxy S II Original Android Development] rINanDO:
I also have this problem sometimes, and trying to get some logs. It seems very random and therefore very difficult/impossible to reproduce. In my cases: catlog, whatsapp, xda, browsing with aosp browser or chrome... I use CoolTool to see CPU or memory load, but all seems to behave normal... I use my phone as daily drive and have crashes at least once or twice a week like this.. But it is good enough for me! I saw a log in a few posts back indicating that probably something is wrong with the audiodriver, but in my opinion it is a result of slowdown in Android OS causing audio troubles/timeouts. Please have patience with this bug. This is a though one! I hope someone will post the 'winning' logcat ;) so LA or anyone willing to help to fix this.
[Galaxy S II Original Android Development] xhoster:
Hey :)

mmcqd/0 seems to be one of the reasons we experience those slowdowns (this would underline the fact, that most of the times it happens when streaming Videos or starting I/O heavy apps (e.g. spotify)).

If those who experience slowdowns could try "cool tool" and use the toolbar with "I/O activity" (set max I/O bandwidth to 75000kb/s and "chart" to "I/O activity) and activate "most resource-intensive process".

When the phone slows down, mmcqd/0 should pop up and I/O activity should be pretty high.

You could also activate CPU usage and CPU freq.

Tried this with and without external SD card and seems to be consistent.

Will try to get some logs tomorrow.

Another bug I found:

When listening to music (from external SD card) and turning the phone from portrait to landscape and back a few times, the music app will crash, but music keeps on playing.

Maybe somebody else could replicate this, to see if it is a problem on my side.

And I will try to catch some logs of this, too.

And thanks to all, who keep this awesome phone alive :cool::D

EDIT: what I wanted to say is not that the mmcqd daemon slows down the phone, but the NAND writing/reading which happens.

I don't know what is causing it, right know. Just that it happens.

EDIT2: Could it be, that the better performance from ext4 (spikes>100mb/s, but I don't know how accurate the reading is) over vfat hogs up the kernel with writing and reading, which causes the CPU usage to spike (Android just seems to idle until heavy I/O Activity is finished)?

Maybe this thread could help...
[Galaxy S II Original Android Development] Weib67:
I agree man, and don't/didn't want to be rube either. I totally respect LA work (feel free to take a look at my previous posts).

However, the problem is real and we need to discuss it.

Plus, we can't state that most of the phones are stable or not, but based on feedbacks, we can at least say that a significant number are affected.

Personally, I'm on an old build (still unofficial, running xposed), and I'm not sure my logs would help in this context.

However, I did an ultra clean official build install on a different I9100 last week (stock kernel and no mods), and I found out that thoses freezes are still present. As many people here.
[Galaxy S II Original Android Development] buffer overflow:
Two stupid question... 1: this rom have Carrier Label ? 2: Someone try to install xposed ?...and if you have succeeded. Thanks in advance ! :D
[Galaxy S II Original Android Development] xhoster:
Regarding the mmcqd/0 slowdowns:

/data (5gb) and /sdcard0 (9gb) have >55% free space.

I trimmed everything, even preload. For sdcard0 just use terminal and type in:

1. su

2. fstrim -v /mnt/media_rw/sdcard0

But even after doing this (again), it gets better, but there are still slowdowns happening, maybe you guys could still try it.

I will use this post to add more info over the day.

1. Yes (lockscreen)

2. Yes and works
[Galaxy S II Original Android Development] buffer overflow:
[MENTION=5397920]xhoster[/MENTION] Well, i was interested if hase out of locksceen.Seems not have this feature. :)
[Galaxy S II Original Android Development] xhoster:
Just on the lockscreen and under the mobile signal tile in the notification quick settings.

But there are a lot of ways to add it into the status bar ;)
[Galaxy S II Original Android Development] buffer overflow:
Yes, i know , but i was curios if have this feature default.

:good:
[Galaxy S II Original Android Development] SafinWasi:
Hey guys. New to the S2 forums.

I have an S2 running CM11 M12 currently and wanted to update to CM12. So I downloaded the 08-01 nightly and flashed it for a clean install. Surprisingly,on the first boot all I get is a black screen with an FC for SystemUI. Rebooted into CM recovery,wiped data and reinstalled CM11. My guess is that it's for this nightly specifically.

So,can anyone give me a confirmed working nightly?

Also,is there a way to replace the recovery? I'm used to CWM and TWRP so for me this one sucks.

Thanks.
[Galaxy S II Original Android Development] Dr.Fix:
This happens to me too, even when not using the phone. Sometimes i leave the phone on the desk without doing anything (with all the apps closed, not running in background).

When I try to wake it up the display doesn't turn on or it turns on but it is completely unresponsive (lock screen is like a bitmap, physical keys don't turn on).

The ony thing I could do is keeping the power button pressed until reboot.

That's very frustrating because in the meantime the phone doesn't work, nor connection. So if someone's looking for me ot texts me I don't receive anything and I'm totaly unaware of this.
[Galaxy S II Original Android Development] kal4metal:
Due to runtime changes (dalvik to art), you have to do a clean install to be sure. Download gustavo kernel unofficial by Lysergic Acid, from the third post in the unofficial cm12 thread. Also download latest Philz recovery, which is signed and flash it over cm recovery but DON'T TRY TO BOOT INTO SYSTEM! Power off and power on again while pressing vol up+menu+power to get in philz recovery. Now flash gustavo kernel zip. Reboot to recovery. Congrats! You're on cwm! But you still need to do a clean install. Wipe data, system, cache and dalvik cache. Then flash your nightly zip. Then gapps and you mods if you use any. Don't forget to reflash gustavo lernel, because you'll bring back cm recovery. Recover your apps from play store after initial boot :)
[Galaxy S II Original Android Development] xhoster:
EDIT: does anybody know if android kernels format ext4 with lazy init enabled?

EDIT2: below this EDIT just makes it a bit better, but slowdowns still happen!

Sorry for spamming this thread, but for everyone experiencing slowdowns:

please trim your normal partitions with a trimmer app from the play store

trim sdcard0 (and sdcard1 if it has an appropiate filesystem)

start terminal

type in "su" -> enter

type in "fstrim -v /mnt/media_rw/sdcard0" -> enter

download kernel audiutor (or any other app capable to change kernel settings)

set I/O Scheduler to "sio"

in the same menu set "Read-Ahead" to "4096kB"

try to keep as much free space on sdcard0 as possible (this ROM seems to be even more depending on fast memory (NAND))

(in kernel audiutor you have to set your settings to be applied after reboot, if you want to have them after rebooting ;) )

This should get rid of most of the slowdowns.

I tried it with heavy multitasking (spotify, google maps and firefox with video in background) and it was pretty stable (don't expect the s2 to be smooth in this kind of situation, but the phone keeps beeing responsive).

After unlocking the phone, there is a spike in I/O activity and seems to be the same reason as for the slowdowns while using it.

Android just handles it this way ("waiting" for I/O to be finished and not using defined CPU % for UI and other system stuff).

Disclaimer: This all is just speculation from my side! It seems to have helped me and doesn't cause harm.
[Galaxy S II Original Android Development] anonimowywybryk:
Does anyone use stweaks bearing kernel Dorimanx ? Someone may give some sense set individual parameters for the system is running stable , fast and does not hog battery
[Galaxy S II Original Android Development] chrisXL:
Update 08/04 available.
[Galaxy S II Original Android Development] Weib67:
Thanks [MENTION=5397920]xhoster[/MENTION] for your response. All ideas are welcome, and yours seem very interesting.

However, a custom kernel is required, right ? Which one would you recommend ? Any possibilities to stay on stock kernel ?

Can't wait to have LA insight on the question. :)
[Galaxy S II Original Android Development] aminya:
Tnx vey much. I flashed this supermod & it is great. I have no noise or breaks anymore.

Also i convert the vip4android that is included tu user app to make it work.

http://xdaforums.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951

---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------

I highly recomend this dorimanX kernel. The battry is great. & also you can easily change cpu governer for more or full performance if needed

http://xdaforums.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879
[Galaxy S II Original Android Development] SafinWasi:
Thanks mate. Just one question. Should I dirty flash over CM11 or install not-working cm12 and then Gustavo kernel+cwm?

Sent from my GT-i9100 running CM11
[Galaxy S II Original Android Development] kal4metal:
If your cm11 build has cwm already then you can skip the philz recovery step. Do a factory reset, wipe system and flash your cm12.1 rom, then gapps (download pico gapps as I suspect you haven't flashed any pit through ODIN to repartition system/data), then gustavo kernel. reboot and boom! You're good to go ;)
[Galaxy S II Original Android Development] Toniccu23:
OTA Problem

With OTA update there is an "md5 verify fail" problem. Solutions?
[Galaxy S II Original Android Development] xhoster:
Use the TRIM enabled cm12.1 kernel from Lanchon: Download (at the bottom)
[Galaxy S II Original Android Development] ringen00:
I'll have to select the Gustavo Kernel zip and the Xposed zip in cyandelta after I flashed Gustavo, right? !

Update:

Think I'll give up cyandelta. The SuperSU binary shall be updated but no effort... :(
[Galaxy S II Original Android Development] kal4metal:
In cyandelta, choose xposed, gapps, gustavo kernel AND SuperSU zip. Make sure you have clear cache checked and try again ;)
[Galaxy S II Original Android Development] ringen00:
Will give it another try.

Will I definitely have to choose gapps too? So far (cmupdater) gapps have been still there after upgrading...

Will have to wait - I'm on 0804 now....

Is it relevant to have the option to update the CM-Recovery in the developer settings deactivated?
[Galaxy S II Original Android Development] zoff_ita:
Hi all, I'm on 0801 but this problem still from previous builds.

I'm trying to revert to CWM recovery but I can't overwrite Cyanogen Recovery.

I tried with heimdall but if I boot directly in download mode i get this error:

$ sudo heimdall flash --RECOVERY recovery.img
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
libusb: error [op_detach_kernel_driver] detach failed error -1 errno 113
Claiming interface again...
ERROR: Claiming interface failed!

Instead if I boot the recovery and change to download mode with "Reboot to bootloader" the process seems to work fine:

$ sudo heimdall flash --RECOVERY recovery.img
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...

Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading RECOVERY
100%
RECOVERY upload successful

Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

but it's extremely fast (uploading lasts a fraction of a second) and on reboot Cyanogen Recovery still stands.

Any idea?
[Galaxy S II Original Android Development] Lysergic Acid:
I saw it, I may need to adopt another approach as this will most likely break another devices. I've had problems with my build environment so now I'm starting everything from scratch, I'll find a way to implement it as soon as my environment is ready to work again.

The kernel itself don't change a lot most of the times, the ramdisk changes more often, so yeah, I would need to keep updating the zip if I follow that way.
[Galaxy S II Original Android Development] kal4metal:
I always install gapps on every OTA with cyandelta. It's a foolproof approach, it doesn't cause any problems. That option in developer settings is for newer devices that have a dedicated recovery partition. You can keep it disabled but it won't have any difference.
[Galaxy S II Original Android Development] Lysergic Acid:
This is a stock CM 12.1 kernel + TWRP 2.8.7.0, up to 04/08/2015 sources, and of course, this is signed :p, flashable from the Cyanogen Recovery. I didn't extensively test this, but should be fine.

Download: https://www.androidfilehost.com/?fid=24052804347787517
[Galaxy S II Original Android Development] Klaus N.:
My girlfriend's i9100 is on the last cm11-build atm., with already modified pitfile. When I'm switching to cm12.1, will the pitfile be untouched? What else do I have to consider?

Thanks in advance.
[Galaxy S II Original Android Development] Phenomzye:
Is there any way to change I/O and governor without any 3rd party program? I don't see the Performance thingy at options unlike other LP ROMs.. and yes I've tapped the developer settings thing
[Galaxy S II Original Android Development] Malhavoc Blackdrake:
That's great! Any chance of a TRIM enabled one too ? :D
[Galaxy S II Original Android Development] Lysergic Acid:
Yes, sadly I can't modify the pit with flashable zips, this can only change with a former pit file flash from odin.

This option was removed in order to have per-app profiles/battery mode.

That kind of differs from a stock kernel idea, I can make one when I have nothing else to do, but no promises ;)
[Galaxy S II Original Android Development] lukss12:
Why is it considered to be incompatible with a stock kernel idea? TRIM is an eMMC standar function and bugged chips are now well known. Also there is a considerable ammount of documentantion about the bug. So, it's more likely they are overreacting. They could merge(adapt) the patch in stock kernel and TRIM will work on non bugged chips while the kernel will block the function on a confiuration with an affected chip.

So resuming. Are they refusing to add TRIM just for being protected for "possible" bricks? Or there is a real risk i'm not aware of?

Would like to know your opinion on this topic! Thanks:)
[Galaxy S II Original Android Development] Lysergic Acid:
The part about a "not stock idea" is just because TRIM is not present in the CM stock kernel. From what I know there's no real risk of bricking because our kernel is patched for that, even MAG2GA chips should be ok, but, there's a risk of wiping commands to brick the device when flashing the ROM coming from a non safe kernel, this doesn't affect TRIM functionality anyway.

The CM admins are really cautious about that, they prefer a lot to stay without TRIM, as they don't have problems without TRIM, we will need a very very good explanation on why we need trim. I've seen maintainers patching devices that never bricked because of that EMMC bug, just to be cautious, I think you get the idea.

It's not impossible though, but good arguments are necessary.
[Galaxy S II Original Android Development] lukss12:
I don't think we could find any argument different from decreasing eMMC life or loosing some MB/s on writing. May be if write performance decrease so much than some write intensive functions like HD recording could not be processed or something like that? But i don't know if it is possible.

Thanks for the answer :D
[Galaxy S II Original Android Development] Malhavoc Blackdrake:
Well, TWRP isn't stock either :p ..but I get the idea :o

On the other hand, could you please put that link in the first post? Many users could miss it otherwise, and it's really useful, especially if in the future you have to tweak it and upload it again too due to changes in the kernel or whatelse.
[Galaxy S II Original Android Development] Klaus N.:
I believe that is good news for me, because I don't want to switch to the rather small stock system partition. I've only asked that, because I read that someone despite of having the modyfied pit, after switching to cm12.1 there was a problem with insufficient system space (e.g. by using the pa micro gapps).

This is, what I meant:

Is this already fixed, so I can switch from cm11 to cm12.1, and the device can use the modified pit system partition fully?

Thank you!
[Galaxy S II Original Android Development] c.pizarro:
While testing the new kernel, it seems that i am unable to mount my external sd card via TWRP.

Is there a possibility to fix this?
[Galaxy S II Original Android Development] daniu:
Hi,

just like everybody else I am more than happy about that new kernel version. And - probably just like most others - I would also love to see the kernel with trim enabled

regards
[Galaxy S II Original Android Development] hebermc:
I am still on one of the may unofficial builds, can I just update to the lastes nightly?
[Galaxy S II Original Android Development] x3dnd3x:
Need a kernel like some mentioned.
[Galaxy S II Original Android Development] OneDream:
Hi everyone.

I'd like to flash CM 12.1 coming from Stock Android v4.1.2. I've tried several methods and suggestions to no avail. So far everything I've tried has resulted in either a bootloop or a phone that's constantly showing me force closing apps.

Could anyone tell me what the best way would be to go about this? Please keep in mind that I haven't flashed and messed around with my S II in a very long time, so consider me to be somewhat of a newbie seeing as how most of my knowledge has most likely become outdated. Thanks in advance.
[Galaxy S II Original Android Development] kai1313:
1. get kitkat compatible cwm (philzz, cwm, gustavo, dorimanx)

2. go to recovery do full/clean wipe (system, cache, dalvik, data) or you can use hawkerpaul script to do full wipe

3. flash the latest(the latest usually more bugs free) CM 12.1 zip

4. flash gapps, if you still use stock PIT (500mb /system), use pico gapps

5. reboot
[Galaxy S II Original Android Development] asia559571:
WONDERFUL:silly: Thank You So Much:highfive:
[Galaxy S II Original Android Development] daniu:
Hi,

wao ... now I am there: CM12.1 with TWRP, Xposed, Xprivacy and everything seems to run quite smoothly.

regards
[Galaxy S II Original Android Development] onlyfor.foren:
Works flawlessly, also in conjunction with CyanDelta. :good:

Thanks
[Galaxy S II Original Android Development] Lysergic Acid:
Yes, I was just waiting for a positive feedback like the below quote ;)

Yes, that problem persisted for a day or two only, there's no more system size issues.