Vu7+ Touch Screen Issue

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Vu7+ Touch Screen Issue

Unread post by gtetil » Thu May 05, 2016 12:37 am

I just received a new C2 controller running Android 5.1.1 (1.4) and a new Vu7+ touch screen. The screen displays fine, but the only way I can get the touch screen to work is to boot up the controller, then unplug the micro-usb connector between screen and controller, then plug back in. Once i plug it back in, the touch screen works. If I reboot the controller, I'm back to the touch screen not working, and I have to un-plug/plug the connector again to get it to work. Any suggestions?

DroidMasterX
Posts: 172
Joined: Tue May 12, 2015 7:56 am
languages_spoken: english
ODROIDs: ODROID C1, ODROID W, ODROID VU
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by DroidMasterX » Fri May 06, 2016 11:20 pm

I have the same problem--you're not alone.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Sat May 07, 2016 5:56 pm

The issue should be fixed with V1.4 update.

Did you install the V1.4 image freshly or upgraded from previous version?
Did you connect the Vu7+ to the OTG port? or normal USB host port?

DroidMasterX
Posts: 172
Joined: Tue May 12, 2015 7:56 am
languages_spoken: english
ODROIDs: ODROID C1, ODROID W, ODROID VU
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by DroidMasterX » Tue May 10, 2016 2:26 am

Fresh 1.4 image. Just flashed it. I am connecting it via the OTG port and it is currently in use as a tablet.

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by gtetil » Tue May 10, 2016 7:51 am

Mine was also a fresh install of v1.4. I've tried both the OTG port and a USB port, but still the same issue.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Tue May 10, 2016 12:21 pm

Can you find "16b4:0703" in the "lsusb" output on Terminal app?

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by gtetil » Wed May 11, 2016 7:49 am

Here's what I get when it first boots up:

Code: Select all

[   27.459744@1] lowmemorykiller: lowmem_shrink: convert oom_adj to oom_score_ad                                                 j:
[   27.461404@1] lowmemorykiller: oom_adj 0 => oom_score_adj 0
[   27.466944@1] lowmemorykiller: oom_adj 1 => oom_score_adj 58
[   27.472529@1] lowmemorykiller: oom_adj 2 => oom_score_adj 117
[   27.478228@1] lowmemorykiller: oom_adj 3 => oom_score_adj 176
[   27.483914@1] lowmemorykiller: oom_adj 9 => oom_score_adj 529
[   27.489619@1] lowmemorykiller: oom_adj 15 => oom_score_adj 1000
[   28.831591@2] acc_open
[   28.831629@2] acc_release
[   29.725821@1] Loading modules backported from Linux version v3.19-rc1-0-g97bf                                                 6af
[   29.727757@1] Backport generated by backports.git v3.19-rc1-1-0-g74aaf28
[   29.845585@2] avc open
[   29.845608@2] amvenc_avc  check CMA pool sucess, max instance: 1.
[   29.848522@2] allocating phys 0x61300000, size 18432k, wq:ffffffc059c8d800.
[   29.855652@2] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some dat                                                 a may be corrupt. Please run fsck.
[   29.865876@2] amvenc_avc  memory config sucess, buff start:0x61300000, size i                                                 s 0x1200000, wq:ffffffc059c8d800.
[   29.875261@2] avc release, wq:ffffffc059c8d800
[   29.879674@2] remove  encode_work_queue ffffffc059c8d800 sucess, _destroy_enc                                                 ode_work_queue line 3521.
[   29.896726@2] codec:vdec_clock_set-----2
[   29.896757@2] codec:vdec1_set_clk 0, 1
[   29.898735@2] codec:vdec_clock_set 2 to 500
[   29.903095@2] ionvideo open
[   30.095889@2] ionvideo_stop_generating!!!!
[   30.095944@2] ionvideo release
[   30.099501@2] codec:vdec_clock_set-----2
[   30.101264@2] codec:vdec1_set_clk 0, 1
[   30.104989@2] codec:vdec_clock_set 2 to 500
[   30.109442@2] ionvideo open
[   30.305874@2] ionvideo_stop_generating!!!!
[   30.305921@2] ionvideo release
[   30.308693@2] codec:vdec_clock_set-----2
[   30.311246@2] codec:vdec1_set_clk 0, 1
[   30.314953@2] codec:vdec_clock_set 2 to 500
[   30.319682@2] ionvideo open
[   30.515854@2] ionvideo_stop_generating!!!!
[   30.515899@2] ionvideo release
[   30.518943@2] codec:vdec_clock_set-----2
[   30.521221@2] codec:vdec1_set_clk 0, 1
[   30.524928@2] codec:vdec_clock_set 2 to 500
[   30.529450@2] ionvideo open
[   30.722039@0] cfg80211: Calling CRDA to update world regulatory domain
[   30.725870@2] ionvideo_stop_generating!!!!
[   30.726998@2] ionvideo release
[   30.732711@2] codec:vdec_clock_set-----2
[   30.733892@2] codec:vdec1_set_clk 0, 1
[   30.737658@2] codec:vdec_clock_set 2 to 500
[   30.741996@2] ionvideo open
[   30.935932@2] ionvideo_stop_generating!!!!
[   30.936002@2] ionvideo release
[   30.938778@2] codec:vdec_clock_set-----2
[   30.941312@2] codec:vdec1_set_clk 0, 1
[   30.945033@2] codec:vdec_clock_set 2 to 500
[   30.949419@2] ionvideo open
[   31.155865@2] ionvideo_stop_generating!!!!
[   31.155915@2] ionvideo release
[   31.158530@2] codec:vdec_clock_set-----2
[   31.161239@2] codec:vdec1_set_clk 0, 1
[   31.164945@2] codec:vdec_clock_set 2 to 500
[   31.169334@2] ionvideo open
[   31.365861@2] ionvideo_stop_generating!!!!
[   31.365917@2] ionvideo release
[   31.368912@2] codec:vdec_clock_set-----2
[   31.371236@2] codec:vdec1_set_clk 0, 1
[   31.374938@2] codec:vdec_clock_set 2 to 500
[   31.379235@2] ionvideo open
[   31.575872@2] ionvideo_stop_generating!!!!
[   31.575927@2] ionvideo release
[   31.578908@2] codec:vdec_clock_set-----2
[   31.581259@2] codec:vdec1_set_clk 0, 1
[   31.584973@2] codec:vdec_clock_set 2 to 500
[   31.589298@2] ionvideo open
[   31.785900@2] ionvideo_stop_generating!!!!
[   31.785955@2] ionvideo release
[   32.246306@3] rtc-pcf8563 1-0051: chip found, driver version 0.4.3
[   32.247012@3] rtc-pcf8563 1-0051: pcf8563_get_datetime: read error
[   32.255560@3] rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc0
[   33.095449@0] dig: isBootCompleted:1!
[   33.266504@2] rtc-pcf8563 1-0051: pcf8563_get_datetime: read error
[   33.291102@0] dig: setDataRoCount count:0!
[   34.696264@3] usb 1-1.1: reset high-speed USB device number 3 using dwc_otg
[   34.806715@3] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502                                                  detected
[   34.837597@0] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
[   34.852445@2] usbcore: registered new interface driver rt2800usb
[   36.872415@0] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firm                                                 ware file 'rt2870.bin'
[   36.878160@0] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware det                                                 ected - version: 0.29
[   37.192979@2] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.636277@0] wlan0: authenticate with f4:f2:6d:ca:ad:d2
[   38.684179@0] wlan0: send auth to f4:f2:6d:ca:ad:d2 (try 1/3)
[   38.686603@3] wlan0: authenticated
[   38.695907@3] wlan0: associate with f4:f2:6d:ca:ad:d2 (try 1/3)
[   38.701744@0] wlan0: RX AssocResp from f4:f2:6d:ca:ad:d2 (capab=0x431 status=                                                 0 aid=6)
[   38.712681@0] wlan0: associated
[   38.712807@0] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   39.569523@2] mtp_open
[   40.875501@1] init: untracked pid 4526 exited with status 0
[   51.846002@1] init: untracked pid 4529 exited with status 0
[   54.979632@1] divider=16,frac=33920000,SDMval=4523
[   54.979821@1] [aml-i2s-dai]i2s dma ffffff8001b01000,phy addr 1621098496,mode 0,ch 2
[   54.986447@1] ----aml_hw_iec958_init,runtime->rate=48000,sample_rate=4--
[   54.993017@1] aml_set_spdif_clk rate
[   54.996588@1] divider=20,frac=33920000,SDMval=5654
[   55.001360@1] set normal 512 fs /4 fs
[   55.004921@1] iec958 mode PCM16
[   55.008071@1] IEC958 16bit
[   55.010707@1] hdmitx: audio: aout notify rate 48000
[   55.015531@1] hdmitx: audio: aout notify size 16
[   55.020131@1] hdmtix: set audio
[   55.023214@1] hdmitx tx_aud_src = 0
[   55.027074@1] hdmitx aud_n_para = 6144
[   55.030379@1] hdmitx set channel status
[   55.034213@1] 958 with i2s
[   55.036929@1] speaker_events--mute =1
[   55.046400@1] aiu i2s playback enable
[   55.046424@1] audio_hw_958_enable 1
[   59.706511@1] aiu i2s playback disable
[   59.706538@1] audio_hw_958_enable 0
[   64.715932@1] speaker_events--mute =0
The last 5 lines here is what I get when I unplug the screen, then plug it back in, and it starts working:

Code: Select all

[   59.706511@1] aiu i2s playback disable
[   59.706538@1] audio_hw_958_enable 0
[   64.715932@1] speaker_events--mute =0

130|shell@odroidc2:/ $ [  203.233100@0] usb 1-1.3: USB disconnect, device number 4
[  207.306160@0] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[  207.414004@3] input: BYZHYYZHY By ZH851 as /devices/dwc2_b/usb1/1-1/1-1.3/1-1.3:1.0/0003:16B4:0703.0002/input/input4
[  207.421684@0] hid-multitouch 0003:16B4:0703.0002: input,hiddev0: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on usb-dwc2_b-1.3/in              put0
[  241.930381@0] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.


Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Wed May 11, 2016 9:33 am

I received today a new c2 running 5.1.1(1.4) and a new Vu7+ and have the same problem !!!

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Wed May 11, 2016 1:08 pm

@Adamouky
Does the touch screen works only when you unplug and plug the USB connector again?

Can you guys tell us which USB devices are connected?

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Wed May 11, 2016 4:44 pm

Sometimes works after reboot.
I have connected usb Bluetooth, wifi and gps.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Wed May 11, 2016 6:24 pm

Can you capture the logcat output on the Terminal app when you meet the issue?

joerg
Posts: 939
Joined: Tue Apr 01, 2014 2:14 am
languages_spoken: german, english, español
ODROIDs: C1, C1+, C2
Location: Germany
Has thanked: 13 times
Been thanked: 38 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by joerg » Wed May 11, 2016 7:52 pm

@odroid: is the driver hid_multitouch compiled into the kernel or it is loadable module? My experience from C1 is that it is better working if loadable and started from init.odroidc.rc. I had the same issue with my carPC and the chalk-elec. When I use custom kernel with hid_multitouch as module it works fine after reboot. If I use kernel with integrated driver, need to plug out and plug in. Only a thought.

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by gtetil » Wed May 11, 2016 10:22 pm

I have the issue even with no other usb devices connected.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Wed May 11, 2016 10:25 pm

@joerg,
Thank you for the idea. I will check it tomorrow.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Thu May 12, 2016 2:00 am

odroid wrote:Can you capture the logcat output on the Terminal app when you meet the issue?
Sorry I can't...

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Thu May 12, 2016 11:51 pm

After every reboot works fine, after shut down the problem appears and the touchscreen stops working.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Fri May 13, 2016 9:13 am

Try this V1.5. We've changed the touch-screen driver as a module for proper detection.
http://odroid.com/dokuwiki/doku.php?id= ... ew_updates

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 13, 2016 11:32 pm

I have downloaded the file 4 times trough odroid utility and can not update because the file is corrupted.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Sat May 14, 2016 5:44 am

I tried to install with dd and installation failed also, please fix the update file.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Sun May 15, 2016 4:52 am

I have installed with dd utility update 1.5 (5.1.1_master-227-v1.5.img) to my c2 and touchscreen Vu7+ have the same problem.
The update did not fix the problem, please do something.

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by gtetil » Mon May 16, 2016 6:24 am

I tried it as well. Still the same problem.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Mon May 16, 2016 1:02 pm

Did you (Adamouky & gtetil) still needed to unplug and plug the USB connection of Vu7+ to enable the touch screen input on V1.5 Android?

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Mon May 16, 2016 7:55 pm

Yes, we still need to unplug and plug the sub connector of Vu7+ to enable the touch screen input on V1.5 Android !!!

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Mon May 16, 2016 9:42 pm

We couldn't reproduce the issue after V1.5 update.
Please grab the logcat output in the terminal app and post it on this thread to find what's wrong.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Tue May 17, 2016 1:58 am

