yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] akhil7j:
Thanks guys. Hard reset worked for me. :-)
[Galaxy S I9000 General] buntoo:
Same happend to my SGS 2day. Maps got stuck and I had to remove & reinsert the batter. And now I just noticed after 6 hours that Accelerometer & Digital Compass not working :(

Isn't there any solution other than hard reset? :mad:
[Galaxy S I9000 General] buntoo:
Ok i made a titanium backup and did a factory reset. Everyting is working fine now. Restoring the data now.
[Galaxy S I9000 General] Cyberdyne systems:
Had same issue a month or so ago, did factory reset and all is well (and hey we need to practice putting everything back on the phone for all the new firmware this model gets :))
[General Questions and Answers] scorpio50:
hey guys.

i m user of htc desire hd. i got 580 mb of ram like everyone but due to installtion of app it remains to 250-280mb after killling apps with appkiller.

is there any way the developer has made to increase ram or transfer sd card memory to ram or use sd card as ram....?

kindly help me and tons of other desire hd users....!
[General Questions and Answers] Siresmokalot:
this interests me as well,though i am pretty sure it's a bad idea to use the sd card as ram if you plan on using it for other purposes as well (i'd compare it to hyperboost with usbsticks on win7/vista,which sucks)
[General Questions and Answers] egorgoblin:
I would not recomend using appkillers, Not only they are usless you might harm your phone. Those aplication you are killing are working in background and using very little memory. You cant even tell how little. Use appkiller just to monitor how many ram a program is using.
[Android Apps and Games] jdb78:
Thank you might. Do you think the ad's will slow the app down so it could possibly lose messages, too?

The beta version you posted within the eZGinger thread worked very well for me up to now, testing your new version from now on.
[Android Apps and Games] hrk:
Absolutely NOT! :-)

It would mean shooting myself in the foot, since I use the same version that's in the market.

Ads are shown only in the screen you use to check/read the messages. It's the same reason that contact name lookup is done there but not on the notification (although the code allows to safely put it there too...)
[Android Apps and Games] hrk:
:D While writing this very message I lost an SMS! :D Luckily the app caught it. Now I've seen that there's a "bug" with long messages, which the stock app merges into one, while my app keeps split. I've looked at the code of the stock app, at the SDK and I don't think I can add it without big changes in the code that I don't like (those very changes, not big changes in general).
[Android Apps and Games] anzoshi:
Please ignore - I was using an outdated version
[Android Apps and Games] hrk:
New release on the Market.

2011-04-16 - 1.4

- Split messages are joined into a single one (only for newly received messages)

- Complete metadata is restored when moving to INBOX (eg: original carrier date in place of when you moved it)

- GUI fixes, so that the progress bar is shown every time the database is read.
[Android Apps and Games] daniel590:
Is the problem with the lost sms only in the stock sms app?
[Android Apps and Games] hrk:
Without reading the source code for other messaging apps, I cannot know.
[Android Apps and Games] hrk:
New release on the Market...

2011-04-17 - 1.5

- Fixed FC when deleting all messages.

- Reworked code to get a faster app.
[Android Apps and Games] hrk:
New release! :)

2011-04-29 - 1.6

- Added count of recovered messages

- UI fixes
[Android Apps and Games] Szyms:
Could you make this app aviable for 2.2? I've got this bug on some Froyo roms.
[Android Apps and Games] hrk:
I thought that the bug was introduced with Gingerbread (hence the name of the app) but I see that half of the market downloads come from FroYo ROMs... which puzzles me, since I've set API 9 as the minimum supported API. How can they download it? :confused:

Are you sure you are suffering from the same bug?

This poses an even bigger problem: how do I rename this app if I add support for FroYo? :p
[Android Apps and Games] Szyms:
Well, I can't be sure until i'll check it :)
[Android Apps and Games] hrk:
I guess you're right... so... 1.7 out!

2011-05-07 - 1.7

- Fixed a rare FC when a message was deleted and phone was under heavy load

- Allowed installation on Android 2.2 FroYo due to popular demand
[Android Apps and Games] ferryPL:
I just tried your app and it really works! I had the problem with receiving messages in stock froyo.

But I have 2 questions.

When I receive sms when my sms app works fine I have two notifications in status bar. One from stock sms app, one from your app. Is it possible to notify that my sms was recovered only when my sms app has been killed due to low free ram?

There should be only one notification. From sms app or your app. Depending which app received message.

Second question is why don't you just modify android sms application if you know where is the problem and how to resolve that? :)
[Android Apps and Games] hrk:
That's bad, I cannot call it "Gingerbread Ghostly SMS" anymore! :D

Unfortunately it's not possible, because of how Android handles notifications. Every messaging app is called at the same time (more or less) and no app knows the existence of the others. The only way to show a single notification is to "steal" the SMS so that the Stock app never receives it. I'd never do that. :)

Because then I could not put ads there! :p Seriously: fixing the issue in the stock app requires a lot of work, with no way to know if Google will accept the changes. And that would be a waste of time. I hope they do fix the bug themselves, then I'll retire the app :)
[Android Apps and Games] ferryPL:
They will not fix the bug themselves. They didn't fix that in 2.1. They didn't fix that in 2.2. They even didn't fix that in 2.3...

Fix this issue in stock app, add your ads and then throw it to the market! ;)
[Android Apps and Games] ObihoernchenDE:
yeah this would be awesome. Maybe you could fix it in Cyanogenmod repos.
[Android Apps and Games] ferryPL:
CM has this feature already.
[Android Apps and Games] hrk:
Are you sure about that? Do you have any proof? Don't get me wrong, I am not picking on you, it's that roalex's COS (Cyanogenmod Open Source) ROM suffers from the bug. So if CM has fixed it, it should be fixed in COS too. :)
[Android Apps and Games] WatsonDue:
Noticed the same thing too. Sometimes it happens.

And I do not receive any notification on these SMS in Ghostly.

I can do some tests if you want.. even in Italian!:D
[Android Apps and Games] hrk:
Ok, I am unsure about the "not receive any notification" part. I am running Ghostly w/ the delayed notification but without deleting or moving the messages back to the INBOX.

There are some messages for which I get a double notification and the new feature (called "Debug accuracy") helped me determine that there was a need for a higher accuracy (1300ms instead of the 1200 which I used). I guess this will help a alot. :)

I'm streamlining code even more, so I'll ask everybody to try the new 1.21 (not yet released, I guess it may be ready tomorrow) and report back those nasty bugs of "not moving messages" or "ghostly didn't receive the message" (which looks way scarier to me)
[Android Apps and Games] hrk:
2011-12-27 - 1.21

- No more lag in list scrolling!

- Focus on last received message

- Long press on a received message to adjust delayed notification accuracy.

This is the market description, but there were optimizations all around trying to avoid any possible extra time in the SMS receiver (well, the database saving part has not been changed since it can't get faster than it already is...)

As usual, test and report back. I hope the new option to "adjust accuracy" will help discriminating between real bugs and perceived ones. :)
[Android Apps and Games] hrk:
2011-12-31 - 1.22

- Fixed "Force-close" on "Delete all". Bug reported on the Android Market

Guys, have a nice 2012! :-)
[Android Apps and Games] HertogJanNL:
Thanks, will test this app, since I've been losing quite a lot of text messages lately!

Will let you know how it works out for me :)
[Android Apps and Games] Lord Bodak:
What are the dangers of setting the accuracy too high? I've been slowly bumping mine to eliminate double notifications and I've had to go all the way to 5500 so far. This is on a Desire Z running Virtuous Sense.
[Android Apps and Games] hrk:
If you did NOT enable "Delete duplicates", there "danger" is that you won't get a notification, but Ghostly will still save the message in its internal database.

If you, however, ENABLED "Delete duplicates", then if you receive a second message from the same sender inside the "tolerance window", Ghostly will ignore it and if Android lost it, you lost it. I can't explain it with words, let's try an example. :)

You have to be using "Received timestamp" instead of "Sender timestamp", and "Delete duplicates" for this to happen.

Time is hh:mm:ss.

08:00:00 +3912345 sends you a message. Android doesn't lose it.

08:00:05 +3912345 sends you a second message. Stupid Android loses it!!

Accuracy: 2000ms.

When you receive the second, Ghostly will see that there is no message in the inbox from +3912345 with a received time between 08:00:03 (time - 2000) and 08:00:07 (time + 2000), so it will save it and show a notification.

Accuracy: 6000ms.

