I need to ask this here since because I have never had this happen to me before in all my time of using Android!
THE EXPLANATION:
I have tried on two separate occasions, to install the I777UCKJ2 firmware on my phone. Everything seems to work well unless I am talking to someone. I can hear the other person very clearly, but they say that my voice goes in and out, almost like I am moving the phone far away from my mouth or something.
The first time I installed the firmware, I thought my phone could have been faulty (it was pretty much out-of-the-box at the time) or that I was putting my finger over the mic. I noticed thought that the latter was not true and that after restoring my firmware back to the stock 2.3.4 (I777UCKH7), the issue went away.
Last week, I tried UCKJ2 again. This time, I called my home phone BEFORE I did the flashing and noticed that the cell's mic sounded nice and clear. I then flashed the UCKJ2 firmware and repeated the test. Sure enough, my cell phone made it sound like someone was putting their hand over my mouth or something (randomly though). I reverted again back to stock and did the test AGAIN... everything was fine again.
I also tried UCKJ4 with the same results!
(NOTE: UCKJ2 was a one-click installer, but UCKJ4 had to be used with Odin. J4 had the kernel placed in Odin's PDA slot and the Modem in the PHONE slot. Everything worked fine on both versions besides this one issue.)
THE QUESTION:
Anyone else having these problems? I just think it is weird and kind of freaky since I am not able to notice the problem unless someone on the other line tells me... or if I call my home phone and talk to myself LOL.
Now, if i am correct, these firmwares are LEAKED, so maybe that is the reason why? Maybe they arent completely compatible with my specific phone?
Anyways, I am content with UCKH7 since it WORKS, but I was just thinking at the time, "Oh wow! An even NEWER firmware is available! Let's update!"
THE ADDITIONAL QUESTION:
Oh, and just to prevent me from having to open another topic:
Any idea when AT&T plans to OFFICIALLY release the next update (whatever it is) for our phones via OTA? This, I am just curious about because if they release the same UCKJ2 or UCKJ4 that I am trying to use, then I am honestly afraid to update!!!!
(sorry for the length of my post btw)
Related
Ok, a few days ago I tried to use kies mini to upgrade to JI6, that experience did not go so well. I stated in another thread my woes, and someone stated how it was my fault so on and so forth, it is what it is, so what, pay my bills
When I got stuck at the galaxy s load screen I was distraught so my first thought was nandroid back to previous settings, big mistake. Once I did that I was then stuck at the vibrant load screen but heard the t-mobile stick together jingle.
Then I got an idea, I flashed Kinglicks kernel, then the vibrant root, then JI2 gps and restarted...Viola my vibrant works again and in the condition it was in before I failed to flash JI6, only one problem though, my baseband is JI6, and kies mine now thinks my devices software version is unregistered.
My phone works without a hitch, but I'm now concerned that I may never be able to upgrade it again. One thing is very much certain my gps is locking on when I'm outside in seconds so I'm not entirely sure what the hell happend...I know this might open me up to some flamming, but like I said, so what, come pay my bills.
TheMightiest1981 said:
Ok, a few days ago I tried to use kies mini to upgrade to JI6, that experience did not go so well. I stated in another thread my woes, and someone stated how it was my fault so on and so forth, it is what it is, so what, pay my bills
When I got stuck at the galaxy s load screen I was distraught so my first thought was nandroid back to previous settings, big mistake. Once I did that I was then stuck at the vibrant load screen but heard the t-mobile stick together jingle.
Then I got an idea, I flashed Kinglicks kernel, then the vibrant root, then JI2 gps and restarted...Viola my vibrant works again and in the condition it was in before I failed to flash JI6, only one problem though, my baseband is JI6, and kies mine now thinks my devices software version is unregistered.
My phone works without a hitch, but I'm now concerned that I may never be able to upgrade it again. One thing is very much certain my gps is locking on when I'm outside in seconds so I'm not entirely sure what the hell happend...I know this might open me up to some flamming, but like I said, so what, come pay my bills.
Click to expand...
Click to collapse
Use ODIN to go back to stock, then update to JI6 using ODIN. Your phone should be back to registered version. I have done all these and I checked my phone with Mini Kies and it recognizes my phone and tells me that I am on the latest firmware. If you do not want to go through the steps do not worry, the devs in this forurms are always a step ahead of the game. I bet when Tmobile, releases 2.2, we will have to do a odin update anywayz.. Since tmobile, will not have enough time to test out every possible scenario we saw during the last release.
So this has been happening randomly on calls for about two weeks now. I'm still on Stock everything and would like to know if this is a known problem, if something is wrong with my phone, or if there is a fix? I'm past the point of returning and getting a new one and plus, I have grown atattched to this phone LOL.
I've tried hitting speaker and then turning it off but that doesn't work. Tried ticking mute and then unticking it, not working either. Reboot doesn't work. Resetting back to stock doesn't change it either.
Thanks to all.
AJ
Sounds like a typical ATT phone call. Would you and the person on the other end both happen to be on speaker phone? I cannot have a call via speaker to my wife if she is on speaker (which see insists on using) - there is too much voxing going on, I only hear every couple of syllables.
T
Sent from my SAMSUNG-SGH-I777 using XDA App
Not a speaker phone call. Seems like it happens mostly when I make calls from speed dial from my homepage screen. I can't conf
irm that last bit though lol.
Another question is this....I just turned my phone completely off and it had 42 % battery. When I turned it back on it now has 22% left.....what in the world is going on lol???
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
asjdwf said:
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
Click to expand...
Click to collapse
I need more details to say this for sure, but I THINK you may be having the same issue I had. Not many people seem to have this issue (only seen a handful across a variety of forums). So if you happen to be a fellow sufferer, then welcome to the club!
My problem was:
After the 2.3.6 update (UCKK6), the person on the other line had trouble hearing me because my voice cut in and out frequently, yet randomly. On my end though, they came in nice and clear. I often had to deal with people hanging up on me because they thought my call dropped or that I hung up, or had to deal with a lot of people repeating "hello? hello!? You there!?" as I helplessly tried responding and not being heard.
My Solution(s):
1) keep the 2.3.6 update, but flash just the 2.3.4 (UCKH7) modem. Everything on your phone will work fine, but you will get the following FALSE warnings (FALSE as in the phone says it can't do something, yet everything works fine anyways. These are only based on first-hand experience and may not happen to you.)
a) upon boot (not wake/unlock) there will be an error notification about you not being able to access your external memory card due to security reasons... don't worry, its bull.
b) when using your phone as a mass media storage device, you will get a notification about the mass storage function not being able to work... this message is also bull.
2) Or you can just completely return to 2.3.4 (UCKH7) and either ignore the update prompts or freeze the process until a newer update that hopefully fixes our problem (or ICS) is released.
I did (1) for about 2 weeks then did (2) after reading all the battery complaints blamed on UCKK6. It reverted just to play it safe with battery life (plus they say that "if it ain't broken, don't fix it" and for me, UCKH7 wasn't broken and the update definitely broke it).
Wow, that sounds identical to me except its they can hear me but I can't hear them LOL. I reverted last night with odin one click downloader and the stock kernel for battery life so we will see what's going to happen today. Is this a phone problem physically or is it software?
Thanks
AJ
For me, its a software issue (modem to be specific) because it only happens on UCKK6 (and the leaked UCKJ1, UCKJ2, and UCKJ4) and when on UCKH7, my calls are as clear as a LAN line.
I say that if the problem still exists now, then its hardware. In that case, try contacting Samsung for a replacement if your ATT warranty is up. You could try ATT too because its a defective phone and they may still do something.
So, without writing a big long explanation, I'll cut straight to the chase and tell you what's been done with some light background.
I woke up one morning and my network was inactive. At first, I thought it was maybe some mobile network issue. One day later, still no connection.
-Odin'd back to stock twice
-reflashed multiple roms (including all the usual formats)
-flashed 5 difference ICS modems (KA5,6,7 and KB1,5)
IMEI error popped up after a new rom flash for those that are curious, but I lost my original a while ago and just adopted a generic. Never had an issue with it affecting my mobile network. I remember having a modem issue before when ICS was in it's discovery phase and flashing roms, but nothing where the modem just stopped while it was running/on.
I just wanted to see if I forgot something before I officially sentence my phone to death. I wanna say maybe a freak surge nuked it or something. That's about all I can think of since I know my way around android. Any ideas appreciated. maybe there's a way to check my hardware I forgot about.
Thanks!
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.
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Something is wrong with the software hes using if working on regular sense build and not cm,best aaking in the rom developers thread.
paradoxed said:
I work with a guy that owns an ATT m7. He isnt too knowledgeable on rooting however he does flash his own roms and has some idea about it all. he told me he bricked his phone and thinks that after flashing so many roms he fried something with the radio. The phone does not receive a signal.
I took the phone home for him to fix. Just to test I flashed CM11 and just as he said radio was not working. It showed bars but if i tried to make a call it didnt work. I figured this would happen anyways so i carried on with obtaining s-off. I then flashed a 4.1.2 RUU. I put my sim card in (straightalk) and at first it didnt work. after a few minutes I looked again and vuala I had service. I added in my APN and everything seemed to go smooth. I did notice that periodically I would look at the phone and see it said "emergency calls only" but it quickly fixed itself (my s4 does the same thing so it could just be my area)
I used the phone all day and it seemed to be fine. Texts and calls worked perfectly. Feeling confident I then rooted and installed twrp. I backed up the stock rom and flashed CM.
No service.....
Anyone have any clue whats going on? I am currently RUUing again to see if it will work again and I am sure it will.
Im having trouble understanding this issue as I feel that if there was a mismatched radio then RUU fixed it. How would CM make this not work? Only thing I havent tried is a different rom (this was a nightly so i dont know if it has an issue) I just really don't feel like going through all the trouble again just to find out its not the ROM.
Hopefully someone has some insite.
Click to expand...
Click to collapse
Yes but after 4.1.2 RUU it still cuts data on and off. Is it possible it's a bad radio or should we try a differentRUU?U
first id say get to an area where the radio reception is better, get an att card and not straight talk and test.this could very well be a hardware issue as well, but it seems more of a simcard issue/software issue than a hardware issue