[opensuse] MTP file access, Android 6.0 and Linux
Unfortunately Android 6.0 (Marshmallow) has dropped USB mass storage mode for accessing the SD card. The remaining USB modes are: MTP, PTP, RNDIS, Audio Source, MIDI and charge only. I am searching a working USB solution for file transfer. MTP works on Windows. But I am mostly unsuccessful with MTP clients on openSUSE (Tumbleweed). The FUSE tools "mtpfs" and "simple-mtpfs" were both unable to mount my Android 6.0 smart-phone external SD card. KDE (KIO) shows the smart-phone but is unable to access data. The only working solution on my PC is Nautilus from Gnome. But even with Nautilus I was unable to transfer a directory with some GB data without errors. So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC. Any ideas? Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 21. September 2016, 09:47:56 CEST schrieb Bjoern Voigt:
Unfortunately Android 6.0 (Marshmallow) has dropped USB mass storage mode for accessing the SD card. The remaining USB modes are: MTP, PTP, RNDIS, Audio Source, MIDI and charge only.
I am searching a working USB solution for file transfer. MTP works on Windows.
But I am mostly unsuccessful with MTP clients on openSUSE (Tumbleweed).
The FUSE tools "mtpfs" and "simple-mtpfs" were both unable to mount my Android 6.0 smart-phone external SD card. KDE (KIO) shows the smart-phone but is unable to access data. The only working solution on my PC is Nautilus from Gnome. But even with Nautilus I was unable to transfer a directory with some GB data without errors.
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
Any ideas?
I'm getting pretty good results with KDE Connect... It's in KDE:Extra. Cheers M -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 21, 2016 at 09:47:56AM +0200, Bjoern Voigt wrote:
Unfortunately Android 6.0 (Marshmallow) has dropped USB mass storage mode for accessing the SD card. The remaining USB modes are: MTP, PTP, RNDIS, Audio Source, MIDI and charge only.
I am searching a working USB solution for file transfer. MTP works on Windows.
But I am mostly unsuccessful with MTP clients on openSUSE (Tumbleweed).
The FUSE tools "mtpfs" and "simple-mtpfs" were both unable to mount my Android 6.0 smart-phone external SD card. KDE (KIO) shows the smart-phone but is unable to access data. The only working solution on my PC is Nautilus from Gnome. But even with Nautilus I was unable to transfer a directory with some GB data without errors.
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
Any ideas?
In general we have MTP support included, but it was not working well as I tested it. In Android 6 you need to specifically allow it on the device too. I just tried Nautilus on Tumbleweed, that seems to open them (after clicking the accept dialog on the device). Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-21 12:04, Marcus Meissner wrote:
On Wed, Sep 21, 2016 at 09:47:56AM +0200, Bjoern Voigt wrote:
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
My tablet uses ex-fat, so I can't do that.
Any ideas?
In general we have MTP support included, but it was not working well as I tested it.
I have 13.1, and using the XFCE desktop I don't have problems transferring files using MTP. It is slow, sometimes it stalls if the android device sleeps, things like that. I transferred 16 GB of videos recently to my tablet, using Thunar and Midnight Commander. Yes, yes, old 'mc' works. The transport is not done by 'mc', but there is a virtual filesystem under "run user mtp: something" that has the tablet. It went fine. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-09-21 12:04, Marcus Meissner wrote:
On Wed, Sep 21, 2016 at 09:47:56AM +0200, Bjoern Voigt wrote:
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
My tablet uses ex-fat, so I can't do that.
exfat can be mounted on linux, no problem. There is a fuse module for it - https://software.opensuse.org/package/fuse-exfat -- Per Jessen, Zürich (15.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op woensdag 21 september 2016 13:25:28 CEST schreef Carlos E. R.
On 2016-09-21 12:04, Marcus Meissner wrote:
On Wed, Sep 21, 2016 at 09:47:56AM +0200, Bjoern Voigt wrote:
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
My tablet uses ex-fat, so I can't do that.
Yes, you can https://software.opensuse.org/search?utf8=%E2%9C %93&q=exfat&search_devel=false&search_unsupported=false&baseproject=openSUSE %3ALeap%3A42.1
Any ideas?
In general we have MTP support included, but it was not working well as I tested it.
I have 13.1, and using the XFCE desktop I don't have problems transferring files using MTP. It is slow, sometimes it stalls if the android device sleeps, things like that.
I transferred 16 GB of videos recently to my tablet, using Thunar and Midnight Commander. Yes, yes, old 'mc' works. The transport is not done by 'mc', but there is a virtual filesystem under "run user mtp: something" that has the tablet. It went fine.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-21 14:21, Knurpht - Gertjan Lettink wrote:
Op woensdag 21 september 2016 13:25:28 CEST schreef Carlos E. R. <> :
My tablet uses ex-fat, so I can't do that.
Yes, you can
https://software.opensuse.org/search?utf8=%E2%9C %93&q=exfat&search_devel=false&search_unsupported=false&baseproject=openSUSE %3ALeap%3A42.1
For 13.1 fuse-exfat comes only from home repositories. So, I can not. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-09-21 14:21, Knurpht - Gertjan Lettink wrote:
Op woensdag 21 september 2016 13:25:28 CEST schreef Carlos E. R. <> :
My tablet uses ex-fat, so I can't do that.
Yes, you can
https://software.opensuse.org/search?utf8=%E2%9C %93&q=exfat&search_devel=false&search_unsupported=false&baseproject=openSUSE %3ALeap%3A42.1
For 13.1 fuse-exfat comes only from home repositories.
So, I can not.
Carlos, you _can_, but you don't _want_ to. You could even download it and build it yourself, it's not that difficult. -- Per Jessen, Zürich (8.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 07:20, Per Jessen wrote:
Carlos E. R. wrote:
For 13.1 fuse-exfat comes only from home repositories.
So, I can not.
Carlos, you _can_, but you don't _want_ to. You could even download it and build it yourself, it's not that difficult.
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Thu, Sep 22, 2016 at 12:28:39PM +0200, Carlos E. R. wrote:
On 2016-09-22 07:20, Per Jessen wrote:
Carlos E. R. wrote:
For 13.1 fuse-exfat comes only from home repositories.
So, I can not.
Carlos, you _can_, but you don't _want_ to. You could even download it and build it yourself, it's not that difficult.
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok.
And FWIW, we can not include exfat support into our products as it is using patent enforced code. So, well. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 12:45, Marcus Meissner wrote:
On Thu, Sep 22, 2016 at 12:28:39PM +0200, Carlos E. R. wrote:
And FWIW, we can not include exfat support into our products as it is using patent enforced code.
I know :-) But you just reminded me to look in packman. Sure enough, it is there :-)) Thanks! -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2016-09-22 12:54, Carlos E. R. wrote:
On 2016-09-22 12:45, Marcus Meissner wrote:
On Thu, Sep 22, 2016 at 12:28:39PM +0200, Carlos E. R. wrote:
And FWIW, we can not include exfat support into our products as it is using patent enforced code.
I know :-)
But you just reminded me to look in packman. Sure enough, it is there :-)) Thanks!
For the record, installing fuse-exfat from packman worked out of the box. Plug in the card and reader, and open it in thunar automatically. Happy camper here :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/23/2016 06:59 PM, Carlos E. R. wrote:
On 2016-09-22 12:54, Carlos E. R. wrote:
On 2016-09-22 12:45, Marcus Meissner wrote:
On Thu, Sep 22, 2016 at 12:28:39PM +0200, Carlos E. R. wrote:
And FWIW, we can not include exfat support into our products as it is using patent enforced code.
I know :-)
But you just reminded me to look in packman. Sure enough, it is there :-)) Thanks!
For the record, installing fuse-exfat from packman worked out of the box. Plug in the card and reader, and open it in thunar automatically.
Happy camper here :-)
I've use the fuse and the kernel mode, and tried utilities Go do a search at https://software.opensuse.org/search for your distribution. Talk to the packagers. Its also in a 'mainstream' repository - http://download.opensuse.org-filesystems -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-24 02:26, Anton Aylward wrote:
On 09/23/2016 06:59 PM, Carlos E. R. wrote:
On 2016-09-22 12:54, Carlos E. R. wrote:
On 2016-09-22 12:45, Marcus Meissner wrote:
On Thu, Sep 22, 2016 at 12:28:39PM +0200, Carlos E. R. wrote:
And FWIW, we can not include exfat support into our products as it is using patent enforced code.
I know :-)
But you just reminded me to look in packman. Sure enough, it is there :-)) Thanks!
For the record, installing fuse-exfat from packman worked out of the box. Plug in the card and reader, and open it in thunar automatically.
Happy camper here :-)
I've use the fuse and the kernel mode, and tried utilities Go do a search at https://software.opensuse.org/search for your distribution. Talk to the packagers.
Its also in a 'mainstream' repository - http://download.opensuse.org-filesystems
No, see Marcus answer at the top of this mail. Exfat is never going to be part of the distribution. Also, for 13.1 there is nothing that can be changed or added. Packages and repos disappear, not the other way. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/23/2016 09:31 PM, Carlos E. R. wrote:
On 2016-09-24 02:26, Anton Aylward wrote:
On 09/23/2016 06:59 PM, Carlos E. R. wrote:
On 2016-09-22 12:54, Carlos E. R. wrote:
For the record, installing fuse-exfat from packman worked out of the box. Plug in the card and reader, and open it in thunar automatically.
Happy camper here :-)
I've use the fuse and the kernel mode, and tried utilities Go do a search at https://software.opensuse.org/search for your distribution. Talk to the packagers.
Its also in a 'mainstream' repository - http://download.opensuse.org-filesystems
No, see Marcus answer at the top of this mail. Exfat is never going to be part of the distribution.
I'm perfectly well aware of the legal issues and constraints; I have been and have been using fuse-exfat since I started using it to transfer files and photos back and forth with my table, getting for over 2 years ago, if memory serves me correctly. We'd been discussion the unreliability of using "home:" repositories. I said "mainstream" in contrast to that. If I'd meant 'distribution' I would have said 'distribution'.
Also, for 13.1 there is nothing that can be changed or added. Packages and repos disappear, not the other way.
I'm not sure about that. For example ... I use the 'latest' build of 'darktable from home:darix He has up to date builds for * openSUSE_13.1 * openSUSE_13.2 * openSUSE_Leap_42.1 * openSUSE_Tumbleweed as well as other distributions. And I thought 13.1 was 'evergeened'. I never took that to mean 'frozen' or 'decaying' as you seem to imply. The web page for evergreen says that updates will arrive in the usual update repository. There are updates there in the last month. If you are trying to tell me that its not in 'filesystems', then sorry, it is.
# zypper info fuse-exfat
Information for package fuse-exfat: ----------------------------------- Repository: openSUSE BuildService - filesystems Name: fuse-exfat Version: 1.2.4-1.1 Arch: x86_64 Vendor: obs://build.opensuse.org/filesystems Installed: Yes Status: up-to-date Installed Size: 86.6 KiB Summary: Free exFAT file system implementation
If you are trying to tell me that obs:filesystem is not part of the 'distribution', then I can only reply that it's not part of 'home:' either. So we get back to the matter of the repositories having an explanatory 'header' file. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-24 05:29, Anton Aylward wrote:
Also, for 13.1 there is nothing that can be changed or added. Packages and repos disappear, not the other way.
I'm not sure about that. For example ... I use the 'latest' build of 'darktable from home:darix He has up to date builds for
* openSUSE_13.1 * openSUSE_13.2 * openSUSE_Leap_42.1 * openSUSE_Tumbleweed
as well as other distributions. And I thought 13.1 was 'evergeened'. I never took that to mean 'frozen' or 'decaying' as you seem to imply. The web page for evergreen says that updates will arrive in the usual update repository. There are updates there in the last month.
The evergreen maintainers do updates to the oss repo, that's about all they can manage to do. Security updates mainly. Some repository maintainers do updates for evergreen, yes. Some remove them. For example, there are no updates to shotwell that I could find. And I need them. I resort to use the one in 42.2B via virtual machine. LibreOffice, Science, Publishing, utilities, filesystem... all have been removed.
If you are trying to tell me that its not in 'filesystems', then sorry, it is.
# zypper info fuse-exfat
Sorry, but search in the OBS said it is not there. I have it enabled: Telcontar:~ # zypper ls | grep file 24 | OBS_filesystems | OBS: filesystems | Yes | Yes | rpm-md Telcontar:~ # However, that repository has been removed for 13.1. I'm using a local mirror: Telcontar:~ # grep url /etc/zypp/repos.d/OBS_filesystems.repo #baseurl=http://download.opensuse.org/repositories/filesystems/openSUSE_13.1 baseurl=http://amonlanc.valinor/mirrors/repositories/filesystems/openSUSE_13.1 Telcontar:~ # Yet, it is true they *had* exfat: Telcontar:~ # zypper se --details fuse-exfat Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+------------------------+------------+-----------+--------+------------------------ i | fuse-exfat | package | 1.2.4-1.2 | x86_64 | EXT: Packman Repository v | fuse-exfat | package | 1.2.4-1.2 | i586 | EXT: Packman Repository v | fuse-exfat | package | 1.2.3-1.1 | x86_64 | OBS: filesystems v | fuse-exfat | package | 1.2.3-1.1 | i586 | OBS: filesystems | fuse-exfat | srcpackage | 1.2.4-1.2 | noarch | EXT: Packman Repository | fuse-exfat | srcpackage | 1.2.3-1.1 | noarch | OBS: filesystems | fuse-exfat-debuginfo | package | 1.2.4-1.2 | x86_64 | EXT: Packman Repository | fuse-exfat-debuginfo | package | 1.2.4-1.2 | i586 | EXT: Packman Repository | fuse-exfat-debugsource | package | 1.2.4-1.2 | x86_64 | EXT: Packman Repository | fuse-exfat-debugsource | package | 1.2.4-1.2 | i586 | EXT: Packman Repository Telcontar:~ # The version in packman in newer.
If you are trying to tell me that obs:filesystem is not part of the 'distribution', then I can only reply that it's not part of 'home:' either.
No, simply that "search OBS" did not find it because the repo has been removed. Maybe you see it because you hit a mirror that still has it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/22/2016 06:28 AM, Carlos E. R. wrote:
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok.
Suuuuuuure! The owner is the guy that (re-)coded it and inserted the trojan. He's the one guy that you can ABSOLUTELY be sure will say "yea, there's nothing wrong with my code, there's no bugs, there's no back-doors, thre's no trojans" while sniggering at you. Of course you *HAVE* to build it yourself. Of course you *HAVE* to pour over each line of code and figure out all the interactions and side effects. Of course you have to have a complete mastery of not just the programming language and all the libraries and includes, which you have poured over in detail as well, but the complier and compiler sub-system to make sure its not suffering from the Thompson Effect: https://www.win.tue.nl/~aeb/linux/hh/thompson/trust.html <quote> The moral is obvious. You can't trust code that you did not totally create yourself. (Especially code from companies that employ people like me.) No amount of source-level verification or scrutiny will protect you from using untrusted code. In demonstrating the possibility of this kind of attack, I picked on the C compiler. I could have picked on any program-handling program such as an assembler, a loader, or even hardware microcode. As the level of program gets lower, these bugs will be harder and harder to detect. A well installed microcode bug will be almost impossible to detect. </quote> I will admit that I did read and understand the code for the V6 kernel, thank you John Lyons. I did read and understand the code for the V7 kernel and many UNIX utilities at that level since I was employed for a few years maintaining them, along with some USB utilities we -ahm - 'imported'. I reviewed SYSTEM III and sampled the code, and felt that the Bell UNIX Systems group had taken a step backwards. In particular, the code for 'more' in BSD was, why typical 'student' coding, quite direct, the USG version was pure spaghetti. One the basis of the code I read I trusted the 'professionals' at USG less that I trusted the group of individuals that produced V6 & V7 and the 'kids and academics' at Berkeley who had produced BSD. Later, seeing the "dialogue" and VAX-Wars between Bill Joy, who was producing the free software of BSD for the VAX, and Dave Cutler, who designed and produced RSX-11M, VMS and VAXELN at Digital Equipment and later went on to develop NT at Microsoft, where the 'open' BSD that Joy was using could be tuned and improved and using a HLL (OK, 'C') faster and better than Cutler could do in assembler for VMS, it pretty much destroyed my fair in 'professional' and 'closed source' systems. I gave up at that point. From then on I relied on automation. There's a quotation one of my university profs employed: If a better system is thine, impart it if not, make use of mine. So I use Linux. One final question, Carlos. Presumably you have installed openSuse from the supplied binaries on the DVD or via the network, update binaries via the repository. Presumable you trust the people who contribute their time to build these. How do you differentiate these people from the ones that use the Build System and put the results in "home:" ? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 13:26, Anton Aylward wrote:
One final question, Carlos. Presumably you have installed openSuse from the supplied binaries on the DVD or via the network, update binaries via the repository. Presumable you trust the people who contribute their time to build these. How do you differentiate these people from the ones that use the Build System and put the results in "home:" ?
I don't know about Carlos, but in my case I place some trust in the 'many eyes' effect. Quite a few people use the builds in the main repository and quite a few people are involved in the builds, and some of those have been for years. So I feel there's a fair chance of problems being discovered. Far fewer eyes on code in home repositories. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/22/2016 08:54 AM, Dave Howorth wrote:
On 2016-09-22 13:26, Anton Aylward wrote:
One final question, Carlos. Presumably you have installed openSuse from the supplied binaries on the DVD or via the network, update binaries via the repository. Presumable you trust the people who contribute their time to build these. How do you differentiate these people from the ones that use the Build System and put the results in "home:" ?
I don't know about Carlos, but in my case I place some trust in the 'many eyes' effect. Quite a few people use the builds in the main repository and quite a few people are involved in the builds, and some of those have been for years. So I feel there's a fair chance of problems being discovered. Far fewer eyes on code in home repositories.
Number vs quality? There are some, popular even, FOSS projects, in GiHub even, which, if you go back over postings, have had flaws that remain undiscovered for years. There's a point/counterpoint about specialists. One of my interests, regular readers might recall, is photography, and I use Darktable. its pretty complex and uses mathematical algorithms which, while I understand the mathematics of, I don't understand either the application to photography not the coding of same. I'm lucky, I suppose, since there are many people using photographic software, FOSS & closed source, who are "just" in it for the art :-) Their eyes glaze over at the maths and the coding, but so what, they are probably better photographers than I am. But not only are the developers of these tools specialists and enthusiasts, and damn sight more helpful when you have a problem than any support I've had from the 'professional' vendors that I've paid money for, and who, probably because the corporate bean counters say its cost-effective and affects the bottom line, outsource first and second level support to script driven know-nothings in distant country, but in their enthusiasm they are more proactive and better at determining problems, not only in the code but in the UI and ancillaries (such as lens databases) than many end users. Yes, YMMV. My point is that you can't treat all the people who use the Build System and put stuff up in "home:" as being equivalent. That goes both ways. http://www.pl-enthusiast.net/2014/07/01/how-did-heartbleed-remain-undiscover... There's a point there about 'lots of pointers and indirection' which is an affliction of C and C++. Complex software or rather voluminous application code, ends up being examined by automated tools. That gets back to trust. The tools may not have the algorithms and heuristics to detect everything; we can see examples of that in the AV scanning industry. Blind spots. http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme... The 'many eyes' principle for FOSS is 'in potentia' rather than 'in esse'. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/22/2016 09:24 AM, Anton Aylward wrote:
Complex software or rather voluminous application code, ends up being examined by automated tools. That gets back to trust. The tools may not have the algorithms and heuristics to detect everything; we can see examples of that in the AV scanning industry. Blind spots.
Further on the matter of long undetected bugs, FOSS and closed system, and how testing, reviews, 'many eyes' and scanners have missed them for a long, long time: https://www.washingtonpost.com/news/the-switch/wp/2014/11/12/microsoft-just-... -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 14:26, Anton Aylward wrote:
On 09/22/2016 06:28 AM, Carlos E. R. wrote:
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok.
Suuuuuuure! The owner is the guy that (re-)coded it and inserted the trojan. He's the one guy that you can ABSOLUTELY be sure will say "yea, there's nothing wrong with my code, there's no bugs, there's no back-doors, thre's no trojans" while sniggering at you.
You understood it totally wrong. Home repos are the play ground of their owners, and typically they are not intended to install from them, unless you can contact the owner and he tells you otherwise. Some people try to build a package doing several tests, to find out why there is certain problem, and when they get it finally, they move the package to a devel or branch project, which is the one they want you to install from. Not from their home project. You would be very wrong, for instance, to install anything from my home repo, because that's the place I try to learn how to build things in OBS. On the other hand, I found fuse exfat on packman, and I installed it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/22/2016 02:25 PM, Carlos E. R. wrote:
Some people try to build a package doing several tests, to find out why there is certain problem, and when they get it finally, they move the package to a devel or branch project, which is the one they want you to install from. Not from their home project.
My experience is otherwise. There are many - exfat is just one - things where the problem is not technical, where the item in question is not going to end up in the mainstream repositories for a variety of reasons. Some of those include matters of openSuse policy that, as crops up in discussion here occasionally, some users don't agree with, that openSuse has, in the opinion of those users, 'crippled' or removed some upstream functionality, and want for any one of a number of reasons.
You would be very wrong, for instance, to install anything from my home repo, because that's the place I try to learn how to build things in OBS.
Thank you for telling us that. We now know what to avoid. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Sep 22, 2016 at 2:50 PM, Anton Aylward
On 09/22/2016 02:25 PM, Carlos E. R. wrote:
Some people try to build a package doing several tests, to find out why there is certain problem, and when they get it finally, they move the package to a devel or branch project, which is the one they want you to install from. Not from their home project.
My experience is otherwise. There are many - exfat is just one - things where the problem is not technical, where the item in question is not going to end up in the mainstream repositories for a variety of reasons. Some of those include matters of openSuse policy that, as crops up in discussion here occasionally, some users don't agree with, that openSuse has, in the opinion of those users, 'crippled' or removed some upstream functionality, and want for any one of a number of reasons.
You would be very wrong, for instance, to install anything from my home repo, because that's the place I try to learn how to build things in OBS.
Thank you for telling us that. We now know what to avoid.
Carlos is totally correct on this. If you want to depend on something in a home: project existing for any period of time or you expect it to be maintained, you need to contact the home: project owner. I break things in my home project intentionally all the time. When I believe they're ready I push my changes to a devel project. Lot of devs do that. Gr -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-23 20:14, Greg Freemyer wrote:
On Thu, Sep 22, 2016 at 2:50 PM, Anton Aylward <> wrote:
On 09/22/2016 02:25 PM, Carlos E. R. wrote:
You would be very wrong, for instance, to install anything from my home repo, because that's the place I try to learn how to build things in OBS.
Thank you for telling us that. We now know what to avoid.
Carlos is totally correct on this. If you want to depend on something in a home: project existing for any period of time or you expect it to be maintained, you need to contact the home: project owner.
I break things in my home project intentionally all the time. When I believe they're ready I push my changes to a devel project. Lot of devs do that.
Yep. It would be nice, thought, that repos have an easy to access readme file with comments about what is the intended use of the repo. And have YaST display that file at the time one adds that repository, in time to accept or cancel. Thus there would be no mistakes. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/23/2016 01:41 PM, Carlos E. R. wrote:
It would be nice, thought, that repos have an easy to access readme file with comments about what is the intended use of the repo. And have YaST display that file at the time one adds that repository, in time to accept or cancel. Thus there would be no mistakes.
Agreed, as long as the file is not named README which occurs so commonly and usually contains NOTHING but an obligatory license. What started out as a good idea has been perverted over time by mundane information. Maybe the file should be named DANGER! or BOOM!. Or maybe people should just password protect their "private" repos where they know there is dangerous or broken stuff lurking. -- After all is said and done, more is said than done.
On 2016-09-23 22:48, John Andersen wrote:
On 09/23/2016 01:41 PM, Carlos E. R. wrote:
It would be nice, thought, that repos have an easy to access readme file with comments about what is the intended use of the repo. And have YaST display that file at the time one adds that repository, in time to accept or cancel. Thus there would be no mistakes.
Agreed, as long as the file is not named README which occurs so commonly and usually contains NOTHING but an obligatory license. What started out as a good idea has been perverted over time by mundane information.
Maybe the file should be named DANGER! or BOOM!.
:-) It really doesn't matter the actual name of the file, just that zypper/yast when adding a repository automatically displays the file and ask to accept. Something like that. An option in zypper to get the description of any repo, installed or not.
Or maybe people should just password protect their "private" repos where they know there is dangerous or broken stuff lurking.
That's another possibility. But in any case, having a "description" of any repo one thinks of adding would be nice. Sometimes there is a description on the search page of openSUSE, but one doesn't always go that road. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Fri, Sep 23, 2016 at 4:48 PM, John Andersen
Or maybe people should just password protect their "private" repos where they know there is dangerous or broken stuff lurking.
The only current option in OBS is "publish" or not. Each project / sub-project gets to set a default set of values for that and each project can override it. I suppose some people only "publish" projects and packages they want the public to see, but I think that is not a well respected rule. Certainly not by me. fyi: If a package isn't published, I think the RPM has to be pulled down with something like wget, then installed locally. I don't really know because I almost always set publish to true. Greg -- Greg Freemyer Upset at the Hillary/Trump choice Don't get mad, get Evan Evan (Never Trump) McMullin for President www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2016-09-22 07:20, Per Jessen wrote:
Carlos E. R. wrote:
For 13.1 fuse-exfat comes only from home repositories.
So, I can not.
Carlos, you _can_, but you don't _want_ to. You could even download it and build it yourself, it's not that difficult.
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok.
For a very minor application like this, I would probably first try it from somebody's home repo. If I had reason to doubt it, I would build it myself or as you mentioned, get it from packman. -- Per Jessen, Zürich (16.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 15:27, Per Jessen wrote:
That's the only alternative I see, build it myself locally. But no, I can not simply install it. Not from a home repo that I do not know who made it. Home repos are not for use unless the owner tells you it is safe and ok.
For a very minor application like this, I would probably first try it from somebody's home repo. If I had reason to doubt it, I would build it myself or as you mentioned, get it from packman.
Packman is the place for this one. It has patent problems. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/21/2016 06:04 AM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too.
Where do you allow it? With my Nexus 5, I get a folder for the phone and in it a folder "store_00010001", along with a couple of text files, but nother below it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-21 14:24, James Knott wrote:
On 09/21/2016 06:04 AM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too.
Where do you allow it? With my Nexus 5, I get a folder for the phone and in it a folder "store_00010001", along with a couple of text files, but nother below it.
When I connect the cable, I get a prompt on the tablet whether to allow transfer. If no prompt, there is a drop-down menu from the top (notification) that says something like more options for the cable. Charge or transfer, three or four options. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 09/21/2016 08:49 AM, Carlos E. R. wrote:
On 09/21/2016 06:04 AM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too. Where do you allow it? With my Nexus 5, I get a folder for the phone and in it a folder "store_00010001", along with a couple of text files, but nother below it. When I connect the cable, I get a prompt on the tablet whether to allow
On 2016-09-21 14:24, James Knott wrote: transfer. If no prompt, there is a drop-down menu from the top (notification) that says something like more options for the cable. Charge or transfer, three or four options.
I get that with an older phone I no longer use. It's running Android v 2.3.6. However, I don't with my tablet running 5.1.1 or current phone 6.0.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 10:28 AM, James Knott wrote:
On 09/21/2016 08:49 AM, Carlos E. R. wrote:
On 09/21/2016 06:04 AM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too. Where do you allow it? With my Nexus 5, I get a folder for the phone and in it a folder "store_00010001", along with a couple of text files, but nother below it. When I connect the cable, I get a prompt on the tablet whether to allow
On 2016-09-21 14:24, James Knott wrote: transfer. If no prompt, there is a drop-down menu from the top (notification) that says something like more options for the cable. Charge or transfer, three or four options.
I get that with an older phone I no longer use. It's running Android v 2.3.6. However, I don't with my tablet running 5.1.1 or current phone 6.0.1
FWIW, I can access both the tablet and current phone in Windows 10. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-09-21 16:39, James Knott wrote:
On 09/21/2016 10:28 AM, James Knott wrote:
On 09/21/2016 08:49 AM, Carlos E. R. wrote:
I get that with an older phone I no longer use. It's running Android v 2.3.6. However, I don't with my tablet running 5.1.1 or current phone 6.0.1
I have a phone with A2, another with A6, a tablet with A6, and another with A4 or 5. It works with all of them, with variations.
FWIW, I can access both the tablet and current phone in Windows 10.
I haven't tried with Windows. Neither with KDE, I use XFCE. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfiuzcACgkQja8UbcUWM1zbVwD/afK/pkkUGXXAA//NGQAnypM3 Z+XUlrphgkDLPML7WOkBAJWp7Qhax5h070NvSvPvnNPKHSZjQnSJ6csY0iVzeenh =gVVV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 06:04 PM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too.
I just tried Nautilus on Tumbleweed, that seems to open them (after clicking the accept dialog on the device).
Ciao, Marcus
Thanks, Marcus, this was very helpful, as I was just working on this same problem - connecting to my phone with a cable and transferring files back and forth. I am running KDE on my smaller laptop at the moment while out of the house, and trying to transfer through dolphin just wasn't working. I would always get the error "The MTP protocol died unexpectedly" with every attempt to transfer, and even if I hit the "allow" button on my phone it would happen again. I have gnome installed on this pc also, but I didn't try to switch over to gnome. Instead, after reading this, I just opened up Nautilus and was able to transfer the files as much as I liked, without any error. Sure beats having to boot up in windows to make the transfer. Using a cable, too, is so much faster than trying to do it over wifi, the cloud, or something else. I haven't tried kde-connect yet - I know a lot of folks like that, and maybe I will see about making that work next. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | Plasma 5.4.7, Qt 5.7.0 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | KDE Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/28/2016 06:17 PM, George from the tribe wrote:
On 09/21/2016 06:04 PM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too.
I just tried Nautilus on Tumbleweed, that seems to open them (after clicking the accept dialog on the device).
Ciao, Marcus
Thanks, Marcus, this was very helpful, as I was just working on this same problem - connecting to my phone with a cable and transferring files back and forth. I am running KDE on my smaller laptop at the moment while out of the house, and trying to transfer through dolphin just wasn't working. I would always get the error "The MTP protocol died unexpectedly" with every attempt to transfer, and even if I hit the "allow" button on my phone it would happen again.
I have gnome installed on this pc also, but I didn't try to switch over to gnome. Instead, after reading this, I just opened up Nautilus and was able to transfer the files as much as I liked, without any error. Sure beats having to boot up in windows to make the transfer. Using a cable, too, is so much faster than trying to do it over wifi, the cloud, or something else. I haven't tried kde-connect yet - I know a lot of folks like that, and maybe I will see about making that work next.
On TW I just transferred many gigs of files to the internal memory card via MTP (yes, that is with a USB cable) to an Android 6.0 device with 0 problems. It instantly came up without issue in KDE as a drive in Device Notifier, and I was able to see the MicroSD card which is installed in the phone, and transfer files to that. I ejected the drive once I was done in KDE, just like any other drive. The fact that some people are having issues with MTP on mobile phones and tablets with Leap/TW make me think this could be a combination of motherboard USB controller problems and/or phone model. It also could be due to faulty hardware, a bad USB port/cable, and the list goes on. I've seen problems with Windows 10 and MTP also, even with the phone's drivers installed to the OS. Refreshing files in File Explorer via MTP (yes, they renamed Windows Explorer because they wanted to sound cool) freezes up an insane amount of time, and there are also problems with writing files via MTP on Windows 10. No such issue on Windows 7, and I had connected many devices to Win 7 machines via MTP with just 7's generic OS drivers and pretty much everything worked right out of the box. No problems refreshing files, or anything. Bottom line is though, that with TW I haven't had any issues with MTP with my Android device. I set it to File transfers on the Android device, and that's all I need to do in order to start transferring files. By the way, MTP isn't a very well-designed protocol in the first place. There are many drawbacks to it and it's not a surprise that it doesn't always work right. Just to edit a file via MTP, you have to transfer the entire file all over again. If an application on your PC wants to open a file on the remote device via MTP, it cannot do that directly. The file has to be copied over to a temporary location on the computer first. MTP operates at the filesystem layer and USB mass storage at the block layer. Windows 7 did MTP the best. Not all problems are with MTP though, some of the issue which arise are the OS's implementation of it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Sep 30, 2016 at 1:35 PM, sdm
On 09/28/2016 06:17 PM, George from the tribe wrote:
On 09/21/2016 06:04 PM, Marcus Meissner wrote:
In general we have MTP support included, but it was not working well as I tested it.
In Android 6 you need to specifically allow it on the device too.
I just tried Nautilus on Tumbleweed, that seems to open them (after clicking the accept dialog on the device).
Ciao, Marcus
Thanks, Marcus, this was very helpful, as I was just working on this same problem - connecting to my phone with a cable and transferring files back and forth. I am running KDE on my smaller laptop at the moment while out of the house, and trying to transfer through dolphin just wasn't working. I would always get the error "The MTP protocol died unexpectedly" with every attempt to transfer, and even if I hit the "allow" button on my phone it would happen again.
I have gnome installed on this pc also, but I didn't try to switch over to gnome. Instead, after reading this, I just opened up Nautilus and was able to transfer the files as much as I liked, without any error. Sure beats having to boot up in windows to make the transfer. Using a cable, too, is so much faster than trying to do it over wifi, the cloud, or something else. I haven't tried kde-connect yet - I know a lot of folks like that, and maybe I will see about making that work next.
On TW I just transferred many gigs of files to the internal memory card via MTP (yes, that is with a USB cable) to an Android 6.0 device with 0 problems. It instantly came up without issue in KDE as a drive in Device Notifier, and I was able to see the MicroSD card which is installed in the phone, and transfer files to that. I ejected the drive once I was done in KDE, just like any other drive.
The fact that some people are having issues with MTP on mobile phones and tablets with Leap/TW make me think this could be a combination of motherboard USB controller problems and/or phone model. It also could be due to faulty hardware, a bad USB port/cable, and the list goes on. I've seen problems with Windows 10 and MTP also, even with the phone's drivers installed to the OS. Refreshing files in File Explorer via MTP (yes, they renamed Windows Explorer because they wanted to sound cool) freezes up an insane amount of time, and there are also problems with writing files via MTP on Windows 10. No such issue on Windows 7, and I had connected many devices to Win 7 machines via MTP with just 7's generic OS drivers and pretty much everything worked right out of the box. No problems refreshing files, or anything.
Bottom line is though, that with TW I haven't had any issues with MTP with my Android device. I set it to File transfers on the Android device, and that's all I need to do in order to start transferring files. By the way, MTP isn't a very well-designed protocol in the first place. There are many drawbacks to it and it's not a surprise that it doesn't always work right. Just to edit a file via MTP, you have to transfer the entire file all over again. If an application on your PC wants to open a file on the remote device via MTP, it cannot do that directly. The file has to be copied over to a temporary location on the computer first. MTP operates at the filesystem layer and USB mass storage at the block layer.
Windows 7 did MTP the best. Not all problems are with MTP though, some of the issue which arise are the OS's implementation of it.
The problem is apparently with the MTP protocol itself. It is not designed to handle multiple simultaneous connections to the same device. On windows this is not a problem because one program mediates the connection. But on Linux this is generally not the case. Some phone models can kill one connection and start up another pretty gracefully, but others have more of a problem with this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On September 21, 2016 12:47:56 AM PDT, Bjoern Voigt
Unfortunately Android 6.0 (Marshmallow) has dropped USB mass storage mode for accessing the SD card. The remaining USB modes are: MTP, PTP, RNDIS, Audio Source, MIDI and charge only.
I am searching a working USB solution for file transfer. MTP works on Windows.
But I am mostly unsuccessful with MTP clients on openSUSE (Tumbleweed).
The FUSE tools "mtpfs" and "simple-mtpfs" were both unable to mount my Android 6.0 smart-phone external SD card. KDE (KIO) shows the smart-phone but is unable to access data. The only working solution on my PC is Nautilus from Gnome. But even with Nautilus I was unable to transfer a directory with some GB data without errors.
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
Any ideas?
Greetings, Björn
As soon as you break your self of this nasty habit of using cables you will have better luck. Use KDEConnect, or ES File Explorer and just move files in either direction via wifi. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-09-21 18:43, John Andersen wrote:
As soon as you break your self of this nasty habit of using cables you will have better luck.
Use KDEConnect, or ES File Explorer and just move files in either direction via wifi.
Please explain. I used ES and sftp, and it downloaded at a mere kilobytes per seconds. Hours to transfer a single movie. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlfiupkACgkQja8UbcUWM1xyDAEAiTRSlQ/ZuHRFdJaSgjZU4smZ MZJl8nRDNDvmYdPevrIA+weDmdo/OP8RPVuyVR+TVvi1QyrMyQWcLfhiENQ/5efK =k5V1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 12:43 PM, John Andersen wrote:
Use KDEConnect
How do you get the devices to pair? I can see them, but when I try to pair, I get a time out. This occurs with both my phone and tablet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Never mind. They're connected now. On 09/21/2016 01:17 PM, James Knott wrote:
Use KDEConnect How do you get the devices to pair? I can see them, but when I try to
On 09/21/2016 12:43 PM, John Andersen wrote: pair, I get a time out. This occurs with both my phone and tablet.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 01:17 PM, James Knott wrote:
Use KDEConnect How do you get the devices to pair? I can see them, but when I try to
On 09/21/2016 12:43 PM, John Andersen wrote: pair, I get a time out. This occurs with both my phone and tablet.
Curious, it works on my desktop system, but not at all on my ThinkPad. Both are running openSUSE 13.1. With the ThinkPad, it can neither see nor be seen by other devices. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 01:51 PM, James Knott wrote:
On 09/21/2016 01:17 PM, James Knott wrote:
Use KDEConnect How do you get the devices to pair? I can see them, but when I try to
On 09/21/2016 12:43 PM, John Andersen wrote: pair, I get a time out. This occurs with both my phone and tablet.
Curious, it works on my desktop system, but not at all on my ThinkPad. Both are running openSUSE 13.1. With the ThinkPad, it can neither see nor be seen by other devices.
Firewall was in the way. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/21/2016 03:47 AM, Bjoern Voigt wrote:
[...]
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
And that doesn't always work both ways ... Its worth remembering that Google has 'increased' the security relating to device access progressively with each release of Android, restricting functions that were previous possible and forcing developers to use API and fixed channels. It used to be that could, for example, download my ebooks from my PC ... MTP ... or copy them directly to the SD cards, and point the book reader/bookshelf at the directory I chose on the SD. Now that's not allowed, the bookshelf app has to import copies onto the device! In other situations yes I can make use of the SD card but I had to get updated versions of the applications, sometimes that meant changing from the free version to the pay-for version of the app. Making sure that you have the latest update is always important, but that doesn't mean things are always in the same place. Microsoft is notorious for changing the UI with each release! Android and phone companies seem to be doing a similar "Oh Shiny!" thing along the same lines. The telcos often customise further. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-09-22 14:36, Anton Aylward wrote:
On 09/21/2016 03:47 AM, Bjoern Voigt wrote:
[...]
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
And that doesn't always work both ways ...
Its worth remembering that Google has 'increased' the security relating to device access progressively with each release of Android, restricting functions that were previous possible and forcing developers to use API and fixed channels.
It used to be that could, for example, download my ebooks from my PC ... MTP ... or copy them directly to the SD cards, and point the book reader/bookshelf at the directory I chose on the SD. Now that's not allowed, the bookshelf app has to import copies onto the device!
That's what I do, copy the files. I use Ebook Droid. The problem is that it fails to discovers the books in the Documents directory, but in the left hand menu you can navigate the local directory and read anything. Or search forthe document with ES and tell to open with Ebook Droid. I have to try again with Calibre.
In other situations yes I can make use of the SD card but I had to get updated versions of the applications, sometimes that meant changing from the free version to the pay-for version of the app.
Making sure that you have the latest update is always important, but that doesn't mean things are always in the same place. Microsoft is notorious for changing the UI with each release! Android and phone companies seem to be doing a similar "Oh Shiny!" thing along the same lines. The telcos often customise further.
I find that Motorola does little customization. I like it. On tablets I do not know, but I got an Asus that does a fair amount of customization. Then there are the Nexus, pure Android, but very expensive. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Thank you for a the comments. I tried KDE Connect and I will use it for some tasks (copying files, sharing desktop notifications ...) Bjoern Voigt wrote:
But I am mostly unsuccessful with MTP clients on openSUSE (Tumbleweed).
The FUSE tools "mtpfs" and "simple-mtpfs" were both unable to mount my Android 6.0 smart-phone external SD card. KDE (KIO) shows the smart-phone but is unable to access data. The only working solution on my PC is Nautilus from Gnome. But even with Nautilus I was unable to transfer a directory with some GB data without errors.
So currently the only stable solution is to take out the SD card from smart-phone and to transfer files directly on PC.
But I will use MTP (an especially simple-mtpfs) as a replacement of the missing USB mass storage access. The following tools work (at least with my Sony smart-phone): * Nautilus * KDE * simple-mtpfs Personally I find the Fuse tool "simple-mtpfs" very useful, because I can use my smart-phone SD cards (internal and external) as file-systems. So I can use my synchronization tools like Git or Rsync: # mkdir ~/phone # simple-mtpfs ~/phone # ls ~/phone Interner Speicher sdcard1 # fusermount -u ~/phone The point is, that only one MTP tool can access the smart-phone at the same time. That's why I wasn't successful before. If simple-mtpfs prints an error like # simple-mtpfs ~/phone LIBMTP PANIC: Trying to dump the error stack of a NULL device! then probably another MTP tool accesses the smart-phone. You can kill them all: # killall -v gvfs-mtp-volume-monitor # killall -v gvfsd-mtp # killall -v mtp.so Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 14:44, Bjoern Voigt wrote:
Personally I find the Fuse tool "simple-mtpfs" very useful, because I can use my smart-phone SD cards (internal and external) as file-systems. So I can use my synchronization tools like Git or Rsync:
You can do that also with the GUI tools. Using XFCE, when connecting to an android mtp device, it appears in "/run/user/1000/gvfs/SOMEWHERE". I don't have one connected right now to verify, but the thing is that you can run normal tasks using that directory. I often use 'mc' to copy files. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2016-10-04 14:44, Bjoern Voigt wrote:
Personally I find the Fuse tool "simple-mtpfs" very useful, because I can use my smart-phone SD cards (internal and external) as file-systems. So I can use my synchronization tools like Git or Rsync: You can do that also with the GUI tools. Using XFCE, when connecting to an android mtp device, it appears in "/run/user/1000/gvfs/SOMEWHERE". I don't have one connected right now to verify, but the thing is that you can run normal tasks using that directory. I often use 'mc' to copy files. Thanks. This works for me too? Do you know, who triggers the GVFS mounting?
Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 22:23, Bjoern Voigt wrote:
Carlos E. R. wrote:
On 2016-10-04 14:44, Bjoern Voigt wrote:
Personally I find the Fuse tool "simple-mtpfs" very useful, because I can use my smart-phone SD cards (internal and external) as file-systems. So I can use my synchronization tools like Git or Rsync: You can do that also with the GUI tools. Using XFCE, when connecting to an android mtp device, it appears in "/run/user/1000/gvfs/SOMEWHERE". I don't have one connected right now to verify, but the thing is that you can run normal tasks using that directory. I often use 'mc' to copy files.
Thanks. This works for me too? Do you know, who triggers the GVFS mounting?
In my case, I open the Android device in Thunar. I assume Nautilus would do the same. I have my phone connected this instant: cer@Telcontar:~> cd /run/user/1000/gvfs/mtp\:host\=%5Busb%3A001%2C019%5D/ cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> ls Almac. interno Tarjeta SD SanDisk cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cd Tarjeta\ SD\ SanDisk/ cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk> ls Android Documentos Garbage LOST.DIR OtherMediaBackup Sounds download fmrecording DCIM FotosClasificadas Highlight Reels OldCamera Pictures WhatsupMediaBackup ebooks cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk> On KDE, I do not know. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Tue, Oct 04, 2016 at 10:31:05PM +0200, Carlos E. R. wrote:
On 2016-10-04 22:23, Bjoern Voigt wrote:
Carlos E. R. wrote:
On 2016-10-04 14:44, Bjoern Voigt wrote:
Personally I find the Fuse tool "simple-mtpfs" very useful, because I can use my smart-phone SD cards (internal and external) as file-systems. So I can use my synchronization tools like Git or Rsync: You can do that also with the GUI tools. Using XFCE, when connecting to an android mtp device, it appears in "/run/user/1000/gvfs/SOMEWHERE". I don't have one connected right now to verify, but the thing is that you can run normal tasks using that directory. I often use 'mc' to copy files.
Thanks. This works for me too? Do you know, who triggers the GVFS mounting?
In my case, I open the Android device in Thunar. I assume Nautilus would do the same.
I have my phone connected this instant:
cer@Telcontar:~> cd /run/user/1000/gvfs/mtp\:host\=%5Busb%3A001%2C019%5D/ cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> ls Almac. interno Tarjeta SD SanDisk cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D>
cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cd Tarjeta\ SD\ SanDisk/ cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk> ls Android Documentos Garbage LOST.DIR OtherMediaBackup Sounds download fmrecording DCIM FotosClasificadas Highlight Reels OldCamera Pictures WhatsupMediaBackup ebooks cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk>
This is done by a GVFS Monitoring slave btw.
On KDE, I do not know.
KDE does not have this kind of thing, it will however offer e.g. Amarok and potentially Dolphin for browsing. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-10-04 22:44, Marcus Meissner wrote:
On Tue, Oct 04, 2016 at 10:31:05PM +0200, Carlos E. R. wrote:
cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D> cd Tarjeta\ SD\ SanDisk/ cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk> ls Android Documentos Garbage LOST.DIR OtherMediaBackup Sounds download fmrecording DCIM FotosClasificadas Highlight Reels OldCamera Pictures WhatsupMediaBackup ebooks cer@Telcontar:/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C019%5D/Tarjeta SD SanDisk>
This is done by a GVFS Monitoring slave btw.
It is really handy :-)
On KDE, I do not know.
KDE does not have this kind of thing, it will however offer e.g. Amarok and potentially Dolphin for browsing.
Ah. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (14)
-
Anton Aylward -
Bjoern Voigt -
Carlos E. R. -
Dave Howorth -
George from the tribe -
Greg Freemyer -
James Knott -
John Andersen -
Knurpht - Gertjan Lettink -
Marcus Meissner -
Mathias Homann -
Per Jessen -
sdm -
Todd Rme