AdMob Error while running in Emulator - LogCat Attached - Mobile Ad Networks

Hello Frieds,
Today while I tried to integrate Admob in my app...
Im Facing this error while running the app in Emulator.
http://pastebin.com/Tbg06tdR
This is the code that I have put up in my XML.
Code:
<com.google.ads.AdView
android:id="@+id/adView"
android:layout_alignParentBottom="true"
android:layout_below="@+id/gridView"
android:layout_height="wrap_content"
android:layout_width="wrap_content"
ads:adUnitId="a155465208dx522s"
ads:adSize="BANNER"
ads:loadAdOnCreate="true"
/>

It cannot find the Google Play Services API; don't use the plain AOSP Android image, launch an emulator with the Google APIs one.

You cant run Admob in an emulator, try it on a real device.

Try to add
Code:
xmlns:ads="schemas.android.com/apk/res-auto"
at the beggining of your layout.

please add test-id for this emulator.

Related

secret code to get the OTA update

open dialer and enter this code *#*#8736364#*#*
if you use apk manager to decompile an apk and look inside AndroidManifest.xml
you can find all sorts of secret codes but be careful I found one that instantly does a factory format including the internal sd card.
example:
Code:
<intent-filter>
<action android:name="android.provider.Telephony.SECRET_CODE" />
<data android:scheme="android_secret_code" android:host="8736364" />
</intent-filter>
just enclose the numbers with *#*# before the numbers and #*#* after the numbers.
tried it and it didnt update Similar thing was posted in a different thread. Anyone able to get it to update?
it was about 10min before I got a notification that there was an update.
I tried it and think it works. I am unable to receive an update because I have my vibrant on att network. Do you know the correct device manager settings for t-mobile
Sent from my SGH-T959 using XDA App

