yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] daniu:
Hi,

well - honestly: at the moment I don't miss anything that was removed with mini (didn't even realize ...) I still dislike the way that is done because I expect some features to be removed that I'd miss in the future (plus: I don't have a glue what e. g. screencast is and might want to use it someday ...).

I do miss trim though and I would love to see you retire from the unnnecessary job to compile extra kernels for us ... And I cannot really follow the logic: CM is not stock and it is potentially dangerous (not even need to limit that to nightlys) - so if the phone gets bricked by that software: nobody can be blamed but the person who installed CM or maybe ... fortune?

NIGHTLYS are compiled automatically - how ignorant can you be to not accept that this might break your phone?

regards
[Galaxy S II Android Development] polter_geist:
Hi,

after 20160301 build with Trebuchet launcher using cosy grid size all icons looks distorted. Is it supposed to be like this?
[Galaxy S II Android Development] tiescher:
Login screen needs 5-10 sec to get displayed

Hi gents.

I installed CM13 on my old i9100 and be happy that this runs fine.

Anyway, I figured out that the login screen (PIN verification) needs around 5-10 seconds to get displayed.

Does anybody else have this issue with CM13?
[Galaxy S II Android Development] DRKMTTR:
i9100 01march build

eMMC Chip: Brickbug VYL00M 0x19

28.02 trim kernel, ext4 fs

antutu 6.0.1 - 16749

after trimming
[Galaxy S II Android Development] Lysergic Acid:
TRIM

Very well, since there seems to be lot of demand for trim, I'll be merging [MENTION=4141005]Lanchon[/MENTION] patches on the official CM kernel. I think if anyone complain about it, he is able to provide me enough documentation on why trim is needed.

If something bad out of it happens, I'll kill all of you who asked for it ( and revert the patch :) )

That's all folks
[Galaxy S II Android Development] Acid0057:
[MENTION=5246166]lysergicacid[/MENTION] AWESOME news.
[Galaxy S II Android Development] Lanchon:
YEAHHHH THANKS!!! :)

for the record: merged on CM 12.1 and 13.0
[Galaxy S II Android Development] makix13:
LA you are the Master, I'll offer my life in case someone lost his S2 because trim support[emoji122] [emoji122] [emoji23] [emoji23]

S2 Cyanogenmod 5.1.1 [official nightly] - Lanchon's kernel isorec - arnab isorec twrp - Xposed [official framework] - Viper4Android
[Galaxy S II Android Development] laserkater:
Awesome news!

i9100 with CM13, rock stable, my daily driver. I pay my respects.
[Galaxy S II Android Development] Farmut83:
please tell me where can I find the inclusion of function "mute the sound an incoming call by turning over the phone"
[Galaxy S II Android Development] the.gangster:
[MENTION=535343]all[/MENTION]

Although I might have slightly exaggerated with my prediction of thousands celebrating him (LA)...

...nevertheless now everybody should klick his Thank-Button.

So come on, let's push his http://xdaforums.com/showthread.php?p=65620785post to a new record. :D
[Galaxy S II Android Development] alienflorina:
Is there a snapshot coming anyone soon? Is the ROM stable enough for that?
[Galaxy S II Android Development] the.gangster:
[MENTION=6752448]alienflorina[/MENTION]

I honestly hope there is no snapshot coming anyone soon (although the ROM would be stable enough), as

then to all people that are currently running an CM12.1-Snapshot build, the CM13 snapshot would be offered

50% of them would update without "realizing" it was a new major version that was offered (or at least later pretend that)

50% of those would be surprised that GApps (or other stuff) no longer work

even the other half, meaning those who remember that a major version update needs reinstallation of GApps with matching new version, would fail to do so with Error #70

This would mean, there would be another rush of panicky frightened users not willing to read about all the problems and their solutions served to those, that already experienced all that on the Nightly-branch already. It took almost 2000 posts to get them back on track.

