yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M8)] Corvus_:
iPhone 4 was the most recent one I can remember but most of what i refer to was pre-smart devices. In the iPhone's case there was a quick hardware revision made to correct the flaw. Honestly though in doing some Googling to back up my opinion I can't find any evidence so I'm gonna have to say you're correct.

I still stand by that no one would be talking about this if it wasn't pushed so hard by the media, both social and traditional, and it's something that could be basically entirely avoided if we treat our phones as phones and give them the attention that a $500+ device should have.
[Galaxy S 5 Q&A, Help & Troubleshooting] kruso:
... Anyone know which APK that are related to the popup functionality?

Thanks
[T-Mobile Samsung Galaxy S 4] thair7391:
To anyone more of an expert than myself on these matters (which I presume to be a large portion of users here), I'd greatly appreciate any help that can be provided. I'd also like for this thread to be a central collection of baseband/modem functions, behaviors, troubleshooting, etc...

I've had a T-Mobile S4 (SGH-M919) for a while now and have mostly used CyanogenMod derived ROM's and as of lately, more Google Play Edition/Nexus type ROM's (which generally appear to be written for the international i9505 and hence show the model number of my phone to be such; this may or may not be relevant). All of the sudden, the other day during a phone call I received, there was no audio on either end of the call. I couldn't hear the caller nor could the caller hear me. This also happens if I initiate the call. I know for a fact that the media speakers (speakers used during speakerphone) as well as the earpiece speaker are perfectly functional so it's not a case of hardware failure where it works on Bluetooth or speakerphone only. As soon as a call initiates, you hear no ringing or audio once the caller answers other than the tone when the call ends/disconnects. First thing I tried was switching from ART back to Dalvik just for the sake of troubleshooting. Second, I tried clearing the cache (and Dalvik, just for the hell of it). Still no success. So next I try a completely different ROM. I was presently on a GPE ROM with the Samsung kernel so I switched to plain CyanogenMod with a custom kernel. I even went back to a stock ROM! No success either way!!

It was at this point I decided that it had to be a hardware/firmware issue since the issue remained when changing ROM's so I naturally assumed baseband/modem. I don't understand why this issue just magically occurred one day when I hadn't changed anything, but I thought that if I reflashed a clean modem image or and updated one, then maybe it would fix it... I was on MDL so I reflashed the MDL modem. No success. Then (and here's where I f****d up), I tried flashing what I THOUGHT was a stock NB4 firmware file in ODIN. Turns out that despite being labeled as stock, it had a custom kernel built-in and tripped my KNOX counter (FFFFFUUUUUUCCCCCKKKK!!!) Well, since I really only intend to use AOSP/CM based ROM's, it's not such a huge deal for me but still, it sucks.

Here's where I had a break: Yesterday, I tried flashing the MDL modem again, then that didn't work so I tried flashing the MK2 modem. I booted up, made a call, and it worked! First time! Well, that was short lived success because I tried another call immediately after to verify and it started all over again. Now, even reflashing MK2 won't get it to work even once like it did this one time.

Does ANYone who understands baseband and modem firmware much better than I do have any insight or instruction on what I can do? Because of this one issue, I have an otherwise perfectly good S4 that I can't use just lying around. I've had a Nexus 5 for almost a year and love it but I just destroyed the screen after a drop the other day and wanted to switch to the S4 temporarily until the Nexus 6 comes out. ANY IDEAS????
[T-Mobile Samsung Galaxy S 4] faiyo:
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
[T-Mobile Samsung Galaxy S 4] thair7391:
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
[T-Mobile Samsung Galaxy S 4] faiyo:
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband

I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).

Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.

About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
[T-Mobile Samsung Galaxy S 4] thair7391:
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!

I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...

I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.

As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
[T-Mobile Samsung Galaxy S 4] faiyo:
I really have no idea about aosp roms for this device because i only used touchwiz to keep samsung features.. so i have no knowledge about firmware compatibility. I would think the creator of the rom should specify any firmware requirements.

On the thought of hardware failure, and i know you said the speakers work, but did you test the sim card slot? Perhaps it needs to be cleaned? Maybe the sim card is partially failing so try a different card? Maybe you cut it and it's loose (you wont believe the crooked sim cards i've seen). I think it's worth pursuing since you said it worked once and not again.. maybe you had just taken the cover off while flashing stuff and touched/pressed it but it's losing contact again after flexing during use. I dunno dude, the kind of call audio issues i've had were always resolved with a reboot & making sure the modem matches the touchwiz build.

