I'm not exactly sure when this problem started, but it persists across every ROM I try, even stock. For whatever reason I can't enable Bluetooth. The toggle stays grayed out when attempting to enable it, and the Bluetooth service just flat out crashes on Oreo. I've Googled around, and everything I find related to this problem dates back to when 6.1 was rolling out, and doing a factory reset was the only fix. I even found one post mentioning that removing the Bluetooth profiles in /data fixed this. Neither of these have worked for me. I even did a total factory reflash back to vanilla stock with a 7.1.2 image, but it didn't do anything for me. Does anyone have any insight on this? Google has been of no help.
Related
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.
Hello everyone!
I'm trying to watch some movies from Google Play Movies but everytimes it gives me this error: "There was a problem while playing, touch to retry.. or reboot the phone" (I don't know if it's the correct translation, my language is italian).
I googled a lot, and I found some possible solutions, like:
- reinstall the application
- clean app's data and cache
- wipe dalvik
- switch to 3g / change wifi
- enable AwesomePlayer instead of NuPlayer
- set the governor to "persistence"
I tried everything, but the problem is still there. I even tried to change rom and kernel but it hasn't solved it!
So I lost my hopes, and switched to Netflix.. but here, same problem! After pushing the play button, it starts a loop with the "loading in progress".. I tried the solutions above, but I haven't solved it yet
Am I the only one with this issue? How can I fix this?
Thanks, and sorry for my bad english
EDIT: I just discovered that by enabling the "simulate secondary screen" option under Developer settings, the movie magically starts into the secondary screen (this works for google play movies only... not for netflix). Anyone knows the reason?
I haven't come across this problem before. It sounds like the kind of bug you might encounter if you are using a custom ROM or kernel. If you are, you could try flashing back to a stock build and see if the problem goes away.
If you are using a stock ROM and kernel, it sounds like you have tried almost everything and it might be time to perform a factory reset. Obviously this is not a common problem with the Galaxy S6 Edge Plus, so it might be the result of a settings change you have made. The quickest way to test the theory will be to perform a factory reset - you can backup first if you want to.
If that doesn't solve the problem, it must be an issue with your WiFi or mobile data provider... but this is a very unlikely possibility.
Good luck with the problem.
nobnut said:
I haven't come across this problem before. It sounds like the kind of bug you might encounter if you are using a custom ROM or kernel. If you are, you could try flashing back to a stock build and see if the problem goes away.
If you are using a stock ROM and kernel, it sounds like you have tried almost everything and it might be time to perform a factory reset. Obviously this is not a common problem with the Galaxy S6 Edge Plus, so it might be the result of a settings change you have made. The quickest way to test the theory will be to perform a factory reset - you can backup first if you want to.
If that doesn't solve the problem, it must be an issue with your WiFi or mobile data provider... but this is a very unlikely possibility.
Good luck with the problem.
Click to expand...
Click to collapse
Thank you for your suggestions
At the moment I'm using Audax ROM and Kernel, but I had the same issue with the stock rom + arter97 kernel..
I had a look to the logcat, and by searching the errors on google I found other users in my same situation (with custom ROMs) I tried the fixes suggested but none of them worked
Same problem. Done most of the solutions provided. Nothing Works. Using Wanam Lite on SM-910C. Anyone could help. :-/
Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.
I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?
Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.
So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.
Hi,
I always thank you for nice information. I almost fixed my phone myself with the help of xda forum, only after I have "googled".
But this time, there's a problem I can't find the solution.
My Note 4 suddenly had few problems. After I had paired a Bluetooth game controller, and tried to change some Input option, the "setting app" just crashed. "Unfortunately Setting has stopped" was what I read. Since that point, every time when I try to go to the Bluetooth settings, it crashed.
After searching, I found that it could be fixed when I "reset" the network information, so I did it. I just got a blank list of Bluetooth and Wifi connection but however I could connect all my devices again… except this controller. As soon as this controller(with a specific name) connects, the setting began to crash again.
So my solution? Just not using the controller.
But after a while, I just got an another bug on the settings app. There is a shortcut for 9 items. After I added only 2 more shortcuts (so totally 7) the + button was disappeared.
It didn't bother me that much.
but... it now bothers me, after I have done the factory reset.
The same symptoms still there. I also did Odin Flash of the newest Firmware(which was already flashed over OTA) which I downloaded from Sammobile and did the wipe data/factory reset again.
Still the same bugs. With that controller, I never have a chance, and also the + button disappears after have added 2 or 3 shortcuts.
So I am really sure that the "settings app" is corrupted. But flashing the firmware didn't help. And even I flash with Odin again and again, the "user data" are still there. So I think this does not flash completely and there is somewhere in the phone a corrupted data for the settings.apk or the corrupted settings.apk is not being replaced or like that.
Is there any possibility to "force" ODIN to completely reflash the phone?
How do the Repair center flash? I thought they also use ODIN...
Any idea and suggestion?
Ok, I found the "answer" myself.
I just downgraded to the latest 5.1.1 firmware and the problem was gone.
But after I just upgraded again to the 6.0, setting app just shut down again because the bluetooth joystick was on the list.
I just upgraded without factory reset.
So it means that must be a firmware issue. No idea if it has to do with mainboards produced in a certain week or with the "name" of this gadget, which causes some crash in the marshmallow settings app.
Ok, now I just wanted to reboot the phone and it has a bootloop. hmm… No idea what's wrong.
so, i will try my luck. first thing is, i have a xt1684 retgb. atm i'm on full stock oreo firmware, a backup that i made where everything should have worked fine. after the issue appeared i restored the backup. but yea, it still persists. what a *****y phone.
now i have the problem, that in any case no voice is recognized neither via the build-in mics nor over a plugged headset.
neither a full stock flash to oreo nor to nougat changed it. everything else seems to be working as it should.
really guys, give me any hint to get rid of this. everything is welcome. :fingers-crossed: i count on you. cheers
okay got a little success in camera. in there i got my voice back after re-enabling mic permission in settings. but it doesn't help on google search e.g. .
i got my mic back working. but i still can't tell what caused it. maybe something equal to the problem that causes no touch issue. don't know. flashed a few stock and rom until it worked again. it was a work or die mission. as mentioned in the stock oreo thread it is really neccessary to let every stock flash finish with the initial setup (even if skip everything) till you are on launcher homescreen.