Now, several minutes after turning on Bluetooth on the computer, it was
finally visible from the phone.

So from the phone I tried sending a file, and I got the screen (on the phone) 
that I attached.
It said: "Type the pairing code then press Return or Enter". (note: "the" 
pairing code. What pairing code? If I am supposed to type it on the computer, 
which "press return or enter" seems to suggest, then it should show up on the 
phone - or viceversa)

So on the computer some prompt was supposed to show up, but it didn't. A
small padlock showed up in the bluetooth icon on the computer, but there
was no prompt for a code anywhere, nor did it show up by clicking on the
bluetooth icon.

After a while the operation timed out from the phone.

Then I tried again.
This time, at the prompt "type the pairing code then press Return or Enter" 
(again the one in the screenshot) I tapped on "pair". (the prompt is quite 
ambiguous: am I supposed to type the code, which I can't possibly know, in 
which case the "pair" button shouldn't be necessary, or should I press "pair" 
and *then* I'll be shown the code on the phone and prompted to insert it on the 
computer, in which case the message is confusing because it's telling me to 
enter it now??)
So I tapped on "pair", and... The file was sent succesfully!! No code showed up 
anywhere and I didn't have to insert it anywhere.
Of course I had paired these two particular devices before, literally years ago 
(and I'm not abusing the word "literally").

The UI of the whole process is a fucking mess on both sides, both Ubuntu
AND Android. There are a bunch of bugs on both sides. Sharing files via
bluetooth is a hell.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661

Title:
  "Receive files over bluetooth" randomly stops working - plus setting
  should be available under BlueTooth settings

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I often send image files via bluetooth from my android phone to my
  ubuntu PC.

  It worked fine until yesterday, but now I systematically get "the
  remote bluetooth device rejected the request".

  Nothing has changed in the way I transfer files and I'm trying from
  the very same phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic 3.0.0-16.29
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
  Uname: Linux 3.0.0-16-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  teo       32650 F.... pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
     Mixer name : 'Realtek ALC660-VD'
     Components : 'HDA:10ec0660,10430000,00100001 
HDA:10573055,10431316,00100700'
     Controls      : 25
     Simple ctrls  : 16
  Date: Sun Mar 18 17:55:36 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic N/A
   linux-backports-modules-3.0.0-16-generic  N/A
   linux-firmware                            1.60.1
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to