Develop Bugs

Galaxy Nexus Signal Questuon...

I know about the Baseband issue in these phone that they're not getting good signal at all well I think I'm suffering for this is while because I have been dropping calls lately and I don't understand why my friend has a nexus is able to get pretty good signal without Abu drop calls so I was wondering if you guys think I should bring my phone to Verizon so they can replace it or should I wait until the software update that supposedly going to fix this signal issue...
Let me know in the comments please
Sent from my Galaxy Nexus using XDA

I think that this is more of a matter of what you want to do. I am not sure what Verizons return/exchange policy is but if you are having problems and can take the phone in and exchange it what have you really got to lose (besides having to re-setup & customize your phone )
If you are OK wwith dealing with the issue (and Verizon has a very liberal return policy) and you want to see if the software update fixes it then wait and see.
Personally, I had an issue with my first GNex that I bought and ended up exchanging it...this resolved my issue.

I doubt it's a a baseband issue since there was a time you had good call quality correct? Reinstall your original baseband or at least do a wipe. Are you using custom ROM? I'm not a programmer nor do I have alot of background but I don't think its hardware as well because it should be an all or nothing kind of thing.
The only think I can suggest is you install the same baseband your friend is using. Also do a clean wipe of the ROM and use a ROM that's well updated. One other thing is how old is your SIM card? Is this your first smart phone? Might want to make your your SIM card is compatible. Old SIM cards have issues like you described.

Deviatorz said:
I doubt it's a a baseband issue since there was a time you had good call quality correct? Reinstall your original baseband or at least do a wipe. Are you using custom ROM? I'm not a programmer nor do I have alot of background but I don't think its hardware as well because it should be an all or nothing kind of thing.
The only think I can suggest is you install the same baseband your friend is using. Also do a clean wipe of the ROM and use a ROM that's well updated. One other thing is how old is your SIM card? Is this your first smart phone? Might want to make your your SIM card is compatible. Old SIM cards have issues like you described.
Click to expand...
Click to collapse
Yeah i dont have any ROMS its all stock and you think if i do a factory reset it might work?

UTXPHANT0M said:
Yeah i dont have any ROMS its all stock and you think if i do a factory reset it might work?
Click to expand...
Click to collapse
I may or may not work. You did say the signal was ok at one point correct? Did you check too see if its an old SIM card issue?

yes I just recently switch dim cards and everything seems good so far I'll keep this forum updated
Sent from my Galaxy Nexus using XDA

[Q] Looking for SGH-T989 hardware knowledge

I have a very strange wifi/bluetooth problem that seemed to come out of nowhere and I think it may be hardware but I'm not too sure. When I format the system and install a new ROM everything works as it should for a little while but then within a few hours the software toggle switch grays out and wifi and or bluetooth don't respond. Bluetooth always seems to go out first but wifi follows soon after. I thought originally I had a corrupted driver or something but no matter how many different ROMS I try, going from gingerbread all the way to jelleybean and the phone always acts the same after a seemingly random amount of time. I don't know too much about how bluetooth/wifi drivers work so this may still be the issue.
Sometimes by toggling the various switches off/on a bunch wifi will go back on, and even more rarely bluetooth will work without a system format but it never stays working. If anyone knows what the problem may be I would appreciate some help or if you can point me to a component level diagram that would be helpful too. I have been looking around for a few weeks now with no luck. I never dropped the phone and it looks like I just pulled it out of the box. I did take it apart and look for loose connections and cold solder joints (I have quite a bit of experience at component level repair) but found nothing.
I did try to go back to stock GB with Odin and that was about the same, it worked for about a day and then the problems crept back up.

I thought for sure someone would have an answer.
Sent from my SGH-T989 using Tapatalk 2

I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app

jmpsatx said:
I have a very similar issue but it only affects my Bluetooth. Sometimes it works, sometimes it doesn't. I haven't been able to pin point it. I've done the exact same steps as you. I just chalked it up to it being a hardware issue since I got my S2 from a lady that ran over the phone with her car. I just replaced the glass. She knew it could be fixed but she wanted me to have a better phone. What a sweet old lady. ANYWHO, I would love to see some more input on this.
Sent from my SGH-T989 using XDA Premium HD app
Click to expand...
Click to collapse
I switched to twrp and the problem isn't gone but it is better. I'm not sure if it's a coincidence or not but this seems like a positive step.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Galaxy Nexus death scheduled ?

Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung

But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^

Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.

Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2

Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app

johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.

Try wiping your SD card

S3 SDS?

I've read a lot about SDS and there seems to be no general consensus on the symptoms of it. Some people say they can enter recovery/dl/etc but the phone crashes all the time. Others say that their phone doesn't turn on at all and won't charge.
Here is my issue with my S3.
I just recently installed 4.3 pacman rom. I got everything set up and everything was going great. I tried to flash ACID MOD 7.0/DevilKernel, and they both failed, so I rebooted back into the system and the phone just shut off.
If I take the battery out and hook it up to a charger, the LED will light up. However, if I plug it in with the battery already inside of it, the LED does not turn on. Also, if I hook up the phone to my computer, it'll make a sound like it is trying to mount the device, but it'll make a stutter sound like it failed. It doesn't do this automatically, it only does it if I try to enter recovery/download mode/or turn the phone on.
I'm not sure if the phone is completely dead, or bricked, or what is going on? Or if anyone has any other suggestions - other than changing the battery, which I did do, lol.

Sounds bricked. What model is you s3 btw? And can you post links to everything you've flashed?
SDS doesn't affect our S3's, it was only the international model that had this issue, and I believe it was only on the original firmware.
Sent from my SCH-I535 using Tapatalk 4

http://forum.xda-developers.com/showthread.php?t=2015525
latest nightly
+ 4.3 gapps. it booted fine from gapps.
http://forum.xda-developers.com/showpost.php?p=38599629&postcount=1005
acid mod v7
2802 + 2805 for sammy devices
http://forum.xda-developers.com/showthread.php?t=2240832
devil kernel
prior to flashing pac i installed 2.6.3 twrp because the 2.5.x i was on did not work. i booted in, flashed pac, got everything set up. after restoring the apps and whatnot, i went back to twrp to install acid + devil kernel. they both failed, so i just rebooted from there and it never turned back on. i just assumed the battery was dead, charged my bat in my external charger, and yeah, never turned on since then.
any way to do this without jtag? i'm not at home right now to do something like that and am out of the country, so im a bit unsure how hard it'd be to get those supplies.
i was able to go to a samsung a/s place, but they would only send back to america. i don't think it is worth paying 200+ when this phone is probably only worth 400 or so out of the box, brand new, maybe even less.
i just assumed it was SDS because the symptoms seemed spot on, but it was really weird. i've never had any issues like this flashing roms and it wont' even go to the boot logo. if i plug it in, it makes it seem like it is trying to mount, but there are no vibrations or anything like that on the phone.
thanks for all the help doc, like always.

