yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] gaspx:
Possibly alternative to disabling power options...

I know this has already been mentioned on various threads regarding Bluetooth woes, but ozBT now appears to work correctly for me since I upgraded my Radio to version 1.06.00;

In a nutshell, ozBT will switch on bluetooth when its required and switch it off again when its finished. So, you can assign the Phone application to be a trigger to turn on BT. I also have mine set so it doesn't switch it off again afterwards as well. Thus, the holy grail that is continuous Bluetoothing.. well nearly!

I say nearly, as there is obviously a time delay between: phone ringing -> ozBT switching on BT (which is actually v.quick) -> BT Headset pairing (not v.quick at all). I'd say it takes around 10 seconds for my BT800 to pair up and realise there is a call incoming.

Not perfect, but not far off it. I'm hoping that by leaving BT on permanently, even when the Exec drops it, ozBT will come to the rescue when I receive a call giving me an almost seamless connection.

Now, I haven't actually tested this when the BT connection is dropped by the Exec, only by me purposely switching off BT and then calling my phone to make sure ozBT is working.

The reason ozBT never worked before is because my Exec would drop the BT connection, but the Blue Led would continue flashing, which I assume means the Exec thinks that it was still connected. Now Radio 1.06.00 has fixed that prob, I'm quietly confident that this is going to work.. mooohahaha.

I'll post back when i'm sure. (fingers crossed)

ozBT

http://oz.sciox.org/ozbt.html
[JASJAR, XDA Exec, MDA Pro General] gaspx:
Would you believe it, everything /was/ working great until this morning.. then I got a phone call and my Jabra wasn't having any of it.

So I checked my XDA, and the Blue led was blinking, check settings and the tick box was checked.. everything should be working, but still nothing from my headset. Unticked/Reticked connection etc, and eventually soft reset, but it didn't solve anything. Tried pairing again, nadda. Tried pairing another phone to the Jabra, and it picked up the XDA.. hmm.. I thought.

Reset the headset and it was all working again. There was nothing wrong with the XDA in the first place <sigh>, it was the Jabra that had crashed.

Bluetooth, don't you just love it.
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
I am using my jasjar with no extRom installed: bluetooth has been on for more than 12 houres now without turning itself off.
[JASJAR, XDA Exec, MDA Pro General] pauliephonic:
Bt woes

Ah well, it sounded too good to be true, M5000 is back to its old tricks again (although sometimes ok for a while)

Still have probs sometimes 5 mins after using headset, I'll go to make a call and the device will have turned bluetooth off.

Tried importing bluetoothfix.reg that I eventually found but it doesn't import...

Very annoying.

Has anyone any idea if this is badly thought out software by microsoft or is it more to do with what HTC (or orange, O2 etc) have done with the SDK?

Has anyone had this problem and then found a fix for it? Could it be hardware related (although I've found enough people complaining about similar that I assume its a design flaw) or am I just unlucky.

P
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
My Jasjar bluetooth is still working after 17 houres with my sony-ericsson hbh660 headset. Signal level is two bars better. Eliminating the i-mate extRom was a nice tip i got on this forum: thanks to all.
[JASJAR, XDA Exec, MDA Pro General] gaspx:
pauliephonic: yep, I thought that might happen - I found exactly the same thing; it doesn't seem to be related to whether the device is left constantly on or not, therefore, not a Power Saving bug..

ozBT is the best you can hope for at the moment. All you do is assign an app or window title (such as the Phone app..) to ozBT, and it will switch on BT whenever that program is active, i.e. if someone rings you, BT is switched on.

Using this technique, my BT has worked all week! ~ bar a slight problem which turned out to be my *Jabra headset* not working. :)
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
After 29 houres bluetooth turned itself off: extRom bypassing is not a solution.
[JASJAR, XDA Exec, MDA Pro General] jamps:
Been experiencing the same problem on my JasJar and HBH-600 (soon to be HBH-662!).

The only way that the bluetooth doesn't shutdown is when i disable powersaving (untick the turn off device if not used for...on battery power).

Have to charge the battery everyday though...

Tried upgrading the Radio from 1.03.xx to 1.04.02, didn't help at all.

ROM: 1.13.53 WWE

Radio: 1.04.02

OS 5.1.1700 (Build 14354.0.1.1)
[JASJAR, XDA Exec, MDA Pro General] 2manytoys:
Hi Guys,

Did anyone find a resolution to this problem :cry:

I have the latest upgrades for both BT800 and i-mate's ROM

BT800 - ROM is V0032

