yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Star] corphish:
#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

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:

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
[Samsung Galaxy Star] corphish:
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.
[Samsung Galaxy Star] BatDroid:
cool.
[Samsung Galaxy Star] SG3:
Try and report back

And one more thing dont quote whole op
[Samsung Galaxy Star] BatDroid:
Random reboots all over.

Waiting for next update.
[Samsung Galaxy Star] andii_nr:
Waw .. great cm11 :D
[Samsung Galaxy Star] bvrraju:
Great work bro

Waiting for cm without bug
[Samsung Galaxy Star] BatDroid:
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.
[Samsung Galaxy Star] corphish:
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.
[Samsung Galaxy Star] BatDroid:
just the ril
[Samsung Galaxy Star] corphish:
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,
[Samsung Galaxy Star] Pratik Mandi:
Great Surprise On Christmas!!

Downloading!!
[Samsung Galaxy Star] Pratik Mandi:
Good.Now Build CM12
[Samsung Galaxy Star] BatDroid:
its really hard work.

let them make stable kk 1st.
[Samsung Galaxy Star] Pratik Mandi:
Oh!!
[Samsung Galaxy Star] corphish:
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:

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:

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

Edit : [MENTION=5925208]psych.half[/MENTION]

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:

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 :

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.
[Samsung Galaxy Star] psych.half:
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 [MENTION=5822936]corphish[/MENTION]

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
[Samsung Galaxy Star] corphish:
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?
[Android Q&A, Help & Troubleshooting] Flay_:
Hello I was directed to post here to resolve this problem.

A little while ago I flashed a bootlogo into my tablet along with a 6.0 M bootanimation. I used it fine for a few weeks and then I decided to change it. I explored on xda a little bit and found an interesting and better bootanimation and downloaded it and flashed it. Now everytime I boot my phone there is only the bootlogo until the device starts. There is no longer any animation. I tried wiping/flashing different bootanimations/logos but its stuck on the same thing. I need help

:confused:
[AT&T Samsung Galaxy S6] archie87:
I've tested this twice with factory resets to make sure I'm not crazy. Disabling all the bloatware via package disabler causes my phone to lag. Most noticeably when swiping on the home screen and opening apps. Skipping package disabler and disabling what I can within the application manager results in more fluidity. Naturally this means I can't disable all that I would like, but I'll take that over the lag. Has anyone else experienced this? Thanks.
[AT&T Samsung Galaxy S6] jondroid2:
My phone was lagging then I used package disabler and it still lags :( but battery life seems slightly better now!

Sent from my SAMSUNG-SM-G890A
[AT&T Samsung Galaxy S6] archie87:
Have you tried clearing the cache?

My phone is a lot smoother now that I stopped using package disabler.
[AT&T Samsung Galaxy S6] Cusa:
Yup, I've stopped using package disabler because my phone was unusable and laggy af.
[AT&T Samsung Galaxy S6] jondroid2:
Yes I've cleared cache in recovery a couple times. Still testing all the apps in disabler to see the differences.

Sent from my SAMSUNG-SM-G890A
[AT&T Samsung Galaxy S6] ProStreetCamaro:
Call me crazy but my S6 active feels smoother after disabling it today. I thought maybe it was just my imagination.
[AT&T Samsung Galaxy S6] archie87:
Glad to know it wasn't just me. I've since uninstalled it.
[AT&T Samsung Galaxy S6] byl233:
Thanks for your tip. I'm searching for the way to get rid of lagging on my active today. I do feel the phone get smoother after I uninstall this app. Do you guys think this app is spying on us:confused:? I saw it gets a lot of permissions in the device manager...
[Nexus 6P Q&A, Help & Troubleshooting] TeeX2.0:
Anyone else having issues getting notifications?

I'm having different issues with various apps, so I'm wondering if it's a Marshmallow optimization issue.

After the most recent update, Snapchat won't give sound notifications (but the light will still blink and the vibrate will still work).

My email app (fastmail) has the opposite issue, where the sound will work but the light won't blink.

Anyone else see issues like this?
[Nexus 6P Q&A, Help & Troubleshooting] PaulQ602:
I was using a custom ringtone that didn't work until I gave the phone app STORAGE permission. You could try giving the offending apps STORAGE permission and see if that helps. Kind of a long shot because my other apps are working right and I didn't actively go and change the storage permission.
[Nexus 6P Q&A, Help & Troubleshooting] TeeX2.0:
thanks for the suggestion, but didn't work for me. I even changed the phone's permission for storage just in case. But the other apps already have permissions granted, so not sure what would break on those two apps.

Especially confusing that they are opposite problems, sound on one, the light on the other one.
[Nexus 6P Q&A, Help & Troubleshooting] TeeX2.0:
UPDATE: I just installed Lightflow Legacy and controlled all my notification sounds and lights that way :)
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] rkshah:
help me guys i have installed carbon rom first then omni rom for my device but it stuck in boot loop so i installed teamwin recovery and now its showing no os

