Related
I love the way it looks on other devices.... is there anyway we could possibly get it ported or otherwise get it to run on the Thunderbolt?
I wouldn't even care if it had data... just the camera and display... I have an extra Bolt and would love to use it as a iDroid.
je2854 said:
I love the way it looks on other devices.... is there anyway we could possibly get it ported or otherwise get it to run on the Thunderbolt?
I wouldn't even care if it had data... just the camera and display... I have an extra Bolt and would love to use it as a iDroid.
Click to expand...
Click to collapse
Patience is a virtue. . @disconnecktie
jonah1234 said:
Patience is a virtue. . @disconnecktie
Click to expand...
Click to collapse
I'll take that as it is on it's way... Thank You
je2854 said:
I'll take that as it is on it's way... Thank You
Click to expand...
Click to collapse
I've been helping jblack with a pretty big project recently but once that is posted I'll be back on paranoid android.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I've been helping jblack with a pretty big project recently but once that is posted I'll be back on paranoid android.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
@disconnecktie I am seeing you everywhere AND on a lot of projects..... Thanks for being such a great dev.
I know you are working on CM9 BUT I would take PA over any ROM any day. If you could push PA up in the queue there just might be some
Pepsi/Caffiene/alcohol/your choice of poison in abundance headed you way :b
P.S. Pepsi is my choice of drug is the only reason why I said that lol
Lol well I have a semi working port already but calling doesn't work properly atm. It makes the call but the mic or speaker don't work in call yet. I'm going to rebase it off of the cm9 that jblack and I have been working on once it is more stable.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Lol well I have a semi working port already but calling doesn't work properly atm. It makes the call but the mic or speaker don't work in call yet. I'm going to rebase it off of the cm9 that jblack and I have been working on once it is more stable.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
could I possibly get a copy of that? I want it for my iDroid I use for work... We aren't allowed phones but CAN have music.
I don't want the rebase just the one that semi-works :b
Check you PMs
Sent from my ADR6400L using Tapatalk 2
Netflix
Does Netflix work on any of these builds you guys are working on? I am running the multi-source aosp from twistedumbrella and that's one of few things that don't work on it.
bedward1229 said:
Does Netflix work on any of these builds you guys are working on? I am running the multi-source aosp from twistedumbrella and that's one of few things that don't work on it.
Click to expand...
Click to collapse
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Haha that's a good start though. I don't think it's a big deal really, even if it never works its definitely not a deal breaker I was just curious. It's cool that you guys are still working on it, thanks for what you do.
I should be taking care of what we talked about yesterday... I have the Sasba ROM with 4EXT on it now...
disconnecktie said:
Not a high priority atm. Getting the kernel and data squared away are a little higher on the list but we're going to address it once we have time. I think its either a drm issue or a dhcp issue. At any rate, in my testing I was able to get it to play audio but video still wouldn't play so it may be a codec issue. I guess if you like to listen to movies you're all set
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
So you're telling me you don't just listen to movies all day on Netflix?
jonah1234 said:
So you're telling me you don't just listen to movies all day on Netflix?
Click to expand...
Click to collapse
Well of course I do... That's why it's on the back burner duh.
Sent from my ADR6400L using Tapatalk 2
I have noticed that any ROMs based on the international base have a problem with putting my Note II into roaming whenever I am connected to my network extender at home. Any ROMs built on the Verizon base work just fine. My question is: can I backup my modem settings with TWRP, flash a ROM built on the international base and then restore the modem as the last step to get around this issue?
Sorry if this is a noob question, but I am new to Android and custom ROMs.
ControlD said:
I have noticed that any ROMs based on the international base have a problem with putting my Note II into roaming whenever I am connected to my network extender at home. Any ROMs built on the Verizon base work just fine. My question is: can I backup my modem settings with TWRP, flash a ROM built on the international base and then restore the modem as the last step to get around this issue?
Sorry if this is a noob question, but I am new to Android and custom ROMs.
Click to expand...
Click to collapse
The modem stays with every flash until you flash a new one, you don't have to worry about it. As for what you want to do I don't think it would matter about the Network Extender, everything you would need would be built in to the international Roms on our forums, but I'm not 100% sure as I've never came across this before.
Sent from my SCH-I605 using XDA Premium HD app
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
shangrila500 said:
The modem stays with every flash until you flash a new one, you don't have to worry about it. As for what you want to do I don't think it would matter about the Network Extender, everything you would need would be built in to the international Roms on our forums, but I'm not 100% sure as I've never came across this before.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the information. I figured the solution probably wasn't that easy.
ControlD said:
Thanks for the information. I figured the solution probably wasn't that easy.
Click to expand...
Click to collapse
Well sting as how the modem carries over no matter what you flash then you wouldn't have a problem there. How does the extender work? Do you connect like WiFi or does the phone automatically pick it up or do you have a special app? I don't think you'd have assn issue as long as you stayed on TW but AOSP you may depending on how the extender works.
Sent from my SCH-I605 using XDA Premium HD app
The network extender connects to a home wireless network so you are basically doing VOIP when connected to it. There is no app to use, the phone automatically uses the extender when it is available.
Sent from my SCH-I605 using Tapatalk 2
ControlD said:
The network extender connects to a home wireless network so you are basically doing VOIP when connected to it. There is no app to use, the phone automatically uses the extender when it is available.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Then it should work with any ROM.
The only thing I have found is this:
http://forum.xda-developers.com/showthread.php?t=2108887
The only time problems were experienced was on AOSP, and that was only due to a leaked modem that probably wasn't optimized yet, so I would bet you won't have any issues
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Then it should work with any ROM.
The only thing I have found is this:
http://forum.xda-developers.com/showthread.php?t=2108887
The only time problems were experienced was on AOSP, and that was only due to a leaked modem that probably wasn't optimized yet, so I would bet you won't have any issues
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the link. That is pretty much exactly what happens for me with any AOSP/International base ROM. I am guessing that network extenders are a Verizon/US only device and perhaps that explains why only Verizon based ROMs properly recognize the extender. The extender itself actually works and my phone calls properly get routed through the extender. The phone however is always on roaming when connected to the extender, so if data roaming for example is turned off things get a little difficult. It isn't a huge deal really, it just keeps me from using some of the more interesting AOSP type ROMs that are available.
ControlD said:
Thanks for the link. That is pretty much exactly what happens for me with any AOSP/International base ROM. I am guessing that network extenders are a Verizon/US only device and perhaps that explains why only Verizon based ROMs properly recognize the extender. The extender itself actually works and my phone calls properly get routed through the extender. The phone however is always on roaming when connected to the extender, so if data roaming for example is turned off things get a little difficult. It isn't a huge deal really, it just keeps me from using some of the more interesting AOSP type ROMs that are available.
Click to expand...
Click to collapse
You could ask Scott if there is a fix for Cleanrom and ask Beans the same thing. You could also ask in the AOSP threads if there is any way for that to be worked on, its very very odd....
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
You could ask Scott if there is a fix for Cleanrom and ask Beans the same thing. You could also ask in the AOSP threads if there is any way for that to be worked on, its very very odd....
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Once I build up the proper post count I will see if those guys have an idea on this.
Sent from my SCH-I605 using Tapatalk 2
ControlD said:
Once I build up the proper post count I will see if those guys have an idea on this.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
It may be something that was either taken out to make the ROM more sleek or not added to the international base.
Sent from my SCH-I605 using XDA Premium HD app
I've noticed only a few ROMS available for the Sprint Note 3. I know Sprint is always a few months behind other carriers but I do greatly prefer Sprint over all other carriers. For their political beliefs there environmental outlook and quality of service. Though... One of my favorite things to do is flash ROMS and tweak my devices. So I'm now I'm in a position where my carrier is preventing me from doing one of the things I enjoy doing. I'm wondering if the ROM developers can start porting their ROMS for SM-N900P Sprint Note 3, or is there a moderately difficult process someone can point me to so I can port them myself. I can follow directions no matter how difficult but I cannot program.
freeza said:
We're in second place in overall threads and as far as the amount of posts, we're in 4th place, but still. While I know this doesn't represent ROMs, it does show activity, and we're not a ghost town. So, please, stop complaining about the lack of development here on the Sprint Galaxy Note 3 forum. We're as active as can be at the moment.
Click to expand...
Click to collapse
Sent from my SM-N900P using Tapatalk
Why not I'm running x note on my phone and have everything working except the camera...
Sent from my SM-N900P using Tapatalk
"So I'm now I'm in a position where my carrier is preventing me from doing one of the things I enjoy doing."
just a bit dramatic, technically they are not stopping you. the lack of roms is stopping you.
but i digress...
While I'm always for more roms, i like mine to be different enough from each other to be able to tell what i'm flashing.
i guess we could just get a bunch of very similar roms that way you could just flash a new one all day.
though i say with the ones we have, and at the rate they get updated, if yuo install them and play around with each one, by the time you were done there would be updates to the first ones to go back and start the whole series over.
that wasn't a run on sentence by the way.
porting roms is a whole can of worms...
starting with getting permissions from the original authors
to figuring out what needs to be changed to make it work.
can be painfree and simple
or can be worse than doing it from scratch.
though i have a prediction, not that i would have heard or anything, that we will see a few new roms shortly.
shhhhhhhhhhhh dont tell them i told you they wil AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
mjcollum said:
"So I'm now I'm in a position where my carrier is preventing me from doing one of the things I enjoy doing."
just a bit dramatic, technically they are not stopping you. the lack of roms is stopping you.
but i digress...
While I'm always for more roms, i like mine to be different enough from each other to be able to tell what i'm flashing.
i guess we could just get a bunch of very similar roms that way you could just flash a new one all day.
though i say with the ones we have, and at the rate they get updated, if yuo install them and play around with each one, by the time you were done there would be updates to the first ones to go back and start the whole series over.
that wasn't a run on sentence by the way
though i have a prediction, not that i would have heard or anything, that we will see a few new roms shortly.
shhhhhhhhhhhh dont tell them i told you they wil AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Click to expand...
Click to collapse
preach on brother!
ram9200 said:
Why not I'm running x note on my phone and have everything working except the camera...
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Interesting did you have to do some tweaking or just flash and use. I didn't think Sprint could you other carriers ROMs.
Sent from my SM-N900P using Xparent Skyblue Tapatalk 2
Definitely had to tweak, had to mess with the framework
Sent from my SM-N900P using Tapatalk
I wonder the same thing is to why we have a very small list of ROMS.
Sent from my SM-N900P using XDA Premium 4 mobile app
For those with the black screen during calls and can't wake call screen...it's not perfect fix but I figured out that if your screen won't wake after pulling it away from your ear tilt it flat like it was laying on a flat surface...it wakes every time for me
HTML:
Blow compressed air into the ear piece.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Blow compressed air into the ear piece.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Its not that...works fine on touchwiz ROMs...only time I see problem is on aosp roms using ktoonsez newer kernels...he will get it ironed out soon I'm sure...but I figured I would post this to help others with same issues
Hmm I've never had that problem when I ran ktoons kernel before.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Hmm I've never had that problem when I ran ktoons kernel before.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Me either...but latest 2 kitkat builds from him have given me this issue... When I run stock cm kernel I don't have problems
jamesd1085 said:
Me either...but latest 2 kitkat builds from him have given me this issue... When I run stock cm kernel I don't have problems
Click to expand...
Click to collapse
I don't have that problem on beanstalk 4.4 ROM with KT kernel.
Everything runs great.
Just one of those things I guess.
Sent from my SCH-I545 using XDA Premium 4 mobile app
.
honkeydick69 said:
I also had proximity sensor issues... Mine turned out to be the white otter box case I have. I just used black sharpie on the case around the sensors, front camera and earpiece and it works just fine now.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Interesting, so the reflection from the white was causing false readings?
Sent from my SCH-I545 using xda app-developers app
Check this post over on the CM11 thread. Lot's of folks thought it was a software problem, but turns out it's just dirty glass in front of the sensor.
Jeff
blulite said:
Check this post over on the CM11 thread. Lot's of folks thought it was a software problem, but turns out it's just dirty glass in front of the sensor.
Jeff
Click to expand...
Click to collapse
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Lol
CM fanboy BS
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Lol
CM fanboy BS
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.
Click to expand...
Click to collapse
I expect bugs in any ROM, including stock ones. However, I must say, that I was experiencing this issue, and without changing anything software wise, I used compressed air on the earpiece, and it fixed the problem.
joshm.1219 said:
Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I had similar issues on TW. Did a quick Google search and found some stuff about dirty sensor. I too thought it sounded crazy, but gave it a try. When I disassembled my back-plate it was easy to see the black haze on the backside of the glass. A q-tip, alcohol, and all fixed. It worked very reliably (like new) on TW, so I decided to try CM11 again. Sure enough, the sensor worked fine with CM11. I posted over on that thread as many folks had been commenting of this problem and everyone assumed it was something broken in CM11.
Read the next handful of posts in the CM11 thread. At first a few called BS on the post, then several folks started trying it and all commented that it worked.
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
blulite said:
I had similar issues on TW. Did a quick Google search and found some stuff about dirty sensor. I too thought it sounded crazy, but gave it a try. When I disassembled my back-plate it was easy to see the black haze on the backside of the glass. A q-tip, alcohol, and all fixed. It worked very reliably (like new) on TW, so I decided to try CM11 again. Sure enough, the sensor worked fine with CM11. I posted over on that thread as many folks had been commenting of this problem and everyone assumed it was something broken in CM11.
Read the next handful of posts in the CM11 thread. At first a few called BS on the post, then several folks started trying it and all commented that it worked.
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
Click to expand...
Click to collapse
spotmark said:
I expect bugs in any ROM, including stock ones. However, I must say, that I was experiencing this issue, and without changing anything software wise, I used compressed air on the earpiece, and it fixed the problem.
Click to expand...
Click to collapse
The point is that if it works on TW without cleaning the sensor but doesn't on CM/AOSP, there's a software issue.
EDIT: not saying that cleaning the sensor wont fix it for the user, but it's like if you plug a hole in your tire.... theres still a hole in your tire.
Sent from my SCH-I545 using Tapatalk
blulite said:
But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
Click to expand...
Click to collapse
Hey that's great it out figured out and you ended up helping others that's what XDA is all about..
Sometimes people's sense of humor just gets misinterpreted through simple text.
Anyways good stuff!
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
EDIT: not saying that cleaning the sensor wont fix it for the user, but it's like if you plug a hole in your tire.... theres still a hole in your tire.
Click to expand...
Click to collapse
Not trying to start a fight, and I'm certainly no fanboy, but I have to disagree with that analogy. If it is due to dust, or debris, and you remove it, there is no hole. Anyway, carry on.
spotmark said:
Not trying to start a fight, and I'm certainly no fanboy, but I have to disagree with that analogy. If it is due to dust, or debris, and you remove it, there is no hole. Anyway, carry on.
Click to expand...
Click to collapse
Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?
Click to expand...
Click to collapse
I agree with that. I guess what I'm trying to say is, that people might be experiencing it for two different reasons. For some, it may be software related, for others, it may be a physical obstruction. So you can't just discount the air fix.
spotmark said:
I agree with that. I guess what I'm trying to say is, that people might be experiencing it for two different reasons. For some, it may be software related, for others, it may be a physical obstruction. So you can't just discount the air fix.
Click to expand...
Click to collapse
Fair enough , sorry if I came off wrong.
Sent from my SCH-I545 using Tapatalk
I just updated to 4.4.2. Been having Bluetooth issues in my Lexus ever since. I can establish a connection but my contacts will no longer transfer. The Bluetooth music intermittently disconnects and reconnects. I havent made any BT calls yet so I don't know how that is behavin. My messages won't transfer as well (call logs do though). I have un-paired and re-paired the phone several times. Usually that does the trick. I am a Lexus Technology Specialist and I deal with these little BT issues all of the time. None of my tricks are working. So disappointed with KitKat right now.
Can I go back? Anything else I can try? Any help is appreciated. Thanks
Blipstein said:
I just updated to 4.4.2. Been having Bluetooth issues in my Lexus ever since. I can establish a connection but my contacts will no longer transfer. The Bluetooth music intermittently disconnects and reconnects. I havent made any BT calls yet so I don't know how that is behavin. My messages won't transfer as well (call logs do though). I have un-paired and re-paired the phone several times. Usually that does the trick. I am a Lexus Technology Specialist and I deal with these little BT issues all of the time. None of my tricks are working. So disappointed with KitKat right now.
Can I go back? Anything else I can try? Any help is appreciated. Thanks
Click to expand...
Click to collapse
I'm sorry that I don't have advice on how to fix your problem. I just wanted to let you know that I am having zero connection problems with the bluetooth to both of my vehicles. They are both Hyundai's if that makes a difference. Are you on the official KitKat or Freeza's "Stockish" rom. I am on Stockish deodex if that helps.
Possibly bad download? Are you having any other issues?
cmdauria said:
I'm sorry that I don't have advice on how to fix your problem. I just wanted to let you know that I am having zero connection problems with the bluetooth to both of my vehicles. They are both Hyundai's if that makes a difference. Are you on the official KitKat or Freeza's "Stockish" rom. I am on Stockish deodex if that helps.
Possibly bad download? Are you having any other issues?
Click to expand...
Click to collapse
I'm on KitKat. Just did the official download Sunday. Only other issue so far is that Astro player (music player I use for listening to Howard Stern. Great for bookmarks since the tracks are 4.5 hours long) is acting weird about the music files. Hard to explain but just odd behavior.
If it was a bad download is there a way to re-download it? I suppose the only way to go back would be to root and flash a ROM?
Thanks dude
cmdauria said:
I'm sorry that I don't have advice on how to fix your problem. I just wanted to let you know that I am having zero connection problems with the bluetooth to both of my vehicles. They are both Hyundai's if that makes a difference. Are you on the official KitKat or Freeza's "Stockish" rom. I am on Stockish deodex if that helps.
Possibly bad download? Are you having any other issues?
Click to expand...
Click to collapse
Did you try the platform edit?
It might very well be that the bluetooth permissions granted by jellybean aren't allowed for KitKat. It would at least rule out that possibility.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Did you try the platform edit?
It might very well be that the bluetooth permissions granted by jellybean aren't allowed for KitKat. It would at least rule out that possibility.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I have no idea what the platform edit is.... Lol. Please explain
Blipstein said:
I have no idea what the platform edit is.... Lol. Please explain
Click to expand...
Click to collapse
If you're rooted, unzip this file, then using root explorer, navigate to system, etc, permissions, rename the platform.xml file that already resides there (add bak to the name), then copy, paste, and set permissions with this file gifted to me by @blackcanopy.
https://www.dropbox.com/s/enfjwbrxk2skzyu/platform.rar
Lol®
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
If you're rooted, unzip this file, then using root explorer, navigate to system, etc, permissions, rename the platform.xml file that already resides there (add bak to the name), then copy, paste, and set permissions with this file gifted to me by @blackcanopy.
https://www.dropbox.com/s/enfjwbrxk2skzyu/platform.rar
Lol®
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I'm not rooted. Haven't been since my EVO days. Does this mean I'm out of options?
Blipstein said:
I'm not rooted. Haven't been since my EVO days. Does this mean I'm out of options?
Click to expand...
Click to collapse
Not at all. I was just testing a theory, and thus it may not even work. If I'm wrong, you've blown Knox for nought.
You could try reading up a bit on the new restrictive write permissions introduced by this flavor of KitKat (TouchWiz). If that is causing your problem, which it may very well be, then you should contact the manufacturer of your device (the bluetooth, not the phone), as I'm certain that you're not the only guy using that product. If yes, then others will be reporting the same problem, and the company will have to fix it. Time here is your option (ie, waiting for this to be a repeating headache for the manufacturer, so they do something about it).
Rooting and flashing roms may not solve your issue. I'd suggest taking the approach with which you're most comfortable, and nothing more.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Not at all. I was just testing a theory, and thus it may not even work. If I'm wrong, you've blown Knox for nought.
You could try reading up a bit on the new restrictive write permissions introduced by this flavor of KitKat (TouchWiz). If that is causing your problem, which it may very well be, then you should contact the manufacturer of your device (the bluetooth, not the phone), as I'm certain that you're not the only guy using that product. If yes, then others will be reporting the same problem, and the company will have to fix it. Time here is your option (ie, waiting for this to be a repeating headache for the manufacturer, so they do something about it).
Rooting and flashing roms may not solve your issue. I'd suggest taking the approach with which you're most comfortable, and nothing more.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Well...I am the manufacture of the product basically. The product is Lexus and I am the Technology Specialist for the dealership. I deal with BT all day long. I have not encountered this particular issue with an Android device. And if I have encountered it I have several processes that typically resolve the issue. None of them worked. So I am confident that the product (Lexus) is working correctly.
I would really love to revert back to ICS. Is that possible somehow? Maybe re-load KitKat? I just want my phone the way it was because this issue is debilitating as I use BT everyday.
Thanks
Blipstein said:
Well...I am the manufacture of the product basically. The product is Lexus and I am the Technology Specialist for the dealership. I deal with BT all day long. I have not encountered this particular issue with an Android device. And if I have encountered it I have several processes that typically resolve the issue. None of them worked. So I am confident that the product (Lexus) is working correctly.
I would really love to revert back to ICS. Is that possible somehow? Maybe re-load KitKat? I just want my phone the way it was because this issue is debilitating as I use BT everyday.
Thanks
Click to expand...
Click to collapse
I use bluetooth daily as well, but via a headset, not the setup you've described.
As to reverting to ICS, it doesn't appear to be possible for you on this device, as this phone came with 4.3 out of the box, whereas 4.04 was compatibility ancient. Many core features of Android just are not available, including Google Now.
I am at a loss here, but I wonder if a call to Samsung would at least bear fruit, as they have a lot of phones running KitKat. Hit them with the Lexus disfunctionality, you deal with a lot of cars, and this phenomenon hit when KitKat hit.
Perchance a senior level tech could troubleshoot with you. It's a good demographic to want to please and not irritate. You've got an incentive for them to help.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Have you done a master reset since the update?
It's a pain but that will tell you if it's a compatability issue or just something that hung around after the update.
I have not. So maybe try a "factory data reset"? Will the device still have the KitKat update?
Blipstein said:
I have not. So maybe try a "factory data reset"? Will the device still have the KitKat update?
Click to expand...
Click to collapse
Yup. Resets everything to either stock in system, or retains any system mods you've made. Thus, if an inverted app resides in system priv-app and the other one is gone, the invert will still be there afterwards.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Called Samsung. They want me to go to a sprint store and reflash KitKat. Gonna try that. I'll report back
Blipstein said:
Called Samsung. They want me to go to a sprint store and reflash KitKat. Gonna try that. I'll report back
Click to expand...
Click to collapse
Have you tried a simple unpairing/repairing after the update? That's one thing I've always had to do a lot on Samsung phones (sometimes over and over like 3 times) after a big update or else it would act stupid and not work correctly.
Sent from my SPH-L900 using xda app-developers app
RayTrue04 said:
Have you tried a simple unpairing/repairing after the update? That's one thing I've always had to do a lot on Samsung phones (sometimes over and over like 3 times) after a big update or else it would act stupid and not work correctly.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I think he indicated that in the OP.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I think he indicated that in the OP.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
My bad. Sad part is I read the OP and totally missed that. No more alcohol for me lol
Sent from my SPH-L900 using xda app-developers app
Blipstein said:
Called Samsung. They want me to go to a sprint store and reflash KitKat. Gonna try that. I'll report back
Click to expand...
Click to collapse
wondering if the trip to the sprint store fixed your issue because i have the same issue.
Aloth600 said:
wondering if the trip to the sprint store fixed your issue because i have the same issue.
Click to expand...
Click to collapse
Hey... Sorry I didn't get back to you guys. I did a "factory data reset" and that seemed to have fixed it. Didn't go into the sprint store.
My contacts won't update in my car but it did it at least once right after the reset so at least my contacts are there. I bet a re-pairing will take care of that. Bluetooth audio and phone have been consistently working correctly. Hope this helps you out
I have done almost every fix for blue tooth I can find. The problem I am having is I connect my ear piece and make of receive a call and 10 to 30 seconds later it disconnects. The blue tooth icon still says connected. If I turn the ear piece off and then on it will reconnect only to do the same thing again.
I am on stock 4.2.2 rooted.
Any help would be great.
Things I have done:
Master reset
Pair and unpaired
Odin back to stock and re rooted
Ryan
Sent from my SM-N900P using xda app-developers app