yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] WaLshy11:
This is a noob question and the TRIM thread is confusing me a bit..

Do I just installed this kernel (following the instructions on the TRIM thread, and of course backup first) and that's it? I don't need to do anything else?
[Galaxy S II Original Android Development] the.gangster:
[MENTION=1963973]WaLshy11[/MENTION]

To trim?

You should install trimmer app or use terminal or adb to fire the fstrim command with partitions /data, /system, /cache, /preload. (Preload is not supported by the trimmer app)
[Galaxy S II Original Android Development] franticfreddy:
Hi,

its great to hear that you have created newest kernel with twrp

recovery!

Unfortunately my phone has the emmc chip with superbrick bug :(

So im afraid to use your kernel..but i really want to give it a try because

of the freeze-fix..

Could you please create same latest kernel (of 10th January 2016) including

freeze-fix and twrp, but *without* trim function? :)

Thanks in advance..
[Galaxy S II Original Android Development] WaLshy11:
I suppose I was mainly looking for the freeze fix part of it, but if the TRIM is there I might as well try it.

Ill re-read the TRIM thread a few more times
[Galaxy S II Original Android Development] the.gangster:
[MENTION=1963973]WaLshy11[/MENTION]

Then you obviously missed the fact that the freezefix-patch was merged into Nightly 20160107 (and newer).

So it's fixed already without this kernel. This one only makes sense if you want to have TWRP or Trim (or both).
[Galaxy S II Original Android Development] WaLshy11:
I did miss that! Thank you!
[Galaxy S II Original Android Development] Lanchon:
no! read below...

dont read anything, just flash and trim, it is totally safe!!

---------- Post added at 11:54 PM ---------- Previous post was at 11:49 PM ----------

lol u r so wrong... only i didnt have the time to post yet :-p
[Galaxy S II Original Android Development] the.gangster:
Man, I am really happy to hear that!!

So I should edit my post. Did you find the error in the 2nd-recovery-from-preload-partition approach or develop something totaly different?

Now everyone will be couriously waiting for your post.

:D
[Galaxy S II Original Android Development] Lanchon:
no, i know what you mean but i didn't really look into that post. i saw how things worked when making the twrp kernels and so hacked it.
[Galaxy S II Original Android Development] the.gangster:
You are the man!

I knew you would find a solution if you only looked at it.
[Galaxy S II Original Android Development] UsualSuspectReaL:
One day now without any freeze and rom is ****ing smooth ! Nice job :D
[Galaxy S II Original Android Development] Lanchon:
PUBLIC SERVICE ANNOUNCEMENT

meet IsoRec, the isolated recovery solution that finally lets you choose your preferred recovery.

enjoy!
[Galaxy S II Original Android Development] matee89:
[MENTION=6159291]Lysergic Acid[/MENTION], [MENTION=5948587]zeitferne[/MENTION]

Amazing job! I can truly recommend CM 12.1 since 20160107 nightly for everyone. The ROM is simply rock solid since you've implemented the kernel freeze. I am a heavy, daily user of my I9100 with 20160107 CM 12.1 nightly and no matter what, I cannot make it freeze (or lag). Multitasking with apps like chrome, viber, tunein, emulators result in really lagfree experience like on the newer smartphones. You've got my appreciation for bringing professional support for I9100 and hope that CM 13 will be even better. Keep it up!
[Galaxy S II Original Android Development] davishammet:
Sorry guys if i'm repetitive but is my first CM; i've an s2 4.1.2 Jelly Bean Stock, and i would to install this CM (first, can u advise me which build is more stable than others?) How i can do? I've read about a KK compatible recovery, where i find it? If someone can help me with a guide, also on private message, i would be grateful. Thanks all :)
[Galaxy S II Original Android Development] Klaerchen:
Better disable ZRAM?

Since quite a while I disabled the ZRAM (removed it from fstab) and find it now (with the freezefix) much better than with activated ZRAM.

After 130 hours of uptime I'm still below 300 MByte system memory and the device is still fast and smooth. I think the possible advantages of having a swap space is over-compensated by the negative effect, that ZRAM reduces the available RAM size. I would vote for disabling ZRAM for our device.

What do you think?
[Galaxy S II Original Android Development] LeBourrin:
I'm agree with you but, before that we need to fix the mysterious Out of Memory bug.
[Galaxy S II Original Android Development] fireburner-de:
FYI: At least since Nightly from 7th Jan, those two vulnerabilities are fixed.
[Galaxy S II Original Android Development] aminya:
My Battery Or Rom?

