Develop Bugs

Really frustrated with new Epic

I just replaced my Hero with an Epic a week ago. I hope this was a wise move but I am having second thoughts. The Hero was barely usable until I rooted, then it was actually pretty good - slow but good. Anyway, I was looking forward to having a phone I could just USE without having to root it or really screw around with it. I guess that is not the case with any Android phone...
Biggest issue is bluetooth. It sporadically works. Generally to get it to work I have to delete it from my car radio, then reinstall - same with the phone. This is not acceptable. Again - I had similar issues with Hero until I rooted - then bluetooth was perfect. I also liked to use an app called RadarNow that I cant get to work on the Epic. Last but not least, I cannot 'mount' the Epic to my PC. PC simply doesn't see the device.
I really appreciate your suggestions! SB

Bluetooth issues with the Epic are pretty common, and caused by Samsung's proprietary bluetooth stacks, once CM7 is complete bluetooth should be flawless.
I haven't tried Radar Now so I can't speak on it, maybe another user can.
Install/Reinstall the Samsung USB drivers and use a cable other than the one included in the box.

I installed the USB drivers this morning. I hope they were from the proper place. No change. I haven't tried changing cables yet.

sbbamafan said:
I installed the USB drivers this morning. I hope they were from the proper place. No change. I haven't tried changing cables yet.
Click to expand...
Click to collapse
If you got them from the Samsung website then they were from the right place. Do that then report back, the one included in the box is a piece of junk.

sbbamafan said:
I just replaced my Hero with an Epic a week ago. I hope this was a wise move but I am having second thoughts. The Hero was barely usable until I rooted, then it was actually pretty good - slow but good. Anyway, I was looking forward to having a phone I could just USE without having to root it or really screw around with it. I guess that is not the case with any Android phone...
Biggest issue is bluetooth. It sporadically works. Generally to get it to work I have to delete it from my car radio, then reinstall - same with the phone. This is not acceptable. Again - I had similar issues with Hero until I rooted - then bluetooth was perfect. I also liked to use an app called RadarNow that I cant get to work on the Epic. Last but not least, I cannot 'mount' the Epic to my PC. PC simply doesn't see the device.
I really appreciate your suggestions! SB
Click to expand...
Click to collapse
I never have BT issues and here are the drivers if you're running Windows
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR

I do not have any BT issues and my epic is perfect in every way - although I am on a stock rom and a patched stock kernel.
I am rooted though, but only so I can do a recovery and removed only two pieces of Sprint Bloatware; Nascar and Football

I haven't used radar now since early in my hero days, but rainy days is just like radar now & works perfectly.
Sent from my SPH-D700 using XDA App

OK 0 it is clear now that I am going to have to root this phone. Can someone tell me what ROM is the best for bluetooth as this is very important to me. Also - is there a way to keep the Sprint TV after rooting?

I came from the hero as well and even on stock The Epic was so much faster and snappier than my rooted Hero was. I have also never had any BT issues in fact it is one of the things I really love about it. I can listen to music all day with maybe one or two skips and this is from the music player, slingplayer, xm radio or pandora. I use a Blue Ant T1 and just bought a Pioneer Nav system for my car and they both work great. You may have a bad phone but hope you get it working.

sbbamafan said:
OK 0 it is clear now that I am going to have to root this phone. Can someone tell me what ROM is the best for bluetooth as this is very important to me. Also - is there a way to keep the Sprint TV after rooting?
Click to expand...
Click to collapse
Try EC05 Plus or SFR 1.2 with Genocide or Vision kernel also make sure you enable journaling.

I came from a Hero 8 months ago as well and up until 3 weeks ago was running a completely stock untouched Epic, not rooted or anything and have never had any issues with BT. Might be worth exchanging it if you really want to stay stock. Maybe you just got a bad device.

[Q] Bluetooth disconnects?

I can't seem to find any mention of this anywhere else, and I have looked. My wife and I both have E4GT and are both experiencing this issue everyday and we both have different Bluetooth headsets.
We will walk away from our phones far enough that our headsets disconnect. Once we close enough, sometimes they connect back up, but most of the time, we have to shut off the Bluetooth radio in the phone and turn it back on before it will connect again. Once in a while we are right next to the phone and it will disconnect for no reason at all.
My wife has a cheaper Rocketfish headset and I have a more expensive Jawbone.
Anyone else having this problem?
both our phones are rooted and we're both running Caulkins rom. She is running an older 2.8.0 and I am sporting 2.8.1. I have asked this in his rom thread, but twice have gotten no responses. I can't find anywhere if there is a Bluetooth radio driver update like with modems.

Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App

davidc23 said:
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
HAHA, I knew someone would ask that!
To be honest with you, we got these phones and two hours later, I had them rooted and flashed, so I couldn't say. I've been rooting and flashing roms since we had our first Droid 1 phones and I just can't seem to leave well enough alone.

