yashsingh1/xdaforums huggingface dataset:
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] user_x25:
You are awesome!
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] StarSix01:
Congratulations!!!!!!!!!!! You are awesome dude;)
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
Maybe it's time to provide a flashable zip to collect logs from other devices... And brave testers :p

I just made a backup this afternoon
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] user_x25:
[MENTION=5532236]nexolight[/MENTION] If you want i can test the rom.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
you are great, my congratulations to you
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Guys do you even read? There's nothing to test yet ;)

You will be stuck with a black scren after the bootlogo. With some luck you may once see the welcome screen for a short time. The logs aren't the problem at the moment ( Ihave enough of them ). No I can't provide a flashable zip cm doesn't let me build it. I could provide the img files (flashing via fastboot). However I'd have to rebuild them with the proper build informations included. Maybe 3-4 Hours of work. To much for that. At the moment this is devloper stage only. I could however update my git. It isn't always up to date since I do my tests without rebuilding everything each time.

I'd say expect ~2 weeks until I get past that. Probably less but who knows.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] user_x25:
Okay dev, take your time, we can wait as much as you want ;)
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
So managed to make a picture. I hope It wasn't just once. Screen goes dark after screen timeout and doen't come back. Probably because the buttons/touchscreen does not work. Or because it freezes. Well just came to that... let's debug this further:

[IMG="Welcome"]http://dl-1.va.us.xda-developers.com/3/8/7/3/8/0/8/_1.jpg?key=eekYQVOC-jhXUsRFCH6T_g&ts=1473765147[/IMG]

Hope I can press this next button soon ;) ~Git it updated with this state.

Edit: this seems to be still a rare not really reprocutable occurence.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] user_x25:
Thank you so much for your work. Good luck!
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
No news yet. However I set up a second build environment. For now:

Download TWRP 3.0.2 GRA-L09

Please note that I'm not responsible for any damage. Flash this like:

For me it is functional with the bug that you have to wait until the screen times out once. Then it reacts.

This is the recovery not a rom
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
Is this recovery version mandatory? I already have a fully functional TWRP 3.x
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Naa it's not. That's just a side product. Every recovery is fine which is able to save & restore the system and boot partition. Doesn't really matter. I didn't know there's one already there for download.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Someone who can decompile that? I'm new to this (Manual):

| ;-- HwcPartialUpdates::UpdateSourceLayer:
| 0x0001d564 stp x29, x30, [sp, -0xa0]!
| 0x0001d568 mov x29, sp
| 0x0001d56c stp x21, x22, [sp, 0x20]
| 0x0001d570 add x21, x29, 0x50
| 0x0001d574 mov x22, x0
| 0x0001d578 stp x19, x20, [sp, 0x10]
| 0x0001d57c mov x0, x21
| 0x0001d580 mov x20, x1
| 0x0001d584 stp x23, x24, [sp, 0x30]
| 0x0001d588 bl sym.android::Region::Region
| 0x0001d58c movz x19, 0
| 0x0001d590 ldr x0, [x20, 0x40] ; [0x40:4]=1 ; '@'
,==< 0x0001d594 cbz x0, 0x1d5cc
.---> 0x0001d598 ldr x3, [x20, 0x48] ; [0x48:4]=0 ; 'H'
||| 0x0001d59c lsl x2, x19, 4
||| 0x0001d5a0 mov x0, x21
||| 0x0001d5a4 add x19, x19, 1
||| 0x0001d5a8 add x4, x3, x2
||| 0x0001d5ac ldr w1, [x3, x2]
||| 0x0001d5b0 ldr w2, [x4, 4] ; [0x4:4]=0x10102
||| 0x0001d5b4 ldr w3, [x4, 8] ; [0x8:4]=0
||| 0x0001d5b8 ldr w4, [x4, 0xc] ; [0xc:4]=0
||| 0x0001d5bc bl sym.android::Region::addRectUnchecked
||| 0x0001d5c0 ldr x1, [x20, 0x40] ; [0x40:4]=1 ; '@'
||| 0x0001d5c4 cmp x1, x19
`===< 0x0001d5c8 b.hi 0x1d598
`--> 0x0001d5cc add x19, x29, 0x78
| 0x0001d5d0 mov x0, x21
| 0x0001d5d4 mov x8, x19
| 0x0001d5d8 mov x1, x22
| 0x0001d5dc bl 0x12770
| 0x0001d5e0 ldr x6, [x29, 0x88]
| 0x0001d5e4 ldr x5, [x29, 0x80]
| 0x0001d5e8 sub x7, x6, 1
| 0x0001d5ec lsl x8, x7, 4
| 0x0001d5f0 add x9, x5, x8
| 0x0001d5f4 ldr w10, [x5, x8]
| 0x0001d5f8 ldr w11, [x9, 8] ; [0x8:4]=0
| 0x0001d5fc ldr w12, [x9, 4] ; [0x4:4]=0x10102
| 0x0001d600 sub w13, w11, w10
| 0x0001d604 ldr w14, [x9, 0xc] ; [0xc:4]=0
| 0x0001d608 cmp w13, wzr
,==< 0x0001d60c b.le 0x1d66c
|| 0x0001d610 sub w15, w14, w12
|| 0x0001d614 cmp w15, wzr
,===< 0x0001d618 b.le 0x1d66c
||| 0x0001d61c add x23, x29, 0xa0
||| 0x0001d620 mov x1, x22
||| 0x0001d624 ldp x16, x17, [x20, 0x30]
||| 0x0001d628 stp x16, x17, [x23, -0x60]!
||| 0x0001d62c mov x0, x23
||| 0x0001d630 mov x2, x23
||| 0x0001d634 bl sym.android::Rect::intersect
||| 0x0001d638 uxtb w24, w0
,====< 0x0001d63c cbnz w24, 0x1d674
|||| 0x0001d640 movz w24, 0x1
..-----> 0x0001d644 mov x0, x19
|||||| 0x0001d648 bl sym.android::Region::_Region
|||||| 0x0001d64c mov x0, x21
|||||| 0x0001d650 bl sym.android::Region::_Region
|||||| 0x0001d654 mov w0, w24
|||||| 0x0001d658 ldp x19, x20, [sp, 0x10] ; [0x10:4]=0xb70003
|||||| 0x0001d65c ldp x21, x22, [sp, 0x20] ; [0x20:4]=64 ; "@" 0x00000020
|||||| 0x0001d660 ldp x23, x24, [sp, 0x30] ; [0x30:4]=0 ; '0'
|||||| 0x0001d664 ldp x29, x30, [sp], 0xa0
|||||| 0x0001d668 ret
|||``--> 0x0001d66c movz w24, 0
`======< 0x0001d670 b 0x1d644
|`----> 0x0001d674 mov x0, x22
| | 0x0001d678 mov x1, x20
| | 0x0001d67c mov x2, x23
| | 0x0001d680 bl 0x12fe0
| | 0x0001d684 mov x0, x22
| | 0x0001d688 mov x1, x20
| | 0x0001d68c mov x2, x23
| | 0x0001d690 bl 0x13dc0
`=====< 0x0001d694 b 0x1d644
| 0x0001d698 ret
`=< 0x0001d69c b sym.operatordelete

If fails at 0x1d5ac (SEGFAULT)
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] GodzillaMonster:
To me it looks like the segv is caused by reading physical address 255.

The particular line is in a loop reading values using an offset table .. it is most likely the loop end condition is not being satisfied (it's counting in register x19 and comparing that value with whatever is at 0x7f7b468788 + 0x40).. it gets to 12 iterations and then it seems to be pointing to something wobbly rather than something good.

Sorry that's not much help - it's easier to see when debugging (with appropriate breakpoints).
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Maybe this is more helpful :) I guess you were pretty accurate.

__int64 __fastcall HwcPartialUpdates::UpdateSourceLayer(__int64 a1, _QWORD *a2)
{
__int64 v2; // x22@1
_QWORD *v3; // x20@1
unsigned __int64 v4; // x19@1
signed __int64 v5; // x2@2
__int64 v6; // x8@3
__int64 v7; // x17@5
unsigned int v8; // w24@5
__int64 v10; // [xsp+40h] [xbp+40h]@5
__int64 v11; // [xsp+48h] [xbp+48h]@5
__int64 v12; // [xsp+50h] [xbp+50h]@1
__int64 v13; // [xsp+78h] [xbp+78h]@7
__int64 v14; // [xsp+80h] [xbp+80h]@3
__int64 v15; // [xsp+88h] [xbp+88h]@3

v2 = a1;
v3 = a2;
android::Region::Region((android::Region *)&v12);
v4 = 0LL;
if ( v3[8] )
{
do
{
v5 = 16 * v4++;
android::Region::addRectUnchecked(
(android::Region *)&v12,
*(_DWORD *)(v3[9] + v5),
*(_DWORD *)(v3[9] + v5 + 4),
*(_DWORD *)(v3[9] + v5 + 8),
*(_DWORD *)(v3[9] + v5 + 12));
}
while ( v3[8] > v4 );
}
android::Region::intersect(&v12, v2);
v6 = 16 * (v15 - 1);
if ( *(_DWORD *)(v14 + v6 + 8) - *(_DWORD *)(v14 + v6) <= 0
|| *(_DWORD *)(v14 + v6 + 12) - *(_DWORD *)(v14 + v6 + 4) <= 0 )
{
v8 = 0;
}
else
{
v7 = v3[7];
v10 = v3[6];
v11 = v7;
v8 = (unsigned __int8)android::Rect::intersect(&v10, v2, &v10);
if ( v8 )
{
HwcPartialUpdates::UpdateSourceCrop(v2, v3, &v10);
HwcPartialUpdates::UpdateDisplayFrame(v2, v3, &v10);
}
else
{
v8 = 1;
}
}
android::Region::~Region((android::Region *)&v13);
android::Region::~Region((android::Region *)&v12);
return v8;
}
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] GodzillaMonster:
:) it is pretty much the same, yes.

I'm not sure what control you have over this code. but you can probably safely skip that loop if you want to see what happens after it. You need to replace the 0x0001d594 cbz x0, 0x1d5cc with 0x0001d594 cbnz x0, 0x1d5cc to do that.

If you only have a binary blob, you can try doing it in a hex editor using techniques like the ones mentioned here: http://stackoverflow.com/questions/9279451/armv7-word-patch-cbnz
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Not sure if that is a good idea.. when attaching the debugger the animation moves each time a little bit when this loop is executed. It will probably just freeze the screen when I'd skip it. It also runs fine up to exactly that point where the ui would be displayed. Sometimes the first frame is displayed. The function is vendor specific and called by the library itself but I assume it accesses the hwc_layer_1 from frameworks/native/services/surfaceflinger/DisplayHardware/HWComposer.cpp and that pointer *a2 refers to the instance of it.

Could it be that the hwc_layer_1 was recreated and that after this the pointer refers to some bad location?

This happens right before the segfault:

From HWcomposer.h

struct DisplayData {
DisplayData();
~DisplayData();
Vector<DisplayConfig> configs;
size_t currentConfig;
uint32_t format; // pixel format from FB hal, for pre-hwc-1.1
bool connected;
bool hasFbComp;
bool hasOvComp;
size_t capacity;
hwc_display_contents_1* list;
[B] hwc_layer_1* framebufferTarget;[/B]
buffer_handle_t fbTargetHandle;
sp<Fence> lastRetireFence; // signals when the last set op retires
sp<Fence> lastDisplayFence; // signals when the last set op takes
// effect on screen
buffer_handle_t outbufHandle;
sp<Fence> outbufAcquireFence;

// protected by mEventControlLock
int32_t events;
};

Ok. I have no clue about pointers in deep I primary work with java, python and js and have coded some robots in a cropped C version.

Edit: I have access to the hwcomposer source code provided by google. However this one is meant to be implemented by the vendor so it's not that helpful. Their version is huge. However I have controll over the code which is probably the cause for this. It would be the very last option to change the machine code with a hex editor.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lataldragon:
I wish all the luck in the world that you can do it . That would be a sensation in the world P8 ;) :D
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
I guess it's because of SafetyNet check, not a rom failure. You can try Magisk.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Gfhoihoi72:
When I install Magisk and run the SafetyNet test it says CTS profile mismatch, but it also said that on my previous rom (which wasn't stock btw, I used the Arrow 6.0 rom with Magisk).

But on that rom the NFC payment worked fine. So I don't think it's SafetyNet causing the issue. But I can be wrong of course.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
Magisk safetynet test says the same to me but I can play pokemongo which relies on the same check used for androidpay.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Gfhoihoi72:
Hmm okay, I will try if it works now with Magisk installed.

Also I found something weird I think. Maybe you know already, but when I set youtube to play 60fps and look at the processor usage, the "mediaserver" process is using almost all of the CPU.

As far as I know the mediaserver only scans the file system for media files. Why would it be doing that when playing a YouTube video? It isn't used for the codecs right? Sorry if I'm very wrong, but maybe it can help you fixing the problem.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
Remember you have to enable magiskhide for your payment apps in magisk settings
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
Is magisksu working for you? I don't get any prompts to grant or deny root access :P
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Gfhoihoi72:
I tried it just now, but still not working. If I hold it up to the payment terminal thing just nothing happens :(

Yes it's working just fine for me. Do you have any other SU app installed? Also be sure the Magisk Manager app can't be closed automatically when you turn your screen off for example. When the app isn't running you won't get any prompts.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
No other su apps. Just flashed the zip and installed apk. I added exception in battery optimisation also but no prompt.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Gfhoihoi72:
Maybe you can try installing it again within the Magisk app. That's the way I did it and it works perfectly as you can see below.

Maybe it doesn't detect the proper boot image location, like it does in the app, when installing the zip?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
So did you change any settings or just straight installed it within the app?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Gfhoihoi72:
Nope, just the auto detected boot location and everything unticked. Be sure to uninstall your previous one first by flashing the uninstaller zip, I don't know what happens when you install it in different locations if it does that.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
I won't do any app ports.

There is probably a fix for any other cam app (apart from footej) from AD2076 at the lineage branch as well as one for the buttons.

I had no time to take them over so far.

About the battery monitoring:

I don't know a specific one but there's probably no need for that.

When I check it I will check the cpu settings and when it's not caused by that then there's not much I could do.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
No fix for camera, yet.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
I worked 5h to review and take over changes from the lineage13 branch to the one from this rom. AD2076 did quite a lot there.

It might take some more time for fine tuning but it should help with a few things.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
Fantastic,great news
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Yagogr98:
Great!

Enviado desde mi HUAWEI GRA-L09 mediante Tapatalk
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Hm seems that the issues with the battery drain in standby is primary caused by the processes thermal-daemon, hw_ueventd and perfhub. Not sure about hw_ueventd anymore but the rest are from the stock rom. There are a few more which eat up cpu time but they are cm system processes. I will try to disable them and look at it again.

cm should have a built in way to prevent overhating (not sure), perfhub is eventually not required at all.

Edit:

disabled hw_ueventd which got replaced by ueventd (cm) afterwards

disabled perfhub

disabled thermal-daemon

no downsides so far. I will let it run for a while.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] dnovoa20:
thanks, great job
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
Is there any downsides so far? How much improvement?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
No downsides so far. Tested camera and gps. hw_ueventd came into place with some usb stuff but that seems also fine as far as I can tell.

I'd say it's a 30-50% standby improvement on my device. Note that this is just my feeling about that.

I couldn't run it more than 1 day in standby but with that battery curve it should be aprx. 36h.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
That sounds good
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
A question to all . Does anyone have warming problems after watching videos?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Ok the new build is up. Please read the changelog.

I cannot confirm everything.

A lot was taken from the Lineage 13 branch from AD2076.

Some stuff was applied 1:1 and some was altered.

If Windows is freaking out about USB tethering (what it always did for any device) make sure to manually install the Microsoft "NDIS compatible remote device" driver for the RNDIS device in the device manager. It is not listed under compatible drivers but you won't experience any UI lags when dealing with the network config in Windows anymore.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] shangzhang:
I am currently on AD2076's Lineage 13. Can I just flash this updated system.img? Do I need to reinstall Gapps?

Thanks a lot for this update.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Gapps are installed in the system partiton. Yes you need to reinstall them.

Also you should flash system.img and boot.img as they were both updated.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Ink Rampant Wolf:
What's working and what is not? Is there any way to flash the camera app of the stock firmware?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
Is all detailed in the main post, works almost everything except fm radio and some freeze on youtube. The camera works fine except for recording videos but you can use the footej application. In the last build has included improvements of lneage branch and goes quite well with control of LED notifications and some improvements in battery and more. Everything is written in the post.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] ruskooo:
but phorto still are lower quality than from the stock one?

This is main thing that i go back to stock firmware becuase i buyed this phone for camera :), how i remember in cm13 the sound in headphone was much more louder than the stock one with viper
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Maybe one day there will be a camera wrapper for more options but the stock camera app will never happen.. This is most certainly tied together with a lot of their framework stuff. CM is clearly not about taking the stock framework.

I personally don't like these software improvement and postprocessing. It is going to be edited afterwards anyway. But when you do, you better keep a stock based rom.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
Can I flash this rom on the rom custom arrow?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
If you can, I flash arrow to cm
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
I get an error when trying to flash the system.img and I do not know why, I need help on how to install this Rom CM13, I'm using Windows 10
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
I flash this ROM both in gratitude version and in arrow and I had no problem. Try to download again system.img in case I fail something, what exact problem tells you when you try to flash
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
I do not speak English so I do not understand much what I said on the ADB screen, but it said something like the system.img was very big or heavy or something like that
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
Target reported max download size...?

If it is if you have to wait for the system to be installed. It takes a few minutes.

Did you do wipes? There is a step by step in the post
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
C:\Users\DarioCristobal\Desktop\Herramientas Modo Fastboot>fastboot devices

S7M7N15814009637 fastboot

C:\Users\DarioCristobal\Desktop\Herramientas Modo Fastboot>fastboot flash boot boot.img

sending 'boot' (23668 KB)... OKAY

writing 'boot'... OKAY

C:\Users\DarioCristobal\Desktop\Herramientas Modo Fastboot>fastboot flash system system.img

sending 'system' (926709 KB)... FAILED (remote: data too large)

C:\Users\DarioCristobal\Desktop\Herramientas Modo Fastboot>

This is what happens every time I try to flash CM13
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
May be failing fastboot tool, i use minimal adb and fastboot
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
Please if you could provide me the link of adb tools?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
It is most likely due to the fastboot tool you use, download minimal adb and fastboot: https://xdaforums.com/showthread.php?t=2317790

pass boot and system to folder where this minimal adb and fastboot, it starts the executable that you will have in the desk and flash normally
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
Efectivale was the tool adb, I am very grateful my brother, and it is installed at last, the only thing you notice is that wake with double tap is not working

---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------

Wake up the screen with double tap is not working
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
Congratulations friend, double tap to wake up still not working the developers are working on it
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
Excellent news, hopefully you can implement the double touch soon to wake the screen, I'm very grateful my brother
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] lespaul79:
Friend I am very glad to have helped you but this magnificent ROM is due to its developers [MENTION=5532236]nexolight[/MENTION] and [MENTION=6233909]AD2076[/MENTION]
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
So it is my brother, very grateful to his [MENTION=5532236]nexolight[/MENTION] and @ AD2076 developers for such a magnificent rom, they are the maximum, I only wish it possible to use the double touch to wake the screen and I would be very happy

---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------

So it is my brother, very grateful to his [MENTION=5532236]nexolight[/MENTION] and [MENTION=6233909]AD2076[/MENTION] developers for such a magnificent rom, they are the maximum, I only wish it possible to use the double touch to wake the screen and I would be very happy
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] AD2076:
Dt2w needs a custom powerhal not included in this build atm.
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] darito30:
Hello [MENTION=6233909]AD2076[/MENTION] thank you very much my brother, you think it possible to include it in an upcoming update ...?

Very grateful to you and [MENTION=5532236]nexolight[/MENTION] for this fantastic Rom CM13
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] zlihtar2:
Signal strength

Dear Nexolight, to me, signal strength (in status bar) is not working. He always shows one line and does not move. Any solutions?

regards,
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] danyp8:
Ma perché non fate in modo che si installi la rom da recovery?Senza usare il computer?
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] :
That was a know bug but works ok now for at least me
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] Xda mdq:
Flickering

:confused:

Problem:

I tried this rom many times starting from different official marshmallow such as b394, b391 and b321 but the flickering of the screen it persist.

Can you help me please

I have a huawei p8(GRA-L09)… i tried to disable the HW overlay and flickering is decrease but when i increase the amount of operations the flickering return

:confused::confused:
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
What exactly do you mean by "flickering"?

I most likely can't help much when I can't reproduce the issue. It sounds almost like a hardware issue to me. Is it the same with other custom roms or any stock rom? Could it be that the brighness sensor has issues and the screen just adjusts to lux value? (Try to disable automatic screen brightness)
[Huawei P8 ROMs, Kernels, Recoveries, & Other Devel] nexolight:
Have you tried moving close to a cell from your provider?

It does work for me but it might be displayed a bit less than it actually is. maybe 1 bar~? Not sure. It's not adjusted perfectly.