Now that feeezes are fixed. I want to ask if other people have battery problems or it's just for mine & my battery is not working good any more. As you see in the attached image the battery acts good in the sleep. But when i use it, & it's awake the percentages go down fast. I have calibrated my battery several times. & even i have put it in the freezer as i googled :D

I used to be on gsstudios dorimanx kernel. & i had imported a [MENTION=5811506]gsstudios[/MENTION] special settings for stweaks that it was great in sleep & some hiw better in awake. but however in awake the story was te same; percentages had gone down fast but not too fast. But because i wanted to have Xtreemmusic sound mod that needed selinux set to premessive ( i'm musician so it's important for me) i changed the kernel & i'm on the [MENTION=4141005]Lanchon[/MENTION] kernel.

The problem is battery or rom?
[Galaxy S II Original Android Development] ouzowtf:
Your battery level drops when the phone is awake and screen is on, therefore it's in use. That's absolutely normal.

Gesendet von meinem LG-H815 mit Tapatalk
[Galaxy S II Original Android Development] the.gangster:
[MENTION=6839284]aminya[/MENTION]

I had simular extrem drops while active. Since I bought new battery that improved a lot.
[Galaxy S II Original Android Development] kudos1uk:
Your battery I think, my battery life is better than ever.

Odd, I use Lanchon Kernel, mine is enforcing, I thought Lanchon kept the kernels stock which would be enforcing?

You can get SELinuxModeChanger that switches selinux at will: http://xdaforums.com/showthread.php?t=2524485
[Galaxy S II Original Android Development] Klaerchen:
I'm not convinced that we really have a memory leak (anymore?). My System memory usage keeps low, even going down to 258 MByte after 140 hours. I never had such a constant behavior in the last months with ZRAM.

I imagine, that in case ZRAM is enabled there is a vicious circle: Android uses swap a little, the ZRAM increases System memory usage and reduces free RAM, so Android swaps more. And so on.

Without ZRAM the memory footprint is constant.
[Galaxy S II Original Android Development] kudos1uk:
Quick question, with freezefix we should keep pegasusq on ondemand, which is standard in the kernel.... so far so good!

In battery settings you can turn "enable per app profiles" on or off in CM12, is comes set to ON by default, as this adjusts the CPU governer, should we keep this turned off?
[Galaxy S II Original Android Development] Klaerchen:
Stay with ondemand, which is also the default selection.
[Galaxy S II Original Android Development] kudos1uk:
I got that bit, that's what I'm clear with.

The question is: If you turn "enable per app profiles" on in Settings>Battery...... does it take you off ondemand?

Should "enable per app profiles" be left to "OFF" so the CPU governer does not get changed?
[Galaxy S II Original Android Development] Naudiz:
How did you do that?

I tried to edit fstab.smdk4210 in root directory ( / ), but it seems to always get reset to default upon boot.
[Galaxy S II Original Android Development] kudos1uk:
You could just set zram to zero with kernel adiutor.
[Galaxy S II Original Android Development] Naudiz:
Of course, you are correct ;)

However, I was specifically curious how he managed to edit fstab :)
[Galaxy S II Original Android Development] the.gangster:
Am I the only one who is totally satisfied with the current ROM? No problems with ZRAM or whatsoever...

---------- Post added at 01:16 AM ---------- Previous post was at 01:02 AM ----------

Now I tried with both devices.

Adb does not detect them while in current CM- or TWRP-recovery.
[Galaxy S II Original Android Development] pilgrim011:
Probably. Lollipop on our device is very slow compared to Kitkat for example. You still have to wait couple of seconds until simple app like dialer opens, there is a delay even in incoming call etc. So, it's far from perfect.
[Galaxy S II Original Android Development] Klaerchen:
I changed the source and rebuilt CM12.1, sorry forgot to mention.
[Galaxy S II Original Android Development] makix13:
I'm very happy with the ROM, it's really good, I know it's not a S6 or similar [emoji6] , but it works great better than jb stock rom (with freezefix patch) .

With Trim, some times seems that fly [emoji2] .

The GPS works, videos, in standby deep sleep it's perfect (original battery from 2011), so for a mobile from 2011,it's a perfect ROM, hope CM 13 will be similar or better [emoji2] .

Thanks to [MENTION=6159291]Lysergic Acid[/MENTION], [MENTION=4141005]Lanchon[/MENTION], [MENTION=5948587]zeitferne[/MENTION], etc... For their work [emoji122] [emoji106]

S2 Cyanogenmod 5.1.1 [official nightly] - Xposed [official framework] - Viper4Android
[Galaxy S II Original Android Development] kudos1uk:
That's not my experience, both of my S2's are streets ahead of KitKat, 170 apps, repartitioned back in KitKat days but opens dialler instantly, no delay on incoming calls (since vibrate turned off (don't know if still needs to be off?).

Best, fastest and smoothest ROM rom I ever ran since new in 2011.
[Galaxy S II Original Android Development] pilgrim011:
Very strange, indeed. I'm constantly moving between KK and LP ROMs and I have flashed many different based ROMs, but every KK ROM is much much faster than any LP (not including ROMs with huge bugs). And it's similar even on newer phones that came with KK and later received official LP upgrades - with LP they are noticeably slower, of course, not as slow as our device, since it's official, optimised upgrade.
[Galaxy S II Original Android Development] fireburner-de:
Anyone experienced performance drops after changing themes?

Just today, AOSP-keyboard and Google Search were bugging after I had changed my theme. After some time, i got a UI has stopped error and afterwards it seams to be normal again.

edit: I am running stock Trebuchet
[Galaxy S II Original Android Development] cherryb8844:
yes me

I feel some crash ui that wasn't ROM fault that an issues only with individual themes like flux So don't worry try to choose another theme.
[Galaxy S II Original Android Development] FDiHD:
So, i;ve repartitioned my phone, and tried to install cm11...all good...., ..but with cm12.1 it seems it have a problem.

I tried, reflash/full wipe/format system , data ( preload i cant format ..it gives me this error )

formatting /preload....

E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12

Error formatting /preload

When im installing cm12..at the end i get this error : warning: no file_contexts detected filesystem ext4 for /dev/block/mmcblk0p12 ..but at the end it says that the script was succesfully installed

I think ..i get bootloop because of the repartition...how do i fix this ? ..can someone help me ?
[Galaxy S II Original Android Development] fireburner-de:
Did you try formatting /preload with a different Recovery, like I suggested in your Thread?
[Galaxy S II Original Android Development] FDiHD:
i did...same .
[Galaxy S II Original Android Development] Naudiz:
Which recovery did you use? Some have a bug which prevents format of /preload.

Try flashing a Kernel with TWRP recovery (e.g. the one in the OP). In TWRP go to "Advanced > Terminal" and type "make_ext4fs /dev/block/mmcblk0p12" by hand. This should work.
[Galaxy S II Original Android Development] ultravy:
Use this guide for repartition by [MENTION=5811506]gsstudios[/MENTION] , and format your partitions correctly (ext4 cache, data, sys & vfat/fat32 sdcard0 your internal storage) . worked for me 1 gb system, 3 gb data!
[Galaxy S II Original Android Development] FDiHD:
i dont have terminal in TWRP

also.. when i try to wipe dalvik cache

E :unkown volume for path [/sd-ext]

after

i tried.. it also says that for mmcblk0p9

:(
[Galaxy S II Original Android Development] Lanchon:
there is a new fixed TWRP for i9100 provided by arnab: adb sideload, terminal, and wipe dalvik all work fine, i just checked.

go and get it from the IsoRec thread (you need the IsoRec kernel too if you don't already have IsoRec; read the OP).
[Galaxy S II Original Android Development] Naudiz:
It's impossible. The terminal is a standard feature of twrp. Look again, it's under the "advanced" button.
[Galaxy S II Original Android Development] FDiHD:
well..i've downloaded the one from the OP , and when i press on the terminal command button it takes me to the filemanager

also..after that mmcblk error it says : patching system image unconditionally...and at the end ..script installed succesfull [0.20000] or something like that
[Galaxy S II Original Android Development] Naudiz:
This is not the filemanager, it is just where you define the starting folder for the terminal, lol

Just hit "select" at the bottom right and the terminal starts in root folder ( / ).
[Galaxy S II Original Android Development] FDiHD:
my bad :)) i found it..and use it..same thing

i have used the modified preload pit files I9100_6GB data - 45mb preload.pit

still bootloop

Installing update ...

detected ext4 filesystem for / dev / block / mmcblk0p9

detected ext4 filesystem for / dev / block / mmcblk0p10

Patching system image unconditionally ...

detected ext4 filesystem for / dev / block / mmcblk0p9

script succeeded: what result [0.20000]

Install from sdcard complete
[Galaxy S II Original Android Development] the.gangster:
Lol

Some people should really read what their screen presents to them...

And btw: "detected ext4 filesystem for..." are just information messages, not error messages.
[Galaxy S II Original Android Development] Naudiz:
The install script runs fine. It just says that /system (mmcblk0p9) and /data (mmcblk0p10) are formatted as ext4, which is correct. Also the "unconditionally" is nothing to be worried about.

What was the result of formatting mmcblk0p12 from terminal, like I told you?
[Galaxy S II Original Android Development] FDiHD:
didnt saw any erros....dont know why its not working...

that mmc---p12 was a typo ...only says about 9 and 10 ,,not 12
[Galaxy S II Original Android Development] Naudiz:
Dude, I'm sorry, but if you don't listen to the people trying to help you, then you can't be helped... :(

I clearly asked you to go to the terminal in TWRP and type make_ext4fs /dev/block/mmcblk0p12 and tell me the output afterwards. This is not a typo, I clearly said mmcblk0p12.

"Didn't saw any errors" is not what I need to know, I need the explicit output of the make_ext4fs command.
[Galaxy S II Original Android Development] FDiHD:
oki..i will do it tomorow again..i;ve gone back for cm11... i need the phone alarm..so i can get up to work tomorow

//i tought i had to do that to solve my problem..sorry again..btw..i remember i had the same problem like 5 months ago...official cm bootlooped..but i think a custom rom based on cm12 worked...resurrectmix or something..the thing is ..that i want to trim the device after i install the rom..and i dont think trim works with custom roms....there are kernels only for cm12.1 soo yeah..oh..and no..i didnt install anything beside cm12.1..tried..formating /system, /data, preload / sdcard0 /emmc , tried installing cm11 -reboot-wipe-then cm12.1..still the same..i waited 10-15 min...still at the boot logo.

10 seconds after it boots...with the cable plugged i hear a sound in windows 10 that something is plugged in
[Galaxy S II Original Android Development] franticfreddy:
Hey there..from what i have read of your problems, i think you missunderstood some instructions and did crossflash the wrong files..

You should start over flash again from scratch...

Best is when use an external sd-card and copy this files onto it..

1. "philz_touch_6.48.4-i9100.zip"

2. "cm-12.1-20160112-NIGHTLY-i9100.zip"

3. "open_gapps-arm-5.1-pico-20151225.zip"

4. "kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-signed.zip"

5. "recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab)-signed.zip"

6. "UPDATE-SuperSU-v2.46.zip"

--

Turn off your phone..take out battery..wait 10 secs..put battery back, and start your phone into recovery (Vol up+Home+Power..)

Now install philz recovery...when done, take out the battery again and wait 10 secs.

Then put battery back and start phone again into recovery..

Now in philz recovery go to mount and storage, there you can format your partitions needed for clean install: /system, /data, /cache, /preload,..and optional /sdcard0 (attention: you will loose all files from internal storage!)

Again attention, do not format /sdcard1 , this is your sd-card with the needed files!

Philz is only needed to format all partitions and install cm12.1 main.

--

When you have format partitions, then you can install cm12.1 nightly in philz.

When done, choose reboot to recovery in philz (advanced power menu).

Now your phone should boot into cm-recovery.

Then install from sdcard1:

1. open gapps

2. super su

3. kernel lanchon

4. recovery lanchon (arnab)

--

When finish all, take out battery again and wait 10 secs..then put back in and

start your phone again into recovery..

TWRP should appear, and there you only need wipe cache + dalvik.

Then reboot system..

--

I hope you understand my poor instructions..lol

Good luck! :)

EDIT:

I remember i have read from some faulty pit files with 6 gb data

some time ago...maybe this is causing your bug...

Better use 1 gb system - 4 gb data - 512 mb preload..

(this is my setup for now, running fine)

After flash another pit file, you *always must format* /system, /data, /cache, /preload, /sdcard0 !

Else you will run into trouble again...
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=7204806]FDiHD[/MENTION], 3-6 from that list are optional:

