Related
Hello, I've been running xboarder56's rooted GB OTA (not the tweaked one) for about 2 months now with almost no problems. However, my phone slows down and starts getting laggy to the point of being unusable after a day or two, and the frequency seems to be increasing. I don't run many background services. Only rebooting fixes the problem temporarily. I'll try to load a webpage on either opera mobile or the stock browser while listening to music and the music starts skipping and popping while the page loads slower than usual, but after rebooting it's fast again with no skipping.
I've been searching the forums and Google and seen a few others with this problem but can't find a fix for it. I've tried clearing the Dalvik cache (with NVflashed CWM) but it didn't seem to help any. Is this a common problem with LG-based Gingerbread ROMs, and does anyone else here still have this problem? I started having this problem after running my last ROM, CM7 RC1 after a month, and when I switched to my current ROM I did do a full wipe/factory reset. I'm thinking about trying the new-ish CM7.1.0.1 stable ROM or Weapon G2x and am wondering if those have this problem as well. Any suggestions? Thanks for your time!
I have honestly had that problem with every most roms I've tried at some point. Maybe not instantly, but it will eventually start to slow down like you described in which i have to reboot.
Dang. Do you think a fix actually exists for this, or does everyone have this problem? It's strange since I can't find much discussion about this.
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
jose makalolot said:
That's the issue I have with any 2.3.3 builds. But with 2.3.4 straight for 2 days now, hasn't experienced this issue yet. Unlike 2.3.3 that even within a day, it needs a reboot. I think there is a problem with LG's memory management.
-----------
sent from my calculator with android
Click to expand...
Click to collapse
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
LuponX said:
If I flash CM7.1.0.1 stable, will ClockWorkMod 3.0.2.7 that I flashed for the CM7 RC suffice? Or do I need to update that too before flashing? Sorry to drag the thread along.
Click to expand...
Click to collapse
It should work fine flashing any zip, but the 5.0.2.0 version of CWM is far better. Flashing it with the One Click tool is a no brainer. Go ahead and update it. It will only take you a few minutes of your time.
jboxer said:
It sounds like you have an app gobbling up memory and not releasing it. All Android phones such be rebooted around once a week to keep things nice and tidy.
Click to expand...
Click to collapse
Do you have any evidence to support that? From what i've read android is made to run better when more memory is used.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
I never had to reboot my Nexus One, or even my T-mobile G1.
I've tried just about every rom for the g2x since i got it about a month ago and they are slow down. I'm not on the 2.3.4 rom and it started out great; now its almost unusable.
Anyone know whats wrong?? i'm about to call t-mobile and try to get another phone. I don't understand how they can release phones that just don't work. How can my single core 1ghz Nexus one be faster then this dual core 1ghz phone?
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
tokimaromi said:
i'm just on stock and i have to reboot my phone every single day or else it's not useable. i have like zero apps on my phone almost so i know that can't be the problem, it's ridiculous
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good to know it isn't only me. I'm trying some more tests on my phone to see whats going on. I think i'm gonna call tmo soon and see what they say.
i'm sure they won't have a good reply for you but definitely share with us if they do! i understand having to reboot the phone like once every three days or so but every single day is totally unacceptable
Sent from my LG-P999 using XDA App
Did anything ever come from this? I'm completely stock, just got this phone the other day. This phone lags harder then my HD2 I just had, which I would have kept if the digitizer didn't go out.
Are you guys on stock? If so then i highly recommend going custom. LG can't code for crap, so lots of stuff that was wrong with this phone has been fixed in the recent custom roms/kernels.
I've had the same issue until i recently switched to Phoenix Blood rom. I recommend it if you want to forget when was the last time you rebooted and still use the phone buttery smooth. I am using Faux kernel and the ROM is rock solid for me. Recently ran and the V6 script(instructions are on the rom's page in development section) with it and now it's even better! Give it a try you would love it;-)
Sent from my LG-P999 using XDA App
Okay I'll check it out later, ya I'm out the box right now but not for long.
Sent from my LG-P999 using xda premium
Yeah get on a ROM without any LG coding or framework. If you guys prefer a more stock 2.3.3 feeling I would suggest Bionix Reloaded.
I make it a habit to reboot my phone every night before I sleep.
Hey guys,
My phone has been acting weird lately. It starts by, lets say, lagging.
I reboot the phone and it gets stuck into a reboot cycle... Great. The only way to fix this is to restore a back up.
I tried reinstalling the rom a couple of times, which resulted into the same problem after a couple days of use.
I've also tried the bubba kernel which, again, resulted into the same problem.
Some specs:
S-OFF, Supercid, HBOOT 2.15, RADIO 1.11
Not sure which ones are actually relevant, but I mentioned it anyways
Any suggestions/questions are welcome. Anything. Thanks for reading.
Well, since you have SuperCID and S-Off you clearly have a basic knowledge of what you are doing. I can only think that it is the kernel or the ROM. I'd never mess around with a kernel, because that is probably the only thing I trust HTC on, that's why I've kept stock. Have you tried another ROM? You might be madly in love with the appearance and the functionality of the ROM, but if it is laggy and is causing you to have to repeatedly restore backups, then you are best off using a smooth one. I also use the CM10.1 nightlies, and I agree with that. If you are seeing screen tearing, then that is not your phone being a retard, that is a known bug that they are going to address. However, some suffer worse than others. My One S is at the grand age of one year and is suffering quite badly from it, yours may not. Also, if you're talking about the RAM dropping from around 350MB at boot to around 150MB in 24 hours, that's pretty normal too.
The screen tearing is rarely noticeable, its actually almost non existent.
Im running the cm10.1 kernel that came with the rom.
I did try ViperOneS but it wouldnt even go further past the splash screen throughout the first reboot after installation in Aroma. Did flash clear fastboot cache and flash boot.img but it didnt work so I gave up on that, lol.
This morning I decided to back up my current rom and restore it after wiping everything, something I only do when installing a new rom. So far my phone is behaving like it should.
I just opened the thread to get help when needed and to get idea's as to why it's behaving like that.
Thank you for your response
Sent from my One S using xda app-developers app
Somebody who has a greater knowledge on this subject than me, most likely usaff, will pop up within the next couple of days and give you some better help than I could. I've only known what I'm doing for a couple of weeks, so I'm new at it, but since I'm a bit of a noob I can give advice that noobs will understand. Since you're clearly not a noob, I didn't help that much.
Maybe some more info is/can be helpfull.
Wich nightly you running?
You say it runs for few days, then you get problems, So it runs correct after initial install.? If So, what programs do you install/use (wich might cause tot make it unstable)
Can you tell how you install the ROM in steps.
Verstuurd van mijn HTC One S met Tapatalk
I haven't experienced this problem in a while anymore. I think a full wipe/reset did the trick before restoring a back up. Thread may be closed
So to start, my phone is rooted and the bootloader is unlocked. I should also have the latest modem flashed. The problem is that the screen will freeze upon some calls, not all of them, and prevents me from doing anything. I can still hear everything that's coming through but the screen itself is just unresponsive. At that point, I usually just pull the battery and reboot and make the call over again. It hasn't happened to me immediately after a battery pull yet.
This problem has occurred to me on multiple roms. I initially noticed it on LiquidSmooth's 3/16/13 stable build and so I re-flashed it making sure to do a clean install. It kept on happening so I kept switching roms and am now on Carbon Rom and it hadn't given me any problems until just now (been on Carbon for over a week). All of my rom installs are done with clean flashes so I really don't know what's going on at this point.
Any help would be absolutely fantastic!
it's a known issue on AOSP roms
Try using the latest Official CM10.1 nightly. Best to do reset, clean install. That issue has pretty much been squashed on the latest builds.
Sent using Tapatalk
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
kupnooduls said:
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am currently using Paranoid Android which is based off cyanogenmod, and I get the same thing. Phone freezes mid call. I was having general freezing problems across the board until I installed PA, I kept thinking is was my launchers, etc, but I am bare bones right now and it still does it periodically, and have once had it do it directly after a battery pull.
When mine does it, the call drops.
Two things..
First, I have been having the same phone freeze issues as everyone else, tried different roms, the dummy file fix, all kinds of different things going through this forum. I wanted to do everything I could possibly do before posting about it.
I am using Paranoid Android. I noticed the cyanogenmod version listed in the phone info is [email protected]#1 Tues March 19
Is this just a PA version number or actually the kernel number? What if I was to flash the newest stable kernel to my PA?
ALSO
I noticed when my phone does its freeze up thing, the battery has been at 53-57%. It does not seem to do it any lower or higher battery percentage. Is it possible that its actually a problem with the battery or the battery percentage programming??? It just seemed odd that it always seemed to be around the same % when it happened.
Any thoughts????
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.
Hello,
I bought a VZW Galaxy S3 at the end of May. I left Touch Whiz on it for about a week before I couldn't stand the look of it any more, It also started freezing and I would have to hold the power button down to reboot it. This would happen 2-3 times a day so I decided to go with a custom rom. I had rooted and installed custom roms on my Nexus 7 several times before so I felt comfortable doing it on my S3. I was able to root it and unlock the bootlader and I installd TWRP as my custom recovery. I flashed the AOKP rom and was using that for several weeks. Initially it worked great and crashed maybe once a day but I figured that was normal for a custom rom. After a few weeks it started to crash more and more. I finally ended up restoring the phone from an AOKP backup I had made the first day. That seemed to help a bit. After it started to get worse again I switched to SlimBean. This one was the worst. It worked good for a few days then crashed constantly. Finally, after getting extremely frustrated I flashed CM 10.1.2 I decided to go with one of the Milestones to be on the safe side. This was working great until now. It constantly freezes and crashes. Also, many of the apps crash. I am just wondering if this is an issue with how I unlocked and rooted it or if this is an issue with my phone? I have also noticed I have terrible reception with any rom even stock. What roms would you guys recommend as a very stable one? I know CM is supposed to be. Any help would be greatly appreciated. Sorry for the long post I wanted to make sure I included enough information.
Thanks.