Related
My application launcher force closes on a fairly regular basis these days. This is a non-rooted phone and see my earlier post for a list of about 90% of the apps I have installed. Afaik I don't have anything out of the ordinary.
Basically the launcher seems to crash more often when I'm opening a folder or trying to move a widget. The thing is, once it restarts, I can then do that action with no issues, and often can't reproduce the problem for quite a few minutes. It feels like it's a memory-leak or something. I tried removing some of my folders and seeing if just having less shortcuts loaded would help, and the results seem inconclusive. I still get crashes, but maybe not quite as often. I also tried going through each of my three toggle widgets to make sure they weren't the cause.
I'm sure other people have run into this on Android, but I haven't seen a lot of screaming about it on this forum, so is it just something people have learned to work around? Is there an established way to figure out what's causing it? I apologize is this is a really common issue, but this is my first android phone and I'm starting to wonder if I'm alone in this.
(I'm using the following widgets: touchdown email, touchdown calendar, RTM, Pandora, Beyondpod, google weather/news, 2 folders with about 5 shortcuts each, probably about 5-6 spaces open across all home screens)
I've had this issue as well. I can reproduce it, but the circumstances under which it happens would rarely come up. I move widgets and shortcuts around, after 20-30 moves, I'll get a crash when pressing on something to move it. Leads me to think its just getting overloaded.
On the other hand, when I first got my N1, something went wrong with it, force closes would happen every 10-60 second for some reason. Regardless, using Home++, I rarely get any issues.
Its a system bug. Discussed in a few threads.
+1 for Home++.
Its a good idea to remove all your widgets from Launcher, coz it still runs under Home++ and starts all the widgets even if they are not active on home++.
I have reflashed the phone about three times with the stock rom and now have moved to custom ones which seem to be working a little better, but I am honestly getting annoyed with how much this phone freezes while in the text window. I have to do a battery pull every time because none of the hard buttons respond either. I have seen many posts and was wondering if anyone has found a fix to this. I might, however, have a bad phone. I did not but it from T-mobile, so if I brought it in to them would they even be able to replace it or how do I go about doing that?
otter5 said:
I have reflashed the phone about three times with the stock rom and now have moved to custom ones which seem to be working a little better, but I am honestly getting annoyed with how much this phone freezes while in the text window. I have to do a battery pull every time because none of the hard buttons respond either. I have seen many posts and was wondering if anyone has found a fix to this. I might, however, have a bad phone. I did not but it from T-mobile, so if I brought it in to them would they even be able to replace it or how do I go about doing that?
Click to expand...
Click to collapse
The SMS freezing issue is widespread in this phone, I honestly don't think you have a bad piece of hardware.
One of the solutions that seems to work most frequently is to keep the number of text messages retained in your phone down to an absolute minimum (like 50 or less) at all times. Clearing them out regularly (and from the deleted folder as well) seems to have eliminated the issue for a bunch of people. If it's critical for you to retain messages longer than that would allow, I'd suggest just backing your messages up with myphone or something similar that allows you to access them off the phone.
I know that's not an ideal solution, but it seems to work. That's the strategy I use all the time, and I've never once had the sms lagging or lockup issues that so many others report.
I've been deleting all my texts as soon as they get over 20 just to minimalize the problem, everything else will start lagging as well if I let this happen. Thanks though. I hope they get a fix for this because I love this phone.
I was haVing the same issues but not as bad as you...you can also try changing the messages too standard not threaded. you can do that by selecting all messages then menu then options...also try running titanium. go to settings/all settings then select windows default I trash mine like that for a while. but what seems to have fixed my problems was just un installing cookies home tab...I mentioned to sirphunkee that in a few days I would install cookies again to see if my problems came back.
I think this MIGHT help you id the problem.
See if removing the memory card helps.
My first unit seemed as bad as yours, if not worse.
Whenever I removed the memory card, it would run SUPER smooth, so I thought to myself, maybe a higher class sdhc would do the trick?
Nope.
There is just something defective about all the TMOUS HD2s...they just fail imho.
toreone said:
I was haVing the same issues but not as bad as you...you can also try changing the messages too standard not threaded. you can do that by selecting all messages then menu then options...also try running titanium. go to settings/all settings then select windows default I trash mine like that for a while. but what seems to have fixed my problems was just un installing cookies home tab...I mentioned to sirphunkee that in a few days I would install cookies again to see if my problems came back.
Click to expand...
Click to collapse
I unthreaded it and have not had a problem all day. Thank you
[SOLVED]
I recently updated to 3.1 on my Iconia, and it seems like when I click the clock/network menu in the toolbar and then exit that to the home screen, the tablet hangs for about a second until it responds. Did something go wrong during the update? I can confirm that I do not have a lot running in the background.
I just tried a factory reset and am applying the update that way. I have a feeling that the rooting I did before the update may have been the cause. I'll report my findings.
Edit: I did the factory reset and things appeared to be snappier than before. Then I was asked to do a smaller update, and upon rebooting, I experienced the same slowness as before. Very strange!
Without knowing what applications you had installed or widgets you had running on your screens, it's impossible to point fingers at anything.
While it is possible that something may have gone wrong with the update, if that was the case it usually leads to a catastrophic failure. Normally the update installs fine, it justy ruins the experience by way of improper coding/handling.
With 3.1, being a (albeit relatively speaking) big update, (read: not major) it could just be that you had an app or widget that wasn't handling the environment very well to begin with and after the update, it got worse.
However, I will admit, the homescreen seem do get refreshed (out of an app) far too often - that is to say - when you leave an intensive application (one with hooks into many resources) and land back at the homescreen, all those widgets etc that may have had their UI's unloaded, now have to restart/refresh.
gammaRascal said:
Without knowing what applications you had installed or widgets you had running on your screens, it's impossible to point fingers at anything.
While it is possible that something may have gone wrong with the update, if that was the case it usually leads to a catastrophic failure. Normally the update installs fine, it justy ruins the experience by way of improper coding/handling.
With 3.1, being a (albeit relatively speaking) big update, (read: not major) it could just be that you had an app or widget that wasn't handling the environment very well to begin with and after the update, it got worse.
However, I will admit, the homescreen seem do get refreshed (out of an app) far too often - that is to say - when you leave an intensive application (one with hooks into many resources) and land back at the homescreen, all those widgets etc that may have had their UI's unloaded, now have to restart/refresh.
Click to expand...
Click to collapse
Yeah, there's no telling. I didn't have a lot of info on, so I just did a system restore and things are super snappy again.
Another strange discovery: it seems that the tablet is more responsive in a certain landscape position as opposed to the portrait view. Also very strange.
It's always been like that.
gammaRascal said:
It's always been like that.
Click to expand...
Click to collapse
Ah ok, sorry I didn't pick that up earlier. Thank you for your help!
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.
Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*
Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.
Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.
I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.
blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk
Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.
I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.
i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150
The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.
schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol
A weird thing has been happening to my S5 since I got it, both before and after rooting. For some reason, not all widgets want to stick to my homescreen in the stock Samsung launcher. When I first got the phone, they all worked, as far as I could tell (I didn't investigate fully at the time, since I had no reason to suspect that they wouldn't work). After a little while, though, I found that I couldn't make Beautiful Widgets widgets stick. I long-pressed the homescreen, chose BW, selected a widget style/size, and customized it in the BW menu, just like it's supposed to work. But no widget appeared on the homescreen. What was weirder was that in the BW app itself, it listed my widget as working, even though it obviously wasn't. Uninstalling/reinstalling the app did nothing but clear the "existing" widget I had created from the list within the app interface.
At first, I thought this problem was limited to BW, so I just got rid of it and decided to jump to another app, but then I found that HD widgets didn't work, and another similar clock/weather-style widget group wouldn't work. Thinking maybe I had created some sort of data corruption, I did a factory reset, which worked for a while, but eventually the widgets stopped working again. After rooting, and finding that the problem still existed, I factory reset again, and started putting my apps back on one at a time, testing to see if it was a conflicting app causing the problem. No luck. The widgets worked until some random time when they simply no longer would.
I finally resolved to go without this kind of widget, since it wasn't a necessity, just a convenience. The problem is that I've now noticed that other kinds of widgets aren't working, either, including some that I'd really like to have work, like the Tasker timer widget.
Has anyone else noticed this problem occurring on their Verizon S5s? I'm going to look into which widgets actually still work (because some do), and which don't, and compile a spreadsheet, see if I can come up with a reason. I doubt I'll be successful, but it might be useful for other people who actually know how to fix things.
PS. Another weird thing is that the widgets stick to Nova Launcher homescreens just fine. Now, that would be okay, except that I want to do some theming now that we can flash some ROMs, and I thought that theming only applies to the stock launcher. Plus, I'm guessing that this isn't normal behavior and I do want to find out why it's happening, not just use a workaround.
After some more digging, I've found that, with only a few exceptions, the widgets that require some sort of customization before placement on the homescreen are the ones that don't work. All widgets that are simply "click-and-drop" work fine. But, if I click a widget and it opens up a configuration page, 9 times out 10 no widget will appear on the homescreen after the configuration.
It doesn't seem to matter what size the widget is, whether the widget's app is stock or third-party, or if it is solo on the widget page or part of a group of widgets from the same app.
Plus, there are some exceptions to this, such as Google Play widgets, Mint, and Email Me Pro. Others work sometimes, depending on what configuration you apply to the widget. For example, the stock Picture Frame widget works when you shuffle the pictures, and doesn't when you choose where to draw pictures from.
Very strange. I'm thinking my only course of action might be to go nuclear and flash a completely different stock image onto my phone through Odin. I downloaded one from this post: http://forum.xda-developers.com/showpost.php?p=53437805&postcount=1289. If I'm correct, this tar image should be exactly the same as the one that was on my phone from the factory, presumably minus whatever problem mine currently has. We'll see how it goes, I guess.
Okay, so flashed the tar image through Odin, reloaded some stuff without rooting (yet), and everything seems to be going fine so far. I'm pretty sure that by this point in my previous experiment, the widgets had stopped working. I think it must have been some sort of corrupted file deep inside my system that isn't there now.