yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Q&A, Help & Troubleshooting] MarcEcko:
It may seem offtopic, but it actually isnt:

In some devices capacitive buttons begin to fail as soon as you flash your phone!. If anyone with a failing phone is in doubt, go ahead back to stock and try rooting (be it by flashing with ODIN or installing as update.zip from recovery).

In my case, as soon as I flashed recovery (either CWM or TWRP, any version) the capacitive buttons started failing, and would work intermittently, then after a small period (around 3-5 minutes) they would begin functioning normally.
[Galaxy S III Mini Q&A, Help & Troubleshooting] nghiroshi:
Did not work for me, there are no such paths:

/sys/devices/platform/i2c-gpio.7/i2c-7/7-0020/leds/button-backlight/ /sys/class/leds/button-backlight/
[Galaxy S III Mini Q&A, Help & Troubleshooting] robindebruin:
Mines are rondom lighting up
[Galaxy S III Mini Q&A, Help & Troubleshooting] JuanDarien:
CM 11 - 10-12-13 - also problematic

i've tried fresh install 4 times already (or what i think its a fresh install, im very new at this), with the stock room works, but with the last release of CM 11 from Maclaw (from today, 10/12/2013) does not work at all.

the ROM is the best i`ve seen, but the capacitive buttons dont work and im gettin desperate! i dont know what to do!

has anybody found a solution?

Thanks!! a lot !

From Argentina!
[Galaxy S III Mini Q&A, Help & Troubleshooting] irufun:
you can edit build prop to use screen button
[Galaxy S III Mini Q&A, Help & Troubleshooting] JuanDarien:
Genius!!!!

its not the best solution ever, i would like to use the softkeys, but its better than been unable to go back on a web page!

you are great, thanks!
[Galaxy S III Mini Q&A, Help & Troubleshooting] irufun:
we just hope developer build/fix the kernel for now ;)
[Galaxy S III Mini Q&A, Help & Troubleshooting] djrebell2006:
The best solution for me -> i will buy me another phone ... :):D
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
I have the same problem... my back and menu button hardware doesn't work... but they are okay when flashing with a stock rom...

French model...I8190XXAMG1 baseband... Does someone have a solution ?

Thanks !
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
Please Maclaw, Have you a way to fix that bug... still no capacitive buttons working... So annoying...

Do u even know if it is related to TWRP/CWM or to the kernel ?

Pleaaasee :)

Thanks for amazing work you do !
[Galaxy S III Mini Q&A, Help & Troubleshooting] djtom1:
Send PM to Maclaw
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
I\ve done... but no answer... Do u no if this is planned ? Also, my phone reboot when receive a SMS... I saw many people having this trouble too... Do u know something about resolution of these ?

Cheers !
[Galaxy S III Mini Q&A, Help & Troubleshooting] alexvv:
i also have these two problems, when a sms arrives my phone reboots and cap. buttons don't work on any custom rom which is a kernel related problem.. it's samsung's fault and i think it's solvable but only by some good developers...
[Galaxy S III Mini Q&A, Help & Troubleshooting] allywilson:
Same issue

Rooted stock, installed CWM 5.5, then installed Maclaw's TWRP and finally CM11 2014-01-09 build.

No more capacitive buttons (even in TWRP).

Updated to CM11 2014-01-10, no change.

Moved to AOKP 2014-01-11, no change (full factory wiped).

Model: GT-I8190 (although it is actually GT-I8190N)

Baseband: I8190NXXAMG3

Country: UK

Using the build.prop method to get the virtual buttons in the mean time ( I did it through adb shell instead of the file manager though).

Hope this is addressed eventually, I thought I was going to have to back to stock until I found the build.prop hack.
[Galaxy S III Mini Q&A, Help & Troubleshooting] LMH1998:
Is there a solution yet?
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
I think there is no other solution than using the 'hack' of build.prop.... It must be related to kernel 3.0.101... But please if someone have a solution... Tell us ! Please Maclaw... help !
[Galaxy S III Mini Q&A, Help & Troubleshooting] ramoneiggy:
Could you please explain how to do the hack
[Galaxy S III Mini Q&A, Help & Troubleshooting] joker79:
try like this. to me work

Set the capacitive light on setup to clouse after 6 sec, if is set up to 1,5 sec you have problem with capacitive butons becouse are kernel issues. Led light and comand of capacitive butons don't interactive property.
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
I was talking about open the file '/system/build.prop' (using root browser for example...) and add the line :

qemu.hw.mainkeys=0 in this file and then reboot... Your buttons will not work better but u'll have a navbar ;)
[Galaxy S III Mini Q&A, Help & Troubleshooting] ramoneiggy:
Thanks, it's better now

Do you know how to customize the look of navbar?
[Galaxy S III Mini Q&A, Help & Troubleshooting] LMH1998:
Still want a fix...

PLEASE MACLAW!
[Galaxy S III Mini Q&A, Help & Troubleshooting] ramoneiggy:
Found this app Ultimate Dynamic Navbar

A good enough solution until someone fixes the problem

https://play.google.com/store/apps/details?id=com.mrbimc.udn.lite&hl=hr
[Galaxy S III Mini Q&A, Help & Troubleshooting] LMH1998:
Thanks dude! I really hope someone fixes it!
[Galaxy S III Mini Q&A, Help & Troubleshooting] darkbluesea:
Problem: Capacitive buttons stop working after custom rom install, at least all roms from maclaw.pl up until 2014-03-03

With custom ROM:

Phone model: GT-i8190

Baseband version: I8190NXXAML1

ROM version: 11-20140302-UNOFFICIAL-golden

With original samsung ROM:

Phone model: GT-i8190N

Baseband version: I890NXXAML1

Android Version: 4.1.2

Wipe?

Factory reset

Cache

Dalvik cache.

Rebooted several times, not from recovery.

What steps will reproduce the problem?

Install any non vendor rom

Capacitive buttons stop working (those that light up).

Although, my roommate, got another phone equal to mine (same model/carrier) and the buttons worked on his phone.

That is, after installing the same custom roms, after reboot, out of the box working buttons.

If you need me to run any other kind of log gathering or try editting some sys files, let me know
[Galaxy S III Mini Q&A, Help & Troubleshooting] LMH1998:
This problem is on a few S3 mini's, there is still no solution for it :( Use on screen buttons.
[Galaxy S III Mini Q&A, Help & Troubleshooting] stolla:
Same Problem :(
[Galaxy S III Mini Q&A, Help & Troubleshooting] Pro100Nikto:
BLN Support

Maclaw,please, try send CM Kenrel withount BLN Support.I think that the problem is caused by this feature...
[Galaxy S III Mini Q&A, Help & Troubleshooting] djtom1:
Maclaw don't read this topic, send Him pm or talk via www.maclaw.pl
[Galaxy S III Mini Q&A, Help & Troubleshooting] dreamH6:
same for me :(
[Galaxy S III Mini Q&A, Help & Troubleshooting] alexvv:
it's not a 3.0.101 kernel issue, any change of kernel will "destroy" the capacitive buttons even if for instance you flash the golden kernel or the bln kernel wich are based on stock but there are still modified.... maclaw says now he's fixed this but mine are still dead....
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
mine are still dead too... No patch yet ?... It's been a while now...
[Galaxy S III Mini Q&A, Help & Troubleshooting] dreamH6:
mine too, but I found a workaround.

Turn on navigation bar editing build.prop.

Install Xposed toolbox

Install module "123 Dimension editor" and reduced bar to 24 dot
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
update?

any update guys? is there a fix?
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
Not yet.... I think novafusion (ex-maclaw) team will never solve it... I sent so many mails for this problem... I also purpose them to send my phone for help them find the bug... No answer... Too bad man... Use navbar forever :s
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
Thanks for the response

I've also sent them e-mails but no answer too! This problem appears only on "N" variants of S3 mini :silly:
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
No, mine isn't N and it doesn't work.... I think the complexity of version affected is one of the problems to solve that issue... That's why I purposed to send my phone... :s
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
L then?

is your phone L variant? Then something strange happens
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
Nope, mine is i8190... Neither L nor N variant... Also, my phone reboots everytime i receive a notification when BLN is enable... Dunno if it can help debugging but...
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
Ok, got it, I have seen devices on youtube where capacitive button work, every device behaves with a different way

Sent from my GT-S7275R
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
Ya, I think it's a tricky bug.... :x I'd like to help solving it but dunno how... :s
[Galaxy S III Mini Q&A, Help & Troubleshooting] 4tis:
Well, I've spent hours this week trying to figure put how to enable the buttons,

Now I'm using enox revenge ROM (and love it!) but it doesn't support OTG (I want to use my microUSB pendrive) * :(

Maclaw's cyanogenmod does, but unfortunately buttons are out of order... -_-

Maybe someone could compare the ROMs and find out how to solve th "buttons problem",

greets

P.S. If anyone know how to enable OTG on enox's mod (i've tried all soft from market with no luck) - please send me PM

_______________________________

S3mini i8190N , Enox Revenge ROM
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
Kernel Issue

you can't have usb-otg with this rom, because it's kernel does not support it! you need to modify it by adding usb-otg support
[Galaxy S III Mini Q&A, Help & Troubleshooting] talski:
I was facing this problem, so i've found that in my case it was related to Google Keyboard, then I switched to SwiftKey and the problem has gone
[Galaxy S III Mini Q&A, Help & Troubleshooting] kotzir:
when switched to swiftkey, capacitive buttons worked?
[Galaxy S III Mini Q&A, Help & Troubleshooting] talski:
Exactly
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Any news on this?

Anybody know what the problem is exactly? :rolleyes:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
Can someone install TerminalEmulator please and give the Output from:

cat /sys/class/leds/button-backlight/brightness

Send from OnePlus One using Tapatalk

---------- Post added at 06:01 AM ---------- Previous post was at 05:54 AM ----------

Also please

ls -l /sys/class/leds
ls -l /sys/class/backlight

Send from OnePlus One using Tapatalk

Edit:

Someone tried replaceing

system/lib/hw/lights.montblanc.so

With the one from Stock?
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Novafusion newest CM11:

ds/button-backlight/brightness <

/system/bin/sh: cat: /sys/class/leds/button-backlight/brightness: No such file or directory

1|u0_a54@golden:/ $ ls -l /sys/class/leds

u0_a54@golden:/ $ ls -l /sys/class/backlight

lrwxrwxrwx root root 2014-09-06 00:30 panel -> ../../devices/mcde_disp_s6e63m0_dsi.0/backlight/panel

u0_a54@golden:/ $

-------------------------------------------------------------------------------------------------------------------------------------------------------------

I tried replacing system/lib/hw/lights.montblanc.so with the stock one and no change after reboot.

There are more lines in the stock lights.montblanc.so - 10 more. I have uploaded them - one of them is from ParanoidAndroid from NovaFusion since it was what i had not ODIN formatted.

I will try to copy paste /sys/class/ folders in CM11 from stock?

Thanks for your help!:highfive:
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
try:

ls -l /sys/devices/platform/leds-regulator/leds

also:

su
find -name *brightness
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Novafusion CM11 Newest:

s/platform/leds-regulator/leds <

/sys/devices/platform/leds-regulator/leds: No such file or directory

1|u0_a54@golden:/ $ su

root@golden:/ # find -name *brightness

./sys/devices/mcde_disp_s6e63m0_dsi.0/backlight/panel/brightness

./sys/devices/mcde_disp_s6e63m0_dsi.0/backlight/panel/actual_brightness

./sys/devices/mcde_disp_s6e63m0_dsi.0/backlight/panel/max_brightness

root@golden:/ #

---------- Post added at 03:04 AM ---------- Previous post was at 02:55 AM ----------

I just have to say that it's not only the light but the buttons themselves that do not work either. :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Raeshabu:
+1

I've tried VanirAOSP and Omni. Capacitive buttons not working in both of them.

Tried also playing with /system/USR folder, to no avail. :confused:

All stock-based ROMs have working capacitive buttons.

Hope the devs could resolve this bug. :angel:

My device:

Model: GT-I8190

ROM: golden_guy's OmniROM

Baseband: ANF3

Kernel: Omni? Or stock. IDK. Probably stock, if Omni does not change it. :o
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Did the logs get you guys any leads? :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
It's hard for me to say, I don't actually own or build for this device. I build for a very similar device; the T599N.

I'd like to see a dmesg on a fresh boot.

su
dmesg > /sdcard/dmesg.log

Post dmesg.log here...

Hopefully the touchkey driver will tell us it's problem...

EDIT: Forgot you were doing this from terminal app. Changed code above.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=4400604]Meticulus[/MENTION] maybe bln in kernel causes the problem?

I can build one without bln for testing.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
Could hurt... I don't think BLN is the problem but I could be wrong. The touchkey driver registers as leds class device much before it registers for BLN. That makes me think that it should show up in /sys/class/leds even if there was a problem with BLN...

It's worth a shot though.:good:

here is the probe for the touchkey driver:

https://github.com/andi34/android_k...drivers/input/keyboard/tc360-touchkey.c#L1637

There are all kinds of message that would show up in a dmesg if there was a failure. I was hoping we would see one of them...:cowboy:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=4400604]Meticulus[/MENTION] i will upload 2 kernel here in next hour.

Send from OnePlus One using Tapatalk

Edit:

First Test-Kernel attached.

Should work on all Custom 4.4.4 Roms

Edit:

Uploaded Second Test-Kernel also.

Will Work on all Custom 4.4.4, will also boot Stock 4.1
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Ah okay well i and others really apreciate any help we can get! :victory:

dmesg.log on NovaFusion CM11 fresh
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
I tried both kernels on NovaFusion CM11 and unfourtnately no difference :( i let the phone down for 5-10 minutes with each kernel to make sure.

I flashed them in NovaFusions TWRP 2.7.1.0.

I use yours regulary the 2.8 version works better for me. :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
Thanks for the dmesg. It makes things a lot clearer. I filtered the dmesg to only show messages from the touchkey driver and it becomes clear that there is a firmware problem... I'm am not sure what can be done about it. I'd really need to have the device to do some testing but the first thing I would try is to disable the firmeware upgrade functionality so see if it would work with out it. As you can see from the log it seems to detect the keys just fine but then tries to "upgrade" the firmware or something; then the driver fails :confused:

Perhaps simply trying other firmwares from other similar devices might help too. ( don't ask me where it gets this firmware :confused: ). Perhaps the firmware is included in the stock rom somewhere?

[MENTION=5153662]Android-Andi[/MENTION]

You might try commenting this line out. The "built-in" firmware seems to load fine but the "firmware updater" seems to find and updated firmware somewhere, flashes it and that causes the problems:

https://github.com/andi34/android_k...drivers/input/keyboard/tc360-touchkey.c#L1780
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
Thx [MENTION=4400604]Meticulus[/MENTION] i will comment it out and rebuild.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
If that doesn't work then, I found the firmware that it is referring to:

https://github.com/andi34/android_kernel_samsung_golden/blob/kk4.4/firmware/coreriver/tc360.fw.ihex

Might look for other versions of that file...:good:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
Another testkernel.

I commented out the line [MENTION=4400604]Meticulus[/MENTION] mentioned.
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
I would lend you mine but you are in America and im in Denmark :(

---------- Post added at 11:53 PM ---------- Previous post was at 11:51 PM ----------

I tried it and it will not go past Samsung Galaxy S III Mini - GT-I8190N screen and the buttons blink 3-4 times and it then bootloops.

I think you guys are on to something! :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] :
Well, that's all I really got... Its just going to take some experimentation with the driver or finding the right firmware to see if it can be fixed... :good:
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
I will make a diff with N kernel source

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Would it help if you had AirDroid access to my phone?

I thank you guys for all the help regardless! :)

---------- Post added at 12:32 AM ---------- Previous post was at 12:31 AM ----------

Sounds good - will AirDroid access help? :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
I diff around a bit and talk to [MENTION=4400604]Meticulus[/MENTION] tomorrow.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
[MENTION=4316190]hedgegee[/MENTION] can you test my test 2 kernel on Stock?

Maybe missing a blob or need different?

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Sure! What should i test? That the buttons work and a dmesg log? :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Android-Andi:
Test if the buttons work. If they do work, then we need to check the proprietary files.

Send from OnePlus One using Tapatalk
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Okay i just install the kernel 2 test and the buttons do NOT work :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] Guik331:
Sort of solve

I apologize in advance for my English. I had the same problem in CM (all versions). And any way to solve it. Wipes, any ROMs except stock, kernels and other advices did not help. Cfpacitive buttons worked ONLY on stock ROM! And then I accidentally broke the screen. I handed it in for repair. Two weeks later, I got a working unit. After this procedure my capacitive buttons work normally!!! So it`s absolutely a hardware bug! I understand that this is very expencive decision. But it works. I don`t know what Samsung do to force capasitive buttons work in "buggy list" of S3 mini`s in stock ROM? Maby they knew a secret)))

Also I want to enumerate the list of problems I encountered when i have this bug:

- Reboots on incoming notifications when BLN is ON (just turn it off and all will be fine)

- endless ROM installing in TWRP (nomatter what version)

Now I have no any problems. And I hope you will be able to solve this problem on software level. Becouse Samsung do it) Good luck!
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Yeah i dont agree with it being a hardware bug when it works on stock. It might be a software "error" in the keys or something but they are functional.

But i think im going to try and return the phone for a different one and maybe i get lucky with it working on custom rom.

[MENTION=5153662]Android-Andi[/MENTION] do you need anything else before i return the phone - maybe you have an idea of the error? :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] bilboquet:
Do you finally change your phone ? Did it solve the problem ? Too bad for me... Garantee expired.... :/ I'd like to help solving this problem too...
[Galaxy S III Mini Q&A, Help & Troubleshooting] hedgegee:
Yes I got the phone back and it works with the new buttons/screen. As far as i got told it is a firmware in the keys (dont know if it has firmware in the keys :laugh: ) problem and NOT a hardware problem.

Anyways i think you should continue to see if it can be fixed - maybe [MENTION=5153662]Android-Andi[/MENTION] can help further?
[Galaxy S III Mini Q&A, Help & Troubleshooting] WoBble12:
Hi everyone!

I seem to have the same problem, still no fix to it? can't send it back to exchange it, I have no more guarantee :(

If smn can help ...
[Galaxy S III Mini Q&A, Help & Troubleshooting] 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:

<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! :o

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.
[Galaxy S III Mini Q&A, Help & Troubleshooting] pi_key:
solution firmware capacitive buttons back / menu

[MENTION=6949316]mativo[/MENTION]

That sounds like a great solution for this huge problem!

It is possible to attach to your posts with the button in the "advanced" posting mode next to the smileys.

Or maybe upload it anywhere else and share the link?

Would it be possible for me as a noob to fix the problem then?

(novafusion CM11 for gt-i8190)

Also:

Would this maybe even fix the problem with the crashes/reboot when the screen is off and notifications come up for sms or something else? :confused:

Im VERY MUCH looking forward to it!!11 :fingers-crossed::fingers-crossed::fingers-crossed: