Database Info

wifi spits in bluetooths eye

Hi all wondering if anyone can shed some light on this one:
i recently bought a htc kaiser (yay) and its great! but i cant get wifi and bluetooth to work simultaneously in any way shape or form - every time i connect the wifi, the bluetooth connections will die - so far ive tested it with multiple devices and its a consistent problem
i even sent the unit back for a replacement but they tested it and said it was fine (i don't believe them cause i tried every which way to get it working) either way ive got the unit back now and i still cant get both to work at the same time - ARGH!!
if i cant get the bastard to work in the next week or so im going to return the unit as its inside the 28 day period - i just wanna be able to stream music from the net over wifi and listen to it using my a2dp headset
anyone have any guru zen insight on this one they feel like sharing?
cheers
fusi

must be a kaiser or rom thing cause i do it all the time at home with the hermes (go hermes go!!!)
have the wifi running fine with AD2P via motorola Ht820s

My Kaiser does both WiFi & BT with no issues. The only thing I can suggest is tinkering with your WiFi access point settings (change the channel, encryption, etc.) -- in particular, channel changes may do the trick, as both BT & 802.11b use the 2.4 GHz band.

thanks for the replies guys i swear im going loopy with this thing - what wifi channels can you confirm it works on for you?

well ive tried every permutation. it doesnt work - supergps are talking out of their arse when they claim they got it working. im really sick and tired of bull**** companies. dont buy from supergps - they might be cheap but you get what you pay for.

Why don't you try asking supergps what they did to get it working and how they have their wifi configured? Sounds to me like it's something in your setup that's causing it if they confirm the device works.

i did
they claim they connected up a lenovo laptop and a sony phone and it 'just worked'
i tried it with the exact same make model etc of kit (and a whole host of other devices (must be about 30+ different devices now)) and it consistently fails
i cant see how they got it working - unless they were testing a different unit or they didn't understand what the fault was - even though i explained the fault in precise detail in about 5 different ways to them over the duration of the day they were testing it
i reckon they just dont wanna deal with the hassle of getting a duff device back
p.s. this is with factory defaults - no customisations or anything (though ive also tried with every permutation of configuration i could conceive) - it just doesnt work

Rooted GingerBread Leak - Bugs

I've been running the rooted GB leak since it came out. So far the battery life is great and it is very stable.
*Edit* I should clarify that I am running 4.5.606 installed as the 2 part rooted zip, I am going to also install 4.5.607 to see if it changes anything.
I have noticed a couple of bugs so far.
I am running on GSM, the signal strength indications are 2 bars lower than they were under Froyo using Fission. The actual signal strength is the same, it is just the indication that is out.
If I turn the phone off and then on again without waiting for 20 seconds the GSM radio fails to initialise on the reboot. It tells me there is no network and asks if I want to switch to Global mode.
Sometimes the camera takes partial pictures, the first third is there the remainder is black.
Sometimes I answer a call and it is silent, no audio. It only happens from a few numbers, it always happens to the same numbers. I had the same issue on a Galaxy S and it was quite common. The entire time that I was running Froyo on the D2G I only found one other number that was a nokia mobile on the same network as mine where there would be no audio every time I called him or he called me. On this build I have had the no audio issue from a landline number, this is a first!
Vz have put a block into the firmware that prevents call diversions being made using the standard codes (ie. **62 etc) It pops up a message saying "Call forward is disabled outside the verizon wireless network"

The only issue you listed that I can confirm is the signal strength indicator for GSM. However, it was working in exactly the same fashion on stock 2.2.

I have noticed quite a few bugs.
1. Sometimes when a text message gets a certain length the keyboard stops working. You have to press home and open it again.
2. Keyboad LED sometimes doesnt come on.
There are a few others but I can't remember. I don't know what the problem is but I'm thinking of flashing back to 2.2 because it's so frustrating.

You can also try 4.5.607.

Gasai Yuno said:
You can also try 4.5.607.
Click to expand...
Click to collapse
Where can I find this? and can I flash it from 606?

http://rootzwiki.com/showthread.php?3406-Gingerbread-leak-D2G-Updated-to-4.5.607!
You need to follow the instructions here. I have been running 606 and it is excellent with just a couple of minor issues, but nothing show stopping. The biggest PITA for me at the moment is the inability to set up call diverts from my phone due to the Vz lock in 606, I am just about to install 607 to see if it changes anything.

4.5.607 is the soak test update; you can find it @ RootzWiki.
To install it, you must be on stock 2.4.330, no root, no bootstrap recovery.
There are no major changes in it. Call forwarding options are still available on VZW only.

wifi ad-hoc also not working properly!

BlueTooth Issues Anyone?
It seems I've lost the ability to connect to my phone over bluetooth serial port from my PC. Can anyone confirm this, or deny it? I've tried 2 PCs, with different BT dongles so far. I've had this problem on GB 606 and now 607. Man bluetooth is a pain. Might try SBF, reverting, but it does become tedious after a while.
(also, if it's just me, any suggestion on how to fix?)

I have flashed back to 2.4.330 and then installed the 4.5.607 update.zip and then rooted with the droid 3 script. No changes that I can see from 4.5.606.
Bluetooth audio works perfectly both ways. I can send a file from my PC to the phone using bluetooth. I can browse the device over bluetooth, but only after installing a 3rd party app. I am running Ubuntu so I can't comment on the windows bluetooth stack, but the linux one seems to perform normally.

SPP
I know BT Audio works. My concern is, did the BlueTooth Serial Port Profile and DUN go away? I used to be able to connect to my phone over BlueTooth and send AT commands to it. Now, no port, no connection.

I'm sure I didn't have DUN support on stock 2.4.330.
Not sure about the BT device which Windows fails to find drivers for, though.

No Call Audio.
mactherapy said:
Sometimes I answer a call and it is silent, no audio. It only happens from a few numbers, it always happens to the same numbers. I had the same issue on a Galaxy S and it was quite common. The entire time that I was running Froyo on the D2G I only found one other number that was a nokia mobile on the same network as mine where there would be no audio every time I called him or he called me. On this build I have had the no audio issue from a landline number, this is a first!
Click to expand...
Click to collapse
Mine did the same thing every other day on GB. I couldn't hear anything and neither could other person on the line. Only way I had been able to fix this is by rebooting the phone. Got very annoying. Went back to Hexen Froyo for now...

So I'm off travelling the world and using my d2g for internet access. I probably should have tested it before I left ;-)
It turns out the USB tethering does not appear to work, I get a connection and an IP address via DHCP, I can ping the gateway on the phone and resolve DNS info if I use the gateway as the server, but I can not get any traffic to pass through the phone.
Wireless tethering won't even connect using the built in App.
I tried Opengarden and the latest beta of the wireless tether app, no joy yet.
Funnily enough the bluetooth networking connected straight away and works perfectly.
I am running linux on my laptop, I guess I will have to boot into windows to see where the issue lies.

I don't claim to know anything, and currently don't have the motivation to go back to Froyo, but SPP and DUN are listed for the Droid2Global on here:
(not allowed to post link to MotoDev specsheet for Droid2Global)
I had SPP on Froyo. Now I don't. Don't know if it's GB, or just me.

wi-fi calling issues alpha ICS

I know it is only an alpha build ICS but this thing rocks. The smoothest ROM I have installed on my g2x. Except for wi-fi calling issues. W-fi calling initiates, can make/receive call but the moment you answer call, other end can't hear and you can't hear the other end and then it crashes. I tried everything already I know under the sun. Re-installed ROM, installed and re-installed different versions of ICS gapps, dalvik wipe, and everything. Just need it at work. I work in a place where every carrier has no signal, so wi-fi calling is awesome. Anybody has same problem with me and found a solution?

I've noticed a reboot or plane mode on/off will randomly fix it. It seems kind of hit-or-miss at this point.

I have the same issue except I haven't been able to make/receive a single call successfully. Admittedly I haven't tried airplane mode or rebooting after the first fail.
I've tried debugging it a bit and there's some strange messages in GANRIL -- there's a bunch of modem commands then suddenly NO CARRIER after some unsolicited command, then the whole thing seems to fail.
There's also some error that happens in the audio lib possibly pointing to a failed hand-off, but maybe that's a red herring.
I've tried a bunch of different versions I've found searching for a solution including one I packaged myself with some experimental build props and the .so and APK files from CM7.2. No success so far.
I kind of want to start a bounty for this -- Wifi Calling is very important for me. TMO signal sucks in my apartment that it's practically unusable even with a zBoost Wi-Ex running in here. In some places like Las Vegas the signal was so bad that I ended up using a Verizon MiFi card + Wifi calling =P
ICS is so cool though that even given all that, not having it is not a total deal breaker for me, just an annoyance.

I also have problems with wifi calling on HFS v1.2. It will connect and I can answer it. However, once I answer I can't hear the other side and they can't hear me and then it appears as if the other side calls again and all I can do is ignore the call.

Yeah, I managed to get this far now -- can sometimes make calls, can receive all calls but audio does not route on received calls. Then it goes into a bad state and requires a reboot for it to work again.
It seems ICS + Wifi Calling works, there's just bugs to iron out ...
Hephzibah said:
I also have problems with wifi calling on HFS v1.2. It will connect and I can answer it. However, once I answer I can't hear the other side and they can't hear me and then it appears as if the other side calls again and all I can do is ignore the call.
Click to expand...
Click to collapse

Successful Wifi Calling setups - please describe?

I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.

kingston73 said:
I'm curious for all you TmoUS people who have the ability to use wifi calling, if you are using it for ICS and it works could you describe your setup - rom, router, internet service, etc.
I've tried wifi calling on 3 different ICS roms and it didn't work for any of them. For my personal setup things work for about 2 or 3 minutes and then the call fails and my phone freezes for a few seconds. To call back I need to disable wifi calling, I've given up on it for now. I'm just curious to know if it might be just the app or if it could be the router or wifi signal or some combination or factors.
Click to expand...
Click to collapse
It is none of the above. Wifi calling on Tmo US with an ICS ROM is a known issue and will not be resolved until a developer gets an actual Tmobile US RUU to play with.
Between that and the inability to use the MyAccount app on an ICS is the whole reason I'm still on AHRD 3.6.
It is well known and documented that WiFi calling will work for a short time then cut out...and the fix by a dev is waiting on the above mentioned RUU.

I know that I've read posts that people claim to have been using wifi calling on ICS without any issues. I know its a known issue and I know the root of the problem is ICS itself, but why do some people say they use it without a problem?

My guess is people try to talk on the phone like me...as little as possible.
if someone is able to carry on a lengthy conversation without issues, I'm in the same boat as you...I'd like to know too.
Sorry...I didn't know you were aware of the apparent issues...

I have Wifi Calling partially working on my T-Mobile/HTC G2 running Andromadus Alpha13 (CyanogenMod 9 based).
I haven't figured out all the specific build.props entries that it needs to work, except I know that some update.zips with a minimal set don't work. I have one that pretty much replaces the build.props with one that spoofs TMO build data as well as other stuff and that this build.prop file works.
In addition to needing the .so files that are provided in all the update.zips I've found, and the Wifi Calling APK, I've read that GanOptimizer.apk is needed too and added that to mine.
I've found I can unreliably make outgoing calls. The first boot it did not work, the second boot I was able to make a call every other attempt or so. The audio quality seemed good too.
I can receive every single incoming call but they won't route audio wise and will drop. Then the app gets into a bad state and can't make outgoing calls either. Rebooting fixes that.
I haven't finished figuring out the bugs. The bottom line is it seems that CM9 *does* support Wifi Calling and it can work with some libraries and APKs added, however there are bugs that need to be figured out and fixed.

So from what it sounds like if I switch to Revolutinoary HD, then I won't get wi-fi calling, but since I'm running CM7, I get wi-fi calling but in exchange my HD camera doesn't work. We really just have to wait for updates now don't we?

Hey I actually just got HD Revolution installed, made a call on wi-fi for 15 minutes or so and it worked just fine.

Im running ARHD ICS and wifi calling works perfectly for me.
Sent from my HTC Sensation 4G using XDA App

That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.

kingston73 said:
That's kind of the point of my post, if it works for you I wanted to know what your exact setup is. I started with ICS on ARHD and wifi calling still only worked a couple minutes before cutting out.
Click to expand...
Click to collapse
+1. Same boat.

Well there's not much to tell really. I just updated my firmware as I was running CM7 to ICS and installed AR HD ICS 6.5.1. Other than that I guess I run NOVA launcher and that's really it

[Q] WiFi and BT Issues with Peregrine Carbon-ROM

Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards

Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/

just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck

Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.

i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/

BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/

Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.

Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^

Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...

Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:

bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time

ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again