yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] sullitf:
Possible epiphany on SMS problem in Hero

Originally mentioned by me here...

I just happened to see a reply to the almost 800 page JACHero thread that may just have given me the root cause of the SMS problems.

A user mentioned that he tested SMS by sending a few messages and missed a few of them. However, after removing all messages from that number he then received the next one no problem. An interested idea that I hadn't thought of until he mentioned it, but it could prove to be the bit of information needed to find the error.

I need as many people on Hero as possible to test this, send messages from another phone seeing what you do and dont receive (something like sending consecutive numbers, letters, etc. so you know what came and what didn't). After you test and can tell you are missing messages delete the thread from that phone number so that the message history is gone from the Messaging app completely. Repeat the first test again, seeing if you again miss message after the first.

If the second test proves to be similar, meaning you are missing messages after a conversation has been started in Messaging, proceed to the next test. Attempt to again send yourself messages from the other phone, but delete all messages between each one. If this is in fact the problem then you should receive all messages as long as a prior conversation does not exist.

Report back with success/failure of the tests, if this proves to be the problem then we have something solid to work on. It could mean something as simple as a SQLite exception being thrown. Possibly, Messaging is receiving all texts but attempts to make a new conversation thread with each new message rather than something like "if conversation exists add message, else create new conversation and add message".

This could explain the anomaly people have been experiencing with messages showing up in the notification bar or SMSPopUp even though no new message is actually present in the Messaging app.

Lets get testing, I hope this isn't another dead end!
[G1 Android Development] abteer:
Everyone that is having SMS problems try this...

rm -r system/sd/dalvik-cache/*

in the terminal

of course su before you enter that

I seem to be getting my text messages now.

Thank TwistedUmbrella for the fix.
[G1 Android Development] abteer:
I just missed a text so I guess it's back to square one.
[G1 Android Development] kvizz:
lol, thanks for the heads up.

thats sometimes why i never get some peoples texts!

there like wtf, i texted you and shiz, im like wtf...
[G1 Android Development] NexVision:
For anyone with the SMS bug not receiving please try this as I posted in the other thread..

The above post only shows part of the fix.
[G1 Android Development] NexVision:
I love how u thank twisted and dont even do the full fix then say it dont work. GOTTA LOVE XDA B000NS
[G1 Android Development] leoni1980:
How would clearing the cache for the default messaging app explain why the same problem occurs if either Handcent OR Chompsms is installed? They have no bearing on the standard messaging app do they?
[G1 Android Development] maxisma:
I don't think this fixes it..
[G1 Android Development] jj972:
I don't think it does either......just tested 3/5 msg received....I didn't get the first two
[G1 Android Development] abteer:
I did both

It didn't fix it

B000NS

But thanks for try

You win a toaster
[G1 Android Development] nolsen311:
It isn't ONLY Europeans getting this, I'm running on AT&T, and it happens semi-consistently. I'm sure it's the memory issue, as it DEFINITELY happens when a force-close/wait prompt is in the foreground. It's probably just that the T-MO users don't notice it because they're too busy searching for service or using up those 1100000 minutes that are the only thing t-mobile has going for it.
[G1 Android Development] sullitf:
The two possibilities I see at the moment are:

A) the messaging service is being killed off to regain the memory. I tried to test the by forcing the scheduler to hang on to the vitals such as gapps with the "renice" command in terminal with no success. -'ll look into this further when i get home tonight.

B) there is a problem with how the messages are stored on the phone. Possibly some type of SQLite error that kills off the messages after it is recieved but before we can see it. This could also explain why ChompSMS and Handcent are having the same problem, they pull from the same database.
[G1 Android Development] sherifone:
Or when AT&T's great coverage and 5 bars doesn't really tell you that their backbone is completely overloaded and your good connection to the tower is useless since there is no backend to support it.
[G1 Android Development] sacredsoul:
JacHero 2.3.5 is out and i saw "SMSReceiver service set to Highest priority" in the changelog. Hopefully, this fix things.
[G1 Android Development] abteer:
I think it might be fixed. Even on the browser I got 20 out of 20. There's a slight delay and slow down while uploading a page and recieving a sms but everything seems to go through.

I even was using the camera and received a message. I think they are on the right track to say the least.
[G1 Android Development] sacredsoul:
So you have not missed a message so far? 100%? Looks like time for Hero again.
[G1 Android Development] abteer:
No I started missing after a couple of reboots and whatnot. Pisses me off. I love that rom.
[G1 Android Development] sacredsoul:
Damn, I just flashed :(
[G1 Android Development] abteer:
Sorry was scrambling to find another rom to flash to. Maybe you'll have better luck. Please report your findings. Maybe it's just me.
[G1 Android Development] blackgin:
That problem is so boring.. We are very very very unlucky.. Can't use this wonderful rom for a problem like this
[G1 Android Development] maxisma:
Yes, this is mad.

Android receives the sms, trys to give it to a sms app, but fails because of missing memory ressources..
[G1 Android Development] leoni1980:
i dont understand why it gets so little attention. People MUST be losing SMS and not realising but they don't seem to care. I've sent myself loads of texts by way of testing on the Hero builds and received all of them, but then I'll suddenly find a message appears in the notifications bar but doesn't show up. This kind of proves that these self-sending tests don't necessarily prove that you're receiving everything. also if you receive multiple messages they won't all show in the notifications bar so you might never know that you haven't got them....
[G1 Android Development] ss1271:
Yes

i m the same as u

i pulled down "text widget" from market too

and when someone send me a text message, the phone's messaging app and notification bar dont have any reactions, but this widget DOES show the message.

if the problem like maxisma describes as the memory issue that killed the messaging app, why the text widget could receive and display text message?

r they using different process of phone?
[G1 Android Development] leoni1980:
The messages must be pushed to the notification bar first, then written (or NOT written!) to some other part of the phone. What could it be that sometimes prevents this data being saved?

I assume the widget is essentially an extension of the notification bar, since if you delete your last message it remains displayed in the widget window, and doesn't seem to mind that the message no longer actually exists.

I wonder where Android 'writes' messages to: I assume not strictly to the default app as the same messages are shared by Chomp or Handcent when they are installed, and the problem persists regardless of what app is installed.

I hope someone has a brainwave soon.
[G1 Android Development] sullitf:
I have been trying all the new hero tons and inevitably returning to a cyanogen rom for stability and speed. The Sms really is a deal breaker for me, having no clue when messages are missed doesn't work for me.

I'll have to try the widget next time I flash a hero rom. I get maybe 30% of my test messages on the last few JAC roms and never have the missed one show up in notifications or anything. If the widget does in fact show all my missed texts as they come in then my guess was wrong. I was thinking the SmsReceiverService was being killed off, pretty sure I'm where Jac got the idea to up its priority in 2.3.5.

However, if all messages do get through it may not be the receiver at all. I'm pretty sure the receiver throws out an intent with a new sms, everything listening to the intent gets it and checks to see what the intent is for (new sms, email, user input, anything really). Maybe the intent isn't always sent out properly, or the class that listens for new texts to add to the database is killed.

If we can track down what it is that actually adds new small messages to the database maybe we can find where it is going wrong.
[G1 Android Development] sullitf:
I have been trying all the new hero roms and inevitably returning to a cyanogen rom for stability and speed. The Sms really is a deal breaker for me, having no clue when messages are missed doesn't work for me.

I'll have to try the widget next time I flash a hero rom. I get maybe 30% of my test messages on the last few JAC roms and never have the missed one show up in notifications or anything. If the widget does in fact show all my missed texts as they come in then my guess was wrong. I was thinking the SmsReceiverService was being killed off, pretty sure I'm where Jac got the idea to up its priority in 2.3.5.

However, if all messages do get through it may not be the receiver at all. I'm pretty sure the receiver throws out an intent with a new sms, everything listening to the intent gets it and checks to see what the intent is for (new sms, email, user input, anything really). Maybe the intent isn't always sent out properly, or the class that listens for new texts to add to the database is killed.

If we can track down what it is that actually adds new small messages to the database maybe we can find where it is going wrong.
[G1 Android Development] abteer:
I can say that the sms widget doesn't pick up the missed messages for me. If that was the case I could live with that.

It's hard for me to believe that people are receiving "100%" of their messages when towards the end of me having 3.3.5 on my phone this morning I was receiving maybe at best 1 out of 5.
[G1 Android Development] ss1271:
And I think although the "text widget" could display messages, the non notification issue will also drives u mad. In addtion, this widget could only show u the last message u received, ie if u received 2 sms, it will only show u the last one.

No notification, neither notification bar nor notification sound and cannot displayed via message app are the biggest problems.

I hope we could got some fixes soon.
[G1 Android Development] sullitf:
While those are definitely the most important, and irriating, bugs the widget may yet lead us in the right direction.

If the widget does show messages that don't show up otherwise that means one thing, messages are getting through and die somewhere along the way. It also means the smsreceiverservice is doing its job in getting the messages and passing them out, but somewhere along the way the service itself, the system intent, or the service that adds the messages to the database is dying.

We need to find out the exact path new messages take and go from there. That may help us pinpoint the process that is dying and throwing away our messages.
[G1 Android Development] sullitf:
Triple post. sorry, I guess my phones browser lagged and resent the request.
[G1 Android Development] leoni1980:
just an update.....

problem still persists in the JACHero release posted today....

:-(
[G1 Android Development] jj972:
Hey I got some crazy news......I'm testing out superhero3 and mannnnnnn.....I got 22/22 sms and bout 4/4 mms so far! I had the big issue with every other rom and this one I think is it.....

Will report back later
[G1 Android Development] leoni1980:
Hate to piss on your bonfire but I tried a similar test last week with JACHero: sent myself 26 sms from A to Z, also got my friend to send me 10 messages in a sequence. I received all of them and rejoiced; but within a few hours I started to have missing texts again. So much as hope Superhero 3 fixes the problem - would hold off the celebrations for now. Do a few reboots, install a few apps. See if the problem stays away.
[G1 Android Development] jj972:
been on it since noon and all the msgs i was referring to were sent from different ppl while i was surfin thru xda.....

a very big step because in drizzys and jacs, i would only receive about 50%-60% in diff order

but like i said so far so good
[G1 Android Development] ss1271:
Woohoo

That'll be the best news I've heard today.

I haven't received any txt msg or mms msg while on jac/drizzy's/superhero v2 except the txt widget sometimes show me one or two...

Have u used swapper? If used, how u set it?

Have u tried open six different apps and then test if u can receive msg/mms or not ?

Thanx for ur test!
[G1 Android Development] jj972:
Well personally I cant stand the lag on rosie so I pushed a launcher and did away with rosie and HTC widgets........

I also removed swapped, teeter,etc...... I still have all hero apps, dialer, etc so I'm good...
[G1 Android Development] abteer:
You might as well run a non hero rom with the hero theme if you don't use rosie imo. But I tested superhero v3 also and got 50 of 51 while in the browser but I couldn't recieve Mms. Oh well. I only ran it for about an hour also so it might degrade after time like mentioned above. Also how did you experience lag on superhero v3? It runs like butter with rosie.
[G1 Android Development] ss1271:
that's the problem.

ROISE may take a lot of memory to suppress the msg app.

SuperHero v2 w/ roise is laggy... i havent tried v3 yet. but i think it may not as fluent as drizzy's or jac's.

btw...if we r using a hero rom w/o roise, why we use it?
[G1 Android Development] jj972:
Yea but I still want the hero dialer,camera,gallery,lockscreen,msging,peep,calender,alarms,etc and that's exactly what I get but with no lag.....

And I don't like the tradeoff when using swapper and hate the lag on rosie without it so I'm satisfied with no rosie
[G1 Android Development] ss1271:
are these newly built Hero ROMs solved the SMS problem?

does anyone have any reports?
[G1 Android Development] j2kquest:
Im using jachero 2.73 with linux swap and ext 3 set up....runs like a stock build and im also receiving sms whilst browsing.

i think its safe to say im getting all my text msg's.....im waiting for someone complain abt not replying to their txt's

So far so good on Jachero 2.73 (aka jacheroski 2.73 new collaboration)
[G1 Android Development] ss1271:
oh nope...

i got a message app forced closed issue...
[Touch Pro2, Tilt 2 Windows Mobile General] Alcibiade:
I bought my TP2 from the web (I was usuing previously an Hermes (X01HT)

Been using it for 3 weeks. It works perfectly. Calls quality is excellent, data transmission fast, no particular issue with Softbank network, I am pretty happy about it

What I dont like, and nothig to do with Japan (Dont get me wrong, I am a big HTC fan and I love my phone):

1. Poor built quality. The phone looks great.. out of the box. After 2 weeks in my pocket the Chrome finish starts to crack and let appear some black paint. I am treating my phone well, really not trying to break it, this is under normal use. Honestly very very far from an iPhone built quality (Again I am not an apple fanboy). It's not a "big" problem but for a phone that costs that much it's not really acceptable (I have an Hermes who took way longer to crack...)

Other issue is the Tilt mecchanism a bit soft and sometimes not deploying the screen exactly inline with the keyboard (Some other posts detail this better than me)

2. TF3D is nice... rather fast... BUT too many important menues are lacking compared to WM6.1 menus (for instance it took em a while to find out that what was preventing me from allowing to synchronize some of my activesync folders was the lack of option in TF3D. Similarly the handling of contacts screen misses too many options). Maybe there is a way to have all WM6.1 menus appear under TF3D, in which case I am a taker if you have some trick (registry trick maybe ?)

3. Some GPS issues, but I hope I'll be able to fix this (Or maybe just my model has an issue)

4. Some slowness in the handling of contacts / SMS (granted I have many so it may come from that but my Hermes (with a modified ROM) was way faster)

All in all very happy with the phone, beautiful screen, excellent touch feeling, lots of great functions... Just the external built quality will probably attract the jokes from my friends with iPhones
[Touch Pro2, Tilt 2 Windows Mobile General] shunsai:
Alcibiade, thank you SO much for starting this thread! I'm in the same boat I guess you were 2 months ago. I'm an x01ht user (actually, i remember seeing your name in the forums). but i think my x01ht's better days are behind it and i'm very ready to move on to my next pda phone. i'm staying with softbank, but refuse to buy anymore of their handicapped phones. so i'm considering buying the Touch Pro 2 (online).

i'm a bit confused though as to if there is a particular model I need to get. the whole GSM versus CDMA thing really confuses me. can you let me know where you bought your touch pro 2 from and which network band. i assume CDMA since japan is WCDMA, right?

again, thanks for any help/info you can give.
[Touch Pro2, Tilt 2 Windows Mobile General] Alcibiade:
I was not sure either and asked the shop (Expansys in HK)

I bught the European model an it works perfectly: 3G is the same in Europe and in Japan (Whereas US carriers use different frequencies). So it will (and does) work perfectly. 2G wont, but it didnt either on your X01HT :)

If you buy it you wont regret it, I really love mine (But the Hermes was an excellent phone... Just needed a bigger screen...)
[Touch Pro2, Tilt 2 Windows Mobile General] shunsai:
thanks for the informative reply. i'm leaning heavily towards ordering mine within the next 24 hours. $700 is a lot of money. out of curiosity, how much did japanese customs duty charge you for the import of the phone?
[Touch Pro2, Tilt 2 Windows Mobile General] shunsai:
Alcibiade, still waiting on you to come back online friend! Guess I need to bump this thread up! I'm looking for some of your expertise and experiences using this phone in Japan. I'm curious as to which ROM you had installed in yours (any chance you can put it in your sig?).

i have another thread going where i'm trying to get other people's experiences with japanese input ability. for some reason, i just can't get Japanese input on my phone. I can see kanji and kana fine in texts, webpages, emails, etc. but i can't enter any myself. when you installed the raphael/diamond Japanese IME, and Softbank MMS on your phone, were you able to write Japanese?
[Tilt, TyTN II, MDA Vario III General] deady:
I have Kaiser with schamps Rom, dunno with version.

I can not connect anymore to a pc via activesync or bluetooth. Tried on different maschines.

Sometimes the phone got stuck in the 3 colcor boot mode, but not it works again. I think i could reflash but i don't want to loose al the unsynced data...

Any ideas?
[Tilt, TyTN II, MDA Vario III General] averestefd:
what to do...

do you have wifi? microsoft myphone.. even live...
[Tilt, TyTN II, MDA Vario III General] veList:
Use pimbackup to backup data.. and then flash new rom or radio.. fast and easy..;)

Cumps,

veList
[Touch Pro2, Tilt 2 Windows Mobile General] Kork:
Hi,

am going to send my TP2 back to amazon because of dead pixels. I want to kill all data from it (except the one on my SD card). So taking out the SD card and doing a hard reset came to my mind. Does this kill anything that is on the phone, or would you suggest another method for clearing all data from it?

Thanks,

Kork
[Touch Pro2, Tilt 2 Windows Mobile General] GordonTGopher:
Yes!

Hard reset will clear all data in the phone, and resets it as if it had just come from the factory. You may want to consider getting something like Sprite backup or SPB backup (search the forum for more info) then when you get your replacement device you can restore everything so it's just like your old one (apart from the dead pixels :-) )

Gordon
[Touch Pro2, Tilt 2 Windows Mobile General] Kork:
I just made a backup using spritebackup :)
[Touch Diamond, MDA Compact IV ROM Development] aqua73:
After upgrading my HTC diamond with any ROM based on win.mobile 6.5 when i softreset the device, the device is doing hardreset and starting completly fresh installation. What might be the problem.
[Touch Diamond, MDA Compact IV ROM Development] benko286:
here is your solution

http://xdaforums.com/showthread.php?t=490182&highlight=strange+problem
[Touch Diamond, MDA Compact IV ROM Development] aqua73:
I hava windows Vista. I tryed MTTY with USB connection, but every time i get "USB port cannot be opened"?????? And what will I get wit this procedure? What actually is the problem?
[Touch Diamond, MDA Compact IV ROM Development] Zaslav:
Funny I started having that problem this morning. I did a reset about 30 mins ago and now my device won't even boot up. I think it's bricked...:eek: Just hangs at the Rogers start up screen.

*sigh*
[Touch Diamond, MDA Compact IV ROM Development] benko286:
read this ;)
[iPAQ rw6828, XDA Atom General] beng46:
signal not so strong (sometimes cant get signal), camera and comm button not functioning when phone is on but still functioning when need to get into bootloader, no stereo sound no ear speaker sound.. but when open radio put on loudspeaker, can hear sound... thia PDA is like short circuit or something... coz still can hear sound when use radio loudspeaker and radio can turn on without using earphone...suspect audio jack faulty (as many these kind of problem on atom come frm audio jack) so the audio jack already taken out... but still same... but still can use as normal PDA such as wifi, got powerpoint, excel, word, CORE player and many apps come with this titanium ROM....plz help can anyone tell me about the problem..thanks

:confused:
[iPAQ rw6828, XDA Atom General] neorox8:
firstly i ws thinking that your inner h/w of the camera or comm button is not n contact with the outer button for the respective. but since you have told that they are working properly in boot loader, so it is not the problem of contact.

Try one thing. Goto Start-> settings-> Buttons (in WM6.1). check if you have camera asigned with respect to the camera button. Check similar for the others also