Fix capacitive button behavior instead of turning them off (root)

[lizaSB]

I own a W8 and I was playing around with CSC codes this afternoon trying to figure out how to call different data icons to the signal status bar. I was changing things around left and right. Imagine my surprise when on one of my reboots my capacitive buttons started displaying the same behavior as the US variants. Apparently the capacitive button behavior is in the CSC codes.

It seems that this tweak breaks Wifi Calling in its current form.

However, if you like the behavior of the buttons and don't use Wifi Calling, whereby they only turn on when you touch the buttons themselves and don't turn on every time you touch the screen, this may be a neat little trick for you to try. You can always undo it if you notice undesirable effects. There is probably no chance of bricking your device after just editing things in the csc folder so you don't have much to lose.

All you have to do is change your sales code to a device that was not manufactured for America.

If you're lazy you can flash this zip. However, the change is very simple:

In the folder /system/csc/ open the file sales_code.dat. This file probably says TMB.
Change it to one of the following codes and reboot

KDO - Koodo
TLS - Telus
RWC - Rogers
BMC - Bell

If you have disabled the capacitive buttons in the Galaxy Buttons app or in adb you'll have to re-enable them to see these changes

Everything still functions normally on my phone even after changing the sales code to TMB, and the only thing I've even noticed this change so far is the button behavior. This makes me think there is a hidden csc string somewhere and T-Mobile/VZW in their brilliance decided to enable it.

 

[mikeyinid]

Didn't change for me. Have you googled cc edits? There's all kinds of crazy stuff out there.

 

[lizaSB]

Didn't change for me. Have you googled cc edits? There's all kinds of crazy stuff out there.

cc or csc?

Interesting that it didn't work for you. So many inconsistencies out there between the variations. I'm tempted to flash a T rom now and try to make it work myself.

Would you be interested in making a backup of your csc folder and trying the stock w8?

Edit: I'm also at the moment not using the keystrings.dat file. You could also try renaming TMB_keystrings.dat as a backup and leaving it uncalled or try using my KDO_keystrings instead.

 

[mikeyinid]

Have you tried flashing 920T rom? If so, what doesn't work?

---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------

I replaced my csc stuff with yours. Don't see any difference.

 

[lizaSB]

Have you tried flashing 920T rom? If so, what doesn't work?

---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------

I replaced my csc stuff with yours. Don't see any difference.

I just uploaded my keystrings.dat also, which is called in the contents.db. You could try either removing the file entirely or replacing it with the one I uploaded

I'm rushing out the door right now and I'm not sure when I'll have time to try flashing a T rom.

My issues with the T rom might've been isolated to too much bloat removed from XtreStoLite. I'm thinking I'll give your version a try -- basically I had two issues with apps. Opera force closed on start and Pushbullet would randomly log me out thus killing push notifications. That paired with the capacitive button annoyance was enough to push me back to stock.

One last edit: one thing I've noticed is that some variants use features.xml for csc codes and others use other.xml for csc codes. Are both are variants in line using other.xml?

 

[mikeyinid]

Ours uses features and others. Others overrides features though.

 

[lizaSB]

This stuff drives me crazy! Like why can I get my shake sensor working with ambient display but you can't?

(╯°□°）╯︵ ┻━┻

 

[LNJ]

Speaking of CSC codes, I recently decided to go back to stock via Kies Firmware Recovery. Model # and SN # pulled up my correct CSC firmware which is Rogers RWC. Upon flashing, and boot, it defaulted to Bell BMC and installed the Bell apps. Plugged in and tried Smart Switch and it said phone is BMC. Did a flash via Smart Switch and same thing.
Tried full firmware flash via Odin and same deal. Defaulted to BMC upon boot even with a Rogers SIM.
Tried without a SIM inserted but no dice again.
Factory resetting in stock recovery gives you a text at the bottom something along the lines of Multi-CSC BMC activated.
None of the CSC changer apps worked on the S6 even when rooted.
Finally found the old school dialer way *#272*IMEI# and got to menu for all Canadian carrier codes including the smaller regional ones and was able to pick RWC. Phone rebooted but I didn't loose anything I had installed which was a pleasant surprise!

---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------

 

[lizaSB]

Have you tried flashing 920T rom? If so, what doesn't work?

---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------

I replaced my csc stuff with yours. Don't see any difference.

Heh heh heh. You sure you perm'd everything correctly? Mod is working perfectly for me at the moment. Just flashed your stock rom applied a bunch of changes and the lights turn off. I'm gonna reverse each step to see where exactly you ended up running into issues

 

[lizaSB]

What the... So, it boils down to this. The only change I made to turn the buttons off is changing the code from TMB to KDO in sales_code.dat

Good grief.

I dirty flashed over my w8 data, so incoming data wipe I guess.

 

[lizaSB]

@mikeyinid Freshly installed your odex'd rom, wiped all caches, data and system. Installed SU, made one single modification to the sales_code.dat and it works.

Anyone else on a T variant feel like testing this? I can see absolutely zero reason this shouldn't be working...

 

[mikeyinid]

@mrapp when I tried it earlier I only did a hot reboot, and it didn't affect anything. I just changed it again and did a full reboot. Now I'm seeing the same behavior as you. Much better ?

 

[lizaSB]

@mrapp when I tried it earlier I only did a hot reboot, and it didn't affect anything. I just changed it again and did a full reboot. Now I'm seeing the same behavior as you. Much better

WOOO!!!:good::laugh:

 

[piccit]

I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'

 

[mikeyinid]

I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'

Indeed it does.

 

[lizaSB]

I think this breaks Wifi Calling. After changing to KDO, it would just get stuck on 'enabling'

You could try using rwc. You also may need to add a csc code? I had a feeling this would happen.

 

[lizaSB]

I don't have time to look into this this morning, but if any one wants to take a look, there are two places I'm going to look. Features.xml in XtreStoLite s5 and the xtrestolite in the dev s6 forum. Or perhaps @edgarf28 would be able to chime in

 

[lizaSB]

I had 2 seconds to look here -- I will look more in depth later. Does this CSC code do anything to help?

<CscFeature_IMS_EnableRCSe>true</CscFeature_IMS_EnableRCSe>

Turn off wifi then disable wifi calling, then re-enable wifi connection.

 

[lizaSB]

@mikeyinid @piccit Can you please try adding this line to your features.xml or others.xml?

Assuming you guys still have the stock features.xml, everything you need should still be there. We don't have wifi calling up here and it may be that it never works. Rogers is a network that is/will be supporting VoLTE, so changing to RWC as your code might be something to try if you havn't tried that code yet.

<CscFeature_WFC_EnableSamsungWfc>true</CscFeature_WFC_EnableSamsungWfc>

Then just make sure you try cycling wifi calling as such:

Turn off wifi then disable wifi calling, then re-enable wifi connection.

Is VoLTE still working?

Unfortunately, I have no way of testing this service. I *do* have a t-mobile sim though. However, my device is locked to Koodo and popping in my sim still produces and Error: Invalid Sim for me

 

[LNJ]

@mrapp, on stock RWC, button only lights up when you touched them and stayed off when you were just touching the screen!
Saying that, when I owned the Optimus G, it worked this way on ICS and when the Rogers update for JB came out, it remained on as long as you were touching the screen and I had to flash an Australian KDZ for it to stay off after 1.5 secs!