Related
Hi,
I noticed that OS constantly unloads my applications.
Say, I visit some page using IE, then switch to another application, then switch back - it is usually at the same page, but, probably depending on idle time, it sporadically gets closed.
That said, when I go to IE again, it starts afresh on its initial page and I must reload my page again. Needless to say, in most cases this is unacceptable. (extra traffic, so it costs $$, also GPRS could become unavailable etc :x )
How do I PREVENT this behaviour?
Not only IE suffers, any application! Sporadically exits despite of fact there are tons of free memory and I would better free resources with another way than just closing what is required for me.
I have elder device with PocketPC 3.0 (Cassiopeia E-125) and it does NOT behave in such a way. Does not close even it has 4times less memory! Now I understand how nice it is.
While this problem persists, I forced to have both devices with me.
Please help me solving this!
Vadim.
I've noticed the same behavior randomly also. I don't have a fix, but you're not alone.
What ROM version are you using? There was an issue with the earlier ROMS in that there were too many programs running and when you launched another program the OS would terminate a background program to provide the necesssary process space.
The newer ROMs have solved this problem, but CheckNotify and ClearNotify (search the forum) will help with the earlier ROMs.
This is an old problem, related to the number of running processes.
Consult this thread
http://www.ppcw.net/?itemid=1645
which will show you how to solve it. Also the newer roms cut down on the number of processes at startup, which helps.
Surur
Mine is much more random than that described. Sometimes I can have a half dozen apps open with no problem, and sometimes a single app will close itself while I work in the phone or the Today screen.
Carlos said:
Mine is much more random than that described. Sometimes I can have a half dozen apps open with no problem, and sometimes a single app will close itself while I work in the phone or the Today screen.
Click to expand...
Click to collapse
Don't forget that we are talking processes, not appications, here. One app. may have many processes and multiple app's may use the same common processes. Therefore, launching one application can generate a number of new processes and that can push you over the limit (e.g. ActiveSync, which launches three or four I recall), so something gets nuked.
I understand, and was looking for a pattern, but there is none. In fact, it seems reversed, as it happens more often while I'm just out and about and less frequenty while the device is in the cradle. Very often it happens after a fresh boot with a single app running.
I may look at it more closely with a process viewer. It's not bugging me enough to make it a priority.
Thank you all for providing many help!
surur said:
This is an old problem, related to the number of running processes.
Consult this thread
http://www.ppcw.net/?itemid=1645
which will show you how to solve it. Also the newer roms cut down on the number of processes at startup, which helps.
Click to expand...
Click to collapse
That explains it all, many fruitful comments, and a prove that there could be no fix but just temporary solutions to reduce a problem a bit.
It is a bit larger problem in my case, because I use special sotware to support Russian.
Too bad MS can't recognize and fix such a big design mistakes.
Does anyone else have this problem? Talk is showing the conversations above my writing, not in time order! How do I change this?
http://db.tt/W5wIoG5
this is weird...
instead of the messages being like in a chat, all his are on top and all mine are on the bottom
I was just about to post about the same issue. I thought the design of gtalk was made like this on purpose until a colleague of mine showed his not doing this.
I've tested to force gtalk to forget all data, but it has not helped. It has virtually made gtalk unusable, as after talking to someone for a few minutes/half an hour, I have to scroll pages up to view what the person responds with. Records so far is that I have to scroll four full length (portrait mode) pages to get to the text to the person I am conversing with.
I have the same problem but thought this was normal until being brought up in this thread
Solved!
The reason was for some unknown reason, it had not applied summer time (BST, for me) so I was running base clock on the device an hour wrong so it showed the correct time.
I went into settings for the date & time and re-selected "London" (was already selected) and suddenly it applied BST correctly. Then just adjust the clock so it shows the correct time and voila, it works again.
Me and my colleague just tested it out and my gtalk has turned from "useless" to "wonderful" in just a configuration change
thanks!
Hi all,
Lately I've been having one hell of a headache because browsing on one network of mine is painfully slow. So much so it's not even worth trying.
It goes like this: Google.com and usually Google search results load instantly. No problem. Then anything beyond that (loading a result or manually inputting a URL) takes FOREVER and usually results in only the top of the page loading with the completion bar stuck on around 75%. Refreshing, clearing cache, etc. etc. made no difference.
It's def not a problem with the network - no other devices suffer and speed tests show no real slowdown.
I Googled a fair bit and found a couple of posts on other forums where people had the same problems with rooted devices. Someone suggested disabling AdFree and giving it ago. THIS FIXED IT! Disabling AdFree, for whatever reason, caused the slowdowns and partial loading of webpages to stop completely.
So my question is - why? As far as I'm aware AdFree just overwrites your HOSTS file with one which redirects ad servers back to 127.0.0.1, something we've all being doing on our PCs for years. It appears that this loopback to localhost is stopping nearly all of the rest of the webpage - everything bar the very top in many cases, possibly because that loads before the first 127.0.0.1 loopback.
So why does this happen under Android, or under certain Android builds? I'm using NexusHD2 based on Gingerbread 2.3.4.
Since reverting back to a clean hosts file, I've got no problem with browsing. Switching AdFree's host file back on causes the problem to return.
Bump!
Sent from my HTC HD2 (Android)
Here is the thing. In the 90% of cases, when I'm using my X8 to do other things, such as, I don't know, using the browser, or whatsapp, or tapatalk, if I receive a new sms the window notification and the status bar notification don't appear. I can see if there is a new sms only if I enter manually into the sms application, and sometimes I find that there is a new one many hours later because I don't usually open the application The funny thing is that sometimes the notification doesn't appear even if I'm not using the phone!
On the other hand, when the sms window decides to show up, if I try to answer through the quick reply and I tap on the "send" button, the message is not sent and if I enter manually into the application, it stays like forever into "sending" and the only way to actually send it is to delete the quick reply and re-write the sms. This thing drives me crazy I think it depends on the ram of the phone, but I tried Go sms and Handcent sms, and many roms but this thing is always there!
What can I do?
I have the same problem, but only when my X8 is showing the "low memory" warning in the notification bar. When it first happened I went looking for an answer, but the closest I came was a FAQ response on the Vodafone (Portugal) site, which confirmed that it's not possible to send/receive SMS when the X8 memory is low.
I never did figure out though, whether or not this is due to operator modifications to the phone, or it's a generic problem with Android 2.1. From your comments it looks like it may well be an Android limitation...
I eventually "solved" my problem by rooting my phone and installing Link2SD - probably the single most important reason for rooting an X8 At one point in time, after pushing everything I could to my SD card, I ended up with almost 100Mb of free space...and then I discovered certain things, such as widgets, don't like to be stored on an SD card lol.
What can I do?
Click to expand...
Click to collapse
I guess the only thing you can do is ensure you always have at least 20-25Mb of free memory (I think that's about the point that the low memory warning appears).
Hi,
I am using W8 and i have lots of mem free on my phone, however i still face the problem. Any idea?
Well but I don't think that using only Whatsapp will bring to a "low memory" status... I mean, sometimes I only turn on the phone and do nothing, and the notification still doesn't appear -.-'
I don't know about the W8, but the "low memory" = "no sms" problem is well known and documented, at least Android 2.1 and 2.2. Here is a link to a bug report first files in November 2009!! about the issue. It's also still actively receiving comments...
Issue 4991: Can not receive SMS when internal memory is low.
http: //code.google.com/p/android/issues/detail?id=4991
One of the most interesting posts (if you spend the time to look) is probably this one:
Comment 272 by [email protected], Aug 30, 2011
@Anyone blaming phone manufacturers:
Take a look at this code (which is STILL current), common to all Android phones (from the GSM section, the CDMA version is almost identical):
Code:
134 if (!mStorageAvailable && (sms.getMessageClass() != MessageClass.CLASS_0)) {
135 // It's a storable message and there's no storage available. Bail.
136 // (See TS 23.038 for a description of class 0 messages.)
137 return Intents.RESULT_SMS_OUT_OF_MEMORY;
138 }
Then the message is *destroyed*, and apps are notified that an SMS was rejected.
The worst part is that this function doesn't even store the message. It just passes it on to the Messaging App! The whole point of having a flexible framework is that the App can do whatever it wants with the message. Who said it was even going to store it? The App could put it on the SD card, or ask the user to clear space if that is also full. Maybe it just needs to be shown once, or maybe it is a "where is my stolen phone" that must be silently responded to and hidden from a thief. Checking storage before it has even been established that the message is MEANT to be stored is astoundingly stupid. It goes against the philosophy of an open framework, and it goes against various design principles (such as leaving the responsibility of checking storage with the code that ACTUALLY STORES SOMETHING).
Whoever wrote this just wasn't thinking. They did so well at not thinking, that they went to the trouble of adding mStorageAvailable to the base class, subscribing to any updates on the storage status of the phone, and then set up a status handler that INFORMS THE CELLULAR RADIO that storage is full, implying that there is no point even informing the phone software about any messages. Thank science that the radio is smart enough to ignore this, or you wouldn't even get a "storage full" notification when the message is rejected.
Was there no code review?
The fix is simple. Delete those five lines. Remove the line that informs the radio about low storage. Six lines and the phone will function properly as a phone. Remove another few lines and there are no longer any references to low storage at all, as there never should have been in the first place.
The question is this: WHY has not not been done yet? It is not a difficult fix. A first year IT student could do it. The changes are simple. The effects are simple. Testing it is simple. It will make a fundamental phone function far more robust. Every second that this is still in the code, it seems more and more like the Android project doesn't actually care about having a working phone.
You simply can't blame the phone manufacturers. Earlier android versions considered 10% storage to be "low". For a phone with 8GB storage, that would mean rejecting a single SMS message when there is 800MB free. They shouldn't even reject it when there is 1MB or even 0MB free for reasons outlined above.
tldr; The code is stupid, the fix is trivial, Google doesn't care.
Click to expand...
Click to collapse
A little further down is suggested workaround (note I have not tried this, and do not recommend it unless you really know what you are doing
Comment 274 by [email protected], Sep 8, 2011
A "workaround" for this is reducing the threshold for the low space warnings.
Code:
Get into adb shell and type:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
insert into secure (name, value) VALUES('sys_storage_threshold_percentage','5');
.quit
This changes the threshold from the original 10% to 5%.
However, this doesn't prevent messages to be deleted when the new threshold is reached.
Click to expand...
Click to collapse
HTH.
You think it may depend on the number of saved messages too? Because the phone has not always done that, and now I have more than 5000 saved messages...
What ROM are you using?
I just tried to replicate the "low memory" == "no SMS" problem on GingerDX v022 by forcefully "spamming" the phone into low memory (17MB internal memory free after I installed some very Angry Birds to knock over some memory cells).
~90 saved SMS (received/sent) in the Messaging app ...
Sent a SMS from my Samsung to the X8 and the notification showed up perfectly - even LauncherPro is showing the (1) count on the SMS/MMS icon in the dock.
I'm using GingerCyborg. The thing it that I always receive the sms (in fact, if I use launcher pro it always shows me the (1) count on the dock), but the notification or the window showing the text message don't appear. So, I receive the sms, but I won't know it until I open the application!
Weird ... I get the Notification sound, the Notification icon in the status bar, the notification itself (pulling down status bar) AND the count-icon on LauncherPro's dock icon.
Installed one more app to make Android crap its pants (we're down to 9MB now), started gReader and had it sit there like that while sending another test SMS ... notification, as described above, still works - though Android is now complaining like crazy about "LOW MEMORY"
EDIT: Read - even when gReader is running I still hear the sound and see the SMS icon in the status bar, so there's no way I would miss out on it.
I don't know what to think, the phone has not always done that, and I tried different roms... Maybe I have the SD full of useless files? I don't know
If you assume the problem is due to your high amount of collected SMS messages ... try this ...
I take your phone is linked to some Google Account. Download SMS Backup+ and back up your messages into your Gmail account (so you can restore them when need be).
EDIT: Now stop auto-sync of your phone with Google or temporarily disconnect from the internet.
Delete a few thousand messages and try.
If the notification starts to work as expected you found the problem ... your SMS storage is "too massive" for the poor Messaging app.
If it still doesn't work clear them all out.
If it still doesn't work ... well ... I can only tell you that I don't have the problem you describe on GingerDX v022 (Stock Kernel) even when the internal storage is low on memory.
On a second thought: Maybe it's an app you installed that causes the "misbehaviour"? I don't use Whatsapp ... I only got XDA (Free version) installed (if we need something that's 'Tapatalk' at its core).
I deleted a few hundreds of sms and now the notification appears but not always. It still has the problem (but I still have a LOT of saved messages). Maybe I'll try by deleting all.
So, lets make a list of issues with this release:
1. Wifi from time to time crashes when enabling it, for example when you try to enable wifi it goes into "limbo state" where you cannot disable or enable it again.
2. Shazam/soundhound cannot identify songs if you play them from integrated music player.
3. The 3rd one is most hardest to explain, basically if application crashes "home" button does not work (in gingerbread it always worked), so you have to wait app to respond or wait about 30 seconds for android message, that application hung.
I'm seriously thining about returning back to gingerbread due to these issues, although battery usage is nice and gps work really impressive, but this release is very buggy
read the stickies - you know...the giant one right at the top of the screen that says
*******DO NOT Start any more New Threads on ICS*******
http://forum.xda-developers.com/showthread.php?t=1544657
I dont care what it says, its not related to that topic anyway, I'm sure I'm not only one who has issues with this release and I think it would be a great idea to keep all issues in one forum thread instead on many threads in this forum.
I'll add an issue too: it has Touchwiz.
Exchange battery bug drain!
Before stating any issue at all, one should state whether or not they did a full wipe/factory reset, if you didn't, the problem is not the firmware, but the owner of the phone.
Of the three issues stated by the opening poster, I only have one, which is the lengthy wait if an app force closes, the other two are not firmware bugs, they are user bugs.
Sent from my GT-I9100 using Tapatalk
If you are interested, I have wiped my phone before installing this release.
Iskorptix said:
I'm seriously thining about returning back to gingerbread due to these issues, although battery usage is nice and gps work really impressive, but this release is very buggy
Click to expand...
Click to collapse
Agree with you there, just gone bag to GB as I am off on hols this week and can do without any hiccups for now.
Iskorptix said:
If you are interested, I have wiped my phone before installing this release.
Click to expand...
Click to collapse
Do it after installing on stock kernel to be 100% sure
except for the occasional force close, I have zero issues (three so far, twice was gmail and lastly the PGA Tour App)
And I did test both Soundhound and Shazam while playing music, identified songs in less than 10 seconds
first of all, i did a full wipe before and after flashing, have no mods installed, just a bunch of apps.
for me, the biggest problem right now is email with social hub. in gingerbread, when i opened the social hub it was in the state i left it, mostly the email accounts overview, now it always starts on feeds, and when you click messages, it shows all accounts' combined inbox and it seems kinda buggy, because the number of new emails never match. notifications show 3 new emails, the social hub says there is 5 and upon opening, it looks like there is only one, because the combined inbox just does not work properly.
also, i set it to display the next message, once i deleted one, but no, it goes back to the ridiculous overview. and within an email there is no next message and previous message buttons anymore, they are only present in the email app, which, incidentally, looks like the social hub, but has completely different buttons, whereas on gingerbread, it was exactly the same (only that the social hub also has facebook and twitter, which is why i use it, to combine all messages in one place, at least if it works).
another bug i already posted in the release thread (but of course it was lost in between all the noob posts, "halp, mai pohne brokez") is that many menu items are way too long and disappear to the right, see attached screenshot. there are settings with checkboxes, and you can't even read, what you just activated/deactivated.
samsung should either make small blue explanations underneath or let those lines scroll through to reveal the right part.
also, after rooting, i could not restore my titanium backup, so i set it all up manually and even then, google play apps that install to the sd card by default, didn't work.
Solution: flashing back stock kernel. another piece of important information, completely lost in the release thread.
i never bothered before, because with the old bootloader and if you bring your device into bootloader mode using the jig, you never have a yellow triangle. (yes, even if you root your device and NOT use the jig afterwards, no yellow triangle).
the following might be specific to my device and not apply to yours, so it does not count as a bug:
when i bought the phone in june '11, it came with ke2 i believe, and it got incredibly hot while playing 3d games (gameloft etc.). non of the roms that came after that had that problem until la2, which also had incredibly poor battery life.
now, lpq has great battery life and does not really get hot, but once you play, while charging your phone, it gets as hot, as it never has before. yesterday, after 30 minutes of osmos hd, i couldn't continue, as my fingers hurt, touching the display and the phone's backside. on battery, i can play for hours without any temparature change.
(if anyone can confirm this, i'd be glad)
oh and before i forget:
@leftovermagic and the others posting while i write this:
the point of that sticky is to stop noobs from creating a new thread with the same topic, which is "lpq released". this is a bug collection and just like the "my first impressions" thread it is something different from the release message. as stated above, reported bugs get totally lost in that thread with hundreds of people too stupid to flash the rom in the first place.
if this thread were to be kept clean from comments and just be a collection of bug reports, it would be useful, general whining is not.
EDIT: oops, forgot the screenshot.
For me the big problem is that some games black screen after 1 minute playing, especially many gameloft games..
Not compatible with ICS yet?
Guys, to keep information somewhat organized and to respect lufc's sticky to not create anymore ICS threads, please discuss issues in one of these 2 existing threads:
http://forum.xda-developers.com/showthread.php?t=1544487 (preferable)
http://forum.xda-developers.com/showthread.php?t=1544557
This makes searching and keeping up with things much simpler.