Develop Bugs

Sent SMS not displaying in TF3D interface

Pretty much what the title says. Texts go through but don't show up. If I send them from the windows mobile generic messiging they always do show. In the TF3D skin (for lack of a better term) the show intermittently. I have the stock sprint rom, and disabled the sent notification. Thinking this may be the problem, I re enabled it to no avail.
Any ideas? This is my only gripe with the phone. Much better than the touch pro original junk I did have five of.
Thanks in advance.

Probably not threading properly, due to timestamp error. check at the top of your texts, should see all sent texts at top. If so, go to htc support, enter your phone/carrier, and you'll be directed to downloads for your TP2, which will have an SMS/Timestamp Hotfix to download, will fix all SMS problems.

HTCJake said:
...go to htc support, enter your phone/carrier, and you'll be directed to downloads for your TP2, which will have an SMS/Timestamp Hotfix to download, will fix all SMS problems.
Click to expand...
Click to collapse
Not for the t-mobile version.
Ivanstein said:
Pretty much what the title says. Texts go through but don't show up. If I send them from the windows mobile generic messiging they always do show. In the TF3D skin (for lack of a better term) the show intermittently. I have the stock sprint rom, and disabled the sent notification. Thinking this may be the problem, I re enabled it to no avail.
Any ideas? This is my only gripe with the phone. Much better than the touch pro original junk I did have five of.
Thanks in advance.
Click to expand...
Click to collapse
Sometimes when I'm texting through the HTC interface, sent messages won't pop up higher than the text input box, but they're still there...I just have to manually scroll down to see them. That may not be your issue, but I wanted to make sure that possiblity just didn't get overlooked

i don't think sense is supposed to show sent messages
sirphunkee said:
Not for the t-mobile version.
Sometimes when I'm texting through the HTC interface, sent messages won't pop up higher than the text input box, but they're still there...I just have to manually scroll down to see them. That may not be your issue, but I wanted to make sure that possiblity just didn't get overlooked
Click to expand...
Click to collapse

I had already installed the 2016 hotfix. If I try to reinstall it, I get a wrong device error. When the texts do show up, the date is correct.
I don't have sense, its the stock sprint 6.1 rom.
I gather this is a pretty unique problem, since googling the hell out of it doesn't get any complaints like it showing up.
I am guessing its in the TF3D interface, since it always works in windows, and I have tried hard resetting, but that doesn't fix it. I did discover it is present in a bone stock config no cabs or anything other than what is in the rom installed, it still does it.
Do I need to demonstrate it to sprint and ask for another device? I am really getting sick of fighting with sprint. The touch pros I had were all crap and getting them to replace it with just a touch pro was a chore, let alone finally getting this TP2. They kept wanting to put me in a RAZR or a Snap. Wow, what a great deal there!

HTC Msging and Camera 2 different settings?

Hey all,
I just posted a thread in the HD2 forum so I will bring it up here to see if anyone has noticed this, because I searched the forums all night last night and didnt find any posts about this:
If this has been covered please direct me to the thread, but it seems there is two camera settings, which is annoying the hell out of me. Let me explain, some may not notice this but I did two days ago when it annoyed me.
When you take a picture with the camera, with the setting 3m and quality of superfine, the pictures based on detail could be anywhere from 500K+ which is fine, but taking the same picture thru the HTC messaging app does not, even though after taking the picture it is barely making 50K, when I checked the settings thru the htc messaging app the camera settings are completely different then when using the camera as a standalone.
In the Standalone the setting is @3m with superfine quality, but thru the messaging app its set to 640x384 and the quality if set to fine or normal. And the resolution is greyed out so you cant change it.
Now you may ask why, the reason is on the fuze I was able to send pictures as attachements thru the app without having to go the camera and then take the picture then go to the msg app and send it, The primary reason I am looking for the resolution change is because on ATT your limit is 600K to send any pix or MMS, so why doesnt the app allow you to choose the compression level and no matter what make the pictures on avg 50-60k?
If anyone knows where this is located please let me know, or if you know how I can change this I'd be thrilled! And no I am not looking to change arcsoft since I fixed the HTC messaging app issue.

