Hi there, on my second vibrant. I'm having some issues with this one and I need help determining if they are hardware related.
I'm running 3 homescreens with:
Beautiful widgets
Pure messenger widget
Switch pro
Pandora
I'm also running launcher pro.
I have some major lag problems when launching apps. It takes a minute or so to open most apps, plus I get a lot of black screens. I've factory reset the phone twice and the issues go away for a while on stock settings but the phone starts to lag a bit as I load apps.
Any ideas?
I might just return it....even though the phone runs ok on stock settings, might have a hard time returning it.
Sent from my SGH-T959 using XDA App
most likely software.. and related to one of the apps you have dl'd. as you said in your post, the phone works fine stock and doesnt start to act up until you load apps.
i would suggest you just install your apps one by one and have a small testing phase between each one. then when it starts lagging you will know what app to avoid.
Wait did this happen on both phones. Even if not, still sounds like something you've done to the phone. I would root and run autostarts to prevent certain items from opening. It's all in the sticky if you want to try.
Its both, look into the lag fix. Launcherpro + all widgets are running off the internal sd along with the appdata (thats moved in the lag fix) and with the poor performing I/O of the internal sd, it lags. The stock launcher + samsung apps is built into the system dir (internal nand) so doesn't lag as bad.
No, I returned the first phone because the homekey wasn't working.
Once the apps do manage to load, I notice that there isn't anything I can do to slow the phone down. Certainly seems more and more like a software bug...Maybe Launcher Pro isn't playing nice (even though I've reinstalled it a few times, and after factory reset). That or the Pure Messenger widget (scrollable) is what's screwing everything up. It worked fine on my Mytouch 3gs though...We'll see.
I'll add apps one by one until I find the culprit.
OK, thus far installed ADW instead of Launcher Pro...
Everything seems to work really well thus far. ADW seems to handle scrollable pure messenger widget much better than Launcher Pro. I think that was the source of my incredible lag.
Still testing, but has anyone else had issues with the scrollable pure messenger widget and Launcher Pro?
LCD Density is the single best thing i've changed on my phone. Cannot live without it. Default is 240 and I have mine set to 200.
All apps work great except for the native Samsung apps. It looks like all the native Samsung developed apps are hard coded in terms of dimensions, while everything else scales nicely.
Is there a work around to make Samsung native apps play nicely?
This works with some apps but not all.. but it is worth a shot.
DL Spare Parts from the market
Turn off Compatibility mode. That got a few things to resize themselves appropriately for me.
you talking about the DPI setting? I run at 184. Be sure to do something divisible by 8 if you want your icons to resize right.
Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?
Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?
Set dpi to 240, install apps and then set dpi back to desired custom dpi
For me it happens also with old market app.
Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App
App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)
Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.
I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.
doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)
You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.
Thanks for the heads-up - I had no idea it would have been from the DPI setting.
It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck
Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.
thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!
Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100
I set my DPI to 200 or something like that, and something kept crashing over and over again (com.android.keyguard) so I could not even use my phone. Also would not connect to the computer in order to fix it. So I forced a factory reset. I am using nova launcher, and someone in a similar thread had said it can go as low as they like with Nova? Not my experience... Ran into this problem before a couple years ago on my Note 8.0 also but never bothered asking about it.
Is the lowest stable setting known?
I personally use 387, as its on the list. 213 is the closest to 200 on the list with 164 being the closest in the high 100s.
640,430,387,286,242,234,213,164,157,145,135(listed twice),075,064
Widgets Freeze
Hi. I have noticed that widgets do not work properly on my brand new Moto X Play. You can add a widget, but it appears frozen and the content does not update or allow interaction. If you modify the widget size, it will stretch the image of the widget, again failing to update the widget. Depending on the widget, it will bring you to the app of you tap on it, but sometimes even that does not work. Deleting and replacing widgets makes no difference. Using Nova launcher appears to fix the issue, although I have not tested this for a period as long as an hour yet.
This seems to be a widespread issue across many phones, including Samsung and Nexus phones, thus is appears to be an Android issue more than a specific Moto issue or a hardware issue. It is possible it is a Google Now Launcher issue specifically.
Is anyone else experiencing this issue or know of a fix? I have yet to find one other than rebooting every hour or so (or possibly switching launchers). The leading theory is that the widget process is being kicked out of memory. The scary thing is that this bug has been reported as far back as Android 4.3, although I never experienced it on my SGS3 with CM11.
Thanks
Have not had any widget issues but have been using Nova launcher. All seem to work fine for me
Nova Launcher continues to solve the problem for me as well.
It is pretty disappointing that a major feature of stock Android fails to work out-of-the-box. I like Nova Launcher, so that is fine, but I shouldn't need 3rd party launchers to recover stock functionality. Hopefully my case is exception and not the rule.
Are you moving the apps to your SD card?