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.
Related
.... will not be anything that is resolved here. It is a problem with the firmware for ICS.
I was talking to somebody at sprint today while I was there and showing them my device and asking if there will be any issues caused by having a virgin mobile ROM on the device. The lady explained to me that they are exactly the same, get the same reception, same update packages, and work on the same network, etc., etc.... All of this was known to me to some extent, but wanted to hear it from somebody at the company... and told me that the only problem they are having is with ICS in general is that there have been data/radio issues with the Galaxy Nexus line as well ever since it released on their network a few weeks ago.
Furthermore, she explained that this was a known bug/issue and that she knew for a fact that an update would be coming with a fix and that it was being worked on right now.
The reason I wanted to share this was because I have seen a lot of misinformation floating around about 1.) having a virgin mobile ROM on your device and 2.) virgin mobile ROM causing data issues - which is not the cause of the issue as I mentioned just now.
Just want you all to be aware of this in case you were thinking having this software and firmware on your device would cause any issues with your billing, your contract, etc. Simply put - it will not. Virgin mobile is owned by sprint, they run on the same towers, same network, and info of accounts is stored in the same place. You could literally walk into a sprint store to pay your bill for your virgin mobile account.
All is well. All is safe. An update will come to fix the data issues, keep your eyes peeled for it folks. We are not given source code for radios, etc., so unfortunately that needs to be fixed on the carrier/manufacturer end - and as I said, it will be fixed and they are working on it. Sit tight.
Hope this cleared up any misconception floating around.
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Oh man, you have no idea how much I was freaking out about the billing. Thanks man. (Y)
xHausx said:
So, you're don't really know how to fix it then? Forgive me for being a little confused, but you say there is a problem with the firmware and then say that there is nothing wrong with it?
Click to expand...
Click to collapse
yeah, i can see the confusion there....
re-worded, i would say it appeared to me that people thought there were data issues because of being on a virgin mobile ROM. The point I am trying to express is that the problem is the firmware, not because the ROM is for the virgin mobile 3D - if this same firmware was released for "official sprint RUU" where your banner said "sprint" they would still be having the same issues. Ex.: the lady at sprint said the galaxy nexus was having the same issue.
If that makes sense.
If not, not sure how else I can explain it.
It seemed people were crediting the problem to the fact that there device is attached to virgin mobile - this is not the case.
EDIT*** lol, nice ninja edit haus - you gotta be quicker than that roffle
xHausx said:
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Click to expand...
Click to collapse
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Punk9 said:
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Click to expand...
Click to collapse
after half a day of having flashing back they determined the problem to be gone??
......
the issues being caused by the firmware are not constant, and apparently are rather random from what I have read. a perfect example is my own device... no issues with new firmware until today (day 3) of having it, even tho many people reported issues after just a couple of hours.
I'll talk with chad and see what he is cooking up... I havent talked to him a whole lot this weekend.
sent from ICEvo
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
this is true... but again, what is your explanation of the galaxy nexus having the same issue, and the fact that a sprint rep was entirely aware of the issue and that is was being worked on and would come in an update?
and surprise, but any new technology is "beta" ..... whether it is an official release or not. it is the price you pay for cutting edge technology.
sent from ICEvo
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
raptoro07 said:
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
Click to expand...
Click to collapse
from what the lady explained to me, yes it is... intermittent data loss is a bug within the new firmware for ICS
my point here is that it has nothing to do with your ROM being intended for a virgin mobile 3D. it is because of a bug within the firmware for the radios.
as i said, sprint rep explained this to me, and seemed very confident in the way she explained it - confirming it as a known issue, and also knowing that it would be fixed soon because it was being worked on and said it would be serviced as a firmware update.
sent from ICEvo
You think a sprint tech in the store is an authority !!
For one thing, many may not care, you lose VPN capabilities. Which I need and want and has nothing to do with ICS. Flashed back to GingerBread an it's still gone.
You may also lose the ability to properly update the PRI when new ones come out with official ICS.
It is not just a banner issue.
I'm not in a roaming area to confirm roaming issues but I believe folks when they say they can no longer roam on th 3G. I never touched my default roaming settings and it always worked fine. You may be right that roaming is only ICS issue. But it smells like it's way more than that by folks reports. And quite believable given the phone half believes it's on Virgin Mobile.
It is the PRI which manages routing that is not correct. And different folks will get different issues depending on their location.
I don't think chad and friends would be working so hard to fix it if it was such minor issue and I trust them more than some sprint sales person.
Like was stated above. There are two kinds of people. Those with issues and those with no issues, YET !!
And please FIX the broken subject.
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
"issues" is a vague word. whats to say a person's issue is due to ICS, the radios, or anything else in particular?
The new radios made me gain 20 pounds. There's no information showing that the radios did or didn't cause this. Yet here we are proverbially attributing all these issues to one thing or the other, when in reality WE DO NOT KNOW what is causing these problems.
retnuh730 said:
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
Click to expand...
Click to collapse
People here are not stupid. Most do backups before they try something.
I restored a backup and lost capabilities I had.
I reflashed every every sprint RUU, Reflash Hboot 1.40, restored back up and things are not the same.
If you flashed that freeza patch your phone has it's feet in both Sprint and Virgin Mobile and it's not good.
Yes, we know we screwed up. And some of us would like it fixed before we get more surprises of what does not work correctly.
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
What is the "setprop" an ADB command? Do you have to use it. I edited the build.prop how you said reset the phone and nothing changed. I am roaming and cannot connect to data. My phone's data works fine when in a coverage area, but obviously not when roaming. I never did any kind of firmware update. Hope that helps.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
powduh09 said:
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
Click to expand...
Click to collapse
+1 this is a direct pull of the ruu for the upcoming vm evo 3d
Sent from my PG86100 using Tapatalk 2
to anyone that hasn't seen it already, if you flashed this firmware, chad is working on a fix over that this thread
http://forum.xda-developers.com/showthread.php?t=1638225&page=41
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
successfully implemented this. Hope this solves the no roaming issue. Thanks
Visionikz03 said:
successfully implemented this. Hope this solves the no roaming issue. Thanks
Click to expand...
Click to collapse
How were you able to do this? I'm trying to research a little on setprop.....but still not fully understanding it
Sent from my PG86100 using xda premium
I recently rooted using RegawMOD EVO 4G LTE Rooter method and then flashed CM 10. The only problem I have is that the following error message pops up right when the phone boots up. "Unfortunately, the process com.android.phone has stopped."
I have seen recommendations from others to clear data within the Contacts Storage app. and it did Not work
I have flashed several nightly's from CM 10 and keep having the same issue.
I have attempted to Fix Permissions within TWRP (v2.2.2.0)
Also attempted to wipe the Cache and Dalvik Cache and still having the error msg pop up at startup.
Any help would greatly be appreciated.
its a known issue, nothing you do will fix it. Its not a high priority and it doesnt affect anything regardless
Did you even read the op? The issue is clearly posted in the op for cm10
Sent from my Cm10 powered Evo Lte!!
kaos420 said:
Did you even read the op? The issue is clearly posted in the op for cm10
Sent from my Cm10 powered Evo Lte!!
Click to expand...
Click to collapse
I did not, i found the issue and then checked the thread. Then several weeks later the op did not do the same. For future reference, please look first in situations like this. That is all
om4 said:
its a known issue, nothing you do will fix it. Its not a high priority and it doesnt affect anything regardless
Click to expand...
Click to collapse
How is this not a high priority? The error pops up constantly making it impossible to actually use the rom other than continually saying ok to the error message. I don't understand why you would say this doesn't affect anything.
It's not a priority because it only happens when the phone is searching for signal
om4 said:
It's not a priority because it only happens when the phone is searching for signal
Click to expand...
Click to collapse
Why do u guys put up with all that crap on CM? I used to run cm7 on my og EVO, but all the stuff not working isn't really worth it. I thought I was cool to be "different", had no Bluetooth, GPS or WiMAX, but I put up with it. When is it enough to say, yeah, this sucks, I'm going back to stock roms?
I mean it is jelly bean and a work in progress, I get that. But what is so great other than it runs super fast and is debloated? Personally, the interface of cm anything seemed so vanilla, no matter how much I themed it.
Let's see, its support by a great team of developers, it is steadily updated and maintained for phones well past eol, and its lightweight compared to sense, 165MB or there about compared to 450+MB. I've never had any major problems with cm, pretty much everything has always worked. The only issue I had was WiMAX on my og EVO and Shinzul did such an awesome job getting WiMAX to work that google merged the commit officially
There are times when I only get that error once on initial boot up as was mentioned by the op. Then there are times when it occurs so frequently that I need to reboot because it is unbearable. It usually goes away once rebooted though.
Hi everybody. I have been reading many of the posts here over the past 6 months and trying to learn as much as I can about different ROMs and issues related to my particular phone which is the Samsung Epic 4G Touch.
Thanks Exit_Only for your helpful work in this thread: http://forum.xda-developers.com/showthread.php?t=1975379. In that thread Sydius 08 asked "How are the Stable 1 tweaks running for you guys? Running CM10 11/18 nightly" I would like to focus on one aspect of that.
First I am currently running cm-10-20121117-UNOFFICIAL-d710 with gapps-jb-20121011-signed. I had installed JellyBeanMod_Stable-One_EO in hopes that it would resolve my long-standing GPS issue. I have read so many threads and I do appreciate all of the comments and attempted fixes by this community. I also use GPS Status and GPS Essentials where I see zero satellites but saw eight or nine instantly with #3 below. Here are the three times when my GPS has worked:
1) When I first got it just over a year ago. It was running Gingerbread 2.3.x (don't remember the last number but think it was 1). It worked perfectly but stopped after about 2 months and worked on and off after that.
2) After the GPS completely stopped working I started learning all I could about using a custom ROM. I tried CyanogenMod 9 but it did not resolve the issue. There's more to the story and more ROMs and tips provided here that I tried but all failed. However, whenever I Odin back to StockCWM-EL26.tar it works perfectly. I followed the tip about getting a fix prior to putting an ICS or JB ROM on.
3) I installed this on 11/15 http://sbrissen.chris41g.org/sbrissen-ALPHA6.zip and my GPS worked perfectly. However, lots of other apps failed miserably and it kept freezing up.
So here I am with nowhere else to turn. This latest CM 10 works perfectly EXCEPT the GPS. I would appreciate any thoughts on this.
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
smoresrock said:
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
Click to expand...
Click to collapse
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Shlickwilly said:
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Click to expand...
Click to collapse
Thank you. I had actually tried that one and ran into a problem with flashing it but I think that's because I didn't go back to StockCWM-EL26.tar first. I might give it a try again. I do love CM 10 and it would be perfect if the GPS worked.
For those who may not know this guy, QBKing77, is one of the best at teaching how to do this. Here is one for the SGIII and the Blazer ROM which he considers one of his favorites. I had to remove the link because I'm such a newbie. Here is the YouTube description: Blazer Rom on the Samsung Galaxy S III [REVIEW]
allenp007 said:
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
Click to expand...
Click to collapse
yep. this is the same method i used to fix my friend's GPS issue on a jelly bean ROM. after seeing to it that i was getting a GPS lock on the stock ROM, i went back into recovery, and flashed the ROM she wanted (paranoid android i think it was)... since then, she's been a happy camper locking into 7-9 satellites indoors
Great news! I was able to resolve this issue by following Qbking's YouTube tutorial: "How to Temporary Boot Stock EL29 on the Samsung Epic 4G Touch." I was able to lock on to 9 satellites and get a fix on my exact location. It was literally showing me in front of the building where I was standing.
I hope this helps someone else who might be going through the same problem with their GPS on an E4GT. If someone could post this information and possibly the link to the thread I referenced earlier I would appreciate it.
Thank you everyone for your comments.
So I just wanted to share something really weird and ask if anyone has ever seen anything like it before.
I recently flashed the last AOKP update, and my phone was running phenomenally. I went out last night and my battery died because I forgot to charge it... No biggie. Got home, turned it on, no signal. Odd, since I have pretty decent service in the area. After doing the usual troubleshooting of cycling airplane mode, I tried pulling the battery and sim. That also didn't work. I went into settings to check my APNs, and instead of the usual menu, I saw only 4 options. The option to select APNs wasn't even there. The last one said "Set CDMA..." something. I forget the rest. Wish I had remembered to take a screenshot. In "About Phone", my baseband was blank. Tried reflashing back to LC5 radio. Still nothing. Did a full wipe and reflash of the ROM, and that got me back in business. Right now, all is well. I was just unaware that a phone could magically switch over to CDMA, even if there is no CDMA radio in an i777.
Any thoughts on the cause?
EDIT:
ROM: Task's AOKP 4.14
Kernel: Stock
Radio: UCLL6 when issue started. Now on UCPLC5
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Phalanx7621 said:
Not an issue that's related to the rom, as far as I know. Unless others have reported this issue and I've missed it. If you do a full wipe and re flash as you've done and don't install any programs for a good 24 to 48 hours, and nothing of the sort happens again, odds are it has something to do with an app you installed. Unless your service provider maybe was experiencing problems at the time.
Click to expand...
Click to collapse
No, definitely an anomaly. Not something that anyone else has reported. I called AT&T to verify if there were any issues in the area or with my account, and everything checked out. I haven't downloaded a new application in months. I restored from TiBu right after reflashing and everything is still good. Like I said, not trying to report it or anything; just looking for thoughts.
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
votinh said:
You meant APN and baseband NEVER come to live? If that's the case, then I haven't heard or read any report about it.
If it's up and running like normal AFTER 5 minutes, then it's has been reported many many times last week.
Click to expand...
Click to collapse
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
nycmalu said:
No... More like APN and baseband were completely fine for almost a week, and then it suddenly stopped working while I was asleep.
Click to expand...
Click to collapse
Well, that's new to me.
Reflash with clean installtion?
I know none of us want to factory reset but some cases, we have to.
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I do agree. ....this is so strange that im putting my phone under 24/7 surveillance. No way I wanna see my phone transformed to CDMA
Hehe....:what:
Sent from SGH-S959G
Pirateghost said:
This is odd but in no way, shape, or form can a i777 transform its hardware to support CDMA
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
nycmalu said:
This is what I thought. I have a feeling that since AOKP is based of CM, there is code built in to support both CDMA and GSM. Somehow, the software glitched, and made the switch.
Click to expand...
Click to collapse
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
samprocat said:
I did confirm your theory. ...playing around to prduce same problem and yes ...very true. ....will play with logcat on next time to save and shoot to CM Team:screwy:
Sent from SGH-S959G
Click to expand...
Click to collapse
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
nycmalu said:
I don't know how you did it, but I'm glad you were able to reproduce the issue. At least I know I'm not crazy.
Click to expand...
Click to collapse
Yes this prop is built in rom just can't find the way to trigger this with log cat on......just need some more playing till this occurre again
Sent from SGH-S959G
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.