yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] KrautHolg:
GT-I9100 CM13 Camera Autofocus

Hi!

Firstly, thanks for all the hard work!

I am running cm-13.0-20160924-NIGHTLY-i9100 on four different phones. And on all four the camera autofocus doesn’t work properly. This also makes it impossible to use the Barcode Scanner from ZXing Team.

I did look at known issues here http://xdaforums.com/showpost.php?p=65298277&postcount=2 and I did make a search for camera autofocus, but no luck.

Can somebody please point me in the right direction?

Any help much appreciated!

Cheers!

KrautHolg
[Galaxy S II Android Development] laserkater:
Funnily it works if you disable the autofocus in the Barcode Scanner app. Had the same issue.
[Galaxy S II Android Development] KrautHolg:
Thanks! Still, the camera per se doesn't work properly. Anybody any ideas?

Cheers!

Holg
[Galaxy S II Android Development] Saber:
The OP has been updated

And with the updated guide, it is good news that the horrible cyanogen recovery mounting bug has been fixed :)

Old parts of the guide for Isorec installation will still be included for those who want to upgrade to an older build. In the future, I will hide this or keep it separated from the main post.

As always, new users who want to upgrade to CM13 should always flash the latest builds.

Saber ;)

(Not gsstudios anymore btw)
[Galaxy S II Android Development] RoyalSandwitch:
My Device does not work properly after following the steps.

When I start the blue thing with two white eyes and a mouth is on my screen and after around 10 min it says "Preparing xx off 24 apps" and when it is at "Preparing xxx 24 off 24 apps" it is restarting again and doing exactly the same thing over and over again.

I already did a factory but that did not help.
[Galaxy S II Android Development] Lobo17:
Problem with cyandelta

I got a generally Problem with cm13 and cyandelta (updater).

I got no google at all on the device (no gapps). The cyandelta I took from a nother device.

After install and start cyandelta crashes  No errors. I just goes off (the app) with the message “das program wurde beendet”. I cannot start it.

Do you know solutions or work arouds? I will not go and install gapps. To get rid of google-account was the reason to flash cm13 (nightly at the moment).

Greetings

Lobo
[Galaxy S II Android Development] noobsgs2:
I'm on TWRP 2.7.1.0 with SLIMKAT 4.4.4 , can i install this TWRP http://xdaforums.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457/page51 , re-pit the phone and install CM13?
[Galaxy S II Android Development] Saber:
Hi,

When you install the TWRP version from the link, the recovery will not appear immediately because the kernel you are currently on does not support isorec recovery. After you've install CM13, you will see TWRP 3.0.x. Everything you've said is fine.

Saber ;)
[Galaxy S II Android Development] noobsgs2:
So TWRP 3.x as first and without rebooting the recovery i should re-pit, CM13 and Gapps?

Or do i have to use Odin?
[Galaxy S II Android Development] TriboDoP:
Hi

Always repit before flashing cm13 and gapps.

In odin flash pit-files and gustavo kernel.

(do not forget to format after repitting).

Then flash with recovery cm 13 and gapps and twrp 3.0.2-1 in one go (to not reboot in between!.

Without pc/odin: put isorec-kernel and isorec recovery twrp 3.0.2-1 and pitfile 1GB system_4GB data using lanchon repit tool (and Rom/gapps) on SD card.

flash with recovery isorec kernel and isorec twrp 3.0.2-1.

In twrp flash lanchon repit tool - pitfile.

Do not forget to format.

Clean flash in twrp cm 13 and gapps.

edit: instead of isorec-kernel i install latest cm11 Rom and gapps (has isorec-kernel) and isorec twrp 3.xxx

So i have a working rom and isorec twrp.

I make then a backup and continue repitting and flashing cm13.
[Galaxy S II Android Development] KidKnowsTech:
DELETED
[Galaxy S II Android Development] TriboDoP:
[MENTION=5848761]shanx_verma[/MENTION]

Hi

Do you have a working custom-recovery?

If yes flash unoffical cm11p 20161119 i9100.zip by [MENTION=5955924]zjq985062714[/MENTION] and isorec twrp recovery 3.0.2-1.zip from micro sd.

In isorec twrp recovery flash latest lanchon repit .zip using 1.0GB system and 4.0GB data.

Format partitions and then flash cm13/cm14 with gapps.
[Galaxy S II Android Development] shanx_verma:
I'm afraid I could not find the 1GB system 4GB Data Repit .zip you quoted.

Can you please direct me to it? :)0/
[Galaxy S II Android Development] TriboDoP:
You really should also read and search by yourself.

Please search for Lanchon repit Tool/github/downloads

And for how to do please read carefully this thread.

Regards
[Galaxy S II Android Development] shanx_verma:
Thanks! :)

Thank you so much for your patience. I guess I wasn't reading thoroughly.

I have finally installed CM13, then with the help of lanchon repit I'm currently on TWRP 3.0.2.0 ISOREC.

Thank You so much for your patience again!! You've been a real great help buddy! :)
[Galaxy S II Android Development] TriboDoP:
Hi

Glad to see you on cm 13!

Btw If you want want to update to latest twrp 3.0.2-1 you find this .img - file on isorec twrp thread (including how to update with present recovery)

Cheers!
[Galaxy S II Android Development] the.gangster:
Just to mention:

You could have also flashed the TWRP 3.0.2-1 as a zip right away.
[Galaxy S II Android Development] Damna:
can't use root privileges

Hi, im using CM13 on S2 I9100 without problems. It works perfectly.

The problem is about root privileges. I enabled the root on apps and adb but anyway neither apps nor terminal access root.

I red tons of threads but no one seems to have had such a glitch.

Did i miss something?
[Galaxy S II Android Development] Saber:
When you flashed CM13, did you remember to select no for the fix/install root prompt?

Saber.
[Galaxy S II Android Development] Namoi:
Guys,

I am facing a problem I can't solve by myself.

I am coming from Dirty Unicorns, so I obviously repited my GS2 initially with a min preload, but as i read that could be problematic I repited using 512MB for preload. Of course sytem is 1GB.

I am also using latest IsoRec (I even tried with the one from The Gangster which allow to wipe preload).

All partitions are wiped.

Nonetheless I always get Error 7 (not 70) when I flash latest Nightly (also tried with past nightlies).

I don't get it. I read one trick is to edit the updater script and remove the first line (assert), but I want to test this only if it is the only solution.

Do someone has a clue ?

Thanks

Edit: I also noticed that the installer script resize my system partition to 500GB after installing oO.
[Galaxy S II Android Development] Damna:
Whoops. No, i guess. Should i flash again it? Or?

Thanx.
[Galaxy S II Android Development] Saber:
Try flashing again but making sure that if the prompt does appear, you select no.

Saber :)
[Galaxy S II Android Development] Damna:
ok i will try and i will let you know. :highfive:

OOOOHH. Thanx. It works. I just flashed the rom and the prompt did not appear but now the root works.
[Galaxy S II Android Development] Namoi:
So I tried another way :

I succesfully installed CM12.1 + Gapps. All is working fine.

So I flashed Lanchon Iso Rec CM12.1 Compatible kernel to be able to flash latest IsoRec TWRP.

Success.

BUT When I tried to install CM13 after perforing a full wipe I still got the Error 7 oO

The line just above states "System partition has unexpected contents after OTA update".

And again I can see the system partition has been resized to 503MB (which must be the default).

What is going wrong ? Do I need to install CM13 on the default sized partition, THEN resize before flashing Gapps ?

In fact, did someone succesfully installed CM13 over CM12.1 using latest TWRP ?

Any hints greatly appreciated, as I am beginning to loose hope.

Thanks
[Galaxy S II Android Development] TriboDoP:
Hi

There is no need to flash any isorec Kernel after flashing cm12 because cm12 has isorec-kernel.

Thats why i flash cm12/cm13 TOGETHER with isorec recovery twrp 3.

I Do not know if it makes any difference but i would clean flash cm12 again to be on stock Kernel.

And then i would repit again to 1GB System 4GB data leaving preload at stock size

Format alll partitions.

Then clean install cm13.

Maybe something went wrong when partitioning.

And you did not mention If you increased data aswell.

I flashed mm roms on many (repitted) devices and it never mattered coming from cm11/12/13 as long as i clean installed it.
[Galaxy S II Android Development] Namoi:
Thanks for answering.

Yes I also modified Data (tried with 4GB then with 6GB when i reverted to standard preload)

I also just tried to install CM13 via Dorimanx Kernel to be on CWM Recovery -> Same problem.

But you say CM12.1 has Iso Rec support, well I read it also. I flashed the Iso Rec compatible Kernel because it didn't work with the last CM12.1 Snapshot. I reflashed TWRP, but each time I rebooted to recovery (from within CM Recovery or from the power menu), it always loaded the CM Recovery. After flashing the compatible Kernel, it eventually worked... I don't understand, but it seems to me latest Snapshot doesn't have the Iso Rec patch build in.

BUT I just saw a new Nightly from this morning. Gonna try it just in case (downloading it right now).

If I got the same problem, well I don't know... maybe I will jsut give up.
[Galaxy S II Android Development] TriboDoP:
You are right. Old snapshots and others from 2015 have no isorec-kernel. But all latest (2016) have.

Even latest cm11 has isorec.

Of course it is adviced to use latest builds because snapshots are not up to date.

I hope you will get it done with latest build.

Remember: we never give up!

Cheers!
[Galaxy S II Android Development] Namoi:
Yep, but the latest CM12.1 Snapshot is the latest CM12.1 build available I could find.

I will try with latest CM13 nightly and i will try to repit but I am already 1GB system, 4GB data and 512MB preload...

Thanks again
[Galaxy S II Android Development] the.gangster:
Once more:

Forget about the preload bull****...

No ROM that I heard of really has problems with a minimized BUT PROPERLY FORMATTED preload partition.

Only Sammy ROM and the dual boot function of dorimanx kernel fills it with data. Others might only wanna check its filesystem's existence...
[Galaxy S II Android Development] TriboDoP:
Hi [MENTION=6560258]the.gangster[/MENTION]

[MENTION=4296852]Namoi[/MENTION] said in his post # 246 that he used your recovery with preload wipe to wipe all partitions.

I just wonder what went wrong then....

Regards
[Galaxy S II Android Development] the.gangster:
Wasn't meant to be offensive.

You can continue to wonder. But as this has nothing to do with it and I read it several times already, I just wanted to emphasize, that the unformatted preload would only cause inability to boot the ROM. (Boot loop)

This error here sounds much more like the checksum for one of the ranges being checked after block image updating failed, thus throwing the error "system partition has unexpected non-zero contents after ota update".

As it aborts then, the block image that has stock-size is not resized to its actual size and remains at 500MB. That can be fixed by running the resize within advanced wipe menu of the TWRP recovery. But it has nothing to do with preload. Flashing a cm-ROM doesn't write into it.

Usually I would have recommended to redownload the ROM and reflash, but he did that already, as he tried out different versions.

Make sure you wipe the resized system partition once more before retrying. Still no guarantee, but worth to try with such an error. Otherwise start from scratch with stock ROM...
[Galaxy S II Android Development] Namoi:
Yes I know (edit : i was replying to your previous post ;) )

I first tried with Min+wipe preload to no avail, so i tried with a standard preload+wipe and I also wiped it again with your modified TWRP just in case.

I did all i could to install CM13 (via IsoRec, via Dorimanx, coming from DU coming from CM12.1) but even latest nightly give me an error 7. I really don't know what is wrong as I said I ended starting from a fresh CM12.1 install with 1GB system and ISo Rec, but no way I always get this error.

I begin to suspect an hardware problem.

Right know I am checking the difference between CM12.1 and CM13 updater script...

Edit2: Yes, i will try one last time with wipe after repit and it it fails maybe i will go through the hassle reflashing stock.

---------- Post added at 05:32 PM ---------- Previous post was at 04:57 PM ----------

Well, I spoted 2 differences between CM12.1 and CM13 updater script.

In the latest the data partition is defacto converted to f2fs AFAIK

mount("f2fs", "EMMC", "/dev/block/mmcblk0p10", "/data", "");

The second on is a check that lead to the error i i get

if range_sha1("/dev/block/mmcblk0p9", "16,0,32770,32801,32803,33315,65535,65536,65538,66050,91028,98304,98306,98337,98339,98851,131071") == "bddc5ce4e3ab918c1ff8916f7ae4e80c44b4522c" then
if range_sha1("/dev/block/mmcblk0p9", "18,32770,32801,32803,33315,65535,65536,65538,66050,91028,91540,97792,98304,98306,98337,98339,98851,131071,131072") == "53d82ebd27c7d13f672ebc847bec3eefad9fb23b" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;

So I changed the first to

mount("Ext4", "EMMC", "/dev/block/mmcblk0p10", "/data", "");

And I dirty removed the check.

Then I installed CM13 again, and guess what ? no errors of course as i removed the checks, but mostly it boots !

So I don't know what is wrong with this updater or what is wrong with my device, but the two don't like each other.

