@Bloody bk What operating system have you running on your computer ?
You can check by watching any youtube video about lineageos 18.1, it's the same across devices.Can you record some video demonsration about the UI please?
Is it completely stock Android or else?
Like Sony's lolIt's more like original Google Android than the misconfigured and bloated stock Android versions that are shipped with OEM devices.
Hello,New version out; see 1st post.
- Hotspot and WiFi Tethering should work now
Yes, please! And tell me step by step what you've done, so that I can reproduce it in the LOG file.Is there any logs I can capture?
Which file have you chosen?found a mixer_paths.xml in your 15.1 thread
How should I do it?Yes, please! And tell me step by step what you've done, so that I can reproduce it in the LOG file.
Nah, it's a pseudonym I've been using over the net in recent years. I use Mac OS and Fedora.@litelinux Do you use Linux Lite ??
(According to your name)
Logging? This is described in several posts; in mine too...How should I do it?
My device keeps as cool as a well cooled drink!BTW the heating is also happening when hotspot is not turned on.
TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels
This feature requires netlink features that are unsupported on
kernel versions lower than 4.4, therefore opt-out for it in such
cases and avoid constantly crashing TcpSocketTracker.
==================================
I keep getting these periodic crashes/hangs, and /data/system/dropbox gets filled:
====================================================
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65648/684
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.parseSockInfo(TcpSocketTracker.java:312)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.pollSocketsInfo(TcpSocketTracker.java:245)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at com.android.server.connectivity.NetworkMonitor$ValidatedState.processMessage(NetworkMonitor.java:1050)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at android.net.networkstack.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at android.net.networkstack.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at android.os.Handler.dispatchMessage(Handler.java:106)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at android.os.Looper.loop(Looper.java:223)
11-04 17:28:28.471 +0000 1625 4410 E TcpSocketTracker: at android.os.HandlerThread.run(HandlerThread.java:67)
====================================================
Fixed in the latest ROM:I can observe this on our device too, the exact same thing.
Yes. But haggertk says here, he changed the kernel. But I can't find any related commits for that. Please help me and point to them. (I'm not a kernel expert)Fixed in the latest ROM: