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.
Related
I know there are several posting about Vibrants shutting down on its own even when it is fully charged, but, most of the posting are about rooted phones. I am experiencing the same problem but with a stock Vibrant upgraded to 2.2 Froyo. Is there a fix for this problem? I just experienced this problem twice today already and I'm hoping stock Vibrant owners might have a solution.
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
cashmundy said:
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
Click to expand...
Click to collapse
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
dustinkh said:
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
I have put my phone back to JFD via Odin quite a few times, let alone resets, so I wouldn't expect much from that. There will apparently never be a stock ICS for the Vibrant. If the underlying problem is indeed fixed in ICS, the OP may want to make the leap to a good rom at some point.
My GF's phone was on stock 2.2 Froyo and shutdown incidentally, it actually just cut power, black screen suddently. Tried two battery and did the same, reflash to VJI6 and JFD and didn't help at all, but after flashing to Bionix 1.3.1 somehow the problem is gone, weird though
Spontaneous halts and reboots indicate a bug in the kernel or drivers. I don't know what bionic uses. ICS kernels are from the 3.x series of Linux, and are incompatible with older roms. Changing ketnel amd/or radio driver might be a way of attacking the problem short of changing roms. I've changed radios with CM7 but still get the halt/reboots.
A spontaneous shutdowm could also be cause by the battery making bad contact.. try smacking or dropping the phone and see if it happens
sent from the xda app on my android smartphone.
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.
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.
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
FistFull95 said:
Hi everybody,
I'd like to hear your thoughts on my problem.
I have been flashing my i9300 since the day I have it. I wasn't impressed with stock TouchWiz (4.1 I believe?) I have been switching between TW based and AOSP roms alot. I just never found the rom I liked. All of them began to run slow, if they were not already slow. (I do not blame any of the roms I have used, I want to point that out)
Recently I sent the phone back for repair, because it had a burnt in screen. So I went ahead and flashed full stock and reset the counter and all the fun stuff. When I rebooted the phone (100% clean wipe, flashed a Netherlands rom) I noticed that the phone was slow as living h*ll. I had flashed it to a "out off the box" experience but the phone was just about useless. I went ahead and flashed a different Netherlands rom, which was a tad bit faster. I went with it and sent it back.
When I received the phone back in my mailbox, they had flashed stock again (why would one flash stock if just the screen had to be replaced?). I noticed that the phone was extremely slow again!
I decided to believe that it was TW to blame, and flashed Omni KitKat. This was fine for about a week, after which the phone would randomly lock up and system.apk began to crash every 30 minutes or so.
I then decided to start with a clean plate and flashed CM11 (full wipe, including media and all). I have been using that for a little over 2 months now, but the same issues are starting to occur. I have tried it without any 3rd party apps installed, without success. The phone locks up about every 5 minutes with the screen on, I can't listen to music (Google Music or PowerAMP) and then switch to another app, because the music will then stop. If I press the home button, there is an 3-10 second delay, after which system.apk decides to reload along with the launcher (Google Now Launcher), things like that. Sounds like a memory problem to me.
I think it might have something to do with a baseband issue, because of the fact that I have had problems similar before, which were (sort of) solved by flashing a different baseband. But I don't think that Sammy's basebands are compatible with CM11, and I have yet to come across a problem with a CM11 baseband on the internet.
Do any of you experts know an explanation to my problem? Would you suggest sending the phone back for repair?
Thanks in advance
Click to expand...
Click to collapse
The problem might occur because of memory which one of my friend had earlier. Can you tell me how long copying files into phone storage takes?? Do you feel like ROMs are geting installed slowly than previous, slow copying of files?
ASOP Roms like CM never come with baseband. they use the same baseband that you already have in your phone. Only Stock based comes with baseband in their firmware. Sometimes(not most of the time) it can be if you are using different baseband than the one of the firmware, like if you have 4.1.2 and installed baseband of older version like of 4.1.1 but this is exceptional..
Thanks for your reply!
I don't think the internal sd has gotten slower tbh. I tried to copy an 2gb dummy bin from the extsd to my infernal sd, which copied with an average speed of 9mb/s.
I have tried experimenting with different TW based roms in the past, so I might still have a wrong baseband / ril. Is there a way of checking this?
Sent from my GT-I9300 using XDA Free mobile app
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