Related
I followed directions to wipe everything as suggested in this post:
http://forum.xda-developers.com/showpost.php?p=20485148&postcount=146
Was using Alfa 13 just fine, but on Alfa 17 I can not get cellular data to work. Confirmed my WAP settings are correct for my carrier.
My baseband it says its a i9020xxkf1 and everything else on the phone works. I can access the market, wifi works, account sync if i have wifi on. I have doubled checked every possible setting. But it will not bring up a data connection over the cellular radio. It even takes calls over the radio. Just no data connectivity.
Any suggestions or reasons why this is occurring? I can easily swap back to an older nandroid image of alfa 13, but I would really like to get on a new version etc.
(Also, I would have made this post in the right dev section, but i lack 10 posts to gain access to it.)
Have you tried removing and replacing your SIM card ?
Also, check if your data counter has a limit set on
You could also manually configure your APN settings with your carrier's settings
Unfortunatly I have done all of those things. It doesn't even attempt to connect to data. I sit at 4 or 5 bars of signal and it never even connects to EDGE/3g at all. Yet if I flip back over to my older image it works flawlessly.
i have also problem with version 17, but i can't post it to developer forum (newbie here)
problem is that i can't hook on any network, no calls no messegas, i'm using croatian tele2/t-mobile....sometimes it connects but still nothing, no calss etc.
also problem (not so much a problem but a solution) when i installed ROM it went to bootloop, all you have to do is remove battery and power up again, and voila, it works, same problem happened when i installed gapps (same solution worked, everything installed from CWM latest version)
there were also posts regarding cwm not stiking after installing cynogen, i had no problem with it, i have latest cwm 5.0.2.3 (think so), sticks like hell tried couple of roms, still sticking
cheers
I have the same problem here... ICS 4.0.3 and my 3G stopped to work.
also tried new 18 version, still no luck, i'm staying on cynogenmod 7 (GB), only ICS version that worked was MUI but i don't like it very much....
http://forum.xda-developers.com/showthread.php?t=1398691
It has been messed around with a fair bit. Various methods have worked for different people. YMMV. I myself had such an issue with the stock FW (of all FWs...).
Not sure if this is the correct place to post, but I am having a rebooting issue with the ROM. The phone seems to reboot while using Google Talk, specifically while typing, the phone just locks up for a few seconds and reboots. It seems to also always be when I'm either typing on the keyboard, or getting focus on a box that requires the keyboard for input. I thought it might be an issue with the gApps that I have installed, but I flashed back to my backup of v7.1, and the issue no longer persists.
Also, a general problem with HO!NO!, on both v7.1 and 8.2, the camera app crashes my phone quite a lot. It is random, so I can't say exactly what's causing it.
Also, is it normal for a phone to have completely incorrect time after rebooting (from a crash by the camera app, I should add) without a data signal? (This was a problem for v7.1. It updates fine within a second with a data signal, but the time seems to default to 00:00 without data.) I was in a place with no signal and all the pictures I took ended up with time stamps of something like December of 2002.
I'm currently using HO!NO! v7.1 with kernel version 3.0.8-HO!NO!_Mod-cyanogenmod+ and Cyanogen Mod version 9-20120721-UNOFFICIAL-p930.
I have the same issue. Same trouble with Jellybean too. I think it's something to do with the Kernel. we need a custom kernel soon!
After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
icedmayhem said:
I have had this issue for some time as well, I know your frustration. It has even made me to the point of switching to a different phone
Click to expand...
Click to collapse
Right now , i am sticking with 44S + BlissPop but it pop error process from time to time =( . i just wish they fix the radio soon.
I got a roommate using CM11S works with no problem. so I might just switch back to KitKat for now.
Gh05tShie1d said:
After so many tests, i can finally confirm this problem.
Basically, in the last week or so, i have been missing almost all incoming calls because of this problem.
I found, even with the newest nightly 02072015,
all CM12 Modem update will cause my OnePlus to not responding to incoming calls after screen lock for more than 5-10 minutes.
My area does not have the best reception, normally 1-2 bars, but i rarely missed a call because of it.
all test are done with clean installation after revert to stock. put in lock for about 5-10 mins.
My test result:
CM11S + 44S Radio, 3 test calls, received all. Caller side ring twice until phone respond.
CM11S + 38R Radio, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
CM11S + CM12 Radio, 3 test calls, received one call. 2 not received, Caller side ring twice then went into voicemail.
CM12 + CM12 Radio, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom2.0 + Bacon_firmware_update, 3 test calls, none received, Caller side ring twice then went into voicemail.
BlissRom1.8 + 44S, 3 test calls, received all. Caller side ring 2 - 3 times until phone respond.
This problem will not occur if the phone is "freshly" locked.
Click to expand...
Click to collapse
Sent from my XT1023 using XDA Free mobile app
does any one have possible fix ?
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
---------- Post added at 06:06 PM ---------- Previous post was at 05:45 PM ----------
Merlin696 said:
I had luck flashing a different modem. From the website below the Full-CM12-23.01.15-modem-flashable.zip did the same thing but I had good results with the Full-CM12-12.01.15-modem-flashable.zip
since I am a new user it wont let me post the link so you guys will have to take out the spaces
http : / / boeffla . df - kunde . de / bacon / modems /
Click to expand...
Click to collapse
Never Mind, that didnt work either.
Tried that before, no luck but thank u regardless
Ok I got it working and have been using it for a quite a while now without issue.
First this is for CM12
Download this modem
cm-28112014-modem-flashable.zip
http : // forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734/post57129886#post57129886
Next you will need to do a firmware flash/update as well otherwise the proximity sensor wont work
bacon_firmware_update_2015_01_29.zip
http : //downloads.katinatez.com/addon/
I know I probably dont have to say it but just to make sure, these should be flashed from recovery
again you will need to take out the the spaces in the http since I have not posted enough to post links
So the fixed worked all day until I turned on my WiFi and then I failed to receive my test call. I turned the WiFi off and it worked fine again. Not sure yet what the correlation is but I think its more than just a modem issue.
I give up, i'm going back to KitKat
---------- Post added at 11:52 AM ---------- Previous post was at 11:37 AM ----------
looks like maybe just maybe the devs have finally started having the issue too
http : //t.co/h0361GBRZl
well its not a fix, but if you leave your radio on 2G calls come through just fine.
I have searched high and low and still cant find anywhere someone has a fix for this issue yet.
Having the same problem on the latest nightly. I really don't want to revert to kitkat.
Problem still persists!
I am on cm-12-20150329-NIGHTLY-bacon.zip nightly and I still have the issue! I really really dont want to go back on KitKat so temporarily I am back on my old phone.
I, too, am experiencing this strange problem. No calls or texts when set to LTE, but they do come through when set to 2G.
I am currently on the 4/5 Exodus rom with the new firmware and modem from Oxygen OS. The issue still happened after flashing the newest CM nightly so I took a chance the new firmware and modem would fix it..... No luck.
Sent from my A0001 using XDA Premium HD app
same problem as well with OxygenOS and recent CM12 nightly. I wish that someone could help find a resolution. This is nuts.
I experience the same problem when I was on Blisspop, gave up and reinstall KK.
Recently tried CM12.1 and have the same problem with that rom too, a little better perhaps.
Hope someone found a solution.
Well back to KiteKat again.
All this time and this thread is buried WAY down in the Q&A section.
Are we the only ones having this problem?
Sent from my OnePlus One
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
JohnM109R said:
Man I so glad I'm still on kk and I will not update to "L" IMO I think it's the biggest flop from Google just like when M$ released Windows ME....guys stay away....
Click to expand...
Click to collapse
I don't think it is a total flop by Google at all. It's probably some errant coding for the radio on our particular phone. I would love to try to figure out why but I have no idea how or where to even start.
Sent from my OnePlus One
OK, it isn't me then. Had a missed call on my screen yesterday when the phone was next to me all the time.
Did you all get a missed call or nothing?
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Hi, Last week I had my phone connected to power bank over night with "Sleep as Android" turned on. In the morning I got my wake up alert but I was unable to wake up my screen to turn it off... so I had to keep the power button down and shutdown the phone.
After that I have faced boot loop (phone worked fine previous evening).
I have tried rebooting phone couple of times but nothing worked so I have restored backup of last CM11s from TWRP (I was running on CM12 nightly during the crash). Phone booted up poperly and I thought everything is fine however after couple of hours I noticed my phone is asking me for my PIN so it has apparently rebooted. It appeared that it is rebooting every couple of hours and after every call (like 5 sec after call ended)...
I have tried restoring other backup but I was facing the same issue. I have done clean install of current CM12 nightly and got the same...
Facing that I decided to clean my phone completely... I have backed up all my data and did wipe and format of everything of everything I could from TWRP. Then via fastboot I have been tring loading YNG1TAS17L 64GB (from here) by flash-all.bat file. After loading bootloader I have received message <waiting for device> and my phone got hardbricked...
I managed to recover it using this guide.
Then I loaded TWRP again and installed COS 12.
On that point my phone started working stable but after a while I noticed that is started losing cell signal. Sometimes it was just for couple of seconds and sometimes it lost it for good (while tring to hardcode cell operator I was getting "error while searching for networks" and I was able to restore connectivity after couple of reboots).
I decided it could be radio/modem related so I have applied full firmware. No go. Loaded CM12 nightly - the same, loaded that modem from oxygen again - no go.
I have tried installing latest BlissPop, Mahdi ROMs and Oxygen and still facing the same issue.
Tested SIM card on other phone and it works fine, tested other SIM card on my OPO and still the same issue so it is phone related.
Getting the following in logcat during time phone is unable to connect to cell signal:
Code:
05-31 11:57:36.265 D/GsmDCT ( 2457): [0]isDataAllowed: not allowed due to - SIM not loaded and not NV subscription
05-31 11:57:36.265 D/GsmDCT ( 2457): [ApnContext:mms] getApnSetting: apnSetting=null
05-31 11:57:36.268 D/GsmDCT ( 2457): [0]isDataAllowed getRecordsLoaded=false
Anyone has any idea what could be a reason of this issue and how to fix it? At this moment everything is working fine except phone calls and Internet over network operator (Wifi works fine). Thanks in advance.
UP
Anyone has any idea? I believe I have narrowed the problem down a bit. It seems 2G/3G is affected only. As long as I'm in LTE range the connection is stable (that explains why I noticed the problem after few hours when I left home).
I have played a bit with hardcoding band and noticed that LTE is running stable (with GSM Signal Monitoring app). When switching to 3G it is dropping every couple of seconds. The strange thing is that 2G is sometimes affected and sometimes not... When switching LTE->2G it seems to be running pretty stable but when switching from 3G->2G it is acting the same way as 3G.
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
spx2000 said:
were you able to fix it?
I went through same experience except that I can barely connect to 4g, 3g 50% of time. Tried many radios but none worked.
Click to expand...
Click to collapse
OP updated the post with how it was fixed. Sorry to bump the thread, but thought I'd inform spx that there was an update. Glad it worked out for you OP, I've saved this in case it ever happens to me, and good luck to spx. Hopefully someone puts this info in a sticky so others can try that if they are stuck too.
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO
artiwal said:
It seems I have managed to solve it by myself. I have loaded factory image of 44S, preformed OTA upgrades and it seems the issue is gone.
The thread can be closed.
Click to expand...
Click to collapse
Where is the 44S that OP used? I have something similar happening with my phone. I revived my phone from a hard brick and now it's not connecting to the cell network. Wifi works, IMEI shows when SIM is inserted, no EFS partition backup (I didn't know that was a thing to do until it was too late).
FWIW, my current build is KTU84Q and I'm running CM-11-20141008-SNAPSHOT-M11-bacon
If I'm understanding correctly none of the current roms work on Sprint's network. Is that correct?
I've tried lineageOS and couldn't hold a signal so if there's one that works please point me in that direction.
Thanks.
I hadn't had any luck with ROMs on Sprint either until today. I decided to restore my TWRP backup of LineageOS 14.1 official, then I re-flashed the bootloader and radio from the most recent stock build (I had been on 4.4.3 to test something). The device was not active on my account at the time, but when it booted up, I got an alert from Signal Check Pro that it had an LTE signal, and the LTE indicator was on. So then I signed on and swapped devices to try to reactivate it, and immediately went into carrier settings and tapped update network settings. I got an alert shortly after saying com.android.phone had stopped, but it appeared to work, and I had a signal and LTE indicator. There was a Lineage update showing (May 17), so I downloaded it (over LTE) and installed it. Everything has been working so far, both before and after the update: voice, LTE (all bands), SMS, MMS, and RCS. So I really didn't do anything different, it's just working now.
Note, I have had SMS problems on every stock build starting with the first 6.0.1 build, and all security releases after it. I haven't had any problems on any older Android version. What happens is it works fine for a while, but at least once a day. SMS stops working until I reboot or update network settings. That's why I installed Lineage, trying to determine if it's a bug in Android or the radio. So far, no problems, but it has only been a few hours.
Sent from my Nexus 5 using Tapatalk
LOL it course the SMS bug struck after about 24 hours.. except this time it took a couple of tries to get data working again, and SMS wouldn't work again.. I knew better.. back to stock again..
Sent from my Nexus 5 using Tapatalk