[RECOVERY][Codina] TWRP 3.1.1 - Galaxy Ace II Android Development

TWRP
for
Samsung Galaxy Ace 2
aka Codina​
Sources
Device tree: https://github.com/ChronoMonochrome/android_device_samsung_codina/tree/omni-7.1
Recovery Source: github.com/ChronoMonochrome/android_bootable_recovery/tree/android-7.1
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
1) before installation, make sure that you've installed chrono kernel (r5.2 version or up is required for TWRP 3.1.1)
2) flash zip file
Download
http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/recovery/TWRP
XDA:DevDB Information
TWRP for codina, Tool/Utility for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome, SergeyL
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-05-22
Created 2015-04-18
Last Updated 2017-05-22

---

Reserved
Changelog:
22.05.2017
rebased to the CM14.1 device tree by SergeyL
updated to the latest omnirom 7.1 sources
removed a device-specific hack
increased the scrollbar width in the file manager
re-added an initial support for the dualboot feature
28.08.2015
updated to latest omnirom's 5.1 recovery source
fixed reboot sequence bug introduced in 2.8.7.0
adjusted brightness and disabled vibration intensity by default
reworked genfstab
19.04.2015
fixed not working taking screenshots (thanks @Epirex for hint)
removed using path to CPU temp as it doesn't work properly
16.04.2015
initial release
added /ramdisk partition to backup list
added path to CPU temperature interface (that doesn't work sometimes though )
Known bugs:
Report here if you have found any
About EXT4/F2FS
Whatever variants of filesystems on /cache, /data and /system (EXT4/F2FS) should work. However, only ext4 was tested by me. If you've encountered any issue with it, post here /ramdisk/twrp.fstab.
About installation on codinap
This installer should support codinap as well as codina. Otherwise report about it as I haven't tested installation on codinap.
Theme materialised
http://forum.xda-developers.com/galaxy-ace/ace-2-apps/twrp-materialised-t3066650

---

OMG @ChronoMonochrome you are doing a very good job for our device .As always many thanks!!!!
btw. later i upload new version of themes for TWRP
Edit: Themes Added

---

guys, is there someone, that for some reason prefer twrp?
I would hear..why, it amuses me, personally(backups, overall mgmt, you know ).
Is it matter of preference?

---

xo.en said:
twrp, cwm.. what's the difference...really(wrote by user of cwm).
(i mean for real, rom modding experience ),
i mean: allright, but this is clearly...matter of preference, not progress, yes?
Click to expand...
Click to collapse
Yep, this is matter of preference...
btw, guys, is there someone, that for some reason prefer twrp?
Click to expand...
Click to collapse
Not that I prefer TWRP or Philz(are we talking about philz?), I just wanted to get familiar with recovery building. Later, maybe I will be able to build ROMs (if it is possible on my machine). Even building recovery(with 4.4.4 sources) on x86 machine wasn't very easy, but at least it's possible. Some mess with default repos was needed.
I would hear..why, it amuses me, personally(backups, you know ).
Click to expand...
Click to collapse
What's wrong with backups?

---

ChronoMonochrome said:
What's wrong with backups?
Click to expand...
Click to collapse
Absolutely nothing..i lost my, uh, thought, sorry.

---

For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this

---

manthes said:
For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this
Click to expand...
Click to collapse
hm. i have not seen cwm blackscreen for year or so(s6d here), in old days only solution was to keep finger on screen in such cwm to see wtf is goin on.
Thing was related to kernel, idd, and definitely not to rom used, imho.

---

I have it all the time with CWM after cwm 5 or a version like that if i remember correctly. I dont know why. Maybe my s6d is more sensitive .
Before twrp it was a torture to test custom roms. However i think that TWRP is much more friendly.
And because we are just spamming right now i have to say that i test this recovery and it looks like that it is working fine (and it has better font)

---

manthes said:
And because we are just spamming right now i have to say that i test this recovery and it looks like that it is working fine (and it has better font)
Click to expand...
Click to collapse
..indeed, sorry for spam...it is good you found this fixed now anyway.

---

manthes said:
For us with cwm black screen it is very important to have TWRP for recovery.
A big thanks to Chrono for this
Click to expand...
Click to collapse
It's fixed on my Kernel and that from Chrono (latest Build).. at least on 20150405 it's 99,9% fixed .. just only one user of the whole world with s6d have still problems ..
btw: i've also s6d now, and even if i hardly OC that LCD.. i still don't have that blackscreen bug.. not on CM11 and not on cwm

---

ace2nutzer said:
It's fixed on my Kernel and that from Chrono (latest Build).. at least on 20150405 it's 99,9% fixed .. just only one user of the whole world with s6d have still problems ..
btw: i've also s6d now, and even if i hardly OC that LCD.. i still don't have that blackscreen bug.. not on CM11 and not on cwm
Click to expand...
Click to collapse
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?

---

xo.en said:
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?
Click to expand...
Click to collapse
Kernel defaults are used on early stage of system init(this is when ROM settings / init.d scripts aren't loaded). But since neither first nor second is used in recovery, there should another way to work around it. I've provided /ramdisk/00recovery that runs at very early stage (probably earliest possible). Almost same work does /ramdisk/00userinit , but it run only when you boot in system.

---

Uploaded new build
Changelog:
19.04.2014
fixed not working taking screenshots (thanks to Epirex for hint)
removed using path to CPU temp as it doesn't work properly
Click to expand...
Click to collapse

---

xo.en said:
Sudden interest:
Tell me something: which settings of gov/i/o are used in twrp/cwm, where choice is taken from? Can we customize it? Or it is just some kind of lowlevel, generic thing?
Click to expand...
Click to collapse
Yeah, i can only speak for my Kernel: I can set for every thing different Gov. I/O: CM, CWM, LPM (Offline-Charging) Also different LCD Brightness... and Different min. max CPU Freqs. and so on..
When i started to build the kernel for the first time, in CWM we had that config: (Default TC):
Performance Gov. (static 1Ghz !)
Brightness: 100%
Now it's running:
interactive, 400 - 800Mhz
Brightness 30% (also for offline charging, and CM bootlogo to save some power..)
EDIT: Nope, on my Kernel the User can only change Kernel tunables via init.d scripts ...(not for cwm and lpm)

---

ace2nutzer said:
Yeah, i can only speak for my Kernel
Click to expand...
Click to collapse
I dig you - so, lowlevel setting that is used in twrp/cwm relies entirely on kernel settings(set/edited before compiling)?
Recovery just uses settings made as default before compiling, yes? This is the point - can we affect this AFTER
I mean - recovery uses same thing that we see after firs boot(i.e. in performance control, chronokernel app, etc), right?
SO, now - can we, in example - add option to change lcd freq setting to cwm/twrp level anyhow, too?
Or this thing is related to different area(i mean - is kiosk mode(you know what i mean..i hope, here) able to manage such things?)?
Ok, post is edited to maximum possible clearity, no more edits...for now

---

xo.en said:
I dig you - so, lowlevel setting that is used in twrp/cwm relies entirely on kernel settings(set/edited before compiling)?
Click to expand...
Click to collapse
Yes. - in ramdisk, .. (boot.img)
Recovery just uses settings made as default before compiling, yes? This is the point
Click to expand...
Click to collapse
Yes
can we affect this AFTER
Click to expand...
Click to collapse
Nope, but if u use Chrono K. then yes.. because u can edit the recovery files .... just do inits ...
I mean - recovery uses same thing that we see after firs boot(i.e. in performance control, chronokernel app, etc), right?
Click to expand...
Click to collapse
Yes, but as i said, it's possibly to use different settings in recovery.. if it's writed as init on recovery files.. otherwise everything will run as kernel defaults ....

---

xo.en said:
SO, now - can we, in example - add option to change lcd freq setting to cwm/twrp level anyhow, too?
Or this thing is related to different area(i mean - is kiosk mode(you know what i mean..i hope, here) able to manage such things?)?
Click to expand...
Click to collapse
If you are talking about kernel defaults itself - then no, these values are hardcoded. However these values can be overriden by initramfs scripts (or by mentioned before script on /ramdisk). As I said it is only a matter of time, I mean it's only about when these scripts runs.

---

ChronoMonochrome said:
If you are talking about kernel defaults itself - then no, these values are hardcoded. However these values can be overriden by initramfs scripts (or by mentioned before script on /ramdisk). As I said it is only a matter of time, I mean it's only about when these scripts runs.
Click to expand...
Click to collapse
Till now, i can override what i want on cwm.. it works.... but the command need to write on the right file / place .. otherwise they are overwritten again by kernel... To check if it works or not, simply check with ADB

---

@ChronoMonochrome Why we need chrono kernel at first?
And can i use this on stock 4.1.2 with stock kernel? Because i always get blackscreen if i use temporary cwm.