Jump to content

How-To - Add a home screen shortcut to the Debug Menu


digiblur

Recommended Posts

I've only tested this on the Samsung Note2, but I believe it also works on the S3 since they are so close in code bases.  If anyone can test this on a S4 please let me know.

 

If you've used an HTC device before you probably know how easy it is to add a shortcut to the Debug screen.  On the Samsung devices it's a little bit harder.  Here's how to set it up:

 

Install SL4A from here:
https://code.google.com/p/android-scripting/downloads/detail?name=sl4a_r6.apk&can=2&q=

Open the App

Hit your Menu button -> Preferences -> Scroll down and check Hide Notifications.  (I think that's the only one I changed)

DEBUGS4LA1.png

 

Hit Menu -> Add -> Shell -> Type in debugmenu in front of the .sh
Type this exactly in the box below the file name(it is case sensitive!)

 

You can download the 4.3 Android Scripts with the information already typed and skip this step of creating the scripts, extract the zip to the sl4a folder on your sdcard:  -Download 4.3 Scripts-

 

For Android 4.3:

 

su -c 'am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://DEBUG'

 

For pre-Android 4.3:

am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://DEBUG

 

DO NOT put a space at the end.  I had to hit space as my keyboard was underlining the last word.

DEBUGS4LA2.png

Hit Menu -> Save & Exit

Tap debugmenu.sh -> then the little silver gear (2nd icon)

 

DEBUGS4LA3.png

It should open your debug menu.  Go ahead and back out to your home screen.

Tap and hold on your home screen and pick the option to add a Shortcut (this depends on your launcher)

Pick the S4LA Icon with description of Scripts

DEBUGS4LA4.png

Pick your debugmenu.sh

Make sure you pick the little silver gear

DEBUGS4LA5.png

 

That's it! 

Of course if you are running my ROM you won't have the 777468 code on the debug screen either, basically two actions to get into the LTE engineering screen.  
 

  • Like 5
Link to comment
Share on other sites

Tried on stock unrooted S4 for you but get this when running:

 

Broadcasting: Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://DEBUG }                                                                                 java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS                                                                                                                                                            at android.os.Parcel.readException(Parcel.java:1425)                                                                                                                                at android.os.Parcel.readException(Parcel.java:1379)                                                                                                                                at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:2435)                                                                                                at com.android.commands.am.Am.sendBroadcast(Am.java:616)                                                                                                                            at com.android.commands.am.Am.run(Am.java:121)                                                                                                                                      at com.android.commands.am.Am.main(Am.java:82)                                                                                                                                      at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)                                                                                                              at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:243)                                                                                                                   at dalvik.system.NativeStart.main(Native Method)

 

 

Sent from my SPH-L900 using Tapatalk 2

 

 

Link to comment
Share on other sites

Tried on stock unrooted S4 for you but get this when running:

 

Broadcasting: Intent { act=android.provider.Telephony.SECRET_CODE dat=android_secret_code://DEBUG }                                                                                 java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS                                                                                                                                                            at android.os.Parcel.readException(Parcel.java:1425)                                                                                                                                at android.os.Parcel.readException(Parcel.java:1379)                                                                                                                                at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:2435)                                                                                                at com.android.commands.am.Am.sendBroadcast(Am.java:616)                                                                                                                            at com.android.commands.am.Am.run(Am.java:121)                                                                                                                                      at com.android.commands.am.Am.main(Am.java:82)                                                                                                                                      at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)                                                                                                              at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:243)                                                                                                                   at dalvik.system.NativeStart.main(Native Method)

 

 

Sent from my SPH-L900 using Tapatalk 2

 

I'd be curious to see if runs using the terminal emulator.  The command will be the same.  To be honest I've never tried this command on a non-rooted phone though.

Link to comment
Share on other sites

Yesssss I've been waiting for this forever. I was actually gonna PM you and ask if you had any ideas about this. I mean, SignalCheck Pro can now give me the hidden menu too, but this is faster. And more awesome.

Link to comment
Share on other sites

Yesssss I've been waiting for this forever. I was actually gonna PM you and ask if you had any ideas about this. I mean, SignalCheck Pro can now give me the hidden menu too, but this is faster. And more awesome.

Not to take away from Mike's app by any means as his is easier to set up. I wonder who helped point him in the right direction?

  • Like 1
Link to comment
Share on other sites

Not to take away from Mike's app by any means as his is easier to set up. I wonder who helped point him in the right direction?

If you're trying to take credit, you're doing a spectacularly bad job :P

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

Stock Rooted SGS4 user here

 

I typed the command in terminal and got same error as compneo.

 

HOWEVER... if i enter su and get root access and run the command, it does indeed pop up the unlock code screen for the 777468 code.

 

now is there a way to get S4LA to call for root access before running the script?

Link to comment
Share on other sites

actually i answered my own question...

 

su -c 'am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://DEBUG'

 

for the script will call root access for the command and thus allow you to enter Unlock Code to get into Debug menu :)

Link to comment
Share on other sites

  • 1 month later...

Digiblur

I typed followed the instructions and the little icon appears for a second then nothing? Here is what I typed?

Posted Image any thoughts?

 

Sent from my SPH-L900 using Tapatalk

 

 

Link to comment
Share on other sites

Digiblur

I typed followed the instructions and the little icon appears for a second then nothing? Here is what I typed?

Posted Image any thoughts?

 

Sent from my SPH-L900 using Tapatalk

Make sure there are no spaces after it.

 

Try doing an adb shell from a PC and running the same command manually to see if it works.

Link to comment
Share on other sites

Make sure there are no spaces after it.

 

Try doing an adb shell from a PC and running the same command manually to see if it works.

Yeah no spaces? adb shell? Thats way above my skill level digiblur i am running your rom does that change anyting being rooted?

Link to comment
Share on other sites

Yeah no spaces? adb shell? Thats way above my skill level digiblur i am running your rom does that change anyting being rooted?

Nope that's all fine.

 

If you have the Note2 toolkit still there is a adb-toolkit file in the folder. Go to a command prompt. Plug up your phone. Go to that folder and type adb-toolkit shell and then you can do whatever commands you want to your phone. Type the one for the broadcast and see if it opens the debug on your device.

Link to comment
Share on other sites

Nope that's all fine.

 

If you have the Note2 toolkit still there is a adb-toolkit file in the folder. Go to a command prompt. Plug up your phone. Go to that folder and type adb-toolkit shell and then you can do whatever commands you want to your phone. Type the one for the broadcast and see if it opens the debug on your device.

ok it worked doing it that way. Now what?

Link to comment
Share on other sites

lol well Thanks digiblur it works now and i learned something new as well. This site is like an IT academy for dummies! So I wanted to figure out why it wouldnt work the first time so  I went back and was looking at the screen shot....well i might have spelled a word wrong. Sometimes its the simple things! I guess Ill head to work and do a little tower hunting still to many white dots in Utah!

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). The do have a reserve level. It is seen as great for new technologies which I presume is IOT or 5g slices.  They did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, RVs in Walmart parking lots where mobile needs all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71. 93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline in June for 850Mhz of mmWave in most of Ohio iirc. No reported sightings.
    • T-Mobile Delivers Industry-Leading Customer, Service Revenue and Profitability Growth in Q1 2024, and Raises 2024 Guidance https://www.t-mobile.com/news/business/t-mobile-q1-2024-earnings — — — — — I find it funny that when they talk about their spectrum layers they're saying n71, n25, and n41. They're completely avoiding talking about mmWave.
    • Was true in my market. Likely means a higher percentage of 5g phones in your market.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...