When you receive the second, Ghostly will see that there is a message in the inbox from +3912345 with a received time between 07:59:50 and 08:00:11, will not store it and will not show a notification. You lost it.

If you can enable "Sender timestamp", I strongly advise you to use it. If you ROM doesn't support it, try not to set accuracy too high or tell people to send you no more than one message every minute ;-)
[Android Apps and Games] Scudderb:
Hi there...

I had an issue back on 12/13/11 where I was "out of nowhere" receiving some duplicate message (http://xdaforums.com/showthread.php?p=20260291#post20260291) which you kindly looked into comparing versions 1.18, 1.19 and 1.20 and came to the conclusion that there was nothing really changed in the versions since 1.18 and that the issue I was experiencing was likely

not

attributable to Ghostly SMS.

Well, right around the time you posted your reply to my issue, I got rather sick, and then the rest of the family did (two little boys) and got busy with "life" and a licensing test. Anyway, I've been out of the loop for a couple months and might be having another issue HOWEVER I want to inquire and check with a few things....get "back into my phone"...to see if I am simply doing something wrong BEFORE I post a question.

Anyway, couple questions that I wanted to understand before I inquired about "an issue"...

First, when I launch your app, it brings me to the "Received messages" screen. At the top (for me) it says "Received messages. 254 recovered so far." Is my understanding that this number "254" is the number of messages that Ghostly has received

and which Android has missed and failed to deliver to my message app inbox

?? Or does number mean something else.

Also, I noticed in the changelog of the recent update 1.21 that one can long press on a received message to adjust the notification accuracy. When I do that for the last few messages in my Ghostly "Received messages" list I get values such as the following:

Delta 24,348, required accuracy: 24,400ms

Delta 31,236, required accuracy: 31,300ms

What exactly is this "delta" number of >24 and 31 seconds respectively?? My settings are as follows if the information is needed to answer my question:

Notification: Show notification checked

Date and time: Use sent date is checked

Delayed notification: Use delayed notification is checked; delay is 10 (ten) seconds; time accuracy is 500 ms; Move lost messages is checked

Like I said, trying to understand a few things as it relates to my understanding of the app and the settings before I inquire about an "issue"...

THANK YOU for your time!!
[Android Apps and Games] hrk:
I'm sorry to hear your news, I hope everything is now okay! :)

The "Recovered" count is as you thought: the number of message that the stock android app missed and Ghostly recovered (either manually by you or automatically if the corresponding option is enabled when using delayed notifications).

Regarding the "Accuracy" feature, I'll explain it again shortly but first of all a very important note: accuracy is never used when the "Use sent timestamp" is selected. Why? I'll explain it in a bit. I see that you enabled the "Use sent timestamp", are you running CyanogenMod7? I ask because CyanogenMod is the only ROM I know of that allows you to use the "sent timestamp" in its stock messaging app.

Unless you can enable the "sent timestamp" in your stock messaging app, DO NOT ENABLE it in Ghostly, or you'll end up with lots of duplicated messages. Well, at the very least it's better to get duplicates than losing messages, by the way... ;)

Now, when (and only when) delayed notifications are enabled, Ghostly will react in this way when receiving a message:

1. A new message has arrived, save it in the internal DB.

2. Ask Android to wake us up after "Delay (in seconds)"

3. Now that we've been woken up, do we "Use sent timestamp"?

3.1 Yes, then search the IBOX for a message with the same sender, the same message body and the same date.

3.2 No, then search the INBOX for a message with the same sender, the same message body and a date between our date - "Tolerance (in ms)" and our date + "Tolerance (in ms)".

4. If such a message exists in the INBOX, then Android didn't lose it, act accordingly (delete from the internal DB, etc etc). Otherwise, Android missed it. Act accordingly (notification, automatic move, etc etc)

When you select a single message from the list and choose "Adjust time ccuracy" option, Ghostly will search the INBOX for every message with the same sender, the same message body and display them sorted in reverse received order. Delta is the difference between the date in the internal DB and the date of the message.

I hope this information will help you and thank you for having taken your time to understand how Ghostly works. If you have any suggestions on how to make it simpler or clearer, don't hesitate to write them. :)
[Android Apps and Games] monomer888:
I have a quick question about the delta and tolerance - does it work in both positive and negative directions?

First of all thanks so much for your app, I relied on it heavily when I had my Desire Z. Although I haven't lost any SMS on my new device so far, it's nice to have Ghostly around. :-)

Anyway, the question about tolerance is that I've noticed that even if my accuracy is set to 1900ms, I still get some SMS captured by Ghostly suggesting a lower accuracy number. I've attached a screenshot of the 'adjust time accuracy' screen to illustrate this - I think it got caught because the Delta is negative? (I don't have 'Use sent timestamp' checked.)
[Android Apps and Games] hrk:
Yes, both directions, check my previous post for the full explanation of the steps Ghostly performs.

What are your settings for "Delete received messages" and "Move lost messages"?

If "Delete received messages" is UNCHECKED, then Ghostly will keep the message and you'll be able to use the "Adjust tolerance". It's normal for you to keep seeing it.

If it was CHECKED, however, then there must be a bug, because you have 1900ms set where 100ms was enough, and Ghostly should have deleted it.

I see that the message in the window isn't clear enough. It doesn't mean that you should change the accuracy value, it simply states the least minimum value required. So if you have a higher accuracy than the requested one, you don't need to change anything (but you could reduce it if you wished...)
[Android Apps and Games] monomer888:
Thanks for your quick response. Your explanation is partly what prompted me to ask the question. :)

Yes I have 'Delete Received Messages' checked, but have included a screenshot of the settings screen to avoid confusion. I just wanted to add that this 'stray capture' does not happen on every message though, just the occasional few. It's not a big issue though, I'd rather have messages be caught in error than missed by mistake! :)
[Android Apps and Games] Shano56:
So, currently, which is more effective? locking sms in memory or using ghostly sms? It seams logical only to have one, so which one works better? I know locking sms in memory uses much needed ram, how much ram does ghostly use?
[Android Apps and Games] hrk:
I use Ghostly w/ Delayed notifications.

Yep, I didn't pay to enable them.

On the other hand, my hourly dayjob wage * hours spent on Ghostly > cost of a new Galaxy Nexus. ;-)

Ghostly uses RAM only when it receives a message, and only as long as it has finished processing it (which means, w/o delayed notification, less than a second).
[Android Apps and Games] hrk:
What the...?!? It looks like I completely forgot to update the thread with the new release. :)

2012-03-03 - 1.23

- Android 4.0 "IceCreamSandwich" look & feel on older devices too!

And so, 94% of Android devices (2.1+) can experience Ghostly SMS with the look and feel of the remaining 3-4% devices (3.2+).
[Android Apps and Games] xfloggingkylex:
This app is awesome and this bug is completely embarrassing.
[Android Apps and Games] hrk:
GetLocalization.com for translations!

Thanks to GetLocalization.com, translating the app is now easy and doesn't require any technical skill. Their web interface allows you to translate even just parts of the app. Want to see Ghostly SMS in your own language? Now you can. :)

I have been using it for No-frills CPU Control, it's really awesome!
[Android Apps and Games] hrk:
1.24! :)

- Many optimizations in list display and action handling.

- Faster loading of messages (except for the first time after updating the app!)

- No more "Loading data" after deleting or moving a message, list will be updated instantly.

- Automatic refresh of list data.

- Reverted list order ("last received message on top") to match the stock SMS/MMS app.

- New Romanian translation
[Android Apps and Games] WatsonDue:
Can't see any update in market.. :rolleyes:

Forgot to release the 1.24? :p
[Android Apps and Games] hrk:
It looks like Google Play got the file, but lost the description, so no update. Weird, it never happened before. I re-published it, it should become available soon. :) Thanks for reporting!
[Android Apps and Games] WatsonDue:
Now it's ok, thanks. :cool:
[Android Apps and Games] anthonys2r:
Dude I LOVE this app! I couldn't figure out what was wrong, Vibrant with 2.2 base, (with these dropped/missing texts) and ghostly managed to catch most of it! (still had 2 slip through though :( )
[Android Apps and Games] hrk:
Glad to know. How do you know that two slipped, though? Do you use delayed notifications w/ "delete duplicate messages"?

I see no way for Ghostly to lose messages after receiving them, UNLESS it gets killed before saving them in the internal database, but I'm pushing my limits in how to have it as fast as possible. :)
[Android Apps and Games] errandum:
A stupid question (and feel free not to answer it), but how does this work? Is it a service? or do you create an intent.recievemessage (or something like that)?

How do you guarantee your app is always running and receiving messages and not killed by constant swap in/out of Android?

Either way, finally a solution to this problem. I even got to have fights in the past due to this sms problem (failed arrangements, etc) and this is a lifesaver. I was considering trading my Desire for an iPhone 4, so... Thank you!
[Android Apps and Games] hrk:
It registers itself as a Receiver for the SMS_RECEIVED event, which means the app will run only when reveicing a message and will terminate its work as soon as it has saved the message in its internal database.

By not running as a Service, but you surely guessed it after my above reply. :)
[Android Apps and Games] fulloflove:
thanks man. I'm trying this. I'm using a GT540 and the SMS constanly be killed although I had chosen to keep sms app in memory. Try various ROMs and the problem just be decreased but not solved
[Android Apps and Games] anthonys2r:
My friend showed me a screenshot on her phone and it showed that it sent but it never was received by Ghostly... :( I reflashed to ICS and it seems like it's happening slightly more often now... (2 within the past 2 days, once again, friend showed me screenshots)

edit: also I do not use delayed notification, can you explain what is that exactly?
[Android Apps and Games] crawfordmd:
Unable to install Ghostly SMS

Looking for assistance here....I had Ghostly SMS installed on my G2 and a couple days ago it stopped working. I tried fixing the permissions and that didn't work so I figured I would uninstall and reinstall, however, when I went to download from Playstore, it would try and install but stop short with the "Insufficient storage space" error. I thought that was strange since I don't have that many apps and plenty of space on my SD card so I tried downloading a different app from Playstore and the app downloaded/installed without any problems. I also tried to restore the old version of Ghostly SMS with Titanium Backup, but that doesn't work either.

Does anyone have any suggestions?
[Android Apps and Games] hrk:
I have no clue, try asking in Mimicry's thread for help, it may be related to their ICS port. Did you install some other app like ChompSMS, Go! SMS, HandCent SMS or something like that before it stopped working?

(I guess I'll put a check to see if the app such apps are installed, since their f-ing developers don't even reply to emails)

EDIT: I forgot to update the thread for 1.25! Weekends are tough...

2012-07-01 - 1.25

- Android 4.1 Jelly Bean compatibility update.
[Android Apps and Games] crawfordmd:
I had Go SMS installed before I had originally installed Ghostly SMS and there weren't any issues. Hmmm, I will ask the question I'm the Mimicry thread as well to see of anyone else is having issues.
[Android Apps and Games] XVI Ames:
Thanks!

Thank you for this app! I have this problem for decades with my android phone, and I admit it is pretty annoying! With you app, I have sent to myself a flood of sms, the sms app did save 9 out of 25 of them... your app did catch all of them! \o/
[Android Apps and Games] hrk:
\o/ indeed!

What puzzles me the most are people who tell me they don't need the app because they don't lose messages. You can know if you receive a message, you can't know if you lost one! :laugh:
[Android Apps and Games] polobunny:
I used to think this was an issue with my carrier. But then I tried your app since I translated it, and it's amazing in low memory situations. I've saved maybe only 3 messages so far (Nexus S is a decent phone), but it's definitely doing it's job.

I'll have to spend for the "pro" version eventually, that will make it a bit more automated. :)
[Android Apps and Games] WatsonDue:
May i do a little request?

I think could be useful to have a "Go to sms app" button on the bottom of the screen.

Usually when I lose a sms, I restore it with the app and then go in the sms app to reply! :laugh:
[Android Apps and Games] XVI Ames:
In addition to this tremendous app, I have also installed this one:

play google com / store / apps / details ? id = com . evanhe . nhfree

It keeps an history of all the notifications, and order them by app... Advantage: I can see, in the same app, the SMS catched by Ghostly, the return receipts which were only "pop ups", with the date and time, under my SMS/MMS app category, and, I don't know yet, probably other stuff that appear in the notification bar and disapear before I see it... The lost SMS problem, I did see it in LIVE several times: while I was walking or anything else, I saw my phone display a new SMS, and then another... and when I went to the SMS app a few minutes later, only one of the messages was there! I guess Notification history would have catch it, but with Ghostly AND Notification History, I am pretty sure I do not lose any sms !