Database Develop

Auto answer v1.5 killed after gb 2.3.4

1st gingerbread update killed app
2nd update if I update will kill app
I emailed the developer
[email protected]
Sorry I can't give you a better answer, but I've been extremely busy over the past few weeks, and I just haven't had the time. The app is open source, so if you are a developer (or know a developer), feel free to try a fix. Matt
I sent him this a couple of weeks ago
Android Bridge ▼ T U E S D A Y , M A Y 1 7 , 2 0 1 1how to answer an incoming call in android 2.3 Today, I was researching on a how to answer incoming call in android 2.3 automatically. My first thought was using "ITelephony.aidl" and call the answerRingingCall(). When i looked into more details answerRingingCall() function all requires MODIFY_PHONE_STATE permission which is marked as a as "signatureOrSystem" which is mentioned here http://android.git.kernel.org/?p=platform/ frameworks/ base.git;a=commit;h=f4ece2086f3b7060edc4b93 a12f04c9af648867a and here http://code.google.com/p/android/issues/ detail?id=15031 bummer. Then thought of a another work-around and bluetooth headset popuped to my mind. In this all I had to do was to call start new intent with ACTION_UP. It worked! here is the soulution BroadcastReceiver PhoneState = new BroadcastReceiver() { @Override public void onReceive(Context context, Intent intent) { if (!intent.getAction().equals("android.intent.action .PHONE_STATE")) return; String state = intent.getStringExtra(TelephonyManager.EXTRA_ STATE); if (state.equals(TelephonyManager.EXTRA_STATE_ RINGING)) { String number = intent.getStringExtra(TelephonyManager.EXTRA_ INCOMING_NUMBER); Intent answer = new Intent(Intent.ACTION_MEDIA_BUTTON); answer.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_HEADSETHOOK)); sendOrderedBroadcast(answer, null); } return; }}; // Update on 2011-09-27 In Android 2.3.3 HTC Sensation this piece of code does not work. Reason is in 2.3.3 I found a HeadsetObserver listening for actual bluetooth plug-in event. So you need to send a Intent pretending there is a headset connected already. To fix this problem you need to send the ACTION_HEADSET_PLUG Intent before calling the above code. Intent buttonDown = new Intent(Intent.ACTION_MEDIA_BUTTON); buttonDown.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_DOWN, KeyEvent.KEYCODE_HEADSETHOOK)); context.sendOrderedBroadcast(buttonDown, "android.permission.CALL_PRIVILEGED"); // froyo and beyond trigger on buttonUp instead of buttonDown Intent buttonUp = new Intent(Intent.ACTION_MEDIA_BUTTON); buttonUp.putExtra(Intent.EXTRA_KEY_EVENT, new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_HEADSETHOOK)); context.sendOrderedBroadcast(buttonUp, "android.permission.CALL_PRIVILEGED"); Intent headSetUnPluggedintent = new Intent(Intent.ACTION_HEADSET_PLUG); headSetUnPluggedintent.addFlags(Intent.FLAG_ RECEIVER_REGISTERED_ONLY); headSetUnPluggedintent.putExtra("state", 0); headSetUnPluggedintent.putExtra("name", "Headset"); // TODO: Should we require a permission? sendOrderedBroadcast(headSetUnPluggedinten t, null);
http://androidbridge.blogspot.com/2011/05/how-to-answer-incoming-call-in-android.html?m=1
I'm not a developer so how would you insert this fix
Bottomline can someone please take a crack at helping this guy out
Sent from my ADR6400L using xda premium

Gear To Device Communication

Hi All,
I'm very new to app development. I have created an app on my Note3 and a client on the Gear but im not sure how to get them talking. Does any one know if there is a Samsung api for doing this or can I just use BLE. Also does any one have a good BLE tutorial?
Thanks in advance.

taylordw said:
Hi All,
I'm very new to app development. I have created an app on my Note3 and a client on the Gear but im not sure how to get them talking. Does any one know if there is a Samsung api for doing this or can I just use BLE. Also does any one have a good BLE tutorial?
Thanks in advance.
Click to expand...
Click to collapse
We are still waiting for sdk to be released

taylordw said:
Hi All,
I'm very new to app development. I have created an app on my Note3 and a client on the Gear but im not sure how to get them talking. Does any one know if there is a Samsung api for doing this or can I just use BLE. Also does any one have a good BLE tutorial?
Thanks in advance.
Click to expand...
Click to collapse
I don't see how you could use Bluetooth protocols for this kind of architecture. You can try to open a Bluetoothsocket and use your own script language to do the talking. http://developer.android.com/reference/android/bluetooth/BluetoothSocket.html
But I would wait for a SDK. Sony also has a SDK for their watches. It makes developing a lot easier with intent-based APIs

BluetoothSocket
appelflap said:
I don't see how you could use Bluetooth protocols for this kind of architecture. You can try to open a Bluetoothsocket and use your own script language to do the talking.
But I would wait for a SDK. Sony also has a SDK for their watches. It makes developing a lot easier with intent-based APIs
Click to expand...
Click to collapse
Thanks for the pointer, that works! :good:
On the watch:
Code:
BluetoothAdapter btAdapter = BluetoothAdapter.getDefaultAdapter();
BluetoothServerSocket bss = btAdapter.listenUsingRfcommWithServiceRecord("Test", UUID.fromString("c3f10dc0-677b-11e3-949a-0800200c9a66"));
BluetoothSocket bs = bss.accept();
byte[] buf = new byte[1024];
InputStream is = bs.getInputStream();
int read = is.read(buf);
is.close();
bs.close();
On the phone:
Code:
BluetoothAdapter btAdapter = BluetoothAdapter.getDefaultAdapter();
Set<BluetoothDevice> devices = btAdapter.getBondedDevices();
BluetoothDevice device = devices.iterator().next();
BluetoothSocket bs = device.createRfcommSocketToServiceRecord(UUID.fromString("c3f10dc0-677b-11e3-949a-0800200c9a66"));
bs.connect();
bs.getOutputStream().write("Hello!".getBytes("UTF-8"));
bs.getOutputStream().flush();
bs.getOutputStream().close();
bs.close();
This is just an example, but it works. Does anyone know if the the Bluetooth GATT APIs might be a better fit, and whether they might be able to control the lifecycle of the app on the watch?

Data Transfer between Samsung Galaxy Note 3 and Samsung Galaxy Gear?
surlydre said:
Thanks for the pointer, that works! :good:
On the watch:
Code:
BluetoothAdapter btAdapter = BluetoothAdapter.getDefaultAdapter();
BluetoothServerSocket bss = btAdapter.listenUsingRfcommWithServiceRecord("Test", UUID.fromString("c3f10dc0-677b-11e3-949a-0800200c9a66"));
BluetoothSocket bs = bss.accept();
byte[] buf = new byte[1024];
InputStream is = bs.getInputStream();
int read = is.read(buf);
is.close();
bs.close();
On the phone:
Code:
BluetoothAdapter btAdapter = BluetoothAdapter.getDefaultAdapter();
Set<BluetoothDevice> devices = btAdapter.getBondedDevices();
BluetoothDevice device = devices.iterator().next();
BluetoothSocket bs = device.createRfcommSocketToServiceRecord(UUID.fromString("c3f10dc0-677b-11e3-949a-0800200c9a66"));
bs.connect();
bs.getOutputStream().write("Hello!".getBytes("UTF-8"));
bs.getOutputStream().flush();
bs.getOutputStream().close();
bs.close();
This is just an example, but it works. Does anyone know if the the Bluetooth GATT APIs might be a better fit, and whether they might be able to control the lifecycle of the app on the watch?
Click to expand...
Click to collapse
Did you succeed in getting the Note 3 and Gear talking with this code, Is data transfer also possible? When I tried deploying such a client application on the watch it immediately crashed and so I thought it could be that the Bluetooth session cannot be started because of an existing Bluetooth connection via the Gear Manager.
After reading some content on different sites regarding this(I could not post those links as I got an error while posting), I thought real time data transfer via Bluetooth will not be possible but if you say it works then may be I should check my code, But is there any other way to transfer data by using the existing Bluetooth pairing via the Gear Manager App?

[Q] Good for Enterprise crashes when Xposed is enabled

Hi folks...
I am using a T-Mo Galaxy Note 3 with 4.3 (jellybean) and the latest Xposed Framework 2.7.1 (for reference, I did also try 2.4 through 2.5.1, with the same results).
I have installed the "Good for Enterprise" application to access my organization's email system. Our policy does NOT restrict use of root, so my issue is NOT with the fact that I am rooted.
However, whenever I enable the framework, even with NO modules enabled, launching Good crashes the app right after I enter my password into it. This is 100% repeatable. If I disable Xposed and reboot, Good works perfectly. This is also 100% repeatable.
I have looked through the logcat output and don't know what to look for, as I see a good amount of recurring debug messages. Any suggestions for how to proceed? Also, is it possible to blacklist an application so Xposed does not try to hook only that app?
Any suggestions are appreciated, and please remember that my organization does NOT restrict root via Good policy, so I don't have to worry about RootCloak, etc.
Thanks folks!
- SG

Xposed Framework Causes Good Mobile Messaging to not function
Hey there, not sure if there is anything that you can do about this but I wanted your input:
For some reason when I activate the xposed installer framework (my Verizon HTC One Max is running the most recent version of the NuSenseSix rom), it causes an app I have installed called "Good for Enterprise" to stop functioning. (Good for Enterprise is used for corporate email). if I disable the framework, then the app functions normally. Is there any way you can give me some advice or a resolution regarding this? the framework version I am running is 2.6.1
Thanks,

Slappy_G said:
Hi folks...
I am using a T-Mo Galaxy Note 3 with 4.3 (jellybean) and the latest Xposed Framework 2.7.1 (for reference, I did also try 2.4 through 2.5.1, with the same results).
I have installed the "Good for Enterprise" application to access my organization's email system. Our policy does NOT restrict use of root, so my issue is NOT with the fact that I am rooted.
However, whenever I enable the framework, even with NO modules enabled, launching Good crashes the app right after I enter my password into it. This is 100% repeatable. If I disable Xposed and reboot, Good works perfectly. This is also 100% repeatable.
I have looked through the logcat output and don't know what to look for, as I see a good amount of recurring debug messages. Any suggestions for how to proceed? Also, is it possible to blacklist an application so Xposed does not try to hook only that app?
Any suggestions are appreciated, and please remember that my organization does NOT restrict root via Good policy, so I don't have to worry about RootCloak, etc.
Thanks folks!
- SG
Click to expand...
Click to collapse
I am experiencing the exact same issue with good and my device. If I keep the framework disabled, good for enterprise works perfectly. As soon as I enable the framework and reboot, good hangs every time when attempting to connect after putting in my password and then just force quits back to the home screen.
I opened a seperate thread regarding the issue not seeing this thread until after I had already posted. I am hopeful that a resolution can be found. I have a Verizon HTC One Max, rooted with NuSenseSix Rom. I have also verified that they do not block access to good when it detects a rooted device. And as stated before, it functions normally on my rooted device as long as I keep the framework disabled.

Please describe in detail what you mean with "stop functioning". Does it crash? Please provide a logcat of the error.

I have merged these two threads. As mentioned, please post a logcat. A blacklist to avoid "loading" Xposed is not possible, because Xposed is initialized at system start and "inherited" by all apps.

rovo89 said:
I have merged these two threads. As mentioned, please post a logcat. A blacklist to avoid "loading" Xposed is not possible, because Xposed is initialized at system start and "inherited" by all apps.
Click to expand...
Click to collapse
Understood. I'll post a logcat this evening of both a positive and a negative case.

I am experiencing the excact same behaviour as stated in the OP, and are working under the same conditions (rooted rom with latest xposed and NO anti-root policy). I would LOVE to help providing logcats, and i happen to be part of the IT department enforcing Good, so i can really test this (they wont blacklist me).
I will produce som logcat for you, any advice on how to best do this? Otherwise i will just throw something at best effort :good: :laugh:
Update: Back with a log, see attatched.
I started Catlog (app), pressed home and launched GFE. I then entered my password, and the app crashed. After this i clicked the shortcut on my launcher to start (resume) catlog, and paused the logging. I then exported the whole thing to the attatched textfile. The loglevel is Verbose.
If any system information is needed, other than those in the log file, please ask.
Kind Regards
TwinAdk

