yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] the.gangster:
I never repitted my phone and my internal SD is Fat32, too.
[Galaxy S II Original Android Development] Typhoon_Master:
Hm. No matter what i do, i cant get fixed it, despite the fact that it worked once. I cant be so supid ...

I now tried ext4, exFat, Fat32, NTFS, f2fs, .. None worked. Do i need a specific partition table? (msdos (mbr), gpt, or anything else?)

formatted everything with gparted from ubuntu
[Galaxy S II Original Android Development] 水島芝:
Hello, I'm jusk asking :)

Will Android M or CM13 compatible in this device?
[Galaxy S II Original Android Development] Dr AM:
Unfortunately Windows :D

---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------

Android M final version is not even released yet -_-
[Galaxy S II Original Android Development] Typhoon_Master:
For everybody struggeling with sd-card formatting not working, i got a permanent solution for myself.

As formatting in windows/ubuntu did just work once (god knows why), i found out that TWRP is in fact able to format your sdcard under

"Wipe" ---> "Advanced Wipe" ---> now select "emmc" ---> "Repair or Change file System" ---> "Change File System" ---> choose your favourit ---> do the swipe! :)

thank you for all

hope i can help anyone

//edit (two days later)

as it turned out you must choose FAT.

i tried using ext4 stuck struggeling with read-only filesystem in cm12
[Galaxy S II Original Android Development] Spyr0s:
it will never happen
[Galaxy S II Original Android Development] kostelo:
Never say never my friend. ;) But please no more off topic posts.
[Galaxy S II Original Android Development] silentcontrole:
when CMUPDATER download a zip file where did he save it ??
[Galaxy S II Original Android Development] buffer overflow:
sdcard0>cmupdater
[Galaxy S II Original Android Development] suprvenu:
Bugs or not?

Video camera app freezes as soon as started.

Wifi tethering not working even though it sets up fine..

Are these bugs or is it just my Phone?:(
[Galaxy S II Original Android Development] RkX_Dyable:
Boot screen

Good Night everyone!

I'm very sad today, since months that I use the Rom's by LA, I've never had a problem.

This afternoon, my SII, was very slowly, and rebooted, two times, Without I don't know why...

When I take my smartphone, from the pocket, I noticed, that a reboot, happened again, but this time, the SII was Stuck in the boot logo. The phone was very hot, but I still waited, a few more minutes, and still boot logo, I've pressed the power button for 10 seconds, and the phone rebooted, but stay the same way, I cant enter in recovery mode...

I don't know what happened :(

Somebody please can help me with this?

Thanks!
[Galaxy S II Original Android Development] suprvenu:
Vol down +home+ power on might get you to recovery....
[Galaxy S II Original Android Development] 水島芝:
That's how into download mode dude

Vol up + home button + power to get into recovery
[Galaxy S II Original Android Development] daniu:
Hi

First I'd remove the battery 4 a while.

Regards
[Galaxy S II Original Android Development] Barry Mad:
@Lysergic Acid = Massive Common Sense re Cm12.1 + TWRP2870signed

[MENTION=6159291]Lysergic Acid[/MENTION]

I cannot Thank +1 You enough for your release/post of stock CM 12.1 kernel + TWRP 2.8.7.0 Signed zip!

To give back to your Loyal user the Right to Backup their Data easily.

Is Just Commonsense Sense Plus+ respect back to their Users.

Without getting Too Political. Are you listening CM!

Happy Birthday to me = 100 XDA posts = Honor of being a Senior Member.

Regards/Respect to you.

bmad.
[Galaxy S II Original Android Development] Mikros:
Hello all,

I was monitoring the thread for ROM issues and it's progress for a long time and now, i am planning to upgrade from cm11 nightly on the next days. Can someone please provide me with the instructions as i have lost the whole procedure. Also, the issue with Google apps after each upgrade, has been fixed?

Thanks
[Galaxy S II Original Android Development] buffer overflow:
Copy/Paste from OP

Boot into Recovery
Wipe all your data
Flash CM-12.1-XXXXXXXX-NIGHTLY-i9100.zip from sdcard
(Optional)Flash Google Apps.zip from sdcard
Reboot
[Galaxy S II Original Android Development] Mikros:
Thanks for your reply.

I knew that was there, but some people are mentioning problems. Eg. with the default kernel after the installation, problem with CM Gapps etc. That's why i posted my question. I want detailed instructions to avoid those issues
[Galaxy S II Original Android Development] buffer overflow:
Well, firstly i don"t use CM gapps, just PA gapps and until now i did not have issues. tk_gapps-modular-pico(uni)-5.1.1-20150802-signed.zip :) UPDATE:....and i use this kernel with TWRP recovery. stock_kernel_twrp-signed ;)
[Galaxy S II Original Android Development] gpvecchi:
Clean install yesterday, now I can't install FB with error 504. :eek:
[Galaxy S II Original Android Development] xt23:
Hey,

tried to install ROM now multiple times with different approaches and always running into the same problem: I'm unable to reboot.

Straight after installation, when I boot it the first time, everything seems to work just fine. I can set up my accounts, make calls, install apps etc. Nothing suspicious, everything seems to run nice and smoothly, like it should.

However, as soon as I shut it down / reboot, I'm stuck with Samsung Logo and yellow triangle. I gave it 15 minutes to settle, but nothing happens. It just stays at this point and gets hot.

Luckily it's still possible to access download mode or recovery via the usual volume up/down + home + power. So I can reset/flash and start all over again. Afterwards it's the same problem again. I can boot it once and set up everything just fine, but as soon as I want to reboot, I'm stuck withe the yellow triangle once again. :(

Here is, what I have done (most of the times):

1. Enter download mode, fire up Odin 1.85 (later tried also 3.09 - result seems to be the same)

2. Insert PIT with 1 GB System, 6 GB Data and 512 MB Preload from here

3. Insert PhilZ-cwm6-XWMS3-FOP-5.15.9.tar.md5 as PDA from here

4. Make sure that "Re-Partition" is checked and Press Start

5. Boot into CWM Recovery, format everything that is not external sd

6. Install cm-12.1-20150808-NIGHTLY-i9100.zip from external sd card

7. reboot

Not sure if I'm doing something wrong or it's a bug. Any help would be greatly appreciated. :)
[Galaxy S II Original Android Development] daniu:
Hi

Did you try to remove the battery for a while?

My phone does not want to enter recovery mode sometimes. It seems like it thinks the battery is depleted even there are more than 50%.

Removing the battery for a while or just waiting with plugged in charged usually helps.

Regards
[Galaxy S II Original Android Development] RkX_Dyable:
I've already tryed that, the only thing I can do is enter in download mode...

PS: The phone don't charge too... :crying: stuk in the battery logo, with that little wheel.

Thanks!
[Galaxy S II Original Android Development] xt23:
Thanks for this suggestion. I tried that, but unfortunately that does not help.

Since you have problems entering recovery mode, this seems to be different problem anyway. I entered recovery approximately about 20 times during the last hours, till battery got down to 20 % (now paused experimenting and waiting for charge due to power failure safety reasons) and never experienced any issue with it so far.
[Galaxy S II Original Android Development] spanitzer:
No nigthly today?

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] LeBourrin:
Ah no, the Cyanogenmod compilator is crashed again! http://jenkins.cyanogenmod.com/view/All/builds
[Galaxy S II Original Android Development] iamnotkurtcobain:
Again :/

Happens a lot lately.
[Galaxy S II Original Android Development] xt23:
Small update on my problem: I have now installed Lysergic Acid's last unofficial Build (06/17). And guess what? It's working! I'm finally able to reboot without a problem. :victory:

Still no clue, why the official build won't reboot properly on my device and hoping that this problem will be fixed in the future. But at least, now I have a functional CM 12.1 on my S2 to work with, until that problem gets solved. :cool:
[Galaxy S II Original Android Development] Malhavoc Blackdrake:
Clean install with TWRP kernel flashed. PA Gapps. Running flawless since an handful of days, very very nice! :)
[Galaxy S II Original Android Development] Typhoon_Master:
After some time i finaly found out how to do the patitioning and formatting of the internal sd-card in TWRP, im now struggeling with an problem, that the mounted partition is read-only. I cant create files or folders from the phone (on pc it works). Cyanogenmod says it is an read-only filesystem.

Can cm12 handle ext4? Does someonw knows a solution?

Thanks.
[Galaxy S II Original Android Development] Phenomzye:
Really nice ROM, only problem is the one we're all facing, I just lost count of how many times it has resetted today while playing Clash of Clans, no overclocks whatsoever and everything stock, it's a shame having to stick with kitkat because of this :<
[Galaxy S II Original Android Development] p3dboard:
Not sure if you want to try this, but the davlik.vm.heapsize is set to 128m in /system/build.prop on the Galaxy S2 rom. On my Galaxy Tab 7.7, I've been playing with larger sizes like 192m, 256m, 320m (384m seems to be too large for the amount of free ram on the S2 under lollipop). Even though we are running with ART and not DAVLIK anymore, ART seems to use these values still for Application Ram management from my observations. So it could be that clash of clan's and applications like Chrome are hitting the 128m memory barrier and then closing.

