Temp Root w/ Bluetooth Issues? - Verizon Droid Incredible 2

Hey all,
Curious if we anyone had seen this issue before. It seems like while my phone is temp rooted it will not connect to anything via bluetooth. It just hangs at the "connecting" phase. It will pair just fine, but not connect. Rebooting the phone and undoing the root allows it to work just fine, but if I temp root it again the same thing happens. Seemed odd, but it is repeatable on my phone and my wifes (both VZW Inc 2s).
-Eric

Currently the temp-root exploit is known to make other parts fail.
This is quite normal since this should only be used to aquire perm-root. But since there is no possibility go perm-root you can go with the temp-root that will make some things failing. It's anoying I know, but that's all we got right now.
Short info about exploits: they are made for letting the system to do things it is not suposed to do. This generally mean that programs uses parts of the memory it doesn't own, this is why other programs can fail.

So if I reboot it should work fine again?
Sent from my ADR6350 using XDA App

Yeap, should fix it

Still has issues....

belongs in General. inc 2 dev forum is saturated with Q&A threads X_X

Moved to proper forum.

Related

Post Root Issues

After painfully occupying my entire weekend getting my Incredible Rooted, the ONLY thing I did was add the WiFi Tether. That was my sole purpose in Rooting.
I did not remove anything. I did not change anything. ONLY loaded the WiFi tether.
Now, I have issues with my phone randomly rebooting.
My phone will show signal but fail to place or receive calls. "Call Failed"
Sometimes when a call comes in, the other side can hear me but I cannot hear them.
My internet connection is sketchy now, facebook photo uploads show success but are blank (red X box) when I or anyone tries to view them.
The Kingston 8GB MicroSD card I originally had in was blown an hour after rooting rendering it not even recognizable in any system (losing a ton of data which is fortunately backed up). Thank goodness for their lifetime warranty.
Finally, I have had to reboot the phone several times due to lock ups.
I did not have a single one of these issues before. WiFi Tether is handy but not worth it if this is the result.
Anyone else having issues Post-Root?
compnird said:
I did not have a single one of these issues before. WiFi Tether is handy but not worth it if this is the result.
Anyone else having issues Post-Root?
Click to expand...
Click to collapse
I have had a couple of slow downs and random reboots, but I chalked it up to setCPU and the fact that I have 200 applications installed, some of them old, with about 25 resident processes.
However, the phone is still 10x more reliable than my G1 was with the most reliable modded firmware and fewer programs. When I cross the bone stock/modded line, I know I'm on my own and stability losses aren't my biggest concerns.
Long story short, I have no answers for you, but without scrutinizing the su, busybox, symlink commands for sources of instability, I would venture that Wireless Tether is a prerelease, and earlier versions of it caused my G1 problems too!
rynosaur said:
I have had a couple of slow downs and random reboots, but I chalked it up to setCPU and the fact that I have 200 applications installed, some of them old, with about 25 resident processes.
However, the phone is still 10x more reliable than my G1 was with the most reliable modded firmware and fewer programs. When I cross the bone stock/modded line, I know I'm on my own and stability losses aren't my biggest concerns.
Long story short, I have no answers for you, but without scrutinizing the su, busybox, symlink commands for sources of instability, I would venture that Wireless Tether is a prerelease, and earlier versions of it caused my G1 problems too!
Click to expand...
Click to collapse
Thanks, I may just end up removing it to see if it resolves my issues. Most have to do with my wireless radio so that makes sense. I didn't correlate the application to the hardware-like issues so I'll be mindful of that now.
Thanks for your 2 cents, it has earned interest.
i have noticed that my ringtone skips. when i listen to it in the settings, it sounds fine. but when someone calls, it sounds awful!!!!
Only issue I am having is with wifi, I have to manually go into settings and scan, after that it works fine.
Sent from my ADR6300 using Tapatalk
I've had some black screens and phone freezes since root. I do have wi-fi tether and root explorer loaded.... but haven't used wi-fi tether
I've had 0 problems - dunno what you guys did wrong. I added superuser, wifi tethering, shootme, titanium backup, and lamppu, and like I said I haven't had a single problem.
I'm good...Haven't had any problems after root.....Except for the fact I can't get it back to recovery mode to make some more changes!!
I have not had Any issues after root. I installed WiFi tether and its working great, but I didn't change anything else. No slow downs, random restart, lockups, or anything of that nature. No negative impact at all. Did I just get lucky??
-------------------------------------
not sent from an iPhone
Also having issues here. My exchange email will no longer sync. Tried to recreate and always get 'failed to create account'. Had to switch to touchdown to get my mail... *shudder*
Had a few random reboots, but they were only when I was using root apps.
Sent from my ADR6300 using Tapatalk
I was having rebooting and freezing up issues before root. Replaced the Sense launcher with Helix 2 and problems disappeared.
Been rooted for several days now with fairly heavy usage, and the phone has been VERY stable...
No new issues for me
Has always rebooted randomly about once a week but no worse, and use wifitether almost constantly.
ilinfinityil said:
I've had 0 problems - dunno what you guys did wrong. I added superuser, wifi tethering, shootme, titanium backup, and lamppu, and like I said I haven't had a single problem.
Click to expand...
Click to collapse
same here. no problems at all.
no problems here at all
if you want to know why it is rebooting, run logcat and wait for it to reboot. You will see what actually crashed in the log. If you don't want to troubleshoot then just use the ruu to put your phone back to stock. It will erase everything and you will have to root again, but it will fix your phone.
I had a random reboot this morning...dont really attribute it to root though because phone would occassionally do this anyways when signal is shaky. If it persists, I will check logcat and see whats the dealio. Other than that, so far loving having root with no problems, ready for the custom ROMS.
Oh I tried the Stericson busybox installer and get failed message. Installed upgraded busybox through titanium backup.
Suggestion
Not that anyone would really read down this far BUT if you are experiencing problems can you also please make sure to include ONE thing in your post:
DID YOU REMOVE ANYTHING?
I am guessing from the thread that people who didn't remove things aren't experiencing problems.
I haven't had any of the problems you've experienced let alone even heard of other people experiencing this. I'm almost certain you messed something up during the root process. Re-root the phone by following the 10 minute instruction video posted here on how to root and everything should be fine.
dnchattan said:
Also having issues here. My exchange email will no longer sync. Tried to recreate and always get 'failed to create account'. Had to switch to touchdown to get my mail... *shudder*
Had a few random reboots, but they were only when I was using root apps.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I started having this issue a few weeks ago but mine isnt realted to root. I wish HTC could figure out how to fix it.
CDODGE said:
I started having this issue a few weeks ago but mine isnt realted to root. I wish HTC could figure out how to fix it.
Click to expand...
Click to collapse
Wonder how many would run that OTA right away...

