Cell plugged in via USB causing annoyance.

[Zarius]

So, when I plug my cell phone in to my tower while I'm in fossapup, the bloody OS keeps "probing cameras", and then tells me "no cameras found." It wouldn't be nearly as bad if it just did it *once*, but it keeps doing it. Why is it doing this, and how the heck do I make it stop?

[williams2]

When I plug cell phone in to charge it, it pops up several windows.

If the usb port is not working properly, because of a bad connection (from maybe a loose connection of the usb jack to the motherboard) it can behave as if you are unplugging and plugging in the usb cable repeatedly.

I found it annoying, so I edited the file /usr/sbin/pupautodetect and added the commandexit as the 2nd line, at the top of the file. That is, I changed this:

Code: Select all

#!/bin/ash

to this:

Code: Select all

#!/bin/ash
exit

I don't know if what you are experiencing is the same thing.

[bigpup]

What mode is the cell phone USB connector in?
charging, media transfer protocol (MTP), Picture transfer protocol (PTP), RNDIS (USB Ethernet), Audio source and MIDI?

[Zarius]

I'm not sure what mode it's in, but it doesn't give me constant dings in windows. (My laptop runs windows, and is working perfectly fine.) So, it's probably not the mode. It *might* be the port, but don't think so. It does the same thing hooked up to the USB3 port I have my wifi dongle hooked up to and the USB2 port I have my Bluetooth dongle hooked up to, and those don't lose connection.

The exit command is what I'll try first, thanks will.

[April]

Put a little metho ,alchohol, on a cotton bud and clean inside the usb plugs if you can.
corrosion causes resistance and capacitance so you have weird frequency responses.

Takes but a minute to eliminate that possibility.

Do you have different cables for usb 3 and 2 or is there a common plug in there somewhere . The phone plug is common anyway. Pencil rubbers clean contact too. Use whatever you can squeeze in there.

I gave Fossa away , too many problems. Made a thread about it too . Xenialpup64-7.5 works well for me .

[bigpup]

I assume you are plugging the phone in to do some kind of data transfer?

I'm not sure what mode it's in, but it doesn't give me constant dings in windows. (My laptop runs windows, and is working perfectly fine.)

Look in the phones settings.
Someplace it should have a way to select or change the USB connector mode.
media transfer protocol (MTP) or Picture transfer protocol (PTP) is probably what Puppy is looking for.

We do not care how Windows works.
Puppy Linux is not using the same programs as Windows uses.

To eliminate one possible cause.
Fossapup64 9.5 has Quickpet program.
Quickpet->Info->Fossapup updates
Run that update.
Reboot and update the fossapupsave so the new changes are now being used.

Any help?

[Zarius]

Put a little metho ,alchohol, on a cotton bud and clean inside the usb plugs if you can.
corrosion causes resistance and capacitance so you have weird frequency responses

Nope, nope, nope. The only ethyl-derivative I have in the house is a) vodka, which will leave water residue, ethyl alcohol residue, and residue from whatever chemical it is they mixed in to booze to make you... purge if you imbibe too much and b) already tinctured, and will leave a dozen *other* kinds of residue.

I do, however, have 90% isopropyl that I cleaned it with (even had some discoloration that might have been light corrosion or just dust), but to no avail. Cleaned PC's and phone's ports, and both ends of the cable.

Do you have different cables for usb 3 and 2 or is there a common plug in there somewhere . The phone plug is common anyway. Pencil rubbers clean contact too. Use whatever you can squeeze in there.

I've tested it on USB 2 and 3 ports on both the front and back of the machine (different hubs). Pretty certain it's not the port.

I assume you are plugging the phone in to do some kind of data transfer?
Look in the phones settings.
Someplace it should have a way to select or change the USB connector mode.
media transfer protocol (MTP) or Picture transfer protocol (PTP) is probably what Puppy is looking for.

Thinking about it, that's proooooobably how the phone is currently set up, though I'm having issues finding the area these options are in. I have put a request for help up on the manufacturer's site and will hopefully hear back eventually.

We do not care how Windows works.
Puppy Linux is not using the same programs as Windows uses.

While you make a valid point, testing the same hardware on different operating systems does provide at least some valid feedback on the issue. The hardware works normally in a different OS both on the same machine and a different one.

I specifically tested on the laptop because I'm setting this up because Windows on this machine is giving me problems, and thus is not an entirely reliable source of data without a known-good set up giving the same results. Or, more accurately, I actively refuse to trust the information given by a known-suspect installation without secondary confirmation.

To eliminate one possible cause.
Fossapup64 9.5 has Quickpet program.
Quickpet->Info->Fossapup updates
Run that update.
Reboot and update the fossapupsave so the new changes are now being used.
Any help?

Negatory, Ghost Rider, the pattern is full. No change.

[Zarius]

When I plug cell phone in to charge it, it pops up several windows.

If the usb port is not working properly, because of a bad connection (from maybe a loose connection of the usb jack to the motherboard) it can behave as if you are unplugging and plugging in the usb cable repeatedly.

I found it annoying, so I edited the file /usr/sbin/pupautodetect and added the commandexit as the 2nd line, at the top of the file. That is, I changed this:

Code: Select all

#!/bin/ash

to this:

Code: Select all

#!/bin/ash
exit

I don't know if what you are experiencing is the same thing.

