Skip to main content

The Saga of EA Customer support part 6

Between the 6th and the 9th not much happened.  Mostly this was the peroid where I was trying to be a nusance and hopefully cause something to show up on a report that would land on a middle managers desk at some point.

Jan 6, 2017

 At some point this day, I gave the game a 1 star review on the play store.  I also took to the official forums and saw several others experiencing the same issue, as early as Nov 1st.  I don't know at what time each happened.

At 1:22 PM I submited a bug, claiming that there was a problem with the support procedures, causing cases to be closed with out a proper resolution.  This was closed without responce, then again reopened by me.  It currently remains open.

At 4:16 PM They responded to my second case, that it was a duplicate, and that it was closed:

Thank you for contacting us back at Electronic Arts. 
I would like to inform that your case (escalated)#[First Case] is already escalated to our specialist team. Please let me share that due to high volume of customers our studio team is unable to respond you back by the expected timeline and in this case I only request you to please have patience and wait for some time, as they are working on your issue. Also do not update the case#[First Case] to avoid delay in response from the specialist .
And, if you want to know the status of your issue, you can update the same case# [Second Case]. Thank you again for understanding and patience. 
This case will get closed automatically. Should you have any further questions regarding this or any other issues, please do not hesitate to let us know. You can also find answers to common questions on our Help Center at http://help.ea.com, or ask our community experts by visiting Answer HQ at http://answers.ea.com.

I responded with the following:
This resolution remains unsatisfactory.
Which reopend the ticket.

At 6:33 PM They responded again to my second case, that it was a duplicate, and that it was closed, a carbon copy of the above email, but this time something caught my eye.

at 8:19 PM I responded with the following:
Please update me on the status of this issue.
The case still remains open, without responce.
Labels:

Comments

Post a Comment

Popular posts from this blog

8Bitdo NES 30 Pro on linux

This post will go over the setup I had to do to get my   8Bitdo  NES30 Pro controller working on my Arch linux desktop with steam.  This results in the system loading the xboxdrv automatically when the controller is connected, and unloading once finished. Firmware Update The first thing to tackle was the firmware update on the controller,  This may not be needed, but I like to keep my devices up to date. After some googling, I was able to find a program called fwupd  that's able to update the controller via a USB connection.  It's available for Arch in the community repo. The basic syntax of the command is: fwupdmgr get-devices fwupdmgr refresh fwupdmgr get-updatessudo fwupdmgr update The controller will need to be put into 'Firmware update mode'.  Be aware that the final command will also update all eligible firmware on your system, so If you don't want that, please dig into the documentation Bluetooth Connection G...
1 comment
Read more

Craftware 1.17 on Arch Linux -- notes

Craftware a slicer for 3d printers is available for linux here .  It looks pretty good, and is supposedly multi threaded with support for hardware acceleration. I can only find it  as a deb file, and there's nothing in the AUR for it. I tried a few of the common methods for installing debs: debtap While it was able to create a package, upon installing it I got this error loading packages... error: failed to prepare transaction (package architecture is not valid) :: package craftware-1.17.1-1-i686 does not have a valid architecture So.. No good. I tried just extracting the package content, and running the binary: ./craftware: error while loading shared libraries: libomp.so: cannot open shared object file: No such file or directory and yes, it is installed. $ ldconfig -v           libomptarget.so -> libomptarget.so          libomp.so -> libomp.so          libzit...
1 comment
Read more