Universal is - ROM is 1.30.76, Radio os 1.09.00, No ExtROM

Thanks

Mal
[JASJAR, XDA Exec, MDA Pro General] Camstech:
I haven't found a resolution, but I have made some observations. When using the Jasjar with either Motorola or V3 BT headsets, I have never had a dropout problem. I think this is the reality for most Jasjar users...no problems. However, I recently installed a THB Blueadapter into my car, and bingo, the Jasjar BT is shutting itself off. I also have an Atom, and the THB Blueadapter will not let it go into standby. If you turn it off, it powers up again in seconds. Therefore there seems to be some aspect of the Blueadapter that behaves differently to the other headsets I use, and this is clearly causing the Jasjar some difficulty. Unlike the Atom, the Jasjar won't wake up.

I have a friend with a Prophet, and it behaves differently again. It will suspend, but still stays connected without any shutdown (ie it works like it should).

It's a pity the new ROM didn't fix this. It is a Jasjar (Universal) problem, not a WM5 one
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
I have a jasjar and a SE HBH660. With last rom upgrade bluetooth stopped turning itself off.
[JASJAR, XDA Exec, MDA Pro General] 2manytoys:
Ok, thanks. I was thinking it was a Jabra problem myself, and the only reason I say that is my old XDAII had all sorts of problems with Ericsson headsets, and once I moved to Motorola it was all good.

Thanks
[JASJAR, XDA Exec, MDA Pro General] Lordsmiff:
I think in many of the cases where people are having problems with bluetooth switching itself off, it is DEFINITELY a hardware problem.

With my first exec, I had no problems at all with bluetooth - everything was fine and it stayed connected all the time without me messing with any power options or anything, so I wondered what you were all on about, thinking maybe you had duff headsets or something.

Then, the external speaker went on my exec and I had it replaced and then the bluetooth nightmare began. Like everyone else, I would use BT to make a call or take a call and then a few minutes later, it wouldn't respond to the headset (HS 850). The blue LED would still be flashing but if I went into the wireless manager app, it would show as off. So, switch it on and it starts working again (though sometimes I'd have to soft reset). This happened no matter which ROM I was using (tried XDA, iMate and Orange) and different Radio versions. It even managed to drop the pairing with my headset a couple of times and it basically became unusable.

I tried getting another replacement out of O2 and after 8 weeks and many phone calls and emails, I managed to get O2 to accept that the phone was faulty and got it replaced and now bluetooth is working perfectly again.

I can only put it down to a bad batch of bluetooth chips or something like that for it to affect so many of us but like I said, I tried everything with each ROM and nothing would solve it.

Sorry to the bearer of bad news but I'd get them replaced if you have the chance before warranties start running out.

Cheers,

Lordsmiff.
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
Latest rom upgrade from i-mate fixed this problem on my jasjar: i now use my bt headset all the time without any problem. Before the rom upgrade it used to go off randomly after a few houres.
[JASJAR, XDA Exec, MDA Pro General] bowpay:
Bluetooth Headset MSVC and Jabra JX-10

I have a cingular 8125 with the latest rom and MSVC 1.5. I have had a lot of problems trying to get my Jabra JX-10 headset to work without a reset when I came across a few files. I simply stored these 3 files on my storage card than copied all 3 shortcuts to my Windows/Startup folder. After a reset all 3 files were called up and since than I am able to use the voice command over the BT Headset.

NOTE:

1. The headset will remain connected at all times if you don't close the connection via the headset. (This will seriously drain your headset).

2. When the headset is not disconnected I can now hear the caller ID accouncement through the Bluetooth Headset. (doesn't help much due to the headset needing to be connected at all times.)

Hopefully someone can figure a way to make the audio on file actvate once a call comes in and audio off when the call is ended.

Not sure if the toggle file worked so I included it just incase.

Let me know if it works for you!

Brian
[JASJAR, XDA Exec, MDA Pro General] oneteam:
Actually I have the same issue.

Before with the original shipped ROM 1.13 the BT works fine.

After upgrade to the ROM 1.30 the BT often disconnects.

The strange thing is that the Connection Manager still shows that BT is on but it is off. Even the advice from Buzz doesn´t help. Maybe someone has another hint what could be done?
[JASJAR, XDA Exec, MDA Pro General] bombastikmda:
New information?

With my Jabra I've no Problems, with my car i have this problems too
[JASJAR, XDA Exec, MDA Pro General] HeartOfDarkness:
I've had the exact same problem, both with the Jabra BT-800 and the MOtorola HT-820 stereo headset.

The problem:

- random disconnection between said Bluetooth headset and Universal;

- blue LED still blinking;

- bluetooth button still "activated" in the connections pannel;

- in bluetooth parameters, however, checkbox "enable bluetooth" is sometimes unticked, sometimes still ticked. This also seems to be random;

- I did *not* have this problem before upgrading my ROMs to an A2DP version (I had the 1.13.xx FRE version, and 1.09 Radio).

This last item would have me believe that it IS a software issue. Either with Windows Mobile, or with the 1.11 radio ROM concurrently with Windows Mobile.

In order to remedy this, I just (a few minutes before posting this and the thourough reading of the entire thread, and others):

- installed Buzz's registry modifications (unattended);

- copied the "hds1:" key to "suspend" as well (for good measure);

- unchecked "auto-power off" from the settings -> power control panel;

- I'll only, from now on, use the clamshell to turn the Universal "on and off" (in a manner of speaking, of course).

I'll see what this "set of tricks" does. I do hope that LordSmiff is wrong ( ;-) no offense ! ), tailazoom's subsequent post has me hopeful it is not, at least, a hardware issue.

Crossing my fingers, I'll report back here. :-)

My Universal:

SFR/Vodaphone v1640

ROM: 1.30.97 FRE (2006/01/03)

Radio: 1.11.00

Prot: 42.45.P8

ExtROM: 1.30.186

Headsets: Jabra BT-800 et Motorola HT-820 (A2DP earphones).

EDIT: ooops, Lordsmiff, not Lordsmith, sowwee !
[JASJAR, XDA Exec, MDA Pro General] tailazoom:
From my last post (5 april) and up to now i have buetooth headset (se hbh600) always on without any single problem.
[JASJAR, XDA Exec, MDA Pro General] HeartOfDarkness:
Hi tailazoom !

That's great news. :-)

Would you mind posting the exact versions of all your currently running various ROMs ?

I might, as a last resort, flash your ROMs instead of mine...

Is your setup A2DP-compliant, btw ?
[JASJAR, XDA Exec, MDA Pro General] HeartOfDarkness:
Alas, thrice alas, still disconnected.... :-S

Well, still trying stuff out... At least until tailazoom tells me what i-Mate ROMs he / she's using... :-S
[JASJAR, XDA Exec, MDA Pro General] HeartOfDarkness:
Ok, I have good new, and bad news.

Starting with the good news, I found the reason for my Bluetooth periodical disconnection, and hopefully most of the people here too.

There seems to be a bug in the latest ROMs (1.30 I guess), that actually turns the Bluetooth drivers off (maybe something BT-related crashes silently, who knows, I don't, I haven't really had time to look into the actual source of the problem, I tried to work around it with generally available means).

What I did in order to identify the problem and work around it:

- installed first a 1.09 radio ROM. I was hopeful since I know many people who found it was more stable than 1.11. It *did* allow for a longer connection between the Uni and the headset, and autoconnection (when either device was turned off / reset)worked very well. But after a while I still got an abnormal disconnection. But in this case, the general Connections panel (with the phone, wifi, bluetooth, activesync, etc. buttons) really showed the Bluetooth button in the "off" position, and when I entered the "settings" menu, it gave me an error message, something along the lines of "there are no Bluetooth resources available". That's what makes me think that there's a driver problem, or something akin;

- rolled back to ROM v1.13, etc. And lo and behold: no more disconnections. *NONE*. And that is as much a bad news as a good one, cause there's no native support for AKU2 in these versions.... :-S

So it would seem that there are two choices:

- live with the disconnection problem and the latest, AKU2 ROMs. Even then, I *strongly* advise to roll back to radio ROM version 1.09 (radio only, so that only a soft reset is needed). It was much more stable, even for the BT connections;

- roll back entire Universal to pre-1.30 versions of ROMs. I personnally tried both WWE et FRE versions of the v1.13 ROM.

There, these were my two cents... Sorry I don't have better news. :-S
[JASJAR, XDA Exec, MDA Pro General] tonyc9:
Guys I have a problem with my bluetooth and my dopod. It connects then disconnects.

I have also noticed that the systems unchecks the "turn on bluetooth" check box and the "make this device discoverable to other devices"

Does anyone have any ideas?

Guys I just read this at another forum.

"The Dopod 838 pro and WM5 have chronic problems with the bluetooth stack, which is why everyone is waiting for the new ROM to appear, which will hopefully be WM6. HTC (manufacturers of Dopod 838 pro) announced that the new ROM will fix all of the known problems"

This I learn after having a car accident (minor) in my car playing with the bluetooth and trying to get it to work. Hutchison 3g should only be selling these with a warning.

I assume there is also a problem with the JasJam as they are the same phone.
[General Questions and Answers] C00lBeanz:
I see when some people take down their status bar, it has a little android with it. Like when you pull it down, a picture of an android follows it. How can i make/put that in?
[General Questions and Answers] jiseuo:
Debugging mode Enabled...

http://www.makeuseof.com/tag/what-is-usb-debugging-mode-on-android-makeuseof-explains/
[General Questions and Answers] C00lBeanz:
And then? Please explain.
[General Questions and Answers] jiseuo:
Please read linked article, but short version is:

USB Debugging mode - special communication mode with other device. Used mainly by developers to debug new apps. It can be also used for hacking or modifying ROM files. Nothing for common users :)

