This is very strange...
I had flashed to the WM6.5 beta4, and had problems with it, so I then flashed to the Reloaded R4 1.4b1. I then noticed the next day when I received a call I could not hear the conversation through the ear piece.
I then made a call and I could not hear through the earpiece, but if I turned on Speaker phone, I could hear through the speaker phone. I rebooted a few times, changed volume settings, and I could sometimes hear through the earpiece. There seems to be no correlation to the activity and it working, but I know the speaker works.
I figured it was a problem with RR4 since it is beta, so I went back to 1.3.0 and problem still persisted. I then tried DCD 4.1, and the problem still exists.
Being frustrated, I updated the RADIO rom to 3.42.50 from 3.42.40. No luck. I then went back to 3.42.40 and still no luck.
I tried loading the audiopara.cab and it seemed to work for one call but then stopped the next.
I am using the latest DCD Carrier settings for VZW.
I'm pulling my hair out, and I'm wondering if anyone has a resolution for this?
It appears to be a hardware issue, and an FRU is in the mail.
exact same thing happened to me two daya after going from stock to bitserve 1.3.2 on my second xv6800. im not blaming anything or anyone. i want to add that using the speaker phone worked and using bluetooth worked but phone ear speaker wouldn't. glad i have full warranty on the phone. getting replacement tomorrow 2/4/09
Did either one of you try a hard reset and going back to the stock ROM? Is going back to the stock ROM even possible on the MR2?
Bitserve,
before I brought it into VZW, I used the Titan Relocker to go back to SPL 2.06, then I used MR2 to update.
Speaker problem still persisted...
Could it be something that came along that is only modifiable from QPST like the GPS assist IP settings? This would mean the flashes wouldn't have affected it to fix it?
My old phone goes back tomo, so let me know if you want me to try anything
MrTek said:
Bitserve,
before I brought it into VZW, I used the Titan Relocker to go back to SPL 2.06, then I used MR2 to update.
Speaker problem still persisted...
Could it be something that came along that is only modifiable from QPST like the GPS assist IP settings? This would mean the flashes wouldn't have affected it to fix it?
My old phone goes back tomo, so let me know if you want me to try anything
Click to expand...
Click to collapse
I don't know if you realize this, but flashing doesn't do a hard reset. I'd recommend doing a hard reset after flashing back to MR2 to see if the problem remains. I know nothing about verizon and their wacky ROMs. If you had a Sprint phone, I might have some ideas. Sorry.
I'm curious now...
What is different about the "reset" after flashing vs initiating a Hard Reset? I've done both, numerous times, and they all seem to leave it in a pristine state after the first load up.
I will try and force a hard reset, but I'm not sure how it differs...
i flashed it back to stock because i was going to take it back to verizon(still under warranty) checked it with the stock rom i forget version # sorry (2.09 i think) but the radio was something like 1.30 and still did NOT work, ear speaker was "muted".
ps i never did mr1 or mr2 went from new(stock) to dcd 3.2.6 then 1.3.1 reloaded then back to verizon
Related
I am having problems with several keys on the keyboard. It is not consistent but just enough to be annoying. I get duplicate spaces, 'I', 'O', and several other keys. Any suggestions on how to remedy?
Thanks!
Me too
I am having the same problems. It all started after I updated the new Sprint ROM. So, if somebody has any insight or knows anything about this it would be great if you would pass it on. I'm going to go into sprint tomorrow before work and see what they say. Thanks in advance.
What have you tried to do already?? What ROM are you running??
I'd start with a Hard Reset. (Press both Soft Keys and hit the reset pinhole). If that don't work, try flashing the ROM again?
Thanks for the posts. I am using DCD 3.0.1. I have already done a hard reset and re-flashed. Interestingly, when I do a reset I see the PPC Geeks splash screen leftover from prior to DCD's 3.0.1.
Perhaps I should go back to the Alltel stock rom and see if it persists. Thoughts?
I had the same problem...with the same keys. Mine also started after flashing DCD 3.0.0 ROM (though I think that was a coincidence). The problem persisted after I flashed back to the latest Sprint ROM. I just had Sprint replace it under warranty.
count me as having these problems as well.. and it's happened ever since I upgraded to a dcd rom in feb..since then i've flashed my rom 6 times I think and each time, this problem pops up at random...really annoying. and ya i've hard reset, reflashed and all that.. this one problem alone had me considering buying a blackberry cuz I email my clients a lot from my phone and when i have to hold down O or A or R to make sure the letter registers, its annoying..any clues?
My phone has done this too. I recall it happening after flashing to the beta radio and DCD's rom. It seems like it has gone away, I'm running DCD's 3.01 on Verizon and haven't noticed for a month or so.
I flashed back to the original Alltel ROM and so far it seems to be better. Keep you posted.
Flashing back to the original Alltel Rom seemed to have resolved this issue. I may try dcd's again when 3.0.3 is released but for now, the keyboard is important enough for me to lose GPS.
I found a supposed fix at http://forum.ppcgeeks.com/showthread.php?t=23875
it seems to be working for others with this problem. Post here at xda if it does happen to work for you.
Occasionally I will try to make a call and will connect, but will not get any audio either way, this is also happening on incoming calls.
The only way to fix this is to reboot the phone, I haven't tracked down what causes it to start doing this, but has anyone else had this problem?
I never had this problem with 3.2.3.
This started to happen to me recently too. Can you end the call, I couldn't. Also, is your phone running dog slow too? I ended up having to hard reset my phone. Works great now.
vbundi said:
Occasionally I will try to make a call and will connect, but will not get any audio either way, this is also happening on incoming calls.
The only way to fix this is to reboot the phone, I haven't tracked down what causes it to start doing this, but has anyone else had this problem?
I never had this problem with 3.2.3.
Click to expand...
Click to collapse
try reinstalling your radio.
Same problem here
I warranty-replaced my first Titan because of these exact symptoms with both the stock Verizon ROM and dcd 3.1.6. I got my new phone (this time with 3.2.6 and 3.42.50) and still the same problem, although less frequently now.
I haven't found a solution yet, but I'll let you know if I do.
We've got 5 phones running 3.2.6 in my office. I was having quite a bit of problems running 3.2.6 and the 3.42.30 radio, it's happened once in a week with the 3.42.50 radio.
Phone runs really good otherwise, but having the actual phone part of the Titan not working 100% is very frustrating...
I was also having the problem and sent back the phone and got a new one then updated to 3.4.4 and it has continues to happen any ideas why
Over the past week or so my phone has decided just to cut off while in my pocket, it turns back on right away. I can't seem to pinpoint any particular time that it turns off because I don't know it's off until I look at, although oddly it seems to happen only when I am at home. It is rooted and running BAMF with new radio and the default BAMF kernal. Also there was a full cell phone coverage outage in my area recently if it has anything to do with the new radio.
Possibly overclocked your kernel too much? Or maybe with the new BAMF feature of waking your phone on the volume keys you are waking and rebooting your phone without realizing it?
Thanks for the reply, I will try changing kernal settings and see if I notice any change.
fireminion said:
new radio
Click to expand...
Click to collapse
There's your problem, I'll bet.
I was fine with the "old" (original) radio revision, but I upgraded to the rooted, but otherwise stock "leaked" version, which included the new radio stuff. It seemed to be fine at home, but I was travelling out of town today, and it rebooted at least 5 times this morning. 3 of those times, without having really done anything with the phone. After a reboot, I'd connect to the WiFi at that site, then just let the phone sit on the table - it would reboot again within an hour. I did try with cell set to both LTE+CDMA and CDMA (auto), didn't seem to make a difference. Maybe it depends on what brand of local BSS/BTS (Nortel, Lucent, Motorola).
So, I flashed the old radio back on (didn't change anything else). It went the rest of the day without rebooting.
I realize this is just one anecdotal bit of data, but it sure points to the new radio, in my case. If you look around, others have blamed reboots on the new radio release, too.
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Diabetic said:
So, this is my short story:
I've had this phone for 6 months. I've had it rooted for about 5 months. I've used tons of Roms, and have had no problems whatsoever. I have several Nandroid backups as well, each dating around 2 months a part (each).
/End Story
Problem:
All of the sudden, I called a friend to find that the in-call volume was EXTREMELY low. I turn it up all the way and could only faintly hear him. He sounded a mile away. I had to turn it on speakerphone to finally make out what he was trying to say.
Things I've Tried:
I've tried going back to each of my Nandroid's, when the sound was working, and nothing was fixed. I've tried Factory Reset with no results. I've wiped cache/dalvik cache - nothing. I've tried messing with Hearing Aid settings - nothing. I've tried turning the volume all the way down in the call, and then turn it all the way up to see if it fixes it - no results.
Currently I'm running the Infected Rom 3.5. But I tried calling people on MIUI, Sense 3.0, etc, with no results thus far.
Question:
WHAT could possibly be causing this? It's not like I blew a speaker, I've never done any volume adjustments on my phone with an app or anything. The receiver still works, as I can hear them, but they sound near non-existent until I switch to speakerphone.
Any guesses/suggestions?
Click to expand...
Click to collapse
As with more abnormal issues such as this, the best recommendation, in my opinion, is to revert to a stock ROM, kernel and clear the /data partition.
This will ensure the device is running 100% stock software. If the issue still persists with stock ROM, kernel and a cleared /data partition (test before loading 3rd party apps) the final conclusion would be a hardware related issue. At this point, should be able to take the device in for service.
If the issue disappears on a stock setup, then you can start eliminating possibilities such as a specific ROM, kernel or 3rd party apps which could be impacting the volume.
Hope that helps!
^
I pretty much did as suggestion, but I decided to put on an almost-stock ROM (with some visual differences) to sprint first. When I told the technician the problem, he noticed the rooted phone and said that it was because of my software. I knew it wasn't, because of all the resetting I had done, different nandroids, etc, and that it was the in-call receiver. He stated he was 100% sure it wasn't.
I went home, went back to full stock. Same problem. Took it to a different sprint store and they said that there was a connector issue, and since they didn't have the part - they will order me a new phone for 38 dollars (I didn't have a warranty).
Not too bad. Too bad the d*ck at the sprint store couldn't have looked at it first, as he would have seen that. But oh well. Whatchya gonna do?
Decided to post this in case someone has similar issues.
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.