I've got a stock op 7 pro (t-mobile converted to international) that has been running fine up until about a week ago. 3 times now I've had an incoming call start and then get dropped after 1/2 a ring. At that point the screen is off and the phone is not going to do anything until you hold down power long enough to force a reboot. When it reboots the call it dropped is NOT in the call history. (thankfully it is in the google voice history) I haven't done anything to it except install user apps and I'm not aware of any of those that would cause this type of thing. I've been using the app "should I answer" as my default phone app but it initially presented no issues and worked fine on my previous phone. If anyone has any thoughts how I can debug this I'd love to hear them.
Related
Hi guys, i like my fuze but damn, its not perfect, i have had this thing freeze couple times, but here are the problems ive had so far. sometimes when im receiving a phone call it will ring for 1 second then hang up, ring 1 second again, hang up, it keeps doing it, and after each ring & hang up session it makes it appear as a missed call. another problem ive had is with the End key, its not responsive sometimes, when i try to hang up a call i will think it ended because the dialpad went away but the call is still going and will go to voicemail or whatever. also if i havent turned off the phone for a while sometimes i cant access the messaging portion of the phone unless i soft reset. is there anyway to cure these problems, and am i the only one having these problems.
If your on a stock rom FLASH IT... the At&t Rom sucks, download advanced config and change the end call delay to something WAY LESS then 3000 milliseconds (which is a 3 second delay just for hitting the end key) mine is at like 50 milliseconds... put the ROMeOS rom for the Fuze on it or something else whatever you feel is the best i use ROMeOS.... oh and when the phone hangs itself up is it all the time or is it only when its in your pocket?
I have searched and all that came up are a bunch of issues with the screen not coming back on. This is not my issue, I wish mine would stay off. I have tried every method I know and my cheek keeps switching calls, hanging up, and dialing other numbers while I am trying to make a call. I've tried the power button method of hitting the power button and continuing the call, but even that hasn't fixed the issue. For the life of me, does anyone know of a "fix" for this? I'm about ready to break this thing in half. Thanks for any and all help.
One more thing, does anyone here use the google VVM? I had it working at one point on my D2, but ever since I switched to the TB I have had trouble getting it to work. I have tried the *71 or whatever method, but I still can't get it to forward. I can log in and see my old messages fine, but for some reason I can't get this one to forward the calls to GV for a message.
Ok, are you rooted, and of so, what ROM are you using.
I've seen some posts where people have problems with their proximity sensor, and they said blowing compressed air in the speaker (back of phone under kickstand) has helped.
Has far as Google voice goes, I've never had a problem setting it up. Again, what Rom are you running (though I don't think I've tried a Rom that didn't like Google voice.)
Sent from my HTC GingerBolt powered by Gingeritis 1.2.1
Bamf 1.8.6 remix. I'll try that. I just don't understand why it still comes back on after hitting the power button while on a call. I had it set up on my phone before changing roms, and I had it working on the D2. And I'm kinda being misleading by saying that it's not "working". I can connect to GV via the app, but I can't get the settings in the VM menu to "stick" as the GV. It keeps giving me the prompt that it is not supported by the "carrier". So I tried the long method of forwarding my missed calls to GV via *71 and two other * numbers seceded by my GV number. But for some reason the calls still won't forward if sent to VM. The only reason I have it is so that I can delete my messages without having to ever actually listen to them, I hate VM altogether, but verizon keeps giving me those popups when I have a message and they won't go away till they are either listened to, or deleted. And I'm not paying 3 or whatever dollars a month just so I can use something that is free though other methods. Thanks for your help.
My proximity sensor has never been the slightest bit reliable on any rom including stock
The proximity sensor on the Thunderbolt is located on the top front face of the device, inside the "V" of the Verizon logo. It can seen under bright light. It seems to be quite sensitive to dust, which causes the screen to turn on/off unexpectedly.
Carefully blow a bit of compressed air into the earpiece grill, and into the small gap between the glass and plastic housing shown in the circle, and it should clear it up.
I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.
Diversion said:
I've had problems with my proximity lately as well.. Been hanging up on people (it's very embarassing) during important calls. It's making me almost switch phones. This happens on ANY rom these days so it tells me it's a hardware problem at this point. Also, usually after I get a phone call and hang up afterwards, the entire phone is unresponsive until I hit the power button on top and hit it again to wake up, then everything is functional again. So annoying.
Click to expand...
Click to collapse
I've always felt like it was a hardware problem.
Hello,
Sorry to post this here. I've been following a few threads about x10 mini pro custom roms for weeks now but after signing up I am not allowed to ask my question to that specific rom there. It said I should post it here first.
I am using the [ROM]MiniCM7 Pro - V7x - GingerBread (2.3.5) by paul-xxx for more than 2 weeks now and it works great, I even have a battery life of about 14 hours now instead of 6 after I stopped using launcher pro and used the standard adw.
But I have 2 serious problems.
The first is that I cannot always unlock my phone. I know I have seen this question a lot but in my case the screen just stays black. There is no slider that does not want to slide. Just a black screen. If I slide open the keyboard I see the lights go on some times. When I connect via usb I can open a shell (via putty) and every thing seems up and running. Just the display is now showing anything.
When pushing buttons and sliding the keyboard several times I sometimes get the screenback. Some times just have to wait 5 minutes or so.
Does anyone have any clue what to do about this?
I tried killing the launcher process but that did not help, it just restarts and even if it did help I do not always have the phone connected to usb.
The other question is about missing calls. I had several missed call alerts while i was sure I was next to the phone all day.
Today I saw it happening for the first time. (because I got a missed call sms and right after that a call on the land line which was the same person who called my cell)
So I called my phone (after letting it go to sleep), used top to see whats going on. I saw the process android.phone.com starting to use more cpu (but not 100%) and I even saw the screen get activated (after 10 seconds or so) but no sound and then it went to voicemail and the phone went dark again but the sms with the missed call came in right away.
Is there a solution to this or are there more people have problems with this?
Any suggestions would be appreciated.
I recently wiped and flashed both my and my fiance's phones. Both the exact same phone, and I used the exact same install method and rom. (CyanogenMod 9) They should both be the exact same... right?! Well having two issues which only work on my phone, not my fiance's.
ISSUE 1
So I am aware that the Samsung Galaxy S 4G has a known issue with sending long texts which popup with a triangle saying something like "cannot send message". In the past, we've split messages using Go SMS pro. I recently found an app called "BIG SMS" and it fixed my phone so now I can send loooong sms messages like normal and with any app! I installed it on my fiance's phone and her's shows the triangle, it goes away, then shows it was sent and received but nobody ever actually gets it?! What does that mean and why would it not work on her phone?
ISSUE 2
My fiance mentioned to me the other day when she turns down her audio using the phone's side rocker, it goes from low volume to mute and stops without going to vibrate. On my phone, I go from low volume, to vibrate, to mute... Where's that option on her phone?
For your first issue, you would have to install another modem. KG4 is the way to go for long messages. Here's a thread with modems that are compatible with the SGS4G. http://forum.xda-developers.com/showthread.php?t=1192436
For issue two, does your fiancee have a different phone than you?
Thanks for the quick reply! No idea how installing a new modem works but I'll definitely look into it. We both have the Samsung Galaxy S 4G, and I flashed the exact same rom using the same methods, and installed the same apps. ONLY difference between our phones is that we just got hers and mine I bought when they first came out.
Installing a new modem is as simple as flashing it through a recovery mode. That's very odd how her phone goes to silent by the volume buttons. I have the same phone and cannot do that and neither can you.
Does she have vibrate off or intensity set all the way low? Maybe.
cm-9-20130227-UNOFFICIAL-galaxys4gmtd.zip
That is the mod I installed for both of us. I was used to the old android so now that we're on ICS, I'm not as familiar so I have yet to even find the intensity option. Under sound, we have the vibrate and ring turned on if that helps... That's about the only option I even see for vibrate without it being inside an app.
I am new to xda, I hope I found the right place for this problem.
I have a phone which is running android 7, the phone is supposed to be a Samsung s8, but I bought it second hand and it seems to be a mix of many things
Anyway, the problem I am having is that for no apparent reason sometimes when a call is received the phone does show the incoming call and does not ring. The call appears only as a missed call.
The way to reset that works is to delete the cache of the phone app. But that works only for a few minutes and then the problem recurs
It doesn't seem to be consistent, however sometimes it seems like setting the phone to do not disturb or silent mode triggers this behavior, and then even after returning to normal mode, the calls do not appear.
Another thing this that it seems like in safe mode I do not have enough this issue
I am not %100 sure about that either
Any idea what setting could cause this problem?
Thamk you to all who have ny suggestions