Start with the CyanogenMod build instructions for i9300
Wherever the guide says i9300, use i9305 instead!
When the guide tells you to install a CM 10.1 ROM on your rooted phone, before running extract-files.sh, you can use the build from codeworkx.
Follow the guide and stop before executing 'repo init'. Do instead:
$ repo init -u git://github.com/perchrh/android.git -b cm-10.1
This uses a device and vendor tree for the i9305 from teamdisgruntled, and a general samsung vendor tree from TheMuppets.
Follow the guide again, until the end.
Flash your phone with the resulting zip file cm-10.1*.zip
Reboot and you're done!
Thanks to xda-member vkggg for posting a similar guide for AOSP that got me started on my CM build.
Do you see the following when doing the 'breakfast' command?
Syncing dependencies
fatal: duplicate project CyanogenMod/android_device_samsung_smdk4412-common in /home/me/android/system/.repo/manifest.xml
android_device_samsung_smdk4412-common is part of the extra's added to the manifext.xml file and it is also included in the local_manifests/roomservice.xml file
mcampbellsmith said:
Do you see the following when doing the 'breakfast' command?
Syncing dependencies
fatal: duplicate project CyanogenMod/android_device_samsung_smdk4412-common in /home/me/android/system/.repo/manifest.xml
android_device_samsung_smdk4412-common is part of the extra's added to the manifext.xml file and it is also included in the local_manifests/roomservice.xml file
Click to expand...
Click to collapse
Thanks! That looks new. Probably -common wasn't included in the other file previously.
I've updated the dependency list to reflect this and the error should be gone now
Update: I've verified the fix. Note that if you had an error while doing repo init, another 'repo init' in the same directory may not work. In that case, remove the .repo directory or do the init in a new directory!
I've been running CM on my HD+ for the last few months and it's been great. I'm working on making some modifications to the VM and to the kernel and it requires building CM from source. I've already done this with several other devices and have had only minor problems. I'm following the instructions and it can't build. I get the following error:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140120-UNOFFICIAL-ovation
TARGET_PRODUCT=cm_ovation
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.7.10-1.16-desktop-x86_64-with-SuSE-12.3-x86_64
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/home/david/Android/system/out
============================================
make: *** /.config: Is a directory. Stop.
I've searched and haven't found a solution but It seems like I'm missing a manifest or something. I'm wondering if this is missing from 10.2 and I should just try building 11 or if there's a way I can build from source.
Thanks to anyone who can help!
No experience building CM but it looks like maybe /.config instead of ./config got invoked?
Sent from HD+ MAG2GA CM 11 from SD
Did you follow this guide? -> http://wiki.cyanogenmod.org/w/Build_for_ovation (repo init for cm11 instead if cm11 is desired)
Its probably just an error that you made. I don't remember seeing it before.
Edit it doesn't like /.config. That much is obvious. So try to rename or move it or fix your problem to avoid it. (if its ~/.config be careful as that is an important dir.)
There is a .config in /out during building process which is the kernel defconfig file. There is also ~/.config. And that's all I know about that. Look around for .config or google your error with "/.config;" removed and see how the "make: *** is a directory. stop" plain version helps you.
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
ddpruitt said:
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
Click to expand...
Click to collapse
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Some other thoughts based on testing:
You get the correct manifest, etc. with the git and repo sync so again its not with what your getting. That all will build it without that weird error.
If there's no .config file in android/system/out/target/product/ovation/obj/KERNEL_OBJ/ then its because it didn't do enough to put one there yet. That shouldn't be the issue as it will rename a .config dir and continue or if it can't then have a different error.
Did you try make clean or make clobber and try building again?
sandsofmyst said:
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Click to expand...
Click to collapse
I had someone else try it on an Ubuntu machine and it has the same issue. I'll try to get the verygreen repos instead of the official CM ones see if that helps
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
sandsofmyst said:
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
Click to expand...
Click to collapse
You're an absolute genius. For some reason I did have a /.config directory, I never even though of looking in the root directories. Must be some strange KDE issue. I deleted it and build kicked off and it's rolling fine now.
On the Lenovo website, I have finally found source code for the kernel of the Lenovo Tab 4 8 Plus. I downloaded the source, made defconfig, and enabled KVM in the kernel and then compiled. I got several errors which couldn't be fixed. I wondered if this was the cause of KVM, so I disabled KVM and tried again. Same errors. Strange that the archive containing the sources for the Lenovo Tab 4 10 Plus is much larger than that of the Lenovo Tab 4 8 Plus, which suggests that the Tab 4 8 Plus sources are not complete yet they both have the same SoC. Shame on Lenovo! This is the last time I get a product from them unless things improve. When I went to complain on the forums, I couldn't even start a thread, even though I had logged in and had verified my email, which is why I'm complaining here. They're also violating the GPL. The Tab 4 series were released in 2017 yet only in 2019 has Lenovo started releasing the kernel source code, clearly a GPL violation. I wanted to start learning ROM development and possibly port Android Pie to the Tab 4 8 Plus but because of this I can't. I love my Tab 4 8 Plus and my Ideapad 310 laptop but I think I'm done with Lenovo after this unless things improve.
code_exec said:
Shame on Lenovo! This is the last time I get a product from them unless things improve. When I went to complain on the forums, I couldn't even start a thread, even though I had logged in and had verified my email, which is why I'm complaining here. They're also violating the GPL. The Tab 4 series were released in 2017 yet only in 2019 has Lenovo started releasing the kernel source code, clearly a GPL violation.
Click to expand...
Click to collapse
I completely agree with your opinion on Lenovo. However, cannot confirm the problem with their forum. Also, they would have published the kernel sources much sooner if someone had asked earlier - which doesn't excuse the fact that they should publish the kernels immediately on their own.
I asked for the kernel source for the 10 Plus and the 8 Plus and got both after a longer wait.
code_exec said:
On the Lenovo website, I have finally found source code for the kernel of the Lenovo Tab 4 8 Plus. I downloaded the source, made defconfig, and enabled KVM in the kernel and then compiled. I got several errors which couldn't be fixed. I wondered if this was the cause of KVM, so I disabled KVM and tried again. Same errors. Strange that the archive containing the sources for the Lenovo Tab 4 10 Plus is much larger than that of the Lenovo Tab 4 8 Plus, which suggests that the Tab 4 8 Plus sources are not complete yet they both have the same SoC.
Click to expand...
Click to collapse
This isn't right. Text can be compressed very well. You have to compare the sources after unpacking, the code of the 8 Plus is compressed twice and therefore much smaller. At first view the kernel looks ok. But I didn't compile it, so you can still be right with your error messages, but the size of an archive is not an argument.
To compare two directories I use the tool Meld.
code_exec said:
I wanted to start learning ROM development and possibly port Android Pie to the Tab 4 8 Plus but because of this I can't. I love my Tab 4 8 Plus and my Ideapad 310 laptop but I think I'm done with Lenovo after this unless things improve.
Click to expand...
Click to collapse
I started with rom development for the same reasons as you, only that I have the Tab4 10 Plus. I want to motivate you not to give up at this point. You have actually very good conditions to develop a working rom, because the Tab3 8 Plus has one or more device tree and kernel and you can use my work on the 10 Plus as well.
LumenReaper said:
I started with rom development for the same reasons as you, only that I have the Tab4 10 Plus. I want to motivate you not to give up at this point. You have actually very good conditions to develop a working rom, because the Tab3 8 Plus has one or more device tree and kernel and you can use my work on the 10 Plus as well.
Click to expand...
Click to collapse
Does the 10 Plus kernel work on the 8 Plus though?
code_exec said:
Does the 10 Plus kernel work on the 8 Plus though?
Click to expand...
Click to collapse
Not without adjustments.
The archive of the X704F contains build instructions from Lenovo and a working defconfig.
Compare the defconfig of the 10 Plus with your own. And as already said, compare the sources with Meld. I'm pretty sure you could get a working kernel out of it.
LumenReaper said:
Not without adjustments.
The archive of the X704F contains build instructions from Lenovo and a working defconfig.
Compare the defconfig of the 10 Plus with your own. And as already said, compare the sources with Meld. I'm pretty sure you could get a working kernel out of it.
Click to expand...
Click to collapse
Here's the actual error I get when compiling: https://pastebin.com/mJyei1Y9
code_exec said:
Here's the actual error I get when compiling: https://pastebin.com/mJyei1Y9
Click to expand...
Click to collapse
Can you send me your defconfig please? I will look into it but probably not today.
LumenReaper said:
Can you send me your defconfig please? I will look into it but probably not today.
Click to expand...
Click to collapse
It's just called defconfig and is located in arch/arm64/configs. The MSM ones appear to be for the Snapdragon 430 and not the Snapdragon 625 the Tab 4 8 Plus uses.
code_exec said:
Here's the actual error I get when compiling: https://pastebin.com/mJyei1Y9
Click to expand...
Click to collapse
interestingly, I get a different error:
HTML:
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC arch/arm64/mm/dma-mapping.o
In file included from ./arch/arm64/include/asm/dma-iommu.h:12:0,
from arch/arm64/mm/dma-mapping.c:33:
include/linux/dma-mapping-fast.h:46:15: warning: 'struct dma_iommu_mapping' declared inside parameter list
error, forbidden warning: dma-mapping-fast.h:46
scripts/Makefile.build:257: recipe for target 'arch/arm64/mm/dma-mapping.o' failed
make[1]: *** [arch/arm64/mm/dma-mapping.o] Error 1
Makefile:946: recipe for target 'arch/arm64/mm' failed
make: *** [arch/arm64/mm] Error 2
and using the kernel config extracted from the kernel in build 180906 for the TB-8704X (I don't have the tablet yet):
HTML:
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
CC drivers/net/ethernet/msm/rndis_ipa.o
In file included from drivers/net/ethernet/msm/rndis_ipa_trace.h:81:0,
from drivers/net/ethernet/msm/rndis_ipa.c:32:
include/trace/define_trace.h:83:43: fatal error: ./rndis_ipa_trace.h: No such file or directory
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'drivers/net/ethernet/msm/rndis_ipa.o' failed
make[4]: *** [drivers/net/ethernet/msm/rndis_ipa.o] Error 1
scripts/Makefile.build:402: recipe for target 'drivers/net/ethernet/msm' failed
make[3]: *** [drivers/net/ethernet/msm] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/net/ethernet' failed
make[2]: *** [drivers/net/ethernet] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/net' failed
make[1]: *** [drivers/net] Error 2
Makefile:946: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I'll play with it some more when I get mine sometime next week and update it and extract the kernel config
I haven't had any luck playing with merging the TB-X704L and TB-8704X sources, still getting the same error.
Edit: I get the same error for the TB-X704L and TB-X704F.
Another edit: did a diff with the Pixel kernel:
HTML:
diff -ur tab48plus/drivers/net/ethernet/msm/rndis_ipa_trace.h msm/drivers/net/ethernet/msm/rndis_ipa_trace.h
--- tab48plus/drivers/net/ethernet/msm/rndis_ipa_trace.h 2017-05-02 05:06:34.000000000 +0100
+++ msm/drivers/net/ethernet/msm/rndis_ipa_trace.h 2019-04-08 13:21:43.806756700 +0100
@@ -77,5 +77,5 @@
/* This part must be outside protection */
#undef TRACE_INCLUDE_PATH
-#define TRACE_INCLUDE_PATH .
+#define TRACE_INCLUDE_PATH ../../drivers/net/ethernet/msm
#include <trace/define_trace.h>
now I've gotten further, there's a lot of these errors
After fixing all the incorrect includes and adding the missing files, I have a kernel image
Edit: https://github.com/Phoenix09/android_kernel_lenovo_tb8704
@code_exec: you should probably extract the config from your device and try building with this repo, I have no idea if any of the configs in the source are for this tablet.
Phoenix09 said:
interestingly, I get a different error:
HTML:
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC arch/arm64/mm/dma-mapping.o
In file included from ./arch/arm64/include/asm/dma-iommu.h:12:0,
from arch/arm64/mm/dma-mapping.c:33:
include/linux/dma-mapping-fast.h:46:15: warning: 'struct dma_iommu_mapping' declared inside parameter list
error, forbidden warning: dma-mapping-fast.h:46
scripts/Makefile.build:257: recipe for target 'arch/arm64/mm/dma-mapping.o' failed
make[1]: *** [arch/arm64/mm/dma-mapping.o] Error 1
Makefile:946: recipe for target 'arch/arm64/mm' failed
make: *** [arch/arm64/mm] Error 2
and using the kernel config extracted from the kernel in build 180906 for the TB-8704X (I don't have the tablet yet):
HTML:
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CHK kernel/config_data.h
CC drivers/net/ethernet/msm/rndis_ipa.o
In file included from drivers/net/ethernet/msm/rndis_ipa_trace.h:81:0,
from drivers/net/ethernet/msm/rndis_ipa.c:32:
include/trace/define_trace.h:83:43: fatal error: ./rndis_ipa_trace.h: No such file or directory
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
^
compilation terminated.
scripts/Makefile.build:257: recipe for target 'drivers/net/ethernet/msm/rndis_ipa.o' failed
make[4]: *** [drivers/net/ethernet/msm/rndis_ipa.o] Error 1
scripts/Makefile.build:402: recipe for target 'drivers/net/ethernet/msm' failed
make[3]: *** [drivers/net/ethernet/msm] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/net/ethernet' failed
make[2]: *** [drivers/net/ethernet] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/net' failed
make[1]: *** [drivers/net] Error 2
Makefile:946: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I'll play with it some more when I get mine sometime next week and update it and extract the kernel config
I haven't had any luck playing with merging the TB-X704L and TB-8704X sources, still getting the same error.
Edit: I get the same error for the TB-X704L and TB-X704F.
Another edit: did a diff with the Pixel kernel:
HTML:
diff -ur tab48plus/drivers/net/ethernet/msm/rndis_ipa_trace.h msm/drivers/net/ethernet/msm/rndis_ipa_trace.h
--- tab48plus/drivers/net/ethernet/msm/rndis_ipa_trace.h 2017-05-02 05:06:34.000000000 +0100
+++ msm/drivers/net/ethernet/msm/rndis_ipa_trace.h 2019-04-08 13:21:43.806756700 +0100
@@ -77,5 +77,5 @@
/* This part must be outside protection */
#undef TRACE_INCLUDE_PATH
-#define TRACE_INCLUDE_PATH .
+#define TRACE_INCLUDE_PATH ../../drivers/net/ethernet/msm
#include <trace/define_trace.h>
now I've gotten further, there's a lot of these errors
After fixing all the incorrect includes and adding the missing files, I have a kernel image
Edit: https://github.com/Phoenix09/android_kernel_lenovo_tb8704
@code_exec: you should probably extract the config from your device and try building with this repo, I have no idea if any of the configs in the source are for this tablet.
Click to expand...
Click to collapse
That GitHub repository lacks a defconfig for the TB-8704F (WiFi-only variant), which I have. Will the TB-8704X (LTE variant) kernel work on the TB-8704F out of the box without adjustments or will adjustments be needed for the kernel to boot? Also, how do I extract the defconfig from my device?
code_exec said:
That GitHub repository lacks a defconfig for the TB-8704F (WiFi-only variant), which I have. Will the TB-8704X (LTE variant) kernel work on the TB-8704F out of the box without adjustments or will adjustments be needed for the kernel to boot? Also, how do I extract the defconfig from my device?
Click to expand...
Click to collapse
it might work, I don't know.
to extract the config:
you'll need mkboot
backup boot with TWRP, transfer boot.img to PC
extract boot.img:
Code:
./mkbootimg_tools/mkboot boot.img boot
decompress kernel:
Code:
cd boot
zcat kernel > kernel.out
extract the config:
Code:
/path/to/kernel/source/scripts/extract-ikconfig kernel.out > defconfig.txt
Phoenix09 said:
it might work, I don't know.
to extract the config:
you'll need mkboot
backup boot with TWRP, transfer boot.img to PC
extract boot.img:
Code:
./mkbootimg_tools/mkboot boot.img boot
decompress kernel:
Code:
cd boot
zcat kernel > kernel.out
extract the config:
Code:
/path/to/kernel/source/scripts/extract-ikconfig kernel.out > defconfig.txt
Click to expand...
Click to collapse
I backed up boot to a microSD card in TWRP recovery. However, there are three files in the backup folder of the microSD: one called 'boot.emmc.win', one called 'boot.emmc.win.sha2', and one called 'recovery.log'
The first file could possibly contain boot.img, but how do I extract it? The second one contains a SHA2 checksum for the first file. The third one is a more detailed log of what was happening in TWRP.
EDIT: Simply renaming boot.emmc.win to boot.img seems to have done the trick. Just extracted it, will look into it now.
EDIT 2: Managed to extract the defconfig and copied it over to the arch/arm64/configs folder and renamed it to tb8704f_defconfig. I then made defconfig and started compiling. Unfortunately same error. Something about topology.c is either broken on this kernel or my version of gcc is unable to parse something in topology.c. Even on the version off of GitHub. You said it was working for you, just curious, what Linux distro are you using? I'm happy to install it into a VM and compile the kernel from that. I'm running Ubuntu 18.04 and have tried compiling both on my host and in a systemd container, but same error.
EDIT 3: Yeah, it's an issue with my gcc compiler, because it doesn't error out at topology.c on an Ubuntu 16.04 systemd container with gcc 5 vs the Ubuntu 18.04 host and container I tried building it on with gcc 7 which did error out at topology.c. It's compiling right now in the Ubuntu 16.04 container and I do hope that it doesn't error out at another stage. It seems to be building well so far.
EDIT 4: I'm currently building it with the tb8704f_defconfig file I extracted from the tablet's boot image. Working well so far. I'm gonna build it without any modifications to the .config file and then flash it to the tablet to see if it works before making modifications with menuconfig. If this compilation goes well, I'll start making modifications with menuconfig.
EDIT 5: Kernel built, now I've got a file called 'Image' as well as Image.gz and Image-dtbs.gz Gzip archives. How do I flash these to the tablet?
code_exec said:
EDIT 2: Managed to extract the defconfig and copied it over to the arch/arm64/configs folder and renamed it to tb8704f_defconfig. I then made defconfig and started compiling. Unfortunately same error. Something about topology.c is either broken on this kernel or my version of gcc is unable to parse something in topology.c. Even on the version off of GitHub. You said it was working for you, just curious, what Linux distro are you using? I'm happy to install it into a VM and compile the kernel from that. I'm running Ubuntu 18.04 and have tried compiling both on my host and in a systemd container, but same error.
Click to expand...
Click to collapse
I'm pretty sure 3.18 won't built with GCC newer than 4.9 (at least without a lot of patches), I'm using Ubuntu 18.04 and Google's toolchain
code_exec said:
EDIT 5: Kernel built, now I've got a file called 'Image' as well as Image.gz and Image-dtbs.gz Gzip archives. How do I flash these to the tablet?
Click to expand...
Click to collapse
replace kernel in the unpacked boot image with Image-dtbs.gz, repack using:
Code:
mkboot boot/ new-boot.img
then you can flash that using the "flash image" option in TWRP
Phoenix09 said:
then you can flash that using the "flash image" option in TWRP
Click to expand...
Click to collapse
Got bootlooped when doing this, but thankfully I made a backup of my previous boot partition so I could restore in TWRP.
Unfortunately, I don't think we're getting very close to making custom ROMs for this tablet. Maybe the reason I got bootlooped was because you used files from the Pixel kernel for the missing files on your GitHub repository. I wonder if files from the Lenovo Tab 4 10 Plus kernel (which has been compiled in the past because there are custom ROMs available for this tablet) could be used instead.
code_exec said:
Got bootlooped when doing this, but thankfully I made a backup of my previous boot partition so I could restore in TWRP.
Unfortunately, I don't think we're getting very close to making custom ROMs for this tablet. Maybe the reason I got bootlooped was because you used files from the Pixel kernel for the missing files on your GitHub repository. I wonder if files from the Lenovo Tab 4 10 Plus kernel (which has been compiled in the past because there are custom ROMs available for this tablet) could be used instead.
Click to expand...
Click to collapse
the files I used from the Pixel kernel were probably generic Qualcomm stuff, I had the exact same issues with the 10 Plus kernel, I can play with it more when I get mine on Thursday.
Edit: I checked properly, they're generic Linux ones, those wouldn't affect booting (all netfilter stuff).
Edit 2: Have opened a ticket about the broken source, let's see if we get anywhere.
Edit 3: There is definitely issues with their source, repacked the stock boot image without modifying it and that boots, repacking it with my compiled kernel does not.
Hi Guys. Great to see people working on this. Will be great to eventually see a ROM for the tab 8 4. Best of luck.
My los15- nougat build stops at 99% with this error:
Non-symlink /out/target/product/oxygen/system/vendor detected!
You cannot install files to /out/target/product/oxygen/system/vendor while building a separate vendor.img!
I have tried a lot of sources and searched the web for a solution.
The only thing a have found in web is this:
https://android.googlesource.com/platform/build/+/3e72ed1%5E%21/
But my makefile does have theses lines.
Does anyone knows how to solve this error ?
harvey186 said:
My los15- nougat build stops at 99% with this error:
Non-symlink /out/target/product/oxygen/system/vendor detected!
You cannot install files to /out/target/product/oxygen/system/vendor while building a separate vendor.img!
I have tried a lot of sources and searched the web for a solution.
The only thing a have found in web is this:
https://android.googlesource.com/platform/build/+/3e72ed1^!/
But my makefile does have theses lines.
Does anyone knows how to solve this error ?
Click to expand...
Click to collapse
Have you got a solution for this ? I am facing the same issue.