Develop Bugs

[Q] Slow and unresponsive DINC

My DINC runs great most of the time. But at least once a day it will become very very slow and almost unresponsive. The commands still work, but take 5-10 seconds to complete. A reboot fixes it completely until the next time that it occurs. This has happened with every kernel, ROM, radio, recovery etc. that i've flashed. I first noticed this after flashing a Cyanogen release MONTHS ago and it hasn't gone away since then. Has anybody else run into this and come up with a fix?
I'm currently running MIUI 12.11 with the 2.15.00.09 radio and invisiblek's #18 kernel...obviously i'm rooted with S-off as well.

I have that happen periodically but it is pretty rare and usually I am trying to do a bunch of things at once so I just assume it is user load on the phone.

try unsyncing everything for a day - see if it still happens

If you call it a dinc its going to act like one.
seriously though you have given us nothing to go on here.
what are you running? have you done a full wipe/factory reset?

lafester said:
If you call it a dinc its going to act like one.
seriously though you have given us nothing to go on here.
what are you running? have you done a full wipe/factory reset?
Click to expand...
Click to collapse
What do you mean i've given you nothing to go on? I said exactly what i'm running. I don't know what more info you'd want about my phone... I've tried system wipes and flashing different ROMS...all to no avail. This can occur when the phone is sitting idle and other times it happens when i'm doing small things like using TFLN (texts from last night). When I was running Cyanogen months ago it would occur every morning when I would go to turn off my alarm...so it was happening at some point during the night when I was doing nothing. The only app that I have running overnight is Locale.
I basically posed the question to see if anyone else is having the same issue. If not, then it probably has to be something to do with one or more apps not playing nicely.

Make sure you do a full wipe, wipe dalvik, each time you flash to a different ROM.
Second, are you overclocking at all? If you are using setCPU, make sure that the max speed is set to at least 998. I have run into where installing a new ROM the max/min speeds are set low to 245. This causes overall phone slowness though...
If you are overclocking, set it to 998 max and see what happens. I cannot go over 1113600 max or my phone gets all weird.

smtom said:
try unsyncing everything for a day - see if it still happens
Click to expand...
Click to collapse
ditto.
if your phone is syncing a lot of things (facebook, 5 e-mail accounts, twitter, etc.) it might be slowing things down significantly.

Rooted Epic freezing

Hello, I have my Epic 4G rooted with One-click, running Twilight Kernal 1.1.0 and SyndicateROM Frozen 1.1.0.... I've got two issues that I can't figure out.
1. It seems whenever I play a game, my phone freezes up while I'm playing and I can't do anything except pull the battery. (Which leads to number 2)
2. So far (except once) whenever I pull the battery to reboot the phone without turning it off first, When it boots back up the majority of my apps all FC on boot. My only option that I have found for this is to wipe the phone and restore with Titanium, although that can be a big pain (not as bad as without a backup lol)
So I have no idea what's going on or how to correct these issues. I've googled my issues and have found situations close to mine, but not close enough to count towards me taking any steps toward it. Thanks in advance.

Number 1- your phone is freezing due to the undervolts that are present in the kernel. U need to flash another kernel.
2. The reason for all the force closes is journaling is disabled so that is causing corrupted data. You can turn journaling on if you just make a backup and restore from that backup. Then you would t have all the force closes the next rime u do a battery pull.
Sent From My Evo Killer!

infamshxr said:
Hello, I have my Epic 4G rooted with One-click, running Twilight Kernal 1.1.0 and SyndicateROM Frozen 1.1.0.... I've got two issues that I can't figure out.
1. It seems whenever I play a game, my phone freezes up while I'm playing and I can't do anything except pull the battery. (Which leads to number 2)
2. So far (except once) whenever I pull the battery to reboot the phone without turning it off first, When it boots back up the majority of my apps all FC on boot. My only option that I have found for this is to wipe the phone and restore with Titanium, although that can be a big pain (not as bad as without a backup lol)
So I have no idea what's going on or how to correct these issues. I've googled my issues and have found situations close to mine, but not close enough to count towards me taking any steps toward it. Thanks in advance.
Click to expand...
Click to collapse
Let's deal with number 2 first. Because you have journaling off, there is no write verification on your phone so whenever you do an improper shutdown it will corrupt a lot of data. The fix is to turn journaling on. Easiest way is to go into Clockwork, do a nand backup and restore.
For number 1, what clock speeds are you running? Words with Friends locks up on me on ANY overclocking or undervolting. So running either SetCPU or Voltage control try capping out at 1GhZ and try your game again.

Guess we were answering at the same time MH, you beat me by a few seconds LOL.

Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?

infamshxr said:
Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?
Click to expand...
Click to collapse
Backup and restore in CWM. Your freezes will be solved by switching to VisionKernel 1.1 or Genocide.

infamshxr said:
Thanks for the replies so far. So to turn on journaling, all I have to do is boot into clockword and make a backup? If not could you please give me some easy steps or point me in the right drection? I'm still really new to this. As far as the cpu undervolting, I know setcpu isn't free, at least not that I found. I'm gonna check voltage control (hopefully its free). Are there any other recommended cpu control apps?
Click to expand...
Click to collapse
Like K0nane said you have to then restore that same backup. And Voltage control works very well with Genocide and there is very detailed instructions in Genocide OP.

Soo... Now that mothers day is almost here, and im done with all that crap, now I have time to work on this lol. So what do you guys suggest? Vision or genocide? Are there ups and downs to choosing one over the other? Btw, I did the backup/restore thing and so far no issues, thanks again for that.

infamshxr said:
Soo... Now that mothers day is almost here, and im done with all that crap, now I have time to work on this lol. So what do you guys suggest? Vision or genocide? Are there ups and downs to choosing one over the other? Btw, I did the backup/restore thing and so far no issues, thanks again for that.
Click to expand...
Click to collapse
Both kernels are fantastic. Read their descriptions for their varying features. Be sure to use VisionKernel 1.1 for now rather than 1.2.

[Q] Normal Stability?

Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference

bump. should I post somewhere else?

Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!

I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App

I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies

Sleep of death

Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.

Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium

I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.

Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App

Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.

Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.

I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.

ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.

did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.

I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.

how often has the sod been happening? I think i got it yesterday, but not sure.

Do you use setcpu?
Sent from my SPH-D710 using Tapatalk

This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.

Sleep Of Death

I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.

I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84

I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium

I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.

I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk

badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84

Are you using SetCPU? If so, don't fix screen off at 200-500.

Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA

Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's

ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?

Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?

The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.

SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.

I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.

It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.

Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot