Database Develop

Bluetooth headset breaks up outdoors playing media but not during phone calls

I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?

It's not a stock rom.
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.

Without getting a logcat there is nothing anyone can do except guess what the issues is.

donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.

zelendel said:
Without getting a logcat there is nothing anyone can do except guess what the issues is.
Click to expand...
Click to collapse
I was hoping someone who had the same problem might chime in. What should I look for in the logcat?

johninor said:
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
Click to expand...
Click to collapse
I just clean flashed the latest version of the Lite ROM and it did not fix my problem.

donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
I tried a clean flash of the Lite ROM. That didn't solve the problem. I then flashed the latest factory image (MOB30W). I did not restore anything or install any apps except Google Play Music and Podcast Addict, which I am using to reproduce the problem. I still have the same problem. Bluetooth media audio is working indoors, but as soon as I step outside it breaks up and goes out completely for 20 or more seconds at a time.
I think that rules out the Lite ROM as the problem. Anyone have any ideas for me?

I googled looking for bluetooth audio breakup issues and I found a few things that were suggested to fix it. They were turning off the WiFi and and turning off GPS. I tried both and they did not help my problem. I didn't expect them to because they were fixes for people reporting general bluetooth breakup on specific devices, while I am seeing the breakup on Media Audio, but not Phone Audio.
If anyone knows of a better place to ask my question, please let me know. I've been searching and can't find an answer or a better place to ask the question.

After some research here may be a fix...
johninor said:
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
Click to expand...
Click to collapse
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

donnyutx said:
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
Thank you. I hadn't found that thread when I searched. I tried the several suggestions in that thread. One was clearing caches, which, of course, I had already done as a result of testing clean installs of the ROM I use and the latest stock ROM. So that didn't solve the problem. The other suggestion was turning off bluetooth scanning in location settings. I hadn't even known that was a thing. I tried turning off bluetooth scanning and wifi scanning this morning and used my phone all day as usual. It didn't solve my problem - no change at all. I had in an earlier test turned off the GPS and that hadn't helped either.
The second link, I believe is just a different way of installing ROMS and managing related stuff. I don't think that tool is going to do anything that I didn't do by installing the latest stock ROM with the flashall.bat script.

Jumping Screen After Nougat

Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/

Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)

Some issues I've had (2 days in)

Love the device, but this one is going in for an exchange. Not sure if it will resolve the issues I had, but my phone was behaving badly. I unlocked and rooted it about 10 minutes after I got it, using the Chainfire method here..
1) WiFi reception is awesome, except it drops the connection constantly! I have an entry level commercial AP (Unifi) and the thing is awesome. All kinds of devices connected to it, but this Moto can't stay connected. From the logs on the controller, it appears to be switching channels constantly. Wifi goes from all bars to bars with x to off.
2) Reboot results in bootloop. On more than one occasion, I had to reset the device multiple times to get it to boot. This morning, I could not get it to complete a boot at all. I've since reflashed the Tmo stock ROM.
3) Lookout randomly comes back! Froze it with TiBu, stop and disable in app manager... nothing kills it! Reason 1 for root!
The WiFi issue is a killer. Again, I am going to take this one in and exchange it for another and hopefully the WiFi issue is gone. I think I'll need to restrain myself from rooting until I pass the exchange date.

I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now

forty9er said:
I had similar issues what i did was flash the stock boot img then do a factory reset and reroot and everything is good now
Click to expand...
Click to collapse
Thanks! I will give that a shot before I take it in.

I've been back on stock with unlocked bootloader for a day and change, and I still get WiFi drops. It seems to happen more with BT on, but they certainly haven't gone away. I've changed a bunch of things on my AP to try and eliminate them too, but it hasn't helped much. I may try disabling the A/C radio (which fixes it for some), but that's hardly an answer. I am starting to think that this is a Nougat or a Qualcomm issue.

Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Sent from my Moto Z (2) using Tapatalk

Tidbits said:
Seems like a hardware issue. If it was a software issue then it would affect more than just you. So far you are the only person on various forms I go to having issues.
Click to expand...
Click to collapse
Well, it seems I'm not the only one.
https://forums.lenovo.com/t5/Moto-Z...terprise-type-5Ghz-band-802-11AC/td-p/3816198
I actually have this issue with another device too , so I think it's either an Android, AP or a Qualcomm thing. Some have said turning off the A/C/N radio helps, but that's not a "solution."

Question mi 11 ultra keeps freezing

hi,so i got my phone with china rom which the seller bootunlocked it and changed it to the offical global rom like 6 months ago and from 3 4 weeks agao im facing a really bad problem,before that i got the problem that i tapped one time and the device would think i've tapped 2 times and it closed the app,i thought it's because of the screen protectors.but from 3 weeks ago i'm facing these real problems:
1-phone suddenly freezes for 3 or 4 seconds then it's responsive for like a second and again till i close all apps and then it gets a little better but after i restart which sometimes leads to a boot loop, it doesn't get smooth and normal, even after that,after some time like 30 40 minutes it freezes again. even the keyboard freezes.
2-if the freezing continues i get a "---- app is not responding wait close",sometimes the miui system shows the same error but if i click on the wait it wont crash or such, it justs behaves like it was before showing the error.
3-sometimes after the restart the battery percentage is shown 0, which i'm pretty sure it isn't. upon restarting again the problem solves.
4-sometimes in specific applications my tap is considered a holding and shows me the holding menu.
5-sometimes i get glitches and lines in some parts of google chrome webs which fades by just scrolling,specially if a video is playing on the web page.
the phone didn't got any physical damage in the past.
i've tried these but no avail:
1-updating the miui
2-disabling virtual extension memory
3-factory reset
4-flash and install the offical rom which somehow lead to a bootloop.
5-flash and install the xiaomi eu stable rom which didn't go on a boot loop but the freezing continued
6-flashing and installing the official rom which this time didn't got stuck in a boot loop but right after booting showed me the "miui is not responding" but i setuped the phone and it sill got the freezing problem.
i used multiple benchmarks and even filled my ram with some app to see if it's the stress leading to a freezing but all the scores were perfectly normal even for storage and ram and the phone wasn't freezing during the tests and benchmarks
sorry that the text got too long but i'm really desperate.

Try in safe mode to rule out a buggy 3rd party app. Run for a day or more.
If it fails that it may be a buggy system app.
Otherwise it may be a hardware issue.

blackhawk said:
Try in safe mode to rule out a buggy 3rd party app. Run for a day or more.
If it fails that it may be a buggy system app.
Otherwise it may be a hardware issue.
Click to expand...
Click to collapse
so i entered the safe mode but it's a black screen with the text : safe mode under it .then it went to booting itself with some vibrations and the non ending mi logo on the screen.

mr.fazeli said:
so i entered the safe mode but it's a black screen with the text : safe mode under it .then it went to booting itself with some vibrations and the non ending mi logo on the screen.
Click to expand...
Click to collapse
Sounds like the firmware is corrupted. This normally shouldn't happen.
Possible rootkit, a hardware failure or perhaps a single event upset hit the kernel or bootloader.
A complete reflash (impossible with a locked bootloader!) will purge any malware, remedy a SEU but not resolve a hardware failure.
Make sure all critical data is redundantly backed up now. It may crash and burn at any time running like that. Not good.
Return for warranty repair if possible.
That's my take on it, someone more familiar with that platform may have a better plan.

blackhawk said:
Sounds like the firmware is corrupted. This normally shouldn't happen.
Possible rootkit, a hardware failure or perhaps a single event upset hit the kernel or bootloader.
A complete reflash will purge any malware, remedy a SEU but not resolve a hardware failure.
For the latter a different rom may work if it bypasses the damage.
Return for warranty repair if possible.
Click to expand...
Click to collapse
I’ve flashed it 2 times with the mi flash tool and one time with the xiaomi eu rom fastboot registery. unfortunatly iv’e got no warranty for the phone in my country,so i fix it or i have to sell it cheap.

