I have followed every set of instructions I've been able to find on installing the Galaxy S6 keyboard on any android device, yet I still haven't gotten it to install successfully.
Has anyone tried to install it and gotten it to work? If not, what keyboard are you using?
put it in to system app
I believe that since it is a Samsung app it will require Samsung's framework for Touchwiz which is not compatible with our device.
It needs the Touchwiz Framework, something we don't have or any phone or tablet outside of Samsung devices has.
Related
Is it possible to install Gear Manager on a non-rooted Google Nexus 7 (2013)?
I've been scouring the forums and followed the steps in http://forum.xda-developers.com/showthread.php?t=2500999.
When it came to GR.GearManagerStub.apk, I installed it by copying it to my Nexus and ran it. I cannot copy it to system/data since I don't have access on a non-rooted device.
Gear manager runs but the manual connection to the pre-paired Gear always fails. FYI, I'm running Null_19.
Thanks for your help.
Well you can't do anything without the geamanagerstub apk. It needs to be a system app. Therefore you need to be rooted
note: null does not affect connecting to a device in anyway. It is still the same stock rom with a few extra features unlocked
ActiveNick said:
Is it possible to install Gear Manager on a non-rooted Google Nexus 7 (2013)?
I've been scouring the forums and followed the steps in http://forum.xda-developers.com/showthread.php?t=2500999.
When it came to GR.GearManagerStub.apk, I installed it by copying it to my Nexus and ran it. I cannot copy it to system/data since I don't have access on a non-rooted device.
Gear manager runs but the manual connection to the pre-paired Gear always fails. FYI, I'm running Null_19.
Thanks for your help.
Click to expand...
Click to collapse
The only other option is installing a custom recovery and flashing it...
Hi!
Does anybody know if it would be possible to install the 'settings.apk' from any android ROM to the Gear using a stock ROM?
I've seen some custom ROMs have already included it (like Null ROM) but I don't really need a full custom ROM for the moment, just that little piece of software... So, would it be possible to take the deodexed apk file from one of those and install it directly to the Gear?
I tried this naive idea and extracted the .apk from the Null ROM, I tried to install it using ADB but unfortunately it didn't work (I would had been so lucky :silly: ). I got this message:
Code:
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
I hope there's some easy way to achieve this :fingers-crossed:
Thank you!
The stock gear rom is a stripped down version of the samsung TW 4.2.2 rom, which has a lot of the dependencies in the setting removed already. If you tried to install any settings.apk, it will not work as it cannot find the dependencies that is required to run.
If you want to get into a new stock rom without pairing first, there is a way to do that. You will need to install the mk7 stock rom (via odin), and then install twrp recovery (via odin), then go into twrp recovery, mount system folder, then delete the secsetupwizard.apk, reboot, then you are at the clock, and can go into settings.
So, mk7 stock ROM is the stripped down version TW 4.2.2 ROM used in our Galaxy Gear by default, right?
Following your instructions I would get the stock ROM, a custom recovery and I would skip the initial pairing with mobile configuration but I wouldn't get the full settings application.
From what I have understood, the only way to get full settings in our watch is by installing a full custom ROM, right?
Thanks for answering quickly
yup, thats my understanding.
Then I suppose I'll have to consider that
You won't regret it. I am running null_23 now. With everything installed, I am getting about 3-4 days battery life. Though I am just using it as a notification unit, no internet(I find it too slow on the watch), no phone calls, and maybe some spy pictures , but to me I think this little watch is perfect for my needs.
Good luck.
I'll give it a try.
Btw, are you using Gear Manager for the notifications? I've noticed some trouble having installed apps on stock ROM and using Gear Manager on its lastest version (apps kept disappearing from the launcher, although were still installed).
Right now I am using ATN manager for notifications. Yes The latest gear manager does sort of "uninstall" the 3rd party apps. I have read in one of the other threads here that earlier versions of GM does not do this. So you may want to download one of the earlier GM versions and give it a try.
I see that I received an update to the Gear Manager today. Now I can't connect the Galaxy S4 to the Gear 2 Neo. Anyone else having this problem?
Background:
Before I noticed the update (which had connected to the Neo just fine), I looked at the watch faces running under Multi Watch and saw they were corrupted (the number for the calendar had floated off to the upper right in the screen). So I decided to reset my watch. When I tried to connect, the watch and phone evidently exchanged PINs correctly, but the phone kept jumping back to the 'Connect' screen and wouldn't recognize the watch as connected.
The Gear keeps reverting to the "select the Gear you want your phone to connect to" screen.
Gear seems paired successfully in the phone's BT settings, but won't connect there either.
Multiple deletes of the Gear in the Bluetooth settings haven't worked. Uninstalled and reinstalled the Gear Manager several times. Cleared all the caches and data for Gear Manager several times.
S4 rooted with Towelroot; SuperSU installed. Root access granted to Titanium Backup, Memory Booster, Root Explorer. Formerly had BusyBox on it and xPosed framework (running Wanam). Uninstalled BusyBox and xPosed and Wanam.
Any ideas?
Did you reboot both the phone and the gear?
Last resort is to reset the gear. It is a pain, but is better than not having it connected. I had to do the same thing.
Yes - rebooted both the phone and the Gear 2 Neo several times. I've been able to test this with another Galaxy S4 and a Galaxy S5 and the Neo connects to both of them. Looks like the problem is in the app, or something that happened when my S4 got rooted.
Looks like the Gear 2 Neo goes back in the box until another update comes out for Gear Manager.
prscott1 said:
Did you reboot both the phone and the gear?
Last resort is to reset the gear. It is a pain, but is better than not having it connected. I had to do the same thing.
Click to expand...
Click to collapse
Another option is to remove the gear manager you installed from sammy and install the one found on this thread: http://forum.xda-developers.com/showthread.php?t=2677686
And is the ROM you have on kitkat?
Good idea - tried it and got the same response. Couldn't find a version number on the one from the link, but I suspect it is the same as Sammy released today.
ROM is stock 4.4.2 Android from VZ - I545VRIFNC5. Rooted. I put BusyBox Pro back on there, and xPosed framework, and Wanam, but I haven't yet enabled Wanam.
prscott1 said:
Another option is to remove the gear manager you installed from sammy and install the one found on this thread: http://forum.xda-developers.com/showthread.php?t=2677686
And is the ROM you have on kitkat?
Click to expand...
Click to collapse
n4ogl said:
Good idea - tried it and got the same response. Couldn't find a version number on the one from the link, but I suspect it is the same as Sammy released today.
ROM is stock 4.4.2 Android from VZ - I545VRIFNC5. Rooted. I put BusyBox Pro back on there, and xPosed framework, and Wanam, but I haven't yet enabled Wanam.
Click to expand...
Click to collapse
Just had the same, what happened to me was that I flashed a new ROM, couldn't get it to connect just like yours.
Resolution was to flash another ROM, one that is basically stock.
Then the Gear Manager kicked in and installed all the relevant apps for the gear neo when I opened it.
I believe that the problem was with some missing files from the ROM I installed first when it stopped working.
I also had to go to get then newer "galaxy apps" from Samsung's mobile website..
You could make a backup and flash some other stock rooted ROM see if that helps..
Otherwise I don't know, this was just a a suggestion..
M..
Question from a n00b
I was successful in rooting VRUFNC5, so here's my (probably noob) question:
Is there a VRUFNC5 file that I can put on the SDCard and use to reflash my phone to stock?
I am not experienced in using ODIN, and the instructions I've found here seem to presume a bit of knowledge that I am not confident I have.
If I can get it back to stock, I'll reconnect the Gear 2 Neo, and then re-root it.
mattbee said:
Just had the same, what happened to me was that I flashed a new ROM, couldn't get it to connect just like yours.
Resolution was to flash another ROM, one that is basically stock.
Then the Gear Manager kicked in and installed all the relevant apps for the gear neo when I opened it.
I believe that the problem was with some missing files from the ROM I installed first when it stopped working.
I also had to go to get then newer "galaxy apps" from Samsung's mobile website..
You could make a backup and flash some other stock rooted ROM see if that helps..
Otherwise I don't know, this was just a a suggestion..
M..
Click to expand...
Click to collapse
Hey! So i'm trying to install the Market Helper app on my Galaxy S3, which tricks google into thinking your phone is something else so you can install apps not compatible with your device. But every time I run it, when it gets to step 2 "doing magical stuff" it just stops, it comes up with the error "Unfortunately, market helper has stopped". So I am running the Codename Lungo rom for Galaxy S3 I9305 and my phone is rooted with Super User working. I tried wiping and formatting the phone and reinstalling the rom, and then trying the Market Helper, still doesn't work. Even immediately after I install the market helper, no difference. Anyone know how to fix this?
I cannot Install Xposed in a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
Make sure you're using a deodexed rom and not a Nougat and one more thing use Samsung xposed version support by wanam for example
ghoster76 said:
Make sure you're using a deodexed rom and not a Nougat and one more thing use Samsung xposed version support by wanam for example
Click to expand...
Click to collapse
Thank you for the info. I have no idea what that is. But I'll research it and figure it out.
samsung use this https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by wanam
It worked!! I was about to go insane with this xposed framework installation. I can finally play youtube videos on the background without ads. The community on this site is amazing.
Thank you so much for your help.
If you ever come to Spain, I'll give you a tour to celebrate!?