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?
Related
Hi
I have done the 1-click lagfix that relies on ext2.
I have also installet autokill (the one that changes the internals of the system)
I have 2200 point in qualcom.
STILL I have massive lagg now. It started out well after the rooting, but now its worse than ever. In fact I have even failed to answer a call due to the lagging.
(I have installed Tasker and have 4 tasks set up, i really hope this is not the reason because I would really miss tasker)
I can notice a big differense if I start the dialer and press Home istead of Back. Assuming Back actually kills the process? If I use Home, I can bring it up again in a split second. Using Back and it an take everything from 300 ms to 4000 ms.
I have now started to experiment with Launcher Pro (who some claims to be faster) but this is actuall just a shell and I cannot dedect any differense.
I have tried different presets in autokill, but since this lag is probably not due to lack of memory, i have now set it to "system default".
Is there a way to keep important processes in memory all the time? Like the dialer, contactbook, sms etc? I dont really care if it takes 500 ms longer to start up google maps or facebook, but the PHONE FEATURES must work properly on the phone.
I run a stockrom JM2
hello, as well as the lag fix, I also disabled ui animations and installed autokiller set to strict or optimum and the lag is now minimal for me, it's still there at times but not as bad as you describe.
ironicly i didnt have this problem before lagfix/autokill. It was there so i decided to run the fix (and the qualcom-score is always cool i thought). But now its worse.
Does anyone have experience with tasker as a performance-killer?
I am just curious if anyone else has had a similar issue and if rooting it would resolve my problem. When my phone is "asleep" and I press the unlock button it almost never lights up immediately. Sometimes it will take 5+ seconds to light up before I am able to slide to unlock.
I am not sure if rooting the device and removing/freezing motoblur and all of the other bloatware would make it run better. I for sure want to root it in hopes that the phone will be less laggy. I think the inspire and captivate run smoother which is somewhat disappointing.
anyone else have a similar complaint or a way to fix it?
I had this problem with 1.26.
Flash firmware to stock 1.26, and update to 1.52 and you should be fine.
Rooting will not help.. Could be apps running in the background or widgets, idk.
Any improvement immediately after phone is fully re-booted?
Edit: I just realized you may not have AT&T...
Hey thanks. It is an at&t atrix and is currently running on 4.1.57. I dont think it "wakes" faster after a reboot. Sometimes it wakes right after I click it, but sometimes I can push the button and wait 5-10 seconds... I assumed rooting it and removing all of the garbage would fix the problem haha!
Actually, I would root anyway, so you can remove a lot of that stock Motoblur stuff, and keep it out of memory (by freezing it). It certainly can't hurt, and it might contribute to a speedier overall experience. Replacing the stock launcher definitely helps in that regard. Launcher Pro, and Go Launcher Ex as a close second, make using the phone so much smoother. Also, use the auto-close task list in the task manager, it could help to improve your problem if it's related to having too many things running.
maledyris said:
Actually, I would root anyway, so you can remove a lot of that stock Motoblur stuff, and keep it out of memory (by freezing it). It certainly can't hurt, and it might contribute to a speedier overall experience. Replacing the stock launcher definitely helps in that regard. Launcher Pro, and Go Launcher Ex as a close second, make using the phone so much smoother. Also, use the auto-close task list in the task manager, it could help to improve your problem if it's related to having too many things running.
Click to expand...
Click to collapse
thank you,
I would like to root my phone to remove that stuff. I dont use any of it (especially motoblur.) I am currently using ADW as a launcher. I like some of the things you can change with it. Is Launcher Pro better? I have gone into the stock task manager to "end" applications, but I will take a look at the auto close feature. Maybe I will add everything BUT my widgets to that category. I have 1 widget per page...... Not sure if that is a no, no lol! 5 pages: beautiful widgets (weather,) pandora, double twist, mini stocks, and my power toggles. Should I not have this many widgets? I am running flickie wallpapers so I dont have a live background.... I think beautiful widgets is the only thing really using a great deal of CPU usage (around 5mb) which isnt much.
I have the same problem.
I am rooted on 1.57 and it did not fix my problem.
I was using gingerblur on 1.26 and the problem was still there.
I do not have titanium pro, so I haven't tried freezing motoblur.
if u are using setCPU and undervolt this could be the problem if you leave iddle sometime and wake the cpu could take a little more, try disabling setCPU profile on screen off (if u have it)
Flash the SBF back to 1.26 and see if you have the problem before installing launcher etc... Regardless, I would install gingerblur since it rox.
Same thing on mine, no change between 4.1.26 and 4.1.57. No change between rooted or unrooted. I've just gotten used to it, and it never takes more than 3 or so seconds for me. I hit the button as i'm pulling it out of my pocket, and it's usually on by the time i have it in view.
+1
i actually notice the same thing
currently on rooted 4.1.57
the lock screen wake up time seems slow...
its funny cause the exact same problem occurs on custom ROMs on the HD2 but I thought a real stock android device wouldnt have this problem...
it's a little bit annoying for me, but im slowly getting used to it. Although i would love for it to be fixed cause I've seen the unlock screens on the Nexus S and Galaxy S and they come on instantly when you push the power button
Remove the Bloat
What would you suggest removing, and is it just an uninstall?
I have it rooted, just dont know what I should uninstall or remove.
Thanks
A few days ago i noticed some not so smooth scrolling when in my calls log. So i thought the phone had been on too long and did a reboot (which solved the scroll lag).
After the boot. I went into the menu and most of my apps had disappeared (i think mainly on my sd). After a minute or two they appeared (out of order and all on the last menu ) so im guessing it was the sd card (which is the standard class 2 i think which came with the phone) My sd has like 12gb free still. And i only have like 25 apps/games. Anybody noticed similar things? And would upgrading my sd to a higher class slove the prob?
I also noticed that when my phone is on standby and i open the game pad without unlocking the phone (takes 20 secs maybe to launch) then press the back or home button. The 4 quick links next to the menu icon have no icons just blank sqaures for a 10 seconds or so. The same if i open the menu a few icons are the blank ones then they appear. Is this the same for other people?
I never noticed this problem before. And its bugging me. The phone is not rooted, uses the standard wallpaper. And only i have google search on the main screen no widgets. Any suggestions? Im gonna try a reset but thought i would see if other people had any similar experiences. Any help/suggestions would be appreciated
What you are probably seeing here is Android's garbage collection system in place. Basically, when apps need memory, the OS will transparently kill apps that aren't in use without telling you. Generally, the user shouldn't really notice it... but things like your apps not all showing right away is normal when the home app is starting back up after having been killed previously. Things that are relatively resource intensive, such as the Playstation emulator built into the Xperia Play, will most likely cause all other apps that are non-essential to be killed.
I don't know if you've used other Android phones before, but it's pretty normal.
Yeah this is my first android phone . Suppose if its pretty normal i will get used to it in time. Maybe i will unroot the phone and remove all the crap and see if that makes it any better. Thanks for the reply btw
Mozza2k11 said:
Yeah this is my first android phone . Suppose if its pretty normal i will get used to it in time. Maybe i will unroot the phone and remove all the crap and see if that makes it any better. Thanks for the reply btw
Click to expand...
Click to collapse
what launcher are you using? if you use launcher pro, there is a "system persistant option" this means it will not kill your launcher in the background, and the apps disapearing issue should not happen
AndroHero said:
what launcher are you using? if you use launcher pro, there is a "system persistant option" this means it will not kill your launcher in the background, and the apps disapearing issue should not happen
Click to expand...
Click to collapse
Im just using the standard play UI. Thinking of trying Launcher Pro or GO Launcher EX. If i unlock my phone before opening the game pad the icons are there. Also if i give my phone 20-30 secs after rebooting my apps are where i left them. So i guess i need to have more patience lol
Does anybody else have problems with the launcher reloading? I have this problem with both the stock launcher and Apex. I still have this problem even after locking Apex into memory. Any remedies for this?
Thanks!
I do. Not sure how to fix it to be honest. I've tried many roms.
Im using nova and have this problem. I even have agressive checked (stay in memory)
Also tried the build prop edit. Neither worked
Would love to have a sure fire way to keep the launcher in memory
Still looking for a solution to this problem..
Supercharger v6
Google it
Does "Pimp My ROM" work on the Nexus 10? You could always lock the launcher in memory.
Good question, I stay away from pimp my room cause I know it causes issues in Roms sometimes
EniGmA1987 said:
Does "Pimp My ROM" work on the Nexus 10? You could always lock the launcher in memory.
Click to expand...
Click to collapse
Locking the launcher in memory doesn't stop the launcher from reloading in my experience.
Isnt the definition of "redrawing" meaning it has to be reloaded because the app was no longer in memory?
Still, if whatever is being used to lock an app in memory does not work then you can always renice the process to put it into the range where the Android OOM manager knows it shouldnt be killed off. I like setting my launcher to have a priority of -17 and my keyboard with a priority of -20. Other systemUI I usually give -15, and (on my phone at least) I have the phone as -19 and google voice as -18. This means that the keyboard is always the most responsive thing there is so no matter what is going on the keyboard never lags when typing. Next is phone so that when a call comes in it doesnt load all laggy like. Google Voice is my texting app and also has to do with the phone so that also gets a high priority. Then the launcher and user interface are also high so their transitions and such always get priority over other things going on in the background. This keeps everything about them smooth since it is unaffected by other background tasks. The smoothness of the system stuff is the primary benefit, but having these values also tells the system they have so high of a priority that they should not be killed off ever when more RAM is needed and other things should be killed instead.
Other things you can do is to set the package installer to be a really low priority so it gets killed as soon as it is no longer actively doing something and also so that installing or updating in the background doesnt completely lag up the system when it starts writing data to disk.
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.