Database Develop

[HOW TO] Stop the Amazon App Store from listing uninstalled apps under My Apps

Have you been sucked in by Amazon's free app of the day promotion, downloaded an app, played with it for a couple hours and then decided to uninstall it?
Have you noticed how that uninstalled app will forever appear under My Apps in the App Store?
I wanted Amazon to stop passively reminding me about my fleeting affair with a past free app every time I go to their app store to try out the next free app of the day. The app store doesn't offer any way of removing the uninstalled and I like my lists to be cleaned up.
The solution I found is not perfect, but it works for me. I tried a variety of ways and this is the only thing I could find that avoided having the uninstalled apps re-appear after the app store syncs itself with my account. It requires root, Root Explorer and SQLite Editor. There are probably other ways to do this, but this worked for me.
In Root Explorer, go to the data/data/com.amazon.venezia/databases folder and open the file called "locker". With SQLite Editor installed, Root Explorer will automatically open the file with write permissions. There will be a list of 8 tables:
Applications - this is the table you want to edit
Blacklist - seems to be a table containing apps that are removed from Amazon
BlacklistCursor - somehow related to Blacklist
ContentTokens - the tokens for the apps you've downloaded. Syncs with your Amazon account every time you open the App Store. Deleting records here does nothing, as far as I could tell.
Downloads - lists any downloaded but not yet installed apps. When you download an app from the Amazon App Store, it downloads to a folder on your SD Card located at sdcard/Android/data/com.amazon.venezia/cache. Amazon names the apk oddly. Deleting records here does nothing, as far as I could tell.
Wishlist - I assume this syncs with your Amazon wishlist for apps. I don't use it, so I don't know for sure.
android_metadata - One record that identifies the locale as en_US.
sqlite_sequence - identifies the next sequence number that can be used (right? I'm not that familiar with it)
Select Applications
The first field is the ASIN identifier that Amazon uses. You can search Amazon for this and find the app that way, just in case you wanted to know.
Now, it would be great if deleting the record you don't want worked, but Amazon will just resync and add the record again. Boo.
The more interesting fields are off to the right, so scroll down that way.
Right after the SoldBy field are true/false flags. I'm listing them here, because I'm not entirely sure what they all do and maybe someone can fill in the blanks. If you edit most of these fields, Amazon will just reset them when it syncs, too. We want IsHiddenFromActionableItems.
IsPurchased - 1 if purchased
IsNew - 1 if there is a new version (to download or already downloaded but not installed, it seems)
IsUpdateAvailable - 1 if there is an update available (installed, with update available)
IsFlagged - not sure
IsNewNotified - 1 if notified of the new version.
IsUpdateAvailableNotified - 1 if notified of an update available. Interestingly, for the apps I uninstall the IsNew flag is true and IsUpdateAvailable is false, but the IsNewNotified is false and IsUpdateAvailableNotified is true. Seems backwards.
IsFlaggedNotified - notified of flagging?
IsHiddenFromActionableItems - this is the one you want.
IsDownloaded - 1 if downloaded and the file is still in its download location.
IsInstalled - 1 if downloaded and installed.
Full step by step:
***You need root***
1. In Root Explorer, go to the data/data/com.amazon.venezia/databases folder and open the file called "locker".
2. Select Applications
3. Highlight the record you want to edit by tapping it
4. Long press on the value in IsHiddenFromActionableItems.
5. Select Edit Field
6. Change the value from 0 to 1 (or the opposite if you want it back in the list)
7. Click Save
8. Repeat 4 - 7 for any other records you want.
9. Hit back to return to the table list and back again to go back to the folder.
That's it. When you run the Amazon App Store again, the apps you've changed the IsHiddenFromActionableItems value to 1 for will no longer appear under New (and presumably Update Available). Unfortunately, the apps will still show up under the All menu, unless you filter by Installed apps only.
Sorry for the long post, but I thought maybe someone else with more background than me would be able to figure out some other workaround.
I'm not responsible if this somehow screws up your phone.

THANK YOU.
God I thought I'd be waiting forever for them to come up with a better way to manage your purchased apps.

I'd be willing to bet that we'll see a better way to manage apps in future releases of their app store, but I'm not willing to wait for that.

You. are a god! Thank you, thank you, thank you!

I was so happy when I saw this post. I tried the recommended resolution. However, when I hit the refresh button in the Amazon App Store, the "hidden" application came back.
Any ideas? I would love to have a solution.
Thanks,
Evan

Two new ideas that may help with this issue:
1) If you are *totally sure* you never want to see the app again..
Just delete the app.
Amazon's official instructions are a ways down this page:
Amazon Appstore for Android says:
(AMAZON OFFICIAL)
Amazon Appstore for Android customers can now permanently delete apps from their account. To use this feature, visit the Your Apps and Devices (http://www.amazon.com/gp/mas/your-account/myapps) section of the Amazon Appstore for Android and click "Actions."
To learn more about this feature, visit:
Appstore for Android FAQs - http://www.amazon.com/appstore/faq
Appstore for Android "Manage Apps" overview - http://www.amazon.com/help/managingapps
Click to expand...
Click to collapse
Note this is a somewhat drastic step - if you change your mind you will have to pay for the app all over again. Works great for free apps of course.
2) Amazon may have given us a way to run off *all* notifications with the latest Amazon App Store apk. See http://www.goodandevo.net/2012/03/turn-off-amazon-appstore-notifications-on-your-htc-evo.html

Does anyone know if there is a similar process that can now be used? It seems like the recent update to the appstore app broke this method.
Sent from my SGH-T999 using Tapatalk 2

In-app billing issue: “This version of the application is not configured for Billing

I am using in-app billing in my android application. After signing, I uploaded a draft APK to the market (no debuggable in manifest), also included the com.android.vending.BILLING permission and all the files.I first tried the reserved android.test.purchased product ID for testing. It worked fine.
Now I add a 'In-app Product' with a new price for managed product to my app in the Google Play Develoiper Console and set the product to active. The APK is still in draft. I created a test user and reset my device to make that test user the primary account on my test device. Also mentioned the product id in String SKU in my main activity.(previously it was android.test.purchase) Now, while trying to install the app, I am seeing this message:
"Error : This version of the application is not configured for Billing through Google Play. Check the help center for more information."
I have waited for more than 2 hours and tried again. Still same. I have also checked the versioncode in the main application and in the phone's installed application is same. I am using In-app Managed Product. Also, I would like to add a product id with yearly subscription if managed product works fine. Please suggest.

Are you using a signed apk? Because a debug apk won't work with InAppBilling.

You need to have exact the same version of application (both signed, both with the same version number). After this, everything should work perfectly.
Sent from my Nexus 4 using xda app-developers app

How to test an android auto app in the car?

Is there a hack or work around for rooted users to use unauthorized android auto apps that are not live in the Play store? For example I am working on one that will read my emails. I have some of it working in the emulator but I want to also try it out in my vehicle. I found this on another forum:
"Because of the UX/Safety concerns, you HAVE to be live on the Play Store - aka go through review (which is a new thing for Android) before testing in-car. However, this doesn't mean that you have to be public - you can publish to the Alpha or Beta channel, so only you and an optional controlled list of people can access it."

Is Samsung gear vr on note 4 dead? any custom rom with vr support?

Hello good people, i have note 4 n190c version and i tried vr and oculus app goes in infinitive loading or sometimes it crash. i tried 2 different stock roms and it is the same... i tried everyhing... facebook services are enabled i checked...
is there way to make it work? even offline? if someone have working gear vr it is posible to copy data and make some kind offline version?

The oculus app on the latest and last Gear vr for the Note 9 has issues you just described as well. I'm running stock firmware as well.

I found out i can only run samsung gallery app offline... i tried other apps to side load like i found apks online but it fails to start black screen usually, it need some signature i think and "Injector for GearVR" app on google play does not working, it fails on every apk to give signature...

I found i way to sideload all apks first you can use "SideloadVR" app google apk and download it, you have a lot of apps to try there, but first you need to make "OSIG" file specific for your device on oculus site you must login with any account (even give number for developer) and go to OSIG generator link google it and there with your ID (you can find in sideloadVR app your id) you then generate OSIG file and download it (be sure it is on phone download folder because sideloadVR only detects osig in that folder) and then you can easily use almost any app that is listed in sideloadVR... for specific app you want to use you can make almost any apk on computer ready for your device with "Add OSIG" google it have tutorial too i managed to make "samsung internet" apk signed with my osig file and app its working in phone normally and i can browse and watch youtube in vr now ...
One more thing... to prevent oculus "update avaiable first screen" when you connect your device to gear vr... use some app disabler i use "FreezeYou!" to disable "Gear VR System" service and no more first screen update... you just need to manually now launch vr app you want and then connect it to gear...

Google Play Console reports performLaunchActivity crashes from non-Google-Play app installations

Hey everyone!
I am getting a few strange crash reports for my application in the Google Play Console. The stacktrace is provided at the bottom of this post.
When I apply the filter "Installation Source = Google Play" in the console, I can see that every single crash of that kind is coming from a device that DID NOT install the application via Google Play.
However, I yesterday pushed a new version of the app to the Play Store (5% staged rollout), and I already got a crash report for this version only four hours after the update came available. Still, the Play Console states that this installation was not done using Google Play, which would indicate that somebody scraped the app bundle from the newest app version from Google Play pretty immediately, and manually installed it somewhere. I do not offer this newest version on any other app store yet.
My questions are as follows:
Do you have experiences with such random crash reports only from app installations that were not made with Google Play?
Is there a probable explanation for the crash with the newest version appearing only after four hours from a non-Google-Play installation?
Do you have any idea what could be causing this exact crash and stacktrace only on few devices and non-Google-Play installations?
Thanks a lot for your thoughts and expertise.
Exception java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:4166)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:4312)
at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:101)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2571)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8741)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1067)

I often get such crash reports that are hidden by the "Installed from = Google Play" filter from my own testing (installing the app from Android Studio on my test devices), but I suppose you have excluded that possibility?
I'm not sure if crashes in Google's automatic pre-launch report test appear as "installed from Google Play" (this is done in the first few minutes after you submit an update).
I don't recognise that exact stack trace.