Hey everyone,
I've noticed that when I put a custom kernel on my Evo, it works great for the first few hours after reboot but then starts seriously lagging and I'm forced to reboot and it works just fine after that till the lagging begins again.
I've used the stock HTC kernel and my phone works fine for days without rebooting.
I've tried Netarchy's kernels, KingKlick's kernels, all the CFS/BFS/HAVS variants of them and they're still super laggy after a few hours.
Does anyone else have this same experience?
Related
Does anyone have problem with appbrain? It runs well and all is good but when i want to go back with back button the screen just blacks out for approximately 1minute.
that's lagging
i dont believe so, last night I instaled fresh new rom and this was the second app that I instald and it was the same.
I had the same problem a few days ago after flashing Darky's 8.0 rom and speedmod kernel.
But after reflashing the rom (without speedmod kernel) and disabling the lag fixes it started working properly.
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.
Hi,
since a few weeks i've got a big problem, my phone freezes to the point where I have to hold the power button to restart it. this started happening when I was on Jellykat v6.7 but still persists after flashing stock rom.
Info:
Flashed latest bootloader
Problem persists on Jellykat and stock, with multiple and stock kernel.
Problem does not occur when running spotify in the background.
Right now I'm running stock rom (4.4.2 from sammy, flashed via odin) with stock kernel and latest bootloader.
When I restart it and check my battery stats I can see my wifi was still working when my phone did not respond, thus the device was on and I was recieving messages while the decive was not awake.
Weird thing is that it works properly when I let spotify play in the background, meaning it doesn't go into deep sleep (I think).:silly:
Right now my device works fine, but only because I have spotify playing the background 24/7 which isn't ideal in terms of battery life and such.
Any thoughts on it?
Thanks in advance!
Still no one? I guess i'll have to survive till I get the note 4 :silly:
Same here
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
silentkiller143 said:
Same thing happened to me when I was on stock rom.. sometimes it froze sometimes it didn't.. (Without spotify)...
Now changed to custom rom... havent faced such issues since then (last one month..not much)
Click to expand...
Click to collapse
It started on custom JellyKat ROM, weird thing is, yesterday it worked perfectly fine without spotify and today it's screwing me over again
Hello there all!
I've been having this issue for a long time.
I've been using the SuperZen ROM, Custom Project T Kernel and official L Speed Mod. Sometimes I got stuck during the device's bootanimation (until this occurred really often). I tried going back to stock kernel and everything went okay, but didn't have the enough time to test some consecutive reboots/power-ons as I did flash my phone again. The issue occured ONCE without the custom kernel, but then reinstalled Prohect T and L Speed Mod.
I am now running Prism Barebone with Project T and L Speed Mod. The issue occurs very often I tried removing L Speed Mod via Emergency_Uninstaller (provided or L Speed official page)...but the issue's still there. I may try a new fresh install by only adding the custom kernel this time, but I did want to ask if anyone experiences this issue as well? I am not sure if it is a hardware issue. Everything was okay with the stock ROM (the actual stock). Please note that my phone was in service ONCE for a screen replacement. I hope that nothing bad happened during that time..
Thank you for any response!