Related
Hello Everyone.
I'm new to the forum and this is my first post, although have been reading and applying a lot of knowledge you guys have! the forum is great!
Anyway, I have an unlocked HTC TyTN II, everything worked fine and I overall very satisfied with the device...
I made a foolish thing! I installed the "Wefi" utility and after playing with it for a little while, I didn't like the thing.. so, I decided to uninstall it.. however, now I find that my kaiser cannot longer connect automatically to my wireless networks after resume.. Now I only get the notification that it has found available wireless networks and, even though I chose not to show the message anymore, it does it every time, and when it does not, the phone doesn't connect to my WiFi.. so I need to do it manually... which is very annoying..
I already restored original registry keys under HLM\Comm\TNETW12511\Parms with no luck so far...
What can I do?... I'm still on the original WM 6.0, have not loaded any ROM changes yet..
Your help would be highly appreciated.
Thanks!
Oscar
Fix for auto connect problem after removing WeFi
My name is Galia Finkelstein and I work at the support desk at WeFi. This doesn't happen anymore on the new version that's been released so for the older version we have a version fix for the problem with the automatic connection, just run this file and you should be good to go http://wefi.com/static/RestoreZCAutoConnect.exe
If I can assist with anything else please drop me a line at [email protected].
WeFi post-uninstall problems
Hi!
I am sufferring from the same problems as "obadillo" - see above.
I downloaded and installed the latest version of WeFi, but after a couple of days of use, I found that I didn't like it, and it also took up too much of my valuable "today" screen space.
After uninstalling, I found that firstly, all my previous wi-fi settings had been lost (WEP keys for my home network, my work network etc etc), and secondly, even after re-enterring these details, my device (HTC Touch UK Version - Orange UK) - (running WM6 Pro) refused to auto-connect when I switch the WiFi on.
After reading the reply from Galia (directly above my post), I downloaded and ran the executable, but found that it made no difference.
Any ideas anyone? I did email Wefi's support email address, but as yet have received no reply.
Thanks in advance!
I have also tried this fix with no success (running WM5). I have also sent an email to wefi support. No response. I would recommend you stay away from this software.
We-Fi Latest Version
I have found a (kind of) solution! I have installed the latest version of We-Fi (downloaded from their website), and then DEselected it in my Today programs. So even though its not in use, its wifi parameters still overrule the PPCs local params. This seems to allow me to switch on and off WiFi WITHOUT using the WeFi software, and it now autoconnects, even with the several wireless networks I have stored, whenever I switch WiFi on, it may take a few seconds to connect, but it now does every time.
Not the greatest "solution", but at least the problem is partially solved.
But as the good man above says, unless you're VERY sure you want to install WeFi, do not install, because you will lose ALL preexisiting WiFi connections and settings etc..
Have a good one!
-=namwollem=-
Hello again, XDA devs!
I also had the problem and I'm struggling with Amir, some guy from the WeFi staff, to get the problem solved or at least recognized.
I left a complete description on my blog with links to people having problems. Here's the article (without links):
Before you consider installing WeFi on your Windows Mobile device, you might want to read this cautiously and save yourself some problems.
If you have not yet tried it, you're not missing much. Although promising, the app takes over your device. It controls your today screen, messes up your wi-fi parameters and some rarer stability issues were also reported.
First, the app needs .Net CF v.2.0, something that takes space and puts more useless crap on your device. Then the app doesn't just find networks and connect to them. Instead it overrides your wi-fi parameters and inserts its own code, thus the uninstallation problems. WeFi also takes a lot of your today screen's estate for basically nothing. How much screen space? Take a look.
Upon uninstalling it, many noticed their devices stopped automatically connecting to wireless networks, among other, rarer problems. The only known fix to the problem is to hard-reset your device and to stay the **** away from this app. We also saw a link to a .exe file somewhere but no one left feedback about it so we assume it's just as good as WeFi. You might also reinstall it, hide it and use it to take care of the wi-fi stuff or go in Settings>Connections>Wi-Fi everytime to select a network to connect to.
The developers were quick to comment about the problem and said they are working on it (see the first comment to this post). However their product page doesn't mention the problem yet and people still get caught. I left them feedback about *some* of the concerned device, assuming it's not all of them, hoping for a change. Feel free to do the same and put some pressure on these guys too.
You might also read one of those threads and see for yourself.
-Nico
Click to expand...
Click to collapse
Full article: http://nicbou.com/2008/07/09/do-not-install…-you-pocket-pcdo-not-install-wefi-on-you-pocket-pc/
I'm trying to get the warning to reach all the download spots, if you guys feel like helping. This is just unacceptable, let's do something about it!
Haim head of WeFi Windows Mobile development team here
Hello all,
First, let me assure you all that we are doing our best to solve any user problem as quickly as possible.
Out of the thousands of mobile users we have, there are really only a few users who complained about this problem.
We released a fix that you can find in: http://www.wefi.com/download/client/RestoreZCAutoConnect.exe
which after executing and doing soft reset should solve the problem.
As our support team explained to “primemaps” via e-mails (sent in 08/07) this fix only works if you uninstall WeFi first.
What you are all describing is that ZeroConfig stopped auto connecting.
By avoiding the manipulation of ZeroConfig default timeouts in our next version (which should be released in about 2 weeks from now), this should not happen anymore.
If this does not help you or you have encountered any other problem – please send me an email to [email protected] and I promise a fast response,
it would help if you mentioned your WeFi version, Device model and ActiveSync version.
I hope you would all choose to install our next version and enjoy the many benefits it can bring you.
Haim
Can't work with it and can't work without it
With my HTC TyTN II I had similar problems as others have described, or maybe even worse: I could no longer work to any wireless networks. It would disconnect in less than one second every time.
I did a hard reset and that didn't work!
I also tried the "fix" the WeFi representative suggested but that didn't help at all either.
What finally helped me was Namwollem's solution: Install WeFi again and removed it from the Today screen (but kept it installed).
I can't help wonder if WeFi changes something in the ROM since a hard reset didn't even fix it.
One of these days I will have to install the ROM all over and see if it makes a difference, but I wish I could avoid that!
I hope others won't be stupid like me and install this #$%[email protected]#&$ software!
Nothing helps for my Diamond to restore Wifi signal
I have Htc diamond with newest Rom downloaded from htc.com.
My problem is that since i installed aplication WEFI(older version) and uninstalled it, i cannot see ANY available wifi networks.. I tried alot of things. I tried soft reset, hard reset, i installed WEFI (newest version) , in moments wifi works and shows available networks and i can connect, but after it doesnt work again.. I would say it shows networks only ocasionally(even if im always surrounded by at least 10 hotspots). I installed newest Rom again, i installed old official ROM, i always put mamximum performance instead of battery, and still i have no results/cannot see ANY available networks). I have a feeling like i really have a hardware problem with wifi now..But again i think whatever it is its caused by this aplication WEFI. Does anylone have any ideas? i saw some Rafael radio ROM , maybe i can try to install that?
Thanks
AArrrggghh!
This god-awful program rears its ugly head again! I have solved the problem totally now by getting a new handset!! Now I have my Touch HD (Blackstone), one thing I WILL NOT do is install this garbage!! A quick search thru the forums here will reveal a small and very useful program which will with one click switch-on WiFi (and auto connect to the signal it finds if stored in your preferred networks) and with another click will switch WiFi off! Its called AKWifiToggle, and while no where near as fancy as WeFi, IT WORKS and DOESN'T MUCK UP YOUR PHONE!!!
Hi guys,
After many hours and days of searching google for a solution to this I'm still stumped.
I have a Galaxy S i9000 running Gingerbread 2.3.3 (had same problem with previous versions also) and I am trying to connect it to my Nokia 616 car kit in "hands free" mode, however, it keeps automatically connecting via "remote sim mode". I can confirm there is no way to disable rSAP (remote sim mode) through the nokia 616, nokia staff were not very helpful either.
There was an option in my old Samsung Jet (i think it was running touchwiz) bluetooth settings which allowed me to switch remote sim mode on and off. The only setting that exists on my SGS is after I connect to the nokia 616 i get the "Deactivate Remote Sim Mode?" option from the drop down bar... However, when I do so, the connection to the car kit is lost and upon reconnect it automatically connects using "Remote Sim Mode", regardless of how many times i try an "deactivate" it...
The only posts I could find about deactivating remote sim mode tell me to hit "Yes" to "Deactivate Remote Sim Mode", then to switch bluetooth off and then on. This does not solve my issue. Problem persists.
The only thing I can think of now is somehow finding perhaps a command line instruction that I can run from terminal to disable remote sim mode or even change a config file somewhere to deactivate it.
Does anybody have any idea how this can be done or maybe just give me a lead on where I can search next, I've hit a dead end with this now and im sure it can be done, somehow.
Thanks heaps for your help.
I'm sorry I cannot help you with this problem, but at least you're not the only one: I have exactly the same problem, but then with a Nokia 616 and a Galaxy S2.
I want it to connect with the normal HFP, so I do not loose the internet connectivity on my phone...
SOLVED Finally!
So after a while of searching then giving up, then contemplating ripping out my nokia 616 car kit and setting it on fire, I decided to revisit this issue and here is how I managed to disable/remove/deactivate remote sim mode or rsap... please note that I havnt really tested to see if this affects any other bluetooth functionality (i dont think it does though) so do at your own risk...
I ended up flashing my galaxy s with Darkys rom 10.2 extreme edition which gave me some nifty options of removing some stock bluetooth apps... I noticed there were a number of bluetooth related apps there, Bluetooth.apk , BluetoothOpp.apk, BluetoothPbap.apk, BluetoothTestMode.apk and the devil himself BrcmBluetoothServices.apk... at first i uninstalled them all except Bluetooth.apk, my phone starting throwing some bluetooth error which was expected, these errors disappeared after I rebooted the phone... I noticed that the 616 no longer connected using rSap (victory!), however, I was almost certain that not all of the apps i removed above would be causing the issue, and im sure that if anything having them removed would cause issues elsewhere so the process of elimination began... I reinstalled them all again, rebooted my phone, sure enough remote sim mode was back, then one by one i uninstalled, rebooted, tested, etc etc untill i came to the conclusion that the app responsible to rSap was in fact BrcmBluetoothServices.apk, after uninstalling it and rebooting Hands Free mode works a treat, I still get a "download error" when i try to download my contacts to the 616 but Im not to fussed about it, at least i can still use all the functionality of my phone in my car now, internet etc etc... as mentioned earlier I dont know if this will have any effect on the other uses for bluetooth so do be careful, not a huge issue because it can be easily reinstalled if nessecary using DarkysRom Tool...
Now I am sure this can be done on a stock firmware, you would most definitely need to root the phone and then find some sort of system app manager to hunt down BrcmBluetoothServices.apk and remove it...
Thats it! If anybody can work out how to successfully download contacts to the nokia 616 please post it here or pm me.
For some strange reason, Spotify no longer seems to recognize my phone's internal storage. I'm unable to listen to the radio and the following error pops up: 'No SD Card Found: We found no place to store our data, please check that you have a working SD card and free space". This started occurring after I upgraded to Mike's ARHD 10 (and remained after I upgraded again to 10.1). I tried Googling the issue, but couldn't find a single instance of anyone facing a similar problem. I'm fairly certain the rom is not to blame since no one else mentioned anything related to this--plus, the rom has been awesome thus far (just like Mike's earlier versions). I tried fixing permissions, and even re-installing rom after performing a full wipe. I also should mention that after uninstalling then re-installing Spotify, the app seems to run fine for a little while--but the error will rear its ugly head again after I try to open the app again at a later time . Also, I am able to access my internal SD card without a problem via ES File Explorer and everything looks about right when I go to Settings > Storage.
Any help would be appreciated
I get the same message when trying to start Spotify on my stock Gnexus. All other apps using internal storage works fine.
I have now uninstalled and reinstalled Spotify and for now it works fine, but I have to download all offline lists again
Zuluboy87 said:
For some strange reason, Spotify no longer seems to recognize my phone's internal storage. I'm unable to listen to the radio and the following error pops up: 'No SD Card Found: We found no place to store our data, please check that you have a working SD card and free space". This started occurring after I upgraded to Mike's ARHD 10 (and remained after I upgraded again to 10.1). I tried Googling the issue, but couldn't find a single instance of anyone facing a similar problem. I'm fairly certain the rom is not to blame since no one else mentioned anything related to this--plus, the rom has been awesome thus far (just like Mike's earlier versions). I tried fixing permissions, and even re-installing rom after performing a full wipe. I also should mention that after uninstalling then re-installing Spotify, the app seems to run fine for a little while--but the error will rear its ugly head again after I try to open the app again at a later time . Also, I am able to access my internal SD card without a problem via ES File Explorer and everything looks about right when I go to Settings > Storage.
Any help would be appreciated
Click to expand...
Click to collapse
anwigr said:
I get the same message when trying to start Spotify on my stock Gnexus. All other apps using internal storage works fine.
I have now uninstalled and reinstalled Spotify and for now it works fine, but I have to download all offline lists again
Click to expand...
Click to collapse
Thanks for the response. I started to receive this error (fairly recently) when I installed or updated my current rom. I got tired of having to keep re-installing the Spotify app, so eventually I went into Settings and decided to 'Delete cache and saved data' for the heck of it. This might not exactly be a feasible option for those who have a paid subscription and actual saved data, but I have yet to receive the same error again. :highfive:
Zuluboy87 said:
Thanks for the response. I started to receive this error (fairly recently) when I installed or updated my current rom. I got tired of having to keep re-installing the Spotify app, so eventually I went into Settings and decided to 'Delete cache and saved data' for the heck of it. This might not exactly be a feasible option for those who have a paid subscription and actual saved data, but I have yet to receive the same error again. :highfive:
Click to expand...
Click to collapse
Same issue here on my S4 (found this thread through the Spotify community... funny how us XDA members always end up troubleshooting products, lol). I was on Slimbean and thought it was the rom. Restored my stock Nandroid and got the same error a few hours later. Apparently, this will happen again later. Just wanted to chime in with my experience.
Same on HTC One. Put Sentinel rom on over the weekend, re-downloaded all my playlists and it worked fine on Monday...this morning, get the SD card message.
I was looking at where all my space was last night since I put Sentinel on and there was about 1.5gb in a Spotify folder under sdcard/data...the folder has gone.
I will re-install Spotify and see what happens.
AngelosDracul said:
Same issue here on my S4 (found this thread through the Spotify community... funny how us XDA members always end up troubleshooting products, lol). I was on Slimbean and thought it was the rom. Restored my stock Nandroid and got the same error a few hours later. Apparently, this will happen again later. Just wanted to chime in with my experience.
Click to expand...
Click to collapse
You should contact Spotify for support, you pay for it afterall.
godutch said:
You should contact Spotify for support, you pay for it afterall.
Click to expand...
Click to collapse
It's been my experience in my past two and a half years here at XDA that the developers of ROMs and homebrew usually find a solution before the actual app developers do. In this case, there was a thread in the spotify support forum. That led me here. *shrug* it's how we do.
AngelosDracul said:
It's been my experience in my past two and a half years here at XDA that the developers of ROMs and homebrew usually find a solution before the actual app developers do. In this case, there was a thread in the spotify support forum. That led me here. *shrug* it's how we do.
Click to expand...
Click to collapse
I come to XDA to find workarounds but when I pay (subscribe to) for something I expect the devs to work on a solution, I think the people working at spotify would like to hear about your problem too, because you can help them but many other people would just give up on them...
I had a problem too and contacted them, they are friendly and responsive
godutch said:
I come to XDA to find workarounds but when I pay (subscribe to) for something I expect the devs to work on a solution, I think the people working at spotify would like to hear about your problem too, because you can help them but many other people would just give up on them...
I had a problem too and contacted them, they are friendly and responsive
Click to expand...
Click to collapse
I always go directly to them. And I did. However, posting in multiple places never hurts. if you read my original post, you would see I found this thread from the Spotify support threads.
AngelosDracul said:
I always go directly to them. And I did. However, posting in multiple places never hurts. if you read my original post, you would see I found this thread from the Spotify support threads.
Click to expand...
Click to collapse
ah you did but you can also email them directly for support
spotify problem
Zuluboy87 said:
For some strange reason, Spotify no longer seems to recognize my phone's internal storage. I'm unable to listen to the radio and the following error pops up: 'No SD Card Found: We found no place to store our data, please check that you have a working SD card and free space". This started occurring after I upgraded to Mike's ARHD 10 (and remained after I upgraded again to 10.1). I tried Googling the issue, but couldn't find a single instance of anyone facing a similar problem. I'm fairly certain the rom is not to blame since no one else mentioned anything related to this--plus, the rom has been awesome thus far (just like Mike's earlier versions). I tried fixing permissions, and even re-installing rom after performing a full wipe. I also should mention that after uninstalling then re-installing Spotify, the app seems to run fine for a little while--but the error will rear its ugly head again after I try to open the app again at a later time . Also, I am able to access my internal SD card without a problem via ES File Explorer and everything looks about right when I go to Settings > Storage.
Any help would be appreciated
Click to expand...
Click to collapse
Spotify has many issues with android and the sd card error problem,i personally read the spotify forums and there are hundreds if not thousands having the same error spotify really should get there act together and fix this after all it is a paid service and you should be getting what you pay for.
What i did was put a new sd card in formatted it using the phone and kept spotify out,everything worked fine,so my advice for now would be to avoid spotify at all costs as you lose everything thats on the card as well ,at least until they fix this bug,of which we are all having to pay for
Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.
OK, I've been wrecking my brain trying to figure out why I can't get the app to run on my note 4. I've been to the devs. Xda page for the app. But he has been mia since February and my post keep getting ignored. I thought I'd make a last ditch effort and try here. Basically the app crashes when I try to launch it. I've downgraded Google search in hopes that it would fix the issue but no luck. I'm running a stock rooted 4.4.4. Any help would be appreciated.
Runs on my stock Rugby Pro running stock 4.1.2 Jelly Bean well enough to allow voice dial and texting from the bluetooth headset on my motorcycle helmet. Without the headset, it is hit-and miss because the app always tries online via wifi first. If in good wifi it still works, but when not good wifi it hangs for a variable (sometimes long) time looking for network. I loaded tasker to toggle wifi off/on when bluetooth is connected, and this seems to fix it well for use daily on my commute by motorcycle. If I drive, I'll probably need to use a bluetooth earpiece. I get the feeling that planets must align for this to work, and it does for me. Developer seems to have abandoned it. I think offline voice recognition - at a minimum for voice dial - should be a mandatory capability for all phones. (And S Voice does NOT work!) If I had not found a fix, I was planning to put my SIM back in the old Rugby II flip and just use the Pro for wifi. They are company phones, and I only went the smartphone route to get company email.
Loading the original Play store version worked for me initially, with no crash issues but still experimenting and learning commands. Then I loaded the latest beta (see page ~ 720 of his main thread) and it seems even better, and Tasker fixed the wifi issue somewhat.
Sent from my LePanII using Tapatalk 2
Thanks for the reply. I have the latest beta install but I still have no luck. I'm wondering if another app such as a antivirus app could be causing it to give me an error.
Doubt it is anti-virus (but possible). Most likely Google Search version or Android version. Check the official thread and find tge ones known to work. I'm just lucky to have a six-month old phone with three-year old software, I guess.