Fixed being unable to see voices in the Android data folder of the app, thanks Kareen: Turns out I forgot to migrate the folders back from when I tried implementing direct boot. Added direct importing of .zvoice files. Since we can't make the files app inport such a file, you can click open with or share to in your file manager, find GoogleTTS Player, then import .zvoice files directly Fixed friendly language names not being translated.

Importing bugs fixed

When I look at Locomel voices and I try using them on my PC, then see how fasdt they actually work, I'm astonished by it. With MultiTTS, I wouldn't have reached here, and I want to thank everyone for believing in this project. Google voices have always been my interest. I am so very glad I got this working. Now I am happy I can be a fulltime GoogleTTS user, on all of my systems. Though more potential can be done on computers by making them run as fast as they can on capable hardware, I don't think I'll get into it. I have almost no experience with PC development.

Information: The default Google voices, the ones you see in GoogleTTS, are less trained than the Google assistant voices you also have access to. Instead of using IO and TP voices like IOF, IOG, IOL, IOM, TPC, TPD, TPF, using the assistant voices you will have better experience: They are hol
jmp
sfg
tfe
tme.
These voices are only available for the English (United States) language and not seen by TalkBack with the official GoogleTTS app.

Do not update your phones to June 2026 security patch level! Instead, use this app and check for updates for when it updates with your supported device. This app, when device supported, allows you to root your device to circumvent a kernel volnerability. With root, you can then install a custom recovery environment and, perhaps, boot a ROM.

PAY EXACT AND CLOSE ATTENTION!
The Fouad MODs channel, for those who are still subscribed, has either been breached, hacked, or the owner sold the channel, and now it is running a scam and we need to talk!
The scam goes like this: On the channel, they are announcing that they're moving to a new channel. When you click the link, a Telegram web app opens that asks you to join. When you click join, it tells you to enter a code they sent. Do, not, enter, that, code!
That code is received, in fact, from Telegram Verified Notifications and it is a Telegram login code! Absolutely do not give these codes out to anyone or don't enter them unless you absolutely know you are trying to sign in!
Starting with this channel, I understand this is an ongoing scam and it won't be the last time you see this. Enable two factor authentication on your account, enable signing in with passkeys, and never share login codes with anyone, especially on a web app, the developers have access to your account after that. Or, if not yet, they'll try to gain access.
So stay on the run, never share your login codes or anything related to your authentication methods!

Version 1.6: What's new: Full support for all watch DPIs, please test with watches and tell if the UI shows up properly. - Added voice downloader - Added volume scale - Hopefuly fixed AutoTTS shit, test as I don't have the app, nor I'll pay for something that I won't use.

Remember: To use the voices, you need to download the Berdock package for the specific language. Enjoy!

I have been trying to look for a trial for NVDA, but I can't find one. Does anyone have/know where I can get the RunaTTS add-on package so I can install it to my NVDA?

Fix: If device's language was not English, the TTS wouldn't speak. Fix: Independent voice selection requested by app was not working. Fix: Voice changing immediately on selection.

Further improvements to performance

A prise, a prise, what a surprise! After this long time, we are here with the X86_64 release of GoogleTTS Player! I jenuinly need testers though. Real ChromeOS or ARM PC testers with Android running as primary OS on their PC! Emulators keep lagging and it's because of emulation, not because of the app.