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

Search This thread

Thenetstriker

Senior Member
Jul 24, 2008
163
104
I've just received my MHL HDMI cable and tested it with the newest cm10.2 nightly build. I did find some hdcp error messages in the dmesg log:

Code:
<6>[ 9401.187407] hdmi_msm hdmi_msm.1: HDCP: AUTH_FAIL_INT received, LINK0_STATUS=0x30000054
<3>[ 9403.185851] hdmi_msm hdmi_msm.1: hdcp_authentication_part1(2600): timedout, Link0=<No RI Match INTR in time>
<3>[ 9403.196684] hdmi_msm hdmi_msm.1: [hdcp_authentication_part1]: HDCP Reauthentication
<4>[ 9403.203795] hdmi_msm hdmi_msm.1: [DEV_DBG]: Calling reauth from [hdmi_msm_hdcp_enable]

I found a switch name hdcp_feature_on in drivers/video/msm/hdmi_msm.c. I compiled a new version with this setting set to false and these errors didn't occur any more. But still there was no video and audio when connecting the cable. Here is the log with hdcp_feature_on = false:

Code:
<6>[  422.017272] mhl: MHL detected
<6>[  422.020202] mhl_usb_online_work: mhl usb online(1)
<6>[  422.025085] msm_otg msm_otg: b_idle work, inputs=0x00020003
<6>[  422.033233] msm_otg msm_otg: changed to mhl_detected, from b_idle
<6>[  422.043701] msm_otg msm_otg: mhl_detected work, inputs=0x00020003
<6>[  422.050018] msm_otg msm_otg: changed to mhl_connected, from mhl_detected
<6>[  422.168151] check_recover_vbus_collapse: VBUS input current still limiting to 0 mA. Retry set 700 mA
<6>[  422.659820] check_recover_vbus_collapse: VBUS input current limiting to 500 mA. Retry set 700 mA
<6>[  422.835144] DCAP: 00 DEV_STATE       : 00
<3>[  422.838287] hdmi_msm hdmi_msm.1: hdmi: HDMI HPD: QDSP OFF
<6>[  422.846832] DCAP: 01 MHL_VERSION     : 10
<6>[  422.853820] DCAP: 02 DEV_CAT         : 13 DEV_TYPE=3 POW=y PLIM0=n PLIM1=n
<6>[  422.868225] mhl_sii_charging_enable (enable)
<6>[  422.874420] DCAP: 03 ADOPTER_ID_H    : 00
<6>[  422.879730] DCAP: 04 ADOPTER_ID_L    : 00
<6>[  422.885986] DCAP: 05 VID_LINK_MODE   : 37
<6>[  422.891113] DCAP: 06 AUD_LINK_MODE   : 00
<6>[  422.894409] hdmi_msm hdmi_msm.1: EDID BLK=0
<6>[  422.898376] hdmi_msm hdmi_msm.1: 00 | 00 FF FF FF FF FF FF 00 3D CB 81 0C 00 00 00 00
<6>[  422.909881] DCAP: 07 VIDEO_TYPE      : 00
<6>[  422.915344] hdmi_msm hdmi_msm.1: 10 | 00 16 01 03 80 46 27 78 0A EE 91 A3 54 4C 99 26
<6>[  422.923553] DCAP: 08 LOG_DEV_MAP     : 00
<6>[  422.930786] DCAP: 09 BANDWIDTH       : 0F
<6>[  422.936035] hdmi_msm hdmi_msm.1: 20 | 0F 50 54 BD EF 80 71 4F 81 00 81 40 81 80 95 00
<6>[  422.943054] DCAP: 0A FEATURE_FLAG    : 00 RCP=n RAP=n SP=n
<6>[  422.954559] hdmi_msm hdmi_msm.1: 30 | 95 0F B3 00 A9 40 02 3A 80 18 71 38 2D 40 58 2C
<6>[  422.963226] DCAP: 0B DEVICE_ID_H     : 92
<6>[  422.968475] DCAP: 0C DEVICE_ID_L     : 41
<6>[  422.977600] hdmi_msm hdmi_msm.1: 40 | 45 00 A0 5A 00 00 00 1E 66 21 50 B0 51 00 1B 30
<6>[  422.984649] hdmi_msm hdmi_msm.1: 50 | 40 70 36 00 A0 5A 00 00 00 1E 00 00 00 FC 00 54
<6>[  422.993804] DCAP: 0D SCRATCHPAD_SIZE : 00
<6>[  422.998809] DCAP: 0E INT_STAT_SIZE   : 33
<6>[  423.003509] hdmi_msm hdmi_msm.1: 60 | 58 2D 4E 52 38 31 38 0A 20 20 20 20 00 00 00 FD
<6>[  423.011169] DCAP: 0F Reserved        : 00
<6>[  423.025573] hdmi_msm hdmi_msm.1: 70 | 00 18 4B 1A 51 11 00 0A 20 20 20 20 20 20 01 7D
<6>[  423.081909] hdmi_msm hdmi_msm.1: EDID BLK=1
<6>[  423.085144] hdmi_msm hdmi_msm.1: 00 | 02 03 3D F1 4B 90 1F 04 13 05 14 03 12 20 21 22
<6>[  423.093078] hdmi_msm hdmi_msm.1: 10 | 38 09 7F 07 0F 7F 07 17 07 50 3F 06 C0 4D 02 00
<6>[  423.100891] hdmi_msm hdmi_msm.1: 20 | 57 06 00 5F 7E 01 67 54 00 83 4F 00 00 6C 03 0C
<6>[  423.108642] hdmi_msm hdmi_msm.1: 30 | 00 18 00 B8 2D C0 00 00 00 00 E2 00 0F 01 1D 00
<6>[  423.116455] hdmi_msm hdmi_msm.1: 40 | 72 51 D0 1E 20 6E 28 55 00 A0 5A 00 00 00 1E 01
<6>[  423.124603] hdmi_msm hdmi_msm.1: 50 | 1D 00 BC 52 D0 1E 20 B8 28 55 40 A0 5A 00 00 00
<6>[  423.132080] hdmi_msm hdmi_msm.1: 60 | 1E 01 1D 80 18 71 1C 16 20 58 2C 25 00 A0 5A 00
<6>[  423.140045] hdmi_msm hdmi_msm.1: 70 | 00 00 9E 00 00 00 00 00 00 00 00 00 00 00 00 A9
<6>[  423.147705] hdmi_msm hdmi_msm.1: EDID: 3D present, 3D-len=0
<4>[  423.153228] hdmi_msm hdmi_msm.1: EDID: type=7 block not found in EDID block
<6>[  423.160247] hdmi_msm hdmi_msm.1: EDID (V=1.3, #CEABlocks=1[V3], ID=ONK, IEEE=0c03, EDID-Ext=0x02)
<6>[  423.170654] hdmi_msm hdmi_msm.1: hdmi_msm_send_event: hdmi state switched to 1
<6>[  423.176910] hdmi_msm hdmi_msm.1: HDMI HPD: CONNECTED: send ONLINE
<6>[  423.183685] hdmi_msm hdmi_msm.1: HDMI HPD: sense : send HDCP_PASS
<6>[  423.204589] mdp4_dtv_start: <ID=16 1920x1080 (88,44,148), (4,5,36) 148MHz>
<6>[  423.207458] dtv_on: tv_src_clk=148500kHz, pm_qos_rate=148500kHz, [0]
<6>[  423.208099] hdmi_msm hdmi_msm.1: HDMI cable connected hdmi_msm_power_on(1920x1080, 148500000)
<3>[  423.208221] Video format is : 16
<6>[  423.208251] hdmi_msm hdmi_msm.1: HDMI Audio: Enabled
<6>[  423.209075] hdmi_msm hdmi_msm.1: hdmi_msm_turn_on: hdmi_audio state switched to 1
<6>[  423.209106] hdmi_msm hdmi_msm.1: HDMI Core: Initialized
<6>[  423.209106] hdmi_msm hdmi_msm.1: power=ON DVI= OFF
<6>[  423.209106] mdp4_dtv_on:
<7>[  423.211120] AUDIO DATA BLOCK: 0000001800000001 0717077f0f077f09 5700024dc0063f50 005467017e5f0006
<7>[  423.211242] SPKR ALLOC DATA BLOCK: 01 00 00 00 03 00 00 00 4f 00 00
<7>[  423.213073] AUDIO DATA BLOCK: 0000001800000001 0717077f0f077f09 5700024dc0063f50 005467017e5f0006
<7>[  423.213195] SPKR ALLOC DATA BLOCK: 01 00 00 00 03 00 00 00 4f 00 00

Does anyone have an idea what else could be the problem?
 

dron39

Senior Member
Sep 20, 2009
723
112
after 10.1.3 RC2 i merged a bunch of patches which need to be tested
it also use newer adreno blob and near all the blob come from 4.2.2

should be stable like RC2, codebase is exactly the same, only device specific is changed

If i flash it - can i update CM to *RC3* or another 10.1.x nightly's without any problems, or i need choose BSP builds in the future?
 

parapaul

Senior Member
Apr 27, 2008
141
18
West Midlands
If i flash it - can i update CM to *RC3* or another 10.1.x nightly's without any problems, or i need choose BSP builds in the future?

Yes - you can keep flashing 10.1.x builds without any problem.

---------- Post added at 08:44 AM ---------- Previous post was at 08:34 AM ----------

I know there's no bug reports for nightly builds, but I've scrolled through the last few pages and not seen this mentioned so I wondered if it may be helpful for the devs:

10.2 nightly 0905:

1. Lockscreen slider shortcuts will not save empty spaces. Replacing apps works, but empy spaces won't save.
2. Graphical glitches using Swiftkey keyboard - against a white background (G+, Chrome or SMS apps) screen occasionally flickers black/white. I'll try the stock keyboard and see if it's a CM or Swiftkey problem.
 

rohit25

Senior Member
Jun 12, 2012
1,685
352
Delhi
Google Pixel 2 XL
Yes - you can keep flashing 10.1.x builds without any problem.

---------- Post added at 08:44 AM ---------- Previous post was at 08:34 AM ----------

I know there's no bug reports for nightly builds, but I've scrolled through the last few pages and not seen this mentioned so I wondered if it may be helpful for the devs:

10.2 nightly 0905:

1. Lockscreen slider shortcuts will not save empty spaces. Replacing apps works, but empy spaces won't save.
2. Graphical glitches using Swiftkey keyboard - against a white background (G+, Chrome or SMS apps) screen occasionally flickers black/white. I'll try the stock keyboard and see if it's a CM or Swiftkey problem.

Okay workaround for slider shortcut.... Instead of choosing apps.... Choose direct dial and choose a number select okay and you will see the direct dial icon.....
Now just slide to the direct dial icon and choose none..... viola empty slider shortcut can be saved

Sent from my C6603 using xda premium
 

dron39

Senior Member
Sep 20, 2009
723
112
In BSP expiremental builds 05-sep not working adb sideload and recovery and recovery can't mount exFAT formatted memory card.
So how can i flash this if i don't have FAT32 card and always format internal memory...:confused:
Flash it now with adb sideload...
 
Last edited:

highKo

Senior Member
Jul 10, 2009
540
86
Altenburg, Thuringia, Germany
Yes - you can keep flashing 10.1.x builds without any problem.

---------- Post added at 08:44 AM ---------- Previous post was at 08:34 AM ----------

I.
2. Graphical glitches using Swiftkey keyboard - against a white background (G+, Chrome or SMS apps) screen occasionally flickers black/white. I'll try the stock keyboard and see if it's a CM or Swiftkey problem.

I have these flickers, too. And I'm using swype keyboard
 

Smurflin96

Member
Sep 17, 2012
34
1
Hello,

Could someone please tell me more specific how i install CM? I didnt quite understand the tutorial in the OP.

Im a noob,

Thank you,
 

jeroenqui

Senior Member
Mar 22, 2010
1,042
4,464
▂ ▃ ▅ ▆ █
Hello,

Could someone please tell me more specific how i install CM? I didnt quite understand the tutorial in the OP.

Im a noob,

Thank you,

Basically :
- unlock your bootloader
- fastboot flash the boot.img from inside the CM zip file
- boot to recovery
- do a factory reset there
- flash the cm zip + gapps zip
- reboot

Sent from my C6603 using Tapatalk 4
 

Smurflin96

Member
Sep 17, 2012
34
1
Basically :
- unlock your bootloader
- fastboot flash the boot.img from inside the CM zip file
- boot to recovery
- do a factory reset there
- flash the cm zip + gapps zip
- reboot

Sent from my C6603 using Tapatalk 4

Do i have to unlock my bootloader?

Fastboot flash, is that using flashtool? So i open flashtool and select fastboot (not flashmode) ?
I dont have any recovery either.

Thanks
 

tomitsu

Senior Member
Jan 8, 2012
95
69
I have a kind of a noob question. What is the difference between FXP builds and the CM builds?

Wysłane z mojego C6603 przy użyciu Tapatalk 4
 

golfgtiedition30

Senior Member
Dec 2, 2012
1,703
1,315
Sony Xperia Z
Samsung Galaxy Ace II
Do i have to unlock my bootloader?

Fastboot flash, is that using flashtool? So i open flashtool and select fastboot (not flashmode) ?
I dont have any recovery either.

Thanks

To flash ANY non stock ROM you need to unlock your bootloader.
Do not attempt to flash this unless you have unlocked.
There's loads of info on the forum....go read it.




Sent from my C6603 using XDA Premium 4 mobile app
 

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