Develop Bugs

[Q] Xperia Z1 C Camera Hardware button not working when screen is on

Hi guys
I bought this Xperia Z1 Compact (D5503) AKA Amami this year February.
everything went well and then i rooted it, i flashed 757 kernel and then rooted it with CWM recovery
i was using RomAur 3.0 rom for a month. the camera button functioned properly and all.
Then i flashed 108 kernel using twrp recovery and flashed another rom (Kat slim) the camera button activates the camera when the screen is off but does not work when the screen is on.
it doesn't start camera when I'm in other apps or even home screen.
even when i start the camera manually i am not able to take photos using the button
it just adjusts the focus when i press the button.

anyone?
please help

This sounds like an issue with your current ROM. You should post this in the ROM thread so the devs can solve this issue if it is a bug.
There is nothing more you can do other than trying with a different ROM.

I tried some other rom called kai rom and its based on. 157 kernel and still it doesn't work :/

jokervulture said:
I tried some other rom called kai rom and its based on. 157 kernel and still it doesn't work :/
Click to expand...
Click to collapse
try latest 157 stock rom via flashtool instead of custom rom via recoveries

Didn't help.
I tried flashing. 157 kernel official
The weirdest part is that the camera button takes photos in external apps like the Google camera but doesn't take photo with the stock camera. It only focuses..

Camera crashes

Hey guys , i have a Xperia Play , with g2kitkat and lupus kernel . My camera crashes all the time .... (Still before the kernel) Every time i clear cache and dalvik cache , and then i open the phone camera works for a litlle , but i cant switch the 2 cameras . Im realy sorry for my bad english . Any ideas how i can fix this ?

No idea?

Kitkat is not a good system for Play. Better feedback have Lollipop, so mayby try newer system.
Edit. Sorry i thought its a kitkat rom... I don't know what is the reason

TheVicious said:
Kitkat is not a good system for Play. Better feedback have Lollipop, so mayby try newer system.
Edit. Sorry i thought its a kitkat rom... I don't know what is the reason
Click to expand...
Click to collapse
:good:

Mayby load system again or change kernel? Which kernel do You load?

TheVicious said:
Mayby load system again or change kernel? Which kernel do You load?
Click to expand...
Click to collapse
i have do it at least 3 times flash 3 different ROM , and i load kernel Lupus.

Lupus - but mayby change version or load doomlords kernel? As far I used Gingerbread i prefered Doomlord kernel then Lupus.

TheVicious said:
Lupus - but mayby change version or load doomlords kernel? As far I used Gingerbread i prefered Doomlord kernel then Lupus.
Click to expand...
Click to collapse
i had the same problem before i got Lupus as my kernel

I can think of 3 reasons:
1. disable flash from quickpannel (shortcut for flash in stock-based gingerbread roms brakes access to camera)
2. Your camera is broken or in near-dead state
3. Flex cable that camera is attached to motherboard is loose/have bad contact (it can happen if too much phone falls to ground)
If you want to check your camera's hardware is working properly, flash stock ftf (any firmware will do). If it doesn't work on stock, it's hardware fault

[Kernel] 3.18 kernel development

3.18 kernel development
Source: link
What works / not work:
K05TS - 1st version P8000: fingerprint and mainspeaker not working (sound is working with headphone or during a call)
K05TE - 2nd version P8000: maybe mainspeaker problems
K06TE - 3rd version P8000: everything work well
Some technical background:
K05TS - 1st version P8000: Lollipop bootloader
K05TE - 2nd version P8000: Marshmallow bootloader version 1
K06TE - 3rd version P8000: Marshmallow bootloader version 2
You can flash all stock rom to all devices.
If you flash a custom recovery or a custom kernel you have to use matching bootloader.
3.10 custom kernel = Lollipop bootloader
3.18 custom kernel = Marshmallow bootloader version 2
there are no custom kernel for bootloader marshmallow version 1 (k05te) - no kernel source
!!!!! Backup IMEI first !!!
Kernel will work only with Roms that based on K06TE.
You have to flash the stock Android 6 from K06TE first.
After this bootloader is matching to k06te based kernel.
Download: Stock K06TE Android 6.0 rom
Unlock bootloader and flash recovery.
I need some help to fix the audio routing.
Sound works well on K05TS with Stock Android 6.0 from K05TE Android 6.0 but there is no kernel source
!! boot.img-kernel.img = zimage = kernel only !!

