[ROM] [CM 12.0/12.1] uCyan for Xperia S [DISCONTINUED]

mickybart · Feb 10, 2015

uCyan 12.x for Xperia S

The purpose of this rom is to provide a rom based on Cyanogenmod 12 (uCyan means "unofficial CyanogenMod").

I will not create nightly build (except if someone else can provide an infrastructure to do it).
The target is to follow the future M release cycle of CyanogenMod Team.

To add extra custom to the ROM you can use Xposed that is stable enough.

Changelog (features, issues, etc)
CM 12 is on heavy development and it seems that dirty flash cause some issues. I encourage you to clean flash every time for the moment.

uCyan 12.1
b05

CyanogenMod 12.1 (sync 2015-07-09)
FMRadio: bug fix (crash when back button pressed on the headphones activity)
Dex2oat: permit dex2oat to run more than 6 minutes (fix installation timeout issues like with Facebook)
Audio Effect: replace AudioFX by ViPER4Android with NEON_HQ mode, QCOM Acoustic Echo Cancellation (aec will be used by default on VoIP)
Audio: review code, enable QCOM Fluence mode and enable double mic (endfire)

If you like ViPER4Android, please go to thanks developers of ViPER4Android and not me. You will find more detail on the section "Good to know

".

b04

CyanogenMod 12.1 (sync 2015-06-12)
Thermal protection: Migration to thermanager with a configuration file located at /system/etc/thermanager.xml. (fix device reboot when too hot). For those who overclock the CPU, please read Overclocking section.

Previous versions

uCyan 12.0
b05

CyanogenMod 12.0 (sync 2015-04-26)
kernel: Add wake gesture (thanks to @ztc1997)
kernel: Touchscreen can power off/on itself based on the proximity sensor state (only in standby mode)
Wake Up: New application embedded to control Wake Gesture and Kernel configuration (can be disabled if you prefer to use manual method and Xposed Module).
Screen will not be turned on if you plug/unplug USB cable by default
GPU: fix some slow down and corruptions (that was visible into Hangout and some launchers)

Previous versions

b04

CyanogenMod 12.0 (sync 2015-04-10)
kernel : the same one than uCyan-12.1 b01
Radio : FM radio is back
Fast Charge : Can be enabled into Settings/Battery/Menu. Will be automatically disabled after a reboot.

b03

Brightness: Screen brightness level like stock ROM (als/curve parameters). Lowest brightness can be set to 2% (5/255). Boot brightness is set to 30%
USB Fast Charge supported (thanks to @ztc1997) use at your own risk
SD card: Read ahead set to 2048kb by default
Zram: switch to lz4 compressor/decompressor (thanks to @ztc1997) + Fix random hard reboot when changing zram disk size on developer GUI.
GPU: Dynamic clocking supported. 2d will run at 96Mhz and 3d at 177Mhz by default. GPU governor is set to ondemand by default. The max frequency depend of the kernel used
Overclocking: OC Ultra kernel is set to start at 1.51Ghz for the CPU. You are free to overclock up to 2.05Ghz.
Hotplug CPU: disabled on all OC kernel. It is safe to start it with OC kernel but you shouldn't do it on OC Ultra.
cm: code update from 2015-02-25

b02

boot: fix boot.img flash with fastboot
kernel: fix dt2w + add color calibration (thanks to @ztc1997 )
cm hardware: userspace color calibration implemented and available under Settings/Display
cm: code update from 2015-02-16
brightness: lowest value can be set to 17 (6.5%)

b01

Initial release with stuffs that come from nAOSProm and CyanogenMod
kernel: based on billchen1977 and nAOSProm (overclocking kernels are available too)
lightbar: Adaptive support added (integration is done on Settings/Buttons)
filesystem: f2fs/ext4 support for /data, /cache, /sdcard
Settings: Developer GUI permit to manage "Low Memory Killer", "zram", "Ambient brightness" and "Overclocking kernel"
Custom parameters are not lost after a dirty flash (zram, minfree, oc, doze etc)
Tap to Wake: Double Tap to Wake implemented with CM hardware (integration is done on Settings/Display)
RIL: update for Nozomi (conference call supported)
FmRadio : NOT working yet

Download
Release available under :
https://mega.co.nz/#F!60cHlYRb!wdYGx9SkRt2S8b3LtHhgeg
http://ovh.to/DXgAKGj

For recovery CWM or TWRP, you can use the FOTAkernel : eg for TWRP 2.8.0.1 or 2.8.4.1 and more

Good to know
Take a look at the end of the developer options GUI

