Develop Bugs

Volume Keys Feature

Hey all, I am an iphone convert. Recently purchased the HTC outright. Great phone. Coming from a jailbroken iphone there are a couple of features that I miss. They're not deal breakers but they are really convenient in my opinion..
I love using my phones as a media player. And although there's no equalizer on the desire, I think the quality is pretty good assuming you're using reasonable earphones.
I found an app on cydia for iphone which reassigned my volume rocker.
If I just tap the volume up or down, it changed the volume as normal.
If I hold the volume key up or down, it skipped the track forwards or backwards.
I was hopeful that a developer might see this as a good addition to the Desire and be able to emulate such a function for the volume keys.
Thanks!

Hmm i'm guessing that you don't use the stock headphones with inline controls then. I'm hoping when the device is rooted a lot of hacks should surface. I want to use the optical trackpad press to bring up the lockscreen for instance. And a flashlight app that actually uses the flash and not a bright white screen lol.

nope. Those earphones are way to large for my ears! I can't even fit the buggers in!
But I agree, being able to wake the phone with the trackpad is a must.
Here's hoping sooner rather than later

ephumuris said:
Hmm i'm guessing that you don't use the stock headphones with inline controls then. I'm hoping when the device is rooted a lot of hacks should surface. I want to use the optical trackpad press to bring up the lockscreen for instance. And a flashlight app that actually uses the flash and not a bright white screen lol.
Click to expand...
Click to collapse
drewsta_j said:
But I agree, being able to wake the phone with the trackpad is a must.
Click to expand...
Click to collapse
Grab the application "No Lock" from the market - works perfectly on my Desire.
drewsta_j said:
Hey all, I am an iphone convert.
Click to expand...
Click to collapse
drewsta_j said:
If I just tap the volume up or down, it changed the volume as normal.
If I hold the volume key up or down, it skipped the track forwards or backwards.
Click to expand...
Click to collapse
Excellent idea. There is currently application with proves key rebinding is possible without root (Tasker), unfortunately it doesn't have volume keys and I do not have time now to try implementing a solution for this.
I will personally look into this in a month (extremely busy atm) as a hobby, and hopefully the device will have been rooted by then making this definitely possible. I'm not an amazing dev., but I can hack around to make things work

Went from Dream to iphone, but Android pulled me back with the Desire.
We are all waiting for root indeed! Shouldn't take too long I reckon. It is definately a must to wake up on menu/trackpad or home key. Anyone has some ideas?
No lock also bypasses the lockpattern, too bad. And it looks as if it runs in the background and only turns off the screen. Feels like it wil drain the battery, but maybe I am mistaking.

NoLock is okay, but any key turns the screen on. This could be a pain if it's in your pocket and you accidentally press the volume keys, for instance.
When I had the tweak that allowed me to skip tracks with the volume keys, it took away most of my needs to turn the screen simply to skip tracks. This helped save the battery.
Not only that, it also helps if you are running a different application. You wouldn't need to go back to the home screen to use the widget.
Just a couple more benefits

