Database Info

Where can I find a working WMODEM.EXE for the HTC Touch Pro(Raphael)

I'm on SPRINT'S HTC TOUCH PRO RAPHAEL
Ive been looking for the classic WMODEM.exe for a long time now.
I tried the Titan version, doesnt work
I tried a bunch of different versions from someone in the XDA Developer's Raphael Software Forum (above this one)
- didnt work.
I dont like ICS because its not that compatible with say, OpenBSD, FreeBSD, requires hacking to get working with Linux, and is basically microsoft proprietary bulls**t. I want the real deal PPP Wmodem. If nobody can provide a working one, and its deemed 'impossible' by the experts here, is there a way to hex edit or hack it so it works? Perhaps there is a registry key that prevents it from loading properly?
Please help me finally get WMODEM.EXE to load on the HTC Touch Pro! ICS sucks!!!

whats the problem you're experiencing when you're trying to load wmodem, exactly?

you double tap or excute the file right? and it does nothing.. you can sit there tapping over and over or pressing the enter button or anything and it just wont run
It's like compiling this into a C program:
main() {
exit(0);
}
--
on a hunch im going to try turning off touchflo3d, and executing the four different versions of wmodem i have, maybe one of them will load.. but i doubt it. I tried doing it this way with the Titan wmodem.exe and it still wouldn't load
ok i tried it, it does not work.
can anyone explain why WMODEM does not work for the TOUCH PRO?
has anyone gotten it to work?
maybe theres something embedded in wmodem.exe that causes it to exit() when executed in this operating environment?
can any developers or someone with debugging tools isolate what the cause is ? I have a feeling you could probably hex edit
or hack the wmodem.exe into working properly. Where would i post to request this?

it's actually running on my device, but when i tap the start connection button, the radio crashes, and the program says it could not open the com port.
i think it might be using obsolete api's or something, and that's why it doesn't load properly.
i tried to use it with a reg logger, to see if it searches for any special settings we could tweak, but i didn't spot anything special.
sry dude.

Where are the real hackers of the phone community? Just wondering? Should I try getting ahold of Lennysh on this issue? i hear hes pretty skilled.
the thing is, ICS drains the hell out of your battery. if you dont have over80% battery life on your touch pro, and you attempt to tether using ICS it will drain like crazy and your computer wont charge it.
as well as it not being a true ppp dialup connection, that too also sucks. meaning you have to use special hacks or tweaks for it to work under linux. thats bs

I will bring this back as I am also looking for a working WModem for the Raph.

afaik, wmodem provides support for gsm, you want dmrouter for cdma (which should come on all cdma roms)
the 5.08 AT&T test rom contains wmodem.exe.. as does the official AT&T ROM.. and it functions fine under both

YouMail Sleep issues

I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.

crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.

I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.

crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.

I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.

Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.

Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.

Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin

Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug

superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.

Bump
Anyone have some insight on this?

Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug

Any news ?

soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse

Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.

Safe Mode

Whenever i say that new smart phones aren't really phones, but actually entertainment devices that make calls, everyone nods and agrees. But what if there was a way to reverse that so they only made calls and pretty much nothing else? I'm looking to find a "safe mode", in which lots of services and drivers aren't even loaded.. ever. A good example of its use would be when i needed to drive 4 hours away for a funeral. I had no need for twitter and angry birds, I just needed to freely communicate with relatives. Another example is being stranded on the highway cause of dead car battery. Most Evo users would be clinging to dear battery life. Sometimes we want to be saturated with features, and other times we would be just fine with a classic green screen phone that only needs a weekly charge.
Would it be possible to dual boot into a very minimalist rom? If i knew my phone had a mode for emergencies, i wouldn't be searching every inch of the web for juice saving tips. Is this possible? If so, which rom would accomplish this? Thanks.
Sent from my HTC Evo 4G [rooted] Sprint 2.3.3(stock Sense, came preinstalled) Freedom-Aggressive kernel 0.8.5 hardware v.4

I have an option on my DroidX and it might work for you. I think it is generic for Android phones.
From the dialer do *#*#4636#*#* and go into the phone menu and you can change the network or disable the data connection altogether. On my phone it makes and receives phone calls and text messages but nothing else.
There is sometimes a delay when I make a change, a few seconds, so be patient.
I have a feeling you could do some damage in this menu so make a note of anything you change.
Since you are rooted, you could also install Droidwall or something similar and be very selective about what applications you allow to have a data connection.

