[John Thomson] usually keeps his phone on vibrate when it’s in his pocket, and he often forgets to turn the ringer back on when setting it down to charge. This typically results in a bunch of missed calls in the meantime, so he had to devise a way to counteract his forgetfulness.

You might remember [John] from the Santa-pede contest we held last December. He wanted to try his hand at yet another competition, the Avnet Dog Days of Summer contest, so he scrambled to come up with a quick fix for his situation. He concocted a simple circuit based on [ChaN’s] design for a “Simple SD Audio Player with an 8-pin IC” that would alert him to incoming calls, even when his phone was on vibrate.

[John] used an ATtiny85, just as [ChaN] did, adding a speaker for sound output and a piezo sensor to detect his phone’s vibrations. When the piezo senses a bit of motion, the audio player kicks in, blaring a series of sounds that are sure to get [John’s] attention.

While he was organizing a party, [Mike Seese] hit upon the idea of chatroom that would operate over SMS. Not being content with the ‘reply all’ function, [Mike] built a Group Messaging Service that runs on his home server.

The chat room is initiated by sending a text to a server. Your friends then reply, and the chatroom is then opened. The project was written in C++, and [Mike] put everything on github for your perusal. The software does use libraries from /n software’s IP*Works, but if you have any trouble obtaining those libraries feel free to drop [Mike] a line.

The great thing about this project is the fact that it’s platform independent – as long as a phone can do SMS, it’ll work. Seems like a great thing for those of us still using the old Nokia ‘bar’ phones. An SMS chatroom has been done before but this is the first time we’ve seen a build that will run off your server, and not internet-based services.

While it may not be the best idea for people without unlimited texts on their phone plan, it’s a really great idea and we’re wondering why something like this isn’t available via Google Voice.

Hackaday forum member [Dan Fruzzetti] wrote in to share a simple, yet useful hack he built just the other day. He and his wife both have Evo 4G smartphones and they were pretty disappointed in the lack of portable charging solutions available.

Instead of buying something and modifying it to his needs, [Dan] decided to build a quick and dirty charger instead. His ghetto-mintyboost was built into a cheap project box he found at Radio Shack, which is stocked with a set of four D-cell batteries. The batteries were wired in series and connected to a pair of salvaged USB ports mounted on a small piece of protoboard.

Knowing that most portable devices get 5.7v from their chargers already, he was not worried about hooking his phones straight into the 6v battery pack he built. He says that the phones actually charge pretty quickly, and that he estimates he should be able to get about 50 charges out of the box before he needs to swap the batteries.

This is not a complex hack by any means. It is quick & dirty, solves an annoying problem, and it’s dead simple to build. That’s exactly why we like it.

That title’s not really fair to [Evan], but he did write a cellphone tetris game that causes your handset to automatically telephone him if you win. He’s using two applications that we’re not very familiar with, Twilio and Tornado. The former handles control input from the cellphone via their simple API. The latter is a web server and web framework that runs the actual game.

If you’re interested in how he put the two together you can poke around in the code. If you really don’t care about how it is done, you might just want to win the game, automatically giving [Evan] a call, running up his wireless bill in the process.

Help us add some value to this article by leaving a comment.  We’d like to know how Twilio compares to Google Voice which doesn’t seem to have a published API (but there is some work in that area). We also think web-based cell phone interactivity, already popular in hacks, is just beginning to build some steam. What are the tools you use to make cellphone interfaces easier and quicker to implement?