Hi all,
My 1st post on xda
I'm no developer, and haven't coded anything since ages, but after some digging I think may be possible to implement such a feature.
According to the android developer reference on (sorry, I'm a new user so I can't post links)
KeyEvent
KeyEvent.Callback #onKeyDown
Dialog #onKeyDown
And those forums (search for this on google)
anddev org disable_volume_keys-t10191.html
google groups android developers Long-press hard volume keys
Tell me if I'm wrong, but those links indicate that it is possible to replace the behavior of a key press ("intercepting" it before it gets interpreted by the system that changes the volume setting). Then once you intercepted it, you can check if it is a normal key press (short), in which case you would still allow to "forward" the information to the system. BUT, if you detected that it is a long press, you activate the action "next track" and do not forward the volume information to the system.
Something like (syntax is nor correct, of course)
Code:
public boolean onKeyDown(int keyCode, KeyEvent event) // the way I understand this line, it will replace the default behavior of the onKeyDown routine
{
if (keyCode == KeyEvent.KEYCODE_VOLUME_DOWN // if the key pressed down is vol_down
...
if the key press is long // don't know the code for that
do the action for next track
return true; // means that you do not forward the keypress to the system
else // if the keypress is not long
return false; // you have not intercepted the keypress, so you forward it to the system
...
else return super.onKeyDown(keyCode, event); // if any other key is pressed, forward it directly
}
Any opinions on that? Is the xda forum the right place to talk about code, or are other forums more suited to discuss about that?

Interesting..
If the code looks like that I might have to take up a hobby in learning how to code. It doesn't appear to be tooo difficult at all.
It does look like you may be on the right track there Bricolo_fr..
Cheers for looking into it.
Drew.

I see a potential problem though. You'd need to know what media playback program is actually being used, and it needs to support receiving messages from other programs so that you can tell it to skip to the next track. This might even require different coding for every player program available, if they receive messages in different ways.
In other words, you could end up having to write your own media player program.

FloatingFatMan said:
I see a potential problem though. You'd need to know what media playback program is actually being used, and it needs to support receiving messages from other programs so that you can tell it to skip to the next track. This might even require different coding for every player program available, if they receive messages in different ways.
In other words, you could end up having to write your own media player program.
Click to expand...
Click to collapse
Ok, well surely there must be a simple solution?
Why can't we say create an app where you could select which media player you are using (only have a few of the main ones) then we would be able to amend the code as per which option they select before it was implemented?

drewsta_j said:
Ok, well surely there must be a simple solution?
Why can't we say create an app where you could select which media player you are using (only have a few of the main ones) then we would be able to amend the code as per which option they select before it was implemented?
Click to expand...
Click to collapse
Sure you can do that; buy you'd have to examine each of those apps, work out if they accept messages, and work out what format said messages need to actually be in.
One would hope they would implement standard interfaces, but that's all it is, a hope.

Well personally, I use the stock player. It ain't the best but it gets the job done. So if it was just created for that at least I'd be more than happy

Thanks for the comments.
FloatingFatMan you are indeed right. I didn't know that all media players don't behave the same. So not all of them accept incoming messages, and not with the same protocol? Hum...
Does that mean that widgets for media player control are only compatible with a specific media player, also?
About the code itself, do you guys think can work?
I'm quite new here, is xda a place about writing code or should we discuss that in another place where people are more used to that?
Cheers

now that the Desire can be rooted...
on the Nexus one (probably other devices too) with the cyanogenmod roms, this feature is availale. just long press vol+ or vol- and you get next/prev track
can this be done with a moded rom on the desire also? what kind of changes need to be applied to the stock rom to add this function?

Bricolo_fr said:
now that the Desire can be rooted...
on the Nexus one (probably other devices too) with the cyanogenmod roms, this feature is availale. just long press vol+ or vol- and you get next/prev track
can this be done with a moded rom on the desire also? what kind of changes need to be applied to the stock rom to add this function?
Click to expand...
Click to collapse
Agreed. am really liking forward to his feature now the phone is rooted.

ephumuris said:
Hmm i'm guessing that you don't use the stock headphones with inline controls then. I'm hoping when the device is rooted a lot of hacks should surface. I want to use the optical trackpad press to bring up the lockscreen for instance. And a flashlight app that actually uses the flash and not a bright white screen lol.
Click to expand...
Click to collapse
You can try Flashapp on the Market. I can post URL yet but you'll find it...]

Another excellent example that long press on a hardkey can be implemented without root is Quick Settings (great app btw): it can be brought up anytime, no matter what app you are running by longpressing the search key.

Did anyone ever get any further with this?

ephumuris said:
And a flashlight app that actually uses the flash and not a bright white screen lol.
Click to expand...
Click to collapse
Apologies as I know it's a bit OT for this thread, but just wanted to make sure you were aware of the LED Desire Light app (http://www.appbrain.com/app/nostovic.android.desire.ledLight) - the latest version even has a nice wee widget to put the flash on/off, but the main app also offers SOS and turning text into Morse code!!

oxygen mod - based on cyanogen has:
* Skip tracks with long press volume up/down
http://forum.xda-developers.com/showthread.php?t=829734
update: it's a cyanogen feature, so all mods based on cyanogen have this
it works with screen locked.

[Q] Can't remap optical joystick?

Besides editing the .kl files, is there something else I need to do to remap the click function of the optical pad? I don't seem to have any success so far...
In both the incrediblec-keypad.kl and qwerty.kl files, the following line exists:
Code:
key 232 DPAD_CENTER WAKE_DROPPED
I have tried simply changing "DPAD_CENTER" to "CAMERA" (in both files) and then rebooting, but the phone does not behave any differently. If I use this same procedure for a different key (like Volume-Up, for example) it works perfectly. Is there something else in the framework that is preventing remapping of the optical click though?
For what it's worth, I'm running Virtuous 3.0.1... though given the fact that I can remap other keys, I'd assume it isn't a ROM issue

I tried the exact same thing. My one problem with this phone is that I can't bind something to this key. I would LOVE to get it to load the camera. I made a thread a few weeks ago, but no one responded. I was thinking making dpad_center isn't actually the right identifier for this key? BUMP!

I wish I could find a way to wake the phone up consistently with the track pad.

1967ls2 said:
I wish I could find a way to wake the phone up consistently with the track pad.
Click to expand...
Click to collapse
I second this
Sent from my Incredible using XDA App

Gahh Its Lee said:
I second this
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
There's a forum dedicated to this tweak
I'm using it now
Sent from my ADR6300 using XDA App

Search optical joystick wake
Sent from my ADR6300 using Tapatalk

So no one has any solutions for mapping the camera to the optical click?

intenselyinsane said:
Search optical joystick wake
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I ran a search for "optical joystick wake" and I don't seem to be able to find the thread you are referring to.

From forum.xda-developers.com/showthread.php?t=825511[/url] it appears that key 232 is incorrect. It should be key 272.

Runawaycoder said:
From forum.xda-developers.com/showthread.php?t=825511[/url] it appears that key 232 is incorrect. It should be key 272.
Click to expand...
Click to collapse
Thank you very much! That is quite helpful. Let me try some experiments on my end and see if I can get this working now...

First off, let me offer major thanks to TheLynxy for clearing up the whole 232/272 thing: I was wondering why rebinding the optical trackpad click never did anything (I was leaving it at 232)
What I've always wanted to do with mine was map it to be a camera button. It would seem that still does not work, even now using the correct key #
If I use the following, nothing at all happens (the phone doesn't even wake up)
Code:
key 272 CAMERA WAKE
Interestingly, however, using the FOCUS command instead will wake the device, but still does not start the camera (even if the camera is already running in the background)
Code:
key 272 FOCUS WAKE
TheLynxy said:
When the phone is on, the trackpad behaves like normal, eg the active application decides what the button does.
Click to expand...
Click to collapse
This is another interesting point about the whole thing. It seems like this is a button that is really on lockdown by the phone.
So while some progress was made, I still can't get the camera functionality I wanted. Oh well.

[Q] Circle button recognized as back button and not acrual game button

Here's my problem: ever since I flashed CM7 and tried to tolerate all the FXProject defects (eg. No touchpads for Dead Space, no camera, no haptic feedback /vibration, no flash, etc.), there was one of those defects that really hurt me from inside... the fact that the circle button is treated ONLY as a back button, and not a game button. I'm aware there are files in the internal flash memory that set the phone's key layout (/system/usr/keylayout/) but I'm just to lazy to figure it out so I'll leave the question to the pros on the forum: How to fix it? I bought this phone considering I'm a dedicated gamer (still have a life tho ) and not being able to kick the opponent's face in Bruce Lee and every other kind of silly stuff you could do with this epicness we call Circle button is just pathetic. You could send me the Original stock rom key layout file(s) so I can replace/compare and fix. Thanks in advance

For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk

AndroHero said:
For starters i'm sure FXP is sorry you have to "Tolerate" all his hard work second the O button acts as the back button on stock too. It's just these games are meant to work in conjunction with sony's software. Remove that and replace it with a rom built from source and thats what you get.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks

DanielEGVi said:
Firstly, I somehow understand that part of "remove that and replace it with a rom..." and now the part I didn't understand pretty much, "...built from source". I understand everything has to be compiled from source code to be executed, but as a noob, I simply didn't understand, could you explain?
Secondly, I downloaded an app from the Market called "Xperia Play Test" that showed up what buttons are pressed in the screen and when I press the circle button it appears next to the physical back button showing up as "back", haven't tried yet on stock rom andsee what happens.
Third, I really think fxp did a good job bringing such a nice rom onto the Xperia's, which gives you simple2ext, theme engine, power bar widget and other cool stuffs, which is why I haven't decided yet to revert to stock.
Anyways, just explain that 'rom built from source' thingy please. Thanks
Click to expand...
Click to collapse
On the pad, the default android actions are X=Ok or select and O=Back, Xperia play optimised games work in conjunction with the sony firmware to ignore the default android action while in a game thus allowing you to use the buttons for game inputs. If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
"Built from source" just means the rom was compiled from the source code provided by the Android open source project (Asop)

AndroHero said:
If you remove the sony software, many of these games can no longer ignore the default android action rendering the O button useless in most cases. This is nothing to do with cyanogen nor can it be fixed as it's not a bug.
Click to expand...
Click to collapse
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.

DanielEGVi said:
So, basicly, I can't do nothing for it, and while I have cyanogen the O button is rendered useless, unless I use stock? Or is there any other whatnot that can ignore the O button? Or disable the back function so the key is still recognized by the app? I can live without using the O button as a back button.
Click to expand...
Click to collapse
It dosent happen for every game. For example gameloft games can use the O button no probs. Maybe you can get the results you want with a button mapping app. I think there is one in themes and apps

BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?

johnsongrantr said:
BUMP:
sorry to resurrect this thread, but this is still a problem, I'm working on a JXD S601 that uses AOSP and I've hit a wall with modifying the qwerty.kl on that device trying to get back/circle to function the same as stock xperia play.
As stated in this thread, the problem is app specific, most operate fine with BACK and others do not, Trying to change it to BUTTON_A (what I determined to be the translated input by viewing the stock qwerty.kl file) does not fix this either.
I have cyanogenmod on my play and I recognize it as a problem on that device as well. Is it possible we can get some assistance looking into what is wrong here?
Click to expand...
Click to collapse
It is STILL a problem, but this thread will die and nothing will stop that. Sorry.
I already gave up and flashed Stock ROM and with lots of effort I have found nothing on the interwebs that serves as a fix to the O button. That's sad isn't it.

I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway

jacklebott said:
I'm not on CM, but have you tried changing the appropriate keylayout file in /system/usr/keylayout/ from "BACK ALT WAKE_DROPPED" to "BUTTON_B"? Cuz with it set to BUTTON_B, it's still recognized properly in-game on the stock ROM but doesn't act as the "Back" button anymore
You said you tried changing it to BUTTON_A but that's wrong anyway
Click to expand...
Click to collapse
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...

DanielEGVi said:
Oh really? I thought BUTTON_A was square and BUTTON_B was triangle...
Click to expand...
Click to collapse
Nope, square is BUTTON_X and triangle is BUTTON_Y

i meant button_b but regardless, the keylayout is identical to the stock on aosp. I think the problem might be in the kcm binaries rather than the keylaout files. It's a theory I'm looking into

[Q] Enable Software Buttons

Is there any way currently to enable software buttons on this phone? I just can not stand capacative buttons, they are simply awful in my opinion.

edda123 said:
Is there any way currently to enable software buttons on this phone? I just can not stand capacative buttons, they are simply awful in my opinion.
Click to expand...
Click to collapse
The only way I see enabling them is by enabling One Hand Mode. Of course the screen size is reduced then. With root it may be possible.

If rooted, you can try this:
http://www.gizbeat.com/2021/disable-or-enable-the-on-screen-virtual-software-keys-in-android/
There are also a few 3rd party apps that may help on Play.

Maybe it is worth buying this phone if I can fully disable the capacative buttons. Root is something I always acquire so that wouldn't be an issue. Exciting!

edda123 said:
Maybe it is worth buying this phone if I can fully disable the capacative buttons. Root is something I always acquire so that wouldn't be an issue. Exciting!
Click to expand...
Click to collapse
This works with JB and KK. Not sure about LP and ZenUI. I can give it a try for you.

Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.

Disabling capacitive buttons
Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
In order to disable those annoying you need to edit "system/usr/keylayout/ftxxxx_ts.kl" rather than formers... As you know commenting those lines :
# key 158 BACK WAKE VIRTUAL
# key 102 HOME WAKE VIRTUAL
# key 139 APP_SWITCH WAKE VIRTUAL
:good:

Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
When I went to build prop to add it, it was commented out. I deleted # but still no softkeys

lordpipa said:
When I went to build prop to add it, it was commented out. I deleted # but still no softkeys
Click to expand...
Click to collapse
Edit the model number prop. If you have the 64GB/4GB WW version, go into:
build.ze551.dual.2p3GHz.prop
Add the line there
Code:
qemu.hw.mainkeys=0
Reboot and enjoy soft keys.

Harfainx said:
Edit the model number prop. If you have the 64GB/4GB WW version, go into:
build.ze551.dual.2p3GHz.prop
Add the line there
Code:
qemu.hw.mainkeys=0
Reboot and enjoy soft keys.
Click to expand...
Click to collapse
I have the 4gb/32gb. Still the same place?

lordpipa said:
I have the 4gb/32gb. Still the same place?
Click to expand...
Click to collapse
Should be if it's the 2.3GHz version (which I think all 4GB RAM builds are).
Give it a shot. Worst case scenario... Nothing happens and you try a different prop.

Harfainx said:
Should be if it's the 2.3GHz version (which I think all 4GB RAM builds are).
Give it a shot. Worst case scenario... Nothing happens and you try a different prop. [emoji14]
Click to expand...
Click to collapse
It did but takes a whole lot of space, lol. Tnx again!!

how to transparent softkey?

Chinaphonearena said:
Soft keys are a go, adding 'qemu.hw.mainkeys=0' to build.prop.
Couldn't get capacitive buttons to disable though. Edited both generic.kl and ***asus***.kl, but they stayed enabled. Not sure if further fiddling could get it accomplished or not.
Click to expand...
Click to collapse
does this require root access? (newb here)

Anyone tried on latest stock MM ww134?
I tried adding on buildprop and buildprop 2.3ghz. Reboot and nothing happens.

i am trying since couple of days, still no use..
adding qemu.hd.mainkeys=0 is not showing any keys, i have a ZE551 model, and editing the build.prop is not doing anything

[Q] How do I enable softkeys on the American Zenfone 2 4GB RAM model?

I've tried editing every build prop file in the system folder and it fails to add software buttons.

TR88 said:
I've tried editing every build prop file in the system folder and it fails to add software buttons.
Click to expand...
Click to collapse
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.

cmendonc2 said:
There are definitely apps on the Play Store that can superimpose softkeys on the screen at the bottom, if you really don't like the capacitive ones.
Click to expand...
Click to collapse
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.

TR88 said:
Funny enough I installed a softkeys app for rooted devices off the play store and it put my phone in a bootloop...looks like I'm going to have to flash the factory firmware.
Click to expand...
Click to collapse
The one that makes the softkeys floating at the bottom?

cmendonc2 said:
The one that makes the softkeys floating at the bottom?
Click to expand...
Click to collapse
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.

TR88 said:
I believe it edited the build prop so it was navigation buttons, not superimposed.
The reason I was trying to get the navigation buttons back by the way was because the capacitive stopped working.
Click to expand...
Click to collapse
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.

cmendonc2 said:
It might be bootlooping because if you try to enable a feature (in the build prop) that isn't on the device (the actual system files), it can't boot up correctly.
Click to expand...
Click to collapse
That's most likely the case, I was just getting frustrated and installed the app without thinking, oh well.
I just want the navigation bar because, at least from my experience, most apps that superimpose the buttons are never the same. They won't appear at boot, interfere with the keyboard, and require a gesture to make them appear.

Doesnt gravity box have an option? Never tried it though.. just saying it might work.

i saw someone doing this but cant remeber where. Look in the develompent forum or in Google+ asus zenui beta development

I've been using this app for the last two years. I can highly recommend it.
http://forum.xda-developers.com/showthread.php?t=2270198

Install LP xposed, and LP gravity box, go to "navigation bar tweaks" and tick "master switch" "enable navigation bar" and soft reboot done =]

You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.

You could use one hand mode until you find a working one.
Sent from my ASUS_Z00AD using XDA Free mobile app

Use Pie Control from the market

rlaw said:
You have to edit the correct build.prop in /system/ that corresponds to your Zenfone 2 model.
If you have the same model as me (WW/64GB/4GB RAM/2.3GHz), you need to edit build.ze551.dual.2p3GHz.prop
If you look through my posting history, you'll see me offer a link to a guide on doing it, link also includes info on disabling the capacitive buttons. On mobile so can't look through myself. Cheers.
Click to expand...
Click to collapse
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk

TR88 said:
Yeah I actually found your thread prior to making this, but despite editing that specific modeled build prop, I did not see any results. It always deleted the line of code after I saved changes.
Sent from my T-Mobile LG G4 using Tapatalk
Click to expand...
Click to collapse
Strange it worked for me perfectly.