Related
Hi Everyone,
I am seeing an issue on my HTC Sensation when attempting to update Apps that I paid for in the Google Play Store. The exact message that I see when attempting to update these Apps is "Package File is Invalid".
Here is a bit of background to this issue -
1). My HTC Sensation has a custom ROM (Elegancia) installed, and I have now re-installed it (which is when these issues started).
2). I can install a ROM and update Apps through the Play Store just fine at the start
3). I install Titanium Backup and perform a restore (I have tried restoring only data & apps + data [starting from scratch and wiping the phone then installing the ROM again to test both scenarios])
4). Apps return to the state that they were in before I flashed the new ROM
*** However now whenever I attempt to update Apps I get the infamous "Package File Invalid" message ***
I have noticed when opening Titanium Backup that it alerts me that the "Android ID" has changed, it also gives two options, 1). Leave the new ID, 2). Restore the old ID
5). I tested the updating of Apps both whilst keeping the new "Android ID", and whilst restoring the old "Android ID", the ID (whilst I am sure is important) doesn't seem to affect whether or not Apps will update.
This issue only appears to be affecting Apps that I have purchased, and the Play Store still recognizes that I have purchased the Apps.
I believe that this issue is related to Titanium Backup. If anybody knows how to get around this it will be greatly appreciated. I have Googled the issue, and read up on it - none of the answers that I found worked, so I figured that another fresh ROM install should fix the problem, however it didn't!
Any help will be greatly appreciated.
Kind Regards,
Davo
Google Play Store has changed on me, and this may be a contributing factor!
Hi Everyone,
The plot thickens - I just logged into the Google Play Store and attempted to install a new App (through a Browser on my Desktop Computer). I was surprised to see the following screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice that the SEND TO box has a greyed out entry - "Telstra HTC Sensation".
I have an interesting predicament, even though I am a Vodafone (AU) customer, the reception at my residence is so poor that I keep an "emergency" Telstra (AU) SIM in case of the need to make an emergency call (I live in Suburbia so why I can't get reception through Vodafone will remain a mystery!).
When I installed the Elegancia ROM I did so with the Vodafone SIM inserted. However when it came to downloading Apps I used the Vodafone SIM. I think that the Google Play Store is now in a "state of limbo" - as originally my phone had Vodafone HTC Sensation and now it has Telstra HTC Sensation.
If I try to install an App onto my phone that has already been there before I see the following:
I can click on Install but nothing downloads to my phone regardless of the SIM that I have inserted - I have tried both.
I now feel like the Google Play Store & Titanium Backup are having a "game of tug of war", and my unfortunate phone is stuck in the middle!
If anybody knows how to reset the "SEND TO" parameter in the Google Play Store please let me know.
Kind Regards,
Davo
My fix -
Hi Everyone,
As attempts to fix this - using methods that I found elsewhere on the web - came to no avail...
My fix -
1). Formatted SD Card (after backing up data to PC)
2). Installed newest firmware 3.33 RUU (PG58IMG.zip)
3). Using 4EXT
a). Formatted Partitions (except SD Card)
b). Ran DragunKorr-WIPE-ALL.zip
c). Wiped cache + dalvik
d). Installed Elegancia ROM (Sense_4.V3.1.0.zip)
4). Configured Apps manually
*** DIDN'T use Titanium Backup ***
I am no longer seeing the infamous "Package File Invalid" message, however the Google Play Store still isn't behaving correctly.
When I log into the Play Store using a browser, and I attempt to install an App I am presented with the following:
Whilst the Play Store now recognizes that my carrier is Vodafone rather than Telstra I am not able to perform App installations from a browser. I have configured many Apps through my phone so the reasoning given by the Play Store (in the above screen capture) is not valid!
Hopefully this information helps those people who are still stuck with the "Package File Invalid" error.
Kind Regards,
Davo
P.S.: I think that this error was originally caused by my flashing several different ROM versions, and restoring Apps / Data with Titanium Backup, over a short period. In my case I installed about 3 different ROMs in the course of one day.
Issue with Google Play Store resolved
Hi Everyone,
I have resolved the Google Play Issue -
1). Log into Google Play Store (using a browser)
2). Scroll to the bottom of the page & locate "My Orders & Settings"
3). Click on the Settings Tab
4). Assign a "Nickname" to your phone
5). Check "Shown in Menus"
6). Save settings
7). Return to the Play Store and download Apps as normal!
It seems that I have overcome all issues related to the "Package File Invalid" error message! Yippee for me!!!
Thanks
Davo
Mr Davo said:
Hi Everyone,
I have resolved the Google Play Issue -
1). Log into Google Play Store (using a browser)
2). Scroll to the bottom of the page & locate "My Orders & Settings"
3). Click on the Settings Tab
4). Assign a "Nickname" to your phone
5). Check "Shown in Menus"
6). Save settings
7). Return to the Play Store and download Apps as normal!
It seems that I have overcome all issues related to the "Package File Invalid" error message! Yippee for me!!!
Thanks
Davo
Click to expand...
Click to collapse
I've been having this error on several occasions, but then I changed my ORM and got it fixed, but now it started again, nothing else worked that I tried. Luckily and weirdly this did. Thanks!
Not 4 me
Any suggestion?????
i think its a rom issue.
last month i flashed 4 different roms. but i got this message a lot lately.
i reflashed the rom but same prob.
searched a lot tried many clearing but still.
i think i got to change rom
Stay away from backup software when it comes to restoring apps and settings between ROM changes.
They are only really useful if you have ROM A, backup, flash ROM B, find that B is bull, and you flash back to A.
Even only restoring settings via Titanium after installing apps directly via the market can make apps crash when switching between versions, both app versions and android versions.
Also, after flashing, make sure you have an up-to-date market on your device, open it and nod-off those dialogs, then let your device settle for like half an hour, possible on Wifi with sleep policy to always-on. That way google can do its job. Name your device on the market via your desktop in the mean time, and install something small like the TRON Bit from there to wake that vending machine and see if app push works.
A proper restore takes half a day of love and sweat. Don't rush it. If you do, it's a weekend. I have flashed ROMs on my DEFY from Froyo to Jelly Bean and back, Quarx, official CM, stock, you name it, and never had that above package problem. But don't get me started on Titanium.
Perhaps this might work for you as well.
I had exactly the same problem, the problem was also related to Titanium Backup, I am not sure if this will work for you, but this is what I did:
In Titanium backup I went to preferences->Restoration settings->I unchecked both "associate to chosen account" and "switch to active data profile"
After that, I restored an earlier backup that I made from the Google play store app via Titanium backup.
Then I went to the market, agreed with the policy, and it worked again.
(I have no idea what I did, I am a total n00b, but it seemed to work for me...)
Mr Davo said:
Hi Everyone,
I am seeing an issue on my HTC Sensation when attempting to update Apps that I paid for in the Google Play Store. The exact message that I see when attempting to update these Apps is "Package File is Invalid".
Here is a bit of background to this issue -
1). My HTC Sensation has a custom ROM (Elegancia) installed, and I have now re-installed it (which is when these issues started).
2). I can install a ROM and update Apps through the Play Store just fine at the start
3). I install Titanium Backup and perform a restore (I have tried restoring only data & apps + data [starting from scratch and wiping the phone then installing the ROM again to test both scenarios])
4). Apps return to the state that they were in before I flashed the new ROM
*** However now whenever I attempt to update Apps I get the infamous "Package File Invalid" message ***
I have noticed when opening Titanium Backup that it alerts me that the "Android ID" has changed, it also gives two options, 1). Leave the new ID, 2). Restore the old ID
5). I tested the updating of Apps both whilst keeping the new "Android ID", and whilst restoring the old "Android ID", the ID (whilst I am sure is important) doesn't seem to affect whether or not Apps will update.
This issue only appears to be affecting Apps that I have purchased, and the Play Store still recognizes that I have purchased the Apps.
I believe that this issue is related to Titanium Backup. If anybody knows how to get around this it will be greatly appreciated. I have Googled the issue, and read up on it - none of the answers that I found worked, so I figured that another fresh ROM install should fix the problem, however it didn't!
Any help will be greatly appreciated.
Kind Regards,
Davo
Click to expand...
Click to collapse
try this it works 4 me
Mr Davo said:
Hi Everyone,
I have resolved the Google Play Issue -
1). Log into Google Play Store (using a browser)
2). Scroll to the bottom of the page & locate "My Orders & Settings"
3). Click on the Settings Tab
4). Assign a "Nickname" to your phone
5). Check "Shown in Menus"
6). Save settings
7). Return to the Play Store and download Apps as normal!
It seems that I have overcome all issues related to the "Package File Invalid" error message! Yippee for me!!!
Thanks
Davo
Click to expand...
Click to collapse
Just go to the access point names and see if there is an option to edit data access point settings. Then see if your connection is proxy enabled. If enabled, write down the proxy address for future referance.
Then erace the proxy address and save settings. Now go to play store and see if it works!
Worked for me…
Reference : androidforums.com/optimus-m-all-things-root/528253-package-file-invalid-error.html
Read more: http://www.android-advice.com/2012/fix-android-market-package-file-is-invalid/#ixzz2Ij2jaTga
zakirox123 said:
Just go to the access point names and see if there is an option to edit data access point settings. Then see if your connection is proxy enabled. If enabled, write down the proxy address for future referance.
Then erace the proxy address and save settings. Now go to play store and see if it works!
Worked for me…
Reference : androidforums.com/optimus-m-all-things-root/528253-package-file-invalid-error.html
Read more: http://www.android-advice.com/2012/fix-android-market-package-file-is-invalid/#ixzz2Ij2jaTga
Click to expand...
Click to collapse
I am on no ROM but only stock, still the same problem. Help needed.
Haha! It worked!
Mr Davo said:
Hi Everyone,
I have resolved the Google Play Issue -
1). Log into Google Play Store (using a browser)
2). Scroll to the bottom of the page & locate "My Orders & Settings"
3). Click on the Settings Tab
4). Assign a "Nickname" to your phone
5). Check "Shown in Menus"
6). Save settings
7). Return to the Play Store and download Apps as normal!
It seems that I have overcome all issues related to the "Package File Invalid" error message! Yippee for me!!!
Thanks
Davo
Click to expand...
Click to collapse
Thanks mate! It just solved my problem on my Sony Xperia Miro! You're the man! :highfive:
Hi guys, if the above does not solve this issue then the router may be the problem. After factory settings my phone I still had the issue. Spoke with the TP Link (router company) and they were able to get if fixed by getting me to do the following:
I changed my router wifi signal to Change Channel to 6, Change Width is 20MHz,
Set it to WPA2-PSK for Authentication Type--TKIP for Encryption
Disable WPS.
I actually solved this problem by going and downloading the app from a different place and installing and then updating via the google play store.
DoomN00b said:
I had exactly the same problem, the problem was also related to Titanium Backup
Click to expand...
Click to collapse
Pretty sure that's not true. Your fix may have worked, but I did a factory reset on the stock ROM...no Titanium Backup, no root, nothing...and it would still happen with certain apps. Like Netflix, Dice Player, and a few others. In fact, rooting it and pulling the APK off a different device was the only way to get it back. All this seemed to start recently, so I would guess its a bone-up on Google's side of the fence and not ours or our devices. Although it doesn't only seem to affect some devices but not all. My Nexus 7, Galaxy Nexus, and Galaxy SII don't have the issue, but my Note 8.0 started this crap about 2 weeks ago. I've tried EVERYTHING (except the nickname one above) out on the internet so far and nothing seems to globally fix it. Some things helped with 1-2 apps, but a lot of others are still having issues.
I was able to install hideman app through playstore and using that app I was able to update all apps that were failing due to that error. The app is easy to understand and has a friendly ui. Until I used this app I wasnt able to fix that error with any other suggested fix. Reboot failed t ofix same with clearing data from playstore and un installing updates from playstore.
Mr Davo said:
Hi Everyone,
I have resolved the Google Play Issue -
1). Log into Google Play Store (using a browser)
2). Scroll to the bottom of the page & locate "My Orders & Settings"
3). Click on the Settings Tab
4). Assign a "Nickname" to your phone
5). Check "Shown in Menus"
6). Save settings
7). Return to the Play Store and download Apps as normal!
It seems that I have overcome all issues related to the "Package File Invalid" error message! Yippee for me!!!
Thanks
Davo
Click to expand...
Click to collapse
Holy crap Davo, that fixed it!!! I wish I had seen this post much earlier!!! This has to be one of the biggest and dumbest screw-ups I've seen with Google/Android in a long time. Why the hell does a nickname for the device even matter?
I have to ask...seriously...how on earth did you ever figure this out?
Hi. I just wanted to post my experience with this problem so it might benefit others. I began having this problem about a week ago on my Nexus 4, Droid X, & ASUS Transformer Pad Infinity TF700T. I tried everything from this site:gizmostorm.com/how-to-fix-package-file-is-invalid-error-on-google-play-store
The only thing that worked was the Hideman VPN but before I tried that I managed to get my Nexus 4 stuck at the X when starting up by trying to manually install the Android 4.3 update because the OTA wouldn't work. I finally just flashed the 4.3 google factory image and rerooted. After all that I was still getting the error from google play on about 5% of my apps until I used the VPN and that was before reinstalling Titanium Backup. I also tested my ibVPN app and it also fixes the error.
I can only assume that this is caused on google's end after all that.
If anybody knows the true cause and how to fix it please let me know so I don't always have to run a VPN to get updates and new apps.
Same issue on my (stock ROM, rooted) SGS2 for a month or two now!
Only for paid apps: I tried anything, also the nickname change (my phone already had one); I have to check the VPN trick.
[EDIT]
I tried running Hideman before update, but the error is the same.
I also found out that the APK I download is not a valid zip file (it does not star with PK chars), is this normal for paid apps?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introducing Kinology - The Premier KFHD7 Custom ROM
Standard Disclaimer: I cannot be held responsible for loss, damages, or any kind of issue whatsoever that could arise from installing this ROM. You install it at your own risk.
Kinology is the premier custom ROM for the Kindle Fire HD 7" tablet. It will not work on any other device. Kinology should be considered a "hybrid OS"; it contains Amazon's 7.4.8 ICS-based core along with Google's ICS Services Framework and application stack.
Feature list
Installation / Download
Advanced Configuration
Known Issues
History
Screenshots
3.3 will be the last version of Kinology. The 7.4.9 update does not leave enough room on the system partition for the Kinology base. Additionally, that version of the Amazon OS is using server side filtering that prevents many non-Amazon approved applications from working correctly. My investigations into the issue did not turn up an easy fix.
What's new?
3.3 - 2014/03/12
Update the base to 7.4.8 and updated included apps. See the History page linked above for further details.
3.2 - 2013/11/21
Kinology itself is unchanged for this release. Only apps have been updated. See the History page linked above for details.
3.1 - 2013/08/11
Updated the base OS to 7.4.6.
The restart/failure message when flashing the boot zip will only be shown if the recovery is actually changed.
Installers now apply ASLR correctly to all libraries.
Added Adobe Flash Player again, as it no longer causes browsers to crash.
Updated GmsCore, Hangouts, and Play Store in the Google package.
Updated Adobe Air in the Amazon Updates package.
Behind the scenes stuff:
* Added code to the make scripts to build all-in-one installation.
* Modified the make scripts so that .apks with identical code and resources always result in binary-identical files.
* Because of the previous modification, update zips can now be automatically generated.
* Many other changes to the make scripts so that they are more resilient.
3.0. - 2013/07/21
Updated the base OS to 7.4.5.
Fixed the disabled wallpaper issue in 7.4.1.
Removed text on battery icons (a percentage option was added by Amazon).
Updated Gmail, GmsCore, and the Play Store in the Google package, and added Hangouts instead of Talk.
Update SuperSU and included SuperSUNoNag.
Removed Adobe Flash Player as it is not compatible with 7.4.5.
Fixed the install process: the boot zip is now required, but it will only flash items that you do not already have installed.
Separated Amazon app updates from Kinology proper in the install process.
XDA:DevDB Information
Kinology [KFHD7/TATE], ROM for the Amazon 7" Kindle Fire HD
Contributors
JulianPaoloThiry
ROM OS Version: 4.0.x Ice Cream Sandwich
Based On: Amazon OS 7.4.8
Version Information
Status: Stable
Current Stable Version: 3.3
Stable Release Date: 2014-03-12
Created 2014-10-16
Last Updated 2014-10-16
I was just cleaning up my system (Had CM10.1 on it, but was facing issues with Video chat in GTalk) to go back to Kinology 2.0.1 and was facing some boot issues. When I went back to see the potential list of ROMs to try, I noticed this thread.
Edit: Flashed it and seems to be stable so far. Still checking stability of various apps.
Edit 2: Spoke too soon. Just got a random reboot. The screen was in landscape mode and was trying to get it to portrait, it just rebooted.I did a first reboot before setting up the device as mentioned in the installation procedure.
Sequence of events before I got the random reboot: I flashed the files as per the installation procedure (verbatim), did a reboot after the first boot, set up the system, added google accounts, installed nova launcher, set that as my primary launcher, tried hangout, it hung in the Video call, force stopped it, then was editing the message here in the forum, went back to Kindle, was rotating to portrait mode, kindle rebooted.
EDIT 3: I am still getting random reboots trying to play around hangout. I will find GTalk apk from somewhere and install. I will update the status after that.
No flash, no fun . That was one of the best features in android for me, besides the roms. If it's possible, i would love to see a fix for it.
Thanks,
Grwy
Sent from my KFTT using xda app-developers app
Request to package just Gtalk and allow option to users to upgrade to Hangouts
One humble request: If you could, please let the users decide if they want to upgrade to hangout. I am facing issues with that, and I was able to uninstall updates to go back to GTalk. But given that Hangouts was directly add to the ROM itself, I could not go back to GTalk by just uninstalling it in Playstore.
I will figure a way to get GTalk back. But it was easier to uninstall from play store
raj3366 said:
I will figure a way to get GTalk back.
Click to expand...
Click to collapse
I can make an updater zip that replaces Hangouts with Talk. Will probably post it tomorrow sometime.
GreyGeist said:
No flash, no fun . That was one of the best features in android for me, besides the roms. If it's possible, i would love to see a fix for it.
Click to expand...
Click to collapse
This bugs me a lot, too. I'm not sure if there will be a solution. Unfortunately, the crash is very low level (in the .so files), so it's very tough to even begin to know how to work around it. I certainly plan to continue working on it, though.
raj3366 said:
I am still getting random reboots trying to play around hangout.
Click to expand...
Click to collapse
I successfully made a video call using Hangouts to my phone for testing and didn't get any reboots. I know that's just one anecdote, but if I recall, GTalk's video/voice didn't work very well for some on Kinology 2 either.
JulianPaoloThiry said:
I can make an updater zip that replaces Hangouts with Talk. Will probably post it tomorrow sometime.
Click to expand...
Click to collapse
That would be awesome. I tried replacing the Hangouts.apk with Talk.apk in the google update zip. But the signature (SHA1-digest) had to be updated in META-INF/CERT.SF and META-INF/MANIFEST.MF files. So I could not get it working.
I had very good success rate using GTalk in Kinology 2.0. I guess my mileage varies. But having GTalk gives me the freedom to upgrade to Hangouts or stay with GTalk depending on whichever works. Again, that's just my personal opinion.
Thanks for looking into this Julian. I am sending this Kindle to my parents so that I could chat over Video call. I have to get it stabilized before that. They are not tech-savy.
So far I am not seeing any other issues. I will report back, if I run into any.
I can't thank you enough for doing this.:good:
JulianPaoloThiry said:
This bugs me a lot, too. I'm not sure if there will be a solution. Unfortunately, the crash is very low level (in the .so files), so it's very tough to even begin to know how to work around it. I certainly plan to continue working on it, though.
Click to expand...
Click to collapse
Alright, thanks. I've always really liked Kinology, but the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
There is now a download available to rollback from Google Hangouts to Google Talk. Be aware that your launcher's caching may cause the icon and/or name of Hangouts to remain unchanged. Be sure to actually launch the app and check it before claiming that the rollback did not work.
Edit: Hmmmm. Hold off downloading that. I can't seem to find the voice/video options at all now.
Edit: False alarm. Turns out that Google Talk cannot voice/video chat with Google Hangouts users. So if your friends upgrade and you do not, you're SOL. There's nothing wrong with the rollback package, so use it if you like.
GreyGeist said:
the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
Click to expand...
Click to collapse
... no one reported either of those issues previously...
I've used Kinology since it was released and have not seen them. I must admit, however, that I have the lock screen disabled (my Kindle never leaves the house and has a book-like cover), so I wouldn't have noticed that one.
I do use Chrome and most other Google apps, and can't recall them ever crashing. Capturing a logcat dump immediately after a crash and sending it to me is the best way to get that sort of thing identified. The only other workable alternative is to report reproducible steps that always result in a crash.
JulianPaoloThiry said:
There is now a download available to rollback from Google Hangouts to Google Talk. Be aware that your launcher's caching may cause the icon and/or name of Hangouts to remain unchanged. Be sure to actually launch the app and check it before claiming that the rollback did not work.
Click to expand...
Click to collapse
Thanks a lot. That solves my problem. I will try it tonight when I get back home and update you. As long as it works with other google talk users, I am good. Is there procedure to repackage it myself? (if you update the google zip, I would not want you to re-package it every time. I would be more than happy to do it myself and share it for those who need that.)
EDIT: I just saw the size of it. I guess no re-packaging necessary. I just need to flash it as the last zip. This even more awesome. Thanks!
Launcher
How do you start up in tablet mode, not Kindle carousel?
Do you need a launcher?
Wind Dancer said:
How do you start up in tablet mode, not Kindle carousel?
Do you need a launcher?
Click to expand...
Click to collapse
If you do not want to use the carousel as your default launcher then you will need to install an alternative launcher from the Play Store, such as GO or Nova. The next time you reboot (or press the home button, I think), your Kindle will ask you which launcher to use, at which time you can tell it to stop asking and just use the one you pick.
JulianPaoloThiry said:
If you do not want to use the carousel as your default launcher then you will need to install an alternative launcher from the Play Store, such as GO or Nova. The next time you reboot (or press the home button, I think), your Kindle will ask you which launcher to use, at which time you can tell it to stop asking and just use the one you pick.
Click to expand...
Click to collapse
okay, thanks for the confirmation
GreyGeist said:
Alright, thanks. I've always really liked Kinology, but the gapps and lockscreen issues were its downfall for me. Are these fixed yet? In the previous build, gapps constantly crashes (especially chrome), and the lockscreen would randomly disappear.
Click to expand...
Click to collapse
Odd, I never had a problems with Gaaps (Google Applications) although I have not liked chrome on any of my Android devices. . .Sorry, I can't compare with lockscreens -since I don't use one on my KFTT, but when I did it was never an issue. . . I hope this new version will be a stable, and dependable as Kinology2 -I am downloading now! (Thanks!) :victory:
Sorry to change topic but does anyone have the full build/version number for 7.4.5, it should be something like this: 7.4.5_D025_XXXXXXX
Thanks
Gilly10 said:
Sorry to change topic but does anyone have the full build/version number for 7.4.5, it should be something like this: 7.4.5_D025_XXXXXXX
Thanks
Click to expand...
Click to collapse
4513120
I cat find the update file anywhere the one i found will not manually update. Could you send me the stock update file for 7.4.5. I like to be up to date as much as i can but amazon is not posting this update on there web site and my auto update is not updating to 7.4.5
Sent from my KFTT using xda app-developers app
Hinzman420 said:
I cat find the update file anywhere the one i found will not manually update. Could you send me the stock update file for 7.4.5. I like to be up to date as much as i can but amazon is not posting this update on there web site and my auto update is not updating to 7.4.5
Click to expand...
Click to collapse
I downloaded this 7.4.5 file but since I'm not on stock Amazon OS I can't test it to see if it'll update properly, also supposedly Adobe Flash doesn't play nice with this build.
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-7.4.5_D025_4513120.bin
Google says this issue is this: https://support.google.com/googleplay/answer/4430885
And there's pretty much nothing we or they can do but watch that page for updates.
My error 403 issue isn't like others that I have found from searching, allow me to explain...
I had two accounts on my device. One of the accounts had paid apps.
I have since abandoned that account, and installed numerous new ROMs on my phone, using only the other account as my now primary account
Now, the second account seems to think it has access to the paid apps that the other account purchased.
This means I can not download them, because it throws error 403 at me. Instead of showing "Purchase" as it should, it shows "Install".
This is even visible when I access the Play Store website from my computer, using only the second account.
See here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And please, do not suggest clearing my play store cache and all that crap, I have tried everything including going back to the stock firmware. The issue exists with my account on Googles end, but I have been back and forth emailing them for 3 weeks now, and it is like talking to a brick wall.
In short, what the frack can I do about this?
Please, if anyone has any real ideas or solutions to this I would be eternally greatful. I really don't want to have to make a whole new google account.
I have the exact same problem... I also have 2 accounts and one has paid apps. I can't seem to download the paid apps but I could download anything else
Maybe try to clear data of play app in system settings ->apps.
Smart app Studio said:
Maybe try to clear data of play app in system settings ->apps.
Click to expand...
Click to collapse
Funny. But still can't get google to sort this. Anyone???
SuperSmashedBro said:
I have the exact same problem... I also have 2 accounts and one has paid apps. I can't seem to download the paid apps but I could download anything else
Click to expand...
Click to collapse
paradoxiumwind said:
Funny. But still can't get google to sort this. Anyone???
Click to expand...
Click to collapse
i have the same problem...two accounts, one with paid apps, cannot update the paid ones...
found this "solution": push the updates to the phone using the google-account of your computer (google - play - apps - myapps...)
only thing i found up to now that works...
Firstly, some problem for this can be done by checking Google Talk is already signed in or not.. ( I have tried)
Make sure your device is logged into Google Talk by following these steps:
1. Go to your device's app launcher, and press the Talk app.
2. If you’re already signed into Talk, press Menu, and then touch Sign out.
3. Launch Talk again to sign in.
Click to expand...
Click to collapse
Secondly, If the error still occurred, here's a brief explanation directly from Play Store:
Getting an error message on my device when downloading
There are a few reasons you may be getting a download error for only one app (or for a few select apps):
1. If the app in question is a paid app, sign in to wallet.google.com/manage to confirm that the purchase was successful. "Error 405"
usually indicates that the download failed because payment did not go through.
2. Check the size of the app - if it's larger than 25M, it may be too large for your device's cache partition. Even if you have enough space
free on your device, the cache partition may be preventing you from downloading large apps.
3. If you're getting "Error: Insufficient space," ensure that after downloading the app, you'll have at least 20M of internal storage space
free. If not, you may need to uninstall apps to free up space.
"Error: 495" usually indicates that there's an issue with your connection. Usually it's temporary, but if it persists, please let us know.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Finally, if the error still occurred after those two steps, directly contact Play Store Help via Mail conversation, it can be a long talk since they also 'super busy', you may be replied by google for several hours or even days. But they definitely helpful (My own Experience). :highfive:
IMPORTANT!
Note that you haven't made any change directly to your Market app in your system, because basically it disturb other gapps and may give you frustrating errors ( again, my own experience )
Rei Zazie said:
Firstly, some problem for this can be done by checking Google Talk is already signed in or not.. ( I have tried)
Secondly, If the error still occurred, here's a brief explanation directly from Play Store:
Finally, if the error still occurred after those two steps, directly contact Play Store Help via Mail conversation, it can be a long talk since they also 'super busy', you may be replied by google for several hours or even days. But they definitely helpful (My own Experience). :highfive:
IMPORTANT!
Note that you haven't made any change directly to your Market app in your system, because basically it disturb other gapps and may give you frustrating errors ( again, my own experience )
Click to expand...
Click to collapse
I'm getting the error on the play store website on my computer - as I said, it thinks my account has purchased these apps when it has not - I only have the option to Install them, and when I try, it gives the error in the screenshots in my first post.
I've had to change from some paid apps like titanium backup pro to the ROM Toolbox as an alternative, but I really need Swiftkey fixed.
I'm still talking to google via email.
Same issue here
I've got the exact same issue on my account also. Google Play support is being no help at all. I've had a ticket open with them for 3 weeks now with 2 emails sent that whole time. I sent them a logcat today to see if they can figure out what is going on. If you get anywhere please post here so we can get this sorted out. It's blocked some of my "must-have" apps so I'm pretty upset about this.
---------- Post added at 07:40 PM ---------- Previous post was at 07:04 PM ----------
Sandcrab said:
I've got the exact same issue on my account also. Google Play support is being no help at all. I've had a ticket open with them for 3 weeks now with 2 emails sent that whole time. I sent them a logcat today to see if they can figure out what is going on. If you get anywhere please post here so we can get this sorted out. It's blocked some of my "must-have" apps so I'm pretty upset about this.
Click to expand...
Click to collapse
So here's what I found out today after loading a new rom and playing around. I have been adding both of my google accounts when I first setup the new phone. When I do this, I get the 403 error on certain apps. What I ended up doing is clearing all accounts off the phone. Then loaded my original gmail account only. This is the account I originally bought all these apps from. I went ahead and turned off all sync options but I don't think this matters. With only that account setup on the phone, I was able to download and install all the apps. I then loaded my new account and synced everything fine.
paradoxiumwind said:
I'm getting the error on the play store website on my computer - as I said, it thinks my account has purchased these apps when it has not - I only have the option to Install them, and when I try, it gives the error in the screenshots in my first post.
I've had to change from some paid apps like titanium backup pro to the ROM Toolbox as an alternative, but I really need Swiftkey fixed.
I'm still talking to google via email.
Click to expand...
Click to collapse
Did you ever get this sorted?? I am getting this error with Tasker and cant download it, Google Play website is saying it is installed, but it is not.
ricey1986 said:
Did you ever get this sorted?? I am getting this error with Tasker and cant download it, Google Play website is saying it is installed, but it is not.
Click to expand...
Click to collapse
Nope. The google support person I have been back and forth with this problem for weeks finally told me they would get back to me and have yet to do so. I think I'll send them another reply and ask what is happening with my issue.
It simply seems that they refuse to admit that the bug exists with my actual account and has nothing to do with my phone or anything. The fact that the bug exists on their play store website, accesssed from my computer, should be evidence enough (I even sent the requested screenshots).
So annoying. I can't update swiftkey or any other paid apps because of this.
Update:
I emailed again and asked for a progress report on my issue, and was told that it is a known issue and this is it: https://support.google.com/googleplay/answer/4430885
And there is nothing they can do, and that I should just keep an eye on that page for updates...
Hi Sunwind,
Your case is still currently under review by the Tier 3 team. I'm not sure how much longer it will be, and I do appreciate your patience thus far.
In the meantime, have you currently tried downloading Swiftkeys application from the Webstore, rather than from your device? You can ititiate the app to install on your device from your computer by signing into play.google.com with your account, navigating to my apps and initiating it to download that way.
I know it won't currently fix the error 403 code, but it might be a temporary work around it.
Thank you so much for you patience.
Sincerely,
Abigail
The Google Support Team
Click to expand...
Click to collapse
paradoxiumwind said:
Update:
I emailed again and asked for a progress report on my issue, and was told that it is a known issue and this is it: https://support.google.com/googleplay/answer/4430885
And there is nothing they can do, and that I should just keep an eye on that page for updates...
Click to expand...
Click to collapse
Guys, here's what I have found out and seems to have fixed this issue for me. When you open the Play Store on your phone it automagically logs you into your google account. What I didn't know is that you can switch logins to your other google account from within the app.
From the main Play Store screen, touch the Play Store menu button at the top left. This is where it says Play Store with an icon and three lines to the left of it. In the menu that pops up, it will show your username (email address) at the top. To the right of your username is a divider line with a small down arrow to the right.
If you click that down arrow it will show you your different accounts set up and you are able to select your other accounts.
What I did was change my account to my old one, and then I was able to download the apps fine. This has worked for every app that I was getting the 403 error on. Try to change accounts there and see if that doesn't fix your issue also.
Sandcrab said:
Guys, here's what I have found out and seems to have fixed this issue for me. When you open the Play Store on your phone it automagically logs you into your google account. What I didn't know is that you can switch logins to your other google account from within the app.
From the main Play Store screen, touch the Play Store menu button at the top left. This is where it says Play Store with an icon and three lines to the left of it. In the menu that pops up, it will show your username (email address) at the top. To the right of your username is a divider line with a small down arrow to the right.
If you click that down arrow it will show you your different accounts set up and you are able to select your other accounts.
What I did was change my account to my old one, and then I was able to download the apps fine. This has worked for every app that I was getting the 403 error on. Try to change accounts there and see if that doesn't fix your issue also.
Click to expand...
Click to collapse
Yes, of course that 'fixes' it, because you are using the account that has access to the apps. This doesn't fix the problem with another account thinking it has access to paid apps from a previous account, when the previous account is no longer in use/signed in to the phone/etc. This is just a 'work-around' in order to get apps you previously paid for.
paradoxiumwind said:
Yes, of course that 'fixes' it, because you are using the account that has access to the apps. This doesn't fix the problem with another account thinking it has access to paid apps from a previous account, when the previous account is no longer in use/signed in to the phone/etc. This is just a 'work-around' in order to get apps you previously paid for.
Click to expand...
Click to collapse
Right. This will get the apps you've already purchased installed on your phone. I though that was the problem you were looking for a solution to.
I have the same problem with paid apps with my multiple google accounts but that was not my main concern. The problem was when it does not allow me to install apps that I have purchased. And realistically until google allows you to transfer apps to different accounts, I will have to keep my old account active. The only other option is to re-buy all my apps on the new account which I am not willing to do.
Sandcrab said:
Right. This will get the apps you've already purchased installed on your phone. I though that was the problem you were looking for a solution to.
I have the same problem with paid apps with my multiple google accounts but that was not my main concern. The problem was when it does not allow me to install apps that I have purchased. And realistically until google allows you to transfer apps to different accounts, I will have to keep my old account active. The only other option is to re-buy all my apps on the new account which I am not willing to do.
Click to expand...
Click to collapse
The issue is detailed in full in the first post, and isn't what you thought it was.
I just resolved my 403 Error code today,I deleted my Google account then re-added it.
coogrrr94 said:
I just resolved my 403 Error code today,I deleted my Google account then re-added it.
Click to expand...
Click to collapse
Indeed, this helped
DelBoy said:
Indeed, this helped
Click to expand...
Click to collapse
I'm still getting this issue. https://support.google.com/googleplay/answer/4430885
I've wiped my phone a few times since last post and still used only the one account, but it still thinks it has access to apps that it doesn't.
This error has been driving me insane for months and there is no proper fix.
Problem:
I get an error 403 when downloading purchased apps off the play store.
Possible Cause:
I was using account A with my phone for years. I decided to get a new account and slowl migrate my stuff over.
I first added account B to my phone and used it for emails only, keeping account A for play store and youtube.
Eventually, I moved all my stuff over and used account B full time. But I noticed when trying to download purchased items, I would get the error.
It seems to me that account A "bled" over into B. So B thinks it has purchased apps when it was A.
Steps to rectify issue:
I've done the usual, clearing caches, removing/re-adding accounts. I know it's not the phone because I've had 3 different phones since this happened. When I got my HTC One, I added account B out the box and the error still happened.
I've had to contact Google support with my issue. I have also had to jump through their hoops in regards to checking things out, but I said to them, if they want to reset account B so it shows I have bought nothing, I don't mind. At least it would work and I don't mind supporting the devs again.
Currently it has been 3 months since contacting Google and the last update was on the 1st of Jan was:
Thanks for writing back and for providing details about the issue you’re having on Google Play. We really appreciate you taking the time to report this - based on the information you sent along, it appears you’re experiencing issue #11112915 from our known issues page, which is characterized by:
- Errors during the download of paid apps from the Play Store
- Download issues occurring with paid apps that were never purchased on Play Store or purchased using the Google Account exhibiting issues
- Download issues occurring on a rooted device or with an account that was previously used on a rooted device
We’re currently investigating a more permanent solution, but in the meantime you can try using a new Google Account with your device.
Click to expand...
Click to collapse
Yeah, I'm not going to make a new account for this issue, sorry Google.
Link to support ticket here.
Also, checking your wallet here, confirms my issue. Doggcatcher, which Play Store says I have purchased, I have not. For me, this isn't a phone issue. Clearing settings will do nothing. The issue is 100% Google, at least for me.
Nothing I can do now but wait for Google to sort it out.
Removing the account and re-adding didn't help me; but installing from the desktop Play store helped.
Doubt I'll be able to update from the phone, but hopefully the website will be able to do it.
Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
You might be able to at least block it from connecting to the web using netguard.
@shaftenberg
Simply disable automatic updates of apps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jwoegerbauer said:
Simply disable automatic updates of apps:
Click to expand...
Click to collapse
Well, as stated in OP, automatic update is disabled in Play Store.
That's why I'm so annoyed because Google App (velvet.apk) doesn't respect the setting.
@SmawtPho20 I don't want to block the Play Store completely, that's not a workaround by itself
Has someone successfully signed velvet.apk so that it won't be recognized by Play Store but still working?
[edit]
I just have tried to sign velvet.apk with another key and installed it as system app, but it crashes then. This isn't a solution.
Magisk debloater module to debloat it.
Karma Firewall, uses almost no battery, freeware.
Or...
If you don't use wifi, set to update by wifi only
pl1992aw said:
Magisk debloater module to debloat it.
Click to expand...
Click to collapse
Well, I do not want to remove the Google App - I just do NOT want it to auto-update it by itself. I mean, come on, the user setting is "do not update" and Google App and Youtube keep updating nevertheless. Gladly I use Youtube Vanced, so because of the other signature, auto update doesn't work.
But Google App force closes when signing with another key.
I'm using the voice search feature alot, this is the only purpose for the app in my case. So I need velvet.apk / Google App.
OR: Has anyone an idea where to get voice search only? This is baked in unfortunately as far as I know.
Voice search? Bixby's big sister
Just more invasive Gookill data mining.
You're not the customer, you're the product.
You know like cattle...
shaftenberg said:
Has anyone an idea where to get voice search only?
Click to expand...
Click to collapse
Try Google Go ?
blackhawk said:
Voice search? Bixby's big sister
Just more invasive Gookill data mining.
You're not the customer, you're the product.
You know like cattle...
Click to expand...
Click to collapse
Your post is not useful at all, please stop trolling if you don't have any helpful things to say.
Stumbled upon many messages of you in the past few hours regarding Play Services and Battery drain and it seems, you simply hate Google but your "advices" do not help as they are out of logic in the corresponding threads.
@pl1992aw Google Go does not provide a system wide voice messaging unfortunately, but thanks for the hint!
shaftenberg said:
Your post is not useful at all, please stop trolling if you don't have any helpful things to say.
Stumbled upon many messages of you in the past few hours regarding Play Services and Battery drain and it seems, you simply hate Google but your "advices" do not help as they are out of logic in the corresponding threads.
@pl1992aw Google Go does not provide a system wide voice messaging unfortunately, but thanks for the hint!
Click to expand...
Click to collapse
shaftenberg said:
Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
Click to expand...
Click to collapse
Simply my opinion. You called it "shady" yourself.
So stop stumbling like a smuck
shaftenberg said:
Hey guys,
I just discovered that the Google Search App (incl Assistant) keeps auto updating on all my devices, although Play Store is set to "manual".
This shouldn't happen at all, find this rather shady.
Has anyone any clue how to block this behavior? I'm rooted, just in case you might ask.
Thanks!
Click to expand...
Click to collapse
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
tacotory said:
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
Click to expand...
Click to collapse
Try clearing the system cache.
Hard reboot.
SDMaid might be able to find/delete the corpse file on a non-root phone. I use the old Samsung 360° powered Device Care* to clear system logs which works well.
*firewall blocked due to potential CCP spyware
blackhawk said:
Try clearing the system cache.
Hard reboot.
SDMaid might be able to find/delete the corpse file on a non-root phone. I use the old Samsung 360° powered Device Care* to clear system logs which works well.
*firewall blocked due to potential CCP spyware
Click to expand...
Click to collapse
Well, I cleared system cache and the app cache and it came back again this am.
Do you happen to know what directory the update file may be saved in and any clues on file name to look for?
Someone on another site recommended disabling Play Store and switching to a different apk app, which sounded promising. My main concern though is that I had already disabled "auto update" on the PS for the Google app and it keeps doing it- so either the file is already on my phone and the app is updating from there, or PS could be ignoring my selection...
tacotory said:
Well, I cleared system cache and the app cache and it came back again this am.
Do you happen to know what directory the update file may be saved in and any clues on file name to look for?
Someone on another site recommended disabling Play Store and switching to a different apk app, which sounded promising. My main concern though is that I had already disabled "auto update" on the PS for the Google app and it keeps doing it- so either the file is already on my phone and the app is updating from there, or PS could be ignoring my selection...
Click to expand...
Click to collapse
I keep Playwhore package disabled unless I need it. It will constantly run in the background, at start up etc. I don't use wifi, my wifi is always disabled so I set it to auto update by wifi only.
Nothing updates on my 10+ unless I authorize it to. Updates are way overrated and many times not in your best interests.
You can try locking it down with Karma Firewall. On Pie and below it's valuable logging feature is full functional. Thank Google for the limited app resources change starting with Q.
Karma uses almost no battery. A great app.
tacotory said:
I'm struggling with the same issue. The voice-to-text was wrecked by the last update. Uninstall update and everything is good again. I have also disabled auto update on the Play Store and it keeps updating. All I can figure is that there is an update file saved on the phone that it is accessing. Does anyone know if it is possible to find/ delete the update file? FWIW, I am not rooted on this device (S20).
Click to expand...
Click to collapse
Finally there is someone with the same problem Not that I like it, but now I don't feel that stupid anymore.
It seems, that Google pushes updates to Google App and Youtube regardless of the user settings in Play Store. But Youtube can't be updated automatically, because I'm using Youtube Vanced and the auto-update fails (haha).
So I suspected that a velvet.apk signed with another key would help, but this crashes immediately at start.
I haven't found a solution yet other than disabling Play Store, but this isn't a workaround for me. If you enable PS again, it will silently update Google App anyway in that short time frame.
I don't even know if Play Store is the culprit or the Google Play Services. If I had to guess, I'd tend more to the Play Services, but I really don't know.
What do you mean with "update file"? The apk to be installed will be downloaded either in a temp directory which isn't accessible without root, or it will be stored in the cache partition which you can safely clear in your recovery (Vol Up & Power). But I assume, deleting the apk wouldn't solve the problem as it has been installed already then.
Goggle Assistant and/or Quick Search maybe the culprit(s). I have both disabled along with Google Backup Transport and Framework.
I'm running on Pie as well as the factory load for most of the Google apps including Gmail and maps. I don't have this issue.
It may have something to do with Google account settings; there are many spread out in a big mess. Go through them all. I disabled most of them including Firebase and casting.
Gookill sucks.
Well, I am several days now without the app updating. Seems the solution was to disable the Google Play Services (not Play Store) app. Not sure if it is temporary or permanent of if it will cause long-term issues, but for now I have the voice-to-text interface that actually works good.
tacotory said:
Well, I am several days now without the app updating. Seems the solution was to disable the Google Play Services (not Play Store) app. Not sure if it is temporary or permanent of if it will cause long-term issues, but for now I have the voice-to-text interface that actually works good.
Click to expand...
Click to collapse
I'm just curious to see if this held or not. I've been dealing with the same thing with my SwiftKey keyboard. The Google app completely ruins speech to text on it. And the more you roll it back, the more frequently it wants to update. I've been fighting it for months and so far the only thing that I found are suggestions that require me to root which I kind of grew out of several years ago.
It is working. I had it backwards in my previous post though. You need to disable Play Store (not Play Services). Disabling Services kills a majority of apps.
I use Swiftkey also, but I don't think it has anything to do with Swiftkey. Swiftkey just uses the Google voice-to-text.
Once Play Store is disabled you have to go the the Google app and uninstall updates. The only negative I have experienced is that you have to enable PS again when you need to download a new app from the store (expected) which will mean uninstalling updates again.
Anyone have any suggestions on how to get the Assistant voice typing option working in Gboard? I'm at my wits end trying to figure this sh!t out and believe I have tried everything I can find on the Internet, as well as my own tinkering. Everything was working fine, but then all of a sudden this morning it stopped and the Assistant voice typing option is grayed out saying You can't currently use Assistant voice typing. The following are things I've tried
clearing data/cache for Gboard, as well as the Google app - still says You can't currently use Assistant voice typing
removed my Google non-gmail account
uninstalling Gboard (beta) and Google app (beta), which leaves you with the system default versions - same message
updated Google app (beta) from Play Store - Assistant voice typing needs an update. Connect to Wi-Fi to automatically download
leave Gboard settings, go back and message returns - You can't currently use Assistant voice typing
switched to non-beta of Google app via APKmirror - same result as the beta
updated to non-beta of Gboard - You can't currently use Assistant voice typing
what else haven't I tried??
Hi, it seems like you are as desperate as I was about that stupid greyed out option. I searched for days until I found a solution at least for my case. Perhaps it also works for you.
These are the instructions I followed:
1. Go into Assistant Settings and select Language (Account-Settings -> Google Assistant -> Sprachen (German for Languages))
2. Remove secondary Language by clicking on it and in Radial-Menu selecting keine (German for "None") right at the top.
3. Go into Gboard-Settings, into Voice typing. Now the option of Assistant Voice Typing should be available. Activate it!
4. Go back into Language-Settings for Assistant and add secondary Language again. After that just check it the Assistant Voice Typing is still activated in The GBoard settings.
You might have to give it some time to download the necessary files. I first thought it did not work, but when I checked again a bit later, it did!
Hope this helps.
vielfalter said:
Hi, it seems like you are as desperate as I was about that stupid greyed out option. I searched for days until I found a solution at least for my case. Perhaps it also works for you.
These are the instructions I followed:
1. Go into Assistant Settings and select Language (Account-Settings -> Google Assistant -> Sprachen (German for Languages))
2. Remove secondary Language by clicking on it and in Radial-Menu selecting keine (German for "None") right at the top.
3. Go into Gboard-Settings, into Voice typing. Now the option of Assistant Voice Typing should be available. Activate it!
4. Go back into Language-Settings for Assistant and add secondary Language again. After that just check it the Assistant Voice Typing is still activated in The GBoard settings.
You might have to give it some time to download the necessary files. I first thought it did not work, but when I checked again a bit later, it did!
Hope this helps.
Click to expand...
Click to collapse
I believe I may have come across your post in my searches and unfortunately I have checked there to see if there were any secondary languages that may have caused this and there are none =(
I ran into the same problem when I added Spanish to my languages for Gboard. Then after that, Google voice assisted typing worked intermittently. There were times that it didn't work, and then times that it did.
My remedy was sticking to just an English keyboard and flashing a whole new rom since I do it every month. I also wiped user data, because I thought whatever caused the problem was in user data.
Then it started working again. Whatever it is by Google, it's a nasty bug.
I've noticed in the settings, it says that I can't use it at times, but when I go to use it, it works perfectly fine.
Another thing is, if you're rooted, you can used rBoard to enable the flag NGA(New Google Assistant), but you will have to first do the fix for the flags by pasting the files they give into your /data/data/ folder to fix whatever Google did to the keyboard that breaks rBoard at the moment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rester555 said:
I ran into the same problem when I added Spanish to my languages for Gboard. Then after that, Google voice assisted typing worked intermittently. There were times that it didn't work, and then times that it did.
My remedy was sticking to just an English keyboard and flashing a whole new rom since I do it every month. I also wiped user data, because I thought whatever caused the problem was in user data.
Then it started working again. Whatever it is by Google, it's a nasty bug.
Click to expand...
Click to collapse
yes, I feel the same way in that it's a nasty bug that is somehow related to languages. tried too many things that I don't remember now, but I believe this started happening after I had added Japanese as a second language somewhere. removing any traces of it did not fix it and I fear unless it's fixed that the only way to fix now is to either wipe or find the cause and report it...
Curiousn00b said:
I've noticed in the settings, it says that I can't use it at times, but when I go to use it, it works perfectly fine.
Another thing is, if you're rooted, you can used rBoard to enable the flag NGA(New Google Assistant), but you will have to first do the fix for the flags by pasting the files they give into your /data/data/ folder to fix whatever Google did to the keyboard that breaks rBoard at the moment.View attachment 5765073
Click to expand...
Click to collapse
do you have a link to this rBoard app? searches turn up rBoard theme manager, but the screenshots of the app do not look anything like yours... are you saying that rBoard breaks or GBoard when it comes to fixing the files in /data/data? does this mean you run this fix from time to time to get NGA working?
dimm0k said:
do you have a link to this rBoard app? searches turn up rBoard theme manager, but the screenshots of the app do not look anything like yours... are you saying that rBoard breaks or GBoard when it comes to fixing the files in /data/data? does this mean you run this fix from time to time to get NGA working?
Click to expand...
Click to collapse
That's correct. It does a lot of things actually. You can even make your own custom themes for GBoard as well as enable different flags that aren't enabled by default.
Here's the XDA link for rBoard linking to the downloads.
[APP] Rboard Theme Manager
*require root* Rboard Theme Manager Manager app for Google Gboard keyboard app. Continuation of Magisk module "Rboard themes" with more customizations and themes. Rboard Themes are not overlays but just additional themes for Gboard app...
forum.xda-developers.com
There's been an uprise lately with XDA vs Telegram and whatnot, but based on what I read on the other thread, this doesn't violate the rules since you're not required to join the group to see this post, so...
Rboard Themes
New fix for flags until we figure it out why this happens: • Download • Extract it to /data/data/com.google.android.inputmethod.latin/shared_prefs • Force close Gboard flags should work now
t.me
This post here will tell you what to do do get rBoard working correctly. Root is required and you have to do this every time you update GBoard since it'll replace what you've done. You can turn off updating so you don't have to do it every time.
Feel free to PM me(or post here so others can see) and I'll happily guide you through whatever you need help with so that you get the hang of the app.
dimm0k said:
Anyone have any suggestions on how to get the Assistant voice typing option working in Gboard? I'm at my wits end trying to figure this sh!t out and believe I have tried everything I can find on the Internet, as well as my own tinkering. Everything was working fine, but then all of a sudden this morning it stopped and the Assistant voice typing option is grayed out saying You can't currently use Assistant voice typing. The following are things I've tried
clearing data/cache for Gboard, as well as the Google app - still says You can't currently use Assistant voice typing
removed my Google non-gmail account
uninstalling Gboard (beta) and Google app (beta), which leaves you with the system default versions - same message
updated Google app (beta) from Play Store - Assistant voice typing needs an update. Connect to Wi-Fi to automatically download
leave Gboard settings, go back and message returns - You can't currently use Assistant voice typing
switched to non-beta of Google app via APKmirror - same result as the beta
updated to non-beta of Gboard - You can't currently use Assistant voice typing
what else haven't I tried??
Click to expand...
Click to collapse
If you are rooted there are some Magisk mods that screw up ASI, which can impact voice input among other things. Pixilify screwed things up for me
K1nsey6 said:
If you are rooted there are some Magisk mods that screw up ASI, which can impact voice input among other things. Pixilify screwed things up for me
Click to expand...
Click to collapse
I was in fact rooted and using Pixelify... were you able to fix whatever issues you had with Pixelify? seems like disabling it as a test does not fix anything on my end regarding this issue...
Possibly trying to disable every accessibility will work. Tried it and after a day or so it worked(not grayed anymore)
dimm0k said:
I was in fact rooted and using Pixelify... were you able to fix whatever issues you had with Pixelify? seems like disabling it as a test does not fix anything on my end regarding this issue...
Click to expand...
Click to collapse
I had to factory reset it. I tried uninstalling ASI updates first with no luck. After a clean install everything works perfectly, without Pixelify. I lost voice text, live translate, Now Playing, and transcribe. I'm sure there were other features that it broke.
The only Pixelify mod I enabled was unlimited Photos storage.
TheShinyEnd said:
Possibly trying to disable every accessibility will work. Tried it and after a day or so it worked(not grayed anymore)
View attachment 5765557
Click to expand...
Click to collapse
I did try this... at least for the ones I actually touched/enabled, but that never helped =(
K1nsey6 said:
I had to factory reset it. I tried uninstalling ASI updates first with no luck. After a clean install everything works perfectly, without Pixelify. I lost voice text, live translate, Now Playing, and transcribe. I'm sure there were other features that it broke.
The only Pixelify mod I enabled was unlimited Photos storage.
Click to expand...
Click to collapse
yes, after your mention and my original suspicions I decided to look more closely into this Pixelify module. what I found and confirmed is that even if you only enable the unlimited Photos storage, there are other things that get installed/modified and one of them is ASI!! I've gone through the install script, as well as the files included in the module to comment out everything not dealing with the unlimited Photos mod. for extra measure I also removed the unneeded APKs and whatever else I could find from the module and repackaged it as a custom module for my own use. so far... it seems to be working!!
Just putting in my thoughts on the whole Pixelify thing, but I said I avoid using that module since it's used to enable Pixel features on non-Pixel devices. Since we already have a Pixel, it changes a lot of settings when everything already works fine.
Other have claimed the other Pixelify(app) doesn't work for them, but maybe you guys can try it as well. Don't know if you guys were apart of the other thread or not, but open it, select Pixel XL, click force stop(grant root), then open Google Photos and back up something. After that, check the description of it at the very very bottom for this tag in the screenshot below.
As for Assistant Voice Typing, you'll have to use rBoard to manually enable it. I've linked it in my other post above with the fix to get it working.
Curiousn00b said:
Just putting in my thoughts on the whole Pixelify thing, but I said I avoid using that module since it's used to enable Pixel features on non-Pixel devices. Since we already have a Pixel, it changes a lot of settings when everything already works fine.
Other have claimed the other Pixelify(app) doesn't work for them, but maybe you guys can try it as well. Don't know if you guys were apart of the other thread or not, but open it, select Pixel XL, click force stop(grant root), then open Google Photos and back up something. After that, check the description of it at the very very bottom for this tag in the screenshot below.
As for Assistant Voice Typing, you'll have to use rBoard to manually enable it. I've linked it in my other post above with the fix to get it working.
Click to expand...
Click to collapse
what is this other Pixelify app that you have in the screenshot?? didn't know there was a frontend for it...
dimm0k said:
what is this other Pixelify app that you have in the screenshot?? didn't know there was a frontend for it...
Click to expand...
Click to collapse
GitHub - Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos: Pixelify GPhotos
Pixelify GPhotos. Contribute to Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos development by creating an account on GitHub.
github.com
It requires LSPosed. Once enabled, just open the app, set it to Pixel XL and click force stop. After that, try backing something up and then check to see if you have what I had in the screenshot above.
dimm0k said:
yes, after your mention and my original suspicions I decided to look more closely into this Pixelify module. what I found and confirmed is that even if you only enable the unlimited Photos storage, there are other things that get installed/modified and one of them is ASI!! I've gone through the install script, as well as the files included in the module to comment out everything not dealing with the unlimited Photos mod. for extra measure I also removed the unneeded APKs and whatever else I could find from the module and repackaged it as a custom module for my own use. so far... it seems to be working!!
Click to expand...
Click to collapse
Does flashing your modified module fix the issue or do you have to factory reset to revert the changes made to the ASI? I have the same problem where my now playing isn't working properly. Voice text, live translate, and transcribe seems to work well. I'm hesitant to factory reset the phone just for the now playing feature.
chaos193 said:
Does flashing your modified module fix the issue or do you have to factory reset to revert the changes made to the ASI? I have the same problem where my now playing isn't working properly. Voice text, live translate, and transcribe seems to work well. I'm hesitant to factory reset the phone just for the now playing feature.
Click to expand...
Click to collapse
you can think of my module pretty much as a gutting of the original module so only the relevant bits pertaining to unlimited photos remain therefore it will not fix the issue without doing a factory reset unfortunately. you may be able to revert the changes by examining all the changes done and reversing them
Curiousn00b said:
GitHub - Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos: Pixelify GPhotos
Pixelify GPhotos. Contribute to Xposed-Modules-Repo/balti.xposed.pixelifygooglephotos development by creating an account on GitHub.
github.com
It requires LSPosed. Once enabled, just open the app, set it to Pixel XL and click force stop. After that, try backing something up and then check to see if you have what I had in the screenshot above.
Click to expand...
Click to collapse
I am considering the LSPosed approach as it does seem cleaner... I know a lot has changed since the XPosed days, but does LSPosed all SafetyNet to pass enough for GPay to work?