I need help. A little over a week ago I flashed the cyanogenmod 7 stable. I did a wipe of basically everything (user data, cache, dalvik, battery) and then flashed the rom via clockworkmod. Everything seemed fine at first, but I soon noticed that my signal was diminishing. I could no longer hold a steady signal. The signal would change from green to white like it was trying to grab for a signal; all in places where I would normally have a full signal.
I have been rooted since about December and have had no problems. I am with USCC. I have tried many roms in the past months too, including cyanogenmod RC4 with no problems. I am not exactly a noob, more like a noob +1, but I have exhausted everything I know to try.
List of what I’ve tried:
• Flashing a new rom (tried every rom I could find for Bravoc)
• Flashed back to stock rom (everything stock except w/ superuser and s-off)
• *228 while in stock rom
• Added APN for MMS
• Changed radios
• Changed kernels
• Installing the RUU from US Cellular’s website
• Various Nandroid Backups
I really don’t know what else to do. My WIFI works fine and I can make calls ok, but 3g is out of the question along with any type of data connection really. Can anybody help????
Only thing I could think is to change the RIL, Radio Interface Layer.
There is a good thread here:
http://forum.xda-developers.com/showthread.php?t=902752
Personally I find the newest (17) radio and the Nexus (1001G) to be good, but I know it's different for each carrier and handset.
Hope this helps!
hmm, I haven't even heard of that yet. I'll for sure try it. Does it apply to CDMA radios as well as GSM?
I also had the same problem. I flash HTC-RIL 2.2.0131HM (Mar 18 2011,00:40:15) (extracted from Desire S Rom) for new radio. everything is fine.
tarurin said:
I also had the same problem. I flash HTC-RIL 2.2.0131HM (Mar 18 2011,00:40:15) (extracted from Desire S Rom) for new radio. everything is fine.
Click to expand...
Click to collapse
Do you know where I can get that RIL?
mkelso27 said:
Do you know where I can get that RIL?
Click to expand...
Click to collapse
You can get it from the URL.
http://forum.xda-developers.com/showthread.php?t=902752
mkelso27 said:
hmm, I haven't even heard of that yet. I'll for sure try it. Does it apply to CDMA radios as well as GSM?
Click to expand...
Click to collapse
I think there is only one for CDMA. You could try using the code in the thread to check your version to see if it's worth trying to change? All the RILs are listed at the top of the thread...
Code:
su
getprop gsm.version.ril-impl
00droid said:
I think there is only one for CDMA. You could try using the code in the thread to check your version to see if it's worth trying to change? All the RILs are listed at the top of the thread...
Code:
su
getprop gsm.version.ril-impl
Click to expand...
Click to collapse
Ok, so my RIL actually matches up with a GSM RIL. Could this be my problem? It kinda sucks though, cause I can't find that CDMA RIL anywhere. :-(
Hm
mkelso27 said:
Ok, so my RIL actually matches up with a GSM RIL. Could this be my problem? It kinda sucks though, cause I can't find that CDMA RIL anywhere. :-(
Click to expand...
Click to collapse
Maybe that's it then - you could post that exact question in the RIL thread, and ask for a link to the CDMA RIL? Must be someone with it somewhere.
Good luck!
Related
hi all,sorry..i'm just wanna ask about one Q?...i'v boot RSL4 build with NAND to my kaiser,it seem very2 nice n gud to stick with this build...but my only problem is my data won't connect n doesn't show at the top of my notification bar...
but when i try to boot from SD after connect my data network in winmo,everything worked perfectly unless a little bit slow...how can i fix this problem? plzzz..
-sorry for my bad english-
From your sig I see you use 1.65 radio, which is good for Europe, have you tried 1.70 or 1.71? these may work better for Malaysia, ( last shipped rom was HK/WWE rom with 1.70 radio ).
Before this, did you try APN settings? in settings/wireless+networks/mobile networks/access point names, add your provider settings there ( check for these online ).
zenity said:
From your sig I see you use 1.65 radio, which is good for Europe, have you tried 1.70 or 1.71? these may work better for Malaysia, ( last shipped rom was HK/WWE rom with 1.70 radio ).
Before this, did you try APN settings? in settings/wireless+networks/mobile networks/access point names, add your provider settings there ( check for these online ).
Click to expand...
Click to collapse
sorry bro,that's my old radio..actually i'm use 1.70.xx.xx now,in winmo it will connect data network for very fast...n yes,i'v fill that APN setting from my servis provider but it's just same ... i'll try for 1.71.xx.xx radio version then..
thnx, bro...
Noticed a few using CM6 builds having data problems, have you tried other builds? My personal favourite has always been Polymod, but kallt's RLS9 froyo build is also very stable, and I have noticed fewer issues with that build.
Sent from my HTC Dream using Tapatalk
zenity said:
Noticed a few using CM6 builds having data problems, have you tried other builds? My personal favourite has always been Polymod, but kallt's RLS9 froyo build is also very stable, and I have noticed fewer issues with that build.
Sent from my HTC Dream using Tapatalk
Click to expand...
Click to collapse
tq bro..i'll try it now..
I just did a software update check, and it came up with a new OTA firmware. It's also listed on the HTC support site.
yup - it's here too.... updating now.
Let's see what it do
Screenshots of versions when it completes would be nice.
Wonder if theres a new radio.
edit: from a post below:
32.44.00.32U_5.09.05.30_2
2.6.32.15
2.10.405.2
downloading as we speak... Damnit! well, its not gingerbread..
The RUU has been out for a while, been running it over a week now...doesn't do a lot but you now get the voice mic on the keyboard and new radio (well, old but new to stock WWE ROMs)
I'm very disappointed
They still haven't fixed the AAC (he-aac v2) bug. What's the problem with implementing the patch google have released HTC???? I guess I have to delete my whole music collection and re-encode into ogg instead.
Talk about multimedia phone!
Also peep is messed up again, to bad since it worked fine in 2.2 since twitter fixed the bug since apparently HTC was to lazy to try themselves.
It seems I'll be getting a Samsung device next time...
*** EDIT *** Forget about the peep issue, it started to work after a few sync tries but the music issue is there and that's what bugs me the most...
EddyOS said:
The RUU has been out for a while, been running it over a week now...doesn't do a lot but you now get the voice mic on the keyboard and new radio (well, old but new to stock WWE ROMs)
Click to expand...
Click to collapse
Any consensus on the new(ish) radio?
Seems to work fine, it's been out a while anyway
has someone extracted the new radio yet?
It's not new, it's been in the radio thread for ages, see my signature for version
It's here anyway (link from the radio thread)
http://android.adamg.co.uk/bravo/radio/32.44.00.32U_5.09.05.30_2.zip
owziee said:
It seems I'll be getting a Samsung device next time...
Click to expand...
Click to collapse
Good luck with that one! The Galaxy S issues (GPS, lag etc) seem far worse than the Desire's. I'm sure these things will be fixed, but then again I'm sure your AAC issue will too - eventually!
Regards,
Dave
foxmeister said:
Good luck with that one! The Galaxy S issues (GPS, lag etc) seem far worse than the Desire's. I'm sure these things will be fixed, but then again I'm sure your AAC issue will too - eventually!
Regards,
Dave
Click to expand...
Click to collapse
the S in the galaxy stands for **** lol
EddyOS said:
It's not new, it's been in the radio thread for ages, see my signature for version
It's here anyway (link from the radio thread)
http://android.adamg.co.uk/bravo/radio/32.44.00.32U_5.09.05.30_2.zip
Click to expand...
Click to collapse
many thanks eddy
Any issues for Orange users who have unbranded their Desires?
Sent from my HTC Desire using Tapatalk
Just installed it in 5 minutes.. my phones seems a little bit zippier then before.. dont know what the android patch is.. but it seems ok !
I become a signature error with my rooted Desired (rooted with unrevoked).
Any ideas?
Maybe with a rooted device you need to use the RUU version, but you loose the root
If you were branded first you'll need your gold card
Did anyone encounter wifi problems after the update? On my device I get I can't enable it anymore. Reboot doesn't solve the problem.
PierreLeDark said:
Did anyone encounter wifi problems after the update? On my device I get I can't enable it anymore. Reboot doesn't solve the problem.
Click to expand...
Click to collapse
no wi-fi problema on my device. Maybe you need to remove a not compatible app or make a hard reset
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem.
My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
Thanks
deathw15h said:
Few n00b questions.
Firstly, how do i flash a nightly on my phone? lets say im running ofw 2.2 SEA edition? Do i follow the same procedure as if to flash RC1... do i also need to flash gapps similarly.
--> I'd say install RC1 and gapps first, then try a nightly by just wiping cache and Dalvik - no need to install gapps again since they're on your phone now. If you install a BOOT version and want to go back to an earlier CM7 nightly, then you might want to start from scratch, reflash froyo and install RC1 + gapps again.
Secondly, are the links on quarxs' CM7 for defy thread up-to-date? or are there newer versions of gapps and nightlies floating around somewhere
--> mostly up to date, but I don't worry about gapps too much as I believe that the Market gets updated automatically anyway (but I might be wrong about that). On the OP, the link to the gapps should show you up to date versions; but read the comments on there - very important.
Third, i have noticed that there is an issue with network and wi-fi when i flash cm7 RC1 over the nordic sbf. when i go back to official 2.2 SEA there is no hassle at all. Since i live in india i was wondering if that was the issue. I can easily take care of the network problem using "baseband switcher for defy" but it still doesnt help the wi-fi problem. My question is.. will using the new BOOTSEA nightly solve this problem. I am assuming from the name is boot"SEA" im assuming its built southeastasia specific.
---> same here my wifi DL speed was really bad for the last month or so on CM7; only after BOOT179-4 install, my wifi speed somewhat got back to normal.
Fourth, ive used CM7 RC1 for a while and apart from the wifi issue i got problems with camera and video... it absolutely doesnt work, wether it be in potrait or landscape or whatever setting... the app just force closes. Any fixes for that.. ive got green lens.
---> My camera and video worked on RC1 (and earlier) but video recording had some chopiness at times. Around July 11th nightly, Quarx released a camera fix (in that nightly) that solved the problem for me. But then days later, on newer nightly builds, I got the FC problem on video camera (same as you but red lens here). Then with BOOT179-4, camera was fine again and so the wifi speed; so all good for me.
--------> I really don't know what's going on with the video camera: many poeple have problems and many have it working on every nightly builds. It has been a problem from day one for Quarx on CM7-jordan... You have to try and see which build works for you I guess. And like you said, BOOT-SEA definitely looks like something you should try - many people liked it and many people say yesterday nightly is the best for them so far... so go on and have fun with testing
---> Before you do more testing though, you can always do a backup from the custom recovery so it will be easy for you to restore your current phone state -if nothing improves. I do this all the time: stock recovery factory reset, nordic flashing, RC1 install then restore my (BOOT179-4 now) backup.
Please help!!! and i hope other similar questions can be added by members here so as to make this thread an FAQ for distressed users like me.
---> I did try to help - I hope I did! If so, you can use that "Thanks" button - hehe!
---> Not sure that a thread entitled "nightly doubts" will become a very popular
FAQ thread though
Thanks
Click to expand...
Click to collapse
........................
[] AL [] said:
........................
Click to expand...
Click to collapse
thanks for all the help
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
dumrul said:
There is a FAQ for flashing cm7 go and read it There is no need for threats like This
Send from my brain using Tapatalk
Click to expand...
Click to collapse
i went thru the whole FAQ but my doubts are regarding the nightlies which it doesnt address hence the thread.
thx for the concern though.
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
deathw15h said:
downloaded the BOOTSEA, but there is another file "cm7-110726-0018-BOOTSEA-Jordan.zip.md5sum" mentioned below it. ( there are similar md5sum files for all nightlies...) are they essential ? and how do i use them.
wanted to clarify before proceeding.
Click to expand...
Click to collapse
Md5 files are to verify your download is not corrupted one. Which you can compare the md5 after downloading the zip file and regenerating the md5 of downloaded file and check against the one in the server.
Sent from my MB525 using XDA App
deathw15h said:
thanks for all the help
Click to expand...
Click to collapse
No problem.
Go read here on the official CM7-jordan thread: http://forum.xda-developers.com/showthread.php?t=1033654&page=943
And from post 9429 particularily; pretty much goes in the same direction I was pointing at regarding the wifi and video camera...
How's the BOOTSEA doing for you?
The nightly ones is just the output that the ones who are working on the rom ups to us. Normally have all that part on topic that say "next version:..."
If you wanna try the nightly one, use as the *.zip that you download when got the "rc1 v2" for exemple. So wipe the phone, choose install from a zip of the sdcard and choose the *.zip, been it the rc1 or the nightly build.
The md5sum file is the one that contains the 5sum from the file. Its nornaly given when you have to download a big file and have fear to corrupt the file. If you use linux, go on terminal and type "5sum file" when file is the name of any file that you have. It will give you a big number. This is the 5sum. The *.md5sum have the 5sum of the respective *.zip nightly rom.
Sent from my MB525 using XDA App
how is the battery life with the nightly builds?
what android version is the 27/7 nightly build using? is it 2.3.5?
yup..its 2.3.5
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess
atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.
Flashable zip added for new Commotio Rom Nightlies
Any chance to apply the patch to a stock rooted rom?
Thanks
Region Code
Hi can someone fix this file for region code?
nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.
Can someone post the patch for latest cm nightlies?
nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.
I am having issues with 4g and 3g switching on the device. Some times there will be no signal at all. 80% of the time doing an Airplane mode cycle will fix it. however this is dozens of times a day. This has been an issue since the M8 release. Can anyone send clear directions to a fix please.
System:
LS970
Cm version 11-20140916-SNAPSHOT-M10-ls970
Kernal 3.4.0-CM+
Maybe this post will help. I believe it's in the forum of the ROM you are using. In the future, try reading here for issues.
http://forum.xda-developers.com/showthread.php?t=
HdMsTrTeCh said:
Maybe this post will help. I believe it's in the forum of the ROM you are using. In the future, try reading here for issues.
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
Not sure if you are being intentionally funny or not, but that link does not go to any thread....
If it was an accident, I think this would be the correct one, right?
http://forum.xda-developers.com/showthread.php?t=2562988
I am not sure what post you were directing that at though.
EDIT: see below for intended post.
Sorry my paste didn't work as expected. here it is....
http://forum.xda-developers.com/showthread.php?p=55462340
Tried that
i couldnt get the APN settings to open up. Through the shortcut maker or terminal. I tried this before posting a new thread. i would have responded to the ongoing thread but XDA rules wont let me post to that one. Had to post here.
domcarreno said:
i couldnt get the APN settings to open up. Through the shortcut maker or terminal. I tried this before posting a new thread. i would have responded to the ongoing thread but XDA rules wont let me post to that one. Had to post here.
Click to expand...
Click to collapse
No problem, everyone starts somewhere.
Try the app "APN Change" from the play store.
better but . . .
So I tried the recommended settings change. Used the Change APN app. LTE is more reliable however when it switches from lte to 3g it will hang for some time or have no connection at all until i cycle airplane mode.
domcarreno said:
I am having issues with 4g and 3g switching on the device. Some times there will be no signal at all. 80% of the time doing an Airplane mode cycle will fix it. however this is dozens of times a day. This has been an issue since the M8 release. Can anyone send clear directions to a fix please.
System:
LS970
Cm version 11-20140916-SNAPSHOT-M10-ls970
Kernal 3.4.0-CM+
Click to expand...
Click to collapse
What radio do you have? (What was the last version of stock you were on?)
Can you get a logcat and radio logcat (logcat -b radio) of the issue happening?
I am using ZVC. The last stock rom i was on was Stocktimus CE 1.5
I dont know how to pull a logcat. Although i have quite a bit of experience flashing and recovering a device from soft brick, I am not much help with troubleshooting. I know just enough to be dangerous.
Hi it was my post that was linked to about adding APNs. I have found that after I flashed stock rooted zvc, updated prl and profile, and restored my CM11 backup, data works fine without requiring a manual APN edit.
However, currently I am running the unofficial GEE-based CM build. I had problems with NFC and battery life last time I tried the official builds (late September), and I do not know the cause or status of those issues. Maybe Shelnutt can weigh in
dwielunski said:
Hi it was my post that was linked to about adding APNs. I have found that after I flashed stock rooted zvc, updated prl and profile, and restored my CM11 backup, data works fine without requiring a manual APN edit.
However, currently I am running the unofficial GEE-based CM build. I had problems with NFC and battery life last time I tried the official builds (late September), and I do not know the cause or status of those issues. Maybe Shelnutt can weigh in
Click to expand...
Click to collapse
i just came from using stocktimus again because i tired of the radio nfc and battery issues as well. dwielunski, what stock rom do you use?
In CM and some others, if you go to settings>mobile networks, there is a built-in shortcut to the APN settings
But honestly, this issue is the most frustrating thing among the AOSP roms, at least for me. It's the one thing that makes me keep flashing back to stock-based ROM's every time I try CM or PA or anything. Why isn't there a clear-cut solution to this when it's such a common problem and we've known about it for so long?
domcarreno said:
i just came from using stocktimus again because i tired of the radio nfc and battery issues as well. dwielunski, what stock rom do you use?
Click to expand...
Click to collapse
Stock rooted zvc as I said. At one point I was using that with a bunch of xposed mods but pretty happy with cm these days. Probably will stay on this until L drops and we get a port. I haven't had any data issues but not sure about NFC