On 01/03/2016 11:29 AM, jd1008 wrote:
On 01/02/2016 08:47 PM, Joseph Loo wrote:
On 01/02/2016 06:11 PM, jd1008 wrote:
On 01/02/2016 07:01 PM, Joe Zeff wrote:
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
Wolfgang S. Rupprecht:
>> There are "charging-only" cables that intentionally leave out the data
>> wires. These are a good idea when you don't want some random charger at
>> a coffee shop or airport to download all your pictures and other data
>> while your phone is charging.
Will W:
> You are r
On Tue, 5 Jan 2016, Wolfgang S. Rupprecht wrote:
Date: Tue, 05 Jan 2016 14:41:55 -0800
From: Wolfgang S. Rupprecht
Reply-To: Community support for Fedora users
To: users@lists.fedoraproject.org
Subject: Re: Cannot access my phone storage from fc22
There are "charging-only" c
Will W writes:
> On Tue, 5 Jan 2016, Tim wrote:
>
>> Date: Tue, 05 Jan 2016 16:45:18 +1030
>> From: Tim
>> Reply-To: Community support for Fedora users
>> To: users@lists.fedoraproject.org
>> Subject: Re: Cannot access my phone storage from fc22
>>
On Tue, 5 Jan 2016, Tim wrote:
Date: Tue, 05 Jan 2016 16:45:18 +1030
From: Tim
Reply-To: Community support for Fedora users
To: users@lists.fedoraproject.org
Subject: Re: Cannot access my phone storage from fc22
Allegedly, on or about 04 January 2016, Will W sent:
I know a lot of people
Allegedly, on or about 04 January 2016, Will W sent:
> I know a lot of people mentioned about the cable, the only one that
> seems to work for me is the cable that came with the phone.
With something like that, it makes me wonder whether there's a problem
with the contacts in the phone's socket,
Hi,
I know a lot of people mentioned about the cable, the only one that seems to
work for me is the cable that came with the phone.
I had this same issue before. Keep trying cables until I found one that worked.
It is a pain, but it happened in windows too with my father.
Regards,
Will W.
ht
On 01/02/2016 08:47 PM, Joseph Loo wrote:
On 01/02/2016 06:11 PM, jd1008 wrote:
On 01/02/2016 07:01 PM, Joe Zeff wrote:
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and l
On 01/02/2016 06:11 PM, jd1008 wrote:
>
>
> On 01/02/2016 07:01 PM, Joe Zeff wrote:
>> On 01/02/2016 05:56 PM, jd1008 wrote:
>>> Well, these are the same cables I used on my previous phones
>>> and they worked extremely well.
>>> My phone is less than 2 years old, and looks like brand new.
>
On 01/02/2016 07:01 PM, Joe Zeff wrote:
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a differen
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cab
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a different computer, or
borrow a cable to see what
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cab
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cable.
Other than that, I've got nothing.
Good lu
On 01/02/2016 04:03 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
On 01/02/2016 01:12 PM, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
Android is 4.4.2 (nothing newer is available for m
On 01/02/2016 03:58 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debu
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
>
> On 01/02/2016 01:12 PM, jd1008 wrote:
> >On 12/30/2015 12:13 PM, Jon LaBadie wrote:
> >>On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
> >>>
> >>>Android is 4.4.2 (nothing newer is available for my phone.
> >>>Developer optio
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
>
> On 12/30/2015 12:13 PM, Jon LaBadie wrote:
> >On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
> >>Android is 4.4.2 (nothing newer is available for my phone.
> >>Developer option set. usb debugging enabled.
> >>
> >>yet, when I
On 01/02/2016 01:12 PM, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to d
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon
$ ps -ef | grep adb
jd 19967
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
>
> $ adb devices
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
>
> ** daemon still not running
> error: cannot connect to daemon
>
> $ ps -ef | grep adb
> jd 19967 1 0 19:06 pts/300
On 12/30/2015 04:58 AM, Tim wrote:
Allegedly, on or about 29 December 2015, jd1008 sent:
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debugging enabled.
yet, when I plug my phone to usb on laptop,
laptop does not mount anything, nor does any icon
appear o
Allegedly, on or about 29 December 2015, jd1008 sent:
> Android is 4.4.2 (nothing newer is available for my phone.
> Developer option set. usb debugging enabled.
>
> yet, when I plug my phone to usb on laptop,
> laptop does not mount anything, nor does any icon
> appear on the panel as a result of
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon
$ ps -ef | grep adb
jd 19967 1 0 19:06 pts/300:00:00 adb -P 5037 fork-server
server
jd 19983 7405 0 19:09 pts/3
24 matches
Mail list logo