On my Galaxy Tab 7.7, using CM 12.1 (unofficial build) 192m / 256m seems to be ok, 320m is pushing it (but on Omni rom unofficial, 320m seems ok). You can give it a try and see if it makes a difference for clash of clans
[Galaxy S II Original Android Development] lukss12:
Long-press for Menu and Back buttons not working on 07/08, it's a problem i also had on unofficial builds. Also music visualizer not showing on lockscreen with stock or custom player.

---------- Post added at 02:08 AM ---------- Previous post was at 01:17 AM ----------

Try on terminal

# mount -o rw, remount /storage/sdcard0

If it works just make a script on boot
[Galaxy S II Original Android Development] Typhoon_Master:
Thank you for the hint. I'll try it :)
[Galaxy S II Original Android Development] daniu:
Hi,

I tried 240 this morning (obviously forgot that you wrote: 256 - while wondering that it should be 240 and not 256 ... - is that a problem?) and got a crash something like 1hr later listening to podcasts for less than 20min ...

BTW: editing that file is not too easy: ES-Explorer can do it by using the ES-Explorer file editor.

Now I am trying 320m and will report as soon as I got a reboot. However listing to podcasts has to wait a while now - so chances for reboots are lower.

regards
[Galaxy S II Original Android Development] lukss12:
It actually is -o rw,remount without the space between the "," and "remount" it should not be necessary to put "-t type". Looking mount points on my phone I see sdcard0 really mounted at

/mnt/media_rw/sdcard0 (try it too)

Sorry it's 4 in the morning here and I start putting spaces where they should not be haha
[Galaxy S II Original Android Development] daniu:
Hi,

well - that did not take as long as expected. Without using the phone I got a reboot with 320m

I will go back to stock value since I don't think that changing this value changes anything ...

regards
[Galaxy S II Original Android Development] Typhoon_Master:
Did you see i edited my post? No matter, i will delete it and post it in this post :)

Command was executed without response, so i assume it was processed successfully.

But no luck for today, i still cant create files or folders on it :(

root@GT-I9100:/storage/sdcard0 # mount -o rw,remount /storage/sdcard0
root@GT-I9100:/storage/sdcard0 #root@GT-I9100:/sdcard # mkdir test
mkdir failed for test, Read-only file system

But this could be interesting, when i do only mount, it comse to this output:

(...)

/dev/block/vold/259:3 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:s
dcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0

(...)

/dev/fuse /storage/sdcard0 fuse rw,relatime,user_id=1023,group_id=1023,default_p
ermissions,allow_other 0 0

seeing that /mnt/media_rw/sdcard0 is with ro option, meaning read-only.

when i remount this location, it gives me this:

root@GT-I9100:/storage/sdcard0 # mount -o rw,remount /mnt/media_rw/sdcard0
mount: Read-only file system

i realy dont know. mount is also showing other mounts (/data, /cache, /system/, ...) which are mounted ext4 partition with rw option, why is it not possible for sdcard?
[Galaxy S II Original Android Development] lukss12:
Sorry I didn't see your comment was edited :o

Try downloading https://play.google.com/store/apps/details?id=me.kuder.diskinfo and look for a difference between /cache and your /sdcard. May be it could help.

EDIT: did you "su" before mount? I think if you didn't it would response with permission denied...but who knows?

Other ideas? Hummm... Do

#su

#mount -o rw,remount /system (also ext4)
[Galaxy S II Original Android Development] Lanchon:
(emphasis added)

hey, just wanted to chip in and say that this is not true if trim is done correctly.

as detailed in my trim-enable howto, you have to:

-have all the kernel patches to make trim safe on all emmc variants (you already have this in your cm-12 kernel, i personally checked it).

-enable trim issuing in the kernel

-NOT ENABLE trim issuing in userland file system tools (for example, the ones that end up in the recovery).

this is how my kernel/recovery images are built, meaning that:

-if my kernel is in control, a bricking command can never be issued.

-if the user runs my file system tools under the control of a foreign kernel AND that kernel supports trim commands AND that kernel does not have all the necessary patches to make trim safe on all emmcs, then nothing bad will happen because my userland tools never issue trims.

this is why recoveries bundled with my trim kernels do not trim partitions after formatting them, a feature that i would love... but safety goes first.

(the plot thickens if you think that userland tools can be made to trim safely under unsafe kernels by using insecure wipe instead of secure wipe. this might be true but we will never know: hard data is missing for "trim bug"; so we don't do it.)

in conclusion:

-no part of a well done kernel/recovery image can cause a brick under any circumstance, including while using other unsafe kernels.

-file system tools never pose a risk because they should never be modify to support trim.

-the trim kernel itself never poses a risk because it is either running and in charge (and thus completely safe), or its modifications are a non-issue because its code can never be executed under the control of another kernel.
[Galaxy S II Original Android Development] Typhoon_Master:
Yes, i su'ed the session before trying commands.

remounting /system processes also without output, so it works like a charm, but has no effect on my sdcard.

I loaded the app, and took some "screen shots", sorry i couldn't do real ones because of missing write permissions on sd-card :P

first two are from /cache, third and fourth from /sdcard

I wonder that on cache partition it says "Partition Type: SD/MMC card" and on sdcard it says "Partition Type: BLKEXT", but i dont know if that matters.

despite the fact, that the app shows sdcard as Read/Write i changed dir to every mountpoint, and tried to create a folder, but always doesn't work.

root@GT-I9100:/storage/sdcard0 # mkdir test
mkdir failed for test, Read-only file system

i now checked dmesg after trying remount:

<2>[ 2413.073643] c0 EXT4-fs error (device mmcblk0p11): ext4_remount:4335: Abort forced by user
[Galaxy S II Original Android Development] Lanchon:
all your troubles are because you didnt follow instructions

flash my latest cm11 trim kernel

then optionally repartition now. 3GB is NOT A GOOD IDEA. you should use 4 or 6 since you want a minimum of 1 or 2 GB free in this partition at all times. you can use my 6GB PIT, and also my linux script if u use linux. (see i9100 trim kernel OP)

then follow instruction spew out by the script:

echo "Reboot into recovery."

echo "Format /system, /cache, /data and /storage/sdcard0."

echo "Format /preload if possible."

echo "Mount USB storage, copy files to flash, eject media, unmount USB storage."

echo "Flash away."

then heed the note in said OP:

UPDATE: due to a bug in CM, the recovery is unable to format the /preload partition. formatting is needed after repartitioning. to manually format, open a terminal on the phone and type: su -c "mkfs.ext2 /dev/block/platform/dw_mmc/by-name/HIDDEN" or from the PC via adb: adb shell su -c "mkfs.ext2 /dev/block/platform/dw_mmc/by-name/HIDDEN"

or still in recovery via adb from PC, this should work:

adb shell mkfs.ext2 /dev/block/platform/dw_mmc/by-name/HIDDEN

you NEED to format preload to boot cm12.1.

you can also trim while you are in recovery, see OP.

EDIT: and you most certainly DO NOT want an ext4 fs in internal sdcard. make sure you use FAT.
[Galaxy S II Original Android Development] Typhoon_Master:
Uhhm... sorry, my problem is NOT about CM12 not booting or anything. I solved the problem with the unformatted /preload already.

... and 3GB system is a good go for me, since i do not have a lots of apps ---> 1GB free space always available

This is about internal sd-card is not writeable! ;)

and why do i not want ext4 for sdcard? it is a good filesystem.
[Galaxy S II Original Android Development] lukss12:
After digging a bit i found that sdcard0 is being mounted by vold using "/fstab.smdk4210" by

#mount all /fstab.smdk4210 on init script.

The thing is in fstab file the options are set "auto" so if vold is using "ro" option in automatic mode, here is the problem. I cant tell you if modifing fstab will result on succes or not but you can try if you want just look for "mmc0" just after -vold managed devices- banner.
[Galaxy S II Original Android Development] Lanchon:
yes, because you after partitioning you formatted it with the wrong tool (a PC), making a nested partition table within the partition (that's why you couldn't mount it from the phone but could from the PC), and finally formatted it in the wrong FS. and you are still stuck with 3GB /data so IMHO opinion you should start over.

you dont want an ext4 fs on sdcard because android cannot work correctly with such a partition. you need to use fat. if you want to use ext4 you need to mount a fuse filesystem over it (just like android 4.x did) which requires you building you own android variant.

or else it will NEVER work correctly, thats why google had to make that silly fuse filesystem in the first place and include it in /data/media devices in android 4.
[Galaxy S II Original Android Development] Typhoon_Master:
i soon found out, that formatting with pc was a bad idea:

what i do not understand is, why is 3GB not enough? i thought 3GB space for system and app-data would be enough since photos, and videos are stored on sd-card.

hm, its bad that we have to use fat cause of various reasons (slow, 4GB limit, ...)

as i formatted ext4, android automatically mounted such fuse partition over sd-card as you can see on my mount output i posted also on previous posts. anyway it didn't work:

/dev/block/vold/259:3 /mnt/media_rw/sdcard0 ext4 ro,dirsync,context=u:object_r:sdcard_posix:s0,nosuid,nodev,noexec,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

however, i formatted emmc with FAT now, and its finally writeable. Thank You!

Also thank you lukss12, for investigating your time helping me. :)
[Galaxy S II Original Android Development] lukss12:
I had my UMS partition formatted with vfat and from mount info i can see it has been managed by vold and fuse is used for /storage/sdcard0 ... So i don't really understand why it can't be ext4 instead of vfat?
[Galaxy S II Original Android Development] Lanchon:
you can make ext4 work, but it will never work correctly.

