Doug’s Blog

Handily dispensing information to .00000001% of the world’s population

Archive for the ‘Cellphone’ Category

Bluetooth issue between Samsung Galaxy S4 and Mercedes

Tuesday, August 13th, 2013

So I got a nice sleek Samsung Galaxy S4 which is awesome! The Verizon store salesman tried to sell me on an iPhone but after I told him no thanks three times he finally let me see the Android options. I have nothing against the iPhone but just like the flexibility and options the Android gives me, plus even the sales guy admits the Galaxy is much faster than the iPhone.

But I digress… where was I? Oh, right — so the phone is AWESOME! Until I tried to pair the sonofabitch to my car, which is only 3 years old but could not do the pairing properly.

I would get the car to “see” the phone, and would enter in the PIN on the car, and the phone would pop-up and ask for the PIN, and the phone would say “paired”, but the car would eventually timeout and say it could not pair.

I tried all kinds of 4 digits PINs to see if that would make a difference, restarted the phone, removed the bluetooth entries and tried from scratch, but to no avail.

Finally I tried a single digit PIN and IT WORKED

So there you go, hope that helps someone, and now my new phone is back to AWESOME

 

SSH/SCP times out on cellular network

Wednesday, August 7th, 2013

I have a centos box I use when travelling and use an AT&T cellular USB modem on it for connectivity. I ran into an interesting problem when connecting in Las Vegas — I could get SSH sessions working fine up to a point, but when a lot of text was being outputted, the session would freeze and the connection would timeout.

This would happen when running “top”, or even if you started a “vi” session!

This looked like an issue with packet sizes, so I tried SCP’ing different file sizes and found that it would break at 1375 bytes when sending a file. After setting my MTU to 1370 the problem went away. The MTU was set to the default of 1500 prior.

So I must conclude that AT&T’s network in Las Vegas has a different network/routing setup than they use in other areas, because I have not see this problem before in California or a number of other states across the country.

For reference, the steps to fix this are:

ifconfig ppp0 mtu 1370

and then you can edit the config file, in my case “/etc/sysconfig/network-scripts/ifcfg-ppp0″ and add:

MTU=1370

to the entries there.

 

RMA HTC Incredible

Monday, October 1st, 2012

My recent (smart)phone is an Incredible-2, and it developed a dead zone on the touch screen lately. I brought it in to Verizon and was slightly disappointed to find out that it was under warranty and they would replace it for free! Disappointed because frankly that new Samsung Galaxy looks sweeeeeet as long as you ignore the kill code that people found on it.

Anyway, new free phone sounds good, so ship it I said. I got the package in the mail with nice & easy instructions and I swapped phones quickly. Kudos to Verizon for making it easy!

The one big bonus I have now is that this phone has MUCH BETTER reception than the old one! I’m not sure why, but in the past when I would drive through the “rainbow” tunnel at the end of the Golden Gate Bridge I would ALWAYS lose signal and my calls would drop. But this new phone has no issues. I can only deduce that not every phone has a nice clean routing of the antennae through the case?

So there you go, next time you get dropped calls, trade your phone in and presto! Happy days!

 

HTC Incredible 2 Tips

Monday, November 28th, 2011

I was using the Android Motorola X for over a year when the GPS function stopped working… not sure if it was because I dropped the phone or something, but when the big Black Friday shopping day came around I decided to switch to the Incredible 2 from HTC. I had used the Incredible 1 in the past and liked it, I switch to the X for the bigger screen and HDMI output.

But after a while, I missed the small form factor of the Incredible! So now I am back it it and really do like the little things HTC adds to its version of Android. Here are a few tips I can offer after taking the time to bring this new phone up to speed.

  • Install Amazon app store. I like this store, and it does a great job of keeping your apps and making them easy to re-install when you switch phones.
  • Ignore the Skype that comes w/ the phone. You can’t (easily) uninstall it, but just go to the Android marketplace and install the official Skype (NOT the one from Verizon) then you can do web calls w/ the front facing camera
  • If you use Swype (and if you don’t, you should try it), the Incredible 2 does not come with it installed. You need to visit swype.com and download the “beta” which is really better than a beta at this point.
  • Install Vlingo for voice recognition functions like calling, asking questions, etc. It’s Android’s “Siri”.

Android Version 2.3.3 Sucks Battery?

Tuesday, June 7th, 2011

I just updated my Android X to version 2.3.3 a few days ago, and now it seems my battery doesn’t last as long!

I haven’t changed any settings, I only keep the bluetooth on (no wi-fi or gps) and whereas my battery would usually last around 14+ hours with normal usage, this new version seems to die in around 8 hours.

UPDATE: I had a reason to flush my android and start from scratch, and this seemed to clear up the battery problem! Why? Who knows! Logic would indicate some app was causing a problem, but I am careful on apps and when I reinstalled everything the battery life was still good.

Android phone contacts all kafloobered

Thursday, January 20th, 2011

A few days ago, my nice Android Motorola X phone went all wonky and kafloobered up my contacts!

Yes, that’s right — kafloobered.

It mixed up names and phone numbers so that when I got a call and it said “John Smith calling” it was really someone else. So I’d answer the phone and say “Hey John,” and it would be the guy you’ve been avoiding for the past few weeks because he wants you to introduce him to your wife’s friend who really doesn’t like him… anyway, I digress.

What I had to do was to drop my sync settings in the phone, and re-sync to my exchange server and gmail account again. That fixed it!