phi303 13 Posted May 7 Share Posted May 7 It's the weirdest thing, on my nvidia shield, if I close emby i.e. hit the back button and hit 'yes' to exit - when I try and load emby again, it will just hang infinitely. same goes with hitting the home button twice and pressing down to remove the app from recent. the only way to get back into emby is completely uninstalling it and re-installing it, oddly going into storage and clearing data and cache doesn't do the trick (makes no sense to me). rebooting the shield also does nothing, it HAS TO BE an uninstall and re-install. IF I just hit the home button and let emby stay in the background and do whatever and go back into emby, it's totally fine so long as I didn't actually close emby. I'm completely dumbfounded by this because nothing makes sense to me. Link to comment Share on other sites More sharing options...
sa2000 19 Posted May 7 Share Posted May 7 I just tried the Emby Android TV app on the Shield - Version 2.1.10g and the app re loaded ok after going through - remote: Back key and then selecting EXIT on the Exit Emby? dialogue and then relaunching Emby. Must be something specific to your configuration. Is it just the one user account that you use ? Could I get more info on the setup and versions in use and maybe get Android app debug logs before the hang and also server logs with debug logging enabled beforehand - covering that period and when the app is restarted and hangs To get the android app debug logs - on the app Settings, select "General Display" and then scroll down until you get to "Enable debug options" and tick/select that. Then go back to the app screen and your account avatar and when that opens, you can choose Send Logs which will send them to emby. Note down the exact time and the emby user account being used. Then restart the app which you expect for it to hang - note down the time and now collect the server logs See this article on android TV logs and server logs Link to comment Share on other sites More sharing options...
sa2000 19 Posted May 8 Share Posted May 8 @phi303is the problem still there ? Have you enabled debug options? You can go through this and after it hangs re-install the go through the steps to send logs and giving the time and timezone and user account name and also getting the server logs in case there are some server aspects Link to comment Share on other sites More sharing options...
ebr 14959 Posted May 8 Share Posted May 8 Hi. Are you running a VPN or any other network watchdog type system? Link to comment Share on other sites More sharing options...
consumer 2 Posted Wednesday at 03:00 PM Share Posted Wednesday at 03:00 PM (edited) Solution at the end. I'd been having the same issue with the Emby for Android TV version 2.1.1.10g. If I use the "Clear Data" I am able to open the app and log in, otherwise same as the OP. I had uninstalled the Android TV app a few times to make sure that I have the latest version and the problem persists. This is happening on both my Hisense TV running Android TV and 2 Invida Shields running Android TV. This behavior was new after upgrading to the beta release of the 4.9 branch. Log errors: 2024-05-15 07:51:49.289 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:51:49.289 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network 2024-05-15 07:52:29.062 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:52:29.062 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network 2024-05-15 07:52:29.066 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:52:29.066 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network My solution was to login to the Emby web interface and change my login password. I used the same password as before and now Android TV auto login works again without issue. Edited Wednesday at 03:00 PM by consumer 2 Link to comment Share on other sites More sharing options...
phi303 13 Posted Wednesday at 06:25 PM Author Share Posted Wednesday at 06:25 PM 3 hours ago, consumer said: Solution at the end. I'd been having the same issue with the Emby for Android TV version 2.1.1.10g. If I use the "Clear Data" I am able to open the app and log in, otherwise same as the OP. I had uninstalled the Android TV app a few times to make sure that I have the latest version and the problem persists. This is happening on both my Hisense TV running Android TV and 2 Invida Shields running Android TV. This behavior was new after upgrading to the beta release of the 4.9 branch. Log errors: 2024-05-15 07:51:49.289 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:51:49.289 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network 2024-05-15 07:52:29.062 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:52:29.062 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network 2024-05-15 07:52:29.066 Debug HttpServer: InitRemoteConnectionInfo - ipAddressFromHeaders: 192.168.200.49 2024-05-15 07:52:29.066 Debug HttpServer: InitRemoteConnectionInfo - rejecting ipAddressFromHeaders as on local network My solution was to login to the Emby web interface and change my login password. I used the same password as before and now Android TV auto login works again without issue. omg, yes, this is exactly the problem! thank you so much! everything is back to normal now. as you stated, i just went and re-added my same password and it's all gravy now - thank you again! 1 Link to comment Share on other sites More sharing options...
ebr 14959 Posted Wednesday at 07:09 PM Share Posted Wednesday at 07:09 PM That's very odd but I'm glad y'all figured something out. Link to comment Share on other sites More sharing options...
phi303 13 Posted Wednesday at 08:19 PM Author Share Posted Wednesday at 08:19 PM On 5/8/2024 at 8:11 AM, ebr said: Hi. Are you running a VPN or any other network watchdog type system? i'm not sure if relevant but I do have a pihole running at the router level. VPNs are only on browsers for me - I wonder if user consumer also has a pihole running? either way, i'm just so happy the problem is solved lol 1 Link to comment Share on other sites More sharing options...
consumer 2 Posted Wednesday at 11:38 PM Share Posted Wednesday at 11:38 PM @phi303 Great catch on the pihole. I am running that also. hmmmmmmm.. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now