Hi, my name is Daniel and I am in serious need of some help. I have a rooted T999 for T-Mobile. TWRP recover installed. I am running into some frankly strange issues. If I am in a call and I am not using the speaker, no one is able to hear me. If I am in a call, they can hear me but with occasional clicking sounds and very bad quality. I tried re installing the baseband but it does nothing. Can anyone help me please?
Baseband version: T999UVEMJC
Thank you!
What Rom and Kernel do you have ? If on Stock then can you do factory reset ?
I am running complete stock. The only thing I put was TWRP 2.6.3 I believe. I have factory reset a few times to no effect.
If you are not on Touchwiz Stock 4.3, then please switch the Baseband to LJC.
Will that solve the mic not working without speaker?
Yes I suspect it might.
Ok, I downloaded the correct basebadnd you told me and flashed it through TWRP. I booted and it showed no signal. Then I went into setting, networks, and mobile networks and it said please insert SIM card. I cleared cache and installed the old baseband and it works but in the same manner.
I don't think you mentioned your Current Rom. Please also provide Kernel.
I have taken a screens hot and attached it. Should help answer your question, I hope
Please if possible, try a AOSP Rom instead of Stock Touchwiz. At the least it will rule out hardware issues. If that's not an option, and SELinux is enforcing, I don't know if you can change.
Yeah, I tried a AOSP rom and no dice. I was looking online and saw that I am actually not the only one. Other people who took the 4.3 update seem to be having this issue.
The AOSP Rom took out the TW Rom as a culprit. If you still have an issue the probably a hardware issue.
Hey guys so I was looking and it turns out I'm more clueless than even I originally suspected. The ROM I originally flashed was based off of Touchwiz. What ROM should I be flashing because I cannot seem to find one that is aosp to the core?
The one I was going to try was Dirty Unicorn but I cannot tell if that even is what I should be trying.
Try Liquidsmooth, Pacman, SlimBean and so on. There are a number of quality Roms out there. I only suggested 3 that first popped into mind
Alright. I'll try those.
Related
Hello. I have a problem with sound in my kaiser with Android. I tried 2 systems [Cynanogen mod 6 (Froyo) and Myn's Warm Donut], 4 radios (from 1.71 to 1.65) and 2 kernels. Sound never appeared. Why?
what zimage or nbh you using if you are using a older one it might have problems
Did you mean kernel? the newest from this page:
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
it may be that you have muted the media volume in settings.
No. I don't have any sound. Not only media. When someone calls to me, I cannot hear him too and this person cant hear me too.
Audio issue
I have the same problem. I tried different builds and nothing helps. Any suggestions??
Just a thought, but have you tried flashing a stock rom, then flashing to nand again? Flashing a stock rom clears the entire nand, leaving no possibility of stray bits of data left from custom roms.
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
<refresh>.
Mu_aawiyah said:
I have to say, I get the same thing, but with a slight variation. Sound works for me up until i make at least one call (but could happen before that). Once I make that call, either during the call, or after, the sound is gone. I too had myn's donut, and then frayo, and both times, the exact same problem. I will try to flash the stock rom, and then back to android, but it is a problem that I also share.
This is my first post on xda, so please be nice!
Click to expand...
Click to collapse
Yeah, flashed it back to a the most recent stock rom, and then back to andriod.. how works perfectly. Sorry i didnt tell you guys earlier.
I think it was to do with the radio thingy-ma-jig. I flashed it with winmo 6.1 from htc website, and then back again.
Now i'm runnying frayo.
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Wagierek said:
I flashed the newest stock rom from htc site too, then 1.65 radio, but it didn't help :/
Click to expand...
Click to collapse
That is most likely because you didnt flash it right. take the .nhb from it, plug it into your sd card and flash it from sd. try that.
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Wagierek said:
I'm not stupid. I always flash anything like that-not via CustomRUU-because I have damaged my USB socket and now my Kaiser cannot be recognized by computer.
PS: Today when I booted my Kaiser, next to ANDROID word, I saw "handset status changed to 1". When I rebooted, it didn't show. What's this?
Click to expand...
Click to collapse
Well, with regards to how I got it fixed (the detailed explanation), i flashed it with a custom winmob rom initially, but surprisingly, the same problem i had with android was happening with the winmob. I could make a call after reboot, but after that call, the sound completely died, and the camera did not work. So i tried to flash with the latest stock rom. I've uploaded the actual roms i used on my public drop box folder here => "i tried posting the link, but because i'm new, it wouldnt allow me...pm me"
I am not a professional on flashing, rather i am a beginner. My tytn 2 is a european T-mobile version. I tried to flash it, it did it half way...then stopped! I tried to do it again, but then it just said "...loading..." and would not go past it. But when i booted to my custom rom, it was still there, but the problems had gone. I guessed that it flashed the radio, and nothing else.
When i then went to android, it worked perfectly.
That was my journey.
I hope that helped... maybe.
Unfortunately, it didn't help.
Any other ideas?
I solved mine by changing radio ROM,but i lost sound and camera in windows,any ROM that fit both android and windows???
What version did you flash?
1.65.14.06
Me too!
I flahsed froyo last night and didn't test after makng calls. I'm having the same issue (lose sound after a phone call). I followed the sticky guide and sim unlocked the radio before flashing (which I think I had already done before). I will try changing radios when I get home to see if this resolves the issue and post my results.
Update: I flashed 1.71.09.01 on my ATT Tilt and this fixed the issue. Now sound and camera work great. Phone runs faster also!
I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions
On NF1 based roms, does anyone have issues answering calls like I do? I keep swiping to answer and it won't work, most of the time I miss the call. I didn't have this issue on an older build of TW.
No problems here. Bad flash, maybe?
Sent from my SM-N900T
Have rebooted your phone anytime lately? Also, if you have lots of tweaks you may be slowing down your phone responses.
Weird issue. I download two different ROMs from different threads, with the same issue. I don't known what the problem could be. I don't usually run a lot of tweaks on TW, I keep it mostly stock most of the time, except, that it could be related to a custom kernel. I'll try a stock kernel
Haven't had that issue. That's including experiences from 2 different note 3's. Stock and rooted.
Tried stock kernel. Same issue. I'll have to try to go completely stock and see if the problem returns. I don't know what it could be. Everything else is fine otherwise. Am I able to run the older kitkat ROMs with the newer stuff? If I can, I'll try to confirm that I don't have an issue with those.
EDIT: happened to try the Canadian S5 port, and I have no issues with answering calls. I will just use it for the time being.
I'm still having this issue and I'm completely stock. I don't know what's wrong. It doesn't exist when I'm running the S5 port or an AOSP rom. Anyone have an idea?
EDIT: Found out my baseband was outdated. It didn't update with the firmware update from Kies. I rooted the stock rom, and used Triangle Away, then Odin flashed the modem, things are well now.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.