Related
Hi
There was mod/ built in script to kill apps by longpress of back key in SGS. is it available for SGS3....??
+1
Sent from my GT-I9300 using xda app-developers app
It comes buit in it Slim, so i'm guessing that cm9/10 or aokp have that feature. I'm also guessing that it's a part of the framework itself.
shaharofir said:
It comes buit in it Slim, so i'm guessing that cm9/10 or aokp have that feature. I'm also guessing that it's a part of the framework itself.
Click to expand...
Click to collapse
Yeah its quite easy to build it into AOSP roms. At the source code level you modify policy/src/com/android/internal/policy/impl/PhoneWindowManager.java which would end up as android.policy.jar in /frameworks
If you can decompile it, it can be added but you would probably also want to decomcpile SecSettings.apk to allow it to be added.
Can't you just enable it in "Settings" » "Developer Options" » "Kill app back button"? This should kill the current app if you hold the back button.
brins0 said:
Can't you just enable it in "Settings" » "Developer Options" » "Kill app back button"? This should kill the current app if you hold the back button.
Click to expand...
Click to collapse
That's what this thread is requesting. In fact that's what my post adds. Obviously this is not a standard option
Sent from my GT-I9300 using Tapatalk 2
brins0 said:
Can't you just enable it in "Settings" » "Developer Options" » "Kill app back button"? This should kill the current app if you hold the back button.
Click to expand...
Click to collapse
I don't have "Kill app back button" under "Developer options"
code72 said:
I don't have "Kill app back button" under "Developer options"
Click to expand...
Click to collapse
No of course not. This is a Development community mod. Not a factory one
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Yeah its quite easy to build it into AOSP roms. At the source code level you modify policy/src/com/android/internal/policy/impl/PhoneWindowManager.java which would end up as android.policy.jar in /frameworks
If you can decompile it, it can be added but you would probably also want to decomcpile SecSettings.apk to allow it to be added.
Click to expand...
Click to collapse
Could you post what has to be modified / added in that file, I wouldn't mind having a bash at adding that to the stock rom.
webwolf_3000 said:
Could you post what has to be modified / added in that file, I wouldn't mind having a bash at adding that to the stock rom.
Click to expand...
Click to collapse
To be clear, I only know how to do it at a source code level, and then I've not done it since Gingerbread so I don't know if the code needs changing. It may be simpler to google it.
However,
This is what would be added for Settings:
packages/apps/Settings/src/com/android/settings/DevelopmentSettings.java
Code:
packages/apps/Settings/src/com/android/settings/DevelopmentSettings.java
public class DevelopmentSettings extends PreferenceActivity
implements DialogInterface.OnClickListener, DialogInterface.OnDismissListener {
private static final String KILL_APP_LONGPRESS_BACK = "kill_app_longpress_back";
private CheckBoxPreference mKillAppLongpressBack;
addPreferencesFromResource(R.xml.development_prefs);
mKillAppLongpressBack = (CheckBoxPreference) findPreference(KILL_APP_LONGPRESS_BACK);
}
@Override
protected void onResume() {
super.onResume();
mKillAppLongpressBack.setChecked(Settings.Secure.getInt(getContentResolver(),
Settings.Secure.KILL_APP_LONGPRESS_BACK, 0) != 0);
}
@Override
public boolean onPreferenceTreeClick(PreferenceScreen preferenceScreen, Preference preference) {
} else if (preference == mKillAppLongpressBack) {
Settings.Secure.putInt(getContentResolver(), Settings.Secure.KILL_APP_LONGPRESS_BACK,
mKillAppLongpressBack.isChecked() ? 1 : 0);
}
And for frameworks:
policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
Code:
Runnable mBackLongPress = new Runnable() {
public void run() {
if (Settings.Secure.getInt(mContext.getContentResolver(),
Settings.Secure.KILL_APP_LONGPRESS_BACK, 0) == 0) {
return;
}
try {
performHapticFeedbackLw(null, HapticFeedbackConstants.LONG_PRESS, false);
IActivityManager mgr = ActivityManagerNative.getDefault();
List<RunningAppProcessInfo> apps = mgr.getRunningAppProcesses();
for (RunningAppProcessInfo appInfo : apps) {
int uid = appInfo.uid;
// Make sure it's a foreground USER application
if (uid >= Process.FIRST_APPLICATION_UID && uid <= Process.LAST_APPLICATION_UID
&& appInfo.importance == RunningAppProcessInfo.IMPORTANCE_FOREGROUND) {
// Kill the entire pid
Toast.makeText(mContext, com.android.internal.R.string.app_killed_message, Toast.LENGTH_SHORT).show();
Process.killProcess(appInfo.pid);
break;
}
}
I think thats everything. Below are the full files so you can see them in context:
138 lines of code - DevelopmentSettings.java
2535 lines of code - PhoneWindowManager.java
good luck!
thanks for that, I'll unpack the the stock ROM when I have some time and figure out how to hook it together, shouldn't be too dificult I'll post the results when I've gaffered it.
dineshh said:
Hi
There was mod/ built in script to kill apps by longpress of back key in SGS. is it available for SGS3....??
Click to expand...
Click to collapse
+1 Any developer please...
Sent from my GT-I9300 using xda premium
ill make one
Sent from my GT-I9300 using xda premium
Has anyone made this mod yet?
Every phone I've had did have this feature on AOSP but not stock. It would be great to have it on Samsung ROMs.
Sent from my GT-I9300 using xda premium
CuBz90 said:
Every phone I've had did have this feature on AOSP but not stock. It would be great to have it on Samsung ROMs.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
+1000!
deliad said:
ill make one
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
looking forward to it.
anything new here?
someone?
Look for JKay's framework in original android dev section.
His framework can do this!
Fixed htc dhd Headset Remote control button is invalid
find dhd kernel Source code (Flemmard or KangBanged)
/arch/arm/mach-msm/board-spade.c
open the board-spade.c file . find
/* HTC_HEADSET_MICROP Driver */
static struct htc_headset_microp_platform_data htc_headset_microp_data = {
.remote_int = 1 << 5,
.remote_irq = MSM_uP_TO_INT(5),
.remote_enable_pin = 1 << 4,
.adc_channel = 0x01,
.adc_remote = {0, 33, 38, 82, 95, 167},
};
Change into
/* HTC_HEADSET_MICROP Driver */
static struct htc_headset_microp_platform_data htc_headset_microp_data = {
.remote_int = 1 << 13,
.remote_irq = MSM_uP_TO_INT(13),
.remote_enable_pin = 1 << 4,
.adc_channel = 0x01,
.adc_remote = {0, 33, 38, 82, 95, 167},
};
ok, it work perfect and special headset working.
I'm from China.sorry I'm not very good at English
Thank you very much!
:victory:Thank you..
ah nice catch!!
ucxl can u give us and source for no wake delay plsssss Thx for your work you are verry good man to post here source code
Nice man !! 你真了不起 ( u are awesome ) !
Sent from my DHD+ loaded with ViperDHD V1.2.1 using xda premium
Compiling a kernel now with headset fix
edit : kernel done waiting for feed back
Sent from my Desire HD using xda premium
p2pjack said:
Compiling a kernel now with headset fix
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Great news, hope a new kernel
You rock bro! Chinese all the way
Sent from my Desire HD using xda app-developers app
So i guess every sense rom dev will include this in their next update?
Now the headset is working, i'll pick the most stable ICS sense 4 ROM
0℃ Team
NiCk.JaY said:
You rock bro! Chinese all the way
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
I am only on behalf of the team expression U of selfless apologize and immense gratitude!
---------- Post added at 01:07 PM ---------- Previous post was at 01:03 PM ----------
ucxl said:
Fixed htc dhd Headset Remote control button is invalid
find dhd kernel Source code (Flemmard or KangBanged)
/arch/arm/mach-msm/board-spade.c
open the board-spade.c file . find
/* HTC_HEADSET_MICROP Driver */
static struct htc_headset_microp_platform_data htc_headset_microp_data = {
.remote_int = 1 << 5,
.remote_irq = MSM_uP_TO_INT(5),
.remote_enable_pin = 1 << 4,
.adc_channel = 0x01,
.adc_remote = {0, 33, 38, 82, 95, 167},
};
Change into
/* HTC_HEADSET_MICROP Driver */
static struct htc_headset_microp_platform_data htc_headset_microp_data = {
.remote_int = 1 << 13,
.remote_irq = MSM_uP_TO_INT(13),
.remote_enable_pin = 1 << 4,
.adc_channel = 0x01,
.adc_remote = {0, 33, 38, 82, 95, 167},
};
ok, it work perfect and special headset working.
I'm from China.sorry I'm not very good at English
Click to expand...
Click to collapse
I am only on behalf of the team expression U of selfless apologize and immense gratitude!
I am willing to put my camera the transplantation technology dedicated to the DHD machine Friends of
all can support ucxl by using his brownser available on google play This man deserve that without it we would have been more back And i have to say its more stable than chrome or maxthon
It's a little bit off topic but, Is there any way to change skip keys in headset to Vol+ and Vol-, and keep skip track functionality with long press?
Sent from my Desire HD using xda app-developers app
I'm sorry I doubted you. Glad to see your stuff here.
well done.thanks
Sent from my Desire HD using xda app-developers app
BIG BROTHER U : Genius man. The most important point in HDD history. Yr Rom is also the best.
Sent from my HTC Desire HD Telus using Tapatalk 2
---------- Post added at 09:15 PM ---------- Previous post was at 08:36 PM ----------
torxx said:
ah nice catch!!
Click to expand...
Click to collapse
You are ready to include in your ROM now?
你真是個天才 !!! (((you're a genius))
ucxl said:
Fixed htc dhd Headset Remote control button is invalid
Click to expand...
Click to collapse
Thanks, my urBeats Monster InEar Headset work perfekt
Sent from my HTC Desire HD using xda app-developers app
@makey404
There are some apps in the play store that allow you to change what the button presses do. I can't remember for sure but I think this was possible.
Sent from my Desire HD using xda app-developers app
bananagranola said:
I'm sorry I doubted you. Glad to see your stuff here.
Click to expand...
Click to collapse
Never mind, I began to do wrong
I know there was a post just like with what I'm doing...but here's something for you to use in your own ROMs.
Code:
#Performance Enhancement
dalvik.vm.heapgrowthlimit=256m
debug.performance.tuning=1
windowsmgr.max_events_per_sec=300
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
debug.sf.hw=1
video.accelerate.hw=1
profiler.force_disable_err_rpt=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.execution-mode=init:jit
ro.kernel.android.checkjni=0
#Battery Enhancement
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=500
ro.mot.eri.losalert.delay=1000
persist.sys.purgeable_assets=1
# Signal Enhancement
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=7
media.stagefright.enable-meta=true
media.stagefright.enable-record=false
ro.ril.hep=1
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
# Video & Picture Enhancement
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Sound & Calls Enhancement
ro.telephony.call_ring.delay=0
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
af.resampler.quality=255
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
#AC!D Audio Volume Hack
-----------------------------
speaker volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.speaker.voice.0=20
audio.speaker.voice.1=21
audio.speaker.voice.2=24
audio.speaker.voice.3=26
audio.speaker.voice.4=28
audio.speaker.voice.5=31
-----------------------------
earpiece volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.earpiece.voice.0=20
audio.earpiece.voice.1=21
audio.earpiece.voice.2=24
audio.earpiece.voice.3=26
audio.earpiece.voice.4=28
audio.earpiece.voice.5=31
-----------------------------------
headset volume is from 9 to 14
this corresponds to -34dB to -19dB
----------------------------------
audio.headset.voice.0=16
audio.headset.voice.1=19
audio.headset.voice.2=22
audio.headset.voice.3=25
audio.headset.voice.4=28
audio.headset.voice.5=31
#Sony BRAVIA Engine
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
Note ** : Bravia Engine build.prop and AC!D build.prop edits still need required files. This is just to enable the settings to work with the files.
Did you get a gs3?
Sent from my SGH-T999 using xda app-developers app
Thanks for your contribution .
seshaz said:
Did you get a gs3?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yes.
TheLastSidekick said:
Yes.
Click to expand...
Click to collapse
Nice
Sent from my SGH-T999 using xda app-developers app
exactly what files are required for the bravia engine?? I've been wanting to use that for awhile now and can't fine much info about it.
SimeonAS89 said:
exactly what files are required for the bravia engine?? I've been wanting to use that for awhile now and can't fine much info about it.
Click to expand...
Click to collapse
Your signature says you have a GS3 so check out this Bravia Engine thread.
Where can I find the volume hack for Ac!d? Version 4.0? I'm on V5 and I'm not sure if it'll work, any takers?
If I edit the build prop in my current Rom do I just reboot for the modified .xml to be loaded? ...or do I need to modify the file in the Rom zip and re-flash?
Do you just add these to the end of the build prop?
Sent from my SGH-T999 using Tapatalk 2
OhhCoreey said:
Do you just add these to the end of the build prop?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did then deleted conflicting and duplicate entries. Still not sure if just a reboot reloads the file though. My data seems a bit faster. I'm on the latest miui port.
Sent from my SGH-T999 using xda app-developers app
I know this was posted somewhere else in XDA, but it's worth a read, much of this stuff seems to be placebo:
http://www.jeffmixon.com/series/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide/
I posted this after I lost my Galaxy S2 and was on my Galaxy S3. Here's an update finally, sorry I forgot where this thread was.
Code:
#Performance Enhancement
dalvik.vm.heapgrowthlimit=256m
debug.performance.tuning=1
windowsmgr.max_events_per_sec=90 (this was proven right, only set it to 90 for best effects)
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
debug.sf.hw=1
video.accelerate.hw=1
profiler.force_disable_err_rpt=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.execution-mode=init:jit
ro.kernel.android.checkjni=0
#Battery Enhancement
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=500
ro.mot.eri.losalert.delay=1000
persist.sys.purgeable_assets=1
# Signal Enhancement
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=7
media.stagefright.enable-meta=true
media.stagefright.enable-record=false
ro.ril.hep=1
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
# Video & Picture Enhancement
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Sound & Calls Enhancement
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=25
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
af.resampler.quality=255
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
#AC!D Audio Volume Hack
-----------------------------
speaker volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.speaker.voice.0=20
audio.speaker.voice.1=21
audio.speaker.voice.2=24
audio.speaker.voice.3=26
audio.speaker.voice.4=28
audio.speaker.voice.5=31
-----------------------------
earpiece volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.earpiece.voice.0=20
audio.earpiece.voice.1=21
audio.earpiece.voice.2=24
audio.earpiece.voice.3=26
audio.earpiece.voice.4=28
audio.earpiece.voice.5=31
-----------------------------------
headset volume is from 9 to 14
this corresponds to -34dB to -19dB
----------------------------------
audio.headset.voice.0=16
audio.headset.voice.1=19
audio.headset.voice.2=22
audio.headset.voice.3=25
audio.headset.voice.4=28
audio.headset.voice.5=31
#Sony BRAVIA Engine
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
The Bravia Engine tweak wouldn't work unless the engine is installed, correct?
How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium
Very good job, thank you.
vassosman said:
The Bravia Engine tweak wouldn't work unless the engine is installed, correct?
Click to expand...
Click to collapse
Correct.
thakrew317 said:
How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You could, I just don't know how to make flashables.
Warren87 said:
Very good job, thank you.
Click to expand...
Click to collapse
No, thank you!
Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....
thakrew317 said:
How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
the above was for you
I tried making one but failed not very educated when doing things like that thank you!!!!
Sent from my SAMSUNG-SGH-T989 using xda premium
Do these mods really make a noticeable difference????
subnoize soulja said:
Do these mods really make a noticeable difference????
Click to expand...
Click to collapse
Try it and let us know I know the mods I used did but too some it may seem like it has not... Only one way too find out...
---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------
thakrew317 said:
I tried making one but failed not very educated when doing things like that thank you!!!!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Its actually very easy and if you need help or wanna learn just let me know... PM me
I manipulate more than I create its easier that way....
playya said:
Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....
Click to expand...
Click to collapse
Hey playya, I have one question for you. The zip puts the tweaks to default.prop. Shouldnt't they be in the build.prop? If not, what does the default.prop do? I've seen a lot of ROM's that have a default.prop in data and always wondered what it did.
Sent from my Nexus 7 using xda app-developers app
playya said:
Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....
Click to expand...
Click to collapse
Thank you for making it a zip!! I would love to learn
Sent from my SGH-T989 using xda premium
Interesting read on some build prop tweaks being busted:
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Apparently Google have said a 'windowsmgr.max_events_per_sec' value above 90 doesn't add anything to performance and can even be detrimental to it.
After messing around with it I noticed 90 makes things more snappier than 300+. At least for me on all of the 4.0.3 ROMs.
Worth noting.
Sent from my SGH-T989 using Tapatalk 2
Reading over the individual prop edits, I'm noticing that my phone does not have all of the props to edit. Without making a paperweight, should I ignore the ones not present. Only asking since the ROMs that the OP has made and I've since flashed all of them, have been a lot quicker then the dated PA I'm running now and ID like to apply them but there are several missing so I figured ID ask here. Thanks with any knowledge you can toss my way
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Tmogalaxys2 said:
Hey playya, I have one question for you. The zip puts the tweaks to default.prop. Shouldnt't they be in the build.prop? If not, what does the default.prop do? I've seen a lot of ROM's that have a default.prop in data and always wondered what it did.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sorry guys for not getting back to you sooner but i coach kids and adults so sometimes I miss stuff. Now what I did was put it in as a local.prop and this actually supersedes your build.prop and it can be used from one rom to another without having to go in and change each build.prop.
also if you update your rom and you do not do a clean install your tweaks should stick without a problem since it wont be overwritten on a flash.
I believe if I am not mistaken that the default.prop is kernel related and if you view it you will see info related to such like usb connection and adb root access
---------- Post added at 09:07 AM ---------- Previous post was at 09:01 AM ----------
tongueman87 said:
Thank you for making it a zip!! I would love to learn
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
No prob I use notepad ++ and total commander to do my manipulations... Send me a pm and we can mess around with stuff. Its really a lot of text and not as difficult as you may think.
playya said:
sorry guys for not getting back to you sooner but i coach kids and adults so sometimes I miss stuff. Now what I did was put it in as a local.prop and this actually supersedes your build.prop and it can be used from one rom to another without having to go in and change each build.prop.
also if you update your rom and you do not do a clean install your tweaks should stick without a problem since it wont be overwritten on a flash.
I believe if I am not mistaken that the default.prop is kernel related and if you view it you will see info related to such like usb connection and adb root access
---------- Post added at 09:07 AM ---------- Previous post was at 09:01 AM ----------
No prob I use notepad ++ and total commander to do my manipulations... Send me a pm and we can mess around with stuff. Its really a lot of text and not as difficult as you may think.
Click to expand...
Click to collapse
Thanks for the info man!
Sent from my Nexus 7 using xda app-developers app
Bumping with update, have more knowledge of the tweaks. And yes, I still do frequent these forums lol, and you guys did get 4.1.2 before GS3 did, but we just got it 3 days ago. Just can't test anything for the GS2. But these are universal, enjoy!
DigitaL BlisS said:
Interesting read on some build prop tweaks being busted:
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Apparently Google have said a 'windowsmgr.max_events_per_sec' value above 90 doesn't add anything to performance and can even be detrimental to it.
After messing around with it I noticed 90 makes things more snappier than 300+. At least for me on all of the 4.0.3 ROMs.
Worth noting.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Yea I was reading this as well. There are actually two pages in his report can find both here:
http://www.jeffmixon.com/series/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide/
TheLastSidekick said:
Bumping with update, have more knowledge of the tweaks. And yes, I still do frequent these forums lol, and you guys did get 4.1.2 before GS3 did, but we just got it 3 days ago. Just can't test anything for the GS2. But these are universal, enjoy!
Click to expand...
Click to collapse
Welcome back old friend =/]
Hello,
I read around the forum about modding the official SecMms app to edit smileys' syntax...There's plenty of information around on how to change the aliases; what I'm actually wondering about is: can I ADD aliases for existing smileys,instead of changing the default values in the "default_smiley_texts" string list of SecMms' array.xml file?
For example: the default value for "Happy" is ": - )" ... can I break something by adding a shorter syntax for it , ": )" , leaving the original one in as well? This way, the app would visualize as graphic smileys both the ones I write in my own syntax and the official ones.
Has anyone tried this?Would it work?
Thanks in advance...
Sent from my GT-I9100P using xda app-developers app
Twain28 said:
Hello,
I read around the forum about modding the official SecMms app to edit smileys' syntax...There's plenty of information around on how to change the aliases; what I'm actually wondering about is: can I ADD aliases for existing smileys,instead of changing the default values in the "default_smiley_texts" string list of SecMms' array.xml file?
For example: the default value for "Happy" is ": - )" ... can I break something by adding a shorter syntax for it , ": )" , leaving the original one in as well? This way, the app would visualize as graphic smileys both the ones I write in my own syntax and the official ones.
Has anyone tried this?Would it work?
Thanks in advance...
Sent from my GT-I9100P using xda app-developers app
Click to expand...
Click to collapse
Try this one ... XPOSED app will help u!!
http://forum.xda-developers.com/showthread.php?t=2138089
Thanks for your suggestion, I'll have a look and see if that's good for me!
Sent from my GT-I9100P using xda app-developers app
It works, many thanks for the suggestion.
This can be closed as fixed.
Sent from my GT-I9100P using xda app-developers app