Tag Archives: Apathy

Cell Phone Subsidizing lives on!!!

March 27, 2016LifeApathy, pissed consumer, Review, Verizonjrdalrymple

I suspect there are a lot of people in the world who are disappointed by the disappearance of cell phone subsidizing. “WHAT, I HAVE TO PAY FOR MY PHONE NOW?” At the end of the day it kind of all comes out in the wash for me, I never did contracts anyway because I simply don’t like being tied to a phone company, on principle, and dating back to the days of being in Alaska Communication’s noose.

For the people who miss those subsidies, I have great news. Not only are they back, but they’re back with a vengeance.

Let’s rewind to the beginning-ish of March. I’ve been with Verizon ever since I moved to MN. I still maintain my AT&T line and number, but just for aesthetic reasons. The only phone I use is my Verizon phone. I also recently got into the smart watch market, albeit the cheap way with a secondhand Moto 360. I won’t say I’m elated with the smart watch, but now that I’ve had it for awhile I definitely feel naked without it. The problem has been that the constant jabber between smart watch and smart phone has caused my aging Motorola phone to have less than acceptable battery life. That’s fine, the Samsung Galaxy S7 was just announced and it’s almost an adequate flagship handset, so I’ll just spend a few bucks and we’ll fix our battery problem and take an upgrade at the same time.

I go into the Verizon store at MOA. Overall the service was satisfactory (personable that is), although it definitely took longer than I wanted to achieve the goal I was seeking. I was not necessarily planning on walking out of there with anything new, the phone was still a pre-order and I just didn’t have the watch in mind. The deal is though – buy yourself a Galaxy S7 and get this sweet deal on the Samsung Gear S2. The sales guy went into adequate detail regarding Tizen, but he was also wearing one and was able to show me the benefits of having a 3g watch. I figured what the F, I’ll try it. What the Verizon salesman was not particularly clear on was that in order to get this sweet deal I was going back to good ol’ subsidized price modeling. So here’s what the *deal* looks like:

The points to take away:

1) The device “only costs me $5.00/mo” according to Verizon staff.

2) The great deal is $150 (43%) off of full retail cost of $350.

Regarding point 1, only $5.00 a month sounds great, but the reality is that it’s over twice that. If you look at surcharges that are in their control combined with governmental charges outside of their control, it’s actually more than double of the “only $5.00 a month.” I called today to talk about canceling it – the early cancellation fee is $175. Less than paying the $11.37 for the term of the contract, but not by a lot.

Regarding point 2, you used to be able to get iPhones valued at $500+ free right? Or is that me imagining things? Either way, it was way better than paying 57% of full retail.

I don’t like being under contract, I don’t like sneaky sales practices, and I don’t like being taken to the cleaners. When the math is done I will be paying (at best) $404.19 to own this thing for a month. The best I can hope for in the resale market is about $300. This month Verizon not only took their normal $150 out of my pocket for the services they provide, but they’re also hosing me for $100 additional that I’ll see no benefit from.

So thanks assholes at Verizon. I was recently shopping around because T-Mobile claims their network is fixed. The only reason I didn’t jump ship is because I honestly had very few complaints about Verizon besides the cost. Fact is they’re all too expensive though, and T-Mobile doesn’t give me any corporate discount on service, so continuing with big red just made sense. I have a new complaint, and after tomorrow my contract with you will be terminated.

As an aside – if you’re considering going from a proper Android Wear device to a Tizen based device, save your money and your frustration. Tizen is garbage, and because I see no looming Wear support coming for the device you’ll find mine on eBay as soon as I’m clear of the bounty on the device, in case you don’t trust my advice…

Dell Bluetooth 365 on Windows 10

August 10, 2015Motorized junk, Technology junkApathy, Bluetooth, HowTo, JetSki, Latitude E4200, Windows 10jrdalrymple

I’m desperately waiting for my parts from Short Block Technologies so that I can get going on the 750sx project. The good news is their ridiculously slow service/shipping gave me all of last weekend to try to get the Bluetooth working properly on my trusty old Latitude E4200. I was at the verge of just buying a new laptop, but I really, really, really hate spending money on portable computers in 2015. I hated it in 2010, I wish they’d just die already. To make matters worse my mom let me borrow her modern Latitude 7350 – it made me beyond the shadow of a doubt not want to buy anything new.

Thus I spent no doubt a good 4 hours or so troubleshooting/uninstalling/fiddling/thissing/thatting the Bluetooth device and software on my trusty old beast. There are a few forum posts indicating this and that, try Lenovo software, try Broadcom’s update, try old drivers in compatibility mode. It all sucked.

Backing up a step it’s worth outlining the symptoms – after the Win10 upgrade both my Microsoft Sculpt Bluetooth mouse and my Microsoft Curve Bluetooth keyboard worked somewhat, but the features weren’t right. I unpaired and discovered no ability to re-pair.

All of my searching led me here – a forum post more about Windows 8, but similar problem. The solution is to use some older Lenovo software.

No compatibility, no BS, it just worked. I did have to unpair then re-pair when finished. Also at the end of the install it did indicate failure, but that is apparently not the case.

Quick link: http://tinyurl.com/b8fptwr

Now back to being angry about my missing boat parts.

B2B Credit Nonesense

January 22, 2015Technology junkApathy, NetApp, SANjrdalrymple

Recently in my workplace we made some pretty serious gear shifts with regard to storage. Being vendor agnostic as I always strive to be I will say that our go-to fabric vendor changed as well as our go-to disk vendor. Since the change things work, but the more I dig into what’s going on under the hood, the more I feel like I’m living in a house of cards.

The change came as the result of 2 companies merging and coalescing on one hardware platform for all systems. Going in with the blinders on I was absolutely indifferent to the fabric change since I’ve worked with the new vendor’s gear in the past and took a liking to it, and as for the storage vendor they had a clean slate to start with so I had no reservations there either. In erecting our new gear some months ago we worked with staff from the company we merged with so as to build like for like environments to ease the merging environments down the road. One thing that made me quite suspect of either the gear we were installing or the practices of the personnel in the other organization was their suggestion to modify b2b credits on the storage side switch ports. Scratching my head I said that I prefer to leave port settings default and only make adjustments AFTER we’ve seen a symptom arise that suggests a need to deviate from default.

Fast forward about 3 quarters and we have 3 new arrays from ACME Storage, 2 directors and 6 pizza box FC switches from ACME SAN. Everything *works* but now that I’ve had time to breath I’m finding things in our environment I don’t like. Let’s compare counters from the busiest ISL links (primaries for a MetroCluster FCVI), before and after. Note that the before counters were last reset about 18 months prior to the dismantling of the ISL while the counters for the new ISL port are reset daily by a script run by our peers:

        Frames Transmitted   B2B Credit Zero Errors   B2BC0 Percentage
Old     2657260246611        2377700058               .089%
New     2851542621           1306395534               45.8%

Both of these ISLs were configured with the staff from the switch manufacturer onsite and configured per best practices published by NetApp. As a matter of fact on the new configuration the B2B credit allocation was padded above and beyond the 150% padding that NetApp recommends. This is the ugliest counter to look at. Other ports have seen similar increases in errors, and seemingly for no good reason. Our production EMR has 8 host ports allocated for both the active and standby nodes, and the standby node is truly standby. Even still I’m seeing many b2b credit zero errors every second on those host ports, not the storage ports.

Mostly this is a pointless diatribe about changes I’m seeing. I’m truly concerned that I’m going to get to start micro-managing my FC ports in order to maintain performance and keep error counters low. If I reach that point I will no doubt be writing another post titled “Don’t buy this vendors junk unless you like being in the business of keeping the lights on.” Watch for that one.

Repairing the trailer from the snow damage

September 5, 2014LifeApathy, HowTojrdalrymple

It came to be that I needed to use the trailer to move some furniture. In case you didn’t see or don’t recall here is a link to see the damage.

Time to repair it, or alternatively pony up $500 or so bucks to rent a truck to get from Chicago to home. The pictures can do most of the talking, but the basic process was as follows:

I used it in its broken state a bit, so I first had to clean out enough stuff to be able to work inside. I also had to source the roof bows. It so happened that my mother and nephew were traveling by the manufacturer about a week and change before I needed the trailer so I asked them to stop and pick up said roof bows. They were cheap, about $20 a piece.
I started by figuring out how it was assembled. Basically the roof is a big section that connects 2 corner pieces together and runs the length. It’s lapped and sandwiched together with some light pieces of laminated board inside. I removed all the screws and laminated board so that I could get the roof bows out. You can see in the pictures where I had to peel up some foil to get to the screws.
I went from front to back cutting out 1 roof bow at a time and replacing it with a new one. I started by supporting the roof off the bow, cutting the bow in the center, it basically fell out with a bit of twisting and bending after being cut in half. I then had to clean the welds on the top plate so that the new bow had a nice place to sit, then I just slid the new bow in place. Wash, rinse repeat all the way back.
Somewhere along the way when I was bored I cut out about 2 feet from the rear of the roof. This was the section that wasn’t going to be usable anymore and needed to be replaced. I also did my best to straighten out the parts that got kinked in the back corner.
I propped the new roof bows up high and pulled them down so that they had some good tension. I then welded them.
Originally the sandwich on the edges was the only thing that kept the roof bows from twisting into and away from each other. I added a third row right down the middle to increase strength. I also used 2×4 instead of the smaller laminated wood to further prevent possible twisting. I think that the original construction was probably adequate, however since I’m not an expert I figured I’d be best served by adding as much meat as I could to prevent this from happening again. I started by placing the separating structures down the top-center, then moved to the side that had come unglued the least and did the side that had separated quite a lot last so that I could do my best to pull it all tight during final assembly.
Before finishing step 6 I sourced and cut to fit the new rear of the roof. It was 4 foot in length and I only cut out 2 feet so I had a nice overlap.
Once the whole thing was structurally sound I crawled up on top and used that really shiny really sticky duct tape to make a seal over all the screw holes and at the seams.
As a last and final protectant I used roof repair sealant everywhere I could. At the edge of all the tape seams and also at the metal seams in the mid section of the trailer and at the tail end.

Anyways, that’s the shortwinded version of how I spent almost the entire week prior to labor day weekend. Enjoy the photos.

The seam in the back corner, this is where it all started.

The seam in the back corner, this is where it all started.19-Aug-2014 18:33, Motorola XT912, 2.4, 4.6mm, 0.004 sec, ISO 100