3: is strongly recommended, if you want the Play Store, 4: if you want trim, 5: only if you want twrp recovery at the end, 6: root works without this, but supersu will give more preferences/option for root.

In the other post you told something about 6GB /data, maybe you got one of these faulty pit files.

[MENTION=7192829]franticfreddy[/MENTION]

I have actually never wiped /preload after moving away from stock ROM. But my Pit left its size untouched. I have run CM 10.1-12.1 without any obvious problems. Do you think this could eventually lead to trouble sometime?
[Galaxy S II Original Android Development] franticfreddy:
Hi,

if you did change size of /preload, its strongly recommended to format the partition.

Its to ensure for any custom-rom to get all correct partitions size and have space for some eventually needed files installed there..

Maybe our CM dont care about /preload now, but you never know about future updates or other custom roms..

But if your phone is running fine now, theres only a very low chance of getting trouble.

Only in case if you want flash stockrom, you must have a clean formatted 512mb /preload.
[Galaxy S II Original Android Development] Naudiz:
Considering your description, I find it more than likely that you still have an unformatted /preload, which gives you trouble booting CM12.

We have already speculated waaaay too much about this problem, just type in the command that I told you in the terminal and post the output here, then we will know more and don't have to speculate...

Using 512MB /preload on an AOSP Rom is absolutely nonsensical and I will never understand why people keep recommending this.

This is not 100% correct. Formatting just ensures that the partition can be mounted.

It doesn't have anything to do with determining the correct size or placing any files there. No files at all are placed into /preload on AOSP roms.
[Galaxy S II Original Android Development] franticfreddy:
Hi,

this is to ensure to have always the option to flash stockrom via odin, in case you played too much around in your customrom and have bootloops or other problems and only can enter downloadmode..

Also, i cant understand why people really need to shrink the /preload just for having only about 467 mb more, when nowadays some 16 gb sd-card only costs about 5 bucks..

Better leave /preload untouched to lower potential risks and problems like descriped before by several users..
[Galaxy S II Original Android Development] Naudiz:
Just because I don't want to waste any space for unneeded partitions, no matter what's the cost for sd-cards ;)

I assume that someone who was capable of repitting the phone once, will be capable to repit it again, when he needs to flash a stock rom via Odin (you can even flash stock-rom and stock-pit in one single process), so I also don't really see the point of that approach.

Anyways... In our case, the dude [MENTION=7204806]FDiHD[/MENTION] already has repitted, so it's needless to discuss, which pit is best, he just needs to properly format his preload and I'm sure, he will have no problem booting CM12.
[Galaxy S II Original Android Development] FDiHD:
soo..i had cm11....

turn off phone

took out batery

turned on the phone in recovery mode

instaled philips recovery

turn off-battery out..

recovery, ..then formated system, data, cache , preload , sdcard0 then installed cm12.1...same log as above ..about mmc...p9 and p10 ..and script succeesfuly installed [/0.2000]

turned off ..took out battery...power on...bootloop

--

now i think i will try to install twrp and check out what i get in the terminal
[Galaxy S II Original Android Development] Drx86:
If you want to go back to stock ROM after repartitioning, you just have to set stock .pit in Odin and flash it together with stock ROM.

It's not difficult, stock .pit can be downloaded from many threads. :)
[Galaxy S II Original Android Development] FDiHD:
afte using make_ext4fs /dev/block/mmcblk0p1 command

Creating filesystem parammeters :

size :23592960

block size:4096

blocks per group :32768

inodes pre group :1440

Inode size :256

Jurnal blocks :1024

Label :

Blocks :5760

Block groups :1

Reserved block group size :7

Created filesystem with 11/1440 inodes and 1128/5760 blocks

=======

also on twrp when using full wipe after it says its formating eMMC using mkdosfs and done..it says with red E: Unknown MTP message type :1
[Galaxy S II Original Android Development] fireburner-de:
[MENTION=7204806]FDiHD[/MENTION], could you please post the output of "df" command in terminal/adb in here. Just to get sure ur Pit has an appropriate size of /system partition. Maybe you got a faulty PIT.
[Galaxy S II Original Android Development] franticfreddy:
Hi,

i think he used some faulty pit file, as i suppose, because he said he used 6 gb data pit file if you have read before, and there are some faulty pit files with 6 gb data found in the internet.

So thats why he still maybe have strange problems, and thats why i recommend now to repit again and use 1 gb system 4 gb data 512mb preload...maybe its waste of space in your eyes, but this is for sure the most safely way to install from scratch as i told before.

---------- Post added at 16:21 ---------- Previous post was at 16:11 ----------

Hi,

this is known error in twrp, and thats why i said, please always use philz recovery to format all partitions /system /data /cache /preload.

format /sdcard0 with vfat, thats default and safest mode..

--

You did everything right :)

..but really strange why you still have problems..my suppose is that your pit file is faulty somehow, so i would repit as described above with another pit file.

The message after finish install cm12.1 with 0.2000 and ..unconditionally is not the problem!