{Z}[DEVELOPMENT] - CM10.1 - Android 4.2.2 - FreeXperia Project

Search This thread

dron39

Senior Member
Sep 20, 2009
723
112

Kali-

Inactive Recognized Developer
Apr 11, 2010
1,633
2,593
Roma
a newer build is in queue, should be out later today after the nightlies task

i have removed the new csd client which should be the issue
anyway, the important patch is the thermal stuff which from our test make phone colder
 

dron39

Senior Member
Sep 20, 2009
723
112
a newer build is in queue, should be out later today after the nightlies task

i have removed the new csd client which should be the issue
anyway, the important patch is the thermal stuff which from our test make phone colder

Is there any way to update CWM from CM 10.2?
Currently won't support exFAT FS...

CSD=new audio driver for calling?
 
Last edited:

Kali-

Inactive Recognized Developer
Apr 11, 2010
1,633
2,593
Roma
i cant flash yuga right now, but thermal changes are not the problem
also i have flashed pollux (tab z lte) with the same changes an it just works fine
 
  • Like
Reactions: power461

OCmylife

Senior Member
Oct 15, 2010
530
278
36
Bocholt(NRW)
Not the most efficient method, but create a local_manifest.xml file in (CM dir)/.repo with the following, save and repo sync:



After which, run



This *should* work, since this is what I usually do :)

I tried that, but I got the following error:

fatal: duplicate project CyanogenMod/android_device_sony_yuga in /home/ocmylife/android/system/.repo/manifest.xml

So I have to delete those lines in the .repo/manifest.xml file, right? But I didn`t found them in there.
 

jeroenqui

Senior Member
Mar 22, 2010
1,042
4,464
▂ ▃ ▅ ▆ █
I tried that, but I got the following error:

fatal: duplicate project CyanogenMod/android_device_sony_yuga in /home/ocmylife/android/system/.repo/manifest.xml

So I have to delete those lines in the .repo/manifest.xml file, right? But I didn`t found them in there.

Paste your manifest.xml here so we can check if something is wrong :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 117
    CyanogenMod is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your phone.

    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.
    */
    66
    HOWTO

    Install instructions:
    first time
    - power off the phone:
    - hold vol+ and plug usb to boot into fastboot (blu led)
    - fastboot flash boot boot.img (from cm10 zip)
    - fastboot reboot
    - enter recovery, on boot led will be violet for 3'', during this period press vol+
    - flash rom zip
    - flash gapps zip
    - wipe
    - reboot

    for update just flash rom zip from recovery
    Google Apps are not included in this ROM. You'll need to find those yourself if you want them.


    ENJOY AN UNOFFICIAL CM10 RELEASE BROUGHT TO YOU BY FreeXperia Team


    PLEASE DONT MIRROR OUR ROMS

    DOWNLOAD
    http://unrestrict.li/FXP
    48
    So, camera as of right now (I'm calling it a night at this point...)

    It now starts up. Preview works, still pictures work.

    However a bunch of issues remain:
    Video recording does not work
    Flash does not work
    Preview freezes after taking a picture until you exit and enter cam app or switch between front/back cams
    Camera icon does not appear in launcher (but you can access cam from lockscreen)

    Still quite a bit to go, but it's significant progress.
    43
    thanks to all who made this possible supporting us
    contributing with code, donations or even trusting us
    thanks to SONY that made all this possible !
    30
    hi.

    im thinking of buying a sony xperia z, but im a cyanogenmod lover. i've been reading about this phone and i have some doubts. and sorry if this is not the appropriate place to ask this, but, im very interested in this rom in case i get the phone.

    i found out that to b able to customize the phone i need to get boot loader unlocked. but that will make me lose bravia engine and FOTA. FOTA is the official sony updates on the rom correct? or is the firmware for something else? even with a custom rom will i need to flash the firmware updates of sony? is there a way to get bravia engine back? does bravia engine 2 makes a diference?

    are there any major known bugs on this rom using CM10.1 (camera, bluetooth, wifi...)?

    thanks in advance

    FOTA is Sony's equivalent of the recovery partition - it just means you can't update your firmware over-the-air. You can still update using FlashTool and an FTF file, or flashing something in CWM.

    Yeah, you'll lose BE2 but I really never saw it as having much of a point...

    Also, one of the CM maintainers (arcee) gave us a great hint of a potentially much easier way to get camera working. If this works it'll be a lot easier than what Steve (cyanogen) did. :)

    The camera issue is basically common to CM10.1 on every single Qualcomm MSM8960 and APQ8064 device that is currently shipping with 4.1 - The Nexus 4 Adreno (GPU) blobs were compiled against one version of gralloc_priv.h, the cam HALs in Android 4.1 of basically every Krait device were compiled against a different version. It turns out, though, that the specific fields the camera uses and those the Nexus GPU blobs care about don't overlap - and all of the other fields are only used in internal compiled code.

    Specifically, cam cares about fd, size, and offset. Adreno blobs care about gpuaddr and maybe some other things - but not fd, size, or offset.

    So we use a custom gralloc_priv.h header that reorders some elements, specifically moving bufferType (which is only used by compiled code and not by any of the blobs) previous to size/offset, so that size/offset are now 4 bytes down from where they were, matching the cam HAL but without moving gpuaddr and breaking the adreno blobs.

    If this works, it's much easier than using IDA to hack Sony's cam blobs, asking Sony to recompile (I'm sure they would be willing to, but might encounter issues with laywers for Qcom-origin code...), or rebasing our kernel up to the latest CAF stuff so we can use QDevNet Adreno blobs (which won't be a magic bullet any more anyway...)