Make Your Own Heat Sink for the LG Optimus 4X HD

Its not a rare occurrence that performing a resource heavy task on your Android device (e.g. … more

Learn How to Create an Old School Dialer

XDA is not only a great source for custom ROMs, kernels, and various modifications for numerous … more

USB Desktop Charger Roundup – XDA TV

Sometimes you learn one way to do something, and that’s the way you do it forever. You never … more

Samsung Galaxy Grand Duos Receives Early CM12 Port

Samsung Galaxy Grand is a dual-SIM phone with a 5 screen that was announced two years ago. … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Bluetooth stopped working....

OP death_entry

2nd June 2014, 08:20 PM   |  #11  
OP Senior Member
Flag London
Thanks Meter: 28
 
266 posts
Join Date:Joined: Nov 2006
More
Quote:
Originally Posted by cosurgi

I worked! Thanks

Yep that fixed it for me too

Wonder why quick boot knocked it out lol....
2nd June 2014, 08:39 PM   |  #12  
Senior Member
Thanks Meter: 15
 
139 posts
Join Date:Joined: May 2006
Easier than a hard reset!
2nd June 2014, 10:09 PM   |  #13  
Senior Member
Thanks Meter: 118
 
563 posts
Join Date:Joined: Nov 2013
Quote:
Originally Posted by death_entry

Yep that fixed it for me too

Wonder why quick boot knocked it out lol....

Quickboot didn't knock it out. The defective TrueSmart MTK firmware and hardware combination cause all sorts of problems with using Bluetooth, including some that require a full power cycle reset. That is not possible with Quickboot enabled unless the battery runs down or is removed.

Sent from my Nexus 5 using Tapatalk
2nd June 2014, 10:37 PM   |  #14  
funky0308's Avatar
Recognized Themer
Flag Osijek
Thanks Meter: 5,537
 
6,782 posts
Join Date:Joined: Aug 2012
Donate to Me
More
Glad to see your BT and TS are working fine now...

All el devices could be "fixed" by restarting it.
They are all using RAM and/or dalvik cache and that has to cleared sometimes...
Dalvik cache is a "place" where Android decompile apk files for quicker access, so when you wip dalvik cache from recovery you are clearing everything so system has to decompile apk files again and RAM is cleared also...

It's like fresh start and it "fix" many software issues that way...

If you have ADB tools and rooted device, you can use adb reboot from adb shell, no need to open your watch, lose warranty and pull battery out...


Sent from my C6903 using Tapatalk
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes