Issues with my Mogul - Mogul, XV6800 General

So I've noticed a couple of issues recently.
Just today, mine started freezing in text messaging when typing a reply. Says I am at like 60% of ram in use, but still crawls like a snail.
I've also noticed an issue with s2p. When sending a picture, it send the same one no matter what one I pick to send.
Any ideas on either of those? Also, what percent of memory does yours usually sit at with nothing running?
Additionally, my wi-fi doesn't work since I installed wm6.1 update. It always says the network is unavailable when I try to connect.
I am running sprints wm6.1 with picture messaging, and htc home plugin, with samsung omnia 3d drivers, oxios close apps

Related

Wizard sometimes sends 2 same text messages

I noticed that Wizard has a very poor GSM signal reception. Compaired to SonyEricsson P910i, which was extremely reliable when it comes to signal reception.
One of the disadventages of bad reception is faster battery drainage, but it doesn't bother me that much.
Sometimes it happens that Wizard tries sending SMS (text message) several times, until it succeeds in that action..unfortunatelly, it seems that the sending was successful every time, so I end up with boosted phone bill, and my recipient with several same messages.
Does this happen to you? It starts driving me crazy, although I have a Wiz for only a month now.
Maybe you are using Pocket Plus?
In that case you have to add tmail.exe (\Windows) to the exception list. You can find the list in the Settings of Pocket Plus.
Yes I do have it installed. But if you're reffering to that problem saying it's because of having Pocket Plus installed, I must say that it did happen even before I installed it 2-3 days ago.
I just opened Pocket Plus' Settings but it seems I cannot find Exception list (though I think I've seen it once I browsed through the option first time I installed it). Could you be more precise?
And, yes, what exactly one gets after adding tmail.exe to the exception list?
My wizard has a v good gsm recetion - you may find the reception better with the original o2 rom rather than the t-mobile one you are using. Or your provider signal is poor!
There is a known glitch so it sends two messages if you close down tmail before the message is sent.
When you said "close" I figured out where the exception list could be So I added tmail.exe to the list..but I kinda doubt it'll solve the problem. If it does..hooray!
I doubt cos I didn't see that Close button actually works like a real close (even with Pocket Plus). Just in case, I've just switched tap and hold functions on close button. Tap will minimise it and hold will close it. And just saw that my messaging app stays open even if I hold stylus over X button

Poor Performance?

Well Ive had my mogul for a while now and everything has been great. Yesterday however things started to change.
It slows way down when texting, often freezing in the text screen. If I restart the phone it solves the problem temporarily, but it pops back up shortly thereafter. Any ideas why? Im running the HTC home customizer and thats it.
Thanks.
*edit* Everything seems to be running incredibly slow now. Even if I restart the phone shortly thereafter the sluggish performance rears its ugly head.
im experience the same, i have found no solution
did you try SKTools FreeUp RAM or Oxios yet?
My sister had the same problem she fixed it (well i fixed it) by deleting all of the text messages she had (over 2,000) the phone isnt ment to hold over 1000 i think. Try to free up memory by deleting some text messages.
Text messages are a HUGE slow down culprit but there's another big culprit too - are you running HTC Home and do you have the input settings set to NOT do predictive text? Ie., turning off the 4 word suggestion as you're typing. Those two things seem to slow my Mogul to a CRAWL!

having lots of probs on stock rom

I got my hero two months ago. She was brand new in box but I bought from an unofficial third party off ebay. I was told that was some sort of developer phone and came with a month of free service.
Instead I flashed her to cricket wireless. Besides the crappy service from cricket the phone worked great! It is the best phone i ever had.
Now two months later it has been very buggy. Standard apps that come on the phone are force closing. I have been having a hard time running some third party apps as well.
Voice recorder force closes on startup. It refuses to record video. pictures work. Sometimes i stop getting texts messages but i dont know if that's cricket or the phone.
Facebook will work for a couple days then it will force close and disapear from the apps pulldown and remove it's icon from my homescreen. Apps disapear from my homescreen.
The battery life has been declining at a steady pace. As of now it feels like I am battleing to keep it charged even though i start with a fresh charge every morning.
I can't get the handcent talk to text to work. Nor can i get the text to voice to work. google voice search doesnt work either.
I recently been using sip agent to make wifi calls because service is so bad that i can't make calls inside my house. (not the phones fault) this could contribute to my dead battery but i try to close sipagent unless I plan on using it.
other apps that used to work fine are force closing but not consistantly.
whatya think is going on? I also dropped my phone twice (with out a cover) but no visual damage was done.
I would recommend reflashing the stock firmware, but you need to find out where exactly the phone came from to find out which firmware to flash.
How many apps do you have installed? If it's 70 or more that's probably the problem and is a known issue w/ the Hero. Some get upwards of 100 apps before random F/Cs happen, other around 70, for me it's around 85. Uninstall some apps and reboot.
Also the HTC location service is buggy and and lags the phone the longer it runs. It's good to reboot the phone daily or move to a custom ROM that has dumped the service.
And finally be careful if you're running a task killer. Some of them kill the process that lets you receive text messages.

tmous hd2 lockups, have to reset 5 times a day

i am getting some lockups on my hd2.
i have had it for 4 days now and it seems to be getting progressively worse.
it seems to have something to do with texting.
when i text there is a long (20 seconds or more) pause before you can enter text.
sometimes after sending texts it wont go back to the home screen.. the phone then will lockup with only the start menu showing..
at this time nothing works.. i have to reset the phone via the HD2SoftReset button i installed from the HD2Tweak program.
any ideas on what is going on?
I had the same problem as you before. I fixed it by deleting my txt from time to time. So you don't store too many of them on your phone.
thats crazy, i never deleted the messages from my tmo 3g dash and it never crashed
hope they fix it soon with fw update
aarons6 said:
thats crazy, i never deleted the messages from my tmo 3g dash and it never crashed
hope they fix it soon with fw update
Click to expand...
Click to collapse
yea, it's weird. somehow it takes awhile for hd2 to load previous text messages.
its entirely the fault of the sense messaging app.
keep your messages to around 100 in and out and you will be fine,
or disable sense messaging and use standard 6.5 threaded and you can keep them.
not a great fix but still a fix
Ditto! I'm having the same issue - locking up and freezing... Augh!
I do not have any text messages on the phone and I get dropped data connections all day. If I power cycle it does come back. It also seems to have an issue with updating my "Current Location" on the home screen. All of the other locations weather update but the phone just can't seem to figure out where it is.
Any ideas on this one?
thanks
i was having those same data issues i just called t mo and they provisioned it properly. have you done that yet/

Change to froyo

