The app is programmed to not show any full screen ads, if the screen is off or if something else is showing on the screen (be it the lock screen, or Android home screen or another app). It just continues reading in such cases. I tried today very hard to reproduce this problem, and cannot. The full screen ad shows ONLY if the screen is on and the text the app is reading is visible, and the app is loading the next chapter of an ebook, or the next article on the reading list.
 
Please answer this question precisely: when you think that the app stopped reading when the screen was locked due to a full screen ad, what EXACTY do you see IMMEDIATELY AFTER unlocking the screen, and before touching anything else on the screen? Also, on which Android device are you using @Voice app, and what is the Android system version on it?
 
Greg

Is the screen on and you follow the text the app reads on screen, when it stops? Or does it stop only when the screen is off, or even on, but something else, not @Voice app is visible on the screen? It's important to know this before giving the correct answer. Let's cover both:
 
1. If the app stops when screen is off or something else, not @Voice is visible on the screen, your phone kills apps working in background to "save battery". Please visit https://hyperionics.com/atVoice/stops.html, press there on the type of phone that you have, read the next page THOROUGHLY and implement the suggested settings.
 
2. If reading stops when screen is on and you observe the text @Voice reads on the screen, you are probably using Google TTS voice, and don't have the latest data downloaded, that Google needs to generate speech locally. Therefore they send each sentence to their servers, generate the speech there and send speech data over the Internet back to the phone to produce sounds. This breaks when the Internet connection slows down or breaks, or when Google servers get overworked. To download the necessary data (or update the data), connect the phone to a good and fast WiFi network, then start speech in @Voice. Google downloads this data automatically when you try to use any such voice, but ONLY on WiFi.
 

Thank you, let me know. The "battery saving" is a huge problem for developers. Original Android versions and Google Pixels after some small adjustments behave well, but other makers aggressively kill apps that work in background to "save battery" and then brag in their ads about the "great battery life" that they devices have. They often have internal lists of apps that should be allowed to work with screen off, like popular music players, but if you're not on their list - bad luck. For both developers and users. More info: https://dontkillmyapp.com/problem
 
 
 

Maybe the headset sends a random "pause button pressed" event to the app? Could you verify if this happens only when you listen through your headset, or also when the headset is completely disconnected and you listen through the phone's speaker? Or with another headset?
 
Greg