apps expect fat semantics, including no permissions and case insensitive file names. all sorts of failures can ensue. app writes file in one case, read it in another, works on all phones... but on yours apps force closes. you want 5GB files or a phone that works?

free space on /data? because its the only big and trimmable partition, since fat cant be trimmed. read on ssd overprovisioning for your answer. choose: either free space on /data or a slow as hell phone. if you need more sdcard just add an sdcard, dont make /data small.
[Galaxy S II Original Android Development] mysteryno46:
Issues flashing Gapps

I flashed the Rom.zip and then when flashing Gapps, the flashing failed(I tried Modular-Micro gapps). So, I thought the file might have got corrupted as I transfer it from another phone to my S2, then while rebooting to system it ask me to Fix-recovery.zip and I selected Yes.

Now it shows me the CM12 Recovery, instead of CWM. And it has option of Apply Update.

Now, I cannot switch back to CWM 6.0.4.7, Plus the .tar download source of CWM 6.0.4.7 doesn't work if I want to try flashing cwm via odin.

Any solutions anyone?
[Galaxy S II Original Android Development] Lanchon:
you need free space and trim of course. use my trim kernel. with 1GB system and 6GB data (my PIT) you can probably get away with trimming once and afterwards use official kernel from then on and still have a fast phone

---------- Post added at 06:09 AM ---------- Previous post was at 06:09 AM ----------

yes, read this thread! search for "signed"
[Galaxy S II Original Android Development] Typhoon_Master:
had to be said.

yes that makes sense. i want a phone that works and 5GB files. ;)

no seriously, it would be cool, if you could use a fast filesystem with no limits.

i got now 3 GB on /data. 1,5GB left free space with a fully configured phone. phone is still quite fast, so i think its enough?

my phone is now working and quite fast. flashing trim kernel will it make even faster?
[Galaxy S II Original Android Development] Lartza:
I wiped everything, flashed 20150810 NIGHTLY and TK Gapps pico, 3G is still not working.

Modem XXMS4, attached is logcat -b radio that I don't know how to read properly
[Galaxy S II Original Android Development] daniu:
Hi

Since you are discussing free space: I got between 70 and 700mb free space on /data with 4GB total space. If I understand correctly I should update to 5GB or remove apps until free space is always around 1GB. Which is not too nice because it would mean that most of the time it is >1.5GB ...

How about free space on /system? I got 512mb there and around 70mb free space. Should I change to 1gb?

Are there PIT-files with half gb - in this case: 4.5gb data?

Regards
[Galaxy S II Original Android Development] Lanchon:
EDIT: no, those 1.5GB will quickly turn into 0.5GB or less as you use the phone.

yes it will. and you need to trim as per the OP.

---------- Post added at 02:46 PM ---------- Previous post was at 02:40 PM ----------

yes you need more free space. and you need to regularly trim that space. but no, dont use 4.5 or 5, use 6GB! what is the problem? the internal memory should be used to run the computer, not store movies! if you need more sdcard, add one.
[Galaxy S II Original Android Development] alienflorina:
20150807

Hello,

Has anyone else been experiencing major slow downs on 20150807 nightly?

Can't find the source of the problem, it slows down in random times making the rom a pain to use.

On the bright side since I add updated to 20150807 I had no reboot so far.

Best regards
[Galaxy S II Original Android Development] the.gangster:
This is only valid for his (@daniu) first question, isn't it?

As I understood so far, there is no advantage in having greater /system partition, as long as it fits for the desired ROM+GApps(+Xposed if needed).

But any free space there would be wasted, wouldn't it?