I'm currently on Resurrection 2.1 ROM with the Siyah kernal 3.2.7.2+ on Samsung Galaxy S2 and am experiencing the following:
When I have made an unsuccessful call e.g. engaged, I keep getting directed to the lock screen immediately after. If I want to retry the call, I have to input my unlock code to access the dial pad again. This becomes very annoying especially if you want to try and retry the call 2-3 times.
I'm not sure if this is a problem or natural behaviour of the phone, but I would be grateful if someone can explain if this is a fault in the software or otherwise.
Thanks
Ben
Related
Hello all
Samsung Vibrant T-Mobile Running Eugene 373's UNOFFICIAL T-Mobile 2.2 Rom (no lagfix).
I seem to be having a problem that when I receive a new sms message, the screen wakes up, and then stays lit indefinitely until I manually lock the phone. Any insight as to if if this
1) rom related
2) any program that could cause this
3) some workaround without wipe data/cache
Any input is appreciated, thanks in advance!
did you ever figure this out? my wifes phone does the same thing
This is just.... weird. are you guys both running the same rom?
Has anyone encountered problems with the dialer?
I can punch in a phone # and press the green button to dial, but it doesn't dial immediately. There seems to be a lag sometimes of up to 30-60 seconds.
Also, sometimes I cannot hang up a call. I press the disconnect button and it just doesn't do anything.
phone app/dialer issue
hello,
i think that the same happened to me. the problem that I am having concerns the phone app on my razr. very, very often when I try dialing somebody, after hitting the the dial button, the screen where is shown a larger photo of the person that I am calling appears then it flashes and disappears (saying <call time 00:00>, something like when the call is terminated) then it reappears by itself after 2 or 3 seconds and the call continues smoothly. this is a very annoying problem, not being able to have control of my calls.
i don`n know what could have started this problem because everything was working fine, and still is apart from this issue. i`m not a skillful android user but i managed to root my phone (making all the necessary backups), then using some specific apps for rooted phones (like titanium, motomizer etc.) and every thing was OK. Lately i`ve installed a navigation program for android to my phone (iGO) but i`m not sure if by doing this, the problem appeared.
to solve this, i`ve tried everything: uninstalling all the suspected apps, factory reset, rolling back my system to a previous backup, updating my system version from 651.73.30.XXXXX.en.EU to 651.167.19.XXXXX.en.EU, cleaning the cache/dalvik cache. the problem still persists...
if you guys have any idea what could have caused this please guide me through a solution.
thanks!
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
stane37 said:
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
Click to expand...
Click to collapse
I have the same problem with my phone. Any solution for this problem thx
Reflash, reflash, and if it happens again - reflash. The screen lock/unlock workaround was working about 90% of the time. I gave the phone to my father (clean new flash) and he didn't experience any issues with the rom so far.
So i bought a Samsung Mega from ebay and seemed everything was ok. However a day or 2 later i noticed i was not able to make a call. I went and did a reset and everything was fine. I have now noticed this is a recurring problem. out of no where the network stops working and i cant make any out going calls or receive any. The bar on the phone still shows a small bar like there is a network. I also noticed that when i make a call with the phone, the screen shuts off automatically. i press the power button to get it back up and when i try to touch anything on the screen it attempts to pull down the drop down menu. It pulls it down like 2 inches and i have to mess with for the actual touch commands for it to work. as soon as i hit the button to call it shuts off. This device is already rooted and i dont know if something done to the phone has made it wonky. I dont really care about the root and if there is way to fix it i would like to hear any suggestions. this is running android version 4.2.2 kernel version 3.4.0-2052936. the Mega model is SGH-I527. Thx
Recently when i swipe right contact to make a call, calling screen appears but it isn't calling. I must wait few minutes till it starts calling or press home button to go to home screen but then any app or anyhing freezes. It happens once in a while since few weeks. I did nothing special, no new apps, no changes at all. Wierd is my gf phone started to do same thing a bit earlier with no reason, too.
After restaring it works nice then after few calls or few days it starts over.
Is there any obvious reason causing that behaviour or not?
GB 2.3.6, Go Launcher Ex. I got this config since 2 yrs.
try clearing the cache often
and it might solve this.
lagging as it may be called.
ginger bread
official update for jellybean is available ota /via Kies for s2
hit that thanks meter and tell i helped you happy to help.
B)