[ROM][UNOFFICIAL][5.1.1][BETA-3][SM-G313H/HZ/ML]CyanogenMod 12.1 for Samsung Galaxy V

[doesntexits]

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.

#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

• 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:

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

 

[doesntexits]

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

 

[doesntexits]

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

 

[MohdRosdi]

Finally, I've waiting for a long time for this cm 12.:good:

 

[Nikit]

Cool nice to see more spredtrum device get cm
great work
btw is audio working ?

 

[doesntexits]

Cool nice to see more spredtrum device get cm
great work
btw is audio working ?

Yes, it's working
Remove audio CFLAGS from BoardConfig.mk and use audio_policy.default, it still working. IDK why

 

[doesntexits]

@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.

 

[corphish]

@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.

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.

 

[doesntexits]

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.

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:

a1@desktop:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj

Camera HAL:

_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:

a1@desktop:~/Downloads$ strings libbinder.so | grep Ion
a1@desktop:~/Downloads$

Nothing shown. IDK why. Maybe Sammy has applied ION driver inside those HAL blobs :/

 

[corphish]

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:

a1@desktop:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj

But... with libbinder:

a1@desktop:~/Downloads$ strings libbinder.so | grep Ion
a1@desktop:~/Downloads$

Nothing shown. IDK why

Alright..recursive grep through lib folder

cd system/lib
grep -R Ion

You mean symbolic link?

$(shell ln [-OPTIONS] <source> <target>)

 

[doesntexits]

Alright..recursive grep through lib folder

cd system/lib
grep -R Ion

Haha, we got our result. MemoryHeapIon is being used as seperate lib.

a1@desktop:~/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
a1@desktop:~/Downloads/lib$

I thought it must be in binder, but we've all wrong

 

[corphish]

Haha, we got our result. MemoryHeapIon is being used as seperate lib.

a1@desktop:~/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
a1@desktop:~/Downloads/lib$

I thought it must be in binder, but we've all wrong

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.

 

[doesntexits]

Get me that blob plox..and see my earlier post..I did not see your query abt webview

Change it to .so

 

[doesntexits]

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.

But...

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...

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

 

[corphish]

But...

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...

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

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.

 

[noelpalacios]

Is for smg316m model?

 

[doesntexits]

is for smg316m model?

read carefully the op please

before installing this rom, make sure your device model is the same as title

 

[tjvvuuren]

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.

 

[MohdRosdi]

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.

Agree with you.

 

[doesntexits]

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.

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.