Related
My nook Simple Touch is rooted used NookManager however I do not get network connectivity on third party apps.
The built in B&N apps and the browser work but the Amazon appstore and any sideloaded apps cannot connect to the internet.
I have even tried installing these apps to the system but that makes no difference.
Any help fixing this problem would be appreciated.
Thanks.
I've since installed the stock android 2.1 email application and that works fine. Confused as to why only these applications have a data connection but other third party ones don't.
tomb20 said:
I've since installed the stock android 2.1 email application and that works fine. Confused as to why only these applications have a data connection but other third party ones don't.
Click to expand...
Click to collapse
That seems kind of bizarre. If you don't have too much installed at this point I think maybe you should use NookManager to restore to factory and try the rooting process again after re-registering the device. Some subtle but vital piece of information is missing.
I have developed the same problem earlier this month. The Amazon Appstore only allows me to see apps I have previously installed. App searches on Amazon fail with a network connectivity problem.
I understand that postcode or phone number security questions have been recently introduced to the appstore login. Can anyone confirm that they can still access the appstore on a NookManager-rooted Nook?
I've just used NookManager's rescue option to successfully restore a year-old Nook image but the problem remains. The Opera Mobile browser opens but fails with an "Internal Service Failure" because the Amazon Appstore is inaccessible. ColorNotes does the same. Several other Amazon apps continue to work fine. Can I, perhaps, find a compatible browser and note app from Google Play and ignore Amazon altogether?
I guess I may have to do a factory rest, but I'll loose all my apps customization. Does a reset ensure the problem will cease?
I began to have trouble with the version of the Amazon App Store that comes with NookManager in short order after rooting some years back. Apps from the store (like Opera Mobile) were cranky and I would get random error messages about the App Store and its problems while reading or doing something else. I finally got rid of it and searched for app sources elsewhere.
I've attached a generic copy of Opera Mobile below. Works great for me although I found that altering the UAString gives better discrimination of sites that offer simpler mobile versions.
I suspect other connectivity issues are due to the Amazon App Store problems as you describe them.
nmyshkin said:
I've attached a generic copy of Opera Mobile below. Works great for me although I found that altering the UAString gives better discrimination of sites that offer simpler mobile versions.
I suspect other connectivity issues are due to the Amazon App Store problems as you describe them.
Click to expand...
Click to collapse
Your generic Opera Mobile works fine once I realized that, for installation, apps like this need to be moved to /system/app and run! I now realize that my early attempts to replace the Amazon version had failed for the same reason. Amazon appstore is no longer a problem, so I thank you.
As for the UAString, I generally prefer desktop view to mobile view, because it's more comprehensive. I'm still hunting for a generic ColorNotes but that matters little.
Joydeck said:
Your generic Opera Mobile works fine once I realized that, for installation, apps like this need to be moved to /system/app and run! I now realize that my early attempts to replace the Amazon version had failed for the same reason. Amazon appstore is no longer a problem, so I thank you.
Click to expand...
Click to collapse
Not sure why your Opera needs to be in the /system/app folder to run properly. Mine is in /data/app and works just fine, but the main thing is that you got it working for you!
Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.
caromcm said:
Using gbooks_10_16.apk I can search and get a book list, but nothing happens when I click a book. The basket/cart and pay apparatus is missing. Does anyone know how I can fix this?
I've also tried gb152.apk, but this doesn't seem to work at all.
I rooted with Nook Manager and then ran NTGAppsAttack (both v.050). NTGAppsAttack went fine until I clicked on Market only to find there were no apps at all anywhere. I left the Nook near my wifi, with wireless on, for hours and finally What's App appeared. I'd have preferred something simpler, but installed it anyway and then, having doubts, uninstalled via the Apps Drawer. I then upgraded the Market and installed SearchMarket, which just brings up the search keyboard. However, it finds apps, thpough only free ones, and downloads them. The Market still shows only What's App, though something else appeared briefly. There was no Books app in the Apps Drawer, so I downloaded the above versions.
Click to expand...
Click to collapse
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Does your version upsync? If so can you post a copy of the apk?
nmyshkin said:
So just to be sure, you are using the NST?
You will see very few/no apps via the Market app. Sometimes the category list will dredge up an app or two (free), but you need SearchMarket to find anything. I think you are right about only free apps. It may be that the old apps cannot negotiate the security transactions for paid apps.
And on that topic, the non-function of the store in Gbooks is your least problem. Have you noticed that it doesn't upsync?! I and others have done a pretty thorough investigation of the various versions that will run on the NST.. The version you mention has a functioning reader but can't upsync. I think up to 1.3.5 the reader still works (going from memory here...) but no upsync. The oldest version that will currently sync is maybe 1.5.2, but only if you can get the book to actually display, which is more miss than hit.
I played with Gbooks for a long time, even though I've never used it. I don't think it's doable without a serious rewrite of the source.
Click to expand...
Click to collapse
Yes, I'm using the NST. I haven't looked at syncing because as I understand it this is just a question of convenience when reading on multiple devices, which is not my aim. I just want to get books onto the Nook. Many thanks.
cjpicci said:
If you haven't already, you'll need to update the certificates on your nook as described in this thread: http://forum.xda-developers.com/showthread.php?p=65344931
Some older versions of Google Books will work, but maybe not all of the features. I have Books version 1.2.2 and can download purchased books from my library, although I purchased them on other devices. You can't purchase books on the old version of the Market or the books app since our nooks don't have Google Play Services, but you should be able to download books purchased on other devices (but same account.
You won't find many compatible apps in the Market at this point, and purchased apps have to be downloaded to other devices and then side loaded to the nook (assuming they're compatible). Some older working versions of apps can be found here on XDA.
Click to expand...
Click to collapse
Many thanks. This is very interesting, but I'll have to wrap a wet towel round my head before going back to the thread you suggest! Too late at night now.
nmyshkin said:
Does your version upsync? If so can you post a copy of the apk?
Click to expand...
Click to collapse
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.
cjpicci said:
It seems to upsync last read pages, roughly anyway since the formatting varies for different devices. Since this old version doesn't support anything like notes or highlights, I'm not sure what else it could sync.
What's the best/most practical way to share files on xda? While I've been lurking for quite some time, I only created an account fairly recently.
Click to expand...
Click to collapse
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
I've solved my problem now. I've been trying to download books from Google, first to my NookST and then to my laptop. But I'm running 32-bit Linux on my laptop and Google, like Adobe, seems determined to exclude Linux from the world of ebooks. So I downloaded to my Android phone and was quite surprised when the book also appeared on my Nook. I was offered the option of syncing, but decided not to be too ambitious in case it caused problems with the rather old Nook software.
It may have helped that I did all the NTGAppsAttack process on my Nook (I didn't want to go to the laptop because of the Linux problem). After I typed in my phone number I first tried to confirm on the phone and, when that didn't work, typed in the confirm number on my Nook. So perhaps the 2 devices finally got quite firmly linked.
I'll have a go at attaching the Google Books version I'm using, gbooks_10_16.apk.
I got it from another post on this forum. The reader works well but doesn't have a search facility.
nmyshkin said:
You can attach the apk file using the options below as you compose your reply or if you're not able to do that yet you can provide a link to any safe place where you can store a copy (Dropbox, etc.) so that people can access the file.
This is sort of amazing. I've never run into a version number like that and am really curious to see what it can do. Casual reading and syncing are all I would care about.
Click to expand...
Click to collapse
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.
cjpicci said:
Here's the md5 for the attached file generated by Android File Verifier:
bde6462cde86e0521d0b78270e11adb4
I think I probably got this apk when it was posted a long time ago, but I can't remember for sure. I just let Lookout scan it again and it came up "safe", for whatever that's worth.
Click to expand...
Click to collapse
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Glad it's working for you too! I can't remember for sure, but I think this version might've been recommended by someone else before. I'll have to look through my old bookmarks...
nmyshkin said:
Well done!! People have been searching for a version of GBooks that would sync for years! I can confirm that this works with free books from Google as well as user-uploaded books. I don't have any books purchased from Google so could not check that.
As with other versions, it helps to have a hardware key assigned to "menu" in order to access things like font size, etc., while reading (I use a long-press of the lower right button).
This is really a great discovery. I'll have to update the various other threads with a pointer to your post.
Click to expand...
Click to collapse
Thanks for all the info, guys. Second time you've steered me in the right direction, nmyshkin. NB Attaching the apk file was difficult because the process was incredibly slow (and not even a whirligig). Lots of notices about scripts that had stalled. I'm running Linux Mint 17 (Cinnamon) 32-bit; browser is Firefox.
I have the 2017 Shield.
I have used BBCIplayer in the US on many Android devices over the years. I usually install from apk or a British Google Play account, and then use a smart DNS service (smart DNS sends the proper signals through a VPN so the BBC server sees me as being in the UK, but the actual video is not sent through the VPN. Except for the limited purpose, the device has a US ip address.)
For every device except the Shield, once the Iplayer app is installed, it stays installed and visible.
The Shield has its own Nvidia made version of Iplayer (the regular version does not work with Google TV.) I installed this once from the Google Play store with a UK Google Play account. It worked fine, then disappeared after a while. I can now get it to work by using a copy of the Nvidia Iplayer apk that I downloaded from the internet - I click on the apk in file manager and then click on the "market" option rather than the "install" option. I am then given a screen where I can "enable" the Iplayer, and it then appears again as a usable app.
If I go into settings when the app is enabled it shows as a system app, rather than a downloaded app (as does the proprietary version of the Amazon video player.)
One of the reasons that I like Android is that it has less of the "big brothery" stuff than IOS (or a Roku, for that matter.) So it pisses me off that the device I paid for is actively frustrating my watching what I want to watch with an app which is on the machine. I'm not saying that Nvidia should be providing me with a VPN connection, but on the other hand it shouldn't be actively blocking me from what I want to do.
Short of hooking up to a VPN 24/7,any ideas as to how to stop this disabling of the app?
I want to try this.. Brit now in Germany. I installed express vpn on my shield but didn't look for iplayer yet.
I assumed I would need vpn set to UK all the time I wish to use BBC then disconnect vpn for normal use.
Sent from my Hauwai P9 EVA-L09 using Tapatalk
From Nvidia :
The BBC iPlayer app is only available inside the UK. If you are not located in that location or have recently moved out of the UK then the app will no longer be available from the main menu of SHIELD Android TV.
If you are located in the UK, please ensure that Location Services is enabled. To do so, navigate to the Settings menu and then into the Personal->Location menu and ensure it is enabled.
If you prefer not to use Location Services, please ensure that the device language selection is set to "English (United Kingdom) (GB)". To do so, navigate to the Settings menu and then into the Preferences->Language menu and select the language from the list.
----
so:
Disabled Location
Set English UK Language
Reboot
Enjoy
Tested
install kodi then install the iplayer plugin
afgok said:
install kodi then install the iplayer plugin
Click to expand...
Click to collapse
if you are outside the UK it still won't work without VPN - at least not from Germany
shaunydub said:
if you are outside the UK it still won't work without VPN - at least not from Germany
Click to expand...
Click to collapse
read the OP its pretty obvious he is using vpn hes in the USA what he wants is a work around for the app being disabled because its not licesensed for use outside the UK hence my post:good:
Hi, after battling with the same issue for some time on the 2015 shield, I've been able to work out a solution;
I've posted the solution up here;
https://forums.geforce.com/default/topic/1011733/shield-tv/how-to-fix-the-disappearing-bbc-iplayer-app-for-out-of-region-/
In-case it gets taken down for any reason, the solution is to extract out the APK of the iplayer system app (using ES file explorer on the shield TV), then pull the resulting APK into "APK Editor Pro" and then modify the app name and package name to create a new APK (making sure the package name doesn't have iplayer in it) and then sideload it onto the shield TV.
This way when the shield is booted, only the inbuilt iplayer app is disabled, but not the modified cloned app.
I expect this same process to work with many other inbuilt apps on the shield TV that might be disabling out of region.
Hope this helps someone!
Hi Watsonash, I scanned the apk you've kindly shared for the disappearing iplayer & it's infected with malware; I checked it with both VirusTotal and NVISO APKScan...
chainfire3356 said:
Hi Watsonash, I scanned the apk you've kindly shared for the disappearing iplayer & it's infected with malware; I checked it with both VirusTotal and NVISO APKScan...
Click to expand...
Click to collapse
hi, those products must be reporting false positives. As said I simply used "APK Editor Pro" to change the information, so unless this in injecting malware (which I'd say is most definitely not the case). I described the process so there is nothing stopping you from taking the exact same approach yourself and generating the modified apk yourself. I just installed Virustotal and it said the apk simply wasn't in its database (which is correct as APK Editor Pro has to resign the app as part of the packaging process).
Hi Watsonash, I aplogize, I should have clarified in my original comment that I didn't think you were purposely putting that apk out there with malware; I was just trying to be brief in my comment, which isn't something that comes naturally, as you'll see... My reasons for posting were to let you know that a scan dectected malware so you could look into why that was & fix it - that being said, every day is a new school day for me, because I wasn't aware of the false positive thing until you mentioned it. Now I understand that it's not something that you can"fix"and it isn't likely infected. I don't know how to modify anything - the only knowledge I have is knowing where to look to find clever people like you who do the work to fix annoying issues like the iplayer disappearing. I am eternally grateful for people like you who figure these things out for people like me & to have learned something new about the false positive issue; I was stupidly thinking that since two different websites showed positives that something was there, but now that I've read into a bit, I've clued in that the majority of the actual antivirus programs on both sites marked it clear. I see now that there are many variables taken into account when these programs come up with a result that doesn't look good.
Again, I apologize; this is why I usually just read & then research & never post comments - I should stick to doing that! Thank you for figuring out this fix; it's very much appreciated!
ronwi2 said:
I have the 2017 Shield.
I have used BBC Iplayer in the US on many Android devices over the years. I usually install from apk or a British Google Play account, and then use a smart DNS service (smart DNS sends the proper signals through a VPN so the BBC server sees me as being in the UK, but the actual video is not sent through the VPN. Except for the limited purpose, the device has a US ip address.)
For every device except the Shield, once the Iplayer app is installed, it stays installed and visible.
The Shield has its own Nvidia made version of Iplayer (the regular version does not work with Google TV.) I installed this once from the Google Play store with a UK Google Play account. It worked fine, then disappeared after a while. I can now get it to work by using a copy of the Nvidia Iplayer apk that I downloaded from the internet - I click on the apk in file manager and then click on the "market" option rather than the "install" option. I am then given a screen where I can "enable" the Iplayer, and it then appears again as a usable app.
If I go into settings when the app is enabled it shows as a system app, rather than a downloaded app (as does the proprietary version of the Amazon video player.)
One of the reasons that I like Android is that it has less of the "big brothery" stuff than IOS (or a Roku, for that matter.) So it pisses me off that the device I paid for is actively frustrating my watching what I want to watch with an app which is on the machine. I'm not saying that Nvidia should be providing me with a VPN connection, but on the other hand it shouldn't be actively blocking me from what I want to do.
Short of hooking up to a VPN 24/7,any ideas as to how to stop this disabling of the app?
Click to expand...
Click to collapse
Sorry for bringing up an old topic. Anyone use smart dns for BBC iPlayer on smart TV?
I want to stream it to my TV without VPN. Also how to install BBC iPlayer application to smart TV if iam outside UK now?
I ran across this "solution" while investigating ways to avoid installing GApps on low-RAM tablets. It is not a perfect solution but if you want to be able to search, browse, etc., and download/install PlayStore apps right on your device, this may serve that purpose.
The app is called the Yalp Store and is available on F-Droid: https://f-droid.org/packages/com.github.yeriomin.yalpstore/
It runs just fine on the NST/G. Options are accessed via the menu "button". As default configured, it uses a generic shared login to access the PlayStore. You could substitute your own credentials, but I would advise against this as using this app would probably make the big G very angry. Search works fine, apps that are not compatible are listed as such and you can set the app to instantly download/install, just like the real thing. The app keeps track of your on-board apps, and can even be set to check for updates (probably unwise, as updates are likely to break functionality for our old devices).
Does this mean I don't need GApps?
Maybe, but probably not. One of the other things I discovered while pursuing this issue is that an increasing number of PlayStore apps which have nothing to do with Google sync or logins, incorporate a Google Framework Services API. So you may be able to download and install them but they will either refuse to run or else whine constantly about needing said Services to be installed. While GApps on the NST/G is not good for much these days except maybe Google Books sync, its hidden system files--which include the Services--may be needed to run PlayStore apps (like even the NPR app--go figure).
There are a few Xposed modules I tried that appear to be able to circumvent this issue (though not for apps requiring Google sync), but you're not going to get Xposed on the NST/G!
Anyway, there are a lot of other places to get apps (like the F-Droid store itself) but even if you get a "PlayStore" app from one of these sources, it may refuse to run if you don't have the GApps package installed. The Yalp Store app indicates which apps rely on GFS.
Edit: oh, and quickest way to exit the app is Settings > More > Log Out
Edit-Edit: no need for GApps except for Google Books. See https://forum.xda-developers.com/nook-touch/general/gapps-install-tested-confirmed-t3782459
the yalp apk installed but it isn't opening ...
aiamuzz said:
the yalp apk installed but it isn't opening ...
Click to expand...
Click to collapse
Wow...something majorly funky going on there with the packages at F-Doid and the GitHub. Version 0.32 is as you describe. Versions 0.31-0.30 install with a lot of Chinese characters in the title bar and then do not run. Version 0.29 from the GitHub gives a package parsing error like it's for the wrong Android version.
Version 0.28 from the GitHub is the newest that functions for me (although the anonymous login is broken). I've attached a copy below and I've made an issue report to the developer via the GitHub.
Edit: here is the response I received to my report of the issue to the developer: "Apparently, new build-tools (specifically aapt2) generate apks which are unusable on old androids.". So....it's not clear whether this will be addressed or not. One of the intents of the simplicity of the Yalp Store was to keep it available to Android systems as old as 2.0. Version 0.28 functions fine except for the anonymous login. If you use your own Google login you should be good, although you might want to open a separate account just for that purpose--to be safe.
update
Just a heads-up on the Yalp Store. The issues with installation, etc., seem to have been resolved with version 0.33 (available via the developer GitHub as of this writing, but not yet on F-Droid).
I had an issue or two at first with search but after exiting and reopening the app everything seemed to work fine. Categories are a little slow, but they do work.
A friend of mine has found that on Play Store there are some apps that aren't "compatible" with the S10+. I too myself have checked and yes, it appears like it isn't compatible.
Can anyone else on other Regions check if this apps appear too like that? I am from Puerto Rico
Apps:
1. Adobe Premier Clip
2. Slice Package Tracker
In Poland (central Europe):
- APClip - same as yours
- Slice - doesn't even show up in results
Explanation
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Yeah, i've had it with a few runtastic apps. Had to download them manually and install the apk.
piotrkruczek said:
In Poland (central Europe):
- APClip - same as yours
- Slice - doesn't even show up in results
Click to expand...
Click to collapse
Thanks man, I aprecciate your help.
AHE_XDA said:
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Click to expand...
Click to collapse
Hey, gotcha, I'll be giving that thread a look, thanks for the explanation I really apreciate your patience. I'll try manually installing the APK and wait till updates for fix the compatibility issuses on the app.
Valinorian said:
Yeah, i've had it with a few runtastic apps. Had to download them manually and install the apk.
Click to expand...
Click to collapse
I'll be giving that a shot and test if they install
atrix_noob said:
Hey, gotcha, I'll be giving that thread a look, thanks for the explanation I really apreciate your patience. I'll try manually installing the APK and wait till updates for fix the compatibility issuses on the app.
Click to expand...
Click to collapse
My pleasure. Anytime.
atrix_noob said:
I'll be giving that a shot and test if they install
Click to expand...
Click to collapse
- runtastic six pack
- Runtastic leg trainer
- Runtastic butt trainer.
They dont show up in appstore but work fine when you install it through apk,
Valinorian said:
- runtastic six pack
- Runtastic leg trainer
- Runtastic butt trainer.
They dont show up in appstore but work fine when you install it through apk,
Click to expand...
Click to collapse
Thanks for the headsup there.
I installed the apps of my original post thru APK amd all work flawlessly
AHE_XDA said:
@atrix_noob
If it's any consolation, the applications install just fine if you download the APK directly (e.g., APKPure).
The best thing to do is to reach to the Developers and inquire when your device will be 'officially' supported. They hold the key.
I'll explain why this happens:
When an application is built, a unique file called a 'Manifest' is created alongside it.
The 'Manifest' lists what the application CAN and CANNOT do when used with a specific device.
When the application is searched via Google Play and the result loaded, the 'Manifest' determines whether or not the device IS or ISN'T compatible.
If the Application is, it will install.
And if it isn't, it won't.
Given the popular of Samsung as a whole, you'll likely see availability soon but given the amount of devices released every month, one can only imagine how many updates a Developer must have to prepare.
If you'd like to learn more, take a look at this:
https://developer.android.com/guide/practices/compatibility
Click to expand...
Click to collapse
The thing is that not each device is manually included in the manifest. New devices are released all the time and unless you exclude something specifically, apps are always made available for distribution. This happens with one of the apps my company runs as well. Whenever a new Galaxy device comes out, its always incompatible with the app and its not because of anything we have done with it.
@Blaaargh
'The thing is that not each device is manually included in the manifest.'
No one said every device is included in the manifest. In fact no devices are listed in the manifest; only declarations.
'New devices are released all the time and unless you exclude something specifically, apps are always made available for distribution. Whenever a new Galaxy device comes out, its always incompatible with the app and its not because of anything we have done with it.'
OP wanted to know why APK X and Y weren't working. I provided him with a generalized explanation of why it MAY happen. It could very well be a Samsung issue but without breaking down the APKs in question, there's no way to be certain.