Related
Hello everybody,
just started a temporary sale for NFC ReTag PRO...
Use any NFC tag (write protected and re-writable) to trigger multiple functions on your device!
You can use this app to associate multiple functions (e.g. toggle Wlan, Bluetooth, Mobile Data, Airplane mode, start navigation,run Tasker task, launch any installed app, use media buttons, call a phone number, add a timestamp, calendar entry and many more) to a specific NFC Tag via an app internal database.
Get it NOW and save some money
Link to the Support thread:
forum.xda-developers.com/showthread.php?t=1477138http://
Free version also available !
Nice and first! Downloading now...
Text to speech bug
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
GenePaton said:
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
Click to expand...
Click to collapse
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
ascsa said:
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
Click to expand...
Click to collapse
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
GenePaton said:
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
Click to expand...
Click to collapse
No Problem ... ... but let´s move to the official support thread (http://forum.xda-developers.com/showthread.php?t=1477138&page=100) ...because this is an old thread ...NFC Retag PRO is currently NOT on sale ... and we shouldn´t confuse the users ...
Just to clarify for any other readers, my e-mail answer to your last post :
The Galaxy S3 GT-I9300 (international model) is one of our main testing devices. Not sure if, there is a problem with the Vodafone Rom or the Australian T model, but it´s working fine here on 4.1.2.
Had a short look at our code and the official api and everything seems fine ... but without a log file or better a device on which we could reproduce the error it´s nearly impossible to be sure ...However, you mentioned it happens with other apps, too , so I would bet on some Vodafone "enhancements" ...
Btw. have you tried the Samsung TTS engine (settings--> language& input -->text-to-speech output--> preferred engine) instead of the Google engine?
I notice there are several versions of tasker. Which do I need?
Muscipula
Sent from my SM-G903F using Tapatalk
I read the module FAQ and the code page and tried out module & xposed code and I was not able to get around my problem. I'm not sure that it was supposed to get around my problem though, but I was hoping to get your take on things. I can't find much data, though I can find a few people asking the same questions as I.
I installed an android 4.3 ROM (http://forum.xda-developers.com/showthread.php?t=2121063) on my phone and tried to connect to an OpenVPN based VPN provider. I got an error and contacted their support. Part of that process was to try another app, so we tried the OpenVPN COnnect app, the official OpenVPN app. I got a different error with that app.
One says that "your android firmware does not support the VPNService API("
OpenVPN Connect says "Sorry, due to a known issue in this version of android, it is not possible to gain permission to open a VPN tunnel"
There seems to be a few problems popping up with OpenVPN based VPNs in various Android 4.x OSs, but none complaine about 4.3 specifically. Usually they complain about 4.4 or back when 4.0 and 4.1 were new. I found this article talking about it on OpenVPN, and they're just pointing the finger, but I can't find the actual bug referenced:
https://forums.openvpn.net/topic13772.html
I came across your code on this page:
https://code.google.com/p/ics-openvpn/wiki/FAQ
And decided to try loading xposed and your module after emailing OpenVPN Connect and receiving a response right away. The guy who replied seemed to think the error is related to the fact that the confirmation acknowledgement dialog is not able to be summoned. I figured maybe the ROM wasn't bypassing it properly or missing some part of it, so I tried your way of bypassing it.
After loading xposed and your module, and selecting the 2 VPN apps, I still get the same results.
What are your thoughts? Should I give up and find a new ROM?
What are you talking about? If you're asking about a specific module (looks to me that way,) you should do that in the appropriate thread.
After some more research and experimentation yesterday, it's looking more like those OpenVPN clients that "support" the VPNServiceAPI actually *require* it, and that annoying/nasty little dialog that google enabled to "protect" the user just serves to piss off advanced users like me. This is my hypothesis at this point, though I have not confirmed this. I suspect this because I just tested on Jelly Bomb, a 4.1 based ROM and see the same results so far.
As far as what I was talking about in my OP, I copy/pasted an email to the author of the xposed module here and tried to reformat it to fit the message board, and apparently I missed a few pronouns. By far not the most egregious use of the English language I've seen on these boards, so what's with the attitude? I don't see specific sub forums for each and every module, so I don't get what you're implying. I only saw the one xposed board, so where else was I supposed to post?
No attitude, I honestly didn't understand how your issue was related to the Xposed framework. I just searched the repo for "VPN" and now see what you're talking about.
The Auto VPN Dialog Confirm doesn't have a thread here on XDA. Reading your post again, you're trying to use Xposed to fix a bug with the app if I'm not mistaken? I'd first try checking the logcat and forwarding that to the author of the VPN app if you haven't already.
I can't answer the rest of your questions since that's up to the module's author. That being said, it looks like a module specific question/request, not a framework query.
My understanding of the issue described here is different, probably because I'm trying to solve the same problem On the other hand, I'm not on ICS anymore, but am using Sammy 4.1.2 stock with DorimanX Kernel 8.43 at the moment.
OpenVPN should be usable for establishing a connection on boot. Out of the box, this creates a dialog to trust this application. Even though I trust it and confirm, there is no way of saving that preference permanently. It seems to be kept for a while (disconnect / reconnect doesn't trigger it again at least ) Therefore, it always reappears each time I boot.
The only possible solution I could find was the Xposed Module "Auto VPN Dialog Confirm" - the same module mentioned by the OP.
I used it together with the OpenVPN Client by colucci.web.it (paid version in my case, because I also wanted TAP support and auto connect functionality as well as the option of controlling it via Tasker).
After installing "Auto VPN Dialog Confirm" it recognized the installed OpenVPN client and offered to allow VPN API connections from it without confirmation. The VPN client also has an option to automatically create connections when Wifi is up and allows to be triggered either when seeing a specific SSID or when connecting to a network which does not have a specific SSID. The latter one is the typical condition for untrusted networks.
Therefore, it achieves what I wanted - being able to route my traffic via OpenVPN in case I'm not connected to my home WiFi
Regarding the issue encountered on ICS - maybe getting in touch with the Developer of the Xposed module might be the best option, unless someone else has already found a solution for it. It could also be good to exactly specify the OpenVPN client used as clearing the Xposed logfile and having "AutoVPN Dialog confirm" run as the only Xposed app (and fail). Afterwards, the log hopefully contains useful feedback for the developer to investigate further (Support URL listed for the module)
Hi. I'm new to Xposed. I was wondering whether there was a module that would allow the digitiser to be kept on (even while screen is off) to accept gestures (like skip forward/backward, toggle flashlight etc). Apparently CyanogenMod on the OnePlus One does this and also the LG G3 for the double-tap feature.
If it's possible on a rom it should be possible in xposed. Xposed is very, very powerful and there is a reason it's called "xposed", as in the meaning to expose or make vulnerable, to show inner secrets.
As for whether such a mod exists right now, probably not. But that doesn't mean other xposed mods don't have such features. It probably depends on the make and model of your device.
Sent from a stolen phone!
shivadow said:
If it's possible on a rom it should be possible in xposed. Xposed is very, very powerful and there is a reason it's called "xposed", as in the meaning to expose or make vulnerable, to show inner secrets.
As for whether such a mod exists right now, probably not. But that doesn't mean other xposed mods don't have such features. It probably depends on the make and model of your device.
Sent from a stolen phone!
Click to expand...
Click to collapse
Hi. Thanks for the information. In my case it's the Samsung S5 phone and the Tesco Hudl 2. I'll try asking on their respective forums. Thanks again.
ME too
i am also waiting for such a xposed module. most of the devs tell its hardware feature all. or some tell its processor feature. and most of the people tell its a kernal fuction.
jjbro007 said:
i am also waiting for such a xposed module. most of the devs tell its hardware feature all. or some tell its processor feature. and most of the people tell its a kernal fuction.
Click to expand...
Click to collapse
Is indeed a kernel feature!
No, it's a hardware feature. If it is not implemented in hardware, it will require constant active mode.
Double tap 2 awake is hardware and software funkcion you need to have this feature implemented in kernel and you need to have screen with digi that can use this software perfect egzample xperia z1 and z1compact they have other screens and z1 can handle this feature and z1c can't have it because of hardware limitation
Hey!
Nfc-payment app called Pivo (https://play.google.com/store/apps/details?id=fi.op.android.lompsa)
Checks for developer options and if it detects them, it won't open.
Rootcloak (The Xposed module) bypasses the detection with this commit: https://github.com/devadvance/rootcloak/pull/99
So maybe @topjohnwu would include something similar to bypass the detection.
-pahapoika
pahapoika91 said:
Hey!
Nfc-payment app called Pivo (https://play.google.com/store/apps/details?id=fi.op.android.lompsa)
Checks for developer options and if it detects them, it won't open.
Rootcloak (The Xposed module) bypasses the detection with this commit: https://github.com/devadvance/rootcloak/pull/99
So maybe @topjohnwu would include something similar to bypass the detection.
-pahapoika
Click to expand...
Click to collapse
I second this idea!
Verstuurd vanaf mijn SM-G955F met Tapatalk
really needed for each payment app!
Torille!
That's a good idea indeed
@topjohnwu Magisk Queries
@topjohnwu
good idea to work on
I don't think this would be possible with magisk, magisk isn't modifying any calls like Xposed is, it's making safety net actually pass so any apps checking safety net see that. Root cloak is intercepting the check of dev options and making it return that it's off, which is out of the scope of magisk.
Sent from my MI MIX using XDA Labs
pahapoika91 said:
Hey!
Nfc-payment app called Pivo (https://play.google.com/store/apps/details?id=fi.op.android.lompsa)
Checks for developer options and if it detects them, it won't open.
Rootcloak (The Xposed module) bypasses the detection with this commit: https://github.com/devadvance/rootcloak/pull/99
So maybe @topjohnwu would include something similar to bypass the detection.
-pahapoika
Click to expand...
Click to collapse
If you have this app installed, you can send here a copy of all the folders of the app (/data/app/ && /data/app/), if its depends of an settings in a file (that i don't think) we can create an Magisk Module to force the right value, but if the detection is running in JAVA so we can't bypass it by Magisk and an XPosed module will be necessary to hooks this detection.
This would be really awesome!
This stupid app (Pivo) doesn't work for me even with MagiskHide + Xposed + RootCloak... Keeps complaining about developer options
yes
in our country new banking apps detect developer options!
we need urgently bypass this problem like magisk root hide.
I got around this issue using Tasker. Just configured it to disable Dev Options when the app in question (a nfc payments app from my bank) is opened and once i exit the payments app the dev options are re-enabled by tasker . In words of Dr. Strange "It's a simple spell but quite unbreakable"
jimbo77 said:
I got around this issue using Tasker. Just configured it to disable Dev Options when the app in question (a nfc payments app from my bank) is opened and once i exit the payments app the dev options are re-enabled by tasker . In words of Dr. Strange "It's a simple spell but quite unbreakable"
Click to expand...
Click to collapse
but in new rooted phones when disable developer option with tasker, oem lock also disabled
so phone brick in customer hand
metalgold2301 said:
but in new rooted phones when disable developer option with tasker, oem lock also disabled
so phone brick in customer hand
Click to expand...
Click to collapse
Which phones? I have a Galaxy Note 10+ and that is not the case. Once you unlock the Bootloader the OEM unlock option is greyed out, if you enable / disable the dev options it will remain unlocked unless you manually turn off the OEM unlock.
jimbo77 said:
Which phones? I have a Galaxy Note 10+ and that is not the case. Once you unlock the Bootloader the OEM unlock option is greyed out, if you enable / disable the dev options it will remain unlocked unless you manually turn off the OEM unlock.
Click to expand...
Click to collapse
yes in s10 a50 a40 you are right oem disabled
but not in a10 a20 a30 a600 a750 and etc
have any method to make unselectable oem option in developer options after root?
if we can do unselectable oem option so we can turn of developer option without effect oem lock
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