And as there was some progress recently or at least an approach on how to deal with the small stock system partition size by switching to common_mini_phone builds, I would hope, that a working solution would be developed beforehand.

On the other hand, if a snapshots came out now and once all following 2000 posts would have been handled, we could also return to common_full_phone builds again, as then even the last device would have been resized its stock system partition to e.g. 1GB.

A working solution to resize without dataloss already exists, but this would also currently need to be explained to all those ending up here as it also has prerequisites (btw: it's a pitty that thread got closed as now users can no longer report their experiences there).

So IMHO an intelligent ROM-default-handling would make sense before taking the step to a Snapshot release. There are already ideas of how to do it.

Not to mention, that a total redesign of CMUpdater would make sense, so that it doesn't manage major version updates as any other update, but to inform a user about the additional steps that have to be taken if someone wants to switch to it.

Wow, that was a lot of text now for such a short question. Sorry for that!

:)
[Galaxy S II Android Development] sajidunia:
WOW!!!! I back you up....:good:
[Galaxy S II Android Development] Syaani:
Build with TRIM is now online.
[Galaxy S II Android Development] mattitch:
Insufficient space for Gapps

Hi there

'First time caller long time listener'

First of all, respect due for keeping the i9100 alive in the CM updates.

I have installed 13 nightly build from yesterday and the install itself is perfect. The only problem is that my device is telling me I have insufficient space for Gapps. I have the latest Pico version which I believe to be the smallest. I had 12.1 installed and gapps installed fine after flashing 6gb PIT file through odin.. Can anyone help???
[Galaxy S II Android Development] the.divergent:
Visit this theard.

http://xdaforums.com/showthread.php?t=3311747

Regards
[Galaxy S II Android Development] andyhers:
you only repit the data partition to 6gb, not the system partition.

use the PIT91001GB_6GB instead of PIT9100_6GB
[Galaxy S II Android Development] tutsipoppy:
I just flashed the latest nightly 20160303 and noticed that the launcher icons on the home screen have considerably shrunk down, while the icons inside the drawer are normal sized as they should be as per the DPI.
[Galaxy S II Android Development] opaco23:
You could try to dial *#*#4636#*#* then select Phone Information.

