Everyone,
I have a strange problem with my prophet, I have tried about 3 diff wm6 roms so far from this site.
And once flashed my phone randomly seems to wake up.
The screen will flash and turn on for now apparent reason.
Any thoughts?
My mate who has a wizard has the same problem.
cheers,
Mike.
Could it simply be the active sync error (it keeps automatically starting up)?
If so, just do this:
Open Activesync on your device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right. You can now go to Menu>Options and delete the Exchange Server setting you just added.
I have the same problem since I installed WM6 Underground yesterday.
I've tried your solution but it doesnt work (it still occurs after a soft reset).
Anyone else has a solution? This is so annoying
Try locking the device
I have noticed the same thing but it's going away if I'm locking the phone (only the power button remaining enabled).
yes this is happening for me using the ASERG 3.12 WM5 ROM.
It's really irritating as it seriously drains the battery. Went down about 30% last night.
Also waking up means running all sorts when the phone is in my pocket.
Short battery life causes me big problems as I travel a lot......
I'm thinking of going back to one of the less troublesome WM5 ROMS. I gave up with WM6 due to the loss of BT, GPRS and Wifi settings after a soft reset.
I'm sure one of the geniuses will fix all these issues soon.
cheers!
this has been fixed - http://forum.xda-developers.com/showthread.php?t=299069
Your waking up problem could be an faulty radio side-effect, it thinks it is receiving a call or sms and wakes up.
The most reliable radio rom right now is 2.61.21. You can upgrade to that without losing any data, and it fixes all call and sms, BT and Wifi issues. I applied that to a Jester's WM5 and solved all my problems plus got a better battery life.
Using a T-Mobile (USA) MDA, HTC Wizard, with the last official T-Mobile ROM, version 2.26.
Just very recently, Bluetooth often stops working, and I cannot get it back on again.
I try various ways of turning it back on. For instance:
1) The BT icon in the tray using the "Battery Status Today plug-in. (Actually I have the newest one, now called "Home Screen Plus Plus".)
2) An app called "Bluetooth Toggle, an icon to click that should switch BT ON and Off.
3) Comm Manager
4) Settings, Connections Tab, Bluetooth settings.
None of those work. In any of them, when I click where ever one should to turn on BT, the screen freezes there, only to be resolved by a soft reboot.
Sometimes on rebooting, BT is working again, but other times not. In fact, for the last several hours today, I have not been able to turn BT on again at all, despite reboots.
Does this sound like a hardware problem, or could it be something that could be resolved through software?
Any suggestions, registry tweaks, etc.?
I guess I could try a hard reset or reflash. But before trying something that drastic, which would require reinstalling all my apps, reconfiguring, etc., I'm wondering if there is something else I can try.
Or, if it's an irrepairable hardware problem, then I should perhaps look for another phone as soon as possible, as I want to have BT. I was waiting though, for a good new 3G WM phone to come out on T-Mobile in the next months. So, I would rather fix the MDA to use for a couple more months, rather than getting a Dash or Shadow now. (Wouldn't get the Wing, as I would prefer my next phone to be smaller and lighter than the MDA.)
Any suggestions on what to try, to see if I can get BT working again?
The change often seems to occur on re-booting. BT is working fine. On re-booting the MDA, BT is off, and I cannot turn it back on, as described above.
However, sometimes on rebooting again, it turns back on.
Any explanation for this?
I have an experiment for people using PPP to try.
In WinMo, disable all your wireless settings. Turn off WiFi, BlueTooth, and cellular data (phone). Boot up Android (I was using HTCClay's SuperHD v1.3).
Do you still have lock ups requiring you to pull the battery? I put a clean install a few minutes ago. I was getting lock ups in just a minute or two. I disabled all wireless in WinMo, booted, and I've been running for about 15 minutes without a lock up.
I read somewhere else (I read XDA too much to remember where), that someone else was having success with this method.
Edit: Using Chucky Rom and Radio 2.12.
With my combo (in sig) and everything off in WinMo, I don't get screen freezes with ppp. I sometimes get weird hesitations when browsing. This browsing hesitation could be numerous things, DNS lookup issues, server issues, etc.
WiFi works too. My only issue is leaving WiFi on and having my phone go into sleep mode for a few minutes. If my phone hibernates while on WiFi, it takes 15seconds to wake it. However, I can leave the phone on a charger all night with WiFi and I'll never get a freeze.
Thanks, Willgill for the info. Here's something I just posted in the SuperHD thread.
Everything is working wonderfully with this change. No more lock ups needing battery pull. I still get a few screen freezes for a few seconds, but this is due to the G-sensor issue. I can work around it by turning off the G-Sensor in settings, and when they release an updated driver, I won't need to. Also wifi is working fine at the office. On Bangsters, when I would turn off wifi, the entire phone would lock up without exception. With the WinMo changes, I can turn wifi on and off without any issue and it picks up signal with no trouble. Even GPS seems to be working better.
Is it possible when Haret shut down WinMo, something was still left in memory and caused unexpected conflicts and lock ups? I'd love to hear from other people who had PPP locking up on them if this helps their setup at all
Well, I can say that there is a good news and bad news for me.
Thanks to your suggestion I've had two results:
First: using "SuperHD2_v1.3 AXI PPP" I was able to get Data connection, first time with PPP.
Second: I was unable to get Data connection with "mattc Leo + Froyo w/Sense 1.7 PPP" not with base kernel not with "oe.netripper.com/files/htcleo_autobuild_evo_tree/zImage-20100913_001101-htcleo".
PS: I think that reason of failure setting Data connection with PPP builds for me is that there is almost no 3G in Moscow and I'm stuck with old/rusty 2G/2.5G GSM/GPRS/EDGE, My thought is that PPP have trouble working with 2G because most of the devs are working in areas with 3G available and simply didn't thought of 2G at all. It wouldn't bother me if not that the evo_kernel is the one which under development currently, not the old nexus_kernel.
And a little update, I am now switched to ★shubCRAFT 1.5★CM6 Final★ thanks to your finding as it appears that only by switching phone module before booting Android is solved the Data connectivity problem with some PPP build.
But that's not all, I've tried shubCRAFT's build before PPP ever was introduced and had to turn out them with only reason that BT in calls wouldn't work, the Phone app just hang it self, but now that is fixed two!
As being discussed in various threads, some people are having BT problems with EB13 based ROMs.
The Problem
Inability to connect at some future time after having paired device with phone. Rebooting doesn't help. Only solution is to unpair, and re-pair, then device will both pair and connect with phone.
Also seen by some people are audio routing problems after disconnecting BT. Not sure if this is confined to devices that support (and connect) A2DP... more investigation/testing needed.
The Workaround
I tested various conditions to see how the BT subsystem behaved under various usage modes. In particular, across boots, turning BT on and off on the phone, on the device, etc. -- and then observed if automatic connection would re-establish after each combination of conditions.
I found that the problem seems to only happen if I turn off BT on the phone. If I leave it on, pair and connect with a BT device, then I can turn the device on and off at will, and it will automatically connect.
This (normal) function persists across reboots, at least for the few I tested.
I don't know how power-hungry the BT radio is when idle and not connected. My gut feel is that it is a pretty small drain, so leaving BT on all the time as a workaround probably won't have much of an impact on battery drain. I use Juice Plotter, and have a good history with BT off to compare to. I'll post JP measurements/results tomorrow after a 24 hour cycle.
Caveats
I also changed my Epic BT device name before I explored this situation with toggling the BT radio on the phone. While the name change did not correct the problem on its own, I can't rule out that the combination of name change and leaving BT on is what is making things work, rather than just the latter alone. So, to try this workaround, you must also change your BT device name on the phone, and leave BT on. Then, clear pairing and re-pair for the target BT device.
My Request
Would people that are having this problem please try this out, and report back in this thread success/failure, and any other observations. What we see in testing these different modes will be very helpful to the devs in trying to trouble-shoot an fix this problem (which I have no doubt they will long before Samsung does).
It should be noted that some folks are having issue connecting to a device, even after un-pairing and re-pairing. If that is the case, you might try this-
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Also, some folks are reporting an issue with multiple pin requests before a device will finally pair. I haven't seen that one myself, but just thought I'd mention it.
For what it's worth, other than the BT routing issue, I haven't seen any of these pairing or connection issues on my stock rfs Epic. It wasn't until I converted my other Epic to ext4 that Bluetooth had any issues, and they were all fixed by wiping data and have not returned since.
I have tried the workout around before in the past, and it changed nothing. Also I have noticed I seem to have more issues with particular audio bluetooth ear pieces, like BlueAnt Q2. It will show pairing is connected but after a couple hrs on the bluetooth connection is gone, but like I said it shows paired. My cheaper Plantronic ear pieces seem to work much better, except the fact I have to re-pair after each reboot of the Epic.
Ive tried leaving bluetooth on all the time, but after a reboot,
i have to repair ive tried all suggestions to fix it and the only way it seems is once it gets connected is always have the phone on and cant die and bluetooth always has to be on,
even after a long period of time somehow it loses the connection even if bluetooth is on and phone stays on,
There must be somethng the developers can patch with a flashable fix or another work around to get squash this annoying bug.. ill try to get a logcat today and try your method again see if i have luck
I will try to leave mine on and see what happens. Name change did not help.
But short on time. But given the chance I want to go back to bonsai 3.0.1 and see if I have the same problem. I don't recall it giving me a problem.
Edit: of I leave BT on, on the phone and just turn the BT device on/off it will not pair back up.
Edit: May have figured something out. I have been toggling BT with a widget. When I toggle from the notification bar it seems to work (so far). Which would also explain why it quite working as I added apps. As from clean install is used the notification bar and later used my power widget. But I have always used a widget before. I will test this out at work and see if this work around keeps working for me.
Sent from my SPH-D700 using XDA Premium App
I have to re-enter the PIN after every reboot. Mildly annoying.
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
automator said:
Having tried the various bluetooth fixes given in different posts, I am now just leaving bluetooth on as described in the workaround above. I have left it on for a couple of days now and have had no trouble whatsoever with my headsets (both regular and stereo/A2DP). They connect as they should and do not require re-pairing. Even if I reboot my phone they have been connecting back up without issue. The only thing I cannot do is manually toggle bluetooth off and back on or the devices need pairing again.
I initially was worried about battery life by leaving BT on, but so far I have not seen any major difference... is the bluetooth radio only consuming power if a device is connected?
I still hope a permanent fix can be found for this as it makes me feel like my phone is "broken" somewhat
BTW, I am running EB13 with CWM 3.0.0.6, Bonsai 3.0.1, and Emotionless Beast theme
Click to expand...
Click to collapse
In my experience, the BT radio does not use any power when not connected to a device. If it does, it's not noticeable in Spare Parts or in performance.
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
blackdragon79 said:
I fixed my connection problem by doing a wipe and fresh install of my current rom. Now my bt is working perfect. Just make sure not to recover your date from nandroid that may cause u to recover what ever was causing the bt problem just restore your apps only my back up or appbrain.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Have the pairing issue with ACS EB13 Frozen ROM 1.0.3/ Twilight kernel. The BT headset I use is Plantronics 975. Never had a problem with any of my phones until now... even my Treo 755 connected properly, not to mention BB Tour FWIW, my headset supports A2DP and I wiped/reflashed ROM/kernel several times without resolving the BT issue. Will leave BT on, but does it mean after every reboot I have to re-pair? That's not good if true, I hope a permanent fix can be found soon.
davidrules7778 said:
What rom are you running?
Also did anyone by wiping data all data, confirm that on bonsai rom fix the non connecting issue?
Click to expand...
Click to collapse
I'm using syndicate frozen
Sent from my SPH-D700 using XDA Premium App
Update: For me at least, this workaround is still working 3 days later without a hitch, and across more reboots than I can count.
While I don't _know_ with tech/spec/engr certainty, as mentioned above it seems that BT uses negligible power when it is only listening for connection requests, and has had no discernible impact on battery drain at all.
So, this seems to be a viable workaround for the time being for some of us... it's real. What we need to work on as a community is figuring out what the critical difference is between those for which it works, and those for which it doesn't. KEEP POSTING AS MUCH DETAIL AND INFO IN THIS THREAD AS YOU CAN, EVERYONE... DATA IS WHAT WILL GET US TO THE BOTTOM OF THIS.
Personally, I think the key difference between the two groups is the size of your junk -- People with small equipment seem to be having all the failures
Sent from my mind using telepathitalk
I've had this issue on all Froyo builds. I have tried 7 different BT headsets from Samsmsung, Plantronics, Jabra & Blue Ant, all of them a2dp compliant with the same result, after a while, they stop connecting and I have to re-pair. As for the "workaround" since I have several extended batteries I've never turned BT off, and while it does take much longer to lose pairing, it eventually stops syncing or syncs only the headset protocol but not A2dp. For myself, the only solution I've found is to go back to DI18 which, although has its faults, works flawlessly with BT
I have been trying to get my brother's Epic working properly. It is rooted with EB13 installed. If this bluetooth error is not related to what others are having, let me know and I will create a different thread. I got his motorola H520 paired. I press the button and it starts the bluetooth voice dialing. It beeps and says please speak and then immediately gives and error saying the connection to the bluetooth was lost but the settings shows it to still be conneceted and it is as you can answer calls with the bluetooth without having to reconnect it.
My plantronics backbeat is paired and for phone calls is working, but sometimes no audio through music or video players. I had to un-pair, then re-pair then audio will work for a while.
I am using CWM 3.0.0.6 with midnight ROM with its installed kernal
Happening on my Plantronics Voyager Pro+ - It seems that everytime I pick up my phone the BT disconnects and then after about 15 to 30 seconds reconnects as long as I don't push any buttons.
There is also a lag "thingy" that occurs when I'm on a call and then another person calls - while the the second call is coming in, it seems like the packets get interrupted from the handset to the headset. Then once the incomming call goes to VM, the audio from the current call gets restored. Not sure if this is helpful or not, but I wonder if there are some routines in the BT transmission that have common "hooks" which are used when a second call comes in - Hope that is not too much of a noob statement...
Is anybody else having that "laggy" issue in the same circumstances?
Hello!
This has happened on multiple occasions:
When I flash stock, I have a routine that I go though, and one of the steps is to flash kevtweaks, found in one of the first few posts here:https://forum.xda-developers.com/ve...od-performance-memory-battery-kevp75-t3638524
When I flash, it usually breaks my Bluetooth and Wi-Fi by stopping their ability to turn on. One time while flashing I found that turning on Wi-Fi and Bluetooth before flashing makes it invulnerable to this... but only once. As of now my Wi-Fi does turn on, but sometimes it takes a few tries and takes about 30 seconds. And my Bluetooth doesn't even act like it's going to turn on.
This is happening on G935A & G935U. The weird thing is some have reported this, and others have had absolutely no problems, including the developer, kevp75.
Inside the tweaks, the dev and I have both looked and can't find anything that would break this (though obviously it's something)
I REALLY like his tweaks, they really help on this crappy eng boot. So I'd like to be able to use my Bluetooth and his tweaks.
Any help would be greatly appreciated