Related
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
alfsamsung
P880-dev
csk1jw
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Device: platform_device_lge_p880 | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20151122:
AOSP 5.1.1_r29 branch up to 2015/11/21
20151121:
p880: kernel: various upstream changes from android-6.0.0_r0.4/5 branch (thanks to @csk1jw)
p880: ril: cleaner and lighter patches (thanks to @csk1jw)
p880: gps: cleaner and lighter patches (thanks to @csk1jw)
AOSP 5.1.1_r13 branch up to 2015/11/20
20150826:
p880: kernel: enable cleancache, remove cpu boost driver
p880: kernel: mm: frontswap: core frontswap functionality
AOSP 5.1.1_r13 branch up to 2015/08/26
20150824:
frameworks/base: fix wakelock issues
p880: set zRAM values with LZ4 and 256MB of RAM
p880: kernel: enable SWAP and LZ4
AOSP 5.1.1_r13 branch up to 2015/08/24
20150714:
frameworks/base: fix GPS for old GPS HALs along with @csk1jw patches
AOSP 5.1.1_r8 branch up to 2015/07/14
20150625:
p880: cm-12.1 kernel branch rebase
AOSP 5.1.1_r1 branch up to 2015/06/25
20150423:
AOSP 5.1.1_r1 branch up to 2015/04/23
20150406:
p880: restore old 'Recent Apps' behavior
AOSP 5.1.0_r3 branch up to 2015/04/01
20150327:
AOSP 5.1.0_r3 branch up to 2015/03/27
20150318:
p880: android-5.1.0_r1 bringup
AOSP 5.1.0_r1 branch up to 2015/03/17
20150123:
p880: revert any update from 2015/01/18
p880: update spn overrides (v3)
P880-dev cm-12.0 branch up to 2015/01/18
AOSP 5.0.2_r1 branch up to 2015/01/23
20150122:
p880: update spn overrides (v3)
P880-dev cm-12.0 branch up to 2015/01/22
AOSP 5.0.2_r1 branch up to 2015/01/22
20150121:
@alfsamsung: p880: prop: reduce ro.ril.wake_lock_timeout and misc cleanup
@alfsamsung: p880: SE policies: allow init to start lgsecclk and set radio props
@alfsamsung: p880: ril: cleanup
frameworks/opt/telephony: implement UICC TLV Data decoding
p880-dev cm-12.0 branch up to 2015/01/21
AOSP 5.0.2_r1 branch up to 2015/01/21
20150120:
frameworks/opt/telephony: Revert: implement UICC TLV Data decoding
p880: add spn overrides
P880-dev cm-12.0 branch up to 2015/01/20
AOSP 5.0.2_r1 branch up to 2015/01/20
20150118:
build: prevent recovery partition to get replaced
frameworks/opt/telephony: implement UICC TLV Data decoding
P880-dev cm-12.0 branch up to 2015/01/18
AOSP 5.0.2_r1 branch up to 2015/01/18
20150117:
p880: update patches method
@P880-dev: p880: audio_effects adjustements
@P880-dev: p880: fix NFC
build: ota: remove cruft
frameworks/native: compatibility work around for bad graphics driver dependency
hax: Add back the SURFACE_SKIP_FIRST_DEQUEUE legacy EGL workaround
p880: fix RIL typo
@P880-dev: p880: add missing cam include
@P880-dev: p880: add 48000 a2dp sampling rate
@P880-dev: p880: update AudioWrapper to fix video recording
@P880-dev: p880: update SE policies
surfaceflinger: squashed fixes for additional hwrotation
libgui: squashed commits for MR0 devices
frameworks/base: fix GPS for old GPS HALs
P880-dev cm-12.0 branch up to 2015/01/17
AOSP 5.0.2_r1 branch up to 2015/01/17
20150111:
binder: add legacy MemoryDealer constructor for Nvidia OMX adaptor
p880: enable ffmpeg decoders
p880: revert audio primary outputs updates
libgui: add pre-MR2-compatible symbol for setPosition and setOrientation
libutils: refbase: jellybean mr1 compat
p880: temporary revert few overlays
frameworks/base: reintroduce button-backlight (and respective inactivity timeout)
@alfsamsung: p880: SE policies updates
@alfsamsung: p880: GPS fixes
@P880-dev: p880: update RIL for 5.0
@P880-dev: p880: GPS fix and config cleanup
P880-dev cm-12.0 branch up to 2015/01/10
AOSP 5.0.2_r1 branch up to 2015/01/10
20150107:
build: use an updated apns-conf.xml version
p880: include MMB vendor
build: bring back Camera2 into the package
libutils: put back the unused virtuals in Vector<>
telephony: SignalStrength: hotfix GSM and TD-SCDMA
init: add a mechanism to extend the property service in device configs
telephony: RIL: squashed support for old RIL
bionic: linker: enable support for non-PIE executables
libbt: add support for board-specific configuration
p880: patches: correct frameworks/opt/telephony repo path name
telephony: RIL: make RIL subclassable
telephony: allow a device to include its own RIL subclass
build: exclude Home launcher
frameworks/av: stagefright: add legacy MediaBuffer::acquireBuffer symbol
build: include Launcher3 and Camera2 modules by default
p880: temporary revert few overlays
camera.tegra: fix camera_common.h include
frameworks/av: libstagefright: extended media support via FFMPEG
bionic: linker: avoid logcat warning with pre KK/LP blobs
build: prevent zip to replace recovery partition
build: do not report an error if building with Sun JDK
build: include kernel inline build
build: make OUT_DIR an absolute path
p880: add patches support
P880-dev cm-12.0 branch up to 2015/01/03
AOSP 5.0.2_r1 branch up to 2015/01/06
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
XDA:DevDB Information
AOSP Lollipop, ROM for the LG Optimus 4X HD
Contributors
MoltenMotherBoard, streambinder
Source Code: https://github.com/MoltenMotherBoard/platform_local
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Created 2015-01-07
Last Updated 2015-08-26
Hey. I'm the project mantainer. Again.
Just to ping it:
streambinder said:
First of all, it's my first thread here: then, I don't want to be overbearing in offering my work, never.
If I would ever result like that, please tell me.
About the project: my team has always followed AOSP projects, even with ARMv6.
This time I decided to work on it, for this phone, as I need bugfree sources even for it, as for all the others custom ROMs.
The build shared is only the result of the first compilation, quickly tested by me.
I would like to ask you to test and report any bug you experience, so that we can reach as soon as possible a bugfree release.
Click to expand...
Click to collapse
This time, I've something else to tell you.
The build is now uploading is pretty stable and the only issues that are affecting it are the ones listed above (as NFC continously crashes, I excluded it from the build).
Updates will come, do not worry, but tomorrow gonna have an exam, and on Monday another one, so... please, be patient.
For testers, have fun with this build!
And... for @fritzcola, this is for you: http://pastebin.com/qUZ9pmKx
Cheers!
Here's a little hands-on clip, made by @EsromG5:
isn't our kernel based on 3.1.x, not 3.0.x?
good job :good:
Flying_Bear said:
isn't our kernel based on 3.1.x, not 3.0.x?
good job :good:
Click to expand...
Click to collapse
Sorry, my mistake.
Anyway, build is up!
Just flashed rom. Feels smooth. Mobile data work without issue for now:good:
Issues:
-can't make outgoing calls (major)
-camera(already known)
-no root acces(you can fix that flashing this ---> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
-lack of options (it's early stage, so :good
Install take a little longer just like start(at boot animation) be patient
I still cant place a call like on euphoria rom :/
streambinder said:
Sorry, my mistake.
Anyway, build is up!
Click to expand...
Click to collapse
There are problems with flashing, don't flash it yet guys.It gives an error; I'll edit and add the lines soon
After rebooting into recovery, it was fixed (as far as I can remember the error was about sys/.../tegra3/app mount failed)
It was probably because I mounted sdcard as flash storage via TWRP before I flashed
xperia u20i said:
Just flashed rom. Feels smooth. Mobile data work without issue for now:good:
Issues:
-can't make outgoing calls (major)
-camera(already known)
-no root acces(you can fix that flashing this ---> http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
-lack of options (it's early stage, so :good
Install take a little longer just like start(at boot animation) be patient
Click to expand...
Click to collapse
Thanks for your report:
- can you pull a log? I test every RIL function and everything is working properly on my side, calls too.
- already known.
- not a prio: as you said, you only need to flash a patch.
- can confirm: that's exactly why I love AOSP.
ex0rt said:
I still cant place a call like on euphoria rom :/
Click to expand...
Click to collapse
Can you pull a log? I don't have any problem.
ottomanhero said:
There are problems with flashing, don't flash it yet guys.It gives an error; I'll edit and add the lines soon
Click to expand...
Click to collapse
Did not have any issue while flashing, it only takes a little bit more.
Which error do you have?
streambinder said:
Thanks for your report:
- can you pull a log? I test every RIL function and everything is working properly on my side, calls too.
- already known.
- not a prio: as you said, you only need to flash a patch.
- can confirm: that's exactly why I love AOSP.
Can you pull a log? I don't have any problem.
Did not have any issue while flashing, it only takes a little bit more.
Which error do you have?
Click to expand...
Click to collapse
I can confirm that there is no flashing error.
Log is here...
edit
https://www.dropbox.com/s/clpj7ntf9k5h4x4/2015-01-07_12.34.zip?dl=0
xperia u20i said:
I can confirm that there is no flashing error.
Log is here...
edit
https://www.dropbox.com/s/clpj7ntf9k5h4x4/2015-01-07_12.34.zip?dl=0
Click to expand...
Click to collapse
Have you wiped /system, /data and /cache partitions before flashing AOSP?
And if you have, I saw you restored few backups with Titanium - and/or maybe something else -, have you checked if making calls worked out-of-box.
I suggest you to wipe everything and test it as the first thing you do once ROM boots up.
streambinder said:
Have you wiped /system, /data and /cache partitions before flashing AOSP?
Click to expand...
Click to collapse
yes, i made full wipe. everything except internal sd card
I edited my post, while this is my usual procedure when flashing ROMs (first mount as USB storage, then copy over and flash) it was seemingly fixed by rebooting to recovery and attempting to flash again.
xperia u20i said:
yes, i made full wipe. everything except internal sd card
Click to expand...
Click to collapse
Have you edited anything before testing calls?
ottomanhero said:
I edited my post, while this is my usual procedure when flashing ROMs (first mount as USB storage, then copy over and flash) it was seemingly fixed by rebooting to recovery and attempting to flash again.
Click to expand...
Click to collapse
No problem, dude.
Glad to see it's working for you, too.
@streambinder Feels pretty smooth after a few minutes!!
streambinder said:
Have you edited anything before testing calls?
Click to expand...
Click to collapse
No, installed rom and gapps (pa gapps) enter email, and flash super su, but maybe i flashed after that tried to make a call i can't remember exactly-
Nothing of that should messed out things, i think.
fritzcola said:
@streambinder Feels pretty smooth after a few minutes!!
Click to expand...
Click to collapse
Yup, I totally agree with you!
xperia u20i said:
No, installed rom and gapps (pa gapps) enter email, and flash super su, but maybe i flashed after that tried to make a call i can't remember exactly-
Nothing of that should messed out things, i think.
Click to expand...
Click to collapse
Maybe, or maybe not.
I suggest you to try: just flash only the AOSP package - do not with the other you mentioned - and check at first calls.
As I do not have your issues, we'll just try to narrow the possibilities field.
streambinder said:
Yup, I totally agree with you!
Maybe, or maybe not.
I suggest you to try: just flash only the AOSP package - do not with the other you mentioned - and check at first calls.
As I do not have your issues, we'll just try to narrow the possibilities field.
Click to expand...
Click to collapse
ok..my battery is empty now (don't know how ) i'll try to make a test again just with flashed rom, today, if not, tomorrow morning.
I got error while flashing and system doesn't boot here's my error
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Device or resource busy
streambinder said:
Can you pull a log? I don't have any problem.
Click to expand...
Click to collapse
I didn't flashed gapps when I tried it, must say it was really smooth, but I need to call people . Can you recommend me an app for logs and I will try to get it asap.
xperia u20i said:
ok..my battery is empty now (don't know how ) i'll try to make a test again just with flashed rom, today, if not, tomorrow morning.
Click to expand...
Click to collapse
Ok, waiting for your updates.
CrazyWinner said:
I got error while flashing and system doesn't boot here's my error
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Device or resource busy
Click to expand...
Click to collapse
Have you formatted /system before flashing the ROM?
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Also, there are sisters threads for working on pollux, odin and dogo.
Changes:
- Jan 30: Initial release
- Feb 5: kernel updates, audio HAL modernization
- Feb 9: WiFi updates
- Feb 13: volume rocker wakeup, sdcard hotplug, camera focus changes, cleanups
- Feb 16: new call fix
- Feb 27: F2FS support
- Mar 1: audio update
- Mar 3: smooth boot animation
- Mar 6: more audio updates
- Apr 3: first 12.1 build
- Apr 20: radio fixed
- Apr 22: Android 5.1.1
- Apr 27: tons of cpu and gpu governor updates/fixes, wifi updates
- May 1: gpu gov and wifi updates
- May 7: app2sd fixes, selinux updates, fixed power hal, oss thermal mgmt, wifi fixes
- May 10: plethora of core kernel and platform updates, init changes
- May 22: scheduler and platform updates, reworked kernel configuration
- July 1: lollipop blobs, init update, new sensor drivers, kernel updates
- July 7: fixed incall audio
- July 8: fixed black screen on boot, fix booting into recovery by toggling volume keys
- July 9: fixed wlan&bt mac config
- July 11: fixed off charging mode
- July 20: fixed gps problems under certain circumstances
- July 21: lp kernel updates, als adjustments
- July 22: led color configuration from ui
- July 30: gps problems fixed again (duh), leds in off charging mode
- Aug 3: row io scheduler, open source gps hal, sepolicy update
- Aug 6: fix sd card access, fix thermal throttle clearance, update power profile
- Sep 10: (ahead of nightlies) bfq and fiops io schedulers (bfq as default), sony 5.1.1 blobs
- Sep 16: (ahead of nightlies) data, sound fixes
- Mar 30: initial CM13 release
- Apr 6: latest cm fixes, kernel updates
- May 2: init updates, improved mac address handling, new camera, kernel lz4 compression, updated audio and gpu, new browser
- May 9: mac addr fixes, bluetooth fixes, camera wrapper improvements
- May 25: f2fs fix, kernel 3.4.112, init update, ipv6 fix
- Jul 5: loads of kernel changes, audio hal, and probably plenty of stuff i forgot
- Jul 7: underp previous build
- Aug 1: bluetooth and audio updates
- Aug 23: offline charger & kernel & f2fs updates
All builds are synchronized with the latest CM tree. For the specific updates to fusion3 and yuga, see the source link below!
Download:
For the brave CM13 DEVELOPMENT BUILD:
cm-13.0-20160823-UNOFFICIAL-yuga.zip
Dirty-flashing on existing 12.1 upgrades normally to CM 13. Beware you will need compatible GApps though!
CM-12.1 nightlies are available:
Official download site
This thread will however remain the prime location for testing new stuff and support on yuga.
Installation:
If you have anything other than CyanogenMod on your device, do a full wipe, and get compatible gapps!
F2FS support: take a look here
Testing:
Some very important "rules" for this:
- Run unmodified versions (no FOTA recovery, no modified kernel, no Xposed framework, etc.)
- Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least.
- If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
I will have to ignore all other "problem reports" as they are essentially useless.
Thanks:
@andyvdsteen - testing, lending me his phone
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also pollux, odin, and so on).
http://review.cyanogenmod.org
Some screen?
Let's Test
Let's flash it
I will port this to Xperia ZR. Waiting for official builds to be released for Xperia Z and ZR!
Sent from my Xperia ZR using XDA Free mobile app
Please report crash UI...other cm12 crash
---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------
comax70 said:
Please report crash UI...other cm12 crash
Click to expand...
Click to collapse
30 build
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
iKillCypher said:
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
Click to expand...
Click to collapse
if you think it's worth it (and you actually have the illusion that updating blobs is just copying over some files), then please go ahead and do it, test it, and create a pull request. other than that, i would be thankful if you stop nagging me (and other devs) about it in forums, gerrit, and on irc.
iKillCypher said:
Push 10.5.1.A.0.292 Blobs For
https://github.com/TheMuppets/proprietary_vendor_sony/tree/cm-12.0/yuga
Thanks.
Click to expand...
Click to collapse
Hmm review.cyanogenmod.org/#/c/86923/ merged on jan 26
Sent from my Xperia Z using Tapatalk 2
that's my commit, yes. he is talking about blobs, though, not the kernel patches.
anyway, it would be helpful if you guys could test this and report back with things that aren't working.
qsnc
I will test most of your updates for now I need you set selinux to enforcing. yes push blobs 10.5.1.A.0.292 Blobs since you have updated the kernel code based on sony.
after that we can hudson yuga to nightly same for odin
@qsnc
there are random reboot happening for yuga, possible due to the kernel changes you did, It seems to be affecting after 28 builds
also you seems to have set the selinux to enforcing there are some permission and denial you need to look at it seems to have messed up the base band etc
Started using this as a daily . Really nice job dev. Chrome beta sometimes crashed but it's not bothering me that much..
Is a solution to a working BT audio close ?
Mobile signal & data works, but not after enabling SELinux. Currently waiting for build with new policy update.
UPDATE: codereview 87608 and 87609 fixes mobile signal and data, but no "3G" or "H+" on top right corner. There is network activity indicators, though.
Cannot hear or speak in call, even after applying http://review.cyanogenmod.org/#/c/86943/ .
Hexchain said:
Mobile signal & data works, but not after enabling SELinux. Currently waiting for build with new policy update.
UPDATE: codereview 87608 and 87609 fixes mobile signal and data, but no "3G" or "H+" on top right corner. There is network activity indicators, though.
Cannot hear or speak in call, even after applying http://review.cyanogenmod.org/#/c/86943/ .
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/86943/ also needs changes in the hal: http://review.cyanogenmod.org/#/c/86942/, that should help with in-call audio... policy update is on the way.
qsnc said:
http://review.cyanogenmod.org/#/c/86943/ also needs changes in the hal: http://review.cyanogenmod.org/#/c/86942/, that should help with in-call audio... policy update is on the way.
Click to expand...
Click to collapse
Do I need to switch hardware/qcom/audio/default to cm-12.0-caf-8960 branch before cherry-picking this change?
EDIT: nvm, found the correct path. Building.
EDIT2: 86942 and 86943 fixed calling issue!
EDIT3: userinit does not function due to selinux.
from /data/misc/audit/audit.log:
Code:
type=2000 msg=audit(1.010:1): initialized
type=1403 msg=audit(1422959102.743:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1422959102.763:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1400 msg=audit(1422959111.141:4): avc: denied { execute } for pid=273 comm="logwrapper" name="busybox" dev="rootfs" ino=4489 scontext=u:r:sysinit:s0 tcontext=u:object_r:rootfs:s0 tclass=file op
_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.141:5): avc: denied { read } for pid=273 comm="busybox" name="userinit.d" dev="mmcblk0p26" ino=718083 scontext=u:r:sysinit:s0 tcontext=u:object_r:system_data_file:s0 t
class=dir op_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.151:6): avc: denied { write } for pid=275 comm="setprop" name="property_service" dev="tmpfs" ino=5902 scontext=u:r:sysinit:s0 tcontext=u:object_r:property_socket:s0 tc
lass=sock_file op_res=-13 ppid=271 pcomm="90userinit" tgid=271 tgcomm="90userinit"
Hexchain said:
Do I need to switch hardware/qcom/audio/default to cm-12.0-caf-8960 branch before cherry-picking this change?
EDIT: nvm, found the correct path. Building.
EDIT2: 86942 and 86943 fixed calling issue!
EDIT3: userinit does not function due to selinux.
from /data/misc/audit/audit.log:
Code:
type=2000 msg=audit(1.010:1): initialized
type=1403 msg=audit(1422959102.743:2): policy loaded auid=4294967295 ses=4294967295
type=1404 msg=audit(1422959102.763:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1400 msg=audit(1422959111.141:4): avc: denied { execute } for pid=273 comm="logwrapper" name="busybox" dev="rootfs" ino=4489 scontext=u:r:sysinit:s0 tcontext=u:object_r:rootfs:s0 tclass=file op
_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.141:5): avc: denied { read } for pid=273 comm="busybox" name="userinit.d" dev="mmcblk0p26" ino=718083 scontext=u:r:sysinit:s0 tcontext=u:object_r:system_data_file:s0 t
class=dir op_res=-13 ppid=272 pcomm="logwrapper" tgid=272 tgcomm="logwrapper"
type=1400 msg=audit(1422959111.151:6): avc: denied { write } for pid=275 comm="setprop" name="property_service" dev="tmpfs" ino=5902 scontext=u:r:sysinit:s0 tcontext=u:object_r:property_socket:s0 tc
lass=sock_file op_res=-13 ppid=271 pcomm="90userinit" tgid=271 tgcomm="90userinit"
Click to expand...
Click to collapse
make sure you pulled in all the latest updates, especially http://review.cyanogenmod.org/#/c/87609/
should you still have trouble booting, please post it, and ill update the sepolicy.
qsnc said:
make sure you pulled in all the latest updates, especially http://review.cyanogenmod.org/#/c/87609/
should you still have trouble booting, please post it, and ill update the sepolicy.
Click to expand...
Click to collapse
No problem with 87609, because before this I have completely no radio. Phone boots, only custom init scripts (in /data/local/userinit.d, called by /system/etc/init.d/90userinit) isn't invoked at all due to SELinux denials.
Here is the script content if relevant (something like MarketEnabler to enable Google Play Service Location Reporting): https://gist.github.com/hexchain/f4c8a3583abe0214922a
Some other minor problem:
Carrier name does not show on lockscreen left up corner (see attachment), and sometimes there is "No service. - <actual carrier name>".
Hexchain said:
No problem with 87609, because before this I have completely no radio. Phone boots, only custom init scripts (in /data/local/userinit.d, called by /system/etc/init.d/90userinit) isn't invoked at all due to SELinux denials.
Here is the script content if relevant (something like MarketEnabler to enable Google Play Service Location Reporting): https://gist.github.com/hexchain/f4c8a3583abe0214922a
Some other minor problem:
Carrier name does not show on lockscreen left up corner (see attachment), and sometimes there is "No service. - <actual carrier name>".
Click to expand...
Click to collapse
you have something funky in your init scripts... because in the "stock" cm12 init scripts, i removed all calls to logwrapper... are you using old scripts or have you modified them in some way?
the userscript does seem to get invoked, as you can see by the setprop denial it "only" is denied access to set a property... you can find out which exactly by searching for the inode on your phone... anyway i am not aware why a "fake carrier id" script should be required? then again, i dont even have a yuga...
Thanks for the quick reply, and thanks for maintaining CM for yuga!
qsnc said:
you have something funky in your init scripts... because in the "stock" cm12 init scripts, i removed all calls to logwrapper... are you using old scripts or have you modified them in some way?
Click to expand...
Click to collapse
There are still calls to logwrapper: https://github.com/CyanogenMod/andr...2.0/prebuilt/common/etc/init.d/90userinit#L13
the userscript does seem to get invoked, as you can see by the setprop denial it "only" is denied access to set a property... you can find out which exactly by searching for the inode on your phone...
Click to expand...
Click to collapse
The setprop denial is for line 14, relevant file is /dev/socket/property_service. If it really was in my script, there should be 4 denials instead of 1.
anyway i am not aware why a "fake carrier id" script should be required? then again, i dont even have a yuga...
Click to expand...
Click to collapse
As I've said, Location Reporting is disabled by Google in my region (by detecting carrier MCCMNC) so I need this to make it available.
Again, thank you for maintaining CM for yuga!
Can any CM12 users confirm WiFi disconnecting during deep sleep? I need to know if it's my derp or not
SuperHanss said:
Can any CM12 users confirm WiFi disconnecting during deep sleep? I need to know if it's my derp or not
Click to expand...
Click to collapse
it does. but Im kinda used to it, as I got the same problem in CM 11. But this time it seems to happen more frequently. Cant find the option "Wifi Optimization" anymore in CM 12. Disabling it in CM 11 fixed it.
I really need help to fix bugs on 802w running cm12.1
Bug:
- Ii i enable QSEECOM service, surfaceflinger cannot read lib ( memory violation ). How can i make surfaceflinger access library with qseecom enable?
- Failed to call ioctl MSMFB_OVERLAY_PLAY err=Operation not permitted. What is that error? Does it relate to selinux or some security??
you can disable selinux to see what nexts .With my experience the bugs may be caused by it.
To disable selinux in kernel source let change command: selinux is not set (from selinux=y) in config files. You can share my device, vendor tree and which kernel source u using? May be i can help u devs )
ANYKERNEL
espressowifi / espresso3g
Please respect the following 2 points
No feature requests!
Overclocked Kernel can be found here
NOTE:
This product is provided "as is" without any warranty. Use on your own risk.
I am not responsible for burned CPU or GPU.
Any kind of OC is really dangerous on Galaxy Tab2. While OMAP 4460 has a built-in temperature sensor, OMAP 4430 doesn't have one. Nothing stops it from overheating...
If you don't read and respect the OP, you accept to make a donation of 50$ to a charity of your choice!
[#WARRANTY]
It is difficult to update all Roms frequently, and it does not always makes sense to compile, download and flash a whole rom, if only some kernel changes are applied.
This kernel will include changes before i add them official to our kernel source (most of the time security bugfixes)!
Android 5.1 and Android 6.0
This Kernel works on all Android 5.1 and Android 6.0 Roms for espressowifi and espresso3g.
Android 4.4
On Android 4.4 we need a different kernel, 4.4 Kernel includes "KitKat" tag on zip name.
What else to say
Kernel compiled using GCC 4.8
Anykernel based on Anykernel2 by @osm0sis ( https://github.com/osm0sis/AnyKernel2 ) - it will dump your boot.img and replace the zImage and add proper kernel modules.
Roms with default libion
LineageOS (unofficial)
espresso3g
lineage-11-20180131-2053-UNOFFICIAL-espresso3g.zip and newer
lineage-13.0_espresso3g-6.0.1-20180130-2211.zip and newer
lineage-14.1_espresso3g-7.1.2-20180131-1859.zip and newer
espressowifi
lineage-11-20180131-2033-UNOFFICIAL-espressowifi.zip and newer
lineage-13.0_espressowifi-6.0.1-20180130-2146.zip and newer
lineage-14.1_espressowifi-7.1.2-20180131-1818.zip and newer
OmniRom (unofficial)
espresso3g
omni_espresso3g-4.4.4-20180127-2337.zip and newer
omni_espresso3g-6.0.1-20180128-0312.zip and newer
omni_espresso3g-7.1.2-20180128-1319.zip and newer
espressowifi
omni_espressowifi-4.4.4-20180127-2310.zip and newer
omni_espressowifi-6.0.1-20180128-0251.zip and newer
omni_espressowifi-7.1.2-20180128-1254.zip and newer
SlimRoms (unofficial)
espresso3g
Slim-espresso3g-4.4.4.build.9.15-UNOFFICIAL-20180128-0125.zip and newer
Slim_espresso3g-6.0.1-20180128-2332.zip and newer
Slim_espresso3g-7.1.2-20180131-1617.zip and newer
espressowifi
Slim-espressowifi-4.4.4.build.9.15-UNOFFICIAL-20180128-0028.zip and newer
Slim_espressowifi-6.0.1-20180128-2308.zip and newer
Slim_espressowifi-7.1.2-20180131-1555.zip and newer
Unlegacy-Android:
All official Unlegacy-Android builds starting on 15th feburary use the default libion
Roms with new DDK
Slim6 , Slim7, OmniROM4, OmniROM 6, OmniROM 7 and LineageOS 11, LineageOS 13 and LineageOS 14.1 compiled after 01.03.2019
[#DONATETOME]
XDA:DevDB Information
(unified) Anykernel, Kernel for the Samsung Galaxy Tab 2
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/Unlegacy-Android/android_kernel_ti_omap4/commits/3.0/common
Kernel Special Features: Testing before applying on our source official, CVE fixes
Version Information
Status: Testing
Created 2016-10-21
Last Updated 2020-05-02
Reserved
As requested, here's my setup to compile espresso kernel.
01.05.2020
Follow https://github.com/andi34/android_build-bot/blob/manifest/README.md and https://github.com/andi34/android_build-bot/blob/kernelcompile/README.md
What do you need
Kernel Source (you can get our latest kernel source on SlimRoms, OmniRoms or CyanogenMods github, "espresso10 kernel")
GCC ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 )
pvr source, added to omap4-common device repo and hardware_ti_omap4 repo (can be found on SlimRoms, OmniRoms or CyanogenMods github)
you can use my scripts put below (update some paths, marked red )
AnyKernel2 Source from osm0sis (see 1. post, update for your tab2 needed)
build-gcc4.8.env:
Code:
[COLOR="Red"]export CROSS_COMPILE='/android/kernelcompile/arm-eabi-4.8/bin/arm-eabi-'[/COLOR]
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
[COLOR="Red"]export STRIP=/android/kernelcompile/arm-eabi-4.8/bin/arm-eabi-strip[/COLOR]
alias 'stm'='$STRIP --strip-unneeded *.ko'
compile-espresso.sh
Code:
#!/bin/bash
readonly red=$(tput setaf 1) # red
readonly grn=$(tput setaf 2) # green
readonly ylw=$(tput setaf 3) # yellow
readonly blu=$(tput setaf 4) # blue
readonly cya=$(tput setaf 6) # cyan
readonly txtbld=$(tput bold) # Bold
readonly bldred=$txtbld$red # red
readonly bldgrn=$txtbld$grn # green
readonly bldylw=$txtbld$ylw # yellow
readonly bldblu=$txtbld$blu # blue
readonly bldcya=$txtbld$cya # cyan
readonly txtrst=$(tput sgr0) # Reset
err() {
echo "$txtrst${red}$*$txtrst" >&2
}
warn() {
echo "$txtrst${ylw}$*$txtrst" >&2
}
info() {
echo "$txtrst${grn}$*$txtrst"
}
setbuildjobs() {
# Set build jobs
JOBS=$(expr 0 + $(grep -c ^processor /proc/cpuinfo))
info "Set build jobs to $JOBS"
}
info "Kernel source path: $KERNELSOURCE"
info "PVR Source path: $PVRSAUCE"
info "Working directory: $WORKINGDIR"
info "resulting zImage and modules stored at: $WORKINGOUTDIR"
setbuildjobs
info "Moving to kernel source"
cd $KERNELSOURCE
info "Import toolchain environment setup"
info "Toolchain: $TOOLCHAIN"
source $SAUCE/build-$TOOLCHAIN.env
info "Create a buid directory, known as KERNEL_OUT directory"
# then always use "O=$SAUCE/espresso" in kernel compilation
info "create working directory"
mkdir -p $WORKINGDIR
warn "Make sure the kernel source clean on first compilation"
make O=$WORKINGDIR mrproper
warn "Rebuild the kernel after a change, maybe we want to reset the compilation counter"
echo 0 > $WORKINGDIR/.version
if [ "$VARIANTDEFCONFIG" = "*p*" ]; then
info "Import kernel config file: $DEFCONFIGNAME"
info "Import variant config file: $VARIANTDEFCONFIGNAME"
make O=$WORKINGDIR VARIANT_DEFCONFIG=$VARIANTDEFCONFIG $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
VARIANTDEFCONFIG=
else
info "Import kernel config file: $DEFCONFIGNAME"
make O=$WORKINGDIR $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
fi
info "lets build the kernel"
make -j$JOBS O=$WORKINGDIR
if [ -f $WORKINGDIR/arch/arm/boot/zImage ]; then
info "Copying the resulting zImage and modules to: $WORKINGOUTDIR"
info "Creating directory..."
mkdir -p $WORKINGOUTDIR
mkdir -p $WORKINGOUTDIR/modules/system/lib/modules
cp $WORKINGDIR/arch/arm/boot/zImage $WORKINGOUTDIR/
find $WORKINGDIR/ -type f -name *.ko -exec cp {} $WORKINGOUTDIR/modules/system/lib/modules/ \;
info "Files moved!"
info "Pointing KERNELDIR to KERNEL_OUT directory"
export KERNELDIR=$WORKINGDIR
warn "Make sure the PVR source clean."
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Building the PVR module..."
# we now use the default libion, our kernel was updated
make -j8 -C $PVRSAUCE/build/linux2/omap4430_android TARGET_PRODUCT="blaze_tablet" BOARD_USE_TI_LIBION=false BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.1
info "Copying the resulting PVR module to: $WORKINGOUTDIR"
cp -fr $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/system/lib/modules/pvrsrvkm_sgx540_120.ko
mv $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/system/lib/modules/
warn "Don't leave any module objects in PVR source!"
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Properly stripping the kernel modules for smaller size (implified as stm command inside build.env)..."
cd $WORKINGOUTDIR/modules/system/lib/modules
stm
info "####################"
info "# Done! #"
info "####################"
else
warn "####################"
warn "# FAILED! #"
warn "####################"
fi
cd $SAUCE
espresso-m.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.8"
DEFCONFIGNAME=espresso_defconfig
WORKINGDIR=$SAUCE/out/$DEFCONFIGNAME
WORKINGOUTDIR=$SAUCE/$DEFCONFIGNAME-bin
. `dirname $0`/compile-espresso.sh
espresso-k.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.8"
DEFCONFIGNAME=espresso_kitkat_defconfig
WORKINGDIR=$SAUCE/espresso-kitkat
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-espresso.sh
Reserved
DEVICE SPECIFIC ANYKERNEL
Edit 02.05.2020
Latest device specific AnyKernel-Zip can be found here:
https://forum.xda-developers.com/showpost.php?p=79259009&postcount=204
Please note: our kernel detects your Tab2 variant at boot and chooses the right driver and config for your device! In some cases (e.g. if the mainboard or the screen got replaced) your device variant isn't detected right and it will use wrong driver!
I am not sure how many user are affected, but in such case we can skip the intelligent board detection and hardcode the variant.
Attached device specific kernel should work on all unified espresso/espressowifi & espresso3g roms from Android 5 up to Android 7, for Android 4 Roms please use the "kitkat" version.
Feel free to buy me a coconut water if it helped you to keep your Tab still, after many years, almost up to date.
UPDATE AnyKernel-2016-10-21
- Update the ext-csd.rev check for eMMC5.1 (fixes emmc detection for some tab2)
- CVE-2016-5195
- CVE-2016-6828
- CVE-2016-7042
thanks andi.
working nice on my own builded aosp-6.0 10/16
Some more CVE fixes applied on top of previous kernel:
CVE-2014-8173
CVE-2014-7970
CVE-2014-5206
CVE-2016-0819
CVE-2015-8830
CVE-2014-9715
I added a CVE overview on 2nd post.
Edit:
Added a KitKat version
Hi Android-Andi.
Has this kernel the OPTION (or plan to enable) to overclock ?
Thanks.
galoneta said:
Hi Android-Andi.
Has this kernel the OPTION (or plan to enable) to overclock ?
Thanks.
Click to expand...
Click to collapse
No as mentioned in first post! Move out of this thread if you are not able to read first post.
~ All my work, news etc. on http://andi34.github.io ~
Guys, if you don't read the OP the thread will be closed and you can take care about a security patched kernel yourself.
Source is available on github, add everything you miss by your own and stop spamming this thread!
Edit: everyone not accepting the forum rules will be reported!
Edit2: Thanks @ Moderator for the post remove / thread clean
~ All my work, news etc. on http://andi34.github.io ~
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Emo Darkemotion said:
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Click to expand...
Click to collapse
OP states that its already patched
Android-Andi said:
"CVE-2016-5195" https://github.com/Unlegacy-Android/...b19311a9089b77
Click to expand...
Click to collapse
Emo Darkemotion said:
SORRY!
I know its off topic but you should read this
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
Click to expand...
Click to collapse
It is quite funny making noise about a bug which existed 9 years now.
1. It is fixed on my kernel as mentioned on 2nd post (wonder why i spend time doing it)
2. I don't see an issue on custom roms (can be fixed within 2 minutes), i would worry about android by your Manufacturer (on all devices).
On android we change the wheel: no central updates like on linux or windows - it is up to your manufacturer to update your device and there's a lot of security issues fixed by google on android every month (and sure, some kernel side too). How many stock updates you get? 1, maybe 2 within 1 year and support drops after that.
To be true: i am not sure if my next device is an android device:
On my g4 i am on stock rom and LG cares 0 about it (Security patch level 2016-07-01... I waited 6 or 7 month to get that update and it was already 1 month behind).
If manufacturer don't care about theire flagships, what else can we do? Flashing custom roms? Right works, but on my daylie driver i don't like to be a flashahollic... I am more thinking about using a different OS.
You should think about my words and don't care about a already fixed security issue
~ All my work, news etc. on http://andi34.github.io ~
Hi Andy,
First of all, many thanks for all your work! I´m using your ROMs and kernels since Slimkat and all are great!
I also do my best colaborating with the translating team of CyanogenMod and SlimRoms (Brazilian Portuguese).
But now I would like to compile a kernel bymyself, to patch the CVEs, changes I like, etc.
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
Thanks in advance and greetings from Brazil!
AranhaEscarlate said:
Hi Andy,
First of all, many thanks for all your work! I´m using your ROMs and kernels since Slimkat and all are great!
I also do my best colaborating with the translating team of CyanogenMod and SlimRoms (Brazilian Portuguese).
But now I would like to compile a kernel bymyself, to patch the CVEs, changes I like, etc.
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
Thanks in advance and greetings from Brazil!
Click to expand...
Click to collapse
Sure, i have nothing to hide i can upload my script next days. Busy on other stuff atm maybe send a small reminder if the script isn't added on 3rd post of this thread end of next week.
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
Sure, i have nothing to hide i can upload my script next days. Busy on other stuff atm maybe send a small reminder if the script isn't added on 3rd post of this thread end of next week.
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Oh and @Android-Andi just a small request , change the color of the text for ""CVE-XXXXXYYYY" DOES NOT AFFECT" because This colour is hard to read on the screen .
AranhaEscarlate said:
(...)
If you have time, can you post here the steps you do to compile the Anykernel?
Don´t need to waste time explaining the things, just post the step-by-step commands (git clone, makes, ADBs, etc) and I will do my research, ok?
(...)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=69241933&postcount=3
Must be enough, everything else you need to read / find out yourself
iamashwin said:
Oh and @Android-Andi just a small request , change the color of the text for ""CVE-XXXXXYYYY" DOES NOT AFFECT" because This colour is hard to read on the screen .
Click to expand...
Click to collapse
Done, should be better now.
Android-Andi said:
http://forum.xda-developers.com/showpost.php?p=69241933&postcount=3
Must be enough, everything else you need to read / find out yourself
Click to expand...
Click to collapse
Thank you very much, Andy!!!
It´s more than enough!
Everything else, I will read documentation at the Internet, but this is a great starting point for me.
What kind ANY KERNEL is important when you can not clocked CPU and graphics
Kutuzov666 said:
What kind ANY KERNEL is important when you can not clocked CPU and graphics
Click to expand...
Click to collapse
Dont use it if you dont want it!
It is for the kind of people who want a secure kernel ... more secure than the one given by samsung (I dont remember the last time they sent us a patched kernel update ...or did they !)
Nearly all the device I own are waaaay too insecure (be it my router (its also a linux system) , phone Landline TV ...) except for my 4 year old tab all thanks to Andi ! Respect it
Besides OP is doing all this as a hobby and not for your or my benefit.
Stop spaming this thread ! Please READ
Please respect the following 2 points
No feature requests!
Overclocking will never be added here!
If you don't read and respect the OP, you accept to make a donation of 50$ to a charity of your choice!
Click to expand...
Click to collapse
PSS If you are satisfied with the answer please delete the message and so will I .Lets keep this thread clean.
Disclaimer:
Code:
/*
*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
Tags:
To avoid confusion with the OFFICIAL CyanogenMod build tags that include Nightly/Developement (every 24 hours, experimental, newest features, unstable) and Snapshot/Release (every 1-2 months, suitable for daily use, devices signed-off by maintainers for inclusion), these UNOFFICIAL builds have three tags:
STABLE: include tested changes and confirmed bug fixes;
are suitable for daily use.
TESTING: include experimental changes to be evaluated and to possibly fix some issues;
may be used as daily driver only if they don't break functionality or introduce new issues.
VZW-ONLY: same as TESTING builds, but support Verizon variant (VZW SM-N910V) only.
Click to expand...
Click to collapse
Changelog:
For the latest changes and bug fixes, check the 2nd post!
Click to expand...
Click to collapse
Status:
This ROM supports all Snapdragon variants, especially US variants (Verizon / VZW SM-N910V, T-Mobile/TMO SM-N910T, Sprint / SPR SM-N910P, and US Cellular / USC SM-N910R4) and Canadian variant (SM-N910W8). This is only possible because I made major changes to the kernel, init, and frameworks/telephony overlays. Moreoever, the vendor proprietary blobs for VZW variant support both CDMA and GSM networks. So, the device name/model and related properties will reflect the VZW base/blobs.
Check the ROM status in the 3rd post!
Click to expand...
Click to collapse
Kernel:
For stability, this ROM uses ~pure Samsung source code for the kernel with carefully cherry-picked commits from CAF MSM 3.10 source code for APQ8084. A few patches are merged to implement some CMHW features. Moreover, driver updates are integrated from the latest Samsung releases.
Base Source Code: SM-N910V_NA_MM_Opensource_N910VVRU2CPD1.zip
Latest Source Code: SM-N910T_NA_MM_Opensource_N910TUVU2EPJ2.zip
Click to expand...
Click to collapse
I'm also contributing to this kernel repo that will be shipped in some builds for extra features.
Click to expand...
Click to collapse
instructions:
Hit THANKS
Make backup
Do a full factory reset
You should wipe the system partition!
Flash ROM + Gapps ARM 7.1
Gapps nano package is recommended!
Enjoy!
Only for international variants (SM-N910F/G):
>>> Flash RIL/QMI fix from the 3rd post, before flashing Gapps.
Click to expand...
Click to collapse
Notes:
Clean flash (wipe system/data/cache/dalvik) is required.
You need to install nano Gapps for ARM SDK 25 (Android 7.1.1 Nougat) .
You may also need to set default Apps and grant special access/permissions.
In Settings/Apps, click the Settings icon and select "Show system" from the 3-dot menu, as needed.
Make sure that your preferred APNs are selected in Settings/Cellular networks.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
UNOFFICIAL CyanogenMod 14.1 Builds for Samsung Galaxy Note 4
Click to expand...
Click to collapse
Support:
A voluntary work consumes resources and more importantly time!
If you'd like to support the development, you may donate here:
It's fine to just click THANKS or enjoy without saying anything.
A donation is to show appreciation of the work I have done already.
A donation is not by any means in expectation of future work.
A donation doesn't entitle for preferred/private support/requests.
A donation is meant as a gift - always appreciated, never required.
Click to expand...
Click to collapse
If you couldn't donate, you can hit THANKS :good:
Click to expand...
Click to collapse
XDA:DevDB Information
CyanogenMod 14.1, ROM for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910VVRU2CPJ2
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 14.1-20161225
Stable Release Date: 2016-12-25
Created 2016-11-06
Last Updated 2016-12-25
Changelog
Green dates are for STABLE builds, blue dates are for TESTING builds, and red dates are for VZW-ONLY builds. To learn more about build tags, check OP!
You may find a WIP section on top, for what to expect in the coming build. You could vote for a newer build by hitting THANKS to the announcement post of the latest build. For more details, check ROM status in the 3rd post!
All builds include the upstream CyanogenMod changes.
END OF DEVELOPMENT
25.12.2016:
Cleaned up and updated audio configs
Disabled ERI operator string for non-VZW variants
Enabled TTY mode in Telecomm service
Increased gain for camcorder microphone
Increased gain for other mixer paths
Made time daemon MLS trusted subject
Restored contexts for directories during init
Set proper WiFi and bluetooth power configs
Updated operator info for CDMA variants
Updated SELinux policy and addressed denials
23.12.2016:
Added missing camera parameters
Addressed SELinux denials
Created missing init directories
Enabled gesture settings
Falling back to L3 by removing liboemcrypto
Re-enabled fingerprint wake-and-unlock
Updated init and kernel ramdisk
Updated RIL SHIM library
20.12.2016:
Cleaned up and updated media codecs
Created missing log directories
Defined actions to be executed during/after boot
Disabled camera CPP duplication
Disabled nonexistent media decoders
Disabled unsupported Qualcomm's flags
Enabled telephony IPv6 capability
Enabled the setgid bit on directories created by init
Fixed nandroid restores due to telephony data
GPS: Added android_runtime dependency
GPS: Cleaned up and updated GPS/location configs
GPS: Fixed missing Samsung sec-GPS configs
GPS: Fixed "Use of memory after it is freed" warning
Handled framebuffer hint for Ambient Display
Reverted "Allow Flashlight service to use wakelock"
Moved camera service to run on late start
Set appropriate permissions for time data
Toned down VM BMS logging level
Tuned system properties for graphics performance
Updated camera parameters and sysfs permissions
Updated and cleaned up SHIM libraries
Updated audio features and board flags
Updated graphics framebuffers permissions
Updated kernel cmdline for debugging
Updated QMUX daemon socket permissions
Updated Qualcomm's time services
Updated SELinux policy and addressed denials
Used the default number of surface buffers
15.12.2016:
Addressed SELinux denials
Allowed Flashlight service to use wakelock
Built OMX libraries from source code
Cleaned up media codecs from white spaces
Disabled fingerprint wake-and-unlock
Enabled Qualcomm's DivX video decoders
Enabled Qualcomm's MPEG video decoders
Fixed fingerprint/home wake conflict
Fixed Google Home app crashing
Fixed Google Fit app crashing
Fixed graphics and media configs
Moved qcamerasvr service to main class
Re-configured radio access family
Reduced bootanimation resolution to speed up boot
Restricted ERI for CDMA carriers
Updated init services GIDs
Updated media codecs and profiles
Updated/Restored trlteRIL java class
13.12.2016:
Added support for Substratum theme engine
Added system properties for Perf
Allowed all display rotation angles
Allowed interfaces to get v6 address for tethering
Cleaned up and organized system properties
Cleaned up and updated kernel ramdisk
Cleaned up CellBroadcastReceiver overlays
Cleaned up framework base overlays
Cleaned up SELinux contexts and escaped '.' character
Configured VSYNC phase offsets
Created Telephony Provider symlinks for legacy RIL
CyanogenMod 14.1 (Android 7.1.1 Nougat)
Disabled bluetooth by default
Disabled Qualcomm's location stack
Enabled extended video features
Enabled install non-market apps by default
Enabled IPv4 defrag and rpfilter support
Enabled IPv6 defrag and rpfilter support
Enabled PCM audio offload by default
Enabled SAP sensors for GPS use
Fixed MMS sending failure
Fixed offline charging animation
Fixed unknown phone number
Fixed unknown network / operator
Fixed Widevine DRM SHIM library
Forced reading operator-string from ERI XML
Increased maximum readahead to 512 KB
Increased media volume to 30 steps
Increased voice call volume to 15 steps
Moved ERI configuration files to CarrierConfig
Moved time_daemon service to main class
Removed duplicated system properties
Removed obsolete system properties
Removed old-apns-conf.xml APN list
Removed QTI telephony extension
Removed TelephonyProvider APN overlays
Removed unneeded Contacts overlays
Removed unneeded Keyguard overlays
Removed unneeded Messaging overlays
Removed unneeded Telephony overlays
Restored Samsung proprietary boot classes
Restored Graphics/HWC system properties
Reverted the custom bootanimation
Set correct permissions for tombstones
Set device provisioned by default
Set P2P preferred channel list
Set SELinux label for wifiloader service
Switched to CM charger libhealthd
Switched to unified LED capabilities overlay
Use 3 surface buffers to avoid timing issues
Used alternate ERI XML via init
Used HTTPS for GPS/XTRA2 download
Updated blobs (MMB29M.N910VVRU2CPJ2)
Updated all GPS/location configs
Updated and unified MMS configs
Updated build info from N910VVRU2CPJ2
Updated CarrierConfig overlay for all variants
Updated consumer IR HAL
Updated charging thresholds in uW
Updated doze and ambient display configs
Updated eMBMS configuration parameters
Updated media codecs and profiles
Updated Qualcomm's Adreno GPU drivers
Updated IMS/VoLTE proprietary blobs
Updated IMS/VoLTE system properties
Updated NFCEE access for Android 7.x Nougat
Updated servcies GIDs and SELinux labels
Updated SELinux policy and addressed denials
Updated system properties for audio
Updated system properties for media
Updated thermal-engine SHIM library
Updated vibrator/vibetonz sysfs permissions
26.11.2016:
Enabled proximity check on screen wake
Enabled suspend when screen is off due to proximity
Increased the maximum size for MMS message
Reset MMS user agent string and profile URL
Updated AAPT/DPI configs and system properties
Updated security configs for Android 7.x Nougat
Updated SELinux and addressed denials
kernel: Addressed eMMC 5.0 spec violation
kernel: Disabled MSM DMA test module
kernel: Updated filesystem drivers
kernel: Updated EXT4 driver
kernel: Updated ecryptFS driver
kernel: Updated sdcardFS driver
kernel: Updated MSM camera driver
kernel: Updated MSM GPU driver
kernel: Updated MSM IPA driver
kernel: Updated MSM SoC sound codecs
kernel: Updated MSM SoC sound driver
kernel: Updated network drivers
kernel: Updated QSEECOM driver
kernel: Updated Qualcomm SoC driver
kernel: Updates from the latest source code
25.11.2016:
Added custom telephony plugin
Added support for trltedt (SM-N910G)
Cleaned up CarrierConfig overlays
Cleaned up framework and boot class path
Customized telephony network values
Ported updates from Pixel XL images
Re-added custom bootanimation
Updated Android filesystem config
Updated ramdisk services groups
Updated SELinux policy and addressed denials
Updated SELinux rules for camera
Updated SELinux rules for CMHW/vibrator
21.11.2016:
Disabled Samsung MTP
Fixed unexpected app crashes
Updated CarrierConfig overlays
Updated telephony overlays
Updated vendor proprietary blobs
19.11.2016:
Fixed first/clean boot issues
Fixed media/Youtube audio issues
Fixed speaker and mic for voice calls
Optimized and cleaned up kernel ramdisk
Removed unused CM NFC feature
Reverted the custom bootanimation
Updated SELinux rules for the kernel
Updated filesystem mount options
Updated filesystem manager flags
Updated firmware GID and mount masks
18.11.2016:
Added support for all Snapdragon variants
Added fs_config support for custom binary
Added custom permissions for pm, camera, and IMS
Applied a fix for emergency calls
Enabled reschedule/delay service restarts
Restored audio configs from Touchwiz
Updated media codecs for Nougat
Updated media profiles for Nougat
Updated RIL java class for Nougat
Updated WiFi configs for Nougat
Updated SELinux and addressed denials
Updated SELinux rules for media hacks
Used set_prop to replace deprecated rules
Custom bootanimation by @Creeper36
14.11.2016:
Enabled audio features
Enabled Cell Broadcast settings
Enabled VoLTE bools
Hacked media for legacy blobs
Unified build for all variants
Updated SELinux policy
13.11.2016:
Addressed SELinux denials
Fixed some errors/exceptions
Updated proprietary blobs
12.11.2016:
Addressed SELinux denials
Fixed Widevine DRM
Restored audio effects
Updated media codecs
Updated bluetooth overlays
Updated telephony overlays
10.11.2016:
Preliminary support for other variants
Updated audio configs
Updated bluetooth configs
Updated SELinux policy
Updated kernel source code
November security patches
06.11.2016:
CyanogenMod 14.1 (Android 7.1 Nougat)
[/QUOTE]
ROM Status
Release Date:
No ETA, but you could vote for a newer build by hitting THANKS to the announcement post of the latest build.
END OF DEVELOPMENT
Click to expand...
Click to collapse
Supported Variants:
This ROM fully support US variants:
Verizon / VZW (SM-N910V)
T-Mobile / TMO (SM-N910T)
Sprint / SPR (SM-N910P)
US Cellular / USC (SM-N910R4)
and
Canadian variant (SM-N910W8)
International Snapdragon variants (SM-N910F and SM-N910G) need RIL/QMI fix. This can be done by flashing blobs from the latest firmware (cm-14.1-trltexx-fix_v3.zip) before flashing Gapps.
Nandroid Backup/Restore:
To fix nandroid restores (No SIM and Phone FCs) due to TelephonyProvider data/symlinks for using legacy RIL blobs on newer versions of Android 7.x+, you may wipe TelephonyProvider data by flashing this ZIP directly after restore and before rebooting to system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Required Firmware:
The latest Android 6.0.1 Marshmallow firmware is required for all variants. Check your device/variant forum for firmware upgrade!
VZW-ONLY:
ROM Firmware Required: N910VVRU2CPJ2
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Bug Reports:
All bug reports should be posted here. I'll ignore the posts that don't include appropriate logs. Unfortunately, I don't have the time to respond to the PMs.
Click to expand...
Click to collapse
Q&A:
There's a linked thread for Q&A, general discussions, and pre-/post-installation chat. Please keep this thread clean and post there all your personal issues that are not related to the development such as Xposed, themes, extra mods, other stuff, ... etc.
This thread is only for development, including bug reports with logs. All other topics should be moved to the new thread.
Thank you for collaboration! That's how users could contribute to the development.
Click to expand...
Click to collapse
It's finally here! I'm so excited! Lol as always @hsbadr, thank you so much for all your hard work and dedication for the community! I will be downloading sometime tonight and report back
@hsbadr Thank you for your continued support with our Note 4.
StayingSober said:
It's finally here! I'm so excited! Lol as always @hsbadr, thank you so much for all your hard work and dedication for the community! I will be downloading sometime tonight and report back
Click to expand...
Click to collapse
Extra Virgin said:
@hsbadr Thank you for your continued support with our Note 4.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The 1st build is now available for download:
http://forum.xda-developers.com/devdb/project/?id=17713#downloads
I have a Note 4 DE - Not Retail
running CyanogenMod Version 13.0-20150525 UNOFICCIAL -trltevzw
Baseband N910VVRU2BOK3
Can I simply flash this from recovery?
THank you for your time!
Definitely be downloading this as it becomes more of a Stable release!
---------- Post added at 04:35 PM ---------- Previous post was at 04:17 PM ----------
plainbum said:
I have a Note 4 DE - Not Retail
running CyanogenMod Version 13.0-20150525 UNOFICCIAL -trltevzw
Baseband N910VVRU2BOK3
Can I simply flash this from recovery?
THank you for your time!
Click to expand...
Click to collapse
I could be wrong, but it does say this:
ROM Firmware Required: N910VVRU2CPG2
Click to expand...
Click to collapse
JOSHSKORN said:
Definitely be downloading this as it becomes more of a Stable release!
---------- Post added at 04:35 PM ---------- Previous post was at 04:17 PM ----------
I could be wrong, but it does say this:
Click to expand...
Click to collapse
I've looked quite a bit and can't seem to find anything on a safe upgrade to CPG2. Do you happen to know where I could find any info on that? Thanks
plainbum said:
I have a Note 4 DE - Not Retail
running CyanogenMod Version 13.0-20150525 UNOFICCIAL -trltevzw
Baseband N910VVRU2BOK3
Can I simply flash this from recovery?
THank you for your time!
Click to expand...
Click to collapse
dhplap said:
I've looked quite a bit and can't seem to find anything on a safe upgrade to CPG2. Do you happen to know where I could find any info on that? Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ROM Firmware Required: N910VVRU2CPD1/N910VVRU2CPF3/N910VVRU2CPG2
hsbadr said:
ROM Firmware Required: N910VVRU2CPD1/N910VVRU2CPF3/N910VVRU2CPG2
Click to expand...
Click to collapse
Thanks hsbadr! And I also want to say thank you for your continued support on our phones. So after I flash this it would be ok to restore my other marshmallow roms and vise versa? Didn't know since this is Nougat. Really appreciate your time and help.
Oh my god! This is extremely exciting!
I'm going to wait to see how stable it is, since my Note is my daily driver, but I can't wait to flash this.
(Does it support Dual Boot?)
Zacharee1 said:
(Does it support Dual Boot?)
Click to expand...
Click to collapse
I think that'd require the dual partitioning
Bicknasty said:
I think that'd require the dual partitioning
Click to expand...
Click to collapse
Well there's Dual Boot Patcher. If it works with that, I could try it out of without breaking CM13.
@hsbadr, amazing job on the build sir! Everything seems to be running smoothly, first boot took about 10 minutes, and after that I breezed through the setup. Found that the old trick of quickly running your finger over the fingerprint sensor to set up prints worked beautifully. Going to try flashing Xposed here in a bit. I will report any and all FC's, or issues, while also running @chevyrhoads Note 7 port. Thank you!
Zacharee1 said:
Well there's Dual Boot Patcher. If it works with that, I could try it out of without breaking CM13.
Click to expand...
Click to collapse
Ohhh, I misunderstood. I thought you were asking about the Nougat seamless updates thing, and how some had been speculating that the dual-partitioning could be repurposed by developers for a dual-boot paradigm.
bertmag said:
@hsbadr, amazing job on the build sir! Everything seems to be running smoothly, first boot took about 10 minutes, and after that I breezed through the setup. Found that the old trick of quickly running your finger over the fingerprint sensor to set up prints worked beautifully. Going to try flashing Xposed here in a bit. I will report any and all FC's, or issues, while also running @chevyrhoads Note 7 port. Thank you!
Click to expand...
Click to collapse
I'm pretty sure Xposed doesn't work on Nougat http://www.xda-developers.com/rovo89-updates-on-current-status-of-xposed-for-android-nougat/
Get this error when trying to install, upgrading from cm 13
GeoHogan said:
Get this error when trying to install, upgrading from cm 13
Click to expand...
Click to collapse
I'm fairly certain you need to clean flash.
Thanks for making this HS.. Just curious if anyone is using this on TING? It installed fine for me.. but i have no cell connection, And when i goto APN settings it says no settings available for this user. Anyone run into this yet?
Actually it isn't seeing my Sim at all.