Hey all,
I updated my UK N8010 to the German release of 4.1.1, but since then S Note has been crashing constantly. I tried a full factory reset of the device, as well as a couple of backups of the app, and have tried fully uninstalling it and re-installing it from an APK I found online, none of these have managed to get it working sadly.
Some searching shows people having issues with S Note, but none like this, and none with any fix. So, has anyone else had this problem? And if so, what did you do to for it? Also if anybody has the APK file for the version of S Note that ships with the 4.1.1 release that would be great if you could share it please?
Ta!
I could use this too, in my case it doesn't crash but does have a blank UI.
EDIT: Had same issue after installing new Redemption ROM which I thought was weird, so removed all Pimp My Rom tweaks and now S-Note works fine. So in my case it was something I did (possibly the Sony Bravia tweak, who knows), whoops.
Oops
Hi there, I'm not feeling very cluey right now.
I finally got around to trying a custom ROM, I went with the latest one @daniel_hk had uploaded which was Slim-p6810-4.4.4.build.7.2.1-UNOFFICIAL-20140816-1116.
I used the cwm-6.0.2.3-p6810.tar recovery.
I had been using the official ICS ROM from a long time ago, it mostly worked fine for me but an app I've started using recently says it really wants a newer version of android.
Before flashing it I took a backup.
Having used the SlimKat for a bit I found a few things I wanted to work didn't and the colour inversion thing was getting to me so I tried CARBON-KK-UNOFFICIAL-20140912-1616-p6810 to see if it would work well enough for me. It has the same Bluetooth problem but I haven't had the screen inversion problem.
Before trying the second custom ROM I also took a backup. I also took a backup after setting up the Carbon ROM so I wouldn't have to do it twice!
Somewhere around here I noticed that my Winblows 7 PC wasn't recognising the tablet anymore, it also was charging slower than it used to.
Wanting to go back to the ICS ROM I was using originally I booted into recovery and went to restore it and here's the problem.
It isn't there to restore.
The other two backups I made are there though.
I was going back to ICS to see if Winblows would detect it again, although I'm starting to suspect that the USB board in the tablet might be faulty now. Windows says that the device has malfunctioned so it doesn't recognise it, I've tried numerous different versions of the USB driver. I remember Winblows update saying it had a newer version of the Samsung Android drivers and let it update them, this may have been a mistake.
So how do I restore my ICS backup, I think I recall there being a file system change when they added the multiple accounts on a device patch, 4.3 I think, so is that part of my problem?
I've also tried using twrp-2.8.0.0 and discovered that it can't use the CWM backups and I then flashed cwm-6.0.4.5 to see if the newest version would help me. Still no dice. As my tablet won't talk to my PC I flashed that with Mobile Odin Pro, I'd avoided buying that as I will probably be getting a Sony Z3 Compact Tablet and Odin seems to be a Samsung only thing.
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
Hey guys!
I'm wondering if anyone else is having a problem with MirrorShare working in the latest update. I just recently tried using it and nothing is showing up for me to connect to. This is very disappointing. If anyone has gotten this to work, I appreciate any advice.
BTW: I'm rooted with TWRP custom recovery and I have xposed installed as well.
Thanks!
Here! But MirrorShare is not the only thing in B571. GPS is also f****d up after the latest update. Also some of my apps stopped working and can't be opened.
I am not rooted and have no unlocked bootloader.
Hi, I have fixed my phone thanks to other users, When Xperia Manager repaired phone, It installed Android 7.0, Everthing works fine except for the Stock Camera application which says it is being used by another application. If I insall another camer application it works fine and snapchat etc. Any ideas of way to fix, I have tried xperia manager again to repair and still the same. Anynone else having this issue ??
Its ok seen how to solve it with unlocking bootloader again.
Thanks
Did you try rebooting your phone?
jmwtac said:
Hi, I have fixed my phone thanks to other users, When Xperia Manager repaired phone, It installed Android 7.0, Everthing works fine except for the Stock Camera application which says it is being used by another application. If I insall another camer application it works fine and snapchat etc. Any ideas of way to fix, I have tried xperia manager again to repair and still the same. Anynone else having this issue ??
Its ok seen how to solve it with unlocking bootloader again.
Thanks
Click to expand...
Click to collapse
Please check the other threads before posting, this issue has been solved already.
You need to Unlock your bootloader again on N using Sony's official guide.