Giter Club home page Giter Club logo

Comments (3)

petrnalevka avatar petrnalevka commented on September 21, 2024

Please correct me if I'm wrong, but isn't this the more aggresssive version of Doze mode introduced in Android 7.0? In general Doze mode can kick in just after screen on and it does restrict networking..

from dont-kill-my-app.

brianjmurrell avatar brianjmurrell commented on September 21, 2024

I thought so too. But I have a LineageOS 15.x (Android 7.x) phone which doesn't exhibit this behaviour and have been talking to somebody with a 7.1 phone that doesn't do it either.

from dont-kill-my-app.

brianjmurrell avatar brianjmurrell commented on September 21, 2024

This gets even more interesting (read: annoying).

It seems I can keep the network "awake" by having it plugged into a USB port and with adb running. I'm not sure if both of those are needed, but they prove a useful way to keep the network awake while investigating other issues.

But even with the network awake (i.e. the device continues to respond to pings), apps running on the device, while the screen is off can't seem to get their packets out of the device.

The example I have on hand is linphone-android. It is Firebase push enabled, so it can be killed by doze, etc. and an FCM push can be sent to wake/start it back up and that does work. I can see, using adb logcat that the app does start up once an FCM push is sent. All good to this point.

As soon as linphone-android wakes it tries to register itself with the SIP proxy it's configured to use but I can see (again, using adb logcat) it trying to register, but doing packet traces on the network, I can see that those registration attempts don't actually result in any network traffic. It's like the phone has blocked the app from being able to send it's network traffic out.

None of this happens on my LineageOS 15.x device. It works perfectly as expected with all of the above. Push starts up linphone-android and it successfully registers with the SIP proxy, so the above shenanigans does not seem to be a stock Android issue, at least with Nougat. I wonder if Oreo has added this additional nasty behaviour.

I would really like to understand if this is stock Android 8.x or if this is more Huawei mucking about.

from dont-kill-my-app.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.