Forum Discussion

daedalus_'s avatar
daedalus_
Newbie Caller
Hace 6 años

One PLUS Plan - Can't Enable HD Video

Hola,

I've been trying to enable HD video over LTE with no success; the page simply tells me the line is not eligible, despite being on One PLUS. I chatted with a rep who had a tech assist them which led to me being asked for a callback as they had to create a service ticket and escalate it. I explained to the call back rep that I needed to speak to tech support, he transferred me to a girl who, bless her, was really wanting to help but not understanding my issue. She seemed to be misunderstanding me and thought I was having an issue with my data plan as a whole and performed a network refresh. I followed along on the off-chance that it fixed the problem. When it didn't, I asked her to check specifically to see if my account had HD playback enabled at all. After checking she informed me that I "can stream HD video because you are on our One PLUS plan." After realizing that the issue wasn't going to be fixed in this call, I thanked her for her help and now I'm here.

Is there any simple solution or workaround to this?

  • Thanks for posting this. This issue is related to what our engineers are already working on. Sorry, there's currently not a workaround I can give but our team's getting this taken care of as quickly as possible.

  • Hi, sorry it's been a busy few days.

    On the Profile tab, there is no Media Settings, at least that I saw. However, the way I've been attempting this is going to Manage Data & Add-Ons, Going under Data Pass and clicking Enable HD. This takes me to straight to Media Settings URL and then says I'm not eligible.

  • ¡Hola, @daedalus_​!

    Did you try following the steps that MC posted above? Keep us posted if you're seeing something different.

  • Are you going to MyT-Mobile.com to enable the HD option? I'm curious if the option just isn't there when you go to the Media Settings Profile tab. The reason I ask is because if that's the issue, we have team's working on resolving that right now. As of right now, we don't have a workaround for that issue.