Hackaday alum [Will O'Brien] has been doing some cellphone integration work. He recently picked up some Motorola c168i cellphones from eBay. It turns out there is a serial port that uses TTL communication with a standard head-phone jack as an interface. [Will] soldered up a connector and used a USB to FTDI cable to interface with the phone. To his surprise he was able to read off the stored text messages even though they were PIN protected in the phone’s operating system. The messages on these units were trivial but this is another example of the importance of clearing your data before discarding your devices.

[Karsten Nohl], with a group of security researchers has broken the A5/1 Stream Cipher behind GSM. Their project web site discusses their work and provides slides(pdf) presented at 26C3. A5/1 has had known vulnerabilities for some time now and is scheduled to be phased out for the newer KASUMI or A5/3 block cipher. This should be an interesting time in the cell phone business.

Thanks to [Tyco] and [MashupMark] for pointing us to this story.

When we first saw Vodaphone’s ringtone commercial where 1000 cell phones perform a section of the William Tell overture, we just assumed it was some slick video editing, not to be taken seriously. Apparently, we were wrong. They actually did this. They actually sent text messages to all the phones in correct timing to play the music.  In the video after the break, you can see some details on how they pulled it off. They had to perform this during non peak usage hours to ensure that all their texts went through. We think this project is pretty impressive. Actually, we still don’t know how they pulled it off, we can’t seem to predict how long a text message will take to reach its destination with any kind of reproducible accuracy.

[via Makezine]

[Vlad-Andre] used some of his free time to build an alti-variometer. He does some para-gliding near restricted air space and wanted a backup altitude warning that would help keep him below the mandated altitude. His solution uses the SparkFun Weather Board in conjunction with their BlueSMiRF dongle to measure altitude and transmit it via Bluetooth. From there, he wrote a program to grab the transmitted data with his cell phone and display the information. His application also has the ability to set altitude warnings and log changes over time.

Using this system he is able to get altitude data with 3.5 inch accuracy. Because the capture application is written in Java it should be easy enough to make this work on other cell phone models. The project is clean and works well but we estimate the cost of the parts to be between $250-300, making it out of reach for those who don’t have a specific need for these types of measurements. This is especially true for paragliders who have much less expensive options available to them.
[Thanks Carl-Emil]

No matter how grumpy you are in the morning, this video should make you smile. This is one of the jobs many of us dream of. Take a tour around Nokia’s product testing facility with Engadget. Watch in the video as phones are squashed, pinched, smacked, baked, shaken, dialed, slid, opened, and closed repeatedly. Sure, we don’t get to see any of them obliterated, but it sure is fun to see those machines at work. Each one of these tests will be run until the phones eventually come apart or cease to function. Too bad they didn’t show us that part of it.

We’re starting to think that phone numbers are deprecated; it may be time to integrate how we connect telephones with the new digital millennium. To get a firm grasp on this topic it is important to take a look at the reason we started using phone numbers, why we still use them, and the why’s and how’s of transitioning to a new system.

History of phone numbers

Telephone numbers started out as a way of physically addressing a telephone extension. Whether connected by an operator at a switchboard or through a magnetic exchange, each number corresponded to the hardware switch that connected the handset you were trying to ring. This originally started with named exchanges such as Pennsylvania-6-5000. The geographic location of the extension was  shown in the name and this system gradually transitioned over to area codes and prefixes.

Continued usage

The proliferation of cell phones means that numbers are no longer tied to a physical location but are routed to the nearest tower to which each wireless phone is currently connected. So why have we continued to use telephone numbers? Backwards compatibility is paramount. Cell phones overtook land lines years ago but there are still millions of people connected to the telephone companies’ wired networks. Most of the phones used on these land lines rely on the touch tone system to function. Even the advent of Voice over Internet Protocol implements the same system of connecting calls by dialing a number.

What works better than phone numbers?

How many different phone numbers does your family have? Many households have a home phone, a cell phone for each family member, and a work phone for each adult. What if all of these numbers were addressed similarly to how the Domain Name System works for internet addresses? Something like this:

phone://famiy.johndoe2155.voice/john_at_home

phone://family.johndoe2155.voice/jane_at_home

phone://www.your_company’s_domain.com/customer_service

This can be accomplished in the near future. All cell phones and many land line phones already have the ability to store numbers so that you only have to enter them once. Cell phones can already input web-style addresses and a firmware upgrade would allow for a new system of addressing and storing voice connection information. Service providers like Comcast and Charter are already providing phone service that utilizes VOIP, paving the way for dialing from your computer. For legacy hardware an inexpensive interface box similar to the digital cable converter boxes could be implemented. The new box would have a keyboard and character LCD and be rolled out in the same way that caller ID boxes were.

Conclusion

No one wants to change their telephone number and be in the position of trying to inform everyone who might ever call them. This is why laws were enacted to allow you to keep your telephone number if you change carriers. If each family owned their “voice domain”, changing carriers, cities, or even countries would be as simple as editing the domain registration. Transitioning to a new system of dynamically addressed telephone extensions is the next logical step in voice communications. Although it would be a change for billions of people, it is possible and worth taking a look at.

[photo credit Projekt Runeberg]

Some grad students at Duke University have been working on a new tool for cell phones equipped with accellerometers. The software called  Phonepoint Pen, allows you to write with your phone in the air. Though we don’t find the applications they mention very practical, we could see this being very nice for application navigation. If you could program a 3 dimentional gesture to load certain apps, that would be nice.

Sometimes you find yourself thinking “this cell phone is far to compact and unobtrusive.” [Trotmaster] had this thought and did something about it. Ok, well actually he’s trying to have some fun and build a glove phone, inspector gadget style.  There really doesn’t seem to be a good reason to do this other than it would be cool, so we’ll proceed on those grounds. He has disassembled the phone and extended all the buttons. When wearing the glove, you can dial by pressing the finger tip buttons with your thumb. The screen is located on the back of the hand and can be lifted and rotated for easy viewing. Can anyone think of an application where this would be a beneficial layout, assuming you refined it a bit?

[via instructables]

Sometimes you absolutely need to keep your phone a secret. You know, like when you’re on spy missions. The goons at the door will always frisk you, but they never check under your shoe, right? [mikeyberman] shows us how to make our own Maxwell Smart style shoe phone. All you need is to dig a giant hole in your shoe sole and cram a cell phone in there. Will it get ruined by water? Probably. Will you look like a goon trying to talk on it? Definitely. Can you make it through airport security? Try it and let us know.

If you can get through the cell phone text speak, you’ll probably enjoy this cool tutorial on how to build a cell phone controlled robot. This bot decodes the key tones, similar to the automated phone systems we’ve all experienced. It uses a chip called a MT8870 DTMF decoder to translate the signal for the Atmega 16 controller. The circuit diagram is pretty hard to read, maybe we missed a downloadable one somewhere. The source code is available.

It would be nice to get some feedback from the robot, so you aren’t driving it completely blind. This is similar to the Lego cell phone rover that we showed you before.  Next, he should make it recognize voice commands.

Like everybody, we sometimes get a little frustrated with our cellphones. Probably one of the most annoying things is when we drop our phones once and they stop working. At Nokia’s hardware damage labs in San Diego, they physically test their phones for extreme uses. They test things like flip tension, water resistance, and even UV resistance. Recently, the folks over at MobileCrunch were given a tour of these labs and were nice enough to post an in-depth article about what they saw. In addition to the impact testing video above, there are many more videos posted that demonstrate the tests they perform.