I don't know how to grab the logcat output in the terminal app.
Tell me how to do it.

DroidMasterX
Posts: 172
Joined: Tue May 12, 2015 7:56 am
languages_spoken: english
ODROIDs: ODROID C1, ODROID W, ODROID VU
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by DroidMasterX » Tue May 17, 2016 2:14 am

So type "logcat" into terminal and tell odroid the results. I haven't the time to get to 1.5 yet, so I can't test it out.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Tue May 17, 2016 3:42 am

Thank you DroidMasterX

gtetil
Posts: 50
Joined: Thu May 05, 2016 12:27 am
languages_spoken: english
ODROIDs: C2
Location: Michigan
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by gtetil » Tue May 17, 2016 6:07 am

I just powered up my C2, and the touch screen worked! So, I pulled power, plugged it back in, and had the same issue again. :cry: I tried this 10 more times. It worked 2 out of the 10.

Here's my logcat:
logcat.jpg

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Tue May 17, 2016 7:38 am

Here is my logcat after startup.
Image
Last edited by Adamouky on Tue May 17, 2016 7:45 am, edited 1 time in total.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Tue May 17, 2016 7:43 am

And here is my logcat after unplug and plug the USB connection.
Image

Popoman
Posts: 9
Joined: Sun Aug 10, 2014 4:46 am
languages_spoken: english
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Popoman » Wed May 18, 2016 4:05 pm

I want to buy the VU7 (800x480) will I have this bug too?

DroidMasterX
Posts: 172
Joined: Tue May 12, 2015 7:56 am
languages_spoken: english
ODROIDs: ODROID C1, ODROID W, ODROID VU
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by DroidMasterX » Wed May 18, 2016 10:54 pm

This is a VU7+ issue from what I understand. The VU7 should be fine I think. (I have the VU7+ higher resolution with this problem).
Hardkernel will figure this out shortly I'm sure.

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Thu May 19, 2016 10:58 am

Can you capture the full logcat output and post a text file?

Also check whether you are running V1.5 or not.
root@odroidc2:/ # cd /system/lib/modules/
root@odroidc2:/system/lib/modules # ls -l
.
.
.
-rw-r--r-- root root 27728 2016-05-12 06:18 hid-multitouch.ko
.
.
.
root@odroidc2:/system/lib/modules # uname -a
Linux localhost 3.14.29 #1 SMP PREEMPT Thu May 12 15:17:43 KST 2016 aarch64 GNU/Linux

root@odroidc2:/system/lib/modules # getprop | grep build
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1463032566]
[ro.build.date]: [Thu May 12 14:56:06 KST 2016]
[ro.build.description]: [odroidc2-eng 5.1.1 LMY47V odroidc2-eng-s905_5.1.1_master-227 test-keys]
[ro.build.display.id]: [odroidc2-eng 5.1.1 LMY47V odroidc2-eng-s905_5.1.1_master-227 test-keys]
[ro.build.fingerprint]: [ODROID/odroidc2/odroidc2:5.1.1/LMY47V/odroidc2-eng-s905_5.1.1_master-227:eng/test-keys]
[ro.build.flavor]: [odroidc2-eng]
[ro.build.host]: [build]
[ro.build.id]: [LMY47V]
[ro.build.product]: [odroidc2]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [jenkins]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [odroidc2-eng-s905_5.1.1_master-227]
[ro.build.version.release]: [5.1.1]
[ro.build.version.sdk]: [22]
root@odroidc2:/system/lib/modules #

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 20, 2016 12:21 am

Today I received a new c2 with new emmc and new cables.
I connected the Vu7+ I had and installed the 1.5 update through odroid utility.
The problem with the touchscreen did not go.
You sed that you couldn't reproduce the issue after V1.5 update so I'm thinking if you couldn't reproduce the issue after V1.5 update and I tried with a new c2, new cables and new emmc and the problem remains perhaps some Vu7+ screens are defective...

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 20, 2016 12:45 am

Here is my logcat :

Code: Select all

