Related
Seems like I've been having this problem regularly since I rooted/installed Fission ROM. I even SBF'ed back to original, but it didn't seem to fix my issue. I regularly have to reboot my phone to receive text messages.
I can't seem to find any rhyme or reason to it. I've tried re-programming my phone, but every time it attempts to reprogram, it makes a weird noise and reboots.
Am I experiencing a hardware problem, possibly? With the radio?
Honestly no idea where to go from here, but inability to receive text messages = huge problem.
Are you using it on Verizon or on a non-Verizon GSM/HSPA network?
I've got the same issue using my milestone1 but milestone2 has more ram, so that problem should'nt appear at this device.
I believe I'm on the Verizon network, I'm using it in places I've always had good coverage.
Update: I re-installed Fission 2.4.3 I had from backup and installed Handcent SMS. So far, so good. I haven't appeared to miss any text messages since then.
Still, it's a very odd situation. Hoping Gingerbread gives some more stability, though I'm not sure why it would matter.
This has happened to me on TMOUS and to a friend as well...I have SGII she has MyTouch 4g...after reboot, a flood of undelivered texts comes in...all with the same time so doesn't help when trying to see when originally sent.
I'm rooted/custom rom and she's bone stock...wondering if its a network issue or android problem
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.
Hi folks
I have a Nexus S (i9020a). It has stock 4.1.2 Jelly bean from Google (downloaded the stock image and flashed it). It worked fine for over a month.
Suddenly few days back this device got a problem. When I dial any number I can't hear any dialing sounds and even after the call has connected I can't hear the opposite person and the opposite person also can't hear me (The phone still shows as 'Dialing' though it's already connected). The same is true when I answer any call. Both parties can't hear anything.
This is solved by rebooting the phone for the first phone call only. After I reboot, the 1st phone call works fine, then this problem persists for any calls I make/receive until I reboot the phone again.
I tried flashing a different radio but this problem is still there. I tried my sim card on a different phone and it works fine, so the problem is not that too. My 3G data works just fine.
I need this phone for the next few days/weeks (hopefully not months) before my Nexus 4 gets delivered :laugh:
Thanks..
Edit: Modified the title; Probably gave the wrong meaning that the problem is solved.
<bump> Modified the title. Earlier title gave an impression that the problem is solved whereas I still have a problem.
Have you installed any apps which could somehow affect the dialler?
Unless someone else can give you a different advice, I can't think of any other option than do a full wipe and reflash.
I haven't installed any such apps.
Also, I already did a full wipe and flashed the stock image again. The problem is still there.
Don't know what else you could try, sorry mate - hope someone else can help you sort it out!
Thanks for trying. I think I will go to some hardware shop and see if they can figure out..
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
ej8989 said:
Try using a headset for making phone calls so that we can identify if it's really the hardware's problem.
Click to expand...
Click to collapse
That's the first thing that I tried... doesnt work.
mailrachit said:
That's the first thing that I tried... doesnt work.
Click to expand...
Click to collapse
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
_android_ said:
I had similar problem when RAM running out. Usually a reboot fix the problem for a bit.
What I did:
1. With Titanium Backup Pro, froze unused RAM hogging system apps, like Google+, Google play magazine,etc
2. Froze or uninstall Facebook, Word with Friends, etc which are resident and hog RAMs .
3. Install marmite kernel, free up more usable RAMs.
Hope it helps you too.
Click to expand...
Click to collapse
Thanks for the suggestion!
I tried this too but doesn't work...
Try any custom ROM instead of stock ROM and a different kernel too. There could be chances that you've flashed the wrong ROM / radio too.
Sent from my Nexus S
Problem solved.
I went to a hardware store today. The guy said that it's a problem with the 3G service of my carrier (Vodafone India). The moment I enabled the '2G only' option in the Mobile networks settings area, this problem was gone. The technician said that this issue is affecting some people randomly. He said that since 3G service was launched just last year, the networks are not yet capable of handling all kinds of devices (he claims that the bug is so erratic that another Nexus S i9020a may work just fine with the very same bootloader/radio/rom which doesn't make any sense). When I said that 3G service was working fine before, he said that most probably my carrier changed some settings on their side which is causing this issue for me.
I have tried this for 6-8 hours now, making a lot of phone calls and it seems that the issue is gone. It saddens me that I am off 3G for now but at least my phone calls and basic EDGE internet works fine. I will have to work with Vodafone to solve this or simply wait for my new phone (Nexus 4) and hope it won't have the same problem..
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
TenderloinShadow said:
Ok, first of all I'm an old veteran at flashing ROMs. Secondly, I know about the SIM card reset, where I restore my phone to factory settings and enter a number in the dialpad (can't remember it, have it written down) to reset your network connection. The thing is, I have a few hours left at work before I'll have time to attempt that, so I wanna explain this issue to the community and see if there's an easier option.
So, to start, I have been running the 01/02 build of Bean Stalk 4.4.2 for a few weeks now with no issue. I'm also on the latest modem, VRUCML1, which I again have been running for a while with no issue.
Today I decided to try out some newer builds, so I made a nandroid and then flashed the new Carbon 4.4 build (01/19). This was when I had my first network issue, where it had me stuck in roaming even though I was in my home. So, thinking the ROM may still have some issues, I switched to a newer build of Bean Stalk (01/17). While I now had mobile data back, I found that my phone was unable to send SMS.
I finally restored my nandroid, yet now I find that this problem is still persisting. I flashed the previous modem, VRBMF1, and the problem still persists.
The weirdest thing, though, is that even though it won't send SMS, my mobile data works fine. I'm able to browse the web at full LTE speeds, but not send SMS.
Edit: After a recent test, it seems phone calls won't work either. So my phone seems to be handling the LTE functions well enough, but is having trouble with the CDMA/EVDO part of the antenna.
Anyone who has any advice, please help. Like I said, I'm inclined to do a SIM reset, but won't be able to until much later tonight.
Click to expand...
Click to collapse
Go into About Phone -> status check your IMEI and PRL and such are they still there?
buhohitr said:
Go into About Phone -> status check your IMEI and PRL and such are they still there?
Click to expand...
Click to collapse
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
TenderloinShadow said:
My IMEI is there, it was the first thing I checked. I did the whole IMEI backup thing way back in the beginning with this phone.
IMEI wouldn't explain the problem anyway. I still have 2-3 bars of LTE at all times, which I wouldn't have if I didn't have my IMEI. For whatever reason regular phone communications (SMS/Calls) won't go through. Since I know that Verizon still routes those communications through the older CDMA/EVDO network, I'm assuming that's the source of my problem.
Click to expand...
Click to collapse
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
The problem i had i couldn't recieved calls. Everything worked fine..
I ended up getting new sim card then the employee dialed *73 then my fone was back in action
buhohitr said:
Sure just make sure things don't get corrupted, if everything is still in order then you can reset sim, worse case call VZ and they can reset (re-provision) the sim for you. Happened to me twice and VZ solved them in both cases.
Click to expand...
Click to collapse
yeah I figured that would have to be the answer from the beginning. Have to Odin back to stock first, won't be able to do that for probably another 3-4 hours because of a work meeting that's about to start, so I figured I'd ask around.
If anyone has any other ideas, I'm open to them. Otherwise I'll reprovision tonight and report back.
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
beepea206 said:
The data/sms issue isn't odd... sms and calls are on the 1x protocol, data is on the LTE/CDMA/EvDO, so if you can't send sms, you can still use data.
Have you tried flashing one of the stock-based roms and seeing if the issue remains? I've encountered that before where stock is fine, but CM/AOSP roms have a wonky issue and *some* people report after doing so, they can get data/calls working on the custom roms. Unfortunately, my resolution there was to cab (LG device) back to factory image.
Click to expand...
Click to collapse
+1
Flash back to stock, or a stock based rom with stock messaging. Try to force the message through. My messages stopped sending on aosp messaging and was persistent through rom flashes. I eventually forced it through using touchwiz messaging.
Sent from my SCH-I535 using Tapatalk 2
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
You probably should flash another modem & then try.Here
http://forum.xda-developers.com/showthread.php?t=2824139
Sent from my One using XDA Premium 4 mobile app
LukaZilla said:
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
Click to expand...
Click to collapse
Hey there fellow Aussie. See link provided by other member, it should fix you up.
Transmitted via Bacon
That modem actually proved to be worse for me.. Before I didnt have stable 3G connection.. that modem made my 4G connection worse too. The best, and most stable modem I have found thus far is in the latest nightlies. It is still very very very weak when it comes to 3G connectivity but its better than everything else I have tried. And believe me, I have tried pretty much every rom there is on this forum including XNPH22R, XNPH25R, MahdiRom, CyanHacker, and All the nightlys.
The only one I havent tried is Color OS because I am afraid it will lock my bootloader again.