[Q] Users Not Able To Install App From Market - Android Q&A, Help & Troubleshooting

I have an application on the market, and with an update released the other day a lot of users are complaining that it no longer works on their phones. None of the permissions or requirements for the application changed with the release, and I was wondering if anyone had any insight as to what may be occurring.
It seems to be ICS phones that are having this issue. There where a few reports from users when the application was first released, and I could never figure out what went wrong.

Related

[Q] com.android.fixed.update

Hey all,
I'm the proud owner of a Samsung Nexus S (sadly the i9020a model, though). I was forced against my will at gun point by someone named Jealousy to install ICS (4.0.4) on my i9020a when it was released for all other Nexus S devices except for the US AT&T version of the phone.
Anyway, love the ICS and absolutely love the ROM I'm using (Brainmaster's stock ICS, w/ Supercharger V6 and a number of other goodies). But I was a bit confused today when I opened my phone and noticed a recently downloaded APK called "update.apk". Looking at it's info, it's name is "com.android.fixed.update" with no author, developer, and minimum version of 0. It weighs roughly 40kb and is not associated with the market, so I'm going to have to disable my "Market-only" settings in order to install it, otherwise it was about to install itself.
I was wonder what it might be. With no other information, I'm a bit hesitant to install it. The only permissions it asks for is Network Access and Start on Boot.
I thought just maybe it was an OTA from a developer (maybe even Brainmaster) but I wasn't exactly sure what kind of access or ability non-service providers had to OTA functionality and what not. (I suppose, if it can probably be modified with some effort, seeing as the source is available...)
Anyway, hoping to hear your thoughts on it. Google showed ONE result for "com.android.fixed.update" and that's it. Thanks for your input in advance!
We also got the same file on our Moto Xoom, I believe its a virus so do not install it. The file was downloaded at biandroid (dot) info which is definitely not associated with android.com
http://anonhq.com/notcompatible-back-market/
that is the explanation
Back in 2012 malware called Not Compatible was haunting android devices. Now more powerful than ever the latest version of NotCompatible.C has its own self protected encryption. Thus making this program difficult to find and delete.
Lookout Inc, a mobile security firm says that this version of the malware is a threat on a massive scale. Once in it has the tendency to control and hack data. It is an advance form of malware that can be seen on a PC a botnet so powerful that it has a server design architecture, P2P communications and as previously said encryption capabilities.
The programming of the malware is one of the hardest to kill malware that we have observed. Once the malware is installed it does not appear on the android operating system as it keeps itself in the background. It only works when the device is unlocked by the user or if it is restarted.
view
Source: Imgur
The only way you can find out is through Manage Applications>Settings. This will show you that an application by the long name of (com.andriod.fixed.update) is running. All you need to do is simply uninstall it.

Slacker Radio caching problems 4.2 Jellybean