u0_a48@odroidc2:/ $ logcat
--------- beginning of main
V/Term    ( 5098): onCreate
D/OpenGLRenderer( 5098): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
D/Atlas   ( 5098): Validating map...
D/Term    ( 5098): TermService started
I/TermService( 5098): Activity called onBind()
I/OpenGLRenderer( 5098): Initialized EGL, version 1.4
D/OpenGLRenderer( 5098): Enabling debug mode 0
I/Term    ( 5098): Bound to TermService
I/TermService( 5098): Activity binding to service
I/libjackpal-androidterm( 5098): JNI_OnLoad
I/Term    ( 5098): waiting for: 5121
W/IInputConnectionWrapper( 5098): showStatusIcon on inactive InputConnection
V/Term    ( 5098): onCreate
I/Term    ( 5098): Bound to TermService
I/TermService( 5098): Activity binding to service
W/InputEventReceiver( 5098): Attempted to finish an input event but the input event receiver has already been disposed.
I/Term    ( 5098): waiting for: 5189
I/Term    ( 5098): Subprocess exited: 129
W/InputEventReceiver( 5098): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver( 5098): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver( 5098): Attempted to finish an input event but the input event receiver has already been disposed.
W/IInputConnectionWrapper( 5098): showStatusIcon on inactive InputConnection
I/Term    ( 5098): Bound to TermService
I/TermService( 5098): Activity binding to service
W/IInputConnectionWrapper( 5098): showStatusIcon on inactive InputConnection
I/Term    ( 5098): Subprocess exited: 129
V/Term    ( 5098): onCreate
D/Term    ( 5098): TermService started
I/TermService( 5098): Activity called onBind()
I/Term    ( 5098): Bound to TermService
I/TermService( 5098): Activity binding to service
I/Term    ( 5098): waiting for: 5702
Last edited by Adamouky on Fri May 20, 2016 12:49 am, edited 1 time in total.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 20, 2016 12:47 am

And here are the checks i did :

Code: Select all

u0_a48@odroidc2:/ $ root@odroidc2:/ #cd /system/lib/modules/
/system/bin/sh: root@odroidc2:/: not found
127|u0_a48@odroidc2:/ $ cd /system/lib/modules/
u0_a48@odroidc2:/system/lib/modules $ # ls -l
u0_a48@odroidc2:/system/lib/modules $ ls -l
-rw-r--r-- root     root       910968 2016-05-12 08:18 8192cu.ko
-rw-r--r-- root     root        30760 2016-05-12 08:18 aml_i2c.ko
-rw-r--r-- root     root       384285 2016-05-12 08:18 aml_thermal.ko
drwxr-xr-x root     root              2016-05-12 08:19 backports
-rwxrwx--- root     root       264749 2016-05-11 16:46 ch341.ko
-rw-r--r-- root     root       356472 2016-05-12 08:18 cifs.ko
-rwxrwx--- root     root       287940 2016-05-11 16:46 cp210x.ko
-rw-r--r-- root     root        11592 2016-05-12 08:18 dwav-usb-mt.ko
-rwxrwx--- root     root       500381 2016-05-11 16:46 ftdi_sio.ko
-rw-r--r-- root     root        27728 2016-05-12 08:18 hid-multitouch.ko
-rw-r--r-- root     root        12496 2016-05-12 08:18 i2c-algo-bit.ko
-rw-r--r-- root     root         7000 2016-05-12 08:18 md4.ko
-rw-r--r-- root     root         4568 2016-05-12 08:18 nls_utf8.ko
-rwxrwx--- root     root       296294 2016-05-11 16:46 pl2303.ko
-rw-r--r-- root     root        16448 2016-05-12 08:18 pwm-ctrl.ko
-rw-r--r-- root     root        11416 2016-05-12 08:18 pwm-meson.ko
-rw-r--r-- root     root         9608 2016-05-12 08:18 rtc-pcf8563.ko
-rw-r--r-- root     root         9592 2016-05-12 08:18 w1-gpio.ko
-rw-r--r-- root     root         9464 2016-05-12 08:18 w1_therm.ko
-rw-r--r-- root     root        50744 2016-05-12 08:18 wire.ko
u0_a48@odroidc2:/system/lib/modules $ uname -a
Linux localhost 3.14.29 #1 SMP PREEMPT Thu May 12 15:17:43 KST 2016 aarch64 GNU/Linux
u0_a48@odroidc2:/system/lib/modules $ getprop
[camera.disable_zsl_mode]: [1]
[config.disable_bluetooth]: [false]
[const.window.h]: [600]
[const.window.w]: [1024]
[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.dex2oat-filter]: [interpret-only]
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [192m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [512k]
[dalvik.vm.heapsize]: [512m]
[dalvik.vm.heapstartsize]: [16m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.image-dex2oat-Xms]: [64m]
[dalvik.vm.image-dex2oat-Xmx]: [64m]
[dalvik.vm.image-dex2oat-filter]: [verify-none]
[dalvik.vm.isa.arm.features]: [default]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.force_rtl]: [0]
[dev.bootcomplete]: [1]
[dhcp.eth0.pid]: [3230]
[dhcp.eth0.reason]: [PREINIT]
[dhcp.eth0.result]: [failed]
[dhcp.wlan0.dns1]: [193.92.3.11]
[dhcp.wlan0.dns2]: [193.92.150.2]
[dhcp.wlan0.dns3]: [192.168.1.1]
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: []
[dhcp.wlan0.gateway]: [192.168.1.1]
[dhcp.wlan0.ipaddress]: [192.168.1.139]
[dhcp.wlan0.leasetime]: [86400]
[dhcp.wlan0.mask]: [255.255.255.0]
[dhcp.wlan0.mtu]: []
[dhcp.wlan0.pid]: [4176]
[dhcp.wlan0.reason]: [REBOOT]
[dhcp.wlan0.result]: [ok]
[dhcp.wlan0.server]: [192.168.1.1]
[dhcp.wlan0.vendorInfo]: []
[drm.service.enabled]: [1]
[init.svc.adbd]: [running]
[init.svc.auto_density]: [stopped]
[init.svc.bootanim]: [stopped]
[init.svc.console]: [running]
[init.svc.debuggerd]: [running]
[init.svc.dhcpcd_eth0]: [stopped]
[init.svc.dhcpcd_wlan0]: [running]
[init.svc.drm]: [running]
[init.svc.dwav_mt]: [stopped]
[init.svc.fuse_internal]: [running]
[init.svc.healthd]: [running]
[init.svc.imageserver]: [running]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.lmkd]: [running]
[init.svc.logd]: [running]
[init.svc.low_mem]: [stopped]
[init.svc.makebootini]: [stopped]
[init.svc.media]: [running]
[init.svc.multitouch]: [stopped]
[init.svc.netd]: [running]
[init.svc.preinstall]: [stopped]
[init.svc.remotecfg]: [stopped]
[init.svc.rtc_daemon]: [running]
[init.svc.sdcard]: [running]
[init.svc.servicemanager]: [running]
[init.svc.su_daemon]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.system_control]: [running]
[init.svc.ueventd]: [running]
[init.svc.usbpm]: [running]
[init.svc.vold]: [running]
[init.svc.wpa_supplicant]: [running]
[init.svc.zygote]: [running]
[libplayer.livets.softdemux]: [1]
[libplayer.netts.recalcpts]: [1]
[media.amplayer.dsource4local]: [1]
[media.amplayer.enable-acodecs]: [ac3,eac3,rm,dts]
[media.amplayer.enable]: [true]
[media.amplayer.startmode]: [true]
[media.amplayer.thumbnail]: [true]
[media.amplayer.widevineenable]: [false]
[media.amsuperplayer.defplayer]: [PV_PLAYER]
[media.amsuperplayer.enable]: [true]
[media.amsuperplayer.m4aplayer]: [STAGEFRIGHT_PLAYER]
[media.arm.audio.decoder]: [ape,flac,dts,ac3,eac3,wma,wmapro,mp3,aac,vorbis,raac,cook,amr,pcm,adpcm,aac_latm,rm]
[media.decoder.vfm.defmap]: [decoder ppmgr deinterlace amvideo]
[media.html5videowin.enable]: [1]
[media.libplayer.curlenable]: [true]
[media.libplayer.modules]: [vhls_mod,dash_mod,curl_mod,prhls_mod,vm_mod]
[media.libplayer.seek.fwdsearch]: [1]
[media.wfd.use-pcm-audio]: [false]
[media.wfd.video-bitrate]: [2000000]
[media.wfd.videoframerate]: [24]
[media.wfd.videoresolution-group]: [0]
[media.wfd.videoresolution-type]: [1]
[mouse.firstbutton]: [right]
[net.bt.name]: [Android]
[net.change]: [net.dns3]
[net.dns1]: [193.92.3.11]
[net.dns2]: [193.92.150.2]
[net.dns3]: [192.168.1.1]
[net.hostname]: [android-1ab64f2a2f683c25]
[net.qtaguid_enabled]: [1]
[net.tcp.default_init_rwnd]: [60]
[persist.demo.hdmirotation]: [landscape]
[persist.service.bdroid.bdaddr]: [22:22:5e:ec:94:00]
[persist.sys.country]: [GR]
[persist.sys.dalvik.vm.lib.2]: [libart.so]
[persist.sys.language]: [el]
[persist.sys.localevar]: []
[persist.sys.profiler_ms]: [0]
[persist.sys.root_access]: [3]
[persist.sys.timezone]: [Europe/Brussels]
[persist.sys.usb.config]: [mtp,adb]
[ro.allow.mock.location]: [1]
[ro.app.optimization]: [true]
[ro.audio.mapvalue]: [0,0,0,0]
[ro.baseband]: [unknown]
[ro.board.platform]: [gxbaby]
[ro.boot.hardware]: [odroidc2]
[ro.boot.selinux]: [disabled]
[ro.boot.serialno]: [HKC213254DFCFFDD]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.bt.bdaddr_path]: [/efs/bluetooth/bt_addr]
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1463032566]
[ro.build.date]: [Thu May 12 14:56:06 KST 2016]
[ro.build.description]: [odroidc2-eng 5.1.1 LMY47V odroidc2-eng-s905_5.1.1_master-227 test-keys]
[ro.build.display.id]: [odroidc2-eng 5.1.1 LMY47V odroidc2-eng-s905_5.1.1_master-227 test-keys]
[ro.build.fingerprint]: [ODROID/odroidc2/odroidc2:5.1.1/LMY47V/odroidc2-eng-s905_5.1.1_master-227:eng/test-keys]
[ro.build.flavor]: [odroidc2-eng]
[ro.build.host]: [build]
[ro.build.id]: [LMY47V]
[ro.build.product]: [odroidc2]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [jenkins]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [odroidc2-eng-s905_5.1.1_master-227]
[ro.build.version.release]: [5.1.1]
[ro.build.version.sdk]: [22]
[ro.camera.preview.LimitedRate]: [1280x720x30,640x480x30,320x240x28]
[ro.camera.preview.MaxSize]: [1280x720]
[ro.camera.preview.UseMJPEG]: [1]
[ro.carrier]: [unknown]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.notification_sound]: [pixiedust.ogg]
[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.config.wallpaper]: [/system/etc/default_wallpaper.png]
[ro.crypto.fuse_sdcard]: [true]
[ro.crypto.state]: [unencrypted]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [1]
[ro.factorytest]: [0]
[ro.firstboot]: [0]
[ro.hardware]: [odroidc2]
[ro.hdmi.device_type]: [4]
[ro.kernel.android.checkjni]: [1]
[ro.kernel.android.gps.speed]: [9600]
[ro.kernel.android.gps]: [/dev/ttyACM0]
[ro.opengles.version]: [131072]
[ro.platform.has.mbxuimode]: [true]
[ro.platform.has.realoutputmode]: [true]
[ro.product.board]: [odroidc2]
[ro.product.brand]: [ODROID]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: []
[ro.product.cpu.abilist]: [armeabi-v7a,armeabi]
[ro.product.device]: [odroidc2]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [HardKernel Co., Ltd.]
[ro.product.model]: [ODROIDC2]
[ro.product.name]: [odroidc2]
[ro.radio.noril]: [false]
[ro.revision]: [523]
[ro.runtime.firstboot]: [955343967703]
[ro.secure]: [00]
[ro.serialno]: [HKC213254DFCFFDD]
[ro.sf.hwrotation]: [0]
[ro.sf.lcd_density]: [160]
[ro.ubootenv.varible.prefix]: [ubootenv.var]
[ro.wifi.channels]: [13]
[ro.zygote]: [zygote32]
[selinux.reload_policy]: [1]
[service.bootanim.exit]: [1]
[service.bootvideo]: [0]
[sys.boot_completed]: [1]
[sys.fb.bits]: [32]
[sys.sysctl.extra_free_kbytes]: [7200]
[sys.sysctl.tcp_def_init_rwnd]: [60]
[sys.usb.config]: [mtp,adb]
[sys.usb.state]: [mtp,adb]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]
[wlan.driver.status]: [ok]
u0_a48@odroidc2:/system/lib/modules $ 

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Fri May 20, 2016 11:13 am