I will report this to the CM13 thread just in case.
[Galaxy S II Android Development] the.gangster:
If you use the Lanchon Repit method with the +wipe command there is no need to use my modified TWRP to format it, as Repit-Tool will care for everything.

The only intention to publish it with that feature was to give that option to those people who used the Odin+pitfile-method, which is often described everywhere but usually misses the important hint to format the preload partition if the partition was changed.

That was not the problem!

F2FS-support was added to CM13 so this was just for that mere purpose added into the updater script.

...what I head already described in my post, to be the actual error.

You removed the check but not the root of the problem (if the ranges are still correct)

And your device would have probably booted fine even after the error, but that way, your partition gets resized again at least (and if you didn't wipe your system partition your addon.d-backups (like GApps...) would have been recovered)
[Galaxy S II Android Development] Namoi:
Yes you are right, but maybe this check (the range as you stated) was the problem. For now evrything is working fine. No FCs, no reboots... well let's see.
[Galaxy S II Android Development] the.gangster:
If so, it could only be fixed with a next nightly. But the two ranges and their expected checksums is subject to change from build to build anyway.

And so far, I heard of noone except you, reporting that error with this build. I read already occasionally about individuals having that problem and with next nightly (or a different one at least) they were doing fine again.
[Galaxy S II Android Development] Namoi:
Hmm, I have this problem with all cm13 nightlies available to download (4 exactly)... Could it be a hardware defect ?
[Galaxy S II Android Development] the.gangster:
[MENTION=4296852]Namoi[/MENTION]

well, sure in theory it could be a hw issue if exactly one of those regions could not be flashed to their expected values so that their content's checksum would not match, but first I would search for other explainations. Although I wouldn't know where to start. You changed the recovery already? Although AFAIK the called function is defined in the updater-binary, maybe it would make sense to check the installation with another recovery. I wouldn't expect my modded one to behave any other than the unmodded one, but even CM-Recovery should be able to flash a new ROM meanwhile. So you could flash the IsoRec-Disabler to re-activate CM-Recovery (as long as you still have a CM13-kernel) and give it a go. It would be no problem to return to an IsoRec recovery again.

Sorry that I can't give you a solution to your problem right away, but as I never experienced it... except once, where I had a broken download or something like that and next try succeeded.

Good luck
[Galaxy S II Android Development] Namoi:
Thanks for your reply :D

Well my GS2 is really one of the first from 2011, so probably hardware misfunction is to be expected. What I supect could be an emmc problem, but I checked it via emmc bug check app which allows to also test the chip and it gave me no errors... ok, but how reliable is it, I have no idea -> It just write to each "cluster" and read it again for unconsistencies I imagine.

I could indeed now try with another recovery just to see (but I tried AFAIR via CWM recovery from Dorimanx Kernel from [MENTION=5811506]Saber[/MENTION] and I also had that bug oO), but as I have absolutely no errors since I installed CM13 via my dirty fix, well I will maybe just live with it except if something goes wrong. I tried it hard to make it misbehave, I tried to backup and to restore via TWRP and it still works...

I am just now amazed that a so old device is able to handle such a new firmware with ease. It's pretty impressive and even smoother than CM12.1 (I had a lot of opportunities these past days to compare as I was swaping from CM12 to CM13 almost on day to day basis to try to fix this bug).

Just the Ram is a real bottleneck here, but ok we know this.

I just regret before CM13 developpement stopped that the backlighting of the hardware keys was not fixed (it worked on CM12) even if we have a workaround I know.

Thanks again

Edit: Just wonder if you know if the kernel parameters exposed in Kernel Adiutor are really modifiable/stickable ?
[Galaxy S II Android Development] the.gangster:
[MENTION=4296852]Namoi[/MENTION]

If you are that amazed already, looks like you havn't tested this one yet. ;)

(btw:that one doesn't have the range-checks in its updater)

You mean, that you have to use the BLN_Mod if you want to set a backlight timeout? As keeping them ON or OFF permanently works without it.

Kernel Audiutor: never needed it so far, but it got mentioned quite often in the CM13-thread, so yes, it should work.
[Galaxy S II Android Development] Namoi:
Hmm, yes I saw, but after all the hassle I get, this one, even if promising, seems a little rough around the edge :p , but I will off course switch to it eventually :D

Yep, the old Syah BLN mod which still is of great help as it seems (problem is you have to you use another kernel tweaking app to deal with it and I don't know which other parameters get tweaked under the hood).

BTW thanks to insist on the fact that stock CM13 could disable backlight as I tried and it didn't work. As you emphasis it, I tried a reboot after disabling it and oh, Oh ! it worked. Don't remember if it is stated in CM13 OP that a reboot is needed, but on my strange device it obviously is.

I will just try, as I noted on my multiple test using DU, Cm12.1 and CM13, that mostly swapiness and Zram seem to have a great impact on how apps get killed out of memory. I would also try a different CPU gov to give a little more punch, but it seems Interactive is not available out of the box (not that I am a hardcore tweaker as my old past experiments on the S2 were always : the more you stay on stock, the less problem you will get -> ie: if it ain't broken, don't fix it).

Thanks again for your insight :)
[Galaxy S II Android Development] the.gangster:
No it's not!

The only only thing needed is after changing a value in its settings to switch of the display (press the power button SHORTLY).

For more details this guide's OP leads you to the right BLN_MOD-thread several times. I must have mentioned this little fact also there somewhere, but (sadly but sometimes also for a good reason) not every detail makes it into an OP. So if you flash that one you have the full bln-experience. If you also flash the addon (published in the same thread and linked in my signature) the BLN_Mod will be preserved upon ROM-updates.

EDIT: for your tuning attempts, you could have a look at post #4 which also mentions some Kernel Audiutor modifications aiming battery or performance improvements!!
[Galaxy S II Android Development] Namoi:
Well I didn't know, but yes it works ! That is great as I use my phone as an alarm clock and the backlight was specially anoying at night, but somehow usefull at day. Thanks.

I also will definitely have deep look at the thread you provided to fix this once and for all (and hope Samsung will stop building phones with hardware keys (next S8 seems to be the beginning btw). I once thought I won't be able to live without hardware keys, but since I bought a Motorola with soft keys... no problems anymore ;) )

Thanks again :good:

Edit: i just saw in the bln thread that the synapse version is a stripped one which great. I thought it could handle others kernel parameters.

Edit: just read the 5 pages. Still not clear if this mod will prevent phone to deep sleep. I know bln for notifications do prevent it, but is the backlight bound to it?

Thanks
[Galaxy S II Android Development] the.gangster:
[MENTION=4296852]Namoi[/MENTION]

one last hint:

Synapse is just a configuration tool which offers you exactly those options what you provide a configuration for. The configuration is provided thru the BLN_MOD.zip. You need both (plus the optional addon).

For the night, you'll love the feature of dimming the lights down to 2.6V using dimmed mode. But that's just one out of five. It was quite some work to make all these options work as they do now, with kind of self-configuring the dependant values where needed and accept them where not in contradiction to the choosen mode and the other values. Plus: you'll find multi-language support in it.

EDIT (to your latest edit) :

man, you should really *read* this guides first 4 posts at the very least! It mentions, that it keeps the device from deep sleep as it is *not* BLNWW ( WW=without Wake-Lock).

This again is also mentioned in the BLN-Thread. But in the currently latest post in there [MENTION=414800]arnab[/MENTION] announced to bring up such an implementation, which would be incredible.

As long as we "just" have the BLN version, you could configure the time-out to stop notifying after e.g. ten minutes...
[Galaxy S II Android Development] Namoi:
Yep I know, I just thought it would expose (as other kernel tools as adiutor) other parameters.

I already used synapse and bln when I used DU on the GS2 and the app provided a lot of other kernel parameters which could clash when one uses kernel adiutor.

But it seems the kernel used by this DU release was open to it.

What about deep sleep with the mod ? Does it prevent it as battery life on this device is already a concern if you see what I mean ;)

---------- Post added at 11:11 PM ---------- Previous post was at 10:53 PM ----------

I read it of course but it was never clear to me IF BLN (blinking/breathing notifications) was totally related to the control of the backlight and its time out. If you check the synapse DU version BLN and backlight control are not in the same section hence my question :)
[Galaxy S II Android Development] the.gangster:
BLN versus BLNWW is not a question of the above configuration-tools as they only configure the behavior.

If a ROM/kernel offers BLNWW-support, the BackLightNotifications with steady lights will not prevent the device from deep sleeping. Otherwise they will. As will blinking/breathing effects on both implementations.

Current implementation on CM13+14.1 is BLN.
[Galaxy S II Android Development] Damna:
what would you do to install the cm13 on a i9105p no root with not working home button?

adb reboot download does not work [requires root(?)]