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
Related
Hey folks, I've done a bit of searching, but I've yet to find anyone with this specific issue with my VZW S4.
All of a sudden I do not have ANY sounds what so ever....I've tried working with settings (sounds, adapt sounds, etc.), rebooting, clearing cache with CWM, pulling the battery. I do have sound from headphones.
Yesterday evening I went to a doctors appointment and muted/put phone on vibrate (don't remember which) and noticed when I got home and returned to normal sound mode in the pulldown that I no longer had any sounds....
I have a Rooted stock MDK...I have not cleared or wiped to factory settings and I've never installed a custom ROM....only rooted and have CWM Recovery (did this about two weeks ago).
Any clue/ideas as to what this could be? Will wiping with CWM clear it up? If I wipe to factory settings, will lose root?
Same issue
Sent from my SCH-I545 using Tapatalk 4
Well, I performed a factory rest with CWM Recovery.....no luck. Still no sounds at all....no notification, speaker, alarm, ringer, etc.
Has anyone else experienced this besides the above poster??
Maybe try restoring stock MDK through Odin. Then re-root. Make sure you don't take the OTA though.
Sent from my SCH-I545 using XDA Premium 4 mobile app
haza12d said:
Maybe try restoring stock MDK through Odin. Then re-root. Make sure you don't take the OTA though.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks!
That's my next option...I've already started to install CM RC2 and its rebooting now. Crossing fingers.
redwings73 said:
Thanks!
That's my next option...I've already started to install CM RC2 and its rebooting now. Crossing fingers.
Click to expand...
Click to collapse
No luck with flashng CM RC2....crap. It must be a phone hardware issue (?)....I'd rather not return it for fear they'll send me a refurb. Worse yet, a refurb with ME7....
BT can cause this to happen. Try sound about from market
NilsP said:
BT can cause this to happen. Try sound about from market
Click to expand...
Click to collapse
What is BT? I just downloaded SoundAbout.....will try that for sure.
redwings73 said:
What is BT? I just downloaded SoundAbout.....will try that for sure.
Click to expand...
Click to collapse
Sorry BlueTooth
NilsP said:
Sorry BlueTooth
Click to expand...
Click to collapse
Ahhh...I should have know.
I've tried a number of things with no luck.....it seems to be a hardware issue. Verizon is overnighting a new (by new, I mean slightly used, right?) S4. Hoping it will be a MDK and not ME7, but I don't have my hopes up.....
Now on to deleting root apps, Triangle Away and Unroot to stock.....
This thread can be closed.... Verizon is sending a replacement.
Sent from my SCH-I545 using Tapatalk 4
You should have tried a battery pull
Sent from my SCH-I545 using XDA Premium 4 mobile app
scottgalit61 said:
You should have tried a battery pull
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah....why didn't I think of that?
Sent from my SCH-I545 using Tapatalk 4
No Sound At all
Sorry to revive but I wanted some advice
I bought my S4 with VRUAMDK firmware used hence I seriously doubt I can ask Verizon to replace it.
when I got it it tested fine I made calls
after rooting it just stopped making any sounds or phone calls, (I'm pretty certain I followed the rooting instructions correctly)
tried unrooting, going back to stock and rerooting and trying several ROMS I still have no sound whatsoever no headphones nothing, it does eventually detect the headphone if plugged in, even in the diagnostic menu sound doesnt work
I can browse using mobile data I can attempt a call and the other phone rings but the dialer doesnt work after placing the call the phone hangs or restarts sometimes.
everything else works I can send and receive text messages, emails, cameras work. etc
if this is a hardware issue what needs to be replaced? any idea whats the best way to get this fixed?
If I need to start a new thread let me know
i was so super happy with my phone when i was on 4.2.2. since the upgrade, i have been experienceing wi-fi connection issues that have been driving me crazy. i have tried everything i know. at this point, i just want to revert back to 4.2.2.
can someone please tell me if this is possible and if so......in nooby terms how do i do it ?
i'm certain i must be rooted which i plan on doing asap !
loco63 said:
i was so super happy with my phone when i was on 4.2.2. since the upgrade, i have been experienceing wi-fi connection issues that have been driving me crazy. i have tried everything i know. at this point, i just want to revert back to 4.2.2.
can someone please tell me if this is possible and if so......in nooby terms how do i do it ?
i'm certain i must be rooted which i plan on doing asap !
Click to expand...
Click to collapse
Unfortunately theres no going back once excepting a OTA update. MDK is the only version with custom recovery. Hopefully Hash will crack a safestrap method but even if he does you'll probably still need a 4.3 Stock kernel. Have you tried a factory reset? Might solve your wifi issues.
Sent from my SCH-I545
Thanks for the info. Do you think if I root and install a custom ROM it may help or am I simply spinmng my wheels until the next OTA ?
I guess I'm wondering if one of the custom Roms might have a better radio ?
Sent from my SCH-I545 using Tapatalk
loco63 said:
Thanks for the info. Do you think if I root and install a custom ROM it may help or am I simply spinmng my wheels until the next OTA ?
I guess I'm wondering if one of the custom Roms might have a better radio ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well there is root exploit, but no custom recovery. So flashing anything isn't possible ATM to even change radios. Also, Samsung is locking everything down with Knox making it more difficult. Hopefully a 4.4 stock leak will save us with bootloader hacks. Trying to be optimistic
Sent from my Nexus 7
That hurts my feelings. Lol.
I sooooo wish I had not upgraded. Darn it !!
Sent from my SCH-I545 using Tapatalk
loco63 said:
That hurts my feelings. Lol.
I sooooo wish I had not upgraded. Darn it !!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
lol Yeah it sucks. I know the feeling. Have you tried a factory reset to see if your WiFi issues are fixed?
If that doesn't fix it you could tell Verizon you tried everything and it should be covered by your warranty for a new replacement.
Sent from my Nexus 7
Factory reset is the only thing I have not tried.
You know, I have not installed Knox. The icon is there but I have not hit the install option. Also, I was reading that there is a way to disable it.
Does that make any difference with flashing an older radio ?
Sent from my SCH-I545 using Tapatalk
loco63 said:
Factory reset is the only thing I have not tried.
You know, I have not installed Knox. The icon is there but I have not hit the install option. Also, I was reading that there is a way to disable it.
Does that make any difference with flashing an older radio ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No, unfortunately. The bootloader needs to be unlocked or exploited in some way for you to be able to get a custom recovery to flash something. No one's been able to crack the firmware for months now, much less 4.3 which just came out.
Sent from the 215
So, if this is the case, what would be the point in bothering to root right now ?
Sent from my SCH-I545 using Tapatalk
To keep them from upgrading you to an even later version that might not be vulnerable to whatever exploit they will eventually discover. (I have a PSP with a version that everyone said was unrootable yet here it is.. playing roms)
Sent from my i337 MF3 using tapatalk.
loco63 said:
So, if this is the case, what would be the point in bothering to root right now ?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I personally wouldn't use the vroot method, shady code & people behind it, but there's lots of benefits to rooting IMO. If you're happy you probably don't need to.
Sent from the 215
I just want my WiFi back to what it was on 4.2. It was my contact with the outside world while stuck at work.
Guess I'm willing to do what ever necessary. Sadly, I've even been considering going back to my iPhone since this update to 4.3.
Sent from my SCH-I545 using Tapatalk
OP, you never said what the wifi issues actually are. A zillion people are on 4.3/MK7 and doing fine with everything.
People do that all the time here and in other forums in other aspects of life. They have a problem, think of the only solution they can imagine, then ask for help implementing it. A better question is can I get help/ideas to correct the original problem.
My apologies, your right. I went back and read my OP. I didn't say what my issues are.
Well, my employer privides an open WiFi for the office. The signal is not extremely strong but it's fair. Signal strength does dip up and down a little.
So while on 4.2, my phone stayed connected to the WiFi. Never disconnected. Once I upgraded to 4.3, it will not stay connected. It constantly drops the signal, scans, sees the signal but won't reconnect. I have to manually force it to connect.
As soon as I sit the phone down and it sleeps, it disconnects again and the process starts over.
The constant scanning is draining my battery fairly quickly.
Sent from my SCH-I545 using Tapatalk
loco63 said:
My apologies, your right. I went back and read my OP. I didn't say what my issues are.
Well, my employer privides an open WiFi for the office. The signal is not extremely strong but it's fair. Signal strength does dip up and down a little.
So while on 4.2, my phone stayed connected to the WiFi. Never disconnected. Once I upgraded to 4.3, it will not stay connected. It constantly drops the signal, scans, sees the signal but won't reconnect. I have to manually force it to connect.
As soon as I sit the phone down and it sleeps, it disconnects again and the process starts over.
The constant scanning is draining my battery fairly quickly.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Do you have insurance?
Sent from the 215
No. I purchased the phone used.
I'm not convinced its the phone. I'm have been reading today online that a lot of others are reporting the same issue.
Seems a lot of people are trying to find a way to downgrade to 4.2 because of the same issue.
Sent from my SCH-I545 using Tapatalk
Do you have you phone set to keep WiFi on during sleep? Also try unticking the WiFi battery optimization
Sent from my SCH-I545 using xda app-developers app
Can you tell me where the wifi battery optimization is? Not able to find d that option. I even googled it and can't figure it out. Lol
Sent from my SCH-I545 using Tapatalk
loco63 said:
Can you tell me where the wifi battery optimization is? Not able to find d that option. I even googled it and can't figure it out. Lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Settings>WiFi>Menu>Advanced settings
Sent from my SCH-I545 using xda app-developers app
I do not ha e that setting. I just read that its not present in 4.3.
Sent from my SCH-I545 using Tapatalk
Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?
Sent from my SM-N900P using Tapatalk
nacron said:
Been having issues with my sensors locking up. I'm running stock rooted with a few xposed mods. I tried turning off all the mods and I still got it intermittently. Thought it was the gear manager for my Galaxy gear. Stopped having the issues after uninstalling the gear manager but it came back. When the auto rotation stops working I check the sensors with *#0*# and it shows the accelerometer is locked and occasionally other sensors fail like barometer and magnetic. A few searches find other phones with this issue sometimes gets fixed with a reflash. Anyone else have this issue?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.
Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I just did a Google search of the topic, and I'm finding a full wipe and reinstall appear to be the agreed upon solution for many. I hate those types of answers, since doing it is a lot of work, and if it doesn't solve your issue, you have just wasted a ton of time for little benefit.
Have you tried uninstalling the Xposed modules and framework completely, rebooting, and wiping cache and dalvik partitions? That's the only other thing I can think of that could fully test your theory of it being an Xposed issue.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape
Sent from my SM-N900P using Tapatalk
nacron said:
Haven't tried removing xposed but I have done cache wipes and fix permissions with no result. Is there a file that's being corrupted somewhere? Had a similar issue on my Galaxy S (original) and wipe fixed that also but in that case it was directly after a game crashed in landscape
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).
I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.
Hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I have no idea as to whether the file is corrupted, as I'm not experiencing your issue. None of the items I read mentioned corrupted files and accelerometers. They did mention running script commands (ie, pinging the sensor to awaken it, but that's above my knowledge base).
I would recommend deleting all Xposed modules and framework if you want to properly test your theory. You can backup the settings on those and just reinstall the apps if it fixes it, and you are going to be reinstalling them anyway if you wipe data. It's the only option of which I can think.
Hope this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.
Sent from my SM-N900P using Tapatalk
nacron said:
Removed the framework and uninstalled exposed, still getting sensor lockups. If reflashing works after removing all these mods, there has to be a system file that's messing up right? I uninstalled lux also and disabled greenify. It was working fine up until a month ago.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Agreed, but I would speculate that the reason I found no answer beyond reflashing or pinging the sensors is that you could be searching for the proverbial needle in the haystack.
If wiping data and installing a new rom is the consensus solution, with no guarantee of success, then that is likely your only option.
It takes me hours to get a new rom up and running exactly the way I want, so I feel ya. At this point, I'm also out of answers.
If another can help, perhaps they can chime in.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware
Sent from my SM-N900P using Tapatalk
nacron said:
Uninstalled a bunch of stuff and now the sensors lock up within 10 min of boot. Barometer no longer registers any data. I'll thinking this GN3 has bad hardware
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
funny, after reading this thread, and seeing mic being stumped, i was wondering... do you have this issue on stock? old habit from my computer repair jobs which is rarely applicable to an android issue is "check HW first".
I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device
Sent from my SM-N900P using Tapatalk
nacron said:
I'm running stock rooted, didn't flash any roms on this, believe me, I'm using all my troubleshooting resources. It's frustrating when a simple thing can mess up an entire device
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
So do you have recovery or otherwise trip Knox? If no, reflash via Odin or Mobile Odin the full rom (see Skunk Ape1 thread), reinject root, then you'll know.
I'd go a step further and aver that, based on what you've written, one way or the other reflashing stock MJ4 is the direction this is headed.
Ya take the phone back, it's out-of-the-box clean, and you're likely going to want to do it anyway. Ya don't take the phone back in the hope you find a fix, you still might flash stock MJ4 to eliminate a potential fix. It doesn't work, your phone is that much closer to being brought back for a return.
Unless there is a more targeted solution, this is perhaps your best course of action.
Sent from my SM-N900P using Xparent BlueTapatalk 2
It seems more stable now. It's super weird, for almost all today the barometer read 0 and the other sensors world lock up about 10 min after boot. This was after removing all the mods and clearing cache and fixing permission. We'll see how stable it is tomorrow.
Sent from my SM-N900P using Tapatalk
So I realized WiFi is causing my Screen of Death issue on EVERY KitKat ROM, and only KitKat ROM's. So what is my next step? Does anyone have a fix on this or anything? It'll either Screen of Death my phone or my data won't work until I turn off WiFi and then I can't turn it back on. Any help would be appreciated guys. I'm desperate now. 15 battery pulls a day are just ridiculous.
Why did you make a new thread? :what:
Anyways...I'm in the same boat as you. Take a few screenshots of your app drawer so I can see if we are using any of the same apps, it's possible one of them are the problem.
Sent from my SCH-I545 using Tapatalk
Well OP isn't very active, so I thought I'd get a logcat. I was connected to WiFi until I noticed it wasn't receiving any data (but still showed connected to WiFi). I turned the screen off and then it would not come back on anymore, but the phone was still responsive. I could turn torch on and off and even took a screenshot, but the screen still refused to come on. I'm guessing that whatever is happening, usually does so while the screen is off, and that's why I get a BSOD.
I'd like to add I've tried a bunch of different modems, clean flashed CM11, even restored no apps...yet the problem persists.
I've attached it to this post, if anyone has time to check it out I would be very grateful.
thesoldier said:
Why did you make a new thread? :what:
Anyways...I'm in the same boat as you. Take a few screenshots of your app drawer so I can see if we are using any of the same apps, it's possible one of them are the problem.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I screenshot my drawer but don't have access to a computer till tomorrow. So I'll send em over. But yeah I just made a new thread because I wasnt getting any answers on the other when I discovered that WiFi was the issue.
I'm just so frustrated with my phone because I can not figure out a fix. At first I installed a clean kitkat ROM with full wipe, and didn't restore apps to see if it was an app but it still did it. Then I even completely unrooted my phone and rerooted, still did it.
Nwwolf1 said:
So I screenshot my drawer but don't have access to a computer till tomorrow. So I'll send em over. But yeah I just made a new thread because I wasnt getting any answers on the other when I discovered that WiFi was the issue.
I'm just so frustrated with my phone because I can not figure out a fix. At first I installed a clean kitkat ROM with full wipe, and didn't restore apps to see if it was an app but it still did it. Then I even completely unrooted my phone and rerooted, still did it.
Click to expand...
Click to collapse
That's alright, if it also did it for you without restoring any apps, its gotta be something else. But what... I have no idea.
It seems that WiFi is crashing while the screen is off and that is resulting in a BSOD. Why the hell is it crashing though... :banghead:
Sent from my SCH-I545 using Tapatalk
thesoldier said:
That's alright, if it also did it for you without restoring any apps, its gotta be something else. But what... I have no idea.
It seems that WiFi is crashing while the screen is off and that is resulting in a BSOD. Why the hell is it crashing though... :banghead:
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah. I'll notice my WiFi is no longer sending data so I'll turn it off then it won't turn on. Or I'll try to turn it off and it won't then I know that if I lock my screen it won't turn on without a battery pull.
I'm not sure where to go from here if nobody can decipher that logcat.
All I can think of is to back up my SD card and completely format the phone.. then see if it persists.
Sent from my SCH-I545 using Tapatalk
Has anyone come up with any solutions to the problem at all?
Nwwolf1 said:
Has anyone come up with any solutions to the problem at all?
Click to expand...
Click to collapse
I have yet to find a solution to this... It seems like nobody else has this issue.
Sent from my SCH-I545 using Tapatalk
So I just odined the stock MDK image, wiping everything. The only thing I copied back over was my pictures. Flashed back to KitKat and it STILL happens. WTF. This is beyond aggravating.
Sent from my SCH-I545 using Tapatalk
Okay I hate to speak too soon. But I MAY have found a temporary fix. I noticed that the screen only freezes and shuts off on the lock screen. Never any other time. So I turned off the android lock screen and put up widget locker instead (set up exactly the same way) so far it hasn't happened. Here's hoping I'm not jynxing myself though!
Never mind. I did speak to soon...ugh we need to find a fix for this and soon. Is it only on the vzw gs4?
Nwwolf1 said:
Never mind. I did speak to soon...ugh we need to find a fix for this and soon. Is it only on the vzw gs4?
Click to expand...
Click to collapse
I've googled and don't see any mention of WiFi causing a bsod.
I'm gonna test my next theory, not let Google restore anything from my Google account. That's the only other thing that is being restored.
Sent from my SCH-I545 using Tapatalk
Well I tried that....still happens. Officially out of ideas.
Sent from my SCH-I545 using Tapatalk
thesoldier said:
Well I tried that....still happens. Officially out of ideas.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I tried that a while back too. I've tried everything I could possible think of. I had to go back to CM10.2 because I just couldn't stand doing a battery pull 10 times a day, killing my battery.
Anyone have any luck with a fix yet?
Nwwolf1 said:
Yeah I tried that a while back too. I've tried everything I could possible think of. I had to go back to CM10.2 because I just couldn't stand doing a battery pull 10 times a day, killing my battery.
Anyone have any luck with a fix yet?
Click to expand...
Click to collapse
Have either of you tried flashing KToonsez kernel with whatever ROMs your on??? Worth a shot. I didn't see either of you mention kennel, you've Odin back to stock and still happens though huh? Maybe bad WiFi antennas idk
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Have either of you tried flashing KToonsez kernel with whatever ROMs your on??? Worth a shot. I didn't see either of you mention kennel, you've Odin back to stock and still happens though huh? Maybe bad WiFi antennas idk
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
That's what's confusing me so much. I know its WiFi but its only on kitkat ROMs. That means that the WiFi antennas must have changed on 4.4 right?
Nwwolf1 said:
That's what's confusing me so much. I know its WiFi but its only on kitkat ROMs. That means that the WiFi antennas must have changed on 4.4 right?
Click to expand...
Click to collapse
So if u have WiFi toggled off during the day you don't have this problem at all?? I'm not really sure myself if anything with wifi has changed in 4.4
How many different kit kat ROMs have you tried? And you said you're in the latest modem?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
So if u have WiFi toggled off during the day you don't have this problem at all?? I'm not really sure myself if anything with wifi has changed in 4.4
How many different kit kat ROMs have you tried? And you said you're in the latest modem?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, it never happens when Wifi is off. I've tried it on CM11, OmniRom, Jelly Beans, PA, Gummy Rom, and I think one other. And what is modem again?
Nwwolf1 said:
Yeah, it never happens when Wifi is off. I've tried it on CM11, OmniRom, Jelly Beans, PA, Gummy Rom, and I think one other. And what is modem again?
Click to expand...
Click to collapse
The modem (baseband) is something you can flash in recovery..
It controls the cells hardware that communicates with the actual cell towers.
That isn't going to mess with your WiFi though.. How about kernels have you tried another one maybe KToonsez ?
Sent from my SCH-I545 using Tapatalk
Hi.
So just recently I allowed the newest update to download on my phone....
and since then my Note 3 has been randomly freezing and rebooting, sometimes making odd noises when the screen is off...
Anyway, I just got this new Sony Vaio laptop with NFC beam on it and decided to try it with my phone. Now mind you, I have NFC turned ON on my phone and I know how to use the beam with both devices. Now, when I try to beam a picture or website to my phone from my laptop I get up to the point where my phone says to "now bring devices back together" but after I do that all I get is the little noise that basically indicates that the data is supposed to be transferred...but instead it keeps sporadically beeping. Does anyone have any idea how to solve this? I just recently did a complete factory reset, pulled the battery, restarted and everything. Nothing has worked.
Are you referring to the 4.4.2 update or has there been another?
Sent from my SM-N900P using Tapatalk
DevilDog512 said:
Are you referring to the 4.4.2 update or has there been another?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
4.4.2
I was late to update.
Hmm. I would try flashing one of the stock tars available in Odin. Make sure to remove your extsdcard and be aware it erases internal storage if you do. But sounds like you got a bad download. Or try with kies or something. The stock tars in Odin won't trip Knox.
Sent from my SM-N900P using Tapatalk
DevilDog512 said:
Hmm. I would try flashing one of the stock tars available in Odin. Make sure to remove your extsdcard and be aware it erases internal storage if you do. But sounds like you got a bad download. Or try with kies or something. The stock tars in Odin won't trip Knox.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
This is exactly right...start by going back to completely stock. That'll get him back to a very good place...
After that, we will see if that fixes the biggest problems described (ie, phone not working). He can down the line worry about the the file sharing issue
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
This is exactly right...start by going back to completely stock. That'll get him back to a very good place...
After that, we will see if that fixes the biggest problems described (ie, phone not working). He can down the line worry about the the file sharing issue
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Exactly. The whole phone making weird noises when screen is off would have been it for me. Lol. That can't be good.
Sent from my SM-N900P using Tapatalk