So... want to cache your radio stations on that shiny new Nexus 4? No workie.
If I want to know how to fix something, I come to XDA. I rarely contact actual product support for... anything. But I want an ETA for a fix to this. So I just chatted up Frank S at Slacker and got.. "answers". Transcript follows:
Frank S.: Hi, my name is Frank S.. How may I help you?
ME: When will the Android app be updated for JB 4.2 compatibility? Caching is broken on Nexus 4
Frank S.: This is a known issue with Android 4.2. We expect this to be fixed in a future version of the Android OS. You can avoid this issue by downgrading to the previous version of Android until a fix is released by Google. We apologize for any inconvenience this may cause.
ME: A downgrade is not possible on this device - ships with 4.2. Can you elaborate on the "Android" issue?
Frank S.: Caching does not work on devices running Android 4.2 due to bugs and changes included in that version of Android. This issue does not appear in previous versions of Android, so we are awaiting a fix from Google in the next version.
ME: Just so I'm clear on this... Slacker will absolutely not be updating the app? Have you any information that indicates Google is going to retrofit their new OS to work with your app?
Frank S.: Google has already announced that there are several major bugs included with Android 4.2, and expect to have these fixed in a future update. Since the issue only appears with this version of the OS and since nothing with the Slacker app has changed as a result of updating to 4.2, we expect to see what changes Google plans before attempting to update the app to work around OS bugs.
ME: Well then... Caching is the sole reason I use Slacker over other services. I will attempt to find a workaround today, but if I fail I will need to cancel the remainder of my subscription
Frank S.: I do apologize for the inconvenience. Since your device is unable to downgrade to 4.1, you should be able to access cached content from your previous device until an update is available.
ME: Previous device? Not in the habit of keeping old devices
Frank S.: THat would be the only solutionwe are able to offer at this time.
ME: Are you saying a pro-rated refund is off the table here?
Frank S.: Slacker does not offer any refunds on purchased subscriptions.
ME: ....nor app updates for compatibility with new platforms? What you're saying is outrageous
Frank S.: Slacker never guarantees that all subscriptions services will be compatible with all phones and all versions of operating systems. While we will always try to make sure our app is available for use for most phones and that as many subscription features are available, some updates may take time to receive, especially on devices that are updated first.
ME: You just got done saying that Slacker would not be updating the app for 4.2 - Do I have that wrong?
Frank S.: We are waiting for Google to release what changes they are making to 4.2 before attempting to update the app to work around OS bugs.
Frank S.: Once we have that information, we will act accordingly.
ME: What "bugs" would you be referring to? Updates to OS framework and functions perhaps? Either Slacker has plans to update for 4.2 compatibility or it doesn't. How does the "OS bug" argument apply here? What is the bug??
Frank S.: I don't have any specific information on the exact issue, only that it is a known issue with Slacker on Android 4.2 and we are currently investigating and awaiting more information from Google before further action is taken
Frank S.: At some point in the future, I would expect the Slacker app to be compatible with Android 4.2, but I don't have any information on when that would be.
ME: Okay.. how about a simple "We're working on the issue...", instead of "Google is the devil and they broke our app!" Thanks
I hope this was a rogue agent... Is "Blame Google!" actually Slacker's stance on this?
I'm glad I'm not the only one having an issue with this. It's frustrating that it goes through the process of "caching stations", for it to not work at all, telling me that I have to stream it. I'll bet it's having issues with the /sdcard/0 change and can't properly locate the files or something stupid. Either way, the runaround response they gave you was unnecessary.
BTW I should mention I'm using a galaxy nexus, running stock/rooted 4.2
byrdman164 said:
I'm glad I'm not the only one having an issue with this. It's frustrating that it goes through the process of "caching stations", for it to not work at all, telling me that I have to stream it. I'll bet it's having issues with the /sdcard/0 change and can't properly locate the files or something stupid. Either way, the runaround response they gave you was unnecessary.
BTW I should mention I'm using a galaxy nexus, running stock/rooted 4.2
Click to expand...
Click to collapse
That occurred to me too. If I have time tomorrow I'll try emulating the ExtSdcard mnt point (or whatever it was in 4.1 lol)
Tried a few different mount points with ICS Binder, no change in caching behavior for me. Tried posting on Slacker forums but they are censoring to the point that the broken caching on 4.2 almost doesn't exist over there. Hell - it barely exists over here. I'm getting lonely
I was all set to do a paid subscription too... Between the cache not working and the app behaving like crap with network changes, I guess I won't.
The app just got an update that fixes cached stations!
Unbelievable... they told me just yesterday that they didn't intend to address the issue at all. Because of that I subscribed to Rhapsody today.
Did I tell you how I feel about my support experience with Slacker... :banghead:
Sent from my Nexus 4 using xda app-developers app
Has anyone tried it yet? Does it whitely fix it? I'm going to try it when I get home on wifi
Sent from my Galaxy Nexus using Tapatalk 2
I can confirm that it does work. I played a cached station and it worked fine. The network activity indicators didn't show activity from streaming.

Restricted user app selection after Oreo not working

