Related
.......................
reserved for future use
more reserved for future use
Sounds good, I'll try it out when it's ready. I use Sashimi whenever I reinstall my phone now. Thanks for all your work!
Oh man the waiting is killing me!!!! Waiting for this and SASHIMI v7.0...
Tutorial looks awesome...I've been looking for something like this..Sweet!
Thanks!
download available now!
This is very good, thank you. However, it would be much better if you include gprs/mms account settings in your next release.
pilgrim011 said:
This is very good, thank you. However, it would be much better if you include gprs/mms account settings in your next release.
Click to expand...
Click to collapse
Thanks.
Any additional CSPs that you would want added for provisioning, please provide links to the CSP XML code along with information about the various variables in the XML and I will add them to future release.
Unfortunately, I'm not familar with xml... Thanks anyway, this is good tool.
pilgrim011 said:
Unfortunately, I'm not familar with xml... Thanks anyway, this is good tool.
Click to expand...
Click to collapse
Well I'm not sure that gprs/mms settings are something that there is a standardized CSP for. If there is, and anyone has info on it, let me know.
OK, upon your request from here...
http://forum.xda-developers.com/showthread.php?p=2508908#post2508908
...I'll go on in this thread (have not been aware there are 2 different threads with the same name in 2 different branches of the forum...)
Regarding the VPN and GPRS and some more settings (I even found some SIP settings) as XML provisioning files:
The MS reference is here:
http://msdn.microsoft.com/en-us/library/ms889539.aspx
Samples for some important ones go here:
GPRS:
http://www.blackberryforums.com/handheld-forum/91310-windows-mobile-gprs-provisioning.html
Code:
<wap-provisioningdoc>
<characteristic type="CM_GPRSEntries">
<characteristic type="O2">
<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}" />
<parm name="UserName" value="APNusername" />
<parm name="Password" value="APNpassword" />
<parm name="SwCompression" value="1" />
<parm name="IpHeaderCompression" value="0" />
<parm name="SpecificNameServers" value="1" />
<parm name="DnsAddr" value="PrimaryDNS" />
<parm name="AltDnsAddr" value="AlternateDNS" />
<parm name="Domain" value="" />
<characteristic type="DevSpecificCellular">
<parm name="GPRSInfoValid" value="1" />
<parm name="GPRSInfoAccessPointName" value="AccessPointName" />
<parm name="BearerInfoValid" value="1" />
<parm name="GPRSInfoProtocolType" value="2" />
<parm name="GPRSInfoL2ProtocolType" value="PPP" />
<parm name="GPRSInfoAddress" value="" />
<parm name="GPRSInfoDataCompression" value="1" />
<parm name="GPRSInfoHeaderCompression" value="1" />
<parm name="GPRSInfoParameters" value="" />
</characteristic>
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic type="HKCU\ControlPanel\PhoneExtendFunction" translation="filesystem">
<parm name="GPRSAuthenticationMethod" datatype="integer" value="1" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
VPN:
http://msdn.microsoft.com/en-us/library/aa455980.aspx
Code:
<wap-provisioningdoc>
<characteristic type="CM_VPNEntries">
<characteristic type="MYVPN">
<parm name="SrcId" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>
<parm name="DestId" value="{A1182988-0D73-439e-87AD-2A5B369F808B}"/>
<parm name="Phone" value="vpn.customer.com"/>
<parm name="UserName" value="user123"/>
<parm name="Password" value="test"/>
<parm name="Domain" value="mydomain"/>
<!-- Determins the type of authentication e.g. IPSec vs PPTP -->
<parm name="Type" value="1"/>
<!-- Determins the type IPSec encryption, either pre shared key or cert based -->
<parm name="IPSecAuth" value="1"/>
<!-- pre shared key can be 256 chars long, but must be ASCII -->
<parm name="PresharedKey" value="1234567890"/>
<parm name="Enabled" value="1" />
</characteristic>
</characteristic>
<!-- Exceptions to route these ips via VPN and not the standard connection:-->
<characteristic type="CM_Mappings">
<characteristic type="16777216">
<parm name="Pattern" value="*://192.168.10.15"/>
<parm name="Network" value="{A1182988-0D73-439E-87AD-2A5B369F808B}"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
SIP:
http://forum.xda-developers.com/showthread.php?t=299950
Code:
<wap-provisioningdoc>
<characteristic type="VoIP">
<parm name="SIPSettings"
value="<provision key='1232ab01' name='_sip_provider_name_'>
<provider name='_sip_provider_name_' />
<user account='_account_' password='_password_'
uri='sip:[email protected]_host.com_'
allowedauth='digest'/>
<sipsrv addr='_sip_proxy.com_' protocol='UDP' role='proxy'>
<session party='First' type='pc2pc' />
<session party='First' type='pc2ph' />
</sipsrv>
<sipsrv addr='_sip_registrar.com_' protocol='UDP' role='registrar'/>
</provision>" />
</characteristic>
</wap-provisioningdoc>
asango said:
OK, upon your request from here...
http://forum.xda-developers.com/showthread.php?p=2508908#post2508908
...I'll go on in this thread (have not been aware there are 2 different threads with the same name in 2 different branches of the forum...)
Regarding the VPN and GPRS and some more settings (I even found some SIP settings) as XML provisioning files:
The MS reference is here:
http://msdn.microsoft.com/en-us/library/ms889539.aspx
Samples for some important ones go here:
GPRS:
http://www.blackberryforums.com/handheld-forum/91310-windows-mobile-gprs-provisioning.html
...
Click to expand...
Click to collapse
Doesn't the HTC Network Wizard control GPRS settings? I thought that was the major point of that tool.
I would think that users would rather use the HTC tool, which is already pre-loaded with settings for all major carriers, rather than enter them in manually in Makisu...
I'm from Serbia, and I have to enter this settings manually, because HTC didn't support carriers from such a small country... And I do think there are many members of xda-devs which have a similar problem with gprs/mms settings.
pilgrim011 said:
I'm from Serbia, and I have to enter this settings manually, because HTC didn't support carriers from such a small country... And I do think there are many members of xda-devs which have a similar problem with gprs/mms settings.
Click to expand...
Click to collapse
Ok, so there may be a need.
Could you tell me which variables of the XML settings file are the ones that generally need to be changed/entered? In most CSP/XML files usually only a few of the many variables actually need changing in 99% of the circumstances.
bengalih said:
Doesn't the HTC Network Wizard control GPRS settings? I thought that was the major point of that tool.
I would think that users would rather use the HTC tool, which is already pre-loaded with settings for all major carriers, rather than enter them in manually in Makisu...
Click to expand...
Click to collapse
May be, but I think not for the VPN settings.
And even if it would, the point is that it must always be configured manually and interactively after a hard reset.
I don't think that the HTC Wizard is generating n XML file that can be used for an automated install.
asango said:
May be, but I think not for the VPN settings.
And even if it would, the point is that it must always be configured manually and interactively after a hard reset.
I don't think that the HTC Wizard is generating n XML file that can be used for an automated install.
Click to expand...
Click to collapse
Actually, the HTC Network wizard is just pulling out the XML file you choose from its provisioning.zip file. So you could just pull out the one you need from the zip and use that. Then you have the same thing that Makisu give you...an XML file.
Makisu doesn't really "automate" anything other than the process of creating the XML file from user input. The alternative is creating the XML file from scratch. Many people are intimidated by XML...or at least it is more error prone. With Makisu you just are asked the questions, and it fills out the XML file for you.
However most people won't find themsleves using Makisu like they use other programs for phone setup (SASHIMI, UC, etc) because once you use Makisu to create the XML file once, you may never need to use it again...
Bengalih, first off great set of programs. The only question i have so far with Makisu is it able to copy some of the setting for the email account? I know for my email to be able to send out i have to have the following checked under the settings box:
outgoing server requires auth; use the same user name and password for sending email; requires SSL for Incoming and Outgoing email. Your program is great and a real time saver when i need to do a hard reset....i was wondering is there any way it can do this or maybe on a future update. Thanks
elosogrande7076 said:
Bengalih, first off great set of programs. The only question i have so far with Makisu is it able to copy some of the setting for the email account? I know for my email to be able to send out i have to have the following checked under the settings box:
outgoing server requires auth; use the same user name and password for sending email; requires SSL for Incoming and Outgoing email. Your program is great and a real time saver when i need to do a hard reset....i was wondering is there any way it can do this or maybe on a future update. Thanks
Click to expand...
Click to collapse
Are you setting up a POP or IMAP account?
I believe based on the current settings, Makisu will do what you are asking for POP3 accounts, but not IMAP (i.e. SSL and outgoing auth).
I will try to add these additional options for toggling on and off in the next version.
bengalih said:
Are you setting up a POP or IMAP account?
I believe based on the current settings, Makisu will do what you are asking for POP3 accounts, but not IMAP (i.e. SSL and outgoing auth).
I will try to add these additional options for toggling on and off in the next version.
Click to expand...
Click to collapse
oh really...yea its imap that im using....i guess i can try to use the pop3 but if u can make it work for the imap that would be awesome....thanks either way
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!
Hello!
This is actually my first post here.
I have been developing some android apps but I have never modded any roms.
My Galaxy Tab 2 10" is terribly slow with the stock rom and I would like to wipe it and install MM.
Is there anybody that could point me to some step by step guide?
Thanks in advance
mapkozaffo said:
Hello!
This is actually my first post here.
I have been developing some android apps but I have never modded any roms.
My Galaxy Tab 2 10" is terribly slow with the stock rom and I would like to wipe it and install MM.
Is there anybody that could point me to some step by step guide?
Thanks in advance
Click to expand...
Click to collapse
<b>HOW TO ROOT Galaxy Tab 2 10.1 Model GT-P5113, GT-P5110 or GT-P5100</b><br />
<br />
<font color="Red"> <b>This solution requires access to a PC running Windows.</b> </font> Linux & Apple install info: post #203. <br />
This process adds 1 to your Download Counter (indicates tablet is customized unless reset to zero). <br />
Like everyone else on xda-developers, I make no guarantees nor bear any responsibility for your Samsung Galaxy Tablet(s). <br />
<br />
<b><font color="Red">This procedure works on stock 4.03 ROM but may not work if your new tablet comes with 4.04 installed. <br />
For those who receive a new tablet running 4.0.3 : ROOT your tablet <font color="Blue">BEFORE </font>you install 4.0.4 update<br />
and if you update to a 4.0.4 ROM by installing a zip file via CWM5 your access to CWM5 should remain. <br />
<font color="Blue">If you used KIES to update to 4.04 BEFORE rooting OR received a new tablet that came loaded with 4.04, <br />
use</font> workaround at post 325. <br />
</font></b><br />
<br />
<b>What you need:</b><br />
1. Odin3-v1.85_3.zip<br />
2.ClockworkMod Recovery Version 5.5.0.4: <b> is no longer available for download so you can try using philz_touch_4.93.6-p5100.zip and his .tar</b> versions which should work as well or better than 5.5.0.4 did. Download BOTH the zip and tar versions.<br />
3. If you never installed Samsung KIES, you MUST install Samsung USB Drivers <b>BEFORE</b> any of the above (so your PC connects to tablet). <br />
<br />
<b>IMPORTANT:</b> Copy <b>philz_touch_4.93.6-p5100.zip</b> to the ROOT of your <b>external</b> sdcard ( /mnt/<b>ext</b>SdCard ). This is the micro sdcard you insert in tablet slot. Your <b>/mnt/sdcard</b> folder is internal memory (not recognized in CWM recovery).<br />
<br />
<b><i>To avoid confusion about using the Volume rocker switch, I'll refer to side closest to POWER button as LEFT/Volume DOWN and side away from power switch as RIGHT/VolumeUP. </i></b><br />
<br />
<b><font color="Red">STEP 1:</font></b><br />
Turn tablet OFF and restart in download mode by pushing and holding Power & <b><font color="Red">Volume UP/RIGHT</font></b> buttons at same time. When wording with yellow triangle appears, push <b>Volume down</b> to continue into download (ODIN) mode. Don't plug tablet into computer yet.<br />
<br />
<b><font color="Red">STEP 2:</font></b><br />
Make sure KIES (if installed) is closed and not running. <br />
Extract <b>Odin3 v1.85.exe</b> and run it.<br />
<br />
<b><font color="Red">STEP 3:</font></b><br />
Connect tablet to computer.<br />
In Odin, click <b>PDA</b> button. Select <b>philz_touch_4.93.6-p5100.tar</b> file you downloaded and click <b>START</b> button. <br />
Let Odin install files. When it's done installing CWM, box turns <b><font color="Lime">GREEN</font></b> and tablet will reboot.<br />
<br />
<b><font color="Red">STEP 4:</font></b><br />
Disconnect tablet from computer. Turn tablet OFF and restart in recovery (CWM) by pushing and holding <b><font color="red">Power & Volume DOWN/LEFT</font></b> buttons at same time. When Samsung Tab 2 10.1 logo appears, you can release power button but continue holding volume button for a few more seconds. Note: If you've done this on other Samsung devices, you will notice that it takes longer before blue CWM text appears ... just be patient. <br />
<br />
Once you are in recovery, use volume button (UP/DOWN/LEFT OR RIGHT) to move around and POWER button to select an option. <br />
Select <b>install zip from sdcard</b>. Choose <b>philz_touch_4.93.6-p5100.zip</b>) file you already copied to root of sdcard. <br />
<br />
When rooting is finished, choose <b>reboot system now</b> from CWM menu.<br />
<br />
<b><font color="Red">DONE !</font></b><br />
<br />
You should now be rooted. Depending on your Tab2 model, you may need to manually install SuperUser and disable <b>SuperSU</b> before you can install or use all root goodies.<br />
<br />
<i><font color="Green">Now that your Tab 2 10.1 is rooted, I strongly suggest going to Play Store and install a free app called <b>Quick Boot</b>. It lets you reboot into CWM the easiest & fastest way. Then reboot into Recovery (CWM) and make a Backup BEFORE you do ANYTHING else to your tablet. </font></i><br />
<br />
<b><font color="Purple">WARNING:</font> Do not install ROM Manager until developer says app will support Tab2 10.1 </b> < Posting this because someone bricked their Tab2. <br />
In addition, ROM Toolbox may not work properly (1 crash reported). <br />
<br />
<i>Thanks to nycbjr, xoomdev, Android Groupee, nitr8, Codeworkx snd trevd for help and pieces of the aforementioned process. </i><br />
<br />
<b>RE-ROOTING</b><br />
If you do a firmware update, simply re-root using same procedure and tablet will retain root status (until you do another firmware sometime in the future). <br />
<br />
<b>UNROOTING</b><br />
I have successfully unrooted my GT-P5113: <b>[How to] UN-ROOT Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110]</b><br />
If you're curious about my complete analysis of this tablet, where to buy accessories at <b>LOW prices </b><br />
and my feedback after testing a few custom ROMs, read my <b>Galaxy Tab2 10.1 Review</b> on epinions.<br />
<br />
Enjoy,<br />
<br />
Glenn <br />
<br />
<font color="Gray"><br />
| Nexus 7 | Galaxy S II | ASUS TF700 | Jura J9 < Love my digital expresso machine<br />
(Sorry y'all ... sold my Tab2 10.1 many moons ago but I have updated the download links shown above). <br />
</font><br />
<font color="MediumTurquoise">Those who click <b>THANKS</b> are appreciated. </font><br />
<br />
<b><i>P.S. Samsung 4.0.4 was my NEW favorite ROM (until I sold my last T2). <br />
404 was faster & smoother than ANY other current custom ROMs!</i></b> and found more WiFi signals & faster tether to my Sprint E4GT Hotspot! Now my Asus TF700 is The Bolt.
Sent from my SM-N910V using Tapatalk
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
If you check out the development thread, you will find roms and all sorts of things for our aging tab.
Sent from my SM-N910V using Tapatalk
mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
If your already rooted then :
This cm13 will do it fine for marshmallow : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
And this twrp to flash it :http://forum.xda-developers.com/gal...overy-team-win-recovery-project-twrp-t3464050
Just follow the instruction and it will be fine :good:
Get yourself a custom recovery, like TWRP.
mapkozaffo said:
Thanks a lot, but what do I do after the device is rooted?
How do I wipe out the existing rom and install MM?
Thanks!
Click to expand...
Click to collapse
if you dont know what you are doing. you shouldnt flash anything.
first step for you. READ!! read all kind of threads here in tab2 forum.
it will help you a lot
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?
Trying to enable Daydream.
I changed build.prop device to sailfish, but I do not have /system/etc/permissions/handheld_core_hardware.xml file, where would I add the 2 permissions for vr?
Code:
<feature name="android.software.vr.mode" />
and
<feature name="android.hardware.vr.high_performance" />
Please let us know
I would also like to know how to do this. Netflix VR requires Daydream.
I'm pretty sure you need the Daydream libraries installed