I think I found the location of the second camera setting, the only problem now is everytime I change the setting in the registry it doesnt make a difference what I change it to in the settings it doesnt change, and when I reset the phone, the values go back. here is the reg entry if anyone can help:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\HTCPhotoPicker\HTCMessaging_Client\Setting\VirtualContent_1]
"ResolutionHeight"=dword:000001E0
"ResolutionWidth"=dword:00000280
"Type"=dword:00000001
"StillQuality"=dword:00000000
"Mode"=dword:00000000
So far I know that "StillQuality" can either be:
0=Auto Fine
1=Basic
2=Normal
3=Fine
It wont allow you to pick "Superfine" by adding 4 just doesnt work.
"Mode" Is for:
0=Camera & Video Mode
1=Video Mode Only
Havent figured out what "Type" is yet.
"ResolutionHeight"=dword:000001E0 = 480
"ResolutionWidth"=dword:00000280 = 640
These two entries I cant make stick to any other resolution then that, Tomorrow I am going to see if it will allow me to change the settings lower then what it defaults to.

Anyone know how???

FIXED: SMS Timestamp Issue

UPDATE: I've found a fix for this issue - AWESOME!
Just go to the Android Market and install the SMS Time Fix app by Matt Precious.
http://www.androlib.com/android.application.com-mattprecious-smsfix-pAFq.aspx
It works perfectly, and updates the time stamp on all messages to relfect PHONE time and not network time. HINT: Make sure the "Last Resort" option is checked in the settings and offset is set to zero. This little app now makes the Evo Messages app usable. Finally...
Hope this is helpful info
So, I've been reading and experiencing several issues with SMS timestamps on the Evo 4G.
It seems there are three distinct issues with SMS timestamps on the the Evo and I believe they all have the same root cause.
Issue 1: When roaming texts are received with the wrong time stamp, offset by several hours (typically 4 or 5 hours off). This causes them to not be threaded in the conversation correctly. Very annoying.
Issue 2: When receiving SMS messages on any network (Sprint or Roaming), the time stamp is off by an hour. The result is the same as Issue 1, but a less extreme example.
Issue 3: When texting back and forth in quick succession, SMS messages are not logged in the order in which they are received, and received text messages ALWAYS appear before sent text messages if they are sent during the same minute, regardless of which one was actually sent first. This is also very annoying.
I believe the root cause is that the native Sense UI messaging app is using the timestamp of the tower of each SMS rather than using the time stored on the phone. To prove this, if you use Handcent and set it to use "phone time" and ignore the tower time, it works perfectly. The thing is that I don't want to use Handcent and I want to use the native app. Is there a setting that can be tweaked to fix this? Has anyone talked to HTC or Sprint about the issue and is a fix in the works?
For such a major problem, I am surprised more people haven't come forward. It's a pretty significant bug...
Thanks,
Matt_TX.
Click to expand...
Click to collapse

I agree and its getting really annoying since it causes me to miss texts.

NM, too easy

Has anyone talked to Sprint or HTC about it? I am sure there HAS to be a fix in the works. The good news is that the native Froyo messaging app does not do this (as far as I can tell). I used a Nexus One on T-mobile and it doesn't occur. It appears to be using the phone's timestamp, as it should...
As long as HTC don't apply their "logic" (or lack thereof) over Froyo, it should be fixed soon.
I also can't believe that Sense UI stops the user from having more than one Exchange account. Android 2.1 (Eclair) does this by default. Why on earth would they remove it?
Anyway, back on topic... Please please post with your thoughts and discoveries around the SMS timestamp issue.
Thanks!

How is this related to development?

tkrechel said:
NM, too easy
Click to expand...
Click to collapse
I'm not sure what you mean by "NM, too easy". Can you explain or provide any insight. Please help if you can. For those of us with this issue, it's REALLY annoying. I apologize if the question is dumb and there is an easy fix.
I realize that some of you may not feel that it is related to development, but I disagree. For those geniuses out there that make ROM's, maybe there is some way to fix this with a setting or minor change in the Sense UI messaging app...
Additionally, there is no need to berate someone that's genuinely asking for help. It's obvious that this forum gets the most traffic, and it's obvious that the smartest "Evo User" minds are located here. I don't think there is any harm in reaching out for help, isn't that the purpose behind these forums

The samething was happening to me last night.
Sent From My HTC EVO 4G

nebenezer said:
How is this related to development?
Click to expand...
Click to collapse
Agreed. If its not happening with Handcent nor the AOSP apk, then its a direct HTC issue.
General Discussion. Also, probably not really that urgent.