This. This right here. (Just tested it, now that my migraine's gone and I remembered about it.) This fixed the issue. Thank you.

[Zarius]

Just as a further note, I did, in fact, find the location to change USB behavior. I set it to Charge Only, and it's doing exactly the same thing. So updating the pupautodetect file is, in fact, exactly the solution I needed.

[bigpup]

I did, in fact, find the location to change USB behavior. I set it to Charge Only

So what was it set to before?

What is the phone?
Make and model?

You may have found a bug in Fossapup64 or Puppy in general.

[Zarius]

I did, in fact, find the location to change USB behavior. I set it to Charge Only

So what was it set to before?

What is the phone?
Make and model?

You may have found a bug in Fossapup64 or Puppy in general.

Galaxy A10E. It *was* set to data transfer, as suspected. But when I changed the behavior to charge only, then reboot the computer back in to FossaPup, the cam hunt continued. Changing the load fixed the issue, so there's no 100% guarantee that it's an issue with pup, but I've removed hardware and external software issues to a sufficient degree that I'd have requested permission to ask my L2 to look at it, if I were still working the warranty help desk. And *probably* gotten approval, as long as it wasn't my third manager.

[April]

Where did you find a place to change usb behaviour?

[April]

I found it annoying, so I edited the file /usr/sbin/pupautodetect and added the commandexit as the 2nd line, at the top of the file. That is, I changed this:

Code: Select all

#!/bin/ash

to this:

Code: Select all

#!/bin/ash
exit

I don't know what fossapup has in here but below is what xenialpup64-7.5 has in that file.

#!/bin/sh
#Barry Kauler, Oct. 2011
#called via udev /etc/udev/rules.d/88-puppy-autodetect.rules
#111007 first release.
#111010 maybe wait until delayedrun has done its stuff.

[ ! "$1" ] && exit
[ "`pidof X`" = "" -a "`pidof Xorg`" = "" ] && exit #X not running.
export PATH='/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/root/my-applications/bin'
export DISPLAY=':0'

#111010 maybe wait until delayedrun has done its stuff...
EXCNT=0
while [ ! -f /tmp/delayedrun_finished_flag ];do #see /usr/sbin/delayedrun.
sleep 2
EXCNT=$(($EXCNT + 1))
[ $EXCNT -gt 10 ] && break #precaution
done

please_install() {
gtkdialog-splash -bg orange -close box -text "Please install $1"
exit
}

case $1 in
camera)
which gmtp 2>&1 >/dev/null || please_install "pupcamera"
gmtp &
;;
android-device)
which gmtp 2>&1 >/dev/null || please_install "mtpdevice"
gmtp mount &
;;

esac

So it must be different . Can you explain please?

Looking at fossapup64-9.5 the same file shows as

#!/bin/ash
#Barry Kauler, Oct. 2011
#called via udev /etc/udev/rules.d/88-puppy-autodetect.rules
#111007 first release.
#111010 maybe wait until delayedrun has done its stuff.

[ ! "$1" ] && exit
[ "`pidof X`" = "" -a "`pidof Xorg`" = "" ] && exit #X not running.
export PATH='/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/root/my-applications/bin'
export DISPLAY=':0'

#111010 maybe wait until delayedrun has done its stuff...
EXCNT=0
while [ ! -f /tmp/delayedrun_finished_flag ];do #see /usr/sbin/delayedrun.
sleep 2
EXCNT=$(($EXCNT + 1))
[ $EXCNT -gt 10 ] && break #precaution
done

please_install() {
gtkdialog-splash -bg orange -close box -text "Please install $1"
exit
}

case $1 in
camera)
pupcamera &
;;
android-device)
if [ "$(which pupmtp)" != "" ]; then
pupmtp &
elif [ "$(which mtpdevice)" != "" ]; then
mtpdevice mount &
else
please_install "mtpdevice or pupmtp"
fi
;;

esac

So I don't follow whats suggested here or what you have done?
If you just exit there then there are other commands that will not be done . There is some path export stuff in there .
It may work for you but it might break other stuff.

[williams2]

There is some path export stuff in there

Exporting the values of bash variables in a script only affects that script and executables that were called by that script (child processes.)
It does not affect other scripts or processes, whether started before, after, or at the same time as that script.
Exporting the values of bash variables in a script does not affect the Puppy operating system at all.
The effect is localized to the script and to any subprocesses started by the script.

Basically, all that the autodetect script does is start pupcamera or pupmtp when a cell phone or a digital camera is plugged in.

[April]

@williams2 Good to know

[Zarius]

Where did you find a place to change usb behaviour?

It ended up being right on the notification drop down, after I deleted all of my backlogged notifications. -.-" Which means I was trying to look too deep in to the system to find it. But that's my own fault for hating smartphones so much.

[April]

It ended up being right on the notification drop down, .

Im not familiar with that term"notification drop down," What do you mean by it ,where is that found please ?

[Jafadmin]

It ended up being right on the notification drop down, .

Im not familiar with that term"notification drop down," What do you mean by it ,where is that found please ?

@April , On my android, when I receive a txt message or an email, a little notification icon appears in the upper-left corner of my display, and the notification light blinks. That is where the USB notification gets put. The problem is, it doesn't always put an icon there. So just down-swipe the upper-left corner when you plug in a USB to PC cable and you should see the notification.

Tap the notification and Robert is your mother's brother ..