Enabling USB debugging essentially starts up the adb daemon on your device, which allows it to communicate with adb on another device to enable debugging commands.

It's used when developing and debugging applications, and allows you (primarily) to:

- Transfer data between a computer and your device (both ways)

- Read log data easily from logcat

- Debug applications, including breakpoints and heap monitoring

- Install and uninstall applications

- Access a stripped-down shell on the device, for command-line interaction.

...

More you can read for example here: http://android.stackexchange.com/questions/16250/what-is-usb-debugging-can-i-keep-it-on-foreverhttp://android.stackexchange.com/questions/16250/what-is-usb-debugging-can-i-keep-it-on-forever
[General Questions and Answers] C00lBeanz:
Yes i know but, that's not what i want.
[General Questions and Answers] C00lBeanz:
bump
[General Questions and Answers] sgirard1991:
I think what you're looking for is a custom notification drawer background.....
[Sprint HTC One (M7)] robfactory:
http://www.androidcentral.com/android-43-updating-hitting-htc-one-developer-edition

" We have just grabbed the 564.04MB update on our unlocked Developer Edition. The update to software version 3.22.1540.1 brings all of the enhancements of Android 4.3, along with improvements to HTC's Sense 5 customization. This falls right in line with what president of HTC America Jason Mackenzie stated earlier this week, and if all goes to plan we'll see other models get the update soon as well."
[Sprint HTC One (M7)] Sloth:
Nice hopefully we will get it soon too :D
[Sprint HTC One (M7)] ticklemepinks:
why would it even mention sense 5 tho since its for the dev edition?
[Sprint HTC One (M7)] afazel:
Dev edition, not Google Play edition
[Sprint HTC One (M7)] tyler.durden:
That's GREAT news for everyone that has a GSM HTC One... Now for us, I'd say it's good news...hopefully Sprint is next.
[Sprint HTC One (M7)] flex360:
someone needs some coffee??
[Sprint HTC One (M7)] neswii:
You guys have to start tagging 4.3 threads with *NOT FOR SPRINT*

I don't think my heart can handle the letdown of a new 4.3 thread that's not for me every day.
[Sprint HTC One (M7)] robfactory:
Haha. My bad. :) At least we are getting a step closer to 4.3 and HTC has acted on their promise.

Now we have to see how soon Sprint is able to release their CDMA version.
[Sprint HTC One (M7)] babymatteo:
But GSM version has had 4.3 Roms for about a month and a half now. So this isn't anything new to them.
[Sprint HTC One (M7)] ticklemepinks:
yep it was late
[Sprint HTC One (M7)] ctiger:
I thought we have sense 5 on the original software?
[Sprint HTC One (M7)] robfactory:
We have Sense 5, but not 4.3. We are supposed to get 4.3 with a few updates to Sense 5, and then a month or two later Sense 5.5.
[Sprint HTC One (M7)] naturecannon:
Thread title should say:

4.3 started dropping tonight For DEV ED............. Since this is the sprint forum and title misleads many. :mad:

Surprised mods didn't lock down 4.3 chatter to one thread yet. It's A bit ridiculous although I understand the excitement and those anxiously waiting!
[Sprint HTC One (M7)] graycorgi:
I feel like the title is click bait. This is a Sprint forum, so the title plus the forum it is in implies it is released for Sprint.
[Sprint HTC One (M7)] the.emilio:
This is a sprint section? Wtf.. this whole time I was in the wrong area.
[Sprint HTC One (M7)] EPayne123:
No, it is in the correct area completely, just misleading title to some. For me, I knew what he meant when I clicked due to reading my other sites also but this is meant to inform others of AN HTC One getting 4.3 but not ours.
[Sprint HTC One (M7)] Dex4:
Any chance you can confirm if the pink, blue and purple tinting is gone from the camera?
[Sprint HTC One (M7)] OMJ:
HTC even posted the ROM :)