You can theoretically create a custom CM7 or AOSP ROM with only the essentials- the phone.apk, contacts.apk, mms.apk, settings, and their corresponding supporting files/ framework.
Mind you, the screen would still be the biggest battery drain. And there comes a question of dual booting (which should be possible in my phone at least, with Magldr...).
Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.5)

Ford Motor Company SYNC/MyFordTouch/MyLincolnTouch Compatibility

Hello, Hopefully I can help with some frustrations regarding the various levels of SYNC systems and their apparent compatibility issues with Galaxy S phones. I will help anyone with this system to the best of my ability, and being a technician for Ford, i have a pretty good handle on these systems.
First off, I would encourage anyone with a question about this system to reference the Device Compatibility Matrix that is available at syncmyride.com, as is some basic troubleshooting information.
Always make sure that your CIP is up to the most current software level. Version numbers are different for each vehicle line(Fiesta, Focus, Fusion, Flex, Edge, MKx, MKt, MKs, MKz, F series, E series, Mustang etc).
There is a known compatibility issue with Samsung Galaxy S family phones that is fairly consistent, however not 100% of the time.
The common symptoms both from my engineering department, and from my own experience is a complete lockup/disconnect when updating the phone book(sync) or a blackscreen and complete system lockup(mytouch variants).
In some instances, mainly with the AT&T flavor, the phones will not connect via bluetooth for media/text messaging or sync services, however they will usually work as a phone. None of the Galaxy S series will accept phone book downloads, and that has been known to completely lock out the system, requiring a hard reset and occasionally a full reflash of the APIM(Accesory Protocol Interface Module, SYNC's brain box) to unlock.
I have found a dead consistent workaround for this that I dont imagine ford would be willing to back, but it is rock solid reliable and relatively simple, it involves flashing a rom that does NOT include touchwiz. I am not familiar enough with these phones to say exactly what, however every phone I have attempted to pair/use with touchwiz has failed, with touchwiz, or stock touchwiz gone, and again, I am not familiar enough to say for sure, the problem disappears.
I have first hand used Bonsai(epic 4g) and Beautiful SGS4G(Galaxy S 4g) as well as CM7(Vibrant) and had zero problems pairing or using any functions with the vehicle. Phone calls, streaming audio, Pandora, Text messaging, navigation etc all work smoothly with no hangups or hitches since romming the phones.
Again I hope this is helpful and if i can help you directly, feel free to contact me via pm or in this thread, however pm is going to be the best way to get in touch with me.
A few quick things that I have consistenly observed...Blackberrys are trouble. SYNC does NOT like BB's. Sync is also very sporadic with non smart-phones. Regular ol dial only phones do not seem to be very compatible, even though there are some listed on the compatibility matrix. Mytouch systems(8" touchscreen navigation with a black background and 4 way grid homescreen with top left-phone, top right-nav/services, bottom left-audio, bottom right climate control) are VERY tempermental. SYNC systems(smaller MFD that is non touch screen, or newer mustangs/raptors etc) are much more forgiving and much hardier from my experience.
Take care!

Great information, thanks.

Hmm -- app possible to remote control a late model ford, like driving the thing around with nobody in it?

lol its not quite that integrated. So far our capabilities in the shop are not that far above what you can do as an end user. I would imagine they will tie remote start, unlock/lock, windows etc in probably by end of the 2013 m/y.
We have managed to run diagnostics through sync as its tied into the HS/MS can networks, but beyond basic code pulling and system network integrity tests we haven't been able to pull reliable data out. Nowhere near solid enough to do realtime diagnostics or fault tracking.

[QUESTION] Is there any hardware testing and diagnostic tool?

Update 25-11-21: My friend told me that there are already some hardware-based physical tools that implement JTAG (IEEE 1149.1). I couldn't be able to say more about this because know nothing about electronics. (Those are very scarse to get where I live).
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based? Something resembling the POST (Power-On Self-Test) performed when a computer boots up, but be it done for testing and information gathering arbitrarily.
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!

ppdmartell said:
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based?
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
Click to expand...
Click to collapse
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.

Droidriven said:
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Click to expand...
Click to collapse
Honestly I didn't know radio was the proper term to refer that hardware component. Now I do and thanks to you.
However, in this case I just used a practical problem to communicate my idea. I should have expressed myself in a better way. The underlying issue was the diagnostic tool itself, and not the radio problem I used, maybe like some sort of low-level query-based tool to test and diagnose the components.
And I also should have done some research in google before posting here too. Maybe I got lucky. Just in case I could find any solution to my issue, I will gladly post it here.
Thanks for the reply.