Related
Help !~
My O2IIs Bluetooth when I turn on it and go to susupend(standby mode?!) around 5 min ,then I resume the OsIIs again but the bluetooth will be turn off and on .....that have a big problems when I"m using the handset and have incoming call ! The OsIIs is going to resume ..... then the handset will be disconnect (because the BT was turn off automatically)~~But any problem when I do it in 5 min !! ......and I'm sure is not my handset connection problem!!
How can I Sovle it??
Thx ~~
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
rakh1 said:
First thing I'd do is ugrade to the latest ROM - you are still using the older one. If you still have problems after that it may be worth going from BT3500 to 3900.
If you don't know how to do either of the above have a little search around the forum. The new ROM is on the O2 site and there are numerous postings about the 3500 to 3900 upgrade all over this forum.
R
Click to expand...
Click to collapse
Don't bother. I have 3900 on my IIs and it still does the same thing.
Thanks for rakh1 and kevinnugent reply~~
In fact ,I tried to downlaod and upgrade the newest ROM form the O2 website ! but my O2IIs is not buy in UK ! so....
In the mean time ,I"m also "cooked" (crack?!.. I don't understand what difference on "cooked" and "crack",haha~) the ROM by the "XDA3nbtool",but have the error message on installation ,that show "Radio image file checksum Error ",when I replace the original radio image,that will show the other image file checksum error.....
And I contact the O2 Custom Center in HK ,but they ask me to contact the Singapore customer service ,and said "they just have a repair service only!they haven't technical support ! "
OMG!! haha...a sick joke !! :lol: :lol:
Finally,the Singapore Custom Center still haven't the solution about this problem !... they just send the "bluetooth BT3500 update patch " for me to try (haha!!...) it can solve this problem or not !!
I have the same problem about BT disconnection
I posted an item about the same problem two days ago...
And the "official" technical support did the same to me: send me the 3500 BT Stack (and I found it in the web and installed two weeks before. Great technical support!).
In fact it's frustrating: I need a car kit that works well for my job, but impossible with Qtek. So, if I want to have a hands free car kit...I must buy another phone?.
Incredible for an expensive machine like Qtek 9090.
I have'nt tryed for the sort of multiple patchs of 3900, but I have no faith in it.
I you find a solution, please let me know.
Good luck!.
j.m.
Hey ~I have the solution now?!~and I tried it a whole day~any problem!
Firstly You must stop the "Auto Power Off" Function on the O2IIs,then go to:
http://www.pocketgear.com/software_detail.asp?id=14621
to download the "screenlock" (software) and install it ,after the installation ,you will not have the icon on the “Program file “ (haha…may be the software bug),than go to “file exploroe” ->”My Device”->”Program files”->”screenLock”->”screenlock.exe”,When you run it the first time it will be create the icon on “program file”,If you want to leave it, press the button 1 and 4 (Calendar and Message button on the IIs) simultaneously! Now !the Bluetooth will be connected every time ~
but I still hoped the O2IIs announce the newest rom update for the Asia user soon……..
By the way, when updated the BT3500 ,the “auto resume” problem will be solve or not ??because I’m updated to BT 3900 still no change…..
Thx
Cangratulations Alextly!
ScreenLock works fine, and although this is like killing flyes with a bazooka, it's the only solution that I know about it, and this convert this solution in the better one.
The only question I've got now it's about power consumption. This program Locks (turns down) the screen but, if I understood well, with the screen locked the CPU is sitill gorking "underground", so the battery life can be reduced (I must do some proves).
As far as I know, the BT3500 doesn't solve the problem (I installed and it's the same). I ignore if the 3900 it does, but I'm afraid that it will not. I have not installed because the 3900 I've fount it's some sort of different patches that and they doesn't seem to be very reliable. So I prefer to wait for official Patche. And as says "kevinnugent" seems not to work.
Let's keep the faith for official technical service (my faith it's going down for minutes).
Thanks for you're finding and congratulations. I would never find this one.
j.m.
ScrrenLock
ScreenLock it's not as fantastic as I though: it shuts down the PDA automatically when you are in no-battery mode (for exemple when you're using TOMTOM), and increase battery consumption dramatically.
j.m.
Interesting... I don't seem to have the same symptoms with my SX66 paired with my SE HBH-300 and HCB-30 (car kit). When the SX66 goes into standby, the BT seems to stay connected. If it does disconect with either handsfree, I just press the call pick-up on the handsfree and it re-establishes the BT connection within 2-3 seconds.
I'm using 3900.
Ken
SX66
In fact I think the connection must not be disconnected. And with my Qtek if you have good luck and re-establish the in some way, maybe you will hear nothing...
My car kit it's Drive Blue from Parrot.
j.m.
Hi
I have the newest firmware version installed on my Qtek 9090 (BA_WWE_14000_147_11200_Ship), and I experience a problem again which I had first when I bought my Qtek but was gone after I had installed Radio version 1.08.00:
Once a day I have to reset my Qtek because I can't hear the one I am calling - usually this happens when I call my mobile phone's answer phone. The phone gets connected but I don't hear anything. After a soft reset everything is fine again.
Is this a known issue? Any solutions to it? Ok - I know I can downgrade to 1.08 again but I dont really wanna do that. And yes, I can stop calling my anser phone ....
Anyone knowing what is causing the problem?
Reagrds,
A
I had the same problem with my Qtek 9090 until I stopped use the Bluetooth feature completely. Since then, everything is fine.
tot 1.12 radio has solved the "no sound" issue.
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
keeping_sg said:
ThExSenatoR said:
keeping_sg said:
tot 1.12 radio has solved the "no sound" issue.
Click to expand...
Click to collapse
I cannot verify this, i have an mda3, upped it to R1.12 but i had many "no sound" problems. Now i downgraded to R1.10 and had not a single no sound issue ..yet
Click to expand...
Click to collapse
i have tried 1.06 & 1.10, all are having that issue. that's why i have upgraded to 1.12 so far so good. umm.....................strange..
Click to expand...
Click to collapse
For me, radio 1.12 delivered:
- worse signal reception
- higher battery consumption
- still no sound issue.
flashed twice & still having the bloody "no sound" issue. really give up. i think the next thing to change is the motherboard. sigh.........................
I had never had this issues untill I upgraded my Radio to 1.12 and then I had it 5 times in one day, went back to 1.10, no more issues
Hmm. This is a really 'odd' problem. I didn't originally have this problem with my SX66. Then, it just 'popped up' one day, and I can't seem to get rid of it.
I have tried different ROM versions (currently 1.40), and my radio version is at 1.10.
I have NEVER used radio 1.12, so I know that's not the CAUSE.
We need to compile a list of people with the problem, and see exactly what combination of ROM and Radio they have, as well as the programs they have installed.
if you read the cingular forums, there are a few folks there that say they have had it all along so I am not sure where to start...
umm....... different ppl have different problem. seems like it's a integration issue.
If you go to some HK forums, you will also find a lot of people suffering from this.
To me, I seldom use it as a phone. I only use it to receive emails and website browsing. When I go overseas and I used it as a phone with a BT handsfree (shut down GPRS connection), everything is just fine. I only encountered once with no sound problem when I take away my BT handsfree on a plane....
It's definitely a bug since a long time ago with old and new versions.....
Sad....and disappointed......
Hi all,
I upgraded my phone to the 1.12 radio along with the 1.40 CE ROM and am always resetting due to the "can't hear caller" issue and I never had this problem before.
I'm going to do a hard reset and see if that helps (clear out all the apps and use it for a day or so). If this doesn't work, I shall revert back to the 1.10 as I had no problems with that.
ROM 1.40.00
Radio 1.12.00
EXT ROM 1.13.139 (with Updated CallerID [1.20] and older version of O2 Active [3.0])
This cant hear caller issue, is it cant AT ALL hear caler or caller is so faint I cant hear him.
I ask as sometimes I get calls that are faint however when the caller rings back it fine. Not sure if its crap reseption or the device.
I got O2IIs from UK and had the same "No sound" problem. I have to SR about 5 times daily to sort it out. However, if I turn off Bluetooth (pairing with my Bluetrek G2) then everything's OK.
My ROM version is 1.31.00 WWE, Radio : 1.10.00, ExtROM: 1.31.139 WWE and BT 1.0.0 Build 3500
Had up to BT 3900 but wont help. Gonna up radio to 1.12. Will post the outcome soon.
I've only experience the problem once since the imate 1.40 upgrade.
Now, I must say that I don't use the phone THAT heavily.
I upgrade to 1.40 EX, it seems working fine, still the sound quality is not good enough...
people!
A guy called Derek has posted a possible solution to this problem here! http://forum.xda-developers.com/viewtopic.php?p=118364
It involves removing the Bluetooth for the startup because he believes that even with the bluetooth off, the unit is still trying to connect to a bluetooth headset.
I'm going to remove/unpair my Bluetooth Headset and see if that makes a difference. If anyone else can try this and post results I'm sure this would help loads of people.
Dom
Please confirm this and I will post it to wiki
@xdadom,
It's correct. As I mentioned in my post, when I "turned off" Bluetooth, everything's OK. The way I "turned off" Bluetooth is exactly the same with Derek did in his post, i.e. delete "Run_BTTrayCE" from Windows\StartUp\
However, I still need Bluetooth for my hand-free device. In my opinion, it's rather a trick, not a solution to kill "No sound" problem. Anyway, we can wait the updated BT version from supplier to sort it out.
I'm having a problem when someone calls, I can't hear them but they can hear me. Once I soft reset, everything's peachy. Just today I used my phone (pda2k with i-mate 1.40 rom) several times. Everything was fine. I turned the flight mode a couple times today. Then, I turned on flight mode, let the phone sit for a while and had an incoming call...I couldn't hear them. I told them to call back in 5 minutes. I tried calling another number but couldn't hear anything, did a reset and everything was fine.
This has happened before and after the 1.40 upgrade. Anyone have any reason why?? I've tried turning the flight mode off and back on, but that didn't help either.
Thanks,
Tom
This is an known issue in 1.40 ROMs, and currently there is no solution.
Dont blame ROM 1.40 because you also face this problem when using ROM 1.31
No solution so far but a trick's available here: http://forum.xda-developers.com/posting.php?mode=reply&t=22239
Solution
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
I don't know if this can help to solve the problem but I wanted to mention that I never had this problems when I was using vodafone, but after I changed the sim card this probleme occured
Solution
The Solution is TURN ON your BLUETOOTH and then TURN OFF your bluetooth.
Re: Solution
asim_ag said:
The Solution is TURN ON your BLUETOOTH and then TURN OFF your bluetooth.
Click to expand...
Click to collapse
Unfortunately for me this actually triggers the no sound issue! My device is fine until the first time I use bluetooth then I can almost 100% guarantee that the next call will be silent.
As stated before with the 1.40.00 rom, this issue is certainly linked to the Bluetooth driver, perhaps on use it is switching audio to their driver for headset use and not restoring it?
Are you using sbp Plus, because this application has issue with bluetooth. Try to close all application not to minimize them when you are done with it. Use PocketNav or Magic Button for that.
Re: Solution
ThExSenatoR said:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Can you tell me if the BT has to be started like you described when you use Tom Tom? Normaly Tom Tom starts the BT automaticaly when it starts. Thanxx
hi
I get this problem a lot when I've had the phone on silent or vibrate and then change it back. I think it mainly happens when I receive a call after this rather than make an outgoing one but after the 1st call even outgoing ones have no sound.
It sounds daft but after a couple of months where I reset whenever it happened I just by chance hit the volume slider & sure enough the in call volume was turned right down. It's worth checking as it's an easy fix for me!!
Kill process
The solution for the problem could be to not run the BT driver. Anyway it's possible to delete from startup the dirver and to run when it need (for GPS or headset...).. But is there a way to kill the BT process without reset the machine (that without BT in the startup does't run the driver) whit a simple "TAP" ?
Thanx... M.
I hope I put my Reply on the right forum, but however...
I recently bought a QTEK9090 via Ebay and also I have the "I can't hear incoming calls..." problem.
Radio 1.06.02 and ROM 1.22.ooWWE. I understand from the postings in this forum that only a few (approx 10 to 15) have a problem and the rest of the world does NOT.
Strange but due to this I am really thinking to replace it by a P910I, as a phone should be able to pick-up calls. I haven't decided because the 9090 is a great machine.
Doesn't anybody have a clue, even not the manufacturer ??
Hi,
i had the same problem. Than i followed the advice above from someone deleting the autostart BT and using the btray.lnk instead. Absolutely fine since then.
greetings
Using the XDA IIs.
Until we get a proper fix, I am using the manual Run_BTTray method to turn on the BT if I need to use my headset.
So what I do is, (a) normally, no BT tray, (b) to use my BT headset, use Run_BTTray to turn on BT tray, (c) use ATBluetooth to actually turn on and off the BT radio, and finally (d) soft-reset to remove the BT Tray when I'm done.
I know it sounds complicated, but is ok after I assign the commands to my buttons (XDA IIs, plenty of buttons!).
What about the pda2k UniDirectional Patch.sa.cab available on the clubimate site.
I had this problem with ROM 1.40 as well as with the previous ROM. I have installed this patch. I have not had this unidirectional problem since then but I am not sure if this will work in the longer term as I have installed the upgraded ROM and the patch only a few days from now.
Love to hear comments of other members who have tried this patch.
Kind Regards
srmz said:
What about the pda2k UniDirectional Patch.sa.cab available on the clubimate site.
I had this problem with ROM 1.40 as well as with the previous ROM. I have installed this patch. I have not had this unidirectional problem since then but I am not sure if this will work in the longer term as I have installed the upgraded ROM and the patch only a few days from now.
Love to hear comments of other members who have tried this patch.
Kind Regards
Click to expand...
Click to collapse
The patch works.... atleast I didnt get the no voice problem after the patch (touch wood :twisted: )
So, I've been searching, and this may be covered, but I seem to have the problem in REVERSE. I can hear the other party when using my BT headset, but they can't hear me! On one call, it'll work, then on another, it won't, and then it'll stop working. I have ROM v.1.40.00 and Radio 1.13.00 I don't know what I could do to fix this problem...
Any suggestion would be appreciated...Although I'm not keen about removing the BT tray from the startup, only to soft reset just to remove it...
Thanks,
Q
does this problem remains in the WM5 ?
I wouldn't know...I'm still on WM2003SE....BTW, I have a Siemens SX66.... Anyone? Please?
I am trying to solve a problem in the Helmi 1.4 ROM for my SX66. The problem is that whenever I turn on the bluetooth functionality, the phone turns on after a minute or two. I keep on turning it OFF and it keeps on turning ON. What should I do? How are you guys with Bluetooth Headsets doing with the Helmi ROM installed on your SX66?
tariq_niazi said:
What should I do??
Click to expand...
Click to collapse
Scratch your head twice, maybe 3 times, look for search button or just read bit the forum about bluetooth. And don't ask a question, that was explained so many times - in general and in technical details. I just checked, there is short info even in Wiki part. So PLEASE, be self-reliant, just a bit.
I won't comment creating a completely new thread about this - you could at leas add it to the (correct) Helmi's ROM discussion.
Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.
what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1
ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?
Have you tried flashing a new radio?
Ta
Dave
data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..
Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?
I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.
hm, looks like a big upcoming problem for everyone...
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.
gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?
same here... im playing around with different radios, it has to be a radio issue imo
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................
I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo
I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.
Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.
Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC
Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.
Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01