Thanks for providing the links! Makes it so much easier to help when we don't have to search for everything!
I'm afraid you have bricked your device. I don't know about the Acid mods compatibility with our device, so it may be part of the problem, but that kernel is for the international S3 (I9300/9305). (I'm assuming you have the T999 btw). Never flash anything for the international models, you're nearly guaranteed to brick the phone!
But there's hope! Verify your model number by looking under the battery. Then check out KAsp3rd's unbrick thread in the development section. It should be towards the top.
Give that a shot and say a prayer! It won't fix all bricks, it depends on what was overwritten, but there's a good chance it'll fix yours!
In the future, it's best to stay out of the international models forum altogether! The devices are very different and you take a huge risk when using anything you find there!
Good luck!
Sent from my SCH-I535 using Tapatalk 4

Thanks Doc. I don't think it'll be fixed unless someone in that thread wants to try to flash that devil kernel and see if they can unbrick it w/o jtag. I followed those instructions to a T, and no dice. Although, I can't really tell if my battery is charged right now. I don't have my external charger on me. I will try again tomorrow, but I really doubt it at this point.

Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4

DocHoliday77 said:
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, it is really weird.
After some toying with it I figured out that it only tries to mount the device when connected to the computer IF and only IF my phone is connected to the computer with no battery. It didn't do this before, which is odd. Even if I take out the SD card it still does this now. Before it would fail to make any sound, and now it tries to install the driver. But then it says it fails to install the driver for it, which is the bricked one, the SUBS DWLND or whatever.
I tried following Kasp3rd's advice to hold the button down longer, and I held it down for a whole five minutes with no luck.
I will try another SD when I get the chance, right now I only have a 64gb with no avail to back it up. The SD card is super old though, you are right Doc. It is from my OG droid, but really I haven't had a need for SD cards since I was on an iPhone after my droid and since the S3 is mine, but i'm not using it, I never really bought a nice SD card for it.
I'm going to run to the store in a bit to get one though and hopefully that will make a difference?

May have missed the part about it being 64GB before. Could be the age, but also those 64's have given lots of folks some problems in the past. Seems the S3 can be a bit finicky with those.
Sent from my SCH-I535 using Tapatalk 4

[Q] Reset ODIN counter

I have an issue with my T999 and that is, I cannot connect via USB (charging or otherwise). I talked with T-Mobile and they're sending me a replacement phone and I have to send my current phone back to them. This is great, but what my concern is, the ODIN counter is at 8, but it is currently not rooted and no custom ROM. I read that if there is any number on the counter, it will void warranty, in which case, I will have to pay for the replacement. I read that I can reset the counter while rooted, but I cannot even connect my device to the computer to do so. I am only asking, because I have searched and could find no information to help me out. I feel that I am just screwed unless someone knows how I can root, reset and flash without USB connectivity.
Thank you.

Do you have CWM or TWRP recovery? If so, it's quite easy. If not, then I'm not sure of any way to do so.
Have you tried other cables or on a different computer?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Do you have CWM or TWRP recovery? If so, it's quite easy. If not, then I'm not sure of any way to do so.
Have you tried other cables or on a different computer?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, I do not have any recoveries that I know of. I have tried other cables and computers, but the connection on the phone itself is screwed. It's so bad in fact, that it shuts the computer down for safety reasons. :crying:

Cannibalshymn said:
Unfortunately, I do not have any recoveries that I know of. I have tried other cables and computers, but the connection on the phone itself is screwed. It's so bad in fact, that it shuts the computer down for safety reasons. :crying:
Click to expand...
Click to collapse
Unfortunately, I don't thing there is anything you will be able to do then. You have to be able to connect to the computer to root the phone. Theres just no other way that has been discovered that I am aware of.
I have heard a lot of people claim that they don't bother checking the counter, so there is hope. Sorry I dont have any better ideas for you man. Good Luck though!

DocHoliday77 said:
Unfortunately, I don't thing there is anything you will be able to do then. You have to be able to connect to the computer to root the phone. Theres just no other way that has been discovered that I am aware of.
I have heard a lot of people claim that they don't bother checking the counter, so there is hope. Sorry I dont have any better ideas for you man. Good Luck though!
Click to expand...
Click to collapse
I was afraid that I would not have any other options. Thanks anyway. I will continue my online research and try things on my own (avoiding complete BRICK).

Cannibalshymn said:
I was afraid that I would not have any other options. Thanks anyway. I will continue my online research and try things on my own (avoiding complete BRICK).
Click to expand...
Click to collapse
You never know! Maybe someone else here will have something you can try.

DocHoliday77 said:
You never know! Maybe someone else here will have something you can try.
Click to expand...
Click to collapse
This is true. If I find something, will surely post in here. Also, would like an opinion. My phone is going back due to a hardware malfunction, not software. Is it a possibility that the counter won't even be an issue?

Cannibalshymn said:
This is true. If I find something, will surely post in here. Also, would like an opinion. My phone is going back due to a hardware malfunction, not software. Is it a possibility that the counter won't even be an issue?
Click to expand...
Click to collapse
If they check it, it will be an issue. This is why so many have major problems with this practice. Rooting the phone, or flashing a rom has nothing to do with a faulty usb port, speaker wiring, loose button, etc. But they can and have refused warranty claims for this before.
Like I said though, I have seen plenty of people claim they got theirs replaced and the counter was tripped. So apparently they never checked it. But on the other side, there have also been people who verified that their claim was denied due to the counter.
If you have insurance though, such as Asurion through Tmobile, this doesnt matter at all. You can flash it, drop it, kick it, drown it. light it, and then throw it across the room, and they will still replace it, minus deductible of course.
I have seen where a few people have replaced the usb port on their phone though. The part is probably pretty cheap, and if its an easy replacement, you may want to consider it.

DocHoliday77 said:
If they check it, it will be an issue. This is why so many have major problems with this practice. Rooting the phone, or flashing a rom has nothing to do with a faulty usb port, speaker wiring, loose button, etc. But they can and have refused warranty claims for this before.
Like I said though, I have seen plenty of people claim they got theirs replaced and the counter was tripped. So apparently they never checked it. But on the other side, there have also been people who verified that their claim was denied due to the counter.
If you have insurance though, such as Asurion through Tmobile, this doesnt matter at all. You can flash it, drop it, kick it, drown it. light it, and then throw it across the room, and they will still replace it, minus deductible of course.
I have seen where a few people have replaced the usb port on their phone though. The part is probably pretty cheap, and if its an easy replacement, you may want to consider it.
Click to expand...
Click to collapse
OK. I get that. I went to a T-Mobile store yesterday with my issue and was told that, if there was an issue with the warranty, I would have to pay $110 (I currently do pay for insurance/protection plan through T-Mobile). The man who looked at the phone said that it looked as though it was just damaged by a faulty Micro-USB plugin, and said that in his opinion, there should not be any issues as far as the warranty goes. That is why I was wondering about the counter and if that would impact it. But the insurance I have is through T-Mobile, and on that note, I should not stress too much about it? I receive the replacement phone as early as tomorrow, in which time, I will send the old one back, where they will inspect the damages and come to their conclusion on whether or not I will have to pay, or if everything is covered. I have found a couple of wireless ADB connections for the phone, but it has been so long since I have rooted the phone that way, that I am just going to take my chances and hope all goes well with the exchange process. Thanks for everything!

Please let us know the final outcome.

If you filed through T-Mobile it's going to be warranty. If you went through Asurion it's insurance. Insurance has a $150 deductible, so either way it sounds like you're better off using warranty.
Sent from my SGH-T999 using Tapatalk

Update: The phone that they sent me is a T999L. Now have 4G LTE. I am returning the old T999 tomorrow afternoon through UPS. As soon as I know something from T-Mobile, I will share the results here.

Cannibalshymn said:
Update: The phone that they sent me is a T999L. Now have 4G LTE. I am returning the old T999 tomorrow afternoon through UPS. As soon as I know something from T-Mobile, I will share the results here.
Click to expand...
Click to collapse
Nice! Congrats on the free upgrade!
Sent from my SGH-T999 using Tapatalk
---------- Post added at 01:36 AM ---------- Previous post was at 01:34 AM ----------
Cannibalshymn said:
Update: The phone that they sent me is a T999L. Now have 4G LTE. I am returning the old T999 tomorrow afternoon through UPS. As soon as I know something from T-Mobile, I will share the results here.
Click to expand...
Click to collapse
Please make sure you read my T999L thread before flashing anything! Some important stuff you should know first is in there.
Sent from my SGH-T999 using Tapatalk