Sam Tab S 8.4 LTE (invalid Processor recognition)
Benchmarl application displays cpu as snapdragon 800, although I desired this processor, I was sold a tablet LTE varient, but it is in fact the under performing Eynos 5 Oct a core processor made by Samsung.
Screenshot_2015-05-10-23-22-34.png
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by postmaster on 10 May, 2015 10:44 PM
[http://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to [email blocked] couldn't be delivered.
anthony wasn't found at primatelabs.com
tender2+df95a2dcc9 Office 365 anthony
Action Required Recipient
[http://products.office.com/en-us/CMSImages/email_StatusGraphic_1.png?version=6ab6cc2f-330e-0c93-6ee7-96c969ab92d8]
Unknown TO address
How to Fix It
The address may be misspelled or may not exist. Try the following:
* Retype the email address then resend the message.
* Clear the recipient Autocomplete cache in Outlook or Outlook Web App by following the steps in this article: Error code 5.1.10 in Exchange Online and Office 365<http://go.microsoft.com/fwlink/?LinkId=389363>.
* Contact the recipient (by phone or instant messaging, for example) to check that the address is correct.
* The recipient may have set up mail forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
If the problem continues, forward this message to your email admin.
Was this helpful? Send feedback<http://go.microsoft.com/fwlink/?LinkId=525921>.
________________________________
More Info for Email Admins
This error occurs because the sender sent a message to someone whose mailbox is hosted by Office 365 and the email address is incorrect. The error is reported by the recipient's email system, but most often it must be fixed by the sender. An example is when the recipient changes their email address but the sender selects the person from the recipient AutoComplete list, which has the out-of-date email address information.
Sometimes it needs to be fixed by the recipient or the recipient's email admin, for example, when the recipient has created a mail forwarding rule to an incorrect address, or if there's a problem with their email address directory. If the sender is using the correct recipient address, and it's still not working, send a test message from another user mailbox to see if it's an issue unique to this sender. If you reproduce the problem sending from another user account, ask the recipient or the recipient's email admin to confirm that the recipient address exists, is correct, and is working. Suggest they check for misbehaving forwarding rules or possible email address directory issues (such as directory synchronization issues).
For more information, see Error code 5.1.10 in Exchange Online and Office 365<http://go.microsoft.com/fwlink/?LinkId=389363>.
Original Message Details
Created Date: 5/10/2015 10:44:23 PM
Sender Address: [email blocked]
Recipient Address: [email blocked]
Subject: Sam Tab S 8.4 LTE (invalid Processor recognition) [Geekbench #15231]
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
DSN generated by: CY1PR0101MB1147.prod.exchangelabs.com
Message Hops
HOP TIME (UTC) FROM TO WITH RELAY TIME
1 5/10/2015
10:44:24 PM [192.228.96.5] postcard.entp.com esmtpa (Exim 4.82) (envelope-from <[email blocked]>) 1 sec
2 5/10/2015
10:44:26 PM postcard.entp.com BN1AFFO11FD012.mail.protection.outlook.com Microsoft SMTP Server (TLS) 2 sec
3 5/10/2015
10:44:27 PM BN1AFFO11FD012.protection.gbl BL2PR01CA0047.outlook.office365.com Microsoft SMTP Server (TLS) 1 sec
4 5/10/2015
10:44:27 PM BL2PR01CA0047.prod.exchangelabs.com CY1PR0101MB1147.prod.exchangelabs.com Microsoft SMTP Server (TLS) *
Original Message Headers
Received: from BL2PR01CA0047.prod.exchangelabs.com (10.141.66.47) by
CY1PR0101MB1147.prod.exchangelabs.com (25.161.163.21) with Microsoft SMTP
Server (TLS) id 15.1.148.16; Sun, 10 May 2015 22:44:27 +0000
Received: from BN1AFFO11FD012.protection.gbl (2a01:111:f400:7c10::122) by
BL2PR01CA0047.outlook.office365.com (2a01:111:e400:c1b::47) with Microsoft
SMTP Server (TLS) id 15.1.160.19 via Frontend Transport; Sun, 10 May 2015
22:44:27 +0000
Authentication-Results: spf=pass (sender IP is 23.235.226.122)
smtp.mailfrom=tenderapp.com; primatelabs.com; dkim=fail (no key for
signature) header.d=tenderapp.com;primatelabs.com; dmarc=bestguesspass
action=none header.from=tenderapp.com;
Received-SPF: Pass (protection.outlook.com: domain of tenderapp.com designates
23.235.226.122 as permitted sender) receiver=protection.outlook.com;
client-ip=23.235.226.122; helo=postcard.entp.com;
Received: from postcard.entp.com (23.235.226.122) by
BN1AFFO11FD012.mail.protection.outlook.com (10.58.52.72) with Microsoft SMTP
Server (TLS) id 15.1.160.8 via Frontend Transport; Sun, 10 May 2015 22:44:26
+0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tenderapp.com; s=sentry;
h=List-Archive:List-Subscribe:List-Unsubscribe:List-Id:List-Post:List-Help:Content-Type:Mime-Version:Subject:Message-Id:To:From:Date; bh=CqEFmHRC43r6dHakGmcAcYqkIetse4zLY5oCrSyCh7w=;
b=de+3UaAlmici4DDsVxLjV2EaEc2NGiDeuv5bo1KmNc0nFpi2kMrEOsvJHMFMTKEwoQDSfpak6FSTn2kaIF8VN9LgB3THIVUx2UaZF9fGXniXNowLxhpWNWtod6PJCFmdJrj255scFpUyVcfuH9j4aflriL9J3T27EtDPC/oixCgJKvdqNMKt7eQ3CjJlANl5JrrqHta/HutJFGfCSx6yHVbeqf+DcEKNHI58FbCIs97lqVIBHOZ60mnLxV8TRih6W4AZ9Z7nGE7EDwzakD6d/vjI9jzxn7dJPjdUD4YeVuEtpEZxaM0K/iYcW74BkjMbMGpjLyZhQfofkm95kuUxHw==;
Received: from [192.228.96.5] (helo=tenderapp.com)
by postcard.entp.com with esmtpa (Exim 4.82)
(envelope-from <[email blocked]>)
id 1YrZxQ-0005Dg-Bu
for [email blocked]; Sun, 10 May 2015 22:44:24 +0000
Date: Sun, 10 May 2015 22:44:23 +0000
From: Adoniah <[email blocked]>
To: <[email blocked]>
Message-ID: <[email blocked]>
Subject: Sam Tab S 8.4 LTE (invalid Processor recognition) [Geekbench #15231]
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="mimepart_554fdf482d5ec_422b3fd97369014015018bc"
List-Help: <http://support.primatelabs.com>
X-Tender: notification
List-Post: <[email blocked]>, <http://support.primatelabs.com/discussions/geekbench/15231-sam-tab-s-84-lte-invalid-processor-recognition>
List-Id: Primate Labs <support.primatelabs.com>
X-Pm-Keepid: true
List-Unsubscribe: <http://support.primatelabs.com/unsubscribe/7798f7b6dabc5b2a1e86c8584fd8ee5f9e1f2ade>
X-Tender-Site: 17311
List-Subscribe: <http://support.primatelabs.com/discussions/geekbench/15231-sam-tab-s-84-lte-invalid-processor-recognition>
List-Archive: <http://support.primatelabs.com/discussions/geekbench>
Return-Path: [email blocked]
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:23.235.226.122;CTRY:;IPV:NLI;EFV:NLI;
X-DkimResult-Test: Failed
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEID:(421252001)(42134001)(42139001)(3002015);SRVR:CY1PR0101MB1147;
2 Posted by Adoniah on 12 May, 2015 01:42 PM
Not displaying correct processor values or product. LTE UK Exynos
Christopher closed this discussion on 18 Nov, 2015 04:06 PM.