I have the same issue with a Jawbone Era.
Has happened on stock roms as well as Caulk's and UnNamed.
What happens with my Era is that it will just stop working. Phone will show that it is still paired, but I get no audio to the device. The only way to fix it is to turn off the Era headset, and turn off bluetooth on the phone. Then turn BT back on, followed by the headset.
It's a real PITA. I got this headset after reading several reviews on the webs saying that it was a great unit.
It is, when it works. Unfortunately this happens at least once a day.
I am looking for a solution as well, and I was even thinking of getting a different headset but after reading that it's happening with completely different headsets makes me think that won't solve anything.
I'll try to report back if I find anything.
One other note, the Jawbone Companion app also is very flaky. Most of the time it will not detect the Era headset even when the phone is connected and it's working fine. This too happens on both stock and custom roms.

Bluetooth
Make sure your phone is set to always discoverable and when you get back in range of your phone try hitting the call/end button on your bluetooth, this should help it re-connect without having to restart the program in your phone.

I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!

jb8301 said:
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
Click to expand...
Click to collapse
I'm seeing a pattern here. It appears from what I'm reading, that it does not matter what Bluetooth headset you have or what rom you're running, it's happening to a few people. Makes me think it's the phone or Gingerbread itself that's the issue. Maybe when ICS is ready to be a daily driver, it'll change.
In one respect it makes me feel better as my wife and I don't have to replace our headsets!!
I am not comfortable in leaving our phone "discoverable" as this opens our phones to possible unwanted access from unscrupulous people.

Original Verizon backup

Does anyone know where I can find the original backup for my Verizon Galaxy Nexus? I got a refurbished phone sent to me Monday and I have to send the phone back because the headset cant hear phone calls and I have rooted my phone and upgraded it to Jellybean without backing up the original OS

Use the second link in my signature
Sent from my Galaxy Nexus using Tapatalk 2

If you want an even older build that what Zepius suggested, you can always look at oldblue910's website: http://www.randomphantasmagoria.com

I'm sorry if this is too off topic. But I don't know what thread to place the question on.
I was told by a Verizon rep (taking his words with large grains of salt) that they have had more Nexus's returned than any other recent device. Its plagued with issues. And a few of them are 4G connectivity issues. Where it will be always connecting and disconnecting from 4G many times a day, even in a fully covered area. The GPS does power cycling all the time using much more battery than necessary. And horrible battery, buggy interface are just a few he mentioned to me.
Are these issues just a Verizon rep trying to push me away from a open and rootable device? Or are they real? And if so, are they only with the Stock Nexus ROM, and most if not all are fixed after flashing one of the many Custom ROMs available? What are some of the most common issues with the Verizon LTE version of the Galaxy Nexus? Both before and flashing a Custom ROM.
Thank you guys for any help, and God Bless

clem11388 said:
I'm sorry if this is too off topic. But I don't know what thread to place the question on.
I was told by a Verizon rep (taking his words with large grains of salt) that they have had more Nexus's returned than any other recent device. Its plagued with issues. And a few of them are 4G connectivity issues. Where it will be always connecting and disconnecting from 4G many times a day, even in a fully covered area. The GPS does power cycling all the time using much more battery than necessary. And horrible battery, buggy interface are just a few he mentioned to me.
Are these issues just a Verizon rep trying to push me away from a open and rootable device? Or are they real? And if so, are they only with the Stock Nexus ROM, and most if not all are fixed after flashing one of the many Custom ROMs available? What are some of the most common issues with the Verizon LTE version of the Galaxy Nexus? Both before and flashing a Custom ROM.
Thank you guys for any help, and God Bless
Click to expand...
Click to collapse
This is my 3rd Galaxy Nexus. The first had a software issue. The second one, which was a new device, stopped charging while the phone was on. Replaced the battery and the phone still wouldnt hold a charge. This one is a refurbished replacement phone and since I've rooted it and installed Jelly Bean, I can only use the phone on speaker, wired headset, and bluetooth. I took the second phone to the Verizon dealer and the sales rep said his Nexus was starting to exhibit the same thing my phone started to do.

llenroht said:
This is my 3rd Galaxy Nexus. The first had a software issue. The second one, which was a new device, stopped charging while the phone was on. Replaced the battery and the phone still wouldnt hold a charge. This one is a refurbished replacement phone and since I've rooted it and installed Jelly Bean, I can only use the phone on speaker, wired headset, and bluetooth. I took the second phone to the Verizon dealer and the sales rep said his Nexus was starting to exhibit the same thing my phone started to do.
Click to expand...
Click to collapse
Have you ever tried a ICS ROM? One that has had much work done with it and has been labeled fully stable and released? Jelly Bean ROMs seem to all be in fairly early stages. So its really hard to know if the issues were with the ROM or with the phone.
Can any one confirm @llenroht 's list of issues? And are these fairly common, even when using a ISC Custom ROM?

