I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
Related
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
Hi guys. I'm having a real hard time with my phone right now and I hope someone can help me.
First of all, my Note is still on ICS running the last stable build of CM9 (CM 9.1.0 to be exact) without any other kernel or radio modifications. I just performed a clean install of this the other day also. The problem I'm having is that the phone will literally be sitting next to me connected to my home wi-fi and it will fail to receive texts and phone calls. What I mean by that is, my girlfriend will be trying to text me but nothing will come through on my phone for up to an hour. Then at some random time, all the so-called pending SMS will finally display on my phone all with the same time-stamp. Similarly, if someone tries to call me, I will have no notification of this until way after the fact when the voicemail symbol appears (that's IF a message was left).
Now, to me, this seams to be happening at completely random times and I have not been able to pinpoint what's causing it. Before, I used to think it happened after a prolonged time of having the phone on silent and non-use. But just last night the problem happened again when this was not a factor.
A few other notes:
Only seems to happen at home where I am connected to wi-fi. And frankly, I don't travel enough to test my phone anywhere else. While at home my signal strength on AT&T fluctuated between 0-1 bar up to 3 bars. Kinda strange, I know.
Before switching to the CM 9.1.0 rom, I was using CM9-Kang h0tsauce "9" 20120817 *reborn* for quite some time. I experienced the problem with that rom as well but it didn't seem to happen as much.
Rebooting the phone seems to help. When I do this, it seems to push everything through and allows me to be able to receive new messages instantly. Obviously, though, this is not a good work-around since I have no idea when the problem will show up.
So.... anyone know what's going on here? Hardware/software/network problem? I've done some searching but couldn't really find this issue discussed anywhere else. Any help is greatly appreciated.
kevindena said:
Hi guys. I'm having a real hard time with my phone right now and I hope someone can help me.
First of all, my Note is still on ICS running the last stable build of CM9 (CM 9.1.0 to be exact) without any other kernel or radio modifications. I just performed a clean install of this the other day also. The problem I'm having is that the phone will literally be sitting next to me connected to my home wi-fi and it will fail to receive texts and phone calls. What I mean by that is, my girlfriend will be trying to text me but nothing will come through on my phone for up to an hour. Then at some random time, all the so-called pending SMS will finally display on my phone all with the same time-stamp. Similarly, if someone tries to call me, I will have no notification of this until way after the fact when the voicemail symbol appears (that's IF a message was left).
Now, to me, this seams to be happening at completely random times and I have not been able to pinpoint what's causing it. Before, I used to think it happened after a prolonged time of having the phone on silent and non-use. But just last night the problem happened again when this was not a factor.
A few other notes:
Only seems to happen at home where I am connected to wi-fi. And frankly, I don't travel enough to test my phone anywhere else. While at home my signal strength on AT&T fluctuated between 0-1 bar up to 3 bars. Kinda strange, I know.
Before switching to the CM 9.1.0 rom, I was using CM9-Kang h0tsauce "9" 20120817 *reborn* for quite some time. I experienced the problem with that rom as well but it didn't seem to happen as much.
Rebooting the phone seems to help. When I do this, it seems to push everything through and allows me to be able to receive new messages instantly. Obviously, though, this is not a good work-around since I have no idea when the problem will show up.
So.... anyone know what's going on here? Hardware/software/network problem? I've done some searching but couldn't really find this issue discussed anywhere else. Any help is greatly appreciated.
Click to expand...
Click to collapse
I have been having the same problems as you on a Blackstar X and Flapjaxxx's ICS build 12. I talked to AT&T a couple of times and they reconnected me to the network which has helped a little, but I still get missed texts and calls, but not as often. I have no idea how to fix the issue. Hopefully, somebody out there does.
Sounds like to me that you have a very bad signal. In case you didn't know, texts go through the phone signal and not wifi. The wifi connection is just a coincidence since you never leave home and are always connected to wifi. Going somewhere with a better signal would help clarify this.
There are apps on Google Play that restore your network when it goes down. Possibly they may help you.
Agoattamer said:
Sounds like to me that you have a very bad signal. In case you didn't know, texts go through the phone signal and not wifi. The wifi connection is just a coincidence since you never leave home and are always connected to wifi. Going somewhere with a better signal would help clarify this.
There are apps on Google Play that restore your network when it goes down. Possibly they may help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will try one of these apps that restores the network. Fingers crossed!
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
gregsarg said:
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
Click to expand...
Click to collapse
Thank you, thank you, thank you!! I will test this as well.
gregsarg said:
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
Click to expand...
Click to collapse
I started having this issue with my One X. Git a replacement and had the same issue. Now on my note I have the same issue. It's only at home though and I'm on wifi. Started on BlackStar X now I'm on FJ AOSPxxx JB. Seems to happen more. Think I might go back to BlackStar. Didn't happen as much
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Also ..if going back to blackstar ...
The older version is UCLF6 ...And the newer version comes from the N7005 device base .....
Not that it makes much difference, but the older version will likely give you the same results as FJ's UCLF6 builds.....
You may want to try the newer version first ...g
Edit: the older builds allow the use of FJ's 3.0.2 kernels....the newer base will not.
I just installed the May 2 build of CM10.1 on my Razr Maxx (XT912). My bluetoothe headset and obd2 dongle pair without problems.
My Polar H7 heart rate sensor, however, refuses to pair. (My Razr doesn't even see it.)
When running stock, I can pair it without problems. It also pairs easily with my laptop. So I'm pretty sure the device is okay.
According to Polar, this is a Bluetooth 4.0 device. They also mention it supports 'Bluetooth Smart', whatever that is.
I tried posting this in the CM10.1 development thread, but apparently I'm not allowed to post there. I also tried going to the CM10.1 bug tracker, but the page didn't load.
Is this a known issue with CM10.1? Or, does anyone know of a way to get the pairing to work? Thanks!!!
It could be a bad install try installing all over again fresh. Also you need 10 posts to post there so just hang around make some posts if you can and see if you can post again. I you can also read through the threads of cm 10 to see for a fix
Sent from my XT910 using Tapatalk 2
I believe cm10 still having some bugs including Bluetooth so try to flash different rom (full working ) that will resolve ya problem
Edit : i had the same problem with cm10 while it was ok with stock jellybean .
Read the cm10 op i think they have mentioned some issues around cm10.
So onwards try to flash full working custom ROM if ya don't wanna face this trouble in future
Thx
Hit the thx button if i helped ya in anyways
Thanks guys. I had already tried the suggestions from the CM10.1 thread, including clearing data for 'Bluetooth Share'. I agree that any of the ROMs based on the stock kernel probably have a better chance of success. Since the device does appear when I search for it when running the stock ROM.
I was just hoping maybe someone else ran into this and had a workaround. Or, at the very least, to let the developers know about the bug.
Thanks for taking the time to reply...
marksibert said:
Thanks guys. I had already tried the suggestions from the CM10.1 thread, including clearing data for 'Bluetooth Share'. I agree that any of the ROMs based on the stock kernel probably have a better chance of success. Since the device does appear when I search for it when running the stock ROM.
I was just hoping maybe someone else ran into this and had a workaround. Or, at the very least, to let the developers know about the bug.
Thanks for taking the time to reply...
Click to expand...
Click to collapse
Clearing data worked for me
BOSS__DAWG said:
Clearing data worked for me
Click to expand...
Click to collapse
Did you clear data for 'Bluetooth Share', or something else?
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband
I have been exploring new roms for my Verizon G3 recently (Have been on CM12.1 for months, and was curious about others roms). When I tried to flash, everything went fine. I ended up really enjoying the rom. Howvwer, after a while, con.android.process has stopped working shows up, and keeps popping up, rendering my phone useless. I tried reflashing it multiple times, with no luck. Same issue. I looked on Cloudy G3's forums and have not found anything (I am also not fond of looking through 101 pages). Has anyone fixed this? I am going to post this on the rom's thread too, but I at least wanted to start here.
8pscott said:
I have been exploring new roms for my Verizon G3 recently (Have been on CM12.1 for months, and was curious about others roms). When I tried to flash, everything went fine. I ended up really enjoying the rom. Howvwer, after a while, con.android.process has stopped working shows up, and keeps popping up, rendering my phone useless. I tried reflashing it multiple times, with no luck. Same issue. I looked on Cloudy G3's forums and have not found anything (I am also not fond of looking through 101 pages). Has anyone fixed this? I am going to post this on the rom's thread too, but I at least wanted to start here.
Click to expand...
Click to collapse
The whole rom is built on an international base - stay away from it as you'll constantly have those kinds of oddities and even rom breaking issues. It's a well known issue and there is no fix - it's not designed to run on a US CDMA phone.
ohlin5 said:
The whole rom is built on an international base - stay away from it as you'll constantly have those kinds of oddities and even rom breaking issues. It's a well known issue and there is no fix - it's not designed to run on a US CDMA phone.
Click to expand...
Click to collapse
Thanks you so much. I knew he made it more for CDMA, but he has a vs985 option. Wierd why he would do that if it does not work. Thanks though. Maybe he'll fix it.
8pscott said:
Thanks you so much. I knew he made it more for CDMA, but he has a vs985 option. Wierd why he would do that if it does not work. Thanks though. Maybe he'll fix it.
Click to expand...
Click to collapse
the reply you got above is wrong. if you'd searched, you'd have found this:
http://forum.xda-developers.com/verizon-lg-g3/general/cloudy-g3-rom-t2920418/page4
dontevenwanttobehere said:
the reply you got above is wrong. if you'd searched, you'd have found this:
http://forum.xda-developers.com/verizon-lg-g3/general/cloudy-g3-rom-t2920418/page4
Click to expand...
Click to collapse
My response was not wrong - it is a known issue. If you would have actually read the full OP and read between the lines, you'd know that the OP asked about a fix for the issue he's currently seeing on CloudyROM for the VS985, which there is not a fix for - believe me I've spent hours researching it.
@8pscott - Yes, there is a VS985 version - Cloudy made it because of "popular request". However, he doesn't live in the US nor own a VS985 device and therefore can't test it and fix any potential bugs. Bottom line is you can definitely use it, but any bugs are fully to be expected and unfortunately they won't be fixed by the dev. The biggest problem is that you're trying to take a GSM base of a rom, and port it over to work on a CDMA device such as our VS985. Sorry, wish there was better news here!
it runs spectacularly on my vs985 after applying the build.prop changes in that thread that i did indeed read. unfortunately the link was just to the page, and not the post.
http://tapatalk.imageshack.com/v2/14/10/29/a74f2b3d244180a2383a22c45ea29439.jpg
dontevenwanttobehere said:
it runs spectacularly on my vs985 after applying the build.prop changes in that thread that i did indeed read. unfortunately the link was just to the page, and not the post.
http://tapatalk.imageshack.com/v2/14/10/29/a74f2b3d244180a2383a22c45ea29439.jpg
Click to expand...
Click to collapse
Out of curiosity, how long have you been running it? I know it runs well while it does....but I know I personally got the same com.android unfixable crashing error that the OP got, too after aa couple weeks of running the thing.
That cleared up after a reflash. I flashed within a few days of the 2.5 release.
hola
I also run cloudy g3 on my vs985 runs great. Best Bluetooth reception on any rom I have ran. I can walk a good 30 ft form my phone and music never breaks up.