[KERNEL] Galaxy Tab S 8.4 SM-T700 (klimtwifi) Permissive kernel - T700XXU1ANF7 - Galaxy Tab S Android Development

[size=+2]Samsung Galaxy Tab S 8.4 (klimtwifi) - Stock kernel SELinux permissive mode[/size]
[size=+1]Introduction[/size]
This kernel is built from stock Samsung source T700XXU1ANF7.This kernel will work on a stock, rooted Tab S 8.4. In addition, I run EMSPilot's NF9 ROM, so this kernel also works perfectly fine on his ROM. Thanks EMSPilot for the great ROM.
[size=+1]Features[/size]
The kernel is completely stock except for the activation of kernel configuation options allowing SELinux to be disabled and the mode to be changed from enforcing to permissive at runtime. It also supports the boot parameter androidboot.selinux=permissive and enables adb insecure in the default.prop in the ramdisk.
[size=+1]Installation instructions[/size]
To install this, use Odin 3.09 to flash the SM-T700-permissive.tar.md5 image using the AP button. DO NOT USE THIS KERNEL ON ANY DEVICE OTHER THAN A SM-T700 KLIMTWIFI. You are responsible for your own device and I make no warranty for this kernel. Flash at your own risk.
[size=+1]Changelog[/size]
Code:
Current changelog: 10-22-2014
[new] Add permissive mode configuration to stock kernel sources
[size=+1]Downloads[/size]
Download link: SM-T700-permissive.tar.md5
Github link: https://github.com/dl12345/SM-T700
[size=+1]FAQ[/size]
Q. Will this trip the Knox flag
A. Yes. Any kernel not signed by Samsung will trip Knox
Q. What Exactly are the changes between this kernel and a stock kernel
A. See below
KERNEL CONFIGURATION CHANGES:
Code:
[[email protected] SM-T700_KK_Opensource]$ diff -Naur klimtwifi_00_defconfig.orig klimtwifi_00_defconfig
--- klimtwifi_00_defconfig.orig 2014-10-18 00:19:42.588511921 +0100
+++ klimtwifi_00_defconfig 2014-10-18 00:19:06.526512090 +0100
@@ -569,6 +569,13 @@
CONFIG_LSM_MMAP_MIN_ADDR=4096
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_SELINUX=y
+CONFIG_SECURITY_SELINUX_BOOTPARAM=y
+CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
+CONFIG_SECURITY_SELINUX_DISABLE=y
+CONFIG_SECURITY_SELINUX_DEVELOP=y
+CONFIG_SECURITY_SELINUX_AVC_STATS=y
+CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
+
# SE Android Network Access Controls
CONFIG_NETWORK_SECMARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
SELinux is forced into permissive mode at boot time through an addition to the init.rc script
INIT.RC CHANGES
Code:
[[email protected] bootimage]$ diff -Naur ramdisk.orig/init.rc ramdisk.new/init.rc
--- ramdisk.orig/init.rc 2014-10-16 23:27:10.680401045 +0100
+++ ramdisk.new/init.rc 2014-10-18 01:01:45.049925094 +0100
@@ -631,6 +631,13 @@
## Daemon processes to be run by init.
##
+
+# Force SELinux into permissive mode
+service sepermit /system/bin/setenforce 0
+ class main
+ user root
+ oneshot
+
service sysmon /system/bin/sysmon
class core
user root
adb insecure is enabled in default.prop
DEFAULT.PROP CHANGES
Code:
[[email protected] bootimage]$ diff -Naur ramdisk.orig/default.prop ramdisk.new/default.prop
--- ramdisk.orig/default.prop 2014-10-16 23:27:10.669399628 +0100
+++ ramdisk.new/default.prop 2014-10-13 03:29:24.756527060 +0100
@@ -2,9 +2,9 @@
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.security.ams.enforcing=1
-ro.secure=1
-ro.allow.mock.location=0
-ro.debuggable=0
-ro.adb.secure=1
+ro.secure=0
+ro.allow.mock.location=1
+ro.debuggable=1
+ro.adb.secure=0
persist.sys.usb.config=mtp
ro.smps.gain.spk=3.0
[size=+1]Thanks To/Credits[/size]
EMSPilot for his NF9 ROM
XDA:DevDB Information
SM-T700 SEPERM, Kernel for the Samsung Galaxy Tab S
Contributors
dl12345
Kernel Special Features: SELinux runtime mode change enabled
Version Information
Status: Beta
Beta Release Date: 2014-10-22
Created 2014-10-22
Last Updated 2014-11-08

Thank u for this! I'm Gunna give it a try here tonight!

Thanks d12345 and to emspilot!

Thanks for sharing your method. Much appreciated.
I currently use a dirty RAMDISK method with my Tab S kernels and a hardcode source method with my Note Edge kernel. I look forward to trying this way next kernel i compile for test.
The dirty way actually removes the SELinux from about device in settings, where the hard-coded way just changes it to "permissive" but is permanent.
Does your way change the devices settings and visible, or is it removed all together (check status with getprop) ?

Thanks man this kernal gave me access to use my wireless xbox controller awesome man!

