Guest luca020400 Posted October 25, 2014 Report Posted October 25, 2014 (edited) The browser is very bugged :( No white boxes but i have black boxes ( really big 1/3 of display ) I hope this can be fixed Later I will build for cm11 And other small graphical glitches on tab switch ( browser ) EDIT : DPI to 240 fixed the black boxes Edited October 25, 2014 by luca020400
Guest luca020400 Posted October 25, 2014 Report Posted October 25, 2014 You should use somethink media-caf-legacy and android_hardware_qcom_display Check team hacklg
Guest DeSTRxL Posted October 25, 2014 Report Posted October 25, 2014 Finally !!!! Thanks chil really good , gave much trouble, it also works on stock browser ?
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 Check this chil https://github.com/armani-dev/android_hardware_qcom_media-caf-legacy https://github.com/armani-dev/android_hardware_qcom_display-caf-legacy caf-legacy
Guest fonz93 Posted October 26, 2014 Report Posted October 26, 2014 (edited) Check this chil https://github.com/armani-dev/android_hardware_qcom_media-caf-legacy https://github.com/armani-dev/android_hardware_qcom_display-caf-legacy caf-legacy Caf-legacy is normal caf, they call it legacy because there is a new-caf (https://github.com/CyanogenMod/android_hardware_qcom_display-caf-new) Edited October 26, 2014 by fonz93
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 Caf-legacy is normal caf, they call it legacy because there is a new-caf OK :(
Guest DeSTRxL Posted October 26, 2014 Report Posted October 26, 2014 The browser is very bugged :( No white boxes but i have black boxes ( really big 1/3 of display ) I hope this can be fixed Later I will build for cm11 And other small graphical glitches on tab switch ( browser ) EDIT : DPI to 240 fixed the black boxes I don't have this problem with DPI at 200 (black box)..
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 (edited) Building cm11 with display and media caf i got this error frameworks/av/media/libmediaplayerservice/StagefrightRecorder.cpp:66:25: fatal error: QCMediaDefs.h: No such file or directory compilation terminated. My fault ;) Using TeamHackLG display-caf In file included from hardware/qcom/display-caf/libhwcomposer/hwc_utils.h:33:0, from hardware/qcom/display-caf/libqdutils/cb_utils.h:33, from hardware/qcom/display-caf/libqdutils/cb_utils.cpp:28: hardware/qcom/display-caf/liboverlay/overlayUtils.h:270:20: error: 'MDP_OVERLAY_PP_CFG_EN' was not declared in this scope hardware/qcom/display-caf/liboverlay/overlayUtils.h: In function 'bool overlay::utils::isYuv(uint32_t)': hardware/qcom/display-caf/liboverlay/overlayUtils.h:486:14: error: 'MDP_YCBYCR_H2V1' was not declared in this scope Edited October 26, 2014 by luca020400
Guest chil360 Posted October 26, 2014 Report Posted October 26, 2014 Are you using the experimental kernel branch?
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 https://github.com/luca020400?tab=repositories Probably I fixed it
Guest DeSTRxL Posted October 26, 2014 Report Posted October 26, 2014 With the ram to 380 ( more or less ) games that I could not run now travel safely
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 With the ram to 380 ( more or less ) games that I could not run now travel safely This is fantastic ;) But I can't run some games with the display-caf ( in aospa work perfectly )
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 (edited) Cyanogenmod 11 doesn't boot :( The rom boots but the screen is black ( adb find mine device but is offline ) Edited October 26, 2014 by luca020400
Guest DeSTRxL Posted October 26, 2014 Report Posted October 26, 2014 This is fantastic ;) But I can't run some games with the display-caf ( in aospa work perfectly ) With the beta 5 aospa how much RAM is available ?
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 (edited) Stock ram ;) @chil360 : this should fix camera ;) https://github.com/luca020400/android_device_huawei_msm7x27a-common/commit/dc1934f754d681b0e1dc3d706824873545783d5b Edited October 26, 2014 by luca020400
Guest DeSTRxL Posted October 26, 2014 Report Posted October 26, 2014 Stock ram ;) @chil360 : this should fix camera ;) https://github.com/luca020400/android_device_huawei_msm7x27a-common/commit/dc1934f754d681b0e1dc3d706824873545783d5b Great , since we are try :)
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 New cm11 doesn't boot :( ( stuck at bootloader )
Guest fonz93 Posted October 26, 2014 Report Posted October 26, 2014 New cm11 doesn't boot :( ( stuck at bootloader ) Did you try to build with dazzozo's frameworks/native?
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 You can check mine locale manifest
Guest chil360 Posted October 26, 2014 Report Posted October 26, 2014 Cyanogenmod 11 doesn't boot :( The rom boots but the screen is black ( adb find mine device but is offline ) In vendor/cm/config/common.mk change persist.sys.root_access from 1 to 3. This enables 'Apps and ADB' root access. This will allow you to use adb logcat during boot so you can see what's going on.
Guest luca020400 Posted October 26, 2014 Report Posted October 26, 2014 OK thanks But now the ROM doesn't boot :( I overwritted the bootable cm11 )
Guest chil360 Posted October 27, 2014 Report Posted October 27, 2014 Made some progess with video decoding... If I add back my modified frameworks_av and set TARGET_QCOM_LEGACY_OMX := true in BoardCommonConfig.mk then video playback works but the color formats are wrong. So I get a green bar at the top of the video and other wierd colors. I copied the frameworks_av changes from legacymod/frameworks_av to my slim based repo when I ported SlimKat as Dazzozo uses this repo in his CM11 rom. It's strange though - most of the changes are only activated when TARGET_QCOM_LEGACY_OMX is set but Dazzozo doesn't set this flag. So why the need for using this repo?? This must be why Luca and I have seen no difference when building roms without the modified frameworks_av.
Guest luca020400 Posted October 27, 2014 Report Posted October 27, 2014 (edited) This should fix camera video recording ;) https://github.com/luca020400/android_device_huawei_msm7x27a-common/commit/dc1934f754d681b0e1dc3d706824873545783d5b And I and Y300-0100 updated OMX and Adreno libs https://github.com/LiquidSmoothHuawei/proprietary_vendor_huawei/commit/a0241c45c21f50c9177abc28015f9606248c4ce0 and https://github.com/LiquidSmoothHuawei/proprietary_vendor_huawei/commit/afccd7c18a2c8fe8244054387af97ffae025dcd0 Edited October 27, 2014 by luca020400
Guest luca020400 Posted October 27, 2014 Report Posted October 27, 2014 (edited) Mine aospa with display caf won't boot ( like cm11 ) stuck at he bootloader Stuck at the bootloader but adb workf fine hahha So the display-caf is bugged I missed some libs ;) I will try later Edited October 27, 2014 by luca020400
Guest luca020400 Posted October 27, 2014 Report Posted October 27, 2014 (edited) logcat with correct libs http://pastebin.com/Dkn7jCdM and this http://pastebin.com/6LDapYcy I/DEBUG ( 144): #01 bef3e8d0 4030b199 /system/lib/libsurfaceflinger.so Surface flinger bug :( Hi dazz :D Finally boots correclty Edited October 27, 2014 by luca020400
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now