Thanks. I don't see any crash/exception of the application there. Is it a normal crash ("<app> has stopped working" or whatever that message says)? If so, can you get the stack trace from it?
But what I noticed is that you have at least one module with quite verbose output (all those lines with "Xposed" tag, they don't come from the framework). Could you please make sure that it crashes even without any active modules?

rovo89 said:
Thanks. I don't see any crash/exception of the application there. Is it a normal crash ("<app> has stopped working" or whatever that message says)? If so, can you get the stack trace from it?
But what I noticed is that you have at least one module with quite verbose output (all those lines with "Xposed" tag, they don't come from the framework). Could you please make sure that it crashes even without any active modules?
Click to expand...
Click to collapse
I will deactivate all modules and re-take the log. It still crashes, that's for sure. When i will screen record the crash, it's not a stopped working crash, the app just closes with it's 'switch to launcher animation'. Once reopened it loads from scratch.
---------- Post added at 11:23 PM ---------- Previous post was at 10:32 PM ----------
Back with log of crash two times in a row, and screen record of working and failing good app. Notice that good cannot he screen recorded, hence the black screen when I'm inside the app. After the working recording I enabled xposed framework and rebooted.
Video and log here:
https://www.dropbox.com/sh/zrkivu9u0k4u2od/AAA5io6UfphGumblJCduRp8da
When you got the files, tell me, I'll remove them from dropbox then.
Kind Regards
TwinAdk

Twin, thanks for uploading the log files and the sharing the videos. i've been super busy and haven't had a chance to do this. what you are showing in your videos is exactly what is happening on my device when the framework is enabled (with no modules enabled/loaded). good prompts for my password and then force quits back to the home screen. it does this over and over again until I disable the framework and restart my device. then good functions normally.
Rovo, let me know if you need me to also supply logs from my device, or if what twin provided is enough to troubleshoot this.
thanks,

No problem, i know that far too well The phone having the problem is a HTC One, m7_ul, running the AICP project rom from here: http://forum.xda-developers.com/showthread.php?t=2632667
I also have an Samsung xCover 2 i can test it on (the wifes) and the former phone, the HTC One X, running a similair AICP rom, in a slightly older version. If this has any intereset, let me know. It would
Also, it occured to me, the Good app also hangs during the initial setup of Good (you have to pair the Good app with your company, by entereing your email address and a one-time key. This is done upon starting the app for the first time).. It has a process where it, after the email and onetime key is submitted, will "log in" - "check stuff" [NOT root policies etc i believe] - "preforms the secure connection" [between phone and company] - "fetches corporate settings" (this is the step where it freezes with XPosed enabled, hence never allowing the initial setup to complete) - "saving settings" [initial setup done, the app loads, if no xposed is present].
Are you interested in a logcat of that process aswell? I am quite sure its the same thing stopping the app from working.
Kind Regards
TwinAdk
EDIT: I just realised the video of the Good app working, was unable to play anywhere else than on my phone, so i screenrecorded it playing on my phone, and posted the screenrecord of a screenrecord to dropbox

you are correct, if i uninstall good and attempt to reinstall while the framework is enabled, it hangs on "retrieving corporate settings". If i disable the framework and reinstall, installation completes with no issues and functions normally. Again this is just enabling the framework on my device, not loading or enabling any modules. I am using a verizon htc one max running rooted nusensesix rom

TwinAdk said:
Video and log here:
https://www.dropbox.com/sh/zrkivu9u0k4u2od/AAA5io6UfphGumblJCduRp8da
When you got the files, tell me, I'll remove them from dropbox then.
Click to expand...
Click to collapse
Thanks, you can remove them.
This isn't a crash - the app deliberatly goes back to the launcher:
Code:
07-16 22:53:08.172 I/ActivityManager(585): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.good.android.gfe/com.good.android.ui.LaunchHomeActivity bnds=[540,960][540,960]} from pid 1068
07-16 22:53:08.312 I/ActivityManager(585): Start proc com.good.android.gfe for activity com.good.android.gfe/com.good.android.ui.LaunchHomeActivity: pid=4604 uid=10161 gids={50161, 3003, 1028, 1015, 1023, 1006}
07-16 22:53:08.943 W/ActivityManager(585): Unable to start service Intent { cmp=com.dell.enterpriseservices/.EnterpriseService } U=0: not found
07-16 22:53:09.633 I/WindowManager(585): Screenshot max retries 4 of Token{41ca04d8 ActivityRecord{41ab9a78 u0 com.good.android.gfe/com.good.android.ui.LaunchHomeActivity t5 f}} appWin=Window{41d18a68 u0 Starting com.good.android.gfe} drawState=4
07-16 22:53:09.643 W/WindowManager(585): Screenshot failure taking screenshot for (1080x1920) to layer 21015
07-16 22:53:09.653 I/ActivityManager(585): START u0 {cmp=com.good.android.gfe/com.good.android.ui.activities.AppLockActivity (has extras)} from pid 4604
07-16 22:53:09.663 W/ActivityManager(585): startActivity called from finishing ActivityRecord{41ab9a78 u0 com.good.android.gfe/com.good.android.ui.LaunchHomeActivity t5 f}; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=com.good.android.gfe/com.good.android.ui.activities.AppLockActivity (has extras) }
...
[B][COLOR="Red"]07-16 22:53:22.687 I/ActivityManager(585): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.teslacoilsw.launcher/com.android.launcher2.Launcher} from pid 4604[/COLOR][/B]
...
07-16 22:53:23.208 I/ActivityManager(585): Process com.good.android.gfe (pid 4604) has died.
07-16 22:53:23.208 I/WindowState(585): WIN DEATH: Window{41f2c360 u0 com.good.android.gfe/com.good.android.ui.activities.AppLockActivity}
I have decompiled the app and it indeed has code for that. Unfortunately, they have used Proguard to obfuscate the code, so it's very hard to understand why exactly they show the launcher. Maybe they have detected Xposed or something done by it, or it caused an unexpected situation.
You could try one more thing - disable the Xposed resources APIs in the installer settings and reboot. That disables a good part of Xposed. If that doesn't help, someone would need to analyse the app in detail. I'm saying "someone" because I don't have enough free time for that.

rovo89 said:
Thanks, you can remove them.
This isn't a crash - the app deliberatly goes back to the launcher:
Code:
07-16 22:53:08.172 I/ActivityManager(585): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.good.android.gfe/com.good.android.ui.LaunchHomeActivity bnds=[540,960][540,960]} from pid 1068
07-16 22:53:08.312 I/ActivityManager(585): Start proc com.good.android.gfe for activity com.good.android.gfe/com.good.android.ui.LaunchHomeActivity: pid=4604 uid=10161 gids={50161, 3003, 1028, 1015, 1023, 1006}
07-16 22:53:08.943 W/ActivityManager(585): Unable to start service Intent { cmp=com.dell.enterpriseservices/.EnterpriseService } U=0: not found
07-16 22:53:09.633 I/WindowManager(585): Screenshot max retries 4 of Token{41ca04d8 ActivityRecord{41ab9a78 u0 com.good.android.gfe/com.good.android.ui.LaunchHomeActivity t5 f}} appWin=Window{41d18a68 u0 Starting com.good.android.gfe} drawState=4
07-16 22:53:09.643 W/WindowManager(585): Screenshot failure taking screenshot for (1080x1920) to layer 21015
07-16 22:53:09.653 I/ActivityManager(585): START u0 {cmp=com.good.android.gfe/com.good.android.ui.activities.AppLockActivity (has extras)} from pid 4604
07-16 22:53:09.663 W/ActivityManager(585): startActivity called from finishing ActivityRecord{41ab9a78 u0 com.good.android.gfe/com.good.android.ui.LaunchHomeActivity t5 f}; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=com.good.android.gfe/com.good.android.ui.activities.AppLockActivity (has extras) }
...
[B][COLOR="Red"]07-16 22:53:22.687 I/ActivityManager(585): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.teslacoilsw.launcher/com.android.launcher2.Launcher} from pid 4604[/COLOR][/B]
...
07-16 22:53:23.208 I/ActivityManager(585): Process com.good.android.gfe (pid 4604) has died.
07-16 22:53:23.208 I/WindowState(585): WIN DEATH: Window{41f2c360 u0 com.good.android.gfe/com.good.android.ui.activities.AppLockActivity}
I have decompiled the app and it indeed has code for that. Unfortunately, they have used Proguard to obfuscate the code, so it's very hard to understand why exactly they show the launcher. Maybe they have detected Xposed or something done by it, or it caused an unexpected situation.
You could try one more thing - disable the Xposed resources APIs in the installer settings and reboot. That disables a good part of Xposed. If that doesn't help, someone would need to analyse the app in detail. I'm saying "someone" because I don't have enough free time for that.
Click to expand...
Click to collapse
See the dropbox folder. I ticked the option and rebooted, then I had same experience and found the shown in the logcat....

