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.
Related
Has anyone had a problem with the intial setup for Good for Enterprise on custom Android ROMs? I installed it (using an issued PIN) on stock eclair on my Captivate and it worked fine. I then rooted, backed it up via TIBU and restored on Froyo and it still worked fine. The same process worked recently on Gingerbread. However, I have tried multiple custom Froyo ROMs and 1 GB recently and if I try the initial setup (with a new PIN) on anything other than stock eclair (even rooted), it will stop at "retrieving policies" and never complete. I then have to ask for a new PIN from my IT support and revert to eclair and finish the setup, backup, and restore on the later custom ROMs. Has anyone seen this and have any idea why? My IT support has no idea. I am not in a policy checking for root access and it does continue to work with root.
EDIT: I wonder if it is that the device name used in build properties is referenced during that step and it fails due to an unknown device...
Also, I have found that after I have it working after a certain PIN used, if I ever restore to an ealier point (due to a theme gone wrong, etc) then it stops syncing even if the restore point is AFTER I had it working with that PIN. It seems like the local software either is exchanging a dynamic password with the server or there is a message index, etc that has to be in sync. Any thoughts?
When in the Good setup screen, go to Menu>Device Info. Does the Phone number appear? I've been using CM7 just fine with Good but after the last few nightlies, Good no longer works. The phone number doesn't appear in the device info. Good thinks there is no phone network present.
I am a heavy Good user, unfortunately also addicted to changing ROMs on a frequent basis. I have never had an issue with Good running on any ROM, just on restoring from TiBu. I can flash new kernels, themes, etc, and Good works just fine. If I re-flash the same ROM, it resides and works just fine. It is only when flashing a new ROM I have problems. Good appears to restore OK, but won't pull new emails to the inbox. I ave to get a new PIN and re-install.
Same here.. i am addicted to flashing as well.
I tried Titanium backup to backup and restore to new ROM, but somehow Good just keep crashing after i put in my password.
I am sure I can ask for new pin, reinstall and what not.. but how often can we ask IT people (for my company at least) for new pins, until one day they may say, bugger off you ROM addict!
Finally figured it out, I think. The trick is to NOT have Good running in persistent mode when you do the backup with TiBu. IOW, reboot and backup with TiBu before you start Good and log in. I did that the last couple of new ROMs and it restored and worked just fine.
Sent from my SGH-I897 using XDA App
GOOD for Enterprise on Imito AM801 Tablet
I am also getting the Phone network is off. This is a tablet and does not have any phone piece or sim card installed. No hardware is even inside the tablet. Has anyone ran accross this issue on tablets?
This works for me.
http://forum.xda-developers.com/showthread.php?p=35263313#post35263313
Good with custom roms
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Anteus20 said:
Just to share a recent experience on that topic:
I wanted to have a custom rom but need GFE for my work which of course has a policy of no root with GFE.
So after a little research and useful info from this forum I figured a very simple way to do it, as long as you don't consider root as critical for your day-to-day stuff
1. Install your custom rom which most likely requires rooting
2. Install SuperSU from the Play Store and use it to remove root completely
3. Install and activate GFE
That's it!
Hoope this helps someone else how got a little scared to have to go through scripts and stuff to do this
Using a Galaxy S4 with Carbon Rom
Click to expand...
Click to collapse
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
joshic75 said:
Does this still work?
I too need GFE on my Galaxy S4 but am sick of the poor battery life. I tried SlimKat and Google Play Edition roms, and removed root using Super SU in both cases. But GFE gives a message "Not supported for this type of Handheld". . Not sure if GFE is looking for a TW based ROM.
I will give it another go using Carbon ROM. Still, any other advice / experience on getting GFE working on a custom ROM would be much appreciated.
Thanks.
Click to expand...
Click to collapse
You quoted a 1 year old post, might be hard to get a reply. Also this is for the S1, while the app (GFE) might be the same, the ROMs definitely aren't.
That being said, chances are that the app was updated to prevent that workaround. You could flash a TW based ROM and test it though.
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
joshic75 said:
Thanks for the reply. I will try posting a fresh question in the Q&A thread in case anyone has more recent experience with GFE. Cheers.
Click to expand...
Click to collapse
There is an xposed module for this.
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
joshic75 said:
Hi, are you referring to Wanam Xposed which has a "fake official system status" functionality?
As I understand, Xposed needs root, but Good for enterprise doesn't work on a rooted handset. Can Xposed work without root?
Also Wanam Xposed is meant to work with TW based ROMs whereas I don't want to go back to TW based ROM unless it is extremely light.
Click to expand...
Click to collapse
I'm a bit confused here, Custom ROMs are pre-rooted. Therefor, if you're not on TW, you're rooted.
And yes, Xposed does require root. As for Wanam, I duno if it works on AOSP but best way to know is you try
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
joshic75 said:
Thanks for replying.
Supersu has a Full Unroot functionality which removes root.
Yes I will try, but every failed attempt sends an email to office admin so I have to be prudent.
http://www.gogadgetx.com/xposed-framework-install-use-best-modules-list/
The link above mentions that root is required while installing XPosed, but later it can perform without root. Is this correct or not?
Click to expand...
Click to collapse
I have never personally tried it without root but you can test that fairly easily. I expect it would depend on the module you're using, some require more permissions than others.
I tried it out but it didn't work.
I have to go back to stock ROM
I no longer have this phone!
---
** Debloater for KitKat **
I decided to create a Debloater script for those that want a clean system.
I've used bits from NoMoto - Stock ROM Debloat Scripts (Moto G) by lost101
As with my previous debloater for JB, I've kept the stock launcher (and circle widget + weather).
Steps:
Prepare/flash your preferred KitKat Stock ROM
Flash + Boot into latest TWRP recovery
Flash Moto Razr i XT890 KitKat Debloater - v0.1.zip (attached below)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you should end up with after rebooting:
Have fun!
I no longer have this phone!
---
** Debloater for JB & ICS Stock ROMs **
This debloater was created using scripts from arman68's infiniROM Debloater v2 and bits from Motorola launcher remover v2.
I've also used a few bits & bobs from Razri-Cleaner v0.7, by GalaxyUser.
Steps:
Prepare your preferred JB Stock ROM to flash using RSD Lite (See here and here)
Boot into fastboot and flash custom recovery - I use the latest TWRP
Make a backup of the untouched stock ROM (so you don't have to keep using RSD Lite)
Flash Razr i [XT890] - Stock Lite 4.1.2.zip (attached in first post)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you will end up with after rebooting:
Enjoy. :good:
~
Note:
This works with Omar's ROM. :good:
This will also work for ICS. If you're using the Xposed Framework, you will get a Segmentation Fault upon installing the framework - You will need this.
~
I decided it would be best to keep the stock launcher (and circle widget + weather).
They can be disabled if you're using another launcher. If you disable gallery, you will need to install an alternative.
The following are safe to freeze/disable:
thanks buddy,what browser do you suggest?chrome is really laggy...
Try Dolphin Browser.
hi ! can i use it on an "used" ROM? i dont want to deleite muy files
Script in Kit Kat
Thankx ! :good:
it works in my Kit Kat , all appz working...
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Azurael said:
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Click to expand...
Click to collapse
I'm in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
aben.dc said:
Im in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
Click to expand...
Click to collapse
Had it last with mine too. Clear the cache of Google services. Of try to format cache in recovery.
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
aben.dc said:
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
Click to expand...
Click to collapse
hmm, strange.
Non off the stuff the script deletes is from google play services. So sry, i dunno then
Hi,
I am (was) a beta tester for the KitKat update release. During my test I also tried your KK debloater, I'm a big supporter of debloated roms.
I was on the last KK beta (before final) when I applied the debloater zip: all it was ok (super fast phone!), but when final OTA came out, the debloated KK rom did not receive any update. I wait till today and it is clear that the update will never come. I reinstalled the last Kk beta without debloating and the update came immediately.
I'have done more times the test and I can confirm that the KK debloater inhibits the Motorola updates.
OK, now final KK has been released...but if Moto decided to release another update (like small bugfix), with a debloated KK rom you do not never know the update is ready. The problem is not the installation (it is clear that is better to apply the update on a stock rom), the problem is that you do not receive any notification that tell you a new update is ready.
Do you have any idea how to fix the debloater script in order to be able to still receive system update notification?
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
Ok so I have a gear sm-v700, I have rooted it and updated it via Keis and is now on Tizen software version v700xxecfi and have run into may different things.
1) the Bluetooth sometimes has issues connecting the gear and my rooted note 3( has the stock s.w, just applied a root) I find that I have to reboot both devices in order to connect.
2) I downloaded the sprocket app and downloaded the developer key and can see to down the app on my gear.
What is the correct way to install apps to the gear that do not come directly from the Samsung app store?
Does it need to be done through the command prompt on your pc or can you do it via odin with the correct file downloaded?
My thought on this are and please correct me if I am wrong...
Odin is for flash the custom ROMS, you can side load the aps by getting the apk you want and then running a command via command prompt( I assume that is called side loading).
I rooted the gear with Impactor 0.9.14
What I am looking to do is get the Sprocket App on the Gear so I can get the navigation like google maps on the device.
I would like to shut off the camera sound, its not super important but it would be nice.
Also I want to install the analog keyboard(I have the zip), as well as getting the device to record as much video as I can..whoo hooo super spy watch!!
Some one on here recommended the Andy Camera...I already have that zip.
I know you tube is your friend but I haven't been able to locate what Im looking to do.
Anyone have any other suggestions on cool apps to have?
Hi, maybe someone in here can help me. I just received a Gear vr and I can not get it to work. I am on a custom rom on the sprint network. Here is what happens:
I plug it in and it says to unplug it to install the software. It installs some software and I go to install let's say 'Oculus 360 photos' and at the end a message pops up saying 'unable to install oculus 360 photos'. I pull down the status bar and click on the failure and it says I have to update the software. I update it and it looks like I'd downloads something but never actually updates. That's where I am. Nothing installs, nothing works. Pretty frustrating...
Sent from my SM-G925P using Tapatalk 2
I had the same problem. Went back to stock and it works great. Maybe today I'll root my phone and stay on stock to see if it's a kernel issue. If I do I'll update you.
You probably do not have the required Facebook apps on your ROM. You need at least com.facebook.system and com.facebook.appmanager.
GoeniGoeGoe said:
You probably do not have the required Facebook apps on your ROM. You need at least com.facebook.system and com.facebook.appmanager.
Click to expand...
Click to collapse
I do have both of those on my phone. It's probably being rooted or the custom ROM.
Sent from my SM-G925P using Tapatalk 2
rizzyrailed said:
I had the same problem. Went back to stock and it works great. Maybe today I'll root my phone and stay on stock to see if it's a kernel issue. If I do I'll update you.
Click to expand...
Click to collapse
Yes, please let me know. I think it has to do with the custom ROM or being rooted.
Sent from my SM-G925P using Tapatalk 2
No problem with being rooted. Custom ROM 100% the case. You need a stock-based TW kernel and therefore stock TW rom with the VR update built-in
seven2099 said:
No problem with being rooted. Custom ROM 100% the case. You need a stock-based TW kernel and therefore stock TW rom with the VR update built-in
Click to expand...
Click to collapse
Thanks for the update. I think that's my problem. I don't think there is a rooted stock based kernel on Sprint.
Sent from my SM-G925P using Tapatalk 2
It's not the kernel. Finally just installed the newest v9 kernel and rooted my phone. I suggest maybe starting with stock, install the vr software and run once then root. Soon I'll install the newest renegade full rom and see what that does.
It's not the rom either. I may be telling you to do more than you have to but maybe just go to stock, get vr apps then root and clean install full rom. Everything is great for me.
Hey, Did you guys solved it?? I have the same problem
I have a G928P, and I had rooted for unlocking it. Because of this problem, I unrooted the phone... Now I get the ****ing free hand activation message (at least it kept unlocked), but the problem is still there... Any idea???
Athossss said:
Hey, Did you guys solved it?? I have the same problem
I have a G928P, and I had rooted for unlocking it. Because of this problem, I unrooted the phone... Now I get the ****ing free hand activation message (at least it kept unlocked), but the problem is still there... Any idea???
Click to expand...
Click to collapse
I solved it. (More or less...)
Edit the file is downloading in the folder "Download" of your cell phone BEFORE it finish. For a reason that I DON´T understand, the software delete this file once it is completed, instead to install it. When you edit the name in the meantime is downloading, you impide it. Then, rename it back to .apk (if not it will keep as ".apk_downloading so you can´t install it), and install it manually.
It finally works.
Does anyone knows how could I impide the file gets deleted? I don´t mind if I have to install it manually, as long as I can. So far, when the app is not very big, I have to be VERY fast in the editing..., or I will not be able to do it.
Im curious, oculus vr worked flawlessly, unil i installed "package disabler pro" and removed "bloat".
I have read that facebook apps are required (rediculous... F*+-ing facebook bulls&*#@.)
Bit is anyone aware of what "bloat is required for functionality?
Sent from my SM-N920W8 using Tapatalk 4
Athossss said:
I solved it. (More or less...)
Edit the file is downloading in the folder "Download" of your cell phone BEFORE it finish. For a reason that I DON´T understand, the software delete this file once it is completed, instead to install it. When you edit the name in the meantime is downloading, you impide it. Then, rename it back to .apk (if not it will keep as ".apk_downloading so you can´t install it), and install it manually.
It finally works.
Does anyone knows how could I impide the file gets deleted? I don´t mind if I have to install it manually, as long as I can. So far, when the app is not very big, I have to be VERY fast in the editing..., or I will not be able to do it.
Click to expand...
Click to collapse
Hello,
I had the same kind of issue on my note 4: update & install of the essential apps were always failing (photos 360, videos, videos 360).
I managed to update by renaming the downloaded file before it got deleted, but I had to do the same operation for all apps then install them manually before I could access the Oculus store.
I wonder why installs fail like that. I rooted the phone with cf-auto-root to be able to use my PS3 controller wirelessly. Maybe it is becuse the kernel is slightly modified for root?
EDIT: Also it seems I will need to use the same method for all installation I do from the oculus store! I really want to fix this. I'll probably try unrooting...
Rooted, it will not work
Sillik said:
Hello,
I had the same kind of issue on my note 4: update & install of the essential apps were always failing (photos 360, videos, videos 360).
I managed to update by renaming the downloaded file before it got deleted, but I had to do the same operation for all apps then install them manually before I could access the Oculus store.
I wonder why installs fail like that. I rooted the phone with cf-auto-root to be able to use my PS3 controller wirelessly. Maybe it is becuse the kernel is slightly modified for root?
EDIT: Also it seems I will need to use the same method for all installation I do from the oculus store! I really want to fix this. I'll probably try unrooting...
Click to expand...
Click to collapse
If the phone is rooted, it will not work. No matter how you install the apps, it will never open oculus.
I had to unroot, and it worked again (installing apps manually, as I explained before). Once rooted again, I even tried to substitute the kernel for the original one. That allowed me to enter in Oculus, but the VR never worked. I had to unroot again.
Does anyone know how to impide it delete the apk file automatically? At least that would help.
Finally got into the process and sign into oculus app
Hi guys,
I finally succeeded in getting the download process working:
- log the samsung app output with logcat via adb
- click on install button of the Gear Vr configuration wizzard
- catch the called urls on logcat and copy/paste them on your browser to download the APKs
( for me : prePost_20160128024220687.apk
prePost_20160128024344077.apk
prePost_20160330073402086.apk
prePost_20160330073501789.apk
prePost_20160330073641987.apk
prePost_20160330073735750.apk)
- install them in the order the urls were called ( adb install -r prePost_20160128024344077.apk )
- on the device, stop the download using the cross
- click the install button again
The download should now be successful.
on Galaxy S6
celkin said:
Im curious, oculus vr worked flawlessly, unil i installed "package disabler pro" and removed "bloat".
I have read that facebook apps are required (rediculous... F*+-ing facebook bulls&*#@.)
Bit is anyone aware of what "bloat is required for functionality?
Sent from my SM-N920W8 using Tapatalk 4
Click to expand...
Click to collapse
Package Disabler Pro locks out all the needed VR apps. I uninstalled it and the VR works great!
Question
netengineer said:
I do have both of those on my phone. It's probably being rooted or the custom ROM.
Sent from my SM-G925P using Tapatalk 2
Click to expand...
Click to collapse
Hey do you known if your phone is a little cracked if the vr will still work good