http://www.htcdev.com/devcenter/downloads
[Sprint HTC One (M7)] nhutpham:
Does anyone know if they fixed the camera tint issue?
[Sprint HTC One (M7)] XaoSilentrzk:
Why don't they just post the damn CDMA Rom too... Jerks
[Sprint HTC One (M7)] Kraizk:
If you read the other forums where people actually have the update, no most are claiming it does not.
[Sprint HTC One (M7)] robfactory:
Camera fix

It would suck if the camera is not fixed. I will soon drop this for the G2 or the Nexus 5.
[Sprint HTC One (M7)] neswii:
If it doesn't fix my phone's camera I'm getting mine replaced ASAP. Ugh, I just want a phone that doesn't crap out on me for at least a year and a half. Is that too much to ask these days?
[Sprint HTC One (M7)] XaoSilentrzk:
Not if it's HTC.

HTC should have changed the slogan from "quietly brilliant" to "quietly... We don't give a damn"
[Sprint HTC One (M7)] crispcat89:
I'm not sure what camera issues people are talking about, never experienced any, I'm waiting for the update just to be "up to date" in a sense. Hopefully they figure it out though, cause what's the point of a camera if it doesn't function as it's meant to.
[Sprint HTC One (M7)] noriyori:
Not that I'm super knowledgeable about this, but how difficult is it to put sprint radios into the 4.3 dev release? I'd think that would take much less time than waiting for sprint to do it. There are a lot of really smart devs working on this device. Even though many of them make it a priority to ditch sense...
[Sprint HTC One (M7)] the.emilio:
Radio's have nothing to do with it. It's the boot.img/kernel that is needed.
[Sprint HTC One (M7)] robfactory:
Sprint 4.3 started being issued today.

Sprint started rolling out 4.3 today. http://www.androidcentral.com/sprint-htc-one-getting-android-43-update
[Sprint HTC One (M7)] OMJ:
lol, old news now... http://xdaforums.com/showthread.php?t=2466996
[Sprint HTC One (M7)] Riff76:
I still think someone should leak 4.3 :D
[Galaxy S 4 Q&A, Help & Troubleshooting] bpollina:
I can't seem to get the drivers to recognize!

I tried both the samsung download and the adb version under extras.

I've pointed it to the correct place but it doesn't recognize.

Device manager lists it as "SAMSUNG_android" and "CDC Serial"

This is a brand new G4 google play edition. I took the OTA to 4.3 and one other update if that matters.

Exact error is "The drivers for this device are not installed. (Code 28)

There is no driver selected for the device information set or element."

I've tried rebooting as well.

Debug is on.
[Off-topic] 7alvi:
So, many of you geeks out there must be following Dexter T.V. show. So what do you think about the ending? I think it was a perfect end. Put your thoughts to words here!
[Off-topic] 7alvi:
1) It's a general notion.

2) I'll let the mods decide that.

3) Dunno.

4) Don't you watch Dexter?
[Off-topic] henvee:
They could have Mad Dexter happy with Hannah And Harrison. Doesn't need to be alone.
[Off-topic] Android_Monsters:
I'd be interested to know what happens in the books: http://www.dexter-books.com
[Off-topic] Archer:
I wasn't expecting a happy ending - that would have been insulting.

But, it should have been done better. It's like we've spent the last 7 years getting to know someone inside out, and then they change in the last 5 minutes of the show into something completely different. Is anyone else reminded of Anakin's 5 minute journey to The Dark Side? It was just badly portrayed.

Apparently though, the last series was meant to span over at least 2, which is where the rumours about it having another series to go came from. They did cram in too much story and that spoilt it.

The last series was rubbish for me. It pretty much killed my appreciation for what had come before.
[Off-topic] 7alvi:
Maybe they crammed too much story that's why people were expecting a somewhat different ending. I feel that the reason why he succumbed into seclusion was because of his very nature. We know Dexter as the person who is known for taking decisions no one could.

But I agree to the point that they did cram too much story in last season. Though it's disappointing to see him like that but he could not have done anything else accounting to his very character.
[Off-topic] Seraz007:
Damn i gotta stop visiting this thread :|

Still haven't seen it :sly: :( :eek:
[Off-topic] 7alvi:
LOL. I'll include "Spoiler alert" in title! :p