[ROM][Official][Nightly]CyanogenMod 13.0 for Huawei G620S, Honor 4/4x

[AlexSander22]

Hi Guys

There Are No Custom Rom For Huawei Honor 4c ???

 

[jerryhou85]

There Are No Custom Rom For Huawei Honor 4c ???

The chipset of 4c is HUAWEI's HiSilicon Kirin 620... unless they release full support documents, it would be impossible...

 

[cmzcAce]

after installed 0505&0513-NIGHTLY-cherry from a earlier CM13 version, the front camera in "video chat function" have some problem in app wechat and QQ: even I am in bright room,the other party see me in a very dark space---- barely see a clear face. Honor 4/4x. pls help.

 

[Moreg90]

@dianlujitao Do you think that commit might help about slow charging?
https://github.com/G620S-CHERRY/and...mmit/c9e79db85411c61d5a399b3cf6eebb3b5e502aa6

Any news about that?
My phone takes more than one hour to charge from 90% to 100% with an 2A charger and sometimes battery percentage goes down suddenly! The full charge takes about 4 hours!
I think they are the major issues of that rom for g620s-l01.

 

[el_charlie]

Does the provided baseband is necessary on a G620-L03? Does it affect the frequency bands? How do I backup the current baseband?

Thanks!

 

[Moreg90]

I'm sorry but I don't know, I didn't make a backup of my baseband, I found the original one on xda!

Anyway I noticed that using the phone always with Wi-Fi I can do about 5 hours with the screen on, while using only mobile network (LTE) it lasts only 3 hours. With the stock emui (with obviously stock baseband) it lasts at least 4 hours with LTE.
This means that the power consumption is higher with other baseband instead the stock one! The difference of 2 hours between with or without Wi-Fi can't be caused by the android system or by the screen!

 

[xd34]

I know that there isn´t any support for NFC because Huawey doesn´t provide source code for the Chip in our devices. OK, there are only propietary drivers and this ROM only supports free code. But in the same way we have to apply a .zip for instaling Google Apps, It would be possible to create a 'patch' with the provided drivers (I don´t know: nfc_nci.msm8916.so / nfc_nci_pn547.default.so ... ) and reconfigurated files (.cgf, .prop or something) in order to use this feature?? I would accept a disclaimer with this exception.

 

[custon3]

When entering the privacy settings for some applications (browser, etc),stops the application settings!
nightly 18052016 device g620s-l01

 

[desalesouche]

I know that there isn´t any support for NFC because Huawey doesn´t provide source code for the Chip in our devices. OK, there are only propietary drivers and this ROM only supports free code. But in the same way we have to apply a .zip for instaling Google Apps, It would be possible to create a 'patch' with the provided drivers (I don´t know: nfc_nci.msm8916.so / nfc_nci_pn547.default.so ... ) and reconfigurated files (.cgf, .prop or something) in order to use this feature?? I would accept a disclaimer with this exception. [/QUOTE @Blefish will be soon back to work on g620s and with his kernel + device tree, he has nfc working for g620s device... some patience is necessary.

 

[nightwalkerkg]

Blefish will be soon back to work on g620s and with his kernel + device tree, he has nfc working for g620s device... some patience is necessary.

Actually with his device tree i was only able to enable NFC, if i tried to send something over it would crash. Not sure if it was because of my build or his device tree, but i think it will need more fixes to work like it should.

 

[desalesouche]

Actually with his device tree i was only able to enable NFC, if i tried to send something over it would crash. Not sure if it was because of my build or his device tree, but i think it will need more fixes to work like it should.

i guess Blefish will fix that.

 

[Matiq01]

Any fix for slow charging on g620s-L01 ?

 

[xd34]

I know that there isn´t any support for NFC because Huawey doesn´t provide source code for the Chip in our devices. OK, there are only propietary drivers and this ROM only supports free code. But in the same way we have to apply a .zip for instaling Google Apps, It would be possible to create a 'patch' with the provided drivers (I don´t know: nfc_nci.msm8916.so / nfc_nci_pn547.default.so ... ) and reconfigurated files (.cgf, .prop or something) in order to use this feature?? I would accept a disclaimer with this exception.

@Blefish will be soon back to work on g620s and with his kernel + device tree, he has nfc working for g620s device... some patience is necessary.

So good news! Thanks to you, Blefish and all the people working on this.

 

[GLokin666]

Hello @dianlujitao cm13 20160520 rom is restarted and to rom does not work
I have seen that there are changes in the sensors... May be that the problem?? ����

Best regards

 

[Panda7991]

Hello I have Honor 4x indian version which is che-l04 will it work on my device ?

I have Honor 4x che-l04 will it work for my device?? And is this stable rom ??

 

[jerryhou85]

I have Honor 4x che-l04 will it work for my device?? And is this stable rom ??

Please read the first post, you are welcome.
Supported device:

C8817D
C8817E
G620S-UL00
G620S-L01/L02/L03
G621-TL00
Che1_CL10
Che1_CL20
Che1_L04

 

[EccTM]

Hey @dianlujitao, I just installed cm-13.0-20160521-NIGHTLY-cherry.zip on my G620S-L01, and my phone is rebooting randomly. Sometimes it doesn't make it past the boot animation, other times I can use it for 10 minutes and then it suddenly restarts. I didn't have any issues with 20160502, but I haven't used any of the nightlys between them to pinpoint when the problem was introduced... Is anyone else having these issues, and what logs can we provide to help debug this?

 

[desalesouche]

Hey @dianlujitao, I just installed cm-13.0-20160521-NIGHTLY-cherry.zip on my G620S-L01, and my phone is rebooting randomly. Sometimes it doesn't make it past the boot animation, other times I can use it for 10 minutes and then it suddenly restarts. I didn't have any issues with 20160502, but I haven't used any of the nightlys between them to pinpoint when the problem was introduced... Is anyone else having these issues, and what logs can we provide to help debug this?

i have also issue i can say for now that kernel change seem not to be the problem. will try to see if jalebi vendors are the problem.

 

[EccTM]

i have also issue i can say for now that kernel change seem not to be the problem. will try to see if jalebi vendors are the problem.

I rolled back to the 20160519 nightly and I haven't had any issues. Have you got a build without the jalebi blobs commit that I could try?

EDIT: I ended up rolling back to 20160502 because the 20160519 nightly was rebooting when receiving a call, and occasionally wouldn't wake up via lock button for some reason.

 

[dianlujitao]

i have also issue i can say for now that kernel change seem not to be the problem. will try to see if jalebi vendors are the problem.

IDK, I undo all recent device/kernel/vendor change and built with latest cm13 code, it's still crashy.
Unfortunately, I'm not able to get any useful log.

PS: if some people have ideas you can contact me on telegram: dianlujitao