[Q] Random Reboots

I'm curious if others are seeing their EVO reboot with random use. It doesn't seem to be related to one specific application although it is hard to say if a background app is the cause. I will be using navigation or an Internet-based app, then the screen goes black and the phone reboots.
I originally thought it was due to rooting, but I'm seeing it on different ROMs. I've wiped the cache and data when flashing the new ROMs and I've tried running with limited apps loaded with my recent move to the OMJ ROM. Everything actually runs great with the exception of the reboots.
I'm posting the issue here since it doesn't seem to be ROM specific and I'm curious if it may be hardware related. Is there a tool that would allow me to easily catch a log of the potential error to seek further help? A point in the right direction would be greatly appreciated.
I'm running stock 2.2 no root, and with gps on my phone reboots in the middle of 911 calls. (Thank God I wasn't calling about an immediate emergency) but it happened twice, once when I called and the other when they called me back. After turning off GPS, it worked fine. I thought this was a bug in 2.1 before update1, I didn't receive the problem until the 2.2 update.
adb logcat might see an error, but I'm not really sure.
Seeing it here. Not Rom or application specific.
try a factory reset.
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
AzmatEQ said:
That's scary news about the reboots during 911 calls. I can't say that I tested that as a trigger for the reboot and I hope I don't have to in the near future. However, it makes me curious if it is related to the phone's interaction with the Sprint network. In your case your 911 call may have been a direct trigger whereas my reboots are seem indirect while I'm using my data plan.
One reason for my reboot was due to me getting the Error Code 67 "Your PCS Vision username and/or password may be incorrect" when trying to tether (USB or hotspot). Rooting allowed me to tether using 3rd party apps, but there may be the underlying problem with my account.
I also should have mentioned that the reboots happen with GPS on as well as off. I typically have it off to save battery life. I've also done factory resets each time I've changed or updated my ROM.
Thanks for the feedback and suggestions so far. I'll try logcat and continue to monitor the forum for advice. I'll also post back any answers I may find elsewhere.
Thanks again.
Click to expand...
Click to collapse
Correction... I meant to say that the reason I rooted (not rebooted) was to get tethering without running into the Error Code 67. I tried the various solutions posted for the Error Code 67, but nothing seemed to work. But I'm curious if this may be part of the underlying issue if my device reboots based on a faulty account configuration when using some aspect of the Sprint network.
sprink0281 said:
I had a reboot tonite, phone was just sitting on table off charger about 90% battery, and I heard the Sprint screen come on looked down and noticed phone was booting up....no idea why first time I've noticed this.
Stock froyo no root...unfortunately :'(
Click to expand...
Click to collapse
The exact same thing happened to me last night. I sent a text, switched to my GMail and then boom. Error message about failure to send an SMS then reboot. Stock unrooted FroYo.
I had reboots only when using Undervolted kernels.
Seemed to be triggered by GPS + Phone call.
Yes, I was also having this problem. Definitely GPS related. Usually it would happen only if I was using the GPS for a long amount of time (navigating) - so I imagine it may be conflicting with cellular data if I received a txt while navigating or something. Who knows.
It was driving me crazy because A. I got lost and B. It started rebooting constantly and would randomly get caught in a boot-loop. I even had the problem after wiping EVERYTHING (even my SD) and reinstalling various ROMs (I tried 5 different ones).
The only solution I found in the end was to find the latest radio and wimax updates, wipe, re-install those - and then install the ROM again.
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
AzmatEQ said:
GPS may be a symptom, but not a cause for me since I typically have GPS off. I find that it typically happens when I'm using a networked based app, like the web browser. Following your post I turned on the GPS, started the navigation app and found that my EVO rebooted after the same amount of time I was experiencing with GPS off.
The more I think about it, it does feel like I just assume that it will reboot after a certain amount of time passes (regardless of app). GPS and Internet are two uses where I will have the screen on for more than just checking email and etc.
Your reply gave me hope and I wiped, reset and reinstalled today. All seemed well and then... auto-reboot. This is driving me nuts. I'm seriously considering reverting back to stock to see if that stops it.
Click to expand...
Click to collapse
Don't go back to stock. I did and it did not fix the rebooting problem. Now I have the rebooting problem and don't have root anymore. Out of the frying can and into the fire.
What's funny is that my phone went through a few days where it would randomly reboot, and this was before I rooted. When it rebooted for the second time in a meeting, I pulled the battery, and didn't put it back in until the meeting was over a few hours later. Don't know if that did anything, but it hasn't rebooted on its own since.
Sent from my blah blah blah blah
Having same issue and my theory is that its sd card related in my case at least... I think it might have to do with froyo netarchy based kernals found in most of the newer froyo roms combined with a slow sd card. (on hardware rev 2)... try flashing a 2.1 rom like fresh 1 or one of the 2.2 roms with an htc based kernal like the am evolution or cyanogen with snap5 or 7.11 (onyl 7based kernal ive tried so far, was panicking because i thought my evo was wrecked). those have both worked for me and i had that issue with 1.3 baked snack, fresh 3, evio and damage control. got random reboots when phone is totally idle, in use, charging or not. evio runs super smooth but the restarts...)
edit for spelling and update roms that gave me the reboot issue.
+1 for random reboots here... it is CERTAINLY more prevalent during GPS use, but I've gotten it without.
Fresh 3 + King BFS#4 got me in a bootloop requiring wipe reflash, standard baked snack 1.5+whatever kernel it comes with has been doing it.
I dig the battery life I was getting... but if undervolting is causing this... ugh.
I'm also getting the boot loop problem. Stock 2.2, all updates.
I've even done the hard reset.. twice!
I tried to follow it with LogCat, but reboot disconnects adb. I was thinking it was the SprintZone app. The P.O.S. app is doing all sorts of non-sense while booting, but eventually it'll reboot around the 11th time and freeze at the "htc EVO 4G" screen.
I wish we could get some resolve here D;
Random Reboots
Thanks for all the input and I'm sorry to hear that I'm not alone, but it is a bit comforting to know I'm not the only one that is frustrated.
I took gleax's advice and I dropped down to the stock 2.1 release found in the thread number 715915. (Sorry, the forum won't let me paste the link.)
I did the required wipes prior to installing the new ROM and I'm still seeing reboots. I now see the OTA update for Android 2.2 and I'm tempted to accept, then send the phone back to Sprint in the even this is a hardware issue. I'd prefer not to, but there doesn't seem to be a way to identify the issue and work towards a resolution. I've tried logcat, but the log seems to start clean after each reboot. That being the case, I don't know how to capture the log leading up to the reboot that would help identify the issue. Any suggestions on a logging tool and where to post to help several of us that are seeing this issue?
Gleax suggested this is may be SD related, so I bought a class 4 card in addition to dropping down to 2.1. I'll give that a shot and try another clean 2.1 install. I'll post the results here in the event they may help others. I'll likely give it a week before unrooting and seeking help from Sprint. I really need a usable device more than I need root access (although both would be ideal).
I had this problem on a very regular basis when I was running OTA 1.32, 2.1 android.. but since I rooted and went to SteelH's stock 2.2, no issues at all. Updated radios when I did that as well.
Hrm, I may have to try flashing to a stock build for awhile... it'll KILL me, but even fully wiping, new radios, cyanogen, still get crazy reboots.

[Q] Call Disconnected - Any Advice?

I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?

[Q] GPS Not Connecting...

I am on my 3rd GS3. The issue I am having is that my Navigation programs (default and telenav) will search and search for satellites, but won't connect. But when I restart my phone, it will work fine for a day or two then back to no connection.
I have spoken to Sprint and this is an unreported problem... until me. So, Sprint will replace my device. I am unrooted and completely stock. I know that Sprint is in Nashville, TN working on installing the 4gLTE towers. It isn't live yet, but they will turn on and off periodically.
I have searched these threads and I have not heard of any others with this issue. My first GS3 was rooted, but I have not done the two replacements. This has only occurred on an unrooted device.
Has anyone heard of this issue and know a resolution? I am considering rooting again to see if that is a fix. This is not a horrible issue, it is much better than a device that won't boot, but any help is greatly appreciated.
Bdozier said:
I am on my 3rd GS3. The issue I am having is that my Navigation programs (default and telenav) will search and search for satellites, but won't connect. But when I restart my phone, it will work fine for a day or two then back to no connection.
I have spoken to Sprint and this is an unreported problem... until me. So, Sprint will replace my device. I am unrooted and completely stock. I know that Sprint is in Nashville, TN working on installing the 4gLTE towers. It isn't live yet, but they will turn on and off periodically.
I have searched these threads and I have not heard of any others with this issue. My first GS3 was rooted, but I have not done the two replacements. This has only occurred on an unrooted device.
Has anyone heard of this issue and know a resolution? I am considering rooting again to see if that is a fix. This is not a horrible issue, it is much better than a device that won't boot, but any help is greatly appreciated.
Click to expand...
Click to collapse
Currently Rooted running the people's rom (3.06) GPS works flawlessly. I have tested and used Scout (By Telenav) Telenav, and Google Maps with no issues at all (tested in FL, MS, And parts of AL during my drive there and back) Haven't had any issues tho.
Mine worked fine while unrooted but started not initializing for startup apps that needed it after i rooted it. I would have to go to the app directly for it to start the GPS. Otherwise the app would continuously look for location. Unfortunately I haven't been able to narrow it down to any one Rom or kernel. Any one else with this issue?
Sent from my SPH-L710 using XDA Premium HD app
I have the same issue but haven't been able to figure out the cause either. Notice it mostly when I set my destination from my house, and wifi connected, then change location after leaving, and phone has kicked over to 3G.
Sent from my SPH-L710 using xda app-developers app
Before I returned my phone for another replacement, I decided to delete all of the apps that I had downloaded. I then rebooted my phone. After 2 days, it worked fine. I then began installing apps one by one. I figured the problem had to be app specific and only apps that use gps. There was one of two apps I decided was the culprit: Facebook or JuiceDefender. I installed Facebook and it worked fine for 2 days. Ample time for the issue to appear. I have figured out that all along JuiceDefender is the problem. It is shutting off GPS like it is supposed to, but not turning it on when it is supposed to. The problem started when I reverted to stock and took the OTA Android update. I am just embarrassed that it took until now to look at the apps as the problem and not the phone. I am going to contact JD and let them know what I have found. I hope there can be a fix, JD really works well... except for my gps!
Anyways, look at apps first as the problem child before running to a repair shop (like I did!) .
Hope this helps others...
Bdozier said:
Before I returned my phone for another replacement, I decided to delete all of the apps that I had downloaded. I then rebooted my phone. After 2 days, it worked fine. I then began installing apps one by one. I figured the problem had to be app specific and only apps that use gps. There was one of two apps I decided was the culprit: Facebook or JuiceDefender. I installed Facebook and it worked fine for 2 days. Ample time for the issue to appear. I have figured out that all along JuiceDefender is the problem. It is shutting off GPS like it is supposed to, but not turning it on when it is supposed to. The problem started when I reverted to stock and took the OTA Android update. I am just embarrassed that it took until now to look at the apps as the problem and not the phone. I am going to contact JD and let them know what I have found. I hope there can be a fix, JD really works well... except for my gps!
Anyways, look at apps first as the problem child before running to a repair shop (like I did!) .
Hope this helps others...
Click to expand...
Click to collapse
JD is designed to disable data connection to conserve battery, You can set it for a threshold where it will keep the connection alive if it's transmitting information back and forth.. (Must have Ultimate for that i believe) So if your disabling the data connection, then it'll kill GPS.
It is set on balanced. That is why I didn't think of juice defender first. Never had this issue until android updated.
Sent from my GT-P5113 using xda app-developers app
I am having the same problem. My GPS will work, but for me, it's only for about 15 mins or so (while in an App that starts it). Then, if I stay in the app, it will just lose connection. If I exit the App, and the GPS turns off, then when I go back it, it will not turn on again. It isn't like it is searching and it doesn't get a signal...it never turns on. The only thing to bring it back is to reboot. I noticed it while on a custom ROM (TPR) and thought it must be that, so I flashed back to stock. Still the same thing. I then tried doing a factory reset. Still not working properly. Anyone have any other ideas?
Thanks in advance.
same here
hotwired34 said:
I am having the same problem. My GPS will work, but for me, it's only for about 15 mins or so (while in an App that starts it). Then, if I stay in the app, it will just lose connection. If I exit the App, and the GPS turns off, then when I go back it, it will not turn on again. It isn't like it is searching and it doesn't get a signal...it never turns on. The only thing to bring it back is to reboot. I noticed it while on a custom ROM (TPR) and thought it must be that, so I flashed back to stock. Still the same thing. I then tried doing a factory reset. Still not working properly. Anyone have any other ideas?
Thanks in advance.
Click to expand...
Click to collapse
I took it in to Sprint they said it was the bad antenna and will give me a refurbish phone. This phone is less than a month old and why I will take a refurbish phone. Like I bought a brand new car and come in for a fix and they took me to the use car lot for a factory certificated car.
So I sent to Samsung and they claimed replacing a part and got the phone back, same problem is still happening.
Anyone can help us on this. It seems a common issue to a few of us.
Here is a simple GPS fix that works well.
http://forum.xda-developers.com/showthread.php?t=2201668

Nexus 5X hotspot not working

I've tried searching google for a solution, but to no avail.
Generally when you search for the title of this thread, you come across plenty of solved problems where devices could connect to the hotspot but not connect to the internet.
My issue is different. Devices cannot even connect to the hotspot, attempting to but eventually failing. I own a brand new Nexus 5X. My brother also has a Nexus 5X and they can all connect to his hotspot. I've tried switching SIM cards and rebooting but no device can connect to my hotspot. It is not a carrier issue as both sims work in my brother's identical phone.
I am really hoping it is a software issue. I want to avoid flashing all stock software (using flash-all.bat) and want to know what I could flash to fix my hotspot.
The phone can make calls and connect to the internet, no trouble. The internet does not drop out when I attempt to turn the hotspot on. However, sometimes the hotspot will attempt to turn on, fail and attempt again. It will loop like that until reboot if that happens.
Modifications:
My brother's phone is stock and the bootloader has never even been unlocked.
My phone has the following modifications:
Unlocked Bootloader
TWRP Recovery
Cataclysm ROM (the latest one, Android 6.0.1, build number mmb29p)
Ultimate Performance (link: http://forum.xda-developers.com/and...od-ultimate-performence-blazing-fast-t3482317)
No custom kernel (unless ultimate performance counts)
All other images are stock.
Please help. I would rather not have to buy a replacement, as I'm pretty sure unlocking the bootloader voids the warranty.
I am having the same problem. DNS never seems to get registered. This goes for tether and bluetooth connection share.
I managed to break something when trying to fix it, and so did a full stock reset. On the bright side, my phone's hardware is fine. On the downside, I forgot to back everything up before I broke it >.<
GravSpider said:
I managed to break something when trying to fix it, and so did a full stock reset. On the bright side, my phone's hardware is fine. On the downside, I forgot to back everything up before I broke it >.<
Click to expand...
Click to collapse
"broken" means 2 very different things to me and you when it comes to phones
bardhi92 said:
"broken" means 2 very different things to me and you when it comes to phones
Click to expand...
Click to collapse
I use the terms break and broke loosely. I am still pretty new to android and modifying it, so I often "break" the software when playing with things I do not understand. I look after the hardware though.
The obvious step would be to revert back to stock image and enable/replace your components one by one, so you can see which one is the cause for your non-working hotspot.
GravSpider said:
I managed to break something when trying to fix it, and so did a full stock reset. On the bright side, my phone's hardware is fine. On the downside, I forgot to back everything up before I broke it >.<
Click to expand...
Click to collapse
So re-flashing fixed it for you? I'm having the exact same issue...
EDIT: Just for future reference, reflashing everything from stock images (7.1.1) fixed this for me as well!

Categories

Resources