I want my Jam not to ask me Pin code at start up, how can i do this ? Any program or settings u know ? I will use this function in phonealarm , when switching the flight mode profile to normal radio mode profile ( yes it can do this according to the daily schedule u made )
Hello
Go to menu phone in start menu or settings-->make sure that the checkbox on the separator phone saying:require a Pin when phone is used is off!!that's it!
Cheers
Thanx a lot Dervian, that was i needed.
Hi
sorry if this is double posted - first time i posted in this thread structure here
first: Thanks a million for a great tool (had to appraise your great effort )
i have a HTC touch pro 2 (couldnt find any solution reading setting manual that worked for pro2), and have these questions:
1. I cant get the three times tapping on the batteryicon to work - noting happens. What do i have to do to make this work on my device? (where is the capacitive sensor located on a pro 2 ?)
Alternative where is the capacitive wipe up located on this device and how to activate this feature?
2. can i make a hardware button as eg "home" button unlock ? If so what do i have to do? I have tried entering the code UnlockKeySequence in section "Keyboard" (i have checked none of the options and i have left blank the field "UnlockedKeys" - is that correct?) for each of the 4 hardware buttons as specified in the manual but it appears that all are ignored by TouchLockPro:
15 = End:
114 = Talk
91 = Home
8 = Back:
The hardware keys seems to be responsive eventhough i have not entered any addresses in field "unlockKeys" - thats not supposed to work like that ?
3. I want keep alive OFF to save battery power (i take disabling this is identical to putting device in sleep mode?) - how can i see if this is disabled ?
4. In section "Telephone API" i entered the command string "!SCREENOFF " in the fields "incoming", "connected" "ended" but it seems that the screen bounces back on again after a short OFF period - it seems to just when connection is established. This is a BUG - or am i missing some setting?
thanks Nolan
Hello everybody,
Like many others here I had problem with GPS on my device. (unable to get a lock)
So I began searching for a solution which does not involve rooting.
And I cam across a solution somewhere on internet.
I will post it here for you people!(Please note down the default settings in case you want to revert back).
From your phone dialer type *#*#1472365#*#*- This will bring up the secret GPSSetup2 application.
Settings\Parameter Settings\Address\Server Type: 1x MPC
Settings\Parameter Settings\Position mode: option3
Settings\Fix Request Settings\Session Operation: Standalone
Settings\Fix Request Settings\Server Option: Local
gpsOne XTRA\Xtra Enable: Enable
After the following steps: Save the settings by exiting and then turn off and on your phone.
After this: use*#*#1472365#*#* and again enter GPSSetup2 application.
Enter: Commands/TTFF test and press start test. It will run the test 5 times. Exit the application.
And after this you will get gps lock in a few seconds. I get it under 10seconds.
Please Note: I live in India, and I do not know the following setting applies for outside India users too.
Thanks.
I am using Galaxy 3, 2.1 update 1 unrooted.
PS: Please run the TTFF test under clear sky for faster response time.
Just used this fix on tmobile galaxy apollo in the uk and it worked well.
Sent from my GT-I9000 using XDA App
Dont work for me :-( but i have froyo..
Sent from my GT-I5800 using XDA App
i hav a better solution.. if ur g3 boots with gps off,it may not work.. but it wil work if u boot ur g3 with gps on..
cheers..
thanks a ton for this tip. now I get lock in around 1 min. (i5800 - 2.1).
Now I can use my GPS!
gps in jpf2.2 works well under
to 2.2 froyo users setting this parameters
in phone dialer insert this code *#*#3214789650#*#*
Settings\Parameter Settings\Position mode: option3 default: option2
Settings\Fix Request Settings\Session Operation: Standalone default: MS based
Settings\Fix Request Settings\Server Option: Local default: Default
gpsOne XTRA\Xtra Enable: Enable default: Disable
in "Commands" press “Get position” select "Log GPS info to SD card" and press "Start GPS" wait locate longitude and latitude and press "stop test".
Exit the application
One of the most popular practices amongst software developers is to leave ‘backdoors’ within the code, which essentially allow anyone with knowledge to get into the system at a much deeper level than you’d expect from an end-user. These backdoors aren’t always with a malicious intent; most of the time, they allow the OEM or programmer to get into the system for troubleshooting when other, usual modes of access have been blocked. They can be quite friendly and helpful if you know what you’re doing.
Smartphones have a good share of these as well, where they’re generally known as secret codes. Most of the time, these numeric/symbolic sequences allow you to access hidden menus, diagnostic tests, areas that could change some of the most basic parameters of your device and whatnot. These secret codes, in fact, have not been exclusive to smartphones, but have long been a part of the dumb-phones and then the feature-phones before most major OEMs joined the smartphone bandwagon. For those devices that run Android, certain codes are shared across the board, and hence, can be used on a variety of devices.
What follows is a collection of some of the secret codes common to the Android platform. All of these would be entered through the phone dialer (just punch in the sequence as shown). Since most hidden menus are manufacturer specific, there’s no guarantee that they’ll work across all Android smartphones, but you can try them out nevertheless on your Samsung, HTC, Motorola, Sony and other devices. Be advised, though, that some of these can cause serious changes to your device’s configuration, so don’t play with something that you don’t fully understand.
*#*#4636#*#* phone information
*2767*3855# hard reset
*#*#7780#*#* factory reset
*#*#7594#*#* change end call/power option
*#*#197328640#*#* service mode
*#*#273283*255*663282*#*#* file copy screen (backup media files)
*#*#526#*#* wlan test
*#*#232338#*#* shows wifi mac address
*#*#1472365#*#* gps test
*#*#1575#*#* another gps test
*#*#232331#*#* bluetooth test
*#*#232337#*# shows bluetooth device address
*#*#8255#*#* gtalk service monitor
Samsung Secrets Code
*#*#0283#*#* packet loopback
*#*#0*#*#* lcd test
*#*#0673#*#* melody test
*#*#0842#*#* device test (vibration test and backlight test)
*#*#2663#*#* touch screen version
*#*#2664#*#* touch screen test
*#*#0588#*#* proximity sensor test
*#*#3264#*#* ram version
Samsung Secrets codes to get firmware version information:
*#*#4986*2650468#*#* pda, phone, h/w, rfcalldate
*#*#1234#*#* pda and phone
*#*#1111#*#* fta sw version
*#*#2222#*#* fta hw version
*#*#44336#*#* pda, phone, csc, build time, changelist number
*#272*IMEI# - To change the salescodes and reset the user data
Thank you !!
Thank you very much ! It's very usefull ... :good:
rahulchauhan700 said:
Thank you very much ! It's very usefull ... :good:
Click to expand...
Click to collapse
your welcome..
thanks for sharing, but on JB 4.1.2 many of these codes are removed from samsung, f.e. the *2767*3855# hard reset code, as it has been prooved that it could be executed via a malicious browser website...
skiflyer said:
thanks for sharing, but on JB 4.1.2 many of these codes are removed from samsung, f.e. the *2767*3855# hard reset code, as it has been prooved that it could be executed via a malicious browser website...
Click to expand...
Click to collapse
Actually, some still work, but our phone uses the old format instead of the new. So don't type "*#*#1234#*#*", but "*#1234#". Same for service mode: "*#197328640#". Etc. Also interesting: "*#9900#" for "SysDump" and fast dormancy.
wats the code for java test menu in samsung gt-c3312 plz tel
Cool tenx
Great
Thank You very much, it helps a lot to find a original among hell of copies in the market
South impassev
Perfect job! All in one place!
Great job. Thank you very much.
Good job keep it up thank
unlock
Samsung Hidden Codes
Not all work due to android o.s. changes and some may be missing
*#TESTMODE#
*#03# Nand Flash Unique Number
*#06# IMEI INFO.
*#745#
*#746#
*#0011# ServiceMode
*#0514# SysDump (shorter list)
*#0808# Qualcom USB settings
*#1111#
*#1575#
*#2222#
*#2263# ServiceMode - toggle Auto/WCDMA/GSM/LTE bands and modes
*#2580#
*#2684#
*#2866#
*#7284# Qualcom USB settings
*#8888# ServiceMode - READ FTA HW VERSION
*#9090# ServiceMode - DIAG CONFIG
*#9900# SysDump
*#32489#
*#66336# ServiceMode - MDM Ramdump mode
*#123456#
*#147852#
*#279301#
*#301279#
*#369852#
*#1478963#
*#3214789#
*#3698741#
*#4238378#
*#5337632#
*#6984125*#
*#22553767#
*#22558463# ResetTotalCallTime
*#73876766#
*#99007788#
*#197328640# ServiceMode - DEBUG SCREEN (1 Basic Information - same as 0011)
*#2767*2878#
*#738767633#
*#3214789650#
*#7387678387#
*#7387677763#
*#4387264636#
*#27663368378# ServiceMode - MAIN MENU (7 DEBUG SCREEN)
*#827828868378#
---------- Post added at 11:15 PM ---------- Previous post was at 11:08 PM ----------
Samsung Hidden Codes
Not all work due to android o.s. changes and some may be missing
*#TESTMODE#
*#03# Nand Flash Unique Number
*#06# IMEI INFO.
*#745#
*#746#
*#0011# ServiceMode
*#0514# SysDump (shorter list)
*#0808# Qualcom USB settings
*#1111#
*#1575#
*#2222#
*#2263# ServiceMode - toggle Auto/WCDMA/GSM/LTE bands and modes
*#2580#
*#2684#
*#2866#
*#7284# Qualcom USB settings
*#8888# ServiceMode - READ FTA HW VERSION
*#9090# ServiceMode
*#9900# SysDump
*#32489#
*#66336# ServiceMode - MDM Ramdump mode
*#123456#
*#147852#
*#279301#
*#301279#
*#369852#
*#1478963#
*#3214789#
*#3698741#
*#4238378#
*#5337632#
*#6984125*#
*#22553767#
*#22558463# ResetTotalCallTime
*#73876766#
*#99007788#
*#197328640# ServiceMode - DEBUG SCREEN (1 Basic Information - same as 0011)
*#2767*2878#
*#738767633#
*#3214789650#
*#7387678387#
*#7387677763#
*#4387264636#
*#27663368378# ServiceMode - MAIN MENU (7 DEBUG SCREEN)
*#827828868378#
:laugh: it works very well
pressed thx to you
thx very much..
It's Very Informative
It's Very Informative. Thanks for Sharing with us
thanks, very useful :good:
Hi all, full testing hardware
* # 0 * #
Looking for the dialer code to enter into calculator to access hidden menu on a Sprint Galaxy tab2, I believe it is a long string of letter and symbols it ends in "+" sign. Just can't find my notes, the standard ##3282# or ##3424# do not work.Thanks
This is great, thanks, although I don't know what half of them mean
The Secret Codes are working ... :laugh:
Very Thanks Bro... :good:
Thnks for that! Been searching for those
Does anyone know how to invoke the slideshow (and how to get out of it).
Do you mean demo mode -> com.nook.partner.daydream.DayDream?
Maybe try:
Code:
adb shell am start -n com.nook.partner.daydream.DayDream
(I don't have partner.apk running so I can't tell immediately.)
Renate NST said:
Do you mean demo mode -> com.nook.partner.daydream.DayDream?
Maybe try:
Code:
adb shell am start -n com.nook.partner.daydream.DayDream
(I don't have partner.apk running so I can't tell immediately.)
Click to expand...
Click to collapse
No, that doesn't do it. ADB returns the error: Bad component name: com.nook.partner.daydream.DayDream
I found this in another post for DISabling demo mode (thought that might be useful....):
"--- turn your Nook ON
--- go to Settings - Screen - on Screen window press-and-hold top-right button AND same time keep tapping the "Screen" caption (on a top of display)
--- Demo Mode will pop up on your display
--- undo 'Toggle the demo mode'
--- now to activate "normal" mode switch off-and-on your Nook !"
This does, indeed make a third entry appear under "Screen" (and greys out the screen timeout option), but checking the toggle demo mode option doesn't seem to do anything so I guess there is additional magic, some odd button combination or a secret handshake, dance, etc., that actually starts demo mode. That knowledge remains unknown to this mortal. Powering down/restarting, rebooting or putting the screen to sleep and reawakening (I didn't try a kiss...) did not do anything. And it just went to sleep on its own right now and on awakening was still in normal mode
I know there is a db entry where the mode can presumably be turned on or off, but the same requirement for additional unknown falderol may apply to actually get the show started. Hmm.
Edit: OK, so I took a look at the packages. Perhaps the one you suggested is for the newer Nooks? Anyway, there is com.bn.demomode so I tried a similar command to the one you suggested: am start -n com.bn.demomode.DemoMode. I got the same error as before (Bad component name).
HOWEVER.....as I was typing this the device just started going through the slides!? So I have discovered one thing already. It's not going to work for what I had hoped. It apparently only reads png images and there is no control over the slides at all, just a relentless circle of the images.
The good news is that the instructions for getting out of demo mode work
The slides are resources inside partner.apk:
res/drawable-xhdpi-v4/demo_00_splash.png
res/drawable-xhdpi-v4/demo_01_glowlight.png
res/drawable-xhdpi-v4/demo_02_display.png
res/drawable-xhdpi-v4/demo_03_navigation.png
res/drawable-xhdpi-v4/demo_04_shop.png
res/drawable-xhdpi-v4/demo_05_touch.png
res/drawable-xhdpi-v4/demo_06_battery.png
res/drawable-xhdpi-v4/demo_07_support.png
res/drawable-xhdpi-v4/demo_08_wifi.png
If you want a real slide show, it's probably better to use an app.
Renate NST said:
The slides are resources inside partner.apk:
res/drawable-xhdpi-v4/demo_00_splash.png
res/drawable-xhdpi-v4/demo_01_glowlight.png
res/drawable-xhdpi-v4/demo_02_display.png
res/drawable-xhdpi-v4/demo_03_navigation.png
res/drawable-xhdpi-v4/demo_04_shop.png
res/drawable-xhdpi-v4/demo_05_touch.png
res/drawable-xhdpi-v4/demo_06_battery.png
res/drawable-xhdpi-v4/demo_07_support.png
res/drawable-xhdpi-v4/demo_08_wifi.png
If you want a real slide show, it's probably better to use an app.
Click to expand...
Click to collapse
Again, I think those might be for a device other than the original NST. There seems to be no partner.apk on the NST and the images for demo mode are in /system/media/slideshow/standard/default but I agree with you about the need for something else. I was just checking to see if a local resource could be harnessed before I looked for something external.
nmyshkin said:
Again, I think those might be for a device other than the original NST.
Click to expand...
Click to collapse
Oops. Sorry, I got all confused. I was thinking NG2 or NG3.
Code:
# cd /data/data/com.android.providers.settings/databases
# sqlite3 settings.db
sqlite> update secure set value='on' where name='demo_mode';
sqlite> .q