Ccieslin said:
Thanks man this kernal gave me access to use my wireless xbox controller awesome man!
Click to expand...
Click to collapse
Do u have a thread u found or any info on getting that to work?

freddy0872 said:
Do u have a thread u found or any info on getting that to work?
Click to expand...
Click to collapse
Hi yes I posted in this thread http://forum.xda-developers.com/galaxy-tab-s/help/gamepad-game-controller-t2820410

Worked great!

Hi, this kernel can be used with a 6.0.1 marshmallow rom?

"seandroid not enforced" and bootloop in recovery
sm-t700 wifi, non-system rooted (rooted but not a system root)
how the title, I installed the selinux permissive with odin (ap)
restarted to enter twrp and saw "seandroid not enforced" red, wrote up/left display,
wiped dalvik in twrp and restart to system, and always twrp,
tried to restart to system again, and twrp a new time..
I am recovering now (i saved boot too, in backup), hope to solve..
-------------------------
refresh, solved with full backup.
knox was completely off.. probably this permissive linux is not good for
marshmallow 6.01 or for this tablet particular firmware..
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
gnmmarechal said:
Worked great!
Click to expand...
Click to collapse
have lollipop?

Related

[Q] Kernel Fails To Boot With Increased Version In Makefile

I have been woeking on a custom kernel I will be releasing shortly but I am having a problem with it. Everything works great with it but when I change the kernel version # and attempt to boot it freezes at rhe samsung screen. I tried insmod -f and compiling with modversions enabled and it continues to freeze and I do not know how to pull a /proc/kmsg during a failed boot to find out as adb does not appear to be active. I suspect a module is barfing at the higher kernel version #. Anyone have a suggestion?
Don't change it.
Its a problem several have had, but with no clear solution yet.
Solution found
Hex edit binary modules from samsung with current required source version...not kosher but it boots and plays well with others. Use my soon to be released kernel as an example.

(CLOSED) [KERNEL] ULTRA Kernel Installer