(I don't have cm13 yet on my s2, but it works in other phones with cm.)
[Galaxy S II Android Development] andyhers:
correct me if i'm wrong,

but it seems since the cm switch our phone to "mini-phone", there are more bugs from previous build.

Those bugs didn't exist in previous build, but they occur in the newer build.

If it's true, i guess it's better to *cancel* the mini-phone, and return to standard phone instead. if it's a matter of 512MB system partition, in my opinion, if we keep limiting ourself to that boundary, isn't it means we limitin ourself for "upgrades" in the future ?

If somehow the next cm14, cm15 and so on, and still supporting i9100, wouldn't it gonna pass beyond 512MB limit ?

I mean it's not the hardware limitiation we're talking about here.

BTW, i'm still staying at 20160210 build since it seems better for me, with "acceptable" bugs for me.

Cheers
[Galaxy S II Android Development] pravingasva:
This is what everyone is saying who have "successfully" re-pitted their devices; and those who have not done so are complaining about the same! Hence, this is a debatable issue. :rolleyes:

And as LA said, he cannot satisfy everyone, so he has to take a stand as early as possible!!
[Galaxy S II Android Development] andyhers:
true, but i just think about the future. it may not feasible to keep the growing platform below limit.

just my 2 cents :fingers-crossed:
[Galaxy S II Android Development] SAMDestroy:
sorry to say thats but for me the OTA update from cm-13.0-20160226-NIGHTLY-i9100.zip to cm-13.0-20160303-NIGHTLY-i9100.zip gets my device into a bootloop
[Galaxy S II Android Development] Lysergic Acid:
For now I have to make stuff working (mostly RIL atm) before figuring out standby issues or fcs. In my case the device is burning after a couple minutes on CM13, so I just boot, log what I need, and power off :cyclops:
[Galaxy S II Android Development] rphlfjrd:
I understand. Those FCS are nothing compared to the RIL.

That's weird, mine never gets to burning level. Maybe sometimes but not often. I even managed to play a game for while. (Cytus to be exact.)

If you need logs, tell me what you need (and how to get em).
[Galaxy S II Android Development] DevisG79:
@LA: I hope this is ok?

I have made TWRP stock kernel for Odin to get back or downgrade. It´s not possible to flash zips in stock Recovery of cm13 yet.
[Galaxy S II Android Development] tulipes3:
Hi all,

I flash this rom cm13, but missing Gapps file how flashback,
[Galaxy S II Android Development] DevisG79:
Try link at the begin of the threat or OpenGapps.org. If you have flashed cm13 and you want to downgrade then via odin
[Galaxy S II Android Development] tulipes3:
thanks for the reply,

but Odin does not work,

is that there no other way?

Thanks;
[Galaxy S II Android Development] pippone121263:
Try to change odin version, I use odin3-v3.07 or odin3-v1.85, both work fine for me. If no luck try change USB cable and USB port. (Make sure to have the right driver, install samsung kies in the case)

If no luck again format everything, normally I format everything (but no PIT) before flash new ROM.

Did you make a backup? In this case a factory reset and a restore will work fine.

Hope it can help
[Galaxy S II Android Development] tulipes3:
hi,

thank you for answering,

Could You explain me

how did you do? and where I find ROM.TAR

Thanks;
[Galaxy S II Android Development] pippone121263:
you can find the rom in sammobile, download it and put it in odin PDA
[Galaxy S II Android Development] rINanDO:
Hi everyone,

I just spotted a fix which makes our RIL finally stop crashing! I just tested this on my i9100 and it works!

https://github.com/CyanogenMod/andr...mmit/53602ffde5527c476a1d7d39da12ecd7f58917f4

http://review.cyanogenmod.org/#/c/122665/
[Galaxy S II Android Development] tulipes3:
Hi pippone121263

Grazie,

Merci,

thank you,
[Galaxy S II Android Development] Ponsel:
Does this fix work for 12.1 too?
[Galaxy S II Android Development] lukss12:
Did you have ril crashes on 12.1?
[Galaxy S II Android Development] Maximko_O <3 wonder:
Hi guys, what does not work on the Alpha 4?
[Galaxy S II Android Development] rINanDO:
I don't think so. You have RIL issues in 12.1?

This fix only disables (using a flag in your device tree) merged code in cm 13.0 which caused old blobs to crash. It was never merged in cm12.1.
[Galaxy S II Android Development] the.gangster:
After a short test of alpha 2 on my still productive S2 I decided to buy a second one as backup phone and for easier testing.

Now that I got it my first try was installing alpha 4. What a big step compared to alpha 2!

Congrats to LA for the progress you made.

Just one thing to mention here (apart from the recovery that doesn't allow flashing) is, that obviously even the current pico OpenGApps is too big already to fit into a stock system partition. At least without modification.

On a stock partition size I have 69.6MB free after flashing alpha 4.
[Galaxy S II Android Development] pippone121263:
You can change your parition to make it bigger I have a 3GB, you can find the PIT file to do it here in XDA...

hope it can help
[Galaxy S II Android Development] the.gangster:
[MENTION=3823153]pippone121263[/MENTION]

Yes I know, as I repitted my first S2 already long time ago.

But as I tried alpha on the second one now, I just wanted to share that information, as I had not read that here before.

It wasn't meant to be a question. But thank you anyway.
[Galaxy S II Android Development] the.gangster:
With Alpha4 I cannot see anything like that. It ran for two days without any issues. Meanwhile it rebooted here and then while playing around with some settings.

After last charging I put it to airplane mode and still there is nothing that burns the device or drains the battery. After more than 24hours it reports 99% deep sleep and predicts unbelievable 16 more days of uptime.
[Galaxy S II Android Development] Andrea900:
With no gapps (and Play Services) installed? Trust this prediction! :D :D :D
[Galaxy S II Android Development] ivanmara:
Hello. How can i format sdcard0 to f2fs file system ? /data and /cache i formated with commands:

mkfs.f2fs -l f2fs /dev/block/mmcblk0p7 (for /cache)

mkfs.f2fs -l f2fs /dev/block/mmcblk0p10 (for /data)

What command for sdcard0?
[Galaxy S II Android Development] Kevin3014:
Assuming that you've got TWRP (isorec)

1. Boot into TWRP recovery

2. Wipe /system, /data and /cache

3. Flash cm13 and gapps like you usually do
[Galaxy S II Android Development] SAMDestroy:
i would wait with this.

like i said on the post above yours. im on bootloop and /data + /cache was on f2fs.

i did a backup of the "faulty", just changed the partitions back to ext4, restored the "faulty" backup what causing the bootloop,booted system,i got one reboot with it (maybe the boot routine was fixing something) and now my device is doing the optimizing apps process.

i would like to change it to f2fs but for now it is just buggy here.

EDIT: my device is fully working again and trimming ext4 is working like expected

yes i do know how to start from scratch :)
[Galaxy S II Android Development] ManuelR9:
Hi guys! I have a S2 with 1GB to system and 8GB to DATA with recovery 2.8.7.0 of Lanchon and CM13 nightly running of 12-02-16, all using this great tutorial and everything perfect. What I have noticed is that the wifi connects and disconnects constantly router from my home , in CM 12.1 never occurred this. I have 2 questions:

1- Can I update the following nightlys OTA without errors bootloop?

2- I saw that Lanchon has released a TRIM recovery, what is it? Bring notifications with LEDs lighting as kernel APOLLO?

Many thanks cracks
[Galaxy S II Android Development] SAMDestroy:
im sure in most situations you wont get a bootloop with OTA updates.

TRIM is already included in current nightly so you dont need to install Lanchons TRIM Kernel. Read and get TRIMMER from the market to do a manual trim of your storage. it should speed up read/write.
[Galaxy S II Android Development] hansmaa:
Just OTA upgraded from cm-13.0-20160227-NIGHTLY-i9100.zip without a hitch.

Forgot to say that I'm using f2fs on /data & /cache since 0226 or so.
[Galaxy S II Android Development] SAMDestroy:
well im not sure what was causing the bootloop on my device i just wrote what i did to solve it.

maybe it was because of how i converted from ext4 to f2fs.

how exactly was you doing it?
[Galaxy S II Android Development] hansmaa:
Ehh... The usual way I guess....

First I made a backup in TWRP,

then ADB into TWRP and reformat /data & /cache

then restore backup using rm -rf instead of reformat.
[Galaxy S II Android Development] n3m3sis:
I am sticking with 20160223 until the updates go back to full phone. I have had root problems with every update since 20160226 (not including the two with the call bug). The one I'm using now with Lanchons latest trim kernel, isorec recovery, Lanchon's trimmer app, re-pit using PIT91001GB_6GB and cputuner profiles to regulate my battery use. Phone is running sweet as a nut! Unless the mini-phone commit is retracted, I guess this is where my experimenting with cm13 stops :(
[Galaxy S II Android Development] ivanmara:
I convert sdcard0, cache, data file system to f2fs and everything work great and faster! No any bootloop.

I used command in TWRP:

mkfs.f2fs -l f2fs /dev/block/mmcblk0p11

After that, reboot system and in Disk Info see that sdcard0 is f2fs. See screenshot :)

p.s.: use cm13 20160302 night build.
[Galaxy S II Android Development] hurda:
Here's a comparison of files in 0223 (pre-mini) and 0224 (post-mini).

File-changes at the top, file omissions at the bottom:

--- /dev/fd/63	2016-03-03 15:29:55.170949049 +0100
+++ /dev/fd/62	2016-03-03 15:29:55.174949096 +0100
@@ -1,8 +1,8 @@
-456413184	.
+419930112	.
-159834112	./app
+127578112	./app
-48189440	./app/LatinIME
-48177152	./app/LatinIME/LatinIME.apk
+17391616	./app/LatinIME
+17379328	./app/LatinIME/LatinIME.apk
-8945664	./app/messaging
-8941568	./app/messaging/messaging.apk
+8876032	./app/messaging
+8871936	./app/messaging/messaging.apk
-10186752	./bin
+9895936	./bin
-4317184	./etc
+4313088	./etc
-12288	./etc/CHANGES.txt
+16384	./etc/CHANGES.txt
-176128	./etc/NOTICE.html.gz
+172032	./etc/NOTICE.html.gz
-76599296	./lib
+74657792	./lib
-62947328	./priv-app
+62861312	./priv-app
-6144000	./xbin
+4239360	./xbin

-884736	./app/PhotoPhase
-880640	./app/PhotoPhase/PhotoPhase.apk
-503808	./app/PhotoTable
-499712	./app/PhotoTable/PhotoTable.apk
-290816	./bin/curl
-4096	./etc/vimrc
-1941504	./lib/lib7z.so
-86016	./priv-app/Screencast
-81920	./priv-app/Screencast/Screencast.apk
-471040	./xbin/7z
-114688	./xbin/bzip2
-163840	./xbin/unrar
-155648	./xbin/unzip
-827392	./xbin/vim
-8192	./xbin/wget
-163840	./xbin/zip

http://pastebin.com/vXwGNzum

Most notable change is LatinIME due to omitting a lot of dictionaries (bg cs da el en_au fi hr hu iw ka lb nb nl pt_pt sv uk).

Also interesting that most packages and audio-files mentioned in common_full*.mk and cm_audio.mk, which are not listed in common.mk or common_mini_phone.mk, are still in the ROM. :confused:
[Galaxy S II Android Development] Splash_6:
Gapps don't work

hi,

thanks for being one step ahead again, i'm really glad with with marshmallow, i like it so thanks

the only problem i'm having right now is the gapps, cause the avaiable version doesn't work in my phone :(

Can you help me....

Thanks
[Galaxy S II Android Development] SAMDestroy:
i was doing the same :-/
[Galaxy S II Android Development] the.divergent:
Plese read OP and first few posts.

Regards
[Galaxy S II Android Development] Kevin3014:
Read this. Good luck!

http://xdaforums.com/galaxy-s2/development-derivatives/guide-want-to-update-to-cm13-read-t3313978
[Galaxy S II Android Development] winone1208:
Trimmed only /system? I format /cache and TRIM on trimmer and see this

I have in /data and /cache f2fs

cm-13.0-20160303-NIGHTLY-i9100.zip
[Galaxy S II Android Development] SAMDestroy:
i had the same with Lanchons TRIM Kernel and cm-13.0-20160226-NIGHTLY-i9100.zip on f2fs.
[Galaxy S II Android Development] Lysergic Acid:
No problem, I reverted the commit: http://review.cyanogenmod.org/#/c/134809.
[Galaxy S II Android Development] stylemessiah:
Im already over all the pages of f2fs talk :)

99.9% of people shouldnt even worry their little heads about it

Why must people go searching for new ways to break things that currently work? :)

