Hi there!
After much trial and error, we finally found one workaround for this annoying glitch event.
Unfortunately, our business is no longer able to continue, but we wanted to share this workaround for those who might be facing the same problem.
Note: This method is not an official workaround. If you apply it, please do so at your own risk.
The workaround we have found is as follows:
・First, prepare one kid’s profile.
・Add the application that is causing the problem to the kid’s profile.
・Switch from the normal profile to the kids’ profile.
・Run the app on the home screen of the kids’ profile.
As far as we have been able to verify, this method has not caused any problems with revocation of microphone privileges.
We hope this method will help someone.
Thank you.
Unfortunately kids stuff is not availble in my location/region.
Also, the app using microphone I’m running in the background. Not sure your workaround would even support that?
@Emma any update? Anything I can support you with? I factory reset my HD10+ and properly registered it, installed all (3) apps from Amazon Appstore and still facing this issue.
Hi @Thomas_Brasser !
The methods we have communicated do not require new children’s devices.
For more information on adding a Kids Profile, please see below.
https://www.amazon.co.jp/gp/help/customer/display.html?ref_=hp_left_v4_sib&nodeId=■■■■■■■■■■■■■■■■&language=en_US
https://www.amazon.co.jp/gp/help/customer/display.html?nodeId=TLapk3JDh2OYFiiBed&language=en_US
For those who may have mispronounced the term, ‘Kids Profile’ is described as ‘Child Profile’ in English.
We hope this information is helpful to you.
Thank you.
Unfortunately the kids profile cannot be setup on my geographic region. (Netherlands)
I am currently testing an automatic reboot application: https://play.google.com/store/apps/details?id=com.vanasoft.rebootme
But it requires google play services/store so not ideal.
Any way to schedule reboots natively maybe?
Hoping for a non-workaround solution/fix to the losing microphone permissions issue.
Hi @Thomas_Brasser !
I see.
So you can’t set up a profile for children in the Netherlands?
We regret it very much.
According to our previous experiments, restarting the Fire tablet did not prevent the loss of microphone privileges.
Rebooting only changed the timing of the loss of microphone privileges to around the time of the reboot.
Also, if you temporarily disconnect the Fire tablet from the WiFi connection just before the loss of microphone privileges, the event of loss of microphone privileges at the expected time will not occur and the microphone privileges will be lost when you reconnect to the WiFi.
Hope this helps you.
It would be helpful if we could get information from Amazon as well, but alas.
Thank you.
Postscript:
https://www.amazon.nl/gp/help/customer/display.html?ref_=hp_gcs_csd_d2_000_1_TE9UR1c1VsPhWeLGcl_idy5TMeA9b&nodeId=TE9UR1c1VsPhWeLGcl&qid=1726021697061&sr=1
I know it’s not a children’s profile, but would the information at this URL be helpful?
Indeed childrens profile does not exist in my region.
And also I found out indeed rebooting is not a working workaround 
Thank you for trying to help me out, unfortunately the shopping profiles are used for amazon shopping, not for devices.
Would love to hear from @Emma any updates.
I’m also waiting for Emma’s response🤚
Thanks in advance @Emma
Yeah, same issue here… it’s horrible. My IP Webcam app running in the background loses Microphone permission once or twice a day. I have to stop it, and grant access again to get it working again… but then ot happens all over again within a few hours. Will try the kids profile workaround mentioned above… how anyone figured that out is beyond me…
Hi, Joe_Hogan!
We feel so sad for that you have encountered this glitch.
We were using Amazon’s cost-effective Fire tablets to run a service for people in need of care.
The service was very well received and we were looking to increase the number of users.
Unfortunately, our project was shut down due to this glitch.
Every day, more than 100 tablets were stripped of their microphone privileges, which had a huge impact on our field operations.
We decided not to continue the service because of the risk of the same problem occurring in the future with Kids Profile.
we are very very disappointed.
We hope that your app and everyone else who encounters this issue will be able to work around it by using Kids’ Profiles.
Thank you.
The reality is that I haven’t seen amazon address a single issue in these forums with an answer other than clear cache or reinstall app. But to your point, the fire tablets are very cost effective. I’m heavily invested in amazon despite this kind of stuff, because their products work well for the average user. Its the power users that get the short end of the stick, and in a twisted way, thats good business. Why expend senior resources solving problems that a tiny minority of power users have?
I think i may have fixed this by manually setting the permission to “allow” through ADB instead of using the fire interface, which only has the option to “Allow while in use”. The steps are basically:
- Enable Developer Options so you can connect USB Debugging
- Get and install the APK file you want and find its package name (upload apk here to find package name): Sixo Online APK Analyzer | sisik
- connect to device with ADB debugging… you can do this many ways, but Fire Toolbox is a good option
- run the following command, substituting the [package_name] for your package name you found above:
cmd appops set --uid [package_name] RECORD_AUDIO allow
- Verify this command worked by reviewing the output of the following command (insert your package name):
cmd appops get --uid [package_name] RECORD_AUDIO
Note: I used APK Mirror to get the APK i wanted instead of using the amazon store, because I could only be sure of the package name if i had the actual APK file to upload… I couldnt be sure what the package name was if i installed though the amazon app store and didnt have the APK file.
1 Like
Hi, there!
We have not heard anything from Amazon, but this troublesome glitch event may have finally stopped reproducing.
The combinations of terminals and FireOS that we were able to confirm we did not reproduce are as follows.
Fire7：8.3.2.4
Fire7：8.3.3.1
Fire HD 8：8.3.2.5
Fire HD 8 PLUS：8.3.2.5
Is the problem event continuing on your devices?
Unfortunately, we have confirmed that the same problem has occurred again since last weekend.
It’s reoccurring on Fire7, Fire HD 8, and Fire HD 8 PLUS.
What is the reason for the recurrence?
I have a hard time understanding it.
What about your device?
1 Like