Overclocking
Overclocked kernel are tested on my own device BUT I won't be responsible for any damages on yours
Please don't enable mpdecision on OC kernel except if you know what you are doing.

Thermanager
By default if the device is too hot it will reduce the screen brightness and CPU clock. When the device will be cool enough it will restore brightness and CPU clock but at 1.5Ghz only.
If you want to force thermanager to restore the clock to a specific value defined by an external overclocking tool, you can edit /system/etc/thermanager.xml.

ViPER4Android
All credits go to ViPER520 and the amazing works.
You should read detail and go to thanks developers.
xda : http://forum.xda-developers.com/showthread.php?t=2191223
website: http://vipersaudio.com/blog/?page_id=31

Howto flash
Read and thanks UlvarinPL

Source
uCyan 12.0
uCyan 12.1

Release
Kernel: 3.4.0
Android: 5.0.2_r1 (cm 12.0), 5.1.1_r6 (cm 12.1)

Thanks
- billchen1977
- ViPER4Android Team
- Cyanogenmod Team
- FXP Team
- TWRP Team
- All the community around Android

FAQ

Facebook installation failed: (not necessary since uCyan-12.1 b05)
Option 1:
adb shell
su
setprop dalvik.vm.dex2oat-flags "--no-watch-dog"
Install Facebook with Google Play or other
setprop dalvik.vm.dex2oat-flags ""

Option 2 (can be needed if you wipe dalvik-cache and you need to compile Facebook during the boot):
edit /system/build.prop and add:
dalvik.vm.dex2oat-flags=--no-watch-dog
reboot the device
install Facebook

mickybart · Feb 10, 2015

As you know CM 12 is in an heavy development stage so don't report bug that are due to CM itself on this thread except if you need to be sure that this is not due to Nozomi integration stuff.

I have not the infrastructure to release a nightly build but the target is to follow M release cycle. the M1 should arrive in a near future. Thanks a lot to CyanogenMod Team for the amazing works.

darknessmc · Feb 10, 2015

I'll try it now
Thanks. Good to see CM12 finally

m1st3r1 · Feb 10, 2015

this is awesome. those new themes for cm themes are looking good. cant wait to try.

mickybart said:
Wipe cache/dalvik (wipe data if you come from another rom)

if coming from pure aosp/naosp rom must wipe data too?

thanks @mickybart

mickybart · Feb 10, 2015

m1st3r1 said:
this is awesome. those new themes for cm themes are looking good. cant wait to try.

if coming from pure aosp/naosp rom must wipe data too?

thanks @mickybart

Not tested but that should work fine.

UlvarinPL · Feb 10, 2015

Hello guys,
Can someone point differences between uCyan and nAOSP??
I know that you Mickeybart are developer of these two. And I dont even know how to thank you for that!!

Are they both on similar stability and development stage?
Is the only diffrence a CM theme engine or they are much more "underhood" changes?
Wich one of them is better for everyday usage? Im on nAOSP b16 and it works almost perfect for me after shutting down tapping to wake up.
I'd love to give it a try

tori_mc · Feb 10, 2015

UlvarinPL said:
Hello guys,
Can someone point diffrences between uCyan and nAOSP??
I know that you Mickeybart are developer of these two. And I dont even know how to thank you for that!!

Are they both on similar stability and development stage?
Is the only diffrence a CM theme engine or they are much more "underhood" changes?
Wich one of them is better for everyday usage? Im on nAOSP b16 and it works almost perfect for me after shutting down tapping to wake up.
I'd love to give it a try

+1

dobi235 · Feb 10, 2015

UlvarinPL said:
Hello guys,
Can someone point differences between uCyan and nAOSP??
I know that you Mickeybart are developer of these two. And I dont even know how to thank you for that!!

Are they both on similar stability and development stage?
Is the only diffrence a CM theme engine or they are much more "underhood" changes?
Wich one of them is better for everyday usage? Im on nAOSP b16 and it works almost perfect for me after shutting down tapping to wake up.
I'd love to give it a try

http://lmgtfy.com/?q=aosp
http://lmgtfy.com/?q=cyanogenmod

you can find by yourself

UlvarinPL · Feb 10, 2015

dobi235 said:
http://lmgtfy.com/?q=aosp
http://lmgtfy.com/?q=cyanogenmod

you can find by yourself

OH Thank you mister clever!!!!
Im not a total idiot and u can belive me or not but i did read that already....

I wanted to know what are underhood changes and in wich development stage are both roms compared to themselves ofc!!
naosp is on b16 after many many bugfixes, and for example i want to know are these bugfixes included in CM12, or is it a step back in development due to changing subject to CM12 funcionality...
Mb if you know that u can share it with us instead of pointing out google, since we all saw how clever you already are

