yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] n3m3sis:
Stuck on 23/02/2016 nightly - reasons why.

After being one of those that mistakenly upgraded from 12.1 to 13, going through a lot of pain, boot brick and a lot of reading, I finally have my GT-i9100 running on cm 13 nicely. I have to admit, I went through a very steep learning curve when trying to get my phone operational again, however I understood better the reason the developers get so mad sometimes , when the users of the forum don't search and read.

The problem is that all the nightlies since 2016023 I have found to be unusable as a daily driver for one reason or another. 20160224 and 2016025 had the well documented calls bug, fixed in 21060226. However in that nightly, I found that the root in the file manager does not work as I am used to and I had to install root explorer to access the root level folders. It was the same in 20160227 so now I have

gone back to 20160223. I have searched the forum for any others that have reported

the root problem, however I have found no other references.

Like to say mucho thanks to Lanchon & GSStudios who, without their Kernel, recovery, trim and pit files, my phone would still be in a boot loop and I would not of found it so easy to backup and restore my phone. Great work and if I ever meet either of you, you will need to book a cab home :D:D:D
[Galaxy S II Android Development] wyssothmar:
If I try in a file explorer to forgive write access to the external SD, these crashes every time. From an Office app it is equally impossible to save a file on the external SD.

What can I do? I have not yet found a solution.

---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------

Another screenshot.
[Galaxy S II Android Development] fireburner-de:
[MENTION=6159291]Lysergic Acid[/MENTION] and all other devs:

I had a reboot after around 250h of uptime.

Here is my last_kmsg in case it might help someone.
[Galaxy S II Android Development] Spyr0s:
Nice, five pages with TRIM questions that should be in TRIM kernel thread...

p.s. everyone is using trim but cm team, except LA, refuses to merge it. Looks like they suffer from constipation.
[Galaxy S II Android Development] infinion:
anyone got this working Greenify Aggressive Doze?i'm on 27/02/2016 nightly...
[Galaxy S II Android Development] Andrea900:
I've not seen the option yet (v. 2.8.2).
[Galaxy S II Android Development] kuyang:
usb not detected

did someone managed to connect this device to linux arch ?

I tried to lsusb but it doesn't show anything.

I am using latest nightly build
[Galaxy S II Android Development] infinion:
Greenify Donate v2.9 beta 2 ; doze notifications being shown in 20160218-NIGHTLY but not in switch to common_mini_phone builds?!
[Galaxy S II Android Development] flurbi:
f2fs

according to Lanchons post in http://review.cyanogenmod.org/#/c/132900/ the f2fs seems to run in a highly experimantal way.

i had problem with whatsapp in an area with low reception today.

suddenly a chat dissappeared.:confused:

running:

2g mode

clean install yesterday

/data formatted in f2fs

/cache in ext4 (because i got error 255 trying to change it to f2fs with twrp)
[Galaxy S II Android Development] hansmaa:
Same happens to me when I try to run Sygic. And migrating to MM, I did the prescribed factory reset as well as deleting the Sygic folder. Anyone got Sygic working on M?
[Galaxy S II Android Development] Lanchon:
there *might* be potential of data loss right now on F2FS due to the way it is currently implemented. but...

1) only if a freeze or reboot happened! if no freeze or reboot, then your data loss is not something that my comments pointed out as possible. or something for which we would know a fix (other than maybe merging a newer f2fs implementation).

2) arnab is proposing changes that would make f2fs safe enough IMHO, see here:

http://review.cyanogenmod.org/#/c/134440/2

if this is merged i'll withdraw my comments re: f2fs. this might happen soon, so migrated users better just wait it out instead of rolling back to ext4.
[Galaxy S II Android Development] flurbi:
had this chat dissapearing without any reboot or shutdown.

this happened once in 24 hours fresh install cm13 running.

for me, i wouldnt speak of data loss^^

perhaps a tiny problem with cm13 and whatsapp in combination with low reception.

but i'm still testing

downloaded gigs of music with "Googe play music" and had no problems with playing them :)

i rolled back to ext4. just to be sure ;)

without any noticable perfomance increasements, why should someone change ?

