-
Posts
153 -
Joined
-
Last visited
Awards
This user doesn't have any awards
Profile Information
-
Location
London, UK
-
Occupation
Freelance Photographer, Videographer and editor
System
-
CPU
Intel i7 7700K @ 5Ghz
-
Motherboard
Asus Strix 270e
-
RAM
Corsair Dominator Platinum LE Chrome
-
GPU
Asus Strix 1080Ti, Asus Strix 1070
-
Case
Corsair 450D
-
Storage
Samsung 850 Pro 500GB SSD
-
PSU
Corsair AX860i
-
Cooling
Corsair H115i
-
Keyboard
Some super old Samsung PS2 keyboard from 2001
-
Mouse
Some crappy Logitech
-
Sound
Bowers & Wilkins 685, BK electronics Monolith subwoofer, Denon 2312 receiver / amp
-
Operating System
Windows 10
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
wackomann's Achievements
-
I’m absolutely floored by the end result of this build. The attention to detail is just incredible!
-
Canon 5d Mark iii vs sony a7r ii
wackomann replied to Sebastian Kurpiel's topic in Photography and Videography
It might be worth checking out the just announced Canon EOS R - it's mirrorless and to compete with the Sony cameras with similar specs to the 5D MK IV -
Love the current tape design TL shirt! Also really like the design in the original post
-
cameras Trying to get my first full frame camera.
wackomann replied to BBking123's topic in Photography and Videography
I'd say either a 6D with a decent lens or a used / grey import 5D MK IV. Just remember, lenses are way way more important than camera body!- 8 replies
-
- dslr
- full frame
-
(and 1 more)
Tagged with:
-
TLDR: I got another replacement after my repaired handset got damaged by Apple. So to finally conclude this fun adventure. I had another Apple store appointment. They did the normal tests and it came back, tadaa, the screen in fact is faulty. However, they can't give me a replacement as Apple want to investigate as to why I've had so many issues with the iPhone X in a short amount of time. Sigh. So anyway, they take my handset away to try and repair it. About 5 days later, I get an email saying my repair is ready to be picked up. I go about a week later due to weather issues here and after one hell of a fiasco in the Apple store, I get my repair back. As I inspect it, it had a whole load of dents and marks on the exterior chrome bezel. I'm talking literally shavings like, if someone took a sharp knife and scraped bits off. It took a while for the Apple store employee to acknowledge this. Anyway, this ended up in getting another handset, so I'm here a few days later with a new handset that is still currently working... *fingers crossed*
-
So, the saga continues *SIGH* As above, I got a replacement handset at an Apple store 16 days ago. This handset seemed to have no problems until today... AGHHH! For no apparent reason, halfway through trying to reply to someone on Facebook, the keyboard / screen after typing one word or so would become unresponsive. I thought this was just the app being crappy, so I quit it and reopened. This didn't work, so I restart the phone. The issue persists, however I start to notice the phone not responding to some swipe gestures. I decide to finally update to 11.2.5 to see if this helps, as I'm downloading the update the phone becomes incredibly unresponsive - the screen almost seems to not be touch sensitive anymore & 3D touch / force touch no longer works. The hold / sleep button is unresponsive, only after what seems about 20 presses it wakes the phone. This then leads to, the phone sometimes not displaying anything on the lock screen (no time / signal etc, only the background) and sometimes only displaying a notification but being incredibly dim - I'm talking, not lowest brightness setting, but like the display is faulty, then suddenly locking again. It would then sporadically open up Apple Pay with me not doing anything and the screen would be back to full brightness like normal. Face ID wouldn't work at all, swipe up to unlock took about 100 attempts before any response, then typing in my passcode was horrendous. I'd press the first number multiple times before it registers then it wouldn't suddenly erase that and show I haven't put in any numbers. So I'm left incredibly frustrated. The reason I'm still updating this thread is to show these problems in one place incase anyone else has similar issues. I don't know whether it's as simple as a ribbon cable not being fully pressed in as I know how tiny and delicate they are - but some of these issues seem very software related. I'm seriously pissed off at this, because my first handset lasted 28 days, now this one 16 days. I don't really know what to do, because I don't want to keep being stuck in a cycle of going back and getting a replacement handset until the warranty runs out
-
So, an update to this. I've been trying to sort this out with Apple and my provider for quite some time. Apple would tell me I need to go to my carrier (which is legally correct in the UK) but then my carrier (EE) would pass the blame onto Apple saying I need to go to them. Back and forth we go, still paying a contract on a phone that I can't use... Anyway, to cut a long story short, I FINALLY got an appointment at the Apple store today and they did indeed confirm, it's a hardware fault with the iPhone X and no longer software. DFU / recover simply wouldn't work and they replicated that in the store. They were very quick to give me a replacement. They did however say, they haven't yet seen a hardware problem from the iPhone X - this leads me to believe either I'm extremely unlucky and this is an isolated case (which I'm sure Apple would say even if this wasn't true), or some of the first batch of iPhone Xs have a hardware fault that Apple doesn't want to admit. So, if anyone is having a similar problem, I'd love to know. As a reminder, this all started on the 2nd December with the boot loop bug. I managed to restore my phone twice in the space of about 2 weeks before it went into a unfixable boot loop, where no DFU or restore would work - no matter the cable, iTunes, computer, USB port or anything I tried. So, here's to hoping this handset lasts for the remainder of this contract....
-
how dark are the OLED blacks on iPhone X?
wackomann replied to kofman13's topic in Phones and Tablets
I can confirm it doesn't fix it. The problem still persists and the only thing that helps is rolling back the date in the phone to pre 2nd December. I've only had one random restart in the last day since doing this.. which is good considering it would crash and boot loop every hour or so previous (until it would get stuck in a boot loop) Sucks, but hopefully they bring out an 11.2.1 asap -
how dark are the OLED blacks on iPhone X?
wackomann replied to kofman13's topic in Phones and Tablets
Hi, iPhone X owner here. Blacks are awesome, bright display (apparently the brightest OLED so far in a phone) and most importantly NOT oversaturated like the Samsung displays. It does have the weird OLED colour shift but that's on all displays. Overall though, it looks great and you'll be really happy with it HOWEVER, I highly highly recommend holding off on getting an iPhone X until Apple roll out to fix the time zone / date bug that temporarily made my, and many other people's, handset unusable. -
After taking the handset back to my carrier (after being advised by Apple to do this) they pretty much told me there's nothing they can do and I need to take it back to Apple *eye roll* Anyway, I was on the phone to Apple for a while and after trying 2 different computers (mac and windows) different cables, USB ports, fresh installs... I finally got it working. I did try DFU mode many times - literally nothing would work. Long story short, it appears if for any reason your update ever fails on an iPhone you HAVE to change the USB port you're trying it with and restart the entire process. Due to a ridiculous set of combinations, this is why it took me a good 10 - 12 times before it worked. If anyone else is having this problem (and the iOS 11 problems) follow these steps as it helped resolve my issues and advised by Apple atm. - Back up your phone if possible - Try the recovery mode first and update - If you get hit with error 26 or 14, it's most likely a USB issue. Either the cable or the USB. - If you get hit with any sort of error DO NOT try the same USB port on the computer. - You CANNOT update the handset with anything other than High Sierra on Mac. - I HIGHLY recommend using an official Apple cable. Saying this, even using a brand new Apple cable still didn't solve my problems, but that was down to the USB issue. - Make sure your iTunes is 100% up to date. The update will not work if both your OS AND iTunes are up to date. - Every one of these things has to be perfect in order for the update to work. This seems obvious, but I was plagued with one of these problems at each step which made it even more confusing trying to work out which issue was the problem. - Finally, probably the most important step, If you're on iOS 11.1.2 or even updated to 11.2, CHANGE YOUR DATE / TIME settings back pre - December 2nd. Even on iOS 11.2 my handset went into a boot loop and having a quick Google, I'm not alone in this. I've put my back a month so I don't have to keep changing it and it keeps at least the number right just not the month. Hopefully Apple release an update to 11.2 to finally fix this time bug. It's terrible having a handset that I feel I can't rely on, but hopefully this is just a temporary issue..