[TIP] [Sabsa Prime 3.0~5.0] for having Apps Update Issue

Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
(Problems with Google Apps might be solved with editing packages.xml and replacing apks. see EDIT 3 bottom)
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install
Titanium Backup
com.keramidas.TitaniumBackup
OR
ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Go for the Apps list.
on Titanium Backup
Tap Backup/Restore
OR
on ROM Toolbox Lite
Tap App Manager
then Tap All Apps
4.
App which its names written Red are on /system/app on apps list.
5.
Find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
Press Uninstall
if you can't find, swipe left or right - it might be there.
8.
Wait until uninstall finishes...
9.
Reboot Your Phone NOW.
It's Done.
There's a one more step if you want to use them is:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
EDIT 1---------------------------------------------------------------------------------------------
for someone having poor(? disconnects too often) data reception,
please check this thread about build.prop Fast Dormancy:
t t p : / / forum.xda-developers.com/showthread.php?t=1684604
EDIT 2---------------------------------------------------------------------Sept. 21th, 2012
>> Oops, I forgot to tell reboot your phone. also, wrote about steps for titanium
EDIT 3------------------------------------------------------------------------Oct. 1st, 2012
>> Found something weired with Google apps by myself. so I edited again.
due to some reason you can't update or Install some Google apps like Google Play Service, etc.
1.
extract apks from gapps package 20120429
if you don't have it, Google it.
2.
go to recovery.
3.
mount /system/as writable.
4.
replace corresponding apks in system/app/
(Incldue MarketUpdater.apk: if you want to keep Play Store updated. and.. included Play Store App from gapps 20120429 IS OUTDATED.
DO NOT REPLACE GoogleBackupTransport.apk: this shares signature with the ROM's so do not replace it otherwise it will be NOT AVAILABLE on your phone.)
if you extracted the gapps package in folder gapps,
Shift-Click upper folder on tree view.
and open command window here
in command-prompt:
adb push /gapps /system/apps
Replacing apks done however you have more steps to do for replaced apks start working.
(optional)
you can unmount /system/ because you have finished replacing apks.
5.
mount /data/as writable.
6.
pull out packages.xml
in command-prompt:
adb pull /data/system/packages.xml
7.
open packages.xml in text editor
(IMPORTANT: DO NOT SAVE files on windows notepad or something else displays all of lines as single line because lack of UNIX support)
8.
Delete shared-user element has name=com.google.uid.shared.
then save.
you have to delete whole element this might look like:
<shared-user name="com.google.uid.shared" userId="10000">
<sigs count="1">
<cert index="1" />
</sigs>
<perms>
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.youtube" />
<item name="android.permission.INTERNET" />
<item name="com.google.android.providers.gmail.permission.WRITE_GMAIL" />
<item name="android.permission.WRITE_SYNC_SETTINGS" />
<item name="android.permission.BROADCAST_STICKY" />
<item name="com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.MASTER_CLEAR" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.ACCESS_DOWNLOAD_MANAGER" />
<item name="com.google.android.providers.gmail.permission.READ_GMAIL" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="com.android.providers.im.permission.WRITE_ONLY" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" />
<item name="com.google.android.gtalkservice.permission.SEND_GTALK_DATA_MESSAGE" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.READ_SYNC_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="com.android.providers.im.permission.READ_ONLY" />
<item name="android.permission.WRITE_SECURE_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser" />
<item name="android.permission.CALL_PHONE" />
<item name="com.google.android.gtalkservice.permission.GTALK_SERVICE" />
<item name="com.android.vending.INTENT_VENDING_ONLY" />
<item name="com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
</perms>
</shared-user>
Click to expand...
Click to collapse
9.
put packages.xml back to your phone.
in command-prompt:
adb push packages.xml /data/system/packages.xml
10.
set its permission rw-rw-r-- as it was.
in adb shell:
# chmod 664 /data/system/packages.xml
# chwon system.system /data/system/packages.xml
(optional)
to check permission has set:
# ls -e /data/system/packages.xml (if -rw-rw-r-- is okay first char is for a directory)
11.
Reboot Your Phone NOW.
It's Done.
Fails to install from Play store
AtomosVE said:
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Tap App Manager
4.
Tap All Apps
Like Titanium, App which its names written Red are on /system/app on apps list.
5.
find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
press Uninstall
8.
wait until uninstall finishes...
It's Done.
There's a one more step if you want to use them:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
Click to expand...
Click to collapse
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Oops, I forgot something..
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
Oh, Forgot to tell rebooting your phone after uninstalled app. Hope you enjoy Facebook
Yowhy said:
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Click to expand...
Click to collapse
Thanks for telling them reboot is need. I was forgot but Now, Corrected

Compile Error

I'm attempting to build omni rom from source on my mac for my galaxy note 2 N7100 and ran into the following error:
Code:
make: *** No rule to make target `vendor/samsung/smdk4412-common/proprietary/system/lib/libExynosHWCService.so', needed by `/Volumes/android/omnirom/out/target/product/n7100/system/lib/libExynosHWCService.so'. Stop.
I ran through all the steps again to make sure I didn't miss anything, but no luck.
Any ideas? Thanks
FYI, I created an omnirom.xml inside the local_manifests folder, here are the contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="omnirom"
review="gerrit.omnirom.org"
fetch="https://github.com/omnirom" />
<project path="device/samsung/n7100" name="android_device_samsung_n7100" remote="omnirom" revision="android-4.4"/>
<project path="device/samsung/smdk4412-common" name="android_device_samsung_smdk4412-common" remote="omnirom" revision="android-4.4"/>
<project path="hardware/samsung" name="android_hardware_samsung" remote="omnirom" revision="android-4.4"/>
<project path="kernel/samsung/smdk4412" name="android_kernel_samsung_smdk4412" remote="omnirom" revision="android-4.4"/>
</manifest>
EDIT: I went through the process again and came across the following error from extract-files.sh:
Code:
remote object '/system/lib/libExynosHWCService.so' does not exist
I currently have omni-4.4.2-20140428-n7100-NIGHTLY.zip installed.
Try adding the Donkey Coyote vendor repo to your local manifest.
https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-4.4
PonsAsinorem said:
Try adding the Donkey Coyote vendor repo to your local manifest.
https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-4.4
Click to expand...
Click to collapse
Hi, I'm a bit new to this so trying to figure out how to add this repo. Would you mind giving an example? Thanks
Also, I searched the repo and the file libExynosHWCService.so doesn't exist so I'm not sure it would help me.
cjhmdm said:
Hi, I'm a bit new to this so trying to figure out how to add this repo. Would you mind giving an example? Thanks
Also, I searched the repo and the file libExynosHWCService.so doesn't exist so I'm not sure it would help me.
Click to expand...
Click to collapse
Can you find the file '/system/lib/libExynosHWCService.so' on your phone ? The script uses "adb pull ..." to retrieve these proprietary files from your handset, so it first needs to exist on your device (it will) and secondly adb needs to be functional. (for what it's worth, you'll also find that file in the nightly zip but you don't want it).
To start with can you do simple things like:
adb devices
adb shell
Is your path setup correctly and pointing to the SDK ?
There are instructions for "configuring USB access" over at the android developers site.
http://source.android.com/source/initializing.html
I have this configured on my machine, but I honestly can't remember if I did this manually or if it was done automagically during the initial repo setup.
FrodgE said:
Can you find the file '/system/lib/libExynosHWCService.so' on your phone ? The script uses "adb pull ..." to retrieve these proprietary files from your handset, so it first needs to exist on your device (it will) and secondly adb needs to be functional. (for what it's worth, you'll also find that file in the nightly zip but you don't want it).
To start with can you do simple things like:
adb devices
adb shell
Is your path setup correctly and pointing to the SDK ?
There are instructions for "configuring USB access" over at the android developers site.
http://source.android.com/source/initializing.html
I have this configured on my machine, but I honestly can't remember if I did this manually or if it was done automagically during the initial repo setup.
Click to expand...
Click to collapse
Hello, thanks for taking the time to reply. My build environment is setup and configured correctly. All of my paths are correct, etc.
In searching my device, which is running omni-4.4.2-20140428-n7100-NIGHTLY.zip, the file libExynosHWCService.so doesn't exist, nor does the 'binary' version exist in the rom zip file.
cjhmdm said:
Hello, thanks for taking the time to reply. My build environment is setup and configured correctly. All of my paths are correct, etc.
In searching my device, which is running omni-4.4.2-20140428-n7100-NIGHTLY.zip, the file libExynosHWCService.so doesn't exist, nor does the 'binary' version exist in the rom zip file.
Click to expand...
Click to collapse
Just add DonkeyCoyote repo as mentioned above and build.
BTW, omnirom remote is already configured by default, you don't need to do it in local manifest.
UtkarshGupta said:
Just add DonkeyCoyote repo as mentioned above and build.
BTW, omnirom remote is already configured by default, you don't need to do it in local manifest.
Click to expand...
Click to collapse
Could you provide an example of how I can add that repo? I'm trying to figure out to add it but haven't had much success so far.
Thanks in advance
Code:
<remote fetch="https://github.com/DonkeyCoyote" name="donkey" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="donkey" revision="android-4.4" />
chasmodo said:
Code:
<remote fetch="https://github.com/DonkeyCoyote" name="donkey" />
<project name="proprietary_vendor_samsung" path="vendor/samsung" remote="donkey" revision="android-4.4" />
Click to expand...
Click to collapse
cjhmdm said:
I'm attempting to build omni rom from source on my mac for my galaxy note 2 N7100 and ran into the following error:
Code:
make: *** No rule to make target `vendor/samsung/smdk4412-common/proprietary/system/lib/libExynosHWCService.so', needed by `/Volumes/android/omnirom/out/target/product/n7100/system/lib/libExynosHWCService.so'. Stop.
I ran through all the steps again to make sure I didn't miss anything, but no luck.
Any ideas? Thanks
FYI, I created an omnirom.xml inside the local_manifests folder, here are the contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="omnirom"
review="gerrit.omnirom.org"
fetch="https://github.com/omnirom" />
<project path="device/samsung/n7100" name="android_device_samsung_n7100" remote="omnirom" revision="android-4.4"/>
<project path="device/samsung/smdk4412-common" name="android_device_samsung_smdk4412-common" remote="omnirom" revision="android-4.4"/>
<project path="hardware/samsung" name="android_hardware_samsung" remote="omnirom" revision="android-4.4"/>
<project path="kernel/samsung/smdk4412" name="android_kernel_samsung_smdk4412" remote="omnirom" revision="android-4.4"/>
</manifest>
EDIT: I went through the process again and came across the following error from extract-files.sh:
Code:
remote object '/system/lib/libExynosHWCService.so' does not exist
I currently have omni-4.4.2-20140428-n7100-NIGHTLY.zip installed.
Click to expand...
Click to collapse
Hello, I'm trying to build a LineageOS rom for Meizu PRO5 which has a similar chipset as Samsung Galaxy S6/Note5, I also encounter a similar error with libExynosHWCService, which says:
Code:
make: *** No rule to make target /home/user/los/system/out/target/product/m86/obj/SHARED_LIBRARIES/libExynosHWCService_intermediates/export_includes', needed by 'home/user/system/out/target/product/m86/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop.
Can you please advise and help? I both have these libraries in the vendor folders for both /lib and /lib64 and currently stuck here. Thanks in advance!

[Q] launcher 8 - can't set as default launcher

Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
schelleursli said:
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
Click to expand...
Click to collapse
It appears from the photographs that your Nook is not recognizing Launcher8 as a launcher app, but instead as a regular app. Are you able to view Launcher8 from ReLaunch's app drawer?
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
schelleursli said:
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
Click to expand...
Click to collapse
Yes, "All applications" is ReLaunch's app drawer.
I don't know exactly how to fix this, but let me do some research, and I'll get back to you.
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Renate NST said:
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Click to expand...
Click to collapse
Thanks for that, I've tried fiddling with the Manifest but I always either get a non working application with an entry in the Home menu or a working application with no entry in the Home menu to choose as default.
If you feel like having a look, this is the default manifest that is in use by launcher 8: pastebin.com/K8BknQuk (I'm not allowed to post links yet)
I do not have the android sdk installed or anything prepared to run ADB on my nook, I'll look into that at some point if the manifest fiddling doesn't work out.
The AndroidManifest.xml looks fine, which is to be expected.
Maybe you "picked" the wrong application at some point?
That's all in /data/system/packages.xml
Check preferred-activities in there.
You can always delete that whole section, as long as you do it cleanly.
Thanks for the continued help. I've had a look at packages.xml preferred-activities looks like this:
Code:
<preferred-activities>
<item name="com.lx.launcher8/.AnallLauncher" match="100000" set="4">
<set name="com.bn.nook.home/.HomeActivity" />
<set name="com.lx.launcher8/.AnallLauncher" />
<set name="com.lx.launcher8/.Home" />
<set name="com.harasoft.relaunch/.Home" />
<filter>
<action name="android.intent.action.MAIN" />
<cat name="android.intent.category.HOME" />
<cat name="android.intent.category.DEFAULT" />
</filter>
</item>
</preferred-activities>
I can turn off my nook and turn it on again then launcher 8 starts by default, but if I press the "n" button on the nook and then press home on the touch-screen I still only get the choice between ReLaunch and the default nook Home. I've also tried completely resetting my device restoring an old unrooted backup then root it again and set it up from scratch, same problem.
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Deafcyclist said:
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Click to expand...
Click to collapse
Yep, that's Nook Touch Mod Manager. It comes pre-installed with NookManager and my 1337 ROM, but it can also be installed manually with some modified framework-related .jar files.
Thanks for the tip, sounds like a good workaround for now.
edit: I see I need a running build environment for that, will see if I can get this to work on my virtual machine.
edit2: got it working
Oh, the "n" button?
B&N has that hardwired to do some B&N specific intent.
This problem has been solved many different ways.
My solution is to patch where the problem is, com.android.internal.policy.impl.PhoneWindowManager (in android.policy.jar).
This just makes the "n" key a normal Home key.
Code:
apktool d android.policy.jar -o C:\AP
mergesmali /v C:\AP PhoneWindowManager.smali PhoneWindowManager$HomeButtonHandler.smali
apktool b C:\AP -o android.policy.jar
Check the mergesmali link in the signature, a zip of the patches is there too.
No it was the "Home" menu button you open by pressing the "n" button. But with Nook Touch Mod Manager I've managed to change the behaviour of said "Home" even though Launcher 8 still wasn't shown as a choice. Thanks for all the help.

Help get UI nav sounds.

Hi there!
I`m running an androidtv rom and i`d like to get the ui navigation sounds for Nexus player.
Thx so much.
well, I did some digging and found audio "ogg" files
"pano_blip_alt, pano_click, pano_error" under ui in media/audio folder under system...but when copied over to my rom nothing changes, so what file do I need to change to load them in my rom?
Thx!
Does anyone have any idea where to look?
You need to update audio_assets.xml in framework-res.apk to this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<audio_assets version="1.0">
<group name="touch_sounds">
<asset id="FX_KEY_CLICK" file="pano_click.ogg" />
<asset id="FX_FOCUS_NAVIGATION_UP" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_DOWN" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_LEFT" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_RIGHT" file="pano_blip_alt.ogg" />
<asset id="FX_KEYPRESS_STANDARD" file="KeypressStandard.ogg" />
<asset id="FX_KEYPRESS_SPACEBAR" file="KeypressSpacebar.ogg" />
<asset id="FX_KEYPRESS_DELETE" file="KeypressDelete.ogg" />
<asset id="FX_KEYPRESS_RETURN" file="KeypressReturn.ogg" />
<asset id="FX_KEYPRESS_INVALID" file="pano_error.ogg" />
</group>
</audio_assets>
Thx man....you are my savior.....love you!!!
update:
I used "Advanced_ApkTool_v4.2.0_By_BDFreak_2.2.1_2" to unpack...made the changes with notepad++, repacked and signed...flashed a zip file with twrp...but it get locked in bootloop...until i reflash the original file back in...glad i thought to make a backup...so now it`s back to normal...what gives?
When using apktool, you'll want to build with the -c option to carry over the signature from the original apk. Also, I'd use the -s option on decode so that it keeps the classes.dex intact. (No need to recompile those if you're just changing a resource.)
Thx so much...I don`t see where to enable those options....are they available on windows?
I just figured we`re talking about 2 different tools ...are you talking about this one?

Categories

Resources