[DISCONTINUED][ROM][UNOFFICIAL][UBERTC/linaro]nvertigo-cm-12.1 for SM-T800 16gb - Galaxy Tab S Android Development

Bad news: this build is discontinued.
Good news: lineageos is comming to chagallwifi. @Paulicat from TeamExynos5420 is doing a great job: https://forum.xda-developers.com/ga...m-lineageos-14-1-sm-t700-t800-coming-t3535159
CU, Nvertigo
I do not do any further builds of this rom. But thanx to @ristokoo - who is not just talking, but taking action - and thanx to @deadman96385, who will commit future fixes - the rom is carried on. For the most current builds look at the last pages of this thread for @ristokoo's builds. Since @ristokoo has no working build-environment, I'll provode you with security fixes and - propably - monthly updates. Many, many Thanx to @ristokoo for his time, dedication and support!
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin flashable tar for BOJ1 can be found here.
Please refer to posting #3 on how to report an issue.
IMPORTANT: netflix does NOT show HD content for the most devices. For detailed information refer to this posting.
I consider the builds from 20151112 on as non-beta and stable.
Don't expect nightlys. I'm planing one build per 10 - 14 days. @lionheartk is pushing upstream updated builds from time to time. You can find them in the thread when he publishs them - so read the thread. When hunting down an issue or implementing new features, I will push test-builds in the thread - not here in OP.
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Credits
@Barracuda77777 (without his contributitions and encouragement there would be no cm11 rom. He alone saved me from loosing myself in source code! Whenever I got stuck he came up with the brilliant change or the day saving idea. Thank you, brother!)
@UpInTheAir (most of the code changes in the kernel from the last 10 days before Christmas are from his SkyHigh kernel. He let me use his code, and most important: he explained with endless patience to me what I was doing... To reflect this the default branch of our kernel is no longer cm-11.0 but cm-11.0-sh [sh for small sister of SkyHigh]. Thank you, mate!
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and me sstarted of from)
@eousphoros (for his device git: the base for @crpalmers work)
@lionheartk for providing twice-a-weak-builds.
@diegocr for getting rid of repackrom.
@deadman96385 for the kernel source from build 20151118 on.
@halaszk88, @faux123 and all the others I forgot
Unique Features
Features not to find in cm at the moment:
sswap support (using sswap binary for utilizing the swap partion of chagallwifi)
init.d support
modulized kernel and module loading support through init.d script 01moduleload
Known Issues
MHL has no sound and wrong colors
If you map MENU to a capacitive key (no matter if key itself or "long press", it will not work - workaround: do not map MENU to anything at all, then the apps are forced to show action overflow menu (aks 3 dot menu) - works on some apps (i.e. bootloguptime) on others not.
Some minor crackling when using bt-audio the same time as 2.4GHz wlan (5Ghz wlan is issue free).
No real issue, but a not currently supported feature: no onscreen navbar. If you want it - no problem: This is your chance to give something to the community!!! Untill you fixed it, you can use this untested workaround
YOU tell us...
Before reporting issues install the most recent release, read the thread and in doubt do a clean flash. For reporting an issue, please read posting number three
Installation
I recommend official twrp3 build from http://forum.xda-developers.com/showpost.php?p=65594033&postcount=315
Do a nandroid backup (and try at least once a restore to be sure it works - reboot to recovery in between backup and restore)
Download the flashable zip and check md5 checksum
read thread (reread postings 1 to 5)
Always do a "clean flash" as described in posting #2 (if you are already on my cm12 rom you can try a "dirty flash" as described in #2 - if you come from any other rom "clean flash" is mandatory!)
(optional: flash gapps)
Recomended
Third party installations of busybox may affect rom; read this.
opengapps: opengapps.org. I use the nano package for arm, version 5.1, from 20151129 (newer may work - but 1129 is proofed to work, as 0304 - for example - is proofed to be an issue).
On Xposed
Xposed is not supported in this thread: xposed changes systemfiles, so the resulting system is not the origin rom any longer. I don't want to discourage anybody from using xposed with this rom: if everything works, you are fine. If issues occur, clean flash with only gapps installed and reproduce the issue.
Source code
Device: https://github.com/nvertigo/android_device_samsung_chagallwifi
Kernel: https://github.com/nvertigo/android_kernel_samsung_chagallwifi
Binaries: https://github.com/nvertigo/android_vendor_samsung_chagallwifi
Standard build branch is current-12.1.
(Due to heavy work in progress git repositories are not always up to date.)
WARNING: try to not ask already answered questions - this will lead to bad karma, which leads to unwanted side-effects in your life. Kidding, of course - but really try to read the thread.
Changlog and Download
Mirrors are welcome. Thank you in advance!
For cm-12 upstream changelog please consult: http://www.cmxlog.com/12/#
Build 20161118
Fixed Zygote whitelist after the patchup from android security bullentin.
Build with UBERTC/linaro toolchains instead of aosp's stock toolchains.
ROM: https://www.androidfilehost.com/?fid=457095661767116515
MD5: f1a68ffce9144ecb9582a3deea61286d
History
Build 20160123
No changes in device-tree and kernel - just a maintain-release with all the cm changes (12:00 h GMT).
ROM: link follows, as soon as upload has finished.
MD5: b65a084022752fd753ac5286b7085352
Build 20160113
Changelog:
Double tap to wake: fix settings. — nvertigo
BoardConfig.mk: enable BOARD_HARDWARE_CLASS. — nvertigo
powerhal: enable wake_gesture when screen switches off, and disable wake_gesture when screen switches on. — nvertigo
CMHW: Add Double Tap to Wake support (1/2) — Sean Hoyt
Switch to software h264 decoding — Sean Hoyt
kernel: use [email protected]'s deathly kernel again. — nvertigo
proprietary-files.txt: not maintained, therefore extract-files.sh and setup-makefiles.sh are needless. — nvertigo
cm.dependencies: removed; doesn't work with UNOFFICIAL builds. — nvertigo
sepolicy: allow netd module_request and fsetid. — nvertigo
sepolicy: allow hostapd searching in efs_file:dir. — nvertigo
fstab: add length for encryptable footer. — nvertigo
device.mk: fix PRODUCT_AAPT_CONFIG, this should not contain dpi keywords. — nvertigo
CMHW: Add Double Tap to Wake support (2/2
changed to cyanogenmod_chagallwifi_defconfig. — nvertigo
power_profile: Correct values from stock rom — Schischu
Inform vendor/cm that BFQ is in use — Sam Mortimer
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add IKCONFIG and IKCONFIG_PROC as module. — nvertigo
synaptics_dsx: Add double tap to wake support — Schischu
chagallwifi: add support for /proc/config.gz — Sean hoyt
tc300k: Fix blinking of capacitive buttons — Schischu
ROM: https://www.androidfilehost.com/?fid=24369303960684813
MD5: 4b7a25fd16e9c11bf8f73d2f2bf4da3b
Mirror:
https://github.com/nvertigo/android...-20160113-UNOFFICIAL-nvertigo-chagallwifi.zip
Happy Flashing!
Build 20151118
IMPORTANT: from build 201151118 on it is mandatory to use a Lollopop boot loader!!! You can check your bootloader version in a rooted shell (adb shell or terminal): "getprop ro.boot.bootloader" the third last digit has to be "O". A odin --flashable tar for BOJ1 can be found here.
Also I strongly recomend a clean flash this time - sorry, folks.
Changelog:
Changed kernel source: this rom comes with deathly kernel from @deadman96385 (Thanx, dude!).
Changed kernel graphics driver f-rom t6xx to midgard.
Updated mali blobs to Lollipop.-
Fixed missing selinux domains for macloader and sswap.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151118-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
https://www.androidfilehost.com/?fid=24269982086999228 Thanx to @diegocr
http://forum.xda-developers.com/showpost.php?p=63903074&postcount=1617 Thanx to Hannibal226
Mirroring is welcome! Please use Mirror as soon as availible - I'm running out of data volume on my download host!
Happy flashing!
Build 20151113
I'm quite proud to call this build the first non-beta, stable release. As I can tell from the user testing of the last test builds, this is the most reliable, media compatible and nearly issue free combination of the configurations we tested. it has chagalls native kitkat mali blobs. Most of the other blobs are from kitkat, too - only wifi-, bt- and widevine blobs are lollipop. I reverted the introduction od lollipop OMX-blobs, 'cause the lollipop ones were introducing some small issues with media playback.
If you expirience bt-audo issues, when using 2.4GHz wlan at the same time, you can try flashing an other audio_policy.conf from here. Depending on your bt-audio-device, time of day, moonphase and humidity one or an other will give better results.
Changelog:
Update mali blobs to native chagall version.
BoardConfig.mk: derp: fix wrong path. — nvertigo (HEAD -> 121-work
Boardconfig.mk: updated graphics and FIMGAPI settings. — nvertigo
cm.mk: remove \ from last line. — nvertigo
Update to BOJ1: wifi and bluetooth. See also the changes in the vendor-git. — nvertigo
audio: desabled offloading again; makes things worse. — nvertigo
add 48k sampling rate for a2dp — Franco Rapetti
audio: added audio offload. Idea from cm's i9500 git. — nvertigo
BoardConfig.mk: cleanup and beautyfy. — nvertigo
Revert "audio_policy.conf: update from N9005." — nvertigo
Disable journaling on system image for save space — nexor (nvertigo/current-12.1, current-12.1
audio: Fix ril log tag. — Andreas Schneider
hal: audio: Match HAL function prototypes. — Andreas Schneider
Various storage fixes — Sinisa (thermskin
fstab.universal5420: fix vold warnings — Sinisa (thermskin
device.mk: Add permissions for bluetooth and voip — Andrew Tarabaras
Add firmware path for Station, fixes wifi hotspot — Andrew Tarabaras
patches: adjusted OMX-google-ffmpeg.diff to upstream. — nvertigo
audio_policy.conf: update from N9005. — nvertigo
patches: adjusted OMX-google-ffmpeg.diff to upstream changes. — nvertigo
rootdir/etc/fstab.universal5420: enabled the additional use of f2fs for /cache and /data. From [email protected] — nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: http://charlesingo.mine.nu/ftp/nvertigo/cm-12.1-20151112-UNOFFICIAL-nvertigo-chagallwifi.zip.md5sum
Mirror:
http://forum.xda-developers.com/showpost.php?p=63820133&postcount=1594 Thanx to @Hannibal226
Happy Flashing!
Build 20150413
Updated from cm-12.0 to cm-12.1 - cm-12.1 is based on AOSP 5.1. Remeber to update your gapps package to 5.1. I recommend pa gapps pico: http://forum.xda-developers.com/paranoid-android/general/5-1-x-5-0-x-4-4-x-pa-gapps-mirror-t3069879
ROM: http://162.220.240.98/ftp/nvertigo/cm-12.1-20150413-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: bdc8dc0937ac7416bad5314a45896719#
Mirrors:
http://forum.xda-developers.com/showpost.php?p=60089014&postcount=893 Thanx to @Hannibal226
Build 20150331
Another sepolicy fix allows the cm-12.0 bootanimation to show up immidietly on boot. ccode is reverted to 00.
Changlog:
sepolicy: allow surfacflinger to add Exynos.HWCService. — Nvertigo
chagallwifi: init: Do not override init.rc! — Christopher R. Palmer
chagallwifi: init: Remove reference to init.recovery.universal5420.usb.rc — Christopher R. Palmer
Revert "Compile stock and Samsung MTPs together [AndreiLux]" — Nvertigo
Revert "enable CONFIG_USB_ANDROID_SAMSUNG_MTP again." — Nvertigo
Revert ccode to 00. — Nvertigo
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150331-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 7161aed1b89f7190702dc5abe77a6f18
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59820711&postcount=806 thanx to @Hannibal226
Build 20150319
This build has a significant advantage: I fixed sepolicy in a way (see git for details), that it's NOT necessary any longer to flash @Chainfires SuperSU. Init.d is working right out of the box. Also Titanium has fixed its problems with cm's superuser. I have adjusted the OP accordingly, so I recommend you read OP again.
I also worked again on MTP and UMS: UMS is only working without problems, if you DON'T use move2sdvard, 'cause sdcard gets unmounted to present it as mass storage to the device on the other end of your usb-cable. BUT: MTP is presenting internal AND external memory WITH ALL DIRECTORIES and not only media containing directories - so you can use it at least on windows machines as substitute for UMS.
The kernel modifications I introduced with rhe seperate keenel are included in roms kernel, and I set ccode for 2.4GHz to EU.
Changelog:
wifi country code: set ccode to EU for 2.4GHz to enable channel 12 and 13. — Nvertigo
Revert "selinux: make init.d work again." — Nvertigo
sepolicy: allow debuggerd access to mali. — Nvertigo
sepolicy: vold: allow module_request. — Nvertigo
sepolicy: fix init.d support for 01moduleload and 10systemtuning. — Nvertigo
include/linux/sched.h: fix my derp from incomplete conflict resolving. — Nvertigo
defconfig: enable CONFIG_CRYPTO_AES_ARM_BS. — Nvertigo
defconfig: adjusted cyanogenmod_chagallwifi_defconfig after incorparating manta's 5.1 from exynos5420. — Nvertigo
for not in cm tree building: adjust CROSS_COMPILE; can be overwritten on command line. — Nvertigo
HID: input: generic hidinput_input_event handler — David Herrmann
net/compat.c,linux/filter.h: share compat_sock_fprog — Will Drewry
sk_run_filter: add BPF_S_ANC_SECCOMP_LD_W — Will Drewry
ARM: pull in <asm/simd.h> from asm-generic — Ard Biesheuvel
crypto: create generic version of ablk_helper — Ard Biesheuvel
ARM: 8120/1: crypto: sha512: add ARM NEON implementation — Jussi Kivilinna
ARM: 8119/1: crypto: sha1: add ARM NEON implementation — Jussi Kivilinna
ARM: 8118/1: crypto: sha1/make use of common SHA-1 structures — Jussi Kivilinna
crypto: arm-aes - fix encryption of unaligned data — Mikulas Patocka
CRYPTO: Fix more AES build errors — Russell King
ARM: add .gitignore entry for aesbs-core.S — Russell King
ARM: add support for bit sliced AES using NEON instructions — Ard Biesheuvel
ARM: move AES typedefs and function prototypes to separate header — Ard Biesheuvel
ARM: 7837/3: fix Thumb-2 bug in AES assembler code — Ard Biesheuvel
ARM: 7723/1: crypto: sha1-armv4-large.S: fix SP handling — Ard Biesheuvel
ARM: 7626/1: arm/crypto: Make asm SHA-1 and AES code Thumb-2 compatible — Dave Martin
arm/crypto: Add optimized AES and SHA1 routines — David McCullough
ARM: add seccomp syscall — Kees Cook
CHROMIUM: ARM: r1->r0 for get/set arguments — Will Drewry
CHROMIUM: ARM: arch/arm: allow a scno of -1 to not cause a SIGILL — Will Drewry
CHROMIUM: arch/arm: select HAVE_ARCH_SECCOMP_FILTER — Will Drewry
CHROMIUM: arch/arm: move secure_computing into trace; respect return code — Will Drewry
CHROMIUM: arch/arm: add asm/syscall.h — Will Drewry
cgroup: remove synchronize_rcu(
power: Avoids bogus error messages for the suspend aborts. — Ruchi Kandoi
freezer: shorten freezer sleep time using exponential backoff — Colin Cross
seccomp: Use atomic operations that are present in kernel 3.4. — Robert Sesek
seccomp: implement SECCOMP_FILTER_FLAG_TSYNC — Kees Cook
seccomp: allow mode setting across threads — Kees Cook
seccomp: introduce writer locking — Kees Cook
seccomp: split filter prep from check and apply — Kees Cook
sched: move no_new_privs into new atomic flags — Kees Cook
Fix execve behavior apparmor for PR_{GET,SET}_NO_NEW_PRIVS — John Johansen
seccomp: add "seccomp" syscall — Kees Cook
seccomp: split mode setting routines — Kees Cook
seccomp: extract check/assign mode helpers — Kees Cook
seccomp: create internal mode-setting function — Kees Cook
CHROMIUM: seccomp: set -ENOSYS if there is no tracer — Will Drewry
seccomp: fix build warnings when there is no CONFIG_SECCOMP_FILTER — Will Drewry
seccomp: ignore secure_computing return values — Will Drewry
seccomp: use a static inline for a function stub — Stephen Rothwell
ptrace,seccomp: Add PTRACE_SECCOMP support — Will Drewry
seccomp: Add SECCOMP_RET_TRAP — Will Drewry
signal, x86: add SIGSYS info and make it synchronous. — Will Drewry
seccomp: add SECCOMP_RET_ERRNO — Will Drewry
seccomp: remove duplicated failure logging — Kees Cook
seccomp: add system call filtering using BPF — Will Drewry
seccomp: kill the seccomp_t typedef — Will Drewry
arch/x86: add syscall_get_arch to syscall.h — Will Drewry
Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs — Andy Lutomirski
prctl: adds PR_SET_TIMERSLACK_PID for setting timer slack of an arbitrary thread. — Ruchi Kandoi
mm: add a field to store names for private anonymous memory — Colin Cross
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150319-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d3164baca1f11987a61a306f87d7985f
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59573116&postcount=693 Thanx to @Hannibal226
Build 20150310
fix vulnerability to FREAK attack in Browser.apk. Until cm (there are curtently two diffrent suggestions in gerrit to fix this) commits a fix, every rom builder can do this before brunching:
Code:
pushd external/chromium_org/third_party/openssl
git fetch http://review.cyanogenmod.org/CyanogenMod/android_external_chromium_org_third_party_openssl refs/changes/39/90739/1 && git cherry-pick FETCH_HEAD
popd
kernel: gone back a few steps (for details see git). After patching kernel to 3.4.106 and applying some additional commits, I hoped increasing speed and decreseaing battary usage, I realized in many loading cycles, that one or some of the additional commits slightly decrease battery life (the opposide of my intention) - so I removed them again. Sadly I have not the time to examine, which commit really did the bad. I will push the questionable commits in branch "questionable". Everybody can test which commit is the culprit patch. My gut feeling suggests the "squash 'enhanced power efficiency' patch" commit. I would be very thankful for help on testing, 'cause it's very time consuming. You need AT LEAST two complete recharging cycles to make an educated decission. Thanx in advance.
UMS mode: fix write acces to device.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150310-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 77cc7bc67818f1251dcf295482fddd65
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59363050&postcount=578 thanx to @Hannibal226
Build 20150305
Changed wifi countrycode back to 00 (rememner to adjust this to the country code your wifi router is operating in, if expirience wifi issues)
Updated f2fs driver
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150305-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 4229d8df0afd698fe0c10dfaed3327db
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59253368&postcount=540 thanx to @Hannibal226
Build 20150228
KODI/XBMC and some games,no input issue solved.
Power off charging fixed.
Updated kernel to 3.4.106.
Cherry picked some effiziency changes from SkyHigh (thanx to @UpInTheAir
USB UMS mode fixed.
Added mdnie mode setting to init.d/10systemtuning. From: [email protected]
Make wifi 2.4GHz channel 12 (and perhaps channel 13) working again.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150228-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: e6ff3a48b31826cfc5c1e31211062e2e
Mirrors:
http://forum.xda-developers.com/showpost.php?p=59161974&postcount=501 thanx to @Retiredfinally
http://forum.xda-developers.com/showpost.php?p=59175868&postcount=507 thanx to @Hannibal226
http://forum.xda-developers.com/showpost.php?p=59179113&postcount=509 thanx to @Bantryred
Build 20150203
fix move to sd card. (*)— Nvertigo
fix power off charging (lpm charging) partly. (**) — Nvertigo
chagallwifi: sepolicy: Fix denial killing CM's SetupWizard — Christopher R. Palmer
chagallwifi: bluetooth: Fix audit denial — Christopher R. Palmer
sepolicy: fix gpsd: simplify file_contexts; restrict gpsd access to files to the required rights. — Nvertigo
chagallwifi: wifi: Switch to world regulatory domain. — Christopher R. Palmer
(*) Works even if wiping system to do a rom-flash, but be carefull: it takes time. If you have moved some apps to sdcard wait for 10 minutes or so after boot seems completed before logging in. On a test I was impatient and the apps seems to have gone from homescreen (nova) and appdrawer, but after a while they was back in app-drawer and I had to readd them to home screen. If waiting a bit before logging in, everything is in place.
Remember when apps are moved to sd, that a nandroid WILL NOT(!) INCLUDE THE MOVED APPS.
Not all apps are movable. If you move apps, that require root, you will be asked again to allow root (like you just reinstalled them).
(**) power off charging IS working. It charges and does not emergency reboot to recovery any longer. It even shows the sammy charging animation, BUT gpio keys (power, volume and home) do not work. So you can't reboot, while plugged in. You also can't switch on screen with animation again. If you want to reboot, plug off device, then the screen will come on with charging status. Wait til it goes black again, wait for three more seconds, and start your device normally with the power button.
This build is done from the 12-work branches of my three gits. I will push this status to current-12.0 soon.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150203-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 2d0c5826ba5d2ba1d2f3761c5165664a
Build 20150128
fixed selinux for gps
fixed selinux for init.d support works only if you flash @Chainfire's SuperSU
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150128-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: 36bc597e89be0af6233abf4f4824bc69
Build 20150125
fixed netflix
adjusted battary capacity to our 7900 mAH specs
all upstreammcommits till 20150125 18:00 h UTC
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150125-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: ac0d1198c4100b407bcc46a01235c6c7
Build 20150123
Set selinux to permissive for now. This fixes: gps and init.d support. repo synced: 20:00 20150123 UTC.
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150123-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: d5fc4388c383e9b8a5beb9aa67cde5e2
Build 20150121
ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-12-20150121-UNOFFICIAL-nvertigo-chagallwifi.zip
MD5: f2a0a10cd867b34a3d3107ef5640b9c8

Different ways of flashing
Very dirty flash:
flash rom
Dirty flash:
wipe system
wipe cache
wipe dalvik-cache
flash rom
flash gapps
Clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
flash rom
flash gapps
Very clean flash
factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps
[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system
wipe cache
wipe dalvik-cache
wipe data (without wiping /data/media) this resets your settings and deletes your installed apps
wipe internal memory
flash rom
flash gapps
I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.
On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?
I count on users good judgment.

Reporting issues
Before you report an issue
Make sure you have installed the most current build.
Do a "clean flash" as described in posting #2 (do NOT flash xposed: it's not supported - see above #1). Dirty flashes are ok most of the time. But you can never know when "not most of the time" a dirty flash produces issues, so before repprting an issue it is mandatory to perform a "clean flash", just in case...
What an issue report should contain (at least)
The more detailed information is provided, the better I can iron it out. It's not possible for me to hunt down any issue that I can't reproduce or understand, the only way to undestand your issue and it's underlaying dynamic is a logcat. I don't know automagically all usecases of all users.
Detailed description of steps to reproduce the issue.
logcat, while reproducing the issue (as text)
I'll ignore all other reports, 'cause that would be just guessing and begging for information.
How to get a logcat
Go to settings->about tablet and tab build number 7 times to enable developer options.
Go to just enabled settings->developer options and enable root access as well as local terminal
open terminal from app-drawer and type:
Code:
su -
logcat -d >/sdcard/Download/logcat.txt
zip /sdcard/Download/logcat.txt
Now you have /sdcard/Download/logcat.txt.zip - this file is the oxygen to burn down your issue!
provide this logfile with your report. Alternatly you can skip the zipping step and upload the palin text file to paste.bin or dropbox or something like this.

How to build cm12 for chagallwifi
Most important preperation step!
Learn git. Read all the manpages, that come with git. I don't speak of github - thats a nice service I like to use, but working with git means working on the command line. githubs web interface is a lightwight, impotent version of git. Github is great as server to store your projects, but not that what youmwill need the next days... Learn git or go home.
Setting up the environment
Consult the HOWTOs of your distro. You can use any distro to build android on, there is even a HOWTO on setting up an android build environment on cygwin on win. Ubuntu, archLinux and gentoo are known to work and have detailed descriptions on the settup.
I use gentoo with icedtea-7. But as stated: any distro will work, once you have setup your environment.
Getting cm12
Find a place on your harddisc partitions with at least 18 GB free space and appropriate access rights for the user you are building with. Get a shell as this user and get the scm source:
Code:
mkdir cm12 #you can call the dir how ever you want - but whenever I refer to cm12
# as directory in this howto, I refer to THIS directory. I may also use the
# term: cm build root.
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1 # this initiates the repo
repo sync # this fetches the code (quite a couple of GBs - get a laaaarge cup of coffee)
Getting chagallwifi specific gits
Copy the following lines as nvertigo_local_manifest.xml to cm12/.repo/local_manifests/
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="tm"
fetch="https://github.com/TheMuppets/" />
<remote name="cm"
fetch="https://github.com/CyanogenMod/" />
<remote name="nvertigo"
fetch="https://github.com/nvertigo/" />
<!-- save us from the step of extract-files -->
<!-- BLOBS for manta -->
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_audience" path="vendor/audience" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_widevine" path="vendor/widevine" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_broadcom" path="vendor/broadcom" remote="tm" revision="cm-12.1" />
<!-- BLOBS for lge -->
<project name="proprietary_vendor_lge" path="vendor/lge" remote="tm" revision="cm-12.1" />
<!-- BLOBS for oneplusone -->
<project name="proprietary_vendor_oneplus" path="vendor/oneplus" remote="tm" revision="cm-12.1" />
<project name="proprietary_vendor_oppo" path="vendor/oppo" remote="tm" revision="cm-12.1" />
<!-- BLOBS, device tree and kernel for chagallwifi -->
<project name="android_vendor_samsung_chagallwifi.git" path="vendor/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_device_samsung_chagallwifi.git" path="device/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
<project name="android_kernel_samsung_chagallwifi.git" path="kernel/samsung/chagallwifi" remote="nvertigo" revision="current-12.1" />
</manifest>
As you can see, I'm building for more devices then chagallwifi. I've decided to keep this file this way: perhaps it holds a hint on how to save us from extract-files.sh.
After you have put nvertigo_local_manifest.xml in place, make sure all dependencies are there and fetch the additional git repos:
Code:
source build/envsetup.sh
breakfast picassowifi #this pushes the relevant git repos to .repo/local_manifests/roomservice.xml and fetches them
repo sync # this one fetches our additions to nvertigo_local_manifest.xml
Build cm12 for chagallwifi
Now you are ready for build. So let's clean the build environment and fire off the magic to homegrow a cm12 rom for chagallwifi (you guessed it: from cm12 dir):
Code:
source build/envsetup.sh
make -j9 ARCH=arm clean #cleaning from previous build; you have to replace 9 by number of cores + 1
make -j9 ARCH=arm clobber #paranoid; you have to replace 9 by number of cores + 1
time breakfast chagallwifi >make.log 2>&1
time brunch chagallwifi >>make.log 2>&1
# in a second shell: tail -f make.log
make.log is better seacheble then scrolling on terminal. If something goes wrong, search for "Error 1". In the lines before that you can see what breaks your build. On my slightly overclocked amd-fx8150 with 16GB Ram brunching takes about 100 minutes.
Now you have build a flashable rom. Congrats.
Developing
Learn git.
Put the following four lines in your /etc/gitconfig
Code:
[alias]
lg1 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(white)%s%C(reset) %C(bold white)— %an%C(reset)%C(bold yellow)%d%C(reset)' --abbrev-commit --date=relative
lg2 = log --graph --all --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(bold yellow)%d%C(reset)%n'' %C(white)%s%C(reset) %C(bold white)— %an%C(reset)' --abbrev-commit
lg = !"git lg1"
Example 1: You have a fix for the device tree.
Code:
cd device/samsung/chagallwifi
git lg1 # get an impression of the git in treeview; scroll, read, learn the way the source flows
git checkout -b my-branch #you create your own local branch
#edit the files for your fix
#if you add a new file
git add new_file
#if you editied an existing file
git add edited_file
#if you want to remove a file
git rm removed_file
#now each edit is in gits staging area, but it's not commited; to commit it locally:
git commit -em "Fix foobar: foo the bar from... Try to document what you have done and why."
#now the message is taken as title for the commit and an editor opens: you can write in more detail to document your changes.
#if you want to provide such a commit in a way I can use ist
git lg1 # get the hash of the commit you want to provide
git format-patch -1 --stdout hash >/tmp/my-commit.diff
Send me the file - do NOT copy'n'paste the content. That would break tabs and spacing and render the commit unsuable. I will apply the commit with "git am", so authorship remains as well as git history. The latter is important if later one wishes to merge two different gits with simalar commits.
If you decide to keep your own git at this point, go to the github web interface, login with your name (i.e. XXXX), go to my device repository and clone it. Back to your local shell in cm12:
Code:
cd device/samsung/chagallwifi
git remote add yyyy https://github.com/XXXX/android_device_samsung_chagallwifi.git
git fetch yyyy
#remember you have commited your changes locally in your local branch cm-12..0
#the local branch cm-12.0 is setup to follow the branch cm-12.0 of the origin remote git
#but we want the local cm-12.0 to follow the one from yyyy:
git branch --set-upstream-to=yyyy/cm-12.0 cm-12.0
git push
Now you have pushed your local commit to your own remote git. Congrats. Now you write me an email: "Huh, look at my git, it fixes everything and will finally bring peace to earth.... It's in hash." Of course, I want this commit in my repo, and that is
Example 2: Take a commit from an other devs git
Code:
cd device/samsung/chagallwifi
git fetch https://github.com/XXXX/android_device_samsung_chagallwifi.git #I don't want to have this as an additional remote
git cherry-pick hash
...to be continued....

Looking forward to your up coming updates of cm12.:good:

Bushcrafter said:
Looking forward to your up coming updates of cm12.:good:
Click to expand...
Click to collapse
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!

nvertigo67 said:
Me too... Would really like to try my build.
It seems my router/3g-stick is broken:
I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.
I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...
How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:

Bushcrafter said:
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:
Click to expand...
Click to collapse
+1 :good::

nvertigo67 said:
Me too... How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
Click to expand...
Click to collapse
No need to apologize. I doubt the rom development for the tab s would be anywhere close to where it is now without your work.
Now after approx 24 hours of hoping for a cm12 rom that will finally boot on my t805, i almost don't dare to ask if there is a slight chance it will happen this time?

Uh maybe someone (maybe me? I'm trying!) could compile the rom from your GIT and upload it somewhere?

Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD

Moscow Desire said:
Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.
MD
Click to expand...
Click to collapse
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!

nvertigo67 said:
Sorry for the incinvience! Thank you for your help!
Download is up - Known Issues is updated. I will cleanup now and update git repositories.
Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.
Thanx to all for their patience!!!
Click to expand...
Click to collapse
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?

Bushcrafter said:
I will give it a try!:good: Its good to see that you got your router problems figured out!
Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?
Click to expand...
Click to collapse
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.

nvertigo67 said:
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.
Click to expand...
Click to collapse
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.

Yay LP thanks will flash when it's a bit more stable

Bushcrafter said:
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.
Click to expand...
Click to collapse
Synapse don't know anything about a kernel - UKM does. UKM does not support our device. Grep the current version of UKM (i belive there is also a git repository for it), take a look at the device files and jason scripts and modify for chagall. You can do it in a way, that settings not availibale in a given kernel are not shown. Everybody would be glad...
My time is limited and I have made the decision to use my time on cm12 for chagall - I have started the above work. I you really want to develop UKM for us all drop me a note and I will push my work to git. But first of all make yourself familar with UKM and git. Propably it would be usefull to read the UKM thread and contact the developer.

Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:

Screenshot, wait time batery life

maxal said:
Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.
Thanks again :good:
Click to expand...
Click to collapse
Sdcard: read issues section in OP for workaround. init.d support is broken at the moument.
What do you mean with "SuperSU won't update"? Error message? Logcat?

Related

[ROM][DEV][BrickedRom][Feb.02]-[CM9Kang]-[v4]-[KSM]-[Touchscreen-fixes]

##DISCLAIMER##
Though this is tested and I am using this, and nothing evil happened until now, it might slap you so hard in your face that not even google is able to find you anymore.
No kidding: !Experimental! This does not fix one bug of CM9 nor does it attempt to do so. So don't b*t*h me about that. This is meant as a test for KSM, to see if any problems arise and how much use (performance gain / more free ram) this gives on Android. (theoretically it should be very useful)
For everyone who wants to give it a try:
Bricked-CM9Kang v4
based on AOSP CM9 #Kangified
What does it give you:
Everything from CM9 + Touchscreen fixes (Dees_Troy27) + KSM (Kernel Samepage Merging) + fixed init.d script autoexecution on bootup (turl)
Bricked v0.4 with KSM support, Default clocks @ 1566/192 ondemand
- OC up to 1914Mhz, Voltage Control via sysfs (SystemTuner, etc), etc, etc.... Look here.
Install:
Do you want a fresh install? Wipe data/factory reset & just flash from recovery.
Already on cm9 and don't want to loose your data? Just flash over your current install without wiping (don't forget to reinstall gapps afterwards).
Download:
v4
ROM + Kernel:
mediafire.com: Click Me
http mirror: Click me
SHA1: 14db526c93962359995ea260c80d2811ba32eaae
Gapps: Click Me
SHA1: 1d277d2d7e802eb13975757df46c09afbaafcd2c
Gappsfixer: Click Me
This removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it after gapps, there can nothing go wrong)
SHA1: 5b66a2e160922626d67b30b459b5323deb8f549d
#cyanogenmod-touchpad Readme and Gapps:
http://ergh.org/cmtp/
Mirror (Folder by jassycliq):
mediafire.com, adfree: Click Me
What is KSM - Kernel Samepage Merging?
From Wikipedia, the free encyclopedia
Kernel SamePage Merging (KSM) (also: Kernel Shared Memory, Memory Merging) lets system share identical memory pages amongst different processes or virtualized guests. This is done by scanning through the memory finding duplicate pages. The duplicate pair is then merged into a single page, and mapped into both original locations. The page is also marked as "copy-on-write", so the kernel will automatically separate them again should one process modify its data.[1]
KSM was originally intended to run more virtual machines on one host by sharing memory between processes as well as virtual machines. Upon implementation, it was also found to be useful for non-virtualized environments where memory is at a premium [2][3]. An experimental implementation of KSM by Red Hat found that 52 virtual instances of Windows XP with 1GB of memory, could run on a host computer that had only 16GB of RAM [4].
KSM first appeared in the version 2.6.32 Linux operating system kernel [2]. To be effective, the operating system kernel must find similar memory pages held by different processes. As well it needs to decide whether the pages are going to update infrequently enough that SamePage Merging would be an efficient use of processor resources [3]. When first proposed, there were concerns that this feature could be exploit as a security vulnerability (this concern has since been addressed). Another concern is that although memory usage is reduced, CPU usage is increased, thus negating potential increases in performance [1].
References
^ a b "Home Page". lwn.net. kernel.org. Retrieved 2010-08-21.
^ a b "Home Page". IBM DeveloperWorks. IBM. Retrieved 2010-08-21.
^ a b "Home Page". kernel.org. kernel.org. Retrieved 2010-08-21.
^ "Home Page". kernelnewbies. kernelnewbies. Retrieved 2010-08-21.
more to KSM: http://bitcube.co.uk...merging-and-kvm
How to see the Magic happening?
Code:
cat /sys/kernel/mm/ksm/full_scans
cat /sys/kernel/mm/ksm/pages_shared
cat /sys/kernel/mm/ksm/pages_sharing
cat /sys/kernel/mm/ksm/pages_to_scan
cat /sys/kernel/mm/ksm/pages_unshared
cat /sys/kernel/mm/ksm/pages_volatile
cat /sys/kernel/mm/ksm/run
cat /sys/kernel/mm/ksm/sleep_millisecs
or just:
Code:
cat /sys/kernel/mm/ksm/*
to get all at once.
Check your RAM stats with:
Code:
free
Source for KSM implementation:
Android source modifications: Click Me
Kernel source modifications: Click Me
(ofc KSM must be enabled in your kernel config)
Source for Bricked:
Click Me
Thanks to everyone who ever contributed anything (even only a whitespace) to any of the used software.
Code:
[B][U][SIZE="5"]Changelog:[/SIZE][/U][/B]
[B]*** v4 ***[/B]
ROM:
synced with CM9 repo @ 05:04 PST 31/01/12
KSM code cleanup. Testing new configuration
Tweaking KSM, lowering CPU usage
Fixing restore of gapps after install (my fault, c&p was being a b*tch)
Allow reboot to recovery (http://review.cyanogenmod.com/#change,12311)
Allow power options menu (http://review.cyanogenmod.com/#change,12315)
Added CombinedBar Auto Hide (http://review.cyanogenmod.com/#change,12281)
SurfaceFlinger: Set the buffer size in the GraphicBufferAlloc (http://review.cyanogenmod.com/#change,12263)
Preference to disable bootanimation for faster boot (http://review.cyanogenmod.com/#change,12169)
Kernel:
ksm update from bricked-pyra source
Lowered min voltage once again (now: 700mV)
Updated KGSL driver with bricked-pyramid:
msm: kgsl: 8Stages 3D scaling, highest @ 300Mhz (fraction 33)
msm: kgsl: 6stages 2D scaling, highest @ 266,7Mhz, 33,35% Overclocked (fraction 100)
msm: kgsl: GPU off while screen off!
msm: kgsl: improved KGSL suspend
msm: kgsl: Use the correct virtual address for pmem regions
msm: kgsl: Delay 30ms to make sure GPU is ready during resume time
msm: kgsl: Update pwrlevel_change
msm: kgsl: Add sysfs attribute to turn GPU DCVS off/on
msm: kgsl: Early Suspend drivers
msm: kgsl: Turbo Mode
msm: kgsl: Don't check for idle while suspended
msm: kgsl: Make kgsl_idle_check check if a nap is allowed
msm: kgsl: fix parameter checking in adreno_ringbuffer_issueibcmds
msm: kgsl: Abort kgsl_pwrctrl_wake() when in KGSL_STATE_INIT
msm: kgsl: create singlethread wq instead of per-cpu wq
msm: kgsl: Fixing earlysuspend/lateresume for multiple devices.
msm: kgsl: run kgsl_idle_check after resuming a device
msm: kgsl: fix coding derp for init pwrctrl
[B]*** v3 ***[/B]
repo synced with CM9 (18:00 CET, 27/01/12)
touchscreen fixups by Dees_Troy, ts: lower touch threshold to help with light touches
touchscreen optimization by Dees_Troy, remove unneeded code and optimize filter
disable_dock_switch, fixes touchstone freezes, thanks to nomadman
hq bootanimation, by Kevin1981 from #cyanogenmod-touchpad on freenode
new quicksettings options, optimized for tablets, http://review.cyanogenmod.com/12162
External Bluetooth GPS support, http://review.cyanogenmod.com/#change,12095
...and many more stuff from the sync, take a look under settings ;)
[B]*** v2 - installfix ***[/B]
*fix setting Bricked as default kernel.
*delete uImage.CyanogenMod
[B]*** Initial Release - v2 ***[/B]
Based on cm9 a0.5
Touchscreen fix by Dees_Troy27
init.d script on boot execution fix by Turl
KSM support kernel & rom side
_
Nice
Sent from my Touchpad using xda premium
sweet dude. I was wondering when the custom ROMs would start showing up. East coast so too late to flash tonight but I will definitely try this out tomorrow. Nice work on the kernel btw.
Any sod fixes on this?
Sent from my Galaxy Nexus using xda premium
Bed time now, I will download and install tomorrow. Thanks!
Great stuff! If we are already using your kernel with CM9, can we just wipe and flash this, or is there something more that needs to be done?
OP updated.
v2 - installfix
###########################################
hotts23 said:
Great stuff! If we are already using your kernel with CM9, can we just wipe and flash this, or is there something more that needs to be done?
Click to expand...
Click to collapse
show-p1984 said:
Install:
Do you want a fresh install? Wipe data/factory reset & just flash from recovery.
Already on cm9 and don't want to loose your data? Just flash over your current install without wiping (don't forget to reinstall gapps afterwards).
Click to expand...
Click to collapse
When I saw the word "bricked" I was utterly scared.
Thanks for all your hard work.
Installed and its AMAZINGLY FAST.
But no WIFI working.. Bummer.
Going back to 0.5
Sent from Epic Touch HD with Tapatalk
axiapc said:
Installed and its AMAZINGLY FAST.
But no WIFI working.. Bummer.
Going back to 0.5
Sent from Epic Touch HD with Tapatalk
Click to expand...
Click to collapse
It has wifi Oo
gimme adb shell uname -a please
Or if you installed the v2 without the "installfix" in it's name, just download the installfix one and flash it over, flash gapps, done.
what is the gappsfixer file for?
Sent from my cm_tenderloin using xda premium
brigked said:
what is the gappsfixer file for?
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
It removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it, there can nothing go wrong )
show-p1984 said:
It removes bad <shared-user> elements from packages.xml and lets android regenerate them. This fixes a problem with gapps signatures. (Just flash it, there can nothing go wrong )
Click to expand...
Click to collapse
OK. Thanks for quick response. Just wondering because i didnt see an explanation on the op. Anyways, flashed it and its working great. wifi is working for me. Thanks!
Sent from my cm_tenderloin using xda premium
show-p1984 said:
It has wifi Oo
gimme adb shell uname -a please
Or if you installed the v2 without the "installfix" in it's name, just download the installfix one and flash it over, flash gapps, done.
Click to expand...
Click to collapse
K brb
Sent from Epic Touch HD with Tapatalk
Just flashed over alpha 0 with the hotfixes, no wipe. Got a kernel panic when it finished booting right after I unlocked it. A quick power+home button reboot got me back to normal. Didn't remember to get a log and haven't been able to reproduce it again, so I'll just attribute the bug to not wiping.
Other than that, everything seems to be working very smooth so far! Thank you!
Reflashed and now WiFi uppppppp...
ICS HP Touchpad using Tapatalk HD
it might be early to request, but can we have the option to permanently enable OTA ADB? please?
Good work dude
I'll flash it later in the evening (GMT).
what's the change log for Bricked V0.34 coz dedicated thread states v.0.31 as latest?
Sent from my Desire HD
question about installing:
If I am still on CM7, do I need to use ACME installer to install your rom?
I know you stated that for fresh install we can just use recovery, but for CM9 it was suggested to use acme installer instead of recovery
thank you

bugs with SHV-E210K build (i9300 variant)

I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
/android/omni/device/samsung/smdk4412-common/common.mk
# Set default USB interface
PRODUCT_DEFAULT_PROPERTY_OVERRIDES += \
persist.sys.usb.config=mtp \
ro.zygote.disable_gl_preload=true
Click to expand...
Click to collapse
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?
Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Entropy512 said:
LTE screams "qcom modem" to me - perhaps look at the i9305 tree?
Click to expand...
Click to collapse
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?
kaijura said:
Figured it out, for anyone searching for this problem - the issue has to do with the ramdisk portion of a (custom) kernel as it wasn't matching up omni's init setups.
Tried a i9305 build it was a little worse off (no mobile connection), haha. I'm thinking of submitting for an official build after I figure out the build for a working stock omni kernel.
Since this device gets few attention (maybe less than 50 in the sgs3 forum) is it possible that you guys could set the jenkins buildbot to build like every week or other week?
Click to expand...
Click to collapse
Hmm, that might be a possibility...
kaijura said:
I have Omni booting and running on a E210K (It is a SGS3 Korean variant, only changes are LTE, 2GB and DMB antenna), but some major bugs need fixing. There not much if any device trees for these out there so I have just been modifying the i9300 and it works.
These are probably the major two issues I have for now:
1. without manually adding ro.zygote.disable_gl_preload=1 to the build prop, it won't boot. I noticed this line wasn't in the i9300 builds either, but it's definitely referenced in my builds:
2. Can't adjust the vibration in advanced settings, when I do I get the logcat message below, there is no (very light) feedback because it seems the value is set very low.
If I manually edit the values (by putting it up to 10+) I can get feedback, so it is working.
Code:
I/ActivityManager( 2466): Displayed org.omnirom.device/.DeviceSettings: +428ms
W/DeviceSettings_Utils_Read( 5375): file /sys/vibrator/pwm_val: 2
W/DeviceSettings_Utils( 5375): file /sys/vibrator/pwm_val not found: java.io.FileNotFoundException: /sys/vibrator/pwm_val: open failed: EACCES (Permission denied)
W/DeviceSettings_Haptic( 5375): key: vibrator_tuning
but I have no idea where/how to proceed.
My device tree is up over at:
https://github.com/kaijura/android_device_samsung_e210k
I am using the same omni sources for smdk4412-common and kernel.
Thanks in advance
Click to expand...
Click to collapse
This says u r building a rom.Is it working fine?
thanks

Where to get arm-eabi-5.2-ub and arm-linux-androideabi-4.9-sm toolchain?

To build this rom: http://forum.xda-developers.com/opt.../rom-euphoria-os-1-0-beta-unofficial-t2990338
I need a more up to date tool chain than deployed in the EOS repo:
prebuilts/gcc/linux-x86/arm/arm-eabi-5.2-ub/bin//arm-eabi-gcc
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9-sm/bin/arm-linux-androideabi-gcc
When I change the BoardConfig such that it uses the old toolchains the compiler crashes with an internal error and the only way to to fix it is to turn of optimization form -O3 to -Os or -O1
Hence I would like to compile it with the toolchain the author used.
Where do I get it from?
EDIT: when i go on http://sabermod.com/ i only get an empty page so i need some t3d party download source for i guess arm-linux-androideabi-4.9-sm

[ROM][AOSP/AOSP-CAF][Oreo/Nougat/Pie] Android 9/8.x/7.1 for Xiaomi Mi 2/2S

Although the Xiaomi Mi 2 is almost five years old, and it seems there would never be a working nougat/oreo ROM after ivan stopped the development of his AOSP project, but it's not the truth. As the issue of light and proximity sensor have been fixed, I think most of the system components are stable enough for dialy usage after my couple days tests, so I decide to release the AOSP 8.0.0 to you today.
Install:
Please make sure your phone haven't modified the stock partition. It means my rom only work with the latest miui-dev partition table, so you have to Download lastest Mi 2 Developer tar file and flash using fastboot before install my oreo/nougat ROM . This process will earse all data on you phone, so backup all data before you getting start.
1. flash stock miui developer by fastboot update (http://en.miui.com/a-234.html)
2. flash twrp recovery use fastboot and reboot
3. hold power and volume up key to boot into recovery mode
4. install oreo or nougat ota package
5. wipe data and cache (you have to do this even if you are using ivan's aosp marshmallow/lollipop)
Working:
(Note: I use Mi 2SC with CDMA network support, but I don't have an available CDMA SIM card right now for test, so users with CDMA network might have trouble with RIL)
- Audio (bluetooth headset not test)
- Bluetooth
- Camera
- RIL
- WIFI
- FM
- Sensors
- GPS
Credit/Thanks
Special thanks to ivan for the initial device source tree and his preview works on Mi2 device.
Many Thanks to @AdrianDC @Ziyan for their great work to bring Android Oreo to MSM8960 platform.
Also thanks to @m11kkaa (M1cha) @zaclimon for their projects.
- Xiaomi Opensource Project
- Google Android Opensource Project
- Team LineageOS/CyanogenMod
- Team Omnirom and Team TWRP recovery
- Team Unlegacy Android
Source:
device tree: https://github.com/windbellx/android_device_xiaomi_aries
https://github.com/windbellx/android_device_xiaomi_msm8960-common
kernel source: https://github.com/windbellx/android_kernel_xiaomi_msm8960
vendor: https://github.com/windbellx/proprietary_vendor_xiaomi
Screenshot:
Download
https://mega.nz/#F!naRFGQDR!d9Uv-Maw56vyYsphAj00Kw
Known issues
1. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
2. Selinux status is on permissive status.
Root
1. download all files under superuser
2. reboot to fastboot, flash boot.img
Code:
fastboot flash boot boot.img
3. boot into recovery, mount /system, push su binary and superuser.rc to your phone
Code:
adb push su /system/xbin/su
adb push superuser.rc /system/etc/init/
4. reboot
Gapps
select one way of below
1. flash MindTheGapps-9.0.0-arm-20181119.zip
2. download OpenGapps Pico (Not support other version due to limited space of /system
upload gapps-config.txt and opengapps zip file to the same folder and flash opengapps
Changelog
2019-01-01
* fixed wrong 1080p parameter in AOSP camera, both rear and front camera support 1080P record now.
* fixed wifi hotspot and usb tethering cannot open.
* fixed echo reappear after first call.
* rebase kernel, improve wakeup speed and stability.
* add percent text for offline charging.
* reimport MHL releted code, try to bring up MHL. (not tested)
* QS UI improved for small-size screen.
* keep the crypto name same with AOSP, try to make disk encryption work. (not tested, format /data and storage before encryption if too many files, or get out of memory error and system reboot).
* stop maintaining this device if no critical bug in this update.
2018-11-19
-> Upgrade to Android Pie(CAF 9.0.0), tag: LA.UM.7.2.r1-05300-sdm660.0
-> Features added:1. Privacy Guard(with optional su support, thanks LineageOS)
2. App Firewall(data, wlan and vpn, thanks LineageOS)
3. Showing Network Speed(thanks Jon Haus, ezio84 and other commiters)
4. Launcher with icon pack support(thanks tfitts1212, maxwen, eldainosor and other commiters)​ -> Fix hidden wireless connection
-> Add DRM support (For Netflix, L3 level, not support HD and higher)
-> Try to fix echo in calls again(not tested, report if not working)
===========================================================
Android Nougat/Oreo start
Download Link:
Only twrp >= 3.2.1 works with ROM >= 20180101
https://mega.nz/#F!VKRggSoL!WAFIK45_IFKhnvlK1eyY4w
Known issues:
1. Hidden network cannot connect.
2. APN needs setting manually to use CDMA data network. (?, not sure, need more tests).
3. Not support 1080P camera record due to outdated kernel driver.
4. Selinux status is on permissive status.
Changelog:
2018-11-01
* md5sum: b957fa0274819a09fd81d2af2958cc69
* echo in calls should fix now, only tested VOIP, need more tests(headset, bluetooth etc).
* with echo fixed, an issue related ES310 chip sleeping that make battery draining fast is also fixed.
- Standby battery time estimate: > 5 days.
- Normal Screen on usage: 5~6 hours.
2018-10-21
*md5sum: 8cbfdceb23c3aa6f382f1a9a79c29004
* fix noise in headset mic
2018-10-19
* md5sum: 9304de676e0dd6428db566b072488e3f
* fix echo audio during calls
* performance tweaks, fix too hot when too many heavy background tasks, now enable all 4 cpu cores by default
* HALs and blobs changes prepare for P
2018-09-01
* md5sum: b7e60c0033b526278468a38cb00f373e
* minor updates and stability improved.
* last update as I'm going to remove all 8.1 source, source will update to github as soon as possible.
* I will try to bring up pie once I get free, but no guarantee and no ETAs.
2018-06-16
* md5sum: da677903b4c5092d57e91f0dc2210a90 aosp-caf-8.1.0-20180616-aries-arch.zip
* bring back Privacy Guard and synchronize to latest LineageOS version.
* fixed sometime the device is too hot while too many background apps and optimize screen-on battery usage.
full battery usage estimated:
>5 hours online surfing with wifi opened(moderate usage, no gaming).
2 days standby (45-50 hours).
3-4 hours(?) using cellular data.
2018-05-06
* md5sum:
- b7121d3f95e91350722da01c8dfdea22 aosp-caf-8.1.0-20180506-aries-arch.zip
- 6988262c9f99c00371a1bc238ffbdf26 aosp-caf-8.1.0-20180506-aries-arch-gapps.zip
* fix gps and compass broken in last build.
* revert media profile changes so screen record now works normally.
* bring back Xiaomi usb otg driver. (Not tested, tell me if it not work)
* enable doze correctly.
* reduce battery usage when WIFI turned off.
* thermal and some kernel tweaks.
2018-04-20
* md5sum: e8fc7f3793d820f279580726f2c34e93 aosp-caf-8.1.0-20180420-aries-arch.zip
* this version is NOT compatible with previous ROM, SO CLEAN DATA/CACHE OPERATION IS REQUIRED.
* switch to CAF source(tag: LA.UM.6.6.r1-07200-89xx.0) instead of Google generic repository. This build contains Qualcomm specific enhancements plus some comunity optimizations, so it gives some improved performanence to this old device (especially pictures slipping and system animation). Thanks to AOSPA and AOSP-CAF.
* fix WiFi hotspot, tethering should work fine now.
* fix audio call volume cannot adjust.
* add firewall(app wifi/data restriction) support to oreo(App info -> Data Usage -> Disable all cellular data access/Disable all Wi-FI data access). Port from Lineage/CM, thanks again for their great works.
* add multiple pointers patch.
* add fake signature patch, for some MicroG users.
* update media profiles, remove 1080p option from camera records.
* now the build type is "user", which will disable adb debugging by default, "adb root" also disabled.
* repatch telephony framework for CDMA users(NOT TESTED).
* it's the final update if no serious issues(this update is to resolve the call volume issue).
2018-03-17:
* This version is expected to be the final version and wouldn't update anymore if no critical issues. I hope you can enjoy this one without obstacles. Source will be updated to github in a few days.
* update to 8.1.0_r17
* update audio configuration files so audio should work flawlessly now.
* update power hal and tweak cpu scheduler, try to make a better battery life.
* remove Privacy Guard (seem have unnormal power usage when data connection opened), revert Apps data path tweak, remove addtion Internet/Sensor permissions(it makes Google Setup Wizard FC).
* fix device hangs while trying power on machine in offline charging mode.
2018-01-27:
(NOTE: new kernel might have problems with some device, please attach your logcat, dmesg and top command result(adb shell -> top -> take a screenshot), plus you device model)
(NOTE 2: If you have installed gapps and don't want to clean data, flash gapps after flash the new ROM, before your first boot, or some app will get a FC, unless reinstall the app)
* Revert to old audio hal so that calling audio works with old configs
* Fix some storage access permission issues. Move all Apps data to /sdcard/AppData, so external storage path that apps got will be /sdcard/AppData/<package name>/
2018-01-19:
* fix system crash when openning gps with IPv6 network
* fix the audioserver crash when using a headphone
* fix app crash when not granted WRITE_STORAGE permission
2018-01-17:
* update to 8.1.0_r7
* switch to new kernel base. After almost one month dialy use test, I decide to abandon the old kernel tree and enable new kernel source tree, so Xiaomi aries now share the same kenel base code with sony huashan(https://github.com/AdrianDC/android_kernel_sony_msm8960t). Adrian DC have been working on AOSP/LineageOS of Sony msm8960 platform for a long time, he also is a recognized and trusted developer of LineageOS. With new kernel, I believe it will be more quickly to bring a features-ready and more stable aries ROM to you. Thanks @AdrianDC for his great work.
* switch to new audio/display/media HAL, report if you have any trouble to aduio, video play and records.
* new kernel support new auto sleep and wakeup (instead of earlysuspend), and many other changes to improve deep-sleep in oreo, so it will be a better battery life when phone is idle.
* adopt some code from Lineage to support CDMA data connection. if you want to report RIL releated issues, please attach both full logcat(adb logcat) and radio logcat(adb logcat -b radio)
* fix power menu not shows correctly
* fix some app cannot open again after force stop
* make lockscreen swipe more easier to unlock
* magisk now can boot properly
2018-01-01:
* fix UI performance. (NEED MORE TESTS)
* port Privacy Guard to aosp-8.1, thanks to team Lineage/CM/SlimROMs (Settings > App & notifications > Privacy Guard)
* superuser now is optional
* isolate app data/files on /sdcard (app now saved data to /sdcard/<package name>/ install of /sdcard/, It make external storage root more neat and more secure in some cases)
* fix alarm not work
* disable permission review, or permissions will reset after every updates
* disable liveshot in case of crashing when touched in video record mode
* secondary try to fix CDMA data connection. (Need feedbacks, plus model)
* fix setting lockscreen pin/pattern nonresponse
* update battery data, try to fix battery value reset. (NEED TEST and FEEDBACK)
* update twrp to 3.2.1
2017-12-09: (Download from here #65)
* Update to 8.1.0_r1
* Enhance security and privacy settings (many thanks to thestinger and CopperheadOS)
** I have added Internet permission and enable permission review for app with targetSdkVersion < 23, If you are not a clean installation, some app might get a FC. Reinstall app and give the permissions(PHONE OR INTERNET) can solve problem.
* Fix Mi2s 32gb with 13MP camera. (NEED TEST)
* Revert kernel gpu driver. Try to solve UI unsmoothly sometime. (NEED FEEDBACK)
* Add CDMA dummy APN patches. Try to solve data connection with CDMA network. (NEED TEST)
* Use old power and charger driver. It works better.
2017-11-19
* initial 7.1.2 and 8.0
Download: OUTDATED! FIND UPDATES FROM CHANGELOG
twrp recovery 3.1.1: https://mega.nz/#!RewDnB5Z!1JaIxJ2-wQpd9BmY1MoqIrt0z9rI2pLg6lKL5Z2lsKg
aosp 8.0.0: https://mega.nz/#!FHpTRCQL!j_Z-XirV12iPhxmnIAWA33W5HB1ca0Mep8lsKSiB10g
aosp 7.1.2: https://mega.nz/#!hTIgGT5a!gfap1JU95VeyfYauYcvlaR-VnHwRLRzklLENMwS2jgs
Great!:highfive:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
lol,cdma 1x can be load ,but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
huo zhuo huda
ziiimy said:
lol,cdma 1x can be load ,but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
You are the first one to make the ril work after M. I think this is exciting.
great!
Can't not connected to hidden WiFi
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
Yes
ziiimy said:
lol,cdma 1x can be load ,but network doesn't
---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
huo zhuo huda
Click to expand...
Click to collapse
Sorry, it wouldn't be fixed as I don't have a CDMA SIM card right now.
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
GuaiYiHU said:
Good work. I'm working on mi2 as well, can I use your rom as a base for fixing the ril? thanks!
Click to expand...
Click to collapse
great my big brother
我是中国用户,小米2太厉害了,居然能用上功能正常的安卓8.0,感谢xda论坛
I am a Chinese user, millet 2 is too powerful, actually able to use the normal function of Android 8.0, thank xda forum
duplicated
-Tex- said:
UI is very unsmooth. After installing gapps got 'setup wizard has stoped' error. Can it be fixed?
Click to expand...
Click to collapse
if you open logcat and got error like this:
Code:
I zygote : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.NativeCrypto>: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/com.android.media.remotedisplay.jar", zip file "/system/framework/com.android.location.provider.jar", zip file "/system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk"],nativeLibraryDirectories=[/system/priv-app/PrebuiltGmsCore/lib/arm, /system/lib, /system/vendor/lib, /system/lib, /system/vendor/lib]]] couldn't find "libgmscore.so"
this is a temporary solution.
1. extract Phonesky.apk and PrebuiltGmsCore.apk from Core/vending-arm.tar.lz Core/gmscore-arm.tar.lz (320/priv-app/PrebuiltGmsCore) in opengapps zip file.
2. extract Phonesky.apk to Phonesky and extract PrebuiltGmsCore.apk to PrebuiltGmsCore use any zip software, or you can run:
Code:
unzip PrebuiltGmsCore.apk -d PrebuiltGmsCore
unzip Phonesky.apk -d Phonesky
the Phonesky and PrebuiltGmsCore folders should like this:
Code:
➜ ls Phonesky
AndroidManifest.xml
android-support-multidex.version.txt
assets
build-data.properties
classes2.dex
classes.dex
com
lib
libs
META-INF
org
res
resources.arsc
Code:
➜ ls PrebuiltGmsCore
AndroidManifest.xml
assets
build-data.properties
classes2.dex
classes3.dex
classes4.dex
classes.dex
com
googledata
HACKED-META-INF
lib
META-INF
org
res
resources.arsc
3. then, push the lib to your phone by adb:
Code:
adb root && adb remount rw
adb shell mkdir -p /system/priv-app/PrebuiltGmsCore/lib/arm/
adb push PrebuiltGmsCore/lib/armeabi-v7a/* /system/priv-app/PrebuiltGmsCore/lib/arm/
adb shell mkdir -p /system/priv-app/Phonesky/lib/arm/
adb push Phonesky/lib/armeabi-v7a/* /system/priv-app/Phonesky/lib/arm/
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
windbells said:
it should works now, tested with gapps nano.
It seem like an uncorrectly odex/install problem, I need more time to investigate it.
Click to expand...
Click to collapse
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
-Tex- said:
Should i do this after installing gapps or do it instead of installing gapps? What about ui smoothness?
Click to expand...
Click to collapse
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Update:
I tried to grab logcat and dmesg to try to find the reason about UI unsmooth.
But the information is too much that I have no idea to find...
So I upload them to my mega.co.nz
logcat:
https://mega.nz/#!KYMVHByT!Mytx_PG8BqhOrMauhr-NtcsqO7Qw7RIw7i2ydJsNj-4
dmesg:
https://mega.nz/#!6UF30KRS!4qzlNs0UFMBHacNX_WsJIrlVmINNsqzVHCYAdkvkaAI
windbells said:
After installing and reboot to system.
If you are still facing ui Smith less after solve the gapps opening, try clean data and cache, if still exists, please attach logcat log and describe you r usecase in a more detailed way, and also, what's your phone model name? 2? 2S? 2S with 13m camera?
Click to expand...
Click to collapse
I will try tomorrow. My phone model mi2sc 16 Gb with 8m camera.
joe820730 said:
I just tried on my Mi2S 16G with 8MP camera,
Almost everything works well, but UI is very unsmooth.
I have 32GB with 13MP camera, but this is my daily use phone, so I don't want try on it.
Click to expand...
Click to collapse
It seems that my kernel not working on 13MP camera, according to the feedback.
I think Mi2S with 8MP camera should work fine as I using 2SC 16GB with 8MP camera. I think it's really smooth after had a data cleaned boot. Even after I installed the opengapps, it's smooth as usual. Can you describe you usecase or record a short video that shows UI stucked.

[KERNEL][O/P/Q] xCG Kernel [Jun 27, 2020]

Code:
/*
* Your warranty is no longer valid.
*
* I am not responsible for bricked devices, dead SD cards, broken touchscreens,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
This is a custom kernel for Redmi 5 designed for simplicity and stability along with few under-the-hood improvements.
Main features:
Miscellaneous backports (of pstore, mm, etc.).
Merged linux-stable (upstream to Linux 3.18.140).
Merged f2fs-stable (upstreamed F2FS).
Merged latest compatible prima drivers (upstreamed Wi-Fi drivers).
Clean, optimized, and minimal imports of code for rosy (based on riva-o-oss branch).
Optimized prima drivers (reduced debugging and unnecessary wakelocks).
Optimized touchscreen drivers (fixed freezing and reduced debugging).
Reduced unnecessary debug and removed useless hard-coded debug.
Compiled with GCC 9.2.1 & "O3" and all code warnings fixed.
Compiler tuned for Cortex-A53 (CPU optimization).
Miscellaneous GPU optimizations.
Memory optimizations.
Full F2FS support.
CRC toggle.
Sound control.
Vibration intensity control.
DriveDroid CD-ROM emulation support.
TTL fixation support.
Wireguard support.
Support for all FAT-based filesystems.
NTFS RW support.
KCAL support.
Miscellaneous config improvements that are not listed here.
Information:
CAF tag kernel: LA.UM.8.6.r1-04600-89xx.0
CAF tag prima: LA.UM.8.6.r1-04600-89xx.0
CPU governors: [interactive], conservative, userspace, powersave, performance.
I/O schedulers: [cfq], noop, deadline.
TCP algorithms: [westwood], cubic, reno.
Compression algorithms: [lz4], lzo.
INITRD compression: [gzip].
Installation instructions:
With a recovery like TWRP:
Download the zip.
Flash it using the recovery's flash function.
You're done, enjoy!
With FKM (Franco Kernel Manager) app:
Open FKM > Flasher > click on "Import a kernel download configuration".
In the dialogue that appeared enter xCG's JSON link that you can find below (copy-paste it).
You're done, enjoy convenient access to everything latest!
Recommended ROMs to use with xCG:
LineageOS 17.1 (baunilla)
LineageOS 16.0 (baunilla)
Downloads:
Latest zip: v4.3.2 (https://github.com/mscalindt/xcg-rosy/releases/download/v4.3.2/xCG-4.3.2-ROSY-Q-20200627.zip)
Changelog: Here (https://forum.xda-developers.com/showpost.php?p=80798487&postcount=2)
TG group: Here (https://t.me/xcgkernel)
List of all releases: Here (https://github.com/mscalindt/xcg-rosy/releases)
FKM JSON link: https://raw.githubusercontent.com/mscalindt/xcg-rosy/fkm-updater/xcg.json
Credits:
osm0sis (for AnyKernel3).
LinuxPanda (for his work on rosy).
baunilla (for his work on rosy).
franciscofranco (for FKM).
And many other people indirectly involved!
XDA:DevDB Information
xCG, Kernel for the Xiaomi Redmi 5
Contributors
mscalindt
Source Code: https://github.com/mscalindt/xcg-rosy
Kernel Special Features: Fixed touchscreen randomly freezing or misbehaving.
Version Information
Status: Stable
Current Stable Version: 4.3.2
Stable Release Date: 2020-06-27
Created 2019-11-05
Last Updated 2020-09-19
Changelog:
v4.3.2 (Jun 27, 2020):
- Reserve less memory for splash_region (was unintentionally increased in v4.3.1).
v4.3.1 (Jun 24, 2020):
- CAF tag LA.UM.8.6.r1-04600-89xx.0 for kernel (no changes affecting rosy).
- CAF tag LA.UM.8.6.r1-04600-89xx.0 for prima.
- Wireguard version 1.0.20200623
- Fixed boot issue on 2 GB rosy variant.
Old changelogs:
v4.3.0 (Jun 23, 2020):
- Wireguard version 1.0.20200611
- Imported missing USB (power-related) code from riva-o-oss.
- Re-upstream from 3.18.124 (LA.UM.8.6.r1-04400-89xx.0) to 3.18.140 (to fix some mismerges).
- Custom upstream (basically backports) of small parts of the FS subsystem.
- Support for all FAT-based filesystems.
- RW support for NTFS.
- KCAL support.
- Miscellaneous fixes.
v4.2.0 (Jun 2, 2020):
- Wireguard version 1.0.20200520
- Imported missing power-related code from riva-o-oss.
- Upstreamed and optimized ashmem.
- Disabled ESD check on ebbg panel (already disabled on touchscreen & other panels).
- Disabled power to panel during idle screen.
- Improved kernel's general reliability.
- Reduced debugging in kernel & prima.
- Reduced cases of frame dropping.
- DDR boost when a new frame is ready to be rendered (optimized DDR usage).
- Support for magic sysrq.
- Various memory-related improvements & mm fixes.
- Many small miscellaneous improvements and fixes.
v4.1.1 (May 10, 2020):
- Wireguard version 1.0.20200506
- Deep sleep fix.
v4.1.0 (May 3, 2020):
- CAF tag LA.UM.8.6.r1-04300-89xx.0 for prima.
- Wireguard version 1.0.20200429
- Ported msm8x16-wcd codec to extcon class.
- Disabled memory controller.
- Improved overall smoothness.
v4.0.0 (April 20, 2020):
- CAF tag LA.UM.8.6.r1-04200-89xx.0 for kernel & prima.
- Wireguard version 1.0.20200413
- New bare-metal GCC 9.2.1 toolchain targeted for Cortex-A.
- Recreated DTS with "100% overlayed content" and some improvements.
- Enabled memory controller for cgroups & page cache.
- Miscellaneous DTS commits from 4.9 CAF.
v3.7.0 (March 30, 2020):
- Wireguard version 0.0.20200318
- Reimported Xiaomi's sound changes to potentially fix any odd sound problems.
- Fixed Xiaomi's broken (on source level) Goodix netlink driver.
- Fixed duplicate flashlight driver probing.
- Disabled CAF's "power aware driver".
- Unlocked CPU min/max freq.
- Now using "O3" level of GCC optimization.
- Miscellaneous fixes.
v3.6.0 (March 11, 2020):
- Optimized memory consumption.
- Miscellaneous small config changes.
v3.5.0 (March 6, 2020):
- CAF tag LA.UM.8.6.r1-04000-89xx.0
- Removed more hard-coded debugging in rosy's touchscreen drivers.
- Removed PPR (per process reclaim), another broken meme from Qualcomm.
- Removed even more debugging in the kernel.
- Disabled KSM (kernel samepage merging).
- Switched back to the usual type of workqueues (bound).
- Miscellaneous fixes and improvements.
v3.4.1 (February 28, 2020):
- Fixed SD card issue.
v3.4.0 (February 27, 2020):
- Wireguard version 0.0.20200215
- Enabled CPUSETS.
- Enabled boosting for CFS tasks.
- Enabled power-efficient workqueue mode.
- Disabled many configs unrelated to rosy.
- Disabled some debug & profiling configs.
- Removed useless dtbs that get appended to the dtb kernel img.
- Removed "adaptive LMK" feature, it is awfully misconfiguring OOM parameters.
- Increased dmesg log size to 256 KB.
- Support for CPU boosting on migration of important threads (known as CPU boost).
- Miscellaneous small config optimizations.
v3.3.1 (February 13, 2020):
- Reduced debugging in prima.
- Disabled ZSWAP.
- Disabled ZCACHE.
v3.3.0 (February 3, 2020):
- Upstreamed prima drivers.
- Miscellaneous DTS changes.
- Miscellaneous touchscreen changes.
- Disabled host ARP offloading in prima.
- Enabled KSM (kernel samepage merging).
- Enabled "front swap".
- Enabled "ZSWAP".
v3.2.0 (January 30, 2020):
- Merged CAF tag LA.UM.8.6.r1-03400-89xx.0
v3.1.3 (January 29, 2020):
- Fixed low sound.
v3.1.2 (January 27, 2020):
- Removed slmk and reverted back to default lmk.
- Wireguard support.
v3.1.1 (January 26, 2020):
- Fixed Magisk not opening/working.
v3.1.0 (January 25, 2020):
- Compiled with GCC 9.2.0 and all code warnings fixed!
- The upstream to 3.18.140 is now based only on linux-stable.
- Now using "Simple LMK" instead of the defalt LMK.
- Vibration intensity control.
- Disabled SELinux audit again.
v3.0.1 (January 19, 2020):
- Fixed animation lag.
v3.0.0 (January 19, 2020):
- Merged android-3.18 (Google's upstreamed 3.18 kernel branch).
- Enabled SELinux audit again.
- Misc small fixes and improvements.
- Rosy's code is now fully based on rosy's latest kernel (riva-o-oss).
- The kernel is now compatible with all ROMs/trees (fixed camera & flashlight).
- Flashing Magisk to keep root after kernel zip flash is not required anymore!
v2.7.1 (January 4, 2020):
- Disabled SELinux audit.
v2.7.0 (January 1, 2020):
- Merged android-3.18 (upstream).
- Miscellaneous improvements.
v2.6.0 (December 23, 2019):
- Merged android-3.18 (upstream).
- Further fixed hotspot issues (fixed no internet).
- Fixed some memory leaks.
- Reduced debugging.
- Optimized several subsystems of the kernel.
- Explicitly defined LZ4 as the default algorithm for ZRAM.
v2.5.0 (December 14, 2019):
- Merged android-3.18 (upstream).
- Fixed hotspot issues.
- CAF tag LA.UM.8.6.r1-02900-89xx.0
v2.4.1 (December 6, 2019):
- Fixed camera issues for specific rosy devices.
- Merged android-3.18 (upstream).
v2.4 (December 2, 2019):
- Some internal changes.
- Merged android-3.18 (upstream).
v2.3.1 (November 21, 2019):
- Added support for TTL fixation.
v2.3 (November 19, 2019):
- CAF tag LA.UM.8.6.r1-02600-89xx.0
- Merged android-3.18 (upstream).
- Updated prima (Wi-Fi) drivers.
- Updated base (small performance and battery improvements to rosy's code).
v2.2 (November 4, 2019):
- Further updated code for rosy.
- Changed default GPU value to 216 MHz.
- Upstreamed to Linux 3.18.140, upstreamed F2FS, etc.
v2.1 (October 26, 2019):
- Removed OnDemand governor.
- Upstreamed CAF tag to LA.UM.8.6.r1-02300-89xx.0
- Updated code for rosy.
v2.0 (October 20, 2019):
- Updated code for rosy.
- Upstreamed CAF tag to LA.UM.8.6.r1-01900-89xx.0
- Dropped NTFS read-write support.
v1.2 (September 15, 2019):
- Added DriveDroid CD-ROM emulation support.
v1.1 (September 14, 2019):
- Upstreamed F2FS.
- Added sound control.
v1.0 (September 11, 2019):
- Initial release.
Nice work bruhh.. keep it update ?
Cool! I'm gonna test it in LOS 17 baunilla
Install only on compatible device/tree for rosy.. I see LOS mentioned but is it compatible with PixelExperience too?
Arsenious said:
Install only on compatible device/tree for rosy.. I see LOS mentioned but is it compatible with PixelExperience too?
Click to expand...
Click to collapse
No.
Bro, did you have telegram channel/group for this kernel ??
Danisp said:
Bro, did you have telegram channel/group for this kernel ??
Click to expand...
Click to collapse
Yes, join the TG group if you want - https://t.me/xcgkernel
How to root redmi5 global? Miui 11 updated thanks
jeeeu94 said:
How to root redmi5 global? Miui 11 updated thanks
Click to expand...
Click to collapse
With magisk, loke in miui10
Download MiUnlock, unlock bootloader and download XioMiTool v2 from internet and follow the instructions and the program will do everything
If you want to do it yourself you just unlock bootloader with mi blocker and download 1.Minimal ADB and Fastboot
2. Twrp.img for ROSY. (Redmi 5) be sure you download the redmi 5 img
Plugin your phone in pc and go in your pc to C:/program files (x86)/minimal ADB and Fastboot and move (or copy) the twrp img in that folder and open command (press windows key and type CMD) in the black screen (if you have never stay in cmd don't scare, is the old way to use the computers, and the actual way in linux )
Type cd C:/program files (x86)/minimal ADB and Fastboot and then pick your phone.
Hold the volume down and power button at same time for 4-6 seconds.
You will see something like FASTBOOT, and a rabbit with an android.
Plug in the phone in pc and in the PC type
Fastboot flash recovery twrp-rosy-3.3.0-0.img (or how is your twrp.img called) and wait 30 seconds
The terminal will tell u something and when it put '' finished " close your terminal and in your phone hold volume up button and power button at same time.
The phone will restart and show you something about TWRP, you are finishing
Reboot System (there is a button for that in twrp) and in android install Magisk manager.apk from internet.
You will see 2 install buttons, press the first and press install
It will download a 5.8 Mb zip press in the notification and open with "copy to..." and copy to SD.
Reboot in twrp (hold up and power again) and tap in install zip, select magisk zip and magisk su binary will be instaled in your phone.
When finished reboot system and open magisk manager and you will see that magisk is installed. Now u have root
If you want to use supersu do the same but instead of flash magisk zip, flash supe su zip. I recommend magisk. As you can see eZ
Happy mod dude!!
New build (v2.3)!
New build (v2.3.1)!
is compatible with rom evolution x 3.3? Android 10.
Jochman10 said:
is compatible with rom evolution x 3.3? Android 10.
Click to expand...
Click to collapse
With the ROM - yes.
With the trees used to build it for rosy - no.
Compatible with havoc 3.0 ?
#Aditya negi said:
Compatible with havoc 3.0 ?
Click to expand...
Click to collapse
No.
compatible with derpfest?
New build is up (2.5.0)!
New build is up (2.6.0)!
After I install the latest kernel, my touch light and camera is not working

Categories

Resources