CM = aosp + cm team tweaks, naosp = aosp + mickeybart teweaks, im very curious what are differences between these.
Also this CM12 for xperia S = Aosp + CM + Mickeybart tweaks, i still think my questions are much more important than knowing that cm is a bloatware free alternative of android for legacy and also new phones (wich is all u can read about cm on their site...)

nisu4717 · Feb 10, 2015

After fixing up radio.
R u going to submit the code to cm for review. And get official support??

dobi235 · Feb 10, 2015

UlvarinPL said:
OH Thank you mister clever!!!!
Im not a total idiot and u can belive me or not but i did read that already....

I wanted to know what are underhood changes and in wich development stage are both roms compared to themselves ofc!!
naosp is on b16 after many many bugfixes, and for example i want to know are these bugfixes included in CM12, or is it a step back in development due to changing subject to CM12 funcionality...
Mb if you know that u can share it with us instead of pointing out google, since we all saw how clever you already are

CM = aosp + cm team tweaks, naosp = aosp + mickeybart teweaks, im very curious what are differences between these.
Also this CM12 for xperia S = Aosp + CM + Mickeybart tweaks, i still think my questions are much more important than knowing that cm is a bloatware free alternative of android for legacy and also new phones (wich is all u can read about cm on their site...)

AOSP is pure android

CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors. (from official CM page)

mickybart · Feb 10, 2015

UlvarinPL said:
Hello guys,
Can someone point differences between uCyan and nAOSP??
I know that you Mickeybart are developer of these two. And I dont even know how to thank you for that!!

Are they both on similar stability and development stage?
Is the only diffrence a CM theme engine or they are much more "underhood" changes?
Wich one of them is better for everyday usage? Im on nAOSP b16 and it works almost perfect for me after shutting down tapping to wake up.
I'd love to give it a try

tori_mc said:
+1

Can someone point differences between uCyan and nAOSP?

nAOSProm is based on AOSP code source with "small" patches to add some features and Nozomi stuffs. Patches are not to heavy to guarantee stability and easy maintenance with AOSP upstream.
uCyan is based on CyanogenMod (based itself on AOSP). there is a lot of patches and change at every level (core, applications, hardware support ...)

Are they both on similar stability and development stage?

For stability absolutely not.
CyanogenMod 12 is on an heavy development and for early adopter. That will surely change after CM-12 M1 release. But everybody is free to use it early and to help CynogenMod to fix bugs. After few day of utilization (more as a developer than final user), it's working fine (some bugs like profile crash for example, on contact and dialer you lost the last position on the contact window if you background the application and foreground it after, etc).

nAOSProm can be considered stable (this doesn't means free of bug and we are all waiting Android 5.1

)

Is the only diffrence a CM theme engine or they are much more "underhood" changes?

There is a lot more like weather integration, quick settings configuration, physical buttons management, profile usage, performance (cpu, governor, io), applications like Eleven (music replacement), Browser, SMS/Mms with Material look and feel, ProGuard etc

Wich one of them is better for everyday usage?

uCyan miss FmRadio support because I have more works than expected on this part. There is a lot of change on the bluetooth part. Except that every tweak made on nAOSProm are ported to uCyan (some one comes from CyanogenMod, some other from me) so you will have the same level of integration.

I have tried to test everything that I can and for me uCyan can be used everyday. In the same time the b17 of nAOSProm will arrive with some stuff that I learn and did with uCyan. Try and answer by yourself

mickybart · Feb 10, 2015

nisu4717 said:
After fixing up radio.
R u going to submit the code to cm for review. And get official support??

I think that bluetooth a2dp is not working. If someone can test it to report ? if it is working that should be maybe possible to submit a review (I think that screen flickering need to be fixed prior).

hYpercrites · Feb 10, 2015

uhm, do i need a clean flash if i come from CM11?

patrol-cz · Feb 10, 2015

Looks great, many thanks!
The dialer app is crashing:

Code:

I/DialpadFragment( 5164): Displaying normal Dialer UI.
I/DialpadFragment( 5164): Displaying normal Dialer UI.
W/ResourcesManager( 5164): Asset path '/system/framework/com.google.android.media.effects.jar' does not exist or contains no resources.
D/OpenGLRenderer( 5164): Render dirty regions requested: true
D/Atlas   ( 5164): Validating map...
D/PhoneApp( 1077): getPhone phoneId:0
E/SQLiteLog( 4800): (1) no such column: account_type
E/DatabaseUtils( 4800): Writing exception to parcel
E/DatabaseUtils( 4800): android.database.sqlite.SQLiteException: no such column: account_type (code 1): , while compiling: SELECT account_type, account_name FROM view_contacts WHERE (_id=?)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:891)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:502)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1316)
E/DatabaseUtils( 4800):         at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:400)
E/DatabaseUtils( 4800):         at com.android.providers.contacts.ContactsProvider2.query(ContactsProvider2.java:6678)
E/DatabaseUtils( 4800):         at com.android.providers.contacts.ContactsProvider2.queryLocal(ContactsProvider2.java:6628)
E/DatabaseUtils( 4800):         at com.android.providers.contacts.ContactsProvider2.query(ContactsProvider2.java:5223)
E/DatabaseUtils( 4800):         at android.content.ContentProvider$Transport.query(ContentProvider.java:213)
E/DatabaseUtils( 4800):         at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/DatabaseUtils( 4800):         at android.os.Binder.execTransact(Binder.java:446)
E/AndroidRuntime( 5164): FATAL EXCEPTION: CallLogAdapter.QueryThread
E/AndroidRuntime( 5164): Process: com.android.dialer, PID: 5164
E/AndroidRuntime( 5164): android.database.sqlite.SQLiteException: no such column: account_type (code 1): , while compiling: SELECT account_type, account_name FROM view_contacts WHERE (_id=?)
E/AndroidRuntime( 5164):        at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:181)
E/AndroidRuntime( 5164):        at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
E/AndroidRuntime( 5164):        at android.content.ContentProviderProxy.query(ContentProviderNative.java:420)
E/AndroidRuntime( 5164):        at android.content.ContentResolver.query(ContentResolver.java:478)
E/AndroidRuntime( 5164):        at android.content.ContentResolver.query(ContentResolver.java:422)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.ContactInfoHelper.lookupContactFromUri(ContactInfoHelper.java:189)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.ContactInfoHelper.queryContactInfoForPhoneNumber(ContactInfoHelper.java:251)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.ContactInfoHelper.lookupNumber(ContactInfoHelper.java:92)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.CallLogAdapterHelper.queryContactInfo(CallLogAdapterHelper.java:336)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.CallLogAdapterHelper.access$100(CallLogAdapterHelper.java:38)
E/AndroidRuntime( 5164):        at com.android.dialer.calllog.CallLogAdapterHelper$QueryThread.run(CallLogAdapterHelper.java:152)
W/ActivityManager(  608):   Force finishing activity com.android.dialer/.DialtactsActivity

It's a serious problem, because I need to use the device as a phone

.
Pavel

UlvarinPL · Feb 10, 2015

thank you Mickybart!!
Hmm i think im gonna give a try to uCyan a little bit later after it will be as u said M1 or at least even with nAOSP

.
till then cant wait for naosp b17!!

PS. Personally in the spotify and podcasts era i do not miss fmradio at all

Thank you for great work!
Honestly you should start accepting donations, im sure a lot of us would love to donate u at least a nice beer to enjoy

m1st3r1 · Feb 10, 2015

patrol-cz said:
Looks great, many thanks!
The dialer app is crashing:

It's a serious problem, because I need to use the device as a phone .
Pavel

clean flash or dirty flash? i dirty flash it, and has dialer app crashing too. plus with messaging (mms.apk) crashing.. i wonder if it happen to with clean flash.

thanks

moe18 · Feb 10, 2015

m1st3r1 said:
clean flash or dirty flash? i dirty flash it, and has dialer app crashing too. plus with messaging (mms.apk) crashing.. i wonder if it happen to with clean flash.

thanks

i did a clean flash and dialer, is lag as in all lollipop builds, but is working fine.. .. just called my bro

for test

m1st3r1 · Feb 10, 2015

moe18 said:
i did a clean flash and dialer, is lag as in all lollipop builds, but is working fine.. .. just called my bro for test

what gapps do you use? and do you have problem with messaging app? or do you use hangout? i use exdialer and it's working fine though, at least to make a call, havent tried for receiving.

i use (latest) pa gapps nano. other things seem working just fine though.

thanks

moe18 · Feb 11, 2015

m1st3r1 said:
what gapps do you use? and do you have problem with messaging app? or do you use hangout? i use exdialer and it's working fine though, at least to make a call, havent tried for receiving.

i use (latest) pa gapps nano. other things seem working just fine though.

thanks

im using PA gapps nano beta 5, using stock cm messagin app, and can recieve call too......(stock phone and dialer app)

[ROM] [CM 12.0/12.1] uCyan for Xperia S [DISCONTINUED]

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts