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

[Zeus Revolution]

congratulation!

Good Friends Luck, hopefully web Android N.......

---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------

Good job!

Good Friends Luck, hopefully we Android N.......

---------- Post added at 11:05 AM ---------- Previous post was at 11:02 AM ----------

congratulation!

Good Friends Luck, hopefully we Android N.......

 

[paranoia_gu]

Here we get something new *sigh*

good news.[emoji111] [emoji111] [emoji111]

通过我的 Che1-CL10 上的 Tapatalk发言

 

[johnybr99]

Here we get something new *sigh*

Congrats man ! I hope marshmallow issues will soon be completely fixed. Cheers

 

[desalesouche]

Here's an experimental TWRP build with CAF N kernel + Linux3.10.103 + latest f2fs-stable, just for testing purpose: https://www.androidfilehost.com/?fid=24727332921017146

Source code already available on my github

what about adding modem to backup partitions in twrp?
/firmware vfat /dev/block/bootdevice/by-name/modem flags=backup=1

 

[GLokin666]

Cyanogenmod13

Hi @dianlujitao you removed the mpdecision the nuclei are 800 MHz at the same time, you can leave them at 400 mhz?

 

[Zeus Revolution]

TWRP 3.0.2-0

Good friend, a question , install the twrp3.0.2-0_cherry_f2fs_v3 ( dianlujitao ) to put f2fs partitions , managed to mount all say the statutes , including system , but when I go to install the gaps tells me that can not be mounted in system as a matter of space .... oh something like that be the problem ?? I am installing the nano ... Thanks in advance .....

 

[jerryhou85]

Good friend, a question , install the twrp3.0.2-0_cherry_f2fs_v3 ( dianlujitao ) to put f2fs partitions , managed to mount all say the statutes , including system , but when I go to install the gaps tells me that can not be mounted in system as a matter of space .... oh something like that be the problem ?? I am installing the nano ... Thanks in advance .....

If you are doing a clean install, I sugges you format /system before you flash system and gapps. You can do that in TWRP Advance Wipe menu.

 

[johnybr99]

I was hoping that the latest telephony update would fix inability to connect to other network providers

 

[desalesouche]

I was hoping that the latest telephony update would fix inability to connect to other network providers

fixed in my latest rom.
thanks to dianlujitao with some cm-14.0 commits he did.
check here: http://forum.xda-developers.com/showpost.php?p=68760516&postcount=486
will upload new kernel to flash on it.

 

[johnybr99]

fixed in my latest rom.
thanks to dianlujitao with some cm-14.0 commits he did.
check here: http://forum.xda-developers.com/showpost.php?p=68760516&postcount=486
will upload new kernel to flash on it.

Thanks man. But it's a bit of hassle to install unofficial release. I have to clean install, and that's a process. Any chance your fixes make it's way to the official release? Congrats btw

 

[desalesouche]

Thanks man. But it's a bit of hassle to install unofficial release. I have to clean install, and that's a process. Any chance your fixes make it's way to the official release? Congrats btw

if you where following change you would knew that know dian is using perfd solution instead mdpdecision.. so no more need to do clean install...

 

[Zeus Revolution]

If you are doing a clean install, I sugges you format /system before you flash system and gapps. You can do that in TWRP Advance Wipe menu.

Thanks friend , but formatting system partition is returned to EXT4 , that's normal ?? That is not left in f2fs format ....

 

[custon3]

Thanks friend , but formatting system partition is returned to EXT4 , that's normal ?? That is not left in f2fs format ....

System only works in ext4.Data and Cache are working in f2fs ...

 

[johnybr99]

if you where following change you would knew that know dian is using perfd solution instead mdpdecision.. so no more need to do clean install...

I've just tried your rom and the problem with networks persists.

 

[desalesouche]

I've just tried your rom and the problem with networks persists.

Sorry my bad, will upload soon rom with fix... please feed back for future post on my thread. thanks

 

[rjrajeev]

I installed this ROM..but I am not getting LTE network for one network(Jio) but am getting reception in stock ROM.. anyway to fix it???

Sent from my Che1-L04 using Tapatalk

 

[TechVenom]

What problems do you guys have with CM13? I was using Mokkee 6.0.1 until yesterday, and i have decided to install CM13 instead, and now i'm using CM13, all cores are working, no battery drain, so i don't know what is a problem with this rom....

 

[desalesouche]

ARM: dts: msm: Enable RTC write and alarm powerup on 8916 ?
https://github.com/tarunkapadia93/kernel_test/commit/09d35f6c1667bb88215eb91d40b7479fb961fdb4
https://android.googlesource.com/ke...ation/devicetree/bindings/rtc/qpnp-rtc.txt#28

qcom,qpnp-rtc-alarm-pwrup: This property enables/disables feature of
powering up phone (from power down state)
through alarm interrupt.
If not mentioned rtc driver will disable
feature of powring-up phone through alarm.

is that possible for our msm8916 devices?

---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------

ARM: dts: msm: Enable RTC write and alarm powerup on 8916 ?
https://github.com/tarunkapadia93/kernel_test/commit/09d35f6c1667bb88215eb91d40b7479fb961fdb4
https://android.googlesource.com/ke...ation/devicetree/bindings/rtc/qpnp-rtc.txt#28

qcom,qpnp-rtc-alarm-pwrup: This property enables/disables feature of
powering up phone (from power down state)
through alarm interrupt.
If not mentioned rtc driver will disable
feature of powring-up phone through alarm.

is that possible for our msm8916 devices?

@dianlujitao
yes it is possible! :laugh:
here is my commits :
https://github.com/G620S-HUAWEI/and...mmit/093ca8cf1a722aa7e4664b2c52c39b3db44dc43b

added that file: https://github.com/CyanogenMod/andr...0ace4aa86/rootdir/etc/init.qcom.early_boot.sh
and did change here: https://github.com/CyanogenMod/andr...22c30ace4aa86/rootdir/etc/ueventd.qcom.rc#L37
/dev/rtc0 0660 system system

So now when device is off, it will wake up about 3 minutes before alarm have to wake you up or warn you that it is time!

nice job with your cm-14.0 commits. ^^ ported to cm-13.0 !

kernel test here. can be flashed on top of official cm-13.0
http://forum.xda-developers.com/showpost.php?p=68817777&postcount=520

 

[dianlujitao]

ARM: dts: msm: Enable RTC write and alarm powerup on 8916 ?
https://github.com/tarunkapadia93/kernel_test/commit/09d35f6c1667bb88215eb91d40b7479fb961fdb4
https://android.googlesource.com/ke...ation/devicetree/bindings/rtc/qpnp-rtc.txt#28

qcom,qpnp-rtc-alarm-pwrup: This property enables/disables feature of
powering up phone (from power down state)
through alarm interrupt.
If not mentioned rtc driver will disable
feature of powring-up phone through alarm.

is that possible for our msm8916 devices?

---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------


@dianlujitao
yes it is possible! :laugh:
here is my commits :
https://github.com/G620S-HUAWEI/and...mmit/093ca8cf1a722aa7e4664b2c52c39b3db44dc43b

added that file: https://github.com/CyanogenMod/andr...0ace4aa86/rootdir/etc/init.qcom.early_boot.sh
and did change here: https://github.com/CyanogenMod/andr...22c30ace4aa86/rootdir/etc/ueventd.qcom.rc#L37
/dev/rtc0 0660 system system

So now when device is off, it will wake up about 3 minutes before alarm have to wake you up or warn you that it is time!

nice job with your cm-14.0 commits. ^^ ported to cm-13.0 !

kernel test here. can be flashed on top of official cm-13.0
http://forum.xda-developers.com/showpost.php?p=68817777&postcount=520

Test this patch instead http://review.cyanogenmod.org/163440
On CM14 the device can be waked but bootloops:

01-01 22:56:06.365  1465  1481 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
01-01 22:56:06.365  1465  1481 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.Bundle android.content.IContentProvider.call(java.lang.String, java.lang.String, java.lang.String, android.os.Bundle)' on a null object reference
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at cyanogenmod.providers.CMSettings$NameValueCache.getStringForUser(CMSettings.java:242)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at cyanogenmod.providers.CMSettings$System.getStringForUser(CMSettings.java:516)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at cyanogenmod.providers.CMSettings$System.getIntForUser(CMSettings.java:561)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at com.android.server.policy.PhoneWindowManager.updateKeyAssignments(PhoneWindowManager.java:2108)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at com.android.server.policy.PhoneWindowManager.init(PhoneWindowManager.java:1900)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at com.android.server.wm.WindowManagerService$4.run(WindowManagerService.java:935)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at android.os.Handler$BlockingRunnable.run(Handler.java:771)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:751)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:95)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:61)
01-01 22:56:06.365  1465  1481 E AndroidRuntime: 	at com.android.server.ServiceThread.run(ServiceThread.java:46)

Anyway, it should work on CM13

 

[jerryhou85]

What problems do you guys have with CM13? I was using Mokkee 6.0.1 until yesterday, and i have decided to install CM13 instead, and now i'm using CM13, all cores are working, no battery drain, so i don't know what is a problem with this rom....

Someone reports that battery drain is too fast... But what I see is totally device/model specific.