I spent the past three days serving as an alternate juror in a federal case.
During breaks/lunch/after hours, I spent time answering email, phone messages, and Monday night and Tuesday night, I posted pacing guides to the target web site, working well into the night.
Thursday, May 26, 2011
Saturday, May 21, 2011
May 20, 2011 - of Phones and Codecs
On Friday, I got to the office and worked on general things, like answering emails, etc, until 9a. At 9a, I took Phoebe's phone to the Verizon store. Her phone has been acting weird ever since a foiled attempt to install FROYO on her Fascinate. The update downloaded, but when it tried to install, it would lock up at the "updating modem..." stage. After a random amount of time (which seemed to get longer with each subsequent attempt to update), a screen would pop up with something akin to "IP_UPDATE_FAILED" or something. In any case, the phone would revert back to OS 2.1-update 1. Well, that's not true, really. It was in some kind of limbo state - it would lose email, send messages with empty content and other weird things.
I walked into the Verizon store and told the guy that I needed the phone flashed back to its original state. I explained the update problem and that I had found a solution online but thought it was better that Verizon do it in case I messed something up. I did not want to void the warranty if things went wrong. He walked (verbally) through the steps I had explained and took the phone. He immediately started the update, as though I had not just explained that I had been down this road and it comes to a sudden dead end. So, he downloads the update and begins the install. I protest repeatedly, but to avail. He is determined that when HE does it, it will work. I realize he has no idea that I have a bit of technical knowledge, but I did my best to explain to him everything I had done and how his attempt to update will end in failure given he is doing EXACTLY what I did (even pulling the battery etc).
After about 45 minutes or so of watching the install sit frozen at the "updating modem..." screen, he tries to restart the phone in "factory reset" mode - which is what I wanted in the first place, remember. No go. The phone reboots and immediately begins the update installation. this, of course, freezes at the "updating modem..." stage. Rinse, repeat. Seriously. I think he rebooted 3 or 4 more times, trying to get it into factory mode. Nope. He pulls up our account to see about getting a new phone, but he can't touch our account because it is a government account. Lovely. He hands me the now BRICKED phone and tells me to call my rep for a new phone. Ummm, this is FRIDAY and this is my boss' phone. You want me to tell my boss that you just killed her phone and that she will be without for the weekend!? Nice.
Well, since the phone was hosed anyway, I figured I would give the steps I found online a whirl. After a bit of trial and error, I managed to get the phone in a "Downloading" mode (note image was found online at Android Forums and is property of its original owner):
In this mode, the phone is ready to accept image updates transferred from a computer. Before I go further, I want to say that there is a factory reset option. But, because the phone was bricked, it only showed a phone icon with a computer next to it and maybe an X or something. Basically, it was saying it couldn't be factory reset (because of the hosed update).
So, I put the phone into this update mode (sorry, you will have to Google that yourself. I am not responsible for what you do to your phone!), downloaded the necessary software and ROM image to get the phone back to out-of-the-box fresh, and held my breath.
After the install (which took about 10-15 minutes, I would guess), the phone rebooted and was as if I had just taken it out of the box, though it was also activated! Note: this wiped EVERYTHING off the phone (though not what was stored on the MicroSD card). So, you should backup your data apps before you try anything on your phone. Heck, you should back it up anyway. We use MyBackupPro. Others use Titanium Backup (or whatever it is called). In any case, the phone performed the first update (a minor one pushed out to all Fascinate users) and then I downloaded and installed the Froyo update. That is a LONG download. UGH. Anyway, it worked! Once that was done and installed, I reinstalled the apps from the MyBackupPro and set up the email and my boss was back in business. We "celebrated" by hitting the local Mexican place for lunch.
After lunch, I headed to Prescott to install the new TAM unit sent by Tandberg. We thought we were just getting the control unit. Instead, they sent a new codec AND control unit, already connected and ready to go. We swapped out the corresponding parts, set the IP info, and fired it up for a test call. It worked perfectly. Since the touch panel had been disconnected during the swap, I reprogrammed the audio/video settings and it all ran smoothly!
By the time we cleaned up, it was quitting time.
I walked into the Verizon store and told the guy that I needed the phone flashed back to its original state. I explained the update problem and that I had found a solution online but thought it was better that Verizon do it in case I messed something up. I did not want to void the warranty if things went wrong. He walked (verbally) through the steps I had explained and took the phone. He immediately started the update, as though I had not just explained that I had been down this road and it comes to a sudden dead end. So, he downloads the update and begins the install. I protest repeatedly, but to avail. He is determined that when HE does it, it will work. I realize he has no idea that I have a bit of technical knowledge, but I did my best to explain to him everything I had done and how his attempt to update will end in failure given he is doing EXACTLY what I did (even pulling the battery etc).
After about 45 minutes or so of watching the install sit frozen at the "updating modem..." screen, he tries to restart the phone in "factory reset" mode - which is what I wanted in the first place, remember. No go. The phone reboots and immediately begins the update installation. this, of course, freezes at the "updating modem..." stage. Rinse, repeat. Seriously. I think he rebooted 3 or 4 more times, trying to get it into factory mode. Nope. He pulls up our account to see about getting a new phone, but he can't touch our account because it is a government account. Lovely. He hands me the now BRICKED phone and tells me to call my rep for a new phone. Ummm, this is FRIDAY and this is my boss' phone. You want me to tell my boss that you just killed her phone and that she will be without for the weekend!? Nice.
Well, since the phone was hosed anyway, I figured I would give the steps I found online a whirl. After a bit of trial and error, I managed to get the phone in a "Downloading" mode (note image was found online at Android Forums and is property of its original owner):
In this mode, the phone is ready to accept image updates transferred from a computer. Before I go further, I want to say that there is a factory reset option. But, because the phone was bricked, it only showed a phone icon with a computer next to it and maybe an X or something. Basically, it was saying it couldn't be factory reset (because of the hosed update).
So, I put the phone into this update mode (sorry, you will have to Google that yourself. I am not responsible for what you do to your phone!), downloaded the necessary software and ROM image to get the phone back to out-of-the-box fresh, and held my breath.
After the install (which took about 10-15 minutes, I would guess), the phone rebooted and was as if I had just taken it out of the box, though it was also activated! Note: this wiped EVERYTHING off the phone (though not what was stored on the MicroSD card). So, you should backup your data apps before you try anything on your phone. Heck, you should back it up anyway. We use MyBackupPro. Others use Titanium Backup (or whatever it is called). In any case, the phone performed the first update (a minor one pushed out to all Fascinate users) and then I downloaded and installed the Froyo update. That is a LONG download. UGH. Anyway, it worked! Once that was done and installed, I reinstalled the apps from the MyBackupPro and set up the email and my boss was back in business. We "celebrated" by hitting the local Mexican place for lunch.
After lunch, I headed to Prescott to install the new TAM unit sent by Tandberg. We thought we were just getting the control unit. Instead, they sent a new codec AND control unit, already connected and ready to go. We swapped out the corresponding parts, set the IP info, and fired it up for a test call. It worked perfectly. Since the touch panel had been disconnected during the swap, I reprogrammed the audio/video settings and it all ran smoothly!
By the time we cleaned up, it was quitting time.
May 19, 2011
On Thursday, May 19, 2011, I met with the Director and Asst Director regarding the future of TIE (Technology Infused Education). It looks like the program will continue one way or another, which is great news for teachers in Arkansas.
I had my area tech meeting starting at 10am, so before that, I installed Impero Client on a couple workstations in the lab for a demo. Once the meeting started, I discussed the Arkansas Digital Sandbox, ArkansasIDEAS, and Arkansas iTunesU. We had a demo from Xirrus Wireless (more a presentation, really). We discussed summer workshops, summer tech workshops specifically. We also went over the changes to the tech plan inventory requirements along with AUP templates/guides provided by the state education department.
After the meeting, I worked with Blevins on their transition to Google Apps for quite some time.
Near the end of the day, I went to the Asst Director's house to work on a data transfer issue between the iPad app called "AudioNote" and the computer. Turned out to be a much easier process than I was trying to make it. Basically, AudioNote will let you copy the recorded files through iTunes' file-sharing feature. This serves to back up the data so one can free up the space on the iPad. The audio files play in Quicktime, and rumor has it they can also be converted using Audacity. If that's true, I never hit the right combo of import settings to get the audio to play in Audacity. The format, according to Quicktime, is IMA-4, 16 kHz, Mono. Audacity has only one IMA setting and it would not let me pull the file in. I tried a variety of other options and still the file came in as a screechy mess. To me, it sounded like the scene in 'Strange Brew" where Bob and Doug play a floppy disk on their record player. In any case, we found a workable solution.
I had my area tech meeting starting at 10am, so before that, I installed Impero Client on a couple workstations in the lab for a demo. Once the meeting started, I discussed the Arkansas Digital Sandbox, ArkansasIDEAS, and Arkansas iTunesU. We had a demo from Xirrus Wireless (more a presentation, really). We discussed summer workshops, summer tech workshops specifically. We also went over the changes to the tech plan inventory requirements along with AUP templates/guides provided by the state education department.
After the meeting, I worked with Blevins on their transition to Google Apps for quite some time.
Near the end of the day, I went to the Asst Director's house to work on a data transfer issue between the iPad app called "AudioNote" and the computer. Turned out to be a much easier process than I was trying to make it. Basically, AudioNote will let you copy the recorded files through iTunes' file-sharing feature. This serves to back up the data so one can free up the space on the iPad. The audio files play in Quicktime, and rumor has it they can also be converted using Audacity. If that's true, I never hit the right combo of import settings to get the audio to play in Audacity. The format, according to Quicktime, is IMA-4, 16 kHz, Mono. Audacity has only one IMA setting and it would not let me pull the file in. I tried a variety of other options and still the file came in as a screechy mess. To me, it sounded like the scene in 'Strange Brew" where Bob and Doug play a floppy disk on their record player. In any case, we found a workable solution.
Thursday, May 19, 2011
May 18, 2011
Note: I had the wrong date listed as the subject before. I was off May 17th. I went to Prescott on the 18th. Thanks. --David
Went to Prescott to work on their distance learning system (upgrade the codec and TAM). The room was not available until after lunch, so I headed to the office. Once there, I helped get folks into the APSCN program on the Macs. When the Macs fire up, our network goes to a crawl. I have to figure out if it is a Mac-thing or a Parallels-thing. Placed a call to DIS and eventually determined the problem is local (also discovered a couple other network-related issues thanks to the wonderful help I received! We have some of the best folks working for us at the state level.
While troubleshooting and waiting for phone calls from DIS, I hooked up my mini with a usb-to-serial cable to my own DL equipment to make sure everything would work once I got back to Prescott. I downloaded some additional software needed for the TAM upgrade. After the DIS call and other general email/troubleshooting, I headed back to Prescott.
The codec upgrade went smoothly. Well, once we had the FULL key codes. Turned out the printout cut off the last digit. Thank goodness for email. The codec upgraded from F2.3 to F9.0.2 (through various stages of upgrades) just fine, though very slow going even through a directly-connected CAT5 cable.
The TAM upgrade failed because I could never get the mini to talk to the TAM. After calling tech support, we determined that the TAM itself was bad. We were doing all these upgrades because the original thought was that the touch panel was bad. Looks like the tech folks on the support end missed that one until I stepped in. That is not "tooting my own horn," but rather a demonstration that over-the-phone troubleshooting sometimes just doesn't cut it.
I did get a nice compliment, though. I was told that I had gone above and beyond ("covered all the bases and then some," I was told) in trying to get things to work. That's how I am: I will exhaust every possible avenue if feasible. The downside to that is that I am wired such I will keep trying sometimes past the point of cost-effectiveness. That is, it may cost more in man-hours than the device is worth - or cost more in man-hours than it would cost to start over with a clean slate. Guess that's the techie in me.
Went to Prescott to work on their distance learning system (upgrade the codec and TAM). The room was not available until after lunch, so I headed to the office. Once there, I helped get folks into the APSCN program on the Macs. When the Macs fire up, our network goes to a crawl. I have to figure out if it is a Mac-thing or a Parallels-thing. Placed a call to DIS and eventually determined the problem is local (also discovered a couple other network-related issues thanks to the wonderful help I received! We have some of the best folks working for us at the state level.
While troubleshooting and waiting for phone calls from DIS, I hooked up my mini with a usb-to-serial cable to my own DL equipment to make sure everything would work once I got back to Prescott. I downloaded some additional software needed for the TAM upgrade. After the DIS call and other general email/troubleshooting, I headed back to Prescott.
The codec upgrade went smoothly. Well, once we had the FULL key codes. Turned out the printout cut off the last digit. Thank goodness for email. The codec upgraded from F2.3 to F9.0.2 (through various stages of upgrades) just fine, though very slow going even through a directly-connected CAT5 cable.
The TAM upgrade failed because I could never get the mini to talk to the TAM. After calling tech support, we determined that the TAM itself was bad. We were doing all these upgrades because the original thought was that the touch panel was bad. Looks like the tech folks on the support end missed that one until I stepped in. That is not "tooting my own horn," but rather a demonstration that over-the-phone troubleshooting sometimes just doesn't cut it.
I did get a nice compliment, though. I was told that I had gone above and beyond ("covered all the bases and then some," I was told) in trying to get things to work. That's how I am: I will exhaust every possible avenue if feasible. The downside to that is that I am wired such I will keep trying sometimes past the point of cost-effectiveness. That is, it may cost more in man-hours than the device is worth - or cost more in man-hours than it would cost to start over with a clean slate. Guess that's the techie in me.
Monday, May 16, 2011
The rest of Monday
Connected with DIS, ADE and AT&T via CIV (heh-heh, just wanted to throw in a couple more three-letter things there) at 10am. No one had trouble seeing or hearing our site. We got the familiar "vaseline" effect (a weird smearing of video image that disappears almost as quickly as it appears). Did some troubleshooting as follows:
* Moved the connections to different ports on same switch.
* Unplugged the switch then plugged it back in.
* Moved connections to a different switch.
* Hooked up a different codec (different brand, even)
Every item above resulted in the same effect - not working. Pixelation, smearing, etc.
Brought Max at DIS on board. After much discussion, I ran a cross-over cable directly from the codec to the router. No connection at all. Fixed crossover cable. Got connection. (call that one 'operator headspace.')
SAME RESULTS! This was both good and bad news. Why? Because it meant the problem was NOT on our network! That's the good news. The bad news: I can't fix it. I have to rely on others to get it fixed. Bad news... Good news? Max is in charge and this is his number one priority since this has been unresolved since we moved into the building in August.
After more discussion, I threw in the possibility that the router itself was the problem, even though the testors saw no real packet loss. Max said he would check the processors in the router to see if they are pegging out at maximum, then trace routes back to DIS to see where the problem was originating. We didn't have a loss problem so much as a latency issue. I guess that means a whole different set of troubleshooting steps for those involved.
I relocated the codec into the tech closet so Trish could scan target tests.
I spent the res of the day evaluating quotes for pocket cameras, creating a new user in email, answering emails and phone messages regarding various issues and questions, worked out the schedule for the area tech meeting on Thursday. I had to help a user get her email password reset - weird issue there. Her login takes her to a different page than everyone else. I am convinced she was logged in under a different IE session. She could not exit her session (something to do with COPA, I think), so I just reset her password and had her put in a new one. I also worked on a machine that had freeze.com on it. UGH, I wish users would not install things like "coupon finders" etc. I know, I can set our system to not allow such things, but I keep hoping education will win out! Pipe dream? Surely, not.
I managed to squeeze in some other things, though right now they seem to have left my brain. Let me say that having the tech offices upstairs and the labs downstairs certainly has me getting in my exercise!! Up the steps, down the steps, repeat for at least half the day.
* Moved the connections to different ports on same switch.
* Unplugged the switch then plugged it back in.
* Moved connections to a different switch.
* Hooked up a different codec (different brand, even)
Every item above resulted in the same effect - not working. Pixelation, smearing, etc.
Brought Max at DIS on board. After much discussion, I ran a cross-over cable directly from the codec to the router. No connection at all. Fixed crossover cable. Got connection. (call that one 'operator headspace.')
SAME RESULTS! This was both good and bad news. Why? Because it meant the problem was NOT on our network! That's the good news. The bad news: I can't fix it. I have to rely on others to get it fixed. Bad news... Good news? Max is in charge and this is his number one priority since this has been unresolved since we moved into the building in August.
After more discussion, I threw in the possibility that the router itself was the problem, even though the testors saw no real packet loss. Max said he would check the processors in the router to see if they are pegging out at maximum, then trace routes back to DIS to see where the problem was originating. We didn't have a loss problem so much as a latency issue. I guess that means a whole different set of troubleshooting steps for those involved.
I relocated the codec into the tech closet so Trish could scan target tests.
I spent the res of the day evaluating quotes for pocket cameras, creating a new user in email, answering emails and phone messages regarding various issues and questions, worked out the schedule for the area tech meeting on Thursday. I had to help a user get her email password reset - weird issue there. Her login takes her to a different page than everyone else. I am convinced she was logged in under a different IE session. She could not exit her session (something to do with COPA, I think), so I just reset her password and had her put in a new one. I also worked on a machine that had freeze.com on it. UGH, I wish users would not install things like "coupon finders" etc. I know, I can set our system to not allow such things, but I keep hoping education will win out! Pipe dream? Surely, not.
I managed to squeeze in some other things, though right now they seem to have left my brain. Let me say that having the tech offices upstairs and the labs downstairs certainly has me getting in my exercise!! Up the steps, down the steps, repeat for at least half the day.
Monday
Got to the office and immediately installed memory in all the macs in our lab. At ten, I am to meet over the distance learning system with tech support from little rock to figure out what our connection problems are.
Thursday, May 12, 2011
Thursday
Started the day by dropping in at the office to finish setting up the fouke early childhood computers.after that, headed to install them.
From there, headed to little rock for TIE training.
Subscribe to:
Posts (Atom)