is trim for ext4 not enough?
[Galaxy S II Android Development] Spyr0s:
I'm using Naptime but it doesn't seem to have an effect and maybe my phone uses even more battery...
[Galaxy S II Android Development] infinion:
got it working with [Root] Doze Settings Editor(last profile) +boost mode greenify (AD+all xposed features checked) :D
[Galaxy S II Android Development] Krzy256:
Hello.

I have problem with installing gapps for CM13 on my GT-i9100.

/system partition is increased from 1,5GB to 4,5GB, but recovery signs problems with not enough memory on /system.

Also I can't use CM recovery, because after select "install from sdcard" recovery displays "Installation aborted (I don't remember a number of code)."
[Galaxy S II Android Development] wave41:
The main screen settings button does not work

automatic update does not work
[Galaxy S II Android Development] ViltusVilks:
Yes, last builds update does not work.. phone is soft-bricked after update, does not boot at all :(

But... 15-02-2016 version works ok (system ir resized for gapps)
[Galaxy S II Android Development] wave41:
it does not turn off during the phone update. I'm starting again re- install twrp
[Galaxy S II Android Development] super_newbie_pro:
Yes its not new, but if you want, its necessary (for me) to download from my PC, move on the phone on SDcard, reboot with another kernel (need reinstall all time when i want update cyanogenmod, with ODIN) and install from zip (why not include this option in the CM13 kernel / recovery mod (install from zip) ???) install the new release CM13 + opengapps and its ok :)
[Galaxy S II Android Development] Krzy256:
My error code: 70

Insufficent storage space avaliable in System partition. You may want to use a smaller Open GApps package or consider removing some apps using gapps-config... etc.

I have 4,5GB on /system and ~4GB free. I'm using Pico version of OpenGApps
[Galaxy S II Android Development] Kurt Krummbein:
I'm quite sure, your PIT resized /data not /system ... stock /system has 512MB, not 1,5GB ( hm stock /data ... don't remember, was too long ago ;) ) - /system with 4,5GB wouldn't make any sense, no sane builder would make a ROM using 4,5GB on system ;).

On the other hand, the most recent nightlys + open-gapps (pico) should not need the PIT anymore.

If it does, the Switch to common_mini_phone could be reverted ;).

Can you post the names and dates of the files you tried to flash?

Gtz

Kurt
[Galaxy S II Android Development] Krzy256:
cm-13.0-20160301-NIGHTLY-i9100 - ROM

open_gapps-arm-6.0-pico-20160301 - GApps
[Galaxy S II Android Development] the.gangster:
Even latest "common_mini_phone"-builds still *do not* offer enough space for Pico-GApps.

I had some people send me there open-gapps-log.txt files, yesterday.

They showed me, that even Nightly-20160228 still occupied like ~408600 KB of System, compared to ~451464 KB on Nightly-20160223 (last common-full-phone build). But even then, a non-modified Pico-GApps package doesn't fit. You would still have to provide a .gapps-config telling the installation to drop at least googletts. Without doing so, Pico-GApps calculate to need 119702 KB in System partition (including the buffer) to install.
[Galaxy S II Android Development] Lord David III.:
I had no problems with connecting to arch linux. I used heimdall, adb and PCmanFM with gvfs-mtp. I think the device was on the nightly from 20160227 when I used it last time. It's the device from my sister, so I can't test it now.
[Galaxy S II Android Development] Krzy256:
I'm used this to increase /system to 1GB, but it's still 512MB.
[Galaxy S II Android Development] Acid0057:
Which pit file did you flash?
[Galaxy S II Android Development] pravingasva:
Why then my system takes 494 MB space? Is it because i've a larger partition?

Also, my CyanDelta zip file is 416 MB, which is the more or less the same always since 20160216 nightlies or before maybe. What has been affected with the "mini" tag?
[Galaxy S II Android Development] Krzy256:
I9100_6GB.pit
[Galaxy S II Android Development] Kurt Krummbein:
Sigh, this is just 6GB data, not 1GB system ;).

Cheers

Kurt

---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------

