Jump to content

[DEV][ROM][13.11.] CyanogenMod 12.1 (Android 5.1.1) for Huawei Y5


Guest KonstaT
 Share

Recommended Posts

24 minutes ago, redxz said:

Well I don't know how am I supposed to enable the drivers then...

Maybe I can backup the msm8909-y560_defconfig and after I have done repo sync replace it?

By editing the msm8909-y560_defconfig of course. Just meant that first build the kernel like your supposed to. Then you can trace your own steps when you start breaking sht. You break, you fix...

Link to comment
Share on other sites

17 minutes ago, KonstaT said:

By editing the msm8909-y560_defconfig of course. Just meant that first build the kernel like your supposed to. Then you can trace your own steps when you start breaking sht. You break, you fix...

Alright, doing it now.

Link to comment
Share on other sites

Okay, I'm confused with this one. I resynced the source, and now I get this:

----------

 arch/arm/mm/pgd.o
  CC      arch/arm/mm/mmu.o
  CC      arch/arm/common/firmware.o
  LD      arch/arm/common/built-in.o
  CC      arch/arm/net/bpf_jit_32.o
  CC      arch/arm/mm/proc-syms.o
  CC      arch/arm/mm/alignment.o
  AS      arch/arm/mm/abort-ev7.o
  AS      arch/arm/mm/pabort-v7.o
  AS      arch/arm/mm/cache-v7.o
  CC      arch/arm/mm/copypage-v6.o
In file included from ../../../../../../kernel/huawei/msm8909/include/linux/cache.h:4:0,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/time.h:4,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/stat.h:18,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/module.h:10,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/moduleloader.h:5,
                 from ../../../../../../kernel/huawei/msm8909/arch/arm/net/bpf_jit_32.c:15:
../../../../../../kernel/huawei/msm8909/arch/arm/net/bpf_jit_32.c: In function 'bpf_jit_compile':
../../../../../../kernel/huawei/msm8909/include/linux/kernel.h:666:17: warning: comparison of distinct pointer types lacks a cast [enabled by default]
error, forbidden warning: kernel.h:666
make[3]: *** [arch/arm/net/bpf_jit_32.o] Error 1
make[2]: *** [arch/arm/net] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC      arch/arm/mm/context.o
  AS      arch/arm/mm/tlb-v7.o
  AS      arch/arm/mm/proc-v7.o
target SharedLib: libc++ (/home/red/android/system/out/target/product/y560/obj/SHARED_LIBRARIES/libc++_intermediates/LINKED/libc++.so)
  LD      arch/arm/mm/built-in.o
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/red/android/system/kernel/huawei/msm8909'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/red/android/system'

------------

Edited by redxz
Link to comment
Share on other sites

3 hours ago, optimusanna™ said:

Hi,

I might have overlooked this, but is this ROM compatible with Huawei Y5 II model CUN-L33 ?

No. Its a completely different device. It is stated in the first post that its made for Huawei Y5 (Y560-L01/L02/L03/U23)

Edited by redxz
Link to comment
Share on other sites

8 hours ago, redxz said:

Okay, I'm confused with this one. I resynced the source, and now I get this:

----------

 arch/arm/mm/pgd.o
  CC      arch/arm/mm/mmu.o
  CC      arch/arm/common/firmware.o
  LD      arch/arm/common/built-in.o
  CC      arch/arm/net/bpf_jit_32.o
  CC      arch/arm/mm/proc-syms.o
  CC      arch/arm/mm/alignment.o
  AS      arch/arm/mm/abort-ev7.o
  AS      arch/arm/mm/pabort-v7.o
  AS      arch/arm/mm/cache-v7.o
  CC      arch/arm/mm/copypage-v6.o
In file included from ../../../../../../kernel/huawei/msm8909/include/linux/cache.h:4:0,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/time.h:4,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/stat.h:18,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/module.h:10,
                 from ../../../../../../kernel/huawei/msm8909/include/linux/moduleloader.h:5,
                 from ../../../../../../kernel/huawei/msm8909/arch/arm/net/bpf_jit_32.c:15:
../../../../../../kernel/huawei/msm8909/arch/arm/net/bpf_jit_32.c: In function 'bpf_jit_compile':
../../../../../../kernel/huawei/msm8909/include/linux/kernel.h:666:17: warning: comparison of distinct pointer types lacks a cast [enabled by default]
error, forbidden warning: kernel.h:666
make[3]: *** [arch/arm/net/bpf_jit_32.o] Error 1
make[2]: *** [arch/arm/net] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC      arch/arm/mm/context.o
  AS      arch/arm/mm/tlb-v7.o
  AS      arch/arm/mm/proc-v7.o
target SharedLib: libc++ (/home/red/android/system/out/target/product/y560/obj/SHARED_LIBRARIES/libc++_intermediates/LINKED/libc++.so)
  LD      arch/arm/mm/built-in.o
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/red/android/system/kernel/huawei/msm8909'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/red/android/system'

------------

You're still compiling with some complete wrong defconfig (you've enabled CONFIG_BPF_JIT).

Link to comment
Share on other sites

7 hours ago, redxz said:

No. Its a completely different device. It is stated in the first post that its made for Huawei Y5 (Y560-L01/L02/L03/U23)

Ok, thanks for the response.

Link to comment
Share on other sites

5 hours ago, KonstaT said:

You're still compiling with some complete wrong defconfig (you've enabled CONFIG_BPF_JIT).

Alright, I resynced the entire source, executed 'source build/envsetup.sh' and 'brunch y560'. I didn't modify anything. But this time, I get errors about drivers/input/touchscreen. Log:

-----------------------------

CHK     kernel/config_data.h                                                  target thumb C++: libOmxVdec <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/vdec/src/hevc_utils.cpp                                                      target thumb C++: libOmxVdec <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp                                                target thumb C++: libOmxVidcCommon <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/common/src/extra_data_handler.cpp                                      target thumb C++: libOmxVidcCommon <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/common/src/vidc_color_converter.cpp
  LD      drivers/input/touchscreen/built-in.o                                  /home/red/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-ld: cannot find /home/red/android/system/kernel/huawei/msm8909/drivers/input/touchscreen/ft_gesture_lib.a: No such file or directory
make[5]: *** [drivers/input/touchscreen/built-in.o] Error 1
make[4]: *** [drivers/input/touchscreen] Error 2
make[3]: *** [drivers/input] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/red/android/system/kernel/huawei/msm8909'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/red/android/system'

#### make failed to build some targets (45:48 (mm:ss)) ####

---------------------

I Googled this issue, and it appears that some guy has the same issue with the same chipset (msm8909).

Edited by redxz
Link to comment
Share on other sites

4 hours ago, redxz said:

Alright, I resynced the entire source, executed 'source build/envsetup.sh' and 'brunch y560'. I didn't modify anything. But this time, I get errors about drivers/input/touchscreen. Log:

-----------------------------

CHK     kernel/config_data.h                                                  target thumb C++: libOmxVdec <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/vdec/src/hevc_utils.cpp                                                      target thumb C++: libOmxVdec <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/vdec/src/omx_vdec_msm8974.cpp                                                target thumb C++: libOmxVidcCommon <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/common/src/extra_data_handler.cpp                                      target thumb C++: libOmxVidcCommon <= hardware/qcom/media-caf/msm8916/mm-video-v4l2/vidc/common/src/vidc_color_converter.cpp
  LD      drivers/input/touchscreen/built-in.o                                  /home/red/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-ld: cannot find /home/red/android/system/kernel/huawei/msm8909/drivers/input/touchscreen/ft_gesture_lib.a: No such file or directory
make[5]: *** [drivers/input/touchscreen/built-in.o] Error 1
make[4]: *** [drivers/input/touchscreen] Error 2
make[3]: *** [drivers/input] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/red/android/system/kernel/huawei/msm8909'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/red/android/system'

#### make failed to build some targets (45:48 (mm:ss)) ####

---------------------

I Googled this issue, and it appears that some guy has the same issue with the same chipset (msm8909).

It's most definitely there, if not, add it. Have you run make mrproper again? I think it also removes all .a.

All .a files are ignored by git so I had to force add it. Maybe git clone is not picking it up either. I'll check. Edit. Not a problem with git.

Edited by KonstaT
Link to comment
Share on other sites

4 hours ago, KonstaT said:

It's most definitely there, if not, add it. Have you run make mrproper again? I think it also removes all .a.

All .a files are ignored by git so I had to force add it. Maybe git clone is not picking it up either. I'll check.

Oh, i think i found the issue. The network apparently cut off, so im afraid it didn't sync all the files. But might be also cause of git. Sorry for disturbing you in any case.

Edited by redxz
Link to comment
Share on other sites

I resynced the entire thing, and applied the patches you sent earlier. It all compiled, except for dt.img. Log:

---------------------------------

Target dt image: /home/red/android/system/out/target/product/y560/dt.img
DTB combiner:
  Input directory: '/home/red/android/system/out/target/product/y560/obj/KERNEL_OBJ/arch/arm/boot/'
  Output file: '/home/red/android/system/out/target/product/y560/dt.img'
=> Found 0 unique DTB(s)
chmod: cannot access ‘/home/red/android/system/out/target/product/y560/dt.img’: No such file or directory
make: *** [/home/red/android/system/out/target/product/y560/dt.img] Error 1
make: *** Waiting for unfinished jobs....
/home/red/android/system/out/host/linux-x86/bin/checkpolicy:  policy configuration loaded
/home/red/android/system/out/host/linux-x86/bin/checkpolicy:  writing binary representation (version 26) to /home/red/android/system/out/target/product/y560/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit
make: Leaving directory `/home/red/android/system'

#### make failed to build some targets (25:07 (mm:ss)) ####

--------------------------

Link to comment
Share on other sites

25 minutes ago, redxz said:

I resynced the entire thing, and applied the patches you sent earlier. It all compiled, except for dt.img. Log:

---------------------------------

Target dt image: /home/red/android/system/out/target/product/y560/dt.img
DTB combiner:
  Input directory: '/home/red/android/system/out/target/product/y560/obj/KERNEL_OBJ/arch/arm/boot/'
  Output file: '/home/red/android/system/out/target/product/y560/dt.img'
=> Found 0 unique DTB(s)
chmod: cannot access ‘/home/red/android/system/out/target/product/y560/dt.img’: No such file or directory
make: *** [/home/red/android/system/out/target/product/y560/dt.img] Error 1
make: *** Waiting for unfinished jobs....
/home/red/android/system/out/host/linux-x86/bin/checkpolicy:  policy configuration loaded
/home/red/android/system/out/host/linux-x86/bin/checkpolicy:  writing binary representation (version 26) to /home/red/android/system/out/target/product/y560/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit
make: Leaving directory `/home/red/android/system'

#### make failed to build some targets (25:07 (mm:ss)) ####

--------------------------

 

23 hours ago, KonstaT said:

You need to revert this or cherry-pick quite a few commits from cm-13.0.

cd device/huawei/y560
git revert 85fbe8c0b375f2624a68b13a777c275179c78228

 

Edited by KonstaT
Link to comment
Share on other sites

3 hours ago, KonstaT said:

 

cd device/huawei/y560
git revert 85fbe8c0b375f2624a68b13a777c275179c78228

 

Package Complete: /home/red/android/system/out/target/product/y560/cm-12.1-20161207-UNOFFICIAL-y560.zip

 

Thank you very much for helping me out!

Link to comment
Share on other sites

10 hours ago, redxz said:

Package Complete: /home/red/android/system/out/target/product/y560/cm-12.1-20161207-UNOFFICIAL-y560.zip

 

Thank you very much for helping me out!

Well done!

7 hours ago, redxz said:

Well, everything seems to be working fine, except for the SIM card. It shows "Emergency calls only". Why is that?

On 12/6/2016 at 9:21 PM, KonstaT said:

... Yep telephony implementation is the biggest problem. I spent two weeks reverse engineering that so I'm not sure if I'm going to make that patch available. You can probably still get RIL working by using couple of prebuilt jars from the latest build I've released.

Try pushing /system/framework/framework.jar and /system/framework/telephony-common.jar from my latest release.