@walter79
K05TE - 2nd version P8000: maybe mainspeaker problems ---> FingerPrint Sensor is working for this version?

boka18 said:
@walter79
K05TE - 2nd version P8000: maybe mainspeaker problems ---> FingerPrint Sensor is working for this version?
Click to expand...
Click to collapse
Dont know. Some should test it.

walter79 said:
Dont know. Some should test it.
Click to expand...
Click to collapse
Neither the recovery nor the boot img (kernel) works for K05TE - 2nd version P8000.
When I flash the recovery nothing changes (looks like the stock recovery), when i flash boot.img (through other recovery) I get bootloop.

Flashed this on my K06TE with the stock 6.0 rom - everything works (including fingerprint), but there is a wake up bug where most of the time instead of showing the lock screen the phone just lights up black, then goes back to sleep. Takes about 2-4 tries for the actual lock screen to show up.

lostmysaves said:
Flashed this on my K06TE with the stock 6.0 rom - everything works (including fingerprint), but there is a wake up bug where most of the time instead of showing the lock screen the phone just lights up black, then goes back to sleep. Takes about 2-4 tries for the actual lock screen to show up.
Click to expand...
Click to collapse
Maybe display wakeup delay is to short.
https://github.com/walter79/android...mmit/7e2a8d33a3b7c0ccc416efdf456a79e94b231239
We should test 200 ms.
Edit:
New kernel with 200 ms uploaded. Only for k06te.

boka18 said:
Neither the recovery nor the boot img (kernel) works for K05TE - 2nd version P8000.
When I flash the recovery nothing changes (looks like the stock recovery), when i flash boot.img (through other recovery) I get bootloop.
Click to expand...
Click to collapse
You have to flash stock Android 6 from K06TE first !!

walter79 said:
Maybe display wakeup delay is to short.
https://github.com/walter79/android...mmit/7e2a8d33a3b7c0ccc416efdf456a79e94b231239
We should test 200 ms.
Edit:
New kernel with 200 ms uploaded. Only for k06te.
Click to expand...
Click to collapse
Still the same problem, though now it seems to work every other time (like blackscreen-lockscreen-blackscreen-lockscreen and so on).

lostmysaves said:
Still the same problem, though now it seems to work every other time (like blackscreen-lockscreen-blackscreen-lockscreen and so on).
Click to expand...
Click to collapse
Can you test 400ms ?

walter79 said:
Can you test 400ms ?
Click to expand...
Click to collapse
It seemed ok at first but after like 20 button presses the black screen happened again
After that i decided to spam the button faster (in the name of science) and got a weird graphical glitch that looked like some liquid being poured inside the screen lol. Might be a different problem, i dunno.
I cant replicate any of these problems on stock boot and i just noticed that the wakeup delay is noticeably longer on it. Maybe try 800ms?

lostmysaves said:
It seemed ok at first but after like 20 button presses the black screen happened again
After that i decided to spam the button faster (in the name of science) and got a weird graphical glitch that looked like some liquid being poured inside the screen lol. Might be a different problem, i dunno.
I cant replicate any of these problems on stock boot and i just noticed that the wakeup delay is noticeably longer on it. Maybe try 800ms?
Click to expand...
Click to collapse
600ms

walter79 said:
You have to flash stock Android 6 from K06TE first !!
Click to expand...
Click to collapse
r u surw? wont i brick it?

The kernel installed through TWRP?

boka18 said:
r u surw? wont i brick it?
Click to expand...
Click to collapse
I flashed all Stock roms on my K05TS and i have no problems to go back to a working rom.
You have to know how to restore your EMEI. It is possible that you can maybe lost it during flashing different stock roms.
Supervaiser said:
The kernel installed through TWRP?
Click to expand...
Click to collapse
Yes. or via fastboot if you bootloader is unlock.

walter79 said:
I flashed all Stock roms on my K05TS and i have no problems to go back to a working rom.
You have to know how to restore your EMEI. It is possible that you can maybe lost it during flashing different stock roms.
Yes. or via fastboot if you bootloader is unlock.
Click to expand...
Click to collapse
I did everything as u said and it works. The wake-up bug is gone! Wow Good job!
Bug - Fingerprint sensor not found (as default).
One question: Will the battery bug with the 15% problem drop remain?

boka18 said:
I did everything as u said and it works. The wake-up bug is gone! Wow Good job!
Bug - Fingerprint sensor not found (as default).
One question: Will the battery bug with the 15% problem drop remain?
Click to expand...
Click to collapse
k05te ? or k05ts ? or k05ts updated to k06te or k05ts updated to k06te ?
15% bug not testet

walter79 said:
k05te ? or k05ts ? or k05ts updated to k06te or k05ts updated to k06te ?
15% bug not testet
Click to expand...
Click to collapse
5te updated to 6te
But i did not managed to install recovery. something went wrong so i reflashed 5te android 6, put recovery and restore los13.
Can you provide recovery that works with 6te?

boka18 said:
5te updated to 6te
But i did not managed to install recovery. something went wrong so i reflashed 5te android 6, put recovery and restore los13.
Can you provide recovery that works with 6te?
Click to expand...
Click to collapse
Did you flash k06te MM Rom. ? Recovery is attached in first post. Did you Fingerprint ever worked with a stock rom?

walter79 said:
Did you flash k06te MM Rom. ? Recovery is attached in first post. Did you Fingerprint ever worked with a stock rom?
Click to expand...
Click to collapse
nope. never worked the fs.

walter79 said:
600ms
Click to expand...
Click to collapse
I put on the core K06TE stock Android 6.0. No error awakening. fingerprint scanner works. Sound works. WiFi and BT work. Others no errors. I will be tested for battery failure after 15%

Upgrade from AEX 4.6 to RR 6.0 (kinda lost) ?

Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP

sixth.pr1m3 said:
Since you are currently on AEX 4.6, I believe that the offline charging is not working. Even I am on 4.6 and I have tried few Oreo ROMs. I think if you are on 1.76 or 1.70 baseband, you are good to go, flash RR.
Question is do you really want offline charging to work? Personally I'm not going to go through all this hassle for just making the offline charging work. I have been using AEX 4.6 without offline charging for a long time and I don't care if my future ROM has it or not.
Yeah, you can flash baseband using fastboot or TWRP
Click to expand...
Click to collapse
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
EDIT: Alright, I installed "Arnova's Pixel2Mod v6" and I now have a working camera. Do not mind my question. I also noticed that you posted the link (on another thread) where I found the Camera mod, so thanks again for your help!

Sinero said:
Thank you for clearing my doubts.
I flashed RR, went smoothly, everything seems to work as planned except for the camera : I do not have the HDR option, and I think a lot of options are missing. Do you have any ideas about that?
As you said offline charging is still not working, and I do not really care neither.
Click to expand...
Click to collapse
Using GCam? HDR option should be working, try the recommended one's from here: https://www.celsoazevedo.com/files/android/google-camera/
Slow motion is not working. If you have dark video issue, use OnePlus 5T Cam.

Thanks again for that link, seems like I edited my last post while you answered !
Here is a little feedback after ten days of usage :
My camera started acting up : usually when going through the camera's gallery the application will crash. I will try another Gcam.
I also noticed that my calls are not working. I can dial someone but when they pick up the call we cannot hear each-other. Does anyone have experienced this kind of situation ?
Everything else is working smoothly, better than under AEX 4.6, sadly with those two main problems I may have to try something else.

Sinero said:
Hello everyone,
It has been a while since I toyed with my Zuk Z2 and I totally missed the Oreo train.
I would like to update my custom ROM with the newest Resurrection Remix OS but some things are still quite unclear.
I saw a lot of talk around updating the baseband version to enable offline charging. And some users also recommend to flash a stock ZUI Oreo ROM before flashing any custom Oreo.
My question is : can I update only my baseband using (fastboot or TWRP) and then directly flash RR 6.0 using the standard full wipe ?
Does that make sense or do I have to take the extra step with the stock ROM ? If so : which version should I install ? 1.9 and then let the OTA do their job ? Will it lock my bootloader again ?
Finally, what step should I take to make this upgrade as easy as possible ?
I am sorry if those questions have been asked lots of time before but I can't figure a clear answer about all of this,
Cheers,
Click to expand...
Click to collapse
For offline charging flash at beast kernal

New front camera (Omnivision OV13B10) doesn't connect with custom Q, on RN8

UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull

Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)

loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7

Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...

loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.

Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it

loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?

Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)

loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?

Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't

loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11

Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important

loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?

Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work

loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results

Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it

Try this bro

Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.

temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public​

Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view