Forgive me if I have posted this in the wrong place but this is all very new to me. I recently flashed my phone to 2.2 and some strange things have been happening. I have two examples I would like to share which both have the same outcome. Trying to import a book into aldiko from the sd card ends in the program being force closed. The phone vibrates once, pauses a few seconds, vibrates three times and then the error message comes up. The second example is pretty much the exact same except it happens when trying to launch a game with psx4droid. One vibration, pause, three vibrations, program closes. Both of these programs worked without issue prior to the change in OS. Could anyone suggest any reasons and solutions to the situation? I was on the last chapter of an amazing book. Thanks in advance,
Gino.
Sent from my GT-I9000 using XDA App
yep doing it to me too, not very often, it was happening a lot at first, but i did a factory reset and it cleared up a lot of them.
I dis one factory reset with no result.should I just keep trying til it goes away?
Sent from my GT-I9000 using XDA App
This has been happening to myself and my partner's Samsung Galaxy S since we upgraded to the official UK Froyo update. Just about any app can crash with the vibrate, pause, 3 vibrates. While mine is rooted with z4root and I have a ton of stuff on it, my partner's is not rooted and only runs some very basic apps.
Did you update through Kies? What version of FroYo are you on?
Try to uninstall the apps, download them and reinstall. Also, using the Kies Registry Patcher, see if Kies will flash the stock 2.2 ROM. All stock ROMs can be found here.
Follow these steps
Ian
Updated with Kies to Froyo (JPO) a month or two ago. I notice JPY is now available through Kies so currently trying that.
I had tried installing/uninstalling apps previously, but according to logcat just about any process can crash with this vibrate pulse, pause, three pulses issue. I've had System, acore, TWL, Market, Gmail, the browser (stock and Dolphin HD), etc. These aren't the normal force closes either. The logs show them as SIGBUS or SIGILL (no K, not SIGKILL) errors, which normally mean a hardware fault, but, given so many people are having the problem after updating to FroYo, and given it's happening on two phones I'm in possession of personally, I'm sure it's related to the FroYo update.
Well, since updating to JPY 6 hours ago I've had zero crashes and the phone seems far more responsive and faster. My quadrant score has increased by around 20%.
There were a number of things that would nearly always crash the phone in the way I described previously - such as updating more than 2 or 3 apps at the same time, rapidly scrolling around certain websites, etc. I updated 10 apps simultaneously, I've gone to all of the websites that would crash the browser, and tried a whole load of other things that were "high risk" on JPO. Zero crashes.
If the phone does crash in the next week or two I will come back and mention it here. But so far, it looks great.
We took a Froyo update and the phone is now no longer able to accept incoming calls or texts when ANY other web-using application is running, e.g. you open the Facebook app and leave it running in the background so you can get notifications from FB and you can't receive any calls or texts until you have shut down FB. You open a browser, you can't receive any calls or texts until you shut down the browser!
Not even sure how to report this as a problem because all the websites we are directed to seem to be FAQs for people who have never seen a phone before. Any recommendations so we can return to the use of phone calls? For the next week or so we have only pay as you surf mobile broadband and no Kies, which resticts things somewhat, but is there anything we can do right away? What about when we get back to a full net connection and Kies? Where do we even report this error, as everyone seems to be having a different type of error with this update, and we'd like to make sure they know about this one, a smartphone that doesn't receive phone calls unless you turn everything else off is a little pointless!
Incidentally, site designers, any chance you could put some text descriptions for your button images? I loaded this site with no pictures and it doesn't come up saying where the reply buttons and such are located like it does when you have alternative text. If people use screenreaders (e.g. blind people like many of my friends) they cannot navigate this site without these. Cheers!
I've tested this and it works fine for me.
Are you sure this isn't just the limitation that's present on ALL GSM networks whereby if you're on 2G (i.e. not WiFi or 3G) then you can only have either a data connection OR a voice call? 2G only supports one type of connection at a time. If you're using data and want to make/receive calls you must use either 3G or WiFi.
The phone is definitely showing 3G as the connection type, and we have two phones on the same network in the same room and only the Froyo one has this problem, which it has never had before. Even in areas where the connection type is showing as HSDPA (never get those letters in the correct order!) it is impossible to get any kind of incoming call when a web application is open. It also applies to applications which are open but not currently using data. Not sure if they use data in a background kind of a way, but if you open a browser and load e.g. Google and after it is fully loaded attempt to call that phone you still get the answerphone. You can only get a phone call if all apps which might potentially use a web connection are shut down. Renders every aspect of the phone useless because you have to shut off Facebook, all browsers, email, weather updates, news feeds... basically everything, just in case you might potentially receive a telephone call.
We had 2 T-mobile phones on Windows Mobile in this same room and neither of those has this problem either. The phones are 2x HTC TYTNII (Tmobile MDA Vario 3) and 1x HTC Wildfire with Android 2.1 which all work and one Samsung Galaxy S on Android 2.2 which worked (in terms of being able to get calls with web apps loaded) up until 2.2 was loaded.
Well, that's very strange. All I can say is that my SGS and my partner's SGS, both were running 2.2 for a couple of months, and now both running 2.2.1 have been fine. I tested both again just now and I can make/receive calls fine on both even while actively using the browser.

Categories

Resources