Hey,
I've created a small magisk module, with that you can use the Argument Reality function inside the Google Camera.
It works on AOSP 8.0 Beta and Stable, maybe it also works on nougat.
When you want to test it on other devices than the Mi A1, please don't forget to make a backup even if bootloop and such things are very unlikely.
Wehen you have a device where it also works you are allowed to create a thread, only condition link me and very important Arnova8G2 because without his work it would not be possible.
Installation instructions:
The modules can easily flashed inside the Magisk Manager or with TWRP.
To get it fully working you have to flash both modules
Downloads:
All in one version:
https://forum.xda-developers.com/mi...re-modded-google-camera-t3720269/post75090632
ARcore Basic files:
https://drive.google.com/folderview?id=1C3pylJpeK9bc93L56v1JWrjJNXnNbU06
ARcore Basic files V2:
https://drive.google.com/file/d/16YyJN1PTDMZ5WPQ_F2VFZuyTJlAOmAyi/view?usp=sharing
Apps Module:
https://drive.google.com/file/d/12t5jRzlEM0tz1mkyKqjwu0RS8yZ37IeY/view?usp=sharing
Apps Module V2:
https://drive.google.com/file/d/19rtu2nUAcH2WKCBbGbm2F75uXsfwKXt4/view?usp=sharing
Do not thank me, just thank him @Arnova8G2
Thanks for your contribution! Will try as soon as I get the oreo beta working on my phone.
Unable to flash via magisk
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
fosco_ said:
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
Click to expand...
Click to collapse
My storage is also encrypted and it works.
AnnePunk said:
My storage is also encrypted and it works.
Click to expand...
Click to collapse
What version of Magisk and Magisk Manager?
fosco_ said:
What version of Magisk and Magisk Manager?
Click to expand...
Click to collapse
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
AnnePunk said:
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
Click to expand...
Click to collapse
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
Had the same bug, reinstall magisk with the Magisk Manager, reboot and try again.
I can flash other zip.. But these two can't be flashed on magisk
Rakibboss said:
I can flash other zip.. But these two can't be flashed on magisk
Click to expand...
Click to collapse
Hmm for me it works
Whatever, i managed to do it via this method
https://forum.xda-developers.com/redmi-note-3/themes/mod-updated-6-11-17-google-camera-hdr-t3701190
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
"I can flash other zip.. But these two can't be flashed on magisk"
You must create an folder "magiskmanager" on internal sd card...then it works
I will try for Android Nougat. Thank you
It doesn't work on nougat .i tried
Hello, install without problems, but I would like to know which Gcam application exactly should I I must use, Thanks.
anyone got it working ?
jeneb11 said:
anyone got it working ?
Click to expand...
Click to collapse
Not working on Redmi Note 4 stock global miui9 with camera2 api enabled. Tried with both magisk, and TWRP, AR Stickers stoped.
how can you install magisk on oreo? when i booted to the twrp, it asks for my pattern and when i draw the pattern, it says pattern failed. so please tell me how can you install magisk on oreo
jigs4wkiller said:
Hmm for me it works
Click to expand...
Click to collapse
Which magisk version??
Related
Today I installed Oreo and am now stuck with default recovery. Did someone manage to install TWRP and SuperSu? Which versions?
I don't want to make a mistake and brick my system...
Der-Knuffi said:
Today I installed Oreo and am now stuck with default recovery. Did someone manage to install TWRP and SuperSu? Which versions?
I don't want to make a mistake and brick my system...
Click to expand...
Click to collapse
Latest blu_spark TWRP should work. For root, I'd recommend Magisk (latest beta) rather than SuperSU.
Explorer23 said:
Latest blu_spark TWRP should work. For root, I'd recommend Magisk (latest beta) rather than SuperSU.
Click to expand...
Click to collapse
What is the advantage of Magisk over SuperSu? Or simply because it works?
Der-Knuffi said:
What is the advantage of Magisk over SuperSu? Or simply because it works?
Click to expand...
Click to collapse
It doesn't break SafetyNet so you can still use banking apps etc. Plus it supports modules which can bring some addition functionality. And it simply works [emoji4]
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
It doesn't break SafetyNet so you can still use banking apps etc. Plus it supports modules which can bring some addition functionality. And it simply works [emoji4]
Click to expand...
Click to collapse
Which version do I need? 14.0 from here?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or a newer?
I found a how-to-install, but it sounds like rocket sience compared to SuperSu:
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
Der-Knuffi said:
Which version do I need? 14.0 from here?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or a newer?
I found a how-to-install, but it sounds like rocket sience compared to SuperSu:
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
Click to expand...
Click to collapse
Sorry, I can't provide more info at the moment as I haven't tried this myself yet (still on AOSPA).
It seems that it is a bit more work right now to get Magisk working in Oreo, but if you follow that guide to the letter it should be fine.
I'm planning to flash OOS 5 and Magisk tomorrow so I can report back then.
Sent from my OnePlus 3 using Tapatalk
Der-Knuffi said:
Which version do I need? 14.0 from here?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or a newer?
I found a how-to-install, but it sounds like rocket sience compared to SuperSu:
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
Click to expand...
Click to collapse
latest 14.3 beta
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
that thread is out dated, the current OOS Oreo now supports Magisk latest beta
so just flash rom and then Magisk 14.3 , and if you want custom kernel do it after that...
after flashing rom flash TWRP again then reboot to TWRP again and flash Magisk and anything else you want.
Der-Knuffi said:
Which version do I need? 14.0 from here?
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or a newer?
I found a how-to-install, but it sounds like rocket sience compared to SuperSu:
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
Click to expand...
Click to collapse
Use the 14.3 beta version and simply flash it. That tutorial was for Open Beta 25 or 26 when Magisk was broken on those builds. Open Beta 27 and up fixed that so now you just need to flash it. Don't know if 14.0 works but I wouldn't try it.
I just installed latest OOS 5.0 with blu_spark TWRP 8.52 and I rooted with latest Magisk beta 14.3. Everything working well.
*Before starting I backed up all the data on my 'internal data' partition.
1. Booted to recovery
2. wiped everything EXCEPT for 'internal storage' and then restarted to recovery
3. Copied full.zip and magisk.zip to internal storage
4. Installed full.zip and magisk.zip, in that order
5. Wiped dalvik and cache and then rebooted to system
In the security & fingerprint menu, the phone says it is encrypted but I still have everything that was on internal data partition.
All the best
Anyone had any success flashing Magisk on the 5T yet? I've tried + it flashes fine, but WiFi doesn't work; neither mobile data.
Semi solution:
https://forum.xda-developers.com/oneplus-5t/development/rom-freedomos-2-0-2-t3709708
The ROM comes with Magisk (I can't say first hand since I don't have a phone yet)
Yes magisk working but dont Format Data.
Hmmm, I have it without issues (I think).
Followed this post: https://forums.oneplus.net/threads/oneplus-5t-unlock-bootloader-flash-twrp-root-nandroid-efs.685403/
@Theberge43 on the 5t not the 5 right? Did you flash v14 or v14.something i.e the beta version? Thanks!
madyoda said:
@Theberge43 on the 5t not the 5 right? Did you flash v14 or v14.something i.e the beta version? Thanks!
Click to expand...
Click to collapse
On the 5T indeed. Used this link (from the mentioned thread): https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
@Theberge43 magisk code 1456 + it's fully working for you? Interesting thanks - I'll try it again as it didn't work for me!
madyoda said:
@Theberge43 magisk code 1456 + it's fully working for you? Interesting thanks - I'll try it again as it didn't work for me!
Click to expand...
Click to collapse
Here is my Magisk.
@Theberge43 nice thanks! About to try
@Theberge43 yup that worked thanks! No idea what happened the first time - possible corrupt zip or faulty flash I guess!
Maybe I spoke a tad too soon. If I reboot, the modem goes again. If I then reboot, it comes back, etc etc. Weird!
Schrotty35 said:
Yes magisk working but dont Format Data.
Click to expand...
Click to collapse
At what point should not format the data? If you are on the stock rom, you have to go on recovery and directly flash magisk?
(When i flash magisk, i reboot always on recovery...and i can't flash FreedomOS with modified TWRP or Blue_spark....)à
I actually flashed the official version and not beta. Works perfectly fine on OP5T (latest OxygenOS update).
No problems at all with magisk. Not using any guide, just flashed twrp, dm-verity patch from jcadduono, magisk 14.0
Both 4G and WiFi work as expected.
v14.3 here with no issues. Was just in a badspot for the first screen shot. Went right back to LTE
mad-murdock said:
No problems at all with magisk. Not using any guide, just flashed twrp, dm-verity patch from jcadduono, magisk 14.0
Both 4G and WiFi work as expected.
Click to expand...
Click to collapse
Dm patch not need.
can't wait to get my 5t , first thing is installing magisk and adaway
Schrotty35 said:
Dm patch not need.
Click to expand...
Click to collapse
With me i must flash dm verity to start on the system
samtab37 said:
With me i must flash dm verity to start on the system
Click to expand...
Click to collapse
Ok have you a link for working version on 5t?
Schrotty35 said:
Ok have you a link for working version on 5t?
Click to expand...
Click to collapse
Is the same as OnePlus 5: https://drive.google.com/file/d/1YMHqtyILolheUuJtjpmCbL6hHKD5MQo0/view?usp=drivesdk
I try new version (v6) of no verity but don't work, for me this file is the only way to boot
Envoyé de mon ONEPLUS A5010 en utilisant Tapatalk
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
equlizer said:
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
Click to expand...
Click to collapse
Use the Magisk Module Busy Box for Android NDK. Works great.
felosisman said:
Use the Magisk Module Busy Box for Android NDK. Works great.
Click to expand...
Click to collapse
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
equlizer said:
Where do i find it? thx
Click to expand...
Click to collapse
Open Magisk Manager, go-to Downloads, find and download "BusyBox for Android NDK 1.27.2", reboot and profit.
Noob question but what is BusyBox and what's it's purpose
mackentosh said:
Noob question but what is BusyBox and what's it's purpose
Click to expand...
Click to collapse
Busybox allows programs to perform actions on your phone using Linux commands. So some apps require it to run some commands and wont work without it.
equlizer said:
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
Click to expand...
Click to collapse
You shouldn't be getting that error anymore if you're using the latest Magisk release. He released version 15.0(1500) a couple days ago, but that was actually fixed in the last beta 14.6.
You would have to reflash your Kernel boot and dtbo and repatch though with the new version. I just used the Magisk Uninstaller script in TWRP, flashed the latest zip of flash Kernel then latest Magisk in TWRP and all good.
I tired all arm64 custom roms for moto z play, some arm, tried mixing with all kernels and magisk/without magisk.
And i can't pass safetynet on all these configurations
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
But I have passed with magisk
Artim_96 said:
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
Click to expand...
Click to collapse
But on my old phone, i was using custom roms (not certificed), and SN was passing.
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
With ROM you using?
dawidrejowski said:
With ROM you using?
Click to expand...
Click to collapse
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
dawidrejowski said:
But on my old phone, i was using custom roms (not certificed), and SN was passing.
Click to expand...
Click to collapse
How old of a phone? My last phone (HTC One M8) passed on custom ROMs because it didn't seem to report the bootloader was unlocked. But I have safety net passing on custom ROMs on my Z play thanks to magisk and universal safteynet fix beta 5.
mijing said:
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
Click to expand...
Click to collapse
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
KrisM22 said:
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
Click to expand...
Click to collapse
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
mijing said:
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
Click to expand...
Click to collapse
That is a very old one - could you please attach it to your post for a few minutes? TIA!
KrisM22 said:
That is a very old one - could you please attach it to your post for a few minutes? TIA!
Click to expand...
Click to collapse
Yes it is too old but till now it is usefull as you can see
mijing said:
Yes it is too old but till now it is usefull as you can see
Click to expand...
Click to collapse
I found it up on
https://androidfilehost.com/?fid=673368273298984533
is that it?
I'll go try it on AOSP 8.1 Alberto97
Yes,It Is. but I dont Know about AOSP Is it will work or not
mijing said:
Yes,It Is. but I dont Know about AOSP Is it will work or not
Click to expand...
Click to collapse
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
KrisM22 said:
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
Click to expand...
Click to collapse
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English? )
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
Edit: Never mind I saw what Rom you were running.
mijing said:
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English )
Click to expand...
Click to collapse
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Im glad you have fix your problem
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Check for Bluetooth and wifi if they are working correctly. I flashed the fix on AOSP and my Bluetooth crashed, needed to restore backup.
So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.
NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's
NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.
NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename
NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.
In the meantime, is someone running GSI as a daily driver?
sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.