u/TooManyInsults

In 12/25, I installed one of these cameras. I connect to it using TinyCam Pro and Slim Camera (on Windows) using a fairly typical rtsp URL to the LAN IP using user id and password. I have TinyCam running 24/7/365 on Android 8 monitoring this camera. It is setup to send email on human object detection. I only occasionally view the camera using Slim Camera on Windows or another instance of TinyCam Pro on my phone. I have its O-Kam app on a phone I never really use because it is required for initial setup. But I can open it and see the camera stream as well (no idea if it is rtsp or what).

For unknown reasons, over the last couple weeks I have experienced a condition when none of the TinyCam or Slim Camera instances find an active stream. TinyCam just shows black in the live view. The camera is ping-able at its reserved IP address. The O-Kam all shows it as alive and I can see a stream. No number of O-Kam triggered restarts does anything about this. Restarting the devices using TinyCam and Slim Camera does nothing.

About the only thing that "fixes" this is removing and re-applying power to the camera.

All this is strange/bad enough. But here is the kicker that I simply cannot understand at all...

Even though TinyCam shows nothing in its live view, I am still getting email on human object detections. I do NOT have motion or other detection enabled on the device in any way. This is done by TinyCam. So I figure that TinyCam is somehow still talking to/seeing the device even though the live view and settings say it is not!

How can this be? And is there a clue in here as to what is happening to the live rtsp stream?

Thanks!

According to Google AI:

The main difference between the am kill and am force-stop commands is how deeply they terminate the application and whether they allow it to restart. am force-stop completely shuts down the app and locks it from running again, whereas am kill only terminates safe background processes, allowing the app to easily wake back up.

It would seem, based upon experiential results, that the Kill App action uses the equivalent of KILL rather than force-stop. And in some cases, KILL does not make the target app dead enough!

I know this has been discussed before. And so far, it appears that the only way for Tasker to force-stop an app is when a rooted device executes am force-stop pkg_name in a shell.

Since I am rooted, I can do that and actually get the results, I seek. But since I know this has come up before, it would be great (if at all possible) if the Kill App action had an option to force-stop instead of KILL.

Anyone else find a different/better solution? Thanks

Akin to the post here but perhaps a little different enough to warrant this...

In my case, I am searching for HTTP Request items in my current Tasker configuration.

The problem comes because a have ALOT of them - mostly in the form of Actions but also some in the form of Profiles.

Digging through the search results to find the Profiles buried along with all of the Actions is a real PIA. It would be so great if there was a way to filter Action/Profile/Variable!

I have tried, for example, searching "event: HTTP Request:" - which is how these are labeled in the search results - when I can actually find them. But that yields no search results whatsoever. I have tried all of the various options (contains, etc) to no avail.

Perhaps there is some other way to do this? Thanks!

Thinking to get some of these for a parallel battery pack. But I generally avoid cells where:

(a) the maH claims are excessive

(b) the cell weight is below what I expect to see

The claim here of 6500 maH is highly questionable to me. But the weight at 140g matches some decent cells I have been using.

Thanks for any tips.

I admit that I am asking here before trying it myself. Just wonder if someone else has checked this out.

Thanks!

Bottom of this page. Thanks

I am really new to Widget v2. It is really interesting and valuable. Thanks!

Seems I have to tap the checkmark for changes to a v2 widget's layout to take effect when I run the task that sets the layout.

This doesn't seem right/normal to me.

Anyone else notice this? Thanks

I have been using KLWP for some time now and I have a wallpaper with many Komponents each of which has several flows running on a regular basis triggered by data format changes (rather than cron - which did not seem to work as well).

I have been having problems after making changes to my wallpapers in the editor. After making/saving ANY change in my wallpaper in the editor, I find that the entire operation of my wallpaper goes whacky - forcing me to reboot my phone in order to clear out the log jam. It has been this way for a while now - certainly over 6 months. But there has been no change in this over time and perhaps it is getting even worse.

Since wallpaper development, at least for me, consists of a series of MANY iterations/changes over time, having to reboot the phone every single time just to see the results of my most recent changes has become intolerable for me.

Has others encountered this? Any suggestions on how to avoid this? Thanks

As seen here? I am confused about the precise size. It says "32650 3.2V 6000mAh LiFePO4 battery 32700 6500mAh". Cannot be both, obviously. In my limited past experience, getting anything more than 6aH in one of these is indeed rare. So the claim of 6.5aH makes me suspicious. Seems like the higher the capacity claim, the lower quality cells seem to be. Thanks for any light you can shed.

Hello and thanks in advance for any suggestions. I have a Win10 host with 2 virtual boxes running (one Android x86 and the other Unbuntu). The host is connected to my Asus router via ethernet. Both virtual boxes have networking configured as shown here.

I have found that if the router is power cycled both virtual boxes keep running fine in all aspects except that their networking breaks - stops working entirely. The UI's networking indicator keeps flashing and there is no sign of any error or abnormal condition. But there is no networking happening either in or outbound.

In order to remedy this situation, I have found that, if I terminate and re-start the virtual boxes upon the router's restart, they come up with all networking as normal again.

Please note that this only happens on a power cycle. I have the router set to reboot nightly and this does NOT seem to have this effect.

So, is there something I can do to "protect" the networking in these virtual boxes?

If not, is there some way to detect the router power cycle so I can create a Task Manager job to restart the virtual boxes? If so, I do not want to do it for reboots, only for the power cycles.

Thanks so much!

I have been using the Android app for years. It is up to date with Play Store. Suddenly, this morning, it will not login/authenticate. I can use the website - doing that here. I have uninstalled/re-installed. No difference. What is going on here? Thanks!

Is this possible? Thanks for any suggestion.

I am asking here because I see so many people using these computers (which I really love)...

I wonder if anyone can tell me what are the items on the inside of the lid that I have outlined in the photo attached?

I ask because I was testing mine w/the cover off entirely and discovered that the BT, which had always worked great, started seriously under-performing. I put the cover back on and all seems fine again.

I have no idea if the attached Google AI is correct. But it made me wonder about the bits on the inside of the lid.

Thanks!

https://preview.redd.it/vbxbvkq8f1bh1.jpg?width=639&format=pjpg&auto=webp&s=d79da3546beb93d091efdadcacf3c9cc7710eca8

https://preview.redd.it/foj9gy0af1bh1.png?width=1080&format=png&auto=webp&s=75c6789c99d9e31ebcfcf60991128698bbde34e2

I purchased some of these pass-thru connectors. Then using two of these USB-C cables with their USB-A ends connected to either side of this thing, I connected one USB-C to my battery pack and the other to my Moto phone for charging. For reasons unclear to me, this did NOT WORK at all.

I then use the one of those cables with its USB-A connected to my battery pack into the USB-C port on this thing and connect the other side of the USB-C to my phone using a USB-C to USB-C cable and the phone DOES CHARGE.

Can someone explain to me why the first scenario does NOT WORK? All of the cables/phones/battery pack work fine otherwise. It is ONLY when connecting via the USB-A ports on this pass-through device that it does NOT work. I am stumped again!

Thanks.

We have 3 lines total. All started on annual plans. I am in the process of moving all three (I hope) to a shared pool. My 1st line is on the pool right now and has been for a couple months. It will renew in a couple days on the 4th.

The annual plan for the 2nd line will expire the 17th of this month. I am not sure if I need to (or if there is any real benefit to) having all the lines renew on the same date. If so, how to be achieve this?

Thanks