Related
Hello.
I've searched the forum and found no answer to this question. And Android 2.2 is coming/not coming/ coming/ maybe coming, so
is there any way to end call with a key, either power or one of three function keys? Android 2.1.
I will root my phone if it is necessary, no problem.
And if someone knew, how to make calls hands-free with bluetooth... Let's say it, as a business phone my X10mini pro is a disaster, comparing to my previous Nokia N95...
Thanks
A.
I'd love to have a solution for this.
Asc_xda said:
Hello.
I've searched the forum and found no answer to this question. And Android 2.2 is coming/not coming/ coming/ maybe coming, so
is there any way to end call with a key, either power or one of three function keys? Android 2.1.
I will root my phone if it is necessary, no problem.
And if someone knew, how to make calls hands-free with bluetooth... Let's say it, as a business phone my X10mini pro is a disaster, comparing to my previous Nokia N95...
Thanks
A.
Click to expand...
Click to collapse
Not sure but may be Tasker can do it. I have a gesture so that when I put the phone face down, it disconnect from the data network and also hangs the current call. Not sure about doing through a key, but I bet that it's possible.
you might want to have a look at ADB Mask controller..
http://forum.xda-developers.com/showthread.php?t=868423
I used this to change my power button to end call
Look on the first picture.. (Sleep button action during call)
kiwiBratwurst said:
you might want to have a look at ADB Mask controller..
http://forum.xda-developers.com/showthread.php?t=868423
I used this to change my power button to end call
Look on the first picture.. (Sleep button action during call)
Click to expand...
Click to collapse
Tryed just that.. it work flawlessly
Glad I could help
kiwiBratwurst said:
Glad I could help
Click to expand...
Click to collapse
Unfortunately X10 mini pro is not supported, only mini.
:/
A.
Asc_xda said:
Unfortunately X10 mini pro is not supported, only mini.
:/
A.
Click to expand...
Click to collapse
Damn.. sorry bout that.. I wonder what the difference is.. perhaps you could ask the DEV who made it to include the pro.. or ask him what he is changing to make the power button end the call..
He is editing some file for sure. Let's hope he will reveal it.
Sent from my U20i using XDA App
Resolved:
For X10 mni pro.
In file "system/usr/keylayout/mimmi_keypad.kl" change this line:
key 107 POWER WAKE_DROPPED
with this:
key 107 ENDCALL WAKE_DROPPED
For X10 mini change the file
"/system/usr/keylayout/robyn_keypad.kl"
REBOOT!
change pwer key function
im on mini pro also,,is it possible to alter that txt with root explorer ,,? thanks
edit sorry does work after reboot,,,
By the way, after this modification the button continues to work for putting the phone into the sleep mode as well!
One more link, I have not tried though:
http://forum.xda-developers.com/showthread.php?t=850464
for mini users I still recommend using the ADB mask controller tool.
kiwiBratwurst said:
for mini users I still recommend using the ADB mask controller tool.
Click to expand...
Click to collapse
Sure. But what it does it changes the line that I quoted. In fact the information comes from ADB developer
vlissine said:
Sure. But what it does it changes the line that I quoted. In fact the information comes from ADB developer
Click to expand...
Click to collapse
Yep, I know that, I asked the ADB mask DEV in the same thread you did and he answered us both in the same post I'm just saying that the ADB mask controller is quicker (for mini users) and can do a bunch of other stuff too.. (pretty much everything can be done with adb, txt editors and root explorer but its always nice having a GUI to speed things up/simplify things)
parthabhatta said:
One more link, I have not tried though:
http://forum.xda-developers.com/showthread.php?t=850464
Click to expand...
Click to collapse
i want more explanation on this. used ADB mask to change the call button
I think I'll try it, reporting later.
Sent from my E10i using XDA App
parthabhatta said:
One more link, I have not tried though:
http://forum.xda-developers.com/showthread.php?t=850464
Click to expand...
Click to collapse
It seems like it is able to map all buttons except the power and the focus... could try to make an x10 version. ill look into it. the dev seems a bit occupied at the moment, i'll put a 'SE x10 minis not fully working" post.
Sent from my E10i using XDA App
kiwiBratwurst said:
you might want to have a look at ADB Mask controller..
http://forum.xda-developers.com/showthread.php?t=868423
I used this to change my power button to end call
Look on the first picture.. (Sleep button action during call)
Click to expand...
Click to collapse
Thank You, miss that one there
I have been trying to run Ubuntu/debian/backtrack distros on ACE. However I have been getting a segmentation fault error for a busybox chroot command in the scripts.
There is a related thread in these forums if anyone is interested, but unfortunately no solution.
http://forum.xda-developers.com/showthread.php?t=1079898
I am just curious to see if anyone here was successful doing it and if so how. Many users have a similar problem and I have gone through lot of general suggestions given in the above thread, but none of them solved my problem. So just trying my luck here to see if anyone else is interested to get one of those distros running on ACE.
If it can make coffee when succesfull...im interested.
Cheers
progress?
Hi Sandred
Did you find out any more in the end? I had the exact same problem with my Galaxy Ace when trying to install BT5.
If you look on rumah-android.com/install-backtrack-5-linux-on-android.html it seems to show it working on an ACE but I haven't tried using debdroid yet. I'll let you know if I do ever get it working though..
Marcus
marcusdw said:
Hi Sandred
Did you find out any more in the end? I had the exact same problem with my Galaxy Ace when trying to install BT5.
If you look on rumah-android.com/install-backtrack-5-linux-on-android.html it seems to show it working on an ACE but I haven't tried using debdroid yet. I'll let you know if I do ever get it working though..
Marcus
Click to expand...
Click to collapse
Marcus,
If you are referring to second image on the above site, it is not ACE. It is Samsung Galaxy something (if you look at left corner of the image, you see a camera/sensor on front left side of the phone) which is not Ace.
Anyways I was not successful running any distribution at all. I have even tried laika linux. The problem is with busybox which itself is segment faulting. Updating to latest greatest version did not help either. I changed different kernels on our phone and it did nothing. I have tried entering all the commands one by one , everything is ok until chroot command, where it just breaks.
I do not think debdroid app will help either, though I have not yet tried it.
I have not yet given up yet, I will keep trying when ever I get time and keep this thread posted. Thanks for asking.
sandred said:
Marcus,
If you are referring to second image on the above site, it is not ACE. It is Samsung Galaxy something
Click to expand...
Click to collapse
How about "S"?
I got it working on my phone. Just follow post #94 in the link given below:
http://forum.xda-developers.com/showthread.php?t=723493&page=10
phoenix2241987 said:
I got it working on my phone. Just follow post #94 in the link given below:
http://forum.xda-developers.com/showthread.php?t=723493&page=10
Click to expand...
Click to collapse
Would it be too much to ask for a video? I'd really like to see that on ace before deciding if i'm goin' for it!
Thanks in advance!
Ubuntu working on SGA
QNBT said:
Would it be too much to ask for a video? I'd really like to see that on ace before deciding if i'm goin' for it!
Thanks in advance!
Click to expand...
Click to collapse
Here goes, a short demo. Recorded this using screencast application in droid explorer.
http://www.youtube.com/watch?v=wCesfuEXAZI
phoenix2241987 said:
Here goes, a short demo. Recorded this using screencast application in droid explorer.
http://www.youtube.com/watch?v=wCesfuEXAZI
Click to expand...
Click to collapse
Thank you! I'm sure that the recording fps is pretty low, so how smooth does it actually run on a ace?
phoenix2241987 said:
I got it working on my phone. Just follow post #94 in the link given below:
http://forum.xda-developers.com/showthread.php?t=723493&page=10
Click to expand...
Click to collapse
thanks, it's working now
phoenix2241987 said:
I got it working on my phone. Just follow post #94 in the link given below:
http://forum.xda-developers.com/showthread.php?t=723493&page=10
Click to expand...
Click to collapse
Thanks a lot phoenix2241987, I got Ubuntu working following the above link!
Except I had to change the script a little bit to make it work on mine. I am attaching the script I modified if in case somebody needs it.
(Actually only this image works, other images of backtrack and laika do not work following the same method/script)
I was able to do a tightVNC session from PC and open up a full screen desktop. Firefox is not bad either, it is fast enough to browse text based sites.
Thanks a lot!
QNBT said:
Thank you! I'm sure that the recording fps is pretty low, so how smooth does it actually run on a ace?
Click to expand...
Click to collapse
Pretty smooth, I should say.. There is a very slight lag, but that shouldn't be a problem. Btw, I'm using the supercharger script. I guess it runs smooth because of that.
And just after running the shell script, when you get the "[email protected]:" prompt, type " vncserver -geometry 480x320" . And in android vnc viewer use port 5902. This will make sure that the resolution fits your screen.
Also use input method as "Touchpad", in vnc viewer settings.
And once you have opened the GUI using vnc viewer, you can close the terminal emulator to free up ram. I found that the GUI runs smoother if you do that. You can use the vnc viewer to bring up the GUI anytime you want, until the next reboot, since ubuntu runs in the background even after you exit from the terminal emulator.
The downside is that you cannot mount your sdcard in your pc, once you have booted up ubuntu. You will have to reboot to get it connected. I guess this is because the ubuntu image is mounted on one of the loop devices manually.
sandred said:
Thanks a lot phoenix2241987, I got Ubuntu working following the above link!
Except I had to change the script a little bit to make it work on mine. I am attaching the script I modified if in case somebody needs it.
(Actually only this image works, other images of backtrack and laika do not work following the same method/script)
I was able to do a tightVNC session from PC and open up a full screen desktop. Firefox is not bad either, it is fast enough to browse text based sites.
Thanks a lot!
Click to expand...
Click to collapse
I see you have modified the loop device #. I had to do that too, since all my loop devices [dm-0 to dm-7] were already mounted upon by some other applications installed on my phone. I had to uninstall one of them, to free up the loop device [in my case, dm-7], and change the script accordingly.
It would be cool if we could get some other OS running too.. Windows, for instance . But i guess that wouldn't be possible, due to the linux architecture of android. But who knows, some day, someone might change the bootloader, and get it to boot as the native OS, instead of running it as a virtual machine.
phoenix2241987 said:
I see you have modified the loop device #. I had to do that too, since all my loop devices [dm-0 to dm-7] were already mounted upon by some other applications installed on my phone. I had to uninstall one of them, to free up the loop device [in my case, dm-7], and change the script accordingly.
It would be cool if we could get some other OS running too.. Windows, for instance . But i guess that wouldn't be possible, due to the linux architecture of android. But who knows, some day, someone might change the bootloader, and get it to boot as the native OS, instead of running it as a virtual machine.
Click to expand...
Click to collapse
maybe windows phone but not windows at least until microsoft port it to RISC with windows 8.
Sent from my GT-S5830 using XDA App
phoenix2241987 said:
Pretty smooth, I should say.. There is a very slight lag, but that shouldn't be a problem. Btw, I'm using the supercharger script. I guess it runs smooth because of that.
And just after running the shell script, when you get the "[email protected]:" prompt, type " vncserver -geometry 480x320" . And in android vnc viewer use port 5902. This will make sure that the resolution fits your screen.
Also use input method as "Touchpad", in vnc viewer settings.
And once you have opened the GUI using vnc viewer, you can close the terminal emulator to free up ram. I found that the GUI runs smoother if you do that. You can use the vnc viewer to bring up the GUI anytime you want, until the next reboot, since ubuntu runs in the background even after you exit from the terminal emulator.
The downside is that you cannot mount your sdcard in your pc, once you have booted up ubuntu. You will have to reboot to get it connected. I guess this is because the ubuntu image is mounted on one of the loop devices manually.
Click to expand...
Click to collapse
That is a pain, it would actually be "better" if we would chose to boot up as ubunto at the startup, that would be awesome.
Thanks for the info!
sandred said:
Thanks a lot phoenix2241987, I got Ubuntu working following the above link!
Except I had to change the script a little bit to make it work on mine. I am attaching the script I modified if in case somebody needs it.
Click to expand...
Click to collapse
I got it working using sandred's modded chubuntu script in combination of this method:
http://forum.xda-developers.com/show...723493&page=10
The problems that it's pretty laggy when I use it. The quality of the color is really low as well.
QNBT said:
The problems that I cant chose the reslution, how do i do that? And it's pretty laggy when I use it. Should the color be good or should it be that low quality?
Click to expand...
Click to collapse
After running the shell script, when you get the "[email protected]:" prompt, type " vncserver -geometry 480x320". I used 480x320 because its the resolution of our galaxy ace, and it fits the screen nicely. You can use any other resolution you want, just put them in place of "480x320". And in android vnc viewer use port 5902.
Regarding the color depth, I use 24 bit, and it runs smoothly. If you have lag, use lower settings, although it will reduce the quality of display. You can change the color settings on the connect screen of the vnc viewer. There is a list-box named "color format".
phoenix2241987 said:
After running the shell script, when you get the "[email protected]:" prompt, type " vncserver -geometry 480x320". I used 480x320 because its the resolution of our galaxy ace, and it fits the screen nicely. You can use any other resolution you want, just put them in place of "480x320". And in android vnc viewer use port 5902.
Regarding the color depth, I use 24 bit, and it runs smoothly. If you have lag, use lower settings, although it will reduce the quality of display. You can change the color settings on the connect screen of the vnc viewer. There is a list-box named "color format".
Click to expand...
Click to collapse
I was so eager that i exited terminal before that text showed up, but for some reason ubuntu still starts up as a bigger resolution after typing those commands. Oh and 5902 doesnt work, only 5901.
OH, nvm! It works now, gonna reboot and start over again then check if it laggs!
For some reason i can only chose "No Pan, Trackball Mouse" Since we have no trackball im unable to move the cursor. Any solution to that?
edit: stupid me, had it on fit screen so..... works now thanks for all the help!
The Team Lambent Corrosion presents:
AndroidExplorer
The AndroidExplorer app is a program, which can help you to explore, copy, move and remove files in your device in the easites way.
FAQ
-Why?
-I know that there is QtADB, but I have two main reasons for finishing this project: 1. competition - it always helps to reach a better quality of app and users have more apps to choose from. 2. Improving programming skills.
-It looks similar to QtADB!
-I've never downloaded QtADB, I've seen it only on screenshots. What's more, I'm focusing on functionality, not appearance.
-When it will be done?
-I don't know yet, it depends on functions you want to see.
I'm opened for any ideas about functionality! I won't be available for a couple days in the nearest future, so please leave ideas here.. I'll read it later.
If you want to become a tester, please contact. All you need is Dropbox account.
Preview screenshot:
Uploaded with ImageShack.us
What is working?
-Exploring files in your PC and Android
-Drag and Drop
-Mounting as RW
-Two ways to copy/move file - copy immediately or add it to the task list
-Progress bar
-Shortcuts to the most useful folders
-Coloring the items that are present on task list
-Expanding a directory tree after refreshing
-Executting files via double-click
-Preview of the tasks list
-Executting tasks in separate thread (no freezes while working)
-Log file
-Many more
DOWNLOAD
AndroidExplorer Technical Preview - DOWNLOAD
Caution: the link contains always the newest version of the AndroidExplorer (including nightly, untested and unstable version)
History of progress: Preview...
Reserved as usual
The post may be useful for me
I think it is enough.
Hi, nice work so far! Looking forward for an release!!
Maybe it is a nice feature to make a "Mount System" button.
Any ideas I get later, I will post, or update this post
Stylooo said:
Hi, nice work so far! Looking forward for an release!!
Maybe it is a nice feature to make a "Mount System" button.
Any ideas I get later, I will post, or update this post
Click to expand...
Click to collapse
Hmm nice idea, I was thinking about it, the button will appear surely
good work, waiting for more can you put the program to open scripts without having to pass the script to the computer? I am asking this because great way for those who would do tests with different values in the scripts: P eg edit build.prop
Hmm, I was also thinking about it and think that it is good idea
Sent from my GT-I5800 using XDA Premium App
benzyniarz1 said:
Hmm, I was also thinking about it and think that it is good idea
Sent from my GT-I5800 using XDA Premium App
Click to expand...
Click to collapse
I am now following this...Really good project
dharamg3 said:
I am now following this...Really good project
Click to expand...
Click to collapse
I'm back, so I start working hardly
Hi, nice work.
Hello, I've decided to release alpha version... You can see how it's working. Check post no. 3 for link.
When app is not detecting your device - unplug and plug it again, wait about 1-2 min and then connect to the device.
Ok, testing It...First thing...looks really good....
Suggestions: the middle area doesnt show folders, i think you should show the folders also there...my suggestion...
cant open files from mobile...maybe you also know it..or is it not implemented yet ?
OK...i had waited for 2-3 mins, now it is taking too much time for opening apps folder...
all these are my review..i'll try out properly tomorrow and give a detail feedback
Really great work...
dharamg3 said:
Suggestions: the middle area doesnt show folders, i think you should show the folders also there...my suggestion...
Click to expand...
Click to collapse
Yeah, it's a good idea
dharamg3 said:
cant open files from mobile...maybe you also know it..or is it not implemented yet ?
Click to expand...
Click to collapse
Yep, not implemented yet. In the future there will be a possiblity of editing files without manual pushing files.
dharamg3 said:
OK...i had waited for 2-3 mins, now it is taking too much time for opening apps folder...
Click to expand...
Click to collapse
Mhm, I need to improve function that is parsing adb result of the files list.. It's hard thing - in the first version it took about 10 min . I'll try to figure out other algorythm.
dharamg3 said:
all these are my review..i'll try out properly tomorrow and give a detail feedback
Really great work... .
Click to expand...
Click to collapse
It would be very useful. Thank you very much
I've just found some bugs with DragAndDrop (like dropping itmes on specifed folder wasn't working). I've solved it, but I won't update link, I'll do it when some other features will be added.
@Dharam list of folders in the middle panel is implemented so folders are shown in the middle panel
@First link updated, nevermind.
subscribed..
Looks really nice and promising, I'm definitely following this one
But as dharam said, the waiting time is really to long for now, I hope you can fix this!
Hey, I've found bug... I don't know why, but it's not a fault of parsing... I've noticed that that it is a fault of adb.. I've no idea why the returning of the result of "adb shell ls -l /system/app" command takes so long time... Espiecially, that other paths works fine..
I need to figure out why.
This thread is for those having proximity sensor issues with Deck's CM10 Jelly Bean builds, but may work for proximity sensor issues in general.
If you simply want to fix proximity sensor issues in Deck's CM10, please download and flash the "signed_cm10_proxfix_update.zip" in recovery.
The below is for those that would like more information on the fix, and how to apply it manually:
After doing some research, prior HTC devices have had this issue, most notably, the HTC Desire HD. From what I have seen, it boils down to improper calibration settings of the proximity sensor. This has been addressed in many XDA, Desire HD, and foreign forums. The below is inspired by those forums, and a previous proximity sensor fix posted by xda member, ClipCarl. Thank you very much CC.
To easily test the reported distance of the sensor, one can download "Proximity Sensor Finder," free from the play store.
When properly working, a "9" will be reported when nothing is in front of the sensor, and a "0" when there is an object is detected; there are no range of values reported.
There is an easy way to apply calibration settings:
In adb shell or terminal emulator, execute:
Code:
su
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will immediately change the calibration of the sensor, but will not persist after reboot.
If this calibration setting makes your proximity sensor function properly, the settings can be made persistent after reboot.
You can either add a script to init.d, using the following instructions, or flash the attatched signed_cm10-proxfix-update.zip.
Create a file (named "99proximity_init" for example, without a file extension) containing the following code:
Code:
#!/system/bin/sh
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
Using adb or a file manager with /system mounted, copy the file to "/system/etc/init.d/"
Verify permissions are set appropriately:
Code:
chown root:shell /system/etc/init.d/99proximity_init
chmod 755 /system/etc/init.d/99proximity_init
Reboot to see if the sensor is working.
Please post your experiences and findings.
But what about those strange looking calibration values? 0x0a0f and 0x140b6050
Shell uses the prefix 0x for numeric constants represented in hex.
You can use a hex calculator, such as Windows Calculator set to programmer view, to play with the values. "0x" may need to be left out of for some calculators to work properly.
Use the terminal emulator or adb method to quickly test the effects of different parameters:
Code:
su
echo 0x<param1> 0x<param2> > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
The first parameter seems to be the lower thresh hold, but does not have a large impact by my testing. Increasingly larger values, +100 dec at a time, seem to give the sensor a better range to detect an object.
The second parameter seems to be the upper thresh hold, and has a large impact on the sensors calibration. Lowering this value further, by -100 dec steps, caused the sensor to not work properly. While raising the value decreased the "detection range" of the sensor.
What are your findings? Did you find something that works better?
Code:
#!/system/bin/sh
echo 0x0a0f 0x140b6050 > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
The above worked perfectly for me. Thanks!
Awesome. I'm glad it worked for you!
Do I need to enter those commands or can I just flash the zip file?
Sent from my EVO using xda premium
You can just flash the zip file.
The commands are there for a more hands on approach: to see how it works; testing; and tinkering.
Galaxy Nexus?
can this work on a galaxy nexus? I need to disable the sensor... :/
I'm not sure if the sensor is affected. This was originally made for an htc desire, but I found that it works on our evo lte.
It should affect your sensor distance if you have a "/sys/devices/virtual/optical_sensors/proximity/ps_kadc" file.
Though I'm not sure how to disable it, but the values can probably be played with make the sensor always report what you want.
Worked for me! Shouldnt this been in the original development sub forum with all the cm10 roms? I probably would've discovered this a long time ago thanks!
Sent from my EVO using xda premium
The two development forums confuse me. I picked this forum because I saw the majority of Cm10 *mods* posted here. Please feel free to ask a mod to move it if you feel it would benefit the community.
I'm very glad it worked for you! I was expecting the proximity sensor issue to be more prominent, mostly because it happened to me, but it really does seem to affect a low percentage.
<-- NitemareX
Glad you posted this up Firkin!
I keep my own copy of the file on my sdcard and on my dropbox account and flash after I flash a new nightly.
This fix works great with Paranoid Android JB rom! I was trying to use another fix linked in that thread, but it wasn't working. Now I tried this and it works perfectly!
Thanks
Using Decks 10-06 build the proximity sensor works as it should.
Sent from my EVO using xda app-developers app
FrikinImpossible, thank you so much! It works for my HTC One X, too!:good::good:
I've tried countless other methods including another fix, but nothing worked.
Keep up the good work!
t.o.m. said:
Using Decks 10-06 build the proximity sensor works as it should.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
After updating my rom to deck's 10/16 irc build, I did not need to flash the proximity fix. It seems deck has fixed proximity sensor issues!
Thank you for the tip tom!
omgomgomgomgomgomg it worked. I've been avoiding making calls because of this. Thank you so much!
This thread REALLY doesn't get anywhere near as much attention as it deserves. Bumping and thanking for being awesome
htc one x
FrikinImpossible said:
The two development forums confuse me. I picked this forum because I saw the majority of Cm10 *mods* posted here. Please feel free to ask a mod to move it if you feel it would benefit the community.
I'm very glad it worked for you! I was expecting the proximity sensor issue to be more prominent, mostly because it happened to me, but it really does seem to affect a low percentage.
Click to expand...
Click to collapse
great :good: work on htc one x running viperx rom,,thanks
The script via terminal works great on my HOX with ARHD 18.
I try to put the script in system/.. to be able to keep the script active after reboot, but that doesn't work... After every reboot i need to put the code in a terminal screen... Not really handy, but very thankfull i have a working P-sensor at least...
::steven:: said:
The script via terminal works great on my HOX with ARHD 18.
I try to put the script in system/.. to be able to keep the script active after reboot, but that doesn't work... After every reboot i need to put the code in a terminal screen... Not really handy, but very thankfull i have a working P-sensor at least...
Click to expand...
Click to collapse
To help me better understand your situation:
Did you try using the update.zip in the first post, or did you manually create the script, move it to the proper directory, then set permissions?
You may want to try the update.zip.
Does your Rom support init.d and have the "system/etc/init.d" directory already created for you?
Some developers create a Rom specific init.d directory.
Are you getting errors copying the script into the "system/etc/init.d" directory or setting the permissions? Sometimes, file explorers are finicky when messing with root and system partitions.
The proper permissions are really important!
Since VZW and Samsung Level 2 support didn't know the answer, here is how to enable the hidden menus on the dialer screen for the Verizon GS4. Previously, there was a 'master' code that enabled the hidden menus. Now it is a filesystem based check. Boo!
Due to editing /system/build.prop and /efs/carrier/HiddenMenu you MUST be rooted. Also, you must be on a stock TouchWiz-based ROM. This will not work on CM builds/etc. At a very minimum, hiddenmenu.apk must be present on your stock device for this to work, but possibly others, so beware of ROMs that remove 'bloat' APKs.
1) Add the following line* to /system/build.prop
Code:
sys.hiddenmenu.enable=1
Edit: I noticed that after I hosed build.prop, it was replaced when I loaded the default system image, so in fact, step 1 above is not necessary, at least for the Verizon variant. This means that once you do step #2 below, the changes made to /efs/carrier/HiddenMenu will persist after an Odin restore of the NoWipe Factory Image posted here. What this means is that root is only required to make the modification, and one could revert to stock afterwards with the hidden menus enabled.
2) Change the contents of /efs/carrier/HiddenMenu from OFF to ON
3) Reboot.
4) Try it out! Go to the phone dialer and enter *#06# (show MEID) as a test.
For more codes that worked on the S3 that (may) also work on the S4, see below:
http://androidforums.com/samsung-ga...unlocking-jelly-bean-service-modes-found.html
Having the hidden menus enabled is particularly useful for those who want to disable WiFi Power Saving mode -- I was having issues with an access point at work, but sadly disabling it didn't fix the problem. Otherwise, the hidden menus are useful to test your sensors/display/etc or just looking around in general. Enjoy!
For those that are NOT rooted, there is an alternative to get to SOME of these menus, but it is not a free app (currently $1.99). It's called "Sammy S Mode". Note that I am not affiliated with the developer, I just bought it to test if the menus were present before I dug deeper into finding out how to fully enable the hidden menus on my Verizon Galaxy S4. When I have time in the next day or so, I'll try to figure out how the app calls the menus, and update the post if I find a free solution for those that are not rooted.
---
* Note: I added the "sys.hiddenmenu.enable=1" line right after the "persist.cne.feature=0" one, but I don't think it matters where you add it. Just be careful editing this file. I managed to get my phone boot-looping, probably because I used notepad to edit the file and it added Windows CR/LFs to it, and had to use the NoWipe Factory Image posted here to restore my phone. The second time around I used Root Explorer's built in text editor and it worked fine.
In case anyone is curious how I figured this out, click here.
Mods: Thanks for moving this to the development section since it fits better here.
---
I wanted to compile a list of the ones that seem useful or new in general and working for me:
*#197328640# Service Mode
*#0228# BatteryStatus
*#0*# Screen/Sensor/Vibration/Touch/Speaker/LED/etc testing -- even gives out raw values for light sensor, barometer, etc in real time
*#2263 RF Band Selection
*#66336 MDM Randump Mode (defaults to OFF)
Thanks OP! Confirmed to be working on my Verizon S4. Followed your guide with the same placement in build.prop and using root explorer.
Thanks, worked great! :thumbup:
Sent from my SCH-I545 using xda app-developers app
I can't be rooted due to work MDM. I hope an alternative method is found. I hate the constant wifi notification.
dmichael said:
I can't be rooted due to work MDM. I hope an alternative method is found. I hate the constant wifi notification.
Click to expand...
Click to collapse
If you were talking about the menu on the S3 that opened "HiddenMenuWifiOffload" dialing *#6335623#, this does not work on my S4. In fact, it stopped working after a software update on the S3. There is a temporary solution that is lost on reboot. I tried it and it works for me. See link below:
http://androidcommunity.com/how-to-...i-notification-on-verizon-galaxy-s-4-20130527
For anyone that needs to get to a service menu without being rooted, here is the basic idea. You'll have to get a launcher or shortcut app that supports creating shortcuts to activities.
Code:
Intent localIntent1 = new Intent("android.intent.action.MAIN");
localIntent1.putExtra("keyString", "0011");
localIntent1.setClassName("com.sec.android.RilServiceModeApp", "com.sec.android.RilServiceModeApp.ServiceModeApp");
startActivity(localIntent1);
I'll expand later using a free app that supports doing that when I get it to work on my end. In the meantime, here's a very simple app that can serve as a template to place the values above:
http://viralpatel.net/blogs/android-install-uninstall-shortcut-example/
Edit 1: A free app can be used to create the shortcut. It is called Manual Intent Shortcuts.
Not working for me, did exactly what was posted. I even posted the line in the same place
Sent from Verizon Galaxy S4
tCizler said:
Not working for me, did exactly what was posted. I even posted the line in the same place
Sent from Verizon Galaxy S4
Click to expand...
Click to collapse
I should note that this only works if you're running a stock ROM. If you're running CM or some other non-TouchWiz ROM or missing hiddenmenu.apk this won't work. I have added this to the OP.
vacaloca said:
I should note that this only works if you're running a stock ROM. If you're running CM or some other non-TouchWiz ROM or missing hiddenmenu.apk this won't work. I have added this to the OP.
Click to expand...
Click to collapse
Yep, stock and rooted
Sent from Verizon Galaxy S4
thank you!
tCizler said:
Not working for me, did exactly what was posted. I even posted the line in the same place
Click to expand...
Click to collapse
tCizler said:
Yep, stock and rooted
Click to expand...
Click to collapse
The only thing I can think of is perhaps there is a space in the /efs/carrier/HiddenMenu file that is failing the code check. It is an exact match:
Code:
if (new File(this.HIDDENMENU_ENABLE_PATH).exists())
try
{
String str = read(this.HIDDENMENU_ENABLE_PATH);
if (str.equals("ON"))
return true;
You can also issue the command when USB debugging is set/connected to PC:
Code:
adb shell getprop sys.hiddenmenu.enable
or
Code:
getprop sys.hiddenmenu.enable
from a terminal emulator app on your phone to verify that the property is set correctly. Either command should return the value input -- 1 in this case.
I'll see if I make a recovery flashable update.zip to make it easier for everyone.
vacaloca said:
The only thing I can think of is perhaps there is a space in the /efs/carrier/HiddenMenu file that is failing the code check. It is an exact match:
Code:
if (new File(this.HIDDENMENU_ENABLE_PATH).exists())
try
{
String str = read(this.HIDDENMENU_ENABLE_PATH);
if (str.equals("ON"))
return true;
You can also issue the command when USB debugging is set/connected to PC:
Code:
adb shell getprop sys.hiddenmenu.enable
or
Code:
getprop sys.hiddenmenu.enable
from a terminal emulator app on your phone to verify that the property is set correctly. Either command should return the value input -- 1 in this case.
I'll see if I make a recovery flashable update.zip to make it easier for everyone.
Click to expand...
Click to collapse
I ran the "getprop sys.hiddenmenu.enable" line in terminal emulator and it came back with a value of "1".
Also, if it's any help, the *#06# code works. A few others work too. Just can't get the hidden menu *#26337# (*#codes#)
Sent from Verizon Galaxy S4
tCizler said:
I ran the "getprop sys.hiddenmenu.enable" line in terminal emulator and it came back with a value of "1".
Also, if it's any help, the *#06# code works. A few others work too. Just can't get the hidden menu *#26337# (*#codes#)
Sent from Verizon Galaxy S4
Click to expand...
Click to collapse
Oh, duh, haha. That's my fault. That was just an example of the format of the codes. There is no *#CODES# menu. :facepalm: I removed that from the OP. Sorry for the confusion, and thanks for testing/helping me clarify my post
The Service Mode Main Menu code is: *#197328640#.
vacaloca said:
Oh, duh, haha. That's my fault. That was just an example of the format of the codes. There is no *#CODES# menu. :facepalm: I removed that from the OP. Sorry for the confusion.
The Service Mode Main Menu code is: *#197328640#.
Click to expand...
Click to collapse
Hahahahaha! Wow now I feel like an ass! The facepalm should be for me
Sent from Verizon Galaxy S4
awesome!!!
vacaloca said:
The Service Mode Main Menu code is: *#197328640#.
Click to expand...
Click to collapse
Working for me.
Interesting choice of code sequence. 1973, 286 (intel), 40 (your age this year if born in 73)
Sent from my SGS4 using one opposable thumb.
ProfEngr said:
Working for me.
Interesting choice of code sequence. 1973, 286 (intel), 40 (your age this year if born in 73)
Sent from my SGS4 using one opposable thumb.
Click to expand...
Click to collapse
Ha, That sure it makes it easy to remember now
Can anyone else share their service mode setting (*#197328640#) under sim information, check nv, band pref? Mine says unexpected value.
Trying to figure out if my sim is borked and causing 4g slowness.
Sent from my SCH-I545 using xda premium
crookedview said:
Can anyone else share their service mode setting (*#197328640#) under sim information, check nv, band pref? Mine says unexpected value.
Trying to figure out if my sim is borked and causing 4g slowness.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Mine says the same and no 4g issues here either. If you have another phone handy that you can swap sims, that would be one way to test. *#2263 has band preference settings, but I haven't touched mine and don't plan to just in case, want to avoid resetting to stock and re-rooting/going back to recovery if the phone doesn't like some setting I picked there.
vacaloca said:
Mine says the same. If you have another phone handy that you can swap sims, that would be one way to test. *#2263 has band preference settings, but I haven't touched mine and don't plan to just in case, haha.
Click to expand...
Click to collapse
Mine says the same, and I have no 4g issues
Sent from Verizon Galaxy S4