plzzz help!!!!!!!!!!!!!!!!!!!!!
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] v7:
Hello,

Thanks for using XDA Assist.

Moving your thread to Galaxy S Advance Q&A,Help and Troubleshooting.

Try to flash a ROM from TWRP.

___

v7

XDA Assist
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] DaksAnkit:
no os , han

:good:

, well try flashing rom zip through recovery and if that doesn`t work i think you have to flash stock rom through ODIN , but be careful and do read the instructions from forum first , i am positive there is some forum here for stock flashing on s advance . :good: good luck
[General Questions and Answers] GranPaSmurf:
My phone is Sprint Galaxy Mega, SPH-L600. Extra, 60 GB external card.

How do I un-install TWRP as recovery? I think Philz would work better for me.

When I reached the step of installing the Custom ROM, TWRP reported 'failure'

I wondered if there is a need for extra memory, mine showed mostly full in the device, so I slashed through uninstalling and getting rid of everything I could reproduce afterward and now have about half of device memory unused. I retried the installation of custom CYM ROM, and again it failed.

I'm not understanding why and what to do next. I appreciate any advice.
[Oppo R7 Plus] coled3:
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
[Oppo R7 Plus] Nexus5-32GB:
Excellent! I am going to test it right now and will report!!!!

Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?

Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom :(
[Oppo R7 Plus] maniac103:
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] Nexus5-32GB:
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.

EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.

CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
[Oppo R7 Plus] shadow25:
Very exited, good job ;)
[Oppo R7 Plus] coled3:
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
[Oppo R7 Plus] Nexus5-32GB:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.

When doing factory reset in CM12.1 recovery I get this:

-- Wiping data...

Formating /data...

E:Failed to start /data/data/org.cyanogenmod.audiofx

Formating /cache...

:confused:
[Oppo R7 Plus] coled3:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
[Oppo R7 Plus] coled3:
check out my post after this (well before now) :D
[Oppo R7 Plus] Nexus5-32GB:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it :rolleyes:
[Oppo R7 Plus] coled3:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
[Oppo R7 Plus] Nexus5-32GB:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...

About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
[Oppo R7 Plus] coled3:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
[Oppo R7 Plus] Nexus5-32GB:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...

EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research :D
[Oppo R7 Plus] coled3:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
[Oppo R7 Plus] Nexus5-32GB:
:D am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
[Oppo R7 Plus] thepinkowl84:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
[Oppo R7 Plus] maniac103:
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.

I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?

Gesendet von meinem R7plusf mit Tapatalk
[Oppo R7 Plus] Nexus5-32GB:
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://xdaforums.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.

No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
[Oppo R7 Plus] manjake:
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!
[Oppo R7 Plus] Heroeagle:
hii all ,,

i have aproblem with all version of cm 13 after 0508 , all version after this date cannot pass oppo logo , then reboot , os cannot boot anymore

any helo !!!
[Oppo R7 Plus] lenrek:
You installed any theme? If what you see boot pattern like: Oppo Logo -> CM Logo -> Android Upgrade -> CM Logo (again!!!). Don't do anything, wait for another 10 more mins (at least).