I use restricted user profiles on the S3 to only allow my children to only access a restricted list of apps I download from the Play Store. It seems that any NEW apps that I download from the play store after the Oreo update do not show up in the list of apps (Settings > Cloud and accounts > Users, select a restricted user).
I did a factory reset this morning, and still no luck. Now only stock apps show up.
I chatted with Samsung this morning, and they want me to take it to the local walk-in Samsung clinic to have it looked at. This seems like a software issue - not a hardware issue. Perhaps Oreo changes the way this feature works - and it is an android issue not a Samsung one?
As a troubleshooting step, would any of you be willing to setup a restricted account on your S3, download a few play store apps and see if they show up to be able to enabled for the restricted account? No matter what I do, only the stock apps show up. It would be helpful to know if others have the problem as well.
I'm having the same problem, we're you able to find a solution? Only happened after the oreo update.
Nigle said:
I'm having the same problem, we're you able to find a solution? Only happened after the oreo update.
Click to expand...
Click to collapse
Thank you for reporting your experience with this to this thread. No solution as of yet. Now that I know someone else is having the same issue, I will try Samsung support again and let them know it is a problem with Oreo for all users - not just my tablet. Unfortunately, I'm guessing the best we can hope for is that it gets Samsung's attention to be included in the next update - which will likely be some time from now.
Update: I installed the Smart Tutor app from the Play Store which allowed a Samsung Support rep to see the issue. They agreed that it was not working as it should and opened issue ticket #2194272620. Hopefully this ticket will allow the issue to be noticed and fixed in a future update.
bthurber said:
Thank you for reporting your experience with this to this thread. No solution as of yet. Now that I know someone else is having the same issue, I will try Samsung support again and let them know it is a problem with Oreo for all users - not just my tablet. Unfortunately, I'm guessing the best we can hope for is that it gets Samsung's attention to be included in the next update - which will likely be some time from now.
Update: I installed the Smart Tutor app from the Play Store which allowed a Samsung Support rep to see the issue. They agreed that it was not working as it should and opened issue ticket #2194272620. Hopefully this ticket will allow the issue to be noticed and fixed in a future update.
Click to expand...
Click to collapse
Thanks for the quick follow up! It's good that they finally acknowledged the issue at least.
Stumbled upon pretty much the same issue when I wanted to create a new restricted user account.
Before the update to Oreo; I had already a restricted account. That one has still the possibility to change the 'run' permission for apps. Not sure if it also works for new installed - I haven't tested that.
de_perre said:
I had already a restricted account. That one has still the possibility to change the 'run' permission for apps. Not sure if it also works for new installed - I haven't tested that.
Click to expand...
Click to collapse
My experience was that new installed apps would not show up for the existing restricted accounts.
It will be interesting to see if the Tab S4 has this same problem
Hi all together!
Same problem here! This is a mandatory feature for me to share the tablet with my kids. Seems that the oreo update ****ed it up.
The bored Samsung support guy asked me to do a factory reset, and now, after 3 hours of configuration it still doesn't work.
Grrr !!! before the factory reset I had at least these apps working in the restricted profile I configured under android 7.
And ideas? Any update from Samsung ticket you opened?
Regards from cologne, Germany
Sui
No new ideas. I am USA but I noticed the korea build was a bit newer so I tried installing that. That didn't help but was interesting.
My understanding from the Samsung rep was that others could call and give the ticket number to get status and add a
"Me too" to it and that may help it get more attention
Having same issue on my Galaxy Tab S3 after Android 8.0.0 install. Did factor reset and still not working. Contacted Samsung using a Samsung Community of "Restricted Profile - New Apps not listed in App and Content Access Menu" and after Samsung suggesting a factory reset, which did not fix problem, they private messaged me to contact Google. I am struggling as there appears to be no way to contact Google for a response other than the mounds of help websites that do not acknowledge or provide fixes. As a parent who is trying to restrict my children's use of tablet to choke off internet and inappropriate items, I am at a loss for now and my kids are whining that they cannot play on any new apps without bugging me to let them use my signon; totally unacceptable.,
Same problem (Samsung Galaxy Tab A6, android oreo 8.1). Completely ruins my restricted account setup for the kids. They're not happy and neither am I!
Solution
"Same problem (Samsung Galaxy Tab A6, android oreo 8.1). Completely ruins my restricted account setup for the kids. They're not happy and neither am I!"
Give restricted account permission to use chrome and search for the app you require as an apk. Then install from that.
99% of apps can be found as an apk so it works as a solution until android gets there acts together and sorts it out.
Same here. I just upgraded my Galaxy Tab 10 A6 T580 to Oreo 8.1.
My kids keep asking when they can get the tablet back...
Same problem here after the Oreo update.
Old restricted accounts still have their previously enabled apps, new restricted accounts only get standard Google/Samsung apps.
New apps installed under Oreo from the Play Store do not show up in the app restrictions list.
Somehow, as restricted users also cannot use the Play Store directly, how are they supposed to get any app other than the standard ones?
This is a bug, not a feature.
If it should prevail, I will dump my Android devices and get Apple iOS phones/tablets for the rest of the family.
Same problem here too. I installed few apps after i upgraded my Galaxy Tab 10 A6 T580 to Oreo 8.1. They are not shown..so even resetted the device. Now all is gone on the redtricted users...
My kids also want to get the tablet back...
If anyone has a solution...pls let me know how!
I talked to the Samsung Germany support on Thursday. They know about and acknowledged the problem, however, there is no cure. The technician I talked to hypothesized about the upcoming Android P (roll-out to Samsung devices is planned for 2019) may fix the issue.
The point is, restricted users may also not use the Play Store to install new apps, so in effect, there is ABSOLUTELY NO WAY to get any apps except the standard stock apps into a restricted user's account. That does not make any sense at all.
Unless this is really intended (making the restricted account option useless), this looks like a gross oversight in QA on behalf of Samsung.
I'll see how this develops. My immediate solution is to use MobileFence to restrict my kids' accounts on mobiles and tablets (working with normal user accounts).
--j.
Scott_B1 said:
Having same issue on my Galaxy Tab S3 after Android 8.0.0 install. Did factor reset and still not working. Contacted Samsung using a Samsung Community of "Restricted Profile - New Apps not listed in App and Content Access Menu" and after Samsung suggesting a factory reset, which did not fix problem, they private messaged me to contact Google. I am struggling as there appears to be no way to contact Google for a response other than the mounds of help websites that do not acknowledge or provide fixes. As a parent who is trying to restrict my children's use of tablet to choke off internet and inappropriate items, I am at a loss for now and my kids are whining that they cannot play on any new apps without bugging me to let them use my signon; totally unacceptable.,
Click to expand...
Click to collapse
Same problem, Galaxy Tab A 10.5 (2018), Android 8.1.0 - massively frustrating!
Same problem here - is there any point in contacting Samsung to log this?
Any work around anyone can recommend? We use the tablets for a lot of lessons and set reading and the kids can't even access Kindle on it any more. I saw someone recommended Mobile Fence already, thanks.
It's causing major family tension because of how it's affecting Minecraft too. Huge frustrations.
Same here. I wonder why restricted user feature persists, it is useless now. A can assign only application installed before upgrade to Android 7.x, now on 8.1 and still no new app for assigning to restricted user.
Samsung Tab A6 (2016).
Same problem, subscribing to thread just to be able to see if there is any resolution.