ULTRA Kernel installer is an AIO kernel tool that uses AROMA installer (what's that?).
This tool is capable to backup, install ULTRA kernel, and restore a kernel backup.
Make a Nandroid backup before using it, to stay safe.​
ULTRA kernel features​​
+ OC support
+ Lot of governors and schedulers added:
-- New governors --
Hotplug
ZZmove
OndemandQ
LulzactiveQ
Smartassv2
InteractiveQ
-- New schedulers --
BFQ
ROW
ZEN
VR
+ PhilZ Recovery (what's that?). Thanks Phil3759!​
DOWNLOAD
Android File Host
Dev-Host​​
Thanks @iiD4x for the idea and logo. And @AndyMcMars!, he spent lot of time on this too.​
​
XDA:DevDB Information
ULTRA Kernel Installer, Kernel for the Samsung Galaxy S Advance I9070
Contributors
t4n017, cocafe, Phil3759, TeamCanjica, TeamNova, AndyMcMars, iiD4x
Kernel Special Features:
Version Information
Status: Beta
Created 2014-03-18
Last Updated 2014-05-28
Changelog
CHANGELOG
20140401 (v4.01)
- Deleted all previous kernels varieties
- Added an all-in-one kernel (called ULTRA)
- Now the installer is compatible with CM-11 users too (choose the right option when prompted)
- UKSM is back (KSM --> UKSM) [testing]
- UKSM now disabled by default
- Added UKSM toggle in Galaxy S Advance settings (advance tab)
- PhilZ recovery updated (v6.25.4)
---x---x---x---
20140328 (v3.28)
- KSM is back (UKSM --> KSM)
- Fixed Aroma FM copy process
- PhilZ recovery updated (v6.24.6)
---x---x---x---
20140325 (v3.25)
- Kernel sources update (lot of performance improvements!)
- PhilZ recovery updated (v6.23.3)
- Script a bit more clean
---x---x---x---
20140323 (v3.23)
- Fixed modules install/restore process. (NOW REALLY!)
---x---x---x---
20140320
- Fixed modules restore process.
---x---x---x---
20140319C
- Now the script will also backup modules files (thanks @darcik for the suggestion).
---x---x---x---
20140319B
- All kernels were rebuilt from scratch
- No more Wi-Fi bug!
- Added Smartassv2, InteractiveQ and Interactive to PLUS (and therefore PLUS+OC) kernel.
---x---x---x---
20140319A
- Temporary deleted PLUS and PLUS+OC due to Wi-Fi bug.
---x---x---x---
20140318
- Initial build
---x---x---x---​
Reserved
Very good, I waiting PhilZ Kernel a long time xD
Thank you!
Well, after lot of test I think the Wi-Fi bug is only happening on PLUS and, therefore, PLUS+OC kernel.
It's weird because I didn't touch anything related to Wi-Fi.
I apologize to those who installed them, and further to those who tried the alternative installation method without result.
I'll built them again from scratch and report back.
"I told you..." :victory:
Is the OC kernel stable? Is it possible to under volt?
fbs said:
"I told you..." :victory:
Click to expand...
Click to collapse
Yes, but lot of user reported PLUS was working fine. Maybe they thought they were installing PLUS but instead, they were restoring the default kernel backup.
marlock87 said:
Is the OC kernel stable? Is it possible to under volt?
Click to expand...
Click to collapse
Not all the Advances can handle the same freq, you should try if you can OC without reboots.
It should be, but I didn't tested UV. If you do, please report
Philz Kernel working fine in RR 5.0.5
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
wingryder said:
i flashed philz kernel on cm11 05/03 build(dalvik runtime).it installed fine but after restarting i always get process.android,phone has stopped.even factory reset including wipe dalvik cache wouldnt resolve the issue.flashing the beanstalk rom since i wanted to try it out anyway.the recovery work fine though including power off(the feature which is actually why i installed it in first place).anyways thanks bringing the kernel for our device and hoping to see more development:good:
Click to expand...
Click to collapse
for now , PhilZ wont work on CM ..
I get the "process.android,phone has stopped" error after installing (wipe cache, wipe, dalvik, install zip), and I used the DEFAULT kernel. Why?
I use Carbon KitKat rom,
So happy to see this topic, thanks for posting!
GREAT NEWS!​​
I've built all the kernels from scratch, now Wi-Fi bug is fixed! Please test and report.
Check changelog for more changes.​
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
elementbt said:
Are these kernels supposed to work with the i9070-P version??? Just to be sure...
Click to expand...
Click to collapse
Yes ofc, when you flash a ROM (like RR) you're using the DEFAULT kernel posted here.
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
darcik said:
Just installed DEFAULT KERNEL and I get the "process.android,phone has stopped" error.
Nothing helped.
CM 11 by Macław.
Click to expand...
Click to collapse
It seems that the kernels aren't working fine on CM 11. I don't know why, but I'll ask TeamCanjica for help.
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
darcik said:
Tnx for fast answer.
Btw, your script is making backup of kernel and coping new modules to system/modules folder,
but if is needed restore old kernel, modules files are new and is problem because they are not working with old kernel
Good, that I did myself copy of these files.
Click to expand...
Click to collapse
Thanks for report bro!, I forgot the modules backup. Anyway you can use DEFAULT kernel to restore them.
But I'll edit the script to backup those files and I'll re-upload them.
Really thank you!

[DISCONTINUED][ROM][UNOFFICIAL][UBERTC/linaro]nvertigo-cm-12.1 for SM-T800 16gb

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?

KERNEL][7.0][SM-G570F (J5 PRIME)] MutantKernel v2 by AlexVolzsk

MutantKernel v2​
LZ4 Compression
Disabled KNOX & TIMA
One click SELinux status change through OKM
TCP Algorithms
Working S-Health
Disabled CRCs (30% performance boost)
Enable NTFS support
Disabled Forced File Encryption
Disabled Secure Storage
Disabled DM_VERITY
Fake knox 0x0
Enable F2FS support
ADB FIXED & Logcat Working at boot
Status: Stable
Current Stable Version: v2
Kernel version: 3.18.14
Google disk | MEGA
Does this work on y variant?

Fine OS Custom Rom Version-7 For J7 Nxt-Core-Neo By Abdullah AL-Noman

------- Fine OS Custom Rom Version-7 For J7-Nxt-Core-Neo . Exynos 7870
............Feature...........
# Based On J701F Pie 9
# One Ui 1.1
# Binary 8 Firmware .
# Latest Security Patch
# 1 November 2019 Security Patch
# De-Knoxed
# Debloat
# All Latest App Included
# Recycle Bin Supported File Manager App
Special Feature
# Supported One Ui 2.0 Apps Included
# Show Data Speed Enable Menu On Status Bar
# Vpn Suported
# Busy Box Included
# Magisk 20.3 Included
# Twrp 3.2.1 Included
# Oem Lock Disabled
# Mock locations - Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
# Secure flag - Allow screenshots/screensharing in secure apps.
# Signature verification - Disable signature verification allowing modification/execution of signed system apps.
# Signature spoofing - Enable signature spoofing app permission.
# Added Screen Capture And Screen Record On Status Bar
# Call Record Allowed By Call App
# LTE Only Option
# Show LTE on 4G Network
# Enable Use Mobile Data Option During Call On Settings
# Enable Google Face Lock Option On Smart Lock
Kernel Information
Kernel Name - Oxygen Kernel Version- 4.0.138
Kernel Creator- Siddhant Naik
# Selinux Status - Permissive
# Binary Lock Disabled
# No Problem For Mount Data Partition And Internal Storage
................... What's New ...............
# Fix wifi
# Add New Charging Logo
# Add J7 Nxt White Boot Logo
XDA:DevDB Information
Fine OS Custom Rom Version-7 For J7 Nxt-Core-Neo By Abdullah AL-Noman, ROM for all devices (see above for details)
Contributors
Abdullah AL-Noman
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest Bootloader
Based On: Samsung One Ui
Version Information
Status: Stable
Current Stable Version: Version-7
Stable Release Date: 2020-03-03
Beta Release Date: 2020-03-03
Created 2020-03-02
Last Updated 2020-08-26

Categories

Resources