Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?
I've got the icon, but no updates as yet...
mwako said:
Anyone else noticed with the diagnosis icon as a short cut if you have been in the menu i was asked earlier to update it in the marketplace ?
Nothing has changed as far as i can see in the diagnosis menu, nor lost any functionality or gained any, I'm not even thinking "this was an update, before any random comments" i'm just pondering and wondering if anyone else had this yet ?
Click to expand...
Click to collapse
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before
skeet94 said:
Had it through as well - didn't notice any new additions or removals from what's already there.
Update: When inputting the codes (i.e. *#0002*28345#) the phone now vibrates whereas it didn't before
Click to expand...
Click to collapse
Can't believe i didn't notice that , I remember now thinking it was an odd feel before when it didn't vibrate inputing the codes, after every other touch/input/exit on the device makes it vibrate, Seems they are doing something then. Lets see if anyone finds any new interesting menus inside ?
The "root menu" doesn't work any more it seems. I don't quite recall the command since I always check the Focus threads.
Updated Service Codes
We have extracted about 90% of the Service Codes from the latest Version I have downloaded. So far, not much in additional options. Maybe some changes in the old ones. Needs to be checked. There are again, some dead codes which are not referenced, so this is normal and not a wrong code from me.
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
AUDIOGAINCONTROL <-- What a shame as I still need to tweak the Volume on Level 1/30. Which should play more this Level.
(Yes I know, I have tweaked the Sound Tuning options)
The App runs a functions called "check cable" and this one calls "JIG_UART"
This function checks for two conditions. Unfortunately just some numbers, which cannot be explained because of a number code only..
This seems to be a Service Cable, as I was not able to run those codes, even when changed from USB to UART in the menu. So lets get an UART cable
If the UART Service Cable is not needed, maybe someone else finds out...
There are also two commands which check a registry value from the phone, and start not for me:
FTAMAIN
VIEWHISTORYNW
So far I have seen only the following new ones:
SerialNumber --> Starts but does not show anything
TFlashUnPairing --> Starts but have not tested it. I don't need to know everything
Some Menu Item was deleted, forgot which ones...
I have attached the Commands and the Hash table. It does not make sense to transfer every hash code, because most of them are already resolved.
I explain how to resolve it, in case you want to try one:
As an example I have chosen the SMDINFO (Open the TXT file)command, because it has only 5 digits:
The first Number: (4) Tells you the length of the code. Because we use 0 too, this code has 5 positions:
Next to the number in the brackets, is the number you put into the DiagApp Tool, starting from the last. Because SMDINFO shows, you only two of them in the same line, you just continue downwards. You can also use the search option:
This results in:
*#03#
Again you look for the numbers next to the numbers in the brackets. So you need to find the numbers for:
(4) (3) (2) (1) (0)
(4) (3) are easy, on the same line... the looks for the next (2), which can be found under: DisableSellOutSMS If you are unsure, use search...
Its easier as it sounds...
If I find anything new and useful, I will let you know...
Let me know any interesting file to disassemble. The is always more then the eye can catch.. At least with a debug guru in the team...
MC
mchabr said:
The most interesting codes run a check before they start. If the conditions do not apply, the diag function will not start.
This would be
TESTMODE <--Root
Click to expand...
Click to collapse
I guess the well known workaound, will result in the same root access.
*#1111# continue to press any number, until the long number at the top gets a minus symbol. Then just press back, until you jump into the main menu.
Hey guys, I wanted to start a thread where all of the few developers that the DVP has can come together and develop for the DVP in a joint-effort, starting with understanding the EM app.
There have been recent changes to the EM app with the new firmware and Mango, so I was hoping to create neutral ground where we can lay out all of the uses of the EM app and how to exploit them for the greater good.
So first of all the basics:
To get the EM app, dial ##634#
There are 3 basic options when you get to the EM App:
Phone Information
System Information
MMS Settings
There isn't much to be done with the Phone and System information, as they are there for pure informational purposes, but something can be done with the MMS Settings
MMS Settings: Here you can edit your MMS settings, including the APN, username, password, Authentication Type, (For Data) and then your actual MMS Settings such as Name, APN, MMSC, MMS Proxy, MMS Port, Username, Password, and Auth Type
Not much developing can be done with these 3 options, but if you tap the blank space below the options and then use the physical keyboard to type "qwertyuiop" without quotes, you get additional options:
RD Test (Password: *#6336#)
MMI Test
MMI Test (Chinese)
FCQ Test
Protocol
Service Center
OOB (Password)
The RD Test brings up a slew of options:
Audio Loop -tests the audio (earphones required)
Backlight- tests the backlight (turn on and off by touching)
BT (Bluetooth) - Displays BT address, the test mode, TX Power Test, and BQB Certification.
Camera- tests camera by taking a picture
Compass-not sure how this works...
FM Radio- tests the radio (needs earphones plugged in)
Gap- measure 4 blocks and enter the measurements
GPS- Turn off location services and test the GPS
Isolated Storage Speed- test the speed of storage
Keypad- push all of the buttons to get back to main menu
LCD (AMOLED)- Test the LCD
LED- Turn on the screen, keypad, and the camera flashlight
Power Cycle- Test one power cycle (I don't know what it means?"
Power Management- Displays statistics of the battery
Recorder- Records audio to test the microphone
RF Power Forward- Displays the bands of your phone, and WCDMA information
Touch Pad- Brings up a menu to test the touch screen
Sensors-calibrate the Light Sensor, Proximity Sensor, and the Accelerometer
SD Card- the status of your SD card, the size, and the OS disk size
Sim Card-Says if your sim card is inserted
Sim Lock - Displays the Lock Code for your sim card...
Slider- tells you that your slider is open or closed
Vibrator-vibrates your phone
Video Music- tests music and video
Wifi-Brings up the Wifi menu, displays MAC address (other options unknown)
About EM- doesn't work(?) Says the page isn't ready yet.
Man Machine Interface Test (MMI) runs a series of tests on your phone, it runs through all the tests in the RD test.
The Function Quality Check Test (FQC Test): Its in Chinese
Protocol requires a password
Service Center, which allows tethering
OOB, requires password.
So, my goal is to have a mutual discussion ground in which we can exploit this EM app to its fullest, and maybe unlock some hidden features of the phone!
This won't help much, but is it normal to have the MMS Settings app show up in the app list? It's been there since I got it a few days ago, and I haven't even dialed ##634#. Also, in the app list, it's titled "Connection Settings", but it identifies itself as MMS Settings in the app itself and has all of the options you mentioned.
ElijahHouck said:
This won't help much, but is it normal to have the MMS Settings app show up in the app list? It's been there since I got it a few days ago, and I haven't even dialed ##634#. Also, in the app list, it's titled "Connection Settings", but it identifies itself as MMS Settings in the app itself and has all of the options you mentioned.
Click to expand...
Click to collapse
Yes, with the new FW 212, its bundled as a seperate App with new purchases.
I dont know if this has been found by anyone yet, but when you press 'protocol' and type in *#6336# it takes you to another menu with three options,
active feature- seems to contain all the options to control the radio frequencies such as wcdma, gsm, bands, save efs log, and reset all..
when i clicked on 'fixed in bands' it seems to give you an option to check which frequencies you would like to use, theres four boxes with four of the regular gsm frequencies, 850,900,1800,1900, but five different wcdma options, I IMT 2000, II PCS 1900, then IV 1700, V 850, and VIII 900..
TMO-stands for tmobile, brings up a longer list of other controls and status screens for the radio and other things that deal with tmobile network..
RILDRV Log Capture- not sure what this one is about but gives you three capture options- capture at function level, capture at info level, and capture at error level, then two buttons that say Capture and unCapture...
curious stuff.. I havent played around with it much yet other than that..
16gb NoDo with 212 firmware
Service Center, which allows tethering
Click to expand...
Click to collapse
Which isn't working in Mango Beta, hopefully works in RTM?
Monkyyy said:
Which isn't working in Mango Beta, hopefully works in RTM?
Click to expand...
Click to collapse
Some people have been reporting that it works with Beta 2, and the RTM(?)
Also, with regards to this thread, I know that the DVP has no developer base behind it like the other devices, so I thought that looking into Dell's own app for its phones would help, and as a joint effort we might find a way into the DVP itself.
Also, I think some notable DVP-goers (such as notebookgrail and domineus) have already tried this, but what if ths thread could help us, or even work in our favor?
the major difficulty in the em.xap is tantamount
primarily the registry editor does work; but it only creates new keys - no modification of keys. Secondly, the interop capabilities has been rendered useless post nodo. So we have a unique situation as far as hacking the dvp
gauravr88 said:
I dont know if this has been found by anyone yet, but when you press 'protocol' and type in *#6336# it takes you to another menu with three options,
active feature- seems to contain all the options to control the radio frequencies such as wcdma, gsm, bands, save efs log, and reset all..
when i clicked on 'fixed in bands' it seems to give you an option to check which frequencies you would like to use, theres four boxes with four of the regular gsm frequencies, 850,900,1800,1900, but five different wcdma options, I IMT 2000, II PCS 1900, then IV 1700, V 850, and VIII 900..
TMO-stands for tmobile, brings up a longer list of other controls and status screens for the radio and other things that deal with tmobile network..
RILDRV Log Capture- not sure what this one is about but gives you three capture options- capture at function level, capture at info level, and capture at error level, then two buttons that say Capture and unCapture...
curious stuff.. I havent played around with it much yet other than that..
16gb NoDo with 212 firmware
Click to expand...
Click to collapse
Its been there since the DVP started.
The bands stuff is basically writing a flag to a file in the Isolated Storage of the EM App. Once you close the app, its state is gone. It doesn't really change bands in the Hardware as we thought to be.
The TMO options is useful if you are into AT Command. I had played with it a lot..But scary stuff. Its basically taking to the Radio Modem.
RILDRV Log Capture - haven't played with it. But looking at the code doesn't give much info.
Curious, why is there a dedicated section to T-Mobile when all of the phones aren't being used with T-Mobile?
Thunder_47 said:
Curious, why is there a dedicated section to T-Mobile when all of the phones aren't being used with T-Mobile?
Click to expand...
Click to collapse
Originally DVP was a TMO exclusive. May be they just left it there in the FW. I don't have a ATT DVP. Do they have the same TMO menu?
Is there anyway that we can use the EM app to change certain things such as IMEI (illegal) or find a way to bypass the upsell page when using Web2Go or T-Zones?
Basically, I want to use DVP with my grandfathered plan.
I don't believe that dell gave tmobile and att every single DVP IMEI out. There must be a low level security on each device that halts you from using web2go/tzones for working. I am trying to find that solution.
I am on tmobile USA with a grandfatherd web2go plan.
I originally ordered a t-mo DVP and found out it wont work on web2go/tzones.
I then bought the unlocked ATT DVP and unfortunately, it STILL doesnt work on web2go/tzones- knowing that I will only have edge speeds. I returned that device, BTW.
Any tips guys?
One thing I noticed: If the DVP chokes on loading up a webpage (via Low tower signal, etc), it will actually bring up the real webpage- somehow bypassing the upsell page.
But if you have full bars, the signal catches on, and you are redirected/forced to pay for an internet plan before you can use the grandfathered plan on the DVP.
I don't think this is possible, the IMEI is hardlined into your phone, changing it (if even possible) would probably cause your phone to be unrecognized by the T Mobile network.
The sad truth with this phone is that there will never be developer support for it like there is for HTC or other devices. Without a way to write to the registry or fix the broken interop service there is simply no way. This is something that the engineers (or their outsourced, contracted employees) at Dell would need to fix. And that won't happen because they won't waste time on an old phone, they'll just launch a new one.
Arcarsenal said:
The sad truth with this phone is that there will never be developer support for it like there is for HTC or other devices. Without a way to write to the registry or fix the broken interop service there is simply no way. This is something that the engineers (or their outsourced, contracted employees) at Dell would need to fix. And that won't happen because they won't waste time on an old phone, they'll just launch a new one.
Click to expand...
Click to collapse
No need to be pessimistic now, I'm sure if we all came together and explored all of the options (starting this this native app) we could eventually get to the promised land
Thunder_47 said:
No need to be pessimistic now, I'm sure if we all came together and explored all of the options (starting this this native app) we could eventually get to the promised land
Click to expand...
Click to collapse
I agree. Lets at lest keep open dialogue. You never know who may get there hands on a DVP...
haha, there's a difference between pessimism and reality. Take a look at the code of the unpacked EM.xap. Everything you'd need for your "native app" would be contained in there, including a way to modify the registry since EM and OurCOM.dll is the software layer that interfaces with the hardware at a limited level. There are people much more versed in the technical details of Windows Phone and the actual code of the EM app that can explain the uphill battle you face much better than I can.
But, any real progress needs to come from Dell themselves first, not the community. Their EM app is literally not completed. And, we know how Dell has responded thus far.
Not trying to be rude or anything, that's just how I see things and the situation with Dell.
edit: in an effort to keep people motivated here is a nice write up (part 1 of 3) about what is possible on a Venue Pro with Nodo: http://dennisdel.com/?p=840
keep in mind that things are now different if you're running Mango.
The line between realism and pessimism is a fine one. However, much in the way that Dell works, little progress fan be made on our side of the equation. But, that doesn't stop us from improving our phones using the tools that we have. Time spent whining about the things we can't do while the HTC guys are having super fun is time wasted.
Sent from my Venue Pro using XDA Windows Phone 7 App
Arcarsenal said:
edit: in an effort to keep people motivated here is a nice write up (part 1 of 3) about what is possible on a Venue Pro with Nodo: http://dennisdel.com/?p=840
keep in mind that things are now different if you're running Mango.
Click to expand...
Click to collapse
That's the same code as in the EM app. OurCOM.dll is nothing more than a gateway to the actual Driver DLL's. I did do some decompiling (PE Explorer and IDA tools) of the OurCOM.dll a while back and found that no code actually exists in it. It just invokes the actual Driver dll's which inturn communicates with dll's MS provides with the core OS. Dell themselves, didn't fully bake the EM app. Halfway along they left the development due to MS advising them not to expose the core features (like regedit,etc). I am not that familiar with C, but if someone has strong knowledge, we can try to work out some movement.
Here is some food for thought info to get someone going deep.
There is a file called QEMDriver.dll which is the actual driver file that does the majority of the gateway work in the EM app. Upon inspecting that file in IDA, i found that the core function resides in Coredll.dll (a MS OS file) and ril.dll (MS OS file for modem, calls, etc).
What i also found was(most people knew) if we crack open a way to provision the phone with the proper rights, anything is possible. MS even has article detailing how to provision certain rights,etc OTA. I tried all and failed.
If anyone wants, i can post the files that i referred and links to the provisioning.
I have seen all over the windows phone development forum that some HTC drivers work with the DVP, as far as tethering goes, can we extend this to other functions?
I know with the Samsung Galaxy Note 3, you have a regional carrier menu which can be accessed using a key sequence on the dial pad. When accessed, a list will be displayed showing all the carriers which the phone supports using their 3 digit abbreviation. When you select a specific carrier and click reboot, the device will do a factory reset using the specific carrier settings you selected. I know the S4 will have the same regional menu but I'm curious as to whether or not I can access this through a dial pad sequence and if so, what the sequence would be.
Thanks in advance for any help which could be provided!
RESOLVED
Unlike the Note 3, the CSC (Consumer Software Customization) otherwise known as the Regional Carrier menu is a hidden menu within the Samsung Device model lineup. This menu will show a listing of scripts in the phone, depicted by a 3 letter code and specific to the carriers which can be preloaded on your device. If your device is unlocked and you wish to use it with one of the specified carriers, you can insert your carrier specific SIM, access this menu and "INSTALL" the specific configured script for that carrier. The question is always asked... "What is the benefit?".
Answer: With smartphones, they are mini computers and not just your typical "telephone". As such, you have multiple settings which vary among carriers. As such, by configuring your device to be carrier specific, it will modify specific settings which are proprietary to that specific carrier. As an example, it will modify the APN details, update your network settings to reflect access to specific modems such as 3G, 4G, HSPA+ and LTE and will also brand the device with specific apps which have been preloaded and configured for that specific carrier such as a "My Account" app. These are just some of the things to name a few which implementation of the proper CSC settings will provide.
Samsung realized that tech savvy people have figured out how to access these menus and this has resulted in fixes implemented in OTA updates to hinder people from being able to do this. As such, you cannot use the typical dialpad entry to gain access to the menu but do have the ability through ROOTING your device. Unfortunately, a ROOT will most likely "void" your warranty so it's at the discretion of the "end user" whether or not the warranty is important.
Thank you to all who assisted and happy trails!
cellrama said:
I know with the Samsung Galaxy Note 3, you have a regional carrier menu which can be accessed using a key sequence on the dial pad. When accessed, a list will be displayed showing all the carriers which the phone supports using their 3 digit abbreviation. When you select a specific carrier and click reboot, the device will do a factory reset using the specific carrier settings you selected. I know the S4 will have the same regional menu but I'm curious as to whether or not I can access this through a dial pad sequence and if so, what the sequence would be.
Thanks in advance for any help which could be provided!
Click to expand...
Click to collapse
Can you please stop spamming yourself lol.
LOL... Well there is an option to Edit/Delete and since I can not "delete" my post, I mine as well indicate it has been resolved and provide the underlying solution.
theunderling said:
Can you please stop spamming yourself lol.
Click to expand...
Click to collapse
What has been resolved?.I understand what you were after as in your 1st post; but your 2nd post indicates you can get the dialler menu if you are rooted.
Since I am rooted......care to tell me the code for me to test then?.
It doesnt matter if you cant, as when I insert a sim, a box normally opens up for me to select which network I want, which then triggers inbuilt settings (apn etc)......and the phone works.
Many people do not wish to "root" their device thus "voiding" the warranty. As an alternative, they can unlock their device and dependent on their OS, they can access the "CSC Menu" through *#272*[IMEI]# Should their "new" carrier be in the default list of supporting scripts installed on the phone by the manufacturer, they can install the script which will "brand" the phone to the new carrier/SIM complete with all the required settings for that carrier. Doing this will BRAND their phone to the new carrier settings without having to root and install a carrier specific ROM etc...
Is this beneficial for you specifically? Absolutely not as you have rooted your device but many on here looking for information find threads which talk partially about something and then you see a posts claiming it's been resolved with no further detail. If I solve something on my own and feel it would benefit some, not all, I may as well post my findings so if someone encounters the same problem, they can access a thread which provides a solution instead of simply saying "FIXED".
You said it best by "It doesnt matter if you cant, as when I insert a sim"... Yes, when you insert a SIM on your rooted device you have access to everything you need. That does not help someone whom does not wish to "root" their device. Maybe I'm reading into matters too much but you seem upset about my posts That being said, ignore them. I'm not bolstering my post count but if I resolve something, I may as well post it since I cannot officially delete my thread but only "edit" it. By posting it's resolved and providing details as to how, this will alleviate someone wasting their time by providing an answer while helping those who may possibly encounter the same situation.
Cheers!
theunderling said:
What has been resolved?.I understand what you were after as in your 1st post; but your 2nd post indicates you can get the dialler menu if you are rooted.
Since I am rooted......care to tell me the code for me to test then?.
It doesnt matter if you cant, as when I insert a sim, a box normally opens up for me to select which network I want, which then triggers inbuilt settings (apn etc)......and the phone works.
Click to expand...
Click to collapse
No.You state in post 2 that you can acess the menu if I am rooted.....so explain how its done since I am rooted.
Also the box that opens up happens when a sim is inserted on all the unrooted samsung phones Ive had, which then triggers carrier settings etc.
So to recap, you did not answer how to get into that menu, and I cant even see how anyone would need to anyhow.
That is all
You are reading way too much into the post and it's asinine. I asked a question, received some feedback via PM and resolved my issue. As quoted from my "Post #2": "As such, you cannot use the typical dialpad entry to gain access to the menu but do have the ability through ROOTING your device." -- I am simply indicating the dial pad entry cannot be used unless you have original firmware which has not been updated. If updated, you can ROOT which allows you to brand your device using alternative methods. Reading way too much into everything...
ROOTING = You can customize your device using many methods and as per your post: "I cant even see how anyone would need to anyhow" is correct for those who are rooting.
*#272*[IMEI]# = You can customize your device to a specific carrier should that carrier be listed in the pre-installed scripts. Your device must be unlocked but this method will not void your warranty by installing a carrier ROM already pre-configured on the device.
I may also add that you're correct! If unlocking a device and not rooting, once you input a non-carrier SIM, you will be prompted for a code but the settings do not always change. Sometimes APN settings are incorrect and there is manual editing required. The suggestion I made regarding the CSC menu will allow you to configure the device to the new carrier ROM without rooting. This will also "customize" the device to that specific carrier so unlike simply features such as APN etc... being changed, you will also have pre-defined apps installed specific to that carrier such as "My Account" and other specific apps you would not obtain by simply unlocking.
I'll make it clear that you ARE RIGHT! Let's leave it at that but for those who do not read so deep into my posts, I find many of them have been helpful as have yours otherwise we would not have received the thanks we have.
Have a great one!
theunderling said:
No.You state in post 2 that you can acess the menu if I am rooted.....so explain how its done since I am rooted.
Also the box that opens up happens when a sim is inserted on all the unrooted samsung phones Ive had, which then triggers carrier settings etc.
So to recap, you did not answer how to get into that menu, and I cant even see how anyone would need to anyhow.
That is all
Click to expand...
Click to collapse