Search results

Oh boy, i hope somebody can help out here... A friend of mine owns this S7 Active, bought in 2017 in ebay. Up to now he did not receive any update, nothing came ever via OTA. Now he starts to be disappointed that he sticks on Android 7 and does not get 8, although there are hints that this...

Thanks for the information ! I had a Samsung S4 with exact the same trouble. (running 5.0.1 original Samsung ROM) Did delete Media Storage Data and restarted the phone. After that the display via MTP was fine... no need for SDrescan. I did know already about the fact that i can restore...

No, BT with Smartwatch and running permanent communication with run.gps fails after few seconds. Then, after stoping the apps on smartwatch and S4 the S4 says "BT stopped" or similar. This was tested with 20151221, dirty flashed over 20151203. I'm back on old version and exchanged file...

Well... i did not flash both files, i did extract libbt-vendor.so from the BT-Fix-File and stored that (with root-permissions, with ESFileExplorer) to system/vendor/lib/libbt-vendor.so. First disable BT, reboot, save the original file, then overwrite it with the file from the fix. Then reboot...

Because of the BT-Issues i did apply the fix again: http://forum.xda-developers.com/showpost.php?p=64022298&postcount=1872 Again, this works perfect. Was running for more than 1 hour with active smartwatch, and there was no problem in BT-Communications.

Funny.... i am having BT-Problems again, and i did not change CM or Gapps, i did not flash anything. I am running on 20151203, and i am using BT for car-handsfree, for data-synch with a notebook, and for communication with smartwatch. Now, after 2 weeks without any issue, the crashes of BT...

Now, after several days of using... i did have 2 crashes with BT. Which is much less then i had before. After stopping bt-share-service, and restarting BT, i immediately get a message: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint...

I started with clean install on cm-12.1-20151107-NIGHTLY-jfltexx & tk_gapps-modular-nano-5.1.1-20150920-signed. Did run some time with that combination, and then updated CM. Dec 01 and then Dec 03

Looks good so far.... now running with my Smartwatch and without manually exchanging files by myself.... I'm happy :)

Now i am convinced.... did not reboot the S4 or smartwatch since i have exchanged that file, and still having rock-solid connection. Yesterday i used Run.GPS while running, which creates a constant BT-data-flow from the S4 to the watch in order to display heartrate, time, distance. In parallel...

see post 1872.... was running around with BT activ, Smartwatch connected, several times handsfree in car connected. 2 times i used music-streaming via BT from the S4 to the car. Started Navigation via "Ok-Google" and did have handsfree connected in parallel... everything worked perfect. That...

I'm starting to get happy... carefully.... have paired with Samsung Gear Live and did never have such a good BT-connection with the phone... you me be my hero of the day :cool: - I found the corresponding post in the opt-thread... the best keyword for searching is "libbt-vendor" - i did not run...

Wow... that's a hint which i will try as well... what exactly did you do? Tried to search in Opt-Thread without success...

Yes. Have selected a mp3 for all, ringtone, alarmtone, messagetone......

All this is what i am experiencing also. The crash with handsfree is in my case also related to transferring contacts-information and call-log.... if you clean the call-log that also helps... for a short time. After buying a smartwatch, which heavily uses BT, things got so worse that i did have...

Today i had some time to test Bluetooth-Issues with Smartwatch,... here are my logs. I hope they can help: I'm currently on an other ROM with quiet good working S4 & Samsung Gear Live, but since i really would like to come back to CM... these are the steps i did: - Went into TWRP and did...

Whenever a log is needed because of stalling BT-Communication with Smartwatch, let me know, i'm ready to clean reflash CM, add GAPPS of your choice, install AndroidWear and let it run. My proposal would be 20150919-nightly, TK-Gapps nano 20150919, as somebody here said that is a smooth running...

Is Baseband also responsible for Bluetooth?

See... and that is exactly the reason why i would like to get advice, which setup to use, before creating a log.

I do not know... but the LG did show the exact same type of errors. Also the bluetooth-crashes indicate a bluetooth issue. Also that the connections to the handsfree to the car is now a little bit more stable..... all this points to bluetooth. Today i am running on "S4 JFLTE-GPE 5.1 by Danvdh"...

I am having issues with Bluetooth.. Long time ago the connection to PC and to handsfree in the car was fixed with an update... but still, let's say 2 times a week, Bluetooth crashes when connecting to car. That is not a big issue to me. But now i am trying to work with Smartwatches again, and...

I have seen your advice to use smartlock to disable lock in wifi-networks... and on my S4 i can only use Bluetooth / NFC for smartlock. Did i understand that wrong, or am i missing something?

I also do not see carrier-name on that place... and i wonder if i did ever see it on that place.

What exactly is the content of these gapps? They say "only basic stuff"... what would it be compared to the old "PA-Gapps" here http://forum.xda-developers.com/android/software/reborn-gapps-5-t3074660... the Pico, the Nano Version?

Interesting, as i am on 20150713 nightly, and the BT-connections are stable. Even after 2 or 3 days, connecting to car for approximately 10 or 15 times, the connection is always active and working. Before that i also had BT-crashes, after one update BT-Deepsleep-Issues, and now after switching...

NZgeek: Thanks for the internal details. Will there be a fix, at any time? Or is this the permanent solution for BT-Issues? I am glad that BT-Issues were fixed, since days i did not have issues with that, where in the past i had to restart BT-services many times per day. But i am not used to...

Have now disabled MPE, which listens permanently to Bluetooth-Connections. Still no DeepSleep with BT turned on. Battery consumption down to 2.8%.... with older version and DeepSleep i used to have lower consumption. But definitly a change in Bluetooth, had not one crash from BT any more. Can...

With BT on (and no DeepSleep) i have 5%/h batteryconsumption. Usually, before this build, i was around 1%. But the good thing is: I did have not one BT-crash after installing the 20150629 nightly... keep fingers crossed :)

I switched to 20150629 nightly. For me it looks as if i do not have DeepSleep any more, if BT is activated. But the phone is not getting hot at all, and first impression is that it also does not show a heavy battery consumption...

Had 2 BT-crashes since my last post, and killing the BT-Share as described by mikshepard did work well for me. This night i had BT-Wakelocks activ, which did prevent DeepSleep, hope that this is also gone with that procedure... then i could at least avoid rebooting the phone. Nevertheless...

mikshepard: Thanks, will try. android_patrizian: Thanks for the absolut useless post. Yes, i did read the posts of the last days, i did read the whole thread. Yes, not everybody has this issue. But yes, more than one has the issue. Please re-read my question. Will try to explain in more...

Did flash version 20150609, hoping to get some healing for BT-Issues. But BT service stopped very soon when using BT for communication with MyPhoneExplorer. I would appreciate if someone could tell if this kind of issues are known, being worked on, or are in plan, or need more information like...

I now have 2 occurences where Bluetooth crashes regularly: - when connecting to car handsfree, at start, when call-logs are transferred. If bluetooth survives that action, then using bluetooth for phone activities seems to be fine - when synching contacts via bluetooth between the S4 and a...

Not here. Weeks ago BT became unstable and has not recovered since then, - when using Smartwatch - when connecting to hands-free in car I stopped the usage of Smartwatch because of this and did return the watch to the store (was not sure at that time, who of the two created the issue)...

My bluetooth-problem still exists. Trying to connect to car and then Bluetooth dies and can not be switched on again.

Vibration only once for each incoming call: Same here. Running on V 12.1 from April 22nd.

Seems as if i have managed to work arround the Bluetooth-Crash (which i did have whenever i connected to my car). Have seen that suggestion somewhere else: I did delete all call-logs. Obviously the first thing, the car wanted to download, after connecting, was the call log, where i did have...

BT issue also here. Almost every time i connect to my car, the S4 stucks, and then BT stops. Can't be switched on again, i have to reboot the S4 completely. I assume, there are a lot of logs available already, let me know if you need another one.

Have searched this forum since 2 days now, but was not able to find answer, instead i found different statements making me even more unsecure, what happened, and what are my next steps. So here is my story: Have used Unlock-Bootloader procedure on HTCDEV, which worked fine. My goal was to use...