We will keep looking this issue. We also could reproduce the issue once when we tried 20 times of hard booting.
Can you "rmmod hid-multitouch.ko" and "insmod hid-multitouch.ko" when the touchscreen doesn't work?

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 20, 2016 1:01 pm

Ok, I will try today

User avatar
codewalker
Posts: 837
Joined: Mon Feb 25, 2013 11:03 am
languages_spoken: english
ODROIDs: all
Has thanked: 31 times
Been thanked: 39 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by codewalker » Fri May 20, 2016 1:09 pm

Try to change the loading timing/sequence of the touch screen drivers.

Code: Select all

$ adb shell
# mount -o rw,remount /
vi /init.odroidc2.board.rc
edit like this.

Code: Select all

on property:dev.bootcomplete=1            
    start dwav_mt                                                          
                                        
on property:init.svc.dwav_mt=stopped                                   
    start multitouch

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Sat May 21, 2016 4:57 pm

Multitouch.ko and loading timing sequence didn't fix the problem...

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Sat May 21, 2016 5:16 pm

I get "cant open" on "insmod hid-multitouch.ko"

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Mon May 23, 2016 11:51 pm

Hi,
Odroid have you find anything new about the Vu7+ issue ?

User avatar
odroid
Site Admin
Posts: 33358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 392 times
Been thanked: 457 times
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by odroid » Tue May 24, 2016 9:58 am

We keep trying to find a solution.
There are some random disconnecting/connecting USB host controller problems in the boot process and it causes the issue probably.

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Tue May 24, 2016 9:17 pm

Hope to hear good news from you soon.

IET_DEMO
Posts: 54
Joined: Wed Sep 30, 2015 3:48 am
languages_spoken: english
ODROIDs: U3,Xu4,c1,C1+
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by IET_DEMO » Tue May 24, 2016 11:39 pm

Hi, I had similar issues with other touchscreen.

What I did is programmatically Plug/Unplug the Usb 1 minute after boot.

So I don't think this issue is only related to VU7.

David

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Fri May 27, 2016 9:57 pm

Hi,
IET_DEMO how can I do this plug/unplug to C2?
Thanks

linuxgnuru
Posts: 26
Joined: Fri Jun 27, 2014 9:01 pm
languages_spoken: english,swahili
ODROIDs: XU4, C2, vu7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by linuxgnuru » Mon May 30, 2016 11:15 pm

By no means is this a permanent fix, but I plug in the micro-usb bridge a few moments after plugging in the power and the touch will work; similar solution to just unpluging and re-plugging in though

IET_DEMO
Posts: 54
Joined: Wed Sep 30, 2015 3:48 am
languages_spoken: english
ODROIDs: U3,Xu4,c1,C1+
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by IET_DEMO » Tue May 31, 2016 12:25 am

Adamouky wrote:Hi,
IET_DEMO how can I do this plug/unplug to C2?
Thanks
You create an application that starts onBoot then:

You execute this system command:
"ls /sys/bus/usb/drivers/usbhid"

Check what it returns:
The file you are looking for starts with "1-1" and contains ":1.0" ->The filename should have a similar pattern for you too

Then:
echo -n YOURFILENAME > /sys/bus/usb/drivers/usbhid/unbind
echo -n YOURFILENAME > /sys/bus/usb/drivers/usbhid/bind

This file correspond to the right usbhid currently plugged on your C2.

Try this and give me some news

David

Adamouky
Posts: 42
Joined: Tue Apr 05, 2016 3:49 am
languages_spoken: english
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Adamouky » Thu Jun 02, 2016 12:37 am

You create an application that starts onBoot then:

You execute this system command:
"ls /sys/bus/usb/drivers/usbhid"

Check what it returns:
The file you are looking for starts with "1-1" and contains ":1.0" ->The filename should have a similar pattern for you too

Then:
echo -n YOURFILENAME > /sys/bus/usb/drivers/usbhid/unbind
echo -n YOURFILENAME > /sys/bus/usb/drivers/usbhid/bind

This file correspond to the right usbhid currently plugged on your C2.

Try this and give me some news

David
Is this app works on otg port ?

Michael90
Posts: 1
Joined: Thu Jun 02, 2016 8:12 pm
languages_spoken: english
ODROIDs: C2
VU7 Plus
Has thanked: 0
Been thanked: 0
Contact:

Re: Vu7+ Touch Screen Issue

Unread post by Michael90 » Thu Jun 02, 2016 8:32 pm

has this issue been resolved yet? I just bought the VU7 plus and C2 and really need the touch to work every time as the cables wont be accessible once I've mounted it in my car.

Post Reply

Return to “Android”

Who is online

Users browsing this forum: No registered users and 2 guests