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

[GLokin666]

I'm busy preparing for ICPC regional and won't start N porting until CAF is fully merged into CM14. As I don't have N proprietary blobs for msm8916, we might have to wait for blobs from other msm8916 devices

Hello, you can use them blobs of the moto g 2015 osprey?
forum.xda-developers.com/2015-moto-g/orig-development/rom-android-source-project-t3457061

Is android N source code.

 

[custon3]

@dianlujitao
They reviewing various configurations for "msm8916:enable core_ctl" the most used values ​​are:/busy_down_thres 30/40 and to /busy_up_thres 60/70

 

[Matiq01]

Have you bug like this: when phone is locked and someone calling, phone start vibration right but screen don't wake up imedietelly, sometimes yes but often must wait somr seconds to wake up and see who calling, sometimes i must click powerbutton to wake up, have you this too ? And battery consumptuon is higher than month ago

Sent from my G620S-L01 using XDA-Developers mobile app

 

[jerryhou85]

Have you bug like this: when phone is locked and someone calling, phone start vibration right but screen don't wake up imedietelly, sometimes yes but often must wait somr seconds to wake up and see who calling, sometimes i must click powerbutton to wake up, have you this too ? And battery consumptuon is higher than month ago

Sent from my G620S-L01 using XDA-Developers mobile app

My phone sometimes indeed a bit slow, but the screen will be up in less than a second.

 

[Zeus Revolution]

@dianlujitao，wait for the honor 4x (che1-cl1) version.

Friend ever have resurrection in our device .... Since the Y550 has it ... Thanks...

---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------

@dianlujitao
They reviewing various configurations for "msm8916:enable core_ctl" the most used values ​​are:/busy_down_thres 30/40 and to /busy_up_thres 60/70

Friend ever have resurrection in our device .... Since the Y550 has it ... Thanks

 

[desalesouche]

carrier config

hi, may be we need a similar commit to fix the missing choice of choosing operator?
https://github.com/UBERROMS/device_huawei_angler/commit/5578e3e072f4aecaa8be0c382571e52fab7ab40e

or does problem come from that we use ons.bins?
this is the "faulty" commit: https://github.com/CyanogenMod/andr...mmit/d2c1ea551ace19606746559b53cf4e401f1dfaf6
thank you.

By the way can you tell me if there is an appropriate java for N? have a good day.

 

[custon3]

Hello, you can use them blobs of the moto g 2015 osprey?
forum.xda-developers.com/2015-moto-g/orig-development/rom-android-source-project-t3457061

Is android N source code.

Here you have more blobs for N-msm8916...
https://github.com/CyanogenMod/android_device_yu_jalebi/tree/cm-14.0?files=1
https://github.com/CyanogenMod/android_device_cyanogen_msm8916-common/tree/cm-14.0?files=1
https://github.com/CyanogenMod/android_device_asus_msm8916-common/tree/cm-14.0?files=1
https://github.com/CyanogenMod/android_kernel_asus_msm8916/tree/cm-14.0?files=1

 

[desalesouche]

cm14.0 camera error

device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp:452:7: error: 'FOCUS_MODE_MANUAL_POSITION' was not declared in this scope
{ FOCUS_MODE_MANUAL_POSITION, CAM_FOCUS_MODE_MANUAL},
^
device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp:516:7: error: 'WHITE_BALANCE_MANUAL_CCT' was not declared in this scope
{ WHITE_BALANCE_MANUAL_CCT, CAM_WB_MODE_CCT},
^
device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp: In member function 'int32_t qcamera::QCameraParameters::setFocusPosition(const qcamera::QCameraParameters&)':
device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp:1979:31: error: 'FOCUS_MODE_MANUAL_POSITION' was not declared in this scope
if (strcmp(focus_str, FOCUS_MODE_MANUAL_POSITION)) {
^
device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp: In member function 'int32_t qcamera::QCameraParameters::setWBManualCCT(const qcamera::QCameraParameters&)':
device/huawei/msm8916-common/camera/QCamera2/HAL/QCameraParameters.cpp:2277:28: error: 'WHITE_BALANCE_MANUAL_CCT' was not declared in this scope
if (strcmp(wb_str, WHITE_BALANCE_MANUAL_CCT)) {
^

@dianlujitao and anyone... hi, may i request some little help about fixing cam with N? thanks .

 

[paranoia_gu]

@dianlujitao

after update the latest code, all cpu core cannot go to sleep.


there are many many logs like this.

09-11 18:35:30.651 412-412/? D/VM_BMS: wake_lock acquired
09-11 18:35:30.651 412-412/? D/VM_BMS: New BMS data - Size=56
09-11 18:35:30.651 412-412/? D/VM_BMS: Start process_bms_data
09-11 18:35:30.656 412-412/? D/VM_BMS: For batt_temp=286 fcc_mah=2994
09-11 18:35:30.656 412-412/? D/VM_BMS: For ocv=3841491 batt_temp=286 soc=51
09-11 18:35:30.656 412-412/? D/VM_BMS: fifo_count=0 acc_count=7
09-11 18:35:30.656 412-412/? D/VM_BMS: INIT: ocv=3841491 last_ocv=3841491 batt_temp=286 soc=51
09-11 18:35:30.656 412-412/? D/VM_BMS: For soc=51 batt_temp=286 slope=5800
09-11 18:35:30.656 412-412/? D/VM_BMS: For soc=51 batt_temp=286 rbatt_sf=96
09-11 18:35:30.656 412-412/? D/VM_BMS: rbatt_mohm_default=146, rbatt_mohm=140, sf=96 batt_temp=286
09-11 18:35:30.657 412-412/? D/VM_BMS: For ocv=3841486 batt_temp=286 soc=51
09-11 18:35:30.657 412-412/? D/VM_BMS: FIFO=0 fifo_avg=3.808299 rbatt=0.190000 slope=0.580000 ibatt=0.174682 ocv=3.841486 soc=51 fcc_ah=2.994000 sample_count=7 sample_interval=70 seq_num=847
09-11 18:35:30.657 412-412/? I/VM_BMS: power_supply_update: ocv_uv=3841486 ibatt=174682 soc=51 seq_num=847
09-11 18:35:30.657 412-412/? D/VM_BMS: End process_bms_data
09-11 18:35:30.658 412-412/? D/VM_BMS: wake_lock released
09-11 18:35:31.643 412-412/? D/VM_BMS: wake_lock acquired
09-11 18:35:31.643 412-412/? D/VM_BMS: New BMS data - Size=56
09-11 18:35:31.643 412-412/? D/VM_BMS: Start process_bms_data
09-11 18:35:31.647 412-412/? D/VM_BMS: For batt_temp=286 fcc_mah=2994
09-11 18:35:31.647 412-412/? D/VM_BMS: For ocv=3841486 batt_temp=286 soc=51
09-11 18:35:31.647 412-412/? D/VM_BMS: fifo_count=0 acc_count=7
09-11 18:35:31.647 412-412/? D/VM_BMS: INIT: ocv=3841486 last_ocv=3841486 batt_temp=286 soc=51
09-11 18:35:31.647 412-412/? D/VM_BMS: For soc=51 batt_temp=286 slope=5800
09-11 18:35:31.647 412-412/? D/VM_BMS: For soc=51 batt_temp=286 rbatt_sf=96
09-11 18:35:31.647 412-412/? D/VM_BMS: rbatt_mohm_default=146, rbatt_mohm=140, sf=96 batt_temp=286
09-11 18:35:31.647 412-412/? D/VM_BMS: For ocv=3841481 batt_temp=286 soc=51
09-11 18:35:31.647 412-412/? D/VM_BMS: FIFO=0 fifo_avg=3.806532 rbatt=0.190000 slope=0.580000 ibatt=0.183956 ocv=3.841481 soc=51 fcc_ah=2.994000 sample_count=7 sample_interval=70 seq_num=848
09-11 18:35:31.648 412-412/? I/VM_BMS: power_supply_update: ocv_uv=3841481 ibatt=183956 soc=51 seq_num=848
09-11 18:35:31.648 412-412/? D/VM_BMS: End process_bms_data
09-11 18:35:31.648 412-412/? D/VM_BMS: wake_lock released

 

[custon3]

@dianlujitao

after update the latest code, all cpu core cannot go to sleep.
View attachment 3871734

there are many many logs like this.

Has yet to add this patch to control the use of cores (enable hotplug).Regards !!
https://review.cyanogenmod.org/160818

 

[desalesouche]

cm-13.0 update

hi all i compiled cm-13.0 update .
let's meet soon on my thread...
http://forum.xda-developers.com/showpost.php?p=68637430&postcount=455
i wanna you test if battery life is better, audio and wifi/data speed.
rom coming soon

 

[paranoia_gu]

Has yet to add this patch to control the use of cores (enable hotplug).Regards !!
https://review.cyanogenmod.org/160818

Applied the patch , but unfortunately all the core are still waking .

Sent from my Nexus 7 using Tapatalk

 

[custon3]

Applied the patch , but unfortunately all the core are still waking .

Sent from my Nexus 7 using Tapatalk

So that the patch works have to install some drivers ..."líne 36 + insmod /system/lib/modules/core_ctl.ko"

 

[paranoia_gu]

So that the patch works have to install some drivers ..."líne 36 + insmod /system/lib/modules/core_ctl.ko"

where can i find the file "core_ctl.ko" ?
it is not in the proprietary files.

 

[custon3]

where can i find the file "core_ctl.ko" ?
it is not in the proprietary files.

I also download the patch and did not see that file "core_ctl.ko". It will take another patch to the kernel (drivers)? and @dian not edited?

 

[desalesouche]

gps logcat

here is logcat done with gps on g620s-L01

 

[Blefish]

Hotplug is not needed, the cores are in low power idle state when they are not used. Just compare power usage, there's not much of a difference. AFAIK even CAF is not using hotplug for 8916 anymore.

Sent from my G620S-L01 using Tapatalk

 

[johnybr99]

Hotplug is not needed, the cores are in low power idle state when they are not used. Just compare power usage, there's not much of a difference. AFAIK even CAF is not using hotplug for 8916 anymore.

Sent from my G620S-L01 using Tapatalk

I understand, but power consumption is huge. I barely get 2 hrs of sot now. It used to be around 4 about 2 months ago.

 

[Blefish]

I understand, but power consumption is huge. I barely get 2 hrs of sot now. It used to be around 4 about 2 months ago.

Does this happen over mobile network? As far as my experience goes, when over mobile network the phone gets really hot and battery empties quite fast. However, over Wi-Fi its more or less ok.

 

[johnybr99]

Does this happen over mobile network? As far as my experience goes, when over mobile network the phone gets really hot and battery empties quite fast. However, over Wi-Fi its more or less ok.

I'm currently in Greece and I get no cellular reception at all. I don't know if it is rom problem or smtg else, but I cannt connect to amy network. But I don't need it. Battery life is bad even on occasional wifi and no cellular reception.