Rant about android 8/9

I have moaned in the past about the rapid pace of Android OS development, and the usual implication of buying a new phone is you forced to upgrade android, but going from Android 6 to 8, looks like its going to be brutal for me, and hard decisions to be made.
On my old S7 phone running Android6, I have the following working reasonably well.
Xposed
Instagram made useable by xposed (app without it is horrible)
Same with snapchat
Various privacy enhancements thanks to xposed
Anag app works perfectly.
Apps mostly honour auto sync setting
However titanium backup only barely functions, it seems it only works properly with supersu which is considered obsolete these days, this app last worked properly on my s5.
Using android 9, there is no xposed at all, to me having no xposed on android is like going out in the street naked.
Using android 8, xposed is in beta, initially it seemed stable, but I have noticed the contacts app goes crazy and unstable as well as phone app after 2-3 days uptime if xposed is enabled on phone.
Some xposed modules have become abandonware and no longer work on Android 8
Some apps including Anag which has no alternative app have become abandonware and dont work properly or at all on Android 8.
Auto sync is disabled on the phone yet I keep getting notifications from apps, related to background sync activity they are doing, e.g. dominoes apps downloads an advert, and sends me a notification asking me if I am hungry to order some pizzas (never ever seen it do this on android 6), various other apps having similar type behaviours, just 10 mins ago backgrounds hd sent me a notification to inform me its downloaded new backgrounds, how has it done this when I havent gave it permission to background sync? ,either the auto sync setting is broken or there is some new feature in newer android that allows apps to spam you. I suspect its the latter, as I think even with auto sync enabled on android 6 I wasnt getting all this app spam.
The problem is this, new phone hardware is nice, my newest phone is lightning fast compared to my s7. But ultimately its the software that makes the phone. Sadly there is no Android 6 for the oneplus6, I dont expect much sympathy on the XDA community as the majority of people here seem happy to always jump on the latest builds of android without a second thought, often beta/alpha builds to boot. But felt like I needed to rant.
I dont know what I am going to do moving forward, I will probably test OOS 8.x, just to rule out custom rom issues, and if issues persist I can forsee myself selling the phone and buying an older model that still is faster (but wont be as fast) just so I can run android 6. I wonder if anyone else has ever deliberately avoided latest model phones to keep old android.
Its becoming evident to me, that many developers cannot keep up with the pace of android updates, so we get this happening, apps becoming abandonware, and users like myself either have to find replacement apps or accept to lose features on their phone. I wonder if IOS has these issues or if that has full backward compatibility that keeps old apps working. I wouldnt be unhappy if e.g. new android major releases were every 2 years with 5 years security support for each release as well. But a sane software support policy goes against google's policies.
Its kind of interesting as we have many news articles about the problem of android fragmentation as such, and often these articles blame everyone except google, they blame end users, they blame phone manufacturers, and they blame mobile carriers, but they never consider the problem might be google simply releasing new versions of android too rapidly.

