The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Lest you ask, my dance club client is looking at setting these up for the "couches" to communicate with the bill acceptor, credit card reader, and other hardware that hangs off each device. So I get to play with some nifty hardware and help him write the interface software -- web services, etc. We're looking at either Ruby or node.js (rather than native C++) for handling all the device I/O and calls to the club's server. Should be quite the learning curve!
Got one a month or so ago and the are awesome, a couple of tips;
1) Use a power supply with 2A, it's very picky. The Wal-wart they offer 5V 2A for $9..95 is a good deal.
2) It's a little picky about uSD I used a Transend 8GB and it didn't work had to go out and get a Sans.
Good luck and have fun, they are a lot of fun!
Along with Antimatter and Dark Matter they've discovered the existence of Doesn't Matter which appears to have no effect on the universe whatsoever!
Rich Tennant 5th Wave
My wife has a Samsung Galaxy S3 with an old version of Android installed.
It is from a Spanish phone company that looks like doesn't want to update the OS for that phone...
I've seen there are methods like the one CyanogenMod is offering to install a new OS version there.
It looks like all are advantages... but... have you done that? should I have something clear before starting doing that? any advice or recommendation? A good tool to be able to make a full backup and restore the phone to the backup if something fails?
There's plenty of information in the Internet, but too much information is like no information at all...
If there is not an update available for your phone, Cyanogen is a great option. I have run it on an old (shipped with 2.3) HTC Thunderboldt, an HP Touch pad (still am there), and recently put it on an HTC One. I have not put it on an S3 or S4, but the steps are similar.
The best place I have found for each of them is http://forum.xda-developers.com/[^] to get the most current and complete steps. They are also VERY good at answering questions there when you may have made a slight mistake.
To do it:
0) Find the forum for your device
1) Find the root/ROM section for your device
2) Read the instructions for doing it from start to finish
3) download the recommended files (Biggest choice is ROM Manager, both Clockwork Mod and TWRP are really good. I just started using TWRP and think I like it better.)
4) Read the instructions for doing it from start to finish
5) Read them again just to be safe
6) Start with step one and move through them sequentially.
7) Only clear/wipe when directed
8) Only reboot when directed
It is really not very difficult once you have done it once, but a mistake can then cost you a LOT of time to figure out and get fixed. (My son grabbed the wrong version of clockwork mod because he didn't read ALL of the instructions before starting and lost access to the SDCard portion of the memory for about 4 days on an HP Touchpad.) It seems that it is much less likely that you can brick a device permanently than it used to be.
Good luck! The custom ROMs take up much less space and give you much better access to your device. I was able to run WireShark on mine the other day to solve an issue that arose.
t is from a Spanish phone company that looks like doesn't want to update the OS for that phone...
If you ever bring Kies to work, you can upgrade the android OS independently from the cell phone company layer. But this requires Kies to work, which I have never ever managed to do (Samsung S1, Samsung S3, Samsung Galaxy Tab 10.1).
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
How old is your PC? Are you sure it isn't entering it's teenage years?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
Well, well, my almost 5-year old PC is far from dead. I mean what happen to upgrade? A little more RAM, new video-card and some HDD and the PC turned from old-aged to modern usable PC, although it is not a gaming beast.
Management spent a lot more work producing the product in 9 months than you have maintaining it in the year after release. It's understandable management feels proprietary about the model produced. And all you did is provide half the initial raw materials needed to build it. (Oops, that's an assumption, a good one I hope)
Plus, I get blamed for any bugs in the functionality
If the bugs can be traced to your design input, that's totally reasonable. If it can clearly be traced back to management's input, then you clearly have to apologize for your mistake and ask for help in correcting the design. If you play it right, you might get management to help with GC too.
Different message. Rick's issue was the debugged could not evaluate the expressions. In my instance the debugger simply refused to. I'm sure it could evaluate it, but cleary I said something to it - maybe a couple of weeks ago - that it didn't like and has chosen this time to throw out a little passive aggression.
(I actually just loved the fact that the error was "refused to evaluate". Not "could not", or "was unable to" but an active refusal. I want to meet the dev who wrote that and buy him a beer)
FYI I'm in the process of reading very boring, but useful to implement documentation and refusing to do what is asked has to be worded in non-aggressive language, so this doesn't meet our company's standard for error messages. Wonder what % of our employees this applies to has actually read the entire thing.
Fortunately, this is not the result of a machine's newly discovered free will. It's just the normal inability of a software developer to generate both a meaningful error message with debugging info for logging and an understandable message for the user at the same time.
Once I had to fix a web application that sent me hundreds of mails when it had a bad day, telling me that an error had occured. No information about the error, or about the place where it happened, or (god forbid) any secret information about the user's parameters so that the error could actually be reproduced.