Link to comment
Share on other sites

1 hour ago, KonstaT said:

Try pushing /system/framework/framework.jar and /system/framework/telephony-common.jar from my latest release.

What are the commands to do so? I'm new to Git.

Link to comment
Share on other sites

28 minutes ago, redxz said:

What are the commands to do so? I'm new to Git.

No, on your phone. Extract them from my release using your favorite zip tool and copy them to your device's /system using your favorite root file explorer.

Edited by KonstaT
Link to comment
Share on other sites

40 minutes ago, KonstaT said:

No, on your phone. Extract them from my release using your favorite zip tool and copy them to your device's /system using your favorite root file explorer.

Okay, got it. Where can I download the files from? I can't seem to find them.

Nevermind, found them in the 13.0 release.

Edited by redxz
Link to comment
Share on other sites

1 hour ago, redxz said:

Okay, got it. Where can I download the files from? I can't seem to find them.

Nevermind, found them in the 13.0 release.

No, not CM13! From the CM12.1 build that is in the first post of this thread of course.

Link to comment
Share on other sites

12 hours ago, KonstaT said:

No, not CM13! From the CM12.1 build that is in the first post of this thread of course.

Alright, the system works as supposed now, though I noticed a few bugs:

  • The variable $EXTERNAL_STORAGE points to /storage/emulated/legacy, which is the internal storage.
  • The home button and menu button functions are switched places (Can be changed from the 'Buttons' menu in the settings.

Other than that, I see no reason why this can't be an official version of CyanogenMod.

Link to comment
Share on other sites

9 hours ago, redxz said:

Alright, the system works as supposed now, though I noticed a few bugs:

  • The variable $EXTERNAL_STORAGE points to /storage/emulated/legacy, which is the internal storage.

Exactly where it's supposed to point. $SECONDARY_STORAGE is external storage. https://source.android.com/devices/storage/config-example.html#android_5_x_both

9 hours ago, redxz said:
  • The home button and menu button functions are switched places (Can be changed from the 'Buttons' menu in the settings.

No such issue. 'Square' button is and is supposed to be MENU button on this device. You're probably just confused that it's not multi-tasking button like it is on Android navigation bar.

9 hours ago, redxz said:

Other than that, I see no reason why this can't be an official version of CyanogenMod.

Goal was never to be official CyanogenMod. There's nothing in it for me.

Link to comment
Share on other sites

6 hours ago, KonstaT said:

Goal was never to be official CyanogenMod. There's nothing in it for me.

Well, I meant it as a compliment, because it works really well, it's fast and responsive too, I even think its better than the stock ROM.

Link to comment
Share on other sites

2 hours ago, redxz said:

Well, I meant it as a compliment, because it works really well, it's fast and responsive too, I even think its better than the stock ROM.

Quality on officially supported devices varies greatly, too. Sometimes it's just simply about the device maintainer's skills. Sometimes device can have an excellent maintainer but the device is not getting the attention it needs (maybe it's only the fifth device in the maintainer's roster). I've done CM on more than half a dozen devices and Android bring ups on eight (if I counted correctly) new Android version so this really isn't new to me. Some devices could have been official at some point - some not for various reasons. All have been cheap and highly unpopular devices so it's never been worth the hassle. ;) This device wouldn't be accepted because of how Yep/Huawei have butchered the telephony stack.

Of course it's better than stock ROM. :P EMUI sets the bar really low and it doesn't take much to beat that.

Link to comment
Share on other sites

55 minutes ago, KonstaT said:

EMUI sets the bar really low and it doesn't take much to beat that.

Yeah, that bothered me a lot :D It was really boring and took a lot of space.

By the way, do the patches you sent earlier work on CM13 for Y560?

Link to comment
Share on other sites

19 minutes ago, redxz said:

Yeah, that bothered me a lot :D It was really boring and took a lot of space.

By the way, do the patches you sent earlier work on CM13 for Y560?

Actually you need none of the patches that were needed for CM12.1.

You might want to revert this as there was still some issues with SELinux in CM13. You also need to do the same thing with framework.jar and telephony-common.jar to get RIL working (use files from my CM13 build this time).

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.