Related
Hey all, As I'm sure other people are I am trying to get my Samsung Gear 2 connected to my Galaxy S5 running the latest CM12 nightly. Unfortunately, Since Lollipop, as far as I'm aware nobody has been able to get the Gear Manager to function correctly on Non-Touchwiz roms.
I have tried just about every combination of installing, uninstalling and restoring from TW roms with Titanium backup that you could think of. Nothing will allow my device to function correctly. Upon pairing with the app, the most common crash is HostManager. The watch will pair but as soon as it does, You get repeated messages of 'Unfortunately, HostManager has stopped.' and the Gear manager app stays at 'Conneting to Gear'. The only way to stop the crash loop is to turn of Bluetooth or Freeze the HostManager app.
Surely there is some way to fix this? I haven't seen a lot of people looking in to it despite the fact that a number of people must want to run their Gear device with an AOSP-type rom?
Here is the logcat from the installation of the HostManager APK (I don't think this is useful, as it all installs correctly but added anyway just in case): pastebin<dot>com/eWp2AuHd
And here is the Logcat from the crash of HostManager: pastebin<dot>com/N0eWGZRL
Sorry about the links, The logcat is too long to fit in an XDA post and I'm below the post count required for posting links, and I don't want to meaninglessly post just in order to insert links.
As you can see I left a large buffer of the logcat around the crash in case there is any other important information about what is going on.
Any help here would be appreciated. If you can fix it and have a PayPal I'll buy you a beer or two
So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?
Albadros said:
So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?
Click to expand...
Click to collapse
Unfortunately I was unable to get it to work. I went and bought a Gear Live insead.
Did this with unrooted HTC m9 and unrooted Gear 2 with latest FW.
Deleted all the files installed on phone from gear manager.
Download latest GM files (extract/ed from APK)
Install every apk except Host Manager and install Gear Manager App as last
Open GM and connect your Gear 2. As soon as it tries to install Host Manager hit home button/go to your file explorer App on your Phone and install Host Manager 2.2.14100299
Open GM again and cancel Host Manager installation.
Have a little patience and it should show you the option to accept the terms.
Set Notifications in GM App on your phone.
If you prefer Root for Gear then you can root your Gear without problems and you don't have to do this all over again.
Sideloading APK's working fine, had S Voice running but coulndn't connect to watch yet.
Changed Bootscreen, sounds and more without problem.
Redmen What OS are you running? 5.0.2? or 5.0.1?
daroota said:
Redmen What OS are you running? 5.0.2? or 5.0.1?
Click to expand...
Click to collapse
5.0.2 with software: 1.32.401.15
Mmmm, I'm running 5.0.2 CM12S on my OnePlus One, and a friend and myself cannot get it to connect in Gear Manager and activate on the watch itself. My thought was since none of the Samsung Galaxies have 5.0.2 yet, Samsung hasn't build a apk for that version yet. I hope they will update it soon.
Wondering the same thing, love my nexus but rendered my gear 2 pretty much worthless. Any advancements towards this?
Sent from my Nexus 6
There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.
daroota said:
There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.
Click to expand...
Click to collapse
This isn't a viable option for those of us that want to swap to an AOSP based ROM. I've tried this, and while it will pair with the phone OK, the gear manager software doesn't work, therefore you can't receive notifications on the watch. The only function that works when you do this is answering phone calls on the watch, as this can be done without Gear 2, as it uses A2DP (I think) so will work with any bluetooth phone for hands-free.
There is also no way to OTA update from a TW ROM to a custom ROM, unless you are referring to an OTA update from a 4.4.4 based AOSP like CM11 to 5.X/CM12?
Correct. I went from cm11 to cm12 on my one plus via OTA.
Sent from my A0001 using XDA Free mobile app
I'm running Cataclysm ROM (the Sept. 10 beta), Franco kernel, and I'm rooted and use Xposed. I receive this error when I try to add a card in Android Pay: "Android Pay cannot be used: Google is unable to verify that your device of the software running on it is Android compatible". I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. Wallet still works as it always has.
I've seen scattered reports of this here and there but no concrete solutions. Has anyone figured out a workaround?
I get this same message on a LG G2, fully stock, rooted, running 5.0.2.
After some searching, I found this, and it did work for me: https://www.reddit.com/r/Android/comments/3k0ge4/android_pay_workaround_without_xposedrootcloak/
Short version: In SuperSU, disable root, goto Android Pay and activate cards. After cards are activated, enable root. Cards still worked.
I'm not sure if you will need to remove the xposed framework (uninstall from inside the xposed installer) and then disable root. I do not use xposed, so I can't confirm this.
This worked perfectly, thanks!
I also recommend using Lockscreen Disabler with Xposed to get rid of the lockscreen requirement.
Do you have to be on the stock kernel? I'm on the latest 5.1.x build of stock lollipop and have Xposed Framework & Franco Kernel installed. I tried full un-root in SuperSu and rebooting, but I still can get Android Pay to complete the card setup. Do I have to re-flash the stock kernel? I figured this was going to be a PITA. lol I understand Googles need for security on the devices with Android Pay, but the check they are doing have to be so hard-core.
Were you able to successfully make a payment with Android Pay? I can add my cards to the app, but Android Pay isn't working for me at McDonald's or Walgreens.
Will Android Pay work on KitKat or only 5.x.x? I have 2 Nexus 5s, one with 4.4.4 and another with 5.1. On the one with 5.1, I have tried the rootcloak method to put both New Google Wallet and Android Pay to the list, force stopped Android Pay, ran it to the end, and it still gives me the error saying that it cannot be used and is unable to verify the device or software running on it is Android compatible. I also had already updated to GPS v8.1.14 and was under the impression that it wasn't functioning properly, so I rolled back to a previous version of 8.1.13, still returns the same error.
Did you even read all of what OP had to say:
"I tried disabling root entirely and using RootCloak (Xposed) to hide root from Android Pay and Google Wallet, but I still can't use Pay. "
So your comment helps not at all since OP said they disabled Root and STILL have this issue. I have the exact same issue at OP so your comment is not the answer to this question. Any one ELSE have any idea how to resolve when you have already disabled root as OP said.
---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------
Any one who actually READ what OP said have an answer? How to resolve this situation when you have already DISABLED ROOT in SU.
Possible Fix to Android Pay Root + Xposed Issue...
Just found this. Posted last night. Won't be able to test it for a few hours when I get off this plane...
Since it has bothered me for a few days now, I'm going to post this in a few related threads to help others getting the AP rollout. I just found this which looks promising ( http://www.droidforums.net/threads/new-xposed-module-hides-root.284455/ ) Obviously, this requires xposed and is a little bit off topic here, but this approach was not working for me anyway (stock rom and kernel but rooted and with xposed. Also xposed rootcloak did not work either)
I'm on a plane currently, so I cannot test this, but if anyone else can confirm it works / does not work, that would be great. I had gotten to the point that I was able to set up my AMEX card after a clean stock 5.1.1. install and make a purchase before rooting and adding xposed back in the mix. However, now that I am rooted again, I had a purchase denied earlier today. Hopefully this is the solution.
I have not tried it, but heard it did not always work: https://plus.google.com/u/0/114618417341022236593/posts/dUW1QxDjiFH
this didn't work for me, G3 CM12.1
None of this has worked for me.
Yeah I tried root cloak, disabling super user, and all that but none of it work on my G3 running CM 12.1 either
Disabling root in SuperSU did not work for me.
Also seems no one has had this problem, but on a dark layer theme "invertion ui" the text of the card and exp and ccv are white on white, and none of the above has worked for me either.
Nexus 5
Chroma
Xposed
Hells Core b20
same issue with stock nexus 5 that at some point in the past was rooted... after several updates, i never bothered to re-root. SuperSU still there, but doesn't start - no root. But still Android Pay wont work with this error. ugh.
My workaround was to revert to Wallet.
After failing to get Android Pay to work on my rooted Nexus5 with all the suggestions above, I remembered that Google Wallet worked for me last week before updating to Android Pay. I went to Titanium Backup and restored it, and Voila Wallet with all my data! Next, I unchecked the Auto-Update setting in Google Play for the Android Pay app. Then I remembered a Titanium BU Feature that allows you to break the market link of the app. I have not tried a transaction yet, but it sure looks like the old Wallet app will work just fine.
My wife runs a stock non-rooted HTC Mini2 and is perturbed that her loyalty cards are locked out by Android Pay. I think the solution here is to install a version of Wallet that I found on APK mirror/. I'll need to enable "untrusted" apps in settings after gaining developer rights, but it should work without much effort beyond that. I'll try it when she gets home.
I'm rooted with Xposed. I uninstalled Xposed and SU but I still get the error message. Is there any way round this please?
Hello,
I have a Galaxy S6 running the latest 6.0.1 XEF stock ROM (no root) before Nougat.
I have choosen not to update to Nougat for the moment as I prefer to wait for better Nougat releases.
I was quite sure the settings of my S6 were set in order to disable search/install of updates. But yesterday, while connected to my network using Wifi, my S6 has started to download the Nougat updates! But, as I said, I don't want it for the moment. I stopped Wifi, then it stopped downloading the updates. I tried to go to the update settings of the S6 to disable updates but it is not possible now to go the "About device > Software update". And each time I connect to WIFI, it resumes the download of the update .
In the application manager, I found 2 apps related to "Software update": for only 1 of them it is possible to stop it and remove cache and data, which I did. I thought I would have cancelled the download of Nougat update and bring me back the possibility to disable update. But unfortunately, it has no effect. I also tried to wipe cache partition, but the same: it has no effect and each time I connect Wifi, it resumes the download of the update.
So, how I can cancel the download of the update and be able to access to the settings to prevent from downloading/installing it??
Thank you for you help!
There's no need, Nougat is stable now.
If you still doesn't want, let it download the update (because you can't cancel it) then block notifications from both updates apps from the settings.
iDroid27210 said:
There's no need, Nougat is stable now.
Click to expand...
Click to collapse
Really? Latest release for XEF has still the same changelist and I read several complains regarding battery life and lags into the Gallery app for example...
stephg27 said:
Really? Latest release for XEF has still the same changelist and I read several complains regarding battery life and lags into the Gallery app for example...
Click to expand...
Click to collapse
I had very bad battery life on Nougat, i was on UAE firmware. When i bought this second S6 i made a decision to stop using custom roms so i tried to flash another firmware, took the last XEF ( from April) and flashed it 2 weeks ago, my battery improved a lot specially in standby , no issues or whatsoever.
Thanks for your feedback!
phone is full, now what?
Sorry to hijack this thread, but it seems the best fit.
Basically the same question as above: "How do I cancel an OS update download in progress" on my Samsung S6
Reasoning is a little different though. Accidentally I started the update process but during the download my phone ran full.
And as you might know, with a full phone some apps dont work.
Of course Android gives me the option to remove files and apps but immediately the free space is occupied by the running update....
Any ideas?
tia!
Im rooted with twrp and stupid me forgot to make a back up. I messed up my Google play store and apk installs (any app) I installed a mod store and lost ability to install apps so I put the original store back and still couldnt install anything. So I tried a hard reset and still cant install any app. So now I have only stock apps with no ability to install anything. Question... Can i fix this? If so..how?
Or can i use a back up a stock firmware from a different lg stylo 3 plus to restore what was messed up? If i can..anyone have a stock back up?
Thanks in advance.
I'm sure you've already fixed this or moved on but if not, there's an update available for the model used by TMO and the .kdz file has dropped for use with LG Bridge
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
timonoj said:
Hi guys,
I'm considering rooting my G930FD. If I just root it, I should be able to disable most of Samsung crap, correct? I'm concerned about being able to use apps that might detect for root/CFW, such as:
-Google Pay
-HSBC
-MobileIron
Is there a way to hide the root from these? I think MobileIron even checks the knox status, so even if root is hidden/disabled, I might still fail that check.
If I install a CFW, what are the current status of affairs? I haven't installed a CFW since my Galaxy S4 times. As in, if I install any Lineage/AOSP, is there any way to get the camera to work with the stock app, or at least make it perform stock/like? What about Google Pay etc on these ROMs? Any stock-based ROM that keeps the camera while minimizing/rooting out all the touchwiz crap, while still working?
Thanks! I've been out of the game for a couple of years and got lost trying to catch up again...
Click to expand...
Click to collapse
I haven't touched my S7 yet so I can't answer you but this could answer some of your questions:
https://forum.xda-developers.com/galaxy-s7/how-to/debloat-galaxy-s7-services-safe-to-t3432967
You don't necessarily have to root, you have to install TWRP as a custom firmware, then get the script, edit it if you don't want some apps to be removed, apply the script and it's debloated.
But I'm sorry I can't tell you if you can install TWRP without tripping Knox, I can't tell you if installing a custom Firmware will disable Google Pay etc... But I guess you can easily find that information by searching, or someone knowing more than me will help you
Installing TWRP will trip Knox if it's like every other Samsung phone I have owned that referenced Knox or warranty bit in download mode.