So, the "common_mini_phone"-build just some missing (well for some guys) apps and still need rePITing or a .gapps-config :(.

Shrug

Kurt
[Galaxy S II Android Development] Krzy256:
My mistake. I thought, I91001GB_3GB.pit means 3GB for Gingerbread ROMs
[Galaxy S II Android Development] n3m3sis:
Hi Krzy256,

There is an excellent guide on re-pitting http://xdaforums.com/galaxy-s2/development-derivatives/mod-increase-partition-size-t3011162 and this pit file zip http://xdaforums.com/attachment.php?attachmentid=3130431&d=1422060280

contains all the pit files you might need (I used the I91001 GB_6GB.pit and have nano gapps installed). If the process seems too complex, then there is Lanchon's flashable repartition zip to assist you.
[Galaxy S II Android Development] the.gangster:
Don't know why your system takes 494 MB. Is that without anything but the pure ROM installed to system?

As it is not due to larger partition. Mini_phone is effective at build-time. So no decision is taken at install-time. And even if I don't know, whether the size calculations in the GApps' log are measuring 1KB as 1000 bytes or as 1024bytes, but such a difference should not result from just that.

Although I also use CyanDelta here and then, I don't know how efficiently it removes unused stuff from the uncompressed zip, but my CMUpdater zip with nightly 20160223 is still 451MB of size! So I doubt yours was 416MB already with 20160216.

---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------

That's what I am currently convinced of after parsing some GApps' logs and looking at the detailed calculations.
[Galaxy S II Android Development] Lysergic Acid:
In the same way, there's guys who don't want to repit to fit gapps. I can't satisfy everyone, you can get any missing stuff from playstore or flashing a zip. This website is all about mods, come on.

That's why we don't have multiuser, I'm answering this question for the third time, we don't have emulated sdcard, we can't get multiuser.

If a phone suddenly shuts down and gets bricked ( even if not from trim ) they'll need someone one to blame. And who will this person be? You? No. I'll be the screwed guy. It's not simple as it looks like guys.
[Galaxy S II Android Development] the.gangster:
According to my calculations (or better: the calculations of the GApps in its log) even Pico-GApps still don't fit into stock-sized system partion.

And this is not a request to drop even more from the builds. I already hinted that the "better" way would be to offer a preconfigured .gapps-config.txt that removes those system components. If I remember correctly, that was in Post #1000. That could even be installed per default to some location on the phone. Instead now they are removed for all, but it still seems not enough, as posted lately.

Yes, you will be the one that is likely getting blamed by 1 or 10 people (if that happened), while definetly getting celebrated by 1000s for implementing it (what will be a fact).

:)
[Galaxy S II Android Development] philippe734:
Please, could you share the scores with antutu v5 or v6. Thanks
[Galaxy S II Android Development] fireburner-de:
Why so harsh?

And as [MENTION=6560258]the.gangster[/MENTION] mentioned, the purpose this commit was merged, seems still not to be valid. CM+pico GApps still don't seem to fit.

Also most users already migrated to CM13 and more cautious users anyway will read OP and etc.

Can't there be a way to satisfy all users? By whatever config file, that by default installs mini CM, but can be changed by experienced users to full CM.

Or like [MENTION=6560258]the.gangster[/MENTION] proposed, with a GApps script.

Another possibility would be to generate another i9100 branch with full CM and TRIM enabled.

Please let us find a solution, that most people will be satisfied with.
[Galaxy S II Android Development] Kurt Krummbein:
Well, this point is true. But - correct if i'm wrong, think i read that on the tread - trim is never done automatically, so we could make a "Trim-App" and pack it to the build, that gives a warning message "Doing this might brick your device, we take no responsibility if this happens!" just like in "Triangle-Away"-App.

Just a thought.

Btw. great that you didn't resign due to the lots and lots of stupid requests during the last months ;).

Cheers

Kurt
[Galaxy S II Android Development] fireburner-de:
You are wrong, trimming on /efs /cache and /data is done automatically with TRIM enabled kernel.
[Galaxy S II Android Development] Kevin3014:
Really? I flashed a TRIM-enabled kernel on CM 12.1 in January hoping that I wouldn't brick my device, and my S2 does have that brick-bug. I honestly thought it needed that app to work. Guess I'm lucky. lol.
[Galaxy S II Android Development] karrlito:
Camera and HW decoder problems + mini phone patch question

Did anyone tested if the "common_mini_phone" patch makes enough space for gapps? Some people say that they can't install pico again. Maybe if the patch test system space before crippling the rom and install "common_mini_phone" only if the system is stock. Is there provided zip to make the phone full or to install missing components because you said "or flashing a zip"? I don't have enough knowledge to make my own zip. I will stay on 20160223 build until something is done about mini phone...

And btw my camera is not focusing. I have to touch the screen to focus, but if take picture there is no auto focus. Can anyone test this with newer builds? This is happening only with stock camera app.

Also my camera is buzzing sometimes. Usually after or during recording video The app makes her to move fast. When that happen is happening only with the stock camera app. Other apps focus fine and don't do buzzing noises but there is no other app that can make video. I tried some but they crash every time.

Also HW decoder is very bad. Many players can't play video using it. Screen recorder is not working too. Even with the command "screenrecord" in ADB.

And the common problem. Mtp switch is not working at all. Every time i take out usb it's going to charge mode. I switched it in everything shown in the setting. Tried restarting after switching but nothing works. It says mtp in setting but when i plug the phone it's charging only.
[Galaxy S II Android Development] nraddan:
Data issues with some apps

HI All,

I got my SGS 2 upgraded to CM13 a couple of days ago after a lot of fuss. I first got the OTA upgrade and Gapps were not working and I hat to repartition and flash everything again. But in the end I got everything working... Almost everything.

Is anyone else hitting issue while using their Data? I have some applications (WhatsApp, Waze, K9 Mail from what I tested) that don't seem to work with 3G/HSDPA while others (Internet, VirtualCards, Out4Food and Banking Application) work like a charm. Another strange issue is that sometimes while also with Data enabled, my phone is not reachable (I cannot call myself and not send SMS although the network seems connected).

Has anyone else encountered this? Is there anything I can debug to get to the bottom of this?

EDIT: Forgot to mention the build. It's 20160224.
[Galaxy S II Android Development] Spyr0s:
Who said that some users are not blaming you already, for the crappy recovery, for this or the other, thats why there is a DISCLAIMER in the OP that states that you are not responsible for any damage. Users are always going to blame someone. Back in the old days there were official Samsung ICS firmware's for i9100 and Note with the brickbug and even CM releases that bricked many phones until the devs in XDA ,Chainfire i think or Entropy found it out and informed Samsung.
[Galaxy S II Android Development] Lanchon:
you are wrong, as fireburner-de said.

you are not lucky: correctly implemented trim kernels won't brick any device.

---------- Post added at 05:43 PM ---------- Previous post was at 04:56 PM ----------

hi [MENTION=6159291]Lysergic Acid[/MENTION],

there seems to be a lot of fuss about about the mini change. (also maybe some problems, see quote above).

-of course the easiest way out would be 2 branches, but that's probably not doable on CM, and maybe even uncomfortable for you.

-a config file as proposed by fireburner-de is probably not doable either: the mini/full choice is a build time thing.

-but the mini thing is not a good solution either, as standard pico doesn't fit.

i can think of two other options:

1A) a CM minifier/debloat flashable script that does more or less the equivalent of mini and then some; enough to fit pico.

-not compatible with cmupdater.

-compatible with cyandelta.

1B) this script could be made compatible with cmupdater by making it so that it stores itself within the gapps backup script set. it would auto-execute after cm flash and before restore of gapps.

1C) this script could also be made compatible with cmupdater by including it in the official cm zip. it would check the free space in /system after install and debloat if under a critical limit. (or it could just decide based on partition size.) a positive side effect of including it in the cm zip is that it can be automatically updated whenever it's needed (ie: cm or pico gapps grow too much yet again), while 1B) would require manual intervention.

2A) a script that formats /preload and moves a set of folders from /system to /preload and symlink them. this would allow full cm and big gapps without repit for the foreseeable future.

-suffers from same interactions with install as 1A), so corresponding solutions 2B) and 2C) are possible.

2C) would be a little extreme maybe. having the standard CM automatically format a new partition (/preload) would break some obscure dual boot setups (yes, some people use /preload).

