4 replies to this topic

[scottyb1to3]

Hello all, 

 

First off, I'm a noob to the forums.  Usually I don't post to forums because I can find almost everything I need to know by hours of searching...unfortunately I'm frustrated.  If I'm missing some vital information please let me know!  My expertise in Android phones and Roms could be classified as an "Expert Novice" or simply put an "Intermediate" user.  

 

I've been happily using the Liquid Smooth Rom for a few months.  With every update I am becoming happier and happier.  Up until a few weeks ago everything was fine until I flashed v2.7.  I then noticed my bluetooth was permanently locked to the off position after I reboot the phone.  In order to get it back I either have to re-flash the rom or use Titanium Backup to restore.  I then flashed v2.8 in hopes that it would fix the issue but the same results occurred.  I just recently did a clean flash but the same results are happening.  

 

I have found some articles about this issue happening with some Samsung phones doing this as well with JB....JB being the culprit.  Is this the same with the Razr?  Or should I just be patient and wait for the next version that hopefully fixes this problem? Anyone else having this problem?

 

Any expert advice will be greatly appreciated!

 

 

[livinginkaos]

Some Bluetooth and GPS issues are solved by installing a stock ROM and activating them then go back to your ROM of choice. Have you determined that this is or is not ROM related? Perhaps asking in the Liquid Smooth thread might bring profit?

[scottyb1to3]

I believe it is ROM related because it works fine on the Stock ROM.  I have just tried your suggestion on activating bluetooth on the stock ROM and switching back to the custom ROM.  You are correct, this might be a good issue to bring up in the L. Smooth thread.  Thanks for your help!

[robocuff]

This is (well, seems to be anyway) a problem with all of the AOSP based roms.  At least it is for me.  Anything AOSP, AOKP, or CM based seems to have this problem.  I've messed around a bit with this on Dhacker's and Hashcode's AOKP rom.  Can't say for sure (not sure if if I've tried enough times) but after several reboots, it seems to me it only occurs when I reboot (or shutdown) with bluetooth enabled.  If I disable it before I reboot, it seems to work as it should once booted up.  If I leave bluetooth enabled and reboot, I can't get it to start once the OS is booted.  

 

What I do to get it to work again is boot to safestrap and wipe cache and dalvik.  Works for me every time.  

 

If you haven't already done so, perhaps you can experiment a bit and see if this is the answer for you.  If so, I don't know what the permanent fix is.  All I can tell you is to disable bluetooth before rebooting.

[scottyb1to3]

Thanks for the input robocuff: After reading your post I tried rebooting after disabling bluetooth and the same problems persists.  However, I seem to remember you are correct and it has worked as you described in earlier versions which leads me to believe it is a version issue.  I also tried your suggestion with the cache/dalvik wipe and it works...sometimes.  If it doesn't I just need to re-flash which takes a little longer but nothing unbearable.  Overall I am happy with the ROM, appreciate the work of the developers and accept the need to adjust accordingly.  Again, thank you to those who have helped with this problem.  I'm just happy to know that this is overall problem with these ROMS in general and not an individual problem.