yashsingh1/xdaforums huggingface dataset:
[Huawei Mate 9 Questions & Answers] cr2:
GPS has little in common with the kernel source, because it is controlled by the userspace daemon /vendor/bin/glgps4774 which you need to trace, disassemble, reverse engineer, etc.

Having an own custom kernel makes this task easier, because you potentiallly can run a standalone debian distro, without being disturbed by android crashing zygote, selinux and things like that.

---------- Post added at 05:53 PM ---------- Previous post was at 05:39 PM ----------

Mate9 has a /dev/block/sdd34 UFS partition labeled 'DTS_A' which has a 4096 header (with digital signature ?) and then the 61 gzip-compressed board DTBs

(debug boards, VICTORIA, VICKY, MHA, LON, DUKE, CMB).

Huawei forgot, or did not want to include the original .dts(i) into the kernel source tree. It is not a big problem,

because the DTB can be easily decompiled into DTS (but with some information loss, mostly readability and convenience).

MHA_TUGL_VN2 is one of then, which is probably picked from OEMINFO based on board ID or something similar:

hi3660_udp_EVB8_VERD_ET
hi3660_udp_EVB8_VERD
hi3660_udp_default
hi3660_udp_EVB8_VERC
hi3660_udp_UFS_only
hi3660_udp_EVB2_VERA
hi3660_udp_EVB8_VERC_DSDA
hi3660_udp_EVB2_VERB
hi3660_udp_EVB2_VERC
hi3660_fpga_010
hi3660_udp_EVB8_VERD_v120
hi3660_udp_v120
hi3660_udp_EVB8_VERD_ET_v120
hi3660_udp_EVB8_VERC_v120
hi3660_emulator
hi3660_udp_v110
hi3660_udp_EVB8_VERD_v110
hi3660_udp_EVB8_VERC_v110
hi3660_fpga_020
hi3660_udp_EVB8_VERD_ET_v110
VICTORIA_TUGL_V3_V101
VICTORIA_TUGL_V3_BACKLIGHT
VICTORIA_LX9_V3
VICTORIA_TUGL_V3_DPD_SKY2_5
VICTORIA_LX9_V3_BACKLIGHT
VICTORIA_TUGL_V3
VICTORIA_LX9_V3_V101
VICKY_LX9_V3
VICKY_TUGL_V3
VICKY_LX9_V3_DPD_SKY2_0
VICKY_TUGL_V3_DPD_SKY2_5
VICKY_TUGL_V3_DPD_SKY2_0
VICKY_TUGL_V1
VICKY_TUGL_V3_V101
MHA_TUGL_V3_ES
MHA_TUGL_V4_RF
MHA_TUGL_VN2
MHA_TUGL_V3_CS_PA
MHA_TUGL_VN1
MHA_TUGL_V3_CS
MHA_TUGL_V3_POWER_BOARD
MHA_TUGL_V3_POWER_BOARD_V110
MHA_TUGL_V4
MHA_TUGL_V1
LON_TUGL_VN1_2
LON_TUGL_V4_A
LON_TUGL_V3_CS
LON_TUGL_V3_CS_2
LON_TUGL_VN1
LON_TUGL_V4_2
LON_TUGL_V1_2
LON_TUGL_V3_ES
LON_TUGL_V1
MHA_TUGL_VN1_120SOC
VICTORIA_TUGL_V1
CMB_TUCL_CS_V3
DUKE_TUCL_V0
CMB_TUCL_V1
CMB_TUCL_ES_V3
CMB_TUCL_FHD_V3
CMB_L09_V1
[Huawei Mate 9 Questions & Answers] dkionline:
Had you any errors yet with removing this flags?
[Huawei Mate 9 Questions & Answers] ante0:
nope. still working on adding i/o schedulers. for some reason they get enabled by default in menuconfig, governors are disabled by default. so something is up with that... and fails to compile with i/o :(

Well, I do get warnings. But it doesn't fail because of them.

Now it's failing because of:

undefined reference to `rq_fifo_time'
[Huawei Mate 9 Questions & Answers] dkionline:
Well, i have often error 2 sub-make...in linaro and uber but stock toolchain working then.
[Huawei Mate 9 Questions & Answers] ante0:
I'm giving up now. We can't change I/O Scheduler. It's set to none (noop) by default, and that's all there is to select xD

We can change the i/o of the sdcard though.

A scheduler is probably not needed anyway.

Some of the governors I added are buggy as well,they turn off all but one core and it's kept at 100% which makes things laggy. Smartassv2 seems to work well though.
[Huawei Mate 9 Questions & Answers] dkionline:
some of are unstable due to big.LITTLE and 8-Core than 4-Core.

Intelliactive should do aswell.

Check https://github.com/kwoktopus/abyss_kernel_eva/tree/master/drivers/cpufreq

edit: add scheduler to defconfig and set as default.
[Huawei Mate 9 Questions & Answers] ante0:
[MENTION=4900664]dkionline[/MENTION] [MENTION=234719]cr2[/MENTION]

Did any of you try the compiled kernel using aarch64-linux-gnu?

The size of zImage is 200kb larger than when compiling with aarch64-linux-android
[Huawei Mate 9 Questions & Answers] dkionline:
[MENTION=2247733]ante0[/MENTION] , i compiled with linaro successfully, but after i made changes it errors somewhere. As i cant see new governors in Kernel Adiutor, i think something is still wrong, as i made changes like yours.
[Huawei Mate 9 Questions & Answers] ante0:
You need to enable them in menuconfig, unless you already edited merge_hi3660_defconfig to make them 'y' by default.

Try 'make CROSS-COMPILER=aarch64-linux-gnu ARCH=arm64 O=../out menuconfig' and see if they are actually enabled.

It's in CPU POWER MANAGEMENT ---> CPU FREQUENCY SCALING --->

enable with space.

Then hit exit back and yes to save :P

That is if you haven't used menuconfig before.

Edit: And I don't know if this makes a difference, but I add them to include/linux/cpufreq.h too.

The default ones are there so I add mine there too (and some of RamKernel's governors were there too in its own source). The governors start at line 483.

for intelliactive you add

#elif defined(CONFIG_CPU_FREQ_DEFAULT_GOV_INTELLIACTIVE)
extern struct cpufreq_governor cpufreq_gov_intelliactive;
#define CPUFREQ_DEFAULT_GOVERNOR	(&cpufreq_gov_intelliactive)

then just copy paste and change for your other governors.
[Huawei Mate 9 Questions & Answers] dkionline:
[MENTION=2247733]ante0[/MENTION] I didn't know that, only thinked, what you talking about? But now i know what to do, thx mate.
[Huawei Mate 9 Questions & Answers] cr2:
Not yet, because i also wanted to make some changes in the ramdisk,

do not load android and have early console access to busybox

over cdc_ether/rndis like in the old good days of linux hacking.

I have also ordered the hikey960 board, which still can be recovered even if you blow

away everything in the UFS.

The bloated vmlinux is 29MB+, so i would not really worry about 200K difference.
[Huawei Mate 9 Questions & Answers] dkionline:
[MENTION=234719]cr2[/MENTION] This flag allready exist in makefile: KBUILD_CFLAGS += $(call cc-disable-warning, unused-variable)
[Huawei Mate 9 Questions & Answers] AndyPhoenix9879:
Regarding the I/O schedulers - why can't you though? Try finding in the defconfigs this line to try changing the default I/O scheduler :

CONFIG_DEFAULT_NOOP=y

Change it to something like

CONFIG_DEFAULT_ROW=y

..or something. An I/O scheduler sometimes can make a world of difference in terms of UI responsiveness and overall fluidity of the phone.
[Huawei Mate 9 Questions & Answers] Blackball:
A question from p10 plus user.

When u install your new kernel there are problems with taking pictures with the original camera?

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] ante0:
Good catch. Yes. When you tap the image from camera it says Loading... Then it he image disappears.

It's set to row actually, but it's I/O for external sdcard. Can't be changed for internal.
[Huawei Mate 9 Questions & Answers] Blackball:
You have an idea how to fix it? I tried another Toolchain but I got the same issue

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] ante0:
Looking at logcat there seems to be something up with sqlite.

06-09 12:00:45.188 E/SQLiteDatabase(26762): android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: gallery_media._data (Sqlite code 2067), (OS error - 2:No such file or directory)
[Huawei Mate 9 Questions & Answers] Blackball:
I only checked the kernel logcat. The funny thing. The first pic I tooked after install works :D

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] ante0:
Looking around in the source for anything related to camera, found include/huawei_platform/touthscreen. :silly:
[Huawei Mate 9 Questions & Answers] Blackball:
Yes I saw that too... Lol.

It's Huawei

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
Hello, i have a problem, after sucess compile the source code, and generated new.img from stock .img with new zImage

have a bootloop, no boot to "OS" only eRecovery

i used Linaro GCC 6.3.1 05-17 Toolchain

and Ubuntu 16.04 with mkbootimg_tools

but no boot my kernel
[Huawei Mate 9 Questions & Answers] cr2:
Do you get some output from 'adb logcat' before the crash, or are you crashing inside the kernel ?

If you can access the filesystem (from recovery2 aka TWRP), you can also check the /splash2/boot_fail/uploading/bootfail_2017*.tar.gz files.
[Huawei Mate 9 Questions & Answers] BadWolfYe:
Stuck on Orange letters...no Huawei bootanimation
[Huawei Mate 9 Questions & Answers] ante0:
How did you acquire ramdisk? I noticed the one you get from Android Image kitchen is no good. The one you get named new-ramdisk after repack is good though.
[Huawei Mate 9 Questions & Answers] dkionline:
Failed by Security patch?
[Huawei Mate 9 Questions & Answers] BadWolfYe:
I used the imgboot_tools (for Ubuntu) for change only the "kernel" image from the stock kernel..
[Huawei Mate 9 Questions & Answers] BadWolfYe:
What?

---------- Post added at 06:46 AM ---------- Previous post was at 06:15 AM ----------

Hi there are the logs from the "splash2/boot_fail"

fastboot_log: https://pastebin.com/RUxyhXet

last_kmsg: http://chopapp.com/#ejzz8zzx

recovery_info.txt:

bootfail_info.txt:

Thanks in advance
[Huawei Mate 9 Questions & Answers] cr2:
You have a 6GB RAM 5p5 LCD model, what is your full "real" device name (product_id) ?

[3118 ms]Audio_codec: [audio]:product_name:VICKY.
[3130 ms]load_teeos: Get product info success, id = 15, product = vicky
dtimage: -----can not find hisi,product_id
[Huawei Mate 9 Questions & Answers] BadWolfYe:
Vicky: VKY-L29C432 (P10+)

the problem are in dtimage?

i used, the source code of huawei for compile, and no changed nothing for the moment... only build-version and, used Linaro GCC...

And the source are from Vicky-Victoria (same for P10 and P10+, but in dts only files for victoria... no for vicky)

i used only the folder "kernel" i deleted the folder "vendor" and "externals"
[Huawei Mate 9 Questions & Answers] cr2:
No, i mean something different. The DTS product_id for VICKY must be one of

VICKY_LX9_V3

VICKY_TUGL_V3

VICKY_LX9_V3_DPD_SKY2_0

VICKY_TUGL_V3_DPD_SKY2_5

VICKY_TUGL_V3_DPD_SKY2_0

VICKY_TUGL_V1

VICKY_TUGL_V3_V101

I think that the problem is in the secure xloader/fastboot operation before loading the kernel.

It is possible to embed the DTB into the kernel Image, but huawei did not include the DTS sources into the kernel tree,

so you must use one of the predefined DTBs (stored on the dts partition).

I have posted the full list (at least for my phone) two pages before.

If you can boot with the stock kernel image, then it is possible to dump the FDT (the in-RAM copy of used DTB).
[Huawei Mate 9 Questions & Answers] dkionline:
Try with GCC 4.9, no Custom Toolchain and see if that helps.
[Huawei Mate 9 Questions & Answers] BadWolfYe:
How i can extract the DTBs for Vicky? and how to implement to the kernel source?

tried without luck... (Same as Linaro)
[Huawei Mate 9 Questions & Answers] cr2:
Please, post the output of "fdisk -l /dev/block/sdd" here (because i have a MHA, and you have a different filesystem layout).
[Huawei Mate 9 Questions & Answers] BadWolfYe:
This:
[Huawei Mate 9 Questions & Answers] cr2:
Hmm, you have EFI ...

What does

ls -l /sys/bus/scsi/devices

say ?

You can dump your FDT with

cat /sys/firmware/fdt > vicky_fdt

or just look at the output of

cat /sys/firmware/fdt | strings | less
[Huawei Mate 9 Questions & Answers] Blackball:
[MENTION=4473319]BadWolfYe[/MENTION]

Please upload ur zimage. Then I make a boot.img for u for testing.

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
I copied with dd if=/dev/block/sdd43 of=sdcard/dts.img

The "dts_a" partition.... now how to extract info?
[Huawei Mate 9 Questions & Answers] cr2:
Search for the gzip offsets:

od -A x -v -t x4 dts.img | grep 088b1f | awk '{print strtonum("0x"$1)}' > /tmp/offs

and then extract all

for off in `cat /tmp/offs`; do dd if=dts.img skip=1 bs=$off of=/tmp/FDTz.$off 2>/dev/null ; gzip -dc /tmp/FDTz.$off > /tmp/FDTunz.$off; strings /tmp/FDTunz.$off | head -3 | tail -1; dtc -I dtb /tmp/FDTunz.$off > /tmp/FDTunzS.$off; done

---------- Post added at 11:48 AM ---------- Previous post was at 11:41 AM ----------

BTW, i can boot into TWRP with 'adb reboot recovery2'. Is it possible to flash the boot.img into some spare partition

(like reserved2) and then boot the new kernel from it with 'adb reboot reserved2' ?
[Huawei Mate 9 Questions & Answers] BadWolfYe:
(my ramdisk it's B130, B150 ramdisk no work (i tried boot from your kernel of, your rom and no worked in my case :( )

My zImage:

https://mega.nz/#!MVEmVCSa!wvnDHuGxZ1s2d1h2lIj8wgLyoVISp1njTmMx_-cjEP4
[MENTION=234719]cr2[/MENTION]

This are the FDT output on vicky_fdt file:

https://pastebin.com/vpHpXSyL

and this the output from terminal of ubuntu from your last commands:

parallels@RevolutionTechs:~/Android/dts$ od -A x -v -t x4 dts.img | grep 088b1f | awk '{print strtonum("0x"$1)}' > /tmp/offs

awk: line 2: function strtonum never defined

parallels@RevolutionTechs:~/Android/dts$ for off in `cat /tmp/offs`; do dd if=dts.img skip=1 bs=$off of=/tmp/FDTz.$off 2>/dev/null ; gzip -dc /tmp/FDTz.$off > /tmp/FDTunz.$off; strings /tmp/FDTunz.$off | head -3 | tail -1; dtc -I dtb /tmp/FDTunz.$off > /tmp/FDTunzS.$off; done

parallels@RevolutionTechs:~/Android/dts$
[Huawei Mate 9 Questions & Answers] cr2:
Ok, so you have VICKY_LX9_LV3 and it should not be a problem.

Install the 'gawk' package, the non-gnu awk does not know the strtonum function.
[Huawei Mate 9 Questions & Answers] Blackball:
[MENTION=4473319]BadWolfYe[/MENTION]

Flash it with twrp (Image) and after install flash your or my supersu .

https://mega.nz/#!XshFmbxb!kPr46JB3EoCHmFVHtfbTnWx26EUJVw1TvC47FXH0Jp0

[MENTION=234719]cr2[/MENTION]

is it possible to extract the dts Folder from stock kernel ?
[Huawei Mate 9 Questions & Answers] cr2:
fastboot picks the DTB from the DTS_A partition (probably by the boardid tag),

hisi,boardid = <0x5 0x5 0x0 0x9>;
hisi,boardname = "MHA_TUGL_VN2";

hisi,gpu_arch = "mimir";
hisi,camera_arch = "platform_v110";
hisi,camera_arch_v120 = "platform_v120";

adds its own stuff into the 'chosen' tag

and this is passed to the kernel (and can be dumped from the /sys/firmware/fdt).

Ramdisk/initrd stage comes later, first you need to load the Image into RAM and Image must find the DTB in some predefined RAM area, too.

chosen {
linux,initrd-end = <0x8192d90>;
linux,initrd-start = <0x7c00000>;
bootargs = "loglevel=4 initcall_debug=n page_tracker=on androidboot.selinux=enforcing androidboot.swtype=normal fastboot_version=CHICAGO-CP00B063_FASTBOOT setup_logctl=0 fastbootdmd=0 enter_recovery=0 androidboot.mode=normal pmu_nv_addr=0x20b20014 low_volt_flag=0 boardid=0x00001585 normal_reset_type=coldboot TP_COLOR=120 ...
};
[Huawei Mate 9 Questions & Answers] BadWolfYe:
yes¡¡¡¡ worked example of output:

but i dont see the files, for copy to kernel source (or inject to kernel.img)

no worked, bootloop-reboot (same error)
[Huawei Mate 9 Questions & Answers] :
You can use bootimg.py search on Google

And extract boot only replace kernel and repack. It could be a issue if you tried modify ramdisk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
i tried abootimg for only pack with "zImage" with same error -.-"
[Huawei Mate 9 Questions & Answers] cr2:
You can try to enable the framebuffer console with penguin logo in .config

then you should see the usual linux kernel boot output on the LCD :)

This should work even without the ramdisk/initrd or with broekn ramdisk/initrd.

# CONFIG_VT_CONSOLE is not set

# CONFIG_FRAMEBUFFER_CONSOLE is not set

# CONFIG_LOGO is not set

---------- Post added at 12:42 PM ---------- Previous post was at 12:31 PM ----------

The files are in /tmp

ls -l /tmp/FDTunzS.*

VICKY_LX9_V3 in /tmp/FDTunzS.1603584 on my MHA

#address-cells = <0x2>;
#size-cells = <0x2>;
model = "hi3660";
compatible = "hisilicon,hi3660";
interrupt-parent = <0x1>;
hisi,boardid = <0x5 0x4 0x1 0x2>;
hisi,boardname = "VICKY_LX9_V3";
hisi,modem_id = <0x3a030c00>;
hisi,sub_platform_info3 = "Kirin960";
hisi,provider3 = "BALONG";
hisi,sub_platform_info2 = "Kirin960";
hisi,provider2 = "BALONG";
hisi,sub_platform_info1 = "Kirin960";
hisi,provider1 = "BALONG";
hisi,sub_platform_info0 = "Kirin960";
hisi,provider0 = "HUAWEI_K3";
hisi,platform_num = <0x4>;
hisi,gpu_arch = "mimir";
hisi,camera_arch = "platform_v110";

You don't need to include it into the kernel (at least not now), because your DTS_A partition is OK,

and fastboot finds it there.

The dumped DTBs help to understand the differences between the models (here MHA_TUGL_VN1 and MHA_TUGL_VN2)

--- /tmp/FDTunzS.2301952 2017-06-05 11:13:47.368236388 +0200
+++ /tmp/FDTunzS.2174976 2017-06-05 11:13:47.284236095 +0200
@@ -6,8 +6,8 @@
model = "hi3660";
compatible = "hisilicon,hi3660";
interrupt-parent = <0x1>;
- hisi,boardid = <0x5 0x5 0x0 0x8>;
- hisi,boardname = "MHA_TUGL_VN1";
+ hisi,boardid = <0x5 0x5 0x0 0x9>;
+ hisi,boardname = "MHA_TUGL_VN2";
hisi,modem_id = <0x3a001400>;
hisi,sub_platform_info3 = "Kirin960";
hisi,provider3 = "BALONG";
@@ -20,6 +20,7 @@
hisi,platform_num = <0x4>;
hisi,gpu_arch = "mimir";
hisi,camera_arch = "platform_v110";
+ hisi,camera_arch_v120 = "platform_v120";

chosen {
};
@@ -11438,6 +11439,7 @@
ufs-kirin-broken-clk-gate-pypass;
ufs-0db-equalizer-product-names = "THGBF7G8K4LBATRC";
volt-irq,ufs-gpios = <0x61 0x6 0x0>;
+ ufs-kirin-linereset-check-disable;
};
[Huawei Mate 9 Questions & Answers] BadWolfYe:
tried "penguin" method xD

result: same (and i dont see the penguin)

if i no need include why are my problem?

[MENTION=477335]Blackball[/MENTION] if possible you upload your complete source code and toolchain please? i dont know whats are my problem, and im hating now Huawei hahahahaha

only for research this it's my make log....:

https://pastebin.com/9yPz7BAz

There are the commands on build_update.sh

There on build_ramdisk.sh:

PS; the original zImage are 11,8MB, my zImage are 11,6MB ¿WTF?
[Huawei Mate 9 Questions & Answers] Blackball:
i didnt change something in the sources.

You can try to flash my latest boot.img. That image boot without

any problem for me.

Just the camera bug is still there.

https://mega.nz/#!D1gmEBSb!4aQaNBZPHRFygKmfJCjMVoIoTY3WueTdi2a16WbSt9Y
[Huawei Mate 9 Questions & Answers] BadWolfYe:
lol probably my phone are big stupid: no work your Boot.img WTF?

Whats your base firmware? my base firmware are: B120/30

can you try if my boot.img (the img you generated for me) if work on your device?

ps; the camera problem are based on ramdisk, if you using the kangvip ramdisk (AL00), try using the B130 boot.img ramdisk, and camera problem fixed....
[Huawei Mate 9 Questions & Answers] Blackball:
Really? I will try. And I try your boot too

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
yeh... example: i flashed the first build of kangvip posted in p10+, with b136 boot image (137 no boot for me (same as my error on my kernel and your kernel)AL00 conflict with L** probably), the result: camera bug.... i flashed the boot.img of my previusly backup: b130: camera bug dissapear...and all work perfect...

now im triying to compile with:

CONFIG_DM_VERITY=n

CONFIG_DM_VERITY_FEC=n

CONFIG_DM_VERITY_HW_RETRY=n

on defconfig... probably no work... but... dont know the problem -.-"

If in your case, your boot.img work, why in my phone not? it's same phone!!!! what the problem!! hahahaha... this make me crazy... really
[Huawei Mate 9 Questions & Answers] Blackball:
What camera bug do you mean?

The camera bug with kernel from sources is that the cam can't save any pictures.

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
my bug: take a photo, mini photo appear on bottom of camera app, click on that appear "loading" after fe seconds "dissapear" and go to previusly photo...

really, no its a bug from source code, its from ramdisk...

Ps; my test without dm-verity flags on defconfig = same as before and before, and before.....
[Huawei Mate 9 Questions & Answers] Blackball:
But I can't unpack the Kang boot image.

Your kernel doesn't boot...

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
no unpack the K_Boot, unpack the B130 boot.img and use that for insert your zImage

my source are broken O_o

what GCC you use?
[Huawei Mate 9 Questions & Answers] Blackball:
i use this one:

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
[Huawei Mate 9 Questions & Answers] BadWolfYe:
trying now with that...
[Huawei Mate 9 Questions & Answers] :
Well some tools repack badly as I asked did you modify ramdisk?
[Huawei Mate 9 Questions & Answers] BadWolfYe:
nope no modified ramdisk...

but, [MENTION=477335]Blackball[/MENTION] tried with the tool i have for repack, and no work anyway the kernel ...

now i are triying compile with Google 4.9 Toolchain no Linaro GCC 6.3.1
[Huawei Mate 9 Questions & Answers] Blackball:
Ramdisk from B130 doesn't work.

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
try ramdisk's the ramdisk are the problem, but use VKY ramdisk no VTR!!!...

try from B125 for example...

or, compare the B130 ramdisk, with your ramdisk...
[Huawei Mate 9 Questions & Answers] Blackball:
With Stock B150 Kernel everything is working well. If I change just the zimage it doesn't work. Ramdisk is the same.

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] ante0:
Try this:

Use the boot.img for your phone build, i.e if you use B158 you use boot.img from B158.

Unpack boot.img using Android Image Kitchen. https://xdaforums.com/devdb/project/?id=1568#downloads Get ALL if you're on linux, Win32 if you're on Windows.

Copy and paste image.gz to the split_image folder created by Android Image Kitchen.

Remove the existing boot.img-zImage file, rename Image.gz to boot.img-zImage.

Repack and see if that works.

This is how I do it. I can't produce a working boot image using zImage, ramdisk.gz and mk_bootimg
[Huawei Mate 9 Questions & Answers] Blackball:
I use superr.. That's working fine.. But B133 not. Don't know why

With B150 I mean that's the cam bug still there so I don't think it's a Ramdisk problem
[Huawei Mate 9 Questions & Answers] BadWolfYe:
try stock boot.img B150 (flash the stock file) and root..., ¿are present camera bug?
[Huawei Mate 9 Questions & Answers] Blackball:
With Stock B150 there is no bug. B150 with my zimage the bug is there

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
LoL

success...

i used my boot.emmc.win backup from TWRP for make the boot.img with original ramdisk, blah blah... (with the bootimg.py)

and booted, and yeah problem of camera present :)

It's kernel related, sorry for the stupid mistake...

in "about device" --> kernel says "unavailable" but... in uname -a on console, says the correct version hahahaha

now, need research for camera....
[Huawei Mate 9 Questions & Answers] ante0:
If you change local name in menuconfig/defconfig it says unavailable. There's a "hack" you can use:

https://xdaforums.com/showthread.php?t=977854

Scroll down to the dev part.
[Huawei Mate 9 Questions & Answers] BadWolfYe:
very thanks, now im researching the part of "camera crash"...

probably in few days i upload my source code with de build.sh files, bootimg.py, ramdisk, cross compiller,.... , to github... for research and etc...
[Huawei Mate 9 Questions & Answers] dkionline:
The most time camera crash if no root installed.
[Huawei Mate 9 Questions & Answers] BadWolfYe:
But i have root...
[Huawei Mate 9 Questions & Answers] BadWolfYe:
Good, now i have kernel version on Settings, but camera bug are present, are related with SQL database, probably problem: Binary file sqlite3

in any case on compiling kernel, the system make this "modules":
[Huawei Mate 9 Questions & Answers] Blackball:
Maybe we should make a Telegram group about kernel camera bug.

Gesendet von meinem VKY-L29 mit Tapatalk
[Huawei Mate 9 Questions & Answers] BadWolfYe:
WTF? hahaha
[Huawei Mate 9 Questions & Answers] :
Telegram group https://t.me/joinchat/AAAAAEPAdZQL3wdGPltzoQ

Done
[Huawei Mate 9 Questions & Answers] dkionline:
Opened new chat here: https://t.me/joinchat/AAAAAA46G2By4mAI64UeKA as last one got deleted.

Hope to see any progress.