Produktsupport

43QG5E63DG

Support - Downloads

EN / PDF

Produkt-PDF

Support - Ofte stillede spørgsmål

Spiller TV'et video- og lydformater?

Alle vores TV spiller video- og musikfiler, men tjek venligst instruktionsbogen for den fulde specifikation.

Kan jeg forbinde min PC eller Mac via HDMI?

HDMI-indgang understøttes på vores TV'er, men hvis du vil afspille beskyttet indhold, skal du have et grafisk kort, som skal være HDCP-kompatibelt.

Hvilket HDMI-kabel skal vi bruge med mit 4K UHD TV?

Afhængigt af kilden anbefaler vi det hurtigste hastighedskabel, der for øjeblikket er tilgængeligt (dvs. Version 2.0)

Kan jeg optage på mit Toshiba TV?

USB-optagelse er tilgængelig på visse Toshiba-modeller. (USB-format skal være FAT32)

Jeg kan ikke finde Internet Portal-knappen på min fjernbetjening?

Internet Portal-knappen er Home-knappen på dit Toshiba TV's fjernbetjening.

Gumb internetskog portala je gumb „Home“ na daljisnkom upravljaču Toshiba televizora.

Kan jeg styre mit Toshiba TV via en mobil app?

Apps til Apple og Android-enheder er tilgængelige - Søg "Toshiba Smart Center" eller 'Toshiba Smart Remote'

Hvilken ekstern lyd tilslutningstype kan jeg bruge i TV'et, hvis jeg vil tilslutte mit Surround Sound system?

Lyd tilslutningstypen er enten via Coax eller Optical output, der ville forbinde til en passende lydforstærker.

Hvad er forskellen mellem Full HD 1080p og HD Ready 720p?

HD Ready TV viser kun HD-udsendelser, mens Full HD-tv'erne gør dette, plus giver endnu større billedkvalitet, når de er tilsluttet til en Full HD-kilde, f.eks. en Blu-ray-afspiller. Hvis dit TV er HD Ready, giver det dig en skærmopløsning på mindst 1366 x 720p. I Danmark sende tv-programmer til HD 720p-niveauet, så hvis du har et HD Ready TV, så vil du opleve TV-programmer på deres højeste detaljegrad.

Har mit Toshiba TV en hovedtelefonudgang?

Alle vores TV har 3,5 mm stereohovedtelefonstik. Når hovedtelefonerne er tilsluttet fjernsynet, vil lyden deaktivere de interne tv-højttalere.

Kan min TV væg monteres?

Alle vores TV'er er VESA væg monterbar kompatible. Hvert TV har en forskellig skruetype, der afhænger af skærm størrelsen. Se venligst instruktionsbogen for den fulde specifikation.

Har mit Toshiba TV en analog tuner samt en digital tuner?

Alle nuværende Toshiba-modeller har både analoge og digitale tunere.

Flere kanaler virker ikke, hvordan kan jeg få alle tilgængelige kanaler?

TV'er viser kun de kanaler, der kan registreres via en antenne under installationen. Hvis du er opmærksom på en række kanaler, der ikke modtages, er det sandsynligt, at antennen ikke modtager stærke nok signaler for at tillade modtagelse af disse kanaler. I dette tilfælde bør du overveje at prøve en anden antennestik eller opgradere din nuværende antenne.

Kan jeg forbinde enheder til mit TV med Bluetooth?

Nogle Toshiba TV understøtter Bluetooth-teknologi. Parring er påkrævet, før du bruger Bluetooth-enhederne med TV'et. Du bør gøre følgende for at parre din enhed med fjernsynet:

1/ Indstil enheden til parringstilstand.

2/ Start enhedsøgning på tv'et.