Question App crashing--developer blaming numerous Pixel users

Midea Air - Apps on Google Play
Midea Air allows you to control your AC from wherever you are
play.google.com
Would some of you Pixel 6 users mind installing and seeing if it crashes on you, please?
Because it's not 100% of users encountering the issue, they blame some Pixel users due to a "classnotfound" error within their application.
Since we've all seen people copy & paste code and other silly things they shouldn't do, which cause crashes, I asked them if they used a root checker:
Yes, and we also have our test team both in China and the U.S. using a couple of problematic models which are reported by users too. But nothing more is found and none of the trails show the problem. And according to the feedback situation, not all users using these phone models are having issues, so we assume it is related to a specific user environment.
Click to expand...
Click to collapse
But they didn't expand on it beyond "yes", unfortunately.
Spoiler: my thoughts & minutia
Other than Play Store app updates and automatic Google-pushed Play/Services updates, all I've done in the past 10-14 days is update Lsposed. I've disabled and rebooted without it, and the issue remains. I've also used a stock boot.img and the app still crashes, which makes me think it's detecting an unlocked bootloader or some similar and unnecessary check(s), and moving forward with its checks which then fails due to Google no longer supporting whatever methods the app is using, and they don't know how to figure it out since it's probably copied & pasted code from many months ago and they're unwilling to suspect that old code is the cause, even though Google normally rolls out subtle security changes like this, very gradually.
Is it really just me and 5-8 other users in the entire world with this issue, or does it crash on some of you as well? I can't imagine it being such bad code that it's only rooted/unlocked bootloaders with the issue. It must be non-rooted and stock Pixel users with the issue as well, and those devices just haven't been pushed the Play Store/Services update yet.
I'd like to know if I'm just getting older and dumber or not, and if I'm truly the cause for the crash, haha. I'm open to being entirely to blame for this, but I don't want to wipe my phone and relock the bootloader for testing quite yet. Thanks for testing and voting in the poll!
Huh? If you've got a "class not found" it seems like it would be pretty easy to determine where the problem lies.
Is it some esoteric Kotlin thing or java.util.boring?
Renate said:
Huh? If you've got a "class not found" it seems like it would be pretty easy to determine where the problem lies.
Is it some esoteric Kotlin thing or java.util.boring?
Click to expand...
Click to collapse
Yeah, I figured something like that should be pretty simple, unless they have zero failures in their own testing. But...is there some new background auto-report for crashes on Android, which ties in to the email address, that I'm unaware of?
I never said anything to them other than email them my phone model, Android build, and posted a google app review (under the same name & email address) with no information other than it crashing. And they repllied, via email, with this:
Due to the uniqueness of this bug, no more code trace can be reported as you received only a line of error indicating "classnotfound". normally there will be at least a few lines more which helps with debugging.
Click to expand...
Click to collapse
Well, there could easily be conditional code for almost anything.
If you can repeatedly bomb this, why don't you get a logcat and see where the problem is?
Code:
$ logcat
The logcat should say what the class is and where it's called from.
Heck, it could even be in JNI code.
I just tested it, opened but due I am not registered and have no compatible AC, I didn't processed further. My cast vote is given, but not sure whether this is helpful, due not sure whether the app crashes when you open it or after login.
Pixel 6, A13, rooted and unlocked bootloader.
Cheers
Tom
oops!
So.... they have test teams in... China? You want to give CHINA control of your air conditioner? And access to data on your phone?
I'm same with tom1807
Yesterday Instagram app started crashing after I got a video message from a friend, I had to clear cache and reinstall it and reboot the phone, its now working fine, it was weird though

Categories

Resources