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
Related
Seems that recently the LEDs for the flash and what are also used for the flashlight are no longer operating on my husbands phone. I've tried wiping and reflashing JellyBlur v1.3 and trying various applications - but it seems that this doesn't help and that those LEDs just don't want to come on. Is there something that I can do to fix this or are they out for good?
I'm also running JellyBlur v1.3 on my phone and my flash/flashlight are working fine. While I'm waiting I'm going to try flashing another ROM to see if that solves the problem, but any tips or helpful posts are greatly appreciated. Thank You. :good:
Update It seems that switching ROMs didn't help it either. The flash still doesn't want to work nor does any flashlight application including stock. Not sure what happened, but hopefully someone can suggest a fix. (Could it be kernel or something similar related?)
- Tried reflashing JellyBlur v1.3 and Skyraider Zeus v1.3
Thundeshed is good and any Rom based off of it is too.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Thundeshed is good and any Rom based off of it is too.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Do you think flashing that might fix the flash issue? I've never encountered this problem before on our phones so it's new to me.
I would definitely make a backup of what you have now, do a good/clean wipe and install a nandroid backup from a different ROM in which the flash was working to see if the flash will work for you again.
If not, the flash may have just given up on you. =\
Note: Clear data 3x, cache once, and dalvik once. (I always recommend clearing data at least 3x because data doesn't always clear within the first or even second time around)
Sent from my ADR6400L using xda premium
RBarnett09 said:
I would definitely make a backup of what you have now, do a good/clean wipe and install a nandroid backup from a different ROM in which the flash was working to see if the flash will work for you again.
If not, the flash may have just given up on you. =\
Note: Clear data 3x, cache once, and dalvik once. (I always recommend clearing data at least 3x because data doesn't always clear within the first or even second time around)
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Yep, tried doing super wipe then cache/dalvik... doesn't work on any of the ROMs I have tried. I guess the flash just went out on his phone. *sad pandas*
I guess he will just have to do for now until I can buy him a new phone. :crying:
WalkerGFX said:
Yep, tried doing super wipe then cache/dalvik... doesn't work on any of the ROMs I have tried. I guess the flash just went out on his phone. *sad pandas*
I guess he will just have to do for now until I can buy him a new phone. :crying:
Click to expand...
Click to collapse
Yeah, that sucks!
I know you can buy the replacement parts for the flash, but you can't find directions on how to repair it anywhere.
Sent from my ADR6400L using xda premium
I think it would be a difficult repair and some soldering would definitely be necessary.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I think it would be a difficult repair and some soldering would definitely be necessary.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I would imagine the same thing.
Just a big pain.
Sent from my ADR6400L using xda premium
I would suggest a warranty replacement if you have the option.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I would suggest a warranty replacement if you have the option.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Good news. I was able to put ICS (Liquid Desensed36) and applied the new combo radio someone developed.
Using the Wi-Fi w/ root from play store using generic ics/jb (wlan0), channel 2, password protected, with router fix was able to fix his Wi-Fi tether.
Also the ICS Liquid Desenesed36 fixed his Flash and flashlight! (Don't know how; I don't question it) :good::good::good::good::good:
There is people having problems with getting the gps to ping in. After flashing a rom. Well here is a fix for everyone having problems. .
Steps to take
1.Reboot into recovery
2.Backup everything up
3.Reboot into recovery
4.WIPE CACHE & DALVIK CACHE
5. FACTORY RESET
6. WIPE DATA
7. WIPE THE INTERNAL SD CARD
8.Flash your favorite rom
9. Reboot system
10. Once you have your phone up and running. Go outside and run your gps.
Or you can just use file manager. And delete the Android file in internal sd card. Restart your phone. Then follow step 10. All should work. .
Sent from my SCH-I605 using Xparent BlueTapatalk 2
Yeah, I don't know. Also, kind of redundant - as factory reset covers everything but wiping internal sdcard.
I can get GPS to run on each and every ROM I run and I've never followed these steps. Download GPS Status from market first. Turn on wifi and GPS - then open Maps. Then open GPS Status. It will say 'Maps updated to latest version'. Type in an address and start navigation. Place in window sill until it locks. Once it locks once - you're good.
Everytime.
Sent from my SCH-I605 using Tapatalk 2
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
Also - I don't think this has any place in development.
Sent from my SCH-I605 using Tapatalk 2
This guide is more of a General fit as no development was required
Moved to General
Thanks
FNM
kennyglass123 said:
This guide is more of a General fit as no development was required
Moved to General
Thanks
FNM
Click to expand...
Click to collapse
Thanks man. Half tired when posting this.
Sent from my SCH-I605 using Xparent BlueTapatalk 2
1ManWolfePack said:
Yeah, I don't know. Also, kind of redundant - as factory reset covers everything but wiping internal sdcard.
I can get GPS to run on each and every ROM I run and I've never followed these steps. Download GPS Status from market first. Turn on wifi and GPS - then open Maps. Then open GPS Status. It will say 'Maps updated to latest version'. Type in an address and start navigation. Place in window sill until it locks. Once it locks once - you're good.
Everytime.
Sent from my SCH-I605 using Tapatalk 2
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
Also - I don't think this has any place in development.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I've never had gps problems ever till I flashed novella rom. I haven't had a gps lock on it yet, but I haven't needed it and I really like this rom, but I'll try your idea first because the first one will take a while.
Sent from my SAMSUNG-SGH-I317 using xda premium
I read somewhere in the Novella thread that if you flash another rom that has working gps, run the GPS Fix app, once it fixes gps, back up that app and restore the rom with broken gps. Then restore GPS Fix app, run it.
I just did this and it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
A few months back I had working GPS on ParanoidAndroid. I let my brother use this phone for a while, and now I'm back. He used a flash of CleanROM while he had it.
As soon as I got this phone back, I flashed to the newest CM nightly. Everything seemed to work fine until I noticed a problem with GPS yesterday.
I'm trying to troubleshoot the problem today. I've flashed VRALJB (after wiping system/data/internal sd) and have done nothing but log in to the App Store and download GPS Test. I usually have no problem getting a fix at my desk indoors, but I've walked outside with this thing too. I see 28 satellites in view, but it's stuck at 0 in use. No matter what I do, it says "In Use 0". This is driving me bonkers.
Edit: Going to try sitting it on the windowsill with nav running. Will report back.
Edit2: Nothing is working. On an old version of beans, only because I know it used to work. Currently 19 in view, 0 in use. Going to give up until I go for a drive or something.
chrisjz said:
I read somewhere in the Novella thread that if you flash another rom that has working gps, run the GPS Fix app, once it fixes gps, back up that app and restore the rom with broken gps. Then restore GPS Fix app, run it.
I just did this and it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I think it's really just getting the lock then immediately flashing new ROM. That worked on s3, razr, lg spectrum and my note. One if the spec devs figured out why it worked, but I can't recall anymore. It was some command it called when working that the bad ROM wasn't and for some reason when it was active it would last through a flash.
Sent from my SGH-T889 using xda app-developers app
Usually deleting and resetting the gps files through the app "gps status" (found in the playstore) works for me within 20-60 seconds, but in my worst case scenario(so far) I did have to reflash scott's verizon patch[newest radios] and THEN run the app, but other than that I think ive been pretty lucky. Never had to reflash any rom to regain gps lock...
I flash ALOT... and also yes.
Desperation bump. Walked all around this morning with GPS Status running. This is the best I get: http://i.imgur.com/brE5B2P.png
illogic6 said:
Desperation bump. Walked all around this morning with GPS Status running. This is the best I get: http://i.imgur.com/brE5B2P.png
Click to expand...
Click to collapse
Have you tried any of the ideas listed above?
Sent from my SAMSUNG-SGH-I317 using xda premium
Yes, definitely. More than one time. I'm on the newest radios if that makes any difference. Starting to wonder if the gps hardware has gone bad.
When I'm wiping, I'm flashing to a rooted/deodexed VRALJB. Can't get a lock on that or on CM.
illogic6 said:
Yes, definitely. More than one time. I'm on the newest radios if that makes any difference. Starting to wonder if the gps hardware has gone bad.
When I'm wiping, I'm flashing to a rooted/deodexed VRALJB. Can't get a lock on that or on CM.
Click to expand...
Click to collapse
Format your internal sd card from your computer. If you know how to. Then pull battery and then restart your phone. Then try to ping the gps. Backup your pics or anything else you dont want to lose. You wont brink your phone by doing this.. its just wiping all the bull crap that built up..
Sent from my SCH-I605 using Xparent BlueTapatalk 2
ezgoing2406 said:
Format your internal sd card from your computer. If you know how to. Then pull battery and then restart your phone. Then try to ping the gps. Backup your pics or anything else you dont want to lose. You wont brink your phone by doing this.. its just wiping all the bull crap that built up..
Sent from my SCH-I605 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
This is what I do:
1) Reboot recovery
2) Wipe cache, dalvik, data
3) Delete everything in /sdcard/
4) Install VRALJB
5) Reboot system
6) Skip setup wizard and go straight to Maps... nothing
7) Sign in to Play store and download GPS Status... nothing
8) Update AGPS data... nothing
9) Toggling off/on Verizon location service.... nothing either way
Back when I used to be able to get a fix with this phone, I would have vertical bars underneath where it says "In View" and "In Use". I'd see them bouncing up and down even before I truly had a fix. I get absolutely nothing now. No movement at all. Indoors, outdoors... I took it for a walk with me today and got nothing. :crying:
Edit: Screw it. I was hoping I wouldn't have to, but I'm going to Odin and re-jailbreak. Will report back.
Edit2: I ran Odin, jailbroke and restored a backup. No difference. Maybe I shouldn't have restored the backup. Sigh...
So even a stock rom won't give you a gps lock? What about before you unlocked/rooted again? Have you tried to go completely back to stock, then a gps lock? If that doesn't work. Give Verizon a call for a replacement.
Sent from my SAMSUNG-SGH-I317 using xda premium
chrisjz said:
So even a stock rom won't give you a gps lock? What about before you unlocked/rooted again? Have you tried to go completely back to stock, then a gps lock? If that doesn't work. Give Verizon a call for a replacement.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah... I just Odin'd again and decided to test before I jailbroke/rooted/anything. No GPS at all on stock VRALJB. Looks like I'll be doing an insurance replacement here in the near future. Don't know what else I can do.
I had to go back to stock, but it worked. I got a GPS. Then I rooted and stopped there. Five minutes later I busted the screen, so I will report with my new phone tomorrow.
Sent from my SCH-I605 using xda premium
Got my replacement today. Whaddya know!? http://i.imgur.com/cvwrQAu.png
illogic6 said:
Got my replacement today. Whaddya know!? http://i.imgur.com/cvwrQAu.png
Click to expand...
Click to collapse
Cool
Sent from my SCH-I605 using Xparent BlueTapatalk 2
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
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
So I've had this problem for as long as I've had the phone. But I never needed to get it resolved until I started hardcore gaming on my phone. My cpu frequency reverts back to either 1.7ghz or lower whenever I startup and play a game. I've tried, (full restore/unroot/start from scratch, new roms, different kernels, deleting the post.boot system file, daemon file mod found in seperate fourm, changing cpu voltage, use the force.) Nothing works. It only seems to happen when I start up a game. The game gets super laggy. I'm currently running x-note rom with beast mode rage kernel. Bear in mind ive tried about every kernel available asside from the old mj4 kernel/rom. Anybody able to help or even point me in the direction of someone who might would be hugely appreciated. Thanks so much,
Matthew Cooksey
mscooksey21 said:
So I've had this problem for as long as I've had the phone. But I never needed to get it resolved until I started hardcore gaming on my phone. My cpu frequency reverts back to either 1.7ghz or lower whenever I startup and play a game. I've tried, (full restore/unroot/start from scratch, new roms, different kernels, deleting the post.boot system file, daemon file mod found in seperate fourm, changing cpu voltage, use the force.) Nothing works. It only seems to happen when I start up a game. The game gets super laggy. I'm currently running x-note rom with beast mode rage kernel. Bear in mind ive tried about every kernel available asside from the old mj4 kernel/rom. Anybody able to help or even point me in the direction of someone who might would be hugely appreciated. Thanks so much,
Matthew Cooksey
Click to expand...
Click to collapse
Go into power savings mode, and make sure that your CPU power saving option is deselected.
I'm nearly certain that is the culprit.
Sent from my SM-N900P using Tapatalk
micmars said:
Go into power savings mode, and make sure that your CPU power saving option is deselected.
I'm nearly certain that is the culprit.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No such luck. Any other ideas?
mscooksey21 said:
No such luck. Any other ideas?
Click to expand...
Click to collapse
If you're on TouchWiz KitKat, MJ4 is a non-starter.
If power saving mode/adjust CPU isn't throttling your upper end, then an app must be setting it at boot.
The power saving mode, CPU option sets the upper end at 1.7 Ghz.
An app may be doing the exact same thing, taking control above all other settings for your device.
Sent from my SM-N900P using Tapatalk
micmars said:
If you're on TouchWiz KitKat, MJ4 is a non-starter.
If power saving mode/adjust CPU isn't throttling your upper end, then an app must be setting it at boot.
The power saving mode, CPU option sets the upper end at 1.7 Ghz.
An app may be doing the exact same thing, taking control above all other settings for your device.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Thats kinda what I imagined also. But I have no idea how to isolate it. I only hace one oc app on my phone. No performance tab in settings. And bear in mind ive already gone back and started from square one multiple times.
mscooksey21 said:
Thats kinda what I imagined also. But I have no idea how to isolate it. I only hace one oc app on my phone. No performance tab in settings. And bear in mind ive already gone back and started from square one multiple times.
Click to expand...
Click to collapse
There's got to be something writing the upper end voltage on boot.
You may have to go completely back to square one.
Sent from my SM-N900P using Tapatalk
micmars said:
There's got to be something writing the upper end voltage on boot.
You may have to go completely back to square one.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Yeah. But I've already tried a full unroot, complete factory reset.
mscooksey21 said:
Yeah. But I've already tried a full unroot, complete factory reset.
Click to expand...
Click to collapse
In not a huge fan of wiping one's internal memory, but it seems the next logical course of action.
Either that, or factory reset first, then flash stock NC5 until you get official status, then and only then flash recovery and root.
No need for auto root package.
Sent from my SM-N900P using Tapatalk
micmars said:
In not a huge fan of wiping one's internal memory, but it seems the next logical course of action.
Either that, or factory reset first, then flash stock NC5 until you get official status, then and only then flash recovery and root.
No need for auto root package.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Okay. Could I factory reset then flash nc5 full restore via odin found in other post? Then how can I tell if its got official status?
mscooksey21 said:
Okay. Could I factory reset then flash nc5 full restore via odin found in other post? Then how can I tell if its got official status?
Click to expand...
Click to collapse
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Got it. Will report back soon.
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Okay so here's the update. I did a full un root return to stock, wiped data, and re rooted/ installed a game and it happened again. Frequencies reverted back to an even lower 1.4ghz almost instantly. I'm at a loss. It only happens when I start up a game. And I know it didn't do this at one point but I don't remember what was different or what i changed from back then.
mscooksey21 said:
Got it. Will report back soon.
Click to expand...
Click to collapse
Any ideas brotha?
micmars said:
You'll know it's official status by going into about phone from settings, general tab.
When that sticks, it'll no longer read "custom."
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Any ideas brotha?
mscooksey21 said:
Okay so here's the update. I did a full un root return to stock, wiped data, and re rooted/ installed a game and it happened again. Frequencies reverted back to an even lower 1.4ghz almost instantly. I'm at a loss. It only happens when I start up a game. And I know it didn't do this at one point but I don't remember what was different or what i changed from back then.
Click to expand...
Click to collapse
That game is messing with your phone. I suggest going completely Stockish DeOdex NC5, adding Beast kernel, SetCPU, and try over clocking your device.
No games.
Sent from my SM-N900P using Tapatalk
micmars said:
That game is messing with your phone. I suggest going completely Stockish DeOdex NC5, adding Beast kernel, SetCPU, and try over clocking your device.
No games.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
It does it for any game I play. gta, mc4, mc5,rr3,etc..
mscooksey21 said:
It does it for any game I play. gta, mc4, mc5,rr3,etc..
Click to expand...
Click to collapse
I'm not knowledgeable about games and your inability to overclock your device.
I am quite clear on the process of elimination and gauging your ability to accomplish a task and rule out the root cause.
For now, stock, rooted, DeOdex rom, simple overclocking app, and kernel capable of doing same.
My suggestion stands.
No games, tell us if you're able to overclock your CPU at all.
Sent from my SM-N900P using Tapatalk
micmars said:
I'm not knowledgeable about games and your inability to overclock your device.
I am quite clear on the process of elimination and gauging your ability to accomplish a task and rule out the root cause.
For now, stock, rooted, DeOdex rom, simple overclocking app, and kernel capable of doing same.
My suggestion stands.
No games, tell us if you're able to overclock your CPU at all.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Will do. Thank you kindly.
When I had the "touchwiz dvfs" enabled none of my oc settings would stick. Just a thought if you could disable that maybe it'll help. There's an xposed module that allows for it.
Sent from my SM-N900P using xda premium