Related
i need help, my screen turns of then it never turns back on, only the soft keys turn on, i was thinking it was because i flashed the newest radio, but i dont know, someone please help me
Jelly Nugget said:
i need help, my screen turns of then it never turns back on, only the soft keys turn on, i was thinking it was because i flashed the newest radio, but i dont know, someone please help me
Click to expand...
Click to collapse
radio shouldn't do this, but it could have been an corrupt download or something, you could try going back to the old radio to see if it helps.
I'm assuming you are rooted?
running which ROM?
I'm pretty sure that if you had a bad radio flash your phone will be permanently bricked.
I'm assuming you can boot it right?
shoman24v said:
I'm pretty sure that if you had a bad radio flash your phone will be permanently bricked.
I'm assuming you can boot it right?
Click to expand...
Click to collapse
yes it can boot up, just when i lock the screen it doesnt work,
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
andybones said:
radio shouldn't do this, but it could have been an corrupt download or something, you could try going back to the old radio to see if it helps.
I'm assuming you are rooted?
running which ROM?
Click to expand...
Click to collapse
noo, it wasnt corrupted, i did flash the old radio, and still no dice, i called asurion, and told the guy i was rooted, he didnt mind, because he was too. lol but yeahh, they are sending me a replacement.
EDIT- and yes im running CM7, but i tried miui and it still does it.
Well, if the phone is able to turn on like you state, I'd say maybe there's an issue with your ROM, maybe a kernel or mod you flashed?
If you had an issue with the button, the phone would not power up. Unless you have to press it really hard?
Maybe you want to do a clean install of a Sense ROM or a clean install of CM7
Jelly Nugget said:
yes it can boot up, just when i lock the screen it doesnt work,
---------- Post added at 11:00 AM ---------- Previous post was at 10:57 AM ----------
noo, it wasnt corrupted, i did flash the old radio, and still no dice, i called asurion, and told the guy i was rooted, he didnt mind, because he was too. lol but yeahh, they are sending me a replacement.
EDIT- and yes im running CM7, but i tried miui and it still does it.
Click to expand...
Click to collapse
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
tylerlawhon said:
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
Click to expand...
Click to collapse
+1 too many megahertz
From this, it sounds like it's not able to handle the speeds.
Don't overclock.
tylerlawhon said:
If you're overclocking your phone, try lowering the GHz. I pushed mine up to 1.6 GHz, and when I locked it, it wouldn't come back up except for the softkeys. I put it back to 1.3 GHz, and it was fine.
Click to expand...
Click to collapse
actually, i underclocked to 806mhz on all my roms to save power.
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
shoman24v said:
Well, if the phone is able to turn on like you state, I'd say maybe there's an issue with your ROM, maybe a kernel or mod you flashed?
If you had an issue with the button, the phone would not power up. Unless you have to press it really hard?
Maybe you want to do a clean install of a Sense ROM or a clean install of CM7
Click to expand...
Click to collapse
ive done a clean install of all the ROMs, like Incredible 3D, Incredible HD, CM7, OMGB, OMFGB, Virtuous, and still no dice on anyone of them.
flash an ruu just to make sure its an actual problem with the phones screen and not you screwing something up by flashing something.
Sent from my Incredible 2 using XDA App
Jelly Nugget said:
actually, i underclocked to 806mhz on all my roms to save power.
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
ive done a clean install of all the ROMs, like Incredible 3D, Incredible HD, CM7, OMGB, OMFGB, Virtuous, and still no dice on anyone of them.
Click to expand...
Click to collapse
That could be your problem if you're not undervolted. (Someone correct me if I'm wrong. It just makes sense in my head lol)
Too much undervolting can cause issues too.
shoman24v said:
Too much undervolting can cause issues too.
Click to expand...
Click to collapse
I figured as much, cuz if you UV too much, you wouldn't be sending adequate power to the CPU, causing it to not work.
times_infinity said:
flash an ruu just to make sure its an actual problem with the phones screen and not you screwing something up by flashing something.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
how would i do that? if i can can i get a link please?
Jelly Nugget said:
how would i do that? if i can can i get a link please?
Click to expand...
Click to collapse
The only one I've been able to find for you, is the newest RUU, and it has to potential (or so it sounds) to take your root.
http://forum.xda-developers.com/search.php?searchid=91685359
This is the latest RUU update for the VivoW
I don't know if RUU'ing will fix it.
Were not 100% clear on the issue. My understanding is that the phone only has issues powering up when the screen is asleep. He's undervolted, which can be an issue.
What I'm curious to know... do you have any issues powering up the device when it's completely off? Any issues with the power button when navigating in HBOOT? If there is no problem with those, I'd believe it's maybe the way the phone is set up.
I'd try to flash a 100% stock ROM with no modifications and see if it's still an issue.
tylerlawhon said:
The only one I've been able to find for you
Click to expand...
Click to collapse
Haha I love it..doing his work for him
Sent from my Incredible 2 using xda premium
shoman24v said:
I don't know if RUU'ing will fix it.
Were not 100% clear on the issue. My understanding is that the phone only has issues powering up when the screen is asleep. He's undervolted, which can be an issue.
What I'm curious to know... do you have any issues powering up the device when it's completely off? Any issues with the power button when navigating in HBOOT? If there is no problem with those, I'd believe it's maybe the way the phone is set up.
I'd try to flash a 100% stock ROM with no modifications and see if it's still an issue.
Click to expand...
Click to collapse
yes, i flashed the ruu, and it did take root. it boots, but when i lock the phone, it still doesnt turn on. it does navigate fine in recovery.
Jelly Nugget said:
yes, i flashed the ruu, and it did take root. it boots, but when i lock the phone, it still doesnt turn on. it does navigate fine in recovery.
Click to expand...
Click to collapse
The exact same issue came up for me about a week ago. I could boot an aosp rom, but like you when I lock the screen and go to unlock I get a black screen with only the soft keys. I still have no solution. But if you take out your sd card and boot up it shouldn't do that anymore so i think it has to do with the sd card or something on it.
Sent from my Incredible 2 using XDA App
I'm having the exact same problem. Only happens on aosp roms, sense roms work fine. Boots up fine with cm7 or miui (a little laggy actually) then when screen is turned off, only softkeys light up... can't unlock
edit-----
Tried to remove the sd card upon boot, like previous post suggested. Still wouldn't unlock on cm7..... even with sd card not installed.
This happens the first time i turn the screen on after a power up/reboot (MIUI + JDKernel/tiamat). Screen does its CRT animation and goes black. Easily fixed with a couple presses of the power button, but now you got me worried it won't always be that simple...
Sent from my Incredible 2 using XDA App
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.
Alright, so my girlfriend's Samsung Galaxy S II started to go through these weird partial reboots several weeks ago (maybe even months). The phone would randomly go black, play the stupid shutdown/startup (dont remember which) jingle...then just simply be at the lock screen with a crossed out circle where the signal bars would be (for just a couple of seconds). When this happened, I used to just tell her to shutdown the phone, take out the battery, and let it sit for about 30 seconds, then put everything back together and start it back up. This seemed to work, which made me think it might have just been a software or at worst a memory issue of some kind.
This issue was always intermittent, but now, no matter what I do, it just keeps looping this "restarting" problem. I can't access any internal memory space from my computer because in the time it takes to connect, it just "reboots" again. I made a logcat of the phone up until the "reboot", and in doing so noticed that when I would browse the phone via adb shell, I saw no mount for the sd card...which then lead me to believe maybe it was an issue with that. I checked the sd card for corruption (and prior to even using it, checked that all blocks were read/writable (legit)), but that led nowhere.
Anyways, not having any idea where to go next, nor where to begin or what to look for in the 5000+ lined logcat, I turn to xda with hopes of getting some sort of help. Thanks in advance for any I get!
EDIT: Oops, some other important notes I didn't mention (other than in title); this is running stock firmware, only OTA. I tried once to upgrade her to ICS via Kies, but the upgrade would never complete. She also refused to let me root her phone...so unless there is a stock recovery mode, her phone has none...
bump, as its been a week and no responses. If anyone has any ideas or can figure out whats wrong from the logcat, please help.
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Sent from my SGH-T989 using Tapatalk
EarthBoundX5 said:
Almost 3 weeks...no answer...isn't there at least 1 person who has an idea or can deduce one from the logcat? Pretty soon I'm gonna have to tell her to give up and get it "fixed" (ie, swapped for a refurb with most likely all her data lost)...
Click to expand...
Click to collapse
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
For starters, thanks everyone for the responses! After this long, its really great to see so many in one day!
richardlibeau said:
Looking at the logcat if it is accurate the problem is overheating and it is shutting itself down. That's why it keeps rebooting from I read but I could be wrong. Also looks like it has wakelock issues. Lot of wakelock errors in logcat. Some app or apps are causing the wakelock issue find them and remove them that might solve the problem.
Click to expand...
Click to collapse
Thats what I thought, because it seemed to get exceptionally hot before "rebooting"...at first...then I was noticing it "rebooting" when clearly cold. If it is indeed overheating like I had thought in the very beginning, is there anything I can do about it? What does it use for heat conductivity and displacement? And for that matter, I would think if it was overheating though, it would actually reboot, not the half-ass semi-reboot its been doing...
And what is wakelock exactly that it would cause an issue? Only apps I see using it are WootWatcher, KeyguardViewMediator and PowerManagerService.
krazierokz said:
i say try to odin back her phone to stock on here there a good post for it to get her back and if she had Gmail sync there shouldnt be a problem unless she really dont want to download everything again i say give odin a shot and then from there upgrade through kies its tricky you have to make sure you have 50% battery life or more and kies errrors out sometimes but it does work i update my friends phone as he does not like all the root stuff lol so i always your kies after a couple errors it will work and thats your best option if she doesnt want to loose anything kies will back it all up for her and are you sure that power button aint sticking sounds like you have a looping issue are you able to go into download mode or are you familiar with this ?
Click to expand...
Click to collapse
I would use odin...but the phone doesn't stay on long enough to do much of anything before "rebooting". Also, she is already using stock firmware + OTA updates. And her contacts are not what I am worried about, its her photos and such. This is the very reason why I hate internal memory for phones...
And I'm pretty sure its not a sticky power button, I had seen that being a common issue when researching before posting. And again, if I have not been clear, its not exactly "rebooting", just semi-rebooting; phone starts up, crap starts running, a min or 2 later, phone acts like its restarting (plays sound and all), then just comes back to the lock screen immediately...I can't really describe it much more than that.
And no, I'm not familiar with "download mode"
bzlik88 said:
Idk how to read logcats but another idea could be you have the sticky power button issue. I think if it was overheating u would feel it and mention it in the op.
Click to expand...
Click to collapse
Ya, like I said in the reply above this, I don't think its the sticky power button problem...but I could always be wrong. I only didn't mention over heating because I felt I did a good job of ruling it out.
DeliciousLimeJuice said:
I used to have this problem when my phone was on ICS. I found that putting it back to GB, and using custom JB roms fixed it. I'd try those.
Click to expand...
Click to collapse
Its running GB atm, never updated to ICS via Kies...
I wish I could help you further but i can say one thing, the rebooting that your describing is called a "hot reboot". I know what ur talking about and others will too if u use that term. Good luck.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
screwregi said:
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
Click to expand...
Click to collapse
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
lordcheeto03 said:
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
screwregi said:
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
Click to expand...
Click to collapse
Nah, I'm mostly just giving you a hard time The CM10 nightly thread has gotten to be a beast to look through; seriously though... that problem is pretty old, and like you said; the only way to get around it is to hold power or do a battery pull. Just wait until you have an alarm go off in the morning and you can't turn it off!
Try the 2013 nightly, it does not appear to have this issue
Nz
notzippy said:
Try the 2013 nightly, it does not appear to have this issue
Nz
Click to expand...
Click to collapse
Maybe not, but it probably has other issues instead!
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
screwregi said:
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
Click to expand...
Click to collapse
Just saying; but there's already a thread for discussing CM10...
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...