I'm having issues with my calls ever since I changed my S3 configuration (ROM, kernel, apps, framework…).
On most of them, I get a soft reboot at the start or in the middle of the conversation.
I've tried changing the modem but there were no results.
How can I diagnose the problem?
Thanks.
P.D: You can see my config on my signature
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
eXtremeDevil said:
It just happened again. I have read the logs but I can't figure out the problem.
Any help?
Thanks.
Click to expand...
Click to collapse
If you have overclocked then lower the frequency I had the same issue on another device and doing so resolved it
We'll see if that's the issue. Thanks for the tip, I'll keep you guys informed.
Have you tried changing kernels, it happened to me once from a custom kernel
Well, I'm very happy with my kernel, but if the problem persist I will consider it.
Thanks!
The problem persists. May be that I installed BusyBox from Play Store when I had it already from the ROM & Kernel?
Yeah most likely thats the problem, try flashing your rom again
Sent from my SM-G900F using XDA Free mobile app
I have uninstalled BusyBox, reflashed the ROM and changed the kernel. I'll keep you guys informed.
So far so good, the system was even better (a lot more stable) and no call reboots. But just now I've had the first one. I guess the number of call reboots have decreased (I'm not sure because it is a ramdom thing) and that's good but, again, any way of diagnose the problem?
Thanks!
EDIT
I often lose my APN settings and I had to reboot the device (a soft reboot is valid as well), may that problem be linked to the other?
I've performed a full wipe and started all over again. Let's see if this time everything works well...
Unbelievable. I did every single thing from scratch and the phone was perfect. Today I make my first call after all the mess and configuration and AGAIN, a soft reboot.
I'm 100% out of ideas here. Is there something, ANYTHING I can do to confront the problem? Some kind of log or monitoring action so I can know a litte bit more about this??
Please, I'm REALLY desperate right now…
I've installed the app SIM Card Manager and the phone field was unkwown. I rebooted and my phone showed up correctly. Maybe the app's fault or my SIM is half-broken? Or is it the phone lector?
Tomorrow I'm changing my SIM for a new one and let's see what happens, really out of ideas right now...
I think I found the cause of the problem.
This modification along with the Xposed app StatusbarVolume seems to cause the reboot when I try to change the volume when in a call.
I can't be 100% sure this is the faliure scenario because the bug is a little bit random, but I am 99% sure anyway.
EDIT
Not sure if the cause is the volume unlink, or the Statusbarvolume overlay failing to show up in call if it has never been invoked outside of a call before since the phone startup. May be a mix of the two things.
Related
EDIT:
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
That post fixed my problem, as well as fixed the problem which the data connection turns off after a call.
Hey guys, sup?
I have a huge problem with my TELUS Touch Pro. Great phone, but just one problem...
Whenever somebody calls me, I can't answer the phone. The onscreen "Answer" button doesn't work, the Talk button doesn't work, pressing the Select button doesn't work...pressing the headphone button does, but sometimes my headphones are in my pocket, or sometimes they're not with me at all!
The only way I can answer them is by ignoring the call, and calling them back. It sucks big time.
Anybody have a solution? And no, I'm not hard-resetting my phone. It started doing this for my first call, so I'm pretty sure it's not my fault.
HEEAAALLLPPP!!!
Is this the stock ROM?
Do you have BT on and connected?
Mine started doing that yesterday. I did a hard reset and so far everythings back to normal. Still do not know what it was tho
I just had my TP replaced and the new one did the same thing, I did not notice until a few days later as I use a bluetooth headset and pushing the answer key on the headset worked. I had to RTN the device to make it work properly. Have not had a problem since. it has been aabout a week and a half.
Sometimes I've noticed this happens when my memory is tied up elsewhere, ie media player or something. Try soft resetting your phone every morning that might help clear it up.
I have had this happen with me on my Titan which I recently traded in for my Touch Pro, and also on my Touch Pro. I noticed it coincided with installing iGo8 GPS software on both. A hard reset was the only way I found to fix it. Uninstalling the software did not do the trick. I could be wrong about the software title I am blaming, but I have everything reloaded on my phone except that, and all is well. I do have a Slide To Answer incoming call screen now with the MightyRom 4.9.5 rom installed, maybe this is a work around, don't know for sure. If anyone else has more feedback, let me know. I would love to find a fix for it so I can use my GPS software.
Mine started doing this crap last night. I reinstalled the S2A cab and just let it go.
I am starting to think it might just be the telus network being a boatload of suck. Mine does it with the stock rom without any programs loaded from time to time. I am thinking it must be the tower failing to acknowledge that you want to answer the call, so the phone keeps ringing becuase it sees there is an incoming call but the tower ignores that you are trying to answer it. This is just my guess based on what I have read about CDMA, I wonder if any GSM users have the same issue.....
Do any of you have Advanced Configuration installed? This is what caused this problem for mine and my brother's TP. Uninstalling didn't fix it. Had to hard reset.
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
I can tell you that this will more than likely fix this for you. Mine was doing the same thing, applied this, done and shut! Good luck.
OMG OMG OMG thanks!!!! That also fixed the problem where it ended the data connection after the call.
Sorry I took so long, I THOUGHT I was subscribed to the thread...
Thanks again!
My SGS2 stopped vibrating. Tried flashing, un-rooting, restoring stock and factory settings. None of these worked.
I am inclined to think that it is a hardware problem.
Has anyone else been dealing with issue? I read some posts on XDA regarding this matter but they were software related as opposed to hardware. Can anyone post instructions on how to fix it or provide any solutions for this issue?
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
UpInTheAir said:
If its hardware, why not flash stock, remove binary flash count with USB jig, and return for warranty?
Sent from my GT-I9100 using xda
premium
Click to expand...
Click to collapse
Cannot get jig in Palestine. Bought the phone from the UK. Sending it back will be problematic. I will look for a repair shop.
Thanks for the quick reply
That's a "bummer" (bad luck). You could make a jig, but as you said that it would be problematic to return. Hope you can sort it easily. Sorry, can't think of anything of use right now.
Sent from my GT-I9100 using xda premium
hey there,
i got the same problem. no more vibrating at all. not with calls or notifications and not as haptic feedback. it started today (was still working in the morning), though i did not drop the phone or anything.
i am still hoping too find that it's a sw-problem. but all potential solutions i find do not help. so i guess i have to contact samsung.
but before i do that i have to get rid of all "hacking".
could you plz tell me what i have to do?
i have now cm9 20120402 nightly.
but i still have a cwm-recovery-backup of the original touchwiz (gingerbread).
-so first i make a backup of my current rom via cwm and of all my apps via titanium and store everything on my pc.
-i flash my touchwiz-backup
-i get one of those: http://www.amazon.de/s/ref=nb_sb_no...ld-keywords=Samsung+Galaxy+S2+USB+Jig&x=0&y=0 , plug it in, wait til its done and remove it again.
after that, samsung will never know i "messed" with the phone??
or do i have to consider/do something else?
tyvm!!
kws
I have the same issue.
When I was on my stock 2.3.5, I found a workaround:
- go into test mode (dial *#0*#)
- find the vibrate button, when you press it, it shouldn't work like you expect
- go back
- plug in your headphones and push the cable a bit to the left
- test vibrate again - this time it should work
- pull the cable out while vibrating, still pushed to the left, vibrations should stay on
I know it sounds crazy but it seems the hardware part that controls the vibrations is near to the jack port - excessive use of headphones, like it was case, must have damaged it somehow.
However, now I'm on CM9, so no test mode for me, I'm achieving the same effect by bashing the back button, so I get semi-constant vibration. I know, It's ridiculous.
Have the same problem here, I think it's software related because the shut down vibration stopped working when I flashed CM9 ICS, I can't remember if it was working anywhere else though. But now I'm back to 2.3.5 and it's not working at all. Did a Factory Reset, Cleaned Cache before and after the flash. Also used the Jig to reset my counter. Any clues?
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
dajomas said:
I am experiencing the same issue.
Yesterday, I downgraded from 4.0.3 back to 2.3.5 as I was having a lot of problems with ICS. Now, my phone works fine again except for the fact that it does not vibrate anymore. (Which it did fine in 4.0.3 and before in 2.3.5)
I tried the trick Lechium06 mentioned in this thread but that did not work for me.
Anyone else having this issue? More important, anyone have a solution???
Greetinx
Johan
Click to expand...
Click to collapse
I saw something similar on CM9 thread, they said it could be a "bad flash", not a corrupted rom but the lack of proper cleanup before and after the flash. But I cleaned up everything before and after and I don't like reconfiguring the whole phone again for nothing.
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
kweso said:
since i had that before, i ruled out a hardware issue. it happend when i played with the system settings. but as i sayed, i tried to reverse everything i did. now after i updated to 0206 and wiped cache and dalvik, still no vibration.
is there anything i could have missed?
is there a possibility to reset all settings to default without deleting all my data?
thx,
kws...
...tapatalking
Click to expand...
Click to collapse
I assume since your posting in xda developers that you are rooted?
If so, just back up data with titanium backup app and factory reset, setup system and then restore USER apps and data only.
Sent from my GT-I9300 using xda premium
kweso said:
it happend again.
dont recall what i did or if i did something last time at all. but it worked for over a year now. and now, my sgs2 doesnt vibrate at all, i tried all possible settings, tested with z-device and rebooted. nothing.
apprechiate any hint!
thx!!
kws
Click to expand...
Click to collapse
Did you install another rom?
My vibration for example didn't work with some cm10.1 nightlies
it started in cm10.1 20130203. then i tried wipe cache and dalvik. nothing. then i updated to 0206 (wiped cache and dalvik again) > still nothing. went to bed. got up. everything ok! its vibration again! i am 100% sure, it did not work, when i left it on my desk last night. this morning, i checked for missed calls and it took a moment until i realized: i got haptik feedback back on patternunlock and keystrokes! checked ringtone-vibration: fine as well!
dont ask me how! would still like to know for myself.
thx,
kws
AW: [Q] Vibrate function doesn't work anymore, hardware issue
call me stupid!
suddenly this evening my phone stopped vibrating again. then i realized: quiet hours! i turned off haptik feedback at night.
could slap myself. at least ill find this thread again, next time i screw it again....
nite,
kws...
...tapatalking
Girls can use it again then. Good news for them!
Sent from the little guy
So I have run in to a bit of a snag, and though I doubt it is ROM specific, I thought I'd start by asking here to see if anyone else has run across this and might have a fix
I first noticed it when I was running ShiftAO5P 3.2, and though I didnt specifically think 3.2.1 would fix it, I tried that, and now the problem has come back.
The gist of the issue is that if I havent used my phone to talk to someone for some unspecified length of time, when I call someone, they cant hear me. I can hear them just fine, but they can't hear anything from my end. If I hang up, and call right back, then it all works fine. Also, it is fine if they call me - works right away without having to re-make the call.
Like I said, I did a complete reload to get to 3.2.1(full wipe, and even reformatted sd card), and since I suspected the tiamat kernel and the call recorder app I had been using under 3.2, I didnt reload those pieces and stuck with just the stock 3.2.1
Everything seemed OK for about the first week or so, but now it is doing the same thing again.
I am guessing it is some app, but I have no idea how to try to chase it down.
I have a logcat that I just dumped right after the problem happened, but dont really know what process to look for.
Any suggestions? TIA!!!
Does anyone ever have issues with the phone/dialer app?
If I try to call someone from contacts, I swipe on their name to the right and nothing happens, if I try again, I notice the contacts app has frozen OR I try to swipe again and nothing happens again. Eventually it might work after 2 or 3 goes.
Then I'll hang up after finally getting it to make the call and the phone immediately tries to make the calls I tried to make earlier... This happens fairly often but not all the time.
OR – (this happens rarely but does happen)
Phone rings, try to swipe the green answer thingo and it just bounces back to where it was, try to swipe/answer again nothing. I can't answer the call. Happened today, really pissed me off. Phone app crashed and refused to make a call after that for about a minute.
Sound familiar to anyone?
Using Android 2.3.5 Vodafone (Australia) stock unrooted.
Anyone?
Would love some help on this.
Yes I am facing the same issues as you.
A few observations:
problems exist on stock dialer app as well as third party dialer apps
It's an intermittent problem i.e. sometimes the problem shows and other times it does not
I was facing the same problem a couple months ago too, since i was running 2.3.3 so i had just upgraded to 2.3.6 and the problem had disappeared. But out of the blue it has again started now while i am running 2.3.6
Currently i am running on stock rom, cf rooted, latest modem.
Am looking for a permanent solution and will post a solution if i find one, in any case hope the official ICS release (due on the 15th) should solve the problem anyways.
Anyone else facing the same problem?
Updates
Usually clearing the cache and calvik cache does not help resolve the issue.
After posting the above post I had just created a ClockWork mod backup and Restored to the same. Dunno how but that resolved the issue, or to be exact, the issue did not surface for a couple days.
Today the issue actually became too much for me to be able to handle.
So I again cleared both cache and dalvik cache and then fixed permissions via CLockWork recovery menu.
Since then I am not facing the issue yet. Hope it works for you too.
(But this is just a preliminary observation and maybe the issue shall resurface with long term use)
p.s. really hoping that the impending ICS update will permanently fix said issue.
Hi guys
I have a really annoying issue with my galaxy s2. It seems to be stuck on emergency calls only and will not let me send texts, call people, etc. I have tried everything- restore stock firmware, factory reset, repair apps and nothing has worked. My IMEI number is not null and it matches the one on my phones box. I dont know what else to try so any help would be very much appreciated
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
MistahBungle said:
Carrier-side I reckon. Call them to ensure there's nothing at their end responsible. Given what you're already tried, and given your IMEI hasn't gone away, seems a bit curious you'd lose connectivity all of a sudden like that (unless it's a hardware issue).
Click to expand...
Click to collapse
I checked and there is no carrier issue and it works fine in other phones
In case and if you're using stock firmware:
1. Boot into Recovery Mode
2. Perform a full factory reset by wiping /data partition.
3. Reboot and see if it fixes the problem
However, try and use a custom firmware in case your OS is causing the problem. When it comes to me, the hardware doesn't have to be necessarily damaged or affected in such a case since the phone app is on emergency calls, so it's fully accessible. I recommend checking the app settings again (maybe tapped on something accidently), but nevertheless, I prefer trying a custom Rom to verify that it's a software issue, or simply flash your stock firmware through ODIN to fix any issue if persisted.