For lydenheder skal du bruge Audio Link-indstillingen i menuen System > Sound menu. For fjernbetjeninger Smart Remote-indstillingen i menuen System > Options > More menu. Vælg menupunktet, og tryk på knappen OK for at åbne den relaterede menu. Ved hjælp af denne menu kan du opdage og forbinde enhederne, der bruger trådløs Bluetooth-teknologi og begynde at bruge dem. Følg vejledningen på skærmen. Start enhedssøgningen. En liste over tilgængelige Bluetooth-enheder vises. Vælg den enhed, du vil oprette forbindelse fra listen, og tryk på knappen OK for at oprette forbindelse.

Hvis meddelelsen “Device connected” vises, er forbindelsen etableret. Hvis forbindelsen fejler, prøv den igen. Bemærk: Du kan tilslutte lydenheder eller fjernbetjeninger via Bluetooth til dit tv. Træk eller sluk for enhver anden tilsluttet lydenhed, for at Bluetooth-funktionen fungerer korrekt.

Kan jeg streame indhold fra min mobile enhed til mit Toshiba TV?

Wireless Display giver dig mulighed for at streame indhold direkte til dit Toshiba TV. (Bemærk: IOS-enheder understøttes ikke)

Hvordan kan jeg trådløst oprette forbindelse til TV ved hjælp af en computer, der kører Windows 10?

Wireless Display giver dig mulighed for at streame indhold direkte til dit Toshiba TV.

Kan jeg forbinde en DVD-afspiller til mit Toshiba TV?

Der er en række mulige forbindelser på dit Toshiba TV. HDMI-porte tilbyder den bedste kvalitetsforbindelse, der tillader transmission af High Definition-billeder på skærmen. SCART-porten tillader nogle ældre produkter at oprette forbindelse til tv'et. Se venligst den enkelte produktspecifikation for de tilslutninger, der er tilgængelige på hvert produkt.

Name	Provider	Purpose	Expiry
PHPSESSID	TOSHIBA	HOLDS USER LOGIN ACTIVITY	1 year
COOKIEPREF	TOSHIBA	HOLDS USERS COOKIE PREFERENCES	1 year

Name	Provider	Purpose	Expiry
_ga	Google	Analytics used to distinguish users	2 years
_gid	Google	Analytics used to distinguish users	1 day

