Database Users

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

[Q] KK4.4.4 External SDcard Fix. WTH?

In order to give permission to access my SDcard I followed the below instructions.
Using a root-enabled file manager navigate to, "/system/etc/permissions"
Edit "platform.xml" and find the "WRITE_EXTERNAL_STORAGE permission."
Add an additional group definition for this permission: <group gid=”media_rw” />
Save the changes to the file.
Restart the phone.
It worked. The problem I'm having now is my Bluetooth will not load. It starts dark green then goes gray.
To try and fix this I simply re-edited the platform.xml and deleted,
<group gid=”media_rw” /> and did a cold restart. Bluetooth still will not working. Any ideas as to
why this happened and how to fix without re-installing.

[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.

HotSpot Setup(Unlocked HTC10 version) - VZW

Thanks for the info from RickOSidhe and jhuff83.
Combining both of the directions i managed to get the hotspot working on VZW Unlimited grandfathered plan with the unlocked HTC 10 on the Verizon network.
PART 1:
Edit this file first:
/system/customize/ACC/default.xml
RickOSidhe
"tethering_guard_support=false (default: true)
TetheringGuard_Rule=0 (default: 9)"
Line 191
From ->
172 <app name="Android_Networking">
...
190 <item type="boolean" name="tether_use_default_upstream">false</item>
191 <item type="boolean" name="tethering_guard_support">true</item>
192 <item type="boolean" name="tethering_roaming_specific">false</item>
193 <item type="string" name="tethering_specific">NONE</item>
194 <item type="string" name="usageCustomerWhiteList">com.htc.android.mail;com.orangelabs.rcs</item>
195 <item type="boolean" name="use_default_apn">true</item>
196 </app>
To ->
172 <app name="Android_Networking">
...
190 <item type="boolean" name="tether_use_default_upstream">false</item>
191 <item type="boolean" name="tethering_guard_support">false</item>
192 <item type="boolean" name="tethering_roaming_specific">false</item>
193 <item type="string" name="tethering_specific">NONE</item>
194 <item type="string" name="usageCustomerWhiteList">com.htc.android.mail;com.orangelabs.rcs</item>
195 <item type="boolean" name="use_default_apn">false</item>
196 </app>
Line 1256
From ->
1254 <app name="Tethering_provision">
1255 <item type="integer" name="CustomziedCarrierDialogType">0</item>
1256 <item type="integer" name="TetheringGuard_Rule">9</item>
1257 </app>
To ->
1254 <app name="Tethering_provision">
1255 <item type="integer" name="CustomziedCarrierDialogType">0</item>
1256 <item type="integer" name="TetheringGuard_Rule">0</item>
1257 </app>
PART 2:
jhuff83
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a text editor
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
NOTE:
1. Mount Read/Write File system-
Type this in the terminal:
# adb shell
# su
Choose one: (for security mount /system back to RO when finished)
Mount system RW:
# mount -o rw,remount,rw /system
Mount system RO:
# mount -o ro,remount,ro /system
2. If you restart - mine is having this issue on the unlocked carbon grey- you may need to select the proper antenna.
2a. From the Dialer enter: *#*#4636#*#*
2b. Goto "Phone information"
2c. Change the the network type to either "CDMA/EvDo/GSM/WCDMA/LTE auto" or an other option of your choice if you want LTE etc.
2d. Exit to the home screen

Thanks but line 191 looks the same?
Sent from my SM-G935V using Tapatalk

default is true* typo.... fixing OP now

This is with the Verizon RUU installed, right?
Sent from my IBM Selectric

Brnway said:
This is with the Verizon RUU installed, right?
Sent from my IBM Selectric
Click to expand...
Click to collapse
This is for the unlocked version + the verizon radios.
This i just confirmed working on the verizon RUU also
FYI: my phone is an unlocked (carbon grey htc10) s-off rooted stock on both using vzw

the build.prop changes are not needed. but never hurts to change them i guess

@afuller42 good to know.
If anyone knows why on the stock HTC10 unlocked version with the verizon radios the antenna changes back after reboots, maybe we can get a fix or a temp fix better then opening the special settings after each reboot.

codelinx said:
@afuller42 good to know.
If anyone knows why on the stock HTC10 unlocked version with the verizon radios the antenna changes back after reboots, maybe we can get a fix or a temp fix better then opening the special settings after each reboot.
Click to expand...
Click to collapse
Try the ol' LTE ON/OFF app from the Thunderbolt days. It works on both the M8 and M9 on MM.....don't have my 10 yet to confirm it does. Will take the pain away of dialing to get to the same place.

good idea... that is some throw back, but i went stock -> unlocked root, s-off -> RUU root/s-off-> Lee Droid, and now i am pretty happy.

My signal is weaker than my wife's s7 now that I'm on the unlocked HTC running it in Verizon, my note 4 had a stronger signal than this. Is anyone else having this issue?

I don't have
<item type="integer" name="TetheringGuard_Rule">9</item>
in my default.xml file. Running stock 1.19.605.22

Working on my VZW HTC 10
First item, thank you for the great post. I am sending this via my laptop using my HTC 10 as hotspot.
A few quick adds:
- I pulled the default.xml file over to the laptop and edited using Notepad++. It does a great job with .xml files, displays line numbers, and doesn't mess with permissions. I didn't bother pushing it back, just used Windows Explorer to copy it back (renaming the original file to a default.xml.bak)
- I'm on an unlocked and rooted Verizon HTC 10 (6545LVW), with S-Off and unlocked via SunShine
- The line numbers in my file were off just slightly from your example, but within a few lines so your guide got me where I needed to be
- I left line 193 alone as <item type="boolean" name="tethering_guard_support">true</item>, so I guess it's not needed(?)
- I changed line 1249 to <item type="integer" name="TetheringGuard_Rule">0</item> (mine was originally set to 1)
- I used BuildProp Editor to add the parameter/value net.tethering.noprovisioning=true (please make sure you always check the permissions (0644 -rw-r--r--) and Owner and Group (root) anytime you modify your BuildProp file. I've learned that one the hard way, as I'm sure many of you have as well...
Bottom line is, native Mobile Hotspot is up on my stock M ROM. Yay!!
Thanks again for the info.

CaptWilly said:
First item, thank you for the great post. I am sending this via my laptop using my HTC 10 as hotspot.
A few quick adds:
- I pulled the default.xml file over to the laptop and edited using Notepad++. It does a great job with .xml files, displays line numbers, and doesn't mess with permissions. I didn't bother pushing it back, just used Windows Explorer to copy it back (renaming the original file to a default.xml.bak)
- I'm on an unlocked and rooted Verizon HTC 10 (6545LVW), with S-Off and unlocked via SunShine
- The line numbers in my file were off just slightly from your example, but within a few lines so your guide got me where I needed to be
- I left line 193 alone as <item type="boolean" name="tethering_guard_support">true</item>, so I guess it's not needed(?)
- I changed line 1249 to <item type="integer" name="TetheringGuard_Rule">0</item> (mine was originally set to 1)
- I used BuildProp Editor to add the parameter/value net.tethering.noprovisioning=true (please make sure you always check the permissions (0644 -rw-r--r--) and Owner and Group (root) anytime you modify your BuildProp file. I've learned that one the hard way, as I'm sure many of you have as well...
Bottom line is, native Mobile Hotspot is up on my stock M ROM. Yay!!
Thanks again for the info.
Click to expand...
Click to collapse
If you don't turn tethering guard to false you may have intermittent issues with wifi and/or tethering working after using the hotspot one time. Sometimes it will require a reboot of the phone to work properly again. Just disable it (false) and be rid of it.
Sent from my HTC6545LVW using Tapatalk

So I successfully got this to work, but then I needed to restore a backup because of a bootloop that an Xposed module caused, and now when I edit the default.xml file, it gets restored to the original on reboot. What could be happening here?! I'm stumped on this one..
UPDATE: so I ended up having to flash the entire 1.85.605.8 RUU again, re-flashing TWRP and SuperSU, and re-editing default.xml - but it took this time. So weird. Cheers

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?