Meanwhile still happily on 20160227 build as there hasnt been anything big enough

for me to worry about flashing and then waiting 30 minutes for the dreaded

optimising stage to optimise 100+ apps :) I hate that part! :)
[Galaxy S II Android Development] Acid0057:
Way to go! Thanks for reverting. I'm assuming the next nightly will pick this up then?
[Galaxy S II Android Development] the.gangster:
[MENTION=6159291]Lysergic Acid[/MENTION]

Thank you for reverting the common_mini_phone patch.

BTW: Look at your Thanks-count for the TRIM-merge-post. Looks like it is already no. 1 even in all-time-statistics. :)

So I guess, it wasn't that wrong to merge that.

Let's see, how much thanks the revert to full_phone will get.

What an amazing week for our device. And once more: Thank you so much for keeping it alive!
[Galaxy S II Android Development] ManuelR9:
So friend, you recommend installing the latest nightly because it will bring the ultimate recovery of LANCHON that supports TRIM right? What's this about TRIM? This recovery brings LED notifications? For the apk TRIMMER used?

Why is there so much interest in moving from ext4 to FRT2?

Many thanks Super crack
[Galaxy S II Android Development] a_mp7:
dont install gapps on my device.cm 13 recovery can not install any zip file in apply update and i install isorec recovery but it isnt install gapps please help me.

one of the gapps good for this ROM ??? except open gapps !!!
[Galaxy S II Android Development] Dr.Fix:
Trimmer seems to do nothing on my phone... See attachment.

Of course I'm on latest trim-enabled nightly.
[Galaxy S II Android Development] hurda:
First page, first post, read "IMPORTANT INFORMATIONS", especially the fourth point.
[Galaxy S II Android Development] fireburner-de:
Well I would say, because curiosity is in humans' blood. Without curiosity we would still live on trees or in caves. ;)

And after all, this is a development thread, so devs need some people to test their "inventions"

I would not judge this at all. Just to add, that some people should better stick to the defaults, that are already well tested.

[MENTION=6159291]Lysergic Acid[/MENTION] You are a true hero! i9100 made a giant step within the last days. :highfive: :good:

Thanks for all you have been doing for our device, so far!

CM13 is almost (see below) perfect for a "stable" snapshot now.

I feel good and environmentally responsible with still using an almost 5 year old device and still do not need to fear being overrun by huge security holes due to lacking software support from the manufacturer.

Though all devs are welcome to create solutions for the users that do not want to repit for now. See [MENTION=4141005]Lanchon[/MENTION]s suggestions over here.

This could prevent another 2000 posts when releasing a snapshot. (As people on CM12.1 snapshot would upgrade to CM13, getting another wave of users, like with nightlies)