Please make sure you are running a full stock firmware package & keep the touchwiz rom consistent with it. Some firmware packages are partial components
[T-Mobile Samsung Galaxy S 4] thair7391:
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
[T-Mobile Samsung Galaxy S 4] Kriptik210:
For starters, up until a few days ago, I ran all types of ROM with an MK5 boot loader and 3 different modems and never had a call issue. After that said, I read a few months ago about a guy had your same issue. He ended up getting a new sim card and he got is audio back. He also had reception issues before getting the no audio issue.
[T-Mobile Samsung Galaxy S 4] serio22:
Try flashing the firmware again, some have to flash it twice for the bootloader to update, which may the trouble. If that doesn't work try a new sim like it was suggested before me
[T-Mobile Samsung Galaxy S 4] thair7391:
I know it's been a while but I basically gave up and just recently came back to it. I've since bought a Nexus 6 so it's not a priority issue anymore however I would still like to fix this otherwise perfectly fine Galaxy S4 that I have lying around! I seemed to believe that there was a special combination of custom ROM and specifically the MK2 modem that would sometimes cause the audio to intermittently work but it appears I was wrong. I flashed the full stock NH7 firmware/baseband etc back to my phone twice as suggested and NY audio worked! For a few calls that is... Then it stopped working again. Sometimes I could clear cache and reboot and it would work! Once or twice anyways before crapping out again... The bottom line is that there isn't a pattern aside from a cleared cache that makes the audio work again before it stops soon after which unfortunately leads me to believe it's a deep rooted hardware issue in the baseband itself. Anyone else have ideas?
[T-Mobile Samsung Galaxy S 4] serio22:
Other than trying a new sim, I can't really think of anything else except to make sure the bootloader really did update. Download Samsung phone info from play store and check bootloader info to make sure it was updated to NH7
[T-Mobile Samsung Galaxy S 4] thair7391:
Unfortunately it is completely updated. I tried a new SIM and everything works still except audio in phone calls, including ringing. I guess it's hardware... Guess now I just have an internet browsing MP3 player with web browsing capabilities. :(
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ironside2011:
Well,just this week nobody can hear me when I make calls or they call me.

I've had my phone work perfect since September 2nd when I bought from Verizon.

It runs 4.4.4 totally stock. Tried clearing out the microphone port and only helped a tad.

Is there a way to fix it without a return exchange?
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] GuestK00143:
I would take it back, mine has been flawless since I got it shortly after the release date.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] ironside2011:
maybe

I was thinking about that. But maybe a factory reset would help
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Chopstix9:
That's the first thing I would've tried !! I mean heck, if my phone isn't working, it's time to drop 5 yards and punt ...
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
Well yeah, but hard resets are always a pain. And most of the time don't fix what's wrong
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] BigBot96:
Go exchamge it. My first S5 (this is my third) had a microphone issue where my voice was muffled and hardly audible. Exchanged it and never looked back.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
I'm gonna go Monday to exchange it. Hopefully it doesn't decide to work while I'm there. Happens a lot to me.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] BigBot96:
Lol yeah... Same here. They didn't believe me but I was within my 14 days so they swapped it with a new one. My second S5 had a black speck right in the middle of the display.. Like a peice of bark under the digitizer. 3rd times the charm lol

Good luck!:good:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
Unfortunately I'm beyond the 14 day exchange policy... Hopefully they be nice about it. Since I can't really use like intended
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Chopstix9:
You said U R running totally stock. What's the pain of a hard reset? Backup appz and it's a snap to restore phone to pre-wipe state. I have odined back to stock, gone through the whole process to root again and restore everything a couple of times now. If anything, that would be considered a pain but it really ain't chit ...

You can be sure that's prolly the first thing the rep is gonna try in the store before giving you a new phone.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
Yeah I know.... I just don't like the whole hard reset process. I'm lazy about it
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] BigBot96:
If there is a problem might be best to go through Samsung for a repair instead of Verizon to just get a refurbished device. That's what I'd do.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] shroyede:
Before you reset/return...take your battery out for 10 min. or so...and then restart your device...maybe the battery voltage or calibration is causing the speaker interference...it's worth a shot.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
I did notice its been getting rocket hot a couple of times this week.

I haven't made any calls or received any since I factory reset it 2 days ago. Maybe it works again, I'll try tomorrow than go to Verizon
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
Well I think it was the battery. The microphone seems to work now. Did 3 voice recordings. All of them came out crystal clear with and without background noise.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] shroyede:
Good to hear...it wouldn't hurt to purchase a new charger too.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
I'm gonna hang on to the charger, its the first offical charger I've had in awhile. My DINC, nexus and gs3 all burned through their real charger oddly quick. I think its the weather where I'm from its been 111°-120°f for all of September
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] shroyede:
Hot damm...try to stay in the shade...lol
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] simonkelso:
Yeah, i leave it inside now unless I need to bring it with me
[Galaxy S III Mini Q&A, Help & Troubleshooting] icewavedesign:
Hello guys!

I got a new galaxy s3 mini (i8200) today so I tried to install a custom ROM since the installed android version was pretty old. I chose cyanogenmod 11.0 from novafusion and I tried to install it using odin. During the setup I got an error:

<ID:0/011> NAND Write Start!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

So I ended up with the phone soft-bricked and I decided to try to use KIES for firmware recovery but without success. So now I have two problems:

- The phone is soft-bricked

- I guess it ran out of battery and whenever I connect the phone to the computer (or even try to charge it) it ends up restarting itself.

Video -- the problem:

[ LINK ]

What should I do now?
[Galaxy S III Mini Q&A, Help & Troubleshooting] cviniciusm:
http://www.gsmarena.com/samsung_i8200_galaxy_s_iii_mini_ve-6190.php

CPU: 1.2 GHz dual-core Cortex-A9

NovaFusion is based on NovaThor.

You can cry now...

... And good luck !
[Galaxy S III Mini Q&A, Help & Troubleshooting] jakot:
There is a sticky unbrick thread here:

http://xdaforums.com/showthread.php?t=2159660

For the charge problem, I think it works in download mode, try to enter that and leave it for a while.

EDIT: missed that this is an i8200... Do you have a backup of stock? If not, I guess you will need to hunt one down...
[Galaxy S III Mini Q&A, Help & Troubleshooting] cviniciusm:
Forget. My bad.
[Galaxy S III Mini Q&A, Help & Troubleshooting] icewavedesign:
I'm trying but I only found few options available and it's so annoying to download 600+ mb when the speed is limited to 30 kbps by the file host.

LE: Is stuck in download mode (Odin Mode) and when is charging the same thing as in the video happens.

Let's say I will be able to charge it, should I flash the stock rom image using odin or there are any other steps that I need to do in order to un-brick it?

.
[Galaxy S III Mini Q&A, Help & Troubleshooting] prototype74:
Your system or boot (kernel) partition is corrupt because you tried to flash a ROM for GT-i8190/N/L model only. You should flash a stock firmware for GT-i8200 model (available on sammobile.com/firmware) if you want a working phone ;)
[Galaxy S III Mini Q&A, Help & Troubleshooting] icewavedesign:
That's true, it was my bad and I realized that later when the phone was already bricked. Do I also need "PIT" file (repartition) or flashing the stock firmware would solve the problem?
[Galaxy S III Mini Q&A, Help & Troubleshooting] prototype74:
You don't need a PIT file. Just flash a stock firmware for your phone model and everything will be ok ;)
[Verizon Samsung Galaxy S 4] Chuck2003:
Hello I have a verizon galaxy S4 that im trying to unroot. It has safestrap installed and has MJ7 loaded onto the phone.

I tried using the below method to unroot my phone http://xdaforums.com/showthread.php?t=2507253

When I tried doing this method I get Odin sits theres for a few minutes and then says FAIL. Now when I try to reboot it says firmware upgrade encountered an issue. Please select recovery mode in kies & try again.

Does any one have any suggestions ?
[Galaxy Tab S General] bobiscool07:
Aside from youtube, is there another place where you guys get Quad HD videos to view on this tablet? I was unable to locate any sources, as I believe netflix and play movies only goes HD.
[8525, TyTN, MDA Vario II, JasJam General] bidinot:
Hello Everyone,

I am having a wierd issue with my HTC Tytn.When my Data connection is active I cannot make or recieve phone calls.Any incoming call goes straight to voicemail and any number I dial the phone will display "call ended" before it even starts to to ring. The minute I close the data connection the phone works again.I have updated my ROM to the latest English ROM.Could my unit be defective?

Thanks in advance!!!
[8525, TyTN, MDA Vario II, JasJam General] Pawlisko:
Hmmm that's weird.

Your TyTN is acting as class C device (Data or Voice), and in fact TyTN is class B device (Data is suspended while on Voice).

Is your unit defective? Possible, but... first backup your TyTN completely, then re-update full ROM, set up data connection and call to check it while on active transfer. If it will be OK - your unit is OK and this is software/registry problem, if not your unit is might be defective. This is the quickest way to determine.
[8525, TyTN, MDA Vario II, JasJam General] Quilliam:
My device does this as well, but only when connected to Slingmobile.

Other "always on" programs are not affecting me.

Not sure if this helps or not :( Just trying to add more data.
[8525, TyTN, MDA Vario II, JasJam General] neo88771:
data causing call dropouts

Hi,

Hope this helps, but here in Australia when using the Telstra HSDPA network on UMTS850, when i'm connected to a data session, I can't receive calls and the caller gets the "phone is switched off" message. If I force the phone to use the old UMTS2100 network, the phone will pause the data session and allow the incoming call. On another forum I have read that this is due to a limitation in the Ericsson 850MHz hardware which the telco is using on their mobile towers and they expect an upgrade to fix it sometime in January. I don't know if this is 100% true, but it is what i have read :)
[8525, TyTN, MDA Vario II, JasJam General] christopherwoods:
If I have a data session in progress it gets disconnected whilst a phone call is in progress (I can receive calls fine, although I have had one or two occasions when people have rung me and it's gone straight to voicemail without notifying me of the call). After I hang up, the data session is reestablished.

Using T-Mobile in the UK for what it's worth.

This is a very weird issue, sorry I can't offer any more info or advice.
[8525, TyTN, MDA Vario II, JasJam General] phatphat:
I'm on T-mob Flext WnW and have the same issue. When I have my data connection established (either gprs or HSDPA) anyone that tries to call goes straight to voice mail. I can make a call which temporarily stops the data session and then re-establishes it after I hang up.

Is this a known issue on T-mob?