• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] freezeing

hitter

Newbie
Last few days I have had the problem where my phone has froze.* Once it was in the morning the other times it was in the evening.* The only way I could get it back was to do a battery pull.* When I do and the phone comes back Titanium backup fires up saying there is a scheduled backup.* I have one backup scheduled and its for nowhere near that time.

I am running AOKP ROM with imoseyon's lean kernel. I have switched versions on both....Including 1.5 kernel and M2 on the ROM.

Anyone see something like this before?
 
Last few days I have had the problem where my phone has froze.* Once it was in the morning the other times it was in the evening.* The only way I could get it back was to do a battery pull.* When I do and the phone comes back Titanium backup fires up saying there is a scheduled backup.* I have one backup scheduled and its for nowhere near that time.

I am running AOKP ROM with imoseyon's lean kernel. I have switched versions on both....Including 1.5 kernel and M2 on the ROM.

Anyone see something like this before?

Could you turn your scheduled Ti backup off and see if it continues?

Also are you undervolting at all or have you changed the CPU frequency to below 350MHz?
 
I can turn the schedule off. It is set for 2am and most of the freezes ha e have happened around 6pm. I am not under volted. I did try one of the lower MHz kernels for a day or so but have been on 1.5 stable for most of the time. I do have interactivex scaling enabled.
 
I would suggest trying interactive then, or a different kernel. I know there have been some issues with the 1.6.x kernels from IMO for some people.
 
I just had it happen again. This time no Ti afterwards. I even tried to to call the phone when it was locked and it didn't ring.

I have the Otter box defender and these battery pulls are getting old. I will try to switch up my
Scaling
 
If that doesn't help I would try reflashing the rom. Make sure you checked the MD5sum and wipe /data, /system, cache, and dalvik before flashing just to make sure you don't leave any trace of a past rom.

If that doesn't help or you did all that the first flash I would try a new rom, not all phones work the same with the same rom/kernel ;)
 
Definitely sounds like either a rogue app or a kernel issue. Since you've switched kernels, I'd lean toward an app causing problems. You sure you don't have any profiles enabled in setcpu or similar with a set on boot option enabled?

Can you list the last 4 or 5 apps you've installed by memory? And have you installed any apps from a source outside the market?
 
Definitely sounds like either a rogue app or a kernel issue. Since you've switched kernels, I'd lean toward an app causing problems. You sure you don't have any profiles enabled in setcpu or similar with a set on boot option enabled?

Can you list the last 4 or 5 apps you've installed by memory? And have you installed any apps from a source outside the market?

I cant really be sure about the apps. They come come and go with only a few that seem to stick around.

I am starting to think it was the InteractiveX gov and my thumb. I watched my self and when I used the phone at times I would turn the screen on to check something turn it off decide to look at something else then turn it back on. All in the matter of seconds. That probably drove the processors nuts with interactivex?


Just a guess?
 
Back
Top Bottom