Why is everyone avoiding LK8?

It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?

Wifi issues, and until recently the inability to go back to older firmware mostly.

Interesting, I haven't seen any WiFi issues. Samsung devices always have crap radios, and LK8 seems on-par with the other releases.

Jellybomb, H20 and MIUI are great Roms and that's why they're on LK8. Hehe
Sent from my SPH-L900 using xda app-developers app

It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.

JellyBomb is great in function, but on every device I've ever used it on, the theming causes problems. Fonts covered, hidden, etc due to the blue. Guess I'll try it again.

Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
This. And also simply because the devs don't want to work with a leak. Who would? Also I prefer few roms with less bugs than a variety with problems.
Sent from my SPH-L900 using xda premium

ScrapMaker said:
It's a bit weird that all the decent ROMs are still on LJC, even after a few weeks with LK8 on the scene... Is there some valid reason for this, or is it simply because the GN2 development section is underwhelming compared to the GS3/etc?
Click to expand...
Click to collapse
LJC works with fewer issues more often for more people than lk8. Many devs stick to it because of all the bugs that stem from lk8.
Sent from my SPH-L900 using Tapatalk HD

I know a lot of devs only upgrade to official releases and newer doesn't always equal better as well
-TeaM VeNuM Like A Boss
-Galaxy Note II Edition

Itchiee said:
It happens in certain scenarios and im speaking from experience. I was unable to connect to a completely open network.
The GS2 had crappy radios, I would not say that about the Note 2.
Deuces.
Click to expand...
Click to collapse
Compared to my HTC Evo series (any of them,) I'd say it's pretty obvious all the radios are quite inferior. That's good information that this firmware might contribute to that though. Thanks!

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol

thunderwagn said:
The Chameleon bug played a big role I think in people avoiding upgrading to LK8. While it didn't seem to cause any real damage, it was annoying as hell not only for the user experiencing it, but also the devs and other members having to see issues and questions related to it constantly. The bug has been squished, but I think the fear still lingers lol
Click to expand...
Click to collapse
I was one of the early catchers of that bug, and was vocal about getting some dev involvement. At the time it was a permanent error, and a pain in the a$$, I had the choice of LJC with HFA/chameleon FC errors (permanent, no matter how it was wiped back to stock), or no wifi.
Thanks to Garwynn, EvilKoncepts, a pal that did testing for them (can't remember his name), there is now a verified fix for it. (Has to do with LK8 changing carrier partition).
So right, most devs don't want to mess with leaks for official releases.
I won't touch it, at least not for now. LK8 has some nice little features, but I'll hold out for a bit, hope a (better? official?) version gets posted by Sammy for SxTp to bring us.

personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.

t3project said:
... the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
normally, I might agree with you, having seen most issues caused by user negligence/ignorance. and fixed by proper procedure being used to reapply a ROM/Odin a stock. but in my (and several others) case, this was on Stock rooted, with the SxTp Stock leak applied. Wifi died for no reason after aprox 24 hrs use. No amount of wiping/resetting to fact-default would fix it.
But going back to LJC did, while bringing other (well documented) problems with it.

t3project said:
personally i havent seen any "bugs" in lk8. i've never had wifi problems and most everyone who has ran ProjectROM hasnt either. if you build off a stable base the only real bugs are usually caused by bad flashes, restoring backups and other misc crap. i'm not saying there arent bugs in roms because someone always forgets something but it's usually user induced not matter how much you dont want to admit it.
Click to expand...
Click to collapse
The only real bug I've found in lk8 is the wifi issue, it seems to not like certain wifi frequencies or channels, as it will connect to some routers but won't connect to others. Could possibly be an issue with the wifi supp or wifi conf files. The other big issue is the carrier partition upgrade in lk8 causing issues when going back to ljc
I like to break stuff!

I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.

ScrapMaker said:
I try any and every new firmware update with the HOPES AND PRAYERS that Samsung will fix their effin' horrible Bluetooth stack... worst of any device I've ever used. CM10 fixes it, but right now that's not a viable option, especially since I like having the SPen...
I hate that when I have my headphones plugged in, sounds still blurt out the speaker... wtf?
When I'm in the car with the headphone jack connected to my aux port, and the BT set to hands-free to my OnStar, I have to yank the audio cable out while driving just to answer. Pretty stupid. HTC, Palm, Motorola, etc all have this figured out, but not Samsung. All their Android smartphones do this.
Click to expand...
Click to collapse
I don't have any issues with BT or audio over the 3.5mm jack. Although I don't have BT in my car I use a headset while I'm working and will have headphones on in the other ear and it switches back and forth just fine
I like to break stuff!

I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.

ScrapMaker said:
I've never once had that work properly with the stock firmware, or even custom ROMs, (aside from AOSP.) If I have BT attached to hands-free only device, and playing music over 3.5mm connection, it will continue to play over the 3.5mm despite having the BT attached. Maybe something changed in LK8 that I didn't pay attention to. This holds true for the S3, S2, and GN2 that I'm aware of.
Click to expand...
Click to collapse
I'm using ljc. Was stock but I've been building my own rom off of the stock OTA and haven't even messed with anything BT or audio out related and have no issues. Maybe it has something to do with your BT device itself, perhaps it and the phone aren't communicating properly after its been idle for a while. I had an old Motorola BT headset that would go idle/sleep and never wake up unless I pressed a button on it so I'd have to answer the call with the phone then press the button on the headset to switch over
I like to break stuff!

weak wifi transmission

I recently reverted to stock on my at&t note 2. I am having wifi issues. The phone gets a strong signal from my router (-50) but I get authentication errors connecting if I am not very close. Standing 5 feet from the router I get terrible throughput. I am running dd-wrt and can see that the router is only getting -90 signal from my phone. Every other device is much stronger.
I have tried disabling wifi power save mode and have tried the OTA update to ucamh3 baseband.
Any suggestions greatly appreciated.

With a weak or malfunctioning wifi setup over multiple roms ....I might suspect a bad antenna ??
Not a for sure thing...but it should be considered...
Several of these devices were returned early on with antenna issues...
With a pure stock UCAMH3 rom running...wifi has been excellent...
I would try a clean slate data reset in recovery...and a router reset as well...
Then set up the wifi again on the device...
It's a long shot...but is certainly a good first step in diagnosing the device and the antenna...
Does the device suffer the same in other wifi areas ??
If not...look back to your home system....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.

kevingt01 said:
Thinking it might be a bad antenna, I ordered a replacement housing which (to my understanding) includes the WiFi antenna on the Note 2. No luck. I'm going to try another ROM to see if I have any better luck. If that doesn't work, might buy a new router. I'll update if I find anything that fixes my issue.
Click to expand...
Click to collapse
I'm on CyanogenMod now with no improvement. Router sees strength of -85 and SNR of 9 when I'm 5 feet away from it.

exact same issues here with i317. wifi worked great for about a year while rooted, and running multiple roms. i loaded SkyNote4.3 and it's been down hill ever since. I'm currently on DN3 4.3 and it works fine if i am close to my router as well. have S4, and Nexus 7 on same router, and they work fine with great signal, so it's not the router. I even removed security from my wifi as a test, and same results.
I have tried reverting to 4.1.2 and still no change. Appears to be SNR related at the moment, as my other wifi devices have 38-50 SNR values on DD-WRT, but my i317 has 10-12. No microwaves or any of that jazz going on, all 3 of these devices sitting next to each other when pulling values.
still investigating, but if anyone has any suggestions i'm open to ideas at this point.
what has been tried: reverting to 4.1.2 stock firmware from sammy, 4.2 bootloaders, 4.3 bootloaders, different modems, different kernels, different roms.

I got a replacement Note 2 from AT&T for this reason. I Googled the problem and found many mentions of it, so I called AT&T and had the CSR Google the problem while I was on the phone..
Of course I hadn't opened it up or anything...

I sent my phone to Samsung twice. The first time they just tried to update the software and claim it was fixed. That obviously did nothing to resolve the problem. I just got it back from a second visit to the service center where they replaced the mainboard. I haven't tried it yet, but expect that solved the problem. I'll confirm later tonight.

yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.

white8785 said:
yeah, i'm to the point where i believe it's antenna related, and I believe it's on the mainboard. unfortunately it's over my 1 year manufacturer warranty and att is telling me they'd charge me the 200 deductible and just replace it. doesn't seem worth it to me at all. it's just odd that it started out of the blue with a 4.3 skynote rom.
Click to expand...
Click to collapse
I thought mine was antenna related so I bought a new housing. That didn't fix it. I read where one person bent up the contacts a little so I tried that and it didn't fix it. I never used to believe software would screw up the hardware, but I really believe some firmware has a bug that's pushes too much power to the wifi transmitter and damages it. That's just a hunch from a few posts I've read. It sounds like this may have happened to people with a Samsung OTA update.
If I were you, I'd log onto Samsung's site and just double check that you don't have any warranty left with them. If not, I'd even try chatting with them expressing disappointment in the device. let them know that apple geniuses would take care of you anyways. Maybe they'll be generous.. worth a shot.

So good and bad news. After getting my phone back from Samsung the second time, wifi authentication issues and drops are gone. The strength is good enough to keep me connected around the house, and speed is fairly consistent throughout the house, and is good enough for browser, etc. However, the speed still isn't up to par with other devices. I'm now experiencing 4-5mbps on speedtest.net (vs. ~20mbps on my other wireless devices). :/