Related
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
j.smith said:
Figured perhaps a bug thread for the Rogers 2.2 update may be in order?
Not sure if this is a bug or not, but it does seem a bit odd. The lock screen usually has the text "swipe screen to unlock" or something to that nature (the part with the <<< and >>>) - mine had it to begin with in 2.2, however now it has dissapeared and I just see the little lock icon saying the phone is locked. Is there any way to get it back or is this a 2.2 "feature" so you see more of your background?
The 2nd problem I noticed I have already started a thread on (and no replies ) - it deals with contact linking and Facebook. Seems something is whacky there too possibly. The thread: http://forum.xda-developers.com/showthread.php?t=907088
Click to expand...
Click to collapse
Definitely a feature. I love the clearer lock screen.
Bug: Haptic feedback vibration is very low system wide (not including soft keys).
Bug: Voice Dialer (Voice Dialler) is misspelled in the App Drawer.
Bug: Going to Settings > Display > Font Style causes a crash.
All I remember so far but there has been several.
Enhanced said:
Definitely a feature. I love the clearer lock screen.
Click to expand...
Click to collapse
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Enhanced said:
Bug: Going to Settings > Display > Font Style causes a crash.
Click to expand...
Click to collapse
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
rnewton01 said:
I've had some issues with wifi losing it's internet / market connection after wake up sometimes. shows still connected, but no network access. i have to turn wifi off, then back on occasionally.
Click to expand...
Click to collapse
Go to Settings -> Wireless and network -> Wi-Fi settings. From this screen, hit your menu key and select Advanced and try changing your Wi-Fi sleep policy to Never... perhaps it's set to "When screen turns off" causing you to lose Wi-Fi whenever you lock your phone?
Oh, another bug possibly...
Go to Camera app and open Settings. Open the wrench tab and go to the 2nd page. Click the Update button beside Firmware update. Either of the next two menu choices ("Check version by network" or "Firmware update") seem to freeze the phone (power off required). Doesn't seem to happen all the time, but my first time trying to get the update to do something caused the phone to lock up in to camera mode.
Also, the "It will occur additional fee." message is quite fun... no idea what fees I will incur, or for what reason (and I won't even get in to the grammar issues).
j.smith said:
Confirmed feature of Froyo, or is this a Rogers/Samsung specific feature? Just wondering because it WAS showing up for a few lock screens right after the upgrade, then eventually stopped showing up - reboot/battery reset didn't get it back... haven't tried a factory reset yet to see if that fixes it (if it's broke).
Click to expand...
Click to collapse
Well it can't be a Froyo feature because no other manufactures use the same lock screen as they do. So it's a Samsung feature brought on by Froyo. Simply, it can't be a bug.
No problems here - did you have it set to a custom/non default font when upgrading? I had mine on default (I prefer that to any other font) and have no issues changing fonts.
Click to expand...
Click to collapse
Yeah, I had to it some other font besides the default font...guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Enhanced said:
W..guess I'm screwed now? Bugs like these make me more anxious to get real Froyo.
Click to expand...
Click to collapse
This is real Froyo from Rogers.
Anyone noticing that it's very glitchy and not smooth?
sirknattar said:
Anyone noticing that it's very glitchy and not smooth?
Click to expand...
Click to collapse
Its much faster and smoother than 2.1 stock was for me. Did you set it up fresh? Older settings can cause issues.
you guys have this issue? you may not even know it until you try to use mass storage mode. I use iSyncr (lets me use smart playlists based on ratings) so I need mass storage mode.
http://forum.xda-developers.com/showthread.php?t=907854
My wife and I (each have a Captivate) have had none of the bugs you guys have mentioned.
All we have experienced is a faster phone and WAY better battery life.
The only thing that upset me is that the update deleted my Ocean Wave livewallpaper, but I just redownloaded it.
Did some of you guys experiencing bugs ever run a custom ROM? I am thinking maybe these issues might be because you did...
Re: Haptic Feedback.
I've noticed it too, it's much weaker than before.
I could have sworn that I saw the option to turn up the intensity before, but can't find it now.
I want to update, but all these bugs are not very comforting
Jeffu said:
I want to update, but all these bugs are not very comforting
Click to expand...
Click to collapse
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
shawn122 said:
Go for it..I installed it and so far the improvements have been great over 2.1
Battery life is much improved, its faster than stock 2.1 (and after applying Ryan's OCLF...its incredibly responsive)
If you do have a lagfix installed prior to upgrading you should uninstall that first. Thats what I did and didn't have much problems. my one issue with Swype was fixed by clearing the cache.
Click to expand...
Click to collapse
I gave it a go on your recommendation. Updated with no issues, now to actually try using it...
Has anyone rooted after applying 2.2? If so, what did you use?
I've been having issues turning on WiFi on my phone ever since I installed the update.
I accidentally clicked Airplane mode on my phone this morning, now my phone has been trying to turn the WiFi back on for about 5 mins....
As for battery life, my phone the first few days after installing Froyo seemed great, but now it doesn't really seem as good? No idea why....
And I've noticed a bit of lag at times while navigating on my phone.
Using LauncherPro Plus as my home screen, haven't rooted or installed any roms or anything.
I have noticed that when you turn the phone on from when it is off, if you don't wait for the wallpaper to display before swiping your phone on, the phone will stall. Mine stalled for about 5 minutes before it responded again.
I'm having a couple of small issues:
1) I can't get the GPS to look position. It just displays "Waiting for Location" and sits there.
2) OCLG - I got about 1000 on quadrant score. It doesn't seem laggy but I wanted to apply this lagfix to see if it can be better. I tried runnig the first option in the menu (z4 rooting), and it tries to launch either a page or the market (not sure which) but says "Page Not Found", but when you close it and press back, it says the root was successful, but all the other options are still "unavailable" so I can't apply the lagfix. There's a second method in the menu to do a root and that one fails as well, so I'm not sure how to get this working.
3) Camera - I got the same problem as a previous poster for the firmware update where it says "fees will occur" then when I click "yes", it tries to launch a page/market (again not sure) and says "Page Not Found".
4) Rooting - not sure how to root because the previous method of putting my update.zip and doing it through the recovery menu fails.
Any help is appreciated.
I was running rooted lagfixed stock Rogers 2.1 before. Removed lagfix first and did a factory reset before updating to 2.2 through Kies.
After updating to 2.2 I re-rooted and lagfixed with no issue.
Things bugs I have noticed on my phone:
- Camera a few times had started up with a black screen only with usual camera options but it's as if it does not see anything from the lens (had done camera fw update on it. You can download it from Samsung Apps app)
- When viewing "Contacts" can't press Back button to exit it so I just press Home button. Small bug
- can't set up smtp outbound email settings on stock email app. Keep getting it can't connect with server even when manually inputting correct settings.
- Battery undetermined as i've been playing with GPS a lot testing it so it drains pretty quick.
- GPS - Had no problems with 2.1 (using GPS + "Use wireless networks") but it's been horrible on 2.2. Locks ok when stationary, fluctuating between 5-9 satellite locks (used lbstestmode to check) but when you are moving or when using it for Navigation, it will be ok for a short bit then would eventually start bouncing all over the place or start getting weak/lost locks. Was using it on the hwy one time and it would suddenly tell me to do a u-turn because it thought I was on a side road. (condition was clear and phone was by windshield).
What it did fix for me:
- Opening Gallery before would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2
- Running latest updated Maps would sometimes lock up the phone requiring battery pull in 2.1. Fixed for me with 2.2 but still somewhat useless because of issue mentioned previously.
I can live with all the bugs except for the abismal gps.
So, ever since I rooted my SGS4G I've had three really odd issues that happens across all ROMs - stock, custom, ODIN, CWM - all of them.
1. When I first boot up the phone it gets stuck in landscape mode. Sometimes it fixes itself after 30-60 minutes, sometimes it doesn't.
2. It randomly goes into Car Mode or Desk Home starts up on its own - on ICBINB and Audiophile if I hit the Home Key then it starts Desk Home. So I have to back out to the Home screen.
3. Also, whenever I play certain games (ex. Angry Birds), it only works for a minute or two, then goes to the home screen. I've uninstalled and reinstalled the games and it still happens.
So, has anyone else had similar or identical issues? If so, how'd you fix them?
I use Titanium Backup to restore most of my apps because, for whatever reason, the Google backup/restore doesn't work with this phone (even in stock). I don't restore system information, just missing apps.
If you want my 2 cents i would say it is hardware, where you are switching roms and the same problem is still happening, the rom should clear out all memory, cache, etc. i would you say to take it back to the store and get a new one. sounds like there is an error with the sensor. good luck
HB66 said:
If you want my 2 cents i would say it is hardware, where you are switching roms and the same problem is still happening, the rom should clear out all memory, cache, etc. i would you say to take it back to the store and get a new one. sounds like there is an error with the sensor. good luck
Click to expand...
Click to collapse
Yeah, I was hoping it wasn't the hardware. Oh well.
if you do take it back you may want to unroot and go back to stock just to be safe because they may see that and say you voided the warranty.
HB66 said:
if you do take it back you may want to unroot and go back to stock just to be safe because they may see that and say you voided the warranty.
Click to expand...
Click to collapse
Yeah, but I'm kinda SOL because I'm not with T-Mobile. I'll just deal with it til I get another phone.
those are very unique problems. i have yet to hear of anyone experiencing problems like that. to me, it sounds like you didnt calibrate your horizontal sensor properly. odin to kc1 and get a fresh start. then make sure you factory reset, wipe cache and your mounts are correct before flashing the ext4 converter and then the audiophile or icbinb rom again. dont reinstall your apps from TB. it usually causes problems for certain apps. download from the market again, back up your apps with cwm, or simply go into data folder with root explorer and copy the apk and the data lib and push it to the rom before you flash. when this is done, let it load and then go back to fix permissions. then go back and recalibrate your horizontal sensor. if you want, you can delete the carcradle.apk and the deskcradle.apk if it still gives you problems.
jager555 said:
those are very unique problems. i have yet to hear of anyone experiencing problems like that. to me, it sounds like you didnt calibrate your horizontal sensor properly. odin to kc1 and get a fresh start. then make sure you factory reset, wipe cache and your mounts are correct before flashing the ext4 converter and then the audiophile or icbinb rom again. dont reinstall your apps from TB. it usually causes problems for certain apps. download from the market again, back up your apps with cwm, or simply go into data folder with root explorer and copy the apk and the data lib and push it to the rom before you flash. when this is done, let it load and then go back to fix permissions. then go back and recalibrate your horizontal sensor. if you want, you can delete the carcradle.apk and the deskcradle.apk if it still gives you problems.
Click to expand...
Click to collapse
I'll try all this tomorrow. I just got home from work and I'm tired as hell. Thanks for the info and I'll letcha know how it turns out.
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.
My GS3 is currently running Bean's Custom Rom build 14; was briefly running Jellywiz RLS8 (nice but too buggy for me) and prior to that was stock/rooted/unlocked with the toggle mods and nothing else. I had updated the radio as the new ones came available. Anyhow, some time ago when I was still on the stock Rom, I could no longer get a GPS lock. Prior to that it had worked just fine. So I flashed crypted's "fix" from this thread (tried both the GS3 specific and generic Google builds) and I was able to almost instantaneously get a "lock," which to me meant the GPS icon in the notification bar went to solid.
HOWEVER, I was now showing my location as being outside of Raleigh, NC - I live in Atlanta, GA. With standalone and Google/VZW gps turned on I would get a relatively accurate location (~30 meters) in Maps but a completely wrong location in Foursquare and my weather apps. So I followed Crypted's directions. I tried wiping cache/dalvik, tried modifying RIL in build.prop from 2 to 1, finally tried the solution where I unchecked all three options in Location settings, powered off, battery pull for 30 secs, reboot to recovery, wipe cache and dalvik, reflash his zip file, boot up, enable ONLY standalone GPS and go to nav, put in a destinaton and let it sit outside for 10 mins. After that it FINALLY gave me an accurate standalone GPS location. Problem is, when I rebooted my phone sometime later in the day, the GPS went back to North Carolina and was essentially broken again. Only after repeating the same process from before did I get it to work again, and even at that it takes a good 10 mins for standalone GPS to update my position when change my location. So what the heck is going on here? Clearly GPS is working on the hardware side, if ever so slowly. Anybody have any suggestions? My next step is to Odin all the way back to stock and see if that fixes it, but I'd really prefer not to have to go through all that trouble. Thanks for any suggestions.
Hey anyone with ideas on this? I know the OP was long but the short version is that after every reboot my standalone gps location reverts back to raleigh, north carolina, a place far from me that my phone has never been. Then it takes about 10 minutes of sitting outside w/ navigation on for the phone to get back to an accurate GPS location. I ran GPS Status during that time and noticed the phone is not locking onto any satellites during that time, up until it finally repositions itself accurately.
You can try this one. Works for some that can get lock but get erroneous locations.
http://forum.xda-developers.com/showthread.php?t=1880810
Thanks, will give it a shot. Hope the issue is addressed in the next ota.
prdog1 said:
You can try this one. Works for some that can get lock but get erroneous locations.
http://forum.xda-developers.com/showthread.php?t=1880810
Click to expand...
Click to collapse
The fix didn't work for me. We have (4) GS3's in my family and mine is the only one that doesn't get a lock in seconds, even indoors. I finally bit the bullet and am exchanging it...
Just got a replacement N5 from Google for a warranty issue and after full re-root and setup I went to get in the car today and use bluetooth and I noticed a problem. Bluetooth will not turn on. Tapping the slider moves the position to on but it remains greyed out and, in fact, off. I tried a restore of the bluetooth share and pairings from Titanium backup and that just hung and never completed. I can always factory reset it but I hate to go back through that ... anyone got a way to 're-install' bluetooth and save a reset and reconfiguring for me?
SWBgHz said:
Just got a replacement N5 from Google for a warranty issue and after full re-root and setup I went to get in the car today and use bluetooth and I noticed a problem. Bluetooth will not turn on. Tapping the slider moves the position to on but it remains greyed out and, in fact, off. I tried a restore of the bluetooth share and pairings from Titanium backup and that just hung and never completed. I can always factory reset it but I hate to go back through that ... anyone got a way to 're-install' bluetooth and save a reset and reconfiguring for me?
Click to expand...
Click to collapse
This apparently has been problem for Nexus 4 and Nexus 5. One poster from android central posted this for his Nexus 4:
I called Google technical support and they found a solution for me.
-In your Nexus 4, go to parameters/Applications/All/Bluetooth
-Here: erase cache, data and updates.
-Resart your phone.
In Nexus 5 Settings>Apps>All>Bluetooth Share. There you might try Clear data and Clear cache.
Got nothing to lose. Hope it works. I cannot test it myself since my Bluetooth is working.
Thanks for the suggestion. I had looked around and saw a couple mentions loosely similar related to the N4 but wasn't sure if same applied to N5. Looking though ... I do not have a bluetooth share app installed. That must be the issue, anyone got a way to re-install that Bluetooth Share, seems my backups from Titanium won't restore it.
Found thread where someone had your issue and solved it with reset.
http://forum.xda-developers.com/google-nexus-5/help/activate-bluetooth-t2595761
Maybe you could do backup to PC and get this restored with reset.
I know it is a PITA.
I figured a reset would square it away, was just hoping to find a way to avoid that if I could. I suppose next w/e I will reset if I don't find another way to get BY back.
Sent from my Nexus 5 using xda app-developers app
SWBgHz said:
Thanks for the suggestion. I had looked around and saw a couple mentions loosely similar related to the N4 but wasn't sure if same applied to N5. Looking though ... I do not have a bluetooth share app installed. That must be the issue, anyone got a way to re-install that Bluetooth Share, seems my backups from Titanium won't restore it.
Click to expand...
Click to collapse
It is working in Nexus 5 same as N4, Go ahead same way it will work
https://play.google.com/store/apps/details?id=com...bluetoothfixrepair
I tried, but there is no Bluetooth Share app installed that I can see in the program manager.
Sent from my Nexus 5 using xda app-developers app
joannn said:
https://play.google.com/store/apps/details?id=com...bluetoothfixrepair
Click to expand...
Click to collapse
When I run this app, it says no BT folder found. Seems the issue is that somehow this BT Share app just isn't there.
Another fix...
I know you already solved your problem, but I thought for people like me, who have found this thread later on, I'd just sign up to XDA and post my fix.
I didn't want to do a hard reset, so I played around with the "Bluetooth-Share"-thing in the Android app manager.
I cleared the cache and the data, that didn't do anything, even after a reboot I couldn't get the Bluetooth toggle from beging greyed out.
After that, I found that button at the very top right, that is labeled as " Uninstall Updates" or something like that. I tapped it and tapped OK at the following prompt. Where the "Uninstall Updates" button was before, should now be a greyed out "Disable" button. Then you need to reboot.
Try to enable Bluetooth. The toggle should turn blue after a few seconds as usual. Bluetooth should work normally now.
I hope my post helped anybody, :cyclops:
-hiwye
I am not having any luck. My bluetooh stopped working after doing a hard reset. Please note I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N4 and N5 have always been completely stock.
I've tried everything in this thread, except I am not sure what hiwye is talking about as I cannot find an uninstall updates. I went ahead and tried another factory restore/wipe and still have same issue. I hit toggle to turn Bluetooth on, it then immediately toggles back to off.
Just as a side note, my bluetooh was working fine until the factory wipe/reset. I did the reset in an attempt to fix a sim card slot issue, that is also still not resolved. Upon restarting my phone, I get "no sim card" message. I got a new sim card and also confirmed the sim card works fine in other phones..... i can turn off, pop it out and back in and boot it again. sometimes it will see the sim card again. It may take 20 times, but finally work..... I should probably start a new thread on the sim card thing, but wondering if my motherboard needs replaced.....
hiwye said:
I know you already solved your problem, but I thought for people like me, who have found this thread later on, I'd just sign up to XDA and post my fix.
I didn't want to do a hard reset, so I played around with the "Bluetooth-Share"-thing in the Android app manager.
I cleared the cache and the data, that didn't do anything, even after a reboot I couldn't get the Bluetooth toggle from beging greyed out.
After that, I found that button at the very top right, that is labeled as " Uninstall Updates" or something like that. I tapped it and tapped OK at the following prompt. Where the "Uninstall Updates" button was before, should now be a greyed out "Disable" button. Then you need to reboot.
Try to enable Bluetooth. The toggle should turn blue after a few seconds as usual. Bluetooth should work normally now.
I hope my post helped anybody, :cyclops:
-hiwye
Click to expand...
Click to collapse
Prodeje79 said:
I am not having any luck. My bluetooh stopped working after doing a hard reset. Please note I've never rooted or flashed a ROM, or unlocked boot loader or anything. My N4 and N5 have always been completely stock.
I've tried everything in this thread, except I am not sure what hiwye is talking about as I cannot find an uninstall updates. I went ahead and tried another factory restore/wipe and still have same issue. I hit toggle to turn Bluetooth on, it then immediately toggles back to off.
Just as a side note, my bluetooh was working fine until the factory wipe/reset. I did the reset in an attempt to fix a sim card slot issue, that is also still not resolved. Upon restarting my phone, I get "no sim card" message. I got a new sim card and also confirmed the sim card works fine in other phones..... i can turn off, pop it out and back in and boot it again. sometimes it will see the sim card again. It may take 20 times, but finally work..... I should probably start a new thread on the sim card thing, but wondering if my motherboard needs replaced.....
Click to expand...
Click to collapse
I get the same Sim card missing screen I have tried a new sprint Sim and same issue. They way I have been fixing it is to pop off back cover and where the vibration motor sits (stays attached to cover) I put my finger in the hole and squeeze the 2 parts together and hold tight till it finishes booting and it will see the card. I'm not sure what's exactly the problem is but it works as temp fix and will stay until the next reboot.
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
I get the same Sim card missing screen I have tried a new sprint Sim and same issue. They way I have been fixing it is to pop off back cover and where the vibration motor sits (stays attached to cover) I put my finger in the hole and squeeze the 2 parts together and hold tight till it finishes booting and it will see the card. I'm not sure what's exactly the problem is but it works as temp fix and will stay until the next reboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
can you take a pic of where you apply pressure?
Any other issues? My bluetooth still doesnt work.
Prodeje79 said:
can you take a pic of where you apply pressure?
Any other issues? My bluetooth still doesnt work.
Click to expand...
Click to collapse
Only device so doing it and taking PUC not gonna happen let me look up some images and I'll post them its not that difficult if you have had the back cover off before its very obvious where motor is. The motor is literally just under the flash led. Pop off cover starting at the top and slowly down each side with a guitar pick there is a tiny bit of adhesive at the bottom of rear cover about where the soft keys are when phone is on. Peel that up slow and you will see the vibration motor stuck to rear cover. See the space it came out of and put finger in that hole. And other finger opposite the first one on the glass and squeeze.... Not crazy so you break screen. Don't take much pressure. Start light and boot it. Says no Sim, try again with a little more pressure. When it first happened I googled sh*t for 2 days and couldn't find a fix. And this worked when I tried and a few reboots after. I shut phone off or battery dies I gotta do it to get Sim recognized.
Sent from my Nexus 5 using XDA Free mobile app
Docarut said:
In Nexus 5 Settings>Apps>All>Bluetooth Share. There you might try Clear data and Clear cache.
Click to expand...
Click to collapse
Worked for me, thanks.