Name	Provider	Purpose	Expiry
_ga	Google	Used to distinguish users.	2 years
_gid	Google	Used to distinguish users.	24 hours
_gat	Google	Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.	1 minute
AMP_TOKEN	Google	Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.	30 seconds to 1 year
_gac_	Google	Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.	90 days
__utma	Google	Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.	2 years from set/update
__utmt	Google	Used to throttle request rate.	10 minutes
__utmb	Google	Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.	30 mins from set/update
__utmc	Google	Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.	End of browser session
__utmz	Google	Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.	6 months from set/update
__utmv	Google	Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.	2 years from set/update
__utmx	Google	Used to determine a user's inclusion in an experiment.	18 months
__utmxx	Google	Used to determine the expiry of experiments a user has been included in.	18 months
_gaexp	Google	Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.	Depends on the length of the experiment, but typically 90 days.
_opt_awcid	Google	Used for campaigns mapped to Google Ads Customer IDs.	24 hours
_opt_awmid	Google	Used for campaigns mapped to Google Ads Campaign IDs.	24 hours
_opt_awgid	Google	Used for campaigns mapped to Google Ads Ad Group IDs	24 hours
_opt_awkid	Google	Used for campaigns mapped to Google Ads Criterion IDs	24 hours
_opt_utmc	Google	Stores the last utm_campaign query parameter.	24 hours
_cf_bm	ZENDESK	This Cloudflare cookie helps manage incoming traffic that matches criteria associated with bots. If interested to learn more, Cloudflare provides further detail about some of their Cookies on the Cloudflare website here:Understanding the Cloudflare Cookies	30 minutes
_cfruid	ZENDESK	Cloudflare cookie used in cases were multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.	Session
_cfduid	ZENDESK	Cloudflare cookie used for security restrictions.	30 days
_zendesk_shared_session	ZENDESK	Authentication cookie - set to be anonymous	8 hours Session duration is configurable by the Subscriber using the Session Expiration config in Admin Center > Security Settings. Can be anything from 5 minutes to 2 weeks. Default is 8 hours.
_zendesk_authenticated	ZENDESK	This is a flag set when a user is authenticated to display the most up to date content.	Session
_gat	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center. See here to enable or disable these Google Analytics Cookies:Enabling Google Analytics for your Help Center	1 minute
_gid	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	1 day
_ga	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	2 years
hc:{user_identifier}:recently_ visited_articles	ZENDESK	[LOCAL STORAGE] To help subscribers understand the resources an end-user has attempted in seeking support, this object tracks recently-viewed articles within the help center. This Cookie allows Zendesk customers to identify an end-user's recently-viewed articles. If used exclusively by Subscriber for providing customer support purposes, this could be deemed Essential.	Forever (Local Storage)
articleVotes	ZENDESK	Article anonymous votes (localStorage or if not available falls back to a session cookie)	Forever (Local Storage)/Session (cookie)
_help_center_session	ZENDESK	Stores unique session key for Help Center product.	Session
ob-{public-api-key}	ZENDESK	Connect js snippet	3 years
_zendesk_nps_session	ZENDESK	Stores a unique key for a session, for landing page after responding to an NPS survey (if enabled)	Session
.appUserId	ZENDESK	Stores the appUser ID for the current session Sunshine Conversations Web Messenger will not drop any Cookies until the widget is initiated by the End-User. If you wish to further control these Cookies using a third-party cookie solution, that is supported.	Forever
.clientId	ZENDESK	Unique identifier of the SDK instance	Forever
.sessionToken	ZENDESK	Session token to be used to authenticate requests on behalf of an anonymous user. Session tokens are linked to a client ID (see clientId)	Forever
lsid	ZENDESK	(From Stripe)	Session
ab_disable_remember_me	ZENDESK	(From Stripe)	Session
cid	ZENDESK	(From Stripe) Stripe analytics "client ID" used for service improvement	Session
checkout-test-session / checkout-live-session	ZENDESK	(From Stripe) Used to power Legacy Checkout's Remember Me function	1 year
ZD-zE_oauth	ZENDESK	Stores the authentication token once the user has been authenticated. Web Widget offers pre-built API functionality for cookie consent; see here:Web Widget Cookie Permission in Developer Center Alternatively, these Cookies respect external cookie bot functionality as well.	2 hours
ZD-settings	ZENDESK	Stores a hash of settings so that we don't keep sending requests to our backend	forever
ZD-suid	ZENDESK	Session id for Sunshine (if Sunshine functionality is being used)	20 minutes
ZD-buid	ZENDESK	Collects Machine ID for use in Sunshine (if Sunshine functionality is being used)	forever
ZD-store	ZENDESK	Ensures consistent presentation of the Web Widget when an End-User navigates to a new web page.	forever
__zlcmid	ZENDESK	Store visitor's machine-id for the Chat widget's authentication Chat Widget offers out-of-the-box cookie consent management, see here:Enabling cookie consent for the Chat widget & Web SDK Alternatively, these Chat Cookies respect external cookie bot functionality as well.	1 year
__zlcprivacy	ZENDESK	Store visitor's decision on CookieLaw	1 year
__zlcstore	ZENDESK	[Local Storage] Store visitor's account settings locally	forever
zte2095	ZENDESK	Used to identify the domain/subdomain the Chat Widget is located on.	Session
AWSALB	ZENDESK	Used to ensure user session remains with the same AWS instance to improve performance and stability.	Session
AWSALBCORS	ZENDESK	Used to ensure user session remains with the same AWS instance to improve performance and stability.	Session
JAR	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots. These Google reCAPTCHA Cookies (JAR-SSID) apply on Help Center pages if sign-ins are enabled, and with respect to submitting tickets, if enabled. reCAPTCHA for submitting tickets can be disabled within the help center settings if desired.	30 days
APISID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
CONSENT	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	20 years
DV	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	Session
HSID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
NID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	6 months
SAPISID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
SID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
SIDCC	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	3 months
SSID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
_ga	Google	Analytics used to distinguish users	2 years
_gid	Google	Analytics used to distinguish users	1 day

