3 replies to this topic

[debonu]

Morning all,

Long time lurker of most things regarding the Bionic. I have been running .232 leak since it came out and I had a few bluetooth issues and a play store issue. So I pulled the trigger on .247 using the HoB without any issues with the hopes that these problems would be solved in the new leak. Unforetunatly they were not... So I'm hoping someone may have some experience with these that can give me a hand trouble shooting and fixing them.

The bluetooth issue is a connectivity issue. I connect my DB to my Subaru Impreza's head unit using bluetooth in order to stream music and obviously for phone calls. Since the .232 update though I am having an issue with the DB randomly disconnecting itself mid stream/call from the headunit. It will stay disconnected for a little bit and then reconnect and pick up where it left off. Very annoying to deal with when trying to hold a conversation or unwind to some music!

The play store issue I'm having is while trying to do multiple app updates. Whenever I have more than one app update in the list and attempt to run them all my DB will download the first update without issue and then sit on "downloading" for the next app. Until I exit out of the play store and go back in or cancel all the updates and start again. Then it just does the same thing until I basically manually install all of the updates. Bringing me back to the old school days before auto updates!

Any help with either of these issues would be greatly appreciated!

Thanks
-D

[kickbutkuss]

Try a factory data reset. This approach has corrected many issues with the various leaks.

[johnlgalt]

Agreed. Going from .232 to .235 I ended up having issues after I got everythign sorted out with the testing and whatnot ( trying to revert .235 back to a working .905 install). When I finally got things fixed, I tried restoring data from TB into .235 several times - I foulnd that I finall had to start all over again, from scratch.

The good news is that, since .235, I have yet to perform a factory reset and all other leaks since then have had no issues.

Since you're coming to .247 directly from .232, a factory reset is highly recommended.

[KenDroid]

I cannot for the life of me get wifi tether working with .247. I thought I changed a setting so I did a full restore with all the wipes and that did NOT fix it. I tried reinstalling FoxFi and it did not work either. I used SQLite to edit the settings and that didn't fix it either. I never had a problem on .902, then on .905 I had to start FoxFi then stop it and start it again. I went straight from .905 to .247 and it's just plain broken. I don't want to go old skool and use PdaNet again, but it looks like my only option... unless someone knows something I can do to fix this

Ok... *the edit*

I uninstalled and reinstalled foxfi, even tried to do a restore of .247. Retried foxfi/stock wifi and wifi w/root and it still would not work. Another forum had a lengthy discussion about this same issue, some people have no trouble and some are just scratching their heads. I tried everything I found from that site and it still did not work (including ROM Manager fix permissions, changing SSID/passcode, uninstalling, rebooting a few dozen times etc.) until at last... it would allow me to connect with the laptop but no internet. From there, I uninstalled all my wifi tether apps, rebooted. ROM Manager fix permissions, reboot. reinstall foxfi, reboot. I kept droidwall turned off and *poof*, internet access. As soon as I enable droidwall, I lose it. I just need to know which of those processes foxfi is using to connect the data to the phone under because just allowing foxfi past the firewall is not enough. Having said that, I can use it but I have to keep droidwall turned off. I checked the log and cannot tell which process is generating the connection, it says something like APP0/1((applications running as root)) then gives my laptop's IP address, but allowing applications running as root through the firewall still cuts internet off to the laptop. *sigh*