[Samsung XE700T1C-A01FR] Smartpad not properly recognised

Bug #1332824 reported by V. Beau
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Expecting at least the smartpad to be properly recognised with the bare minimum multi-touch gesture: two-fingers right click, side scrolling, two-fingers scrolling, mouse speed.

xinput -list gives:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Wacom ISDv4 EC Pen stylus id=9 [slave pointer (2)]
⎜ ↳ Atmel Atmel maXTouch Digitizer id=10 [slave pointer (2)]
⎜ ↳ USB Keyboard+SmartPad id=13 [slave pointer (2)]
⎜ ↳ Wacom ISDv4 EC Pen eraser id=16 [slave pointer (2)]
⎜ ↳ Asus gaming Mouse (G112) id=19 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ WebCam SC-50AFL11C54N id=11 [slave keyboard (3)]
    ↳ USB Keyboard+SmartPad id=12 [slave keyboard (3)]
    ↳ WebCam SC-20HDM12347N id=14 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    ↳ Chicony USB Keyboard id=17 [slave keyboard (3)]
    ↳ Chicony USB Keyboard id=18 [slave keyboard (3)]
    ↳ Acer Crystal Eye Webcam id=20 [slave keyboard (3)]

Note that "USB Keyboard+SmartPad" is present twice (id 12 and 13)

Also note that running
 xinput test 13
doesn't detect any multitouch on the smartpad.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Jun 21 15:52:14 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
InstallationDate: Installed on 2014-06-18 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=1fdb1c66-705c-4c1a-8d6c-d363ad0e53b9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P10AAT.050.140215.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: XE700T1C-A01FR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
dmi.product.name: 700T1C
dmi.product.version: P10AAT
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Jun 21 15:48:56 2014
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 116
 vendor ACR
xserver.version: 2:1.15.1-0ubuntu2
---
.tmp.unity.support.test.0:

ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.351
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: Fresh install
DistroCodename: vivid
DistroRelease: Ubuntu 15.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c0e1]
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
Package: xorg 1:7.7+7ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Tags: vivid ubuntu reproducible compiz-0.9
Uname: Linux 3.18.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P10AAT.050.140215.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: XE700T1C-A01FR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01FR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
dmi.product.name: 700T1C
dmi.product.version: P10AAT
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.1+15.04.20150213-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.58-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Feb 24 20:25:35 2015
xserver.configfile: default
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 12637
 vendor AUO
xserver.version: 2:1.16.2.901-1ubuntu4

Revision history for this message
V. Beau (vincent-beau) wrote :
Revision history for this message
sicengxiangshi (sicengxiangshixyz) wrote :

This bug was reported as early as the end of 2012, It appears that nobody had ever working on it.

Revision history for this message
penalvch (penalvch) wrote :

V. Beau, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg 1332824

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

no longer affects: xorg (Ubuntu)
affects: fedora → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
V. Beau (vincent-beau) wrote : BootDmesg.txt

apport information

tags: added: apport-collected reproducible vivid
description: updated
Revision history for this message
V. Beau (vincent-beau) wrote : BootLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : CurrentDmesg.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : Dependencies.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : DpkgLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : GconfCompiz.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : LightdmLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : Lspci.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : Lsusb.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : ProcInterrupts.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : ProcModules.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : UdevDb.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : UdevLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : UnitySupportTest.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : XorgLog.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : Xrandr.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : xdpyinfo.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : xserver.devices.txt

apport information

Revision history for this message
V. Beau (vincent-beau) wrote : Re: Samsung XE700T1C Keyboard and touchpad not properly recognised

As you may already have guessed, this is still an issue.

For the recordm the situation remains the same: Mouse & Touchpad is reporting a single button mouse.

penalvch (penalvch)
description: updated
summary: - Samsung XE700T1C Keyboard and touchpad not properly recognised
+ Samsung XE700T1C touchpad not properly recognised
penalvch (penalvch)
summary: - Samsung XE700T1C touchpad not properly recognised
+ [Samsung XE700T1C-A01FR] Smartpad not properly recognised
Changed in xorg (Ubuntu):
importance: Low → Medium
status: Incomplete → Triaged
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

kernel problem if it's not reported as a touchpad

having the same device under core pointer and keyboard is normal, since it has both devices

affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
penalvch (penalvch) wrote :

V. Beau, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.XY-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
V. Beau (vincent-beau) wrote :

Hi, me again, this bug is still valid for Ubuntu 15.10

Using the following kernel:
4.2.0-34-generic #39-Ubuntu SMP Thu Mar 10 22:13:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

penalvch (penalvch)
tags: added: wily
Revision history for this message
Ahmed (aitalaat) wrote :

Bug still exists for ubuntu 18.10

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please attach dmesg.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Teclalivre (geral-e) wrote :

Bug still exists in ubuntu 20.04 LTS.

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

(I was closing this bug report; but I note a mention of it still impacting focal... I found this bug because it still occurs with a live system (jammy) I was just testing...

I've thus re-opened it

It occurred for me on a live system of

Lubuntu jammy 2021-12-23 ISO amd64 on
- samsung 700t1c, i5-3317U, 4gb ram...

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Confirmed
Chris Guiver (guiverc)
tags: added: focal jammy
removed: trusty vivid wily
Revision history for this message
Chris Guiver (guiverc) wrote (last edit ):

Further to my last comment (#32), I zsync'd today's Ubuntu Desktop (jammy) for a QA-test so as report on iso.qa.ubuntu.com & link here..

Ubuntu jammy Desktop ISO (2021-12-29) on
- samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics)

NO problems have occurred; on booting the jammy image I can use the device perfectly ! I'll update lubuntu jammy daily & re-test, then remove 'jammy' tag if I can't recreate issue I mentioned in #32. I cannot re-create issue with Ubuntu Desktop..

updated Lubuntu jammy ISO (2021-12-29) & no-issues on another 'live' QA-test so I'm removing 'jammy' tag

Chris Guiver (guiverc)
tags: removed: jammy
To post a comment you must log in.