I flashed several different ROMs with ROM Manager to see which one I liked. I noticed that my phone was getting more and more sluggish with each flash. Any idea what could be causing this and how I could fix it?
ohtanya said:
I flashed several different ROMs with ROM Manager to see which one I liked. I noticed that my phone was getting more and more sluggish with each flash. Any idea what could be causing this and how I could fix it?
Click to expand...
Click to collapse
Well it might be that you installed one to many Rom on top of other, some roms require and suggest you wipe data and cache before installing their roms.
Related
so, i previously had a rooted ROM. one of the stock rooted 2.2 roms that came out a while back. 2.09? and now the new rooted stock roms are out, 2.10? so i tried to install that. used rom manager and installed from SD and everything went well. but now i seem to have a problem with random reboots. haven't quite found a correlation between anything causing reboots yet. is there a way to log what happens to find out what may be causing the reboot?
or should i try flashing a new radio? i really don't see how radio's affect stability (came from winMo where it didn't), but i've seen reports about that here.
i have already tried restoring to my previous rom (via rom manager) and the random reboots are still there.
Well radio is how hardware communicates with software so I would guess it would be that.. in rom manager there is a rom download section.. click on NeoPhyTe and at the bottom there are radios so just flash one of them
Sent from my HTC Desire using XDA App
1. hard reset. is it still doing it?
2. adb logcat. <- this logs what is happening with your phone. but without knowing what is causing it you could be watching your logs for a while
So was a cause found? Reason for asking is because quite a few of us are starting to get the same problem including myself .
I have a problem with MIUI rom. Some days ago, my phone suddenly had FC, now, my phone run really slow and laggy... If I turn off the screen, my phone won't wake up, only four button in the bottom light up.
I wiped everything in CMW (system,data, and cache, also sd-card) but it doesn't work.
The fresh install had the same issues
I have this problem only with MIUI rom
any help
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
zandroid said:
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
Click to expand...
Click to collapse
i have tried from 1.8.5 to 1.9.2.
it's very weird
this guy has the same problem with me, maybe he can explain better than me
http://forums.miui.us/showthread.php?3740-Display-won-t-wake-from-sleep
Hey guys, I flashed 1.819 yesterday and everything was going great. The ROM ran smoothly and I was having no issues at all. When I woke up the next morning my display would not turn back on. Every time I tried to turn on the display the soft lights would light up but the display remained unresponsive. The phone still seemed functional as I could hear e-mail and sms notifications coming through.
When I rebooted my phone it was abnormally slow.. mounting the sd card and syncing seemed like it was taking forever and the launcher was very jittery.. if I let my display time out it would not come back on and I'd be forced to pull the battery and try again.
I performed a full wipe through clockwork recovery (everything, including wiping system,data, and cache in 'mounts and usb') and reinstalled 1.819. The fresh install had the same issues.. if I let my display time out I wouldn't be able to turn it back on. I thought I was having some wonky hardware issue but after flashing my previous sense rom and everything is working perfectly.. so I'm pretty much scratching my head here. My phone was kickass for one day and became allergic to MIUI overnight!
Click to expand...
Click to collapse
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
PacerguyDon said:
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
Click to expand...
Click to collapse
i have tried both
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
ttupa said:
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
Click to expand...
Click to collapse
immediately after the flash. I don't install any other apps
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
spiderj said:
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
Click to expand...
Click to collapse
Try different kernel
Sent from my Incredible 2 3D using XDA App
tenchu_712 said:
immediately after the flash. I don't install any other apps
Click to expand...
Click to collapse
tenchu, your signature says you are not English or American. Are you running the MIUI.us ROM on your incredible 2 in English - and not another language?
.....just a thought.
Hi, I'm using Galaxy Note N7100. I have been experiencing random freezes on my phone lately. I have tried switching from ProBam to various other AOSP roms and nothing much changed. I have cleared Cache+Dalvik every time along with Factory reset. Also, I cannot add my Google account to the newly installed rom sometimes. It shows a message that says that "Connection could not be established." Presently I am on RootBox ROM. Please help, this is really frustrating. Also, would cleaning Internal storage help in any way?
Also, I haven't flashed any kernels. Just the stock ones, that come with the respective Roms.
Htc Pirate said:
Hi, I'm using Galaxy Note N7100. I have been experiencing random freezes on my phone lately. I have tried switching from ProBam to various other AOSP roms and nothing much changed. I have cleared Cache+Dalvik every time along with Factory reset. Also, I cannot add my Google account to the newly installed rom sometimes. It shows a message that says that "Connection could not be established." Presently I am on RootBox ROM. Please help, this is really frustrating. Also, would cleaning Internal storage help in any way?
Also, I haven't flashed any kernels. Just the stock ones, that come with the respective Roms.
Click to expand...
Click to collapse
What I would do is to install a original rom from sammy and if you still have this problem with that rom get sammy to fix it.
Just tell them what you have problems with and they will probably take it in for a fix.
And it sounds like you might have a emmc problem, have a look here as alot of users have had the same problem.
http://forum.xda-developers.com/showthread.php?t=2093599
And her is a more in detail http://forum.xda-developers.com/showpost.php?p=36499838&postcount=1
Hope it helps.
flash latest TW ROM :good:
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
What killed the camera? Is it possible that a bad ROM could have done it?
Is it possible to fix this via software?
I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
aalaap said:
I had a perfectly working Galaxy Nexus running CM10.x, which I updated to a CM11 nightly. This worked great for a week or so and then the camera and gallery started FCing. After several resets, restores, newer/older nightly installs, nothing changed. Tried all possible combinations of new/old Gapps, but still no luck. I tried different ROMs - PA, stock 4.3 and some others, but nope. I even tried Ubuntu Touch and even that couldn't access the camera. This is when I was pretty convinced that the camera module itself must have died.
My questions:
1) What killed the camera? Is it possible that a bad ROM could have done it?
2) Is it possible to fix this via software? I can try and get it repaired locally, but I just want to know if anything can be done at home.
Thanks.
Click to expand...
Click to collapse
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
jsgraphicart said:
A ROM wouldnt just kill the camera over time. It would have not worked right after the ROM was installed. So I doubt it was a ROM. I would do a full reset. Not just a normal factory reset but flash the factory image and see if it fixes it. If it doesn't then most likely it's a hardware issue.
Click to expand...
Click to collapse
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
aalaap said:
I've used the phone for over a year without any issues with several kernels and ROMs before and the camera worked just fine.
Yes, I've done a complete clean up - I wiped the whole phone and memory (using the fastboot -w option) and installed different ROMs and even a different OS (Ubuntu Touch), but the camera issue persists.
I believe it's hardware issue, but I just wanted to know if anyone's faced a similar problem.
Click to expand...
Click to collapse
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
jsgraphicart said:
So you went through this process?
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895
Click to expand...
Click to collapse
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
aalaap said:
Yup. I believe that's the exact post I referred to when I did it.
It even lost root during this process (of course) and I had to do it again - something I hadn't done in almost two years.
Since it was a spare phone, there wasn't any useful data on it. I backed up a few pictures and completely wiped it clean. No luck.
I'll add that the issue is only with the camera. Some apps FC, some apps (such as Camera+) give a message saying it was unable to connect to the camera or something. I believe the Gallery also FCs because it uses the camera at some point. All other apps work perfectly fine.
Click to expand...
Click to collapse
Usually if the phone has any issues at all, that process fixes them. And if it doesn't, then there is usually something wrong with the hardware. I wouldn't think the problem was brought on by installing a ROM or kernel though.
I think it's related to the kernel that you're using
......
i think yes but if you change the rom it will work
some roms the camera has some bugs big bugs colors are broken and stuff
I've had my OnePlus 3 for about a week and a half now, at first (on stock OS) I had no problems. Then I rooted and installed a custom ROM, IIRC it was ParanoidAndroid, all was well except my display kept freezing randomly, but I could 'fix' it by going to standby then unlocking again. It happens in all apps, but not when watching a video. It often freezes when using apps like Reddit or when I'm texting someone, and it's almost guaranteed when I watch a long GIF.
I then tried several other ROMs to see if it was just PA, but when I installed CM14 the same thing happened. I then tried CM13, where the bug had changed a little, the screen wouldn't respond to the power button, and it would stay on for 5-10 seconds, frozen the whole time. I then read somewhere that it could be GApps, so I downloaded a mini and stock .zip and tried them both. Still getting the freeze. Cleared dalvik/cache, still freezing.
I've just no idea why it's happening, has anybody dealt with something similar or has any clue why? Cheers.
Anyone?
cmowze said:
Anyone?
Click to expand...
Click to collapse
does this happen on cm based roms, or on aosp and OOS ones too?
timrock7 said:
does this happen on cm based roms, or on aosp and OOS ones too?
Click to expand...
Click to collapse
It's happened on PA and AOSCP ROMs, but I haven't tried flashing an OOS ROM yet so I'll try that later.
Flashed OP3Lite, based on OOS, and it works fine. No idea why no other ROM works though, seeing as nobody else has this problem.