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?
Related
Hello, i decided to make a thread for a ton of CM mostly stock builds. Im going to be updateing these builds every so often. Except maybe 10.1 as development as far as the Cyanogenmod team goes has come to a very slow pace.(As its close to its final stages)
Credits for the ability to have these roms goes to Arco, ADC Team. Camcory. And all the other devs for our device and others. And of course the Cyanogenmod Team and the entire community.
All standards apply...if you phone blows up not my fault. If your cat eats your phone because the cyanogenmod boot animation looks tasty not my fault. Flash these like any other rom... my cwm from other thread will work fine.
Also response to this thread will be limited as its just a pile of roms. Not gonna try and go through dev talk about a billion roms all in the same place. feel free to talk about the roms all you want and ill try my best. If i miss anything feel free to PM me and ill try to address whatever the situation may be.
Also these are not ment to be replacements to anyone elses rom but instead just updated builds. And/or builds i use or have used personally. Kernel source 1 Kernel source 2 Kernel source 3
androidfilehost
CM10.1 : ION/PMEM
GAPPS:
Mirror 1
ROM 12-21-13:
Changes:
Sync CM sources
Mirror 1
CM10.2 : ION/PMEM!
GAPPS:
Mirror 1
ROM 8-3-13:
Changes:
Sync CM sources
Mirror 1*Broken Link editing note*
ROM 1-7-14:
Mirror 1*Broken Link editing note*
ROM 1-11-14:
Changes:
Sync CM sources
Mirror 1*Broken Link editing note*
ROM 1-29-14:
Changes:
Sync CM sources
Mirror 1
ROM 6-27-14:
Changes:
Sync CM sources
Mirror 1
Donation
TY to the following XDA members for contributing:
unmesh59
CM11.0 : ION/PMEM
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera/Video
Wifi and USB tethering
Known Issues
Fixed In newer builds: Lowest quality in camcorder, doesn't work. Therefore MMS Video Capture also. (Workaround available for older builds)
No other known issues.
GAPPS 1-5-14 (Recommended):
Mirror 1
GAPPS 6-6-14 Here for those with custom images or different rom(Too Big for This cm11 build):
Mirror 1
Older builds:
ROM 1-6-14:
Changes:
Initial release
Mirror 1
ROM 1-11-14:
Changes:
Fixed storage swapping - ty arco
Enable TARGET_USE_QCOM_BIONIC_OPTIMIZATION - ty arco
Possible workaround for the graphic glitch - ty arco
Updated media profiles - ty arco
Increased minimum CPU frequency to 368 MHz
Lowered zRAM size to half of what it was - ty arco
Kernel 3.4.76
Synced with CM
Mirror 1
ROM 1-15-14:
Changes:
Enabled Low Power Audio (LPA)
Fixed VOIP audio - ty arco
Fixed Netflix playback
USB OTG and zRAM fixes (credits Christopher83)
Kernel 3.4.77
Synced with CM
Mirror 1 *Broken Link editing note*
ROM 1-29-14:
Changes:
Disabled Low Power Audio (LPA)
Updated Adreno blobs - ty arco
Synced with CM
Mirror 1
ROM 2-7-14:
Changes:
Synced with CM
Mirror 1
ROM 2-14-14
Changes:
Synced with CM
Mirror 1
ROM 3-13-14 Leaving old build but breaking link for more testing.(harder to dl so you know what your getting)
Changes:
Synced with CM
Updated Adreno blobs - ty arco
Kernel 3.4.82
Mirror 1
ROM 3-19-14
Changes:
Synced with CM
Mirror 1
Kernel to Fix Audio *Broken Link editing note*
ROM 4-15-14
Changes:
Synced with CM
Mirror 1
ADC Linaro Kernel for this build
ROM 4-25-14
Changes:
Synced with CM
Mirror 1
ROM 5-8-14
Changes:
Synced with CM
Mirror 1
Mirror 2
ROM 5-25-14
Changes:
Fixed some audio routing bugs - ty arco
Enabled LPA (Low Power Audio) again
Lockscreen wallpaper
New theme engine
Synced with CM
Mirror 1
Mirror 2
ADC/Linaro Kernel[Mirror 1][Mirror 2] or Christopher K^Kernel[Mirror 1][Mirror 2]
More Kernel Options
ROM 6-8-14
Changes:
Sync with CM
Android 4.4.3
Enable KSM deferred timer - ty arco
Roll back UMS dirty ratio to 20 - ty arco
Add qcmediaplayer - ty arco
unblank screen during init - ty arco
Mirror 1
Mirror 2
ADC/Linaro Kernel[Mirror 1][Mirror 2] or Christopher K^Kernel[Mirror 1] [Mirror 2]
More Kernel Options
ROM 6-18-14
Changes:
Sync with CM
Adding setprop entries for tcp delayed ack for Wifi & LTE - ty arco
Add Back KK Adreno Drivers
Mirror 1
ADC/Linaro Kernel[Mirror 1] or Christopher K^Kernel[Mirror 1]
Round 2 Kernels
ADC/Linaro Kernel[Mirror 1] or
Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 7-7-14
Changes:
Sync with CM
Remove obsolete LPA prop - ty arco
Updates to PowerHAL - ty arco
Disable gapless mode - Fixes some audio issues - ty arco
Mirror 1
ADC/Linaro Kernel[Mirror 1] or Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 8-28-14
Sync with CM
Fixed Torch wake lock(arco)
Change some bluetooth permissions(arco)
Set default brightness to 80(arco)
Add OMX lib for hardware MP3 playback(arco)
Enabled "soft reboot" feature(sirmordred)
Enable proximity wake feature
Set ROW as default scheduler
Enable "Eject SD Card"(sirmordred)
Update vidc firmware and alsa lib (sirmordred)
Mirror 1
ADC/Linaro Kernel[Mirror 1] or
Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 9-9-14
Sync with CM
MMS Workaround(by me)
Mirror 1
ADC/Linaro Kernel[Mirror 1] or
Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 10-4-14
Sync with CM
Mirror 1
ROM 10-31-14
Sync with CM
Mirror 1
ADC/Linaro Kernel[Mirror 1] or
Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 12-09-14
Sync with CM
Mirror 1
ADC/Linaro Kernel[Mirror 1] or
Christopher K^Kernel[Mirror 1]
More Kernel Options
ROM 12-24-14
Sync with CM
OS2SD Instructions for flashing
OS2SD
OS2SD Mirror 1
CWM - OS2SD TWRP
ROM 12-25-14
Fix sensor issue.
OS2SD
OS2SD Mirror 1
ADC/Linaro Kernel or
Christopher K^Kernel
More Kernel Options
ROM 4-10-15(OS2SD):
Changes:
- KitKat 4.4.4 (KTU84Q)
- Synched with latest Cyanogenmod 11.0 sources
- BoardConfig: Avoid poisoning the host binaries with bad ABIs (rmcc)
- ramdisk: Change the class of rmt_storage service (arco)
- ramdisk: Change /dev/smd7 owner and group (arco)
- prop: Increase max background services to 8 (Christopher83)
- prop: Enabled HighEndGraphics by default (sirmordred)
- cm: Switch to full phone config (sirmordred)
- device: Disable HW MP3 decoder (sirmordred)
- BoardConfig: Reduced userdata partition size by 16 KB (sirmordred)
- rootdir: Blank/Unblank framebuffer to clear splash screen while on bootanimation (sirmordred)
- rootdir: Change permissions on external storage mount points (arco)
- rootdir: Remove sdcard1 from fuse_usbdisk service (arco)
- overlay: Set external storage devices as non-emulated (arco)
- camera: Modify base.common.version API define (arco)
- rootdir: Increase zram disk size to 256mb on 512mb devices (arco)
- rootdir: Increase Swappiness to 100 (arco)
- prop: Use /cache partition to store dex files of system apps (Christopher83)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 7-15-15(OS2SD):
Changes:
- KitKat 4.4.4 (KTU84Q)
- Synced with latest Cyanogenmod 11.0 sources
Mirror 1
Christopher K^Kernel
Stock no swap
More Kernel Options
ROM 11-4-15(OS2SD):
Changes:
- KitKat 4.4.4 (KTU84Q)
- Synced with latest Cyanogenmod 11.0 sources
Mirror 1
Christopher K^Kernel
Stock no swap
More Kernel Options
ROM 1-4-16(OS2SD):
Changes:
- KitKat 4.4.4 (KTU84Q)
- Synced with latest Cyanogenmod 11.0 sources
Mirror 1
Christopher K^Kernel
Stock no swap
More Kernel Options
CM12.0 : ION/PMEM
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
HW accelerated gui
HW accelerated video
Camera/Video
Wifi and USB tethering
Known Issues
Must enable dev options root and install SuperSU for root!
Camera app is buggy
USB mass storage Doesnt work
You tell me!
GAPPS 11-09-14: http://www.mediafire.com/?1vrqasod29md6fm
ROM 1-11-15(OS2SD):
Mirror 1
ROM 1-11-15v2(OS2SD):
Changes:
- overlay: Update device hardware keys integer(Me)
- overlay: Add deviceHardwareWakeKeys config (Me)
- device: Use healtd charger during off-mode charging (credits to Christopher83)
Mirror 1
ROM 1-14-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest CyanogenMod 12.0 sources
device/samsung/ancora_tmo
- bluetooth: Updated config (credits to sirmordred)
- gps: Some improvements to HAL (credits to sirmordred)
- ril: Ignore getCellInfoList and setCellInfoListRate calls (credits to arco68)
- overlay: Updated overlay for recent fw/base changes (credits to sirmordred)
- prop: Increase max background services to 8 (credits to Christopher83)
- prop: Update the property name for AwesomePlayer usage (credits to Christopher83)
- prop: Removed deprecated properties (credits to sirmordred)
- prop: Add back debug.egl.hw=1 (credits to arco68)
- Revert "ramdisk: Remove permissions change for /proc/cmdline on early-init" (credits to arco68)
- ramdisk: Some updates and cleanups (credits to Christopher83)
- ramdisk: Add config for USB charging (credits to arco68)
- ramdisk: Use NOOP I/O scheduler during boot (credits to Christopher83)
- sepolicy: Allow read/write on device-specific sysfs files (credits to Christopher83)
- sepolicy: Allow system apps, like AriesParts, to perform su shell commands (credits to Christopher83)
- sepolicy: Add missing policies for bluetooth (credits to Christopher83)
- sepolicy: Add missing policies for netd (credits to Christopher83)
- sepolicy: Fix additional denials (credits to Christopher83)
Mirror 1
ROM 2-1-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest CyanogenMod 12.0 sources
device/samsung/ancora_tmo
-GPS HAL: NTP Server(Me)
-gps: Makefiles cleanup and some changes to correctly build GPS HAL (credits to Christopher83)
-gps: Zero-out dev structure after checking for NULL (credits to Christopher83)
-prop: Removed deprecated properties
-ramdisk: Some updates and cleanups (credits to Christopher83)
-sepolicy: Updates from ariesve device (credits to Christopher83)
-BoardConfig: Enabled extended font support (credits to sirmordred)
-BoardConfig: Make dexpreopt flag compatible for multiplatform compiling (credits to Harakhti)
-BoardConfig: Disable some audio features (credits to arco68)
-BoardConfig: Enable some charger options (credits to mikeNG)
-prop: Enable high-end graphic effects by default (credits to Christopher83)
-device: Support for F2FS formatted /data partition (credits to Christopher83)
-ril: Fix multi-part SMS sending (credits to Christopher83)
-sepolicy: Allow system server to R/W from radio devices (credits to Christopher83)
Mirror 1
ROM 2-12-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
-Opensourced libsensors (By Myself, sirmordred, Christopher83, CastagnaIT, and maybe more from ADC TEAM)
Mirror 1
ROM 3-15-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
- prop: Add property to indicate we support usb-otg (sirmordred)
- camera: Modify base.common.version API define (arco)
- Revert "device: Move AAPT config to cm.mk" (arco fix for missing assets)
- uevent: Set perm of dev/ledflash as R/W (sirmordred)
- BoardConfig: Enable some healthd charger options (sirmordred)
- device: Updated liblight (sirmordred)
- device: Removed deprecated egl.cfg (sirmordred)
- prop: Disable offload audio (arco)
- rootdir: Increase zram disk size to 256mb on 512mb devices (arco)
- rootdir: Increase Swappiness to 100 (arco)
Mirror 1
ROM 4-10-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
- rootdir: Remove sdcard1 from fuse_usbdisk service (arco)
- BoardConfig: Reduced userdata partition size by 16 KB (sirmordred)
- device: Use local copy of wpa_supplicant_overlay_conf (sirmordred)
- device: Add support for display color calibration (KCAL) (arco)
- cmhw: Add keydisabler class (sirmordred)
- rootdir: Set permissions for keydisabler (arco)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 5-08-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
- rootdir: Various updates to init (sirmordred)
- Revert "rootdir: Increase Swappiness to 100" (arco)
- Revert "rootdir: Increase zram disk size to 256mb on 512mb devices" (arco)
- rootdir: Use lz4 compression for ZRAM (arco)
- rootdir: Reduce ZRAM size to 128MB (arco)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 5-20-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
- overlay: Define default quick setting tiles (arco)
- device: Use ART small mode (mikeNG)
- device: Disable dex2oat watchdog (mikeNG)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 7-21-15(OS2SD):
Changes:
- Lollipop 5.0.2 (LRX22G)
- Synched with latest Cyanogenmod 12.0 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
CM12.1 : ION/PMEM
What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
HW accelerated gui
HW accelerated video
Camera/Video
Wifi and USB tethering
Known Issues
Blank mobile network signal icon, even if calls and data network are working
You tell me!
GAPPS 6-02-15: https://github.com/cgapps/vendor_google/tree/builds/arm
ROM 4-13-15(OS2SD):
Changes:
- Lollipop 5.1 (LMY47I)
- Synched with latest CyanogenMod 12.1 sources
Mirror 1
ROM 5-31-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY48B)
- Synched with latest Cyanogenmod 12.1 sources
- overlay: Define default quick setting tiles (arco)
- device: Use ART small mode (mikeNG)
- device: Disable dex2oat watchdog (mikeNG)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 6-10-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY48B)
- Synched with latest Cyanogenmod 12.1 sources
- ancora_tmo: gps: More NTP servers(Doadin/Cars1189/Me)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 7-8-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY48G)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 8-19-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY48G)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 9-10-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LVY48F)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 9-30-15(OS2SD):
Changes:
- Lollipop 5.1.1 (LVY48F)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 1-4-16(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY48Y)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 2-7-16(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY49G)
- Synched with latest Cyanogenmod 12.1 sources
- Fix Display Due To Change in Previous Build (Me)
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 3-26-16(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY49H)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
ROM 8-15-16(OS2SD):
Changes:
- Lollipop 5.1.1 (LMY49J)
- Synched with latest Cyanogenmod 12.1 sources
Mirror 1
Christopher K^Kernel
More Kernel Options
Kernel Information:
All K^Kernels have overclocking the one labeled OC has just that no change to cpu voltage or memory. (Other misc tweaks still apply)
OC = Overclock
UV = Under Volt
EXUV = Extra Under Volt
Memory levels(aka settings>about phone>Memory):
high 380 MB of free RAM
very high 390 MB of free RAM
extra high 406 MB of free RAM
standard/default/small w.e. 370 MB of free RAM
New Builds:
high 406 MB of free RAM
very high 416 MB of free RAM
extra high gone
standard/default/small w.e. 396 MB of free RAM
Notes for OS2SD:
Before you start: I cannot stress enough cwm backups/restoring will not work with this OS2SD release! And data MUST be formated NOT Optional!
1. You MUST Backup All data or it WILL be lost!
2. You MUST Format /system, /data, /cache, and /sdcard0 in cwm/twrp.
At this point you can format sdcard0 as ext4.
3. Install the new CWM/TWRP the old one will not work from now on!
If you didnt before now would also be a good time to format the internal storage which in the new recovery is now /data to ext4.
4. Once formated first flash the OS2SD rom
5. Then flash GAPPS and/or other packages.
At this point you can restore data. Note the kernel is special so you cant use older ones so you can only restore things like /data backups and adb/titanium backups.
6. Then reboot and enjoy the extra space!
thanks cars1198 for this OP. 10.1 and 10.2 work like ya said. i like 10.1 better between the 2. really cant wait til i get cm11 working like others have.
testing cm11 again using cmw 6.0.4.4 right now.
13min Update. Still spinning animation on first boot. gonna wait 25mins before trying something else. if I get ill report back. if i don't either A) i passed out or B) still trying to get it
Will test what i can! thanks for always helping around man you were like the batmn to this forum. it was about time you shared it people you talent
det0xx said:
Will test what i can! thanks for always helping around man you were like the batmn to this forum. it was about time you shared it people you talent
Click to expand...
Click to collapse
Most of the credit goes to the others i mention in OP. I am mearly filling in the space in the dev scene on exhibit side of things. The other devs i mention have worked hard on other devices and ours and i just want to help the exhibit community benefit from their amazing work. And at the very least keep us updated with the latest CM source.
OP's updated with final words/links. If anyone has any questions or conserns or wants to share words of wisdom about anything or the format of any of my above posts feel free to PM me.
TripFX said:
thanks cars1198 for this OP. 10.1 and 10.2 work like ya said. i like 10.1 better between the 2. really cant wait til i get cm11 working like others have.
testing cm11 again using cmw 6.0.4.4 right now.
13min Update. Still spinning animation on first boot. gonna wait 25mins before trying something else. if I get ill report back. if i don't either A) i passed out or B) still trying to get it
Click to expand...
Click to collapse
I took out the battery after a while and got passed the boot animation, but them this message popped up "Unfortunately, the process android.process.acore has stopped" I rebooted again and the error messages stopped.
Jorge_007 said:
I took out the battery after a while and got passed the boot animation, but them this message popped up "Unfortunately, the process android.process.acore has stopped"
Click to expand...
Click to collapse
yup i can make it to that before numerous times. i want to make it past that. I want to be able to flash like i can with every other rom but cm11.
UPDATE:
got to your point. rebooted and let it go and it took fine. fully loaded in. no hangs or reboots. now to make sure gapps doesn't make it go crazy again.
TripFX said:
yup i can make it to that before numerous times. i want to make it past that. I want to be able to flash like i can with every other rom but cm11.
Click to expand...
Click to collapse
The first recovery i used that worked was jfbs 6.0.4.5. If you haven't tried that yet id recommend that.(Not that im guaranteeing it will work but just one i can confirm worked for me)
cars1189 said:
The first recovery i used that worked was jfbs 6.0.4.5. If you haven't tried that yet id recommend that.(Not that im guaranteeing it will work but just one i can confirm worked for me)
Click to expand...
Click to collapse
actually i swapped to your 6.0.4.6. took 2 reboots first made it to homescreen but kept giving me same errors most people like me have which is things such as phone and theme providers constantly stop responding. 2nd boot went in fine. I intentionally rebooted 10 time after that to see if it would give the homescreen errors again and it didn't. just flashed the gapps you posted now. first boot went to upgrading android and made all the way to finishing boot then it just rebooted it self right after and so far stuck on on animation again not frozen nor randomly rebooting again. will try what ya said next. no art enabled either.
TripFX said:
actually i swapped to your 6.0.4.6. took 2 reboots first made it to homescreen but kept giving me same errors most people like me have which is things such as phone and theme providers constantly stop responding. 2nd boot went in fine. I intentionally rebooted 10 time after that to see if it would give the homescreen errors again and it didn't. just flashed the gapps you posted now. first boot went to upgrading android and made all the way to finishing boot then it just rebooted it self right after and so far stuck on on animation again not frozen nor randomly rebooting again. will try what ya said next. no art enabled either.
Click to expand...
Click to collapse
You are doing full wipes in between each right? If you havent id try that with my cwm 6.0.4.6.(or the 6.0.4.5 i just posted)
cars1189 said:
You are doing full wipes in between each right? If you havent id try that with my cwm 6.0.4.6.(or the 6.0.4.5 i just posted)
Click to expand...
Click to collapse
do full wipe with gapps as well? also can i do bot adb and dsmaq at the same time?
no go with adb on first boot. just says waiting for device. wiped system cache data 3 times each in that order. first boot will go in to home with phone and themes provider stop responding. gonna try 6.0.4.5 instead of 6.0.4.6.
TripFX said:
do full wipe with gapps as well? also can i do bot adb and dsmaq at the same time?
no go with adb on first boot. just says waiting for device. wiped system cache data 3 times each in that order. first boot will go in to home with phone and themes provider stop responding. gonna try 6.0.4.5 instead of 6.0.4.6.
Click to expand...
Click to collapse
Untill you get a stable rom i wouldnt try any gapps yet.
cars1189 said:
Untill you get a stable rom i wouldnt try any gapps yet.
Click to expand...
Click to collapse
well after the million reboots after i was able to get in once completely with no errors is when i tried the gapps. and after doing gapps it went back to throwing a fit. wiped everything 6 times. installed 6.0.4.5 rebooted. wiped everything again 6 more times. now trying first boot with 6.0.4.5
edit: adb logcat and adb shell will not take on first boot. also i can get a cwm logcat for ya. just waiting on this first boot to see what happens before pulling log from cwm
edit2: failed again. here is cwm recovery log. cant pm you cause it says you have it disabled or can't receive any.
edit3: i can install your 10.1 perfectly everything time using 6.0.4.4 - 6.0.4.5 that i've tested so far. going to try every version of cm11 in order to see which build it starts at having issues at. still on 6.0.4.5
edit4.: intial release build -12/23 tested all perfectly aside noted bugs per each release.
hey bro downloaded your 10.1 a few hours ago, its like I have a new phone..:good: muy excellente!! i'm tempted to try out your 10.2 but I need a stable phone for a few days.., unless you or someone can vouch for it and say its stable. either way.. i'll ask about your cm11 rom but am very fearful to try it out..
Nitro Lopez said:
hey bro downloaded your 10.1 a few hours ago, its like I have a new phone..:good: muy excellente!! i'm tempted to try out your 10.2 but I need a stable phone for a few days.., unless you or someone can vouch for it and say its stable. either way.. i'll ask about your cm11 rom but am very fearful to try it out..
Click to expand...
Click to collapse
10.1 is rock solid so far. wife is loving more than aoip so far.
im try to see which cm11 build the problem some NOT ALL of us are having. make nandroid of cm10.1. try lastest cm11 build and if you have any issues revert back to nandroid until we get it sorted out.
TripFX said:
10.1 is rock solid so far. wife is loving more than aoip so far.
im try to see which cm11 build the problem some NOT ALL of us are having. make nandroid of cm10.1. try lastest cm11 build and if you have any issues revert back to nandroid until we get it sorted out.
Click to expand...
Click to collapse
I know right, having a Working ROM is awesome!..., no offense to jfbs, I love his ROM it just ain't working right on my phone. but I guess it works fine on others phone?? oh well, let the ROM wars begin!:highfive:
Nitro Lopez said:
I know right, having a Working ROM is awesome!..., no offense to jfbs, I love his ROM it just ain't working right on my phone. but I guess it works fine on others phone?? oh well, let the ROM wars begin!:highfive:
Click to expand...
Click to collapse
actually so far with jfbs version from intial release up to 12/23 build doesn't have the issue that i know of so far. pin pointing which build it breaks at.
Nitro Lopez said:
hey bro downloaded your 10.1 a few hours ago, its like I have a new phone..:good: muy excellente!! i'm tempted to try out your 10.2 but I need a stable phone for a few days.., unless you or someone can vouch for it and say its stable. either way.. i'll ask about your cm11 rom but am very fearful to try it out..
Click to expand...
Click to collapse
The 10.2 is old and still using full pmem it does work but i would not recommend it over the 10.1 ion/pmem or 11.0 ion/pmem. Hopefully ill be updateing it soon with an ion/pmem build so we will have all 3 up-to-date or very recent(lessthan 1 month old).
Introduction
This ROM is inspired by JustArchi's build optimizations that provide up to 6x performance boost .
I am not a developer by any means, I did my homework and I figured out how to compile and cherry-pick cool things. I am open to advice and guides that can help me make this ROM even better, you can also always ask for features and I'll do my best to bring them in.
As this is my rom for daily use, it contains many, many tweaks and endless hours of work of the best devs of XDA. In these features you can find Faux's Intelliplug, Yank555 powersuspend driver and many other stuff. At this point if you use any other kernel with my ROM you will lose about 80% of the features and the experience I want to provide will be lost. If you like other custom kernels such as Pink please kindly use official Nightlys.
If you are still here and haven't ran away you must know that you can always ask me for new features you see in other fine roms (Such as Temasek, CrDroid, etc) and if everybody like that feature (Including me) I will gladly bring it into the ROM. Don't forget that if you want a full featured ROM there's plenty of fine choices. The main idea with this is the same as with my old CM11 builds; "To stay as close to Stable CM as possible while adding on a little somethin' somethin' to make things better."
DISCLAIMER: I am not responsible for any damages to your device, always have a nandroid on hand if anything happens
Main Features
Based on CyanogenMod 13 latest updates
ROM compiled with UberTC 5.2
Build optimized with Graphite and O3 flags
Build optimized Cortex A7 architecture
Custom cosmetical changes
Screen Record
Custom msm8226-common device branch (Different PowerHAL)
Custom Kernel with several features out of the box such as:
-Upstream GPU patches
-GPU Overclock
-HTC dynamic fsync
-USB fast charging
-Some Interactive picks
-Power efficient workqueues
-Simple GPU Algorithm
And much more, for a deep insight you can visit my github
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation Instructions:
Upgrading from a previous build:
1.- Flash the ROM
2.- Flash any add-ons you want
3.- Wipe dalvik and cache
4.- Reboot into ROM
Upgrading from any other ROM even CM11:
1.- Full wipe
2.- Flash the ROM
3.- Flash GApps
4.- Flash any add-ons you want
5.- Wipe dalvik and cache
6.- Reboot into ROM
Downloads:
ROM
Build 4
Build 3
Build 2.1
Build 2
Build 1
Kernel
[MM]Beto's_Kernel_V6.0.zip
5.1.1 releases,
Beto's_Kernel_V5.0.zip
Beto's_Kernel_V4.1.zip
My preferred GApps:
Open Gapps
--Recommended Settings--
Nope.
Source and credits:
*CyanogenMod for the awesome ROM and great support for our device
*Somcom3X our beautiful CM maintainer.
*JustArchi for the countless hours of testing build flags and Toolchains.
*Chainfire for the great Superuser.
*bedalus (picked lot of things from your kernel)
*GalacticStrider for his amazing build work on SaberSunset.
*CL3Kener
*Faux
*Synergy510 For his amazing work with Saberize optimizations which made possible this ROM. (I also took his thread as base to make this one )
This ROM wouldn't be possible without them, so please donate and show your support to them.
ROM OS Version: 6.0.1 Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 13
Source: My kernel sauce
Version Information
Status: Stable
Created 01/30/2015
Changelog
Build 4
-Updated to latest cm-13.0
-Changed some out of the box kernel settings
Click to expand...
Click to collapse
Build 3
Synced with latest cm-13.0 sources
MSM8226-Common
- Revert "msm8226-common: Add falcon and peregrine sensors HAL" …
- Revert "msm8226-common: Enable proximity check on wake" …
- Revert "msm8226-common: Enable Ambient Display" …
- msm8226-common: Kill Doze and sensor usage …
vendor/motorola
- Revert "falcon peregrine: Remove proprietary sensors HAL" …
cm/vendor
- Added Kcal control by savoca
- Added latest AdAway
- Added Nova Launcher
Click to expand...
Click to collapse
Build 2.1
Fixed derps with BT and optimzation flags
Click to expand...
Click to collapse
Build 2
ROM:
-Updated to latest cm-13.0 release
Kernel:
-Added Kcal support
-Added Faux Sound Control
Click to expand...
Click to collapse
Build 1
MSM8226-COMMON
-Default scheduler is ROW
[+] Which is vastly superior than default on real life usage
-Killed custom cm PowerHAL in favour of Qualcomm implementation.
[+] This improves battery consumption both on iddle and screen on.
-Disabled hispeed_freq when screen is off
[+] Intended to improve energy usage on iddle
-Replaced some libs to match qcom vendor
[+] This one fix some very annoying logs on the PowerHAL as it looked for libs that didn't exist. Such as “QCOM*PowerHAL:*Failed to acquire lock”
-Added MSM8226 board optimizations
[+] Given more data to the compiler such as number of cores and cache L1/L2 to allow it to optimize the code even further
Frameworks/Base:
-Ability to hide root icon
-Switchable kill-app timer
Build
-Compiled with Arter97 optimization flags
-Build compiled with UberTC 5.3 optimized
Vendor/cm
-Some cosmetical changes
Kernel: (Featuring my old kernel which is a stock kernel with a couple of extra features)
-Upstream GPU patches
-GPU Overclock
-Intelli-Plug and Mako hotplug
-HTC dynamic fsync
-USB fast charging
-Some Interactive picks
-Power efficient workqueues
-Simple GPU Algorithm
-Intelliactive governor
-More TCP congestion
-CPU-Boost on which is needed by qcom PowerHAL
-“A lot” of misc stuff which you can check on my github
Click to expand...
Click to collapse
Final
-Updated to latest cm-12.1 sources
-Reverted some custom PowerHal upstream commits since we are using qcom implementation
-Deleted profile settings that used to turn on MP-Decision on several tasks (We may now use Intelli-Plug without it messing around)
Click to expand...
Click to collapse
Build 26
-Updated to latest CM-12.1 sources
-Added wakelock blocker.
-Default scheduler is ROW again.
-Reverted custom PowerHal implementation
-Reverted readahead back to normal values
Click to expand...
Click to collapse
Build 25
ROM:
Updated to latest cm-12.1 sources.
Removed Nova Launcher
Custom PowerHAL implementation
[+] This one changes the battery profiles, specially for power saving, making the phone actually usable on saving mode (More info here)
Added MSM8226 board optimizations
[+] Given more data to the compiler such as number of cores and cache L1/L2 to allow it to optimize the code even further for our phone.
Bionic changes
[+] Added optimized memcpy implementation for Cortex A7
ART Optimizations
Patch to allow Viper4Android on enforcing mode
Misc UI changes
Kernel:
Pushed readahead to 512Kb
Intelli-Plug updates
Default scheduler is now BFQ
SELinux is now enforced.
soc: qcom: bam_dmux: Add fast-shutdown flag
[+] This one should greatly reduce bam_dmux_wakelock on our 4G device
Click to expand...
Click to collapse
Build 24
-Updated to latest CM-12.1 sources
-Reverted some unnecesary framework/base commits
-Restored MotoDoze
-ROM compiled now with Uber 4.9, which is fairly similar to SaberMod. Just for testing purposes.
-Cleaned my build environment squashing commits
Click to expand...
Click to collapse
Build 23
-Updated to latest CM-12.1 sources
-ROM is now compiled with GCC 4.9, the toolchain that'll be shiped on M.
-Fixed wrong auto-vectorization of ID3 iterator causing various media crashes with badly-tagged MP3s
-Kernel compiled with Linaro 4.9.4
-Added built in SuperSu menu (Require SuperSu)
-Updated to ArchiDroid Optimizations 4.1.
Click to expand...
Click to collapse
Build 22
-Updated to latest CM-12.1 sources
-Refactored kernel after *some guy* decided to fix Interactive governor when there it was nothing wrong with it.
-Updated kernel toolchain to Linaro 4.9.4
-Updated SaberMod 4.8 to latest release
Click to expand...
Click to collapse
Build 19
Updated to latest CM12 sources
Fixed hide supersu icon option
Disabled Faux123 Simple_Ondemand
Enabled Arter97 AdrenoIdler 1.1
Misc kernel cherry-picks I had before my phone died
Click to expand...
Click to collapse
Build 18
-Updated to latest CM12 sources
-Lot of things have been fixed, specially fixed parameters for lowminfree memory and possibly bluetooth hiccups
-Updated SaberMod toolchain.
Click to expand...
Click to collapse
Build 16
Updated to latest CM12 sources
Kernel and ROM are now separated, if you want my kernel it must be downloaded and flashed after the ROM.
Merged pull request of @Frazew
Fixed screen record which I had broke on Build 15
Build lited with Opti-Charger
Misc updates to Kernel
Click to expand...
Click to collapse
Build 15.1
-Finished bringing features of old kernel to the new one
-Implemented misc build.prop tweaks (Commit)
-Introduced Opti-Charger (To improve RAM use, more info in the spoiler)
Custom ROMs in the beginning had limited space to work with which is why Cyanogen introduced opticharging to the custom release tool in order to shrink apks to fit more apps on system partitions of the original android devices. The opticharger script pulls apart apks near the end of the build and optimizes all pngs drawables found in them. Originally this script used optipng which is great and there is absolutely no quality loss involved in the png compressions but more recently I’ve begun using pngquant because it compresses pngs even smaller 30-70% with usually an average of about 50%. Pngquant does result in a slight loss of quality but nobody has noticed yet (See more on pngquant here: http://pngquant.org/) (If you are worried about quality you can always use optipng which compresses without any quality loss themers usually use this option instead)
Currently, CyanogenMod has abandoned the use of the opticharger but many ROMs still use it such as SLIM, AOKP, LiquidSmooth, Dirty Unicorns, Carbon, Validus, and many others. Themers and app developers alike use these techniques as well to make their apps/themes run more smoothly. Making pngs 70% smaller actually makes the loading time 3 times faster for these pngs and also saves you RAM. I understand apks aren't all pngs but you'd be surprised how many junk pngs google has left behind since froyo that serve no purpose but are loaded into your ram with SystemUI anyways. Thankfully opticharging shrinks all of those undesirables by usually 50-70% and saves you several MB worth of space and speeds up your SystemUI. Since you can't unload the system UI this is well worth the effort! My motto always is every little bit counts
Many still argue that high end device don’t need opticharging anymore because they are fast enough to handle these full-sized pngs. While this is true it still doesn’t change the fact that opticharing IS still slightly faster and opticharged apks do use less ram
.
Click to expand...
Click to collapse
Build 15
-Updated latest CM-12.1 sources
-Switched kernel to latest CM sources, meaning you can use Optimus and Spirit kernel now. Make sure to update your bootloader if you don't want "screen-tearing" lines.
-Merged Arter97's fix to Play Store FC's
Click to expand...
Click to collapse
Build 14.1
First attempt to fix suddenly battery drops
Added more TCP congestion options
Click to expand...
Click to collapse
Build 14
Synced latest CM-12.1 sources
Featuring latest 5.1.1 R1 release.
Fixed crazy radio wakeups on deep sleep
Removed p-thread to get more battery life (MOAR!)
Added quick lockscreen gestures (To turn screen on when notification led is blinking and pocket mode)
Switched to latest JusArchi 5.1 gcc optimized for Cortex A7.
Added screen-recorder, which can be enabled on "Buttons" -> "Poweroff Menu"
Probably more stuff I don't remember right now
Click to expand...
Click to collapse
Build 11
Updated to latest CM-12.1 sources 8/05
We are back to my "stock" kernel which doesn't have DT2W
Released 2 variants of my kernel, one with DT2W and the other without it.
Click to expand...
Click to collapse
Build 10.1
Enabled DT2W implementation
Enabled power efficient workqueues
Activated fast charge via USB
Some misc picks to enhance kernel
Click to expand...
Click to collapse
Build 8.1
Fixed kernel Toolchain (Crucial for a perfect synergy with optimizations)
Click to expand...
Click to collapse
Build 8
Featuring Android 5.1.1
Synced latest CM12.1 sources 21/04/15
Updated kernel Toolchain to SaberMod 5.0
Complete rebase to kernel.
Updated graphite flags.
Beast benchmark scores (over 20k)
All old optimizations that are posted on OP are up and running too.
Click to expand...
Click to collapse
Build 6
Updated with latest CM12 sources
Intelli-Plug 4.0 with eco-mode is back.
Added some special changes to hotplug
Added option to hide the annoying icon of root at status bar. (@Pupet_Master bet you are going to love this one)
Switched to Linaro Toolchain 4.9.2 optimized for A7 Cortex architecture. (Rom is still compiled with SaberMod)
Misc tweaks to kernel.
Click to expand...
Click to collapse
Build 5
Reworked Project, added all optimization flags.
Click to expand...
Click to collapse
Build 4
*Synced latest CM12 sources
*No screen-tearing issues
*Re-Enabled MP-Decision
*Added new implementation of Intelliplug directly from Faux's Github
*Removed IntelliMinMax governor (For now)
*Updated powersuspend driver to v1.5
*Updated SaberMod Toolchains
*Ditched my old build environment and bringed up @JustArchi optimizations which takes Android to a whole new level
Important changes:
- Optimized for speed yet more all instructions - ARM and THUMB (-O3)
- Optimized for speed also parts which are compiled with Clang (-O3)
- Turned off all debugging code (lack of -g)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Sorted the common symbols by alignment in descending order. This is to prevent gaps between symbols due to alignment constraints (-Wl,--sort-common)
Click to expand...
Click to collapse
Build 3
Updated CM12 commits.
Initial Modular O3 Implementation … (Yay!)
armv7-a-neon: Apply Correct mfpu and mfloat tunings per arch …
Updated Graphite flags
Speed up Recents Menu, StatusBar and Windows Orientation.
Added a setting to disable expanded notifications.
Disabled MP-Decision (Conflicting with Intelli-Plug when performance per app is ON)
Enabled Intelli-Plug by default.
Misc cherry-picks to polish new optimizations
Click to expand...
Click to collapse
Build 2
Added Graphite optimizations
Added Strict-Aliasing optimizations
Updated latest CM12 sources.
Click to expand...
Click to collapse
FAQ
Thanks a lot @Travisholt92 for writing this guide, please give him a big thanks here!
Question 1: I am coming from (Stock or CM11), how can i install this?
Answer 1:
1. Back up all of your files, text messages, and everything else that you dont want to lose (try Easy Backup in the Google Play Store). You will lose everything stored on your phones internal storage and applications , your SD card will be safe.
2. Download the latest build posted in OP and Download GAPPS and move the .zip files onto your SD card (Remember where you put these files).
3. Shut down your phone.
4. Reboot into recovery mode by holding down the volume down button and the power button, then releasing the power button. This will come up with the Fastboot interface. Press volume down to highlight Recovery and then press volume up to boot into recovery mode.
(through TWRP)
5. Press Wipe
6. Press Advanced Wipe
7. Select Dalvik Cache, Data, Internal Storage, Cache, and System.
(Do not select microSD card or USB OTG)
8. Swipe to wipe.
9. Press Install. At the top of the screen make sure it says "Storage: microSD card". Navigate to the ROM .zip file and press it.
10. Press Add More Zips and select the GAPPS .zip file.
11. Swipe to confirm flash, reboot system, enjoy SaberMod!
(If none of these answers fix your issue read the comments for others having similar issues to see if anybody has found a fix for the issue. If the issue hasn't been meantioned previously please report the issue, leave a comment. Make sure to state what build you are running and what kernel you are using if you installed a custom kernel. If its something that happens when you perform a certain action such as after sending a text your phone reboots, try and be as detailed as possible when reporting the bug)
Question 2: I just installed (insert build name here and issue below). How do i fix this?
A. and my device is stuck at boot animation, device boots but spams with system application errors (meaning installed by your ROM not from GAPPS) , or anything else that prevents you from using your phone.
Answer: Backup your device and follow the directions for answer 1. (install the last ROM you were running if you are coming from an AOSP build if needed to back up your data)
B. and my device boots but spams with my downloaded application errors.
Answer: Uninstall the application and redownload it from the Google Play Store.
Gonna test
Que buena ver un chileno por estos lares, y más aun desarrollando roms, bastante bueno; voy a probar la ROM y ver como anda
English; Gonna test the rom and will say how it works
Any severe bugs up to know?
primewell said:
Any severe bugs up to know?
Click to expand...
Click to collapse
Only CM11 bugs, wich at this stage of develeopment are almost zero. That's the idea of applying only minimal stuff, the result is a enhanced CM11 experience with the same stability.
Next build will inlude GPU and RAM OC.
.
I also prefer CM 11 for now. Better stability and performance. And your ROM is great! No bugs so far. Thanks!
BUG
I Got Alll cores running on 1190hz all time and i can't change the frequencies
SplaszIG said:
I Got Alll cores running on 1190hz all time and i can't change the frequencies
Click to expand...
Click to collapse
It is not a bug, MPdecision shows all cores at full freq, but if you check them at real time (I.E using CoolTool) you'll see they work normally.
Anyway, I DK if add more features on the next build (Halo maybe?) or keep things simple with Linaro and Archi's optimizations. What do you guys think?
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
WiCiO_MeDi said:
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
Click to expand...
Click to collapse
+1
WiCiO_MeDi said:
keep it simple, there are other ROMs for those who want more.
or you can make it modular and give additional functions in flashable zips
Click to expand...
Click to collapse
Will do.
Thanks for your input!
I Think that modular add ons wolud be great , btw i would like more perfomance improvements too:good:
Wonderful job, hermano trasandino'. One thing I'm missing is the Tap2Wake feature. How can I add it to this ROM ?
Thanks
I'm guessing there's still this mystical memory leak problem as in CM11?
Sent from my XT1039 using XDA Free mobile app
New build is up. Currently I'm adding general tweaks before fetching more advanced stuff. (I'm having a lot of fun on Blechdose's AeroKernel and Faux github )
Changelog:
Updated with latest CM sources
Added GPU OC 550mhz
Added Min CPU Freq 192mhz
GPU optimizations
Added instructions for Cortex A7 architecture
ARM: use -mcpu=cortex-a7 when targeting MSM8226 CPU
Added frequency to corner mappings for msm8226v2
Reverted RAM OC due overheating
Interactive governor misc tweaks.
Click to expand...
Click to collapse
Link: Build 2
Can I flash this doing a clean install from CM12? There will be no problem right?
rodsayd said:
Can I flash this doing a clean install from CM12? There will be no problem right?
Click to expand...
Click to collapse
Yes. That's the way I've done it. Just simply erase everything EXCEPT sdcard and usbotg. Then, as usual, flash this ROM and then Gapps
I've been using it since yesterday and the perfomance is amazing! I will keep this as a daily driver, just one problem: sometimes the camera doesn't take the photo, it freezes just after I push the botton (I had the same problem on CM12).
rodsayd said:
I've been using it since yesterday and the perfomance is amazing! I will keep this as a daily driver, just one problem: sometimes the camera doesn't take the photo, it freezes just after I push the botton (I had the same problem on CM12).
Click to expand...
Click to collapse
Glad to see there's actually someone using and enjoying it. I'm having pretty good battery life and performance too, I guess Linaro and JustArchi's optimizations are just magical.
Regarding the camera, I don't use stock CM11 app but "A Better Camera" from the PlayStore. GIve it a shot and tell me if the issue persists.
Regards!
Great, I will try it. By the way, there isn't block screen notifications on the rom? That would be a nice feature if you can add it and keep up the good work, I'm staying with this.
Here comes the Marshmallow!
I don't want to waste too much time to maintain a few threads. From now on, I'll put all Marshmallow developments in this thread.
Since Tab Plus is almost identical, it'll also be included here. All builds are unofficials. Please click the ROM images for details and read post#2 for extra infos.
Release Note:
2016/8/13
This is the Android-6.0.1_r62 version of OmniROM-6. This might probably be the last Omni-6.
2016/8/4
This is the Android-6.0.1_r62 version of DU-10.4.
2016/7/29
This is the Android-6.0.1_r52 version of CM-13.0. As N is coming, it might probably be the last CM-13.0.
There were few reports on Gapps issues but again with no detail. I already mentioned many times that I can't access Google services locally. I tried once more on this new build via VPN and again I have no problem with that.
1. I flashed the latest CM (20160729) + opengapps pico 20160722 + SuperSU 2.52 with the latest TWRP 3.0.2-0.
2. After a factory reset and reboot, I completed the setup.
3. I connected to a VPN and add a Google account.
Everything went smooth as expected.
The following are the screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had also done a battery life test:
1. no sim card
2. WiFi off after sleep
3. Added a Google account.
My 3 years old battery can standby over 2 weeks. Everytime I turn on the screen, WiFi connected normally.
Here is the screenshot
*** These are the minimal essential info. required for a report, nothing less.
*** If you don't want to provide those, just don't post. You'll be ignored...
2016/7/7
DU-10.3 (Android 6.0.1_r46) is out. Cheers!
2016/6/21
This is the Android-6.0.1_r46 version of OmniROM 6. Cheers!
2016/6/9
This is the Android-6.0.1_r46 version of CM-13.0. Cheers!
2016/5/25
DU-10.2 (Android 6.0.1_r43) is out. Cheers!
2016/5/11
Omni merged Android 6.0.1_r43. This is mainly an version update. Cheers!
2016/5/3
This is the Android-6.0.1_r30 version of CM-13.0. The adaptive brightness and live display are fixed. The Bluetooh app is also patched to work with Bluez now. Cheers!
2016/5/1
Android-6.0.1_r30 required a patch to work with Bluez. You may find the patch here.
This patch would work for the latest Omni (20160414) and DU (20160425).
HISTORY:
2016/4/25
DU has released the v10.1 which is Android 6.0.1_r30. A few bug fixes are included.
2016/4/14
Omni merged Android 6.0.1_r30. This is mainly an version update. Cheers!
2016/4/5
In this CM build, the flickering fix is included. CM also use the opensource UMB library now. Minus one in the blobs count and better chance for newer versions of Android. Cheers!
2016/4/3
DU use the AOSP linker. When updated to 6.0.1_r22, the PIE support is gone. I have rebuilt the linker. Flash this
View attachment du-gps-patch.zip will get the gps back. For i815, GPS is ok but the RIL library requires the same PIE support. You need to flash it too.
2016/3/31
The current Gapps have permission issues again. Flash this View attachment gapps-perm-patch.zip after the ROM and Gapps would fix the permissions of Gapps at reboot.
Theory: I didn't want to change the original security of AOSP so I put an init.d script to fix the permission at start. It would be the same as the assignment of permission in App settings. The default security and permissions hierarchy is preserved. I think this is the better way.
However, the current growth of ROM and Gapps delay the Package Manager service (which is for permission granting). A wait loop is now added to the script. It would wait for the Package Manage service now. I think it would work for the future Gapps too.
2016/3/29
As I suspected, there are a few coincidences cause the flickering. DU and CM are quite different and yet both have the flickering issue... :cyclops: After I fixed the calculation of ambient and debouncing, the other cause embossed. I was aiming at the openGL, gui, ui, sensor, brightness and algorithm for weeks. Seems all dead ends after the fix. I decided to put it aside and started testing the Carbon-M. Carbon-M is quite "primitive" and close to AOSP. There is no flickering as expected.
When you have eliminated the impossible, whatever remains, however improbable must be the truth... I then start again with the whole frameworks. I compared the four sources and eliminate the libraries one by one. Finally, I think I found a solution! Only time can tell if it is the ultimate cure. :fingers-crossed:
Hoping this DU is more or less the complete released. Cheers!
2016/3/23
Omni also merged the 6.0.1_r22 source and It's been over a month since the last update. There are a few bug fixes in PerformanceControl. I also updated the modem driver for i815 in the kernel. Hoping the mobile data would work now. :fingers-crossed:
2016/3/15
CM has merged the latest 6.0.1_r22. It's time to have an update. The same fixes applied and the flickering is almost gone now. At this moment, it is more or less fully functioning now. Cheers!
2016/3/7
DU had updated the included SuperSU zip to 2.65 which is not working for our kernel. You would see an error message at the end of flashing. For the time being, you can manually flash the Beta-SuperSU-2.52 after the rom to get root. I already updated the build script. Subsequent builds will replace the included SuperSU.
2016/3/5
The Display settings crashed in the last DU 20160303. This View attachment du-patch-20160305.zip would fix that.
2016/3/3
Finally, I narrow down to a few services that cause the flickering of screen. I believe there are a few overlapping incidences causing it. The random combinations of ambient and debouncing calculation are almost impossible to trace. I can't say the flickering is completely gone now but it is limited to only a few at start. Similar fixes will be apply to CM later. I seldom quit the thing I started and the update of DU is always on my mind. This is the second and hoping the fully working DU. Cheers! :victory:
2016/2/22
Although r16 is out, it was for Pixel-C and based on r5. May be that's why CM and Omni didn't merge it.
I was thinking to release a new DU but I still have no idea about the flickering yet. I'm also busy on my Nexus7 developments. Omni has included some consolidations and I have fixed a few things. I think it's about time to have an Omni update. I didn't test it in deep. Hoping everything is still in the right place...
2016/2/10
I spent most of the time studying why there is flickering in CM-13.0 and others but not Omni6. It was really random to track a path. I haven't find anything concrete yet. I have put a few stability measures though. Anyway, it's a new version release. Some part of the performance control apk were rewritten.
2016/2/4
Turn out there are limits for a single post. So grouping all ROMs to one thread was another wrong move... Have to make adaptions later.
After a few long day and night of boring and sweaty works, I can finally sit down in front of my Ubuntu PC to enjoy a coffee. It is harder and harder to earn a few more bucks now...
Omni and CM just merged to the latest Android 6.0.1_r13 now so It's time for a new Omni. I had included the "Double tap to wake" feature in the kernel last week. I have tried on my Nexus 7 and p6800 for sometimes. After a few adjustments, I think it's time to release it for everyone to test. A new settings is added to the Advanced page of Performance Settings. Check post#2 for details. Tab Plus use a different touch screen. I just did what I thought appropriate, please report.
I hope there is nothing missing in this build but who can tell? :cyclops:
2016/2/2
There was a report that 20160122 cm-13.0 for Tab-plus not boot. I used a build script to build all the models. I think the ccache in my new system might catch some objects from 7.7. The graphic objects have different screen size which stop tab plus' graphic driver with a black screen. I have rebuilt the CM kernels for Tab plus. They will be available in the host and mirror shortly.
2016/2/1
Apn-config.xml is missing in the last DU-10.0. Apn set up would crash. I packed a patch which is in post#239.
2016/1/27
Since there are not much progress in CM and Omni, I tried another ROM the Dirty Unicrons. DU is also an old player for years. I use DU in my Nexus 4 for sometimes. It is stable and amazing. DU is even closer to AOSP than Omni. Even if it included SuperSU, it has smaller foot print. The Dirty Tweaks apk offers a lot of customizations. Before my hard drive failure, I can't fix a bug so I delayed it. Fresh start sometimes would give us surprises. I finally fixed the bug in DU. Sadly, it also got the occasional flickering. Really don't know why Seems only Omni is immune from it. I used the same HAL libraries from Omni and most of the Graphic codes are the same! That must be something buried really deep... Any idea is welcome.
Anyway, DU has its good character which is worth trying. Enjoy!
2016/1/22
In this build, the barcode and Google translate format is fixed. Those apps won't crash now. I added extra settings to L2CAP in Bluez. Files can be sent via Bluetooth now but still can't received files. The occasional flickering appear in other Samsung devices too. I patched a few things for that. Seems it's gone now but only time can tell. 3minit battery mod is included as Omni. (See Q&A in post#2).
This is the first CM after my hard drive failure. Hoping everything is in the right place now... :fingers-crossed:
2016/1/18
2016/1/17
2016/1/16
2016/1/15
2016/1/7
2016/1/6
2015/12/30
2015/12/29
2015/12/22
2015/12/16
2015/12/14
2015/12/10
2015/12/8
2015/12/6
Flash this View attachment 3567048 if you have SIM detection problem.
2015/12/5
2015/11/28
2015/11/26
2015/11/24
2015/11/16
2015/11/14
2015/11/4
2015/10/27
Screenshots: :laugh:
View attachment 3531073
Change log: :victory:
Code:
[COLOR="Blue"]2016/8/13[/COLOR]
- Latest 6.0.1_r62 (MTC20F) source from Omni
- Add PowerHAL for exynos4
- Add MM native support for double tap wake in Display settings
- Bluez 5.41 update
[COLOR="Blue"]2016/6/21[/COLOR]
- Latest 6.0.1_r46 (MOB30M) source from Omni
- Bluez update
[COLOR="Blue"]2016/5/11[/COLOR]
- Latest 6.0.1_r43 (MOB30J) source from Omni
- Bluez 5.39 from bluez.org
[COLOR="Blue"]2016/4/14[/COLOR]
- Latest 6.0.1_r30 (MOB30D) source from Omni
- Default RW permission for exteranl sdcard
- Testing Mira cast with new Wifi library
- Bluez 5.38 from bluez.org
[COLOR="Blue"]2016/3/23[/COLOR]
- Latest 6.0.1_r22 (MHC19J) source from Omni
- kernel: update modem driver for i815
- Settings: fix a bug which cause Advanced page crash at the first launch
- SystemUI: fix a bug in status bar
[COLOR="Blue"]2016/2/22[/COLOR]
- Latest 6.0.1_r13 (MMB29U) source from Omni
- kernel: fix a bug in DT2W
- kernel: fix the occasional background process crash at cpu idle
- PerformanceControl: fix the initial settings for CPUsettings
- SystemUI: Fix the crash when 3minit battery apks not installed
- Latest update from Bluez
[COLOR="Blue"]2016/2/4[/COLOR]
Source revisions:
- Latest 6.0.1_r13 (MMB29U) source from Omni
- kernel: Double tap to wake (DT2W), initial commit
- kernel: DT2W, fine tune settings
- Settings: add DT2W settings in Advanced page of Performance Settings
- Settings: add bound region and time between taps controls
- Settings: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
- Bug fix in video playback
- Bluez: fix file send via bluetooth. (receive still fail)
[COLOR="Blue"]2016/1/15[/COLOR]
Source revisions: [ATTACH]3611268._xfImport[/ATTACH]
- Latest 6.0.1_r10 (MMB29T) source from Omni
- kernel: F2FS support
- kernel: Fix a bug in F2FS
- Rewrite samsung color format support
- Fix rotation freeze after deep sleep.
- To keep the data persist at reboot, PerformanceControl requries ROOT now
- Add Power (screen off) Tile to QS. Short press:screen off, Long press:power menu
- Include 3minit battery mod in SystemUI. (work with app from 3minit)
- Bluez 5.37 update from bluez.org
- DRM: low the security to Level 3
[COLOR="Blue"]2015/12/29[/COLOR]
Source revisions: [ATTACH]3592090[/ATTACH]
- Fix the RIL libraries for i815,
- GPS fix with Dmitry's patch as in cm-13.0
- Latest Nexus5 DRM blobs
- Introduce the new OmniJaws
- New boot animation and wall paper (seems not working for us)
- Delay the init.d script to 99ApkPermissions
- Increase the time out of AOT compiler
- New set of camera preview data for Tab-Plus
- gcc 4.9 is used for kernel and platform
[COLOR="Blue"]2015/12/16[/COLOR]
Source revisions: [ATTACH]3578277[/ATTACH]
- Latest 6.0.1_r3 (MMB29M) source.
- Add 80ApkPermissions script to init.d
- Add captive portal check switch in build property
- Fixes in telephony to support 6.0.1
- Add a few debug lines in camera HAL (for Tab-plus testing)
- Fix a few minor bug in kernel
- BlueZ update from bluez.org
- Start Handsfree protocol without WB
[COLOR="Blue"]2015/12/5[/COLOR]
Source revisions: [ATTACH]3565823[/ATTACH]
- Fix video recording in Camera
- Fix video playback (a bug in colorformat)
- Fix rotation stop after awake
- Suport SAMSUNG LPM in libhealth. (Fix reboot at power off when charge/usb cable is plugged)
- Merge Mali API 29 code to kernel driver.
- Update to Mali API 29 blobs
- A few patches in the kernel
- First port of BlueZ 5.36 to M
- Reinstate the BlueZ support in kernel and platform
[COLOR="Blue"]2015/11/24[/COLOR]
- Latest 6.0.0_r26 (MDB08M) source.
- Triple check the RIL libraries for p6200 and t869
- Patch in Camera HAL which fixed the torch in QS
- Merge the Linux kernel source 3.0.y (3.0.101).
- Disabled the Bluetooth backport for the time being. (Conflict with net)
- Support for Samung LPM which avoid rebooting at power off (when charger or USB cable connected)
- Include the GPS patch for the last build
- Fix the Power management HAL.
- Fix a few Omni features
- Fix the glitches at rotation
[COLOR="Blue"]2015/11/14[/COLOR]
- New blob for RIL (binary hack from newer Samsung device)
- RILClass: update the responses and include new requests
- optimize build script to shorten the time of flash
- Rewrite the Camera HAL
- Fix some Omni features
- Add GPU support to PerformanceControl
- Samsung Color Format support for codec
- Replace some text relocation blobs
[COLOR="Blue"]2015/11/4[/COLOR]
- Fix the external storage support
- Support for mode
- Support for OTG sdcard
- Fix the Camera
- Add screenshot tile in QS
- consolidate the boot menu
- included the libemoji for Emoji factory
[COLOR="Blue"]2015/10/27[/COLOR]
- Omni source 6.0.0_r1 (MRA58K), alpha release
- Fix build for Frameworks, Settings, PerformanceControl, Hardwares, etc.
- Fix release tool to pass build
- Fix boot loop in boot.img
- Fix orientation and colorspace
- Fix light sensor
- Fix GPS
- Add kernel uid_cputime support
- Add boot menu
Know issues:
1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
TO DO: Without the source of ES, nothing can be done.... *
2. Mobiledata for i815 probably working now.
TO DO: A shim library and a few patches with the blob. Can read the Baseband now. Waiting for report form i815 owner
3. Fast forward in video playback not working properly.
4. Adopted mode for ext. sd might not work.
5. May be more. Please report.
*** Number of asterisks indicate the importance and priority. ***
Screenshots: :laugh:
View attachment 3569154
Change log: :victory:
Code:
[COLOR="Blue"]2016/7/29[/COLOR]
- Latest 6.0.1_r52 (MOB30R) source from CM
- Add custom PowerHAL
- Add native support for double tap wake in Display settings
- BlueZ 5.41 update
[COLOR="Blue"]2016/6/9[/COLOR]
- Latest 6.0.1_r46 (MOB30M) source from CM
[COLOR="Blue"]2016/5/3[/COLOR]
- Latest 6.0.1_r30 (MOD30D) source from CM
- Fix the adaptive brightness and live display
- Bluetooth app: patch to work with Bluez
- BlueZ 5.39 update
[COLOR="Blue"]2016/4/5[/COLOR]
- Latest 6.0.1_r22 (MHC19J) source from CM
- Fix the occasional flickering for screen
- Testing Mira cast with new Wifi library
- Open source UMB library
- Enable write permission for external sdcard
- kernel: update modem driver for i815
- PerformanceControl: fix a bug which cause Advanced page crash at the first launch
- BlueZ 5.38 update
[COLOR="Blue"]2016/3/15[/COLOR]
Source revisions:
- Latest 6.0.1_r22 (MHC19J) source.
- All fixes in Omni6
- Fix the Display service for Ambient and Decouncing calculation
- kernel: A few minor fixes
- PerformanceControl: Fix the crash of Highend Graphics in Advanced page
- BlueZ update from bluez.org
[COLOR="Blue"]2016/2/10[/COLOR]
Source revisions:
- Latest 6.0.1_r13 (MMB29U) source.
- kernel: Double tap to wake (DT2W), initial commit (see post#2 for detail)
- kernel: DT2W, fine tune settings
- PerformanceControl: add DT2W settings in Advanced page
- PerformanceControl: add bound region and time between taps controls
- PerformanceControl: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
- SystemUI: fix a bug in 3minit battery which cause battery icon not shown
- Fix video playback.
[COLOR="Blue"]2016/1/22[/COLOR]
Source revisions: [ATTACH]3618827._xfImport[/ATTACH]
- kernel: fix a bug in F2FS
- camera: fix the format for barcode and Google translate
- Fix auto rotation. (Not working in the previous builds)
- PerformanceControl: settings are persist after reboot now
- DRM: low the security to Level 3
- Include 3minit battery mod in SystemUI. (see post#2 for detail)
- Bluetooth: Fix in l2cap settings. Files can be sent now but not received yet..
[COLOR="Blue"]2016/1/6[/COLOR]
Source revisions: [ATTACH]3601912._xfImport[/ATTACH]
- Latest 6.0.1_r10 (MMB29T) source.
- Add F2FS support in kernel
- Modify gpsd blob to load libdmitry
- Fix in sensor listener. (for rotation fail after deep sleep)
- gcc 4.9 is used for both kernel and platform
- Fix the RIL libraries for i815,
- Latest Nexus5 DRM blobs
- Increase the time out of AOT compiler
- Seperate set of camera preview and thumbnail data for Tab-Plus
- BlueZ 5.37 update from bluez.org
[COLOR="Blue"]2015/12/22[/COLOR]
Source revisions: [ATTACH]3585427[/ATTACH]
- Add libdmitry to fix Gps
- Modify gpsd blob to load libdmitry
- stlport build from source
- New DRM blobs from other device
- Add USES_LEGACY_ACQUIRE_WVM support to frameworks
- Add old Parcel::writeBlob() definition to work with the old blobs
- Add ApkPermissions script to init.d (to fix the permissions of Gapps)
- Fix i815 data by shim library
- exFat support for external sdcard (from CM)
- BlueZ update from bluez.org
[COLOR="Blue"]2015/12/10[/COLOR]
Source revisions: [ATTACH]3571293[/ATTACH]
- Latest 6.0.1_r3 (MMB29M) source.
- Enable hot swap to disable the "SIM card added" pop up
- Add captive portal check switch in build property
- Fixes in telephony to support 6.0.1
- Use original AOSP keyboard (CM's port crash on new Google service)
- BlueZ(5.36) support for M
- Start Handsfree protocol without WB
[COLOR="Blue"]2015/11/28[/COLOR]
Source revisions: [ATTACH]3563538[/ATTACH]
- Latest 6.0.0_r26 ((MDB08M) source.
- Patch in Camera HAL which fixed the torch in QS
- All fixes in Omni6
- Fix the Power management HAL.
- Mali API 29 blob update
- Merger Mali API 29 source to kernel driver (r3p2-01rev4)
Know issues:
1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
TO DO: Without the source of ES, nothing can be done.... *
2. Mobiledata for i815 probably working now.
3. Adopted mode for ext. sd might not work.
4. May be more. Please report.
*** Number of asterisks indicate the importance and priority. ***
Screenshots: :laugh:
Change log: :victory:
Code:
[COLOR="Blue"]2016/8/4[/COLOR]
- Latest 6.0.1_r62 (MTC20F)-DIRTY-DEEDS v-10.4
- Add custom PowerHAL
- Add native support for double tap wake in Display settings
- BlueZ 5.41 update
[COLOR="Blue"]2016/7/6[/COLOR]
- Latest 6.0.1_r46 (MOB30M)-DIRTY-DEEDS v-10.3
- All Fixes from Omni are included
[COLOR="Blue"]2016/5/25[/COLOR]
- Latest 6.0.1_r43 (MOB30J)-DIRTY-DEEDS v-10.2
- All Fixes from Omni are included
[COLOR="Blue"]2016/4/25[/COLOR]
- Latest 6.0.1_r30 (MOB30D)-DIRTY-DEEDS v-10.1
- All Fixes from Omni are included
- Testing Mira cast with new Wifi library
- BlueZ(5.39) update from bluez.org
[COLOR="Blue"]2016/3/29[/COLOR]
- Latest 6.0.1_r22 (MHC19J)-DIRTY-DEEDS v-10.0
- All Fixes from Omni are included
- Fix the occasional flickering
- Fix the crash in Display settings
- Assign the default write permission to external sdcard
- Fix the hardware decoder for video playback
- Reinstate the SuperSU-2.52 as built-in root
- PerformanceControl: Fix a potential crash when stated at the first time
- BlueZ(5.38) update from bluez.org
[COLOR="Blue"]2016/3/7[/COLOR]
- Latest 6.0.1_r13 (MMB29U)-DIRTY-DEEDS v-10.0
- All Fixes from Omni is included
- kernel: Full F2FS support
- kernel: Double tap to wake (DT2W), with fine tune settings
- PerformanceControl: DT2W settings in Advanced page
- PerformanceControl: zh-rCN, zh-rHK and zh-rTW translations
- Fixes in Display service for Ambient and Decouncing calculation
- Include the missing APN from last build
- Bluetooth: Latest Bluez stack with MM patches.
[COLOR="Blue"]2016/1/28[/COLOR]
- Android 6.0.1_r10 (MMB29T) -DIRTY-DEEDS v-10.0
- All kernel features as CM and Omni. OC, F2FS, uid_cputime, etc.
- All Fixes from Omni is included
- Fixes in Dirty Tweaks
- camera fix for barcode and Google translate included
- Include 3minit battery mod in SystemUI. (see post#2 for detail)
- Bluetooth: Latest Bluez stack with MM patches.
Know issues:
1. Fast forward in video playback not working properly.
2. Adopted mode for ext. sd might not work.
3. May be more. Please report...
Testing ...
Planning ...
Downloads: :highfive:
OmniROM:
AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
Dev-Host: OmniROM6
mirror: 百度网盘 ***Request from China.
CyanogenMod
AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
Dev-Host: cm-13.0
mirror: 百度网盘 ***Request from China.
DirtyUnicorns:
AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
Dev-Host: DU-10.0
mirror: 百度网盘 ***Request from China.
Gapps: OpenGapps DeltaGapps
** some Gapps might cause random reset and misbehaviour **
To ROOT: download the latest recovery flashable ZIP from chainfire.eu
Tested SpuerSU versions: Omni:2.49, 2.52, 2.65, 2.66 CM:2.49, 252
DU is already rooted.
Source:
github: https://github.com/danielhk?tab=repositories
Credits: :good:
** The OmniROM team who have such a good idea and their hardworks
** The CyanogenMod team who keep many devices alive!
** The DirtyUnicorns team's selflessness and persistance.
** All those donate and/or support me. Giving me the resources and reasons to carry on!
** The Bluez team who makes bluetooth possible for old devices!
** @Chainfire for the great SuperSU
Donations: :angel:
Extra Informations
Background Info. & Tips:
New approach for ext. SD and OTG
M auto-detect the external storage and mount it accordingly. For ext. SD, you may choose either Portable or Adopted mode. An adopted SD would act like the internal SD. When a SD (or USB OTG with an SD) is inserted, a notification will handle it. You might need a simple convertion first. If the card is originally FAT, FAT32 or EXT4, the content is most likely preserved. For obsolete format like exFat, the content will be erased.
*** In any case, backup the content first.
TIPS:
Remove Portable SD card before reboot or power ON. Google doesn't have device with ext. SD. Limited support.
If an ext. SD is inserted before boot, it might take longer to boot and sometimes a crash. Fixed!
The performance of adopted mode depends on the performance of the ext. SD. At least a class 10 is recommended.
In Portable mode, the mount point is automatically generated. You may browse its content from notification or Settings.
Update your file explorer (eg. ES) to latest if available.
** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
Things about Gapps
Everyone knows that Gapps are those proprietary apps from Google. For custom ROMs to have them. Contributors pull those apps and supporting libraries form an existing (usually the latest model with latest version available) stock AOSP ROM. Pack them into a recovery flashable zip. It is up to that contributor to decide which apps to included.
The question is "Why Gapps are so unfriendly to M?"
After some digging, I found a reason. The SensorManager has changed. Some essential functions that "Old" blobs (even from KK or some LP) required are undefined now. Thus some blobs would fail to load. The most obvious one is gpsd. Even if they were loaded, some function were failed. Play service can't get the LOCATION permissions because it "thinks" GPS is missing.
TIPS:
Those apps are usually located inside the /system partition. Flashing a ROM would format the /system partition and required flashing the Gapps again. Some Gapps are in /data and would survive. However, "thanks" to the eMMC brick bug, our devices won't actually format the /system partition. Hence Gapps would survive in our device.
A factory reset won't erase the Gapps but only their settings and data.
Since it is pull from other devices. Resolution can be an issue causing crashes in some old devices.
Gapps usually rely on Google services. Upgrading google services might affects some of the Gapps.
Gapps and some system apps can be disabled/enabled in Apps settings now.
** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
BlueZ support for Marshmallow
If you read the View attachment README.txt of BlueZ for Android. It states that Kitkat is fully functioning but some features are not yet or partial implemented in Android 5.0. Definitely more for 6.0. Socket (L2CAP & RFCOMM) is one of the partially supported. That means file transfer in Lollipop is not fully working now. Some devices with Bluedroid also face similar situation. During the porting, I found that 6.0 has change quite a lot. Some struct and functions are redefined. Some requests would crash in the Old HAL (Bluedroid too). I fixed a few things (eg. Handsfree protocol). May be still a few glitches but its usable. Let's hope for the best.
TIPS:
Devices would easier to connect when it is ON before the tab.
During calls, the Bluetooth icon would appear but with no audio.
You might need to press the Bluetooth button once to connect the audio to the Bluetooth headset.
When audio is connected, press the button will end calls as usual.
When audio is connected, volume keys would sync with the system volume.
F2FS (Flash friendly file system)
F2FS is a "new" thing. It is include in the Linux 3.8 kernel in late 2012. As the name imply, it is friendly to NAND storages. Since there is no cylinder, head and sectors, a different way to handle it seems sensible. The solid state flash storage is non volatile storage which requires a "higher" voltage to write (or flash). There is a life limit for such action (over 100K flashes for SLC). The MLC (and then TLC, QLC) technology make it easier to multiply the storage capacity but shorten the life of it at the same time. Most of the eMMC are MLC (1k ~ 5k flashes) now. How to make use of all the cells equally is definitely essential for the life of the flash storage. F2FS take it into account so it is "friendly" to Flash memories.
TIPS:
To test F2FS, just convert the /cache partition first. If the kernel doesn't support it, it would just fail to boot. It would done no harm to your valuable data.
Read only partitions (eg. /system) has no or little difference. For compatibility, most of the custom ROMs won't support it. No need to try.
Double Tap to Wake (DT2W)
This feature was implemented in a few China made phones for sometime. Recently, there is a leak of this disabled feature in the Nexus6 kerenl. There are a few ports in the Nexus' kernels. I studied them for a while and decided to make a move. ElementalX's kernel for flo helps a lot. I finally port it to my Nexus7 and our Tab. To increase the reliability and avoiding false activation, I added two interfaces for bound area and duration between taps. It depends on the resolution of the touch screen to decide the optimum values.
TIPS:
If you have dirty flash from earlier version or DU, you need to clear data of Settings. and reset. Otherwise the Advanced page in Performance Settings might crash.
The default bound between the taps is 30 pixels which is around the size of our finger tip. To avoid false activation (say inside a bag, etc.), you may make it smaller but it would required more accurate taps to activate.
Similarly, the shorter duration between the taps would lessen the chances of false activation but you need a quicker action to activate. The default duration is now set to 50ms. Taps over this period would be ignored.
Click to expand...
Click to collapse
Q & A:
Q: How to flash?
A: NOTE! This is for user with experience:
1. Latest TWRP (2.8.6.x or above) is required.
2. Download ROM (+Gapps (+SuperSU)) and copy to the Sdcard (external or internal.)
3. Backup data to external sd and keep in a safe place
4. Reboot to recovery (Press [PWR] + [Vol+], Release [PWR] when Samsung Logo appear)
5. Factory reset / wipe data
6. Flash ROM (+Gapps and SuperSU if you want to ROOT)
7. Reboot and wait for at least 10min. (Block mode not working for all devices. It might take longer for post setup)
** If you flash Gapps separately, it would cause "SetupWizard" to crash and other issue. **
Flash everything again at the same time. OR, see the fix in another Q&A below
Q: How to enable "Developer options" in Settings?
A: Follow the steps:
1. Settings > About Tablet
2. Hit "Build number" 7 times
To restore the default state (Developer options hiding):
1. Settings > Apps
2. Select the app "Settings"
3. Hit "Storage"
4. Hit "CLEAR DATA"
Q: Why my PC can't see the Tab when USB is connected?
A: With the USB cable connected, check the following:
1. Make sure USB debugging is ON. Settings > Developer options > USB debugging
2. Pull down the QuickSettings
3. Hit the "USB file transfer" Notification.
4. If Charging only is selected. Hit "Transfer files (MTP)" or "Transfer photos (PTP)".
Still not working!
1. Make sure the USB cable is OK
2. With the cable connected. Turn USB debugging OFF. Settings > Developer options > USB debugging
3. Turn USB debugging ON again.
4. A dialogue will popup on the Tab's screen. Enable the checker box (which is the PC connected)
Q: Why can't I download anything with Browsers?
A: M has a new stricter and wider permission settings.
For security reason, "Dangerous" permissions are disabled.
It is up to the user to decide and assign afterwards.
Futher info. of System Permission can be found HERE.
To check the permission for each app:
HTML:
Settings > Apps > [the app] > Permissions
Q: How to fix SetupWizard crash of Gapps?
A: As the above, It is the security again.
The permissions for SetupWizard are "Dangerous" and disabled.
Note: For CM with Gapps, there will be two SetupWizards. "com.cyanogenmode.setupwizard" and "com.google.android.setupwizard". The one with the blue CyanogenMod icon is from CM. It's the one comes with Gapps crashed.
1. Just flash ROM (+ SuperSU) only and set up the system first.
2. Then flash Gapps.
If SetupWizard crash after reboot:
Method 1:
3. You can still enter Settings via QS. There will be a short time slot after you press OK in the warning dialogue. A bit tricky but doable.
4. Select "Apps" and select "show system" in the advance menu. (top right)
5. Locate can select SetupWizard.
6. Select "Permissions"
7. Enable "Phone" and "Contacts" will stop the crash.
OR
Method 2:
Your device is rooted and you know how to use adb. Use the following commands:-
Code:
3. adb shell
4. $ su
5. # pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
The crash will stop immediately.
Q: How to fix Google Play service crashes?
A: Again It's the security. Google Play service requires the permissions
ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION.
BUT there is nowhere to set it.
Only a rooted device with adb can fix it:
Code:
1. adb shell
2. $ su
3. # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
4. # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
Q: How to enable 3minit battery mod?
A: Follow the steps:
1. Download V3.1 apps MinitBatteryResources and 3MinitBatterySettings
2. Install both apps
3. Reboot
4. Launch 3MinitBatterySettings to setup (take a while to start)
Note: The default size -20 is a bit too small, -5 is good enough for me
Click to expand...
Click to collapse
Thanks for your ROMS
Testing now
Not sure if placebo but its quite fast ,gonna try out doze
philipnzw said:
Testing now
Not sure if placebo but its quite fast ,gonna try out doze
Click to expand...
Click to collapse
Opening apps definitely felt quicker than 5.1.1
Nice to see android 6 on this dinosaur lol- just flashed and a lot of restarts and crashes hoping they will be fixed with updates thanks for another rom option
Sent from my Xperia Z Ultra using XDA Premium HD app
Thanks for the continued support
Seems very useable when gapps are not installed, but with them I cannot get past the setup wizard crashing.
Tried other gapps with the same result.
Anyone get past this already?
Edit: Seems installing everything and then factory resetting lets me get further.
Wow, I can't believe this device is still kicking! Even though I don't have mine anymore, it was my first android device. May it prosper
Hi Daniel
I've installed your new rom to my P6200.
The install process was as easy as usual. Flashed rom, g-apps and superSu in one turn.
The first boot took really a very long time (>10 min. SD was inserted). I was a little afraid that I was stuck at the boot-logo but finally the setup wizard appears. :highfive:
Setup went through without any problem. (except the known "SIM issue")
When I was trying to restore my backup from ext. SD with Titanium Backup I could not select ext. SD as usual.
So I did a search within the whole device
and the TI-backup folder was found at mysterious place
After the restore of my apps and data I started ES file explorer and found that the mysterious place is my ext. SD with a new name: 6E12-D522
When I attach USB memory it apears like this:
all the content is in one folder, so you have to open up this folder to find you folders and files on the stick (minor issue)
I was not able to send the screenshots to my google-drive via wifi.
I've had two unexpected FC till now.
Some times when leaving setting the apex-launcher needs some seconds to reload the app-icons.
Overall performance and handling is really good.
For a first experimental-release this is a great shot!! Thank very much Daniel.
I'm sure you will make marshmallow usable for our "stone-age" devices :fingers-crossed:
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
vinnity said:
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
Click to expand...
Click to collapse
Have the same problem, except with MX-Player + Codec ARMv7.
Install Youtube take long time, have to cancell and reinstall then it ok but during playing youtube just have sound with black screen also not get simcard.
Viper4android not working .-. Might be the selinux mode thingy ,haven't tried changing that yet
Can't get play store to install apps,just gives error message
Tablet crashed when changing sd card to adoption mode (panicked), 16gb card became 16mb ,reformating using slimkat helped fixed that
Overall it's very usable and smooth ,can't wait for next build
daniel_hk, thnx for your work! As i can feel, M running much faster, tnan 5.x.x - and thats really great.
Some issiues that i found
- video only shows in s/w mode in MX Player (no awesome player in developer options?)
- stock browser crashes on download
- Android terminal emulator crashes on start (may be this is app issue)
- seems that wi fi not stable, when playing video from samba share approx. every 10 min playback in mx player stopped. Fixing it by sliding left for a few seconds back
and last, that comes from 5.x.x (as i remember) - very long charging time with genuine samsung cable/adapter (as i remeber SkyHigh Kernel is quite faster), if it is possible to increase charging speed, that will be great!
Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep
Hope to have new build soon to experience
vinnity said:
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
Click to expand...
Click to collapse
uli-hh said:
Have the same problem, except with MX-Player + Codec ARMv7.
Click to expand...
Click to collapse
Harrison Le said:
Install Youtube take long time, have to cancell and reinstall then it ok but during playing youtube just have sound with black screen also not get simcard.
Click to expand...
Click to collapse
In my region, I can only access Youtube and Google services via VPN. Someone had set up a server for me to download the source. It is quite slow but working. I don't think I have the luxury and time to browse those...
Anyway, media codec seems not working yet. I think Omni team is working on it, I just don't want to repeat. I will take a look when official (or any other unofficial) is out.
philipnzw said:
Viper4android not working .-. Might be the selinux mode thingy ,haven't tried changing that yet
Can't get play store to install apps,just gives error message
Tablet crashed when changing sd card to adoption mode (panicked), 16gb card became 16mb ,reformating using slimkat helped fixed that
Overall it's very usable and smooth ,can't wait for next build
Click to expand...
Click to collapse
1. I'm not a gamer nor an active Youtuber. Can't help much. Let the experts discuss and share.
2. I had tested adopted mode with no problem. Yes, it is a bit lagging and might took a retry in reformatting. After that, there will be two partitions, one small and the rest would be internal.
M use a new approach to handle Sdcards. Our good old way of file browsing (eg. with ES) need to evolve. There is a link in post#2 which is the "detail" provided by Google... It might take some time to digest.
yurius said:
daniel_hk, thnx for your work! As i can feel, M running much faster, tnan 5.x.x - and thats really great.
Some issiues that i found
- video only shows in s/w mode in MX Player (no awesome player in developer options?)
- stock browser crashes on download
- Android terminal emulator crashes on start (may be this is app issue)
- seems that wi fi not stable, when playing video from samba share approx. every 10 min playback in mx player stopped. Fixing it by sliding left for a few seconds back
and last, that comes from 5.x.x (as i remember) - very long charging time with genuine samsung cable/adapter (as i remeber SkyHigh Kernel is quite faster), if it is possible to increase charging speed, that will be great!
Click to expand...
Click to collapse
1. See the above for video playback
2. I don't have problem in downloading with the included browser. Details please, to int. sd or ext. sd? which link? etc. It might be site related.
3. As before, I don't think I'm in the position to test third party apks.
4. What you described seems that it go to sleep and wake lock issue. MX might need an update for M.
5. This is another common question I don't want to answer. I'm not comfortable to compare nor pointing out who's right or wrong. Not long ago, someone think I ignored the fixes in S2 and keep on pressing and posting. Our mind is a funny thing. No matter how many time and whatever I said. I just can't change what someone think. Only if people willing to open their eye to see the fact. One man's candy can be the other's poison.
Nowadays, everything is efficiency oriented. People tends to pick a few keywords and think they get it. Only few would really read. I don't know how many people would read this but it's my habit to explain as clear as possible.
For charging, I think it apply to all devices...
There were a few things we believed working. I can tell you those few "tricks" are all included in the kernel either before or after for years. After studied the specifications (from chip manufacturer not Samsung) of the chips inside our tab carefully, I can tell you it is not what we thought.
a. The boot loader firmware has a set of value for the chip. Something like current limit.
b. No matter how high the current is applying, the main decision is inside the battery's circuitry. To avoid "explosion", it would allow only the right amount of current to charge the battery at a specific temperature.
If the device is ON, yes, the consumption of the OS would account for the time to fully charged. It depends on how many apks installed and running, environmental aspects like wifi signals, carrier signals, temperature, etc. It is just too argumentative to "feel".
If it is OFF, the difference should be neglected. The boot loader firmware has its own set of value. No matter what inside the tab's memory, even without a kernel or ROM, it can still charge the battery. The kernel binary (which I already mentioned has the same "tricks") is account for showing the charging images and sensing the buttons etc. Yes, there are differences on the only few services (adb, screens, etc.) but it is simply neglectable.
The main aspect would be the age of the battery which account for how long and how fast it is charging. Just do an experiment. Flash different ROMs and time the differences.
uli-hh said:
Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep
View attachment 3535470
Click to expand...
Click to collapse
Yes, the radio daemon crash because the ril blob is tooooo old. It would retry indefinitely even if you are in flight mode. It would be definitely a drain. The good news is that I think I found a fix. I'm working on it now. It would be the ultimate solution which I believe we can survive a few more generations.
To all:
This is a completely new OS. Some apks are not working as expected. When the time come, apks might have updates. In this experimental build, some features are not working yet. This is not the daily driver if you are looking for.
Thanks for the support and enthusiasm but no matter how many wants and hopes are there. No matter how many people mentioned how times times, I simply don't have the resource and time to fulfil them all. I appreciate the detail reports on issues which I miss or overlook. I'm humble to those pointing me out. Although only few people would really read, I'm polishing the presentation of my posts. I "hope" people would know what I'm doing.
@daniel_hk - the source revision attachments in the omni change log says it's missing when i try to open it.
Thanks for your hard work. I started on a slim marshmallow build, but it was missing a number of code patches in their base code
p3dboard said:
@daniel_hk - the source revision attachments in the omni change log says it's missing when i try to open it.
Thanks for your hard work. I started on a slim marshmallow build, but it was missing a number of code patches in their base code
Click to expand...
Click to collapse
Yeah! I don't why it's gone :cyclops:
I have uploaded the attachment again. Thanks!
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.
As most of you guys know Magisk will not work for us on the international snapdragon S9 and S9+
So, I have made a custom kernel that will allow us to have root on stock pie firmware.
You will need to format data unless you want to stay encrypted. If you wish to stay encrypted you can.
Files needed:
klabit kernel V6.5
FK Manager g9650 kernel download configuration link
FK Manager g9600 kernel download configuration link
FK Manager g9650 GSI kernel download configuration link
FK Manager g9600 GSI kernel download configuration link
Copy the g96x0_q_vx.zip to your external sd card.
Make sure you have TWRP installed
Flash the g96x0_q_vx.zip
Flash Magisk
Reboot to system.
If you currently do not have a working lockscreen/pin/fingerprint setup, you will need to restore your stock boot.img either via backup or extract your boot.img from the official firmware and flash the img then flash my kernel.
Changelog:
Code:
V6.5
[LIST]
Merge OSRC: N9600ZHU5FTK1
[/LIST]
V6.4
[LIST]
Merge OSRC: G9650ZHS6DTG2
Merge OSRC: G9650ZHS7ETH1
Remove additinal SafetyNet flags from /proc/cmdline
Proc: Fake CMDline
Merge OSRC: G9650ZHU7ETI3
Merge OSRC: G9650ZHU7ETJ2
Expanded GSI kernel compatibility for Android 11 support
[/LIST]
V6.3
[LIST]
Merge OSRC: G9650ZHS6DTF1
Merge OSRC: G9650ZCU6ETF6
[/LIST]
V6.2
[LIST]
Merge OSRC: G9650ZCS6DTD5
[/LIST]
V6.1
[LIST]
Add powersave governor
Add conservative governor
Add ondemand governor
[/LIST]
V6.0
[LIST]
[*]7e123dad108c Import crownqlte && starqlte defconfigs
[*]824f70f8d070 Add .gitignore
[*]7d3612a88cbf Import G9600 and N9600 defconfig && initialize
[*]c1e7a35e59a7 Import G9600 and N9600 dts with verity removed
[*]0a587fae1745 Add option for gsi mtp driver
[*]10b851dfaa03 star2qlte: Initialize defconfig
[*]5f38f4cc0d99 Remove verity
[*]101dedaf7aec scripts: remove localversion + from kernel version strings
[*]c1b726584344 selinux: enable selinux faking
[*]70ed91e9c15a star2qltechn: Enable Samsung MTP driver
[*]9c88019d96fd drivers: usb: add separated Samsung MTP option
[*]6c54f88a648b star2qltechn: Update defconfig
[*]13a223ea3ed9 dts: disable avb,verify
[*]5c36fed8d37b Regen configs
[*]9a37c1921037 (osrc) OSRC: G9650ZCU6DTA9
[/LIST]
V5.9
- Small version bump to 5.9.
- Integrate auto patch of security patch date since Samsung slow af. (Credit to [user=4280397]@djb77[/user])
- Better GSI compatibility.
- Better OneUI compatibility for recent/most up-to-date firmwares.
V5.8
- Fix compilation issue for n9600
- Version update to V5.8
- Add changelog
- Update crownqlte defconfig
- OSRC: G9650ZCU6CSJ2
- Merge SM-N9600 defconfig and dts
V5.7
- Merge G9650ZHU5CSH6 source which includes fix for the recent zero day on android binder driver
- Prevents potential wake-lock while on wireless charger
- Merge G9650ZCU5CSI3 source which includes some Note9 camera integrations
- Adds support for wireless adapters based on Broadcom 43436 chipset
- Increased wifi security
- Increased wifi hotspot security
- DHD 100.13.36.1 - 2019.07.31
Security Patch
- CS8424803(By Choi Hyeonu) SI-14869: Moved the length check routine for the nlioc variable before accessing it in the wl_cfgvendor_priv_string_handler() function
DHD 100.13.36 - 2019.05.24
New Feature
- CS5350346(By Jung Junyeop) Fake AP - Fixed to provide correct channel information for beacon receive result
- Enable to support Fake AP
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
- WIPS attack warning reporting
(This patch should be sync up with FW 13.38.60(4361B0), FW 13.50.10(4361B2) or higher version)
Security Patch
- CS8069399(By Kang Hyung Wook) SI-13926 Fixed use-after-free in the wl_cfg80211_set_mgmt_vndr_ies function
Others
- CS7939107(By Kim Tae-Yong) Included memdump value prints in the dump information
- Added missing options into the Kconfig file
DHD 100.13.32 - 2019.04.26
Kernel Panic
- CS7696936(By Min SungBin) Fix misspelling of CUSTOMER_HW4_DEBUG definition
- CS7706946(By Min SungBin) Fixed to avoid kernel panic due to race condition of cfg->scan_request
Security Patch
- CS7860687(By Kang Hyung Wook) SI-12455: Fixed use-after-free write in dhd_set_monitor() function
- CS7949699(By Choi Hyeonu) SI-14074: Fixed Security issue, Potential stack-based buffer overflow in dhd_pktfilter_offload_set
- CS7956197(By Choi Hyeonu) SI-14130: Fixed the multiple NULL pointer dereference in wl_cfgvendor.c
Others
- CS6844193(By MinSoo Kim) Changed log level of LQCM report
- CS7099653(By Nitesh Suthar) Enabled frameburst to enhance throughput for BCM43436 projects
- CS7362375(By Gu Ja Heon) Added Private command in order to receive every beacon in Suspend
- CS7526157(By Suthar Nitesh) Fixed DualBandConcurrency field in .softap.info
- CS7765577(By Park Heebae) Wifi-on time reduction by reading necessary CIS information
- CS7827257(By Choi Hyeonu) Fixed kernel panic caused by invalid memory access
- CS7834653(By Kang MinHo) Removed redundant TX error prints during suspend in SDIO
- CS7884436(By Beom Jip Kim) Fixed to cancel p2p listen offloading by framework scan request
- CS7892037(By Sun Yinghan) Fixed to support W2018/KELLY Android P OS upgrade
DHD 100.13.31.1 - 2019.04.19
Others
- CS4726130(By Min Hyun-Ki) Added User priority to AC mapping in case of various DSCP types that may not compatible with RFC8325
- CS6951980(By Min Hyun-Ki) Changed the UP to AC mapping of CS6 based on the RFC8325
DHD 100.13.31 - 2019.02.15
Others
- CS7241767(By LEE EONJI) Added more logs for the DPC schedule error debugging
- CS7299641(By Kim MinSoo) Enabled LB_TXP for MSM8998 Platform
- CS7323375(By kwon Jaecheol) Enabled the softap.info file support in BCM4359 platform
- CS7362527(By Hyeonu Choi) Cancel P2P listen offloading operation when SoftAP brings up
- CS7363197(By Junhak Lim) Fixed prevent issues
- CS7386068(By Lee Gibum) Disabled frameburst for "2.4Ghz + SoftAP" (Drame & Great projects)
- Fixed the scan failure when p2p listen offload is triggered
- Fixed to abort scan when connection/disconnection requested
- Prevented the bus suspend by the PCIe Runtime PM from abnormal ISR status
V5.5
- Merge G9650ZHU5CSG8 source which includes some stock Samsung debugging sanity checks and increase of stability
- Prevent possible IO/wake-locks when accessing sdcard
V5.4
- Merge G9650ZCU5CSFB source which includes additional ethernet support and additional battery stats support
- Removed more verity from the appended dtb
- Finally fixed FK Manager compatibility!! (ie no longer need to reflash Magisk)
V5.3
- Added Conservative gov for G9600 (sorry I could have sworn I included this in V5.2)
- Fix stability issues
- Remove Interactive governor
V5
- Removed Defex
- Removed Samsung rooting protections
- Removed RKP (Realtime Kernel Protection)
- Added Conservative cpu governor
- Sanity checks for video drivers and the power share feature
- Added support for broadcom 43456 wireless cards
- Added ddhd random mac scanning
- Added more security to wifi hotspot to protect from ARP attacks,
- CS7111512(By LEE EONJI) Detect turn on failure in factory binary
- CS7299329(By Kim Yu-Kyoung) Fixed SoftAP CTS fail due to interface creation failure
- Blocked WLC_E_ROAM event to fix wakes-up frequently under weak signal AP
- Changed error results of GETSTAINFO private command to BCME_UNSUPPORTED if the BIGDATA_SOFTAP is not supported
- Fixed kernel panic during mfg mode interface creation
- CS7091164(By Kang Hyung Wook) SI-13561: Fixed kernel heap overflow security issue at dhdpcie_downloadvars
- CS7091371(By Kang Hyung Wook) SI-13584: Fixed kernel panic due to access to not allocated memory
- CS6785460(By Jeong Min Cheol) Send HANG event to the framework for the sequential private command failure
- CS7003600(By Kang MinHo) Support android private command for restoring roam/scan parameters
- CS7094302(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7103552(By LEE EONJI) Fixed the recovery routine to fix the D3_ACK timeout issue
- CS7119174(By Kim Seong Hwan) Avoid HANG event indication due to sequential private command failures in case of unsupported error
- CS7137399(By Yoon YeJi) Fixed connect failure caused by connection information not initialized
- CS7141596(By Suthar Nitesh) Fixed MHS operates with STA mac address
- Control HANG report for consecutive Android private command failure by sysfs
- Increased the NUMBER_SEQUENTIAL_PRIVCMD_ERRORS from 4 to 7
- Taking a SOCRAM dump in the sequential private command error case
- CS6935603(By Hong Min Whoa) SI-13638: Fixed Kernel warning message by restructuring the DMA_LOCK and DMA_UNLOCK
- CS7091347(By Kang Hyung Wook) SI-13585: Fixed kernel panic due to write buffer exceeds the size
- CS6650676(YeJi Yoon) Fixed mismatch connect status between framework and DHD
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6715508(By Choi Hyeonu) Exported sysfs for ADPS bad AP list
- CS6744438(By Yoon Jae Ho) Fixed duplicated roaming notification to WPA supplicant during FT roaming
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6856753(By kwon Jaecheol) Added the dual interface capability filed in the SoftAP info file (.softap.info)
- CS6870793(By Tae-Yong Kim) Fixed prevent issues
- CS6871138(By Lee Gibum) Configure AER registers to debug PCIE ERROR ATTN issues
- CS6880409(By Sung-gi Choi) Fixed prevent issues
- CS6887298(By Min Whoa Hong) Fixed prevent issues
- CS6928243(By Sung-gi Choi) Fixed prevent issues
- CS6935678(By Hwang MinSik) Fixed array out of bound issue from sysfs mac address
- CS6984743(By Min SungBin) Print DPC schedule request timestamp for ROT issue
- CS6985032(By LEE EONJI) Enabled DHD_RECOVER_TIMEOUT for D3_ACK missing case on 4359C0 and 4361B0
- CS6993967(By Jeong Min Cheol) Added last_d3_inform_timestamp to check root cause of ROT
- CS7042030(By Min SungBin) Implemented the new API to sync up the status between RC and EP to avoid unwanted L1ss configuration
- Changed the DHD_COMMON_DUMP_PATH for non-BCM4375 Android P OS projects
- DHD driven random mac enable by default for 4361B0
- Enable frameburst for standalone 2.4GHz SoftAP on Dream and Great project
- Wi-Fi Sharing-Lite feature support for Android P OS
- CS6461136(By Min SungBin) Fixed for kernel panic due to stack overflow at get_roamscan_channel_list()
- CS6302259(By Kang Hyung Wook) Supported DHD driven Random MAC feature
- CS6324532(By Choi Hyeonu) Port files under /data/vendor/conn to sysfs after Android P OS
- CS6396705(By Min SungBin) Added additional timestamp log to debug resumed on timeout issue
- CS6398346(By Hyeonu Choi) Fixed prevent issues
- CS6516071(By Choi Hyeonu) Fixed for corner case of schedule_timeout() API at dhd_timeout_expired()
- CS6536174(By Choi Hyeonu) CS6433018(By Choi Hyeonu) Fixed prevent issues
- CS6594869(By Min SungBin) Triggering Kernel panic for the scheduling problem only if the memdump mode is enabled
- CS6600348(By LEE EONJI) Implemented 4359c0/GraceR P OS Wi-Fi sharing feature
- CS6658253(By Choi Hyeonu) Fixed random mac setting issue instead of otp mac
- CS6678972(By Hwang MinSik) Fixed TIS/TRP test failure and high current issue from sysfs change
- CS6713692(By Kim MinSoo) Fixed NET_RX delay issue
- CS6769798(By Kim Beom Jip) Fixed for GraceR/4359c0 P OS P2P connection failure issue
- CS6791516(By Lee Gibum) Fixed the unexpected frameburst enable on standalone SoftAP in 2GHz
- CS6791556(By Hwang MinSik) Removed CR/LF character at .cid.info including sysfs
- CS6809444(By Hwang MinSik) Unified DHD_COMMON_DUMP_PATH for the Android P OS project of all chips
- Changed the timestamp value to Kernel local time to debug resumed on timeout and scan timeout issues
- Defer RxBuf post size based on the rxbufpost_sz iovar return value for monitor mode
- Disabled DHD_LB_IRQSET for Exynos8890 platform
- Dump AER HeaderLog registers in configuration space for PCIe debugging
- Dumping PCIe registers for PCIe debugging enhancement
- Fixed VHT features enable issue from GraceR project
- Fixed unexpected RSDB mode configuration for legacy RSDB chip
- Implemented the debug code to check if the scan timeout or resumed on timeout happens due to the DPC scheduling problem
- Refined TDLS initialization code
Kernel source: https://github.com/klabit87/android_kernel_samsung_sdm845
Thanks to @tylerhole and the @stang5litre test group for testing anything I throw at them!
Thanks to @djb77 for the ramdisk patches
You guys are the best!
Hell yeah bro! Kickin ass and takin names as per usual! Killer job! Thanks!
very good, I has test it,OK, work fine.
I want to know how to modify the kernel configuration file.
.
Oh God! Thank you teacher, really thank you, you have taken our terminal to another level, God bless. I hope you will continue with us a lot longer. Greetings.
i loaded TWRP from Travis82 , got stuck un a bootloop screen from twrp.
franc33s said:
i loaded TWRP from Travis82 , got stuck un a bootloop screen from twrp.
Click to expand...
Click to collapse
How long did you wait? You will need to wait for 10-12 minutes and it will boot. I tested this multiple times myself and others as well before I released it here.
Sent from my Pixel 2 XL using Tapatalk
tomatolei said:
very good, I has test it,OK, work fine.
I want to know how to modify the kernel configuration file.
.
Click to expand...
Click to collapse
Check my GitHub. The source is linked at the bottom of the op. I'm working on updating sources for TWRP as well.
Sent from my Pixel 2 XL using Tapatalk
franc33s said:
i loaded TWRP from Travis82 , got stuck un a bootloop screen from twrp.
Click to expand...
Click to collapse
I bet your phone was connected to the computer. Travis TWRP causes reboots when plugged in which is why we dont use it.
stang5litre 5.0 Edition Roms
klabit87 said:
How long did you wait? You will need to wait for 10-12 minutes and it will boot. I tested this multiple times myself and others as well before I released it here.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
ohh so the bootloop should be normal for 10 to 12 minutes? tough it would be stuck on the samsung bootscreen for those minutes, im goint to try again then.
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
stang5litre said:
I bet your phone was connected to the computer. Travis TWRP causes reboots when plugged in which is why we dont use it.
stang5litre 5.0 Edition Roms
Click to expand...
Click to collapse
with one should i use then?
I did the steps as you indicated them and when restarting (for the second time) in TRWP I can not access the internal storage and I have encryption, what do you suggest doing? by others it works normally, I have a successful ROOT.
NOTE: the steps that I followed were the following:
1 flash zip root foot, from external memory
2.- format data (yes)
3.- reboot
4.- Again reboot
5.- again restart, but now in twrp.
franc33s said:
ohh so the bootloop should be normal for 10 to 12 minutes? tough it would be stuck on the samsung bootscreen for those minutes, im goint to try again then.
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
with one should i use then?
Click to expand...
Click to collapse
I would use @klabit87 TWRP as it doesn't have that issue. Its posted in his thread
stang5litre said:
I would use @klabit87 TWRP as it doesn't have that issue. Its posted in his thread
Click to expand...
Click to collapse
the problem with the twrp of klabit87 is that it does not recognize mtp, and that option is very useful when the device does not turn on and you want to extract your data and thus format the system, or is it already working?
stang5litre said:
I would use @klabit87 TWRP as it doesn't have that issue. Its posted in his thread
Click to expand...
Click to collapse
so the one he did for the note 9? should work without any problems?
chalofito said:
the problem with the twrp of klabit87 is that it does not recognize mtp, and that option is very useful when the device does not turn on and you want to extract your data and thus format the system, or is it already working?
Click to expand...
Click to collapse
Travis doesn't either. His reboots with computer connected to phone klabits doesnt, so not sure what your missing ?
stang5litre 5.0 Edition Roms
stang5litre said:
Travis doesn't either. His reboots with computer connected to phone klabits doesnt, so not sure what your missing ?
stang5litre 5.0 Edition Roms
Click to expand...
Click to collapse
travis twrp does it, you just have to deactivate and activate mtp and connect without problem, but that's not the problem, my problem is that I can not access internal storage, and I can not flash anything, it tells me that it has not been mounted data , and create me I do the steps that klabit mentions for the root on android pie. please help me.
franc33s said:
so the one he did for the note 9? should work without any problems?
Click to expand...
Click to collapse
No. do not use the one for Note 9.
I have a twrp on my afh. I didnt make it public because it is not complete since mtp doesnt work. But others found it so whatever.
chalofito said:
travis twrp does it, you just have to deactivate and activate mtp and connect without problem, but that's not the problem, my problem is that I can not access internal storage, and I can not flash anything, it tells me that it has not been mounted data , and create me I do the steps that klabit mentions for the root on android pie. please help me.
Click to expand...
Click to collapse
Your internal storage is encrypted currently. I will work on decryption in a bit. but until then use your microsdcard and be patient.
I plan to update twrp with pie sources and make sure that mtp and adb are working properly.
klabit87 said:
Your internal storage is encrypted currently. I will work on decryption in a bit. but until then use your microsdcard and be patient.
I plan to update twrp with pie sources and make sure that mtp and adb are working properly.
Click to expand...
Click to collapse
Thanks was all I wanted to know, gladly I hope, for the moment I will install the firmware more root, since I thought that the problem was me and I was doing something wrong. Greetings.:highfive:
klabit87 said:
No. do not use the one for Note 9.
I have a twrp on my afh. I didnt make it public because it is not complete since mtp doesnt work. But others found it so whatever.
can you send me it?
Click to expand...
Click to collapse
franc33s said:
klabit87 said:
No. do not use the one for Note 9.
I have a twrp on my afh. I didnt make it public because it is not complete since mtp doesnt work. But others found it so whatever.
can you send me it?
Click to expand...
Click to collapse
As i believe it was stated before, mtp does not work on this one but adb does and it does not reboot instantly if you are plugged into your pc.
https://forum.xda-developers.com/showpost.php?p=78571048&postcount=143
Click to expand...
Click to collapse
stang5litre said:
I would use @klabit87 TWRP as it doesn't have that issue. Its posted in his thread
Click to expand...
Click to collapse
Isn't his twrp only for g9650?