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.
Related
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
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
Is wifi direct disabled by Samsung for the Skyrocket? Coworker and I are on ICS 4.0.3 (ICSMOD5) and can connect but when we try to send a file,pic or anything it doesn't display his device as an available option.
Really tired of having to pull out my SD card to send files.
same problem on my end except it won't fully connect either. just detect other devices. probably just an early version bug.
Maybe. I don't remember if this was available back on 2.3.6 or not.
We do have wifi direct cert but is samsung disabling this?
http://certifications.wi-fi.org/pdf_certificate.php?cid=WFA12015
i believe it was.
at least 2.3.5 it was.
Switched to a few different roms with the same results. Even tried to mix and match ICS roms with coworkers and we still can't get it to do jack.
Hand to face moment..
SOLVED: Disable the data and reconnect. It wasn't allowing the send I think because the LTE was still on. Works fine now.
I bought a refurbished Motorola Defy+ which came preinstalled with Gingerbread 2.3.4. Out of the box, the phone was able to receive calls, although I didn't test making calls at that time.
I ran the stock Software Update from Settings, and this installed 2.3.6 on the phone. Since that point, I can no longer make or receive calls on the phone. As soon as the phone tries to make the connection, it reboots: either when making a call into the phone, at the first ring, or when dialing out. I have confirmed that it's not the dialer itself that is the problem by using different dialer apps.
I have performed a full factory reset on the phone and tried with wifi, etc turned off but it has made no difference at all. Other features of the phone are absolutely fine and I have had no unexpected reboots due to any other cause.
After searching around it seems quite a few people have had problems with their Defy+ rebooting, but this is generally either during a call or just randomly. In my case it is absolutely at the exact time that it tries to make the phone network connection and at no other time.
Could this be a hardware problem, or is it more likely to be the 2.3.6 ROM installed by the software update? If I install another ROM, is it likely to fix the problem? If so, how would I go about downgrading the phone to the 2.3.4 version?
Thanks in advance.
OK, I jumped the gun.
I hadn't actually connected to any of my mobile phone network's APNs at the time I posted the above. Now that I have configured it to connect via 2G or 3G, I get random reboots all the time.
Not that this helps or anything.
In this thread i am only referring to the WiFi/Bluetooth clash that seems to affect some of us but not all of us.
ie; The problem appears to be with the WiFi, WiFi fails to disconnect when leaving the ssid area. Wont reconnect when returning to the area, the WiFi connection just cycles, hunting and hunting, never connecting..... until i turn the Bluetooth off, then it connects within seconds. Switching off the Bluetooth appears to eliminate a 2.4ghz clash between the wifi and Bluetooth, allowing the WiFi to operate freely.
Other phone manufacturers have had to deal with this, its not uncommon.
I've been evolved in a bit of discussion about wifi this week, And i have found I have the WiFi/Bluetooth clash on my twin-core. but not the quad-core.
so i thought we should distribute the version numbers that are trouble free, that seems to me to be a better place to start than with just random testing like i have had to do to get my result... .. so a bunch of test roms later, here are the rom versions i use, and have turned out to be trouble free.
Twincore - Now runs "CleanROM 3", based on build version 1.88.707.2, now runs problem free. I had previously tryed Asian roms 1.77.708.3 & 1.77.708.2, the Modaco IR1(1.29.401.11), all had the W/BT problem.... there were some others that didnt work either but i lost track.
I also tried the wifi fix provided by JSLenterprises but got no relief from that, not on any of the versions i tested.
(To be fair to JSLenterprises, i dont even know if his fix was for this issue, i just tryed it because i was testing anything WiFi for my solution!)
Quadcore - Still running factory 1.29.728.12, always ran problem free!
Anyone else got some build numbers that you know are trouble free? we might be able to narrow down weeks of research for others trying to resolve this bluetooth/wifi clash.... or else wait for the proposed offical update of course.
And anyone having familiar problems might want to flash these versions i suggest, just to make sure i didnt just get lucky.
lets solve this sh..!
You had bluetooth issues, and flashing cleanrom 3.0 fixed them?
what issued did you have? my bluetooth is terrible.
Was person calling me hearing their echo when im on bluetooth one of these problems?? Just bought bloototh for car and receiver hears their own voice, big echo they say
I had no issue with the bluetooth itself...
explanation in opening post........