Database Develop

camera app

hi everybody,
I'm running Lineage Os 14 on moto g Thea, and the camera has a problem when activating HDR, it always gets jammed. Plus when opening gallery things get very slow. So I turned to other apps and found two options:
- google camera 2.7: works fine, but it still is a little slow in opening and rotating to landscape.
- one plus camera 2.5.4: it is very fast, but the flash is disabled most of the time because it reads excessive heat (impossible).
anyone has experience in this or can suggest a camera app?
cheers

update
the flash issue on one plus camera is gone after some use.
nevertheless, it has a problem with the panorama image composition, does not work properly so all panoramas are screwed up..

Alternative method but can help in something, maybe...
Hello my friend, I'm using google translate to communicate with you.
I also use lineage 14.1 however I use a camera and gallery of the motorola, updated until.
But I flash the zip after GApps before the first reboot, and right after configuring it, I upgrade through the play store, and then, with a file manager, I go to the / data / app folder and find the two camera folders and of the gallery, I modify ALL permissions within these folders to 777, restart and I have a gallery and camera 100% functional.
Optionally there are other options, but that's how I do it.
If you want to try, I'll leave the zip LINK that I got in a part of the forum that I can not remember where else.
Remember that I have no responsibility for any damage, it is a way of trying to help, but as I only tested on mine, I have no guarantee of anything
It was testing on mya the XT1078 with lineage 14.1 and root (of course), because without it I would have no way to modify the permissions.
Unfortunately my account is new so I can not pass the link to you, then remove the spaces and join to form a link:
Download: https: //mega.nz/ #!vY5w3BKa!fx- wqPKS-tXvCyrQqIAA7MwjU_ 1QluMMxfkg7C2CL60
I wish luck and success there.

Needing to modify the latest Camera NX APK

I have been using the latest Camera NX (arm obviously) on my phone for a while now.
I recently changed two build.prop values and the app now crashes on launch every time, even after reinstalling.
The keys I changed were "ro.product.model" and "ro.product.manufacturer"
I gave these the value of "Pixel XL" and "google" in order to trick my nexus 6 into thinking that it's Pixel XL and enable certain features like trusted voice and Google Lens.
One of both of these changes must have made the app incompatible with my phone.
However, I feel like it should be easy to modify the Camera NX apk file to allow it to run on a "Pixel XL" since it works with the hardware fine, I believe it's just a matter of values matching.
I've never done anything like this before though and don't quite no where to start. I've opened the apk file with an 7-Zip to see if I could see anything that would stick out, but I just don't know what I would be looking for.
Any help would be appreciated as I would love to be able to continue using my favorite camera app and also have Google lens and trusted voice working.
Thank you
Edit:
The Camera NX apk file can be found here at the bottom of the site
https://chromloop.com/2016/12/updat...g-fixes-performance-improvement-apk-download/

Does not function on phones with Toybox - BLU STUDIO XL 2

Thank you for all you hard work, I have been a user for many releases prior and love that your software has always been "there and working well". So why only speak up when I have a problem, so for that I apologize.
I have managed to obtain a version of Xposed (Systemless) ported for Magisk installed on my phone (SDK 23) and while Magisk lists Xposed in its installed module list with a check box saying it is active, the Xposed menu shows the green notification area that says it is working, when I install XprivacyLua, and while after the installation of XprivacyLUa, in the Modules section of Xposed there is a check box showing that XprivacyLua is installed and active, the problem is that the Xprivacy app thinks it is not loaded. I sent trace logs captured via adb to the Xprivacy developer and he says that Xposed believes the XprivacyLua app is not installed (even though all indications are that it is active).
Someone who knows more about this than me stated my problem was likely with Toybox being on the phone and something about symlinks where he gave another suggestion about loading Busybox and then following with loading a BusyBox binary zip package via TWRP. All this does is render me not able to access MagiskManager any longer.
Do you know anything about such an issue and how I might get around it? I am saddened that using this valuable tool is being made so difficult from all the new hardware changes. I normally stick with age old phones, but accidents happen, the old one's cracked and my new one won't seem to work with Xposed.
Thanks!
BLU STUDIO XL 2 16/2G
MT6737
ARMv7 Processor rev4 (V71)
armv71

Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.

Donphillipe said:
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Click to expand...
Click to collapse
What about making system run in permissive mode?
have you tried?
I have not "jumped" from superSU to majisk so my method is to use superSU.
I have a recovery install package that sets file in place to make permissive and force superSU to install systemless.
you can give a try.
the updater-script prints out a message it was made for "blu tank xtreme pro" but it is fine for other phones too. I made it for/ with other dev who wanted to have one step to make root and permissive.
I do not know how will respond to majisk, so better off to try ununstall that first, and start fresh.

[MAGISK] Ambient EQ Tweak

Hey all,
Just wanted to share a simple Magisk Module that tweaks the Ambient EQ on our phones to behave more like Apple's True Tone feature. This idea and module was originally created by @MishaalRahman and published here. As you can see the article was published in November 2019, and the structure of Magisk Modules has since changed. So, the module that you can download from that article no longer works. I've simply updated the module to be compatible with the new Magisk Module file structure and function correctly on our phones.
Instructions and Notes:
Note: This module was originally created for the Pixel 4 (Flame). Due to the Pixel 4 XL (Coral) using a different panel, this module may have unintended effects on screen color and gamma that I have not been able to test. Give it a shot if you'd like, but YMMV.
Install via Magisk Manager or flash the .zip using your favorite Kernel Manager and reboot.
The module has been submitted to the Magisk Module Repo, where it will be able to be downloaded directly from the Magisk Manager app, but it is awaiting approval.
Download (AFH)
Original Author: @MishaalRahman
Original Module and Associated Documentation: https://www.xda-developers.com/google-pixel-4-ambient-eq-tweak/
Source: https://github.com/Alcolawl/AmbientEQTweak

Thanks! I really appreciate it.
Like two months without the module working and you fixed it.

After normal installation, the performance of some apps is significantly reduced.

gyuuuu said:
After normal installation, the performance of some apps is significantly reduced.
Click to expand...
Click to collapse
I haven't noticed it

Alcolawl said:
Hey all,
Just wanted to share a simple Magisk Module that tweaks the Ambient EQ on our phones to behave more like Apple's True Tone feature. This idea and module was originally created by @MishaalRahman and published here. As you can see the article was published in November 2019, and the structure of Magisk Modules has since changed. So, the module that you can download from that article no longer works. I've simply updated the module to be compatible with the new Magisk Module file structure and function correctly on our phones.
Instructions and Notes:
Note: This module was originally created for the Pixel 4 (Flame). Due to the Pixel 4 XL (Coral) using a different panel, this module may have unintended effects on screen color and gamma that I have not been able to test. Give it a shot if you'd like, but YMMV.
Install via Magisk Manager or flash the .zip using your favorite Kernel Manager and reboot.
The module has been submitted to the Magisk Module Repo, where it will be able to be downloaded directly from the Magisk Manager app, but it is awaiting approval.
Download (AFH)
Original AuthorMishaalRahman
Original Module and Associated Documentation:https://www.xda-developers.com/google-pixel-4-ambient-eq-tweak/
Source:https://github.com/Alcolawl/AmbientEQTweak
Click to expand...
Click to collapse
Somehow after enabling this module on Android 11 beta 2.5 phone goes crazy.
I get delayed sms, delayed emails, app in the play store don't download and weather doesn't show.
Disabling an restarting fixed it , enable, restart, problem comes again

peikojose said:
Somehow after enabling this module on Android 11 beta 2.5 phone goes crazy.
I get delayed sms, delayed emails, app in the play store don't download and weather doesn't show.
Disabling an restarting fixed it , enable, restart, problem comes again
Click to expand...
Click to collapse
Wild stuff. I'd assume it's because you're using Android 11 beta. The way this works is basically an overlay for System UI, which I'm assuming has seen at least some moderate changes from Android 10 to Android 11. I'm not entirely sure why it would break things like SMS, but I would definitely assume that this isn't compatible with Android 11. This will be something I'll have to work on when Android 11 officially drops.

Alcolawl said:
Wild stuff. I'd assume it's because you're using Android 11 beta. The way this works is basically an overlay for System UI, which I'm assuming has seen at least some moderate changes from Android 10 to Android 11. I'm not entirely sure why it would break things like SMS, but I would definitely assume that this isn't compatible with Android 11. This will be something I'll have to work on when Android 11 officially drops.
Click to expand...
Click to collapse
Yeah it doesn't make any sense but at least with this beta it does that.. and it is totally easy to reproduce for me...

Any update to make it work properly with Android 11? Just asking.
Thanks!

peikojose said:
Any update to make it work properly with Android 11? Just asking.
Thanks!
Click to expand...
Click to collapse
Unfortunately I may just abandon this idea. It turns out that this module was actually responsible for the frustratingly horrible performance I was experiencing when using Snapchat. Like the phone totally locking up for 5-10 seconds sometimes for seemingly no reason. I know Snapchat is a massive piece of ****, but unfortunately, my tries to convince several groups of friends to move to a different app have been unsuccessful. After removing this module, performance was restored. Because of this, along with other reports of sluggish performance when using this module, I'll most likely discontinue working on this for Android 11.

Alcolawl said:
Unfortunately I may just abandon this idea. It turns out that this module was actually responsible for the frustratingly horrible performance I was experiencing when using Snapchat. Like the phone totally locking up for 5-10 seconds sometimes for seemingly no reason. I know Snapchat is a massive piece of ****, but unfortunately, my tries to convince several groups of friends to move to a different app have been unsuccessful. After removing this module, performance was restored. Because of this, along with other reports of sluggish performance when using this module, I'll most likely discontinue working on this for Android 11.
Click to expand...
Click to collapse
Yes. I was one of the ones that reported problems even with sms after using this module.
So sad! Thanks anyway

com.adobe.ims.accountaccess (Adobe Account Access) seems to detect Magisk, even while hidden.

H! So I am actually unsure where to post this..
Here's hoping you can figure something out and not be mad at me if this is the wrong place to post this.
Initially, i was going to post this as a Bug report on Github. However, I figured this was not correct.
Technically speaking this also isn't really an issue with magisk itself, more that adobe might have found a way to circumvent magisk anti detection methods.
In short: The App "Adobe Account Access" (com.adobe.ims.accountaccess on the play store: https://play.google.com/store/apps/details?id=com.adobe.ims.accountaccess) seems to have found a way to detect magisk and/or root, even though root detection is hidden in magisk.
The App just displays a prompt, saying "Device not supported. Sorry, your phone is not supported for Adobe Account Access.", even though the device used should be supported.
I checked with adobe community support on whether my Phone is supported or not and according to them, it should indeed be supported: https://community.adobe.com/t5/acco...-access-app-device-not-supported/m-p/11696613
I suspect they have found a way to get around all magisk anti detection methods and i would be grateful if someone would be kind enough to check if there is a workaround or if magisk's detection prevention needs an update.
Unfortunately, i don't have much more to say other than that..
There aren't any magisk log entries that would indicate something went wrong (only entries mentioning the app are"i" loglevel, one coming from hide_list_add and one coming from proc_monitor).
I could not find anything out of the ordinary in the logcat, although i suppose i could be more thorough with my search.
My technical/general info would be:
Magisk Version used: 22.0 (22000) (18)
SafetyNet integrity: Both basicIntegrity AND ctsProfile = pass; evalType = BASIC
ROM used: OxygenOS 10.0.11.GM21BA
Android version: 10
Device name: OnePlus 7 Pro
"Adobe Account Access" App version: 1.6
+++ Please feel free to ask for any additional info in case I missed it +++
Thanks in advance for any productive suggestion!

When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list, and with the Magisk app unhidden.

Didgeridoohan said:
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list.
Click to expand...
Click to collapse
Oh? That is peculiar.. Damn, that implies an issue somewhere else i reckon ://
It displays it immediately after launching the app. The very first screen..
What phone and which OS (/ROM) are you using? Might just be that my phone is genuinely not supported and the folks over at the adobe community forum lied when saying my phone should be compatible..
Also, which android version are you on if you don't mind me asking?

You don't have any modules installed? No edxposed or lsposed, or magisk modules?
Have you tried root detection apps like Root Beer Fresh to see if indeed the app is unable to detect root? If you try any such app, remember to add it to the Magisk Hide list beforehand, otherwise the app will clearly detect root.

It's a OnePlus 3T with Android 9 ArrowOS. As stated above, it could very well be a module, like EdXposed. Or a root app, or a file or folder on your device, or something completely different.
It's not detecting Magisk at least, that's for sure...
General root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

@Barrel Titor
Samsung Galaxy S7 Custom 9.0 Pie, Magisk 22 root with random name, application without hiding works fine.

Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.

Barrel Titor said:
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Click to expand...
Click to collapse
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.

mario0318 said:
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
Click to expand...
Click to collapse
I cannot find any results using this search term on google other than my own post on the adobe community forums.. This one: https://community.adobe.com/t5/acco...access-app-device-not-supported/td-p/11695914

@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?

Barrel Titor said:
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Click to expand...
Click to collapse
Well, the well known magisk module MHPC or Magisk Hide Props Config comes to mind. You can change device fingerprints and maybe also give the Device Simulation feature a go, or custom edit any range of configurable props.
You could do so without the module editing the build.props yourself. Or if you stick with edxposed and deal with not having magisk manager's hide enabled, perhaps any of the device spoofers on the xposed repo could fool the app. Or Sudohide if you set Adobe app to hide from any and all apps that are root relevant. May also consider removing directories in your internal and removable storage for things like TWRP or PBRP, Titanium Backup, xposes, etc, you know, things that a simple media scan looking for any sign of root apps might pick up.
But for now, I'd give MHPC a try and change device fingerprint and maybe enable device simulation if simple fingerprint change doesn't work.

I'm having the same issue on a rooted OnePlus 8T

Same for me on op7 pro. Hiding with somiko but Adobe still not working. Nor could I bypass square, it notes root when it pairs Bluetooth