Name	Provider	Purpose	Expiry
_ga	Google	Used to distinguish users.	2 years
_gid	Google	Used to distinguish users.	24 hours
_gat	Google	Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_.	1 minute
AMP_TOKEN	Google	Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.	30 seconds to 1 year
_gac_	Google	Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.	90 days
__utma	Google	Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.	2 years from set/update
__utmt	Google	Used to throttle request rate.	10 minutes
__utmb	Google	Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.	30 mins from set/update
__utmc	Google	Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.	End of browser session
__utmz	Google	Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.	6 months from set/update
__utmv	Google	Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.	2 years from set/update
__utmx	Google	Used to determine a user's inclusion in an experiment.	18 months
__utmxx	Google	Used to determine the expiry of experiments a user has been included in.	18 months
_gaexp	Google	Used to determine a user's inclusion in an experiment and the expiry of experiments a user has been included in.	Depends on the length of the experiment, but typically 90 days.
_opt_awcid	Google	Used for campaigns mapped to Google Ads Customer IDs.	24 hours
_opt_awmid	Google	Used for campaigns mapped to Google Ads Campaign IDs.	24 hours
_opt_awgid	Google	Used for campaigns mapped to Google Ads Ad Group IDs	24 hours
_opt_awkid	Google	Used for campaigns mapped to Google Ads Criterion IDs	24 hours
_opt_utmc	Google	Stores the last utm_campaign query parameter.	24 hours
_cf_bm	ZENDESK	This Cloudflare cookie helps manage incoming traffic that matches criteria associated with bots. If interested to learn more, Cloudflare provides further detail about some of their Cookies on the Cloudflare website here:Understanding the Cloudflare Cookies	30 minutes
_cfruid	ZENDESK	Cloudflare cookie used in cases were multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold.	Session
_cfduid	ZENDESK	Cloudflare cookie used for security restrictions.	30 days
_zendesk_shared_session	ZENDESK	Authentication cookie - set to be anonymous	8 hours Session duration is configurable by the Subscriber using the Session Expiration config in Admin Center > Security Settings. Can be anything from 5 minutes to 2 weeks. Default is 8 hours.
_zendesk_authenticated	ZENDESK	This is a flag set when a user is authenticated to display the most up to date content.	Session
_gat	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center. See here to enable or disable these Google Analytics Cookies:Enabling Google Analytics for your Help Center	1 minute
_gid	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	1 day
_ga	ZENDESK	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	2 years
hc:{user_identifier}:recently_ visited_articles	ZENDESK	[LOCAL STORAGE] To help subscribers understand the resources an end-user has attempted in seeking support, this object tracks recently-viewed articles within the help center. This Cookie allows Zendesk customers to identify an end-user's recently-viewed articles. If used exclusively by Subscriber for providing customer support purposes, this could be deemed Essential.	Forever (Local Storage)
articleVotes	ZENDESK	Article anonymous votes (localStorage or if not available falls back to a session cookie)	Forever (Local Storage)/Session (cookie)
_help_center_session	ZENDESK	Stores unique session key for Help Center product.	Session
ob-{public-api-key}	ZENDESK	Connect js snippet	3 years
_zendesk_nps_session	ZENDESK	Stores a unique key for a session, for landing page after responding to an NPS survey (if enabled)	Session
.appUserId	ZENDESK	Stores the appUser ID for the current session Sunshine Conversations Web Messenger will not drop any Cookies until the widget is initiated by the End-User. If you wish to further control these Cookies using a third-party cookie solution, that is supported.	Forever
.clientId	ZENDESK	Unique identifier of the SDK instance	Forever
.sessionToken	ZENDESK	Session token to be used to authenticate requests on behalf of an anonymous user. Session tokens are linked to a client ID (see clientId)	Forever
lsid	ZENDESK	(From Stripe)	Session
ab_disable_remember_me	ZENDESK	(From Stripe)	Session
cid	ZENDESK	(From Stripe) Stripe analytics "client ID" used for service improvement	Session
checkout-test-session / checkout-live-session	ZENDESK	(From Stripe) Used to power Legacy Checkout's Remember Me function	1 year
ZD-zE_oauth	ZENDESK	Stores the authentication token once the user has been authenticated. Web Widget offers pre-built API functionality for cookie consent; see here:Web Widget Cookie Permission in Developer Center Alternatively, these Cookies respect external cookie bot functionality as well.	2 hours
ZD-settings	ZENDESK	Stores a hash of settings so that we don't keep sending requests to our backend	forever
ZD-suid	ZENDESK	Session id for Sunshine (if Sunshine functionality is being used)	20 minutes
ZD-buid	ZENDESK	Collects Machine ID for use in Sunshine (if Sunshine functionality is being used)	forever
ZD-store	ZENDESK	Ensures consistent presentation of the Web Widget when an End-User navigates to a new web page.	forever
__zlcmid	ZENDESK	Store visitor's machine-id for the Chat widget's authentication Chat Widget offers out-of-the-box cookie consent management, see here:Enabling cookie consent for the Chat widget & Web SDK Alternatively, these Chat Cookies respect external cookie bot functionality as well.	1 year
__zlcprivacy	ZENDESK	Store visitor's decision on CookieLaw	1 year
__zlcstore	ZENDESK	[Local Storage] Store visitor's account settings locally	forever
zte2095	ZENDESK	Used to identify the domain/subdomain the Chat Widget is located on.	Session
AWSALB	ZENDESK	Used to ensure user session remains with the same AWS instance to improve performance and stability.	Session
AWSALBCORS	ZENDESK	Used to ensure user session remains with the same AWS instance to improve performance and stability.	Session
JAR	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots. These Google reCAPTCHA Cookies (JAR-SSID) apply on Help Center pages if sign-ins are enabled, and with respect to submitting tickets, if enabled. reCAPTCHA for submitting tickets can be disabled within the help center settings if desired.	30 days
APISID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
CONSENT	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	20 years
DV	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	Session
HSID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
NID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	6 months
SAPISID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
SID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
SIDCC	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	3 months
SSID	ZENDESK	Used to allow human users easy access to Zendesk features, while blocking actions by bots.	2 years
_ga	Google	Analytics used to distinguish users	2 years
_gid	Google	Analytics used to distinguish users	1 day