Maybe it could be possible for the installation procedure to check /system size and if at 512MB create a Gapps config file automatically.

This still would not remove anything, as this config would just come to work, when the user tries to flash GApps. Then it would remove stuff from CM and Gapps and so make CM+pico Gapps fit in the stock partition.

Everyone having 768MB or above in /system would not get that config created at all, and could enjoy the full flavor of CM (like it is now again).

Unfortunately I do know to little in android development to run such a project, but maybe some experienced dev will create such a solution.
[Galaxy S II Android Development] hurda:
[MENTION=7183558]fireburner-de[/MENTION]

IMHO there isn't really a lot of space to save with deleting files. The biggest space-saver in 0224 and newer was the smaller LatinIME-keyboard due to fewer dictionaries, but that would require rebuilding the apk or distributing the different apk-versions in the CM-install-package. The other packages and audio-files supposedly left out from common_mini*.mk are just a couple hundred KiB in size, almost not worth the effort.

The next biggest chunk is webview.apk at 37MiB. If that could be moved to /data, that would be a huge help in meeting the space-requirements for pico-gapps in /system. Isn' t it installed there when updated via Google Play anyway?
[Galaxy S II Android Development] fireburner-de:
[MENTION=6740948]hurda[/MENTION] All GApps components are additionally installed to /data, when they get updated. So they take up space in /system and /data after they got updated. That's why it is suggested to regularly flash the newest GApps package, to free up that space in /data, again.

But I guess that your idea of approach could lead the way.

Maybe all CM Apps that do not require root at all, could be moved to /data within the installation procedure.
[Galaxy S II Android Development] Acid0057:
Or just leave it the way it is and advise partitioning. Lanchon made a safe script that repartition in recovery. Way less chance of bricking your phone and super easy. Gsstudios even made a thread on common cm13 issues to help as well. I say keep the Rom the way it is. No space saving measures.
[Galaxy S II Android Development] pravingasva:
Flash the kernel once again and it will be done! You have to do it after flashing the rom.