some solutions need inclusion in std cm. but all need a revert of mini. so LA, your opinion makes or breaks these options. are you willing to go with any of this? if you ask me, 1C) seems best.

thanks!
[Galaxy S II Android Development] daniu:
Hi

Just want to add to the discussion that cm is still usable without gapps and that I would not like some script to debloat my system automatically just because gapps would not fit in any more.

Totally forgot that my system is 756 - not a problem at all without gapps ...

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Android Development] fireburner-de:
But you know, that the change to common_mini_phone already did the exact thing you do not want: It removed apps and librarys from CM.

edit: I just got notified by a user on a german android board, that soundrecorder still is included in 20160301, which means this list seems not to fit.

So on top of the discussions about mini CM, it would nice if we would know more about what actually is effected by this commit.
[Galaxy S II Android Development] stylemessiah:
I dont understand why things have to get complicated with the mini change

LP needed a 1Gb system partition to work properly and no one making an LP ROM backpedalled to accommodate the people who couldnt read an OP and the requirements

It should be a simple matter of "This ROM needs a 1Gb system" in the OP, users choice as to whether they want to use it or not.

I dont understand why the changes were made to (seemingly) accommodate a very very small number of people who refuse

to read or respect requirements

If ive got any of those presumptions wrong, i apologise

But in this day and age, and we've been keeping the S2 alive longer than anyone thought, people need to

accept they are going to have to make some changes if they want to use provided and up to date ROMS
[Galaxy S II Android Development] geekch:
How install the gapps without repartitioning

It´s very easy ,

just have to install the gapps aroma

and not select anything ,

thus only installs google play services and google play , and delete

unnecessary system things with assistant.

For example, I uninstalled the aosp gallery , aosp email , aosp camera , the aosp keyboard , cyanogen services... ,

and I then installed the google substitutes.

This method has a problem , you can not upgrade without doing the whole process again. :)
[Galaxy S II Android Development] the.gangster:
[MENTION=6965400]geekch[/MENTION]

That's what I was hinting at already: to get rid of the need to do all that again and again, simply put your desired configuration (including the stock components you want to remove) into a .gapps-config.txt and you can simply flash any newly downloaded opengapps package and it will behave exactly like you configured it.
[Galaxy S II Android Development] pravingasva:
Exactly! there are few people who either dont read the OP carefully or they are too lazy to do the extra steps. Custom ROMs are not for the scared and lazy people! You are not paying the developers for making your phone gorgeous, so you have to adjust accordingly, Thats All!!
[Galaxy S II Android Development] daniu:
Hi

Yes I do know that - that's why I liked all posts (at least some) that promote changing that back.

Just also want to emphasize that cm13 does NOT need 1GB system partition as it was posted repeatedly here recently ... (I got 765 and I think if you never use gapps even 512 was always enough)

Actually I agree to the original cm opinion: cm is not cm+gapps and if cm does not easily work with gapps then that is totally OK ... as long as people are informed about that somewhere. RTFM!

Actually I think that the cm updater is a strange thing: it helps people to update to software that might just not work at all. In combination with a recovery that cannot do nandroid backups that is really a very wrong thing to do and in my opinion that is the culprit ...

BTW: are people really using the updater without any possibility to go back? That is crazy if I might say that ... worst thing now is that the software gets changed so that this people can go on like this ...

BTW2: I used to have a debloat-script that removed quite some system components like: browser, animated background, camera app and the like. Is it possible to install a small gapps package after doing this? Did someone test that?

Regards

Sent from my x-phone using brain 2.0

---------- Post added at 06:48 AM ---------- Previous post was at 06:22 AM ----------

Hey ...

YOUR WARRANTY IS NOW VOID

does not apply any more? Are you saying that you take any responsibility for software that gets compiled automatically in the night? (and that BTW works perfectly for thousands of people)

I think if anybody complains about a phone getting bricked after at least 3years of use he does not understand anything about electronics.

Regards

Sent from my x-phone using brain 2.0
[Galaxy S II Android Development] Lanchon:
lol the plot thickens... well LA will have to implement something. everybody has the problem now, including you. the script would fix the issue for most users, although not for you. we know that LA doesn't want the full CM. there might not be a solution that is ideal for everyone...