Develop Bugs

[Q] Glide freezing up

Hello,
I've been experiencing annoying freezing up issues with my second-hand Glide. In all cases, the freeze happens with the screen off and a race condition ensues discharging the battery (even when plugged into power). Searching around, I've seen a good number of references to this problem:
androidforums.com/samsung-captivate-glide/462710-freeze-ups-anyone.html
gsmarena.com/samsung_i927_captivate_glide-reviews-4071.php
comparecellular.com/cell-phones/galaxy-s-glide
but I have not been able to find any resolution. Sometimes I feel like this: xkcd.com/979 . In essence I'm trying to determine if this is a hardware fault or something which can be fixed by software. Seeing minimal Glide development does not help since there are very limited options for ROMs. Since this device did get a nod for ICS, there's still hope in that, but until then have to suffer.
Anyone seen a resolution other than exchange? Warranty?

Unfortunately, this is quite common but there are few users that did not had any freezes since day one of their Glides.
One issue is, you have your Google calendar sync and you have "Auto Sync" active. This leads for the Calendar to Sync improperly during sleep mode resulting in a sync loop, which makes the device unresponsive thus, wont wake up upon pressing power/lock key. Solution, uncheck the "Auto Sync" function in Settings, Manually sync everything, or uncheck the "Sync Calendar on your Google account.
The other thing which is very common, is leaving wifi on while charging. This results on the same issue above but the reason is not clear. I experience this one in 1 out of 5 chances, so I turn wifi off or set the wifi sleep policy to "when screen turns off" in Settings. Happens on stock and custom ROM(s), except when Cranium Kernel is flashed.
In conclusion, I never thought that these are hardware issues ATM, for my previous Samsung devices also have these, but is eliminated by updating firmware, or flashing a custom ROM.

Thank you for the suggestions. I will verify wifi sleep policy as well as disable calendar sync to see if it helps. And now that there is some activity regarding ICS for this unit, maybe I'll get to test a new ROM to see if it helps.
thanks again

Neither unsynching google+calendars, or the WiFi+charging solutions worked for me.
Is there any hope for those of us with no immediate remedy?
Has Samsung even acknowledged that this is an issue?
When do you predict us getting an ICS update that will solve the issue?
Its a damn shame since I'm ****in loving this phone so far, yet i can't even use it when I want to sometimes.

Well yeah....I can confirm. I reflashed my device and restore my apps...did not do any mods and whatnot. Used it for a day and charged it overnight, no internet. And bam! Sleep Death. Like i said, this is common, and does not think that this is a hardware issue for a lot is experiencing it. So for now, dont left your glide charging overnight, or if you will, download a night clock, or use the stock desk clock. You will have a clock beside you and will keep your device awake all night.

Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?

wLnston said:
Interesting, I don't have that "sleep death" issue.
Do you have any idea when we'll receive the ICS update?
Click to expand...
Click to collapse
The issue you addressed is so called "sleep death." A few weeks past, ATT announced that 10 of their devices will get ICS in less than a month (including the Glide). No word from Rogers when will they update their version of the device.

Unfortunately AT&T did not state when they would push the update as well they only named the devices that will get it.

Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?

wLnston said:
Has Samsung acknowledged the Sleep Death issue, and whether they will resolve it in the next OTA update?
Click to expand...
Click to collapse
I believe Samsung is already knowledgeable about the issue....unfortunately, it is not that easy to make a software update just to solve 1 problem (on the contrary to the Captivate SGH-I897 with GPS issues on Eclair, ATT immediately released a FW update within less than 2 weeks to fix it). And, even though I said the Sleep Death is quite common, not all of the users have this, so again, maybe unless a considerable large number of users (or all users) experience this, they might look into it. So I also believe that Samsung (along with ATT/Rogers) will correct the issue on the next update. When? Heaven knows.
If you are experiencing the sleep death more than twice a day, without doing anything, or if you believe non of your installed programs is at fault, and you are still in your return period, I suggest you exchange your device. You might get a unit that is unaffected. My Sleep Death only occurs when I left the phone charging for extended periods of time, like charging overnight which I always do. As I've mentioned, I keep the device awake like installing a night clock application or activating the stock desk clock app.

Well I'm going to try turning on the night clock app this night and see if that stops the sleep death.
And I bought the phone second hand off craigslist. Even if its within the 90-day period, I doubt I'll get any warranty/return ability as I am not the original customer.

interesting problem, will this should hold me back from buying it when my friends will be in the states?

taiber2000 said:
interesting problem, will this should hold me back from buying it when my friends will be in the states?
Click to expand...
Click to collapse
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day (on the contrary of the OP's post). In fact, my last sleep death was 10 days previous....it's been reliable and does the job.

gabby131 said:
I can't say.....but in my case, the issue is not really that serious in my part. As I said, when I left my device plugged in extended periods of time, then the Sleep Death might trigger....but I never experience any Sleep Deaths while the phone is unplugged and using it throughout the day. In fact, my last sleep death was 10 days previous....it's been reliable and does the job.
Click to expand...
Click to collapse
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.

dudejb said:
I got the sleep death once. It just happened but I have not had it again. I must admit it is scary but I heard you can flash another rom as that is supposed to fix it. I do have the stock rom from Rogers and have not rooted yet.
Click to expand...
Click to collapse
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).

i have a therory about that, as some other user mentaioned when they useed adracat kernel (that is OC) the problem is gone. maybe samsung uses a underclocked tegra2 prossesor and that tha problem.

gabby131 said:
Well that is a good sign....when did you experience? how? please keep your observations. for me, I can replicate the issue by plugging/charging it....I do also have the stock Rogers ROM and I am rooted......my only tip is, don't leave your Glide charging in extended periods (more than 3-4 hours or so).
Click to expand...
Click to collapse
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.

dudejb said:
No the charging for extended periods does not matter. Every night I set my phone to charge at around Midnight and unplug it at around 6:30 AM. I also have Wifi on. I heard it was WIFI and charging that did it. Luckily I am not experiencing it. Gabby did you flash and install the Clock Work Mod? I am thinking about it.
Click to expand...
Click to collapse
this is exactly what I am experiencing....and I can replicate this issue about 8/10 times....well this should hopefully be fixable via FW update (like my SGH-I896 from 2.1 to 2.2).
Yes I have CWMR installed and is very handy....I am now going back to flash OsiMood ROM for I think I already know what triggers the Sleep Death specially in stock ROMs....

Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!

wLnston said:
Will flashing a new ROM be an issue for me when the OTA ICS update drops?
I read that rooting your phone would be problematic when ICS comes.
If its not an issue, which ROM should I use that will get rid of the Sleep Death issue?
And suppose the ICS fixes the sleepdeath. Will I be able to unroot my phone and revert it back to stock so that I can put ICS on it?
Sorry for the long post!
Click to expand...
Click to collapse
Some people have stated that once you install a Rooted Rom you will no longer get pushed the updated from your service provider. They stated this from Gingerbread 2.3.5 to 2.3.6
In order to go back to stock you have to somehow back up what you have before you flash anything or find it on the web. I am not sure about this but have heard of others doing this.
Your other option is use a ROM that someone cooks with ICS when it becomes available. I have heard of many people toying with getting this set up.

[Q] Continous Vibration

Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?

l_daruwala said:
Hello people!
I am a new member with XDA Developers
Anyways, I would like to ask if any of you face this problem where at any random time the phone would start vibrating continously until you shut down the phone and is there a fix for this?
Click to expand...
Click to collapse
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie

jamidodger1 said:
Hello and welcome the the XDA Forum!
I've found at time that the app "Whatsapp" when I get a message, My phone will constantly vibrate until the screen goes off for 5-10 seconds then it's fine until I turn the screen / unlock the phone, I think it's a common problem as I remember someone else had this issue.
Jamie
Click to expand...
Click to collapse
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)

l_daruwala said:
Yes i also found that too, but sometimes I encounter the problem with SMS too. Never encountered this problem with my previous phones, the GALAXY Ace (GT-S5830) and the GALAXY 3 (GT-I5801)
Click to expand...
Click to collapse
It hasn't done it for SMS for me but yeah it never did it on my previous phone either ZTE Blade

When my profile switch app change profile and take phone to silent mode sometimes makes my W too...
The only solution reboot...

Looks like this affects all GALAXY W's

l_daruwala said:
Looks like this affects all GALAXY W's
Click to expand...
Click to collapse
Yes, and it happens always the best time... meetings, driving...etc.

never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem

Happens to mine, seems like it was only when Whatsapp and something else had a notification at the same time.

soulbkd said:
never happen to me
but if it happened, I'll flash a new fresh ROM and see if it solves the problem
Click to expand...
Click to collapse
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.

mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)

soulbkd said:
that's weird, mine never experience it
I have tried stock, Bagux's, Blacknote, Kezra, and deodexed rom.
maybe something to do with HW version?
mine is rev 0.6 (via *#2222#)
Click to expand...
Click to collapse
Unfortunately mine too. No more idea.

Damn, mine is also REV 0.6 as well.

Still same problem
Mine also rev 0.6
Tried Rebel Rom, Bagux, Bionic Cow 2 v 7, stock DXLM3, stock XXLM8 , all still has the same random vibration.
And the vibration won't stop until you reboot.
Probably hardware related?

This happens to me since the first day I got this phone...
Honestly, it's annoying me !
Cause the only way to Stop it, is a reboot..
Sometimes it starts to vibrate in school, and as Im using a TPU SoftCase it's even more uncomfortable...
I thaught I was the only one, but seems like it affects all Wonders..
No matter which Rom I use, everytime the same Problem
A random time.

mayerkemp said:
I had many ROMs like: Stock, Kezra, F.A.W Special. I get vibration in each case.
Click to expand...
Click to collapse
same problem

Screen flicker issue in all CM10 based roms!

Is anyone else having an issue with their screen flickering randomly (& constantly) when they flash a CM10 based rom? I've never had the issue once in stock ice cream sandwich based roms. As soon as I flash a CM10 rom, the issue starts. Anyone else having this issue & is there a fix for it? I love the speed of Jelly Bean, but the screen problem is so annoying that I keep going back to TW/ICS. It's happened on all 3 CM10 based roms I've flashed.

What kind of flickering? A dark to light repeated flicker when it's dimming as the screen is still on? or a flicker where the screen flashes off and then back on?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

Kinda like flashing off and back on. Almost like a strobe. The screen doesn't actually turn off. It just flickers real quick. I've been playing around with different settings trying to fix it. No luck yet. I noticed that a new kernel was released today. I'm going to install that to see if it fixes the issue. It's worth a shot.

There was no point in making a thread. U obviously use cm10 or aokp and if u read the threads it is a known issue. Its definitely being worked on. Turn off force GPU rendering in developer options for now ....it helps

this happens on stock rom as well. known issue :/

It's a HW overlay issue. Qualcomm is still updating their drivers for vsync (Butter).

mrmako777 said:
this happens on stock rom as well. known issue :/
Click to expand...
Click to collapse
I'm on team sonics freegs3 RC 6 which is based off the stock rom and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

OTAw said:
I'm on team sonics freegs3 rom which is based on stock and have yet to experience this... running the adama v3 kernel as well.
The only thing I notice is when the screen is dimming, sometimes it flickers dark to light a few times before staying dim then turns off.
Are you doing anything specific when this occurs or is it random?
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
typically does it when the keyboard is open. somewhere around here theres a thread about it

I just pinpointed the problem. It's SwiftKey. I just went a half hour with no issues. As soon as I installed SwiftKey, the screen started flickering again. My issue had nothing to do with GPU rendering. I hope this helps anyone else who has been having the same issue.
Sent from my SGH-T999 using xda premium

Ok I think I see something similar to what you guys are talking about. I usually have been seeing it in the Google chrome app when I go to open a new tab.. the tab(s) slots will start flickering and go haywire for a moment.
----
And I'm not using swift key as mentioned above.
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

I used to have the flicker too til I updated to xquizit v16 ...
Sent from my SGH-T999 using xda premium

Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.

Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII

yea its definitely software related. you see it big time in aosp/ jb roms mainly such as cm10 or aokp jb. im running aokp jb build that whitehawkx has out and I do see it. If i keep gpu rendering off it flickers a lot less. basically qualcomm is updating vsync almost everyday and the devs are adding it in as it comes i assume. it will get better over time....anyone running jb aokp go to settings/about phone/android version tap that ten times or so to get the easter egg and u will see a lot of flickering

OTAw said:
Seems to be automatically turned off, at least on mine :/
---> Brought to you in part by my T999 / T-Mobile Galaxy SIII
Click to expand...
Click to collapse
You have to manually check it every time you reboot.

Normally I wouldn't harp on someone for posting a thread that could be answered with a simple search but this is just ridiculous. The flickering issue is probably the largest current bug on all CM10 ROMs and has been discussed countless times in all of the CM10 ROM threads as well as the new kernel threads.
You need to read a little before posting in a panic.

I wasn't in the panic, pal. Thank you for your constructive response!
Sent from my SGH-T999 using xda premium

Fuse8499 said:
Did you try turning off "Force GPU rendering" as sarni suggested? Maybe that's where your particular issue lies. I'm just glad it's software related. Shouldn't be long before we see a fix.
Click to expand...
Click to collapse
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.

Hayhay said:
It's not "Force GPU rendering" that stops the flickering. You have to check "Disable Hardware Overlay" every time you reboot to stop the flickering at the moment.
Also, to the one individual who said Swiftkey is the issue, it's definitely not. The issue occurs some time after you flash the roms - even if you don't install any third party apps. Like someone else already said, it's more likely to be an issue with the constant driver updates Qualcomm is releasing. Eventually, it should go away.
Click to expand...
Click to collapse
You are correct sir, it is the HW Overlay, disable it, flickering goes away...

has anyone experienced a tiny flicker when pressing the power button to turn the screen off? i seem to be having this issue with CM10

[Q[ What causes SSODs in JB ROMS?

Question, does anybody know what exactly causes the SSODs in the JB ROMS? Just curious. I've had them happen in the MOST UNWANTED times. Like, I'll be recording a video. Then suddenly the phone will freeze, then either reboot or shut off. I would then have to take the battery out and put it back in. To turn the phone back on.

pwner5889 said:
Question, does anybody know what exactly causes the SSODs in the JB ROMS? Just curious. I've had them happen in the MOST UNWANTED times. Like, I'll be recording a video. Then suddenly the phone will freeze, then either reboot or shut off. I would then have to take the battery out and put it back in. To turn the phone back on.
Click to expand...
Click to collapse
If the source of the problem was known I'm sure it would already been fixed
Sent from my SGH-T989 using Tapatalk 2

meh, alright.

VoiD_Dweller said:
If the source of the problem was known I'm sure it would already been fixed
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Well, not necessarily. First thing is find out what is causing them. Second, will be what can be done with said cause to fix it, without breaking anything. Though, once the cause is revealed, im sure it wont take to long to fix the issue.

note to the op don't remove the battery, you can damage your phone.. just hold the power button, it will restart..

LoopDoGG79 said:
Well, not necessarily. First thing is find out what is causing them. Second, will be what can be done with said cause to fix it, without breaking anything. Though, once the cause is revealed, im sure it wont take to long to fix the issue.
Click to expand...
Click to collapse
Yea I think the two of you are saying the same thing.. Its basically recognize issue and these smart developers for android will squash the bug. The thing that gets me is the question. Like in typing it do you really think that as long as the bug has been out that if someone knew what to do it would not of been done? Also if you check the changelogs you see countless kernel fixes that shows they are trying everything. What needed to be done in this case is trying to understand the changelogs and commits so you better educate yourself on Android

The biggest annoyance for anyone wanting to mess with less-than-stable ROMs is that you really can't tell what's going to cause it. As with any other software/OS/whatever it is completely dependant on what you have done to the phone. The minute you begin adding apps or configuring your phone to anything other than the exact way it comes, you are causing your own unique set of test criteria.
Obviously there are gray areas in all of this, and customizations can often even assist in the understanding of what causes failures, but the bottom line is that it's up to you just as much as it is up to the stability of the ROM.

4.2.2: Bluetooth won't turn on

OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...

wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?

wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.

zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.

Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium

joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth

wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329

joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.

Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium

After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium

djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.

wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium

djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...

wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium

bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.

Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...