Udforsk tv'er

Premium

QLED

4K UHD LED

All TVs

Support

Vejledning til køb af TV

Se garanti

Hvor kan det købes

Kontakt Os

Kontakt os

Udforsk tv'er

Lær mere

	Country	Language
	United Kingdom	English
	Bosnia & Herzegovina (Bosna i Hercegovina)	Bosanski Hrvatski Srpski English
	Bulgaria (България)	български English
	Croatia (Hrvatska)	Hrvatski English
	Cyprus (Κύπρος)	Ελληνικά English
	Czech Republic (Česká republika)	Čeština English
	DACH (Deutschland - Österreich - Suisse)	Deutsch Français English
	Denmark (Danmark)	Dansk English
	Finland (Suomi)	Suomi English
	France (France)	Français English
	Greece (Ελλάς)	Ελληνικά English
	Hungary (Magyarország)	Magyar English
	Iberia (España - Portugal)	Español Português English
	Italy (Italia)	Italiano English
	Lithuania (Lietuva)	Lietuvių English
	Malta	English
	Netherlands (Nederland)	Nederlands English
	Norway (Norge)	Norsk English
	Poland (Polska)	Polski English
	Romania (România)	Român English
	Serbia (Srbija)	Srpski English
	Slovakia (Slovensko)	Slovenčina English
	Slovenia (Slovenija)	Slovenščina English
	Sweden (Sverige)	Svenska English
	Turkey (Türkiye)	Türkçe English
	Ukraine (Україна)	Українська English