My users get update errors in GooglePlay with errors "907" and "963" and I believe it is because the app is installed on external sdcard.
So I just think to prevent this I could change the install behaviour of my app be changing the android:installLocation from "auto" to "internalOnly".
Now I am not sure what happens to all already installed apps located on the external memory card, when they update to a version configured to "internalOnly".
Is there any issue, risk that the install will fail ?
The error 907 is similar to Android error 963 where installation or update is cancelled right after the download bar reaches completion. If you have already tried re-installing after a reboot and you're still getting this error, here is how you can fix the error:
Clear Cache and Data.
Update Google Play Store - check if your Google Play Store is the latest version.
*Unmount SD card before install
You may check this forum for more solution offered by community: http://valuestuffz.blogspot.com/2015/06/how-to-fix-error-907-in-google-play.html
For your question, 'now I am not sure what happens to all already installed apps located on the external memory card, when they update to a version configured to "internalOnly"?
It depends on your version of Android. Android 6.0 Marshmallow lets your 'adopt' your SD card. Some pre-Marshmallow devices may let you move apps manually, but only if the developer allows it. If you want more flexibility than either of these options offer, you can root your phone and use an app called Link2SD to make it happen.
Additionally, when you adopt your SD card as internal storage, you cannot remove the SD card from the device without affecting the functionality of your device and the SD card is not usable in any other device.
Related
I am trying to enroll a fleet of Android 5.1 devices which did never receive a newer version of Android and are not working with any third party ROM. So we're stuck on 5.1.
As the Google Play Services in the ROM was so old, that I couldn't even install the Android Device Policy DPC, I updated the Play Services in the ROM using an update.zip, wiped the device and then enrolled the device using a NFC tag.
Unfortunately, enrollment is not working, and I'm not even getting an error message. The DPC seems to set itself as the device owner, but no enrollment is taking place - the device does not show up on the API, and upon launching the DPC from the application drawer and clicking on the "Get started"-button, we always are presented with "Your system cannot be managed by this app. Please contact your administrator".
Well, I am the administrator and I have no clue, why this is failing.
Has anyone an idea, what the DPC is looking for before deciding that the device cannot be managed? Or how to get a more meaningful message out of the DPC?
The Android Management API doesn't support NFC provisioning on Android 5.1. It is only supported on Android 6.0 and above.
The documentation previously mentioned that 5.1 is supported, that was an error and we have now updated it.
I have been developing a Windows phone app on my lunch breaks at work and spare time at home. The project is stored in my Dropbox so it's the same on both pcs. At work when I debug/deploy to the device everything is fine and dandy. At home however I get the following.
Error : DEP6100 : The following unexpected error occurred during boostrapping stage 'Connecting to the device':
SmartDeviceException - Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Error : DEP6200 : Boostrapping 'Device' failed. Device cannot be found. Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
Now in both cases I'm using the same version of the SDK and of VS on the same Microsoft account on the same phone on the same project. But it doesn't work.
I have reinstall the SDK twice now to no avail.
When I run the device registration I get the following message.
Unable to connect to a phone. Make sure the Windows Phone IP over USB transport service is running
I'm not sure what I'm doing wrong here, has anyone run into this before? Any ideas of a fix for the issue?
Update:
I have uninstalled 2013 r4 and installed 2015. I have done a hard reset on my phone. I have run Windows Update and I'm up to date. I have tried making brand new projects as some of the posts suggest, to no avail. Same issue occurs, except now my emulators get:
The following unexpected error occurred during bootstrapping stage 'Connecting to the device '184901A8-DC44-4CED-869E-DC7733D048D6'
I'm guessing the next step is reinstalling Windows, I think I'll just wait till Windows 10 comes out.
Possible Fixes:
1.Try reconnecting your phone.
2. try re registering your phone as developer device
3. try this fix
https://dev.windowsphone.com/en-US/OEM/docs/Phone_Testing/Configuring_IP_over_USB
Testing apps on windows phones can be frustrating. One common problem I get is the need to reinstall drivers for the phone. I think this may be your problem.
The other problem similar to this I've encountered, was when registering for windows phone not using the correct version on that pc for 8.0 or 8.1.
Aside from this, there is a list with links provided that may help you. Let us know how you get on.
This link Problems and fixes when registering a Windows Phone 8 device to deploy/debug applications covers the major issues, some mentioned by Akash.
The following is a summary of the points discussed in the above link:
Windows Phone IP Over USB Transport(IpOverUsbSvc) service is running
Phone name is already in use by this account
Too many phones have already been registered with your account
Device lockscreen has to be unlocked (and it is unlocked)
Can’t find any devices
Point 5 is also addressed in this answer https://stackoverflow.com/a/30303946/3956566.
Update after comment
The other thing that you may need to do is:
1. make sure you have all your updates in Windows.
2. Make sure you have all VS updates.
3. reinstall VS.
4. Reinstall any .net framework packages for VS.
The first two are the most likely things.
If worse comes to worse, to reinstall windows.
I have needed to do all of the above at one time or another to fix various issues. Painful, yes.
And don't forget to reboot your machine.
Let me know if this works. There MUST be a solution.
I know what you mean about the phone appearing in explorer, update anyway, won't hurt to reinstall them.
This might sound like a stupid question, but what is the current version of Genymotion? I just downloaded Genymotion this morning.
How do you download Google Play for Genymotion? I am emulating Android 4.4.0.
How do you get Clash of Clans on Genymotion?
I use a Mac, version 10.9.
The current version is: 2.2.0. You can check that out in Help menu
To install Google Play, you need to install some Google play services. Some of them are GApps , PaGApps. You can google them out to know more.
You can get Gapps here. This version is for Virtual devices running 4.3 or above. There are different package available (micro, mini, full, stock). Read the description for all the details you need.
You can get paGApps here. This also contains different packages. Read the full file name for more info
You just need to drag and drop the downloaded zip file to
To your 3rd question, Clash of Clans is a 3d game. Though I haven't tried it on Genymotion emulator, the game might require some dependencies like ARM Translation. But, nothing can be learned without trying. So, try grabbing an APK of Clash of titans, drag and drop the apk to the emulator and check if it installs. If it does, try to play and enjoy.
I own a ZTE Open, UK edition. I tried upgrading from 1.0 to 1.2 following these instructions.
https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/comment-page-1/#comments
The update I installed came from ZTE themselves, and was not a custom, or third-party ROM.
The upgrade worked smoothly and had no errors, and I was prompted to reboot my device. Since then it has been in a reboot loop.
I've tried entering recovery mode and restoring to factory settings, but nothing worked. Likewise, I've tried wiping the cache from recovery mode, but with no success.
Any help would be much appreciated.
EDIT: Also worth adding that I cannot access the phone via ADB or Fastboot.
I had a similar problem when I tried to update to 1.2 using the same tutorial
(I have the US model).
The problem seems to be jumping from 1.0 to 1.2. You need to load 1.1 first, then 1.2.
The solution for me was to download both of the ZTE Official 1.1 updates linked on the
ZTE Open device page for my region (on the mozilla developer website under the heading "Upgrading Firefox OS" linked below).
Do not change the downloaded files names, just unzip them both and put both .zip files on the root of an sd card and reboot into recovery.
You should be able to flash one of the two files using the install update choice, the other will give an error (I can't read the full filenames on the phone so I'm not sure which one actually worked for me, that is why I say just try both.)
After flashing you should clear cache, wipe data and reboot.
If all goes well you should have a fresh factory load of 1.1 on you phone and you can now follow that tutorial to upgrade to the developer preview of 1.2.
If your recovery won't flash either of the official EU 1.1 updates you may have some how replaced your stock EU firmware with a stock US firmware, one update will say signature verification error and the other one will give another longer error 7 something or other. I replaced my US firmware with an EU firmware (v1.0) without realizing it and thought my phone was totally bricked because I couldn't get any US 1.1 firmware to flash and I couldn't get to fastboot or adb to manually flash a build (I loaded EU 1.0 version then used fastboot to flash a 1.4 build that wouldn't boot). The solution to that problem was to load an official EU 1.1 .zip from recovery and then load the US 1.2 developer preview from fastboot which replaces the EU recovery and let me flash an official US 1.1 .zip build.
Try not to mix and match firmwares from different regions, the Open doesn't seem to like that.
I was able to get the ZTE preview of 1.2 to work but it has a nasty bug with the notification bar so I went back to the official 1.1 build so you may want to stay at 1.1. If you do load 1.2, the key to using the notification bar is to tap and hold above the screen and slowly "roll" your finger onto the bar until you can pull it down (that might not make much sense now but if you get 1.2 loaded you will understand).
Hope that helps.
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN
When upgrading to V1.1 before attempting to upgrade further, I might be able to explain why #Foo observed that only one of the two ZTE files worked (ZTE file links: European, US - each has two files). I didn't hit the reboot loop, but I was unable to install what looked like the right file.
The reason is that there are two links for upgrading to V1.1.0B02 - one link is labeled "(for V1.0)" and the other is labeled "(for V1.1)". This really tripped me up as I was scanning the list for 1.1 and jumping over the (right) file labeled for 1.0.
Very clearly, if you are upgrading from 1.0, then you need the "V1.1.0B02(for V1.0)" version. Just downloading both and trying each one may be easiest, but it vexed me to not understand this.
If you pick the wrong one, I found the error message (E:signature verification failed) to be very unhelpful after booting into recovery and attempt to flash from the SD card.
I've configured an email ID (obviously gmail id) to 20 android devices all are situated at different place now if i want to install an application. to all device like Avast antivirus
if any device have already installed then how could i be able to do this.
Goal :
1: Install an application to all devices if not intalled.
2: devices may have already intstalled application then it will show install say if one have intall and other don't then how to install in all devices.
I am not too versed in telephony. I know for blackberries you have to have a blackberry [enterprise] server to manage devices in this fashion. I think one client for android is called Good, but if you do a search for android enterprise management, you probably could find others.