HanishKVC’s General Blog zone

May 17, 2007

BeYOND stupidity SONY, do LOOK = Come to your senses, allow Indian PS3 Owners access to Playstation Store +++, Link India PS site from global

Filed under: gaming,General,India,life,protest,PS3,Sony,technology — hanishkvc @ 8:39 pm

Hi Sony / Sony India if you are listening.

  1. At first you charge us a lot for your PS3 (among the highest rates in the world for PS3)[I mind(50-50), luckily I got it when coming from US],
  2. next you give us a very small set of Games for PS3 [I mind it very much, its bad],
  3. On top you don’t allow us access to Playstation Store[I mind it very very much, its daytime robbery],

WHAT LOGIC ?e?IS THIS.

Please look BeYOND your foolish/senseless/stupid attitude and logic and correct these mistakes. Atleast if you can’t fix <1>(cost of PS3) above, then atleast because Indians are paying you a lot more compared to many other regions atleast fix <2> (game library) and <3> (PSN store++) above.

Similarly in future once Playstation HOME debuts don’t repeat the same mistakes. Let Indians participate in it from Day one.

Also I am also a Sony PSP owner in India and even Sonys’ own stores don’t have good library of games for it also.

Last but not the least why DON’T we have a link to India PS3/PS2/PSP site from playstion.com / asia.playstation.com.

Come on wake up and be a good CE company and be good to your customers.

Note: I am a really frustrated Sony Customer in India with a Sony Camera, PSP, PS3. So when it came the time to buy a HDTV for my PS3 I went with Samsung. Hint Hint …..

Note: Only reason I went with PS3 instead of XBox360 inspite of all your stupidities was your support for Linux and Cell, but that doesn’t mean you can take me for a_ride/granted for ever.
Note: I am posting it in some not directly related categories also, so that hopefully I get the message across to Sony. Sorry for that.

Advertisements

May 16, 2007

Short and simple commandline Bluetooth in any new Linux distros

Filed under: bluetooth,debian,linux,Nokia,OpenSource,technology — hanishkvc @ 7:22 pm

Yesterday I had to transfer some files/S60 Opensource programs to my Nokia 6630 mobile and so picked up my usb bluetooth dongle (after ages) and connected to my Linux PC to achieve the same. I had forgotten the things which I had done long time back to get it working (Also one of these days I have to find out where I had noted those steps down).

Either way I started by remembering that I have to try and use obex logic to put those files on the mobile (now come on remembering that isn’t that difficult;-). Soon I remembered most of the things to do through aptitude search/show bluetooth/bluetooth packages, dpkg -L <bluetooth related packages>, some trail_N_error and net searching (googling).

But to my horror what ever I do the connection wouldn’t establish has the bluetooth stack on the PC wasn’t pickup the PIN which I just configured on the PC. After some more rtfm and dpkg -L bluez-utils and cross verification on the bluez website I realised that the way the PIN to be used is specified to the bluetooth stack has changed on the PC and now instead of the pin_handler it uses a dbus based passkey handler. So I compiled the given passkey_agent.c and resolved it. And thus could achieve the file transfer without going into windows thou with some deficit of sleep 😉

So here are the commands one could use to work with bluetooth devices in a linux based pc =>

hciconfig
– Gives info about the bluetooth hci on your pc
– Ensure the device is up and running and has required scan modes
– hcitool dev should also give some of this info

hcitool inq and hcitool scan
– Gives info about or rather identifies nearby bluetooth devices

hcitool info <BTAddr>
– Get info about remote bluetooth device

l2ping <BTAddr>
– One way to see if we can communicate with a remote bluetooth device

sdptool browse <BTAddr> or sdptool records <BTAddr>
– Gives info about the services provided by a remote bluetooth device

obexftp –nopath –noconn –uuid none –bluetooth <BTAddr> –channel <OPUSHChann
elNo> –put <FileToPut>
– Allows one to send file without specifying the pin on the remote device side
– The OPush channel number for device is got from sdptool above

passkey-agent –default <Pin>
– Pin specified here is what the remote BT device should provide
or its user enter on that device when requested.

obexftp -b <BTAddr> -v -p <FileToPut>
– Allows one to put a file onto the specified BT device
– obexftp could also be used to get or list the files on the BT device
– also allows one to identify a nearby BT device by just giving -b option

obexpushd
– Allows one to recieve files sent from a bluetooth device.
– Depending on who started it, the recieved files will be stored in the corresponding home directory

Note: The old style pin_handler doesn’t work with latest bluez, you require a
dbus based passkey handler and there is one provided by default by bluez-utils
called passkey-agent
Hope this helps anyone who is trying to use bluetooth devices from the commandline on a new linux distro, as well as it would help me to remember for the future for my own use.

Create a free website or blog at WordPress.com.