Go into settings > more > mobile networks. Make sure CDMA subscription is set to RUIM/SIM and system select is Automatic. If either weren't set correctly, set them as I've suggested and reboot or cycle airplane mode and see if it fixes data.
Go into settings > more > mobile networks. Make sure CDMA subscription is set to RUIM/SIM and system select is Automatic. If either weren't set correctly, set them as I've suggested and reboot or cycle airplane mode and see if it fixes data.
The 10.1.0.3 fix was meant for the MF1 firmware. So reverting to MB1 isn't the correct solution per say.
Baseband and updates
Ok, so the baseband is the firmware. I didn't know that 3rd party ROMs don't include the firmware updates. Or at least I didn't think it mattered that I kept the original firmware that was on the phone before I rooted and flashed custom ROMs, and never had to worry about firmware updates again. I have no desire to go back to Stock on the GSIII, but if it is the only (reliable) way to get updated firmware I guess I might consider it. I'm assuming new firmwares can be flashed in a custom recovery like a ROM? Also, I've never (before recently) seen any mention of needing to make sure I'm running a particular baseband before flashing a ROM on the ROM's install instructions. Are they usually compatible with most firmwares that the device could be running, even if they are older versions? Seems like that's a hugely important thing if compatibility becomes a problem, especially for "stable" releases like the recent GSIII 10.1.0.X releases. Thanks very much, this is very good to know, and I'm surprised I hadn't heard of it before.
Ok, so the baseband is the firmware. I didn't know that 3rd party ROMs don't include the firmware updates. Or at least I didn't think it mattered that I kept the original firmware that was on the phone before I rooted and flashed custom ROMs, and never had to worry about firmware updates again. I have no desire to go back to Stock on the GSIII, but if it is the only (reliable) way to get updated firmware I guess I might consider it. I'm assuming new firmwares can be flashed in a custom recovery like a ROM? Also, I've never (before recently) seen any mention of needing to make sure I'm running a particular baseband before flashing a ROM on the ROM's install instructions. Are they usually compatible with most firmwares that the device could be running, even if they are older versions? Seems like that's a hugely important thing if compatibility becomes a problem, especially for "stable" releases like the recent GSIII 10.1.0.X releases. Thanks very much, this is very good to know, and I'm surprised I hadn't heard of it before.
Running stock is the only hands off way to get firmware updates, indeed. The best way to know when there is an updated firmware available is to keep your ear to the ground and when an OTA is released, chances are it ships with an updated firmware pack. Within hours the mod community has said firmware available for us 3rd party ROM people, and we install it manually. And yes, its flashed in recovery just like a ROM.
As far as not having heard about it before, it wasn't as big of a deal until recently. There were a lot of instabilities (such as random reboots) that were occurring to people running AOSP ROMs, and once invisiblek realized it was because we weren't updating all parts of the "firmware package" (such as trust zone, RPM and so on) and we all updated the necessary parts of the firmware, those problems went away. There are also kernel changes happening lately that are dependent on modules in the latest firmware, and that is a big part of why it is suddenly necessary to keep them up to date. Let me know if you have any additional questions regarding this topic.
My data keeps going in and out after I flashed to latest stable 10.1.3. This happened when I came from 10.1 to nightlies before the stable came out so I just to my backup and stayed on 10.1. I finally flashed the newest 10.1.3 and the new radio MF1 and my phone reception still sucks. I don't understand why. It would come and have 1 bar then go back to no bars. I wiped cache, data, and dalvik. Installed 10.1.3, gapps, then new MF1 radio. Any ideas?!
Does the phone need to take a while to get a good signal?
edit: i also tried the switch home to auto and toggle airplane mode. seems to bring back 4g for a few moments then it dispapears
Does the phone need to take a while to get a good signal?
edit: i also tried the switch home to auto and toggle airplane mode. seems to bring back 4g for a few moments then it dispapears
Last edited:
can't change network to gsm!
I'm in Europe, running 10.1.0.3. When I go into settings-more-mobile-network-network mode and select 'global' it won't stick. It defaults to lte/cdma/evdo/gsm/wcdma and it won't recognize my sim card. Any ideas? I've tried phone info & *#*#4636#*#* to change the network types but it just won't stick
Any help would be greatly appreciated!
I'm in Europe, running 10.1.0.3. When I go into settings-more-mobile-network-network mode and select 'global' it won't stick. It defaults to lte/cdma/evdo/gsm/wcdma and it won't recognize my sim card. Any ideas? I've tried phone info & *#*#4636#*#* to change the network types but it just won't stick
Any help would be greatly appreciated!
I am running 10.1.0.3. Our club has a web site. The club roster is a PDF file. When I click on it from my phone's web browser (any browser), I am prompted for an app to download the file. If I choose any web browser, the download is unsuccessful. If I choose ESfile, it downloads successfully, but Adobe Reader cannot open it and reports "invalid PDF format". I can open previously downloaded PDF files without issue.
This is very informative, but I'd like to just clarify that if you're not on stock it's very easy to just flash the latest firmware in recovery when one comes up. The first sentence makes it seem difficult if you're not on stock or something. Usually it's linked in the OP of these threads. Though it's best to wait a few days before updating because the second to last firmware update broke data for a lot of people, even those on stock ROMs.
6/30 nightly
I tried 10.1.0.1, didn't work so well for my phone. Had to odin back to stock and update back to mf1/re-root, etc. I flashed the 6/30 cm nightly and it's worked like a charm. It seems like there have been problems with all of the updates (nightly and stable) since then. Has anyone updated to a latest nightly that works? Also if you haven't stick w/ the 6/30 nightly...works like a beaut.
Good luck to everyone.
I tried 10.1.0.1, didn't work so well for my phone. Had to odin back to stock and update back to mf1/re-root, etc. I flashed the 6/30 cm nightly and it's worked like a charm. It seems like there have been problems with all of the updates (nightly and stable) since then. Has anyone updated to a latest nightly that works? Also if you haven't stick w/ the 6/30 nightly...works like a beaut.
Good luck to everyone.
Does anyone know how to get MyVerizon app working? I read some posts in the Development thread that indicated that some necessary frameworks aren't included with CM to make this app function. But I can't find information on how to get it working.
Thanks for any help!
Thanks for any help!
To get MyVerizon and Verizon Visual Voicemail working, you will need either the VerizonSSO.apk, or the VerizonLogin.apk. I have found the latter to work more reliably for me. I will post it here in a bit.
Sent using Tapatalk
I've been updating daily to each new nightly without issue. My only problems have been the stable releases.
Errr isn't this backwards? So which nightly is more stable than Stable and doesn't introduce any new bugs?
Sent from my Nexus 4 using Tapatalk 2
So, a little clarification please. Is it a requirement to be on the MF1 modem in order to use CM 10.1.0.3, or can I stay at what I am currently using, FYI , I'm still using VRLHE and I haven't found a reason for me to change my modem at all.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13Post development questions/logcats etc in the development thread. Post "my data doesn't work" here (after reading the OP). The mods don't like the developers thread being filled with these questions, and it's contrary to the goal of that board. I'll keep both OPs updated.
Development thread: http://xdaforums.com/showthread.php?t=2053799
10.1.3 has been released.
As for all recent releases, please make sure you are on the MF1 modem
Cyanogen Mod 10.1.0 Release is now available:
http://get.cm/?device=d2vzw
Huge thanks to the CM devs! Pop on over to http://www.cyanogenmod.org/ and make a donation (mouse over "Community" at the top right then select "Donate to us") if you'd like to help support the CM project!
Anyone looking for mastamoon's build with his tweaks, reverts, and cherrypicks - it was moved to Android Development. Here is the link! http://xdaforums.com/showthread.php?t=2094251
Rooting, flashing, installing roms, following any instructions below, will void your phone's warranty and there is a chance (however small) that you'll screw up and permanently break your phone. Anything you do to your phone in violation of the warranty, insurance, or anything else is at your own risk!
-+-+-+-+-+-+-+-+ OFFICIAL DOWNLOAD LINK -+-+-+-+-+-+-+-+
http://get.cm/?device=d2vzw
-+-+-+-+-+-+-+-+ NIGHTLY CHANGE LOG -+-+-+-+-+-+-+-+
App from invisiblek: https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies
Or: http://10.1.cmxlog.com/?device=d2vzw
-+-+-+-+-+-+-+-+ GUIDE ON HOW TO ROOT AND FLASH -+-+-+-+-+-+-+-+
http://xdaforums.com/showthread.php?t=2046439
-+-+-+-+-+-+-+-+ HOW TO BACKUP AND RESTORE YOUR IMEI -+-+-+-+-+-+-+-+
http://xdaforums.com/showthread.php?t=1852255&highlight=nvbackup
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ -+-+-+-+-+-+-+-+
https://plus.google.com/+CyanogenMod/posts
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ COMMUNITY -+-+-+-+-+-+-+-+
https://plus.google.com/communities/107373456059326217974
-+-+-+-+-+-+-+-+ KNOWN / REPORTED ISSUES -+-+-+-+-+-+-+-+
On the 10.1.3 RC: (updated 7/18)
1: Only use the MF1 AIO file available here.
2: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
3: Verizon FIOS app crashes
4: BT headsets don't work with the Skype app
5: One channel audio on headphones.
6: Low recording volume using the camcorder.
7: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
On the latest nightlies: (updated 7/18)
1: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
2: Verizon FIOS app crashes
3: BT headsets don't work with the Skype app
4: Low recording volume using the camcorder.
5: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
Many other problems are fixed by simply re-flashing the same rom file over itself.
Please PM repeatable issues from the release to me. Post a logcat in the developer thread or a JIRA ticket if you expect it to get fixed.
-+-+-+-+-+-+-+-+ SPECIAL NOTES -+-+-+-+-+-+-+-+
1. To enable Developer Options: Menu > Settings > About Phone. Tap build number 7 times to unlock Developer Options
2. Photosphere: This feature is not offered on non-nexus devices
3. There are a lot of questions about how CM10.1 moves your files to sdcard/0/ folder. This is to support multi-users. If you flash back and forth between a non-4.2 ROM and CM10.1 (which is 4.2) you'll end up with sdcard/0/0/..etc since the upgrade to 10.1 moves your folders into a new /0/. You can safely move your files out of /0/ back to your sdcard if you're on CM10, or back to the first /0 folder if you're on CM10.1.
4. Don't update from CM10 to CM10.1 using the built-in cmupdater. Update in recovery for the first flash from CM10 to 10.1. Once on 10.1 you can use cmupdater.
-+-+-+-+-+-+-+-+ INSTALLATION NOTES -+-+-+-+-+-+-+-+
- CM can be flashed using CWM or TWRP. Only use the latest TWRP or CWM!
- When you install CM10.1 your data will be moved to a new folder /0/ (this is to support multi-users).
- Make sure you have the latest CWM or TWRP installed so that your recovery isn't confused by the new location of your backups. Official TWRP d2vzw or Latest CWM (scroll down to Samsung Galaxy S3 (Verizon))
- GAPPS is not included in any CM download. You must flash a gapps zip if coming from another rom or when starting with a clean install. You do not need to flash gapps when 'dirty flashing' over a previous CM install. Download gapps here.
- According to Cyanogen it is possible to flash CM10.1 over top of an existing CM10 installation. It is generally recommended to do a clean install if you run into any issues.
- Always make a backup before you try a dirty flash or upgrade to CM10.1.
-+-+-+-+-+-+-+-+ HOW TO INSTALL OVER CM10 -+-+-+-+-+-+-+-+
- Consider backing up your IMEI if you haven't already (link)
- If you use a lockscreen pattern disable it
- Flash the latest CWM or Official TWRP d2vzw
- Download a CM10.1 rom (nightly or unofficial) to your sd card
- Download the latest gapps from goo to your sd card
- Reboot into recovery
- Make a backup
- Wipe cache and dalvik (if you want)
- Install CM10.1 zip
- Install gapps
- Reboot
- After your phone boots go into Menu > Settings > Apps. Under "All" find "Clock", open it, and click "Clear Data"
-+-+-+-+-+-+-+-+ HOW TO INSTALL FROM ANY ROM OTHER THAN CM -+-+-+-+-+-+-+-+
- Consider backing up your IMEI if you haven't already (link)
- Flash the latest CWM or Official TWRP d2vzw
- Download a CM10.1 rom (nightly or unofficial) to your sd card
- Download the latest gapps from goo to your sd card
- Use an app like Titanium Backup or Mybackup Pro to backup your apps (if you want)
- Use an app like SMS Backup+ to backup your text messages and call log (if you want)
- Reboot into recovery
- Make a backup
- Wipe cache and dalvik (if you want)
- Wipe Data/Factory Reset/System
- Install CM10.1 zip
- Install gapps
- Reboot
- Reinstall Titanium Backup/Mybackup Pro/SMS Backup+ and restore the stuff you have to have, but its better to reinstall things from the market if possible (keep in mind your backups will be located in sdcard/0/) (if you want)
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I am not a developer, I have no direct association with the CM project, I am just a community member. I will do my best to maintain this thread. Please PM me with any OP suggestions!10
I'm starting a petition for you to write your own animation. If I get 2 more signatures, you have to do it. +1's and Thanks to this post count as signatures. Contract is binding and non-negotiable. You are as obligated to perform your end as the CM10.1 devs are to listen to your petition. Petition open.
5
Actually, I'm not sure if this is fixed in 3.4 or not. I usually reboot too often to see this (for me it would take like a day for the problem to surface)
It's most definitely on the radar, just not high priority. I'll try to keep it running for an extended period of time and see if this problem comes up. (But the weekend might be a bad time to make a promise like this =P)
The problem with 90% of these "one-off" issues that people have is that there are too many variables. My suggestion, if you are running into an unreported or obscure problem, is to wipe data/factory reset, reflash your rom and official gapps only. No custom stuff (inverted gapps, custom kernels, etc) and boot up, don't install any apps, and see if the problem is still there. When you start replacing system files with "unofficial" ones (gapps, kernel/modules) many different things can happen that are tough to account for. This goes for installing root apps too, or apps designed to "monitor" your device for certain things. Who knows WTF a root app is doing mucking around on your device, and these battery monitor, tasker, etc apps can cause wakelocks and other unintentional problems. Especially since you don't know how an app for say, ICS, would play with JB 4.2.2, and who knows if the app dev has updated to account for any changes to JB. I don't mean to bash anyone's app or kernel, I'm sure most of them run perfectly fine, but getting to the root cause of a problem has to start with eliminating all external variables.
Ok, enough of my long-winded rants.
Regardless of what you have running/flashed/etc, make sure you are posting relevant logcats and dmesgs, especially on these odd problems that nobody else seems to have. If you don't, your post isn't much help to anyone. (Hint: use pastebin!)5http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20121229-UNOFFICIAL-d2vzw.zip
Has LockClock included:
https://plus.google.com/105849811393167071979/posts/KBHPeMRXpGo
Also the gps squash from caf:
http://review.cyanogenmod.org/#/c/29349/
Sync'd about 15-20 minutes ago4For those of you having trouble with the Lock Screen Clock, here is what works to get it up and running. First you go into system settings (settings), then under the "interface" section you will hit "system". There you will find the settings for "Lock clock widget". After you have set up all the preferences, get your phone back to the lock screen (I found that going to your home screen and then hitting the power button is the easiest way). Now that you are sitting at a black screen, hit the power button, or home button, to wake the screen. Immediately upon doing that, you will see the two big gridlines appear on each side of the screen, the subtle prompt to show you there are screens to each side you can swipe. Swipe the screen from left to right. You will see a big "+" in the middle of the screen. Now, while at that screen with the "+", swipe back from right to left and it will take you back to the main lock screen. As soon as you hit the main lock screen, long press the screen and drag it up into the garbage can. If you correctly deleted the home lock screen, it will now automatically advance you back to the big "+" screen. Hit the big "+". You will now see you have a few options. The third one down will be "Lock Clock". Hit that and you will now have it as your lock screen. I will however say that it is a little bit buggy right now, especially if you are trying to get appointments to show, but it does work!
I am on the latest OFFICIAL 10.1-20121231-NIGHTLY, flashed dirty from yesterdays nightly. I will be doing a full wipe and clean install later today to see if the anomalies with the new lock screen widget persist or go away. What I am seeing is that when you add the lock screen widget, it will show your calendar event, but after the screen goes to sleep, the appointments are no longer on the widget when you wake the screen back up. The weather is there, and the battery state is there right below the weather, but no appointments. If I swipe that screen showing weather and battery state back and forth from the "+" screen, the appointments show back up, but the battery state is missing. Also, turning the battery status off on the lock screen doesn't change it from not showing the appointments. I think that should be enough info to point someone to a fix.
I hope that helps!
Scott