./agree on all poins with OP.
I posted in Q&A about this same issues, with no replies 8(.
Anyway, I thought it was related to the modified prl that I installed. However it would do it even when I was on the stock prl.
Long story short, I called sprint and said I was having the issue. They said they were going to refresh something on their side, to wait 20 mins then power cycle the phone.
Did that and to my surprise it worked! Then yesterday I re-flashed a custom rom and the sms timestaps went all wonky. /sigh

suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.

this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.

davebu said:
suck it up and use handcent or chomp, they are overall better apps, just not as nice of a UI.
Click to expand...
Click to collapse
look at this guy.
handcent didn't work on my froyo rom, not sure about chomp, didn't try it.
at work i always have this problem, texts are recieved 5 hours into the future, whereas the ones i send are the correct time. occasionally ones they send are the correct time so i have to scroll up and down and it is very annoying.
not a fan of handcents pop up notifications, i guess i could turn em off.
guess i'll just 'suck it up'

regulator207 said:
this has been a problem for quite some time. I've looked everywhere for a solution. This was a problem on winmo phones as well.
I switched to handcent and never looked back. Once you get it all customized, it's awesome.
Click to expand...
Click to collapse
yup, had the same problem on my old HTC Diamond with Sense/TF3d on it.

Updated First Post...

[Q] GingerBliss SMS Timestamp

I'm using TSM GingerBliss and noticed the timestamps for incoming messages with the HTC messaging app are 3 hours earlier than my phone's current time. Haven't seen this before and haven't quite gotten around to testing with GoSMS or another app. Does anyone know why this is happening, or what file/setting I need to modify to correct this?
I would've posted this in the development area but I haven't posted enough past posts, and it's probably suitable for the general area anyway.

I am running TSM Bliss too but my time stamp is correct. I am not sure what is going on. I would try another messaging app to see if it is wrong there too. If so then you know it isn't the messaging app. There could be some sort of lag on your local Verizon network at the moment.

Hmm, thank you, and good thought on the Verizon lag, but I'm not sure if that's the issue though. As an initial test I sent myself a message, which returns within a few seconds with a timestamp 3 hours earlier than my phone's time. I'll try another app to check as well.
As a temporary fix I installed 'SMS Time Fix' which helps, but I'm curious now as to the actual problem.

Same here man idk what's going on
Sent from my ADR6350 using XDA App

honestly, i dont know why its doing that for some and not others..and tbh i dont know (ive poured through the xmls) and not seen why/what would be doing that

Yeah, that makes two of us so far I've tried with the stock and GoSMS apps with the same result. The SMS Time Fix app does work at fixing the timestamp, but I'm curious as to how it does this which could lead to some ideas. Newt's Inc2HD ROM has the same issue.
So does the messaging system rely on time zone info? I'm heading to another time zone so I'll be able to test that.

Ok, so I'm in Kansas City, and now the timestamps of my incoming messages are 2 hours behind. So for some reason the messaging system thinks I'm in the Pacific time zone. Maybe it's using my home zip code that I have setup through Verizon, which is in California...not sure. Another strange thing is that MMS are not affected, only SMS, go figure.
However, I might have found a setting on my flight over that could work. Maybe someone can confirm this, but in the folder
/data/data/com.android.mms/shared_prefs
there is a file
com.android.mms.customizationBySIM.xml
that has a line
<boolean name="SMS_Use_Device_Time" value ="false" />
I changed it to true, and now all the incoming messages use my phone's time, even after restart. I don't know, maybe that was added by the SMS Time Fix app, sounds promising though. Any thoughts?

Exif data from mms pic

Does anyone now a way to retain exif data information from mms pics that are received.It seems whenever I save a pic all the exif data gets wiped,lol I remember when I had a tmobile dash (windows Mobile) it gave you the exif data flawlessly.And now Im on my third android and it seems that the exif information does not get included when I get pics from mms,anyone know any codes or anything inyo term emu to enable this feature,
Thanks

You could ask people to gmail them to you instead of MMS, I assume it wont be converted in.anyway.

phatmanxxl said:
You could ask people to gmail them to you instead of MMS, I assume it wont be converted in.anyway.
Click to expand...
Click to collapse
good idea,im going to try that now I remember someone sent a pic to me from an ipod before lol.

I don't remember what phone it was (might have been the Samsung Moment) but the cooked ROMs had MMS broken for a while. Gmail is great cause it will stay in your mailbox for as long as you want instead of your phone, even when you switch carriers, phones or ROMs.

brianhot1 said:
good idea,im going to try that now I remember someone sent a pic to me from an ipod before lol.
Click to expand...
Click to collapse
Yea it seems as tho this might be the only way to view exif I saw some info there,I wish I could get this thru regular mms, not everyone has my gmail, and I don't want any and everybody with it lol

phatmanxxl said:
I don't remember what phone it was (might have been the Samsung Moment) but the cooked ROMs had MMS broken for a while. Gmail is great cause it will stay in your mailbox for as long as you want instead of your phone, even when you switch carriers, phones or ROMs.
Click to expand...
Click to collapse
O ok, and I am stock rooted ek02

Try the email app, make a separate email account through yahoo or what ever. Im not sure if you can download attachments though I never used it.

the email would be a good idea,I would really like it for mms tho that I receive from my phone number,anyone know of any scripts or anything to run in term emu for that to happen,or would this not ever be possible

brianhot1 said:
the email would be a good idea,I would really like it for mms tho that I receive from my phone number,anyone know of any scripts or anything to run in term emu for that to happen,or would this not ever be possible
Click to expand...
Click to collapse
BUMP ... This would be a great feature to be able to script something( Tasker maybe ) to email you any mms that comes along.

RubenRybnik said:
BUMP ... This would be a great feature to be able to script something( Tasker maybe ) to email you any mms that comes along.
Click to expand...
Click to collapse
sounds good to me,I wonder if such a thing is possible

Anyone? Or no one else is interested

I'm pretty sure there isn't a script you could use for this. It's really going to depend on the senders phone. Some phones will compress the image, reformat it, remove 'junk' information such as exif when sending an MMS. Sometimes it's the carriers servers that remove exif. Other times it's the recipients phone.
The thing is, Android has a MAJOR flaw. MMS
Unless you have devs that remove or minimize compression from the stock app (or you use Handcent or Go! SMS) there's nothing that can be done. Android horribly compresses pictures and videos. a 1MB picture can be cut to 5kB or less. I remember my Blackberry 8900... on EDGE no less... would send a 3MB pictures through MMS with no issues. I even think the exif data was retained when I received them, assuming the sender or carrier didn't strip that info. Those were the days...

KCRic said:
I'm pretty sure there isn't a script you could use for this. It's really going to depend on the senders phone. Some phones will compress the image, reformat it, remove 'junk' information such as exif when sending an MMS. Sometimes it's the carriers servers that remove exif. Other times it's the recipients phone.
The thing is, Android has a MAJOR flaw. MMS
Unless you have devs that remove or minimize compression from the stock app (or you use Handcent or Go! SMS) there's nothing that can be done. Android horribly compresses pictures and videos. a 1MB picture can be cut to 5kB or less. I remember my Blackberry 8900... on EDGE no less... would send a 3MB pictures through MMS with no issues. I even think the exif data was retained when I received them, assuming the sender or carrier didn't strip that info. Those were the days...
Click to expand...
Click to collapse
o ok I also been looking at this to online
http://code.google.com/p/android/issues/detail?id=3251

would this help anyone,anyone who is a programmer? this looks french to me lol
http://stackoverflow.com/questions/2323722/using-the-android-sdk-im-not-seeing-any-exif-in-my-jpegs

brianhot1 said:
would this help anyone,anyone who is a programmer? this looks french to me lol
http://stackoverflow.com/questions/2323722/using-the-android-sdk-im-not-seeing-any-exif-in-my-jpegs
Click to expand...
Click to collapse
NO ONE?

brianhot1 said:
would this help anyone,anyone who is a programmer? this looks french to me lol
http://stackoverflow.com/questions/2323722/using-the-android-sdk-im-not-seeing-any-exif-in-my-jpegs
Click to expand...
Click to collapse
For the issue of exif data not being sent with mms pictures - or being received that will not help.
What that's about is the person is using a call used to access the camera in another app that they're developing. The issue is that it doesn't by default save any exif data. That's a different code. For him/her the issue isn't not being able to access exif data from a picture - it's the fact that it's not saving to begin with.
Now, in the mms app there may be a line telling it to remove all non essential data from a picture before sending. However, even if you allow the information to be retained odds are it will only work on your end - not the receivers. Same goes for them if they send a picture. Then again - carriers may just as well block exif data for safety reasons. A lot of people unknowingly have geotagging activated. I'm sure you can see how that could be very bad in some situations.