Mornig,
I just noticed that i get a notification from Good, saying that "GFE does not have connection [to the corporate network]. Unlock GFE to initiate the connection". See the screenshot (_20140718_072316.JPG) posted in the dropbox folder. I received this while GFE was unable to open, and it confirms that GFE is indeed running in the background..
I tried to rename the Xposed app in the phone, to test, using xSuite (weak attempt, but you never know). Also, i stripped GFE of some permissions using the App Settings module:
- Read External storage
- Read Logs
- com.dell.enterpriseservices.SET_PROPERTY_THIRDPARTY_APPINSTALL (custom GFE permission added to the manifest i belive). Possibly a permission used for corporate inforced rules (that do not apply here yet, but i still nuked it)
I will try stripping permissions to see where it gets me.
Also, there is this module, - http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher - but it does not work for me at least.
Then there is this thread - http://forum.xda-developers.com/showthread.php?t=2040163 - but the "4.3+ xposed way" mentioned in the very first post, is also no good...
I also tested the rootcloak app, where the developer says it may work with GFE, but he needs more testing. It does not.
I fear however, that all these past efforts have been nullified by some recent GFE update, because the case here is that we dont even get to start the program.
Kind Regards
TwinAdk
EDIT: Okay, that was quick.. I stripped GFE of EVERY SINGLE permission. This caused it to FC on me the first time. The dump report revealed it needed the WAKE_LOCK permission, so i granted it that and retried.. On the second launch, it returned to my launcher as we have seen before...
In fact, i find this behaviour unacceptable, as my company has NOT decided against Xposed, rooting, etc, and a company could for all we know depend on both GFE and Xposed (unlikely, yes, impossible, no). But GFE seems to be dead set against opening up when Xposed is active.
Would it be possible to intercept and block the return to launcher call to android? Just to see where it gets us? This would require a module, i know.
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Okay, i read up on another thread, and found this post here: http://forum.xda-developers.com/showpost.php?p=53198439&postcount=833
It states the following:
Information Notification: Good for Enterprise (GFE) Good Mobile Messaging Client (GMMC) for Android v2.5 running Android OS v4.4.2 May Encounter Application Restarts After Entering the Password on the Nexus 4 and Nexus 5 Device
Date: June 3, 2014
Problem:
Good for Enterprise (GFE) Good Mobile Messaging Client (GMMC) for Android version 2.5 running Android OS 4.4.2 may encounter application restarts after entering the password on the Nexus 4 and Nexus 5 Device. This problem has occurred after upgrading from GMMC for Android version 2.4 to GMMC for Android version 2.5 and with doing a fresh installation of GMMC for Android version 2.5.
Environment:
· Good for Enterprise (GFE) Good Mobile Messaging Client (GMMC) for Android version 2.5
· Nexus 4 and Nexus 5 devices with Android OS 4.4.2
Please Note:
A re-install of the GFE GMMC Android version 2.5 will not resolve the problem.
Workaround:
Please install the older version of Good for Enterprise (GFE) Good Mobile Messaging Client (GMMC) for Android version 2.4 on your device and disable the auto update setting for this application.
· Here is the link to get the GFE for Android 2.4 release - https://get.good.com/ea/android/
· It's very important to disable the auto update for the application, so it does not auto update to GFE version 2.5.
o Open the Google Play Store
o Hit Menu (3 dots in the upper right)
o Select Settings
o Uncheck 'Auto-update' apps
FIX:
Good Engineering is currently working on a permanent fix for this issue. We will keep you updated on the availability of the new software version.
If you have questions, please contact our technical support team at 1-408-352-7100, 1-866-448-8458 or submit an online support ticket at www.good.com/gmp.
Thank you,
Click to expand...
Click to collapse
Provided this information, i downloaded the 2.4 release of GFE, instead of the 2.5 from Google Play Store - and it just works.
After uninstalling 2.5, rebooting and installing 2.4, i can open up GFE with Xposed fully enabled. I also have the GFE Patcher module (http://repo.xposed.info/module/com.phantasm.xposed.gfesecuritypatcher) installed, just in case.. even though my company does not block root.
Summa summarum - It seems we can call off the witch hunt, and conclude that its a bug in 2.5 of GFE causing the issues.
Also, the GFE Patch module seems to work for people with root, and in the thread where i found the bug-info, people are reporting that 2.5 of GFE works, when installed on top of 2.4, via playstore. This is however not the case for me, 2.5 still returns to launcher.
@revo89, thank you for all your time and effort in this matter, and once again, thank you for the xposed framework as a whole, its is a truly amazing piece of art, and my phone is not my phone without it! :good::good:

@twin
You are absolutely correct buddy. After reading your recent update to this thread, I removed and reinstalled w/ GFE 2.4 via the link you provided. that took care of my issue. I can use GFE 2.4 with the framework & modules enabled with no issues. as soon as I upgrade again to 2.5, I start experiencing the same issue as before where it force quits back to the home screen. for now I will use 2.4 until a newer version of GFE is released and will test again with that version. but at least now I have a working solution to the issue.
thanks again for all your time and assistance in troubleshooting this problem.

Thanks so much everyone for working on this thread. I run xposed on a Verizon note2 and I have been having this same issue described here. Its been driving me crazy and I've had to live without xposed since this 'bug' arrived. I'll try 2.4 as well and then wait for GFE to fix the newer versions. Thanks again.

I had this issue.. It's rom dependant.
I had one rom on my Note2 that had this issue. But a rooted stock rom does not have this issue.
I'm running a HTC One M8 as of today. It's got rooted stock, it also does not have this issue.
Hope that helps (but yeah 2.4 works, I kept a backup in titanium)

Indeed, it seems that the rom makes a difference, because some people say it works (2.5), and some doesnt.. Must be parts of the rom that is the issue, and that part is used only in some roms
Kind Regards
TwinAdk

Awesome, this thread was a lifesaver! I couldn't figure out why and kept reinstalling and on the phone with tech support at my company who basically told me to do a hard reset (right....). The older version 2.4 works fine. Thanks TwinAdk!

[Q] How to change carrier text on demand

Hello,
I'm trying to develop an Xposed module that will allow me to change the carrier text of the device on demand (in reality, this will happen when the music track is changed).
I'm already using a BroadcastReceiver to listen to track-changed events from various media players, but I want to change the carrier text of the device when I receive such an intent.
However, I wasn't able to find how to do it using Xposed, as it only allows me to hook methods before/after they execute (feel free to correct me if I'm wrong of course), which isn't exactly what I need.
I went through the source code of XBlastTools for changing the carrier text, but wasn't able to conclude much for my needs.
Please advise in setting up a method that will basically get a String and replace the carrier text with that given String (at any given time). Something like this:
Code:
public void setName(String name) {
// TODO implement
}

Normally, you'd put your BroadcastReceiver somewhere you can access the carrier TextView from. You'd then be able to edit it when you want normally. In this case it looks like there's an easier way, though.
Here's how I'd do it: register a BroadcastReceiver in CarrierText's constructor. In that receiver, get and save the text you want as a class variable. Then hook getCarrierTextForSimState and make it return that variable.
http://grepcode.com/file_/repositor...licy/impl/keyguard/CarrierText.java/?v=source

GermainZ said:
Normally, you'd put your BroadcastReceiver somewhere you can access the carrier TextView from. You'd then be able to edit it when you want normally. In this case it looks like there's an easier way, though.
Here's how I'd do it: register a BroadcastReceiver in CarrierText's constructor. In that receiver, get and save the text you want as a class variable. Then hook getCarrierTextForSimState and make it return that variable.
http://grepcode.com/file_/repositor...licy/impl/keyguard/CarrierText.java/?v=source
Click to expand...
Click to collapse
That's a good way of doing things if it weren't for the "on demand" requirement.
Basically, what I want to do is set the carrier text to a different one whenever the onReceive() of the BroadcastReceiver is called, so I can't just hook into getCarrierTextForSimState() and change that, because it probably won't be called whenever I need.

benthe said:
That's a good way of doing things if it weren't for the "on demand" requirement.
Basically, what I want to do is set the carrier text to a different one whenever the onReceive() of the BroadcastReceiver is called, so I can't just hook into getCarrierTextForSimState() and change that, because it probably won't be called whenever I need.
Click to expand...
Click to collapse
Then call the setText method from your receiver as well.

GermainZ said:
Then call the setText method from your receiver as well.
Click to expand...
Click to collapse
By the way, I think the class you linked to only affects the carrier name that appears on the lockscreen.
I'm not that interested in this carrier text to be honest, and basically want to set the carrier text whereever it may be the class you linked to is pulling it from.
The main idea behind my module is that I have a BT headset in my car that can only display the carrier name & bluetooth name of my phone, but I want it to display the currently playing track. So I want to change the bluetooth name of the phone to the artist of the currently playing song (almost works at this point, just have some crashes I need to deal with), and set the carrier name to the name of the song that's currently playing.
However, I didn't manage to do that later. I tried various methods, but no luck so far.
EDIT: I managed to get everything working for the most part (I didn't test it with the actual BT headset, but both the BT and carrier names change when changing tracks).
However, I'm getting 2 error messages constantly as soon as I start playback:
1. Unfortunately, the process android.process.acore has stopped.
2. Unfortunately, the process android.process.media has stopped.
Any ideas on how to fix those two? What's causing them seems to be the changing of the bluetooth name (although it does work, just shows me those two crash errors time after time). Here's the code for my bluetooth manager.
Disabling the "setName" call of the BluetoothAdapter fixes the crashes (but obviously doesn't change the BT name of the device, which defeats the purpose).
Also, replacing the said call with:
Code:
XposedHelpers.callMethod(mLocalAdapter, "setName", name);
fixes this, but I prefer to do things without using reflection and hooking if I can (which is possible in this case), so it seems like it's just a permission issue.
It might be because of a permission problem:
I put together a quick Android app to simulate changing the BT name in the same way, and it crashed without adding:
Code:
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
to the manifest file.
However, if I recall correctly, Xposed modules run in root mode, so they shouldn't need permissions to do whatever they please. Also, I tried adding the above permissions to my module, but it still crashes.
Any help on the matter would be most appreciated.

I just checked which class XBlastTools hooked and assumed that's it. If not, look for the right one or see the first part of post #2.
About the crashes: check your logcat.
Xposed modules do not run as root, they'll have the same permissions as the process they're in (the app you're hooking). You can hook anything, though (including Android system methods).

GermainZ said:
I just checked which class XBlastTools hooked and assumed that's it. If not, look for the right one or see the first part of post #2.
About the crashes: check your logcat.
Xposed modules do not run as root, they'll have the same permissions as the process they're in (the app you're hooking). You can hook anything, though (including Android system methods).
Click to expand...
Click to collapse
Thanks for the help.
I got the carrier name part working perfectly now (or so it seems at least, I'll have to check later in the actual car BT headset).
The only part that remains to make the module fully functional is the Bluetooth one. I checked my logcat, and like I said in my previous post - I think it's a permission issue, which is rather weird - as I set both permissions needed for Bluetooth for the module. Keep in mind that the part that's running the bluetooth code in the app isn't hooking anything, it runs on the module itself as far as I can tell. I'm calling it on the onReceive callback from the BroadcastReceiver (I don't think the app that send the broadcast has bluetooth permissions, but that shouldn't matter, should it?).

benthe said:
Thanks for the help.
I got the carrier name part working perfectly now (or so it seems at least, I'll have to check later in the actual car BT headset).
The only part that remains to make the module fully functional is the Bluetooth one. I checked my logcat, and like I said in my previous post - I think it's a permission issue, which is rather weird - as I set both permissions needed for Bluetooth for the module. Keep in mind that the part that's running the bluetooth code in the app isn't hooking anything, it runs on the module itself as far as I can tell. I'm calling it on the onReceive callback from the BroadcastReceiver (I don't think the app that send the broadcast has bluetooth permissions, but that shouldn't matter, should it?).
Click to expand...
Click to collapse
Remember that all hooked code does *not* run as your app so your app's permissions don't matter here. Hooked code runs as if it was in the hooked process.
Can't say much else without the actual error.

GermainZ said:
Remember that all hooked code does *not* run as your app so your app's permissions don't matter here. Hooked code runs as if it was in the hooked process.
Can't say much else without the actual error.
Click to expand...
Click to collapse
But this code does run on the module.
In my main class (that implements IXposedHookLoadPackage), I'm initializing a class (that derives from Object, and doesn't implement any interfaces), in which I register the BroadcastReceiver (on the context of the application, via AndroidAppHelper.currentApplication().getApplicationContext()), when the onReceive() method is called in the BroadcastReceiver I call the setName() method of the BluetoothAdapter.
If it doesn't run on the module application, on what application does it run on?
And here's the error:
E/AndroidRuntime( 5063): FATAL EXCEPTION: main
E/AndroidRuntime( 5063): Process: com.maxmpz.audioplayer, PID: 5063
E/AndroidRuntime( 5063): java.lang.RuntimeException: Error receiving broadcast Intent { act=com.maxmpz.audioplayer.TRACK_CHANGED flg=0x10 (has extras) } in com.bengr.MusicMetadataForLegacyDevices.Musi
[email protected]
E/AndroidRuntime( 5063): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:785)
E/AndroidRuntime( 5063): at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 5063): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 5063): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 5063): at android.app.ActivityThread.main(ActivityThread.java:5144)
E/AndroidRuntime( 5063): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 5063): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 5063): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/AndroidRuntime( 5063): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/AndroidRuntime( 5063): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/AndroidRuntime( 5063): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 5063): Caused by: java.lang.SecurityException: Need BLUETOOTH ADMIN permission: Neither user 10128 nor current process has android.permission.BLUETOOTH_ADMIN.
E/AndroidRuntime( 5063): at android.os.Parcel.readException(Parcel.java:1465)
E/AndroidRuntime( 5063): at android.os.Parcel.readException(Parcel.java:1419)
E/AndroidRuntime( 5063): at android.bluetooth.IBluetooth$Stub$Proxy.setName(IBluetooth.java:783)
E/AndroidRuntime( 5063): at android.bluetooth.BluetoothAdapter.setName(BluetoothAdapter.java:660)
E/AndroidRuntime( 5063): at com.bengr.MusicMetadataForLegacyDevices.BluetoothManager.setName(BluetoothManager.java:50)
E/AndroidRuntime( 5063): at com.bengr.MusicMetadataForLegacyDevices.MusicListener.updateRemoteFieldsFromLocalFields(MusicListener.java:150)
E/AndroidRuntime( 5063): at com.bengr.MusicMetadataForLegacyDevices.MusicListener.setTrackMetadata(MusicListener.java:144)
E/AndroidRuntime( 5063): at com.bengr.MusicMetadataForLegacyDevices.MusicListener.access$4(MusicListener.java:138)
E/AndroidRuntime( 5063): at com.bengr.MusicMetadataForLegacyDevices.MusicListener$1.onReceive(MusicListener.java:105)
E/AndroidRuntime( 5063): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:775)
E/AndroidRuntime( 5063): ... 10 more
W/ActivityManager( 935): Force finishing activity com.maxmpz.audioplayer/.PlayerUIActivity
W/ActivityManager( 935): Force finishing activity com.maxmpz.audioplayer/.PlayListActivity
D/LogFetchServiceManager( 6618): Received entry added
W/ActivityManager( 935): Activity pause timeout for ActivityRecord{42d72640 u0 com.maxmpz.audioplayer/.PlayerUIActivity t4 f}
I/Timeline( 1490): Timeline: Activity_idle id: [email protected] time:183794
I/Timeline( 935): Timeline: Activity_windows_visible id: ActivityRecord{42ca81c8 u0 com.teslacoilsw.launcher/com.android.launcher2.Launcher t1} time:184001
W/System.err( 5009): LOG: Warning Unknown dock level ignored.
Click to expand...
Click to collapse
Also, here's the project (together with the PowerAMP API project, as it depends on it, and the Android tester application I made to simulate changing the bluetooth name on a "regular" project): link, if that's of any help.

I can't check the project right now, but just to make sure I understand correctly, you're doing something like this:
1- You're hooking the class in which the carrier text is set and registering a BroadcastReceiver there.
2- From your app, you're sending a broadcast whenever you want (possibly with the text you want in the extras).
3- In the BroadcastReceiver's onReceive method, you're setting the carrier text to the value you just received.
If that's what you're doing, it seems fine to me. For the permissions issue, I suppose adding the required permission to your manifest will fix that.

GermainZ said:
I can't check the project right now, but just to make sure I understand correctly, you're doing something like this:
1- You're hooking the class in which the carrier text is set and registering a BroadcastReceiver there.
2- From your app, you're sending a broadcast whenever you want (possibly with the text you want in the extras).
3- In the BroadcastReceiver's onReceive method, you're setting the carrier text to the value you just received.
If that's what you're doing, it seems fine to me. For the permissions issue, I suppose adding the required permission to your manifest will fix that.
Click to expand...
Click to collapse
Not really. The carrier text has nothing to do with the issue anymore. Even if I removed all the code that has to do with the carrier text, and left the bluetooth part alone - the issue would persist.
What I'm doing is this:
1- Have a regular class (meaning it derives from Object directly, and doesn't implement any interfaces).
2- In the said class I set up a BroadcastReceiver (using the application context, which I got via AndroidAppHelper.currentApplication().getApplicationContext(), which is static and can be called from anywhere).
3- When the BroadcastReceiver's onReceive() is called (again, in the previously mentioned class), I call BluetoothAdapter.getDefaultAdapter().setText with the text I want to set as the phone's BT name.
4- Error messages pop-up, and the error I attached in my previous reply shows up on the logcat. (this step occurs when the onReceive is called, which calls the setText).
When I comment out the setText() call, no errors occur (but the BT name doesn't change, obviously).
It's important to note that I did add the needed permissions to my manifest:
AndroidManifest.xml:
Code:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.bengr.musicmetadateforlegacydevices"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="19" />
<uses-permission android:name="android.permission.BLUETOOTH" />
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<meta-data android:name="xposedmodule" android:value="true"/>
<meta-data android:name="xposedminversion" android:value="50"/>
<meta-data android:name="xposeddescription" android:value="Changes the device's carrier and bluetooth names to display the currently playing track."/>
</application>
</manifest>

So you're not using Xposed for anything anymore? Sorry but I'm a bit confused now.

GermainZ said:
So you're not using Xposed for anything anymore? Sorry but I'm a bit confused now.
Click to expand...
Click to collapse
For what I'm doing right now? Not really.
My module is composed of two parts - one for changing the BT name (which doesn't require private calls, and can be done via Android's public API), and one for changing the carrier name (which does require Xposed, as I'm doing some private calls etc).
The carrier name part of the module works perfectly right now.
However, the Bluetooth one doesn't; and crashes as mentioned before, and throws a permission error. However, on a side-project that's just a regular Android app, that also changes the BT name this works (keep in mind that in both the side-project and the Xposed module project I added both Android bluetooth permissions).

Android Pay stopped working

Hi,
I've an S7 Edge (GM-935F) that I've flashed with LineageOS and rooted with Magisk (currently 15.3, waiting for 15.4 to go stable). Since late December I was able to use Android Pay despite Safety Net checks never passing from Magisk Manager. Two weeks ago this stopped and when trying to use Android Pay the phone reports "You are no longer able to use Android Pay on this device". I've updated LineageOS nightly builds (which come through weekly) and have only the Xposed module installed (and up-to-date) from the Magisk modules list (i.e. it too is systemless). The Play Store shows my device as "Uncertified" under Settings > Device certification. I'd read here that Xposed causes the checks Android Pay performs to fail, but Xposed was installed and active (I use Gravity Box) when Android Pay was working and I've not updated Xposed since then (its version 89.2 of SDK25).
Its strange as I can start the Android Pay app and see my cards (payment and store) that I've added, just can't make actual payments.
A couple of catlog outputs from having failed to pay (unfortunately I don't have a CatLog from when Android Pay was working to compare this to)...
Catlog device info
Code:
build.board: universal8890
build.bootloader: G935FXXS1DQHF
build.brand: samsung
build.cpu_abi: arm64-v8a
build.cpu_abi2:
build.device: hero2lte
build.display: lineage_hero2lte-userdebug 7.1.2 NJH47F eaf65f5fde
build.fingerprint: samsung/lineage_hero2lte/hero2lte:7.1.2/NJH47F/eaf65f5fde:userdebug/release-keys
build.hardware: samsungexynos8890
build.host: agrippa.acc.umu.se
build.id: NJH47F
build.manufacturer: samsung
build.model: SM-G935F
build.product: lineage_hero2lte
build.radio: G935FXXU1DQD7
build.serial: ad07160328408551ce
build.tags: release-keys
build.time: 1517395812000
build.type: userdebug
build.user: jenkins
version.codename: REL
version.incremental: eaf65f5fde
version.release: 7.1.2
version.sdk_int: 25
Catlog from a failure to pay last week (can't remember what I filtered on, possibly 'pay')
Code:
02-09 14:21:12.958 I/ActivityManager(4796): Start proc 9367:com.google.android.apps.walletnfcrel/u0a128 for service com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.clientconfig.sync.ClientConfigSyncService
02-09 15:37:04.335 I/ActivityManager(4796): Start proc 11094:com.google.android.apps.walletnfcrel/u0a128 for backup com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.sharedpreferences.backup.TapAndPayBackupAgent
02-09 15:58:43.464 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:43.512 I/ActivityManager(4796): Start proc 11707:com.google.android.gms.ui/u0a33 for activity com.google.android.gms/.tapandpay.tap.TapUiActivity
02-09 15:58:43.549 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:44.729 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:44.847 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:45.752 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:45.875 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:49.593 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:49.699 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:50.082 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:58:50.156 I/ActivityManager(4796): START u0 {act=com.google.android.gms.tapandpay.tap.TAP_EVENT cat=[targeted_intent_op_prefix:.tapandpay.tap.TapEventIntentOperation] flg=0x10040000 cmp=com.google.android.gms/.tapandpay.tap.TapUiActivity (has extras)} from uid 10033 on display 0
02-09 15:59:29.338 I/ActivityManager(4796): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.cardlist.CardListActivity bnds=[720,2054][981,2333] (has extras)} from uid 10027 on display 0
02-09 15:59:32.201 I/ActivityManager(4796): START u0 {cmp=com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.paymentcard.PaymentCardDetailsActivity (has extras)} from uid 10128 on display 0
02-09 16:04:01.184 I/ActivityManager(4796): START u0 {flg=0x10008000 cmp=com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.cardlist.CardListActivity (has extras)} from uid 10128 on display 0
02-09 16:04:08.506 I/ActivityManager(4796): START u0 {cmp=com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.cardlist.CardListActivity (has extras)} from uid 1000 on display 0
02-09 16:04:10.943 I/ActivityManager(4796): START u0 {cmp=com.google.android.apps.walletnfcrel/com.google.commerce.tapandpay.android.survey.SurveyActivity (has extras)} from uid 10128 on display 0
CatLog from failed payment this morning (filterd on "android.gms") with some activity from yesterday (was too long to include in a post here, hence pastebining it)
Its not vital that I get this working but I was starting to like the convenience of not having to take my wallet out. Any advice or suggestions would be very much appreciated.
Thanks in advance.

Not sure if relevant, but Santander app just updated and though hidden with Magisk Hide still detects root versions 15.3 and 5.6.
Edit: Cleared cache and data from banking app and works now

got same problem since yesterday. it worked perfectly with magisk root. any fix to this problem?

Hi,
Thanks for the input, I'm wary of clearing the cache for Android Pay as I'm unsure whether that is where card details are kept/stored, if so wiping may remove them. I can open the Android Pay app ok. My banking app (Nationwide) works fine, as does PayPal. Android Pay is by default hidden under Magisk Managers "Magisk Hide".
Reading through theres a thread which suggests using a dated module to use Universal SafetyNet Fix | Universal Hide but towards the end of the thread user Didgeridoohan recommends against it and suggests instead obtaining a valid fingerprint for the phone and using a boot script via resetprop method. They have a very useful page on using Magisk.
I think I'll give that a go, I've been meaning to give resetprop a whirl to get HDR working in the camera. Unsure where to find a valid fingerprint for this model of phone though, searching is almost useless as it returns matches on using the fingerprint scanner. Will have a trawl through the S7 Edge forum here though and see what i can find.
Updated this morning to the latest nightly build of LineageOS 14.1 and the device is still uncertified under Play Store > Settings > Device Certificate (I've an old backup from 2018-01-18 when the phone was working with Android Pay that I may give a whirl and see if it still allows payments, bit of a faff though). Also found a long thread on Android Pay on the Samsung GM-935F that I'll have a read through and another thread Has anyone got android pay working with root? where people have had success with root (including someone reporting success with Magisk).
Any other suggestions welcome.

+1
Same thing here. Samsung S7 Edge on Superman 2.7 rom.
Android pay stopped working a few days ago. I tried updating Magisk 15.3 / 5.6 (Android Pay is checked in Magisk Hide)
I'm able to open the app and see my cards. I deleted one of my credit card but unable to add it anymore. It always tells me "You are no longer able to use Android Pay on this device".
no luck...
any help would be appreciated.

Problem solved.
Install Safety net fix v2 beta 5. (check link below)
Download and flash with TWRP.
Reboot.
https://www.google.ca/amp/s/forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/amp/
Android Pay back to normal.
?

Slingky1178 said:
Problem solved.
Install Safety net fix v2 beta 5. (check link below)
Download and flash with TWRP.
Reboot.
https://www.google.ca/amp/s/forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/amp/
Android Pay back to normal.
[emoji6]
Click to expand...
Click to collapse
Thanks [emoji106]
通过我的 SM-G9500 上的 Tapatalk发言

Slingky1178 said:
Problem solved.
Install Safety net fix v2 beta 5. (check link below)
Download and flash with TWRP.
Reboot.
https://www.google.ca/amp/s/forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/amp/
Android Pay back to normal.
Click to expand...
Click to collapse
This didn't fix NFC issue though right? Just let you use the app properly again?

Slingky1178 said:
Problem solved.
Install Safety net fix v2 beta 5. (check link below)
Download and flash with TWRP.
Reboot.
https://www.google.ca/amp/s/forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/amp/
Android Pay back to normal.
Click to expand...
Click to collapse
didn't work for me (magisk v16)

Android pay stop working for me too. I was on magisk v. 15 and one day stop working. Every time when I try to pay payment get declined. Saftynet pass, but payment is declined every time when I want to use android pay. I cleared cache, data and still not working. I updated bo magisk v. 16 and still not working
---------- Post added at 08:51 AM ---------- Previous post was at 08:02 AM ----------
Android pay stop working for me too. I was on magisk v. 15 and one day stop working. Every time when I try to pay payment get declined. Saftynet pass, but payment is declined every time when I want to use android pay. I cleared cache, data and still not working. I updated bo magisk v. 16 and still not working

tambukey said:
This didn't fix NFC issue though right? Just let you use the app properly again?
Click to expand...
Click to collapse
For me, NFC is working cause I was able to pay at gas station and grocery store so it seems to be working again.
Most important, the following error message disappear ;
"You are no longer able to use Android Pay on this device".
I only installed Safety net fix v2 beta 5 via TWRP.
Then re-added my credit card and set it as default.
Presentely, Magisk v16, Magisk Manager 5.6.1
Android Pay is already disabled in Magisk Hide.
Sorry it didn't work for everyone.
I read that safety net fix changes build.prop and other things like that for better compatibility.
So it might be other Magisk modules...?
In my case, I only use Busybox for Android NDK 1.27.2m and Viper4AndroidFX 2.5.0.5.
Good luck guys.

Slingky1178 said:
For me, NFC is working cause I was able to pay at gas station and grocery store so it seems to be working again.
Most important, the following error message disappear ;
"You are no longer able to use Android Pay on this device".
I only installed Safety net fix v2 beta 5 via TWRP.
Then re-added my credit card and set it as default.
Presentely, Magisk v16, Magisk Manager 5.6.1
Android Pay is already disabled in Magisk Hide.
Sorry it didn't work for everyone.
I read that safety net fix changes build.prop and other things like that for better compatibility.
So it might be other Magisk modules...?
In my case, I only use Busybox for Android NDK 1.27.2m and Viper4AndroidFX 2.5.0.5.
Good luck guys.
Click to expand...
Click to collapse
I upgraded to the v2 beta 5 for safety fix, but haven't tested yet. Can I ask more about your device, trying to piece together why some people get it to work and other don't. What device, which rom, and I see you're on most recent Magisk. Have you tried it again since updating those? And also you 100% never got the NFC side to work before upgrading to Safety Net v2 beta 5?

tambukey said:
I upgraded to the v2 beta 5 for safety fix, but haven't tested yet. Can I ask more about your device, trying to piece together why some people get it to work and other don't. What device, which rom, and I see you're on most recent Magisk. Have you tried it again since updating those? And also you 100% never got the NFC side to work before upgrading to Safety Net v2 beta 5?
Click to expand...
Click to collapse
My device is Samsung S7 Edge on Superman rom 2.8
Carrier is Bell Canada.
Yes, I tried Google Pay this morning and still fonctionning.
It was working a few days ago like others (via NFC of course)
One day, it stopped working with the error message "You are no longer able to use Android Pay on this device".
I deleted my credit card from Android Pay app but was unable to readd it.
So I dig that forum and finally decided to install safety net fix and it's working now.

Slingky1178 said:
My device is Samsung S7 Edge on Superman rom 2.8
Carrier is Bell Canada.
Yes, I tried Google Pay this morning and still fonctionning.
It was working a few days ago like others (via NFC of course)
One day, it stopped working with the error message "You are no longer able to use Android Pay on this device".
I deleted my credit card from Android Pay app but was unable to readd it.
So I dig that forum and finally decided to install safety net fix and it's working now.
Click to expand...
Click to collapse
Awesome, thank you. I have not gotten that error before, but I don't think that would stop it from working. Hopefully I will figure out why it just never starts the NFC process. Granted, after visiting Canada twice now I truly feel like U.S. is super far behind on NFC payment at registers. We have the right tech, but they never enable them at any store. I can only find a couple in my area that show the symbols, and for all I know they don't actually have them on since basically no one in the states seems to use it.

tambukey said:
Awesome, thank you. I have not gotten that error before, but I don't think that would stop it from working. Hopefully I will figure out why it just never starts the NFC process. Granted, after visiting Canada twice now I truly feel like U.S. is super far behind on NFC payment at registers. We have the right tech, but they never enable them at any store. I can only find a couple in my area that show the symbols, and for all I know they don't actually have them on since basically no one in the states seems to use it.
Click to expand...
Click to collapse
From my personnal experience, Canada used to lag behind USA for tech deployment.
Major banks just activated NFC payments via smartphones like april last year.
(before it was working but a NFC sim card was required and it was just working for a very limited number of smartphones)
Now, I would think pretty much any smartphone with NFC is compatible.
The problem is that merchants also have to replace their terminals so maybe they don't want to pay for that...
Now, I'm able to pay at drugstore, grocery stores, gas stations and even restaurants.
The only drawback is the 100$ limit.

Slingky1178 said:
From my personnal experience, Canada used to lag behind USA for tech deployment.
Major banks just activated NFC payments via smartphones like april last year.
(before it was working but a NFC sim card was required and it was just working for a very limited number of smartphones)
Now, I would think pretty much any smartphone with NFC is compatible.
The problem is that merchants also have to replace their terminals so maybe they don't want to pay for that...
Now, I'm able to pay at drugstore, grocery stores, gas stations and even restaurants.
The only drawback is the 100$ limit.
Click to expand...
Click to collapse
There is a limit? Is that a bank set limit? I

I'm pretty sure it's configured by the merchant.
Only place I saw more was at "Maxi A Plein Gaz".
It's a gas station. Max is 150$.
And Google Pay on phone works even outside at the pump

Slingky1178 said:
I'm pretty sure it's configured by the merchant.
Only place I saw more was at "Maxi A Plein Gaz".
It's a gas station. Max is 150$.
And Google Pay on phone works even outside at the pump
Click to expand...
Click to collapse
Strange I have never seen limits, granted mine doesn't work , Regardless thanks for the info. I will be doing some testing soon, luckily I have a mall near me where every vending machine has one and there are about 5 different types available to test with.

tambukey said:
Awesome, thank you. I have not gotten that error before, but I don't think that would stop it from working. Hopefully I will figure out why it just never starts the NFC process. Granted, after visiting Canada twice now I truly feel like U.S. is super far behind on NFC payment at registers. We have the right tech, but they never enable them at any store. I can only find a couple in my area that show the symbols, and for all I know they don't actually have them on since basically no one in the states seems to use it.
Click to expand...
Click to collapse
I've got the same problem using the Universal SafetyNet module on my Xperia Z5. Everything in AndroidPay works, but when I go to pay it seems like NFC never gets activated. I know NFC works on my ROM because I can use Android Beam with no issues.
I'm wondering if it's an issue with the module spoofing the wrong phone or if others are able to use AndroidPay on a custom ROM with the Universal module.

Devo7v said:
I've got the same problem using the Universal SafetyNet module on my Xperia Z5. Everything in AndroidPay works, but when I go to pay it seems like NFC never gets activated. I know NFC works on my ROM because I can use Android Beam with no issues.
I'm wondering if it's an issue with the module spoofing the wrong phone or if others are able to use AndroidPay on a custom ROM with the Universal module.
Click to expand...
Click to collapse
So far I haven't figured out a correlation on who has it working and who doesn't. It's kinda hit or miss since there really don't seem to me a lot of people trying to get it to work. I don't think it has to do with the Universal Module. I looked at its script and don't see anything related specifically to NFC, maybe something to do with how it affects SEpolicy but I am not sure. I am still pretty new to most programming languages.
I am wondering if we can come up with a script to basically force the pay NFC to activate. Like a root accessed app that starts nfc, reads if any are nearby, verifies it is a pay service, then loads the saved card into active nfc? Again, I have no idea how to actually make that happen.