(EDIT) Solution: I remember a long time ago when I went from stock to CM11 I lost all GPS capability. It was determined this is just a random occurance and all you need to do is flash back to stock, get a lock, then reflash CM11 until the lock sticks. With this previous tactic, I applied the same principle to the bluetooth issue since it was apparent I had a unique situation and most did not have issues. Steps taken to fix the bluetooth issue:
Step 1: Backup everything to external SD
Step 2: RUU back to GPE 4.4.2 (found VZW variant on XDA)
Step 3: OTA Update to 4.4.4 because the build needs to be higher than 4.4.2's build
Step 4: Ran bluetooth through car for a little bit and also ensured I had a GPS lock
Step 5: Reflash CM Recovery
Step 6: Wiped /system, /data (sdcard), /cache, and /dalvik
Step 7: Flashed CM12. Restored via Titanium Backup and on 3rd day without bluetooth dropping out yet (fingers still crossed)
Obviously I did not provide much detail on the steps because there are numerous tutorials already. However, if someone would like more explicit instructions just ask.
----------------------------
Greetings. A few weeks ago I made the jump from CM11 to CM12. I first did a dirty flash and a had a few problems so I ultimately did a clean flash. I transferred everything to my external and wiped everything else (system, data, dalvik, cache) then reinstalled CM12. Both on CM11 and CM12 I noticed that my bluetooth, when connected to my car streaming audio, would randomly disconnect. The phone would still think it was connected, but my headunit would lose the connection. This never happened on CM11, leading me to believe the headunit is not the culprit. I've erased the bluetooth cache, wiped cache in recovery, and deleted and repaired numerous times.
Android 5.0.2
CM version 12-20150320-NIGHTLY-m8 (has been happening since I first switched in the beginning of March)
Kernel: 3.4.0-g1ac088b
What I've observed:
- I cannot force the disconnect through any specific action
- It almost exclusively (cannot say for 100%) happens when the screen is off
- It does not happen every time the screen is off
- I've tried in both performance and balance mode -- no difference
- I've never had this problem before going to CM12
- When the connection is working, everything works as expected (no volume issues, can control through headunit, etc)
- If I disable then reenable bluetooth the devices will reconnect and work until the random disconnect occurs again
- When connected as phone only, it does not disconnect. It is only the audio profile (A2DP I believe)
Has anyone else observed this as well? Furthermore, does anyone have a solution? I've scoured the interwebs and I found a few issues but all related to the One Plus One -- and those solutions did not work for me.
Any help is greatly appreciated. I did a CATLOG and noticed numerous bluetooth issues, but I do not have the log on me at the moment. I can recapture it and post it if it helps.
Thanks.
Bill
Related
I followed directions to wipe everything as suggested in this post:
http://forum.xda-developers.com/showpost.php?p=20485148&postcount=146
Was using Alfa 13 just fine, but on Alfa 17 I can not get cellular data to work. Confirmed my WAP settings are correct for my carrier.
My baseband it says its a i9020xxkf1 and everything else on the phone works. I can access the market, wifi works, account sync if i have wifi on. I have doubled checked every possible setting. But it will not bring up a data connection over the cellular radio. It even takes calls over the radio. Just no data connectivity.
Any suggestions or reasons why this is occurring? I can easily swap back to an older nandroid image of alfa 13, but I would really like to get on a new version etc.
(Also, I would have made this post in the right dev section, but i lack 10 posts to gain access to it.)
Have you tried removing and replacing your SIM card ?
Also, check if your data counter has a limit set on
You could also manually configure your APN settings with your carrier's settings
Unfortunatly I have done all of those things. It doesn't even attempt to connect to data. I sit at 4 or 5 bars of signal and it never even connects to EDGE/3g at all. Yet if I flip back over to my older image it works flawlessly.
i have also problem with version 17, but i can't post it to developer forum (newbie here)
problem is that i can't hook on any network, no calls no messegas, i'm using croatian tele2/t-mobile....sometimes it connects but still nothing, no calss etc.
also problem (not so much a problem but a solution) when i installed ROM it went to bootloop, all you have to do is remove battery and power up again, and voila, it works, same problem happened when i installed gapps (same solution worked, everything installed from CWM latest version)
there were also posts regarding cwm not stiking after installing cynogen, i had no problem with it, i have latest cwm 5.0.2.3 (think so), sticks like hell tried couple of roms, still sticking
cheers
I have the same problem here... ICS 4.0.3 and my 3G stopped to work.
also tried new 18 version, still no luck, i'm staying on cynogenmod 7 (GB), only ICS version that worked was MUI but i don't like it very much....
http://forum.xda-developers.com/showthread.php?t=1398691
It has been messed around with a fair bit. Various methods have worked for different people. YMMV. I myself had such an issue with the stock FW (of all FWs...).
Q&A for [ROM][4.4.4r2]p6800/p6810/i815(12Sep2014)CarbonROM Kitkat Unofficial
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth (BlueZ) issues on Samsung Tab7.7 CarbonRom (latest by Daniel_hk)
Hi!
Having flashed this http://forum.xda-developers.com/showthread.php?t=2723126 pretty one, I've experiencing unstable bluetooth connection with almost everything. Philips bluetooth music station connects after 10 seconds only for half a minute then drops (i can see a slight screen flash-redraw on the phablet), car multimedia does not discover the phablet as a 'phone' device (only audio), which means no convenient hands-free for me. And I'm not alone to these problems: http://forum.xda-developers.com/showpost.php?p=55861531&postcount=103, 'alnon' describes same issue.
Can someone check out this ROM and/or confirm this bug? Also, if anyone knows of a solution/fix, please advise!
A Big Thank-You to Daniel
I've used some of Daniel's roms before, but I have to say that the Carbon rom is by far the best -- fast, with low battery usage, and a chance to use KitKat.
Thanks.
Samsung Tab 6800 CarbonRom
Hi,
I just installed the unofficial CarbonRom(4.4.4) release on my Samsung Galaxy Tab P6800. I upgraded from official rooted ICS using TWRP. The tab boots up fine but hangs within a minute of operation. Please help and let me know if you guys have any ideas on what is causing this.
Regards
Here I installed last build (december one) and bluetooth cant receive files from another android, neither can turned off. I have a p6800.
Bluetooth bug... cant turn off
I really like this carbon Rom. It runs like a Mercedes SL. But i have one big problem,. Once i turn on Bluetooth, i am not able to dissable it. Every time i try to switch it of, it turns on itself short time after again. I think it is the so called "cant't turn oft issue". But i cant find a solution to fix this. Actually Bluetooth is always in in my Device. But i dont need it.
Any help would be great
Best regards
Litreb
problem accessing internal memory
guys, i have some problem after intall this ROM. first step before install this room , i do wipe data and cache from boot recovery and install via CWM. but after finish installing, when i try access data in the internal memory, i got empty data, i think all data in teh internal memory has been formatted. But.. when i try to installing once again, when using option select zip from internal memory, all folder in the internall memory has appear. so i canceling to install and try to open data again, but the internall memory was empty, different when i looking from recovery mode before.
so. is it normal? how i can access again data that doesn't appear when open in normal mode? thanks a lot
Bluetooth problem
Hi there,
I was reading for years until I yesterday decidet to flash (from stock) to this rom.
All went fine (besides a corrupt backup, sh. happens)
All seems to work besides: bluetooth.
I thougt there should be no Bluetooth issue with this rom?
I can turn BT on or off, but the Tab doesn't find any bluetooth device.
I canNOT turn on its visibility for other devices. Its not found by eg. my pc.
Anyone who had the same problem?
With stockrom it worked all fine, no hardware change.
THANK YOU - to anybody who finds some minutes to care about a newbie
dvorak104
This Build work well except Bt
I installed the 12 december version with opengapps nano GAPPS package. But I get a horrible wakelock on google play services, no matter what I try. I can't seem to track it down or solve it.. (tracked it down with Wakelock Detector, GSAM Battery Monitor). It's preventing deep sleep. Any tips?
Tab 7.7 CarbonRom KitKat starts automatically when charging
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
memunnik said:
Hi,
I've installed [ROM][4.4.4r2]p6800/p6810/i815(12Dec2014)CarbonROM Kitkat Unofficial on my tab 7.7. with TWRP recovery project 3.0.2-0. Although everything seems to be working fine, except known issues, I have one issue. When I turn off my tablet and start charging, my tablet automatically starts/reboots after a minute or so. Is there a way from preventing this automatically reboot when charging, while I my tab is shut down? I want to charge my tab turned off because it will charge much faster. I've been looking around for same issues of different devices and possible solutions but nothing seems to work for me:
- Disabeling Stay a Wake while charging.
- Turn off while charging cable is already connected.
- Switch to original cables, chargers or not using data cable
- Can't edit LPM, PLayLPM, IPod, etc., because I can't find such battery animation file
#!/system/bin/sh
sleep 40 (Maybe I can change the amount of time to boot while charging, e.g. to 100.000)
/system/bin/reboot
- Delete Cache and Data-storage.
- Maximize CPU Frequency to max. 1400 Mhz.
Can somebody please help me and find me a solution!?
Click to expand...
Click to collapse
The automatic reboot when charging was a bug in the old Kitkat Rom's that Daniel fixed with Android Lollipop rom's, its a feature of those builds.
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon
I'm running my OnePlus One and I've had this issue since the first CM12 update to Lollipop, but with the recent OTA claiming to have fixed "Bluetooth" issues and this still isn't fixed I'd really like to know if theres a solution.
Basically I have an aftermarket Pioneer headunit. When I start the car and it attempts to connect to the phone, the phone takes almost a full minute before it connects. Prior to lollipop it would connect in 2-3 seconds.
I stream music from my phone using Spotify and Google Play Music, using either has tons of stuttering over Bluetooth. Atleast once every minute or so, it will stutter for a second or two.
And finally, the radio only ever sees the song information for the first track that plays from when the phone connects. Skipping songs, restarting the app won't change the song data that's being sent out. The only thing I can do to update is to restart the phone and it will get stuck again. This is by far my biggest gripe because it worked fine on KitKat and JellyBean for me on CM11.
I really like Lollipop but neither CM12 or OxygenOS has solved this issue for me. Right now all I can think of is just flashing an older CM11 rom but I'd like to know of any alternatives, whether that be a different ROM or whatever. I've also read up that someone just flashed an older CM11 radio/modem onto CM12, but I don't know if that was a solution, there was no follow up post.
It does this with nearly every aftermarket radio I've paired my phone with (friend's cars etc.)
Details:
OnePlus One
CM12 YNG1TAS2I3
TWRP Recovery / Rooted.
I just got a new 2015 VW Golf and a new Moto G. Before the Moto G, I had a OnePlus One and it was having this problem as well. It's actually the reason I ended up with a new Moto G, because after two weeks or so of troubleshooting I couldn't figure out what was causing the problem. Immediately upon pairing the Moto G it's been having skipping/stuttering issues with Spotify and Youtube.
My first thought was that it obviously must be an issue with the car, but it isn't, as I've tried many different phones with the car (extensively) and they all work just fine, with the exception of the Moto G (2015) and the OnePlus One. I'm at wits end after having spent so much time on this issue.
Seems to be a compatibility issue between certain phones(or software) and this car(or multiple cars), but that some work just fine. The phones seem to work fine with other bluetooth devices, but just not this one.
On the OnePlus One here are some of the things I tried (there were a lot so I can't possible remember them all):
1. Repaired bluetooth
2. turned off wifi.
3. turned off bluetooth contact sharing
4. restarted device
5. hard reset
6. wiped data and cache in recovery mode
7. reinstalled spotify/wiped app date and cache.
8. toggled nu/awesome player in developer options
9. rooted/unlocked bootloader and flashed many different roms, some with CM12 base and some with out. I had heard Oxygen OS had less problems, but still didn't fix the issue.
10. Tried the ro.bluetooth.request.master=true fix in build.prop
11. av.offload.enabled=true to false
Is anyone else having this issue? There are a lot of vague threads out there about other phones and streaming issues via bluetooth, but I'm not sure what applies to this phone or what doesn't.
Some basic troubleshooting done on the Moto G
1. Repaired bluetooth
2. turned off wifi.
3. turned off bluetooth contact sharing
4. restarted device
5. hard reset
6. wiped data and cache in recovery mode
7. reinstalled spotify/wiped app date and cache.
8. toggled nu/awesome player in developer options
Any help would be great. Might just return the device if I can't get it working.
yeah, I have the same issue. Data and cache wiping in recovery mode sorted out for a couple of months but now I am getting the stuttering again. I use Bluetooth for all my listening and I hate this bug.
I have the same problem on my Moto G. Seems like some CPU/RAM issue since I've notice it got worse when I try to use any other program with spotify. But it's good to know that other ROMs don't work. I was about to test that.