CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
And most important: DON'T READ THE OP
What's working:
Wifi (connection, tethering, etc)
Bluetooth
Camera, video codecs
RIL (Calls, SMS, mobile data)
Storage (both internal and external)
MTP storage (both internal and external)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS
Sound recording
Torch (flashlight)
BUGS/Not working :
There're lots of bugs, but main are
(SM-G313ML) Mobile data doesn't work
Switching to other fonts will get bootloops after restart. In this case, if you use TWRP recovery, go to File Manager >> delete "themes" from /data/system would help you escape this without factory reset
Distorted Bluetooth sound on calls
First time installing CyanogenMod 12.1 to your Galaxy V, or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended)
INSTALLATION VIDEO
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, be kind and give proper credits
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-source doesn't mean "out of respect"
DOWNLOADS:
Click to expand...
Click to collapse
In Downloads section
Mirror: Beta 3 Update 1
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy Ace 4
Contributors
doesntexits, ngoquang2708
Source Code: https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-12.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 3 Update 1
Beta Release Date: 2016-05-28
Created 2016-02-16
Last Updated 2016-06-12
CHANGELOG:
- ALPHA-1
Initial release
- ALPHA-2
Fixed ION driver, now camera, video codecs, etc are working
Fixed audio
Dual-SIM is dead for now
Reserved zRAM size to 128MB
- ALPHA-3
Fully fixed RIL (thanks to @ngoquang2708), will switch to beta on next builds
Fully fixed Bluetooth
- BETA-1
Faster app installation, but slower app startup, a trade-off!
Improve media playback: some media app can play flawlessly, but not YouTube, sorry
zRAM size now can be set in build.prop
thanks to @ngoquang2708
- BETA-2
Fixed audio stuffs
Fixed video decoding stuffs (included YouTube)
Fixed video recording
Don't remember list start, blah blah...
- BETA-3
Updated sources, Android security patch version 2016-04-01
Switched memory allocator to dlmalloc(), which increase performance a lot
Odexed apps now will be in /system partition, not in /data/dalvik-cache anymore (significantly save internal storage, as this thingy eats up to 300MB of our internal storage)
Powered by OC Kernel (unexpectedly compiled )
- BETA-3 update 1: Fixed random reboots, switched to stock kernel
F.A.Q
Q: ROM startup too slow?
A: This device is just a single-core phone, so the first startup is super-duper slow, and some lags are expected during usage
Q: ETAs?
A: See here: Link
Q: Anymore models supported?
A: SM-G313ML, SM-G313H
Q: Is init.d supported on this ROM?
A: Every CyanogenMod ROMs support init.d, so be free at scriptings
Q: Can you include ABCXYZ feature / Samsung Apps here?
A: NO!
Q: Can i use your ROM as a base for portings?
A: Yes, you could, but give proper credits
Q: Status 7 when installing the ROM?
A: Use TWRP recovery to install the ROM, as CWM is not supported yet
Q: Server error in Google Play Store?
A: Install latest Google Play Services manually first (might take long time, due to Lollipop's nature), then you can install apps from GG Play as usual
Finally, I've waiting for a long time for this cm 12.:good:
Cool nice to see more spredtrum device get cm
great work
btw is audio working ?
Dreamstar said:
Cool nice to see more spredtrum device get cm
great work
btw is audio working ?
Click to expand...
Click to collapse
Yes, it's working
Remove audio CFLAGS from BoardConfig.mk and use audio_policy.default, it still working. IDK why
@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.
doesntexits said:
@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.
Click to expand...
Click to collapse
Well grep through Camera or HWC HAL and see whether they are dependent on those symbols or not:/
Anyways, I had a confusion about HWRendering and HWC. I still have tho.
SWRendering means running the system on CPU only, on HWRendering, its done by GPU (and CPU probably). HWC plays a part in it, if HWC is broken, I don't think HWRendering will necessarily be broken. So you were right earlier .
So if on egl.cfg, you are on mali renderer and no kernel.qemu flag set, and everything is fine, then HWRendering works, you would probably mention that HWC is not working. Anyway if that's the case, have you applied this icu4c patch?
Because we have applied it and boom, HWRendering is broken badly. We are on SWRendering now, and its so sluggish.
corphish said:
Well grep through Camera or HWC HAL and see whether they are dependent on those symbols or not:/
Anyways, I had a confusion about HWRendering and HWC. I still have tho.
SWRendering means running the system on CPU only, on HWRendering, its done by GPU (and CPU probably). HWC plays a part in it, if HWC is broken, I don't think HWRendering will necessarily be broken. So you were right earlier .
So if on egl.cfg, you are on mali renderer and no kernel.qemu flag set, and everything is fine, then HWRendering works, you would probably mention that HWC is not working. Anyway if that's the case, have you applied this icu4c patch?
Because we have applied it and boom, HWRendering is broken badly. We are on SWRendering now, and its so sluggish.
Click to expand...
Click to collapse
I haven't patched anything. Just used the source and it still works. Our HW rendering seems working fine, but it's very sluggish if in low RAM mode (damn laggy, lockscreen goes black). IDK why that CPVE works with HWC? Maybe some more "grep"?
Btw, our camera already gives missing symbol in logcat. It disappeared from Trebuchet and if open it from lockscreen, it FCs, so everything related to ION driver are broken for now. IDK why codecs needs ION (failed allocating)
Another question: How to make a link in makefile? Prebuilt webview doesn't work if missing a link to /system/app/webview/lib/arm
Edit: I got wrong question The coreprimeve3g HAL requires those symbols:
Code:
[email protected]:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
Camera HAL:
Code:
_ZN7android13MemoryHeapIon16IOMMU_is_enabledEi
_ZN7android13MemoryHeapIon9free_iovaEimj
_ZN7android2spINS_13MemoryHeapIonEED2Ev
_ZN7android2spINS_13MemoryHeapIonEED1Ev
_ZN7android2spINS_13MemoryHeapIonEEaSEPS1_
_ZN7android13MemoryHeapIonC1EPKcjjm
_ZNK7android13MemoryHeapIon9getHeapIDEv
_ZN7android13MemoryHeapIon21get_phy_addr_from_ionEPmPj
_ZN7android13MemoryHeapIon8get_iovaEiPmPj
_ZNK7android13MemoryHeapIon7getBaseEv
_ZN7android13MemoryHeapIon9Free_iovaEiimj
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
_ZN7android13MemoryHeapIon8Get_iovaEiiPmPj
_ZN7android13MemoryHeapIon16flush_ion_bufferEPvS1_j
MemoryHeapIon::Get_mm_ion: %d addr 0x%x size 0x%x
MemoryHeapIon::Get_mm_iova: %d
allocCameraMem: error pHeapIon is null.
allocCameraMem: error get pHeapIon addr - method %d result 0x%x
MemoryHeapIon::Get_mm_ion: %d addr 0x%lx size 0x%x
But... with libbinder:
Code:
[email protected]:~/Downloads$ strings libbinder.so | grep Ion
[email protected]:~/Downloads$
Nothing shown. IDK why. Maybe Sammy has applied ION driver inside those HAL blobs :/
doesntexits said:
I haven't patched anything. Just used the source and it still works. Our HW rendering seems working fine, but it's very sluggish if in low RAM mode (damn laggy, lockscreen goes black). IDK why that CPVE works with HWC? Maybe some more "grep"?
Btw, our camera already gives missing symbol in logcat. It disappeared from Trebuchet and if open it from lockscreen, it FCs, so everything related to ION driver are broken for now. IDK why codecs needs ION (failed allocating)
Another question: How to make a link in makefile? Prebuilt webview doesn't work if missing a link to /system/app/webview/lib/arm
Edit: I got wrong question The coreprimeve3g HAL requires those symbols:
Code:
[email protected]:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
But... with libbinder:
Code:
[email protected]:~/Downloads$ strings libbinder.so | grep Ion
[email protected]:~/Downloads$
Nothing shown. IDK why
Click to expand...
Click to collapse
Alright..recursive grep through lib folder
Code:
cd system/lib
grep -R Ion
You mean symbolic link?
Code:
$(shell ln [-OPTIONS] <source> <target>)
corphish said:
Alright..recursive grep through lib folder
Code:
cd system/lib
grep -R Ion
Click to expand...
Click to collapse
Haha, we got our result. MemoryHeapIon is being used as seperate lib.
Code:
[email protected]:~/Downloads/lib$ grep -R Ion
Binary file libstagefright_sprd_h264enc.so matches
Binary file libstagefright_sprd_vpxdec.so matches
Binary file libstagefright_sprd_h264dec.so matches
Binary file hw/camera.sc8830.so matches
Binary file hw/hwcomposer.sc8830.so matches
Binary file libstagefright_sprd_mpeg4enc.so matches
Binary file libomxvpu.so matches
Binary file libstagefrighthw.so matches
Binary file libvpu.so matches
Binary file libstagefright_sprd_mpeg4dec.so matches
Binary file libmemoryheapion.so matches
[email protected]:~/Downloads/lib$
I thought it must be in binder, but we've all wrong
doesntexits said:
Haha, we got our result. MemoryHeapIon is being used as seperate lib.
Code:
[email protected]:~/Downloads/lib$ grep -R Ion
Binary file libstagefright_sprd_h264enc.so matches
Binary file libstagefright_sprd_vpxdec.so matches
Binary file libstagefright_sprd_h264dec.so matches
Binary file hw/camera.sc8830.so matches
Binary file hw/hwcomposer.sc8830.so matches
Binary file libstagefright_sprd_mpeg4enc.so matches
Binary file libomxvpu.so matches
Binary file libstagefrighthw.so matches
Binary file libvpu.so matches
Binary file libstagefright_sprd_mpeg4dec.so matches
Binary file libmemoryheapion.so matches
[email protected]:~/Downloads/lib$
I thought it must be in binder, but we've all wrong
Click to expand...
Click to collapse
Get me that blob plox..and see my earlier post..I did not see your query abt webview
Edit @ doesntexits
Add it and see logs, HWC and Camera HAL should load.
You will probably need a factory reset to make Camera App visible, and the torch toggle too.
Because during first boot, if Camera HAL fails to load, no camera app in system will be viewed even tho its fixed later.
corphish said:
Get me that blob plox..and see my earlier post..I did not see your query abt webview
Click to expand...
Click to collapse
Change it to .so
corphish said:
Edit @ doesntexits
Add it and see logs, HWC and Camera HAL should load.
You will probably need a factory reset to make Camera App visible, and the torch toggle too.
Because during first boot, if Camera HAL fails to load, no camera app in system will be viewed even tho its fixed later.
Click to expand...
Click to collapse
But...
Code:
E/HAL ( 178): load: module=/system/lib/hw/camera.scx15.so
E/HAL ( 178): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIonC1EPKcjjm" referenced by "camera.scx15.so"...
E/CameraService( 178): Could not load camera HAL module
and...
Code:
E/HAL ( 124): load: module=/system/lib/hw/hwcomposer.scx15.so
E/HAL ( 124): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPiS1_" referenced by "hwcomposer.scx15.so"...
E/SurfaceFlinger( 124): hwcomposer module not found
Edit: I "grep"ed again, and those symbols from our libs is different than libmemoryheapion.so. Looks like we've to re-build it for ourselves
doesntexits said:
But...
Code:
E/HAL ( 178): load: module=/system/lib/hw/camera.scx15.so
E/HAL ( 178): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIonC1EPKcjjm" referenced by "camera.scx15.so"...
E/CameraService( 178): Could not load camera HAL module
and...
Code:
E/HAL ( 124): load: module=/system/lib/hw/hwcomposer.scx15.so
E/HAL ( 124): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPiS1_" referenced by "hwcomposer.scx15.so"...
E/SurfaceFlinger( 124): hwcomposer module not found
Edit: I "grep"ed again, and those symbols from our libs is different than libmemoryheapion.so. Looks like we've to re-build it for ourselves
Click to expand...
Click to collapse
Alright.
I really liked what Sammy did here, ship memory heap ion as a separate unit. In this way they dont have to adapt binder.
I will do the same too. I will however build on cm11 tree as I dont have cm12.1 tree. Probably you could try and let me know if it builds or not.
Is for smg316m model?
noelpalacios said:
is for smg316m model?
Click to expand...
Click to collapse
read carefully the op please
before installing this rom, make sure your device model is the same as title
Click to expand...
Click to collapse
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
tjvvuuren said:
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
Click to expand...
Click to collapse
Agree with you.
tjvvuuren said:
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
Click to expand...
Click to collapse
Actually, CM12.1 just missing ION driver, which makes camera, codecs and some thingies work. We just need that, else mobile data could be fixed later.
Related
Disclaimer
This ROM is constantly under development, and the file(s) provided are a snapshot at a particular point in time. There are no guarantees that they will work. On the other hand, it's quite possible that the file(s) here may make your phone explode, make your boy/girlfriend leave for another country, cause you immense financial loss or other horrible things. The CyanogenMod team and I are not responsible for any of it.
***THIS ROM ONLY WORKS WITH OK1 OR PREVIOUS BOOTLOADERS/MODEMS***
Reporting Bugs
This thread is for development discussion of this ROM only. If you have encountered a bug, please try to reproduce it with a CLEAN FLASH without any other apps/data (unless specifically needed to reproduce the bug).
Valid bug reports will contain the items below as a minimum:
Steps to reproduce error
Phone firmware (Baseband) - (i.e. NK2, OB7, OG5) - You can find this by going to Settings->About phone and looking for Baseband version
Version of CyanogenMod (i.e. 2015XXXX-UNOFFICIAL)
Filename / version of gapps used if the issue may be related to gapps
Logcat - CatLog is a good Android app to save logs with. You can attach to your XDA post if you desire or use a service like PasteBin.
Installation Instructions
MAKE SURE YOU ARE ON OG5 OR GREATER BASEBAND!!!!
Use TWRP!
Do a nandroid! What happens when the ROM doesn't work?? You'll be stuck, that's what!
Factory Reset if this is your first flash of CyanogenMod 13.0! (Wipe Cache/Dalvik/Data)
Install the latest nightly ROM ZIP file!
Install your favorite gapps (Slim Marshmallow Gapps is the only version I consider at this point in testing)
What Works / Doesn't
Working: Mobile Data
Working: WiFi
Working: Camera / Camcorder
Working: Calls / SMS / MMS
Working: GPS
Working: Bluetooth
Working: External SD, including formatting
Working: S-Pen
[*]Not Working: Bluetooth (Voice Calls) -- Needs more testing and more logs (fixed in 01/22/16 build)
[*]Not Working: APN Access (even if you make an Activity shortcut) (fixed in 02/04/16 build)
[*]Not Working: Exfat formatted external SD cards (fixed in 12/16/15 build)
Not Tested: Anything not mentioned above.
Found Bugs
Camera takes a long time to launch the first time each boot (before asking for location permissions, if first time)
Camcorder crashes if you use UHD 4k resolution -- 1080p works fine.
Browser crashes when downloading files -- use Chrome instead or edit Browser's permissions to allow "Storage".
Brightness gets wonky - when you let the phone dim, it may not go back to normal brightness. Press power to turn off screen and press again to fix the brightness and turn screen back on. Seems to be resolved by turning off Ambient Display / Daydream.
Automatic time zones may not work properly. You can force a timezone in Settings->Date and Time
Sometimes calls will show up as "Unknown" in the call log.
Cannot use WiFi Hotspot in 5GHz Mode
Camera freezes when you use the flash -- use alternate camera from Play Store
Download
AFH
Sources
Device Tree
Common Tree
Kernel
To compile, you will need a proper build environment. You will also need a stock OG5 or OK1 ROM to extract the proprietary files from. These builds also use the Adreno blobs from "shamu" (here). The shamu blobs Adreno blobs replace any blobs from the OG5/OK1 ROM.
THIS THREAD IS NOT FOR BUILD ENVIRONMENT OR COMPILING DISCUSSIONS
Please be aware that cm-13.0 is in a HUGE state of flux. You should NOT depend on this as your primary ROM. I cannot guarantee that everything (or anything) will work.
If you cannot post a helpful message or a detailed bug report, please do not post at all.
XDA:DevDB Information
CyanogenMod 13.0 for trltespr, ROM for the Sprint Samsung Galaxy Note 4
Contributors
nivron, drcrimzon, fattire
Source Code: https://github.com/fat-tire/android_kernel_samsung_trlte/tree/cm-13.0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: OG5 or Greater Baseband
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-12-03
Last Updated 2016-02-25
Changelogs
Below are changelogs for the different versions of the ROM available for download on AFH. Please re-read the original post, as the Working/Not Working/Known Issues section relates to the MOST RECENT version of the ROM.
06/21/16 - Probable Final Build
Upstream CM features and bug fixes
05/24/16
Includes "Gello" Browser instead of AOSP Browser
Specific ISO options in Camera are now selectable
Updated CPU/Architecture Variants for Build
Upstream CM features and bug fixes
05/18/16
Upstream CM features and bug fixes
05/05/16
Upstream CM features and bug fixes
04/12/16
Upstream CM features and bug fixes
03/21/16 - EXPERIMENTAL BUILD
Upstream CM features and bug fixes
Misc common updates to get closer to my branch
03/08/16 - EXPERIMENTAL BUILD
Upstream bug fixes and features
Updated time_daemon (fix time/date resets?) Credit: @placiano and @Pafcholini
SELINUX Enforcing
Back to Fat Tire's common repo (which I contribute to)
Charging Rapidly will now show if >= 750mA
Vibrator Intensity configurable via Settings->Display
03/01/16 - EXPERIMENTAL BUILD
Fingerprint Scanner (a bit tricky to use, but it works) - Credit: Ljzyal
Added sensorhub service - Credit: raymanfx, fattire
02/25/16 - EXPERIMENTAL BUILD
Upstream bug fixes and features
Less GPS Debugging in Logs
Removed init system prop generator
Removed trlteusc (because of above change)
Shimmed libqc-opt.so
Switched build to clang
Switched back to CM PowerHAL
Added hardware-backed graphics for Recents
Removed qcmediaplayer
Removed tcmiface
Stopped mpdecision from spamming the logs
Removed ZeroLemon fix (Battery Capacity Testing)
02/09/16
Upstream bug fixes
Fixed accidental touch input while in call
02/04/16
Upstream bug fixes
CM - Fresh installs won't default to 24-hour time or a particular date format.
CM - Live Lockscreen (currently cannot disable properly, will be fixed in future build)
APN Settings are now available/editable
Useless "Carrier Settings" option removed.
01/27/16
Bluetooth - Corrected to a more proper fix.
Upstream bug fixes
01/22/16
Upstream bug fixes
Forgot to add the ZeroLemon battery fix (AGAIN), should be back next build
01/14/16
New Camera App
Removal of Busybox in favor of Toybox (upstream AOSP change)
Upstream CM Changes
Forgot to add the ZeroLemon battery fix, should be back next build
01/04/16
Upstream CM Changes
12/16/15
Upstream CM Changes
Exfat external SD cards now are usable
12/10/15
Upstream CM Changes
ZeroLemon Fuel Gauge Fix (by TheLoneWolf20)
12/09/15
Upstream AOSP/CAF Changes
Upstream CyanogenMod Changes
Fixed Button Remapping (Recents Button Now Available for Mapping)
Re-Enabled Stylus Gestures
Added Updated Offmode Charging (Now With Icon!)
One of the upstream AOSP changes is related to DHCP on WiFi. Certain DHCP servers use non-standard UDP ports when they offer addresses. The prior build that was posted would not interpret these properly, and you would lose WiFi connectivity within a minute or so of connecting. This is now fixed.
12/03/15
Initial Version
6.0 is here!!
Thank u so much dude!!!
I'll fix in a bit but the OP says to get Slim Lollipop gapps. That was from me copying the old thread. Use the Marshmallow gapps, obviously!
Sent from my SM-N910P using Tapatalk
Thank you!
Please always review the current status of the ROM before posting any potential bugs. I'm also curious to see if our issue sending texts is fixed - the one that requires switching the network types.
Sent from my SM-N910P using Tapatalk
Superb. Great work nivs.
Getting folder not found in mega, it worked from the office about an hour ago but not anymore.
Won't download on my phone or pc link might be dead ?
Mega site is asking for decryption key ...
I'm uploading to AFH now, will update OP when complete with link.
See OP for AFH link.
Thanks ?
Does it have mobile Hotspot?
Nice work, keep it up!
I have tested and can confirm Hotspot is working.
Also can confirm Xposed Frameworks works without issue on this build as well, just make sure you get xposed-v78-sdk23-arm.
crazycori said:
Nice work, keep it up!
I have tested and can confirm Hotspot is working.
Also can confirm Xposed Frameworks works without issue on this build as well, just make sure you get xposed-v78-sdk23-arm.
Click to expand...
Click to collapse
Sms work without fix?
xyojimbox said:
Sms work without fix?
Click to expand...
Click to collapse
Yeah, I was able to send SMS and MMS without issues right after install.
drcrimzon said:
I'm uploading to AFH now, will update OP when complete with link.
See OP for AFH link.
Click to expand...
Click to collapse
Got it, it worked, thanks a billion! Loving MM
Thanks for the AFH upload! Silly MEGA.
I'm going to work on this a bit more today and try to get some of the bugs worked out. Future uploads will probably be AFH only.
drcrimzon said:
I'm uploading to AFH now, will update OP when complete with link.
See OP for AFH link.
Click to expand...
Click to collapse
Sent from my SM-N910P using Tapatalk
Does or when will this include the zero lemom mod if not does anyone know a kernel I can flash onto this that includes it? Also is this a nightly update?
Just a warning for any newb's, as it states:
•Not Working: Exfat formatted external SD cards
Anyone installs this ROM and has this type of filesystem with your EXTSdcard may very well have issues with your SD card and the ROM thinking it is corrupted and try to FIX (meaning it will format the disk). DO NOT DO THIS or you will lose your SDCard.
You may also have issues after you play with CM13 and go back to other ROMs with not being able to read the SDcard (thinking it is corrupted and not readable, this is NOT true, it is still there). I got around this by wiping device, and using CM12.1 (latest), copying all of my SDCard to my PC, then formatting the SCDard back to a universally readable filesystem.
Code:
#include <std_disclaimer.h>
/*
* 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.*/
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
What's working
Mostly everything except for those mentioned in Not working list.
What's not working
Video Recording.
Mobile data on one of the SIMs when using dual SIM.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation Instructions
If you are flashing from stock :
You need to have an SELinux enabled recovery. Use TWRP or CWM 6.0.5.1. Use the CWM which is in the downloads section below.
Download the CM11 zip and put in phone.
Reboot to recovery.
Wipe data/factory reset.
Wipe cache.
Install the CM11 zip.
(Optional)Flash Gapps (find it in downloads section).
Reboot.
If you are upgrading from CM11 (Assuming you have a SELinux enabled recovery):
Download the CM11 zip and put it in phone.
Reboot to recovery.
Simply flash the CM11, no need to wipe anything.
Reboot.
Todo
If you want to use dual SIM, open terminal emulator and execute following:
Code:
su
setprop persist.radio.multisim.config dsds
reboot
Troubleshooting
Visit this thread and post your queries there, and you may well be replied.
Download
CyanogenMod 11 - Beta 5
Gapps
Source
Device Tree
Kernel Source
Vendor Blobs
Patches (Copy Paste files)
Credits
@Unjustified Dev and @Doc_cheilvenerdi.org - For starting the CM project, initial tress and stuff.
@psych.half - For his fixes in CM10.1, ideas and ofcourse for his kernel.
@Dreamstar - For his SELinux enabled recovery, without which CM11 was not possible.
@andii_nr - For fixes.
@doesntexits and @ngoquang2708 - For their works in SGV, patches and their help.
@DigiGoon - For his highly compressed CM11 sources.
@dhinesh77 @pawitp and others - Various fixes and references have been taken from their work.
XDA:DevDB Information
CyanogenMod 11, ROM for the Samsung Galaxy Star
Contributors
corphish, Dreamstar, psych.half
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Beta
Current Beta Version: 3.0
Beta Release Date: 2016-01-24
Created 2015-12-18
Last Updated 2016-05-25
Changelog
Code:
[B]Beta 4_r2 - 9 March 2016[/B]
-It fixes all the stuff which broke in beta4, but were working in beta3.
--Fixed in call audio volume.
--Fixed WiFi tethering.
-Source underwent major cleanup again, we have eliminated most of the source patches, which are now device specific units.
--Compiled Camera, HWComposer from source.
--Detached MemoryHeapIon from binder and compiled it as separate unit.
--We now have our own RIL class. No source hacks to get RIL working.
-Fixed the weird 'No resources found' like message in recovery while flashing.
-Added WiFi direct permissions.
[B]Beta 4 - 20 February 2016[/B]
-Fixed Bluetooth.
-Fixed Bluetooth tethering.
-Fixed Offline charging.
-Fixed Dual SIM.
-Fixed data subscription (2nd SIM mobile data)
-Fixed reboot to recovery.
-Fixed more dalvik VM related memory issues (like app crashes).
-Fixed artifacts observed while screen rotation.
-Fixed black preview in Camera app, glitches in dialer app.
-Activated HW Rendering.
-Fixed audio recording.
-Audio HAL is compiled from source, is AOSP compatible, but may have limitations because all Samsung's optimizations (if any) in Audio HAL is gone.
-Added more SPRD specific OMX libs.
-Compiled various EGL related blobs from source, updated some of them.
-Compiled sensors HAL from source.
-SELinux is enabled and is now enforcing.
-Picked various critical fixes in kernel from @psych.half 's kernel.
-Switched to GCC 4.7, which is the default toolchain in CM.
-Removed various debugging in kernel.
-Implemented @psych.half's CPUFreq driver (min - 1000Mhz, max - 1200 Mhz).
-Enabled ondemand and powersave governor.
[B]Beta 3 - 24 January 2016[/B]
-Fixed Mobile Data.
-Fixed WiFi tethering.
-Fixed USB Tethering.
-Fixed audio routing to loudspeaker and headphones during call when switched to.
-Fixed various app crashes, app installation issues and memory related issues.
-Updated kernel to latest of works by @psych.half
[B]Beta 2 - 18 January 2016[/B]
-Fixed External storage (thanks to [user=220904]@andi[/user]i_nr)
-Switched to updated kernel (updated meaning updates from both stock and kernel patches) by @psych.half. This should fix the brightness bug and the battery bug that some users face. WiFi driver is also updated.
-Fixed IMEI for good. IMEI is now detected the way it is done on any android phone. No need to use any apps for that.
-Fixed USSD dialing/receiving.
-Switched to single-SIM mode (because dual SIM is broken).
-Remove loads of unneeded services.
[B]Beta 1 - 12 January 2016[/B]
-mint -> mint2g
-Fixed battery, its status and everything related to it.
-Fixed Web Browsing and related stuff.
-Updated ramdisk.
-Enabled CPU frequency scaling in kernel.
-Enabled KSM (Kernel Samepage Merging).
-Applied fixes for external storage by [user=220904]@andi[/user]i_nr (Needs confirmation)
-Initial fixes for RIL.
[B]Alpha 2 - 25 December 2015[/B]
-Fixed audio (both from speakers and headphones).
-Fixed HWComposer.
-Fixed EGL crashes and random reboots.
-Fixed camera to some extent (it starts, but cant save pics).
-Camera HAL included is new one compiled from source (BETA version, some more features than the stock HAL).
-Fixed microphone to some extent (it starts listening, but does not record anything).
-Switched to de-odexed builds.
-Updated blobs.
[B]Alpha 1 - 18 December 2015[/B]
-Initial release.
Tracker
Its hard for me to remember all the stuff I fixed in the meantime. So I will update this post (hopefully) with the stuff that has been fixed and will be available in next update.
Following things have been fixed and will be available in next update :
Re-fixed WiFi tethering.
Fixed in-call loudspeaker volume.
Support
F.A.Q
Q. I have faced some issues, which is not mentioned in the 'Not Working' list........?
A. For bug reports, the least we can expect from you is a logcat taken during the issue. Or atleast, you could tell us how and when did you face the bug, how can we reproduce the bug to fix it. Reports without any of these will be ignored.
Q. I got a status 7 error when flashing the CM11 zip...? / My device is stuck at boot logo after flashing CM11...?
A. Please use the recovery that is mentioned in the downloads section. It is recommended to use TWRP as it is known working for all.
Q. I put the ROM zip in internal memory while I was in stock ROM, but when I go to TWRP and try to flash it, the zip is not there, help!
A. TWRP uses psych.half's storage hack that he did in CM10.1. You will need to mount /data (its generally done by default), and then go to /data/media and there you can find the zip.
Q. I successfully flashed CM11, but all my data in internal memory is gone!
A. It hasn't, you can still find them in /data/media.
Q. Can you add XYZ feature to the ROM?
A. No!
Q. Can I use your ROM/any part of ROM and modify it and release it separately?
A. Yes you can. But please mention proper credits.
Q. I flashed this ROM, but I dont find any Google App, where can I find it?
A. Flash gapps mentioned in OP.
Q. Are any 3rd party utilities/kernels/themes/mods supported?
A. No, not yet. If they are supported, it will be clearly mentioned in their respective threads.
Q. If no mods are supported, how can we customize our experience?
A. This is CyanogenMod, a completely different ROM from stock. As of now, no kernels are supported, but you can customize the looks using CM11's highly customizable theme engine.
Bug reporting
How to report a bug?
First off all, check the 'not working' list and see if the bug you are facing is already mentioned or not. If it is, stop right away because the concerned people working on the ROM are aware of the issue.
If the bug/issue is not mentioned in 'not working' list, check the Frequently Asked Question (F.A.Q) and see if issue is resolved already.
If the issue you face is not in FAQ either, you would probably post a reply in this forum, and not PM anyone, about the bug.
Attach a logcat.
If not possible, mention a proper way how you encountered the bug.
Also mention any 3rd party stuff you installed. (Like mods, themes, kernels etc)
Following things WILL NOT be considered as bugs. So please do not post such bug reports, they will be ignored.
Low benchmark scores. Even if Stock results better.
Poor performance in gaming. Even if Stock results better.
High RAM usage/low RAM available.
Various kernel control app crashes.
Crashes of various UI elements when a custom theme/mod is applied.
Random reboots, and other issues caused by flashing custom kernel.
cool.
Dark Knight Begins said:
gonna try now.
Click to expand...
Click to collapse
Try and report back
And one more thing dont quote whole op
SG3 said:
Try and report back
And one more thing dont quote whole op
Click to expand...
Click to collapse
Random reboots all over.
Waiting for next update.
Waw .. great cm11
Great work bro
Waiting for cm without bug
bvrraju said:
Great work bro
Waiting for cm without bug
Click to expand...
Click to collapse
its real hard to make it without bugs.
I just want the ril fixed ..
thats all.
I know C nd D r really working hard to make it.
but we also shud knw that we own a really low end device.
Status Update
We have been working, and... :
Audio -Its fixed, both audio from speakers and headphones.
HWComposer -Its fixed too, patches to libbinder worked.
Camera - Umm, its broken. Problem is, I expected Camera to be fixed by patching libbinder, but it didn't, camera HAL was not loading at all. I eventually got the HAL to load, but it would then cause various system instabilities, so its still broken.
Microphone - Well, microphone does listen to when any respective app is started, but won't record anything (unlike last time, where it won't listen and start recording at all).
RIL - Well, that's really a tough one to fix.
Random Reboots and Freezes - Random reboots are gone, but freezes (caused due to EGL issues) still persists.
P.S : Sources are constantly being updated, patches will only be released after a next release is made. As of the current released build (Alpha 1), not much patches are used, except for those which are mentioned in the device tree.
corphish said:
We have been working, and... :
Audio -Its fixed, both audio from speakers and headphones.
HWComposer -Its fixed too, patches to libbinder worked.
Camera - Umm, its broken. Problem is, I expected Camera to be fixed by patching libbinder, but it didn't, camera HAL was not loading at all. I eventually got the HAL to load, but it would then cause various system instabilities, so its still broken.
Microphone - Well, microphone does listen to when any respective app is started, but won't record anything (unlike last time, where it won't listen and start recording at all).
RIL - Well, that's really a tough one to fix.
Random Reboots and Freezes - Random reboots are gone, but freezes (caused due to EGL issues) still persists.
P.S : Sources are constantly being updated, patches will only be released after a next release is made. As of the current released build (Alpha 1), not much patches are used, except for those which are mentioned in the device tree.
Click to expand...
Click to collapse
just the ril
Alpha 2 is up
Changelog
-Fixed audio (both from speakers and headphones).
-Fixed HWComposer.
-Fixed EGL crashes and random reboots.
-Fixed camera to some extent (it starts, but cant save pics).
-Camera HAL included is new one compiled from source (BETA version, some more features than the stock HAL).
-Fixed microphone to some extent (it starts listening, but does not record anything).
-Switched to de-odexed builds.
-Updated blobs.
Download updated in OP
This build is intended to see how our phone runs kitkat, explore kitkat's new features (if you haven't already), in a decent, less-annoying way. This is not intended for daily use.
About RIL?
That's all I get. We have fixed baseband too, but not included in this release.
Perks of the new camera HAL?
Well, camera might not be fully functional, but that is not because of the new HAL being used, things are same even with stock HAL. This HAL works perfectly with CM10.1. Only bug is the camera preview format has weird colours (just like what we have in recovery, blues look orange and all that). Anyway,
cool!
Great Surprise On Christmas!!
Downloading!!
Good.Now Build CM12
Pratik Mandi said:
Good.Now Build CM12
Click to expand...
Click to collapse
its really hard work.
let them make stable kk 1st.
Dark Knight Begins said:
its really hard work.
let them make stable kk 1st.
Click to expand...
Click to collapse
Oh!!
psych.half said:
Ah GT-S5283 is qcom, I just saw it in download when searching opensource.samsung.
mfserial looks like code for AT/UART for baseband.
Samsung has it disabled cause it wrote their own mfserial.
Yup I checked the RIL implementation in stock. I havent had time to fully reverse eng the stuffs. But heres what I found.
Check the last blocks of code in stock 'init.sp8810.rc' , you see the #datarouter. Thats where the RIL is.
The DR,SMD,DTT,BCS,mobex daemon are responsible for parsing the raw UART, setting up CSC and sending data to framework.
So first try adding those and see.
And if that doesnt work they are using broadcasts to these apps, so you might need to hack on these.
com.sec.app.RilErrorNotifier
com.android.samsungtest.RilDTTCommand
Click to expand...
Click to collapse
Well, adding those surely did 'something' to RIL. Well things went worse, but atleast now we know they are related to RIL.
Like, initially, sim0 radio was off, but sim1 radio was out of service, now both are off.
Anyways, I was comparing the radio logs of stock and cm11, let's take IMEI for instance, and see how it looks like :
Stock:
Code:
D/[B]RILC[/B] ( 102): [0021]< GET_IMEI [COLOR="SeaGreen"]{35**************}[/COLOR]
D/RIL ( 102): put Channel ID '4'
I/RILC ( 102): -->CommandThread [1020] free one command
D/RILJ ( 823): [rild1] [0021]< GET_IMEI
And in CM11:
Code:
D/use-Rlog/RLOG-[B]RILC[/B]( 92): [0023]< GET_IMEI [COLOR="Red"]fails by E_GENERIC_FAILURE[/COLOR]
Any ideas?
We are using SamsungBCMRIL (which is the extension of AOSP RIL itself) in the framework side. PS : That RIL class is fix for dialing, manual network mode etc, basic stuff like signals and imei should work with default setup.
And we are using all the ril blobs from stock ROM
Also, the have you checked the following scripts?
ext_data.sh
ext_kill.sh
They override props by getting original props using getprop, but when I try getprop in terminal emulator, nothing is returned
Edit : @psych.half
After a bit more debugging, I found the reason why IMEI detection fails, radio fails to turn on etc.
it is due to the fact that, respective AT Commands are failing, not all commands fail, but critical commands fail :crying:
Here's how AT commands are handled in stock:
Code:
D/AT ( 102): Channel4: AT> AT+CGSN
[COLOR="SeaGreen"]D/AT ( 102): Channel4: AT< 35**************
D/AT ( 102): Channel4: AT< OK
D/RILC ( 102): [0021]< GET_IMEI {35**************}[/COLOR]
And in CM11 :
Code:
D/use-Rlog/RLOG-AT( 92): Channel4: AT> AT+CGSN
[COLOR="Red"]D/use-Rlog/RLOG-AT( 91): Channel2: AT< ERROR[/COLOR]
So any ideas? How ATs are parsed?
All we can do is in framework level, and add/remove blobs. We can't do anything with ril blobs.
corphish said:
Well, adding those surely did 'something' to RIL. Well things went worse, but atleast now we know they are related to RIL.
Like, initially, sim0 radio was off, but sim1 radio was out of service, now both are off.
Anyways, I was comparing the radio logs of stock and cm11, let's take IMEI for instance, and see how it looks like :
Stock:
Code:
D/[B]RILC[/B] ( 102): [0021]< GET_IMEI [COLOR="SeaGreen"]{35**************}[/COLOR]
D/RIL ( 102): put Channel ID '4'
I/RILC ( 102): -->CommandThread [1020] free one command
D/RILJ ( 823): [rild1] [0021]< GET_IMEI
And in CM11:
Code:
D/use-Rlog/RLOG-[B]RILC[/B]( 92): [0023]< GET_IMEI [COLOR="Red"]fails by E_GENERIC_FAILURE[/COLOR]
Any ideas?
We are using SamsungBCMRIL (which is the extension of AOSP RIL itself) in the framework side. PS : That RIL class is fix for dialing, manual network mode etc, basic stuff like signals and imei should work with default setup.
And we are using all the ril blobs from stock ROM
Also, the have you checked the following scripts?
ext_data.sh
ext_kill.sh
They override props by getting original props using getprop, but when I try getprop in terminal emulator, nothing is returned
Edit : @psych.half
After a bit more debugging, I found the reason why IMEI detection fails, radio fails to turn on etc.
it is due to the fact that, respective AT Commands are failing, not all commands fail, but critical commands fail :crying:
Here's how AT commands are handled in stock:
Code:
D/AT ( 102): Channel4: AT> AT+CGSN
[COLOR="SeaGreen"]D/AT ( 102): Channel4: AT< 35**************
D/AT ( 102): Channel4: AT< OK
D/RILC ( 102): [0021]< GET_IMEI {35**************}[/COLOR]
And in CM11 :
Code:
D/use-Rlog/RLOG-AT( 92): Channel4: AT> AT+CGSN
[COLOR="Red"]D/use-Rlog/RLOG-AT( 91): Channel2: AT< ERROR[/COLOR]
So any ideas? How ATs are parsed?
All we can do is in framework level, and add/remove blobs. We can't do anything with ril blobs.
Click to expand...
Click to collapse
On closer inscpection the datarouter is for another functionality. You know in stock ROM we can use select which SIM to use mobile data from.
Afaik, BCMRil is for Broadcom ones Spreadtrum doesnt seem to need a seperate RIL class
So maybe we need to take libreference-ril.so and libril_sprd.so from another sprd which doesnt depend on samsung's stuff. Samsung made a lot of modification on libril on this one.. Heck there isnt even telephony framework, ril is handled by its own apps..
Update @corphish
after some log digging, AT commamds are handled by at_distributor.. but it only setups socket... and executes "am broadcast com.sec.atd.request_reconnect"..
Yup its handled by samsung's own app
psych.half said:
On closer inscpection the datarouter is for another functionality. You know in stock ROM we can use select which SIM to use mobile data from.
Afaik, BCMRil is for Broadcom ones Spreadtrum doesnt seem to need a seperate RIL class
So maybe we need to take libreference-ril.so and libril_sprd.so from another sprd which doesnt depend on samsung's stuff. Samsung made a lot of modification on libril on this one.. Heck there isnt even telephony framework, ril is handled by its own apps..
Update @corphish
after some log digging, AT commamds are handled by at_distributor.. but it only setups socket... and executes "am broadcast com.sec.atd.request_reconnect"..
Yup its handled by samsung's own app
Click to expand...
Click to collapse
Alright!
RIL is connected though. Never had that problem of it failing to connect.
So what's the next thing we should do? Try adding apps from stock?
The Prehistory of UltimateROM
About a month ago I decided to set out to improve the performance of my phone with a more optimized build. I had already begun building OmniROM 5.1.1 with a some set of optimizations based on the work of OptiPop Team, and shortly after some the major issues on Marshmallow on our devices were resolved, this idea to create an ultimatively optimized AOSP-based ROM has born.
Why Should You Use UltimateROM? What makes it different?!
Honestly, I don't necessarily care, how many users or downloads my ROM has. Most importantly, and what I do care about is people liking and enjoying their phone; if you try UltimateROM and you like it, great! I'm glad you enjoy it. If you don't, maybe leave some feedback on how I can improve it, and go try something else in the meantime. If you'd like to know, what I've done that makes this ROM unique, here is a list:
Highly optimized. similar to Linaro(and in many ways, better than), build, resulting in a smoother Android
Compeletely developed in the open, everything I do is right on my GitHub for anybody to use and improve upon.
A unique kernel which attempts to balance features, stability, and of course, performance
Almost the sources, excluding apps, the SystemUI and some more, are based on CyanogenMod ones, which means there are more fixes and support for our legacy devices (even though CyanogenMod itself doesn't really support any devices like our, anyway google doesn't even do that minimal support as CM Team does)
Disabled SELinux. Looking backward on how many issues SELinux was causing and still causing for people that use it on MM, it seems to me a ridiculuos how google promotes and implements it everywhere, without any proof of improving anything rather than making worse.
Current Information
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Please also note that currently I don't test installation with the Gapps. So far installation is only tested as dualboot ROM - though, the uploaded build is an usual one, - please let me know if the uploaded build has issues with booting, even though normally this should not happen.
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
Formatting SDcard as adoptable storage will screw it up (don't format / encrypt)
MTP bug with doubled folders in sdcard root folder
ROM features:
Dark Marshmallow Theme
long volume press to skip track
PA Pie control
SlimRecents / improved AOSP recents
Re-added task manager
Navigation Bar
System UI tuner
expanded desktop
storages are swapped by default
extended reboot menu
customizable button backlight settings
Viper4Android FX
superuser embedded
Download
UltimateROM
Installation
Before installation, make sure that you have enough free space on partition /system. AT LEAST 540 Mb is required for this build if installing WITHOUT any Gapps. If you don't have enough space, follow repartition manual. (at your own responsibility for any kind of possible damage. Be sure to measure twice and cut once!). There is a CWM ReParted zip that was tested by @Culateralligator.
wipe cache
make sure you're using TWRP 2.8.6.0. All the below is only tested on this recovery. Philz is not supported by this ROM and not planned to in the near future. Note that TWRP from the linked topic requires preinstalled chrono kernel.
install ROM first
install latest chrono kernel
install gapps (optional), if you do so, make sure you are not running of space on /system ( about GApps )
Sources:
https://github.com/UltimateROM/android_manifest
Thank Yous
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.0.0.0! Also thanks for helping me implementing some features to this ROM.
JDCTeam, BenzoROM - thanks for great cherry-picks!
MWisBest - this project was heavily inspired by his FML (Fork My Life) ROM
OptiPop - an initial set of optimizations that the currently used by me is based upon
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks
@shaqman89 - for providing the build server
@S.AMU - for providing FTP server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome, SergeyL, JDCTeam, OptiPop Team, BenzoROM, OmniROM, AOKP, CyanogenMod, SlimRoms, AOSPA, Temasek.
Source Code: https://github.com/UltimateROM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.1.2 ROM or up + kitkat-compatible recovery
Based On: AOSP, CyanogenMod
Version Information
Status: Stable
Created 2016-03-20
Last Updated 2018-08-20
Changelogs
Changelog
20.08.2018 - build #13
sources update
switch to opensource sensors
switch more device libs to open source base
unified codina / janice build
02.12.2017 - build #12
fixed native moving apps to SDcard
APP2SD and similar apps now should work correctly *
fixed second incoming call not to crash rild (not tested, needs confirmation), thanks to @SergeyL
small RIL fixes
NOTE: installation method was updated. Flash latest chrono kernel build after this ROM install.
02.04.2017 - build #11
kernel updated to r5.0
sdcard mount fixes
integrated an unofficial build of the Xposed framework
ported the utility mtools *
* for repairing the broken sdcard label you can move the file /system/bin/mtools to /system/xbin folder, then type in the terminal emulator mlabel/i]. It will show the current sdcard label and will prompt to type the new one.
27.02.2017 - build #10
updated sources to 6.0.1_r78
added an initial support of the PowerHAL *
ported some changes from Resurrection Remix 7.1.1 build (thanks to SergeyL for patches)
updated kernel to r5.x.x (mostly updates from google android-3.4 kernel)
changed recovery to TWRP 3.x.x
unstable MySQL optimizations are reverted
changed buttons backlight mode - backlight is only enabled when buttons are pressed
experimental change scheduling policy of the surfaceflinger to FIFO
maybe, something yet
* at the moment there's no support of changing the PowerHAL profiles from the Settings, however, you can change profile in a file /system/etc/init.d/999powerhal
Proceed installation of this build only with data wipe.
20.09.2016 - build #9
Fully switched to an opensource RIL! Many thanks to Meticulus for finding the working RIL sources and fixing it, also I'd like to thank millosr and mickybart from Nozomi (Xperia S) forum for fixing the crash when performing a call and providing patches for debugging the proprietary libril!
More libs now are built from source - credit goes to Meticulus
Added sdcardfs support (requires at least build r4.8 of Chrono Kernel)
Added home key press to accept the incoming call and power key press to end the active call features from CyanogenMod - thanks to SergeyL for helping with finding those patches
Changed LowMemoryKiller tunables to the more aggressive + increased zram size to 400Mb - multitasking should be (hopefully) better
Changed Dynamic governor tunables to be more aggressive
Various minor fixes that improves the stability of ROM
We've also finally got rid of all shim (i.e. interposed) libraries that were needed in order for some features (camera, GPS etc) to work
30.05.2016 - build #8
updated wifi autoconnection fix (fixed the battery stats)
fixed SystemUI FC when switching USB mode via status bar notification
fixed GSM / WCDMA preferred / WCDMA Only switching
fixed soft reboot when switching 2G/3G with an enabled mobile data
added Pie Control from Paranoid Android
added SlimRecents
updated AOSP recents implementation ("clear all" button doesn't properly work, so don't enable it or use SlimRecents)
added task manager
allowed disabling of brighness slider disabling
revert AOSP camera to 5.1.1 (fixed the photo cropping issue)
added FAT images mounting via UMS support (use
sys.config.opt_sd0device=full_path_to_the_image.img build.prop setting to override the device mounted as Sdcard0 or sys.config.opt_sd1device for Sdcard1)
26.05.2016 - build #7
Work around wifi autoconnection issue
Fixed video encoding issue by some apps (instagram video upload etc) - thanks to Meticulus for the original patch
Added LockClock back
Added option to show the weather in the status bar
Various small improvements, tweaks etc.
23.05.2016 - build #6
More ROM modules compiled with GCC instead of Clang (GCC supports more optimizations)
Almost ROM modules compiled with Link Time Optimizations
Enabled graphite optimizations for more ROM modules
Added autovectorization optimization on per-modular base
More modules built in ARM mode
Allowed disabling of FC notification
Added time-context custom header images feature
Added customization of the carrier label
Added SystemUI tuner
Added display autorotation setting
19.05.2016 - build #5
updated kernel to r4.4.1
added and enabled by default UMS (USB Mass Storage) mode
re-added some default AOSP optimizations
added navigation bar
added battery level icon customization setting
added long back press to kill app feature
remove 3 secs delay in Superuser before to give the app permissions
added feature of disabling mediascaner at boot
added Sqilte performance improvements
disabled an unnecessary debug
another fixes / improvements
fixed graphical glitches in some apps caused by new UMP lib
resized bootanication (thanks Lemu @ 4pda.ru)
fixed init.d scripts
added aggresive Dynamic governor settings
13.05.2016 - build #4
cleaned up the default google optimizations, removed unnecessary flags
disabled forcible ARM mode optimization - until I revisit this again
added performance settings from OmniROM
added CM Filemanager
added a few more opensource code to libUMP, replacing calls to old library
fxed up an inadeqate CPU time consumption caused by logd process
6.05.2016 - build #3
updated sources to 6.0.1_r30
kernel update to r4.3.1
switched to GCC 5.3 toolchain by UBER
enabled graphite, fast math, loop nest, unsafe loop and some more optimizations
entire build is compiled in ARM mode
switched to opensource RIL libraries (based on CyanogenMod repos)
UMP (Unified Memory Provider) library now is mostly opensource - based upon CM sources
Attempt to fix storage permission issues in some apps such as browser - not tested
fixup for RIL java code - thanks to @SergeyL
disabled scrolling cache
SQLite code optimizations
Reduced various delays
many other fixes and improvements - thanks to SergeyL for patches
20.03.2016 - build #2
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
20.03.2016 - build #1
initial release
Miscellaneous
reserved
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
2.V4A needs to works with busybox, lol...
But ROM works smooth
fim5646 said:
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
Click to expand...
Click to collapse
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
2.V4A needs to works with busybox, lol...
Click to expand...
Click to collapse
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
ChronoMonochrome said:
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
Click to expand...
Click to collapse
Yeah,these 4 fonts only support Janpanese,Korean,Simplified Chinese and Traditional Chinese,(lastest outdated AOSP 6.0 has same problem...）Maybe OmniROM has different font files
ChronoMonochrome said:
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
Click to expand...
Click to collapse
Yeah....
Is there any way to fix sdcard problem?
And thanks for this awesome rom.
Fake2Dead said:
Is there any way to fix sdcard problem?
Click to expand...
Click to collapse
What problem exactly?
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Culateralligator said:
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Click to expand...
Click to collapse
GApps aren't personally tested by me, but I guess, you'll need those provided by SergeyL else keyboard will crash.
ChronoMonochrome said:
What problem exactly?
Click to expand...
Click to collapse
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Fake2Dead said:
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Click to expand...
Click to collapse
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
ChronoMonochrome said:
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
Click to expand...
Click to collapse
Thank you so much for help. I tried to format from windows(exfat) and it worked!
Edit: Don't try to format sdcard as fat32 it didn't worked on me
Pastorious said:
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
Click to expand...
Click to collapse
I can confirm Web Browser is unstable.
I haven't those WiFi problems yet, but I'm testing for little time.
What do you mean with smallest GApps?
I've tried no repartition + SergeyL GApps and I get ERROR CODE 70 -not enough system space-.
Culateralligator said:
I
What do you mean with smallest GApps?
Click to expand...
Click to collapse
I found somewhere gapps ~45MB, still too big for install, i have no idea how install Play shop
New build is 20.03.2016(#2) UP!
Changelog
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler to free up some space
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
Might fix GApps not being fitted on /system issue in the future, but I'll need a volunteer to test the new partition scheme. If anyone knows how to modify CWM repartition scheme zip and create a new one with ~700-750Mb on /system, it would be even much great, because right now I have absolutely no time for this.
Enjoy!
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Succesfully installed gapps removed printspooler webbrowser gallery calendar clock and 1 more thing and i found 48 mb gapps
Culateralligator said:
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Click to expand...
Click to collapse
Indeed, it seems that I have misapplied one fix to the vold binary. Does this issue also appear on CM13?
P.s. it's possible that vold from CM13 will also work, because UltimateROM use same sources as CM. Can anyone try replacing /system/bin/vold and check if it helps?
What's up guys, even though this Nexus 4 is 4 years old, (pun not intended XD) it's still holding up strong and in time for some Nougat treatment. [emoji14]
Note: Most of the components are working and I believe that it is enough for daily tasks. However, YOU see whether it fits your needs or not.
Working:
- Audio
- Wi-Fi
- Bluetooth
- RIL
- H/W Acceleration
- USB
- GPS
- NFC
- Sensors
Semi-Working:
- Camera (Video recording stutters sometimes with some apps)
Not Working:
How to Flash:
1. Download Zip
2. Flash zip
3. Flash GApps
4. Wipe Data (If coming from anything other than 7.0)
4. Flash SuperSU (Optionnal, Uses systemless as a root method)
5. Profit
Note: You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings.
Download:
AOSP 7.0 download folder
Mirror
Quanta:
Quanta V19 Test
GApps:
OpenGApps
Banks GApps
SuperSU: SuperSU Stable
Sources:
Device Tree
Kernel Source
Changelog, other stuff
Code:
V10 (18/12/16):
- Updated to Android 7.1.1
- Patched kernel with the latest security fixes.
V9: (14/10/16)
- Video recording on Camera2 partially fixed (Video shakes sometimes)
- Fixed stack trace for native processes
- Updated to October's Security patches
- Misc fixes
V8: (18/09/16)
- Kernel patched accordingly to September security fixes (Patches all Quadrooter exploits up to now)
- Fixed Torch
V7: (11/09/16)
- Updated to September security fixes (For real this time)
- Enabled H/W encoding for video recording
- Re-enabled navigation bar tweaks and night mode in SystemUI
- Fixed Google Play Services FC's using OpenGApps (For real also)
- Add possibility to change WebView provider
V6: (09/09/16)
- Updated to September security patches
- Fixed freezing while watching YouTube
- Attempt to enable LTE
- Hidden misc battery drain as it causes some misinterpretations
V5: (05/09/16)
- Enabled Doze for real this time
- Reverted a change that may have broke Camera
V4: (02/09/16)
- Fixed H/W video decoding for the most part
- Kernel: SDCard FS enabled
- Attempt to fix permissions for GApps
- Enabled Navigation Bar tweaks and Night mode in SystemUI Tuner.
V3: (30/08/16)
- Fixed Sensors
- Semi-Fixed camera
- Fixed MPDecision
- Enabled Doze
- Used Flo's developper preview N GPU drivers
V2: (28/08/16)
- Fixed audio
- Fixed GPS
- Fixed data connectivity
- Disabled the power toggle widget which caused Settings to crash on every boot
V1 (26/08/16):
- Initial release
Here's a video showing how to install the ROM. (Thanks @Swapnil Soni)
Here's another one with a little overview of it. (Thanks @DaKoin)
Build instructions:
Since some of you guys asked me how to build from scratch, I will give a walkthrough of what I mostly did.
Note that this is in no way a walkthrough in how to compile (there are several guides for that on XDA) but more a guide
on how I did my setup so you can replicate the AOSP builds on your device.
Here's what I did:
1. Download the latest AOSP revision for android-7.1 which is r6 at the time of this writing (replace with whatever required branch necessary)
Code:
repo init -u https://android.googlesource.com/platform/manifest -b refs/tags/android-7.1.1_r6
repo sync
2. Download the kernel source used for the build:
Code:
git clone https://github.com/zaclimon/android_kernel_google_msm -b mako_nougat
3. Once both sources has been downloaded, compile the kernel. Note that AOSP do have a kernel toolchain that you can use to compile
Code:
export CROSS_COMPILE "/path/to/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-"
make mako_defconfig
make -j$(grep -c processor /proc/cpuinfo)
4. Copy the arch/arm/boot/zImage file to the Android source into device/lge/mako-kernel
Note: You must create the said directories if they don't exist. You also must rename the file to kernel after copy.
5. Go back to the AOSP source, and download/update/replace the following repositories for each component (relative path):
Code:
device/lge:
git clone https://github.com/zaclimon/android_device_lge_mako mako
hardware/qcom:
git clone https://github.com/zaclimon/android_hardware_qcom_audio audio
git clone https://github.com/zaclimon/android_hardware_qcom_display display
git clone https://github.com/zaclimon/android_hardware_qcom_gps gps
git clone https://github.com/zaclimon/android_hardware_qcom_media media
vendor:
git clone https://github.com/zaclimon/android_vendor_lge lge
6. Apply the following patches to each of their respective repositories:
Code:
bionic:
https://github.com/LineageOS/android_bionic/commit/81af26a3a033723fb34ddf280e33a9d4a6ce82c4.patch
frameworks/base:
https://gist.github.com/zaclimon/bb39d7f5059b63e3add3b5cad15e87db
https://android-review.googlesource.com/#/c/147266/
system/sepolicy:
https://github.com/LineageOS/android_system_sepolicy/commit/10dd0402ab62aa1a6416d7ea549a6a3eea1c6ae4.patch
7. Increase RAM usage for Jack (Only if you have 6/8GB of RAM in your system)
Code:
export ANDROID_JACK_VM_ARGS="-Xmx4g -Dfile.encoding=UTF-8 -XX:+TieredCompilation"
8. Once all the patches have been applied, we can now proceed to compile the system.
Code:
. build/envsetup.sh && lunch aosp_mako-userdebug
make -j$(grep -c processor /proc/cpuinfo) otapackage
9. The build should be in out/target/product/mako
10. Flash and enjoy!!
You're the king, buddy! ?
P.
[sntfrmnxs⁴]
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
nitin.chobhe said:
first
Nitin
Click to expand...
Click to collapse
Ha ha ! Almost.
Sent from my Nexus 4 using Tapatalk
You're great!!
nitin.chobhe said:
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
Click to expand...
Click to collapse
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Merci infiniement !!!
Just downloaded, and works, I think we need to changes the permission so that google play service not crashing
Its people like you who make this world a better place, thank you very much!
zaclimon said:
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Click to expand...
Click to collapse
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
funthomasz said:
Its people like you who make this world a better place, thank you very much!
Click to expand...
Click to collapse
nitin.chobhe said:
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
Click to expand...
Click to collapse
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
I am coming from the fake Nexus Rom aka I do not have a custom bootloader yet. What bootloader is the best to go with?
Could someone write me a quick instruction how to get started with my situation. I bet there are a lot coming from fake nexus.
Thanks for the great work!!
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
aabuk said:
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
Click to expand...
Click to collapse
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
zaclimon said:
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
Click to expand...
Click to collapse
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
zaclimon said:
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
Click to expand...
Click to collapse
hahaha, okie, atleast i got some space to look at dem kernelzz, thanks for echo
cqloveqc said:
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
Click to expand...
Click to collapse
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Gu$houn* said:
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Click to expand...
Click to collapse
Yes, I've tried that by using a es file manager, but if we can make the 240 default, we don't need to make change anymore
Damn I'm late to the party, downloading now !
And thanks a ton @zaclimon for keeping mako alive, you're the man !
@zaclimon nice work.. keep it clean please
This is only for SM-P605 (lt03lte)! Even loading an custom recovery will irreversible trigger Knox to 0x1!
LineageOS/CyanogenMod is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS/CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (GApps). LineageOS/CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
How to flash:
-Be sure you are on 5.1.1 Bootloader and Modem (Flash 5.1.1 firmware via Odin) !
-Flash TWRP (version 3.0.0-0 or newer recommended)
-Make Nandroid backup (optional)
-Wipe > Advanced Wipe > select data, system, ART/Dalvik Cache, Cache, Internal Storage > Swipe
-Install > select Lineage14.1 Zip > Swipe, optional: flash GAPPS, SU Addon (before rebooting!)
-Reboot
Please read full OP before posting or flashing anything. Please don't report any bugs, if you use Xposed, any mod or modified the system.
Please report no issues, if you
using the official builds (or others than mine)
flashed Xposed
or modified the system
What is working
Everything
No major issues/bugs
Download
Other Builds
GAPPS
Notes:
- If SIM is not detected/RIL not working, flash 5.1.1 firmware again!
- Enable root: flash SU Addon, Settings > About tablet > tap 5x at build number. Settings > Developer options > Root Access
- just ignore E: Unknown Command errors in TWRP
- Flash GAPPS before reboot first time after flash!
- If using MTP/PTP shows no files, please tap one more at transfer files in notifications
- If something not listed ist not working, please test it also with SELinux permissive (setenforce 0 via Terminal Emulator/ADB Shell or use SELinuxModeChanger)
Changelog:
20210320: Synced sources
20200913: Synced sources, added midi support, disabled 5 GHz AP
20200318: Synced sources
20200124: Synced sources, a few kernel changes
20191101: Synced sources, small changes
20190801: Synced sources, slightly higher volume on speaker and Headset, small changes
20190303: Synced sources,smaller changes
20181226: Synced sources, changed SEPolicy, updated HID driver, small changes
Older
--Lineage--
20181217: Synced sources
20181029: Synced sources, small changes
20180816: Synced sources
20180618: Synced sources (Security Patch Level 2018-05-05), switched to 2048 heap/hwui memory map, sepolicy
20180524: Security Patch Level 2018-05-05
20180424: Synced sources
20180326: Synced sources, small things
20180307: Synced sources, kernel security patches, a few things
20180124: Synced sources, removed libsecril and legacy sd symlink, kernel updates
20171205: Synced sources, RIL changes, implemented stylus gestures
20171026: Synced sources, fixed magnet cover, switched to source built CAF ril, some kernel changes
20170925: Synced sources, fixed camera, kernel updates, sepolicy updates
20170829: Synced sources, switched to msm8974-common kernel (with some changes for our device), CLOCK_BOOTTIME_ALARM support, some smaller changes (Note: Please flash boot.img from post #643 to fix camera!)
20170803: Fixed MpDecision
20170802: Synced sources, only activate button light if they are pressed, added missing low latency record (-->for Skype etc.), updated init and sepolicy, some small improvements and changes
20170723: Synced sources, grant proper unix permissions for netmgrd and rmt_storage, updated sepolicy and init, smaller changes
20170703: Synced sources, removed buggy timekeep (fixes wifi problem), RIL updated (fixes Autotimezone), disabled live display per default, some minor changes
20170626: Synced sources, switched to Sony Timekeep (experimental), added SamsungDoze, enabled sdcardfs, enabled CIFS/NFS, mac access fixed, some kernel changes
20170614: Synced sources (Android 7.1.2_r17), quiet "KERNEL IS NOT SEANDROID ENFORCING"
20170604: Synced sources, fixed a bunch of kernel leaks
20170518: Synced sources, Only expose su when daemon is running
20170507: Synced sources (android-7.1.2_r8, Jelly...), correct keylayout config, enabled volume wake settings, added missing liblight defines, fixed prefered network setting, fixed rotation problem
20170422: Synced sources (Android 7.1.2), F2FS support, changed keylayout again, some kernel changes, IR changes from Lineage, dex preopt (not prerooted, flash SU Addon)
20170320: Synced sources, prerooted again, enabled Miracast/WiDi overlay, added missing SEPolicys for s-pen third party apps
20170301 #2 : Fixed tethering/hotspot (not prerooted, flash SU Addon)
20170301 #1: Synced sources, improved macloader related stuff (not prerooted, flash SU Addon)
20170203: Synces sources, fixed telehony fc after Nandroid restore, enhanced off charging mode
20170126: Synces sources, enabled Blur, a few kernel changes
20170114: Synced sources (Android 7.1.1_r9)
20170104: Synced sources, removed some deprecated stuff (dhcpcd entries, legacy symlinks)
20161231: Synced sources, Bluetooth disabled per default, unknown sources enabled per default
20161227: Synced sources, first Lineage build
--CyanogenMod--
20161215: Synced sources (Android 7.1.1_r6), disable notification LED for now (until I find a better solution), switched to common IR/lights HAL, last build from CyanogenMod Sources
20161207: Synced sources (Android 7.1.1), reduced power consumption, add missing SELinux rule
20161202: Synced sources, fixed magnetic cover, fixed VOIP mic
20161128: Synced sources, fixed off charging Mode, changed keylayout: Menu button: menu, longpressmenu: splitscreen view, doubletaphome: recent Apps
20161115: Synced sources, fixed camcorder, mapped longpressmenu as menu
20161110: Synced sources, Setup Wizard fixed, updated SEPolicy
20163010: first xda release, sync with cm 14.1 sources
Credit: LineageOS/CyanogenMod Team, Maintainer and Valera1978
Kevin F. Haggerty, Paul Keith
Sources:
Device
Kernel
Kernel since 20170829
Vendor
XDA:DevDB Information
Unofficial LineageOS (CyanogenMod) 14.1 for SM-P605, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)
Contributors
davidmueller13
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 5.1.1 bootloader and modem
Based On: LineageOS
Version Information
Status: Stable
Created 2016-10-30
Last Updated 2020-09-17
FAQ - Frequently Asked Questions
FAQ
Please read before posting anything!
Will this work/can you make it work on P600/P601?
Short answer: No! Only SM-P605 is supported.
But there are other projects for your device. For P600 (n1awifi) you can just download the latest official nightly.
Can you add xy feature?
It is and will stay a build straight from LineageOS sources, not a fork, so no. And also afaik there is no feature request way for LineageOS atm.
My SIM card is not recognized. What can I do?
As RIL blobs are from 5.1.1 firmware package, you need to be on modem from 5.1.1 firmware. The easiest way: just get an firmware package from Sammobile, Updato... and flash it via Odin. If it's still not working after that, do the same again (sometimes this is necessary).
Something is not working (correctly) / I found a bug? What should I do?
Make sure there are no potential courses for that issue like installed Xposed or system modifications. Also look, if it's listed in the OP or somebody already mentioned it. If not, just post about it and all information about it you have (circumstances, steps to reproduce it...).
Of course only for my builds you found in that thread, not for other/offical builds.
Amazing work!
Running your 10-27 build since yesterday night and working great so far on my T-Mobile P-607T.
Only thing noticed so far are that can not change the battery style and display battery % on the statusbar.
That's purely cosmetic, the build is fast and stable. Weather location service works, have not tested GPS
nav yet.
Setup wizard worked for me on the 10-27 build.
Will download and test this build.
Thanks for keep supporting the Note 10.1 2014.
Thanks
Thanks for making this sweet build. Everything works well on my P607-TM except for the fact that it thinks the SIM card is not inserted. I came from a aosp 6.0.1 build and did an advanced format of everything except for external SD card. I tried formatting a few times and reinstalling a few times with no luck.
iandy1 said:
Only thing noticed so far are that can not change the battery style and display battery % on the statusbar..
Click to expand...
Click to collapse
Yes, some stuff for that is not fully ported and implemented yet.
iandy1 said:
Setup wizard worked for me on the 10-27 build.
Click to expand...
Click to collapse
Thats the SetupWizard App, that comes with GAPPS. I had to remove the CyanogenMod SetupWizard, because of a FC while Wifi Setup. (I think, it uses the deprecated SETUP_WIFI_NETWORK.)
temijun said:
except for the fact that it thinks the SIM card is not inserted. I came from a aosp 6.0.1 build and did an advanced format of everything except for external SD card. I tried formatting a few times and reinstalling a few times with no luck.
Click to expand...
Click to collapse
Make sure, you are on the latest modem (e.g. by flashing latest firmware).
Also an LogCat would be useful (How to do this).
Yeah you're absolutely right about the radio firmware once I upgraded baseband from P607TUVUBOI2 to P607TUVSBPH1 and reflash everything works as expected! thanks again for this awesome rom!
davidmueller13 said:
Yes, some stuff for that is not fully ported and implemented yet.
Thats the SetupWizard App, that comes with GAPPS. I had to remove the CyanogenMod SetupWizard, because of a FC while Wifi Setup. (I think, it uses the deprecated SETUP_WIFI_NETWORK.)
Make sure, you are on the latest modem (e.g. by flashing latest firmware).
Also an LogCat would be useful (How to do this).
Click to expand...
Click to collapse
firmware is very smooth, but
- Sometimes crash settings app
- Does not work the microphone during a call through Skype
Does this version fix the bug that I saw with rotation?
Edit. Isn't a bug. Settings disabled rotation for certain orientation by default. Need fix by changing in settings.
it cant read my sim
Does it support exfat or ntfs file system with write rights?
great rom..sometimes a little bit stuttering, but finally great to have 7.1
how do you use your stylus? do u have a special app for that?
Thank you again
ameenkhaled said:
it cant read my sim
Click to expand...
Click to collapse
I flashed back to the default TMobile P607TUVUBOI2 firmware and then did an internal update to P607TUVSBPH1 which updated the radio baseband. This solved the missing SIM issue for me.
Hooray! One more of my devices could hop on CM14.x! I think imma start building myself starting next month...
Are MTP and ADB connections working too? Those aren't present in official CM13 nightlies and are the most irritating I found in them.
Sent from Google Nexus 6P @ CM13
AndyYan said:
Are MTP and ADB connections working too? Those aren't present in official CM13 nightlies and are the most irritating I found in them.
Click to expand...
Click to collapse
Yes, they work.
In the CM13 Nighlys the kernel driver for MTP is failing. If you want to fix/add some things to your CM13 Builds:
Fix camera failing while SELinux Enforcing: http://review.cyanogenmod.org/#/c/165576/
Fix MTP-driver: https://github.com/davidmueller13/k...mmit/4785cabeb9047e8d9e5e19e3f3f5c4f4e3a59ceb
enable adoptable storage: https://github.com/davidmueller13/d...mmit/5ed5e71080c366e3e35ee23f032b86da74db2dba
And if you want to build CM14, it's important that you know that i use the common graphic binaries:
https://github.com/TheMuppets/proprietary_vendor_qcom_binaries
temijun said:
I flashed back to the default TMobile P607TUVUBOI2 firmware and then did an internal update to P607TUVSBPH1 which updated the radio baseband. This solved the missing SIM issue for me.
Click to expand...
Click to collapse
Does PH1 update the baseband? I extracted modem.bin from PH1 tar and flashed, and later flashed the whole PH1 package from Odin, but baseband stays at OI2...
Sent from Google Nexus 6P @ CM13
---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ----------
davidmueller13 said:
Yes, they work.
In the CM13 Nighlys the kernel driver for MTP is failing. If you want to fix/add some things to your CM13 Builds:
Fix camera failing while SELinux Enforcing: http://review.cyanogenmod.org/#/c/165576/
Fix MTP-driver: https://github.com/davidmueller13/k...mmit/4785cabeb9047e8d9e5e19e3f3f5c4f4e3a59ceb
enable adoptable storage: https://github.com/davidmueller13/d...mmit/5ed5e71080c366e3e35ee23f032b86da74db2dba
And if you want to build CM14, it's important that you know that i use the common graphic binaries:
https://github.com/TheMuppets/proprietary_vendor_qcom_binaries
Click to expand...
Click to collapse
Do the patches works for TWRP too? Last I recalled TWRP also doesn't have ADB/MTP, if those could fix it I might consider syncing TWRP and do a patched build...
Sent from Google Nexus 6P @ CM13
AndyYan said:
Do the patches works for TWRP too? Last I recalled TWRP also doesn't have ADB/MTP, if those could fix it I might consider syncing TWRP and do a patched build...
Click to expand...
Click to collapse
I think, it's the same issue. If you want to build TWRP you should use a OmniROM source tree (i change the device tree for that a bit :https://github.com/davidmueller13/device_lt03lte_nougat/tree/omni ).
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Cirno5 said:
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Yes, that is normal. I don't know how to fix it myself without gravitybox. That option won't work because 7.0/7.1 has no xposed support yet.
Sent from my LG-H850 using XDA-Developers mobile app
Cirno5 said:
Is it common that the menu button calls up the recent apps?
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Manually edit the .kl file in /system/usr/keylayout (can't remember which, but should be obvious).
Sent from Google Nexus 6P @ CM13
Cirno5 said:
I tried editing it in options but no matter if short press or long press are changed to any option available it still uses recent apps.
Click to expand...
Click to collapse
Change in sec_touchscreen.kl in system/usr/keylayout "APP_SWITCH VIRTUAL" to "MENU VIRTUAL".
I think, i will change it in the next build and set the app switch to "long press home" and disable "double tap home".
Good news for camcorder: I fixed recording, but we have to wait for some changes in CM14.1. But at least it works for our device finally in CM13.