Hi, I am running azure 1.01 and installed the various kernels. No problem so far, but the app. SetCpu causes the legend hang for 5-10 seconds after activating the phone and causes ADW or Launcher to FC.
With different settings en kernels, same result. After removing SetCpu, no problem anymore.
Anyone having issues like this?
Thanks, Ik
Related
Hey - I recently downloaded Das BAMF 3.0 RC3 with Imo's leanKernel on Extreme, and everything seemed to be running smoothly (at one point my touch screen did not respond, but a battery pull fixed that, ha). Just recently my app animations (for example, when I go to the app drawer, the apps 'fly' in and then 'fly' away when I close them) is VERY laggy, and they were not before. I did not update or change anything... I am using LauncherPro and WidgetLocker, but always have been. I have been trying to change settings around but no luck. Does anyone have any suggestions or know how to fix this? Any help would be appreciated! Thanks!
EDIT: And scrolling them the apps is very fast - it is just them flying in and out. Very strange...
EDIT 2: A completely other problem I am having - when I try to reboot, it doesn't reboot, it just shuts off. Is this a serious problem or something small that can fix it, or is this a known issue with the ROM that I will have to deal with until they fix?
Hello
My galaxy s2 doesnt wake up after put in to sleep mode, back n menu keys light up but no haptic feedback, while screen is on, no problems at all. please help me as ive tried wiping, reflashing different roms, trying multiple kernels and setting clock frequencies to always be on 1,2 ghz.
You must have something installed, like SetCPU and the phone goes below 200 MHz in powersave mode.
To all,
Please don't play with underclock/undervolt/overclock stuffs too much, it can damage the device big time. This is a phone for gods sake, keep playing with Sandy Bridge CPU's, they will take your tortures.
Regards.
I do have SetCPU installed, though i haven't touched the frequencies or voltages until after this problem which was when I put the frequencies to 1,2 gHz as lowest and highest. I have discovered another problem where TW launcher gets FC as soon as I touch the screen. Will try to uninstall SetCPU if I get the oppertunity.
wipe and then install cognition s2, its a modem rom and kernel all in one so you'll have no problems. then once its installed don't install setcpu
Sent from my GT-I9100 using XDA Premium App
Thank for your reply and all your help, I was insecure about custom roms so i installed stock rom amd it turned out great
My Thunderbolt is rooted, and I have tried several different ROMs (some AOSP even) and different kernels, and still I get this strange problem... I use WidgetLocker and fairly often when I go to unlock my phone, the touch screen doesn't work. I have to turn the screen on and off several times and sometimes that works, but it may take up to several minutes for it to finally register my touch. I even sometimes have to pull the battery because after ten minutes, nothing is responding. At first, I thought it the ROM/kernel - I used BAMF in the beginning and that is when I noticed it. Then I switched to ShiftSense, and I barely noticed the touch screen ever failing on me, but the lack of GPS locking and accuracy made me switch to NonSense, which I enjoy but again the touch screen not working at the WidgetLocker lock screen comes up again. My other theory was maybe the HTC Ring Lock Screen gets in the way, so I downloaded NoLock and disabled it, but that didn't work. Then I tried use the WL HomeHelper, but that didn't work... I tried different settings, but no avail. I really enjoy WidgetLocker and I want to try to keep it, but I am not sure what other things I should try to fix this problem. Any suggestions would be greatly appreciated! Thanks guys!
widget locker did that to me several times so I gave up on it. Its definitely a problem with widget locker and not your phone or ROM. It freezes. I even set it to unlock with long press of back button and that would freeze as well.
my phone does the same thing, i think its a problem with our phone and gingerbread. it happens less with froyo. I believe its a radio issue.
Sent from my ADR6400L using xda premium
I have used widget locker on over 10 different android devices I've own. I've never had a freeze issue with it. Reason I've had freeze issue starting with low RAM device. Then voltage to low or cpu frequency to low.
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Aup808 said:
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Click to expand...
Click to collapse
take off or freeze widget locker for a few days and see how your phone does. If it doesn't freeze, then you know its the app.
As for the guy that has used widget locker on 10 devices without problems, I call BS, I tried it on stock, and several customs and always had problems.
I sort of like the features of WidgetLocker than my default lock screen doesn't have and the look of it, so if I turn it off, I sort of want to try to find a replacement app in the meantime.
I just wanted to chime in and say I have this issue with my Thunderbolt and Widgetlocker as well. I've found that it usually freezes if I let my screen turn off by timing out. I'll turn it back on and the screen doesn't respond at all. I've found that if I let my screen timeout again while on the Widgetlocker screen, my touch screen will be responsive the next time I turn it on again.
Sent from my Bolt
Same problem here, I stopped using widget locker and just use the sense 3 lockscreen now.
I just wanted to put in my two cents - I was have the same problems with WidgetLocker on BAMF Forever (1.0.7 & 1.0.9). I found another thread on here (http://forum.xda-developers.com/showthread.php?t=1151269) that someone with a BAMF Sense 3 ROM and a custom kernel was having the same issue. Someone else suggested upping the voltage on the kernel to 368 or changing the kernel. It didn't work for him, but it did for me. I'm not using a custom kernel, but there is an option to change that in BAMF Settings. I've been running it at 368 for several days now and I only had one lockup (but that was shortly after bootup and the phone was probably busy doing other things in the background). HTH
Does two similar cpu frrequency changer conflict and result in reboot?? Cause recently I used 2 apps setcpu and cpu control lite and witnessed 3 reboots back to back.
XGr7078 said:
Does two similar cpu frrequency changer conflict and result in reboot?? Cause recently I used 2 apps setcpu and cpu control lite and witnessed 3 reboots back to back.
Click to expand...
Click to collapse
I use a value of 748 in SetCPU it works fine, if I put more, I get a reboot.
red led flashed
I mistakenly pulled the trigger and overclocked to 825 MHz I got freeze nothing working on phone.Then I reflashed rom with hot reboot......Was this necessary or was there another way out..????
Anyone heard of a problem like this? I'm on CleanROM but about half the time after a task runs the touch screen is only responsive for 5 seconds out of every 20.
The only task I run turns on bluetooth, run an autoconnect, and turns off wifi.
Searching came up with zip.
Details?
Clean or dirty flash? This can cause issues if it is the latter.
What kernel are you using? If you are using a custom kernel, undervolting too much can cause issues like un responsiveness.
Sent from my Xposed Beans Note 2