mr.fazeli said:
I’ve flashed it 2 times with the mi flash tool and one time with the xiaomi eu rom fastboot registery. unfortunatly iv’e got no warranty for the phone in my country,so i fix it or i have to sell it cheap.
Click to expand...
Click to collapse
See my previous edited post. The issue may be the bootloader has been corrupted and/or a hardware failure. You're in way deeper than I ever had to go with the firmware on an Android.

blackhawk said:
See my previous edited post. The issue may be the bootloader has been corrupted and/or a hardware failure. You're in way deeper than I ever had to go with the firmware on an Android.
Click to expand...
Click to collapse
Can i flash or reset the boot loader? Also thank u for helping me.

mr.fazeli said:
Can i flash or reset the boot loader? Also thank u for helping me.
Click to expand...
Click to collapse
Not if it's locked. Someone may know how to unlock it here, I do not. That may not be the issue though or the root cause... You're welcome but I'm afraid I wasn't much help.
Try some Google searches for that manufacturer and devices with the same issue. Add xda to the searches to search XDA, that works better than the XDA search engine.

S20FE Bricked itself

Hey so my father's phone just kinda bricked itself one morning. We don't know how or why. But he did tell me he installed the newest software update a few days ago, meaning he got OneUI 5.0.
If it matters, this is a german version of the S20FE, unfortunately im unaware if he has the Samsung CPU or Snapdragon CPU version.
I'm tasked with getting the data off the phone, but unfortunately i can not boot into android. The phone either freezes at the "Samsung Secured by Knox" logo or bootloops at that logo. When charging it does not show battery percentage, only the lightning symbol.
I can easily access the downloading mode, but recovery mode is very hard to get to, usually because of the bootloop, takes me around 10 to 30 minutes to get into.
Wiping Cache partition does not work, "repair apps" results in the bootloop
The logs always end displaying 3 times the same error: unable to set property "ro.boottime.init.mount.cache" to "1": error code: 0x18
Does anyone have an idea on how to get all the files off of it? I heard you can use Odin to flash it without losing data but also heard that it doesnt work since OneUI 3.1, and since OneUI 5.0 is very fresh i don't think anyone ever tried flashing it without data loss.

Unless you can boot it into safe mode you're boned.
If he really needs the data... take it to a data recovery specialist. Rates are around $800 for advanced recovery services, it may be less.
Otherwise see if a factory reset fixes it. Always redundantly and regularly backup critical data to avoid complete data lose.

blackhawk said:
Unless you can boot it into safe mode you're boned.
If he really needs the data... take it to a data recovery specialist. Rates are around $800 for advanced recovery services, it may be less.
Otherwise see if a factory reset fixes it. Always redundantly and regularly backup critical data to avoid complete data lose.
Click to expand...
Click to collapse
Safe Mode Freezes up
And knowing my Father, he won't pay that amount of money to recover the data..

JojoOn3DS said:
Safe Mode Freezes up
And knowing my Father, he won't pay that amount of money to recover the data..
Click to expand...
Click to collapse
Maybe it's a lesson he needs to learn the hard way. Androids rarely crash and burn but it does happen. Messing with the firmware is always a risk. One reason why I never do OTA updates/upgrades.
Data is fragile... not redundantly backing it up is an open invitation for trouble. A drop, water exposure, a near lighting strike, a hardware failure, malware, etc can destroy the data if that's the sole copy of it. Really it's only a matter of time until it happens. He needs to take a more vested interest in the device... or suffer the consequences.
Maybe someone here can help you but hands on by a specialist maybe the only viable shot there is at recovering the data now.

I have been able to unbrick Samsung devices in the past. I have posted what I did on this website.

blackhawk said:
Maybe it's a lesson he needs to learn the hard way. Androids rarely crash and burn but it does happen. Messing with the firmware is always a risk. One reason why I never do OTA updates/upgrades.
Data is fragile... not redundantly backing it up is an open invitation for trouble. A drop, water exposure, a near lighting strike, a hardware failure, malware, etc can destroy the data if that's the sole copy of it. Really it's only a matter of time until it happens. He needs to take a more vested interest in the device... or suffer the consequences.
Maybe someone here can help you but hands on by a specialist maybe the only viable shot there is at recovering the data now.
Click to expand...
Click to collapse
Update, he sais he has his files on google drive. Now i tried to reinstall android using Odin3, i installed OneUI 4 with android 12, the farthest that i got was now a charging indicator showing percentage and the samsung android bootlogo after the bootloader logo. but then it crashes. OneUI 5 android 13 makes it bootloop again. The last thing i might do is just root the device

JojoOn3DS said:
Update, he sais he has his files on google drive. Now i tried to reinstall android using Odin3, i installed OneUI 4 with android 12, the farthest that i got was now a charging indicator showing percentage and the samsung android bootlogo after the bootloader logo. but then it crashes. OneUI 5 android 13 makes it bootloop again. The last thing i might do is just root the device
Click to expand...
Click to collapse
Well that's good... if it works.
You try the last version it was running on before it went to hell? If was me I use the earliest version available. I would not root it as dad will likely get in trouble for sure... and lose some core features forever.
First thing I would have tried is a factory reset. Anytime you flash firmware you're taking a risk; there's zero risk to clearing the user data partition.

blackhawk said:
Well that's good... if it works.
You try the last version it was running on before it went to hell? If was me I use the earliest version available. I would not root it as dad will likely get in trouble for sure... and lose some core features forever.
First thing I would have tried is a factory reset. Anytime you flash firmware you're taking a risk; there's zero risk to clearing the user data partition.
Click to expand...
Click to collapse
The data is already gone, it was backed up by Google Drive and my dad got the data on his older phone now. The earliest version i can install after an OneUI 4 update is OneUI 4 android 12, which i have already tried, any older than that results in a Fail because the device refuses to flash OneUI 3 or older.
It does boot android *sometimes* with OneUI 4 Android 12. but never to the "Welcome" screen. OneUI 5 Android 13 causes it to reboot nonstop again (like originally). I am planning on downloading different versions of OneUI 4 android 12 for this device and see if it ever boots fully.
Allthough this seems like a software defect, im starting to doubt the battery itself, because when it was charging it only showed 5% after an entire night on the charger.

JojoOn3DS said:
The data is already gone, it was backed up by Google Drive and my dad got the data on his older phone now. The earliest version i can install after an OneUI 4 update is OneUI 4 android 12, which i have already tried, any older than that results in a Fail because the device refuses to flash OneUI 3 or older.
It does boot android *sometimes* with OneUI 4 Android 12. but never to the "Welcome" screen. OneUI 5 Android 13 causes it to reboot nonstop again (like originally). I am planning on downloading different versions of OneUI 4 android 12 for this device and see if it ever boots fully.
Allthough this seems like a software defect, im starting to doubt the battery itself, because when it was charging it only showed 5% after an entire night on the charger.
Click to expand...
Click to collapse
If SOT sucks now...
Replace the battery before you attempt another flash. Not worth bricking a phone over a battery.

blackhawk said:
If SOT sucks now...
Replace the battery before you attempt another flash. Not worth bricking a phone over a battery.
Click to expand...
Click to collapse
Yeah will probably do that, i have already flashed it like 30 times probably haha, still soft bricked like before but not hard bricked.

JojoOn3DS said:
Yeah will probably do that, i have already flashed it like 30 times probably haha, still soft bricked like before but not hard bricked.
Click to expand...
Click to collapse
No harm, no foul...