[ROM][WiP][4.2.2] CM-10.1 | OpenSEMC - RC2

Search This thread

RaymanFX

Inactive Recognized Developer
Jan 8, 2011
1,122
16,501
28
Hannover


Android 4.2.2 (CM-10.1) for the Xperia S


cid.png



Code:
#include <std_disclaimer.h> 
/*  
 * Your warranty is now void.  
 *  
 * I am not responsible for bricked devices, dead pets, thermonuclear  
 * war, or the current economic crisis caused by you following these  
 * directions. YOU are choosing to make these modificiations, and  
 * if you point your finger at me for messing up your device, We will  
 * laugh at you.  Loud and hard.
 */


CHANGELOG:
GitHub


BUGS:
Generic: http://code.google.com/p/opensemc/issues/list
Version-specific: http://code.google.com/p/opensemc/wiki/Versions


DOWNLOADS:
Google Project Home


SOURCE:
GitHub


THE TEAM:
Current Team Status


MAINTAINERS:
Your maintainers for the Xperia S (Nozomi) are Arakmar and RaymanFX


CREDITS:
FXP for the CM10 initial sources!
CyanogenMod for CyanogenMod!
My team members for doing awesome work!
 
Last edited:

RaymanFX

Inactive Recognized Developer
Jan 8, 2011
1,122
16,501
28
Hannover
Information

Versioning:

As of BETA2, two versions are distributed, the 'CAF' version and the 'Makozomi' version.

CAF (Code Aurora Forum):
This version uses the CAF display driver, which in general has more fixes and the newest qcom stuff over the AOSP one.

+ MPD composition and overlay drawing should be improved using this display driver
+ Code widely used on non-nexus devices
- HDMI is broken


Makozomi (Mako+Nozomi):
This version uses the AOSP (Mako/Nexus4) display driver, which in general is not up-to-date with the newest qcom code, but proven to be stable over time.

+ HDMI works flawlessly
+ Pure Mako/Nexus4 drivers
- MDP composition and overall drawing performance could be a tad worse compared to CAF


The choice is yours.
If you rely on HDMI, Makozomi will serve you well.
 
Last edited:

m1st3r1

Senior Member
Aug 15, 2010
890
279
Jakarta
Great news, just waiting for the hardware acceleration and it's all good for me.

Thanks..

Sent from my LT26i using Tapatalk 2
 

Ben36

Senior Member
Jun 8, 2012
8,254
2,868
Just wipe everything in cwm and flash the zip file?

Sent from my Jellybean Xperia S :D

---------- Post added at 09:30 PM ---------- Previous post was at 08:50 PM ----------

Lol. Don't thank me, it was a question :p

Sent from my Jellybean Xperia S :D
 

Felimenta97

Senior Member
Aug 5, 2011
7,863
2,305
26
Ribeirão Preto
realy nice group here
with lots of interesting info @ development
i think everybody should see this

http://www.facebook.com/groups/437393782991982/472271862837507/?notif_t=group_activity

In fact, not everyone should see this. I created the group, and it is meant only for a few testers and the devs working on it.

WARNING: Don't even ask to join because I won't accept anyone anymore.

This action isn't meant to be rude, but to keep control of whoever is in there.

Sent from my LT26i using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 437


    Android 4.2.2 (CM-10.1) for the Xperia S


    cid.png



    Code:
    #include <std_disclaimer.h> 
    /*  
     * Your warranty is now void.  
     *  
     * I am not responsible for bricked devices, dead pets, thermonuclear  
     * war, or the current economic crisis caused by you following these  
     * directions. YOU are choosing to make these modificiations, and  
     * if you point your finger at me for messing up your device, We will  
     * laugh at you.  Loud and hard.
     */


    CHANGELOG:
    GitHub


    BUGS:
    Generic: http://code.google.com/p/opensemc/issues/list
    Version-specific: http://code.google.com/p/opensemc/wiki/Versions


    DOWNLOADS:
    Google Project Home


    SOURCE:
    GitHub


    THE TEAM:
    Current Team Status


    MAINTAINERS:
    Your maintainers for the Xperia S (Nozomi) are Arakmar and RaymanFX


    CREDITS:
    FXP for the CM10 initial sources!
    CyanogenMod for CyanogenMod!
    My team members for doing awesome work!
    188
    Downloads

    ==========
    Version info
    ==========


    DEPRECATED. Please refer to the Google Project Home instead!

    Google Apps: Goo.im


    WIPE DATA IF COMING FROM OS < 4.2.1!
    138
    98
    As I understand, the kernel in all JB versions is 3.4, but there are minor changes in them between the versions.
    Wait, did I miss something completely important and we're getting 4.3?

    Also, icymi, Sony's announced an update for some 2012 phones. Some phones that currently have 4.1 may make a jump to 4.3. I'm just seeing if they're man enough to give us 4.3... (even though 4.1 is broken)

    I'll save you before someone rants you for rejecting the S3 chipset being abandoned by Qualcomm :)
    [Edit - damnit, Novastylez was faster]

    Here's the thing. I talked to some Sony internals and responsibles, as well as a russian developer, who is somehow involved with Sony and is a good friend of mine (I'll not name him here directly for some reasons), he also was the person he received the first leaked Jellybean builds back in January.
    Long story short, the outcome of this was basically that Sony did some outstanding work on the 3.4 kernel. Instead of just bringing it up-to-date with Jellybean user space drivers (HALs), they updated it to the new CAF API (MR1 respective) and wrapped the Jellybean display HAL around the MR1 API, which was never meant to run on the S3 chipset. So their kernel basically has >4.1 and beyond compatible video drivers, it's just missing fences (that's also why LeTama was able to bring the Sony kernel up-to-date for 4.2 userspace drivers by just adding fences, we discussed this aswell).

    ==> outcome: I dare to say Sony could basically provide 4.2 or eve 4.3 builds for our device pretty easily.
    But I guess they just dropped support for our device (except for bugfix 4.1 releases) because it's and oldie and they have way too much newer devices they have to support.

    So what I will be doing the next few days is trying to upgrade my display-legacy HAL to the new MR1 API from CAF, but leave out fences so we don't get into trouble there, leaving the kernel drivers mostly untouched (except for the synchronization driver frameworks).


    And yes - the first 4.3 build will arrive soon, I am expecting it to work better than current 4.2 builds actually :)
    WiFi tethering is working flawlessly (been using it the last few days without pause), there are close to no display related bugs, battery life feels at least as well as stock, it might only lack some smoothness compared to chocolate versions. But it is stable. No crashes whatsoever. Oh, and HDMI should also work flawlessly here. I am working on improving the legacy drivers, it's just a matter of time until they work at least as well as chocolate drivers.
    94
    Information

    Versioning:

    As of BETA2, two versions are distributed, the 'CAF' version and the 'Makozomi' version.

    CAF (Code Aurora Forum):
    This version uses the CAF display driver, which in general has more fixes and the newest qcom stuff over the AOSP one.

    + MPD composition and overlay drawing should be improved using this display driver
    + Code widely used on non-nexus devices
    - HDMI is broken


    Makozomi (Mako+Nozomi):
    This version uses the AOSP (Mako/Nexus4) display driver, which in general is not up-to-date with the newest qcom code, but proven to be stable over time.

    + HDMI works flawlessly
    + Pure Mako/Nexus4 drivers
    - MDP composition and overall drawing performance could be a tad worse compared to CAF


    The choice is yours.
    If you rely on HDMI, Makozomi will serve you well.