I'm using a Galaxy watch 4 Classic for a month now and it has been working perfectly fine. But the only issue I'm facing is unable to quickly reconnect after my phone restarts. I have to repeat the long first-time connection procedure (which has got quite frustrating TBH). I even have to do this when I turn on Flight Mode on my phone. I know it is not how it is supposed to act normally but I believe there must be some solution to this.
It seems to be something wrong with my Samsung Wearables app. It does not seem to remember any device after a restart.
Also to mention, my phone is rooted if that is causing this.
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer) from here:
https://github.com/3arthur6/BluetoothLibraryPatcher/releases/tag/v2.4.1
And this problem should go away. Reboot and re-pair your device. Should remember them afterwards.
I tried to install the Bluetooth patch file but, the root manager I have installed "EFTSU Manager", does not open any of the Bluetooth patch files I downloaded. I installed Magsik but it does not seem to work on this device. Also my device boots normally. No TWRP from where I can install packages.
Please guide me on how I should make this work... If any additional details are required, ask ill provide them.
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Here my "Diary"...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
IMHO only fixed after FukKkKtory Reset Watch again.
Best Regards
Skipping f%$ing useless Intro by tap tap few times on Screen.
This is since Tizen totally stupid feature because in earlier Tizen firmware Intro asked for skip...
Seems Samsung loves to torture user by stupid tasks.
Best Regards
adfree said:
If not Top Secret...
Why not tell Model Name of your Phone...
Samsung not Samsung?
For instance I fixed this ugly issue on my Samsung SM-A202F rooted with Magisk...
Best Regards
Click to expand...
Click to collapse
My Device is Samsung Galaxy S9 SM-G960F. I guess it is not rooted with magisk because magisk app wont work on this device.
ShaDisNX255 said:
It is indeed your root that's causing this problem
Install the Bluetooth Library patcher via Magisk or TWRP (whichever you prefer)
Click to expand...
Click to collapse
As you told, i tried to install the patch file using Magisk for which i installed Magisk. But it did not seem to work. Have a look at the screenshots from the app and log.
What should i do now.
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
Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match
I’ve recently been trying to root my Samsung SM-J710FN. I managed to find a sequence of actions that consistently produces a rooted phone. I found TWRP 3.0.2 (I know that later versions exist, but this is the latest I could find for this model) and flashed it using Odin. I then use it to wipe the data partition (because, apparently, TWRP doesn’t work well with encryption). I use adb push to copy SuperSU 2.79 (downloaded from here) and no-verity-opt-encrypt-6.0 (in accordance with instructions in this thread, downloaded from here) to /data, then I install both of them using TWRP and reboot.
While the phone does appear rooted, it does end up having some serious problems. Here are some that I managed to find:
The camera doesn’t work. When I try to start the Camera app, it just crashes after a few moments.
The flashlight doesn’t work. When I try to turn it on using the button in the quick settings panel at the top, I get a message saying that the Camera app is using the flashlight (and the flashlight doesn’t turn on, obviously).
The phone does not automatically change orientation as I rotate it (in apps that are supposed to support it, such as Google Chrome), even though the appropriate settings are enabled.
The brightness controls do not affect the screen’s brightness in any way.
(I also can’t manage to re-encrypt the phone after rooting it, but that’s probably better left for a different thread.)
Has anyone else encountered similar problems? What can I do to solve them?
Have you tried to reflash stock ROM again?
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
I finally figured it out. Looks like I should have used a different SuperSU version. I repeated the process using SuperSU v2.82 SR5 and the problems stopped.
(I’m still trying to get the phone to be both rooted and encrypted, but that’s a separate story…)
EDIT: I gave up on SuperSU and used Magisk instead. It’s much easier and seems to work perfectly even with encryption!
Can you give me link to download a Android system and Magisk. Which one you used. I have the same problem :c
Here’s Magisk: https://forum.xda-developers.com/apps/magisk
As for “Android system”, do you mean stock firmware? In that case, I’m really sorry but I haven’t really kept a link to the place I downloaded it from Besides, you need stock firmware that matches your specific phone (based on the part of the world where you bought the phone, I think? I’m not quite sure), which may not be the same as mine.
I've already done it, I downloaded all the necessary files from sammobile.com
But thank you for your willingness to help
voidphantom said:
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
Click to expand...
Click to collapse
Can you give me the link of the Stock ROM?
When twrp install j7 max then phone go to bootloop problem please tell me how I fix this problem
dealiyo said:
Can you give me the link of the Stock ROM?
Click to expand...
Click to collapse
As I said before, unfortunately, I have not kept a link to the stock firmware. Further, judging by your other posts, you don’t seem to have a device of the same model as mine (I have SM-J710FN, you said you have SM-J710GN), which means my stock firmware isn’t going to be useful to you anyway.
Hello! currently running Dr. Ketan S09 on SM-S908B/DS and was wondering if there are any modules that can replace system audio files for customization?
I tried older method with this flasher tool that @alessio89g created some years ago. I used my favorite Metal Gear Solid sounds in this pack. however when flashing it complains that magisk needs to be updated to 13 or something.
It's a long shot but maybe someone is knowledgeable enough to fix up this zip and get it working so we can all enjoy?
Thanks for any help and input on this
C3R741N said:
Hello! currently running Dr. Ketan S09 on SM-S908B/DS and was wondering if there are any modules that can replace system audio files for customization?
I tried older method with this flasher tool that @alessio89g created some years ago. I used my favorite Metal Gear Solid sounds in this pack. however when flashing it complains that magisk needs to be updated to 13 or something.
It's a long shot but maybe someone is knowledgeable enough to fix up this zip and get it working so we can all enjoy?
Thanks for any help and input on this
Click to expand...
Click to collapse
Try this
dr.ketan said:
Try this
Click to expand...
Click to collapse
I will update how this goes soon, I unfortunately have to triple wipe and re-setup device. Google Fi support had me boot into safe mode when trying to get my 5g service to stay on (it kept staying on 4g) and doing so wiped the rom when booting back in so I'm going stock , getting my 5g to work correctly, then setting up rom again, and then I will flash this nice module you linked for me and let you know how it goes. Thanks Doc
(as it turns out it was googles network acting up for some devices and is being fixed, made me screw up phone for no reason)
alessio89g also responded in another thread and gave me these also haven't tested them yet but said they can be used in roms, the apk might be helpful for selecting sounds in roms that can't access /media
I will update as soon as I get a chance to test all this stuffs
dr.ketan said:
Try this
Click to expand...
Click to collapse
IT WORKS ALMOST 100% PERFECTLY THANK YOU SOO MUCH!!!!! the only thing I need to adjust is the volume for unlock and lock because it's a tad quiet and the only sound I can't get to play is when using the navigation bar buttons(S_HW_Touch.ogg). I had a sound set to the right file but it's not playing anything.
I realized this file was used back on Note 5 when we used to have physical buttons on the phone but now we have UI integrated buttons on the screen, so not sure if this file even activates a sound for that anymore, or why its still in the system files, but I also don't understand how that's all linked together so maybe we can't assign a sound to those anymore?
Hi,
ive tried to root my Galaxy S10 via Magisk. Everything worked just fine, i patched the AP file thrue Magisk, istalled via ODIN and started the device like mentioned in the manuals. When i started the device the Magisk App appeared after some seconds, i pressed install and it installed. Now comes the strange thing. When i start the app it still seems like there is no root whatsoever. It doesnt ask me for anything else and it looks just like the same as before.
Does anyone know what to do?
thanks for your help in adcance
Don't nail me but I believe one must patch recovery and boot into recovery mode all the time. I know there was NEMESIS kernel that could boot straight into Magisk. also on github for the S10e issues there are some replies from dev to patch boot.img, which is contradictory to Magisk installation guide, so I don't know for sure.