Capacitive buttons problem

Search This thread
By:
Advanced…
K

Kromann2607

New member
Feb 18, 2017
1
0
S3 mini i8190n Capacitive buttons FIX

Hello I had the same problem but now I have the fix it without problems :) this is because once you have flashed the recovery ROM for the phone. You forgot to remove the battery from the phone before trying to start the phone in recovery mode and this creates the problem of Capacitive buttons do not working.

The solution is to flash back to your backup or the stork ROM and launch the phone up and wait for 5 minutes, until the Capacitive buttons works again. then start it up in recovery mode and wipe the old system again and then install the new ROM again. Remember to wipe Dalvik cache and cache after installation and then just reboot it into the new system and then the Capacitive buttons should work again.

It worked for me so let me finally hear if it works for you too :)
 
F

FZG-87

New member
Mar 19, 2018
1
0
I am also affected by the problem. Custom ROMs disable my capacitive buttons, stock works just fine.

The problem seems to be rather rare, as I barely found anything on the topic, so I am glad to have found this thread right here!

My question: Will the Kernel patch offered above work with versions newer than Novafusion CM 12.1? Or is somebody willing to develop a similar kernel patch that works for the newer versions of CM/Lineage? That would be awesome!

Model: GT-I8190
Country: Germany
Baseband: I8190XXAMG4
 
B

BrickTop01

Member
Sep 17, 2018
6
0
Samsung Galaxy S6
Samsung Galaxy S9
FZG-87 said:
I am also affected by the problem. Custom ROMs disable my capacitive buttons, stock works just fine.

The problem seems to be rather rare, as I barely found anything on the topic, so I am glad to have found this thread right here!

My question: Will the Kernel patch offered above work with versions newer than Novafusion CM 12.1? Or is somebody willing to develop a similar kernel patch that works for the newer versions of CM/Lineage? That would be awesome!

Model: GT-I8190
Country: Germany
Baseband: I8190XXAMG4
Click to expand...
Click to collapse

Doesn't work, tried it on the 6.0.1 lineage by novafusion.

found temporary work around by activating the touch screen buttons using build.prop editor, but would really prefer the actual hardware buttons.

Open your build.prop using build.prop editor app (in /system)
press the pencil icon and then scroll down to the bottom
on a NEW line add qemu.hw.mainkeys=0
then press enter to add a new blank line at the end
Save & reboot
 
You must log in or register to reply here.

Similar threads

M
bootloader problem
Replies
15
Views
33K
Q
QuintusE
S
What's the best and trusted site to buy an unlock code?
Replies
24
Views
93K
T
Tommy Gunn
E
[Solved] Galaxy S3 mini home button problem
Replies
6
Views
14K
M
mark-1978
F
Problem with my s3 mini GT-I8190 reboot every 20 or 30 seconds
Replies
41
Views
29K
M
mr.ticko
S
S3 Mini restart/switching off by itself problem
Replies
23
Views
24K
winastotot
winastotot

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    M
    mativo
    I just found this thread. I posted a comment here in a different thread
    http://xdaforums.com/showpost.php?p=65031278&postcount=3630
    I more or less can repeat it here. In the past I had several working devices; now I got one of
    those with the buttons-problem; so I have several fully working and
    one with failing softkeys. Flashing original Samsung FW: Keys work.
    Flashing Cyanogenmod: keys don't work (repeatable).

    Now looking for official Samsung Sources I found that there is another
    package "GT-I8190_EUR_JB_Opensource.zip" with an updated Firmware and
    modified kernel driver for the touch-chip. (!!)

    drivers/input/keyboard/tc360-touchkey.c
    firmware/coreriver/tc360.fw.ihex

    Looking at dmesg at the failing device shows that there is a communication problem between the
    chip and the controller:
    Code: 
    <3>[ 98.615020] tc360 7-0020: failed to read fw ver (-6)
<3>[ 98.615081] tc360 7-0020: fail to read fw ver (-6)
<6>[ 98.615142] tc360 7-0020: retry read flash fw ver (4)
<3>[ 98.616455] tc360 7-0020: failed to read fw ver (-6)
<6>[ 98.616760] tc360_power: off (0)
<6>[ 98.720275] tc360_power: on (0)
    There are several other indications after phone reboot in dmesg

    looking into the source code and comparing the output it looks like that there is a
    communication issue with the chip when using the existing CM Nova kernel.

    The idea was it may be due to a different (newer) firmware (ver. 0x19) compared to the 0x18 in CM kernel
    which does not match to the kernel code. The changes in the driver looks like changes in timing (counters) which could
    actually explain the behaviour I see.

    I took the novafusion kernel from github and exchanged the two files from the newer Samsung source-package
    and created a kernel zip (with the help of the F-Kernel package).
    After flashing - the HW keys of the "bad device" do work now! :eek:

    So the root cause obviously was a new Firmware already existing in the Coreriver TC360 IC which
    does not work with the older kernel versions (and thus with Novafusion Kernel.
    BTW: The same most likely holds for TWRP: On the bad device the HW keys also don't work in TWRP.

    So basically the Sensors Firmware needs to match with the kernel.

    Using the new kernel+firmware would upgrade the TC360 FW as well and, consequently may require an
    kernel update for TWRP also. This would have to be tested.
    I've built a small kernel-only install package which did the work on my phone.
    Maybe I can attach it here. But I don't know how to do this.
    View
    3
    New Macław
    New Macław
    Ok, let's deal with it.

    I need your:
    - model (i8190/n/l)
    - country
    - baseband

    Maybe we can figure on which phones problem exists and then eliminate them.
    View
    2
    New Macław
    New Macław
    Ok, probably I have found a way to handle with this issue, tomorrow we should resolve it.

    Wysłane z mojego GT-I8190 przy użyciu Tapatalk 4
    View
    2
    peter_baz
    peter_baz
    New Macław said:
    Ok, let's deal with it.

    I need your:
    - model (i8190/n/l)
    - country
    - baseband

    Maybe we can figure on which phones problem exists and then eliminate them.
    Click to expand...
    Click to collapse

    i8190
    GR
    I8190XXAMD3

    also tried over I8190XXAMG4_I8190OXXAMH1
    View
    2
    A
    Antialize
    enensales said:
    it happened to me i thought it's a CWM bug, it's just a Samsung bug, reboot using the power button and it will make alright to work!
    Click to expand...
    Click to collapse

    I rebooted a lot of times and waited and couple of minutes.. now i am back to stock
    i will test the latest updates of AOKP or CM and we will see!!
    View

New posts